diff --git a/.github/workflows/availability-probe.yml b/.github/workflows/availability-probe.yml new file mode 100644 index 00000000..602a17b6 --- /dev/null +++ b/.github/workflows/availability-probe.yml @@ -0,0 +1,88 @@ +# ============================================================================= +# Availability probe (CDS-CSO-AVR, CDS-TRC-USH) +# ============================================================================= +# An availability monitor on infrastructure independent of the offering: it +# runs on GitHub Actions, not AWS, probes the core services over HTTPS every 15 +# minutes (scripts/availability-probe.py), keeps 35 days of history, derives +# availability incidents, and publishes JSON + Markdown to the repository's +# `availability-status` branch. GitHub serves that branch, so the status stays +# readable when the offering's CloudFront or S3 is down: +# https://raw.githubusercontent.com/sam-aydlette/samaydlette.com/availability-status/availability-status.json +# https://github.com/sam-aydlette/samaydlette.com/blob/availability-status/availability-status.md +# +# The branch holds one commit, replaced on every run (history lives in the +# JSON), so the repository does not grow by a commit every 15 minutes. The +# workflow's token can write contents (no narrower scope exists); the job only +# ever pushes refs/heads/availability-status, and main is protected by its own +# branch rules. The deploy reads this feed and fails when it is missing or more +# than 2 hours old, so the published package never cites a monitor that has +# stopped (scripts/availability-probe.py --check-fresh). +# +# Caveats stated in the feed: history begins at the first run; GitHub may delay +# a scheduled run under load, and disables schedules on a repository with no +# activity for 60 days (the deploy's freshness check then fails). +# ============================================================================= +name: Availability probe + +on: + schedule: + - cron: '*/15 * * * *' + push: + branches: [main] + workflow_dispatch: + +permissions: {} + +concurrency: + group: availability-probe + cancel-in-progress: false + +jobs: + probe: + name: Probe the core services from outside AWS + runs-on: ubuntu-latest + timeout-minutes: 10 + permissions: + contents: write # push the status branch; nothing else + steps: + - name: Checkout the probe + uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 + with: + ref: main + persist-credentials: false + + - name: Read the previous status feed + run: | + set -euo pipefail + # Public repository: an anonymous fetch. No branch yet means a first run. + if git fetch --depth 1 --quiet origin availability-status 2>/dev/null; then + git show FETCH_HEAD:availability-status.json > previous-status.json || echo '{}' > previous-status.json + else + echo '{}' > previous-status.json + fi + + - name: Probe the core services + run: python3 scripts/availability-probe.py --previous previous-status.json --out-dir status-out + + - name: Publish the status feed to the availability-status branch + env: + GH_TOKEN: ${{ github.token }} + REPO: ${{ github.repository }} + run: | + set -euo pipefail + cd status-out + git init --quiet + git checkout --quiet --orphan availability-status + git add availability-status.json availability-status.md + git -c user.name="availability-probe" -c user.email="availability-probe@users.noreply.github.com" \ + commit --quiet -m "Availability status $(jq -r .generated_at availability-status.json)" + auth=$(printf 'x-access-token:%s' "$GH_TOKEN" | base64 -w0) + echo "::add-mask::$auth" + git -c http.extraheader="AUTHORIZATION: basic $auth" \ + push --quiet --force "https://github.com/${REPO}.git" HEAD:refs/heads/availability-status + + # After publishing: an ongoing incident fails the run, and GitHub notifies + # the operator of the failed scheduled run (email). The status is already + # published either way. + - name: Alert on an ongoing availability incident + run: python3 scripts/availability-probe.py --fail-on-incident status-out/availability-status.json diff --git a/.github/workflows/codeql.yml b/.github/workflows/codeql.yml new file mode 100644 index 00000000..b80a2e80 --- /dev/null +++ b/.github/workflows/codeql.yml @@ -0,0 +1,132 @@ +# ============================================================================= +# CodeQL (SAST of first-party code; VDR-CSO-DET, VDR-CSO-DAC, VDR-TFR-PSD) +# ============================================================================= +# Static analysis of the code this system ships and runs, uploaded to GitHub +# code scanning (free on a public repository): +# +# repo this repository: Python (the generators and gates in scripts/, +# tools/), JavaScript (the runtime Lambda, the watchdog, the +# CloudFront functions, the site and trust-center JS) and the +# GitHub Actions workflows themselves. +# silk-reeling the Silk Reeling app as deployed: its Python API Lambda and +# its SPA. Its source lives in a private repository with no code +# scanning of its own, so it is analysed here, from the same ref +# the deploy builds (vars.SILK_REELING_REF, default main). +# +# When: on every push and pull request to main (changed code is analysed before +# and as it merges), after every successful deploy to main (the Silk Reeling +# code the deploy just shipped), and daily (new queries over unchanged code). +# +# The VDR builds read the open CodeQL alerts on main through the code-scanning +# API (scripts/fetch-detection-feeds.sh); the detection gate fails the run when +# any category below has no error-free analysis on main in the last 72 hours +# (detection.codeql, infrastructure/schemas/detection-feeds.json, which lists the +# categories this file produces; tests/test_detect_wiring.py keeps them equal). +# ============================================================================= +name: CodeQL + +on: + push: + branches: [ main ] + pull_request: + branches: [ main ] + schedule: + - cron: '41 5 * * *' # 05:41 UTC daily + workflow_dispatch: + # After every deploy to main; the job conditions drop deploy runs that did not + # succeed or came from a pull request. + workflow_run: + workflows: [Deploy Website with OPA Compliance] + types: [completed] + branches: [main] + +permissions: + contents: read + +concurrency: + group: codeql-${{ github.event_name == 'pull_request' && github.ref || 'main' }} + cancel-in-progress: false + +jobs: + repo: + name: CodeQL (${{ matrix.language }}) + if: >- + github.event_name != 'workflow_run' || + (github.event.workflow_run.conclusion == 'success' && github.event.workflow_run.event != 'pull_request') + runs-on: ubuntu-latest + timeout-minutes: 30 + permissions: + contents: read + security-events: write # upload the results to code scanning + strategy: + fail-fast: false + matrix: + language: [python, javascript-typescript, actions] + steps: + - name: Checkout + uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 + with: + persist-credentials: false + + - name: Initialize CodeQL + uses: github/codeql-action/init@9b3254085494b55a0f7c4c2b3d2d52cc712ce370 # v4.39.1 + with: + languages: ${{ matrix.language }} + build-mode: none + + - name: Analyze + uses: github/codeql-action/analyze@9b3254085494b55a0f7c4c2b3d2d52cc712ce370 # v4.39.1 + with: + category: /language:${{ matrix.language }} + + silk-reeling: + name: CodeQL Silk Reeling (${{ matrix.language }}) + # Needs the private-source token, which pull requests do not get; the + # app's code does not change in this repository's pull requests anyway. + if: >- + github.event_name != 'pull_request' && + (github.event_name != 'workflow_run' || + (github.event.workflow_run.conclusion == 'success' && github.event.workflow_run.event != 'pull_request')) + runs-on: ubuntu-latest + timeout-minutes: 30 + permissions: + contents: read + security-events: write # upload the results to code scanning + strategy: + fail-fast: false + matrix: + language: [python, javascript-typescript] + steps: + - name: Checkout + uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 + with: + persist-credentials: false + + # The app's source only, without its git metadata (which would carry the + # token in the remote URL). + - name: Fetch the Silk Reeling source (the ref the deploy builds) + env: + SILK_REELING_REF: ${{ vars.SILK_REELING_REF || 'main' }} + SILK_REELING_REPO_TOKEN: ${{ secrets.SILK_REELING_REPO_TOKEN }} + run: | + set -euo pipefail + [ -n "${SILK_REELING_REPO_TOKEN}" ] || { echo "::error::SILK_REELING_REPO_TOKEN is not set"; exit 1; } + git clone --quiet --depth 1 --branch "$SILK_REELING_REF" \ + "https://x-access-token:${SILK_REELING_REPO_TOKEN}@github.com/sam-aydlette/silk-reeling-mirror.git" silk-reeling + rm -rf silk-reeling/.git + ls silk-reeling/backend silk-reeling/frontend > /dev/null + + - name: Initialize CodeQL + uses: github/codeql-action/init@9b3254085494b55a0f7c4c2b3d2d52cc712ce370 # v4.39.1 + with: + languages: ${{ matrix.language }} + build-mode: none + source-root: silk-reeling + + # The results (rule, file path, line, message) go to this repository's code + # scanning; the database, which holds the private source, is not uploaded. + - name: Analyze + uses: github/codeql-action/analyze@9b3254085494b55a0f7c4c2b3d2d52cc712ce370 # v4.39.1 + with: + category: /silk-reeling/language:${{ matrix.language }} + upload-database: false diff --git a/.github/workflows/deploy-with-opa.yml b/.github/workflows/deploy-with-opa.yml index 933f590b..9742ef52 100644 --- a/.github/workflows/deploy-with-opa.yml +++ b/.github/workflows/deploy-with-opa.yml @@ -102,7 +102,7 @@ permissions: issues: write pull-requests: write security-events: write - id-token: write # assume the plan (compliance-check) and deploy roles via GitHub OIDC (POAM-001) + id-token: write # assume the plan (compliance-check) and deploy roles via GitHub OIDC jobs: # =========================================================================== @@ -119,8 +119,9 @@ jobs: # run if any of them is still queued after the grace period, turning an # open-ended hang into a fast, re-runnable failure. # - # `deploy` and `notify` are deliberately not watched: they are queued waiting - # on their dependencies, which is correct behaviour and not a stuck runner. + # Jobs with `needs:` (the deploy, the simulated assessor, the two publisher + # proofs, notify) are deliberately not watched: they are queued waiting on + # their dependencies, which is correct behaviour and not a stuck runner. # # Known limitation: this job needs a runner too, so it cannot help when # allocation fails completely. It covers the partial case actually observed, @@ -139,17 +140,20 @@ jobs: GRACE_MINUTES: '12' run: | set -euo pipefail - # Watch by exclusion, not by listing the jobs to watch. `deploy` and - # `notify` are queued waiting on their dependencies, which is correct; + # Watch by exclusion, not by listing the jobs to watch. A job with + # `needs:` is queued waiting on its dependencies, which is correct; # everything else queued has no runner. Excluding is the fail-safe # direction: renaming a watched job would silently drop it from an - # inclusion list, whereas here it stays watched, and only a NEW dependent - # job could cause a false cancel — which is loud and gets noticed. - DEPENDENT='["Deploy Infrastructure","Notify on Failure","Queue watchdog"]' + # inclusion list, whereas here it stays watched. DEPENDENT is every job + # with `needs:` plus this one; tests/test_queue_watchdog.py derives it + # from this file and fails when a dependent job is missing. A job that + # calls a reusable workflow appears as " / ", + # so a dependent name also excludes everything under it. + DEPENDENT='["Deploy Infrastructure","Simulated assessor","Prove the certification package maintainer","Prove the incident report publisher","Post-deploy simulated assessor","Post-deploy assessment binding","Notify on Failure","Queue watchdog"]' + FILTER='[.jobs[] | select(.status == "queued") | .name | select(. as $n | '"$DEPENDENT"' | any(. as $d | $n == $d or ($n | startswith($d + " / "))) | not)] | join(", ")' stuck='' for _ in $(seq 1 $(( GRACE_MINUTES * 2 ))); do - stuck=$(gh api "repos/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID/jobs" \ - --jq "[.jobs[] | select(.status == \"queued\") | .name] - $DEPENDENT | join(\", \")") + stuck=$(gh api "repos/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID/jobs" --jq "$FILTER") if [ -z "$stuck" ]; then echo "All independent jobs have runners." exit 0 @@ -173,6 +177,10 @@ jobs: name: Unit tests (pytest + opa test) runs-on: ubuntu-latest timeout-minutes: 10 + # No credentials of any kind: this job runs the test suite and its unpinned + # test tools, so it gets no OIDC token (the workflow default grants one). + permissions: + contents: read steps: - name: Checkout code uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 @@ -188,8 +196,20 @@ jobs: chmod 755 ./opa sudo mv opa /usr/local/bin + # The completeness gate (operator's decision of 2026-11-05): every + # applicable FedRAMP rule must be Implemented or Not Applicable, or nothing + # deploys. The deploy job needs this job, so this runs before any apply. + - name: FedRAMP rules complete (no gaps) + run: python3 scripts/_frr.py --complete + - name: Python unit tests - run: python3 -m pytest tests/ -q + run: python3 -m pytest tests/ -q --junitxml=pytest-results.xml + + # FRC-CSX-VVR: every test a FedRAMP rule record cites as evidence ran and + # passed in the run above (a skipped or missing one fails too). The result + # per record is signed and published by the deploy as frr-evidence.json. + - name: FedRAMP rule evidence passed (cited tests) + run: python3 scripts/check-frr-evidence.py --junit pytest-results.xml --output frr-evidence.json --commit "${{ github.sha }}" # REQ-GOV-2: run the method's conformance tests (data/method-profile.json # maps Appendix B T1-T74 to the tests that implement them) and record the @@ -205,7 +225,9 @@ jobs: uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7.0.2 with: name: conformance-results - path: conformance-results.json + path: | + conformance-results.json + frr-evidence.json if-no-files-found: error # The policy suite is an exhibit: format is enforced, strict compilation @@ -243,11 +265,29 @@ jobs: - name: Exception register expiry check run: python3 scripts/check-exceptions.py + # AFC-CSO-NOC: the FedRAMP Security Inbox contact (data/cds/offering.json) + # cannot change without a history entry recording that FedRAMP was + # notified. Compared with the merge base on a pull request and with the + # previous commit on a push, so the history is also append-only. + - name: FedRAMP Security Inbox change notice (AFC-CSO-NOC) + env: + BASE_REF: ${{ github.event_name == 'pull_request' && github.base_ref || '' }} + BEFORE_SHA: ${{ github.event_name == 'push' && github.event.before || '' }} + run: | + base="" + if [ -n "$BASE_REF" ] && git fetch --no-tags --depth=1 origin "$BASE_REF"; then + git show FETCH_HEAD:data/cds/offering.json > fsi-base.json 2>/dev/null && base="--base fsi-base.json" + elif [ -n "$BEFORE_SHA" ] && git fetch --no-tags --depth=1 origin "$BEFORE_SHA"; then + git show "$BEFORE_SHA":data/cds/offering.json > fsi-base.json 2>/dev/null && base="--base fsi-base.json" + fi + # shellcheck disable=SC2086 # $base is an optional flag pair + python3 scripts/check-fsi-notice.py $base + # Known Go-vs-Wasm builtin divergences (%q, %v-on-sets, host time) are # banned at lint time; the parity test catches what the corpus exercises, # this catches the rest before it exists. It also requires every sprintf # format to be a literal (or concat of literals) with no precision - # specifier: the condition the closed POAM-035 (sprintf-js) rested on, kept + # specifier: the condition the closed sprintf-js finding rested on, kept # as a guard. - name: Wasm-safe builtin check run: python3 scripts/check-wasm-safe.py @@ -319,7 +359,7 @@ jobs: # instead of hanging on GitHub's 6-hour default. timeout-minutes: 6 with: - # GitHub OIDC role assumption — no long-lived access key (POAM-001). + # GitHub OIDC role assumption — no long-lived access key. # This job only plans, so it assumes the plan-only role # (infrastructure/bootstrap/plan-role.tf): read-only account access plus # the state lock. Deploy credentials exist only in the deploy job, behind @@ -582,15 +622,20 @@ jobs: # signal via the GitHub Actions OIDC provider. Without it, the Sigstore # signing step cannot obtain an OIDC token and `cosign sign-blob` fails. id-token: write - # actions: read lets GITHUB_TOKEN download the weekly ZAP DAST artifact. - # Dependabot alerts are read with the DEPENDABOT_ALERTS_TOKEN secret: - # GITHUB_TOKEN cannot read them. + # actions: read lets GITHUB_TOKEN download the ZAP DAST artifacts, and + # security-events: read the CodeQL code-scanning alerts. Dependabot alerts + # are read with the DEPENDABOT_ALERTS_TOKEN secret: GITHUB_TOKEN cannot. actions: read + security-events: read # Detect-and-recover gate events (infrastructure/schemas/gate-modes.json) are # appended here by scripts/_gates.py and published with this run's evidence. env: GATE_EVENTS_FILE: /tmp/gate-events.jsonl - needs: [test, compliance-check, security-scan] + needs: [test, compliance-check, security-scan, simulated-assessor] + # The KSI signal this deploy published: the post-deploy assessment must + # cover exactly it. + outputs: + signal_id: ${{ steps.ksi.outputs.signal_id }} # IMPORTANT: Only deploy if on main branch AND security check passed if: github.ref == 'refs/heads/main' && needs.compliance-check.outputs.compliant == 'true' environment: ${{ github.event.inputs.environment || 'prod' }} @@ -606,6 +651,29 @@ jobs: with: fetch-depth: 0 + # The package maintenance and quarterly cycle records (CPO-CSX-CPM, + # CCM-OCR-AVL, CDS-CSO-HAD, SDR-CSX-KMT) describe the system after this + # deploy, so it fails here, before anything is applied or built, unless the + # unattended maintainer's role variable and environment are in place. The + # package-maintainer job below then proves the role publishes. + - name: Package maintainer preflight + env: + PACKAGE_MAINTENANCE_ROLE_ARN: ${{ vars.AWS_PACKAGE_MAINTENANCE_ROLE_ARN }} + GITHUB_TOKEN: ${{ github.token }} + run: python3 scripts/check-package-maintainer.py + # The incident report records (IEC-CSO-IIR/OIR/FIR/AIR) describe the system + # after a successful deploy, which includes the unattended publisher in + # .github/workflows/incident-reports.yml. Fail before anything is applied if + # its prerequisites are missing: the role variable set and naming the + # bootstrap role, and the incident-reports environment main-only (checked + # when the job token can read it; said so when it cannot). The + # incident-publisher job below then proves the role publishes. + - name: Incident report publisher preflight + env: + INCIDENT_REPORTS_ROLE_ARN: ${{ vars.AWS_INCIDENT_REPORTS_ROLE_ARN }} + GITHUB_TOKEN: ${{ github.token }} + run: python3 scripts/check-incident-publisher.py + - name: Setup Terraform uses: hashicorp/setup-terraform@dfe3c3f87815947d99a8997f908cb6525fc44e9e # v4.0.1 with: @@ -638,7 +706,7 @@ jobs: # retry the assume-role call to ride through a brief blip. timeout-minutes: 6 with: - # GitHub OIDC role assumption — no long-lived access key (POAM-001). + # GitHub OIDC role assumption — no long-lived access key. # Role ARN is a repo variable so the account ID stays out of the YAML. role-to-assume: ${{ vars.AWS_DEPLOY_ROLE_ARN }} aws-region: ${{ env.AWS_REGION }} @@ -689,6 +757,15 @@ jobs: name: conformance-results path: infrastructure/ + # The simulated assessor's pre-deploy signed set (simulated-assessment.json + + # .bundle), verified against the pinned assessor identity, and bound to the + # commit and published signal it covered, when the SDR is built. + - name: Download the simulated assessment + uses: actions/download-artifact@9000827ccba6bdab643e8b6fd33ac0654aef8333 # v8.0.2 + with: + name: simulated-assessment-pre-deploy + path: infrastructure/ + # ------------------------------------------------------------------------- # REBUILD MONITORING FUNCTION # ------------------------------------------------------------------------- @@ -762,7 +839,7 @@ jobs: echo "No existing IAM role policy found - will be created" fi - # Import the at-rest CMK + its alias if they exist (Task 6, POAM-011/018). + # Import the at-rest CMK + its alias if they exist. # State is ephemeral per run, so the unconditional aws_kms_key.at_rest would # otherwise be created fresh every run — orphaning keys and colliding on the # alias. Resolve the key by its stable alias and adopt both into state. @@ -787,8 +864,8 @@ jobs: echo "No existing at-rest CMK found - will be created" fi - # Import the compliance Lambda's dead-letter queue if it exists (Task 8b, - # POAM-013). Ephemeral state: adopt it so it isn't recreated each run. + # Import the compliance Lambda's dead-letter queue if it exists. + # Ephemeral state: adopt it so it isn't recreated each run. DLQ_URL=$(aws sqs get-queue-url --queue-name samaydlette-com-opa-compliance-dlq --query 'QueueUrl' --output text 2>/dev/null || true) if [ -n "$DLQ_URL" ] && [ "$DLQ_URL" != "None" ]; then if ! terraform state show 'aws_sqs_queue.compliance_dlq[0]' >/dev/null 2>&1; then @@ -802,8 +879,8 @@ jobs: echo "No existing compliance DLQ found - will be created" fi - # Import the runtime-signal signing CMK + alias if they exist (Task 5, - # POAM-002). Ephemeral state: resolve the key by its stable alias and + # Import the runtime-signal signing CMK + alias if they exist. + # Ephemeral state: resolve the key by its stable alias and # adopt both so the asymmetric signing key is not recreated each run. if aws kms describe-key --key-id alias/samaydlette-com-runtime-signing >/dev/null 2>&1; then SIGNING_KEY_ID=$(aws kms describe-key --key-id alias/samaydlette-com-runtime-signing --query 'KeyMetadata.KeyId' --output text) @@ -849,7 +926,7 @@ jobs: echo "No existing DNSSEC KSK found - will be created" fi - # Import the access-log bucket if it exists (Task 7, POAM-005). Ephemeral + # Import the access-log bucket if it exists. Ephemeral # state: the bucket would otherwise be recreated each run (and fail as a # name collision), so adopt it when present. if aws s3api head-bucket --bucket samaydlette-com-logs >/dev/null 2>&1; then @@ -865,7 +942,7 @@ jobs: fi # Import the compliance Lambda's log group if it exists (auto-created by - # Lambda; now managed for customer-CMK encryption + retention, POAM-018). + # Lambda; now managed for customer-CMK encryption + retention). # Must precede the Lambda import since the function depends_on it. if aws logs describe-log-groups --log-group-name-prefix "/aws/lambda/samaydlette-com-opa-compliance" --query 'logGroups[?logGroupName==`/aws/lambda/samaydlette-com-opa-compliance`]' --output text | grep -q .; then echo "Compliance Lambda log group exists in AWS" @@ -1146,10 +1223,27 @@ jobs: # DETECTION INPUTS AND G7 — before anything is applied # ------------------------------------------------------------------------- # The previous VDR, Dependabot alerts, the CISA KEV catalog, FIRST EPSS and - # the latest weekly DAST report, fetched here (not after apply) so that a + # the latest DAST reports and CodeQL alerts, fetched here (not after apply) so that a # detection failure stops the deploy before it mutates anything (T52: G7 # blocks every team). A failed fetch leaves .error, never an empty # stand-in. The SAST files come from the security-scan job, Grype from above. + # The authenticated DAST of the Silk Reeling API (zap-dast.yml) signs in with + # these; without them the API scan fails and, 72 hours later, so does every + # VDR build. Stop here instead, before anything is applied or published. + - name: Require the DAST scanner credentials + env: + SILK_DAST_USERNAME: ${{ secrets.SILK_DAST_USERNAME }} + SILK_DAST_PASSWORD: ${{ secrets.SILK_DAST_PASSWORD }} + SILK_DAST_TOTP_SECRET: ${{ secrets.SILK_DAST_TOTP_SECRET }} + SILK_DAST_USER_POOL_ID: ${{ secrets.SILK_DAST_USER_POOL_ID }} + run: | + missing="" + for k in SILK_DAST_USERNAME SILK_DAST_PASSWORD SILK_DAST_TOTP_SECRET SILK_DAST_USER_POOL_ID; do + [ -n "${!k:-}" ] || missing="$missing $k" + done + [ -z "$missing" ] || { echo "::error::repository secret(s) not set:$missing (docs/runbooks/dast-scanner-user.md)"; exit 1; } + echo "DAST scanner credentials present." + - name: Fetch detection feeds working-directory: infrastructure env: @@ -1166,8 +1260,19 @@ jobs: --grype grype-python.json grype-js.json grype-lambda.json grype-a11y.json \ --dependabot dependabot-alerts.json --previous-vdr previous-vdr-report.json \ --checkov checkov-results.sarif --tfsec tfsec-results.json \ + --codeql codeql-alerts.json --zap-api zap-api-report.json \ --output detection.json + # VDR-CSO-AKE: nothing with a known exploited vulnerability is activated. + # Runs before the plan, the apply and the website sync (G1 in the VDR build + # runs after them). + - name: KEV gate before apply (VDR-CSO-AKE) + working-directory: infrastructure + run: | + python3 ../scripts/kev-gate.py --kev kev-catalog.json \ + --grype grype-python.json grype-js.json grype-lambda.json grype-a11y.json \ + --dependabot dependabot-alerts.json + - name: Generate fresh Terraform plan working-directory: infrastructure run: terraform plan -lock-timeout=300s -out=tfplan @@ -1177,7 +1282,7 @@ jobs: run: terraform apply -lock-timeout=300s -auto-approve tfplan # The app Lambda once ran a stale environment for four months while every - # apply reported it updated (POAM-038). Ask the running app which Cognito + # apply reported it updated. Ask the running app which Cognito # settings it sees and stop before publishing if they differ from Terraform. - name: Silk Reeling runtime config matches Terraform run: | @@ -1321,6 +1426,7 @@ jobs: fi - name: Build deploy-time KSI signal + id: ksi working-directory: infrastructure env: # Tells the emitter to pre-populate provenance.attestation with the @@ -1332,6 +1438,11 @@ jobs: run: | echo "Building deploy-time KSI signal..." python3 ../scripts/build-ksi-signal.py + sid=$(jq -r '.signal_id' ksi-signal.json) + if ! printf '%s' "$sid" | grep -qE '^[0-9a-f-]{36}$'; then + echo "::error::the built KSI signal carries a malformed signal_id"; exit 1 + fi + echo "signal_id=$sid" >> "$GITHUB_OUTPUT" echo "Signal contents (truncated):" jq '{signal_id, emitted_at, csp, system_id, component_count: (.components | length), @@ -1360,6 +1471,30 @@ jobs: - name: Install cosign uses: sigstore/cosign-installer@7e8b541eb2e61bf99390e1afd4be13a184e9ebc5 # v3.10.1 + # IVV-CSO-FIA / SDR-CSO-FRR: the pre-deploy assessment validated the state + # that is live now, before this deploy publishes anything. Read that state's + # KSI signal independently (signature verified against the deploy identity) + # so the SDR and CPO builders can refuse a set that covered any other signal + # or commit. Nothing under /.well-known/ has been replaced yet at this point. + - name: Bind the pre-deploy assessment to the state it covered + working-directory: infrastructure + run: | + set -euo pipefail + for f in ksi-signal.json ksi-signal.bundle; do + code=$(curl -sSL --max-time 30 -o "live-$f" -w '%{http_code}' "https://samaydlette.com/.well-known/$f") \ + || { echo "::error::cannot fetch the published $f"; exit 1; } + [ "$code" = 200 ] || { echo "::error::fetching the published $f returned HTTP $code"; exit 1; } + done + cosign verify-blob --bundle live-ksi-signal.bundle \ + --certificate-identity 'https://github.com/sam-aydlette/samaydlette.com/.github/workflows/deploy-with-opa.yml@refs/heads/main' \ + --certificate-oidc-issuer https://token.actions.githubusercontent.com live-ksi-signal.json + sid=$(jq -r '.signal_id' live-ksi-signal.json) + if ! printf '%s' "$sid" | grep -qE '^[0-9a-f-]{36}$'; then + echo "::error::the published KSI signal carries a malformed signal_id"; exit 1 + fi + echo "ASSESSED_SIGNAL_ID=$sid" >> "$GITHUB_ENV" + echo "The pre-deploy assessment must cover commit $GITHUB_SHA and published signal $sid." + - name: Sign KSI signal working-directory: infrastructure run: | @@ -1393,10 +1528,10 @@ jobs: opa-policy-bundle.tar.gz echo "✅ OPA policy bundle signed and verified against the pinned identity" - # Framework-coverage figures are not stamped into committed HTML: the trust + # The Rev5 Moderate figures are not stamped into committed HTML: the trust # center renders them from trust-center.json, which build-trust-center.py - # computes on every deploy from the control projection (scripts/_controls.py, - # via inject-figures.compute_figures), so there is nothing committed to drift. + # computes on every deploy from the control projection (scripts/_controls.py), + # so there is nothing committed to drift. # The OSCAL SSP that used to be built here is retired (CR26): the SDR carries # the per-control record (rev5_controls) and the CPO the package overview. @@ -1414,20 +1549,62 @@ jobs: # fetched and checked by the detection gate (G7) before apply. # The signed runtime signal is the only live read a mitigation can cite # (rule 1: a mitigation verified by a live read makes a finding fully - # mitigated). The builder verifies its signature against - # infrastructure/keys/runtime-signing-key.json and its age; anything short - # of verified and fresh voids every mitigation that needs a live read, so a - # failed fetch can only keep findings open, never close them. - - name: Fetch the signed runtime signal (live read for mitigations) + # mitigated), and the second automated method the SDR counts per KSI + # (FRC-CSX-VVK). It must re-validate THIS deploy's system against THIS + # deploy's inventory: the emitter is invoked synchronously, after apply, + # with the signed inventory staged under deploy-staging// (redaction + # gate first: the staged copy is in the website bucket). The emitter writes + # its signed signal next to it; the deploy reads it back, deletes the + # staging objects, and the VDR and SDR builders verify its signature + # (infrastructure/keys/runtime-signing-key.json), its age, and (the SDR) + # that it re-validated this commit. Any failure fails the deploy: the SDR + # step requires two automated methods per KSI. The deploy role's + # lambda:InvokeFunction and S3 object writes are existing grants (the + # post-publish compliance check and the site sync use them). + - name: Re-validate the deployed system against this inventory (runtime emitter, FRC-CSX-VVK) working-directory: infrastructure + env: + COMMIT: ${{ github.sha }} run: | - if curl -sfL --retry 3 --retry-delay 2 -o ksi-signal-runtime.json \ - "https://samaydlette.com/.well-known/ksi-signal-runtime.json"; then - echo "Runtime signal fetched: emitted $(jq -r '.emitted_at' ksi-signal-runtime.json 2>/dev/null || echo 'unreadable; the builder will reject it')" - else - echo "::warning::Could not fetch the runtime signal; mitigations that need a live read are void this run." - rm -f ksi-signal-runtime.json + set -euo pipefail + python3 ../scripts/check-published-redaction.py ksi-signal.json + BUCKET=$(terraform output -raw s3_bucket_name) + FN=$(terraform output -raw lambda_function_name) + STAGE="deploy-staging/${COMMIT}" + cleanup() { aws s3 rm "s3://${BUCKET}/${STAGE}/" --recursive --only-show-errors || true; } + trap cleanup EXIT + aws s3 cp ksi-signal.json "s3://${BUCKET}/${STAGE}/ksi-signal.json" \ + --content-type application/json --cache-control no-store --only-show-errors + if ! aws lambda invoke --function-name "$FN" --cli-binary-format raw-in-base64-out --cli-read-timeout 300 \ + --payload "{\"stage\":\"${COMMIT}\"}" runtime-invoke.json > runtime-invoke-meta.json; then + echo "::error::Could not invoke the runtime emitter. The deploy role needs lambda:InvokeFunction on the emitter (bootstrap)." + exit 1 fi + if jq -e '.FunctionError' runtime-invoke-meta.json >/dev/null \ + || [ "$(jq -r '.statusCode' runtime-invoke.json)" != "200" ]; then + echo "::error::The runtime emitter's staged run failed: $(jq -c '.body // .errorMessage' runtime-invoke.json)" + exit 1 + fi + aws s3 cp "s3://${BUCKET}/${STAGE}/ksi-signal-runtime.json" ksi-signal-runtime.json --only-show-errors + GOT=$(jq -r '.provenance.source.commit // ""' ksi-signal-runtime.json) + if [ "$GOT" != "$COMMIT" ]; then + echo "::error::The staged runtime signal re-validated commit ${GOT:-none}, not ${COMMIT}" + exit 1 + fi + echo "Runtime signal for ${COMMIT}: $(jq -c '.validations | group_by(.result) | map({(.[0].result): length}) | add' ksi-signal-runtime.json)" + + # VDR-CSO-FAV: runs of the pipeline that a block-mode check stopped. The + # next report lists each one (no run IDs or URLs are kept). A failed query + # fails the step: no list cannot read as "no failures". + - name: Collect failed pipeline runs (VDR-CSO-FAV) + working-directory: infrastructure + env: + GH_TOKEN: ${{ github.token }} + run: | + set -euo pipefail + gh run list --repo "${{ github.repository }}" --branch main --status failure --limit 100 \ + --json workflowName,createdAt,updatedAt,event,headBranch > failed-runs.json + jq length failed-runs.json - name: Build VDR Report (FedRAMP 20x Class C) working-directory: infrastructure @@ -1442,11 +1619,15 @@ jobs: --dependabot dependabot-alerts.json \ --grype grype.json \ --zap zap-report.json \ + --zap-max-age-days 3 \ + --zap-api zap-api-report.json \ + --codeql codeql-alerts.json \ --kev kev-catalog.json \ --epss epss-scores.csv.gz \ --detection detection.json \ --conformance conformance-results.json \ --runtime-signal ksi-signal-runtime.json \ + --failed-runs failed-runs.json \ --output vdr-report.json echo "VDR summary:" jq '{summary, rules_reference, risk_accepted_count: (.risk_accepted | length)}' vdr-report.json @@ -1532,6 +1713,71 @@ jobs: cosign sign-blob --yes --new-bundle-format --bundle "$a.bundle" "$a.json" done + # Incident reports (IEC-CSO-IIR/OIR/FIR) and the incident log, from the + # incident register and this build's VDR (VER-TFR-IRI/NRI triggers). The + # same builder runs unattended in incident-reports.yml on every change to + # the register; the deploy republishes them so a deploy never serves a log + # older than the register it was built from. Each report is validated + # against FedRAMP's schema before it is written. No clock check here: an + # overdue report must not block the deploy that may be the fix; the + # incident-reports workflow and the evidence watchdog alarm on it. + - name: Build incident reports (IIR, OIR, FIR) + working-directory: infrastructure + run: | + set -euo pipefail + python3 ../scripts/build-incident-report.py --incidents ../data/incidents.json --vdr vdr-report.json --out-dir . + # SIMULATED delivery (IEC-CSO-IIR/OIR/FIR/AIR): every listed report is + # read back, hash- and schema-checked and "delivered" to a simulated + # FedRAMP and agency recipient; nothing is sent. A failed delivery + # stops the deploy here, before the SDR is built or anything published. + python3 ../scripts/deliver-incident-reports.py --dir . + for f in incident-*.json; do + cosign sign-blob --yes --new-bundle-format --bundle "${f%.json}.bundle" "$f" + done + # VDR-TFR-NMV: every non-machine resource (policies, procedures, plans, the + # operator role, records, registers) passes its machine checks + # (scripts/_nonmachine.py: paths and DEC IDs resolve, no retired mechanism, + # tagged counts match the code). The deploy stops otherwise, before anything + # is published; the status is published with the VDR. + - name: Non-machine verification and validation (VDR-TFR-NMV) + working-directory: infrastructure + run: | + set -euo pipefail + python3 ../scripts/check-non-machine-vv.py --enforce --out vdr-non-machine-vv.json + cosign sign-blob --yes --new-bundle-format --bundle vdr-non-machine-vv.bundle vdr-non-machine-vv.json + + # VER-TFR-MHR, VER-RPT-HLO, VER-RPT-PER: the month-to-date activity report, + # in human-readable form, listing every kind of detection and response + # activity ("none this period" when nothing happened). The previous published + # report carries the month's earlier runs forward, read only if its signature + # verifies against this workflow or the other publisher. + - name: Build monthly VDR activity report (VER-TFR-MHR) + working-directory: infrastructure + env: + SITE: https://${{ vars.DOMAIN_NAME || 'samaydlette.com' }}/.well-known + run: | + set -euo pipefail + prev=() + if curl -sfL --retry 3 --retry-delay 5 -o previous-vdr-monthly.json "$SITE/vdr-monthly.json"; then + curl -sfL --retry 3 --retry-delay 5 -o previous-vdr-monthly.bundle "$SITE/vdr-monthly.bundle" + ok=0 + for identity in \ + "https://github.com/${{ github.repository }}/.github/workflows/deploy-with-opa.yml@refs/heads/main" \ + "https://github.com/${{ github.repository }}/.github/workflows/evidence-nightly.yml@refs/heads/main"; do + if cosign verify-blob --bundle previous-vdr-monthly.bundle --certificate-identity "$identity" \ + --certificate-oidc-issuer https://token.actions.githubusercontent.com previous-vdr-monthly.json 2>/dev/null; then ok=1; break; fi + done + [ "$ok" -eq 1 ] || { echo "::error::previous vdr-monthly.json does not verify; refusing to carry it forward"; exit 1; } + prev=(--previous previous-vdr-monthly.json) + else + echo "No previous vdr-monthly.json published; the month starts with this build's runs." + fi + python3 ../scripts/build-vdr-monthly.py --vdr vdr-report.json --history vdr-history.json \ + --decisions ../data/decisions.json --activities ../data/vdr-activities.json \ + --non-machine vdr-non-machine-vv.json "${prev[@]}" \ + --incidents ../data/incidents.json --assessment simulated-assessment.json + cosign sign-blob --yes --new-bundle-format --bundle vdr-monthly.bundle vdr-monthly.json + # ------------------------------------------------------------------------- # PROJECT THE CANONICAL INVENTORY INTO FEDRAMP IIW (APPENDIX M) SHAPE # ------------------------------------------------------------------------- @@ -1558,49 +1804,282 @@ jobs: - name: Build Ongoing Certification Report (CCM) working-directory: infrastructure run: | - echo "Building Ongoing Certification Report (CCM-OCR-AVL: quarterly human-readable summary)..." + echo "Building Ongoing Certification Report (CCM-OCR-AVL, FedRAMP's OCR schema, fixed CCM calendar)..." + # Append-only (version, KSI metric and training history): a 404 starts + # it; any other failure stops the deploy instead of resetting it. + python3 ../scripts/fetch-published-history.py ongoing-certification-report.json previous-ocr.json python3 ../scripts/build-ocr.py \ --vdr vdr-report.json \ --decisions ../data/decisions.json \ --ksi-signal ksi-signal.json \ --scn-register ../docs/scn/scn-register.csv \ + --previous previous-ocr.json \ --output ongoing-certification-report.json \ --md-output ongoing-certification-report.md - jq '{next_ongoing_certification_report_date, next_quarterly_review_date}' ongoing-certification-report.json + jq '.providerExtensions.continuousMonitoring | {nextOngoingCertificationReportDate, nextQuarterlyReviewDate}' ongoing-certification-report.json + + # W8 edge checks (FRC-CSO-JSN, CDS-CSO-AVR, CDS-TRC-USH, CDS-TRC-ACL). Each + # depends on something outside this deploy (the operator-applied bootstrap + # stack, or the independent monitor on GitHub Actions) and fails the deploy + # when it is missing, before the SDR says the rule is met. + - name: Check /.well-known/ JSON response headers (CORS, Content-Type, nosniff) + env: + DOMAIN: ${{ vars.DOMAIN_NAME || 'samaydlette.com' }} + run: python3 scripts/check-wellknown-headers.py --site "https://$DOMAIN" - - name: Build CDS certification-data artifacts (overview, availability, policy index) + - name: Read the independent availability feed (fails when missing or stale) + working-directory: infrastructure + env: + REPO: ${{ github.repository }} + run: | + set -euo pipefail + curl -fsS --max-time 30 -o availability-probe.json \ + "https://raw.githubusercontent.com/$REPO/availability-status/availability-status.json" + python3 ../scripts/availability-probe.py --check-fresh availability-probe.json --max-age-hours 2 + + # The CloudFront access records carry no IP, cookie, query string or user + # agent (the delivery's field allowlist, checked here); only /.well-known/ + # and /trust/ requests are counted, and only monthly aggregates published. + - name: Check edge access logging and build the access summary working-directory: infrastructure + env: + DOMAIN: ${{ vars.DOMAIN_NAME || 'samaydlette.com' }} run: | - echo "Building CDS certification-overview package, availability feed, policy index..." - # availability history: fetch the previously-published feed (best-effort) - curl -sfL -o previous-availability.json "https://samaydlette.com/.well-known/availability.json" \ - || echo '{"history":[]}' > previous-availability.json - python3 ../scripts/build-cds-overview.py \ - --offering ../data/cds/offering.json --profile ../data/system-profile.json --ksi-signal ksi-signal.json + set -euo pipefail + umask 077 + trap 'rm -rf edge-access-records edge-deliveries.json edge-delivery-source.json' EXIT + name="${DOMAIN//./-}-edge-access" + aws logs describe-deliveries --region us-east-1 --output json > edge-deliveries.json + aws logs get-delivery-source --name "$name" --region us-east-1 --output json > edge-delivery-source.json || true + python3 ../scripts/check-edge-access-logging.py \ + --deliveries edge-deliveries.json --source edge-delivery-source.json --name "$name" + bucket="${DOMAIN//./-}-logs" + account=$(aws sts get-caller-identity --query Account --output text) + aws s3 sync "s3://$bucket/cloudfront/" edge-access-records/cloudfront/ --only-show-errors + aws s3 sync "s3://$bucket/AWSLogs/$account/CloudFront/" edge-access-records/default/ --only-show-errors + # Append-only: a 404 starts the history; any other failure stops the deploy. + python3 ../scripts/fetch-published-history.py access-summary.json previous-access-summary.json \ + --site "https://$DOMAIN" + python3 ../scripts/build-access-summary.py \ + --records edge-access-records --previous previous-access-summary.json + + - name: Build CDS certification-data artifacts (availability, policy index, review calendar) + working-directory: infrastructure + run: | + echo "Building availability feed, policy index, Quarterly Review calendar..." + # CCM-QTR-REG: the review calendar file, from the fixed CCM calendar. + python3 ../scripts/_ccm.py --ics quarterly-review.ics + # Availability as measured by the independent monitor (read and checked above). python3 ../scripts/build-availability.py \ - --previous previous-availability.json --ksi-signal ksi-signal.json - python3 ../scripts/build-policy-index.py --output policy-index.json --md-output policy-index.md + --probe-feed availability-probe.json --ksi-signal ksi-signal.json + python3 ../scripts/build-policy-index.py --output policy-index.json --md-output policy-index.md --publish-dir policies + + # The Minimum Assessment Scope (MAS-CSO-IIR/FLO/MDI/TPR, FRC-CSX-MAS), generated + # from this build's inventory, the boundary classification's flows, the CSPs + # the edge serves and the third-party records. Fails the deploy, before the + # SDR, on an unplaced off-origin host, an external service or data store in + # no flow, a data store without a metadata entry, an undecided third-party + # record, or a component type no KSI covers. Signed and published with the + # rest after the gates. + # IVV-CSO-STE / IVV-CSO-DUS: the assessor guide, generated from the rule + # records (the simulated assessor received and ran the same guide before this + # job started). Signed and published with the rest. + - name: Build the assessor guide + working-directory: infrastructure + env: + GITHUB_SHA: ${{ github.sha }} + run: python3 ../scripts/build-assessor-guide.py --commit "$GITHUB_SHA" --output assessor-guide.json --md-output assessor-guide.md + + # CDS-TRC-AAI / CDS-TRC-SSM / CDS-UTC-AAD / CDS-UTC-AGA: the real register + # fails the deploy on a denial not notified to FedRAMP within 5 business + # days; the exercise runs the same code over fictional agencies dated from + # today and fails unless every expected outcome (late and overdue notices + # included) is observed. Nothing is sent to anyone. + - name: Agency access register check and simulated-agency exercise + working-directory: infrastructure + run: | + set -euo pipefail + python3 ../scripts/agency-access.py validate + python3 ../scripts/agency-access.py exercise --output agency-access-exercise.json --md-output agency-access-exercise.md + + - name: Build the Minimum Assessment Scope + working-directory: infrastructure + env: + GITHUB_SHA: ${{ github.sha }} + run: | + python3 ../scripts/build-mas.py --ksi-signal ksi-signal.json --commit "$GITHUB_SHA" \ + --output minimum-assessment-scope.json --md-output minimum-assessment-scope.md + cosign sign-blob --yes --new-bundle-format --bundle minimum-assessment-scope.bundle minimum-assessment-scope.json + + # The Secure Configuration Guide and the per-service cryptographic module + # list (SCG-CSO-RSC/PUB/AUP, SCG-ENH-MRG/API/VRH; CMU-CSO-CMD/UVM/CAT), from + # data/secure-configuration.json and data/crypto-modules.json joined with this + # deploy's inventory. Fails on an unreleased change to a default, a decision + # that is not in force, an inventoried component type with no module mapping, + # or a retired mechanism in the guide. + - name: Build the secure configuration guide (SCG, cryptographic modules) + working-directory: infrastructure + run: | + set -euo pipefail + python3 ../scripts/build-scg.py --ksi-signal ksi-signal.json \ + --output secure-configuration-guide.json --md-output secure-configuration-guide.md + cosign sign-blob --yes --new-bundle-format --bundle secure-configuration-guide.bundle secure-configuration-guide.json + + # SCG-ENH-CMP / SCG-ENH-EXP: read the live settings of the top-level and + # privileged accounts (read-only; the deploy role's secure-configuration-reads + # policy in infrastructure/bootstrap) and compare each with the guide. A + # deviation no in-force decision covers, or a setting that cannot be read, + # fails the deploy here, before the SDR is built and before anything is + # published. The export carries values only: no account ID, ARN or IAM name. + - name: Compare live security settings with the secure configuration guide + working-directory: infrastructure + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + DEPENDABOT_TOKEN: ${{ secrets.DEPENDABOT_ALERTS_TOKEN }} + run: | + set -euo pipefail + pool=$(terraform output -raw cognito_user_pool_id) + python3 ../scripts/check-secure-config.py --cognito-pool-id "$pool" \ + --output security-settings.json --md-output security-settings.md + cosign sign-blob --yes --new-bundle-format --bundle security-settings.bundle security-settings.json + + # The IEC records claim an unattended publisher that assumes its own role. + # Prove the role can be assumed, from this job, before the SDR is built: + # if it cannot, the deploy stops here and nothing claiming it is published. + # The incident-publisher job after the deploy then runs the publisher itself. + - name: Incident report publisher role can be assumed + env: + INCIDENT_REPORTS_ROLE_ARN: ${{ vars.AWS_INCIDENT_REPORTS_ROLE_ARN }} + run: python3 scripts/check-incident-role.py + + # SIMULATION. The FedRAMP Security Inbox is simulated for this proof of + # concept (operator's decision): nothing real is received or sent. This + # runs the inbox logic (scripts/_fsi.py) over committed synthetic messages + # and fails the deploy if any outcome differs from the expected one + # (AFC-CSO-INB/TFG/RCV/CRA/EMR/IMA/ACK, simulated). + - name: FedRAMP Security Inbox simulation (synthetic messages; nothing received or sent) + working-directory: infrastructure + run: | + python3 ../scripts/build-fsi-simulation.py \ + --messages ../data/fsi-simulation/messages.json \ + --offering ../data/cds/offering.json \ + --output fedramp-inbox-simulation.json + + # Significant Change Notifications (SCN-CSO-HIS/HRM/NOM/INF) and the + # append-only evaluation log (SCN-CSO-MAR). The builder fails if this build + # would drop or rewrite anything the previous published copies hold, so they + # are fetched first: a 404 means nothing has been published yet, any other + # failure stops the deploy rather than restarting the record. + - name: Build Significant Change Notifications and the evaluation log + working-directory: infrastructure + env: + GH_TOKEN: ${{ github.token }} + run: | + fetch() { + code=$(curl -sSL -o "$2" -w '%{http_code}' "https://samaydlette.com/.well-known/$1") \ + || { echo "::error::cannot fetch the published $1"; exit 1; } + case "$code" in + 200) ;; + 404) rm -f "$2"; echo "$1 not published yet" ;; + *) echo "::error::fetching the published $1 returned HTTP $code"; exit 1 ;; + esac + } + fetch significant-change-notifications.json previous-scn-index.json + fetch scn-evaluations.json previous-scn-evaluations.json + python3 ../scripts/build-scn.py --previous-index previous-scn-index.json \ + --previous-log previous-scn-evaluations.json --commit "$GITHUB_SHA" - name: Build Security Decision Record (SDR — 20x SSP replacement) working-directory: infrastructure + env: + VDR_SIGNER: https://github.com/${{ github.workflow_ref }} + COMMIT: ${{ github.sha }} run: | - echo "Building Security Decision Record (SDR-CSO-FRR per KSI, SDR-CSF-CTF per Rev5 control) from the control projection..." - curl -sfL -o previous-sdr.json "https://samaydlette.com/.well-known/security-decision-record.json" \ - || echo '{}' > previous-sdr.json + echo "Building the Security Decision Record (FedRAMP schema): every applicable rule, KSI and Moderate control..." + # Append-only (version, KSI metric and training history): a 404 starts + # it; any other failure stops the deploy instead of resetting it. + python3 ../scripts/fetch-published-history.py security-decision-record.json previous-sdr.json + # The scheduled reviews' published records (scripts/_scheduled_review.py): + # each counts as a method for its KSIs only when build-sdr.py verifies its + # signature against its publisher and finds it current and passing. One + # not published yet is not counted; it never stands in for another method. + mkdir -p scheduled + SCHED="" + for k in audit-log-review:vdr-audit-log-review recovery-exercise:vdr-recovery-exercises \ + security-review:security-reviews; do + f="${k#*:}" + if curl -sfL -o "scheduled/$f.json" "https://samaydlette.com/.well-known/$f.json" \ + && curl -sfL -o "scheduled/$f.bundle" "https://samaydlette.com/.well-known/$f.bundle"; then + SCHED="$SCHED --scheduled-record ${k%%:*}=scheduled/$f.json" + else + echo "$f is not published yet; its method is not counted"; rm -f "scheduled/$f.json" "scheduled/$f.bundle" + fi + done + # shellcheck disable=SC2086 # $SCHED is a word list by design python3 ../scripts/build-sdr.py \ --catalog schemas/ksi-catalog.json --ksi-signal ksi-signal.json \ - --vdr vdr-report.json --profile ../data/system-profile.json --previous-sdr previous-sdr.json + --runtime-signal ksi-signal-runtime.json \ + --vdr vdr-report.json --profile ../data/system-profile.json --previous-sdr previous-sdr.json \ + --assessment simulated-assessment.json --assessment-bundle simulated-assessment.bundle \ + --assessment-commit "$COMMIT" --assessment-signal-id "$ASSESSED_SIGNAL_ID" \ + --vdr-bundle vdr-report.bundle --vdr-identity "$VDR_SIGNER" \ + --runtime-commit "$COMMIT" --require-two-methods $SCHED + # FRC-CSX-VVK: a KSI short of two automated methods without an in-force + # accepted decision fails the deploy here, before + # anything is published. The runtime method counts only for the signal + # the staged emitter run produced for this commit. # REQ-ASR-1 / T74: re-read the written SDR and fail if any assessor text # differs from the assessor's signed record, or a signed record is missing. - python3 ../scripts/_assessor.py --sdr security-decision-record.json + python3 ../scripts/_assessor.py --sdr security-decision-record.json \ + --assessment simulated-assessment.json --assessment-bundle simulated-assessment.bundle \ + --assessment-commit "$COMMIT" --assessment-signal-id "$ASSESSED_SIGNAL_ID" - name: Build Certification Package Overview (CPO) working-directory: infrastructure run: | - echo "Building Certification Package Overview (CPO-CSO-OVR); with the SDR, the SSP replacement..." + echo "Building Certification Package Overview (CPO-CSO-OVR, FedRAMP's CPO schema); with the SDR, the SSP replacement..." + # Append-only (version, KSI metric and training history): a 404 starts + # it; any other failure stops the deploy instead of resetting it. + python3 ../scripts/fetch-published-history.py certification-package-overview.json previous-cpo.json python3 ../scripts/build-cpo.py \ --offering ../data/cds/offering.json --profile ../data/system-profile.json \ - --overview certification-overview-package.json --ksi-signal ksi-signal.json + --ksi-signal ksi-signal.json --previous-cpo previous-cpo.json \ + --assessment simulated-assessment.json --assessment-bundle simulated-assessment.bundle \ + --assessment-commit "$GITHUB_SHA" --assessment-signal-id "$ASSESSED_SIGNAL_ID" + + # FRC-CSO-PKG: the package (CPO, SDR, OCR) is checked against its schemas + # and the applicable rules, and "submitted" to a simulated FedRAMP intake: a + # function in scripts/submit-package.py. NOTHING IS SENT; the submission is + # an entry in the signed, published log. Any unexpected outcome fails here. + # The same log records the simulated FedRAMP's certification report when one + # is due (CDS-CSO-FRC) and files a notice of every FedRAMP Security Inbox + # contact change, failing unless it is filed within one business day of the deploy that + # first published the change (AFC-CSO-NOC, scripts/check-fsi-notice.py). + - name: Simulated package submission to FedRAMP (nothing is sent) + working-directory: infrastructure + run: | + # Append-only: a 404 starts the log; any other failure stops the deploy. + python3 ../scripts/fetch-published-history.py package-submission-log.json previous-package-submission-log.json + python3 ../scripts/submit-package.py --previous previous-package-submission-log.json \ + --output package-submission-log.json --commit "$GITHUB_SHA" + + # CDS-CSO-FRC: FedRAMP is SIMULATED. The simulated FedRAMP issues a stand-in + # certification report only in response to a simulated submission (the step + # above): the first, after any adaptive or transformative SCN, and once a + # year; the submission log holds it verbatim with the date received. Every + # logged report is published unmodified (its sha256 is checked against the + # log) and the deploy fails if one is first published more than 2 weeks + # after receipt. Each says it is NOT ISSUED BY FEDRAMP and the system is not + # certified. Nothing is received from or sent to FedRAMP. + - name: FedRAMP Certification Reports published unmodified (simulated FedRAMP) + working-directory: infrastructure + run: | + # Append-only (first-publication dates): a 404 starts the index; any + # other failure stops the deploy. + python3 ../scripts/fetch-published-history.py fedramp-certification-reports.json \ + previous-fedramp-certification-reports.json + python3 ../scripts/publish-certification-reports.py --submission-log package-submission-log.json \ + --previous previous-fedramp-certification-reports.json --out . # The authorization-boundary map the trust center draws: the inventory's # components placed by docs/boundary/boundary-classification.json, connected @@ -1684,16 +2163,62 @@ jobs: run: | echo "Signing ongoing-certification-report.json with cosign keyless..." cosign sign-blob --yes --new-bundle-format --bundle ongoing-certification-report.bundle ongoing-certification-report.json + echo "Signing fedramp-inbox-simulation.json (SIMULATION) with cosign keyless..." + cosign sign-blob --yes --new-bundle-format --bundle fedramp-inbox-simulation.bundle fedramp-inbox-simulation.json - name: Sign CDS certification-data artifacts working-directory: infrastructure run: | echo "Signing CDS artifacts with cosign keyless..." - cosign sign-blob --yes --new-bundle-format --bundle certification-overview-package.bundle certification-overview-package.json cosign sign-blob --yes --new-bundle-format --bundle availability.bundle availability.json cosign sign-blob --yes --new-bundle-format --bundle policy-index.bundle policy-index.json cosign sign-blob --yes --new-bundle-format --bundle security-decision-record.bundle security-decision-record.json cosign sign-blob --yes --new-bundle-format --bundle certification-package-overview.bundle certification-package-overview.json + cosign sign-blob --yes --new-bundle-format --bundle fedramp-certification-reports.bundle fedramp-certification-reports.json + cosign sign-blob --yes --new-bundle-format --bundle package-submission-log.bundle package-submission-log.json + cosign sign-blob --yes --new-bundle-format --bundle access-summary.bundle access-summary.json + for a in significant-change-notifications scn-evaluations; do + cosign sign-blob --yes --new-bundle-format --bundle "$a.bundle" "$a.json" + done + cosign sign-blob --yes --new-bundle-format --bundle significant-change-notifications.atom.bundle significant-change-notifications.atom + + # CDS-TRC-HMR / CDS-CSO-CBF / CDS-TRC-PAC: a complete human-readable view + # of every JSON and CSV artifact this deploy publishes, each parsed back and + # required to reproduce its original exactly (the build fails otherwise), + # then the signed manifest of all certification data. published-docs.txt + # lists the views and the policy documents; the redaction gate scans and + # the publish step uploads exactly that list. + - name: Build the human-readable views and the trust manifest (format parity) + working-directory: infrastructure + env: + GITHUB_SHA: ${{ github.sha }} + run: | + set -euo pipefail + : > published-docs.txt + ls policies/*.md >> published-docs.txt + python3 ../scripts/build-human-views.py --freshness schemas/freshness-config.json --dir . --list published-docs.txt + # Every other JSON the publish steps put has its view too: each incident + # report, the inventory's JSON Schema (published beside the signal, so + # its view is built from a copy here), and each certification report + # (its view sits beside it in fedramp-certification-reports/ and is put + # by the step that publishes the reports). + cp schemas/ksi-signal.schema.json ksi-signal.schema.json + shopt -s nullglob + python3 ../scripts/build-human-views.py ksi-signal.schema.json incident-INC-*.json --list published-docs.txt + reports=(fedramp-certification-reports/*.json) + if [ "${#reports[@]}" -gt 0 ]; then python3 ../scripts/build-human-views.py "${reports[@]}"; fi + shopt -u nullglob + python3 ../scripts/build-trust-manifest.py --dir . --policy-index policy-index.json --commit "$GITHUB_SHA" \ + --output trust-manifest.json --md-output trust-manifest.md + python3 ../scripts/build-human-views.py trust-manifest.json --list published-docs.txt + + # CDS-CSO-FID: every FedRAMP report this deploy publishes carries the + # offering's FedRAMP ID (scripts/check-fedramp-id.py REPORTS lists them). + # Runs once every listed file is built (the trust center and manifest are + # the last), and before anything is published. + - name: FedRAMP ID in every FedRAMP report (CDS-CSO-FID) + working-directory: infrastructure + run: python3 ../scripts/check-fedramp-id.py - name: Sign trust-center artifacts (boundary map, gate report, trust center) working-directory: infrastructure @@ -1705,6 +2230,11 @@ jobs: if [ -f boundary-corroboration.json ]; then cosign sign-blob --yes --new-bundle-format --bundle boundary-corroboration.bundle boundary-corroboration.json fi + # The simulated assessment arrives signed by the assessor's own identity + # and is published with that bundle, never re-signed here. + for a in assessor-guide agency-access-exercise frr-evidence trust-manifest; do + cosign sign-blob --yes --new-bundle-format --bundle "$a.bundle" "$a.json" + done # Publication redaction gate: no artifact this run is about to publish # carries an AWS account ID. The inventory builder redacts it @@ -1720,12 +2250,24 @@ jobs: files="ksi-signal.json schemas/ksi-signal.schema.json vdr-report.json vdr-report.md vdr-trend.json iiw.csv" for a in vdr-detail-report vdr-accepted-vulnerabilities vdr-history; do files="$files $a.json"; done for a in vdr-detail-report vdr-accepted-vulnerabilities; do files="$files $a.md"; done - files="$files ongoing-certification-report.json ongoing-certification-report.md" - for a in certification-overview-package availability policy-index security-decision-record certification-package-overview; do files="$files $a.json $a.md"; done + files="$files vdr-non-machine-vv.json vdr-monthly.json vdr-monthly.md" + files="$files ongoing-certification-report.json ongoing-certification-report.md fedramp-inbox-simulation.json" + for a in availability policy-index security-decision-record certification-package-overview secure-configuration-guide security-settings; do files="$files $a.json $a.md"; done + for a in access-summary; do files="$files $a.json $a.md"; done + for a in significant-change-notifications scn-evaluations; do files="$files $a.json $a.md"; done + files="$files significant-change-notifications.atom" + for a in assessor-guide agency-access-exercise trust-manifest; do files="$files $a.json $a.md"; done + files="$files frr-evidence.json simulated-assessment.json" + # The human-readable views and the policy documents (the list the publish step uploads). + if [ -f published-docs.txt ]; then files="$files $(cat published-docs.txt)"; fi + files="$files fedramp-certification-reports.json package-submission-log.json quarterly-review.ics" for a in boundary-map reconcile-report trust-center conformance-results boundary-corroboration; do [ -f "$a.json" ] || continue files="$files $a.json" done + files="$files minimum-assessment-scope.json minimum-assessment-scope.md" + # Incident log and reports (built every deploy, so the glob always matches). + for f in incident-*.json incident-*.md; do files="$files $f"; done # shellcheck disable=SC2086 # a word list by design python3 ../scripts/check-published-redaction.py $files @@ -1759,6 +2301,13 @@ jobs: for a in vdr-detail-report vdr-accepted-vulnerabilities; do aws s3 cp "$a.md" "s3://$BUCKET_NAME/.well-known/$a.md" --content-type "text/markdown; charset=utf-8" --cache-control "public, max-age=300" done + # Non-machine V&V status (VDR-TFR-NMV) + bundle. + aws s3 cp vdr-non-machine-vv.json "s3://$BUCKET_NAME/.well-known/vdr-non-machine-vv.json" --content-type application/json --cache-control "public, max-age=300" + aws s3 cp vdr-non-machine-vv.bundle "s3://$BUCKET_NAME/.well-known/vdr-non-machine-vv.bundle" --content-type application/json --cache-control "public, max-age=300" + # Monthly activity report (VER-TFR-MHR) + bundle + human-readable rendering. + aws s3 cp vdr-monthly.json "s3://$BUCKET_NAME/.well-known/vdr-monthly.json" --content-type application/json --cache-control "public, max-age=300" + aws s3 cp vdr-monthly.bundle "s3://$BUCKET_NAME/.well-known/vdr-monthly.bundle" --content-type application/json --cache-control "public, max-age=300" + aws s3 cp vdr-monthly.md "s3://$BUCKET_NAME/.well-known/vdr-monthly.md" --content-type "text/markdown; charset=utf-8" --cache-control "public, max-age=300" # IIW aws s3 cp iiw.csv "s3://$BUCKET_NAME/.well-known/iiw.csv" --content-type text/csv --cache-control "public, max-age=300" aws s3 cp iiw.bundle "s3://$BUCKET_NAME/.well-known/iiw.bundle" --content-type application/json --cache-control "public, max-age=300" @@ -1768,19 +2317,38 @@ jobs: # SDR (per-KSI and per-Rev5-control records) and CPO on 2026-11-05. Their # published copies are deleted rather than left to go stale unwatched; # the round-trip step below asserts they are gone. - for retired in oscal-poam.json oscal-poam.bundle oscal-poam.json.intoto.jsonl oscal-ssp.json oscal-ssp.bundle oscal-ssp.json.intoto.jsonl; do + # The CDS certification-overview package folded into the CPO on 2026-11-05. + for retired in oscal-poam.json oscal-poam.bundle oscal-poam.json.intoto.jsonl oscal-ssp.json oscal-ssp.bundle oscal-ssp.json.intoto.jsonl certification-overview-package.json certification-overview-package.bundle certification-overview-package.md; do aws s3 rm "s3://$BUCKET_NAME/.well-known/$retired" done # Ongoing Certification Report (CCM-OCR-AVL) + human-readable rendering aws s3 cp ongoing-certification-report.json "s3://$BUCKET_NAME/.well-known/ongoing-certification-report.json" --content-type application/json --cache-control "public, max-age=300" aws s3 cp ongoing-certification-report.bundle "s3://$BUCKET_NAME/.well-known/ongoing-certification-report.bundle" --content-type application/json --cache-control "public, max-age=300" aws s3 cp ongoing-certification-report.md "s3://$BUCKET_NAME/.well-known/ongoing-certification-report.md" --content-type "text/markdown; charset=utf-8" --cache-control "public, max-age=300" + aws s3 cp fedramp-inbox-simulation.json "s3://$BUCKET_NAME/.well-known/fedramp-inbox-simulation.json" --content-type application/json --cache-control "public, max-age=300" + aws s3 cp fedramp-inbox-simulation.bundle "s3://$BUCKET_NAME/.well-known/fedramp-inbox-simulation.bundle" --content-type application/json --cache-control "public, max-age=300" # CDS certification-data artifacts (overview package, availability feed, policy index) + bundles + human-readable - for a in certification-overview-package availability policy-index security-decision-record certification-package-overview; do + for a in availability policy-index security-decision-record certification-package-overview secure-configuration-guide security-settings; do + aws s3 cp "$a.json" "s3://$BUCKET_NAME/.well-known/$a.json" --content-type application/json --cache-control "public, max-age=300" + aws s3 cp "$a.bundle" "s3://$BUCKET_NAME/.well-known/$a.bundle" --content-type application/json --cache-control "public, max-age=300" + aws s3 cp "$a.md" "s3://$BUCKET_NAME/.well-known/$a.md" --content-type "text/markdown; charset=utf-8" --cache-control "public, max-age=300" + done + # Trust-center access summary (CDS-TRC-ACL): aggregate counts only; and the + # Significant Change Notifications + evaluation log (SCN-*) + bundles + human-readable. + for a in access-summary significant-change-notifications scn-evaluations; do aws s3 cp "$a.json" "s3://$BUCKET_NAME/.well-known/$a.json" --content-type application/json --cache-control "public, max-age=300" aws s3 cp "$a.bundle" "s3://$BUCKET_NAME/.well-known/$a.bundle" --content-type application/json --cache-control "public, max-age=300" aws s3 cp "$a.md" "s3://$BUCKET_NAME/.well-known/$a.md" --content-type "text/markdown; charset=utf-8" --cache-control "public, max-age=300" done + # CDS-CSO-FRC index and the simulated FRC-CSO-PKG submission log (signed), and + # the Quarterly Review calendar file (CCM-QTR-REG). + for a in fedramp-certification-reports package-submission-log; do + aws s3 cp "$a.json" "s3://$BUCKET_NAME/.well-known/$a.json" --content-type application/json --cache-control "public, max-age=300" + aws s3 cp "$a.bundle" "s3://$BUCKET_NAME/.well-known/$a.bundle" --content-type application/json --cache-control "public, max-age=300" + done + aws s3 cp quarterly-review.ics "s3://$BUCKET_NAME/.well-known/quarterly-review.ics" --content-type "text/calendar; charset=utf-8" --cache-control "public, max-age=300" + aws s3 cp significant-change-notifications.atom "s3://$BUCKET_NAME/.well-known/significant-change-notifications.atom" --content-type "application/atom+xml; charset=utf-8" --cache-control "public, max-age=300" + aws s3 cp significant-change-notifications.atom.bundle "s3://$BUCKET_NAME/.well-known/significant-change-notifications.atom.bundle" --content-type application/json --cache-control "public, max-age=300" # Trust center: the generated boundary map, the gate's own report (it exists # only because the gate above passed) and the trust center's data. for a in boundary-map reconcile-report trust-center conformance-results boundary-corroboration; do @@ -1788,8 +2356,63 @@ jobs: aws s3 cp "$a.json" "s3://$BUCKET_NAME/.well-known/$a.json" --content-type application/json --cache-control "public, max-age=300" aws s3 cp "$a.bundle" "s3://$BUCKET_NAME/.well-known/$a.bundle" --content-type application/json --cache-control "public, max-age=300" done + # Minimum Assessment Scope (MAS-CSO-IIR/FLO/MDI/TPR) + bundle + human-readable + aws s3 cp minimum-assessment-scope.json "s3://$BUCKET_NAME/.well-known/minimum-assessment-scope.json" --content-type application/json --cache-control "public, max-age=300" + aws s3 cp minimum-assessment-scope.bundle "s3://$BUCKET_NAME/.well-known/minimum-assessment-scope.bundle" --content-type application/json --cache-control "public, max-age=300" + aws s3 cp minimum-assessment-scope.md "s3://$BUCKET_NAME/.well-known/minimum-assessment-scope.md" --content-type "text/markdown; charset=utf-8" --cache-control "public, max-age=300" + # Trust-center data: the assessor guide, the agency access exercise and + # the manifest (JSON, signature, Markdown); the per-rule evidence result; + # the simulated assessor's set with ITS bundle (signed by the assessor's + # identity, not this workflow's). + for a in assessor-guide agency-access-exercise trust-manifest; do + aws s3 cp "$a.json" "s3://$BUCKET_NAME/.well-known/$a.json" --content-type application/json --cache-control "public, max-age=300" + aws s3 cp "$a.bundle" "s3://$BUCKET_NAME/.well-known/$a.bundle" --content-type application/json --cache-control "public, max-age=300" + aws s3 cp "$a.md" "s3://$BUCKET_NAME/.well-known/$a.md" --content-type "text/markdown; charset=utf-8" --cache-control "public, max-age=300" + done + for a in frr-evidence simulated-assessment; do + aws s3 cp "$a.json" "s3://$BUCKET_NAME/.well-known/$a.json" --content-type application/json --cache-control "public, max-age=300" + aws s3 cp "$a.bundle" "s3://$BUCKET_NAME/.well-known/$a.bundle" --content-type application/json --cache-control "public, max-age=300" + done + # The complete human-readable views and the policies and procedures. + while read -r f; do + aws s3 cp "$f" "s3://$BUCKET_NAME/.well-known/$f" --content-type "text/markdown; charset=utf-8" --cache-control "public, max-age=300" + done < published-docs.txt + # Incident log (IEC-CSO-EFR) + every Initial/Ongoing/Final report + signatures + aws s3 cp incident-reports.json "s3://$BUCKET_NAME/.well-known/incident-reports.json" --content-type application/json --cache-control "public, max-age=300" + aws s3 cp incident-reports.bundle "s3://$BUCKET_NAME/.well-known/incident-reports.bundle" --content-type application/json --cache-control "public, max-age=300" + aws s3 cp incident-reports.md "s3://$BUCKET_NAME/.well-known/incident-reports.md" --content-type "text/markdown; charset=utf-8" --cache-control "public, max-age=300" + aws s3 cp incident-deliveries.json "s3://$BUCKET_NAME/.well-known/incident-deliveries.json" --content-type application/json --cache-control "public, max-age=300" + aws s3 cp incident-deliveries.bundle "s3://$BUCKET_NAME/.well-known/incident-deliveries.bundle" --content-type application/json --cache-control "public, max-age=300" + for f in incident-INC-*.json; do + aws s3 cp "$f" "s3://$BUCKET_NAME/.well-known/$f" --content-type application/json --cache-control "public, max-age=300" + aws s3 cp "${f%.json}.bundle" "s3://$BUCKET_NAME/.well-known/${f%.json}.bundle" --content-type application/json --cache-control "public, max-age=300" + done echo "✅ All signed artifacts published to /.well-known/ (post-gate)" + # CDS-CSO-FRC: each FedRAMP Certification Report exactly as received (data + # committed byte for byte; its sha256 checked against the register when the + # index was built), and read back from the origin to prove the served bytes + # are unmodified. Separate from the step above because the files are named + # by the register, not by this workflow. Simulated FedRAMP: see the index. + - name: Publish FedRAMP Certification Reports byte-identical + working-directory: infrastructure + run: | + set -euo pipefail + BUCKET_NAME=$(terraform output -raw s3_bucket_name) + python3 ../scripts/check-published-redaction.py fedramp-certification-reports/* + jq -r '.reports[] | "\(.file) \(.sha256)"' fedramp-certification-reports.json | while read -r f sha; do + aws s3 cp "fedramp-certification-reports/$f" "s3://$BUCKET_NAME/.well-known/fedramp-certification-reports/$f" \ + --content-type application/json --cache-control "public, max-age=300" + got=$(aws s3 cp "s3://$BUCKET_NAME/.well-known/fedramp-certification-reports/$f" - | sha256sum | awk '{print $1}') + [ "$got" = "$sha" ] || { echo "::error::$f served bytes differ from the report as received"; exit 1; } + echo "published unmodified: fedramp-certification-reports/$f" + # Its complete human-readable view (CDS-TRC-HMR), built beside it and + # scanned by the gate above with the report. + aws s3 cp "fedramp-certification-reports/${f%.json}.view.md" \ + "s3://$BUCKET_NAME/.well-known/fedramp-certification-reports/${f%.json}.view.md" \ + --content-type "text/markdown; charset=utf-8" --cache-control "public, max-age=300" + done + # ------------------------------------------------------------------------- # ATTEST ARTIFACT PROVENANCE (SLSA v1 / in-toto, DSSE — Task 14 / S2) # ------------------------------------------------------------------------- @@ -1865,25 +2488,34 @@ jobs: for a in vdr-detail-report vdr-accepted-vulnerabilities vdr-history; do check "$a.json" ".well-known/$a.json" done + check vdr-non-machine-vv.json .well-known/vdr-non-machine-vv.json + check vdr-monthly.json .well-known/vdr-monthly.json check ongoing-certification-report.json .well-known/ongoing-certification-report.json - check certification-overview-package.json .well-known/certification-overview-package.json + check fedramp-inbox-simulation.json .well-known/fedramp-inbox-simulation.json check availability.json .well-known/availability.json check policy-index.json .well-known/policy-index.json check security-decision-record.json .well-known/security-decision-record.json check certification-package-overview.json .well-known/certification-package-overview.json + check fedramp-certification-reports.json .well-known/fedramp-certification-reports.json + check package-submission-log.json .well-known/package-submission-log.json + check quarterly-review.ics .well-known/quarterly-review.ics + check significant-change-notifications.json .well-known/significant-change-notifications.json + check significant-change-notifications.atom .well-known/significant-change-notifications.atom + check scn-evaluations.json .well-known/scn-evaluations.json check iiw.csv .well-known/iiw.csv check boundary-map.json .well-known/boundary-map.json check reconcile-report.json .well-known/reconcile-report.json check trust-center.json .well-known/trust-center.json check conformance-results.json .well-known/conformance-results.json if [ -f boundary-corroboration.json ]; then check boundary-corroboration.json .well-known/boundary-corroboration.json; fi + for f in incident-*.json; do check "$f" ".well-known/$f"; done # SLSA/in-toto provenance attestations (S2/S3): served bytes match the build. for a in ksi-signal.json security-decision-record.json vdr-report.json iiw.csv; do check "$a.intoto.jsonl" ".well-known/$a.intoto.jsonl" done # Retired artifacts must be gone from the origin. Only a 404 counts as # gone: any other error (e.g. AccessDenied) fails rather than passing. - for retired in oscal-poam.json oscal-poam.bundle oscal-poam.json.intoto.jsonl oscal-ssp.json oscal-ssp.bundle oscal-ssp.json.intoto.jsonl; do + for retired in oscal-poam.json oscal-poam.bundle oscal-poam.json.intoto.jsonl oscal-ssp.json oscal-ssp.bundle oscal-ssp.json.intoto.jsonl certification-overview-package.json certification-overview-package.bundle certification-overview-package.md; do if head_err=$(aws s3api head-object --bucket "$BUCKET_NAME" --key ".well-known/$retired" 2>&1 >/dev/null); then echo "::error::retired artifact still published: .well-known/$retired"; fail=1 elif printf '%s' "$head_err" | grep -q '(404)'; then @@ -2063,6 +2695,23 @@ jobs: if: always() run: rm -f infrastructure/tfstate-bootstrap.json + # =========================================================================== + # SIMULATED ASSESSOR (not a FedRAMP Recognized assessment) + # =========================================================================== + # "Totally Real Assessment Services, LLC (simulated)" verifies and validates + # every rule and KSI from the assessor guide and signs its record under its + # own workflow identity (a reusable workflow, so the certificate names + # simulated-assessor.yml). Runs where the deploy runs; the deploy needs it, and + # the SDR build fails without its signed set. + simulated-assessor: + name: Simulated assessor + needs: [test, compliance-check] + if: github.ref == 'refs/heads/main' && needs.compliance-check.outputs.compliant == 'true' + permissions: + contents: read + id-token: write + uses: ./.github/workflows/simulated-assessor.yml + # =========================================================================== # JOB 3: EXTRA SECURITY SCANS # =========================================================================== @@ -2155,6 +2804,90 @@ jobs: tfsec-results.json retention-days: 5 + # CPO-CSX-CPM: after every successful deploy, the unattended package + # maintainer runs once, so a green deploy proves it verifies the just-published + # package, rebuilds it at the deployed commit and publishes with its own role. + package-maintainer: + name: Prove the certification package maintainer + needs: [deploy] + if: needs.deploy.result == 'success' + permissions: + contents: read + id-token: write + issues: write + uses: ./.github/workflows/package-maintenance.yml + # Least privilege: the one secret the maintainer uses, not `inherit`. + secrets: + CLOUDFRONT_DISTRIBUTION_ID: ${{ secrets.CLOUDFRONT_DISTRIBUTION_ID }} + + # A deploy is not done until the unattended incident report publisher has run + # on its own role from the incident-reports environment: the IEC records say + # it publishes, so a deploy where it cannot fails here. + incident-publisher: + name: Prove the incident report publisher + needs: [deploy] + if: needs.deploy.result == 'success' + permissions: + contents: read + id-token: write + issues: write + uses: ./.github/workflows/incident-reports.yml + # Least privilege: the one secret the publisher uses, not `inherit`. + secrets: + CLOUDFRONT_DISTRIBUTION_ID: ${{ secrets.CLOUDFRONT_DISTRIBUTION_ID }} + + # IVV-CSO-FIA / IVV-CSX-AIA: the pre-deploy assessment is a gate on the state + # this deploy replaces. This one assesses the state it just published, once the + # unattended publishers have also run: the same assessor, the same checks, and + # the live KSI signal must carry this commit. A failure fails the run and the + # notify job raises the deployment-failure issue (what was published stays). + post-deploy-assessor: + name: Post-deploy simulated assessor + needs: [deploy, package-maintainer, incident-publisher] + if: github.ref == 'refs/heads/main' && needs.deploy.result == 'success' && needs.package-maintainer.result == 'success' && needs.incident-publisher.result == 'success' + permissions: + contents: read + id-token: write + uses: ./.github/workflows/simulated-assessor.yml + with: + phase: post-deploy + + # The post-deploy set is accepted only when its signature verifies against the + # pinned assessor identity and it covers this commit and the KSI signal this + # deploy published (scripts/_assessor.py, bind); anything else fails the run. + post-deploy-binding: + name: Post-deploy assessment binding + runs-on: ubuntu-latest + timeout-minutes: 10 + needs: [deploy, post-deploy-assessor] + if: github.ref == 'refs/heads/main' && needs.post-deploy-assessor.result == 'success' + permissions: + contents: read + steps: + - name: Checkout the pinned assessor identity + uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 + with: + persist-credentials: false + + - name: Install cosign + uses: sigstore/cosign-installer@7e8b541eb2e61bf99390e1afd4be13a184e9ebc5 # v3.10.1 + + - name: Download the post-deploy assessment + uses: actions/download-artifact@9000827ccba6bdab643e8b6fd33ac0654aef8333 # v8.0.2 + with: + name: simulated-assessment-post-deploy + path: post-deploy/ + + - name: Verify the post-deploy assessment covers the just-published state + env: + PUBLISHED_SIGNAL_ID: ${{ needs.deploy.outputs.signal_id }} + run: | + python3 scripts/_assessor.py \ + --assessment post-deploy/simulated-assessment.json --assessment-bundle post-deploy/simulated-assessment.bundle \ + --assessment-commit "$GITHUB_SHA" --assessment-signal-id "$PUBLISHED_SIGNAL_ID" + jq -e '.subject.phase == "post-deploy"' post-deploy/simulated-assessment.json > /dev/null \ + || { echo "::error::the post-deploy set is not a post-deploy assessment"; exit 1; } + # =========================================================================== # JOB 4: ALERT WHEN THINGS BREAK # =========================================================================== @@ -2177,8 +2910,13 @@ jobs: notify: name: Notify on Failure runs-on: ubuntu-latest - needs: [compliance-check, deploy] - if: always() && (needs.compliance-check.result == 'failure' || needs.deploy.result == 'failure') + # The simulated assessor fails a run without failing the deploy (the deploy + # is then skipped), so its result is watched here too. So are the unit + # tests (which hold the rule-completeness gate) and the security scan: on + # main their failure skips the deploy rather than failing it. On a pull + # request their failure is the PR's own red check, so no issue is raised. + needs: [test, security-scan, compliance-check, simulated-assessor, deploy, package-maintainer, incident-publisher, post-deploy-assessor, post-deploy-binding] + if: always() && ((github.event_name != 'pull_request' && (needs.test.result == 'failure' || needs.security-scan.result == 'failure')) || needs.compliance-check.result == 'failure' || needs.simulated-assessor.result == 'failure' || needs.deploy.result == 'failure' || needs.package-maintainer.result == 'failure' || needs.incident-publisher.result == 'failure' || needs.post-deploy-assessor.result == 'failure' || needs.post-deploy-binding.result == 'failure') permissions: contents: read issues: write @@ -2190,8 +2928,15 @@ jobs: # `${{ }}` interpolation into the script body — templating workflow context # straight into executable script is the habit that causes injection bugs. env: + TEST_RESULT: ${{ needs.test.result }} + SCAN_RESULT: ${{ needs.security-scan.result }} COMPLIANCE_RESULT: ${{ needs.compliance-check.result }} + ASSESSOR_RESULT: ${{ needs.simulated-assessor.result }} DEPLOY_RESULT: ${{ needs.deploy.result }} + PUBLISHER_RESULT: ${{ needs.incident-publisher.result }} + MAINTAINER_RESULT: ${{ needs.package-maintainer.result }} + POST_ASSESSOR_RESULT: ${{ needs.post-deploy-assessor.result }} + POST_BINDING_RESULT: ${{ needs.post-deploy-binding.result }} with: script: | const TITLE = `Deployment failing: ${context.workflow}`; @@ -2205,8 +2950,15 @@ jobs: `| Trigger | \`${context.eventName}\` |`, `| Commit | ${context.sha} |`, `| Ref | ${context.ref} |`, + `| Unit tests (rule completeness included) | \`${process.env.TEST_RESULT}\` |`, + `| Security scan | \`${process.env.SCAN_RESULT}\` |`, `| Compliance check | \`${process.env.COMPLIANCE_RESULT}\` |`, + `| Simulated assessor | \`${process.env.ASSESSOR_RESULT}\` |`, `| Deploy | \`${process.env.DEPLOY_RESULT}\` |`, + `| Incident report publisher | \`${process.env.PUBLISHER_RESULT}\` |`, + `| Package maintainer | \`${process.env.MAINTAINER_RESULT}\` |`, + `| Post-deploy simulated assessor | \`${process.env.POST_ASSESSOR_RESULT}\` |`, + `| Post-deploy assessment binding | \`${process.env.POST_BINDING_RESULT}\` |`, ``, `Review the failing step in the run log, and the compliance reports it uploaded.`, ``, diff --git a/.github/workflows/evidence-nightly.yml b/.github/workflows/evidence-nightly.yml index 044323d1..2f5a906d 100644 --- a/.github/workflows/evidence-nightly.yml +++ b/.github/workflows/evidence-nightly.yml @@ -14,8 +14,11 @@ # So this workflow does the one thing that genuinely needs a daily cadence and # needs no infrastructure change at all: re-run the dependency scan against a # freshly-pulled Grype database, rebuild the VDR and its trend ledger, put them -# through the same vulnerability and reconciliation gates, and republish exactly -# those five objects. No Terraform apply. No website sync. No write outside +# through the same vulnerability and reconciliation gates, and republish the VDR +# family (the report, the trend, FedRAMP's three vulnerability reports, the +# monthly activity report and the non-machine V&V status, with their signatures, +# readable views and the provenance attestation; the publish step lists each +# object). No Terraform apply. No website sync. No write outside # `.well-known/vdr-*`. One more object in that prefix, vdr-status.json, is a # status beacon written on every run, pass or fail, for the evidence SLA # watchdog (infrastructure/watchdog.tf). It carries outcomes, not evidence. @@ -236,10 +239,11 @@ jobs: # Sigstore keyless signing via the GitHub Actions OIDC provider, and the # AWS role assumption. No AWS long-lived key. id-token: write - # Lets GITHUB_TOKEN download the weekly ZAP DAST artifact. Dependabot - # alerts are read with the DEPENDABOT_ALERTS_TOKEN secret: GITHUB_TOKEN - # cannot read them. + # Lets GITHUB_TOKEN download the ZAP DAST artifacts (actions) and read + # the CodeQL code-scanning alerts (security-events). Dependabot alerts are + # read with the DEPENDABOT_ALERTS_TOKEN secret: GITHUB_TOKEN cannot. actions: read + security-events: read steps: # ------------------------------------------------------------------------- @@ -423,7 +427,7 @@ jobs: # DETECTION INPUTS AND G7 # ------------------------------------------------------------------------- # The previous VDR, Dependabot alerts, the CISA KEV catalog, FIRST EPSS and - # the latest weekly DAST report. A failed fetch leaves .error, never + # the latest DAST reports and CodeQL alerts. A failed fetch leaves .error, never # an empty stand-in; the detection gate below fails the run on it (T52). - name: Fetch detection feeds working-directory: infrastructure @@ -441,6 +445,7 @@ jobs: --grype grype-python.json grype-js.json grype-lambda.json grype-a11y.json \ --dependabot dependabot-alerts.json --previous-vdr previous-vdr-report.json \ --checkov checkov-results.sarif --tfsec tfsec-results.json \ + --codeql codeql-alerts.json --zap-api zap-api-report.json \ --output detection.json # ------------------------------------------------------------------------- @@ -448,14 +453,17 @@ jobs: # ------------------------------------------------------------------------- # scripts/reconcile.py loads the signal, VDR, SDR and CPO and reads the # decision register from the checkout. The SDR and CPO are the ones the last - # reviewed deploy published with this inventory; they arrive over the public - # internet, so each is verified against the deploy workflow's pinned identity - # before use, exactly like the inventory above. Fail closed: an unverifiable + # reviewed deploy published with this inventory (or the daily package + # maintainer rebuilt from it); they arrive over the public internet, so each + # is verified against one of those two pinned identities before use, exactly like the inventory above. Fail closed: an unverifiable # artifact is not evidence. They are not re-signed or re-published here. - name: Fetch and verify the published SDR and CPO (reconciliation inputs) working-directory: infrastructure run: | set -euo pipefail + # Signed by the deploy, or by the daily package maintainer that rebuilds + # them at the deployed commit (package-maintenance.yml, CPO-CSX-CPM). + MAINTAINER_IDENTITY="https://github.com/${{ github.repository }}/.github/workflows/package-maintenance.yml@refs/heads/main" for art in security-decision-record certification-package-overview; do curl -sfL --retry 3 --retry-delay 5 -o "$art.json" "${SITE_ORIGIN}/.well-known/$art.json" curl -sfL --retry 3 --retry-delay 5 -o "$art.bundle" "${SITE_ORIGIN}/.well-known/$art.bundle" @@ -463,6 +471,11 @@ jobs: --bundle "$art.bundle" \ --certificate-identity "${DEPLOY_SIGNER_IDENTITY}" \ --certificate-oidc-issuer "${COSIGN_OIDC_ISSUER}" \ + "$art.json" \ + || cosign verify-blob \ + --bundle "$art.bundle" \ + --certificate-identity "${MAINTAINER_IDENTITY}" \ + --certificate-oidc-issuer "${COSIGN_OIDC_ISSUER}" \ "$art.json" done @@ -515,6 +528,46 @@ jobs: # --opa is deliberately not passed; see the header. Its absence leaves the # builder's default path pointing at a file that does not exist, which # ingest_opa treats as an empty finding set. + # VDR-CSO-FAV: runs of the pipeline that a block-mode check stopped. The + # next report lists each one (no run IDs or URLs are kept). A failed query + # fails the step: no list cannot read as "no failures". + # KSI-MLA-RVL, KSI-CMT-RVP (DEC-195: nobody reads the logs by hand): CloudTrail + # write events and GitHub's record of main since the previous review, judged + # by rule; a planted simulated intruder must be caught every run. Anything + # unexpected goes into GATE_EVENTS_FILE (audit-log.unexpected, detect-and- + # recover), so the VDR built next carries it as a process finding. Needs + # cloudtrail:LookupEvents (infrastructure/bootstrap/evidence-nightly.tf); an + # AccessDenied stops the run with that instruction. + - name: Audit-log review (KSI-MLA-RVL) + working-directory: infrastructure + env: + GITHUB_TOKEN: ${{ github.token }} + run: | + set -euo pipefail + prev=() + code=$(curl -s -o previous-audit-log-review.json -w '%{http_code}' "${SITE_ORIGIN}/.well-known/vdr-audit-log-review.json") + if [ "$code" = "200" ]; then + curl -sfL --retry 3 -o previous-audit-log-review.bundle "${SITE_ORIGIN}/.well-known/vdr-audit-log-review.bundle" + cosign verify-blob --bundle previous-audit-log-review.bundle --certificate-oidc-issuer "${COSIGN_OIDC_ISSUER}" \ + --certificate-identity "https://github.com/${{ github.repository }}/.github/workflows/evidence-nightly.yml@refs/heads/main" \ + previous-audit-log-review.json + prev=(--previous previous-audit-log-review.json) + elif [ "$code" != "404" ] && [ "$code" != "403" ]; then + echo "::error::vdr-audit-log-review.json answered HTTP $code"; exit 1 + fi + python3 ../scripts/audit-log-review.py --out vdr-audit-log-review.json "${prev[@]}" + cosign sign-blob --yes --new-bundle-format --bundle vdr-audit-log-review.bundle vdr-audit-log-review.json + + - name: Collect failed pipeline runs (VDR-CSO-FAV) + working-directory: infrastructure + env: + GH_TOKEN: ${{ github.token }} + run: | + set -euo pipefail + gh run list --repo "${{ github.repository }}" --branch main --status failure --limit 100 \ + --json workflowName,createdAt,updatedAt,event,headBranch > failed-runs.json + jq length failed-runs.json + - name: Build VDR Report (FedRAMP 20x Class C) id: vdr working-directory: infrastructure @@ -528,12 +581,16 @@ jobs: --dependabot dependabot-alerts.json \ --grype grype.json \ --zap zap-report.json \ + --zap-max-age-days 3 \ + --zap-api zap-api-report.json \ + --codeql codeql-alerts.json \ --kev kev-catalog.json \ --epss epss-scores.csv.gz \ --detection detection.json \ --conformance conformance-results.json \ --ksi-signal ksi-signal.json \ --runtime-signal ksi-signal-runtime.json \ + --failed-runs failed-runs.json \ --output vdr-report.json jq '{summary, risk_accepted_count: (.risk_accepted | length)}' vdr-report.json @@ -602,7 +659,11 @@ jobs: if: ${{ !cancelled() && steps.vdr.outcome == 'success' }} working-directory: infrastructure run: | - python3 ../scripts/reconcile.py --artifacts-dir . --live --expect-commit "${SIGNAL_COMMIT}" + # --runtime-signal adds invariant (n): every machine component has an + # assessed runtime validation under 72h (VDR-TFR-MVX). A runtime signal + # that failed to fetch was removed above, which fails (n), never skips it. + python3 ../scripts/reconcile.py --artifacts-dir . --live --expect-commit "${SIGNAL_COMMIT}" \ + --runtime-signal ksi-signal-runtime.json # ------------------------------------------------------------------------- # SIGN — only the artifacts this workflow publishes @@ -650,6 +711,102 @@ jobs: cosign sign-blob --yes --new-bundle-format --bundle "$a.bundle" "$a.json" done + # VDR-TFR-NMV: the machine checks of every non-machine resource, published + # with the VDR. Not enforced here (a stale document must not stop the + # nightly evidence); the deploy enforces it, and a failing check publishes + # verifiedAt at the epoch, so the watchdog alarms at once. + - name: Non-machine verification and validation status (VDR-TFR-NMV) + working-directory: infrastructure + run: | + set -euo pipefail + python3 ../scripts/check-non-machine-vv.py --out vdr-non-machine-vv.json + cosign sign-blob --yes --new-bundle-format --bundle vdr-non-machine-vv.bundle vdr-non-machine-vv.json + + # KSI-RPL-TRC (DEC-195): on the first of each month, the recovery exercise: + # the site rebuilt from the deployed commit and compared with what is served, + # versioning and PITR re-read from the verified runtime signal, and each + # November a simulated tabletop. Read-only; nothing is restored. A failing + # exercise is not frozen and does not stop the VDR refresh: the index is + # still written, and the run fails at the end instead (step "Scheduled + # reviews held and not overdue"). A frozen exercise's files pass the + # FedRAMP ID and redaction gates here, before they are signed. + - name: Hold the recovery exercise when due (KSI-RPL-TRC) + id: recovery + continue-on-error: true + working-directory: infrastructure + run: | + set -euo pipefail + : > recovery-new.txt + prev=() + code=$(curl -s -o previous-recovery-exercises.json -w '%{http_code}' "${SITE_ORIGIN}/.well-known/vdr-recovery-exercises.json") + if [ "$code" = "200" ]; then + curl -sfL --retry 3 -o previous-recovery-exercises.bundle "${SITE_ORIGIN}/.well-known/vdr-recovery-exercises.bundle" + cosign verify-blob --bundle previous-recovery-exercises.bundle --certificate-oidc-issuer "${COSIGN_OIDC_ISSUER}" \ + --certificate-identity "https://github.com/${{ github.repository }}/.github/workflows/evidence-nightly.yml@refs/heads/main" \ + previous-recovery-exercises.json + prev=(--previous-index previous-recovery-exercises.json) + elif [ "$code" != "404" ] && [ "$code" != "403" ]; then + echo "::error::vdr-recovery-exercises.json answered HTTP $code"; exit 1 + fi + python3 ../scripts/hold-recovery-exercise.py --commit "$SIGNAL_COMMIT" \ + --runtime-signal ksi-signal-runtime.json "${prev[@]}" --out . --new-files recovery-new.txt \ + || rc=$? + cosign sign-blob --yes --new-bundle-format --bundle vdr-recovery-exercises.bundle vdr-recovery-exercises.json + while read -r f; do + [[ "$f" =~ ^vdr-recovery-exercise-[0-9]{4}-[0-9]{2}-[0-9]{2}\.json$ ]] || { echo "::error::unexpected file $f"; exit 1; } + python3 ../scripts/check-fedramp-id.py "$f" + python3 ../scripts/check-published-redaction.py "$f" "${f%.json}.view.md" + cosign sign-blob --yes --new-bundle-format --bundle "${f%.json}.bundle" "$f" + done < recovery-new.txt + exit "${rc:-0}" + + # VER-TFR-MHR, VER-RPT-HLO, VER-RPT-PER: the month-to-date activity report, + # in human-readable form, listing every kind of detection and response + # activity ("none this period" when nothing happened). The previous published + # report carries the month's earlier runs forward, read only if its signature + # verifies against this workflow or the other publisher. + - name: Build monthly VDR activity report (VER-TFR-MHR) + working-directory: infrastructure + run: | + set -euo pipefail + prev=() + if curl -sfL --retry 3 --retry-delay 5 -o previous-vdr-monthly.json "${SITE_ORIGIN}/.well-known/vdr-monthly.json"; then + curl -sfL --retry 3 --retry-delay 5 -o previous-vdr-monthly.bundle "${SITE_ORIGIN}/.well-known/vdr-monthly.bundle" + ok=0 + for identity in "${DEPLOY_SIGNER_IDENTITY}" \ + "https://github.com/${{ github.repository }}/.github/workflows/evidence-nightly.yml@refs/heads/main"; do + if cosign verify-blob --bundle previous-vdr-monthly.bundle --certificate-identity "$identity" \ + --certificate-oidc-issuer "${COSIGN_OIDC_ISSUER}" previous-vdr-monthly.json 2>/dev/null; then ok=1; break; fi + done + [ "$ok" -eq 1 ] || { echo "::error::previous vdr-monthly.json does not verify; refusing to carry it forward"; exit 1; } + prev=(--previous previous-vdr-monthly.json) + else + echo "No previous vdr-monthly.json published; the month starts with this build's runs." + fi + # Activities generated from run records (VER-RPT-HLO): the simulated + # assessor's and the inbox exercise's published runs, each used only + # when its signature verifies; the incident exercises; this run's + # recovery exercises and audit-log review. + gen=(--incidents ../data/incidents.json --recovery-exercises vdr-recovery-exercises.json + --audit-log-review vdr-audit-log-review.json) + for pair in "simulated-assessment:simulated-assessor.yml:--assessment" \ + "fedramp-inbox-simulation:deploy-with-opa.yml:--inbox"; do + IFS=: read -r name wf flag <<< "$pair" + if curl -sfL --retry 3 -o "run-$name.json" "${SITE_ORIGIN}/.well-known/$name.json" \ + && curl -sfL --retry 3 -o "run-$name.bundle" "${SITE_ORIGIN}/.well-known/$name.bundle" \ + && cosign verify-blob --bundle "run-$name.bundle" --certificate-oidc-issuer "${COSIGN_OIDC_ISSUER}" \ + --certificate-identity "https://github.com/${{ github.repository }}/.github/workflows/$wf@refs/heads/main" \ + "run-$name.json" 2>/dev/null; then + gen+=("$flag" "run-$name.json") + else + echo "::notice::$name.json is not published or does not verify; its runs are not listed this time" + fi + done + python3 ../scripts/build-vdr-monthly.py --vdr vdr-report.json --history vdr-history.json \ + --decisions ../data/decisions.json --activities ../data/vdr-activities.json \ + --non-machine vdr-non-machine-vv.json "${prev[@]}" "${gen[@]}" + cosign sign-blob --yes --new-bundle-format --bundle vdr-monthly.bundle vdr-monthly.json + # The published VDR carries a SLSA/in-toto provenance attestation, and that # attestation binds to the artifact's sha256. Republishing vdr-report.json # without re-attesting it would leave the served @@ -694,13 +851,38 @@ jobs: # SSE-S3 (AES256), so no KMS grant is involved. # Publication redaction gate over exactly the files the next step uploads # (scripts/_redact.py): fails closed on any AWS account ID. + # CDS-CSO-CBF: the complete human-readable view of each JSON republished + # below, parsed back and required to reproduce it, so the views the deploy + # published never drift from the JSON this run replaces. + - name: Rebuild the human-readable views (format parity) + working-directory: infrastructure + run: >- + python3 ../scripts/build-human-views.py + vdr-report.json vdr-trend.json vdr-detail-report.json vdr-accepted-vulnerabilities.json vdr-history.json + vdr-non-machine-vv.json vdr-monthly.json vdr-audit-log-review.json vdr-recovery-exercises.json + + # CDS-CSO-FID: every report this run republishes carries the offering's + # FedRAMP ID (the same gate the deploy runs over its REPORTS list). + - name: FedRAMP ID in every republished report (CDS-CSO-FID) + working-directory: infrastructure + run: >- + python3 ../scripts/check-fedramp-id.py + vdr-report.json vdr-trend.json vdr-detail-report.json vdr-accepted-vulnerabilities.json vdr-history.json + vdr-non-machine-vv.json vdr-monthly.json vdr-audit-log-review.json vdr-recovery-exercises.json + - name: Publication redaction gate (no AWS account ID) working-directory: infrastructure run: >- python3 ../scripts/check-published-redaction.py vdr-report.json vdr-report.md vdr-trend.json vdr-detail-report.json vdr-detail-report.md vdr-accepted-vulnerabilities.json - vdr-accepted-vulnerabilities.md vdr-history.json + vdr-accepted-vulnerabilities.md vdr-history.json vdr-non-machine-vv.json + vdr-monthly.json vdr-monthly.md + vdr-report.view.md vdr-trend.view.md vdr-detail-report.view.md + vdr-accepted-vulnerabilities.view.md vdr-history.view.md + vdr-non-machine-vv.view.md vdr-monthly.view.md + vdr-audit-log-review.json vdr-audit-log-review.view.md + vdr-recovery-exercises.json vdr-recovery-exercises.view.md - name: Publish VDR + trend to /.well-known/ id: publish @@ -729,9 +911,38 @@ jobs: done put vdr-detail-report.md "text/markdown; charset=utf-8" put vdr-accepted-vulnerabilities.md "text/markdown; charset=utf-8" + # The complete human-readable views, rebuilt with the JSON above. + for a in vdr-report vdr-trend vdr-detail-report vdr-accepted-vulnerabilities vdr-history vdr-non-machine-vv vdr-monthly; do + put "$a.view.md" "text/markdown; charset=utf-8" + done + # Non-machine V&V status (VDR-TFR-NMV). + put vdr-non-machine-vv.json "application/json" + put vdr-non-machine-vv.bundle "application/json" + # Monthly activity report (VER-TFR-MHR). + put vdr-monthly.json "application/json" + put vdr-monthly.bundle "application/json" + put vdr-monthly.md "text/markdown; charset=utf-8" # The refreshed provenance attestation. Its key matches the same # `.well-known/vdr-*` prefix, so it needs no extra IAM grant. put vdr-report.json.intoto.jsonl "application/json" + # Scheduled reviews (scripts/_scheduled_review.py), under the same prefix. + put vdr-audit-log-review.view.md "text/markdown; charset=utf-8" + put vdr-audit-log-review.bundle "application/json" + put vdr-audit-log-review.json "application/json" + # A held recovery exercise is frozen: never put over a served copy. Its + # files were gated and signed in the step that held it. + while read -r f; do + code=$(curl -s -o /dev/null -w '%{http_code}' "${SITE_ORIGIN}/.well-known/$f") + if [ "$code" != "404" ] && [ "$code" != "403" ]; then + echo "::error::.well-known/$f is already served (HTTP $code): a held exercise is never overwritten"; exit 1 + fi + put "${f%.json}.view.md" "text/markdown; charset=utf-8" + put "${f%.json}.bundle" "application/json" + put "$f" "application/json" + done < <(cat recovery-new.txt 2>/dev/null || true) + put vdr-recovery-exercises.view.md "text/markdown; charset=utf-8" + put vdr-recovery-exercises.bundle "application/json" + put vdr-recovery-exercises.json "application/json" # Scoped to exactly the paths this workflow wrote. The deploy path # invalidates `/*`; that is a whole-site operation and is not this @@ -777,6 +988,66 @@ jobs: --expect-sha256 "${BUILT_SHA}" \ --retries 12 --retry-delay 20 + # CCM-QTR-MTG: a Quarterly Review date passed with no review published + # (package-maintenance.yml holds them, with simulated attendees) fails the + # nightly. A missing index is checked as empty: any passed date then fails. + - name: No Quarterly Review overdue + run: | + set -euo pipefail + code=$(curl -s -o qr-index.json -w '%{http_code}' "${SITE_ORIGIN}/.well-known/quarterly-reviews.json") + case "$code" in + 200) + # Only the maintainer's signature counts: a forged index cannot hide a missed review. + curl -sfL --retry 3 -o qr-index.bundle "${SITE_ORIGIN}/.well-known/quarterly-reviews.bundle" + cosign verify-blob --bundle qr-index.bundle --certificate-oidc-issuer "${COSIGN_OIDC_ISSUER}" \ + --certificate-identity "https://github.com/sam-aydlette/samaydlette.com/.github/workflows/package-maintenance.yml@refs/heads/main" \ + qr-index.json + python3 scripts/check-quarterly-review.py --index qr-index.json ;; + 403|404) python3 scripts/check-quarterly-review.py --no-index ;; + *) echo "::error::quarterly-reviews.json answered HTTP $code"; exit 1 ;; + esac + + # DEC-195: the scheduled reviews ran. A recovery exercise or Annual Security + # Review due date passed with none published fails the nightly (the security + # review's index only counts when the maintainer's signature verifies); a + # recovery exercise that failed today fails it too, after the VDR published; + # and an unexpected write evaluated reportable stops it (audit-log.reportable). + - name: Scheduled reviews held and not overdue + if: ${{ always() && steps.publish.outcome == 'success' }} + env: + RECOVERY: ${{ steps.recovery.outcome }} + run: | + set -euo pipefail + if ! git cat-file -e "${SIGNAL_COMMIT}:scripts/check-scheduled-review.py" 2>/dev/null; then + echo "::notice::the deployed commit predates the automated scheduled reviews"; exit 0 + fi + [ "$RECOVERY" != "failure" ] || { echo "::error::the recovery exercise failed (see its step)"; exit 1; } + python3 scripts/audit-log-review.py --enforce infrastructure/vdr-audit-log-review.json + if [ -f infrastructure/vdr-recovery-exercises.json ]; then + python3 scripts/check-scheduled-review.py --review recovery-exercise --index infrastructure/vdr-recovery-exercises.json + else + python3 scripts/check-scheduled-review.py --review recovery-exercise --no-index + fi + code=$(curl -s -o sr-index.json -w '%{http_code}' "${SITE_ORIGIN}/.well-known/security-reviews.json") + case "$code" in + 200) + curl -sfL --retry 3 -o sr-index.bundle "${SITE_ORIGIN}/.well-known/security-reviews.bundle" + cosign verify-blob --bundle sr-index.bundle --certificate-oidc-issuer "${COSIGN_OIDC_ISSUER}" \ + --certificate-identity "https://github.com/${{ github.repository }}/.github/workflows/package-maintenance.yml@refs/heads/main" \ + sr-index.json + python3 scripts/check-scheduled-review.py --review security-review --index sr-index.json ;; + 403|404) python3 scripts/check-scheduled-review.py --review security-review --no-index ;; + *) echo "::error::security-reviews.json answered HTTP $code"; exit 1 ;; + esac + + # SCG-ENH-CMP: the repository settings the workflow token can read, compared + # with the secure configuration guide's recommended values (DEC-151). + - name: Compare repository settings with the secure configuration guide (SCG-ENH-CMP) + env: + GITHUB_TOKEN: ${{ github.token }} + DEPENDABOT_TOKEN: ${{ secrets.DEPENDABOT_ALERTS_TOKEN }} + run: python3 scripts/check-secure-config.py --account github-owner --output "$RUNNER_TEMP/repo-settings.json" --md-output "$RUNNER_TEMP/repo-settings.md" + # ------------------------------------------------------------------------- # STATUS BEACON — written on every run, pass or fail # ------------------------------------------------------------------------- @@ -807,7 +1078,11 @@ jobs: # What G7 found about each detection input, when the gate got that far. [ -s detection.json ] || echo 'null' > detection.json if [ -s conformance-results.json ]; then cp conformance-results.json conformance-status.json; else echo 'null' > conformance-status.json; fi + # CDS-CSO-FID: the offering's FedRAMP ID. The beacon publishes whatever + # failed, so an unreadable offering gives null rather than no beacon. + fid=$(python3 -c 'import sys; sys.path.insert(0, "../scripts"); import _offering; print(_offering.fedramp_id())' 2>/dev/null || true) jq -n \ + --arg fid "$fid" \ --slurpfile gs gate-status.json \ --slurpfile det detection.json \ --slurpfile prof conformance-status.json \ @@ -817,11 +1092,12 @@ jobs: --arg reconcile "${RECONCILE:-not reached}" \ --arg published "${PUBLISHED:-not reached}" \ --arg finished_at "$(date -u +%Y-%m-%dT%H:%M:%SZ)" \ - --arg run_url "${GITHUB_SERVER_URL}/${GITHUB_REPOSITORY}/actions/runs/${GITHUB_RUN_ID}" \ + --arg run_commit "${GITHUB_SHA}" \ --arg commit "${SIGNAL_COMMIT:-unknown}" \ - '{schema: "vdr-status/1", result: $result, finished_at: $finished_at, + '{schema: "vdr-status/1", fedRampId: (if $fid == "" then null else $fid end), + result: $result, finished_at: $finished_at, vuln_gate: $vuln_gate, reconcile: $reconcile, published: $published, - inventory_commit: $commit, run_url: $run_url, + inventory_commit: $commit, run: {workflow: "evidence-nightly.yml", commit: $run_commit}, gates: $gs[0].gates, gate_events: $gs[0].gate_events, detection: $det[0], profile: (if $prof[0] then {profile_version: $prof[0].profile_version, conformance_sha256: $profsha} else null end)}' > vdr-status.json diff --git a/.github/workflows/incident-reports.yml b/.github/workflows/incident-reports.yml new file mode 100644 index 00000000..20618e32 --- /dev/null +++ b/.github/workflows/incident-reports.yml @@ -0,0 +1,279 @@ +# ============================================================================= +# GitHub Actions Workflow: Incident Reports (IEC-CSO-AIR) +# ============================================================================= +# FedRAMP's Incident Evaluation and Communication rules put an Initial Incident +# Report one hour after a FedRAMP Reportable Incident is identified (Class C, +# N3-N5), and an Ongoing report every six hours after that. The deploy path is +# behind a human reviewer and cannot keep those clocks, so reporting runs here, +# unattended, the moment the incident register changes (IEC-CSO-AIR: automate +# reporting; no hand-crafted email): +# +# push to data/incidents.json on main, or by hand, or twice a day, or after +# each nightly VDR refresh +# -> validate the register (scripts/_incidents.py, fail-closed) +# -> fetch the published VDR, verified against the deploy or nightly +# identity, for the vulnerabilities that are reportable incidents +# (VER-TFR-IRI / VER-TFR-NRI, decided by policies/triage.rego) +# -> build every IIR/OIR/FIR (validated against FedRAMP's incident report +# schema) and the incident log (scripts/build-incident-report.py) +# -> sign, redaction-gate, publish under /.well-known/incident-*, invalidate +# -> check the clocks: fail, and raise an issue, when a report is overdue +# +# The evidence watchdog (infrastructure/watchdog.tf) reads the published log +# hourly and pages by email when a listed report passes its deadline, on AWS's +# clock, whether or not this workflow runs. +# +# NOTIFICATION IS PUBLISH-ONLY. Nothing here sends a report to FedRAMP or to an +# agency. The operator has not authorized sending, and this system has no +# FedRAMP certification and no agency customers; the register's policy and +# every report say so. Sending is a separate decision and a separate change. +# +# THE TRADE, as for the evidence nightly: an unattended production write. Its +# role (infrastructure/bootstrap/incident-reports.tf, operator-applied) can put +# objects under `.well-known/incident-*` and invalidate the CDN, and nothing +# else: no Terraform, no website sync, no delete, no read of anything. +# ============================================================================= + +name: Incident Reports + +on: + push: + branches: [main] + paths: [data/incidents.json] + workflow_dispatch: + # Called by every deploy (deploy-with-opa.yml, job incident-publisher) after + # the deploy job succeeds, so a green deploy proves this publisher assumes its + # role from the incident-reports environment and publishes; a deploy whose + # publisher cannot fails. + workflow_call: + # Only the secret the publish step uses; the caller passes it by name. + secrets: + CLOUDFRONT_DISTRIBUTION_ID: + required: true + # Keeps the published log inside its 24-hour freshness window when nothing + # changes, and re-reads the VDR for new VER-TFR-IRI/NRI triggers. + schedule: + - cron: '47 7 * * *' + - cron: '47 19 * * *' + # Right after each nightly VDR refresh, so a vulnerability that has just + # become a reportable incident is in the log within minutes of the VDR. + workflow_run: + workflows: [Evidence Nightly (VDR refresh)] + types: [completed] + branches: [main] + +concurrency: + group: incident-reports + cancel-in-progress: false + +permissions: + contents: read + +env: + AWS_REGION: us-east-2 + # Same pins as the deploy and the nightly (tests/test_incidents.py checks). + OPA_VERSION: 1.18.2 + OPA_SHA256: 9903e5125ac281104f2c4b7371d10cc3b74a98933743fcbfc174f9bf0ab20de8 + SITE_BUCKET: samaydlette.com + SITE_ORIGIN: https://samaydlette.com + COSIGN_OIDC_ISSUER: https://token.actions.githubusercontent.com + +jobs: + report: + name: Build, sign and publish incident reports + runs-on: ubuntu-latest + timeout-minutes: 20 + # A nightly that did not succeed published no new VDR; a pull request never + # reaches the role. The event check closes a fork branch named `main`. + if: >- + github.event_name != 'workflow_run' || ( + github.event.workflow_run.conclusion == 'success' && + github.event.workflow_run.event != 'pull_request' && + github.event.workflow_run.head_repository.full_name == github.repository) + # No required reviewer: the clocks run while nobody is awake. The role this + # environment can assume writes only .well-known/incident-*. + environment: incident-reports + outputs: + clock: ${{ steps.clock.outcome }} + publish: ${{ steps.publish.outcome }} + permissions: + contents: read + id-token: write + + steps: + - name: Checkout code + uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 + + - name: Install cosign + uses: sigstore/cosign-installer@7e8b541eb2e61bf99390e1afd4be13a184e9ebc5 # v3.10.1 + + - name: Setup OPA (triage policy) + run: | + curl -fL --retry 5 --retry-delay 5 --connect-timeout 10 --max-time 120 \ + -o opa "https://openpolicyagent.org/downloads/v${{ env.OPA_VERSION }}/opa_linux_amd64_static" + echo "${{ env.OPA_SHA256 }} opa" | sha256sum -c - + chmod 755 ./opa + sudo mv opa /usr/local/bin + opa version + + # The VDR arrives over the public internet, so it is verified before a byte + # of it is used: it must be signed by the deploy or the nightly on main. + - name: Fetch and verify the published VDR report + run: | + set -euo pipefail + mkdir -p out + curl -sfL --retry 3 --retry-delay 5 -o vdr-report.json "${SITE_ORIGIN}/.well-known/vdr-report.json" + curl -sfL --retry 3 --retry-delay 5 -o vdr-report.bundle "${SITE_ORIGIN}/.well-known/vdr-report.bundle" + ok=0 + for wf in deploy-with-opa evidence-nightly; do + if cosign verify-blob --bundle vdr-report.bundle \ + --certificate-identity "https://github.com/${{ github.repository }}/.github/workflows/$wf.yml@refs/heads/main" \ + --certificate-oidc-issuer "${COSIGN_OIDC_ISSUER}" vdr-report.json 2>/dev/null; then ok=1; break; fi + done + [ "$ok" -eq 1 ] || { echo "::error::the published VDR does not verify; refusing to derive incidents from it"; exit 1; } + + - name: Build incident reports (IIR, OIR, FIR) + id: build + run: python3 scripts/build-incident-report.py --incidents data/incidents.json --vdr vdr-report.json --out-dir out + + # SIMULATED delivery: each report goes to a simulated FedRAMP and agency + # recipient and the delivery log records it. Nothing is sent. A failed + # delivery fails the run before anything is published. + - name: Deliver incident reports (simulated recipients; nothing sent) + run: python3 scripts/deliver-incident-reports.py --dir out + + # CDS-CSO-FID: the log, every report and the delivery log carry the + # offering's FedRAMP ID (the deploy runs the same gate). + - name: FedRAMP ID in every incident report (CDS-CSO-FID) + working-directory: out + run: python3 ../scripts/check-fedramp-id.py incident-*.json + + # CDS-CSO-CBF: the complete human-readable view of the incident log, the + # delivery log and every report, parsed back and required to reproduce each, so the views the + # deploy published never drift from the JSON this run replaces. Built before + # the redaction gate, which scans them (incident-*.md). + - name: Rebuild the human-readable views (format parity) + working-directory: out + run: python3 ../scripts/build-human-views.py incident-reports.json incident-deliveries.json incident-INC-*.json + + - name: Sign incident reports + working-directory: out + run: | + set -euo pipefail + for f in incident-*.json; do + cosign sign-blob --yes --new-bundle-format --bundle "${f%.json}.bundle" "$f" + done + + - name: Publication redaction gate (no AWS account ID) + working-directory: out + run: python3 ../scripts/check-published-redaction.py incident-*.json incident-*.md + + - name: Configure AWS credentials + uses: aws-actions/configure-aws-credentials@e1253824e5c10ff9df46874f81ed3ec929e19cfd # v6.3.0 + timeout-minutes: 6 + with: + # Defined in infrastructure/bootstrap/incident-reports.tf. Unset until + # the operator applies it and sets the variable; this step then fails + # and the alert job says so. + role-to-assume: ${{ vars.AWS_INCIDENT_REPORTS_ROLE_ARN }} + aws-region: ${{ env.AWS_REGION }} + retry-max-attempts: 5 + + - name: Publish incident reports to /.well-known/ + id: publish + working-directory: out + run: | + set -euo pipefail + put() { + aws s3api put-object --bucket "${SITE_BUCKET}" --key ".well-known/$1" --body "$1" \ + --content-type "$2" --cache-control "public, max-age=300" --query 'ETag' --output text > /dev/null + echo "published .well-known/$1" + } + # Every report first, the log that lists them last. + for f in incident-INC-*.json; do + put "${f%.json}.view.md" "text/markdown; charset=utf-8" + put "$f" "application/json" + put "${f%.json}.bundle" "application/json" + done + put incident-deliveries.view.md "text/markdown; charset=utf-8" + put incident-deliveries.json "application/json" + put incident-deliveries.bundle "application/json" + put incident-reports.md "text/markdown; charset=utf-8" + put incident-reports.view.md "text/markdown; charset=utf-8" + put incident-reports.bundle "application/json" + put incident-reports.json "application/json" + + - name: Invalidate CloudFront cache (incident paths only) + env: + DISTRIBUTION_ID: ${{ secrets.CLOUDFRONT_DISTRIBUTION_ID }} + run: | + set -euo pipefail + aws cloudfront create-invalidation --distribution-id "${DISTRIBUTION_ID}" \ + --paths "/.well-known/incident-*" --query 'Invalidation.Id' --output text + + - name: Assert the published incident log is fresh at the edge + run: | + set -euo pipefail + python3 scripts/check-evidence-freshness.py \ + --url "${SITE_ORIGIN}/.well-known/incident-reports.json" \ + --expect-sha256 "$(sha256sum out/incident-reports.json | awk '{print $1}')" \ + --retries 12 --retry-delay 20 + + # Last, so an overdue report is published (the log says what is late) and + # still fails the run. The watchdog pages on the same list independently. + - name: Incident report clocks (fail when a report is due and missing) + id: clock + if: ${{ !cancelled() && steps.build.outcome == 'success' }} + run: python3 scripts/build-incident-report.py --check out/incident-reports.json + + alert: + name: Alert on incident reporting + runs-on: ubuntu-latest + needs: [report] + if: always() && needs.report.result == 'failure' + permissions: + contents: read + issues: write + steps: + - name: Raise or update the incident-reporting issue + uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0 + env: + CLOCK: ${{ needs.report.outputs.clock }} + PUBLISH: ${{ needs.report.outputs.publish }} + with: + script: | + const TITLE = 'Incident reporting: a report is overdue or was not published'; + const runUrl = `${context.payload.repository.html_url}/actions/runs/${context.runId}`; + const clock = process.env.CLOCK || 'not reached'; + const publish = process.env.PUBLISH || 'not reached'; + const runbook = `${context.payload.repository.html_url}/blob/main/docs/incident-response.md#reporting-fedramp-reportable-incidents-iec`; + const body = [ + `The incident reports workflow failed ([run](${runUrl}), trigger \`${context.eventName}\`).`, + ``, + `| | |`, `|---|---|`, + `| Report clocks | \`${clock}\` |`, + `| Publish | \`${publish}\` |`, + ``, + clock === 'failure' + ? `**A FedRAMP incident report is past its Class C deadline.** The "Incident report clocks" step names each one. Record the report (or open the incident) in data/incidents.json and push; this workflow publishes it.` + : `**The reports were not built or published.** Check the failing step. If "Configure AWS credentials" failed, the incident-reports role or the AWS_INCIDENT_REPORTS_ROLE_ARN variable is missing (infrastructure/bootstrap/incident-reports.tf).`, + ``, + `Runbook: ${runbook}. This issue is reused; each failure adds a comment.`, + ].join('\n'); + const existing = await github.paginate(github.rest.issues.listForRepo, { + owner: context.repo.owner, repo: context.repo.repo, state: 'all', per_page: 100, + labels: 'incident-reporting', + }); + const match = existing.filter(i => i.title === TITLE && !i.pull_request) + .sort((a, b) => (a.state === b.state ? a.number - b.number : a.state === 'open' ? -1 : 1))[0]; + if (match) { + if (match.state === 'closed') { + await github.rest.issues.update({ owner: context.repo.owner, repo: context.repo.repo, + issue_number: match.number, state: 'open' }); + } + await github.rest.issues.createComment({ owner: context.repo.owner, repo: context.repo.repo, + issue_number: match.number, body }); + } else { + await github.rest.issues.create({ owner: context.repo.owner, repo: context.repo.repo, title: TITLE, + body, labels: ['compliance', 'incident-reporting', 'urgent'], assignees: [context.repo.owner] }); + } diff --git a/.github/workflows/package-maintenance.yml b/.github/workflows/package-maintenance.yml new file mode 100644 index 00000000..53e2ece3 --- /dev/null +++ b/.github/workflows/package-maintenance.yml @@ -0,0 +1,548 @@ +# ============================================================================= +# GitHub Actions Workflow: Certification Package Maintenance (CPO-CSX-CPM) +# ============================================================================= +# FedRAMP 20x Class C: keep the certification package up to date at least every +# two weeks (CPO-CSX-CPM), keep daily KSI metric data (SDR-CSX-KMT), and issue +# the Ongoing Certification Report on its calendar date with a snapshot of the +# package (CCM-OCR-AVL/SOR, CDS-CSO-HAD). The deploy is behind a human reviewer +# and keeps none of those dates, so this runs daily, unattended: +# +# daily cron, or by hand, or called by every deploy after it succeeds +# -> fetch the published inputs and verify every signature (fail closed): +# the KSI signal (deploy), the VDR (deploy or nightly), and the copies +# this run replaces (CPO, SDR, OCR: deploy or this workflow) +# -> check out the commit the published inventory was built from, so the +# rebuild describes the deployed system, not an undeployed main +# -> rebuild the SDR (one more daily metric point), the OCR and the CPO, +# each validated against FedRAMP's schema; write the review calendar; +# on or after an issue date not yet issued, freeze that report and +# snapshot the package (scripts/issue-ocr.py) +# -> FedRAMP ID, sensitivity and redaction gates; sign; attest the SDR +# -> refuse to overwrite an issued report; publish; invalidate; verify the +# edge serves what was built +# +# THE TRADE, as for the evidence nightly: an unattended production write. Its +# role (infrastructure/bootstrap/package-maintenance.tf, operator-applied) can +# put the package objects listed there and invalidate the CDN, and nothing else: +# no Terraform, no website sync, no delete, no read. +# ============================================================================= + +name: Certification Package Maintenance + +on: + workflow_dispatch: + # Called by every deploy (deploy-with-opa.yml, job package-maintainer) after + # the deploy job succeeds, so a green deploy proves this maintainer verifies, + # rebuilds and publishes with its own role. + workflow_call: + secrets: + CLOUDFRONT_DISTRIBUTION_ID: + required: true + schedule: + - cron: '37 9 * * *' + +concurrency: + group: package-maintenance + cancel-in-progress: false + +permissions: + contents: read + +env: + AWS_REGION: us-east-2 + OPA_VERSION: 1.18.2 + OPA_SHA256: 9903e5125ac281104f2c4b7371d10cc3b74a98933743fcbfc174f9bf0ab20de8 + SITE_BUCKET: samaydlette.com + SITE_ORIGIN: https://samaydlette.com + COSIGN_OIDC_ISSUER: https://token.actions.githubusercontent.com + ID_DEPLOY: https://github.com/sam-aydlette/samaydlette.com/.github/workflows/deploy-with-opa.yml@refs/heads/main + ID_NIGHTLY: https://github.com/sam-aydlette/samaydlette.com/.github/workflows/evidence-nightly.yml@refs/heads/main + ID_MAINTENANCE: https://github.com/sam-aydlette/samaydlette.com/.github/workflows/package-maintenance.yml@refs/heads/main + +jobs: + maintain: + name: Rebuild, sign and publish the certification package + runs-on: ubuntu-latest + timeout-minutes: 25 + # No required reviewer: the dates run while nobody is awake. The role this + # environment can assume writes only the package objects. + environment: package-maintenance + outputs: + publish: ${{ steps.publish.outcome }} + permissions: + contents: read + id-token: write + # The Annual Security Review reads the pipeline's run history (gh run list). + actions: read + + steps: + - name: Checkout code + uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 + with: + fetch-depth: 0 + + - name: Install cosign + uses: sigstore/cosign-installer@7e8b541eb2e61bf99390e1afd4be13a184e9ebc5 # v3.10.1 + + - name: Setup OPA + run: | + curl -fL --retry 5 --retry-delay 5 --connect-timeout 10 --max-time 120 \ + -o opa "https://openpolicyagent.org/downloads/v${{ env.OPA_VERSION }}/opa_linux_amd64_static" + echo "${{ env.OPA_SHA256 }} opa" | sha256sum -c - + chmod 755 ./opa + sudo mv opa /usr/local/bin + + # Everything arrives over the public internet, so nothing is used before its + # signature checks out against the workflows allowed to have signed it. The + # published CPO, SDR and OCR are the copies this run replaces: they must be + # signed by the deploy or by this workflow, or the run stops. + - name: Fetch and verify the published package and its inputs + run: | + set -euo pipefail + mkdir -p work + cd work + fetch() { curl -sfL --retry 3 --retry-delay 5 -o "$1" "${SITE_ORIGIN}/.well-known/$1"; } + verify() { # verify ... + f="$1"; b="$2"; shift 2 + for id in "$@"; do + if cosign verify-blob --bundle "$b" --certificate-identity "$id" \ + --certificate-oidc-issuer "${COSIGN_OIDC_ISSUER}" "$f" 2>/dev/null; then return 0; fi + done + echo "::error::$f does not verify against the identities allowed to sign it; refusing to use it" + return 1 + } + fetch ksi-signal.json; fetch ksi-signal.bundle + verify ksi-signal.json ksi-signal.bundle "$ID_DEPLOY" + for a in vdr-report vdr-detail-report vdr-accepted-vulnerabilities vdr-history; do + fetch "$a.json"; fetch "$a.bundle"; verify "$a.json" "$a.bundle" "$ID_DEPLOY" "$ID_NIGHTLY" + done + for a in security-decision-record certification-package-overview ongoing-certification-report; do + fetch "$a.json"; fetch "$a.bundle"; fetch "$a.md" + verify "$a.json" "$a.bundle" "$ID_DEPLOY" "$ID_MAINTENANCE" + done + for a in boundary-map policy-index availability trust-center fedramp-certification-reports package-submission-log; do + fetch "$a.json"; fetch "$a.bundle"; verify "$a.json" "$a.bundle" "$ID_DEPLOY" + done + fetch iiw.csv; fetch iiw.bundle; verify iiw.csv iiw.bundle "$ID_DEPLOY" + # The simulated assessor's signed set: verified by the builders below + # (scripts/_assessor.py) against the pinned assessor identity. + fetch simulated-assessment.json || rm -f simulated-assessment.json + fetch simulated-assessment.bundle || rm -f simulated-assessment.bundle + # The issue index exists once this workflow has run; before that, none. + # Only a definite "not there" starts a new one; any other failure stops + # the run rather than rebuild the index without its earlier issues. + code=$(curl -s -o /dev/null -w '%{http_code}' "${SITE_ORIGIN}/.well-known/ocr-issues.json") + if [ "$code" = "404" ] || [ "$code" = "403" ]; then + echo "No published issue index yet; starting one." + else + fetch ocr-issues.json; fetch ocr-issues.bundle + verify ocr-issues.json ocr-issues.bundle "$ID_MAINTENANCE" + fi + # Verified in-band by build-sdr.py against the committed runtime key. + fetch ksi-signal-runtime.json || rm -f ksi-signal-runtime.json + # The scheduled reviews' records, verified in-band by build-sdr.py against + # their publishers (scripts/_signers.py); one not published yet is not counted. + for a in vdr-audit-log-review vdr-recovery-exercises security-reviews; do + if ! { fetch "$a.json" && fetch "$a.bundle"; }; then rm -f "$a.json" "$a.bundle"; fi + done + SIGNAL_COMMIT=$(jq -r '.provenance.source.commit' ksi-signal.json) + if ! printf '%s' "$SIGNAL_COMMIT" | grep -qE '^[0-9a-f]{40}$'; then + echo "::error::published inventory carries a malformed commit id"; exit 1 + fi + echo "SIGNAL_COMMIT=${SIGNAL_COMMIT}" >> "$GITHUB_ENV" + + # Rebuild at the deployed commit: the records, registers and builders that + # the published inventory was built with. A commit that is not on main is + # not this repository's deployed state. + - name: Check out the deployed commit + run: | + set -euo pipefail + git merge-base --is-ancestor "$SIGNAL_COMMIT" origin/main || { + echo "::error::the published inventory's commit is not on main"; exit 1; } + git checkout -q --detach "$SIGNAL_COMMIT" + for f in scripts/issue-ocr.py scripts/build-cpo.py scripts/build-ocr.py scripts/build-sdr.py; do + [ -f "$f" ] || { echo "::error::the deployed commit has no $f"; exit 1; } + done + + - name: Rebuild the SDR, OCR and CPO at the deployed commit + working-directory: infrastructure + run: | + set -euo pipefail + W=../work + mkdir -p out + # The simulated assessor's set, for the SDR, the T74 re-check and the + # CPO summary. A deployed commit from before the assessor existed has + # builders that take no such argument; it is rebuilt as it was deployed. + # shellcheck disable=SC2086 # $ASSESSMENT is a word list by design + ASSESSMENT="" + if grep -q -- '--assessment-bundle' ../scripts/build-cpo.py; then + ASSESSMENT="--assessment $W/simulated-assessment.json --assessment-bundle $W/simulated-assessment.bundle" + fi + # The set covers the deployed commit and the signal the deploy's SDR + # (signature verified above) states it validated; any other is refused. + if grep -q -- '--assessment-signal-id' ../scripts/build-cpo.py; then + ASSESSED=$(jq -r '.providerExtensions.assessmentCoverage.signalId // empty' "$W/security-decision-record.json") + if ! printf '%s' "$ASSESSED" | grep -qE '^[0-9a-f-]{36}$'; then + echo "::error::the published SDR does not state which KSI signal its assessment covered"; exit 1 + fi + ASSESSMENT="$ASSESSMENT --assessment-commit $SIGNAL_COMMIT --assessment-signal-id $ASSESSED" + fi + # FRC-CSX-VVK: the VDR's signature (verified above) for the dependency-scan + # method, and a KSI short of two automated methods without an accepted + # decision fails the run. Older deployed builders take neither. + VVK="" + if grep -q -- '--require-two-methods' ../scripts/build-sdr.py; then + VVK="--vdr-bundle vdr-report.bundle --vdr-identity $ID_DEPLOY --vdr-identity $ID_NIGHTLY --require-two-methods" + fi + # The runtime method counts only when the runtime signal re-validated + # the deployed inventory (the same binding the deploy applies). + if grep -q -- '--runtime-commit' ../scripts/build-sdr.py; then + VVK="$VVK --runtime-commit $SIGNAL_COMMIT" + fi + # The scheduled reviews' records count for their KSIs (FRC-CSX-VVK) when + # their signatures verify; an older deployed builder takes no such argument. + if grep -q -- '--scheduled-record' ../scripts/build-sdr.py; then + for k in audit-log-review:vdr-audit-log-review recovery-exercise:vdr-recovery-exercises \ + security-review:security-reviews; do + f="${k#*:}" + if [ -f "$W/$f.json" ] && [ -f "$W/$f.bundle" ]; then + VVK="$VVK --scheduled-record ${k%%:*}=$W/$f.json" + fi + done + fi + cp "$W/ksi-signal.json" "$W/vdr-report.json" "$W/vdr-report.bundle" . + [ -f "$W/ksi-signal-runtime.json" ] && cp "$W/ksi-signal-runtime.json" . + python3 ../scripts/build-sdr.py \ + --catalog schemas/ksi-catalog.json --ksi-signal ksi-signal.json \ + --runtime-signal ksi-signal-runtime.json --vdr vdr-report.json --profile ../data/system-profile.json \ + --previous-sdr "$W/security-decision-record.json" \ + --output out/security-decision-record.json --md-output out/security-decision-record.md \ + $VVK \ + $ASSESSMENT + python3 ../scripts/_assessor.py --sdr out/security-decision-record.json \ + $ASSESSMENT + python3 ../scripts/build-ocr.py --vdr vdr-report.json --decisions ../data/decisions.json \ + --ksi-signal ksi-signal.json --scn-register ../docs/scn/scn-register.csv \ + --previous "$W/ongoing-certification-report.json" \ + --output out/ongoing-certification-report.json --md-output out/ongoing-certification-report.md + python3 ../scripts/build-cpo.py --offering ../data/cds/offering.json --profile ../data/system-profile.json \ + --ksi-signal ksi-signal.json --previous-cpo "$W/certification-package-overview.json" \ + --output out/certification-package-overview.json --md-output out/certification-package-overview.md \ + $ASSESSMENT + python3 ../scripts/_ccm.py --ics out/quarterly-review.ics + + # The snapshot is the package as published at issue time: the verified + # copies fetched above, with this run's rebuilt CPO, SDR and OCR and their + # signatures (signed first, so the snapshot holds signed files). + - name: Sign the rebuilt reports + working-directory: infrastructure/out + run: | + set -euo pipefail + for a in security-decision-record certification-package-overview ongoing-certification-report; do + cosign sign-blob --yes --new-bundle-format --bundle "$a.bundle" "$a.json" + done + + - name: Issue the quarterly report when due (frozen, with a snapshot) + working-directory: infrastructure + run: | + set -euo pipefail + W=../work + cp out/*.json out/*.md out/*.bundle "$W/" + prev="" + [ -f "$W/ocr-issues.json" ] && prev="--previous-index $W/ocr-issues.json" + # shellcheck disable=SC2086 + python3 ../scripts/issue-ocr.py --work "$W" --out out $prev --new-files out/issued.txt \ + --vdr vdr-report.json --ksi-signal ksi-signal.json + cat out/issued.txt + + # CCM-QTR-MTG/RTR/SRR, CCM-OCR-FBM/AFS: on each review date, the Quarterly + # Review is held with simulated attendees (DEC-194: the operator engages no + # real party) and published, never rewritten; the index is republished on + # every run. Its frozen report must match the sha256 the issue index records. + - name: Hold the Quarterly Review when due (simulated attendees) + working-directory: infrastructure + run: | + set -euo pipefail + W=../work + : > out/reviews.txt + # A deployed commit from before automated reviews has no generator; it + # is maintained as it was deployed (the deploy of a later commit runs it). + [ -f ../scripts/hold-quarterly-review.py ] || { echo "::notice::the deployed commit predates automated Quarterly Reviews"; exit 0; } + fetch() { curl -sfL --retry 3 --retry-delay 5 -o "$W/$1" "${SITE_ORIGIN}/.well-known/$1"; } + prev="" + code=$(curl -s -o /dev/null -w '%{http_code}' "${SITE_ORIGIN}/.well-known/quarterly-reviews.json") + if [ "$code" = "404" ] || [ "$code" = "403" ]; then + echo "No published review index yet; starting one." + elif [ "$code" = "200" ]; then + fetch quarterly-reviews.json; fetch quarterly-reviews.bundle + cosign verify-blob --bundle "$W/quarterly-reviews.bundle" --certificate-identity "$ID_MAINTENANCE" \ + --certificate-oidc-issuer "${COSIGN_OIDC_ISSUER}" "$W/quarterly-reviews.json" + prev="--previous-index $W/quarterly-reviews.json" + else + echo "::error::quarterly-reviews.json answered HTTP $code: refusing to rebuild the index without it"; exit 1 + fi + # The frozen reports a due review reads; checked against the verified + # issue index's sha256 by the script. + for d in $(jq -r '.issues[].issueDate' out/ocr-issues.json); do + [[ "$d" =~ ^[0-9]{4}-[0-9]{2}-[0-9]{2}$ ]] || { echo "::error::malformed issue date in the issue index"; exit 1; } + [ -f "out/ocr-issue-$d.json" ] || fetch "ocr-issue-$d.json" || true + done + # shellcheck disable=SC2086 + python3 ../scripts/hold-quarterly-review.py --ocr-index out/ocr-issues.json \ + --issues-dir out --issues-dir "$W" $prev --out out --new-files out/reviews.txt + cat out/reviews.txt >> out/issued.txt + + # KSI-PIY-RIS/RES, KSI-SVC-EIS, KSI-INR-RPI, PL-4 (DEC-195: no review meeting): + # on its due date the Annual Security Review is generated from the deployed + # commit's data and signed off by a simulated reviewer; a failing item fails + # the run and is held again once fixed. On every run the rules of behavior's + # current sha256 is acknowledged by simulated personnel if it changed. The + # index is republished every run; a held review is never rewritten. + - name: Hold the Annual Security Review when due (simulated sign-off) + working-directory: infrastructure + env: + GH_TOKEN: ${{ github.token }} + run: | + set -euo pipefail + W=../work + [ -f ../scripts/hold-security-review.py ] || { echo "::notice::the deployed commit predates the automated security review"; exit 0; } + fetch() { curl -sfL --retry 3 --retry-delay 5 -o "$W/$1" "${SITE_ORIGIN}/.well-known/$1"; } + prev=() + code=$(curl -s -o /dev/null -w '%{http_code}' "${SITE_ORIGIN}/.well-known/security-reviews.json") + if [ "$code" = "200" ]; then + fetch security-reviews.json; fetch security-reviews.bundle + cosign verify-blob --bundle "$W/security-reviews.bundle" --certificate-identity "$ID_MAINTENANCE" \ + --certificate-oidc-issuer "${COSIGN_OIDC_ISSUER}" "$W/security-reviews.json" + prev=(--previous-index "$W/security-reviews.json") + # The last review, for what changed since; checked against the index's sha256 by the script. + last=$(jq -r '.reviews[-1].dueDate // empty' "$W/security-reviews.json") + if [ -n "$last" ]; then + [[ "$last" =~ ^[0-9]{4}-[0-9]{2}-[0-9]{2}$ ]] || { echo "::error::malformed due date in the review index"; exit 1; } + fetch "security-review-$last.json" + fi + elif [ "$code" != "404" ] && [ "$code" != "403" ]; then + echo "::error::security-reviews.json answered HTTP $code: refusing to rebuild the index without it"; exit 1 + fi + gh run list --repo "${{ github.repository }}" --limit 1000 --json workflowName,createdAt,updatedAt > out/runs.json + python3 ../scripts/hold-security-review.py --ksi-signal ksi-signal.json --vdr vdr-report.json \ + --runs out/runs.json "${prev[@]}" --previous-dir "$W" --out out --new-files out/security-new.txt + rm -f out/runs.json + cat out/security-new.txt >> out/issued.txt + + # CDS-CSO-CBF: the complete human-readable view of each JSON republished + # below, parsed back and required to reproduce it, so the views the deploy + # published never drift from the JSON this run replaces. Every JSON or CSV + # issued this run (the frozen report, its snapshot manifest and copies, a + # Quarterly Review) gets its view too, issued and never rewritten with it. + - name: Rebuild the human-readable views (format parity) + working-directory: infrastructure/out + run: | + set -euo pipefail + issued=$(grep -E '\.(json|csv)$' issued.txt || true) + # shellcheck disable=SC2086 # $issued is a word list by design + python3 ../../scripts/build-human-views.py \ + security-decision-record.json certification-package-overview.json ongoing-certification-report.json \ + ocr-issues.json $( [ -f quarterly-reviews.json ] && echo quarterly-reviews.json ) \ + $( [ -f security-reviews.json ] && echo security-reviews.json ) $issued + for f in $issued; do echo "${f%.*}.view.md" >> issued.txt; done + + - name: Gates (FedRAMP ID, redaction) + working-directory: infrastructure/out + run: | + set -euo pipefail + python3 ../../scripts/check-fedramp-id.py security-decision-record.json \ + certification-package-overview.json ongoing-certification-report.json ocr-issues.json \ + $( [ -f quarterly-reviews.json ] && echo quarterly-reviews.json ) \ + $( [ -f security-reviews.json ] && echo security-reviews.json ) \ + $(grep -E '^(ocr-issue-.*\.json|snapshot-.*\.json|quarterly-review-.*\.json|security-review-.*\.json)$' issued.txt || true) + # Every issued file, the snapshot copies under snapshots// included. + # Signatures are Sigstore's output and are not scanned (as in the deploy). + # shellcheck disable=SC2046 + python3 ../../scripts/check-published-redaction.py security-decision-record.json security-decision-record.md \ + certification-package-overview.json certification-package-overview.md \ + ongoing-certification-report.json ongoing-certification-report.md ocr-issues.json quarterly-review.ics \ + security-decision-record.view.md certification-package-overview.view.md \ + ongoing-certification-report.view.md ocr-issues.view.md \ + $( [ -f quarterly-reviews.json ] && echo quarterly-reviews.json quarterly-reviews.view.md ) \ + $( [ -f security-reviews.json ] && echo security-reviews.json security-reviews.view.md ) \ + $(grep -E '^(ocr-issue-|snapshot-|snapshots/|quarterly-review-|security-review-)' issued.txt | grep -vE '\.(bundle|intoto\.jsonl)$' || true) + + - name: Sign the issue index and new issues; attest the SDR + working-directory: infrastructure/out + run: | + set -euo pipefail + cosign sign-blob --yes --new-bundle-format --bundle ocr-issues.bundle ocr-issues.json + if [ -f quarterly-reviews.json ]; then + cosign sign-blob --yes --new-bundle-format --bundle quarterly-reviews.bundle quarterly-reviews.json + fi + if [ -f security-reviews.json ]; then + cosign sign-blob --yes --new-bundle-format --bundle security-reviews.bundle security-reviews.json + fi + for f in $(grep -E '^(ocr-issue-.*|snapshot-.*|quarterly-review-.*|security-review-.*)\.json$' issued.txt || true); do + cosign sign-blob --yes --new-bundle-format --bundle "${f%.json}.bundle" "$f" + echo "${f%.json}.bundle" >> issued.txt + done + python3 ../../scripts/build-provenance.py --ksi-signal ../ksi-signal.json \ + --generator ../../scripts/build-sdr.py --output sdr.predicate.json + cosign attest-blob --yes --new-bundle-format --predicate sdr.predicate.json --type slsaprovenance1 \ + --bundle security-decision-record.json.intoto.jsonl security-decision-record.json + cosign verify-blob-attestation --new-bundle-format --bundle security-decision-record.json.intoto.jsonl \ + --type slsaprovenance1 --certificate-identity "$ID_MAINTENANCE" \ + --certificate-oidc-issuer "${COSIGN_OIDC_ISSUER}" security-decision-record.json + python3 ../../scripts/verify-attestation.py --bundle security-decision-record.json.intoto.jsonl \ + --artifact security-decision-record.json --ksi-signal ../ksi-signal.json + + - name: Configure AWS credentials + uses: aws-actions/configure-aws-credentials@e1253824e5c10ff9df46874f81ed3ec929e19cfd # v6.3.0 + timeout-minutes: 6 + with: + # Defined in infrastructure/bootstrap/package-maintenance.tf; the deploy's + # preflight fails while it is unset. + role-to-assume: ${{ vars.AWS_PACKAGE_MAINTENANCE_ROLE_ARN }} + aws-region: ${{ env.AWS_REGION }} + retry-max-attempts: 5 + + - name: Publish the certification package to /.well-known/ + id: publish + working-directory: infrastructure/out + run: | + set -euo pipefail + put() { + aws s3api put-object --bucket "${SITE_BUCKET}" --key ".well-known/$1" --body "$1" \ + --content-type "$2" --cache-control "public, max-age=300" --query 'ETag' --output text > /dev/null + echo "published .well-known/$1" + } + ctype() { + case "$1" in + *.md) echo "text/markdown; charset=utf-8" ;; + *.ics) echo "text/calendar; charset=utf-8" ;; + *.csv) echo "text/csv" ;; + *) echo "application/json" ;; + esac + } + # An issued report and its snapshot are never rewritten. + while read -r f; do + [ -n "$f" ] || continue + code=$(curl -s -o /dev/null -w '%{http_code}' "${SITE_ORIGIN}/.well-known/$f") + if [ "$code" != "404" ] && [ "$code" != "403" ]; then + echo "::error::.well-known/$f is already served (HTTP $code): issued files are never overwritten"; exit 1 + fi + done < issued.txt + while read -r f; do [ -n "$f" ] && put "$f" "$(ctype "$f")"; done < issued.txt + for a in security-decision-record certification-package-overview ongoing-certification-report; do + put "$a.md" "text/markdown; charset=utf-8" + put "$a.view.md" "text/markdown; charset=utf-8" + put "$a.bundle" application/json + put "$a.json" application/json + done + put security-decision-record.json.intoto.jsonl application/json + put quarterly-review.ics "text/calendar; charset=utf-8" + put ocr-issues.view.md "text/markdown; charset=utf-8" + put ocr-issues.bundle application/json + put ocr-issues.json application/json + if [ -f quarterly-reviews.json ]; then + put quarterly-reviews.view.md "text/markdown; charset=utf-8" + put quarterly-reviews.bundle application/json + put quarterly-reviews.json application/json + fi + if [ -f security-reviews.json ]; then + put security-reviews.view.md "text/markdown; charset=utf-8" + put security-reviews.bundle application/json + put security-reviews.json application/json + fi + + - name: Invalidate CloudFront cache (package paths only) + env: + DISTRIBUTION_ID: ${{ secrets.CLOUDFRONT_DISTRIBUTION_ID }} + run: | + set -euo pipefail + aws cloudfront create-invalidation --distribution-id "${DISTRIBUTION_ID}" \ + --paths "/.well-known/security-decision-record*" "/.well-known/certification-package-overview*" \ + "/.well-known/ongoing-certification-report*" "/.well-known/ocr-issue*" \ + "/.well-known/quarterly-review*" "/.well-known/security-review*" --query 'Invalidation.Id' --output text + + - name: Assert the edge serves the rebuilt package + run: | + set -euo pipefail + for a in security-decision-record certification-package-overview ongoing-certification-report ocr-issues \ + quarterly-reviews security-reviews; do + [ -f "infrastructure/out/$a.json" ] || continue + python3 scripts/check-evidence-freshness.py --url "${SITE_ORIGIN}/.well-known/$a.json" \ + --expect-sha256 "$(sha256sum "infrastructure/out/$a.json" | awk '{print $1}')" \ + --retries 12 --retry-delay 20 + done + + # CCM-QTR-MTG: the index the edge now serves (asserted byte-identical above) + # must list a review for every review date already passed. This run is + # called by every deploy and runs daily, so a missed review fails both. + - name: No Quarterly Review overdue (published index) + run: | + set -euo pipefail + [ -f scripts/check-quarterly-review.py ] || { echo "::notice::the deployed commit predates automated Quarterly Reviews"; exit 0; } + python3 scripts/check-quarterly-review.py --index infrastructure/out/quarterly-reviews.json + + + # DEC-195: the Annual Security Review index the edge now serves lists a + # review for every due date passed, and acknowledges the deployed rules of + # behavior (PL-4); the nightly's recovery exercises are not overdue (its + # index counts only when the nightly's signature verifies; before the first + # nightly after the first deploy it is not published yet, and the nightly's + # own check and the evidence watchdog cover that). Called by every deploy, + # so either one missing fails the deploy. + - name: Scheduled reviews held and not overdue (published indexes) + run: | + set -euo pipefail + [ -f scripts/check-scheduled-review.py ] || { echo "::notice::the deployed commit predates the automated scheduled reviews"; exit 0; } + python3 scripts/check-scheduled-review.py --review security-review \ + --index infrastructure/out/security-reviews.json --rules-of-behavior docs/rules-of-behavior.md + code=$(curl -s -o rx-index.json -w '%{http_code}' "${SITE_ORIGIN}/.well-known/vdr-recovery-exercises.json") + case "$code" in + 200) + curl -sfL --retry 3 -o rx-index.bundle "${SITE_ORIGIN}/.well-known/vdr-recovery-exercises.bundle" + cosign verify-blob --bundle rx-index.bundle --certificate-identity "$ID_NIGHTLY" \ + --certificate-oidc-issuer "${COSIGN_OIDC_ISSUER}" rx-index.json + python3 scripts/check-scheduled-review.py --review recovery-exercise --index rx-index.json ;; + 403|404) echo "::notice::no recovery exercise published yet; the evidence nightly holds the first and fails while one is overdue" ;; + *) echo "::error::vdr-recovery-exercises.json answered HTTP $code"; exit 1 ;; + esac + alert: + name: Alert on package maintenance + runs-on: ubuntu-latest + needs: [maintain] + if: always() && needs.maintain.result == 'failure' + permissions: + contents: read + issues: write + steps: + - name: Raise or update the package-maintenance issue + uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0 + env: + PUBLISH: ${{ needs.maintain.outputs.publish }} + with: + script: | + const TITLE = 'Certification package maintenance failed'; + const runUrl = `${context.payload.repository.html_url}/actions/runs/${context.runId}`; + const body = [ + `The certification package maintenance run failed ([run](${runUrl}), trigger \`${context.eventName}\`, publish \`${process.env.PUBLISH || 'not reached'}\`).`, + ``, + `Until it succeeds, the CPO, SDR and OCR are not refreshed, a due Ongoing Certification Report is not issued, and the evidence watchdog pages when they pass their 14-day window (CPO-CSX-CPM). If "Configure AWS credentials" failed, the role or the AWS_PACKAGE_MAINTENANCE_ROLE_ARN variable is missing (infrastructure/bootstrap/package-maintenance.tf). If a fetch or verify failed, a published input is not signed by the workflow allowed to sign it: investigate before re-running.`, + ``, + `This issue is reused; each failure adds a comment.`, + ].join('\n'); + const existing = await github.paginate(github.rest.issues.listForRepo, { + owner: context.repo.owner, repo: context.repo.repo, state: 'all', per_page: 100, + labels: 'package-maintenance', + }); + const match = existing.filter(i => i.title === TITLE && !i.pull_request) + .sort((a, b) => (a.state === b.state ? a.number - b.number : a.state === 'open' ? -1 : 1))[0]; + if (match) { + if (match.state === 'closed') { + await github.rest.issues.update({ owner: context.repo.owner, repo: context.repo.repo, + issue_number: match.number, state: 'open' }); + } + await github.rest.issues.createComment({ owner: context.repo.owner, repo: context.repo.repo, + issue_number: match.number, body }); + } else { + await github.rest.issues.create({ owner: context.repo.owner, repo: context.repo.repo, + title: TITLE, body, labels: ['package-maintenance'] }); + } diff --git a/.github/workflows/scn-deadlines.yml b/.github/workflows/scn-deadlines.yml new file mode 100644 index 00000000..424efff6 --- /dev/null +++ b/.github/workflows/scn-deadlines.yml @@ -0,0 +1,68 @@ +# ============================================================================= +# SCN DEADLINE CHECK (SCN-ADP-NTF, SCN-TRF-NAF/NAV/UPD, SCN-CSO-EMG) +# ============================================================================= +# Once a business day, compares the published evaluation log and notification +# index with the register on main and fails on anything late and outstanding: +# a change named as adaptive/transformative/emergency with no record by its +# deadline, a notice not yet published after its deadline, or a transformative +# change's documentation not updated within 30 business days. The rules are in +# scripts/_scn.py (tests/test_scn.py). A failure raises or updates one GitHub +# issue, the same paper trail the evidence nightly uses. +# +# Reads only public URLs and this checkout: no AWS credentials, no writes +# outside the issue. +# ============================================================================= + +name: SCN Deadlines + +on: + schedule: + - cron: "17 13 * * 1-5" + workflow_dispatch: + +permissions: + contents: read + +jobs: + deadlines: + runs-on: ubuntu-latest + timeout-minutes: 5 + outputs: + result: ${{ steps.check.outcome }} + steps: + - name: Checkout code + uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 + + - name: Check SCN deadlines + id: check + run: python3 scripts/check-scn-deadlines.py + + alert: + name: Raise the overdue-SCN issue + runs-on: ubuntu-latest + needs: [deadlines] + if: always() && needs.deadlines.result == 'failure' + permissions: + issues: write + steps: + - name: Raise or update the overdue-SCN issue + uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0 + with: + script: | + const TITLE = 'Significant Change Notification overdue'; + const runUrl = `${context.payload.repository.html_url}/actions/runs/${context.runId}`; + const body = [ + 'The scheduled SCN deadline check failed: a significant change has a record or notice past its deadline.', + '', + `The "Check SCN deadlines" step in [this run](${runUrl}) names each item. Add the record to docs/scn/scn-register.csv and deploy, which publishes it; a notice is given when the deploy publishes it.`, + ].join('\n'); + const open = (await github.paginate(github.rest.issues.listForRepo, { + owner: context.repo.owner, repo: context.repo.repo, state: 'open', per_page: 100, + })).filter(i => i.title === TITLE && !i.pull_request); + if (open.length) { + await github.rest.issues.createComment({ + owner: context.repo.owner, repo: context.repo.repo, issue_number: open[0].number, body, + }); + } else { + await github.rest.issues.create({ owner: context.repo.owner, repo: context.repo.repo, title: TITLE, body }); + } diff --git a/.github/workflows/scn-tag.yml b/.github/workflows/scn-tag.yml index 7492dcbe..54a6d7b4 100644 --- a/.github/workflows/scn-tag.yml +++ b/.github/workflows/scn-tag.yml @@ -1,16 +1,19 @@ # ============================================================================= -# SCN TAG VALIDATOR +# SCN EVALUATION GATE (SCN-CSO-EVA) # ============================================================================= -# Enforces FedRAMP 20x Significant Change Notification rules SCN-CSO-EVA and -# SCN-CSO-MAR by reading the SCN-Type tag from either the PR description (on -# pull_request events) or the commit message (on push events). The git history -# is the SCN audit record (SCN-CSO-MAR), and this gate ensures every entry in -# that record carries a recognized SCN-Type categorization. +# Every change carries an explicit significant-change evaluation: an SCN-Type +# line, a one-line SCN-Rationale and, for adaptive, transformative and emergency +# changes, the SCN-Record it will be documented in. The pull request's +# description is read on pull_request events; on a push to main, the merged +# pull request's description (or the commit message for a direct push). # -# Categorization defaults to routine-recurring per docs/policies/cm-policy.md -# when no SCN-Type line is present. The validator only fails on a malformed -# SCN-Type value; missing tags are treated as the default. Operators must -# explicitly upgrade the categorization for Adaptive or Transformative changes. +# There is no default. A missing type, a missing or placeholder rationale, or an +# unrecognized value fails. class-change always fails: it is a new +# certification, not a significant change. A transformative change fails until +# its initial and final plans have been published 30 and 10 business days +# (SCN-TRF-NIP/NFP). The rules live in scripts/_scn.py and are unit-tested in +# tests/test_scn.py; the deploy writes every merged evaluation to the +# append-only log at /.well-known/scn-evaluations.json (SCN-CSO-MAR). # ============================================================================= name: SCN Tag @@ -28,41 +31,33 @@ permissions: jobs: scn-tag: runs-on: ubuntu-latest + timeout-minutes: 5 steps: - - name: Validate SCN-Type tag + - name: Checkout code + uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 + + # Untrusted text (a PR description, a commit message) reaches the script + # only through the environment, never by ${{ }} interpolation into shell. + - name: Validate the SCN evaluation env: PR_BODY: ${{ github.event.pull_request.body }} COMMIT_MSG: ${{ github.event.head_commit.message }} EVENT_NAME: ${{ github.event_name }} + GH_TOKEN: ${{ github.token }} + REPO: ${{ github.repository }} run: | set -euo pipefail if [ "${EVENT_NAME}" = "pull_request" ]; then - content="${PR_BODY:-}" + SCN_TEXT="${PR_BODY:-}" source_label="PR description" else - content="${COMMIT_MSG:-}" + SCN_TEXT="${COMMIT_MSG:-}" source_label="commit message" + pr=$(printf '%s\n' "${SCN_TEXT}" | head -n1 | sed -nE 's/^Merge pull request #([0-9]+) from .*/\1/p') + if [ -n "${pr}" ]; then + SCN_TEXT=$(gh api "repos/${REPO}/pulls/${pr}" --jq '.body // ""') + source_label="description of merged PR #${pr}" + fi fi - # Extract the SCN-Type line if present. Match optional leading hashes - # (Markdown heading) and case-insensitive 'SCN-Type:' prefix. - tag=$(printf '%s\n' "${content}" | grep -iE '^[[:space:]]*##?[[:space:]]*SCN-Type:' | head -n1 | sed -E 's/^[[:space:]]*##?[[:space:]]*SCN-Type:[[:space:]]*//I' | tr -d '[:space:]' || true) - case "${tag}" in - adaptive|routine-recurring|transformative) - echo "SCN-Type: ${tag} (from ${source_label})" - ;; - emergency) - # Emergency-change procedure per CR26 SCN-CSO-EMG. The change itself - # is permitted to bypass the formal SCN flow; the retroactive - # documentation is required per the IR runbook. - echo "::warning::SCN-Type: emergency (from ${source_label}). Emergency-change procedure invoked per SCN-CSO-EMG; retroactive SCN documentation required within 5 business days. See docs/incident-response.md." - ;; - "") - # Per CM policy default: missing tag = routine-recurring. This is the - # documented default for sole-operator direct pushes; do not fail. - echo "::notice::No SCN-Type line in ${source_label}; defaulting to routine-recurring per docs/policies/cm-policy.md." - ;; - *) - echo "::error::SCN-Type '${tag}' in ${source_label} is not a recognized value. Must be one of: adaptive | routine-recurring | transformative | emergency. See SCN-CSO-EVA / SCN-CSO-EMG in docs/policies/cm-policy.md." - exit 1 - ;; - esac + export SCN_TEXT + python3 scripts/scn-evaluate.py --text-env SCN_TEXT --source "${source_label}" diff --git a/.github/workflows/simulated-assessor.yml b/.github/workflows/simulated-assessor.yml new file mode 100644 index 00000000..a794cf9b --- /dev/null +++ b/.github/workflows/simulated-assessor.yml @@ -0,0 +1,129 @@ +# ============================================================================= +# SIMULATED ASSESSOR — "Totally Real Assessment Services, LLC (simulated)" +# ============================================================================= +# SIMULATED. Not independent of the provider, not a FedRAMP Recognized +# independent assessment service, no FedRAMP assessor ID. It stands in for an +# assessor so the assessor port (IVV-CSO-FIA/ICP, IVV-CSX-AIA, CPO-CSO-OSA, +# SDR-CSO-FRR) is exercised end to end on every deploy. +# +# The deploy calls this as a reusable workflow twice: before its deploy job +# (phase pre-deploy: the commit being deployed and the published state it +# replaces; the SDR is built from this set) and after the deploy has published +# (phase post-deploy: the just-published state, which must carry this commit). +# Each set names the commit and KSI signal it covered, and the provider refuses +# it for any other. Because it is a reusable workflow, the Sigstore certificate that signs its record names +# THIS file (job_workflow_ref), not deploy-with-opa.yml: the assessor signs +# under its own identity, which infrastructure/keys/assessor-identity.json pins. +# It holds no AWS credentials and reads only public URLs and the repository. +# +# It follows the provider's assessor guide (scripts/build-assessor-guide.py): +# re-runs every test a rule record cites, finds every cited workflow step and +# decision, fetches every cited published artifact and verifies its signature +# and age, and checks every KSI against the live, verified KSI signal. Then it +# writes one signed set: a result per rule, per KSI, and an overall summary. +# Any failure fails this job, and the deploy job needs it. +# ============================================================================= +name: Simulated assessor (not a FedRAMP assessment) + +on: + workflow_call: + inputs: + phase: + description: pre-deploy (the gate before the SDR is built) or post-deploy (the just-published state) + type: string + default: pre-deploy + +permissions: {} + +env: + # Kept equal to deploy-with-opa.yml's pins by tests/test_simulated_assessor.py. + OPA_VERSION: 1.18.2 + OPA_SHA256: 9903e5125ac281104f2c4b7371d10cc3b74a98933743fcbfc174f9bf0ab20de8 + +jobs: + assess: + name: Totally Real Assessment Services, LLC (simulated) + runs-on: ubuntu-latest + timeout-minutes: 20 + # No id-token here: this job installs unpinned test tooling from PyPI and + # runs the provider's tests, so it must not be able to sign. The signing + # job below installs nothing but cosign. + permissions: + contents: read + steps: + - name: Checkout the commit under assessment + uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 + with: + persist-credentials: false + + - name: Install the assessor's tools + run: | + python3 -m pip install --user pytest jsonschema pyyaml cryptography + curl -fL --retry 5 --retry-delay 5 --connect-timeout 10 --max-time 120 \ + -o opa "https://openpolicyagent.org/downloads/v${OPA_VERSION}/opa_linux_amd64_static" + echo "${OPA_SHA256} opa" | sha256sum -c - + chmod 755 ./opa + sudo mv opa /usr/local/bin + + # The assessor verifies every published artifact's Sigstore bundle with + # cosign (assess.py cosign_verify). Verifying needs no id-token. + - name: Install cosign (verify only) + uses: sigstore/cosign-installer@7e8b541eb2e61bf99390e1afd4be13a184e9ebc5 # v3.10.1 + + # IVV-CSO-STE: the provider supplies the technical explanation (the guide); + # the assessor works from it. + - name: Receive the provider's assessor guide + run: python3 scripts/build-assessor-guide.py --commit "$GITHUB_SHA" --output assessor-guide.json --md-output assessor-guide.md + + - name: Assess every rule and KSI (verification and validation) + env: + PHASE: ${{ inputs.phase }} + run: python3 tools/simulated-assessor/assess.py --guide assessor-guide.json --repo . --commit "$GITHUB_SHA" --phase "$PHASE" --output simulated-assessment.json + + - name: Pass the unsigned assessment to the signing job + uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7.0.2 + with: + name: simulated-assessment-${{ inputs.phase }}-unsigned + path: simulated-assessment.json + if-no-files-found: error + + sign: + name: Totally Real Assessment Services, LLC (simulated) signs + needs: [assess] + runs-on: ubuntu-latest + timeout-minutes: 10 + permissions: + contents: read + id-token: write # keyless signing under this workflow's own identity + steps: + - name: Checkout the pinned assessor identity + uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 + with: + persist-credentials: false + + - name: Receive the unsigned assessment + uses: actions/download-artifact@9000827ccba6bdab643e8b6fd33ac0654aef8333 # v8.0.2 + with: + name: simulated-assessment-${{ inputs.phase }}-unsigned + + - name: Install cosign + uses: sigstore/cosign-installer@7e8b541eb2e61bf99390e1afd4be13a184e9ebc5 # v3.10.1 + + - name: Sign the assessment (keyless, the assessor's own identity) + run: cosign sign-blob --yes --new-bundle-format --bundle simulated-assessment.bundle simulated-assessment.json + + - name: Verify the assessment signature against the pinned assessor identity + run: | + id=$(python3 -c 'import json; print(json.load(open("infrastructure/keys/assessor-identity.json"))["certificate_identity"])') + cosign verify-blob --bundle simulated-assessment.bundle \ + --certificate-identity "$id" \ + --certificate-oidc-issuer https://token.actions.githubusercontent.com simulated-assessment.json + + - name: Hand the signed assessment to the provider + uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7.0.2 + with: + name: simulated-assessment-${{ inputs.phase }} + path: | + simulated-assessment.json + simulated-assessment.bundle + if-no-files-found: error diff --git a/.github/workflows/zap-dast.yml b/.github/workflows/zap-dast.yml index 067ce54b..de285025 100644 --- a/.github/workflows/zap-dast.yml +++ b/.github/workflows/zap-dast.yml @@ -1,43 +1,78 @@ # ============================================================================= -# ZAP DAST Scan (SA-11(8) Dynamic Code Analysis) +# ZAP DAST Scan (SA-11(8) Dynamic Code Analysis; VDR-CSO-DAC, VDR-TFR-PSD) # ============================================================================= -# Weekly OWASP ZAP baseline scan against the live site, in CI. This mechanizes -# SA-11(8): a dynamic analysis tool runs on a schedule and its findings are -# documented (the ZAP action maintains a tracking issue, which the operator -# records as decisions in data/decisions.json). SAST (Checkov, tfsec) and SCA (Syft, Grype) run on -# every deploy in deploy-with-opa.yml; this adds the dynamic layer. +# Two OWASP ZAP scans of the live system, in one run: # -# Weekly, so the latest report is always inside the VDR builder's 14-day DAST -# window (--zap-max-age-days, the Class C drift-detection cadence). The report is -# uploaded as the `zap-dast-report` artifact, for the VDR builds to read from -# the latest successful main-branch run (wired in a follow-up change). +# zap_baseline unauthenticated baseline of the site (passive rules), artifact +# `zap-dast-report`, read by the VDR build's --zap. +# zap_api AUTHENTICATED ZAP API scan of the Silk Reeling API, driven by +# the API's own OpenAPI document (the routes the deployed app +# actually serves), signed in as a dedicated Cognito scanner user +# so the requests pass the API Gateway JWT authorizer and reach the +# code behind /api. Artifact `zap-api-report`, read by --zap-api. +# +# When: daily, and after every successful deploy to main (workflow_run), so a +# changed running surface is dynamically tested right after it ships (DAC) and +# the latest scan is never more than a day old against the 3-day Class C sample +# cadence (PSD). The VDR builds take both reports from the latest SUCCESSFUL run +# on main, whatever triggered it (scripts/fetch-detection-feeds.sh); a run +# succeeds only when both scans did. A missed scan stops the VDR build: the +# baseline via --zap-max-age-days 3 (detection.zap.stale), the API scan after 72 +# hours (detection.zap-api, infrastructure/schemas/detection-feeds.json). +# +# The scanner user's credentials are repository secrets (SILK_DAST_USERNAME, +# SILK_DAST_PASSWORD, SILK_DAST_TOTP_SECRET, SILK_DAST_USER_POOL_ID); the user is +# created by the operator (docs/runbooks/dast-scanner-user.md). The sign-in is +# SRP + TOTP through the app client's existing flows (scripts/dast-cognito-token.py); +# no app-client flow is widened. The access token is masked before it is written +# anywhere and ZAP sends it only to samaydlette.com (ZAP_AUTH_HEADER_SITE). # # The issue title is plain words: the action finds its tracking issue with an # unquoted GitHub search query (`is:issue state:open repo:... `), so # search syntax in the title breaks it. Parentheses in the title made every run since July # fail with "The search query contains invalid syntax" before the artifact was # uploaded. -# -# Phase 1 (here): UNAUTHENTICATED scan of the public/static surface, which -# already satisfies "employ a dynamic analysis tool." Phase 2 (tracked -# follow-up): authenticated coverage of the Basic-Auth-gated taiji application -# via a ZAP context + credentials, for full URL coverage. # ============================================================================= name: ZAP DAST Scan on: schedule: - - cron: '23 7 * * 1' # 07:23 UTC every Monday + - cron: '23 7 * * *' # 07:23 UTC daily workflow_dispatch: # allow on-demand runs + # After every deploy to main: the run uses this file from main and scans what + # was just deployed. The job conditions drop deploy runs that did not succeed + # or came from a pull request (a fork's branch named `main` passes the + # `branches` filter alone). + workflow_run: + workflows: [Deploy Website with OPA Compliance] + types: [completed] + branches: [main] permissions: contents: read - issues: write # ZAP maintains one tracking issue for triage + +# One scan run at a time against the live site; a queued one still runs. +concurrency: + group: zap-dast + cancel-in-progress: false + +env: + SITE: https://samaydlette.com + # The API scan's image, pinned by digest (its container receives a live access + # token). 2.17.0 is ZAP's current release; refresh the pin with each release. + ZAP_IMAGE: 'ghcr.io/zaproxy/zaproxy:2.17.0@sha256:9624669db72f54d86c4b46a7064518bd9bf79d8c61a4c31befa9923489f328af' jobs: zap_baseline: name: OWASP ZAP Baseline (unauthenticated) + if: >- + github.event_name != 'workflow_run' || + (github.event.workflow_run.conclusion == 'success' && github.event.workflow_run.event != 'pull_request') runs-on: ubuntu-latest + timeout-minutes: 30 + permissions: + contents: read + issues: write # ZAP maintains one tracking issue for triage steps: - name: Checkout uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 @@ -51,3 +86,90 @@ jobs: allow_issue_writing: true issue_title: 'ZAP DAST findings for SA-11.8' artifact_name: 'zap-dast-report' + + zap_api: + name: OWASP ZAP API Scan (authenticated, Silk Reeling API) + if: >- + github.event_name != 'workflow_run' || + (github.event.workflow_run.conclusion == 'success' && github.event.workflow_run.event != 'pull_request') + runs-on: ubuntu-latest + timeout-minutes: 45 + permissions: + contents: read + steps: + - name: Checkout + uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 + with: + persist-credentials: false + + # The routes come from the app itself: FastAPI publishes the OpenAPI + # document of exactly the routes it serves. It names no server, so the + # scan's base (the CloudFront path the API is served under) is set here. + - name: Fetch the API definition and app client config + run: | + set -euo pipefail + curl -sfL --retry 3 --retry-delay 2 -o silk-openapi.raw.json "${SITE}/silk-reeling/openapi.json" + curl -sfL --retry 3 --retry-delay 2 -o silk-reeling-auth.json "${SITE}/.well-known/silk-reeling-auth.json" + jq --arg base "${SITE}/silk-reeling" '.servers = [{url: $base}]' silk-openapi.raw.json > silk-openapi.json + jq -e '.paths | keys | any(startswith("/api/"))' silk-openapi.json > /dev/null \ + || { echo "::error::the API definition lists no /api/ routes"; exit 1; } + echo "API routes in scope: $(jq -r '.paths | keys | join(", ")' silk-openapi.json)" + + # The token is masked before it is written anywhere, and reaches ZAP only + # through the environment. + - name: Sign in the DAST scanner user (Cognito SRP + TOTP) + env: + SILK_DAST_USERNAME: ${{ secrets.SILK_DAST_USERNAME }} + SILK_DAST_PASSWORD: ${{ secrets.SILK_DAST_PASSWORD }} + SILK_DAST_TOTP_SECRET: ${{ secrets.SILK_DAST_TOTP_SECRET }} + SILK_DAST_USER_POOL_ID: ${{ secrets.SILK_DAST_USER_POOL_ID }} + run: | + set -euo pipefail + tokfile="${RUNNER_TEMP:?}/dast-token" + trap 'rm -f "$tokfile"' EXIT + python3 scripts/dast-cognito-token.py token --auth-config silk-reeling-auth.json --out "$tokfile" + token=$(cat "$tokfile") + [ -n "$token" ] || { echo "::error::no access token"; exit 1; } + echo "::add-mask::${token}" + echo "ZAP_AUTH_HEADER_VALUE=Bearer ${token}" >> "$GITHUB_ENV" + + # Proof the scan is authenticated and the boundary holds: with the token an + # /api route answers 200, without it the gateway refuses. + - name: Verify the token is accepted and the API refuses without it + run: | + set -euo pipefail + with=$(curl -s -o /dev/null -w '%{http_code}' -H "Authorization: ${ZAP_AUTH_HEADER_VALUE}" "${SITE}/silk-reeling/api/exercises") + without=$(curl -s -o /dev/null -w '%{http_code}' "${SITE}/silk-reeling/api/exercises") + echo "GET /api/exercises: ${with} with the scanner token, ${without} without" + [ "$with" = 200 ] || { echo "::error::the scanner token was not accepted (${with})"; exit 1; } + [ "$without" = 401 ] || { echo "::error::the API answered ${without} without a token"; exit 1; } + + - name: ZAP API Scan (authenticated) + uses: zaproxy/action-api-scan@5158fe4d9d8fcc75ea204db81317cce7f9e5453d # v0.10.0 + env: + ZAP_AUTH_HEADER: Authorization + ZAP_AUTH_HEADER_SITE: samaydlette.com + with: + docker_name: ${{ env.ZAP_IMAGE }} + target: '/zap/wrk/silk-openapi.json' + format: openapi + # Gentle on a production API behind a 20 rps stage throttle, and capped + # well inside the token's 60-minute lifetime. + cmd_options: '-a -z "-config scanner.threadPerHost=2 -config scanner.maxScanDurationInMins=20"' + fail_action: false # informational here; the VDR build and vulnerability gate decide + allow_issue_writing: false # findings reach the VDR; no second public tracking issue + artifact_name: 'zap-api-report' + + # The token outlived the scan, so every request in it was authenticated. + - name: Verify the token still held after the scan + run: | + set -euo pipefail + with=$(curl -s -o /dev/null -w '%{http_code}' -H "Authorization: ${ZAP_AUTH_HEADER_VALUE}" "${SITE}/silk-reeling/api/exercises") + [ "$with" = 200 ] || { echo "::error::the scanner token expired or was refused during the scan (${with})"; exit 1; } + + - name: Check the API report exists + run: | + set -euo pipefail + jq -e '(.site | type == "array") and (.site | length > 0)' report_json.json > /dev/null \ + || { echo "::error::the API scan produced no report"; exit 1; } + echo "API scan: $(jq '[.site[].alerts[]?] | length' report_json.json) alert type(s); generated $(jq -r '."@generated"' report_json.json)" diff --git a/.gitignore b/.gitignore index 39dcd4c8..ff4cd10b 100644 --- a/.gitignore +++ b/.gitignore @@ -42,15 +42,17 @@ website/.well-known/iiw.csv infrastructure/iiw.csv infrastructure/oscal-ssp.json infrastructure/ksi-signal.json -infrastructure/cmmc-out.json # CR26 certification-data artifacts (built in CI from the canonical inventory, signed # and published to /.well-known/; never committed — same policy as the OSCAL artifacts above) infrastructure/ongoing-certification-report.json infrastructure/ongoing-certification-report.md -infrastructure/certification-overview-package.json -infrastructure/certification-overview-package.md infrastructure/certification-package-overview.json infrastructure/certification-package-overview.md +infrastructure/quarterly-review.ics +infrastructure/ocr-issues.json +infrastructure/fedramp-certification-reports.json +infrastructure/fedramp-certification-reports/ +infrastructure/package-submission-log.json infrastructure/security-decision-record.json infrastructure/security-decision-record.md infrastructure/availability.json @@ -153,6 +155,8 @@ tests/__pycache__/ # (Python's venv also writes its own .venv/.gitignore, but that only covers the # .venv name; these cover the other conventional ones.) .venv/ +# A worktree may symlink its venv; a symlink does not match the directory pattern. +.venv venv/ env/ .mypy_cache/ diff --git a/CACHE-BUSTING.md b/CACHE-BUSTING.md deleted file mode 100644 index 03a28e4f..00000000 --- a/CACHE-BUSTING.md +++ /dev/null @@ -1,54 +0,0 @@ -# Cache Busting Guide - -## What is Cache Busting? - -Cache busting ensures that visitors to your website always get the latest version of your CSS and JavaScript files, rather than loading outdated versions from their browser cache. - -## How It Works - -All CSS and JavaScript files in your HTML files now include a version query parameter (e.g., `main.css?v=1766154770906`). When you update this version number, browsers will treat the file as new and download the latest version. - -## Usage - -### Automatic (CI) - -The deploy workflow (`.github/workflows/deploy-with-opa.yml`) runs `node update-cache-version.js` immediately before the S3 sync step. Every deploy ships a fresh `?v=<timestamp>` on all CSS/JS references — no manual step required. - -### Manual (local dev) - -Run the script yourself when you want to preview the rewritten HTML locally: - -```bash -npm run cache-bust -# or: node update-cache-version.js -``` - -You generally do not need to commit the rewritten `?v=` values; CI overwrites them on the next deploy. - -### What Happens - -The script will: -1. Generate a new version number based on the current timestamp -2. Find all HTML files in the `website/` directory -3. Update all CSS and JS file references with the new version number -4. Display a summary of updated files - -### Example Output - -``` -Updating cache-busting version to: 1766154770906 - -✓ Updated: index.html -✓ Updated: pages/article-21.html -... - -28 file(s) updated with version 1766154770906 -``` - -## Technical Details - -The cache-busting script (`update-cache-version.js`): -- Uses timestamp-based versioning for uniqueness -- Automatically finds and updates all HTML files -- Preserves existing file structure and formatting -- Only modifies version query parameters on asset URLs diff --git a/CLAUDE.md b/CLAUDE.md index a7ccabb9..46a266f1 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -10,15 +10,34 @@ Hold two facts at once — they shape every decision: - **It is a real, functioning production system.** Real AWS infrastructure, real CI/CD, real cryptographic signing. Changes must keep it deployable and keep the compliance gate green. Treat `main` as production. - **Merging to `main` no longer deploys on its own:** the `deploy` job is bound to the `prod` GitHub Environment, which requires a human reviewer, so every deploy halts before `terraform apply` until someone approves it in the Actions UI. `deploy-with-opa.yml` has **no `schedule:` trigger** — a scheduled deploy could only ever queue at that gate, which is what let twelve days of stale evidence pass unnoticed. Every path to `terraform apply` is now human-initiated *and* human-approved. - - **One thing does run unattended: `evidence-nightly.yml`.** See the trade recorded under *Security & compliance rules*. + - **Three workflows write production evidence unattended:** `evidence-nightly.yml` (the VDR), `package-maintenance.yml` (the CPO, SDR and OCR, and the quarterly issues) and `incident-reports.yml` (the incident reports), each with its own narrowly scoped role and no required reviewer. See the trade recorded under *Security & compliance rules*. - **It is also a proof of concept for a scaled version** — a reference architecture for what agency- or enterprise-grade automated compliance ("evidence reciprocity") would look like across many systems. Favor designs that generalize and stay legible; treat the single-account, single-site specifics as stand-ins for a multi-system deployment. **Be honest about the gap:** this repo has **no federal data and no agency sponsor**. It demonstrates the mechanism; it is **not** an authorized system. Never imply otherwise in code, docs, or generated artifacts. +## Proof-of-concept latitude +This system shows that policy as code can automate CR26. It is not certified. +Procedure may flex. Claims may not. + +- Implemented: a real mechanism ran on real inputs, and evidence exists. +- Simulated: a real mechanism ran on a labeled stand-in input. +- Not Demonstrated: not built; say why. +- Not Applicable: the rule does not apply; say why. + +Before using a stand-in, show that a bad input changes the result, and that a +real input could replace it without changing the logic. If you can't, mark the +record Not Demonstrated. + +You may propose a stand-in or scope cut. You may not approve one. Record each +with what is real, what is simulated, and who approved it. + +Never choose a status because a gate requires it. If the honest status blocks +the build, stop and tell me. + ## Codebase map Confirm against the working tree on first run; correct this section if reality differs. - `infrastructure/` — Terraform (`main.tf`), OPA policy packages (`policy/`), JSON schemas (`schemas/ksi-signal.schema.json`, `schemas/ksi-catalog.json`), runtime Lambda (`lambda/index.js`). -- `scripts/` — the artifact **generators**: `build-ksi-signal.py` (the canonical inventory), the VDR builder, and the CR26 record builders (`build-sdr.py`, `build-cpo.py`, and `build-cr26-vdr.py`, which turns the VDR report into FedRAMP's VDT, AVI and history reports). CR26 reports are validated against FedRAMP's 2026-06-24 JSON schemas, vendored verbatim with their sha256s in `infrastructure/schemas/fedramp-2026-06-24/`, by `scripts/_fedramp_schema.py` before they are written; a report that does not validate is never written. Never edit a vendored schema; the loader refuses any file whose hash differs from `SOURCES.json`. The per-control view (status, origination, statement per NIST 800-53 control) is the control projection in `scripts/_controls.py`, computed in memory from the inventory and the KSI catalog; the OSCAL SSP that used to carry it was retired under CR26 (2026-11-05) and the SDR's `rev5_controls` publishes it. Every human decision about a finding is a record in `data/decisions.json` (the decision register, which replaced the POA&M under CR26), read through `scripts/_decisions.py` by the VDR builder, the vulnerability gate, reconciliation and the trust center; every in-force record carries `decided_by`, `decided_on` and an annual `review_by`, which the loader and `tests/test_decision_records.py` enforce. These are the source of truth for everything published. `scripts/_common.py` holds the helpers they share (`classify` — the inheritance rule four artifacts must agree on — plus `sha256_file`, `prop`, `load_hub`, `sid`); it is imported via an `__file__`-relative `sys.path.insert` so every script stays standalone-runnable from any cwd. **`scripts/staged/` is not wired into anything** — parked generators, see its README; never assume a script there runs. +- `scripts/` — the artifact **generators**: `build-ksi-signal.py` (the canonical inventory), the VDR builder, and the CR26 record builders (`build-sdr.py`, `build-cpo.py`, and `build-cr26-vdr.py`, which turns the VDR report into FedRAMP's VDT, AVI and history reports). CR26 reports are validated against FedRAMP's 2026-06-24 JSON schemas, vendored verbatim with their sha256s in `infrastructure/schemas/fedramp-2026-06-24/`, by `scripts/_fedramp_schema.py` before they are written; a report that does not validate is never written. Never edit a vendored schema; the loader refuses any file whose hash differs from `SOURCES.json`. The per-control view (status, origination, statement per NIST 800-53 control) is the control projection in `scripts/_controls.py`, computed in memory from the inventory and the KSI catalog; the OSCAL SSP that used to carry it was retired under CR26 (2026-11-05) and the SDR's `rev5_controls` publishes it. Every human decision about a finding is a record in `data/decisions.json` (the decision register, which replaced the POA&M under CR26), read through `scripts/_decisions.py` by the VDR builder, the vulnerability gate, reconciliation and the trust center; every in-force record carries `decided_by`, `decided_on` and an annual `review_by`, which the loader and `tests/test_decision_records.py` enforce. Whether each FedRAMP rule that applies (20x Program Class C, derived from the pinned corpus's applicability metadata by `_rules.applicable_provider_rules`) is implemented is a record in `data/frr-records.json`, read through `scripts/_frr.py`: one record per applicable rule, a missing or extra record fails, and a record may say "Implemented" only with evidence that resolves (a test, a workflow step, a freshness-governed published artifact, or an in-force decision). A change that implements a rule flips its record in the same PR, with the evidence. A record describes the state after a successful deploy of its commit, never "not yet deployed"; anything the deploy depends on (a bootstrap apply, a repo variable) must make the deploy fail when missing. These are the source of truth for everything published. `scripts/_common.py` holds the helpers they share (`classify` — the inheritance rule four artifacts must agree on — plus `sha256_file`, `prop`, `load_hub`, `sid`); it is imported via an `__file__`-relative `sys.path.insert` so every script stays standalone-runnable from any cwd. Every file in `scripts/` has a caller (a workflow, a Makefile, the infrastructure or another script; `tests/test_repo_hygiene.py` enforces it), and every file under `data/` has a reader. - `website/` — static site content. `website/.well-known/` is where the **published** artifacts are served from (KSI signal + bundle, SDR, CPO, VDR + trend, IIW CSV, runtime signal, signing pubkey, schema), but in git it tracks only `security.txt` and `vdr-trend.json`: everything else there is gitignored build output that the deploy signs and uploads (the website sync excludes `.well-known/*`). - `docs/` — `policies/`, `runbooks/`, `scn/`, and `assessment/` (e.g. `ground-truth.md`). - `website/research/` — plain static pages: `authorization-boundary.html` (scope; **read it first for the "why"**) and the long-form essay `staying-in-the-loop.html` (threshold dynamics, titled "Staying in the Loop"). The essay's filename is **not** referenced by `build-ksi-signal.py`, which discovers pages with `rglob("*.html")`; the hardcoded path lives in `tools/essay/paths.py`, so renaming means updating that. `/research/tuning-the-eigenvalue.html` and `/research/the-plumbing.html` are redirect stubs (the latter to the dashboard; the "Automated Security Compliance" paper is retired). @@ -28,8 +47,9 @@ Confirm against the working tree on first run; correct this section if reality d - `tools/boundary-map/corroborate.py` (local only) — independent corroboration of the map by RAMPART on TAP, which collects the account from the AWS APIs. The operator runs it and commits `docs/boundary/corroboration.json`; the deploy signs and publishes it as `/.well-known/boundary-corroboration.json`, and the trust center reports its result and age (30-day window). Resources only TAP sees go to the decision queue. - `scripts/build-trust-center.py` — the trust center's data (`/.well-known/trust-center.json`, signed): the "is this picture true?" checks, the queue of decisions that need a person, the policy catalog, the escalation rate and the decision log, all derived from this build's artifacts and the registers. Built after the reconciliation gate; fails closed if its inputs are bound to another inventory. A register field that is not recorded (who decided, when, review date) is published as a gap, never filled in. - `.github/workflows/deploy-with-opa.yml`, `infrastructure/Makefile`, `.checkov.yaml` — the pipeline, entry points, and IaC scan config. -- `.github/workflows/evidence-nightly.yml` — the unattended VDR refresh, **twice a day**, plus once after every successful deploy to `main` (`workflow_run`, so a deploy that fixes a failing nightly also clears its beacon): re-scan (Syft + Grype against a fresh vulnerability DB), rebuild the VDR + trend, run the same vulnerability and reconciliation gates, republish six objects under `.well-known/vdr-*` (report, bundle, markdown, trend, trend bundle, provenance attestation), and on every run, pass or fail, write a status beacon (`.well-known/vdr-status.json`, outcomes only, unsigned). No `terraform apply`, no website sync. Its alerting is the `alert` job (a GitHub issue), not the deploy workflow's `notify`. -- `infrastructure/watchdog.tf` + `infrastructure/watchdog/` — the **evidence SLA watchdog**: an hourly Lambda reads every artifact listed in the governed freshness config from the bucket (AWS APIs only, no internet egress), publishes the VDR's and runtime signal's ages, the nightly's result and a count of artifacts past their window as CloudWatch metrics, and four alarms email the operator via a CMK-encrypted SNS topic. This is the page; the GitHub issue is the paper trail. The email subscription is created out of band so no address enters Terraform state. Runbook: `docs/runbooks/evidence-sla-alarm.md`. +- `data/incidents.json` + `scripts/_incidents.py` + `scripts/build-incident-report.py` — the incident register and FedRAMP incident reporting (IEC-CSO-*; VER-TFR-IRI/NRI via `policies/triage.rego` `incident_triggers`). Every incident carries its reportability evaluation; reportable ones get Initial/Ongoing/Final reports in FedRAMP's schema on the Class C clocks read from the pinned rules, published with the incident log at `/.well-known/incident-reports.json`. `.github/workflows/incident-reports.yml` publishes them unattended (role in `infrastructure/bootstrap/incident-reports.tf`, `.well-known/incident-*` only); the watchdog pages on an overdue report. Notification is publish-only: nothing is sent to FedRAMP or an agency. Exercises are records with `exercise: true`. +- `.github/workflows/evidence-nightly.yml` — the unattended VDR refresh, **twice a day**, plus once after every successful deploy to `main` (`workflow_run`, so a deploy that fixes a failing nightly also clears its beacon): re-scan (Syft + Grype against a fresh vulnerability DB), rebuild the VDR + trend, run the same vulnerability and reconciliation gates, republish its objects under `.well-known/vdr-*` (the VDR report, the trend ledger, FedRAMP's three CR26 vulnerability reports, the monthly activity report and the non-machine V&V status, each with its signature and readable views, and the provenance attestation; the publish step lists each one), and on every run, pass or fail, write a status beacon (`.well-known/vdr-status.json`, outcomes only, unsigned). No `terraform apply`, no website sync. Its alerting is the `alert` job (a GitHub issue), not the deploy workflow's `notify`. +- `infrastructure/watchdog.tf` + `infrastructure/watchdog/` — the **evidence SLA watchdog**: an hourly Lambda reads every artifact listed in the governed freshness config from the bucket (AWS APIs only, no internet egress), publishes the VDR's and runtime signal's ages, the nightly's result and a count of artifacts past their window as CloudWatch metrics, and five alarms email the operator via a CMK-encrypted SNS topic. This is the page; the GitHub issue is the paper trail. The email subscription is created out of band so no address enters Terraform state. Runbook: `docs/runbooks/evidence-sla-alarm.md`. AWS: account is referenced in the published KSI signal; `us-east-2` for the site/app/Lambda/S3/CloudWatch/API Gateway/Secrets Manager, `us-east-1` for ACM/CloudFront and the DNSSEC/CloudFront KMS keys. Confirm before acting. @@ -37,10 +57,10 @@ AWS: account is referenced in the published KSI signal; `us-east-2` for the site The system rests on one idea: **the canonical inventory is the single source of truth; every other artifact is derived from it and reconciled against live reality.** -- **NEVER hand-edit generated artifacts** (`/.well-known/*.json`, the SSP, the KSI signal, the VDR). Change the **generator** in `scripts/` and regenerate. +- **NEVER hand-edit generated artifacts** (`/.well-known/*.json`, the KSI signal, the VDR, the SDR and CPO). Change the **generator** in `scripts/` and regenerate. - All artifacts must build from one inventory `signal_id`/hash and carry it. A decision about a finding goes in `data/decisions.json` and nowhere else; reference it by its `DEC-NNN` ID. - A **reconciliation gate** runs in CI before publish and **fails closed**. **NEVER disable, weaken, or bypass it (or the OPA gate) to make a build pass.** Fix the underlying issue or raise it. -- **Site content is inventoried content.** `build_html_components()` in `scripts/build-ksi-signal.py` hashes **every** `*.html` under `website/` into the canonical inventory as an `html_artifact`. So editing a page changes its sha256 in the KSI signal, the SSP, and the VDR, and *adding* a page adds a component. Both are fine and both are generator-driven: run the pipeline, never hand-add the entry. A content-only change is still a pipeline change. +- **Site content is inventoried content.** `build_html_components()` in `scripts/build-ksi-signal.py` hashes **every** `*.html` under `website/` into the canonical inventory as an `html_artifact`. So editing a page changes its sha256 in the KSI signal and the VDR, and *adding* a page adds a component. Both are fine and both are generator-driven: run the pipeline, never hand-add the entry. A content-only change is still a pipeline change. - **Publish freshness:** a green pipeline must publish *this run's* artifacts. The served `/.well-known/*` must carry the current commit and a fresh `emitted_at`; a stale serve is a bug, not a cache quirk. This has bitten before — verify the post-deploy round-trip. ## How to work @@ -76,7 +96,7 @@ Speed comes from parallelizing *independent* work, not from putting more agents - **Least privilege always.** Never broaden IAM to make something work — scope down or ask. - **Published reporting must be under 24 hours old, and something now enforces it.** Every freshness window is a governed value in `infrastructure/schemas/freshness-config.json` (one entry per artifact published under `/.well-known/`, schema-validated, with who decided it and a review date). The trust center, the watchdog (Lambda and alarm thresholds) and `scripts/check-evidence-freshness.py` all read it and fail closed without it; never put a window back as a literal. A new published artifact needs an entry, or `tests/test_freshness_config.py` fails. `scripts/check-evidence-freshness.py` fetches `/.well-known/vdr-report.json` over the public URL and fails if its `emitted_at` is outside the window (`--all <site>` checks every listed artifact). Note what the reconciliation gate does *not* do: `check_f_freshness` in `scripts/reconcile.py` only asserts that the staged signal carries the current commit and has an `emitted_at` at all. It has no staleness threshold and never looks at the live edge — which is why twelve days of rot passed with every gate green. Don't mistake one for the other. - **The unattended-write trade — read this before touching `evidence-nightly.yml`.** That workflow runs nightly with **no required reviewer**, because published evidence has to stay fresh while nobody is awake. It is a genuine unattended production write and it is named as one. What makes it acceptable is its size: it replaces an unattended `terraform apply` over the whole stack with an unattended `PutObject` under a single S3 key prefix. Its dedicated OIDC role (`infrastructure/bootstrap/evidence-nightly.tf`) can write **only** `.well-known/vdr-*`, invalidate CloudFront, and make the read-only calls the reconciliation gate's `--live` sweep needs. It cannot apply Terraform, sync the website, delete an object, or write anywhere else. **The correct response to "the nightly needs one more permission" is to ask whether that work belongs on the unattended path at all — not to widen the role.** The `prod` environment and its reviewer requirement are separate and must stay as they are. -- **The nightly refreshes the VDR only, and binds to the *published* inventory.** It fetches `/.well-known/ksi-signal.json`, verifies its Sigstore bundle against the deploy workflow's pinned identity, and uses that `signal_id` to satisfy reconciliation invariant (e) without rebuilding the inventory. It fetches the published SDR and CPO and verifies their signatures **as gate inputs only** — never re-signed, never re-published. A changed inventory means changed infrastructure and belongs on the reviewed deploy path. A newly disclosed CVE **cannot** auto-publish: invariants (g) and (h) require a human-authored POA&M entry, so the nightly fails until someone dispositions it. That is the gate working; the `alert` job is what makes the failure visible. The live reconciliation (`--live`) runs even when the vulnerability gate has failed, and the alert names which gate stopped the run, so a failing vulnerability gate can no longer hide a skipped drift check. Publishing still requires both gates to pass. +- **The nightly refreshes the VDR only, and binds to the *published* inventory.** It fetches `/.well-known/ksi-signal.json`, verifies its Sigstore bundle against the deploy workflow's pinned identity, and uses that `signal_id` to satisfy reconciliation invariant (e) without rebuilding the inventory. It fetches the published SDR and CPO and verifies their signatures **as gate inputs only** — never re-signed, never re-published. A changed inventory means changed infrastructure and belongs on the reviewed deploy path. A newly disclosed CVE **cannot** auto-publish past its clock: invariant (h) requires every VDR finding to resolve to an in-force decision record (`data/decisions.json`) or be open within its clock, so the nightly fails until it is dispositioned. That is the gate working; the `alert` job is what makes the failure visible. The live reconciliation (`--live`) runs even when the vulnerability gate has failed, and the alert names which gate stopped the run, so a failing vulnerability gate can no longer hide a skipped drift check. Publishing still requires both gates to pass. - **NEVER hardcode account IDs, ARNs, or secrets** in committed code/Terraform — use variables and data sources. Reading the account ID for verification is fine; committing it is not. Never commit credentials. - **NEVER assert any service's FedRAMP authorization status without verifying it from a current source.** - **Don't fabricate compliance.** If a control can't be met, document the residual honestly with a Moderate-level rationale. Dismissed scanner findings must be classified as **false positive** (with justification) or **risk-accepted** — never silently dropped. diff --git a/Makefile b/Makefile index a5355c30..7fc38437 100644 --- a/Makefile +++ b/Makefile @@ -122,6 +122,12 @@ check-full: check require-artifacts @$(MAKE) --no-print-directory reconcile @echo "✅ check-full: PASS" +# The completeness gate the deploy runs before anything is applied: every +# applicable FedRAMP rule Implemented or Not Applicable (scripts/_frr.py). +# Not part of `check`: work toward it lands on branches that are not yet complete. +check-complete: + python3 scripts/_frr.py --complete + require-artifacts: @missing=""; \ for f in ksi-signal.json vdr-report.json security-decision-record.json certification-package-overview.json; do \ diff --git a/README.md b/README.md index 172e001b..0a841abb 100644 --- a/README.md +++ b/README.md @@ -87,7 +87,7 @@ curl -O https://samaydlette.com/.well-known/ksi-signal.json curl -O https://samaydlette.com/.well-known/ksi-signal.bundle cosign verify-blob \ --bundle ksi-signal.bundle \ - --certificate-identity-regexp 'https://github.com/sam-aydlette/samaydlette.com/.github/workflows/.+' \ + --certificate-identity 'https://github.com/sam-aydlette/samaydlette.com/.github/workflows/deploy-with-opa.yml@refs/heads/main' \ --certificate-oidc-issuer https://token.actions.githubusercontent.com \ ksi-signal.json ``` @@ -122,12 +122,13 @@ The repository ships a documentation set that closes 27 KSI indicators with rati | [`docs/architecture-decisions.md`](docs/architecture-decisions.md) | KSI-CMT-RVP, KSI-CNA-RNT/ULN/RVP/OFA, KSI-IAM-JIT, KSI-MLA-OSM/RVL/ALA, KSI-PIY-RSD, KSI-SVC-EIS/ASM/PRR/VCM | ADR-style records of architectural decisions per KSI | | [`docs/incident-response.md`](docs/incident-response.md) | KSI-INR-RIR, KSI-INR-RPI, KSI-INR-AAR | IR runbook with detection sources, triage, after-action template | | [`docs/recovery-plan.md`](docs/recovery-plan.md) | KSI-RPL-RRO, KSI-RPL-ARP, KSI-RPL-ABO, KSI-RPL-TRC | RTO 21 days / RPO 24 hours, recovery procedure, tabletop log | -| [`docs/security-review.md`](docs/security-review.md) | KSI-PIY-RIS | Annual security review template + first entry | +| [`docs/security-review.md`](docs/security-review.md) | KSI-PIY-RIS | How the Annual Security Review is generated (`scripts/hold-security-review.py`), and its history | | [`docs/supply-chain.md`](docs/supply-chain.md) | KSI-SCR-MIT, KSI-SCR-MON | SCRM with Dependabot config in `.github/dependabot.yml` | | [`docs/training-log.md`](docs/training-log.md) | KSI-CED-RAT | Self-attested training log | | [`data/decisions.json`](data/decisions.json) | (cross-cutting — meta) | The decision register: every decision about a finding (false positive, accepted risk, operational requirement, remediation history), with who decided, when, and the review date. Replaced the POA&M under CR26 | +| [`data/frr-records.json`](data/frr-records.json) | SDR-CSO-FRR | One record per FedRAMP rule applicable to 20x Class C: status, implementation, evidence, and the gap and closing work when not implemented. Validated by `scripts/_frr.py`, which refuses a claim of "Implemented" without evidence that resolves | | [`docs/policies/`](docs/policies/) | NIST 800-53 Rev 5 *-1 controls (AC-1, AT-1, ... SR-1, PT-1) | Per-family policy and procedures docs, plus the FedRAMP 20x Secure Configuration Guide. Each file integrates the relevant 20x rules (SCN, VDR, MAS, SCG, CCM, ICP, FSI, UCM) and cites AWS authorization package AGENCYAMAZONEW for inherited families | -| [`docs/continuous-monitoring-plan.md`](docs/continuous-monitoring-plan.md) | CA-7, KSI-MLA, FedRAMP 20x CCM | Continuous Monitoring strategy and mechanisms (deploy-time gate, runtime emitter, VDR aggregator, annual review) | +| [`docs/continuous-monitoring-plan.md`](docs/continuous-monitoring-plan.md) | CA-7, KSI-MLA, FedRAMP 20x CCM | Continuous Monitoring strategy and mechanisms (deploy-time gate, runtime emitter, VDR aggregator, generated Annual Security Review) | | [`docs/privacy-threshold-analysis.md`](docs/privacy-threshold-analysis.md) | PT-1 (negative determination) | PTA: no PII processed; full PIA not required | | [`docs/rules-of-behavior.md`](docs/rules-of-behavior.md) | PL-4 | Sole-operator acceptable-use commitments | | [`website/.well-known/security.txt`](website/.well-known/security.txt) | KSI-PIY-RVD | RFC 9116 vulnerability disclosure | @@ -229,7 +230,7 @@ The pipeline produces five artifacts at `/.well-known/` — the FedRAMP 20x KSI │ ├── schemas/ # KSI signal schema, FedRAMP KSI catalog, policy-input schemas │ ├── lambda/index.js # runtime KSI emitter; runs the SAME Rego, compiled to Wasm │ └── bootstrap/ # operator-applied: OIDC, IAM, CloudFront, DNSSEC, tf state -├── scripts/ # the artifact generators — 25 live +├── scripts/ # the artifact generators and gates │ ├── _common.py # the shared helpers (classify, sha256_file, prop, ...) │ ├── build-ksi-signal.py # THE CANONICAL INVENTORY; everything derives from it │ ├── _controls.py # the control projection (per-control view) @@ -237,14 +238,13 @@ The pipeline produces five artifacts at `/.well-known/` — the FedRAMP 20x KSI │ ├── build-sdr.py build-cpo.py build-ocr.py ... │ ├── reconcile.py # the fail-closed reconciliation gate │ ├── vuln-gate.py check-exceptions.py check-policy-annotations.py check-wasm-safe.py -│ ├── verify-published.sh # verify the LIVE evidence, no AWS needed -│ └── staged/ # NOT wired into the pipeline — see its README +│ └── verify-published.sh # verify the LIVE evidence, no AWS needed ├── website/ # static site; every *.html is hashed into the inventory │ ├── index.html trust/ pages/ assets/ │ ├── research/ # methodology + scope docs; read these for the "why" │ └── .well-known/security.txt # RFC 9116 (generated artifacts are NOT committed) -├── data/ # vendored NIST/FedRAMP source data + PROVENANCE.md -│ ├── catalogs/ profiles/ mappings/ baselines/ schemas/oscal/ +├── data/ # registers + vendored NIST/FedRAMP source data (PROVENANCE.md) +│ ├── catalogs/ profiles/ # 800-53 Rev5 catalog, FedRAMP Rev5 Moderate baseline ├── policies/triage.rego # vulnerability triage policy ├── docs/ # policies/, scn/, runbooks/, assessment/ ├── tools/ # both are CI gates, not optional tooling @@ -391,6 +391,11 @@ same way. There is no local publish target, by design. +Cache busting: just before the website sync, the deploy runs +`node update-cache-version.js` (also `npm run cache-bust`), which stamps a fresh +`?v=<timestamp>` on every CSS and JS reference in `website/**/*.html`, so visitors +never get a stale asset. The rewritten values need not be committed. + ### Local: infrastructure and the offline gates ```bash cd infrastructure @@ -470,14 +475,6 @@ aws s3 sync . s3://samaydlette.com/ --exclude "*.tf" --exclude ".terraform/*" -- aws cloudfront create-invalidation --distribution-id E1234567890123 --paths "/*" ``` -### Debug Mode (When You're Really Stuck) - -```bash -export TF_LOG=DEBUG -export AWS_CLI_FILE_ENCODING=UTF-8 -./deploy.sh -``` - **Pro Tip:** Most compliance automation failures happen during policy development, not in production. Test extensively with sample data before going live. ## License diff --git a/REMEDIATION-REPORT.md b/REMEDIATION-REPORT.md deleted file mode 100644 index 10139dae..00000000 --- a/REMEDIATION-REPORT.md +++ /dev/null @@ -1,170 +0,0 @@ -# Remediation Report — verify-then-fix engagement, 2026-07 - -Scope: the five Phase-0 verification questions and the prioritized gap list from -the July 2026 remediation brief. Ground rule applied throughout: where the brief -conflicted with the repository or live AWS state, the repo/live state won and -the discrepancy is recorded here. All live checks were read-only CLI or curl -against the published `/.well-known/` artifacts. - -Headline: **a majority of the brief's findings were already fixed on `main` -before this engagement began** (the brief appears to have been written against -a ~mid-June snapshot). The real, still-open gaps were: two failing tag -validations, stale narrative strings inside the signal generator, an over-broad -SSP downgrade heuristic, SSP auth controls still dispositioned for the pre-app -world, a runtime emitter blind spot, stale human docs, a missing SCN record, -and the absence of any CloudTrail trail. All of those are fixed in PRs #218–#225. - -## Phase 0 — verification results - -### 0.1 App auth ground truth -**Deployed reality (live CLI, 2026-07-02..06): Amazon Cognito** — pool with -`MfaConfiguration: ON` (TOTP), 14-char password policy, admin-only creation; -API Gateway JWT authorizer on `ANY /api/{proxy+}` (issuer = the pool, audience -= the pinned SPA client); `$default` route open serving only the SPA shell; -stage throttling 20 req/s / burst 10; access logging to a CMK-encrypted log -group. Terraform, article-28, the live KSI signal, and the published SPA auth -config all agree. The brief's premise ("Basic Auth deployed, article -overclaims") was **inverted**: the article was right; the stale surfaces were -`docs/poam.md`'s POAM-021/022/023 narrative paragraphs (present-tense Basic -Auth; fixed in PR #223) and one marketing sentence (fixed, same PR). The app -Lambda does call the Anthropic API directly (POAM-020, risk-accepted; see 3.4). - -### 0.2 POA&M set reconciliation -Authoritative set: **POAM-001..031 with POAM-016 retired → 30 items**, exactly -what the live `oscal-poam.json` carries (regenerated daily) and what `main`'s -`build-oscal-poam.py` and `docs/poam.md` already encode. The brief's "poam.md -ends at 024" and "README lists only 001/002" were stale-branch/README issues: -main's poam.md has all rows; the README genuinely was stale (presented 001/002 -as open; both closed June) — fixed in PR #223. Article-28's POAM-025 reference -is real (hardware/phishing-resistant MFA, open operational-requirement, added -from the 2026-06-22 Prowler triage). The brief's "192 implemented-requirements" -README claim did not exist (README said 331; the builder now emits 333 and the -figure is machine-stamped via inject-figures, PR #223). - -### 0.3 Failing validation identity -Two real findings, both tag gaps, plus two tooling defects: -- **v-0015** (deploy-time signal): access-log bucket missing the `CostCenter` - required tag → fixed in Terraform (PR #218). -- **r-0000** (runtime signal): website bucket (not Terraform-managed; data - source only) missing all six classification tags → fixed live via - `put-bucket-tagging` (2026-07-06), preserving the existing tags, values - mirroring the inventory's projected classification. -- Tooling defect 1: the SSP builder downgraded controls via a hardcoded - policy-id→KSI map, dragging in passing KSIs (CA-7/SI-7(7) went partial with - no failing evidence) → now reads the signal's own per-KSI attribution - (PR #220). -- Tooling defect 2: the runtime emitter validated only the *first* S3 bucket, - so the log bucket was never re-checked at runtime → now iterates every - object_store component, with a metadata-only IAM grant (PR #221). -The brief's "45 passing / 1 failing" matched the deploy signal; the SSP partial -cluster (12 controls) resolves once #218 deploys and #220 corrects attribution. -A third alleged defect (deployed policy wasm containing a rule with no -committed source) was an artifact of reading a stale branch — the -classification rules are committed in `infrastructure/policies.rego` on main. - -### 0.4 KSI completeness vs final CR26 -**No gap.** The final CR26 corpus (local clone, HEAD 2026-06-25) defines **46** -Class C KSIs (the ~56 figure was pre-final; Class B and C share the same 46); -the live SDR's 46 `rule_records`, the local `ksi-catalog.json`, and the corpus -are identical sets — zero diff. VDR-* vs VER-*: **both families exist as -distinct stable rulesets** in the final corpus (VDR = Detection & Response, 18 -rules; VER = Evaluation & Reporting, 25 rules); the generator and the live -`vdr-report.json` (regenerated 2026-07-02, not stale) already cite both -correctly. No action taken; none needed. - -### 0.5 Audit trail reality -**No CloudTrail trail exists** (no TF resource, no delivery bucket; the -operator IAM user is denied `cloudtrail:DescribeTrails`, so absence was -established structurally). All three live CloudWatch log groups are **365-day -retention, CMK-encrypted** — POAM-017/018/024 closures are real; the brief's -"7-day retention" was pre-closure. The one true residue: the live signal's -`baseline_configuration` strings still said "7-day retention" and "DNSSEC not -enabled" — hardcoded generator text, fixed in PR #219. The log bucket has a -400-day lifecycle in TF (live check denied to the operator user; flagged, not -asserted). CloudTrail gap remediated in PR #225. - -## Phase 1 — truth reconciliation - -| Item | Result | -|---|---| -| 1.1 inventory native_id bug | **Already fixed on main** before this engagement (per-resource ARN as native_id; duplicate-native_id fail-closed gate in `validate-ksi-signal.py` with unit tests). Verified in the live signal: 212 components, zero duplicate native_ids, the app Lambda carries its own ARN. No action needed. | -| 1.2 boundary vs deployed surface | The ABD/DFD (`authorization-boundary.html`) was **already current** (flow H: Cognito JWT ingress). The real gap was the **SSP**: IA-2 (+enh), IA-8, AC-7, AC-11/12 still `not-applicable`. Fixed per the brief's preferred design: dispositions now **derive from the inventory's identity_provider component** and revert automatically if the app is torn down (PR #222). AC-11 stays honestly N/A (device session lock; AC-12 token expiry bounds it). SC-5 was already implemented. | -| 1.3 impact-level contradiction | **Premise not reproducible on main.** `docs/poam.md` is uniformly Moderate (header and rationales); no "FIPS-199 Low" text exists. The only Low-flavored friction is the Prowler scan baseline name (`fedramp_20x_ksi_low`), which is a scanner-tier issue (see 2.1), not a categorization claim. `reconcile.py` passed because there was nothing to fail. No invariant added — there is no textual pattern to guard that wouldn't be theater. | -| 1.4 stale surfaces sweep | README POA&M section, POAM-016 ghost reference, old KSI IDs, hand-typed counts → PR #223 (README joins inject-figures targets; the 331/333 headline figure is now machine-stamped). poam.md narratives → PR #223. VDR staleness: **not stale** (emitted 2026-07-02; 0.4). Risk-accepted count basis (VDR 18 vs SDR 10) and the three `poam_ref: null` suppressions could not be fully reconciled in this pass — left open, see "Not completed". DNSSEC claim → PR #219 (the signal was wrong in the *other* direction: DNSSEC is ON). | -| 1.5 freshness enforcement | **Largely satisfied by design already:** the deploy workflow runs on a daily cron and executes `reconcile.py --live --expect-commit` before and after publish; every artifact regenerates daily (live signal `emitted_at` was same-day on every check). The brief's "deploy signal stuck at 2026-06-12" no longer reproduces. No extra skew job added — a second scheduled checker would duplicate the daily pipeline; noted as a conscious skip. | - -## Phase 2 — CR26 Class C mechanics - -| Item | Result | -|---|---| -| 2.1 two independent methods per KSI | **Open — the one substantive P1 gap remaining.** Today's two persistent methods (OPA deploy gate, runtime Lambda) share the same compiled Rego, so independence is arguable; the Prowler runs (2026-06-22/23) were manual and used the Low KSI baseline. Plan: scheduled Prowler on the moderate/Class-C-appropriate baseline (verify the exact framework id against the installed Prowler version rather than assuming a name), results mapped to KSI ids and merged into the SDR's per-KSI verification fields, with explicit exceptions where a second automated method is genuinely N/A (documentation-method KSIs). Deferred rather than shipped half-wired — see "Not completed". | -| 2.2 sign the runtime signal | **Already done (POAM-002 closed 2026-06-17)** and verified live: `provenance.attestation` carries a KMS ECDSA-P256 signature; `/.well-known/runtime-signing-pubkey.pem` serves the public key (HTTP 200). No action needed. | -| 2.3 clear the failing validation | Done via PR #218 (config fix, the honest disposition — no POA&M entry needed for a promptly-remediated tag) plus the live website-bucket tagging. SSP partials self-resolve on the next deploy. | -| 2.4 SCN hygiene | The app addition had SCN-2026-001 (Adaptive, verified). The **auth change had no SCN record** — backfilled as SCN-2026-002 with SIA and a fresh post-implementation verification (PR #224). The CloudTrail addition ships with its own SCN-2026-003 (PR #225). Commit/PR SCN-Type tagging follows the existing validator (missing tag = routine-recurring by policy). | - -## Phase 3 — cross-framework gaps - -| Item | Result | -|---|---| -| 3.1 CI credentials (POAM-001) | **Already done (closed 2026-06-15), verified:** the workflow assumes a role via `aws-actions/configure-aws-credentials` with OIDC (`role-to-assume` from a repo variable); the bootstrap layer defines the OIDC provider + repo-scoped trust; poam.md/OSCAL record the legacy user and secrets deleted. No action needed. | -| 3.2 app access-control ladder | **Already done:** stage throttling (POAM-023 closed), access logging (POAM-024 closed), and the full IdP upgrade (Cognito, POAM-021/022 closed) are live-verified. The CloudWatch metric-filter + alarm on credential-guessing was **not** built: Cognito lockout + gateway throttling structurally addressed the trigger, and the WAF pre-authorization stands on record in the POAM-023 closure text (PR #223). POAM-025 (hardware/phishing-resistant MFA for operator accounts) remains open by operator choice — TOTP keeps CMMC 3.5.3 green; the SSP now says exactly that (PR #222). | -| 3.3 audit retention (POAM-017/AU-11) | Log groups already at 365-day CMK (closed, verified). The missing piece was CloudTrail: **PR #225** adds a multi-region, validation-enabled management trail with 12-month active + Deep-Archive-to-30-months tiering; the deploy role deliberately cannot stop or delete it. Cost < $1/month. Needs one manual bootstrap apply (called out in the PR). | -| 3.4 external interconnection (POAM-020) | **Deferred, documented.** Bedrock migration was not executed (model/feature parity and app-code changes are an operator product decision; the app source lives outside this repo). Verified the SSP emits the interconnection only via the app's presence in inventory. The annual terms-verification task exists implicitly via the secret-rotation check; a calendarized terms review is listed as follow-up. | -| 3.5 DNSSEC | **Enabled all along** (live: `SIGNING`; TF manages the KSK). The false claim was the signal saying "not enabled" — fixed in PR #219. The baseline strings remain type-level constants rather than live-derived; deriving them from config is noted as follow-up hardening, with the reconciliation gate as the drift backstop. | -| 3.6 vulnerability evidence | **Mostly already done on main:** Syft/Grype SCA feeds the VDR (CVE-keyed ledger), monthly scheduled OWASP ZAP baseline exists (`zap-dast.yml`), Dependabot is configured. "Zero CVEs" is scanner-proven in the current pipeline. pip-audit for Python deps not separately added (Grype covers the built Lambda artifact). No action this pass. | -| 3.7 GuardDuty | **Not enabled — needs an operator cost decision.** Expected low single-digit $/month (within the stated ceiling) but it is a recurring spend on a detective service whose findings would also need a surfacing path into the runtime signal/VDR; flagged rather than silently enabled. | - -## Phase 4 — framework profile currency - -Not executed this pass (P2–P3): TX-RAMP PM 4.0 baseline re-derivation (4.1), -800-171A objective decomposition + inherited-count re-derive (4.2), GovRAMP/ -CJIS re-run + conditional CJI trigger template (4.3), FedRAMP OSCAL validator -run (4.4). 4.2/4.3 depend on the 1.2 re-dispositions (PR #222) merging first, -so sequencing them after this batch is correct, not just convenient. - -## Deliverables - -| PR | Branch | What | -|---|---|---| -| #218 | fix/logs-bucket-costcenter-tag | CostCenter tag → clears v-0015 | -| #219 | fix/signal-baseline-truth | DNSSEC/retention narrative truth in the signal + SIEM section | -| #220 | fix/ssp-downgrade-attribution | SSP partial-downgrade follows per-KSI verdict | -| #221 | fix/runtime-emitter-all-buckets | Runtime emitter validates every inventory bucket | -| #222 | fix/ssp-auth-controls-from-inventory | IA-2*/IA-8/AC-7/AC-12 derived from inventory | -| #223 | docs/human-surfaces-currency | README / poam.md narratives / architecture-decisions / mirror page | -| #224 | docs/scn-002-cognito-auth | SCN backfill for the auth change | -| #225 | infra/cloudtrail-management-trail | CloudTrail trail + bootstrap grant (stacked on #219) | - -Live changes applied directly (additive, reversible, verified): website-bucket -classification tags (2026-07-06; next runtime emission clears r-0000). - -CodeGuard (software-security) ran against every PR diff; no findings. All -branches pass the python suite; figure/reconcile gates run in CI per normal. - -## Not completed, and why - -1. **2.1 second independent method (P1).** Requires verifying the correct - Prowler Class-C/moderate framework id, an SDR schema decision for per-KSI - verification-method fields, and a result-ingestion path that doesn't - involve CI pushing to main. Shipping a guessed framework name or a - half-wired merge would violate the don't-fabricate rule. Concrete next - step: one PR adding `prowler.yml` (monthly, OIDC read-only role) + a - `data/verification/prowler-ksi-map.json` consumed by `build-sdr.py`. -2. **VDR risk-accepted count basis + 3 null poam_refs (1.4 tail).** Needs a - counting-basis decision (findings vs suppressions vs POA&M items) that - should be made once, in the VDR generator, with the operator's definition. -3. **3.4 Bedrock migration** — operator product decision; app source is in a - separate repository. -4. **3.7 GuardDuty** — recurring-cost + findings-surfacing decision; flagged. -5. **Phase 4 items** — sequenced behind PR #222 by design. -6. **POAM-025 hardware token** — operator-physical action, unchanged. - -## Operator actions needed now - -1. Review/merge PRs #218–#224 (independent; any order). For #225: apply the - bootstrap layer first (new `cloudtrail-management` deploy-role policy), - then merge #219, retarget #225 to main, merge. -2. After the next daily deploy + runtime emission: confirm the dashboard/SDR - show 46/46 passing and the SSP has no unexplained partials. -3. Decide: GuardDuty (3.7), Bedrock migration (3.4), and the Prowler - second-method PR (2.1) — say the word and each becomes its own branch. diff --git a/data/PROVENANCE.md b/data/PROVENANCE.md index 0f802a12..38e88c80 100644 --- a/data/PROVENANCE.md +++ b/data/PROVENANCE.md @@ -1,19 +1,23 @@ # `data/` — Authoritative source provenance -All control catalogs, baseline profiles, and crosswalks under `data/` are vendored -verbatim from authoritative sources at pinned commits. Nothing here is hand-keyed or -reconstructed; each file is a byte-identical copy from the commit recorded below. +The control catalog and baseline profiles under `data/` are vendored verbatim from +authoritative sources at pinned commits. Nothing here is hand-keyed or reconstructed; +each file is a byte-identical copy from the commit recorded below. Retrieval date: **2026-06-09**. -## NIST OSCAL control catalogs +The CMMC (800-171), GovRAMP and TX-RAMP inputs, the Rev 4 catalog and crosswalks, the +FedRAMP High baseline and the OSCAL schemas that used to live here were removed with +the framework figures they fed (git history keeps them). What remains is what the +Rev 5 Moderate view of the Security Decision Record reads. + +## NIST OSCAL control catalog - **Source:** `usnistgov/oscal-content` — https://github.com/usnistgov/oscal-content - **Pinned commit:** `78650f02ad9321bb7b817846f8fbd4f2bcd620de` - **Vendored:** - - `catalogs/NIST_SP-800-53_rev5_catalog.json` — NIST SP 800-53 Rev 5 control catalog (the hub catalog). - - `catalogs/NIST_SP-800-53_rev4_catalog.json` — NIST SP 800-53 Rev 4 control catalog (Rev4-bridge target). -- **Authority:** NIST maintains the official OSCAL representations of SP 800-53 Rev 4/5. + - `catalogs/NIST_SP-800-53_rev5_catalog.json` — NIST SP 800-53 Rev 5 control catalog (control titles for `scripts/sync-ksi-catalog.py`). +- **Authority:** NIST maintains the official OSCAL representations of SP 800-53 Rev 5. -## FedRAMP Rev 5 OSCAL baselines +## FedRAMP Rev 5 OSCAL baseline - **Source:** `OSCAL-Foundation/fedramp-resources` — https://github.com/OSCAL-Foundation/fedramp-resources - **Pinned commit:** `383977291aad960b0811faf6ebf5a893b0811f7f` - **Relocation note:** FedRAMP's machine-readable OSCAL content **moved** from @@ -22,42 +26,8 @@ Retrieval date: **2026-06-09**. machine-readable packages, https://www.fedramp.gov/rfcs/0024/). The old GSA repo path no longer resolves; this repo is the current authoritative home. - **Vendored:** - - `profiles/FedRAMP_rev5_MODERATE-baseline_profile.json` — FedRAMP Rev 5 Moderate **profile** (imports the 800-53 Rev5 catalog; 323 controls selected, 264 `set-parameters`, 4 `alters`). - - `profiles/FedRAMP_rev5_HIGH-baseline_profile.json` — FedRAMP Rev 5 High profile (needed for the "narrow High" control absorption). - - `profiles/FedRAMP_rev5_MODERATE-baseline-resolved-profile_catalog.json` — FedRAMP-published **resolved** Moderate catalog. - - `profiles/FedRAMP_rev5_HIGH-baseline-resolved-profile_catalog.json` — FedRAMP-published resolved High catalog. - - The `*-resolved-profile_catalog.json` files are FedRAMP's own resolution output; they - are used as a **correctness oracle** — our in-house resolver resolves the profile and - its result is diffed against this published catalog to prove the resolver is correct. - -## Control Mappings (`mappings/`) — derived, OSCAL Control Mapping Model v1.2.x -- `mappings/SP800-53_rev4-to-rev5.mapping.json` — Rev4→Rev5 control mapping, **derived - deterministically from the two vendored NIST catalogs** by `scripts/staged/build-control-mapping.py` - (same-id active → `equivalent`; controls withdrawn in Rev5 → the Rev5 catalog's *own* - `incorporated-into`/`moved-to` link → `subset-of`). 919/922 mapped; 3 residue (no clean - single successor) recorded in the document. No hand-keyed crosswalk. - -## 800-171 Rev 2 (CMMC) -- `catalogs/NIST_SP-800-171_rev2_catalog.json` — OSCAL catalog of the 110 requirements, - built by `scripts/staged/build-171-catalog.py` from NIST's authoritative machine-readable - export. NIST does not publish 800-171 as OSCAL, so this is derived from the NIST source - (not a community conversion). -- `sources/sp800-171r2-security-reqs.csv` — the source, vendored from the citable NIST URL: - https://csrc.nist.gov/csrc/media/Publications/sp/800-171/rev-2/final/documents/sp800-171r2-security-reqs.csv - -## Pending (sourced at their respective checkpoints) -- **171 Rev2 → 800-53 Rev4 crosswalk** (the CMMC projection rail) — NOT yet sourced. Lives in - 800-171 Rev2 **Appendix D** (publication, not a standalone file) or **NIST CPRT - `relationships`**. The CSF-v1.0→171 mapping is a *different* crosswalk (CSF, not 800-53). - -## OSCAL JSON schemas (validation gate) -- `schemas/oscal/oscal_{component,mapping,ssp}_schema.json` — vendored from the - **usnistgov/OSCAL v1.2.2** release. Used by `scripts/staged/validate-oscal.py`. (Patterns - are stripped at validation time — OSCAL's ECMA `\p{}` regex is incompatible with - Python `re`; structure/required/enums are still enforced. Full Metaschema constraint - validation via NIST `oscal-cli` is the CI gold standard.) + - `profiles/FedRAMP_rev5_MODERATE-baseline_profile.json` — FedRAMP Rev 5 Moderate **profile** (imports the 800-53 Rev5 catalog; 323 controls selected, 264 `set-parameters`, 4 `alters`). `scripts/_controls.py` reads its parameter values. + - `profiles/FedRAMP_rev5_MODERATE-baseline-resolved-profile_catalog.json` — FedRAMP-published **resolved** Moderate catalog. `scripts/_controls.py` reads the baseline's control set from it. ## Target OSCAL version -All authored artifacts target **OSCAL v1.2.x** (current release v1.2.2; the Control Mapping -Model is released and stable as of v1.2.0). +The authored component definition (`component-definitions/`) targets **OSCAL v1.2.x**. diff --git a/data/agency-access-exercise.json b/data/agency-access-exercise.json new file mode 100644 index 00000000..411c2baa --- /dev/null +++ b/data/agency-access-exercise.json @@ -0,0 +1,23 @@ +{ + "_note": "The agency-access exercise the deploy runs (scripts/agency-access.py exercise). Every agency here is fictional and every date is a business-day offset from the day it runs, so the 5-business-day denial clock is exercised against today's calendar. Nobody decides anything by hand: each access request is decided by the script's fixed rules on the day it arrives, and the automated notifier writes each denial notice to the simulated FedRAMP after the delay given here (null is a notifier outage that has not ended). The exercise fails the deploy unless every outcome in `expected` is observed, including the late and overdue notices the processor must catch.", + "disclaimer": "SIMULATED (DEC-194). These agencies do not exist, no federal agency has requested access, and nothing is sent to FedRAMP or anyone: a denial notice is this log entry. Any resemblance to a real agency is the result of a very tired naming committee.", + "requests": [ + {"id": "AAR-X01", "agency": "Department of Hypothetical Affairs (simulated)", "system": "Hypothetical Records Portal", "kind": "access", "channel": "simulated request", "asks": "To be on record as reading the package.", "received_on_offset": -9}, + {"id": "AAR-X02", "agency": "Bureau of Made-Up Statistics (simulated)", "system": "Totally Average Dashboard", "kind": "access", "channel": "simulated request", "asks": "Write access to the website, to round the numbers up.", "received_on_offset": -8, "notifier_delay_business_days": 4}, + {"id": "AAR-X03", "agency": "Office of Strictly Imaginary Procurement (simulated)", "kind": "access", "channel": "simulated request", "asks": "The whole package, by fax, in triplicate.", "received_on_offset": -2, "notifier_delay_business_days": 4}, + {"id": "AAR-X04", "agency": "Agency of Unverifiable Claims (simulated)", "kind": "access", "channel": "simulated request", "asks": "Access, on the strength of a very confident letterhead.", "received_on_offset": -12, "notifier_delay_business_days": 7}, + {"id": "AAR-X05", "agency": "Department of Hypothetical Affairs (simulated)", "system": "Second Opinion Service", "kind": "access", "channel": "simulated request", "asks": "To be on record for a second system.", "received_on_offset": -7}, + {"id": "AAR-X06", "agency": "Department of Hypothetical Affairs (simulated)", "system": "Second Opinion Service", "kind": "withdrawal", "channel": "simulated request", "received_on_offset": -1, "withdraws": "AAR-X05"}, + {"id": "AAR-X07", "agency": "Commission on Rhetorical Questions (simulated)", "kind": "access", "channel": "simulated request", "asks": "Is access really necessary? If so, the raw logs.", "received_on_offset": -7, "notifier_delay_business_days": null}, + {"id": "AAR-X08", "agency": "FedRAMP (simulated)", "kind": "inventory-request", "channel": "simulated request", "received_on_offset": -1} + ], + "expected": { + "AAR-X01": "in inventory", + "AAR-X02": "denial notice on time", + "AAR-X03": "denial notice pending", + "AAR-X04": "denial notice late", + "AAR-X05": "withdrawn", + "AAR-X07": "denial notice overdue", + "AAR-X08": "inventory supplied" + } +} diff --git a/data/agency-access.json b/data/agency-access.json new file mode 100644 index 00000000..58e287c0 --- /dev/null +++ b/data/agency-access.json @@ -0,0 +1,5 @@ +{ + "schema": "agency-access/1", + "_note": "The register of agency access requests, decisions and withdrawals (CDS-TRC-AAI, CDS-UTC-AAD); procedure in docs/procedures/agency-access.md, read by scripts/agency-access.py, which the deploy runs. No engagement (DEC-194): no real agency or FedRAMP request is taken, so the list is empty, and validation fails the deploy on any entry that is not `simulated: true` for an agency named '... (simulated)'. Records name agencies and systems, never people. The mechanism is exercised on every deploy with plainly fictional agencies (data/agency-access-exercise.json).", + "requests": [] +} diff --git a/data/baselines/govramp-txramp-cjis.selections.json b/data/baselines/govramp-txramp-cjis.selections.json deleted file mode 100644 index 3ef6ece5..00000000 --- a/data/baselines/govramp-txramp-cjis.selections.json +++ /dev/null @@ -1,807 +0,0 @@ -{ - "_provenance": "GovRAMP Moderate Rev5 + CJIS overlay from GovRAMP-Controls-Matrix_Mod_Rev5_V1.11_01302026_CJIS.xlsx (sheet 12_Mod Controls, 'Required for Authorized'=Yes). TX-RAMP L1/L2 from 'TX-RAMP Security Control Baselines 2021-11-29.xlsx' (Combined sheet).", - "baselines": { - "govramp_moderate_cjis": { - "revision": "rev5", - "catalog": "800-53 Rev5", - "controls": [ - "ac-1", - "ac-11", - "ac-11.1", - "ac-12", - "ac-14", - "ac-17", - "ac-17.1", - "ac-17.2", - "ac-17.3", - "ac-17.4", - "ac-18", - "ac-18.1", - "ac-18.3", - "ac-19", - "ac-19.5", - "ac-2", - "ac-2.1", - "ac-2.12", - "ac-2.13", - "ac-2.2", - "ac-2.3", - "ac-2.4", - "ac-2.5", - "ac-2.7", - "ac-2.9", - "ac-20", - "ac-20.1", - "ac-20.2", - "ac-21", - "ac-22", - "ac-3", - "ac-3.14", - "ac-4", - "ac-4.21", - "ac-5", - "ac-6", - "ac-6.1", - "ac-6.10", - "ac-6.2", - "ac-6.5", - "ac-6.7", - "ac-6.9", - "ac-7", - "ac-8", - "at-1", - "at-2", - "at-2.2", - "at-2.3", - "at-3", - "at-3.5", - "at-4", - "au-1", - "au-11", - "au-12", - "au-2", - "au-3", - "au-3.1", - "au-3.3", - "au-4", - "au-5", - "au-6", - "au-6.1", - "au-6.3", - "au-7", - "au-7.1", - "au-8", - "au-9", - "au-9.4", - "ca-1", - "ca-2", - "ca-2.1", - "ca-2.3", - "ca-3", - "ca-5", - "ca-6", - "ca-7", - "ca-7.1", - "ca-7.4", - "ca-8", - "ca-8.1", - "ca-9", - "cm-1", - "cm-10", - "cm-11", - "cm-12", - "cm-12.1", - "cm-2", - "cm-2.2", - "cm-2.3", - "cm-2.7", - "cm-3", - "cm-3.2", - "cm-3.4", - "cm-4", - "cm-4.2", - "cm-5", - "cm-5.1", - "cm-5.5", - "cm-6", - "cm-6.1", - "cm-7", - "cm-7.1", - "cm-7.2", - "cm-7.5", - "cm-8", - "cm-8.1", - "cm-8.3", - "cm-9", - "cp-1", - "cp-10", - "cp-10.2", - "cp-2", - "cp-2.1", - "cp-2.3", - "cp-2.8", - "cp-3", - "cp-4", - "cp-4.1", - "cp-6", - "cp-6.1", - "cp-6.3", - "cp-7", - "cp-7.1", - "cp-7.2", - "cp-7.3", - "cp-8", - "cp-8.1", - "cp-8.2", - "cp-9", - "cp-9.1", - "cp-9.8", - "ia-0", - "ia-1", - "ia-11", - "ia-12", - "ia-12.2", - "ia-12.3", - "ia-12.5", - "ia-2", - "ia-2.1", - "ia-2.12", - "ia-2.2", - "ia-2.5", - "ia-2.6", - "ia-2.8", - "ia-3", - "ia-4", - "ia-4.4", - "ia-5", - "ia-5.1", - "ia-5.2", - "ia-5.6", - "ia-5.7", - "ia-5.j", - "ia-5.k", - "ia-5.l", - "ia-5.m", - "ia-5.n", - "ia-5.o", - "ia-6", - "ia-7", - "ia-8", - "ia-8.1", - "ia-8.2", - "ia-8.4", - "ir-1", - "ir-2", - "ir-2.3", - "ir-3", - "ir-3.2", - "ir-4", - "ir-4.1", - "ir-5", - "ir-6", - "ir-6.1", - "ir-6.3", - "ir-7", - "ir-7.1", - "ir-8", - "ir-8.1", - "ir-9", - "ir-9.2", - "ir-9.3", - "ir-9.4", - "ma-1", - "ma-2", - "ma-3", - "ma-3.1", - "ma-3.2", - "ma-3.3", - "ma-4", - "ma-5", - "ma-5.1", - "ma-6", - "mp-1", - "mp-2", - "mp-3", - "mp-4", - "mp-5", - "mp-6", - "mp-7", - "pe-1", - "pe-10", - "pe-11", - "pe-12", - "pe-13", - "pe-13.1", - "pe-13.2", - "pe-14", - "pe-15", - "pe-16", - "pe-17", - "pe-2", - "pe-3", - "pe-4", - "pe-5", - "pe-6", - "pe-6.1", - "pe-8", - "pe-8.3", - "pe-9", - "pl-1", - "pl-10", - "pl-11", - "pl-2", - "pl-4", - "pl-4.1", - "pl-8", - "pl-9", - "ps-1", - "ps-2", - "ps-3", - "ps-3.3", - "ps-4", - "ps-5", - "ps-6", - "ps-7", - "ps-8", - "ps-9", - "ra-1", - "ra-2", - "ra-3", - "ra-3.1", - "ra-5", - "ra-5.11", - "ra-5.2", - "ra-5.3", - "ra-5.5", - "ra-7", - "ra-9", - "sa-1", - "sa-10", - "sa-11", - "sa-11.1", - "sa-11.2", - "sa-15", - "sa-15.3", - "sa-2", - "sa-22", - "sa-3", - "sa-4", - "sa-4.1", - "sa-4.2", - "sa-4.9", - "sa-5", - "sa-8", - "sa-9", - "sa-9.1", - "sa-9.2", - "sa-9.5", - "sc-1", - "sc-10", - "sc-12", - "sc-13", - "sc-15", - "sc-17", - "sc-18", - "sc-2", - "sc-20", - "sc-21", - "sc-22", - "sc-23", - "sc-28", - "sc-28.1", - "sc-39", - "sc-4", - "sc-45", - "sc-45.1", - "sc-5", - "sc-7", - "sc-7.12", - "sc-7.18", - "sc-7.23", - "sc-7.3", - "sc-7.4", - "sc-7.5", - "sc-7.7", - "sc-7.8", - "sc-8", - "sc-8.1", - "si-1", - "si-10", - "si-11", - "si-12", - "si-12.1", - "si-12.2", - "si-12.3", - "si-16", - "si-2", - "si-2.2", - "si-2.3", - "si-3", - "si-4", - "si-4.1", - "si-4.16", - "si-4.18", - "si-4.2", - "si-4.23", - "si-4.4", - "si-4.5", - "si-5", - "si-6", - "si-7", - "si-7.1", - "si-7.7", - "si-8", - "si-8.2", - "sr-1", - "sr-10", - "sr-11", - "sr-11.1", - "sr-11.2", - "sr-12", - "sr-2", - "sr-2.1", - "sr-3", - "sr-5", - "sr-6", - "sr-8" - ] - }, - "txramp_level1": { - "revision": "rev4", - "catalog": "800-53 Rev4", - "controls": [ - "ac-1", - "ac-14", - "ac-17", - "ac-18", - "ac-19", - "ac-2", - "ac-20", - "ac-22", - "ac-3", - "ac-7", - "ac-8", - "at-1", - "at-2", - "at-3", - "at-4", - "au-1", - "au-11", - "au-12", - "au-2", - "au-3", - "au-4", - "au-5", - "au-6", - "au-8", - "au-9", - "ca-1", - "ca-2", - "ca-2.1", - "ca-3", - "ca-5", - "ca-6", - "ca-7", - "ca-9", - "cm-1", - "cm-10", - "cm-11", - "cm-2", - "cm-4", - "cm-6", - "cm-7", - "cm-8", - "cp-1", - "cp-10", - "cp-2", - "cp-3", - "cp-4", - "cp-9", - "ia-1", - "ia-2", - "ia-2.1", - "ia-2.12", - "ia-4", - "ia-5", - "ia-5.1", - "ia-5.11", - "ia-6", - "ia-7", - "ia-8", - "ia-8.2", - "ia-8.3", - "ir-1", - "ir-2", - "ir-4", - "ir-5", - "ir-6", - "ir-7", - "ir-8", - "ir-9", - "ma-1", - "ma-2", - "ma-4", - "ma-5", - "mp-1", - "mp-2", - "mp-6", - "mp-7", - "pe-1", - "pe-13", - "pe-14", - "pe-15", - "pe-16", - "pe-2", - "pe-3", - "pe-6", - "pe-8", - "pl-1", - "pl-2", - "pl-4", - "ps-1", - "ps-2", - "ps-3", - "ps-4", - "ps-5", - "ps-6", - "ps-7", - "ps-8", - "ra-1", - "ra-2", - "ra-3", - "ra-5", - "sa-1", - "sa-2", - "sa-3", - "sa-4", - "sa-4.1", - "sa-5", - "sa-9", - "sc-1", - "sc-15", - "sc-20", - "sc-21", - "sc-22", - "sc-39", - "sc-5", - "sc-7", - "si-1", - "si-12", - "si-16", - "si-2", - "si-3", - "si-4", - "si-5" - ] - }, - "txramp_level2": { - "revision": "rev4", - "catalog": "800-53 Rev4", - "controls": [ - "ac-1", - "ac-10", - "ac-11", - "ac-11.1", - "ac-12", - "ac-14", - "ac-17", - "ac-17.1", - "ac-17.2", - "ac-17.3", - "ac-17.4", - "ac-17.9", - "ac-18", - "ac-18.1", - "ac-19", - "ac-19.5", - "ac-2", - "ac-2.1", - "ac-2.10", - "ac-2.12", - "ac-2.2", - "ac-2.3", - "ac-2.4", - "ac-2.5", - "ac-2.7", - "ac-2.9", - "ac-20", - "ac-20.1", - "ac-20.2", - "ac-21", - "ac-22", - "ac-3", - "ac-4", - "ac-4.21", - "ac-5", - "ac-6", - "ac-6.1", - "ac-6.10", - "ac-6.2", - "ac-6.5", - "ac-6.9", - "ac-7", - "ac-8", - "at-1", - "at-2", - "at-2.2", - "at-3", - "at-4", - "au-1", - "au-11", - "au-12", - "au-2", - "au-2.3", - "au-3", - "au-3.1", - "au-4", - "au-5", - "au-6", - "au-6.1", - "au-6.3", - "au-7", - "au-7.1", - "au-8", - "au-8.1", - "au-9", - "au-9.2", - "au-9.4", - "ca-1", - "ca-2", - "ca-2.1", - "ca-2.2", - "ca-2.3", - "ca-3", - "ca-3.3", - "ca-3.5", - "ca-5", - "ca-6", - "ca-7", - "ca-7.1", - "ca-8", - "ca-8.1", - "ca-9", - "cm-1", - "cm-10", - "cm-10.1", - "cm-11", - "cm-2", - "cm-2.1", - "cm-2.2", - "cm-2.3", - "cm-2.7", - "cm-3", - "cm-3.2", - "cm-4", - "cm-5", - "cm-5.1", - "cm-5.3", - "cm-5.5", - "cm-6", - "cm-6.1", - "cm-7", - "cm-7.1", - "cm-7.2", - "cm-7.5", - "cm-8", - "cm-8.1", - "cm-8.3", - "cm-8.5", - "cm-9", - "cp-1", - "cp-10", - "cp-10.2", - "cp-2", - "cp-2.1", - "cp-2.2", - "cp-2.3", - "cp-2.8", - "cp-3", - "cp-4", - "cp-4.1", - "cp-6", - "cp-6.1", - "cp-6.3", - "cp-7", - "cp-7.1", - "cp-7.2", - "cp-7.3", - "cp-8", - "cp-8.1", - "cp-8.2", - "cp-9", - "cp-9.1", - "cp-9.3", - "ia-1", - "ia-2", - "ia-2.1", - "ia-2.11", - "ia-2.12", - "ia-2.2", - "ia-2.3", - "ia-2.5", - "ia-2.8", - "ia-3", - "ia-4", - "ia-4.4", - "ia-5", - "ia-5.1", - "ia-5.11", - "ia-5.2", - "ia-5.3", - "ia-5.4", - "ia-5.6", - "ia-5.7", - "ia-6", - "ia-7", - "ia-8", - "ia-8.2", - "ia-8.3", - "ir-1", - "ir-2", - "ir-3", - "ir-3.2", - "ir-4", - "ir-4.1", - "ir-5", - "ir-6", - "ir-6.1", - "ir-7", - "ir-7.1", - "ir-7.2", - "ir-8", - "ir-9", - "ir-9.1", - "ir-9.2", - "ir-9.3", - "ir-9.4", - "ma-1", - "ma-2", - "ma-3", - "ma-3.1", - "ma-3.2", - "ma-3.3", - "ma-4", - "ma-4.2", - "ma-5", - "ma-5.1", - "ma-6", - "mp-1", - "mp-2", - "mp-3", - "mp-4", - "mp-5", - "mp-5.4", - "mp-6", - "mp-6.2", - "mp-7", - "mp-7.1", - "pe-1", - "pe-10", - "pe-11", - "pe-12", - "pe-13", - "pe-13.2", - "pe-13.3", - "pe-14", - "pe-14.2", - "pe-15", - "pe-16", - "pe-17", - "pe-2", - "pe-3", - "pe-4", - "pe-5", - "pe-6", - "pe-6.1", - "pe-8", - "pe-9", - "pl-1", - "pl-2", - "pl-2.3", - "pl-4", - "pl-4.1", - "pl-8", - "ps-1", - "ps-2", - "ps-3", - "ps-4", - "ps-5", - "ps-6", - "ps-7", - "ps-8", - "ra-1", - "ra-2", - "ra-3", - "ra-5", - "ra-5.1", - "ra-5.2", - "ra-5.3", - "ra-5.5", - "ra-5.6", - "ra-5.8", - "sa-1", - "sa-10", - "sa-10.1", - "sa-11", - "sa-11.1", - "sa-11.2", - "sa-11.8", - "sa-2", - "sa-3", - "sa-4", - "sa-4.1", - "sa-4.2", - "sa-4.8", - "sa-4.9", - "sa-5", - "sa-8", - "sa-9", - "sa-9.1", - "sa-9.2", - "sa-9.4", - "sa-9.5", - "sc-1", - "sc-10", - "sc-12", - "sc-12.2", - "sc-12.3", - "sc-13", - "sc-15", - "sc-17", - "sc-18", - "sc-19", - "sc-2", - "sc-20", - "sc-21", - "sc-22", - "sc-23", - "sc-28", - "sc-28.1", - "sc-39", - "sc-4", - "sc-5", - "sc-6", - "sc-7", - "sc-7.12", - "sc-7.13", - "sc-7.18", - "sc-7.3", - "sc-7.4", - "sc-7.5", - "sc-7.7", - "sc-7.8", - "sc-8", - "sc-8.1", - "si-1", - "si-10", - "si-11", - "si-12", - "si-16", - "si-2", - "si-2.2", - "si-2.3", - "si-3", - "si-3.1", - "si-3.2", - "si-3.7", - "si-4", - "si-4.1", - "si-4.14", - "si-4.16", - "si-4.2", - "si-4.23", - "si-4.4", - "si-4.5", - "si-5", - "si-6", - "si-7", - "si-7.1", - "si-7.7", - "si-8", - "si-8.1", - "si-8.2" - ] - } - }, - "cjis_specific_note": "GovRAMP+CJIS selection includes CJIS-specific items (ia-0, ia-5.j..o) that are not standard 800-53 controls; they surface as residue against an 800-53 hub." -} \ No newline at end of file diff --git a/data/catalogs/NIST_SP-800-171_rev2_catalog.json b/data/catalogs/NIST_SP-800-171_rev2_catalog.json deleted file mode 100644 index 002db247..00000000 --- a/data/catalogs/NIST_SP-800-171_rev2_catalog.json +++ /dev/null @@ -1,3398 +0,0 @@ -{ - "catalog": { - "uuid": "482584fc-3502-5f9b-8a0e-33f657028ab1", - "metadata": { - "title": "NIST SP 800-171 Revision 2 \u2014 Protecting CUI in Nonfederal Systems", - "last-modified": "2026-06-10T00:00:00Z", - "version": "Rev 2", - "oscal-version": "1.2.2", - "remarks": "Derived from NIST's authoritative machine-readable export (sp800-171r2-security-reqs.xlsx). The 110 security requirements = CMMC Level 2 (locked to Rev 2 by DoD class deviation)." - }, - "groups": [ - { - "id": "3.1", - "title": "Access Control", - "controls": [ - { - "id": "3.1.1", - "title": "3.1.1", - "props": [ - { - "name": "label", - "value": "3.1.1" - }, - { - "name": "sort-id", - "value": "03.01.01" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.1.1_smt", - "name": "statement", - "prose": "Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems)." - }, - { - "id": "3.1.1_gdn", - "name": "guidance", - "prose": "Access control policies (e.g., identity- or role-based policies, control matrices, and cryptography) control access between active entities or subjects (i.e., users or processes acting on behalf of users) and passive entities or objects (e.g., devices, files, records, and domains) in systems. Access enforcement mechanisms can be employed at the application and service level to provide increased information security. Other systems include systems internal and external to the organization. This requirement focuses on account management for systems and applications. The definition of and enforcement of access authorizations, other than those determined by account\ntype (e.g., privileged verses non-privileged) are addressed in requirement 3.1.2." - } - ] - }, - { - "id": "3.1.2", - "title": "3.1.2", - "props": [ - { - "name": "label", - "value": "3.1.2" - }, - { - "name": "sort-id", - "value": "03.01.02" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.1.2_smt", - "name": "statement", - "prose": "Limit system access to the types of transactions and functions that authorized users are permitted to execute." - }, - { - "id": "3.1.2_gdn", - "name": "guidance", - "prose": "Organizations may choose to define access privileges or other attributes by account, by type of account, or a combination of both. System account types include individual, shared, group, system, anonymous, guest, emergency, developer, manufacturer, vendor, and temporary. Other attributes required for authorizing access include restrictions on time-of-day, day-of-week, and point-of-origin. In defining other account attributes, organizations consider system-related requirements (e.g., system upgrades scheduled maintenance,) and mission or business requirements, (e.g., time zone differences, customer requirements, remote access to support travel requirements)." - } - ] - }, - { - "id": "3.1.3", - "title": "3.1.3", - "props": [ - { - "name": "label", - "value": "3.1.3" - }, - { - "name": "sort-id", - "value": "03.01.03" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.3_smt", - "name": "statement", - "prose": "Control the flow of CUI in accordance with approved authorizations." - }, - { - "id": "3.1.3_gdn", - "name": "guidance", - "prose": "Information flow control regulates where information can travel within a system and between systems (versus who can access the information) and without explicit regard to subsequent accesses to that information. Flow control restrictions include the following: keeping export-controlled information from being transmitted in the clear to the Internet; blocking outside traffic that claims to be from within the organization; restricting requests to the Internet that are not from the internal web proxy server; and limiting information transfers between organizations based on data structures and content. Organizations commonly use information flow control policies and enforcement mechanisms to control the flow of information between designated sources and destinations (e.g., networks, individuals, and devices) within systems and between interconnected systems. Flow control is based on characteristics of the information or the information path. Enforcement occurs in boundary protection devices (e.g., gateways, routers, guards, encrypted tunnels, firewalls) that employ rule sets or establish configuration settings that restrict system services, provide a packet-filtering capability based on header information, or message-filtering capability based on message content (e.g., implementing key word searches or using document characteristics). Organizations also consider the trustworthiness of filtering and inspection mechanisms (i.e., hardware, firmware, and software components) that are critical to information flow enforcement. Transferring information between systems representing different security domains with different security policies introduces risk that such transfers violate one or more domain security policies. In such situations, information owners or stewards provide guidance at designated policy enforcement points between interconnected systems. Organizations consider mandating specific architectural solutions when required to enforce specific security policies. Enforcement includes: prohibiting information transfers between interconnected systems (i.e., allowing access only); employing hardware mechanisms to enforce one-way information flows; and implementing trustworthy regrading mechanisms to reassign security attributes and security labels." - } - ] - }, - { - "id": "3.1.4", - "title": "3.1.4", - "props": [ - { - "name": "label", - "value": "3.1.4" - }, - { - "name": "sort-id", - "value": "03.01.04" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.4_smt", - "name": "statement", - "prose": "Separate the duties of individuals to reduce the risk of malevolent activity without collusion." - }, - { - "id": "3.1.4_gdn", - "name": "guidance", - "prose": "Separation of duties addresses the potential for abuse of authorized privileges and helps to reduce the risk of malevolent activity without collusion. Separation of duties includes dividing mission functions and system support functions among different individuals or roles; conducting system support functions with different individuals (e.g., configuration management, quality assurance and testing, system management, programming, and network security); and ensuring that security personnel administering access control functions do not also administer audit functions. Because separation of duty violations can span systems and application domains, organizations consider the entirety of organizational systems and system components when developing policy on separation of duties." - } - ] - }, - { - "id": "3.1.5", - "title": "3.1.5", - "props": [ - { - "name": "label", - "value": "3.1.5" - }, - { - "name": "sort-id", - "value": "03.01.05" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.5_smt", - "name": "statement", - "prose": "Employ the principle of least privilege, including for specific security functions and privileged accounts." - }, - { - "id": "3.1.5_gdn", - "name": "guidance", - "prose": "Organizations employ the principle of least privilege for specific duties and authorized accesses for users and processes. The principle of least privilege is applied with the goal of authorized privileges no higher than necessary to accomplish required organizational missions or business functions. Organizations consider the creation of additional processes, roles, and system accounts as necessary, to achieve least privilege. Organizations also apply least privilege to the development, implementation, and operation of organizational systems. Security functions include establishing system accounts, setting events to be logged, setting intrusion detection parameters, and configuring access authorizations (i.e., permissions, privileges). Privileged accounts, including super user accounts, are typically described as system administrator for various types of commercial off-the-shelf operating systems. Restricting privileged accounts to specific personnel or roles prevents day-to-day users from having access to privileged information or functions. Organizations may differentiate in the application of this requirement between allowed privileges for local accounts and for domain accounts provided organizations retain the ability to control system configurations for key security parameters and as otherwise necessary to sufficiently mitigate risk." - } - ] - }, - { - "id": "3.1.6", - "title": "3.1.6", - "props": [ - { - "name": "label", - "value": "3.1.6" - }, - { - "name": "sort-id", - "value": "03.01.06" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.6_smt", - "name": "statement", - "prose": "Use non-privileged accounts or roles when accessing nonsecurity functions" - }, - { - "id": "3.1.6_gdn", - "name": "guidance", - "prose": "This requirement limits exposure when operating from within privileged accounts or roles. The inclusion of roles addresses situations where organizations implement access control policies such as role-based access control and where a change of role provides the same degree of assurance in the change of access authorizations for the user and all processes acting on behalf of the user as would be provided by a change between a privileged and non-privileged account." - } - ] - }, - { - "id": "3.1.7", - "title": "3.1.7", - "props": [ - { - "name": "label", - "value": "3.1.7" - }, - { - "name": "sort-id", - "value": "03.01.07" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.7_smt", - "name": "statement", - "prose": "Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs." - }, - { - "id": "3.1.7_gdn", - "name": "guidance", - "prose": "Privileged functions include establishing system accounts, performing system integrity checks, conducting patching operations, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. Note that this requirement represents a condition to be achieved by the definition of authorized privileges in 3.1.2. Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Logging the use of privileged functions is one way to detect such misuse, and in doing so, help mitigate the risk from insider threats and the advanced persistent threat." - } - ] - }, - { - "id": "3.1.8", - "title": "3.1.8", - "props": [ - { - "name": "label", - "value": "3.1.8" - }, - { - "name": "sort-id", - "value": "03.01.08" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.8_smt", - "name": "statement", - "prose": "Limit unsuccessful logon attempts." - }, - { - "id": "3.1.8_gdn", - "name": "guidance", - "prose": "This requirement applies regardless of whether the logon occurs via a local or network connection. Due to the potential for denial of service, automatic lockouts initiated by systems are, in most cases, temporary and automatically release after a predetermined period established by the organization (i.e., a delay algorithm). If a delay algorithm is selected, organizations may employ different algorithms for different system components based on the capabilities of the respective components. Responses to unsuccessful logon attempts may be implemented at the operating system and application levels." - } - ] - }, - { - "id": "3.1.9", - "title": "3.1.9", - "props": [ - { - "name": "label", - "value": "3.1.9" - }, - { - "name": "sort-id", - "value": "03.01.09" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.9_smt", - "name": "statement", - "prose": "Provide privacy and security notices consistent with applicable CUI rules." - }, - { - "id": "3.1.9_gdn", - "name": "guidance", - "prose": "System use notifications can be implemented using messages or warning banners displayed before individuals log in to organizational systems. System use notifications are used only for access via logon interfaces with human users and are not required when such human interfaces do not exist. Based on a risk assessment, organizations consider whether a secondary system use notification is needed to access applications or other system resources after the initial network logon. Where necessary, posters or other printed materials may be used in lieu of an automated system banner. Organizations consult with the Office of General Counsel for legal review and approval of warning banner content" - } - ] - }, - { - "id": "3.1.10", - "title": "3.1.10", - "props": [ - { - "name": "label", - "value": "3.1.10" - }, - { - "name": "sort-id", - "value": "03.01.10" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.10_smt", - "name": "statement", - "prose": "Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity" - }, - { - "id": "3.1.10_gdn", - "name": "guidance", - "prose": "Session locks are temporary actions taken when users stop work and move away from the immediate vicinity of the system but do not want to log out because of the temporary nature of their absences. Session locks are implemented where session activities can be determined, typically at the operating system level (but can also be at the application level). Session locks are not an acceptable substitute for logging out of the system, for example, if organizations require users to log out at the end of the workday. Pattern-hiding displays can include static or dynamic images, for example, patterns used with screen savers, photographic images, solid colors, clock, battery life indicator, or a blank screen, with the additional caveat that none of the images convey controlled unclassified information." - } - ] - }, - { - "id": "3.1.11", - "title": "3.1.11", - "props": [ - { - "name": "label", - "value": "3.1.11" - }, - { - "name": "sort-id", - "value": "03.01.11" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.11_smt", - "name": "statement", - "prose": "Terminate (automatically) a user session after a defined condition." - }, - { - "id": "3.1.11_gdn", - "name": "guidance", - "prose": "This requirement addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., disconnecting from the network). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. Session termination terminates all processes associated with a user\u2019s logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated. Conditions or trigger events requiring automatic session termination can include organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on system use" - } - ] - }, - { - "id": "3.1.12", - "title": "3.1.12", - "props": [ - { - "name": "label", - "value": "3.1.12" - }, - { - "name": "sort-id", - "value": "03.01.12" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.12_smt", - "name": "statement", - "prose": "Monitor and control remote access sessions." - }, - { - "id": "3.1.12_gdn", - "name": "guidance", - "prose": "Remote access is access to organizational systems by users (or processes acting on behalf of users) communicating through external networks (e.g., the Internet). Remote access methods include dial-up, broadband, and wireless. Organizations often employ encrypted virtual private networks (VPNs) to enhance confidentiality over remote connections. The use of encrypted VPNs does not make the access non-remote; however, the use of VPNs, when adequately provisioned with appropriate control (e.g., employing encryption techniques for confidentiality protection), may provide sufficient assurance to the organization that it can effectively treat such connections as internal networks. VPNs with encrypted tunnels can affect the capability to adequately monitor network communications traffic for malicious code. Automated monitoring and control of remote access sessions allows organizations to detect cyber-attacks and help to ensure ongoing compliance with remote access policies by auditing connection activities of remote users on a variety of system components (e.g., servers, workstations, notebook computers, smart phones, and tablets). [SP 800-46], [SP 800-77], and [SP 800-113] provide guidance on secure remote access and virtual private networks." - } - ] - }, - { - "id": "3.1.13", - "title": "3.1.13", - "props": [ - { - "name": "label", - "value": "3.1.13" - }, - { - "name": "sort-id", - "value": "03.01.13" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.13_smt", - "name": "statement", - "prose": "Employ cryptographic mechanisms to protect the confidentiality of remote access sessions." - }, - { - "id": "3.1.13_gdn", - "name": "guidance", - "prose": "Cryptographic standards include FIPS-validated cryptography and NSA-approved cryptography. See [NIST CRYPTO]; [NIST CAVP]; [NIST CMVP]; National Security Agency Cryptographic Standards." - } - ] - }, - { - "id": "3.1.14", - "title": "3.1.14", - "props": [ - { - "name": "label", - "value": "3.1.14" - }, - { - "name": "sort-id", - "value": "03.01.14" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.14_smt", - "name": "statement", - "prose": "Route remote access via managed access control points." - }, - { - "id": "3.1.14_gdn", - "name": "guidance", - "prose": "Routing remote access through managed access control points enhances explicit, organizational control over such connections, reducing the susceptibility to unauthorized access to organizational systems resulting in the unauthorized disclosure of CUI." - } - ] - }, - { - "id": "3.1.15", - "title": "3.1.15", - "props": [ - { - "name": "label", - "value": "3.1.15" - }, - { - "name": "sort-id", - "value": "03.01.15" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.15_smt", - "name": "statement", - "prose": "Authorize remote execution of privileged commands and remote access to security-relevant information." - }, - { - "id": "3.1.15_gdn", - "name": "guidance", - "prose": "A privileged command is a human-initiated (interactively or via a process operating on behalf of the human) command executed on a system involving the control, monitoring, or administration of the system including security functions and associated security-relevant information. Security-relevant information is any information within the system that can potentially impact the operation of security functions or the provision of security services in a manner that could result in failure to enforce the system security policy or maintain isolation of code and data. Privileged commands give individuals the ability to execute sensitive, security-critical, or security-relevant system functions. Controlling such access from remote locations helps to ensure that unauthorized individuals are not able to execute such commands freely with the potential to do serious or catastrophic damage to organizational systems. Note that the ability to affect the integrity of the system is considered security-relevant as that could enable the means to by-pass security functions although not directly impacting the function itself." - } - ] - }, - { - "id": "3.1.16", - "title": "3.1.16", - "props": [ - { - "name": "label", - "value": "3.1.16" - }, - { - "name": "sort-id", - "value": "03.01.16" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.16_smt", - "name": "statement", - "prose": "Authorize wireless access prior to allowing such connections" - }, - { - "id": "3.1.16_gdn", - "name": "guidance", - "prose": "Establishing usage restrictions and configuration/connection requirements for wireless access to the system provides criteria for organizations to support wireless access authorization decisions. Such restrictions and requirements reduce the susceptibility to unauthorized access to the system through wireless technologies. Wireless networks use authentication protocols which provide credential protection and mutual authentication. [SP 800-97] provides guidance on secure wireless networks." - } - ] - }, - { - "id": "3.1.17", - "title": "3.1.17", - "props": [ - { - "name": "label", - "value": "3.1.17" - }, - { - "name": "sort-id", - "value": "03.01.17" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.17_smt", - "name": "statement", - "prose": "Protect wireless access using authentication and encryption" - }, - { - "id": "3.1.17_gdn", - "name": "guidance", - "prose": "Organizations authenticate individuals and devices to help protect wireless access to the system. Special attention is given to the wide variety of devices that are part of the Internet of Things with potential wireless access to organizational systems. See [NIST CRYPTO]." - } - ] - }, - { - "id": "3.1.18", - "title": "3.1.18", - "props": [ - { - "name": "label", - "value": "3.1.18" - }, - { - "name": "sort-id", - "value": "03.01.18" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.18_smt", - "name": "statement", - "prose": "Control connection of mobile devices." - }, - { - "id": "3.1.18_gdn", - "name": "guidance", - "prose": "A mobile device is a computing device that has a small form factor such that it can easily be carried by a single individual; is designed to operate without a physical connection (e.g., wirelessly transmit or receive information); possesses local, non-removable or removable data storage; and includes a self-contained power source. Mobile devices may also include voice communication capabilities, on-board sensors that allow the device to capture information, or built-in features for synchronizing local data with remote locations. Examples of mobile devices include smart phones, e-readers, and tablets. Due to the large variety of mobile devices with different technical characteristics and capabilities, organizational restrictions may vary for the different types of devices. Usage restrictions and implementation guidance for mobile devices include: device identification and authentication; configuration management; implementation of mandatory protective software (e.g., malicious code detection, firewall); scanning devices for malicious code; updating virus protection software; scanning for critical software updates and patches; conducting primary operating system (and possibly other resident software) integrity checks; and disabling unnecessary hardware (e.g., wireless, infrared). The need to provide adequate security for mobile devices goes beyond this requirement. Many controls for mobile devices are reflected in other CUI security requirements. [SP 800-124] provides guidance on mobile device security." - } - ] - }, - { - "id": "3.1.19", - "title": "3.1.19", - "props": [ - { - "name": "label", - "value": "3.1.19" - }, - { - "name": "sort-id", - "value": "03.01.19" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.19_smt", - "name": "statement", - "prose": "Encrypt CUI on mobile devices and mobile computing platforms.[23]" - }, - { - "id": "3.1.19_gdn", - "name": "guidance", - "prose": "Organizations can employ full-device encryption or container-based encryption to protect the confidentiality of CUI on mobile devices and computing platforms. Container-based encryption provides a more fine-grained approach to the encryption of data and information including encrypting selected data structures such as files, records, or fields. See [NIST CRYPTO].\n\n[23] Mobile devices and computing platforms include, for example, smartphones and tablets." - } - ] - }, - { - "id": "3.1.20", - "title": "3.1.20", - "props": [ - { - "name": "label", - "value": "3.1.20" - }, - { - "name": "sort-id", - "value": "03.01.20" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.20_smt", - "name": "statement", - "prose": "Verify and control/limit connections to and use of external systems." - }, - { - "id": "3.1.20_gdn", - "name": "guidance", - "prose": "External systems are systems or components of systems for which organizations typically have no direct supervision and authority over the application of security requirements and controls or the determination of the effectiveness of implemented controls on those systems. External systems include personally owned systems, components, or devices and privately-owned computing and communications devices resident in commercial or public facilities. This requirement also addresses the use of external systems for the processing, storage, or transmission of CUI, including accessing cloud services (e.g., infrastructure as a service, platform as a service, or software as a service) from organizational systems. Organizations establish terms and conditions for the use of external systems in accordance with organizational security policies and procedures. Terms and conditions address as a minimum, the types of applications that can be accessed on organizational systems from external systems. If terms and conditions with the owners of external systems cannot be established, organizations may impose restrictions on organizational personnel using those external systems. This requirement recognizes that there are circumstances where individuals using external systems (e.g., contractors, coalition partners) need to access organizational systems. In those situations, organizations need confidence that the external systems contain the necessary controls so as not to compromise, damage, or otherwise harm organizational systems. Verification that the required controls have been effectively implemented can be achieved by third-party, independent assessments, attestations, or other means, depending on the assurance or confidence level required by organizations. Note that while \u201cexternal\u201d typically refers to outside of the organization\u2019s direct supervision and authority, that is not always the case. Regarding the protection of CUI across an organization, the organization may have systems that process CUI and others that do not. And among the systems that process CUI there are likely access restrictions for CUI that apply between systems. Therefore, from the perspective of a given system, other systems within the organization may be considered \u201cexternal\" to that system." - } - ] - }, - { - "id": "3.1.21", - "title": "3.1.21", - "props": [ - { - "name": "label", - "value": "3.1.21" - }, - { - "name": "sort-id", - "value": "03.01.21" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.21_smt", - "name": "statement", - "prose": "Limit use of portable storage devices on external systems." - }, - { - "id": "3.1.21_gdn", - "name": "guidance", - "prose": "Limits on the use of organization-controlled portable storage devices in external systems include complete prohibition of the use of such devices or restrictions on how the devices may be used and under what conditions the devices may be used. Note that while \u201cexternal\u201d typically refers to outside of the organization\u2019s direct supervision and authority, that is not always the case. Regarding the protection of CUI across an organization, the organization may have systems that process CUI and others that do not. Among the systems that process CUI there are likely access restrictions for CUI that apply between systems. Therefore, from the perspective of a given system, other systems within the organization may be considered \u201cexternal\" to that system." - } - ] - }, - { - "id": "3.1.22", - "title": "3.1.22", - "props": [ - { - "name": "label", - "value": "3.1.22" - }, - { - "name": "sort-id", - "value": "03.01.22" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.1.22_smt", - "name": "statement", - "prose": "Control CUI posted or processed on publicly accessible systems." - }, - { - "id": "3.1.22_gdn", - "name": "guidance", - "prose": "In accordance with laws, Executive Orders, directives, policies, regulations, or standards, the public is not authorized access to nonpublic information (e.g., information protected under the Privacy Act, CUI, and proprietary information). This requirement addresses systems that are controlled by the organization and accessible to the public, typically without identification or authentication. Individuals authorized to post CUI onto publicly accessible systems are designated. The content of information is reviewed prior to posting onto publicly accessible systems to ensure that nonpublic information is not included." - } - ] - } - ] - }, - { - "id": "3.2", - "title": "Awareness and Training", - "controls": [ - { - "id": "3.2.1", - "title": "3.2.1", - "props": [ - { - "name": "label", - "value": "3.2.1" - }, - { - "name": "sort-id", - "value": "03.02.01" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.2.1_smt", - "name": "statement", - "prose": "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." - }, - { - "id": "3.2.1_gdn", - "name": "guidance", - "prose": "Organizations determine the content and frequency of security awareness training and security awareness techniques based on the specific organizational requirements and the systems to which personnel have authorized access. The content includes a basic understanding of the need for information security and user actions to maintain security and to respond to suspected security incidents. The content also addresses awareness of the need for operations security. Security awareness techniques include: formal training; offering supplies inscribed with security reminders; generating email advisories or notices from organizational officials; displaying logon screen messages; displaying security awareness posters; and conducting information security awareness events. [SP 800-50] provides guidance on security awareness and training programs." - } - ] - }, - { - "id": "3.2.2", - "title": "3.2.2", - "props": [ - { - "name": "label", - "value": "3.2.2" - }, - { - "name": "sort-id", - "value": "03.02.02" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.2.2_smt", - "name": "statement", - "prose": "Ensure that personnel are trained to carry out their assigned information security-related duties and responsibilities." - }, - { - "id": "3.2.2_gdn", - "name": "guidance", - "prose": "Organizations determine the content and frequency of security training based on the assigned duties, roles, and responsibilities of individuals and the security requirements of organizations and the systems to which personnel have authorized access. In addition, organizations provide system developers, enterprise architects, security architects, acquisition/procurement officials, software developers, system developers, systems integrators, system/network administrators, personnel conducting configuration management and auditing activities, personnel performing independent verification and validation, security assessors, and other personnel having access to system-level software, security-related technical training specifically tailored for their assigned duties. Comprehensive role-based training addresses management, operational, and technical roles and responsibilities covering physical, personnel, and technical controls. Such training can include policies, procedures, tools, and artifacts for the security roles defined. Organizations also provide the training necessary for individuals to carry out their responsibilities related to operations and supply chain security within the context of organizational information security programs. [SP 800-181] provides guidance on role-based information security training in the workplace. [SP 800-161] provides guidance on supply chain risk management." - } - ] - }, - { - "id": "3.2.3", - "title": "3.2.3", - "props": [ - { - "name": "label", - "value": "3.2.3" - }, - { - "name": "sort-id", - "value": "03.02.03" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.2.3_smt", - "name": "statement", - "prose": "Provide security awareness training on recognizing and reporting potential indicators of insider threat." - }, - { - "id": "3.2.3_gdn", - "name": "guidance", - "prose": "Potential indicators and possible precursors of insider threat include behaviors such as: inordinate, long-term job dissatisfaction; attempts to gain access to information that is not required for job performance; unexplained access to financial resources; bullying or sexual harassment of fellow employees; workplace violence; and other serious violations of the policies, procedures, directives, rules, or practices of organizations. Security awareness training includes how to communicate employee and management concerns regarding potential indicators of insider threat through appropriate organizational channels in accordance with established organizational policies and procedures. Organizations may consider tailoring insider threat awareness topics to the role (e.g., training for managers may be focused on specific changes in behavior of team members, while training for employees may be focused on more general observations)." - } - ] - } - ] - }, - { - "id": "3.3", - "title": "Audit and Accountability", - "controls": [ - { - "id": "3.3.1", - "title": "3.3.1", - "props": [ - { - "name": "label", - "value": "3.3.1" - }, - { - "name": "sort-id", - "value": "03.03.01" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.3.1_smt", - "name": "statement", - "prose": "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" - }, - { - "id": "3.3.1_gdn", - "name": "guidance", - "prose": "An event is any observable occurrence in a system, which includes unlawful or unauthorized system activity. Organizations identify event types for which a logging functionality is needed as those events which are significant and relevant to the security of systems and the environments in which those systems operate to meet specific and ongoing auditing needs. Event types can include password changes, failed logons or failed accesses related to systems, administrative privilege usage, or third-party credential usage. In determining event types that require logging, organizations consider the monitoring and auditing appropriate for each of the CUI security requirements. Monitoring and auditing requirements can be balanced with other system needs. For example, organizations may determine that systems must have the capability to log every file access both successful and unsuccessful, but not activate that capability except for specific circumstances due to the potential burden on system performance. Audit records can be generated at various levels of abstraction, including at the packet level as information traverses the network. Selecting the appropriate level of abstraction is a critical aspect of an audit logging capability and can facilitate the identification of root causes to problems. Organizations consider in the definition of event types, the logging necessary to cover related events such as the steps in distributed, transaction-based processes (e.g., processes that are distributed across multiple organizations) and actions that occur in service-oriented or cloud-based architectures. Audit record content that may be necessary to satisfy this requirement includes time stamps, source and destination addresses, user or process identifiers, event descriptions, success or fail indications, filenames involved, and access control or flow control rules invoked. Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the system after the event occurred). Detailed information that organizations may consider in audit records includes full text recording of privileged commands or the individual identities of group account users. Organizations consider limiting the additional audit log information to only that information explicitly needed for specific audit requirements. This facilitates the use of audit trails and audit logs by not including information that could potentially be misleading or could make it more difficult to locate information of interest. Audit logs are reviewed and analyzed as often as needed to provide important information to organizations to facilitate risk-based decision making. [SP 800-92] provides guidance on security log management." - } - ] - }, - { - "id": "3.3.2", - "title": "3.3.2", - "props": [ - { - "name": "label", - "value": "3.3.2" - }, - { - "name": "sort-id", - "value": "03.03.02" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.3.2_smt", - "name": "statement", - "prose": "Ensure that the actions of individual system users can be uniquely traced to those users, so they can be held accountable for their actions." - }, - { - "id": "3.3.2_gdn", - "name": "guidance", - "prose": "This requirement ensures that the contents of the audit record include the information needed to link the audit event to the actions of an individual to the extent feasible. Organizations consider logging for traceability including results from monitoring of account usage, remote access, wireless connectivity, mobile device connection, communications at system boundaries, configuration settings, physical access, nonlocal maintenance, use of maintenance tools, temperature and humidity, equipment delivery and removal, system component inventory, use of mobile code, and use of Voice over Internet Protocol (VoIP)." - } - ] - }, - { - "id": "3.3.3", - "title": "3.3.3", - "props": [ - { - "name": "label", - "value": "3.3.3" - }, - { - "name": "sort-id", - "value": "03.03.03" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.3.3_smt", - "name": "statement", - "prose": "Review and update logged events." - }, - { - "id": "3.3.3_gdn", - "name": "guidance", - "prose": "The intent of this requirement is to periodically re-evaluate which logged events will continue to be included in the list of events to be logged. The event types that are logged by organizations may change over time. Reviewing and updating the set of logged event types periodically is necessary to ensure that the current set remains necessary and sufficient." - } - ] - }, - { - "id": "3.3.4", - "title": "3.3.4", - "props": [ - { - "name": "label", - "value": "3.3.4" - }, - { - "name": "sort-id", - "value": "03.03.04" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.3.4_smt", - "name": "statement", - "prose": "Alert in the event of an audit logging process failure." - }, - { - "id": "3.3.4_gdn", - "name": "guidance", - "prose": "Audit logging process failures include software and hardware errors, failures in the audit record capturing mechanisms, and audit record storage capacity being reached or exceeded. This requirement applies to each audit record data storage repository (i.e., distinct system component where audit records are stored), the total audit record storage capacity of organizations (i.e., all audit record data storage repositories combined), or both." - } - ] - }, - { - "id": "3.3.5", - "title": "3.3.5", - "props": [ - { - "name": "label", - "value": "3.3.5" - }, - { - "name": "sort-id", - "value": "03.03.05" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.3.5_smt", - "name": "statement", - "prose": "Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity." - }, - { - "id": "3.3.5_gdn", - "name": "guidance", - "prose": "Correlating audit record review, analysis, and reporting processes helps to ensure that they do not operate independently, but rather collectively. Regarding the assessment of a given organizational system, the requirement is agnostic as to whether this correlation is applied at the system level or at the organization level across all systems." - } - ] - }, - { - "id": "3.3.6", - "title": "3.3.6", - "props": [ - { - "name": "label", - "value": "3.3.6" - }, - { - "name": "sort-id", - "value": "03.03.06" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.3.6_smt", - "name": "statement", - "prose": "Provide audit record reduction and report generation to support on-demand analysis and reporting." - }, - { - "id": "3.3.6_gdn", - "name": "guidance", - "prose": "Audit record reduction is a process that manipulates collected audit information and organizes such information in a summary format that is more meaningful to analysts. Audit record reduction and report generation capabilities do not always emanate from the same system or organizational entities conducting auditing activities. Audit record reduction capability can include, for example, modern data mining techniques with advanced data filters to identify anomalous behavior in audit records. The report generation capability provided by the system can help generate customizable reports. Time ordering of audit records can be a significant issue if the granularity of the time stamp in the record is insufficient." - } - ] - }, - { - "id": "3.3.7", - "title": "3.3.7", - "props": [ - { - "name": "label", - "value": "3.3.7" - }, - { - "name": "sort-id", - "value": "03.03.07" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.3.7_smt", - "name": "statement", - "prose": "Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records" - }, - { - "id": "3.3.7_gdn", - "name": "guidance", - "prose": "Internal system clocks are used to generate time stamps, which include date and time. Time is expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. The granularity of time measurements refers to the degree of synchronization between system clocks and reference clocks, for example, clocks synchronizing within hundreds of milliseconds or within tens of milliseconds. Organizations may define different time granularities for different system components. Time service can also be critical to other security capabilities such as access control and identification and authentication, depending on the nature of the mechanisms used to support those capabilities. This requirement provides uniformity of time stamps for systems with multiple system clocks and systems connected over a network. See [IETF 5905]." - } - ] - }, - { - "id": "3.3.8", - "title": "3.3.8", - "props": [ - { - "name": "label", - "value": "3.3.8" - }, - { - "name": "sort-id", - "value": "03.03.08" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.3.8_smt", - "name": "statement", - "prose": "Protect audit information and audit logging tools from unauthorized access, modification, and deletion." - }, - { - "id": "3.3.8_gdn", - "name": "guidance", - "prose": "Audit information includes all information (e.g., audit records, audit log settings, and audit reports) needed to successfully audit system activity. Audit logging tools are those programs and devices used to conduct audit and logging activities. This requirement focuses on the technical protection of audit information and limits the ability to access and execute audit logging tools to authorized individuals. Physical protection of audit information is addressed by media protection and physical and environmental protection requirements." - } - ] - }, - { - "id": "3.3.9", - "title": "3.3.9", - "props": [ - { - "name": "label", - "value": "3.3.9" - }, - { - "name": "sort-id", - "value": "03.03.09" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.3.9_smt", - "name": "statement", - "prose": "Limit management of audit logging functionality to a subset of privileged users." - }, - { - "id": "3.3.9_gdn", - "name": "guidance", - "prose": "Individuals with privileged access to a system and who are also the subject of an audit by that system, may affect the reliability of audit information by inhibiting audit logging activities or modifying audit records. This requirement specifies that privileged access be further defined between audit-related privileges and other privileges, thus limiting the users with audit-related privileges" - } - ] - } - ] - }, - { - "id": "3.4", - "title": "Configuration Management", - "controls": [ - { - "id": "3.4.1", - "title": "3.4.1", - "props": [ - { - "name": "label", - "value": "3.4.1" - }, - { - "name": "sort-id", - "value": "03.04.01" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.4.1_smt", - "name": "statement", - "prose": "Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles." - }, - { - "id": "3.4.1_gdn", - "name": "guidance", - "prose": "Baseline configurations are documented, formally reviewed, and agreed-upon specifications for systems or configuration items within those systems. Baseline configurations serve as a basis for future builds, releases, and changes to systems. Baseline configurations include information about system components (e.g., standard software packages installed on workstations, notebook computers, servers, network components, or mobile devices; current version numbers and update and patch information on operating systems and applications; and configuration settings and parameters), network topology, and the logical placement of those components within the system architecture. Baseline configurations of systems also reflect the current enterprise architecture. Maintaining effective baseline configurations requires creating new baselines as organizational systems change over time. Baseline configuration maintenance includes reviewing and updating the baseline configuration when changes are made based on security risks and deviations from the established baseline configuration. Organizations can implement centralized system component inventories that include components from multiple organizational systems. In such situations, organizations ensure that the resulting inventories include system-specific information required for proper component accountability (e.g., system association, system owner). Information deemed necessary for effective accountability of system components includes hardware inventory specifications, software license information, software version numbers, component owners, and for networked components or devices, machine names and network addresses. Inventory specifications include manufacturer, device type, model, serial number, and physical location. [SP 800-128] provides guidance on security-focused configuration management." - } - ] - }, - { - "id": "3.4.2", - "title": "3.4.2", - "props": [ - { - "name": "label", - "value": "3.4.2" - }, - { - "name": "sort-id", - "value": "03.04.02" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.4.2_smt", - "name": "statement", - "prose": "Establish and enforce security configuration settings for information technology products employed in organizational systems." - }, - { - "id": "3.4.2_gdn", - "name": "guidance", - "prose": "Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture or functionality of the system. Information technology products for which security-related configuration settings can be defined include mainframe computers, servers, workstations, input and output devices (e.g., scanners, copiers, and printers), network components (e.g., firewalls, routers, gateways, voice and data switches, wireless access points, network appliances, sensors), operating systems, middleware, and applications. Security parameters are those parameters impacting the security state of systems including the parameters required to satisfy other security requirements. Security parameters include: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, and remote connections. Organizations establish organization-wide configuration settings and subsequently derive specific configuration settings for systems. The established settings become part of the systems configuration baseline. Common secure configurations (also referred to as security configuration checklists, lockdown and hardening guides, security reference guides, security technical implementation guides) provide recognized, standardized, and established benchmarks that stipulate secure configuration settings for specific information technology platforms/products and instructions for configuring those system components to meet operational requirements. Common secure configurations can be developed by a variety of organizations including information technology product developers, manufacturers, vendors, consortia, academia, industry, federal agencies, and other organizations in the public and private sectors. [SP 800-70] and [SP 800-128] provide guidance on security configuration settings." - } - ] - }, - { - "id": "3.4.3", - "title": "3.4.3", - "props": [ - { - "name": "label", - "value": "3.4.3" - }, - { - "name": "sort-id", - "value": "03.04.03" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.4.3_smt", - "name": "statement", - "prose": "Track, review, approve or disapprove, and log changes to organizational systems." - }, - { - "id": "3.4.3_gdn", - "name": "guidance", - "prose": "Tracking, reviewing, approving/disapproving, and logging changes is called configuration change control. Configuration change control for organizational systems involves the systematic proposal, justification, implementation, testing, review, and disposition of changes to the systems, including system upgrades and modifications. Configuration change control includes changes to baseline configurations for components and configuration items of systems, changes to configuration settings for information technology products (e.g., operating systems, applications, firewalls, routers, and mobile devices), unscheduled and unauthorized changes, and changes to remediate vulnerabilities. Processes for managing configuration changes to systems include Configuration Control Boards or Change Advisory Boards that review and approve proposed changes to systems. For new development systems or systems undergoing major upgrades, organizations consider including representatives from development organizations on the Configuration Control Boards or Change Advisory Boards. Audit logs of changes include activities before and after changes are made to organizational systems and the activities required to implement such changes. [SP 800-128] provides guidance on configuration change control." - } - ] - }, - { - "id": "3.4.4", - "title": "3.4.4", - "props": [ - { - "name": "label", - "value": "3.4.4" - }, - { - "name": "sort-id", - "value": "03.04.04" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.4.4_smt", - "name": "statement", - "prose": "Analyze the security impact of changes prior to implementation." - }, - { - "id": "3.4.4_gdn", - "name": "guidance", - "prose": "Organizational personnel with information security responsibilities (e.g., system administrators, system security officers, system security managers, and systems security engineers) conduct security impact analyses. Individuals conducting security impact analyses possess the necessary skills and technical expertise to analyze the changes to systems and the associated security ramifications. Security impact analysis may include reviewing security plans to understand security requirements and reviewing system design documentation to understand the implementation of controls and how specific changes might affect the controls. Security impact analyses may also include risk assessments to better understand the impact of the changes and to determine if additional controls are required. [SP 800-128] provides guidance on configuration change control and security impact analysis." - } - ] - }, - { - "id": "3.4.5", - "title": "3.4.5", - "props": [ - { - "name": "label", - "value": "3.4.5" - }, - { - "name": "sort-id", - "value": "03.04.05" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.4.5_smt", - "name": "statement", - "prose": "Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems." - }, - { - "id": "3.4.5_gdn", - "name": "guidance", - "prose": "Any changes to the hardware, software, or firmware components of systems can potentially have significant effects on the overall security of the systems. Therefore, organizations permit only qualified and authorized individuals to access systems for purposes of initiating changes, including upgrades and modifications. Access restrictions for change also include software libraries. Access restrictions include physical and logical access control requirements, workflow automation, media libraries, abstract layers (e.g., changes implemented into external interfaces rather than directly into systems), and change windows (e.g., changes occur only during certain specified times). In addition to security concerns, commonly-accepted due diligence for configuration management includes access restrictions as an essential part in ensuring the ability to effectively manage the configuration. [SP 800-128] provides guidance on configuration change control." - } - ] - }, - { - "id": "3.4.6", - "title": "3.4.6", - "props": [ - { - "name": "label", - "value": "3.4.6" - }, - { - "name": "sort-id", - "value": "03.04.06" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.4.6_smt", - "name": "statement", - "prose": "Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities." - }, - { - "id": "3.4.6_gdn", - "name": "guidance", - "prose": "Systems can provide a wide variety of functions and services. Some of the functions and services routinely provided by default, may not be necessary to support essential organizational missions, functions, or operations. It is sometimes convenient to provide multiple services from single system components. However, doing so increases risk over limiting the services provided by any one component. Where feasible, organizations limit component functionality to a single function per component. Organizations review functions and services provided by systems or components of systems, to determine which functions and services are candidates for elimination. Organizations disable unused or unnecessary physical and logical ports and protocols to prevent unauthorized connection of devices, transfer of information, and tunneling. Organizations can utilize network scanning tools, intrusion detection and prevention systems, and end-point protections such as firewalls and host-based intrusion detection systems to identify and prevent the use of prohibited functions, ports, protocols, and services." - } - ] - }, - { - "id": "3.4.7", - "title": "3.4.7", - "props": [ - { - "name": "label", - "value": "3.4.7" - }, - { - "name": "sort-id", - "value": "03.04.07" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.4.7_smt", - "name": "statement", - "prose": "Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services." - }, - { - "id": "3.4.7_gdn", - "name": "guidance", - "prose": "Restricting the use of nonessential software (programs) includes restricting the roles allowed to approve program execution; prohibiting auto-execute; program blacklisting and whitelisting; or restricting the number of program instances executed at the same time. The organization makes a security-based determination which functions, ports, protocols, and/or services are restricted. Bluetooth, File Transfer Protocol (FTP), and peer-to-peer networking are examples of protocols organizations consider preventing the use of, restricting, or disabling." - } - ] - }, - { - "id": "3.4.8", - "title": "3.4.8", - "props": [ - { - "name": "label", - "value": "3.4.8" - }, - { - "name": "sort-id", - "value": "03.04.08" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.4.8_smt", - "name": "statement", - "prose": "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." - }, - { - "id": "3.4.8_gdn", - "name": "guidance", - "prose": "The process used to identify software programs that are not authorized to execute on systems is commonly referred to as blacklisting. The process used to identify software programs that are authorized to execute on systems is commonly referred to as whitelisting. Whitelisting is the stronger of the two policies for restricting software program execution. In addition to whitelisting, organizations consider verifying the integrity of whitelisted software programs using, for example, cryptographic checksums, digital signatures, or hash functions. Verification of whitelisted software can occur either prior to execution or at system startup. [SP 800-167] provides guidance on application whitelisting." - } - ] - }, - { - "id": "3.4.9", - "title": "3.4.9", - "props": [ - { - "name": "label", - "value": "3.4.9" - }, - { - "name": "sort-id", - "value": "03.04.09" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.4.9_smt", - "name": "statement", - "prose": "Control and monitor user-installed software." - }, - { - "id": "3.4.9_gdn", - "name": "guidance", - "prose": "Users can install software in organizational systems if provided the necessary privileges. To maintain control over the software installed, organizations identify permitted and prohibited actions regarding software installation through policies. Permitted software installations include updates and security patches to existing software and applications from organization-approved \u201capp stores.\u201d Prohibited software installations may include software with unknown or suspect pedigrees or software that organizations consider potentially malicious. The policies organizations select governing user-installed software may be organization-developed or provided by some external entity. Policy enforcement methods include procedural methods, automated methods, or both." - } - ] - } - ] - }, - { - "id": "3.5", - "title": "Identification and Authentication", - "controls": [ - { - "id": "3.5.1", - "title": "3.5.1", - "props": [ - { - "name": "label", - "value": "3.5.1" - }, - { - "name": "sort-id", - "value": "03.05.01" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.5.1_smt", - "name": "statement", - "prose": "Identify system users, processes acting on behalf of users, and devices." - }, - { - "id": "3.5.1_gdn", - "name": "guidance", - "prose": "Common device identifiers include Media Access Control (MAC), Internet Protocol (IP) addresses, or device-unique token identifiers. Management of individual identifiers is not applicable to shared system accounts. Typically, individual identifiers are the user names associated with the system accounts assigned to those individuals. Organizations may require unique identification of individuals in group accounts or for detailed accountability of individual activity. In addition, this requirement addresses individual identifiers that are not necessarily associated with system accounts. Organizational devices requiring identification may be defined by type, by device, or by a combination of type/device. [SP 800-63-3] provides guidance on digital identities." - } - ] - }, - { - "id": "3.5.2", - "title": "3.5.2", - "props": [ - { - "name": "label", - "value": "3.5.2" - }, - { - "name": "sort-id", - "value": "03.05.02" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.5.2_smt", - "name": "statement", - "prose": "Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems." - }, - { - "id": "3.5.2_gdn", - "name": "guidance", - "prose": "Individual authenticators include the following: passwords, key cards, cryptographic devices, and one-time password devices. Initial authenticator content is the actual content of the authenticator, for example, the initial password. In contrast, the requirements about authenticator content include the minimum password length. Developers ship system components with factory default authentication credentials to allow for initial installation and configuration. Default authentication credentials are often well known, easily discoverable, and present a significant security risk. Systems support authenticator management by organization-defined settings and restrictions for various authenticator characteristics including minimum password length, validation time window for time synchronous one-time tokens, and number of allowed rejections during the verification stage of biometric authentication. Authenticator management includes issuing and revoking, when no longer needed, authenticators for temporary access such as that required for remote maintenance. Device authenticators include certificates and passwords. [SP 800-63-3] provides guidance on digital identities." - } - ] - }, - { - "id": "3.5.3", - "title": "3.5.3", - "props": [ - { - "name": "label", - "value": "3.5.3" - }, - { - "name": "sort-id", - "value": "03.05.03" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.5.3_smt", - "name": "statement", - "prose": "Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.[24] [25]." - }, - { - "id": "3.5.3_gdn", - "name": "guidance", - "prose": "Multifactor authentication requires the use of two or more different factors to authenticate. The factors are defined as something you know (e.g., password, personal identification number [PIN]); something you have (e.g., cryptographic identification device, token); or something you are (e.g., biometric). Multifactor authentication solutions that feature physical authenticators include hardware authenticators providing time-based or challenge-response authenticators and smart cards. In addition to authenticating users at the system level (i.e., at logon), organizations may also employ authentication mechanisms at the application level, when necessary, to provide increased information security. Access to organizational systems is defined as local access or network access. Local access is any access to organizational systems by users (or processes acting on behalf of users) where such access is obtained by direct connections without the use of networks. Network access is access to systems by users (or processes acting on behalf of users) where such access is obtained through network connections (i.e., nonlocal accesses). Remote access is a type of network access that involves communication through external networks. The use of encrypted virtual private networks for connections between organization-controlled and non-organization controlled endpoints may be treated as internal networks with regard to protecting the confidentiality of information. [SP 800-63-3] provides guidance on digital identities.\n\n[24] Multifactor authentication requires two or more different factors to achieve authentication. The factors include: something you know (e.g., password/PIN); something you have (e.g., cryptographic identification device, token); or something you are (e.g., biometric). The requirement for multifactor authentication should not be interpreted as requiring federal Personal Identity Verification (PIV) card or Department of Defense Common Access Card (CAC)-like solutions. A variety of multifactor solutions (including those with replay resistance) using tokens and biometrics are commercially available. Such solutions may employ hard tokens (e.g., smartcards, key fobs, or dongles) or soft tokens to store user credentials. \n[25] Local access is any access to a system by a user (or process acting on behalf of a user) communicating through a direct connection without the use of a network. Network access is any access to a system by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, Internet)." - } - ] - }, - { - "id": "3.5.4", - "title": "3.5.4", - "props": [ - { - "name": "label", - "value": "3.5.4" - }, - { - "name": "sort-id", - "value": "03.05.04" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.5.4_smt", - "name": "statement", - "prose": "Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts." - }, - { - "id": "3.5.4_gdn", - "name": "guidance", - "prose": "Authentication processes resist replay attacks if it is impractical to successfully authenticate by recording or replaying previous authentication messages. Replay-resistant techniques include protocols that use nonces or challenges such as time synchronous or challenge-response one-time authenticators. [SP 800-63-3] provides guidance on digital identities." - } - ] - }, - { - "id": "3.5.5", - "title": "3.5.5", - "props": [ - { - "name": "label", - "value": "3.5.5" - }, - { - "name": "sort-id", - "value": "03.05.05" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.5.5_smt", - "name": "statement", - "prose": "Prevent reuse of identifiers for a defined period." - }, - { - "id": "3.5.5_gdn", - "name": "guidance", - "prose": "Identifiers are provided for users, processes acting on behalf of users, or devices (3.5.1). Preventing reuse of identifiers implies preventing the assignment of previously used individual, group, role, or device identifiers to different individuals, groups, roles, or devices." - } - ] - }, - { - "id": "3.5.6", - "title": "3.5.6", - "props": [ - { - "name": "label", - "value": "3.5.6" - }, - { - "name": "sort-id", - "value": "03.05.06" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.5.6_smt", - "name": "statement", - "prose": "Disable identifiers after a defined period of inactivity." - }, - { - "id": "3.5.6_gdn", - "name": "guidance", - "prose": "Inactive identifiers pose a risk to organizational information because attackers may exploit an inactive identifier to gain undetected access to organizational devices. The owners of the inactive accounts may not notice if unauthorized access to the account has been obtained." - } - ] - }, - { - "id": "3.5.7", - "title": "3.5.7", - "props": [ - { - "name": "label", - "value": "3.5.7" - }, - { - "name": "sort-id", - "value": "03.05.07" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.5.7_smt", - "name": "statement", - "prose": "Enforce a minimum password complexity and change of characters when new passwords are created." - }, - { - "id": "3.5.7_gdn", - "name": "guidance", - "prose": "This requirement applies to single-factor authentication of individuals using passwords as individual or group authenticators, and in a similar manner, when passwords are used as part of multifactor authenticators. The number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. To mitigate certain brute force attacks against passwords, organizations may also consider salting passwords." - } - ] - }, - { - "id": "3.5.8", - "title": "3.5.8", - "props": [ - { - "name": "label", - "value": "3.5.8" - }, - { - "name": "sort-id", - "value": "03.05.08" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.5.8_smt", - "name": "statement", - "prose": "Prohibit password reuse for a specified number of generations." - }, - { - "id": "3.5.8_gdn", - "name": "guidance", - "prose": "Password lifetime restrictions do not apply to temporary passwords" - } - ] - }, - { - "id": "3.5.9", - "title": "3.5.9", - "props": [ - { - "name": "label", - "value": "3.5.9" - }, - { - "name": "sort-id", - "value": "03.05.09" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.5.9_smt", - "name": "statement", - "prose": "Allow temporary password use for system logons with an immediate change to a permanent password." - }, - { - "id": "3.5.9_gdn", - "name": "guidance", - "prose": "Changing temporary passwords to permanent passwords immediately after system logon ensures that the necessary strength of the authentication mechanism is implemented at the earliest opportunity, reducing the susceptibility to authenticator compromises." - } - ] - }, - { - "id": "3.5.10", - "title": "3.5.10", - "props": [ - { - "name": "label", - "value": "3.5.10" - }, - { - "name": "sort-id", - "value": "03.05.10" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.5.10_smt", - "name": "statement", - "prose": "Store and transmit only cryptographically-protected passwords." - }, - { - "id": "3.5.10_gdn", - "name": "guidance", - "prose": "Cryptographically-protected passwords use salted one-way cryptographic hashes of passwords. See [NIST CRYPTO]." - } - ] - }, - { - "id": "3.5.11", - "title": "3.5.11", - "props": [ - { - "name": "label", - "value": "3.5.11" - }, - { - "name": "sort-id", - "value": "03.05.11" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.5.11_smt", - "name": "statement", - "prose": "Obscure feedback of authentication information" - }, - { - "id": "3.5.11_gdn", - "name": "guidance", - "prose": "The feedback from systems does not provide any information that would allow unauthorized individuals to compromise authentication mechanisms. For some types of systems or system components, for example, desktop or notebook computers with relatively large monitors, the threat (often referred to as shoulder surfing) may be significant. For other types of systems or components, for example, mobile devices with small displays, this threat may be less significant, and is balanced against the increased likelihood of typographic input errors due to the small keyboards. Therefore, the means for obscuring the authenticator feedback is selected accordingly. Obscuring authenticator feedback includes displaying asterisks when users type passwords into input devices or displaying feedback for a very limited time before fully obscuring it." - } - ] - } - ] - }, - { - "id": "3.6", - "title": "Incident response", - "controls": [ - { - "id": "3.6.1", - "title": "3.6.1", - "props": [ - { - "name": "label", - "value": "3.6.1" - }, - { - "name": "sort-id", - "value": "03.06.01" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.6.1_smt", - "name": "statement", - "prose": "Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities." - }, - { - "id": "3.6.1_gdn", - "name": "guidance", - "prose": "Organizations recognize that incident handling capability is dependent on the capabilities of organizational systems and the mission/business processes being supported by those systems. Organizations consider incident handling as part of the definition, design, and development of mission/business processes and systems. Incident-related information can be obtained from a variety of sources including audit monitoring, network monitoring, physical access monitoring, user and administrator reports, and reported supply chain events. Effective incident handling capability includes coordination among many organizational entities including mission/business owners, system owners, authorizing officials, human resources offices, physical and personnel security offices, legal departments, operations personnel, procurement offices, and the risk executive. As part of user response activities, incident response training is provided by organizations and is linked directly to the assigned roles and responsibilities of organizational personnel to ensure that the appropriate content and level of detail is included in such training. For example, regular users may only need to know who to call or how to recognize an incident on the system; system administrators may require additional training on how to handle or remediate incidents; and incident responders may receive more specific training on forensics, reporting, system recovery, and restoration. Incident response training includes user training in the identification/reporting of suspicious activities from external and internal sources. User response activities also includes incident response assistance which may consist of help desk support, assistance groups, and access to forensics services or consumer redress services, when required. [SP 800-61] provides guidance on incident handling. [SP 800-86] and [SP 800-101] provide guidance on integrating forensic techniques into incident response. [SP 800-161] provides guidance on supply chain risk management." - } - ] - }, - { - "id": "3.6.2", - "title": "3.6.2", - "props": [ - { - "name": "label", - "value": "3.6.2" - }, - { - "name": "sort-id", - "value": "03.06.02" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.6.2_smt", - "name": "statement", - "prose": "Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization." - }, - { - "id": "3.6.2_gdn", - "name": "guidance", - "prose": "Tracking and documenting system security incidents includes maintaining records about each incident, the status of the incident, and other pertinent information necessary for forensics, evaluating incident details, trends, and handling. Incident information can be obtained from a variety of sources including incident reports, incident response teams, audit monitoring, network monitoring, physical access monitoring, and user/administrator reports. Reporting incidents addresses specific incident reporting requirements within an organization and the formal incident reporting requirements for the organization. Suspected security incidents may also be reported and include the receipt of suspicious email communications that can potentially contain malicious code. The types of security incidents reported, the content and timeliness of the reports, and the designated reporting authorities reflect applicable laws, Executive Orders, directives, regulations, and policies. [SP 800-61] provides guidance on incident handling." - } - ] - }, - { - "id": "3.6.3", - "title": "3.6.3", - "props": [ - { - "name": "label", - "value": "3.6.3" - }, - { - "name": "sort-id", - "value": "03.06.03" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.6.3_smt", - "name": "statement", - "prose": "Test the organizational incident response capability." - }, - { - "id": "3.6.3_gdn", - "name": "guidance", - "prose": "Organizations test incident response capabilities to determine the effectiveness of the capabilities and to identify potential weaknesses or deficiencies. Incident response testing includes the use of checklists, walk-through or tabletop exercises, simulations (both parallel and full interrupt), and comprehensive exercises. Incident response testing can also include a determination of the effects on organizational operations (e.g., reduction in mission capabilities), organizational assets, and individuals due to incident response. [SP 800-84] provides guidance on testing programs for information technology capabilities." - } - ] - } - ] - }, - { - "id": "3.7", - "title": "Maintenance", - "controls": [ - { - "id": "3.7.1", - "title": "3.7.1", - "props": [ - { - "name": "label", - "value": "3.7.1" - }, - { - "name": "sort-id", - "value": "03.07.01" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.7.1_smt", - "name": "statement", - "prose": "Perform maintenance on organizational systems.[26]." - }, - { - "id": "3.7.1_gdn", - "name": "guidance", - "prose": "This requirement addresses the information security aspects of the system maintenance program and applies to all types of maintenance to any system component (including hardware, firmware, applications) conducted by any local or nonlocal entity. System maintenance also includes those components not directly associated with information processing and data or information retention such as scanners, copiers, and printers.\n\n[26] In general, system maintenance requirements tend to support the security objective of availability. However, improper system maintenance or a failure to perform maintenance can result in the unauthorized disclosure of CUI, thus compromising confidentiality of that information." - } - ] - }, - { - "id": "3.7.2", - "title": "3.7.2", - "props": [ - { - "name": "label", - "value": "3.7.2" - }, - { - "name": "sort-id", - "value": "03.07.02" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.7.2_smt", - "name": "statement", - "prose": "Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance." - }, - { - "id": "3.7.2_gdn", - "name": "guidance", - "prose": "This requirement addresses security-related issues with maintenance tools that are not within the organizational system boundaries that process, store, or transmit CUI, but are used specifically for diagnostic and repair actions on those systems. Organizations have flexibility in determining the controls in place for maintenance tools, but can include approving, controlling, and monitoring the use of such tools. Maintenance tools are potential vehicles for transporting malicious code, either intentionally or unintentionally, into a facility and into organizational systems. Maintenance tools can include hardware, software, and firmware items, for example, hardware and software diagnostic test equipment and hardware and software packet sniffers." - } - ] - }, - { - "id": "3.7.3", - "title": "3.7.3", - "props": [ - { - "name": "label", - "value": "3.7.3" - }, - { - "name": "sort-id", - "value": "03.07.03" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.7.3_smt", - "name": "statement", - "prose": "Ensure equipment removed for off-site maintenance is sanitized of any CUI." - }, - { - "id": "3.7.3_gdn", - "name": "guidance", - "prose": "This requirement addresses the information security aspects of system maintenance that are performed off-site and applies to all types of maintenance to any system component (including applications) conducted by a local or nonlocal entity (e.g., in-contract, warranty, in- house, software maintenance agreement). [SP 800-88] provides guidance on media sanitization." - } - ] - }, - { - "id": "3.7.4", - "title": "3.7.4", - "props": [ - { - "name": "label", - "value": "3.7.4" - }, - { - "name": "sort-id", - "value": "03.07.04" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.7.4_smt", - "name": "statement", - "prose": "Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems." - }, - { - "id": "3.7.4_gdn", - "name": "guidance", - "prose": "If, upon inspection of media containing maintenance diagnostic and test programs, organizations determine that the media contain malicious code, the incident is handled consistent with incident handling policies and procedures." - } - ] - }, - { - "id": "3.7.5", - "title": "3.7.5", - "props": [ - { - "name": "label", - "value": "3.7.5" - }, - { - "name": "sort-id", - "value": "03.07.05" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.7.5_smt", - "name": "statement", - "prose": "Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete." - }, - { - "id": "3.7.5_gdn", - "name": "guidance", - "prose": "Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through an external network. The authentication techniques employed in the establishment of these nonlocal maintenance and diagnostic sessions reflect the network access requirements in 3.5.3." - } - ] - }, - { - "id": "3.7.6", - "title": "3.7.6", - "props": [ - { - "name": "label", - "value": "3.7.6" - }, - { - "name": "sort-id", - "value": "03.07.06" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.7.6_smt", - "name": "statement", - "prose": "Supervise the maintenance activities of maintenance personnel without required access authorization." - }, - { - "id": "3.7.6_gdn", - "name": "guidance", - "prose": "This requirement applies to individuals who are performing hardware or software maintenance on organizational systems, while 3.10.1 addresses physical access for individuals whose maintenance duties place them within the physical protection perimeter of the systems (e.g., custodial staff, physical plant maintenance personnel). Individuals not previously identified as authorized maintenance personnel, such as information technology manufacturers, vendors, consultants, and systems integrators, may require privileged access to organizational systems, for example, when required to conduct maintenance activities with little or no notice. Organizations may choose to issue temporary credentials to these individuals based on organizational risk assessments. Temporary credentials may be for one-time use or for very limited time periods." - } - ] - } - ] - }, - { - "id": "3.8", - "title": "Media Protection", - "controls": [ - { - "id": "3.8.1", - "title": "3.8.1", - "props": [ - { - "name": "label", - "value": "3.8.1" - }, - { - "name": "sort-id", - "value": "03.08.01" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.8.1_smt", - "name": "statement", - "prose": "Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital." - }, - { - "id": "3.8.1_gdn", - "name": "guidance", - "prose": "System media includes digital and non-digital media. Digital media includes diskettes, magnetic tapes, external and removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes paper and microfilm. Protecting digital media includes limiting access to design specifications stored on compact disks or flash drives in the media library to the project leader and any individuals on the development team. Physically controlling system media includes conducting inventories, maintaining accountability for stored media, and ensuring procedures are in place to allow individuals to check out and return media to the media library. Secure storage includes a locked drawer, desk, or cabinet, or a controlled media library. Access to CUI on system media can be limited by physically controlling such media, which includes conducting inventories, ensuring procedures are in place to allow individuals to check out and return media to the media library, and maintaining accountability for all stored media. [SP 800-111] provides guidance on storage encryption technologies for end user devices." - } - ] - }, - { - "id": "3.8.2", - "title": "3.8.2", - "props": [ - { - "name": "label", - "value": "3.8.2" - }, - { - "name": "sort-id", - "value": "03.08.02" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.8.2_smt", - "name": "statement", - "prose": "Limit access to CUI on system media to authorized users" - }, - { - "id": "3.8.2_gdn", - "name": "guidance", - "prose": "Access can be limited by physically controlling system media and secure storage areas. Physically controlling system media includes conducting inventories, ensuring procedures are in place to allow individuals to check out and return system media to the media library, and maintaining accountability for all stored media. Secure storage includes a locked drawer, desk, or cabinet, or a controlled media library" - } - ] - }, - { - "id": "3.8.3", - "title": "3.8.3", - "props": [ - { - "name": "label", - "value": "3.8.3" - }, - { - "name": "sort-id", - "value": "03.08.03" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.8.3_smt", - "name": "statement", - "prose": "Sanitize or destroy system media containing CUI before disposal or release for reuse." - }, - { - "id": "3.8.3_gdn", - "name": "guidance", - "prose": "This requirement applies to all system media, digital and non-digital, subject to disposal or reuse. Examples include: digital media found in workstations, network components, scanners, copiers, printers, notebook computers, and mobile devices; and non-digital media such as paper and microfilm. The sanitization process removes information from the media such that the information cannot be retrieved or reconstructed. Sanitization techniques, including clearing, purging, cryptographic erase, and destruction, prevent the disclosure of information to unauthorized individuals when such media is released for reuse or disposal. Organizations determine the appropriate sanitization methods, recognizing that destruction may be necessary when other methods cannot be applied to the media requiring sanitization. Organizations use discretion on the employment of sanitization techniques and procedures for media containing information that is in the public domain or publicly releasable or deemed to have no adverse impact on organizations or individuals if released for reuse or disposal. Sanitization of non-digital media includes destruction, removing CUI from documents, or redacting selected sections or words from a document by obscuring the redacted sections or words in a manner equivalent in effectiveness to removing the words or sections from the document. NARA policy and guidance control sanitization processes for controlled unclassified information. [SP 800-88] provides guidance on media sanitization." - } - ] - }, - { - "id": "3.8.4", - "title": "3.8.4", - "props": [ - { - "name": "label", - "value": "3.8.4" - }, - { - "name": "sort-id", - "value": "03.08.04" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.8.4_smt", - "name": "statement", - "prose": "Mark media with necessary CUI markings and distribution limitations.[27]" - }, - { - "id": "3.8.4_gdn", - "name": "guidance", - "prose": "The term security marking refers to the application or use of human-readable security attributes. System media includes digital and non-digital media. Marking of system media reflects applicable federal laws, Executive Orders, directives, policies, and regulations. See [NARA MARK].\n\n[27] The implementation of this requirement is per marking guidance in [32 CFR 2002] and [NARA CUI]. Standard Form (SF) 902 (approximate size 2.125\u201d x 1.25\u201d) and SF 903 (approximate size 2.125\u201d x .625\u201d) can be used on media that contains CUI such as hard drives, or USB devices. Both forms are available from https://www.gsaadvantage.gov." - } - ] - }, - { - "id": "3.8.5", - "title": "3.8.5", - "props": [ - { - "name": "label", - "value": "3.8.5" - }, - { - "name": "sort-id", - "value": "03.08.05" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.8.5_smt", - "name": "statement", - "prose": "Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas." - }, - { - "id": "3.8.5_gdn", - "name": "guidance", - "prose": "Controlled areas are areas or spaces for which organizations provide physical or procedural controls to meet the requirements established for protecting systems and information. Controls to maintain accountability for media during transport include locked containers and cryptography. Cryptographic mechanisms can provide confidentiality and integrity protections depending upon the mechanisms used. Activities associated with transport include the actual transport as well as those activities such as releasing media for transport and ensuring that media enters the appropriate transport processes. For the actual transport, authorized transport and courier personnel may include individuals external to the organization. Maintaining accountability of media during transport includes restricting transport activities to authorized personnel and tracking and obtaining explicit records of transport activities as the media moves through the transportation system to prevent and detect loss, destruction, or tampering." - } - ] - }, - { - "id": "3.8.6", - "title": "3.8.6", - "props": [ - { - "name": "label", - "value": "3.8.6" - }, - { - "name": "sort-id", - "value": "03.08.06" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.8.6_smt", - "name": "statement", - "prose": "Implement cryptographic mechanisms to protect the confidentiality of CUI stored on digital media during transport unless otherwise protected by alternative physical safeguards." - }, - { - "id": "3.8.6_gdn", - "name": "guidance", - "prose": "This requirement applies to portable storage devices (e.g., USB memory sticks, digital video disks, compact disks, external or removable hard disk drives). See [NIST CRYPTO]. [SP 800-111] provides guidance on storage encryption technologies for end user devices." - } - ] - }, - { - "id": "3.8.7", - "title": "3.8.7", - "props": [ - { - "name": "label", - "value": "3.8.7" - }, - { - "name": "sort-id", - "value": "03.08.07" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.8.7_smt", - "name": "statement", - "prose": "Control the use of removable media on system components." - }, - { - "id": "3.8.7_gdn", - "name": "guidance", - "prose": "In contrast to requirement 3.8.1, which restricts user access to media, this requirement restricts the use of certain types of media on systems, for example, restricting or prohibiting the use of flash drives or external hard disk drives. Organizations can employ technical and nontechnical controls (e.g., policies, procedures, and rules of behavior) to control the use of system media. Organizations may control the use of portable storage devices, for example, by using physical cages on workstations to prohibit access to certain external ports, or disabling or removing the ability to insert, read, or write to such devices. Organizations may also limit the use of portable storage devices to only approved devices including devices provided by the organization, devices provided by other approved organizations, and devices that are not personally owned. Finally, organizations may control the use of portable storage devices based on the type of device, prohibiting the use of writeable, portable devices, and implementing this restriction by disabling or removing the capability to write to such devices." - } - ] - }, - { - "id": "3.8.8", - "title": "3.8.8", - "props": [ - { - "name": "label", - "value": "3.8.8" - }, - { - "name": "sort-id", - "value": "03.08.08" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.8.8_smt", - "name": "statement", - "prose": "Prohibit the use of portable storage devices when such devices have no identifiable owner." - }, - { - "id": "3.8.8_gdn", - "name": "guidance", - "prose": "Requiring identifiable owners (e.g., individuals, organizations, or projects) for portable storage devices reduces the overall risk of using such technologies by allowing organizations to assign responsibility and accountability for addressing known vulnerabilities in the devices (e.g., insertion of malicious code)." - } - ] - }, - { - "id": "3.8.9", - "title": "3.8.9", - "props": [ - { - "name": "label", - "value": "3.8.9" - }, - { - "name": "sort-id", - "value": "03.08.09" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.8.9_smt", - "name": "statement", - "prose": "Protect the confidentiality of backup CUI at storage locations." - }, - { - "id": "3.8.9_gdn", - "name": "guidance", - "prose": "Organizations can employ cryptographic mechanisms or alternative physical controls to protect the confidentiality of backup information at designated storage locations. Backed-up information containing CUI may include system-level information and user-level information. System-level information includes system-state information, operating system software, application software, and licenses. User-level information includes information other than system-level information." - } - ] - } - ] - }, - { - "id": "3.9", - "title": "Personnel Security", - "controls": [ - { - "id": "3.9.1", - "title": "3.9.1", - "props": [ - { - "name": "label", - "value": "3.9.1" - }, - { - "name": "sort-id", - "value": "03.09.01" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.9.1_smt", - "name": "statement", - "prose": "Screen individuals prior to authorizing access to organizational systems containing CUI." - }, - { - "id": "3.9.1_gdn", - "name": "guidance", - "prose": "Personnel security screening (vetting) activities involve the evaluation/assessment of individual\u2019s conduct, integrity, judgment, loyalty, reliability, and stability (i.e., the trustworthiness of the individual) prior to authorizing access to organizational systems containing CUI. The screening activities reflect applicable federal laws, Executive Orders, directives, policies, regulations, and specific criteria established for the level of access required for assigned positions." - } - ] - }, - { - "id": "3.9.2", - "title": "3.9.2", - "props": [ - { - "name": "label", - "value": "3.9.2" - }, - { - "name": "sort-id", - "value": "03.09.02" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.9.2_smt", - "name": "statement", - "prose": "Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers" - }, - { - "id": "3.9.2_gdn", - "name": "guidance", - "prose": "Protecting CUI during and after personnel actions may include returning system-related property and conducting exit interviews. System-related property includes hardware authentication tokens, identification cards, system administration technical manuals, keys, and building passes. Exit interviews ensure that individuals who have been terminated understand the security constraints imposed by being former employees and that proper accountability is achieved for system-related property. Security topics of interest at exit interviews can include reminding terminated individuals of nondisclosure agreements and potential limitations on future employment. Exit interviews may not be possible for some terminated individuals, for example, in cases related to job abandonment, illnesses, and non-availability of supervisors. For termination actions, timely execution is essential for individuals terminated for cause. In certain situations, organizations consider disabling the system accounts of individuals that are being terminated prior to the individuals being notified. This requirement applies to reassignments or transfers of individuals when the personnel action is permanent or of such extended durations as to require protection. Organizations define the CUI protections appropriate for the types of reassignments or transfers, whether permanent or extended. Protections that may be required for transfers or reassignments to other positions within organizations include returning old and issuing new keys, identification cards, and building passes; changing system access authorizations (i.e., privileges); closing system accounts and establishing new accounts; and providing for access to official records to which individuals had access at previous work locations and in previous system accounts." - } - ] - } - ] - }, - { - "id": "3.10", - "title": "Physical Protection", - "controls": [ - { - "id": "3.10.1", - "title": "3.10.1", - "props": [ - { - "name": "label", - "value": "3.10.1" - }, - { - "name": "sort-id", - "value": "03.10.01" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.10.1_smt", - "name": "statement", - "prose": "Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals." - }, - { - "id": "3.10.1_gdn", - "name": "guidance", - "prose": "This requirement applies to employees, individuals with permanent physical access authorization credentials, and visitors. Authorized individuals have credentials that include badges, identification cards, and smart cards. Organizations determine the strength of authorization credentials needed consistent with applicable laws, directives, policies, regulations, standards, procedures, and guidelines. This requirement applies only to areas within facilities that have not been designated as publicly accessible. Limiting physical access to equipment may include placing equipment in locked rooms or other secured areas and allowing access to authorized individuals only; and placing equipment in locations that can be monitored by organizational personnel. Computing devices, external disk drives, networking devices, monitors, printers, copiers, scanners, facsimile machines, and audio devices are examples of equipment." - } - ] - }, - { - "id": "3.10.2", - "title": "3.10.2", - "props": [ - { - "name": "label", - "value": "3.10.2" - }, - { - "name": "sort-id", - "value": "03.10.02" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.10.2_smt", - "name": "statement", - "prose": "Protect and monitor the physical facility and support infrastructure for organizational systems." - }, - { - "id": "3.10.2_gdn", - "name": "guidance", - "prose": "Monitoring of physical access includes publicly accessible areas within organizational facilities. This can be accomplished, for example, by the employment of guards; the use of sensor devices; or the use of video surveillance equipment such as cameras. Examples of support infrastructure include system distribution, transmission, and power lines. Security controls applied to the support infrastructure prevent accidental damage, disruption, and physical tampering. Such controls may also be necessary to prevent eavesdropping or modification of unencrypted transmissions. Physical access controls to support infrastructure include locked wiring closets; disconnected or locked spare jacks; protection of cabling by conduit or cable trays; and wiretapping sensors." - } - ] - }, - { - "id": "3.10.3", - "title": "3.10.3", - "props": [ - { - "name": "label", - "value": "3.10.3" - }, - { - "name": "sort-id", - "value": "03.10.03" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.10.3_smt", - "name": "statement", - "prose": "Escort visitors and monitor visitor activity." - }, - { - "id": "3.10.3_gdn", - "name": "guidance", - "prose": "Individuals with permanent physical access authorization credentials are not considered visitors. Audit logs can be used to monitor visitor activity." - } - ] - }, - { - "id": "3.10.4", - "title": "3.10.4", - "props": [ - { - "name": "label", - "value": "3.10.4" - }, - { - "name": "sort-id", - "value": "03.10.04" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.10.4_smt", - "name": "statement", - "prose": "Maintain audit logs of physical access." - }, - { - "id": "3.10.4_gdn", - "name": "guidance", - "prose": "Organizations have flexibility in the types of audit logs employed. Audit logs can be procedural (e.g., a written log of individuals accessing the facility), automated (e.g., capturing ID provided by a PIV card), or some combination thereof. Physical access points can include facility access points, interior access points to systems or system components requiring supplemental access controls, or both. System components (e.g., workstations, notebook computers) may be in areas designated as publicly accessible with organizations safeguarding access to such devices." - } - ] - }, - { - "id": "3.10.5", - "title": "3.10.5", - "props": [ - { - "name": "label", - "value": "3.10.5" - }, - { - "name": "sort-id", - "value": "03.10.05" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.10.5_smt", - "name": "statement", - "prose": "Control and manage physical access devices." - }, - { - "id": "3.10.5_gdn", - "name": "guidance", - "prose": "Physical access devices include keys, locks, combinations, and card readers." - } - ] - }, - { - "id": "3.10.6", - "title": "3.10.6", - "props": [ - { - "name": "label", - "value": "3.10.6" - }, - { - "name": "sort-id", - "value": "03.10.06" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.10.6_smt", - "name": "statement", - "prose": "Enforce safeguarding measures for CUI at alternate work sites." - }, - { - "id": "3.10.6_gdn", - "name": "guidance", - "prose": "Alternate work sites may include government facilities or the private residences of employees. Organizations may define different security requirements for specific alternate work sites or types of sites depending on the work-related activities conducted at those sites. [SP 800-46] and [SP 800-114] provide guidance on enterprise and user security when teleworking." - } - ] - } - ] - }, - { - "id": "3.11", - "title": "Risk Assessment", - "controls": [ - { - "id": "3.11.1", - "title": "3.11.1", - "props": [ - { - "name": "label", - "value": "3.11.1" - }, - { - "name": "sort-id", - "value": "03.11.01" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.11.1_smt", - "name": "statement", - "prose": "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" - }, - { - "id": "3.11.1_gdn", - "name": "guidance", - "prose": "Clearly defined system boundaries are a prerequisite for effective risk assessments. Such risk assessments consider threats, vulnerabilities, likelihood, and impact to organizational operations, organizational assets, and individuals based on the operation and use of organizational systems. Risk assessments also consider risk from external parties (e.g., service providers, contractors operating systems on behalf of the organization, individuals accessing organizational systems, outsourcing entities). Risk assessments, either formal or informal, can be conducted at the organization level, the mission or business process level, or the system level, and at any phase in the system development life cycle. [SP 800-30] provides guidance on conducting risk assessments." - } - ] - }, - { - "id": "3.11.2", - "title": "3.11.2", - "props": [ - { - "name": "label", - "value": "3.11.2" - }, - { - "name": "sort-id", - "value": "03.11.02" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.11.2_smt", - "name": "statement", - "prose": "Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified." - }, - { - "id": "3.11.2_gdn", - "name": "guidance", - "prose": "Organizations determine the required vulnerability scanning for all system components, ensuring that potential sources of vulnerabilities such as networked printers, scanners, and copiers are not overlooked. The vulnerabilities to be scanned are readily updated as new vulnerabilities are discovered, announced, and scanning methods developed. This process ensures that potential vulnerabilities in the system are identified and addressed as quickly as possible. Vulnerability analyses for custom software applications may require additional approaches such as static analysis, dynamic analysis, binary analysis, or a hybrid of the three approaches. Organizations can employ these analysis approaches in source code reviews and in a variety of tools (e.g., static analysis tools, web-based application scanners, binary analyzers) and in source code reviews. Vulnerability scanning includes: scanning for patch levels; scanning for functions, ports, protocols, and services that should not be accessible to users or devices; and scanning for improperly configured or incorrectly operating information flow control mechanisms. To facilitate interoperability, organizations consider using products that are Security Content Automated Protocol (SCAP)-validated, scanning tools that express vulnerabilities in the Common Vulnerabilities and Exposures (CVE) naming convention, and that employ the Open Vulnerability Assessment Language (OVAL) to determine the presence of system vulnerabilities. Sources for vulnerability information include the Common Weakness Enumeration (CWE) listing and the National Vulnerability Database (NVD). Security assessments, such as red team exercises, provide additional sources of potential vulnerabilities for which to scan. Organizations also consider using scanning tools that express vulnerability impact by the Common Vulnerability Scoring System (CVSS). In certain situations, the nature of the vulnerability scanning may be more intrusive or the system component that is the subject of the scanning may contain highly sensitive information. Privileged access authorization to selected system components facilitates thorough vulnerability scanning and protects the sensitive nature of such scanning. [SP 800-40] provides guidance on vulnerability management." - } - ] - }, - { - "id": "3.11.3", - "title": "3.11.3", - "props": [ - { - "name": "label", - "value": "3.11.3" - }, - { - "name": "sort-id", - "value": "03.11.03" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.11.3_smt", - "name": "statement", - "prose": "Remediate vulnerabilities in accordance with risk assessments." - }, - { - "id": "3.11.3_gdn", - "name": "guidance", - "prose": "Vulnerabilities discovered, for example, via the scanning conducted in response to 3.11.2, are remediated with consideration of the related assessment of risk. The consideration of risk influences the prioritization of remediation efforts and the level of effort to be expended in the remediation for specific vulnerabilities." - } - ] - } - ] - }, - { - "id": "3.12", - "title": "Security Assessment", - "controls": [ - { - "id": "3.12.1", - "title": "3.12.1", - "props": [ - { - "name": "label", - "value": "3.12.1" - }, - { - "name": "sort-id", - "value": "03.12.01" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.12.1_smt", - "name": "statement", - "prose": "Periodically assess the security controls in organizational systems to determine if the controls are effective in their application." - }, - { - "id": "3.12.1_gdn", - "name": "guidance", - "prose": "Organizations assess security controls in organizational systems and the environments in which those systems operate as part of the system development life cycle. Security controls are the safeguards or countermeasures organizations implement to satisfy security requirements. By assessing the implemented security controls, organizations determine if the security safeguards or countermeasures are in place and operating as intended. Security control assessments ensure that information security is built into organizational systems; identify weaknesses and deficiencies early in the development process; provide essential information needed to make risk-based decisions; and ensure compliance to vulnerability mitigation procedures. Assessments are conducted on the implemented security controls as documented in system security plans. Security assessment reports document assessment results in sufficient detail as deemed necessary by organizations, to determine the accuracy and completeness of the reports and whether the security controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting security requirements. Security assessment results are provided to the individuals or roles appropriate for the types of assessments being conducted. Organizations ensure that security assessment results are current, relevant to the determination of security control effectiveness, and obtained with the appropriate level of assessor independence. Organizations can choose to use other types of assessment activities such as vulnerability scanning and system monitoring to maintain the security posture of systems during the system life cycle. [SP 800-53] provides guidance on security and privacy controls for systems and organizations. [SP 800-53A] provides guidance on developing security assessment plans and conducting assessments." - } - ] - }, - { - "id": "3.12.2", - "title": "3.12.2", - "props": [ - { - "name": "label", - "value": "3.12.2" - }, - { - "name": "sort-id", - "value": "03.12.02" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.12.2_smt", - "name": "statement", - "prose": "Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems." - }, - { - "id": "3.12.2_gdn", - "name": "guidance", - "prose": "The plan of action is a key document in the information security program. Organizations develop plans of action that describe how any unimplemented security requirements will be met and how any planned mitigations will be implemented. Organizations can document the system security plan and plan of action as separate or combined documents and in any chosen format. Federal agencies may consider the submitted system security plans and plans of action as critical inputs to an overall risk management decision to process, store, or transmit CUI on a system hosted by a nonfederal organization and whether it is advisable to pursue an agreement or contract with the nonfederal organization. [NIST CUI] provides supplemental material for Special Publication 800-171 including templates for plans of action." - } - ] - }, - { - "id": "3.12.3", - "title": "3.12.3", - "props": [ - { - "name": "label", - "value": "3.12.3" - }, - { - "name": "sort-id", - "value": "03.12.03" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.12.3_smt", - "name": "statement", - "prose": "Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls." - }, - { - "id": "3.12.3_gdn", - "name": "guidance", - "prose": "Continuous monitoring programs facilitate ongoing awareness of threats, vulnerabilities, and information security to support organizational risk management decisions. The terms continuous and ongoing imply that organizations assess and analyze security controls and information security-related risks at a frequency sufficient to support risk-based decisions. The results of continuous monitoring programs generate appropriate risk response actions by organizations. Providing access to security information on a continuing basis through reports or dashboards gives organizational officials the capability to make effective and timely risk management decisions. Automation supports more frequent updates to hardware, software, firmware inventories, and other system information. Effectiveness is further enhanced when continuous monitoring outputs are formatted to provide information that is specific, measurable, actionable, relevant, and timely. Monitoring requirements, including the need for specific monitoring, may also be referenced in other requirements. [SP 800-137] provides guidance on continuous monitoring." - } - ] - }, - { - "id": "3.12.4", - "title": "3.12.4", - "props": [ - { - "name": "label", - "value": "3.12.4" - }, - { - "name": "sort-id", - "value": "03.12.04" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.12.4_smt", - "name": "statement", - "prose": "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.[28]" - }, - { - "id": "3.12.4_gdn", - "name": "guidance", - "prose": "System security plans relate security requirements to a set of security controls. System security plans also describe, at a high level, how the security controls meet those security requirements, but do not provide detailed, technical descriptions of the design or implementation of the controls. System security plans contain sufficient information to enable a design and implementation that is unambiguously compliant with the intent of the plans and subsequent determinations of risk if the plan is implemented as intended. Security plans need not be single documents; the plans can be a collection of various documents including documents that already exist. Effective security plans make extensive use of references to policies, procedures, and additional documents (e.g., design and implementation specifications) where more detailed information can be obtained. This reduces the documentation requirements associated with security programs and maintains security-related information in other established management/operational areas related to enterprise architecture, system development life cycle, systems engineering, and acquisition. Federal agencies may consider the submitted system security plans and plans of action as critical inputs to an overall risk management decision to process, store, or transmit CUI on a system hosted by a nonfederal organization and whether it is advisable to pursue an agreement or contract with the nonfederal organization. [SP 800-18] provides guidance on developing security plans. [NIST CUI] provides supplemental material for Special Publication 800-171 including templates for system security plans." - } - ] - } - ] - }, - { - "id": "3.13", - "title": "System and Communications Protection", - "controls": [ - { - "id": "3.13.1", - "title": "3.13.1", - "props": [ - { - "name": "label", - "value": "3.13.1" - }, - { - "name": "sort-id", - "value": "03.13.01" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.13.1_smt", - "name": "statement", - "prose": "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." - }, - { - "id": "3.13.1_gdn", - "name": "guidance", - "prose": "Communications can be monitored, controlled, and protected at boundary components and by restricting or prohibiting interfaces in organizational systems. Boundary components include gateways, routers, firewalls, guards, network-based malicious code analysis and virtualization systems, or encrypted tunnels implemented within a system security architecture (e.g., routers protecting firewalls or application gateways residing on protected subnetworks). Restricting or prohibiting interfaces in organizational systems includes restricting external web communications traffic to designated web servers within managed interfaces and prohibiting external traffic that appears to be spoofing internal addresses. Organizations consider the shared nature of commercial telecommunications services in the implementation of security requirements associated with the use of such services. Commercial telecommunications services are commonly based on network components and consolidated management systems shared by all attached commercial customers and may also include third party-provided access lines and other service elements. Such transmission services may represent sources of increased risk despite contract security provisions. [SP 800-41] provides guidance on firewalls and firewall policy. [SP 800-125B] provides guidance on security for virtualization technologies.\n\n[28] There is no prescribed format or specified level of detail for system security plans. However, organizations ensure that the required information in 3.12.4 is conveyed in those plans." - } - ] - }, - { - "id": "3.13.2", - "title": "3.13.2", - "props": [ - { - "name": "label", - "value": "3.13.2" - }, - { - "name": "sort-id", - "value": "03.13.02" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.13.2_smt", - "name": "statement", - "prose": "Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems." - }, - { - "id": "3.13.2_gdn", - "name": "guidance", - "prose": "Organizations apply systems security engineering principles to new development systems or systems undergoing major upgrades. For legacy systems, organizations apply systems security engineering principles to system upgrades and modifications to the extent feasible, given the current state of hardware, software, and firmware components within those systems. The application of systems security engineering concepts and principles helps to develop trustworthy, secure, and resilient systems and system components and reduce the susceptibility of organizations to disruptions, hazards, and threats. Examples of these concepts and principles include developing layered protections; establishing security policies, architecture, and controls as the foundation for design; incorporating security requirements into the system development life cycle; delineating physical and logical security boundaries; ensuring that developers are trained on how to build secure software; and performing threat modeling to identify use cases, threat agents, attack vectors and patterns, design patterns, and compensating controls needed to mitigate risk. Organizations that apply security engineering concepts and principles can facilitate the development of trustworthy, secure systems, system components, and system services; reduce risk to acceptable levels; and make informed risk-management decisions. [SP 800-160-1] provides guidance on systems security engineering." - } - ] - }, - { - "id": "3.13.3", - "title": "3.13.3", - "props": [ - { - "name": "label", - "value": "3.13.3" - }, - { - "name": "sort-id", - "value": "03.13.03" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.13.3_smt", - "name": "statement", - "prose": "Separate user functionality from system management functionality." - }, - { - "id": "3.13.3_gdn", - "name": "guidance", - "prose": "System management functionality includes functions necessary to administer databases, network components, workstations, or servers, and typically requires privileged user access. The separation of user functionality from system management functionality is physical or logical. Organizations can implement separation of system management functionality from user functionality by using different computers, different central processing units, different instances of operating systems, or different network addresses; virtualization techniques; or combinations of these or other methods, as appropriate. This type of separation includes web administrative interfaces that use separate authentication methods for users of any other system resources. Separation of system and user functionality may include isolating administrative interfaces on different domains and with additional access controls." - } - ] - }, - { - "id": "3.13.4", - "title": "3.13.4", - "props": [ - { - "name": "label", - "value": "3.13.4" - }, - { - "name": "sort-id", - "value": "03.13.04" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.13.4_smt", - "name": "statement", - "prose": "Prevent unauthorized and unintended information transfer via shared system resources." - }, - { - "id": "3.13.4_gdn", - "name": "guidance", - "prose": "The control of information in shared system resources (e.g., registers, cache memory, main memory, hard disks) is also commonly referred to as object reuse and residual information protection. This requirement prevents information produced by the actions of prior users or roles (or the actions of processes acting on behalf of prior users or roles) from being available to any current users or roles (or current processes acting on behalf of current users or roles) that obtain access to shared system resources after those resources have been released back to the system. This requirement also applies to encrypted representations of information. This requirement does not address information remanence, which refers to residual representation of data that has been nominally deleted; covert channels (including storage or timing channels) where shared resources are manipulated to violate information flow restrictions; or components within systems for which there are only single users or roles." - } - ] - }, - { - "id": "3.13.5", - "title": "3.13.5", - "props": [ - { - "name": "label", - "value": "3.13.5" - }, - { - "name": "sort-id", - "value": "03.13.05" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.13.5_smt", - "name": "statement", - "prose": "Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks." - }, - { - "id": "3.13.5_gdn", - "name": "guidance", - "prose": "Subnetworks that are physically or logically separated from internal networks are referred to as demilitarized zones (DMZs). DMZs are typically implemented with boundary control devices and techniques that include routers, gateways, firewalls, virtualization, or cloud-based technologies. [SP 800-41] provides guidance on firewalls and firewall policy. [SP 800-125B] provides guidance on security for virtualization technologies" - } - ] - }, - { - "id": "3.13.6", - "title": "3.13.6", - "props": [ - { - "name": "label", - "value": "3.13.6" - }, - { - "name": "sort-id", - "value": "03.13.06" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.13.6_smt", - "name": "statement", - "prose": "Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception)." - }, - { - "id": "3.13.6_gdn", - "name": "guidance", - "prose": "This requirement applies to inbound and outbound network communications traffic at the system boundary and at identified points within the system. A deny-all, permit-by-exception network communications traffic policy ensures that only those connections which are essential and approved are allowed." - } - ] - }, - { - "id": "3.13.7", - "title": "3.13.7", - "props": [ - { - "name": "label", - "value": "3.13.7" - }, - { - "name": "sort-id", - "value": "03.13.07" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.13.7_smt", - "name": "statement", - "prose": "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)." - }, - { - "id": "3.13.7_gdn", - "name": "guidance", - "prose": "Split tunneling might be desirable by remote users to communicate with local system resources such as printers or file servers. However, split tunneling allows unauthorized external connections, making the system more vulnerable to attack and to exfiltration of organizational information. This requirement is implemented in remote devices (e.g., notebook computers, smart phones, and tablets) through configuration settings to disable split tunneling in those devices, and by preventing configuration settings from being readily configurable by users. This requirement is implemented in the system by the detection of split tunneling (or of configuration settings that allow split tunneling) in the remote device, and by prohibiting the connection if the remote device is using split tunneling." - } - ] - }, - { - "id": "3.13.8", - "title": "3.13.8", - "props": [ - { - "name": "label", - "value": "3.13.8" - }, - { - "name": "sort-id", - "value": "03.13.08" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.13.8_smt", - "name": "statement", - "prose": "Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards." - }, - { - "id": "3.13.8_gdn", - "name": "guidance", - "prose": "This requirement applies to internal and external networks and any system components that can transmit information including servers, notebook computers, desktop computers, mobile devices, printers, copiers, scanners, and facsimile machines. Communication paths outside the physical protection of controlled boundaries are susceptible to both interception and modification. Organizations relying on commercial providers offering transmission services as commodity services rather than as fully dedicated services (i.e., services which can be highly specialized to individual customer needs), may find it difficult to obtain the necessary assurances regarding the implementation of the controls for transmission confidentiality. In such situations, organizations determine what types of confidentiality services are available in commercial telecommunication service packages. If it is infeasible or impractical to obtain the necessary safeguards and assurances of the effectiveness of the safeguards through appropriate contracting vehicles, organizations implement compensating safeguards or explicitly accept the additional risk. An example of an alternative physical safeguard is a protected distribution system (PDS) where the distribution medium is protected against electronic or physical intercept, thereby ensuring the confidentiality of the information being transmitted. See [NIST CRYPTO]." - } - ] - }, - { - "id": "3.13.9", - "title": "3.13.9", - "props": [ - { - "name": "label", - "value": "3.13.9" - }, - { - "name": "sort-id", - "value": "03.13.09" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.13.9_smt", - "name": "statement", - "prose": "Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity." - }, - { - "id": "3.13.9_gdn", - "name": "guidance", - "prose": "This requirement applies to internal and external networks. Terminating network connections associated with communications sessions include de-allocating associated TCP/IP address or port pairs at the operating system level, or de-allocating networking assignments at the application level if multiple application sessions are using a single, operating system-level network connection. Time periods of user inactivity may be established by organizations and include time periods by type of network access or for specific network accesses" - } - ] - }, - { - "id": "3.13.10", - "title": "3.13.10", - "props": [ - { - "name": "label", - "value": "3.13.10" - }, - { - "name": "sort-id", - "value": "03.13.10" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.13.10_smt", - "name": "statement", - "prose": "Establish and manage cryptographic keys for cryptography employed in organizational systems." - }, - { - "id": "3.13.10_gdn", - "name": "guidance", - "prose": "Cryptographic key management and establishment can be performed using manual procedures or mechanisms supported by manual procedures. Organizations define key management requirements in accordance with applicable federal laws, Executive Orders, policies, directives, regulations, and standards specifying appropriate options, levels, and parameters. [SP 800-56A] and [SP 800-57-1] provide guidance on cryptographic key management and key establishment." - } - ] - }, - { - "id": "3.13.11", - "title": "3.13.11", - "props": [ - { - "name": "label", - "value": "3.13.11" - }, - { - "name": "sort-id", - "value": "03.13.11" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.13.11_smt", - "name": "statement", - "prose": "Employ FIPS-validated cryptography when used to protect the confidentiality of CUI." - }, - { - "id": "3.13.11_gdn", - "name": "guidance", - "prose": "Cryptography can be employed to support many security solutions including the protection of controlled unclassified information, the provision of digital signatures, and the enforcement of information separation when authorized individuals have the necessary clearances for such information but lack the necessary formal access approvals. Cryptography can also be used to support random number generation and hash generation. Cryptographic standards include FIPS-validated cryptography and/or NSA-approved cryptography. See [NIST CRYPTO]; [NIST CAVP]; and [NIST CMVP]." - } - ] - }, - { - "id": "3.13.12", - "title": "3.13.12", - "props": [ - { - "name": "label", - "value": "3.13.12" - }, - { - "name": "sort-id", - "value": "03.13.12" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.13.12_smt", - "name": "statement", - "prose": "Prohibit remote activation of collaborative computing devices and provide indication of devices in use to users present at the device.[29]." - }, - { - "id": "3.13.12_gdn", - "name": "guidance", - "prose": "Collaborative computing devices include networked white boards, cameras, and microphones. Indication of use includes signals to users when collaborative computing devices are activated. Dedicated video conferencing systems, which rely on one of the participants calling or connecting to the other party to activate the video conference, are excluded.\n\n[29] Dedicated video conferencing systems, which rely on one of the participants calling or connecting to the other party to activate the video conference, are excluded." - } - ] - }, - { - "id": "3.13.13", - "title": "3.13.13", - "props": [ - { - "name": "label", - "value": "3.13.13" - }, - { - "name": "sort-id", - "value": "03.13.13" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.13.13_smt", - "name": "statement", - "prose": "Control and monitor the use of mobile code." - }, - { - "id": "3.13.13_gdn", - "name": "guidance", - "prose": "Mobile code technologies include Java, JavaScript, ActiveX, Postscript, PDF, Flash animations, and VBScript. Decisions regarding the use of mobile code in organizational systems are based on the potential for the code to cause damage to the systems if used maliciously. Usage restrictions and implementation guidance apply to the selection and use of mobile code installed on servers and mobile code downloaded and executed on individual workstations, notebook computers, and devices (e.g., smart phones). Mobile code policy and procedures address controlling or preventing the development, acquisition, or introduction of unacceptable mobile code in systems, including requiring mobile code to be digitally signed by a trusted source. [SP 800-28] provides guidance on mobile code." - } - ] - }, - { - "id": "3.13.14", - "title": "3.13.14", - "props": [ - { - "name": "label", - "value": "3.13.14" - }, - { - "name": "sort-id", - "value": "03.13.14" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.13.14_smt", - "name": "statement", - "prose": "Control and monitor the use of Voice over Internet Protocol (VoIP) technologies." - }, - { - "id": "3.13.14_gdn", - "name": "guidance", - "prose": "VoIP has different requirements, features, functionality, availability, and service limitations when compared with the Plain Old Telephone Service (POTS) (i.e., the standard telephone service). In contrast, other telephone services are based on high-speed, digital communications lines, such as Integrated Services Digital Network (ISDN) and Fiber Distributed Data Interface (FDDI). The main distinctions between POTS and non-POTS services are speed and bandwidth. To address the threats associated with VoIP, usage restrictions and implementation guidelines are based on the potential for the VoIP technology to cause damage to the system if it is used maliciously. Threats to VoIP are similar to those inherent with any Internet-based application. [SP 800-58] provides guidance on Voice Over IP Systems." - } - ] - }, - { - "id": "3.13.15", - "title": "3.13.15", - "props": [ - { - "name": "label", - "value": "3.13.15" - }, - { - "name": "sort-id", - "value": "03.13.15" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.13.15_smt", - "name": "statement", - "prose": "Protect the authenticity of communications sessions." - }, - { - "id": "3.13.15_gdn", - "name": "guidance", - "prose": "Authenticity protection includes protecting against man-in-the-middle attacks, session hijacking, and the insertion of false information into communications sessions. This requirement addresses communications protection at the session versus packet level (e.g., sessions in service-oriented architectures providing web-based services) and establishes grounds for confidence at both ends of communications sessions in ongoing identities of other parties and in the validity of information transmitted. [SP 800-77], [SP 800-95], and [SP 800-113] provide guidance on secure communications sessions." - } - ] - }, - { - "id": "3.13.16", - "title": "3.13.16", - "props": [ - { - "name": "label", - "value": "3.13.16" - }, - { - "name": "sort-id", - "value": "03.13.16" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.13.16_smt", - "name": "statement", - "prose": "Protect the confidentiality of CUI at rest." - }, - { - "id": "3.13.16_gdn", - "name": "guidance", - "prose": "Information at rest refers to the state of information when it is not in process or in transit and is located on storage devices as specific components of systems. The focus of protection at rest is not on the type of storage device or the frequency of access but rather the state of the information. Organizations can use different mechanisms to achieve confidentiality protections, including the use of cryptographic mechanisms and file share scanning. Organizations may also use other controls including secure off-line storage in lieu of online storage when adequate protection of information at rest cannot otherwise be achieved or continuous monitoring to identify malicious code at rest. See [NIST CRYPTO]." - } - ] - } - ] - }, - { - "id": "3.14", - "title": "System and Information Integrity", - "controls": [ - { - "id": "3.14.1", - "title": "3.14.1", - "props": [ - { - "name": "label", - "value": "3.14.1" - }, - { - "name": "sort-id", - "value": "03.14.01" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.14.1_smt", - "name": "statement", - "prose": "Identify, report, and correct system flaws in a timely manner." - }, - { - "id": "3.14.1_gdn", - "name": "guidance", - "prose": "Organizations identify systems that are affected by announced software and firmware flaws including potential vulnerabilities resulting from those flaws and report this information to designated personnel with information security responsibilities. Security-relevant updates include patches, service packs, hot fixes, and anti-virus signatures. Organizations address flaws discovered during security assessments, continuous monitoring, incident response activities, and system error handling. Organizations can take advantage of available resources such as the Common Weakness Enumeration (CWE) database or Common Vulnerabilities and Exposures (CVE) database in remediating flaws discovered in organizational systems. Organization-defined time periods for updating security-relevant software and firmware may vary based on a variety of factors including the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). Some types of flaw remediation may require more testing than other types of remediation. [SP 800-40] provides guidance on patch management technologies." - } - ] - }, - { - "id": "3.14.2", - "title": "3.14.2", - "props": [ - { - "name": "label", - "value": "3.14.2" - }, - { - "name": "sort-id", - "value": "03.14.02" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.14.2_smt", - "name": "statement", - "prose": "Provide protection from malicious code at designated locations within organizational systems." - }, - { - "id": "3.14.2_gdn", - "name": "guidance", - "prose": "Designated locations include system entry and exit points which may include firewalls, remote-access servers, workstations, electronic mail servers, web servers, proxy servers, notebook computers, and mobile devices. Malicious code includes viruses, worms, Trojan horses, and spyware. Malicious code can be encoded in various formats (e.g., UUENCODE, Unicode), contained within compressed or hidden files, or hidden in files using techniques such as steganography. Malicious code can be inserted into systems in a variety of ways including web accesses, electronic mail, electronic mail attachments, and portable storage devices. Malicious code insertions occur through the exploitation of system vulnerabilities. Malicious code protection mechanisms include anti-virus signature definitions and reputation-based technologies. A variety of technologies and methods exist to limit or eliminate the effects of malicious code. Pervasive configuration management and comprehensive software integrity controls may be effective in preventing execution of unauthorized code. In addition to commercial off-the-shelf software, malicious code may also be present in custom-built software. This could include logic bombs, back doors, and other types of cyber-attacks that could affect organizational missions/business functions. Traditional malicious code protection mechanisms cannot always detect such code. In these situations, organizations rely instead on other safeguards including secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to help ensure that software does not perform functions other than the functions intended. [SP 800-83] provides guidance on malware incident prevention." - } - ] - }, - { - "id": "3.14.3", - "title": "3.14.3", - "props": [ - { - "name": "label", - "value": "3.14.3" - }, - { - "name": "sort-id", - "value": "03.14.03" - }, - { - "name": "basic-or-derived", - "value": "Basic" - } - ], - "parts": [ - { - "id": "3.14.3_smt", - "name": "statement", - "prose": "Monitor system security alerts and advisories and take action in response." - }, - { - "id": "3.14.3_gdn", - "name": "guidance", - "prose": "There are many publicly available sources of system security alerts and advisories. For example, the Department of Homeland Security\u2019s Cybersecurity and Infrastructure Security Agency (CISA) generates security alerts and advisories to maintain situational awareness across the federal government and in nonfederal organizations. Software vendors, subscription services, and industry information sharing and analysis centers (ISACs) may also provide security alerts and advisories. Examples of response actions include notifying relevant external organizations, for example, external mission/business partners, supply chain partners, external service providers, and peer or supporting organizations. [SP 800-161] provides guidance on supply chain risk management." - } - ] - }, - { - "id": "3.14.4", - "title": "3.14.4", - "props": [ - { - "name": "label", - "value": "3.14.4" - }, - { - "name": "sort-id", - "value": "03.14.04" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.14.4_smt", - "name": "statement", - "prose": "Update malicious code protection mechanisms when new releases are available." - }, - { - "id": "3.14.4_gdn", - "name": "guidance", - "prose": "Malicious code protection mechanisms include anti-virus signature definitions and reputation-based technologies. A variety of technologies and methods exist to limit or eliminate the effects of malicious code. Pervasive configuration management and comprehensive software integrity controls may be effective in preventing execution of unauthorized code. In addition to commercial off-the-shelf software, malicious code may also be present in custom-built software. This could include logic bombs, back doors, and other types of cyber-attacks that could affect organizational missions/business functions. Traditional malicious code protection mechanisms cannot always detect such code. In these situations, organizations rely instead on other safeguards including secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to help ensure that software does not perform functions other than the functions intended." - } - ] - }, - { - "id": "3.14.5", - "title": "3.14.5", - "props": [ - { - "name": "label", - "value": "3.14.5" - }, - { - "name": "sort-id", - "value": "03.14.05" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.14.5_smt", - "name": "statement", - "prose": "Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed." - }, - { - "id": "3.14.5_gdn", - "name": "guidance", - "prose": "Periodic scans of organizational systems and real-time scans of files from external sources can detect malicious code. Malicious code can be encoded in various formats (e.g., UUENCODE, Unicode), contained within compressed or hidden files, or hidden in files using techniques such as steganography. Malicious code can be inserted into systems in a variety of ways including web accesses, electronic mail, electronic mail attachments, and portable storage devices. Malicious code insertions occur through the exploitation of system vulnerabilities." - } - ] - }, - { - "id": "3.14.6", - "title": "3.14.6", - "props": [ - { - "name": "label", - "value": "3.14.6" - }, - { - "name": "sort-id", - "value": "03.14.06" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.14.6_smt", - "name": "statement", - "prose": "Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks." - }, - { - "id": "3.14.6_gdn", - "name": "guidance", - "prose": "System monitoring includes external and internal monitoring. External monitoring includes the observation of events occurring at the system boundary (i.e., part of perimeter defense and boundary protection). Internal monitoring includes the observation of events occurring within the system. Organizations can monitor systems, for example, by observing audit record activities in real time or by observing other system aspects such as access patterns, characteristics of access, and other actions. The monitoring objectives may guide determination of the events. System monitoring capability is achieved through a variety of tools and techniques (e.g., intrusion detection systems, intrusion prevention systems, malicious code protection software, scanning tools, audit record monitoring software, network monitoring software). Strategic locations for monitoring devices include selected perimeter locations and near server farms supporting critical applications, with such devices being employed at managed system interfaces. The granularity of monitoring information collected is based on organizational monitoring objectives and the capability of systems to support such objectives. System monitoring is an integral part of continuous monitoring and incident response programs. Output from system monitoring serves as input to continuous monitoring and incident response programs. A network connection is any connection with a device that communicates through a network (e.g., local area network, Internet). A remote connection is any connection with a device communicating through an external network (e.g., the Internet). Local, network, and remote connections can be either wired or wireless. Unusual or unauthorized activities or conditions related to inbound/outbound communications traffic include internal traffic that indicates the presence of malicious code in systems or propagating among system components, the unauthorized exporting of information, or signaling to external systems. Evidence of malicious code is used to identify potentially compromised systems or system components. System monitoring requirements, including the need for specific types of system monitoring, may be referenced in other requirements. [SP 800-94] provides guidance on intrusion detection and prevention systems." - } - ] - }, - { - "id": "3.14.7", - "title": "3.14.7", - "props": [ - { - "name": "label", - "value": "3.14.7" - }, - { - "name": "sort-id", - "value": "03.14.07" - }, - { - "name": "basic-or-derived", - "value": "Derived" - } - ], - "parts": [ - { - "id": "3.14.7_smt", - "name": "statement", - "prose": "Identify unauthorized use of organizational systems." - }, - { - "id": "3.14.7_gdn", - "name": "guidance", - "prose": "System monitoring includes external and internal monitoring. System monitoring can detect unauthorized use of organizational systems. System monitoring is an integral part of continuous monitoring and incident response programs. Monitoring is achieved through a variety of tools and techniques (e.g., intrusion detection systems, intrusion prevention systems, malicious code protection software, scanning tools, audit record monitoring software, network monitoring software). Output from system monitoring serves as input to continuous monitoring and incident response programs. Unusual/unauthorized activities or conditions related to inbound and outbound communications traffic include internal traffic that indicates the presence of malicious code in systems or propagating among system components, the unauthorized exporting of information, or signaling to external systems. Evidence of malicious code is used to identify potentially compromised systems or system components. System monitoring requirements, including the need for specific types of system monitoring, may be referenced in other requirements. [SP 800-94] provides guidance on intrusion detection and prevention systems." - } - ] - } - ] - } - ] - } -} diff --git a/data/catalogs/NIST_SP-800-53_rev4_catalog.json b/data/catalogs/NIST_SP-800-53_rev4_catalog.json deleted file mode 100644 index 4967ea32..00000000 --- a/data/catalogs/NIST_SP-800-53_rev4_catalog.json +++ /dev/null @@ -1,130117 +0,0 @@ -{ - "catalog": { - "uuid": "cd20580b-7b77-4031-8c06-28bd016f3104", - "metadata": { - "title": "NIST Special Publication 800-53 Revision 4: Security and Privacy Controls for Federal Information Systems and Organizations", - "last-modified": "2026-05-11T16:16:09.00000-00:00", - "version": "2015-01-22", - "oscal-version": "1.2.2", - "props": [ - { - "name": "keywords", - "value": "Assurance, computer security, FISMA, Privacy Act, Risk Management Framework, security controls, security requirements" - } - ], - "links": [ - { - "href": "#16b3b234-3406-44dc-8645-7da61b6e81f1", - "rel": "alternate" - }, - { - "href": "#fb81fb1c-165e-43a4-8264-1dfd3182b630", - "rel": "canonical" - } - ], - "roles": [ - { - "id": "creator", - "title": "Document creator" - }, - { - "id": "contact", - "title": "Contact" - } - ], - "parties": [ - { - "uuid": "93122cb0-95bc-4fdb-8b48-85ff60f9509b", - "type": "organization", - "name": "Joint Task Force, Transformation Initiative", - "email-addresses": [ - "sec-cert@nist.gov" - ], - "addresses": [ - { - "addr-lines": [ - "National Institute of Standards and Technology", - "Attn: Computer Security Division", - "Information Technology Laboratory", - "100 Bureau Drive (Mail Stop 8930)" - ], - "city": "Gaithersburg", - "state": "MD", - "postal-code": "20899-8930" - } - ] - } - ], - "responsible-parties": [ - { - "role-id": "creator", - "party-uuids": [ - "93122cb0-95bc-4fdb-8b48-85ff60f9509b" - ] - }, - { - "role-id": "contact", - "party-uuids": [ - "93122cb0-95bc-4fdb-8b48-85ff60f9509b" - ] - } - ] - }, - "groups": [ - { - "id": "ac", - "class": "family", - "title": "Access Control", - "controls": [ - { - "id": "ac-1", - "class": "SP800-53", - "title": "Access Control Policy and Procedures", - "params": [ - { - "id": "ac-1_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "ac-1_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "ac-1_prm_3", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "AC-1" - }, - { - "name": "sort-id", - "value": "ac-01" - } - ], - "links": [ - { - "href": "#5c201b63-0768-417b-ac22-3f014e3941b2", - "rel": "reference" - }, - { - "href": "#9cb3d8fe-2127-48ba-821e-cdd2d7aee921", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ac-1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ac-1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops, documents, and disseminates to {{ insert: param, ac-1_prm_1 }}:", - "parts": [ - { - "id": "ac-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "An access control policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "ac-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the access control policy and associated access controls; and" - } - ] - }, - { - "id": "ac-1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the current:", - "parts": [ - { - "id": "ac-1_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Access control policy {{ insert: param, ac-1_prm_2 }}; and" - }, - { - "id": "ac-1_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Access control procedures {{ insert: param, ac-1_prm_3 }}." - } - ] - } - ] - }, - { - "id": "ac-1_gdn", - "name": "guidance", - "prose": "This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the AC family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures.", - "links": [ - { - "href": "#pm-9", - "rel": "related" - } - ] - }, - { - "id": "ac-1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(a)" - } - ], - "parts": [ - { - "id": "ac-1.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(a)(1)" - } - ], - "parts": [ - { - "id": "ac-1.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(a)(1)[1]" - } - ], - "prose": "develops and documents an access control policy that addresses:", - "parts": [ - { - "id": "ac-1.a.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(a)(1)[1][a]" - } - ], - "prose": "purpose;" - }, - { - "id": "ac-1.a.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(a)(1)[1][b]" - } - ], - "prose": "scope;" - }, - { - "id": "ac-1.a.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(a)(1)[1][c]" - } - ], - "prose": "roles;" - }, - { - "id": "ac-1.a.1_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(a)(1)[1][d]" - } - ], - "prose": "responsibilities;" - }, - { - "id": "ac-1.a.1_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(a)(1)[1][e]" - } - ], - "prose": "management commitment;" - }, - { - "id": "ac-1.a.1_obj.1.f", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(a)(1)[1][f]" - } - ], - "prose": "coordination among organizational entities;" - }, - { - "id": "ac-1.a.1_obj.1.g", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(a)(1)[1][g]" - } - ], - "prose": "compliance;" - } - ] - }, - { - "id": "ac-1.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(a)(1)[2]" - } - ], - "prose": "defines personnel or roles to whom the access control policy are to be disseminated;" - }, - { - "id": "ac-1.a.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(a)(1)[3]" - } - ], - "prose": "disseminates the access control policy to organization-defined personnel or roles;" - } - ] - }, - { - "id": "ac-1.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(a)(2)" - } - ], - "parts": [ - { - "id": "ac-1.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(a)(2)[1]" - } - ], - "prose": "develops and documents procedures to facilitate the implementation of the access control policy and associated access control controls;" - }, - { - "id": "ac-1.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(a)(2)[2]" - } - ], - "prose": "defines personnel or roles to whom the procedures are to be disseminated;" - }, - { - "id": "ac-1.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(a)(2)[3]" - } - ], - "prose": "disseminates the procedures to organization-defined personnel or roles;" - } - ] - } - ] - }, - { - "id": "ac-1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(b)" - } - ], - "parts": [ - { - "id": "ac-1.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(b)(1)" - } - ], - "parts": [ - { - "id": "ac-1.b.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(b)(1)[1]" - } - ], - "prose": "defines the frequency to review and update the current access control policy;" - }, - { - "id": "ac-1.b.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(b)(1)[2]" - } - ], - "prose": "reviews and updates the current access control policy with the organization-defined frequency;" - } - ] - }, - { - "id": "ac-1.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(b)(2)" - } - ], - "parts": [ - { - "id": "ac-1.b.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(b)(2)[1]" - } - ], - "prose": "defines the frequency to review and update the current access control procedures; and" - }, - { - "id": "ac-1.b.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-1(b)(2)[2]" - } - ], - "prose": "reviews and updates the current access control procedures with the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy and procedures\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with access control responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "ac-2", - "class": "SP800-53", - "title": "Account Management", - "params": [ - { - "id": "ac-2_prm_1", - "label": "organization-defined information system account types" - }, - { - "id": "ac-2_prm_2", - "label": "organization-defined personnel or roles" - }, - { - "id": "ac-2_prm_3", - "label": "organization-defined procedures or conditions" - }, - { - "id": "ac-2_prm_4", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "AC-2" - }, - { - "name": "sort-id", - "value": "ac-02" - } - ], - "parts": [ - { - "id": "ac-2_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ac-2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Identifies and selects the following types of information system accounts to support organizational missions/business functions: {{ insert: param, ac-2_prm_1 }};" - }, - { - "id": "ac-2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Assigns account managers for information system accounts;" - }, - { - "id": "ac-2_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Establishes conditions for group and role membership;" - }, - { - "id": "ac-2_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Specifies authorized users of the information system, group and role membership, and access authorizations (i.e., privileges) and other attributes (as required) for each account;" - }, - { - "id": "ac-2_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Requires approvals by {{ insert: param, ac-2_prm_2 }} for requests to create information system accounts;" - }, - { - "id": "ac-2_smt.f", - "name": "item", - "props": [ - { - "name": "label", - "value": "f." - } - ], - "prose": "Creates, enables, modifies, disables, and removes information system accounts in accordance with {{ insert: param, ac-2_prm_3 }};" - }, - { - "id": "ac-2_smt.g", - "name": "item", - "props": [ - { - "name": "label", - "value": "g." - } - ], - "prose": "Monitors the use of information system accounts;" - }, - { - "id": "ac-2_smt.h", - "name": "item", - "props": [ - { - "name": "label", - "value": "h." - } - ], - "prose": "Notifies account managers:", - "parts": [ - { - "id": "ac-2_smt.h.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "When accounts are no longer required;" - }, - { - "id": "ac-2_smt.h.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "When users are terminated or transferred; and" - }, - { - "id": "ac-2_smt.h.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "When individual information system usage or need-to-know changes;" - } - ] - }, - { - "id": "ac-2_smt.i", - "name": "item", - "props": [ - { - "name": "label", - "value": "i." - } - ], - "prose": "Authorizes access to the information system based on:", - "parts": [ - { - "id": "ac-2_smt.i.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "A valid access authorization;" - }, - { - "id": "ac-2_smt.i.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Intended system usage; and" - }, - { - "id": "ac-2_smt.i.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Other attributes as required by the organization or associated missions/business functions;" - } - ] - }, - { - "id": "ac-2_smt.j", - "name": "item", - "props": [ - { - "name": "label", - "value": "j." - } - ], - "prose": "Reviews accounts for compliance with account management requirements {{ insert: param, ac-2_prm_4 }}; and" - }, - { - "id": "ac-2_smt.k", - "name": "item", - "props": [ - { - "name": "label", - "value": "k." - } - ], - "prose": "Establishes a process for reissuing shared/group account credentials (if deployed) when individuals are removed from the group." - } - ] - }, - { - "id": "ac-2_gdn", - "name": "guidance", - "prose": "Information system account types include, for example, individual, shared, group, system, guest/anonymous, emergency, developer/manufacturer/vendor, temporary, and service. Some of the account management requirements listed above can be implemented by organizational information systems. The identification of authorized users of the information system and the specification of access privileges reflects the requirements in other security controls in the security plan. Users requiring administrative privileges on information system accounts receive additional scrutiny by appropriate organizational personnel (e.g., system owner, mission/business owner, or chief information security officer) responsible for approving such accounts and privileged access. Organizations may choose to define access privileges or other attributes by account, by type of account, or a combination of both. Other attributes required for authorizing access include, for example, restrictions on time-of-day, day-of-week, and point-of-origin. In defining other account attributes, organizations consider system-related requirements (e.g., scheduled maintenance, system upgrades) and mission/business requirements, (e.g., time zone differences, customer requirements, remote access to support travel requirements). Failure to consider these factors could affect information system availability. Temporary and emergency accounts are accounts intended for short-term use. Organizations establish temporary accounts as a part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. Organizations establish emergency accounts in response to crisis situations and with the need for rapid account activation. Therefore, emergency account activation may bypass normal account authorization processes. Emergency and temporary accounts are not to be confused with infrequently used accounts (e.g., local logon accounts used for special tasks defined by organizations or when network resources are unavailable). Such accounts remain available and are not subject to automatic disabling or removal dates. Conditions for disabling or deactivating accounts include, for example: (i) when shared/group, emergency, or temporary accounts are no longer required; or (ii) when individuals are transferred or terminated. Some types of information system accounts may require specialized training.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-5", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ac-10", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#ac-20", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-11", - "rel": "related" - }, - { - "href": "#ma-3", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#ma-5", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "ac-2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(a)" - } - ], - "parts": [ - { - "id": "ac-2.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(a)[1]" - } - ], - "prose": "defines information system account types to be identified and selected to support organizational missions/business functions;" - }, - { - "id": "ac-2.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(a)[2]" - } - ], - "prose": "identifies and selects organization-defined information system account types to support organizational missions/business functions;" - } - ] - }, - { - "id": "ac-2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(b)" - } - ], - "prose": "assigns account managers for information system accounts;" - }, - { - "id": "ac-2.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(c)" - } - ], - "prose": "establishes conditions for group and role membership;" - }, - { - "id": "ac-2.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(d)" - } - ], - "prose": "specifies for each account (as required):", - "parts": [ - { - "id": "ac-2.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(d)[1]" - } - ], - "prose": "authorized users of the information system;" - }, - { - "id": "ac-2.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(d)[2]" - } - ], - "prose": "group and role membership;" - }, - { - "id": "ac-2.d_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(d)[3]" - } - ], - "prose": "access authorizations (i.e., privileges);" - }, - { - "id": "ac-2.d_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(d)[4]" - } - ], - "prose": "other attributes;" - } - ] - }, - { - "id": "ac-2.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(e)" - } - ], - "parts": [ - { - "id": "ac-2.e_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(e)[1]" - } - ], - "prose": "defines personnel or roles required to approve requests to create information system accounts;" - }, - { - "id": "ac-2.e_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(e)[2]" - } - ], - "prose": "requires approvals by organization-defined personnel or roles for requests to create information system accounts;" - } - ] - }, - { - "id": "ac-2.f_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(f)" - } - ], - "parts": [ - { - "id": "ac-2.f_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(f)[1]" - } - ], - "prose": "defines procedures or conditions to:", - "parts": [ - { - "id": "ac-2.f_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(f)[1][a]" - } - ], - "prose": "create information system accounts;" - }, - { - "id": "ac-2.f_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(f)[1][b]" - } - ], - "prose": "enable information system accounts;" - }, - { - "id": "ac-2.f_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(f)[1][c]" - } - ], - "prose": "modify information system accounts;" - }, - { - "id": "ac-2.f_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(f)[1][d]" - } - ], - "prose": "disable information system accounts;" - }, - { - "id": "ac-2.f_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(f)[1][e]" - } - ], - "prose": "remove information system accounts;" - } - ] - }, - { - "id": "ac-2.f_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(f)[2]" - } - ], - "prose": "in accordance with organization-defined procedures or conditions:", - "parts": [ - { - "id": "ac-2.f_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(f)[2][a]" - } - ], - "prose": "creates information system accounts;" - }, - { - "id": "ac-2.f_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(f)[2][b]" - } - ], - "prose": "enables information system accounts;" - }, - { - "id": "ac-2.f_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(f)[2][c]" - } - ], - "prose": "modifies information system accounts;" - }, - { - "id": "ac-2.f_obj.2.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(f)[2][d]" - } - ], - "prose": "disables information system accounts;" - }, - { - "id": "ac-2.f_obj.2.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(f)[2][e]" - } - ], - "prose": "removes information system accounts;" - } - ] - } - ] - }, - { - "id": "ac-2.g_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(g)" - } - ], - "prose": "monitors the use of information system accounts;" - }, - { - "id": "ac-2.h_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(h)" - } - ], - "prose": "notifies account managers:", - "parts": [ - { - "id": "ac-2.h.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(h)(1)" - } - ], - "prose": "when accounts are no longer required;" - }, - { - "id": "ac-2.h.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(h)(2)" - } - ], - "prose": "when users are terminated or transferred;" - }, - { - "id": "ac-2.h.3_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(h)(3)" - } - ], - "prose": "when individual information system usage or need to know changes;" - } - ] - }, - { - "id": "ac-2.i_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(i)" - } - ], - "prose": "authorizes access to the information system based on;", - "parts": [ - { - "id": "ac-2.i.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(i)(1)" - } - ], - "prose": "a valid access authorization;" - }, - { - "id": "ac-2.i.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(i)(2)" - } - ], - "prose": "intended system usage;" - }, - { - "id": "ac-2.i.3_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(i)(3)" - } - ], - "prose": "other attributes as required by the organization or associated missions/business functions;" - } - ] - }, - { - "id": "ac-2.j_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(j)" - } - ], - "parts": [ - { - "id": "ac-2.j_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(j)[1]" - } - ], - "prose": "defines the frequency to review accounts for compliance with account management requirements;" - }, - { - "id": "ac-2.j_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(j)[2]" - } - ], - "prose": "reviews accounts for compliance with account management requirements with the organization-defined frequency; and" - } - ] - }, - { - "id": "ac-2.k_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(k)" - } - ], - "prose": "establishes a process for reissuing shared/group account credentials (if deployed) when individuals are removed from the group." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of active system accounts along with the name of the individual associated with each account\n\nlist of conditions for group and role membership\n\nnotifications or records of recently transferred, separated, or terminated employees\n\nlist of recently disabled information system accounts along with the name of the individual associated with each account\n\naccess authorization records\n\naccount management compliance reviews\n\ninformation system monitoring records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes account management on the information system\n\nautomated mechanisms for implementing account management" - } - ] - } - ], - "controls": [ - { - "id": "ac-2.1", - "class": "SP800-53-enhancement", - "title": "Automated System Account Management", - "props": [ - { - "name": "label", - "value": "AC-2(1)" - }, - { - "name": "sort-id", - "value": "ac-02.01" - } - ], - "parts": [ - { - "id": "ac-2.1_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to support the management of information system accounts." - }, - { - "id": "ac-2.1_gdn", - "name": "guidance", - "prose": "The use of automated mechanisms can include, for example: using email or text messaging to automatically notify account managers when users are terminated or transferred; using the information system to monitor account usage; and using telephonic notification to report atypical system account usage." - }, - { - "id": "ac-2.1_obj", - "name": "objective", - "prose": "Determine if the organization employs automated mechanisms to support the management of information system accounts." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing account management functions" - } - ] - } - ] - }, - { - "id": "ac-2.2", - "class": "SP800-53-enhancement", - "title": "Removal of Temporary / Emergency Accounts", - "params": [ - { - "id": "ac-2.2_prm_1", - "select": { - "choice": [ - "removes", - "disables" - ] - } - }, - { - "id": "ac-2.2_prm_2", - "label": "organization-defined time period for each type of account" - } - ], - "props": [ - { - "name": "label", - "value": "AC-2(2)" - }, - { - "name": "sort-id", - "value": "ac-02.02" - } - ], - "parts": [ - { - "id": "ac-2.2_smt", - "name": "statement", - "prose": "The information system automatically {{ insert: param, ac-2.2_prm_1 }} temporary and emergency accounts after {{ insert: param, ac-2.2_prm_2 }}." - }, - { - "id": "ac-2.2_gdn", - "name": "guidance", - "prose": "This control enhancement requires the removal of both temporary and emergency accounts automatically after a predefined period of time has elapsed, rather than at the convenience of the systems administrator." - }, - { - "id": "ac-2.2_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-2.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(2)[1]" - } - ], - "prose": "the organization defines the time period after which the information system automatically removes or disables temporary and emergency accounts; and" - }, - { - "id": "ac-2.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(2)[2]" - } - ], - "prose": "the information system automatically removes or disables temporary and emergency accounts after the organization-defined time period for each type of account." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system-generated list of temporary accounts removed and/or disabled\n\ninformation system-generated list of emergency accounts removed and/or disabled\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing account management functions" - } - ] - } - ] - }, - { - "id": "ac-2.3", - "class": "SP800-53-enhancement", - "title": "Disable Inactive Accounts", - "params": [ - { - "id": "ac-2.3_prm_1", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "AC-2(3)" - }, - { - "name": "sort-id", - "value": "ac-02.03" - } - ], - "parts": [ - { - "id": "ac-2.3_smt", - "name": "statement", - "prose": "The information system automatically disables inactive accounts after {{ insert: param, ac-2.3_prm_1 }}." - }, - { - "id": "ac-2.3_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-2.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(3)[1]" - } - ], - "prose": "the organization defines the time period after which the information system automatically disables inactive accounts; and" - }, - { - "id": "ac-2.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(3)[2]" - } - ], - "prose": "the information system automatically disables inactive accounts after the organization-defined time period." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system-generated list of temporary accounts removed and/or disabled\n\ninformation system-generated list of emergency accounts removed and/or disabled\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing account management functions" - } - ] - } - ] - }, - { - "id": "ac-2.4", - "class": "SP800-53-enhancement", - "title": "Automated Audit Actions", - "params": [ - { - "id": "ac-2.4_prm_1", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "AC-2(4)" - }, - { - "name": "sort-id", - "value": "ac-02.04" - } - ], - "parts": [ - { - "id": "ac-2.4_smt", - "name": "statement", - "prose": "The information system automatically audits account creation, modification, enabling, disabling, and removal actions, and notifies {{ insert: param, ac-2.4_prm_1 }}." - }, - { - "id": "ac-2.4_gdn", - "name": "guidance", - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - } - ] - }, - { - "id": "ac-2.4_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-2.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(4)[1]" - } - ], - "prose": "the information system automatically audits the following account actions:", - "parts": [ - { - "id": "ac-2.4_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(4)[1][a]" - } - ], - "prose": "creation;" - }, - { - "id": "ac-2.4_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(4)[1][b]" - } - ], - "prose": "modification;" - }, - { - "id": "ac-2.4_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(4)[1][c]" - } - ], - "prose": "enabling;" - }, - { - "id": "ac-2.4_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(4)[1][d]" - } - ], - "prose": "disabling;" - }, - { - "id": "ac-2.4_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(4)[1][e]" - } - ], - "prose": "removal;" - } - ] - }, - { - "id": "ac-2.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(4)[2]" - } - ], - "prose": "the organization defines personnel or roles to be notified of the following account actions:", - "parts": [ - { - "id": "ac-2.4_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(4)[2][a]" - } - ], - "prose": "creation;" - }, - { - "id": "ac-2.4_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(4)[2][b]" - } - ], - "prose": "modification;" - }, - { - "id": "ac-2.4_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(4)[2][c]" - } - ], - "prose": "enabling;" - }, - { - "id": "ac-2.4_obj.2.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(4)[2][d]" - } - ], - "prose": "disabling;" - }, - { - "id": "ac-2.4_obj.2.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(4)[2][e]" - } - ], - "prose": "removal;" - } - ] - }, - { - "id": "ac-2.4_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(4)[3]" - } - ], - "prose": "the information system notifies organization-defined personnel or roles of the following account actions:", - "parts": [ - { - "id": "ac-2.4_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(4)[3][a]" - } - ], - "prose": "creation;" - }, - { - "id": "ac-2.4_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(4)[3][b]" - } - ], - "prose": "modification;" - }, - { - "id": "ac-2.4_obj.3.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(4)[3][c]" - } - ], - "prose": "enabling;" - }, - { - "id": "ac-2.4_obj.3.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(4)[3][d]" - } - ], - "prose": "disabling; and" - }, - { - "id": "ac-2.4_obj.3.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(4)[3][e]" - } - ], - "prose": "removal." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nnotifications/alerts of account creation, modification, enabling, disabling, and removal actions\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing account management functions" - } - ] - } - ] - }, - { - "id": "ac-2.5", - "class": "SP800-53-enhancement", - "title": "Inactivity Logout", - "params": [ - { - "id": "ac-2.5_prm_1", - "label": "organization-defined time-period of expected inactivity or description of when to log out" - } - ], - "props": [ - { - "name": "label", - "value": "AC-2(5)" - }, - { - "name": "sort-id", - "value": "ac-02.05" - } - ], - "parts": [ - { - "id": "ac-2.5_smt", - "name": "statement", - "prose": "The organization requires that users log out when {{ insert: param, ac-2.5_prm_1 }}." - }, - { - "id": "ac-2.5_gdn", - "name": "guidance", - "links": [ - { - "href": "#sc-23", - "rel": "related" - } - ] - }, - { - "id": "ac-2.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-2.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(5)[1]" - } - ], - "prose": "defines either the time period of expected inactivity that requires users to log out or the description of when users are required to log out; and" - }, - { - "id": "ac-2.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(5)[2]" - } - ], - "prose": "requires that users log out when the organization-defined time period of inactivity is reached or in accordance with organization-defined description of when to log out." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsecurity violation reports\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nusers that must comply with inactivity logout policy" - } - ] - } - ] - }, - { - "id": "ac-2.6", - "class": "SP800-53-enhancement", - "title": "Dynamic Privilege Management", - "params": [ - { - "id": "ac-2.6_prm_1", - "label": "organization-defined list of dynamic privilege management capabilities" - } - ], - "props": [ - { - "name": "label", - "value": "AC-2(6)" - }, - { - "name": "sort-id", - "value": "ac-02.06" - } - ], - "parts": [ - { - "id": "ac-2.6_smt", - "name": "statement", - "prose": "The information system implements the following dynamic privilege management capabilities: {{ insert: param, ac-2.6_prm_1 }}." - }, - { - "id": "ac-2.6_gdn", - "name": "guidance", - "prose": "In contrast to conventional access control approaches which employ static information system accounts and predefined sets of user privileges, dynamic access control approaches (e.g., service-oriented architectures) rely on run time access control decisions facilitated by dynamic privilege management. While user identities may remain relatively constant over time, user privileges may change more frequently based on ongoing mission/business requirements and operational needs of organizations. Dynamic privilege management can include, for example, the immediate revocation of privileges from users, as opposed to requiring that users terminate and restart their sessions to reflect any changes in privileges. Dynamic privilege management can also refer to mechanisms that change the privileges of users based on dynamic rules as opposed to editing specific user profiles. This type of privilege management includes, for example, automatic adjustments of privileges if users are operating out of their normal work times, or if information systems are under duress or in emergency maintenance situations. This control enhancement also includes the ancillary effects of privilege changes, for example, the potential changes to encryption keys used for communications. Dynamic privilege management can support requirements for information system resiliency.", - "links": [ - { - "href": "#ac-16", - "rel": "related" - } - ] - }, - { - "id": "ac-2.6_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-2.6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(6)[1]" - } - ], - "prose": "the organization defines a list of dynamic privilege management capabilities to be implemented by the information system; and" - }, - { - "id": "ac-2.6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(6)[2]" - } - ], - "prose": "the information system implements the organization-defined list of dynamic privilege management capabilities." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsystem-generated list of dynamic privilege management capabilities\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system implementing dynamic privilege management capabilities" - } - ] - } - ] - }, - { - "id": "ac-2.7", - "class": "SP800-53-enhancement", - "title": "Role-based Schemes", - "params": [ - { - "id": "ac-2.7_prm_1", - "label": "organization-defined actions" - } - ], - "props": [ - { - "name": "label", - "value": "AC-2(7)" - }, - { - "name": "sort-id", - "value": "ac-02.07" - } - ], - "parts": [ - { - "id": "ac-2.7_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ac-2.7_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Establishes and administers privileged user accounts in accordance with a role-based access scheme that organizes allowed information system access and privileges into roles;" - }, - { - "id": "ac-2.7_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Monitors privileged role assignments; and" - }, - { - "id": "ac-2.7_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Takes {{ insert: param, ac-2.7_prm_1 }} when privileged role assignments are no longer appropriate." - } - ] - }, - { - "id": "ac-2.7_gdn", - "name": "guidance", - "prose": "Privileged roles are organization-defined roles assigned to individuals that allow those individuals to perform certain security-relevant functions that ordinary users are not authorized to perform. These privileged roles include, for example, key management, account management, network and system administration, database administration, and web administration." - }, - { - "id": "ac-2.7_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-2.7.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(7)(a)" - } - ], - "prose": "establishes and administers privileged user accounts in accordance with a role-based access scheme that organizes allowed information system access and privileges into roles;", - "links": [ - { - "href": "#ac-2.7_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ac-2.7.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(7)(b)" - } - ], - "prose": "monitors privileged role assignments;", - "links": [ - { - "href": "#ac-2.7_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "ac-2.7.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(7)(c)" - } - ], - "parts": [ - { - "id": "ac-2.7.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(7)(c)[1]" - } - ], - "prose": "defines actions to be taken when privileged role assignments are no longer appropriate; and" - }, - { - "id": "ac-2.7.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(7)(c)[2]" - } - ], - "prose": "takes organization-defined actions when privileged role assignments are no longer appropriate." - } - ], - "links": [ - { - "href": "#ac-2.7_smt.c", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system-generated list of privileged user accounts and associated role\n\nrecords of actions taken when privileged role assignments are no longer appropriate\n\ninformation system audit records\n\naudit tracking and monitoring reports\n\ninformation system monitoring records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing account management functions\n\nautomated mechanisms monitoring privileged role assignments" - } - ] - } - ] - }, - { - "id": "ac-2.8", - "class": "SP800-53-enhancement", - "title": "Dynamic Account Creation", - "params": [ - { - "id": "ac-2.8_prm_1", - "label": "organization-defined information system accounts" - } - ], - "props": [ - { - "name": "label", - "value": "AC-2(8)" - }, - { - "name": "sort-id", - "value": "ac-02.08" - } - ], - "parts": [ - { - "id": "ac-2.8_smt", - "name": "statement", - "prose": "The information system creates {{ insert: param, ac-2.8_prm_1 }} dynamically." - }, - { - "id": "ac-2.8_gdn", - "name": "guidance", - "prose": "Dynamic approaches for creating information system accounts (e.g., as implemented within service-oriented architectures) rely on establishing accounts (identities) at run time for entities that were previously unknown. Organizations plan for dynamic creation of information system accounts by establishing trust relationships and mechanisms with the appropriate authorities to validate related authorizations and privileges.", - "links": [ - { - "href": "#ac-16", - "rel": "related" - } - ] - }, - { - "id": "ac-2.8_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-2.8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(8)[1]" - } - ], - "prose": "the organization defines information system accounts to be created by the information system dynamically; and" - }, - { - "id": "ac-2.8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(8)[2]" - } - ], - "prose": "the information system creates organization-defined information system accounts dynamically." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsystem-generated list of information system accounts\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing account management functions" - } - ] - } - ] - }, - { - "id": "ac-2.9", - "class": "SP800-53-enhancement", - "title": "Restrictions On Use of Shared / Group Accounts", - "params": [ - { - "id": "ac-2.9_prm_1", - "label": "organization-defined conditions for establishing shared/group accounts" - } - ], - "props": [ - { - "name": "label", - "value": "AC-2(9)" - }, - { - "name": "sort-id", - "value": "ac-02.09" - } - ], - "parts": [ - { - "id": "ac-2.9_smt", - "name": "statement", - "prose": "The organization only permits the use of shared/group accounts that meet {{ insert: param, ac-2.9_prm_1 }}." - }, - { - "id": "ac-2.9_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-2.9_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(9)[1]" - } - ], - "prose": "defines conditions for establishing shared/group accounts; and" - }, - { - "id": "ac-2.9_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(9)[2]" - } - ], - "prose": "only permits the use of shared/group accounts that meet organization-defined conditions for establishing shared/group accounts." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsystem-generated list of shared/group accounts and associated role\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing management of shared/group accounts" - } - ] - } - ] - }, - { - "id": "ac-2.10", - "class": "SP800-53-enhancement", - "title": "Shared / Group Account Credential Termination", - "props": [ - { - "name": "label", - "value": "AC-2(10)" - }, - { - "name": "sort-id", - "value": "ac-02.10" - } - ], - "parts": [ - { - "id": "ac-2.10_smt", - "name": "statement", - "prose": "The information system terminates shared/group account credentials when members leave the group." - }, - { - "id": "ac-2.10_obj", - "name": "objective", - "prose": "Determine if the information system terminates shared/group account credentials when members leave the group." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\naccount access termination records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing account management functions" - } - ] - } - ] - }, - { - "id": "ac-2.11", - "class": "SP800-53-enhancement", - "title": "Usage Conditions", - "params": [ - { - "id": "ac-2.11_prm_1", - "label": "organization-defined circumstances and/or usage conditions" - }, - { - "id": "ac-2.11_prm_2", - "label": "organization-defined information system accounts" - } - ], - "props": [ - { - "name": "label", - "value": "AC-2(11)" - }, - { - "name": "sort-id", - "value": "ac-02.11" - } - ], - "parts": [ - { - "id": "ac-2.11_smt", - "name": "statement", - "prose": "The information system enforces {{ insert: param, ac-2.11_prm_1 }} for {{ insert: param, ac-2.11_prm_2 }}." - }, - { - "id": "ac-2.11_gdn", - "name": "guidance", - "prose": "Organizations can describe the specific conditions or circumstances under which information system accounts can be used, for example, by restricting usage to certain days of the week, time of day, or specific durations of time." - }, - { - "id": "ac-2.11_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-2.11_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(11)[1]" - } - ], - "prose": "the organization defines circumstances and/or usage conditions to be enforced for information system accounts;" - }, - { - "id": "ac-2.11_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(11)[2]" - } - ], - "prose": "the organization defines information system accounts for which organization-defined circumstances and/or usage conditions are to be enforced; and" - }, - { - "id": "ac-2.11_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(11)[3]" - } - ], - "prose": "the information system enforces organization-defined circumstances and/or usage conditions for organization-defined information system accounts." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsystem-generated list of information system accounts and associated assignments of usage circumstances and/or usage conditions\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing account management functions" - } - ] - } - ] - }, - { - "id": "ac-2.12", - "class": "SP800-53-enhancement", - "title": "Account Monitoring / Atypical Usage", - "params": [ - { - "id": "ac-2.12_prm_1", - "label": "organization-defined atypical usage" - }, - { - "id": "ac-2.12_prm_2", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "AC-2(12)" - }, - { - "name": "sort-id", - "value": "ac-02.12" - } - ], - "parts": [ - { - "id": "ac-2.12_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ac-2.12_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Monitors information system accounts for {{ insert: param, ac-2.12_prm_1 }}; and" - }, - { - "id": "ac-2.12_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Reports atypical usage of information system accounts to {{ insert: param, ac-2.12_prm_2 }}." - } - ] - }, - { - "id": "ac-2.12_gdn", - "name": "guidance", - "prose": "Atypical usage includes, for example, accessing information systems at certain times of the day and from locations that are not consistent with the normal usage patterns of individuals working in organizations.", - "links": [ - { - "href": "#ca-7", - "rel": "related" - } - ] - }, - { - "id": "ac-2.12_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-2.12.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(12)(a)" - } - ], - "parts": [ - { - "id": "ac-2.12.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(12)(a)[1]" - } - ], - "prose": "defines atypical usage to be monitored for information system accounts;" - }, - { - "id": "ac-2.12.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(12)(a)[2]" - } - ], - "prose": "monitors information system accounts for organization-defined atypical usage;" - } - ], - "links": [ - { - "href": "#ac-2.12_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ac-2.12.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(12)(b)" - } - ], - "parts": [ - { - "id": "ac-2.12.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(12)(b)[1]" - } - ], - "prose": "defines personnel or roles to whom atypical usage of information system accounts are to be reported; and" - }, - { - "id": "ac-2.12.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(12)(b)[2]" - } - ], - "prose": "reports atypical usage of information system accounts to organization-defined personnel or roles." - } - ], - "links": [ - { - "href": "#ac-2.12_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system monitoring records\n\ninformation system audit records\n\naudit tracking and monitoring reports\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing account management functions" - } - ] - } - ] - }, - { - "id": "ac-2.13", - "class": "SP800-53-enhancement", - "title": "Disable Accounts for High-risk Individuals", - "params": [ - { - "id": "ac-2.13_prm_1", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "AC-2(13)" - }, - { - "name": "sort-id", - "value": "ac-02.13" - } - ], - "parts": [ - { - "id": "ac-2.13_smt", - "name": "statement", - "prose": "The organization disables accounts of users posing a significant risk within {{ insert: param, ac-2.13_prm_1 }} of discovery of the risk." - }, - { - "id": "ac-2.13_gdn", - "name": "guidance", - "prose": "Users posing a significant risk to organizations include individuals for whom reliable evidence or intelligence indicates either the intention to use authorized access to information systems to cause harm or through whom adversaries will cause harm. Harm includes potential adverse impacts to organizational operations and assets, individuals, other organizations, or the Nation. Close coordination between authorizing officials, information system administrators, and human resource managers is essential in order for timely execution of this control enhancement.", - "links": [ - { - "href": "#ps-4", - "rel": "related" - } - ] - }, - { - "id": "ac-2.13_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-2.13_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(13)[1]" - } - ], - "prose": "defines the time period within which accounts are disabled upon discovery of a significant risk posed by users of such accounts; and" - }, - { - "id": "ac-2.13_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-2(13)[2]" - } - ], - "prose": "disables accounts of users posing a significant risk within the organization-defined time period of discovery of the risk." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsystem-generated list of disabled accounts\n\nlist of user activities posing significant organizational risk\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing account management functions" - } - ] - } - ] - } - ] - }, - { - "id": "ac-3", - "class": "SP800-53", - "title": "Access Enforcement", - "props": [ - { - "name": "label", - "value": "AC-3" - }, - { - "name": "sort-id", - "value": "ac-03" - } - ], - "parts": [ - { - "id": "ac-3_smt", - "name": "statement", - "prose": "The information system enforces approved authorizations for logical access to information and system resources in accordance with applicable access control policies." - }, - { - "id": "ac-3_gdn", - "name": "guidance", - "prose": "Access control policies (e.g., identity-based policies, role-based policies, control matrices, cryptography) control access between active entities or subjects (i.e., users or processes acting on behalf of users) and passive entities or objects (e.g., devices, files, records, domains) in information systems. In addition to enforcing authorized access at the information system level and recognizing that information systems can host many applications and services in support of organizational missions and business operations, access enforcement mechanisms can also be employed at the application and service level to provide increased information security.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-5", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ac-16", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#ac-20", - "rel": "related" - }, - { - "href": "#ac-21", - "rel": "related" - }, - { - "href": "#ac-22", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-11", - "rel": "related" - }, - { - "href": "#ma-3", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#ma-5", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - } - ] - }, - { - "id": "ac-3_obj", - "name": "objective", - "prose": "Determine if the information system enforces approved authorizations for logical access to information and system resources in accordance with applicable access control policies." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing access enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of approved authorizations (user privileges)\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with access enforcement responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing access control policy" - } - ] - } - ], - "controls": [ - { - "id": "ac-3.1", - "class": "SP800-53-enhancement", - "title": "Restricted Access to Privileged Functions", - "props": [ - { - "name": "label", - "value": "AC-3(1)" - }, - { - "name": "sort-id", - "value": "ac-03.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#ac-6", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ac-3.2", - "class": "SP800-53-enhancement", - "title": "Dual Authorization", - "params": [ - { - "id": "ac-3.2_prm_1", - "label": "organization-defined privileged commands and/or other organization-defined actions" - } - ], - "props": [ - { - "name": "label", - "value": "AC-3(2)" - }, - { - "name": "sort-id", - "value": "ac-03.02" - } - ], - "parts": [ - { - "id": "ac-3.2_smt", - "name": "statement", - "prose": "The information system enforces dual authorization for {{ insert: param, ac-3.2_prm_1 }}." - }, - { - "id": "ac-3.2_gdn", - "name": "guidance", - "prose": "Dual authorization mechanisms require the approval of two authorized individuals in order to execute. Organizations do not require dual authorization mechanisms when immediate responses are necessary to ensure public and environmental safety. Dual authorization may also be known as two-person control.", - "links": [ - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#mp-6", - "rel": "related" - } - ] - }, - { - "id": "ac-3.2_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-3.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(2)[1]" - } - ], - "prose": "the organization defines privileged commands and/or other actions for which dual authorization is to be enforced; and" - }, - { - "id": "ac-3.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(2)[2]" - } - ], - "prose": "the information system enforces dual authorization for organization-defined privileged commands and/or other organization-defined actions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing access enforcement and dual authorization\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of privileged commands requiring dual authorization\n\nlist of actions requiring dual authorization\n\nlist of approved authorizations (user privileges)\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with access enforcement responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Dual authorization mechanisms implementing access control policy" - } - ] - } - ] - }, - { - "id": "ac-3.3", - "class": "SP800-53-enhancement", - "title": "Mandatory Access Control", - "params": [ - { - "id": "ac-3.3_prm_1", - "label": "organization-defined mandatory access control policy" - }, - { - "id": "ac-3.3_prm_2", - "label": "organization-defined subjects" - }, - { - "id": "ac-3.3_prm_3", - "label": "organization-defined privileges (i.e., they are trusted subjects)" - } - ], - "props": [ - { - "name": "label", - "value": "AC-3(3)" - }, - { - "name": "sort-id", - "value": "ac-03.03" - } - ], - "parts": [ - { - "id": "ac-3.3_smt", - "name": "statement", - "prose": "The information system enforces {{ insert: param, ac-3.3_prm_1 }} over all subjects and objects where the policy:", - "parts": [ - { - "id": "ac-3.3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Is uniformly enforced across all subjects and objects within the boundary of the information system;" - }, - { - "id": "ac-3.3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Specifies that a subject that has been granted access to information is constrained from doing any of the following;", - "parts": [ - { - "id": "ac-3.3_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "(1)" - } - ], - "prose": "Passing the information to unauthorized subjects or objects;" - }, - { - "id": "ac-3.3_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "(2)" - } - ], - "prose": "Granting its privileges to other subjects;" - }, - { - "id": "ac-3.3_smt.b.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "(3)" - } - ], - "prose": "Changing one or more security attributes on subjects, objects, the information system, or information system components;" - }, - { - "id": "ac-3.3_smt.b.4", - "name": "item", - "props": [ - { - "name": "label", - "value": "(4)" - } - ], - "prose": "Choosing the security attributes and attribute values to be associated with newly created or modified objects; or" - }, - { - "id": "ac-3.3_smt.b.5", - "name": "item", - "props": [ - { - "name": "label", - "value": "(5)" - } - ], - "prose": "Changing the rules governing access control; and" - } - ] - }, - { - "id": "ac-3.3_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Specifies that {{ insert: param, ac-3.3_prm_2 }} may explicitly be granted {{ insert: param, ac-3.3_prm_3 }} such that they are not limited by some or all of the above constraints." - } - ] - }, - { - "id": "ac-3.3_gdn", - "name": "guidance", - "prose": "Mandatory access control as defined in this control enhancement is synonymous with nondiscretionary access control, and is not constrained only to certain historical uses (e.g., implementations using the Bell-LaPadula Model). The above class of mandatory access control policies constrains what actions subjects can take with information obtained from data objects for which they have already been granted access, thus preventing the subjects from passing the information to unauthorized subjects and objects. This class of mandatory access control policies also constrains what actions subjects can take with respect to the propagation of access control privileges; that is, a subject with a privilege cannot pass that privilege to other subjects. The policy is uniformly enforced over all subjects and objects to which the information system has control. Otherwise, the access control policy can be circumvented. This enforcement typically is provided via an implementation that meets the reference monitor concept (see AC-25). The policy is bounded by the information system boundary (i.e., once the information is passed outside of the control of the system, additional means may be required to ensure that the constraints on the information remain in effect). The trusted subjects described above are granted privileges consistent with the concept of least privilege (see AC-6). Trusted subjects are only given the minimum privileges relative to the above policy necessary for satisfying organizational mission/business needs. The control is most applicable when there is some policy mandate (e.g., law, Executive Order, directive, or regulation) that establishes a policy regarding access to sensitive/classified information and some users of the information system are not authorized access to all sensitive/classified information resident in the information system. This control can operate in conjunction with AC-3 (4). A subject that is constrained in its operation by policies governed by this control is still able to operate under the less rigorous constraints of AC-3 (4), but policies governed by this control take precedence over the less rigorous constraints of AC-3 (4). For example, while a mandatory access control policy imposes a constraint preventing a subject from passing information to another subject operating at a different sensitivity label, AC-3 (4) permits the subject to pass the information to any subject with the same sensitivity label as the subject.", - "links": [ - { - "href": "#ac-25", - "rel": "related" - }, - { - "href": "#sc-11", - "rel": "related" - } - ] - }, - { - "id": "ac-3.3_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-3.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(3)[1]" - } - ], - "prose": "the organization defines mandatory access control policies to be enforced over all subjects and objects;" - }, - { - "id": "ac-3.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(3)[2]" - } - ], - "prose": "the organization defines subjects over which organization-defined mandatory access control policies are to be enforced;" - }, - { - "id": "ac-3.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(3)[3]" - } - ], - "prose": "the organization defines objects over which organization-defined mandatory access control policies are to be enforced;" - }, - { - "id": "ac-3.3_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(3)[4]" - } - ], - "prose": "the organization defines subjects that may explicitly be granted privileges such that they are not limited by the constraints specified elsewhere within this control;" - }, - { - "id": "ac-3.3_obj.5", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(3)[5]" - } - ], - "prose": "the organization defines privileges that may be granted to organization-defined subjects;" - }, - { - "id": "ac-3.3_obj.6", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(3)[6]" - } - ], - "prose": "the information system enforces organization-defined mandatory access control policies over all subjects and objects where the policy specifies that:", - "parts": [ - { - "id": "ac-3.3.a_obj.6", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(3)[6](a)" - } - ], - "prose": "the policy is uniformly enforced across all subjects and objects within the boundary of the information system;", - "links": [ - { - "href": "#ac-3.3_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ac-3.3.b_obj.6", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(3)[6](b)" - } - ], - "prose": "a subject that has been granted access to information is constrained from doing any of the following:", - "parts": [ - { - "id": "ac-3.3.b.1_obj.6", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(3)[6](b)(1)" - } - ], - "prose": "passing the information to unauthorized subjects or objects;", - "links": [ - { - "href": "#ac-3.3_smt.b.1", - "rel": "corresp" - } - ] - }, - { - "id": "ac-3.3.b.2_obj.6", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(3)[6](b)(2)" - } - ], - "prose": "granting its privileges to other subjects;", - "links": [ - { - "href": "#ac-3.3_smt.b.2", - "rel": "corresp" - } - ] - }, - { - "id": "ac-3.3.b.3_obj.6", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(3)[6](b)(3)" - } - ], - "prose": "changing one or more security attributes on:", - "parts": [ - { - "id": "ac-3.3.b.3_obj.6.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(3)[6](b)(3)[a]" - } - ], - "prose": "subjects;" - }, - { - "id": "ac-3.3.b.3_obj.6.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(3)[6](b)(3)[b]" - } - ], - "prose": "objects;" - }, - { - "id": "ac-3.3.b.3_obj.6.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(3)[6](b)(3)[c]" - } - ], - "prose": "the information system; or" - }, - { - "id": "ac-3.3.b.3_obj.6.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(3)[6](b)(3)[d]" - } - ], - "prose": "system components;" - } - ], - "links": [ - { - "href": "#ac-3.3_smt.b.3", - "rel": "corresp" - } - ] - }, - { - "id": "ac-3.3.b.4_obj.6", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(3)[6](b)(4)" - } - ], - "prose": "choosing the security attributes and attribute values to be associated with newly created or modified objects; or", - "links": [ - { - "href": "#ac-3.3_smt.b.4", - "rel": "corresp" - } - ] - }, - { - "id": "ac-3.3.b.5_obj.6", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(3)[6](b)(5)" - } - ], - "prose": "changing the rules governing access control; and", - "links": [ - { - "href": "#ac-3.3_smt.b.5", - "rel": "corresp" - } - ] - } - ], - "links": [ - { - "href": "#ac-3.3_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "ac-3.3.c_obj.6", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(3)[6](c)" - } - ], - "prose": "organization-defined subjects may explicitly be granted organization-defined privileges such that they are not limited by some or all of the above constraints.", - "links": [ - { - "href": "#ac-3.3_smt.c", - "rel": "corresp" - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nmandatory access control policies\n\nprocedures addressing access enforcement\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of subjects and objects (i.e., users and resources) requiring enforcement of mandatory access control policies\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with access enforcement responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing mandatory access control" - } - ] - } - ] - }, - { - "id": "ac-3.4", - "class": "SP800-53-enhancement", - "title": "Discretionary Access Control", - "params": [ - { - "id": "ac-3.4_prm_1", - "label": "organization-defined discretionary access control policy" - } - ], - "props": [ - { - "name": "label", - "value": "AC-3(4)" - }, - { - "name": "sort-id", - "value": "ac-03.04" - } - ], - "parts": [ - { - "id": "ac-3.4_smt", - "name": "statement", - "prose": "The information system enforces {{ insert: param, ac-3.4_prm_1 }} over defined subjects and objects where the policy specifies that a subject that has been granted access to information can do one or more of the following:", - "parts": [ - { - "id": "ac-3.4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Pass the information to any other subjects or objects;" - }, - { - "id": "ac-3.4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Grant its privileges to other subjects;" - }, - { - "id": "ac-3.4_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Change security attributes on subjects, objects, the information system, or the information system’s components;" - }, - { - "id": "ac-3.4_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "(d)" - } - ], - "prose": "Choose the security attributes to be associated with newly created or revised objects; or" - }, - { - "id": "ac-3.4_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "(e)" - } - ], - "prose": "Change the rules governing access control." - } - ] - }, - { - "id": "ac-3.4_gdn", - "name": "guidance", - "prose": "When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects. This control enhancement can operate in conjunction with AC-3 (3). A subject that is constrained in its operation by policies governed by AC-3 (3) is still able to operate under the less rigorous constraints of this control enhancement. Thus, while AC-3 (3) imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, AC-3 (4) permits the subject to pass the information to any subject at the same sensitivity level. The policy is bounded by the information system boundary. Once the information is passed outside of the control of the information system, additional means may be required to ensure that the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control." - }, - { - "id": "ac-3.4_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-3.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(4)[1]" - } - ], - "prose": "the organization defines discretionary access control policies to be enforced over defined subjects and objects;" - }, - { - "id": "ac-3.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(4)[2]" - } - ], - "prose": "the information system enforces organization-defined discretionary access control policies over defined subjects and objects where the policy specifies that a subject has been granted access to information and can do one or more of the following:", - "parts": [ - { - "id": "ac-3.4.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(4)[2](a)" - } - ], - "prose": "pass the information to any other subjects or objects;", - "links": [ - { - "href": "#ac-3.4_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ac-3.4.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(4)[2](b)" - } - ], - "prose": "grant its privileges to other subjects;", - "links": [ - { - "href": "#ac-3.4_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "ac-3.4.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(4)[2](c)" - } - ], - "prose": "change security attributes on:", - "parts": [ - { - "id": "ac-3.4.c_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(4)[2](c)[a]" - } - ], - "prose": "subjects," - }, - { - "id": "ac-3.4.c_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(4)[2](c)[b]" - } - ], - "prose": "objects," - }, - { - "id": "ac-3.4.c_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(4)[2](c)[c]" - } - ], - "prose": "the information system, or" - }, - { - "id": "ac-3.4.c_obj.2.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(4)[2](c)[d]" - } - ], - "prose": "the information system’s components;" - } - ], - "links": [ - { - "href": "#ac-3.4_smt.c", - "rel": "corresp" - } - ] - }, - { - "id": "ac-3.4.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(4)[2](d)" - } - ], - "prose": "choose the security attributes to be associated with newly created or revised objects; or", - "links": [ - { - "href": "#ac-3.4_smt.d", - "rel": "corresp" - } - ] - }, - { - "id": "ac-3.4.e_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(4)[2](e)" - } - ], - "prose": "change the rules governing access control.", - "links": [ - { - "href": "#ac-3.4_smt.e", - "rel": "corresp" - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\ndiscretionary access control policies\n\nprocedures addressing access enforcement\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of subjects and objects (i.e., users and resources) requiring enforcement of discretionary access control policies\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with access enforcement responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing discretionary access control policy" - } - ] - } - ] - }, - { - "id": "ac-3.5", - "class": "SP800-53-enhancement", - "title": "Security-relevant Information", - "params": [ - { - "id": "ac-3.5_prm_1", - "label": "organization-defined security-relevant information" - } - ], - "props": [ - { - "name": "label", - "value": "AC-3(5)" - }, - { - "name": "sort-id", - "value": "ac-03.05" - } - ], - "parts": [ - { - "id": "ac-3.5_smt", - "name": "statement", - "prose": "The information system prevents access to {{ insert: param, ac-3.5_prm_1 }} except during secure, non-operable system states." - }, - { - "id": "ac-3.5_gdn", - "name": "guidance", - "prose": "Security-relevant information is any information within information systems that can potentially impact the operation of security functions or the provision of security services in a manner that could result in failure to enforce system security policies or maintain the isolation of code and data. Security-relevant information includes, for example, filtering rules for routers/firewalls, cryptographic key management information, configuration parameters for security services, and access control lists. Secure, non-operable system states include the times in which information systems are not performing mission/business-related processing (e.g., the system is off-line for maintenance, troubleshooting, boot-up, shut down).", - "links": [ - { - "href": "#cm-3", - "rel": "related" - } - ] - }, - { - "id": "ac-3.5_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-3.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(5)[1]" - } - ], - "prose": "the organization defines security-relevant information to which the information system prevents access except during secure, non-operable system states; and" - }, - { - "id": "ac-3.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(5)[2]" - } - ], - "prose": "the information system prevents access to organization-defined security-relevant information except during secure, non-operable system states." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing access enforcement\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with access enforcement responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms preventing access to security-relevant information within the information system" - } - ] - } - ] - }, - { - "id": "ac-3.6", - "class": "SP800-53-enhancement", - "title": "Protection of User and System Information", - "props": [ - { - "name": "label", - "value": "AC-3(6)" - }, - { - "name": "sort-id", - "value": "ac-03.06" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#mp-4", - "rel": "incorporated-into" - }, - { - "href": "#sc-28", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ac-3.7", - "class": "SP800-53-enhancement", - "title": "Role-based Access Control", - "params": [ - { - "id": "ac-3.7_prm_1", - "label": "organization-defined roles and users authorized to assume such roles" - } - ], - "props": [ - { - "name": "label", - "value": "AC-3(7)" - }, - { - "name": "sort-id", - "value": "ac-03.07" - } - ], - "parts": [ - { - "id": "ac-3.7_smt", - "name": "statement", - "prose": "The information system enforces a role-based access control policy over defined subjects and objects and controls access based upon {{ insert: param, ac-3.7_prm_1 }}." - }, - { - "id": "ac-3.7_gdn", - "name": "guidance", - "prose": "Role-based access control (RBAC) is an access control policy that restricts information system access to authorized users. Organizations can create specific roles based on job functions and the authorizations (i.e., privileges) to perform needed operations on organizational information systems associated with the organization-defined roles. When users are assigned to the organizational roles, they inherit the authorizations or privileges defined for those roles. RBAC simplifies privilege administration for organizations because privileges are not assigned directly to every user (which can be a significant number of individuals for mid- to large-size organizations) but are instead acquired through role assignments. RBAC can be implemented either as a mandatory or discretionary form of access control. For organizations implementing RBAC with mandatory access controls, the requirements in AC-3 (3) define the scope of the subjects and objects covered by the policy." - }, - { - "id": "ac-3.7_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-3.7_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(7)[1]" - } - ], - "prose": "the organization defines roles to control information system access;" - }, - { - "id": "ac-3.7_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(7)[2]" - } - ], - "prose": "the organization defines users authorized to assume the organization-defined roles;" - }, - { - "id": "ac-3.7_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(7)[3]" - } - ], - "prose": "the information system controls access based on organization-defined roles and users authorized to assume such roles;" - }, - { - "id": "ac-3.7_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(7)[4]" - } - ], - "prose": "the information system enforces a role-based access control policy over defined:", - "parts": [ - { - "id": "ac-3.7_obj.4.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(7)[4][a]" - } - ], - "prose": "subjects, and" - }, - { - "id": "ac-3.7_obj.4.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(7)[4][b]" - } - ], - "prose": "objects." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nrole-based access control policies\n\nprocedures addressing access enforcement\n\nsecurity plan, information system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of roles, users, and associated privileges required to control information system access\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with access enforcement responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing role-based access control policy" - } - ] - } - ] - }, - { - "id": "ac-3.8", - "class": "SP800-53-enhancement", - "title": "Revocation of Access Authorizations", - "params": [ - { - "id": "ac-3.8_prm_1", - "label": "organization-defined rules governing the timing of revocations of access authorizations" - } - ], - "props": [ - { - "name": "label", - "value": "AC-3(8)" - }, - { - "name": "sort-id", - "value": "ac-03.08" - } - ], - "parts": [ - { - "id": "ac-3.8_smt", - "name": "statement", - "prose": "The information system enforces the revocation of access authorizations resulting from changes to the security attributes of subjects and objects based on {{ insert: param, ac-3.8_prm_1 }}." - }, - { - "id": "ac-3.8_gdn", - "name": "guidance", - "prose": "Revocation of access rules may differ based on the types of access revoked. For example, if a subject (i.e., user or process) is removed from a group, access may not be revoked until the next time the object (e.g., file) is opened or until the next time the subject attempts a new access to the object. Revocation based on changes to security labels may take effect immediately. Organizations can provide alternative approaches on how to make revocations immediate if information systems cannot provide such capability and immediate revocation is necessary." - }, - { - "id": "ac-3.8_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-3.8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(8)[1]" - } - ], - "prose": "the organization defines rules governing the timing of revocations of access authorizations; and" - }, - { - "id": "ac-3.8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(8)[2]" - } - ], - "prose": "the information system enforces the revocation of access authorizations resulting from changes to the security attributes of subjects and objects based on organization-defined rules governing the timing of revocations of access authorizations." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing access enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nrules governing revocation of access authorizations, information system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with access enforcement responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing access enforcement functions" - } - ] - } - ] - }, - { - "id": "ac-3.9", - "class": "SP800-53-enhancement", - "title": "Controlled Release", - "params": [ - { - "id": "ac-3.9_prm_1", - "label": "organization-defined information system or system component" - }, - { - "id": "ac-3.9_prm_2", - "label": "organization-defined security safeguards" - }, - { - "id": "ac-3.9_prm_3", - "label": "organization-defined security safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "AC-3(9)" - }, - { - "name": "sort-id", - "value": "ac-03.09" - } - ], - "parts": [ - { - "id": "ac-3.9_smt", - "name": "statement", - "prose": "The information system does not release information outside of the established system boundary unless:", - "parts": [ - { - "id": "ac-3.9_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "The receiving {{ insert: param, ac-3.9_prm_1 }} provides {{ insert: param, ac-3.9_prm_2 }}; and" - }, - { - "id": "ac-3.9_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": " {{ insert: param, ac-3.9_prm_3 }} are used to validate the appropriateness of the information designated for release." - } - ] - }, - { - "id": "ac-3.9_gdn", - "name": "guidance", - "prose": "Information systems can only protect organizational information within the confines of established system boundaries. Additional security safeguards may be needed to ensure that such information is adequately protected once it is passed beyond the established information system boundaries. Examples of information leaving the system boundary include transmitting information to an external information system or printing the information on one of its printers. In cases where the information system is unable to make a determination of the adequacy of the protections provided by entities outside its boundary, as a mitigating control, organizations determine procedurally whether the external information systems are providing adequate security. The means used to determine the adequacy of the security provided by external information systems include, for example, conducting inspections or periodic testing, establishing agreements between the organization and its counterpart organizations, or some other process. The means used by external entities to protect the information received need not be the same as those used by the organization, but the means employed are sufficient to provide consistent adjudication of the security policy to protect the information. This control enhancement requires information systems to employ technical or procedural means to validate the information prior to releasing it to external systems. For example, if the information system passes information to another system controlled by another organization, technical means are employed to validate that the security attributes associated with the exported information are appropriate for the receiving system. Alternatively, if the information system passes information to a printer in organization-controlled space, procedural means can be employed to ensure that only appropriately authorized individuals gain access to the printer. This control enhancement is most applicable when there is some policy mandate (e.g., law, Executive Order, directive, or regulation) that establishes policy regarding access to the information, and that policy applies beyond the realm of a particular information system or organization." - }, - { - "id": "ac-3.9_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-3.9_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(9)[1]" - } - ], - "prose": "the organization defines the information system or system component authorized to receive information released outside of the established system boundary of the information system releasing such information;" - }, - { - "id": "ac-3.9_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(9)[2]" - } - ], - "prose": "the organization defines security safeguards to be provided by organization-defined information system or system component receiving information released from an information system outside of the established system boundary;" - }, - { - "id": "ac-3.9_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(9)[3]" - } - ], - "prose": "the organization defines security safeguards to be used to validate the appropriateness of the information designated for release;" - }, - { - "id": "ac-3.9_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(9)[4]" - } - ], - "prose": "the information system does not release information outside of the established system boundary unless:", - "parts": [ - { - "id": "ac-3.9.a_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(9)[4](a)" - } - ], - "prose": "the receiving organization-defined information system or system component provides organization-defined security safeguards; and", - "links": [ - { - "href": "#ac-3.9_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ac-3.9.b_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(9)[4](b)" - } - ], - "prose": "the organization-defined security safeguards are used to validate the appropriateness of the information designated for release.", - "links": [ - { - "href": "#ac-3.9_smt.b", - "rel": "corresp" - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing access enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of security safeguards provided by receiving information system or system components\n\nlist of security safeguards validating appropriateness of information designated for release\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with access enforcement responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing access enforcement functions" - } - ] - } - ] - }, - { - "id": "ac-3.10", - "class": "SP800-53-enhancement", - "title": "Audited Override of Access Control Mechanisms", - "params": [ - { - "id": "ac-3.10_prm_1", - "label": "organization-defined conditions" - } - ], - "props": [ - { - "name": "label", - "value": "AC-3(10)" - }, - { - "name": "sort-id", - "value": "ac-03.10" - } - ], - "parts": [ - { - "id": "ac-3.10_smt", - "name": "statement", - "prose": "The organization employs an audited override of automated access control mechanisms under {{ insert: param, ac-3.10_prm_1 }}." - }, - { - "id": "ac-3.10_gdn", - "name": "guidance", - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - } - ] - }, - { - "id": "ac-3.10_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-3.10_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(10)[1]" - } - ], - "prose": "defines conditions under which to employ an audited override of automated access control mechanisms; and" - }, - { - "id": "ac-3.10_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-3(10)[2]" - } - ], - "prose": "employs an audited override of automated access control mechanisms under organization-defined conditions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing access enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nconditions for employing audited override of automated access control mechanisms\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with access enforcement responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing access enforcement functions" - } - ] - } - ] - } - ] - }, - { - "id": "ac-4", - "class": "SP800-53", - "title": "Information Flow Enforcement", - "params": [ - { - "id": "ac-4_prm_1", - "label": "organization-defined information flow control policies" - } - ], - "props": [ - { - "name": "label", - "value": "AC-4" - }, - { - "name": "sort-id", - "value": "ac-04" - } - ], - "parts": [ - { - "id": "ac-4_smt", - "name": "statement", - "prose": "The information system enforces approved authorizations for controlling the flow of information within the system and between interconnected systems based on {{ insert: param, ac-4_prm_1 }}." - }, - { - "id": "ac-4_gdn", - "name": "guidance", - "prose": "Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. Flow control restrictions include, for example, keeping export-controlled information from being transmitted in the clear to the Internet, blocking outside traffic that claims to be from within the organization, restricting web requests to the Internet that are not from the internal web proxy server, and limiting information transfers between organizations based on data structures and content. Transferring information between information systems representing different security domains with different security policies introduces risk that such transfers violate one or more domain security policies. In such situations, information owners/stewards provide guidance at designated policy enforcement points between interconnected systems. Organizations consider mandating specific architectural solutions when required to enforce specific security policies. Enforcement includes, for example: (i) prohibiting information transfers between interconnected systems (i.e., allowing access only); (ii) employing hardware mechanisms to enforce one-way information flows; and (iii) implementing trustworthy regrading mechanisms to reassign security attributes and security labels. Organizations commonly employ information flow control policies and enforcement mechanisms to control the flow of information between designated sources and destinations (e.g., networks, individuals, and devices) within information systems and between interconnected systems. Flow control is based on the characteristics of the information and/or the information path. Enforcement occurs, for example, in boundary protection devices (e.g., gateways, routers, guards, encrypted tunnels, firewalls) that employ rule sets or establish configuration settings that restrict information system services, provide a packet-filtering capability based on header information, or message-filtering capability based on message content (e.g., implementing key word searches or using document characteristics). Organizations also consider the trustworthiness of filtering/inspection mechanisms (i.e., hardware, firmware, and software components) that are critical to information flow enforcement. Control enhancements 3 through 22 primarily address cross-domain solution needs which focus on more advanced filtering techniques, in-depth analysis, and stronger flow enforcement mechanisms implemented in cross-domain products, for example, high-assurance guards. Such capabilities are generally not available in commercial off-the-shelf information technology products.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#ac-21", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sc-2", - "rel": "related" - }, - { - "href": "#sc-5", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-18", - "rel": "related" - } - ] - }, - { - "id": "ac-4_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4[1]" - } - ], - "prose": "the organization defines information flow control policies to control the flow of information within the system and between interconnected systems; and" - }, - { - "id": "ac-4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4[2]" - } - ], - "prose": "the information system enforces approved authorizations for controlling the flow of information within the system and between interconnected systems based on organization-defined information flow control policies." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system baseline configuration\n\nlist of information flow authorizations\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement policy" - } - ] - } - ], - "controls": [ - { - "id": "ac-4.1", - "class": "SP800-53-enhancement", - "title": "Object Security Attributes", - "params": [ - { - "id": "ac-4.1_prm_1", - "label": "organization-defined security attributes" - }, - { - "id": "ac-4.1_prm_2", - "label": "organization-defined information, source, and destination objects" - }, - { - "id": "ac-4.1_prm_3", - "label": "organization-defined information flow control policies" - } - ], - "props": [ - { - "name": "label", - "value": "AC-4(1)" - }, - { - "name": "sort-id", - "value": "ac-04.01" - } - ], - "parts": [ - { - "id": "ac-4.1_smt", - "name": "statement", - "prose": "The information system uses {{ insert: param, ac-4.1_prm_1 }} associated with {{ insert: param, ac-4.1_prm_2 }} to enforce {{ insert: param, ac-4.1_prm_3 }} as a basis for flow control decisions." - }, - { - "id": "ac-4.1_gdn", - "name": "guidance", - "prose": "Information flow enforcement mechanisms compare security attributes associated with information (data content and data structure) and source/destination objects, and respond appropriately (e.g., block, quarantine, alert administrator) when the mechanisms encounter information flows not explicitly allowed by information flow policies. For example, an information object labeled Secret would be allowed to flow to a destination object labeled Secret, but an information object labeled Top Secret would not be allowed to flow to a destination object labeled Secret. Security attributes can also include, for example, source and destination addresses employed in traffic filter firewalls. Flow enforcement using explicit security attributes can be used, for example, to control the release of certain types of information.", - "links": [ - { - "href": "#ac-16", - "rel": "related" - } - ] - }, - { - "id": "ac-4.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-4.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(1)[1]" - } - ], - "prose": "the organization defines information flow control policies as a basis for flow control decisions;" - }, - { - "id": "ac-4.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(1)[2]" - } - ], - "prose": "the organization defines security attributes to be associated with information, source, and destination objects;" - }, - { - "id": "ac-4.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(1)[3]" - } - ], - "prose": "the organization defines the following objects to be associated with organization-defined security attributes:", - "parts": [ - { - "id": "ac-4.1_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(1)[3][a]" - } - ], - "prose": "information;" - }, - { - "id": "ac-4.1_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(1)[3][b]" - } - ], - "prose": "source;" - }, - { - "id": "ac-4.1_obj.3.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(1)[3][c]" - } - ], - "prose": "destination; and" - } - ] - }, - { - "id": "ac-4.1_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(1)[4]" - } - ], - "prose": "the information system uses organization-defined security attributes associated with organization-defined information, source, and destination objects to enforce organization-defined information flow control policies as a basis for flow control decisions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of security attributes and associated information, source, and destination objects enforcing information flow control policies\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement policy" - } - ] - } - ] - }, - { - "id": "ac-4.2", - "class": "SP800-53-enhancement", - "title": "Processing Domains", - "params": [ - { - "id": "ac-4.2_prm_1", - "label": "organization-defined information flow control policies" - } - ], - "props": [ - { - "name": "label", - "value": "AC-4(2)" - }, - { - "name": "sort-id", - "value": "ac-04.02" - } - ], - "parts": [ - { - "id": "ac-4.2_smt", - "name": "statement", - "prose": "The information system uses protected processing domains to enforce {{ insert: param, ac-4.2_prm_1 }} as a basis for flow control decisions." - }, - { - "id": "ac-4.2_gdn", - "name": "guidance", - "prose": "Within information systems, protected processing domains are processing spaces that have controlled interactions with other processing spaces, thus enabling control of information flows between these spaces and to/from data/information objects. A protected processing domain can be provided, for example, by implementing domain and type enforcement. In domain and type enforcement, information system processes are assigned to domains; information is identified by types; and information flows are controlled based on allowed information accesses (determined by domain and type), allowed signaling among domains, and allowed process transitions to other domains." - }, - { - "id": "ac-4.2_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-4.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(2)[1]" - } - ], - "prose": "the organization defines information flow control policies as a basis for flow control decisions; and" - }, - { - "id": "ac-4.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(2)[2]" - } - ], - "prose": "the information system uses protected processing domains to enforce organization-defined information flow control policies as a basis for flow control decisions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system security architecture and associated documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement policy" - } - ] - } - ] - }, - { - "id": "ac-4.3", - "class": "SP800-53-enhancement", - "title": "Dynamic Information Flow Control", - "params": [ - { - "id": "ac-4.3_prm_1", - "label": "organization-defined policies" - } - ], - "props": [ - { - "name": "label", - "value": "AC-4(3)" - }, - { - "name": "sort-id", - "value": "ac-04.03" - } - ], - "parts": [ - { - "id": "ac-4.3_smt", - "name": "statement", - "prose": "The information system enforces dynamic information flow control based on {{ insert: param, ac-4.3_prm_1 }}." - }, - { - "id": "ac-4.3_gdn", - "name": "guidance", - "prose": "Organizational policies regarding dynamic information flow control include, for example, allowing or disallowing information flows based on changing conditions or mission/operational considerations. Changing conditions include, for example, changes in organizational risk tolerance due to changes in the immediacy of mission/business needs, changes in the threat environment, and detection of potentially harmful or adverse events.", - "links": [ - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "ac-4.3_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-4.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(3)[1]" - } - ], - "prose": "the organization defines policies to enforce dynamic information flow control; and" - }, - { - "id": "ac-4.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(3)[2]" - } - ], - "prose": "the information system enforces dynamic information flow control based on organization-defined policies." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system security architecture and associated documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement policy" - } - ] - } - ] - }, - { - "id": "ac-4.4", - "class": "SP800-53-enhancement", - "title": "Content Check Encrypted Information", - "params": [ - { - "id": "ac-4.4_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "decrypting the information", - "blocking the flow of the encrypted information", - "terminating communications sessions attempting to pass encrypted information", - " {{ insert: param, ac-4.4_prm_2 }} " - ] - } - }, - { - "id": "ac-4.4_prm_2", - "depends-on": "ac-4.4_prm_1", - "label": "organization-defined procedure or method" - } - ], - "props": [ - { - "name": "label", - "value": "AC-4(4)" - }, - { - "name": "sort-id", - "value": "ac-04.04" - } - ], - "parts": [ - { - "id": "ac-4.4_smt", - "name": "statement", - "prose": "The information system prevents encrypted information from bypassing content-checking mechanisms by {{ insert: param, ac-4.4_prm_1 }}." - }, - { - "id": "ac-4.4_gdn", - "name": "guidance", - "links": [ - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "ac-4.4_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-4.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(4)[1]" - } - ], - "prose": "the organization defines a procedure or method to be employed to prevent encrypted information from bypassing content-checking mechanisms;" - }, - { - "id": "ac-4.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(4)[2]" - } - ], - "prose": "the information system prevents encrypted information from bypassing content-checking mechanisms by doing one or more of the following:", - "parts": [ - { - "id": "ac-4.4_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(4)[2][a]" - } - ], - "prose": "decrypting the information;" - }, - { - "id": "ac-4.4_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(4)[2][b]" - } - ], - "prose": "blocking the flow of the encrypted information;" - }, - { - "id": "ac-4.4_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(4)[2][c]" - } - ], - "prose": "terminating communications sessions attempting to pass encrypted information; and/or" - }, - { - "id": "ac-4.4_obj.2.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(4)[2][d]" - } - ], - "prose": "employing the organization-defined procedure or method." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement policy" - } - ] - } - ] - }, - { - "id": "ac-4.5", - "class": "SP800-53-enhancement", - "title": "Embedded Data Types", - "params": [ - { - "id": "ac-4.5_prm_1", - "label": "organization-defined limitations" - } - ], - "props": [ - { - "name": "label", - "value": "AC-4(5)" - }, - { - "name": "sort-id", - "value": "ac-04.05" - } - ], - "parts": [ - { - "id": "ac-4.5_smt", - "name": "statement", - "prose": "The information system enforces {{ insert: param, ac-4.5_prm_1 }} on embedding data types within other data types." - }, - { - "id": "ac-4.5_gdn", - "name": "guidance", - "prose": "Embedding data types within other data types may result in reduced flow control effectiveness. Data type embedding includes, for example, inserting executable files as objects within word processing files, inserting references or descriptive information into a media file, and compressed or archived data types that may include multiple embedded data types. Limitations on data type embedding consider the levels of embedding and prohibit levels of data type embedding that are beyond the capability of the inspection tools." - }, - { - "id": "ac-4.5_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-4.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(5)[1]" - } - ], - "prose": "the organization defines limitations to be enforced on embedding data types within other data types; and" - }, - { - "id": "ac-4.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(5)[2]" - } - ], - "prose": "the information system enforces organization-defined limitations on embedding data types within other data types." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of limitations to be enforced on embedding data types within other data types\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement policy" - } - ] - } - ] - }, - { - "id": "ac-4.6", - "class": "SP800-53-enhancement", - "title": "Metadata", - "params": [ - { - "id": "ac-4.6_prm_1", - "label": "organization-defined metadata" - } - ], - "props": [ - { - "name": "label", - "value": "AC-4(6)" - }, - { - "name": "sort-id", - "value": "ac-04.06" - } - ], - "parts": [ - { - "id": "ac-4.6_smt", - "name": "statement", - "prose": "The information system enforces information flow control based on {{ insert: param, ac-4.6_prm_1 }}." - }, - { - "id": "ac-4.6_gdn", - "name": "guidance", - "prose": "Metadata is information used to describe the characteristics of data. Metadata can include structural metadata describing data structures (e.g., data format, syntax, and semantics) or descriptive metadata describing data contents (e.g., age, location, telephone number). Enforcing allowed information flows based on metadata enables simpler and more effective flow control. Organizations consider the trustworthiness of metadata with regard to data accuracy (i.e., knowledge that the metadata values are correct with respect to the data), data integrity (i.e., protecting against unauthorized changes to metadata tags), and the binding of metadata to the data payload (i.e., ensuring sufficiently strong binding techniques with appropriate levels of assurance).", - "links": [ - { - "href": "#ac-16", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "ac-4.6_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-4.6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(6)[1]" - } - ], - "prose": "the organization defines metadata to be used as a means of enforcing information flow control; and" - }, - { - "id": "ac-4.6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(6)[2]" - } - ], - "prose": "the information system enforces information flow control based on organization-defined metadata." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ntypes of metadata used to enforce information flow control decisions\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement policy" - } - ] - } - ] - }, - { - "id": "ac-4.7", - "class": "SP800-53-enhancement", - "title": "One-way Flow Mechanisms", - "params": [ - { - "id": "ac-4.7_prm_1", - "label": "organization-defined one-way information flows" - } - ], - "props": [ - { - "name": "label", - "value": "AC-4(7)" - }, - { - "name": "sort-id", - "value": "ac-04.07" - } - ], - "parts": [ - { - "id": "ac-4.7_smt", - "name": "statement", - "prose": "The information system enforces {{ insert: param, ac-4.7_prm_1 }} using hardware mechanisms." - }, - { - "id": "ac-4.7_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-4.7_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(7)[1]" - } - ], - "prose": "the organization defines one-way information flows to be enforced by the information system; and" - }, - { - "id": "ac-4.7_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(7)[2]" - } - ], - "prose": "the information system enforces organization-defined one-way information flows using hardware mechanisms." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system hardware mechanisms and associated configurations\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Hardware mechanisms implementing information flow enforcement policy" - } - ] - } - ] - }, - { - "id": "ac-4.8", - "class": "SP800-53-enhancement", - "title": "Security Policy Filters", - "params": [ - { - "id": "ac-4.8_prm_1", - "label": "organization-defined security policy filters" - }, - { - "id": "ac-4.8_prm_2", - "label": "organization-defined information flows" - } - ], - "props": [ - { - "name": "label", - "value": "AC-4(8)" - }, - { - "name": "sort-id", - "value": "ac-04.08" - } - ], - "parts": [ - { - "id": "ac-4.8_smt", - "name": "statement", - "prose": "The information system enforces information flow control using {{ insert: param, ac-4.8_prm_1 }} as a basis for flow control decisions for {{ insert: param, ac-4.8_prm_2 }}." - }, - { - "id": "ac-4.8_gdn", - "name": "guidance", - "prose": "Organization-defined security policy filters can address data structures and content. For example, security policy filters for data structures can check for maximum file lengths, maximum field sizes, and data/file types (for structured and unstructured data). Security policy filters for data content can check for specific words (e.g., dirty/clean word filters), enumerated values or data value ranges, and hidden content. Structured data permits the interpretation of data content by applications. Unstructured data typically refers to digital information without a particular data structure or with a data structure that does not facilitate the development of rule sets to address the particular sensitivity of the information conveyed by the data or the associated flow enforcement decisions. Unstructured data consists of: (i) bitmap objects that are inherently non language-based (i.e., image, video, or audio files); and (ii) textual objects that are based on written or printed languages (e.g., commercial off-the-shelf word processing documents, spreadsheets, or emails). Organizations can implement more than one security policy filter to meet information flow control objectives (e.g., employing clean word lists in conjunction with dirty word lists may help to reduce false positives)." - }, - { - "id": "ac-4.8_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-4.8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(8)[1]" - } - ], - "prose": "the organization defines security policy filters to be used as a basis for enforcing flow control decisions;" - }, - { - "id": "ac-4.8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(8)[2]" - } - ], - "prose": "the organization defines information flows for which flow control decisions are to be applied and enforced; and" - }, - { - "id": "ac-4.8_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(8)[3]" - } - ], - "prose": "the information system enforces information flow control using organization-defined security policy filters as a basis for flow control decisions for organization-defined information flows." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of security policy filters regulating flow control decisions\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement policy" - } - ] - } - ] - }, - { - "id": "ac-4.9", - "class": "SP800-53-enhancement", - "title": "Human Reviews", - "params": [ - { - "id": "ac-4.9_prm_1", - "label": "organization-defined information flows" - }, - { - "id": "ac-4.9_prm_2", - "label": "organization-defined conditions" - } - ], - "props": [ - { - "name": "label", - "value": "AC-4(9)" - }, - { - "name": "sort-id", - "value": "ac-04.09" - } - ], - "parts": [ - { - "id": "ac-4.9_smt", - "name": "statement", - "prose": "The information system enforces the use of human reviews for {{ insert: param, ac-4.9_prm_1 }} under the following conditions: {{ insert: param, ac-4.9_prm_2 }}." - }, - { - "id": "ac-4.9_gdn", - "name": "guidance", - "prose": "Organizations define security policy filters for all situations where automated flow control decisions are possible. When a fully automated flow control decision is not possible, then a human review may be employed in lieu of, or as a complement to, automated security policy filtering. Human reviews may also be employed as deemed necessary by organizations." - }, - { - "id": "ac-4.9_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-4.9_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(9)[1]" - } - ], - "prose": "the organization defines information flows requiring the use of human reviews;" - }, - { - "id": "ac-4.9_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(9)[2]" - } - ], - "prose": "the organization defines conditions under which the use of human reviews for organization-defined information flows is to be enforced; and" - }, - { - "id": "ac-4.9_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(9)[3]" - } - ], - "prose": "the information system enforces the use of human reviews for organization-defined information flows under organization-defined conditions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nrecords of human reviews regarding information flows\n\nlist of conditions requiring human reviews for information flows\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with information flow enforcement responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms enforcing the use of human reviews" - } - ] - } - ] - }, - { - "id": "ac-4.10", - "class": "SP800-53-enhancement", - "title": "Enable / Disable Security Policy Filters", - "params": [ - { - "id": "ac-4.10_prm_1", - "label": "organization-defined security policy filters" - }, - { - "id": "ac-4.10_prm_2", - "label": "organization-defined conditions" - } - ], - "props": [ - { - "name": "label", - "value": "AC-4(10)" - }, - { - "name": "sort-id", - "value": "ac-04.10" - } - ], - "parts": [ - { - "id": "ac-4.10_smt", - "name": "statement", - "prose": "The information system provides the capability for privileged administrators to enable/disable {{ insert: param, ac-4.10_prm_1 }} under the following conditions: {{ insert: param, ac-4.10_prm_2 }}." - }, - { - "id": "ac-4.10_gdn", - "name": "guidance", - "prose": "For example, as allowed by the information system authorization, administrators can enable security policy filters to accommodate approved data types." - }, - { - "id": "ac-4.10_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-4.10_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(10)[1]" - } - ], - "prose": "the organization defines security policy filters that privileged administrators have the capability to enable/disable;" - }, - { - "id": "ac-4.10_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(10)[2]" - } - ], - "prose": "the organization-defined conditions under which privileged administrators have the capability to enable/disable organization-defined security policy filters; and" - }, - { - "id": "ac-4.10_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(10)[3]" - } - ], - "prose": "the information system provides the capability for privileged administrators to enable/disable organization-defined security policy filters under organization-defined conditions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\ninformation flow information policies\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of security policy filters enabled/disabled by privileged administrators\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for enabling/disabling security policy filters\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement policy" - } - ] - } - ] - }, - { - "id": "ac-4.11", - "class": "SP800-53-enhancement", - "title": "Configuration of Security Policy Filters", - "params": [ - { - "id": "ac-4.11_prm_1", - "label": "organization-defined security policy filters" - } - ], - "props": [ - { - "name": "label", - "value": "AC-4(11)" - }, - { - "name": "sort-id", - "value": "ac-04.11" - } - ], - "parts": [ - { - "id": "ac-4.11_smt", - "name": "statement", - "prose": "The information system provides the capability for privileged administrators to configure {{ insert: param, ac-4.11_prm_1 }} to support different security policies." - }, - { - "id": "ac-4.11_gdn", - "name": "guidance", - "prose": "For example, to reflect changes in security policies, administrators can change the list of “dirty words” that security policy mechanisms check in accordance with the definitions provided by organizations." - }, - { - "id": "ac-4.11_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-4.11_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(11)[1]" - } - ], - "prose": "the organization defines security policy filters that privileged administrators have the capability to configure to support different security policies; and" - }, - { - "id": "ac-4.11_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(11)[2]" - } - ], - "prose": "the information system provides the capability for privileged administrators to configure organization-defined security policy filters to support different security policies." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of security policy filters\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for configuring security policy filters\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement policy" - } - ] - } - ] - }, - { - "id": "ac-4.12", - "class": "SP800-53-enhancement", - "title": "Data Type Identifiers", - "params": [ - { - "id": "ac-4.12_prm_1", - "label": "organization-defined data type identifiers" - } - ], - "props": [ - { - "name": "label", - "value": "AC-4(12)" - }, - { - "name": "sort-id", - "value": "ac-04.12" - } - ], - "parts": [ - { - "id": "ac-4.12_smt", - "name": "statement", - "prose": "The information system, when transferring information between different security domains, uses {{ insert: param, ac-4.12_prm_1 }} to validate data essential for information flow decisions." - }, - { - "id": "ac-4.12_gdn", - "name": "guidance", - "prose": "Data type identifiers include, for example, filenames, file types, file signatures/tokens, and multiple internal file signatures/tokens. Information systems may allow transfer of data only if compliant with data type format specifications." - }, - { - "id": "ac-4.12_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-4.12_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(12)[1]" - } - ], - "prose": "the organization defines data type identifiers to be used, when transferring information between different security domains, to validate data essential for information flow decisions; and" - }, - { - "id": "ac-4.12_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(12)[2]" - } - ], - "prose": "the information system, when transferring information between different security domains, uses organization-defined data type identifiers to validate data essential for information flow decisions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of data type identifiers\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement policy" - } - ] - } - ] - }, - { - "id": "ac-4.13", - "class": "SP800-53-enhancement", - "title": "Decomposition into Policy-relevant Subcomponents", - "params": [ - { - "id": "ac-4.13_prm_1", - "label": "organization-defined policy-relevant subcomponents" - } - ], - "props": [ - { - "name": "label", - "value": "AC-4(13)" - }, - { - "name": "sort-id", - "value": "ac-04.13" - } - ], - "parts": [ - { - "id": "ac-4.13_smt", - "name": "statement", - "prose": "The information system, when transferring information between different security domains, decomposes information into {{ insert: param, ac-4.13_prm_1 }} for submission to policy enforcement mechanisms." - }, - { - "id": "ac-4.13_gdn", - "name": "guidance", - "prose": "Policy enforcement mechanisms apply filtering, inspection, and/or sanitization rules to the policy-relevant subcomponents of information to facilitate flow enforcement prior to transferring such information to different security domains. Parsing transfer files facilitates policy decisions on source, destination, certificates, classification, attachments, and other security-related component differentiators." - }, - { - "id": "ac-4.13_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-4.13_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(13)[1]" - } - ], - "prose": "the organization defines policy-relevant subcomponents to decompose information for submission to policy enforcement mechanisms when transferring such information between different security domains; and" - }, - { - "id": "ac-4.13_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(13)[2]" - } - ], - "prose": "the information system, when transferring information between different security domains, decomposes information into organization-defined policy-relevant subcomponents for submission to policy enforcement mechanisms." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement policy" - } - ] - } - ] - }, - { - "id": "ac-4.14", - "class": "SP800-53-enhancement", - "title": "Security Policy Filter Constraints", - "params": [ - { - "id": "ac-4.14_prm_1", - "label": "organization-defined security policy filters" - } - ], - "props": [ - { - "name": "label", - "value": "AC-4(14)" - }, - { - "name": "sort-id", - "value": "ac-04.14" - } - ], - "parts": [ - { - "id": "ac-4.14_smt", - "name": "statement", - "prose": "The information system, when transferring information between different security domains, implements {{ insert: param, ac-4.14_prm_1 }} requiring fully enumerated formats that restrict data structure and content." - }, - { - "id": "ac-4.14_gdn", - "name": "guidance", - "prose": "Data structure and content restrictions reduce the range of potential malicious and/or unsanctioned content in cross-domain transactions. Security policy filters that restrict data structures include, for example, restricting file sizes and field lengths. Data content policy filters include, for example: (i) encoding formats for character sets (e.g., Universal Character Set Transformation Formats, American Standard Code for Information Interchange); (ii) restricting character data fields to only contain alpha-numeric characters; (iii) prohibiting special characters; and (iv) validating schema structures." - }, - { - "id": "ac-4.14_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-4.14_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(14)[1]" - } - ], - "prose": "the organization defines security policy filters to be implemented that require fully enumerated formats restricting data structure and content when transferring information between different security domains; and" - }, - { - "id": "ac-4.14_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(14)[2]" - } - ], - "prose": "the information system, when transferring information between different security domains, implements organization-defined security policy filters requiring fully enumerated formats that restrict data structure and content." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of security policy filters\n\nlist of data content policy filters\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement policy" - } - ] - } - ] - }, - { - "id": "ac-4.15", - "class": "SP800-53-enhancement", - "title": "Detection of Unsanctioned Information", - "params": [ - { - "id": "ac-4.15_prm_1", - "label": "organized-defined unsanctioned information" - }, - { - "id": "ac-4.15_prm_2", - "label": "organization-defined security policy" - } - ], - "props": [ - { - "name": "label", - "value": "AC-4(15)" - }, - { - "name": "sort-id", - "value": "ac-04.15" - } - ], - "parts": [ - { - "id": "ac-4.15_smt", - "name": "statement", - "prose": "The information system, when transferring information between different security domains, examines the information for the presence of {{ insert: param, ac-4.15_prm_1 }} and prohibits the transfer of such information in accordance with the {{ insert: param, ac-4.15_prm_2 }}." - }, - { - "id": "ac-4.15_gdn", - "name": "guidance", - "prose": "Detection of unsanctioned information includes, for example, checking all information to be transferred for malicious code and dirty words.", - "links": [ - { - "href": "#si-3", - "rel": "related" - } - ] - }, - { - "id": "ac-4.15_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-4.15_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(15)[1]" - } - ], - "prose": "the organization defines unsanctioned information to be detected when transferring information between different security domains;" - }, - { - "id": "ac-4.15_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(15)[2]" - } - ], - "prose": "the organization defines the security policy that requires the transfer of organization-defined unsanctioned information between different security domains to be prohibited when the presence of such information is detected; and" - }, - { - "id": "ac-4.15_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(15)[3]" - } - ], - "prose": "the information system, when transferring information between different security domains, examines the information for the presence of organization-defined unsanctioned information and prohibits the transfer of such information in accordance with the organization-defined security policy." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of unsanctioned information types and associated information\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement policy" - } - ] - } - ] - }, - { - "id": "ac-4.16", - "class": "SP800-53-enhancement", - "title": "Information Transfers On Interconnected Systems", - "props": [ - { - "name": "label", - "value": "AC-4(16)" - }, - { - "name": "sort-id", - "value": "ac-04.16" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#ac-4", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ac-4.17", - "class": "SP800-53-enhancement", - "title": "Domain Authentication", - "params": [ - { - "id": "ac-4.17_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "organization, system, application, individual" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "AC-4(17)" - }, - { - "name": "sort-id", - "value": "ac-04.17" - } - ], - "parts": [ - { - "id": "ac-4.17_smt", - "name": "statement", - "prose": "The information system uniquely identifies and authenticates source and destination points by {{ insert: param, ac-4.17_prm_1 }} for information transfer." - }, - { - "id": "ac-4.17_gdn", - "name": "guidance", - "prose": "Attribution is a critical component of a security concept of operations. The ability to identify source and destination points for information flowing in information systems, allows the forensic reconstruction of events when required, and encourages policy compliance by attributing policy violations to specific organizations/individuals. Successful domain authentication requires that information system labels distinguish among systems, organizations, and individuals involved in preparing, sending, receiving, or disseminating information.", - "links": [ - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - } - ] - }, - { - "id": "ac-4.17_obj", - "name": "objective", - "prose": "Determine if the information system uniquely identifies and authenticates:", - "parts": [ - { - "id": "ac-4.17_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(17)[1]" - } - ], - "parts": [ - { - "id": "ac-4.17_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(17)[1][a]" - } - ], - "prose": "source points for information transfer;" - }, - { - "id": "ac-4.17_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(17)[1][b]" - } - ], - "prose": "destination points for information transfer;" - } - ] - }, - { - "id": "ac-4.17_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(17)[2]" - } - ], - "prose": "by one or more of the following:", - "parts": [ - { - "id": "ac-4.17_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(17)[2][a]" - } - ], - "prose": "organization;" - }, - { - "id": "ac-4.17_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(17)[2][b]" - } - ], - "prose": "system;" - }, - { - "id": "ac-4.17_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(17)[2][c]" - } - ], - "prose": "application; and/or" - }, - { - "id": "ac-4.17_obj.2.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(17)[2][d]" - } - ], - "prose": "individual." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\nprocedures addressing source and destination domain identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement policy" - } - ] - } - ] - }, - { - "id": "ac-4.18", - "class": "SP800-53-enhancement", - "title": "Security Attribute Binding", - "params": [ - { - "id": "ac-4.18_prm_1", - "label": "organization-defined binding techniques" - } - ], - "props": [ - { - "name": "label", - "value": "AC-4(18)" - }, - { - "name": "sort-id", - "value": "ac-04.18" - } - ], - "parts": [ - { - "id": "ac-4.18_smt", - "name": "statement", - "prose": "The information system binds security attributes to information using {{ insert: param, ac-4.18_prm_1 }} to facilitate information flow policy enforcement." - }, - { - "id": "ac-4.18_gdn", - "name": "guidance", - "prose": "Binding techniques implemented by information systems affect the strength of security attribute binding to information. Binding strength and the assurance associated with binding techniques play an important part in the trust organizations have in the information flow enforcement process. The binding techniques affect the number and degree of additional reviews required by organizations.", - "links": [ - { - "href": "#ac-16", - "rel": "related" - }, - { - "href": "#sc-16", - "rel": "related" - } - ] - }, - { - "id": "ac-4.18_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-4.18_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(18)[1]" - } - ], - "prose": "the organization defines binding techniques to be used to facilitate information flow policy enforcement; and" - }, - { - "id": "ac-4.18_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(18)[2]" - } - ], - "prose": "the information system binds security attributes to information using organization-defined binding techniques to facilitate information flow policy enforcement." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information flow enforcement policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of binding techniques to bind security attributes to information\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information flow enforcement responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement functions" - } - ] - } - ] - }, - { - "id": "ac-4.19", - "class": "SP800-53-enhancement", - "title": "Validation of Metadata", - "props": [ - { - "name": "label", - "value": "AC-4(19)" - }, - { - "name": "sort-id", - "value": "ac-04.19" - } - ], - "parts": [ - { - "id": "ac-4.19_smt", - "name": "statement", - "prose": "The information system, when transferring information between different security domains, applies the same security policy filtering to metadata as it applies to data payloads." - }, - { - "id": "ac-4.19_gdn", - "name": "guidance", - "prose": "This control enhancement requires the validation of metadata and the data to which the metadata applies. Some organizations distinguish between metadata and data payloads (i.e., only the data to which the metadata is bound). Other organizations do not make such distinctions, considering metadata and the data to which the metadata applies as part of the payload. All information (including metadata and the data to which the metadata applies) is subject to filtering and inspection." - }, - { - "id": "ac-4.19_obj", - "name": "objective", - "prose": "Determine if the information system, when transferring information between different security domains, applies the same security policy filtering to metadata as it applies to data payloads." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information flow enforcement policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of security policy filtering criteria applied to metadata and data payloads\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information flow enforcement responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement functions" - } - ] - } - ] - }, - { - "id": "ac-4.20", - "class": "SP800-53-enhancement", - "title": "Approved Solutions", - "params": [ - { - "id": "ac-4.20_prm_1", - "label": "organization-defined solutions in approved configurations" - }, - { - "id": "ac-4.20_prm_2", - "label": "organization-defined information" - } - ], - "props": [ - { - "name": "label", - "value": "AC-4(20)" - }, - { - "name": "sort-id", - "value": "ac-04.20" - } - ], - "parts": [ - { - "id": "ac-4.20_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, ac-4.20_prm_1 }} to control the flow of {{ insert: param, ac-4.20_prm_2 }} across security domains." - }, - { - "id": "ac-4.20_gdn", - "name": "guidance", - "prose": "Organizations define approved solutions and configurations in cross-domain policies and guidance in accordance with the types of information flows across classification boundaries. The Unified Cross Domain Management Office (UCDMO) provides a baseline listing of approved cross-domain solutions." - }, - { - "id": "ac-4.20_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-4.20_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(20)[1]" - } - ], - "prose": "defines solutions in approved configurations to control the flow of information across security domains;" - }, - { - "id": "ac-4.20_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(20)[2]" - } - ], - "prose": "defines information for which organization-defined solutions in approved configurations are to be employed to control the flow of such information across security domains; and" - }, - { - "id": "ac-4.20_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(20)[3]" - } - ], - "prose": "employs organization-defined solutions in approved configurations to control the flow of organization-defined information across security domains." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information flow enforcement policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of solutions in approved configurations\n\napproved configuration baselines\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information flow enforcement responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement functions" - } - ] - } - ] - }, - { - "id": "ac-4.21", - "class": "SP800-53-enhancement", - "title": "Physical / Logical Separation of Information Flows", - "params": [ - { - "id": "ac-4.21_prm_1", - "label": "organization-defined mechanisms and/or techniques" - }, - { - "id": "ac-4.21_prm_2", - "label": "organization-defined required separations by types of information" - } - ], - "props": [ - { - "name": "label", - "value": "AC-4(21)" - }, - { - "name": "sort-id", - "value": "ac-04.21" - } - ], - "parts": [ - { - "id": "ac-4.21_smt", - "name": "statement", - "prose": "The information system separates information flows logically or physically using {{ insert: param, ac-4.21_prm_1 }} to accomplish {{ insert: param, ac-4.21_prm_2 }}." - }, - { - "id": "ac-4.21_gdn", - "name": "guidance", - "prose": "Enforcing the separation of information flows by type can enhance protection by ensuring that information is not commingled while in transit and by enabling flow control by transmission paths perhaps not otherwise achievable. Types of separable information include, for example, inbound and outbound communications traffic, service requests and responses, and information of differing security categories." - }, - { - "id": "ac-4.21_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-4.21_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(21)[1]" - } - ], - "prose": "the organization defines the required separations of information flows by types of information;" - }, - { - "id": "ac-4.21_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(21)[2]" - } - ], - "prose": "the organization defines the mechanisms and/or techniques to be used to separate information flows logically or physically; and" - }, - { - "id": "ac-4.21_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-4(21)[3]" - } - ], - "prose": "the information system separates information flows logically or physically using organization-defined mechanisms and/or techniques to accomplish organization-defined required separations by types of information." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information flow enforcement policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of required separation of information flows by information types\n\nlist of mechanisms and/or techniques used to logically or physically separate information flows\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information flow enforcement responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement functions" - } - ] - } - ] - }, - { - "id": "ac-4.22", - "class": "SP800-53-enhancement", - "title": "Access Only", - "props": [ - { - "name": "label", - "value": "AC-4(22)" - }, - { - "name": "sort-id", - "value": "ac-04.22" - } - ], - "parts": [ - { - "id": "ac-4.22_smt", - "name": "statement", - "prose": "The information system provides access from a single device to computing platforms, applications, or data residing on multiple different security domains, while preventing any information flow between the different security domains." - }, - { - "id": "ac-4.22_gdn", - "name": "guidance", - "prose": "The information system, for example, provides a desktop for users to access each connected security domain without providing any mechanisms to allow transfer of information between the different security domains." - }, - { - "id": "ac-4.22_obj", - "name": "objective", - "prose": "Determine if the information system provides access from a single device to computing platforms, applications, or data residing on multiple different security domains, while preventing any information flow between the different security domains." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information flow enforcement policy\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information flow enforcement responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information flow enforcement functions" - } - ] - } - ] - } - ] - }, - { - "id": "ac-5", - "class": "SP800-53", - "title": "Separation of Duties", - "params": [ - { - "id": "ac-5_prm_1", - "label": "organization-defined duties of individuals" - } - ], - "props": [ - { - "name": "label", - "value": "AC-5" - }, - { - "name": "sort-id", - "value": "ac-05" - } - ], - "parts": [ - { - "id": "ac-5_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ac-5_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Separates {{ insert: param, ac-5_prm_1 }};" - }, - { - "id": "ac-5_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Documents separation of duties of individuals; and" - }, - { - "id": "ac-5_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Defines information system access authorizations to support separation of duties." - } - ] - }, - { - "id": "ac-5_gdn", - "name": "guidance", - "prose": "Separation of duties addresses the potential for abuse of authorized privileges and helps to reduce the risk of malevolent activity without collusion. Separation of duties includes, for example: (i) dividing mission functions and information system support functions among different individuals and/or roles; (ii) conducting information system support functions with different individuals (e.g., system management, programming, configuration management, quality assurance and testing, and network security); and (iii) ensuring security personnel administering access control functions do not also administer audit functions.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pe-4", - "rel": "related" - }, - { - "href": "#ps-2", - "rel": "related" - } - ] - }, - { - "id": "ac-5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-5.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-5(a)" - } - ], - "parts": [ - { - "id": "ac-5.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-5(a)[1]" - } - ], - "prose": "defines duties of individuals to be separated;" - }, - { - "id": "ac-5.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-5(a)[2]" - } - ], - "prose": "separates organization-defined duties of individuals;" - } - ] - }, - { - "id": "ac-5.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-5(b)" - } - ], - "prose": "documents separation of duties; and" - }, - { - "id": "ac-5.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-5(c)" - } - ], - "prose": "defines information system access authorizations to support separation of duties." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing divisions of responsibility and separation of duties\n\ninformation system configuration settings and associated documentation\n\nlist of divisions of responsibility and separation of duties\n\ninformation system access authorizations\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for defining appropriate divisions of responsibility and separation of duties\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing separation of duties policy" - } - ] - } - ] - }, - { - "id": "ac-6", - "class": "SP800-53", - "title": "Least Privilege", - "props": [ - { - "name": "label", - "value": "AC-6" - }, - { - "name": "sort-id", - "value": "ac-06" - } - ], - "parts": [ - { - "id": "ac-6_smt", - "name": "statement", - "prose": "The organization employs the principle of least privilege, allowing only authorized accesses for users (or processes acting on behalf of users) which are necessary to accomplish assigned tasks in accordance with organizational missions and business functions." - }, - { - "id": "ac-6_gdn", - "name": "guidance", - "prose": "Organizations employ least privilege for specific duties and information systems. The principle of least privilege is also applied to information system processes, ensuring that the processes operate at privilege levels no higher than necessary to accomplish required organizational missions/business functions. Organizations consider the creation of additional processes, roles, and information system accounts as necessary, to achieve least privilege. Organizations also apply least privilege to the development, implementation, and operation of organizational information systems.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-5", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - } - ] - }, - { - "id": "ac-6_obj", - "name": "objective", - "prose": "Determine if the organization employs the principle of least privilege, allowing only authorized access for users (and processes acting on behalf of users) which are necessary to accomplish assigned tasks in accordance with organizational missions and business functions." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\nlist of assigned access authorizations (user privileges)\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for defining least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing least privilege functions" - } - ] - } - ], - "controls": [ - { - "id": "ac-6.1", - "class": "SP800-53-enhancement", - "title": "Authorize Access to Security Functions", - "params": [ - { - "id": "ac-6.1_prm_1", - "label": "organization-defined security functions (deployed in hardware, software, and firmware) and security-relevant information" - } - ], - "props": [ - { - "name": "label", - "value": "AC-6(1)" - }, - { - "name": "sort-id", - "value": "ac-06.01" - } - ], - "parts": [ - { - "id": "ac-6.1_smt", - "name": "statement", - "prose": "The organization explicitly authorizes access to {{ insert: param, ac-6.1_prm_1 }}." - }, - { - "id": "ac-6.1_gdn", - "name": "guidance", - "prose": "Security functions include, for example, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. Security-relevant information includes, for example, filtering rules for routers/firewalls, cryptographic key management information, configuration parameters for security services, and access control lists. Explicitly authorized personnel include, for example, security administrators, system and network administrators, system security officers, system maintenance personnel, system programmers, and other privileged users.", - "links": [ - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - } - ] - }, - { - "id": "ac-6.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-6.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(1)[1]" - } - ], - "prose": "defines security-relevant information for which access must be explicitly authorized;" - }, - { - "id": "ac-6.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(1)[2]" - } - ], - "prose": "defines security functions deployed in:", - "parts": [ - { - "id": "ac-6.1_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(1)[2][a]" - } - ], - "prose": "hardware;" - }, - { - "id": "ac-6.1_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(1)[2][b]" - } - ], - "prose": "software;" - }, - { - "id": "ac-6.1_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(1)[2][c]" - } - ], - "prose": "firmware;" - } - ] - }, - { - "id": "ac-6.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(1)[3]" - } - ], - "prose": "explicitly authorizes access to:", - "parts": [ - { - "id": "ac-6.1_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(1)[3][a]" - } - ], - "prose": "organization-defined security functions; and" - }, - { - "id": "ac-6.1_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(1)[3][b]" - } - ], - "prose": "security-relevant information." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\nlist of security functions (deployed in hardware, software, and firmware) and security-relevant information for which access must be explicitly authorized\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for defining least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing least privilege functions" - } - ] - } - ] - }, - { - "id": "ac-6.2", - "class": "SP800-53-enhancement", - "title": "Non-privileged Access for Nonsecurity Functions", - "params": [ - { - "id": "ac-6.2_prm_1", - "label": "organization-defined security functions or security-relevant information" - } - ], - "props": [ - { - "name": "label", - "value": "AC-6(2)" - }, - { - "name": "sort-id", - "value": "ac-06.02" - } - ], - "parts": [ - { - "id": "ac-6.2_smt", - "name": "statement", - "prose": "The organization requires that users of information system accounts, or roles, with access to {{ insert: param, ac-6.2_prm_1 }}, use non-privileged accounts or roles, when accessing nonsecurity functions." - }, - { - "id": "ac-6.2_gdn", - "name": "guidance", - "prose": "This control enhancement limits exposure when operating from within privileged accounts or roles. The inclusion of roles addresses situations where organizations implement access control policies such as role-based access control and where a change of role provides the same degree of assurance in the change of access authorizations for both the user and all processes acting on behalf of the user as would be provided by a change between a privileged and non-privileged account.", - "links": [ - { - "href": "#pl-4", - "rel": "related" - } - ] - }, - { - "id": "ac-6.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-6.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(2)[1]" - } - ], - "prose": "defines security functions or security-relevant information to which users of information system accounts, or roles, have access; and" - }, - { - "id": "ac-6.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(2)[2]" - } - ], - "prose": "requires that users of information system accounts, or roles, with access to organization-defined security functions or security-relevant information, use non-privileged accounts, or roles, when accessing nonsecurity functions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\nlist of system-generated security functions or security-relevant information assigned to information system accounts or roles\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for defining least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing least privilege functions" - } - ] - } - ] - }, - { - "id": "ac-6.3", - "class": "SP800-53-enhancement", - "title": "Network Access to Privileged Commands", - "params": [ - { - "id": "ac-6.3_prm_1", - "label": "organization-defined privileged commands" - }, - { - "id": "ac-6.3_prm_2", - "label": "organization-defined compelling operational needs" - } - ], - "props": [ - { - "name": "label", - "value": "AC-6(3)" - }, - { - "name": "sort-id", - "value": "ac-06.03" - } - ], - "parts": [ - { - "id": "ac-6.3_smt", - "name": "statement", - "prose": "The organization authorizes network access to {{ insert: param, ac-6.3_prm_1 }} only for {{ insert: param, ac-6.3_prm_2 }} and documents the rationale for such access in the security plan for the information system." - }, - { - "id": "ac-6.3_gdn", - "name": "guidance", - "prose": "Network access is any access across a network connection in lieu of local access (i.e., user being physically present at the device).", - "links": [ - { - "href": "#ac-17", - "rel": "related" - } - ] - }, - { - "id": "ac-6.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-6.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(3)[1]" - } - ], - "prose": "defines privileged commands to which network access is to be authorized only for compelling operational needs;" - }, - { - "id": "ac-6.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(3)[2]" - } - ], - "prose": "defines compelling operational needs for which network access to organization-defined privileged commands are to be solely authorized;" - }, - { - "id": "ac-6.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(3)[3]" - } - ], - "prose": "authorizes network access to organization-defined privileged commands only for organization-defined compelling operational needs; and" - }, - { - "id": "ac-6.3_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(3)[4]" - } - ], - "prose": "documents the rationale for authorized network access to organization-defined privileged commands in the security plan for the information system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\nsecurity plan\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of operational needs for authorizing network access to privileged commands\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for defining least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing least privilege functions" - } - ] - } - ] - }, - { - "id": "ac-6.4", - "class": "SP800-53-enhancement", - "title": "Separate Processing Domains", - "props": [ - { - "name": "label", - "value": "AC-6(4)" - }, - { - "name": "sort-id", - "value": "ac-06.04" - } - ], - "parts": [ - { - "id": "ac-6.4_smt", - "name": "statement", - "prose": "The information system provides separate processing domains to enable finer-grained allocation of user privileges." - }, - { - "id": "ac-6.4_gdn", - "name": "guidance", - "prose": "Providing separate processing domains for finer-grained allocation of user privileges includes, for example: (i) using virtualization techniques to allow additional privileges within a virtual machine while restricting privileges to other virtual machines or to the underlying actual machine; (ii) employing hardware and/or software domain separation mechanisms; and (iii) implementing separate physical domains.", - "links": [ - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - }, - { - "href": "#sc-30", - "rel": "related" - }, - { - "href": "#sc-32", - "rel": "related" - } - ] - }, - { - "id": "ac-6.4_obj", - "name": "objective", - "prose": "Determine if the information system provides separate processing domains to enable finer-grained allocation of user privileges." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for defining least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing least privilege functions" - } - ] - } - ] - }, - { - "id": "ac-6.5", - "class": "SP800-53-enhancement", - "title": "Privileged Accounts", - "params": [ - { - "id": "ac-6.5_prm_1", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "AC-6(5)" - }, - { - "name": "sort-id", - "value": "ac-06.05" - } - ], - "parts": [ - { - "id": "ac-6.5_smt", - "name": "statement", - "prose": "The organization restricts privileged accounts on the information system to {{ insert: param, ac-6.5_prm_1 }}." - }, - { - "id": "ac-6.5_gdn", - "name": "guidance", - "prose": "Privileged accounts, including super user accounts, are typically described as system administrator for various types of commercial off-the-shelf operating systems. Restricting privileged accounts to specific personnel or roles prevents day-to-day users from having access to privileged information/functions. Organizations may differentiate in the application of this control enhancement between allowed privileges for local accounts and for domain accounts provided organizations retain the ability to control information system configurations for key security parameters and as otherwise necessary to sufficiently mitigate risk.", - "links": [ - { - "href": "#cm-6", - "rel": "related" - } - ] - }, - { - "id": "ac-6.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-6.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(5)[1]" - } - ], - "prose": "defines personnel or roles for which privileged accounts on the information system are to be restricted; and" - }, - { - "id": "ac-6.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(5)[2]" - } - ], - "prose": "restricts privileged accounts on the information system to organization-defined personnel or roles." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\nlist of system-generated privileged accounts\n\nlist of system administration personnel\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for defining least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing least privilege functions" - } - ] - } - ] - }, - { - "id": "ac-6.6", - "class": "SP800-53-enhancement", - "title": "Privileged Access by Non-organizational Users", - "props": [ - { - "name": "label", - "value": "AC-6(6)" - }, - { - "name": "sort-id", - "value": "ac-06.06" - } - ], - "parts": [ - { - "id": "ac-6.6_smt", - "name": "statement", - "prose": "The organization prohibits privileged access to the information system by non-organizational users." - }, - { - "id": "ac-6.6_gdn", - "name": "guidance", - "links": [ - { - "href": "#ia-8", - "rel": "related" - } - ] - }, - { - "id": "ac-6.6_obj", - "name": "objective", - "prose": "Determine if the organization prohibits privileged access to the information system by non-organizational users." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\nlist of system-generated privileged accounts\n\nlist of non-organizational users\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for defining least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms prohibiting privileged access to the information system" - } - ] - } - ] - }, - { - "id": "ac-6.7", - "class": "SP800-53-enhancement", - "title": "Review of User Privileges", - "params": [ - { - "id": "ac-6.7_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "ac-6.7_prm_2", - "label": "organization-defined roles or classes of users" - } - ], - "props": [ - { - "name": "label", - "value": "AC-6(7)" - }, - { - "name": "sort-id", - "value": "ac-06.07" - } - ], - "parts": [ - { - "id": "ac-6.7_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ac-6.7_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Reviews {{ insert: param, ac-6.7_prm_1 }} the privileges assigned to {{ insert: param, ac-6.7_prm_2 }} to validate the need for such privileges; and" - }, - { - "id": "ac-6.7_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Reassigns or removes privileges, if necessary, to correctly reflect organizational mission/business needs." - } - ] - }, - { - "id": "ac-6.7_gdn", - "name": "guidance", - "prose": "The need for certain assigned user privileges may change over time reflecting changes in organizational missions/business function, environments of operation, technologies, or threat. Periodic review of assigned user privileges is necessary to determine if the rationale for assigning such privileges remains valid. If the need cannot be revalidated, organizations take appropriate corrective actions.", - "links": [ - { - "href": "#ca-7", - "rel": "related" - } - ] - }, - { - "id": "ac-6.7_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-6.7.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(7)(a)" - } - ], - "parts": [ - { - "id": "ac-6.7.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(7)(a)[1]" - } - ], - "prose": "defines roles or classes of users to which privileges are assigned;" - }, - { - "id": "ac-6.7.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(7)(a)[2]" - } - ], - "prose": "defines the frequency to review the privileges assigned to organization-defined roles or classes of users to validate the need for such privileges;" - }, - { - "id": "ac-6.7.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(7)(a)[3]" - } - ], - "prose": "reviews the privileges assigned to organization-defined roles or classes of users with the organization-defined frequency to validate the need for such privileges; and" - } - ], - "links": [ - { - "href": "#ac-6.7_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ac-6.7.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(7)(b)" - } - ], - "prose": "reassigns or removes privileges, if necessary, to correctly reflect organizational missions/business needs.", - "links": [ - { - "href": "#ac-6.7_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\nlist of system-generated roles or classes of users and assigned privileges\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nvalidation reviews of privileges assigned to roles or classes or users\n\nrecords of privilege removals or reassignments for roles or classes of users\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for reviewing least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing review of user privileges" - } - ] - } - ] - }, - { - "id": "ac-6.8", - "class": "SP800-53-enhancement", - "title": "Privilege Levels for Code Execution", - "params": [ - { - "id": "ac-6.8_prm_1", - "label": "organization-defined software" - } - ], - "props": [ - { - "name": "label", - "value": "AC-6(8)" - }, - { - "name": "sort-id", - "value": "ac-06.08" - } - ], - "parts": [ - { - "id": "ac-6.8_smt", - "name": "statement", - "prose": "The information system prevents {{ insert: param, ac-6.8_prm_1 }} from executing at higher privilege levels than users executing the software." - }, - { - "id": "ac-6.8_gdn", - "name": "guidance", - "prose": "In certain situations, software applications/programs need to execute with elevated privileges to perform required functions. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking such applications/programs, those users are indirectly provided with greater privileges than assigned by organizations." - }, - { - "id": "ac-6.8_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-6.8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(8)[1]" - } - ], - "prose": "the organization defines software that should not execute at higher privilege levels than users executing the software; and" - }, - { - "id": "ac-6.8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(8)[2]" - } - ], - "prose": "the information system prevents organization-defined software from executing at higher privilege levels than users executing the software." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\nlist of software that should not execute at higher privilege levels than users executing software\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for defining least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing least privilege functions for software execution" - } - ] - } - ] - }, - { - "id": "ac-6.9", - "class": "SP800-53-enhancement", - "title": "Auditing Use of Privileged Functions", - "props": [ - { - "name": "label", - "value": "AC-6(9)" - }, - { - "name": "sort-id", - "value": "ac-06.09" - } - ], - "parts": [ - { - "id": "ac-6.9_smt", - "name": "statement", - "prose": "The information system audits the execution of privileged functions." - }, - { - "id": "ac-6.9_gdn", - "name": "guidance", - "prose": "Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse, and in doing so, help mitigate the risk from insider threats and the advanced persistent threat (APT).", - "links": [ - { - "href": "#au-2", - "rel": "related" - } - ] - }, - { - "id": "ac-6.9_obj", - "name": "objective", - "prose": "Determine if the information system audits the execution of privileged functions." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of privileged functions to be audited\n\nlist of audited events\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for reviewing least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms auditing the execution of least privilege functions" - } - ] - } - ] - }, - { - "id": "ac-6.10", - "class": "SP800-53-enhancement", - "title": "Prohibit Non-privileged Users from Executing Privileged Functions", - "props": [ - { - "name": "label", - "value": "AC-6(10)" - }, - { - "name": "sort-id", - "value": "ac-06.10" - } - ], - "parts": [ - { - "id": "ac-6.10_smt", - "name": "statement", - "prose": "The information system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures." - }, - { - "id": "ac-6.10_gdn", - "name": "guidance", - "prose": "Privileged functions include, for example, establishing information system accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users." - }, - { - "id": "ac-6.10_obj", - "name": "objective", - "prose": "Determine if the information system prevents non-privileged users from executing privileged functions to include:", - "parts": [ - { - "id": "ac-6.10_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(10)[1]" - } - ], - "prose": "disabling implemented security safeguards/countermeasures;" - }, - { - "id": "ac-6.10_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(10)[2]" - } - ], - "prose": "circumventing security safeguards/countermeasures; or" - }, - { - "id": "ac-6.10_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-6(10)[3]" - } - ], - "prose": "altering implemented security safeguards/countermeasures." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of privileged functions and associated user account assignments\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for defining least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing least privilege functions for non-privileged users" - } - ] - } - ] - } - ] - }, - { - "id": "ac-7", - "class": "SP800-53", - "title": "Unsuccessful Logon Attempts", - "params": [ - { - "id": "ac-7_prm_1", - "label": "organization-defined number" - }, - { - "id": "ac-7_prm_2", - "label": "organization-defined time period" - }, - { - "id": "ac-7_prm_3", - "select": { - "choice": [ - "locks the account/node for an {{ insert: param, ac-7_prm_4 }} ", - "locks the account/node until released by an administrator", - "delays next logon prompt according to {{ insert: param, ac-7_prm_5 }} " - ] - } - }, - { - "id": "ac-7_prm_4", - "depends-on": "ac-7_prm_3", - "label": "organization-defined time period" - }, - { - "id": "ac-7_prm_5", - "depends-on": "ac-7_prm_3", - "label": "organization-defined delay algorithm" - } - ], - "props": [ - { - "name": "label", - "value": "AC-7" - }, - { - "name": "sort-id", - "value": "ac-07" - } - ], - "parts": [ - { - "id": "ac-7_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "ac-7_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Enforces a limit of {{ insert: param, ac-7_prm_1 }} consecutive invalid logon attempts by a user during a {{ insert: param, ac-7_prm_2 }}; and" - }, - { - "id": "ac-7_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Automatically {{ insert: param, ac-7_prm_3 }} when the maximum number of unsuccessful attempts is exceeded." - } - ] - }, - { - "id": "ac-7_gdn", - "name": "guidance", - "prose": "This control applies regardless of whether the logon occurs via a local or network connection. Due to the potential for denial of service, automatic lockouts initiated by information systems are usually temporary and automatically release after a predetermined time period established by organizations. If a delay algorithm is selected, organizations may choose to employ different algorithms for different information system components based on the capabilities of those components. Responses to unsuccessful logon attempts may be implemented at both the operating system and the application levels.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-9", - "rel": "related" - }, - { - "href": "#ac-14", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - } - ] - }, - { - "id": "ac-7_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-7.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-7(a)" - } - ], - "parts": [ - { - "id": "ac-7.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-7(a)[1]" - } - ], - "prose": "the organization defines the number of consecutive invalid logon attempts allowed to the information system by a user during an organization-defined time period;" - }, - { - "id": "ac-7.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-7(a)[2]" - } - ], - "prose": "the organization defines the time period allowed by a user of the information system for an organization-defined number of consecutive invalid logon attempts;" - }, - { - "id": "ac-7.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-7(a)[3]" - } - ], - "prose": "the information system enforces a limit of organization-defined number of consecutive invalid logon attempts by a user during an organization-defined time period;" - } - ] - }, - { - "id": "ac-7.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-7(b)" - } - ], - "parts": [ - { - "id": "ac-7.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-7(b)[1]" - } - ], - "prose": "the organization defines account/node lockout time period or logon delay algorithm to be automatically enforced by the information system when the maximum number of unsuccessful logon attempts is exceeded;" - }, - { - "id": "ac-7.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-7(b)[2]" - } - ], - "prose": "the information system, when the maximum number of unsuccessful logon attempts is exceeded, automatically:", - "parts": [ - { - "id": "ac-7.b_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-7(b)[2][a]" - } - ], - "prose": "locks the account/node for the organization-defined time period;" - }, - { - "id": "ac-7.b_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-7(b)[2][b]" - } - ], - "prose": "locks the account/node until released by an administrator; or" - }, - { - "id": "ac-7.b_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-7(b)[2][c]" - } - ], - "prose": "delays next logon prompt according to the organization-defined delay algorithm." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing unsuccessful logon attempts\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem developers\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing access control policy for unsuccessful logon attempts" - } - ] - } - ], - "controls": [ - { - "id": "ac-7.1", - "class": "SP800-53-enhancement", - "title": "Automatic Account Lock", - "props": [ - { - "name": "label", - "value": "AC-7(1)" - }, - { - "name": "sort-id", - "value": "ac-07.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#ac-7", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ac-7.2", - "class": "SP800-53-enhancement", - "title": "Purge / Wipe Mobile Device", - "params": [ - { - "id": "ac-7.2_prm_1", - "label": "organization-defined mobile devices" - }, - { - "id": "ac-7.2_prm_2", - "label": "organization-defined purging/wiping requirements/techniques" - }, - { - "id": "ac-7.2_prm_3", - "label": "organization-defined number" - } - ], - "props": [ - { - "name": "label", - "value": "AC-7(2)" - }, - { - "name": "sort-id", - "value": "ac-07.02" - } - ], - "parts": [ - { - "id": "ac-7.2_smt", - "name": "statement", - "prose": "The information system purges/wipes information from {{ insert: param, ac-7.2_prm_1 }} based on {{ insert: param, ac-7.2_prm_2 }} after {{ insert: param, ac-7.2_prm_3 }} consecutive, unsuccessful device logon attempts." - }, - { - "id": "ac-7.2_gdn", - "name": "guidance", - "prose": "This control enhancement applies only to mobile devices for which a logon occurs (e.g., personal digital assistants, smart phones, tablets). The logon is to the mobile device, not to any one account on the device. Therefore, successful logons to any accounts on mobile devices reset the unsuccessful logon count to zero. Organizations define information to be purged/wiped carefully in order to avoid over purging/wiping which may result in devices becoming unusable. Purging/wiping may be unnecessary if the information on the device is protected with sufficiently strong encryption mechanisms.", - "links": [ - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - }, - { - "href": "#mp-6", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "ac-7.2_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-7.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-7(2)[1]" - } - ], - "prose": "the organization defines mobile devices to be purged/wiped after organization-defined number of consecutive, unsuccessful device logon attempts;" - }, - { - "id": "ac-7.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-7(2)[2]" - } - ], - "prose": "the organization defines purging/wiping requirements/techniques to be used when organization-defined mobile devices are purged/wiped after organization-defined number of consecutive, unsuccessful device logon attempts;" - }, - { - "id": "ac-7.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-7(2)[3]" - } - ], - "prose": "the organization defines the number of consecutive, unsuccessful logon attempts allowed for accessing mobile devices before the information system purges/wipes information from such devices; and" - }, - { - "id": "ac-7.2_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-7(2)[4]" - } - ], - "prose": "the information system purges/wipes information from organization-defined mobile devices based on organization-defined purging/wiping requirements/techniques after organization-defined number of consecutive, unsuccessful logon attempts." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing unsuccessful login attempts on mobile devices\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of mobile devices to be purged/wiped after organization-defined consecutive, unsuccessful device logon attempts\n\nlist of purging/wiping requirements or techniques for mobile devices\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing access control policy for unsuccessful device logon attempts" - } - ] - } - ] - } - ] - }, - { - "id": "ac-8", - "class": "SP800-53", - "title": "System Use Notification", - "params": [ - { - "id": "ac-8_prm_1", - "label": "organization-defined system use notification message or banner" - }, - { - "id": "ac-8_prm_2", - "label": "organization-defined conditions" - } - ], - "props": [ - { - "name": "label", - "value": "AC-8" - }, - { - "name": "sort-id", - "value": "ac-08" - } - ], - "parts": [ - { - "id": "ac-8_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "ac-8_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Displays to users {{ insert: param, ac-8_prm_1 }} before granting access to the system that provides privacy and security notices consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance and states that:", - "parts": [ - { - "id": "ac-8_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Users are accessing a U.S. Government information system;" - }, - { - "id": "ac-8_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Information system usage may be monitored, recorded, and subject to audit;" - }, - { - "id": "ac-8_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Unauthorized use of the information system is prohibited and subject to criminal and civil penalties; and" - }, - { - "id": "ac-8_smt.a.4", - "name": "item", - "props": [ - { - "name": "label", - "value": "4." - } - ], - "prose": "Use of the information system indicates consent to monitoring and recording;" - } - ] - }, - { - "id": "ac-8_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Retains the notification message or banner on the screen until users acknowledge the usage conditions and take explicit actions to log on to or further access the information system; and" - }, - { - "id": "ac-8_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "For publicly accessible systems:", - "parts": [ - { - "id": "ac-8_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Displays system use information {{ insert: param, ac-8_prm_2 }}, before granting further access;" - }, - { - "id": "ac-8_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Displays references, if any, to monitoring, recording, or auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities; and" - }, - { - "id": "ac-8_smt.c.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Includes a description of the authorized uses of the system." - } - ] - } - ] - }, - { - "id": "ac-8_gdn", - "name": "guidance", - "prose": "System use notifications can be implemented using messages or warning banners displayed before individuals log in to information systems. System use notifications are used only for access via logon interfaces with human users and are not required when such human interfaces do not exist. Organizations consider system use notification messages/banners displayed in multiple languages based on specific organizational needs and the demographics of information system users. Organizations also consult with the Office of the General Counsel for legal review and approval of warning banner content." - }, - { - "id": "ac-8_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-8.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-8(a)" - } - ], - "parts": [ - { - "id": "ac-8.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-8(a)[1]" - } - ], - "prose": "the organization defines a system use notification message or banner to be displayed by the information system to users before granting access to the system;" - }, - { - "id": "ac-8.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-8(a)[2]" - } - ], - "prose": "the information system displays to users the organization-defined system use notification message or banner before granting access to the information system that provides privacy and security notices consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance, and states that:", - "parts": [ - { - "id": "ac-8.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-8(a)[2](1)" - } - ], - "prose": "users are accessing a U.S. Government information system;" - }, - { - "id": "ac-8.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-8(a)[2](2)" - } - ], - "prose": "information system usage may be monitored, recorded, and subject to audit;" - }, - { - "id": "ac-8.a.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-8(a)[2](3)" - } - ], - "prose": "unauthorized use of the information system is prohibited and subject to criminal and civil penalties;" - }, - { - "id": "ac-8.a.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-8(a)[2](4)" - } - ], - "prose": "use of the information system indicates consent to monitoring and recording;" - } - ] - } - ] - }, - { - "id": "ac-8.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-8(b)" - } - ], - "prose": "the information system retains the notification message or banner on the screen until users acknowledge the usage conditions and take explicit actions to log on to or further access the information system;" - }, - { - "id": "ac-8.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-8(c)" - } - ], - "prose": "for publicly accessible systems:", - "parts": [ - { - "id": "ac-8.c.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-8(c)(1)" - } - ], - "parts": [ - { - "id": "ac-8.c.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-8(c)(1)[1]" - } - ], - "prose": "the organization defines conditions for system use to be displayed by the information system before granting further access;" - }, - { - "id": "ac-8.c.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-8(c)(1)[2]" - } - ], - "prose": "the information system displays organization-defined conditions before granting further access;" - } - ] - }, - { - "id": "ac-8.c.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-8(c)(2)" - } - ], - "prose": "the information system displays references, if any, to monitoring, recording, or auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities; and" - }, - { - "id": "ac-8.c.3_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-8(c)(3)" - } - ], - "prose": "the information system includes a description of the authorized uses of the system." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprivacy and security policies, procedures addressing system use notification\n\ndocumented approval of information system use notification messages or banners\n\ninformation system audit records\n\nuser acknowledgements of notification message or banner\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system use notification messages\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for providing legal advice\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing system use notification" - } - ] - } - ] - }, - { - "id": "ac-9", - "class": "SP800-53", - "title": "Previous Logon (access) Notification", - "props": [ - { - "name": "label", - "value": "AC-9" - }, - { - "name": "sort-id", - "value": "ac-09" - } - ], - "parts": [ - { - "id": "ac-9_smt", - "name": "statement", - "prose": "The information system notifies the user, upon successful logon (access) to the system, of the date and time of the last logon (access)." - }, - { - "id": "ac-9_gdn", - "name": "guidance", - "prose": "This control is applicable to logons to information systems via human user interfaces and logons to systems that occur in other types of architectures (e.g., service-oriented architectures).", - "links": [ - { - "href": "#ac-7", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - } - ] - }, - { - "id": "ac-9_obj", - "name": "objective", - "prose": "Determine if the information system notifies the user, upon successful logon (access) to the system, of the date and time of the last logon (access)." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing previous logon notification\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system notification messages\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing access control policy for previous logon notification" - } - ] - } - ], - "controls": [ - { - "id": "ac-9.1", - "class": "SP800-53-enhancement", - "title": "Unsuccessful Logons", - "props": [ - { - "name": "label", - "value": "AC-9(1)" - }, - { - "name": "sort-id", - "value": "ac-09.01" - } - ], - "parts": [ - { - "id": "ac-9.1_smt", - "name": "statement", - "prose": "The information system notifies the user, upon successful logon/access, of the number of unsuccessful logon/access attempts since the last successful logon/access." - }, - { - "id": "ac-9.1_obj", - "name": "objective", - "prose": "Determine if the information system notifies the user, upon successful logon/access, of the number of unsuccessful logon/access attempts since the last successful logon/access." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing previous logon notification\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing access control policy for previous logon notification" - } - ] - } - ] - }, - { - "id": "ac-9.2", - "class": "SP800-53-enhancement", - "title": "Successful / Unsuccessful Logons", - "params": [ - { - "id": "ac-9.2_prm_1", - "select": { - "choice": [ - "successful logons/accesses", - "unsuccessful logon/access attempts", - "both" - ] - } - }, - { - "id": "ac-9.2_prm_2", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "AC-9(2)" - }, - { - "name": "sort-id", - "value": "ac-09.02" - } - ], - "parts": [ - { - "id": "ac-9.2_smt", - "name": "statement", - "prose": "The information system notifies the user of the number of {{ insert: param, ac-9.2_prm_1 }} during {{ insert: param, ac-9.2_prm_2 }}." - }, - { - "id": "ac-9.2_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-9.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-9(2)[1]" - } - ], - "prose": "the organization defines the time period within which the information system must notify the user of the number of:", - "parts": [ - { - "id": "ac-9.2_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-9(2)[1][a]" - } - ], - "prose": "successful logons/accesses; and/or" - }, - { - "id": "ac-9.2_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-9(2)[1][b]" - } - ], - "prose": "unsuccessful logon/access attempts;" - } - ] - }, - { - "id": "ac-9.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-9(2)[2]" - } - ], - "prose": "the information system, during the organization-defined time period, notifies the user of the number of:", - "parts": [ - { - "id": "ac-9.2_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-9(2)[2][a]" - } - ], - "prose": "successful logons/accesses; and/or" - }, - { - "id": "ac-9.2_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-9(2)[2][b]" - } - ], - "prose": "unsuccessful logon/access attempts." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing previous logon notification\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing access control policy for previous logon notification" - } - ] - } - ] - }, - { - "id": "ac-9.3", - "class": "SP800-53-enhancement", - "title": "Notification of Account Changes", - "params": [ - { - "id": "ac-9.3_prm_1", - "label": "organization-defined security-related characteristics/parameters of the user’s account" - }, - { - "id": "ac-9.3_prm_2", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "AC-9(3)" - }, - { - "name": "sort-id", - "value": "ac-09.03" - } - ], - "parts": [ - { - "id": "ac-9.3_smt", - "name": "statement", - "prose": "The information system notifies the user of changes to {{ insert: param, ac-9.3_prm_1 }} during {{ insert: param, ac-9.3_prm_2 }}." - }, - { - "id": "ac-9.3_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-9.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-9(3)[1]" - } - ], - "prose": "the organization defines security-related characteristics/parameters of a user’s account;" - }, - { - "id": "ac-9.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-9(3)[2]" - } - ], - "prose": "the organization defines the time period within which changes to organization-defined security-related characteristics/parameters of a user’s account must occur; and" - }, - { - "id": "ac-9.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-9(3)[3]" - } - ], - "prose": "the information system notifies the user of changes to organization-defined security-related characteristics/parameters of the user’s account during the organization-defined time period." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing previous logon notification\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing access control policy for previous logon notification" - } - ] - } - ] - }, - { - "id": "ac-9.4", - "class": "SP800-53-enhancement", - "title": "Additional Logon Information", - "params": [ - { - "id": "ac-9.4_prm_1", - "label": "organization-defined information to be included in addition to the date and time of the last logon (access)" - } - ], - "props": [ - { - "name": "label", - "value": "AC-9(4)" - }, - { - "name": "sort-id", - "value": "ac-09.04" - } - ], - "parts": [ - { - "id": "ac-9.4_smt", - "name": "statement", - "prose": "The information system notifies the user, upon successful logon (access), of the following additional information: {{ insert: param, ac-9.4_prm_1 }}." - }, - { - "id": "ac-9.4_gdn", - "name": "guidance", - "prose": "This control enhancement permits organizations to specify additional information to be provided to users upon logon including, for example, the location of last logon. User location is defined as that information which can be determined by information systems, for example, IP addresses from which network logons occurred, device identifiers, or notifications of local logons." - }, - { - "id": "ac-9.4_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-9.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-9(4)[1]" - } - ], - "prose": "the organization defines information to be included in addition to the date and time of the last logon (access); and" - }, - { - "id": "ac-9.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-9(4)[2]" - } - ], - "prose": "the information system notifies the user, upon successful logon (access), of the organization-defined information to be included in addition to the date and time of the last logon (access)." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing previous logon notification\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing access control policy for previous logon notification" - } - ] - } - ] - } - ] - }, - { - "id": "ac-10", - "class": "SP800-53", - "title": "Concurrent Session Control", - "params": [ - { - "id": "ac-10_prm_1", - "label": "organization-defined account and/or account type" - }, - { - "id": "ac-10_prm_2", - "label": "organization-defined number" - } - ], - "props": [ - { - "name": "label", - "value": "AC-10" - }, - { - "name": "sort-id", - "value": "ac-10" - } - ], - "parts": [ - { - "id": "ac-10_smt", - "name": "statement", - "prose": "The information system limits the number of concurrent sessions for each {{ insert: param, ac-10_prm_1 }} to {{ insert: param, ac-10_prm_2 }}." - }, - { - "id": "ac-10_gdn", - "name": "guidance", - "prose": "Organizations may define the maximum number of concurrent sessions for information system accounts globally, by account type (e.g., privileged user, non-privileged user, domain, specific application), by account, or a combination. For example, organizations may limit the number of concurrent sessions for system administrators or individuals working in particularly sensitive domains or mission-critical applications. This control addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts." - }, - { - "id": "ac-10_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-10_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-10[1]" - } - ], - "prose": "the organization defines account and/or account types for the information system;" - }, - { - "id": "ac-10_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-10[2]" - } - ], - "prose": "the organization defines the number of concurrent sessions to be allowed for each organization-defined account and/or account type; and" - }, - { - "id": "ac-10_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-10[3]" - } - ], - "prose": "the information system limits the number of concurrent sessions for each organization-defined account and/or account type to the organization-defined number of concurrent sessions allowed." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing concurrent session control\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing access control policy for concurrent session control" - } - ] - } - ] - }, - { - "id": "ac-11", - "class": "SP800-53", - "title": "Session Lock", - "params": [ - { - "id": "ac-11_prm_1", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "AC-11" - }, - { - "name": "sort-id", - "value": "ac-11" - } - ], - "links": [ - { - "href": "#4da24a96-6cf8-435d-9d1f-c73247cad109", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ac-11_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "ac-11_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Prevents further access to the system by initiating a session lock after {{ insert: param, ac-11_prm_1 }} of inactivity or upon receiving a request from a user; and" - }, - { - "id": "ac-11_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Retains the session lock until the user reestablishes access using established identification and authentication procedures." - } - ] - }, - { - "id": "ac-11_gdn", - "name": "guidance", - "prose": "Session locks are temporary actions taken when users stop work and move away from the immediate vicinity of information systems but do not want to log out because of the temporary nature of their absences. Session locks are implemented where session activities can be determined. This is typically at the operating system level, but can also be at the application level. Session locks are not an acceptable substitute for logging out of information systems, for example, if organizations require users to log out at the end of workdays.", - "links": [ - { - "href": "#ac-7", - "rel": "related" - } - ] - }, - { - "id": "ac-11_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-11.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-11(a)" - } - ], - "parts": [ - { - "id": "ac-11.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-11(a)[1]" - } - ], - "prose": "the organization defines the time period of user inactivity after which the information system initiates a session lock;" - }, - { - "id": "ac-11.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-11(a)[2]" - } - ], - "prose": "the information system prevents further access to the system by initiating a session lock after organization-defined time period of user inactivity or upon receiving a request from a user; and" - } - ] - }, - { - "id": "ac-11.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-11(b)" - } - ], - "prose": "the information system retains the session lock until the user reestablishes access using established identification and authentication procedures." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing session lock\n\nprocedures addressing identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing access control policy for session lock" - } - ] - } - ], - "controls": [ - { - "id": "ac-11.1", - "class": "SP800-53-enhancement", - "title": "Pattern-hiding Displays", - "props": [ - { - "name": "label", - "value": "AC-11(1)" - }, - { - "name": "sort-id", - "value": "ac-11.01" - } - ], - "parts": [ - { - "id": "ac-11.1_smt", - "name": "statement", - "prose": "The information system conceals, via the session lock, information previously visible on the display with a publicly viewable image." - }, - { - "id": "ac-11.1_gdn", - "name": "guidance", - "prose": "Publicly viewable images can include static or dynamic images, for example, patterns used with screen savers, photographic images, solid colors, clock, battery life indicator, or a blank screen, with the additional caveat that none of the images convey sensitive information." - }, - { - "id": "ac-11.1_obj", - "name": "objective", - "prose": "Determine if the information system conceals, via the session lock, information previously visible on the display with a publicly viewable image." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing session lock\n\ndisplay screen with session lock activated\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system session lock mechanisms" - } - ] - } - ] - } - ] - }, - { - "id": "ac-12", - "class": "SP800-53", - "title": "Session Termination", - "params": [ - { - "id": "ac-12_prm_1", - "label": "organization-defined conditions or trigger events requiring session disconnect" - } - ], - "props": [ - { - "name": "label", - "value": "AC-12" - }, - { - "name": "sort-id", - "value": "ac-12" - } - ], - "parts": [ - { - "id": "ac-12_smt", - "name": "statement", - "prose": "The information system automatically terminates a user session after {{ insert: param, ac-12_prm_1 }}." - }, - { - "id": "ac-12_gdn", - "name": "guidance", - "prose": "This control addresses the termination of user-initiated logical sessions in contrast to SC-10 which addresses the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. Session termination terminates all processes associated with a user’s logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated. Conditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, time-of-day restrictions on information system use.", - "links": [ - { - "href": "#sc-10", - "rel": "related" - }, - { - "href": "#sc-23", - "rel": "related" - } - ] - }, - { - "id": "ac-12_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-12_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-12[1]" - } - ], - "prose": "the organization defines conditions or trigger events requiring session disconnect; and" - }, - { - "id": "ac-12_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-12[2]" - } - ], - "prose": "the information system automatically terminates a user session after organization-defined conditions or trigger events requiring session disconnect occurs." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing session termination\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of conditions or trigger events requiring session disconnect\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing user session termination" - } - ] - } - ], - "controls": [ - { - "id": "ac-12.1", - "class": "SP800-53-enhancement", - "title": "User-initiated Logouts / Message Displays", - "params": [ - { - "id": "ac-12.1_prm_1", - "label": "organization-defined information resources" - } - ], - "props": [ - { - "name": "label", - "value": "AC-12(1)" - }, - { - "name": "sort-id", - "value": "ac-12.01" - } - ], - "parts": [ - { - "id": "ac-12.1_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "ac-12.1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Provides a logout capability for user-initiated communications sessions whenever authentication is used to gain access to {{ insert: param, ac-12.1_prm_1 }}; and" - }, - { - "id": "ac-12.1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Displays an explicit logout message to users indicating the reliable termination of authenticated communications sessions." - } - ] - }, - { - "id": "ac-12.1_gdn", - "name": "guidance", - "prose": "Information resources to which users gain access via authentication include, for example, local workstations, databases, and password-protected websites/web-based services. Logout messages for web page access, for example, can be displayed after authenticated sessions have been terminated. However, for some types of interactive sessions including, for example, file transfer protocol (FTP) sessions, information systems typically send logout messages as final messages prior to terminating sessions." - }, - { - "id": "ac-12.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-12.1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-12(1)(a)" - } - ], - "parts": [ - { - "id": "ac-12.1.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-12(1)(a)[1]" - } - ], - "prose": "the organization defines information resources for which user authentication is required to gain access to such resources;" - }, - { - "id": "ac-12.1.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-12(1)(a)[2]" - } - ], - "prose": "the information system provides a logout capability for user-initiated communications sessions whenever authentication is used to gain access to organization-defined information resources; and" - } - ], - "links": [ - { - "href": "#ac-12.1_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ac-12.1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-12(1)(b)" - } - ], - "prose": "the information system displays an explicit logout message to users indicating the reliable termination of authenticated communications sessions.", - "links": [ - { - "href": "#ac-12.1_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing session termination\n\nuser logout messages\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system session lock mechanisms" - } - ] - } - ] - } - ] - }, - { - "id": "ac-13", - "class": "SP800-53", - "title": "Supervision and Review - Access Control", - "props": [ - { - "name": "label", - "value": "AC-13" - }, - { - "name": "sort-id", - "value": "ac-13" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "incorporated-into" - }, - { - "href": "#au-6", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ac-14", - "class": "SP800-53", - "title": "Permitted Actions Without Identification or Authentication", - "params": [ - { - "id": "ac-14_prm_1", - "label": "organization-defined user actions" - } - ], - "props": [ - { - "name": "label", - "value": "AC-14" - }, - { - "name": "sort-id", - "value": "ac-14" - } - ], - "parts": [ - { - "id": "ac-14_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ac-14_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Identifies {{ insert: param, ac-14_prm_1 }} that can be performed on the information system without identification or authentication consistent with organizational missions/business functions; and" - }, - { - "id": "ac-14_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Documents and provides supporting rationale in the security plan for the information system, user actions not requiring identification or authentication." - } - ] - }, - { - "id": "ac-14_gdn", - "name": "guidance", - "prose": "This control addresses situations in which organizations determine that no identification or authentication is required in organizational information systems. Organizations may allow a limited number of user actions without identification or authentication including, for example, when individuals access public websites or other publicly accessible federal information systems, when individuals use mobile phones to receive calls, or when facsimiles are received. Organizations also identify actions that normally require identification or authentication but may under certain circumstances (e.g., emergencies), allow identification or authentication mechanisms to be bypassed. Such bypasses may occur, for example, via a software-readable physical switch that commands bypass of the logon functionality and is protected from accidental or unmonitored use. This control does not apply to situations where identification and authentication have already occurred and are not repeated, but rather to situations where identification and authentication have not yet occurred. Organizations may decide that there are no user actions that can be performed on organizational information systems without identification and authentication and thus, the values for assignment statements can be none.", - "links": [ - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - } - ] - }, - { - "id": "ac-14_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-14.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-14(a)" - } - ], - "parts": [ - { - "id": "ac-14.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-14(a)[1]" - } - ], - "prose": "defines user actions that can be performed on the information system without identification or authentication consistent with organizational missions/business functions;" - }, - { - "id": "ac-14.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-14(a)[2]" - } - ], - "prose": "identifies organization-defined user actions that can be performed on the information system without identification or authentication consistent with organizational missions/business functions; and" - } - ] - }, - { - "id": "ac-14.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-14(b)" - } - ], - "prose": "documents and provides supporting rationale in the security plan for the information system, user actions not requiring identification or authentication." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing permitted actions without identification or authentication\n\ninformation system configuration settings and associated documentation\n\nsecurity plan\n\nlist of user actions that can be performed without identification or authentication\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - } - ], - "controls": [ - { - "id": "ac-14.1", - "class": "SP800-53-enhancement", - "title": "Necessary Uses", - "props": [ - { - "name": "label", - "value": "AC-14(1)" - }, - { - "name": "sort-id", - "value": "ac-14.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#ac-14", - "rel": "incorporated-into" - } - ] - } - ] - }, - { - "id": "ac-15", - "class": "SP800-53", - "title": "Automated Marking", - "props": [ - { - "name": "label", - "value": "AC-15" - }, - { - "name": "sort-id", - "value": "ac-15" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#mp-3", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ac-16", - "class": "SP800-53", - "title": "Security Attributes", - "params": [ - { - "id": "ac-16_prm_1", - "label": "organization-defined types of security attributes" - }, - { - "id": "ac-16_prm_2", - "label": "organization-defined security attribute values" - }, - { - "id": "ac-16_prm_3", - "label": "organization-defined security attributes" - }, - { - "id": "ac-16_prm_4", - "label": "organization-defined information systems" - }, - { - "id": "ac-16_prm_5", - "label": "organization-defined values or ranges" - } - ], - "props": [ - { - "name": "label", - "value": "AC-16" - }, - { - "name": "sort-id", - "value": "ac-16" - } - ], - "parts": [ - { - "id": "ac-16_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ac-16_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Provides the means to associate {{ insert: param, ac-16_prm_1 }} having {{ insert: param, ac-16_prm_2 }} with information in storage, in process, and/or in transmission;" - }, - { - "id": "ac-16_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Ensures that the security attribute associations are made and retained with the information;" - }, - { - "id": "ac-16_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Establishes the permitted {{ insert: param, ac-16_prm_3 }} for {{ insert: param, ac-16_prm_4 }}; and" - }, - { - "id": "ac-16_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Determines the permitted {{ insert: param, ac-16_prm_5 }} for each of the established security attributes." - } - ] - }, - { - "id": "ac-16_gdn", - "name": "guidance", - "prose": "Information is represented internally within information systems using abstractions known as data structures. Internal data structures can represent different types of entities, both active and passive. Active entities, also known as subjects, are typically associated with individuals, devices, or processes acting on behalf of individuals. Passive entities, also known as objects, are typically associated with data structures such as records, buffers, tables, files, inter-process pipes, and communications ports. Security attributes, a form of metadata, are abstractions representing the basic properties or characteristics of active and passive entities with respect to safeguarding information. These attributes may be associated with active entities (i.e., subjects) that have the potential to send or receive information, to cause information to flow among objects, or to change the information system state. These attributes may also be associated with passive entities (i.e., objects) that contain or receive information. The association of security attributes to subjects and objects is referred to as binding and is typically inclusive of setting the attribute value and the attribute type. Security attributes when bound to data/information, enables the enforcement of information security policies for access control and information flow control, either through organizational processes or information system functions or mechanisms. The content or assigned values of security attributes can directly affect the ability of individuals to access organizational information. Organizations can define the types of attributes needed for selected information systems to support missions/business functions. There is potentially a wide range of values that can be assigned to any given security attribute. Release markings could include, for example, US only, NATO, or NOFORN (not releasable to foreign nationals). By specifying permitted attribute ranges and values, organizations can ensure that the security attribute values are meaningful and relevant. The term security labeling refers to the association of security attributes with subjects and objects represented by internal data structures within organizational information systems, to enable information system-based enforcement of information security policies. Security labels include, for example, access authorizations, data life cycle protection (i.e., encryption and data expiration), nationality, affiliation as contractor, and classification of information in accordance with legal and compliance requirements. The term security marking refers to the association of security attributes with objects in a human-readable form, to enable organizational process-based enforcement of information security policies. The AC-16 base control represents the requirement for user-based attribute association (marking). The enhancements to AC-16 represent additional requirements including information system-based attribute association (labeling). Types of attributes include, for example, classification level for objects and clearance (access authorization) level for subjects. An example of a value for both of these attribute types is Top Secret.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ac-21", - "rel": "related" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-10", - "rel": "related" - }, - { - "href": "#sc-16", - "rel": "related" - }, - { - "href": "#mp-3", - "rel": "related" - } - ] - }, - { - "id": "ac-16_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-16.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(a)" - } - ], - "parts": [ - { - "id": "ac-16.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(a)[1]" - } - ], - "prose": "defines types of security attributes to be associated with information:", - "parts": [ - { - "id": "ac-16.a_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(a)[1][a]" - } - ], - "prose": "in storage;" - }, - { - "id": "ac-16.a_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(a)[1][b]" - } - ], - "prose": "in process; and/or" - }, - { - "id": "ac-16.a_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(a)[1][c]" - } - ], - "prose": "in transmission;" - } - ] - }, - { - "id": "ac-16.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(a)[2]" - } - ], - "prose": "defines security attribute values for organization-defined types of security attributes;" - }, - { - "id": "ac-16.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(a)[3]" - } - ], - "prose": "provides the means to associate organization-defined types of security attributes having organization-defined security attribute values with information:", - "parts": [ - { - "id": "ac-16.a_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(a)[3][a]" - } - ], - "prose": "in storage;" - }, - { - "id": "ac-16.a_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(a)[3][b]" - } - ], - "prose": "in process; and/or" - }, - { - "id": "ac-16.a_obj.3.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(a)[3][c]" - } - ], - "prose": "in transmission;" - } - ] - } - ] - }, - { - "id": "ac-16.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(b)" - } - ], - "prose": "ensures that the security attribute associations are made and retained with the information;" - }, - { - "id": "ac-16.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(c)" - } - ], - "parts": [ - { - "id": "ac-16.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(c)[1]" - } - ], - "prose": "defines information systems for which the permitted organization-defined security attributes are to be established;" - }, - { - "id": "ac-16.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(c)[2]" - } - ], - "prose": "defines security attributes that are permitted for organization-defined information systems;" - }, - { - "id": "ac-16.c_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(c)[3]" - } - ], - "prose": "establishes the permitted organization-defined security attributes for organization-defined information systems;" - } - ] - }, - { - "id": "ac-16.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(d)" - } - ], - "parts": [ - { - "id": "ac-16.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(d)[1]" - } - ], - "prose": "defines values or ranges for each of the established security attributes; and" - }, - { - "id": "ac-16.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(d)[2]" - } - ], - "prose": "determines the permitted organization-defined values or ranges for each of the established security attributes." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing the association of security attributes to information in storage, in process, and in transmission\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational capability supporting and maintaining the association of security attributes to information in storage, in process, and in transmission" - } - ] - } - ], - "controls": [ - { - "id": "ac-16.1", - "class": "SP800-53-enhancement", - "title": "Dynamic Attribute Association", - "params": [ - { - "id": "ac-16.1_prm_1", - "label": "organization-defined subjects and objects" - }, - { - "id": "ac-16.1_prm_2", - "label": "organization-defined security policies" - } - ], - "props": [ - { - "name": "label", - "value": "AC-16(1)" - }, - { - "name": "sort-id", - "value": "ac-16.01" - } - ], - "parts": [ - { - "id": "ac-16.1_smt", - "name": "statement", - "prose": "The information system dynamically associates security attributes with {{ insert: param, ac-16.1_prm_1 }} in accordance with {{ insert: param, ac-16.1_prm_2 }} as information is created and combined." - }, - { - "id": "ac-16.1_gdn", - "name": "guidance", - "prose": "Dynamic association of security attributes is appropriate whenever the security characteristics of information changes over time. Security attributes may change, for example, due to information aggregation issues (i.e., the security characteristics of individual information elements are different from the combined elements), changes in individual access authorizations (i.e., privileges), and changes in the security category of information.", - "links": [ - { - "href": "#ac-4", - "rel": "related" - } - ] - }, - { - "id": "ac-16.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-16.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(1)[1]" - } - ], - "prose": "the organization defines subjects and objects to which security attributes are to be dynamically associated as information is created and combined;" - }, - { - "id": "ac-16.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(1)[2]" - } - ], - "prose": "the organization defines security policies requiring the information system to dynamically associate security attributes with organization-defined subjects and objects; and" - }, - { - "id": "ac-16.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(1)[3]" - } - ], - "prose": "the information system dynamically associates security attributes with organization-defined subjects and objects in accordance with organization-defined security policies as information is created and combined." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing dynamic association of security attributes to information\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing dynamic association of security attributes to information" - } - ] - } - ] - }, - { - "id": "ac-16.2", - "class": "SP800-53-enhancement", - "title": "Attribute Value Changes by Authorized Individuals", - "props": [ - { - "name": "label", - "value": "AC-16(2)" - }, - { - "name": "sort-id", - "value": "ac-16.02" - } - ], - "parts": [ - { - "id": "ac-16.2_smt", - "name": "statement", - "prose": "The information system provides authorized individuals (or processes acting on behalf of individuals) the capability to define or change the value of associated security attributes." - }, - { - "id": "ac-16.2_gdn", - "name": "guidance", - "prose": "The content or assigned values of security attributes can directly affect the ability of individuals to access organizational information. Therefore, it is important for information systems to be able to limit the ability to create or modify security attributes to authorized individuals.", - "links": [ - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#au-2", - "rel": "related" - } - ] - }, - { - "id": "ac-16.2_obj", - "name": "objective", - "prose": "Determine if the information system provides authorized individuals (or processes acting on behalf on individuals) the capability to define or change the value of associated security attributes." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing the change of security attribute values\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of individuals authorized to change security attributes\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for changing values of security attributes\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms permitting changes to values of security attributes" - } - ] - } - ] - }, - { - "id": "ac-16.3", - "class": "SP800-53-enhancement", - "title": "Maintenance of Attribute Associations by Information System", - "params": [ - { - "id": "ac-16.3_prm_1", - "label": "organization-defined security attributes" - }, - { - "id": "ac-16.3_prm_2", - "label": "organization-defined subjects and objects" - } - ], - "props": [ - { - "name": "label", - "value": "AC-16(3)" - }, - { - "name": "sort-id", - "value": "ac-16.03" - } - ], - "parts": [ - { - "id": "ac-16.3_smt", - "name": "statement", - "prose": "The information system maintains the association and integrity of {{ insert: param, ac-16.3_prm_1 }} to {{ insert: param, ac-16.3_prm_2 }}." - }, - { - "id": "ac-16.3_gdn", - "name": "guidance", - "prose": "Maintaining the association and integrity of security attributes to subjects and objects with sufficient assurance helps to ensure that the attribute associations can be used as the basis of automated policy actions. Automated policy actions include, for example, access control decisions or information flow control decisions." - }, - { - "id": "ac-16.3_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-16.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(3)[1]" - } - ], - "prose": "the organization defines security attributes to be associated with organization-defined subjects and objects;" - }, - { - "id": "ac-16.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(3)[2]" - } - ], - "prose": "the organization defines subjects and objects requiring the association and integrity of security attributes to such subjects and objects to be maintained; and" - }, - { - "id": "ac-16.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(3)[3]" - } - ], - "prose": "the information system maintains the association and integrity of organization-defined security attributes to organization-defined subjects and objects." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing the association of security attributes to information\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms maintaining association and integrity of security attributes to information" - } - ] - } - ] - }, - { - "id": "ac-16.4", - "class": "SP800-53-enhancement", - "title": "Association of Attributes by Authorized Individuals", - "params": [ - { - "id": "ac-16.4_prm_1", - "label": "organization-defined security attributes" - }, - { - "id": "ac-16.4_prm_2", - "label": "organization-defined subjects and objects" - } - ], - "props": [ - { - "name": "label", - "value": "AC-16(4)" - }, - { - "name": "sort-id", - "value": "ac-16.04" - } - ], - "parts": [ - { - "id": "ac-16.4_smt", - "name": "statement", - "prose": "The information system supports the association of {{ insert: param, ac-16.4_prm_1 }} with {{ insert: param, ac-16.4_prm_2 }} by authorized individuals (or processes acting on behalf of individuals)." - }, - { - "id": "ac-16.4_gdn", - "name": "guidance", - "prose": "The support provided by information systems can vary to include: (i) prompting users to select specific security attributes to be associated with specific information objects; (ii) employing automated mechanisms for categorizing information with appropriate attributes based on defined policies; or (iii) ensuring that the combination of selected security attributes selected is valid. Organizations consider the creation, deletion, or modification of security attributes when defining auditable events." - }, - { - "id": "ac-16.4_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-16.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(4)[1]" - } - ], - "prose": "the organization defines security attributes to be associated with subjects and objects by authorized individuals (or processes acting on behalf of individuals);" - }, - { - "id": "ac-16.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(4)[2]" - } - ], - "prose": "the organization defines subjects and objects requiring the association of organization-defined security attributes by authorized individuals (or processes acting on behalf of individuals); and" - }, - { - "id": "ac-16.4_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(4)[3]" - } - ], - "prose": "the information system supports the association of organization-defined security attributes with organization-defined subjects and objects by authorized individuals (or processes acting on behalf of individuals)." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing the association of security attributes to information\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of users authorized to associate security attributes to information\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for associating security attributes to information\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting user associations of security attributes to information" - } - ] - } - ] - }, - { - "id": "ac-16.5", - "class": "SP800-53-enhancement", - "title": "Attribute Displays for Output Devices", - "params": [ - { - "id": "ac-16.5_prm_1", - "label": "organization-identified special dissemination, handling, or distribution instructions" - }, - { - "id": "ac-16.5_prm_2", - "label": "organization-identified human-readable, standard naming conventions" - } - ], - "props": [ - { - "name": "label", - "value": "AC-16(5)" - }, - { - "name": "sort-id", - "value": "ac-16.05" - } - ], - "parts": [ - { - "id": "ac-16.5_smt", - "name": "statement", - "prose": "The information system displays security attributes in human-readable form on each object that the system transmits to output devices to identify {{ insert: param, ac-16.5_prm_1 }} using {{ insert: param, ac-16.5_prm_2 }}." - }, - { - "id": "ac-16.5_gdn", - "name": "guidance", - "prose": "Information system outputs include, for example, pages, screens, or equivalent. Information system output devices include, for example, printers and video displays on computer workstations, notebook computers, and personal digital assistants." - }, - { - "id": "ac-16.5_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-16.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(5)[1]" - } - ], - "prose": "the organization identifies special dissemination, handling, or distribution instructions to be used for each object that the information system transmits to output devices;" - }, - { - "id": "ac-16.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(5)[2]" - } - ], - "prose": "the organization identifies human-readable, standard naming conventions for the security attributes to be displayed in human-readable form on each object that the information system transmits to output devices; and" - }, - { - "id": "ac-16.5_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(5)[3]" - } - ], - "prose": "the information system displays security attributes in human-readable form on each object that the system transmits to output devices to identify organization-identified special dissemination, handling, or distribution instructions using organization-identified human readable, standard naming conventions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing display of security attributes in human-readable form\n\nspecial dissemination, handling, or distribution instructions\n\ntypes of human-readable, standard naming conventions\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System output devices displaying security attributes in human-readable form on each object" - } - ] - } - ] - }, - { - "id": "ac-16.6", - "class": "SP800-53-enhancement", - "title": "Maintenance of Attribute Association by Organization", - "params": [ - { - "id": "ac-16.6_prm_1", - "label": "organization-defined security attributes" - }, - { - "id": "ac-16.6_prm_2", - "label": "organization-defined subjects and objects" - }, - { - "id": "ac-16.6_prm_3", - "label": "organization-defined security policies" - } - ], - "props": [ - { - "name": "label", - "value": "AC-16(6)" - }, - { - "name": "sort-id", - "value": "ac-16.06" - } - ], - "parts": [ - { - "id": "ac-16.6_smt", - "name": "statement", - "prose": "The organization allows personnel to associate, and maintain the association of {{ insert: param, ac-16.6_prm_1 }} with {{ insert: param, ac-16.6_prm_2 }} in accordance with {{ insert: param, ac-16.6_prm_3 }}." - }, - { - "id": "ac-16.6_gdn", - "name": "guidance", - "prose": "This control enhancement requires individual users (as opposed to the information system) to maintain associations of security attributes with subjects and objects." - }, - { - "id": "ac-16.6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-16.6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(6)[1]" - } - ], - "prose": "defines security attributes to be associated with subjects and objects;" - }, - { - "id": "ac-16.6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(6)[2]" - } - ], - "prose": "defines subjects and objects to be associated with organization-defined security attributes;" - }, - { - "id": "ac-16.6_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(6)[3]" - } - ], - "prose": "defines security policies to allow personnel to associate, and maintain the association of organization-defined security attributes with organization-defined subjects and objects; and" - }, - { - "id": "ac-16.6_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(6)[4]" - } - ], - "prose": "allows personnel to associate, and maintain the association of organization-defined security attributes with organization-defined subjects and objects in accordance with organization-defined security policies." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing association of security attributes with subjects and objects\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for associating and maintaining association of security attributes with subjects and objects\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting associations of security attributes to subjects and objects" - } - ] - } - ] - }, - { - "id": "ac-16.7", - "class": "SP800-53-enhancement", - "title": "Consistent Attribute Interpretation", - "props": [ - { - "name": "label", - "value": "AC-16(7)" - }, - { - "name": "sort-id", - "value": "ac-16.07" - } - ], - "parts": [ - { - "id": "ac-16.7_smt", - "name": "statement", - "prose": "The organization provides a consistent interpretation of security attributes transmitted between distributed information system components." - }, - { - "id": "ac-16.7_gdn", - "name": "guidance", - "prose": "In order to enforce security policies across multiple components in distributed information systems (e.g., distributed database management systems, cloud-based systems, and service-oriented architectures), organizations provide a consistent interpretation of security attributes that are used in access enforcement and flow enforcement decisions. Organizations establish agreements and processes to ensure that all distributed information system components implement security attributes with consistent interpretations in automated access/flow enforcement actions." - }, - { - "id": "ac-16.7_obj", - "name": "objective", - "prose": "Determine if the organization provides a consistent interpretation of security attributes transmitted between distributed information system components." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing consistent interpretation of security attributes transmitted between distributed information system components\n\nprocedures addressing access enforcement\n\nprocedures addressing information flow enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for providing consistent interpretation of security attributes used in access enforcement and information flow enforcement actions\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing access enforcement and information flow enforcement functions" - } - ] - } - ] - }, - { - "id": "ac-16.8", - "class": "SP800-53-enhancement", - "title": "Association Techniques / Technologies", - "params": [ - { - "id": "ac-16.8_prm_1", - "label": "organization-defined techniques or technologies" - }, - { - "id": "ac-16.8_prm_2", - "label": "organization-defined level of assurance" - } - ], - "props": [ - { - "name": "label", - "value": "AC-16(8)" - }, - { - "name": "sort-id", - "value": "ac-16.08" - } - ], - "parts": [ - { - "id": "ac-16.8_smt", - "name": "statement", - "prose": "The information system implements {{ insert: param, ac-16.8_prm_1 }} with {{ insert: param, ac-16.8_prm_2 }} in associating security attributes to information." - }, - { - "id": "ac-16.8_gdn", - "name": "guidance", - "prose": "The association (i.e., binding) of security attributes to information within information systems is of significant importance with regard to conducting automated access enforcement and flow enforcement actions. The association of such security attributes can be accomplished with technologies/techniques providing different levels of assurance. For example, information systems can cryptographically bind security attributes to information using digital signatures with the supporting cryptographic keys protected by hardware devices (sometimes known as hardware roots of trust)." - }, - { - "id": "ac-16.8_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-16.8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(8)[1]" - } - ], - "prose": "the organization defines techniques or technologies to be implemented in associating security attributes to information;" - }, - { - "id": "ac-16.8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(8)[2]" - } - ], - "prose": "the organization defines level of assurance to be provided when the information system implements organization-defined technologies or technologies to associate security attributes to information; and" - }, - { - "id": "ac-16.8_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(8)[3]" - } - ], - "prose": "the information system implements organization-defined techniques or technologies with organization-defined level of assurance in associating security attributes to information." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing association of security attributes to information\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for associating security attributes to information\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing techniques or technologies associating security attributes to information" - } - ] - } - ] - }, - { - "id": "ac-16.9", - "class": "SP800-53-enhancement", - "title": "Attribute Reassignment", - "params": [ - { - "id": "ac-16.9_prm_1", - "label": "organization-defined techniques or procedures" - } - ], - "props": [ - { - "name": "label", - "value": "AC-16(9)" - }, - { - "name": "sort-id", - "value": "ac-16.09" - } - ], - "parts": [ - { - "id": "ac-16.9_smt", - "name": "statement", - "prose": "The organization ensures that security attributes associated with information are reassigned only via re-grading mechanisms validated using {{ insert: param, ac-16.9_prm_1 }}." - }, - { - "id": "ac-16.9_gdn", - "name": "guidance", - "prose": "Validated re-grading mechanisms are employed by organizations to provide the requisite levels of assurance for security attribute reassignment activities. The validation is facilitated by ensuring that re-grading mechanisms are single purpose and of limited function. Since security attribute reassignments can affect security policy enforcement actions (e.g., access/flow enforcement decisions), using trustworthy re-grading mechanisms is necessary to ensure that such mechanisms perform in a consistent/correct mode of operation." - }, - { - "id": "ac-16.9_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-16.9_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(9)[1]" - } - ], - "prose": "defines techniques or procedures to validate re-grading mechanisms used to reassign association of security attributes with information; and" - }, - { - "id": "ac-16.9_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-16(9)[2]" - } - ], - "prose": "ensures that security attributes associated with information are reassigned only via re-grading mechanisms validated using organization-defined techniques or procedures." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing reassignment of security attributes to information\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for reassigning association of security attributes to information\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing techniques or procedures for reassigning association of security attributes to information" - } - ] - } - ] - }, - { - "id": "ac-16.10", - "class": "SP800-53-enhancement", - "title": "Attribute Configuration by Authorized Individuals", - "props": [ - { - "name": "label", - "value": "AC-16(10)" - }, - { - "name": "sort-id", - "value": "ac-16.10" - } - ], - "parts": [ - { - "id": "ac-16.10_smt", - "name": "statement", - "prose": "The information system provides authorized individuals the capability to define or change the type and value of security attributes available for association with subjects and objects." - }, - { - "id": "ac-16.10_gdn", - "name": "guidance", - "prose": "The content or assigned values of security attributes can directly affect the ability of individuals to access organizational information. Therefore, it is important for information systems to be able to limit the ability to create or modify security attributes to authorized individuals only." - }, - { - "id": "ac-16.10_obj", - "name": "objective", - "prose": "Determine if the information system provides authorized individuals the capability to define or change the type and value of security attributes available for association with subjects and objects." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing configuration of security attributes by authorized individuals\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for defining or changing security attributes associated with information\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing capability for defining or changing security attributes" - } - ] - } - ] - } - ] - }, - { - "id": "ac-17", - "class": "SP800-53", - "title": "Remote Access", - "props": [ - { - "name": "label", - "value": "AC-17" - }, - { - "name": "sort-id", - "value": "ac-17" - } - ], - "links": [ - { - "href": "#5309d4d0-46f8-4213-a749-e7584164e5e8", - "rel": "reference" - }, - { - "href": "#99f331f2-a9f0-46c2-9856-a3cbb9b89442", - "rel": "reference" - }, - { - "href": "#349fe082-502d-464a-aa0c-1443c6a5cf40", - "rel": "reference" - }, - { - "href": "#1201fcf3-afb1-4675-915a-fb4ae0435717", - "rel": "reference" - }, - { - "href": "#d1a4e2a9-e512-4132-8795-5357aba29254", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ac-17_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ac-17_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Establishes and documents usage restrictions, configuration/connection requirements, and implementation guidance for each type of remote access allowed; and" - }, - { - "id": "ac-17_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Authorizes remote access to the information system prior to allowing such connections." - } - ] - }, - { - "id": "ac-17_gdn", - "name": "guidance", - "prose": "Remote access is access to organizational information systems by users (or processes acting on behalf of users) communicating through external networks (e.g., the Internet). Remote access methods include, for example, dial-up, broadband, and wireless. Organizations often employ encrypted virtual private networks (VPNs) to enhance confidentiality and integrity over remote connections. The use of encrypted VPNs does not make the access non-remote; however, the use of VPNs, when adequately provisioned with appropriate security controls (e.g., employing appropriate encryption techniques for confidentiality and integrity protection) may provide sufficient assurance to the organization that it can effectively treat such connections as internal networks. Still, VPN connections traverse external networks, and the encrypted VPN does not enhance the availability of remote connections. Also, VPNs with encrypted tunnels can affect the organizational capability to adequately monitor network communications traffic for malicious code. Remote access controls apply to information systems other than public web servers or systems designed for public access. This control addresses authorization prior to allowing remote access without specifying the formats for such authorization. While organizations may use interconnection security agreements to authorize remote access connections, such agreements are not required by this control. Enforcing access restrictions for remote connections is addressed in AC-3.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#ac-20", - "rel": "related" - }, - { - "href": "#ca-3", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#pe-17", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#sc-10", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "ac-17_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-17.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-17(a)" - } - ], - "parts": [ - { - "id": "ac-17.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-17(a)[1]" - } - ], - "prose": "identifies the types of remote access allowed to the information system;" - }, - { - "id": "ac-17.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-17(a)[2]" - } - ], - "prose": "establishes for each type of remote access allowed:", - "parts": [ - { - "id": "ac-17.a_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-17(a)[2][a]" - } - ], - "prose": "usage restrictions;" - }, - { - "id": "ac-17.a_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-17(a)[2][b]" - } - ], - "prose": "configuration/connection requirements;" - }, - { - "id": "ac-17.a_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-17(a)[2][c]" - } - ], - "prose": "implementation guidance;" - } - ] - }, - { - "id": "ac-17.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-17(a)[3]" - } - ], - "prose": "documents for each type of remote access allowed:", - "parts": [ - { - "id": "ac-17.a_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-17(a)[3][a]" - } - ], - "prose": "usage restrictions;" - }, - { - "id": "ac-17.a_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-17(a)[3][b]" - } - ], - "prose": "configuration/connection requirements;" - }, - { - "id": "ac-17.a_obj.3.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-17(a)[3][c]" - } - ], - "prose": "implementation guidance; and" - } - ] - } - ] - }, - { - "id": "ac-17.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-17(b)" - } - ], - "prose": "authorizes remote access to the information system prior to allowing such connections." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing remote access implementation and usage (including restrictions)\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system configuration settings and associated documentation\n\nremote access authorizations\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for managing remote access connections\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Remote access management capability for the information system" - } - ] - } - ], - "controls": [ - { - "id": "ac-17.1", - "class": "SP800-53-enhancement", - "title": "Automated Monitoring / Control", - "props": [ - { - "name": "label", - "value": "AC-17(1)" - }, - { - "name": "sort-id", - "value": "ac-17.01" - } - ], - "parts": [ - { - "id": "ac-17.1_smt", - "name": "statement", - "prose": "The information system monitors and controls remote access methods." - }, - { - "id": "ac-17.1_gdn", - "name": "guidance", - "prose": "Automated monitoring and control of remote access sessions allows organizations to detect cyber attacks and also ensure ongoing compliance with remote access policies by auditing connection activities of remote users on a variety of information system components (e.g., servers, workstations, notebook computers, smart phones, and tablets).", - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - } - ] - }, - { - "id": "ac-17.1_obj", - "name": "objective", - "prose": "Determine if the information system monitors and controls remote access methods." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing remote access to the information system\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\ninformation system monitoring records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms monitoring and controlling remote access methods" - } - ] - } - ] - }, - { - "id": "ac-17.2", - "class": "SP800-53-enhancement", - "title": "Protection of Confidentiality / Integrity Using Encryption", - "props": [ - { - "name": "label", - "value": "AC-17(2)" - }, - { - "name": "sort-id", - "value": "ac-17.02" - } - ], - "parts": [ - { - "id": "ac-17.2_smt", - "name": "statement", - "prose": "The information system implements cryptographic mechanisms to protect the confidentiality and integrity of remote access sessions." - }, - { - "id": "ac-17.2_gdn", - "name": "guidance", - "prose": "The encryption strength of mechanism is selected based on the security categorization of the information.", - "links": [ - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "ac-17.2_obj", - "name": "objective", - "prose": "Determine if the information system implements cryptographic mechanisms to protect the confidentiality and integrity of remote access sessions." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing remote access to the information system\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ncryptographic mechanisms and associated configuration documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Cryptographic mechanisms protecting confidentiality and integrity of remote access sessions" - } - ] - } - ] - }, - { - "id": "ac-17.3", - "class": "SP800-53-enhancement", - "title": "Managed Access Control Points", - "params": [ - { - "id": "ac-17.3_prm_1", - "label": "organization-defined number" - } - ], - "props": [ - { - "name": "label", - "value": "AC-17(3)" - }, - { - "name": "sort-id", - "value": "ac-17.03" - } - ], - "parts": [ - { - "id": "ac-17.3_smt", - "name": "statement", - "prose": "The information system routes all remote accesses through {{ insert: param, ac-17.3_prm_1 }} managed network access control points." - }, - { - "id": "ac-17.3_gdn", - "name": "guidance", - "prose": "Limiting the number of access control points for remote accesses reduces the attack surface for organizations. Organizations consider the Trusted Internet Connections (TIC) initiative requirements for external network connections.", - "links": [ - { - "href": "#sc-7", - "rel": "related" - } - ] - }, - { - "id": "ac-17.3_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-17.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-17(3)[1]" - } - ], - "prose": "the organization defines the number of managed network access control points through which all remote accesses are to be routed; and" - }, - { - "id": "ac-17.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-17(3)[2]" - } - ], - "prose": "the information system routes all remote accesses through the organization-defined number of managed network access control points." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing remote access to the information system\n\ninformation system design documentation\n\nlist of all managed network access control points\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms routing all remote accesses through managed network access control points" - } - ] - } - ] - }, - { - "id": "ac-17.4", - "class": "SP800-53-enhancement", - "title": "Privileged Commands / Access", - "params": [ - { - "id": "ac-17.4_prm_1", - "label": "organization-defined needs" - } - ], - "props": [ - { - "name": "label", - "value": "AC-17(4)" - }, - { - "name": "sort-id", - "value": "ac-17.04" - } - ], - "parts": [ - { - "id": "ac-17.4_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ac-17.4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Authorizes the execution of privileged commands and access to security-relevant information via remote access only for {{ insert: param, ac-17.4_prm_1 }}; and" - }, - { - "id": "ac-17.4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Documents the rationale for such access in the security plan for the information system." - } - ] - }, - { - "id": "ac-17.4_gdn", - "name": "guidance", - "links": [ - { - "href": "#ac-6", - "rel": "related" - } - ] - }, - { - "id": "ac-17.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-17.4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-17(4)(a)" - } - ], - "parts": [ - { - "id": "ac-17.4.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-17(4)(a)[1]" - } - ], - "prose": "defines needs to authorize the execution of privileged commands and access to security-relevant information via remote access;" - }, - { - "id": "ac-17.4.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-17(4)(a)[2]" - } - ], - "prose": "authorizes the execution of privileged commands and access to security-relevant information via remote access only for organization-defined needs; and" - } - ], - "links": [ - { - "href": "#ac-17.4_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ac-17.4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-17(4)(b)" - } - ], - "prose": "documents the rationale for such access in the information system security plan.", - "links": [ - { - "href": "#ac-17.4_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing remote access to the information system\n\ninformation system configuration settings and associated documentation\n\nsecurity plan\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing remote access management" - } - ] - } - ] - }, - { - "id": "ac-17.5", - "class": "SP800-53-enhancement", - "title": "Monitoring for Unauthorized Connections", - "props": [ - { - "name": "label", - "value": "AC-17(5)" - }, - { - "name": "sort-id", - "value": "ac-17.05" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#si-4", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ac-17.6", - "class": "SP800-53-enhancement", - "title": "Protection of Information", - "props": [ - { - "name": "label", - "value": "AC-17(6)" - }, - { - "name": "sort-id", - "value": "ac-17.06" - } - ], - "parts": [ - { - "id": "ac-17.6_smt", - "name": "statement", - "prose": "The organization ensures that users protect information about remote access mechanisms from unauthorized use and disclosure." - }, - { - "id": "ac-17.6_gdn", - "name": "guidance", - "links": [ - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - } - ] - }, - { - "id": "ac-17.6_obj", - "name": "objective", - "prose": "Determine if the organization ensures that users protect information about remote access mechanisms from unauthorized use and disclosure." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing remote access to the information system\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for implementing or monitoring remote access to the information system\n\ninformation system users with knowledge of information about remote access mechanisms\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "ac-17.7", - "class": "SP800-53-enhancement", - "title": "Additional Protection for Security Function Access", - "props": [ - { - "name": "label", - "value": "AC-17(7)" - }, - { - "name": "sort-id", - "value": "ac-17.07" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#ac-3.10", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ac-17.8", - "class": "SP800-53-enhancement", - "title": "Disable Nonsecure Network Protocols", - "props": [ - { - "name": "label", - "value": "AC-17(8)" - }, - { - "name": "sort-id", - "value": "ac-17.08" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#cm-7", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ac-17.9", - "class": "SP800-53-enhancement", - "title": "Disconnect / Disable Access", - "params": [ - { - "id": "ac-17.9_prm_1", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "AC-17(9)" - }, - { - "name": "sort-id", - "value": "ac-17.09" - } - ], - "parts": [ - { - "id": "ac-17.9_smt", - "name": "statement", - "prose": "The organization provides the capability to expeditiously disconnect or disable remote access to the information system within {{ insert: param, ac-17.9_prm_1 }}." - }, - { - "id": "ac-17.9_gdn", - "name": "guidance", - "prose": "This control enhancement requires organizations to have the capability to rapidly disconnect current users remotely accessing the information system and/or disable further remote access. The speed of disconnect or disablement varies based on the criticality of missions/business functions and the need to eliminate immediate or future remote access to organizational information systems." - }, - { - "id": "ac-17.9_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-17.9_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-17(9)[1]" - } - ], - "prose": "defines the time period within which to expeditiously disconnect or disable remote access to the information system; and" - }, - { - "id": "ac-17.9_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-17(9)[2]" - } - ], - "prose": "provides the capability to expeditiously disconnect or disable remote access to the information system within the organization-defined time period." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing disconnecting or disabling remote access to the information system\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsecurity plan, information system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing capability to disconnect or disable remote access to information system" - } - ] - } - ] - } - ] - }, - { - "id": "ac-18", - "class": "SP800-53", - "title": "Wireless Access", - "props": [ - { - "name": "label", - "value": "AC-18" - }, - { - "name": "sort-id", - "value": "ac-18" - } - ], - "links": [ - { - "href": "#238ed479-eccb-49f6-82ec-ab74a7a428cf", - "rel": "reference" - }, - { - "href": "#d1b1d689-0f66-4474-9924-c81119758dc1", - "rel": "reference" - }, - { - "href": "#6f336ecd-f2a0-4c84-9699-0491d81b6e0d", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ac-18_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ac-18_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Establishes usage restrictions, configuration/connection requirements, and implementation guidance for wireless access; and" - }, - { - "id": "ac-18_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Authorizes wireless access to the information system prior to allowing such connections." - } - ] - }, - { - "id": "ac-18_gdn", - "name": "guidance", - "prose": "Wireless technologies include, for example, microwave, packet radio (UHF/VHF), 802.11x, and Bluetooth. Wireless networks use authentication protocols (e.g., EAP/TLS, PEAP), which provide credential protection and mutual authentication.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#ca-3", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "ac-18_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-18.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-18(a)" - } - ], - "prose": "establishes for wireless access:", - "parts": [ - { - "id": "ac-18.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-18(a)[1]" - } - ], - "prose": "usage restrictions;" - }, - { - "id": "ac-18.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-18(a)[2]" - } - ], - "prose": "configuration/connection requirement;" - }, - { - "id": "ac-18.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-18(a)[3]" - } - ], - "prose": "implementation guidance; and" - } - ] - }, - { - "id": "ac-18.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-18(b)" - } - ], - "prose": "authorizes wireless access to the information system prior to allowing such connections." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing wireless access implementation and usage (including restrictions)\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nwireless access authorizations\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for managing wireless access connections\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Wireless access management capability for the information system" - } - ] - } - ], - "controls": [ - { - "id": "ac-18.1", - "class": "SP800-53-enhancement", - "title": "Authentication and Encryption", - "params": [ - { - "id": "ac-18.1_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "users", - "devices" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "AC-18(1)" - }, - { - "name": "sort-id", - "value": "ac-18.01" - } - ], - "parts": [ - { - "id": "ac-18.1_smt", - "name": "statement", - "prose": "The information system protects wireless access to the system using authentication of {{ insert: param, ac-18.1_prm_1 }} and encryption." - }, - { - "id": "ac-18.1_gdn", - "name": "guidance", - "links": [ - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "ac-18.1_obj", - "name": "objective", - "prose": "Determine if the information system protects wireless access to the system using encryption and one or more of the following:", - "parts": [ - { - "id": "ac-18.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-18(1)[1]" - } - ], - "prose": "authentication of users; and/or" - }, - { - "id": "ac-18.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-18(1)[2]" - } - ], - "prose": "authentication of devices." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing wireless implementation and usage (including restrictions)\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing wireless access protections to the information system" - } - ] - } - ] - }, - { - "id": "ac-18.2", - "class": "SP800-53-enhancement", - "title": "Monitoring Unauthorized Connections", - "props": [ - { - "name": "label", - "value": "AC-18(2)" - }, - { - "name": "sort-id", - "value": "ac-18.02" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#si-4", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ac-18.3", - "class": "SP800-53-enhancement", - "title": "Disable Wireless Networking", - "props": [ - { - "name": "label", - "value": "AC-18(3)" - }, - { - "name": "sort-id", - "value": "ac-18.03" - } - ], - "parts": [ - { - "id": "ac-18.3_smt", - "name": "statement", - "prose": "The organization disables, when not intended for use, wireless networking capabilities internally embedded within information system components prior to issuance and deployment." - }, - { - "id": "ac-18.3_gdn", - "name": "guidance", - "links": [ - { - "href": "#ac-19", - "rel": "related" - } - ] - }, - { - "id": "ac-18.3_obj", - "name": "objective", - "prose": "Determine if the organization disables, when not intended for use, wireless networking capabilities internally embedded within information system components prior to issuance and deployment." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing wireless implementation and usage (including restrictions)\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms managing the disabling of wireless networking capabilities internally embedded within information system components" - } - ] - } - ] - }, - { - "id": "ac-18.4", - "class": "SP800-53-enhancement", - "title": "Restrict Configurations by Users", - "props": [ - { - "name": "label", - "value": "AC-18(4)" - }, - { - "name": "sort-id", - "value": "ac-18.04" - } - ], - "parts": [ - { - "id": "ac-18.4_smt", - "name": "statement", - "prose": "The organization identifies and explicitly authorizes users allowed to independently configure wireless networking capabilities." - }, - { - "id": "ac-18.4_gdn", - "name": "guidance", - "prose": "Organizational authorizations to allow selected users to configure wireless networking capability are enforced in part, by the access enforcement mechanisms employed within organizational information systems.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#sc-15", - "rel": "related" - } - ] - }, - { - "id": "ac-18.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-18.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-18(4)[1]" - } - ], - "prose": "identifies users allowed to independently configure wireless networking capabilities; and" - }, - { - "id": "ac-18.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-18(4)[2]" - } - ], - "prose": "explicitly authorizes the identified users allowed to independently configure wireless networking capabilities." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing wireless implementation and usage (including restrictions)\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms authorizing independent user configuration of wireless networking capabilities" - } - ] - } - ] - }, - { - "id": "ac-18.5", - "class": "SP800-53-enhancement", - "title": "Antennas / Transmission Power Levels", - "props": [ - { - "name": "label", - "value": "AC-18(5)" - }, - { - "name": "sort-id", - "value": "ac-18.05" - } - ], - "parts": [ - { - "id": "ac-18.5_smt", - "name": "statement", - "prose": "The organization selects radio antennas and calibrates transmission power levels to reduce the probability that usable signals can be received outside of organization-controlled boundaries." - }, - { - "id": "ac-18.5_gdn", - "name": "guidance", - "prose": "Actions that may be taken by organizations to limit unauthorized use of wireless communications outside of organization-controlled boundaries include, for example: (i) reducing the power of wireless transmissions so that the transmissions are less likely to emit a signal that can be used by adversaries outside of the physical perimeters of organizations; (ii) employing measures such as TEMPEST to control wireless emanations; and (iii) using directional/beam forming antennas that reduce the likelihood that unintended receivers will be able to intercept signals. Prior to taking such actions, organizations can conduct periodic wireless surveys to understand the radio frequency profile of organizational information systems as well as other systems that may be operating in the area.", - "links": [ - { - "href": "#pe-19", - "rel": "related" - } - ] - }, - { - "id": "ac-18.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-18.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-18(5)[1]" - } - ], - "prose": "selects radio antennas to reduce the probability that usable signals can be received outside of organization-controlled boundaries; and" - }, - { - "id": "ac-18.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-18(5)[2]" - } - ], - "prose": "calibrates transmission power levels to reduce the probability that usable signals can be received outside of organization-controlled boundaries." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing wireless implementation and usage (including restrictions)\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Wireless access capability protecting usable signals from unauthorized access outside organization-controlled boundaries" - } - ] - } - ] - } - ] - }, - { - "id": "ac-19", - "class": "SP800-53", - "title": "Access Control for Mobile Devices", - "props": [ - { - "name": "label", - "value": "AC-19" - }, - { - "name": "sort-id", - "value": "ac-19" - } - ], - "links": [ - { - "href": "#4da24a96-6cf8-435d-9d1f-c73247cad109", - "rel": "reference" - }, - { - "href": "#1201fcf3-afb1-4675-915a-fb4ae0435717", - "rel": "reference" - }, - { - "href": "#0293a393-fbe8-4ed1-b0b4-f6fbd3ae1589", - "rel": "reference" - }, - { - "href": "#6513e480-fada-4876-abba-1397084dfb26", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ac-19_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ac-19_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Establishes usage restrictions, configuration requirements, connection requirements, and implementation guidance for organization-controlled mobile devices; and" - }, - { - "id": "ac-19_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Authorizes the connection of mobile devices to organizational information systems." - } - ] - }, - { - "id": "ac-19_gdn", - "name": "guidance", - "prose": "A mobile device is a computing device that: (i) has a small form factor such that it can easily be carried by a single individual; (ii) is designed to operate without a physical connection (e.g., wirelessly transmit or receive information); (iii) possesses local, non-removable or removable data storage; and (iv) includes a self-contained power source. Mobile devices may also include voice communication capabilities, on-board sensors that allow the device to capture information, and/or built-in features for synchronizing local data with remote locations. Examples include smart phones, E-readers, and tablets. Mobile devices are typically associated with a single individual and the device is usually in close proximity to the individual; however, the degree of proximity can vary depending upon on the form factor and size of the device. The processing, storage, and transmission capability of the mobile device may be comparable to or merely a subset of desktop systems, depending upon the nature and intended purpose of the device. Due to the large variety of mobile devices with different technical characteristics and capabilities, organizational restrictions may vary for the different classes/types of such devices. Usage restrictions and specific implementation guidance for mobile devices include, for example, configuration management, device identification and authentication, implementation of mandatory protective software (e.g., malicious code detection, firewall), scanning devices for malicious code, updating virus protection software, scanning for critical software updates and patches, conducting primary operating system (and possibly other resident software) integrity checks, and disabling unnecessary hardware (e.g., wireless, infrared). Organizations are cautioned that the need to provide adequate security for mobile devices goes beyond the requirements in this control. Many safeguards and countermeasures for mobile devices are reflected in other security controls in the catalog allocated in the initial control baselines as starting points for the development of security plans and overlays using the tailoring process. There may also be some degree of overlap in the requirements articulated by the security controls within the different families of controls. AC-20 addresses mobile devices that are not organization-controlled.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-7", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-20", - "rel": "related" - }, - { - "href": "#ca-9", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-43", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "ac-19_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-19.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-19(a)" - } - ], - "prose": "establishes for organization-controlled mobile devices:", - "parts": [ - { - "id": "ac-19.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-19(a)[1]" - } - ], - "prose": "usage restrictions;" - }, - { - "id": "ac-19.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-19(a)[2]" - } - ], - "prose": "configuration/connection requirement;" - }, - { - "id": "ac-19.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-19(a)[3]" - } - ], - "prose": "implementation guidance; and" - } - ] - }, - { - "id": "ac-19.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-19(b)" - } - ], - "prose": "authorizes the connection of mobile devices to organizational information systems." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing access control for mobile device usage (including restrictions)\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nauthorizations for mobile device connections to organizational information systems\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel using mobile devices to access organizational information systems\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control capability authorizing mobile device connections to organizational information systems" - } - ] - } - ], - "controls": [ - { - "id": "ac-19.1", - "class": "SP800-53-enhancement", - "title": "Use of Writable / Portable Storage Devices", - "props": [ - { - "name": "label", - "value": "AC-19(1)" - }, - { - "name": "sort-id", - "value": "ac-19.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#mp-7", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ac-19.2", - "class": "SP800-53-enhancement", - "title": "Use of Personally Owned Portable Storage Devices", - "props": [ - { - "name": "label", - "value": "AC-19(2)" - }, - { - "name": "sort-id", - "value": "ac-19.02" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#mp-7", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ac-19.3", - "class": "SP800-53-enhancement", - "title": "Use of Portable Storage Devices with No Identifiable Owner", - "props": [ - { - "name": "label", - "value": "AC-19(3)" - }, - { - "name": "sort-id", - "value": "ac-19.03" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#mp-7", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ac-19.4", - "class": "SP800-53-enhancement", - "title": "Restrictions for Classified Information", - "params": [ - { - "id": "ac-19.4_prm_1", - "label": "organization-defined security officials" - }, - { - "id": "ac-19.4_prm_2", - "label": "organization-defined security policies" - } - ], - "props": [ - { - "name": "label", - "value": "AC-19(4)" - }, - { - "name": "sort-id", - "value": "ac-19.04" - } - ], - "parts": [ - { - "id": "ac-19.4_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ac-19.4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Prohibits the use of unclassified mobile devices in facilities containing information systems processing, storing, or transmitting classified information unless specifically permitted by the authorizing official; and" - }, - { - "id": "ac-19.4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Enforces the following restrictions on individuals permitted by the authorizing official to use unclassified mobile devices in facilities containing information systems processing, storing, or transmitting classified information:", - "parts": [ - { - "id": "ac-19.4_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "(1)" - } - ], - "prose": "Connection of unclassified mobile devices to classified information systems is prohibited;" - }, - { - "id": "ac-19.4_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "(2)" - } - ], - "prose": "Connection of unclassified mobile devices to unclassified information systems requires approval from the authorizing official;" - }, - { - "id": "ac-19.4_smt.b.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "(3)" - } - ], - "prose": "Use of internal or external modems or wireless interfaces within the unclassified mobile devices is prohibited; and" - }, - { - "id": "ac-19.4_smt.b.4", - "name": "item", - "props": [ - { - "name": "label", - "value": "(4)" - } - ], - "prose": "Unclassified mobile devices and the information stored on those devices are subject to random reviews and inspections by {{ insert: param, ac-19.4_prm_1 }}, and if classified information is found, the incident handling policy is followed." - } - ] - }, - { - "id": "ac-19.4_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Restricts the connection of classified mobile devices to classified information systems in accordance with {{ insert: param, ac-19.4_prm_2 }}." - } - ] - }, - { - "id": "ac-19.4_gdn", - "name": "guidance", - "links": [ - { - "href": "#ca-6", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - } - ] - }, - { - "id": "ac-19.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-19.4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-19(4)(a)" - } - ], - "prose": "prohibits the use of unclassified mobile devices in facilities containing information systems processing, storing, or transmitting classified information unless specifically permitted by the authorizing official;", - "links": [ - { - "href": "#ac-19.4_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ac-19.4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-19(4)(b)" - } - ], - "prose": "enforces the following restrictions on individuals permitted by the authorizing official to use unclassified mobile devices in facilities containing information systems processing, storing, or transmitting classified information:", - "parts": [ - { - "id": "ac-19.4.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-19(4)(b)(1)" - } - ], - "prose": "connection of unclassified mobile devices to classified information systems is prohibited;", - "links": [ - { - "href": "#ac-19.4_smt.b.1", - "rel": "corresp" - } - ] - }, - { - "id": "ac-19.4.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-19(4)(b)(2)" - } - ], - "prose": "connection of unclassified mobile devices to unclassified information systems requires approval from the authorizing official;", - "links": [ - { - "href": "#ac-19.4_smt.b.2", - "rel": "corresp" - } - ] - }, - { - "id": "ac-19.4.b.3_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-19(4)(b)(3)" - } - ], - "prose": "use of internal or external modems or wireless interfaces within the unclassified mobile devices is prohibited;", - "links": [ - { - "href": "#ac-19.4_smt.b.3", - "rel": "corresp" - } - ] - }, - { - "id": "ac-19.4.b.4_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-19(4)(b)(4)" - } - ], - "parts": [ - { - "id": "ac-19.4.b.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-19(4)(b)(4)[1]" - } - ], - "prose": "defines security officials responsible for reviews and inspections of unclassified mobile devices and the information stored on those devices;" - }, - { - "id": "ac-19.4.b.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-19(4)(b)(4)[2]" - } - ], - "prose": "unclassified mobile devices and the information stored on those devices are subject to random reviews/inspections by organization-defined security officials;" - }, - { - "id": "ac-19.4.b.4_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-19(4)(b)(4)[3]" - } - ], - "prose": "the incident handling policy is followed if classified information is found;" - } - ], - "links": [ - { - "href": "#ac-19.4_smt.b.4", - "rel": "corresp" - } - ] - } - ], - "links": [ - { - "href": "#ac-19.4_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "ac-19.4.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-19(4)(c)" - } - ], - "parts": [ - { - "id": "ac-19.4.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-19(4)(c)[1]" - } - ], - "prose": "defines security policies to restrict the connection of classified mobile devices to classified information systems; and" - }, - { - "id": "ac-19.4.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-19(4)(c)[2]" - } - ], - "prose": "restricts the connection of classified mobile devices to classified information systems in accordance with organization-defined security policies." - } - ], - "links": [ - { - "href": "#ac-19.4_smt.c", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nincident handling policy\n\nprocedures addressing access control for mobile devices\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nevidentiary documentation for random inspections and reviews of mobile devices\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel responsible for random reviews/inspections of mobile devices\n\norganizational personnel using mobile devices in facilities containing information systems processing, storing, or transmitting classified information\n\norganizational personnel with incident response responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms prohibiting the use of internal or external modems or wireless interfaces with mobile devices" - } - ] - } - ] - }, - { - "id": "ac-19.5", - "class": "SP800-53-enhancement", - "title": "Full Device / Container-based Encryption", - "params": [ - { - "id": "ac-19.5_prm_1", - "select": { - "choice": [ - "full-device encryption", - "container encryption" - ] - } - }, - { - "id": "ac-19.5_prm_2", - "label": "organization-defined mobile devices" - } - ], - "props": [ - { - "name": "label", - "value": "AC-19(5)" - }, - { - "name": "sort-id", - "value": "ac-19.05" - } - ], - "parts": [ - { - "id": "ac-19.5_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, ac-19.5_prm_1 }} to protect the confidentiality and integrity of information on {{ insert: param, ac-19.5_prm_2 }}." - }, - { - "id": "ac-19.5_gdn", - "name": "guidance", - "prose": "Container-based encryption provides a more fine-grained approach to the encryption of data/information on mobile devices, including for example, encrypting selected data structures such as files, records, or fields.", - "links": [ - { - "href": "#mp-5", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#sc-28", - "rel": "related" - } - ] - }, - { - "id": "ac-19.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-19.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-19(5)[1]" - } - ], - "prose": "defines mobile devices for which full-device encryption or container encryption is required to protect the confidentiality and integrity of information on such devices; and" - }, - { - "id": "ac-19.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-19(5)[2]" - } - ], - "prose": "employs full-device encryption or container encryption to protect the confidentiality and integrity of information on organization-defined mobile devices." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing access control for mobile devices\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nencryption mechanism s and associated configuration documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with access control responsibilities for mobile devices\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Encryption mechanisms protecting confidentiality and integrity of information on mobile devices" - } - ] - } - ] - } - ] - }, - { - "id": "ac-20", - "class": "SP800-53", - "title": "Use of External Information Systems", - "props": [ - { - "name": "label", - "value": "AC-20" - }, - { - "name": "sort-id", - "value": "ac-20" - } - ], - "links": [ - { - "href": "#e85cdb3f-7f0a-4083-8639-f13f70d3760b", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ac-20_smt", - "name": "statement", - "prose": "The organization establishes terms and conditions, consistent with any trust relationships established with other organizations owning, operating, and/or maintaining external information systems, allowing authorized individuals to:", - "parts": [ - { - "id": "ac-20_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Access the information system from external information systems; and" - }, - { - "id": "ac-20_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Process, store, or transmit organization-controlled information using external information systems." - } - ] - }, - { - "id": "ac-20_gdn", - "name": "guidance", - "prose": "External information systems are information systems or components of information systems that are outside of the authorization boundary established by organizations and for which organizations typically have no direct supervision and authority over the application of required security controls or the assessment of control effectiveness. External information systems include, for example: (i) personally owned information systems/devices (e.g., notebook computers, smart phones, tablets, personal digital assistants); (ii) privately owned computing and communications devices resident in commercial or public facilities (e.g., hotels, train stations, convention centers, shopping malls, or airports); (iii) information systems owned or controlled by nonfederal governmental organizations; and (iv) federal information systems that are not owned by, operated by, or under the direct supervision and authority of organizations. This control also addresses the use of external information systems for the processing, storage, or transmission of organizational information, including, for example, accessing cloud services (e.g., infrastructure as a service, platform as a service, or software as a service) from organizational information systems. For some external information systems (i.e., information systems operated by other federal agencies, including organizations subordinate to those agencies), the trust relationships that have been established between those organizations and the originating organization may be such, that no explicit terms and conditions are required. Information systems within these organizations would not be considered external. These situations occur when, for example, there are pre-existing sharing/trust agreements (either implicit or explicit) established between federal agencies or organizations subordinate to those agencies, or when such trust agreements are specified by applicable laws, Executive Orders, directives, or policies. Authorized individuals include, for example, organizational personnel, contractors, or other individuals with authorized access to organizational information systems and over which organizations have the authority to impose rules of behavior with regard to system access. Restrictions that organizations impose on authorized individuals need not be uniform, as those restrictions may vary depending upon the trust relationships between organizations. Therefore, organizations may choose to impose different security restrictions on contractors than on state, local, or tribal governments. This control does not apply to the use of external information systems to access public interfaces to organizational information systems (e.g., individuals accessing federal information through www.usa.gov). Organizations establish terms and conditions for the use of external information systems in accordance with organizational security policies and procedures. Terms and conditions address as a minimum: types of applications that can be accessed on organizational information systems from external information systems; and the highest security category of information that can be processed, stored, or transmitted on external information systems. If terms and conditions with the owners of external information systems cannot be established, organizations may impose restrictions on organizational personnel using those external systems.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#ca-3", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - } - ] - }, - { - "id": "ac-20_obj", - "name": "objective", - "prose": "Determine if the organization establishes terms and conditions, consistent with any trust relationships established with other organizations owning, operating, and/or maintaining external information systems, allowing authorized individuals to:", - "parts": [ - { - "id": "ac-20.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-20(a)" - } - ], - "prose": "access the information system from the external information systems; and" - }, - { - "id": "ac-20.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-20(b)" - } - ], - "prose": "process, store, or transmit organization-controlled information using external information systems." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing the use of external information systems\n\nexternal information systems terms and conditions\n\nlist of types of applications accessible from external information systems\n\nmaximum security categorization for information processed, stored, or transmitted on external information systems\n\ninformation system configuration settings and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for defining terms and conditions for use of external information systems to access organizational systems\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing terms and conditions on use of external information systems" - } - ] - } - ], - "controls": [ - { - "id": "ac-20.1", - "class": "SP800-53-enhancement", - "title": "Limits On Authorized Use", - "props": [ - { - "name": "label", - "value": "AC-20(1)" - }, - { - "name": "sort-id", - "value": "ac-20.01" - } - ], - "parts": [ - { - "id": "ac-20.1_smt", - "name": "statement", - "prose": "The organization permits authorized individuals to use an external information system to access the information system or to process, store, or transmit organization-controlled information only when the organization:", - "parts": [ - { - "id": "ac-20.1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Verifies the implementation of required security controls on the external system as specified in the organization’s information security policy and security plan; or" - }, - { - "id": "ac-20.1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Retains approved information system connection or processing agreements with the organizational entity hosting the external information system." - } - ] - }, - { - "id": "ac-20.1_gdn", - "name": "guidance", - "prose": "This control enhancement recognizes that there are circumstances where individuals using external information systems (e.g., contractors, coalition partners) need to access organizational information systems. In those situations, organizations need confidence that the external information systems contain the necessary security safeguards (i.e., security controls), so as not to compromise, damage, or otherwise harm organizational information systems. Verification that the required security controls have been implemented can be achieved, for example, by third-party, independent assessments, attestations, or other means, depending on the confidence level required by organizations.", - "links": [ - { - "href": "#ca-2", - "rel": "related" - } - ] - }, - { - "id": "ac-20.1_obj", - "name": "objective", - "prose": "Determine if the organization permits authorized individuals to use an external information system to access the information system or to process, store, or transmit organization-controlled information only when the organization:", - "parts": [ - { - "id": "ac-20.1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-20(1)(a)" - } - ], - "prose": "verifies the implementation of required security controls on the external system as specified in the organization’s information security policy and security plan; or", - "links": [ - { - "href": "#ac-20.1_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ac-20.1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-20(1)(b)" - } - ], - "prose": "retains approved information system connection or processing agreements with the organizational entity hosting the external information system.", - "links": [ - { - "href": "#ac-20.1_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing the use of external information systems\n\nsecurity plan\n\ninformation system connection or processing agreements\n\naccount management documents\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing limits on use of external information systems" - } - ] - } - ] - }, - { - "id": "ac-20.2", - "class": "SP800-53-enhancement", - "title": "Portable Storage Devices", - "params": [ - { - "id": "ac-20.2_prm_1", - "select": { - "choice": [ - "restricts", - "prohibits" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "AC-20(2)" - }, - { - "name": "sort-id", - "value": "ac-20.02" - } - ], - "parts": [ - { - "id": "ac-20.2_smt", - "name": "statement", - "prose": "The organization {{ insert: param, ac-20.2_prm_1 }} the use of organization-controlled portable storage devices by authorized individuals on external information systems." - }, - { - "id": "ac-20.2_gdn", - "name": "guidance", - "prose": "Limits on the use of organization-controlled portable storage devices in external information systems include, for example, complete prohibition of the use of such devices or restrictions on how the devices may be used and under what conditions the devices may be used." - }, - { - "id": "ac-20.2_obj", - "name": "objective", - "prose": "Determine if the organization restricts or prohibits the use of organization-controlled portable storage devices by authorized individuals on external information systems." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing the use of external information systems\n\nsecurity plan\n\ninformation system configuration settings and associated documentation\n\ninformation system connection or processing agreements\n\naccount management documents\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for restricting or prohibiting use of organization-controlled storage devices on external information systems\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing restrictions on use of portable storage devices" - } - ] - } - ] - }, - { - "id": "ac-20.3", - "class": "SP800-53-enhancement", - "title": "Non-organizationally Owned Systems / Components / Devices", - "params": [ - { - "id": "ac-20.3_prm_1", - "select": { - "choice": [ - "restricts", - "prohibits" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "AC-20(3)" - }, - { - "name": "sort-id", - "value": "ac-20.03" - } - ], - "parts": [ - { - "id": "ac-20.3_smt", - "name": "statement", - "prose": "The organization {{ insert: param, ac-20.3_prm_1 }} the use of non-organizationally owned information systems, system components, or devices to process, store, or transmit organizational information." - }, - { - "id": "ac-20.3_gdn", - "name": "guidance", - "prose": "Non-organizationally owned devices include devices owned by other organizations (e.g., federal/state agencies, contractors) and personally owned devices. There are risks to using non-organizationally owned devices. In some cases, the risk is sufficiently high as to prohibit such use. In other cases, it may be such that the use of non-organizationally owned devices is allowed but restricted in some way. Restrictions include, for example: (i) requiring the implementation of organization-approved security controls prior to authorizing such connections; (ii) limiting access to certain types of information, services, or applications; (iii) using virtualization techniques to limit processing and storage activities to servers or other system components provisioned by the organization; and (iv) agreeing to terms and conditions for usage. For personally owned devices, organizations consult with the Office of the General Counsel regarding legal issues associated with using such devices in operational environments, including, for example, requirements for conducting forensic analyses during investigations after an incident." - }, - { - "id": "ac-20.3_obj", - "name": "objective", - "prose": "Determine if the organization restricts or prohibits the use of non-organizationally owned information systems, system components, or devices to process, store, or transmit organizational information." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing the use of external information systems\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system connection or processing agreements\n\naccount management documents\n\ninformation system audit records, other relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for restricting or prohibiting use of non-organizationally owned information systems, system components, or devices\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing restrictions on the use of non-organizationally owned systems/components/devices" - } - ] - } - ] - }, - { - "id": "ac-20.4", - "class": "SP800-53-enhancement", - "title": "Network Accessible Storage Devices", - "params": [ - { - "id": "ac-20.4_prm_1", - "label": "organization-defined network accessible storage devices" - } - ], - "props": [ - { - "name": "label", - "value": "AC-20(4)" - }, - { - "name": "sort-id", - "value": "ac-20.04" - } - ], - "parts": [ - { - "id": "ac-20.4_smt", - "name": "statement", - "prose": "The organization prohibits the use of {{ insert: param, ac-20.4_prm_1 }} in external information systems." - }, - { - "id": "ac-20.4_gdn", - "name": "guidance", - "prose": "Network accessible storage devices in external information systems include, for example, online storage devices in public, hybrid, or community cloud-based systems." - }, - { - "id": "ac-20.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-20.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-20(4)[1]" - } - ], - "prose": "defines network accessible storage devices to be prohibited from use in external information systems; and" - }, - { - "id": "ac-20.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-20(4)[2]" - } - ], - "prose": "prohibits the use of organization-defined network accessible storage devices in external information systems." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing use of network accessible storage devices in external information systems\n\nsecurity plan, information system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system connection or processing agreements\n\nlist of network accessible storage devices prohibited from use in external information systems\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for prohibiting use of network accessible storage devices in external information systems\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms prohibiting the use of network accessible storage devices in external information systems" - } - ] - } - ] - } - ] - }, - { - "id": "ac-21", - "class": "SP800-53", - "title": "Information Sharing", - "params": [ - { - "id": "ac-21_prm_1", - "label": "organization-defined information sharing circumstances where user discretion is required" - }, - { - "id": "ac-21_prm_2", - "label": "organization-defined automated mechanisms or manual processes" - } - ], - "props": [ - { - "name": "label", - "value": "AC-21" - }, - { - "name": "sort-id", - "value": "ac-21" - } - ], - "parts": [ - { - "id": "ac-21_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ac-21_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Facilitates information sharing by enabling authorized users to determine whether access authorizations assigned to the sharing partner match the access restrictions on the information for {{ insert: param, ac-21_prm_1 }}; and" - }, - { - "id": "ac-21_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Employs {{ insert: param, ac-21_prm_2 }} to assist users in making information sharing/collaboration decisions." - } - ] - }, - { - "id": "ac-21_gdn", - "name": "guidance", - "prose": "This control applies to information that may be restricted in some manner (e.g., privileged medical information, contract-sensitive information, proprietary information, personally identifiable information, classified information related to special access programs or compartments) based on some formal or administrative determination. Depending on the particular information-sharing circumstances, sharing partners may be defined at the individual, group, or organizational level. Information may be defined by content, type, security category, or special access program/compartment.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - } - ] - }, - { - "id": "ac-21_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-21.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-21(a)" - } - ], - "parts": [ - { - "id": "ac-21.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-21(a)[1]" - } - ], - "prose": "defines information sharing circumstances where user discretion is required;" - }, - { - "id": "ac-21.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-21(a)[2]" - } - ], - "prose": "facilitates information sharing by enabling authorized users to determine whether access authorizations assigned to the sharing partner match the access restrictions on the information for organization-defined information sharing circumstances;" - } - ] - }, - { - "id": "ac-21.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-21(b)" - } - ], - "parts": [ - { - "id": "ac-21.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-21(b)[1]" - } - ], - "prose": "defines automated mechanisms or manual processes to be employed to assist users in making information sharing/collaboration decisions; and" - }, - { - "id": "ac-21.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-21(b)[2]" - } - ], - "prose": "employs organization-defined automated mechanisms or manual processes to assist users in making information sharing/collaboration decisions." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing user-based collaboration and information sharing (including restrictions)\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of users authorized to make information sharing/collaboration decisions\n\nlist of information sharing circumstances requiring user discretion\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel responsible for making information sharing/collaboration decisions\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms or manual process implementing access authorizations supporting information sharing/user collaboration decisions" - } - ] - } - ], - "controls": [ - { - "id": "ac-21.1", - "class": "SP800-53-enhancement", - "title": "Automated Decision Support", - "props": [ - { - "name": "label", - "value": "AC-21(1)" - }, - { - "name": "sort-id", - "value": "ac-21.01" - } - ], - "parts": [ - { - "id": "ac-21.1_smt", - "name": "statement", - "prose": "The information system enforces information-sharing decisions by authorized users based on access authorizations of sharing partners and access restrictions on information to be shared." - }, - { - "id": "ac-21.1_obj", - "name": "objective", - "prose": "Determine if the information system enforces information-sharing decisions by authorized users based on:", - "parts": [ - { - "id": "ac-21.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-21(1)[1]" - } - ], - "prose": "access authorizations of sharing partners; and" - }, - { - "id": "ac-21.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-21(1)[2]" - } - ], - "prose": "access restrictions on information to be shared." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing user-based collaboration and information sharing (including restrictions)\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsystem-generated list of users authorized to make information sharing/collaboration decisions\n\nsystem-generated list of sharing partners and access authorizations\n\nsystem-generated list of access restrictions regarding information to be shared\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing access authorizations supporting information sharing/user collaboration decisions" - } - ] - } - ] - }, - { - "id": "ac-21.2", - "class": "SP800-53-enhancement", - "title": "Information Search and Retrieval", - "params": [ - { - "id": "ac-21.2_prm_1", - "label": "organization-defined information sharing restrictions" - } - ], - "props": [ - { - "name": "label", - "value": "AC-21(2)" - }, - { - "name": "sort-id", - "value": "ac-21.02" - } - ], - "parts": [ - { - "id": "ac-21.2_smt", - "name": "statement", - "prose": "The information system implements information search and retrieval services that enforce {{ insert: param, ac-21.2_prm_1 }}." - }, - { - "id": "ac-21.2_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-21.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-21(2)[1]" - } - ], - "prose": "the organization defines information sharing restrictions to be enforced through information search and retrieval services; and" - }, - { - "id": "ac-21.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-21(2)[2]" - } - ], - "prose": "the information system implements information search and retrieval services that enforce organization-defined information sharing restrictions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing user-based collaboration and information sharing (including restrictions)\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsystem-generated list of access restrictions regarding information to be shared\n\ninformation search and retrieval records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with access enforcement responsibilities for information system search and retrieval services\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system search and retrieval services enforcing information sharing restrictions" - } - ] - } - ] - } - ] - }, - { - "id": "ac-22", - "class": "SP800-53", - "title": "Publicly Accessible Content", - "params": [ - { - "id": "ac-22_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "AC-22" - }, - { - "name": "sort-id", - "value": "ac-22" - } - ], - "parts": [ - { - "id": "ac-22_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ac-22_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Designates individuals authorized to post information onto a publicly accessible information system;" - }, - { - "id": "ac-22_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Trains authorized individuals to ensure that publicly accessible information does not contain nonpublic information;" - }, - { - "id": "ac-22_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Reviews the proposed content of information prior to posting onto the publicly accessible information system to ensure that nonpublic information is not included; and" - }, - { - "id": "ac-22_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Reviews the content on the publicly accessible information system for nonpublic information {{ insert: param, ac-22_prm_1 }} and removes such information, if discovered." - } - ] - }, - { - "id": "ac-22_gdn", - "name": "guidance", - "prose": "In accordance with federal laws, Executive Orders, directives, policies, regulations, standards, and/or guidance, the general public is not authorized access to nonpublic information (e.g., information protected under the Privacy Act and proprietary information). This control addresses information systems that are controlled by the organization and accessible to the general public, typically without identification or authentication. The posting of information on non-organization information systems is covered by organizational policy.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#au-13", - "rel": "related" - } - ] - }, - { - "id": "ac-22_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-22.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-22(a)" - } - ], - "prose": "designates individuals authorized to post information onto a publicly accessible information system;" - }, - { - "id": "ac-22.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-22(b)" - } - ], - "prose": "trains authorized individuals to ensure that publicly accessible information does not contain nonpublic information;" - }, - { - "id": "ac-22.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-22(c)" - } - ], - "prose": "reviews the proposed content of information prior to posting onto the publicly accessible information system to ensure that nonpublic information is not included;" - }, - { - "id": "ac-22.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-22(d)" - } - ], - "parts": [ - { - "id": "ac-22.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-22(d)[1]" - } - ], - "prose": "defines the frequency to review the content on the publicly accessible information system for nonpublic information;" - }, - { - "id": "ac-22.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-22(d)[2]" - } - ], - "prose": "reviews the content on the publicly accessible information system for nonpublic information with the organization-defined frequency; and" - }, - { - "id": "ac-22.d_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-22(d)[3]" - } - ], - "prose": "removes nonpublic information from the publicly accessible information system, if discovered." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing publicly accessible content\n\nlist of users authorized to post publicly accessible content on organizational information systems\n\ntraining materials and/or records\n\nrecords of publicly accessible information reviews\n\nrecords of response to nonpublic information on public websites\n\nsystem audit logs\n\nsecurity awareness training records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for managing publicly accessible information posted on organizational information systems\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing management of publicly accessible content" - } - ] - } - ] - }, - { - "id": "ac-23", - "class": "SP800-53", - "title": "Data Mining Protection", - "params": [ - { - "id": "ac-23_prm_1", - "label": "organization-defined data mining prevention and detection techniques" - }, - { - "id": "ac-23_prm_2", - "label": "organization-defined data storage objects" - } - ], - "props": [ - { - "name": "label", - "value": "AC-23" - }, - { - "name": "sort-id", - "value": "ac-23" - } - ], - "parts": [ - { - "id": "ac-23_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, ac-23_prm_1 }} for {{ insert: param, ac-23_prm_2 }} to adequately detect and protect against data mining." - }, - { - "id": "ac-23_gdn", - "name": "guidance", - "prose": "Data storage objects include, for example, databases, database records, and database fields. Data mining prevention and detection techniques include, for example: (i) limiting the types of responses provided to database queries; (ii) limiting the number/frequency of database queries to increase the work factor needed to determine the contents of such databases; and (iii) notifying organizational personnel when atypical database queries or accesses occur. This control focuses on the protection of organizational information from data mining while such information resides in organizational data stores. In contrast, AU-13 focuses on monitoring for organizational information that may have been mined or otherwise obtained from data stores and is now available as open source information residing on external sites, for example, through social networking or social media websites." - }, - { - "id": "ac-23_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-23_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-23[1]" - } - ], - "prose": "defines data mining prevention and detection techniques to be employed for organization-defined storage objects to adequately detect and protect against data mining;" - }, - { - "id": "ac-23_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-23[2]" - } - ], - "prose": "defines data storage objects to be protected from data mining; and" - }, - { - "id": "ac-23_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-23[3]" - } - ], - "prose": "employs organization-defined data mining prevention and detection techniques for organization-defined data storage objects to adequately detect and protect against data mining." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing data mining techniques\n\nprocedures addressing protection of data storage objects against data mining\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit logs\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for implementing data mining detection and prevention techniques for data storage objects\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing data mining prevention and detection" - } - ] - } - ] - }, - { - "id": "ac-24", - "class": "SP800-53", - "title": "Access Control Decisions", - "params": [ - { - "id": "ac-24_prm_1", - "label": "organization-defined access control decisions" - } - ], - "props": [ - { - "name": "label", - "value": "AC-24" - }, - { - "name": "sort-id", - "value": "ac-24" - } - ], - "parts": [ - { - "id": "ac-24_smt", - "name": "statement", - "prose": "The organization establishes procedures to ensure {{ insert: param, ac-24_prm_1 }} are applied to each access request prior to access enforcement." - }, - { - "id": "ac-24_gdn", - "name": "guidance", - "prose": "Access control decisions (also known as authorization decisions) occur when authorization information is applied to specific accesses. In contrast, access enforcement occurs when information systems enforce access control decisions. While it is very common to have access control decisions and access enforcement implemented by the same entity, it is not required and it is not always an optimal implementation choice. For some architectures and distributed information systems, different entities may perform access control decisions and access enforcement." - }, - { - "id": "ac-24_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ac-24_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-24[1]" - } - ], - "prose": "defines access control decisions to be applied to each access request prior to access control enforcement; and" - }, - { - "id": "ac-24_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-24[2]" - } - ], - "prose": "establishes procedures to ensure organization-defined access control decisions are applied to each access request prior to access control enforcement." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing access control decisions\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for establishing procedures regarding access control decisions to the information system\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms applying established access control decisions and procedures" - } - ] - } - ], - "controls": [ - { - "id": "ac-24.1", - "class": "SP800-53-enhancement", - "title": "Transmit Access Authorization Information", - "params": [ - { - "id": "ac-24.1_prm_1", - "label": "organization-defined access authorization information" - }, - { - "id": "ac-24.1_prm_2", - "label": "organization-defined security safeguards" - }, - { - "id": "ac-24.1_prm_3", - "label": "organization-defined information systems" - } - ], - "props": [ - { - "name": "label", - "value": "AC-24(1)" - }, - { - "name": "sort-id", - "value": "ac-24.01" - } - ], - "parts": [ - { - "id": "ac-24.1_smt", - "name": "statement", - "prose": "The information system transmits {{ insert: param, ac-24.1_prm_1 }} using {{ insert: param, ac-24.1_prm_2 }} to {{ insert: param, ac-24.1_prm_3 }} that enforce access control decisions." - }, - { - "id": "ac-24.1_gdn", - "name": "guidance", - "prose": "In distributed information systems, authorization processes and access control decisions may occur in separate parts of the systems. In such instances, authorization information is transmitted securely so timely access control decisions can be enforced at the appropriate locations. To support the access control decisions, it may be necessary to transmit as part of the access authorization information, supporting security attributes. This is due to the fact that in distributed information systems, there are various access control decisions that need to be made and different entities (e.g., services) make these decisions in a serial fashion, each requiring some security attributes to make the decisions. Protecting access authorization information (i.e., access control decisions) ensures that such information cannot be altered, spoofed, or otherwise compromised during transmission." - }, - { - "id": "ac-24.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-24.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-24(1)[1]" - } - ], - "prose": "the organization defines access authorization information that the information system transmits to organization-defined information systems that enforce access control decisions;" - }, - { - "id": "ac-24.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-24(1)[2]" - } - ], - "prose": "the organization defines security safeguards to be used when the information system transmits organization-defined authorization information to organization-defined information systems that enforce access control decisions;" - }, - { - "id": "ac-24.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-24(1)[3]" - } - ], - "prose": "the organization defines the information systems that enforce access control decisions; and" - }, - { - "id": "ac-24.1_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-24(1)[4]" - } - ], - "prose": "the information system transmits organization-defined access authorization information using organization-defined security safeguards to organization-defined information systems that enforce access control decisions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing access enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with access enforcement responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing access enforcement functions" - } - ] - } - ] - }, - { - "id": "ac-24.2", - "class": "SP800-53-enhancement", - "title": "No User or Process Identity", - "params": [ - { - "id": "ac-24.2_prm_1", - "label": "organization-defined security attributes" - } - ], - "props": [ - { - "name": "label", - "value": "AC-24(2)" - }, - { - "name": "sort-id", - "value": "ac-24.02" - } - ], - "parts": [ - { - "id": "ac-24.2_smt", - "name": "statement", - "prose": "The information system enforces access control decisions based on {{ insert: param, ac-24.2_prm_1 }} that do not include the identity of the user or process acting on behalf of the user." - }, - { - "id": "ac-24.2_gdn", - "name": "guidance", - "prose": "In certain situations, it is important that access control decisions can be made without information regarding the identity of the users issuing the requests. These are generally instances where preserving individual privacy is of paramount importance. In other situations, user identification information is simply not needed for access control decisions and, especially in the case of distributed information systems, transmitting such information with the needed degree of assurance may be very expensive or difficult to accomplish." - }, - { - "id": "ac-24.2_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-24.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-24(2)[1]" - } - ], - "prose": "the organization defines security attributes that support access control decisions that do not include the identity of the user or processes acting on behalf of the user; and" - }, - { - "id": "ac-24.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-24(2)[2]" - } - ], - "prose": "the information system enforces access control decisions based on organization-defined security attributes that do not include the identity of the user or process acting on behalf of the user." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing access enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with access enforcement responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing access enforcement functions" - } - ] - } - ] - } - ] - }, - { - "id": "ac-25", - "class": "SP800-53", - "title": "Reference Monitor", - "params": [ - { - "id": "ac-25_prm_1", - "label": "organization-defined access control policies" - } - ], - "props": [ - { - "name": "label", - "value": "AC-25" - }, - { - "name": "sort-id", - "value": "ac-25" - } - ], - "parts": [ - { - "id": "ac-25_smt", - "name": "statement", - "prose": "The information system implements a reference monitor for {{ insert: param, ac-25_prm_1 }} that is tamperproof, always invoked, and small enough to be subject to analysis and testing, the completeness of which can be assured." - }, - { - "id": "ac-25_gdn", - "name": "guidance", - "prose": "Information is represented internally within information systems using abstractions known as data structures. Internal data structures can represent different types of entities, both active and passive. Active entities, also known as subjects, are typically associated with individuals, devices, or processes acting on behalf of individuals. Passive entities, also known as objects, are typically associated with data structures such as records, buffers, tables, files, inter-process pipes, and communications ports. Reference monitors typically enforce mandatory access control policies—a type of access control that restricts access to objects based on the identity of subjects or groups to which the subjects belong. The access controls are mandatory because subjects with certain privileges (i.e., access permissions) are restricted from passing those privileges on to any other subjects, either directly or indirectly—that is, the information system strictly enforces the access control policy based on the rule set established by the policy. The tamperproof property of the reference monitor prevents adversaries from compromising the functioning of the mechanism. The always invoked property prevents adversaries from bypassing the mechanism and hence violating the security policy. The smallness property helps to ensure the completeness in the analysis and testing of the mechanism to detect weaknesses or deficiencies (i.e., latent flaws) that would prevent the enforcement of the security policy.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-16", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - }, - { - "href": "#sc-39", - "rel": "related" - } - ] - }, - { - "id": "ac-25_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ac-25_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-25[1]" - } - ], - "prose": "the organization defines access control policies for which the information system implements a reference monitor to enforce such policies; and" - }, - { - "id": "ac-25_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AC-25[2]" - } - ], - "prose": "the information system implements a reference monitor for organization-defined access control policies that is tamperproof, always invoked, and small enough to be subject to analysis and testing, the completeness of which can be assured." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing access enforcement\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with access enforcement responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing access enforcement functions" - } - ] - } - ] - } - ] - }, - { - "id": "at", - "class": "family", - "title": "Awareness and Training", - "controls": [ - { - "id": "at-1", - "class": "SP800-53", - "title": "Security Awareness and Training Policy and Procedures", - "params": [ - { - "id": "at-1_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "at-1_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "at-1_prm_3", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "AT-1" - }, - { - "name": "sort-id", - "value": "at-01" - } - ], - "links": [ - { - "href": "#5c201b63-0768-417b-ac22-3f014e3941b2", - "rel": "reference" - }, - { - "href": "#825438c3-248d-4e30-a51e-246473ce6ada", - "rel": "reference" - }, - { - "href": "#e12b5738-de74-4fb3-8317-a3995a8a1898", - "rel": "reference" - }, - { - "href": "#9cb3d8fe-2127-48ba-821e-cdd2d7aee921", - "rel": "reference" - } - ], - "parts": [ - { - "id": "at-1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "at-1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops, documents, and disseminates to {{ insert: param, at-1_prm_1 }}:", - "parts": [ - { - "id": "at-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "A security awareness and training policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "at-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the security awareness and training policy and associated security awareness and training controls; and" - } - ] - }, - { - "id": "at-1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the current:", - "parts": [ - { - "id": "at-1_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Security awareness and training policy {{ insert: param, at-1_prm_2 }}; and" - }, - { - "id": "at-1_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Security awareness and training procedures {{ insert: param, at-1_prm_3 }}." - } - ] - } - ] - }, - { - "id": "at-1_gdn", - "name": "guidance", - "prose": "This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the AT family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures.", - "links": [ - { - "href": "#pm-9", - "rel": "related" - } - ] - }, - { - "id": "at-1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "at-1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(a)" - } - ], - "parts": [ - { - "id": "at-1.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(a)(1)" - } - ], - "parts": [ - { - "id": "at-1.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(a)(1)[1]" - } - ], - "prose": "develops and documents an security awareness and training policy that addresses:", - "parts": [ - { - "id": "at-1.a.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(a)(1)[1][a]" - } - ], - "prose": "purpose;" - }, - { - "id": "at-1.a.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(a)(1)[1][b]" - } - ], - "prose": "scope;" - }, - { - "id": "at-1.a.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(a)(1)[1][c]" - } - ], - "prose": "roles;" - }, - { - "id": "at-1.a.1_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(a)(1)[1][d]" - } - ], - "prose": "responsibilities;" - }, - { - "id": "at-1.a.1_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(a)(1)[1][e]" - } - ], - "prose": "management commitment;" - }, - { - "id": "at-1.a.1_obj.1.f", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(a)(1)[1][f]" - } - ], - "prose": "coordination among organizational entities;" - }, - { - "id": "at-1.a.1_obj.1.g", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(a)(1)[1][g]" - } - ], - "prose": "compliance;" - } - ] - }, - { - "id": "at-1.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(a)(1)[2]" - } - ], - "prose": "defines personnel or roles to whom the security awareness and training policy are to be disseminated;" - }, - { - "id": "at-1.a.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(a)(1)[3]" - } - ], - "prose": "disseminates the security awareness and training policy to organization-defined personnel or roles;" - } - ] - }, - { - "id": "at-1.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(a)(2)" - } - ], - "parts": [ - { - "id": "at-1.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(a)(2)[1]" - } - ], - "prose": "develops and documents procedures to facilitate the implementation of the security awareness and training policy and associated awareness and training controls;" - }, - { - "id": "at-1.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(a)(2)[2]" - } - ], - "prose": "defines personnel or roles to whom the procedures are to be disseminated;" - }, - { - "id": "at-1.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(a)(2)[3]" - } - ], - "prose": "disseminates the procedures to organization-defined personnel or roles;" - } - ] - } - ] - }, - { - "id": "at-1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(b)" - } - ], - "parts": [ - { - "id": "at-1.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(b)(1)" - } - ], - "parts": [ - { - "id": "at-1.b.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(b)(1)[1]" - } - ], - "prose": "defines the frequency to review and update the current security awareness and training policy;" - }, - { - "id": "at-1.b.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(b)(1)[2]" - } - ], - "prose": "reviews and updates the current security awareness and training policy with the organization-defined frequency;" - } - ] - }, - { - "id": "at-1.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(b)(2)" - } - ], - "parts": [ - { - "id": "at-1.b.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(b)(2)[1]" - } - ], - "prose": "defines the frequency to review and update the current security awareness and training procedures; and" - }, - { - "id": "at-1.b.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-1(b)(2)[2]" - } - ], - "prose": "reviews and updates the current security awareness and training procedures with the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security awareness and training policy and procedures\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security awareness and training responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "at-2", - "class": "SP800-53", - "title": "Security Awareness Training", - "params": [ - { - "id": "at-2_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "AT-2" - }, - { - "name": "sort-id", - "value": "at-02" - } - ], - "links": [ - { - "href": "#bb61234b-46c3-4211-8c2b-9869222a720d", - "rel": "reference" - }, - { - "href": "#c5034e0c-eba6-4ecd-a541-79f0678f4ba4", - "rel": "reference" - }, - { - "href": "#e12b5738-de74-4fb3-8317-a3995a8a1898", - "rel": "reference" - } - ], - "parts": [ - { - "id": "at-2_smt", - "name": "statement", - "prose": "The organization provides basic security awareness training to information system users (including managers, senior executives, and contractors):", - "parts": [ - { - "id": "at-2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "As part of initial training for new users;" - }, - { - "id": "at-2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "When required by information system changes; and" - }, - { - "id": "at-2_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": " {{ insert: param, at-2_prm_1 }} thereafter." - } - ] - }, - { - "id": "at-2_gdn", - "name": "guidance", - "prose": "Organizations determine the appropriate content of security awareness training and security awareness techniques based on the specific organizational requirements and the information systems to which personnel have authorized access. The content includes a basic understanding of the need for information security and user actions to maintain security and to respond to suspected security incidents. The content also addresses awareness of the need for operations security. Security awareness techniques can include, for example, displaying posters, offering supplies inscribed with security reminders, generating email advisories/notices from senior organizational officials, displaying logon screen messages, and conducting information security awareness events.", - "links": [ - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#at-4", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - } - ] - }, - { - "id": "at-2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "at-2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-2(a)" - } - ], - "prose": "provides basic security awareness training to information system users (including managers, senior executives, and contractors) as part of initial training for new users;" - }, - { - "id": "at-2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-2(b)" - } - ], - "prose": "provides basic security awareness training to information system users (including managers, senior executives, and contractors) when required by information system changes; and" - }, - { - "id": "at-2.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-2(c)" - } - ], - "parts": [ - { - "id": "at-2.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-2(c)[1]" - } - ], - "prose": "defines the frequency to provide refresher security awareness training thereafter to information system users (including managers, senior executives, and contractors); and" - }, - { - "id": "at-2.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-2(c)[2]" - } - ], - "prose": "provides refresher security awareness training to information users (including managers, senior executives, and contractors) with the organization-defined frequency." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security awareness and training policy\n\nprocedures addressing security awareness training implementation\n\nappropriate codes of federal regulations\n\nsecurity awareness training curriculum\n\nsecurity awareness training materials\n\nsecurity plan\n\ntraining records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for security awareness training\n\norganizational personnel with information security responsibilities\n\norganizational personnel comprising the general information system user community" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms managing security awareness training" - } - ] - } - ], - "controls": [ - { - "id": "at-2.1", - "class": "SP800-53-enhancement", - "title": "Practical Exercises", - "props": [ - { - "name": "label", - "value": "AT-2(1)" - }, - { - "name": "sort-id", - "value": "at-02.01" - } - ], - "parts": [ - { - "id": "at-2.1_smt", - "name": "statement", - "prose": "The organization includes practical exercises in security awareness training that simulate actual cyber attacks." - }, - { - "id": "at-2.1_gdn", - "name": "guidance", - "prose": "Practical exercises may include, for example, no-notice social engineering attempts to collect information, gain unauthorized access, or simulate the adverse impact of opening malicious email attachments or invoking, via spear phishing attacks, malicious web links.", - "links": [ - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cp-4", - "rel": "related" - }, - { - "href": "#ir-3", - "rel": "related" - } - ] - }, - { - "id": "at-2.1_obj", - "name": "objective", - "prose": "Determine if the organization includes practical exercises in security awareness training that simulate actual cyber attacks." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security awareness and training policy\n\nprocedures addressing security awareness training implementation\n\nsecurity awareness training curriculum\n\nsecurity awareness training materials\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel that participate in security awareness training\n\norganizational personnel with responsibilities for security awareness training\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing cyber attack simulations in practical exercises" - } - ] - } - ] - }, - { - "id": "at-2.2", - "class": "SP800-53-enhancement", - "title": "Insider Threat", - "props": [ - { - "name": "label", - "value": "AT-2(2)" - }, - { - "name": "sort-id", - "value": "at-02.02" - } - ], - "parts": [ - { - "id": "at-2.2_smt", - "name": "statement", - "prose": "The organization includes security awareness training on recognizing and reporting potential indicators of insider threat." - }, - { - "id": "at-2.2_gdn", - "name": "guidance", - "prose": "Potential indicators and possible precursors of insider threat can include behaviors such as inordinate, long-term job dissatisfaction, attempts to gain access to information not required for job performance, unexplained access to financial resources, bullying or sexual harassment of fellow employees, workplace violence, and other serious violations of organizational policies, procedures, directives, rules, or practices. Security awareness training includes how to communicate employee and management concerns regarding potential indicators of insider threat through appropriate organizational channels in accordance with established organizational policies and procedures.", - "links": [ - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#pm-12", - "rel": "related" - }, - { - "href": "#ps-3", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - } - ] - }, - { - "id": "at-2.2_obj", - "name": "objective", - "prose": "Determine if the organization includes security awareness training on recognizing and reporting potential indicators of insider threat." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security awareness and training policy\n\nprocedures addressing security awareness training implementation\n\nsecurity awareness training curriculum\n\nsecurity awareness training materials\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel that participate in security awareness training\n\norganizational personnel with responsibilities for basic security awareness training\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "at-3", - "class": "SP800-53", - "title": "Role-based Security Training", - "params": [ - { - "id": "at-3_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "AT-3" - }, - { - "name": "sort-id", - "value": "at-03" - } - ], - "links": [ - { - "href": "#bb61234b-46c3-4211-8c2b-9869222a720d", - "rel": "reference" - }, - { - "href": "#825438c3-248d-4e30-a51e-246473ce6ada", - "rel": "reference" - }, - { - "href": "#e12b5738-de74-4fb3-8317-a3995a8a1898", - "rel": "reference" - } - ], - "parts": [ - { - "id": "at-3_smt", - "name": "statement", - "prose": "The organization provides role-based security training to personnel with assigned security roles and responsibilities:", - "parts": [ - { - "id": "at-3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Before authorizing access to the information system or performing assigned duties;" - }, - { - "id": "at-3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "When required by information system changes; and" - }, - { - "id": "at-3_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": " {{ insert: param, at-3_prm_1 }} thereafter." - } - ] - }, - { - "id": "at-3_gdn", - "name": "guidance", - "prose": "Organizations determine the appropriate content of security training based on the assigned roles and responsibilities of individuals and the specific security requirements of organizations and the information systems to which personnel have authorized access. In addition, organizations provide enterprise architects, information system developers, software developers, acquisition/procurement officials, information system managers, system/network administrators, personnel conducting configuration management and auditing activities, personnel performing independent verification and validation activities, security control assessors, and other personnel having access to system-level software, adequate security-related technical training specifically tailored for their assigned duties. Comprehensive role-based training addresses management, operational, and technical roles and responsibilities covering physical, personnel, and technical safeguards and countermeasures. Such training can include for example, policies, procedures, tools, and artifacts for the organizational security roles defined. Organizations also provide the training necessary for individuals to carry out their responsibilities related to operations and supply chain security within the context of organizational information security programs. Role-based security training also applies to contractors providing services to federal agencies.", - "links": [ - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-4", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#ps-7", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - }, - { - "href": "#sa-12", - "rel": "related" - }, - { - "href": "#sa-16", - "rel": "related" - } - ] - }, - { - "id": "at-3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "at-3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-3(a)" - } - ], - "prose": "provides role-based security training to personnel with assigned security roles and responsibilities before authorizing access to the information system or performing assigned duties;" - }, - { - "id": "at-3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-3(b)" - } - ], - "prose": "provides role-based security training to personnel with assigned security roles and responsibilities when required by information system changes; and" - }, - { - "id": "at-3.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-3(c)" - } - ], - "parts": [ - { - "id": "at-3.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-3(c)[1]" - } - ], - "prose": "defines the frequency to provide refresher role-based security training thereafter to personnel with assigned security roles and responsibilities; and" - }, - { - "id": "at-3.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-3(c)[2]" - } - ], - "prose": "provides refresher role-based security training to personnel with assigned security roles and responsibilities with the organization-defined frequency." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security awareness and training policy\n\nprocedures addressing security training implementation\n\ncodes of federal regulations\n\nsecurity training curriculum\n\nsecurity training materials\n\nsecurity plan\n\ntraining records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for role-based security training\n\norganizational personnel with assigned information system security roles and responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms managing role-based security training" - } - ] - } - ], - "controls": [ - { - "id": "at-3.1", - "class": "SP800-53-enhancement", - "title": "Environmental Controls", - "params": [ - { - "id": "at-3.1_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "at-3.1_prm_2", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "AT-3(1)" - }, - { - "name": "sort-id", - "value": "at-03.01" - } - ], - "parts": [ - { - "id": "at-3.1_smt", - "name": "statement", - "prose": "The organization provides {{ insert: param, at-3.1_prm_1 }} with initial and {{ insert: param, at-3.1_prm_2 }} training in the employment and operation of environmental controls." - }, - { - "id": "at-3.1_gdn", - "name": "guidance", - "prose": "Environmental controls include, for example, fire suppression and detection devices/systems, sprinkler systems, handheld fire extinguishers, fixed fire hoses, smoke detectors, temperature/humidity, HVAC, and power within the facility. Organizations identify personnel with specific roles and responsibilities associated with environmental controls requiring specialized training.", - "links": [ - { - "href": "#pe-1", - "rel": "related" - }, - { - "href": "#pe-13", - "rel": "related" - }, - { - "href": "#pe-14", - "rel": "related" - }, - { - "href": "#pe-15", - "rel": "related" - } - ] - }, - { - "id": "at-3.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "at-3.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-3(1)[1]" - } - ], - "prose": "defines personnel or roles to be provided with initial and refresher training in the employment and operation of environmental controls;" - }, - { - "id": "at-3.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-3(1)[2]" - } - ], - "prose": "provides organization-defined personnel or roles with initial and refresher training in the employment and operation of environmental controls;" - }, - { - "id": "at-3.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-3(1)[3]" - } - ], - "prose": "defines the frequency to provide refresher training in the employment and operation of environmental controls; and" - }, - { - "id": "at-3.1_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-3(1)[4]" - } - ], - "prose": "provides refresher training in the employment and operation of environmental controls with the organization-defined frequency." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security awareness and training policy\n\nprocedures addressing security training implementation\n\nsecurity training curriculum\n\nsecurity training materials\n\nsecurity plan\n\ntraining records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for role-based security training\n\norganizational personnel with responsibilities for employing and operating environmental controls" - } - ] - } - ] - }, - { - "id": "at-3.2", - "class": "SP800-53-enhancement", - "title": "Physical Security Controls", - "params": [ - { - "id": "at-3.2_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "at-3.2_prm_2", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "AT-3(2)" - }, - { - "name": "sort-id", - "value": "at-03.02" - } - ], - "parts": [ - { - "id": "at-3.2_smt", - "name": "statement", - "prose": "The organization provides {{ insert: param, at-3.2_prm_1 }} with initial and {{ insert: param, at-3.2_prm_2 }} training in the employment and operation of physical security controls." - }, - { - "id": "at-3.2_gdn", - "name": "guidance", - "prose": "Physical security controls include, for example, physical access control devices, physical intrusion alarms, monitoring/surveillance equipment, and security guards (deployment and operating procedures). Organizations identify personnel with specific roles and responsibilities associated with physical security controls requiring specialized training.", - "links": [ - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pe-4", - "rel": "related" - }, - { - "href": "#pe-5", - "rel": "related" - } - ] - }, - { - "id": "at-3.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "at-3.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-3(2)[1]" - } - ], - "prose": "defines personnel or roles to be provided with initial and refresher training in the employment and operation of physical security controls;" - }, - { - "id": "at-3.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-3(2)[2]" - } - ], - "prose": "provides organization-defined personnel or roles with initial and refresher training in the employment and operation of physical security controls;" - }, - { - "id": "at-3.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-3(2)[3]" - } - ], - "prose": "defines the frequency to provide refresher training in the employment and operation of physical security controls; and" - }, - { - "id": "at-3.2_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-3(2)[4]" - } - ], - "prose": "provides refresher training in the employment and operation of physical security controls with the organization-defined frequency." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security awareness and training policy\n\nprocedures addressing security training implementation\n\nsecurity training curriculum\n\nsecurity training materials\n\nsecurity plan\n\ntraining records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for role-based security training\n\norganizational personnel with responsibilities for employing and operating physical security controls" - } - ] - } - ] - }, - { - "id": "at-3.3", - "class": "SP800-53-enhancement", - "title": "Practical Exercises", - "props": [ - { - "name": "label", - "value": "AT-3(3)" - }, - { - "name": "sort-id", - "value": "at-03.03" - } - ], - "parts": [ - { - "id": "at-3.3_smt", - "name": "statement", - "prose": "The organization includes practical exercises in security training that reinforce training objectives." - }, - { - "id": "at-3.3_gdn", - "name": "guidance", - "prose": "Practical exercises may include, for example, security training for software developers that includes simulated cyber attacks exploiting common software vulnerabilities (e.g., buffer overflows), or spear/whale phishing attacks targeted at senior leaders/executives. These types of practical exercises help developers better understand the effects of such vulnerabilities and appreciate the need for security coding standards and processes." - }, - { - "id": "at-3.3_obj", - "name": "objective", - "prose": "Determine if the organization includes practical exercises in security training that reinforce training objectives." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security awareness and training policy\n\nprocedures addressing security awareness training implementation\n\nsecurity awareness training curriculum\n\nsecurity awareness training materials\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for role-based security training\n\norganizational personnel that participate in security awareness training" - } - ] - } - ] - }, - { - "id": "at-3.4", - "class": "SP800-53-enhancement", - "title": "Suspicious Communications and Anomalous System Behavior", - "params": [ - { - "id": "at-3.4_prm_1", - "label": "organization-defined indicators of malicious code" - } - ], - "props": [ - { - "name": "label", - "value": "AT-3(4)" - }, - { - "name": "sort-id", - "value": "at-03.04" - } - ], - "parts": [ - { - "id": "at-3.4_smt", - "name": "statement", - "prose": "The organization provides training to its personnel on {{ insert: param, at-3.4_prm_1 }} to recognize suspicious communications and anomalous behavior in organizational information systems." - }, - { - "id": "at-3.4_gdn", - "name": "guidance", - "prose": "A well-trained workforce provides another organizational safeguard that can be employed as part of a defense-in-depth strategy to protect organizations against malicious code coming in to organizations via email or the web applications. Personnel are trained to look for indications of potentially suspicious email (e.g., receiving an unexpected email, receiving an email containing strange or poor grammar, or receiving an email from an unfamiliar sender but who appears to be from a known sponsor or contractor). Personnel are also trained on how to respond to such suspicious email or web communications (e.g., not opening attachments, not clicking on embedded web links, and checking the source of email addresses). For this process to work effectively, all organizational personnel are trained and made aware of what constitutes suspicious communications. Training personnel on how to recognize anomalous behaviors in organizational information systems can potentially provide early warning for the presence of malicious code. Recognition of such anomalous behavior by organizational personnel can supplement automated malicious code detection and protection tools and systems employed by organizations." - }, - { - "id": "at-3.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "at-3.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-3(4)[1]" - } - ], - "prose": "defines indicators of malicious code; and" - }, - { - "id": "at-3.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-3(4)[2]" - } - ], - "prose": "provides training to its personnel on organization-defined indicators of malicious code to recognize suspicious communications and anomalous behavior in organizational information systems." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security awareness and training policy\n\nprocedures addressing security training implementation\n\nsecurity training curriculum\n\nsecurity training materials\n\nsecurity plan\n\ntraining records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for role-based security training\n\norganizational personnel that participate in security awareness training" - } - ] - } - ] - } - ] - }, - { - "id": "at-4", - "class": "SP800-53", - "title": "Security Training Records", - "params": [ - { - "id": "at-4_prm_1", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "AT-4" - }, - { - "name": "sort-id", - "value": "at-04" - } - ], - "parts": [ - { - "id": "at-4_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "at-4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Documents and monitors individual information system security training activities including basic security awareness training and specific information system security training; and" - }, - { - "id": "at-4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Retains individual training records for {{ insert: param, at-4_prm_1 }}." - } - ] - }, - { - "id": "at-4_gdn", - "name": "guidance", - "prose": "Documentation for specialized training may be maintained by individual supervisors at the option of the organization.", - "links": [ - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#pm-14", - "rel": "related" - } - ] - }, - { - "id": "at-4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "at-4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-4(a)" - } - ], - "parts": [ - { - "id": "at-4.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-4(a)[1]" - } - ], - "prose": "documents individual information system security training activities including:", - "parts": [ - { - "id": "at-4.a_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-4(a)[1][a]" - } - ], - "prose": "basic security awareness training;" - }, - { - "id": "at-4.a_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-4(a)[1][b]" - } - ], - "prose": "specific role-based information system security training;" - } - ] - }, - { - "id": "at-4.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-4(a)[2]" - } - ], - "prose": "monitors individual information system security training activities including:", - "parts": [ - { - "id": "at-4.a_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-4(a)[2][a]" - } - ], - "prose": "basic security awareness training;" - }, - { - "id": "at-4.a_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-4(a)[2][b]" - } - ], - "prose": "specific role-based information system security training;" - } - ] - } - ] - }, - { - "id": "at-4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-4(b)" - } - ], - "parts": [ - { - "id": "at-4.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-4(b)[1]" - } - ], - "prose": "defines a time period to retain individual training records; and" - }, - { - "id": "at-4.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AT-4(b)[2]" - } - ], - "prose": "retains individual training records for the organization-defined time period." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security awareness and training policy\n\nprocedures addressing security training records\n\nsecurity awareness and training records\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security training record retention responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting management of security training records" - } - ] - } - ] - }, - { - "id": "at-5", - "class": "SP800-53", - "title": "Contacts with Security Groups and Associations", - "props": [ - { - "name": "label", - "value": "AT-5" - }, - { - "name": "sort-id", - "value": "at-05" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#pm-15", - "rel": "incorporated-into" - } - ] - } - ] - }, - { - "id": "au", - "class": "family", - "title": "Audit and Accountability", - "controls": [ - { - "id": "au-1", - "class": "SP800-53", - "title": "Audit and Accountability Policy and Procedures", - "params": [ - { - "id": "au-1_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "au-1_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "au-1_prm_3", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "AU-1" - }, - { - "name": "sort-id", - "value": "au-01" - } - ], - "links": [ - { - "href": "#5c201b63-0768-417b-ac22-3f014e3941b2", - "rel": "reference" - }, - { - "href": "#9cb3d8fe-2127-48ba-821e-cdd2d7aee921", - "rel": "reference" - } - ], - "parts": [ - { - "id": "au-1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "au-1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops, documents, and disseminates to {{ insert: param, au-1_prm_1 }}:", - "parts": [ - { - "id": "au-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "An audit and accountability policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "au-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the audit and accountability policy and associated audit and accountability controls; and" - } - ] - }, - { - "id": "au-1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the current:", - "parts": [ - { - "id": "au-1_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Audit and accountability policy {{ insert: param, au-1_prm_2 }}; and" - }, - { - "id": "au-1_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Audit and accountability procedures {{ insert: param, au-1_prm_3 }}." - } - ] - } - ] - }, - { - "id": "au-1_gdn", - "name": "guidance", - "prose": "This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the AU family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures.", - "links": [ - { - "href": "#pm-9", - "rel": "related" - } - ] - }, - { - "id": "au-1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "au-1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(a)" - } - ], - "parts": [ - { - "id": "au-1.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(a)(1)" - } - ], - "parts": [ - { - "id": "au-1.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(a)(1)[1]" - } - ], - "prose": "develops and documents an audit and accountability policy that addresses:", - "parts": [ - { - "id": "au-1.a.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(a)(1)[1][a]" - } - ], - "prose": "purpose;" - }, - { - "id": "au-1.a.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(a)(1)[1][b]" - } - ], - "prose": "scope;" - }, - { - "id": "au-1.a.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(a)(1)[1][c]" - } - ], - "prose": "roles;" - }, - { - "id": "au-1.a.1_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(a)(1)[1][d]" - } - ], - "prose": "responsibilities;" - }, - { - "id": "au-1.a.1_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(a)(1)[1][e]" - } - ], - "prose": "management commitment;" - }, - { - "id": "au-1.a.1_obj.1.f", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(a)(1)[1][f]" - } - ], - "prose": "coordination among organizational entities;" - }, - { - "id": "au-1.a.1_obj.1.g", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(a)(1)[1][g]" - } - ], - "prose": "compliance;" - } - ] - }, - { - "id": "au-1.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(a)(1)[2]" - } - ], - "prose": "defines personnel or roles to whom the audit and accountability policy are to be disseminated;" - }, - { - "id": "au-1.a.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(a)(1)[3]" - } - ], - "prose": "disseminates the audit and accountability policy to organization-defined personnel or roles;" - } - ] - }, - { - "id": "au-1.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(a)(2)" - } - ], - "parts": [ - { - "id": "au-1.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(a)(2)[1]" - } - ], - "prose": "develops and documents procedures to facilitate the implementation of the audit and accountability policy and associated audit and accountability controls;" - }, - { - "id": "au-1.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(a)(2)[2]" - } - ], - "prose": "defines personnel or roles to whom the procedures are to be disseminated;" - }, - { - "id": "au-1.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(a)(2)[3]" - } - ], - "prose": "disseminates the procedures to organization-defined personnel or roles;" - } - ] - } - ] - }, - { - "id": "au-1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(b)" - } - ], - "parts": [ - { - "id": "au-1.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(b)(1)" - } - ], - "parts": [ - { - "id": "au-1.b.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(b)(1)[1]" - } - ], - "prose": "defines the frequency to review and update the current audit and accountability policy;" - }, - { - "id": "au-1.b.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(b)(1)[2]" - } - ], - "prose": "reviews and updates the current audit and accountability policy with the organization-defined frequency;" - } - ] - }, - { - "id": "au-1.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(b)(2)" - } - ], - "parts": [ - { - "id": "au-1.b.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(b)(2)[1]" - } - ], - "prose": "defines the frequency to review and update the current audit and accountability procedures; and" - }, - { - "id": "au-1.b.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-1(b)(2)[2]" - } - ], - "prose": "reviews and updates the current audit and accountability procedures in accordance with the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy and procedures\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "au-2", - "class": "SP800-53", - "title": "Audit Events", - "params": [ - { - "id": "au-2_prm_1", - "label": "organization-defined auditable events" - }, - { - "id": "au-2_prm_2", - "label": "organization-defined audited events (the subset of the auditable events defined in AU-2 a.) along with the frequency of (or situation requiring) auditing for each identified event" - } - ], - "props": [ - { - "name": "label", - "value": "AU-2" - }, - { - "name": "sort-id", - "value": "au-02" - } - ], - "links": [ - { - "href": "#672fd561-b92b-4713-b9cf-6c9d9456728b", - "rel": "reference" - }, - { - "href": "#85280698-0417-489d-b214-12bb935fb939", - "rel": "reference" - } - ], - "parts": [ - { - "id": "au-2_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "au-2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Determines that the information system is capable of auditing the following events: {{ insert: param, au-2_prm_1 }};" - }, - { - "id": "au-2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Coordinates the security audit function with other organizational entities requiring audit-related information to enhance mutual support and to help guide the selection of auditable events;" - }, - { - "id": "au-2_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Provides a rationale for why the auditable events are deemed to be adequate to support after-the-fact investigations of security incidents; and" - }, - { - "id": "au-2_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Determines that the following events are to be audited within the information system: {{ insert: param, au-2_prm_2 }}." - } - ] - }, - { - "id": "au-2_gdn", - "name": "guidance", - "prose": "An event is any observable occurrence in an organizational information system. Organizations identify audit events as those events which are significant and relevant to the security of information systems and the environments in which those systems operate in order to meet specific and ongoing audit needs. Audit events can include, for example, password changes, failed logons, or failed accesses related to information systems, administrative privilege usage, PIV credential usage, or third-party credential usage. In determining the set of auditable events, organizations consider the auditing appropriate for each of the security controls to be implemented. To balance auditing requirements with other information system needs, this control also requires identifying that subset of auditable events that are audited at a given point in time. For example, organizations may determine that information systems must have the capability to log every file access both successful and unsuccessful, but not activate that capability except for specific circumstances due to the potential burden on system performance. Auditing requirements, including the need for auditable events, may be referenced in other security controls and control enhancements. Organizations also include auditable events that are required by applicable federal laws, Executive Orders, directives, policies, regulations, and standards. Audit records can be generated at various levels of abstraction, including at the packet level as information traverses the network. Selecting the appropriate level of abstraction is a critical aspect of an audit capability and can facilitate the identification of root causes to problems. Organizations consider in the definition of auditable events, the auditing necessary to cover related events such as the steps in distributed, transaction-based processes (e.g., processes that are distributed across multiple organizations) and actions that occur in service-oriented architectures.", - "links": [ - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#au-3", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "au-2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "au-2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-2(a)" - } - ], - "parts": [ - { - "id": "au-2.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-2(a)[1]" - } - ], - "prose": "defines the auditable events that the information system must be capable of auditing;" - }, - { - "id": "au-2.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-2(a)[2]" - } - ], - "prose": "determines that the information system is capable of auditing organization-defined auditable events;" - } - ] - }, - { - "id": "au-2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-2(b)" - } - ], - "prose": "coordinates the security audit function with other organizational entities requiring audit-related information to enhance mutual support and to help guide the selection of auditable events;" - }, - { - "id": "au-2.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-2(c)" - } - ], - "prose": "provides a rationale for why the auditable events are deemed to be adequate to support after-the-fact investigations of security incidents;" - }, - { - "id": "au-2.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-2(d)" - } - ], - "parts": [ - { - "id": "au-2.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-2(d)[1]" - } - ], - "prose": "defines the subset of auditable events defined in AU-2a that are to be audited within the information system;" - }, - { - "id": "au-2.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-2(d)[2]" - } - ], - "prose": "determines that the subset of auditable events defined in AU-2a are to be audited within the information system; and" - }, - { - "id": "au-2.d_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-2(d)[3]" - } - ], - "prose": "determines the frequency of (or situation requiring) auditing for each identified event." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing auditable events\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\ninformation system auditable events\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information system auditing" - } - ] - } - ], - "controls": [ - { - "id": "au-2.1", - "class": "SP800-53-enhancement", - "title": "Compilation of Audit Records from Multiple Sources", - "props": [ - { - "name": "label", - "value": "AU-2(1)" - }, - { - "name": "sort-id", - "value": "au-02.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#au-12", - "rel": "incorporated-into" - } - ] - }, - { - "id": "au-2.2", - "class": "SP800-53-enhancement", - "title": "Selection of Audit Events by Component", - "props": [ - { - "name": "label", - "value": "AU-2(2)" - }, - { - "name": "sort-id", - "value": "au-02.02" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#au-12", - "rel": "incorporated-into" - } - ] - }, - { - "id": "au-2.3", - "class": "SP800-53-enhancement", - "title": "Reviews and Updates", - "params": [ - { - "id": "au-2.3_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "AU-2(3)" - }, - { - "name": "sort-id", - "value": "au-02.03" - } - ], - "parts": [ - { - "id": "au-2.3_smt", - "name": "statement", - "prose": "The organization reviews and updates the audited events {{ insert: param, au-2.3_prm_1 }}." - }, - { - "id": "au-2.3_gdn", - "name": "guidance", - "prose": "Over time, the events that organizations believe should be audited may change. Reviewing and updating the set of audited events periodically is necessary to ensure that the current set is still necessary and sufficient." - }, - { - "id": "au-2.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "au-2.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-2(3)[1]" - } - ], - "prose": "defines the frequency to review and update the audited events; and" - }, - { - "id": "au-2.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-2(3)[2]" - } - ], - "prose": "reviews and updates the auditable events with organization-defined frequency." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing auditable events\n\nsecurity plan\n\nlist of organization-defined auditable events\n\nauditable events review and update records\n\ninformation system audit records\n\ninformation system incident reports\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting review and update of auditable events" - } - ] - } - ] - }, - { - "id": "au-2.4", - "class": "SP800-53-enhancement", - "title": "Privileged Functions", - "props": [ - { - "name": "label", - "value": "AU-2(4)" - }, - { - "name": "sort-id", - "value": "au-02.04" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#ac-6.9", - "rel": "incorporated-into" - } - ] - } - ] - }, - { - "id": "au-3", - "class": "SP800-53", - "title": "Content of Audit Records", - "props": [ - { - "name": "label", - "value": "AU-3" - }, - { - "name": "sort-id", - "value": "au-03" - } - ], - "parts": [ - { - "id": "au-3_smt", - "name": "statement", - "prose": "The information system generates audit records containing information that establishes what type of event occurred, when the event occurred, where the event occurred, the source of the event, the outcome of the event, and the identity of any individuals or subjects associated with the event." - }, - { - "id": "au-3_gdn", - "name": "guidance", - "prose": "Audit record content that may be necessary to satisfy the requirement of this control, includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the information system after the event occurred).", - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-8", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "#si-11", - "rel": "related" - } - ] - }, - { - "id": "au-3_obj", - "name": "objective", - "prose": "Determine if the information system generates audit records containing information that establishes:", - "parts": [ - { - "id": "au-3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-3[1]" - } - ], - "prose": "what type of event occurred;" - }, - { - "id": "au-3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-3[2]" - } - ], - "prose": "when the event occurred;" - }, - { - "id": "au-3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-3[3]" - } - ], - "prose": "where the event occurred;" - }, - { - "id": "au-3_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-3[4]" - } - ], - "prose": "the source of the event;" - }, - { - "id": "au-3_obj.5", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-3[5]" - } - ], - "prose": "the outcome of the event; and" - }, - { - "id": "au-3_obj.6", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-3[6]" - } - ], - "prose": "the identity of any individuals or subjects associated with the event." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing content of audit records\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of organization-defined auditable events\n\ninformation system audit records\n\ninformation system incident reports\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information system auditing of auditable events" - } - ] - } - ], - "controls": [ - { - "id": "au-3.1", - "class": "SP800-53-enhancement", - "title": "Additional Audit Information", - "params": [ - { - "id": "au-3.1_prm_1", - "label": "organization-defined additional, more detailed information" - } - ], - "props": [ - { - "name": "label", - "value": "AU-3(1)" - }, - { - "name": "sort-id", - "value": "au-03.01" - } - ], - "parts": [ - { - "id": "au-3.1_smt", - "name": "statement", - "prose": "The information system generates audit records containing the following additional information: {{ insert: param, au-3.1_prm_1 }}." - }, - { - "id": "au-3.1_gdn", - "name": "guidance", - "prose": "Detailed information that organizations may consider in audit records includes, for example, full text recording of privileged commands or the individual identities of group account users. Organizations consider limiting the additional audit information to only that information explicitly needed for specific audit requirements. This facilitates the use of audit trails and audit logs by not including information that could potentially be misleading or could make it more difficult to locate information of interest." - }, - { - "id": "au-3.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-3.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-3(1)[1]" - } - ], - "prose": "the organization defines additional, more detailed information to be contained in audit records that the information system generates; and" - }, - { - "id": "au-3.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-3(1)[2]" - } - ], - "prose": "the information system generates audit records containing the organization-defined additional, more detailed information." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing content of audit records\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of organization-defined auditable events\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system audit capability" - } - ] - } - ] - }, - { - "id": "au-3.2", - "class": "SP800-53-enhancement", - "title": "Centralized Management of Planned Audit Record Content", - "params": [ - { - "id": "au-3.2_prm_1", - "label": "organization-defined information system components" - } - ], - "props": [ - { - "name": "label", - "value": "AU-3(2)" - }, - { - "name": "sort-id", - "value": "au-03.02" - } - ], - "parts": [ - { - "id": "au-3.2_smt", - "name": "statement", - "prose": "The information system provides centralized management and configuration of the content to be captured in audit records generated by {{ insert: param, au-3.2_prm_1 }}." - }, - { - "id": "au-3.2_gdn", - "name": "guidance", - "prose": "This control enhancement requires that the content to be captured in audit records be configured from a central location (necessitating automation). Organizations coordinate the selection of required audit content to support the centralized management and configuration capability provided by the information system.", - "links": [ - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-7", - "rel": "related" - } - ] - }, - { - "id": "au-3.2_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-3.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-3(2)[1]" - } - ], - "prose": "the organization defines information system components that generate audit records whose content is to be centrally managed and configured by the information system; and" - }, - { - "id": "au-3.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-3(2)[2]" - } - ], - "prose": "the information system provides centralized management and configuration of the content to be captured in audit records generated by the organization-defined information system components." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing content of audit records\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of organization-defined auditable events\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system capability implementing centralized management and configuration of audit record content" - } - ] - } - ] - } - ] - }, - { - "id": "au-4", - "class": "SP800-53", - "title": "Audit Storage Capacity", - "params": [ - { - "id": "au-4_prm_1", - "label": "organization-defined audit record storage requirements" - } - ], - "props": [ - { - "name": "label", - "value": "AU-4" - }, - { - "name": "sort-id", - "value": "au-04" - } - ], - "parts": [ - { - "id": "au-4_smt", - "name": "statement", - "prose": "The organization allocates audit record storage capacity in accordance with {{ insert: param, au-4_prm_1 }}." - }, - { - "id": "au-4_gdn", - "name": "guidance", - "prose": "Organizations consider the types of auditing to be performed and the audit processing requirements when allocating audit storage capacity. Allocating sufficient audit storage capacity reduces the likelihood of such capacity being exceeded and resulting in the potential loss or reduction of auditing capability.", - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-5", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-7", - "rel": "related" - }, - { - "href": "#au-11", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "au-4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "au-4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-4[1]" - } - ], - "prose": "defines audit record storage requirements; and" - }, - { - "id": "au-4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-4[2]" - } - ], - "prose": "allocates audit record storage capacity in accordance with the organization-defined audit record storage requirements." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit storage capacity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\naudit record storage requirements\n\naudit record storage capability for information system components\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit record storage capacity and related configuration settings" - } - ] - } - ], - "controls": [ - { - "id": "au-4.1", - "class": "SP800-53-enhancement", - "title": "Transfer to Alternate Storage", - "params": [ - { - "id": "au-4.1_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "AU-4(1)" - }, - { - "name": "sort-id", - "value": "au-04.01" - } - ], - "parts": [ - { - "id": "au-4.1_smt", - "name": "statement", - "prose": "The information system off-loads audit records {{ insert: param, au-4.1_prm_1 }} onto a different system or media than the system being audited." - }, - { - "id": "au-4.1_gdn", - "name": "guidance", - "prose": "Off-loading is a process designed to preserve the confidentiality and integrity of audit records by moving the records from the primary information system to a secondary or alternate system. It is a common process in information systems with limited audit storage capacity; the audit storage is used only in a transitory fashion until the system can communicate with the secondary or alternate system designated for storing the audit records, at which point the information is transferred." - }, - { - "id": "au-4.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-4.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-4(1)[1]" - } - ], - "prose": "the organization defines the frequency to off-load audit records onto a different system or media than the system being audited; and" - }, - { - "id": "au-4.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-4(1)[2]" - } - ], - "prose": "the information system off-loads audit records onto a different system or media than the system being audited with the organization-defined frequency." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit storage capacity\n\nprocedures addressing transfer of information system audit records to secondary or alternate systems\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlogs of audit record transfers to secondary or alternate systems\n\ninformation system audit records transferred to secondary or alternate systems\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit storage capacity planning responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting transfer of audit records onto a different system" - } - ] - } - ] - } - ] - }, - { - "id": "au-5", - "class": "SP800-53", - "title": "Response to Audit Processing Failures", - "params": [ - { - "id": "au-5_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "au-5_prm_2", - "label": "organization-defined actions to be taken (e.g., shut down information system, overwrite oldest audit records, stop generating audit records)" - } - ], - "props": [ - { - "name": "label", - "value": "AU-5" - }, - { - "name": "sort-id", - "value": "au-05" - } - ], - "parts": [ - { - "id": "au-5_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "au-5_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Alerts {{ insert: param, au-5_prm_1 }} in the event of an audit processing failure; and" - }, - { - "id": "au-5_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Takes the following additional actions: {{ insert: param, au-5_prm_2 }}." - } - ] - }, - { - "id": "au-5_gdn", - "name": "guidance", - "prose": "Audit processing failures include, for example, software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. Organizations may choose to define additional actions for different audit processing failures (e.g., by type, by location, by severity, or a combination of such factors). This control applies to each audit data storage repository (i.e., distinct information system component where audit records are stored), the total audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both.", - "links": [ - { - "href": "#au-4", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ] - }, - { - "id": "au-5_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-5.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(a)" - } - ], - "parts": [ - { - "id": "au-5.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(a)[1]" - } - ], - "prose": "the organization defines the personnel or roles to be alerted in the event of an audit processing failure;" - }, - { - "id": "au-5.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(a)[2]" - } - ], - "prose": "the information system alerts the organization-defined personnel or roles in the event of an audit processing failure;" - } - ] - }, - { - "id": "au-5.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(b)" - } - ], - "parts": [ - { - "id": "au-5.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(b)[1]" - } - ], - "prose": "the organization defines additional actions to be taken (e.g., shutdown information system, overwrite oldest audit records, stop generating audit records) in the event of an audit processing failure; and" - }, - { - "id": "au-5.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(b)[2]" - } - ], - "prose": "the information system takes the additional organization-defined actions in the event of an audit processing failure." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing response to audit processing failures\n\ninformation system design documentation\n\nsecurity plan\n\ninformation system configuration settings and associated documentation\n\nlist of personnel to be notified in case of an audit processing failure\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing information system response to audit processing failures" - } - ] - } - ], - "controls": [ - { - "id": "au-5.1", - "class": "SP800-53-enhancement", - "title": "Audit Storage Capacity", - "params": [ - { - "id": "au-5.1_prm_1", - "label": "organization-defined personnel, roles, and/or locations" - }, - { - "id": "au-5.1_prm_2", - "label": "organization-defined time period" - }, - { - "id": "au-5.1_prm_3", - "label": "organization-defined percentage" - } - ], - "props": [ - { - "name": "label", - "value": "AU-5(1)" - }, - { - "name": "sort-id", - "value": "au-05.01" - } - ], - "parts": [ - { - "id": "au-5.1_smt", - "name": "statement", - "prose": "The information system provides a warning to {{ insert: param, au-5.1_prm_1 }} within {{ insert: param, au-5.1_prm_2 }} when allocated audit record storage volume reaches {{ insert: param, au-5.1_prm_3 }} of repository maximum audit record storage capacity." - }, - { - "id": "au-5.1_gdn", - "name": "guidance", - "prose": "Organizations may have multiple audit data storage repositories distributed across multiple information system components, with each repository having different storage volume capacities." - }, - { - "id": "au-5.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-5.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(1)[1]" - } - ], - "prose": "the organization defines:", - "parts": [ - { - "id": "au-5.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(1)[1][a]" - } - ], - "prose": "personnel to be warned when allocated audit record storage volume reaches organization-defined percentage of repository maximum audit record storage capacity;" - }, - { - "id": "au-5.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(1)[1][b]" - } - ], - "prose": "roles to be warned when allocated audit record storage volume reaches organization-defined percentage of repository maximum audit record storage capacity; and/or" - }, - { - "id": "au-5.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(1)[1][c]" - } - ], - "prose": "locations to be warned when allocated audit record storage volume reaches organization-defined percentage of repository maximum audit record storage capacity;" - } - ] - }, - { - "id": "au-5.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(1)[2]" - } - ], - "prose": "the organization defines the time period within which the information system is to provide a warning to the organization-defined personnel, roles, and/or locations when allocated audit record storage volume reaches the organization-defined percentage of repository maximum audit record storage capacity;" - }, - { - "id": "au-5.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(1)[3]" - } - ], - "prose": "the organization defines the percentage of repository maximum audit record storage capacity that, if reached, requires a warning to be provided; and" - }, - { - "id": "au-5.1_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(1)[4]" - } - ], - "prose": "the information system provides a warning to the organization-defined personnel, roles, and/or locations within the organization-defined time period when allocated audit record storage volume reaches the organization-defined percentage of repository maximum audit record storage capacity." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing response to audit processing failures\n\ninformation system design documentation\n\nsecurity plan\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing audit storage limit warnings" - } - ] - } - ] - }, - { - "id": "au-5.2", - "class": "SP800-53-enhancement", - "title": "Real-time Alerts", - "params": [ - { - "id": "au-5.2_prm_1", - "label": "organization-defined real-time period" - }, - { - "id": "au-5.2_prm_2", - "label": "organization-defined personnel, roles, and/or locations" - }, - { - "id": "au-5.2_prm_3", - "label": "organization-defined audit failure events requiring real-time alerts" - } - ], - "props": [ - { - "name": "label", - "value": "AU-5(2)" - }, - { - "name": "sort-id", - "value": "au-05.02" - } - ], - "parts": [ - { - "id": "au-5.2_smt", - "name": "statement", - "prose": "The information system provides an alert in {{ insert: param, au-5.2_prm_1 }} to {{ insert: param, au-5.2_prm_2 }} when the following audit failure events occur: {{ insert: param, au-5.2_prm_3 }}." - }, - { - "id": "au-5.2_gdn", - "name": "guidance", - "prose": "Alerts provide organizations with urgent messages. Real-time alerts provide these messages at information technology speed (i.e., the time from event detection to alert occurs in seconds or less)." - }, - { - "id": "au-5.2_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-5.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(2)[1]" - } - ], - "prose": "the organization defines audit failure events requiring real-time alerts;" - }, - { - "id": "au-5.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(2)[2]" - } - ], - "prose": "the organization defines:", - "parts": [ - { - "id": "au-5.2_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(2)[2][a]" - } - ], - "prose": "personnel to be alerted when organization-defined audit failure events requiring real-time alerts occur;" - }, - { - "id": "au-5.2_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(2)[2][b]" - } - ], - "prose": "roles to be alerted when organization-defined audit failure events requiring real-time alerts occur; and/or" - }, - { - "id": "au-5.2_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(2)[2][c]" - } - ], - "prose": "locations to be alerted when organization-defined audit failure events requiring real-time alerts occur;" - } - ] - }, - { - "id": "au-5.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(2)[3]" - } - ], - "prose": "the organization defines the real-time period within which the information system is to provide an alert to the organization-defined personnel, roles, and/or locations when the organization-defined audit failure events requiring real-time alerts occur; and" - }, - { - "id": "au-5.2_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(2)[4]" - } - ], - "prose": "the information system provides an alert within the organization-defined real-time period to the organization-defined personnel, roles, and/or locations when organization-defined audit failure events requiring real-time alerts occur." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing response to audit processing failures\n\ninformation system design documentation\n\nsecurity plan\n\ninformation system configuration settings and associated documentation\n\nrecords of notifications or real-time alerts when audit processing failures occur\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing real-time audit alerts when organization-defined audit failure events occur" - } - ] - } - ] - }, - { - "id": "au-5.3", - "class": "SP800-53-enhancement", - "title": "Configurable Traffic Volume Thresholds", - "params": [ - { - "id": "au-5.3_prm_1", - "select": { - "choice": [ - "rejects", - "delays" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "AU-5(3)" - }, - { - "name": "sort-id", - "value": "au-05.03" - } - ], - "parts": [ - { - "id": "au-5.3_smt", - "name": "statement", - "prose": "The information system enforces configurable network communications traffic volume thresholds reflecting limits on auditing capacity and {{ insert: param, au-5.3_prm_1 }} network traffic above those thresholds." - }, - { - "id": "au-5.3_gdn", - "name": "guidance", - "prose": "Organizations have the capability to reject or delay the processing of network communications traffic if auditing such traffic is determined to exceed the storage capacity of the information system audit function. The rejection or delay response is triggered by the established organizational traffic volume thresholds which can be adjusted based on changes to audit storage capacity." - }, - { - "id": "au-5.3_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-5.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(3)[1]" - } - ], - "prose": "the information system enforces configurable network communications traffic volume thresholds reflecting limits on auditing capacity;" - }, - { - "id": "au-5.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(3)[2]" - } - ], - "prose": "the organization selects if network traffic above configurable traffic volume thresholds is to be:", - "parts": [ - { - "id": "au-5.3_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(3)[2][a]" - } - ], - "prose": "rejected; or" - }, - { - "id": "au-5.3_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(3)[2][b]" - } - ], - "prose": "delayed; and" - } - ] - }, - { - "id": "au-5.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(3)[3]" - } - ], - "prose": "the information system rejects or delays network communications traffic generated above configurable traffic volume thresholds." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing response to audit processing failures\n\ninformation system design documentation\n\nsecurity plan\n\ninformation system configuration settings and associated documentation\n\nconfiguration of network communications traffic volume thresholds\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system capability implementing configurable traffic volume thresholds" - } - ] - } - ] - }, - { - "id": "au-5.4", - "class": "SP800-53-enhancement", - "title": "Shutdown On Failure", - "params": [ - { - "id": "au-5.4_prm_1", - "select": { - "choice": [ - "full system shutdown", - "partial system shutdown", - "degraded operational mode with limited mission/business functionality available" - ] - } - }, - { - "id": "au-5.4_prm_2", - "label": "organization-defined audit failures" - } - ], - "props": [ - { - "name": "label", - "value": "AU-5(4)" - }, - { - "name": "sort-id", - "value": "au-05.04" - } - ], - "parts": [ - { - "id": "au-5.4_smt", - "name": "statement", - "prose": "The information system invokes a {{ insert: param, au-5.4_prm_1 }} in the event of {{ insert: param, au-5.4_prm_2 }}, unless an alternate audit capability exists." - }, - { - "id": "au-5.4_gdn", - "name": "guidance", - "prose": "Organizations determine the types of audit failures that can trigger automatic information system shutdowns or degraded operations. Because of the importance of ensuring mission/business continuity, organizations may determine that the nature of the audit failure is not so severe that it warrants a complete shutdown of the information system supporting the core organizational missions/business operations. In those instances, partial information system shutdowns or operating in a degraded mode with reduced capability may be viable alternatives.", - "links": [ - { - "href": "#au-15", - "rel": "related" - } - ] - }, - { - "id": "au-5.4_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-5.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(4)[1]" - } - ], - "prose": "the organization selects one of the following specific actions for the information system to invoke in the event of organization-defined audit failures:", - "parts": [ - { - "id": "au-5.4_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(4)[1][a]" - } - ], - "prose": "full system shutdown;" - }, - { - "id": "au-5.4_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(4)[1][b]" - } - ], - "prose": "partial system shutdown; or" - }, - { - "id": "au-5.4_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(4)[1][c]" - } - ], - "prose": "degraded operational mode with limited mission/business functionality available;" - } - ] - }, - { - "id": "au-5.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(4)[2]" - } - ], - "prose": "the organization defines audit failures that, unless an alternate audit capability exists, are to trigger the information system to invoke a specific action; and" - }, - { - "id": "au-5.4_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-5(4)[3]" - } - ], - "prose": "the information system invokes the selected specific action in the event of organization-defined audit failures, unless an alternate audit capability exists." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing response to audit processing failures\n\ninformation system design documentation\n\nsecurity plan\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system capability invoking system shutdown or degraded operational mode in the event of an audit processing failure" - } - ] - } - ] - } - ] - }, - { - "id": "au-6", - "class": "SP800-53", - "title": "Audit Review, Analysis, and Reporting", - "params": [ - { - "id": "au-6_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "au-6_prm_2", - "label": "organization-defined inappropriate or unusual activity" - }, - { - "id": "au-6_prm_3", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "AU-6" - }, - { - "name": "sort-id", - "value": "au-06" - } - ], - "parts": [ - { - "id": "au-6_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "au-6_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Reviews and analyzes information system audit records {{ insert: param, au-6_prm_1 }} for indications of {{ insert: param, au-6_prm_2 }}; and" - }, - { - "id": "au-6_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reports findings to {{ insert: param, au-6_prm_3 }}." - } - ] - }, - { - "id": "au-6_gdn", - "name": "guidance", - "prose": "Audit review, analysis, and reporting covers information security-related auditing performed by organizations including, for example, auditing that results from monitoring of account usage, remote access, wireless connectivity, mobile device connection, configuration settings, system component inventory, use of maintenance tools and nonlocal maintenance, physical access, temperature and humidity, equipment delivery and removal, communications at the information system boundaries, use of mobile code, and use of VoIP. Findings can be reported to organizational entities that include, for example, incident response team, help desk, information security group/department. If organizations are prohibited from reviewing and analyzing audit information or unable to conduct such activities (e.g., in certain national security applications or systems), the review/analysis may be carried out by other organizations granted such authority.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#au-7", - "rel": "related" - }, - { - "href": "#au-16", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-10", - "rel": "related" - }, - { - "href": "#cm-11", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#ir-5", - "rel": "related" - }, - { - "href": "#ir-6", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pe-6", - "rel": "related" - }, - { - "href": "#pe-14", - "rel": "related" - }, - { - "href": "#pe-16", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-18", - "rel": "related" - }, - { - "href": "#sc-19", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "au-6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "au-6.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(a)" - } - ], - "parts": [ - { - "id": "au-6.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(a)[1]" - } - ], - "prose": "defines the types of inappropriate or unusual activity to look for when information system audit records are reviewed and analyzed;" - }, - { - "id": "au-6.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(a)[2]" - } - ], - "prose": "defines the frequency to review and analyze information system audit records for indications of organization-defined inappropriate or unusual activity;" - }, - { - "id": "au-6.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(a)[3]" - } - ], - "prose": "reviews and analyzes information system audit records for indications of organization-defined inappropriate or unusual activity with the organization-defined frequency;" - } - ] - }, - { - "id": "au-6.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(b)" - } - ], - "parts": [ - { - "id": "au-6.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(b)[1]" - } - ], - "prose": "defines personnel or roles to whom findings resulting from reviews and analysis of information system audit records are to be reported; and" - }, - { - "id": "au-6.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(b)[2]" - } - ], - "prose": "reports findings to organization-defined personnel or roles." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit review, analysis, and reporting\n\nreports of audit findings\n\nrecords of actions taken in response to reviews/analyses of audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit review, analysis, and reporting responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ], - "controls": [ - { - "id": "au-6.1", - "class": "SP800-53-enhancement", - "title": "Process Integration", - "props": [ - { - "name": "label", - "value": "AU-6(1)" - }, - { - "name": "sort-id", - "value": "au-06.01" - } - ], - "parts": [ - { - "id": "au-6.1_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to integrate audit review, analysis, and reporting processes to support organizational processes for investigation and response to suspicious activities." - }, - { - "id": "au-6.1_gdn", - "name": "guidance", - "prose": "Organizational processes benefiting from integrated audit review, analysis, and reporting include, for example, incident response, continuous monitoring, contingency planning, and Inspector General audits.", - "links": [ - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "#pm-7", - "rel": "related" - } - ] - }, - { - "id": "au-6.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "au-6.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(1)[1]" - } - ], - "prose": "employs automated mechanisms to integrate:", - "parts": [ - { - "id": "au-6.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(1)[1][a]" - } - ], - "prose": "audit review;" - }, - { - "id": "au-6.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(1)[1][b]" - } - ], - "prose": "analysis;" - }, - { - "id": "au-6.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(1)[1][c]" - } - ], - "prose": "reporting processes;" - } - ] - }, - { - "id": "au-6.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(1)[2]" - } - ], - "prose": "uses integrated audit review, analysis and reporting processes to support organizational processes for:", - "parts": [ - { - "id": "au-6.1_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(1)[2][a]" - } - ], - "prose": "investigation of suspicious activities; and" - }, - { - "id": "au-6.1_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(1)[2][b]" - } - ], - "prose": "response to suspicious activities." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit review, analysis, and reporting\n\nprocedures addressing investigation and response to suspicious activities\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit review, analysis, and reporting responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms integrating audit review, analysis, and reporting processes" - } - ] - } - ] - }, - { - "id": "au-6.2", - "class": "SP800-53-enhancement", - "title": "Automated Security Alerts", - "props": [ - { - "name": "label", - "value": "AU-6(2)" - }, - { - "name": "sort-id", - "value": "au-06.02" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#si-4", - "rel": "incorporated-into" - } - ] - }, - { - "id": "au-6.3", - "class": "SP800-53-enhancement", - "title": "Correlate Audit Repositories", - "props": [ - { - "name": "label", - "value": "AU-6(3)" - }, - { - "name": "sort-id", - "value": "au-06.03" - } - ], - "parts": [ - { - "id": "au-6.3_smt", - "name": "statement", - "prose": "The organization analyzes and correlates audit records across different repositories to gain organization-wide situational awareness." - }, - { - "id": "au-6.3_gdn", - "name": "guidance", - "prose": "Organization-wide situational awareness includes awareness across all three tiers of risk management (i.e., organizational, mission/business process, and information system) and supports cross-organization awareness.", - "links": [ - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - } - ] - }, - { - "id": "au-6.3_obj", - "name": "objective", - "prose": "Determine if the organization analyzes and correlates audit records across different repositories to gain organization-wide situational awareness." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit review, analysis, and reporting\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records across different repositories\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit review, analysis, and reporting responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting analysis and correlation of audit records" - } - ] - } - ] - }, - { - "id": "au-6.4", - "class": "SP800-53-enhancement", - "title": "Central Review and Analysis", - "props": [ - { - "name": "label", - "value": "AU-6(4)" - }, - { - "name": "sort-id", - "value": "au-06.04" - } - ], - "parts": [ - { - "id": "au-6.4_smt", - "name": "statement", - "prose": "The information system provides the capability to centrally review and analyze audit records from multiple components within the system." - }, - { - "id": "au-6.4_gdn", - "name": "guidance", - "prose": "Automated mechanisms for centralized reviews and analyses include, for example, Security Information Management products.", - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - } - ] - }, - { - "id": "au-6.4_obj", - "name": "objective", - "prose": "Determine if the information system provides the capability to centrally review and analyze audit records from multiple components within the system." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit review, analysis, and reporting\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsecurity plan\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit review, analysis, and reporting responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system capability to centralize review and analysis of audit records" - } - ] - } - ] - }, - { - "id": "au-6.5", - "class": "SP800-53-enhancement", - "title": "Integration / Scanning and Monitoring Capabilities", - "params": [ - { - "id": "au-6.5_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "vulnerability scanning information", - "performance data", - "information system monitoring information", - " {{ insert: param, au-6.5_prm_2 }} " - ] - } - }, - { - "id": "au-6.5_prm_2", - "depends-on": "au-6.5_prm_1", - "label": "organization-defined data/information collected from other sources" - } - ], - "props": [ - { - "name": "label", - "value": "AU-6(5)" - }, - { - "name": "sort-id", - "value": "au-06.05" - } - ], - "parts": [ - { - "id": "au-6.5_smt", - "name": "statement", - "prose": "The organization integrates analysis of audit records with analysis of {{ insert: param, au-6.5_prm_1 }} to further enhance the ability to identify inappropriate or unusual activity." - }, - { - "id": "au-6.5_gdn", - "name": "guidance", - "prose": "This control enhancement does not require vulnerability scanning, the generation of performance data, or information system monitoring. Rather, the enhancement requires that the analysis of information being otherwise produced in these areas is integrated with the analysis of audit information. Security Event and Information Management System tools can facilitate audit record aggregation/consolidation from multiple information system components as well as audit record correlation and analysis. The use of standardized audit record analysis scripts developed by organizations (with localized script adjustments, as necessary) provides more cost-effective approaches for analyzing audit record information collected. The correlation of audit record information with vulnerability scanning information is important in determining the veracity of vulnerability scans and correlating attack detection events with scanning results. Correlation with performance data can help uncover denial of service attacks or cyber attacks resulting in unauthorized use of resources. Correlation with system monitoring information can assist in uncovering attacks and in better relating audit information to operational situations.", - "links": [ - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - } - ] - }, - { - "id": "au-6.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "au-6.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(5)[1]" - } - ], - "prose": "defines data/information to be collected from other sources;" - }, - { - "id": "au-6.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(5)[2]" - } - ], - "prose": "selects sources of data/information to be analyzed and integrated with the analysis of audit records from one or more of the following:", - "parts": [ - { - "id": "au-6.5_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(5)[2][a]" - } - ], - "prose": "vulnerability scanning information;" - }, - { - "id": "au-6.5_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(5)[2][b]" - } - ], - "prose": "performance data;" - }, - { - "id": "au-6.5_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(5)[2][c]" - } - ], - "prose": "information system monitoring information; and/or" - }, - { - "id": "au-6.5_obj.2.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(5)[2][d]" - } - ], - "prose": "organization-defined data/information collected from other sources; and" - } - ] - }, - { - "id": "au-6.5_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(5)[3]" - } - ], - "prose": "integrates the analysis of audit records with the analysis of selected data/information to further enhance the ability to identify inappropriate or unusual activity." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit review, analysis, and reporting\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nintegrated analysis of audit records, vulnerability scanning information, performance data, network monitoring information and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit review, analysis, and reporting responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing capability to integrate analysis of audit records with analysis of data/information sources" - } - ] - } - ] - }, - { - "id": "au-6.6", - "class": "SP800-53-enhancement", - "title": "Correlation with Physical Monitoring", - "props": [ - { - "name": "label", - "value": "AU-6(6)" - }, - { - "name": "sort-id", - "value": "au-06.06" - } - ], - "parts": [ - { - "id": "au-6.6_smt", - "name": "statement", - "prose": "The organization correlates information from audit records with information obtained from monitoring physical access to further enhance the ability to identify suspicious, inappropriate, unusual, or malevolent activity." - }, - { - "id": "au-6.6_gdn", - "name": "guidance", - "prose": "The correlation of physical audit information and audit logs from information systems may assist organizations in identifying examples of suspicious behavior or supporting evidence of such behavior. For example, the correlation of an individual’s identity for logical access to certain information systems with the additional physical security information that the individual was actually present at the facility when the logical access occurred, may prove to be useful in investigations." - }, - { - "id": "au-6.6_obj", - "name": "objective", - "prose": "Determine if the organization correlates information from audit records with information obtained from monitoring physical access to enhance the ability to identify suspicious, inappropriate, unusual, or malevolent activity." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit review, analysis, and reporting\n\nprocedures addressing physical access monitoring\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ndocumentation providing evidence of correlated information obtained from audit records and physical access monitoring records\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit review, analysis, and reporting responsibilities\n\norganizational personnel with physical access monitoring responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing capability to correlate information from audit records with information from monitoring physical access" - } - ] - } - ] - }, - { - "id": "au-6.7", - "class": "SP800-53-enhancement", - "title": "Permitted Actions", - "params": [ - { - "id": "au-6.7_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "information system process", - "role", - "user" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "AU-6(7)" - }, - { - "name": "sort-id", - "value": "au-06.07" - } - ], - "parts": [ - { - "id": "au-6.7_smt", - "name": "statement", - "prose": "The organization specifies the permitted actions for each {{ insert: param, au-6.7_prm_1 }} associated with the review, analysis, and reporting of audit information." - }, - { - "id": "au-6.7_gdn", - "name": "guidance", - "prose": "Organizations specify permitted actions for information system processes, roles, and/or users associated with the review, analysis, and reporting of audit records through account management techniques. Specifying permitted actions on audit information is a way to enforce the principle of least privilege. Permitted actions are enforced by the information system and include, for example, read, write, execute, append, and delete." - }, - { - "id": "au-6.7_obj", - "name": "objective", - "prose": "Determine if the organization specifies the permitted actions for each one or more of the following associated with the review, analysis and reporting of audit information:", - "parts": [ - { - "id": "au-6.7_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(7)[1]" - } - ], - "prose": "information system process;" - }, - { - "id": "au-6.7_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(7)[2]" - } - ], - "prose": "role; and/or" - }, - { - "id": "au-6.7_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(7)[3]" - } - ], - "prose": "user." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing process, role and/or user permitted actions from audit review, analysis, and reporting\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit review, analysis, and reporting responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting permitted actions for review, analysis, and reporting of audit information" - } - ] - } - ] - }, - { - "id": "au-6.8", - "class": "SP800-53-enhancement", - "title": "Full Text Analysis of Privileged Commands", - "props": [ - { - "name": "label", - "value": "AU-6(8)" - }, - { - "name": "sort-id", - "value": "au-06.08" - } - ], - "parts": [ - { - "id": "au-6.8_smt", - "name": "statement", - "prose": "The organization performs a full text analysis of audited privileged commands in a physically distinct component or subsystem of the information system, or other information system that is dedicated to that analysis." - }, - { - "id": "au-6.8_gdn", - "name": "guidance", - "prose": "This control enhancement requires a distinct environment for the dedicated analysis of audit information related to privileged users without compromising such information on the information system where the users have elevated privileges including the capability to execute privileged commands. Full text analysis refers to analysis that considers the full text of privileged commands (i.e., commands and all parameters) as opposed to analysis that considers only the name of the command. Full text analysis includes, for example, the use of pattern matching and heuristics.", - "links": [ - { - "href": "#au-3", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "#au-11", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - } - ] - }, - { - "id": "au-6.8_obj", - "name": "objective", - "prose": "Determine if the organization performs a full text analysis of audited privileged commands in:", - "parts": [ - { - "id": "au-6.8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(8)[1]" - } - ], - "prose": "a physically distinct component or subsystem of the information system; or" - }, - { - "id": "au-6.8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(8)[2]" - } - ], - "prose": "other information system that is dedicated to that analysis." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit review, analysis, and reporting\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ntext analysis tools and techniques\n\ntext analysis documentation of audited privileged commands\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit review, analysis, and reporting responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing capability to perform a full text analysis of audited privilege commands" - } - ] - } - ] - }, - { - "id": "au-6.9", - "class": "SP800-53-enhancement", - "title": "Correlation with Information from Nontechnical Sources", - "props": [ - { - "name": "label", - "value": "AU-6(9)" - }, - { - "name": "sort-id", - "value": "au-06.09" - } - ], - "parts": [ - { - "id": "au-6.9_smt", - "name": "statement", - "prose": "The organization correlates information from nontechnical sources with audit information to enhance organization-wide situational awareness." - }, - { - "id": "au-6.9_gdn", - "name": "guidance", - "prose": "Nontechnical sources include, for example, human resources records documenting organizational policy violations (e.g., sexual harassment incidents, improper use of organizational information assets). Such information can lead organizations to a more directed analytical effort to detect potential malicious insider activity. Due to the sensitive nature of the information available from nontechnical sources, organizations limit access to such information to minimize the potential for the inadvertent release of privacy-related information to individuals that do not have a need to know. Thus, correlation of information from nontechnical sources with audit information generally occurs only when individuals are suspected of being involved in a security incident. Organizations obtain legal advice prior to initiating such actions.", - "links": [ - { - "href": "#at-2", - "rel": "related" - } - ] - }, - { - "id": "au-6.9_obj", - "name": "objective", - "prose": "Determine if the organization correlates information from nontechnical sources with audit information to enhance organization-wide situational awareness." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit review, analysis, and reporting\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ndocumentation providing evidence of correlated information obtained from audit records and organization-defined nontechnical sources\n\nlist of information types from nontechnical sources for correlation with audit information\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit review, analysis, and reporting responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing capability to correlate information from non-technical sources" - } - ] - } - ] - }, - { - "id": "au-6.10", - "class": "SP800-53-enhancement", - "title": "Audit Level Adjustment", - "props": [ - { - "name": "label", - "value": "AU-6(10)" - }, - { - "name": "sort-id", - "value": "au-06.10" - } - ], - "parts": [ - { - "id": "au-6.10_smt", - "name": "statement", - "prose": "The organization adjusts the level of audit review, analysis, and reporting within the information system when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information." - }, - { - "id": "au-6.10_gdn", - "name": "guidance", - "prose": "The frequency, scope, and/or depth of the audit review, analysis, and reporting may be adjusted to meet organizational needs based on new information received." - }, - { - "id": "au-6.10_obj", - "name": "objective", - "prose": "Determine if the organization adjusts the level of audit review, analysis, and reporting within the information system when there is a change in risk based on:", - "parts": [ - { - "id": "au-6.10_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(10)[1]" - } - ], - "prose": "law enforcement information;" - }, - { - "id": "au-6.10_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(10)[2]" - } - ], - "prose": "intelligence information; and/or" - }, - { - "id": "au-6.10_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-6(10)[3]" - } - ], - "prose": "other credible sources of information." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit review, analysis, and reporting\n\norganizational risk assessment\n\nsecurity control assessment\n\nvulnerability assessment\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit review, analysis, and reporting responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting review, analysis, and reporting of audit information" - } - ] - } - ] - } - ] - }, - { - "id": "au-7", - "class": "SP800-53", - "title": "Audit Reduction and Report Generation", - "props": [ - { - "name": "label", - "value": "AU-7" - }, - { - "name": "sort-id", - "value": "au-07" - } - ], - "parts": [ - { - "id": "au-7_smt", - "name": "statement", - "prose": "The information system provides an audit reduction and report generation capability that:", - "parts": [ - { - "id": "au-7_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Supports on-demand audit review, analysis, and reporting requirements and after-the-fact investigations of security incidents; and" - }, - { - "id": "au-7_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Does not alter the original content or time ordering of audit records." - } - ] - }, - { - "id": "au-7_gdn", - "name": "guidance", - "prose": "Audit reduction is a process that manipulates collected audit information and organizes such information in a summary format that is more meaningful to analysts. Audit reduction and report generation capabilities do not always emanate from the same information system or from the same organizational entities conducting auditing activities. Audit reduction capability can include, for example, modern data mining techniques with advanced data filters to identify anomalous behavior in audit records. The report generation capability provided by the information system can generate customizable reports. Time ordering of audit records can be a significant issue if the granularity of the timestamp in the record is insufficient.", - "links": [ - { - "href": "#au-6", - "rel": "related" - } - ] - }, - { - "id": "au-7_obj", - "name": "objective", - "prose": "Determine if the information system provides an audit reduction and report generation capability that supports:", - "parts": [ - { - "id": "au-7.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-7(a)" - } - ], - "parts": [ - { - "id": "au-7.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-7(a)[1]" - } - ], - "prose": "on-demand audit review;" - }, - { - "id": "au-7.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-7(a)[2]" - } - ], - "prose": "analysis;" - }, - { - "id": "au-7.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-7(a)[3]" - } - ], - "prose": "reporting requirements;" - }, - { - "id": "au-7.a_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-7(a)[4]" - } - ], - "prose": "after-the-fact investigations of security incidents; and" - } - ] - }, - { - "id": "au-7.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-7(b)" - } - ], - "prose": "does not alter the original content or time ordering of audit records." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit reduction and report generation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\naudit reduction, review, analysis, and reporting tools\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit reduction and report generation responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit reduction and report generation capability" - } - ] - } - ], - "controls": [ - { - "id": "au-7.1", - "class": "SP800-53-enhancement", - "title": "Automatic Processing", - "params": [ - { - "id": "au-7.1_prm_1", - "label": "organization-defined audit fields within audit records" - } - ], - "props": [ - { - "name": "label", - "value": "AU-7(1)" - }, - { - "name": "sort-id", - "value": "au-07.01" - } - ], - "parts": [ - { - "id": "au-7.1_smt", - "name": "statement", - "prose": "The information system provides the capability to process audit records for events of interest based on {{ insert: param, au-7.1_prm_1 }}." - }, - { - "id": "au-7.1_gdn", - "name": "guidance", - "prose": "Events of interest can be identified by the content of specific audit record fields including, for example, identities of individuals, event types, event locations, event times, event dates, system resources involved, IP addresses involved, or information objects accessed. Organizations may define audit event criteria to any degree of granularity required, for example, locations selectable by general networking location (e.g., by network or subnetwork) or selectable by specific information system component.", - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - } - ] - }, - { - "id": "au-7.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-7.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-7(1)[1]" - } - ], - "prose": "the organization defines audit fields within audit records in order to process audit records for events of interest; and" - }, - { - "id": "au-7.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-7(1)[2]" - } - ], - "prose": "the information system provides the capability to process audit records for events of interest based on the organization-defined audit fields within audit records." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit reduction and report generation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\naudit reduction, review, analysis, and reporting tools\n\naudit record criteria (fields) establishing events of interest\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit reduction and report generation responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit reduction and report generation capability" - } - ] - } - ] - }, - { - "id": "au-7.2", - "class": "SP800-53-enhancement", - "title": "Automatic Sort and Search", - "params": [ - { - "id": "au-7.2_prm_1", - "label": "organization-defined audit fields within audit records" - } - ], - "props": [ - { - "name": "label", - "value": "AU-7(2)" - }, - { - "name": "sort-id", - "value": "au-07.02" - } - ], - "parts": [ - { - "id": "au-7.2_smt", - "name": "statement", - "prose": "The information system provides the capability to sort and search audit records for events of interest based on the content of {{ insert: param, au-7.2_prm_1 }}." - }, - { - "id": "au-7.2_gdn", - "name": "guidance", - "prose": "Sorting and searching of audit records may be based upon the contents of audit record fields, for example: (i) date/time of events; (ii) user identifiers; (iii) Internet Protocol (IP) addresses involved in the event; (iv) type of event; or (v) event success/failure." - }, - { - "id": "au-7.2_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-7.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-7(2)[1]" - } - ], - "prose": "the organization defines audit fields within audit records in order to sort and search audit records for events of interest based on content of such audit fields; and" - }, - { - "id": "au-7.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-7(2)[2]" - } - ], - "prose": "the information system provides the capability to sort and search audit records for events of interest based on the content of organization-defined audit fields within audit records." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit reduction and report generation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\naudit reduction, review, analysis, and reporting tools\n\naudit record criteria (fields) establishing events of interest\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit reduction and report generation responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit reduction and report generation capability" - } - ] - } - ] - } - ] - }, - { - "id": "au-8", - "class": "SP800-53", - "title": "Time Stamps", - "params": [ - { - "id": "au-8_prm_1", - "label": "organization-defined granularity of time measurement" - } - ], - "props": [ - { - "name": "label", - "value": "AU-8" - }, - { - "name": "sort-id", - "value": "au-08" - } - ], - "parts": [ - { - "id": "au-8_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "au-8_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Uses internal system clocks to generate time stamps for audit records; and" - }, - { - "id": "au-8_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Records time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT) and meets {{ insert: param, au-8_prm_1 }}." - } - ] - }, - { - "id": "au-8_gdn", - "name": "guidance", - "prose": "Time stamps generated by the information system include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. Granularity of time measurements refers to the degree of synchronization between information system clocks and reference clocks, for example, clocks synchronizing within hundreds of milliseconds or within tens of milliseconds. Organizations may define different time granularities for different system components. Time service can also be critical to other security capabilities such as access control and identification and authentication, depending on the nature of the mechanisms used to support those capabilities.", - "links": [ - { - "href": "#au-3", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - } - ] - }, - { - "id": "au-8_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-8.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-8(a)" - } - ], - "prose": "the information system uses internal system clocks to generate time stamps for audit records;" - }, - { - "id": "au-8.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-8(b)" - } - ], - "parts": [ - { - "id": "au-8.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-8(b)[1]" - } - ], - "prose": "the information system records time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT);" - }, - { - "id": "au-8.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-8(b)[2]" - } - ], - "prose": "the organization defines the granularity of time measurement to be met when recording time stamps for audit records; and" - }, - { - "id": "au-8.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-8(b)[3]" - } - ], - "prose": "the organization records time stamps for audit records that meet the organization-defined granularity of time measurement." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing time stamp generation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing time stamp generation" - } - ] - } - ], - "controls": [ - { - "id": "au-8.1", - "class": "SP800-53-enhancement", - "title": "Synchronization with Authoritative Time Source", - "params": [ - { - "id": "au-8.1_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "au-8.1_prm_2", - "label": "organization-defined authoritative time source" - }, - { - "id": "au-8.1_prm_3", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "AU-8(1)" - }, - { - "name": "sort-id", - "value": "au-08.01" - } - ], - "parts": [ - { - "id": "au-8.1_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "au-8.1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Compares the internal information system clocks {{ insert: param, au-8.1_prm_1 }} with {{ insert: param, au-8.1_prm_2 }}; and" - }, - { - "id": "au-8.1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Synchronizes the internal system clocks to the authoritative time source when the time difference is greater than {{ insert: param, au-8.1_prm_3 }}." - } - ] - }, - { - "id": "au-8.1_gdn", - "name": "guidance", - "prose": "This control enhancement provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network." - }, - { - "id": "au-8.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-8.1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-8(1)(a)" - } - ], - "parts": [ - { - "id": "au-8.1.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-8(1)(a)[1]" - } - ], - "prose": "the organization defines the authoritative time source to which internal information system clocks are to be compared;" - }, - { - "id": "au-8.1.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-8(1)(a)[2]" - } - ], - "prose": "the organization defines the frequency to compare the internal information system clocks with the organization-defined authoritative time source; and" - }, - { - "id": "au-8.1.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-8(1)(a)[3]" - } - ], - "prose": "the information system compares the internal information system clocks with the organization-defined authoritative time source with organization-defined frequency; and" - } - ], - "links": [ - { - "href": "#au-8.1_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "au-8.1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-8(1)(b)" - } - ], - "parts": [ - { - "id": "au-8.1.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-8(1)(b)[1]" - } - ], - "prose": "the organization defines the time period that, if exceeded by the time difference between the internal system clocks and the authoritative time source, will result in the internal system clocks being synchronized to the authoritative time source; and" - }, - { - "id": "au-8.1.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-8(1)(b)[2]" - } - ], - "prose": "the information system synchronizes the internal information system clocks to the authoritative time source when the time difference is greater than the organization-defined time period." - } - ], - "links": [ - { - "href": "#au-8.1_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing time stamp generation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing internal information system clock synchronization" - } - ] - } - ] - }, - { - "id": "au-8.2", - "class": "SP800-53-enhancement", - "title": "Secondary Authoritative Time Source", - "props": [ - { - "name": "label", - "value": "AU-8(2)" - }, - { - "name": "sort-id", - "value": "au-08.02" - } - ], - "parts": [ - { - "id": "au-8.2_smt", - "name": "statement", - "prose": "The information system identifies a secondary authoritative time source that is located in a different geographic region than the primary authoritative time source." - }, - { - "id": "au-8.2_obj", - "name": "objective", - "prose": "Determine if the information system identifies a secondary authoritative time source that is located in a different geographic region than the primary authoritative time source." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing time stamp generation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing internal information system clock authoritative time sources" - } - ] - } - ] - } - ] - }, - { - "id": "au-9", - "class": "SP800-53", - "title": "Protection of Audit Information", - "props": [ - { - "name": "label", - "value": "AU-9" - }, - { - "name": "sort-id", - "value": "au-09" - } - ], - "parts": [ - { - "id": "au-9_smt", - "name": "statement", - "prose": "The information system protects audit information and audit tools from unauthorized access, modification, and deletion." - }, - { - "id": "au-9_gdn", - "name": "guidance", - "prose": "Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity. This control focuses on technical protection of audit information. Physical protection of audit information is addressed by media protection controls and physical and environmental protection controls.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pe-6", - "rel": "related" - } - ] - }, - { - "id": "au-9_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-9_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9[1]" - } - ], - "prose": "the information system protects audit information from unauthorized:", - "parts": [ - { - "id": "au-9_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9[1][a]" - } - ], - "prose": "access;" - }, - { - "id": "au-9_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9[1][b]" - } - ], - "prose": "modification;" - }, - { - "id": "au-9_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9[1][c]" - } - ], - "prose": "deletion;" - } - ] - }, - { - "id": "au-9_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9[2]" - } - ], - "prose": "the information system protects audit tools from unauthorized:", - "parts": [ - { - "id": "au-9_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9[2][a]" - } - ], - "prose": "access;" - }, - { - "id": "au-9_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9[2][b]" - } - ], - "prose": "modification; and" - }, - { - "id": "au-9_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9[2][c]" - } - ], - "prose": "deletion." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\naccess control policy and procedures\n\nprocedures addressing protection of audit information\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation, information system audit records\n\naudit tools\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing audit information protection" - } - ] - } - ], - "controls": [ - { - "id": "au-9.1", - "class": "SP800-53-enhancement", - "title": "Hardware Write-once Media", - "props": [ - { - "name": "label", - "value": "AU-9(1)" - }, - { - "name": "sort-id", - "value": "au-09.01" - } - ], - "parts": [ - { - "id": "au-9.1_smt", - "name": "statement", - "prose": "The information system writes audit trails to hardware-enforced, write-once media." - }, - { - "id": "au-9.1_gdn", - "name": "guidance", - "prose": "This control enhancement applies to the initial generation of audit trails (i.e., the collection of audit records that represents the audit information to be used for detection, analysis, and reporting purposes) and to the backup of those audit trails. The enhancement does not apply to the initial generation of audit records prior to being written to an audit trail. Write-once, read-many (WORM) media includes, for example, Compact Disk-Recordable (CD-R) and Digital Video Disk-Recordable (DVD-R). In contrast, the use of switchable write-protection media such as on tape cartridges or Universal Serial Bus (USB) drives results in write-protected, but not write-once, media.", - "links": [ - { - "href": "#au-4", - "rel": "related" - }, - { - "href": "#au-5", - "rel": "related" - } - ] - }, - { - "id": "au-9.1_obj", - "name": "objective", - "prose": "Determine if the information system writes audit trails to hardware-enforced, write-once media." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\naccess control policy and procedures\n\nprocedures addressing protection of audit information\n\ninformation system design documentation\n\ninformation system hardware settings\n\ninformation system configuration settings and associated documentation\n\ninformation system storage media\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media storing audit trails" - } - ] - } - ] - }, - { - "id": "au-9.2", - "class": "SP800-53-enhancement", - "title": "Audit Backup On Separate Physical Systems / Components", - "params": [ - { - "id": "au-9.2_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "AU-9(2)" - }, - { - "name": "sort-id", - "value": "au-09.02" - } - ], - "parts": [ - { - "id": "au-9.2_smt", - "name": "statement", - "prose": "The information system backs up audit records {{ insert: param, au-9.2_prm_1 }} onto a physically different system or system component than the system or component being audited." - }, - { - "id": "au-9.2_gdn", - "name": "guidance", - "prose": "This control enhancement helps to ensure that a compromise of the information system being audited does not also result in a compromise of the audit records.", - "links": [ - { - "href": "#au-4", - "rel": "related" - }, - { - "href": "#au-5", - "rel": "related" - }, - { - "href": "#au-11", - "rel": "related" - } - ] - }, - { - "id": "au-9.2_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-9.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9(2)[1]" - } - ], - "prose": "the organization defines the frequency to back up audit records onto a physically different system or system component than the system or component being audited; and" - }, - { - "id": "au-9.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9(2)[2]" - } - ], - "prose": "the information system backs up audit records with the organization-defined frequency, onto a physically different system or system component than the system or component being audited." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing protection of audit information\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation, system or media storing backups of information system audit records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing the backing up of audit records" - } - ] - } - ] - }, - { - "id": "au-9.3", - "class": "SP800-53-enhancement", - "title": "Cryptographic Protection", - "props": [ - { - "name": "label", - "value": "AU-9(3)" - }, - { - "name": "sort-id", - "value": "au-09.03" - } - ], - "parts": [ - { - "id": "au-9.3_smt", - "name": "statement", - "prose": "The information system implements cryptographic mechanisms to protect the integrity of audit information and audit tools." - }, - { - "id": "au-9.3_gdn", - "name": "guidance", - "prose": "Cryptographic mechanisms used for protecting the integrity of audit information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash.", - "links": [ - { - "href": "#au-10", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "au-9.3_obj", - "name": "objective", - "prose": "Determine if the information system:", - "parts": [ - { - "id": "au-9.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9(3)[1]" - } - ], - "prose": "uses cryptographic mechanisms to protect the integrity of audit information; and" - }, - { - "id": "au-9.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9(3)[2]" - } - ], - "prose": "uses cryptographic mechanisms to protect the integrity of audit tools." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\naccess control policy and procedures\n\nprocedures addressing protection of audit information\n\ninformation system design documentation\n\ninformation system hardware settings\n\ninformation system configuration settings and associated documentation, information system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Cryptographic mechanisms protecting integrity of audit information and tools" - } - ] - } - ] - }, - { - "id": "au-9.4", - "class": "SP800-53-enhancement", - "title": "Access by Subset of Privileged Users", - "params": [ - { - "id": "au-9.4_prm_1", - "label": "organization-defined subset of privileged users" - } - ], - "props": [ - { - "name": "label", - "value": "AU-9(4)" - }, - { - "name": "sort-id", - "value": "au-09.04" - } - ], - "parts": [ - { - "id": "au-9.4_smt", - "name": "statement", - "prose": "The organization authorizes access to management of audit functionality to only {{ insert: param, au-9.4_prm_1 }}." - }, - { - "id": "au-9.4_gdn", - "name": "guidance", - "prose": "Individuals with privileged access to an information system and who are also the subject of an audit by that system, may affect the reliability of audit information by inhibiting audit activities or modifying audit records. This control enhancement requires that privileged access be further defined between audit-related privileges and other privileges, thus limiting the users with audit-related privileges.", - "links": [ - { - "href": "#ac-5", - "rel": "related" - } - ] - }, - { - "id": "au-9.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "au-9.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9(4)[1]" - } - ], - "prose": "defines a subset of privileged users to be authorized access to management of audit functionality; and" - }, - { - "id": "au-9.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9(4)[2]" - } - ], - "prose": "authorizes access to management of audit functionality to only the organization-defined subset of privileged users." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\naccess control policy and procedures\n\nprocedures addressing protection of audit information\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation, system-generated list of privileged users with access to management of audit functionality\n\naccess authorizations\n\naccess control list\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms managing access to audit functionality" - } - ] - } - ] - }, - { - "id": "au-9.5", - "class": "SP800-53-enhancement", - "title": "Dual Authorization", - "params": [ - { - "id": "au-9.5_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "movement", - "deletion" - ] - } - }, - { - "id": "au-9.5_prm_2", - "label": "organization-defined audit information" - } - ], - "props": [ - { - "name": "label", - "value": "AU-9(5)" - }, - { - "name": "sort-id", - "value": "au-09.05" - } - ], - "parts": [ - { - "id": "au-9.5_smt", - "name": "statement", - "prose": "The organization enforces dual authorization for {{ insert: param, au-9.5_prm_1 }} of {{ insert: param, au-9.5_prm_2 }}." - }, - { - "id": "au-9.5_gdn", - "name": "guidance", - "prose": "Organizations may choose different selection options for different types of audit information. Dual authorization mechanisms require the approval of two authorized individuals in order to execute. Dual authorization may also be known as two-person control.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - } - ] - }, - { - "id": "au-9.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "au-9.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9(5)[1]" - } - ], - "prose": "defines audit information for which dual authorization is to be enforced;" - }, - { - "id": "au-9.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9(5)[2]" - } - ], - "prose": "defines one or more of the following types of operations on audit information for which dual authorization is to be enforced:", - "parts": [ - { - "id": "au-9.5_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9(5)[2][a]" - } - ], - "prose": "movement; and/or" - }, - { - "id": "au-9.5_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9(5)[2][b]" - } - ], - "prose": "deletion; and" - } - ] - }, - { - "id": "au-9.5_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9(5)[3]" - } - ], - "prose": "enforces dual authorization for the movement and/or deletion of organization-defined audit information." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\naccess control policy and procedures\n\nprocedures addressing protection of audit information\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation, access authorizations\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing enforcement of dual authorization" - } - ] - } - ] - }, - { - "id": "au-9.6", - "class": "SP800-53-enhancement", - "title": "Read Only Access", - "params": [ - { - "id": "au-9.6_prm_1", - "label": "organization-defined subset of privileged users" - } - ], - "props": [ - { - "name": "label", - "value": "AU-9(6)" - }, - { - "name": "sort-id", - "value": "au-09.06" - } - ], - "parts": [ - { - "id": "au-9.6_smt", - "name": "statement", - "prose": "The organization authorizes read-only access to audit information to {{ insert: param, au-9.6_prm_1 }}." - }, - { - "id": "au-9.6_gdn", - "name": "guidance", - "prose": "Restricting privileged user authorizations to read-only helps to limit the potential damage to organizations that could be initiated by such users (e.g., deleting audit records to cover up malicious activity)." - }, - { - "id": "au-9.6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "au-9.6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9(6)[1]" - } - ], - "prose": "defines the subset of privileged users to be authorized read-only access to audit information; and" - }, - { - "id": "au-9.6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-9(6)[2]" - } - ], - "prose": "authorizes read-only access to audit information to the organization-defined subset of privileged users." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\naccess control policy and procedures\n\nprocedures addressing protection of audit information\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation, system-generated list of privileged users with read-only access to audit information\n\naccess authorizations\n\naccess control list\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms managing access to audit information" - } - ] - } - ] - } - ] - }, - { - "id": "au-10", - "class": "SP800-53", - "title": "Non-repudiation", - "params": [ - { - "id": "au-10_prm_1", - "label": "organization-defined actions to be covered by non-repudiation" - } - ], - "props": [ - { - "name": "label", - "value": "AU-10" - }, - { - "name": "sort-id", - "value": "au-10" - } - ], - "parts": [ - { - "id": "au-10_smt", - "name": "statement", - "prose": "The information system protects against an individual (or process acting on behalf of an individual) falsely denying having performed {{ insert: param, au-10_prm_1 }}." - }, - { - "id": "au-10_gdn", - "name": "guidance", - "prose": "Types of individual actions covered by non-repudiation include, for example, creating information, sending and receiving messages, approving information (e.g., indicating concurrence or signing a contract). Non-repudiation protects individuals against later claims by: (i) authors of not having authored particular documents; (ii) senders of not having transmitted messages; (iii) receivers of not having received messages; or (iv) signatories of not having signed documents. Non-repudiation services can be used to determine if information originated from a particular individual, or if an individual took specific actions (e.g., sending an email, signing a contract, approving a procurement request) or received specific information. Organizations obtain non-repudiation services by employing various techniques or mechanisms (e.g., digital signatures, digital message receipts).", - "links": [ - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#sc-16", - "rel": "related" - }, - { - "href": "#sc-17", - "rel": "related" - }, - { - "href": "#sc-23", - "rel": "related" - } - ] - }, - { - "id": "au-10_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-10_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10[1]" - } - ], - "prose": "the organization defines actions to be covered by non-repudiation; and" - }, - { - "id": "au-10_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10[2]" - } - ], - "prose": "the information system protects against an individual (or process acting on behalf of an individual) falsely denying having performed organization-defined actions to be covered by non-repudiation." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing non-repudiation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing non-repudiation capability" - } - ] - } - ], - "controls": [ - { - "id": "au-10.1", - "class": "SP800-53-enhancement", - "title": "Association of Identities", - "params": [ - { - "id": "au-10.1_prm_1", - "label": "organization-defined strength of binding" - } - ], - "props": [ - { - "name": "label", - "value": "AU-10(1)" - }, - { - "name": "sort-id", - "value": "au-10.01" - } - ], - "parts": [ - { - "id": "au-10.1_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "au-10.1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Binds the identity of the information producer with the information to {{ insert: param, au-10.1_prm_1 }}; and" - }, - { - "id": "au-10.1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Provides the means for authorized individuals to determine the identity of the producer of the information." - } - ] - }, - { - "id": "au-10.1_gdn", - "name": "guidance", - "prose": "This control enhancement supports audit requirements that provide organizational personnel with the means to identify who produced specific information in the event of an information transfer. Organizations determine and approve the strength of the binding between the information producer and the information based on the security category of the information and relevant risk factors.", - "links": [ - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-16", - "rel": "related" - } - ] - }, - { - "id": "au-10.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-10.1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(1)(a)" - } - ], - "parts": [ - { - "id": "au-10.1.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(1)(a)[1]" - } - ], - "prose": "the organization defines the strength of binding to be employed between the identity of the information producer and the information;" - }, - { - "id": "au-10.1.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(1)(a)[2]" - } - ], - "prose": "the information system binds the identity of the information producer with the information to the organization-defined strength of binding; and" - } - ], - "links": [ - { - "href": "#au-10.1_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "au-10.1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(1)(b)" - } - ], - "prose": "the information system provides the means for authorized individuals to determine the identity of the producer of the information.", - "links": [ - { - "href": "#au-10.1_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing non-repudiation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing non-repudiation capability" - } - ] - } - ] - }, - { - "id": "au-10.2", - "class": "SP800-53-enhancement", - "title": "Validate Binding of Information Producer Identity", - "params": [ - { - "id": "au-10.2_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "au-10.2_prm_2", - "label": "organization-defined actions" - } - ], - "props": [ - { - "name": "label", - "value": "AU-10(2)" - }, - { - "name": "sort-id", - "value": "au-10.02" - } - ], - "parts": [ - { - "id": "au-10.2_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "au-10.2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Validates the binding of the information producer identity to the information at {{ insert: param, au-10.2_prm_1 }}; and" - }, - { - "id": "au-10.2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Performs {{ insert: param, au-10.2_prm_2 }} in the event of a validation error." - } - ] - }, - { - "id": "au-10.2_gdn", - "name": "guidance", - "prose": "This control enhancement prevents the modification of information between production and review. The validation of bindings can be achieved, for example, by the use of cryptographic checksums. Organizations determine if validations are in response to user requests or generated automatically.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-16", - "rel": "related" - } - ] - }, - { - "id": "au-10.2_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-10.2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(2)(a)" - } - ], - "parts": [ - { - "id": "au-10.2.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(2)(a)[1]" - } - ], - "prose": "the organization defines the frequency to validate the binding of the information producer identity to the information;" - }, - { - "id": "au-10.2.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(2)(a)[2]" - } - ], - "prose": "the information system validates the binding of the information producer identity to the information at the organization-defined frequency; and" - } - ], - "links": [ - { - "href": "#au-10.2_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "au-10.2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(2)(b)" - } - ], - "parts": [ - { - "id": "au-10.2.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(2)(b)[1]" - } - ], - "prose": "the organization defines actions to be performed in the event of a validation error; and" - }, - { - "id": "au-10.2.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(2)(b)[2]" - } - ], - "prose": "the information system performs organization-defined actions in the event of a validation error." - } - ], - "links": [ - { - "href": "#au-10.2_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing non-repudiation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nvalidation records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing non-repudiation capability" - } - ] - } - ] - }, - { - "id": "au-10.3", - "class": "SP800-53-enhancement", - "title": "Chain of Custody", - "props": [ - { - "name": "label", - "value": "AU-10(3)" - }, - { - "name": "sort-id", - "value": "au-10.03" - } - ], - "parts": [ - { - "id": "au-10.3_smt", - "name": "statement", - "prose": "The information system maintains reviewer/releaser identity and credentials within the established chain of custody for all information reviewed or released." - }, - { - "id": "au-10.3_gdn", - "name": "guidance", - "prose": "Chain of custody is a process that tracks the movement of evidence through its collection, safeguarding, and analysis life cycle by documenting each person who handled the evidence, the date and time it was collected or transferred, and the purpose for the transfer. If the reviewer is a human or if the review function is automated but separate from the release/transfer function, the information system associates the identity of the reviewer of the information to be released with the information and the information label. In the case of human reviews, this control enhancement provides organizational officials the means to identify who reviewed and released the information. In the case of automated reviews, this control enhancement ensures that only approved review functions are employed.", - "links": [ - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-16", - "rel": "related" - } - ] - }, - { - "id": "au-10.3_obj", - "name": "objective", - "prose": "Determine if the information system:", - "parts": [ - { - "id": "au-10.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(3)[1]" - } - ], - "prose": "maintains reviewer/releaser identity within the established chain of custody for all information reviewed;" - }, - { - "id": "au-10.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(3)[2]" - } - ], - "prose": "maintains reviewer/releaser identity within the established chain of custody for all information released;" - }, - { - "id": "au-10.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(3)[3]" - } - ], - "prose": "maintains reviewer/releaser credentials within the established chain of custody for all information reviewed; and" - }, - { - "id": "au-10.3_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(3)[4]" - } - ], - "prose": "maintains reviewer/releaser credentials within the established chain of custody for all information released." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing non-repudiation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nrecords of information reviews and releases\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing non-repudiation capability" - } - ] - } - ] - }, - { - "id": "au-10.4", - "class": "SP800-53-enhancement", - "title": "Validate Binding of Information Reviewer Identity", - "params": [ - { - "id": "au-10.4_prm_1", - "label": "organization-defined security domains" - }, - { - "id": "au-10.4_prm_2", - "label": "organization-defined actions" - } - ], - "props": [ - { - "name": "label", - "value": "AU-10(4)" - }, - { - "name": "sort-id", - "value": "au-10.04" - } - ], - "parts": [ - { - "id": "au-10.4_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "au-10.4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Validates the binding of the information reviewer identity to the information at the transfer or release points prior to release/transfer between {{ insert: param, au-10.4_prm_1 }}; and" - }, - { - "id": "au-10.4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Performs {{ insert: param, au-10.4_prm_2 }} in the event of a validation error." - } - ] - }, - { - "id": "au-10.4_gdn", - "name": "guidance", - "prose": "This control enhancement prevents the modification of information between review and transfer/release. The validation of bindings can be achieved, for example, by the use of cryptographic checksums. Organizations determine validations are in response to user requests or generated automatically.", - "links": [ - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-16", - "rel": "related" - } - ] - }, - { - "id": "au-10.4_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-10.4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(4)(a)" - } - ], - "parts": [ - { - "id": "au-10.4.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(4)(a)[1]" - } - ], - "prose": "the organization defines security domains for which the binding of the information reviewer identity to the information is to be validated at the transfer or release points prior to release/transfer between such domains;" - }, - { - "id": "au-10.4.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(4)(a)[2]" - } - ], - "prose": "the information system validates the binding of the information reviewer identity to the information at the transfer or release points prior to release/transfer between organization-defined security domains;" - } - ], - "links": [ - { - "href": "#au-10.4_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "au-10.4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(4)(b)" - } - ], - "parts": [ - { - "id": "au-10.4.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(4)(b)[1]" - } - ], - "prose": "the organization defines actions to be performed in the event of a validation error; and" - }, - { - "id": "au-10.4.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-10(4)(b)[2]" - } - ], - "prose": "the information system performs organization-defined actions in the event of a validation error." - } - ], - "links": [ - { - "href": "#au-10.4_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing non-repudiation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nvalidation records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing non-repudiation capability" - } - ] - } - ] - }, - { - "id": "au-10.5", - "class": "SP800-53-enhancement", - "title": "Digital Signatures", - "props": [ - { - "name": "label", - "value": "AU-10(5)" - }, - { - "name": "sort-id", - "value": "au-10.05" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#si-7", - "rel": "incorporated-into" - } - ] - } - ] - }, - { - "id": "au-11", - "class": "SP800-53", - "title": "Audit Record Retention", - "params": [ - { - "id": "au-11_prm_1", - "label": "organization-defined time period consistent with records retention policy" - } - ], - "props": [ - { - "name": "label", - "value": "AU-11" - }, - { - "name": "sort-id", - "value": "au-11" - } - ], - "parts": [ - { - "id": "au-11_smt", - "name": "statement", - "prose": "The organization retains audit records for {{ insert: param, au-11_prm_1 }} to provide support for after-the-fact investigations of security incidents and to meet regulatory and organizational information retention requirements." - }, - { - "id": "au-11_gdn", - "name": "guidance", - "prose": "Organizations retain audit records until it is determined that they are no longer needed for administrative, legal, audit, or other operational purposes. This includes, for example, retention and availability of audit records relative to Freedom of Information Act (FOIA) requests, subpoenas, and law enforcement actions. Organizations develop standard categories of audit records relative to such types of actions and standard response processes for each type of action. The National Archives and Records Administration (NARA) General Records Schedules provide federal policy on record retention.", - "links": [ - { - "href": "#au-4", - "rel": "related" - }, - { - "href": "#au-5", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "#mp-6", - "rel": "related" - } - ] - }, - { - "id": "au-11_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "au-11_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-11[1]" - } - ], - "prose": "defines a time period to retain audit records that is consistent with records retention policy;" - }, - { - "id": "au-11_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-11[2]" - } - ], - "prose": "retains audit records for the organization-defined time period consistent with records retention policy to:", - "parts": [ - { - "id": "au-11_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-11[2][a]" - } - ], - "prose": "provide support for after-the-fact investigations of security incidents; and" - }, - { - "id": "au-11_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-11[2][b]" - } - ], - "prose": "meet regulatory and organizational information retention requirements." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\naudit record retention policy and procedures\n\nsecurity plan\n\norganization-defined retention period for audit records\n\naudit record archives\n\naudit logs\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit record retention responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - } - ], - "controls": [ - { - "id": "au-11.1", - "class": "SP800-53-enhancement", - "title": "Long-term Retrieval Capability", - "params": [ - { - "id": "au-11.1_prm_1", - "label": "organization-defined measures" - } - ], - "props": [ - { - "name": "label", - "value": "AU-11(1)" - }, - { - "name": "sort-id", - "value": "au-11.01" - } - ], - "parts": [ - { - "id": "au-11.1_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, au-11.1_prm_1 }} to ensure that long-term audit records generated by the information system can be retrieved." - }, - { - "id": "au-11.1_gdn", - "name": "guidance", - "prose": "Measures employed by organizations to help facilitate the retrieval of audit records include, for example, converting records to newer formats, retaining equipment capable of reading the records, and retaining necessary documentation to help organizational personnel understand how to interpret the records." - }, - { - "id": "au-11.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "au-11.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-11(1)[1]" - } - ], - "prose": "defines measures to be employed to ensure that long-term audit records generated by the information system can be retrieved; and" - }, - { - "id": "au-11.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-11(1)[2]" - } - ], - "prose": "employs organization-defined measures to ensure that long-term audit records generated by the information system can be retrieved." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\naudit record retention policy and procedures\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\naudit record archives\n\naudit logs\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit record retention responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing audit record retention capability" - } - ] - } - ] - } - ] - }, - { - "id": "au-12", - "class": "SP800-53", - "title": "Audit Generation", - "params": [ - { - "id": "au-12_prm_1", - "label": "organization-defined information system components" - }, - { - "id": "au-12_prm_2", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "AU-12" - }, - { - "name": "sort-id", - "value": "au-12" - } - ], - "parts": [ - { - "id": "au-12_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "au-12_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Provides audit record generation capability for the auditable events defined in AU-2 a. at {{ insert: param, au-12_prm_1 }};" - }, - { - "id": "au-12_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Allows {{ insert: param, au-12_prm_2 }} to select which auditable events are to be audited by specific components of the information system; and" - }, - { - "id": "au-12_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Generates audit records for the events defined in AU-2 d. with the content defined in AU-3." - } - ] - }, - { - "id": "au-12_gdn", - "name": "guidance", - "prose": "Audit records can be generated from many different information system components. The list of audited events is the set of events for which audits are to be generated. These events are typically a subset of all events for which the information system is capable of generating audit records.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-3", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-7", - "rel": "related" - } - ] - }, - { - "id": "au-12_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-12.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-12(a)" - } - ], - "parts": [ - { - "id": "au-12.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-12(a)[1]" - } - ], - "prose": "the organization defines the information system components which are to provide audit record generation capability for the auditable events defined in AU-2a;" - }, - { - "id": "au-12.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-12(a)[2]" - } - ], - "prose": "the information system provides audit record generation capability, for the auditable events defined in AU-2a, at organization-defined information system components;" - } - ] - }, - { - "id": "au-12.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-12(b)" - } - ], - "parts": [ - { - "id": "au-12.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-12(b)[1]" - } - ], - "prose": "the organization defines the personnel or roles allowed to select which auditable events are to be audited by specific components of the information system;" - }, - { - "id": "au-12.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-12(b)[2]" - } - ], - "prose": "the information system allows the organization-defined personnel or roles to select which auditable events are to be audited by specific components of the system; and" - } - ] - }, - { - "id": "au-12.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-12(c)" - } - ], - "prose": "the information system generates audit records for the events defined in AU-2d with the content in defined in AU-3." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit record generation\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of auditable events\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit record generation responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing audit record generation capability" - } - ] - } - ], - "controls": [ - { - "id": "au-12.1", - "class": "SP800-53-enhancement", - "title": "System-wide / Time-correlated Audit Trail", - "params": [ - { - "id": "au-12.1_prm_1", - "label": "organization-defined information system components" - }, - { - "id": "au-12.1_prm_2", - "label": "organization-defined level of tolerance for the relationship between time stamps of individual records in the audit trail" - } - ], - "props": [ - { - "name": "label", - "value": "AU-12(1)" - }, - { - "name": "sort-id", - "value": "au-12.01" - } - ], - "parts": [ - { - "id": "au-12.1_smt", - "name": "statement", - "prose": "The information system compiles audit records from {{ insert: param, au-12.1_prm_1 }} into a system-wide (logical or physical) audit trail that is time-correlated to within {{ insert: param, au-12.1_prm_2 }}." - }, - { - "id": "au-12.1_gdn", - "name": "guidance", - "prose": "Audit trails are time-correlated if the time stamps in the individual audit records can be reliably related to the time stamps in other audit records to achieve a time ordering of the records within organizational tolerances.", - "links": [ - { - "href": "#au-8", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - } - ] - }, - { - "id": "au-12.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-12.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-12(1)[1]" - } - ], - "prose": "the organization defines the information system components from which audit records are to be compiled into a system-wide (logical or physical) audit trail;" - }, - { - "id": "au-12.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-12(1)[2]" - } - ], - "prose": "the organization defines the level of tolerance for the relationship between time stamps of individual records in the audit trail; and" - }, - { - "id": "au-12.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-12(1)[3]" - } - ], - "prose": "the information system compiles audit records from organization-defined information system components into a system-wide (logical or physical) audit trail that is time-correlated to within the organization-defined level of tolerance for the relationship between time stamps of individual records in the audit trail." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit record generation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsystem-wide audit trail (logical or physical)\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit record generation responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing audit record generation capability" - } - ] - } - ] - }, - { - "id": "au-12.2", - "class": "SP800-53-enhancement", - "title": "Standardized Formats", - "props": [ - { - "name": "label", - "value": "AU-12(2)" - }, - { - "name": "sort-id", - "value": "au-12.02" - } - ], - "parts": [ - { - "id": "au-12.2_smt", - "name": "statement", - "prose": "The information system produces a system-wide (logical or physical) audit trail composed of audit records in a standardized format." - }, - { - "id": "au-12.2_gdn", - "name": "guidance", - "prose": "Audit information that is normalized to common standards promotes interoperability and exchange of such information between dissimilar devices and information systems. This facilitates production of event information that can be more readily analyzed and correlated. Standard formats for audit records include, for example, system log records and audit records compliant with Common Event Expressions (CEE). If logging mechanisms within information systems do not conform to standardized formats, systems may convert individual audit records into standardized formats when compiling system-wide audit trails." - }, - { - "id": "au-12.2_obj", - "name": "objective", - "prose": "Determine if the information system produces a system-wide (logical or physical) audit trail composed of audit records in a standardized format." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit record generation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsystem-wide audit trail (logical or physical)\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit record generation responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing audit record generation capability" - } - ] - } - ] - }, - { - "id": "au-12.3", - "class": "SP800-53-enhancement", - "title": "Changes by Authorized Individuals", - "params": [ - { - "id": "au-12.3_prm_1", - "label": "organization-defined individuals or roles" - }, - { - "id": "au-12.3_prm_2", - "label": "organization-defined information system components" - }, - { - "id": "au-12.3_prm_3", - "label": "organization-defined selectable event criteria" - }, - { - "id": "au-12.3_prm_4", - "label": "organization-defined time thresholds" - } - ], - "props": [ - { - "name": "label", - "value": "AU-12(3)" - }, - { - "name": "sort-id", - "value": "au-12.03" - } - ], - "parts": [ - { - "id": "au-12.3_smt", - "name": "statement", - "prose": "The information system provides the capability for {{ insert: param, au-12.3_prm_1 }} to change the auditing to be performed on {{ insert: param, au-12.3_prm_2 }} based on {{ insert: param, au-12.3_prm_3 }} within {{ insert: param, au-12.3_prm_4 }}." - }, - { - "id": "au-12.3_gdn", - "name": "guidance", - "prose": "This control enhancement enables organizations to extend or limit auditing as necessary to meet organizational requirements. Auditing that is limited to conserve information system resources may be extended to address certain threat situations. In addition, auditing may be limited to a specific set of events to facilitate audit reduction, analysis, and reporting. Organizations can establish time thresholds in which audit actions are changed, for example, near real-time, within minutes, or within hours.", - "links": [ - { - "href": "#au-7", - "rel": "related" - } - ] - }, - { - "id": "au-12.3_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "au-12.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-12(3)[1]" - } - ], - "prose": "the organization defines information system components on which auditing is to be performed;" - }, - { - "id": "au-12.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-12(3)[2]" - } - ], - "prose": "the organization defines individuals or roles authorized to change the auditing to be performed on organization-defined information system components;" - }, - { - "id": "au-12.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-12(3)[3]" - } - ], - "prose": "the organization defines time thresholds within which organization-defined individuals or roles can change the auditing to be performed on organization-defined information system components;" - }, - { - "id": "au-12.3_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-12(3)[4]" - } - ], - "prose": "the organization defines selectable event criteria that support the capability for organization-defined individuals or roles to change the auditing to be performed on organization-defined information system components; and" - }, - { - "id": "au-12.3_obj.5", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-12(3)[5]" - } - ], - "prose": "the information system provides the capability for organization-defined individuals or roles to change the auditing to be performed on organization-defined information system components based on organization-defined selectable event criteria within organization-defined time thresholds." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit record generation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsystem-generated list of individuals or roles authorized to change auditing to be performed\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with audit record generation responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing audit record generation capability" - } - ] - } - ] - } - ] - }, - { - "id": "au-13", - "class": "SP800-53", - "title": "Monitoring for Information Disclosure", - "params": [ - { - "id": "au-13_prm_1", - "label": "organization-defined open source information and/or information sites" - }, - { - "id": "au-13_prm_2", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "AU-13" - }, - { - "name": "sort-id", - "value": "au-13" - } - ], - "parts": [ - { - "id": "au-13_smt", - "name": "statement", - "prose": "The organization monitors {{ insert: param, au-13_prm_1 }} {{ insert: param, au-13_prm_2 }} for evidence of unauthorized disclosure of organizational information." - }, - { - "id": "au-13_gdn", - "name": "guidance", - "prose": "Open source information includes, for example, social networking sites.", - "links": [ - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - } - ] - }, - { - "id": "au-13_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "au-13_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-13[1]" - } - ], - "prose": "defines open source information and/or information sites to be monitored for evidence of unauthorized disclosure of organizational information;" - }, - { - "id": "au-13_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-13[2]" - } - ], - "prose": "defines a frequency to monitor organization-defined open source information and/or information sites for evidence of unauthorized disclosure of organizational information; and" - }, - { - "id": "au-13_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-13[3]" - } - ], - "prose": "monitors organization-defined open source information and/or information sites for evidence of unauthorized disclosure of organizational information with the organization-defined frequency." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing information disclosure monitoring\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nmonitoring records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for monitoring open source information and/or information sites\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing monitoring for information disclosure" - } - ] - } - ], - "controls": [ - { - "id": "au-13.1", - "class": "SP800-53-enhancement", - "title": "Use of Automated Tools", - "props": [ - { - "name": "label", - "value": "AU-13(1)" - }, - { - "name": "sort-id", - "value": "au-13.01" - } - ], - "parts": [ - { - "id": "au-13.1_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to determine if organizational information has been disclosed in an unauthorized manner." - }, - { - "id": "au-13.1_gdn", - "name": "guidance", - "prose": "Automated mechanisms can include, for example, automated scripts to monitor new posts on selected websites, and commercial services providing notifications and alerts to organizations." - }, - { - "id": "au-13.1_obj", - "name": "objective", - "prose": "Determine if the organization employs automated mechanisms to determine if organizational information has been disclosed in an unauthorized manner." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing information disclosure monitoring\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nautomated monitoring tools\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for monitoring information disclosures\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing monitoring for information disclosure" - } - ] - } - ] - }, - { - "id": "au-13.2", - "class": "SP800-53-enhancement", - "title": "Review of Monitored Sites", - "params": [ - { - "id": "au-13.2_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "AU-13(2)" - }, - { - "name": "sort-id", - "value": "au-13.02" - } - ], - "parts": [ - { - "id": "au-13.2_smt", - "name": "statement", - "prose": "The organization reviews the open source information sites being monitored {{ insert: param, au-13.2_prm_1 }}." - }, - { - "id": "au-13.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "au-13.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-13(2)[1]" - } - ], - "prose": "defines a frequency to review the open source information sites being monitored; and" - }, - { - "id": "au-13.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-13(2)[2]" - } - ], - "prose": "reviews the open source information sites being monitored with the organization-defined frequency." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing information disclosure monitoring\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nreviews for open source information sites being monitored\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for monitoring open source information sites\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing monitoring for information disclosure" - } - ] - } - ] - } - ] - }, - { - "id": "au-14", - "class": "SP800-53", - "title": "Session Audit", - "props": [ - { - "name": "label", - "value": "AU-14" - }, - { - "name": "sort-id", - "value": "au-14" - } - ], - "parts": [ - { - "id": "au-14_smt", - "name": "statement", - "prose": "The information system provides the capability for authorized users to select a user session to capture/record or view/hear." - }, - { - "id": "au-14_gdn", - "name": "guidance", - "prose": "Session audits include, for example, monitoring keystrokes, tracking websites visited, and recording information and/or file transfers. Session auditing activities are developed, integrated, and used in consultation with legal counsel in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, or standards.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#au-4", - "rel": "related" - }, - { - "href": "#au-5", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "#au-11", - "rel": "related" - } - ] - }, - { - "id": "au-14_obj", - "name": "objective", - "prose": "Determine if the information system provides the capability for authorized users to select a user session to:", - "parts": [ - { - "id": "au-14_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-14[1]" - } - ], - "prose": "capture/record; and/or" - }, - { - "id": "au-14_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-14[2]" - } - ], - "prose": "view/hear." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing user session auditing\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing user session auditing capability" - } - ] - } - ], - "controls": [ - { - "id": "au-14.1", - "class": "SP800-53-enhancement", - "title": "System Start-up", - "props": [ - { - "name": "label", - "value": "AU-14(1)" - }, - { - "name": "sort-id", - "value": "au-14.01" - } - ], - "parts": [ - { - "id": "au-14.1_smt", - "name": "statement", - "prose": "The information system initiates session audits at system start-up." - }, - { - "id": "au-14.1_obj", - "name": "objective", - "prose": "Determine if the information system initiates session audits at system start-up." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing user session auditing\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing user session auditing capability" - } - ] - } - ] - }, - { - "id": "au-14.2", - "class": "SP800-53-enhancement", - "title": "Capture/record and Log Content", - "props": [ - { - "name": "label", - "value": "AU-14(2)" - }, - { - "name": "sort-id", - "value": "au-14.02" - } - ], - "parts": [ - { - "id": "au-14.2_smt", - "name": "statement", - "prose": "The information system provides the capability for authorized users to capture/record and log content related to a user session." - }, - { - "id": "au-14.2_obj", - "name": "objective", - "prose": "Determine if the information system provides the capability for authorized users to:", - "parts": [ - { - "id": "au-14.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-14(2)[1]" - } - ], - "prose": "capture/record content related to a user session; and" - }, - { - "id": "au-14.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-14(2)[2]" - } - ], - "prose": "log content related to a user session." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing user session auditing\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing user session auditing capability" - } - ] - } - ] - }, - { - "id": "au-14.3", - "class": "SP800-53-enhancement", - "title": "Remote Viewing / Listening", - "props": [ - { - "name": "label", - "value": "AU-14(3)" - }, - { - "name": "sort-id", - "value": "au-14.03" - } - ], - "parts": [ - { - "id": "au-14.3_smt", - "name": "statement", - "prose": "The information system provides the capability for authorized users to remotely view/hear all content related to an established user session in real time." - }, - { - "id": "au-14.3_obj", - "name": "objective", - "prose": "Determine if the information system provides the capability for authorized users to remotely view/hear all content related to an established user session in real time." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing user session auditing\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing user session auditing capability" - } - ] - } - ] - } - ] - }, - { - "id": "au-15", - "class": "SP800-53", - "title": "Alternate Audit Capability", - "params": [ - { - "id": "au-15_prm_1", - "label": "organization-defined alternate audit functionality" - } - ], - "props": [ - { - "name": "label", - "value": "AU-15" - }, - { - "name": "sort-id", - "value": "au-15" - } - ], - "parts": [ - { - "id": "au-15_smt", - "name": "statement", - "prose": "The organization provides an alternate audit capability in the event of a failure in primary audit capability that provides {{ insert: param, au-15_prm_1 }}." - }, - { - "id": "au-15_gdn", - "name": "guidance", - "prose": "Since an alternate audit capability may be a short-term protection employed until the failure in the primary auditing capability is corrected, organizations may determine that the alternate audit capability need only provide a subset of the primary audit functionality that is impacted by the failure.", - "links": [ - { - "href": "#au-5", - "rel": "related" - } - ] - }, - { - "id": "au-15_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "au-15_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-15[1]" - } - ], - "prose": "defines alternative audit functionality to be provided in the event of a failure in primary audit capability; and" - }, - { - "id": "au-15_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-15[2]" - } - ], - "prose": "provides an alternative audit capability in the event of a failure in primary audit capability that provides organization-defined alternative audit functionality." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing alternate audit capability\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ntest records for alternative audit capability\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel responsible for providing alternate audit capability\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing alternative audit capability" - } - ] - } - ] - }, - { - "id": "au-16", - "class": "SP800-53", - "title": "Cross-organizational Auditing", - "params": [ - { - "id": "au-16_prm_1", - "label": "organization-defined methods" - }, - { - "id": "au-16_prm_2", - "label": "organization-defined audit information" - } - ], - "props": [ - { - "name": "label", - "value": "AU-16" - }, - { - "name": "sort-id", - "value": "au-16" - } - ], - "parts": [ - { - "id": "au-16_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, au-16_prm_1 }} for coordinating {{ insert: param, au-16_prm_2 }} among external organizations when audit information is transmitted across organizational boundaries." - }, - { - "id": "au-16_gdn", - "name": "guidance", - "prose": "When organizations use information systems and/or services of external organizations, the auditing capability necessitates a coordinated approach across organizations. For example, maintaining the identity of individuals that requested particular services across organizational boundaries may often be very difficult, and doing so may prove to have significant performance ramifications. Therefore, it is often the case that cross-organizational auditing (e.g., the type of auditing capability provided by service-oriented architectures) simply captures the identity of individuals issuing requests at the initial information system, and subsequent systems record that the requests emanated from authorized individuals.", - "links": [ - { - "href": "#au-6", - "rel": "related" - } - ] - }, - { - "id": "au-16_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "au-16_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-16[1]" - } - ], - "prose": "defines audit information to be coordinated among external organizations when audit information is transmitted across organizational boundaries;" - }, - { - "id": "au-16_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-16[2]" - } - ], - "prose": "defines methods for coordinating organization-defined audit information among external organizations when audit information is transmitted across organizational boundaries; and" - }, - { - "id": "au-16_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-16[3]" - } - ], - "prose": "employs organization-defined methods for coordinating organization-defined audit information among external organizations when audit information is transmitted across organizational boundaries." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing methods for coordinating audit information among external organizations\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nmethods for coordinating audit information among external organizations\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for coordinating audit information among external organizations\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing cross-organizational auditing (if applicable)" - } - ] - } - ], - "controls": [ - { - "id": "au-16.1", - "class": "SP800-53-enhancement", - "title": "Identity Preservation", - "props": [ - { - "name": "label", - "value": "AU-16(1)" - }, - { - "name": "sort-id", - "value": "au-16.01" - } - ], - "parts": [ - { - "id": "au-16.1_smt", - "name": "statement", - "prose": "The organization requires that the identity of individuals be preserved in cross-organizational audit trails." - }, - { - "id": "au-16.1_gdn", - "name": "guidance", - "prose": "This control enhancement applies when there is a need to be able to trace actions that are performed across organizational boundaries to a specific individual." - }, - { - "id": "au-16.1_obj", - "name": "objective", - "prose": "Determine if the organization requires that the identity of individuals be preserved in cross- organizational audit trails." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing cross-organizational audit trails\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with cross-organizational audit responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing cross-organizational auditing (if applicable)" - } - ] - } - ] - }, - { - "id": "au-16.2", - "class": "SP800-53-enhancement", - "title": "Sharing of Audit Information", - "params": [ - { - "id": "au-16.2_prm_1", - "label": "organization-defined organizations" - }, - { - "id": "au-16.2_prm_2", - "label": "organization-defined cross-organizational sharing agreements" - } - ], - "props": [ - { - "name": "label", - "value": "AU-16(2)" - }, - { - "name": "sort-id", - "value": "au-16.02" - } - ], - "parts": [ - { - "id": "au-16.2_smt", - "name": "statement", - "prose": "The organization provides cross-organizational audit information to {{ insert: param, au-16.2_prm_1 }} based on {{ insert: param, au-16.2_prm_2 }}." - }, - { - "id": "au-16.2_gdn", - "name": "guidance", - "prose": "Because of the distributed nature of the audit information, cross-organization sharing of audit information may be essential for effective analysis of the auditing being performed. For example, the audit records of one organization may not provide sufficient information to determine the appropriate or inappropriate use of organizational information resources by individuals in other organizations. In some instances, only the home organizations of individuals have the appropriate knowledge to make such determinations, thus requiring the sharing of audit information among organizations." - }, - { - "id": "au-16.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "au-16.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-16(2)[1]" - } - ], - "prose": "defines organizations with whom cross-organizational audit information is to be shared;" - }, - { - "id": "au-16.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-16(2)[2]" - } - ], - "prose": "defines cross-organizational sharing agreements to be used when providing cross-organizational audit information to organization-defined organizations; and" - }, - { - "id": "au-16.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "AU-16(2)[3]" - } - ], - "prose": "provides cross-organizational audit information to organization-defined organizations based on organization-defined cross-organizational sharing agreements." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Audit and accountability policy\n\nprocedures addressing cross-organizational sharing of audit information\n\ncross-organizational sharing agreements\n\ndata sharing agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for sharing cross-organizational audit information\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - } - ] - } - ] - }, - { - "id": "ca", - "class": "family", - "title": "Security Assessment and Authorization", - "controls": [ - { - "id": "ca-1", - "class": "SP800-53", - "title": "Security Assessment and Authorization Policy and Procedures", - "params": [ - { - "id": "ca-1_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "ca-1_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "ca-1_prm_3", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "CA-1" - }, - { - "name": "sort-id", - "value": "ca-01" - } - ], - "links": [ - { - "href": "#5c201b63-0768-417b-ac22-3f014e3941b2", - "rel": "reference" - }, - { - "href": "#0a0c26b6-fd44-4274-8b36-93442d49d998", - "rel": "reference" - }, - { - "href": "#cd4cf751-3312-4a55-b1a9-fad2f1db9119", - "rel": "reference" - }, - { - "href": "#9cb3d8fe-2127-48ba-821e-cdd2d7aee921", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ca-1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ca-1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops, documents, and disseminates to {{ insert: param, ca-1_prm_1 }}:", - "parts": [ - { - "id": "ca-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "A security assessment and authorization policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "ca-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the security assessment and authorization policy and associated security assessment and authorization controls; and" - } - ] - }, - { - "id": "ca-1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the current:", - "parts": [ - { - "id": "ca-1_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Security assessment and authorization policy {{ insert: param, ca-1_prm_2 }}; and" - }, - { - "id": "ca-1_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Security assessment and authorization procedures {{ insert: param, ca-1_prm_3 }}." - } - ] - } - ] - }, - { - "id": "ca-1_gdn", - "name": "guidance", - "prose": "This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the CA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures.", - "links": [ - { - "href": "#pm-9", - "rel": "related" - } - ] - }, - { - "id": "ca-1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ca-1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(a)" - } - ], - "parts": [ - { - "id": "ca-1.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(a)(1)" - } - ], - "parts": [ - { - "id": "ca-1.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(a)(1)[1]" - } - ], - "prose": "develops and documents a security assessment and authorization policy that addresses:", - "parts": [ - { - "id": "ca-1.a.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(a)(1)[1][a]" - } - ], - "prose": "purpose;" - }, - { - "id": "ca-1.a.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(a)(1)[1][b]" - } - ], - "prose": "scope;" - }, - { - "id": "ca-1.a.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(a)(1)[1][c]" - } - ], - "prose": "roles;" - }, - { - "id": "ca-1.a.1_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(a)(1)[1][d]" - } - ], - "prose": "responsibilities;" - }, - { - "id": "ca-1.a.1_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(a)(1)[1][e]" - } - ], - "prose": "management commitment;" - }, - { - "id": "ca-1.a.1_obj.1.f", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(a)(1)[1][f]" - } - ], - "prose": "coordination among organizational entities;" - }, - { - "id": "ca-1.a.1_obj.1.g", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(a)(1)[1][g]" - } - ], - "prose": "compliance;" - } - ] - }, - { - "id": "ca-1.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(a)(1)[2]" - } - ], - "prose": "defines personnel or roles to whom the security assessment and authorization policy is to be disseminated;" - }, - { - "id": "ca-1.a.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(a)(1)[3]" - } - ], - "prose": "disseminates the security assessment and authorization policy to organization-defined personnel or roles;" - } - ] - }, - { - "id": "ca-1.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(a)(2)" - } - ], - "parts": [ - { - "id": "ca-1.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(a)(2)[1]" - } - ], - "prose": "develops and documents procedures to facilitate the implementation of the security assessment and authorization policy and associated assessment and authorization controls;" - }, - { - "id": "ca-1.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(a)(2)[2]" - } - ], - "prose": "defines personnel or roles to whom the procedures are to be disseminated;" - }, - { - "id": "ca-1.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(a)(2)[3]" - } - ], - "prose": "disseminates the procedures to organization-defined personnel or roles;" - } - ] - } - ] - }, - { - "id": "ca-1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(b)" - } - ], - "parts": [ - { - "id": "ca-1.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(b)(1)" - } - ], - "parts": [ - { - "id": "ca-1.b.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(b)(1)[1]" - } - ], - "prose": "defines the frequency to review and update the current security assessment and authorization policy;" - }, - { - "id": "ca-1.b.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(b)(1)[2]" - } - ], - "prose": "reviews and updates the current security assessment and authorization policy with the organization-defined frequency;" - } - ] - }, - { - "id": "ca-1.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(b)(2)" - } - ], - "parts": [ - { - "id": "ca-1.b.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(b)(2)[1]" - } - ], - "prose": "defines the frequency to review and update the current security assessment and authorization procedures; and" - }, - { - "id": "ca-1.b.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-1(b)(2)[2]" - } - ], - "prose": "reviews and updates the current security assessment and authorization procedures with the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security assessment and authorization policy and procedures\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security assessment and authorization responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "ca-2", - "class": "SP800-53", - "title": "Security Assessments", - "params": [ - { - "id": "ca-2_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "ca-2_prm_2", - "label": "organization-defined individuals or roles" - } - ], - "props": [ - { - "name": "label", - "value": "CA-2" - }, - { - "name": "sort-id", - "value": "ca-02" - } - ], - "links": [ - { - "href": "#c5034e0c-eba6-4ecd-a541-79f0678f4ba4", - "rel": "reference" - }, - { - "href": "#e85cdb3f-7f0a-4083-8639-f13f70d3760b", - "rel": "reference" - }, - { - "href": "#0a0c26b6-fd44-4274-8b36-93442d49d998", - "rel": "reference" - }, - { - "href": "#d480aa6a-7a88-424e-a10c-ad1c7870354b", - "rel": "reference" - }, - { - "href": "#cd4cf751-3312-4a55-b1a9-fad2f1db9119", - "rel": "reference" - }, - { - "href": "#c4691b88-57d1-463b-9053-2d0087913f31", - "rel": "reference" - }, - { - "href": "#cee2c6ca-0261-4a6f-b630-e41d8ffdd82b", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ca-2_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ca-2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops a security assessment plan that describes the scope of the assessment including:", - "parts": [ - { - "id": "ca-2_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Security controls and control enhancements under assessment;" - }, - { - "id": "ca-2_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Assessment procedures to be used to determine security control effectiveness; and" - }, - { - "id": "ca-2_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Assessment environment, assessment team, and assessment roles and responsibilities;" - } - ] - }, - { - "id": "ca-2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Assesses the security controls in the information system and its environment of operation {{ insert: param, ca-2_prm_1 }} to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting established security requirements;" - }, - { - "id": "ca-2_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Produces a security assessment report that documents the results of the assessment; and" - }, - { - "id": "ca-2_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Provides the results of the security control assessment to {{ insert: param, ca-2_prm_2 }}." - } - ] - }, - { - "id": "ca-2_gdn", - "name": "guidance", - "prose": "Organizations assess security controls in organizational information systems and the environments in which those systems operate as part of: (i) initial and ongoing security authorizations; (ii) FISMA annual assessments; (iii) continuous monitoring; and (iv) system development life cycle activities. Security assessments: (i) ensure that information security is built into organizational information systems; (ii) identify weaknesses and deficiencies early in the development process; (iii) provide essential information needed to make risk-based decisions as part of security authorization processes; and (iv) ensure compliance to vulnerability mitigation procedures. Assessments are conducted on the implemented security controls from Appendix F (main catalog) and Appendix G (Program Management controls) as documented in System Security Plans and Information Security Program Plans. Organizations can use other types of assessment activities such as vulnerability scanning and system monitoring to maintain the security posture of information systems during the entire life cycle. Security assessment reports document assessment results in sufficient detail as deemed necessary by organizations, to determine the accuracy and completeness of the reports and whether the security controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting security requirements. The FISMA requirement for assessing security controls at least annually does not require additional assessment activities to those activities already in place in organizational security authorization processes. Security assessment results are provided to the individuals or roles appropriate for the types of assessments being conducted. For example, assessments conducted in support of security authorization decisions are provided to authorizing officials or authorizing official designated representatives. To satisfy annual assessment requirements, organizations can use assessment results from the following sources: (i) initial or ongoing information system authorizations; (ii) continuous monitoring; or (iii) system development life cycle activities. Organizations ensure that security assessment results are current, relevant to the determination of security control effectiveness, and obtained with the appropriate level of assessor independence. Existing security control assessment results can be reused to the extent that the results are still valid and can also be supplemented with additional assessments as needed. Subsequent to initial authorizations and in accordance with OMB policy, organizations assess security controls during continuous monitoring. Organizations establish the frequency for ongoing security control assessments in accordance with organizational continuous monitoring strategies. Information Assurance Vulnerability Alerts provide useful examples of vulnerability mitigation procedures. External audits (e.g., audits by external entities such as regulatory agencies) are outside the scope of this control.", - "links": [ - { - "href": "#ca-5", - "rel": "related" - }, - { - "href": "#ca-6", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#pm-9", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#sa-11", - "rel": "related" - }, - { - "href": "#sa-12", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "ca-2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ca-2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(a)" - } - ], - "prose": "develops a security assessment plan that describes the scope of the assessment including:", - "parts": [ - { - "id": "ca-2.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(a)(1)" - } - ], - "prose": "security controls and control enhancements under assessment;" - }, - { - "id": "ca-2.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(a)(2)" - } - ], - "prose": "assessment procedures to be used to determine security control effectiveness;" - }, - { - "id": "ca-2.a.3_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(a)(3)" - } - ], - "parts": [ - { - "id": "ca-2.a.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(a)(3)[1]" - } - ], - "prose": "assessment environment;" - }, - { - "id": "ca-2.a.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(a)(3)[2]" - } - ], - "prose": "assessment team;" - }, - { - "id": "ca-2.a.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(a)(3)[3]" - } - ], - "prose": "assessment roles and responsibilities;" - } - ] - } - ] - }, - { - "id": "ca-2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(b)" - } - ], - "parts": [ - { - "id": "ca-2.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(b)[1]" - } - ], - "prose": "defines the frequency to assess the security controls in the information system and its environment of operation;" - }, - { - "id": "ca-2.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(b)[2]" - } - ], - "prose": "assesses the security controls in the information system with the organization-defined frequency to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting established security requirements;" - } - ] - }, - { - "id": "ca-2.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(c)" - } - ], - "prose": "produces a security assessment report that documents the results of the assessment;" - }, - { - "id": "ca-2.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(d)" - } - ], - "parts": [ - { - "id": "ca-2.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(d)[1]" - } - ], - "prose": "defines individuals or roles to whom the results of the security control assessment are to be provided; and" - }, - { - "id": "ca-2.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(d)[2]" - } - ], - "prose": "provides the results of the security control assessment to organization-defined individuals or roles." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security assessment and authorization policy\n\nprocedures addressing security assessment planning\n\nprocedures addressing security assessments\n\nsecurity assessment plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security assessment responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting security assessment, security assessment plan development, and/or security assessment reporting" - } - ] - } - ], - "controls": [ - { - "id": "ca-2.1", - "class": "SP800-53-enhancement", - "title": "Independent Assessors", - "params": [ - { - "id": "ca-2.1_prm_1", - "label": "organization-defined level of independence" - } - ], - "props": [ - { - "name": "label", - "value": "CA-2(1)" - }, - { - "name": "sort-id", - "value": "ca-02.01" - } - ], - "parts": [ - { - "id": "ca-2.1_smt", - "name": "statement", - "prose": "The organization employs assessors or assessment teams with {{ insert: param, ca-2.1_prm_1 }} to conduct security control assessments." - }, - { - "id": "ca-2.1_gdn", - "name": "guidance", - "prose": "Independent assessors or assessment teams are individuals or groups who conduct impartial assessments of organizational information systems. Impartiality implies that assessors are free from any perceived or actual conflicts of interest with regard to the development, operation, or management of the organizational information systems under assessment or to the determination of security control effectiveness. To achieve impartiality, assessors should not: (i) create a mutual or conflicting interest with the organizations where the assessments are being conducted; (ii) assess their own work; (iii) act as management or employees of the organizations they are serving; or (iv) place themselves in positions of advocacy for the organizations acquiring their services. Independent assessments can be obtained from elements within organizations or can be contracted to public or private sector entities outside of organizations. Authorizing officials determine the required level of independence based on the security categories of information systems and/or the ultimate risk to organizational operations, organizational assets, or individuals. Authorizing officials also determine if the level of assessor independence provides sufficient assurance that the results are sound and can be used to make credible, risk-based decisions. This includes determining whether contracted security assessment services have sufficient independence, for example, when information system owners are not directly involved in contracting processes or cannot unduly influence the impartiality of assessors conducting assessments. In special situations, for example, when organizations that own the information systems are small or organizational structures require that assessments are conducted by individuals that are in the developmental, operational, or management chain of system owners, independence in assessment processes can be achieved by ensuring that assessment results are carefully reviewed and analyzed by independent teams of experts to validate the completeness, accuracy, integrity, and reliability of the results. Organizations recognize that assessments performed for purposes other than direct support to authorization decisions are, when performed by assessors with sufficient independence, more likely to be useable for such decisions, thereby reducing the need to repeat assessments." - }, - { - "id": "ca-2.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ca-2.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(1)[1]" - } - ], - "prose": "defines the level of independence to be employed to conduct security control assessments; and" - }, - { - "id": "ca-2.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(1)[2]" - } - ], - "prose": "employs assessors or assessment teams with the organization-defined level of independence to conduct security control assessments." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security assessment and authorization policy\n\nprocedures addressing security assessments\n\nsecurity authorization package (including security plan, security assessment plan, security assessment report, plan of action and milestones, authorization statement)\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security assessment responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "ca-2.2", - "class": "SP800-53-enhancement", - "title": "Specialized Assessments", - "params": [ - { - "id": "ca-2.2_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "ca-2.2_prm_2", - "select": { - "choice": [ - "announced", - "unannounced" - ] - } - }, - { - "id": "ca-2.2_prm_3", - "select": { - "how-many": "one-or-more", - "choice": [ - "in-depth monitoring", - "vulnerability scanning", - "malicious user testing", - "insider threat assessment", - "performance/load testing", - " {{ insert: param, ca-2.2_prm_4 }} " - ] - } - }, - { - "id": "ca-2.2_prm_4", - "depends-on": "ca-2.2_prm_3", - "label": "organization-defined other forms of security assessment" - } - ], - "props": [ - { - "name": "label", - "value": "CA-2(2)" - }, - { - "name": "sort-id", - "value": "ca-02.02" - } - ], - "parts": [ - { - "id": "ca-2.2_smt", - "name": "statement", - "prose": "The organization includes as part of security control assessments, {{ insert: param, ca-2.2_prm_1 }}, {{ insert: param, ca-2.2_prm_2 }}, {{ insert: param, ca-2.2_prm_3 }}." - }, - { - "id": "ca-2.2_gdn", - "name": "guidance", - "prose": "Organizations can employ information system monitoring, insider threat assessments, malicious user testing, and other forms of testing (e.g., verification and validation) to improve readiness by exercising organizational capabilities and indicating current performance levels as a means of focusing actions to improve security. Organizations conduct assessment activities in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. Authorizing officials approve the assessment methods in coordination with the organizational risk executive function. Organizations can incorporate vulnerabilities uncovered during assessments into vulnerability remediation processes.", - "links": [ - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - } - ] - }, - { - "id": "ca-2.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ca-2.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(2)[1]" - } - ], - "prose": "selects one or more of the following forms of specialized security assessment to be included as part of security control assessments:", - "parts": [ - { - "id": "ca-2.2_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(2)[1][a]" - } - ], - "prose": "in-depth monitoring;" - }, - { - "id": "ca-2.2_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(2)[1][b]" - } - ], - "prose": "vulnerability scanning;" - }, - { - "id": "ca-2.2_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(2)[1][c]" - } - ], - "prose": "malicious user testing;" - }, - { - "id": "ca-2.2_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(2)[1][d]" - } - ], - "prose": "insider threat assessment;" - }, - { - "id": "ca-2.2_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(2)[1][e]" - } - ], - "prose": "performance/load testing; and/or" - }, - { - "id": "ca-2.2_obj.1.f", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(2)[1][f]" - } - ], - "prose": "other forms of organization-defined specialized security assessment;" - } - ] - }, - { - "id": "ca-2.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(2)[2]" - } - ], - "prose": "defines the frequency for conducting the selected form(s) of specialized security assessment;" - }, - { - "id": "ca-2.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(2)[3]" - } - ], - "prose": "defines whether the specialized security assessment will be announced or unannounced; and" - }, - { - "id": "ca-2.2_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(2)[4]" - } - ], - "prose": "conducts announced or unannounced organization-defined forms of specialized security assessments with the organization-defined frequency as part of security control assessments." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security assessment and authorization policy\n\nprocedures addressing security assessments\n\nsecurity plan\n\nsecurity assessment plan\n\nsecurity assessment report\n\nsecurity assessment evidence\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security assessment responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting security control assessment" - } - ] - } - ] - }, - { - "id": "ca-2.3", - "class": "SP800-53-enhancement", - "title": "External Organizations", - "params": [ - { - "id": "ca-2.3_prm_1", - "label": "organization-defined information system" - }, - { - "id": "ca-2.3_prm_2", - "label": "organization-defined external organization" - }, - { - "id": "ca-2.3_prm_3", - "label": "organization-defined requirements" - } - ], - "props": [ - { - "name": "label", - "value": "CA-2(3)" - }, - { - "name": "sort-id", - "value": "ca-02.03" - } - ], - "parts": [ - { - "id": "ca-2.3_smt", - "name": "statement", - "prose": "The organization accepts the results of an assessment of {{ insert: param, ca-2.3_prm_1 }} performed by {{ insert: param, ca-2.3_prm_2 }} when the assessment meets {{ insert: param, ca-2.3_prm_3 }}." - }, - { - "id": "ca-2.3_gdn", - "name": "guidance", - "prose": "Organizations may often rely on assessments of specific information systems by other (external) organizations. Utilizing such existing assessments (i.e., reusing existing assessment evidence) can significantly decrease the time and resources required for organizational assessments by limiting the amount of independent assessment activities that organizations need to perform. The factors that organizations may consider in determining whether to accept assessment results from external organizations can vary. Determinations for accepting assessment results can be based on, for example, past assessment experiences one organization has had with another organization, the reputation that organizations have with regard to assessments, the level of detail of supporting assessment documentation provided, or mandates imposed upon organizations by federal legislation, policies, or directives." - }, - { - "id": "ca-2.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ca-2.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(3)[1]" - } - ], - "prose": "defines an information system for which the results of a security assessment performed by an external organization are to be accepted;" - }, - { - "id": "ca-2.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(3)[2]" - } - ], - "prose": "defines an external organization from which to accept a security assessment performed on an organization-defined information system;" - }, - { - "id": "ca-2.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(3)[3]" - } - ], - "prose": "defines the requirements to be met by a security assessment performed by organization-defined external organization on organization-defined information system; and" - }, - { - "id": "ca-2.3_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-2(3)[4]" - } - ], - "prose": "accepts the results of an assessment of an organization-defined information system performed by an organization-defined external organization when the assessment meets organization-defined requirements." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security assessment and authorization policy\n\nprocedures addressing security assessments\n\nsecurity plan\n\nsecurity assessment requirements\n\nsecurity assessment plan\n\nsecurity assessment report\n\nsecurity assessment evidence\n\nplan of action and milestones\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security assessment responsibilities\n\norganizational personnel with information security responsibilities\n\npersonnel performing security assessments for the specified external organization" - } - ] - } - ] - } - ] - }, - { - "id": "ca-3", - "class": "SP800-53", - "title": "System Interconnections", - "params": [ - { - "id": "ca-3_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "CA-3" - }, - { - "name": "sort-id", - "value": "ca-03" - } - ], - "links": [ - { - "href": "#e85cdb3f-7f0a-4083-8639-f13f70d3760b", - "rel": "reference" - }, - { - "href": "#2711f068-734e-4afd-94ba-0b22247fbc88", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ca-3_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ca-3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Authorizes connections from the information system to other information systems through the use of Interconnection Security Agreements;" - }, - { - "id": "ca-3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Documents, for each interconnection, the interface characteristics, security requirements, and the nature of the information communicated; and" - }, - { - "id": "ca-3_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Reviews and updates Interconnection Security Agreements {{ insert: param, ca-3_prm_1 }}." - } - ] - }, - { - "id": "ca-3_gdn", - "name": "guidance", - "prose": "This control applies to dedicated connections between information systems (i.e., system interconnections) and does not apply to transitory, user-controlled connections such as email and website browsing. Organizations carefully consider the risks that may be introduced when information systems are connected to other systems with different security requirements and security controls, both within organizations and external to organizations. Authorizing officials determine the risk associated with information system connections and the appropriate controls employed. If interconnecting systems have the same authorizing official, organizations do not need to develop Interconnection Security Agreements. Instead, organizations can describe the interface characteristics between those interconnecting systems in their respective security plans. If interconnecting systems have different authorizing officials within the same organization, organizations can either develop Interconnection Security Agreements or describe the interface characteristics between systems in the security plans for the respective systems. Organizations may also incorporate Interconnection Security Agreement information into formal contracts, especially for interconnections established between federal agencies and nonfederal (i.e., private sector) organizations. Risk considerations also include information systems sharing the same networks. For certain technologies (e.g., space, unmanned aerial vehicles, and medical devices), there may be specialized connections in place during preoperational testing. Such connections may require Interconnection Security Agreements and be subject to additional security controls.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-20", - "rel": "related" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "#au-16", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "ca-3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ca-3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(a)" - } - ], - "prose": "authorizes connections from the information system to other information systems through the use of Interconnection Security Agreements;" - }, - { - "id": "ca-3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(b)" - } - ], - "prose": "documents, for each interconnection:", - "parts": [ - { - "id": "ca-3.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(b)[1]" - } - ], - "prose": "the interface characteristics;" - }, - { - "id": "ca-3.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(b)[2]" - } - ], - "prose": "the security requirements;" - }, - { - "id": "ca-3.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(b)[3]" - } - ], - "prose": "the nature of the information communicated;" - } - ] - }, - { - "id": "ca-3.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(c)" - } - ], - "parts": [ - { - "id": "ca-3.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(c)[1]" - } - ], - "prose": "defines the frequency to review and update Interconnection Security Agreements; and" - }, - { - "id": "ca-3.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(c)[2]" - } - ], - "prose": "reviews and updates Interconnection Security Agreements with the organization-defined frequency." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing information system connections\n\nsystem and communications protection policy\n\ninformation system Interconnection Security Agreements\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for developing, implementing, or approving information system interconnection agreements\n\norganizational personnel with information security responsibilities\n\npersonnel managing the system(s) to which the Interconnection Security Agreement applies" - } - ] - } - ], - "controls": [ - { - "id": "ca-3.1", - "class": "SP800-53-enhancement", - "title": "Unclassified National Security System Connections", - "params": [ - { - "id": "ca-3.1_prm_1", - "label": "organization-defined unclassified, national security system" - }, - { - "id": "ca-3.1_prm_2", - "label": "organization-defined boundary protection device" - } - ], - "props": [ - { - "name": "label", - "value": "CA-3(1)" - }, - { - "name": "sort-id", - "value": "ca-03.01" - } - ], - "parts": [ - { - "id": "ca-3.1_smt", - "name": "statement", - "prose": "The organization prohibits the direct connection of an {{ insert: param, ca-3.1_prm_1 }} to an external network without the use of {{ insert: param, ca-3.1_prm_2 }}." - }, - { - "id": "ca-3.1_gdn", - "name": "guidance", - "prose": "Organizations typically do not have control over external networks (e.g., the Internet). Approved boundary protection devices (e.g., routers, firewalls) mediate communications (i.e., information flows) between unclassified national security systems and external networks. This control enhancement is required for organizations processing, storing, or transmitting Controlled Unclassified Information (CUI)." - }, - { - "id": "ca-3.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ca-3.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(1)[1]" - } - ], - "prose": "defines an unclassified, national security system whose direct connection to an external network is to be prohibited without the use of approved boundary protection device;" - }, - { - "id": "ca-3.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(1)[2]" - } - ], - "prose": "defines a boundary protection device to be used to establish the direct connection of an organization-defined unclassified, national security system to an external network; and" - }, - { - "id": "ca-3.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(1)[3]" - } - ], - "prose": "prohibits the direct connection of an organization-defined unclassified, national security system to an external network without the use of an organization-defined boundary protection device." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing information system connections\n\nsystem and communications protection policy\n\ninformation system interconnection security agreements\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsecurity assessment report\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for managing direct connections to external networks\n\nnetwork administrators\n\norganizational personnel with information security responsibilities\n\npersonnel managing directly connected external networks" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting the management of external network connections" - } - ] - } - ] - }, - { - "id": "ca-3.2", - "class": "SP800-53-enhancement", - "title": "Classified National Security System Connections", - "params": [ - { - "id": "ca-3.2_prm_1", - "label": "organization-defined boundary protection device" - } - ], - "props": [ - { - "name": "label", - "value": "CA-3(2)" - }, - { - "name": "sort-id", - "value": "ca-03.02" - } - ], - "parts": [ - { - "id": "ca-3.2_smt", - "name": "statement", - "prose": "The organization prohibits the direct connection of a classified, national security system to an external network without the use of {{ insert: param, ca-3.2_prm_1 }}." - }, - { - "id": "ca-3.2_gdn", - "name": "guidance", - "prose": "Organizations typically do not have control over external networks (e.g., the Internet). Approved boundary protection devices (e.g., routers, firewalls) mediate communications (i.e., information flows) between classified national security systems and external networks. In addition, approved boundary protection devices (typically managed interface/cross-domain systems) provide information flow enforcement from information systems to external networks." - }, - { - "id": "ca-3.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ca-3.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(2)[1]" - } - ], - "prose": "defines a boundary protection device to be used to establish the direct connection of a classified, national security system to an external network; and" - }, - { - "id": "ca-3.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(2)[2]" - } - ], - "prose": "prohibits the direct connection of a classified, national security system to an external network without the use of an organization-defined boundary protection device." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing information system connections\n\nsystem and communications protection policy\n\ninformation system interconnection security agreements\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsecurity assessment report\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for managing direct connections to external networks\n\nnetwork administrators\n\norganizational personnel with information security responsibilities\n\npersonnel managing directly connected external networks" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting the management of external network connections" - } - ] - } - ] - }, - { - "id": "ca-3.3", - "class": "SP800-53-enhancement", - "title": "Unclassified Non-national Security System Connections", - "params": [ - { - "id": "ca-3.3_prm_1", - "label": "organization-defined unclassified, non-national security system" - }, - { - "id": "ca-3.3_prm_2", - "label": "Assignment; organization-defined boundary protection device" - } - ], - "props": [ - { - "name": "label", - "value": "CA-3(3)" - }, - { - "name": "sort-id", - "value": "ca-03.03" - } - ], - "parts": [ - { - "id": "ca-3.3_smt", - "name": "statement", - "prose": "The organization prohibits the direct connection of an {{ insert: param, ca-3.3_prm_1 }} to an external network without the use of {{ insert: param, ca-3.3_prm_2 }}." - }, - { - "id": "ca-3.3_gdn", - "name": "guidance", - "prose": "Organizations typically do not have control over external networks (e.g., the Internet). Approved boundary protection devices (e.g., routers, firewalls) mediate communications (i.e., information flows) between unclassified non-national security systems and external networks. This control enhancement is required for organizations processing, storing, or transmitting Controlled Unclassified Information (CUI)." - }, - { - "id": "ca-3.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ca-3.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(3)[1]" - } - ], - "prose": "defines an unclassified, non-national security system whose direct connection to an external network is to be prohibited without the use of approved boundary protection device;" - }, - { - "id": "ca-3.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(3)[2]" - } - ], - "prose": "defines a boundary protection device to be used to establish the direct connection of an organization-defined unclassified, non-national security system to an external network; and" - }, - { - "id": "ca-3.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(3)[3]" - } - ], - "prose": "prohibits the direct connection of an organization-defined unclassified, non-national security system to an external network without the use of an organization-defined boundary protection device." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing information system connections\n\nsystem and communications protection policy\n\ninformation system interconnection security agreements\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsecurity assessment report\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for managing direct connections to external networks\n\nnetwork administrators\n\norganizational personnel with information security responsibilities\n\npersonnel managing directly connected external networks" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting the management of external network connections" - } - ] - } - ] - }, - { - "id": "ca-3.4", - "class": "SP800-53-enhancement", - "title": "Connections to Public Networks", - "params": [ - { - "id": "ca-3.4_prm_1", - "label": "organization-defined information system" - } - ], - "props": [ - { - "name": "label", - "value": "CA-3(4)" - }, - { - "name": "sort-id", - "value": "ca-03.04" - } - ], - "parts": [ - { - "id": "ca-3.4_smt", - "name": "statement", - "prose": "The organization prohibits the direct connection of an {{ insert: param, ca-3.4_prm_1 }} to a public network." - }, - { - "id": "ca-3.4_gdn", - "name": "guidance", - "prose": "A public network is any network accessible to the general public including, for example, the Internet and organizational extranets with public access." - }, - { - "id": "ca-3.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ca-3.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(4)[1]" - } - ], - "prose": "defines an information system whose direct connection to a public network is to be prohibited; and" - }, - { - "id": "ca-3.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(4)[2]" - } - ], - "prose": "prohibits the direct connection of an organization-defined information system to a public network." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing information system connections\n\nsystem and communications protection policy\n\ninformation system interconnection security agreements\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsecurity assessment report\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting the management of public network connections" - } - ] - } - ] - }, - { - "id": "ca-3.5", - "class": "SP800-53-enhancement", - "title": "Restrictions On External System Connections", - "params": [ - { - "id": "ca-3.5_prm_1", - "select": { - "choice": [ - "allow-all, deny-by-exception", - "deny-all, permit-by-exception" - ] - } - }, - { - "id": "ca-3.5_prm_2", - "label": "organization-defined information systems" - } - ], - "props": [ - { - "name": "label", - "value": "CA-3(5)" - }, - { - "name": "sort-id", - "value": "ca-03.05" - } - ], - "parts": [ - { - "id": "ca-3.5_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, ca-3.5_prm_1 }} policy for allowing {{ insert: param, ca-3.5_prm_2 }} to connect to external information systems." - }, - { - "id": "ca-3.5_gdn", - "name": "guidance", - "prose": "Organizations can constrain information system connectivity to external domains (e.g., websites) by employing one of two policies with regard to such connectivity: (i) allow-all, deny by exception, also known as blacklisting (the weaker of the two policies); or (ii) deny-all, allow by exception, also known as whitelisting (the stronger of the two policies). For either policy, organizations determine what exceptions, if any, are acceptable.", - "links": [ - { - "href": "#cm-7", - "rel": "related" - } - ] - }, - { - "id": "ca-3.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ca-3.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(5)[1]" - } - ], - "prose": "defines information systems to be allowed to connect to external information systems;" - }, - { - "id": "ca-3.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(5)[2]" - } - ], - "prose": "employs one of the following policies for allowing organization-defined information systems to connect to external information systems:", - "parts": [ - { - "id": "ca-3.5_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(5)[2][a]" - } - ], - "prose": "allow-all policy;" - }, - { - "id": "ca-3.5_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(5)[2][b]" - } - ], - "prose": "deny-by-exception policy;" - }, - { - "id": "ca-3.5_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(5)[2][c]" - } - ], - "prose": "deny-all policy; or" - }, - { - "id": "ca-3.5_obj.2.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-3(5)[2][d]" - } - ], - "prose": "permit-by-exception policy." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing information system connections\n\nsystem and communications protection policy\n\ninformation system interconnection agreements\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsecurity assessment report\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for managing connections to external information systems\n\nnetwork administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing restrictions on external system connections" - } - ] - } - ] - } - ] - }, - { - "id": "ca-4", - "class": "SP800-53", - "title": "Security Certification", - "props": [ - { - "name": "label", - "value": "CA-4" - }, - { - "name": "sort-id", - "value": "ca-04" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#ca-2", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ca-5", - "class": "SP800-53", - "title": "Plan of Action and Milestones", - "params": [ - { - "id": "ca-5_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "CA-5" - }, - { - "name": "sort-id", - "value": "ca-05" - } - ], - "links": [ - { - "href": "#2c5884cd-7b96-425c-862a-99877e1cf909", - "rel": "reference" - }, - { - "href": "#0a0c26b6-fd44-4274-8b36-93442d49d998", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ca-5_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ca-5_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops a plan of action and milestones for the information system to document the organization’s planned remedial actions to correct weaknesses or deficiencies noted during the assessment of the security controls and to reduce or eliminate known vulnerabilities in the system; and" - }, - { - "id": "ca-5_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Updates existing plan of action and milestones {{ insert: param, ca-5_prm_1 }} based on the findings from security controls assessments, security impact analyses, and continuous monitoring activities." - } - ] - }, - { - "id": "ca-5_gdn", - "name": "guidance", - "prose": "Plans of action and milestones are key documents in security authorization packages and are subject to federal reporting requirements established by OMB.", - "links": [ - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#pm-4", - "rel": "related" - } - ] - }, - { - "id": "ca-5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ca-5.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-5(a)" - } - ], - "prose": "develops a plan of action and milestones for the information system to:", - "parts": [ - { - "id": "ca-5.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-5(a)[1]" - } - ], - "prose": "document the organization’s planned remedial actions to correct weaknesses or deficiencies noted during the assessment of the security controls;" - }, - { - "id": "ca-5.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-5(a)[2]" - } - ], - "prose": "reduce or eliminate known vulnerabilities in the system;" - } - ] - }, - { - "id": "ca-5.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-5(b)" - } - ], - "parts": [ - { - "id": "ca-5.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-5(b)[1]" - } - ], - "prose": "defines the frequency to update the existing plan of action and milestones;" - }, - { - "id": "ca-5.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-5(b)[2]" - } - ], - "prose": "updates the existing plan of action and milestones with the organization-defined frequency based on the findings from:", - "parts": [ - { - "id": "ca-5.b_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-5(b)[2][a]" - } - ], - "prose": "security controls assessments;" - }, - { - "id": "ca-5.b_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-5(b)[2][b]" - } - ], - "prose": "security impact analyses; and" - }, - { - "id": "ca-5.b_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-5(b)[2][c]" - } - ], - "prose": "continuous monitoring activities." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security assessment and authorization policy\n\nprocedures addressing plan of action and milestones\n\nsecurity plan\n\nsecurity assessment plan\n\nsecurity assessment report\n\nsecurity assessment evidence\n\nplan of action and milestones\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with plan of action and milestones development and implementation responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms for developing, implementing, and maintaining plan of action and milestones" - } - ] - } - ], - "controls": [ - { - "id": "ca-5.1", - "class": "SP800-53-enhancement", - "title": "Automation Support for Accuracy / Currency", - "props": [ - { - "name": "label", - "value": "CA-5(1)" - }, - { - "name": "sort-id", - "value": "ca-05.01" - } - ], - "parts": [ - { - "id": "ca-5.1_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to help ensure that the plan of action and milestones for the information system is accurate, up to date, and readily available." - }, - { - "id": "ca-5.1_obj", - "name": "objective", - "prose": "Determine if the organization employs automated mechanisms to help ensure that the plan of action and milestones for the information system is:", - "parts": [ - { - "id": "ca-5.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-5(1)[1]" - } - ], - "prose": "accurate;" - }, - { - "id": "ca-5.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-5(1)[2]" - } - ], - "prose": "up to date; and" - }, - { - "id": "ca-5.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-5(1)[3]" - } - ], - "prose": "readily available." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security assessment and authorization policy\n\nprocedures addressing plan of action and milestones\n\ninformation system design documentation, information system configuration settings and associated documentation\n\ninformation system audit records\n\nplan of action and milestones\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with plan of action and milestones development and implementation responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms for developing, implementing and maintaining plan of action and milestones" - } - ] - } - ] - } - ] - }, - { - "id": "ca-6", - "class": "SP800-53", - "title": "Security Authorization", - "params": [ - { - "id": "ca-6_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "CA-6" - }, - { - "name": "sort-id", - "value": "ca-06" - } - ], - "links": [ - { - "href": "#9f77f845-e3ea-4ca4-b2c0-aa9eedc214ab", - "rel": "reference" - }, - { - "href": "#bedb15b7-ec5c-4a68-807f-385125751fcd", - "rel": "reference" - }, - { - "href": "#0a0c26b6-fd44-4274-8b36-93442d49d998", - "rel": "reference" - }, - { - "href": "#cee2c6ca-0261-4a6f-b630-e41d8ffdd82b", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ca-6_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ca-6_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Assigns a senior-level executive or manager as the authorizing official for the information system;" - }, - { - "id": "ca-6_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Ensures that the authorizing official authorizes the information system for processing before commencing operations; and" - }, - { - "id": "ca-6_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Updates the security authorization {{ insert: param, ca-6_prm_1 }}." - } - ] - }, - { - "id": "ca-6_gdn", - "name": "guidance", - "prose": "Security authorizations are official management decisions, conveyed through authorization decision documents, by senior organizational officials or executives (i.e., authorizing officials) to authorize operation of information systems and to explicitly accept the risk to organizational operations and assets, individuals, other organizations, and the Nation based on the implementation of agreed-upon security controls. Authorizing officials provide budgetary oversight for organizational information systems or assume responsibility for the mission/business operations supported by those systems. The security authorization process is an inherently federal responsibility and therefore, authorizing officials must be federal employees. Through the security authorization process, authorizing officials assume responsibility and are accountable for security risks associated with the operation and use of organizational information systems. Accordingly, authorizing officials are in positions with levels of authority commensurate with understanding and accepting such information security-related risks. OMB policy requires that organizations conduct ongoing authorizations of information systems by implementing continuous monitoring programs. Continuous monitoring programs can satisfy three-year reauthorization requirements, so separate reauthorization processes are not necessary. Through the employment of comprehensive continuous monitoring processes, critical information contained in authorization packages (i.e., security plans, security assessment reports, and plans of action and milestones) is updated on an ongoing basis, providing authorizing officials and information system owners with an up-to-date status of the security state of organizational information systems and environments of operation. To reduce the administrative cost of security reauthorization, authorizing officials use the results of continuous monitoring processes to the maximum extent possible as the basis for rendering reauthorization decisions.", - "links": [ - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#pm-9", - "rel": "related" - }, - { - "href": "#pm-10", - "rel": "related" - } - ] - }, - { - "id": "ca-6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ca-6.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-6(a)" - } - ], - "prose": "assigns a senior-level executive or manager as the authorizing official for the information system;" - }, - { - "id": "ca-6.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-6(b)" - } - ], - "prose": "ensures that the authorizing official authorizes the information system for processing before commencing operations;" - }, - { - "id": "ca-6.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-6(c)" - } - ], - "parts": [ - { - "id": "ca-6.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-6(c)[1]" - } - ], - "prose": "defines the frequency to update the security authorization; and" - }, - { - "id": "ca-6.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-6(c)[2]" - } - ], - "prose": "updates the security authorization with the organization-defined frequency." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security assessment and authorization policy\n\nprocedures addressing security authorization\n\nsecurity authorization package (including security plan\n\nsecurity assessment report\n\nplan of action and milestones\n\nauthorization statement)\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security authorization responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms that facilitate security authorizations and updates" - } - ] - } - ] - }, - { - "id": "ca-7", - "class": "SP800-53", - "title": "Continuous Monitoring", - "params": [ - { - "id": "ca-7_prm_1", - "label": "organization-defined metrics" - }, - { - "id": "ca-7_prm_2", - "label": "organization-defined frequencies" - }, - { - "id": "ca-7_prm_3", - "label": "organization-defined frequencies" - }, - { - "id": "ca-7_prm_4", - "label": "organization-defined personnel or roles" - }, - { - "id": "ca-7_prm_5", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "CA-7" - }, - { - "name": "sort-id", - "value": "ca-07" - } - ], - "links": [ - { - "href": "#bedb15b7-ec5c-4a68-807f-385125751fcd", - "rel": "reference" - }, - { - "href": "#0a0c26b6-fd44-4274-8b36-93442d49d998", - "rel": "reference" - }, - { - "href": "#d480aa6a-7a88-424e-a10c-ad1c7870354b", - "rel": "reference" - }, - { - "href": "#cd4cf751-3312-4a55-b1a9-fad2f1db9119", - "rel": "reference" - }, - { - "href": "#c4691b88-57d1-463b-9053-2d0087913f31", - "rel": "reference" - }, - { - "href": "#cee2c6ca-0261-4a6f-b630-e41d8ffdd82b", - "rel": "reference" - }, - { - "href": "#8ade2fbe-e468-4ca8-9a40-54d7f23c32bb", - "rel": "reference" - }, - { - "href": "#2d8b14e9-c8b5-4d3d-8bdc-155078f3281b", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ca-7_smt", - "name": "statement", - "prose": "The organization develops a continuous monitoring strategy and implements a continuous monitoring program that includes:", - "parts": [ - { - "id": "ca-7_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Establishment of {{ insert: param, ca-7_prm_1 }} to be monitored;" - }, - { - "id": "ca-7_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Establishment of {{ insert: param, ca-7_prm_2 }} for monitoring and {{ insert: param, ca-7_prm_3 }} for assessments supporting such monitoring;" - }, - { - "id": "ca-7_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Ongoing security control assessments in accordance with the organizational continuous monitoring strategy;" - }, - { - "id": "ca-7_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Ongoing security status monitoring of organization-defined metrics in accordance with the organizational continuous monitoring strategy;" - }, - { - "id": "ca-7_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Correlation and analysis of security-related information generated by assessments and monitoring;" - }, - { - "id": "ca-7_smt.f", - "name": "item", - "props": [ - { - "name": "label", - "value": "f." - } - ], - "prose": "Response actions to address results of the analysis of security-related information; and" - }, - { - "id": "ca-7_smt.g", - "name": "item", - "props": [ - { - "name": "label", - "value": "g." - } - ], - "prose": "Reporting the security status of organization and the information system to {{ insert: param, ca-7_prm_4 }} {{ insert: param, ca-7_prm_5 }}." - } - ] - }, - { - "id": "ca-7_gdn", - "name": "guidance", - "prose": "Continuous monitoring programs facilitate ongoing awareness of threats, vulnerabilities, and information security to support organizational risk management decisions. The terms continuous and ongoing imply that organizations assess/analyze security controls and information security-related risks at a frequency sufficient to support organizational risk-based decisions. The results of continuous monitoring programs generate appropriate risk response actions by organizations. Continuous monitoring programs also allow organizations to maintain the security authorizations of information systems and common controls over time in highly dynamic environments of operation with changing mission/business needs, threats, vulnerabilities, and technologies. Having access to security-related information on a continuing basis through reports/dashboards gives organizational officials the capability to make more effective and timely risk management decisions, including ongoing security authorization decisions. Automation supports more frequent updates to security authorization packages, hardware/software/firmware inventories, and other system information. Effectiveness is further enhanced when continuous monitoring outputs are formatted to provide information that is specific, measurable, actionable, relevant, and timely. Continuous monitoring activities are scaled in accordance with the security categories of information systems.", - "links": [ - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-5", - "rel": "related" - }, - { - "href": "#ca-6", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#pm-6", - "rel": "related" - }, - { - "href": "#pm-9", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#sa-11", - "rel": "related" - }, - { - "href": "#sa-12", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "ca-7_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ca-7.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(a)" - } - ], - "parts": [ - { - "id": "ca-7.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(a)[1]" - } - ], - "prose": "develops a continuous monitoring strategy that defines metrics to be monitored;" - }, - { - "id": "ca-7.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(a)[2]" - } - ], - "prose": "develops a continuous monitoring strategy that includes monitoring of organization-defined metrics;" - }, - { - "id": "ca-7.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(a)[3]" - } - ], - "prose": "implements a continuous monitoring program that includes monitoring of organization-defined metrics in accordance with the organizational continuous monitoring strategy;" - } - ] - }, - { - "id": "ca-7.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(b)" - } - ], - "parts": [ - { - "id": "ca-7.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(b)[1]" - } - ], - "prose": "develops a continuous monitoring strategy that defines frequencies for monitoring;" - }, - { - "id": "ca-7.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(b)[2]" - } - ], - "prose": "defines frequencies for assessments supporting monitoring;" - }, - { - "id": "ca-7.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(b)[3]" - } - ], - "prose": "develops a continuous monitoring strategy that includes establishment of the organization-defined frequencies for monitoring and for assessments supporting monitoring;" - }, - { - "id": "ca-7.b_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(b)[4]" - } - ], - "prose": "implements a continuous monitoring program that includes establishment of organization-defined frequencies for monitoring and for assessments supporting such monitoring in accordance with the organizational continuous monitoring strategy;" - } - ] - }, - { - "id": "ca-7.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(c)" - } - ], - "parts": [ - { - "id": "ca-7.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(c)[1]" - } - ], - "prose": "develops a continuous monitoring strategy that includes ongoing security control assessments;" - }, - { - "id": "ca-7.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(c)[2]" - } - ], - "prose": "implements a continuous monitoring program that includes ongoing security control assessments in accordance with the organizational continuous monitoring strategy;" - } - ] - }, - { - "id": "ca-7.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(d)" - } - ], - "parts": [ - { - "id": "ca-7.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(d)[1]" - } - ], - "prose": "develops a continuous monitoring strategy that includes ongoing security status monitoring of organization-defined metrics;" - }, - { - "id": "ca-7.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(d)[2]" - } - ], - "prose": "implements a continuous monitoring program that includes ongoing security status monitoring of organization-defined metrics in accordance with the organizational continuous monitoring strategy;" - } - ] - }, - { - "id": "ca-7.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(e)" - } - ], - "parts": [ - { - "id": "ca-7.e_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(e)[1]" - } - ], - "prose": "develops a continuous monitoring strategy that includes correlation and analysis of security-related information generated by assessments and monitoring;" - }, - { - "id": "ca-7.e_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(e)[2]" - } - ], - "prose": "implements a continuous monitoring program that includes correlation and analysis of security-related information generated by assessments and monitoring in accordance with the organizational continuous monitoring strategy;" - } - ] - }, - { - "id": "ca-7.f_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(f)" - } - ], - "parts": [ - { - "id": "ca-7.f_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(f)[1]" - } - ], - "prose": "develops a continuous monitoring strategy that includes response actions to address results of the analysis of security-related information;" - }, - { - "id": "ca-7.f_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(f)[2]" - } - ], - "prose": "implements a continuous monitoring program that includes response actions to address results of the analysis of security-related information in accordance with the organizational continuous monitoring strategy;" - } - ] - }, - { - "id": "ca-7.g_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(g)" - } - ], - "parts": [ - { - "id": "ca-7.g_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(g)[1]" - } - ], - "prose": "develops a continuous monitoring strategy that defines the personnel or roles to whom the security status of the organization and information system are to be reported;" - }, - { - "id": "ca-7.g_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(g)[2]" - } - ], - "prose": "develops a continuous monitoring strategy that defines the frequency to report the security status of the organization and information system to organization-defined personnel or roles;" - }, - { - "id": "ca-7.g_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(g)[3]" - } - ], - "prose": "develops a continuous monitoring strategy that includes reporting the security status of the organization or information system to organizational-defined personnel or roles with the organization-defined frequency; and" - }, - { - "id": "ca-7.g_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(g)[4]" - } - ], - "prose": "implements a continuous monitoring program that includes reporting the security status of the organization and information system to organization-defined personnel or roles with the organization-defined frequency in accordance with the organizational continuous monitoring strategy." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security assessment and authorization policy\n\nprocedures addressing continuous monitoring of information system security controls\n\nprocedures addressing configuration management\n\nsecurity plan\n\nsecurity assessment report\n\nplan of action and milestones\n\ninformation system monitoring records\n\nconfiguration management records, security impact analyses\n\nstatus reports\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with continuous monitoring responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Mechanisms implementing continuous monitoring" - } - ] - } - ], - "controls": [ - { - "id": "ca-7.1", - "class": "SP800-53-enhancement", - "title": "Independent Assessment", - "params": [ - { - "id": "ca-7.1_prm_1", - "label": "organization-defined level of independence" - } - ], - "props": [ - { - "name": "label", - "value": "CA-7(1)" - }, - { - "name": "sort-id", - "value": "ca-07.01" - } - ], - "parts": [ - { - "id": "ca-7.1_smt", - "name": "statement", - "prose": "The organization employs assessors or assessment teams with {{ insert: param, ca-7.1_prm_1 }} to monitor the security controls in the information system on an ongoing basis." - }, - { - "id": "ca-7.1_gdn", - "name": "guidance", - "prose": "Organizations can maximize the value of assessments of security controls during the continuous monitoring process by requiring that such assessments be conducted by assessors or assessment teams with appropriate levels of independence based on continuous monitoring strategies. Assessor independence provides a degree of impartiality to the monitoring process. To achieve such impartiality, assessors should not: (i) create a mutual or conflicting interest with the organizations where the assessments are being conducted; (ii) assess their own work; (iii) act as management or employees of the organizations they are serving; or (iv) place themselves in advocacy positions for the organizations acquiring their services." - }, - { - "id": "ca-7.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ca-7.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(1)[1]" - } - ], - "prose": "defines a level of independence to be employed to monitor the security controls in the information system on an ongoing basis; and" - }, - { - "id": "ca-7.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(1)[2]" - } - ], - "prose": "employs assessors or assessment teams with the organization-defined level of independence to monitor the security controls in the information system on an ongoing basis." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security assessment and authorization policy\n\nprocedures addressing continuous monitoring of information system security controls\n\nsecurity plan\n\nsecurity assessment report\n\nplan of action and milestones\n\ninformation system monitoring records\n\nsecurity impact analyses\n\nstatus reports\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with continuous monitoring responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "ca-7.2", - "class": "SP800-53-enhancement", - "title": "Types of Assessments", - "props": [ - { - "name": "label", - "value": "CA-7(2)" - }, - { - "name": "sort-id", - "value": "ca-07.02" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#ca-2", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ca-7.3", - "class": "SP800-53-enhancement", - "title": "Trend Analyses", - "props": [ - { - "name": "label", - "value": "CA-7(3)" - }, - { - "name": "sort-id", - "value": "ca-07.03" - } - ], - "parts": [ - { - "id": "ca-7.3_smt", - "name": "statement", - "prose": "The organization employs trend analyses to determine if security control implementations, the frequency of continuous monitoring activities, and/or the types of activities used in the continuous monitoring process need to be modified based on empirical data." - }, - { - "id": "ca-7.3_gdn", - "name": "guidance", - "prose": "Trend analyses can include, for example, examining recent threat information regarding the types of threat events that have occurred within the organization or across the federal government, success rates of certain types of cyber attacks, emerging vulnerabilities in information technologies, evolving social engineering techniques, results from multiple security control assessments, the effectiveness of configuration settings, and findings from Inspectors General or auditors." - }, - { - "id": "ca-7.3_obj", - "name": "objective", - "prose": "Determine if the organization employs trend analyses to determine if the following items need to be modified based on empirical data:", - "parts": [ - { - "id": "ca-7.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(3)[1]" - } - ], - "prose": "security control implementations;" - }, - { - "id": "ca-7.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(3)[2]" - } - ], - "prose": "the frequency of continuous monitoring activities; and/or" - }, - { - "id": "ca-7.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-7(3)[3]" - } - ], - "prose": "the types of activities used in the continuous monitoring process." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Continuous monitoring strategy\n\nSecurity assessment and authorization policy\n\nprocedures addressing continuous monitoring of information system security controls\n\nsecurity plan\n\nsecurity assessment report\n\nplan of action and milestones\n\ninformation system monitoring records\n\nsecurity impact analyses\n\nstatus reports\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with continuous monitoring responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "ca-8", - "class": "SP800-53", - "title": "Penetration Testing", - "params": [ - { - "id": "ca-8_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "ca-8_prm_2", - "label": "organization-defined information systems or system components" - } - ], - "props": [ - { - "name": "label", - "value": "CA-8" - }, - { - "name": "sort-id", - "value": "ca-08" - } - ], - "parts": [ - { - "id": "ca-8_smt", - "name": "statement", - "prose": "The organization conducts penetration testing {{ insert: param, ca-8_prm_1 }} on {{ insert: param, ca-8_prm_2 }}." - }, - { - "id": "ca-8_gdn", - "name": "guidance", - "prose": "Penetration testing is a specialized type of assessment conducted on information systems or individual system components to identify vulnerabilities that could be exploited by adversaries. Such testing can be used to either validate vulnerabilities or determine the degree of resistance organizational information systems have to adversaries within a set of specified constraints (e.g., time, resources, and/or skills). Penetration testing attempts to duplicate the actions of adversaries in carrying out hostile cyber attacks against organizations and provides a more in-depth analysis of security-related weaknesses/deficiencies. Organizations can also use the results of vulnerability analyses to support penetration testing activities. Penetration testing can be conducted on the hardware, software, or firmware components of an information system and can exercise both physical and technical security controls. A standard method for penetration testing includes, for example: (i) pretest analysis based on full knowledge of the target system; (ii) pretest identification of potential vulnerabilities based on pretest analysis; and (iii) testing designed to determine exploitability of identified vulnerabilities. All parties agree to the rules of engagement before the commencement of penetration testing scenarios. Organizations correlate the penetration testing rules of engagement with the tools, techniques, and procedures that are anticipated to be employed by adversaries carrying out attacks. Organizational risk assessments guide decisions on the level of independence required for personnel conducting penetration testing.", - "links": [ - { - "href": "#sa-12", - "rel": "related" - } - ] - }, - { - "id": "ca-8_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ca-8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-8[1]" - } - ], - "prose": "defines information systems or system components on which penetration testing is to be conducted;" - }, - { - "id": "ca-8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-8[2]" - } - ], - "prose": "defines the frequency to conduct penetration testing on organization-defined information systems or system components; and" - }, - { - "id": "ca-8_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-8[3]" - } - ], - "prose": "conducts penetration testing on organization-defined information systems or system components with the organization-defined frequency." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security assessment and authorization policy\n\nprocedures addressing penetration testing\n\nsecurity plan\n\nsecurity assessment plan\n\npenetration test report\n\nsecurity assessment report\n\nsecurity assessment evidence\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security assessment responsibilities\n\norganizational personnel with information security responsibilities, system/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting penetration testing" - } - ] - } - ], - "controls": [ - { - "id": "ca-8.1", - "class": "SP800-53-enhancement", - "title": "Independent Penetration Agent or Team", - "props": [ - { - "name": "label", - "value": "CA-8(1)" - }, - { - "name": "sort-id", - "value": "ca-08.01" - } - ], - "parts": [ - { - "id": "ca-8.1_smt", - "name": "statement", - "prose": "The organization employs an independent penetration agent or penetration team to perform penetration testing on the information system or system components." - }, - { - "id": "ca-8.1_gdn", - "name": "guidance", - "prose": "Independent penetration agents or teams are individuals or groups who conduct impartial penetration testing of organizational information systems. Impartiality implies that penetration agents or teams are free from any perceived or actual conflicts of interest with regard to the development, operation, or management of the information systems that are the targets of the penetration testing. Supplemental guidance for CA-2 (1) provides additional information regarding independent assessments that can be applied to penetration testing.", - "links": [ - { - "href": "#ca-2", - "rel": "related" - } - ] - }, - { - "id": "ca-8.1_obj", - "name": "objective", - "prose": "Determine if the organization employs an independent penetration agent or penetration team to perform penetration testing on the information system or system components." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security assessment and authorization policy\n\nprocedures addressing penetration testing\n\nsecurity plan\n\nsecurity assessment plan\n\npenetration test report\n\nsecurity assessment report\n\nsecurity assessment evidence\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security assessment responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "ca-8.2", - "class": "SP800-53-enhancement", - "title": "Red Team Exercises", - "params": [ - { - "id": "ca-8.2_prm_1", - "label": "organization-defined red team exercises" - }, - { - "id": "ca-8.2_prm_2", - "label": "organization-defined rules of engagement" - } - ], - "props": [ - { - "name": "label", - "value": "CA-8(2)" - }, - { - "name": "sort-id", - "value": "ca-08.02" - } - ], - "parts": [ - { - "id": "ca-8.2_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, ca-8.2_prm_1 }} to simulate attempts by adversaries to compromise organizational information systems in accordance with {{ insert: param, ca-8.2_prm_2 }}." - }, - { - "id": "ca-8.2_gdn", - "name": "guidance", - "prose": "Red team exercises extend the objectives of penetration testing by examining the security posture of organizations and their ability to implement effective cyber defenses. As such, red team exercises reflect simulated adversarial attempts to compromise organizational mission/business functions and provide a comprehensive assessment of the security state of information systems and organizations. Simulated adversarial attempts to compromise organizational missions/business functions and the information systems that support those missions/functions may include technology-focused attacks (e.g., interactions with hardware, software, or firmware components and/or mission/business processes) and social engineering-based attacks (e.g., interactions via email, telephone, shoulder surfing, or personal conversations). While penetration testing may be largely laboratory-based testing, organizations use red team exercises to provide more comprehensive assessments that reflect real-world conditions. Red team exercises can be used to improve security awareness and training and to assess levels of security control effectiveness." - }, - { - "id": "ca-8.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ca-8.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-8(2)[1]" - } - ], - "prose": "defines red team exercises to be employed to simulate attempts by adversaries to compromise organizational information systems;" - }, - { - "id": "ca-8.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-8(2)[2]" - } - ], - "prose": "defines rules of engagement for employing organization-defined red team exercises; and" - }, - { - "id": "ca-8.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-8(2)[3]" - } - ], - "prose": "employs organization-defined red team exercises to simulate attempts by adversaries to compromise organizational information systems in accordance with organization-defined rules of engagement." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security assessment and authorization policy\n\nprocedures addressing penetration testing\n\nprocedures addressing red team exercises\n\nsecurity plan\n\nsecurity assessment plan\n\nresults of red team exercise\n\npenetration test report\n\nsecurity assessment report\n\nrules of engagement\n\nsecurity assessment evidence\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security assessment responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting employment of red team exercises" - } - ] - } - ] - } - ] - }, - { - "id": "ca-9", - "class": "SP800-53", - "title": "Internal System Connections", - "params": [ - { - "id": "ca-9_prm_1", - "label": "organization-defined information system components or classes of components" - } - ], - "props": [ - { - "name": "label", - "value": "CA-9" - }, - { - "name": "sort-id", - "value": "ca-09" - } - ], - "parts": [ - { - "id": "ca-9_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ca-9_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Authorizes internal connections of {{ insert: param, ca-9_prm_1 }} to the information system; and" - }, - { - "id": "ca-9_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Documents, for each internal connection, the interface characteristics, security requirements, and the nature of the information communicated." - } - ] - }, - { - "id": "ca-9_gdn", - "name": "guidance", - "prose": "This control applies to connections between organizational information systems and (separate) constituent system components (i.e., intra-system connections) including, for example, system connections with mobile devices, notebook/desktop computers, printers, copiers, facsimile machines, scanners, sensors, and servers. Instead of authorizing each individual internal connection, organizations can authorize internal connections for a class of components with common characteristics and/or configurations, for example, all digital printers, scanners, and copiers with a specified processing, storage, and transmission capability or all smart phones with a specific baseline configuration.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "ca-9_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ca-9.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-9(a)" - } - ], - "parts": [ - { - "id": "ca-9.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-9(a)[1]" - } - ], - "prose": "defines information system components or classes of components to be authorized as internal connections to the information system;" - }, - { - "id": "ca-9.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-9(a)[2]" - } - ], - "prose": "authorizes internal connections of organization-defined information system components or classes of components to the information system;" - } - ] - }, - { - "id": "ca-9.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-9(b)" - } - ], - "prose": "documents, for each internal connection:", - "parts": [ - { - "id": "ca-9.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-9(b)[1]" - } - ], - "prose": "the interface characteristics;" - }, - { - "id": "ca-9.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-9(b)[2]" - } - ], - "prose": "the security requirements; and" - }, - { - "id": "ca-9.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CA-9(b)[3]" - } - ], - "prose": "the nature of the information communicated." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing information system connections\n\nsystem and communications protection policy\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of components or classes of components authorized as internal system connections\n\nsecurity assessment report\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for developing, implementing, or authorizing internal system connections\n\norganizational personnel with information security responsibilities" - } - ] - } - ], - "controls": [ - { - "id": "ca-9.1", - "class": "SP800-53-enhancement", - "title": "Security Compliance Checks", - "props": [ - { - "name": "label", - "value": "CA-9(1)" - }, - { - "name": "sort-id", - "value": "ca-09.01" - } - ], - "parts": [ - { - "id": "ca-9.1_smt", - "name": "statement", - "prose": "The information system performs security compliance checks on constituent system components prior to the establishment of the internal connection." - }, - { - "id": "ca-9.1_gdn", - "name": "guidance", - "prose": "Security compliance checks may include, for example, verification of the relevant baseline configuration.", - "links": [ - { - "href": "#cm-6", - "rel": "related" - } - ] - }, - { - "id": "ca-9.1_obj", - "name": "objective", - "prose": "Determine if the information system performs security compliance checks on constituent system components prior to the establishment of the internal connection." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Access control policy\n\nprocedures addressing information system connections\n\nsystem and communications protection policy\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of components or classes of components authorized as internal system connections\n\nsecurity assessment report\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for developing, implementing, or authorizing internal system connections\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting compliance checks" - } - ] - } - ] - } - ] - } - ] - }, - { - "id": "cm", - "class": "family", - "title": "Configuration Management", - "controls": [ - { - "id": "cm-1", - "class": "SP800-53", - "title": "Configuration Management Policy and Procedures", - "params": [ - { - "id": "cm-1_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "cm-1_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "cm-1_prm_3", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "CM-1" - }, - { - "name": "sort-id", - "value": "cm-01" - } - ], - "links": [ - { - "href": "#5c201b63-0768-417b-ac22-3f014e3941b2", - "rel": "reference" - }, - { - "href": "#9cb3d8fe-2127-48ba-821e-cdd2d7aee921", - "rel": "reference" - } - ], - "parts": [ - { - "id": "cm-1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cm-1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops, documents, and disseminates to {{ insert: param, cm-1_prm_1 }}:", - "parts": [ - { - "id": "cm-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "A configuration management policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "cm-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the configuration management policy and associated configuration management controls; and" - } - ] - }, - { - "id": "cm-1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the current:", - "parts": [ - { - "id": "cm-1_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Configuration management policy {{ insert: param, cm-1_prm_2 }}; and" - }, - { - "id": "cm-1_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Configuration management procedures {{ insert: param, cm-1_prm_3 }}." - } - ] - } - ] - }, - { - "id": "cm-1_gdn", - "name": "guidance", - "prose": "This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the CM family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures.", - "links": [ - { - "href": "#pm-9", - "rel": "related" - } - ] - }, - { - "id": "cm-1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(a)" - } - ], - "parts": [ - { - "id": "cm-1.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(a)(1)" - } - ], - "parts": [ - { - "id": "cm-1.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(a)(1)[1]" - } - ], - "prose": "develops and documents a configuration management policy that addresses:", - "parts": [ - { - "id": "cm-1.a.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(a)(1)[1][a]" - } - ], - "prose": "purpose;" - }, - { - "id": "cm-1.a.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(a)(1)[1][b]" - } - ], - "prose": "scope;" - }, - { - "id": "cm-1.a.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(a)(1)[1][c]" - } - ], - "prose": "roles;" - }, - { - "id": "cm-1.a.1_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(a)(1)[1][d]" - } - ], - "prose": "responsibilities;" - }, - { - "id": "cm-1.a.1_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(a)(1)[1][e]" - } - ], - "prose": "management commitment;" - }, - { - "id": "cm-1.a.1_obj.1.f", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(a)(1)[1][f]" - } - ], - "prose": "coordination among organizational entities;" - }, - { - "id": "cm-1.a.1_obj.1.g", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(a)(1)[1][g]" - } - ], - "prose": "compliance;" - } - ] - }, - { - "id": "cm-1.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(a)(1)[2]" - } - ], - "prose": "defines personnel or roles to whom the configuration management policy is to be disseminated;" - }, - { - "id": "cm-1.a.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(a)(1)[3]" - } - ], - "prose": "disseminates the configuration management policy to organization-defined personnel or roles;" - } - ] - }, - { - "id": "cm-1.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(a)(2)" - } - ], - "parts": [ - { - "id": "cm-1.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(a)(2)[1]" - } - ], - "prose": "develops and documents procedures to facilitate the implementation of the configuration management policy and associated configuration management controls;" - }, - { - "id": "cm-1.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(a)(2)[2]" - } - ], - "prose": "defines personnel or roles to whom the procedures are to be disseminated;" - }, - { - "id": "cm-1.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(a)(2)[3]" - } - ], - "prose": "disseminates the procedures to organization-defined personnel or roles;" - } - ] - } - ] - }, - { - "id": "cm-1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(b)" - } - ], - "parts": [ - { - "id": "cm-1.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(b)(1)" - } - ], - "parts": [ - { - "id": "cm-1.b.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(b)(1)[1]" - } - ], - "prose": "defines the frequency to review and update the current configuration management policy;" - }, - { - "id": "cm-1.b.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(b)(1)[2]" - } - ], - "prose": "reviews and updates the current configuration management policy with the organization-defined frequency;" - } - ] - }, - { - "id": "cm-1.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(b)(2)" - } - ], - "parts": [ - { - "id": "cm-1.b.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(b)(2)[1]" - } - ], - "prose": "defines the frequency to review and update the current configuration management procedures; and" - }, - { - "id": "cm-1.b.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-1(b)(2)[2]" - } - ], - "prose": "reviews and updates the current configuration management procedures with the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy and procedures\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with configuration management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - } - ] - }, - { - "id": "cm-2", - "class": "SP800-53", - "title": "Baseline Configuration", - "props": [ - { - "name": "label", - "value": "CM-2" - }, - { - "name": "sort-id", - "value": "cm-02" - } - ], - "links": [ - { - "href": "#080f8068-5e3e-435e-9790-d22ba4722693", - "rel": "reference" - } - ], - "parts": [ - { - "id": "cm-2_smt", - "name": "statement", - "prose": "The organization develops, documents, and maintains under configuration control, a current baseline configuration of the information system." - }, - { - "id": "cm-2_gdn", - "name": "guidance", - "prose": "This control establishes baseline configurations for information systems and system components including communications and connectivity-related aspects of systems. Baseline configurations are documented, formally reviewed and agreed-upon sets of specifications for information systems or configuration items within those systems. Baseline configurations serve as a basis for future builds, releases, and/or changes to information systems. Baseline configurations include information about information system components (e.g., standard software packages installed on workstations, notebook computers, servers, network components, or mobile devices; current version numbers and patch information on operating systems and applications; and configuration settings/parameters), network topology, and the logical placement of those components within the system architecture. Maintaining baseline configurations requires creating new baselines as organizational information systems change over time. Baseline configurations of information systems reflect the current enterprise architecture.", - "links": [ - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#cm-9", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - }, - { - "href": "#pm-5", - "rel": "related" - }, - { - "href": "#pm-7", - "rel": "related" - } - ] - }, - { - "id": "cm-2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2[1]" - } - ], - "prose": "develops and documents a current baseline configuration of the information system; and" - }, - { - "id": "cm-2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2[2]" - } - ], - "prose": "maintains, under configuration control, a current baseline configuration of the information system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing the baseline configuration of the information system\n\nconfiguration management plan\n\nenterprise architecture documentation\n\ninformation system design documentation\n\ninformation system architecture and configuration documentation\n\ninformation system configuration settings and associated documentation\n\nchange control records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with configuration management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing baseline configurations\n\nautomated mechanisms supporting configuration control of the baseline configuration" - } - ] - } - ], - "controls": [ - { - "id": "cm-2.1", - "class": "SP800-53-enhancement", - "title": "Reviews and Updates", - "params": [ - { - "id": "cm-2.1_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "cm-2.1_prm_2", - "label": "Assignment organization-defined circumstances" - } - ], - "props": [ - { - "name": "label", - "value": "CM-2(1)" - }, - { - "name": "sort-id", - "value": "cm-02.01" - } - ], - "parts": [ - { - "id": "cm-2.1_smt", - "name": "statement", - "prose": "The organization reviews and updates the baseline configuration of the information system:", - "parts": [ - { - "id": "cm-2.1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": " {{ insert: param, cm-2.1_prm_1 }};" - }, - { - "id": "cm-2.1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "When required due to {{ insert: param, cm-2.1_prm_2 }}; and" - }, - { - "id": "cm-2.1_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "As an integral part of information system component installations and upgrades." - } - ] - }, - { - "id": "cm-2.1_gdn", - "name": "guidance", - "links": [ - { - "href": "#cm-5", - "rel": "related" - } - ] - }, - { - "id": "cm-2.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-2.1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(1)(a)" - } - ], - "parts": [ - { - "id": "cm-2.1.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(1)(a)[1]" - } - ], - "prose": "defines the frequency to review and update the baseline configuration of the information system;" - }, - { - "id": "cm-2.1.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(1)(a)[2]" - } - ], - "prose": "reviews and updates the baseline configuration of the information system with the organization-defined frequency;" - } - ], - "links": [ - { - "href": "#cm-2.1_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "cm-2.1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(1)(b)" - } - ], - "parts": [ - { - "id": "cm-2.1.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(1)(b)[1]" - } - ], - "prose": "defines circumstances that require the baseline configuration of the information system to be reviewed and updated;" - }, - { - "id": "cm-2.1.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(1)(b)[2]" - } - ], - "prose": "reviews and updates the baseline configuration of the information system when required due to organization-defined circumstances; and" - } - ], - "links": [ - { - "href": "#cm-2.1_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "cm-2.1.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(1)(c)" - } - ], - "prose": "reviews and updates the baseline configuration of the information system as an integral part of information system component installations and upgrades.", - "links": [ - { - "href": "#cm-2.1_smt.c", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nconfiguration management plan\n\nprocedures addressing the baseline configuration of the information system\n\nprocedures addressing information system component installations and upgrades\n\ninformation system architecture and configuration documentation\n\ninformation system configuration settings and associated documentation\n\nrecords of information system baseline configuration reviews and updates\n\ninformation system component installations/upgrades and associated records\n\nchange control records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with configuration management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing baseline configurations\n\nautomated mechanisms supporting review and update of the baseline configuration" - } - ] - } - ] - }, - { - "id": "cm-2.2", - "class": "SP800-53-enhancement", - "title": "Automation Support for Accuracy / Currency", - "props": [ - { - "name": "label", - "value": "CM-2(2)" - }, - { - "name": "sort-id", - "value": "cm-02.02" - } - ], - "parts": [ - { - "id": "cm-2.2_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to maintain an up-to-date, complete, accurate, and readily available baseline configuration of the information system." - }, - { - "id": "cm-2.2_gdn", - "name": "guidance", - "prose": "Automated mechanisms that help organizations maintain consistent baseline configurations for information systems include, for example, hardware and software inventory tools, configuration management tools, and network management tools. Such tools can be deployed and/or allocated as common controls, at the information system level, or at the operating system or component level (e.g., on workstations, servers, notebook computers, network components, or mobile devices). Tools can be used, for example, to track version numbers on operating system applications, types of software installed, and current patch levels. This control enhancement can be satisfied by the implementation of CM-8 (2) for organizations that choose to combine information system component inventory and baseline configuration activities.", - "links": [ - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - } - ] - }, - { - "id": "cm-2.2_obj", - "name": "objective", - "prose": "Determine if the organization employs automated mechanisms to maintain:", - "parts": [ - { - "id": "cm-2.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(2)[1]" - } - ], - "prose": "an up-to-date baseline configuration of the information system;" - }, - { - "id": "cm-2.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(2)[2]" - } - ], - "prose": "a complete baseline configuration of the information system;" - }, - { - "id": "cm-2.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(2)[3]" - } - ], - "prose": "an accurate baseline configuration of the information system; and" - }, - { - "id": "cm-2.2_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(2)[4]" - } - ], - "prose": "a readily available baseline configuration of the information system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing the baseline configuration of the information system\n\nconfiguration management plan\n\ninformation system design documentation\n\ninformation system architecture and configuration documentation\n\ninformation system configuration settings and associated documentation\n\nconfiguration change control records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with configuration management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing baseline configurations\n\nautomated mechanisms implementing baseline configuration maintenance" - } - ] - } - ] - }, - { - "id": "cm-2.3", - "class": "SP800-53-enhancement", - "title": "Retention of Previous Configurations", - "params": [ - { - "id": "cm-2.3_prm_1", - "label": "organization-defined previous versions of baseline configurations of the information system" - } - ], - "props": [ - { - "name": "label", - "value": "CM-2(3)" - }, - { - "name": "sort-id", - "value": "cm-02.03" - } - ], - "parts": [ - { - "id": "cm-2.3_smt", - "name": "statement", - "prose": "The organization retains {{ insert: param, cm-2.3_prm_1 }} to support rollback." - }, - { - "id": "cm-2.3_gdn", - "name": "guidance", - "prose": "Retaining previous versions of baseline configurations to support rollback may include, for example, hardware, software, firmware, configuration files, and configuration records." - }, - { - "id": "cm-2.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-2.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(3)[1]" - } - ], - "prose": "defines previous versions of baseline configurations of the information system to be retained to support rollback; and" - }, - { - "id": "cm-2.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(3)[2]" - } - ], - "prose": "retains organization-defined previous versions of baseline configurations of the information system to support rollback." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing the baseline configuration of the information system\n\nconfiguration management plan\n\ninformation system architecture and configuration documentation\n\ninformation system configuration settings and associated documentation\n\ncopies of previous baseline configuration versions\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with configuration management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing baseline configurations" - } - ] - } - ] - }, - { - "id": "cm-2.4", - "class": "SP800-53-enhancement", - "title": "Unauthorized Software", - "props": [ - { - "name": "label", - "value": "CM-2(4)" - }, - { - "name": "sort-id", - "value": "cm-02.04" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#cm-7", - "rel": "incorporated-into" - } - ] - }, - { - "id": "cm-2.5", - "class": "SP800-53-enhancement", - "title": "Authorized Software", - "props": [ - { - "name": "label", - "value": "CM-2(5)" - }, - { - "name": "sort-id", - "value": "cm-02.05" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#cm-7", - "rel": "incorporated-into" - } - ] - }, - { - "id": "cm-2.6", - "class": "SP800-53-enhancement", - "title": "Development and Test Environments", - "props": [ - { - "name": "label", - "value": "CM-2(6)" - }, - { - "name": "sort-id", - "value": "cm-02.06" - } - ], - "parts": [ - { - "id": "cm-2.6_smt", - "name": "statement", - "prose": "The organization maintains a baseline configuration for information system development and test environments that is managed separately from the operational baseline configuration." - }, - { - "id": "cm-2.6_gdn", - "name": "guidance", - "prose": "Establishing separate baseline configurations for development, testing, and operational environments helps protect information systems from unplanned/unexpected events related to development and testing activities. Separate baseline configurations allow organizations to apply the configuration management that is most appropriate for each type of configuration. For example, management of operational configurations typically emphasizes the need for stability, while management of development/test configurations requires greater flexibility. Configurations in the test environment mirror the configurations in the operational environment to the extent practicable so that the results of the testing are representative of the proposed changes to the operational systems. This control enhancement requires separate configurations but not necessarily separate physical environments.", - "links": [ - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - } - ] - }, - { - "id": "cm-2.6_obj", - "name": "objective", - "prose": "Determine if the organization maintains a baseline configuration for information system development and test environments that is managed separately from the operational baseline configuration." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing the baseline configuration of the information system\n\nconfiguration management plan\n\ninformation system design documentation\n\ninformation system architecture and configuration documentation\n\ninformation system configuration settings and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with configuration management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing baseline configurations\n\nautomated mechanisms implementing separate baseline configurations for development, test, and operational environments" - } - ] - } - ] - }, - { - "id": "cm-2.7", - "class": "SP800-53-enhancement", - "title": "Configure Systems, Components, or Devices for High-risk Areas", - "params": [ - { - "id": "cm-2.7_prm_1", - "label": "organization-defined information systems, system components, or devices" - }, - { - "id": "cm-2.7_prm_2", - "label": "organization-defined configurations" - }, - { - "id": "cm-2.7_prm_3", - "label": "organization-defined security safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "CM-2(7)" - }, - { - "name": "sort-id", - "value": "cm-02.07" - } - ], - "parts": [ - { - "id": "cm-2.7_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cm-2.7_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Issues {{ insert: param, cm-2.7_prm_1 }} with {{ insert: param, cm-2.7_prm_2 }} to individuals traveling to locations that the organization deems to be of significant risk; and" - }, - { - "id": "cm-2.7_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Applies {{ insert: param, cm-2.7_prm_3 }} to the devices when the individuals return." - } - ] - }, - { - "id": "cm-2.7_gdn", - "name": "guidance", - "prose": "When it is known that information systems, system components, or devices (e.g., notebook computers, mobile devices) will be located in high-risk areas, additional security controls may be implemented to counter the greater threat in such areas coupled with the lack of physical security relative to organizational-controlled areas. For example, organizational policies and procedures for notebook computers used by individuals departing on and returning from travel include, for example, determining which locations are of concern, defining required configurations for the devices, ensuring that the devices are configured as intended before travel is initiated, and applying specific safeguards to the device after travel is completed. Specially configured notebook computers include, for example, computers with sanitized hard drives, limited applications, and additional hardening (e.g., more stringent configuration settings). Specified safeguards applied to mobile devices upon return from travel include, for example, examining the device for signs of physical tampering and purging/reimaging the hard disk drive. Protecting information residing on mobile devices is covered in the media protection family." - }, - { - "id": "cm-2.7_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-2.7.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(7)(a)" - } - ], - "parts": [ - { - "id": "cm-2.7.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(7)(a)[1]" - } - ], - "prose": "defines information systems, system components, or devices to be issued to individuals traveling to locations that the organization deems to be of significant risk;" - }, - { - "id": "cm-2.7.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(7)(a)[2]" - } - ], - "prose": "defines configurations to be employed on organization-defined information systems, system components, or devices issued to individuals traveling to such locations;" - }, - { - "id": "cm-2.7.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(7)(a)[3]" - } - ], - "prose": "issues organization-defined information systems, system components, or devices with organization-defined configurations to individuals traveling to locations that the organization deems to be of significant risk;" - } - ], - "links": [ - { - "href": "#cm-2.7_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "cm-2.7.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(7)(b)" - } - ], - "parts": [ - { - "id": "cm-2.7.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(7)(b)[1]" - } - ], - "prose": "defines security safeguards to be applied to the devices when the individuals return; and" - }, - { - "id": "cm-2.7.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-2(7)(b)[2]" - } - ], - "prose": "applies organization-defined safeguards to the devices when the individuals return." - } - ], - "links": [ - { - "href": "#cm-2.7_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nconfiguration management plan\n\nprocedures addressing the baseline configuration of the information system\n\nprocedures addressing information system component installations and upgrades\n\ninformation system architecture and configuration documentation\n\ninformation system configuration settings and associated documentation\n\nrecords of information system baseline configuration reviews and updates\n\ninformation system component installations/upgrades and associated records\n\nchange control records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with configuration management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing baseline configurations" - } - ] - } - ] - } - ] - }, - { - "id": "cm-3", - "class": "SP800-53", - "title": "Configuration Change Control", - "params": [ - { - "id": "cm-3_prm_1", - "label": "organization-defined time period" - }, - { - "id": "cm-3_prm_2", - "label": "organization-defined configuration change control element (e.g., committee, board)" - }, - { - "id": "cm-3_prm_3", - "select": { - "how-many": "one-or-more", - "choice": [ - " {{ insert: param, cm-3_prm_4 }} ", - " {{ insert: param, cm-3_prm_5 }} " - ] - } - }, - { - "id": "cm-3_prm_4", - "depends-on": "cm-3_prm_3", - "label": "organization-defined frequency" - }, - { - "id": "cm-3_prm_5", - "depends-on": "cm-3_prm_3", - "label": "organization-defined configuration change conditions" - } - ], - "props": [ - { - "name": "label", - "value": "CM-3" - }, - { - "name": "sort-id", - "value": "cm-03" - } - ], - "links": [ - { - "href": "#080f8068-5e3e-435e-9790-d22ba4722693", - "rel": "reference" - } - ], - "parts": [ - { - "id": "cm-3_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cm-3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Determines the types of changes to the information system that are configuration-controlled;" - }, - { - "id": "cm-3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews proposed configuration-controlled changes to the information system and approves or disapproves such changes with explicit consideration for security impact analyses;" - }, - { - "id": "cm-3_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Documents configuration change decisions associated with the information system;" - }, - { - "id": "cm-3_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Implements approved configuration-controlled changes to the information system;" - }, - { - "id": "cm-3_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Retains records of configuration-controlled changes to the information system for {{ insert: param, cm-3_prm_1 }};" - }, - { - "id": "cm-3_smt.f", - "name": "item", - "props": [ - { - "name": "label", - "value": "f." - } - ], - "prose": "Audits and reviews activities associated with configuration-controlled changes to the information system; and" - }, - { - "id": "cm-3_smt.g", - "name": "item", - "props": [ - { - "name": "label", - "value": "g." - } - ], - "prose": "Coordinates and provides oversight for configuration change control activities through {{ insert: param, cm-3_prm_2 }} that convenes {{ insert: param, cm-3_prm_3 }}." - } - ] - }, - { - "id": "cm-3_gdn", - "name": "guidance", - "prose": "Configuration change controls for organizational information systems involve the systematic proposal, justification, implementation, testing, review, and disposition of changes to the systems, including system upgrades and modifications. Configuration change control includes changes to baseline configurations for components and configuration items of information systems, changes to configuration settings for information technology products (e.g., operating systems, applications, firewalls, routers, and mobile devices), unscheduled/unauthorized changes, and changes to remediate vulnerabilities. Typical processes for managing configuration changes to information systems include, for example, Configuration Control Boards that approve proposed changes to systems. For new development information systems or systems undergoing major upgrades, organizations consider including representatives from development organizations on the Configuration Control Boards. Auditing of changes includes activities before and after changes are made to organizational information systems and the auditing activities required to implement such changes.", - "links": [ - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-9", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ] - }, - { - "id": "cm-3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(a)" - } - ], - "prose": "determines the type of changes to the information system that must be configuration-controlled;" - }, - { - "id": "cm-3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(b)" - } - ], - "prose": "reviews proposed configuration-controlled changes to the information system and approves or disapproves such changes with explicit consideration for security impact analyses;" - }, - { - "id": "cm-3.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(c)" - } - ], - "prose": "documents configuration change decisions associated with the information system;" - }, - { - "id": "cm-3.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(d)" - } - ], - "prose": "implements approved configuration-controlled changes to the information system;" - }, - { - "id": "cm-3.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(e)" - } - ], - "parts": [ - { - "id": "cm-3.e_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(e)[1]" - } - ], - "prose": "defines a time period to retain records of configuration-controlled changes to the information system;" - }, - { - "id": "cm-3.e_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(e)[2]" - } - ], - "prose": "retains records of configuration-controlled changes to the information system for the organization-defined time period;" - } - ] - }, - { - "id": "cm-3.f_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(f)" - } - ], - "prose": "audits and reviews activities associated with configuration-controlled changes to the information system;" - }, - { - "id": "cm-3.g_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(g)" - } - ], - "parts": [ - { - "id": "cm-3.g_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(g)[1]" - } - ], - "prose": "defines a configuration change control element (e.g., committee, board) responsible for coordinating and providing oversight for configuration change control activities;" - }, - { - "id": "cm-3.g_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(g)[2]" - } - ], - "prose": "defines the frequency with which the configuration change control element must convene; and/or" - }, - { - "id": "cm-3.g_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(g)[3]" - } - ], - "prose": "defines configuration change conditions that prompt the configuration change control element to convene; and" - }, - { - "id": "cm-3.g_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(g)[4]" - } - ], - "prose": "coordinates and provides oversight for configuration change control activities through organization-defined configuration change control element that convenes at organization-defined frequency and/or for any organization-defined configuration change conditions." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing information system configuration change control\n\nconfiguration management plan\n\ninformation system architecture and configuration documentation\n\nsecurity plan\n\nchange control records\n\ninformation system audit records\n\nchange control audit and review reports\n\nagenda /minutes from configuration change control oversight meetings\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with configuration change control responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nmembers of change control board or similar" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for configuration change control\n\nautomated mechanisms that implement configuration change control" - } - ] - } - ], - "controls": [ - { - "id": "cm-3.1", - "class": "SP800-53-enhancement", - "title": "Automated Document / Notification / Prohibition of Changes", - "params": [ - { - "id": "cm-3.1_prm_1", - "label": "organized-defined approval authorities" - }, - { - "id": "cm-3.1_prm_2", - "label": "organization-defined time period" - }, - { - "id": "cm-3.1_prm_3", - "label": "organization-defined personnel" - } - ], - "props": [ - { - "name": "label", - "value": "CM-3(1)" - }, - { - "name": "sort-id", - "value": "cm-03.01" - } - ], - "parts": [ - { - "id": "cm-3.1_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to:", - "parts": [ - { - "id": "cm-3.1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Document proposed changes to the information system;" - }, - { - "id": "cm-3.1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Notify {{ insert: param, cm-3.1_prm_1 }} of proposed changes to the information system and request change approval;" - }, - { - "id": "cm-3.1_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Highlight proposed changes to the information system that have not been approved or disapproved by {{ insert: param, cm-3.1_prm_2 }};" - }, - { - "id": "cm-3.1_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "(d)" - } - ], - "prose": "Prohibit changes to the information system until designated approvals are received;" - }, - { - "id": "cm-3.1_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "(e)" - } - ], - "prose": "Document all changes to the information system; and" - }, - { - "id": "cm-3.1_smt.f", - "name": "item", - "props": [ - { - "name": "label", - "value": "(f)" - } - ], - "prose": "Notify {{ insert: param, cm-3.1_prm_3 }} when approved changes to the information system are completed." - } - ] - }, - { - "id": "cm-3.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-3.1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(1)(a)" - } - ], - "prose": "employs automated mechanisms to document proposed changes to the information system;", - "links": [ - { - "href": "#cm-3.1_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "cm-3.1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(1)(b)" - } - ], - "parts": [ - { - "id": "cm-3.1.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(1)(b)[1]" - } - ], - "prose": "defines approval authorities to be notified of proposed changes to the information system and request change approval;" - }, - { - "id": "cm-3.1.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(1)(b)[2]" - } - ], - "prose": "employs automated mechanisms to notify organization-defined approval authorities of proposed changes to the information system and request change approval;" - } - ], - "links": [ - { - "href": "#cm-3.1_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "cm-3.1.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(1)(c)" - } - ], - "parts": [ - { - "id": "cm-3.1.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(1)(c)[1]" - } - ], - "prose": "defines the time period within which proposed changes to the information system that have not been approved or disapproved must be highlighted;" - }, - { - "id": "cm-3.1.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(1)(c)[2]" - } - ], - "prose": "employs automated mechanisms to highlight proposed changes to the information system that have not been approved or disapproved by organization-defined time period;" - } - ], - "links": [ - { - "href": "#cm-3.1_smt.c", - "rel": "corresp" - } - ] - }, - { - "id": "cm-3.1.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(1)(d)" - } - ], - "prose": "employs automated mechanisms to prohibit changes to the information system until designated approvals are received;", - "links": [ - { - "href": "#cm-3.1_smt.d", - "rel": "corresp" - } - ] - }, - { - "id": "cm-3.1.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(1)(e)" - } - ], - "prose": "employs automated mechanisms to document all changes to the information system;", - "links": [ - { - "href": "#cm-3.1_smt.e", - "rel": "corresp" - } - ] - }, - { - "id": "cm-3.1.f_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(1)(f)" - } - ], - "parts": [ - { - "id": "cm-3.1.f_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(1)(f)[1]" - } - ], - "prose": "defines personnel to be notified when approved changes to the information system are completed; and" - }, - { - "id": "cm-3.1.f_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(1)(f)[2]" - } - ], - "prose": "employs automated mechanisms to notify organization-defined personnel when approved changes to the information system are completed." - } - ], - "links": [ - { - "href": "#cm-3.1_smt.f", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing information system configuration change control\n\nconfiguration management plan\n\ninformation system design documentation\n\ninformation system architecture and configuration documentation\n\nautomated configuration control mechanisms\n\ninformation system configuration settings and associated documentation\n\nchange control records\n\ninformation system audit records\n\nchange approval requests\n\nchange approvals\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with configuration change control responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for configuration change control\n\nautomated mechanisms implementing configuration change control activities" - } - ] - } - ] - }, - { - "id": "cm-3.2", - "class": "SP800-53-enhancement", - "title": "Test / Validate / Document Changes", - "props": [ - { - "name": "label", - "value": "CM-3(2)" - }, - { - "name": "sort-id", - "value": "cm-03.02" - } - ], - "parts": [ - { - "id": "cm-3.2_smt", - "name": "statement", - "prose": "The organization tests, validates, and documents changes to the information system before implementing the changes on the operational system." - }, - { - "id": "cm-3.2_gdn", - "name": "guidance", - "prose": "Changes to information systems include modifications to hardware, software, or firmware components and configuration settings defined in CM-6. Organizations ensure that testing does not interfere with information system operations. Individuals/groups conducting tests understand organizational security policies and procedures, information system security policies and procedures, and the specific health, safety, and environmental risks associated with particular facilities/processes. Operational systems may need to be taken off-line, or replicated to the extent feasible, before testing can be conducted. If information systems must be taken off-line for testing, the tests are scheduled to occur during planned system outages whenever possible. If testing cannot be conducted on operational systems, organizations employ compensating controls (e.g., testing on replicated systems)." - }, - { - "id": "cm-3.2_obj", - "name": "objective", - "prose": "Determine if the organization, before implementing changes on the operational system:", - "parts": [ - { - "id": "cm-3.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(2)[1]" - } - ], - "prose": "tests changes to the information system;" - }, - { - "id": "cm-3.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(2)[2]" - } - ], - "prose": "validates changes to the information system; and" - }, - { - "id": "cm-3.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(2)[3]" - } - ], - "prose": "documents changes to the information system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nconfiguration management plan\n\nprocedures addressing information system configuration change control\n\ninformation system design documentation\n\ninformation system architecture and configuration documentation\n\ninformation system configuration settings and associated documentation\n\ntest records\n\nvalidation records\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with configuration change control responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for configuration change control\n\nautomated mechanisms supporting and/or implementing testing, validating, and documenting information system changes" - } - ] - } - ] - }, - { - "id": "cm-3.3", - "class": "SP800-53-enhancement", - "title": "Automated Change Implementation", - "props": [ - { - "name": "label", - "value": "CM-3(3)" - }, - { - "name": "sort-id", - "value": "cm-03.03" - } - ], - "parts": [ - { - "id": "cm-3.3_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to implement changes to the current information system baseline and deploys the updated baseline across the installed base." - }, - { - "id": "cm-3.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-3.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(3)[1]" - } - ], - "prose": "employs automated mechanisms to implement changes to the current information system baseline; and" - }, - { - "id": "cm-3.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(3)[2]" - } - ], - "prose": "deploys the updated baseline across the installed base." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nconfiguration management plan\n\nprocedures addressing information system configuration change control\n\ninformation system design documentation\n\ninformation system architecture and configuration documentation\n\nautomated configuration control mechanisms\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with configuration change control responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for configuration change control\n\nautomated mechanisms implementing changes to current information system baseline" - } - ] - } - ] - }, - { - "id": "cm-3.4", - "class": "SP800-53-enhancement", - "title": "Security Representative", - "params": [ - { - "id": "cm-3.4_prm_1", - "label": "organization-defined configuration change control element" - } - ], - "props": [ - { - "name": "label", - "value": "CM-3(4)" - }, - { - "name": "sort-id", - "value": "cm-03.04" - } - ], - "parts": [ - { - "id": "cm-3.4_smt", - "name": "statement", - "prose": "The organization requires an information security representative to be a member of the {{ insert: param, cm-3.4_prm_1 }}." - }, - { - "id": "cm-3.4_gdn", - "name": "guidance", - "prose": "Information security representatives can include, for example, senior agency information security officers, information system security officers, or information system security managers. Representation by personnel with information security expertise is important because changes to information system configurations can have unintended side effects, some of which may be security-relevant. Detecting such changes early in the process can help avoid unintended, negative consequences that could ultimately affect the security state of organizational information systems. The configuration change control element in this control enhancement reflects the change control elements defined by organizations in CM-3." - }, - { - "id": "cm-3.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-3.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(4)[1]" - } - ], - "prose": "specifies the configuration change control elements (as defined in CM-3g) of which an information security representative is to be a member; and" - }, - { - "id": "cm-3.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(4)[2]" - } - ], - "prose": "requires an information security representative to be a member of the specified configuration control element." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing information system configuration change control\n\nconfiguration management plan\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with configuration change control responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for configuration change control" - } - ] - } - ] - }, - { - "id": "cm-3.5", - "class": "SP800-53-enhancement", - "title": "Automated Security Response", - "params": [ - { - "id": "cm-3.5_prm_1", - "label": "organization-defined security responses" - } - ], - "props": [ - { - "name": "label", - "value": "CM-3(5)" - }, - { - "name": "sort-id", - "value": "cm-03.05" - } - ], - "parts": [ - { - "id": "cm-3.5_smt", - "name": "statement", - "prose": "The information system implements {{ insert: param, cm-3.5_prm_1 }} automatically if baseline configurations are changed in an unauthorized manner." - }, - { - "id": "cm-3.5_gdn", - "name": "guidance", - "prose": "Security responses include, for example, halting information system processing, halting selected system functions, or issuing alerts/notifications to organizational personnel when there is an unauthorized modification of a configuration item." - }, - { - "id": "cm-3.5_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "cm-3.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(5)[1]" - } - ], - "prose": "the organization defines security responses to be implemented automatically if baseline configurations are changed in an unauthorized manner; and" - }, - { - "id": "cm-3.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(5)[2]" - } - ], - "prose": "the information system implements organization-defined security responses automatically if baseline configurations are changed in an unauthorized manner." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing information system configuration change control\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system architecture and configuration documentation\n\ninformation system configuration settings and associated documentation\n\nalerts/notifications of unauthorized baseline configuration changes\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with configuration change control responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for configuration change control\n\nautomated mechanisms implementing security responses to changes to the baseline configurations" - } - ] - } - ] - }, - { - "id": "cm-3.6", - "class": "SP800-53-enhancement", - "title": "Cryptography Management", - "params": [ - { - "id": "cm-3.6_prm_1", - "label": "organization-defined security safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "CM-3(6)" - }, - { - "name": "sort-id", - "value": "cm-03.06" - } - ], - "parts": [ - { - "id": "cm-3.6_smt", - "name": "statement", - "prose": "The organization ensures that cryptographic mechanisms used to provide {{ insert: param, cm-3.6_prm_1 }} are under configuration management." - }, - { - "id": "cm-3.6_gdn", - "name": "guidance", - "prose": "Regardless of the cryptographic means employed (e.g., public key, private key, shared secrets), organizations ensure that there are processes and procedures in place to effectively manage those means. For example, if devices use certificates as a basis for identification and authentication, there needs to be a process in place to address the expiration of those certificates.", - "links": [ - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "cm-3.6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-3.6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(6)[1]" - } - ], - "prose": "defines security safeguards provided by cryptographic mechanisms that are to be under configuration management; and" - }, - { - "id": "cm-3.6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-3(6)[2]" - } - ], - "prose": "ensures that cryptographic mechanisms used to provide organization-defined security safeguards are under configuration management." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing information system configuration change control\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system architecture and configuration documentation\n\ninformation system configuration settings and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with configuration change control responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for configuration change control\n\ncryptographic mechanisms implementing organizational security safeguards" - } - ] - } - ] - } - ] - }, - { - "id": "cm-4", - "class": "SP800-53", - "title": "Security Impact Analysis", - "props": [ - { - "name": "label", - "value": "CM-4" - }, - { - "name": "sort-id", - "value": "cm-04" - } - ], - "links": [ - { - "href": "#080f8068-5e3e-435e-9790-d22ba4722693", - "rel": "reference" - } - ], - "parts": [ - { - "id": "cm-4_smt", - "name": "statement", - "prose": "The organization analyzes changes to the information system to determine potential security impacts prior to change implementation." - }, - { - "id": "cm-4_gdn", - "name": "guidance", - "prose": "Organizational personnel with information security responsibilities (e.g., Information System Administrators, Information System Security Officers, Information System Security Managers, and Information System Security Engineers) conduct security impact analyses. Individuals conducting security impact analyses possess the necessary skills/technical expertise to analyze the changes to information systems and the associated security ramifications. Security impact analysis may include, for example, reviewing security plans to understand security control requirements and reviewing system design documentation to understand control implementation and how specific changes might affect the controls. Security impact analyses may also include assessments of risk to better understand the impact of the changes and to determine if additional security controls are required. Security impact analyses are scaled in accordance with the security categories of the information systems.", - "links": [ - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-9", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - } - ] - }, - { - "id": "cm-4_obj", - "name": "objective", - "prose": "Determine if the organization analyzes changes to the information system to determine potential security impacts prior to change implementation." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing security impact analysis for changes to the information system\n\nconfiguration management plan\n\nsecurity impact analysis documentation\n\nanalysis tools and associated outputs\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for conducting security impact analysis\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for security impact analysis" - } - ] - } - ], - "controls": [ - { - "id": "cm-4.1", - "class": "SP800-53-enhancement", - "title": "Separate Test Environments", - "props": [ - { - "name": "label", - "value": "CM-4(1)" - }, - { - "name": "sort-id", - "value": "cm-04.01" - } - ], - "parts": [ - { - "id": "cm-4.1_smt", - "name": "statement", - "prose": "The organization analyzes changes to the information system in a separate test environment before implementation in an operational environment, looking for security impacts due to flaws, weaknesses, incompatibility, or intentional malice." - }, - { - "id": "cm-4.1_gdn", - "name": "guidance", - "prose": "Separate test environment in this context means an environment that is physically or logically isolated and distinct from the operational environment. The separation is sufficient to ensure that activities in the test environment do not impact activities in the operational environment, and information in the operational environment is not inadvertently transmitted to the test environment. Separate environments can be achieved by physical or logical means. If physically separate test environments are not used, organizations determine the strength of mechanism required when implementing logical separation (e.g., separation achieved through virtual machines).", - "links": [ - { - "href": "#sa-11", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - } - ] - }, - { - "id": "cm-4.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-4.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-4(1)[1]" - } - ], - "prose": "analyzes changes to the information system in a separate test environment before implementation in an operational environment;" - }, - { - "id": "cm-4.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-4(1)[2]" - } - ], - "prose": "when analyzing changes to the information system in a separate test environment, looks for security impacts due to:", - "parts": [ - { - "id": "cm-4.1_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-4(1)[2][a]" - } - ], - "prose": "flaws;" - }, - { - "id": "cm-4.1_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-4(1)[2][b]" - } - ], - "prose": "weaknesses;" - }, - { - "id": "cm-4.1_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-4(1)[2][c]" - } - ], - "prose": "incompatibility; and" - }, - { - "id": "cm-4.1_obj.2.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-4(1)[2][d]" - } - ], - "prose": "intentional malice." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing security impact analysis for changes to the information system\n\nconfiguration management plan\n\nsecurity impact analysis documentation\n\nanalysis tools and associated outputs information system design documentation\n\ninformation system architecture and configuration documentation\n\nchange control records\n\ninformation system audit records\n\ndocumentation evidence of separate test and operational environments\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for conducting security impact analysis\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for security impact analysis\n\nautomated mechanisms supporting and/or implementing security impact analysis of changes" - } - ] - } - ] - }, - { - "id": "cm-4.2", - "class": "SP800-53-enhancement", - "title": "Verification of Security Functions", - "props": [ - { - "name": "label", - "value": "CM-4(2)" - }, - { - "name": "sort-id", - "value": "cm-04.02" - } - ], - "parts": [ - { - "id": "cm-4.2_smt", - "name": "statement", - "prose": "The organization, after the information system is changed, checks the security functions to verify that the functions are implemented correctly, operating as intended, and producing the desired outcome with regard to meeting the security requirements for the system." - }, - { - "id": "cm-4.2_gdn", - "name": "guidance", - "prose": "Implementation is this context refers to installing changed code in the operational information system.", - "links": [ - { - "href": "#sa-11", - "rel": "related" - } - ] - }, - { - "id": "cm-4.2_obj", - "name": "objective", - "prose": "Determine if the organization, after the information system is changed, checks the security functions to verify that the functions are:", - "parts": [ - { - "id": "cm-4.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-4(2)[1]" - } - ], - "prose": "implemented correctly;" - }, - { - "id": "cm-4.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-4(2)[2]" - } - ], - "prose": "operating as intended; and" - }, - { - "id": "cm-4.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-4(2)[3]" - } - ], - "prose": "producing the desired outcome with regard to meeting the security requirements for the system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing security impact analysis for changes to the information system\n\nconfiguration management plan\n\nsecurity impact analysis documentation\n\nanalysis tools and associated outputs\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for conducting security impact analysis\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for security impact analysis\n\nautomated mechanisms supporting and/or implementing verification of security functions" - } - ] - } - ] - } - ] - }, - { - "id": "cm-5", - "class": "SP800-53", - "title": "Access Restrictions for Change", - "props": [ - { - "name": "label", - "value": "CM-5" - }, - { - "name": "sort-id", - "value": "cm-05" - } - ], - "parts": [ - { - "id": "cm-5_smt", - "name": "statement", - "prose": "The organization defines, documents, approves, and enforces physical and logical access restrictions associated with changes to the information system." - }, - { - "id": "cm-5_gdn", - "name": "guidance", - "prose": "Any changes to the hardware, software, and/or firmware components of information systems can potentially have significant effects on the overall security of the systems. Therefore, organizations permit only qualified and authorized individuals to access information systems for purposes of initiating changes, including upgrades and modifications. Organizations maintain records of access to ensure that configuration change control is implemented and to support after-the-fact actions should organizations discover any unauthorized changes. Access restrictions for change also include software libraries. Access restrictions include, for example, physical and logical access controls (see AC-3 and PE-3), workflow automation, media libraries, abstract layers (e.g., changes implemented into third-party interfaces rather than directly into information systems), and change windows (e.g., changes occur only during specified times, making unauthorized changes easy to discover).", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - } - ] - }, - { - "id": "cm-5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5[1]" - } - ], - "prose": "defines physical access restrictions associated with changes to the information system;" - }, - { - "id": "cm-5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5[2]" - } - ], - "prose": "documents physical access restrictions associated with changes to the information system;" - }, - { - "id": "cm-5_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5[3]" - } - ], - "prose": "approves physical access restrictions associated with changes to the information system;" - }, - { - "id": "cm-5_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5[4]" - } - ], - "prose": "enforces physical access restrictions associated with changes to the information system;" - }, - { - "id": "cm-5_obj.5", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5[5]" - } - ], - "prose": "defines logical access restrictions associated with changes to the information system;" - }, - { - "id": "cm-5_obj.6", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5[6]" - } - ], - "prose": "documents logical access restrictions associated with changes to the information system;" - }, - { - "id": "cm-5_obj.7", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5[7]" - } - ], - "prose": "approves logical access restrictions associated with changes to the information system; and" - }, - { - "id": "cm-5_obj.8", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5[8]" - } - ], - "prose": "enforces logical access restrictions associated with changes to the information system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing access restrictions for changes to the information system\n\nconfiguration management plan\n\ninformation system design documentation\n\ninformation system architecture and configuration documentation\n\ninformation system configuration settings and associated documentation\n\nlogical access approvals\n\nphysical access approvals\n\naccess credentials\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with logical access control responsibilities\n\norganizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing access restrictions to change\n\nautomated mechanisms supporting/implementing/enforcing access restrictions associated with changes to the information system" - } - ] - } - ], - "controls": [ - { - "id": "cm-5.1", - "class": "SP800-53-enhancement", - "title": "Automated Access Enforcement / Auditing", - "props": [ - { - "name": "label", - "value": "CM-5(1)" - }, - { - "name": "sort-id", - "value": "cm-05.01" - } - ], - "parts": [ - { - "id": "cm-5.1_smt", - "name": "statement", - "prose": "The information system enforces access restrictions and supports auditing of the enforcement actions." - }, - { - "id": "cm-5.1_gdn", - "name": "guidance", - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - } - ] - }, - { - "id": "cm-5.1_obj", - "name": "objective", - "prose": "Determine if the information system:", - "parts": [ - { - "id": "cm-5.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5(1)[1]" - } - ], - "prose": "enforces access restrictions for change; and" - }, - { - "id": "cm-5.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5(1)[2]" - } - ], - "prose": "supports auditing of the enforcement actions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing access restrictions for changes to the information system\n\ninformation system design documentation\n\ninformation system architecture and configuration documentation\n\ninformation system configuration settings and associated documentation\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing access restrictions to change\n\nautomated mechanisms implementing enforcement of access restrictions for changes to the information system\n\nautomated mechanisms supporting auditing of enforcement actions" - } - ] - } - ] - }, - { - "id": "cm-5.2", - "class": "SP800-53-enhancement", - "title": "Review System Changes", - "params": [ - { - "id": "cm-5.2_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "cm-5.2_prm_2", - "label": "organization-defined circumstances" - } - ], - "props": [ - { - "name": "label", - "value": "CM-5(2)" - }, - { - "name": "sort-id", - "value": "cm-05.02" - } - ], - "parts": [ - { - "id": "cm-5.2_smt", - "name": "statement", - "prose": "The organization reviews information system changes {{ insert: param, cm-5.2_prm_1 }} and {{ insert: param, cm-5.2_prm_2 }} to determine whether unauthorized changes have occurred." - }, - { - "id": "cm-5.2_gdn", - "name": "guidance", - "prose": "Indications that warrant review of information system changes and the specific circumstances justifying such reviews may be obtained from activities carried out by organizations during the configuration change process.", - "links": [ - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-7", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#pe-6", - "rel": "related" - }, - { - "href": "#pe-8", - "rel": "related" - } - ] - }, - { - "id": "cm-5.2_obj", - "name": "objective", - "prose": "Determine if the organization, in an effort to ascertain whether unauthorized changes have occurred:", - "parts": [ - { - "id": "cm-5.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5(2)[1]" - } - ], - "prose": "defines the frequency to review information system changes;" - }, - { - "id": "cm-5.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5(2)[2]" - } - ], - "prose": "defines circumstances that warrant review of information system changes;" - }, - { - "id": "cm-5.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5(2)[3]" - } - ], - "prose": "reviews information system changes with the organization-defined frequency; and" - }, - { - "id": "cm-5.2_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5(2)[4]" - } - ], - "prose": "reviews information system changes with the organization-defined circumstances." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing access restrictions for changes to the information system\n\nconfiguration management plan\n\nsecurity plan\n\nreviews of information system changes\n\naudit and review reports\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing access restrictions to change\n\nautomated mechanisms supporting/implementing information system reviews to determine whether unauthorized changes have occurred" - } - ] - } - ] - }, - { - "id": "cm-5.3", - "class": "SP800-53-enhancement", - "title": "Signed Components", - "params": [ - { - "id": "cm-5.3_prm_1", - "label": "organization-defined software and firmware components" - } - ], - "props": [ - { - "name": "label", - "value": "CM-5(3)" - }, - { - "name": "sort-id", - "value": "cm-05.03" - } - ], - "parts": [ - { - "id": "cm-5.3_smt", - "name": "statement", - "prose": "The information system prevents the installation of {{ insert: param, cm-5.3_prm_1 }} without verification that the component has been digitally signed using a certificate that is recognized and approved by the organization." - }, - { - "id": "cm-5.3_gdn", - "name": "guidance", - "prose": "Software and firmware components prevented from installation unless signed with recognized and approved certificates include, for example, software and firmware version updates, patches, service packs, device drivers, and basic input output system (BIOS) updates. Organizations can identify applicable software and firmware components by type, by specific items, or a combination of both. Digital signatures and organizational verification of such signatures, is a method of code authentication.", - "links": [ - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "cm-5.3_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "cm-5.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5(3)[1]" - } - ], - "prose": "the organization defines software and firmware components that the information system will prevent from being installed without verification that such components have been digitally signed using a certificate that is recognized and approved by the organization; and" - }, - { - "id": "cm-5.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5(3)[2]" - } - ], - "prose": "the information system prevents the installation of organization-defined software and firmware components without verification that such components have been digitally signed using a certificate that is recognized and approved by the organization." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing access restrictions for changes to the information system\n\nconfiguration management plan\n\nsecurity plan\n\nlist of software and firmware components to be prohibited from installation without a recognized and approved certificate\n\ninformation system design documentation\n\ninformation system architecture and configuration documentation\n\ninformation system configuration settings and associated documentation\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing access restrictions to change\n\nautomated mechanisms preventing installation of software and firmware components not signed with an organization-recognized and approved certificate" - } - ] - } - ] - }, - { - "id": "cm-5.4", - "class": "SP800-53-enhancement", - "title": "Dual Authorization", - "params": [ - { - "id": "cm-5.4_prm_1", - "label": "organization-defined information system components and system-level information" - } - ], - "props": [ - { - "name": "label", - "value": "CM-5(4)" - }, - { - "name": "sort-id", - "value": "cm-05.04" - } - ], - "parts": [ - { - "id": "cm-5.4_smt", - "name": "statement", - "prose": "The organization enforces dual authorization for implementing changes to {{ insert: param, cm-5.4_prm_1 }}." - }, - { - "id": "cm-5.4_gdn", - "name": "guidance", - "prose": "Organizations employ dual authorization to ensure that any changes to selected information system components and information cannot occur unless two qualified individuals implement such changes. The two individuals possess sufficient skills/expertise to determine if the proposed changes are correct implementations of approved changes. Dual authorization may also be known as two-person control.", - "links": [ - { - "href": "#ac-5", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - } - ] - }, - { - "id": "cm-5.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-5.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5(4)[1]" - } - ], - "prose": "defines information system components and system-level information requiring dual authorization to be enforced when implementing changes; and" - }, - { - "id": "cm-5.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5(4)[2]" - } - ], - "prose": "enforces dual authorization for implementing changes to organization-defined information system components and system-level information." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing access restrictions for changes to the information system\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system architecture and configuration documentation\n\ninformation system configuration settings and associated documentation\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with dual authorization enforcement responsibilities for implementing information system changes\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing access restrictions to change\n\nautomated mechanisms implementing dual authorization enforcement" - } - ] - } - ] - }, - { - "id": "cm-5.5", - "class": "SP800-53-enhancement", - "title": "Limit Production / Operational Privileges", - "params": [ - { - "id": "cm-5.5_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "CM-5(5)" - }, - { - "name": "sort-id", - "value": "cm-05.05" - } - ], - "parts": [ - { - "id": "cm-5.5_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cm-5.5_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Limits privileges to change information system components and system-related information within a production or operational environment; and" - }, - { - "id": "cm-5.5_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Reviews and reevaluates privileges {{ insert: param, cm-5.5_prm_1 }}." - } - ] - }, - { - "id": "cm-5.5_gdn", - "name": "guidance", - "prose": "In many organizations, information systems support multiple core missions/business functions. Limiting privileges to change information system components with respect to operational systems is necessary because changes to a particular information system component may have far-reaching effects on mission/business processes supported by the system where the component resides. The complex, many-to-many relationships between systems and mission/business processes are in some cases, unknown to developers.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - } - ] - }, - { - "id": "cm-5.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-5.5.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5(5)(a)" - } - ], - "prose": "limits privileges to change information system components and system-related information within a production or operational environment;", - "links": [ - { - "href": "#cm-5.5_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "cm-5.5.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5(5)(b)" - } - ], - "parts": [ - { - "id": "cm-5.5.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5(5)(b)[1]" - } - ], - "prose": "defines the frequency to review and reevaluate privileges; and" - }, - { - "id": "cm-5.5.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-5(5)(b)[2]" - } - ], - "prose": "reviews and reevaluates privileges with the organization-defined frequency." - } - ], - "links": [ - { - "href": "#cm-5.5_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing access restrictions for changes to the information system\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system architecture and configuration documentation\n\ninformation system configuration settings and associated documentation\n\nuser privilege reviews\n\nuser privilege recertifications\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing access restrictions to change\n\nautomated mechanisms supporting and/or implementing access restrictions for change" - } - ] - } - ] - }, - { - "id": "cm-5.6", - "class": "SP800-53-enhancement", - "title": "Limit Library Privileges", - "props": [ - { - "name": "label", - "value": "CM-5(6)" - }, - { - "name": "sort-id", - "value": "cm-05.06" - } - ], - "parts": [ - { - "id": "cm-5.6_smt", - "name": "statement", - "prose": "The organization limits privileges to change software resident within software libraries." - }, - { - "id": "cm-5.6_gdn", - "name": "guidance", - "prose": "Software libraries include privileged programs.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - } - ] - }, - { - "id": "cm-5.6_obj", - "name": "objective", - "prose": "Determine if the organization limits privileges to change software resident within software libraries." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing access restrictions for changes to the information system\n\nconfiguration management plan\n\ninformation system design documentation\n\ninformation system architecture and configuration documentation\n\ninformation system configuration settings and associated documentation\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing access restrictions to change\n\nautomated mechanisms supporting and/or implementing access restrictions for change" - } - ] - } - ] - }, - { - "id": "cm-5.7", - "class": "SP800-53-enhancement", - "title": "Automatic Implementation of Security Safeguards", - "props": [ - { - "name": "label", - "value": "CM-5(7)" - }, - { - "name": "sort-id", - "value": "cm-05.07" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#si-7", - "rel": "incorporated-into" - } - ] - } - ] - }, - { - "id": "cm-6", - "class": "SP800-53", - "title": "Configuration Settings", - "params": [ - { - "id": "cm-6_prm_1", - "label": "organization-defined security configuration checklists" - }, - { - "id": "cm-6_prm_2", - "label": "organization-defined information system components" - }, - { - "id": "cm-6_prm_3", - "label": "organization-defined operational requirements" - } - ], - "props": [ - { - "name": "label", - "value": "CM-6" - }, - { - "name": "sort-id", - "value": "cm-06" - } - ], - "links": [ - { - "href": "#990268bf-f4a9-4c81-91ae-dc7d3115f4b1", - "rel": "reference" - }, - { - "href": "#0b3d8ba9-051f-498d-81ea-97f0f018c612", - "rel": "reference" - }, - { - "href": "#0916ef02-3618-411b-a525-565c088849a6", - "rel": "reference" - }, - { - "href": "#84a37532-6db6-477b-9ea8-f9085ebca0fc", - "rel": "reference" - }, - { - "href": "#080f8068-5e3e-435e-9790-d22ba4722693", - "rel": "reference" - }, - { - "href": "#275cc052-0f7f-423c-bdb6-ed503dc36228", - "rel": "reference" - }, - { - "href": "#e95dd121-2733-413e-bf1e-f1eb49f20a98", - "rel": "reference" - }, - { - "href": "#647b6de3-81d0-4d22-bec1-5f1333e34380", - "rel": "reference" - } - ], - "parts": [ - { - "id": "cm-6_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cm-6_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Establishes and documents configuration settings for information technology products employed within the information system using {{ insert: param, cm-6_prm_1 }} that reflect the most restrictive mode consistent with operational requirements;" - }, - { - "id": "cm-6_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Implements the configuration settings;" - }, - { - "id": "cm-6_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Identifies, documents, and approves any deviations from established configuration settings for {{ insert: param, cm-6_prm_2 }} based on {{ insert: param, cm-6_prm_3 }}; and" - }, - { - "id": "cm-6_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Monitors and controls changes to the configuration settings in accordance with organizational policies and procedures." - } - ] - }, - { - "id": "cm-6_gdn", - "name": "guidance", - "prose": "Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the information system that affect the security posture and/or functionality of the system. Information technology products for which security-related configuration settings can be defined include, for example, mainframe computers, servers (e.g., database, electronic mail, authentication, web, proxy, file, domain name), workstations, input/output devices (e.g., scanners, copiers, and printers), network components (e.g., firewalls, routers, gateways, voice and data switches, wireless access points, network appliances, sensors), operating systems, middleware, and applications. Security-related parameters are those parameters impacting the security state of information systems including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: (i) registry settings; (ii) account, file, directory permission settings; and (iii) settings for functions, ports, protocols, services, and remote connections. Organizations establish organization-wide configuration settings and subsequently derive specific settings for information systems. The established settings become part of the systems configuration baseline. Common secure configurations (also referred to as security configuration checklists, lockdown and hardening guides, security reference guides, security technical implementation guides) provide recognized, standardized, and established benchmarks that stipulate secure configuration settings for specific information technology platforms/products and instructions for configuring those information system components to meet operational requirements. Common secure configurations can be developed by a variety of organizations including, for example, information technology product developers, manufacturers, vendors, consortia, academia, industry, federal agencies, and other organizations in the public and private sectors. Common secure configurations include the United States Government Configuration Baseline (USGCB) which affects the implementation of CM-6 and other controls such as AC-19 and CM-7. The Security Content Automation Protocol (SCAP) and the defined standards within the protocol (e.g., Common Configuration Enumeration) provide an effective method to uniquely identify, track, and control configuration settings. OMB establishes federal policy on configuration requirements for federal information systems.", - "links": [ - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "cm-6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-6.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(a)" - } - ], - "parts": [ - { - "id": "cm-6.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(a)[1]" - } - ], - "prose": "defines security configuration checklists to be used to establish and document configuration settings for the information technology products employed;" - }, - { - "id": "cm-6.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(a)[2]" - } - ], - "prose": "ensures the defined security configuration checklists reflect the most restrictive mode consistent with operational requirements;" - }, - { - "id": "cm-6.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(a)[3]" - } - ], - "prose": "establishes and documents configuration settings for information technology products employed within the information system using organization-defined security configuration checklists;" - } - ] - }, - { - "id": "cm-6.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(b)" - } - ], - "prose": "implements the configuration settings established/documented in CM-6(a);;" - }, - { - "id": "cm-6.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(c)" - } - ], - "parts": [ - { - "id": "cm-6.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(c)[1]" - } - ], - "prose": "defines information system components for which any deviations from established configuration settings must be:", - "parts": [ - { - "id": "cm-6.c_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(c)[1][a]" - } - ], - "prose": "identified;" - }, - { - "id": "cm-6.c_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(c)[1][b]" - } - ], - "prose": "documented;" - }, - { - "id": "cm-6.c_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(c)[1][c]" - } - ], - "prose": "approved;" - } - ] - }, - { - "id": "cm-6.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(c)[2]" - } - ], - "prose": "defines operational requirements to support:", - "parts": [ - { - "id": "cm-6.c_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(c)[2][a]" - } - ], - "prose": "the identification of any deviations from established configuration settings;" - }, - { - "id": "cm-6.c_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(c)[2][b]" - } - ], - "prose": "the documentation of any deviations from established configuration settings;" - }, - { - "id": "cm-6.c_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(c)[2][c]" - } - ], - "prose": "the approval of any deviations from established configuration settings;" - } - ] - }, - { - "id": "cm-6.c_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(c)[3]" - } - ], - "prose": "identifies any deviations from established configuration settings for organization-defined information system components based on organizational-defined operational requirements;" - }, - { - "id": "cm-6.c_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(c)[4]" - } - ], - "prose": "documents any deviations from established configuration settings for organization-defined information system components based on organizational-defined operational requirements;" - }, - { - "id": "cm-6.c_obj.5", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(c)[5]" - } - ], - "prose": "approves any deviations from established configuration settings for organization-defined information system components based on organizational-defined operational requirements;" - } - ] - }, - { - "id": "cm-6.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(d)" - } - ], - "parts": [ - { - "id": "cm-6.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(d)[1]" - } - ], - "prose": "monitors changes to the configuration settings in accordance with organizational policies and procedures; and" - }, - { - "id": "cm-6.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(d)[2]" - } - ], - "prose": "controls changes to the configuration settings in accordance with organizational policies and procedures." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing configuration settings for the information system\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsecurity configuration checklists\n\nevidence supporting approved deviations from established configuration settings\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security configuration management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing configuration settings\n\nautomated mechanisms that implement, monitor, and/or control information system configuration settings\n\nautomated mechanisms that identify and/or document deviations from established configuration settings" - } - ] - } - ], - "controls": [ - { - "id": "cm-6.1", - "class": "SP800-53-enhancement", - "title": "Automated Central Management / Application / Verification", - "params": [ - { - "id": "cm-6.1_prm_1", - "label": "organization-defined information system components" - } - ], - "props": [ - { - "name": "label", - "value": "CM-6(1)" - }, - { - "name": "sort-id", - "value": "cm-06.01" - } - ], - "parts": [ - { - "id": "cm-6.1_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to centrally manage, apply, and verify configuration settings for {{ insert: param, cm-6.1_prm_1 }}." - }, - { - "id": "cm-6.1_gdn", - "name": "guidance", - "links": [ - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - } - ] - }, - { - "id": "cm-6.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-6.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(1)[1]" - } - ], - "prose": "defines information system components for which automated mechanisms are to be employed to:", - "parts": [ - { - "id": "cm-6.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(1)[1][a]" - } - ], - "prose": "centrally manage configuration settings of such components;" - }, - { - "id": "cm-6.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(1)[1][b]" - } - ], - "prose": "apply configuration settings of such components;" - }, - { - "id": "cm-6.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(1)[1][c]" - } - ], - "prose": "verify configuration settings of such components;" - } - ] - }, - { - "id": "cm-6.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(1)[2]" - } - ], - "prose": "employs automated mechanisms to:", - "parts": [ - { - "id": "cm-6.1_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(1)[2][a]" - } - ], - "prose": "centrally manage configuration settings for organization-defined information system components;" - }, - { - "id": "cm-6.1_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(1)[2][b]" - } - ], - "prose": "apply configuration settings for organization-defined information system components; and" - }, - { - "id": "cm-6.1_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(1)[2][c]" - } - ], - "prose": "verify configuration settings for organization-defined information system components." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing configuration settings for the information system\n\nconfiguration management plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsecurity configuration checklists\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security configuration management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing configuration settings\n\nautomated mechanisms implemented to centrally manage, apply, and verify information system configuration settings" - } - ] - } - ] - }, - { - "id": "cm-6.2", - "class": "SP800-53-enhancement", - "title": "Respond to Unauthorized Changes", - "params": [ - { - "id": "cm-6.2_prm_1", - "label": "organization-defined security safeguards" - }, - { - "id": "cm-6.2_prm_2", - "label": "organization-defined configuration settings" - } - ], - "props": [ - { - "name": "label", - "value": "CM-6(2)" - }, - { - "name": "sort-id", - "value": "cm-06.02" - } - ], - "parts": [ - { - "id": "cm-6.2_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, cm-6.2_prm_1 }} to respond to unauthorized changes to {{ insert: param, cm-6.2_prm_2 }}." - }, - { - "id": "cm-6.2_gdn", - "name": "guidance", - "prose": "Responses to unauthorized changes to configuration settings can include, for example, alerting designated organizational personnel, restoring established configuration settings, or in extreme cases, halting affected information system processing.", - "links": [ - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "cm-6.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-6.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(2)[1]" - } - ], - "prose": "defines configuration settings that, if modified by unauthorized changes, result in organizational security safeguards being employed to respond to such changes;" - }, - { - "id": "cm-6.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(2)[2]" - } - ], - "prose": "defines security safeguards to be employed to respond to unauthorized changes to organization-defined configuration settings; and" - }, - { - "id": "cm-6.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-6(2)[3]" - } - ], - "prose": "employs organization-defined security safeguards to respond to unauthorized changes to organization-defined configuration settings." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing configuration settings for the information system\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nalerts/notifications of unauthorized changes to information system configuration settings\n\ndocumented responses to unauthorized changes to information system configuration settings\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security configuration management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational process for responding to unauthorized changes to information system configuration settings\n\nautomated mechanisms supporting and/or implementing security safeguards for response to unauthorized changes" - } - ] - } - ] - }, - { - "id": "cm-6.3", - "class": "SP800-53-enhancement", - "title": "Unauthorized Change Detection", - "props": [ - { - "name": "label", - "value": "CM-6(3)" - }, - { - "name": "sort-id", - "value": "cm-06.03" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#si-7", - "rel": "incorporated-into" - } - ] - }, - { - "id": "cm-6.4", - "class": "SP800-53-enhancement", - "title": "Conformance Demonstration", - "props": [ - { - "name": "label", - "value": "CM-6(4)" - }, - { - "name": "sort-id", - "value": "cm-06.04" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#cm-4", - "rel": "incorporated-into" - } - ] - } - ] - }, - { - "id": "cm-7", - "class": "SP800-53", - "title": "Least Functionality", - "params": [ - { - "id": "cm-7_prm_1", - "label": "organization-defined prohibited or restricted functions, ports, protocols, and/or services" - } - ], - "props": [ - { - "name": "label", - "value": "CM-7" - }, - { - "name": "sort-id", - "value": "cm-07" - } - ], - "links": [ - { - "href": "#e42b2099-3e1c-415b-952c-61c96533c12e", - "rel": "reference" - } - ], - "parts": [ - { - "id": "cm-7_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cm-7_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Configures the information system to provide only essential capabilities; and" - }, - { - "id": "cm-7_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Prohibits or restricts the use of the following functions, ports, protocols, and/or services: {{ insert: param, cm-7_prm_1 }}." - } - ] - }, - { - "id": "cm-7_gdn", - "name": "guidance", - "prose": "Information systems can provide a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). Additionally, it is sometimes convenient to provide multiple services from single information system components, but doing so increases risk over limiting the services provided by any one component. Where feasible, organizations limit component functionality to a single function per device (e.g., email servers or web servers, but not both). Organizations review functions and services provided by information systems or individual components of information systems, to determine which functions and services are candidates for elimination (e.g., Voice Over Internet Protocol, Instant Messaging, auto-execute, and file sharing). Organizations consider disabling unused or unnecessary physical and logical ports/protocols (e.g., Universal Serial Bus, File Transfer Protocol, and Hyper Text Transfer Protocol) on information systems to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling. Organizations can utilize network scanning tools, intrusion detection and prevention systems, and end-point protections such as firewalls and host-based intrusion detection systems to identify and prevent the use of prohibited functions, ports, protocols, and services.", - "links": [ - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - } - ] - }, - { - "id": "cm-7_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-7.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(a)" - } - ], - "prose": "configures the information system to provide only essential capabilities;" - }, - { - "id": "cm-7.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(b)" - } - ], - "parts": [ - { - "id": "cm-7.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(b)[1]" - } - ], - "prose": "defines prohibited or restricted:", - "parts": [ - { - "id": "cm-7.b_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(b)[1][a]" - } - ], - "prose": "functions;" - }, - { - "id": "cm-7.b_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(b)[1][b]" - } - ], - "prose": "ports;" - }, - { - "id": "cm-7.b_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(b)[1][c]" - } - ], - "prose": "protocols; and/or" - }, - { - "id": "cm-7.b_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(b)[1][d]" - } - ], - "prose": "services;" - } - ] - }, - { - "id": "cm-7.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(b)[2]" - } - ], - "prose": "prohibits or restricts the use of organization-defined:", - "parts": [ - { - "id": "cm-7.b_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(b)[2][a]" - } - ], - "prose": "functions;" - }, - { - "id": "cm-7.b_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(b)[2][b]" - } - ], - "prose": "ports;" - }, - { - "id": "cm-7.b_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(b)[2][c]" - } - ], - "prose": "protocols; and/or" - }, - { - "id": "cm-7.b_obj.2.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(b)[2][d]" - } - ], - "prose": "services." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nconfiguration management plan\n\nprocedures addressing least functionality in the information system\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsecurity configuration checklists\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security configuration management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes prohibiting or restricting functions, ports, protocols, and/or services\n\nautomated mechanisms implementing restrictions or prohibition of functions, ports, protocols, and/or services" - } - ] - } - ], - "controls": [ - { - "id": "cm-7.1", - "class": "SP800-53-enhancement", - "title": "Periodic Review", - "params": [ - { - "id": "cm-7.1_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "cm-7.1_prm_2", - "label": "organization-defined functions, ports, protocols, and services within the information system deemed to be unnecessary and/or nonsecure" - } - ], - "props": [ - { - "name": "label", - "value": "CM-7(1)" - }, - { - "name": "sort-id", - "value": "cm-07.01" - } - ], - "parts": [ - { - "id": "cm-7.1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cm-7.1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Reviews the information system {{ insert: param, cm-7.1_prm_1 }} to identify unnecessary and/or nonsecure functions, ports, protocols, and services; and" - }, - { - "id": "cm-7.1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Disables {{ insert: param, cm-7.1_prm_2 }}." - } - ] - }, - { - "id": "cm-7.1_gdn", - "name": "guidance", - "prose": "The organization can either make a determination of the relative security of the function, port, protocol, and/or service or base the security decision on the assessment of other entities. Bluetooth, FTP, and peer-to-peer networking are examples of less than secure protocols.", - "links": [ - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - } - ] - }, - { - "id": "cm-7.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-7.1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(a)" - } - ], - "parts": [ - { - "id": "cm-7.1.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(a)[1]" - } - ], - "prose": "defines the frequency to review the information system to identify unnecessary and/or nonsecure:", - "parts": [ - { - "id": "cm-7.1.a_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(a)[1][a]" - } - ], - "prose": "functions;" - }, - { - "id": "cm-7.1.a_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(a)[1][b]" - } - ], - "prose": "ports;" - }, - { - "id": "cm-7.1.a_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(a)[1][c]" - } - ], - "prose": "protocols; and/or" - }, - { - "id": "cm-7.1.a_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(a)[1][d]" - } - ], - "prose": "services;" - } - ] - }, - { - "id": "cm-7.1.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(a)[2]" - } - ], - "prose": "reviews the information system with the organization-defined frequency to identify unnecessary and/or nonsecure:", - "parts": [ - { - "id": "cm-7.1.a_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(a)[2][a]" - } - ], - "prose": "functions;" - }, - { - "id": "cm-7.1.a_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(a)[2][b]" - } - ], - "prose": "ports;" - }, - { - "id": "cm-7.1.a_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(a)[2][c]" - } - ], - "prose": "protocols; and/or" - }, - { - "id": "cm-7.1.a_obj.2.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(a)[2][d]" - } - ], - "prose": "services;" - } - ] - } - ], - "links": [ - { - "href": "#cm-7.1_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "cm-7.1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(b)" - } - ], - "parts": [ - { - "id": "cm-7.1.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(b)[1]" - } - ], - "prose": "defines, within the information system, unnecessary and/or nonsecure:", - "parts": [ - { - "id": "cm-7.1.b_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(b)[1][a]" - } - ], - "prose": "functions;" - }, - { - "id": "cm-7.1.b_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(b)[1][b]" - } - ], - "prose": "ports;" - }, - { - "id": "cm-7.1.b_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(b)[1][c]" - } - ], - "prose": "protocols; and/or" - }, - { - "id": "cm-7.1.b_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(b)[1][d]" - } - ], - "prose": "services;" - } - ] - }, - { - "id": "cm-7.1.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(b)[2]" - } - ], - "prose": "disables organization-defined unnecessary and/or nonsecure:", - "parts": [ - { - "id": "cm-7.1.b_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(b)[2][a]" - } - ], - "prose": "functions;" - }, - { - "id": "cm-7.1.b_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(b)[2][b]" - } - ], - "prose": "ports;" - }, - { - "id": "cm-7.1.b_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(b)[2][c]" - } - ], - "prose": "protocols; and/or" - }, - { - "id": "cm-7.1.b_obj.2.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(1)(b)[2][d]" - } - ], - "prose": "services." - } - ] - } - ], - "links": [ - { - "href": "#cm-7.1_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing least functionality in the information system\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsecurity configuration checklists\n\ndocumented reviews of functions, ports, protocols, and/or services\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for reviewing functions, ports, protocols, and services on the information system\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for reviewing/disabling nonsecure functions, ports, protocols, and/or services\n\nautomated mechanisms implementing review and disabling of nonsecure functions, ports, protocols, and/or services" - } - ] - } - ] - }, - { - "id": "cm-7.2", - "class": "SP800-53-enhancement", - "title": "Prevent Program Execution", - "params": [ - { - "id": "cm-7.2_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - " {{ insert: param, cm-7.2_prm_2 }} ", - "rules authorizing the terms and conditions of software program usage" - ] - } - }, - { - "id": "cm-7.2_prm_2", - "depends-on": "cm-7.2_prm_1", - "label": "organization-defined policies regarding software program usage and restrictions" - } - ], - "props": [ - { - "name": "label", - "value": "CM-7(2)" - }, - { - "name": "sort-id", - "value": "cm-07.02" - } - ], - "parts": [ - { - "id": "cm-7.2_smt", - "name": "statement", - "prose": "The information system prevents program execution in accordance with {{ insert: param, cm-7.2_prm_1 }}." - }, - { - "id": "cm-7.2_gdn", - "name": "guidance", - "links": [ - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#pm-5", - "rel": "related" - } - ] - }, - { - "id": "cm-7.2_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "cm-7.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(2)[1]" - } - ], - "prose": "the organization defines policies regarding software program usage and restrictions;" - }, - { - "id": "cm-7.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(2)[2]" - } - ], - "prose": "the information system prevents program execution in accordance with one or more of the following:", - "parts": [ - { - "id": "cm-7.2_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(2)[2][a]" - } - ], - "prose": "organization-defined policies regarding program usage and restrictions; and/or" - }, - { - "id": "cm-7.2_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(2)[2][b]" - } - ], - "prose": "rules authorizing the terms and conditions of software program usage." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing least functionality in the information system\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system design documentation\n\nspecifications for preventing software program execution\n\ninformation system configuration settings and associated documentation\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes preventing program execution on the information system\n\norganizational processes for software program usage and restrictions\n\nautomated mechanisms preventing program execution on the information system\n\nautomated mechanisms supporting and/or implementing software program usage and restrictions" - } - ] - } - ] - }, - { - "id": "cm-7.3", - "class": "SP800-53-enhancement", - "title": "Registration Compliance", - "params": [ - { - "id": "cm-7.3_prm_1", - "label": "organization-defined registration requirements for functions, ports, protocols, and services" - } - ], - "props": [ - { - "name": "label", - "value": "CM-7(3)" - }, - { - "name": "sort-id", - "value": "cm-07.03" - } - ], - "parts": [ - { - "id": "cm-7.3_smt", - "name": "statement", - "prose": "The organization ensures compliance with {{ insert: param, cm-7.3_prm_1 }}." - }, - { - "id": "cm-7.3_gdn", - "name": "guidance", - "prose": "Organizations use the registration process to manage, track, and provide oversight for information systems and implemented functions, ports, protocols, and services." - }, - { - "id": "cm-7.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-7.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(3)[1]" - } - ], - "prose": "defines registration requirements for:", - "parts": [ - { - "id": "cm-7.3_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(3)[1][a]" - } - ], - "prose": "functions;" - }, - { - "id": "cm-7.3_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(3)[1][b]" - } - ], - "prose": "ports;" - }, - { - "id": "cm-7.3_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(3)[1][c]" - } - ], - "prose": "protocols; and/or" - }, - { - "id": "cm-7.3_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(3)[1][d]" - } - ], - "prose": "services;" - } - ] - }, - { - "id": "cm-7.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(3)[2]" - } - ], - "prose": "ensures compliance with organization-defined registration requirements for:", - "parts": [ - { - "id": "cm-7.3_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(3)[2][a]" - } - ], - "prose": "functions;" - }, - { - "id": "cm-7.3_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(3)[2][b]" - } - ], - "prose": "ports;" - }, - { - "id": "cm-7.3_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(3)[2][c]" - } - ], - "prose": "protocols; and/or" - }, - { - "id": "cm-7.3_obj.2.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(3)[2][d]" - } - ], - "prose": "services." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing least functionality in the information system\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system configuration settings and associated documentation\n\naudit and compliance reviews\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes ensuring compliance with registration requirements for functions, ports, protocols, and/or services\n\nautomated mechanisms implementing compliance with registration requirements for functions, ports, protocols, and/or services" - } - ] - } - ] - }, - { - "id": "cm-7.4", - "class": "SP800-53-enhancement", - "title": "Unauthorized Software / Blacklisting", - "params": [ - { - "id": "cm-7.4_prm_1", - "label": "organization-defined software programs not authorized to execute on the information system" - }, - { - "id": "cm-7.4_prm_2", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "CM-7(4)" - }, - { - "name": "sort-id", - "value": "cm-07.04" - } - ], - "parts": [ - { - "id": "cm-7.4_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cm-7.4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Identifies {{ insert: param, cm-7.4_prm_1 }};" - }, - { - "id": "cm-7.4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Employs an allow-all, deny-by-exception policy to prohibit the execution of unauthorized software programs on the information system; and" - }, - { - "id": "cm-7.4_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Reviews and updates the list of unauthorized software programs {{ insert: param, cm-7.4_prm_2 }}." - } - ] - }, - { - "id": "cm-7.4_gdn", - "name": "guidance", - "prose": "The process used to identify software programs that are not authorized to execute on organizational information systems is commonly referred to as blacklisting. Organizations can implement CM-7 (5) instead of this control enhancement if whitelisting (the stronger of the two policies) is the preferred approach for restricting software program execution.", - "links": [ - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#pm-5", - "rel": "related" - } - ] - }, - { - "id": "cm-7.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-7.4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(4)(a)" - } - ], - "prose": "Identifies/defines software programs not authorized to execute on the information system;", - "links": [ - { - "href": "#cm-7.4_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "cm-7.4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(4)(b)" - } - ], - "prose": "employs an allow-all, deny-by-exception policy to prohibit the execution of unauthorized software programs on the information system;", - "links": [ - { - "href": "#cm-7.4_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "cm-7.4.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(4)(c)" - } - ], - "parts": [ - { - "id": "cm-7.4.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(4)(c)[1]" - } - ], - "prose": "defines the frequency to review and update the list of unauthorized software programs on the information system; and" - }, - { - "id": "cm-7.4.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(4)(c)[2]" - } - ], - "prose": "reviews and updates the list of unauthorized software programs with the organization-defined frequency." - } - ], - "links": [ - { - "href": "#cm-7.4_smt.c", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing least functionality in the information system\n\nconfiguration management plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of software programs not authorized to execute on the information system\n\nsecurity configuration checklists\n\nreview and update records associated with list of unauthorized software programs\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for identifying software not authorized to execute on the information system\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational process for identifying, reviewing, and updating programs not authorized to execute on the information system\n\norganizational process for implementing blacklisting\n\nautomated mechanisms supporting and/or implementing blacklisting" - } - ] - } - ] - }, - { - "id": "cm-7.5", - "class": "SP800-53-enhancement", - "title": "Authorized Software / Whitelisting", - "params": [ - { - "id": "cm-7.5_prm_1", - "label": "organization-defined software programs authorized to execute on the information system" - }, - { - "id": "cm-7.5_prm_2", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "CM-7(5)" - }, - { - "name": "sort-id", - "value": "cm-07.05" - } - ], - "parts": [ - { - "id": "cm-7.5_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cm-7.5_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Identifies {{ insert: param, cm-7.5_prm_1 }};" - }, - { - "id": "cm-7.5_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the information system; and" - }, - { - "id": "cm-7.5_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Reviews and updates the list of authorized software programs {{ insert: param, cm-7.5_prm_2 }}." - } - ] - }, - { - "id": "cm-7.5_gdn", - "name": "guidance", - "prose": "The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as whitelisting. In addition to whitelisting, organizations consider verifying the integrity of white-listed software programs using, for example, cryptographic checksums, digital signatures, or hash functions. Verification of white-listed software can occur either prior to execution or at system startup.", - "links": [ - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#pm-5", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - }, - { - "href": "#sc-34", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "cm-7.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-7.5.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(5)(a)" - } - ], - "prose": "Identifies/defines software programs authorized to execute on the information system;", - "links": [ - { - "href": "#cm-7.5_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "cm-7.5.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(5)(b)" - } - ], - "prose": "employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the information system;", - "links": [ - { - "href": "#cm-7.5_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "cm-7.5.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(5)(c)" - } - ], - "parts": [ - { - "id": "cm-7.5.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(5)(c)[1]" - } - ], - "prose": "defines the frequency to review and update the list of authorized software programs on the information system; and" - }, - { - "id": "cm-7.5.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-7(5)(c)[2]" - } - ], - "prose": "reviews and updates the list of authorized software programs with the organization-defined frequency." - } - ], - "links": [ - { - "href": "#cm-7.5_smt.c", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing least functionality in the information system\n\nconfiguration management plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of software programs authorized to execute on the information system\n\nsecurity configuration checklists\n\nreview and update records associated with list of authorized software programs\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for identifying software authorized to execute on the information system\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational process for identifying, reviewing, and updating programs authorized to execute on the information system\n\norganizational process for implementing whitelisting\n\nautomated mechanisms implementing whitelisting" - } - ] - } - ] - } - ] - }, - { - "id": "cm-8", - "class": "SP800-53", - "title": "Information System Component Inventory", - "params": [ - { - "id": "cm-8_prm_1", - "label": "organization-defined information deemed necessary to achieve effective information system component accountability" - }, - { - "id": "cm-8_prm_2", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "CM-8" - }, - { - "name": "sort-id", - "value": "cm-08" - } - ], - "links": [ - { - "href": "#080f8068-5e3e-435e-9790-d22ba4722693", - "rel": "reference" - } - ], - "parts": [ - { - "id": "cm-8_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cm-8_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops and documents an inventory of information system components that:", - "parts": [ - { - "id": "cm-8_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Accurately reflects the current information system;" - }, - { - "id": "cm-8_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Includes all components within the authorization boundary of the information system;" - }, - { - "id": "cm-8_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Is at the level of granularity deemed necessary for tracking and reporting; and" - }, - { - "id": "cm-8_smt.a.4", - "name": "item", - "props": [ - { - "name": "label", - "value": "4." - } - ], - "prose": "Includes {{ insert: param, cm-8_prm_1 }}; and" - } - ] - }, - { - "id": "cm-8_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the information system component inventory {{ insert: param, cm-8_prm_2 }}." - } - ] - }, - { - "id": "cm-8_gdn", - "name": "guidance", - "prose": "Organizations may choose to implement centralized information system component inventories that include components from all organizational information systems. In such situations, organizations ensure that the resulting inventories include system-specific information required for proper component accountability (e.g., information system association, information system owner). Information deemed necessary for effective accountability of information system components includes, for example, hardware inventory specifications, software license information, software version numbers, component owners, and for networked components or devices, machine names and network addresses. Inventory specifications include, for example, manufacturer, device type, model, serial number, and physical location.", - "links": [ - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#pm-5", - "rel": "related" - } - ] - }, - { - "id": "cm-8_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-8.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(a)" - } - ], - "parts": [ - { - "id": "cm-8.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(a)(1)" - } - ], - "prose": "develops and documents an inventory of information system components that accurately reflects the current information system;" - }, - { - "id": "cm-8.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(a)(2)" - } - ], - "prose": "develops and documents an inventory of information system components that includes all components within the authorization boundary of the information system;" - }, - { - "id": "cm-8.a.3_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(a)(3)" - } - ], - "prose": "develops and documents an inventory of information system components that is at the level of granularity deemed necessary for tracking and reporting;" - }, - { - "id": "cm-8.a.4_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(a)(4)" - } - ], - "parts": [ - { - "id": "cm-8.a.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(a)(4)[1]" - } - ], - "prose": "defines the information deemed necessary to achieve effective information system component accountability;" - }, - { - "id": "cm-8.a.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(a)(4)[2]" - } - ], - "prose": "develops and documents an inventory of information system components that includes organization-defined information deemed necessary to achieve effective information system component accountability;" - } - ] - } - ] - }, - { - "id": "cm-8.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(b)" - } - ], - "parts": [ - { - "id": "cm-8.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(b)[1]" - } - ], - "prose": "defines the frequency to review and update the information system component inventory; and" - }, - { - "id": "cm-8.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(b)[2]" - } - ], - "prose": "reviews and updates the information system component inventory with the organization-defined frequency." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing information system component inventory\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system inventory records\n\ninventory reviews and update records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for information system component inventory\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for developing and documenting an inventory of information system components\n\nautomated mechanisms supporting and/or implementing the information system component inventory" - } - ] - } - ], - "controls": [ - { - "id": "cm-8.1", - "class": "SP800-53-enhancement", - "title": "Updates During Installations / Removals", - "props": [ - { - "name": "label", - "value": "CM-8(1)" - }, - { - "name": "sort-id", - "value": "cm-08.01" - } - ], - "parts": [ - { - "id": "cm-8.1_smt", - "name": "statement", - "prose": "The organization updates the inventory of information system components as an integral part of component installations, removals, and information system updates." - }, - { - "id": "cm-8.1_obj", - "name": "objective", - "prose": "Determine if the organization updates the inventory of information system components as an integral part of:", - "parts": [ - { - "id": "cm-8.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(1)[1]" - } - ], - "prose": "component installations;" - }, - { - "id": "cm-8.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(1)[2]" - } - ], - "prose": "component removals; and" - }, - { - "id": "cm-8.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(1)[3]" - } - ], - "prose": "information system updates." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing information system component inventory\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system inventory records\n\ninventory reviews and update records\n\ncomponent installation records\n\ncomponent removal records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for updating the information system component inventory\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for updating inventory of information system components\n\nautomated mechanisms implementing updating of the information system component inventory" - } - ] - } - ] - }, - { - "id": "cm-8.2", - "class": "SP800-53-enhancement", - "title": "Automated Maintenance", - "props": [ - { - "name": "label", - "value": "CM-8(2)" - }, - { - "name": "sort-id", - "value": "cm-08.02" - } - ], - "parts": [ - { - "id": "cm-8.2_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to help maintain an up-to-date, complete, accurate, and readily available inventory of information system components." - }, - { - "id": "cm-8.2_gdn", - "name": "guidance", - "prose": "Organizations maintain information system inventories to the extent feasible. Virtual machines, for example, can be difficult to monitor because such machines are not visible to the network when not in use. In such cases, organizations maintain as up-to-date, complete, and accurate an inventory as is deemed reasonable. This control enhancement can be satisfied by the implementation of CM-2 (2) for organizations that choose to combine information system component inventory and baseline configuration activities.", - "links": [ - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "cm-8.2_obj", - "name": "objective", - "prose": "Determine if the organization employs automated mechanisms to maintain an inventory of information system components that is:", - "parts": [ - { - "id": "cm-8.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(2)[1]" - } - ], - "prose": "up-to-date;" - }, - { - "id": "cm-8.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(2)[2]" - } - ], - "prose": "complete;" - }, - { - "id": "cm-8.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(2)[3]" - } - ], - "prose": "accurate; and" - }, - { - "id": "cm-8.2_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(2)[4]" - } - ], - "prose": "readily available." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nconfiguration management plan\n\nprocedures addressing information system component inventory\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system inventory records\n\nchange control records\n\ninformation system maintenance records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for managing the automated mechanisms implementing the information system component inventory\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for maintaining the inventory of information system components\n\nautomated mechanisms implementing the information system component inventory" - } - ] - } - ] - }, - { - "id": "cm-8.3", - "class": "SP800-53-enhancement", - "title": "Automated Unauthorized Component Detection", - "params": [ - { - "id": "cm-8.3_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "cm-8.3_prm_2", - "select": { - "how-many": "one-or-more", - "choice": [ - "disables network access by such components", - "isolates the components", - "notifies {{ insert: param, cm-8.3_prm_3 }} " - ] - } - }, - { - "id": "cm-8.3_prm_3", - "depends-on": "cm-8.3_prm_2", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "CM-8(3)" - }, - { - "name": "sort-id", - "value": "cm-08.03" - } - ], - "parts": [ - { - "id": "cm-8.3_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cm-8.3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Employs automated mechanisms {{ insert: param, cm-8.3_prm_1 }} to detect the presence of unauthorized hardware, software, and firmware components within the information system; and" - }, - { - "id": "cm-8.3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Takes the following actions when unauthorized components are detected: {{ insert: param, cm-8.3_prm_2 }}." - } - ] - }, - { - "id": "cm-8.3_gdn", - "name": "guidance", - "prose": "This control enhancement is applied in addition to the monitoring for unauthorized remote connections and mobile devices. Monitoring for unauthorized system components may be accomplished on an ongoing basis or by the periodic scanning of systems for that purpose. Automated mechanisms can be implemented within information systems or in other separate devices. Isolation can be achieved, for example, by placing unauthorized information system components in separate domains or subnets or otherwise quarantining such components. This type of component isolation is commonly referred to as sandboxing.", - "links": [ - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - } - ] - }, - { - "id": "cm-8.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-8.3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(3)(a)" - } - ], - "parts": [ - { - "id": "cm-8.3.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(3)(a)[1]" - } - ], - "prose": "defines the frequency to employ automated mechanisms to detect the presence of unauthorized:", - "parts": [ - { - "id": "cm-8.3.a_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(3)(a)[1][a]" - } - ], - "prose": "hardware components within the information system;" - }, - { - "id": "cm-8.3.a_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(3)(a)[1][b]" - } - ], - "prose": "software components within the information system;" - }, - { - "id": "cm-8.3.a_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(3)(a)[1][c]" - } - ], - "prose": "firmware components within the information system;" - } - ] - }, - { - "id": "cm-8.3.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(3)(a)[2]" - } - ], - "prose": "employs automated mechanisms with the organization-defined frequency to detect the presence of unauthorized:", - "parts": [ - { - "id": "cm-8.3.a_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(3)(a)[2][a]" - } - ], - "prose": "hardware components within the information system;" - }, - { - "id": "cm-8.3.a_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(3)(a)[2][b]" - } - ], - "prose": "software components within the information system;" - }, - { - "id": "cm-8.3.a_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(3)(a)[2][c]" - } - ], - "prose": "firmware components within the information system;" - } - ] - } - ], - "links": [ - { - "href": "#cm-8.3_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "cm-8.3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(3)(b)" - } - ], - "parts": [ - { - "id": "cm-8.3.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(3)(b)[1]" - } - ], - "prose": "defines personnel or roles to be notified when unauthorized components are detected;" - }, - { - "id": "cm-8.3.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(3)(b)[2]" - } - ], - "prose": "takes one or more of the following actions when unauthorized components are detected:", - "parts": [ - { - "id": "cm-8.3.b_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(3)(b)[2][a]" - } - ], - "prose": "disables network access by such components;" - }, - { - "id": "cm-8.3.b_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(3)(b)[2][b]" - } - ], - "prose": "isolates the components; and/or" - }, - { - "id": "cm-8.3.b_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(3)(b)[2][c]" - } - ], - "prose": "notifies organization-defined personnel or roles." - } - ] - } - ], - "links": [ - { - "href": "#cm-8.3_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing information system component inventory\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system inventory records\n\nalerts/notifications of unauthorized components within the information system\n\ninformation system monitoring records\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for managing the automated mechanisms implementing unauthorized information system component detection\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for detection of unauthorized information system components\n\nautomated mechanisms implementing the detection of unauthorized information system components" - } - ] - } - ] - }, - { - "id": "cm-8.4", - "class": "SP800-53-enhancement", - "title": "Accountability Information", - "params": [ - { - "id": "cm-8.4_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "name", - "position", - "role" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "CM-8(4)" - }, - { - "name": "sort-id", - "value": "cm-08.04" - } - ], - "parts": [ - { - "id": "cm-8.4_smt", - "name": "statement", - "prose": "The organization includes in the information system component inventory information, a means for identifying by {{ insert: param, cm-8.4_prm_1 }}, individuals responsible/accountable for administering those components." - }, - { - "id": "cm-8.4_gdn", - "name": "guidance", - "prose": "Identifying individuals who are both responsible and accountable for administering information system components helps to ensure that the assigned components are properly administered and organizations can contact those individuals if some action is required (e.g., component is determined to be the source of a breach/compromise, component needs to be recalled/replaced, or component needs to be relocated)." - }, - { - "id": "cm-8.4_obj", - "name": "objective", - "prose": "Determine if the organization includes in the information system component inventory for information system components, a means for identifying the individuals responsible and accountable for administering those components by one or more of the following:", - "parts": [ - { - "id": "cm-8.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(4)[1]" - } - ], - "prose": "name;" - }, - { - "id": "cm-8.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(4)[2]" - } - ], - "prose": "position; and/or" - }, - { - "id": "cm-8.4_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(4)[3]" - } - ], - "prose": "role." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing information system component inventory\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system inventory records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for managing the information system component inventory\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for maintaining the inventory of information system components\n\nautomated mechanisms implementing the information system component inventory" - } - ] - } - ] - }, - { - "id": "cm-8.5", - "class": "SP800-53-enhancement", - "title": "No Duplicate Accounting of Components", - "props": [ - { - "name": "label", - "value": "CM-8(5)" - }, - { - "name": "sort-id", - "value": "cm-08.05" - } - ], - "parts": [ - { - "id": "cm-8.5_smt", - "name": "statement", - "prose": "The organization verifies that all components within the authorization boundary of the information system are not duplicated in other information system component inventories." - }, - { - "id": "cm-8.5_gdn", - "name": "guidance", - "prose": "This control enhancement addresses the potential problem of duplicate accounting of information system components in large or complex interconnected systems." - }, - { - "id": "cm-8.5_obj", - "name": "objective", - "prose": "Determine if the organization verifies that all components within the authorization boundary of the information system are not duplicated in other information system inventories." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing information system component inventory\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system inventory records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system inventory responsibilities\n\norganizational personnel with responsibilities for defining information system components within the authorization boundary of the system\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for maintaining the inventory of information system components\n\nautomated mechanisms implementing the information system component inventory" - } - ] - } - ] - }, - { - "id": "cm-8.6", - "class": "SP800-53-enhancement", - "title": "Assessed Configurations / Approved Deviations", - "props": [ - { - "name": "label", - "value": "CM-8(6)" - }, - { - "name": "sort-id", - "value": "cm-08.06" - } - ], - "parts": [ - { - "id": "cm-8.6_smt", - "name": "statement", - "prose": "The organization includes assessed component configurations and any approved deviations to current deployed configurations in the information system component inventory." - }, - { - "id": "cm-8.6_gdn", - "name": "guidance", - "prose": "This control enhancement focuses on configuration settings established by organizations for information system components, the specific components that have been assessed to determine compliance with the required configuration settings, and any approved deviations from established configuration settings.", - "links": [ - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - } - ] - }, - { - "id": "cm-8.6_obj", - "name": "objective", - "prose": "Determine if the organization includes in the information system component inventory:", - "parts": [ - { - "id": "cm-8.6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(6)[1]" - } - ], - "prose": "assessed component configurations; and" - }, - { - "id": "cm-8.6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(6)[2]" - } - ], - "prose": "any approved deviations to current deployed configurations." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing information system component inventory\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system inventory records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with inventory management and assessment responsibilities for information system components\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for maintaining the inventory of information system components\n\nautomated mechanisms implementing the information system component inventory" - } - ] - } - ] - }, - { - "id": "cm-8.7", - "class": "SP800-53-enhancement", - "title": "Centralized Repository", - "props": [ - { - "name": "label", - "value": "CM-8(7)" - }, - { - "name": "sort-id", - "value": "cm-08.07" - } - ], - "parts": [ - { - "id": "cm-8.7_smt", - "name": "statement", - "prose": "The organization provides a centralized repository for the inventory of information system components." - }, - { - "id": "cm-8.7_gdn", - "name": "guidance", - "prose": "Organizations may choose to implement centralized information system component inventories that include components from all organizational information systems. Centralized repositories of information system component inventories provide opportunities for efficiencies in accounting for organizational hardware, software, and firmware assets. Such repositories may also help organizations rapidly identify the location and responsible individuals of system components that have been compromised, breached, or are otherwise in need of mitigation actions. Organizations ensure that the resulting centralized inventories include system-specific information required for proper component accountability (e.g., information system association, information system owner)." - }, - { - "id": "cm-8.7_obj", - "name": "objective", - "prose": "Determine if the organization provides a centralized repository for the inventory of information system components." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing information system component inventory\n\nconfiguration management plan\n\ninformation system design documentation\n\ninformation system inventory repository\n\ninformation system inventory records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with inventory management responsibilities for information system components\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing the information system component inventory in a centralized repository" - } - ] - } - ] - }, - { - "id": "cm-8.8", - "class": "SP800-53-enhancement", - "title": "Automated Location Tracking", - "props": [ - { - "name": "label", - "value": "CM-8(8)" - }, - { - "name": "sort-id", - "value": "cm-08.08" - } - ], - "parts": [ - { - "id": "cm-8.8_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to support tracking of information system components by geographic location." - }, - { - "id": "cm-8.8_gdn", - "name": "guidance", - "prose": "The use of automated mechanisms to track the location of information system components can increase the accuracy of component inventories. Such capability may also help organizations rapidly identify the location and responsible individuals of system components that have been compromised, breached, or are otherwise in need of mitigation actions." - }, - { - "id": "cm-8.8_obj", - "name": "objective", - "prose": "Determine if the organization employs automated mechanisms to support tracking of information system components by geographic location." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing information system component inventory\n\nconfiguration management plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system inventory records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with inventory management responsibilities for information system components\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing the information system component inventory\n\nautomated mechanisms supporting tracking of information system components by geographic location" - } - ] - } - ] - }, - { - "id": "cm-8.9", - "class": "SP800-53-enhancement", - "title": "Assignment of Components to Systems", - "params": [ - { - "id": "cm-8.9_prm_1", - "label": "organization-defined acquired information system components" - } - ], - "props": [ - { - "name": "label", - "value": "CM-8(9)" - }, - { - "name": "sort-id", - "value": "cm-08.09" - } - ], - "parts": [ - { - "id": "cm-8.9_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cm-8.9_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Assigns {{ insert: param, cm-8.9_prm_1 }} to an information system; and" - }, - { - "id": "cm-8.9_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Receives an acknowledgement from the information system owner of this assignment." - } - ] - }, - { - "id": "cm-8.9_gdn", - "name": "guidance", - "prose": "Organizations determine the criteria for or types of information system components (e.g., microprocessors, motherboards, software, programmable logic controllers, and network devices) that are subject to this control enhancement.", - "links": [ - { - "href": "#sa-4", - "rel": "related" - } - ] - }, - { - "id": "cm-8.9_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-8.9.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(9)(a)" - } - ], - "parts": [ - { - "id": "cm-8.9.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(9)(a)[1]" - } - ], - "prose": "defines acquired information system components to be assigned to an information system; and" - }, - { - "id": "cm-8.9.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(9)(a)[2]" - } - ], - "prose": "assigns organization-defined acquired information system components to an information system; and" - } - ], - "links": [ - { - "href": "#cm-8.9_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "cm-8.9.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-8(9)(b)" - } - ], - "prose": "receives an acknowledgement from the information system owner of the assignment.", - "links": [ - { - "href": "#cm-8.9_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing information system component inventory\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system design documentation\n\nacknowledgements of information system component assignments\n\ninformation system inventory records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with inventory management responsibilities for information system components\n\ninformation system owner\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for assigning components to systems\n\norganizational processes for acknowledging assignment of components to systems\n\nautomated mechanisms implementing assignment of acquired components to the information system\n\nautomated mechanisms implementing acknowledgment of assignment of acquired components to the information system" - } - ] - } - ] - } - ] - }, - { - "id": "cm-9", - "class": "SP800-53", - "title": "Configuration Management Plan", - "props": [ - { - "name": "label", - "value": "CM-9" - }, - { - "name": "sort-id", - "value": "cm-09" - } - ], - "links": [ - { - "href": "#080f8068-5e3e-435e-9790-d22ba4722693", - "rel": "reference" - } - ], - "parts": [ - { - "id": "cm-9_smt", - "name": "statement", - "prose": "The organization develops, documents, and implements a configuration management plan for the information system that:", - "parts": [ - { - "id": "cm-9_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Addresses roles, responsibilities, and configuration management processes and procedures;" - }, - { - "id": "cm-9_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Establishes a process for identifying configuration items throughout the system development life cycle and for managing the configuration of the configuration items;" - }, - { - "id": "cm-9_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Defines the configuration items for the information system and places the configuration items under configuration management; and" - }, - { - "id": "cm-9_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Protects the configuration management plan from unauthorized disclosure and modification." - } - ] - }, - { - "id": "cm-9_gdn", - "name": "guidance", - "prose": "Configuration management plans satisfy the requirements in configuration management policies while being tailored to individual information systems. Such plans define detailed processes and procedures for how configuration management is used to support system development life cycle activities at the information system level. Configuration management plans are typically developed during the development/acquisition phase of the system development life cycle. The plans describe how to move changes through change management processes, how to update configuration settings and baselines, how to maintain information system component inventories, how to control development, test, and operational environments, and how to develop, release, and update key documents. Organizations can employ templates to help ensure consistent and timely development and implementation of configuration management plans. Such templates can represent a master configuration management plan for the organization at large with subsets of the plan implemented on a system by system basis. Configuration management approval processes include designation of key management stakeholders responsible for reviewing and approving proposed changes to information systems, and personnel that conduct security impact analyses prior to the implementation of changes to the systems. Configuration items are the information system items (hardware, software, firmware, and documentation) to be configuration-managed. As information systems continue through the system development life cycle, new configuration items may be identified and some existing configuration items may no longer need to be under configuration control.", - "links": [ - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - } - ] - }, - { - "id": "cm-9_obj", - "name": "objective", - "prose": "Determine if the organization develops, documents, and implements a configuration management plan for the information system that:", - "parts": [ - { - "id": "cm-9.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-9(a)" - } - ], - "parts": [ - { - "id": "cm-9.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-9(a)[1]" - } - ], - "prose": "addresses roles;" - }, - { - "id": "cm-9.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-9(a)[2]" - } - ], - "prose": "addresses responsibilities;" - }, - { - "id": "cm-9.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-9(a)[3]" - } - ], - "prose": "addresses configuration management processes and procedures;" - } - ] - }, - { - "id": "cm-9.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-9(b)" - } - ], - "prose": "establishes a process for:", - "parts": [ - { - "id": "cm-9.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-9(b)[1]" - } - ], - "prose": "identifying configuration items throughout the SDLC;" - }, - { - "id": "cm-9.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-9(b)[2]" - } - ], - "prose": "managing the configuration of the configuration items;" - } - ] - }, - { - "id": "cm-9.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-9(c)" - } - ], - "parts": [ - { - "id": "cm-9.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-9(c)[1]" - } - ], - "prose": "defines the configuration items for the information system;" - }, - { - "id": "cm-9.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-9(c)[2]" - } - ], - "prose": "places the configuration items under configuration management;" - } - ] - }, - { - "id": "cm-9.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-9(d)" - } - ], - "prose": "protects the configuration management plan from unauthorized:", - "parts": [ - { - "id": "cm-9.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-9(d)[1]" - } - ], - "prose": "disclosure; and" - }, - { - "id": "cm-9.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-9(d)[2]" - } - ], - "prose": "modification." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing configuration management planning\n\nconfiguration management plan\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for developing the configuration management plan\n\norganizational personnel with responsibilities for implementing and managing processes defined in the configuration management plan\n\norganizational personnel with responsibilities for protecting the configuration management plan\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for developing and documenting the configuration management plan\n\norganizational processes for identifying and managing configuration items\n\norganizational processes for protecting the configuration management plan\n\nautomated mechanisms implementing the configuration management plan\n\nautomated mechanisms for managing configuration items\n\nautomated mechanisms for protecting the configuration management plan" - } - ] - } - ], - "controls": [ - { - "id": "cm-9.1", - "class": "SP800-53-enhancement", - "title": "Assignment of Responsibility", - "props": [ - { - "name": "label", - "value": "CM-9(1)" - }, - { - "name": "sort-id", - "value": "cm-09.01" - } - ], - "parts": [ - { - "id": "cm-9.1_smt", - "name": "statement", - "prose": "The organization assigns responsibility for developing the configuration management process to organizational personnel that are not directly involved in information system development." - }, - { - "id": "cm-9.1_gdn", - "name": "guidance", - "prose": "In the absence of dedicated configuration management teams assigned within organizations, system developers may be tasked to develop configuration management processes using personnel who are not directly involved in system development or integration. This separation of duties ensures that organizations establish and maintain a sufficient degree of independence between the information system development and integration processes and configuration management processes to facilitate quality control and more effective oversight." - }, - { - "id": "cm-9.1_obj", - "name": "objective", - "prose": "Determine if the organization assigns responsibility for developing the configuration management process to organizational personnel that are not directly involved in information system development." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing responsibilities for configuration management process development\n\nconfiguration management plan\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for configuration management process development\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "cm-10", - "class": "SP800-53", - "title": "Software Usage Restrictions", - "props": [ - { - "name": "label", - "value": "CM-10" - }, - { - "name": "sort-id", - "value": "cm-10" - } - ], - "parts": [ - { - "id": "cm-10_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cm-10_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Uses software and associated documentation in accordance with contract agreements and copyright laws;" - }, - { - "id": "cm-10_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Tracks the use of software and associated documentation protected by quantity licenses to control copying and distribution; and" - }, - { - "id": "cm-10_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Controls and documents the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work." - } - ] - }, - { - "id": "cm-10_gdn", - "name": "guidance", - "prose": "Software license tracking can be accomplished by manual methods (e.g., simple spreadsheets) or automated methods (e.g., specialized tracking applications) depending on organizational needs.", - "links": [ - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - } - ] - }, - { - "id": "cm-10_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-10.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-10(a)" - } - ], - "prose": "uses software and associated documentation in accordance with contract agreements and copyright laws;" - }, - { - "id": "cm-10.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-10(b)" - } - ], - "prose": "tracks the use of software and associated documentation protected by quantity licenses to control copying and distribution; and" - }, - { - "id": "cm-10.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-10(c)" - } - ], - "prose": "controls and documents the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing software usage restrictions\n\nconfiguration management plan\n\nsecurity plan\n\nsoftware contract agreements and copyright laws\n\nsite license documentation\n\nlist of software usage restrictions\n\nsoftware license tracking reports\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators\n\norganizational personnel operating, using, and/or maintaining the information system\n\norganizational personnel with software license management responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational process for tracking the use of software protected by quantity licenses\n\norganization process for controlling/documenting the use of peer-to-peer file sharing technology\n\nautomated mechanisms implementing software license tracking\n\nautomated mechanisms implementing and controlling the use of peer-to-peer files sharing technology" - } - ] - } - ], - "controls": [ - { - "id": "cm-10.1", - "class": "SP800-53-enhancement", - "title": "Open Source Software", - "params": [ - { - "id": "cm-10.1_prm_1", - "label": "organization-defined restrictions" - } - ], - "props": [ - { - "name": "label", - "value": "CM-10(1)" - }, - { - "name": "sort-id", - "value": "cm-10.01" - } - ], - "parts": [ - { - "id": "cm-10.1_smt", - "name": "statement", - "prose": "The organization establishes the following restrictions on the use of open source software: {{ insert: param, cm-10.1_prm_1 }}." - }, - { - "id": "cm-10.1_gdn", - "name": "guidance", - "prose": "Open source software refers to software that is available in source code form. Certain software rights normally reserved for copyright holders are routinely provided under software license agreements that permit individuals to study, change, and improve the software. From a security perspective, the major advantage of open source software is that it provides organizations with the ability to examine the source code. However, there are also various licensing issues associated with open source software including, for example, the constraints on derivative use of such software." - }, - { - "id": "cm-10.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-10.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-10(1)[1]" - } - ], - "prose": "defines restrictions on the use of open source software; and" - }, - { - "id": "cm-10.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-10(1)[2]" - } - ], - "prose": "establishes organization-defined restrictions on the use of open source software." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing restrictions on use of open source software\n\nconfiguration management plan\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for establishing and enforcing restrictions on use of open source software\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational process for restricting the use of open source software\n\nautomated mechanisms implementing restrictions on the use of open source software" - } - ] - } - ] - } - ] - }, - { - "id": "cm-11", - "class": "SP800-53", - "title": "User-installed Software", - "params": [ - { - "id": "cm-11_prm_1", - "label": "organization-defined policies" - }, - { - "id": "cm-11_prm_2", - "label": "organization-defined methods" - }, - { - "id": "cm-11_prm_3", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "CM-11" - }, - { - "name": "sort-id", - "value": "cm-11" - } - ], - "parts": [ - { - "id": "cm-11_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cm-11_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Establishes {{ insert: param, cm-11_prm_1 }} governing the installation of software by users;" - }, - { - "id": "cm-11_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Enforces software installation policies through {{ insert: param, cm-11_prm_2 }}; and" - }, - { - "id": "cm-11_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Monitors policy compliance at {{ insert: param, cm-11_prm_3 }}." - } - ] - }, - { - "id": "cm-11_gdn", - "name": "guidance", - "prose": "If provided the necessary privileges, users have the ability to install software in organizational information systems. To maintain control over the types of software installed, organizations identify permitted and prohibited actions regarding software installation. Permitted software installations may include, for example, updates and security patches to existing software and downloading applications from organization-approved “app stores” Prohibited software installations may include, for example, software with unknown or suspect pedigrees or software that organizations consider potentially malicious. The policies organizations select governing user-installed software may be organization-developed or provided by some external entity. Policy enforcement methods include procedural methods (e.g., periodic examination of user accounts), automated methods (e.g., configuration settings implemented on organizational information systems), or both.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - } - ] - }, - { - "id": "cm-11_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cm-11.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-11(a)" - } - ], - "parts": [ - { - "id": "cm-11.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-11(a)[1]" - } - ], - "prose": "defines policies to govern the installation of software by users;" - }, - { - "id": "cm-11.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-11(a)[2]" - } - ], - "prose": "establishes organization-defined policies governing the installation of software by users;" - } - ] - }, - { - "id": "cm-11.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-11(b)" - } - ], - "parts": [ - { - "id": "cm-11.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-11(b)[1]" - } - ], - "prose": "defines methods to enforce software installation policies;" - }, - { - "id": "cm-11.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-11(b)[2]" - } - ], - "prose": "enforces software installation policies through organization-defined methods;" - } - ] - }, - { - "id": "cm-11.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-11(c)" - } - ], - "parts": [ - { - "id": "cm-11.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-11(c)[1]" - } - ], - "prose": "defines frequency to monitor policy compliance; and" - }, - { - "id": "cm-11.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-11(c)[2]" - } - ], - "prose": "monitors policy compliance at organization-defined frequency." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing user installed software\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of rules governing user installed software\n\ninformation system monitoring records\n\ninformation system audit records\n\nother relevant documents or records\n\ncontinuous monitoring strategy" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for governing user-installed software\n\norganizational personnel operating, using, and/or maintaining the information system\n\norganizational personnel monitoring compliance with user-installed software policy\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes governing user-installed software on the information system\n\nautomated mechanisms enforcing rules/methods for governing the installation of software by users\n\nautomated mechanisms monitoring policy compliance" - } - ] - } - ], - "controls": [ - { - "id": "cm-11.1", - "class": "SP800-53-enhancement", - "title": "Alerts for Unauthorized Installations", - "params": [ - { - "id": "cm-11.1_prm_1", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "CM-11(1)" - }, - { - "name": "sort-id", - "value": "cm-11.01" - } - ], - "parts": [ - { - "id": "cm-11.1_smt", - "name": "statement", - "prose": "The information system alerts {{ insert: param, cm-11.1_prm_1 }} when the unauthorized installation of software is detected." - }, - { - "id": "cm-11.1_gdn", - "name": "guidance", - "links": [ - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "cm-11.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "cm-11.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-11(1)[1]" - } - ], - "prose": "the organization defines personnel or roles to be alerted when the unauthorized installation of software is detected; and" - }, - { - "id": "cm-11.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CM-11(1)[2]" - } - ], - "prose": "the information system alerts organization-defined personnel or roles when the unauthorized installation of software is detected." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing user installed software\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for governing user-installed software\n\norganizational personnel operating, using, and/or maintaining the information system\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes governing user-installed software on the information system\n\nautomated mechanisms for alerting personnel/roles when unauthorized installation of software is detected" - } - ] - } - ] - }, - { - "id": "cm-11.2", - "class": "SP800-53-enhancement", - "title": "Prohibit Installation Without Privileged Status", - "props": [ - { - "name": "label", - "value": "CM-11(2)" - }, - { - "name": "sort-id", - "value": "cm-11.02" - } - ], - "parts": [ - { - "id": "cm-11.2_smt", - "name": "statement", - "prose": "The information system prohibits user installation of software without explicit privileged status." - }, - { - "id": "cm-11.2_gdn", - "name": "guidance", - "prose": "Privileged status can be obtained, for example, by serving in the role of system administrator.", - "links": [ - { - "href": "#ac-6", - "rel": "related" - } - ] - }, - { - "id": "cm-11.2_obj", - "name": "objective", - "prose": "Determine if the information system prohibits user installation of software without explicit privileged status." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Configuration management policy\n\nprocedures addressing user installed software\n\nconfiguration management plan\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nalerts/notifications of unauthorized software installations\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for governing user-installed software\n\norganizational personnel operating, using, and/or maintaining the information system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes governing user-installed software on the information system\n\nautomated mechanisms for prohibiting installation of software without privileged status (e.g., access controls)" - } - ] - } - ] - } - ] - } - ] - }, - { - "id": "cp", - "class": "family", - "title": "Contingency Planning", - "controls": [ - { - "id": "cp-1", - "class": "SP800-53", - "title": "Contingency Planning Policy and Procedures", - "params": [ - { - "id": "cp-1_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "cp-1_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "cp-1_prm_3", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "CP-1" - }, - { - "name": "sort-id", - "value": "cp-01" - } - ], - "links": [ - { - "href": "#023104bc-6f75-4cd5-b7d0-fc92326f8007", - "rel": "reference" - }, - { - "href": "#5c201b63-0768-417b-ac22-3f014e3941b2", - "rel": "reference" - }, - { - "href": "#748a81b9-9cad-463f-abde-8b368167e70d", - "rel": "reference" - }, - { - "href": "#9cb3d8fe-2127-48ba-821e-cdd2d7aee921", - "rel": "reference" - } - ], - "parts": [ - { - "id": "cp-1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cp-1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops, documents, and disseminates to {{ insert: param, cp-1_prm_1 }}:", - "parts": [ - { - "id": "cp-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "A contingency planning policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "cp-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the contingency planning policy and associated contingency planning controls; and" - } - ] - }, - { - "id": "cp-1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the current:", - "parts": [ - { - "id": "cp-1_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Contingency planning policy {{ insert: param, cp-1_prm_2 }}; and" - }, - { - "id": "cp-1_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Contingency planning procedures {{ insert: param, cp-1_prm_3 }}." - } - ] - } - ] - }, - { - "id": "cp-1_gdn", - "name": "guidance", - "prose": "This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the CP family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures.", - "links": [ - { - "href": "#pm-9", - "rel": "related" - } - ] - }, - { - "id": "cp-1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "cp-1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(a)" - } - ], - "parts": [ - { - "id": "cp-1.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(a)(1)" - } - ], - "parts": [ - { - "id": "cp-1.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(a)(1)[1]" - } - ], - "prose": "the organization develops and documents a contingency planning policy that addresses:", - "parts": [ - { - "id": "cp-1.a.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(a)(1)[1][a]" - } - ], - "prose": "purpose;" - }, - { - "id": "cp-1.a.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(a)(1)[1][b]" - } - ], - "prose": "scope;" - }, - { - "id": "cp-1.a.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(a)(1)[1][c]" - } - ], - "prose": "roles;" - }, - { - "id": "cp-1.a.1_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(a)(1)[1][d]" - } - ], - "prose": "responsibilities;" - }, - { - "id": "cp-1.a.1_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(a)(1)[1][e]" - } - ], - "prose": "management commitment;" - }, - { - "id": "cp-1.a.1_obj.1.f", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(a)(1)[1][f]" - } - ], - "prose": "coordination among organizational entities;" - }, - { - "id": "cp-1.a.1_obj.1.g", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(a)(1)[1][g]" - } - ], - "prose": "compliance;" - } - ] - }, - { - "id": "cp-1.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(a)(1)[2]" - } - ], - "prose": "the organization defines personnel or roles to whom the contingency planning policy is to be disseminated;" - }, - { - "id": "cp-1.a.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(a)(1)[3]" - } - ], - "prose": "the organization disseminates the contingency planning policy to organization-defined personnel or roles;" - } - ] - }, - { - "id": "cp-1.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(a)(2)" - } - ], - "parts": [ - { - "id": "cp-1.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(a)(2)[1]" - } - ], - "prose": "the organization develops and documents procedures to facilitate the implementation of the contingency planning policy and associated contingency planning controls;" - }, - { - "id": "cp-1.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(a)(2)[2]" - } - ], - "prose": "the organization defines personnel or roles to whom the procedures are to be disseminated;" - }, - { - "id": "cp-1.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(a)(2)[3]" - } - ], - "prose": "the organization disseminates the procedures to organization-defined personnel or roles;" - } - ] - } - ] - }, - { - "id": "cp-1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(b)" - } - ], - "parts": [ - { - "id": "cp-1.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(b)(1)" - } - ], - "parts": [ - { - "id": "cp-1.b.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(b)(1)[1]" - } - ], - "prose": "the organization defines the frequency to review and update the current contingency planning policy;" - }, - { - "id": "cp-1.b.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(b)(1)[2]" - } - ], - "prose": "the organization reviews and updates the current contingency planning with the organization-defined frequency;" - } - ] - }, - { - "id": "cp-1.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(b)(2)" - } - ], - "parts": [ - { - "id": "cp-1.b.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(b)(2)[1]" - } - ], - "prose": "the organization defines the frequency to review and update the current contingency planning procedures; and" - }, - { - "id": "cp-1.b.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-1(b)(2)[2]" - } - ], - "prose": "the organization reviews and updates the current contingency planning procedures with the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy and procedures\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency planning responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "cp-2", - "class": "SP800-53", - "title": "Contingency Plan", - "params": [ - { - "id": "cp-2_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "cp-2_prm_2", - "label": "organization-defined key contingency personnel (identified by name and/or by role) and organizational elements" - }, - { - "id": "cp-2_prm_3", - "label": "organization-defined frequency" - }, - { - "id": "cp-2_prm_4", - "label": "organization-defined key contingency personnel (identified by name and/or by role) and organizational elements" - } - ], - "props": [ - { - "name": "label", - "value": "CP-2" - }, - { - "name": "sort-id", - "value": "cp-02" - } - ], - "links": [ - { - "href": "#023104bc-6f75-4cd5-b7d0-fc92326f8007", - "rel": "reference" - }, - { - "href": "#748a81b9-9cad-463f-abde-8b368167e70d", - "rel": "reference" - } - ], - "parts": [ - { - "id": "cp-2_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cp-2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops a contingency plan for the information system that:", - "parts": [ - { - "id": "cp-2_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Identifies essential missions and business functions and associated contingency requirements;" - }, - { - "id": "cp-2_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Provides recovery objectives, restoration priorities, and metrics;" - }, - { - "id": "cp-2_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Addresses contingency roles, responsibilities, assigned individuals with contact information;" - }, - { - "id": "cp-2_smt.a.4", - "name": "item", - "props": [ - { - "name": "label", - "value": "4." - } - ], - "prose": "Addresses maintaining essential missions and business functions despite an information system disruption, compromise, or failure;" - }, - { - "id": "cp-2_smt.a.5", - "name": "item", - "props": [ - { - "name": "label", - "value": "5." - } - ], - "prose": "Addresses eventual, full information system restoration without deterioration of the security safeguards originally planned and implemented; and" - }, - { - "id": "cp-2_smt.a.6", - "name": "item", - "props": [ - { - "name": "label", - "value": "6." - } - ], - "prose": "Is reviewed and approved by {{ insert: param, cp-2_prm_1 }};" - } - ] - }, - { - "id": "cp-2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Distributes copies of the contingency plan to {{ insert: param, cp-2_prm_2 }};" - }, - { - "id": "cp-2_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Coordinates contingency planning activities with incident handling activities;" - }, - { - "id": "cp-2_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Reviews the contingency plan for the information system {{ insert: param, cp-2_prm_3 }};" - }, - { - "id": "cp-2_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Updates the contingency plan to address changes to the organization, information system, or environment of operation and problems encountered during contingency plan implementation, execution, or testing;" - }, - { - "id": "cp-2_smt.f", - "name": "item", - "props": [ - { - "name": "label", - "value": "f." - } - ], - "prose": "Communicates contingency plan changes to {{ insert: param, cp-2_prm_4 }}; and" - }, - { - "id": "cp-2_smt.g", - "name": "item", - "props": [ - { - "name": "label", - "value": "g." - } - ], - "prose": "Protects the contingency plan from unauthorized disclosure and modification." - } - ] - }, - { - "id": "cp-2_gdn", - "name": "guidance", - "prose": "Contingency planning for information systems is part of an overall organizational program for achieving continuity of operations for mission/business functions. Contingency planning addresses both information system restoration and implementation of alternative mission/business processes when systems are compromised. The effectiveness of contingency planning is maximized by considering such planning throughout the phases of the system development life cycle. Performing contingency planning on hardware, software, and firmware development can be an effective means of achieving information system resiliency. Contingency plans reflect the degree of restoration required for organizational information systems since not all systems may need to fully recover to achieve the level of continuity of operations desired. Information system recovery objectives reflect applicable laws, Executive Orders, directives, policies, standards, regulations, and guidelines. In addition to information system availability, contingency plans also address other security-related events resulting in a reduction in mission and/or business effectiveness, such as malicious attacks compromising the confidentiality or integrity of information systems. Actions addressed in contingency plans include, for example, orderly/graceful degradation, information system shutdown, fallback to a manual mode, alternate information flows, and operating in modes reserved for when systems are under attack. By closely coordinating contingency planning with incident handling activities, organizations can ensure that the necessary contingency planning activities are in place and activated in the event of a security incident.", - "links": [ - { - "href": "#ac-14", - "rel": "related" - }, - { - "href": "#cp-6", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - }, - { - "href": "#cp-8", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#cp-10", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - }, - { - "href": "#pm-8", - "rel": "related" - }, - { - "href": "#pm-11", - "rel": "related" - } - ] - }, - { - "id": "cp-2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(a)" - } - ], - "prose": "develops and documents a contingency plan for the information system that:", - "parts": [ - { - "id": "cp-2.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(a)(1)" - } - ], - "prose": "identifies essential missions and business functions and associated contingency requirements;" - }, - { - "id": "cp-2.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(a)(2)" - } - ], - "parts": [ - { - "id": "cp-2.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(a)(2)[1]" - } - ], - "prose": "provides recovery objectives;" - }, - { - "id": "cp-2.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(a)(2)[2]" - } - ], - "prose": "provides restoration priorities;" - }, - { - "id": "cp-2.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(a)(2)[3]" - } - ], - "prose": "provides metrics;" - } - ] - }, - { - "id": "cp-2.a.3_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(a)(3)" - } - ], - "parts": [ - { - "id": "cp-2.a.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(a)(3)[1]" - } - ], - "prose": "addresses contingency roles;" - }, - { - "id": "cp-2.a.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(a)(3)[2]" - } - ], - "prose": "addresses contingency responsibilities;" - }, - { - "id": "cp-2.a.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(a)(3)[3]" - } - ], - "prose": "addresses assigned individuals with contact information;" - } - ] - }, - { - "id": "cp-2.a.4_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(a)(4)" - } - ], - "prose": "addresses maintaining essential missions and business functions despite an information system disruption, compromise, or failure;" - }, - { - "id": "cp-2.a.5_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(a)(5)" - } - ], - "prose": "addresses eventual, full information system restoration without deterioration of the security safeguards originally planned and implemented;" - }, - { - "id": "cp-2.a.6_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(a)(6)" - } - ], - "parts": [ - { - "id": "cp-2.a.6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(a)(6)[1]" - } - ], - "prose": "defines personnel or roles to review and approve the contingency plan for the information system;" - }, - { - "id": "cp-2.a.6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(a)(6)[2]" - } - ], - "prose": "is reviewed and approved by organization-defined personnel or roles;" - } - ] - } - ] - }, - { - "id": "cp-2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(b)" - } - ], - "parts": [ - { - "id": "cp-2.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(b)[1]" - } - ], - "prose": "defines key contingency personnel (identified by name and/or by role) and organizational elements to whom copies of the contingency plan are to be distributed;" - }, - { - "id": "cp-2.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(b)[2]" - } - ], - "prose": "distributes copies of the contingency plan to organization-defined key contingency personnel and organizational elements;" - } - ] - }, - { - "id": "cp-2.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(c)" - } - ], - "prose": "coordinates contingency planning activities with incident handling activities;" - }, - { - "id": "cp-2.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(d)" - } - ], - "parts": [ - { - "id": "cp-2.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(d)[1]" - } - ], - "prose": "defines a frequency to review the contingency plan for the information system;" - }, - { - "id": "cp-2.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(d)[2]" - } - ], - "prose": "reviews the contingency plan with the organization-defined frequency;" - } - ] - }, - { - "id": "cp-2.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(e)" - } - ], - "prose": "updates the contingency plan to address:", - "parts": [ - { - "id": "cp-2.e_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(e)[1]" - } - ], - "prose": "changes to the organization, information system, or environment of operation;" - }, - { - "id": "cp-2.e_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(e)[2]" - } - ], - "prose": "problems encountered during plan implementation, execution, and testing;" - } - ] - }, - { - "id": "cp-2.f_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(f)" - } - ], - "parts": [ - { - "id": "cp-2.f_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(f)[1]" - } - ], - "prose": "defines key contingency personnel (identified by name and/or by role) and organizational elements to whom contingency plan changes are to be communicated;" - }, - { - "id": "cp-2.f_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(f)[2]" - } - ], - "prose": "communicates contingency plan changes to organization-defined key contingency personnel and organizational elements; and" - } - ] - }, - { - "id": "cp-2.g_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(g)" - } - ], - "prose": "protects the contingency plan from unauthorized disclosure and modification." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency operations for the information system\n\ncontingency plan\n\nsecurity plan\n\nevidence of contingency plan reviews and updates\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\norganizational personnel with incident handling responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for contingency plan development, review, update, and protection\n\nautomated mechanisms for developing, reviewing, updating and/or protecting the contingency plan" - } - ] - } - ], - "controls": [ - { - "id": "cp-2.1", - "class": "SP800-53-enhancement", - "title": "Coordinate with Related Plans", - "props": [ - { - "name": "label", - "value": "CP-2(1)" - }, - { - "name": "sort-id", - "value": "cp-02.01" - } - ], - "parts": [ - { - "id": "cp-2.1_smt", - "name": "statement", - "prose": "The organization coordinates contingency plan development with organizational elements responsible for related plans." - }, - { - "id": "cp-2.1_gdn", - "name": "guidance", - "prose": "Plans related to contingency plans for organizational information systems include, for example, Business Continuity Plans, Disaster Recovery Plans, Continuity of Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, Cyber Incident Response Plans, Insider Threat Implementation Plan, and Occupant Emergency Plans." - }, - { - "id": "cp-2.1_obj", - "name": "objective", - "prose": "Determine if the organization coordinates contingency plan development with organizational elements responsible for related plans." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency operations for the information system\n\ncontingency plan\n\nbusiness contingency plans\n\ndisaster recovery plans\n\ncontinuity of operations plans\n\ncrisis communications plans\n\ncritical infrastructure plans\n\ncyber incident response plan\n\ninsider threat implementation plans\n\noccupant emergency plans\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\norganizational personnel with information security responsibilities\n\npersonnel with responsibility for related plans" - } - ] - } - ] - }, - { - "id": "cp-2.2", - "class": "SP800-53-enhancement", - "title": "Capacity Planning", - "props": [ - { - "name": "label", - "value": "CP-2(2)" - }, - { - "name": "sort-id", - "value": "cp-02.02" - } - ], - "parts": [ - { - "id": "cp-2.2_smt", - "name": "statement", - "prose": "The organization conducts capacity planning so that necessary capacity for information processing, telecommunications, and environmental support exists during contingency operations." - }, - { - "id": "cp-2.2_gdn", - "name": "guidance", - "prose": "Capacity planning is needed because different types of threats (e.g., natural disasters, targeted cyber attacks) can result in a reduction of the available processing, telecommunications, and support services originally intended to support the organizational missions/business functions. Organizations may need to anticipate degraded operations during contingency operations and factor such degradation into capacity planning." - }, - { - "id": "cp-2.2_obj", - "name": "objective", - "prose": "Determine if the organization conducts capacity planning so that necessary capacity exists during contingency operations for:", - "parts": [ - { - "id": "cp-2.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(2)[1]" - } - ], - "prose": "information processing;" - }, - { - "id": "cp-2.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(2)[2]" - } - ], - "prose": "telecommunications; and" - }, - { - "id": "cp-2.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(2)[3]" - } - ], - "prose": "environmental support." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency operations for the information system\n\ncontingency plan\n\ncapacity planning documents\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "cp-2.3", - "class": "SP800-53-enhancement", - "title": "Resume Essential Missions / Business Functions", - "params": [ - { - "id": "cp-2.3_prm_1", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "CP-2(3)" - }, - { - "name": "sort-id", - "value": "cp-02.03" - } - ], - "parts": [ - { - "id": "cp-2.3_smt", - "name": "statement", - "prose": "The organization plans for the resumption of essential missions and business functions within {{ insert: param, cp-2.3_prm_1 }} of contingency plan activation." - }, - { - "id": "cp-2.3_gdn", - "name": "guidance", - "prose": "Organizations may choose to carry out the contingency planning activities in this control enhancement as part of organizational business continuity planning including, for example, as part of business impact analyses. The time period for resumption of essential missions/business functions may be dependent on the severity/extent of disruptions to the information system and its supporting infrastructure.", - "links": [ - { - "href": "#pe-12", - "rel": "related" - } - ] - }, - { - "id": "cp-2.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-2.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(3)[1]" - } - ], - "prose": "defines the time period to plan for the resumption of essential missions and business functions as a result of contingency plan activation; and" - }, - { - "id": "cp-2.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(3)[2]" - } - ], - "prose": "plans for the resumption of essential missions and business functions within organization-defined time period of contingency plan activation." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency operations for the information system\n\ncontingency plan\n\nsecurity plan\n\nbusiness impact assessment\n\nother related plans\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for resumption of missions and business functions" - } - ] - } - ] - }, - { - "id": "cp-2.4", - "class": "SP800-53-enhancement", - "title": "Resume All Missions / Business Functions", - "params": [ - { - "id": "cp-2.4_prm_1", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "CP-2(4)" - }, - { - "name": "sort-id", - "value": "cp-02.04" - } - ], - "parts": [ - { - "id": "cp-2.4_smt", - "name": "statement", - "prose": "The organization plans for the resumption of all missions and business functions within {{ insert: param, cp-2.4_prm_1 }} of contingency plan activation." - }, - { - "id": "cp-2.4_gdn", - "name": "guidance", - "prose": "Organizations may choose to carry out the contingency planning activities in this control enhancement as part of organizational business continuity planning including, for example, as part of business impact analyses. The time period for resumption of all missions/business functions may be dependent on the severity/extent of disruptions to the information system and its supporting infrastructure.", - "links": [ - { - "href": "#pe-12", - "rel": "related" - } - ] - }, - { - "id": "cp-2.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-2.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(4)[1]" - } - ], - "prose": "defines the time period to plan for the resumption of all missions and business functions as a result of contingency plan activation; and" - }, - { - "id": "cp-2.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(4)[2]" - } - ], - "prose": "plans for the resumption of all missions and business functions within organization-defined time period of contingency plan activation." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency operations for the information system\n\ncontingency plan\n\nsecurity plan\n\nbusiness impact assessment\n\nother related plans\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for resumption of missions and business functions" - } - ] - } - ] - }, - { - "id": "cp-2.5", - "class": "SP800-53-enhancement", - "title": "Continue Essential Missions / Business Functions", - "props": [ - { - "name": "label", - "value": "CP-2(5)" - }, - { - "name": "sort-id", - "value": "cp-02.05" - } - ], - "parts": [ - { - "id": "cp-2.5_smt", - "name": "statement", - "prose": "The organization plans for the continuance of essential missions and business functions with little or no loss of operational continuity and sustains that continuity until full information system restoration at primary processing and/or storage sites." - }, - { - "id": "cp-2.5_gdn", - "name": "guidance", - "prose": "Organizations may choose to carry out the contingency planning activities in this control enhancement as part of organizational business continuity planning including, for example, as part of business impact analyses. Primary processing and/or storage sites defined by organizations as part of contingency planning may change depending on the circumstances associated with the contingency (e.g., backup sites may become primary sites).", - "links": [ - { - "href": "#pe-12", - "rel": "related" - } - ] - }, - { - "id": "cp-2.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-2.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(5)[1]" - } - ], - "prose": "plans for the continuance of essential missions and business functions with little or no loss of operational continuity; and" - }, - { - "id": "cp-2.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(5)[2]" - } - ], - "prose": "sustains that operational continuity until full information system restoration at primary processing and/or storage sites." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency operations for the information system\n\ncontingency plan\n\nbusiness impact assessment\n\nprimary processing site agreements\n\nprimary storage site agreements\n\nalternate processing site agreements\n\nalternate storage site agreements\n\ncontingency plan test documentation\n\ncontingency plan test results\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for continuing missions and business functions" - } - ] - } - ] - }, - { - "id": "cp-2.6", - "class": "SP800-53-enhancement", - "title": "Alternate Processing / Storage Site", - "props": [ - { - "name": "label", - "value": "CP-2(6)" - }, - { - "name": "sort-id", - "value": "cp-02.06" - } - ], - "parts": [ - { - "id": "cp-2.6_smt", - "name": "statement", - "prose": "The organization plans for the transfer of essential missions and business functions to alternate processing and/or storage sites with little or no loss of operational continuity and sustains that continuity through information system restoration to primary processing and/or storage sites." - }, - { - "id": "cp-2.6_gdn", - "name": "guidance", - "prose": "Organizations may choose to carry out the contingency planning activities in this control enhancement as part of organizational business continuity planning including, for example, as part of business impact analyses. Primary processing and/or storage sites defined by organizations as part of contingency planning may change depending on the circumstances associated with the contingency (e.g., backup sites may become primary sites).", - "links": [ - { - "href": "#pe-12", - "rel": "related" - } - ] - }, - { - "id": "cp-2.6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-2.6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(6)[1]" - } - ], - "prose": "plans for the transfer of essential missions and business functions to alternate processing and/or storage sites with little or no loss of operational continuity; and" - }, - { - "id": "cp-2.6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-2(6)[2]" - } - ], - "prose": "sustains that operational continuity through information system restoration to primary processing and/or storage sites." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency operations for the information system\n\ncontingency plan\n\nbusiness impact assessment\n\nalternate processing site agreements\n\nalternate storage site agreements\n\ncontingency plan testing documentation\n\ncontingency plan test results\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for transfer of essential missions and business functions to alternate processing/storage sites" - } - ] - } - ] - }, - { - "id": "cp-2.7", - "class": "SP800-53-enhancement", - "title": "Coordinate with External Service Providers", - "props": [ - { - "name": "label", - "value": "CP-2(7)" - }, - { - "name": "sort-id", - "value": "cp-02.07" - } - ], - "parts": [ - { - "id": "cp-2.7_smt", - "name": "statement", - "prose": "The organization coordinates its contingency plan with the contingency plans of external service providers to ensure that contingency requirements can be satisfied." - }, - { - "id": "cp-2.7_gdn", - "name": "guidance", - "prose": "When the capability of an organization to successfully carry out its core missions/business functions is dependent on external service providers, developing a timely and comprehensive contingency plan may become more challenging. In this situation, organizations coordinate contingency planning activities with the external entities to ensure that the individual plans reflect the overall contingency needs of the organization.", - "links": [ - { - "href": "#sa-9", - "rel": "related" - } - ] - }, - { - "id": "cp-2.7_obj", - "name": "objective", - "prose": "Determine if the organization coordinates its contingency plan with the contingency plans of external service provides to ensure contingency requirements can be satisfied." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency operations for the information system\n\ncontingency plan\n\ncontingency plans of external\n\nservice providers\n\nservice level agreements\n\nsecurity plan\n\ncontingency plan requirements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\nexternal service providers\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "cp-2.8", - "class": "SP800-53-enhancement", - "title": "Identify Critical Assets", - "props": [ - { - "name": "label", - "value": "CP-2(8)" - }, - { - "name": "sort-id", - "value": "cp-02.08" - } - ], - "parts": [ - { - "id": "cp-2.8_smt", - "name": "statement", - "prose": "The organization identifies critical information system assets supporting essential missions and business functions." - }, - { - "id": "cp-2.8_gdn", - "name": "guidance", - "prose": "Organizations may choose to carry out the contingency planning activities in this control enhancement as part of organizational business continuity planning including, for example, as part of business impact analyses. Organizations identify critical information system assets so that additional safeguards and countermeasures can be employed (above and beyond those safeguards and countermeasures routinely implemented) to help ensure that organizational missions/business functions can continue to be conducted during contingency operations. In addition, the identification of critical information assets facilitates the prioritization of organizational resources. Critical information system assets include technical and operational aspects. Technical aspects include, for example, information technology services, information system components, information technology products, and mechanisms. Operational aspects include, for example, procedures (manually executed operations) and personnel (individuals operating technical safeguards and/or executing manual procedures). Organizational program protection plans can provide assistance in identifying critical assets.", - "links": [ - { - "href": "#sa-14", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - } - ] - }, - { - "id": "cp-2.8_obj", - "name": "objective", - "prose": "Determine if the organization identifies critical information system assets supporting essential missions and business functions." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency operations for the information system\n\ncontingency plan\n\nbusiness impact assessment\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "cp-3", - "class": "SP800-53", - "title": "Contingency Training", - "params": [ - { - "id": "cp-3_prm_1", - "label": "organization-defined time period" - }, - { - "id": "cp-3_prm_2", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "CP-3" - }, - { - "name": "sort-id", - "value": "cp-03" - } - ], - "links": [ - { - "href": "#023104bc-6f75-4cd5-b7d0-fc92326f8007", - "rel": "reference" - }, - { - "href": "#825438c3-248d-4e30-a51e-246473ce6ada", - "rel": "reference" - }, - { - "href": "#e12b5738-de74-4fb3-8317-a3995a8a1898", - "rel": "reference" - } - ], - "parts": [ - { - "id": "cp-3_smt", - "name": "statement", - "prose": "The organization provides contingency training to information system users consistent with assigned roles and responsibilities:", - "parts": [ - { - "id": "cp-3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Within {{ insert: param, cp-3_prm_1 }} of assuming a contingency role or responsibility;" - }, - { - "id": "cp-3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "When required by information system changes; and" - }, - { - "id": "cp-3_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": " {{ insert: param, cp-3_prm_2 }} thereafter." - } - ] - }, - { - "id": "cp-3_gdn", - "name": "guidance", - "prose": "Contingency training provided by organizations is linked to the assigned roles and responsibilities of organizational personnel to ensure that the appropriate content and level of detail is included in such training. For example, regular users may only need to know when and where to report for duty during contingency operations and if normal duties are affected; system administrators may require additional training on how to set up information systems at alternate processing and storage sites; and managers/senior leaders may receive more specific training on how to conduct mission-essential functions in designated off-site locations and how to establish communications with other governmental entities for purposes of coordination on contingency-related activities. Training for contingency roles/responsibilities reflects the specific continuity requirements in the contingency plan.", - "links": [ - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#ir-2", - "rel": "related" - } - ] - }, - { - "id": "cp-3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-3(a)" - } - ], - "parts": [ - { - "id": "cp-3.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-3(a)[1]" - } - ], - "prose": "defines a time period within which contingency training is to be provided to information system users assuming a contingency role or responsibility;" - }, - { - "id": "cp-3.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-3(a)[2]" - } - ], - "prose": "provides contingency training to information system users consistent with assigned roles and responsibilities within the organization-defined time period of assuming a contingency role or responsibility;" - } - ] - }, - { - "id": "cp-3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-3(b)" - } - ], - "prose": "provides contingency training to information system users consistent with assigned roles and responsibilities when required by information system changes;" - }, - { - "id": "cp-3.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-3(c)" - } - ], - "parts": [ - { - "id": "cp-3.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-3(c)[1]" - } - ], - "prose": "defines the frequency for contingency training thereafter; and" - }, - { - "id": "cp-3.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-3(c)[2]" - } - ], - "prose": "provides contingency training to information system users consistent with assigned roles and responsibilities with the organization-defined frequency thereafter." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency training\n\ncontingency plan\n\ncontingency training curriculum\n\ncontingency training material\n\nsecurity plan\n\ncontingency training records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency planning, plan implementation, and training responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for contingency training" - } - ] - } - ], - "controls": [ - { - "id": "cp-3.1", - "class": "SP800-53-enhancement", - "title": "Simulated Events", - "props": [ - { - "name": "label", - "value": "CP-3(1)" - }, - { - "name": "sort-id", - "value": "cp-03.01" - } - ], - "parts": [ - { - "id": "cp-3.1_smt", - "name": "statement", - "prose": "The organization incorporates simulated events into contingency training to facilitate effective response by personnel in crisis situations." - }, - { - "id": "cp-3.1_obj", - "name": "objective", - "prose": "Determine if the organization incorporates simulated events into contingency training to facilitate effective response by personnel in crisis situations." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency training\n\ncontingency plan\n\ncontingency training curriculum\n\ncontingency training material\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency planning, plan implementation, and training responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for contingency training\n\nautomated mechanisms for simulating contingency events" - } - ] - } - ] - }, - { - "id": "cp-3.2", - "class": "SP800-53-enhancement", - "title": "Automated Training Environments", - "props": [ - { - "name": "label", - "value": "CP-3(2)" - }, - { - "name": "sort-id", - "value": "cp-03.02" - } - ], - "parts": [ - { - "id": "cp-3.2_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to provide a more thorough and realistic contingency training environment." - }, - { - "id": "cp-3.2_obj", - "name": "objective", - "prose": "Determine if the organization employs automated mechanisms to provide a more thorough and realistic contingency training environment." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency training\n\ncontingency plan\n\ncontingency training curriculum\n\ncontingency training material\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency planning, plan implementation, and training responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for contingency training\n\nautomated mechanisms for providing contingency training environments" - } - ] - } - ] - } - ] - }, - { - "id": "cp-4", - "class": "SP800-53", - "title": "Contingency Plan Testing", - "params": [ - { - "id": "cp-4_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "cp-4_prm_2", - "label": "organization-defined tests" - } - ], - "props": [ - { - "name": "label", - "value": "CP-4" - }, - { - "name": "sort-id", - "value": "cp-04" - } - ], - "links": [ - { - "href": "#023104bc-6f75-4cd5-b7d0-fc92326f8007", - "rel": "reference" - }, - { - "href": "#e85cdb3f-7f0a-4083-8639-f13f70d3760b", - "rel": "reference" - }, - { - "href": "#748a81b9-9cad-463f-abde-8b368167e70d", - "rel": "reference" - }, - { - "href": "#0243a05a-e8a3-4d51-9364-4a9d20b0dcdf", - "rel": "reference" - } - ], - "parts": [ - { - "id": "cp-4_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cp-4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Tests the contingency plan for the information system {{ insert: param, cp-4_prm_1 }} using {{ insert: param, cp-4_prm_2 }} to determine the effectiveness of the plan and the organizational readiness to execute the plan;" - }, - { - "id": "cp-4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews the contingency plan test results; and" - }, - { - "id": "cp-4_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Initiates corrective actions, if needed." - } - ] - }, - { - "id": "cp-4_gdn", - "name": "guidance", - "prose": "Methods for testing contingency plans to determine the effectiveness of the plans and to identify potential weaknesses in the plans include, for example, walk-through and tabletop exercises, checklists, simulations (parallel, full interrupt), and comprehensive exercises. Organizations conduct testing based on the continuity requirements in contingency plans and include a determination of the effects on organizational operations, assets, and individuals arising due to contingency operations. Organizations have flexibility and discretion in the breadth, depth, and timelines of corrective actions.", - "links": [ - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-3", - "rel": "related" - }, - { - "href": "#ir-3", - "rel": "related" - } - ] - }, - { - "id": "cp-4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-4(a)" - } - ], - "parts": [ - { - "id": "cp-4.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-4(a)[1]" - } - ], - "prose": "defines tests to determine the effectiveness of the contingency plan and the organizational readiness to execute the plan;" - }, - { - "id": "cp-4.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-4(a)[2]" - } - ], - "prose": "defines a frequency to test the contingency plan for the information system;" - }, - { - "id": "cp-4.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-4(a)[3]" - } - ], - "prose": "tests the contingency plan for the information system with the organization-defined frequency, using organization-defined tests to determine the effectiveness of the plan and the organizational readiness to execute the plan;" - } - ] - }, - { - "id": "cp-4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-4(b)" - } - ], - "prose": "reviews the contingency plan test results; and" - }, - { - "id": "cp-4.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-4(c)" - } - ], - "prose": "initiates corrective actions, if needed." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency plan testing\n\ncontingency plan\n\nsecurity plan\n\ncontingency plan test documentation\n\ncontingency plan test results\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for contingency plan testing, reviewing or responding to contingency plan tests\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for contingency plan testing\n\nautomated mechanisms supporting the contingency plan and/or contingency plan testing" - } - ] - } - ], - "controls": [ - { - "id": "cp-4.1", - "class": "SP800-53-enhancement", - "title": "Coordinate with Related Plans", - "props": [ - { - "name": "label", - "value": "CP-4(1)" - }, - { - "name": "sort-id", - "value": "cp-04.01" - } - ], - "parts": [ - { - "id": "cp-4.1_smt", - "name": "statement", - "prose": "The organization coordinates contingency plan testing with organizational elements responsible for related plans." - }, - { - "id": "cp-4.1_gdn", - "name": "guidance", - "prose": "Plans related to contingency plans for organizational information systems include, for example, Business Continuity Plans, Disaster Recovery Plans, Continuity of Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, Cyber Incident Response Plans, and Occupant Emergency Plans. This control enhancement does not require organizations to create organizational elements to handle related plans or to align such elements with specific plans. It does require, however, that if such organizational elements are responsible for related plans, organizations should coordinate with those elements.", - "links": [ - { - "href": "#ir-8", - "rel": "related" - }, - { - "href": "#pm-8", - "rel": "related" - } - ] - }, - { - "id": "cp-4.1_obj", - "name": "objective", - "prose": "Determine if the organization coordinates contingency plan testing with organizational elements responsible for related plans." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nincident response policy\n\nprocedures addressing contingency plan testing\n\ncontingency plan testing documentation\n\ncontingency plan\n\nbusiness continuity plans\n\ndisaster recovery plans\n\ncontinuity of operations plans\n\ncrisis communications plans\n\ncritical infrastructure plans\n\ncyber incident response plans\n\noccupant emergency plans\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency plan testing responsibilities\n\norganizational personnel\n\npersonnel with responsibilities for related plans\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "cp-4.2", - "class": "SP800-53-enhancement", - "title": "Alternate Processing Site", - "props": [ - { - "name": "label", - "value": "CP-4(2)" - }, - { - "name": "sort-id", - "value": "cp-04.02" - } - ], - "parts": [ - { - "id": "cp-4.2_smt", - "name": "statement", - "prose": "The organization tests the contingency plan at the alternate processing site:", - "parts": [ - { - "id": "cp-4.2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "To familiarize contingency personnel with the facility and available resources; and" - }, - { - "id": "cp-4.2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "To evaluate the capabilities of the alternate processing site to support contingency operations." - } - ] - }, - { - "id": "cp-4.2_gdn", - "name": "guidance", - "links": [ - { - "href": "#cp-7", - "rel": "related" - } - ] - }, - { - "id": "cp-4.2_obj", - "name": "objective", - "prose": "Determine if the organization tests the contingency plan at the alternate processing site to:", - "parts": [ - { - "id": "cp-4.2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-4(2)(a)" - } - ], - "prose": "familiarize contingency personnel with the facility and available resources; and", - "links": [ - { - "href": "#cp-4.2_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "cp-4.2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-4(2)(b)" - } - ], - "prose": "evaluate the capabilities of the alternate processing site to support contingency operations.", - "links": [ - { - "href": "#cp-4.2_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency plan testing\n\ncontingency plan\n\ncontingency plan test documentation\n\ncontingency plan test results\n\nalternate processing site agreements\n\nservice-level agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for contingency plan testing\n\nautomated mechanisms supporting the contingency plan and/or contingency plan testing" - } - ] - } - ] - }, - { - "id": "cp-4.3", - "class": "SP800-53-enhancement", - "title": "Automated Testing", - "props": [ - { - "name": "label", - "value": "CP-4(3)" - }, - { - "name": "sort-id", - "value": "cp-04.03" - } - ], - "parts": [ - { - "id": "cp-4.3_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to more thoroughly and effectively test the contingency plan." - }, - { - "id": "cp-4.3_gdn", - "name": "guidance", - "prose": "Automated mechanisms provide more thorough and effective testing of contingency plans, for example: (i) by providing more complete coverage of contingency issues; (ii) by selecting more realistic test scenarios and environments; and (iii) by effectively stressing the information system and supported missions." - }, - { - "id": "cp-4.3_obj", - "name": "objective", - "prose": "Determine if the organization employs automated mechanisms to more thoroughly and effectively test the contingency plan." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency plan testing\n\ncontingency plan\n\nautomated mechanisms supporting contingency plan testing\n\ncontingency plan test documentation\n\ncontingency plan test results\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency plan testing responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for contingency plan testing\n\nautomated mechanisms supporting contingency plan testing" - } - ] - } - ] - }, - { - "id": "cp-4.4", - "class": "SP800-53-enhancement", - "title": "Full Recovery / Reconstitution", - "props": [ - { - "name": "label", - "value": "CP-4(4)" - }, - { - "name": "sort-id", - "value": "cp-04.04" - } - ], - "parts": [ - { - "id": "cp-4.4_smt", - "name": "statement", - "prose": "The organization includes a full recovery and reconstitution of the information system to a known state as part of contingency plan testing." - }, - { - "id": "cp-4.4_gdn", - "name": "guidance", - "links": [ - { - "href": "#cp-10", - "rel": "related" - }, - { - "href": "#sc-24", - "rel": "related" - } - ] - }, - { - "id": "cp-4.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-4.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-4(4)[1]" - } - ], - "prose": "includes a full recovery of the information system to a known state as part of contingency plan testing; and" - }, - { - "id": "cp-4.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-4(4)[2]" - } - ], - "prose": "includes a full reconstitution of the information system to a known state as part of contingency plan testing." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing information system recovery and reconstitution\n\ncontingency plan\n\ncontingency plan test documentation\n\ncontingency plan test results\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency plan testing responsibilities\n\norganizational personnel with information system recovery and reconstitution responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for contingency plan testing\n\nautomated mechanisms supporting contingency plan testing\n\nautomated mechanisms supporting recovery and reconstitution of the information system" - } - ] - } - ] - } - ] - }, - { - "id": "cp-5", - "class": "SP800-53", - "title": "Contingency Plan Update", - "props": [ - { - "name": "label", - "value": "CP-5" - }, - { - "name": "sort-id", - "value": "cp-05" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#cp-2", - "rel": "incorporated-into" - } - ] - }, - { - "id": "cp-6", - "class": "SP800-53", - "title": "Alternate Storage Site", - "props": [ - { - "name": "label", - "value": "CP-6" - }, - { - "name": "sort-id", - "value": "cp-06" - } - ], - "links": [ - { - "href": "#748a81b9-9cad-463f-abde-8b368167e70d", - "rel": "reference" - } - ], - "parts": [ - { - "id": "cp-6_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cp-6_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Establishes an alternate storage site including necessary agreements to permit the storage and retrieval of information system backup information; and" - }, - { - "id": "cp-6_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Ensures that the alternate storage site provides information security safeguards equivalent to that of the primary site." - } - ] - }, - { - "id": "cp-6_gdn", - "name": "guidance", - "prose": "Alternate storage sites are sites that are geographically distinct from primary storage sites. An alternate storage site maintains duplicate copies of information and data in the event that the primary storage site is not available. Items covered by alternate storage site agreements include, for example, environmental conditions at alternate sites, access rules, physical and environmental protection requirements, and coordination of delivery/retrieval of backup media. Alternate storage sites reflect the requirements in contingency plans so that organizations can maintain essential missions/business functions despite disruption, compromise, or failure in organizational information systems.", - "links": [ - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#cp-10", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - } - ] - }, - { - "id": "cp-6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-6[1]" - } - ], - "prose": "establishes an alternate storage site including necessary agreements to permit the storage and retrieval of information system backup information; and" - }, - { - "id": "cp-6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-6[2]" - } - ], - "prose": "ensures that the alternate storage site provides information security safeguards equivalent to that of the primary site." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate storage sites\n\ncontingency plan\n\nalternate storage site agreements\n\nprimary storage site agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency plan alternate storage site responsibilities\n\norganizational personnel with information system recovery responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for storing and retrieving information system backup information at the alternate storage site\n\nautomated mechanisms supporting and/or implementing storage and retrieval of information system backup information at the alternate storage site" - } - ] - } - ], - "controls": [ - { - "id": "cp-6.1", - "class": "SP800-53-enhancement", - "title": "Separation from Primary Site", - "props": [ - { - "name": "label", - "value": "CP-6(1)" - }, - { - "name": "sort-id", - "value": "cp-06.01" - } - ], - "parts": [ - { - "id": "cp-6.1_smt", - "name": "statement", - "prose": "The organization identifies an alternate storage site that is separated from the primary storage site to reduce susceptibility to the same threats." - }, - { - "id": "cp-6.1_gdn", - "name": "guidance", - "prose": "Threats that affect alternate storage sites are typically defined in organizational assessments of risk and include, for example, natural disasters, structural failures, hostile cyber attacks, and errors of omission/commission. Organizations determine what is considered a sufficient degree of separation between primary and alternate storage sites based on the types of threats that are of concern. For one particular type of threat (i.e., hostile cyber attack), the degree of separation between sites is less relevant.", - "links": [ - { - "href": "#ra-3", - "rel": "related" - } - ] - }, - { - "id": "cp-6.1_obj", - "name": "objective", - "prose": "Determine if the organization identifies an alternate storage site that is separated from the primary storage site to reduce susceptibility to the same threats." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate storage sites\n\ncontingency plan\n\nalternate storage site\n\nalternate storage site agreements\n\nprimary storage site agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency plan alternate storage site responsibilities\n\norganizational personnel with information system recovery responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "cp-6.2", - "class": "SP800-53-enhancement", - "title": "Recovery Time / Point Objectives", - "props": [ - { - "name": "label", - "value": "CP-6(2)" - }, - { - "name": "sort-id", - "value": "cp-06.02" - } - ], - "parts": [ - { - "id": "cp-6.2_smt", - "name": "statement", - "prose": "The organization configures the alternate storage site to facilitate recovery operations in accordance with recovery time and recovery point objectives." - }, - { - "id": "cp-6.2_obj", - "name": "objective", - "prose": "Determine if the organization configures the alternate storage site to facilitate recovery operations in accordance with recovery time objectives and recovery point objectives (as specified in the information system contingency plan)." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate storage sites\n\ncontingency plan\n\nalternate storage site\n\nalternate storage site agreements\n\nalternate storage site configurations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency plan testing responsibilities\n\norganizational personnel with responsibilities for testing related plans\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for contingency plan testing\n\nautomated mechanisms supporting recovery time/point objectives" - } - ] - } - ] - }, - { - "id": "cp-6.3", - "class": "SP800-53-enhancement", - "title": "Accessibility", - "props": [ - { - "name": "label", - "value": "CP-6(3)" - }, - { - "name": "sort-id", - "value": "cp-06.03" - } - ], - "parts": [ - { - "id": "cp-6.3_smt", - "name": "statement", - "prose": "The organization identifies potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster and outlines explicit mitigation actions." - }, - { - "id": "cp-6.3_gdn", - "name": "guidance", - "prose": "Area-wide disruptions refer to those types of disruptions that are broad in geographic scope (e.g., hurricane, regional power outage) with such determinations made by organizations based on organizational assessments of risk. Explicit mitigation actions include, for example: (i) duplicating backup information at other alternate storage sites if access problems occur at originally designated alternate sites; or (ii) planning for physical access to retrieve backup information if electronic accessibility to the alternate site is disrupted.", - "links": [ - { - "href": "#ra-3", - "rel": "related" - } - ] - }, - { - "id": "cp-6.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-6.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-6(3)[1]" - } - ], - "prose": "identifies potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster; and" - }, - { - "id": "cp-6.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-6(3)[2]" - } - ], - "prose": "outlines explicit mitigation actions for such potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate storage sites\n\ncontingency plan\n\nalternate storage site\n\nlist of potential accessibility problems to alternate storage site\n\nmitigation actions for accessibility problems to alternate storage site\n\norganizational risk assessments\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency plan alternate storage site responsibilities\n\norganizational personnel with information system recovery responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "cp-7", - "class": "SP800-53", - "title": "Alternate Processing Site", - "params": [ - { - "id": "cp-7_prm_1", - "label": "organization-defined information system operations" - }, - { - "id": "cp-7_prm_2", - "label": "organization-defined time period consistent with recovery time and recovery point objectives" - } - ], - "props": [ - { - "name": "label", - "value": "CP-7" - }, - { - "name": "sort-id", - "value": "cp-07" - } - ], - "links": [ - { - "href": "#748a81b9-9cad-463f-abde-8b368167e70d", - "rel": "reference" - } - ], - "parts": [ - { - "id": "cp-7_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cp-7_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Establishes an alternate processing site including necessary agreements to permit the transfer and resumption of {{ insert: param, cp-7_prm_1 }} for essential missions/business functions within {{ insert: param, cp-7_prm_2 }} when the primary processing capabilities are unavailable;" - }, - { - "id": "cp-7_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Ensures that equipment and supplies required to transfer and resume operations are available at the alternate processing site or contracts are in place to support delivery to the site within the organization-defined time period for transfer/resumption; and" - }, - { - "id": "cp-7_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Ensures that the alternate processing site provides information security safeguards equivalent to those of the primary site." - } - ] - }, - { - "id": "cp-7_gdn", - "name": "guidance", - "prose": "Alternate processing sites are sites that are geographically distinct from primary processing sites. An alternate processing site provides processing capability in the event that the primary processing site is not available. Items covered by alternate processing site agreements include, for example, environmental conditions at alternate sites, access rules, physical and environmental protection requirements, and coordination for the transfer/assignment of personnel. Requirements are specifically allocated to alternate processing sites that reflect the requirements in contingency plans to maintain essential missions/business functions despite disruption, compromise, or failure in organizational information systems.", - "links": [ - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-6", - "rel": "related" - }, - { - "href": "#cp-8", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#cp-10", - "rel": "related" - }, - { - "href": "#ma-6", - "rel": "related" - } - ] - }, - { - "id": "cp-7_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-7.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-7(a)" - } - ], - "parts": [ - { - "id": "cp-7.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-7(a)[1]" - } - ], - "prose": "defines information system operations requiring an alternate processing site to be established to permit the transfer and resumption of such operations;" - }, - { - "id": "cp-7.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-7(a)[2]" - } - ], - "prose": "defines the time period consistent with recovery time objectives and recovery point objectives (as specified in the information system contingency plan) for transfer/resumption of organization-defined information system operations for essential missions/business functions;" - }, - { - "id": "cp-7.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-7(a)[3]" - } - ], - "prose": "establishes an alternate processing site including necessary agreements to permit the transfer and resumption of organization-defined information system operations for essential missions/business functions, within the organization-defined time period, when the primary processing capabilities are unavailable;" - } - ] - }, - { - "id": "cp-7.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-7(b)" - } - ], - "parts": [ - { - "id": "cp-7.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-7(b)[1]" - } - ], - "prose": "ensures that equipment and supplies required to transfer and resume operations are available at the alternate processing site; or" - }, - { - "id": "cp-7.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-7(b)[2]" - } - ], - "prose": "ensures that contracts are in place to support delivery to the site within the organization-defined time period for transfer/resumption; and" - } - ] - }, - { - "id": "cp-7.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-7(c)" - } - ], - "prose": "ensures that the alternate processing site provides information security safeguards equivalent to those of the primary site." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate processing sites\n\ncontingency plan\n\nalternate processing site agreements\n\nprimary processing site agreements\n\nspare equipment and supplies inventory at alternate processing site\n\nequipment and supply contracts\n\nservice-level agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for contingency planning and/or alternate site arrangements\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for recovery at the alternate site\n\nautomated mechanisms supporting and/or implementing recovery at the alternate processing site" - } - ] - } - ], - "controls": [ - { - "id": "cp-7.1", - "class": "SP800-53-enhancement", - "title": "Separation from Primary Site", - "props": [ - { - "name": "label", - "value": "CP-7(1)" - }, - { - "name": "sort-id", - "value": "cp-07.01" - } - ], - "parts": [ - { - "id": "cp-7.1_smt", - "name": "statement", - "prose": "The organization identifies an alternate processing site that is separated from the primary processing site to reduce susceptibility to the same threats." - }, - { - "id": "cp-7.1_gdn", - "name": "guidance", - "prose": "Threats that affect alternate processing sites are typically defined in organizational assessments of risk and include, for example, natural disasters, structural failures, hostile cyber attacks, and errors of omission/commission. Organizations determine what is considered a sufficient degree of separation between primary and alternate processing sites based on the types of threats that are of concern. For one particular type of threat (i.e., hostile cyber attack), the degree of separation between sites is less relevant.", - "links": [ - { - "href": "#ra-3", - "rel": "related" - } - ] - }, - { - "id": "cp-7.1_obj", - "name": "objective", - "prose": "Determine if the organization identifies an alternate processing site that is separated from the primary storage site to reduce susceptibility to the same threats." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate processing sites\n\ncontingency plan\n\nalternate processing site\n\nalternate processing site agreements\n\nprimary processing site agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency plan alternate processing site responsibilities\n\norganizational personnel with information system recovery responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "cp-7.2", - "class": "SP800-53-enhancement", - "title": "Accessibility", - "props": [ - { - "name": "label", - "value": "CP-7(2)" - }, - { - "name": "sort-id", - "value": "cp-07.02" - } - ], - "parts": [ - { - "id": "cp-7.2_smt", - "name": "statement", - "prose": "The organization identifies potential accessibility problems to the alternate processing site in the event of an area-wide disruption or disaster and outlines explicit mitigation actions." - }, - { - "id": "cp-7.2_gdn", - "name": "guidance", - "prose": "Area-wide disruptions refer to those types of disruptions that are broad in geographic scope (e.g., hurricane, regional power outage) with such determinations made by organizations based on organizational assessments of risk.", - "links": [ - { - "href": "#ra-3", - "rel": "related" - } - ] - }, - { - "id": "cp-7.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-7.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-7(2)[1]" - } - ], - "prose": "identifies potential accessibility problems to the alternate processing site in the event of an area-wide disruption or disaster; and" - }, - { - "id": "cp-7.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-7(2)[2]" - } - ], - "prose": "outlines explicit mitigation actions for such potential accessibility problems to the alternate processing site in the event of an area-wide disruption or disaster." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate processing sites\n\ncontingency plan\n\nalternate processing site\n\nalternate processing site agreements\n\nprimary processing site agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency plan alternate processing site responsibilities\n\norganizational personnel with information system recovery responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "cp-7.3", - "class": "SP800-53-enhancement", - "title": "Priority of Service", - "props": [ - { - "name": "label", - "value": "CP-7(3)" - }, - { - "name": "sort-id", - "value": "cp-07.03" - } - ], - "parts": [ - { - "id": "cp-7.3_smt", - "name": "statement", - "prose": "The organization develops alternate processing site agreements that contain priority-of-service provisions in accordance with organizational availability requirements (including recovery time objectives)." - }, - { - "id": "cp-7.3_gdn", - "name": "guidance", - "prose": "Priority-of-service agreements refer to negotiated agreements with service providers that ensure that organizations receive priority treatment consistent with their availability requirements and the availability of information resources at the alternate processing site." - }, - { - "id": "cp-7.3_obj", - "name": "objective", - "prose": "Determine if the organization develops alternate processing site agreements that contain priority-of-service provisions in accordance with organizational availability requirements (including recovery time objectives as specified in the information system contingency plan)." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate processing sites\n\ncontingency plan\n\nalternate processing site agreements\n\nservice-level agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency plan alternate processing site responsibilities\n\norganizational personnel with information system recovery responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for acquisitions/contractual agreements" - } - ] - } - ] - }, - { - "id": "cp-7.4", - "class": "SP800-53-enhancement", - "title": "Preparation for Use", - "props": [ - { - "name": "label", - "value": "CP-7(4)" - }, - { - "name": "sort-id", - "value": "cp-07.04" - } - ], - "parts": [ - { - "id": "cp-7.4_smt", - "name": "statement", - "prose": "The organization prepares the alternate processing site so that the site is ready to be used as the operational site supporting essential missions and business functions." - }, - { - "id": "cp-7.4_gdn", - "name": "guidance", - "prose": "Site preparation includes, for example, establishing configuration settings for information system components at the alternate processing site consistent with the requirements for such settings at the primary site and ensuring that essential supplies and other logistical considerations are in place.", - "links": [ - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - } - ] - }, - { - "id": "cp-7.4_obj", - "name": "objective", - "prose": "Determine if the organization prepares the alternate processing site so that the site is ready to be used as the operational site supporting essential missions and business functions." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate processing sites\n\ncontingency plan\n\nalternate processing site\n\nalternate processing site agreements\n\nalternate processing site configurations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency plan alternate processing site responsibilities\n\norganizational personnel with information system recovery responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing recovery at the alternate processing site" - } - ] - } - ] - }, - { - "id": "cp-7.5", - "class": "SP800-53-enhancement", - "title": "Equivalent Information Security Safeguards", - "props": [ - { - "name": "label", - "value": "CP-7(5)" - }, - { - "name": "sort-id", - "value": "cp-07.05" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#cp-7", - "rel": "incorporated-into" - } - ] - }, - { - "id": "cp-7.6", - "class": "SP800-53-enhancement", - "title": "Inability to Return to Primary Site", - "props": [ - { - "name": "label", - "value": "CP-7(6)" - }, - { - "name": "sort-id", - "value": "cp-07.06" - } - ], - "parts": [ - { - "id": "cp-7.6_smt", - "name": "statement", - "prose": "The organization plans and prepares for circumstances that preclude returning to the primary processing site." - }, - { - "id": "cp-7.6_obj", - "name": "objective", - "prose": "Determine if the organization plans and prepares for circumstances that preclude returning to the primary processing site." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate processing sites\n\ncontingency plan\n\nalternate processing site\n\nalternate processing site agreements\n\nalternate processing site configurations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system reconstitution responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "cp-8", - "class": "SP800-53", - "title": "Telecommunications Services", - "params": [ - { - "id": "cp-8_prm_1", - "label": "organization-defined information system operations" - }, - { - "id": "cp-8_prm_2", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "CP-8" - }, - { - "name": "sort-id", - "value": "cp-08" - } - ], - "links": [ - { - "href": "#748a81b9-9cad-463f-abde-8b368167e70d", - "rel": "reference" - }, - { - "href": "#fb5844de-ff96-47c0-b258-4f52bcc2f30d", - "rel": "reference" - }, - { - "href": "#3ac12e79-f54f-4a63-9f4b-ee4bcd4df604", - "rel": "reference" - } - ], - "parts": [ - { - "id": "cp-8_smt", - "name": "statement", - "prose": "The organization establishes alternate telecommunications services including necessary agreements to permit the resumption of {{ insert: param, cp-8_prm_1 }} for essential missions and business functions within {{ insert: param, cp-8_prm_2 }} when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites." - }, - { - "id": "cp-8_gdn", - "name": "guidance", - "prose": "This control applies to telecommunications services (data and voice) for primary and alternate processing and storage sites. Alternate telecommunications services reflect the continuity requirements in contingency plans to maintain essential missions/business functions despite the loss of primary telecommunications services. Organizations may specify different time periods for primary/alternate sites. Alternate telecommunications services include, for example, additional organizational or commercial ground-based circuits/lines or satellites in lieu of ground-based communications. Organizations consider factors such as availability, quality of service, and access when entering into alternate telecommunications agreements.", - "links": [ - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-6", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - } - ] - }, - { - "id": "cp-8_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-8[1]" - } - ], - "prose": "defines information system operations requiring alternate telecommunications services to be established to permit the resumption of such operations;" - }, - { - "id": "cp-8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-8[2]" - } - ], - "prose": "defines the time period to permit resumption of organization-defined information system operations for essential missions and business functions; and" - }, - { - "id": "cp-8_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-8[3]" - } - ], - "prose": "establishes alternate telecommunications services including necessary agreements to permit the resumption of organization-defined information system operations for essential missions and business functions, within the organization-defined time period, when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate telecommunications services\n\ncontingency plan\n\nprimary and alternate telecommunications service agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency plan telecommunications responsibilities\n\norganizational personnel with information system recovery responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for acquisitions/contractual agreements" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting telecommunications" - } - ] - } - ], - "controls": [ - { - "id": "cp-8.1", - "class": "SP800-53-enhancement", - "title": "Priority of Service Provisions", - "props": [ - { - "name": "label", - "value": "CP-8(1)" - }, - { - "name": "sort-id", - "value": "cp-08.01" - } - ], - "parts": [ - { - "id": "cp-8.1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cp-8.1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Develops primary and alternate telecommunications service agreements that contain priority-of-service provisions in accordance with organizational availability requirements (including recovery time objectives); and" - }, - { - "id": "cp-8.1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Requests Telecommunications Service Priority for all telecommunications services used for national security emergency preparedness in the event that the primary and/or alternate telecommunications services are provided by a common carrier." - } - ] - }, - { - "id": "cp-8.1_gdn", - "name": "guidance", - "prose": "Organizations consider the potential mission/business impact in situations where telecommunications service providers are servicing other organizations with similar priority-of-service provisions." - }, - { - "id": "cp-8.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-8.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-8(1)[1]" - } - ], - "prose": "develops primary and alternate telecommunications service agreements that contain priority-of-service provisions in accordance with organizational availability requirements (including recovery time objectives as specified in the information system contingency plan); and" - }, - { - "id": "cp-8.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-8(1)[2]" - } - ], - "prose": "requests Telecommunications Service Priority for all telecommunications services used for national security emergency preparedness in the event that the primary and/or alternate telecommunications services are provided by a common carrier." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing primary and alternate telecommunications services\n\ncontingency plan\n\nprimary and alternate telecommunications service agreements\n\nTelecommunications Service Priority documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency plan telecommunications responsibilities\n\norganizational personnel with information system recovery responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for acquisitions/contractual agreements" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting telecommunications" - } - ] - } - ] - }, - { - "id": "cp-8.2", - "class": "SP800-53-enhancement", - "title": "Single Points of Failure", - "props": [ - { - "name": "label", - "value": "CP-8(2)" - }, - { - "name": "sort-id", - "value": "cp-08.02" - } - ], - "parts": [ - { - "id": "cp-8.2_smt", - "name": "statement", - "prose": "The organization obtains alternate telecommunications services to reduce the likelihood of sharing a single point of failure with primary telecommunications services." - }, - { - "id": "cp-8.2_obj", - "name": "objective", - "prose": "Determine if the organization obtains alternate telecommunications services to reduce the likelihood of sharing a single point of failure with primary telecommunications services." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing primary and alternate telecommunications services\n\ncontingency plan\n\nprimary and alternate telecommunications service agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency plan telecommunications responsibilities\n\norganizational personnel with information system recovery responsibilities\n\nprimary and alternate telecommunications service providers\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "cp-8.3", - "class": "SP800-53-enhancement", - "title": "Separation of Primary / Alternate Providers", - "props": [ - { - "name": "label", - "value": "CP-8(3)" - }, - { - "name": "sort-id", - "value": "cp-08.03" - } - ], - "parts": [ - { - "id": "cp-8.3_smt", - "name": "statement", - "prose": "The organization obtains alternate telecommunications services from providers that are separated from primary service providers to reduce susceptibility to the same threats." - }, - { - "id": "cp-8.3_gdn", - "name": "guidance", - "prose": "Threats that affect telecommunications services are typically defined in organizational assessments of risk and include, for example, natural disasters, structural failures, hostile cyber/physical attacks, and errors of omission/commission. Organizations seek to reduce common susceptibilities by, for example, minimizing shared infrastructure among telecommunications service providers and achieving sufficient geographic separation between services. Organizations may consider using a single service provider in situations where the service provider can provide alternate telecommunications services meeting the separation needs addressed in the risk assessment." - }, - { - "id": "cp-8.3_obj", - "name": "objective", - "prose": "Determine if the organization obtains alternate telecommunications services from providers that are separated from primary service providers to reduce susceptibility to the same threats." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing primary and alternate telecommunications services\n\ncontingency plan\n\nprimary and alternate telecommunications service agreements\n\nalternate telecommunications service provider site\n\nprimary telecommunications service provider site\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency plan telecommunications responsibilities\n\norganizational personnel with information system recovery responsibilities\n\nprimary and alternate telecommunications service providers\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "cp-8.4", - "class": "SP800-53-enhancement", - "title": "Provider Contingency Plan", - "params": [ - { - "id": "cp-8.4_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "CP-8(4)" - }, - { - "name": "sort-id", - "value": "cp-08.04" - } - ], - "parts": [ - { - "id": "cp-8.4_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cp-8.4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Requires primary and alternate telecommunications service providers to have contingency plans;" - }, - { - "id": "cp-8.4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Reviews provider contingency plans to ensure that the plans meet organizational contingency requirements; and" - }, - { - "id": "cp-8.4_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Obtains evidence of contingency testing/training by providers {{ insert: param, cp-8.4_prm_1 }}." - } - ] - }, - { - "id": "cp-8.4_gdn", - "name": "guidance", - "prose": "Reviews of provider contingency plans consider the proprietary nature of such plans. In some situations, a summary of provider contingency plans may be sufficient evidence for organizations to satisfy the review requirement. Telecommunications service providers may also participate in ongoing disaster recovery exercises in coordination with the Department of Homeland Security, state, and local governments. Organizations may use these types of activities to satisfy evidentiary requirements related to service provider contingency plan reviews, testing, and training." - }, - { - "id": "cp-8.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-8.4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-8(4)(a)" - } - ], - "parts": [ - { - "id": "cp-8.4.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-8(4)(a)[1]" - } - ], - "prose": "requires primary telecommunications service provider to have contingency plans;" - }, - { - "id": "cp-8.4.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-8(4)(a)[2]" - } - ], - "prose": "requires alternate telecommunications service provider(s) to have contingency plans;" - } - ], - "links": [ - { - "href": "#cp-8.4_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "cp-8.4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-8(4)(b)" - } - ], - "prose": "reviews provider contingency plans to ensure that the plans meet organizational contingency requirements;", - "links": [ - { - "href": "#cp-8.4_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "cp-8.4.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-8(4)(c)" - } - ], - "parts": [ - { - "id": "cp-8.4.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-8(4)(c)[1]" - } - ], - "prose": "defines the frequency to obtain evidence of contingency testing/training by providers; and" - }, - { - "id": "cp-8.4.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-8(4)(c)[2]" - } - ], - "prose": "obtains evidence of contingency testing/training by providers with the organization-defined frequency." - } - ], - "links": [ - { - "href": "#cp-8.4_smt.c", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing primary and alternate telecommunications services\n\ncontingency plan\n\nprovider contingency plans\n\nevidence of contingency testing/training by providers\n\nprimary and alternate telecommunications service agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency planning, plan implementation, and testing responsibilities\n\nprimary and alternate telecommunications service providers\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for acquisitions/contractual agreements" - } - ] - } - ] - }, - { - "id": "cp-8.5", - "class": "SP800-53-enhancement", - "title": "Alternate Telecommunication Service Testing", - "params": [ - { - "id": "cp-8.5_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "CP-8(5)" - }, - { - "name": "sort-id", - "value": "cp-08.05" - } - ], - "parts": [ - { - "id": "cp-8.5_smt", - "name": "statement", - "prose": "The organization tests alternate telecommunication services {{ insert: param, cp-8.5_prm_1 }}." - }, - { - "id": "cp-8.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-8.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-8(5)[1]" - } - ], - "prose": "defines the frequency to test alternate telecommunication services; and" - }, - { - "id": "cp-8.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-8(5)[2]" - } - ], - "prose": "tests alternate telecommunication services with the organization-defined frequency." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate telecommunications services\n\ncontingency plan\n\nevidence of testing alternate telecommunications services\n\nalternate telecommunications service agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency planning, plan implementation, and testing responsibilities\n\nalternate telecommunications service providers\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting testing alternate telecommunications services" - } - ] - } - ] - } - ] - }, - { - "id": "cp-9", - "class": "SP800-53", - "title": "Information System Backup", - "params": [ - { - "id": "cp-9_prm_1", - "label": "organization-defined frequency consistent with recovery time and recovery point objectives" - }, - { - "id": "cp-9_prm_2", - "label": "organization-defined frequency consistent with recovery time and recovery point objectives" - }, - { - "id": "cp-9_prm_3", - "label": "organization-defined frequency consistent with recovery time and recovery point objectives" - } - ], - "props": [ - { - "name": "label", - "value": "CP-9" - }, - { - "name": "sort-id", - "value": "cp-09" - } - ], - "links": [ - { - "href": "#748a81b9-9cad-463f-abde-8b368167e70d", - "rel": "reference" - } - ], - "parts": [ - { - "id": "cp-9_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "cp-9_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Conducts backups of user-level information contained in the information system {{ insert: param, cp-9_prm_1 }};" - }, - { - "id": "cp-9_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Conducts backups of system-level information contained in the information system {{ insert: param, cp-9_prm_2 }};" - }, - { - "id": "cp-9_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Conducts backups of information system documentation including security-related documentation {{ insert: param, cp-9_prm_3 }}; and" - }, - { - "id": "cp-9_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Protects the confidentiality, integrity, and availability of backup information at storage locations." - } - ] - }, - { - "id": "cp-9_gdn", - "name": "guidance", - "prose": "System-level information includes, for example, system-state information, operating system and application software, and licenses. User-level information includes any information other than system-level information. Mechanisms employed by organizations to protect the integrity of information system backups include, for example, digital signatures and cryptographic hashes. Protection of system backup information while in transit is beyond the scope of this control. Information system backups reflect the requirements in contingency plans as well as other organizational requirements for backing up information.", - "links": [ - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-6", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "cp-9_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-9.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(a)" - } - ], - "parts": [ - { - "id": "cp-9.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(a)[1]" - } - ], - "prose": "defines a frequency, consistent with recovery time objectives and recovery point objectives as specified in the information system contingency plan, to conduct backups of user-level information contained in the information system;" - }, - { - "id": "cp-9.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(a)[2]" - } - ], - "prose": "conducts backups of user-level information contained in the information system with the organization-defined frequency;" - } - ] - }, - { - "id": "cp-9.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(b)" - } - ], - "parts": [ - { - "id": "cp-9.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(b)[1]" - } - ], - "prose": "defines a frequency, consistent with recovery time objectives and recovery point objectives as specified in the information system contingency plan, to conduct backups of system-level information contained in the information system;" - }, - { - "id": "cp-9.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(b)[2]" - } - ], - "prose": "conducts backups of system-level information contained in the information system with the organization-defined frequency;" - } - ] - }, - { - "id": "cp-9.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(c)" - } - ], - "parts": [ - { - "id": "cp-9.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(c)[1]" - } - ], - "prose": "defines a frequency, consistent with recovery time objectives and recovery point objectives as specified in the information system contingency plan, to conduct backups of information system documentation including security-related documentation;" - }, - { - "id": "cp-9.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(c)[2]" - } - ], - "prose": "conducts backups of information system documentation, including security-related documentation, with the organization-defined frequency; and" - } - ] - }, - { - "id": "cp-9.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(d)" - } - ], - "prose": "protects the confidentiality, integrity, and availability of backup information at storage locations." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing information system backup\n\ncontingency plan\n\nbackup storage location(s)\n\ninformation system backup logs or records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system backup responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for conducting information system backups\n\nautomated mechanisms supporting and/or implementing information system backups" - } - ] - } - ], - "controls": [ - { - "id": "cp-9.1", - "class": "SP800-53-enhancement", - "title": "Testing for Reliability / Integrity", - "params": [ - { - "id": "cp-9.1_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "CP-9(1)" - }, - { - "name": "sort-id", - "value": "cp-09.01" - } - ], - "parts": [ - { - "id": "cp-9.1_smt", - "name": "statement", - "prose": "The organization tests backup information {{ insert: param, cp-9.1_prm_1 }} to verify media reliability and information integrity." - }, - { - "id": "cp-9.1_gdn", - "name": "guidance", - "links": [ - { - "href": "#cp-4", - "rel": "related" - } - ] - }, - { - "id": "cp-9.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-9.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(1)[1]" - } - ], - "prose": "defines the frequency to test backup information to verify media reliability and information integrity; and" - }, - { - "id": "cp-9.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(1)[2]" - } - ], - "prose": "tests backup information with the organization-defined frequency to verify media reliability and information integrity." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing information system backup\n\ncontingency plan\n\ninformation system backup test results\n\ncontingency plan test documentation\n\ncontingency plan test results\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system backup responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for conducting information system backups\n\nautomated mechanisms supporting and/or implementing information system backups" - } - ] - } - ] - }, - { - "id": "cp-9.2", - "class": "SP800-53-enhancement", - "title": "Test Restoration Using Sampling", - "props": [ - { - "name": "label", - "value": "CP-9(2)" - }, - { - "name": "sort-id", - "value": "cp-09.02" - } - ], - "parts": [ - { - "id": "cp-9.2_smt", - "name": "statement", - "prose": "The organization uses a sample of backup information in the restoration of selected information system functions as part of contingency plan testing." - }, - { - "id": "cp-9.2_gdn", - "name": "guidance", - "links": [ - { - "href": "#cp-4", - "rel": "related" - } - ] - }, - { - "id": "cp-9.2_obj", - "name": "objective", - "prose": "Determine if the organization uses a sample of backup information in the restoration of selected information system functions as part of contingency plan testing." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing information system backup\n\ncontingency plan\n\ninformation system backup test results\n\ncontingency plan test documentation\n\ncontingency plan test results\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system backup responsibilities\n\norganizational personnel with contingency planning/contingency plan testing responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for conducting information system backups\n\nautomated mechanisms supporting and/or implementing information system backups" - } - ] - } - ] - }, - { - "id": "cp-9.3", - "class": "SP800-53-enhancement", - "title": "Separate Storage for Critical Information", - "params": [ - { - "id": "cp-9.3_prm_1", - "label": "organization-defined critical information system software and other security-related information" - } - ], - "props": [ - { - "name": "label", - "value": "CP-9(3)" - }, - { - "name": "sort-id", - "value": "cp-09.03" - } - ], - "parts": [ - { - "id": "cp-9.3_smt", - "name": "statement", - "prose": "The organization stores backup copies of {{ insert: param, cp-9.3_prm_1 }} in a separate facility or in a fire-rated container that is not collocated with the operational system." - }, - { - "id": "cp-9.3_gdn", - "name": "guidance", - "prose": "Critical information system software includes, for example, operating systems, cryptographic key management systems, and intrusion detection/prevention systems. Security-related information includes, for example, organizational inventories of hardware, software, and firmware components. Alternate storage sites typically serve as separate storage facilities for organizations.", - "links": [ - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - } - ] - }, - { - "id": "cp-9.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-9.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(3)[1]" - } - ], - "parts": [ - { - "id": "cp-9.3_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(3)[1][a]" - } - ], - "prose": "defines critical information system software and other security-related information requiring backup copies to be stored in a separate facility; or" - }, - { - "id": "cp-9.3_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(3)[1][b]" - } - ], - "prose": "defines critical information system software and other security-related information requiring backup copies to be stored in a fire-rated container that is not collocated with the operational system; and" - } - ] - }, - { - "id": "cp-9.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(3)[2]" - } - ], - "prose": "stores backup copies of organization-defined critical information system software and other security-related information in a separate facility or in a fire-rated container that is not collocated with the operational system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing information system backup\n\ncontingency plan\n\nbackup storage location(s)\n\ninformation system backup configurations and associated documentation\n\ninformation system backup logs or records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\norganizational personnel with information system backup responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "cp-9.4", - "class": "SP800-53-enhancement", - "title": "Protection from Unauthorized Modification", - "props": [ - { - "name": "label", - "value": "CP-9(4)" - }, - { - "name": "sort-id", - "value": "cp-09.04" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#cp-9", - "rel": "incorporated-into" - } - ] - }, - { - "id": "cp-9.5", - "class": "SP800-53-enhancement", - "title": "Transfer to Alternate Storage Site", - "params": [ - { - "id": "cp-9.5_prm_1", - "label": "organization-defined time period and transfer rate consistent with the recovery time and recovery point objectives" - } - ], - "props": [ - { - "name": "label", - "value": "CP-9(5)" - }, - { - "name": "sort-id", - "value": "cp-09.05" - } - ], - "parts": [ - { - "id": "cp-9.5_smt", - "name": "statement", - "prose": "The organization transfers information system backup information to the alternate storage site {{ insert: param, cp-9.5_prm_1 }}." - }, - { - "id": "cp-9.5_gdn", - "name": "guidance", - "prose": "Information system backup information can be transferred to alternate storage sites either electronically or by physical shipment of storage media." - }, - { - "id": "cp-9.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-9.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(5)[1]" - } - ], - "prose": "defines a time period, consistent with recovery time objectives and recovery point objectives as specified in the information system contingency plan, to transfer information system backup information to the alternate storage site;" - }, - { - "id": "cp-9.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(5)[2]" - } - ], - "prose": "defines a transfer rate, consistent with recovery time objectives and recovery point objectives as specified in the information system contingency plan, to transfer information system backup information to the alternate storage site; and" - }, - { - "id": "cp-9.5_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(5)[3]" - } - ], - "prose": "transfers information system backup information to the alternate storage site with the organization-defined time period and transfer rate." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing information system backup\n\ncontingency plan\n\ninformation system backup logs or records\n\nevidence of system backup information transferred to alternate storage site\n\nalternate storage site agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system backup responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for transferring information system backups to the alternate storage site\n\nautomated mechanisms supporting and/or implementing information system backups\n\nautomated mechanisms supporting and/or implementing information transfer to the alternate storage site" - } - ] - } - ] - }, - { - "id": "cp-9.6", - "class": "SP800-53-enhancement", - "title": "Redundant Secondary System", - "props": [ - { - "name": "label", - "value": "CP-9(6)" - }, - { - "name": "sort-id", - "value": "cp-09.06" - } - ], - "parts": [ - { - "id": "cp-9.6_smt", - "name": "statement", - "prose": "The organization accomplishes information system backup by maintaining a redundant secondary system that is not collocated with the primary system and that can be activated without loss of information or disruption to operations." - }, - { - "id": "cp-9.6_gdn", - "name": "guidance", - "links": [ - { - "href": "#cp-7", - "rel": "related" - }, - { - "href": "#cp-10", - "rel": "related" - } - ] - }, - { - "id": "cp-9.6_obj", - "name": "objective", - "prose": "Determine if the organization accomplishes information system backup by maintaining a redundant secondary system that:", - "parts": [ - { - "id": "cp-9.6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(6)[1]" - } - ], - "prose": "is not collocated with the primary system; and" - }, - { - "id": "cp-9.6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(6)[2]" - } - ], - "prose": "can be activated without loss of information or disruption to operations." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing information system backup\n\ncontingency plan\n\ninformation system backup test results\n\ncontingency plan test results\n\ncontingency plan test documentation\n\nredundant secondary system for information system backups\n\nlocation(s) of redundant secondary backup system(s)\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system backup responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for the redundant secondary system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for maintaining redundant secondary systems\n\nautomated mechanisms supporting and/or implementing information system backups\n\nautomated mechanisms supporting and/or implementing information transfer to a redundant secondary system" - } - ] - } - ] - }, - { - "id": "cp-9.7", - "class": "SP800-53-enhancement", - "title": "Dual Authorization", - "params": [ - { - "id": "cp-9.7_prm_1", - "label": "organization-defined backup information" - } - ], - "props": [ - { - "name": "label", - "value": "CP-9(7)" - }, - { - "name": "sort-id", - "value": "cp-09.07" - } - ], - "parts": [ - { - "id": "cp-9.7_smt", - "name": "statement", - "prose": "The organization enforces dual authorization for the deletion or destruction of {{ insert: param, cp-9.7_prm_1 }}." - }, - { - "id": "cp-9.7_gdn", - "name": "guidance", - "prose": "Dual authorization ensures that the deletion or destruction of backup information cannot occur unless two qualified individuals carry out the task. Individuals deleting/destroying backup information possess sufficient skills/expertise to determine if the proposed deletion/destruction of backup information reflects organizational policies and procedures. Dual authorization may also be known as two-person control.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - } - ] - }, - { - "id": "cp-9.7_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-9.7_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(7)[1]" - } - ], - "prose": "defines backup information that requires dual authorization to be enforced for the deletion or destruction of such information; and" - }, - { - "id": "cp-9.7_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-9(7)[2]" - } - ], - "prose": "enforces dual authorization for the deletion or destruction of organization-defined backup information." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing information system backup\n\ncontingency plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsystem generated list of dual authorization credentials or rules\n\nlogs or records of deletion or destruction of backup information\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system backup responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing dual authorization\n\nautomated mechanisms supporting and/or implementing deletion/destruction of backup information" - } - ] - } - ] - } - ] - }, - { - "id": "cp-10", - "class": "SP800-53", - "title": "Information System Recovery and Reconstitution", - "props": [ - { - "name": "label", - "value": "CP-10" - }, - { - "name": "sort-id", - "value": "cp-10" - } - ], - "links": [ - { - "href": "#023104bc-6f75-4cd5-b7d0-fc92326f8007", - "rel": "reference" - }, - { - "href": "#748a81b9-9cad-463f-abde-8b368167e70d", - "rel": "reference" - } - ], - "parts": [ - { - "id": "cp-10_smt", - "name": "statement", - "prose": "The organization provides for the recovery and reconstitution of the information system to a known state after a disruption, compromise, or failure." - }, - { - "id": "cp-10_gdn", - "name": "guidance", - "prose": "Recovery is executing information system contingency plan activities to restore organizational missions/business functions. Reconstitution takes place following recovery and includes activities for returning organizational information systems to fully operational states. Recovery and reconstitution operations reflect mission and business priorities, recovery point/time and reconstitution objectives, and established organizational metrics consistent with contingency plan requirements. Reconstitution includes the deactivation of any interim information system capabilities that may have been needed during recovery operations. Reconstitution also includes assessments of fully restored information system capabilities, reestablishment of continuous monitoring activities, potential information system reauthorizations, and activities to prepare the systems against future disruptions, compromises, or failures. Recovery/reconstitution capabilities employed by organizations can include both automated mechanisms and manual procedures.", - "links": [ - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-6", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-6", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#sc-24", - "rel": "related" - } - ] - }, - { - "id": "cp-10_obj", - "name": "objective", - "prose": "Determine if the organization provides for:", - "parts": [ - { - "id": "cp-10_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-10[1]" - } - ], - "prose": "the recovery of the information system to a known state after:", - "parts": [ - { - "id": "cp-10_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-10[1][a]" - } - ], - "prose": "a disruption;" - }, - { - "id": "cp-10_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-10[1][b]" - } - ], - "prose": "a compromise; or" - }, - { - "id": "cp-10_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-10[1][c]" - } - ], - "prose": "a failure;" - } - ] - }, - { - "id": "cp-10_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-10[2]" - } - ], - "prose": "the reconstitution of the information system to a known state after:", - "parts": [ - { - "id": "cp-10_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-10[2][a]" - } - ], - "prose": "a disruption;" - }, - { - "id": "cp-10_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-10[2][b]" - } - ], - "prose": "a compromise; or" - }, - { - "id": "cp-10_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-10[2][c]" - } - ], - "prose": "a failure." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing information system backup\n\ncontingency plan\n\ninformation system backup test results\n\ncontingency plan test results\n\ncontingency plan test documentation\n\nredundant secondary system for information system backups\n\nlocation(s) of redundant secondary backup system(s)\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency planning, recovery, and/or reconstitution responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes implementing information system recovery and reconstitution operations\n\nautomated mechanisms supporting and/or implementing information system recovery and reconstitution operations" - } - ] - } - ], - "controls": [ - { - "id": "cp-10.1", - "class": "SP800-53-enhancement", - "title": "Contingency Plan Testing", - "props": [ - { - "name": "label", - "value": "CP-10(1)" - }, - { - "name": "sort-id", - "value": "cp-10.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#cp-4", - "rel": "incorporated-into" - } - ] - }, - { - "id": "cp-10.2", - "class": "SP800-53-enhancement", - "title": "Transaction Recovery", - "props": [ - { - "name": "label", - "value": "CP-10(2)" - }, - { - "name": "sort-id", - "value": "cp-10.02" - } - ], - "parts": [ - { - "id": "cp-10.2_smt", - "name": "statement", - "prose": "The information system implements transaction recovery for systems that are transaction-based." - }, - { - "id": "cp-10.2_gdn", - "name": "guidance", - "prose": "Transaction-based information systems include, for example, database management systems and transaction processing systems. Mechanisms supporting transaction recovery include, for example, transaction rollback and transaction journaling." - }, - { - "id": "cp-10.2_obj", - "name": "objective", - "prose": "Determine if the information system implements transaction recovery for systems that are transaction-based." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing information system recovery and reconstitution\n\ncontingency plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ncontingency plan test documentation\n\ncontingency plan test results\n\ninformation system transaction recovery records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for transaction recovery\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing transaction recovery capability" - } - ] - } - ] - }, - { - "id": "cp-10.3", - "class": "SP800-53-enhancement", - "title": "Compensating Security Controls", - "props": [ - { - "name": "label", - "value": "CP-10(3)" - }, - { - "name": "sort-id", - "value": "cp-10.03" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-53r4", - "rel": "incorporated-into" - } - ] - }, - { - "id": "cp-10.4", - "class": "SP800-53-enhancement", - "title": "Restore Within Time Period", - "params": [ - { - "id": "cp-10.4_prm_1", - "label": "organization-defined restoration time-periods" - } - ], - "props": [ - { - "name": "label", - "value": "CP-10(4)" - }, - { - "name": "sort-id", - "value": "cp-10.04" - } - ], - "parts": [ - { - "id": "cp-10.4_smt", - "name": "statement", - "prose": "The organization provides the capability to restore information system components within {{ insert: param, cp-10.4_prm_1 }} from configuration-controlled and integrity-protected information representing a known, operational state for the components." - }, - { - "id": "cp-10.4_gdn", - "name": "guidance", - "prose": "Restoration of information system components includes, for example, reimaging which restores components to known, operational states.", - "links": [ - { - "href": "#cm-2", - "rel": "related" - } - ] - }, - { - "id": "cp-10.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-10.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-10(4)[1]" - } - ], - "prose": "defines a time period to restore information system components from configuration-controlled and integrity-protected information representing a known, operational state for the components; and" - }, - { - "id": "cp-10.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-10(4)[2]" - } - ], - "prose": "provides the capability to restore information system components within the organization-defined time period from configuration-controlled and integrity-protected information representing a known, operational state for the components." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing information system recovery and reconstitution\n\ncontingency plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ncontingency plan test documentation\n\ncontingency plan test results\n\nevidence of information system recovery and reconstitution operations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system recovery and reconstitution responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing recovery/reconstitution of information system information" - } - ] - } - ] - }, - { - "id": "cp-10.5", - "class": "SP800-53-enhancement", - "title": "Failover Capability", - "props": [ - { - "name": "label", - "value": "CP-10(5)" - }, - { - "name": "sort-id", - "value": "cp-10.05" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#si-13", - "rel": "incorporated-into" - } - ] - }, - { - "id": "cp-10.6", - "class": "SP800-53-enhancement", - "title": "Component Protection", - "props": [ - { - "name": "label", - "value": "CP-10(6)" - }, - { - "name": "sort-id", - "value": "cp-10.06" - } - ], - "parts": [ - { - "id": "cp-10.6_smt", - "name": "statement", - "prose": "The organization protects backup and restoration hardware, firmware, and software." - }, - { - "id": "cp-10.6_gdn", - "name": "guidance", - "prose": "Protection of backup and restoration hardware, firmware, and software components includes both physical and technical safeguards. Backup and restoration software includes, for example, router tables, compilers, and other security-relevant system software.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - } - ] - }, - { - "id": "cp-10.6_obj", - "name": "objective", - "prose": "Determine if the organization protects backup and restoration:", - "parts": [ - { - "id": "cp-10.6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-10(6)[1]" - } - ], - "prose": "hardware;" - }, - { - "id": "cp-10.6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-10(6)[2]" - } - ], - "prose": "firmware; and" - }, - { - "id": "cp-10.6_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-10(6)[3]" - } - ], - "prose": "software." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing information system recovery and reconstitution\n\ncontingency plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlogical access credentials\n\nphysical access credentials\n\nlogical access authorization records\n\nphysical access authorization records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system recovery and reconstitution responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for protecting backup and restoration hardware, firmware, and software\n\nautomated mechanisms supporting and/or implementing protection of backup and restoration hardware, firmware, and software" - } - ] - } - ] - } - ] - }, - { - "id": "cp-11", - "class": "SP800-53", - "title": "Alternate Communications Protocols", - "params": [ - { - "id": "cp-11_prm_1", - "label": "organization-defined alternative communications protocols" - } - ], - "props": [ - { - "name": "label", - "value": "CP-11" - }, - { - "name": "sort-id", - "value": "cp-11" - } - ], - "parts": [ - { - "id": "cp-11_smt", - "name": "statement", - "prose": "The information system provides the capability to employ {{ insert: param, cp-11_prm_1 }} in support of maintaining continuity of operations." - }, - { - "id": "cp-11_gdn", - "name": "guidance", - "prose": "Contingency plans and the associated training and testing for those plans, incorporate an alternate communications protocol capability as part of increasing the resilience of organizational information systems. Alternate communications protocols include, for example, switching from Transmission Control Protocol/Internet Protocol (TCP/IP) Version 4 to TCP/IP Version 6. Switching communications protocols may affect software applications and therefore, the potential side effects of introducing alternate communications protocols are analyzed prior to implementation." - }, - { - "id": "cp-11_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "cp-11_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-11[1]" - } - ], - "prose": "the organization defines alternative communications protocols to be employed in support of maintaining continuity of operations; and" - }, - { - "id": "cp-11_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-11[2]" - } - ], - "prose": "the information system provides the capability to employ organization-defined alternative communications protocols in support of maintaining continuity of operations." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternative communications protocols\n\ncontingency plan\n\ncontinuity of operations plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of alternative communications protocols supporting continuity of operations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\norganizational personnel with continuity of operations planning and plan implementation responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms employing alternative communications protocols" - } - ] - } - ] - }, - { - "id": "cp-12", - "class": "SP800-53", - "title": "Safe Mode", - "params": [ - { - "id": "cp-12_prm_1", - "label": "organization-defined conditions" - }, - { - "id": "cp-12_prm_2", - "label": "organization-defined restrictions of safe mode of operation" - } - ], - "props": [ - { - "name": "label", - "value": "CP-12" - }, - { - "name": "sort-id", - "value": "cp-12" - } - ], - "parts": [ - { - "id": "cp-12_smt", - "name": "statement", - "prose": "The information system, when {{ insert: param, cp-12_prm_1 }} are detected, enters a safe mode of operation with {{ insert: param, cp-12_prm_2 }}." - }, - { - "id": "cp-12_gdn", - "name": "guidance", - "prose": "For information systems supporting critical missions/business functions including, for example, military operations and weapons systems, civilian space operations, nuclear power plant operations, and air traffic control operations (especially real-time operational environments), organizations may choose to identify certain conditions under which those systems revert to a predefined safe mode of operation. The safe mode of operation, which can be activated automatically or manually, restricts the types of activities or operations information systems could execute when those conditions are encountered. Restriction includes, for example, allowing only certain functions that could be carried out under limited power or with reduced communications bandwidth." - }, - { - "id": "cp-12_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "cp-12_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-12[1]" - } - ], - "prose": "the organization defines conditions that, when detected, requires the information system to enter a safe mode of operation;" - }, - { - "id": "cp-12_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-12[2]" - } - ], - "prose": "the organization defines restrictions of safe mode of operation; and" - }, - { - "id": "cp-12_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-12[3]" - } - ], - "prose": "the information system, when organization-defined conditions are detected, enters a safe mode of operation with organization-defined restrictions of safe mode of operation." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing safe mode of operation for the information system\n\ncontingency plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system administration manuals\n\ninformation system operation manuals\n\ninformation system installation manuals\n\ncontingency plan test records\n\nincident handling records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operation responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing safe mode of operation" - } - ] - } - ] - }, - { - "id": "cp-13", - "class": "SP800-53", - "title": "Alternative Security Mechanisms", - "params": [ - { - "id": "cp-13_prm_1", - "label": "organization-defined alternative or supplemental security mechanisms" - }, - { - "id": "cp-13_prm_2", - "label": "organization-defined security functions" - } - ], - "props": [ - { - "name": "label", - "value": "CP-13" - }, - { - "name": "sort-id", - "value": "cp-13" - } - ], - "parts": [ - { - "id": "cp-13_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, cp-13_prm_1 }} for satisfying {{ insert: param, cp-13_prm_2 }} when the primary means of implementing the security function is unavailable or compromised." - }, - { - "id": "cp-13_gdn", - "name": "guidance", - "prose": "This control supports information system resiliency and contingency planning/continuity of operations. To ensure mission/business continuity, organizations can implement alternative or supplemental security mechanisms. These mechanisms may be less effective than the primary mechanisms (e.g., not as easy to use, not as scalable, or not as secure). However, having the capability to readily employ these alternative/supplemental mechanisms enhances overall mission/business continuity that might otherwise be adversely impacted if organizational operations had to be curtailed until the primary means of implementing the functions was restored. Given the cost and level of effort required to provide such alternative capabilities, this control would typically be applied only to critical security capabilities provided by information systems, system components, or information system services. For example, an organization may issue to senior executives and system administrators one-time pads in case multifactor tokens, the organization’s standard means for secure remote authentication, is compromised.", - "links": [ - { - "href": "#cp-2", - "rel": "related" - } - ] - }, - { - "id": "cp-13_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "cp-13_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-13[1]" - } - ], - "prose": "defines alternative or supplemental security mechanisms to be employed when the primary means of implementing the security function is unavailable or compromised;" - }, - { - "id": "cp-13_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-13[2]" - } - ], - "prose": "defines security functions to be satisfied using organization-defined alternative or supplemental security mechanisms when the primary means of implementing the security function is unavailable or compromised; and" - }, - { - "id": "cp-13_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "CP-13[3]" - } - ], - "prose": "employs organization-defined alternative or supplemental security mechanisms satisfying organization-defined security functions when the primary means of implementing the security function is unavailable or compromised." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate security mechanisms\n\ncontingency plan\n\ncontinuity of operations plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ncontingency plan test records\n\ncontingency plan test results\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operation responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system capability implementing alternative security mechanisms" - } - ] - } - ] - } - ] - }, - { - "id": "ia", - "class": "family", - "title": "Identification and Authentication", - "controls": [ - { - "id": "ia-1", - "class": "SP800-53", - "title": "Identification and Authentication Policy and Procedures", - "params": [ - { - "id": "ia-1_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "ia-1_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "ia-1_prm_3", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "IA-1" - }, - { - "name": "sort-id", - "value": "ia-01" - } - ], - "links": [ - { - "href": "#c80c10b3-1294-4984-a4cc-d1733ca432b9", - "rel": "reference" - }, - { - "href": "#5c201b63-0768-417b-ac22-3f014e3941b2", - "rel": "reference" - }, - { - "href": "#644f44a9-a2de-4494-9c04-cd37fba45471", - "rel": "reference" - }, - { - "href": "#ead74ea9-4c9c-446d-9b92-bcbf0ad4b655", - "rel": "reference" - }, - { - "href": "#2a71298a-ee90-490e-80ff-48c967173a47", - "rel": "reference" - }, - { - "href": "#2042d97b-f7f6-4c74-84f8-981867684659", - "rel": "reference" - }, - { - "href": "#9cb3d8fe-2127-48ba-821e-cdd2d7aee921", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ia-1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ia-1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops, documents, and disseminates to {{ insert: param, ia-1_prm_1 }}:", - "parts": [ - { - "id": "ia-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "An identification and authentication policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "ia-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls; and" - } - ] - }, - { - "id": "ia-1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the current:", - "parts": [ - { - "id": "ia-1_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Identification and authentication policy {{ insert: param, ia-1_prm_2 }}; and" - }, - { - "id": "ia-1_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Identification and authentication procedures {{ insert: param, ia-1_prm_3 }}." - } - ] - } - ] - }, - { - "id": "ia-1_gdn", - "name": "guidance", - "prose": "This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the IA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures.", - "links": [ - { - "href": "#pm-9", - "rel": "related" - } - ] - }, - { - "id": "ia-1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ia-1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(a)" - } - ], - "parts": [ - { - "id": "ia-1.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(a)(1)" - } - ], - "parts": [ - { - "id": "ia-1.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(a)(1)[1]" - } - ], - "prose": "develops and documents an identification and authentication policy that addresses:", - "parts": [ - { - "id": "ia-1.a.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(a)(1)[1][a]" - } - ], - "prose": "purpose;" - }, - { - "id": "ia-1.a.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(a)(1)[1][b]" - } - ], - "prose": "scope;" - }, - { - "id": "ia-1.a.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(a)(1)[1][c]" - } - ], - "prose": "roles;" - }, - { - "id": "ia-1.a.1_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(a)(1)[1][d]" - } - ], - "prose": "responsibilities;" - }, - { - "id": "ia-1.a.1_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(a)(1)[1][e]" - } - ], - "prose": "management commitment;" - }, - { - "id": "ia-1.a.1_obj.1.f", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(a)(1)[1][f]" - } - ], - "prose": "coordination among organizational entities;" - }, - { - "id": "ia-1.a.1_obj.1.g", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(a)(1)[1][g]" - } - ], - "prose": "compliance;" - } - ] - }, - { - "id": "ia-1.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(a)(1)[2]" - } - ], - "prose": "defines personnel or roles to whom the identification and authentication policy is to be disseminated; and" - }, - { - "id": "ia-1.a.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(a)(1)[3]" - } - ], - "prose": "disseminates the identification and authentication policy to organization-defined personnel or roles;" - } - ] - }, - { - "id": "ia-1.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(a)(2)" - } - ], - "parts": [ - { - "id": "ia-1.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(a)(2)[1]" - } - ], - "prose": "develops and documents procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls;" - }, - { - "id": "ia-1.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(a)(2)[2]" - } - ], - "prose": "defines personnel or roles to whom the procedures are to be disseminated;" - }, - { - "id": "ia-1.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(a)(2)[3]" - } - ], - "prose": "disseminates the procedures to organization-defined personnel or roles;" - } - ] - } - ] - }, - { - "id": "ia-1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(b)" - } - ], - "parts": [ - { - "id": "ia-1.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(b)(1)" - } - ], - "parts": [ - { - "id": "ia-1.b.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(b)(1)[1]" - } - ], - "prose": "defines the frequency to review and update the current identification and authentication policy;" - }, - { - "id": "ia-1.b.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(b)(1)[2]" - } - ], - "prose": "reviews and updates the current identification and authentication policy with the organization-defined frequency; and" - } - ] - }, - { - "id": "ia-1.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(b)(2)" - } - ], - "parts": [ - { - "id": "ia-1.b.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(b)(2)[1]" - } - ], - "prose": "defines the frequency to review and update the current identification and authentication procedures; and" - }, - { - "id": "ia-1.b.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-1(b)(2)[2]" - } - ], - "prose": "reviews and updates the current identification and authentication procedures with the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy and procedures\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with identification and authentication responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "ia-2", - "class": "SP800-53", - "title": "Identification and Authentication (organizational Users)", - "props": [ - { - "name": "label", - "value": "IA-2" - }, - { - "name": "sort-id", - "value": "ia-02" - } - ], - "links": [ - { - "href": "#ad733a42-a7ed-4774-b988-4930c28852f3", - "rel": "reference" - }, - { - "href": "#ff3bfb02-79b2-411f-8735-98dfe5af2ab0", - "rel": "reference" - }, - { - "href": "#4da24a96-6cf8-435d-9d1f-c73247cad109", - "rel": "reference" - }, - { - "href": "#74e740a4-c45d-49f3-a86e-eb747c549e01", - "rel": "reference" - }, - { - "href": "#c80c10b3-1294-4984-a4cc-d1733ca432b9", - "rel": "reference" - }, - { - "href": "#644f44a9-a2de-4494-9c04-cd37fba45471", - "rel": "reference" - }, - { - "href": "#ead74ea9-4c9c-446d-9b92-bcbf0ad4b655", - "rel": "reference" - }, - { - "href": "#2a71298a-ee90-490e-80ff-48c967173a47", - "rel": "reference" - }, - { - "href": "#2042d97b-f7f6-4c74-84f8-981867684659", - "rel": "reference" - }, - { - "href": "#ba557c91-ba3e-4792-adc6-a4ae479b39ff", - "rel": "reference" - }, - { - "href": "#85280698-0417-489d-b214-12bb935fb939", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ia-2_smt", - "name": "statement", - "prose": "The information system uniquely identifies and authenticates organizational users (or processes acting on behalf of organizational users)." - }, - { - "id": "ia-2_gdn", - "name": "guidance", - "prose": "Organizational users include employees or individuals that organizations deem to have equivalent status of employees (e.g., contractors, guest researchers). This control applies to all accesses other than: (i) accesses that are explicitly identified and documented in AC-14; and (ii) accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity. Organizations employ passwords, tokens, or biometrics to authenticate user identities, or in the case multifactor authentication, or some combination thereof. Access to organizational information systems is defined as either local access or network access. Local access is any access to organizational information systems by users (or processes acting on behalf of users) where such access is obtained by direct connections without the use of networks. Network access is access to organizational information systems by users (or processes acting on behalf of users) where such access is obtained through network connections (i.e., nonlocal accesses). Remote access is a type of network access that involves communication through external networks (e.g., the Internet). Internal networks include local area networks and wide area networks. In addition, the use of encrypted virtual private networks (VPNs) for network connections between organization-controlled endpoints and non-organization controlled endpoints may be treated as internal networks from the perspective of protecting the confidentiality and integrity of information traversing the network. Organizations can satisfy the identification and authentication requirements in this control by complying with the requirements in Homeland Security Presidential Directive 12 consistent with the specific organizational implementation plans. Multifactor authentication requires the use of two or more different factors to achieve authentication. The factors are defined as: (i) something you know (e.g., password, personal identification number [PIN]); (ii) something you have (e.g., cryptographic identification device, token); or (iii) something you are (e.g., biometric). Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD common access card. In addition to identifying and authenticating users at the information system level (i.e., at logon), organizations also employ identification and authentication mechanisms at the application level, when necessary, to provide increased information security. Identification and authentication requirements for other than organizational users are described in IA-8.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-14", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - } - ] - }, - { - "id": "ia-2_obj", - "name": "objective", - "prose": "Determine if the information system uniquely identifies and authenticates organizational users (or processes acting on behalf of organizational users)." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of information system accounts\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\norganizational personnel with account management responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for uniquely identifying and authenticating users\n\nautomated mechanisms supporting and/or implementing identification and authentication capability" - } - ] - } - ], - "controls": [ - { - "id": "ia-2.1", - "class": "SP800-53-enhancement", - "title": "Network Access to Privileged Accounts", - "props": [ - { - "name": "label", - "value": "IA-2(1)" - }, - { - "name": "sort-id", - "value": "ia-02.01" - } - ], - "parts": [ - { - "id": "ia-2.1_smt", - "name": "statement", - "prose": "The information system implements multifactor authentication for network access to privileged accounts." - }, - { - "id": "ia-2.1_gdn", - "name": "guidance", - "links": [ - { - "href": "#ac-6", - "rel": "related" - } - ] - }, - { - "id": "ia-2.1_obj", - "name": "objective", - "prose": "Determine if the information system implements multifactor authentication for network access to privileged accounts." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of information system accounts\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing multifactor authentication capability" - } - ] - } - ] - }, - { - "id": "ia-2.2", - "class": "SP800-53-enhancement", - "title": "Network Access to Non-privileged Accounts", - "props": [ - { - "name": "label", - "value": "IA-2(2)" - }, - { - "name": "sort-id", - "value": "ia-02.02" - } - ], - "parts": [ - { - "id": "ia-2.2_smt", - "name": "statement", - "prose": "The information system implements multifactor authentication for network access to non-privileged accounts." - }, - { - "id": "ia-2.2_obj", - "name": "objective", - "prose": "Determine if the information system implements multifactor authentication for network access to non-privileged accounts." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of information system accounts\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing multifactor authentication capability" - } - ] - } - ] - }, - { - "id": "ia-2.3", - "class": "SP800-53-enhancement", - "title": "Local Access to Privileged Accounts", - "props": [ - { - "name": "label", - "value": "IA-2(3)" - }, - { - "name": "sort-id", - "value": "ia-02.03" - } - ], - "parts": [ - { - "id": "ia-2.3_smt", - "name": "statement", - "prose": "The information system implements multifactor authentication for local access to privileged accounts." - }, - { - "id": "ia-2.3_gdn", - "name": "guidance", - "links": [ - { - "href": "#ac-6", - "rel": "related" - } - ] - }, - { - "id": "ia-2.3_obj", - "name": "objective", - "prose": "Determine if the information system implements multifactor authentication for local access to privileged accounts." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of information system accounts\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing multifactor authentication capability" - } - ] - } - ] - }, - { - "id": "ia-2.4", - "class": "SP800-53-enhancement", - "title": "Local Access to Non-privileged Accounts", - "props": [ - { - "name": "label", - "value": "IA-2(4)" - }, - { - "name": "sort-id", - "value": "ia-02.04" - } - ], - "parts": [ - { - "id": "ia-2.4_smt", - "name": "statement", - "prose": "The information system implements multifactor authentication for local access to non-privileged accounts." - }, - { - "id": "ia-2.4_obj", - "name": "objective", - "prose": "Determine if the information system implements multifactor authentication for local access to non-privileged accounts." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of information system accounts\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing multifactor authentication capability" - } - ] - } - ] - }, - { - "id": "ia-2.5", - "class": "SP800-53-enhancement", - "title": "Group Authentication", - "props": [ - { - "name": "label", - "value": "IA-2(5)" - }, - { - "name": "sort-id", - "value": "ia-02.05" - } - ], - "parts": [ - { - "id": "ia-2.5_smt", - "name": "statement", - "prose": "The organization requires individuals to be authenticated with an individual authenticator when a group authenticator is employed." - }, - { - "id": "ia-2.5_gdn", - "name": "guidance", - "prose": "Requiring individuals to use individual authenticators as a second level of authentication helps organizations to mitigate the risk of using group authenticators." - }, - { - "id": "ia-2.5_obj", - "name": "objective", - "prose": "Determine if the organization requires individuals to be authenticated with an individual authenticator when a group authenticator is employed." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of information system accounts\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing authentication capability for group accounts" - } - ] - } - ] - }, - { - "id": "ia-2.6", - "class": "SP800-53-enhancement", - "title": "Network Access to Privileged Accounts - Separate Device", - "params": [ - { - "id": "ia-2.6_prm_1", - "label": "organization-defined strength of mechanism requirements" - } - ], - "props": [ - { - "name": "label", - "value": "IA-2(6)" - }, - { - "name": "sort-id", - "value": "ia-02.06" - } - ], - "parts": [ - { - "id": "ia-2.6_smt", - "name": "statement", - "prose": "The information system implements multifactor authentication for network access to privileged accounts such that one of the factors is provided by a device separate from the system gaining access and the device meets {{ insert: param, ia-2.6_prm_1 }}." - }, - { - "id": "ia-2.6_gdn", - "name": "guidance", - "links": [ - { - "href": "#ac-6", - "rel": "related" - } - ] - }, - { - "id": "ia-2.6_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ia-2.6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-2(6)[1]" - } - ], - "prose": "the information system implements multifactor authentication for network access to privileged accounts such that one of the factors is provided by a device separate from the system gaining access;" - }, - { - "id": "ia-2.6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-2(6)[2]" - } - ], - "prose": "the organization defines strength of mechanism requirements to be enforced by a device separate from the system gaining network access to privileged accounts; and" - }, - { - "id": "ia-2.6_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-2(6)[3]" - } - ], - "prose": "the information system implements multifactor authentication for network access to privileged accounts such that a device, separate from the system gaining access, meets organization-defined strength of mechanism requirements." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of information system accounts\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing multifactor authentication capability" - } - ] - } - ] - }, - { - "id": "ia-2.7", - "class": "SP800-53-enhancement", - "title": "Network Access to Non-privileged Accounts - Separate Device", - "params": [ - { - "id": "ia-2.7_prm_1", - "label": "organization-defined strength of mechanism requirements" - } - ], - "props": [ - { - "name": "label", - "value": "IA-2(7)" - }, - { - "name": "sort-id", - "value": "ia-02.07" - } - ], - "parts": [ - { - "id": "ia-2.7_smt", - "name": "statement", - "prose": "The information system implements multifactor authentication for network access to non-privileged accounts such that one of the factors is provided by a device separate from the system gaining access and the device meets {{ insert: param, ia-2.7_prm_1 }}." - }, - { - "id": "ia-2.7_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ia-2.7_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-2(7)[1]" - } - ], - "prose": "the information system implements multifactor authentication for network access to non-privileged accounts such that one of the factors is provided by a device separate from the system gaining access;" - }, - { - "id": "ia-2.7_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-2(7)[2]" - } - ], - "prose": "the organization defines strength of mechanism requirements to be enforced by a device separate from the system gaining network access to non-privileged accounts; and" - }, - { - "id": "ia-2.7_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-2(7)[3]" - } - ], - "prose": "the information system implements multifactor authentication for network access to non-privileged accounts such that a device, separate from the system gaining access, meets organization-defined strength of mechanism requirements." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of information system accounts\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing multifactor authentication capability" - } - ] - } - ] - }, - { - "id": "ia-2.8", - "class": "SP800-53-enhancement", - "title": "Network Access to Privileged Accounts - Replay Resistant", - "props": [ - { - "name": "label", - "value": "IA-2(8)" - }, - { - "name": "sort-id", - "value": "ia-02.08" - } - ], - "parts": [ - { - "id": "ia-2.8_smt", - "name": "statement", - "prose": "The information system implements replay-resistant authentication mechanisms for network access to privileged accounts." - }, - { - "id": "ia-2.8_gdn", - "name": "guidance", - "prose": "Authentication processes resist replay attacks if it is impractical to achieve successful authentications by replaying previous authentication messages. Replay-resistant techniques include, for example, protocols that use nonces or challenges such as Transport Layer Security (TLS) and time synchronous or challenge-response one-time authenticators." - }, - { - "id": "ia-2.8_obj", - "name": "objective", - "prose": "Determine if the information system implements replay-resistant authentication mechanisms for network access to privileged accounts." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of privileged information system accounts\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing identification and authentication capability\n\nautomated mechanisms supporting and/or implementing replay resistant authentication mechanisms" - } - ] - } - ] - }, - { - "id": "ia-2.9", - "class": "SP800-53-enhancement", - "title": "Network Access to Non-privileged Accounts - Replay Resistant", - "props": [ - { - "name": "label", - "value": "IA-2(9)" - }, - { - "name": "sort-id", - "value": "ia-02.09" - } - ], - "parts": [ - { - "id": "ia-2.9_smt", - "name": "statement", - "prose": "The information system implements replay-resistant authentication mechanisms for network access to non-privileged accounts." - }, - { - "id": "ia-2.9_gdn", - "name": "guidance", - "prose": "Authentication processes resist replay attacks if it is impractical to achieve successful authentications by recording/replaying previous authentication messages. Replay-resistant techniques include, for example, protocols that use nonces or challenges such as Transport Layer Security (TLS) and time synchronous or challenge-response one-time authenticators." - }, - { - "id": "ia-2.9_obj", - "name": "objective", - "prose": "Determine if the information system implements replay-resistant authentication mechanisms for network access to non-privileged accounts." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of non-privileged information system accounts\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing identification and authentication capability\n\nautomated mechanisms supporting and/or implementing replay resistant authentication mechanisms" - } - ] - } - ] - }, - { - "id": "ia-2.10", - "class": "SP800-53-enhancement", - "title": "Single Sign-on", - "params": [ - { - "id": "ia-2.10_prm_1", - "label": "organization-defined information system accounts and services" - } - ], - "props": [ - { - "name": "label", - "value": "IA-2(10)" - }, - { - "name": "sort-id", - "value": "ia-02.10" - } - ], - "parts": [ - { - "id": "ia-2.10_smt", - "name": "statement", - "prose": "The information system provides a single sign-on capability for {{ insert: param, ia-2.10_prm_1 }}." - }, - { - "id": "ia-2.10_gdn", - "name": "guidance", - "prose": "Single sign-on enables users to log in once and gain access to multiple information system resources. Organizations consider the operational efficiencies provided by single sign-on capabilities with the increased risk from disclosures of single authenticators providing access to multiple system resources." - }, - { - "id": "ia-2.10_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ia-2.10_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-2(10)[1]" - } - ], - "prose": "the organization defines a list of information system accounts and services for which a single sign-on capability must be provided; and" - }, - { - "id": "ia-2.10_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-2(10)[2]" - } - ], - "prose": "the information system provides a single sign-on capability for organization-defined information system accounts and services." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing single sign-on capability for information system accounts and services\n\nprocedures addressing identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of information system accounts and services requiring single sign-on capability\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing identification and authentication capability\n\nautomated mechanisms supporting and/or implementing single sign-on capability for information system accounts and services" - } - ] - } - ] - }, - { - "id": "ia-2.11", - "class": "SP800-53-enhancement", - "title": "Remote Access - Separate Device", - "params": [ - { - "id": "ia-2.11_prm_1", - "label": "organization-defined strength of mechanism requirements" - } - ], - "props": [ - { - "name": "label", - "value": "IA-2(11)" - }, - { - "name": "sort-id", - "value": "ia-02.11" - } - ], - "parts": [ - { - "id": "ia-2.11_smt", - "name": "statement", - "prose": "The information system implements multifactor authentication for remote access to privileged and non-privileged accounts such that one of the factors is provided by a device separate from the system gaining access and the device meets {{ insert: param, ia-2.11_prm_1 }}." - }, - { - "id": "ia-2.11_gdn", - "name": "guidance", - "prose": "For remote access to privileged/non-privileged accounts, the purpose of requiring a device that is separate from the information system gaining access for one of the factors during multifactor authentication is to reduce the likelihood of compromising authentication credentials stored on the system. For example, adversaries deploying malicious code on organizational information systems can potentially compromise such credentials resident on the system and subsequently impersonate authorized users.", - "links": [ - { - "href": "#ac-6", - "rel": "related" - } - ] - }, - { - "id": "ia-2.11_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ia-2.11_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-2(11)[1]" - } - ], - "prose": "the information system implements multifactor authentication for remote access to privileged accounts such that one of the factors is provided by a device separate from the system gaining access;" - }, - { - "id": "ia-2.11_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-2(11)[2]" - } - ], - "prose": "the information system implements multifactor authentication for remote access to non-privileged accounts such that one of the factors is provided by a device separate from the system gaining access;" - }, - { - "id": "ia-2.11_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-2(11)[3]" - } - ], - "prose": "the organization defines strength of mechanism requirements to be enforced by a device separate from the system gaining remote access to privileged accounts;" - }, - { - "id": "ia-2.11_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-2(11)[4]" - } - ], - "prose": "the organization defines strength of mechanism requirements to be enforced by a device separate from the system gaining remote access to non-privileged accounts;" - }, - { - "id": "ia-2.11_obj.5", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-2(11)[5]" - } - ], - "prose": "the information system implements multifactor authentication for remote access to privileged accounts such that a device, separate from the system gaining access, meets organization-defined strength of mechanism requirements; and" - }, - { - "id": "ia-2.11_obj.6", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-2(11)[6]" - } - ], - "prose": "the information system implements multifactor authentication for remote access to non-privileged accounts such that a device, separate from the system gaining access, meets organization-defined strength of mechanism requirements." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of privileged and non-privileged information system accounts\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing identification and authentication capability" - } - ] - } - ] - }, - { - "id": "ia-2.12", - "class": "SP800-53-enhancement", - "title": "Acceptance of PIV Credentials", - "props": [ - { - "name": "label", - "value": "IA-2(12)" - }, - { - "name": "sort-id", - "value": "ia-02.12" - } - ], - "parts": [ - { - "id": "ia-2.12_smt", - "name": "statement", - "prose": "The information system accepts and electronically verifies Personal Identity Verification (PIV) credentials." - }, - { - "id": "ia-2.12_gdn", - "name": "guidance", - "prose": "This control enhancement applies to organizations implementing logical access control systems (LACS) and physical access control systems (PACS). Personal Identity Verification (PIV) credentials are those credentials issued by federal agencies that conform to FIPS Publication 201 and supporting guidance documents. OMB Memorandum 11-11 requires federal agencies to continue implementing the requirements specified in HSPD-12 to enable agency-wide use of PIV credentials.", - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - } - ] - }, - { - "id": "ia-2.12_obj", - "name": "objective", - "prose": "Determine if the information system:", - "parts": [ - { - "id": "ia-2.12_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-2(12)[1]" - } - ], - "prose": "accepts Personal Identity Verification (PIV) credentials; and" - }, - { - "id": "ia-2.12_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-2(12)[2]" - } - ], - "prose": "electronically verifies Personal Identity Verification (PIV) credentials." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nPIV verification records\n\nevidence of PIV credentials\n\nPIV credential authorizations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing acceptance and verification of PIV credentials" - } - ] - } - ] - }, - { - "id": "ia-2.13", - "class": "SP800-53-enhancement", - "title": "Out-of-band Authentication", - "params": [ - { - "id": "ia-2.13_prm_1", - "label": "organization-defined out-of-band authentication" - }, - { - "id": "ia-2.13_prm_2", - "label": "organization-defined conditions" - } - ], - "props": [ - { - "name": "label", - "value": "IA-2(13)" - }, - { - "name": "sort-id", - "value": "ia-02.13" - } - ], - "parts": [ - { - "id": "ia-2.13_smt", - "name": "statement", - "prose": "The information system implements {{ insert: param, ia-2.13_prm_1 }} under {{ insert: param, ia-2.13_prm_2 }}." - }, - { - "id": "ia-2.13_gdn", - "name": "guidance", - "prose": "Out-of-band authentication (OOBA) refers to the use of two separate communication paths to identify and authenticate users or devices to an information system. The first path (i.e., the in-band path), is used to identify and authenticate users or devices, and generally is the path through which information flows. The second path (i.e., the out-of-band path) is used to independently verify the authentication and/or requested action. For example, a user authenticates via a notebook computer to a remote server to which the user desires access, and requests some action of the server via that communication path. Subsequently, the server contacts the user via the user’s cell phone to verify that the requested action originated from the user. The user may either confirm the intended action to an individual on the telephone or provide an authentication code via the telephone. This type of authentication can be employed by organizations to mitigate actual or suspected man-in the-middle attacks. The conditions for activation can include, for example, suspicious activities, new threat indicators or elevated threat levels, or the impact level or classification level of information in requested transactions.", - "links": [ - { - "href": "#ia-10", - "rel": "related" - }, - { - "href": "#ia-11", - "rel": "related" - }, - { - "href": "#sc-37", - "rel": "related" - } - ] - }, - { - "id": "ia-2.13_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ia-2.13_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-2(13)[1]" - } - ], - "prose": "the organization defines out-of-band authentication to be implemented by the information system;" - }, - { - "id": "ia-2.13_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-2(13)[2]" - } - ], - "prose": "the organization defines conditions under which the information system implements organization-defined out-of-band authentication; and" - }, - { - "id": "ia-2.13_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-2(13)[3]" - } - ], - "prose": "the information system implements organization-defined out-of-band authentication under organization-defined conditions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nsystem-generated list of out-of-band authentication paths\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing out-of-band authentication capability" - } - ] - } - ] - } - ] - }, - { - "id": "ia-3", - "class": "SP800-53", - "title": "Device Identification and Authentication", - "params": [ - { - "id": "ia-3_prm_1", - "label": "organization-defined specific and/or types of devices" - }, - { - "id": "ia-3_prm_2", - "select": { - "how-many": "one-or-more", - "choice": [ - "local", - "remote", - "network" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "IA-3" - }, - { - "name": "sort-id", - "value": "ia-03" - } - ], - "parts": [ - { - "id": "ia-3_smt", - "name": "statement", - "prose": "The information system uniquely identifies and authenticates {{ insert: param, ia-3_prm_1 }} before establishing a {{ insert: param, ia-3_prm_2 }} connection." - }, - { - "id": "ia-3_gdn", - "name": "guidance", - "prose": "Organizational devices requiring unique device-to-device identification and authentication may be defined by type, by device, or by a combination of type/device. Information systems typically use either shared known information (e.g., Media Access Control [MAC] or Transmission Control Protocol/Internet Protocol [TCP/IP] addresses) for device identification or organizational authentication solutions (e.g., IEEE 802.1x and Extensible Authentication Protocol [EAP], Radius server with EAP-Transport Layer Security [TLS] authentication, Kerberos) to identify/authenticate devices on local and/or wide area networks. Organizations determine the required strength of authentication mechanisms by the security categories of information systems. Because of the challenges of applying this control on large scale, organizations are encouraged to only apply the control to those limited number (and type) of devices that truly need to support this capability.", - "links": [ - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#ca-3", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - } - ] - }, - { - "id": "ia-3_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ia-3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3[1]" - } - ], - "prose": "the organization defines specific and/or types of devices that the information system uniquely identifies and authenticates before establishing one or more of the following:", - "parts": [ - { - "id": "ia-3_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3[1][a]" - } - ], - "prose": "a local connection;" - }, - { - "id": "ia-3_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3[1][b]" - } - ], - "prose": "a remote connection; and/or" - }, - { - "id": "ia-3_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3[1][c]" - } - ], - "prose": "a network connection; and" - } - ] - }, - { - "id": "ia-3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3[2]" - } - ], - "prose": "the information system uniquely identifies and authenticates organization-defined devices before establishing one or more of the following:", - "parts": [ - { - "id": "ia-3_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3[2][a]" - } - ], - "prose": "a local connection;" - }, - { - "id": "ia-3_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3[2][b]" - } - ], - "prose": "a remote connection; and/or" - }, - { - "id": "ia-3_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3[2][c]" - } - ], - "prose": "a network connection." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing device identification and authentication\n\ninformation system design documentation\n\nlist of devices requiring unique identification and authentication\n\ndevice connection reports\n\ninformation system configuration settings and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with operational responsibilities for device identification and authentication\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing device identification and authentication capability" - } - ] - } - ], - "controls": [ - { - "id": "ia-3.1", - "class": "SP800-53-enhancement", - "title": "Cryptographic Bidirectional Authentication", - "params": [ - { - "id": "ia-3.1_prm_1", - "label": "organization-defined specific devices and/or types of devices" - }, - { - "id": "ia-3.1_prm_2", - "select": { - "how-many": "one-or-more", - "choice": [ - "local", - "remote", - "network" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "IA-3(1)" - }, - { - "name": "sort-id", - "value": "ia-03.01" - } - ], - "parts": [ - { - "id": "ia-3.1_smt", - "name": "statement", - "prose": "The information system authenticates {{ insert: param, ia-3.1_prm_1 }} before establishing {{ insert: param, ia-3.1_prm_2 }} connection using bidirectional authentication that is cryptographically based." - }, - { - "id": "ia-3.1_gdn", - "name": "guidance", - "prose": "A local connection is any connection with a device communicating without the use of a network. A network connection is any connection with a device that communicates through a network (e.g., local area or wide area network, Internet). A remote connection is any connection with a device communicating through an external network (e.g., the Internet). Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of greater risk (e.g., remote connections).", - "links": [ - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "ia-3.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ia-3.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3(1)[1]" - } - ], - "prose": "the organization defines specific and/or types of devices requiring use of cryptographically based, bidirectional authentication to authenticate before establishing one or more of the following:", - "parts": [ - { - "id": "ia-3.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3(1)[1][a]" - } - ], - "prose": "a local connection;" - }, - { - "id": "ia-3.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3(1)[1][b]" - } - ], - "prose": "a remote connection; and/or" - }, - { - "id": "ia-3.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3(1)[1][c]" - } - ], - "prose": "a network connection;" - } - ] - }, - { - "id": "ia-3.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3(1)[2]" - } - ], - "prose": "the information system uses cryptographically based bidirectional authentication to authenticate organization-defined devices before establishing one or more of the following:", - "parts": [ - { - "id": "ia-3.1_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3(1)[2][a]" - } - ], - "prose": "a local connection;" - }, - { - "id": "ia-3.1_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3(1)[2][b]" - } - ], - "prose": "a remote connection; and/or" - }, - { - "id": "ia-3.1_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3(1)[2][c]" - } - ], - "prose": "a network connection." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing device identification and authentication\n\ninformation system design documentation\n\nlist of devices requiring unique identification and authentication\n\ndevice connection reports\n\ninformation system configuration settings and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with operational responsibilities for device identification and authentication\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing device authentication capability\n\ncryptographically based bidirectional authentication mechanisms" - } - ] - } - ] - }, - { - "id": "ia-3.2", - "class": "SP800-53-enhancement", - "title": "Cryptographic Bidirectional Network Authentication", - "props": [ - { - "name": "label", - "value": "IA-3(2)" - }, - { - "name": "sort-id", - "value": "ia-03.02" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#ia-3.1", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ia-3.3", - "class": "SP800-53-enhancement", - "title": "Dynamic Address Allocation", - "params": [ - { - "id": "ia-3.3_prm_1", - "label": "organization-defined lease information and lease duration" - } - ], - "props": [ - { - "name": "label", - "value": "IA-3(3)" - }, - { - "name": "sort-id", - "value": "ia-03.03" - } - ], - "parts": [ - { - "id": "ia-3.3_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ia-3.3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Standardizes dynamic address allocation lease information and the lease duration assigned to devices in accordance with {{ insert: param, ia-3.3_prm_1 }}; and" - }, - { - "id": "ia-3.3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Audits lease information when assigned to a device." - } - ] - }, - { - "id": "ia-3.3_gdn", - "name": "guidance", - "prose": "DHCP-enabled clients obtaining leases for IP addresses from DHCP servers, is a typical example of dynamic address allocation for devices.", - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-3", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - } - ] - }, - { - "id": "ia-3.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ia-3.3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3(3)(a)" - } - ], - "parts": [ - { - "id": "ia-3.3.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3(3)(a)[1]" - } - ], - "prose": "defines lease information to be employed to standardize dynamic address allocation for devices;" - }, - { - "id": "ia-3.3.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3(3)(a)[2]" - } - ], - "prose": "defines lease duration to be employed to standardize dynamic address allocation for devices;" - }, - { - "id": "ia-3.3.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3(3)(a)[3]" - } - ], - "prose": "standardizes dynamic address allocation of lease information assigned to devices in accordance with organization-defined lease information;" - }, - { - "id": "ia-3.3.a_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3(3)(a)[4]" - } - ], - "prose": "standardizes dynamic address allocation of the lease duration assigned to devices in accordance with organization-defined lease duration; and" - } - ], - "links": [ - { - "href": "#ia-3.3_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ia-3.3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3(3)(b)" - } - ], - "prose": "audits lease information when assigned to a device.", - "links": [ - { - "href": "#ia-3.3_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing device identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nevidence of lease information and lease duration assigned to devices\n\ndevice connection reports\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with operational responsibilities for device identification and authentication\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing device identification and authentication capability\n\nautomated mechanisms supporting and/or implementing dynamic address allocation\n\nautomated mechanisms supporting and/or implanting auditing of lease information" - } - ] - } - ] - }, - { - "id": "ia-3.4", - "class": "SP800-53-enhancement", - "title": "Device Attestation", - "params": [ - { - "id": "ia-3.4_prm_1", - "label": "organization-defined configuration management process" - } - ], - "props": [ - { - "name": "label", - "value": "IA-3(4)" - }, - { - "name": "sort-id", - "value": "ia-03.04" - } - ], - "parts": [ - { - "id": "ia-3.4_smt", - "name": "statement", - "prose": "The organization ensures that device identification and authentication based on attestation is handled by {{ insert: param, ia-3.4_prm_1 }}." - }, - { - "id": "ia-3.4_gdn", - "name": "guidance", - "prose": "Device attestation refers to the identification and authentication of a device based on its configuration and known operating state. This might be determined via some cryptographic hash of the device. If device attestation is the means of identification and authentication, then it is important that patches and updates to the device are handled via a configuration management process such that the those patches/updates are done securely and at the same time do not disrupt the identification and authentication to other devices." - }, - { - "id": "ia-3.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ia-3.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3(4)[1]" - } - ], - "prose": "defines configuration management process to be employed to handle device identification and authentication based on attestation; and" - }, - { - "id": "ia-3.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-3(4)[2]" - } - ], - "prose": "ensures that device identification and authentication based on attestation is handled by organization-defined configuration management process." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing device identification and authentication\n\nprocedures addressing device configuration management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nconfiguration management records\n\nchange control records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with operational responsibilities for device identification and authentication\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing device identification and authentication capability\n\nautomated mechanisms supporting and/or implementing configuration management\n\ncryptographic mechanisms supporting device attestation" - } - ] - } - ] - } - ] - }, - { - "id": "ia-4", - "class": "SP800-53", - "title": "Identifier Management", - "params": [ - { - "id": "ia-4_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "ia-4_prm_2", - "label": "organization-defined time period" - }, - { - "id": "ia-4_prm_3", - "label": "organization-defined time period of inactivity" - } - ], - "props": [ - { - "name": "label", - "value": "IA-4" - }, - { - "name": "sort-id", - "value": "ia-04" - } - ], - "links": [ - { - "href": "#c80c10b3-1294-4984-a4cc-d1733ca432b9", - "rel": "reference" - }, - { - "href": "#ead74ea9-4c9c-446d-9b92-bcbf0ad4b655", - "rel": "reference" - }, - { - "href": "#2a71298a-ee90-490e-80ff-48c967173a47", - "rel": "reference" - }, - { - "href": "#2042d97b-f7f6-4c74-84f8-981867684659", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ia-4_smt", - "name": "statement", - "prose": "The organization manages information system identifiers by:", - "parts": [ - { - "id": "ia-4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Receiving authorization from {{ insert: param, ia-4_prm_1 }} to assign an individual, group, role, or device identifier;" - }, - { - "id": "ia-4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Selecting an identifier that identifies an individual, group, role, or device;" - }, - { - "id": "ia-4_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Assigning the identifier to the intended individual, group, role, or device;" - }, - { - "id": "ia-4_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Preventing reuse of identifiers for {{ insert: param, ia-4_prm_2 }}; and" - }, - { - "id": "ia-4_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Disabling the identifier after {{ insert: param, ia-4_prm_3 }}." - } - ] - }, - { - "id": "ia-4_gdn", - "name": "guidance", - "prose": "Common device identifiers include, for example, media access control (MAC), Internet protocol (IP) addresses, or device-unique token identifiers. Management of individual identifiers is not applicable to shared information system accounts (e.g., guest and anonymous accounts). Typically, individual identifiers are the user names of the information system accounts assigned to those individuals. In such instances, the account management activities of AC-2 use account names provided by IA-4. This control also addresses individual identifiers not necessarily associated with information system accounts (e.g., identifiers used in physical security control databases accessed by badge reader systems for access to information systems). Preventing reuse of identifiers implies preventing the assignment of previously used individual, group, role, or device identifiers to different individuals, groups, roles, or devices.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "#sc-37", - "rel": "related" - } - ] - }, - { - "id": "ia-4_obj", - "name": "objective", - "prose": "Determine if the organization manages information system identifiers by:", - "parts": [ - { - "id": "ia-4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(a)" - } - ], - "parts": [ - { - "id": "ia-4.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(a)[1]" - } - ], - "prose": "defining personnel or roles from whom authorization must be received to assign:", - "parts": [ - { - "id": "ia-4.a_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(a)[1][a]" - } - ], - "prose": "an individual identifier;" - }, - { - "id": "ia-4.a_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(a)[1][b]" - } - ], - "prose": "a group identifier;" - }, - { - "id": "ia-4.a_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(a)[1][c]" - } - ], - "prose": "a role identifier; and/or" - }, - { - "id": "ia-4.a_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(a)[1][d]" - } - ], - "prose": "a device identifier;" - } - ] - }, - { - "id": "ia-4.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(a)[2]" - } - ], - "prose": "receiving authorization from organization-defined personnel or roles to assign:", - "parts": [ - { - "id": "ia-4.a_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(a)[2][a]" - } - ], - "prose": "an individual identifier;" - }, - { - "id": "ia-4.a_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(a)[2][b]" - } - ], - "prose": "a group identifier;" - }, - { - "id": "ia-4.a_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(a)[2][c]" - } - ], - "prose": "a role identifier; and/or" - }, - { - "id": "ia-4.a_obj.2.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(a)[2][d]" - } - ], - "prose": "a device identifier;" - } - ] - } - ] - }, - { - "id": "ia-4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(b)" - } - ], - "prose": "selecting an identifier that identifies:", - "parts": [ - { - "id": "ia-4.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(b)[1]" - } - ], - "prose": "an individual;" - }, - { - "id": "ia-4.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(b)[2]" - } - ], - "prose": "a group;" - }, - { - "id": "ia-4.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(b)[3]" - } - ], - "prose": "a role; and/or" - }, - { - "id": "ia-4.b_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(b)[4]" - } - ], - "prose": "a device;" - } - ] - }, - { - "id": "ia-4.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(c)" - } - ], - "prose": "assigning the identifier to the intended:", - "parts": [ - { - "id": "ia-4.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(c)[1]" - } - ], - "prose": "individual;" - }, - { - "id": "ia-4.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(c)[2]" - } - ], - "prose": "group;" - }, - { - "id": "ia-4.c_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(c)[3]" - } - ], - "prose": "role; and/or" - }, - { - "id": "ia-4.c_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(c)[4]" - } - ], - "prose": "device;" - } - ] - }, - { - "id": "ia-4.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(d)" - } - ], - "parts": [ - { - "id": "ia-4.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(d)[1]" - } - ], - "prose": "defining a time period for preventing reuse of identifiers;" - }, - { - "id": "ia-4.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(d)[2]" - } - ], - "prose": "preventing reuse of identifiers for the organization-defined time period;" - } - ] - }, - { - "id": "ia-4.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(e)" - } - ], - "parts": [ - { - "id": "ia-4.e_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(e)[1]" - } - ], - "prose": "defining a time period of inactivity to disable the identifier; and" - }, - { - "id": "ia-4.e_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(e)[2]" - } - ], - "prose": "disabling the identifier after the organization-defined time period of inactivity." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing identifier management\n\nprocedures addressing account management\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of information system accounts\n\nlist of identifiers generated from physical access control devices\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with identifier management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing identifier management" - } - ] - } - ], - "controls": [ - { - "id": "ia-4.1", - "class": "SP800-53-enhancement", - "title": "Prohibit Account Identifiers as Public Identifiers", - "props": [ - { - "name": "label", - "value": "IA-4(1)" - }, - { - "name": "sort-id", - "value": "ia-04.01" - } - ], - "parts": [ - { - "id": "ia-4.1_smt", - "name": "statement", - "prose": "The organization prohibits the use of information system account identifiers that are the same as public identifiers for individual electronic mail accounts." - }, - { - "id": "ia-4.1_gdn", - "name": "guidance", - "prose": "Prohibiting the use of information systems account identifiers that are the same as some public identifier such as the individual identifier section of an electronic mail address, makes it more difficult for adversaries to guess user identifiers on organizational information systems.", - "links": [ - { - "href": "#at-2", - "rel": "related" - } - ] - }, - { - "id": "ia-4.1_obj", - "name": "objective", - "prose": "Determine if the organization prohibits the use of information system account identifiers that are the same as public identifiers for individual electronic mail accounts." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing identifier management\n\nprocedures addressing account management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with identifier management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing identifier management" - } - ] - } - ] - }, - { - "id": "ia-4.2", - "class": "SP800-53-enhancement", - "title": "Supervisor Authorization", - "props": [ - { - "name": "label", - "value": "IA-4(2)" - }, - { - "name": "sort-id", - "value": "ia-04.02" - } - ], - "parts": [ - { - "id": "ia-4.2_smt", - "name": "statement", - "prose": "The organization requires that the registration process to receive an individual identifier includes supervisor authorization." - }, - { - "id": "ia-4.2_obj", - "name": "objective", - "prose": "Determine if the organization requires that the registration process to receive an individual identifier includes supervisor authorization." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing identifier management\n\nprocedures addressing account management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with identifier management responsibilities\n\nsupervisors responsible for authorizing identifier registration\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing identifier management" - } - ] - } - ] - }, - { - "id": "ia-4.3", - "class": "SP800-53-enhancement", - "title": "Multiple Forms of Certification", - "props": [ - { - "name": "label", - "value": "IA-4(3)" - }, - { - "name": "sort-id", - "value": "ia-04.03" - } - ], - "parts": [ - { - "id": "ia-4.3_smt", - "name": "statement", - "prose": "The organization requires multiple forms of certification of individual identification be presented to the registration authority." - }, - { - "id": "ia-4.3_gdn", - "name": "guidance", - "prose": "Requiring multiple forms of identification, such as documentary evidence or a combination of documents and biometrics, reduces the likelihood of individuals using fraudulent identification to establish an identity, or at least increases the work factor of potential adversaries." - }, - { - "id": "ia-4.3_obj", - "name": "objective", - "prose": "Determine if the organization requires multiple forms of certification of individual identification such as documentary evidence or a combination of documents and biometrics be presented to the registration authority." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing identifier management\n\nprocedures addressing account management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with identifier management responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing identifier management" - } - ] - } - ] - }, - { - "id": "ia-4.4", - "class": "SP800-53-enhancement", - "title": "Identify User Status", - "params": [ - { - "id": "ia-4.4_prm_1", - "label": "organization-defined characteristic identifying individual status" - } - ], - "props": [ - { - "name": "label", - "value": "IA-4(4)" - }, - { - "name": "sort-id", - "value": "ia-04.04" - } - ], - "parts": [ - { - "id": "ia-4.4_smt", - "name": "statement", - "prose": "The organization manages individual identifiers by uniquely identifying each individual as {{ insert: param, ia-4.4_prm_1 }}." - }, - { - "id": "ia-4.4_gdn", - "name": "guidance", - "prose": "Characteristics identifying the status of individuals include, for example, contractors and foreign nationals. Identifying the status of individuals by specific characteristics provides additional information about the people with whom organizational personnel are communicating. For example, it might be useful for a government employee to know that one of the individuals on an email message is a contractor.", - "links": [ - { - "href": "#at-2", - "rel": "related" - } - ] - }, - { - "id": "ia-4.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ia-4.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(4)[1]" - } - ], - "prose": "defines a characteristic to be used to identify individual status; and" - }, - { - "id": "ia-4.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(4)[2]" - } - ], - "prose": "manages individual identifiers by uniquely identifying each individual as the organization-defined characteristic identifying individual status." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing identifier management\n\nprocedures addressing account management\n\nlist of characteristics identifying individual status\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with identifier management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing identifier management" - } - ] - } - ] - }, - { - "id": "ia-4.5", - "class": "SP800-53-enhancement", - "title": "Dynamic Management", - "props": [ - { - "name": "label", - "value": "IA-4(5)" - }, - { - "name": "sort-id", - "value": "ia-04.05" - } - ], - "parts": [ - { - "id": "ia-4.5_smt", - "name": "statement", - "prose": "The information system dynamically manages identifiers." - }, - { - "id": "ia-4.5_gdn", - "name": "guidance", - "prose": "In contrast to conventional approaches to identification which presume static accounts for preregistered users, many distributed information systems including, for example, service-oriented architectures, rely on establishing identifiers at run time for entities that were previously unknown. In these situations, organizations anticipate and provision for the dynamic establishment of identifiers. Preestablished trust relationships and mechanisms with appropriate authorities to validate identities and related credentials are essential.", - "links": [ - { - "href": "#ac-16", - "rel": "related" - } - ] - }, - { - "id": "ia-4.5_obj", - "name": "objective", - "prose": "Determine if the information system dynamically manages identifiers." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing identifier management\n\nprocedures addressing account management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with identifier management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing dynamic identifier management" - } - ] - } - ] - }, - { - "id": "ia-4.6", - "class": "SP800-53-enhancement", - "title": "Cross-organization Management", - "params": [ - { - "id": "ia-4.6_prm_1", - "label": "organization-defined external organizations" - } - ], - "props": [ - { - "name": "label", - "value": "IA-4(6)" - }, - { - "name": "sort-id", - "value": "ia-04.06" - } - ], - "parts": [ - { - "id": "ia-4.6_smt", - "name": "statement", - "prose": "The organization coordinates with {{ insert: param, ia-4.6_prm_1 }} for cross-organization management of identifiers." - }, - { - "id": "ia-4.6_gdn", - "name": "guidance", - "prose": "Cross-organization identifier management provides the capability for organizations to appropriately identify individuals, groups, roles, or devices when conducting cross-organization activities involving the processing, storage, or transmission of information." - }, - { - "id": "ia-4.6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ia-4.6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(6)[1]" - } - ], - "prose": "defines external organizations with whom to coordinate cross-organization management of identifiers; and" - }, - { - "id": "ia-4.6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-4(6)[2]" - } - ], - "prose": "coordinates with organization-defined external organizations for cross-organization management of identifiers." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing identifier management\n\nprocedures addressing account management\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with identifier management responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing identifier management" - } - ] - } - ] - }, - { - "id": "ia-4.7", - "class": "SP800-53-enhancement", - "title": "In-person Registration", - "props": [ - { - "name": "label", - "value": "IA-4(7)" - }, - { - "name": "sort-id", - "value": "ia-04.07" - } - ], - "parts": [ - { - "id": "ia-4.7_smt", - "name": "statement", - "prose": "The organization requires that the registration process to receive an individual identifier be conducted in person before a designated registration authority." - }, - { - "id": "ia-4.7_gdn", - "name": "guidance", - "prose": "In-person registration reduces the likelihood of fraudulent identifiers being issued because it requires the physical presence of individuals and actual face-to-face interactions with designated registration authorities." - }, - { - "id": "ia-4.7_obj", - "name": "objective", - "prose": "Determine if the organization requires that the registration process to receive an individual identifier be conducted in person before a designated registration authority." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing identifier management\n\nprocedures addressing account management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with identifier management responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "ia-5", - "class": "SP800-53", - "title": "Authenticator Management", - "params": [ - { - "id": "ia-5_prm_1", - "label": "organization-defined time period by authenticator type" - } - ], - "props": [ - { - "name": "label", - "value": "IA-5" - }, - { - "name": "sort-id", - "value": "ia-05" - } - ], - "links": [ - { - "href": "#ff3bfb02-79b2-411f-8735-98dfe5af2ab0", - "rel": "reference" - }, - { - "href": "#74e740a4-c45d-49f3-a86e-eb747c549e01", - "rel": "reference" - }, - { - "href": "#c80c10b3-1294-4984-a4cc-d1733ca432b9", - "rel": "reference" - }, - { - "href": "#ead74ea9-4c9c-446d-9b92-bcbf0ad4b655", - "rel": "reference" - }, - { - "href": "#644f44a9-a2de-4494-9c04-cd37fba45471", - "rel": "reference" - }, - { - "href": "#2a71298a-ee90-490e-80ff-48c967173a47", - "rel": "reference" - }, - { - "href": "#2042d97b-f7f6-4c74-84f8-981867684659", - "rel": "reference" - }, - { - "href": "#ba557c91-ba3e-4792-adc6-a4ae479b39ff", - "rel": "reference" - }, - { - "href": "#85280698-0417-489d-b214-12bb935fb939", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ia-5_smt", - "name": "statement", - "prose": "The organization manages information system authenticators by:", - "parts": [ - { - "id": "ia-5_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Verifying, as part of the initial authenticator distribution, the identity of the individual, group, role, or device receiving the authenticator;" - }, - { - "id": "ia-5_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Establishing initial authenticator content for authenticators defined by the organization;" - }, - { - "id": "ia-5_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Ensuring that authenticators have sufficient strength of mechanism for their intended use;" - }, - { - "id": "ia-5_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Establishing and implementing administrative procedures for initial authenticator distribution, for lost/compromised or damaged authenticators, and for revoking authenticators;" - }, - { - "id": "ia-5_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Changing default content of authenticators prior to information system installation;" - }, - { - "id": "ia-5_smt.f", - "name": "item", - "props": [ - { - "name": "label", - "value": "f." - } - ], - "prose": "Establishing minimum and maximum lifetime restrictions and reuse conditions for authenticators;" - }, - { - "id": "ia-5_smt.g", - "name": "item", - "props": [ - { - "name": "label", - "value": "g." - } - ], - "prose": "Changing/refreshing authenticators {{ insert: param, ia-5_prm_1 }};" - }, - { - "id": "ia-5_smt.h", - "name": "item", - "props": [ - { - "name": "label", - "value": "h." - } - ], - "prose": "Protecting authenticator content from unauthorized disclosure and modification;" - }, - { - "id": "ia-5_smt.i", - "name": "item", - "props": [ - { - "name": "label", - "value": "i." - } - ], - "prose": "Requiring individuals to take, and having devices implement, specific security safeguards to protect authenticators; and" - }, - { - "id": "ia-5_smt.j", - "name": "item", - "props": [ - { - "name": "label", - "value": "j." - } - ], - "prose": "Changing authenticators for group/role accounts when membership to those accounts changes." - } - ] - }, - { - "id": "ia-5_gdn", - "name": "guidance", - "prose": "Individual authenticators include, for example, passwords, tokens, biometrics, PKI certificates, and key cards. Initial authenticator content is the actual content (e.g., the initial password) as opposed to requirements about authenticator content (e.g., minimum password length). In many cases, developers ship information system components with factory default authentication credentials to allow for initial installation and configuration. Default authentication credentials are often well known, easily discoverable, and present a significant security risk. The requirement to protect individual authenticators may be implemented via control PL-4 or PS-6 for authenticators in the possession of individuals and by controls AC-3, AC-6, and SC-28 for authenticators stored within organizational information systems (e.g., passwords stored in hashed or encrypted formats, files containing encrypted or hashed passwords accessible with administrator privileges). Information systems support individual authenticator management by organization-defined settings and restrictions for various authenticator characteristics including, for example, minimum password length, password composition, validation time window for time synchronous one-time tokens, and number of allowed rejections during the verification stage of biometric authentication. Specific actions that can be taken to safeguard authenticators include, for example, maintaining possession of individual authenticators, not loaning or sharing individual authenticators with others, and reporting lost, stolen, or compromised authenticators immediately. Authenticator management includes issuing and revoking, when no longer needed, authenticators for temporary access such as that required for remote maintenance. Device authenticators include, for example, certificates and passwords.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#ps-5", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#sc-17", - "rel": "related" - }, - { - "href": "#sc-28", - "rel": "related" - } - ] - }, - { - "id": "ia-5_obj", - "name": "objective", - "prose": "Determine if the organization manages information system authenticators by:", - "parts": [ - { - "id": "ia-5.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(a)" - } - ], - "prose": "verifying, as part of the initial authenticator distribution, the identity of:", - "parts": [ - { - "id": "ia-5.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(a)[1]" - } - ], - "prose": "the individual receiving the authenticator;" - }, - { - "id": "ia-5.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(a)[2]" - } - ], - "prose": "the group receiving the authenticator;" - }, - { - "id": "ia-5.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(a)[3]" - } - ], - "prose": "the role receiving the authenticator; and/or" - }, - { - "id": "ia-5.a_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(a)[4]" - } - ], - "prose": "the device receiving the authenticator;" - } - ] - }, - { - "id": "ia-5.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(b)" - } - ], - "prose": "establishing initial authenticator content for authenticators defined by the organization;" - }, - { - "id": "ia-5.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(c)" - } - ], - "prose": "ensuring that authenticators have sufficient strength of mechanism for their intended use;" - }, - { - "id": "ia-5.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(d)" - } - ], - "parts": [ - { - "id": "ia-5.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(d)[1]" - } - ], - "prose": "establishing and implementing administrative procedures for initial authenticator distribution;" - }, - { - "id": "ia-5.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(d)[2]" - } - ], - "prose": "establishing and implementing administrative procedures for lost/compromised or damaged authenticators;" - }, - { - "id": "ia-5.d_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(d)[3]" - } - ], - "prose": "establishing and implementing administrative procedures for revoking authenticators;" - } - ] - }, - { - "id": "ia-5.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(e)" - } - ], - "prose": "changing default content of authenticators prior to information system installation;" - }, - { - "id": "ia-5.f_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(f)" - } - ], - "parts": [ - { - "id": "ia-5.f_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(f)[1]" - } - ], - "prose": "establishing minimum lifetime restrictions for authenticators;" - }, - { - "id": "ia-5.f_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(f)[2]" - } - ], - "prose": "establishing maximum lifetime restrictions for authenticators;" - }, - { - "id": "ia-5.f_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(f)[3]" - } - ], - "prose": "establishing reuse conditions for authenticators;" - } - ] - }, - { - "id": "ia-5.g_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(g)" - } - ], - "parts": [ - { - "id": "ia-5.g_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(g)[1]" - } - ], - "prose": "defining a time period (by authenticator type) for changing/refreshing authenticators;" - }, - { - "id": "ia-5.g_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(g)[2]" - } - ], - "prose": "changing/refreshing authenticators with the organization-defined time period by authenticator type;" - } - ] - }, - { - "id": "ia-5.h_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(h)" - } - ], - "prose": "protecting authenticator content from unauthorized:", - "parts": [ - { - "id": "ia-5.h_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(h)[1]" - } - ], - "prose": "disclosure;" - }, - { - "id": "ia-5.h_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(h)[2]" - } - ], - "prose": "modification;" - } - ] - }, - { - "id": "ia-5.i_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(i)" - } - ], - "parts": [ - { - "id": "ia-5.i_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(i)[1]" - } - ], - "prose": "requiring individuals to take specific security safeguards to protect authenticators;" - }, - { - "id": "ia-5.i_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(i)[2]" - } - ], - "prose": "having devices implement specific security safeguards to protect authenticators; and" - } - ] - }, - { - "id": "ia-5.j_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(j)" - } - ], - "prose": "changing authenticators for group/role accounts when membership to those accounts changes." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing authenticator management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of information system authenticator types\n\nchange control records associated with managing information system authenticators\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with authenticator management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing authenticator management capability" - } - ] - } - ], - "controls": [ - { - "id": "ia-5.1", - "class": "SP800-53-enhancement", - "title": "Password-based Authentication", - "params": [ - { - "id": "ia-5.1_prm_1", - "label": "organization-defined requirements for case sensitivity, number of characters, mix of upper-case letters, lower-case letters, numbers, and special characters, including minimum requirements for each type" - }, - { - "id": "ia-5.1_prm_2", - "label": "organization-defined number" - }, - { - "id": "ia-5.1_prm_3", - "label": "organization-defined numbers for lifetime minimum, lifetime maximum" - }, - { - "id": "ia-5.1_prm_4", - "label": "organization-defined number" - } - ], - "props": [ - { - "name": "label", - "value": "IA-5(1)" - }, - { - "name": "sort-id", - "value": "ia-05.01" - } - ], - "parts": [ - { - "id": "ia-5.1_smt", - "name": "statement", - "prose": "The information system, for password-based authentication:", - "parts": [ - { - "id": "ia-5.1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Enforces minimum password complexity of {{ insert: param, ia-5.1_prm_1 }};" - }, - { - "id": "ia-5.1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Enforces at least the following number of changed characters when new passwords are created: {{ insert: param, ia-5.1_prm_2 }};" - }, - { - "id": "ia-5.1_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Stores and transmits only cryptographically-protected passwords;" - }, - { - "id": "ia-5.1_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "(d)" - } - ], - "prose": "Enforces password minimum and maximum lifetime restrictions of {{ insert: param, ia-5.1_prm_3 }};" - }, - { - "id": "ia-5.1_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "(e)" - } - ], - "prose": "Prohibits password reuse for {{ insert: param, ia-5.1_prm_4 }} generations; and" - }, - { - "id": "ia-5.1_smt.f", - "name": "item", - "props": [ - { - "name": "label", - "value": "(f)" - } - ], - "prose": "Allows the use of a temporary password for system logons with an immediate change to a permanent password." - } - ] - }, - { - "id": "ia-5.1_gdn", - "name": "guidance", - "prose": "This control enhancement applies to single-factor authentication of individuals using passwords as individual or group authenticators, and in a similar manner, when passwords are part of multifactor authenticators. This control enhancement does not apply when passwords are used to unlock hardware authenticators (e.g., Personal Identity Verification cards). The implementation of such password mechanisms may not meet all of the requirements in the enhancement. Cryptographically-protected passwords include, for example, encrypted versions of passwords and one-way cryptographic hashes of passwords. The number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. Password lifetime restrictions do not apply to temporary passwords. To mitigate certain brute force attacks against passwords, organizations may also consider salting passwords.", - "links": [ - { - "href": "#ia-6", - "rel": "related" - } - ] - }, - { - "id": "ia-5.1_obj", - "name": "objective", - "prose": "Determine if, for password-based authentication:", - "parts": [ - { - "id": "ia-5.1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(1)(a)" - } - ], - "parts": [ - { - "id": "ia-5.1.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(1)(a)[1]" - } - ], - "prose": "the organization defines requirements for case sensitivity;" - }, - { - "id": "ia-5.1.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(1)(a)[2]" - } - ], - "prose": "the organization defines requirements for number of characters;" - }, - { - "id": "ia-5.1.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(1)(a)[3]" - } - ], - "prose": "the organization defines requirements for the mix of upper-case letters, lower-case letters, numbers and special characters;" - }, - { - "id": "ia-5.1.a_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(1)(a)[4]" - } - ], - "prose": "the organization defines minimum requirements for each type of character;" - }, - { - "id": "ia-5.1.a_obj.5", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(1)(a)[5]" - } - ], - "prose": "the information system enforces minimum password complexity of organization-defined requirements for case sensitivity, number of characters, mix of upper-case letters, lower-case letters, numbers, and special characters, including minimum requirements for each type;" - } - ], - "links": [ - { - "href": "#ia-5.1_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ia-5.1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(1)(b)" - } - ], - "parts": [ - { - "id": "ia-5.1.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(1)(b)[1]" - } - ], - "prose": "the organization defines a minimum number of changed characters to be enforced when new passwords are created;" - }, - { - "id": "ia-5.1.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(1)(b)[2]" - } - ], - "prose": "the information system enforces at least the organization-defined minimum number of characters that must be changed when new passwords are created;" - } - ], - "links": [ - { - "href": "#ia-5.1_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "ia-5.1.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(1)(c)" - } - ], - "prose": "the information system stores and transmits only encrypted representations of passwords;", - "links": [ - { - "href": "#ia-5.1_smt.c", - "rel": "corresp" - } - ] - }, - { - "id": "ia-5.1.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(1)(d)" - } - ], - "parts": [ - { - "id": "ia-5.1.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(1)(d)[1]" - } - ], - "prose": "the organization defines numbers for password minimum lifetime restrictions to be enforced for passwords;" - }, - { - "id": "ia-5.1.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(1)(d)[2]" - } - ], - "prose": "the organization defines numbers for password maximum lifetime restrictions to be enforced for passwords;" - }, - { - "id": "ia-5.1.d_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(1)(d)[3]" - } - ], - "prose": "the information system enforces password minimum lifetime restrictions of organization-defined numbers for lifetime minimum;" - }, - { - "id": "ia-5.1.d_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(1)(d)[4]" - } - ], - "prose": "the information system enforces password maximum lifetime restrictions of organization-defined numbers for lifetime maximum;" - } - ], - "links": [ - { - "href": "#ia-5.1_smt.d", - "rel": "corresp" - } - ] - }, - { - "id": "ia-5.1.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(1)(e)" - } - ], - "parts": [ - { - "id": "ia-5.1.e_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(1)(e)[1]" - } - ], - "prose": "the organization defines the number of password generations to be prohibited from password reuse;" - }, - { - "id": "ia-5.1.e_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(1)(e)[2]" - } - ], - "prose": "the information system prohibits password reuse for the organization-defined number of generations; and" - } - ], - "links": [ - { - "href": "#ia-5.1_smt.e", - "rel": "corresp" - } - ] - }, - { - "id": "ia-5.1.f_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(1)(f)" - } - ], - "prose": "the information system allows the use of a temporary password for system logons with an immediate change to a permanent password.", - "links": [ - { - "href": "#ia-5.1_smt.f", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\npassword policy\n\nprocedures addressing authenticator management\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\npassword configurations and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with authenticator management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing password-based authenticator management capability" - } - ] - } - ] - }, - { - "id": "ia-5.2", - "class": "SP800-53-enhancement", - "title": "Pki-based Authentication", - "props": [ - { - "name": "label", - "value": "IA-5(2)" - }, - { - "name": "sort-id", - "value": "ia-05.02" - } - ], - "parts": [ - { - "id": "ia-5.2_smt", - "name": "statement", - "prose": "The information system, for PKI-based authentication:", - "parts": [ - { - "id": "ia-5.2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Validates certifications by constructing and verifying a certification path to an accepted trust anchor including checking certificate status information;" - }, - { - "id": "ia-5.2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Enforces authorized access to the corresponding private key;" - }, - { - "id": "ia-5.2_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Maps the authenticated identity to the account of the individual or group; and" - }, - { - "id": "ia-5.2_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "(d)" - } - ], - "prose": "Implements a local cache of revocation data to support path discovery and validation in case of inability to access revocation information via the network." - } - ] - }, - { - "id": "ia-5.2_gdn", - "name": "guidance", - "prose": "Status information for certification paths includes, for example, certificate revocation lists or certificate status protocol responses. For PIV cards, validation of certifications involves the construction and verification of a certification path to the Common Policy Root trust anchor including certificate policy processing.", - "links": [ - { - "href": "#ia-6", - "rel": "related" - } - ] - }, - { - "id": "ia-5.2_obj", - "name": "objective", - "prose": "Determine if the information system, for PKI-based authentication:", - "parts": [ - { - "id": "ia-5.2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(2)(a)" - } - ], - "parts": [ - { - "id": "ia-5.2.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(2)(a)[1]" - } - ], - "prose": "validates certifications by constructing a certification path to an accepted trust anchor;" - }, - { - "id": "ia-5.2.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(2)(a)[2]" - } - ], - "prose": "validates certifications by verifying a certification path to an accepted trust anchor;" - }, - { - "id": "ia-5.2.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(2)(a)[3]" - } - ], - "prose": "includes checking certificate status information when constructing and verifying the certification path;" - } - ], - "links": [ - { - "href": "#ia-5.2_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ia-5.2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(2)(b)" - } - ], - "prose": "enforces authorized access to the corresponding private key;", - "links": [ - { - "href": "#ia-5.2_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "ia-5.2.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(2)(c)" - } - ], - "prose": "maps the authenticated identity to the account of the individual or group; and", - "links": [ - { - "href": "#ia-5.2_smt.c", - "rel": "corresp" - } - ] - }, - { - "id": "ia-5.2.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(2)(d)" - } - ], - "prose": "implements a local cache of revocation data to support path discovery and validation in case of inability to access revocation information via the network.", - "links": [ - { - "href": "#ia-5.2_smt.d", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing authenticator management\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nPKI certification validation records\n\nPKI certification revocation lists\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with PKI-based, authenticator management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing PKI-based, authenticator management capability" - } - ] - } - ] - }, - { - "id": "ia-5.3", - "class": "SP800-53-enhancement", - "title": "In-person or Trusted Third-party Registration", - "params": [ - { - "id": "ia-5.3_prm_1", - "label": "organization-defined types of and/or specific authenticators" - }, - { - "id": "ia-5.3_prm_2", - "select": { - "choice": [ - "in person", - "by a trusted third party" - ] - } - }, - { - "id": "ia-5.3_prm_3", - "label": "organization-defined registration authority" - }, - { - "id": "ia-5.3_prm_4", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "IA-5(3)" - }, - { - "name": "sort-id", - "value": "ia-05.03" - } - ], - "parts": [ - { - "id": "ia-5.3_smt", - "name": "statement", - "prose": "The organization requires that the registration process to receive {{ insert: param, ia-5.3_prm_1 }} be conducted {{ insert: param, ia-5.3_prm_2 }} before {{ insert: param, ia-5.3_prm_3 }} with authorization by {{ insert: param, ia-5.3_prm_4 }}." - }, - { - "id": "ia-5.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ia-5.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(3)[1]" - } - ], - "prose": "defines types of and/or specific authenticators to be received in person or by a trusted third party;" - }, - { - "id": "ia-5.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(3)[2]" - } - ], - "prose": "defines the registration authority with oversight of the registration process for receipt of organization-defined types of and/or specific authenticators;" - }, - { - "id": "ia-5.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(3)[3]" - } - ], - "prose": "defines personnel or roles responsible for authorizing organization-defined registration authority;" - }, - { - "id": "ia-5.3_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(3)[4]" - } - ], - "prose": "defines if the registration process is to be conducted:", - "parts": [ - { - "id": "ia-5.3_obj.4.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(3)[4][a]" - } - ], - "prose": "in person; or" - }, - { - "id": "ia-5.3_obj.4.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(3)[4][b]" - } - ], - "prose": "by a trusted third party; and" - } - ] - }, - { - "id": "ia-5.3_obj.5", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(3)[5]" - } - ], - "prose": "requires that the registration process to receive organization-defined types of and/or specific authenticators be conducted in person or by a trusted third party before organization-defined registration authority with authorization by organization-defined personnel or roles." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing authenticator management\n\nregistration process for receiving information system authenticators\n\nlist of authenticators requiring in-person registration\n\nlist of authenticators requiring trusted third party registration\n\nauthenticator registration documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with authenticator management responsibilities\n\nregistration authority\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "ia-5.4", - "class": "SP800-53-enhancement", - "title": "Automated Support for Password Strength Determination", - "params": [ - { - "id": "ia-5.4_prm_1", - "label": "organization-defined requirements" - } - ], - "props": [ - { - "name": "label", - "value": "IA-5(4)" - }, - { - "name": "sort-id", - "value": "ia-05.04" - } - ], - "parts": [ - { - "id": "ia-5.4_smt", - "name": "statement", - "prose": "The organization employs automated tools to determine if password authenticators are sufficiently strong to satisfy {{ insert: param, ia-5.4_prm_1 }}." - }, - { - "id": "ia-5.4_gdn", - "name": "guidance", - "prose": "This control enhancement focuses on the creation of strong passwords and the characteristics of such passwords (e.g., complexity) prior to use, the enforcement of which is carried out by organizational information systems in IA-5 (1).", - "links": [ - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - } - ] - }, - { - "id": "ia-5.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ia-5.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(4)[1]" - } - ], - "prose": "defines requirements to be satisfied by password authenticators; and" - }, - { - "id": "ia-5.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(4)[2]" - } - ], - "prose": "employs automated tools to determine if password authenticators are sufficiently strong to satisfy organization-defined requirements." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing authenticator management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nautomated tools for evaluating password authenticators\n\npassword strength assessment results\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with authenticator management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing password-based authenticator management capability\n\nautomated tools for determining password strength" - } - ] - } - ] - }, - { - "id": "ia-5.5", - "class": "SP800-53-enhancement", - "title": "Change Authenticators Prior to Delivery", - "props": [ - { - "name": "label", - "value": "IA-5(5)" - }, - { - "name": "sort-id", - "value": "ia-05.05" - } - ], - "parts": [ - { - "id": "ia-5.5_smt", - "name": "statement", - "prose": "The organization requires developers/installers of information system components to provide unique authenticators or change default authenticators prior to delivery/installation." - }, - { - "id": "ia-5.5_gdn", - "name": "guidance", - "prose": "This control enhancement extends the requirement for organizations to change default authenticators upon information system installation, by requiring developers and/or installers to provide unique authenticators or change default authenticators for system components prior to delivery and/or installation. However, it typically does not apply to the developers of commercial off-the-shelve information technology products. Requirements for unique authenticators can be included in acquisition documents prepared by organizations when procuring information systems or system components." - }, - { - "id": "ia-5.5_obj", - "name": "objective", - "prose": "Determine if the organization requires developers/installers of information system components to:", - "parts": [ - { - "id": "ia-5.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(5)[1]" - } - ], - "prose": "provide unique authenticators prior to delivery/installation; or" - }, - { - "id": "ia-5.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(5)[2]" - } - ], - "prose": "change default authenticators prior to delivery/installation." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nsystem and services acquisition policy\n\nprocedures addressing authenticator management\n\nprocedures addressing the integration of security requirements into the acquisition process\n\nacquisition documentation\n\nacquisition contracts for information system procurements or services\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with authenticator management responsibilities\n\norganizational personnel with information system security, acquisition, and contracting responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing authenticator management capability" - } - ] - } - ] - }, - { - "id": "ia-5.6", - "class": "SP800-53-enhancement", - "title": "Protection of Authenticators", - "props": [ - { - "name": "label", - "value": "IA-5(6)" - }, - { - "name": "sort-id", - "value": "ia-05.06" - } - ], - "parts": [ - { - "id": "ia-5.6_smt", - "name": "statement", - "prose": "The organization protects authenticators commensurate with the security category of the information to which use of the authenticator permits access." - }, - { - "id": "ia-5.6_gdn", - "name": "guidance", - "prose": "For information systems containing multiple security categories of information without reliable physical or logical separation between categories, authenticators used to grant access to the systems are protected commensurate with the highest security category of information on the systems." - }, - { - "id": "ia-5.6_obj", - "name": "objective", - "prose": "Determine if the organization protects authenticators commensurate with the security category of the information to which use of the authenticator permits access." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing authenticator management\n\nsecurity categorization documentation for the information system\n\nsecurity assessments of authenticator protections\n\nrisk assessment results\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with authenticator management responsibilities\n\norganizational personnel implementing and/or maintaining authenticator protections\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing authenticator management capability\n\nautomated mechanisms protecting authenticators" - } - ] - } - ] - }, - { - "id": "ia-5.7", - "class": "SP800-53-enhancement", - "title": "No Embedded Unencrypted Static Authenticators", - "props": [ - { - "name": "label", - "value": "IA-5(7)" - }, - { - "name": "sort-id", - "value": "ia-05.07" - } - ], - "parts": [ - { - "id": "ia-5.7_smt", - "name": "statement", - "prose": "The organization ensures that unencrypted static authenticators are not embedded in applications or access scripts or stored on function keys." - }, - { - "id": "ia-5.7_gdn", - "name": "guidance", - "prose": "Organizations exercise caution in determining whether embedded or stored authenticators are in encrypted or unencrypted form. If authenticators are used in the manner stored, then those representations are considered unencrypted authenticators. This is irrespective of whether that representation is perhaps an encrypted version of something else (e.g., a password)." - }, - { - "id": "ia-5.7_obj", - "name": "objective", - "prose": "Determine if the organization ensures that unencrypted static authenticators are not:", - "parts": [ - { - "id": "ia-5.7_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(7)[1]" - } - ], - "prose": "embedded in applications;" - }, - { - "id": "ia-5.7_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(7)[2]" - } - ], - "prose": "embedded in access scripts; or" - }, - { - "id": "ia-5.7_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(7)[3]" - } - ], - "prose": "stored on function keys." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing authenticator management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlogical access scripts\n\napplication code reviews for detecting unencrypted static authenticators\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with authenticator management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing authenticator management capability\n\nautomated mechanisms implementing authentication in applications" - } - ] - } - ] - }, - { - "id": "ia-5.8", - "class": "SP800-53-enhancement", - "title": "Multiple Information System Accounts", - "params": [ - { - "id": "ia-5.8_prm_1", - "label": "organization-defined security safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "IA-5(8)" - }, - { - "name": "sort-id", - "value": "ia-05.08" - } - ], - "parts": [ - { - "id": "ia-5.8_smt", - "name": "statement", - "prose": "The organization implements {{ insert: param, ia-5.8_prm_1 }} to manage the risk of compromise due to individuals having accounts on multiple information systems." - }, - { - "id": "ia-5.8_gdn", - "name": "guidance", - "prose": "When individuals have accounts on multiple information systems, there is the risk that the compromise of one account may lead to the compromise of other accounts if individuals use the same authenticators. Possible alternatives include, for example: (i) having different authenticators on all systems; (ii) employing some form of single sign-on mechanism; or (iii) including some form of one-time passwords on all systems." - }, - { - "id": "ia-5.8_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ia-5.8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(8)[1]" - } - ], - "prose": "defines security safeguards to manage the risk of compromise due to individuals having accounts on multiple information systems; and" - }, - { - "id": "ia-5.8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(8)[2]" - } - ], - "prose": "implements organization-defined security safeguards to manage the risk of compromise due to individuals having accounts on multiple information systems." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing authenticator management\n\nsecurity plan\n\nlist of individuals having accounts on multiple information systems\n\nlist of security safeguards intended to manage risk of compromise due to individuals having accounts on multiple information systems\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with authenticator management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing safeguards for authenticator management" - } - ] - } - ] - }, - { - "id": "ia-5.9", - "class": "SP800-53-enhancement", - "title": "Cross-organization Credential Management", - "params": [ - { - "id": "ia-5.9_prm_1", - "label": "organization-defined external organizations" - } - ], - "props": [ - { - "name": "label", - "value": "IA-5(9)" - }, - { - "name": "sort-id", - "value": "ia-05.09" - } - ], - "parts": [ - { - "id": "ia-5.9_smt", - "name": "statement", - "prose": "The organization coordinates with {{ insert: param, ia-5.9_prm_1 }} for cross-organization management of credentials." - }, - { - "id": "ia-5.9_gdn", - "name": "guidance", - "prose": "Cross-organization management of credentials provides the capability for organizations to appropriately authenticate individuals, groups, roles, or devices when conducting cross-organization activities involving the processing, storage, or transmission of information." - }, - { - "id": "ia-5.9_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ia-5.9_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(9)[1]" - } - ], - "prose": "defines external organizations with whom to coordinate cross-organizational management of credentials; and" - }, - { - "id": "ia-5.9_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(9)[2]" - } - ], - "prose": "coordinates with organization-defined external organizations for cross-organizational management of credentials." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing authenticator management\n\nprocedures addressing account management\n\nsecurity plan\n\ninformation security agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with authenticator management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing safeguards for authenticator management" - } - ] - } - ] - }, - { - "id": "ia-5.10", - "class": "SP800-53-enhancement", - "title": "Dynamic Credential Association", - "props": [ - { - "name": "label", - "value": "IA-5(10)" - }, - { - "name": "sort-id", - "value": "ia-05.10" - } - ], - "parts": [ - { - "id": "ia-5.10_smt", - "name": "statement", - "prose": "The information system dynamically provisions identities." - }, - { - "id": "ia-5.10_gdn", - "name": "guidance", - "prose": "Authentication requires some form of binding between an identity and the authenticator used to confirm the identity. In conventional approaches, this binding is established by pre-provisioning both the identity and the authenticator to the information system. For example, the binding between a username (i.e., identity) and a password (i.e., authenticator) is accomplished by provisioning the identity and authenticator as a pair in the information system. New authentication techniques allow the binding between the identity and the authenticator to be implemented outside an information system. For example, with smartcard credentials, the identity and the authenticator are bound together on the card. Using these credentials, information systems can authenticate identities that have not been pre-provisioned, dynamically provisioning the identity after authentication. In these situations, organizations can anticipate the dynamic provisioning of identities. Preestablished trust relationships and mechanisms with appropriate authorities to validate identities and related credentials are essential." - }, - { - "id": "ia-5.10_obj", - "name": "objective", - "prose": "Determine if the information system dynamically provisions identifiers." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing identifier management\n\nsecurity plan\n\ninformation system design documentation\n\nautomated mechanisms providing dynamic binding of identifiers and authenticators\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with identifier management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing identifier management capability\n\nautomated mechanisms implementing dynamic provisioning of identifiers" - } - ] - } - ] - }, - { - "id": "ia-5.11", - "class": "SP800-53-enhancement", - "title": "Hardware Token-based Authentication", - "params": [ - { - "id": "ia-5.11_prm_1", - "label": "organization-defined token quality requirements" - } - ], - "props": [ - { - "name": "label", - "value": "IA-5(11)" - }, - { - "name": "sort-id", - "value": "ia-05.11" - } - ], - "parts": [ - { - "id": "ia-5.11_smt", - "name": "statement", - "prose": "The information system, for hardware token-based authentication, employs mechanisms that satisfy {{ insert: param, ia-5.11_prm_1 }}." - }, - { - "id": "ia-5.11_gdn", - "name": "guidance", - "prose": "Hardware token-based authentication typically refers to the use of PKI-based tokens, such as the U.S. Government Personal Identity Verification (PIV) card. Organizations define specific requirements for tokens, such as working with a particular PKI." - }, - { - "id": "ia-5.11_obj", - "name": "objective", - "prose": "Determine if, for hardware token-based authentication:", - "parts": [ - { - "id": "ia-5.11_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(11)[1]" - } - ], - "prose": "the organization defines token quality requirements to be satisfied; and" - }, - { - "id": "ia-5.11_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(11)[2]" - } - ], - "prose": "the information system employs mechanisms that satisfy organization-defined token quality requirements." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing authenticator management\n\nsecurity plan\n\ninformation system design documentation\n\nautomated mechanisms employing hardware token-based authentication for the information system\n\nlist of token quality requirements\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with authenticator management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing hardware token-based authenticator management capability" - } - ] - } - ] - }, - { - "id": "ia-5.12", - "class": "SP800-53-enhancement", - "title": "Biometric-based Authentication", - "params": [ - { - "id": "ia-5.12_prm_1", - "label": "organization-defined biometric quality requirements" - } - ], - "props": [ - { - "name": "label", - "value": "IA-5(12)" - }, - { - "name": "sort-id", - "value": "ia-05.12" - } - ], - "parts": [ - { - "id": "ia-5.12_smt", - "name": "statement", - "prose": "The information system, for biometric-based authentication, employs mechanisms that satisfy {{ insert: param, ia-5.12_prm_1 }}." - }, - { - "id": "ia-5.12_gdn", - "name": "guidance", - "prose": "Unlike password-based authentication which provides exact matches of user-input passwords to stored passwords, biometric authentication does not provide such exact matches. Depending upon the type of biometric and the type of collection mechanism, there is likely to be some divergence from the presented biometric and stored biometric which serves as the basis of comparison. There will likely be both false positives and false negatives when making such comparisons. The rate at which the false accept and false reject rates are equal is known as the crossover rate. Biometric quality requirements include, for example, acceptable crossover rates, as that essentially reflects the accuracy of the biometric." - }, - { - "id": "ia-5.12_obj", - "name": "objective", - "prose": "Determine if, for biometric-based authentication:", - "parts": [ - { - "id": "ia-5.12_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(12)[1]" - } - ], - "prose": "the organization defines biometric quality requirements to be satisfied; and" - }, - { - "id": "ia-5.12_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(12)[2]" - } - ], - "prose": "the information system employs mechanisms that satisfy organization-defined biometric quality requirements." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing authenticator management\n\nsecurity plan\n\ninformation system design documentation\n\nautomated mechanisms employing biometric-based authentication for the information system\n\nlist of biometric quality requirements\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with authenticator management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing biometric-based authenticator management capability" - } - ] - } - ] - }, - { - "id": "ia-5.13", - "class": "SP800-53-enhancement", - "title": "Expiration of Cached Authenticators", - "params": [ - { - "id": "ia-5.13_prm_1", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "IA-5(13)" - }, - { - "name": "sort-id", - "value": "ia-05.13" - } - ], - "parts": [ - { - "id": "ia-5.13_smt", - "name": "statement", - "prose": "The information system prohibits the use of cached authenticators after {{ insert: param, ia-5.13_prm_1 }}." - }, - { - "id": "ia-5.13_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ia-5.13_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(13)[1]" - } - ], - "prose": "the organization defines the time period after which the information system is to prohibit the use of cached authenticators; and" - }, - { - "id": "ia-5.13_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(13)[2]" - } - ], - "prose": "the information system prohibits the use of cached authenticators after the organization-defined time period." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing authenticator management\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with authenticator management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing authenticator management capability" - } - ] - } - ] - }, - { - "id": "ia-5.14", - "class": "SP800-53-enhancement", - "title": "Managing Content of PKI Trust Stores", - "props": [ - { - "name": "label", - "value": "IA-5(14)" - }, - { - "name": "sort-id", - "value": "ia-05.14" - } - ], - "parts": [ - { - "id": "ia-5.14_smt", - "name": "statement", - "prose": "The organization, for PKI-based authentication, employs a deliberate organization-wide methodology for managing the content of PKI trust stores installed across all platforms including networks, operating systems, browsers, and applications." - }, - { - "id": "ia-5.14_obj", - "name": "objective", - "prose": "Determine if the organization, for PKI-based authentication, employs a deliberate organization-wide methodology for managing the content of PKI trust stores installed across all platforms including:", - "parts": [ - { - "id": "ia-5.14_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(14)[1]" - } - ], - "prose": "networks;" - }, - { - "id": "ia-5.14_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(14)[2]" - } - ], - "prose": "operating systems;" - }, - { - "id": "ia-5.14_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(14)[3]" - } - ], - "prose": "browsers; and" - }, - { - "id": "ia-5.14_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-5(14)[4]" - } - ], - "prose": "applications." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing authenticator management\n\nsecurity plan\n\norganizational methodology for managing content of PKI trust stores across installed all platforms\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nenterprise security architecture documentation\n\nenterprise architecture documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with authenticator management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing PKI-based authenticator management capability\n\nautomated mechanisms supporting and/or implementing the PKI trust store capability" - } - ] - } - ] - }, - { - "id": "ia-5.15", - "class": "SP800-53-enhancement", - "title": "Ficam-approved Products and Services", - "props": [ - { - "name": "label", - "value": "IA-5(15)" - }, - { - "name": "sort-id", - "value": "ia-05.15" - } - ], - "parts": [ - { - "id": "ia-5.15_smt", - "name": "statement", - "prose": "The organization uses only FICAM-approved path discovery and validation products and services." - }, - { - "id": "ia-5.15_gdn", - "name": "guidance", - "prose": "Federal Identity, Credential, and Access Management (FICAM)-approved path discovery and validation products and services are those products and services that have been approved through the FICAM conformance program, where applicable." - }, - { - "id": "ia-5.15_obj", - "name": "objective", - "prose": "Determine if the organization uses only FICAM-approved path discovery and validation products and services." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing identifier management\n\nsecurity plan\n\ninformation system design documentation\n\nautomated mechanisms providing dynamic binding of identifiers and authenticators\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with identification and authentication management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing account management capability\n\nautomated mechanisms supporting and/or implementing identification and authentication management capability for the information system" - } - ] - } - ] - } - ] - }, - { - "id": "ia-6", - "class": "SP800-53", - "title": "Authenticator Feedback", - "props": [ - { - "name": "label", - "value": "IA-6" - }, - { - "name": "sort-id", - "value": "ia-06" - } - ], - "parts": [ - { - "id": "ia-6_smt", - "name": "statement", - "prose": "The information system obscures feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals." - }, - { - "id": "ia-6_gdn", - "name": "guidance", - "prose": "The feedback from information systems does not provide information that would allow unauthorized individuals to compromise authentication mechanisms. For some types of information systems or system components, for example, desktops/notebooks with relatively large monitors, the threat (often referred to as shoulder surfing) may be significant. For other types of systems or components, for example, mobile devices with 2-4 inch screens, this threat may be less significant, and may need to be balanced against the increased likelihood of typographic input errors due to the small keyboards. Therefore, the means for obscuring the authenticator feedback is selected accordingly. Obscuring the feedback of authentication information includes, for example, displaying asterisks when users type passwords into input devices, or displaying feedback for a very limited time before fully obscuring it.", - "links": [ - { - "href": "#pe-18", - "rel": "related" - } - ] - }, - { - "id": "ia-6_obj", - "name": "objective", - "prose": "Determine if the information system obscures feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing authenticator feedback\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing the obscuring of feedback of authentication information during authentication" - } - ] - } - ] - }, - { - "id": "ia-7", - "class": "SP800-53", - "title": "Cryptographic Module Authentication", - "props": [ - { - "name": "label", - "value": "IA-7" - }, - { - "name": "sort-id", - "value": "ia-07" - } - ], - "links": [ - { - "href": "#39f9087d-7687-46d2-8eda-b6f4b7a4d8a9", - "rel": "reference" - }, - { - "href": "#b09d1a31-d3c9-4138-a4f4-4c63816afd7d", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ia-7_smt", - "name": "statement", - "prose": "The information system implements mechanisms for authentication to a cryptographic module that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for such authentication." - }, - { - "id": "ia-7_gdn", - "name": "guidance", - "prose": "Authentication mechanisms may be required within a cryptographic module to authenticate an operator accessing the module and to verify that the operator is authorized to assume the requested role and perform services within that role.", - "links": [ - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "ia-7_obj", - "name": "objective", - "prose": "Determine if the information system implements mechanisms for authentication to a cryptographic module that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for such authentication." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing cryptographic module authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for cryptographic module authentication\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing cryptographic module authentication" - } - ] - } - ] - }, - { - "id": "ia-8", - "class": "SP800-53", - "title": "Identification and Authentication (non-organizational Users)", - "props": [ - { - "name": "label", - "value": "IA-8" - }, - { - "name": "sort-id", - "value": "ia-08" - } - ], - "links": [ - { - "href": "#ff3bfb02-79b2-411f-8735-98dfe5af2ab0", - "rel": "reference" - }, - { - "href": "#74e740a4-c45d-49f3-a86e-eb747c549e01", - "rel": "reference" - }, - { - "href": "#599fe9ba-4750-4450-9eeb-b95bd19a5e8f", - "rel": "reference" - }, - { - "href": "#ba557c91-ba3e-4792-adc6-a4ae479b39ff", - "rel": "reference" - }, - { - "href": "#c80c10b3-1294-4984-a4cc-d1733ca432b9", - "rel": "reference" - }, - { - "href": "#644f44a9-a2de-4494-9c04-cd37fba45471", - "rel": "reference" - }, - { - "href": "#2157bb7e-192c-4eaa-877f-93ef6b0a3292", - "rel": "reference" - }, - { - "href": "#654f21e2-f3bc-43b2-abdc-60ab8d09744b", - "rel": "reference" - }, - { - "href": "#85280698-0417-489d-b214-12bb935fb939", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ia-8_smt", - "name": "statement", - "prose": "The information system uniquely identifies and authenticates non-organizational users (or processes acting on behalf of non-organizational users)." - }, - { - "id": "ia-8_gdn", - "name": "guidance", - "prose": "Non-organizational users include information system users other than organizational users explicitly covered by IA-2. These individuals are uniquely identified and authenticated for accesses other than those accesses explicitly identified and documented in AC-14. In accordance with the E-Authentication E-Government initiative, authentication of non-organizational users accessing federal information systems may be required to protect federal, proprietary, or privacy-related information (with exceptions noted for national security systems). Organizations use risk assessments to determine authentication needs and consider scalability, practicality, and security in balancing the need to ensure ease of use for access to federal information and information systems with the need to protect and adequately mitigate risk. IA-2 addresses identification and authentication requirements for access to information systems by organizational users.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-14", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#sa-12", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - } - ] - }, - { - "id": "ia-8_obj", - "name": "objective", - "prose": "Determine if the information system uniquely identifies and authenticates non-organizational users (or processes acting on behalf of non-organizational users)." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of information system accounts\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\norganizational personnel with account management responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing identification and authentication capability" - } - ] - } - ], - "controls": [ - { - "id": "ia-8.1", - "class": "SP800-53-enhancement", - "title": "Acceptance of PIV Credentials from Other Agencies", - "props": [ - { - "name": "label", - "value": "IA-8(1)" - }, - { - "name": "sort-id", - "value": "ia-08.01" - } - ], - "parts": [ - { - "id": "ia-8.1_smt", - "name": "statement", - "prose": "The information system accepts and electronically verifies Personal Identity Verification (PIV) credentials from other federal agencies." - }, - { - "id": "ia-8.1_gdn", - "name": "guidance", - "prose": "This control enhancement applies to logical access control systems (LACS) and physical access control systems (PACS). Personal Identity Verification (PIV) credentials are those credentials issued by federal agencies that conform to FIPS Publication 201 and supporting guidance documents. OMB Memorandum 11-11 requires federal agencies to continue implementing the requirements specified in HSPD-12 to enable agency-wide use of PIV credentials.", - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - } - ] - }, - { - "id": "ia-8.1_obj", - "name": "objective", - "prose": "Determine if the information system:", - "parts": [ - { - "id": "ia-8.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-8(1)[1]" - } - ], - "prose": "accepts Personal Identity Verification (PIV) credentials from other agencies; and" - }, - { - "id": "ia-8.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-8(1)[2]" - } - ], - "prose": "electronically verifies Personal Identity Verification (PIV) credentials from other agencies." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nPIV verification records\n\nevidence of PIV credentials\n\nPIV credential authorizations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers\n\norganizational personnel with account management responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing identification and authentication capability\n\nautomated mechanisms that accept and verify PIV credentials" - } - ] - } - ] - }, - { - "id": "ia-8.2", - "class": "SP800-53-enhancement", - "title": "Acceptance of Third-party Credentials", - "props": [ - { - "name": "label", - "value": "IA-8(2)" - }, - { - "name": "sort-id", - "value": "ia-08.02" - } - ], - "parts": [ - { - "id": "ia-8.2_smt", - "name": "statement", - "prose": "The information system accepts only FICAM-approved third-party credentials." - }, - { - "id": "ia-8.2_gdn", - "name": "guidance", - "prose": "This control enhancement typically applies to organizational information systems that are accessible to the general public, for example, public-facing websites. Third-party credentials are those credentials issued by nonfederal government entities approved by the Federal Identity, Credential, and Access Management (FICAM) Trust Framework Solutions initiative. Approved third-party credentials meet or exceed the set of minimum federal government-wide technical, security, privacy, and organizational maturity requirements. This allows federal government relying parties to trust such credentials at their approved assurance levels.", - "links": [ - { - "href": "#au-2", - "rel": "related" - } - ] - }, - { - "id": "ia-8.2_obj", - "name": "objective", - "prose": "Determine if the information system accepts only FICAM-approved third-party credentials." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of FICAM-approved, third-party credentialing products, components, or services procured and implemented by organization\n\nthird-party credential verification records\n\nevidence of FICAM-approved third-party credentials\n\nthird-party credential authorizations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers\n\norganizational personnel with account management responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing identification and authentication capability\n\nautomated mechanisms that accept FICAM-approved credentials" - } - ] - } - ] - }, - { - "id": "ia-8.3", - "class": "SP800-53-enhancement", - "title": "Use of Ficam-approved Products", - "params": [ - { - "id": "ia-8.3_prm_1", - "label": "organization-defined information systems" - } - ], - "props": [ - { - "name": "label", - "value": "IA-8(3)" - }, - { - "name": "sort-id", - "value": "ia-08.03" - } - ], - "parts": [ - { - "id": "ia-8.3_smt", - "name": "statement", - "prose": "The organization employs only FICAM-approved information system components in {{ insert: param, ia-8.3_prm_1 }} to accept third-party credentials." - }, - { - "id": "ia-8.3_gdn", - "name": "guidance", - "prose": "This control enhancement typically applies to information systems that are accessible to the general public, for example, public-facing websites. FICAM-approved information system components include, for example, information technology products and software libraries that have been approved by the Federal Identity, Credential, and Access Management conformance program.", - "links": [ - { - "href": "#sa-4", - "rel": "related" - } - ] - }, - { - "id": "ia-8.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ia-8.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-8(3)[1]" - } - ], - "prose": "defines information systems in which only FICAM-approved information system components are to be employed to accept third-party credentials; and" - }, - { - "id": "ia-8.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-8(3)[2]" - } - ], - "prose": "employs only FICAM-approved information system components in organization-defined information systems to accept third-party credentials." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nsystem and services acquisition policy\n\nprocedures addressing user identification and authentication\n\nprocedures addressing the integration of security requirements into the acquisition process\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nthird-party credential validations\n\nthird-party credential authorizations\n\nthird-party credential records\n\nlist of FICAM-approved information system components procured and implemented by organization\n\nacquisition documentation\n\nacquisition contracts for information system procurements or services\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\nsystem/network administrators\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information system security, acquisition, and contracting responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing identification and authentication capability" - } - ] - } - ] - }, - { - "id": "ia-8.4", - "class": "SP800-53-enhancement", - "title": "Use of Ficam-issued Profiles", - "props": [ - { - "name": "label", - "value": "IA-8(4)" - }, - { - "name": "sort-id", - "value": "ia-08.04" - } - ], - "parts": [ - { - "id": "ia-8.4_smt", - "name": "statement", - "prose": "The information system conforms to FICAM-issued profiles." - }, - { - "id": "ia-8.4_gdn", - "name": "guidance", - "prose": "This control enhancement addresses open identity management standards. To ensure that these standards are viable, robust, reliable, sustainable (e.g., available in commercial information technology products), and interoperable as documented, the United States Government assesses and scopes identity management standards and technology implementations against applicable federal legislation, directives, policies, and requirements. The result is FICAM-issued implementation profiles of approved protocols (e.g., FICAM authentication protocols such as SAML 2.0 and OpenID 2.0, as well as other protocols such as the FICAM Backend Attribute Exchange).", - "links": [ - { - "href": "#sa-4", - "rel": "related" - } - ] - }, - { - "id": "ia-8.4_obj", - "name": "objective", - "prose": "Determine if the information system conforms to FICAM-issued profiles." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nsystem and services acquisition policy\n\nprocedures addressing user identification and authentication\n\nprocedures addressing the integration of security requirements into the acquisition process\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of FICAM-issued profiles and associated, approved protocols\n\nacquisition documentation\n\nacquisition contracts for information system procurements or services\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers\n\norganizational personnel with account management responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing identification and authentication capability\n\nautomated mechanisms supporting and/or implementing conformance with FICAM-issued profiles" - } - ] - } - ] - }, - { - "id": "ia-8.5", - "class": "SP800-53-enhancement", - "title": "Acceptance of PIV-I Credentials", - "props": [ - { - "name": "label", - "value": "IA-8(5)" - }, - { - "name": "sort-id", - "value": "ia-08.05" - } - ], - "parts": [ - { - "id": "ia-8.5_smt", - "name": "statement", - "prose": "The information system accepts and electronically verifies Personal Identity Verification-I (PIV-I) credentials." - }, - { - "id": "ia-8.5_gdn", - "name": "guidance", - "prose": "This control enhancement: (i) applies to logical and physical access control systems; and (ii) addresses Non-Federal Issuers (NFIs) of identity cards that desire to interoperate with United States Government Personal Identity Verification (PIV) information systems and that can be trusted by federal government-relying parties. The X.509 certificate policy for the Federal Bridge Certification Authority (FBCA) addresses PIV-I requirements. The PIV-I card is suitable for Assurance Level 4 as defined in OMB Memorandum 04-04 and NIST Special Publication 800-63, and multifactor authentication as defined in NIST Special Publication 800-116. PIV-I credentials are those credentials issued by a PIV-I provider whose PIV-I certificate policy maps to the Federal Bridge PIV-I Certificate Policy. A PIV-I provider is cross-certified (directly or through another PKI bridge) with the FBCA with policies that have been mapped and approved as meeting the requirements of the PIV-I policies defined in the FBCA certificate policy.", - "links": [ - { - "href": "#au-2", - "rel": "related" - } - ] - }, - { - "id": "ia-8.5_obj", - "name": "objective", - "prose": "Determine if the information system:", - "parts": [ - { - "id": "ia-8.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-8(5)[1]" - } - ], - "prose": "accepts Personal Identity Verification-I (PIV-I) credentials; and" - }, - { - "id": "ia-8.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-8(5)[2]" - } - ], - "prose": "electronically verifies Personal Identity Verification-I (PIV-I) credentials." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user identification and authentication\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nPIV-I verification records\n\nevidence of PIV-I credentials\n\nPIV-I credential authorizations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers\n\norganizational personnel with account management responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing identification and authentication capability\n\nautomated mechanisms that accept and verify PIV-I credentials" - } - ] - } - ] - } - ] - }, - { - "id": "ia-9", - "class": "SP800-53", - "title": "Service Identification and Authentication", - "params": [ - { - "id": "ia-9_prm_1", - "label": "organization-defined information system services" - }, - { - "id": "ia-9_prm_2", - "label": "organization-defined security safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "IA-9" - }, - { - "name": "sort-id", - "value": "ia-09" - } - ], - "parts": [ - { - "id": "ia-9_smt", - "name": "statement", - "prose": "The organization identifies and authenticates {{ insert: param, ia-9_prm_1 }} using {{ insert: param, ia-9_prm_2 }}." - }, - { - "id": "ia-9_gdn", - "name": "guidance", - "prose": "This control supports service-oriented architectures and other distributed architectural approaches requiring the identification and authentication of information system services. In such architectures, external services often appear dynamically. Therefore, information systems should be able to determine in a dynamic manner, if external providers and associated services are authentic. Safeguards implemented by organizational information systems to validate provider and service authenticity include, for example, information or code signing, provenance graphs, and/or electronic signatures indicating or including the sources of services." - }, - { - "id": "ia-9_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ia-9_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-9[1]" - } - ], - "prose": "defines information system services to be identified and authenticated using security safeguards;" - }, - { - "id": "ia-9_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-9[2]" - } - ], - "prose": "defines security safeguards to be used to identify and authenticate organization-defined information system services; and" - }, - { - "id": "ia-9_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-9[3]" - } - ], - "prose": "identifies and authenticates organization-defined information system services using organization-defined security safeguards." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing service identification and authentication\n\nsecurity plan\n\ninformation system design documentation\n\nsecurity safeguards used to identify and authenticate information system services\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers\n\norganizational personnel with identification and authentication responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security safeguards implementing service identification and authentication capability" - } - ] - } - ], - "controls": [ - { - "id": "ia-9.1", - "class": "SP800-53-enhancement", - "title": "Information Exchange", - "props": [ - { - "name": "label", - "value": "IA-9(1)" - }, - { - "name": "sort-id", - "value": "ia-09.01" - } - ], - "parts": [ - { - "id": "ia-9.1_smt", - "name": "statement", - "prose": "The organization ensures that service providers receive, validate, and transmit identification and authentication information." - }, - { - "id": "ia-9.1_obj", - "name": "objective", - "prose": "Determine if the organization ensures that service providers:", - "parts": [ - { - "id": "ia-9.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-9(1)[1]" - } - ], - "prose": "receive identification and authentication information;" - }, - { - "id": "ia-9.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-9(1)[2]" - } - ], - "prose": "validate identification and authentication information; and" - }, - { - "id": "ia-9.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-9(1)[3]" - } - ], - "prose": "transmit identification and authentication information." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing service identification and authentication\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with identification and authentication responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nservice providers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing service identification and authentication capabilities" - } - ] - } - ] - }, - { - "id": "ia-9.2", - "class": "SP800-53-enhancement", - "title": "Transmission of Decisions", - "params": [ - { - "id": "ia-9.2_prm_1", - "label": "organization-defined services" - } - ], - "props": [ - { - "name": "label", - "value": "IA-9(2)" - }, - { - "name": "sort-id", - "value": "ia-09.02" - } - ], - "parts": [ - { - "id": "ia-9.2_smt", - "name": "statement", - "prose": "The organization ensures that identification and authentication decisions are transmitted between {{ insert: param, ia-9.2_prm_1 }} consistent with organizational policies." - }, - { - "id": "ia-9.2_gdn", - "name": "guidance", - "prose": "For distributed architectures (e.g., service-oriented architectures), the decisions regarding the validation of identification and authentication claims may be made by services separate from the services acting on those decisions. In such situations, it is necessary to provide the identification and authentication decisions (as opposed to the actual identifiers and authenticators) to the services that need to act on those decisions.", - "links": [ - { - "href": "#sc-8", - "rel": "related" - } - ] - }, - { - "id": "ia-9.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ia-9.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-9(2)[1]" - } - ], - "prose": "defines services for which identification and authentication decisions transmitted between such services are to be consistent with organizational policies; and" - }, - { - "id": "ia-9.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-9(2)[2]" - } - ], - "prose": "ensures that identification and authentication decisions are transmitted between organization-defined services consistent with organizational policies." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing service identification and authentication\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\ntransmission records\n\ntransmission verification records\n\nrules for identification and authentication transmission decisions between organizational services\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with identification and authentication responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing service identification and authentication capabilities" - } - ] - } - ] - } - ] - }, - { - "id": "ia-10", - "class": "SP800-53", - "title": "Adaptive Identification and Authentication", - "params": [ - { - "id": "ia-10_prm_1", - "label": "organization-defined supplemental authentication techniques or mechanisms" - }, - { - "id": "ia-10_prm_2", - "label": "organization-defined circumstances or situations" - } - ], - "props": [ - { - "name": "label", - "value": "IA-10" - }, - { - "name": "sort-id", - "value": "ia-10" - } - ], - "parts": [ - { - "id": "ia-10_smt", - "name": "statement", - "prose": "The organization requires that individuals accessing the information system employ {{ insert: param, ia-10_prm_1 }} under specific {{ insert: param, ia-10_prm_2 }}." - }, - { - "id": "ia-10_gdn", - "name": "guidance", - "prose": "Adversaries may compromise individual authentication mechanisms and subsequently attempt to impersonate legitimate users. This situation can potentially occur with any authentication mechanisms employed by organizations. To address this threat, organizations may employ specific techniques/mechanisms and establish protocols to assess suspicious behavior (e.g., individuals accessing information that they do not typically access as part of their normal duties, roles, or responsibilities, accessing greater quantities of information than the individuals would routinely access, or attempting to access information from suspicious network addresses). In these situations when certain preestablished conditions or triggers occur, organizations can require selected individuals to provide additional authentication information. Another potential use for adaptive identification and authentication is to increase the strength of mechanism based on the number and/or types of records being accessed.", - "links": [ - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "ia-10_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ia-10_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-10[1]" - } - ], - "prose": "defines specific circumstances or situations that require individuals accessing the information system to employ supplemental authentication techniques or mechanisms;" - }, - { - "id": "ia-10_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-10[2]" - } - ], - "prose": "defines supplemental authentication techniques or mechanisms to be employed when accessing the information system under specific organization-defined circumstances or situations; and" - }, - { - "id": "ia-10_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-10[3]" - } - ], - "prose": "requires that individuals accessing the information system employ organization-defined supplemental authentication techniques or mechanisms under specific organization-defined circumstances or situations." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing adaptive/ supplemental identification and authentication techniques or mechanisms\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsupplemental identification and authentication techniques or mechanisms\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers\n\norganizational personnel with identification and authentication responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing identification and authentication capability" - } - ] - } - ] - }, - { - "id": "ia-11", - "class": "SP800-53", - "title": "Re-authentication", - "params": [ - { - "id": "ia-11_prm_1", - "label": "organization-defined circumstances or situations requiring re-authentication" - } - ], - "props": [ - { - "name": "label", - "value": "IA-11" - }, - { - "name": "sort-id", - "value": "ia-11" - } - ], - "parts": [ - { - "id": "ia-11_smt", - "name": "statement", - "prose": "The organization requires users and devices to re-authenticate when {{ insert: param, ia-11_prm_1 }}." - }, - { - "id": "ia-11_gdn", - "name": "guidance", - "prose": "In addition to the re-authentication requirements associated with session locks, organizations may require re-authentication of individuals and/or devices in other situations including, for example: (i) when authenticators change; (ii), when roles change; (iii) when security categories of information systems change; (iv), when the execution of privileged functions occurs; (v) after a fixed period of time; or (vi) periodically.", - "links": [ - { - "href": "#ac-11", - "rel": "related" - } - ] - }, - { - "id": "ia-11_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ia-11_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-11[1]" - } - ], - "prose": "defines circumstances or situations requiring re-authentication;" - }, - { - "id": "ia-11_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-11[2]" - } - ], - "prose": "requires users to re-authenticate when organization-defined circumstances or situations require re-authentication; and" - }, - { - "id": "ia-11_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IA-11[3]" - } - ], - "prose": "requires devices to re-authenticate when organization-defined circumstances or situations require re-authentication." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user and device re-authentication\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of circumstances or situations requiring re-authentication\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system operations responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers\n\norganizational personnel with identification and authentication responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing identification and authentication capability" - } - ] - } - ] - } - ] - }, - { - "id": "ir", - "class": "family", - "title": "Incident Response", - "controls": [ - { - "id": "ir-1", - "class": "SP800-53", - "title": "Incident Response Policy and Procedures", - "params": [ - { - "id": "ir-1_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "ir-1_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "ir-1_prm_3", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "IR-1" - }, - { - "name": "sort-id", - "value": "ir-01" - } - ], - "links": [ - { - "href": "#5c201b63-0768-417b-ac22-3f014e3941b2", - "rel": "reference" - }, - { - "href": "#be95fb85-a53f-4624-bdbb-140075500aa3", - "rel": "reference" - }, - { - "href": "#6d431fee-658f-4a0e-9f2e-a38b5d398fab", - "rel": "reference" - }, - { - "href": "#9cb3d8fe-2127-48ba-821e-cdd2d7aee921", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ir-1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ir-1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops, documents, and disseminates to {{ insert: param, ir-1_prm_1 }}:", - "parts": [ - { - "id": "ir-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "An incident response policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "ir-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the incident response policy and associated incident response controls; and" - } - ] - }, - { - "id": "ir-1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the current:", - "parts": [ - { - "id": "ir-1_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Incident response policy {{ insert: param, ir-1_prm_2 }}; and" - }, - { - "id": "ir-1_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Incident response procedures {{ insert: param, ir-1_prm_3 }}." - } - ] - } - ] - }, - { - "id": "ir-1_gdn", - "name": "guidance", - "prose": "This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the IR family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures.", - "links": [ - { - "href": "#pm-9", - "rel": "related" - } - ] - }, - { - "id": "ir-1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(a)" - } - ], - "parts": [ - { - "id": "ir-1.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(a)(1)" - } - ], - "parts": [ - { - "id": "ir-1.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(a)(1)[1]" - } - ], - "prose": "develops and documents an incident response policy that addresses:", - "parts": [ - { - "id": "ir-1.a.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(a)(1)[1][a]" - } - ], - "prose": "purpose;" - }, - { - "id": "ir-1.a.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(a)(1)[1][b]" - } - ], - "prose": "scope;" - }, - { - "id": "ir-1.a.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(a)(1)[1][c]" - } - ], - "prose": "roles;" - }, - { - "id": "ir-1.a.1_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(a)(1)[1][d]" - } - ], - "prose": "responsibilities;" - }, - { - "id": "ir-1.a.1_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(a)(1)[1][e]" - } - ], - "prose": "management commitment;" - }, - { - "id": "ir-1.a.1_obj.1.f", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(a)(1)[1][f]" - } - ], - "prose": "coordination among organizational entities;" - }, - { - "id": "ir-1.a.1_obj.1.g", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(a)(1)[1][g]" - } - ], - "prose": "compliance;" - } - ] - }, - { - "id": "ir-1.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(a)(1)[2]" - } - ], - "prose": "defines personnel or roles to whom the incident response policy is to be disseminated;" - }, - { - "id": "ir-1.a.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(a)(1)[3]" - } - ], - "prose": "disseminates the incident response policy to organization-defined personnel or roles;" - } - ] - }, - { - "id": "ir-1.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(a)(2)" - } - ], - "parts": [ - { - "id": "ir-1.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(a)(2)[1]" - } - ], - "prose": "develops and documents procedures to facilitate the implementation of the incident response policy and associated incident response controls;" - }, - { - "id": "ir-1.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(a)(2)[2]" - } - ], - "prose": "defines personnel or roles to whom the procedures are to be disseminated;" - }, - { - "id": "ir-1.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(a)(2)[3]" - } - ], - "prose": "disseminates the procedures to organization-defined personnel or roles;" - } - ] - } - ] - }, - { - "id": "ir-1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(b)" - } - ], - "parts": [ - { - "id": "ir-1.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(b)(1)" - } - ], - "parts": [ - { - "id": "ir-1.b.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(b)(1)[1]" - } - ], - "prose": "defines the frequency to review and update the current incident response policy;" - }, - { - "id": "ir-1.b.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(b)(1)[2]" - } - ], - "prose": "reviews and updates the current incident response policy with the organization-defined frequency;" - } - ] - }, - { - "id": "ir-1.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(b)(2)" - } - ], - "parts": [ - { - "id": "ir-1.b.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(b)(2)[1]" - } - ], - "prose": "defines the frequency to review and update the current incident response procedures; and" - }, - { - "id": "ir-1.b.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-1(b)(2)[2]" - } - ], - "prose": "reviews and updates the current incident response procedures with the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy and procedures\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident response responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "ir-2", - "class": "SP800-53", - "title": "Incident Response Training", - "params": [ - { - "id": "ir-2_prm_1", - "label": "organization-defined time period" - }, - { - "id": "ir-2_prm_2", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "IR-2" - }, - { - "name": "sort-id", - "value": "ir-02" - } - ], - "links": [ - { - "href": "#825438c3-248d-4e30-a51e-246473ce6ada", - "rel": "reference" - }, - { - "href": "#e12b5738-de74-4fb3-8317-a3995a8a1898", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ir-2_smt", - "name": "statement", - "prose": "The organization provides incident response training to information system users consistent with assigned roles and responsibilities:", - "parts": [ - { - "id": "ir-2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Within {{ insert: param, ir-2_prm_1 }} of assuming an incident response role or responsibility;" - }, - { - "id": "ir-2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "When required by information system changes; and" - }, - { - "id": "ir-2_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": " {{ insert: param, ir-2_prm_2 }} thereafter." - } - ] - }, - { - "id": "ir-2_gdn", - "name": "guidance", - "prose": "Incident response training provided by organizations is linked to the assigned roles and responsibilities of organizational personnel to ensure the appropriate content and level of detail is included in such training. For example, regular users may only need to know who to call or how to recognize an incident on the information system; system administrators may require additional training on how to handle/remediate incidents; and incident responders may receive more specific training on forensics, reporting, system recovery, and restoration. Incident response training includes user training in the identification and reporting of suspicious activities, both from external and internal sources.", - "links": [ - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#cp-3", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - } - ] - }, - { - "id": "ir-2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-2(a)" - } - ], - "parts": [ - { - "id": "ir-2.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-2(a)[1]" - } - ], - "prose": "defines a time period within which incident response training is to be provided to information system users assuming an incident response role or responsibility;" - }, - { - "id": "ir-2.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-2(a)[2]" - } - ], - "prose": "provides incident response training to information system users consistent with assigned roles and responsibilities within the organization-defined time period of assuming an incident response role or responsibility;" - } - ] - }, - { - "id": "ir-2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-2(b)" - } - ], - "prose": "provides incident response training to information system users consistent with assigned roles and responsibilities when required by information system changes;" - }, - { - "id": "ir-2.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-2(c)" - } - ], - "parts": [ - { - "id": "ir-2.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-2(c)[1]" - } - ], - "prose": "defines the frequency to provide refresher incident response training to information system users consistent with assigned roles or responsibilities; and" - }, - { - "id": "ir-2.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-2(c)[2]" - } - ], - "prose": "after the initial incident response training, provides refresher incident response training to information system users consistent with assigned roles and responsibilities in accordance with the organization-defined frequency to provide refresher training." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident response training\n\nincident response training curriculum\n\nincident response training materials\n\nsecurity plan\n\nincident response plan\n\nsecurity plan\n\nincident response training records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident response training and operational responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ], - "controls": [ - { - "id": "ir-2.1", - "class": "SP800-53-enhancement", - "title": "Simulated Events", - "props": [ - { - "name": "label", - "value": "IR-2(1)" - }, - { - "name": "sort-id", - "value": "ir-02.01" - } - ], - "parts": [ - { - "id": "ir-2.1_smt", - "name": "statement", - "prose": "The organization incorporates simulated events into incident response training to facilitate effective response by personnel in crisis situations." - }, - { - "id": "ir-2.1_obj", - "name": "objective", - "prose": "Determine if the organization incorporates simulated events into incident response training to facilitate effective response by personnel in crisis situations." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident response training\n\nincident response training curriculum\n\nincident response training materials\n\nincident response plan\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident response training and operational responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms that support and/or implement simulated events for incident response training" - } - ] - } - ] - }, - { - "id": "ir-2.2", - "class": "SP800-53-enhancement", - "title": "Automated Training Environments", - "props": [ - { - "name": "label", - "value": "IR-2(2)" - }, - { - "name": "sort-id", - "value": "ir-02.02" - } - ], - "parts": [ - { - "id": "ir-2.2_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to provide a more thorough and realistic incident response training environment." - }, - { - "id": "ir-2.2_obj", - "name": "objective", - "prose": "Determine if the organization employs automated mechanisms to provide a more thorough and realistic incident response training environment." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident response training\n\nincident response training curriculum\n\nincident response training materials\n\nautomated mechanisms supporting incident response training\n\nincident response plan\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident response training and operational responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms that provide a thorough and realistic incident response training environment" - } - ] - } - ] - } - ] - }, - { - "id": "ir-3", - "class": "SP800-53", - "title": "Incident Response Testing", - "params": [ - { - "id": "ir-3_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "ir-3_prm_2", - "label": "organization-defined tests" - } - ], - "props": [ - { - "name": "label", - "value": "IR-3" - }, - { - "name": "sort-id", - "value": "ir-03" - } - ], - "links": [ - { - "href": "#0243a05a-e8a3-4d51-9364-4a9d20b0dcdf", - "rel": "reference" - }, - { - "href": "#c4691b88-57d1-463b-9053-2d0087913f31", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ir-3_smt", - "name": "statement", - "prose": "The organization tests the incident response capability for the information system {{ insert: param, ir-3_prm_1 }} using {{ insert: param, ir-3_prm_2 }} to determine the incident response effectiveness and documents the results." - }, - { - "id": "ir-3_gdn", - "name": "guidance", - "prose": "Organizations test incident response capabilities to determine the overall effectiveness of the capabilities and to identify potential weaknesses or deficiencies. Incident response testing includes, for example, the use of checklists, walk-through or tabletop exercises, simulations (parallel/full interrupt), and comprehensive exercises. Incident response testing can also include a determination of the effects on organizational operations (e.g., reduction in mission capabilities), organizational assets, and individuals due to incident response.", - "links": [ - { - "href": "#cp-4", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - } - ] - }, - { - "id": "ir-3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-3[1]" - } - ], - "prose": "defines incident response tests to test the incident response capability for the information system;" - }, - { - "id": "ir-3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-3[2]" - } - ], - "prose": "defines the frequency to test the incident response capability for the information system; and" - }, - { - "id": "ir-3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-3[3]" - } - ], - "prose": "tests the incident response capability for the information system with the organization-defined frequency, using organization-defined tests to determine the incident response effectiveness and documents the results." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\ncontingency planning policy\n\nprocedures addressing incident response testing\n\nprocedures addressing contingency plan testing\n\nincident response testing material\n\nincident response test results\n\nincident response test plan\n\nincident response plan\n\ncontingency plan\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident response testing responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ], - "controls": [ - { - "id": "ir-3.1", - "class": "SP800-53-enhancement", - "title": "Automated Testing", - "props": [ - { - "name": "label", - "value": "IR-3(1)" - }, - { - "name": "sort-id", - "value": "ir-03.01" - } - ], - "parts": [ - { - "id": "ir-3.1_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to more thoroughly and effectively test the incident response capability." - }, - { - "id": "ir-3.1_gdn", - "name": "guidance", - "prose": "Organizations use automated mechanisms to more thoroughly and effectively test incident response capabilities, for example: (i) by providing more complete coverage of incident response issues; (ii) by selecting more realistic test scenarios and test environments; and (iii) by stressing the response capability.", - "links": [ - { - "href": "#at-2", - "rel": "related" - } - ] - }, - { - "id": "ir-3.1_obj", - "name": "objective", - "prose": "Determine if the organization employs automated mechanisms to more thoroughly and effectively test the incident response capability." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\ncontingency planning policy\n\nprocedures addressing incident response testing\n\nprocedures addressing contingency plan testing\n\nincident response testing documentation\n\nincident response test results\n\nincident response test plan\n\nincident response plan\n\ncontingency plan\n\nsecurity plan\n\nautomated mechanisms supporting incident response tests\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident response testing responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms that more thoroughly and effectively test the incident response capability" - } - ] - } - ] - }, - { - "id": "ir-3.2", - "class": "SP800-53-enhancement", - "title": "Coordination with Related Plans", - "props": [ - { - "name": "label", - "value": "IR-3(2)" - }, - { - "name": "sort-id", - "value": "ir-03.02" - } - ], - "parts": [ - { - "id": "ir-3.2_smt", - "name": "statement", - "prose": "The organization coordinates incident response testing with organizational elements responsible for related plans." - }, - { - "id": "ir-3.2_gdn", - "name": "guidance", - "prose": "Organizational plans related to incident response testing include, for example, Business Continuity Plans, Contingency Plans, Disaster Recovery Plans, Continuity of Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, and Occupant Emergency Plans." - }, - { - "id": "ir-3.2_obj", - "name": "objective", - "prose": "Determine if the organization coordinates incident response testing with organizational elements responsible for related plans." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\ncontingency planning policy\n\nprocedures addressing incident response testing\n\nincident response testing documentation\n\nincident response plan\n\nbusiness continuity plans\n\ncontingency plans\n\ndisaster recovery plans\n\ncontinuity of operations plans\n\ncrisis communications plans\n\ncritical infrastructure plans\n\noccupant emergency plans\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident response testing responsibilities\n\norganizational personnel with responsibilities for testing organizational plans related to incident response testing\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "ir-4", - "class": "SP800-53", - "title": "Incident Handling", - "props": [ - { - "name": "label", - "value": "IR-4" - }, - { - "name": "sort-id", - "value": "ir-04" - } - ], - "links": [ - { - "href": "#c5034e0c-eba6-4ecd-a541-79f0678f4ba4", - "rel": "reference" - }, - { - "href": "#be95fb85-a53f-4624-bdbb-140075500aa3", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ir-4_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ir-4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Implements an incident handling capability for security incidents that includes preparation, detection and analysis, containment, eradication, and recovery;" - }, - { - "id": "ir-4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Coordinates incident handling activities with contingency planning activities; and" - }, - { - "id": "ir-4_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Incorporates lessons learned from ongoing incident handling activities into incident response procedures, training, and testing, and implements the resulting changes accordingly." - } - ] - }, - { - "id": "ir-4_gdn", - "name": "guidance", - "prose": "Organizations recognize that incident response capability is dependent on the capabilities of organizational information systems and the mission/business processes being supported by those systems. Therefore, organizations consider incident response as part of the definition, design, and development of mission/business processes and information systems. Incident-related information can be obtained from a variety of sources including, for example, audit monitoring, network monitoring, physical access monitoring, user/administrator reports, and reported supply chain events. Effective incident handling capability includes coordination among many organizational entities including, for example, mission/business owners, information system owners, authorizing officials, human resources offices, physical and personnel security offices, legal departments, operations personnel, procurement offices, and the risk executive (function).", - "links": [ - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-4", - "rel": "related" - }, - { - "href": "#ir-2", - "rel": "related" - }, - { - "href": "#ir-3", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - }, - { - "href": "#pe-6", - "rel": "related" - }, - { - "href": "#sc-5", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "ir-4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(a)" - } - ], - "prose": "implements an incident handling capability for security incidents that includes:", - "parts": [ - { - "id": "ir-4.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(a)[1]" - } - ], - "prose": "preparation;" - }, - { - "id": "ir-4.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(a)[2]" - } - ], - "prose": "detection and analysis;" - }, - { - "id": "ir-4.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(a)[3]" - } - ], - "prose": "containment;" - }, - { - "id": "ir-4.a_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(a)[4]" - } - ], - "prose": "eradication;" - }, - { - "id": "ir-4.a_obj.5", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(a)[5]" - } - ], - "prose": "recovery;" - } - ] - }, - { - "id": "ir-4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(b)" - } - ], - "prose": "coordinates incident handling activities with contingency planning activities;" - }, - { - "id": "ir-4.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(c)" - } - ], - "parts": [ - { - "id": "ir-4.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(c)[1]" - } - ], - "prose": "incorporates lessons learned from ongoing incident handling activities into:", - "parts": [ - { - "id": "ir-4.c_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(c)[1][a]" - } - ], - "prose": "incident response procedures;" - }, - { - "id": "ir-4.c_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(c)[1][b]" - } - ], - "prose": "training;" - }, - { - "id": "ir-4.c_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(c)[1][c]" - } - ], - "prose": "testing/exercises;" - } - ] - }, - { - "id": "ir-4.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(c)[2]" - } - ], - "prose": "implements the resulting changes accordingly to:", - "parts": [ - { - "id": "ir-4.c_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(c)[2][a]" - } - ], - "prose": "incident response procedures;" - }, - { - "id": "ir-4.c_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(c)[2][b]" - } - ], - "prose": "training; and" - }, - { - "id": "ir-4.c_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(c)[2][c]" - } - ], - "prose": "testing/exercises." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\ncontingency planning policy\n\nprocedures addressing incident handling\n\nincident response plan\n\ncontingency plan\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident handling responsibilities\n\norganizational personnel with contingency planning responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident handling capability for the organization" - } - ] - } - ], - "controls": [ - { - "id": "ir-4.1", - "class": "SP800-53-enhancement", - "title": "Automated Incident Handling Processes", - "props": [ - { - "name": "label", - "value": "IR-4(1)" - }, - { - "name": "sort-id", - "value": "ir-04.01" - } - ], - "parts": [ - { - "id": "ir-4.1_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to support the incident handling process." - }, - { - "id": "ir-4.1_gdn", - "name": "guidance", - "prose": "Automated mechanisms supporting incident handling processes include, for example, online incident management systems." - }, - { - "id": "ir-4.1_obj", - "name": "objective", - "prose": "Determine if the organization employs automated mechanisms to support the incident handling process." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident handling\n\nautomated mechanisms supporting incident handling\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nincident response plan\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident handling responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms that support and/or implement the incident handling process" - } - ] - } - ] - }, - { - "id": "ir-4.2", - "class": "SP800-53-enhancement", - "title": "Dynamic Reconfiguration", - "params": [ - { - "id": "ir-4.2_prm_1", - "label": "organization-defined information system components" - } - ], - "props": [ - { - "name": "label", - "value": "IR-4(2)" - }, - { - "name": "sort-id", - "value": "ir-04.02" - } - ], - "parts": [ - { - "id": "ir-4.2_smt", - "name": "statement", - "prose": "The organization includes dynamic reconfiguration of {{ insert: param, ir-4.2_prm_1 }} as part of the incident response capability." - }, - { - "id": "ir-4.2_gdn", - "name": "guidance", - "prose": "Dynamic reconfiguration includes, for example, changes to router rules, access control lists, intrusion detection/prevention system parameters, and filter rules for firewalls and gateways. Organizations perform dynamic reconfiguration of information systems, for example, to stop attacks, to misdirect attackers, and to isolate components of systems, thus limiting the extent of the damage from breaches or compromises. Organizations include time frames for achieving the reconfiguration of information systems in the definition of the reconfiguration capability, considering the potential need for rapid response in order to effectively address sophisticated cyber threats.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-16", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - } - ] - }, - { - "id": "ir-4.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-4.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(2)[1]" - } - ], - "prose": "defines information system components to be dynamically reconfigured as part of the incident response capability; and" - }, - { - "id": "ir-4.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(2)[2]" - } - ], - "prose": "includes dynamic reconfiguration of organization-defined information system components as part of the incident response capability." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident handling\n\nautomated mechanisms supporting incident handling\n\nlist of system components to be dynamically reconfigured as part of incident response capability\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nincident response plan\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident handling responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms that support and/or implement dynamic reconfiguration of components as part of incident response" - } - ] - } - ] - }, - { - "id": "ir-4.3", - "class": "SP800-53-enhancement", - "title": "Continuity of Operations", - "params": [ - { - "id": "ir-4.3_prm_1", - "label": "organization-defined classes of incidents" - }, - { - "id": "ir-4.3_prm_2", - "label": "organization-defined actions to take in response to classes of incidents" - } - ], - "props": [ - { - "name": "label", - "value": "IR-4(3)" - }, - { - "name": "sort-id", - "value": "ir-04.03" - } - ], - "parts": [ - { - "id": "ir-4.3_smt", - "name": "statement", - "prose": "The organization identifies {{ insert: param, ir-4.3_prm_1 }} and {{ insert: param, ir-4.3_prm_2 }} to ensure continuation of organizational missions and business functions." - }, - { - "id": "ir-4.3_gdn", - "name": "guidance", - "prose": "Classes of incidents include, for example, malfunctions due to design/implementation errors and omissions, targeted malicious attacks, and untargeted malicious attacks. Appropriate incident response actions include, for example, graceful degradation, information system shutdown, fall back to manual mode/alternative technology whereby the system operates differently, employing deceptive measures, alternate information flows, or operating in a mode that is reserved solely for when systems are under attack." - }, - { - "id": "ir-4.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-4.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(3)[1]" - } - ], - "prose": "defines classes of incidents requiring an organization-defined action to be taken;" - }, - { - "id": "ir-4.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(3)[2]" - } - ], - "prose": "defines actions to be taken in response to organization-defined classes of incidents; and" - }, - { - "id": "ir-4.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(3)[3]" - } - ], - "prose": "identifies organization-defined classes of incidents and organization-defined actions to take in response to classes of incidents to ensure continuation of organizational missions and business functions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident handling\n\nincident response plan\n\nsecurity plan\n\nlist of classes of incidents\n\nlist of appropriate incident response actions\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident handling responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms that support and/or implement continuity of operations" - } - ] - } - ] - }, - { - "id": "ir-4.4", - "class": "SP800-53-enhancement", - "title": "Information Correlation", - "props": [ - { - "name": "label", - "value": "IR-4(4)" - }, - { - "name": "sort-id", - "value": "ir-04.04" - } - ], - "parts": [ - { - "id": "ir-4.4_smt", - "name": "statement", - "prose": "The organization correlates incident information and individual incident responses to achieve an organization-wide perspective on incident awareness and response." - }, - { - "id": "ir-4.4_gdn", - "name": "guidance", - "prose": "Sometimes the nature of a threat event, for example, a hostile cyber attack, is such that it can only be observed by bringing together information from different sources including various reports and reporting procedures established by organizations." - }, - { - "id": "ir-4.4_obj", - "name": "objective", - "prose": "Determine if the organization correlates incident information and individual incident responses to achieve an organization-wide perspective on incident awareness and response." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident handling\n\nincident response plan\n\nsecurity plan\n\nautomated mechanisms supporting incident and event correlation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nincident management correlation logs\n\nevent management correlation logs\n\nsecurity information and event management logs\n\nincident management correlation reports\n\nevent management correlation reports\n\nsecurity information and event management reports\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident handling responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with whom incident information and individual incident responses are to be correlated" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for correlating incident information and individual incident responses\n\nautomated mechanisms that support and or implement correlation of incident response information with individual incident responses" - } - ] - } - ] - }, - { - "id": "ir-4.5", - "class": "SP800-53-enhancement", - "title": "Automatic Disabling of Information System", - "params": [ - { - "id": "ir-4.5_prm_1", - "label": "organization-defined security violations" - } - ], - "props": [ - { - "name": "label", - "value": "IR-4(5)" - }, - { - "name": "sort-id", - "value": "ir-04.05" - } - ], - "parts": [ - { - "id": "ir-4.5_smt", - "name": "statement", - "prose": "The organization implements a configurable capability to automatically disable the information system if {{ insert: param, ir-4.5_prm_1 }} are detected." - }, - { - "id": "ir-4.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-4.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(5)[1]" - } - ], - "prose": "defines security violations that, if detected, initiate a configurable capability to automatically disable the information system; and" - }, - { - "id": "ir-4.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(5)[2]" - } - ], - "prose": "implements a configurable capability to automatically disable the information system if any of the organization-defined security violations are detected." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident handling\n\nautomated mechanisms supporting incident handling\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nincident response plan\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident handling responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident handling capability for the organization\n\nautomated mechanisms supporting and/or implementing automatic disabling of the information system" - } - ] - } - ] - }, - { - "id": "ir-4.6", - "class": "SP800-53-enhancement", - "title": "Insider Threats - Specific Capabilities", - "props": [ - { - "name": "label", - "value": "IR-4(6)" - }, - { - "name": "sort-id", - "value": "ir-04.06" - } - ], - "parts": [ - { - "id": "ir-4.6_smt", - "name": "statement", - "prose": "The organization implements incident handling capability for insider threats." - }, - { - "id": "ir-4.6_gdn", - "name": "guidance", - "prose": "While many organizations address insider threat incidents as an inherent part of their organizational incident response capability, this control enhancement provides additional emphasis on this type of threat and the need for specific incident handling capabilities (as defined within organizations) to provide appropriate and timely responses." - }, - { - "id": "ir-4.6_obj", - "name": "objective", - "prose": "Determine if the organization implements incident handling capability for insider threats." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident handling\n\nautomated mechanisms supporting incident handling\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nincident response plan\n\nsecurity plan\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident handling responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident handling capability for the organization" - } - ] - } - ] - }, - { - "id": "ir-4.7", - "class": "SP800-53-enhancement", - "title": "Insider Threats - Intra-organization Coordination", - "params": [ - { - "id": "ir-4.7_prm_1", - "label": "organization-defined components or elements of the organization" - } - ], - "props": [ - { - "name": "label", - "value": "IR-4(7)" - }, - { - "name": "sort-id", - "value": "ir-04.07" - } - ], - "parts": [ - { - "id": "ir-4.7_smt", - "name": "statement", - "prose": "The organization coordinates incident handling capability for insider threats across {{ insert: param, ir-4.7_prm_1 }}." - }, - { - "id": "ir-4.7_gdn", - "name": "guidance", - "prose": "Incident handling for insider threat incidents (including preparation, detection and analysis, containment, eradication, and recovery) requires close coordination among a variety of organizational components or elements to be effective. These components or elements include, for example, mission/business owners, information system owners, human resources offices, procurement offices, personnel/physical security offices, operations personnel, and risk executive (function). In addition, organizations may require external support from federal, state, and local law enforcement agencies." - }, - { - "id": "ir-4.7_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-4.7_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(7)[1]" - } - ], - "prose": "defines components or elements of the organization with whom the incident handling capability for insider threats is to be coordinated; and" - }, - { - "id": "ir-4.7_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(7)[2]" - } - ], - "prose": "coordinates incident handling capability for insider threats across organization-defined components or elements of the organization." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident handling\n\nincident response plan\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident handling responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel/elements with whom incident handling capability is to be coordinated" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for coordinating incident handling" - } - ] - } - ] - }, - { - "id": "ir-4.8", - "class": "SP800-53-enhancement", - "title": "Correlation with External Organizations", - "params": [ - { - "id": "ir-4.8_prm_1", - "label": "organization-defined external organizations" - }, - { - "id": "ir-4.8_prm_2", - "label": "organization-defined incident information" - } - ], - "props": [ - { - "name": "label", - "value": "IR-4(8)" - }, - { - "name": "sort-id", - "value": "ir-04.08" - } - ], - "parts": [ - { - "id": "ir-4.8_smt", - "name": "statement", - "prose": "The organization coordinates with {{ insert: param, ir-4.8_prm_1 }} to correlate and share {{ insert: param, ir-4.8_prm_2 }} to achieve a cross-organization perspective on incident awareness and more effective incident responses." - }, - { - "id": "ir-4.8_gdn", - "name": "guidance", - "prose": "The coordination of incident information with external organizations including, for example, mission/business partners, military/coalition partners, customers, and multitiered developers, can provide significant benefits. Cross-organizational coordination with respect to incident handling can serve as an important risk management capability. This capability allows organizations to leverage critical information from a variety of sources to effectively respond to information security-related incidents potentially affecting the organization’s operations, assets, and individuals." - }, - { - "id": "ir-4.8_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-4.8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(8)[1]" - } - ], - "prose": "defines external organizations with whom organizational incident information is to be coordinated;" - }, - { - "id": "ir-4.8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(8)[2]" - } - ], - "prose": "defines incident information to be correlated and shared with organization-defined external organizations; and" - }, - { - "id": "ir-4.8_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(8)[3]" - } - ], - "prose": "the organization coordinates with organization-defined external organizations to correlate and share organization-defined information to achieve a cross-organization perspective on incident awareness and more effective incident responses." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident handling\n\nlist of external organizations\n\nrecords of incident handling coordination with external organizations\n\nincident response plan\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident handling responsibilities\n\norganizational personnel with information security responsibilities\n\npersonnel from external organizations with whom incident response information is to be coordinated/shared/correlated" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for coordinating incident handling information with external organizations" - } - ] - } - ] - }, - { - "id": "ir-4.9", - "class": "SP800-53-enhancement", - "title": "Dynamic Response Capability", - "params": [ - { - "id": "ir-4.9_prm_1", - "label": "organization-defined dynamic response capabilities" - } - ], - "props": [ - { - "name": "label", - "value": "IR-4(9)" - }, - { - "name": "sort-id", - "value": "ir-04.09" - } - ], - "parts": [ - { - "id": "ir-4.9_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, ir-4.9_prm_1 }} to effectively respond to security incidents." - }, - { - "id": "ir-4.9_gdn", - "name": "guidance", - "prose": "This control enhancement addresses the deployment of replacement or new capabilities in a timely manner in response to security incidents (e.g., adversary actions during hostile cyber attacks). This includes capabilities implemented at the mission/business process level (e.g., activating alternative mission/business processes) and at the information system level.", - "links": [ - { - "href": "#cp-10", - "rel": "related" - } - ] - }, - { - "id": "ir-4.9_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-4.9_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(9)[1]" - } - ], - "prose": "defines dynamic response capabilities to be employed to effectively respond to security incidents; and" - }, - { - "id": "ir-4.9_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-4(9)[2]" - } - ], - "prose": "employs organization-defined dynamic response capabilities to effectively respond to security incidents." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident handling\n\nautomated mechanisms supporting dynamic response capabilities\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nincident response plan\n\nsecurity plan\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident handling responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for dynamic response capability\n\nautomated mechanisms supporting and/or implementing the dynamic response capability for the organization" - } - ] - } - ] - }, - { - "id": "ir-4.10", - "class": "SP800-53-enhancement", - "title": "Supply Chain Coordination", - "props": [ - { - "name": "label", - "value": "IR-4(10)" - }, - { - "name": "sort-id", - "value": "ir-04.10" - } - ], - "parts": [ - { - "id": "ir-4.10_smt", - "name": "statement", - "prose": "The organization coordinates incident handling activities involving supply chain events with other organizations involved in the supply chain." - }, - { - "id": "ir-4.10_gdn", - "name": "guidance", - "prose": "Organizations involved in supply chain activities include, for example, system/product developers, integrators, manufacturers, packagers, assemblers, distributors, vendors, and resellers. Supply chain incidents include, for example, compromises/breaches involving information system components, information technology products, development processes or personnel, and distribution processes or warehousing facilities." - }, - { - "id": "ir-4.10_obj", - "name": "objective", - "prose": "Determine if the organization coordinates incident handling activities involving supply chain events with other organizations involved in the supply chain." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing supply chain coordination\n\nacquisition contracts\n\nservice-level agreements\n\nincident response plan\n\nsecurity plan\n\nincident response plans of other organization involved in supply chain activities\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident handling responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "ir-5", - "class": "SP800-53", - "title": "Incident Monitoring", - "props": [ - { - "name": "label", - "value": "IR-5" - }, - { - "name": "sort-id", - "value": "ir-05" - } - ], - "links": [ - { - "href": "#be95fb85-a53f-4624-bdbb-140075500aa3", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ir-5_smt", - "name": "statement", - "prose": "The organization tracks and documents information system security incidents." - }, - { - "id": "ir-5_gdn", - "name": "guidance", - "prose": "Documenting information system security incidents includes, for example, maintaining records about each incident, the status of the incident, and other pertinent information necessary for forensics, evaluating incident details, trends, and handling. Incident information can be obtained from a variety of sources including, for example, incident reports, incident response teams, audit monitoring, network monitoring, physical access monitoring, and user/administrator reports.", - "links": [ - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - }, - { - "href": "#pe-6", - "rel": "related" - }, - { - "href": "#sc-5", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "ir-5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-5[1]" - } - ], - "prose": "tracks information system security incidents; and" - }, - { - "id": "ir-5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-5[2]" - } - ], - "prose": "documents information system security incidents." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident monitoring\n\nincident response records and documentation\n\nincident response plan\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident monitoring responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident monitoring capability for the organization\n\nautomated mechanisms supporting and/or implementing tracking and documenting of system security incidents" - } - ] - } - ], - "controls": [ - { - "id": "ir-5.1", - "class": "SP800-53-enhancement", - "title": "Automated Tracking / Data Collection / Analysis", - "props": [ - { - "name": "label", - "value": "IR-5(1)" - }, - { - "name": "sort-id", - "value": "ir-05.01" - } - ], - "parts": [ - { - "id": "ir-5.1_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to assist in the tracking of security incidents and in the collection and analysis of incident information." - }, - { - "id": "ir-5.1_gdn", - "name": "guidance", - "prose": "Automated mechanisms for tracking security incidents and collecting/analyzing incident information include, for example, the Einstein network monitoring device and monitoring online Computer Incident Response Centers (CIRCs) or other electronic databases of incidents.", - "links": [ - { - "href": "#au-7", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - } - ] - }, - { - "id": "ir-5.1_obj", - "name": "objective", - "prose": "Determine if the organization employs automated mechanisms to assist in:", - "parts": [ - { - "id": "ir-5.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-5(1)[1]" - } - ], - "prose": "the tracking of security incidents;" - }, - { - "id": "ir-5.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-5(1)[2]" - } - ], - "prose": "the collection of incident information; and" - }, - { - "id": "ir-5.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-5(1)[3]" - } - ], - "prose": "the analysis of incident information." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident monitoring\n\nautomated mechanisms supporting incident monitoring\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nincident response plan\n\nsecurity plan\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident monitoring responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms assisting in tracking of security incidents and in the collection and analysis of incident information" - } - ] - } - ] - } - ] - }, - { - "id": "ir-6", - "class": "SP800-53", - "title": "Incident Reporting", - "params": [ - { - "id": "ir-6_prm_1", - "label": "organization-defined time period" - }, - { - "id": "ir-6_prm_2", - "label": "organization-defined authorities" - } - ], - "props": [ - { - "name": "label", - "value": "IR-6" - }, - { - "name": "sort-id", - "value": "ir-06" - } - ], - "links": [ - { - "href": "#be95fb85-a53f-4624-bdbb-140075500aa3", - "rel": "reference" - }, - { - "href": "#02631467-668b-4233-989b-3dfded2fd184", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ir-6_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ir-6_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Requires personnel to report suspected security incidents to the organizational incident response capability within {{ insert: param, ir-6_prm_1 }}; and" - }, - { - "id": "ir-6_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reports security incident information to {{ insert: param, ir-6_prm_2 }}." - } - ] - }, - { - "id": "ir-6_gdn", - "name": "guidance", - "prose": "The intent of this control is to address both specific incident reporting requirements within an organization and the formal incident reporting requirements for federal agencies and their subordinate organizations. Suspected security incidents include, for example, the receipt of suspicious email communications that can potentially contain malicious code. The types of security incidents reported, the content and timeliness of the reports, and the designated reporting authorities reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Current federal policy requires that all federal agencies (unless specifically exempted from such requirements) report security incidents to the United States Computer Emergency Readiness Team (US-CERT) within specified time frames designated in the US-CERT Concept of Operations for Federal Cyber Security Incident Handling.", - "links": [ - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-5", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - } - ] - }, - { - "id": "ir-6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-6.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-6(a)" - } - ], - "parts": [ - { - "id": "ir-6.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-6(a)[1]" - } - ], - "prose": "defines the time period within which personnel report suspected security incidents to the organizational incident response capability;" - }, - { - "id": "ir-6.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-6(a)[2]" - } - ], - "prose": "requires personnel to report suspected security incidents to the organizational incident response capability within the organization-defined time period;" - } - ] - }, - { - "id": "ir-6.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-6(b)" - } - ], - "parts": [ - { - "id": "ir-6.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-6(b)[1]" - } - ], - "prose": "defines authorities to whom security incident information is to be reported; and" - }, - { - "id": "ir-6.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-6(b)[2]" - } - ], - "prose": "reports security incident information to organization-defined authorities." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident reporting\n\nincident reporting records and documentation\n\nincident response plan\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident reporting responsibilities\n\norganizational personnel with information security responsibilities\n\npersonnel who have/should have reported incidents\n\npersonnel (authorities) to whom incident information is to be reported" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for incident reporting\n\nautomated mechanisms supporting and/or implementing incident reporting" - } - ] - } - ], - "controls": [ - { - "id": "ir-6.1", - "class": "SP800-53-enhancement", - "title": "Automated Reporting", - "props": [ - { - "name": "label", - "value": "IR-6(1)" - }, - { - "name": "sort-id", - "value": "ir-06.01" - } - ], - "parts": [ - { - "id": "ir-6.1_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to assist in the reporting of security incidents." - }, - { - "id": "ir-6.1_gdn", - "name": "guidance", - "links": [ - { - "href": "#ir-7", - "rel": "related" - } - ] - }, - { - "id": "ir-6.1_obj", - "name": "objective", - "prose": "Determine if the organization employs automated mechanisms to assist in the reporting of security incidents." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident reporting\n\nautomated mechanisms supporting incident reporting\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nincident response plan\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident reporting responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for incident reporting\n\nautomated mechanisms supporting and/or implementing reporting of security incidents" - } - ] - } - ] - }, - { - "id": "ir-6.2", - "class": "SP800-53-enhancement", - "title": "Vulnerabilities Related to Incidents", - "params": [ - { - "id": "ir-6.2_prm_1", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "IR-6(2)" - }, - { - "name": "sort-id", - "value": "ir-06.02" - } - ], - "parts": [ - { - "id": "ir-6.2_smt", - "name": "statement", - "prose": "The organization reports information system vulnerabilities associated with reported security incidents to {{ insert: param, ir-6.2_prm_1 }}." - }, - { - "id": "ir-6.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-6.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-6(2)[1]" - } - ], - "prose": "defines personnel or roles to whom information system vulnerabilities associated with reported security incidents are to be reported; and" - }, - { - "id": "ir-6.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-6(2)[2]" - } - ], - "prose": "reports information system vulnerabilities associated with reported security incidents to organization-defined personnel or roles." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident reporting\n\nincident response plan\n\nsecurity plan\n\nsecurity incident reports and associated information system vulnerabilities\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident reporting responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\npersonnel to whom vulnerabilities associated with security incidents are to be reported" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for incident reporting\n\nautomated mechanisms supporting and/or implementing reporting of vulnerabilities associated with security incidents" - } - ] - } - ] - }, - { - "id": "ir-6.3", - "class": "SP800-53-enhancement", - "title": "Coordination with Supply Chain", - "props": [ - { - "name": "label", - "value": "IR-6(3)" - }, - { - "name": "sort-id", - "value": "ir-06.03" - } - ], - "parts": [ - { - "id": "ir-6.3_smt", - "name": "statement", - "prose": "The organization provides security incident information to other organizations involved in the supply chain for information systems or information system components related to the incident." - }, - { - "id": "ir-6.3_gdn", - "name": "guidance", - "prose": "Organizations involved in supply chain activities include, for example, system/product developers, integrators, manufacturers, packagers, assemblers, distributors, vendors, and resellers. Supply chain incidents include, for example, compromises/breaches involving information system components, information technology products, development processes or personnel, and distribution processes or warehousing facilities. Organizations determine the appropriate information to share considering the value gained from support by external organizations with the potential for harm due to sensitive information being released to outside organizations of perhaps questionable trustworthiness." - }, - { - "id": "ir-6.3_obj", - "name": "objective", - "prose": "Determine if the organization provides security incident information to other organizations involved in the supply chain for information systems or information system components related to the incident." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing supply chain coordination\n\nacquisition contracts\n\nservice-level agreements\n\nincident response plan\n\nsecurity plan\n\nplans of other organization involved in supply chain activities\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident reporting responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for incident reporting\n\nautomated mechanisms supporting and/or implementing reporting of incident information involved in the supply chain" - } - ] - } - ] - } - ] - }, - { - "id": "ir-7", - "class": "SP800-53", - "title": "Incident Response Assistance", - "props": [ - { - "name": "label", - "value": "IR-7" - }, - { - "name": "sort-id", - "value": "ir-07" - } - ], - "parts": [ - { - "id": "ir-7_smt", - "name": "statement", - "prose": "The organization provides an incident response support resource, integral to the organizational incident response capability that offers advice and assistance to users of the information system for the handling and reporting of security incidents." - }, - { - "id": "ir-7_gdn", - "name": "guidance", - "prose": "Incident response support resources provided by organizations include, for example, help desks, assistance groups, and access to forensics services, when required.", - "links": [ - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-6", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - } - ] - }, - { - "id": "ir-7_obj", - "name": "objective", - "prose": "Determine if the organization provides an incident response support resource:", - "parts": [ - { - "id": "ir-7_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-7[1]" - } - ], - "prose": "that is integral to the organizational incident response capability; and" - }, - { - "id": "ir-7_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-7[2]" - } - ], - "prose": "that offers advice and assistance to users of the information system for the handling and reporting of security incidents." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident response assistance\n\nincident response plan\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident response assistance and support responsibilities\n\norganizational personnel with access to incident response support and assistance capability\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for incident response assistance\n\nautomated mechanisms supporting and/or implementing incident response assistance" - } - ] - } - ], - "controls": [ - { - "id": "ir-7.1", - "class": "SP800-53-enhancement", - "title": "Automation Support for Availability of Information / Support", - "props": [ - { - "name": "label", - "value": "IR-7(1)" - }, - { - "name": "sort-id", - "value": "ir-07.01" - } - ], - "parts": [ - { - "id": "ir-7.1_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to increase the availability of incident response-related information and support." - }, - { - "id": "ir-7.1_gdn", - "name": "guidance", - "prose": "Automated mechanisms can provide a push and/or pull capability for users to obtain incident response assistance. For example, individuals might have access to a website to query the assistance capability, or conversely, the assistance capability may have the ability to proactively send information to users (general distribution or targeted) as part of increasing understanding of current response capabilities and support." - }, - { - "id": "ir-7.1_obj", - "name": "objective", - "prose": "Determine if the organization employs automated mechanisms to increase the availability of incident response-related information and support." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident response assistance\n\nautomated mechanisms supporting incident response support and assistance\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nincident response plan\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident response support and assistance responsibilities\n\norganizational personnel with access to incident response support and assistance capability\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for incident response assistance\n\nautomated mechanisms supporting and/or implementing an increase in the availability of incident response information and support" - } - ] - } - ] - }, - { - "id": "ir-7.2", - "class": "SP800-53-enhancement", - "title": "Coordination with External Providers", - "props": [ - { - "name": "label", - "value": "IR-7(2)" - }, - { - "name": "sort-id", - "value": "ir-07.02" - } - ], - "parts": [ - { - "id": "ir-7.2_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ir-7.2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Establishes a direct, cooperative relationship between its incident response capability and external providers of information system protection capability; and" - }, - { - "id": "ir-7.2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Identifies organizational incident response team members to the external providers." - } - ] - }, - { - "id": "ir-7.2_gdn", - "name": "guidance", - "prose": "External providers of information system protection capability include, for example, the Computer Network Defense program within the U.S. Department of Defense. External providers help to protect, monitor, analyze, detect, and respond to unauthorized activity within organizational information systems and networks." - }, - { - "id": "ir-7.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-7.2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-7(2)(a)" - } - ], - "prose": "establishes a direct, cooperative relationship between its incident response capability and external providers of information system protection capability; and", - "links": [ - { - "href": "#ir-7.2_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ir-7.2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-7(2)(b)" - } - ], - "prose": "identifies organizational incident response team members to the external providers.", - "links": [ - { - "href": "#ir-7.2_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident response assistance\n\nincident response plan\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident response support and assistance responsibilities\n\nexternal providers of information system protection capability\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "ir-8", - "class": "SP800-53", - "title": "Incident Response Plan", - "params": [ - { - "id": "ir-8_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "ir-8_prm_2", - "label": "organization-defined incident response personnel (identified by name and/or by role) and organizational elements" - }, - { - "id": "ir-8_prm_3", - "label": "organization-defined frequency" - }, - { - "id": "ir-8_prm_4", - "label": "organization-defined incident response personnel (identified by name and/or by role) and organizational elements" - } - ], - "props": [ - { - "name": "label", - "value": "IR-8" - }, - { - "name": "sort-id", - "value": "ir-08" - } - ], - "links": [ - { - "href": "#be95fb85-a53f-4624-bdbb-140075500aa3", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ir-8_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ir-8_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops an incident response plan that:", - "parts": [ - { - "id": "ir-8_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Provides the organization with a roadmap for implementing its incident response capability;" - }, - { - "id": "ir-8_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Describes the structure and organization of the incident response capability;" - }, - { - "id": "ir-8_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Provides a high-level approach for how the incident response capability fits into the overall organization;" - }, - { - "id": "ir-8_smt.a.4", - "name": "item", - "props": [ - { - "name": "label", - "value": "4." - } - ], - "prose": "Meets the unique requirements of the organization, which relate to mission, size, structure, and functions;" - }, - { - "id": "ir-8_smt.a.5", - "name": "item", - "props": [ - { - "name": "label", - "value": "5." - } - ], - "prose": "Defines reportable incidents;" - }, - { - "id": "ir-8_smt.a.6", - "name": "item", - "props": [ - { - "name": "label", - "value": "6." - } - ], - "prose": "Provides metrics for measuring the incident response capability within the organization;" - }, - { - "id": "ir-8_smt.a.7", - "name": "item", - "props": [ - { - "name": "label", - "value": "7." - } - ], - "prose": "Defines the resources and management support needed to effectively maintain and mature an incident response capability; and" - }, - { - "id": "ir-8_smt.a.8", - "name": "item", - "props": [ - { - "name": "label", - "value": "8." - } - ], - "prose": "Is reviewed and approved by {{ insert: param, ir-8_prm_1 }};" - } - ] - }, - { - "id": "ir-8_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Distributes copies of the incident response plan to {{ insert: param, ir-8_prm_2 }};" - }, - { - "id": "ir-8_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Reviews the incident response plan {{ insert: param, ir-8_prm_3 }};" - }, - { - "id": "ir-8_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Updates the incident response plan to address system/organizational changes or problems encountered during plan implementation, execution, or testing;" - }, - { - "id": "ir-8_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Communicates incident response plan changes to {{ insert: param, ir-8_prm_4 }}; and" - }, - { - "id": "ir-8_smt.f", - "name": "item", - "props": [ - { - "name": "label", - "value": "f." - } - ], - "prose": "Protects the incident response plan from unauthorized disclosure and modification." - } - ] - }, - { - "id": "ir-8_gdn", - "name": "guidance", - "prose": "It is important that organizations develop and implement a coordinated approach to incident response. Organizational missions, business functions, strategies, goals, and objectives for incident response help to determine the structure of incident response capabilities. As part of a comprehensive incident response capability, organizations consider the coordination and sharing of information with external organizations, including, for example, external service providers and organizations involved in the supply chain for organizational information systems.", - "links": [ - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - } - ] - }, - { - "id": "ir-8_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-8.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(a)" - } - ], - "prose": "develops an incident response plan that:", - "parts": [ - { - "id": "ir-8.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(a)(1)" - } - ], - "prose": "provides the organization with a roadmap for implementing its incident response capability;" - }, - { - "id": "ir-8.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(a)(2)" - } - ], - "prose": "describes the structure and organization of the incident response capability;" - }, - { - "id": "ir-8.a.3_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(a)(3)" - } - ], - "prose": "provides a high-level approach for how the incident response capability fits into the overall organization;" - }, - { - "id": "ir-8.a.4_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(a)(4)" - } - ], - "prose": "meets the unique requirements of the organization, which relate to:", - "parts": [ - { - "id": "ir-8.a.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(a)(4)[1]" - } - ], - "prose": "mission;" - }, - { - "id": "ir-8.a.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(a)(4)[2]" - } - ], - "prose": "size;" - }, - { - "id": "ir-8.a.4_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(a)(4)[3]" - } - ], - "prose": "structure;" - }, - { - "id": "ir-8.a.4_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(a)(4)[4]" - } - ], - "prose": "functions;" - } - ] - }, - { - "id": "ir-8.a.5_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(a)(5)" - } - ], - "prose": "defines reportable incidents;" - }, - { - "id": "ir-8.a.6_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(a)(6)" - } - ], - "prose": "provides metrics for measuring the incident response capability within the organization;" - }, - { - "id": "ir-8.a.7_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(a)(7)" - } - ], - "prose": "defines the resources and management support needed to effectively maintain and mature an incident response capability;" - }, - { - "id": "ir-8.a.8_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(a)(8)" - } - ], - "parts": [ - { - "id": "ir-8.a.8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(a)(8)[1]" - } - ], - "prose": "defines personnel or roles to review and approve the incident response plan;" - }, - { - "id": "ir-8.a.8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(a)(8)[2]" - } - ], - "prose": "is reviewed and approved by organization-defined personnel or roles;" - } - ] - } - ] - }, - { - "id": "ir-8.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(b)" - } - ], - "parts": [ - { - "id": "ir-8.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(b)[1]" - } - ], - "parts": [ - { - "id": "ir-8.b_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(b)[1][a]" - } - ], - "prose": "defines incident response personnel (identified by name and/or by role) to whom copies of the incident response plan are to be distributed;" - }, - { - "id": "ir-8.b_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(b)[1][b]" - } - ], - "prose": "defines organizational elements to whom copies of the incident response plan are to be distributed;" - } - ] - }, - { - "id": "ir-8.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(b)[2]" - } - ], - "prose": "distributes copies of the incident response plan to organization-defined incident response personnel (identified by name and/or by role) and organizational elements;" - } - ] - }, - { - "id": "ir-8.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(c)" - } - ], - "parts": [ - { - "id": "ir-8.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(c)[1]" - } - ], - "prose": "defines the frequency to review the incident response plan;" - }, - { - "id": "ir-8.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(c)[2]" - } - ], - "prose": "reviews the incident response plan with the organization-defined frequency;" - } - ] - }, - { - "id": "ir-8.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(d)" - } - ], - "prose": "updates the incident response plan to address system/organizational changes or problems encountered during plan:", - "parts": [ - { - "id": "ir-8.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(d)[1]" - } - ], - "prose": "implementation;" - }, - { - "id": "ir-8.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(d)[2]" - } - ], - "prose": "execution; or" - }, - { - "id": "ir-8.d_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(d)[3]" - } - ], - "prose": "testing;" - } - ] - }, - { - "id": "ir-8.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(e)" - } - ], - "parts": [ - { - "id": "ir-8.e_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(e)[1]" - } - ], - "parts": [ - { - "id": "ir-8.e_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(e)[1][a]" - } - ], - "prose": "defines incident response personnel (identified by name and/or by role) to whom incident response plan changes are to be communicated;" - }, - { - "id": "ir-8.e_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(e)[1][b]" - } - ], - "prose": "defines organizational elements to whom incident response plan changes are to be communicated;" - } - ] - }, - { - "id": "ir-8.e_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(e)[2]" - } - ], - "prose": "communicates incident response plan changes to organization-defined incident response personnel (identified by name and/or by role) and organizational elements; and" - } - ] - }, - { - "id": "ir-8.f_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-8(f)" - } - ], - "prose": "protects the incident response plan from unauthorized disclosure and modification." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident response planning\n\nincident response plan\n\nrecords of incident response plan reviews and approvals\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident response planning responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational incident response plan and related organizational processes" - } - ] - } - ] - }, - { - "id": "ir-9", - "class": "SP800-53", - "title": "Information Spillage Response", - "params": [ - { - "id": "ir-9_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "ir-9_prm_2", - "label": "organization-defined actions" - } - ], - "props": [ - { - "name": "label", - "value": "IR-9" - }, - { - "name": "sort-id", - "value": "ir-09" - } - ], - "parts": [ - { - "id": "ir-9_smt", - "name": "statement", - "prose": "The organization responds to information spills by:", - "parts": [ - { - "id": "ir-9_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Identifying the specific information involved in the information system contamination;" - }, - { - "id": "ir-9_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Alerting {{ insert: param, ir-9_prm_1 }} of the information spill using a method of communication not associated with the spill;" - }, - { - "id": "ir-9_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Isolating the contaminated information system or system component;" - }, - { - "id": "ir-9_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Eradicating the information from the contaminated information system or component;" - }, - { - "id": "ir-9_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Identifying other information systems or system components that may have been subsequently contaminated; and" - }, - { - "id": "ir-9_smt.f", - "name": "item", - "props": [ - { - "name": "label", - "value": "f." - } - ], - "prose": "Performing other {{ insert: param, ir-9_prm_2 }}." - } - ] - }, - { - "id": "ir-9_gdn", - "name": "guidance", - "prose": "Information spillage refers to instances where either classified or sensitive information is inadvertently placed on information systems that are not authorized to process such information. Such information spills often occur when information that is initially thought to be of lower sensitivity is transmitted to an information system and then is subsequently determined to be of higher sensitivity. At that point, corrective action is required. The nature of the organizational response is generally based upon the degree of sensitivity of the spilled information (e.g., security category or classification level), the security capabilities of the information system, the specific nature of contaminated storage media, and the access authorizations (e.g., security clearances) of individuals with authorized access to the contaminated system. The methods used to communicate information about the spill after the fact do not involve methods directly associated with the actual spill to minimize the risk of further spreading the contamination before such contamination is isolated and eradicated." - }, - { - "id": "ir-9_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-9.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-9(a)" - } - ], - "prose": "responds to information spills by identifying the specific information causing the information system contamination;" - }, - { - "id": "ir-9.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-9(b)" - } - ], - "parts": [ - { - "id": "ir-9.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-9(b)[1]" - } - ], - "prose": "defines personnel to be alerted of the information spillage;" - }, - { - "id": "ir-9.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-9(b)[2]" - } - ], - "prose": "identifies a method of communication not associated with the information spill to use to alert organization-defined personnel of the spill;" - }, - { - "id": "ir-9.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-9(b)[3]" - } - ], - "prose": "responds to information spills by alerting organization-defined personnel of the information spill using a method of communication not associated with the spill;" - } - ] - }, - { - "id": "ir-9.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-9(c)" - } - ], - "prose": "responds to information spills by isolating the contaminated information system;" - }, - { - "id": "ir-9.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-9(d)" - } - ], - "prose": "responds to information spills by eradicating the information from the contaminated information system;" - }, - { - "id": "ir-9.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-9(e)" - } - ], - "prose": "responds to information spills by identifying other information systems that may have been subsequently contaminated;" - }, - { - "id": "ir-9.f_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-9(f)" - } - ], - "parts": [ - { - "id": "ir-9.f_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-9(f)[1]" - } - ], - "prose": "defines other actions to be performed in response to information spills; and" - }, - { - "id": "ir-9.f_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-9(f)[2]" - } - ], - "prose": "responds to information spills by performing other organization-defined actions." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing information spillage\n\nincident response plan\n\nrecords of information spillage alerts/notifications, list of personnel who should receive alerts of information spillage\n\nlist of actions to be performed regarding information spillage\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident response responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for information spillage response\n\nautomated mechanisms supporting and/or implementing information spillage response actions and related communications" - } - ] - } - ], - "controls": [ - { - "id": "ir-9.1", - "class": "SP800-53-enhancement", - "title": "Responsible Personnel", - "params": [ - { - "id": "ir-9.1_prm_1", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "IR-9(1)" - }, - { - "name": "sort-id", - "value": "ir-09.01" - } - ], - "parts": [ - { - "id": "ir-9.1_smt", - "name": "statement", - "prose": "The organization assigns {{ insert: param, ir-9.1_prm_1 }} with responsibility for responding to information spills." - }, - { - "id": "ir-9.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-9.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-9(1)[1]" - } - ], - "prose": "defines personnel with responsibility for responding to information spills; and" - }, - { - "id": "ir-9.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-9(1)[2]" - } - ], - "prose": "assigns organization-defined personnel with responsibility for responding to information spills." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing information spillage\n\nincident response plan\n\nlist of personnel responsible for responding to information spillage\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident response responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "ir-9.2", - "class": "SP800-53-enhancement", - "title": "Training", - "params": [ - { - "id": "ir-9.2_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "IR-9(2)" - }, - { - "name": "sort-id", - "value": "ir-09.02" - } - ], - "parts": [ - { - "id": "ir-9.2_smt", - "name": "statement", - "prose": "The organization provides information spillage response training {{ insert: param, ir-9.2_prm_1 }}." - }, - { - "id": "ir-9.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-9.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-9(2)[1]" - } - ], - "prose": "defines the frequency to provide information spillage response training; and" - }, - { - "id": "ir-9.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-9(2)[2]" - } - ], - "prose": "provides information spillage response training with the organization-defined frequency." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing information spillage response training\n\ninformation spillage response training curriculum\n\ninformation spillage response training materials\n\nincident response plan\n\ninformation spillage response training records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident response training responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "ir-9.3", - "class": "SP800-53-enhancement", - "title": "Post-spill Operations", - "params": [ - { - "id": "ir-9.3_prm_1", - "label": "organization-defined procedures" - } - ], - "props": [ - { - "name": "label", - "value": "IR-9(3)" - }, - { - "name": "sort-id", - "value": "ir-09.03" - } - ], - "parts": [ - { - "id": "ir-9.3_smt", - "name": "statement", - "prose": "The organization implements {{ insert: param, ir-9.3_prm_1 }} to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions." - }, - { - "id": "ir-9.3_gdn", - "name": "guidance", - "prose": "Correction actions for information systems contaminated due to information spillages may be very time-consuming. During those periods, personnel may not have access to the contaminated systems, which may potentially affect their ability to conduct organizational business." - }, - { - "id": "ir-9.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-9.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-9(3)[1]" - } - ], - "prose": "defines procedures that ensure organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions; and" - }, - { - "id": "ir-9.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-9(3)[2]" - } - ], - "prose": "implements organization-defined procedures to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident handling\n\nprocedures addressing information spillage\n\nincident response plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident response responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for post-spill operations" - } - ] - } - ] - }, - { - "id": "ir-9.4", - "class": "SP800-53-enhancement", - "title": "Exposure to Unauthorized Personnel", - "params": [ - { - "id": "ir-9.4_prm_1", - "label": "organization-defined security safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "IR-9(4)" - }, - { - "name": "sort-id", - "value": "ir-09.04" - } - ], - "parts": [ - { - "id": "ir-9.4_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, ir-9.4_prm_1 }} for personnel exposed to information not within assigned access authorizations." - }, - { - "id": "ir-9.4_gdn", - "name": "guidance", - "prose": "Security safeguards include, for example, making personnel exposed to spilled information aware of the federal laws, directives, policies, and/or regulations regarding the information and the restrictions imposed based on exposure to such information." - }, - { - "id": "ir-9.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ir-9.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-9(4)[1]" - } - ], - "prose": "defines security safeguards to be employed for personnel exposed to information not within assigned access authorizations; and" - }, - { - "id": "ir-9.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "IR-9(4)[2]" - } - ], - "prose": "employs organization-defined security safeguards for personnel exposed to information not within assigned access authorizations." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident handling\n\nprocedures addressing information spillage\n\nincident response plan\n\nsecurity safeguards regarding information spillage/exposure to unauthorized personnel\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident response responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for dealing with information exposed to unauthorized personnel\n\nautomated mechanisms supporting and/or implementing safeguards for personnel exposed to information not within assigned access authorizations" - } - ] - } - ] - } - ] - }, - { - "id": "ir-10", - "class": "SP800-53", - "title": "Integrated Information Security Analysis Team", - "props": [ - { - "name": "label", - "value": "IR-10" - }, - { - "name": "sort-id", - "value": "ir-10" - } - ], - "parts": [ - { - "id": "ir-10_smt", - "name": "statement", - "prose": "The organization establishes an integrated team of forensic/malicious code analysts, tool developers, and real-time operations personnel." - }, - { - "id": "ir-10_gdn", - "name": "guidance", - "prose": "Having an integrated team for incident response facilitates information sharing. Such capability allows organizational personnel, including developers, implementers, and operators, to leverage the team knowledge of the threat in order to implement defensive measures that will enable organizations to deter intrusions more effectively. Moreover, it promotes the rapid detection of intrusions, development of appropriate mitigations, and the deployment of effective defensive measures. For example, when an intrusion is detected, the integrated security analysis team can rapidly develop an appropriate response for operators to implement, correlate the new incident with information on past intrusions, and augment ongoing intelligence development. This enables the team to identify adversary TTPs that are linked to the operations tempo or to specific missions/business functions, and to define responsive actions in a way that does not disrupt the mission/business operations. Ideally, information security analysis teams are distributed within organizations to make the capability more resilient." - }, - { - "id": "ir-10_obj", - "name": "objective", - "prose": "Determine if the organization establishes an integrated team of forensic/malicious code analyst, tool developers, and real-time operations personnel." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Incident response policy\n\nprocedures addressing incident response planning and security analysis team integration\n\nincident response plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with incident response and information security analysis responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel participating on integrated security analysis teams" - } - ] - } - ] - } - ] - }, - { - "id": "ma", - "class": "family", - "title": "Maintenance", - "controls": [ - { - "id": "ma-1", - "class": "SP800-53", - "title": "System Maintenance Policy and Procedures", - "params": [ - { - "id": "ma-1_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "ma-1_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "ma-1_prm_3", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "MA-1" - }, - { - "name": "sort-id", - "value": "ma-01" - } - ], - "links": [ - { - "href": "#5c201b63-0768-417b-ac22-3f014e3941b2", - "rel": "reference" - }, - { - "href": "#9cb3d8fe-2127-48ba-821e-cdd2d7aee921", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ma-1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ma-1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops, documents, and disseminates to {{ insert: param, ma-1_prm_1 }}:", - "parts": [ - { - "id": "ma-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "A system maintenance policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "ma-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the system maintenance policy and associated system maintenance controls; and" - } - ] - }, - { - "id": "ma-1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the current:", - "parts": [ - { - "id": "ma-1_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "System maintenance policy {{ insert: param, ma-1_prm_2 }}; and" - }, - { - "id": "ma-1_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "System maintenance procedures {{ insert: param, ma-1_prm_3 }}." - } - ] - } - ] - }, - { - "id": "ma-1_gdn", - "name": "guidance", - "prose": "This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the MA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures.", - "links": [ - { - "href": "#pm-9", - "rel": "related" - } - ] - }, - { - "id": "ma-1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ma-1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(a)" - } - ], - "parts": [ - { - "id": "ma-1.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(a)(1)" - } - ], - "parts": [ - { - "id": "ma-1.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(a)(1)[1]" - } - ], - "prose": "develops and documents a system maintenance policy that addresses:", - "parts": [ - { - "id": "ma-1.a.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(a)(1)[1][a]" - } - ], - "prose": "purpose;" - }, - { - "id": "ma-1.a.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(a)(1)[1][b]" - } - ], - "prose": "scope;" - }, - { - "id": "ma-1.a.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(a)(1)[1][c]" - } - ], - "prose": "roles;" - }, - { - "id": "ma-1.a.1_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(a)(1)[1][d]" - } - ], - "prose": "responsibilities;" - }, - { - "id": "ma-1.a.1_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(a)(1)[1][e]" - } - ], - "prose": "management commitment;" - }, - { - "id": "ma-1.a.1_obj.1.f", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(a)(1)[1][f]" - } - ], - "prose": "coordination among organizational entities;" - }, - { - "id": "ma-1.a.1_obj.1.g", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(a)(1)[1][g]" - } - ], - "prose": "compliance;" - } - ] - }, - { - "id": "ma-1.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(a)(1)[2]" - } - ], - "prose": "defines personnel or roles to whom the system maintenance policy is to be disseminated;" - }, - { - "id": "ma-1.a.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(a)(1)[3]" - } - ], - "prose": "disseminates the system maintenance policy to organization-defined personnel or roles;" - } - ] - }, - { - "id": "ma-1.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(a)(2)" - } - ], - "parts": [ - { - "id": "ma-1.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(a)(2)[1]" - } - ], - "prose": "develops and documents procedures to facilitate the implementation of the maintenance policy and associated system maintenance controls;" - }, - { - "id": "ma-1.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(a)(2)[2]" - } - ], - "prose": "defines personnel or roles to whom the procedures are to be disseminated;" - }, - { - "id": "ma-1.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(a)(2)[3]" - } - ], - "prose": "disseminates the procedures to organization-defined personnel or roles;" - } - ] - } - ] - }, - { - "id": "ma-1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(b)" - } - ], - "parts": [ - { - "id": "ma-1.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(b)(1)" - } - ], - "parts": [ - { - "id": "ma-1.b.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(b)(1)[1]" - } - ], - "prose": "defines the frequency to review and update the current system maintenance policy;" - }, - { - "id": "ma-1.b.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(b)(1)[2]" - } - ], - "prose": "reviews and updates the current system maintenance policy with the organization-defined frequency;" - } - ] - }, - { - "id": "ma-1.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(b)(2)" - } - ], - "parts": [ - { - "id": "ma-1.b.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(b)(2)[1]" - } - ], - "prose": "defines the frequency to review and update the current system maintenance procedures; and" - }, - { - "id": "ma-1.b.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-1(b)(2)[2]" - } - ], - "prose": "reviews and updates the current system maintenance procedures with the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Maintenance policy and procedures\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with maintenance responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "ma-2", - "class": "SP800-53", - "title": "Controlled Maintenance", - "params": [ - { - "id": "ma-2_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "ma-2_prm_2", - "label": "organization-defined maintenance-related information" - } - ], - "props": [ - { - "name": "label", - "value": "MA-2" - }, - { - "name": "sort-id", - "value": "ma-02" - } - ], - "parts": [ - { - "id": "ma-2_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ma-2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Schedules, performs, documents, and reviews records of maintenance and repairs on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements;" - }, - { - "id": "ma-2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Approves and monitors all maintenance activities, whether performed on site or remotely and whether the equipment is serviced on site or removed to another location;" - }, - { - "id": "ma-2_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Requires that {{ insert: param, ma-2_prm_1 }} explicitly approve the removal of the information system or system components from organizational facilities for off-site maintenance or repairs;" - }, - { - "id": "ma-2_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Sanitizes equipment to remove all information from associated media prior to removal from organizational facilities for off-site maintenance or repairs;" - }, - { - "id": "ma-2_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Checks all potentially impacted security controls to verify that the controls are still functioning properly following maintenance or repair actions; and" - }, - { - "id": "ma-2_smt.f", - "name": "item", - "props": [ - { - "name": "label", - "value": "f." - } - ], - "prose": "Includes {{ insert: param, ma-2_prm_2 }} in organizational maintenance records." - } - ] - }, - { - "id": "ma-2_gdn", - "name": "guidance", - "prose": "This control addresses the information security aspects of the information system maintenance program and applies to all types of maintenance to any system component (including applications) conducted by any local or nonlocal entity (e.g., in-contract, warranty, in-house, software maintenance agreement). System maintenance also includes those components not directly associated with information processing and/or data/information retention such as scanners, copiers, and printers. Information necessary for creating effective maintenance records includes, for example: (i) date and time of maintenance; (ii) name of individuals or group performing the maintenance; (iii) name of escort, if necessary; (iv) a description of the maintenance performed; and (v) information system components/equipment removed or replaced (including identification numbers, if applicable). The level of detail included in maintenance records can be informed by the security categories of organizational information systems. Organizations consider supply chain issues associated with replacement components for information systems.", - "links": [ - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#mp-6", - "rel": "related" - }, - { - "href": "#pe-16", - "rel": "related" - }, - { - "href": "#sa-12", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - } - ] - }, - { - "id": "ma-2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ma-2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(a)" - } - ], - "parts": [ - { - "id": "ma-2.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(a)[1]" - } - ], - "prose": "schedules maintenance and repairs on information system components in accordance with:", - "parts": [ - { - "id": "ma-2.a_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(a)[1][a]" - } - ], - "prose": "manufacturer or vendor specifications; and/or" - }, - { - "id": "ma-2.a_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(a)[1][b]" - } - ], - "prose": "organizational requirements;" - } - ] - }, - { - "id": "ma-2.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(a)[2]" - } - ], - "prose": "performs maintenance and repairs on information system components in accordance with:", - "parts": [ - { - "id": "ma-2.a_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(a)[2][a]" - } - ], - "prose": "manufacturer or vendor specifications; and/or" - }, - { - "id": "ma-2.a_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(a)[2][b]" - } - ], - "prose": "organizational requirements;" - } - ] - }, - { - "id": "ma-2.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(a)[3]" - } - ], - "prose": "documents maintenance and repairs on information system components in accordance with:", - "parts": [ - { - "id": "ma-2.a_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(a)[3][a]" - } - ], - "prose": "manufacturer or vendor specifications; and/or" - }, - { - "id": "ma-2.a_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(a)[3][b]" - } - ], - "prose": "organizational requirements;" - } - ] - }, - { - "id": "ma-2.a_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(a)[4]" - } - ], - "prose": "reviews records of maintenance and repairs on information system components in accordance with:", - "parts": [ - { - "id": "ma-2.a_obj.4.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(a)[4][a]" - } - ], - "prose": "manufacturer or vendor specifications; and/or" - }, - { - "id": "ma-2.a_obj.4.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(a)[4][b]" - } - ], - "prose": "organizational requirements;" - } - ] - } - ] - }, - { - "id": "ma-2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(b)" - } - ], - "parts": [ - { - "id": "ma-2.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(b)[1]" - } - ], - "prose": "approves all maintenance activities, whether performed on site or remotely and whether the equipment is serviced on site or removed to another location;" - }, - { - "id": "ma-2.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(b)[2]" - } - ], - "prose": "monitors all maintenance activities, whether performed on site or remotely and whether the equipment is serviced on site or removed to another location;" - } - ] - }, - { - "id": "ma-2.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(c)" - } - ], - "parts": [ - { - "id": "ma-2.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(c)[1]" - } - ], - "prose": "defines personnel or roles required to explicitly approve the removal of the information system or system components from organizational facilities for off-site maintenance or repairs;" - }, - { - "id": "ma-2.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(c)[2]" - } - ], - "prose": "requires that organization-defined personnel or roles explicitly approve the removal of the information system or system components from organizational facilities for off-site maintenance or repairs;" - } - ] - }, - { - "id": "ma-2.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(d)" - } - ], - "prose": "sanitizes equipment to remove all information from associated media prior to removal from organizational facilities for off-site maintenance or repairs;" - }, - { - "id": "ma-2.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(e)" - } - ], - "prose": "checks all potentially impacted security controls to verify that the controls are still functioning properly following maintenance or repair actions;" - }, - { - "id": "ma-2.f_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(f)" - } - ], - "parts": [ - { - "id": "ma-2.f_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(f)[1]" - } - ], - "prose": "defines maintenance-related information to be included in organizational maintenance records; and" - }, - { - "id": "ma-2.f_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(f)[2]" - } - ], - "prose": "includes organization-defined maintenance-related information in organizational maintenance records." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing controlled information system maintenance\n\nmaintenance records\n\nmanufacturer/vendor maintenance specifications\n\nequipment sanitization records\n\nmedia sanitization records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel responsible for media sanitization\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for scheduling, performing, documenting, reviewing, approving, and monitoring maintenance and repairs for the information system\n\norganizational processes for sanitizing information system components\n\nautomated mechanisms supporting and/or implementing controlled maintenance\n\nautomated mechanisms implementing sanitization of information system components" - } - ] - } - ], - "controls": [ - { - "id": "ma-2.1", - "class": "SP800-53-enhancement", - "title": "Record Content", - "props": [ - { - "name": "label", - "value": "MA-2(1)" - }, - { - "name": "sort-id", - "value": "ma-02.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#ma-2", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ma-2.2", - "class": "SP800-53-enhancement", - "title": "Automated Maintenance Activities", - "props": [ - { - "name": "label", - "value": "MA-2(2)" - }, - { - "name": "sort-id", - "value": "ma-02.02" - } - ], - "parts": [ - { - "id": "ma-2.2_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ma-2.2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Employs automated mechanisms to schedule, conduct, and document maintenance and repairs; and" - }, - { - "id": "ma-2.2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Produces up-to date, accurate, and complete records of all maintenance and repair actions requested, scheduled, in process, and completed." - } - ] - }, - { - "id": "ma-2.2_gdn", - "name": "guidance", - "links": [ - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#ma-3", - "rel": "related" - } - ] - }, - { - "id": "ma-2.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ma-2.2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(2)(a)" - } - ], - "prose": "employs automated mechanisms to:", - "parts": [ - { - "id": "ma-2.2.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(2)(a)[1]" - } - ], - "prose": "schedule maintenance and repairs;" - }, - { - "id": "ma-2.2.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(2)(a)[2]" - } - ], - "prose": "conduct maintenance and repairs;" - }, - { - "id": "ma-2.2.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(2)(a)[3]" - } - ], - "prose": "document maintenance and repairs;" - } - ], - "links": [ - { - "href": "#ma-2.2_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ma-2.2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(2)(b)" - } - ], - "prose": "produces up-to-date, accurate, and complete records of all maintenance and repair actions:", - "parts": [ - { - "id": "ma-2.2.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(2)(b)[1]" - } - ], - "prose": "requested;" - }, - { - "id": "ma-2.2.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(2)(b)[2]" - } - ], - "prose": "scheduled;" - }, - { - "id": "ma-2.2.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(2)(b)[3]" - } - ], - "prose": "in process; and" - }, - { - "id": "ma-2.2.b_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-2(2)(b)[4]" - } - ], - "prose": "completed." - } - ], - "links": [ - { - "href": "#ma-2.2_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing controlled information system maintenance\n\nautomated mechanisms supporting information system maintenance activities\n\ninformation system configuration settings and associated documentation\n\nmaintenance records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing controlled maintenance\n\nautomated mechanisms supporting and/or implementing production of records of maintenance and repair actions" - } - ] - } - ] - } - ] - }, - { - "id": "ma-3", - "class": "SP800-53", - "title": "Maintenance Tools", - "props": [ - { - "name": "label", - "value": "MA-3" - }, - { - "name": "sort-id", - "value": "ma-03" - } - ], - "links": [ - { - "href": "#263823e0-a971-4b00-959d-315b26278b22", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ma-3_smt", - "name": "statement", - "prose": "The organization approves, controls, and monitors information system maintenance tools." - }, - { - "id": "ma-3_gdn", - "name": "guidance", - "prose": "This control addresses security-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational information systems. Maintenance tools can include hardware, software, and firmware items. Maintenance tools are potential vehicles for transporting malicious code, either intentionally or unintentionally, into a facility and subsequently into organizational information systems. Maintenance tools can include, for example, hardware/software diagnostic test equipment and hardware/software packet sniffers. This control does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing “ping,” “ls,” “ipconfig, or the hardware and software implementing the monitoring port of an Ethernet switch.", - "links": [ - { - "href": "#ma-2", - "rel": "related" - }, - { - "href": "#ma-5", - "rel": "related" - }, - { - "href": "#mp-6", - "rel": "related" - } - ] - }, - { - "id": "ma-3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ma-3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-3[1]" - } - ], - "prose": "approves information system maintenance tools;" - }, - { - "id": "ma-3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-3[2]" - } - ], - "prose": "controls information system maintenance tools; and" - }, - { - "id": "ma-3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-3[3]" - } - ], - "prose": "monitors information system maintenance tools." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing information system maintenance tools\n\ninformation system maintenance tools and associated documentation\n\nmaintenance records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for approving, controlling, and monitoring maintenance tools\n\nautomated mechanisms supporting and/or implementing approval, control, and/or monitoring of maintenance tools" - } - ] - } - ], - "controls": [ - { - "id": "ma-3.1", - "class": "SP800-53-enhancement", - "title": "Inspect Tools", - "props": [ - { - "name": "label", - "value": "MA-3(1)" - }, - { - "name": "sort-id", - "value": "ma-03.01" - } - ], - "parts": [ - { - "id": "ma-3.1_smt", - "name": "statement", - "prose": "The organization inspects the maintenance tools carried into a facility by maintenance personnel for improper or unauthorized modifications." - }, - { - "id": "ma-3.1_gdn", - "name": "guidance", - "prose": "If, upon inspection of maintenance tools, organizations determine that the tools have been modified in an improper/unauthorized manner or contain malicious code, the incident is handled consistent with organizational policies and procedures for incident handling.", - "links": [ - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "ma-3.1_obj", - "name": "objective", - "prose": "Determine if the organization inspects the maintenance tools carried into a facility by maintenance personnel for improper or unauthorized modifications." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing information system maintenance tools\n\ninformation system maintenance tools and associated documentation\n\nmaintenance tool inspection records\n\nmaintenance records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for inspecting maintenance tools\n\nautomated mechanisms supporting and/or implementing inspection of maintenance tools" - } - ] - } - ] - }, - { - "id": "ma-3.2", - "class": "SP800-53-enhancement", - "title": "Inspect Media", - "props": [ - { - "name": "label", - "value": "MA-3(2)" - }, - { - "name": "sort-id", - "value": "ma-03.02" - } - ], - "parts": [ - { - "id": "ma-3.2_smt", - "name": "statement", - "prose": "The organization checks media containing diagnostic and test programs for malicious code before the media are used in the information system." - }, - { - "id": "ma-3.2_gdn", - "name": "guidance", - "prose": "If, upon inspection of media containing maintenance diagnostic and test programs, organizations determine that the media contain malicious code, the incident is handled consistent with organizational incident handling policies and procedures.", - "links": [ - { - "href": "#si-3", - "rel": "related" - } - ] - }, - { - "id": "ma-3.2_obj", - "name": "objective", - "prose": "Determine if the organization checks media containing diagnostic and test programs for malicious code before the media are used in the information system." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing information system maintenance tools\n\ninformation system maintenance tools and associated documentation\n\nmaintenance records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational process for inspecting media for malicious code\n\nautomated mechanisms supporting and/or implementing inspection of media used for maintenance" - } - ] - } - ] - }, - { - "id": "ma-3.3", - "class": "SP800-53-enhancement", - "title": "Prevent Unauthorized Removal", - "params": [ - { - "id": "ma-3.3_prm_1", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "MA-3(3)" - }, - { - "name": "sort-id", - "value": "ma-03.03" - } - ], - "parts": [ - { - "id": "ma-3.3_smt", - "name": "statement", - "prose": "The organization prevents the unauthorized removal of maintenance equipment containing organizational information by:", - "parts": [ - { - "id": "ma-3.3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Verifying that there is no organizational information contained on the equipment;" - }, - { - "id": "ma-3.3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Sanitizing or destroying the equipment;" - }, - { - "id": "ma-3.3_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Retaining the equipment within the facility; or" - }, - { - "id": "ma-3.3_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "(d)" - } - ], - "prose": "Obtaining an exemption from {{ insert: param, ma-3.3_prm_1 }} explicitly authorizing removal of the equipment from the facility." - } - ] - }, - { - "id": "ma-3.3_gdn", - "name": "guidance", - "prose": "Organizational information includes all information specifically owned by organizations and information provided to organizations in which organizations serve as information stewards." - }, - { - "id": "ma-3.3_obj", - "name": "objective", - "prose": "Determine if the organization prevents the unauthorized removal of maintenance equipment containing organizational information by:", - "parts": [ - { - "id": "ma-3.3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-3(3)(a)" - } - ], - "prose": "verifying that there is no organizational information contained on the equipment;", - "links": [ - { - "href": "#ma-3.3_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ma-3.3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-3(3)(b)" - } - ], - "prose": "sanitizing or destroying the equipment;", - "links": [ - { - "href": "#ma-3.3_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "ma-3.3.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-3(3)(c)" - } - ], - "prose": "retaining the equipment within the facility; or", - "links": [ - { - "href": "#ma-3.3_smt.c", - "rel": "corresp" - } - ] - }, - { - "id": "ma-3.3.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-3(3)(d)" - } - ], - "parts": [ - { - "id": "ma-3.3.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-3(3)(d)[1]" - } - ], - "prose": "defining personnel or roles that can grant an exemption from explicitly authorizing removal of the equipment from the facility; and" - }, - { - "id": "ma-3.3.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-3(3)(d)[2]" - } - ], - "prose": "obtaining an exemption from organization-defined personnel or roles explicitly authorizing removal of the equipment from the facility." - } - ], - "links": [ - { - "href": "#ma-3.3_smt.d", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing information system maintenance tools\n\ninformation system maintenance tools and associated documentation\n\nmaintenance records\n\nequipment sanitization records\n\nmedia sanitization records\n\nexemptions for equipment removal\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel responsible for media sanitization" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational process for preventing unauthorized removal of information\n\nautomated mechanisms supporting media sanitization or destruction of equipment\n\nautomated mechanisms supporting verification of media sanitization" - } - ] - } - ] - }, - { - "id": "ma-3.4", - "class": "SP800-53-enhancement", - "title": "Restricted Tool Use", - "props": [ - { - "name": "label", - "value": "MA-3(4)" - }, - { - "name": "sort-id", - "value": "ma-03.04" - } - ], - "parts": [ - { - "id": "ma-3.4_smt", - "name": "statement", - "prose": "The information system restricts the use of maintenance tools to authorized personnel only." - }, - { - "id": "ma-3.4_gdn", - "name": "guidance", - "prose": "This control enhancement applies to information systems that are used to carry out maintenance functions.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-5", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - } - ] - }, - { - "id": "ma-3.4_obj", - "name": "objective", - "prose": "Determine if the organization restricts the use of maintenance tools to authorized personnel only." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing information system maintenance tools\n\ninformation system maintenance tools and associated documentation\n\nlist of personnel authorized to use maintenance tools\n\nmaintenance tool usage records\n\nmaintenance records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational process for restricting use of maintenance tools\n\nautomated mechanisms supporting and/or implementing restricted use of maintenance tools" - } - ] - } - ] - } - ] - }, - { - "id": "ma-4", - "class": "SP800-53", - "title": "Nonlocal Maintenance", - "props": [ - { - "name": "label", - "value": "MA-4" - }, - { - "name": "sort-id", - "value": "ma-04" - } - ], - "links": [ - { - "href": "#d715b234-9b5b-4e07-b1ed-99836727664d", - "rel": "reference" - }, - { - "href": "#f2dbd4ec-c413-4714-b85b-6b7184d1c195", - "rel": "reference" - }, - { - "href": "#c80c10b3-1294-4984-a4cc-d1733ca432b9", - "rel": "reference" - }, - { - "href": "#644f44a9-a2de-4494-9c04-cd37fba45471", - "rel": "reference" - }, - { - "href": "#263823e0-a971-4b00-959d-315b26278b22", - "rel": "reference" - }, - { - "href": "#a4aa9645-9a8a-4b51-90a9-e223250f9a75", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ma-4_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ma-4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Approves and monitors nonlocal maintenance and diagnostic activities;" - }, - { - "id": "ma-4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Allows the use of nonlocal maintenance and diagnostic tools only as consistent with organizational policy and documented in the security plan for the information system;" - }, - { - "id": "ma-4_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Employs strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions;" - }, - { - "id": "ma-4_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Maintains records for nonlocal maintenance and diagnostic activities; and" - }, - { - "id": "ma-4_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Terminates session and network connections when nonlocal maintenance is completed." - } - ] - }, - { - "id": "ma-4_gdn", - "name": "guidance", - "prose": "Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. Authentication techniques used in the establishment of nonlocal maintenance and diagnostic sessions reflect the network access requirements in IA-2. Typically, strong authentication requires authenticators that are resistant to replay attacks and employ multifactor authentication. Strong authenticators include, for example, PKI where certificates are stored on a token protected by a password, passphrase, or biometric. Enforcing requirements in MA-4 is accomplished in part by other controls.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-3", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "#ma-2", - "rel": "related" - }, - { - "href": "#ma-5", - "rel": "related" - }, - { - "href": "#mp-6", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-10", - "rel": "related" - }, - { - "href": "#sc-17", - "rel": "related" - } - ] - }, - { - "id": "ma-4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ma-4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(a)" - } - ], - "parts": [ - { - "id": "ma-4.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(a)[1]" - } - ], - "prose": "approves nonlocal maintenance and diagnostic activities;" - }, - { - "id": "ma-4.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(a)[2]" - } - ], - "prose": "monitors nonlocal maintenance and diagnostic activities;" - } - ] - }, - { - "id": "ma-4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(b)" - } - ], - "prose": "allows the use of nonlocal maintenance and diagnostic tools only:", - "parts": [ - { - "id": "ma-4.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(b)[1]" - } - ], - "prose": "as consistent with organizational policy;" - }, - { - "id": "ma-4.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(b)[2]" - } - ], - "prose": "as documented in the security plan for the information system;" - } - ] - }, - { - "id": "ma-4.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(c)" - } - ], - "prose": "employs strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions;" - }, - { - "id": "ma-4.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(d)" - } - ], - "prose": "maintains records for nonlocal maintenance and diagnostic activities;" - }, - { - "id": "ma-4.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(e)" - } - ], - "parts": [ - { - "id": "ma-4.e_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(e)[1]" - } - ], - "prose": "terminates sessions when nonlocal maintenance or diagnostics is completed; and" - }, - { - "id": "ma-4.e_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(e)[2]" - } - ], - "prose": "terminates network connections when nonlocal maintenance or diagnostics is completed." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing nonlocal information system maintenance\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nmaintenance records\n\ndiagnostic records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing nonlocal maintenance\n\nautomated mechanisms implementing, supporting, and/or managing nonlocal maintenance\n\nautomated mechanisms for strong authentication of nonlocal maintenance diagnostic sessions\n\nautomated mechanisms for terminating nonlocal maintenance sessions and network connections" - } - ] - } - ], - "controls": [ - { - "id": "ma-4.1", - "class": "SP800-53-enhancement", - "title": "Auditing and Review", - "params": [ - { - "id": "ma-4.1_prm_1", - "label": "organization-defined audit events" - } - ], - "props": [ - { - "name": "label", - "value": "MA-4(1)" - }, - { - "name": "sort-id", - "value": "ma-04.01" - } - ], - "parts": [ - { - "id": "ma-4.1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ma-4.1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Audits nonlocal maintenance and diagnostic sessions {{ insert: param, ma-4.1_prm_1 }}; and" - }, - { - "id": "ma-4.1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Reviews the records of the maintenance and diagnostic sessions." - } - ] - }, - { - "id": "ma-4.1_gdn", - "name": "guidance", - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - } - ] - }, - { - "id": "ma-4.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ma-4.1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(1)(a)" - } - ], - "parts": [ - { - "id": "ma-4.1.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(1)(a)[1]" - } - ], - "prose": "defines audit events to audit nonlocal maintenance and diagnostic sessions;" - }, - { - "id": "ma-4.1.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(1)(a)[2]" - } - ], - "prose": "audits organization-defined audit events for non-local maintenance and diagnostic sessions; and" - } - ], - "links": [ - { - "href": "#ma-4.1_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ma-4.1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(1)(b)" - } - ], - "prose": "reviews records of the maintenance and diagnostic sessions.", - "links": [ - { - "href": "#ma-4.1_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing nonlocal information system maintenance\n\nlist of audit events\n\ninformation system configuration settings and associated documentation\n\nmaintenance records\n\ndiagnostic records\n\naudit records\n\nreviews of maintenance and diagnostic session records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with audit and review responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for audit and review of nonlocal maintenance\n\nautomated mechanisms supporting and/or implementing audit and review of nonlocal maintenance" - } - ] - } - ] - }, - { - "id": "ma-4.2", - "class": "SP800-53-enhancement", - "title": "Document Nonlocal Maintenance", - "props": [ - { - "name": "label", - "value": "MA-4(2)" - }, - { - "name": "sort-id", - "value": "ma-04.02" - } - ], - "parts": [ - { - "id": "ma-4.2_smt", - "name": "statement", - "prose": "The organization documents in the security plan for the information system, the policies and procedures for the establishment and use of nonlocal maintenance and diagnostic connections." - }, - { - "id": "ma-4.2_obj", - "name": "objective", - "prose": "Determine if the organization documents in the security plan for the information system:", - "parts": [ - { - "id": "ma-4.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(2)[1]" - } - ], - "prose": "the policies for the establishment and use of nonlocal maintenance and diagnostic connections; and" - }, - { - "id": "ma-4.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(2)[2]" - } - ], - "prose": "the procedures for the establishment and use of nonlocal maintenance and diagnostic connections." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing non-local information system maintenance\n\nsecurity plan\n\nmaintenance records\n\ndiagnostic records\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "ma-4.3", - "class": "SP800-53-enhancement", - "title": "Comparable Security / Sanitization", - "props": [ - { - "name": "label", - "value": "MA-4(3)" - }, - { - "name": "sort-id", - "value": "ma-04.03" - } - ], - "parts": [ - { - "id": "ma-4.3_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ma-4.3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Requires that nonlocal maintenance and diagnostic services be performed from an information system that implements a security capability comparable to the capability implemented on the system being serviced; or" - }, - { - "id": "ma-4.3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Removes the component to be serviced from the information system prior to nonlocal maintenance or diagnostic services, sanitizes the component (with regard to organizational information) before removal from organizational facilities, and after the service is performed, inspects and sanitizes the component (with regard to potentially malicious software) before reconnecting the component to the information system." - } - ] - }, - { - "id": "ma-4.3_gdn", - "name": "guidance", - "prose": "Comparable security capability on information systems, diagnostic tools, and equipment providing maintenance services implies that the implemented security controls on those systems, tools, and equipment are at least as comprehensive as the controls on the information system being serviced.", - "links": [ - { - "href": "#ma-3", - "rel": "related" - }, - { - "href": "#sa-12", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "ma-4.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ma-4.3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(3)(a)" - } - ], - "prose": "requires that nonlocal maintenance and diagnostic services be performed from an information system that implements a security capability comparable to the capability implemented on the system being serviced; or", - "links": [ - { - "href": "#ma-4.3_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ma-4.3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(3)(b)" - } - ], - "parts": [ - { - "id": "ma-4.3.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(3)(b)[1]" - } - ], - "prose": "removes the component to be serviced from the information system;" - }, - { - "id": "ma-4.3.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(3)(b)[2]" - } - ], - "prose": "sanitizes the component (with regard to organizational information) prior to nonlocal maintenance or diagnostic services and/or before removal from organizational facilities; and" - }, - { - "id": "ma-4.3.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(3)(b)[3]" - } - ], - "prose": "inspects and sanitizes the component (with regard to potentially malicious software) after service is performed on the component and before reconnecting the component to the information system." - } - ], - "links": [ - { - "href": "#ma-4.3_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing nonlocal information system maintenance\n\nservice provider contracts and/or service-level agreements\n\nmaintenance records\n\ninspection records\n\naudit records\n\nequipment sanitization records\n\nmedia sanitization records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\ninformation system maintenance provider\n\norganizational personnel with information security responsibilities\n\norganizational personnel responsible for media sanitization\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for comparable security and sanitization for nonlocal maintenance\n\norganizational processes for removal, sanitization, and inspection of components serviced via nonlocal maintenance\n\nautomated mechanisms supporting and/or implementing component sanitization and inspection" - } - ] - } - ] - }, - { - "id": "ma-4.4", - "class": "SP800-53-enhancement", - "title": "Authentication / Separation of Maintenance Sessions", - "params": [ - { - "id": "ma-4.4_prm_1", - "label": "organization-defined authenticators that are replay resistant" - } - ], - "props": [ - { - "name": "label", - "value": "MA-4(4)" - }, - { - "name": "sort-id", - "value": "ma-04.04" - } - ], - "parts": [ - { - "id": "ma-4.4_smt", - "name": "statement", - "prose": "The organization protects nonlocal maintenance sessions by:", - "parts": [ - { - "id": "ma-4.4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Employing {{ insert: param, ma-4.4_prm_1 }}; and" - }, - { - "id": "ma-4.4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Separating the maintenance sessions from other network sessions with the information system by either:", - "parts": [ - { - "id": "ma-4.4_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "(1)" - } - ], - "prose": "Physically separated communications paths; or" - }, - { - "id": "ma-4.4_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "(2)" - } - ], - "prose": "Logically separated communications paths based upon encryption." - } - ] - } - ] - }, - { - "id": "ma-4.4_gdn", - "name": "guidance", - "links": [ - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "ma-4.4_obj", - "name": "objective", - "prose": "Determine if the organization protects nonlocal maintenance sessions by:", - "parts": [ - { - "id": "ma-4.4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(4)(a)" - } - ], - "parts": [ - { - "id": "ma-4.4.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(4)(a)[1]" - } - ], - "prose": "defining replay resistant authenticators to be employed to protect nonlocal maintenance sessions;" - }, - { - "id": "ma-4.4.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(4)(a)[2]" - } - ], - "prose": "employing organization-defined authenticators that are replay resistant;" - } - ], - "links": [ - { - "href": "#ma-4.4_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ma-4.4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(4)(b)" - } - ], - "prose": "separating the maintenance sessions from other network sessions with the information system by either:", - "parts": [ - { - "id": "ma-4.4.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(4)(b)(1)" - } - ], - "prose": "physically separated communications paths; or", - "links": [ - { - "href": "#ma-4.4_smt.b.1", - "rel": "corresp" - } - ] - }, - { - "id": "ma-4.4.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(4)(b)(2)" - } - ], - "prose": "logically separated communications paths based upon encryption.", - "links": [ - { - "href": "#ma-4.4_smt.b.2", - "rel": "corresp" - } - ] - } - ], - "links": [ - { - "href": "#ma-4.4_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing nonlocal information system maintenance\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nmaintenance records\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\nnetwork engineers\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for protecting nonlocal maintenance sessions\n\nautomated mechanisms implementing replay resistant authenticators\n\nautomated mechanisms implementing logically separated/encrypted communications paths" - } - ] - } - ] - }, - { - "id": "ma-4.5", - "class": "SP800-53-enhancement", - "title": "Approvals and Notifications", - "params": [ - { - "id": "ma-4.5_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "ma-4.5_prm_2", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "MA-4(5)" - }, - { - "name": "sort-id", - "value": "ma-04.05" - } - ], - "parts": [ - { - "id": "ma-4.5_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ma-4.5_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Requires the approval of each nonlocal maintenance session by {{ insert: param, ma-4.5_prm_1 }}; and" - }, - { - "id": "ma-4.5_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Notifies {{ insert: param, ma-4.5_prm_2 }} of the date and time of planned nonlocal maintenance." - } - ] - }, - { - "id": "ma-4.5_gdn", - "name": "guidance", - "prose": "Notification may be performed by maintenance personnel. Approval of nonlocal maintenance sessions is accomplished by organizational personnel with sufficient information security and information system knowledge to determine the appropriateness of the proposed maintenance." - }, - { - "id": "ma-4.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ma-4.5.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(5)(a)" - } - ], - "parts": [ - { - "id": "ma-4.5.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(5)(a)[1]" - } - ], - "prose": "defines personnel or roles required to approve each nonlocal maintenance session;" - }, - { - "id": "ma-4.5.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(5)(a)[2]" - } - ], - "prose": "requires the approval of each nonlocal maintenance session by organization-defined personnel or roles;" - } - ], - "links": [ - { - "href": "#ma-4.5_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ma-4.5.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(5)(b)" - } - ], - "parts": [ - { - "id": "ma-4.5.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(5)(b)[1]" - } - ], - "prose": "defines personnel or roles to be notified of the date and time of planned nonlocal maintenance; and" - }, - { - "id": "ma-4.5.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-4(5)(b)[2]" - } - ], - "prose": "notifies organization-defined personnel roles of the date and time of planned nonlocal maintenance." - } - ], - "links": [ - { - "href": "#ma-4.5_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing non-local information system maintenance\n\nsecurity plan\n\nnotifications supporting nonlocal maintenance sessions\n\nmaintenance records\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with notification responsibilities\n\norganizational personnel with approval responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for approving and notifying personnel regarding nonlocal maintenance\n\nautomated mechanisms supporting notification and approval of nonlocal maintenance" - } - ] - } - ] - }, - { - "id": "ma-4.6", - "class": "SP800-53-enhancement", - "title": "Cryptographic Protection", - "props": [ - { - "name": "label", - "value": "MA-4(6)" - }, - { - "name": "sort-id", - "value": "ma-04.06" - } - ], - "parts": [ - { - "id": "ma-4.6_smt", - "name": "statement", - "prose": "The information system implements cryptographic mechanisms to protect the integrity and confidentiality of nonlocal maintenance and diagnostic communications." - }, - { - "id": "ma-4.6_gdn", - "name": "guidance", - "links": [ - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "ma-4.6_obj", - "name": "objective", - "prose": "Determine if the information system implements cryptographic mechanisms to protect the integrity and confidentiality of nonlocal maintenance and diagnostic communications." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing non-local information system maintenance\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ncryptographic mechanisms protecting nonlocal maintenance activities\n\nmaintenance records\n\ndiagnostic records\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\nnetwork engineers\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Cryptographic mechanisms protecting nonlocal maintenance and diagnostic communications" - } - ] - } - ] - }, - { - "id": "ma-4.7", - "class": "SP800-53-enhancement", - "title": "Remote Disconnect Verification", - "props": [ - { - "name": "label", - "value": "MA-4(7)" - }, - { - "name": "sort-id", - "value": "ma-04.07" - } - ], - "parts": [ - { - "id": "ma-4.7_smt", - "name": "statement", - "prose": "The information system implements remote disconnect verification at the termination of nonlocal maintenance and diagnostic sessions." - }, - { - "id": "ma-4.7_gdn", - "name": "guidance", - "prose": "Remote disconnect verification ensures that remote connections from nonlocal maintenance sessions have been terminated and are no longer available for use.", - "links": [ - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "ma-4.7_obj", - "name": "objective", - "prose": "Determine if the information system implements remote disconnect verification at the termination of nonlocal maintenance and diagnostic sessions." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing non-local information system maintenance\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ncryptographic mechanisms protecting nonlocal maintenance activities\n\nmaintenance records\n\ndiagnostic records\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\nnetwork engineers\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing remote disconnect verifications of terminated nonlocal maintenance and diagnostic sessions" - } - ] - } - ] - } - ] - }, - { - "id": "ma-5", - "class": "SP800-53", - "title": "Maintenance Personnel", - "props": [ - { - "name": "label", - "value": "MA-5" - }, - { - "name": "sort-id", - "value": "ma-05" - } - ], - "parts": [ - { - "id": "ma-5_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ma-5_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Establishes a process for maintenance personnel authorization and maintains a list of authorized maintenance organizations or personnel;" - }, - { - "id": "ma-5_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Ensures that non-escorted personnel performing maintenance on the information system have required access authorizations; and" - }, - { - "id": "ma-5_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Designates organizational personnel with required access authorizations and technical competence to supervise the maintenance activities of personnel who do not possess the required access authorizations." - } - ] - }, - { - "id": "ma-5_gdn", - "name": "guidance", - "prose": "This control applies to individuals performing hardware or software maintenance on organizational information systems, while PE-2 addresses physical access for individuals whose maintenance duties place them within the physical protection perimeter of the systems (e.g., custodial staff, physical plant maintenance personnel). Technical competence of supervising individuals relates to the maintenance performed on the information systems while having required access authorizations refers to maintenance on and near the systems. Individuals not previously identified as authorized maintenance personnel, such as information technology manufacturers, vendors, systems integrators, and consultants, may require privileged access to organizational information systems, for example, when required to conduct maintenance activities with little or no notice. Based on organizational assessments of risk, organizations may issue temporary credentials to these individuals. Temporary credentials may be for one-time use or for very limited time periods.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pe-4", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - } - ] - }, - { - "id": "ma-5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ma-5.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(a)" - } - ], - "parts": [ - { - "id": "ma-5.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(a)[1]" - } - ], - "prose": "establishes a process for maintenance personnel authorization;" - }, - { - "id": "ma-5.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(a)[2]" - } - ], - "prose": "maintains a list of authorized maintenance organizations or personnel;" - } - ] - }, - { - "id": "ma-5.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(b)" - } - ], - "prose": "ensures that non-escorted personnel performing maintenance on the information system have required access authorizations; and" - }, - { - "id": "ma-5.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(c)" - } - ], - "prose": "designates organizational personnel with required access authorizations and technical competence to supervise the maintenance activities of personnel who do not possess the required access authorizations." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing maintenance personnel\n\nservice provider contracts\n\nservice-level agreements\n\nlist of authorized personnel\n\nmaintenance records\n\naccess control records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for authorizing and managing maintenance personnel\n\nautomated mechanisms supporting and/or implementing authorization of maintenance personnel" - } - ] - } - ], - "controls": [ - { - "id": "ma-5.1", - "class": "SP800-53-enhancement", - "title": "Individuals Without Appropriate Access", - "props": [ - { - "name": "label", - "value": "MA-5(1)" - }, - { - "name": "sort-id", - "value": "ma-05.01" - } - ], - "parts": [ - { - "id": "ma-5.1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ma-5.1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Implements procedures for the use of maintenance personnel that lack appropriate security clearances or are not U.S. citizens, that include the following requirements:", - "parts": [ - { - "id": "ma-5.1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "(1)" - } - ], - "prose": "Maintenance personnel who do not have needed access authorizations, clearances, or formal access approvals are escorted and supervised during the performance of maintenance and diagnostic activities on the information system by approved organizational personnel who are fully cleared, have appropriate access authorizations, and are technically qualified;" - }, - { - "id": "ma-5.1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "(2)" - } - ], - "prose": "Prior to initiating maintenance or diagnostic activities by personnel who do not have needed access authorizations, clearances or formal access approvals, all volatile information storage components within the information system are sanitized and all nonvolatile storage media are removed or physically disconnected from the system and secured; and" - } - ] - }, - { - "id": "ma-5.1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Develops and implements alternate security safeguards in the event an information system component cannot be sanitized, removed, or disconnected from the system." - } - ] - }, - { - "id": "ma-5.1_gdn", - "name": "guidance", - "prose": "This control enhancement denies individuals who lack appropriate security clearances (i.e., individuals who do not possess security clearances or possess security clearances at a lower level than required) or who are not U.S. citizens, visual and electronic access to any classified information, Controlled Unclassified Information (CUI), or any other sensitive information contained on organizational information systems. Procedures for the use of maintenance personnel can be documented in security plans for the information systems.", - "links": [ - { - "href": "#mp-6", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - } - ] - }, - { - "id": "ma-5.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ma-5.1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(1)(a)" - } - ], - "prose": "implements procedures for the use of maintenance personnel that lack appropriate security clearances or are not U.S. citizens, that include the following requirements:", - "parts": [ - { - "id": "ma-5.1.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(1)(a)(1)" - } - ], - "prose": "maintenance personnel who do not have needed access authorizations, clearances, or formal access approvals are escorted and supervised during the performance of maintenance and diagnostic activities on the information system by approved organizational personnel who:", - "parts": [ - { - "id": "ma-5.1.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(1)(a)(1)[1]" - } - ], - "prose": "are fully cleared;" - }, - { - "id": "ma-5.1.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(1)(a)(1)[2]" - } - ], - "prose": "have appropriate access authorizations;" - }, - { - "id": "ma-5.1.a.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(1)(a)(1)[3]" - } - ], - "prose": "are technically qualified;" - } - ], - "links": [ - { - "href": "#ma-5.1_smt.a.1", - "rel": "corresp" - } - ] - }, - { - "id": "ma-5.1.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(1)(a)(2)" - } - ], - "prose": "prior to initiating maintenance or diagnostic activities by personnel who do not have needed access authorizations, clearances, or formal access approvals:", - "parts": [ - { - "id": "ma-5.1.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(1)(a)(2)[1]" - } - ], - "prose": "all volatile information storage components within the information system are sanitized; and" - }, - { - "id": "ma-5.1.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(1)(a)(2)[2]" - } - ], - "prose": "all nonvolatile storage media are removed; or" - }, - { - "id": "ma-5.1.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(1)(a)(2)[3]" - } - ], - "prose": "all nonvolatile storage media are physically disconnected from the system and secured; and" - } - ], - "links": [ - { - "href": "#ma-5.1_smt.a.2", - "rel": "corresp" - } - ] - } - ], - "links": [ - { - "href": "#ma-5.1_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ma-5.1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(1)(b)" - } - ], - "prose": "develops and implements alternative security safeguards in the event an information system component cannot be sanitized, removed, or disconnected from the system.", - "links": [ - { - "href": "#ma-5.1_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing maintenance personnel\n\ninformation system media protection policy\n\nphysical and environmental protection policy\n\nsecurity plan\n\nlist of maintenance personnel requiring escort/supervision\n\nmaintenance records\n\naccess control records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with personnel security responsibilities\n\norganizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel responsible for media sanitization\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing maintenance personnel without appropriate access\n\nautomated mechanisms supporting and/or implementing alternative security safeguards\n\nautomated mechanisms supporting and/or implementing information storage component sanitization" - } - ] - } - ] - }, - { - "id": "ma-5.2", - "class": "SP800-53-enhancement", - "title": "Security Clearances for Classified Systems", - "props": [ - { - "name": "label", - "value": "MA-5(2)" - }, - { - "name": "sort-id", - "value": "ma-05.02" - } - ], - "parts": [ - { - "id": "ma-5.2_smt", - "name": "statement", - "prose": "The organization ensures that personnel performing maintenance and diagnostic activities on an information system processing, storing, or transmitting classified information possess security clearances and formal access approvals for at least the highest classification level and for all compartments of information on the system." - }, - { - "id": "ma-5.2_gdn", - "name": "guidance", - "links": [ - { - "href": "#ps-3", - "rel": "related" - } - ] - }, - { - "id": "ma-5.2_obj", - "name": "objective", - "prose": "Determine if the organization ensures that personnel performing maintenance and diagnostic activities on an information system processing, storing, or transmitting classified information possess:", - "parts": [ - { - "id": "ma-5.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(2)[1]" - } - ], - "prose": "security clearances for at least the highest classification level on the system;" - }, - { - "id": "ma-5.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(2)[2]" - } - ], - "prose": "security clearances for all compartments of information on the system;" - }, - { - "id": "ma-5.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(2)[3]" - } - ], - "prose": "formal access approvals for at least the highest classification level on the system; and" - }, - { - "id": "ma-5.2_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(2)[4]" - } - ], - "prose": "formal access approvals for all compartments of information on the system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing maintenance personnel\n\npersonnel records\n\nmaintenance records\n\naccess control records\n\naccess credentials\n\naccess authorizations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with personnel security responsibilities\n\norganizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing security clearances for maintenance personnel" - } - ] - } - ] - }, - { - "id": "ma-5.3", - "class": "SP800-53-enhancement", - "title": "Citizenship Requirements for Classified Systems", - "props": [ - { - "name": "label", - "value": "MA-5(3)" - }, - { - "name": "sort-id", - "value": "ma-05.03" - } - ], - "parts": [ - { - "id": "ma-5.3_smt", - "name": "statement", - "prose": "The organization ensures that personnel performing maintenance and diagnostic activities on an information system processing, storing, or transmitting classified information are U.S. citizens." - }, - { - "id": "ma-5.3_gdn", - "name": "guidance", - "links": [ - { - "href": "#ps-3", - "rel": "related" - } - ] - }, - { - "id": "ma-5.3_obj", - "name": "objective", - "prose": "Determine if the organization ensures that personnel performing maintenance and diagnostic activities on an information system processing, storing, or transmitting classified information are U.S. citizens." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing maintenance personnel\n\npersonnel records\n\nmaintenance records\n\naccess control records\n\naccess credentials\n\naccess authorizations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with personnel security responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "ma-5.4", - "class": "SP800-53-enhancement", - "title": "Foreign Nationals", - "props": [ - { - "name": "label", - "value": "MA-5(4)" - }, - { - "name": "sort-id", - "value": "ma-05.04" - } - ], - "parts": [ - { - "id": "ma-5.4_smt", - "name": "statement", - "prose": "The organization ensures that:", - "parts": [ - { - "id": "ma-5.4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Cleared foreign nationals (i.e., foreign nationals with appropriate security clearances), are used to conduct maintenance and diagnostic activities on classified information systems only when the systems are jointly owned and operated by the United States and foreign allied governments, or owned and operated solely by foreign allied governments; and" - }, - { - "id": "ma-5.4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Approvals, consents, and detailed operational conditions regarding the use of foreign nationals to conduct maintenance and diagnostic activities on classified information systems are fully documented within Memoranda of Agreements." - } - ] - }, - { - "id": "ma-5.4_gdn", - "name": "guidance", - "links": [ - { - "href": "#ps-3", - "rel": "related" - } - ] - }, - { - "id": "ma-5.4_obj", - "name": "objective", - "prose": "Determine if the organization ensures that:", - "parts": [ - { - "id": "ma-5.4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(4)(a)" - } - ], - "prose": "cleared foreign nationals (i.e., foreign nationals with appropriate security clearances) are used to conduct maintenance and diagnostic activities on classified information systems only when the systems are:", - "parts": [ - { - "id": "ma-5.4.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(4)(a)[1]" - } - ], - "prose": "jointly owned and operated by the United States and foreign allied governments; or" - }, - { - "id": "ma-5.4.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(4)(a)[2]" - } - ], - "prose": "owned and operated solely by foreign allied governments; and" - } - ], - "links": [ - { - "href": "#ma-5.4_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ma-5.4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-5(4)(b)" - } - ], - "prose": "approvals, consents, and detailed operational conditions regarding the use of foreign nationals to conduct maintenance and diagnostic activities on classified information systems are fully documented within Memoranda of Agreements.", - "links": [ - { - "href": "#ma-5.4_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing maintenance personnel\n\ninformation system media protection policy\n\naccess control policy and procedures\n\nphysical and environmental protection policy and procedures\n\nmemorandum of agreement\n\nmaintenance records\n\naccess control records\n\naccess credentials\n\naccess authorizations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities, organizational personnel with personnel security responsibilities\n\norganizational personnel managing memoranda of agreements\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing foreign national maintenance personnel" - } - ] - } - ] - }, - { - "id": "ma-5.5", - "class": "SP800-53-enhancement", - "title": "Nonsystem-related Maintenance", - "props": [ - { - "name": "label", - "value": "MA-5(5)" - }, - { - "name": "sort-id", - "value": "ma-05.05" - } - ], - "parts": [ - { - "id": "ma-5.5_smt", - "name": "statement", - "prose": "The organization ensures that non-escorted personnel performing maintenance activities not directly associated with the information system but in the physical proximity of the system, have required access authorizations." - }, - { - "id": "ma-5.5_gdn", - "name": "guidance", - "prose": "Personnel performing maintenance activities in other capacities not directly related to the information system include, for example, physical plant personnel and janitorial personnel." - }, - { - "id": "ma-5.5_obj", - "name": "objective", - "prose": "Determine if the organization ensures that non-escorted personnel performing maintenance activities not directly associated with the information system but in the physical proximity of the system, have required access authorizations." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing maintenance personnel\n\ninformation system media protection policy\n\naccess control policy and procedures\n\nphysical and environmental protection policy and procedures\n\nmaintenance records\n\naccess control records\n\naccess authorizations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with personnel security responsibilities\n\norganizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "ma-6", - "class": "SP800-53", - "title": "Timely Maintenance", - "params": [ - { - "id": "ma-6_prm_1", - "label": "organization-defined information system components" - }, - { - "id": "ma-6_prm_2", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "MA-6" - }, - { - "name": "sort-id", - "value": "ma-06" - } - ], - "parts": [ - { - "id": "ma-6_smt", - "name": "statement", - "prose": "The organization obtains maintenance support and/or spare parts for {{ insert: param, ma-6_prm_1 }} within {{ insert: param, ma-6_prm_2 }} of failure." - }, - { - "id": "ma-6_gdn", - "name": "guidance", - "prose": "Organizations specify the information system components that result in increased risk to organizational operations and assets, individuals, other organizations, or the Nation when the functionality provided by those components is not operational. Organizational actions to obtain maintenance support typically include having appropriate contracts in place.", - "links": [ - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - }, - { - "href": "#sa-14", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - } - ] - }, - { - "id": "ma-6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ma-6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-6[1]" - } - ], - "prose": "defines information system components for which maintenance support and/or spare parts are to be obtained;" - }, - { - "id": "ma-6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-6[2]" - } - ], - "prose": "defines the time period within which maintenance support and/or spare parts are to be obtained after a failure;" - }, - { - "id": "ma-6_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-6[3]" - } - ], - "parts": [ - { - "id": "ma-6_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-6[3][a]" - } - ], - "prose": "obtains maintenance support for organization-defined information system components within the organization-defined time period of failure; and/or" - }, - { - "id": "ma-6_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-6[3][b]" - } - ], - "prose": "obtains spare parts for organization-defined information system components within the organization-defined time period of failure." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing information system maintenance\n\nservice provider contracts\n\nservice-level agreements\n\ninventory and availability of spare parts\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for ensuring timely maintenance" - } - ] - } - ], - "controls": [ - { - "id": "ma-6.1", - "class": "SP800-53-enhancement", - "title": "Preventive Maintenance", - "params": [ - { - "id": "ma-6.1_prm_1", - "label": "organization-defined information system components" - }, - { - "id": "ma-6.1_prm_2", - "label": "organization-defined time intervals" - } - ], - "props": [ - { - "name": "label", - "value": "MA-6(1)" - }, - { - "name": "sort-id", - "value": "ma-06.01" - } - ], - "parts": [ - { - "id": "ma-6.1_smt", - "name": "statement", - "prose": "The organization performs preventive maintenance on {{ insert: param, ma-6.1_prm_1 }} at {{ insert: param, ma-6.1_prm_2 }}." - }, - { - "id": "ma-6.1_gdn", - "name": "guidance", - "prose": "Preventive maintenance includes proactive care and servicing of organizational information systems components for the purpose of maintaining equipment and facilities in satisfactory operating condition. Such maintenance provides for the systematic inspection, tests, measurements, adjustments, parts replacement, detection, and correction of incipient failures either before they occur or before they develop into major defects. The primary goal of preventive maintenance is to avoid/mitigate the consequences of equipment failures. Preventive maintenance is designed to preserve and restore equipment reliability by replacing worn components before they actually fail. Methods of determining what preventive (or other) failure management policies to apply include, for example, original equipment manufacturer (OEM) recommendations, statistical failure records, requirements of codes, legislation, or regulations within a jurisdiction, expert opinion, maintenance that has already been conducted on similar equipment, or measured values and performance indications." - }, - { - "id": "ma-6.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ma-6.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-6(1)[1]" - } - ], - "prose": "defines information system components on which preventive maintenance is to be performed;" - }, - { - "id": "ma-6.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-6(1)[2]" - } - ], - "prose": "defines time intervals within which preventive maintenance is to be performed on organization-defined information system components; and" - }, - { - "id": "ma-6.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-6(1)[3]" - } - ], - "prose": "performs preventive maintenance on organization-defined information system components at organization-defined time intervals." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing information system maintenance\n\nservice provider contracts\n\nservice-level agreements\n\nsecurity plan\n\nmaintenance records\n\nlist of system components requiring preventive maintenance\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for preventive maintenance\n\nautomated mechanisms supporting and/or implementing preventive maintenance" - } - ] - } - ] - }, - { - "id": "ma-6.2", - "class": "SP800-53-enhancement", - "title": "Predictive Maintenance", - "params": [ - { - "id": "ma-6.2_prm_1", - "label": "organization-defined information system components" - }, - { - "id": "ma-6.2_prm_2", - "label": "organization-defined time intervals" - } - ], - "props": [ - { - "name": "label", - "value": "MA-6(2)" - }, - { - "name": "sort-id", - "value": "ma-06.02" - } - ], - "parts": [ - { - "id": "ma-6.2_smt", - "name": "statement", - "prose": "The organization performs predictive maintenance on {{ insert: param, ma-6.2_prm_1 }} at {{ insert: param, ma-6.2_prm_2 }}." - }, - { - "id": "ma-6.2_gdn", - "name": "guidance", - "prose": "Predictive maintenance, or condition-based maintenance, attempts to evaluate the condition of equipment by performing periodic or continuous (online) equipment condition monitoring. The goal of predictive maintenance is to perform maintenance at a scheduled point in time when the maintenance activity is most cost-effective and before the equipment loses performance within a threshold. The predictive component of predictive maintenance stems from the goal of predicting the future trend of the equipment's condition. This approach uses principles of statistical process control to determine at what point in the future maintenance activities will be appropriate. Most predictive maintenance inspections are performed while equipment is in service, thereby minimizing disruption of normal system operations. Predictive maintenance can result in substantial cost savings and higher system reliability. Predictive maintenance tends to include measurement of the item. To evaluate equipment condition, predictive maintenance utilizes nondestructive testing technologies such as infrared, acoustic (partial discharge and airborne ultrasonic), corona detection, vibration analysis, sound level measurements, oil analysis, and other specific online tests." - }, - { - "id": "ma-6.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ma-6.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-6(2)[1]" - } - ], - "prose": "defines information system components on which predictive maintenance is to be performed;" - }, - { - "id": "ma-6.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-6(2)[2]" - } - ], - "prose": "defines time intervals within which predictive maintenance is to be performed on organization-defined information system components; and" - }, - { - "id": "ma-6.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MA-6(2)[3]" - } - ], - "prose": "performs predictive maintenance on organization-defined information system components at organization-defined time intervals." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing information system maintenance\n\nservice provider contracts\n\nservice-level agreements\n\nsecurity plan\n\nmaintenance records\n\nlist of system components requiring predictive maintenance\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for predictive maintenance\n\nautomated mechanisms supporting and/or implementing predictive maintenance" - } - ] - } - ] - }, - { - "id": "ma-6.3", - "class": "SP800-53-enhancement", - "title": "Automated Support for Predictive Maintenance", - "props": [ - { - "name": "label", - "value": "MA-6(3)" - }, - { - "name": "sort-id", - "value": "ma-06.03" - } - ], - "parts": [ - { - "id": "ma-6.3_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to transfer predictive maintenance data to a computerized maintenance management system." - }, - { - "id": "ma-6.3_gdn", - "name": "guidance", - "prose": "A computerized maintenance management system maintains a computer database of information about the maintenance operations of organizations and automates processing equipment condition data in order to trigger maintenance planning, execution, and reporting." - }, - { - "id": "ma-6.3_obj", - "name": "objective", - "prose": "Determine if the organization employs automated mechanisms to transfer predictive maintenance data to a computerized maintenance management system." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system maintenance policy\n\nprocedures addressing information system maintenance\n\nservice provider contracts\n\nservice-level agreements\n\nsecurity plan\n\nmaintenance records\n\nlist of system components requiring predictive maintenance\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system maintenance responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing the transfer of predictive maintenance data to a computerized maintenance management system\n\noperations of the computer maintenance management system" - } - ] - } - ] - } - ] - } - ] - }, - { - "id": "mp", - "class": "family", - "title": "Media Protection", - "controls": [ - { - "id": "mp-1", - "class": "SP800-53", - "title": "Media Protection Policy and Procedures", - "params": [ - { - "id": "mp-1_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "mp-1_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "mp-1_prm_3", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "MP-1" - }, - { - "name": "sort-id", - "value": "mp-01" - } - ], - "links": [ - { - "href": "#5c201b63-0768-417b-ac22-3f014e3941b2", - "rel": "reference" - }, - { - "href": "#9cb3d8fe-2127-48ba-821e-cdd2d7aee921", - "rel": "reference" - } - ], - "parts": [ - { - "id": "mp-1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "mp-1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops, documents, and disseminates to {{ insert: param, mp-1_prm_1 }}:", - "parts": [ - { - "id": "mp-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "A media protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "mp-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the media protection policy and associated media protection controls; and" - } - ] - }, - { - "id": "mp-1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the current:", - "parts": [ - { - "id": "mp-1_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Media protection policy {{ insert: param, mp-1_prm_2 }}; and" - }, - { - "id": "mp-1_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Media protection procedures {{ insert: param, mp-1_prm_3 }}." - } - ] - } - ] - }, - { - "id": "mp-1_gdn", - "name": "guidance", - "prose": "This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the MP family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures.", - "links": [ - { - "href": "#pm-9", - "rel": "related" - } - ] - }, - { - "id": "mp-1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "mp-1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(a)" - } - ], - "parts": [ - { - "id": "mp-1.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(a)(1)" - } - ], - "parts": [ - { - "id": "mp-1.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(a)(1)[1]" - } - ], - "prose": "develops and documents a media protection policy that addresses:", - "parts": [ - { - "id": "mp-1.a.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(a)(1)[1][a]" - } - ], - "prose": "purpose;" - }, - { - "id": "mp-1.a.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(a)(1)[1][b]" - } - ], - "prose": "scope;" - }, - { - "id": "mp-1.a.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(a)(1)[1][c]" - } - ], - "prose": "roles;" - }, - { - "id": "mp-1.a.1_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(a)(1)[1][d]" - } - ], - "prose": "responsibilities;" - }, - { - "id": "mp-1.a.1_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(a)(1)[1][e]" - } - ], - "prose": "management commitment;" - }, - { - "id": "mp-1.a.1_obj.1.f", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(a)(1)[1][f]" - } - ], - "prose": "coordination among organizational entities;" - }, - { - "id": "mp-1.a.1_obj.1.g", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(a)(1)[1][g]" - } - ], - "prose": "compliance;" - } - ] - }, - { - "id": "mp-1.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(a)(1)[2]" - } - ], - "prose": "defines personnel or roles to whom the media protection policy is to be disseminated;" - }, - { - "id": "mp-1.a.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(a)(1)[3]" - } - ], - "prose": "disseminates the media protection policy to organization-defined personnel or roles;" - } - ] - }, - { - "id": "mp-1.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(a)(2)" - } - ], - "parts": [ - { - "id": "mp-1.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(a)(2)[1]" - } - ], - "prose": "develops and documents procedures to facilitate the implementation of the media protection policy and associated media protection controls;" - }, - { - "id": "mp-1.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(a)(2)[2]" - } - ], - "prose": "defines personnel or roles to whom the procedures are to be disseminated;" - }, - { - "id": "mp-1.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(a)(2)[3]" - } - ], - "prose": "disseminates the procedures to organization-defined personnel or roles;" - } - ] - } - ] - }, - { - "id": "mp-1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(b)" - } - ], - "parts": [ - { - "id": "mp-1.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(b)(1)" - } - ], - "parts": [ - { - "id": "mp-1.b.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(b)(1)[1]" - } - ], - "prose": "defines the frequency to review and update the current media protection policy;" - }, - { - "id": "mp-1.b.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(b)(1)[2]" - } - ], - "prose": "reviews and updates the current media protection policy with the organization-defined frequency;" - } - ] - }, - { - "id": "mp-1.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(b)(2)" - } - ], - "parts": [ - { - "id": "mp-1.b.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(b)(2)[1]" - } - ], - "prose": "defines the frequency to review and update the current media protection procedures; and" - }, - { - "id": "mp-1.b.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-1(b)(2)[2]" - } - ], - "prose": "reviews and updates the current media protection procedures with the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Media protection policy and procedures\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with media protection responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "mp-2", - "class": "SP800-53", - "title": "Media Access", - "params": [ - { - "id": "mp-2_prm_1", - "label": "organization-defined types of digital and/or non-digital media" - }, - { - "id": "mp-2_prm_2", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "MP-2" - }, - { - "name": "sort-id", - "value": "mp-02" - } - ], - "links": [ - { - "href": "#e85cdb3f-7f0a-4083-8639-f13f70d3760b", - "rel": "reference" - }, - { - "href": "#3cac5e7b-9ebf-4bbb-9af5-ae032de78e8e", - "rel": "reference" - } - ], - "parts": [ - { - "id": "mp-2_smt", - "name": "statement", - "prose": "The organization restricts access to {{ insert: param, mp-2_prm_1 }} to {{ insert: param, mp-2_prm_2 }}." - }, - { - "id": "mp-2_gdn", - "name": "guidance", - "prose": "Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. Restricting non-digital media access includes, for example, denying access to patient medical records in a community hospital unless the individuals seeking access to such records are authorized healthcare providers. Restricting access to digital media includes, for example, limiting access to design specifications stored on compact disks in the media library to the project leader and the individuals on the development team.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - } - ] - }, - { - "id": "mp-2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "mp-2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-2[1]" - } - ], - "prose": "defines types of digital and/or non-digital media requiring restricted access;" - }, - { - "id": "mp-2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-2[2]" - } - ], - "prose": "defines personnel or roles authorized to access organization-defined types of digital and/or non-digital media; and" - }, - { - "id": "mp-2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-2[3]" - } - ], - "prose": "restricts access to organization-defined types of digital and/or non-digital media to organization-defined personnel or roles." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\nprocedures addressing media access restrictions\n\naccess control policy and procedures\n\nphysical and environmental protection policy and procedures\n\nmedia storage facilities\n\naccess control records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media protection responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for restricting information media\n\nautomated mechanisms supporting and/or implementing media access restrictions" - } - ] - } - ], - "controls": [ - { - "id": "mp-2.1", - "class": "SP800-53-enhancement", - "title": "Automated Restricted Access", - "props": [ - { - "name": "label", - "value": "MP-2(1)" - }, - { - "name": "sort-id", - "value": "mp-02.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#mp-4.2", - "rel": "incorporated-into" - } - ] - }, - { - "id": "mp-2.2", - "class": "SP800-53-enhancement", - "title": "Cryptographic Protection", - "props": [ - { - "name": "label", - "value": "MP-2(2)" - }, - { - "name": "sort-id", - "value": "mp-02.02" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-28.1", - "rel": "incorporated-into" - } - ] - } - ] - }, - { - "id": "mp-3", - "class": "SP800-53", - "title": "Media Marking", - "params": [ - { - "id": "mp-3_prm_1", - "label": "organization-defined types of information system media" - }, - { - "id": "mp-3_prm_2", - "label": "organization-defined controlled areas" - } - ], - "props": [ - { - "name": "label", - "value": "MP-3" - }, - { - "name": "sort-id", - "value": "mp-03" - } - ], - "links": [ - { - "href": "#e85cdb3f-7f0a-4083-8639-f13f70d3760b", - "rel": "reference" - } - ], - "parts": [ - { - "id": "mp-3_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "mp-3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Marks information system media indicating the distribution limitations, handling caveats, and applicable security markings (if any) of the information; and" - }, - { - "id": "mp-3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Exempts {{ insert: param, mp-3_prm_1 }} from marking as long as the media remain within {{ insert: param, mp-3_prm_2 }}." - } - ] - }, - { - "id": "mp-3_gdn", - "name": "guidance", - "prose": "The term security marking refers to the application/use of human-readable security attributes. The term security labeling refers to the application/use of security attributes with regard to internal data structures within information systems (see AC-16). Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. Security marking is generally not required for media containing information determined by organizations to be in the public domain or to be publicly releasable. However, some organizations may require markings for public information indicating that the information is publicly releasable. Marking of information system media reflects applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.", - "links": [ - { - "href": "#ac-16", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - } - ] - }, - { - "id": "mp-3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "mp-3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-3(a)" - } - ], - "prose": "marks information system media indicating the:", - "parts": [ - { - "id": "mp-3.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-3(a)[1]" - } - ], - "prose": "distribution limitations of the information;" - }, - { - "id": "mp-3.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-3(a)[2]" - } - ], - "prose": "handling caveats of the information;" - }, - { - "id": "mp-3.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-3(a)[3]" - } - ], - "prose": "applicable security markings (if any) of the information;" - } - ] - }, - { - "id": "mp-3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-3(b)" - } - ], - "parts": [ - { - "id": "mp-3.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-3(b)[1]" - } - ], - "prose": "defines types of information system media to be exempted from marking as long as the media remain in designated controlled areas;" - }, - { - "id": "mp-3.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-3(b)[2]" - } - ], - "prose": "defines controlled areas where organization-defined types of information system media exempt from marking are to be retained; and" - }, - { - "id": "mp-3.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-3(b)[3]" - } - ], - "prose": "exempts organization-defined types of information system media from marking as long as the media remain within organization-defined controlled areas." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\nprocedures addressing media marking\n\nphysical and environmental protection policy and procedures\n\nsecurity plan\n\nlist of information system media marking security attributes\n\ndesignated controlled areas\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media protection and marking responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for marking information media\n\nautomated mechanisms supporting and/or implementing media marking" - } - ] - } - ] - }, - { - "id": "mp-4", - "class": "SP800-53", - "title": "Media Storage", - "params": [ - { - "id": "mp-4_prm_1", - "label": "organization-defined types of digital and/or non-digital media" - }, - { - "id": "mp-4_prm_2", - "label": "organization-defined controlled areas" - } - ], - "props": [ - { - "name": "label", - "value": "MP-4" - }, - { - "name": "sort-id", - "value": "mp-04" - } - ], - "links": [ - { - "href": "#e85cdb3f-7f0a-4083-8639-f13f70d3760b", - "rel": "reference" - }, - { - "href": "#81f09e01-d0b0-4ae2-aa6a-064ed9950070", - "rel": "reference" - }, - { - "href": "#a6c774c0-bf50-4590-9841-2a5c1c91ac6f", - "rel": "reference" - }, - { - "href": "#3cac5e7b-9ebf-4bbb-9af5-ae032de78e8e", - "rel": "reference" - } - ], - "parts": [ - { - "id": "mp-4_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "mp-4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Physically controls and securely stores {{ insert: param, mp-4_prm_1 }} within {{ insert: param, mp-4_prm_2 }}; and" - }, - { - "id": "mp-4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Protects information system media until the media are destroyed or sanitized using approved equipment, techniques, and procedures." - } - ] - }, - { - "id": "mp-4_gdn", - "name": "guidance", - "prose": "Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. Physically controlling information system media includes, for example, conducting inventories, ensuring procedures are in place to allow individuals to check out and return media to the media library, and maintaining accountability for all stored media. Secure storage includes, for example, a locked drawer, desk, or cabinet, or a controlled media library. The type of media storage is commensurate with the security category and/or classification of the information residing on the media. Controlled areas are areas for which organizations provide sufficient physical and procedural safeguards to meet the requirements established for protecting information and/or information systems. For media containing information determined by organizations to be in the public domain, to be publicly releasable, or to have limited or no adverse impact on organizations or individuals if accessed by other than authorized personnel, fewer safeguards may be needed. In these situations, physical access controls provide adequate protection.", - "links": [ - { - "href": "#cp-6", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-7", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - } - ] - }, - { - "id": "mp-4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "mp-4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-4(a)" - } - ], - "parts": [ - { - "id": "mp-4.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-4(a)[1]" - } - ], - "prose": "defines types of digital and/or non-digital media to be physically controlled and securely stored within designated controlled areas;" - }, - { - "id": "mp-4.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-4(a)[2]" - } - ], - "prose": "defines controlled areas designated to physically control and securely store organization-defined types of digital and/or non-digital media;" - }, - { - "id": "mp-4.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-4(a)[3]" - } - ], - "prose": "physically controls organization-defined types of digital and/or non-digital media within organization-defined controlled areas;" - }, - { - "id": "mp-4.a_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-4(a)[4]" - } - ], - "prose": "securely stores organization-defined types of digital and/or non-digital media within organization-defined controlled areas; and" - } - ] - }, - { - "id": "mp-4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-4(b)" - } - ], - "prose": "protects information system media until the media are destroyed or sanitized using approved equipment, techniques, and procedures." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\nprocedures addressing media storage\n\nphysical and environmental protection policy and procedures\n\naccess control policy and procedures\n\nsecurity plan\n\ninformation system media\n\ndesignated controlled areas\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media protection and storage responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for storing information media\n\nautomated mechanisms supporting and/or implementing secure media storage/media protection" - } - ] - } - ], - "controls": [ - { - "id": "mp-4.1", - "class": "SP800-53-enhancement", - "title": "Cryptographic Protection", - "props": [ - { - "name": "label", - "value": "MP-4(1)" - }, - { - "name": "sort-id", - "value": "mp-04.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-28.1", - "rel": "incorporated-into" - } - ] - }, - { - "id": "mp-4.2", - "class": "SP800-53-enhancement", - "title": "Automated Restricted Access", - "props": [ - { - "name": "label", - "value": "MP-4(2)" - }, - { - "name": "sort-id", - "value": "mp-04.02" - } - ], - "parts": [ - { - "id": "mp-4.2_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to restrict access to media storage areas and to audit access attempts and access granted." - }, - { - "id": "mp-4.2_gdn", - "name": "guidance", - "prose": "Automated mechanisms can include, for example, keypads on the external entries to media storage areas.", - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - } - ] - }, - { - "id": "mp-4.2_obj", - "name": "objective", - "prose": "Determine if the organization employs automated mechanisms to:", - "parts": [ - { - "id": "mp-4.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-4(2)[1]" - } - ], - "prose": "restrict access to media storage areas;" - }, - { - "id": "mp-4.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-4(2)[2]" - } - ], - "prose": "audit access attempts; and" - }, - { - "id": "mp-4.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-4(2)[3]" - } - ], - "prose": "audit access granted." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\nprocedures addressing media storage\n\naccess control policy and procedures\n\nphysical and environmental protection policy and procedures\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nmedia storage facilities\n\naccess control devices\n\naccess control records\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media protection and storage responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms restricting access to media storage areas\n\nautomated mechanisms auditing access attempts and access granted to media storage areas" - } - ] - } - ] - } - ] - }, - { - "id": "mp-5", - "class": "SP800-53", - "title": "Media Transport", - "params": [ - { - "id": "mp-5_prm_1", - "label": "organization-defined types of information system media" - }, - { - "id": "mp-5_prm_2", - "label": "organization-defined security safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "MP-5" - }, - { - "name": "sort-id", - "value": "mp-05" - } - ], - "links": [ - { - "href": "#e85cdb3f-7f0a-4083-8639-f13f70d3760b", - "rel": "reference" - }, - { - "href": "#f152844f-b1ef-4836-8729-6277078ebee1", - "rel": "reference" - } - ], - "parts": [ - { - "id": "mp-5_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "mp-5_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Protects and controls {{ insert: param, mp-5_prm_1 }} during transport outside of controlled areas using {{ insert: param, mp-5_prm_2 }};" - }, - { - "id": "mp-5_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Maintains accountability for information system media during transport outside of controlled areas;" - }, - { - "id": "mp-5_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Documents activities associated with the transport of information system media; and" - }, - { - "id": "mp-5_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Restricts the activities associated with the transport of information system media to authorized personnel." - } - ] - }, - { - "id": "mp-5_gdn", - "name": "guidance", - "prose": "Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. This control also applies to mobile devices with information storage capability (e.g., smart phones, tablets, E-readers), that are transported outside of controlled areas. Controlled areas are areas or spaces for which organizations provide sufficient physical and/or procedural safeguards to meet the requirements established for protecting information and/or information systems. Physical and technical safeguards for media are commensurate with the security category or classification of the information residing on the media. Safeguards to protect media during transport include, for example, locked containers and cryptography. Cryptographic mechanisms can provide confidentiality and integrity protections depending upon the mechanisms used. Activities associated with transport include the actual transport as well as those activities such as releasing media for transport and ensuring that media enters the appropriate transport processes. For the actual transport, authorized transport and courier personnel may include individuals from outside the organization (e.g., U.S. Postal Service or a commercial transport or delivery service). Maintaining accountability of media during transport includes, for example, restricting transport activities to authorized personnel, and tracking and/or obtaining explicit records of transport activities as the media moves through the transportation system to prevent and detect loss, destruction, or tampering. Organizations establish documentation requirements for activities associated with the transport of information system media in accordance with organizational assessments of risk to include the flexibility to define different record-keeping methods for the different types of media transport as part of an overall system of transport-related records.", - "links": [ - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#mp-3", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#sc-28", - "rel": "related" - } - ] - }, - { - "id": "mp-5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "mp-5.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-5(a)" - } - ], - "parts": [ - { - "id": "mp-5.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-5(a)[1]" - } - ], - "prose": "defines types of information system media to be protected and controlled during transport outside of controlled areas;" - }, - { - "id": "mp-5.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-5(a)[2]" - } - ], - "prose": "defines security safeguards to protect and control organization-defined information system media during transport outside of controlled areas;" - }, - { - "id": "mp-5.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-5(a)[3]" - } - ], - "prose": "protects and controls organization-defined information system media during transport outside of controlled areas using organization-defined security safeguards;" - } - ] - }, - { - "id": "mp-5.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-5(b)" - } - ], - "prose": "maintains accountability for information system media during transport outside of controlled areas;" - }, - { - "id": "mp-5.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-5(c)" - } - ], - "prose": "documents activities associated with the transport of information system media; and" - }, - { - "id": "mp-5.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-5(d)" - } - ], - "prose": "restricts the activities associated with transport of information system media to authorized personnel." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\nprocedures addressing media storage\n\nphysical and environmental protection policy and procedures\n\naccess control policy and procedures\n\nsecurity plan\n\ninformation system media\n\ndesignated controlled areas\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media protection and storage responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for storing information media\n\nautomated mechanisms supporting and/or implementing media storage/media protection" - } - ] - } - ], - "controls": [ - { - "id": "mp-5.1", - "class": "SP800-53-enhancement", - "title": "Protection Outside of Controlled Areas", - "props": [ - { - "name": "label", - "value": "MP-5(1)" - }, - { - "name": "sort-id", - "value": "mp-05.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#mp-5", - "rel": "incorporated-into" - } - ] - }, - { - "id": "mp-5.2", - "class": "SP800-53-enhancement", - "title": "Documentation of Activities", - "props": [ - { - "name": "label", - "value": "MP-5(2)" - }, - { - "name": "sort-id", - "value": "mp-05.02" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#mp-5", - "rel": "incorporated-into" - } - ] - }, - { - "id": "mp-5.3", - "class": "SP800-53-enhancement", - "title": "Custodians", - "props": [ - { - "name": "label", - "value": "MP-5(3)" - }, - { - "name": "sort-id", - "value": "mp-05.03" - } - ], - "parts": [ - { - "id": "mp-5.3_smt", - "name": "statement", - "prose": "The organization employs an identified custodian during transport of information system media outside of controlled areas." - }, - { - "id": "mp-5.3_gdn", - "name": "guidance", - "prose": "Identified custodians provide organizations with specific points of contact during the media transport process and facilitate individual accountability. Custodial responsibilities can be transferred from one individual to another as long as an unambiguous custodian is identified at all times." - }, - { - "id": "mp-5.3_obj", - "name": "objective", - "prose": "Determine if the organization employs an identified custodian during transport of information system media outside of controlled areas." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\nprocedures addressing media transport\n\nphysical and environmental protection policy and procedures\n\ninformation system media transport records\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media transport responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "mp-5.4", - "class": "SP800-53-enhancement", - "title": "Cryptographic Protection", - "props": [ - { - "name": "label", - "value": "MP-5(4)" - }, - { - "name": "sort-id", - "value": "mp-05.04" - } - ], - "parts": [ - { - "id": "mp-5.4_smt", - "name": "statement", - "prose": "The information system implements cryptographic mechanisms to protect the confidentiality and integrity of information stored on digital media during transport outside of controlled areas." - }, - { - "id": "mp-5.4_gdn", - "name": "guidance", - "prose": "This control enhancement applies to both portable storage devices (e.g., USB memory sticks, compact disks, digital video disks, external/removable hard disk drives) and mobile devices with storage capability (e.g., smart phones, tablets, E-readers).", - "links": [ - { - "href": "#mp-2", - "rel": "related" - } - ] - }, - { - "id": "mp-5.4_obj", - "name": "objective", - "prose": "Determine if the organization employs cryptographic mechanisms to protect the confidentiality and integrity of information stored on digital media during transport outside of controlled areas." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\nprocedures addressing media transport\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system media transport records\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media transport responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Cryptographic mechanisms protecting information on digital media during transportation outside controlled areas" - } - ] - } - ] - } - ] - }, - { - "id": "mp-6", - "class": "SP800-53", - "title": "Media Sanitization", - "params": [ - { - "id": "mp-6_prm_1", - "label": "organization-defined information system media" - }, - { - "id": "mp-6_prm_2", - "label": "organization-defined sanitization techniques and procedures" - } - ], - "props": [ - { - "name": "label", - "value": "MP-6" - }, - { - "name": "sort-id", - "value": "mp-06" - } - ], - "links": [ - { - "href": "#e85cdb3f-7f0a-4083-8639-f13f70d3760b", - "rel": "reference" - }, - { - "href": "#f152844f-b1ef-4836-8729-6277078ebee1", - "rel": "reference" - }, - { - "href": "#263823e0-a971-4b00-959d-315b26278b22", - "rel": "reference" - }, - { - "href": "#a47466c4-c837-4f06-a39f-e68412a5f73d", - "rel": "reference" - } - ], - "parts": [ - { - "id": "mp-6_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "mp-6_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Sanitizes {{ insert: param, mp-6_prm_1 }} prior to disposal, release out of organizational control, or release for reuse using {{ insert: param, mp-6_prm_2 }} in accordance with applicable federal and organizational standards and policies; and" - }, - { - "id": "mp-6_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Employs sanitization mechanisms with the strength and integrity commensurate with the security category or classification of the information." - } - ] - }, - { - "id": "mp-6_gdn", - "name": "guidance", - "prose": "This control applies to all information system media, both digital and non-digital, subject to disposal or reuse, whether or not the media is considered removable. Examples include media found in scanners, copiers, printers, notebook computers, workstations, network components, and mobile devices. The sanitization process removes information from the media such that the information cannot be retrieved or reconstructed. Sanitization techniques, including clearing, purging, cryptographic erase, and destruction, prevent the disclosure of information to unauthorized individuals when such media is reused or released for disposal. Organizations determine the appropriate sanitization methods recognizing that destruction is sometimes necessary when other methods cannot be applied to media requiring sanitization. Organizations use discretion on the employment of approved sanitization techniques and procedures for media containing information deemed to be in the public domain or publicly releasable, or deemed to have no adverse impact on organizations or individuals if released for reuse or disposal. Sanitization of non-digital media includes, for example, removing a classified appendix from an otherwise unclassified document, or redacting selected sections or words from a document by obscuring the redacted sections/words in a manner equivalent in effectiveness to removing them from the document. NSA standards and policies control the sanitization process for media containing classified information.", - "links": [ - { - "href": "#ma-2", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#sc-4", - "rel": "related" - } - ] - }, - { - "id": "mp-6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "mp-6.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(a)" - } - ], - "parts": [ - { - "id": "mp-6.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(a)[1]" - } - ], - "prose": "defines information system media to be sanitized prior to:", - "parts": [ - { - "id": "mp-6.a_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(a)[1][a]" - } - ], - "prose": "disposal;" - }, - { - "id": "mp-6.a_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(a)[1][b]" - } - ], - "prose": "release out of organizational control; or" - }, - { - "id": "mp-6.a_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(a)[1][c]" - } - ], - "prose": "release for reuse;" - } - ] - }, - { - "id": "mp-6.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(a)[2]" - } - ], - "prose": "defines sanitization techniques or procedures to be used for sanitizing organization-defined information system media prior to:", - "parts": [ - { - "id": "mp-6.a_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(a)[2][a]" - } - ], - "prose": "disposal;" - }, - { - "id": "mp-6.a_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(a)[2][b]" - } - ], - "prose": "release out of organizational control; or" - }, - { - "id": "mp-6.a_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(a)[2][c]" - } - ], - "prose": "release for reuse;" - } - ] - }, - { - "id": "mp-6.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(a)[3]" - } - ], - "prose": "sanitizes organization-defined information system media prior to disposal, release out of organizational control, or release for reuse using organization-defined sanitization techniques or procedures in accordance with applicable federal and organizational standards and policies; and" - } - ] - }, - { - "id": "mp-6.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(b)" - } - ], - "prose": "employs sanitization mechanisms with strength and integrity commensurate with the security category or classification of the information." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\nprocedures addressing media sanitization and disposal\n\napplicable federal standards and policies addressing media sanitization\n\nmedia sanitization records\n\naudit records\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with media sanitization responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for media sanitization\n\nautomated mechanisms supporting and/or implementing media sanitization" - } - ] - } - ], - "controls": [ - { - "id": "mp-6.1", - "class": "SP800-53-enhancement", - "title": "Review / Approve / Track / Document / Verify", - "props": [ - { - "name": "label", - "value": "MP-6(1)" - }, - { - "name": "sort-id", - "value": "mp-06.01" - } - ], - "parts": [ - { - "id": "mp-6.1_smt", - "name": "statement", - "prose": "The organization reviews, approves, tracks, documents, and verifies media sanitization and disposal actions." - }, - { - "id": "mp-6.1_gdn", - "name": "guidance", - "prose": "Organizations review and approve media to be sanitized to ensure compliance with records-retention policies. Tracking/documenting actions include, for example, listing personnel who reviewed and approved sanitization and disposal actions, types of media sanitized, specific files stored on the media, sanitization methods used, date and time of the sanitization actions, personnel who performed the sanitization, verification actions taken, personnel who performed the verification, and disposal action taken. Organizations verify that the sanitization of the media was effective prior to disposal.", - "links": [ - { - "href": "#si-12", - "rel": "related" - } - ] - }, - { - "id": "mp-6.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "mp-6.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(1)[1]" - } - ], - "prose": "reviews media sanitization and disposal actions;" - }, - { - "id": "mp-6.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(1)[2]" - } - ], - "prose": "approves media sanitization and disposal actions;" - }, - { - "id": "mp-6.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(1)[3]" - } - ], - "prose": "tracks media sanitization and disposal actions;" - }, - { - "id": "mp-6.1_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(1)[4]" - } - ], - "prose": "documents media sanitization and disposal actions; and" - }, - { - "id": "mp-6.1_obj.5", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(1)[5]" - } - ], - "prose": "verifies media sanitization and disposal actions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\nprocedures addressing media sanitization and disposal\n\nmedia sanitization and disposal records\n\nreview records for media sanitization and disposal actions\n\napprovals for media sanitization and disposal actions\n\ntracking records\n\nverification records\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media sanitization and disposal responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for media sanitization\n\nautomated mechanisms supporting and/or implementing media sanitization" - } - ] - } - ] - }, - { - "id": "mp-6.2", - "class": "SP800-53-enhancement", - "title": "Equipment Testing", - "params": [ - { - "id": "mp-6.2_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "MP-6(2)" - }, - { - "name": "sort-id", - "value": "mp-06.02" - } - ], - "parts": [ - { - "id": "mp-6.2_smt", - "name": "statement", - "prose": "The organization tests sanitization equipment and procedures {{ insert: param, mp-6.2_prm_1 }} to verify that the intended sanitization is being achieved." - }, - { - "id": "mp-6.2_gdn", - "name": "guidance", - "prose": "Testing of sanitization equipment and procedures may be conducted by qualified and authorized external entities (e.g., other federal agencies or external service providers)." - }, - { - "id": "mp-6.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "mp-6.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(2)[1]" - } - ], - "prose": "defines the frequency for testing sanitization equipment and procedures to verify that the intended sanitization is being achieved; and" - }, - { - "id": "mp-6.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(2)[2]" - } - ], - "prose": "tests sanitization equipment and procedures with the organization-defined frequency to verify that the intended sanitization is being achieved." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\nprocedures addressing media sanitization and disposal\n\nprocedures addressing testing of media sanitization equipment\n\nresults of media sanitization equipment and procedures testing\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media sanitization responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for media sanitization\n\nautomated mechanisms supporting and/or implementing media sanitization" - } - ] - } - ] - }, - { - "id": "mp-6.3", - "class": "SP800-53-enhancement", - "title": "Nondestructive Techniques", - "params": [ - { - "id": "mp-6.3_prm_1", - "label": "organization-defined circumstances requiring sanitization of portable storage devices" - } - ], - "props": [ - { - "name": "label", - "value": "MP-6(3)" - }, - { - "name": "sort-id", - "value": "mp-06.03" - } - ], - "parts": [ - { - "id": "mp-6.3_smt", - "name": "statement", - "prose": "The organization applies nondestructive sanitization techniques to portable storage devices prior to connecting such devices to the information system under the following circumstances: {{ insert: param, mp-6.3_prm_1 }}." - }, - { - "id": "mp-6.3_gdn", - "name": "guidance", - "prose": "This control enhancement applies to digital media containing classified information and Controlled Unclassified Information (CUI). Portable storage devices can be the source of malicious code insertions into organizational information systems. Many of these devices are obtained from unknown and potentially untrustworthy sources and may contain malicious code that can be readily transferred to information systems through USB ports or other entry portals. While scanning such storage devices is always recommended, sanitization provides additional assurance that the devices are free of malicious code to include code capable of initiating zero-day attacks. Organizations consider nondestructive sanitization of portable storage devices when such devices are first purchased from the manufacturer or vendor prior to initial use or when organizations lose a positive chain of custody for the devices.", - "links": [ - { - "href": "#si-3", - "rel": "related" - } - ] - }, - { - "id": "mp-6.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "mp-6.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(3)[1]" - } - ], - "prose": "defines circumstances requiring sanitization of portable storage devices; and" - }, - { - "id": "mp-6.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(3)[2]" - } - ], - "prose": "applies nondestructive sanitization techniques to portable storage devices prior to connecting such devices to the information system under organization-defined circumstances requiring sanitization of portable storage devices." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\nprocedures addressing media sanitization and disposal\n\nlist of circumstances requiring sanitization of portable storage devices\n\nmedia sanitization records\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media sanitization responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for media sanitization of portable storage devices\n\nautomated mechanisms supporting and/or implementing media sanitization" - } - ] - } - ] - }, - { - "id": "mp-6.4", - "class": "SP800-53-enhancement", - "title": "Controlled Unclassified Information", - "props": [ - { - "name": "label", - "value": "MP-6(4)" - }, - { - "name": "sort-id", - "value": "mp-06.04" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#mp-6", - "rel": "incorporated-into" - } - ] - }, - { - "id": "mp-6.5", - "class": "SP800-53-enhancement", - "title": "Classified Information", - "props": [ - { - "name": "label", - "value": "MP-6(5)" - }, - { - "name": "sort-id", - "value": "mp-06.05" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#mp-6", - "rel": "incorporated-into" - } - ] - }, - { - "id": "mp-6.6", - "class": "SP800-53-enhancement", - "title": "Media Destruction", - "props": [ - { - "name": "label", - "value": "MP-6(6)" - }, - { - "name": "sort-id", - "value": "mp-06.06" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#mp-6", - "rel": "incorporated-into" - } - ] - }, - { - "id": "mp-6.7", - "class": "SP800-53-enhancement", - "title": "Dual Authorization", - "params": [ - { - "id": "mp-6.7_prm_1", - "label": "organization-defined information system media" - } - ], - "props": [ - { - "name": "label", - "value": "MP-6(7)" - }, - { - "name": "sort-id", - "value": "mp-06.07" - } - ], - "parts": [ - { - "id": "mp-6.7_smt", - "name": "statement", - "prose": "The organization enforces dual authorization for the sanitization of {{ insert: param, mp-6.7_prm_1 }}." - }, - { - "id": "mp-6.7_gdn", - "name": "guidance", - "prose": "Organizations employ dual authorization to ensure that information system media sanitization cannot occur unless two technically qualified individuals conduct the task. Individuals sanitizing information system media possess sufficient skills/expertise to determine if the proposed sanitization reflects applicable federal/organizational standards, policies, and procedures. Dual authorization also helps to ensure that sanitization occurs as intended, both protecting against errors and false claims of having performed the sanitization actions. Dual authorization may also be known as two-person control.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - } - ] - }, - { - "id": "mp-6.7_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "mp-6.7_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(7)[1]" - } - ], - "prose": "defines information system media requiring dual authorization to be enforced for sanitization of such media; and" - }, - { - "id": "mp-6.7_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(7)[2]" - } - ], - "prose": "enforces dual authorization for the sanitization of organization-defined information system media." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\nprocedures addressing media sanitization and disposal\n\nlist of information system media requiring dual authorization for sanitization\n\nauthorization records\n\nmedia sanitization records\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media sanitization responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes requiring dual authorization for media sanitization\n\nautomated mechanisms supporting and/or implementing media sanitization\n\nautomated mechanisms supporting and/or implementing dual authorization" - } - ] - } - ] - }, - { - "id": "mp-6.8", - "class": "SP800-53-enhancement", - "title": "Remote Purging / Wiping of Information", - "params": [ - { - "id": "mp-6.8_prm_1", - "label": "organization-defined information systems, system components, or devices" - }, - { - "id": "mp-6.8_prm_2", - "label": "organization-defined conditions" - } - ], - "props": [ - { - "name": "label", - "value": "MP-6(8)" - }, - { - "name": "sort-id", - "value": "mp-06.08" - } - ], - "parts": [ - { - "id": "mp-6.8_smt", - "name": "statement", - "prose": "The organization provides the capability to purge/wipe information from {{ insert: param, mp-6.8_prm_1 }} either remotely or under the following conditions: {{ insert: param, mp-6.8_prm_2 }}." - }, - { - "id": "mp-6.8_gdn", - "name": "guidance", - "prose": "This control enhancement protects data/information on organizational information systems, system components, or devices (e.g., mobile devices) if such systems, components, or devices are obtained by unauthorized individuals. Remote purge/wipe commands require strong authentication to mitigate the risk of unauthorized individuals purging/wiping the system/component/device. The purge/wipe function can be implemented in a variety of ways including, for example, by overwriting data/information multiple times or by destroying the key necessary to decrypt encrypted data." - }, - { - "id": "mp-6.8_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "mp-6.8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(8)[1]" - } - ], - "prose": "defines information systems, system components, or devices to purge/wipe either remotely or under specific organizational conditions;" - }, - { - "id": "mp-6.8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(8)[2]" - } - ], - "prose": "defines conditions under which information is to be purged/wiped from organization-defined information systems, system components, or devices; and" - }, - { - "id": "mp-6.8_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(8)[3]" - } - ], - "prose": "provides the capability to purge/wipe information from organization-defined information systems, system components, or devices either:", - "parts": [ - { - "id": "mp-6.8_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(8)[3][a]" - } - ], - "prose": "remotely; or" - }, - { - "id": "mp-6.8_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-6(8)[3][b]" - } - ], - "prose": "under organization-defined conditions." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\nprocedures addressing media sanitization and disposal\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nmedia sanitization records\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media sanitization responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for purging/wiping media\n\nautomated mechanisms supporting and/or implementing purge/wipe capabilities" - } - ] - } - ] - } - ] - }, - { - "id": "mp-7", - "class": "SP800-53", - "title": "Media Use", - "params": [ - { - "id": "mp-7_prm_1", - "select": { - "choice": [ - "restricts", - "prohibits" - ] - } - }, - { - "id": "mp-7_prm_2", - "label": "organization-defined types of information system media" - }, - { - "id": "mp-7_prm_3", - "label": "organization-defined information systems or system components" - }, - { - "id": "mp-7_prm_4", - "label": "organization-defined security safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "MP-7" - }, - { - "name": "sort-id", - "value": "mp-07" - } - ], - "links": [ - { - "href": "#e85cdb3f-7f0a-4083-8639-f13f70d3760b", - "rel": "reference" - }, - { - "href": "#3cac5e7b-9ebf-4bbb-9af5-ae032de78e8e", - "rel": "reference" - } - ], - "parts": [ - { - "id": "mp-7_smt", - "name": "statement", - "prose": "The organization {{ insert: param, mp-7_prm_1 }} the use of {{ insert: param, mp-7_prm_2 }} on {{ insert: param, mp-7_prm_3 }} using {{ insert: param, mp-7_prm_4 }}." - }, - { - "id": "mp-7_gdn", - "name": "guidance", - "prose": "Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. This control also applies to mobile devices with information storage capability (e.g., smart phones, tablets, E-readers). In contrast to MP-2, which restricts user access to media, this control restricts the use of certain types of media on information systems, for example, restricting/prohibiting the use of flash drives or external hard disk drives. Organizations can employ technical and nontechnical safeguards (e.g., policies, procedures, rules of behavior) to restrict the use of information system media. Organizations may restrict the use of portable storage devices, for example, by using physical cages on workstations to prohibit access to certain external ports, or disabling/removing the ability to insert, read or write to such devices. Organizations may also limit the use of portable storage devices to only approved devices including, for example, devices provided by the organization, devices provided by other approved organizations, and devices that are not personally owned. Finally, organizations may restrict the use of portable storage devices based on the type of device, for example, prohibiting the use of writeable, portable storage devices, and implementing this restriction by disabling or removing the capability to write to such devices.", - "links": [ - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - } - ] - }, - { - "id": "mp-7_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "mp-7_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-7[1]" - } - ], - "prose": "defines types of information system media to be:", - "parts": [ - { - "id": "mp-7_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-7[1][a]" - } - ], - "prose": "restricted on information systems or system components; or" - }, - { - "id": "mp-7_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-7[1][b]" - } - ], - "prose": "prohibited from use on information systems or system components;" - } - ] - }, - { - "id": "mp-7_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-7[2]" - } - ], - "prose": "defines information systems or system components on which the use of organization-defined types of information system media is to be one of the following:", - "parts": [ - { - "id": "mp-7_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-7[2][a]" - } - ], - "prose": "restricted; or" - }, - { - "id": "mp-7_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-7[2][b]" - } - ], - "prose": "prohibited;" - } - ] - }, - { - "id": "mp-7_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-7[3]" - } - ], - "prose": "defines security safeguards to be employed to restrict or prohibit the use of organization-defined types of information system media on organization-defined information systems or system components; and" - }, - { - "id": "mp-7_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-7[4]" - } - ], - "prose": "restricts or prohibits the use of organization-defined information system media on organization-defined information systems or system components using organization-defined security safeguards." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\nsystem use policy\n\nprocedures addressing media usage restrictions\n\nsecurity plan\n\nrules of behavior\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media use responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for media use\n\nautomated mechanisms restricting or prohibiting use of information system media on information systems or system components" - } - ] - } - ], - "controls": [ - { - "id": "mp-7.1", - "class": "SP800-53-enhancement", - "title": "Prohibit Use Without Owner", - "props": [ - { - "name": "label", - "value": "MP-7(1)" - }, - { - "name": "sort-id", - "value": "mp-07.01" - } - ], - "parts": [ - { - "id": "mp-7.1_smt", - "name": "statement", - "prose": "The organization prohibits the use of portable storage devices in organizational information systems when such devices have no identifiable owner." - }, - { - "id": "mp-7.1_gdn", - "name": "guidance", - "prose": "Requiring identifiable owners (e.g., individuals, organizations, or projects) for portable storage devices reduces the risk of using such technologies by allowing organizations to assign responsibility and accountability for addressing known vulnerabilities in the devices (e.g., malicious code insertion).", - "links": [ - { - "href": "#pl-4", - "rel": "related" - } - ] - }, - { - "id": "mp-7.1_obj", - "name": "objective", - "prose": "Determine if the organization prohibits the use of portable storage devices in organizational information systems when such devices have no identifiable owner." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\nsystem use policy\n\nprocedures addressing media usage restrictions\n\nsecurity plan\n\nrules of behavior\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media use responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for media use\n\nautomated mechanisms prohibiting use of media on information systems or system components" - } - ] - } - ] - }, - { - "id": "mp-7.2", - "class": "SP800-53-enhancement", - "title": "Prohibit Use of Sanitization-resistant Media", - "props": [ - { - "name": "label", - "value": "MP-7(2)" - }, - { - "name": "sort-id", - "value": "mp-07.02" - } - ], - "parts": [ - { - "id": "mp-7.2_smt", - "name": "statement", - "prose": "The organization prohibits the use of sanitization-resistant media in organizational information systems." - }, - { - "id": "mp-7.2_gdn", - "name": "guidance", - "prose": "Sanitization-resistance applies to the capability to purge information from media. Certain types of media do not support sanitize commands, or if supported, the interfaces are not supported in a standardized way across these devices. Sanitization-resistant media include, for example, compact flash, embedded flash on boards and devices, solid state drives, and USB removable media.", - "links": [ - { - "href": "#mp-6", - "rel": "related" - } - ] - }, - { - "id": "mp-7.2_obj", - "name": "objective", - "prose": "Determine if the organization prohibits the use of sanitization-resistant media in organizational information systems." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy, system use policy\n\nprocedures addressing media usage restrictions\n\nrules of behavior\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media use responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for media use\n\nautomated mechanisms prohibiting use of media on information systems or system components" - } - ] - } - ] - } - ] - }, - { - "id": "mp-8", - "class": "SP800-53", - "title": "Media Downgrading", - "params": [ - { - "id": "mp-8_prm_1", - "label": "organization-defined information system media downgrading process" - }, - { - "id": "mp-8_prm_2", - "label": "organization-defined strength and integrity" - }, - { - "id": "mp-8_prm_3", - "label": "organization-defined information system media requiring downgrading" - } - ], - "props": [ - { - "name": "label", - "value": "MP-8" - }, - { - "name": "sort-id", - "value": "mp-08" - } - ], - "parts": [ - { - "id": "mp-8_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "mp-8_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Establishes {{ insert: param, mp-8_prm_1 }} that includes employing downgrading mechanisms with {{ insert: param, mp-8_prm_2 }};" - }, - { - "id": "mp-8_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Ensures that the information system media downgrading process is commensurate with the security category and/or classification level of the information to be removed and the access authorizations of the potential recipients of the downgraded information;" - }, - { - "id": "mp-8_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Identifies {{ insert: param, mp-8_prm_3 }}; and" - }, - { - "id": "mp-8_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Downgrades the identified information system media using the established process." - } - ] - }, - { - "id": "mp-8_gdn", - "name": "guidance", - "prose": "This control applies to all information system media, digital and non-digital, subject to release outside of the organization, whether or not the media is considered removable. The downgrading process, when applied to system media, removes information from the media, typically by security category or classification level, such that the information cannot be retrieved or reconstructed. Downgrading of media includes redacting information to enable wider release and distribution. Downgrading of media also ensures that empty space on the media (e.g., slack space within files) is devoid of information." - }, - { - "id": "mp-8_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "mp-8.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-8(a)" - } - ], - "parts": [ - { - "id": "mp-8.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-8(a)[1]" - } - ], - "prose": "defines the information system media downgrading process;" - }, - { - "id": "mp-8.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-8(a)[2]" - } - ], - "prose": "defines the strength and integrity with which media downgrading mechanisms are to be employed;" - }, - { - "id": "mp-8.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-8(a)[3]" - } - ], - "prose": "establishes an organization-defined information system media downgrading process that includes employing downgrading mechanisms with organization-defined strength and integrity;" - } - ] - }, - { - "id": "mp-8.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-8(b)" - } - ], - "prose": "ensures that the information system media downgrading process is commensurate with the:", - "parts": [ - { - "id": "mp-8.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-8(b)[1]" - } - ], - "prose": "security category and/or classification level of the information to be removed;" - }, - { - "id": "mp-8.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-8(b)[2]" - } - ], - "prose": "access authorizations of the potential recipients of the downgraded information;" - } - ] - }, - { - "id": "mp-8.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-8(c)" - } - ], - "prose": "identifies/defines information system media requiring downgrading; and" - }, - { - "id": "mp-8.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-8(d)" - } - ], - "prose": "downgrades the identified information system media using the established process." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\nprocedures addressing media downgrading\n\nsystem categorization documentation\n\nlist of media requiring downgrading\n\nrecords of media downgrading\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media downgrading responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for media downgrading\n\nautomated mechanisms supporting and/or implementing media downgrading" - } - ] - } - ], - "controls": [ - { - "id": "mp-8.1", - "class": "SP800-53-enhancement", - "title": "Documentation of Process", - "props": [ - { - "name": "label", - "value": "MP-8(1)" - }, - { - "name": "sort-id", - "value": "mp-08.01" - } - ], - "parts": [ - { - "id": "mp-8.1_smt", - "name": "statement", - "prose": "The organization documents information system media downgrading actions." - }, - { - "id": "mp-8.1_gdn", - "name": "guidance", - "prose": "Organizations can document the media downgrading process by providing information such as the downgrading technique employed, the identification number of the downgraded media, and the identity of the individual that authorized and/or performed the downgrading action." - }, - { - "id": "mp-8.1_obj", - "name": "objective", - "prose": "Determine if the organization documents information system media downgrading actions." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\nprocedures addressing media downgrading\n\nlist of media requiring downgrading\n\nrecords of media downgrading\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media downgrading responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for media downgrading\n\nautomated mechanisms supporting and/or implementing media downgrading" - } - ] - } - ] - }, - { - "id": "mp-8.2", - "class": "SP800-53-enhancement", - "title": "Equipment Testing", - "params": [ - { - "id": "mp-8.2_prm_1", - "label": "organization-defined tests" - }, - { - "id": "mp-8.2_prm_2", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "MP-8(2)" - }, - { - "name": "sort-id", - "value": "mp-08.02" - } - ], - "parts": [ - { - "id": "mp-8.2_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, mp-8.2_prm_1 }} of downgrading equipment and procedures to verify correct performance {{ insert: param, mp-8.2_prm_2 }}." - }, - { - "id": "mp-8.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "mp-8.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-8(2)[1]" - } - ], - "parts": [ - { - "id": "mp-8.2_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-8(2)[1][a]" - } - ], - "prose": "defines tests to be employed for downgrading equipment;" - }, - { - "id": "mp-8.2_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-8(2)[1][b]" - } - ], - "prose": "defines procedures to verify correct performance;" - } - ] - }, - { - "id": "mp-8.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-8(2)[2]" - } - ], - "prose": "defines the frequency for employing tests of downgrading equipment and procedures to verify correct performance; and" - }, - { - "id": "mp-8.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-8(2)[3]" - } - ], - "prose": "employs organization-defined tests of downgrading equipment and procedures to verify correct performance with the organization-defined frequency." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\nprocedures addressing media downgrading\n\nprocedures addressing testing of media downgrading equipment\n\nresults of downgrading equipment and procedures testing\n\naudit records: other relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media downgrading responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for media downgrading\n\nautomated mechanisms supporting and/or implementing media downgrading\n\nautomated mechanisms supporting and/or implementing tests for downgrading equipment" - } - ] - } - ] - }, - { - "id": "mp-8.3", - "class": "SP800-53-enhancement", - "title": "Controlled Unclassified Information", - "params": [ - { - "id": "mp-8.3_prm_1", - "label": "organization-defined Controlled Unclassified Information (CUI)" - } - ], - "props": [ - { - "name": "label", - "value": "MP-8(3)" - }, - { - "name": "sort-id", - "value": "mp-08.03" - } - ], - "parts": [ - { - "id": "mp-8.3_smt", - "name": "statement", - "prose": "The organization downgrades information system media containing {{ insert: param, mp-8.3_prm_1 }} prior to public release in accordance with applicable federal and organizational standards and policies." - }, - { - "id": "mp-8.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "mp-8.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-8(3)[1]" - } - ], - "prose": "defines Controlled Unclassified Information (CUI) contained on information system media that requires downgrading prior to public release; and" - }, - { - "id": "mp-8.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "MP-8(3)[2]" - } - ], - "prose": "downgrades information system media containing organization-defined CUI prior to public release in accordance with applicable federal and organizational standards and policies." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\naccess authorization policy\n\nprocedures addressing downgrading of media containing CUI\n\napplicable federal and organizational standards and policies regarding protection of CUI\n\nmedia downgrading records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media downgrading responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for media downgrading\n\nautomated mechanisms supporting and/or implementing media downgrading" - } - ] - } - ] - }, - { - "id": "mp-8.4", - "class": "SP800-53-enhancement", - "title": "Classified Information", - "props": [ - { - "name": "label", - "value": "MP-8(4)" - }, - { - "name": "sort-id", - "value": "mp-08.04" - } - ], - "parts": [ - { - "id": "mp-8.4_smt", - "name": "statement", - "prose": "The organization downgrades information system media containing classified information prior to release to individuals without required access authorizations in accordance with NSA standards and policies." - }, - { - "id": "mp-8.4_gdn", - "name": "guidance", - "prose": "Downgrading of classified information uses approved sanitization tools, techniques, and procedures to transfer information confirmed to be unclassified from classified information systems to unclassified media." - }, - { - "id": "mp-8.4_obj", - "name": "objective", - "prose": "Determine if the organization downgrades information system media containing classified information prior to release to individuals without required access authorizations in accordance with NSA standards and policies." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system media protection policy\n\naccess authorization policy\n\nprocedures addressing downgrading of media containing classified information\n\nprocedures addressing handling of classified information\n\nNSA standards and policies regarding protection of classified information\n\nmedia downgrading records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information system media downgrading responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for media downgrading\n\nautomated mechanisms supporting and/or implementing media downgrading" - } - ] - } - ] - } - ] - } - ] - }, - { - "id": "pe", - "class": "family", - "title": "Physical and Environmental Protection", - "controls": [ - { - "id": "pe-1", - "class": "SP800-53", - "title": "Physical and Environmental Protection Policy and Procedures", - "params": [ - { - "id": "pe-1_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "pe-1_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "pe-1_prm_3", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "PE-1" - }, - { - "name": "sort-id", - "value": "pe-01" - } - ], - "links": [ - { - "href": "#5c201b63-0768-417b-ac22-3f014e3941b2", - "rel": "reference" - }, - { - "href": "#9cb3d8fe-2127-48ba-821e-cdd2d7aee921", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pe-1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pe-1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops, documents, and disseminates to {{ insert: param, pe-1_prm_1 }}:", - "parts": [ - { - "id": "pe-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "A physical and environmental protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "pe-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the physical and environmental protection policy and associated physical and environmental protection controls; and" - } - ] - }, - { - "id": "pe-1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the current:", - "parts": [ - { - "id": "pe-1_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Physical and environmental protection policy {{ insert: param, pe-1_prm_2 }}; and" - }, - { - "id": "pe-1_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Physical and environmental protection procedures {{ insert: param, pe-1_prm_3 }}." - } - ] - } - ] - }, - { - "id": "pe-1_gdn", - "name": "guidance", - "prose": "This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the PE family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures.", - "links": [ - { - "href": "#pm-9", - "rel": "related" - } - ] - }, - { - "id": "pe-1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(a)" - } - ], - "parts": [ - { - "id": "pe-1.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(a)(1)" - } - ], - "parts": [ - { - "id": "pe-1.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(a)(1)[1]" - } - ], - "prose": "develops and documents a physical and environmental protection policy that addresses:", - "parts": [ - { - "id": "pe-1.a.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(a)(1)[1][a]" - } - ], - "prose": "purpose;" - }, - { - "id": "pe-1.a.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(a)(1)[1][b]" - } - ], - "prose": "scope;" - }, - { - "id": "pe-1.a.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(a)(1)[1][c]" - } - ], - "prose": "roles;" - }, - { - "id": "pe-1.a.1_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(a)(1)[1][d]" - } - ], - "prose": "responsibilities;" - }, - { - "id": "pe-1.a.1_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(a)(1)[1][e]" - } - ], - "prose": "management commitment;" - }, - { - "id": "pe-1.a.1_obj.1.f", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(a)(1)[1][f]" - } - ], - "prose": "coordination among organizational entities;" - }, - { - "id": "pe-1.a.1_obj.1.g", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(a)(1)[1][g]" - } - ], - "prose": "compliance;" - } - ] - }, - { - "id": "pe-1.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(a)(1)[2]" - } - ], - "prose": "defines personnel or roles to whom the physical and environmental protection policy is to be disseminated;" - }, - { - "id": "pe-1.a.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(a)(1)[3]" - } - ], - "prose": "disseminates the physical and environmental protection policy to organization-defined personnel or roles;" - } - ] - }, - { - "id": "pe-1.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(a)(2)" - } - ], - "parts": [ - { - "id": "pe-1.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(a)(2)[1]" - } - ], - "prose": "develops and documents procedures to facilitate the implementation of the physical and environmental protection policy and associated physical and environmental protection controls;" - }, - { - "id": "pe-1.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(a)(2)[2]" - } - ], - "prose": "defines personnel or roles to whom the procedures are to be disseminated;" - }, - { - "id": "pe-1.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(a)(2)[3]" - } - ], - "prose": "disseminates the procedures to organization-defined personnel or roles;" - } - ] - } - ] - }, - { - "id": "pe-1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(b)" - } - ], - "parts": [ - { - "id": "pe-1.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(b)(1)" - } - ], - "parts": [ - { - "id": "pe-1.b.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(b)(1)[1]" - } - ], - "prose": "defines the frequency to review and update the current physical and environmental protection policy;" - }, - { - "id": "pe-1.b.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(b)(1)[2]" - } - ], - "prose": "reviews and updates the current physical and environmental protection policy with the organization-defined frequency;" - } - ] - }, - { - "id": "pe-1.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(b)(2)" - } - ], - "parts": [ - { - "id": "pe-1.b.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(b)(2)[1]" - } - ], - "prose": "defines the frequency to review and update the current physical and environmental protection procedures; and" - }, - { - "id": "pe-1.b.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-1(b)(2)[2]" - } - ], - "prose": "reviews and updates the current physical and environmental protection procedures with the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy and procedures\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical and environmental protection responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "pe-2", - "class": "SP800-53", - "title": "Physical Access Authorizations", - "params": [ - { - "id": "pe-2_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "PE-2" - }, - { - "name": "sort-id", - "value": "pe-02" - } - ], - "parts": [ - { - "id": "pe-2_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pe-2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops, approves, and maintains a list of individuals with authorized access to the facility where the information system resides;" - }, - { - "id": "pe-2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Issues authorization credentials for facility access;" - }, - { - "id": "pe-2_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Reviews the access list detailing authorized facility access by individuals {{ insert: param, pe-2_prm_1 }}; and" - }, - { - "id": "pe-2_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Removes individuals from the facility access list when access is no longer required." - } - ] - }, - { - "id": "pe-2_gdn", - "name": "guidance", - "prose": "This control applies to organizational employees and visitors. Individuals (e.g., employees, contractors, and others) with permanent physical access authorization credentials are not considered visitors. Authorization credentials include, for example, badges, identification cards, and smart cards. Organizations determine the strength of authorization credentials needed (including level of forge-proof badges, smart cards, or identification cards) consistent with federal standards, policies, and procedures. This control only applies to areas within facilities that have not been designated as publicly accessible.", - "links": [ - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pe-4", - "rel": "related" - }, - { - "href": "#ps-3", - "rel": "related" - } - ] - }, - { - "id": "pe-2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-2(a)" - } - ], - "parts": [ - { - "id": "pe-2.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-2(a)[1]" - } - ], - "prose": "develops a list of individuals with authorized access to the facility where the information system resides;" - }, - { - "id": "pe-2.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-2(a)[2]" - } - ], - "prose": "approves a list of individuals with authorized access to the facility where the information system resides;" - }, - { - "id": "pe-2.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-2(a)[3]" - } - ], - "prose": "maintains a list of individuals with authorized access to the facility where the information system resides;" - } - ] - }, - { - "id": "pe-2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-2(b)" - } - ], - "prose": "issues authorization credentials for facility access;" - }, - { - "id": "pe-2.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-2(c)" - } - ], - "parts": [ - { - "id": "pe-2.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-2(c)[1]" - } - ], - "prose": "defines the frequency to review the access list detailing authorized facility access by individuals;" - }, - { - "id": "pe-2.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-2(c)[2]" - } - ], - "prose": "reviews the access list detailing authorized facility access by individuals with the organization-defined frequency; and" - } - ] - }, - { - "id": "pe-2.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-2(d)" - } - ], - "prose": "removes individuals from the facility access list when access is no longer required." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access authorizations\n\nsecurity plan\n\nauthorized personnel access list\n\nauthorization credentials\n\nphysical access list reviews\n\nphysical access termination records and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access authorization responsibilities\n\norganizational personnel with physical access to information system facility\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for physical access authorizations\n\nautomated mechanisms supporting and/or implementing physical access authorizations" - } - ] - } - ], - "controls": [ - { - "id": "pe-2.1", - "class": "SP800-53-enhancement", - "title": "Access by Position / Role", - "props": [ - { - "name": "label", - "value": "PE-2(1)" - }, - { - "name": "sort-id", - "value": "pe-02.01" - } - ], - "parts": [ - { - "id": "pe-2.1_smt", - "name": "statement", - "prose": "The organization authorizes physical access to the facility where the information system resides based on position or role." - }, - { - "id": "pe-2.1_gdn", - "name": "guidance", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - } - ] - }, - { - "id": "pe-2.1_obj", - "name": "objective", - "prose": "Determine if the organization authorizes physical access to the facility where the information system resides based on position or role." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access authorizations\n\nphysical access control logs or records\n\nlist of positions/roles and corresponding physical access authorizations\n\ninformation system entry and exit points\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access authorization responsibilities\n\norganizational personnel with physical access to information system facility\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for physical access authorizations\n\nautomated mechanisms supporting and/or implementing physical access authorizations" - } - ] - } - ] - }, - { - "id": "pe-2.2", - "class": "SP800-53-enhancement", - "title": "Two Forms of Identification", - "params": [ - { - "id": "pe-2.2_prm_1", - "label": "organization-defined list of acceptable forms of identification" - } - ], - "props": [ - { - "name": "label", - "value": "PE-2(2)" - }, - { - "name": "sort-id", - "value": "pe-02.02" - } - ], - "parts": [ - { - "id": "pe-2.2_smt", - "name": "statement", - "prose": "The organization requires two forms of identification from {{ insert: param, pe-2.2_prm_1 }} for visitor access to the facility where the information system resides." - }, - { - "id": "pe-2.2_gdn", - "name": "guidance", - "prose": "Acceptable forms of government photo identification include, for example, passports, Personal Identity Verification (PIV) cards, and drivers’ licenses. In the case of gaining access to facilities using automated mechanisms, organizations may use PIV cards, key cards, PINs, and biometrics.", - "links": [ - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - } - ] - }, - { - "id": "pe-2.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-2.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-2(2)[1]" - } - ], - "prose": "defines a list of acceptable forms of identification for visitor access to the facility where the information system resides; and" - }, - { - "id": "pe-2.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-2(2)[2]" - } - ], - "prose": "requires two forms of identification from the organization-defined list of acceptable forms of identification for visitor access to the facility where the information system resides." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access authorizations\n\nlist of acceptable forms of identification for visitor access to the facility where information system resides\n\naccess authorization forms\n\naccess credentials\n\nphysical access control logs or records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access authorization responsibilities\n\norganizational personnel with physical access to information system facility\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for physical access authorizations\n\nautomated mechanisms supporting and/or implementing physical access authorizations" - } - ] - } - ] - }, - { - "id": "pe-2.3", - "class": "SP800-53-enhancement", - "title": "Restrict Unescorted Access", - "params": [ - { - "id": "pe-2.3_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "security clearances for all information contained within the system", - "formal access authorizations for all information contained within the system", - "need for access to all information contained within the system", - " {{ insert: param, pe-2.3_prm_2 }} " - ] - } - }, - { - "id": "pe-2.3_prm_2", - "depends-on": "pe-2.3_prm_1", - "label": "organization-defined credentials" - } - ], - "props": [ - { - "name": "label", - "value": "PE-2(3)" - }, - { - "name": "sort-id", - "value": "pe-02.03" - } - ], - "parts": [ - { - "id": "pe-2.3_smt", - "name": "statement", - "prose": "The organization restricts unescorted access to the facility where the information system resides to personnel with {{ insert: param, pe-2.3_prm_1 }}." - }, - { - "id": "pe-2.3_gdn", - "name": "guidance", - "prose": "Due to the highly sensitive nature of classified information stored within certain facilities, it is important that individuals lacking sufficient security clearances, access approvals, or need to know, be escorted by individuals with appropriate credentials to ensure that such information is not exposed or otherwise compromised.", - "links": [ - { - "href": "#ps-2", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - } - ] - }, - { - "id": "pe-2.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-2.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-2(3)[1]" - } - ], - "prose": "defines credentials to be employed to restrict unescorted access to the facility where the information system resides to authorized personnel;" - }, - { - "id": "pe-2.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-2(3)[2]" - } - ], - "prose": "restricts unescorted access to the facility where the information system resides to personnel with one or more of the following:", - "parts": [ - { - "id": "pe-2.3_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-2(3)[2][a]" - } - ], - "prose": "security clearances for all information contained within the system;" - }, - { - "id": "pe-2.3_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-2(3)[2][b]" - } - ], - "prose": "formal access authorizations for all information contained within the system;" - }, - { - "id": "pe-2.3_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-2(3)[2][c]" - } - ], - "prose": "need for access to all information contained within the system; and/or" - }, - { - "id": "pe-2.3_obj.2.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-2(3)[2][d]" - } - ], - "prose": "organization-defined credentials." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access authorizations\n\nauthorized personnel access list\n\nsecurity clearances\n\naccess authorizations\n\naccess credentials\n\nphysical access control logs or records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access authorization responsibilities\n\norganizational personnel with physical access to information system facility\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for physical access authorizations\n\nautomated mechanisms supporting and/or implementing physical access authorizations" - } - ] - } - ] - } - ] - }, - { - "id": "pe-3", - "class": "SP800-53", - "title": "Physical Access Control", - "params": [ - { - "id": "pe-3_prm_1", - "label": "organization-defined entry/exit points to the facility where the information system resides" - }, - { - "id": "pe-3_prm_2", - "select": { - "how-many": "one-or-more", - "choice": [ - " {{ insert: param, pe-3_prm_3 }} ", - "guards" - ] - } - }, - { - "id": "pe-3_prm_3", - "depends-on": "pe-3_prm_2", - "label": "organization-defined physical access control systems/devices" - }, - { - "id": "pe-3_prm_4", - "label": "organization-defined entry/exit points" - }, - { - "id": "pe-3_prm_5", - "label": "organization-defined security safeguards" - }, - { - "id": "pe-3_prm_6", - "label": "organization-defined circumstances requiring visitor escorts and monitoring" - }, - { - "id": "pe-3_prm_7", - "label": "organization-defined physical access devices" - }, - { - "id": "pe-3_prm_8", - "label": "organization-defined frequency" - }, - { - "id": "pe-3_prm_9", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "PE-3" - }, - { - "name": "sort-id", - "value": "pe-03" - } - ], - "links": [ - { - "href": "#c80c10b3-1294-4984-a4cc-d1733ca432b9", - "rel": "reference" - }, - { - "href": "#ead74ea9-4c9c-446d-9b92-bcbf0ad4b655", - "rel": "reference" - }, - { - "href": "#2a71298a-ee90-490e-80ff-48c967173a47", - "rel": "reference" - }, - { - "href": "#2042d97b-f7f6-4c74-84f8-981867684659", - "rel": "reference" - }, - { - "href": "#2157bb7e-192c-4eaa-877f-93ef6b0a3292", - "rel": "reference" - }, - { - "href": "#6caa237b-531b-43ac-9711-d8f6b97b0377", - "rel": "reference" - }, - { - "href": "#398e33fd-f404-4e5c-b90e-2d50d3181244", - "rel": "reference" - }, - { - "href": "#61081e7f-041d-4033-96a7-44a439071683", - "rel": "reference" - }, - { - "href": "#dd2f5acd-08f1-435a-9837-f8203088dc1a", - "rel": "reference" - }, - { - "href": "#85280698-0417-489d-b214-12bb935fb939", - "rel": "reference" - }, - { - "href": "#5ed1f4d5-1494-421b-97ed-39d3c88ab51f", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pe-3_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pe-3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Enforces physical access authorizations at {{ insert: param, pe-3_prm_1 }} by;", - "parts": [ - { - "id": "pe-3_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Verifying individual access authorizations before granting access to the facility; and" - }, - { - "id": "pe-3_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Controlling ingress/egress to the facility using {{ insert: param, pe-3_prm_2 }};" - } - ] - }, - { - "id": "pe-3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Maintains physical access audit logs for {{ insert: param, pe-3_prm_4 }};" - }, - { - "id": "pe-3_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Provides {{ insert: param, pe-3_prm_5 }} to control access to areas within the facility officially designated as publicly accessible;" - }, - { - "id": "pe-3_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Escorts visitors and monitors visitor activity {{ insert: param, pe-3_prm_6 }};" - }, - { - "id": "pe-3_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Secures keys, combinations, and other physical access devices;" - }, - { - "id": "pe-3_smt.f", - "name": "item", - "props": [ - { - "name": "label", - "value": "f." - } - ], - "prose": "Inventories {{ insert: param, pe-3_prm_7 }} every {{ insert: param, pe-3_prm_8 }}; and" - }, - { - "id": "pe-3_smt.g", - "name": "item", - "props": [ - { - "name": "label", - "value": "g." - } - ], - "prose": "Changes combinations and keys {{ insert: param, pe-3_prm_9 }} and/or when keys are lost, combinations are compromised, or individuals are transferred or terminated." - } - ] - }, - { - "id": "pe-3_gdn", - "name": "guidance", - "prose": "This control applies to organizational employees and visitors. Individuals (e.g., employees, contractors, and others) with permanent physical access authorization credentials are not considered visitors. Organizations determine the types of facility guards needed including, for example, professional physical security staff or other personnel such as administrative staff or information system users. Physical access devices include, for example, keys, locks, combinations, and card readers. Safeguards for publicly accessible areas within organizational facilities include, for example, cameras, monitoring by guards, and isolating selected information systems and/or system components in secured areas. Physical access control systems comply with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. The Federal Identity, Credential, and Access Management Program provides implementation guidance for identity, credential, and access management capabilities for physical access control systems. Organizations have flexibility in the types of audit logs employed. Audit logs can be procedural (e.g., a written log of individuals accessing the facility and when such access occurred), automated (e.g., capturing ID provided by a PIV card), or some combination thereof. Physical access points can include facility access points, interior access points to information systems and/or components requiring supplemental access controls, or both. Components of organizational information systems (e.g., workstations, terminals) may be located in areas designated as publicly accessible with organizations safeguarding access to such devices.", - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pe-4", - "rel": "related" - }, - { - "href": "#pe-5", - "rel": "related" - }, - { - "href": "#ps-3", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - } - ] - }, - { - "id": "pe-3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(a)" - } - ], - "parts": [ - { - "id": "pe-3.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(a)[1]" - } - ], - "prose": "defines entry/exit points to the facility where the information system resides;" - }, - { - "id": "pe-3.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(a)[2]" - } - ], - "prose": "enforces physical access authorizations at organization-defined entry/exit points to the facility where the information system resides by:", - "parts": [ - { - "id": "pe-3.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(a)[2](1)" - } - ], - "prose": "verifying individual access authorizations before granting access to the facility;" - }, - { - "id": "pe-3.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(a)[2](2)" - } - ], - "parts": [ - { - "id": "pe-3.a.2_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(a)[2](2)[a]" - } - ], - "prose": "defining physical access control systems/devices to be employed to control ingress/egress to the facility where the information system resides;" - }, - { - "id": "pe-3.a.2_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(a)[2](2)[b]" - } - ], - "prose": "using one or more of the following ways to control ingress/egress to the facility:", - "parts": [ - { - "id": "pe-3.a.2_obj.2.b.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(a)[2](2)[b][1]" - } - ], - "prose": "organization-defined physical access control systems/devices; and/or" - }, - { - "id": "pe-3.a.2_obj.2.b.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(a)[2](2)[b][2]" - } - ], - "prose": "guards;" - } - ] - } - ] - } - ] - } - ] - }, - { - "id": "pe-3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(b)" - } - ], - "parts": [ - { - "id": "pe-3.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(b)[1]" - } - ], - "prose": "defines entry/exit points for which physical access audit logs are to be maintained;" - }, - { - "id": "pe-3.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(b)[2]" - } - ], - "prose": "maintains physical access audit logs for organization-defined entry/exit points;" - } - ] - }, - { - "id": "pe-3.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(c)" - } - ], - "parts": [ - { - "id": "pe-3.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(c)[1]" - } - ], - "prose": "defines security safeguards to be employed to control access to areas within the facility officially designated as publicly accessible;" - }, - { - "id": "pe-3.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(c)[2]" - } - ], - "prose": "provides organization-defined security safeguards to control access to areas within the facility officially designated as publicly accessible;" - } - ] - }, - { - "id": "pe-3.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(d)" - } - ], - "parts": [ - { - "id": "pe-3.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(d)[1]" - } - ], - "prose": "defines circumstances requiring visitor:", - "parts": [ - { - "id": "pe-3.d_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(d)[1][a]" - } - ], - "prose": "escorts;" - }, - { - "id": "pe-3.d_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(d)[1][b]" - } - ], - "prose": "monitoring;" - } - ] - }, - { - "id": "pe-3.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(d)[2]" - } - ], - "prose": "in accordance with organization-defined circumstances requiring visitor escorts and monitoring:", - "parts": [ - { - "id": "pe-3.d_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(d)[2][a]" - } - ], - "prose": "escorts visitors;" - }, - { - "id": "pe-3.d_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(d)[2][b]" - } - ], - "prose": "monitors visitor activities;" - } - ] - } - ] - }, - { - "id": "pe-3.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(e)" - } - ], - "parts": [ - { - "id": "pe-3.e_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(e)[1]" - } - ], - "prose": "secures keys;" - }, - { - "id": "pe-3.e_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(e)[2]" - } - ], - "prose": "secures combinations;" - }, - { - "id": "pe-3.e_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(e)[3]" - } - ], - "prose": "secures other physical access devices;" - } - ] - }, - { - "id": "pe-3.f_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(f)" - } - ], - "parts": [ - { - "id": "pe-3.f_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(f)[1]" - } - ], - "prose": "defines physical access devices to be inventoried;" - }, - { - "id": "pe-3.f_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(f)[2]" - } - ], - "prose": "defines the frequency to inventory organization-defined physical access devices;" - }, - { - "id": "pe-3.f_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(f)[3]" - } - ], - "prose": "inventories the organization-defined physical access devices with the organization-defined frequency;" - } - ] - }, - { - "id": "pe-3.g_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(g)" - } - ], - "parts": [ - { - "id": "pe-3.g_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(g)[1]" - } - ], - "prose": "defines the frequency to change combinations and keys; and" - }, - { - "id": "pe-3.g_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(g)[2]" - } - ], - "prose": "changes combinations and keys with the organization-defined frequency and/or when:", - "parts": [ - { - "id": "pe-3.g_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(g)[2][a]" - } - ], - "prose": "keys are lost;" - }, - { - "id": "pe-3.g_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(g)[2][b]" - } - ], - "prose": "combinations are compromised;" - }, - { - "id": "pe-3.g_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(g)[2][c]" - } - ], - "prose": "individuals are transferred or terminated." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access control\n\nsecurity plan\n\nphysical access control logs or records\n\ninventory records of physical access control devices\n\ninformation system entry and exit points\n\nrecords of key and lock combination changes\n\nstorage locations for physical access control devices\n\nphysical access control devices\n\nlist of security safeguards controlling access to designated publicly accessible areas within facility\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for physical access control\n\nautomated mechanisms supporting and/or implementing physical access control\n\nphysical access control devices" - } - ] - } - ], - "controls": [ - { - "id": "pe-3.1", - "class": "SP800-53-enhancement", - "title": "Information System Access", - "params": [ - { - "id": "pe-3.1_prm_1", - "label": "organization-defined physical spaces containing one or more components of the information system" - } - ], - "props": [ - { - "name": "label", - "value": "PE-3(1)" - }, - { - "name": "sort-id", - "value": "pe-03.01" - } - ], - "parts": [ - { - "id": "pe-3.1_smt", - "name": "statement", - "prose": "The organization enforces physical access authorizations to the information system in addition to the physical access controls for the facility at {{ insert: param, pe-3.1_prm_1 }}." - }, - { - "id": "pe-3.1_gdn", - "name": "guidance", - "prose": "This control enhancement provides additional physical security for those areas within facilities where there is a concentration of information system components (e.g., server rooms, media storage areas, data and communications centers).", - "links": [ - { - "href": "#ps-2", - "rel": "related" - } - ] - }, - { - "id": "pe-3.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-3.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(1)[1]" - } - ], - "prose": "defines physical spaces containing one or more components of the information system; and" - }, - { - "id": "pe-3.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(1)[2]" - } - ], - "prose": "enforces physical access authorizations to the information system in addition to the physical access controls for the facility at organization-defined physical spaces containing one or more components of the information system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access control\n\nphysical access control logs or records\n\nphysical access control devices\n\naccess authorizations\n\naccess credentials\n\ninformation system entry and exit points\n\nlist of areas within the facility containing concentrations of information system components or information system components requiring additional physical protection\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access authorization responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for physical access control to the information system/components\n\nautomated mechanisms supporting and/or implementing physical access control for facility areas containing information system components" - } - ] - } - ] - }, - { - "id": "pe-3.2", - "class": "SP800-53-enhancement", - "title": "Facility / Information System Boundaries", - "params": [ - { - "id": "pe-3.2_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "PE-3(2)" - }, - { - "name": "sort-id", - "value": "pe-03.02" - } - ], - "parts": [ - { - "id": "pe-3.2_smt", - "name": "statement", - "prose": "The organization performs security checks {{ insert: param, pe-3.2_prm_1 }} at the physical boundary of the facility or information system for unauthorized exfiltration of information or removal of information system components." - }, - { - "id": "pe-3.2_gdn", - "name": "guidance", - "prose": "Organizations determine the extent, frequency, and/or randomness of security checks to adequately mitigate risk associated with exfiltration.", - "links": [ - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - } - ] - }, - { - "id": "pe-3.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-3.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(2)[1]" - } - ], - "prose": "defines the frequency to perform security checks at the physical boundary of the facility or information system for:", - "parts": [ - { - "id": "pe-3.2_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(2)[1][a]" - } - ], - "prose": "unauthorized exfiltration of information; or" - }, - { - "id": "pe-3.2_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(2)[1][b]" - } - ], - "prose": "removal of information system components; and" - } - ] - }, - { - "id": "pe-3.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(2)[2]" - } - ], - "prose": "performs security checks with the organization-defined frequency at the physical boundary of the facility or information system for:", - "parts": [ - { - "id": "pe-3.2_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(2)[2][a]" - } - ], - "prose": "unauthorized exfiltration of information; or" - }, - { - "id": "pe-3.2_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(2)[2][b]" - } - ], - "prose": "removal of information system components." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access control\n\nphysical access control logs or records\n\nrecords of security checks\n\nsecurity audit reports\n\nsecurity inspection reports\n\nfacility layout documentation\n\ninformation system entry and exit points\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for physical access control to the facility and/or information system\n\nautomated mechanisms supporting and/or implementing physical access control for the facility or information system\n\nautomated mechanisms supporting and/or implementing security checks for unauthorized exfiltration of information" - } - ] - } - ] - }, - { - "id": "pe-3.3", - "class": "SP800-53-enhancement", - "title": "Continuous Guards / Alarms / Monitoring", - "props": [ - { - "name": "label", - "value": "PE-3(3)" - }, - { - "name": "sort-id", - "value": "pe-03.03" - } - ], - "parts": [ - { - "id": "pe-3.3_smt", - "name": "statement", - "prose": "The organization employs guards and/or alarms to monitor every physical access point to the facility where the information system resides 24 hours per day, 7 days per week." - }, - { - "id": "pe-3.3_gdn", - "name": "guidance", - "links": [ - { - "href": "#cp-6", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - } - ] - }, - { - "id": "pe-3.3_obj", - "name": "objective", - "prose": "Determine if the organization employs one or more of the following to monitor every physical access point to the facility where the information system resides 24 hours per day, 7 days per week:", - "parts": [ - { - "id": "pe-3.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(3)[1]" - } - ], - "prose": "guards; and/or" - }, - { - "id": "pe-3.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(3)[2]" - } - ], - "prose": "alarms." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access control\n\nphysical access control logs or records\n\nphysical access control devices\n\nfacility surveillance records\n\nfacility layout documentation\n\ninformation system entry and exit points\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for physical access control to the facility where the information system resides\n\nautomated mechanisms supporting and/or implementing physical access control for the facility where the information system resides" - } - ] - } - ] - }, - { - "id": "pe-3.4", - "class": "SP800-53-enhancement", - "title": "Lockable Casings", - "params": [ - { - "id": "pe-3.4_prm_1", - "label": "organization-defined information system components" - } - ], - "props": [ - { - "name": "label", - "value": "PE-3(4)" - }, - { - "name": "sort-id", - "value": "pe-03.04" - } - ], - "parts": [ - { - "id": "pe-3.4_smt", - "name": "statement", - "prose": "The organization uses lockable physical casings to protect {{ insert: param, pe-3.4_prm_1 }} from unauthorized physical access." - }, - { - "id": "pe-3.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-3.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(4)[1]" - } - ], - "prose": "defines information system components to be protected from unauthorized physical access using lockable physical casings; and" - }, - { - "id": "pe-3.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(4)[2]" - } - ], - "prose": "uses lockable physical casings to protect organization-defined information system components from unauthorized physical access." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access control\n\nsecurity plan\n\nlist of information system components requiring protection through lockable physical casings\n\nlockable physical casings\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Lockable physical casings" - } - ] - } - ] - }, - { - "id": "pe-3.5", - "class": "SP800-53-enhancement", - "title": "Tamper Protection", - "params": [ - { - "id": "pe-3.5_prm_1", - "label": "organization-defined security safeguards" - }, - { - "id": "pe-3.5_prm_2", - "select": { - "how-many": "one-or-more", - "choice": [ - "detect", - "prevent" - ] - } - }, - { - "id": "pe-3.5_prm_3", - "label": "organization-defined hardware components" - } - ], - "props": [ - { - "name": "label", - "value": "PE-3(5)" - }, - { - "name": "sort-id", - "value": "pe-03.05" - } - ], - "parts": [ - { - "id": "pe-3.5_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, pe-3.5_prm_1 }} to {{ insert: param, pe-3.5_prm_2 }} physical tampering or alteration of {{ insert: param, pe-3.5_prm_3 }} within the information system." - }, - { - "id": "pe-3.5_gdn", - "name": "guidance", - "prose": "Organizations may implement tamper detection/prevention at selected hardware components or tamper detection at some components and tamper prevention at other components. Tamper detection/prevention activities can employ many types of anti-tamper technologies including, for example, tamper-detection seals and anti-tamper coatings. Anti-tamper programs help to detect hardware alterations through counterfeiting and other supply chain-related risks.", - "links": [ - { - "href": "#sa-12", - "rel": "related" - } - ] - }, - { - "id": "pe-3.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-3.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(5)[1]" - } - ], - "prose": "defines security safeguards to be employed to detect and/or prevent physical tampering or alteration of organization-defined hardware components within the information system;" - }, - { - "id": "pe-3.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(5)[2]" - } - ], - "prose": "defines hardware components within the information system for which security safeguards are to be employed to detect and/or prevent physical tampering or alteration of such components;" - }, - { - "id": "pe-3.5_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(5)[3]" - } - ], - "prose": "employs organization-defined security safeguards to do one or more of the following:", - "parts": [ - { - "id": "pe-3.5_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(5)[3][a]" - } - ], - "prose": "detect physical tampering or alteration of organization-defined hardware components within the information system; and/or" - }, - { - "id": "pe-3.5_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(5)[3][b]" - } - ], - "prose": "prevent physical tampering or alteration of organization-defined hardware components within the information system." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access control\n\nlist of security safeguards to detect/prevent physical tampering or alteration of information system hardware components\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes to detect/prevent physical tampering or alteration of information system hardware components\n\nautomated mechanisms/security safeguards supporting and/or implementing detection/prevention of physical tampering/alternation of information system hardware components" - } - ] - } - ] - }, - { - "id": "pe-3.6", - "class": "SP800-53-enhancement", - "title": "Facility Penetration Testing", - "params": [ - { - "id": "pe-3.6_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "PE-3(6)" - }, - { - "name": "sort-id", - "value": "pe-03.06" - } - ], - "parts": [ - { - "id": "pe-3.6_smt", - "name": "statement", - "prose": "The organization employs a penetration testing process that includes {{ insert: param, pe-3.6_prm_1 }}, unannounced attempts to bypass or circumvent security controls associated with physical access points to the facility." - }, - { - "id": "pe-3.6_gdn", - "name": "guidance", - "links": [ - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - } - ] - }, - { - "id": "pe-3.6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-3.6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(6)[1]" - } - ], - "prose": "defines the frequency of unannounced attempts to be included in a penetration testing process to bypass or circumvent security controls associated with physical access points to the facility; and" - }, - { - "id": "pe-3.6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-3(6)[2]" - } - ], - "prose": "employs a penetration testing process with the organization-defined frequency that includes unannounced attempts to bypass or circumvent security controls associated with physical access points to the facility." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access control\n\nprocedures addressing penetration testing\n\nrules of engagement and associated documentation\n\npenetration test results\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for facility penetration testing\n\nautomated mechanisms supporting and/or implementing facility penetration testing" - } - ] - } - ] - } - ] - }, - { - "id": "pe-4", - "class": "SP800-53", - "title": "Access Control for Transmission Medium", - "params": [ - { - "id": "pe-4_prm_1", - "label": "organization-defined information system distribution and transmission lines" - }, - { - "id": "pe-4_prm_2", - "label": "organization-defined security safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "PE-4" - }, - { - "name": "sort-id", - "value": "pe-04" - } - ], - "links": [ - { - "href": "#06dff0ea-3848-4945-8d91-e955ee69f05d", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pe-4_smt", - "name": "statement", - "prose": "The organization controls physical access to {{ insert: param, pe-4_prm_1 }} within organizational facilities using {{ insert: param, pe-4_prm_2 }}." - }, - { - "id": "pe-4_gdn", - "name": "guidance", - "prose": "Physical security safeguards applied to information system distribution and transmission lines help to prevent accidental damage, disruption, and physical tampering. In addition, physical safeguards may be necessary to help prevent eavesdropping or in transit modification of unencrypted transmissions. Security safeguards to control physical access to system distribution and transmission lines include, for example: (i) locked wiring closets; (ii) disconnected or locked spare jacks; and/or (iii) protection of cabling by conduit or cable trays.", - "links": [ - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pe-5", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - } - ] - }, - { - "id": "pe-4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-4[1]" - } - ], - "prose": "defines information system distribution and transmission lines requiring physical access controls;" - }, - { - "id": "pe-4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-4[2]" - } - ], - "prose": "defines security safeguards to be employed to control physical access to organization-defined information system distribution and transmission lines within organizational facilities; and" - }, - { - "id": "pe-4_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-4[3]" - } - ], - "prose": "controls physical access to organization-defined information system distribution and transmission lines within organizational facilities using organization-defined security safeguards." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing access control for transmission medium\n\ninformation system design documentation\n\nfacility communications and wiring diagrams\n\nlist of physical security safeguards applied to information system distribution and transmission lines\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for access control to distribution and transmission lines\n\nautomated mechanisms/security safeguards supporting and/or implementing access control to distribution and transmission lines" - } - ] - } - ] - }, - { - "id": "pe-5", - "class": "SP800-53", - "title": "Access Control for Output Devices", - "props": [ - { - "name": "label", - "value": "PE-5" - }, - { - "name": "sort-id", - "value": "pe-05" - } - ], - "parts": [ - { - "id": "pe-5_smt", - "name": "statement", - "prose": "The organization controls physical access to information system output devices to prevent unauthorized individuals from obtaining the output." - }, - { - "id": "pe-5_gdn", - "name": "guidance", - "prose": "Controlling physical access to output devices includes, for example, placing output devices in locked rooms or other secured areas and allowing access to authorized individuals only, and placing output devices in locations that can be monitored by organizational personnel. Monitors, printers, copiers, scanners, facsimile machines, and audio devices are examples of information system output devices.", - "links": [ - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pe-4", - "rel": "related" - }, - { - "href": "#pe-18", - "rel": "related" - } - ] - }, - { - "id": "pe-5_obj", - "name": "objective", - "prose": "Determine if the organization controls physical access to information system output devices to prevent unauthorized individuals from obtaining the output." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing access control for display medium\n\nfacility layout of information system components\n\nactual displays from information system components\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for access control to output devices\n\nautomated mechanisms supporting and/or implementing access control to output devices" - } - ] - } - ], - "controls": [ - { - "id": "pe-5.1", - "class": "SP800-53-enhancement", - "title": "Access to Output by Authorized Individuals", - "params": [ - { - "id": "pe-5.1_prm_1", - "label": "organization-defined output devices" - } - ], - "props": [ - { - "name": "label", - "value": "PE-5(1)" - }, - { - "name": "sort-id", - "value": "pe-05.01" - } - ], - "parts": [ - { - "id": "pe-5.1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pe-5.1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Controls physical access to output from {{ insert: param, pe-5.1_prm_1 }}; and" - }, - { - "id": "pe-5.1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Ensures that only authorized individuals receive output from the device." - } - ] - }, - { - "id": "pe-5.1_gdn", - "name": "guidance", - "prose": "Controlling physical access to selected output devices includes, for example, placing printers, copiers, and facsimile machines in controlled areas with keypad access controls or limiting access to individuals with certain types of badges." - }, - { - "id": "pe-5.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-5.1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-5(1)(a)" - } - ], - "parts": [ - { - "id": "pe-5.1.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-5(1)(a)[1]" - } - ], - "prose": "defines output devices whose output requires physical access controls;" - }, - { - "id": "pe-5.1.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-5(1)(a)[2]" - } - ], - "prose": "controls physical access to output from organization-defined output devices; and" - } - ], - "links": [ - { - "href": "#pe-5.1_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "pe-5.1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-5(1)(b)" - } - ], - "prose": "ensures that only authorized individuals receive output from the device.", - "links": [ - { - "href": "#pe-5.1_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access control\n\nlist of output devices and associated outputs requiring physical access controls\n\nphysical access control logs or records for areas containing output devices and related outputs\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for access control to output devices\n\nautomated mechanisms supporting and/or implementing access control to output devices" - } - ] - } - ] - }, - { - "id": "pe-5.2", - "class": "SP800-53-enhancement", - "title": "Access to Output by Individual Identity", - "params": [ - { - "id": "pe-5.2_prm_1", - "label": "organization-defined output devices" - } - ], - "props": [ - { - "name": "label", - "value": "PE-5(2)" - }, - { - "name": "sort-id", - "value": "pe-05.02" - } - ], - "parts": [ - { - "id": "pe-5.2_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "pe-5.2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Controls physical access to output from {{ insert: param, pe-5.2_prm_1 }}; and" - }, - { - "id": "pe-5.2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Links individual identity to receipt of the output from the device." - } - ] - }, - { - "id": "pe-5.2_gdn", - "name": "guidance", - "prose": "Controlling physical access to selected output devices includes, for example, installing security functionality on printers, copiers, and facsimile machines that allows organizations to implement authentication (e.g., using a PIN or hardware token) on output devices prior to the release of output to individuals." - }, - { - "id": "pe-5.2_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "pe-5.2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-5(2)(a)" - } - ], - "parts": [ - { - "id": "pe-5.2.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-5(2)(a)[1]" - } - ], - "prose": "the organization defines output devices whose output requires physical access controls;" - }, - { - "id": "pe-5.2.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-5(2)(a)[2]" - } - ], - "prose": "the information system controls physical access to output from organization-defined output devices; and" - } - ], - "links": [ - { - "href": "#pe-5.2_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "pe-5.2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-5(2)(b)" - } - ], - "prose": "the information system links individual identity to receipt of the output from the device.", - "links": [ - { - "href": "#pe-5.2_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access control\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of output devices and associated outputs requiring physical access controls\n\nphysical access control logs or records for areas containing output devices and related outputs\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for access control to output devices\n\nautomated mechanisms supporting and/or implementing access control to output devices" - } - ] - } - ] - }, - { - "id": "pe-5.3", - "class": "SP800-53-enhancement", - "title": "Marking Output Devices", - "params": [ - { - "id": "pe-5.3_prm_1", - "label": "organization-defined information system output devices" - } - ], - "props": [ - { - "name": "label", - "value": "PE-5(3)" - }, - { - "name": "sort-id", - "value": "pe-05.03" - } - ], - "parts": [ - { - "id": "pe-5.3_smt", - "name": "statement", - "prose": "The organization marks {{ insert: param, pe-5.3_prm_1 }} indicating the appropriate security marking of the information permitted to be output from the device." - }, - { - "id": "pe-5.3_gdn", - "name": "guidance", - "prose": "Outputs devices include, for example, printers, monitors, facsimile machines, scanners, copiers, and audio devices. This control enhancement is generally applicable to information system output devices other than mobiles devices." - }, - { - "id": "pe-5.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-5.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-5(3)[1]" - } - ], - "prose": "defines information system output devices to be marked with appropriate security marking of the information permitted to be output from such devices; and" - }, - { - "id": "pe-5.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-5(3)[2]" - } - ], - "prose": "marks organization-defined information system output devices indicating the appropriate security marking of the information permitted to be output from the device." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access control\n\nsecurity markings for information types permitted as output from information system output devices\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for marking output devices" - } - ] - } - ] - } - ] - }, - { - "id": "pe-6", - "class": "SP800-53", - "title": "Monitoring Physical Access", - "params": [ - { - "id": "pe-6_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "pe-6_prm_2", - "label": "organization-defined events or potential indications of events" - } - ], - "props": [ - { - "name": "label", - "value": "PE-6" - }, - { - "name": "sort-id", - "value": "pe-06" - } - ], - "parts": [ - { - "id": "pe-6_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pe-6_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Monitors physical access to the facility where the information system resides to detect and respond to physical security incidents;" - }, - { - "id": "pe-6_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews physical access logs {{ insert: param, pe-6_prm_1 }} and upon occurrence of {{ insert: param, pe-6_prm_2 }}; and" - }, - { - "id": "pe-6_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Coordinates results of reviews and investigations with the organizational incident response capability." - } - ] - }, - { - "id": "pe-6_gdn", - "name": "guidance", - "prose": "Organizational incident response capabilities include investigations of and responses to detected physical security incidents. Security incidents include, for example, apparent security violations or suspicious physical access activities. Suspicious physical access activities include, for example: (i) accesses outside of normal work hours; (ii) repeated accesses to areas not normally accessed; (iii) accesses for unusual lengths of time; and (iv) out-of-sequence accesses.", - "links": [ - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - } - ] - }, - { - "id": "pe-6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-6.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-6(a)" - } - ], - "prose": "monitors physical access to the facility where the information system resides to detect and respond to physical security incidents;" - }, - { - "id": "pe-6.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-6(b)" - } - ], - "parts": [ - { - "id": "pe-6.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-6(b)[1]" - } - ], - "prose": "defines the frequency to review physical access logs;" - }, - { - "id": "pe-6.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-6(b)[2]" - } - ], - "prose": "defines events or potential indication of events requiring physical access logs to be reviewed;" - }, - { - "id": "pe-6.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-6(b)[3]" - } - ], - "prose": "reviews physical access logs with the organization-defined frequency and upon occurrence of organization-defined events or potential indications of events; and" - } - ] - }, - { - "id": "pe-6.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-6(c)" - } - ], - "prose": "coordinates results of reviews and investigations with the organizational incident response capability." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access monitoring\n\nsecurity plan\n\nphysical access logs or records\n\nphysical access monitoring records\n\nphysical access log reviews\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access monitoring responsibilities\n\norganizational personnel with incident response responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring physical access\n\nautomated mechanisms supporting and/or implementing physical access monitoring\n\nautomated mechanisms supporting and/or implementing reviewing of physical access logs" - } - ] - } - ], - "controls": [ - { - "id": "pe-6.1", - "class": "SP800-53-enhancement", - "title": "Intrusion Alarms / Surveillance Equipment", - "props": [ - { - "name": "label", - "value": "PE-6(1)" - }, - { - "name": "sort-id", - "value": "pe-06.01" - } - ], - "parts": [ - { - "id": "pe-6.1_smt", - "name": "statement", - "prose": "The organization monitors physical intrusion alarms and surveillance equipment." - }, - { - "id": "pe-6.1_obj", - "name": "objective", - "prose": "Determine if the organization monitors physical intrusion alarms and surveillance equipment." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access monitoring\n\nsecurity plan\n\nphysical access logs or records\n\nphysical access monitoring records\n\nphysical access log reviews\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access monitoring responsibilities\n\norganizational personnel with incident response responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring physical intrusion alarms and surveillance equipment\n\nautomated mechanisms supporting and/or implementing physical access monitoring\n\nautomated mechanisms supporting and/or implementing physical intrusion alarms and surveillance equipment" - } - ] - } - ] - }, - { - "id": "pe-6.2", - "class": "SP800-53-enhancement", - "title": "Automated Intrusion Recognition / Responses", - "params": [ - { - "id": "pe-6.2_prm_1", - "label": "organization-defined classes/types of intrusions" - }, - { - "id": "pe-6.2_prm_2", - "label": "organization-defined response actions" - } - ], - "props": [ - { - "name": "label", - "value": "PE-6(2)" - }, - { - "name": "sort-id", - "value": "pe-06.02" - } - ], - "parts": [ - { - "id": "pe-6.2_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to recognize {{ insert: param, pe-6.2_prm_1 }} and initiate {{ insert: param, pe-6.2_prm_2 }}." - }, - { - "id": "pe-6.2_gdn", - "name": "guidance", - "links": [ - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "pe-6.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-6.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-6(2)[1]" - } - ], - "prose": "defines classes/types of intrusions to be recognized by automated mechanisms;" - }, - { - "id": "pe-6.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-6(2)[2]" - } - ], - "prose": "defines response actions to be initiated by automated mechanisms when organization-defined classes/types of intrusions are recognized; and" - }, - { - "id": "pe-6.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-6(2)[3]" - } - ], - "prose": "employs automated mechanisms to recognize organization-defined classes/types of intrusions and initiate organization-defined response actions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access monitoring\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of response actions to be initiated when specific classes/types of intrusions are recognized\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access monitoring responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring physical access\n\nautomated mechanisms supporting and/or implementing physical access monitoring\n\nautomated mechanisms supporting and/or implementing recognition of classes/types of intrusions and initiation of a response" - } - ] - } - ] - }, - { - "id": "pe-6.3", - "class": "SP800-53-enhancement", - "title": "Video Surveillance", - "params": [ - { - "id": "pe-6.3_prm_1", - "label": "organization-defined operational areas" - }, - { - "id": "pe-6.3_prm_2", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "PE-6(3)" - }, - { - "name": "sort-id", - "value": "pe-06.03" - } - ], - "parts": [ - { - "id": "pe-6.3_smt", - "name": "statement", - "prose": "The organization employs video surveillance of {{ insert: param, pe-6.3_prm_1 }} and retains video recordings for {{ insert: param, pe-6.3_prm_2 }}." - }, - { - "id": "pe-6.3_gdn", - "name": "guidance", - "prose": "This control enhancement focuses on recording surveillance video for purposes of subsequent review, if circumstances so warrant (e.g., a break-in detected by other means). It does not require monitoring surveillance video although organizations may choose to do so. Note that there may be legal considerations when performing and retaining video surveillance, especially if such surveillance is in a public location." - }, - { - "id": "pe-6.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-6.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-6(3)[1]" - } - ], - "prose": "defines operational areas where video surveillance is to be employed;" - }, - { - "id": "pe-6.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-6(3)[2]" - } - ], - "prose": "defines a time period to retain video recordings of organization-defined operational areas;" - }, - { - "id": "pe-6.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-6(3)[3]" - } - ], - "parts": [ - { - "id": "pe-6.3_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-6(3)[3][a]" - } - ], - "prose": "employs video surveillance of organization-defined operational areas; and" - }, - { - "id": "pe-6.3_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-6(3)[3][b]" - } - ], - "prose": "retains video recordings for the organization-defined time period." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access monitoring\n\nvideo surveillance equipment used to monitor operational areas\n\nvideo recordings of operational areas where video surveillance is employed\n\nvideo surveillance equipment logs or records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access monitoring responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring physical access\n\nautomated mechanisms supporting and/or implementing physical access monitoring\n\nautomated mechanisms supporting and/or implementing video surveillance" - } - ] - } - ] - }, - { - "id": "pe-6.4", - "class": "SP800-53-enhancement", - "title": "Monitoring Physical Access to Information Systems", - "params": [ - { - "id": "pe-6.4_prm_1", - "label": "organization-defined physical spaces containing one or more components of the information system" - } - ], - "props": [ - { - "name": "label", - "value": "PE-6(4)" - }, - { - "name": "sort-id", - "value": "pe-06.04" - } - ], - "parts": [ - { - "id": "pe-6.4_smt", - "name": "statement", - "prose": "The organization monitors physical access to the information system in addition to the physical access monitoring of the facility as {{ insert: param, pe-6.4_prm_1 }}." - }, - { - "id": "pe-6.4_gdn", - "name": "guidance", - "prose": "This control enhancement provides additional monitoring for those areas within facilities where there is a concentration of information system components (e.g., server rooms, media storage areas, communications centers).", - "links": [ - { - "href": "#ps-2", - "rel": "related" - }, - { - "href": "#ps-3", - "rel": "related" - } - ] - }, - { - "id": "pe-6.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-6.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-6(4)[1]" - } - ], - "prose": "defines physical spaces containing one or more components of the information system; and" - }, - { - "id": "pe-6.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-6(4)[2]" - } - ], - "prose": "monitors physical access to the information system in addition to the physical access monitoring of the facility at organization-defined physical spaces containing one or more components of the information system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access monitoring\n\nphysical access control logs or records\n\nphysical access control devices\n\naccess authorizations\n\naccess credentials\n\nlist of areas within the facility containing concentrations of information system components or information system components requiring additional physical access monitoring\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with physical access monitoring responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring physical access to the information system\n\nautomated mechanisms supporting and/or implementing physical access monitoring for facility areas containing information system components" - } - ] - } - ] - } - ] - }, - { - "id": "pe-7", - "class": "SP800-53", - "title": "Visitor Control", - "props": [ - { - "name": "label", - "value": "PE-7" - }, - { - "name": "sort-id", - "value": "pe-07" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#pe-2", - "rel": "incorporated-into" - }, - { - "href": "#pe-3", - "rel": "incorporated-into" - } - ] - }, - { - "id": "pe-8", - "class": "SP800-53", - "title": "Visitor Access Records", - "params": [ - { - "id": "pe-8_prm_1", - "label": "organization-defined time period" - }, - { - "id": "pe-8_prm_2", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "PE-8" - }, - { - "name": "sort-id", - "value": "pe-08" - } - ], - "parts": [ - { - "id": "pe-8_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pe-8_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Maintains visitor access records to the facility where the information system resides for {{ insert: param, pe-8_prm_1 }}; and" - }, - { - "id": "pe-8_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews visitor access records {{ insert: param, pe-8_prm_2 }}." - } - ] - }, - { - "id": "pe-8_gdn", - "name": "guidance", - "prose": "Visitor access records include, for example, names and organizations of persons visiting, visitor signatures, forms of identification, dates of access, entry and departure times, purposes of visits, and names and organizations of persons visited. Visitor access records are not required for publicly accessible areas." - }, - { - "id": "pe-8_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-8.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-8(a)" - } - ], - "parts": [ - { - "id": "pe-8.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-8(a)[1]" - } - ], - "prose": "defines the time period to maintain visitor access records to the facility where the information system resides;" - }, - { - "id": "pe-8.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-8(a)[2]" - } - ], - "prose": "maintains visitor access records to the facility where the information system resides for the organization-defined time period;" - } - ] - }, - { - "id": "pe-8.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-8(b)" - } - ], - "parts": [ - { - "id": "pe-8.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-8(b)[1]" - } - ], - "prose": "defines the frequency to review visitor access records; and" - }, - { - "id": "pe-8.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-8(b)[2]" - } - ], - "prose": "reviews visitor access records with the organization-defined frequency." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing visitor access records\n\nsecurity plan\n\nvisitor access control logs or records\n\nvisitor access record or log reviews\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with visitor access records responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for maintaining and reviewing visitor access records\n\nautomated mechanisms supporting and/or implementing maintenance and review of visitor access records" - } - ] - } - ], - "controls": [ - { - "id": "pe-8.1", - "class": "SP800-53-enhancement", - "title": "Automated Records Maintenance / Review", - "props": [ - { - "name": "label", - "value": "PE-8(1)" - }, - { - "name": "sort-id", - "value": "pe-08.01" - } - ], - "parts": [ - { - "id": "pe-8.1_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to facilitate the maintenance and review of visitor access records." - }, - { - "id": "pe-8.1_obj", - "name": "objective", - "prose": "Determine if the organization employs automated mechanisms to facilitate the maintenance and review of visitor access records." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing visitor access records\n\nautomated mechanisms supporting management of visitor access records\n\nvisitor access control logs or records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with visitor access records responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for maintaining and reviewing visitor access records\n\nautomated mechanisms supporting and/or implementing maintenance and review of visitor access records" - } - ] - } - ] - }, - { - "id": "pe-8.2", - "class": "SP800-53-enhancement", - "title": "Physical Access Records", - "props": [ - { - "name": "label", - "value": "PE-8(2)" - }, - { - "name": "sort-id", - "value": "pe-08.02" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#pe-2", - "rel": "incorporated-into" - } - ] - } - ] - }, - { - "id": "pe-9", - "class": "SP800-53", - "title": "Power Equipment and Cabling", - "props": [ - { - "name": "label", - "value": "PE-9" - }, - { - "name": "sort-id", - "value": "pe-09" - } - ], - "parts": [ - { - "id": "pe-9_smt", - "name": "statement", - "prose": "The organization protects power equipment and power cabling for the information system from damage and destruction." - }, - { - "id": "pe-9_gdn", - "name": "guidance", - "prose": "Organizations determine the types of protection necessary for power equipment and cabling employed at different locations both internal and external to organizational facilities and environments of operation. This includes, for example, generators and power cabling outside of buildings, internal cabling and uninterruptable power sources within an office or data center, and power sources for self-contained entities such as vehicles and satellites.", - "links": [ - { - "href": "#pe-4", - "rel": "related" - } - ] - }, - { - "id": "pe-9_obj", - "name": "objective", - "prose": "Determine if the organization protects power equipment and power cabling for the information system from damage and destruction." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing power equipment/cabling protection\n\nfacilities housing power equipment/cabling\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for protecting power equipment/cabling\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing protection of power equipment/cabling" - } - ] - } - ], - "controls": [ - { - "id": "pe-9.1", - "class": "SP800-53-enhancement", - "title": "Redundant Cabling", - "params": [ - { - "id": "pe-9.1_prm_1", - "label": "organization-defined distance" - } - ], - "props": [ - { - "name": "label", - "value": "PE-9(1)" - }, - { - "name": "sort-id", - "value": "pe-09.01" - } - ], - "parts": [ - { - "id": "pe-9.1_smt", - "name": "statement", - "prose": "The organization employs redundant power cabling paths that are physically separated by {{ insert: param, pe-9.1_prm_1 }}." - }, - { - "id": "pe-9.1_gdn", - "name": "guidance", - "prose": "Physically separate, redundant power cables help to ensure that power continues to flow in the event one of the cables is cut or otherwise damaged." - }, - { - "id": "pe-9.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-9.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-9(1)[1]" - } - ], - "prose": "defines the distance by which redundant power cabling paths are to be physically separated; and" - }, - { - "id": "pe-9.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-9(1)[2]" - } - ], - "prose": "employs redundant power cabling paths that are physically separated by organization-defined distance." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing power equipment/cabling protection\n\nfacilities housing power equipment/cabling\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for protecting power equipment/cabling\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing protection of power equipment/cabling" - } - ] - } - ] - }, - { - "id": "pe-9.2", - "class": "SP800-53-enhancement", - "title": "Automatic Voltage Controls", - "params": [ - { - "id": "pe-9.2_prm_1", - "label": "organization-defined critical information system components" - } - ], - "props": [ - { - "name": "label", - "value": "PE-9(2)" - }, - { - "name": "sort-id", - "value": "pe-09.02" - } - ], - "parts": [ - { - "id": "pe-9.2_smt", - "name": "statement", - "prose": "The organization employs automatic voltage controls for {{ insert: param, pe-9.2_prm_1 }}." - }, - { - "id": "pe-9.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-9.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-9(2)[1]" - } - ], - "prose": "defines critical information system components that require automatic voltage controls; and" - }, - { - "id": "pe-9.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-9(2)[2]" - } - ], - "prose": "employs automatic voltage controls for organization-defined critical information system components." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing voltage control\n\nsecurity plan\n\nlist of critical information system components requiring automatic voltage controls\n\nautomatic voltage control mechanisms and associated configurations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for environmental protection of information system components\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing automatic voltage controls" - } - ] - } - ] - } - ] - }, - { - "id": "pe-10", - "class": "SP800-53", - "title": "Emergency Shutoff", - "params": [ - { - "id": "pe-10_prm_1", - "label": "organization-defined location by information system or system component" - } - ], - "props": [ - { - "name": "label", - "value": "PE-10" - }, - { - "name": "sort-id", - "value": "pe-10" - } - ], - "parts": [ - { - "id": "pe-10_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pe-10_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Provides the capability of shutting off power to the information system or individual system components in emergency situations;" - }, - { - "id": "pe-10_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Places emergency shutoff switches or devices in {{ insert: param, pe-10_prm_1 }} to facilitate safe and easy access for personnel; and" - }, - { - "id": "pe-10_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Protects emergency power shutoff capability from unauthorized activation." - } - ] - }, - { - "id": "pe-10_gdn", - "name": "guidance", - "prose": "This control applies primarily to facilities containing concentrations of information system resources including, for example, data centers, server rooms, and mainframe computer rooms.", - "links": [ - { - "href": "#pe-15", - "rel": "related" - } - ] - }, - { - "id": "pe-10_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-10.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-10(a)" - } - ], - "prose": "provides the capability of shutting off power to the information system or individual system components in emergency situations;" - }, - { - "id": "pe-10.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-10(b)" - } - ], - "parts": [ - { - "id": "pe-10.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-10(b)[1]" - } - ], - "prose": "defines the location of emergency shutoff switches or devices by information system or system component;" - }, - { - "id": "pe-10.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-10(b)[2]" - } - ], - "prose": "places emergency shutoff switches or devices in the organization-defined location by information system or system component to facilitate safe and easy access for personnel; and" - } - ] - }, - { - "id": "pe-10.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-10(c)" - } - ], - "prose": "protects emergency power shutoff capability from unauthorized activation." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing power source emergency shutoff\n\nsecurity plan\n\nemergency shutoff controls or switches\n\nlocations housing emergency shutoff switches and devices\n\nsecurity safeguards protecting emergency power shutoff capability from unauthorized activation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for emergency power shutoff capability (both implementing and using the capability)\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing emergency power shutoff" - } - ] - } - ], - "controls": [ - { - "id": "pe-10.1", - "class": "SP800-53-enhancement", - "title": "Accidental / Unauthorized Activation", - "props": [ - { - "name": "label", - "value": "PE-10(1)" - }, - { - "name": "sort-id", - "value": "pe-10.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#pe-10", - "rel": "incorporated-into" - } - ] - } - ] - }, - { - "id": "pe-11", - "class": "SP800-53", - "title": "Emergency Power", - "params": [ - { - "id": "pe-11_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "an orderly shutdown of the information system", - "transition of the information system to long-term alternate power" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "PE-11" - }, - { - "name": "sort-id", - "value": "pe-11" - } - ], - "parts": [ - { - "id": "pe-11_smt", - "name": "statement", - "prose": "The organization provides a short-term uninterruptible power supply to facilitate {{ insert: param, pe-11_prm_1 }} in the event of a primary power source loss." - }, - { - "id": "pe-11_gdn", - "name": "guidance", - "links": [ - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - } - ] - }, - { - "id": "pe-11_obj", - "name": "objective", - "prose": "Determine if the organization provides a short-term uninterruptible power supply to facilitate one or more of the following in the event of a primary power source loss:", - "parts": [ - { - "id": "pe-11_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-11[1]" - } - ], - "prose": "an orderly shutdown of the information system; and/or" - }, - { - "id": "pe-11_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-11[2]" - } - ], - "prose": "transition of the information system to long-term alternate power." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing emergency power\n\nuninterruptible power supply\n\nuninterruptible power supply documentation\n\nuninterruptible power supply test records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for emergency power and/or planning\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing uninterruptible power supply\n\nthe uninterruptable power supply" - } - ] - } - ], - "controls": [ - { - "id": "pe-11.1", - "class": "SP800-53-enhancement", - "title": "Long-term Alternate Power Supply - Minimal Operational Capability", - "props": [ - { - "name": "label", - "value": "PE-11(1)" - }, - { - "name": "sort-id", - "value": "pe-11.01" - } - ], - "parts": [ - { - "id": "pe-11.1_smt", - "name": "statement", - "prose": "The organization provides a long-term alternate power supply for the information system that is capable of maintaining minimally required operational capability in the event of an extended loss of the primary power source." - }, - { - "id": "pe-11.1_gdn", - "name": "guidance", - "prose": "This control enhancement can be satisfied, for example, by the use of a secondary commercial power supply or other external power supply. Long-term alternate power supplies for the information system can be either manually or automatically activated." - }, - { - "id": "pe-11.1_obj", - "name": "objective", - "prose": "Determine if the organization provides a long-term alternate power supply for the information system that is capable of maintaining minimally required operational capability in the event of an extended loss of the primary power source." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing emergency power\n\nalternate power supply\n\nalternate power supply documentation\n\nalternate power supply test records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for emergency power and/or planning\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing alternate power supply\n\nthe alternate power supply" - } - ] - } - ] - }, - { - "id": "pe-11.2", - "class": "SP800-53-enhancement", - "title": "Long-term Alternate Power Supply - Self-contained", - "params": [ - { - "id": "pe-11.2_prm_1", - "select": { - "choice": [ - "minimally required operational capability", - "full operational capability" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "PE-11(2)" - }, - { - "name": "sort-id", - "value": "pe-11.02" - } - ], - "parts": [ - { - "id": "pe-11.2_smt", - "name": "statement", - "prose": "The organization provides a long-term alternate power supply for the information system that is:", - "parts": [ - { - "id": "pe-11.2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Self-contained;" - }, - { - "id": "pe-11.2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Not reliant on external power generation; and" - }, - { - "id": "pe-11.2_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Capable of maintaining {{ insert: param, pe-11.2_prm_1 }} in the event of an extended loss of the primary power source." - } - ] - }, - { - "id": "pe-11.2_gdn", - "name": "guidance", - "prose": "This control enhancement can be satisfied, for example, by the use of one or more generators with sufficient capacity to meet the needs of the organization. Long-term alternate power supplies for organizational information systems are either manually or automatically activated." - }, - { - "id": "pe-11.2_obj", - "name": "objective", - "prose": "Determine if the organization provides a long-term alternate power supply for the information system that is:", - "parts": [ - { - "id": "pe-11.2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-11(2)(a)" - } - ], - "prose": "self-contained;", - "links": [ - { - "href": "#pe-11.2_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "pe-11.2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-11(2)(b)" - } - ], - "prose": "not reliant on external power generation;", - "links": [ - { - "href": "#pe-11.2_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "pe-11.2.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-11(2)(c)" - } - ], - "prose": "capable of maintaining one of the following in the event of an extended loss of the primary power source:", - "parts": [ - { - "id": "pe-11.2.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-11(2)(c)[1]" - } - ], - "prose": "minimally required operational capability; or" - }, - { - "id": "pe-11.2.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-11(2)(c)[2]" - } - ], - "prose": "full operational capability." - } - ], - "links": [ - { - "href": "#pe-11.2_smt.c", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing emergency power\n\nalternate power supply\n\nalternate power supply documentation\n\nalternate power supply test records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for emergency power and/or planning\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing alternate power supply\n\nthe alternate power supply" - } - ] - } - ] - } - ] - }, - { - "id": "pe-12", - "class": "SP800-53", - "title": "Emergency Lighting", - "props": [ - { - "name": "label", - "value": "PE-12" - }, - { - "name": "sort-id", - "value": "pe-12" - } - ], - "parts": [ - { - "id": "pe-12_smt", - "name": "statement", - "prose": "The organization employs and maintains automatic emergency lighting for the information system that activates in the event of a power outage or disruption and that covers emergency exits and evacuation routes within the facility." - }, - { - "id": "pe-12_gdn", - "name": "guidance", - "prose": "This control applies primarily to facilities containing concentrations of information system resources including, for example, data centers, server rooms, and mainframe computer rooms.", - "links": [ - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - } - ] - }, - { - "id": "pe-12_obj", - "name": "objective", - "prose": "Determine if the organization employs and maintains automatic emergency lighting for the information system that:", - "parts": [ - { - "id": "pe-12_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-12[1]" - } - ], - "prose": "activates in the event of a power outage or disruption; and" - }, - { - "id": "pe-12_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-12[2]" - } - ], - "prose": "covers emergency exits and evacuation routes within the facility." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing emergency lighting\n\nemergency lighting documentation\n\nemergency lighting test records\n\nemergency exits and evacuation routes\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for emergency lighting and/or planning\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing emergency lighting capability" - } - ] - } - ], - "controls": [ - { - "id": "pe-12.1", - "class": "SP800-53-enhancement", - "title": "Essential Missions / Business Functions", - "props": [ - { - "name": "label", - "value": "PE-12(1)" - }, - { - "name": "sort-id", - "value": "pe-12.01" - } - ], - "parts": [ - { - "id": "pe-12.1_smt", - "name": "statement", - "prose": "The organization provides emergency lighting for all areas within the facility supporting essential missions and business functions." - }, - { - "id": "pe-12.1_obj", - "name": "objective", - "prose": "Determine if the organization provides emergency lighting for all areas within the facility supporting essential missions and business functions." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing emergency lighting\n\nemergency lighting documentation\n\nemergency lighting test records\n\nemergency exits and evacuation routes\n\nareas/locations within facility supporting essential missions and business functions\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for emergency lighting and/or planning\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing emergency lighting capability" - } - ] - } - ] - } - ] - }, - { - "id": "pe-13", - "class": "SP800-53", - "title": "Fire Protection", - "props": [ - { - "name": "label", - "value": "PE-13" - }, - { - "name": "sort-id", - "value": "pe-13" - } - ], - "parts": [ - { - "id": "pe-13_smt", - "name": "statement", - "prose": "The organization employs and maintains fire suppression and detection devices/systems for the information system that are supported by an independent energy source." - }, - { - "id": "pe-13_gdn", - "name": "guidance", - "prose": "This control applies primarily to facilities containing concentrations of information system resources including, for example, data centers, server rooms, and mainframe computer rooms. Fire suppression and detection devices/systems include, for example, sprinkler systems, handheld fire extinguishers, fixed fire hoses, and smoke detectors." - }, - { - "id": "pe-13_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-13_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-13[1]" - } - ], - "prose": "employs fire suppression and detection devices/systems for the information system that are supported by an independent energy source; and" - }, - { - "id": "pe-13_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-13[2]" - } - ], - "prose": "maintains fire suppression and detection devices/systems for the information system that are supported by an independent energy source." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing fire protection\n\nfire suppression and detection devices/systems\n\nfire suppression and detection devices/systems documentation\n\ntest records of fire suppression and detection devices/systems\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for fire detection and suppression devices/systems\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing fire suppression/detection devices/systems" - } - ] - } - ], - "controls": [ - { - "id": "pe-13.1", - "class": "SP800-53-enhancement", - "title": "Detection Devices / Systems", - "params": [ - { - "id": "pe-13.1_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "pe-13.1_prm_2", - "label": "organization-defined emergency responders" - } - ], - "props": [ - { - "name": "label", - "value": "PE-13(1)" - }, - { - "name": "sort-id", - "value": "pe-13.01" - } - ], - "parts": [ - { - "id": "pe-13.1_smt", - "name": "statement", - "prose": "The organization employs fire detection devices/systems for the information system that activate automatically and notify {{ insert: param, pe-13.1_prm_1 }} and {{ insert: param, pe-13.1_prm_2 }} in the event of a fire." - }, - { - "id": "pe-13.1_gdn", - "name": "guidance", - "prose": "Organizations can identify specific personnel, roles, and emergency responders in the event that individuals on the notification list must have appropriate access authorizations and/or clearances, for example, to obtain access to facilities where classified operations are taking place or where there are information systems containing classified information." - }, - { - "id": "pe-13.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-13.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-13(1)[1]" - } - ], - "prose": "defines personnel or roles to be notified in the event of a fire;" - }, - { - "id": "pe-13.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-13(1)[2]" - } - ], - "prose": "defines emergency responders to be notified in the event of a fire;" - }, - { - "id": "pe-13.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-13(1)[3]" - } - ], - "prose": "employs fire detection devices/systems for the information system that, in the event of a fire,:", - "parts": [ - { - "id": "pe-13.1_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-13(1)[3][a]" - } - ], - "prose": "activate automatically;" - }, - { - "id": "pe-13.1_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-13(1)[3][b]" - } - ], - "prose": "notify organization-defined personnel or roles; and" - }, - { - "id": "pe-13.1_obj.3.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-13(1)[3][c]" - } - ], - "prose": "notify organization-defined emergency responders." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing fire protection\n\nfacility housing the information system\n\nalarm service-level agreements\n\ntest records of fire suppression and detection devices/systems\n\nfire suppression and detection devices/systems documentation\n\nalerts/notifications of fire events\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for fire detection and suppression devices/systems\n\norganizational personnel with responsibilities for notifying appropriate personnel, roles, and emergency responders of fires\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing fire detection devices/systems\n\nactivation of fire detection devices/systems (simulated)\n\nautomated notifications" - } - ] - } - ] - }, - { - "id": "pe-13.2", - "class": "SP800-53-enhancement", - "title": "Suppression Devices / Systems", - "params": [ - { - "id": "pe-13.2_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "pe-13.2_prm_2", - "label": "organization-defined emergency responders" - } - ], - "props": [ - { - "name": "label", - "value": "PE-13(2)" - }, - { - "name": "sort-id", - "value": "pe-13.02" - } - ], - "parts": [ - { - "id": "pe-13.2_smt", - "name": "statement", - "prose": "The organization employs fire suppression devices/systems for the information system that provide automatic notification of any activation to {{ insert: param, pe-13.2_prm_1 }} and {{ insert: param, pe-13.2_prm_2 }}." - }, - { - "id": "pe-13.2_gdn", - "name": "guidance", - "prose": "Organizations can identify specific personnel, roles, and emergency responders in the event that individuals on the notification list must have appropriate access authorizations and/or clearances, for example, to obtain access to facilities where classified operations are taking place or where there are information systems containing classified information." - }, - { - "id": "pe-13.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-13.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-13(2)[1]" - } - ], - "prose": "defines personnel or roles to be provided automatic notification of any activation of fire suppression devices/systems for the information system;" - }, - { - "id": "pe-13.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-13(2)[2]" - } - ], - "prose": "defines emergency responders to be provided automatic notification of any activation of fire suppression devices/systems for the information system;" - }, - { - "id": "pe-13.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-13(2)[3]" - } - ], - "prose": "employs fire suppression devices/systems for the information system that provide automatic notification of any activation to:", - "parts": [ - { - "id": "pe-13.2_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-13(2)[3][a]" - } - ], - "prose": "organization-defined personnel or roles; and" - }, - { - "id": "pe-13.2_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-13(2)[3][b]" - } - ], - "prose": "organization-defined emergency responders." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing fire protection\n\nfire suppression and detection devices/systems documentation\n\nfacility housing the information system\n\nalarm service-level agreements\n\ntest records of fire suppression and detection devices/systems\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for fire detection and suppression devices/systems\n\norganizational personnel with responsibilities for providing automatic notifications of any activation of fire suppression devices/systems to appropriate personnel, roles, and emergency responders\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing fire suppression devices/systems\n\nactivation of fire suppression devices/systems (simulated)\n\nautomated notifications" - } - ] - } - ] - }, - { - "id": "pe-13.3", - "class": "SP800-53-enhancement", - "title": "Automatic Fire Suppression", - "props": [ - { - "name": "label", - "value": "PE-13(3)" - }, - { - "name": "sort-id", - "value": "pe-13.03" - } - ], - "parts": [ - { - "id": "pe-13.3_smt", - "name": "statement", - "prose": "The organization employs an automatic fire suppression capability for the information system when the facility is not staffed on a continuous basis." - }, - { - "id": "pe-13.3_obj", - "name": "objective", - "prose": "Determine if the organization employs an automatic fire suppression capability for the information system when the facility is not staffed on a continuous basis." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing fire protection\n\nfire suppression and detection devices/systems documentation\n\nfacility housing the information system\n\nalarm service-level agreements\n\ntest records of fire suppression and detection devices/systems\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for fire detection and suppression devices/systems\n\norganizational personnel with responsibilities for providing automatic notifications of any activation of fire suppression devices/systems to appropriate personnel, roles, and emergency responders\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing fire suppression devices/systems\n\nactivation of fire suppression devices/systems (simulated)" - } - ] - } - ] - }, - { - "id": "pe-13.4", - "class": "SP800-53-enhancement", - "title": "Inspections", - "params": [ - { - "id": "pe-13.4_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "pe-13.4_prm_2", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "PE-13(4)" - }, - { - "name": "sort-id", - "value": "pe-13.04" - } - ], - "parts": [ - { - "id": "pe-13.4_smt", - "name": "statement", - "prose": "The organization ensures that the facility undergoes {{ insert: param, pe-13.4_prm_1 }} inspections by authorized and qualified inspectors and resolves identified deficiencies within {{ insert: param, pe-13.4_prm_2 }}." - }, - { - "id": "pe-13.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-13.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-13(4)[1]" - } - ], - "prose": "defines the frequency of inspections to be conducted on the facility by authorized and qualified inspectors;" - }, - { - "id": "pe-13.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-13(4)[2]" - } - ], - "prose": "ensures that the facility undergoes inspections by authorized and qualified inspectors with the organization-defined frequency;" - }, - { - "id": "pe-13.4_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-13(4)[3]" - } - ], - "prose": "defines a time period to resolve deficiencies identified when the facility undergoes such inspections; and" - }, - { - "id": "pe-13.4_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-13(4)[4]" - } - ], - "prose": "resolves identified deficiencies within the organization-defined time period." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing fire protection\n\nsecurity plan\n\nfacility housing the information system\n\ninspection plans\n\ninspection results\n\ninspect reports\n\ntest records of fire suppression and detection devices/systems\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for planning, approving, and executing fire inspections\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "pe-14", - "class": "SP800-53", - "title": "Temperature and Humidity Controls", - "params": [ - { - "id": "pe-14_prm_1", - "label": "organization-defined acceptable levels" - }, - { - "id": "pe-14_prm_2", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "PE-14" - }, - { - "name": "sort-id", - "value": "pe-14" - } - ], - "parts": [ - { - "id": "pe-14_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pe-14_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Maintains temperature and humidity levels within the facility where the information system resides at {{ insert: param, pe-14_prm_1 }}; and" - }, - { - "id": "pe-14_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Monitors temperature and humidity levels {{ insert: param, pe-14_prm_2 }}." - } - ] - }, - { - "id": "pe-14_gdn", - "name": "guidance", - "prose": "This control applies primarily to facilities containing concentrations of information system resources, for example, data centers, server rooms, and mainframe computer rooms.", - "links": [ - { - "href": "#at-3", - "rel": "related" - } - ] - }, - { - "id": "pe-14_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-14.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-14(a)" - } - ], - "parts": [ - { - "id": "pe-14.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-14(a)[1]" - } - ], - "prose": "defines acceptable temperature levels to be maintained within the facility where the information system resides;" - }, - { - "id": "pe-14.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-14(a)[2]" - } - ], - "prose": "defines acceptable humidity levels to be maintained within the facility where the information system resides;" - }, - { - "id": "pe-14.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-14(a)[3]" - } - ], - "prose": "maintains temperature levels within the facility where the information system resides at the organization-defined levels;" - }, - { - "id": "pe-14.a_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-14(a)[4]" - } - ], - "prose": "maintains humidity levels within the facility where the information system resides at the organization-defined levels;" - } - ] - }, - { - "id": "pe-14.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-14(b)" - } - ], - "parts": [ - { - "id": "pe-14.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-14(b)[1]" - } - ], - "prose": "defines the frequency to monitor temperature levels;" - }, - { - "id": "pe-14.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-14(b)[2]" - } - ], - "prose": "defines the frequency to monitor humidity levels;" - }, - { - "id": "pe-14.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-14(b)[3]" - } - ], - "prose": "monitors temperature levels with the organization-defined frequency; and" - }, - { - "id": "pe-14.b_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-14(b)[4]" - } - ], - "prose": "monitors humidity levels with the organization-defined frequency." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing temperature and humidity control\n\nsecurity plan\n\ntemperature and humidity controls\n\nfacility housing the information system\n\ntemperature and humidity controls documentation\n\ntemperature and humidity records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for information system environmental controls\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing maintenance and monitoring of temperature and humidity levels" - } - ] - } - ], - "controls": [ - { - "id": "pe-14.1", - "class": "SP800-53-enhancement", - "title": "Automatic Controls", - "props": [ - { - "name": "label", - "value": "PE-14(1)" - }, - { - "name": "sort-id", - "value": "pe-14.01" - } - ], - "parts": [ - { - "id": "pe-14.1_smt", - "name": "statement", - "prose": "The organization employs automatic temperature and humidity controls in the facility to prevent fluctuations potentially harmful to the information system." - }, - { - "id": "pe-14.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-14.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-14(1)[1]" - } - ], - "prose": "employs automatic temperature controls in the facility to prevent fluctuations potentially harmful to the information system; and" - }, - { - "id": "pe-14.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-14(1)[2]" - } - ], - "prose": "employs automatic humidity controls in the facility to prevent fluctuations potentially harmful to the information system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing temperature and humidity controls\n\nfacility housing the information system\n\nautomated mechanisms for temperature and humidity\n\ntemperature and humidity controls\n\ntemperature and humidity documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for information system environmental controls\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing temperature and humidity levels" - } - ] - } - ] - }, - { - "id": "pe-14.2", - "class": "SP800-53-enhancement", - "title": "Monitoring with Alarms / Notifications", - "props": [ - { - "name": "label", - "value": "PE-14(2)" - }, - { - "name": "sort-id", - "value": "pe-14.02" - } - ], - "parts": [ - { - "id": "pe-14.2_smt", - "name": "statement", - "prose": "The organization employs temperature and humidity monitoring that provides an alarm or notification of changes potentially harmful to personnel or equipment." - }, - { - "id": "pe-14.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-14.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-14(2)[1]" - } - ], - "prose": "employs temperature monitoring that provides an alarm of changes potentially harmful to personnel or equipment; and/or" - }, - { - "id": "pe-14.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-14(2)[2]" - } - ], - "prose": "employs temperature monitoring that provides notification of changes potentially harmful to personnel or equipment;" - }, - { - "id": "pe-14.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-14(2)[3]" - } - ], - "prose": "employs humidity monitoring that provides an alarm of changes potentially harmful to personnel or equipment; and/or" - }, - { - "id": "pe-14.2_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-14(2)[4]" - } - ], - "prose": "employs humidity monitoring that provides notification of changes potentially harmful to personnel or equipment." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing temperature and humidity monitoring\n\nfacility housing the information system\n\nlogs or records of temperature and humidity monitoring\n\nrecords of changes to temperature and humidity levels that generate alarms or notifications\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for information system environmental controls\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing temperature and humidity monitoring" - } - ] - } - ] - } - ] - }, - { - "id": "pe-15", - "class": "SP800-53", - "title": "Water Damage Protection", - "props": [ - { - "name": "label", - "value": "PE-15" - }, - { - "name": "sort-id", - "value": "pe-15" - } - ], - "parts": [ - { - "id": "pe-15_smt", - "name": "statement", - "prose": "The organization protects the information system from damage resulting from water leakage by providing master shutoff or isolation valves that are accessible, working properly, and known to key personnel." - }, - { - "id": "pe-15_gdn", - "name": "guidance", - "prose": "This control applies primarily to facilities containing concentrations of information system resources including, for example, data centers, server rooms, and mainframe computer rooms. Isolation valves can be employed in addition to or in lieu of master shutoff valves to shut off water supplies in specific areas of concern, without affecting entire organizations.", - "links": [ - { - "href": "#at-3", - "rel": "related" - } - ] - }, - { - "id": "pe-15_obj", - "name": "objective", - "prose": "Determine if the organization protects the information system from damage resulting from water leakage by providing master shutoff or isolation valves that are:", - "parts": [ - { - "id": "pe-15_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-15[1]" - } - ], - "prose": "accessible;" - }, - { - "id": "pe-15_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-15[2]" - } - ], - "prose": "working properly; and" - }, - { - "id": "pe-15_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-15[3]" - } - ], - "prose": "known to key personnel." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing water damage protection\n\nfacility housing the information system\n\nmaster shutoff valves\n\nlist of key personnel with knowledge of location and activation procedures for master shutoff valves for the plumbing system\n\nmaster shutoff valve documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for information system environmental controls\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Master water-shutoff valves\n\norganizational process for activating master water-shutoff" - } - ] - } - ], - "controls": [ - { - "id": "pe-15.1", - "class": "SP800-53-enhancement", - "title": "Automation Support", - "params": [ - { - "id": "pe-15.1_prm_1", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "PE-15(1)" - }, - { - "name": "sort-id", - "value": "pe-15.01" - } - ], - "parts": [ - { - "id": "pe-15.1_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to detect the presence of water in the vicinity of the information system and alerts {{ insert: param, pe-15.1_prm_1 }}." - }, - { - "id": "pe-15.1_gdn", - "name": "guidance", - "prose": "Automated mechanisms can include, for example, water detection sensors, alarms, and notification systems." - }, - { - "id": "pe-15.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-15.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-15(1)[1]" - } - ], - "prose": "defines personnel or roles to be alerted when the presence of water is detected in the vicinity of the information system;" - }, - { - "id": "pe-15.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-15(1)[2]" - } - ], - "prose": "employs automated mechanisms to detect the presence of water in the vicinity of the information system; and" - }, - { - "id": "pe-15.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-15(1)[3]" - } - ], - "prose": "alerts organization-defined personnel or roles when the presence of water is detected in the vicinity of the information system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing water damage protection\n\nfacility housing the information system\n\nautomated mechanisms for water shutoff valves\n\nautomated mechanisms detecting presence of water in vicinity of information system\n\nalerts/notifications of water detection in information system facility\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for information system environmental controls\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing water detection capability and alerts for the information system" - } - ] - } - ] - } - ] - }, - { - "id": "pe-16", - "class": "SP800-53", - "title": "Delivery and Removal", - "params": [ - { - "id": "pe-16_prm_1", - "label": "organization-defined types of information system components" - } - ], - "props": [ - { - "name": "label", - "value": "PE-16" - }, - { - "name": "sort-id", - "value": "pe-16" - } - ], - "parts": [ - { - "id": "pe-16_smt", - "name": "statement", - "prose": "The organization authorizes, monitors, and controls {{ insert: param, pe-16_prm_1 }} entering and exiting the facility and maintains records of those items." - }, - { - "id": "pe-16_gdn", - "name": "guidance", - "prose": "Effectively enforcing authorizations for entry and exit of information system components may require restricting access to delivery areas and possibly isolating the areas from the information system and media libraries.", - "links": [ - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#ma-2", - "rel": "related" - }, - { - "href": "#ma-3", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - }, - { - "href": "#sa-12", - "rel": "related" - } - ] - }, - { - "id": "pe-16_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-16_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-16[1]" - } - ], - "prose": "defines types of information system components to be authorized, monitored, and controlled as such components are entering and exiting the facility;" - }, - { - "id": "pe-16_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-16[2]" - } - ], - "prose": "authorizes organization-defined information system components entering the facility;" - }, - { - "id": "pe-16_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-16[3]" - } - ], - "prose": "monitors organization-defined information system components entering the facility;" - }, - { - "id": "pe-16_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-16[4]" - } - ], - "prose": "controls organization-defined information system components entering the facility;" - }, - { - "id": "pe-16_obj.5", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-16[5]" - } - ], - "prose": "authorizes organization-defined information system components exiting the facility;" - }, - { - "id": "pe-16_obj.6", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-16[6]" - } - ], - "prose": "monitors organization-defined information system components exiting the facility;" - }, - { - "id": "pe-16_obj.7", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-16[7]" - } - ], - "prose": "controls organization-defined information system components exiting the facility;" - }, - { - "id": "pe-16_obj.8", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-16[8]" - } - ], - "prose": "maintains records of information system components entering the facility; and" - }, - { - "id": "pe-16_obj.9", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-16[9]" - } - ], - "prose": "maintains records of information system components exiting the facility." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing delivery and removal of information system components from the facility\n\nsecurity plan\n\nfacility housing the information system\n\nrecords of items entering and exiting the facility\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for controlling information system components entering and exiting the facility\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational process for authorizing, monitoring, and controlling information system-related items entering and exiting the facility\n\nautomated mechanisms supporting and/or implementing authorizing, monitoring, and controlling information system-related items entering and exiting the facility" - } - ] - } - ] - }, - { - "id": "pe-17", - "class": "SP800-53", - "title": "Alternate Work Site", - "params": [ - { - "id": "pe-17_prm_1", - "label": "organization-defined security controls" - } - ], - "props": [ - { - "name": "label", - "value": "PE-17" - }, - { - "name": "sort-id", - "value": "pe-17" - } - ], - "links": [ - { - "href": "#5309d4d0-46f8-4213-a749-e7584164e5e8", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pe-17_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pe-17_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Employs {{ insert: param, pe-17_prm_1 }} at alternate work sites;" - }, - { - "id": "pe-17_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Assesses as feasible, the effectiveness of security controls at alternate work sites; and" - }, - { - "id": "pe-17_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Provides a means for employees to communicate with information security personnel in case of security incidents or problems." - } - ] - }, - { - "id": "pe-17_gdn", - "name": "guidance", - "prose": "Alternate work sites may include, for example, government facilities or private residences of employees. While commonly distinct from alternative processing sites, alternate work sites may provide readily available alternate locations as part of contingency operations. Organizations may define different sets of security controls for specific alternate work sites or types of sites depending on the work-related activities conducted at those sites. This control supports the contingency planning activities of organizations and the federal telework initiative.", - "links": [ - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - } - ] - }, - { - "id": "pe-17_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-17.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-17(a)" - } - ], - "parts": [ - { - "id": "pe-17.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-17(a)[1]" - } - ], - "prose": "defines security controls to be employed at alternate work sites;" - }, - { - "id": "pe-17.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-17(a)[2]" - } - ], - "prose": "employs organization-defined security controls at alternate work sites;" - } - ] - }, - { - "id": "pe-17.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-17(b)" - } - ], - "prose": "assesses, as feasible, the effectiveness of security controls at alternate work sites; and" - }, - { - "id": "pe-17.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-17(c)" - } - ], - "prose": "provides a means for employees to communicate with information security personnel in case of security incidents or problems." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing alternate work sites for organizational personnel\n\nsecurity plan\n\nlist of security controls required for alternate work sites\n\nassessments of security controls at alternate work sites\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel approving use of alternate work sites\n\norganizational personnel using alternate work sites\n\norganizational personnel assessing controls at alternate work sites\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for security at alternate work sites\n\nautomated mechanisms supporting alternate work sites\n\nsecurity controls employed at alternate work sites\n\nmeans of communications between personnel at alternate work sites and security personnel" - } - ] - } - ] - }, - { - "id": "pe-18", - "class": "SP800-53", - "title": "Location of Information System Components", - "params": [ - { - "id": "pe-18_prm_1", - "label": "organization-defined physical and environmental hazards" - } - ], - "props": [ - { - "name": "label", - "value": "PE-18" - }, - { - "name": "sort-id", - "value": "pe-18" - } - ], - "parts": [ - { - "id": "pe-18_smt", - "name": "statement", - "prose": "The organization positions information system components within the facility to minimize potential damage from {{ insert: param, pe-18_prm_1 }} and to minimize the opportunity for unauthorized access." - }, - { - "id": "pe-18_gdn", - "name": "guidance", - "prose": "Physical and environmental hazards include, for example, flooding, fire, tornados, earthquakes, hurricanes, acts of terrorism, vandalism, electromagnetic pulse, electrical interference, and other forms of incoming electromagnetic radiation. In addition, organizations consider the location of physical entry points where unauthorized individuals, while not being granted access, might nonetheless be in close proximity to information systems and therefore increase the potential for unauthorized access to organizational communications (e.g., through the use of wireless sniffers or microphones).", - "links": [ - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#pe-19", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - } - ] - }, - { - "id": "pe-18_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-18_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-18[1]" - } - ], - "prose": "defines physical hazards that could result in potential damage to information system components within the facility;" - }, - { - "id": "pe-18_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-18[2]" - } - ], - "prose": "defines environmental hazards that could result in potential damage to information system components within the facility;" - }, - { - "id": "pe-18_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-18[3]" - } - ], - "prose": "positions information system components within the facility to minimize potential damage from organization-defined physical and environmental hazards; and" - }, - { - "id": "pe-18_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-18[4]" - } - ], - "prose": "positions information system components within the facility to minimize the opportunity for unauthorized access." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing positioning of information system components\n\ndocumentation providing the location and position of information system components within the facility\n\nlocations housing information system components within the facility\n\nlist of physical and environmental hazards with potential to damage information system components within the facility\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for positioning information system components\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for positioning information system components" - } - ] - } - ], - "controls": [ - { - "id": "pe-18.1", - "class": "SP800-53-enhancement", - "title": "Facility Site", - "props": [ - { - "name": "label", - "value": "PE-18(1)" - }, - { - "name": "sort-id", - "value": "pe-18.01" - } - ], - "parts": [ - { - "id": "pe-18.1_smt", - "name": "statement", - "prose": "The organization plans the location or site of the facility where the information system resides with regard to physical and environmental hazards and for existing facilities, considers the physical and environmental hazards in its risk mitigation strategy." - }, - { - "id": "pe-18.1_gdn", - "name": "guidance", - "links": [ - { - "href": "#pm-8", - "rel": "related" - } - ] - }, - { - "id": "pe-18.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-18.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-18(1)[1]" - } - ], - "prose": "plans the location or site of the facility where the information system resides with regard to physical hazards;" - }, - { - "id": "pe-18.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-18(1)[2]" - } - ], - "prose": "plans the location or site of the facility where the information system resides with regard to environmental hazards;" - }, - { - "id": "pe-18.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-18(1)[3]" - } - ], - "prose": "for existing facilities, considers the physical hazards in its risk mitigation strategy; and" - }, - { - "id": "pe-18.1_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-18(1)[4]" - } - ], - "prose": "for existing facilities, considers the environmental hazards in its risk mitigation strategy." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nphysical site planning documents\n\norganizational assessment of risk, contingency plan\n\nrisk mitigation strategy documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with site selection responsibilities for the facility housing the information system\n\norganizational personnel with risk mitigation responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for site planning" - } - ] - } - ] - } - ] - }, - { - "id": "pe-19", - "class": "SP800-53", - "title": "Information Leakage", - "props": [ - { - "name": "label", - "value": "PE-19" - }, - { - "name": "sort-id", - "value": "pe-19" - } - ], - "links": [ - { - "href": "#e85cdb3f-7f0a-4083-8639-f13f70d3760b", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pe-19_smt", - "name": "statement", - "prose": "The organization protects the information system from information leakage due to electromagnetic signals emanations." - }, - { - "id": "pe-19_gdn", - "name": "guidance", - "prose": "Information leakage is the intentional or unintentional release of information to an untrusted environment from electromagnetic signals emanations. Security categories or classifications of information systems (with respect to confidentiality) and organizational security policies guide the selection of security controls employed to protect systems against information leakage due to electromagnetic signals emanations." - }, - { - "id": "pe-19_obj", - "name": "objective", - "prose": "Determine if the organization protects the information system from information leakage due to electromagnetic signals emanations." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing information leakage due to electromagnetic signals emanations\n\nmechanisms protecting the information system against electronic signals emanation\n\nfacility housing the information system\n\nrecords from electromagnetic signals emanation tests\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for information system environmental controls\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing protection from information leakage due to electromagnetic signals emanations" - } - ] - } - ], - "controls": [ - { - "id": "pe-19.1", - "class": "SP800-53-enhancement", - "title": "National Emissions / Tempest Policies and Procedures", - "props": [ - { - "name": "label", - "value": "PE-19(1)" - }, - { - "name": "sort-id", - "value": "pe-19.01" - } - ], - "parts": [ - { - "id": "pe-19.1_smt", - "name": "statement", - "prose": "The organization ensures that information system components, associated data communications, and networks are protected in accordance with national emissions and TEMPEST policies and procedures based on the security category or classification of the information." - }, - { - "id": "pe-19.1_obj", - "name": "objective", - "prose": "Determine if the organization ensures that the following are protected in accordance with national emissions and TEMPEST policies and procedures based on the security category or classification of the information:", - "parts": [ - { - "id": "pe-19.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-19(1)[1]" - } - ], - "prose": "information system components;" - }, - { - "id": "pe-19.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-19(1)[2]" - } - ], - "prose": "associated data communications; and" - }, - { - "id": "pe-19.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-19(1)[3]" - } - ], - "prose": "networks." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing information leakage that comply with national emissions and TEMPEST policies and procedures\n\ninformation system component design documentation\n\ninformation system configuration settings and associated documentation other relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibilities for information system environmental controls\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system components for compliance with national emissions and TEMPEST policies and procedures" - } - ] - } - ] - } - ] - }, - { - "id": "pe-20", - "class": "SP800-53", - "title": "Asset Monitoring and Tracking", - "params": [ - { - "id": "pe-20_prm_1", - "label": "organization-defined asset location technologies" - }, - { - "id": "pe-20_prm_2", - "label": "organization-defined assets" - }, - { - "id": "pe-20_prm_3", - "label": "organization-defined controlled areas" - } - ], - "props": [ - { - "name": "label", - "value": "PE-20" - }, - { - "name": "sort-id", - "value": "pe-20" - } - ], - "parts": [ - { - "id": "pe-20_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pe-20_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Employs {{ insert: param, pe-20_prm_1 }} to track and monitor the location and movement of {{ insert: param, pe-20_prm_2 }} within {{ insert: param, pe-20_prm_3 }}; and" - }, - { - "id": "pe-20_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Ensures that asset location technologies are employed in accordance with applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance." - } - ] - }, - { - "id": "pe-20_gdn", - "name": "guidance", - "prose": "Asset location technologies can help organizations ensure that critical assets such as vehicles or essential information system components remain in authorized locations. Organizations consult with the Office of the General Counsel and the Senior Agency Official for Privacy (SAOP)/Chief Privacy Officer (CPO) regarding the deployment and use of asset location technologies to address potential privacy concerns.", - "links": [ - { - "href": "#cm-8", - "rel": "related" - } - ] - }, - { - "id": "pe-20_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pe-20.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-20(a)" - } - ], - "parts": [ - { - "id": "pe-20.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-20(a)[1]" - } - ], - "prose": "defines assets whose location and movement are to be tracked and monitored;" - }, - { - "id": "pe-20.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-20(a)[2]" - } - ], - "prose": "defines asset location technologies to be employed to track and monitor the location and movement of organization-defined assets;" - }, - { - "id": "pe-20.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-20(a)[3]" - } - ], - "prose": "defines controlled areas within which to track and monitor organization-defined assets;" - }, - { - "id": "pe-20.a_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-20(a)[4]" - } - ], - "prose": "employs organization-defined asset location technologies to track and monitor the location and movement of organization-defined assets within organization-defined controlled areas; and" - } - ] - }, - { - "id": "pe-20.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PE-20(b)" - } - ], - "prose": "ensures that asset location technologies are employed in accordance with applicable federal laws, Executive Orders, directives, regulations, policies, standards and guidance." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing asset monitoring and tracking\n\nasset location technologies and associated configuration documentation\n\nlist of organizational assets requiring tracking and monitoring\n\nasset monitoring and tracking records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with asset monitoring and tracking responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for tracking and monitoring assets\n\nautomated mechanisms supporting and/or implementing tracking and monitoring of assets" - } - ] - } - ] - } - ] - }, - { - "id": "pl", - "class": "family", - "title": "Planning", - "controls": [ - { - "id": "pl-1", - "class": "SP800-53", - "title": "Security Planning Policy and Procedures", - "params": [ - { - "id": "pl-1_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "pl-1_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "pl-1_prm_3", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "PL-1" - }, - { - "name": "sort-id", - "value": "pl-01" - } - ], - "links": [ - { - "href": "#5c201b63-0768-417b-ac22-3f014e3941b2", - "rel": "reference" - }, - { - "href": "#9c5c9e8c-dc81-4f55-a11c-d71d7487790f", - "rel": "reference" - }, - { - "href": "#9cb3d8fe-2127-48ba-821e-cdd2d7aee921", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pl-1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pl-1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops, documents, and disseminates to {{ insert: param, pl-1_prm_1 }}:", - "parts": [ - { - "id": "pl-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "A security planning policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "pl-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the security planning policy and associated security planning controls; and" - } - ] - }, - { - "id": "pl-1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the current:", - "parts": [ - { - "id": "pl-1_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Security planning policy {{ insert: param, pl-1_prm_2 }}; and" - }, - { - "id": "pl-1_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Security planning procedures {{ insert: param, pl-1_prm_3 }}." - } - ] - } - ] - }, - { - "id": "pl-1_gdn", - "name": "guidance", - "prose": "This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the PL family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures.", - "links": [ - { - "href": "#pm-9", - "rel": "related" - } - ] - }, - { - "id": "pl-1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pl-1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(a)" - } - ], - "parts": [ - { - "id": "pl-1.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(a)(1)" - } - ], - "parts": [ - { - "id": "pl-1.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(a)(1)[1]" - } - ], - "prose": "develops and documents a planning policy that addresses:", - "parts": [ - { - "id": "pl-1.a.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(a)(1)[1][a]" - } - ], - "prose": "purpose;" - }, - { - "id": "pl-1.a.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(a)(1)[1][b]" - } - ], - "prose": "scope;" - }, - { - "id": "pl-1.a.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(a)(1)[1][c]" - } - ], - "prose": "roles;" - }, - { - "id": "pl-1.a.1_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(a)(1)[1][d]" - } - ], - "prose": "responsibilities;" - }, - { - "id": "pl-1.a.1_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(a)(1)[1][e]" - } - ], - "prose": "management commitment;" - }, - { - "id": "pl-1.a.1_obj.1.f", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(a)(1)[1][f]" - } - ], - "prose": "coordination among organizational entities;" - }, - { - "id": "pl-1.a.1_obj.1.g", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(a)(1)[1][g]" - } - ], - "prose": "compliance;" - } - ] - }, - { - "id": "pl-1.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(a)(1)[2]" - } - ], - "prose": "defines personnel or roles to whom the planning policy is to be disseminated;" - }, - { - "id": "pl-1.a.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(a)(1)[3]" - } - ], - "prose": "disseminates the planning policy to organization-defined personnel or roles;" - } - ] - }, - { - "id": "pl-1.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(a)(2)" - } - ], - "parts": [ - { - "id": "pl-1.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(a)(2)[1]" - } - ], - "prose": "develops and documents procedures to facilitate the implementation of the planning policy and associated planning controls;" - }, - { - "id": "pl-1.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(a)(2)[2]" - } - ], - "prose": "defines personnel or roles to whom the procedures are to be disseminated;" - }, - { - "id": "pl-1.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(a)(2)[3]" - } - ], - "prose": "disseminates the procedures to organization-defined personnel or roles;" - } - ] - } - ] - }, - { - "id": "pl-1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(b)" - } - ], - "parts": [ - { - "id": "pl-1.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(b)(1)" - } - ], - "parts": [ - { - "id": "pl-1.b.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(b)(1)[1]" - } - ], - "prose": "defines the frequency to review and update the current planning policy;" - }, - { - "id": "pl-1.b.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(b)(1)[2]" - } - ], - "prose": "reviews and updates the current planning policy with the organization-defined frequency;" - } - ] - }, - { - "id": "pl-1.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(b)(2)" - } - ], - "parts": [ - { - "id": "pl-1.b.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(b)(2)[1]" - } - ], - "prose": "defines the frequency to review and update the current planning procedures; and" - }, - { - "id": "pl-1.b.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-1(b)(2)[2]" - } - ], - "prose": "reviews and updates the current planning procedures with the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Planning policy and procedures\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with planning responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "pl-2", - "class": "SP800-53", - "title": "System Security Plan", - "params": [ - { - "id": "pl-2_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "pl-2_prm_2", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "PL-2" - }, - { - "name": "sort-id", - "value": "pl-02" - } - ], - "links": [ - { - "href": "#9c5c9e8c-dc81-4f55-a11c-d71d7487790f", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pl-2_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pl-2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops a security plan for the information system that:", - "parts": [ - { - "id": "pl-2_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Is consistent with the organization’s enterprise architecture;" - }, - { - "id": "pl-2_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Explicitly defines the authorization boundary for the system;" - }, - { - "id": "pl-2_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Describes the operational context of the information system in terms of missions and business processes;" - }, - { - "id": "pl-2_smt.a.4", - "name": "item", - "props": [ - { - "name": "label", - "value": "4." - } - ], - "prose": "Provides the security categorization of the information system including supporting rationale;" - }, - { - "id": "pl-2_smt.a.5", - "name": "item", - "props": [ - { - "name": "label", - "value": "5." - } - ], - "prose": "Describes the operational environment for the information system and relationships with or connections to other information systems;" - }, - { - "id": "pl-2_smt.a.6", - "name": "item", - "props": [ - { - "name": "label", - "value": "6." - } - ], - "prose": "Provides an overview of the security requirements for the system;" - }, - { - "id": "pl-2_smt.a.7", - "name": "item", - "props": [ - { - "name": "label", - "value": "7." - } - ], - "prose": "Identifies any relevant overlays, if applicable;" - }, - { - "id": "pl-2_smt.a.8", - "name": "item", - "props": [ - { - "name": "label", - "value": "8." - } - ], - "prose": "Describes the security controls in place or planned for meeting those requirements including a rationale for the tailoring decisions; and" - }, - { - "id": "pl-2_smt.a.9", - "name": "item", - "props": [ - { - "name": "label", - "value": "9." - } - ], - "prose": "Is reviewed and approved by the authorizing official or designated representative prior to plan implementation;" - } - ] - }, - { - "id": "pl-2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Distributes copies of the security plan and communicates subsequent changes to the plan to {{ insert: param, pl-2_prm_1 }};" - }, - { - "id": "pl-2_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Reviews the security plan for the information system {{ insert: param, pl-2_prm_2 }};" - }, - { - "id": "pl-2_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Updates the plan to address changes to the information system/environment of operation or problems identified during plan implementation or security control assessments; and" - }, - { - "id": "pl-2_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Protects the security plan from unauthorized disclosure and modification." - } - ] - }, - { - "id": "pl-2_gdn", - "name": "guidance", - "prose": "Security plans relate security requirements to a set of security controls and control enhancements. Security plans also describe, at a high level, how the security controls and control enhancements meet those security requirements, but do not provide detailed, technical descriptions of the specific design or implementation of the controls/enhancements. Security plans contain sufficient information (including the specification of parameter values for assignment and selection statements either explicitly or by reference) to enable a design and implementation that is unambiguously compliant with the intent of the plans and subsequent determinations of risk to organizational operations and assets, individuals, other organizations, and the Nation if the plan is implemented as intended. Organizations can also apply tailoring guidance to the security control baselines in Appendix D and CNSS Instruction 1253 to develop overlays for community-wide use or to address specialized requirements, technologies, or missions/environments of operation (e.g., DoD-tactical, Federal Public Key Infrastructure, or Federal Identity, Credential, and Access Management, space operations). Appendix I provides guidance on developing overlays. Security plans need not be single documents; the plans can be a collection of various documents including documents that already exist. Effective security plans make extensive use of references to policies, procedures, and additional documents (e.g., design and implementation specifications) where more detailed information can be obtained. This reduces the documentation requirements associated with security programs and maintains security-related information in other established management/operational areas related to enterprise architecture, system development life cycle, systems engineering, and acquisition. For example, security plans do not contain detailed contingency plan or incident response plan information but instead provide explicitly or by reference, sufficient information to define what needs to be accomplished by those plans.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ac-14", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-20", - "rel": "related" - }, - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-3", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-9", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#ma-5", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - }, - { - "href": "#pl-7", - "rel": "related" - }, - { - "href": "#pm-1", - "rel": "related" - }, - { - "href": "#pm-7", - "rel": "related" - }, - { - "href": "#pm-8", - "rel": "related" - }, - { - "href": "#pm-9", - "rel": "related" - }, - { - "href": "#pm-11", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-17", - "rel": "related" - } - ] - }, - { - "id": "pl-2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pl-2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(a)" - } - ], - "prose": "develops a security plan for the information system that:", - "parts": [ - { - "id": "pl-2.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(a)(1)" - } - ], - "prose": "is consistent with the organization’s enterprise architecture;" - }, - { - "id": "pl-2.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(a)(2)" - } - ], - "prose": "explicitly defines the authorization boundary for the system;" - }, - { - "id": "pl-2.a.3_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(a)(3)" - } - ], - "prose": "describes the operational context of the information system in terms of missions and business processes;" - }, - { - "id": "pl-2.a.4_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(a)(4)" - } - ], - "prose": "provides the security categorization of the information system including supporting rationale;" - }, - { - "id": "pl-2.a.5_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(a)(5)" - } - ], - "prose": "describes the operational environment for the information system and relationships with or connections to other information systems;" - }, - { - "id": "pl-2.a.6_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(a)(6)" - } - ], - "prose": "provides an overview of the security requirements for the system;" - }, - { - "id": "pl-2.a.7_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(a)(7)" - } - ], - "prose": "identifies any relevant overlays, if applicable;" - }, - { - "id": "pl-2.a.8_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(a)(8)" - } - ], - "prose": "describes the security controls in place or planned for meeting those requirements including a rationale for the tailoring and supplemental decisions;" - }, - { - "id": "pl-2.a.9_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(a)(9)" - } - ], - "prose": "is reviewed and approved by the authorizing official or designated representative prior to plan implementation;" - } - ] - }, - { - "id": "pl-2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(b)" - } - ], - "parts": [ - { - "id": "pl-2.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(b)[1]" - } - ], - "prose": "defines personnel or roles to whom copies of the security plan are to be distributed and subsequent changes to the plan are to be communicated;" - }, - { - "id": "pl-2.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(b)[2]" - } - ], - "prose": "distributes copies of the security plan and communicates subsequent changes to the plan to organization-defined personnel or roles;" - } - ] - }, - { - "id": "pl-2.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(c)" - } - ], - "parts": [ - { - "id": "pl-2.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(c)[1]" - } - ], - "prose": "defines the frequency to review the security plan for the information system;" - }, - { - "id": "pl-2.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(c)[2]" - } - ], - "prose": "reviews the security plan for the information system with the organization-defined frequency;" - } - ] - }, - { - "id": "pl-2.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(d)" - } - ], - "prose": "updates the plan to address:", - "parts": [ - { - "id": "pl-2.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(d)[1]" - } - ], - "prose": "changes to the information system/environment of operation;" - }, - { - "id": "pl-2.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(d)[2]" - } - ], - "prose": "problems identified during plan implementation;" - }, - { - "id": "pl-2.d_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(d)[3]" - } - ], - "prose": "problems identified during security control assessments;" - } - ] - }, - { - "id": "pl-2.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(e)" - } - ], - "prose": "protects the security plan from unauthorized:", - "parts": [ - { - "id": "pl-2.e_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(e)[1]" - } - ], - "prose": "disclosure; and" - }, - { - "id": "pl-2.e_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(e)[2]" - } - ], - "prose": "modification." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security planning policy\n\nprocedures addressing security plan development and implementation\n\nprocedures addressing security plan reviews and updates\n\nenterprise architecture documentation\n\nsecurity plan for the information system\n\nrecords of security plan reviews and updates\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security planning and plan implementation responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for security plan development/review/update/approval\n\nautomated mechanisms supporting the information system security plan" - } - ] - } - ], - "controls": [ - { - "id": "pl-2.1", - "class": "SP800-53-enhancement", - "title": "Concept of Operations", - "props": [ - { - "name": "label", - "value": "PL-2(1)" - }, - { - "name": "sort-id", - "value": "pl-02.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#pl-7", - "rel": "incorporated-into" - } - ] - }, - { - "id": "pl-2.2", - "class": "SP800-53-enhancement", - "title": "Functional Architecture", - "props": [ - { - "name": "label", - "value": "PL-2(2)" - }, - { - "name": "sort-id", - "value": "pl-02.02" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#pl-8", - "rel": "incorporated-into" - } - ] - }, - { - "id": "pl-2.3", - "class": "SP800-53-enhancement", - "title": "Plan / Coordinate with Other Organizational Entities", - "params": [ - { - "id": "pl-2.3_prm_1", - "label": "organization-defined individuals or groups" - } - ], - "props": [ - { - "name": "label", - "value": "PL-2(3)" - }, - { - "name": "sort-id", - "value": "pl-02.03" - } - ], - "parts": [ - { - "id": "pl-2.3_smt", - "name": "statement", - "prose": "The organization plans and coordinates security-related activities affecting the information system with {{ insert: param, pl-2.3_prm_1 }} before conducting such activities in order to reduce the impact on other organizational entities." - }, - { - "id": "pl-2.3_gdn", - "name": "guidance", - "prose": "Security-related activities include, for example, security assessments, audits, hardware and software maintenance, patch management, and contingency plan testing. Advance planning and coordination includes emergency and nonemergency (i.e., planned or nonurgent unplanned) situations. The process defined by organizations to plan and coordinate security-related activities can be included in security plans for information systems or other documents, as appropriate.", - "links": [ - { - "href": "#cp-4", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - } - ] - }, - { - "id": "pl-2.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pl-2.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(3)[1]" - } - ], - "prose": "defines individuals or groups with whom security-related activities affecting the information system are to be planned and coordinated before conducting such activities in order to reduce the impact on other organizational entities; and" - }, - { - "id": "pl-2.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-2(3)[2]" - } - ], - "prose": "plans and coordinates security-related activities affecting the information system with organization-defined individuals or groups before conducting such activities in order to reduce the impact on other organizational entities." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security planning policy\n\naccess control policy\n\ncontingency planning policy\n\nprocedures addressing security-related activity planning for the information system\n\nsecurity plan for the information system\n\ncontingency plan for the information system\n\ninformation system design documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security planning and plan implementation responsibilities\n\norganizational individuals or groups with whom security-related activities are to be planned and coordinated\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "pl-3", - "class": "SP800-53", - "title": "System Security Plan Update", - "props": [ - { - "name": "label", - "value": "PL-3" - }, - { - "name": "sort-id", - "value": "pl-03" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#pl-2", - "rel": "incorporated-into" - } - ] - }, - { - "id": "pl-4", - "class": "SP800-53", - "title": "Rules of Behavior", - "params": [ - { - "id": "pl-4_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "PL-4" - }, - { - "name": "sort-id", - "value": "pl-04" - } - ], - "links": [ - { - "href": "#9c5c9e8c-dc81-4f55-a11c-d71d7487790f", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pl-4_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pl-4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Establishes and makes readily available to individuals requiring access to the information system, the rules that describe their responsibilities and expected behavior with regard to information and information system usage;" - }, - { - "id": "pl-4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Receives a signed acknowledgment from such individuals, indicating that they have read, understand, and agree to abide by the rules of behavior, before authorizing access to information and the information system;" - }, - { - "id": "pl-4_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Reviews and updates the rules of behavior {{ insert: param, pl-4_prm_1 }}; and" - }, - { - "id": "pl-4_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Requires individuals who have signed a previous version of the rules of behavior to read and re-sign when the rules of behavior are revised/updated." - } - ] - }, - { - "id": "pl-4_gdn", - "name": "guidance", - "prose": "This control enhancement applies to organizational users. Organizations consider rules of behavior based on individual user roles and responsibilities, differentiating, for example, between rules that apply to privileged users and rules that apply to general users. Establishing rules of behavior for some types of non-organizational users including, for example, individuals who simply receive data/information from federal information systems, is often not feasible given the large number of such users and the limited nature of their interactions with the systems. Rules of behavior for both organizational and non-organizational users can also be established in AC-8, System Use Notification. PL-4 b. (the signed acknowledgment portion of this control) may be satisfied by the security awareness training and role-based security training programs conducted by organizations if such training includes rules of behavior. Organizations can use electronic signatures for acknowledging rules of behavior.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ac-8", - "rel": "related" - }, - { - "href": "#ac-9", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#ac-20", - "rel": "related" - }, - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#cm-11", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#mp-7", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - } - ] - }, - { - "id": "pl-4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pl-4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-4(a)" - } - ], - "parts": [ - { - "id": "pl-4.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-4(a)[1]" - } - ], - "prose": "establishes, for individuals requiring access to the information system, the rules that describe their responsibilities and expected behavior with regard to information and information system usage;" - }, - { - "id": "pl-4.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-4(a)[2]" - } - ], - "prose": "makes readily available to individuals requiring access to the information system, the rules that describe their responsibilities and expected behavior with regard to information and information system usage;" - } - ] - }, - { - "id": "pl-4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-4(b)" - } - ], - "prose": "receives a signed acknowledgement from such individuals, indicating that they have read, understand, and agree to abide by the rules of behavior, before authorizing access to information and the information system;" - }, - { - "id": "pl-4.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-4(c)" - } - ], - "parts": [ - { - "id": "pl-4.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-4(c)[1]" - } - ], - "prose": "defines the frequency to review and update the rules of behavior;" - }, - { - "id": "pl-4.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-4(c)[2]" - } - ], - "prose": "reviews and updates the rules of behavior with the organization-defined frequency; and" - } - ] - }, - { - "id": "pl-4.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-4(d)" - } - ], - "prose": "requires individuals who have signed a previous version of the rules of behavior to read and resign when the rules of behavior are revised/updated." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security planning policy\n\nprocedures addressing rules of behavior for information system users\n\nrules of behavior\n\nsigned acknowledgements\n\nrecords for rules of behavior reviews and updates\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for establishing, reviewing, and updating rules of behavior\n\norganizational personnel who are authorized users of the information system and have signed and resigned rules of behavior\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for establishing, reviewing, disseminating, and updating rules of behavior\n\nautomated mechanisms supporting and/or implementing the establishment, review, dissemination, and update of rules of behavior" - } - ] - } - ], - "controls": [ - { - "id": "pl-4.1", - "class": "SP800-53-enhancement", - "title": "Social Media and Networking Restrictions", - "props": [ - { - "name": "label", - "value": "PL-4(1)" - }, - { - "name": "sort-id", - "value": "pl-04.01" - } - ], - "parts": [ - { - "id": "pl-4.1_smt", - "name": "statement", - "prose": "The organization includes in the rules of behavior, explicit restrictions on the use of social media/networking sites and posting organizational information on public websites." - }, - { - "id": "pl-4.1_gdn", - "name": "guidance", - "prose": "This control enhancement addresses rules of behavior related to the use of social media/networking sites: (i) when organizational personnel are using such sites for official duties or in the conduct of official business; (ii) when organizational information is involved in social media/networking transactions; and (iii) when personnel are accessing social media/networking sites from organizational information systems. Organizations also address specific rules that prevent unauthorized entities from obtaining and/or inferring non-public organizational information (e.g., system account information, personally identifiable information) from social media/networking sites." - }, - { - "id": "pl-4.1_obj", - "name": "objective", - "prose": "Determine if the organization includes the following in the rules of behavior:", - "parts": [ - { - "id": "pl-4.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-4(1)[1]" - } - ], - "prose": "explicit restrictions on the use of social media/networking sites; and" - }, - { - "id": "pl-4.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-4(1)[2]" - } - ], - "prose": "posting organizational information on public websites." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security planning policy\n\nprocedures addressing rules of behavior for information system users\n\nrules of behavior\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for establishing, reviewing, and updating rules of behavior\n\norganizational personnel who are authorized users of the information system and have signed rules of behavior\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for establishing rules of behavior\n\nautomated mechanisms supporting and/or implementing the establishment of rules of behavior" - } - ] - } - ] - } - ] - }, - { - "id": "pl-5", - "class": "SP800-53", - "title": "Privacy Impact Assessment", - "props": [ - { - "name": "label", - "value": "PL-5" - }, - { - "name": "sort-id", - "value": "pl-05" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-53r4", - "rel": "incorporated-into" - }, - { - "href": "https://doi.org/10.6028/NIST.SP.800-53r4", - "rel": "incorporated-into" - } - ] - }, - { - "id": "pl-6", - "class": "SP800-53", - "title": "Security-related Activity Planning", - "props": [ - { - "name": "label", - "value": "PL-6" - }, - { - "name": "sort-id", - "value": "pl-06" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#pl-2", - "rel": "incorporated-into" - } - ] - }, - { - "id": "pl-7", - "class": "SP800-53", - "title": "Security Concept of Operations", - "params": [ - { - "id": "pl-7_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "PL-7" - }, - { - "name": "sort-id", - "value": "pl-07" - } - ], - "parts": [ - { - "id": "pl-7_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pl-7_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops a security Concept of Operations (CONOPS) for the information system containing at a minimum, how the organization intends to operate the system from the perspective of information security; and" - }, - { - "id": "pl-7_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the CONOPS {{ insert: param, pl-7_prm_1 }}." - } - ] - }, - { - "id": "pl-7_gdn", - "name": "guidance", - "prose": "The security CONOPS may be included in the security plan for the information system or in other system development life cycle-related documents, as appropriate. Changes to the CONOPS are reflected in ongoing updates to the security plan, the information security architecture, and other appropriate organizational documents (e.g., security specifications for procurements/acquisitions, system development life cycle documents, and systems/security engineering documents).", - "links": [ - { - "href": "#pl-2", - "rel": "related" - } - ] - }, - { - "id": "pl-7_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pl-7.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-7(a)" - } - ], - "prose": "develops a security Concept of Operations (CONOPS) for the information system containing at a minimum, how the organization intends to operate the system from the perspective of information security;" - }, - { - "id": "pl-7.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-7(b)" - } - ], - "parts": [ - { - "id": "pl-7.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-7(b)[1]" - } - ], - "prose": "defines the frequency to review and update the security CONOPS; and" - }, - { - "id": "pl-7.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-7(b)[2]" - } - ], - "prose": "reviews and updates the security CONOPS with the organization-defined frequency." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security planning policy\n\nprocedures addressing security CONOPS development\n\nprocedures addressing security CONOPS reviews and updates\n\nsecurity CONOPS for the information system\n\nsecurity plan for the information system\n\nrecords of security CONOPS reviews and updates\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security planning and plan implementation responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for developing, reviewing, and updating the security CONOPS\n\nautomated mechanisms supporting and/or implementing the development, review, and update of the security CONOPS" - } - ] - } - ] - }, - { - "id": "pl-8", - "class": "SP800-53", - "title": "Information Security Architecture", - "params": [ - { - "id": "pl-8_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "PL-8" - }, - { - "name": "sort-id", - "value": "pl-08" - } - ], - "parts": [ - { - "id": "pl-8_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pl-8_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops an information security architecture for the information system that:", - "parts": [ - { - "id": "pl-8_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Describes the overall philosophy, requirements, and approach to be taken with regard to protecting the confidentiality, integrity, and availability of organizational information;" - }, - { - "id": "pl-8_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Describes how the information security architecture is integrated into and supports the enterprise architecture; and" - }, - { - "id": "pl-8_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Describes any information security assumptions about, and dependencies on, external services;" - } - ] - }, - { - "id": "pl-8_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the information security architecture {{ insert: param, pl-8_prm_1 }} to reflect updates in the enterprise architecture; and" - }, - { - "id": "pl-8_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Ensures that planned information security architecture changes are reflected in the security plan, the security Concept of Operations (CONOPS), and organizational procurements/acquisitions." - } - ] - }, - { - "id": "pl-8_gdn", - "name": "guidance", - "prose": "This control addresses actions taken by organizations in the design and development of information systems. The information security architecture at the individual information system level is consistent with and complements the more global, organization-wide information security architecture described in PM-7 that is integral to and developed as part of the enterprise architecture. The information security architecture includes an architectural description, the placement/allocation of security functionality (including security controls), security-related information for external interfaces, information being exchanged across the interfaces, and the protection mechanisms associated with each interface. In addition, the security architecture can include other important security-related information, for example, user roles and access privileges assigned to each role, unique security requirements, the types of information processed, stored, and transmitted by the information system, restoration priorities of information and information system services, and any other specific protection needs. In today’s modern architecture, it is becoming less common for organizations to control all information resources. There are going to be key dependencies on external information services and service providers. Describing such dependencies in the information security architecture is important to developing a comprehensive mission/business protection strategy. Establishing, developing, documenting, and maintaining under configuration control, a baseline configuration for organizational information systems is critical to implementing and maintaining an effective information security architecture. The development of the information security architecture is coordinated with the Senior Agency Official for Privacy (SAOP)/Chief Privacy Officer (CPO) to ensure that security controls needed to support privacy requirements are identified and effectively implemented. PL-8 is primarily directed at organizations (i.e., internally focused) to help ensure that organizations develop an information security architecture for the information system, and that the security architecture is integrated with or tightly coupled to the enterprise architecture through the organization-wide information security architecture. In contrast, SA-17 is primarily directed at external information technology product/system developers and integrators (although SA-17 could be used internally within organizations for in-house system development). SA-17, which is complementary to PL-8, is selected when organizations outsource the development of information systems or information system components to external entities, and there is a need to demonstrate/show consistency with the organization’s enterprise architecture and information security architecture.", - "links": [ - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#pm-7", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-17", - "rel": "related" - }, - { - "href": "https://doi.org/10.6028/NIST.SP.800-53r4", - "rel": "related" - } - ] - }, - { - "id": "pl-8_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pl-8.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-8(a)" - } - ], - "prose": "develops an information security architecture for the information system that describes:", - "parts": [ - { - "id": "pl-8.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-8(a)(1)" - } - ], - "prose": "the overall philosophy, requirements, and approach to be taken with regard to protecting the confidentiality, integrity, and availability of organizational information;" - }, - { - "id": "pl-8.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-8(a)(2)" - } - ], - "prose": "how the information security architecture is integrated into and supports the enterprise architecture;" - }, - { - "id": "pl-8.a.3_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-8(a)(3)" - } - ], - "prose": "any information security assumptions about, and dependencies on, external services;" - } - ] - }, - { - "id": "pl-8.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-8(b)" - } - ], - "parts": [ - { - "id": "pl-8.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-8(b)[1]" - } - ], - "prose": "defines the frequency to review and update the information security architecture;" - }, - { - "id": "pl-8.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-8(b)[2]" - } - ], - "prose": "reviews and updates the information security architecture with the organization-defined frequency to reflect updates in the enterprise architecture;" - } - ] - }, - { - "id": "pl-8.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-8(c)" - } - ], - "prose": "ensures that planned information security architecture changes are reflected in:", - "parts": [ - { - "id": "pl-8.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-8(c)[1]" - } - ], - "prose": "the security plan;" - }, - { - "id": "pl-8.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-8(c)[2]" - } - ], - "prose": "the security Concept of Operations (CONOPS); and" - }, - { - "id": "pl-8.c_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-8(c)[3]" - } - ], - "prose": "the organizational procurements/acquisitions." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security planning policy\n\nprocedures addressing information security architecture development\n\nprocedures addressing information security architecture reviews and updates\n\nenterprise architecture documentation\n\ninformation security architecture documentation\n\nsecurity plan for the information system\n\nsecurity CONOPS for the information system\n\nrecords of information security architecture reviews and updates\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security planning and plan implementation responsibilities\n\norganizational personnel with information security architecture development responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for developing, reviewing, and updating the information security architecture\n\nautomated mechanisms supporting and/or implementing the development, review, and update of the information security architecture" - } - ] - } - ], - "controls": [ - { - "id": "pl-8.1", - "class": "SP800-53-enhancement", - "title": "Defense-in-depth", - "params": [ - { - "id": "pl-8.1_prm_1", - "label": "organization-defined security safeguards" - }, - { - "id": "pl-8.1_prm_2", - "label": "organization-defined locations and architectural layers" - } - ], - "props": [ - { - "name": "label", - "value": "PL-8(1)" - }, - { - "name": "sort-id", - "value": "pl-08.01" - } - ], - "parts": [ - { - "id": "pl-8.1_smt", - "name": "statement", - "prose": "The organization designs its security architecture using a defense-in-depth approach that:", - "parts": [ - { - "id": "pl-8.1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Allocates {{ insert: param, pl-8.1_prm_1 }} to {{ insert: param, pl-8.1_prm_2 }}; and" - }, - { - "id": "pl-8.1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Ensures that the allocated security safeguards operate in a coordinated and mutually reinforcing manner." - } - ] - }, - { - "id": "pl-8.1_gdn", - "name": "guidance", - "prose": "Organizations strategically allocate security safeguards (procedural, technical, or both) in the security architecture so that adversaries have to overcome multiple safeguards to achieve their objective. Requiring adversaries to defeat multiple mechanisms makes it more difficult to successfully attack critical information resources (i.e., increases adversary work factor) and also increases the likelihood of detection. The coordination of allocated safeguards is essential to ensure that an attack that involves one safeguard does not create adverse unintended consequences (e.g., lockout, cascading alarms) by interfering with another safeguard. Placement of security safeguards is a key activity. Greater asset criticality or information value merits additional layering. Thus, an organization may choose to place anti-virus software at organizational boundary layers, email/web servers, notebook computers, and workstations to maximize the number of related safeguards adversaries must penetrate before compromising the information and information systems.", - "links": [ - { - "href": "#sc-29", - "rel": "related" - }, - { - "href": "#sc-36", - "rel": "related" - } - ] - }, - { - "id": "pl-8.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pl-8.1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-8(1)(a)" - } - ], - "parts": [ - { - "id": "pl-8.1.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-8(1)(a)[1]" - } - ], - "prose": "defines security safeguards to be allocated to locations and architectural layers within the design of its security architecture;" - }, - { - "id": "pl-8.1.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-8(1)(a)[2]" - } - ], - "prose": "defines locations and architectural layers of its security architecture in which organization-defined security safeguards are to be allocated;" - }, - { - "id": "pl-8.1.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-8(1)(a)[3]" - } - ], - "prose": "designs its security architecture using a defense-in-depth approach that allocates organization-defined security safeguards to organization-defined locations and architectural layers; and" - } - ], - "links": [ - { - "href": "#pl-8.1_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "pl-8.1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-8(1)(b)" - } - ], - "prose": "designs its security architecture using a defense-in-depth approach that ensures the allocated organization-defined security safeguards operate in a coordinated and mutually reinforcing manner.", - "links": [ - { - "href": "#pl-8.1_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security planning policy\n\nprocedures addressing information security architecture development\n\nenterprise architecture documentation\n\ninformation security architecture documentation\n\nsecurity plan for the information system\n\nsecurity CONOPS for the information system\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security planning and plan implementation responsibilities\n\norganizational personnel with information security architecture development responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for designing the information security architecture\n\nautomated mechanisms supporting and/or implementing the design of the information security architecture" - } - ] - } - ] - }, - { - "id": "pl-8.2", - "class": "SP800-53-enhancement", - "title": "Supplier Diversity", - "params": [ - { - "id": "pl-8.2_prm_1", - "label": "organization-defined security safeguards" - }, - { - "id": "pl-8.2_prm_2", - "label": "organization-defined locations and architectural layers" - } - ], - "props": [ - { - "name": "label", - "value": "PL-8(2)" - }, - { - "name": "sort-id", - "value": "pl-08.02" - } - ], - "parts": [ - { - "id": "pl-8.2_smt", - "name": "statement", - "prose": "The organization requires that {{ insert: param, pl-8.2_prm_1 }} allocated to {{ insert: param, pl-8.2_prm_2 }} are obtained from different suppliers." - }, - { - "id": "pl-8.2_gdn", - "name": "guidance", - "prose": "Different information technology products have different strengths and weaknesses. Providing a broad spectrum of products complements the individual offerings. For example, vendors offering malicious code protection typically update their products at different times, often developing solutions for known viruses, Trojans, or worms according to their priorities and development schedules. By having different products at different locations (e.g., server, boundary, desktop) there is an increased likelihood that at least one will detect the malicious code.", - "links": [ - { - "href": "#sa-12", - "rel": "related" - } - ] - }, - { - "id": "pl-8.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pl-8.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-8(2)[1]" - } - ], - "prose": "defines security safeguards to be allocated to locations and architectural layers within the design of its security architecture;" - }, - { - "id": "pl-8.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-8(2)[2]" - } - ], - "prose": "defines locations and architectural layers of its security architecture in which organization-defined security safeguards are to be allocated; and" - }, - { - "id": "pl-8.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-8(2)[3]" - } - ], - "prose": "requires that organization-defined security safeguards allocated to organization-defined locations and architectural layers are obtained from different suppliers." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security planning policy\n\nprocedures addressing information security architecture development\n\nenterprise architecture documentation\n\ninformation security architecture documentation\n\nsecurity plan for the information system\n\nsecurity CONOPS for the information system\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security planning and plan implementation responsibilities\n\norganizational personnel with information security architecture development responsibilities\n\norganizational personnel with acquisition responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for obtaining information security safeguards from different suppliers" - } - ] - } - ] - } - ] - }, - { - "id": "pl-9", - "class": "SP800-53", - "title": "Central Management", - "params": [ - { - "id": "pl-9_prm_1", - "label": "organization-defined security controls and related processes" - } - ], - "props": [ - { - "name": "label", - "value": "PL-9" - }, - { - "name": "sort-id", - "value": "pl-09" - } - ], - "links": [ - { - "href": "#0a0c26b6-fd44-4274-8b36-93442d49d998", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pl-9_smt", - "name": "statement", - "prose": "The organization centrally manages {{ insert: param, pl-9_prm_1 }}." - }, - { - "id": "pl-9_gdn", - "name": "guidance", - "prose": "Central management refers to the organization-wide management and implementation of selected security controls and related processes. Central management includes planning, implementing, assessing, authorizing, and monitoring the organization-defined, centrally managed security controls and processes. As central management of security controls is generally associated with common controls, such management promotes and facilitates standardization of security control implementations and management and judicious use of organizational resources. Centrally-managed security controls and processes may also meet independence requirements for assessments in support of initial and ongoing authorizations to operate as part of organizational continuous monitoring. As part of the security control selection process, organizations determine which controls may be suitable for central management based on organizational resources and capabilities. Organizations consider that it may not always be possible to centrally manage every aspect of a security control. In such cases, the security control is treated as a hybrid control with the control managed and implemented either centrally or at the information system level. Controls and control enhancements that are candidates for full or partial central management include, but are not limited to: AC-2 (1) (2) (3) (4); AC-17 (1) (2) (3) (9); AC-18 (1) (3) (4) (5); AC-19 (4); AC-22; AC-23; AT-2 (1) (2); AT-3 (1) (2) (3); AT-4; AU-6 (1) (3) (5) (6) (9); AU-7 (1) (2); AU-11, AU-13, AU-16, CA-2 (1) (2) (3); CA-3 (1) (2) (3); CA-7 (1); CA-9; CM-2 (1) (2); CM-3 (1) (4); CM-4; CM-6 (1); CM-7 (4) (5); CM-8 (all); CM-9 (1); CM-10; CM-11; CP-7 (all); CP-8 (all); SC-43; SI-2; SI-3; SI-7; and SI-8." - }, - { - "id": "pl-9_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pl-9_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-9[1]" - } - ], - "prose": "defines security controls and related processes to be centrally managed; and" - }, - { - "id": "pl-9_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PL-9[2]" - } - ], - "prose": "centrally manages organization-defined security controls and related processes." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Security planning policy\n\nprocedures addressing security plan development and implementation\n\nsecurity plan for the information system\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security planning and plan implementation responsibilities\n\norganizational personnel with responsibilities for planning/implementing central management of security controls and related processes\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for central management of security controls and related processes\n\nautomated mechanisms supporting and/or implementing central management of security controls and related processes" - } - ] - } - ] - } - ] - }, - { - "id": "ps", - "class": "family", - "title": "Personnel Security", - "controls": [ - { - "id": "ps-1", - "class": "SP800-53", - "title": "Personnel Security Policy and Procedures", - "params": [ - { - "id": "ps-1_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "ps-1_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "ps-1_prm_3", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "PS-1" - }, - { - "name": "sort-id", - "value": "ps-01" - } - ], - "links": [ - { - "href": "#5c201b63-0768-417b-ac22-3f014e3941b2", - "rel": "reference" - }, - { - "href": "#9cb3d8fe-2127-48ba-821e-cdd2d7aee921", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ps-1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ps-1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops, documents, and disseminates to {{ insert: param, ps-1_prm_1 }}:", - "parts": [ - { - "id": "ps-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "A personnel security policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "ps-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the personnel security policy and associated personnel security controls; and" - } - ] - }, - { - "id": "ps-1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the current:", - "parts": [ - { - "id": "ps-1_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Personnel security policy {{ insert: param, ps-1_prm_2 }}; and" - }, - { - "id": "ps-1_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Personnel security procedures {{ insert: param, ps-1_prm_3 }}." - } - ] - } - ] - }, - { - "id": "ps-1_gdn", - "name": "guidance", - "prose": "This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the PS family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures.", - "links": [ - { - "href": "#pm-9", - "rel": "related" - } - ] - }, - { - "id": "ps-1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ps-1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(a)" - } - ], - "parts": [ - { - "id": "ps-1.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(a)(1)" - } - ], - "parts": [ - { - "id": "ps-1.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(a)(1)[1]" - } - ], - "prose": "develops and documents an personnel security policy that addresses:", - "parts": [ - { - "id": "ps-1.a.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(a)(1)[1][a]" - } - ], - "prose": "purpose;" - }, - { - "id": "ps-1.a.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(a)(1)[1][b]" - } - ], - "prose": "scope;" - }, - { - "id": "ps-1.a.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(a)(1)[1][c]" - } - ], - "prose": "roles;" - }, - { - "id": "ps-1.a.1_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(a)(1)[1][d]" - } - ], - "prose": "responsibilities;" - }, - { - "id": "ps-1.a.1_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(a)(1)[1][e]" - } - ], - "prose": "management commitment;" - }, - { - "id": "ps-1.a.1_obj.1.f", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(a)(1)[1][f]" - } - ], - "prose": "coordination among organizational entities;" - }, - { - "id": "ps-1.a.1_obj.1.g", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(a)(1)[1][g]" - } - ], - "prose": "compliance;" - } - ] - }, - { - "id": "ps-1.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(a)(1)[2]" - } - ], - "prose": "defines personnel or roles to whom the personnel security policy is to be disseminated;" - }, - { - "id": "ps-1.a.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(a)(1)[3]" - } - ], - "prose": "disseminates the personnel security policy to organization-defined personnel or roles;" - } - ] - }, - { - "id": "ps-1.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(a)(2)" - } - ], - "parts": [ - { - "id": "ps-1.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(a)(2)[1]" - } - ], - "prose": "develops and documents procedures to facilitate the implementation of the personnel security policy and associated personnel security controls;" - }, - { - "id": "ps-1.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(a)(2)[2]" - } - ], - "prose": "defines personnel or roles to whom the procedures are to be disseminated;" - }, - { - "id": "ps-1.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(a)(2)[3]" - } - ], - "prose": "disseminates the procedures to organization-defined personnel or roles;" - } - ] - } - ] - }, - { - "id": "ps-1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(b)" - } - ], - "parts": [ - { - "id": "ps-1.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(b)(1)" - } - ], - "parts": [ - { - "id": "ps-1.b.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(b)(1)[1]" - } - ], - "prose": "defines the frequency to review and update the current personnel security policy;" - }, - { - "id": "ps-1.b.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(b)(1)[2]" - } - ], - "prose": "reviews and updates the current personnel security policy with the organization-defined frequency;" - } - ] - }, - { - "id": "ps-1.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(b)(2)" - } - ], - "parts": [ - { - "id": "ps-1.b.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(b)(2)[1]" - } - ], - "prose": "defines the frequency to review and update the current personnel security procedures; and" - }, - { - "id": "ps-1.b.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-1(b)(2)[2]" - } - ], - "prose": "reviews and updates the current personnel security procedures with the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Personnel security policy and procedures\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with access control responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "ps-2", - "class": "SP800-53", - "title": "Position Risk Designation", - "params": [ - { - "id": "ps-2_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "PS-2" - }, - { - "name": "sort-id", - "value": "ps-02" - } - ], - "links": [ - { - "href": "#0c97e60b-325a-4efa-ba2b-90f20ccd5abc", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ps-2_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ps-2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Assigns a risk designation to all organizational positions;" - }, - { - "id": "ps-2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Establishes screening criteria for individuals filling those positions; and" - }, - { - "id": "ps-2_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Reviews and updates position risk designations {{ insert: param, ps-2_prm_1 }}." - } - ] - }, - { - "id": "ps-2_gdn", - "name": "guidance", - "prose": "Position risk designations reflect Office of Personnel Management policy and guidance. Risk designations can guide and inform the types of authorizations individuals receive when accessing organizational information and information systems. Position screening criteria include explicit information security role appointment requirements (e.g., training, security clearances).", - "links": [ - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#ps-3", - "rel": "related" - } - ] - }, - { - "id": "ps-2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ps-2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-2(a)" - } - ], - "prose": "assigns a risk designation to all organizational positions;" - }, - { - "id": "ps-2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-2(b)" - } - ], - "prose": "establishes screening criteria for individuals filling those positions;" - }, - { - "id": "ps-2.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-2(c)" - } - ], - "parts": [ - { - "id": "ps-2.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-2(c)[1]" - } - ], - "prose": "defines the frequency to review and update position risk designations; and" - }, - { - "id": "ps-2.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-2(c)[2]" - } - ], - "prose": "reviews and updates position risk designations with the organization-defined frequency." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Personnel security policy\n\nprocedures addressing position categorization\n\nappropriate codes of federal regulations\n\nlist of risk designations for organizational positions\n\nsecurity plan\n\nrecords of position risk designation reviews and updates\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for assigning, reviewing, and updating position risk designations\n\norganizational processes for establishing screening criteria" - } - ] - } - ] - }, - { - "id": "ps-3", - "class": "SP800-53", - "title": "Personnel Screening", - "params": [ - { - "id": "ps-3_prm_1", - "label": "organization-defined conditions requiring rescreening and, where rescreening is so indicated, the frequency of such rescreening" - } - ], - "props": [ - { - "name": "label", - "value": "PS-3" - }, - { - "name": "sort-id", - "value": "ps-03" - } - ], - "links": [ - { - "href": "#0c97e60b-325a-4efa-ba2b-90f20ccd5abc", - "rel": "reference" - }, - { - "href": "#e85cdb3f-7f0a-4083-8639-f13f70d3760b", - "rel": "reference" - }, - { - "href": "#c80c10b3-1294-4984-a4cc-d1733ca432b9", - "rel": "reference" - }, - { - "href": "#f152844f-b1ef-4836-8729-6277078ebee1", - "rel": "reference" - }, - { - "href": "#ead74ea9-4c9c-446d-9b92-bcbf0ad4b655", - "rel": "reference" - }, - { - "href": "#2a71298a-ee90-490e-80ff-48c967173a47", - "rel": "reference" - }, - { - "href": "#2042d97b-f7f6-4c74-84f8-981867684659", - "rel": "reference" - }, - { - "href": "#6caa237b-531b-43ac-9711-d8f6b97b0377", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ps-3_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ps-3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Screens individuals prior to authorizing access to the information system; and" - }, - { - "id": "ps-3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Rescreens individuals according to {{ insert: param, ps-3_prm_1 }}." - } - ] - }, - { - "id": "ps-3_gdn", - "name": "guidance", - "prose": "Personnel screening and rescreening activities reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, guidance, and specific criteria established for the risk designations of assigned positions. Organizations may define different rescreening conditions and frequencies for personnel accessing information systems based on types of information processed, stored, or transmitted by the systems.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#ps-2", - "rel": "related" - } - ] - }, - { - "id": "ps-3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ps-3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-3(a)" - } - ], - "prose": "screens individuals prior to authorizing access to the information system;" - }, - { - "id": "ps-3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-3(b)" - } - ], - "parts": [ - { - "id": "ps-3.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-3(b)[1]" - } - ], - "prose": "defines conditions requiring re-screening;" - }, - { - "id": "ps-3.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-3(b)[2]" - } - ], - "prose": "defines the frequency of re-screening where it is so indicated; and" - }, - { - "id": "ps-3.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-3(b)[3]" - } - ], - "prose": "re-screens individuals in accordance with organization-defined conditions requiring re-screening and, where re-screening is so indicated, with the organization-defined frequency of such re-screening." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Personnel security policy\n\nprocedures addressing personnel screening\n\nrecords of screened personnel\n\nsecurity plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for personnel screening" - } - ] - } - ], - "controls": [ - { - "id": "ps-3.1", - "class": "SP800-53-enhancement", - "title": "Classified Information", - "props": [ - { - "name": "label", - "value": "PS-3(1)" - }, - { - "name": "sort-id", - "value": "ps-03.01" - } - ], - "parts": [ - { - "id": "ps-3.1_smt", - "name": "statement", - "prose": "The organization ensures that individuals accessing an information system processing, storing, or transmitting classified information are cleared and indoctrinated to the highest classification level of the information to which they have access on the system." - }, - { - "id": "ps-3.1_gdn", - "name": "guidance", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - } - ] - }, - { - "id": "ps-3.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ps-3.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-3(1)[1]" - } - ], - "prose": "ensures that individuals accessing an information system processing, storing, or transmitting classified information are cleared to the highest classification level of the information to which they have access on the system; and" - }, - { - "id": "ps-3.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-3(1)[2]" - } - ], - "prose": "ensures that individuals accessing an information system processing, storing, or transmitting classified information are indoctrinated to the highest classification level of the information to which they have access on the system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Personnel security policy\n\nprocedures addressing personnel screening\n\nrecords of screened personnel\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for clearing and indoctrinating personnel for access to classified information" - } - ] - } - ] - }, - { - "id": "ps-3.2", - "class": "SP800-53-enhancement", - "title": "Formal Indoctrination", - "props": [ - { - "name": "label", - "value": "PS-3(2)" - }, - { - "name": "sort-id", - "value": "ps-03.02" - } - ], - "parts": [ - { - "id": "ps-3.2_smt", - "name": "statement", - "prose": "The organization ensures that individuals accessing an information system processing, storing, or transmitting types of classified information which require formal indoctrination, are formally indoctrinated for all of the relevant types of information to which they have access on the system." - }, - { - "id": "ps-3.2_gdn", - "name": "guidance", - "prose": "Types of classified information requiring formal indoctrination include, for example, Special Access Program (SAP), Restricted Data (RD), and Sensitive Compartment Information (SCI).", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - } - ] - }, - { - "id": "ps-3.2_obj", - "name": "objective", - "prose": "Determine if the organization ensures that individuals accessing an information system processing, storing, or transmitting types of classified information which require formal indoctrination, are formally indoctrinated for all of the relevant types of information to which they have access on the system." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Personnel security policy\n\nprocedures addressing personnel screening\n\nrecords of screened personnel\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for formal indoctrination for all relevant types of information to which personnel have access" - } - ] - } - ] - }, - { - "id": "ps-3.3", - "class": "SP800-53-enhancement", - "title": "Information with Special Protection Measures", - "params": [ - { - "id": "ps-3.3_prm_1", - "label": "organization-defined additional personnel screening criteria" - } - ], - "props": [ - { - "name": "label", - "value": "PS-3(3)" - }, - { - "name": "sort-id", - "value": "ps-03.03" - } - ], - "parts": [ - { - "id": "ps-3.3_smt", - "name": "statement", - "prose": "The organization ensures that individuals accessing an information system processing, storing, or transmitting information requiring special protection:", - "parts": [ - { - "id": "ps-3.3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Have valid access authorizations that are demonstrated by assigned official government duties; and" - }, - { - "id": "ps-3.3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Satisfy {{ insert: param, ps-3.3_prm_1 }}." - } - ] - }, - { - "id": "ps-3.3_gdn", - "name": "guidance", - "prose": "Organizational information requiring special protection includes, for example, Controlled Unclassified Information (CUI) and Sources and Methods Information (SAMI). Personnel security criteria include, for example, position sensitivity background screening requirements." - }, - { - "id": "ps-3.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ps-3.3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-3(3)(a)" - } - ], - "prose": "ensures that individuals accessing an information system processing, storing, or transmitting information requiring special protection have valid access authorizations that are demonstrated by assigned official government duties;", - "links": [ - { - "href": "#ps-3.3_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ps-3.3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-3(3)(b)" - } - ], - "parts": [ - { - "id": "ps-3.3.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-3(3)(b)[1]" - } - ], - "prose": "defines additional personnel screening criteria to be satisfied for individuals accessing an information system processing, storing, or transmitting information requiring special protection; and" - }, - { - "id": "ps-3.3.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-3(3)(b)[2]" - } - ], - "prose": "ensures that individuals accessing an information system processing, storing, or transmitting information requiring special protection satisfy organization-defined additional personnel screening criteria." - } - ], - "links": [ - { - "href": "#ps-3.3_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Personnel security policy\n\naccess control policy, procedures addressing personnel screening\n\nrecords of screened personnel\n\nscreening criteria\n\nrecords of access authorizations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for ensuring valid access authorizations for information requiring special protection\n\norganizational process for additional personnel screening for information requiring special protection" - } - ] - } - ] - } - ] - }, - { - "id": "ps-4", - "class": "SP800-53", - "title": "Personnel Termination", - "params": [ - { - "id": "ps-4_prm_1", - "label": "organization-defined time period" - }, - { - "id": "ps-4_prm_2", - "label": "organization-defined information security topics" - }, - { - "id": "ps-4_prm_3", - "label": "organization-defined personnel or roles" - }, - { - "id": "ps-4_prm_4", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "PS-4" - }, - { - "name": "sort-id", - "value": "ps-04" - } - ], - "parts": [ - { - "id": "ps-4_smt", - "name": "statement", - "prose": "The organization, upon termination of individual employment:", - "parts": [ - { - "id": "ps-4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Disables information system access within {{ insert: param, ps-4_prm_1 }};" - }, - { - "id": "ps-4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Terminates/revokes any authenticators/credentials associated with the individual;" - }, - { - "id": "ps-4_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Conducts exit interviews that include a discussion of {{ insert: param, ps-4_prm_2 }};" - }, - { - "id": "ps-4_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Retrieves all security-related organizational information system-related property;" - }, - { - "id": "ps-4_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Retains access to organizational information and information systems formerly controlled by terminated individual; and" - }, - { - "id": "ps-4_smt.f", - "name": "item", - "props": [ - { - "name": "label", - "value": "f." - } - ], - "prose": "Notifies {{ insert: param, ps-4_prm_3 }} within {{ insert: param, ps-4_prm_4 }}." - } - ] - }, - { - "id": "ps-4_gdn", - "name": "guidance", - "prose": "Information system-related property includes, for example, hardware authentication tokens, system administration technical manuals, keys, identification cards, and building passes. Exit interviews ensure that terminated individuals understand the security constraints imposed by being former employees and that proper accountability is achieved for information system-related property. Security topics of interest at exit interviews can include, for example, reminding terminated individuals of nondisclosure agreements and potential limitations on future employment. Exit interviews may not be possible for some terminated individuals, for example, in cases related to job abandonment, illnesses, and nonavailability of supervisors. Exit interviews are important for individuals with security clearances. Timely execution of termination actions is essential for individuals terminated for cause. In certain situations, organizations consider disabling the information system accounts of individuals that are being terminated prior to the individuals being notified.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#ps-5", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - } - ] - }, - { - "id": "ps-4_obj", - "name": "objective", - "prose": "Determine if the organization, upon termination of individual employment,:", - "parts": [ - { - "id": "ps-4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-4(a)" - } - ], - "parts": [ - { - "id": "ps-4.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-4(a)[1]" - } - ], - "prose": "defines a time period within which to disable information system access;" - }, - { - "id": "ps-4.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-4(a)[2]" - } - ], - "prose": "disables information system access within the organization-defined time period;" - } - ] - }, - { - "id": "ps-4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-4(b)" - } - ], - "prose": "terminates/revokes any authenticators/credentials associated with the individual;" - }, - { - "id": "ps-4.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-4(c)" - } - ], - "parts": [ - { - "id": "ps-4.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-4(c)[1]" - } - ], - "prose": "defines information security topics to be discussed when conducting exit interviews;" - }, - { - "id": "ps-4.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-4(c)[2]" - } - ], - "prose": "conducts exit interviews that include a discussion of organization-defined information security topics;" - } - ] - }, - { - "id": "ps-4.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-4(d)" - } - ], - "prose": "retrieves all security-related organizational information system-related property;" - }, - { - "id": "ps-4.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-4(e)" - } - ], - "prose": "retains access to organizational information and information systems formerly controlled by the terminated individual;" - }, - { - "id": "ps-4.f_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-4(f)" - } - ], - "parts": [ - { - "id": "ps-4.f_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-4(f)[1]" - } - ], - "prose": "defines personnel or roles to be notified of the termination;" - }, - { - "id": "ps-4.f_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-4(f)[2]" - } - ], - "prose": "defines the time period within which to notify organization-defined personnel or roles; and" - }, - { - "id": "ps-4.f_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-4(f)[3]" - } - ], - "prose": "notifies organization-defined personnel or roles within the organization-defined time period." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Personnel security policy\n\nprocedures addressing personnel termination\n\nrecords of personnel termination actions\n\nlist of information system accounts\n\nrecords of terminated or revoked authenticators/credentials\n\nrecords of exit interviews\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for personnel termination\n\nautomated mechanisms supporting and/or implementing personnel termination notifications\n\nautomated mechanisms for disabling information system access/revoking authenticators" - } - ] - } - ], - "controls": [ - { - "id": "ps-4.1", - "class": "SP800-53-enhancement", - "title": "Post-employment Requirements", - "props": [ - { - "name": "label", - "value": "PS-4(1)" - }, - { - "name": "sort-id", - "value": "ps-04.01" - } - ], - "parts": [ - { - "id": "ps-4.1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ps-4.1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Notifies terminated individuals of applicable, legally binding post-employment requirements for the protection of organizational information; and" - }, - { - "id": "ps-4.1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Requires terminated individuals to sign an acknowledgment of post-employment requirements as part of the organizational termination process." - } - ] - }, - { - "id": "ps-4.1_gdn", - "name": "guidance", - "prose": "Organizations consult with the Office of the General Counsel regarding matters of post-employment requirements on terminated individuals." - }, - { - "id": "ps-4.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ps-4.1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-4(1)(a)" - } - ], - "prose": "notifies terminated individuals of applicable, legally binding, post-employment requirements for the protection of organizational information; and", - "links": [ - { - "href": "#ps-4.1_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ps-4.1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-4(1)(b)" - } - ], - "prose": "requires terminated individuals to sign an acknowledgement of post-employment requirements as part of the organizational termination process.", - "links": [ - { - "href": "#ps-4.1_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Personnel security policy\n\nprocedures addressing personnel termination\n\nsigned post-employment acknowledgement forms\n\nlist of applicable, legally binding post-employment requirements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for post-employment requirements" - } - ] - } - ] - }, - { - "id": "ps-4.2", - "class": "SP800-53-enhancement", - "title": "Automated Notification", - "params": [ - { - "id": "ps-4.2_prm_1", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "PS-4(2)" - }, - { - "name": "sort-id", - "value": "ps-04.02" - } - ], - "parts": [ - { - "id": "ps-4.2_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to notify {{ insert: param, ps-4.2_prm_1 }} upon termination of an individual." - }, - { - "id": "ps-4.2_gdn", - "name": "guidance", - "prose": "In organizations with a large number of employees, not all personnel who need to know about termination actions receive the appropriate notifications—or, if such notifications are received, they may not occur in a timely manner. Automated mechanisms can be used to send automatic alerts or notifications to specific organizational personnel or roles (e.g., management personnel, supervisors, personnel security officers, information security officers, systems administrators, or information technology administrators) when individuals are terminated. Such automatic alerts or notifications can be conveyed in a variety of ways, including, for example, telephonically, via electronic mail, via text message, or via websites." - }, - { - "id": "ps-4.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ps-4.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-4(2)[1]" - } - ], - "prose": "defines personnel or roles to be notified upon termination of an individual; and" - }, - { - "id": "ps-4.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-4(2)[2]" - } - ], - "prose": "employs automated mechanisms to notify organization-defined personnel or roles upon termination of an individual." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Personnel security policy\n\nprocedures addressing personnel termination\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nrecords of personnel termination actions\n\nautomated notifications of employee terminations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for personnel termination\n\nautomated mechanisms supporting and/or implementing personnel termination notifications" - } - ] - } - ] - } - ] - }, - { - "id": "ps-5", - "class": "SP800-53", - "title": "Personnel Transfer", - "params": [ - { - "id": "ps-5_prm_1", - "label": "organization-defined transfer or reassignment actions" - }, - { - "id": "ps-5_prm_2", - "label": "organization-defined time period following the formal transfer action" - }, - { - "id": "ps-5_prm_3", - "label": "organization-defined personnel or roles" - }, - { - "id": "ps-5_prm_4", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "PS-5" - }, - { - "name": "sort-id", - "value": "ps-05" - } - ], - "parts": [ - { - "id": "ps-5_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ps-5_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Reviews and confirms ongoing operational need for current logical and physical access authorizations to information systems/facilities when individuals are reassigned or transferred to other positions within the organization;" - }, - { - "id": "ps-5_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Initiates {{ insert: param, ps-5_prm_1 }} within {{ insert: param, ps-5_prm_2 }};" - }, - { - "id": "ps-5_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Modifies access authorization as needed to correspond with any changes in operational need due to reassignment or transfer; and" - }, - { - "id": "ps-5_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Notifies {{ insert: param, ps-5_prm_3 }} within {{ insert: param, ps-5_prm_4 }}." - } - ] - }, - { - "id": "ps-5_gdn", - "name": "guidance", - "prose": "This control applies when reassignments or transfers of individuals are permanent or of such extended durations as to make the actions warranted. Organizations define actions appropriate for the types of reassignments or transfers, whether permanent or extended. Actions that may be required for personnel transfers or reassignments to other positions within organizations include, for example: (i) returning old and issuing new keys, identification cards, and building passes; (ii) closing information system accounts and establishing new accounts; (iii) changing information system access authorizations (i.e., privileges); and (iv) providing for access to official records to which individuals had access at previous work locations and in previous information system accounts.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#ps-4", - "rel": "related" - } - ] - }, - { - "id": "ps-5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ps-5.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-5(a)" - } - ], - "prose": "when individuals are reassigned or transferred to other positions within the organization, reviews and confirms ongoing operational need for current:", - "parts": [ - { - "id": "ps-5.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-5(a)[1]" - } - ], - "prose": "logical access authorizations to information systems;" - }, - { - "id": "ps-5.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-5(a)[2]" - } - ], - "prose": "physical access authorizations to information systems and facilities;" - } - ] - }, - { - "id": "ps-5.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-5(b)" - } - ], - "parts": [ - { - "id": "ps-5.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-5(b)[1]" - } - ], - "prose": "defines transfer or reassignment actions to be initiated following transfer or reassignment;" - }, - { - "id": "ps-5.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-5(b)[2]" - } - ], - "prose": "defines the time period within which transfer or reassignment actions must occur following transfer or reassignment;" - }, - { - "id": "ps-5.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-5(b)[3]" - } - ], - "prose": "initiates organization-defined transfer or reassignment actions within the organization-defined time period following transfer or reassignment;" - } - ] - }, - { - "id": "ps-5.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-5(c)" - } - ], - "prose": "modifies access authorization as needed to correspond with any changes in operational need due to reassignment or transfer;" - }, - { - "id": "ps-5.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-5(d)" - } - ], - "parts": [ - { - "id": "ps-5.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-5(d)[1]" - } - ], - "prose": "defines personnel or roles to be notified when individuals are reassigned or transferred to other positions within the organization;" - }, - { - "id": "ps-5.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-5(d)[2]" - } - ], - "prose": "defines the time period within which to notify organization-defined personnel or roles when individuals are reassigned or transferred to other positions within the organization; and" - }, - { - "id": "ps-5.d_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-5(d)[3]" - } - ], - "prose": "notifies organization-defined personnel or roles within the organization-defined time period when individuals are reassigned or transferred to other positions within the organization." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Personnel security policy\n\nprocedures addressing personnel transfer\n\nsecurity plan\n\nrecords of personnel transfer actions\n\nlist of information system and facility access authorizations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with personnel security responsibilities organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for personnel transfer\n\nautomated mechanisms supporting and/or implementing personnel transfer notifications\n\nautomated mechanisms for disabling information system access/revoking authenticators" - } - ] - } - ] - }, - { - "id": "ps-6", - "class": "SP800-53", - "title": "Access Agreements", - "params": [ - { - "id": "ps-6_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "ps-6_prm_2", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "PS-6" - }, - { - "name": "sort-id", - "value": "ps-06" - } - ], - "parts": [ - { - "id": "ps-6_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ps-6_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops and documents access agreements for organizational information systems;" - }, - { - "id": "ps-6_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the access agreements {{ insert: param, ps-6_prm_1 }}; and" - }, - { - "id": "ps-6_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Ensures that individuals requiring access to organizational information and information systems:", - "parts": [ - { - "id": "ps-6_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Sign appropriate access agreements prior to being granted access; and" - }, - { - "id": "ps-6_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Re-sign access agreements to maintain access to organizational information systems when access agreements have been updated or {{ insert: param, ps-6_prm_2 }}." - } - ] - } - ] - }, - { - "id": "ps-6_gdn", - "name": "guidance", - "prose": "Access agreements include, for example, nondisclosure agreements, acceptable use agreements, rules of behavior, and conflict-of-interest agreements. Signed access agreements include an acknowledgement that individuals have read, understand, and agree to abide by the constraints associated with organizational information systems to which access is authorized. Organizations can use electronic signatures to acknowledge access agreements unless specifically prohibited by organizational policy.", - "links": [ - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#ps-2", - "rel": "related" - }, - { - "href": "#ps-3", - "rel": "related" - }, - { - "href": "#ps-4", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - } - ] - }, - { - "id": "ps-6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ps-6.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-6(a)" - } - ], - "prose": "develops and documents access agreements for organizational information systems;" - }, - { - "id": "ps-6.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-6(b)" - } - ], - "parts": [ - { - "id": "ps-6.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-6(b)[1]" - } - ], - "prose": "defines the frequency to review and update the access agreements;" - }, - { - "id": "ps-6.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-6(b)[2]" - } - ], - "prose": "reviews and updates the access agreements with the organization-defined frequency;" - } - ] - }, - { - "id": "ps-6.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-6(c)" - } - ], - "parts": [ - { - "id": "ps-6.c.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-6(c)(1)" - } - ], - "prose": "ensures that individuals requiring access to organizational information and information systems sign appropriate access agreements prior to being granted access;" - }, - { - "id": "ps-6.c.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-6(c)(2)" - } - ], - "parts": [ - { - "id": "ps-6.c.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-6(c)(2)[1]" - } - ], - "prose": "defines the frequency to re-sign access agreements to maintain access to organizational information systems when access agreements have been updated;" - }, - { - "id": "ps-6.c.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-6(c)(2)[2]" - } - ], - "prose": "ensures that individuals requiring access to organizational information and information systems re-sign access agreements to maintain access to organizational information systems when access agreements have been updated or with the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Personnel security policy\n\nprocedures addressing access agreements for organizational information and information systems\n\nsecurity plan\n\naccess agreements\n\nrecords of access agreement reviews and updates\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel who have signed/resigned access agreements\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for access agreements\n\nautomated mechanisms supporting access agreements" - } - ] - } - ], - "controls": [ - { - "id": "ps-6.1", - "class": "SP800-53-enhancement", - "title": "Information Requiring Special Protection", - "props": [ - { - "name": "label", - "value": "PS-6(1)" - }, - { - "name": "sort-id", - "value": "ps-06.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#ps-3", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ps-6.2", - "class": "SP800-53-enhancement", - "title": "Classified Information Requiring Special Protection", - "props": [ - { - "name": "label", - "value": "PS-6(2)" - }, - { - "name": "sort-id", - "value": "ps-06.02" - } - ], - "parts": [ - { - "id": "ps-6.2_smt", - "name": "statement", - "prose": "The organization ensures that access to classified information requiring special protection is granted only to individuals who:", - "parts": [ - { - "id": "ps-6.2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Have a valid access authorization that is demonstrated by assigned official government duties;" - }, - { - "id": "ps-6.2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Satisfy associated personnel security criteria; and" - }, - { - "id": "ps-6.2_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Have read, understood, and signed a nondisclosure agreement." - } - ] - }, - { - "id": "ps-6.2_gdn", - "name": "guidance", - "prose": "Classified information requiring special protection includes, for example, collateral information, Special Access Program (SAP) information, and Sensitive Compartmented Information (SCI). Personnel security criteria reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance." - }, - { - "id": "ps-6.2_obj", - "name": "objective", - "prose": "Determine if the organization ensures that access to classified information requiring special protection is granted only to individuals who:", - "parts": [ - { - "id": "ps-6.2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-6(2)(a)" - } - ], - "prose": "have a valid access authorization that is demonstrated by assigned official government duties;", - "links": [ - { - "href": "#ps-6.2_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ps-6.2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-6(2)(b)" - } - ], - "prose": "satisfy associated personnel security criteria; and", - "links": [ - { - "href": "#ps-6.2_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "ps-6.2.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-6(2)(c)" - } - ], - "prose": "have read, understood, and signed a nondisclosure agreement.", - "links": [ - { - "href": "#ps-6.2_smt.c", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Personnel security policy\n\nprocedures addressing access agreements for organizational information and information systems\n\naccess agreements\n\naccess authorizations\n\npersonnel security criteria\n\nsigned nondisclosure agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel who have signed nondisclosure agreements\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for access to classified information requiring special protection" - } - ] - } - ] - }, - { - "id": "ps-6.3", - "class": "SP800-53-enhancement", - "title": "Post-employment Requirements", - "props": [ - { - "name": "label", - "value": "PS-6(3)" - }, - { - "name": "sort-id", - "value": "ps-06.03" - } - ], - "parts": [ - { - "id": "ps-6.3_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ps-6.3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Notifies individuals of applicable, legally binding post-employment requirements for protection of organizational information; and" - }, - { - "id": "ps-6.3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Requires individuals to sign an acknowledgment of these requirements, if applicable, as part of granting initial access to covered information." - } - ] - }, - { - "id": "ps-6.3_gdn", - "name": "guidance", - "prose": "Organizations consult with the Office of the General Counsel regarding matters of post-employment requirements on terminated individuals." - }, - { - "id": "ps-6.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ps-6.3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-6(3)(a)" - } - ], - "prose": "notifies individuals of applicable, legally binding post-employment requirements for protection of organizational information; and", - "links": [ - { - "href": "#ps-6.3_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "ps-6.3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-6(3)(b)" - } - ], - "prose": "requires individuals to sign an acknowledgement of these requirements, if applicable, as part of granting initial access to covered information.", - "links": [ - { - "href": "#ps-6.3_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Personnel security policy\n\nprocedures addressing access agreements for organizational information and information systems\n\nsigned post-employment acknowledgement forms\n\naccess agreements\n\nlist of applicable, legally binding post-employment requirements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel who have signed access agreements that include post-employment requirements\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for post-employment requirements\n\nautomated mechanisms supporting notifications and individual acknowledgements of post-employment requirements" - } - ] - } - ] - } - ] - }, - { - "id": "ps-7", - "class": "SP800-53", - "title": "Third-party Personnel Security", - "params": [ - { - "id": "ps-7_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "ps-7_prm_2", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "PS-7" - }, - { - "name": "sort-id", - "value": "ps-07" - } - ], - "links": [ - { - "href": "#0c775bc3-bfc3-42c7-a382-88949f503171", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ps-7_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ps-7_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Establishes personnel security requirements including security roles and responsibilities for third-party providers;" - }, - { - "id": "ps-7_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Requires third-party providers to comply with personnel security policies and procedures established by the organization;" - }, - { - "id": "ps-7_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Documents personnel security requirements;" - }, - { - "id": "ps-7_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Requires third-party providers to notify {{ insert: param, ps-7_prm_1 }} of any personnel transfers or terminations of third-party personnel who possess organizational credentials and/or badges, or who have information system privileges within {{ insert: param, ps-7_prm_2 }}; and" - }, - { - "id": "ps-7_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Monitors provider compliance." - } - ] - }, - { - "id": "ps-7_gdn", - "name": "guidance", - "prose": "Third-party providers include, for example, service bureaus, contractors, and other organizations providing information system development, information technology services, outsourced applications, and network and security management. Organizations explicitly include personnel security requirements in acquisition-related documents. Third-party providers may have personnel working at organizational facilities with credentials, badges, or information system privileges issued by organizations. Notifications of third-party personnel changes ensure appropriate termination of privileges and credentials. Organizations define the transfers and terminations deemed reportable by security-related characteristics that include, for example, functions, roles, and nature of credentials/privileges associated with individuals transferred or terminated.", - "links": [ - { - "href": "#ps-2", - "rel": "related" - }, - { - "href": "#ps-3", - "rel": "related" - }, - { - "href": "#ps-4", - "rel": "related" - }, - { - "href": "#ps-5", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - }, - { - "href": "#sa-21", - "rel": "related" - } - ] - }, - { - "id": "ps-7_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ps-7.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-7(a)" - } - ], - "prose": "establishes personnel security requirements, including security roles and responsibilities, for third-party providers;" - }, - { - "id": "ps-7.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-7(b)" - } - ], - "prose": "requires third-party providers to comply with personnel security policies and procedures established by the organization;" - }, - { - "id": "ps-7.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-7(c)" - } - ], - "prose": "documents personnel security requirements;" - }, - { - "id": "ps-7.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-7(d)" - } - ], - "parts": [ - { - "id": "ps-7.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-7(d)[1]" - } - ], - "prose": "defines personnel or roles to be notified of any personnel transfers or terminations of third-party personnel who possess organizational credentials and/or badges, or who have information system privileges;" - }, - { - "id": "ps-7.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-7(d)[2]" - } - ], - "prose": "defines the time period within which third-party providers are required to notify organization-defined personnel or roles of any personnel transfers or terminations of third-party personnel who possess organizational credentials and/or badges, or who have information system privileges;" - }, - { - "id": "ps-7.d_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-7(d)[3]" - } - ], - "prose": "requires third-party providers to notify organization-defined personnel or roles within the organization-defined time period of any personnel transfers or terminations of third-party personnel who possess organizational credentials and/or badges, or who have information system privileges; and" - } - ] - }, - { - "id": "ps-7.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-7(e)" - } - ], - "prose": "monitors provider compliance." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Personnel security policy\n\nprocedures addressing third-party personnel security\n\nlist of personnel security requirements\n\nacquisition documents\n\nservice-level agreements\n\ncompliance monitoring process\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with personnel security responsibilities\n\nthird-party providers\n\nsystem/network administrators\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing and monitoring third-party personnel security\n\nautomated mechanisms supporting and/or implementing monitoring of provider compliance" - } - ] - } - ] - }, - { - "id": "ps-8", - "class": "SP800-53", - "title": "Personnel Sanctions", - "params": [ - { - "id": "ps-8_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "ps-8_prm_2", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "PS-8" - }, - { - "name": "sort-id", - "value": "ps-08" - } - ], - "parts": [ - { - "id": "ps-8_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ps-8_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Employs a formal sanctions process for individuals failing to comply with established information security policies and procedures; and" - }, - { - "id": "ps-8_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Notifies {{ insert: param, ps-8_prm_1 }} within {{ insert: param, ps-8_prm_2 }} when a formal employee sanctions process is initiated, identifying the individual sanctioned and the reason for the sanction." - } - ] - }, - { - "id": "ps-8_gdn", - "name": "guidance", - "prose": "Organizational sanctions processes reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Sanctions processes are described in access agreements and can be included as part of general personnel policies and procedures for organizations. Organizations consult with the Office of the General Counsel regarding matters of employee sanctions.", - "links": [ - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - } - ] - }, - { - "id": "ps-8_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ps-8.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-8(a)" - } - ], - "prose": "employs a formal sanctions process for individuals failing to comply with established information security policies and procedures;" - }, - { - "id": "ps-8.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-8(b)" - } - ], - "parts": [ - { - "id": "ps-8.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-8(b)[1]" - } - ], - "prose": "defines personnel or roles to be notified when a formal employee sanctions process is initiated;" - }, - { - "id": "ps-8.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-8(b)[2]" - } - ], - "prose": "defines the time period within which organization-defined personnel or roles must be notified when a formal employee sanctions process is initiated; and" - }, - { - "id": "ps-8.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PS-8(b)[3]" - } - ], - "prose": "notifies organization-defined personnel or roles within the organization-defined time period when a formal employee sanctions process is initiated, identifying the individual sanctioned and the reason for the sanction." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Personnel security policy\n\nprocedures addressing personnel sanctions\n\nrules of behavior\n\nrecords of formal sanctions\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing personnel sanctions\n\nautomated mechanisms supporting and/or implementing notifications" - } - ] - } - ] - } - ] - }, - { - "id": "ra", - "class": "family", - "title": "Risk Assessment", - "controls": [ - { - "id": "ra-1", - "class": "SP800-53", - "title": "Risk Assessment Policy and Procedures", - "params": [ - { - "id": "ra-1_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "ra-1_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "ra-1_prm_3", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "RA-1" - }, - { - "name": "sort-id", - "value": "ra-01" - } - ], - "links": [ - { - "href": "#5c201b63-0768-417b-ac22-3f014e3941b2", - "rel": "reference" - }, - { - "href": "#a466121b-f0e2-41f0-a5f9-deb0b5fe6b15", - "rel": "reference" - }, - { - "href": "#9cb3d8fe-2127-48ba-821e-cdd2d7aee921", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ra-1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ra-1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops, documents, and disseminates to {{ insert: param, ra-1_prm_1 }}:", - "parts": [ - { - "id": "ra-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "A risk assessment policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "ra-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the risk assessment policy and associated risk assessment controls; and" - } - ] - }, - { - "id": "ra-1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the current:", - "parts": [ - { - "id": "ra-1_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Risk assessment policy {{ insert: param, ra-1_prm_2 }}; and" - }, - { - "id": "ra-1_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Risk assessment procedures {{ insert: param, ra-1_prm_3 }}." - } - ] - } - ] - }, - { - "id": "ra-1_gdn", - "name": "guidance", - "prose": "This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the RA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures.", - "links": [ - { - "href": "#pm-9", - "rel": "related" - } - ] - }, - { - "id": "ra-1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ra-1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(a)" - } - ], - "parts": [ - { - "id": "ra-1.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(a)(1)" - } - ], - "parts": [ - { - "id": "ra-1.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(a)(1)[1]" - } - ], - "prose": "develops and documents a risk assessment policy that addresses:", - "parts": [ - { - "id": "ra-1.a.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(a)(1)[1][a]" - } - ], - "prose": "purpose;" - }, - { - "id": "ra-1.a.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(a)(1)[1][b]" - } - ], - "prose": "scope;" - }, - { - "id": "ra-1.a.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(a)(1)[1][c]" - } - ], - "prose": "roles;" - }, - { - "id": "ra-1.a.1_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(a)(1)[1][d]" - } - ], - "prose": "responsibilities;" - }, - { - "id": "ra-1.a.1_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(a)(1)[1][e]" - } - ], - "prose": "management commitment;" - }, - { - "id": "ra-1.a.1_obj.1.f", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(a)(1)[1][f]" - } - ], - "prose": "coordination among organizational entities;" - }, - { - "id": "ra-1.a.1_obj.1.g", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(a)(1)[1][g]" - } - ], - "prose": "compliance;" - } - ] - }, - { - "id": "ra-1.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(a)(1)[2]" - } - ], - "prose": "defines personnel or roles to whom the risk assessment policy is to be disseminated;" - }, - { - "id": "ra-1.a.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(a)(1)[3]" - } - ], - "prose": "disseminates the risk assessment policy to organization-defined personnel or roles;" - } - ] - }, - { - "id": "ra-1.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(a)(2)" - } - ], - "parts": [ - { - "id": "ra-1.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(a)(2)[1]" - } - ], - "prose": "develops and documents procedures to facilitate the implementation of the risk assessment policy and associated risk assessment controls;" - }, - { - "id": "ra-1.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(a)(2)[2]" - } - ], - "prose": "defines personnel or roles to whom the procedures are to be disseminated;" - }, - { - "id": "ra-1.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(a)(2)[3]" - } - ], - "prose": "disseminates the procedures to organization-defined personnel or roles;" - } - ] - } - ] - }, - { - "id": "ra-1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(b)" - } - ], - "parts": [ - { - "id": "ra-1.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(b)(1)" - } - ], - "parts": [ - { - "id": "ra-1.b.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(b)(1)[1]" - } - ], - "prose": "defines the frequency to review and update the current risk assessment policy;" - }, - { - "id": "ra-1.b.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(b)(1)[2]" - } - ], - "prose": "reviews and updates the current risk assessment policy with the organization-defined frequency;" - } - ] - }, - { - "id": "ra-1.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(b)(2)" - } - ], - "parts": [ - { - "id": "ra-1.b.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(b)(2)[1]" - } - ], - "prose": "defines the frequency to review and update the current risk assessment procedures; and" - }, - { - "id": "ra-1.b.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-1(b)(2)[2]" - } - ], - "prose": "reviews and updates the current risk assessment procedures with the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "risk assessment policy and procedures\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with risk assessment responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "ra-2", - "class": "SP800-53", - "title": "Security Categorization", - "props": [ - { - "name": "label", - "value": "RA-2" - }, - { - "name": "sort-id", - "value": "ra-02" - } - ], - "links": [ - { - "href": "#e85cdb3f-7f0a-4083-8639-f13f70d3760b", - "rel": "reference" - }, - { - "href": "#a466121b-f0e2-41f0-a5f9-deb0b5fe6b15", - "rel": "reference" - }, - { - "href": "#d480aa6a-7a88-424e-a10c-ad1c7870354b", - "rel": "reference" - }, - { - "href": "#f152844f-b1ef-4836-8729-6277078ebee1", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ra-2_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ra-2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Categorizes information and the information system in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance;" - }, - { - "id": "ra-2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Documents the security categorization results (including supporting rationale) in the security plan for the information system; and" - }, - { - "id": "ra-2_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Ensures that the authorizing official or authorizing official designated representative reviews and approves the security categorization decision." - } - ] - }, - { - "id": "ra-2_gdn", - "name": "guidance", - "prose": "Clearly defined authorization boundaries are a prerequisite for effective security categorization decisions. Security categories describe the potential adverse impacts to organizational operations, organizational assets, and individuals if organizational information and information systems are comprised through a loss of confidentiality, integrity, or availability. Organizations conduct the security categorization process as an organization-wide activity with the involvement of chief information officers, senior information security officers, information system owners, mission/business owners, and information owners/stewards. Organizations also consider the potential adverse impacts to other organizations and, in accordance with the USA PATRIOT Act of 2001 and Homeland Security Presidential Directives, potential national-level adverse impacts. Security categorization processes carried out by organizations facilitate the development of inventories of information assets, and along with CM-8, mappings to specific information system components where information is processed, stored, or transmitted.", - "links": [ - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - } - ] - }, - { - "id": "ra-2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ra-2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-2(a)" - } - ], - "prose": "categorizes information and the information system in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance;" - }, - { - "id": "ra-2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-2(b)" - } - ], - "prose": "documents the security categorization results (including supporting rationale) in the security plan for the information system; and" - }, - { - "id": "ra-2.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-2(c)" - } - ], - "prose": "ensures the authorizing official or authorizing official designated representative reviews and approves the security categorization decision." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Risk assessment policy\n\nsecurity planning policy and procedures\n\nprocedures addressing security categorization of organizational information and information systems\n\nsecurity plan\n\nsecurity categorization documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security categorization and risk assessment responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for security categorization" - } - ] - } - ] - }, - { - "id": "ra-3", - "class": "SP800-53", - "title": "Risk Assessment", - "params": [ - { - "id": "ra-3_prm_1", - "select": { - "choice": [ - "security plan", - "risk assessment report", - " {{ insert: param, ra-3_prm_2 }} " - ] - } - }, - { - "id": "ra-3_prm_2", - "depends-on": "ra-3_prm_1", - "label": "organization-defined document" - }, - { - "id": "ra-3_prm_3", - "label": "organization-defined frequency" - }, - { - "id": "ra-3_prm_4", - "label": "organization-defined personnel or roles" - }, - { - "id": "ra-3_prm_5", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "RA-3" - }, - { - "name": "sort-id", - "value": "ra-03" - } - ], - "links": [ - { - "href": "#ff3bfb02-79b2-411f-8735-98dfe5af2ab0", - "rel": "reference" - }, - { - "href": "#a466121b-f0e2-41f0-a5f9-deb0b5fe6b15", - "rel": "reference" - }, - { - "href": "#d480aa6a-7a88-424e-a10c-ad1c7870354b", - "rel": "reference" - }, - { - "href": "#85280698-0417-489d-b214-12bb935fb939", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ra-3_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ra-3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Conducts an assessment of risk, including the likelihood and magnitude of harm, from the unauthorized access, use, disclosure, disruption, modification, or destruction of the information system and the information it processes, stores, or transmits;" - }, - { - "id": "ra-3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Documents risk assessment results in {{ insert: param, ra-3_prm_1 }};" - }, - { - "id": "ra-3_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Reviews risk assessment results {{ insert: param, ra-3_prm_3 }};" - }, - { - "id": "ra-3_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Disseminates risk assessment results to {{ insert: param, ra-3_prm_4 }}; and" - }, - { - "id": "ra-3_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Updates the risk assessment {{ insert: param, ra-3_prm_5 }} or whenever there are significant changes to the information system or environment of operation (including the identification of new threats and vulnerabilities), or other conditions that may impact the security state of the system." - } - ] - }, - { - "id": "ra-3_gdn", - "name": "guidance", - "prose": "Clearly defined authorization boundaries are a prerequisite for effective risk assessments. Risk assessments take into account threats, vulnerabilities, likelihood, and impact to organizational operations and assets, individuals, other organizations, and the Nation based on the operation and use of information systems. Risk assessments also take into account risk from external parties (e.g., service providers, contractors operating information systems on behalf of the organization, individuals accessing organizational information systems, outsourcing entities). In accordance with OMB policy and related E-authentication initiatives, authentication of public users accessing federal information systems may also be required to protect nonpublic or privacy-related information. As such, organizational assessments of risk also address public access to federal information systems. Risk assessments (either formal or informal) can be conducted at all three tiers in the risk management hierarchy (i.e., organization level, mission/business process level, or information system level) and at any phase in the system development life cycle. Risk assessments can also be conducted at various steps in the Risk Management Framework, including categorization, security control selection, security control implementation, security control assessment, information system authorization, and security control monitoring. RA-3 is noteworthy in that the control must be partially implemented prior to the implementation of other controls in order to complete the first two steps in the Risk Management Framework. Risk assessments can play an important role in security control selection processes, particularly during the application of tailoring guidance, which includes security control supplementation.", - "links": [ - { - "href": "#ra-2", - "rel": "related" - }, - { - "href": "#pm-9", - "rel": "related" - } - ] - }, - { - "id": "ra-3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ra-3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(a)" - } - ], - "prose": "conducts an assessment of risk, including the likelihood and magnitude of harm, from the unauthorized access, use, disclosure, disruption, modification, or destruction of:", - "parts": [ - { - "id": "ra-3.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(a)[1]" - } - ], - "prose": "the information system;" - }, - { - "id": "ra-3.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(a)[2]" - } - ], - "prose": "the information the system processes, stores, or transmits;" - } - ] - }, - { - "id": "ra-3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(b)" - } - ], - "parts": [ - { - "id": "ra-3.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(b)[1]" - } - ], - "prose": "defines a document in which risk assessment results are to be documented (if not documented in the security plan or risk assessment report);" - }, - { - "id": "ra-3.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(b)[2]" - } - ], - "prose": "documents risk assessment results in one of the following:", - "parts": [ - { - "id": "ra-3.b_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(b)[2][a]" - } - ], - "prose": "the security plan;" - }, - { - "id": "ra-3.b_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(b)[2][b]" - } - ], - "prose": "the risk assessment report; or" - }, - { - "id": "ra-3.b_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(b)[2][c]" - } - ], - "prose": "the organization-defined document;" - } - ] - } - ] - }, - { - "id": "ra-3.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(c)" - } - ], - "parts": [ - { - "id": "ra-3.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(c)[1]" - } - ], - "prose": "defines the frequency to review risk assessment results;" - }, - { - "id": "ra-3.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(c)[2]" - } - ], - "prose": "reviews risk assessment results with the organization-defined frequency;" - } - ] - }, - { - "id": "ra-3.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(d)" - } - ], - "parts": [ - { - "id": "ra-3.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(d)[1]" - } - ], - "prose": "defines personnel or roles to whom risk assessment results are to be disseminated;" - }, - { - "id": "ra-3.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(d)[2]" - } - ], - "prose": "disseminates risk assessment results to organization-defined personnel or roles;" - } - ] - }, - { - "id": "ra-3.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(e)" - } - ], - "parts": [ - { - "id": "ra-3.e_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(e)[1]" - } - ], - "prose": "defines the frequency to update the risk assessment;" - }, - { - "id": "ra-3.e_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(e)[2]" - } - ], - "prose": "updates the risk assessment:", - "parts": [ - { - "id": "ra-3.e_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(e)[2][a]" - } - ], - "prose": "with the organization-defined frequency;" - }, - { - "id": "ra-3.e_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(e)[2][b]" - } - ], - "prose": "whenever there are significant changes to the information system or environment of operation (including the identification of new threats and vulnerabilities); and" - }, - { - "id": "ra-3.e_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-3(e)[2][c]" - } - ], - "prose": "whenever there are other conditions that may impact the security state of the system." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Risk assessment policy\n\nsecurity planning policy and procedures\n\nprocedures addressing organizational assessments of risk\n\nsecurity plan\n\nrisk assessment\n\nrisk assessment results\n\nrisk assessment reviews\n\nrisk assessment updates\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with risk assessment responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for risk assessment\n\nautomated mechanisms supporting and/or for conducting, documenting, reviewing, disseminating, and updating the risk assessment" - } - ] - } - ] - }, - { - "id": "ra-4", - "class": "SP800-53", - "title": "Risk Assessment Update", - "props": [ - { - "name": "label", - "value": "RA-4" - }, - { - "name": "sort-id", - "value": "ra-04" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#ra-3", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ra-5", - "class": "SP800-53", - "title": "Vulnerability Scanning", - "params": [ - { - "id": "ra-5_prm_1", - "label": "organization-defined frequency and/or randomly in accordance with organization-defined process" - }, - { - "id": "ra-5_prm_2", - "label": "organization-defined response times" - }, - { - "id": "ra-5_prm_3", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "RA-5" - }, - { - "name": "sort-id", - "value": "ra-05" - } - ], - "links": [ - { - "href": "#bdd14f6c-41ab-4277-8d74-a0ce75a0eb1d", - "rel": "reference" - }, - { - "href": "#84a37532-6db6-477b-9ea8-f9085ebca0fc", - "rel": "reference" - }, - { - "href": "#c4691b88-57d1-463b-9053-2d0087913f31", - "rel": "reference" - }, - { - "href": "#15522e92-9192-463d-9646-6a01982db8ca", - "rel": "reference" - }, - { - "href": "#275cc052-0f7f-423c-bdb6-ed503dc36228", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ra-5_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "ra-5_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Scans for vulnerabilities in the information system and hosted applications {{ insert: param, ra-5_prm_1 }} and when new vulnerabilities potentially affecting the system/applications are identified and reported;" - }, - { - "id": "ra-5_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Employs vulnerability scanning tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for:", - "parts": [ - { - "id": "ra-5_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Enumerating platforms, software flaws, and improper configurations;" - }, - { - "id": "ra-5_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Formatting checklists and test procedures; and" - }, - { - "id": "ra-5_smt.b.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Measuring vulnerability impact;" - } - ] - }, - { - "id": "ra-5_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Analyzes vulnerability scan reports and results from security control assessments;" - }, - { - "id": "ra-5_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Remediates legitimate vulnerabilities {{ insert: param, ra-5_prm_2 }} in accordance with an organizational assessment of risk; and" - }, - { - "id": "ra-5_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Shares information obtained from the vulnerability scanning process and security control assessments with {{ insert: param, ra-5_prm_3 }} to help eliminate similar vulnerabilities in other information systems (i.e., systemic weaknesses or deficiencies)." - } - ] - }, - { - "id": "ra-5_gdn", - "name": "guidance", - "prose": "Security categorization of information systems guides the frequency and comprehensiveness of vulnerability scans. Organizations determine the required vulnerability scanning for all information system components, ensuring that potential sources of vulnerabilities such as networked printers, scanners, and copiers are not overlooked. Vulnerability analyses for custom software applications may require additional approaches such as static analysis, dynamic analysis, binary analysis, or a hybrid of the three approaches. Organizations can employ these analysis approaches in a variety of tools (e.g., web-based application scanners, static analysis tools, binary analyzers) and in source code reviews. Vulnerability scanning includes, for example: (i) scanning for patch levels; (ii) scanning for functions, ports, protocols, and services that should not be accessible to users or devices; and (iii) scanning for improperly configured or incorrectly operating information flow control mechanisms. Organizations consider using tools that express vulnerabilities in the Common Vulnerabilities and Exposures (CVE) naming convention and that use the Open Vulnerability Assessment Language (OVAL) to determine/test for the presence of vulnerabilities. Suggested sources for vulnerability information include the Common Weakness Enumeration (CWE) listing and the National Vulnerability Database (NVD). In addition, security control assessments such as red team exercises provide other sources of potential vulnerabilities for which to scan. Organizations also consider using tools that express vulnerability impact by the Common Vulnerability Scoring System (CVSS).", - "links": [ - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#ra-2", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#sa-11", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - } - ] - }, - { - "id": "ra-5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ra-5.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(a)" - } - ], - "parts": [ - { - "id": "ra-5.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(a)[1]" - } - ], - "parts": [ - { - "id": "ra-5.a_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(a)[1][a]" - } - ], - "prose": "defines the frequency for conducting vulnerability scans on the information system and hosted applications; and/or" - }, - { - "id": "ra-5.a_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(a)[1][b]" - } - ], - "prose": "defines the process for conducting random vulnerability scans on the information system and hosted applications;" - } - ] - }, - { - "id": "ra-5.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(a)[2]" - } - ], - "prose": "in accordance with the organization-defined frequency and/or organization-defined process for conducting random scans, scans for vulnerabilities in:", - "parts": [ - { - "id": "ra-5.a_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(a)[2][a]" - } - ], - "prose": "the information system;" - }, - { - "id": "ra-5.a_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(a)[2][b]" - } - ], - "prose": "hosted applications;" - } - ] - }, - { - "id": "ra-5.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(a)[3]" - } - ], - "prose": "when new vulnerabilities potentially affecting the system/applications are identified and reported, scans for vulnerabilities in:", - "parts": [ - { - "id": "ra-5.a_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(a)[3][a]" - } - ], - "prose": "the information system;" - }, - { - "id": "ra-5.a_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(a)[3][b]" - } - ], - "prose": "hosted applications;" - } - ] - } - ] - }, - { - "id": "ra-5.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(b)" - } - ], - "prose": "employs vulnerability scanning tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for:", - "parts": [ - { - "id": "ra-5.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(b)(1)" - } - ], - "parts": [ - { - "id": "ra-5.b.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(b)(1)[1]" - } - ], - "prose": "enumerating platforms;" - }, - { - "id": "ra-5.b.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(b)(1)[2]" - } - ], - "prose": "enumerating software flaws;" - }, - { - "id": "ra-5.b.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(b)(1)[3]" - } - ], - "prose": "enumerating improper configurations;" - } - ] - }, - { - "id": "ra-5.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(b)(2)" - } - ], - "parts": [ - { - "id": "ra-5.b.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(b)(2)[1]" - } - ], - "prose": "formatting checklists;" - }, - { - "id": "ra-5.b.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(b)(2)[2]" - } - ], - "prose": "formatting test procedures;" - } - ] - }, - { - "id": "ra-5.b.3_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(b)(3)" - } - ], - "prose": "measuring vulnerability impact;" - } - ] - }, - { - "id": "ra-5.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(c)" - } - ], - "parts": [ - { - "id": "ra-5.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(c)[1]" - } - ], - "prose": "analyzes vulnerability scan reports;" - }, - { - "id": "ra-5.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(c)[2]" - } - ], - "prose": "analyzes results from security control assessments;" - } - ] - }, - { - "id": "ra-5.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(d)" - } - ], - "parts": [ - { - "id": "ra-5.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(d)[1]" - } - ], - "prose": "defines response times to remediate legitimate vulnerabilities in accordance with an organizational assessment of risk;" - }, - { - "id": "ra-5.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(d)[2]" - } - ], - "prose": "remediates legitimate vulnerabilities within the organization-defined response times in accordance with an organizational assessment of risk;" - } - ] - }, - { - "id": "ra-5.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(e)" - } - ], - "parts": [ - { - "id": "ra-5.e_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(e)[1]" - } - ], - "prose": "defines personnel or roles with whom information obtained from the vulnerability scanning process and security control assessments is to be shared;" - }, - { - "id": "ra-5.e_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(e)[2]" - } - ], - "prose": "shares information obtained from the vulnerability scanning process with organization-defined personnel or roles to help eliminate similar vulnerabilities in other information systems (i.e., systemic weaknesses or deficiencies); and" - }, - { - "id": "ra-5.e_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(e)[3]" - } - ], - "prose": "shares information obtained from security control assessments with organization-defined personnel or roles to help eliminate similar vulnerabilities in other information systems (i.e., systemic weaknesses or deficiencies)." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Risk assessment policy\n\nprocedures addressing vulnerability scanning\n\nrisk assessment\n\nsecurity plan\n\nsecurity assessment report\n\nvulnerability scanning tools and associated configuration documentation\n\nvulnerability scanning results\n\npatch and vulnerability management records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with risk assessment, security control assessment and vulnerability scanning responsibilities\n\norganizational personnel with vulnerability scan analysis responsibilities\n\norganizational personnel with vulnerability remediation responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for vulnerability scanning, analysis, remediation, and information sharing\n\nautomated mechanisms supporting and/or implementing vulnerability scanning, analysis, remediation, and information sharing" - } - ] - } - ], - "controls": [ - { - "id": "ra-5.1", - "class": "SP800-53-enhancement", - "title": "Update Tool Capability", - "props": [ - { - "name": "label", - "value": "RA-5(1)" - }, - { - "name": "sort-id", - "value": "ra-05.01" - } - ], - "parts": [ - { - "id": "ra-5.1_smt", - "name": "statement", - "prose": "The organization employs vulnerability scanning tools that include the capability to readily update the information system vulnerabilities to be scanned." - }, - { - "id": "ra-5.1_gdn", - "name": "guidance", - "prose": "The vulnerabilities to be scanned need to be readily updated as new vulnerabilities are discovered, announced, and scanning methods developed. This updating process helps to ensure that potential vulnerabilities in the information system are identified and addressed as quickly as possible.", - "links": [ - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "ra-5.1_obj", - "name": "objective", - "prose": "Determine if the organization employs vulnerability scanning tools that include the capability to readily update the information system vulnerabilities to be scanned." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Procedures addressing vulnerability scanning\n\nsecurity plan\n\nsecurity assessment report\n\nvulnerability scanning tools and associated configuration documentation\n\nvulnerability scanning results\n\npatch and vulnerability management records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with vulnerability scanning responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for vulnerability scanning\n\nautomated mechanisms/tools supporting and/or implementing vulnerability scanning" - } - ] - } - ] - }, - { - "id": "ra-5.2", - "class": "SP800-53-enhancement", - "title": "Update by Frequency / Prior to New Scan / When Identified", - "params": [ - { - "id": "ra-5.2_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - " {{ insert: param, ra-5.2_prm_2 }} ", - "prior to a new scan", - "when new vulnerabilities are identified and reported" - ] - } - }, - { - "id": "ra-5.2_prm_2", - "depends-on": "ra-5.2_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "RA-5(2)" - }, - { - "name": "sort-id", - "value": "ra-05.02" - } - ], - "parts": [ - { - "id": "ra-5.2_smt", - "name": "statement", - "prose": "The organization updates the information system vulnerabilities scanned {{ insert: param, ra-5.2_prm_1 }}." - }, - { - "id": "ra-5.2_gdn", - "name": "guidance", - "links": [ - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-5", - "rel": "related" - } - ] - }, - { - "id": "ra-5.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ra-5.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(2)[1]" - } - ], - "prose": "defines the frequency to update the information system vulnerabilities scanned;" - }, - { - "id": "ra-5.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(2)[2]" - } - ], - "prose": "updates the information system vulnerabilities scanned one or more of the following:", - "parts": [ - { - "id": "ra-5.2_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(2)[2][a]" - } - ], - "prose": "with the organization-defined frequency;" - }, - { - "id": "ra-5.2_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(2)[2][b]" - } - ], - "prose": "prior to a new scan; and/or" - }, - { - "id": "ra-5.2_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(2)[2][c]" - } - ], - "prose": "when new vulnerabilities are identified and reported." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Procedures addressing vulnerability scanning\n\nsecurity plan\n\nsecurity assessment report\n\nvulnerability scanning tools and associated configuration documentation\n\nvulnerability scanning results\n\npatch and vulnerability management records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with vulnerability scanning responsibilities\n\norganizational personnel with vulnerability scan analysis responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for vulnerability scanning\n\nautomated mechanisms/tools supporting and/or implementing vulnerability scanning" - } - ] - } - ] - }, - { - "id": "ra-5.3", - "class": "SP800-53-enhancement", - "title": "Breadth / Depth of Coverage", - "props": [ - { - "name": "label", - "value": "RA-5(3)" - }, - { - "name": "sort-id", - "value": "ra-05.03" - } - ], - "parts": [ - { - "id": "ra-5.3_smt", - "name": "statement", - "prose": "The organization employs vulnerability scanning procedures that can identify the breadth and depth of coverage (i.e., information system components scanned and vulnerabilities checked)." - }, - { - "id": "ra-5.3_obj", - "name": "objective", - "prose": "Determine if the organization employs vulnerability scanning procedures that can identify:", - "parts": [ - { - "id": "ra-5.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(3)[1]" - } - ], - "prose": "the breadth of coverage (i.e., information system components scanned); and" - }, - { - "id": "ra-5.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(3)[2]" - } - ], - "prose": "the depth of coverage (i.e., vulnerabilities checked)." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Procedures addressing vulnerability scanning\n\nsecurity plan\n\nsecurity assessment report\n\nvulnerability scanning tools and associated configuration documentation\n\nvulnerability scanning results\n\npatch and vulnerability management records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with vulnerability scanning responsibilities\n\norganizational personnel with vulnerability scan analysis responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for vulnerability scanning\n\nautomated mechanisms/tools supporting and/or implementing vulnerability scanning" - } - ] - } - ] - }, - { - "id": "ra-5.4", - "class": "SP800-53-enhancement", - "title": "Discoverable Information", - "params": [ - { - "id": "ra-5.4_prm_1", - "label": "organization-defined corrective actions" - } - ], - "props": [ - { - "name": "label", - "value": "RA-5(4)" - }, - { - "name": "sort-id", - "value": "ra-05.04" - } - ], - "parts": [ - { - "id": "ra-5.4_smt", - "name": "statement", - "prose": "The organization determines what information about the information system is discoverable by adversaries and subsequently takes {{ insert: param, ra-5.4_prm_1 }}." - }, - { - "id": "ra-5.4_gdn", - "name": "guidance", - "prose": "Discoverable information includes information that adversaries could obtain without directly compromising or breaching the information system, for example, by collecting information the system is exposing or by conducting extensive searches of the web. Corrective actions can include, for example, notifying appropriate organizational personnel, removing designated information, or changing the information system to make designated information less relevant or attractive to adversaries.", - "links": [ - { - "href": "#au-13", - "rel": "related" - } - ] - }, - { - "id": "ra-5.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ra-5.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(4)[1]" - } - ], - "prose": "defines corrective actions to be taken if information about the information system is discoverable by adversaries;" - }, - { - "id": "ra-5.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(4)[2]" - } - ], - "prose": "determines what information about the information system is discoverable by adversaries; and" - }, - { - "id": "ra-5.4_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(4)[3]" - } - ], - "prose": "subsequently takes organization-defined corrective actions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Procedures addressing vulnerability scanning\n\nsecurity assessment report\n\npenetration test results\n\nvulnerability scanning results\n\nrisk assessment report\n\nrecords of corrective actions taken\n\nincident response records\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with vulnerability scanning and/or penetration testing responsibilities\n\norganizational personnel with vulnerability scan analysis responsibilities\n\norganizational personnel responsible for risk response\n\norganizational personnel responsible for incident management and response\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for vulnerability scanning\n\norganizational processes for risk response\n\norganizational processes for incident management and response\n\nautomated mechanisms/tools supporting and/or implementing vulnerability scanning\n\nautomated mechanisms supporting and/or implementing risk response\n\nautomated mechanisms supporting and/or implementing incident management and response" - } - ] - } - ] - }, - { - "id": "ra-5.5", - "class": "SP800-53-enhancement", - "title": "Privileged Access", - "params": [ - { - "id": "ra-5.5_prm_1", - "label": "organization-identified information system components" - }, - { - "id": "ra-5.5_prm_2", - "label": "organization-defined vulnerability scanning activities" - } - ], - "props": [ - { - "name": "label", - "value": "RA-5(5)" - }, - { - "name": "sort-id", - "value": "ra-05.05" - } - ], - "parts": [ - { - "id": "ra-5.5_smt", - "name": "statement", - "prose": "The information system implements privileged access authorization to {{ insert: param, ra-5.5_prm_1 }} for selected {{ insert: param, ra-5.5_prm_2 }}." - }, - { - "id": "ra-5.5_gdn", - "name": "guidance", - "prose": "In certain situations, the nature of the vulnerability scanning may be more intrusive or the information system component that is the subject of the scanning may contain highly sensitive information. Privileged access authorization to selected system components facilitates more thorough vulnerability scanning and also protects the sensitive nature of such scanning." - }, - { - "id": "ra-5.5_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "ra-5.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(5)[1]" - } - ], - "prose": "the organization defines information system components to which privileged access is authorized for selected vulnerability scanning activities;" - }, - { - "id": "ra-5.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(5)[2]" - } - ], - "prose": "the organization defines vulnerability scanning activities selected for privileged access authorization to organization-defined information system components; and" - }, - { - "id": "ra-5.5_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-5(5)[3]" - } - ], - "prose": "the information system implements privileged access authorization to organization-defined information system components for selected organization-defined vulnerability scanning activities." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Risk assessment policy\n\nprocedures addressing vulnerability scanning\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of information system components for vulnerability scanning\n\npersonnel access authorization list\n\nauthorization credentials\n\naccess authorization records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with vulnerability scanning responsibilities\n\nsystem/network administrators\n\norganizational personnel responsible for access control to the information system\n\norganizational personnel responsible for configuration management of the information system\n\nsystem developers\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for vulnerability scanning\n\norganizational processes for access control\n\nautomated mechanisms supporting and/or implementing access control\n\nautomated mechanisms/tools supporting and/or implementing vulnerability scanning" - } - ] - } - ] - }, - { - "id": "ra-5.6", - "class": "SP800-53-enhancement", - "title": "Automated Trend Analyses", - "props": [ - { - "name": "label", - "value": "RA-5(6)" - }, - { - "name": "sort-id", - "value": "ra-05.06" - } - ], - "parts": [ - { - "id": "ra-5.6_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to compare the results of vulnerability scans over time to determine trends in information system vulnerabilities." - }, - { - "id": "ra-5.6_gdn", - "name": "guidance", - "links": [ - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-5", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "ra-5.6_obj", - "name": "objective", - "prose": "Determine if the organization employs automated mechanisms to compare the results of vulnerability scans over time to determine trends in information system vulnerabilities." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Risk assessment policy\n\nprocedures addressing vulnerability scanning\n\ninformation system design documentation\n\nvulnerability scanning tools and techniques documentation\n\nvulnerability scanning results\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with vulnerability scanning responsibilities\n\norganizational personnel with vulnerability scan analysis responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for vulnerability scanning\n\nautomated mechanisms/tools supporting and/or implementing vulnerability scanning\n\nautomated mechanisms supporting and/or implementing trend analysis of vulnerability scan results" - } - ] - } - ] - }, - { - "id": "ra-5.7", - "class": "SP800-53-enhancement", - "title": "Automated Detection and Notification of Unauthorized Components", - "props": [ - { - "name": "label", - "value": "RA-5(7)" - }, - { - "name": "sort-id", - "value": "ra-05.07" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#cm-8", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ra-5.8", - "class": "SP800-53-enhancement", - "title": "Review Historic Audit Logs", - "props": [ - { - "name": "label", - "value": "RA-5(8)" - }, - { - "name": "sort-id", - "value": "ra-05.08" - } - ], - "parts": [ - { - "id": "ra-5.8_smt", - "name": "statement", - "prose": "The organization reviews historic audit logs to determine if a vulnerability identified in the information system has been previously exploited." - }, - { - "id": "ra-5.8_gdn", - "name": "guidance", - "links": [ - { - "href": "#au-6", - "rel": "related" - } - ] - }, - { - "id": "ra-5.8_obj", - "name": "objective", - "prose": "Determine if the organization reviews historic audit logs to determine if a vulnerability identified in the information system has been previously exploited." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Risk assessment policy\n\nprocedures addressing vulnerability scanning\n\naudit logs\n\nrecords of audit log reviews\n\nvulnerability scanning results\n\npatch and vulnerability management records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with vulnerability scanning responsibilities\n\norganizational personnel with vulnerability scan analysis responsibilities\n\norganizational personnel with audit record review responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for vulnerability scanning\n\norganizational process for audit record review and response\n\nautomated mechanisms/tools supporting and/or implementing vulnerability scanning\n\nautomated mechanisms supporting and/or implementing audit record review" - } - ] - } - ] - }, - { - "id": "ra-5.9", - "class": "SP800-53-enhancement", - "title": "Penetration Testing and Analyses", - "props": [ - { - "name": "label", - "value": "RA-5(9)" - }, - { - "name": "sort-id", - "value": "ra-05.09" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#ca-8", - "rel": "incorporated-into" - } - ] - }, - { - "id": "ra-5.10", - "class": "SP800-53-enhancement", - "title": "Correlate Scanning Information", - "props": [ - { - "name": "label", - "value": "RA-5(10)" - }, - { - "name": "sort-id", - "value": "ra-05.10" - } - ], - "parts": [ - { - "id": "ra-5.10_smt", - "name": "statement", - "prose": "The organization correlates the output from vulnerability scanning tools to determine the presence of multi-vulnerability/multi-hop attack vectors." - }, - { - "id": "ra-5.10_obj", - "name": "objective", - "prose": "Determine if the organization correlates the output from vulnerability scanning tools to determine the presence of multi-vulnerability/multi-hop attack vectors." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Risk assessment policy\n\nprocedures addressing vulnerability scanning\n\nrisk assessment\n\nsecurity plan\n\nvulnerability scanning tools and techniques documentation\n\nvulnerability scanning results\n\nvulnerability management records\n\naudit records\n\nevent/vulnerability correlation logs\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with vulnerability scanning responsibilities\n\norganizational personnel with vulnerability scan analysis responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for vulnerability scanning\n\nautomated mechanisms/tools supporting and/or implementing vulnerability scanning\n\nautomated mechanisms implementing correlation of vulnerability scan results" - } - ] - } - ] - } - ] - }, - { - "id": "ra-6", - "class": "SP800-53", - "title": "Technical Surveillance Countermeasures Survey", - "params": [ - { - "id": "ra-6_prm_1", - "label": "organization-defined locations" - }, - { - "id": "ra-6_prm_2", - "select": { - "how-many": "one-or-more", - "choice": [ - " {{ insert: param, ra-6_prm_3 }} ", - " {{ insert: param, ra-6_prm_4 }} " - ] - } - }, - { - "id": "ra-6_prm_3", - "depends-on": "ra-6_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "ra-6_prm_4", - "depends-on": "ra-6_prm_2", - "label": "organization-defined events or indicators occur" - } - ], - "props": [ - { - "name": "label", - "value": "RA-6" - }, - { - "name": "sort-id", - "value": "ra-06" - } - ], - "parts": [ - { - "id": "ra-6_smt", - "name": "statement", - "prose": "The organization employs a technical surveillance countermeasures survey at {{ insert: param, ra-6_prm_1 }} {{ insert: param, ra-6_prm_2 }}." - }, - { - "id": "ra-6_gdn", - "name": "guidance", - "prose": "Technical surveillance countermeasures surveys are performed by qualified personnel to detect the presence of technical surveillance devices/hazards and to identify technical security weaknesses that could aid in the conduct of technical penetrations of surveyed facilities. Such surveys provide evaluations of the technical security postures of organizations and facilities and typically include thorough visual, electronic, and physical examinations in and about surveyed facilities. The surveys also provide useful input into risk assessments and organizational exposure to potential adversaries." - }, - { - "id": "ra-6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "ra-6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-6[1]" - } - ], - "prose": "defines locations to employ technical surveillance countermeasure surveys;" - }, - { - "id": "ra-6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-6[2]" - } - ], - "prose": "defines a frequency to employ technical surveillance countermeasure surveys;" - }, - { - "id": "ra-6_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-6[3]" - } - ], - "prose": "defines events or indicators which, if they occur, trigger a technical surveillance countermeasures survey;" - }, - { - "id": "ra-6_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-6[4]" - } - ], - "prose": "employs a technical surveillance countermeasures survey at organization-defined locations one or more of the following:", - "parts": [ - { - "id": "ra-6_obj.4.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-6[4][a]" - } - ], - "prose": "with the organization-defined frequency; and/or" - }, - { - "id": "ra-6_obj.4.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "RA-6[4][b]" - } - ], - "prose": "when organization-defined events or indicators occur." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Risk assessment policy\n\nprocedures addressing technical surveillance countermeasures surveys\n\nsecurity plan\n\naudit records/event logs\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with technical surveillance countermeasures surveys responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for technical surveillance countermeasures surveys\n\nautomated mechanisms/tools supporting and/or implementing technical surveillance countermeasures surveys" - } - ] - } - ] - } - ] - }, - { - "id": "sa", - "class": "family", - "title": "System and Services Acquisition", - "controls": [ - { - "id": "sa-1", - "class": "SP800-53", - "title": "System and Services Acquisition Policy and Procedures", - "params": [ - { - "id": "sa-1_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "sa-1_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "sa-1_prm_3", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "SA-1" - }, - { - "name": "sort-id", - "value": "sa-01" - } - ], - "links": [ - { - "href": "#5c201b63-0768-417b-ac22-3f014e3941b2", - "rel": "reference" - }, - { - "href": "#9cb3d8fe-2127-48ba-821e-cdd2d7aee921", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sa-1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sa-1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops, documents, and disseminates to {{ insert: param, sa-1_prm_1 }}:", - "parts": [ - { - "id": "sa-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "A system and services acquisition policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "sa-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the system and services acquisition policy and associated system and services acquisition controls; and" - } - ] - }, - { - "id": "sa-1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the current:", - "parts": [ - { - "id": "sa-1_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "System and services acquisition policy {{ insert: param, sa-1_prm_2 }}; and" - }, - { - "id": "sa-1_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "System and services acquisition procedures {{ insert: param, sa-1_prm_3 }}." - } - ] - } - ] - }, - { - "id": "sa-1_gdn", - "name": "guidance", - "prose": "This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the SA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures.", - "links": [ - { - "href": "#pm-9", - "rel": "related" - } - ] - }, - { - "id": "sa-1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(a)" - } - ], - "parts": [ - { - "id": "sa-1.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(a)(1)" - } - ], - "parts": [ - { - "id": "sa-1.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(a)(1)[1]" - } - ], - "prose": "develops and documents a system and services acquisition policy that addresses:", - "parts": [ - { - "id": "sa-1.a.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(a)(1)[1][a]" - } - ], - "prose": "purpose;" - }, - { - "id": "sa-1.a.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(a)(1)[1][b]" - } - ], - "prose": "scope;" - }, - { - "id": "sa-1.a.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(a)(1)[1][c]" - } - ], - "prose": "roles;" - }, - { - "id": "sa-1.a.1_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(a)(1)[1][d]" - } - ], - "prose": "responsibilities;" - }, - { - "id": "sa-1.a.1_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(a)(1)[1][e]" - } - ], - "prose": "management commitment;" - }, - { - "id": "sa-1.a.1_obj.1.f", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(a)(1)[1][f]" - } - ], - "prose": "coordination among organizational entities;" - }, - { - "id": "sa-1.a.1_obj.1.g", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(a)(1)[1][g]" - } - ], - "prose": "compliance;" - } - ] - }, - { - "id": "sa-1.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(a)(1)[2]" - } - ], - "prose": "defines personnel or roles to whom the system and services acquisition policy is to be disseminated;" - }, - { - "id": "sa-1.a.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(a)(1)[3]" - } - ], - "prose": "disseminates the system and services acquisition policy to organization-defined personnel or roles;" - } - ] - }, - { - "id": "sa-1.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(a)(2)" - } - ], - "parts": [ - { - "id": "sa-1.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(a)(2)[1]" - } - ], - "prose": "develops and documents procedures to facilitate the implementation of the system and services acquisition policy and associated system and services acquisition controls;" - }, - { - "id": "sa-1.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(a)(2)[2]" - } - ], - "prose": "defines personnel or roles to whom the procedures are to be disseminated;" - }, - { - "id": "sa-1.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(a)(2)[3]" - } - ], - "prose": "disseminates the procedures to organization-defined personnel or roles;" - } - ] - } - ] - }, - { - "id": "sa-1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(b)" - } - ], - "parts": [ - { - "id": "sa-1.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(b)(1)" - } - ], - "parts": [ - { - "id": "sa-1.b.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(b)(1)[1]" - } - ], - "prose": "defines the frequency to review and update the current system and services acquisition policy;" - }, - { - "id": "sa-1.b.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(b)(1)[2]" - } - ], - "prose": "reviews and updates the current system and services acquisition policy with the organization-defined frequency;" - } - ] - }, - { - "id": "sa-1.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(b)(2)" - } - ], - "parts": [ - { - "id": "sa-1.b.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(b)(2)[1]" - } - ], - "prose": "defines the frequency to review and update the current system and services acquisition procedures; and" - }, - { - "id": "sa-1.b.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-1(b)(2)[2]" - } - ], - "prose": "reviews and updates the current system and services acquisition procedures with the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy and procedures\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "sa-2", - "class": "SP800-53", - "title": "Allocation of Resources", - "props": [ - { - "name": "label", - "value": "SA-2" - }, - { - "name": "sort-id", - "value": "sa-02" - } - ], - "links": [ - { - "href": "#29fcfe59-33cd-494a-8756-5907ae3a8f92", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sa-2_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sa-2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Determines information security requirements for the information system or information system service in mission/business process planning;" - }, - { - "id": "sa-2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Determines, documents, and allocates the resources required to protect the information system or information system service as part of its capital planning and investment control process; and" - }, - { - "id": "sa-2_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Establishes a discrete line item for information security in organizational programming and budgeting documentation." - } - ] - }, - { - "id": "sa-2_gdn", - "name": "guidance", - "prose": "Resource allocation for information security includes funding for the initial information system or information system service acquisition and funding for the sustainment of the system/service.", - "links": [ - { - "href": "#pm-3", - "rel": "related" - }, - { - "href": "#pm-11", - "rel": "related" - } - ] - }, - { - "id": "sa-2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-2(a)" - } - ], - "prose": "determines information security requirements for the information system or information system service in mission/business process planning;" - }, - { - "id": "sa-2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-2(b)" - } - ], - "prose": "to protect the information system or information system service as part of its capital planning and investment control process:", - "parts": [ - { - "id": "sa-2.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-2(b)[1]" - } - ], - "prose": "determines the resources required;" - }, - { - "id": "sa-2.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-2(b)[2]" - } - ], - "prose": "documents the resources required;" - }, - { - "id": "sa-2.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-2(b)[3]" - } - ], - "prose": "allocates the resources required; and" - } - ] - }, - { - "id": "sa-2.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-2(c)" - } - ], - "prose": "establishes a discrete line item for information security in organizational programming and budgeting documentation." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing the allocation of resources to information security requirements\n\nprocedures addressing capital planning and investment control\n\norganizational programming and budgeting documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with capital planning, investment control, organizational programming and budgeting responsibilities\n\norganizational personnel responsible for determining information security requirements for information systems/services\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for determining information security requirements\n\norganizational processes for capital planning, programming, and budgeting\n\nautomated mechanisms supporting and/or implementing organizational capital planning, programming, and budgeting" - } - ] - } - ] - }, - { - "id": "sa-3", - "class": "SP800-53", - "title": "System Development Life Cycle", - "params": [ - { - "id": "sa-3_prm_1", - "label": "organization-defined system development life cycle" - } - ], - "props": [ - { - "name": "label", - "value": "SA-3" - }, - { - "name": "sort-id", - "value": "sa-03" - } - ], - "links": [ - { - "href": "#0a0c26b6-fd44-4274-8b36-93442d49d998", - "rel": "reference" - }, - { - "href": "#abd950ae-092f-4b7a-b374-1c7c67fe9350", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sa-3_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sa-3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Manages the information system using {{ insert: param, sa-3_prm_1 }} that incorporates information security considerations;" - }, - { - "id": "sa-3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Defines and documents information security roles and responsibilities throughout the system development life cycle;" - }, - { - "id": "sa-3_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Identifies individuals having information security roles and responsibilities; and" - }, - { - "id": "sa-3_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Integrates the organizational information security risk management process into system development life cycle activities." - } - ] - }, - { - "id": "sa-3_gdn", - "name": "guidance", - "prose": "A well-defined system development life cycle provides the foundation for the successful development, implementation, and operation of organizational information systems. To apply the required security controls within the system development life cycle requires a basic understanding of information security, threats, vulnerabilities, adverse impacts, and risk to critical missions/business functions. The security engineering principles in SA-8 cannot be properly applied if individuals that design, code, and test information systems and system components (including information technology products) do not understand security. Therefore, organizations include qualified personnel, for example, chief information security officers, security architects, security engineers, and information system security officers in system development life cycle activities to ensure that security requirements are incorporated into organizational information systems. It is equally important that developers include individuals on the development team that possess the requisite security expertise and skills to ensure that needed security capabilities are effectively integrated into the information system. Security awareness and training programs can help ensure that individuals having key security roles and responsibilities have the appropriate experience, skills, and expertise to conduct assigned system development life cycle activities. The effective integration of security requirements into enterprise architecture also helps to ensure that important security considerations are addressed early in the system development life cycle and that those considerations are directly related to the organizational mission/business processes. This process also facilitates the integration of the information security architecture into the enterprise architecture, consistent with organizational risk management and information security strategies.", - "links": [ - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#pm-7", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - } - ] - }, - { - "id": "sa-3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-3(a)" - } - ], - "parts": [ - { - "id": "sa-3.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-3(a)[1]" - } - ], - "prose": "defines a system development life cycle that incorporates information security considerations to be used to manage the information system;" - }, - { - "id": "sa-3.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-3(a)[2]" - } - ], - "prose": "manages the information system using the organization-defined system development life cycle;" - } - ] - }, - { - "id": "sa-3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-3(b)" - } - ], - "prose": "defines and documents information security roles and responsibilities throughout the system development life cycle;" - }, - { - "id": "sa-3.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-3(c)" - } - ], - "prose": "identifies individuals having information security roles and responsibilities; and" - }, - { - "id": "sa-3.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-3(d)" - } - ], - "prose": "integrates the organizational information security risk management process into system development life cycle activities." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing the integration of information security into the system development life cycle process\n\ninformation system development life cycle documentation\n\ninformation security risk management strategy/program documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security and system life cycle development responsibilities\n\norganizational personnel with information security risk management responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for defining and documenting the SDLC\n\norganizational processes for identifying SDLC roles and responsibilities\n\norganizational process for integrating information security risk management into the SDLC\n\nautomated mechanisms supporting and/or implementing the SDLC" - } - ] - } - ] - }, - { - "id": "sa-4", - "class": "SP800-53", - "title": "Acquisition Process", - "props": [ - { - "name": "label", - "value": "SA-4" - }, - { - "name": "sort-id", - "value": "sa-04" - } - ], - "links": [ - { - "href": "#ad733a42-a7ed-4774-b988-4930c28852f3", - "rel": "reference" - }, - { - "href": "#1737a687-52fb-4008-b900-cbfa836f7b65", - "rel": "reference" - }, - { - "href": "#d715b234-9b5b-4e07-b1ed-99836727664d", - "rel": "reference" - }, - { - "href": "#c80c10b3-1294-4984-a4cc-d1733ca432b9", - "rel": "reference" - }, - { - "href": "#0a5db899-f033-467f-8631-f5a8ba971475", - "rel": "reference" - }, - { - "href": "#0c775bc3-bfc3-42c7-a382-88949f503171", - "rel": "reference" - }, - { - "href": "#d818efd3-db31-4953-8afa-9e76afe83ce2", - "rel": "reference" - }, - { - "href": "#0a0c26b6-fd44-4274-8b36-93442d49d998", - "rel": "reference" - }, - { - "href": "#abd950ae-092f-4b7a-b374-1c7c67fe9350", - "rel": "reference" - }, - { - "href": "#84a37532-6db6-477b-9ea8-f9085ebca0fc", - "rel": "reference" - }, - { - "href": "#cee2c6ca-0261-4a6f-b630-e41d8ffdd82b", - "rel": "reference" - }, - { - "href": "#56d671da-6b7b-4abf-8296-84b61980390a", - "rel": "reference" - }, - { - "href": "#c95a9986-3cd6-4a98-931b-ccfc56cb11e5", - "rel": "reference" - }, - { - "href": "#5ed1f4d5-1494-421b-97ed-39d3c88ab51f", - "rel": "reference" - }, - { - "href": "#bbd50dd1-54ce-4432-959d-63ea564b1bb4", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sa-4_smt", - "name": "statement", - "prose": "The organization includes the following requirements, descriptions, and criteria, explicitly or by reference, in the acquisition contract for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs:", - "parts": [ - { - "id": "sa-4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Security functional requirements;" - }, - { - "id": "sa-4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Security strength requirements;" - }, - { - "id": "sa-4_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Security assurance requirements;" - }, - { - "id": "sa-4_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Security-related documentation requirements;" - }, - { - "id": "sa-4_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Requirements for protecting security-related documentation;" - }, - { - "id": "sa-4_smt.f", - "name": "item", - "props": [ - { - "name": "label", - "value": "f." - } - ], - "prose": "Description of the information system development environment and environment in which the system is intended to operate; and" - }, - { - "id": "sa-4_smt.g", - "name": "item", - "props": [ - { - "name": "label", - "value": "g." - } - ], - "prose": "Acceptance criteria." - } - ] - }, - { - "id": "sa-4_gdn", - "name": "guidance", - "prose": "Information system components are discrete, identifiable information technology assets (e.g., hardware, software, or firmware) that represent the building blocks of an information system. Information system components include commercial information technology products. Security functional requirements include security capabilities, security functions, and security mechanisms. Security strength requirements associated with such capabilities, functions, and mechanisms include degree of correctness, completeness, resistance to direct attack, and resistance to tampering or bypass. Security assurance requirements include: (i) development processes, procedures, practices, and methodologies; and (ii) evidence from development and assessment activities providing grounds for confidence that the required security functionality has been implemented and the required security strength has been achieved. Security documentation requirements address all phases of the system development life cycle. Security functionality, assurance, and documentation requirements are expressed in terms of security controls and control enhancements that have been selected through the tailoring process. The security control tailoring process includes, for example, the specification of parameter values through the use of assignment and selection statements and the specification of platform dependencies and implementation information. Security documentation provides user and administrator guidance regarding the implementation and operation of security controls. The level of detail required in security documentation is based on the security category or classification level of the information system and the degree to which organizations depend on the stated security capability, functions, or mechanisms to meet overall risk response expectations (as defined in the organizational risk management strategy). Security requirements can also include organizationally mandated configuration settings specifying allowed functions, ports, protocols, and services. Acceptance criteria for information systems, information system components, and information system services are defined in the same manner as such criteria for any organizational acquisition or procurement. The Federal Acquisition Regulation (FAR) Section 7.103 contains information security requirements from FISMA.", - "links": [ - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#ps-7", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-11", - "rel": "related" - }, - { - "href": "#sa-12", - "rel": "related" - } - ] - }, - { - "id": "sa-4_obj", - "name": "objective", - "prose": "Determine if the organization includes the following requirements, descriptions, and criteria, explicitly or by reference, in the acquisition contracts for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs:", - "parts": [ - { - "id": "sa-4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(a)" - } - ], - "prose": "security functional requirements;" - }, - { - "id": "sa-4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(b)" - } - ], - "prose": "security strength requirements;" - }, - { - "id": "sa-4.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(c)" - } - ], - "prose": "security assurance requirements;" - }, - { - "id": "sa-4.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(d)" - } - ], - "prose": "security-related documentation requirements;" - }, - { - "id": "sa-4.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(e)" - } - ], - "prose": "requirements for protecting security-related documentation;" - }, - { - "id": "sa-4.f_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(f)" - } - ], - "prose": "description of:", - "parts": [ - { - "id": "sa-4.f_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(f)[1]" - } - ], - "prose": "the information system development environment;" - }, - { - "id": "sa-4.f_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(f)[2]" - } - ], - "prose": "the environment in which the system is intended to operate; and" - } - ] - }, - { - "id": "sa-4.g_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(g)" - } - ], - "prose": "acceptance criteria." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing the integration of information security requirements, descriptions, and criteria into the acquisition process\n\nacquisition contracts for the information system, system component, or information system service\n\ninformation system design documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with responsibility for determining information system security functional, strength, and assurance requirements\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for determining information system security functional, strength, and assurance requirements\n\norganizational processes for developing acquisition contracts\n\nautomated mechanisms supporting and/or implementing acquisitions and inclusion of security requirements in contracts" - } - ] - } - ], - "controls": [ - { - "id": "sa-4.1", - "class": "SP800-53-enhancement", - "title": "Functional Properties of Security Controls", - "props": [ - { - "name": "label", - "value": "SA-4(1)" - }, - { - "name": "sort-id", - "value": "sa-04.01" - } - ], - "parts": [ - { - "id": "sa-4.1_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to provide a description of the functional properties of the security controls to be employed." - }, - { - "id": "sa-4.1_gdn", - "name": "guidance", - "prose": "Functional properties of security controls describe the functionality (i.e., security capability, functions, or mechanisms) visible at the interfaces of the controls and specifically exclude functionality and data structures internal to the operation of the controls.", - "links": [ - { - "href": "#sa-5", - "rel": "related" - } - ] - }, - { - "id": "sa-4.1_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to provide a description of the functional properties of the security controls to be employed." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing the integration of information security requirements, descriptions, and criteria into the acquisition process\n\nsolicitation documents\n\nacquisition documentation\n\nacquisition contracts for the information system, system component, or information system services\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with responsibility for determining information system security functional requirements\n\ninformation system developer or service provider\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for determining information system security functional, requirements\n\norganizational processes for developing acquisition contracts\n\nautomated mechanisms supporting and/or implementing acquisitions and inclusion of security requirements in contracts" - } - ] - } - ] - }, - { - "id": "sa-4.2", - "class": "SP800-53-enhancement", - "title": "Design / Implementation Information for Security Controls", - "params": [ - { - "id": "sa-4.2_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "security-relevant external system interfaces", - "high-level design", - "low-level design", - "source code or hardware schematics", - " {{ insert: param, sa-4.2_prm_2 }} " - ] - } - }, - { - "id": "sa-4.2_prm_2", - "depends-on": "sa-4.2_prm_1", - "label": "organization-defined design/implementation information" - }, - { - "id": "sa-4.2_prm_3", - "label": "organization-defined level of detail" - } - ], - "props": [ - { - "name": "label", - "value": "SA-4(2)" - }, - { - "name": "sort-id", - "value": "sa-04.02" - } - ], - "parts": [ - { - "id": "sa-4.2_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to provide design and implementation information for the security controls to be employed that includes: {{ insert: param, sa-4.2_prm_1 }} at {{ insert: param, sa-4.2_prm_3 }}." - }, - { - "id": "sa-4.2_gdn", - "name": "guidance", - "prose": "Organizations may require different levels of detail in design and implementation documentation for security controls employed in organizational information systems, system components, or information system services based on mission/business requirements, requirements for trustworthiness/resiliency, and requirements for analysis and testing. Information systems can be partitioned into multiple subsystems. Each subsystem within the system can contain one or more modules. The high-level design for the system is expressed in terms of multiple subsystems and the interfaces between subsystems providing security-relevant functionality. The low-level design for the system is expressed in terms of modules with particular emphasis on software and firmware (but not excluding hardware) and the interfaces between modules providing security-relevant functionality. Source code and hardware schematics are typically referred to as the implementation representation of the information system.", - "links": [ - { - "href": "#sa-5", - "rel": "related" - } - ] - }, - { - "id": "sa-4.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-4.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(2)[1]" - } - ], - "prose": "defines level of detail that the developer is required to provide in design and implementation information for the security controls to be employed in the information system, system component, or information system service;" - }, - { - "id": "sa-4.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(2)[2]" - } - ], - "prose": "defines design/implementation information that the developer is to provide for the security controls to be employed (if selected);" - }, - { - "id": "sa-4.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(2)[3]" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to provide design and implementation information for the security controls to be employed that includes, at the organization-defined level of detail, one or more of the following:", - "parts": [ - { - "id": "sa-4.2_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(2)[3][a]" - } - ], - "prose": "security-relevant external system interfaces;" - }, - { - "id": "sa-4.2_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(2)[3][b]" - } - ], - "prose": "high-level design;" - }, - { - "id": "sa-4.2_obj.3.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(2)[3][c]" - } - ], - "prose": "low-level design;" - }, - { - "id": "sa-4.2_obj.3.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(2)[3][d]" - } - ], - "prose": "source code;" - }, - { - "id": "sa-4.2_obj.3.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(2)[3][e]" - } - ], - "prose": "hardware schematics; and/or" - }, - { - "id": "sa-4.2_obj.3.f", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(2)[3][f]" - } - ], - "prose": "organization-defined design/implementation information." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing the integration of information security requirements, descriptions, and criteria into the acquisition process\n\nsolicitation documents\n\nacquisition documentation\n\nacquisition contracts for the information system, system components, or information system services\n\ndesign and implementation information for security controls employed in the information system, system component, or information system service\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with responsibility for determining information system security requirements\n\ninformation system developer or service provider\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for determining level of detail for system design and security controls\n\norganizational processes for developing acquisition contracts\n\nautomated mechanisms supporting and/or implementing development of system design details" - } - ] - } - ] - }, - { - "id": "sa-4.3", - "class": "SP800-53-enhancement", - "title": "Development Methods / Techniques / Practices", - "params": [ - { - "id": "sa-4.3_prm_1", - "label": "organization-defined state-of-the-practice system/security engineering methods, software development methods, testing/evaluation/validation techniques, and quality control processes" - } - ], - "props": [ - { - "name": "label", - "value": "SA-4(3)" - }, - { - "name": "sort-id", - "value": "sa-04.03" - } - ], - "parts": [ - { - "id": "sa-4.3_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to demonstrate the use of a system development life cycle that includes {{ insert: param, sa-4.3_prm_1 }}." - }, - { - "id": "sa-4.3_gdn", - "name": "guidance", - "prose": "Following a well-defined system development life cycle that includes state-of-the-practice software development methods, systems/security engineering methods, quality control processes, and testing, evaluation, and validation techniques helps to reduce the number and severity of latent errors within information systems, system components, and information system services. Reducing the number/severity of such errors reduces the number of vulnerabilities in those systems, components, and services.", - "links": [ - { - "href": "#sa-12", - "rel": "related" - } - ] - }, - { - "id": "sa-4.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-4.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(3)[1]" - } - ], - "prose": "defines state-of-the-practice system/security engineering methods to be included in the system development life cycle employed by the developer of the information system, system component, or information system service;" - }, - { - "id": "sa-4.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(3)[2]" - } - ], - "prose": "defines software development methods to be included in the system development life cycle employed by the developer of the information system, system component, or information system service;" - }, - { - "id": "sa-4.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(3)[3]" - } - ], - "prose": "defines testing/evaluation/validation techniques to be included in the system development life cycle employed by the developer of the information system, system component, or information system service;" - }, - { - "id": "sa-4.3_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(3)[4]" - } - ], - "prose": "defines quality control processes to be included in the system development life cycle employed by the developer of the information system, system component, or information system service;" - }, - { - "id": "sa-4.3_obj.5", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(3)[5]" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to demonstrate the use of a system development life cycle that includes:", - "parts": [ - { - "id": "sa-4.3_obj.5.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(3)[5][a]" - } - ], - "prose": "organization-defined state-of-the-practice system/security engineering methods;" - }, - { - "id": "sa-4.3_obj.5.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(3)[5][b]" - } - ], - "prose": "organization-defined software development methods;" - }, - { - "id": "sa-4.3_obj.5.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(3)[5][c]" - } - ], - "prose": "organization-defined testing/evaluation/validation techniques; and" - }, - { - "id": "sa-4.3_obj.5.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(3)[5][d]" - } - ], - "prose": "organization-defined quality control processes." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing the integration of information security requirements, descriptions, and criteria into the acquisition process\n\nsolicitation documents\n\nacquisition documentation\n\nacquisition contracts for the information system, system component, or information system service\n\nlist of system/security engineering methods to be included in developer’s system development life cycle process\n\nlist of software development methods to be included in developer’s system development life cycle process\n\nlist of testing/evaluation/validation techniques to be included in developer’s system development life cycle process\n\nlist of quality control processes to be included in developer’s system development life cycle process\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with responsibility for determining information system security requirements\n\norganizational personnel with information security and system life cycle responsibilities\n\ninformation system developer or service provider" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for development methods, techniques, and processes" - } - ] - } - ] - }, - { - "id": "sa-4.4", - "class": "SP800-53-enhancement", - "title": "Assignment of Components to Systems", - "props": [ - { - "name": "label", - "value": "SA-4(4)" - }, - { - "name": "sort-id", - "value": "sa-04.04" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#cm-8.9", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sa-4.5", - "class": "SP800-53-enhancement", - "title": "System / Component / Service Configurations", - "params": [ - { - "id": "sa-4.5_prm_1", - "label": "organization-defined security configurations" - } - ], - "props": [ - { - "name": "label", - "value": "SA-4(5)" - }, - { - "name": "sort-id", - "value": "sa-04.05" - } - ], - "parts": [ - { - "id": "sa-4.5_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to:", - "parts": [ - { - "id": "sa-4.5_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Deliver the system, component, or service with {{ insert: param, sa-4.5_prm_1 }} implemented; and" - }, - { - "id": "sa-4.5_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Use the configurations as the default for any subsequent system, component, or service reinstallation or upgrade." - } - ] - }, - { - "id": "sa-4.5_gdn", - "name": "guidance", - "prose": "Security configurations include, for example, the U.S. Government Configuration Baseline (USGCB) and any limitations on functions, ports, protocols, and services. Security characteristics include, for example, requiring that all default passwords have been changed.", - "links": [ - { - "href": "#cm-8", - "rel": "related" - } - ] - }, - { - "id": "sa-4.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-4.5.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(5)(a)" - } - ], - "parts": [ - { - "id": "sa-4.5.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(5)(a)[1]" - } - ], - "prose": "defines security configurations to be implemented by the developer of the information system, system component, or information system service;" - }, - { - "id": "sa-4.5.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(5)(a)[2]" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to deliver the system, component, or service with organization-defined security configurations implemented; and" - } - ], - "links": [ - { - "href": "#sa-4.5_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "sa-4.5.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(5)(b)" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to use the configurations as the default for any subsequent system, component, or service reinstallation or upgrade.", - "links": [ - { - "href": "#sa-4.5_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing the integration of information security requirements, descriptions, and criteria into the acquisition process\n\nsolicitation documents\n\nacquisition documentation\n\nacquisition contracts for the information system, system component, or information system service\n\nsecurity configurations to be implemented by developer of the information system, system component, or information system service\n\nservice-level agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with responsibility for determining information system security requirements\n\ninformation system developer or service provider\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms used to verify that the configuration of the information system, component, or service, as delivered, is as specified" - } - ] - } - ] - }, - { - "id": "sa-4.6", - "class": "SP800-53-enhancement", - "title": "Use of Information Assurance Products", - "props": [ - { - "name": "label", - "value": "SA-4(6)" - }, - { - "name": "sort-id", - "value": "sa-04.06" - } - ], - "parts": [ - { - "id": "sa-4.6_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sa-4.6_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Employs only government off-the-shelf (GOTS) or commercial off-the-shelf (COTS) information assurance (IA) and IA-enabled information technology products that compose an NSA-approved solution to protect classified information when the networks used to transmit the information are at a lower classification level than the information being transmitted; and" - }, - { - "id": "sa-4.6_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Ensures that these products have been evaluated and/or validated by NSA or in accordance with NSA-approved procedures." - } - ] - }, - { - "id": "sa-4.6_gdn", - "name": "guidance", - "prose": "COTS IA or IA-enabled information technology products used to protect classified information by cryptographic means may be required to use NSA-approved key management.", - "links": [ - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "sa-4.6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-4.6.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(6)(a)" - } - ], - "prose": "employs only government off-the-shelf (GOTS) or commercial off-the-shelf (COTS) information assurance (IA) and IA-enabled information technology products that compose an NSA-approved solution to protect classified information when the networks used to transmit the information are at a lower classification level than the information being transmitted; and", - "links": [ - { - "href": "#sa-4.6_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "sa-4.6.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(6)(b)" - } - ], - "prose": "ensures that these products have been evaluated and/or validated by the NSA or in accordance with NSA-approved procedures.", - "links": [ - { - "href": "#sa-4.6_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing the integration of information security requirements, descriptions, and criteria into the acquisition process\n\nsolicitation documents\n\nacquisition documentation\n\nacquisition contracts for the information system, system component, or information system service\n\nsecurity configurations to be implemented by developer of the information system, system component, or information system service\n\nservice-level agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with responsibility for determining information system security requirements\n\norganizational personnel responsible for ensuring information assurance products are NSA-approved and are evaluated and/or validated products in accordance with NSA-approved procedures\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for selecting and employing evaluated and/or validated information assurance products and services that compose an NSA-approved solution to protect classified information" - } - ] - } - ] - }, - { - "id": "sa-4.7", - "class": "SP800-53-enhancement", - "title": "Niap-approved Protection Profiles", - "props": [ - { - "name": "label", - "value": "SA-4(7)" - }, - { - "name": "sort-id", - "value": "sa-04.07" - } - ], - "parts": [ - { - "id": "sa-4.7_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sa-4.7_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Limits the use of commercially provided information assurance (IA) and IA-enabled information technology products to those products that have been successfully evaluated against a National Information Assurance partnership (NIAP)-approved Protection Profile for a specific technology type, if such a profile exists; and" - }, - { - "id": "sa-4.7_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Requires, if no NIAP-approved Protection Profile exists for a specific technology type but a commercially provided information technology product relies on cryptographic functionality to enforce its security policy, that the cryptographic module is FIPS-validated." - } - ] - }, - { - "id": "sa-4.7_gdn", - "name": "guidance", - "links": [ - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "sa-4.7_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-4.7.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(7)(a)" - } - ], - "prose": "limits the use of commercially-provided information assurance (IA) and IA-enabled information technology products to those products that have been successfully evaluated against a National Information Assurance partnership (NIAP)-approved Protection Profile for a specific technology type, if such a profile exists; and", - "links": [ - { - "href": "#sa-4.7_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "sa-4.7.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(7)(b)" - } - ], - "prose": "requires, if no NIAP-approved Protection Profile exists for a specific technology type but a commercially provided information technology product relies on cryptographic functionality to enforce its security policy, that the cryptographic module is FIPS-validated.", - "links": [ - { - "href": "#sa-4.7_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing the integration of information security requirements, descriptions, and criteria into the acquisition process\n\nsolicitation documents\n\nacquisition documentation\n\nacquisition contracts for the information system, system component, or information system service\n\nNAIP-approved protection profiles\n\nFIPS-validation information for cryptographic functionality\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with responsibility for determining information system security requirements\n\norganizational personnel responsible for ensuring information assurance products are have been evaluated against a NIAP-approved protection profile or for ensuring products relying on cryptographic functionality are FIPS-validated\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for selecting and employing products/services evaluated against a NIAP-approved protection profile or FIPS-validated products" - } - ] - } - ] - }, - { - "id": "sa-4.8", - "class": "SP800-53-enhancement", - "title": "Continuous Monitoring Plan", - "params": [ - { - "id": "sa-4.8_prm_1", - "label": "organization-defined level of detail" - } - ], - "props": [ - { - "name": "label", - "value": "SA-4(8)" - }, - { - "name": "sort-id", - "value": "sa-04.08" - } - ], - "parts": [ - { - "id": "sa-4.8_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to produce a plan for the continuous monitoring of security control effectiveness that contains {{ insert: param, sa-4.8_prm_1 }}." - }, - { - "id": "sa-4.8_gdn", - "name": "guidance", - "prose": "The objective of continuous monitoring plans is to determine if the complete set of planned, required, and deployed security controls within the information system, system component, or information system service continue to be effective over time based on the inevitable changes that occur. Developer continuous monitoring plans include a sufficient level of detail such that the information can be incorporated into the continuous monitoring strategies and programs implemented by organizations.", - "links": [ - { - "href": "#ca-7", - "rel": "related" - } - ] - }, - { - "id": "sa-4.8_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-4.8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(8)[1]" - } - ], - "prose": "defines the level of detail the developer of the information system, system component, or information system service is required to provide when producing a plan for the continuous monitoring of security control effectiveness; and" - }, - { - "id": "sa-4.8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(8)[2]" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to produce a plan for the continuous monitoring of security control effectiveness that contains the organization-defined level of detail." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing developer continuous monitoring plans\n\nprocedures addressing the integration of information security requirements, descriptions, and criteria into the acquisition process\n\ndeveloper continuous monitoring plans\n\nsecurity assessment plans\n\nacquisition contracts for the information system, system component, or information system service\n\nacquisition documentation\n\nsolicitation documentation\n\nservice-level agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with responsibility for determining information system security requirements\n\ninformation system developers\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Vendor processes for continuous monitoring\n\nautomated mechanisms supporting and/or implementing developer continuous monitoring" - } - ] - } - ] - }, - { - "id": "sa-4.9", - "class": "SP800-53-enhancement", - "title": "Functions / Ports / Protocols / Services in Use", - "props": [ - { - "name": "label", - "value": "SA-4(9)" - }, - { - "name": "sort-id", - "value": "sa-04.09" - } - ], - "parts": [ - { - "id": "sa-4.9_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to identify early in the system development life cycle, the functions, ports, protocols, and services intended for organizational use." - }, - { - "id": "sa-4.9_gdn", - "name": "guidance", - "prose": "The identification of functions, ports, protocols, and services early in the system development life cycle (e.g., during the initial requirements definition and design phases) allows organizations to influence the design of the information system, information system component, or information system service. This early involvement in the life cycle helps organizations to avoid or minimize the use of functions, ports, protocols, or services that pose unnecessarily high risks and understand the trade-offs involved in blocking specific ports, protocols, or services (or when requiring information system service providers to do so). Early identification of functions, ports, protocols, and services avoids costly retrofitting of security controls after the information system, system component, or information system service has been implemented. SA-9 describes requirements for external information system services with organizations identifying which functions, ports, protocols, and services are provided from external sources.", - "links": [ - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - } - ] - }, - { - "id": "sa-4.9_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to identify early in the system development life cycle:", - "parts": [ - { - "id": "sa-4.9_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(9)[1]" - } - ], - "prose": "the functions intended for organizational use;" - }, - { - "id": "sa-4.9_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(9)[2]" - } - ], - "prose": "the ports intended for organizational use;" - }, - { - "id": "sa-4.9_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(9)[3]" - } - ], - "prose": "the protocols intended for organizational use; and" - }, - { - "id": "sa-4.9_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-4(9)[4]" - } - ], - "prose": "the services intended for organizational use." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing the integration of information security requirements, descriptions, and criteria into the acquisition process\n\ninformation system design documentation\n\ninformation system documentation including functions, ports, protocols, and services intended for organizational use\n\nacquisition contracts for information systems or services\n\nacquisition documentation\n\nsolicitation documentation\n\nservice-level agreements\n\norganizational security requirements, descriptions, and criteria for developers of information systems, system components, and information system services\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with responsibility for determining information system security requirements\n\nsystem/network administrators\n\norganizational personnel operating, using, and/or maintaining the information system\n\ninformation system developers\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "sa-4.10", - "class": "SP800-53-enhancement", - "title": "Use of Approved PIV Products", - "props": [ - { - "name": "label", - "value": "SA-4(10)" - }, - { - "name": "sort-id", - "value": "sa-04.10" - } - ], - "parts": [ - { - "id": "sa-4.10_smt", - "name": "statement", - "prose": "The organization employs only information technology products on the FIPS 201-approved products list for Personal Identity Verification (PIV) capability implemented within organizational information systems." - }, - { - "id": "sa-4.10_gdn", - "name": "guidance", - "links": [ - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - } - ] - }, - { - "id": "sa-4.10_obj", - "name": "objective", - "prose": "Determine if the organization employs only information technology products on the FIPS 201-approved products list for Personal Identity Verification (PIV) capability implemented within organizational information systems." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing the integration of information security requirements, descriptions, and criteria into the acquisition process\n\nsolicitation documentation\n\nacquisition documentation\n\nacquisition contracts for the information system, system component, or information system service\n\nservice-level agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with responsibility for determining information system security requirements\n\norganizational personnel with responsibility for ensuring only FIPS 201-approved products are implemented\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for selecting and employing FIPS 201-approved products" - } - ] - } - ] - } - ] - }, - { - "id": "sa-5", - "class": "SP800-53", - "title": "Information System Documentation", - "params": [ - { - "id": "sa-5_prm_1", - "label": "organization-defined actions" - }, - { - "id": "sa-5_prm_2", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "SA-5" - }, - { - "name": "sort-id", - "value": "sa-05" - } - ], - "parts": [ - { - "id": "sa-5_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sa-5_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Obtains administrator documentation for the information system, system component, or information system service that describes:", - "parts": [ - { - "id": "sa-5_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Secure configuration, installation, and operation of the system, component, or service;" - }, - { - "id": "sa-5_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Effective use and maintenance of security functions/mechanisms; and" - }, - { - "id": "sa-5_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Known vulnerabilities regarding configuration and use of administrative (i.e., privileged) functions;" - } - ] - }, - { - "id": "sa-5_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Obtains user documentation for the information system, system component, or information system service that describes:", - "parts": [ - { - "id": "sa-5_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "User-accessible security functions/mechanisms and how to effectively use those security functions/mechanisms;" - }, - { - "id": "sa-5_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Methods for user interaction, which enables individuals to use the system, component, or service in a more secure manner; and" - }, - { - "id": "sa-5_smt.b.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "User responsibilities in maintaining the security of the system, component, or service;" - } - ] - }, - { - "id": "sa-5_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Documents attempts to obtain information system, system component, or information system service documentation when such documentation is either unavailable or nonexistent and takes {{ insert: param, sa-5_prm_1 }} in response;" - }, - { - "id": "sa-5_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Protects documentation as required, in accordance with the risk management strategy; and" - }, - { - "id": "sa-5_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Distributes documentation to {{ insert: param, sa-5_prm_2 }}." - } - ] - }, - { - "id": "sa-5_gdn", - "name": "guidance", - "prose": "This control helps organizational personnel understand the implementation and operation of security controls associated with information systems, system components, and information system services. Organizations consider establishing specific measures to determine the quality/completeness of the content provided. The inability to obtain needed documentation may occur, for example, due to the age of the information system/component or lack of support from developers and contractors. In those situations, organizations may need to recreate selected documentation if such documentation is essential to the effective implementation or operation of security controls. The level of protection provided for selected information system, component, or service documentation is commensurate with the security category or classification of the system. For example, documentation associated with a key DoD weapons system or command and control system would typically require a higher level of protection than a routine administrative system. Documentation that addresses information system vulnerabilities may also require an increased level of protection. Secure operation of the information system, includes, for example, initially starting the system and resuming secure system operation after any lapse in system operation.", - "links": [ - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#ps-2", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - } - ] - }, - { - "id": "sa-5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-5.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(a)" - } - ], - "prose": "obtains administrator documentation for the information system, system component, or information system service that describes:", - "parts": [ - { - "id": "sa-5.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(a)(1)" - } - ], - "parts": [ - { - "id": "sa-5.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(a)(1)[1]" - } - ], - "prose": "secure configuration of the system, system component, or service;" - }, - { - "id": "sa-5.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(a)(1)[2]" - } - ], - "prose": "secure installation of the system, system component, or service;" - }, - { - "id": "sa-5.a.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(a)(1)[3]" - } - ], - "prose": "secure operation of the system, system component, or service;" - } - ] - }, - { - "id": "sa-5.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(a)(2)" - } - ], - "parts": [ - { - "id": "sa-5.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(a)(2)[1]" - } - ], - "prose": "effective use of the security features/mechanisms;" - }, - { - "id": "sa-5.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(a)(2)[2]" - } - ], - "prose": "effective maintenance of the security features/mechanisms;" - } - ] - }, - { - "id": "sa-5.a.3_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(a)(3)" - } - ], - "prose": "known vulnerabilities regarding configuration and use of administrative (i.e., privileged) functions;" - } - ] - }, - { - "id": "sa-5.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(b)" - } - ], - "prose": "obtains user documentation for the information system, system component, or information system service that describes:", - "parts": [ - { - "id": "sa-5.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(b)(1)" - } - ], - "parts": [ - { - "id": "sa-5.b.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(b)(1)[1]" - } - ], - "prose": "user-accessible security functions/mechanisms;" - }, - { - "id": "sa-5.b.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(b)(1)[2]" - } - ], - "prose": "how to effectively use those functions/mechanisms;" - } - ] - }, - { - "id": "sa-5.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(b)(2)" - } - ], - "prose": "methods for user interaction, which enables individuals to use the system, component, or service in a more secure manner;" - }, - { - "id": "sa-5.b.3_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(b)(3)" - } - ], - "prose": "user responsibilities in maintaining the security of the system, component, or service;" - } - ] - }, - { - "id": "sa-5.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(c)" - } - ], - "parts": [ - { - "id": "sa-5.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(c)[1]" - } - ], - "prose": "defines actions to be taken after documented attempts to obtain information system, system component, or information system service documentation when such documentation is either unavailable or nonexistent;" - }, - { - "id": "sa-5.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(c)[2]" - } - ], - "prose": "documents attempts to obtain information system, system component, or information system service documentation when such documentation is either unavailable or nonexistent;" - }, - { - "id": "sa-5.c_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(c)[3]" - } - ], - "prose": "takes organization-defined actions in response;" - } - ] - }, - { - "id": "sa-5.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(d)" - } - ], - "prose": "protects documentation as required, in accordance with the risk management strategy;" - }, - { - "id": "sa-5.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(e)" - } - ], - "parts": [ - { - "id": "sa-5.e_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(e)[1]" - } - ], - "prose": "defines personnel or roles to whom documentation is to be distributed; and" - }, - { - "id": "sa-5.e_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-5(e)[2]" - } - ], - "prose": "distributes documentation to organization-defined personnel or roles." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing information system documentation\n\ninformation system documentation including administrator and user guides\n\nrecords documenting attempts to obtain unavailable or nonexistent information system documentation\n\nlist of actions to be taken in response to documented attempts to obtain information system, system component, or information system service documentation\n\nrisk management strategy documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with responsibility for determining information system security requirements\n\nsystem administrators\n\norganizational personnel operating, using, and/or maintaining the information system\n\ninformation system developers\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for obtaining, protecting, and distributing information system administrator and user documentation" - } - ] - } - ], - "controls": [ - { - "id": "sa-5.1", - "class": "SP800-53-enhancement", - "title": "Functional Properties of Security Controls", - "props": [ - { - "name": "label", - "value": "SA-5(1)" - }, - { - "name": "sort-id", - "value": "sa-05.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sa-4.1", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sa-5.2", - "class": "SP800-53-enhancement", - "title": "Security-relevant External System Interfaces", - "props": [ - { - "name": "label", - "value": "SA-5(2)" - }, - { - "name": "sort-id", - "value": "sa-05.02" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sa-4.2", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sa-5.3", - "class": "SP800-53-enhancement", - "title": "High-level Design", - "props": [ - { - "name": "label", - "value": "SA-5(3)" - }, - { - "name": "sort-id", - "value": "sa-05.03" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sa-4.2", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sa-5.4", - "class": "SP800-53-enhancement", - "title": "Low-level Design", - "props": [ - { - "name": "label", - "value": "SA-5(4)" - }, - { - "name": "sort-id", - "value": "sa-05.04" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sa-4.2", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sa-5.5", - "class": "SP800-53-enhancement", - "title": "Source Code", - "props": [ - { - "name": "label", - "value": "SA-5(5)" - }, - { - "name": "sort-id", - "value": "sa-05.05" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sa-4.2", - "rel": "incorporated-into" - } - ] - } - ] - }, - { - "id": "sa-6", - "class": "SP800-53", - "title": "Software Usage Restrictions", - "props": [ - { - "name": "label", - "value": "SA-6" - }, - { - "name": "sort-id", - "value": "sa-06" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#cm-10", - "rel": "incorporated-into" - }, - { - "href": "#si-7", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sa-7", - "class": "SP800-53", - "title": "User-installed Software", - "props": [ - { - "name": "label", - "value": "SA-7" - }, - { - "name": "sort-id", - "value": "sa-07" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#cm-11", - "rel": "incorporated-into" - }, - { - "href": "#si-7", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sa-8", - "class": "SP800-53", - "title": "Security Engineering Principles", - "props": [ - { - "name": "label", - "value": "SA-8" - }, - { - "name": "sort-id", - "value": "sa-08" - } - ], - "links": [ - { - "href": "#21b1ed35-56d2-40a8-bdfe-b461fffe322f", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sa-8_smt", - "name": "statement", - "prose": "The organization applies information system security engineering principles in the specification, design, development, implementation, and modification of the information system." - }, - { - "id": "sa-8_gdn", - "name": "guidance", - "prose": "Organizations apply security engineering principles primarily to new development information systems or systems undergoing major upgrades. For legacy systems, organizations apply security engineering principles to system upgrades and modifications to the extent feasible, given the current state of hardware, software, and firmware within those systems. Security engineering principles include, for example: (i) developing layered protections; (ii) establishing sound security policy, architecture, and controls as the foundation for design; (iii) incorporating security requirements into the system development life cycle; (iv) delineating physical and logical security boundaries; (v) ensuring that system developers are trained on how to build secure software; (vi) tailoring security controls to meet organizational and operational needs; (vii) performing threat modeling to identify use cases, threat agents, attack vectors, and attack patterns as well as compensating controls and design patterns needed to mitigate risk; and (viii) reducing risk to acceptable levels, thus enabling informed risk management decisions.", - "links": [ - { - "href": "#pm-7", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-17", - "rel": "related" - }, - { - "href": "#sc-2", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - } - ] - }, - { - "id": "sa-8_obj", - "name": "objective", - "prose": "Determine if the organization applies information system security engineering principles in:", - "parts": [ - { - "id": "sa-8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-8[1]" - } - ], - "prose": "the specification of the information system;" - }, - { - "id": "sa-8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-8[2]" - } - ], - "prose": "the design of the information system;" - }, - { - "id": "sa-8_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-8[3]" - } - ], - "prose": "the development of the information system;" - }, - { - "id": "sa-8_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-8[4]" - } - ], - "prose": "the implementation of the information system; and" - }, - { - "id": "sa-8_obj.5", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-8[5]" - } - ], - "prose": "the modification of the information system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing security engineering principles used in the specification, design, development, implementation, and modification of the information system\n\ninformation system design documentation\n\ninformation security requirements and specifications for the information system\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with responsibility for determining information system security requirements\n\norganizational personnel with information system specification, design, development, implementation, and modification responsibilities\n\ninformation system developers\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for applying security engineering principles in information system specification, design, development, implementation, and modification\n\nautomated mechanisms supporting the application of security engineering principles in information system specification, design, development, implementation, and modification" - } - ] - } - ] - }, - { - "id": "sa-9", - "class": "SP800-53", - "title": "External Information System Services", - "params": [ - { - "id": "sa-9_prm_1", - "label": "organization-defined security controls" - }, - { - "id": "sa-9_prm_2", - "label": "organization-defined processes, methods, and techniques" - } - ], - "props": [ - { - "name": "label", - "value": "SA-9" - }, - { - "name": "sort-id", - "value": "sa-09" - } - ], - "links": [ - { - "href": "#0c775bc3-bfc3-42c7-a382-88949f503171", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sa-9_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sa-9_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Requires that providers of external information system services comply with organizational information security requirements and employ {{ insert: param, sa-9_prm_1 }} in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance;" - }, - { - "id": "sa-9_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Defines and documents government oversight and user roles and responsibilities with regard to external information system services; and" - }, - { - "id": "sa-9_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Employs {{ insert: param, sa-9_prm_2 }} to monitor security control compliance by external service providers on an ongoing basis." - } - ] - }, - { - "id": "sa-9_gdn", - "name": "guidance", - "prose": "External information system services are services that are implemented outside of the authorization boundaries of organizational information systems. This includes services that are used by, but not a part of, organizational information systems. FISMA and OMB policy require that organizations using external service providers that are processing, storing, or transmitting federal information or operating information systems on behalf of the federal government ensure that such providers meet the same security requirements that federal agencies are required to meet. Organizations establish relationships with external service providers in a variety of ways including, for example, through joint ventures, business partnerships, contracts, interagency agreements, lines of business arrangements, licensing agreements, and supply chain exchanges. The responsibility for managing risks from the use of external information system services remains with authorizing officials. For services external to organizations, a chain of trust requires that organizations establish and retain a level of confidence that each participating provider in the potentially complex consumer-provider relationship provides adequate protection for the services rendered. The extent and nature of this chain of trust varies based on the relationships between organizations and the external providers. Organizations document the basis for trust relationships so the relationships can be monitored over time. External information system services documentation includes government, service providers, end user security roles and responsibilities, and service-level agreements. Service-level agreements define expectations of performance for security controls, describe measurable outcomes, and identify remedies and response requirements for identified instances of noncompliance.", - "links": [ - { - "href": "#ca-3", - "rel": "related" - }, - { - "href": "#ir-7", - "rel": "related" - }, - { - "href": "#ps-7", - "rel": "related" - } - ] - }, - { - "id": "sa-9_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-9.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(a)" - } - ], - "parts": [ - { - "id": "sa-9.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(a)[1]" - } - ], - "prose": "defines security controls to be employed by providers of external information system services;" - }, - { - "id": "sa-9.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(a)[2]" - } - ], - "prose": "requires that providers of external information system services comply with organizational information security requirements;" - }, - { - "id": "sa-9.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(a)[3]" - } - ], - "prose": "requires that providers of external information system services employ organization-defined security controls in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance;" - } - ] - }, - { - "id": "sa-9.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(b)" - } - ], - "parts": [ - { - "id": "sa-9.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(b)[1]" - } - ], - "prose": "defines and documents government oversight with regard to external information system services;" - }, - { - "id": "sa-9.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(b)[2]" - } - ], - "prose": "defines and documents user roles and responsibilities with regard to external information system services;" - } - ] - }, - { - "id": "sa-9.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(c)" - } - ], - "parts": [ - { - "id": "sa-9.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(c)[1]" - } - ], - "prose": "defines processes, methods, and techniques to be employed to monitor security control compliance by external service providers; and" - }, - { - "id": "sa-9.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(c)[2]" - } - ], - "prose": "employs organization-defined processes, methods, and techniques to monitor security control compliance by external service providers on an ongoing basis." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing external information system services\n\nprocedures addressing methods and techniques for monitoring security control compliance by external service providers of information system services\n\nacquisition contracts, service-level agreements\n\norganizational security requirements and security specifications for external provider services\n\nsecurity control assessment evidence from external providers of information system services\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\nexternal providers of information system services\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring security control compliance by external service providers on an ongoing basis\n\nautomated mechanisms for monitoring security control compliance by external service providers on an ongoing basis" - } - ] - } - ], - "controls": [ - { - "id": "sa-9.1", - "class": "SP800-53-enhancement", - "title": "Risk Assessments / Organizational Approvals", - "params": [ - { - "id": "sa-9.1_prm_1", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "SA-9(1)" - }, - { - "name": "sort-id", - "value": "sa-09.01" - } - ], - "parts": [ - { - "id": "sa-9.1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sa-9.1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Conducts an organizational assessment of risk prior to the acquisition or outsourcing of dedicated information security services; and" - }, - { - "id": "sa-9.1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Ensures that the acquisition or outsourcing of dedicated information security services is approved by {{ insert: param, sa-9.1_prm_1 }}." - } - ] - }, - { - "id": "sa-9.1_gdn", - "name": "guidance", - "prose": "Dedicated information security services include, for example, incident monitoring, analysis and response, operation of information security-related devices such as firewalls, or key management services.", - "links": [ - { - "href": "#ca-6", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - } - ] - }, - { - "id": "sa-9.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-9.1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(1)(a)" - } - ], - "prose": "conducts an organizational assessment of risk prior to the acquisition or outsourcing of dedicated information security services;", - "links": [ - { - "href": "#sa-9.1_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "sa-9.1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(1)(b)" - } - ], - "parts": [ - { - "id": "sa-9.1.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(1)(b)[1]" - } - ], - "prose": "defines personnel or roles designated to approve the acquisition or outsourcing of dedicated information security services; and" - }, - { - "id": "sa-9.1.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(1)(b)[2]" - } - ], - "prose": "ensures that the acquisition or outsourcing of dedicated information security services is approved by organization-defined personnel or roles." - } - ], - "links": [ - { - "href": "#sa-9.1_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing external information system services\n\nacquisition documentation\n\nacquisition contracts for the information system, system component, or information system service\n\nrisk assessment reports\n\napproval records for acquisition or outsourcing of dedicated information security services\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information system security responsibilities\n\nexternal providers of information system services\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for conducting a risk assessment prior to acquiring or outsourcing dedicated information security services\n\norganizational processes for approving the outsourcing of dedicated information security services\n\nautomated mechanisms supporting and/or implementing risk assessment\n\nautomated mechanisms supporting and/or implementing approval processes" - } - ] - } - ] - }, - { - "id": "sa-9.2", - "class": "SP800-53-enhancement", - "title": "Identification of Functions / Ports / Protocols / Services", - "params": [ - { - "id": "sa-9.2_prm_1", - "label": "organization-defined external information system services" - } - ], - "props": [ - { - "name": "label", - "value": "SA-9(2)" - }, - { - "name": "sort-id", - "value": "sa-09.02" - } - ], - "parts": [ - { - "id": "sa-9.2_smt", - "name": "statement", - "prose": "The organization requires providers of {{ insert: param, sa-9.2_prm_1 }} to identify the functions, ports, protocols, and other services required for the use of such services." - }, - { - "id": "sa-9.2_gdn", - "name": "guidance", - "prose": "Information from external service providers regarding the specific functions, ports, protocols, and services used in the provision of such services can be particularly useful when the need arises to understand the trade-offs involved in restricting certain functions/services or blocking certain ports/protocols.", - "links": [ - { - "href": "#cm-7", - "rel": "related" - } - ] - }, - { - "id": "sa-9.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-9.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(2)[1]" - } - ], - "prose": "defines external information system services for which providers of such services are to identify the functions, ports, protocols, and other services required for the use of such services;" - }, - { - "id": "sa-9.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(2)[2]" - } - ], - "prose": "requires providers of organization-defined external information system services to identify:", - "parts": [ - { - "id": "sa-9.2_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(2)[2][a]" - } - ], - "prose": "the functions required for the use of such services;" - }, - { - "id": "sa-9.2_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(2)[2][b]" - } - ], - "prose": "the ports required for the use of such services;" - }, - { - "id": "sa-9.2_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(2)[2][c]" - } - ], - "prose": "the protocols required for the use of such services; and" - }, - { - "id": "sa-9.2_obj.2.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(2)[2][d]" - } - ], - "prose": "the other services required for the use of such services." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing external information system services\n\nacquisition contracts for the information system, system component, or information system service\n\nacquisition documentation\n\nsolicitation documentation, service-level agreements\n\norganizational security requirements and security specifications for external service providers\n\nlist of required functions, ports, protocols, and other services\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nexternal providers of information system services" - } - ] - } - ] - }, - { - "id": "sa-9.3", - "class": "SP800-53-enhancement", - "title": "Establish / Maintain Trust Relationship with Providers", - "params": [ - { - "id": "sa-9.3_prm_1", - "label": "organization-defined security requirements, properties, factors, or conditions defining acceptable trust relationships" - } - ], - "props": [ - { - "name": "label", - "value": "SA-9(3)" - }, - { - "name": "sort-id", - "value": "sa-09.03" - } - ], - "parts": [ - { - "id": "sa-9.3_smt", - "name": "statement", - "prose": "The organization establishes, documents, and maintains trust relationships with external service providers based on {{ insert: param, sa-9.3_prm_1 }}." - }, - { - "id": "sa-9.3_gdn", - "name": "guidance", - "prose": "The degree of confidence that the risk from using external services is at an acceptable level depends on the trust that organizations place in the external providers, individually or in combination. Trust relationships can help organization to gain increased levels of confidence that participating service providers are providing adequate protection for the services rendered. Such relationships can be complicated due to the number of potential entities participating in the consumer-provider interactions, subordinate relationships and levels of trust, and the types of interactions between the parties. In some cases, the degree of trust is based on the amount of direct control organizations are able to exert on external service providers with regard to employment of security controls necessary for the protection of the service/information and the evidence brought forth as to the effectiveness of those controls. The level of control is typically established by the terms and conditions of the contracts or service-level agreements and can range from extensive control (e.g., negotiating contracts or agreements that specify security requirements for the providers) to very limited control (e.g., using contracts or service-level agreements to obtain commodity services such as commercial telecommunications services). In other cases, levels of trust are based on factors that convince organizations that required security controls have been employed and that determinations of control effectiveness exist. For example, separately authorized external information system services provided to organizations through well-established business relationships may provide degrees of trust in such services within the tolerable risk range of the organizations using the services. External service providers may also outsource selected services to other external entities, making the trust relationship more difficult and complicated to manage. Depending on the nature of the services, organizations may find it very difficult to place significant trust in external providers. This is not due to any inherent untrustworthiness on the part of providers, but to the intrinsic level of risk in the services." - }, - { - "id": "sa-9.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-9.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(3)[1]" - } - ], - "prose": "defines requirements, properties, factors, or conditions defining acceptable trust relationships;" - }, - { - "id": "sa-9.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(3)[2]" - } - ], - "prose": "based on organization-defined requirements, properties, factors, or conditions defining acceptable trust relationships:", - "parts": [ - { - "id": "sa-9.3_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(3)[2][a]" - } - ], - "prose": "establishes trust relationships with external service providers;" - }, - { - "id": "sa-9.3_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(3)[2][b]" - } - ], - "prose": "documents trust relationships with external service providers; and" - }, - { - "id": "sa-9.3_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(3)[2][c]" - } - ], - "prose": "maintains trust relationships with external service providers." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing external information system services\n\nacquisition contracts for the information system, system component, or information system service\n\nacquisition documentation\n\nsolicitation documentation\n\nservice-level agreements\n\norganizational security requirements, properties, factors, or conditions defining acceptable trust relationships\n\ndocumentation of trust relationships with external service providers\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nexternal providers of information system services" - } - ] - } - ] - }, - { - "id": "sa-9.4", - "class": "SP800-53-enhancement", - "title": "Consistent Interests of Consumers and Providers", - "params": [ - { - "id": "sa-9.4_prm_1", - "label": "organization-defined security safeguards" - }, - { - "id": "sa-9.4_prm_2", - "label": "organization-defined external service providers" - } - ], - "props": [ - { - "name": "label", - "value": "SA-9(4)" - }, - { - "name": "sort-id", - "value": "sa-09.04" - } - ], - "parts": [ - { - "id": "sa-9.4_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, sa-9.4_prm_1 }} to ensure that the interests of {{ insert: param, sa-9.4_prm_2 }} are consistent with and reflect organizational interests." - }, - { - "id": "sa-9.4_gdn", - "name": "guidance", - "prose": "As organizations increasingly use external service providers, the possibility exists that the interests of the service providers may diverge from organizational interests. In such situations, simply having the correct technical, procedural, or operational safeguards in place may not be sufficient if the service providers that implement and control those safeguards are not operating in a manner consistent with the interests of the consuming organizations. Possible actions that organizations might take to address such concerns include, for example, requiring background checks for selected service provider personnel, examining ownership records, employing only trustworthy service providers (i.e., providers with which organizations have had positive experiences), and conducting periodic/unscheduled visits to service provider facilities." - }, - { - "id": "sa-9.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-9.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(4)[1]" - } - ], - "prose": "defines external service providers whose interests are to be consistent with and reflect organizational interests;" - }, - { - "id": "sa-9.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(4)[2]" - } - ], - "prose": "defines security safeguards to be employed to ensure that the interests of organization-defined external service providers are consistent with and reflect organizational interests; and" - }, - { - "id": "sa-9.4_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(4)[3]" - } - ], - "prose": "employs organization-defined security safeguards to ensure that the interests of organization-defined external service providers are consistent with and reflect organizational interests." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing external information system services\n\nacquisition contracts for the information system, system component, or information system service\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\norganizational security requirements/safeguards for external service providers\n\npersonnel security policies for external service providers\n\nassessments performed on external service providers\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nexternal providers of information system services" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for defining and employing safeguards to ensure consistent interests with external service providers\n\nautomated mechanisms supporting and/or implementing safeguards to ensure consistent interests with external service providers" - } - ] - } - ] - }, - { - "id": "sa-9.5", - "class": "SP800-53-enhancement", - "title": "Processing, Storage, and Service Location", - "params": [ - { - "id": "sa-9.5_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "information processing", - "information/data", - "information system services" - ] - } - }, - { - "id": "sa-9.5_prm_2", - "label": "organization-defined locations" - }, - { - "id": "sa-9.5_prm_3", - "label": "organization-defined requirements or conditions" - } - ], - "props": [ - { - "name": "label", - "value": "SA-9(5)" - }, - { - "name": "sort-id", - "value": "sa-09.05" - } - ], - "parts": [ - { - "id": "sa-9.5_smt", - "name": "statement", - "prose": "The organization restricts the location of {{ insert: param, sa-9.5_prm_1 }} to {{ insert: param, sa-9.5_prm_2 }} based on {{ insert: param, sa-9.5_prm_3 }}." - }, - { - "id": "sa-9.5_gdn", - "name": "guidance", - "prose": "The location of information processing, information/data storage, or information system services that are critical to organizations can have a direct impact on the ability of those organizations to successfully execute their missions/business functions. This situation exists when external providers control the location of processing, storage or services. The criteria external providers use for the selection of processing, storage, or service locations may be different from organizational criteria. For example, organizations may want to ensure that data/information storage locations are restricted to certain locations to facilitate incident response activities (e.g., forensic analyses, after-the-fact investigations) in case of information security breaches/compromises. Such incident response activities may be adversely affected by the governing laws or protocols in the locations where processing and storage occur and/or the locations from which information system services emanate." - }, - { - "id": "sa-9.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-9.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(5)[1]" - } - ], - "prose": "defines locations where organization-defined information processing, information/data, and/or information system services are to be restricted;" - }, - { - "id": "sa-9.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(5)[2]" - } - ], - "prose": "defines requirements or conditions to restrict the location of information processing, information/data, and/or information system services;" - }, - { - "id": "sa-9.5_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(5)[3]" - } - ], - "prose": "restricts the location of one or more of the following to organization-defined locations based on organization-defined requirements or conditions:", - "parts": [ - { - "id": "sa-9.5_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(5)[3][a]" - } - ], - "prose": "information processing;" - }, - { - "id": "sa-9.5_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(5)[3][b]" - } - ], - "prose": "information/data; and/or" - }, - { - "id": "sa-9.5_obj.3.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-9(5)[3][c]" - } - ], - "prose": "information services." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing external information system services\n\nacquisition contracts for the information system, system component, or information system service\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nrestricted locations for information processing\n\ninformation/data and/or information system services\n\ninformation processing, information/data, and/or information system services to be maintained in restricted locations\n\norganizational security requirements or conditions for external providers\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nexternal providers of information system services" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for defining requirements to restrict locations of information processing, information/data, or information services\n\norganizational processes for ensuring the location is restricted in accordance with requirements or conditions" - } - ] - } - ] - } - ] - }, - { - "id": "sa-10", - "class": "SP800-53", - "title": "Developer Configuration Management", - "params": [ - { - "id": "sa-10_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "design", - "development", - "implementation", - "operation" - ] - } - }, - { - "id": "sa-10_prm_2", - "label": "organization-defined configuration items under configuration management" - }, - { - "id": "sa-10_prm_3", - "label": "organization-defined personnel" - } - ], - "props": [ - { - "name": "label", - "value": "SA-10" - }, - { - "name": "sort-id", - "value": "sa-10" - } - ], - "links": [ - { - "href": "#080f8068-5e3e-435e-9790-d22ba4722693", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sa-10_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to:", - "parts": [ - { - "id": "sa-10_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Perform configuration management during system, component, or service {{ insert: param, sa-10_prm_1 }};" - }, - { - "id": "sa-10_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Document, manage, and control the integrity of changes to {{ insert: param, sa-10_prm_2 }};" - }, - { - "id": "sa-10_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Implement only organization-approved changes to the system, component, or service;" - }, - { - "id": "sa-10_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Document approved changes to the system, component, or service and the potential security impacts of such changes; and" - }, - { - "id": "sa-10_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Track security flaws and flaw resolution within the system, component, or service and report findings to {{ insert: param, sa-10_prm_3 }}." - } - ] - }, - { - "id": "sa-10_gdn", - "name": "guidance", - "prose": "This control also applies to organizations conducting internal information systems development and integration. Organizations consider the quality and completeness of the configuration management activities conducted by developers as evidence of applying effective security safeguards. Safeguards include, for example, protecting from unauthorized modification or destruction, the master copies of all material used to generate security-relevant portions of the system hardware, software, and firmware. Maintaining the integrity of changes to the information system, information system component, or information system service requires configuration control throughout the system development life cycle to track authorized changes and prevent unauthorized changes. Configuration items that are placed under configuration management (if existence/use is required by other security controls) include: the formal model; the functional, high-level, and low-level design specifications; other design data; implementation documentation; source code and hardware schematics; the running version of the object code; tools for comparing new versions of security-relevant hardware descriptions and software/firmware source code with previous versions; and test fixtures and documentation. Depending on the mission/business needs of organizations and the nature of the contractual relationships in place, developers may provide configuration management support during the operations and maintenance phases of the life cycle.", - "links": [ - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#cm-9", - "rel": "related" - }, - { - "href": "#sa-12", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - } - ] - }, - { - "id": "sa-10_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-10.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(a)" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to perform configuration management during one or more of the following:", - "parts": [ - { - "id": "sa-10.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(a)[1]" - } - ], - "prose": "system, component, or service design;" - }, - { - "id": "sa-10.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(a)[2]" - } - ], - "prose": "system, component, or service development;" - }, - { - "id": "sa-10.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(a)[3]" - } - ], - "prose": "system, component, or service implementation; and/or" - }, - { - "id": "sa-10.a_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(a)[4]" - } - ], - "prose": "system, component, or service operation;" - } - ] - }, - { - "id": "sa-10.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(b)" - } - ], - "parts": [ - { - "id": "sa-10.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(b)[1]" - } - ], - "prose": "defines configuration items to be placed under configuration management;" - }, - { - "id": "sa-10.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(b)[2]" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to:", - "parts": [ - { - "id": "sa-10.b_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(b)[2][a]" - } - ], - "prose": "document the integrity of changes to organization-defined items under configuration management;" - }, - { - "id": "sa-10.b_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(b)[2][b]" - } - ], - "prose": "manage the integrity of changes to organization-defined items under configuration management;" - }, - { - "id": "sa-10.b_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(b)[2][c]" - } - ], - "prose": "control the integrity of changes to organization-defined items under configuration management;" - } - ] - } - ] - }, - { - "id": "sa-10.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(c)" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to implement only organization-approved changes to the system, component, or service;" - }, - { - "id": "sa-10.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(d)" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to document:", - "parts": [ - { - "id": "sa-10.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(d)[1]" - } - ], - "prose": "approved changes to the system, component, or service;" - }, - { - "id": "sa-10.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(d)[2]" - } - ], - "prose": "the potential security impacts of such changes;" - } - ] - }, - { - "id": "sa-10.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(e)" - } - ], - "parts": [ - { - "id": "sa-10.e_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(e)[1]" - } - ], - "prose": "defines personnel to whom findings, resulting from security flaws and flaw resolution tracked within the system, component, or service, are to be reported;" - }, - { - "id": "sa-10.e_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(e)[2]" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to:", - "parts": [ - { - "id": "sa-10.e_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(e)[2][a]" - } - ], - "prose": "track security flaws within the system, component, or service;" - }, - { - "id": "sa-10.e_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(e)[2][b]" - } - ], - "prose": "track security flaw resolution within the system, component, or service; and" - }, - { - "id": "sa-10.e_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(e)[2][c]" - } - ], - "prose": "report findings to organization-defined personnel." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing system developer configuration management\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nsystem developer configuration management plan\n\nsecurity flaw and flaw resolution tracking records\n\nsystem change authorization records\n\nchange control records\n\nconfiguration management records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with configuration management responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring developer configuration management\n\nautomated mechanisms supporting and/or implementing the monitoring of developer configuration management" - } - ] - } - ], - "controls": [ - { - "id": "sa-10.1", - "class": "SP800-53-enhancement", - "title": "Software / Firmware Integrity Verification", - "props": [ - { - "name": "label", - "value": "SA-10(1)" - }, - { - "name": "sort-id", - "value": "sa-10.01" - } - ], - "parts": [ - { - "id": "sa-10.1_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to enable integrity verification of software and firmware components." - }, - { - "id": "sa-10.1_gdn", - "name": "guidance", - "prose": "This control enhancement allows organizations to detect unauthorized changes to software and firmware components through the use of tools, techniques, and/or mechanisms provided by developers. Integrity checking mechanisms can also address counterfeiting of software and firmware components. Organizations verify the integrity of software and firmware components, for example, through secure one-way hashes provided by developers. Delivered software and firmware components also include any updates to such components.", - "links": [ - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "sa-10.1_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to enable integrity verification of software and firmware components." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing system developer configuration management\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system\n\nsystem component, or information system service\n\nsystem developer configuration management plan\n\nsoftware and firmware integrity verification records\n\nsystem change authorization records\n\nchange control records\n\nconfiguration management records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with configuration management responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring developer configuration management\n\nautomated mechanisms supporting and/or implementing the monitoring of developer configuration management" - } - ] - } - ] - }, - { - "id": "sa-10.2", - "class": "SP800-53-enhancement", - "title": "Alternative Configuration Management Processes", - "props": [ - { - "name": "label", - "value": "SA-10(2)" - }, - { - "name": "sort-id", - "value": "sa-10.02" - } - ], - "parts": [ - { - "id": "sa-10.2_smt", - "name": "statement", - "prose": "The organization provides an alternate configuration management process using organizational personnel in the absence of a dedicated developer configuration management team." - }, - { - "id": "sa-10.2_gdn", - "name": "guidance", - "prose": "Alternate configuration management processes may be required, for example, when organizations use commercial off-the-shelf (COTS) information technology products. Alternate configuration management processes include organizational personnel that: (i) are responsible for reviewing/approving proposed changes to information systems, system components, and information system services; and (ii) conduct security impact analyses prior to the implementation of any changes to systems, components, or services (e.g., a configuration control board that considers security impacts of changes during development and includes representatives of both the organization and the developer, when applicable)." - }, - { - "id": "sa-10.2_obj", - "name": "objective", - "prose": "Determine if the organization provides an alternative configuration management process with organizational personnel in the absence of a dedicated developer configuration management team." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing system developer configuration management\n\nprocedures addressing configuration management\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system\n\nsystem component, or information system service\n\nsystem developer configuration management plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with configuration management responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring developer configuration management\n\nautomated mechanisms supporting and/or implementing the monitoring of developer configuration management" - } - ] - } - ] - }, - { - "id": "sa-10.3", - "class": "SP800-53-enhancement", - "title": "Hardware Integrity Verification", - "props": [ - { - "name": "label", - "value": "SA-10(3)" - }, - { - "name": "sort-id", - "value": "sa-10.03" - } - ], - "parts": [ - { - "id": "sa-10.3_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to enable integrity verification of hardware components." - }, - { - "id": "sa-10.3_gdn", - "name": "guidance", - "prose": "This control enhancement allows organizations to detect unauthorized changes to hardware components through the use of tools, techniques, and/or mechanisms provided by developers. Organizations verify the integrity of hardware components, for example, with hard-to-copy labels and verifiable serial numbers provided by developers, and by requiring the implementation of anti-tamper technologies. Delivered hardware components also include updates to such components.", - "links": [ - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "sa-10.3_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to enable integrity verification of hardware components." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing system developer configuration management\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nsystem developer configuration management plan\n\nhardware integrity verification records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with configuration management responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring developer configuration management\n\nautomated mechanisms supporting and/or implementing the monitoring of developer configuration management" - } - ] - } - ] - }, - { - "id": "sa-10.4", - "class": "SP800-53-enhancement", - "title": "Trusted Generation", - "props": [ - { - "name": "label", - "value": "SA-10(4)" - }, - { - "name": "sort-id", - "value": "sa-10.04" - } - ], - "parts": [ - { - "id": "sa-10.4_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to employ tools for comparing newly generated versions of security-relevant hardware descriptions and software/firmware source and object code with previous versions." - }, - { - "id": "sa-10.4_gdn", - "name": "guidance", - "prose": "This control enhancement addresses changes to hardware, software, and firmware components between versions during development. In contrast, SA-10 (1) and SA-10 (3) allow organizations to detect unauthorized changes to hardware, software, and firmware components through the use of tools, techniques, and/or mechanisms provided by developers." - }, - { - "id": "sa-10.4_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to employ tools for comparing newly generated versions of:", - "parts": [ - { - "id": "sa-10.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(4)[1]" - } - ], - "prose": "security-relevant hardware descriptions with previous versions; and" - }, - { - "id": "sa-10.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-10(4)[2]" - } - ], - "prose": "software/firmware source and object code with previous versions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing system developer configuration management\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nsystem developer configuration management plan\n\nchange control records\n\nconfiguration management records\n\nconfiguration control audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with configuration management responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring developer configuration management\n\nautomated mechanisms supporting and/or implementing the monitoring of developer configuration management" - } - ] - } - ] - }, - { - "id": "sa-10.5", - "class": "SP800-53-enhancement", - "title": "Mapping Integrity for Version Control", - "props": [ - { - "name": "label", - "value": "SA-10(5)" - }, - { - "name": "sort-id", - "value": "sa-10.05" - } - ], - "parts": [ - { - "id": "sa-10.5_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to maintain the integrity of the mapping between the master build data (hardware drawings and software/firmware code) describing the current version of security-relevant hardware, software, and firmware and the on-site master copy of the data for the current version." - }, - { - "id": "sa-10.5_gdn", - "name": "guidance", - "prose": "This control enhancement addresses changes to hardware, software, and firmware components during initial development and during system life cycle updates. Maintaining the integrity between the master copies of security-relevant hardware, software, and firmware (including designs and source code) and the equivalent data in master copies on-site in operational environments is essential to ensure the availability of organizational information systems supporting critical missions and/or business functions." - }, - { - "id": "sa-10.5_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to maintain the integrity of the mapping between the master build data (hardware drawings and software/firmware code) describing the current version of security-relevant hardware, software, and firmware and the on-site master copy of the data for the current version." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing system developer configuration management\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nsystem developer configuration management plan\n\nchange control records\n\nconfiguration management records\n\nversion control change/update records\n\nintegrity verification records between master copies of security-relevant hardware, software, and firmware (including designs and source code)\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with configuration management responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring developer configuration management\n\nautomated mechanisms supporting and/or implementing the monitoring of developer configuration management" - } - ] - } - ] - }, - { - "id": "sa-10.6", - "class": "SP800-53-enhancement", - "title": "Trusted Distribution", - "props": [ - { - "name": "label", - "value": "SA-10(6)" - }, - { - "name": "sort-id", - "value": "sa-10.06" - } - ], - "parts": [ - { - "id": "sa-10.6_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to execute procedures for ensuring that security-relevant hardware, software, and firmware updates distributed to the organization are exactly as specified by the master copies." - }, - { - "id": "sa-10.6_gdn", - "name": "guidance", - "prose": "The trusted distribution of security-relevant hardware, software, and firmware updates helps to ensure that such updates are faithful representations of the master copies maintained by the developer and have not been tampered with during distribution." - }, - { - "id": "sa-10.6_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to execute procedures for ensuring that security-relevant hardware, software, and firmware updates distributed to the organization are exactly as specified by the master copies." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing system developer configuration management\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system\n\nsystem component, or information system service\n\nsystem developer configuration management plan\n\nchange control records\n\nconfiguration management records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with configuration management responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring developer configuration management\n\nautomated mechanisms supporting and/or implementing the monitoring of developer configuration management" - } - ] - } - ] - } - ] - }, - { - "id": "sa-11", - "class": "SP800-53", - "title": "Developer Security Testing and Evaluation", - "params": [ - { - "id": "sa-11_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "unit", - "integration", - "system", - "regression" - ] - } - }, - { - "id": "sa-11_prm_2", - "label": "organization-defined depth and coverage" - } - ], - "props": [ - { - "name": "label", - "value": "SA-11" - }, - { - "name": "sort-id", - "value": "sa-11" - } - ], - "links": [ - { - "href": "#1737a687-52fb-4008-b900-cbfa836f7b65", - "rel": "reference" - }, - { - "href": "#cd4cf751-3312-4a55-b1a9-fad2f1db9119", - "rel": "reference" - }, - { - "href": "#275cc052-0f7f-423c-bdb6-ed503dc36228", - "rel": "reference" - }, - { - "href": "#15522e92-9192-463d-9646-6a01982db8ca", - "rel": "reference" - }, - { - "href": "#0931209f-00ae-4132-b92c-bc645847e8f9", - "rel": "reference" - }, - { - "href": "#4ef539ba-b767-4666-b0d3-168c53005fa3", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sa-11_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to:", - "parts": [ - { - "id": "sa-11_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Create and implement a security assessment plan;" - }, - { - "id": "sa-11_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Perform {{ insert: param, sa-11_prm_1 }} testing/evaluation at {{ insert: param, sa-11_prm_2 }};" - }, - { - "id": "sa-11_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Produce evidence of the execution of the security assessment plan and the results of the security testing/evaluation;" - }, - { - "id": "sa-11_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Implement a verifiable flaw remediation process; and" - }, - { - "id": "sa-11_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Correct flaws identified during security testing/evaluation." - } - ] - }, - { - "id": "sa-11_gdn", - "name": "guidance", - "prose": "Developmental security testing/evaluation occurs at all post-design phases of the system development life cycle. Such testing/evaluation confirms that the required security controls are implemented correctly, operating as intended, enforcing the desired security policy, and meeting established security requirements. Security properties of information systems may be affected by the interconnection of system components or changes to those components. These interconnections or changes (e.g., upgrading or replacing applications and operating systems) may adversely affect previously implemented security controls. This control provides additional types of security testing/evaluation that developers can conduct to reduce or eliminate potential flaws. Testing custom software applications may require approaches such as static analysis, dynamic analysis, binary analysis, or a hybrid of the three approaches. Developers can employ these analysis approaches in a variety of tools (e.g., web-based application scanners, static analysis tools, binary analyzers) and in source code reviews. Security assessment plans provide the specific activities that developers plan to carry out including the types of analyses, testing, evaluation, and reviews of software and firmware components, the degree of rigor to be applied, and the types of artifacts produced during those processes. The depth of security testing/evaluation refers to the rigor and level of detail associated with the assessment process (e.g., black box, gray box, or white box testing). The coverage of security testing/evaluation refers to the scope (i.e., number and type) of the artifacts included in the assessment process. Contracts specify the acceptance criteria for security assessment plans, flaw remediation processes, and the evidence that the plans/processes have been diligently applied. Methods for reviewing and protecting assessment plans, evidence, and documentation are commensurate with the security category or classification level of the information system. Contracts may specify documentation protection requirements.", - "links": [ - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - } - ] - }, - { - "id": "sa-11_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-11.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(a)" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to create and implement a security plan;" - }, - { - "id": "sa-11.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(b)" - } - ], - "parts": [ - { - "id": "sa-11.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(b)[1]" - } - ], - "prose": "defines the depth of testing/evaluation to be performed by the developer of the information system, system component, or information system service;" - }, - { - "id": "sa-11.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(b)[2]" - } - ], - "prose": "defines the coverage of testing/evaluation to be performed by the developer of the information system, system component, or information system service;" - }, - { - "id": "sa-11.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(b)[3]" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to perform one or more of the following testing/evaluation at the organization-defined depth and coverage:", - "parts": [ - { - "id": "sa-11.b_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(b)[3][a]" - } - ], - "prose": "unit testing/evaluation;" - }, - { - "id": "sa-11.b_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(b)[3][b]" - } - ], - "prose": "integration testing/evaluation;" - }, - { - "id": "sa-11.b_obj.3.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(b)[3][c]" - } - ], - "prose": "system testing/evaluation; and/or" - }, - { - "id": "sa-11.b_obj.3.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(b)[3][d]" - } - ], - "prose": "regression testing/evaluation;" - } - ] - } - ] - }, - { - "id": "sa-11.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(c)" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to produce evidence of:", - "parts": [ - { - "id": "sa-11.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(c)[1]" - } - ], - "prose": "the execution of the security assessment plan;" - }, - { - "id": "sa-11.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(c)[2]" - } - ], - "prose": "the results of the security testing/evaluation;" - } - ] - }, - { - "id": "sa-11.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(d)" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to implement a verifiable flaw remediation process; and" - }, - { - "id": "sa-11.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(e)" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to correct flaws identified during security testing/evaluation." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing system developer security testing\n\nprocedures addressing flaw remediation\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nsystem developer security test plans\n\nrecords of developer security testing results for the information system, system component, or information system service\n\nsecurity flaw and remediation tracking records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with developer security testing responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring developer security testing and evaluation\n\nautomated mechanisms supporting and/or implementing the monitoring of developer security testing and evaluation" - } - ] - } - ], - "controls": [ - { - "id": "sa-11.1", - "class": "SP800-53-enhancement", - "title": "Static Code Analysis", - "props": [ - { - "name": "label", - "value": "SA-11(1)" - }, - { - "name": "sort-id", - "value": "sa-11.01" - } - ], - "parts": [ - { - "id": "sa-11.1_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to employ static code analysis tools to identify common flaws and document the results of the analysis." - }, - { - "id": "sa-11.1_gdn", - "name": "guidance", - "prose": "Static code analysis provides a technology and methodology for security reviews. Such analysis can be used to identify security vulnerabilities and enforce security coding practices. Static code analysis is most effective when used early in the development process, when each code change can be automatically scanned for potential weaknesses. Static analysis can provide clear remediation guidance along with defects to enable developers to fix such defects. Evidence of correct implementation of static analysis can include, for example, aggregate defect density for critical defect types, evidence that defects were inspected by developers or security professionals, and evidence that defects were fixed. An excessively high density of ignored findings (commonly referred to as ignored or false positives) indicates a potential problem with the analysis process or tool. In such cases, organizations weigh the validity of the evidence against evidence from other sources." - }, - { - "id": "sa-11.1_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to employ static code analysis tools to identify common flaws and document the results of the analysis." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing system developer security testing\n\nprocedures addressing flaw remediation\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nsystem developer security test plans\n\nsystem developer security testing results\n\nsecurity flaw and remediation tracking records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with developer security testing responsibilities\n\norganizational personnel with configuration management responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring developer security testing and evaluation\n\nautomated mechanisms supporting and/or implementing the monitoring of developer security testing and evaluation\n\nstatic code analysis tools" - } - ] - } - ] - }, - { - "id": "sa-11.2", - "class": "SP800-53-enhancement", - "title": "Threat and Vulnerability Analyses", - "props": [ - { - "name": "label", - "value": "SA-11(2)" - }, - { - "name": "sort-id", - "value": "sa-11.02" - } - ], - "parts": [ - { - "id": "sa-11.2_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to perform threat and vulnerability analyses and subsequent testing/evaluation of the as-built system, component, or service." - }, - { - "id": "sa-11.2_gdn", - "name": "guidance", - "prose": "Applications may deviate significantly from the functional and design specifications created during the requirements and design phases of the system development life cycle. Therefore, threat and vulnerability analyses of information systems, system components, and information system services prior to delivery are critical to the effective operation of those systems, components, and services. Threat and vulnerability analyses at this phase of the life cycle help to ensure that design or implementation changes have been accounted for, and that any new vulnerabilities created as a result of those changes have been reviewed and mitigated.", - "links": [ - { - "href": "#pm-15", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - } - ] - }, - { - "id": "sa-11.2_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to perform:", - "parts": [ - { - "id": "sa-11.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(2)[1]" - } - ], - "prose": "threat analyses of the as-built, system component, or service;" - }, - { - "id": "sa-11.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(2)[2]" - } - ], - "prose": "vulnerability analyses of the as-built, system component, or service; and" - }, - { - "id": "sa-11.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(2)[3]" - } - ], - "prose": "subsequent testing/evaluation of the as-built, system component, or service." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing system developer security testing\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nsystem developer security test plans\n\nrecords of developer security testing results for the information system, system component, or information system service\n\nvulnerability scanning results\n\ninformation system risk assessment reports\n\nthreat and vulnerability analysis reports\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with developer security testing responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring developer security testing and evaluation\n\nautomated mechanisms supporting and/or implementing the monitoring of developer security testing and evaluation" - } - ] - } - ] - }, - { - "id": "sa-11.3", - "class": "SP800-53-enhancement", - "title": "Independent Verification of Assessment Plans / Evidence", - "params": [ - { - "id": "sa-11.3_prm_1", - "label": "organization-defined independence criteria" - } - ], - "props": [ - { - "name": "label", - "value": "SA-11(3)" - }, - { - "name": "sort-id", - "value": "sa-11.03" - } - ], - "parts": [ - { - "id": "sa-11.3_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sa-11.3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Requires an independent agent satisfying {{ insert: param, sa-11.3_prm_1 }} to verify the correct implementation of the developer security assessment plan and the evidence produced during security testing/evaluation; and" - }, - { - "id": "sa-11.3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Ensures that the independent agent is either provided with sufficient information to complete the verification process or granted the authority to obtain such information." - } - ] - }, - { - "id": "sa-11.3_gdn", - "name": "guidance", - "prose": "Independent agents have the necessary qualifications (i.e., expertise, skills, training, and experience) to verify the correct implementation of developer security assessment plans.", - "links": [ - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#sa-12", - "rel": "related" - } - ] - }, - { - "id": "sa-11.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-11.3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(3)(a)" - } - ], - "parts": [ - { - "id": "sa-11.3.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(3)(a)[1]" - } - ], - "prose": "defines independence criteria that an independent agent is required to satisfy;" - }, - { - "id": "sa-11.3.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(3)(a)[2]" - } - ], - "prose": "requires an independent agent satisfying organization-defined independence criteria to verify:", - "parts": [ - { - "id": "sa-11.3.a_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(3)(a)[2][a]" - } - ], - "prose": "the correct implementation of the developer security assessment plan;" - }, - { - "id": "sa-11.3.a_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(3)(a)[2][b]" - } - ], - "prose": "the evidence produced during security testing/evaluation;" - } - ] - } - ], - "links": [ - { - "href": "#sa-11.3_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "sa-11.3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(3)(b)" - } - ], - "prose": "ensures that the independent agent is either:", - "parts": [ - { - "id": "sa-11.3.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(3)(b)[1]" - } - ], - "prose": "provided with sufficient information to complete the verification process; or" - }, - { - "id": "sa-11.3.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(3)(b)[2]" - } - ], - "prose": "granted the authority to obtain such information." - } - ], - "links": [ - { - "href": "#sa-11.3_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing system developer security testing\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nindependent verification and validation reports\n\nsecurity test and evaluation plans\n\nsecurity test and evaluation results for the information system, system component, or information system service\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with developer security testing responsibilities\n\nsystem developers\n\nindependent verification agent" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring developer security testing and evaluation\n\nautomated mechanisms supporting and/or implementing the monitoring of developer security testing and evaluation" - } - ] - } - ] - }, - { - "id": "sa-11.4", - "class": "SP800-53-enhancement", - "title": "Manual Code Reviews", - "params": [ - { - "id": "sa-11.4_prm_1", - "label": "organization-defined specific code" - }, - { - "id": "sa-11.4_prm_2", - "label": "organization-defined processes, procedures, and/or techniques" - } - ], - "props": [ - { - "name": "label", - "value": "SA-11(4)" - }, - { - "name": "sort-id", - "value": "sa-11.04" - } - ], - "parts": [ - { - "id": "sa-11.4_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to perform a manual code review of {{ insert: param, sa-11.4_prm_1 }} using {{ insert: param, sa-11.4_prm_2 }}." - }, - { - "id": "sa-11.4_gdn", - "name": "guidance", - "prose": "Manual code reviews are usually reserved for the critical software and firmware components of information systems. Such code reviews are uniquely effective at identifying weaknesses that require knowledge of the application’s requirements or context which are generally unavailable to more automated analytic tools and techniques such as static or dynamic analysis. Components benefiting from manual review include for example, verifying access control matrices against application controls and reviewing more detailed aspects of cryptographic implementations and controls." - }, - { - "id": "sa-11.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-11.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(4)[1]" - } - ], - "prose": "defines specific code for which the developer of the information system, system component, or information system service is required to perform a manual code review;" - }, - { - "id": "sa-11.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(4)[2]" - } - ], - "prose": "defines processes, procedures, and/or techniques to be used when the developer performs a manual code review of organization-defined specific code; and" - }, - { - "id": "sa-11.4_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(4)[3]" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to perform a manual code review of organization-defined specific code using organization-defined processes, procedures, and/or techniques." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing system developer security testing\n\nprocesses, procedures, and/or techniques for performing manual code reviews\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nsystem developer security testing and evaluation plans\n\nsystem developer security testing and evaluation results\n\nlist of code requiring manual reviews\n\nrecords of manual code reviews\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with developer security testing responsibilities\n\nsystem developers\n\nindependent verification agent" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring developer security testing and evaluation\n\nautomated mechanisms supporting and/or implementing the monitoring of developer security testing and evaluation" - } - ] - } - ] - }, - { - "id": "sa-11.5", - "class": "SP800-53-enhancement", - "title": "Penetration Testing", - "params": [ - { - "id": "sa-11.5_prm_1", - "label": "organization-defined breadth/depth" - }, - { - "id": "sa-11.5_prm_2", - "label": "organization-defined constraints" - } - ], - "props": [ - { - "name": "label", - "value": "SA-11(5)" - }, - { - "name": "sort-id", - "value": "sa-11.05" - } - ], - "parts": [ - { - "id": "sa-11.5_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to perform penetration testing at {{ insert: param, sa-11.5_prm_1 }} and with {{ insert: param, sa-11.5_prm_2 }}." - }, - { - "id": "sa-11.5_gdn", - "name": "guidance", - "prose": "Penetration testing is an assessment methodology in which assessors, using all available information technology product and/or information system documentation (e.g., product/system design specifications, source code, and administrator/operator manuals) and working under specific constraints, attempt to circumvent implemented security features of information technology products and information systems. Penetration testing can include, for example, white, gray, or black box testing with analyses performed by skilled security professionals simulating adversary actions. The objective of penetration testing is to uncover potential vulnerabilities in information technology products and information systems resulting from implementation errors, configuration faults, or other operational deployment weaknesses or deficiencies. Penetration tests can be performed in conjunction with automated and manual code reviews to provide greater levels of analysis than would ordinarily be possible." - }, - { - "id": "sa-11.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-11.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(5)[1]" - } - ], - "prose": "defines for the developer of the information system, system component, or information system service:", - "parts": [ - { - "id": "sa-11.5_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(5)[1][a]" - } - ], - "prose": "the breadth of penetration testing to be performed by the developer;" - }, - { - "id": "sa-11.5_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(5)[1][b]" - } - ], - "prose": "the depth of penetration testing to be performed by the developer;" - } - ] - }, - { - "id": "sa-11.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(5)[2]" - } - ], - "prose": "defines constraints under which the developer is to perform penetration testing; and" - }, - { - "id": "sa-11.5_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(5)[3]" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to perform penetration testing at organization-defined breadth/depth and with organization-defined constraints." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing system developer security testing\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nsystem developer penetration testing and evaluation plans\n\nsystem developer penetration testing and evaluation results\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with developer security testing responsibilities\n\nsystem developers\n\nindependent verification agent" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring developer security testing and evaluation\n\nautomated mechanisms supporting and/or implementing the monitoring of developer security testing and evaluation" - } - ] - } - ] - }, - { - "id": "sa-11.6", - "class": "SP800-53-enhancement", - "title": "Attack Surface Reviews", - "props": [ - { - "name": "label", - "value": "SA-11(6)" - }, - { - "name": "sort-id", - "value": "sa-11.06" - } - ], - "parts": [ - { - "id": "sa-11.6_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to perform attack surface reviews." - }, - { - "id": "sa-11.6_gdn", - "name": "guidance", - "prose": "Attack surfaces of information systems are exposed areas that make those systems more vulnerable to cyber attacks. This includes any accessible areas where weaknesses or deficiencies in information systems (including the hardware, software, and firmware components) provide opportunities for adversaries to exploit vulnerabilities. Attack surface reviews ensure that developers: (i) analyze both design and implementation changes to information systems; and (ii) mitigate attack vectors generated as a result of the changes. Correction of identified flaws includes, for example, deprecation of unsafe functions." - }, - { - "id": "sa-11.6_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to perform attack surface reviews." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing system developer security testing\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nsystem developer security testing and evaluation plans\n\nsystem developer security testing and evaluation results\n\nrecords of attack surface reviews\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with developer security testing responsibilities\n\norganizational personnel with configuration management responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring developer security testing and evaluation\n\nautomated mechanisms supporting and/or implementing the monitoring of developer security testing and evaluation" - } - ] - } - ] - }, - { - "id": "sa-11.7", - "class": "SP800-53-enhancement", - "title": "Verify Scope of Testing / Evaluation", - "params": [ - { - "id": "sa-11.7_prm_1", - "label": "organization-defined depth of testing/evaluation" - } - ], - "props": [ - { - "name": "label", - "value": "SA-11(7)" - }, - { - "name": "sort-id", - "value": "sa-11.07" - } - ], - "parts": [ - { - "id": "sa-11.7_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to verify that the scope of security testing/evaluation provides complete coverage of required security controls at {{ insert: param, sa-11.7_prm_1 }}." - }, - { - "id": "sa-11.7_gdn", - "name": "guidance", - "prose": "Verifying that security testing/evaluation provides complete coverage of required security controls can be accomplished by a variety of analytic techniques ranging from informal to formal. Each of these techniques provides an increasing level of assurance corresponding to the degree of formality of the analysis. Rigorously demonstrating security control coverage at the highest levels of assurance can be provided by the use of formal modeling and analysis techniques including correlation between control implementation and corresponding test cases." - }, - { - "id": "sa-11.7_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-11.7_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(7)[1]" - } - ], - "prose": "defines the depth of testing/evaluation to ensure the scope of security/testing evaluation provides complete coverage of required security controls; and" - }, - { - "id": "sa-11.7_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-11(7)[2]" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to verify that the scope of security testing/evaluation provides complete coverage of required security controls at the organization-defined depth of testing/evaluation." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing system developer security testing\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nsystem developer security testing and evaluation plans\n\nsystem developer security testing and evaluation results\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with developer security testing responsibilities\n\nsystem developers\n\nindependent verification agent" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring developer security testing and evaluation\n\nautomated mechanisms supporting and/or implementing the monitoring of developer security testing and evaluation" - } - ] - } - ] - }, - { - "id": "sa-11.8", - "class": "SP800-53-enhancement", - "title": "Dynamic Code Analysis", - "props": [ - { - "name": "label", - "value": "SA-11(8)" - }, - { - "name": "sort-id", - "value": "sa-11.08" - } - ], - "parts": [ - { - "id": "sa-11.8_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to employ dynamic code analysis tools to identify common flaws and document the results of the analysis." - }, - { - "id": "sa-11.8_gdn", - "name": "guidance", - "prose": "Dynamic code analysis provides run-time verification of software programs, using tools capable of monitoring programs for memory corruption, user privilege issues, and other potential security problems. Dynamic code analysis employs run-time tools to help to ensure that security functionality performs in the manner in which it was designed. A specialized type of dynamic analysis, known as fuzz testing, induces program failures by deliberately introducing malformed or random data into software programs. Fuzz testing strategies derive from the intended use of applications and the functional and design specifications for the applications. To understand the scope of dynamic code analysis and hence the assurance provided, organizations may also consider conducting code coverage analysis (checking the degree to which the code has been tested using metrics such as percent of subroutines tested or percent of program statements called during execution of the test suite) and/or concordance analysis (checking for words that are out of place in software code such as non-English language words or derogatory terms)." - }, - { - "id": "sa-11.8_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to employ dynamic code analysis tools to identify common flaws and document the results of the analysis." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing system developer security testing\n\nprocedures addressing flaw remediation\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nsystem developer security test and evaluation plans\n\nsecurity test and evaluation results\n\nsecurity flaw and remediation tracking reports\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with developer security testing responsibilities\n\norganizational personnel with configuration management responsibilities\n\nsystem developers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for monitoring developer security testing and evaluation\n\nautomated mechanisms supporting and/or implementing the monitoring of developer security testing and evaluation" - } - ] - } - ] - } - ] - }, - { - "id": "sa-12", - "class": "SP800-53", - "title": "Supply Chain Protection", - "params": [ - { - "id": "sa-12_prm_1", - "label": "organization-defined security safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "SA-12" - }, - { - "name": "sort-id", - "value": "sa-12" - } - ], - "links": [ - { - "href": "#8ab6bcdc-339b-4068-b45e-994814a6e187", - "rel": "reference" - }, - { - "href": "#bdd2f49e-edf7-491f-a178-4487898228f3", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sa-12_smt", - "name": "statement", - "prose": "The organization protects against supply chain threats to the information system, system component, or information system service by employing {{ insert: param, sa-12_prm_1 }} as part of a comprehensive, defense-in-breadth information security strategy." - }, - { - "id": "sa-12_gdn", - "name": "guidance", - "prose": "Information systems (including system components that compose those systems) need to be protected throughout the system development life cycle (i.e., during design, development, manufacturing, packaging, assembly, distribution, system integration, operations, maintenance, and retirement). Protection of organizational information systems is accomplished through threat awareness, by the identification, management, and reduction of vulnerabilities at each phase of the life cycle and the use of complementary, mutually reinforcing strategies to respond to risk. Organizations consider implementing a standardized process to address supply chain risk with respect to information systems and system components, and to educate the acquisition workforce on threats, risk, and required security controls. Organizations use the acquisition/procurement processes to require supply chain entities to implement necessary security safeguards to: (i) reduce the likelihood of unauthorized modifications at each stage in the supply chain; and (ii) protect information systems and information system components, prior to taking delivery of such systems/components. This control also applies to information system services. Security safeguards include, for example: (i) security controls for development systems, development facilities, and external connections to development systems; (ii) vetting development personnel; and (iii) use of tamper-evident packaging during shipping/warehousing. Methods for reviewing and protecting development plans, evidence, and documentation are commensurate with the security category or classification level of the information system. Contracts may specify documentation protection requirements.", - "links": [ - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#pe-16", - "rel": "related" - }, - { - "href": "#pl-8", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - }, - { - "href": "#sa-14", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "#sa-18", - "rel": "related" - }, - { - "href": "#sa-19", - "rel": "related" - }, - { - "href": "#sc-29", - "rel": "related" - }, - { - "href": "#sc-30", - "rel": "related" - }, - { - "href": "#sc-38", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "sa-12_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-12_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12[1]" - } - ], - "prose": "defines security safeguards to be employed to protect against supply chain threats to the information system, system component, or information system service; and" - }, - { - "id": "sa-12_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12[2]" - } - ], - "prose": "protects against supply chain threats to the information system, system component, or information system service by employing organization-defined security safeguards as part of a comprehensive, defense-in-breadth information security strategy." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing supply chain protection\n\nprocedures addressing the integration of information security requirements into the acquisition process\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nlist of supply chain threats\n\nlist of security safeguards to be taken against supply chain threats\n\nsystem development life cycle documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for defining safeguards for and protecting against supply chain threats\n\nautomated mechanisms supporting and/or implementing safeguards for supply chain threats" - } - ] - } - ], - "controls": [ - { - "id": "sa-12.1", - "class": "SP800-53-enhancement", - "title": "Acquisition Strategies / Tools / Methods", - "params": [ - { - "id": "sa-12.1_prm_1", - "label": "organization-defined tailored acquisition strategies, contract tools, and procurement methods" - } - ], - "props": [ - { - "name": "label", - "value": "SA-12(1)" - }, - { - "name": "sort-id", - "value": "sa-12.01" - } - ], - "parts": [ - { - "id": "sa-12.1_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, sa-12.1_prm_1 }} for the purchase of the information system, system component, or information system service from suppliers." - }, - { - "id": "sa-12.1_gdn", - "name": "guidance", - "prose": "The use of acquisition and procurement processes by organizations early in the system development life cycle provides an important vehicle to protect the supply chain. Organizations use available all-source intelligence analysis to inform the tailoring of acquisition strategies, tools, and methods. There are a number of different tools and techniques available (e.g., obscuring the end use of an information system or system component, using blind or filtered buys). Organizations also consider creating incentives for suppliers who: (i) implement required security safeguards; (ii) promote transparency into their organizational processes and security practices; (iii) provide additional vetting of the processes and security practices of subordinate suppliers, critical information system components, and services; (iv) restrict purchases from specific suppliers or countries; and (v) provide contract language regarding the prohibition of tainted or counterfeit components. In addition, organizations consider minimizing the time between purchase decisions and required delivery to limit opportunities for adversaries to corrupt information system components or products. Finally, organizations can use trusted/controlled distribution, delivery, and warehousing options to reduce supply chain risk (e.g., requiring tamper-evident packaging of information system components during shipping and warehousing).", - "links": [ - { - "href": "#sa-19", - "rel": "related" - } - ] - }, - { - "id": "sa-12.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-12.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(1)[1]" - } - ], - "prose": "defines the following to be employed for the purchase of the information system, system component, or information system service from suppliers:", - "parts": [ - { - "id": "sa-12.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(1)[1][a]" - } - ], - "prose": "tailored acquisition strategies;" - }, - { - "id": "sa-12.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(1)[1][b]" - } - ], - "prose": "contract tools;" - }, - { - "id": "sa-12.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(1)[1][c]" - } - ], - "prose": "procurement methods; and" - } - ] - }, - { - "id": "sa-12.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(1)[2]" - } - ], - "prose": "employs organization-defined tailored acquisition strategies, contract tools, and procurement methods for the purchase of the information system, system component, or information system service from suppliers." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing supply chain protection\n\nprocedures addressing the integration of information security requirements into the acquisition process\n\nprocedures addressing the integration of acquisition strategies, contract tools, and procure methods into the acquisition process\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for information systems or services\n\npurchase orders/requisitions for the information system\n\nsystem component\n\nor information system service from suppliers\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for defining and employing tailored acquisition strategies, contract tools, and procurement methods\n\nautomated mechanisms supporting and/or implementing the definition and employment of tailored acquisition strategies, contract tools, and procurement methods" - } - ] - } - ] - }, - { - "id": "sa-12.2", - "class": "SP800-53-enhancement", - "title": "Supplier Reviews", - "props": [ - { - "name": "label", - "value": "SA-12(2)" - }, - { - "name": "sort-id", - "value": "sa-12.02" - } - ], - "parts": [ - { - "id": "sa-12.2_smt", - "name": "statement", - "prose": "The organization conducts a supplier review prior to entering into a contractual agreement to acquire the information system, system component, or information system service." - }, - { - "id": "sa-12.2_gdn", - "name": "guidance", - "prose": "Supplier reviews include, for example: (i) analysis of supplier processes used to design, develop, test, implement, verify, deliver, and support information systems, system components, and information system services; and (ii) assessment of supplier training and experience in developing systems, components, or services with the required security capability. These reviews provide organizations with increased levels of visibility into supplier activities during the system development life cycle to promote more effective supply chain risk management. Supplier reviews can also help to determine whether primary suppliers have security safeguards in place and a practice for vetting subordinate suppliers, for example, second- and third-tier suppliers, and any subcontractors." - }, - { - "id": "sa-12.2_obj", - "name": "objective", - "prose": "Determine if the organization conducts a supplier review prior to entering into a contractual agreement to acquire the information system, system component, or information system service." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing supply chain protection\n\nprocedures addressing the integration of information security requirements into the acquisition process\n\nrecords of supplier due diligence reviews\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for conducting supplier reviews\n\nautomated mechanisms supporting and/or implementing supplier reviews" - } - ] - } - ] - }, - { - "id": "sa-12.3", - "class": "SP800-53-enhancement", - "title": "Trusted Shipping and Warehousing", - "props": [ - { - "name": "label", - "value": "SA-12(3)" - }, - { - "name": "sort-id", - "value": "sa-12.03" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sa-12.1", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sa-12.4", - "class": "SP800-53-enhancement", - "title": "Diversity of Suppliers", - "props": [ - { - "name": "label", - "value": "SA-12(4)" - }, - { - "name": "sort-id", - "value": "sa-12.04" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sa-12.13", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sa-12.5", - "class": "SP800-53-enhancement", - "title": "Limitation of Harm", - "params": [ - { - "id": "sa-12.5_prm_1", - "label": "organization-defined security safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "SA-12(5)" - }, - { - "name": "sort-id", - "value": "sa-12.05" - } - ], - "parts": [ - { - "id": "sa-12.5_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, sa-12.5_prm_1 }} to limit harm from potential adversaries identifying and targeting the organizational supply chain." - }, - { - "id": "sa-12.5_gdn", - "name": "guidance", - "prose": "Supply chain risk is part of the advanced persistent threat (APT). Security safeguards and countermeasures to reduce the probability of adversaries successfully identifying and targeting the supply chain include, for example: (i) avoiding the purchase of custom configurations to reduce the risk of acquiring information systems, components, or products that have been corrupted via supply chain actions targeted at specific organizations; (ii) employing a diverse set of suppliers to limit the potential harm from any given supplier in the supply chain; (iii) employing approved vendor lists with standing reputations in industry, and (iv) using procurement carve outs (i.e., exclusions to commitments or obligations)." - }, - { - "id": "sa-12.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-12.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(5)[1]" - } - ], - "prose": "defines security safeguards to be employed to limit harm from potential adversaries identifying and targeting the organizational supply chain; and" - }, - { - "id": "sa-12.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(5)[2]" - } - ], - "prose": "employs organization-defined security safeguards to limit harm from potential adversaries identifying and targeting the organizational supply chain." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nconfiguration management policy\n\nprocedures addressing supply chain protection\n\nprocedures addressing the integration of information security requirements into the acquisition process\n\nprocedures addressing the baseline configuration of the information system\n\nconfiguration management plan\n\ninformation system design documentation\n\ninformation system architecture and associated configuration documentation\n\nsolicitation documentation\n\nacquisition documentation\n\nacquisition contracts for the information system, system component, or information system service\n\nlist of security safeguards to be taken to protect organizational supply chain against potential supply chain threats\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for defining and employing safeguards to limit harm from adversaries of the organizational supply chain\n\nautomated mechanisms supporting and/or implementing the definition and employment of safeguards to protect the organizational supply chain" - } - ] - } - ] - }, - { - "id": "sa-12.6", - "class": "SP800-53-enhancement", - "title": "Minimizing Procurement Time", - "props": [ - { - "name": "label", - "value": "SA-12(6)" - }, - { - "name": "sort-id", - "value": "sa-12.06" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sa-12.1", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sa-12.7", - "class": "SP800-53-enhancement", - "title": "Assessments Prior to Selection / Acceptance / Update", - "props": [ - { - "name": "label", - "value": "SA-12(7)" - }, - { - "name": "sort-id", - "value": "sa-12.07" - } - ], - "parts": [ - { - "id": "sa-12.7_smt", - "name": "statement", - "prose": "The organization conducts an assessment of the information system, system component, or information system service prior to selection, acceptance, or update." - }, - { - "id": "sa-12.7_gdn", - "name": "guidance", - "prose": "Assessments include, for example, testing, evaluations, reviews, and analyses. Independent, third-party entities or organizational personnel conduct assessments of systems, components, products, tools, and services. Organizations conduct assessments to uncover unintentional vulnerabilities and intentional vulnerabilities including, for example, malicious code, malicious processes, defective software, and counterfeits. Assessments can include, for example, static analyses, dynamic analyses, simulations, white, gray, and black box testing, fuzz testing, penetration testing, and ensuring that components or services are genuine (e.g., using tags, cryptographic hash verifications, or digital signatures). Evidence generated during security assessments is documented for follow-on actions carried out by organizations.", - "links": [ - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#sa-11", - "rel": "related" - } - ] - }, - { - "id": "sa-12.7_obj", - "name": "objective", - "prose": "Determine if the organization conducts an assessment of the information system, system component, or information system service prior to:", - "parts": [ - { - "id": "sa-12.7_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(7)[1]" - } - ], - "prose": "selection;" - }, - { - "id": "sa-12.7_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(7)[2]" - } - ], - "prose": "acceptance; or" - }, - { - "id": "sa-12.7_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(7)[3]" - } - ], - "prose": "update." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing supply chain protection\n\nprocedures addressing the integration of information security requirements into the acquisition process\n\nsecurity test and evaluation results\n\nvulnerability assessment results\n\npenetration testing results\n\norganizational risk assessment results\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for conducting assessments prior to selection, acceptance, or update\n\nautomated mechanisms supporting and/or implementing the conducting of assessments prior to selection, acceptance, or update" - } - ] - } - ] - }, - { - "id": "sa-12.8", - "class": "SP800-53-enhancement", - "title": "Use of All-source Intelligence", - "props": [ - { - "name": "label", - "value": "SA-12(8)" - }, - { - "name": "sort-id", - "value": "sa-12.08" - } - ], - "parts": [ - { - "id": "sa-12.8_smt", - "name": "statement", - "prose": "The organization uses all-source intelligence analysis of suppliers and potential suppliers of the information system, system component, or information system service." - }, - { - "id": "sa-12.8_gdn", - "name": "guidance", - "prose": "All-source intelligence analysis is employed by organizations to inform engineering, acquisition, and risk management decisions. All-source intelligence consists of intelligence products and/or organizations and activities that incorporate all sources of information, most frequently including human intelligence, imagery intelligence, measurement and signature intelligence, signals intelligence, and open source data in the production of finished intelligence. Where available, such information is used to analyze the risk of both intentional and unintentional vulnerabilities from development, manufacturing, and delivery processes, people, and the environment. This review is performed on suppliers at multiple tiers in the supply chain sufficient to manage risks.", - "links": [ - { - "href": "#sa-15", - "rel": "related" - } - ] - }, - { - "id": "sa-12.8_obj", - "name": "objective", - "prose": "Determine if the organization uses all-source intelligence analysis of:", - "parts": [ - { - "id": "sa-12.8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(8)[1]" - } - ], - "prose": "suppliers of the information system, system component, or information system service; and" - }, - { - "id": "sa-12.8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(8)[2]" - } - ], - "prose": "potential suppliers of the information system, system component, or information system service." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing supply chain protection\n\nsolicitation documentation\n\nacquisition documentation\n\nacquisition contracts for the information system, system component, or information system service\n\nrecords of all-source intelligence analyses\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for use of an all-source analysis of suppliers and potential suppliers\n\nautomated mechanisms supporting and/or implementing the use of all-source analysis of suppliers and potential suppliers" - } - ] - } - ] - }, - { - "id": "sa-12.9", - "class": "SP800-53-enhancement", - "title": "Operations Security", - "params": [ - { - "id": "sa-12.9_prm_1", - "label": "organization-defined Operations Security (OPSEC) safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "SA-12(9)" - }, - { - "name": "sort-id", - "value": "sa-12.09" - } - ], - "parts": [ - { - "id": "sa-12.9_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, sa-12.9_prm_1 }} in accordance with classification guides to protect supply chain-related information for the information system, system component, or information system service." - }, - { - "id": "sa-12.9_gdn", - "name": "guidance", - "prose": "Supply chain information includes, for example: user identities; uses for information systems, information system components, and information system services; supplier identities; supplier processes; security requirements; design specifications; testing and evaluation results; and system/component configurations. This control enhancement expands the scope of OPSEC to include suppliers and potential suppliers. OPSEC is a process of identifying critical information and subsequently analyzing friendly actions attendant to operations and other activities to: (i) identify those actions that can be observed by potential adversaries; (ii) determine indicators that adversaries might obtain that could be interpreted or pieced together to derive critical information in sufficient time to cause harm to organizations; (iii) implement safeguards or countermeasures to eliminate or reduce to an acceptable level, exploitable vulnerabilities; and (iv) consider how aggregated information may compromise the confidentiality of users or uses of the supply chain. OPSEC may require organizations to withhold critical mission/business information from suppliers and may include the use of intermediaries to hide the end use, or users, of information systems, system components, or information system services." - }, - { - "id": "sa-12.9_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-12.9_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(9)[1]" - } - ], - "prose": "defines Operations Security (OPSEC) safeguards to be employed in accordance with classification guides to protect supply chain-related information for the information system, system component, or information system service; and" - }, - { - "id": "sa-12.9_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(9)[2]" - } - ], - "prose": "employs organization-defined OPSEC safeguards in accordance with classification guides to protect supply chain-related information for the information system, system component, or information system service." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing supply chain protection\n\nsolicitation documentation\n\nacquisition documentation\n\nacquisition contracts for the information system, system component, or information system service\n\nrecords of all-source intelligence analyses\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for defining and employing OPSEC safeguards\n\nautomated mechanisms supporting and/or implementing the definition and employment of OPSEC safeguards" - } - ] - } - ] - }, - { - "id": "sa-12.10", - "class": "SP800-53-enhancement", - "title": "Validate as Genuine and Not Altered", - "params": [ - { - "id": "sa-12.10_prm_1", - "label": "organization-defined security safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "SA-12(10)" - }, - { - "name": "sort-id", - "value": "sa-12.10" - } - ], - "parts": [ - { - "id": "sa-12.10_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, sa-12.10_prm_1 }} to validate that the information system or system component received is genuine and has not been altered." - }, - { - "id": "sa-12.10_gdn", - "name": "guidance", - "prose": "For some information system components, especially hardware, there are technical means to help determine if the components are genuine or have been altered. Security safeguards used to validate the authenticity of information systems and information system components include, for example, optical/nanotechnology tagging and side-channel analysis. For hardware, detailed bill of material information can highlight the elements with embedded logic complete with component and production location." - }, - { - "id": "sa-12.10_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-12.10_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(10)[1]" - } - ], - "prose": "defines security safeguards to be employed to validate that the information system or system component received is genuine and has not been altered; and" - }, - { - "id": "sa-12.10_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(10)[2]" - } - ], - "prose": "employs organization-defined security safeguards to validate that the information system or system components received is genuine and has not been altered." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing supply chain protection\n\nprocedures address the integration of information security requirements into the acquisition process\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nevidentiary documentation (including applicable configurations) indicating the information system, system component, or information system service are genuine and have not been altered\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for defining and employing validation safeguards\n\nautomated mechanisms supporting and/or implementing the definition and employment of validation safeguards" - } - ] - } - ] - }, - { - "id": "sa-12.11", - "class": "SP800-53-enhancement", - "title": "Penetration Testing / Analysis of Elements, Processes, and Actors", - "params": [ - { - "id": "sa-12.11_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "organizational analysis, independent third-party analysis, organizational penetration testing, independent third-party penetration testing" - ] - } - }, - { - "id": "sa-12.11_prm_2", - "label": "organization-defined supply chain elements, processes, and actors" - } - ], - "props": [ - { - "name": "label", - "value": "SA-12(11)" - }, - { - "name": "sort-id", - "value": "sa-12.11" - } - ], - "parts": [ - { - "id": "sa-12.11_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, sa-12.11_prm_1 }} of {{ insert: param, sa-12.11_prm_2 }} associated with the information system, system component, or information system service." - }, - { - "id": "sa-12.11_gdn", - "name": "guidance", - "prose": "This control enhancement addresses analysis and/or testing of the supply chain, not just delivered items. Supply chain elements are information technology products or product components that contain programmable logic and that are critically important to information system functions. Supply chain processes include, for example: (i) hardware, software, and firmware development processes; (ii) shipping/handling procedures; (iii) personnel and physical security programs; (iv) configuration management tools/measures to maintain provenance; or (v) any other programs, processes, or procedures associated with the production/distribution of supply chain elements. Supply chain actors are individuals with specific roles and responsibilities in the supply chain. The evidence generated during analyses and testing of supply chain elements, processes, and actors is documented and used to inform organizational risk management activities and decisions.", - "links": [ - { - "href": "#ra-5", - "rel": "related" - } - ] - }, - { - "id": "sa-12.11_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-12.11_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(11)[1]" - } - ], - "prose": "defines supply chain:", - "parts": [ - { - "id": "sa-12.11_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(11)[1][a]" - } - ], - "prose": "elements to be analyzed and/or tested;" - }, - { - "id": "sa-12.11_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(11)[1][b]" - } - ], - "prose": "processes to be analyzed and/or tested;" - }, - { - "id": "sa-12.11_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(11)[1][c]" - } - ], - "prose": "actors to be analyzed and/or tested;" - } - ] - }, - { - "id": "sa-12.11_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(11)[2]" - } - ], - "prose": "employs one or more of the following to analyze and/or test organization-defined supply chain elements, processes, and actors associated with the information system, system component, or information system service:", - "parts": [ - { - "id": "sa-12.11_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(11)[2][a]" - } - ], - "prose": "organizational analysis;" - }, - { - "id": "sa-12.11_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(11)[2][b]" - } - ], - "prose": "independent third party analysis;" - }, - { - "id": "sa-12.11_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(11)[2][c]" - } - ], - "prose": "organizational penetration testing; and/or" - }, - { - "id": "sa-12.11_obj.2.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(11)[2][d]" - } - ], - "prose": "independent third-party penetration testing." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing supply chain protection\n\nevidence of organizational analysis, independent third-party analysis, organizational penetration testing, and/or independent third-party penetration testing\n\nlist of supply chain elements, processes, and actors (associated with the information system, system component, or information system service) subject to analysis and/or testing\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain protection responsibilities\n\norganizational personnel with responsibilities for analyzing and/or testing supply chain elements, processes, and actors" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for defining and employing methods of analysis/testing of supply chain elements, processes, and actors\n\nautomated mechanisms supporting and/or implementing the analysis/testing of supply chain elements, processes, and actors" - } - ] - } - ] - }, - { - "id": "sa-12.12", - "class": "SP800-53-enhancement", - "title": "Inter-organizational Agreements", - "props": [ - { - "name": "label", - "value": "SA-12(12)" - }, - { - "name": "sort-id", - "value": "sa-12.12" - } - ], - "parts": [ - { - "id": "sa-12.12_smt", - "name": "statement", - "prose": "The organization establishes inter-organizational agreements and procedures with entities involved in the supply chain for the information system, system component, or information system service." - }, - { - "id": "sa-12.12_gdn", - "name": "guidance", - "prose": "The establishment of inter-organizational agreements and procedures provides for notification of supply chain compromises. Early notification of supply chain compromises that can potentially adversely affect or have adversely affected organizational information systems, including critical system components, is essential for organizations to provide appropriate responses to such incidents." - }, - { - "id": "sa-12.12_obj", - "name": "objective", - "prose": "Determine if the organization establishes, with entities involved in the supply chain for the information system, system component, or information system service,:", - "parts": [ - { - "id": "sa-12.12_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(12)[1]" - } - ], - "prose": "inter-organizational agreements; and" - }, - { - "id": "sa-12.12_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(12)[2]" - } - ], - "prose": "inter-organizational procedures." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing supply chain protection\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\ninter-organizational agreements and procedures\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for establishing inter-organizational agreements and procedures with supply chain entities" - } - ] - } - ] - }, - { - "id": "sa-12.13", - "class": "SP800-53-enhancement", - "title": "Critical Information System Components", - "params": [ - { - "id": "sa-12.13_prm_1", - "label": "organization-defined security safeguards" - }, - { - "id": "sa-12.13_prm_2", - "label": "organization-defined critical information system components" - } - ], - "props": [ - { - "name": "label", - "value": "SA-12(13)" - }, - { - "name": "sort-id", - "value": "sa-12.13" - } - ], - "parts": [ - { - "id": "sa-12.13_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, sa-12.13_prm_1 }} to ensure an adequate supply of {{ insert: param, sa-12.13_prm_2 }}." - }, - { - "id": "sa-12.13_gdn", - "name": "guidance", - "prose": "Adversaries can attempt to impede organizational operations by disrupting the supply of critical information system components or corrupting supplier operations. Safeguards to ensure adequate supplies of critical information system components include, for example: (i) the use of multiple suppliers throughout the supply chain for the identified critical components; and (ii) stockpiling of spare components to ensure operation during mission-critical times." - }, - { - "id": "sa-12.13_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-12.13_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(13)[1]" - } - ], - "prose": "defines critical information system components for which security safeguards are to be employed to ensure an adequate supply of such components;" - }, - { - "id": "sa-12.13_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(13)[2]" - } - ], - "prose": "defines security safeguards to be employed to ensure an adequate supply of organization-defined critical information components; and" - }, - { - "id": "sa-12.13_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(13)[3]" - } - ], - "prose": "employs organization-defined security safeguards to ensure an adequate supply of organization-defined critical information system components." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing supply chain protection\n\nphysical inventory of critical information system components\n\ninventory records of critical information system components\n\nlist of security safeguards ensuring adequate supply of critical information system components\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for defining and employing security safeguards to ensure an adequate supply of critical information system components\n\nautomated mechanisms supporting and/or implementing the security safeguards that ensure an adequate supply of critical information system components" - } - ] - } - ] - }, - { - "id": "sa-12.14", - "class": "SP800-53-enhancement", - "title": "Identity and Traceability", - "params": [ - { - "id": "sa-12.14_prm_1", - "label": "organization-defined supply chain elements, processes, and actors" - } - ], - "props": [ - { - "name": "label", - "value": "SA-12(14)" - }, - { - "name": "sort-id", - "value": "sa-12.14" - } - ], - "parts": [ - { - "id": "sa-12.14_smt", - "name": "statement", - "prose": "The organization establishes and retains unique identification of {{ insert: param, sa-12.14_prm_1 }} for the information system, system component, or information system service." - }, - { - "id": "sa-12.14_gdn", - "name": "guidance", - "prose": "Knowing who and what is in the supply chains of organizations is critical to gaining visibility into what is happening within such supply chains, as well as monitoring and identifying high-risk events and activities. Without reasonable visibility and traceability into supply chains (i.e., elements, processes, and actors), it is very difficult for organizations to understand and therefore manage risk, and to reduce the likelihood of adverse events. Uniquely identifying acquirer and integrator roles, organizations, personnel, mission and element processes, testing and evaluation procedures, delivery mechanisms, support mechanisms, communications/delivery paths, and disposal/final disposition activities as well as the components and tools used, establishes a foundational identity structure for assessment of supply chain activities. For example, labeling (using serial numbers) and tagging (using radio-frequency identification [RFID] tags) individual supply chain elements including software packages, modules, and hardware devices, and processes associated with those elements can be used for this purpose. Identification methods are sufficient to support the provenance in the event of a supply chain issue or adverse supply chain event." - }, - { - "id": "sa-12.14_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-12.14_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(14)[1]" - } - ], - "prose": "defines the following for the establishment and retention of unique identification:", - "parts": [ - { - "id": "sa-12.14_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(14)[1][a]" - } - ], - "prose": "supply chain elements;" - }, - { - "id": "sa-12.14_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(14)[1][b]" - } - ], - "prose": "supply chain processes;" - }, - { - "id": "sa-12.14_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(14)[1][c]" - } - ], - "prose": "supply chain actors; and" - } - ] - }, - { - "id": "sa-12.14_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-12(14)[2]" - } - ], - "prose": "establishes and retains unique identification of organization-defined supply chain elements, processes, and actors for the information system, system component, or information system service." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing supply chain protection\n\nprocedures addressing the integration of information security requirements into the acquisition process\n\nlist of supply chain elements, processes, and actors (associated with the information system, system component, or information system service) requiring implementation of unique identification processes, procedures, tools, mechanisms, equipment, techniques and/or configurations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain protection responsibilities\n\norganizational personnel with responsibilities for establishing and retaining unique identification of supply chain elements, processes, and actors" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for defining, establishing, and retaining unique identification for supply chain elements, processes, and actors\n\nautomated mechanisms supporting and/or implementing the definition, establishment, and retention of unique identification for supply chain elements, processes, and actors" - } - ] - } - ] - }, - { - "id": "sa-12.15", - "class": "SP800-53-enhancement", - "title": "Processes to Address Weaknesses or Deficiencies", - "props": [ - { - "name": "label", - "value": "SA-12(15)" - }, - { - "name": "sort-id", - "value": "sa-12.15" - } - ], - "parts": [ - { - "id": "sa-12.15_smt", - "name": "statement", - "prose": "The organization establishes a process to address weaknesses or deficiencies in supply chain elements identified during independent or organizational assessments of such elements." - }, - { - "id": "sa-12.15_gdn", - "name": "guidance", - "prose": "Evidence generated during independent or organizational assessments of supply chain elements (e.g., penetration testing, audits, verification/validation activities) is documented and used in follow-on processes implemented by organizations to respond to the risks related to the identified weaknesses and deficiencies. Supply chain elements include, for example, supplier development processes and supplier distribution systems." - }, - { - "id": "sa-12.15_obj", - "name": "objective", - "prose": "Determine if the organization establishes a process to address weaknesses or deficiencies in supply chain elements identified during independent or organizational assessments of such elements." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing supply chain protection\n\nprocedures addressing weaknesses or deficiencies in supply chain elements\n\nresults of independent or organizational assessments of supply chain controls and processes\n\nacquisition contracts, service-level agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for addressing weaknesses or deficiencies in supply chain elements\n\nautomated mechanisms supporting and/or implementing the addressing of weaknesses or deficiencies in supply chain elements" - } - ] - } - ] - } - ] - }, - { - "id": "sa-13", - "class": "SP800-53", - "title": "Trustworthiness", - "params": [ - { - "id": "sa-13_prm_1", - "label": "organization-defined information system, information system component, or information system service" - }, - { - "id": "sa-13_prm_2", - "label": "organization-defined assurance overlay" - } - ], - "props": [ - { - "name": "label", - "value": "SA-13" - }, - { - "name": "sort-id", - "value": "sa-13" - } - ], - "links": [ - { - "href": "#e85cdb3f-7f0a-4083-8639-f13f70d3760b", - "rel": "reference" - }, - { - "href": "#aba82822-b6e6-4abe-af2e-3fdd68f0bcf8", - "rel": "reference" - }, - { - "href": "#07b79057-4b85-471e-bd16-84844917325b", - "rel": "reference" - }, - { - "href": "#cd4cf751-3312-4a55-b1a9-fad2f1db9119", - "rel": "reference" - }, - { - "href": "#f152844f-b1ef-4836-8729-6277078ebee1", - "rel": "reference" - }, - { - "href": "#abd950ae-092f-4b7a-b374-1c7c67fe9350", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sa-13_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sa-13_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Describes the trustworthiness required in the {{ insert: param, sa-13_prm_1 }} supporting its critical missions/business functions; and" - }, - { - "id": "sa-13_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Implements {{ insert: param, sa-13_prm_2 }} to achieve such trustworthiness." - } - ] - }, - { - "id": "sa-13_gdn", - "name": "guidance", - "prose": "This control helps organizations to make explicit trustworthiness decisions when designing, developing, and implementing information systems that are needed to conduct critical organizational missions/business functions. Trustworthiness is a characteristic/property of an information system that expresses the degree to which the system can be expected to preserve the confidentiality, integrity, and availability of the information it processes, stores, or transmits. Trustworthy information systems are systems that are capable of being trusted to operate within defined levels of risk despite the environmental disruptions, human errors, and purposeful attacks that are expected to occur in the specified environments of operation. Trustworthy systems are important to mission/business success. Two factors affecting the trustworthiness of information systems include: (i) security functionality (i.e., the security features, functions, and/or mechanisms employed within the system and its environment of operation); and (ii) security assurance (i.e., the grounds for confidence that the security functionality is effective in its application). Developers, implementers, operators, and maintainers of organizational information systems can increase the level of assurance (and trustworthiness), for example, by employing well-defined security policy models, structured and rigorous hardware, software, and firmware development techniques, sound system/security engineering principles, and secure configuration settings (defined by a set of assurance-related security controls in Appendix E). Assurance is also based on the assessment of evidence produced during the system development life cycle. Critical missions/business functions are supported by high-impact systems and the associated assurance requirements for such systems. The additional assurance controls in Table E-4 in Appendix E (designated as optional) can be used to develop and implement high-assurance solutions for specific information systems and system components using the concept of overlays described in Appendix I. Organizations select assurance overlays that have been developed, validated, and approved for community adoption (e.g., cross-organization, governmentwide), limiting the development of such overlays on an organization-by-organization basis. Organizations can conduct criticality analyses as described in SA-14, to determine the information systems, system components, or information system services that require high-assurance solutions. Trustworthiness requirements and assurance overlays can be described in the security plans for organizational information systems.", - "links": [ - { - "href": "#ra-2", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-14", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - } - ] - }, - { - "id": "sa-13_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-13.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-13(a)" - } - ], - "parts": [ - { - "id": "sa-13.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-13(a)[1]" - } - ], - "prose": "defines information system, system component, or information system service for which the trustworthiness required is to be described;" - }, - { - "id": "sa-13.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-13(a)[2]" - } - ], - "prose": "describes the trustworthiness required in organization-defined information system, information system component, or information system service supporting its critical mission/business functions;" - } - ] - }, - { - "id": "sa-13.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-13(b)" - } - ], - "parts": [ - { - "id": "sa-13.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-13(b)[1]" - } - ], - "prose": "defines an assurance overlay to be implemented to achieve such trustworthiness; and" - }, - { - "id": "sa-13.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-13(b)[2]" - } - ], - "prose": "organization implements the organization-defined assurance overlay to achieve such trustworthiness." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing trustworthiness requirements for the information system, system component, or information system service\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsecurity categorization documentation/results\n\nsecurity authorization package for the information system, system component, or information system service\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nauthorizing official" - } - ] - } - ] - }, - { - "id": "sa-14", - "class": "SP800-53", - "title": "Criticality Analysis", - "params": [ - { - "id": "sa-14_prm_1", - "label": "organization-defined information systems, information system components, or information system services" - }, - { - "id": "sa-14_prm_2", - "label": "organization-defined decision points in the system development life cycle" - } - ], - "props": [ - { - "name": "label", - "value": "SA-14" - }, - { - "name": "sort-id", - "value": "sa-14" - } - ], - "parts": [ - { - "id": "sa-14_smt", - "name": "statement", - "prose": "The organization identifies critical information system components and functions by performing a criticality analysis for {{ insert: param, sa-14_prm_1 }} at {{ insert: param, sa-14_prm_2 }}." - }, - { - "id": "sa-14_gdn", - "name": "guidance", - "prose": "Criticality analysis is a key tenet of supply chain risk management and informs the prioritization of supply chain protection activities such as attack surface reduction, use of all-source intelligence, and tailored acquisition strategies. Information system engineers can conduct an end-to-end functional decomposition of an information system to identify mission-critical functions and components. The functional decomposition includes the identification of core organizational missions supported by the system, decomposition into the specific functions to perform those missions, and traceability to the hardware, software, and firmware components that implement those functions, including when the functions are shared by many components within and beyond the information system boundary. Information system components that allow for unmediated access to critical components or functions are considered critical due to the inherent vulnerabilities such components create. Criticality is assessed in terms of the impact of the function or component failure on the ability of the component to complete the organizational missions supported by the information system. A criticality analysis is performed whenever an architecture or design is being developed or modified, including upgrades.", - "links": [ - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#pl-8", - "rel": "related" - }, - { - "href": "#pm-1", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-12", - "rel": "related" - }, - { - "href": "#sa-13", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "#sa-20", - "rel": "related" - } - ] - }, - { - "id": "sa-14_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-14_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-14[1]" - } - ], - "prose": "defines information systems, information system components, or information system services requiring a criticality analysis to identify critical information system components and functions;" - }, - { - "id": "sa-14_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-14[2]" - } - ], - "prose": "defines decision points in the system development life cycle when a criticality analysis is to be performed for organization-defined information systems, information system components, or information system services; and" - }, - { - "id": "sa-14_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-14[3]" - } - ], - "prose": "identifies critical information system components and functions by performing a criticality analysis for organization-defined information systems, information system components, or information system services at organization-defined decisions points in the system development life cycle." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing criticality analysis requirements for information systems, security plan\n\ncontingency plan\n\nlist of information systems, information system components, or information system services requiring criticality analyses\n\nlist of critical information system components and functions identified by criticality analyses\n\ncriticality analysis documentation\n\nbusiness impact analysis documentation\n\nsystem development life cycle documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for performing criticality analysis for the information system" - } - ] - } - ], - "controls": [ - { - "id": "sa-14.1", - "class": "SP800-53-enhancement", - "title": "Critical Components with No Viable Alternative Sourcing", - "props": [ - { - "name": "label", - "value": "SA-14(1)" - }, - { - "name": "sort-id", - "value": "sa-14.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sa-20", - "rel": "incorporated-into" - } - ] - } - ] - }, - { - "id": "sa-15", - "class": "SP800-53", - "title": "Development Process, Standards, and Tools", - "params": [ - { - "id": "sa-15_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "sa-15_prm_2", - "label": "organization-defined security requirements" - } - ], - "props": [ - { - "name": "label", - "value": "SA-15" - }, - { - "name": "sort-id", - "value": "sa-15" - } - ], - "parts": [ - { - "id": "sa-15_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sa-15_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Requires the developer of the information system, system component, or information system service to follow a documented development process that:", - "parts": [ - { - "id": "sa-15_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Explicitly addresses security requirements;" - }, - { - "id": "sa-15_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Identifies the standards and tools used in the development process;" - }, - { - "id": "sa-15_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Documents the specific tool options and tool configurations used in the development process; and" - }, - { - "id": "sa-15_smt.a.4", - "name": "item", - "props": [ - { - "name": "label", - "value": "4." - } - ], - "prose": "Documents, manages, and ensures the integrity of changes to the process and/or tools used in development; and" - } - ] - }, - { - "id": "sa-15_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews the development process, standards, tools, and tool options/configurations {{ insert: param, sa-15_prm_1 }} to determine if the process, standards, tools, and tool options/configurations selected and employed can satisfy {{ insert: param, sa-15_prm_2 }}." - } - ] - }, - { - "id": "sa-15_gdn", - "name": "guidance", - "prose": "Development tools include, for example, programming languages and computer-aided design (CAD) systems. Reviews of development processes can include, for example, the use of maturity models to determine the potential effectiveness of such processes. Maintaining the integrity of changes to tools and processes enables accurate supply chain risk assessment and mitigation, and requires robust configuration control throughout the life cycle (including design, development, transport, delivery, integration, and maintenance) to track authorized changes and prevent unauthorized changes.", - "links": [ - { - "href": "#sa-3", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - } - ] - }, - { - "id": "sa-15_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-15.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(a)" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to follow a documented development process that:", - "parts": [ - { - "id": "sa-15.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(a)(1)" - } - ], - "prose": "explicitly addresses security requirements;" - }, - { - "id": "sa-15.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(a)(2)" - } - ], - "prose": "identifies the standards and tools used in the development process;" - }, - { - "id": "sa-15.a.3_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(a)(3)" - } - ], - "parts": [ - { - "id": "sa-15.a.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(a)(3)[1]" - } - ], - "prose": "documents the specific tool options used in the development process;" - }, - { - "id": "sa-15.a.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(a)(3)[2]" - } - ], - "prose": "documents the specific tool configurations used in the development process;" - } - ] - }, - { - "id": "sa-15.a.4_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(a)(4)" - } - ], - "parts": [ - { - "id": "sa-15.a.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(a)(4)[1]" - } - ], - "prose": "documents changes to the process and/or tools used in the development;" - }, - { - "id": "sa-15.a.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(a)(4)[2]" - } - ], - "prose": "manages changes to the process and/or tools used in the development;" - }, - { - "id": "sa-15.a.4_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(a)(4)[3]" - } - ], - "prose": "ensures the integrity of changes to the process and/or tools used in the development;" - } - ] - } - ] - }, - { - "id": "sa-15.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(b)" - } - ], - "parts": [ - { - "id": "sa-15.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(b)[1]" - } - ], - "prose": "defines a frequency to review the development process, standards, tools, and tool options/configurations;" - }, - { - "id": "sa-15.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(b)[2]" - } - ], - "prose": "defines security requirements to be satisfied by the process, standards, tools, and tool option/configurations selected and employed; and" - }, - { - "id": "sa-15.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(b)[3]" - } - ], - "parts": [ - { - "id": "sa-15.b_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(b)[3][a]" - } - ], - "prose": "reviews the development process with the organization-defined frequency to determine if the process selected and employed can satisfy organization-defined security requirements;" - }, - { - "id": "sa-15.b_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(b)[3][b]" - } - ], - "prose": "reviews the development standards with the organization-defined frequency to determine if the standards selected and employed can satisfy organization-defined security requirements;" - }, - { - "id": "sa-15.b_obj.3.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(b)[3][c]" - } - ], - "prose": "reviews the development tools with the organization-defined frequency to determine if the tools selected and employed can satisfy organization-defined security requirements; and" - }, - { - "id": "sa-15.b_obj.3.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(b)[3][d]" - } - ], - "prose": "reviews the development tool options/configurations with the organization-defined frequency to determine if the tool options/configurations selected and employed can satisfy organization-defined security requirements." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing development process, standards, and tools\n\nprocedures addressing the integration of security requirements during the development process\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nsystem developer documentation listing tool options/configuration guides, configuration management records\n\nchange control records\n\nconfiguration control records\n\ndocumented reviews of development process, standards, tools, and tool options/configurations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - } - ], - "controls": [ - { - "id": "sa-15.1", - "class": "SP800-53-enhancement", - "title": "Quality Metrics", - "params": [ - { - "id": "sa-15.1_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - " {{ insert: param, sa-15.1_prm_2 }} ", - " {{ insert: param, sa-15.1_prm_3 }} ", - "upon delivery" - ] - } - }, - { - "id": "sa-15.1_prm_2", - "depends-on": "sa-15.1_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "sa-15.1_prm_3", - "depends-on": "sa-15.1_prm_1", - "label": "organization-defined program review milestones" - } - ], - "props": [ - { - "name": "label", - "value": "SA-15(1)" - }, - { - "name": "sort-id", - "value": "sa-15.01" - } - ], - "parts": [ - { - "id": "sa-15.1_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to:", - "parts": [ - { - "id": "sa-15.1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Define quality metrics at the beginning of the development process; and" - }, - { - "id": "sa-15.1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Provide evidence of meeting the quality metrics {{ insert: param, sa-15.1_prm_1 }}." - } - ] - }, - { - "id": "sa-15.1_gdn", - "name": "guidance", - "prose": "Organizations use quality metrics to establish minimum acceptable levels of information system quality. Metrics may include quality gates which are collections of completion criteria or sufficiency standards representing the satisfactory execution of particular phases of the system development project. A quality gate, for example, may require the elimination of all compiler warnings or an explicit determination that the warnings have no impact on the effectiveness of required security capabilities. During the execution phases of development projects, quality gates provide clear, unambiguous indications of progress. Other metrics apply to the entire development project. These metrics can include defining the severity thresholds of vulnerabilities, for example, requiring no known vulnerabilities in the delivered information system with a Common Vulnerability Scoring System (CVSS) severity of Medium or High." - }, - { - "id": "sa-15.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-15.1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(1)(a)" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to define quality metrics at the beginning of the development process;", - "links": [ - { - "href": "#sa-15.1_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "sa-15.1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(1)(b)" - } - ], - "parts": [ - { - "id": "sa-15.1.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(1)(b)[1]" - } - ], - "prose": "defines a frequency to provide evidence of meeting the quality metrics;" - }, - { - "id": "sa-15.1.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(1)(b)[2]" - } - ], - "prose": "defines program review milestones to provide evidence of meeting the quality metrics;" - }, - { - "id": "sa-15.1.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(1)(b)[3]" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to provide evidence of meeting the quality metrics one or more of the following:", - "parts": [ - { - "id": "sa-15.1.b_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(1)(b)[3][a]" - } - ], - "prose": "with the organization-defined frequency;" - }, - { - "id": "sa-15.1.b_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(1)(b)[3][b]" - } - ], - "prose": "in accordance with the organization-defined program review milestones; and/or" - }, - { - "id": "sa-15.1.b_obj.3.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(1)(b)[3][c]" - } - ], - "prose": "upon delivery of the information system, system component, or information system service." - } - ] - } - ], - "links": [ - { - "href": "#sa-15.1_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing development process, standards, and tools\n\nprocedures addressing the integration of security requirements into the acquisition process\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nlist of quality metrics\n\ndocumentation evidence of meeting quality metrics\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - } - ] - }, - { - "id": "sa-15.2", - "class": "SP800-53-enhancement", - "title": "Security Tracking Tools", - "props": [ - { - "name": "label", - "value": "SA-15(2)" - }, - { - "name": "sort-id", - "value": "sa-15.02" - } - ], - "parts": [ - { - "id": "sa-15.2_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to select and employ a security tracking tool for use during the development process." - }, - { - "id": "sa-15.2_gdn", - "name": "guidance", - "prose": "Information system development teams select and deploy security tracking tools, including, for example, vulnerability/work item tracking systems that facilitate assignment, sorting, filtering, and tracking of completed work items or tasks associated with system development processes." - }, - { - "id": "sa-15.2_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to select and employ a security tracking tool for use during the development process." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing development process, standards, and tools\n\nprocedures addressing the integration of security requirements into the acquisition process\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nlist of quality metrics\n\ndocumentation evidence of meeting quality metrics\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - } - ] - }, - { - "id": "sa-15.3", - "class": "SP800-53-enhancement", - "title": "Criticality Analysis", - "params": [ - { - "id": "sa-15.3_prm_1", - "label": "organization-defined breadth/depth" - }, - { - "id": "sa-15.3_prm_2", - "label": "organization-defined decision points in the system development life cycle" - } - ], - "props": [ - { - "name": "label", - "value": "SA-15(3)" - }, - { - "name": "sort-id", - "value": "sa-15.03" - } - ], - "parts": [ - { - "id": "sa-15.3_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to perform a criticality analysis at {{ insert: param, sa-15.3_prm_1 }} and at {{ insert: param, sa-15.3_prm_2 }}." - }, - { - "id": "sa-15.3_gdn", - "name": "guidance", - "prose": "This control enhancement provides developer input to the criticality analysis performed by organizations in SA-14. Developer input is essential to such analysis because organizations may not have access to detailed design documentation for information system components that are developed as commercial off-the-shelf (COTS) information technology products (e.g., functional specifications, high-level designs, low-level designs, and source code/hardware schematics).", - "links": [ - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-14", - "rel": "related" - } - ] - }, - { - "id": "sa-15.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-15.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(3)[1]" - } - ], - "prose": "defines the breadth of criticality analysis to be performed by the developer of the information system, system component, or information system service;" - }, - { - "id": "sa-15.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(3)[2]" - } - ], - "prose": "defines the depth of criticality analysis to be performed by the developer of the information system, system component, or information system service;" - }, - { - "id": "sa-15.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(3)[3]" - } - ], - "prose": "defines decision points in the system development life cycle when a criticality analysis is to be performed for the information system, system component, or information system service; and" - }, - { - "id": "sa-15.3_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(3)[4]" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to perform a criticality analysis at the organization-defined breadth/depth and at organization-defined decision points in the system development life cycle." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing development process, standards, and tools\n\nprocedures addressing criticality analysis requirements for the information system, system component, or information system service\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\ncriticality analysis documentation\n\nbusiness impact analysis documentation\n\nsoftware development life cycle documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel responsibility for performing criticality analysis\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for performing criticality analysis\n\nautomated mechanisms supporting and/or implementing criticality analysis" - } - ] - } - ] - }, - { - "id": "sa-15.4", - "class": "SP800-53-enhancement", - "title": "Threat Modeling / Vulnerability Analysis", - "params": [ - { - "id": "sa-15.4_prm_1", - "label": "organization-defined breadth/depth" - }, - { - "id": "sa-15.4_prm_2", - "label": "organization-defined information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels" - }, - { - "id": "sa-15.4_prm_3", - "label": "organization-defined tools and methods" - }, - { - "id": "sa-15.4_prm_4", - "label": "organization-defined acceptance criteria" - } - ], - "props": [ - { - "name": "label", - "value": "SA-15(4)" - }, - { - "name": "sort-id", - "value": "sa-15.04" - } - ], - "parts": [ - { - "id": "sa-15.4_smt", - "name": "statement", - "prose": "The organization requires that developers perform threat modeling and a vulnerability analysis for the information system at {{ insert: param, sa-15.4_prm_1 }} that:", - "parts": [ - { - "id": "sa-15.4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Uses {{ insert: param, sa-15.4_prm_2 }};" - }, - { - "id": "sa-15.4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Employs {{ insert: param, sa-15.4_prm_3 }}; and" - }, - { - "id": "sa-15.4_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Produces evidence that meets {{ insert: param, sa-15.4_prm_4 }}." - } - ] - }, - { - "id": "sa-15.4_gdn", - "name": "guidance", - "links": [ - { - "href": "#sa-4", - "rel": "related" - } - ] - }, - { - "id": "sa-15.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-15.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(4)[1]" - } - ], - "prose": "defines the breadth of threat modeling and vulnerability analysis to be performed by developers for the information system;" - }, - { - "id": "sa-15.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(4)[2]" - } - ], - "prose": "defines the depth of threat modeling and vulnerability analysis to be performed by developers for the information system;" - }, - { - "id": "sa-15.4_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(4)[3]" - } - ], - "prose": "defines information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels to be used in threat modeling and vulnerability analysis;" - }, - { - "id": "sa-15.4_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(4)[4]" - } - ], - "prose": "defines tools and methods to be employed in threat modeling and vulnerability analysis;" - }, - { - "id": "sa-15.4_obj.5", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(4)[5]" - } - ], - "prose": "defines acceptance criteria for evidence produced from threat modeling and vulnerability analysis;" - }, - { - "id": "sa-15.4_obj.6", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(4)[6]" - } - ], - "prose": "requires that developers perform threat modeling and a vulnerability analysis for the information system at the organization-defined breadth/depth that:", - "parts": [ - { - "id": "sa-15.4.a_obj.6", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(4)[6](a)" - } - ], - "prose": "uses organization-defined information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels;", - "links": [ - { - "href": "#sa-15.4_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "sa-15.4.b_obj.6", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(4)[6](b)" - } - ], - "prose": "employs organization-defined tools and methods; and", - "links": [ - { - "href": "#sa-15.4_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "sa-15.4.c_obj.6", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(4)[6](c)" - } - ], - "prose": "produces evidence that meets organization-defined acceptance criteria.", - "links": [ - { - "href": "#sa-15.4_smt.c", - "rel": "corresp" - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing development process, standards, and tools\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nthreat modeling documentation\n\nvulnerability analysis results\n\norganizational risk assessments\n\nacceptance criteria for evidence produced from threat modeling and vulnerability analysis\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for performing development threat modeling and vulnerability analysis\n\nautomated mechanisms supporting and/or implementing development threat modeling and vulnerability analysis" - } - ] - } - ] - }, - { - "id": "sa-15.5", - "class": "SP800-53-enhancement", - "title": "Attack Surface Reduction", - "params": [ - { - "id": "sa-15.5_prm_1", - "label": "organization-defined thresholds" - } - ], - "props": [ - { - "name": "label", - "value": "SA-15(5)" - }, - { - "name": "sort-id", - "value": "sa-15.05" - } - ], - "parts": [ - { - "id": "sa-15.5_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to reduce attack surfaces to {{ insert: param, sa-15.5_prm_1 }}." - }, - { - "id": "sa-15.5_gdn", - "name": "guidance", - "prose": "Attack surface reduction is closely aligned with developer threat and vulnerability analyses and information system architecture and design. Attack surface reduction is a means of reducing risk to organizations by giving attackers less opportunity to exploit weaknesses or deficiencies (i.e., potential vulnerabilities) within information systems, information system components, and information system services. Attack surface reduction includes, for example, applying the principle of least privilege, employing layered defenses, applying the principle of least functionality (i.e., restricting ports, protocols, functions, and services), deprecating unsafe functions, and eliminating application programming interfaces (APIs) that are vulnerable to cyber attacks.", - "links": [ - { - "href": "#cm-7", - "rel": "related" - } - ] - }, - { - "id": "sa-15.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-15.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(5)[1]" - } - ], - "prose": "defines thresholds to which attack surfaces are to be reduced; and" - }, - { - "id": "sa-15.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(5)[2]" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to reduce attack surfaces to organization-defined thresholds." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing development process, standards, and tools\n\nprocedures addressing attack surface reduction\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, or information system service\n\ninformation system design documentation\n\nnetwork diagram\n\ninformation system configuration settings and associated documentation establishing/enforcing organization-defined thresholds for reducing attack surfaces\n\nlist of restricted ports, protocols, functions and services\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel responsibility for attack surface reduction thresholds\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for defining attack surface reduction thresholds" - } - ] - } - ] - }, - { - "id": "sa-15.6", - "class": "SP800-53-enhancement", - "title": "Continuous Improvement", - "props": [ - { - "name": "label", - "value": "SA-15(6)" - }, - { - "name": "sort-id", - "value": "sa-15.06" - } - ], - "parts": [ - { - "id": "sa-15.6_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to implement an explicit process to continuously improve the development process." - }, - { - "id": "sa-15.6_gdn", - "name": "guidance", - "prose": "Developers of information systems, information system components, and information system services consider the effectiveness/efficiency of current development processes for meeting quality objectives and addressing security capabilities in current threat environments." - }, - { - "id": "sa-15.6_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to implement an explicit process to continuously improve the development process." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing development process, standards, and tools\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nquality goals and metrics for improving system development process\n\nsecurity assessments and/or quality control reviews of system development process\n\nplans of action and milestones for improving system development process\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - } - ] - }, - { - "id": "sa-15.7", - "class": "SP800-53-enhancement", - "title": "Automated Vulnerability Analysis", - "params": [ - { - "id": "sa-15.7_prm_1", - "label": "organization-defined tools" - }, - { - "id": "sa-15.7_prm_2", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "SA-15(7)" - }, - { - "name": "sort-id", - "value": "sa-15.07" - } - ], - "parts": [ - { - "id": "sa-15.7_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to:", - "parts": [ - { - "id": "sa-15.7_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Perform an automated vulnerability analysis using {{ insert: param, sa-15.7_prm_1 }};" - }, - { - "id": "sa-15.7_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Determine the exploitation potential for discovered vulnerabilities;" - }, - { - "id": "sa-15.7_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Determine potential risk mitigations for delivered vulnerabilities; and" - }, - { - "id": "sa-15.7_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "(d)" - } - ], - "prose": "Deliver the outputs of the tools and results of the analysis to {{ insert: param, sa-15.7_prm_2 }}." - } - ] - }, - { - "id": "sa-15.7_gdn", - "name": "guidance", - "links": [ - { - "href": "#ra-5", - "rel": "related" - } - ] - }, - { - "id": "sa-15.7_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-15.7.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(7)(a)" - } - ], - "parts": [ - { - "id": "sa-15.7.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(7)(a)[1]" - } - ], - "prose": "defines tools to be used to perform automated vulnerability analysis of the information system, system component, or information system service;" - }, - { - "id": "sa-15.7.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(7)(a)[2]" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to perform an automated vulnerability analysis using organization-defined tools;" - } - ], - "links": [ - { - "href": "#sa-15.7_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "sa-15.7.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(7)(b)" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to determine the exploitation potential for discovered vulnerabilities;", - "links": [ - { - "href": "#sa-15.7_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "sa-15.7.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(7)(c)" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to determine potential risk mitigations for delivered vulnerabilities;", - "links": [ - { - "href": "#sa-15.7_smt.c", - "rel": "corresp" - } - ] - }, - { - "id": "sa-15.7.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(7)(d)" - } - ], - "parts": [ - { - "id": "sa-15.7.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(7)(d)[1]" - } - ], - "prose": "defines personnel or roles to whom the output of the tools and results of the analysis are to be delivered; and" - }, - { - "id": "sa-15.7.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(7)(d)[2]" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to deliver the outputs of the tools and results of the analysis to organization-defined personnel or roles." - } - ], - "links": [ - { - "href": "#sa-15.7_smt.d", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing development process, standards, and tools\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nvulnerability analysis tools and associated documentation\n\nrisk assessment reports\n\nvulnerability analysis results\n\nvulnerability mitigation reports\n\nrisk mitigation strategy documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel performing automated vulnerability analysis on the information system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for vulnerability analysis of information systems, system components, or information system services under development\n\nautomated mechanisms supporting and/or implementing vulnerability analysis of information systems, system components, or information system services under development" - } - ] - } - ] - }, - { - "id": "sa-15.8", - "class": "SP800-53-enhancement", - "title": "Reuse of Threat / Vulnerability Information", - "props": [ - { - "name": "label", - "value": "SA-15(8)" - }, - { - "name": "sort-id", - "value": "sa-15.08" - } - ], - "parts": [ - { - "id": "sa-15.8_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to use threat modeling and vulnerability analyses from similar systems, components, or services to inform the current development process." - }, - { - "id": "sa-15.8_gdn", - "name": "guidance", - "prose": "Analysis of vulnerabilities found in similar software applications can inform potential design or implementation issues for information systems under development. Similar information systems or system components may exist within developer organizations. Authoritative vulnerability information is available from a variety of public and private sector sources including, for example, the National Vulnerability Database." - }, - { - "id": "sa-15.8_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to use threat modeling and vulnerability analyses from similar systems, components, or services to inform the current development process." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing development process, standards, and tools\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nthreat modeling and vulnerability analyses from similar information systems, system components, or information system service\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - } - ] - }, - { - "id": "sa-15.9", - "class": "SP800-53-enhancement", - "title": "Use of Live Data", - "props": [ - { - "name": "label", - "value": "SA-15(9)" - }, - { - "name": "sort-id", - "value": "sa-15.09" - } - ], - "parts": [ - { - "id": "sa-15.9_smt", - "name": "statement", - "prose": "The organization approves, documents, and controls the use of live data in development and test environments for the information system, system component, or information system service." - }, - { - "id": "sa-15.9_gdn", - "name": "guidance", - "prose": "The use of live data in preproduction environments can result in significant risk to organizations. Organizations can minimize such risk by using test or dummy data during the development and testing of information systems, information system components, and information system services." - }, - { - "id": "sa-15.9_obj", - "name": "objective", - "prose": "Determine if the organization, for the information system, system component, or information system service:", - "parts": [ - { - "id": "sa-15.9_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(9)[1]" - } - ], - "prose": "approves the use of live data in development and test environments;" - }, - { - "id": "sa-15.9_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(9)[2]" - } - ], - "prose": "documents the use of live data in development and test environments; and" - }, - { - "id": "sa-15.9_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-15(9)[3]" - } - ], - "prose": "controls the use of live data in development and test environments." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing development process, standards, and tools\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ndocumentation authorizing use of live data in development and test environments\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for approving, documenting, and controlling the use of live data in development and test environments\n\nautomated mechanisms supporting and/or implementing the approval, documentation, and control of the use of live data in development and test environments" - } - ] - } - ] - }, - { - "id": "sa-15.10", - "class": "SP800-53-enhancement", - "title": "Incident Response Plan", - "props": [ - { - "name": "label", - "value": "SA-15(10)" - }, - { - "name": "sort-id", - "value": "sa-15.10" - } - ], - "parts": [ - { - "id": "sa-15.10_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to provide an incident response plan." - }, - { - "id": "sa-15.10_gdn", - "name": "guidance", - "prose": "The incident response plan for developers of information systems, system components, and information system services is incorporated into organizational incident response plans to provide the type of incident response information not readily available to organizations. Such information may be extremely helpful, for example, when organizations respond to vulnerabilities in commercial off-the-shelf (COTS) information technology products.", - "links": [ - { - "href": "#ir-8", - "rel": "related" - } - ] - }, - { - "id": "sa-15.10_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to provide an incident response plan." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing development process, standards, and tools\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, or services\n\nacquisition documentation\n\nsolicitation documentation\n\nservice-level agreements\n\ndeveloper incident response plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - } - ] - }, - { - "id": "sa-15.11", - "class": "SP800-53-enhancement", - "title": "Archive Information System / Component", - "props": [ - { - "name": "label", - "value": "SA-15(11)" - }, - { - "name": "sort-id", - "value": "sa-15.11" - } - ], - "parts": [ - { - "id": "sa-15.11_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system or system component to archive the system or component to be released or delivered together with the corresponding evidence supporting the final security review." - }, - { - "id": "sa-15.11_gdn", - "name": "guidance", - "prose": "Archiving relevant documentation from the development process can provide a readily available baseline of information that can be helpful during information system/component upgrades or modifications." - }, - { - "id": "sa-15.11_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system or system component to archive the system or component to be released or delivered together with the corresponding evidence supporting the final security review." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing development process, standards, and tools\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, or services\n\nacquisition documentation\n\nsolicitation documentation\n\nservice-level agreements\n\ndeveloper incident response plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - } - ] - } - ] - }, - { - "id": "sa-16", - "class": "SP800-53", - "title": "Developer-provided Training", - "params": [ - { - "id": "sa-16_prm_1", - "label": "organization-defined training" - } - ], - "props": [ - { - "name": "label", - "value": "SA-16" - }, - { - "name": "sort-id", - "value": "sa-16" - } - ], - "parts": [ - { - "id": "sa-16_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to provide {{ insert: param, sa-16_prm_1 }} on the correct use and operation of the implemented security functions, controls, and/or mechanisms." - }, - { - "id": "sa-16_gdn", - "name": "guidance", - "prose": "This control applies to external and internal (in-house) developers. Training of personnel is an essential element to ensure the effectiveness of security controls implemented within organizational information systems. Training options include, for example, classroom-style training, web-based/computer-based training, and hands-on training. Organizations can also request sufficient training materials from developers to conduct in-house training or offer self-training to organizational personnel. Organizations determine the type of training necessary and may require different types of training for different security functions, controls, or mechanisms.", - "links": [ - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - } - ] - }, - { - "id": "sa-16_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-16_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-16[1]" - } - ], - "prose": "defines training to be provided by the developer of the information system, system component, or information system service; and" - }, - { - "id": "sa-16_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-16[2]" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to provide organization-defined training on the correct use and operation of the implemented security functions, controls, and/or mechanisms." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing developer-provided training\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\ndeveloper-provided training materials\n\ntraining records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information system security responsibilities\n\nsystem developer\n\norganizational or third-party developers with training responsibilities for the information system, system component, or information system service" - } - ] - } - ] - }, - { - "id": "sa-17", - "class": "SP800-53", - "title": "Developer Security Architecture and Design", - "props": [ - { - "name": "label", - "value": "SA-17" - }, - { - "name": "sort-id", - "value": "sa-17" - } - ], - "parts": [ - { - "id": "sa-17_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to produce a design specification and security architecture that:", - "parts": [ - { - "id": "sa-17_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Is consistent with and supportive of the organization’s security architecture which is established within and is an integrated part of the organization’s enterprise architecture;" - }, - { - "id": "sa-17_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Accurately and completely describes the required security functionality, and the allocation of security controls among physical and logical components; and" - }, - { - "id": "sa-17_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Expresses how individual security functions, mechanisms, and services work together to provide required security capabilities and a unified approach to protection." - } - ] - }, - { - "id": "sa-17_gdn", - "name": "guidance", - "prose": "This control is primarily directed at external developers, although it could also be used for internal (in-house) development. In contrast, PL-8 is primarily directed at internal developers to help ensure that organizations develop an information security architecture and such security architecture is integrated or tightly coupled to the enterprise architecture. This distinction is important if/when organizations outsource the development of information systems, information system components, or information system services to external entities, and there is a requirement to demonstrate consistency with the organization’s enterprise architecture and information security architecture.", - "links": [ - { - "href": "#pl-8", - "rel": "related" - }, - { - "href": "#pm-7", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - } - ] - }, - { - "id": "sa-17_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to produce a design specification and security architecture that:", - "parts": [ - { - "id": "sa-17.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(a)" - } - ], - "prose": "is consistent with and supportive of the organization’s security architecture which is established within and is an integrated part of the organization’s enterprise architecture;" - }, - { - "id": "sa-17.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(b)" - } - ], - "prose": "accurately and completely describes:", - "parts": [ - { - "id": "sa-17.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(b)[1]" - } - ], - "prose": "the required security functionality;" - }, - { - "id": "sa-17.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(b)[2]" - } - ], - "prose": "the allocation of security controls among physical and logical components; and" - } - ] - }, - { - "id": "sa-17.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(c)" - } - ], - "prose": "expresses how individual security functions, mechanisms, and services work together to provide required security capabilities and a unified approach to protection." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nenterprise architecture policy\n\nprocedures addressing developer security architecture and design specification for the information system\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\ndesign specification and security architecture documentation for the system\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with security architecture and design responsibilities" - } - ] - } - ], - "controls": [ - { - "id": "sa-17.1", - "class": "SP800-53-enhancement", - "title": "Formal Policy Model", - "params": [ - { - "id": "sa-17.1_prm_1", - "label": "organization-defined elements of organizational security policy" - } - ], - "props": [ - { - "name": "label", - "value": "SA-17(1)" - }, - { - "name": "sort-id", - "value": "sa-17.01" - } - ], - "parts": [ - { - "id": "sa-17.1_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to:", - "parts": [ - { - "id": "sa-17.1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Produce, as an integral part of the development process, a formal policy model describing the {{ insert: param, sa-17.1_prm_1 }} to be enforced; and" - }, - { - "id": "sa-17.1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Prove that the formal policy model is internally consistent and sufficient to enforce the defined elements of the organizational security policy when implemented." - } - ] - }, - { - "id": "sa-17.1_gdn", - "name": "guidance", - "prose": "Formal models describe specific behaviors or security policies using formal languages, thus enabling the correctness of those behaviors/policies to be formally proven. Not all components of information systems can be modeled, and generally, formal specifications are scoped to specific behaviors or policies of interest (e.g., nondiscretionary access control policies). Organizations choose the particular formal modeling language and approach based on the nature of the behaviors/policies to be described and the available tools. Formal modeling tools include, for example, Gypsy and Zed." - }, - { - "id": "sa-17.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-17.1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(1)(a)" - } - ], - "parts": [ - { - "id": "sa-17.1.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(1)(a)[1]" - } - ], - "prose": "defines elements of the organizational security policy to be enforced under a formal policy model produced by the developer as an integral part of the development process for the information system, system component, or information system service;" - }, - { - "id": "sa-17.1.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(1)(a)[2]" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to produce, as an integral part of the development process, a formal policy model describing the organization-defined elements of organizational security policy to be enforced; and" - } - ], - "links": [ - { - "href": "#sa-17.1_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "sa-17.1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(1)(b)" - } - ], - "prose": "requires the developer of the information system, system component, or information system service to prove that the formal policy model is internally consistent and sufficient to enforce the defined elements of the organizational security policy when implemented.", - "links": [ - { - "href": "#sa-17.1_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nenterprise architecture policy\n\nprocedures addressing developer security architecture and design specification for the information system\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\ndesign specification and security architecture documentation for the system\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with security architecture and design responsibilities" - } - ] - } - ] - }, - { - "id": "sa-17.2", - "class": "SP800-53-enhancement", - "title": "Security-relevant Components", - "props": [ - { - "name": "label", - "value": "SA-17(2)" - }, - { - "name": "sort-id", - "value": "sa-17.02" - } - ], - "parts": [ - { - "id": "sa-17.2_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to:", - "parts": [ - { - "id": "sa-17.2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Define security-relevant hardware, software, and firmware; and" - }, - { - "id": "sa-17.2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Provide a rationale that the definition for security-relevant hardware, software, and firmware is complete." - } - ] - }, - { - "id": "sa-17.2_gdn", - "name": "guidance", - "prose": "Security-relevant hardware, software, and firmware represent the portion of the information system, component, or service that must be trusted to perform correctly in order to maintain required security properties.", - "links": [ - { - "href": "#sa-5", - "rel": "related" - } - ] - }, - { - "id": "sa-17.2_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to:", - "parts": [ - { - "id": "sa-17.2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(2)(a)" - } - ], - "parts": [ - { - "id": "sa-17.2.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(2)(a)[1]" - } - ], - "prose": "define security-relevant hardware;" - }, - { - "id": "sa-17.2.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(2)(a)[2]" - } - ], - "prose": "define security-relevant software;" - }, - { - "id": "sa-17.2.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(2)(a)[3]" - } - ], - "prose": "define security-relevant firmware; and" - } - ], - "links": [ - { - "href": "#sa-17.2_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "sa-17.2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(2)(b)" - } - ], - "prose": "provide a rationale that the definition for security-relevant hardware, software, and firmware components is complete.", - "links": [ - { - "href": "#sa-17.2_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nenterprise architecture policy\n\nprocedures addressing developer security architecture and design specification for the information system\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nlist of security-relevant hardware, software, and firmware components\n\ndocumented rationale of completeness regarding definitions provided for security-relevant hardware, software, and firmware\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developers\n\norganizational personnel with security architecture and design responsibilities" - } - ] - } - ] - }, - { - "id": "sa-17.3", - "class": "SP800-53-enhancement", - "title": "Formal Correspondence", - "props": [ - { - "name": "label", - "value": "SA-17(3)" - }, - { - "name": "sort-id", - "value": "sa-17.03" - } - ], - "parts": [ - { - "id": "sa-17.3_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to:", - "parts": [ - { - "id": "sa-17.3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Produce, as an integral part of the development process, a formal top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of exceptions, error messages, and effects;" - }, - { - "id": "sa-17.3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Show via proof to the extent feasible with additional informal demonstration as necessary, that the formal top-level specification is consistent with the formal policy model;" - }, - { - "id": "sa-17.3_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Show via informal demonstration, that the formal top-level specification completely covers the interfaces to security-relevant hardware, software, and firmware;" - }, - { - "id": "sa-17.3_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "(d)" - } - ], - "prose": "Show that the formal top-level specification is an accurate description of the implemented security-relevant hardware, software, and firmware; and" - }, - { - "id": "sa-17.3_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "(e)" - } - ], - "prose": "Describe the security-relevant hardware, software, and firmware mechanisms not addressed in the formal top-level specification but strictly internal to the security-relevant hardware, software, and firmware." - } - ] - }, - { - "id": "sa-17.3_gdn", - "name": "guidance", - "prose": "Correspondence is an important part of the assurance gained through modeling. It demonstrates that the implementation is an accurate transformation of the model, and that any additional code or implementation details present have no impact on the behaviors or policies being modeled. Formal methods can be used to show that the high-level security properties are satisfied by the formal information system description, and that the formal system description is correctly implemented by a description of some lower level, for example a hardware description. Consistency between the formal top-level specification and the formal policy models is generally not amenable to being fully proven. Therefore, a combination of formal/informal methods may be needed to show such consistency. Consistency between the formal top-level specification and the implementation may require the use of an informal demonstration due to limitations in the applicability of formal methods to prove that the specification accurately reflects the implementation. Hardware, software, and firmware mechanisms strictly internal to security-relevant hardware, software, and firmware include, for example, mapping registers and direct memory input/output.", - "links": [ - { - "href": "#sa-5", - "rel": "related" - } - ] - }, - { - "id": "sa-17.3_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to:", - "parts": [ - { - "id": "sa-17.3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(3)(a)" - } - ], - "prose": "produce, as an integral part of the development process, a formal top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of:", - "parts": [ - { - "id": "sa-17.3.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(3)(a)[1]" - } - ], - "prose": "exceptions;" - }, - { - "id": "sa-17.3.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(3)(a)[2]" - } - ], - "prose": "error messages;" - }, - { - "id": "sa-17.3.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(3)(a)[3]" - } - ], - "prose": "effects;" - } - ], - "links": [ - { - "href": "#sa-17.3_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "sa-17.3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(3)(b)" - } - ], - "prose": "show via proof to the extent feasible with additional informal demonstration as necessary, that the formal top-level specification is consistent with the formal policy model;", - "links": [ - { - "href": "#sa-17.3_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "sa-17.3.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(3)(c)" - } - ], - "prose": "show via informal demonstration, that the formal top-level specification completely covers the interfaces to security-relevant hardware, software, and firmware;", - "links": [ - { - "href": "#sa-17.3_smt.c", - "rel": "corresp" - } - ] - }, - { - "id": "sa-17.3.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(3)(d)" - } - ], - "prose": "show that the formal top-level specification is an accurate description of the implemented security-relevant hardware, software, and firmware; and", - "links": [ - { - "href": "#sa-17.3_smt.d", - "rel": "corresp" - } - ] - }, - { - "id": "sa-17.3.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(3)(e)" - } - ], - "prose": "describe the security-relevant hardware, software, and firmware mechanisms not addressed in the formal top-level specification but strictly internal to the security-relevant hardware, software, and firmware.", - "links": [ - { - "href": "#sa-17.3_smt.e", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nenterprise architecture policy\n\nformal policy model\n\nprocedures addressing developer security architecture and design specification for the information system\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\nformal top-level specification documentation\n\ninformation system security architecture and design documentation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ndocumentation describing security-relevant hardware, software and firmware mechanisms not addressed in the formal top-level specification documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with security architecture and design responsibilities" - } - ] - } - ] - }, - { - "id": "sa-17.4", - "class": "SP800-53-enhancement", - "title": "Informal Correspondence", - "params": [ - { - "id": "sa-17.4_prm_1", - "select": { - "choice": [ - "informal demonstration, convincing argument with formal methods as feasible" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "SA-17(4)" - }, - { - "name": "sort-id", - "value": "sa-17.04" - } - ], - "parts": [ - { - "id": "sa-17.4_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to:", - "parts": [ - { - "id": "sa-17.4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Produce, as an integral part of the development process, an informal descriptive top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of exceptions, error messages, and effects;" - }, - { - "id": "sa-17.4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Show via {{ insert: param, sa-17.4_prm_1 }} that the descriptive top-level specification is consistent with the formal policy model;" - }, - { - "id": "sa-17.4_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Show via informal demonstration, that the descriptive top-level specification completely covers the interfaces to security-relevant hardware, software, and firmware;" - }, - { - "id": "sa-17.4_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "(d)" - } - ], - "prose": "Show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant hardware, software, and firmware; and" - }, - { - "id": "sa-17.4_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "(e)" - } - ], - "prose": "Describe the security-relevant hardware, software, and firmware mechanisms not addressed in the descriptive top-level specification but strictly internal to the security-relevant hardware, software, and firmware." - } - ] - }, - { - "id": "sa-17.4_gdn", - "name": "guidance", - "prose": "Correspondence is an important part of the assurance gained through modeling. It demonstrates that the implementation is an accurate transformation of the model, and that any additional code or implementation details present has no impact on the behaviors or policies being modeled. Consistency between the descriptive top-level specification (i.e., high-level/low-level design) and the formal policy model is generally not amenable to being fully proven. Therefore, a combination of formal/informal methods may be needed to show such consistency. Hardware, software, and firmware mechanisms strictly internal to security-relevant hardware, software, and firmware include, for example, mapping registers and direct memory input/output.", - "links": [ - { - "href": "#sa-5", - "rel": "related" - } - ] - }, - { - "id": "sa-17.4_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to:", - "parts": [ - { - "id": "sa-17.4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(4)(a)" - } - ], - "prose": "produce, as an integral part of the development process, an informal descriptive top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of:", - "parts": [ - { - "id": "sa-17.4.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(4)(a)[1]" - } - ], - "prose": "exceptions;" - }, - { - "id": "sa-17.4.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(4)(a)[2]" - } - ], - "prose": "error messages;" - }, - { - "id": "sa-17.4.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(4)(a)[3]" - } - ], - "prose": "effects;" - } - ], - "links": [ - { - "href": "#sa-17.4_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "sa-17.4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(4)(b)" - } - ], - "prose": "show via informal demonstration and/or convincing argument with formal methods as feasible that the descriptive top-level specification is consistent with the formal policy model;", - "links": [ - { - "href": "#sa-17.4_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "sa-17.4.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(4)(c)" - } - ], - "prose": "show via informal demonstration, that the descriptive top-level specification completely covers the interfaces to security-relevant hardware, software, and firmware;", - "links": [ - { - "href": "#sa-17.4_smt.c", - "rel": "corresp" - } - ] - }, - { - "id": "sa-17.4.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(4)(d)" - } - ], - "prose": "show that the descriptive top-level specification is an accurate description of the interfaces to the security-relevant hardware, software, and firmware; and", - "links": [ - { - "href": "#sa-17.4_smt.d", - "rel": "corresp" - } - ] - }, - { - "id": "sa-17.4.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(4)(e)" - } - ], - "prose": "describe the security-relevant hardware, software, and firmware mechanisms not addressed in the descriptive top-level specification but strictly internal to the security-relevant hardware, software, and firmware.", - "links": [ - { - "href": "#sa-17.4_smt.e", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nenterprise architecture policy\n\nformal policy model\n\nprocedures addressing developer security architecture and design specification for the information system\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\ninformal descriptive top-level specification documentation\n\ninformation system security architecture and design documentation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ndocumentation describing security-relevant hardware, software and firmware mechanisms not addressed in the informal descriptive top-level specification documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with security architecture and design responsibilities" - } - ] - } - ] - }, - { - "id": "sa-17.5", - "class": "SP800-53-enhancement", - "title": "Conceptually Simple Design", - "props": [ - { - "name": "label", - "value": "SA-17(5)" - }, - { - "name": "sort-id", - "value": "sa-17.05" - } - ], - "parts": [ - { - "id": "sa-17.5_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to:", - "parts": [ - { - "id": "sa-17.5_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Design and structure the security-relevant hardware, software, and firmware to use a complete, conceptually simple protection mechanism with precisely defined semantics; and" - }, - { - "id": "sa-17.5_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Internally structure the security-relevant hardware, software, and firmware with specific regard for this mechanism." - } - ] - }, - { - "id": "sa-17.5_gdn", - "name": "guidance", - "links": [ - { - "href": "#sc-3", - "rel": "related" - } - ] - }, - { - "id": "sa-17.5_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to:", - "parts": [ - { - "id": "sa-17.5.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(5)(a)" - } - ], - "prose": "design and structure the security-relevant hardware, software, and firmware to use a complete, conceptually simple protection mechanism with precisely defined semantics; and", - "links": [ - { - "href": "#sa-17.5_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "sa-17.5.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-17(5)(b)" - } - ], - "prose": "internally structure the security-relevant hardware, software, and firmware with specific regard for this mechanism.", - "links": [ - { - "href": "#sa-17.5_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nenterprise architecture policy\n\nprocedures addressing developer security architecture and design specification for the information system\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\ninformation system design documentation\n\ninformation system security architecture documentation\n\ninformation system configuration settings and associated documentation\n\ndeveloper documentation describing design and structure of security-relevant hardware, software, and firmware components\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with security architecture and design responsibilities" - } - ] - } - ] - }, - { - "id": "sa-17.6", - "class": "SP800-53-enhancement", - "title": "Structure for Testing", - "props": [ - { - "name": "label", - "value": "SA-17(6)" - }, - { - "name": "sort-id", - "value": "sa-17.06" - } - ], - "parts": [ - { - "id": "sa-17.6_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to structure security-relevant hardware, software, and firmware to facilitate testing." - }, - { - "id": "sa-17.6_gdn", - "name": "guidance", - "links": [ - { - "href": "#sa-11", - "rel": "related" - } - ] - }, - { - "id": "sa-17.6_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to structure security-relevant hardware, software, and firmware to facilitate testing." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nenterprise architecture policy\n\nprocedures addressing developer security architecture and design specification for the information system\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\ninformation system design documentation\n\ninformation system security architecture documentation\n\ninformation system configuration settings and associated documentation\n\ndeveloper documentation describing design and structure of security-relevant hardware, software, and firmware components to facilitate testing\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with security architecture and design responsibilities" - } - ] - } - ] - }, - { - "id": "sa-17.7", - "class": "SP800-53-enhancement", - "title": "Structure for Least Privilege", - "props": [ - { - "name": "label", - "value": "SA-17(7)" - }, - { - "name": "sort-id", - "value": "sa-17.07" - } - ], - "parts": [ - { - "id": "sa-17.7_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service to structure security-relevant hardware, software, and firmware to facilitate controlling access with least privilege." - }, - { - "id": "sa-17.7_gdn", - "name": "guidance", - "links": [ - { - "href": "#ac-5", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - } - ] - }, - { - "id": "sa-17.7_obj", - "name": "objective", - "prose": "Determine if the organization requires the developer of the information system, system component, or information system service to structure security-relevant hardware, software, and firmware to facilitate controlling access with least privilege." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nenterprise architecture policy\n\nprocedures addressing developer security architecture and design specification for the information system\n\nsolicitation documentation\n\nacquisition documentation\n\nservice-level agreements\n\nacquisition contracts for the information system, system component, or information system service\n\ninformation system design documentation\n\ninformation system security architecture documentation\n\ninformation system configuration settings and associated documentation\n\ndeveloper documentation describing design and structure of security-relevant hardware, software, and firmware components to facilitate controlling access with least privilege\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with security architecture and design responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "sa-18", - "class": "SP800-53", - "title": "Tamper Resistance and Detection", - "props": [ - { - "name": "label", - "value": "SA-18" - }, - { - "name": "sort-id", - "value": "sa-18" - } - ], - "parts": [ - { - "id": "sa-18_smt", - "name": "statement", - "prose": "The organization implements a tamper protection program for the information system, system component, or information system service." - }, - { - "id": "sa-18_gdn", - "name": "guidance", - "prose": "Anti-tamper technologies and techniques provide a level of protection for critical information systems, system components, and information technology products against a number of related threats including modification, reverse engineering, and substitution. Strong identification combined with tamper resistance and/or tamper detection is essential to protecting information systems, components, and products during distribution and when in use.", - "links": [ - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#sa-12", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "sa-18_obj", - "name": "objective", - "prose": "Determine if the organization implements a tamper protection program for the information system, system component, or information system service." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing tamper resistance and detection\n\ntamper protection program documentation\n\ntamper protection tools and techniques documentation\n\ntamper resistance and detection tools and techniques documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for the tamper protection program" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for implementation of the tamper protection program\n\nautomated mechanisms supporting and/or implementing the tamper protection program" - } - ] - } - ], - "controls": [ - { - "id": "sa-18.1", - "class": "SP800-53-enhancement", - "title": "Multiple Phases of SDLC", - "props": [ - { - "name": "label", - "value": "SA-18(1)" - }, - { - "name": "sort-id", - "value": "sa-18.01" - } - ], - "parts": [ - { - "id": "sa-18.1_smt", - "name": "statement", - "prose": "The organization employs anti-tamper technologies and techniques during multiple phases in the system development life cycle including design, development, integration, operations, and maintenance." - }, - { - "id": "sa-18.1_gdn", - "name": "guidance", - "prose": "Organizations use a combination of hardware and software techniques for tamper resistance and detection. Organizations employ obfuscation and self-checking, for example, to make reverse engineering and modifications more difficult, time-consuming, and expensive for adversaries. Customization of information systems and system components can make substitutions easier to detect and therefore limit damage.", - "links": [ - { - "href": "#sa-3", - "rel": "related" - } - ] - }, - { - "id": "sa-18.1_obj", - "name": "objective", - "prose": "Determine if the organization employs anti-tamper technologies and techniques during multiple phases in the system development life cycle including:", - "parts": [ - { - "id": "sa-18.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-18(1)[1]" - } - ], - "prose": "design;" - }, - { - "id": "sa-18.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-18(1)[2]" - } - ], - "prose": "development;" - }, - { - "id": "sa-18.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-18(1)[3]" - } - ], - "prose": "integration;" - }, - { - "id": "sa-18.1_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-18(1)[4]" - } - ], - "prose": "operations; and" - }, - { - "id": "sa-18.1_obj.5", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-18(1)[5]" - } - ], - "prose": "maintenance." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing tamper resistance and detection\n\ntamper protection program documentation\n\ntamper protection tools and techniques documentation\n\ntamper resistance and detection tools (technologies) and techniques documentation\n\nsystem development life cycle documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for the tamper protection program\n\norganizational personnel with SDLC responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for employing anti-tamper technologies\n\nautomated mechanisms supporting and/or implementing anti-tamper technologies" - } - ] - } - ] - }, - { - "id": "sa-18.2", - "class": "SP800-53-enhancement", - "title": "Inspection of Information Systems, Components, or Devices", - "params": [ - { - "id": "sa-18.2_prm_1", - "label": "organization-defined information systems, system components, or devices" - }, - { - "id": "sa-18.2_prm_2", - "select": { - "how-many": "one-or-more", - "choice": [ - "at random", - "at {{ insert: param, sa-18.2_prm_3 }}, upon {{ insert: param, sa-18.2_prm_4 }} " - ] - } - }, - { - "id": "sa-18.2_prm_3", - "depends-on": "sa-18.2_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "sa-18.2_prm_4", - "depends-on": "sa-18.2_prm_2", - "label": "organization-defined indications of need for inspection" - } - ], - "props": [ - { - "name": "label", - "value": "SA-18(2)" - }, - { - "name": "sort-id", - "value": "sa-18.02" - } - ], - "parts": [ - { - "id": "sa-18.2_smt", - "name": "statement", - "prose": "The organization inspects {{ insert: param, sa-18.2_prm_1 }} {{ insert: param, sa-18.2_prm_2 }} to detect tampering." - }, - { - "id": "sa-18.2_gdn", - "name": "guidance", - "prose": "This control enhancement addresses both physical and logical tampering and is typically applied to mobile devices, notebook computers, or other system components taken out of organization-controlled areas. Indications of need for inspection include, for example, when individuals return from travel to high-risk locations.", - "links": [ - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "sa-18.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-18.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-18(2)[1]" - } - ], - "prose": "defines information systems, system components, or devices to be inspected to detect tampering;" - }, - { - "id": "sa-18.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-18(2)[2]" - } - ], - "prose": "defines the frequency to inspect organization-defined information systems, system components, or devices to detect tampering;" - }, - { - "id": "sa-18.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-18(2)[3]" - } - ], - "prose": "defines indications of need for inspection of organization-defined information systems, system components, or devices to detect tampering;" - }, - { - "id": "sa-18.2_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-18(2)[4]" - } - ], - "prose": "inspects organization-defined information systems, system components, or devices to detect tampering, selecting one or more of the following:", - "parts": [ - { - "id": "sa-18.2_obj.4.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-18(2)[4][a]" - } - ], - "prose": "at random;" - }, - { - "id": "sa-18.2_obj.4.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-18(2)[4][b]" - } - ], - "prose": "with the organization-defined frequency; and/or" - }, - { - "id": "sa-18.2_obj.4.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-18(2)[4][c]" - } - ], - "prose": "upon organization-defined indications of need for inspection." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing tamper resistance and detection\n\nrecords of random inspections\n\ninspection reports/results\n\nassessment reports/results\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for the tamper protection program" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for inspecting information systems, system components, or devices to detect tampering\n\nautomated mechanisms supporting and/or implementing tampering detection" - } - ] - } - ] - } - ] - }, - { - "id": "sa-19", - "class": "SP800-53", - "title": "Component Authenticity", - "params": [ - { - "id": "sa-19_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "source of counterfeit component", - " {{ insert: param, sa-19_prm_2 }} ", - " {{ insert: param, sa-19_prm_3 }} " - ] - } - }, - { - "id": "sa-19_prm_2", - "depends-on": "sa-19_prm_1", - "label": "organization-defined external reporting organizations" - }, - { - "id": "sa-19_prm_3", - "depends-on": "sa-19_prm_1", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "SA-19" - }, - { - "name": "sort-id", - "value": "sa-19" - } - ], - "parts": [ - { - "id": "sa-19_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sa-19_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops and implements anti-counterfeit policy and procedures that include the means to detect and prevent counterfeit components from entering the information system; and" - }, - { - "id": "sa-19_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reports counterfeit information system components to {{ insert: param, sa-19_prm_1 }}." - } - ] - }, - { - "id": "sa-19_gdn", - "name": "guidance", - "prose": "Sources of counterfeit components include, for example, manufacturers, developers, vendors, and contractors. Anti-counterfeiting policy and procedures support tamper resistance and provide a level of protection against the introduction of malicious code. External reporting organizations include, for example, US-CERT.", - "links": [ - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#sa-12", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "sa-19_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-19.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-19(a)" - } - ], - "prose": "develops and implements anti-counterfeit policy and procedures that include the means to detect and prevent counterfeit components from entering the information system;" - }, - { - "id": "sa-19.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-19(b)" - } - ], - "parts": [ - { - "id": "sa-19.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-19(b)[1]" - } - ], - "prose": "defines external reporting organizations to whom counterfeit information system components are to be reported;" - }, - { - "id": "sa-19.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-19(b)[2]" - } - ], - "prose": "defines personnel or roles to whom counterfeit information system components are to be reported;" - }, - { - "id": "sa-19.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-19(b)[3]" - } - ], - "prose": "reports counterfeit information system components to one or more of the following:", - "parts": [ - { - "id": "sa-19.b_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-19(b)[3][a]" - } - ], - "prose": "the source of counterfeit component;" - }, - { - "id": "sa-19.b_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-19(b)[3][b]" - } - ], - "prose": "the organization-defined external reporting organizations; and/or" - }, - { - "id": "sa-19.b_obj.3.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-19(b)[3][c]" - } - ], - "prose": "the organization-defined personnel or roles." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nanti-counterfeit policy and procedures\n\nmedia disposal policy\n\nmedia protection policy\n\nincident response policy\n\ntraining materials addressing counterfeit information system components\n\ntraining records on detection and prevention of counterfeit components from entering the information system\n\nreports notifying developers/manufacturers/vendors/ contractors and/or external reporting organizations of counterfeit information system components\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for anti-counterfeit policy, procedures, and reporting" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for anti-counterfeit detection, prevention, and reporting\n\nautomated mechanisms supporting and/or implementing anti-counterfeit detection, prevention, and reporting" - } - ] - } - ], - "controls": [ - { - "id": "sa-19.1", - "class": "SP800-53-enhancement", - "title": "Anti-counterfeit Training", - "params": [ - { - "id": "sa-19.1_prm_1", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "SA-19(1)" - }, - { - "name": "sort-id", - "value": "sa-19.01" - } - ], - "parts": [ - { - "id": "sa-19.1_smt", - "name": "statement", - "prose": "The organization trains {{ insert: param, sa-19.1_prm_1 }} to detect counterfeit information system components (including hardware, software, and firmware)." - }, - { - "id": "sa-19.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-19.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-19(1)[1]" - } - ], - "prose": "defines personnel or roles to be trained to detect counterfeit information system components (including hardware, software, and firmware); and" - }, - { - "id": "sa-19.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-19(1)[2]" - } - ], - "prose": "trains organization-defined personnel or roles to detect counterfeit information system components (including hardware, software, and firmware)." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nanti-counterfeit policy and procedures\n\nmedia disposal policy\n\nmedia protection policy\n\nincident response policy\n\ntraining materials addressing counterfeit information system components\n\ntraining records on detection of counterfeit information system components\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for anti-counterfeit policy, procedures, and training" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for anti-counterfeit training" - } - ] - } - ] - }, - { - "id": "sa-19.2", - "class": "SP800-53-enhancement", - "title": "Configuration Control for Component Service / Repair", - "params": [ - { - "id": "sa-19.2_prm_1", - "label": "organization-defined information system components" - } - ], - "props": [ - { - "name": "label", - "value": "SA-19(2)" - }, - { - "name": "sort-id", - "value": "sa-19.02" - } - ], - "parts": [ - { - "id": "sa-19.2_smt", - "name": "statement", - "prose": "The organization maintains configuration control over {{ insert: param, sa-19.2_prm_1 }} awaiting service/repair and serviced/repaired components awaiting return to service." - }, - { - "id": "sa-19.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-19.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-19(2)[1]" - } - ], - "prose": "defines information system components requiring configuration control to be maintained when awaiting service/repair;" - }, - { - "id": "sa-19.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-19(2)[2]" - } - ], - "prose": "defines information system components requiring configuration control to be maintained when awaiting return to service; and" - }, - { - "id": "sa-19.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-19(2)[3]" - } - ], - "prose": "maintains configuration control over organization-defined information system components awaiting service/repairs and serviced/repaired components awaiting return to service." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nanti-counterfeit policy and procedures\n\nmedia protection policy\n\nconfiguration management plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nconfiguration control records for components awaiting service/repair\n\nconfiguration control records for serviced/repaired components awaiting return to service\n\ninformation system maintenance records\n\ninformation system audit records\n\ninventory management records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for anti-counterfeit policy and procedures\n\norganizational personnel with responsibility for configuration management" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for configuration management\n\nautomated mechanisms supporting and/or implementing configuration management" - } - ] - } - ] - }, - { - "id": "sa-19.3", - "class": "SP800-53-enhancement", - "title": "Component Disposal", - "params": [ - { - "id": "sa-19.3_prm_1", - "label": "organization-defined techniques and methods" - } - ], - "props": [ - { - "name": "label", - "value": "SA-19(3)" - }, - { - "name": "sort-id", - "value": "sa-19.03" - } - ], - "parts": [ - { - "id": "sa-19.3_smt", - "name": "statement", - "prose": "The organization disposes of information system components using {{ insert: param, sa-19.3_prm_1 }}." - }, - { - "id": "sa-19.3_gdn", - "name": "guidance", - "prose": "Proper disposal of information system components helps to prevent such components from entering the gray market." - }, - { - "id": "sa-19.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-19.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-19(3)[1]" - } - ], - "prose": "defines techniques and methods to dispose of information system components; and" - }, - { - "id": "sa-19.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-19(3)[2]" - } - ], - "prose": "disposes of information system components using organization-defined techniques and methods." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nanti-counterfeit policy and procedures\n\nmedia disposal policy\n\nmedia protection policy\n\ndisposal records for information system components\n\ndocumentation of disposal techniques and methods employed for information system components\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for anti-counterfeit policy and procedures\n\norganizational personnel with responsibility for disposal of information system components" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational techniques and methods for information system component disposal\n\nautomated mechanisms supporting and/or implementing system component disposal" - } - ] - } - ] - }, - { - "id": "sa-19.4", - "class": "SP800-53-enhancement", - "title": "Anti-counterfeit Scanning", - "params": [ - { - "id": "sa-19.4_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "SA-19(4)" - }, - { - "name": "sort-id", - "value": "sa-19.04" - } - ], - "parts": [ - { - "id": "sa-19.4_smt", - "name": "statement", - "prose": "The organization scans for counterfeit information system components {{ insert: param, sa-19.4_prm_1 }}." - }, - { - "id": "sa-19.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-19.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-19(4)[1]" - } - ], - "prose": "defines a frequency to scan for counterfeit information system components; and" - }, - { - "id": "sa-19.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-19(4)[2]" - } - ], - "prose": "scans for counterfeit information system components with the organization-defined frequency." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nanti-counterfeit policy and procedures\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nscanning tools and associated documentation\n\nscanning results\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for anti-counterfeit policy and procedures\n\norganizational personnel with responsibility for anti-counterfeit scanning" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for anti-counterfeit scanning\n\nautomated mechanisms supporting and/or implementing anti-counterfeit scanning" - } - ] - } - ] - } - ] - }, - { - "id": "sa-20", - "class": "SP800-53", - "title": "Customized Development of Critical Components", - "params": [ - { - "id": "sa-20_prm_1", - "label": "organization-defined critical information system components" - } - ], - "props": [ - { - "name": "label", - "value": "SA-20" - }, - { - "name": "sort-id", - "value": "sa-20" - } - ], - "parts": [ - { - "id": "sa-20_smt", - "name": "statement", - "prose": "The organization re-implements or custom develops {{ insert: param, sa-20_prm_1 }}." - }, - { - "id": "sa-20_gdn", - "name": "guidance", - "prose": "Organizations determine that certain information system components likely cannot be trusted due to specific threats to and vulnerabilities in those components, and for which there are no viable security controls to adequately mitigate the resulting risk. Re-implementation or custom development of such components helps to satisfy requirements for higher assurance. This is accomplished by initiating changes to system components (including hardware, software, and firmware) such that the standard attacks by adversaries are less likely to succeed. In situations where no alternative sourcing is available and organizations choose not to re-implement or custom develop critical information system components, additional safeguards can be employed (e.g., enhanced auditing, restrictions on source code and system utility access, and protection from deletion of system and application files.", - "links": [ - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-14", - "rel": "related" - } - ] - }, - { - "id": "sa-20_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-20_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-20[1]" - } - ], - "prose": "defines critical information system components to be re-implemented or custom developed; and" - }, - { - "id": "sa-20_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-20[2]" - } - ], - "prose": "re-implements or custom develops organization-defined information system components." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing customized development of critical information system components\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nsystem development life cycle documentation addressing custom development of critical information system components\n\nconfiguration management records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility re-implementation or customized development of critical information system components" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for re-implementing or customized development of critical information system components\n\nautomated mechanisms supporting and/or implementing re-implementation or customized development of critical information system components" - } - ] - } - ] - }, - { - "id": "sa-21", - "class": "SP800-53", - "title": "Developer Screening", - "params": [ - { - "id": "sa-21_prm_1", - "label": "organization-defined information system, system component, or information system service" - }, - { - "id": "sa-21_prm_2", - "label": "organization-defined official government duties" - }, - { - "id": "sa-21_prm_3", - "label": "organization-defined additional personnel screening criteria" - } - ], - "props": [ - { - "name": "label", - "value": "SA-21" - }, - { - "name": "sort-id", - "value": "sa-21" - } - ], - "parts": [ - { - "id": "sa-21_smt", - "name": "statement", - "prose": "The organization requires that the developer of {{ insert: param, sa-21_prm_1 }}:", - "parts": [ - { - "id": "sa-21_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Have appropriate access authorizations as determined by assigned {{ insert: param, sa-21_prm_2 }}; and" - }, - { - "id": "sa-21_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Satisfy {{ insert: param, sa-21_prm_3 }}." - } - ] - }, - { - "id": "sa-21_gdn", - "name": "guidance", - "prose": "Because the information system, system component, or information system service may be employed in critical activities essential to the national and/or economic security interests of the United States, organizations have a strong interest in ensuring that the developer is trustworthy. The degree of trust required of the developer may need to be consistent with that of the individuals accessing the information system/component/service once deployed. Examples of authorization and personnel screening criteria include clearance, satisfactory background checks, citizenship, and nationality. Trustworthiness of developers may also include a review and analysis of company ownership and any relationships the company has with entities potentially affecting the quality/reliability of the systems, components, or services being developed.", - "links": [ - { - "href": "#ps-3", - "rel": "related" - }, - { - "href": "#ps-7", - "rel": "related" - } - ] - }, - { - "id": "sa-21_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-21_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-21[1]" - } - ], - "prose": "defines the information system, system component, or information system service for which the developer is to be screened;" - }, - { - "id": "sa-21_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-21[2]" - } - ], - "prose": "defines official government duties to be used to determine appropriate access authorizations for the developer;" - }, - { - "id": "sa-21_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-21[3]" - } - ], - "prose": "defines additional personnel screening criteria to be satisfied by the developer;" - }, - { - "id": "sa-21_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-21[4]" - } - ], - "parts": [ - { - "id": "sa-21_obj.4.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-21[4][a]" - } - ], - "prose": "requires that the developer of organization-defined information system, system component, or information system service have appropriate access authorizations as determined by assigned organization-defined official government duties; and" - }, - { - "id": "sa-21_obj.4.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-21[4][b]" - } - ], - "prose": "requires that the developer of organization-defined information system, system component, or information system service satisfy organization-defined additional personnel screening criteria." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\npersonnel security policy and procedures\n\nprocedures addressing personnel screening\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of appropriate access authorizations required by developers of the information system\n\npersonnel screening criteria and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for developer screening" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for developer screening\n\nautomated mechanisms supporting developer screening" - } - ] - } - ], - "controls": [ - { - "id": "sa-21.1", - "class": "SP800-53-enhancement", - "title": "Validation of Screening", - "params": [ - { - "id": "sa-21.1_prm_1", - "label": "organization-defined actions" - } - ], - "props": [ - { - "name": "label", - "value": "SA-21(1)" - }, - { - "name": "sort-id", - "value": "sa-21.01" - } - ], - "parts": [ - { - "id": "sa-21.1_smt", - "name": "statement", - "prose": "The organization requires the developer of the information system, system component, or information system service take {{ insert: param, sa-21.1_prm_1 }} to ensure that the required access authorizations and screening criteria are satisfied." - }, - { - "id": "sa-21.1_gdn", - "name": "guidance", - "prose": "Satisfying required access authorizations and personnel screening criteria includes, for example, providing a listing of all the individuals authorized to perform development activities on the selected information system, system component, or information system service so that organizations can validate that the developer has satisfied the necessary authorization and screening requirements." - }, - { - "id": "sa-21.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-21.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-21(1)[1]" - } - ], - "prose": "defines actions to be taken by the developer of the information system, system component, or information system service to ensure that the required access authorizations and screening criteria are satisfied; and" - }, - { - "id": "sa-21.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-21(1)[2]" - } - ], - "prose": "requires the developer of the information system, system component, or information system service take organization-defined actions to ensure that the required access authorizations and screening criteria are satisfied." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\npersonnel security policy and procedures\n\nprocedures addressing personnel screening\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of appropriate access authorizations required by developers of the information system\n\npersonnel screening criteria and associated documentation\n\nlist of actions ensuring required access authorizations and screening criteria are satisfied\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for developer screening\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for developer screening\n\nautomated mechanisms supporting developer screening" - } - ] - } - ] - } - ] - }, - { - "id": "sa-22", - "class": "SP800-53", - "title": "Unsupported System Components", - "props": [ - { - "name": "label", - "value": "SA-22" - }, - { - "name": "sort-id", - "value": "sa-22" - } - ], - "parts": [ - { - "id": "sa-22_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sa-22_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Replaces information system components when support for the components is no longer available from the developer, vendor, or manufacturer; and" - }, - { - "id": "sa-22_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Provides justification and documents approval for the continued use of unsupported system components required to satisfy mission/business needs." - } - ] - }, - { - "id": "sa-22_gdn", - "name": "guidance", - "prose": "Support for information system components includes, for example, software patches, firmware updates, replacement parts, and maintenance contracts. Unsupported components (e.g., when vendors are no longer providing critical software patches), provide a substantial opportunity for adversaries to exploit new weaknesses discovered in the currently installed components. Exceptions to replacing unsupported system components may include, for example, systems that provide critical mission/business capability where newer technologies are not available or where the systems are so isolated that installing replacement components is not an option.", - "links": [ - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - } - ] - }, - { - "id": "sa-22_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-22.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-22(a)" - } - ], - "prose": "replaces information system components when support for the components is no longer available from the developer, vendor, or manufacturer;" - }, - { - "id": "sa-22.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-22(b)" - } - ], - "parts": [ - { - "id": "sa-22.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-22(b)[1]" - } - ], - "prose": "provides justification for the continued use of unsupported system components required to satisfy mission/business needs; and" - }, - { - "id": "sa-22.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-22(b)[2]" - } - ], - "prose": "documents approval for the continued use of unsupported system components required to satisfy mission/business needs." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing replacement or continued use of unsupported information system components\n\ndocumented evidence of replacing unsupported information system components\n\ndocumented approvals (including justification) for continued use of unsupported information system components\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility system development life cycle\n\norganizational personnel responsible for configuration management" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for replacing unsupported system components\n\nautomated mechanisms supporting and/or implementing replacement of unsupported system components" - } - ] - } - ], - "controls": [ - { - "id": "sa-22.1", - "class": "SP800-53-enhancement", - "title": "Alternative Sources for Continued Support", - "params": [ - { - "id": "sa-22.1_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "in-house support", - " {{ insert: param, sa-22.1_prm_2 }} " - ] - } - }, - { - "id": "sa-22.1_prm_2", - "depends-on": "sa-22.1_prm_1", - "label": "organization-defined support from external providers" - } - ], - "props": [ - { - "name": "label", - "value": "SA-22(1)" - }, - { - "name": "sort-id", - "value": "sa-22.01" - } - ], - "parts": [ - { - "id": "sa-22.1_smt", - "name": "statement", - "prose": "The organization provides {{ insert: param, sa-22.1_prm_1 }} for unsupported information system components." - }, - { - "id": "sa-22.1_gdn", - "name": "guidance", - "prose": "This control enhancement addresses the need to provide continued support for selected information system components that are no longer supported by the original developers, vendors, or manufacturers when such components remain essential to mission/business operations. Organizations can establish in-house support, for example, by developing customized patches for critical software components or secure the services of external providers who through contractual relationships, provide ongoing support for the designated unsupported components. Such contractual relationships can include, for example, Open Source Software value-added vendors." - }, - { - "id": "sa-22.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sa-22.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-22(1)[1]" - } - ], - "prose": "defines support from external providers to be provided for unsupported information system components;" - }, - { - "id": "sa-22.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-22(1)[2]" - } - ], - "prose": "provides and/or obtains support for unsupported information system components from one or more of the following:", - "parts": [ - { - "id": "sa-22.1_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-22(1)[2][a]" - } - ], - "prose": "in-house support; and/or" - }, - { - "id": "sa-22.1_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SA-22(1)[2][b]" - } - ], - "prose": "organization-defined support from external providers." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and services acquisition policy\n\nprocedures addressing support for unsupported information system components\n\nsolicitation documentation\n\nacquisition documentation\n\nacquisition contracts\n\nservice-level agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility system development life cycle\n\norganizational personnel or third-party external providers supporting information system components no longer supported by original developers, vendors, or manufacturers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for supporting system components no longer supported by original developers, vendors, or manufacturers\n\nautomated mechanisms providing support for system components no longer supported by original developers, vendors, or manufacturers" - } - ] - } - ] - } - ] - } - ] - }, - { - "id": "sc", - "class": "family", - "title": "System and Communications Protection", - "controls": [ - { - "id": "sc-1", - "class": "SP800-53", - "title": "System and Communications Protection Policy and Procedures", - "params": [ - { - "id": "sc-1_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "sc-1_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "sc-1_prm_3", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "SC-1" - }, - { - "name": "sort-id", - "value": "sc-01" - } - ], - "links": [ - { - "href": "#5c201b63-0768-417b-ac22-3f014e3941b2", - "rel": "reference" - }, - { - "href": "#9cb3d8fe-2127-48ba-821e-cdd2d7aee921", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sc-1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sc-1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops, documents, and disseminates to {{ insert: param, sc-1_prm_1 }}:", - "parts": [ - { - "id": "sc-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "A system and communications protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "sc-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls; and" - } - ] - }, - { - "id": "sc-1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the current:", - "parts": [ - { - "id": "sc-1_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "System and communications protection policy {{ insert: param, sc-1_prm_2 }}; and" - }, - { - "id": "sc-1_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "System and communications protection procedures {{ insert: param, sc-1_prm_3 }}." - } - ] - } - ] - }, - { - "id": "sc-1_gdn", - "name": "guidance", - "prose": "This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the SC family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures.", - "links": [ - { - "href": "#pm-9", - "rel": "related" - } - ] - }, - { - "id": "sc-1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(a)" - } - ], - "parts": [ - { - "id": "sc-1.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(a)(1)" - } - ], - "parts": [ - { - "id": "sc-1.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(a)(1)[1]" - } - ], - "prose": "develops and documents a system and communications protection policy that addresses:", - "parts": [ - { - "id": "sc-1.a.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(a)(1)[1][a]" - } - ], - "prose": "purpose;" - }, - { - "id": "sc-1.a.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(a)(1)[1][b]" - } - ], - "prose": "scope;" - }, - { - "id": "sc-1.a.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(a)(1)[1][c]" - } - ], - "prose": "roles;" - }, - { - "id": "sc-1.a.1_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(a)(1)[1][d]" - } - ], - "prose": "responsibilities;" - }, - { - "id": "sc-1.a.1_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(a)(1)[1][e]" - } - ], - "prose": "management commitment;" - }, - { - "id": "sc-1.a.1_obj.1.f", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(a)(1)[1][f]" - } - ], - "prose": "coordination among organizational entities;" - }, - { - "id": "sc-1.a.1_obj.1.g", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(a)(1)[1][g]" - } - ], - "prose": "compliance;" - } - ] - }, - { - "id": "sc-1.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(a)(1)[2]" - } - ], - "prose": "defines personnel or roles to whom the system and communications protection policy is to be disseminated;" - }, - { - "id": "sc-1.a.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(a)(1)[3]" - } - ], - "prose": "disseminates the system and communications protection policy to organization-defined personnel or roles;" - } - ] - }, - { - "id": "sc-1.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(a)(2)" - } - ], - "parts": [ - { - "id": "sc-1.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(a)(2)[1]" - } - ], - "prose": "develops and documents procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls;" - }, - { - "id": "sc-1.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(a)(2)[2]" - } - ], - "prose": "defines personnel or roles to whom the procedures are to be disseminated;" - }, - { - "id": "sc-1.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(a)(2)[3]" - } - ], - "prose": "disseminates the procedures to organization-defined personnel or roles;" - } - ] - } - ] - }, - { - "id": "sc-1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(b)" - } - ], - "parts": [ - { - "id": "sc-1.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(b)(1)" - } - ], - "parts": [ - { - "id": "sc-1.b.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(b)(1)[1]" - } - ], - "prose": "defines the frequency to review and update the current system and communications protection policy;" - }, - { - "id": "sc-1.b.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(b)(1)[2]" - } - ], - "prose": "reviews and updates the current system and communications protection policy with the organization-defined frequency;" - } - ] - }, - { - "id": "sc-1.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(b)(2)" - } - ], - "parts": [ - { - "id": "sc-1.b.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(b)(2)[1]" - } - ], - "prose": "defines the frequency to review and update the current system and communications protection procedures; and" - }, - { - "id": "sc-1.b.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-1(b)(2)[2]" - } - ], - "prose": "reviews and updates the current system and communications protection procedures with the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy and procedures\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and communications protection responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "sc-2", - "class": "SP800-53", - "title": "Application Partitioning", - "props": [ - { - "name": "label", - "value": "SC-2" - }, - { - "name": "sort-id", - "value": "sc-02" - } - ], - "parts": [ - { - "id": "sc-2_smt", - "name": "statement", - "prose": "The information system separates user functionality (including user interface services) from information system management functionality." - }, - { - "id": "sc-2_gdn", - "name": "guidance", - "prose": "Information system management functionality includes, for example, functions necessary to administer databases, network components, workstations, or servers, and typically requires privileged user access. The separation of user functionality from information system management functionality is either physical or logical. Organizations implement separation of system management-related functionality from user functionality by using different computers, different central processing units, different instances of operating systems, different network addresses, virtualization techniques, or combinations of these or other methods, as appropriate. This type of separation includes, for example, web administrative interfaces that use separate authentication methods for users of any other information system resources. Separation of system and user functionality may include isolating administrative interfaces on different domains and with additional access controls.", - "links": [ - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - } - ] - }, - { - "id": "sc-2_obj", - "name": "objective", - "prose": "Determine if the information system separates user functionality (including user interface services) from information system management functionality." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing application partitioning\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Separation of user functionality from information system management functionality" - } - ] - } - ], - "controls": [ - { - "id": "sc-2.1", - "class": "SP800-53-enhancement", - "title": "Interfaces for Non-privileged Users", - "props": [ - { - "name": "label", - "value": "SC-2(1)" - }, - { - "name": "sort-id", - "value": "sc-02.01" - } - ], - "parts": [ - { - "id": "sc-2.1_smt", - "name": "statement", - "prose": "The information system prevents the presentation of information system management-related functionality at an interface for non-privileged users." - }, - { - "id": "sc-2.1_gdn", - "name": "guidance", - "prose": "This control enhancement ensures that administration options (e.g., administrator privileges) are not available to general users (including prohibiting the use of the grey-out option commonly used to eliminate accessibility to such information). Such restrictions include, for example, not presenting administration options until users establish sessions with administrator privileges.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - } - ] - }, - { - "id": "sc-2.1_obj", - "name": "objective", - "prose": "Determine if the information system prevents the presentation of information system management-related functionality at an interface for non-privileged users." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing application partitioning\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nnon-privileged users of the information system\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Separation of user functionality from information system management functionality" - } - ] - } - ] - } - ] - }, - { - "id": "sc-3", - "class": "SP800-53", - "title": "Security Function Isolation", - "props": [ - { - "name": "label", - "value": "SC-3" - }, - { - "name": "sort-id", - "value": "sc-03" - } - ], - "parts": [ - { - "id": "sc-3_smt", - "name": "statement", - "prose": "The information system isolates security functions from nonsecurity functions." - }, - { - "id": "sc-3_gdn", - "name": "guidance", - "prose": "The information system isolates security functions from nonsecurity functions by means of an isolation boundary (implemented via partitions and domains). Such isolation controls access to and protects the integrity of the hardware, software, and firmware that perform those security functions. Information systems implement code separation (i.e., separation of security functions from nonsecurity functions) in a number of ways, including, for example, through the provision of security kernels via processor rings or processor modes. For non-kernel code, security function isolation is often achieved through file system protections that serve to protect the code on disk, and address space protections that protect executing code. Information systems restrict access to security functions through the use of access control mechanisms and by implementing least privilege capabilities. While the ideal is for all of the code within the security function isolation boundary to only contain security-relevant code, it is sometimes necessary to include nonsecurity functions within the isolation boundary as an exception.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-13", - "rel": "related" - }, - { - "href": "#sc-2", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-39", - "rel": "related" - } - ] - }, - { - "id": "sc-3_obj", - "name": "objective", - "prose": "Determine if the information system isolates security functions from nonsecurity functions." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing security function isolation\n\nlist of security functions to be isolated from nonsecurity functions\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Separation of security functions from nonsecurity functions within the information system" - } - ] - } - ], - "controls": [ - { - "id": "sc-3.1", - "class": "SP800-53-enhancement", - "title": "Hardware Separation", - "props": [ - { - "name": "label", - "value": "SC-3(1)" - }, - { - "name": "sort-id", - "value": "sc-03.01" - } - ], - "parts": [ - { - "id": "sc-3.1_smt", - "name": "statement", - "prose": "The information system utilizes underlying hardware separation mechanisms to implement security function isolation." - }, - { - "id": "sc-3.1_gdn", - "name": "guidance", - "prose": "Underlying hardware separation mechanisms include, for example, hardware ring architectures, commonly implemented within microprocessors, and hardware-enforced address segmentation used to support logically distinct storage objects with separate attributes (i.e., readable, writeable)." - }, - { - "id": "sc-3.1_obj", - "name": "objective", - "prose": "Determine if the information system utilizes underlying hardware separation mechanisms to implement security function isolation." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing security function isolation\n\ninformation system design documentation\n\nhardware separation mechanisms\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Separation of security functions from nonsecurity functions within the information system" - } - ] - } - ] - }, - { - "id": "sc-3.2", - "class": "SP800-53-enhancement", - "title": "Access / Flow Control Functions", - "props": [ - { - "name": "label", - "value": "SC-3(2)" - }, - { - "name": "sort-id", - "value": "sc-03.02" - } - ], - "parts": [ - { - "id": "sc-3.2_smt", - "name": "statement", - "prose": "The information system isolates security functions enforcing access and information flow control from nonsecurity functions and from other security functions." - }, - { - "id": "sc-3.2_gdn", - "name": "guidance", - "prose": "Security function isolation occurs as a result of implementation; the functions can still be scanned and monitored. Security functions that are potentially isolated from access and flow control enforcement functions include, for example, auditing, intrusion detection, and anti-virus functions." - }, - { - "id": "sc-3.2_obj", - "name": "objective", - "prose": "Determine if the information system isolates security functions enforcing:", - "parts": [ - { - "id": "sc-3.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-3(2)[1]" - } - ], - "prose": "access control from nonsecurity functions;" - }, - { - "id": "sc-3.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-3(2)[2]" - } - ], - "prose": "information flow control from nonsecurity functions;" - }, - { - "id": "sc-3.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-3(2)[3]" - } - ], - "prose": "access control from other security functions; and" - }, - { - "id": "sc-3.2_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-3(2)[4]" - } - ], - "prose": "information flow control from other security functions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing security function isolation\n\nlist of critical security functions\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Isolation of security functions enforcing access and information flow control" - } - ] - } - ] - }, - { - "id": "sc-3.3", - "class": "SP800-53-enhancement", - "title": "Minimize Nonsecurity Functionality", - "props": [ - { - "name": "label", - "value": "SC-3(3)" - }, - { - "name": "sort-id", - "value": "sc-03.03" - } - ], - "parts": [ - { - "id": "sc-3.3_smt", - "name": "statement", - "prose": "The organization minimizes the number of nonsecurity functions included within the isolation boundary containing security functions." - }, - { - "id": "sc-3.3_gdn", - "name": "guidance", - "prose": "In those instances where it is not feasible to achieve strict isolation of nonsecurity functions from security functions, it is necessary to take actions to minimize the nonsecurity-relevant functions within the security function boundary. Nonsecurity functions contained within the isolation boundary are considered security-relevant because errors or maliciousness in such software, by virtue of being within the boundary, can impact the security functions of organizational information systems. The design objective is that the specific portions of information systems providing information security are of minimal size/complexity. Minimizing the number of nonsecurity functions in the security-relevant components of information systems allows designers and implementers to focus only on those functions which are necessary to provide the desired security capability (typically access enforcement). By minimizing nonsecurity functions within the isolation boundaries, the amount of code that must be trusted to enforce security policies is reduced, thus contributing to understandability." - }, - { - "id": "sc-3.3_obj", - "name": "objective", - "prose": "Determine if the organization implements an information system isolation boundary to minimize the number of nonsecurity functions included within the boundary containing security functions." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing security function isolation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing an isolation boundary" - } - ] - } - ] - }, - { - "id": "sc-3.4", - "class": "SP800-53-enhancement", - "title": "Module Coupling and Cohesiveness", - "props": [ - { - "name": "label", - "value": "SC-3(4)" - }, - { - "name": "sort-id", - "value": "sc-03.04" - } - ], - "parts": [ - { - "id": "sc-3.4_smt", - "name": "statement", - "prose": "The organization implements security functions as largely independent modules that maximize internal cohesiveness within modules and minimize coupling between modules." - }, - { - "id": "sc-3.4_gdn", - "name": "guidance", - "prose": "The reduction in inter-module interactions helps to constrain security functions and to manage complexity. The concepts of coupling and cohesion are important with respect to modularity in software design. Coupling refers to the dependencies that one module has on other modules. Cohesion refers to the relationship between the different functions within a particular module. Good software engineering practices rely on modular decomposition, layering, and minimization to reduce and manage complexity, thus producing software modules that are highly cohesive and loosely coupled." - }, - { - "id": "sc-3.4_obj", - "name": "objective", - "prose": "Determine if the organization implements security functions as largely independent modules that:", - "parts": [ - { - "id": "sc-3.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-3(4)[1]" - } - ], - "prose": "maximize internal cohesiveness within modules; and" - }, - { - "id": "sc-3.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-3(4)[2]" - } - ], - "prose": "minimize coupling between modules." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing security function isolation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for maximizing internal cohesiveness within modules and minimizing coupling between modules\n\nautomated mechanisms supporting and/or implementing security functions as independent modules" - } - ] - } - ] - }, - { - "id": "sc-3.5", - "class": "SP800-53-enhancement", - "title": "Layered Structures", - "props": [ - { - "name": "label", - "value": "SC-3(5)" - }, - { - "name": "sort-id", - "value": "sc-03.05" - } - ], - "parts": [ - { - "id": "sc-3.5_smt", - "name": "statement", - "prose": "The organization implements security functions as a layered structure minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers." - }, - { - "id": "sc-3.5_gdn", - "name": "guidance", - "prose": "The implementation of layered structures with minimized interactions among security functions and non-looping layers (i.e., lower-layer functions do not depend on higher-layer functions) further enables the isolation of security functions and management of complexity." - }, - { - "id": "sc-3.5_obj", - "name": "objective", - "prose": "Determine if the organization implements security functions as a layered structure:", - "parts": [ - { - "id": "sc-3.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-3(5)[1]" - } - ], - "prose": "minimizing interactions between layers of the design; and" - }, - { - "id": "sc-3.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-3(5)[2]" - } - ], - "prose": "avoiding any dependence by lower layers on the functionality or correctness of higher layers." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing security function isolation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for implementing security functions as a layered structure that minimizes interactions between layers and avoids dependence by lower layers on functionality/correctness of higher layers\n\nautomated mechanisms supporting and/or implementing security functions as a layered structure" - } - ] - } - ] - } - ] - }, - { - "id": "sc-4", - "class": "SP800-53", - "title": "Information in Shared Resources", - "props": [ - { - "name": "label", - "value": "SC-4" - }, - { - "name": "sort-id", - "value": "sc-04" - } - ], - "parts": [ - { - "id": "sc-4_smt", - "name": "statement", - "prose": "The information system prevents unauthorized and unintended information transfer via shared system resources." - }, - { - "id": "sc-4_gdn", - "name": "guidance", - "prose": "This control prevents information, including encrypted representations of information, produced by the actions of prior users/roles (or the actions of processes acting on behalf of prior users/roles) from being available to any current users/roles (or current processes) that obtain access to shared system resources (e.g., registers, main memory, hard disks) after those resources have been released back to information systems. The control of information in shared resources is also commonly referred to as object reuse and residual information protection. This control does not address: (i) information remanence which refers to residual representation of data that has been nominally erased or removed; (ii) covert channels (including storage and/or timing channels) where shared resources are manipulated to violate information flow restrictions; or (iii) components within information systems for which there are only single users/roles.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#mp-6", - "rel": "related" - } - ] - }, - { - "id": "sc-4_obj", - "name": "objective", - "prose": "Determine if the information system prevents unauthorized and unintended information transfer via shared system resources." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing information protection in shared system resources\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms preventing unauthorized and unintended transfer of information via shared system resources" - } - ] - } - ], - "controls": [ - { - "id": "sc-4.1", - "class": "SP800-53-enhancement", - "title": "Security Levels", - "props": [ - { - "name": "label", - "value": "SC-4(1)" - }, - { - "name": "sort-id", - "value": "sc-04.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-4", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sc-4.2", - "class": "SP800-53-enhancement", - "title": "Periods Processing", - "params": [ - { - "id": "sc-4.2_prm_1", - "label": "organization-defined procedures" - } - ], - "props": [ - { - "name": "label", - "value": "SC-4(2)" - }, - { - "name": "sort-id", - "value": "sc-04.02" - } - ], - "parts": [ - { - "id": "sc-4.2_smt", - "name": "statement", - "prose": "The information system prevents unauthorized information transfer via shared resources in accordance with {{ insert: param, sc-4.2_prm_1 }} when system processing explicitly switches between different information classification levels or security categories." - }, - { - "id": "sc-4.2_gdn", - "name": "guidance", - "prose": "This control enhancement applies when there are explicit changes in information processing levels during information system operations, for example, during multilevel processing and periods processing with information at different classification levels or security categories. Organization-defined procedures may include, for example, approved sanitization processes for electronically stored information." - }, - { - "id": "sc-4.2_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-4.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-4(2)[1]" - } - ], - "prose": "the organization defines procedures to be employed to ensure unauthorized information transfer via shared resources is prevented when system processing explicitly switches between different information classification levels or security categories; and" - }, - { - "id": "sc-4.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-4(2)[2]" - } - ], - "prose": "the information system prevents unauthorized information transfer via shared resources in accordance with organization-defined procedures when system processing explicitly switches between different information classification levels or security categories." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing information protection in shared system resources\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms preventing unauthorized transfer of information via shared system resources" - } - ] - } - ] - } - ] - }, - { - "id": "sc-5", - "class": "SP800-53", - "title": "Denial of Service Protection", - "params": [ - { - "id": "sc-5_prm_1", - "label": "organization-defined types of denial of service attacks or references to sources for such information" - }, - { - "id": "sc-5_prm_2", - "label": "organization-defined security safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "SC-5" - }, - { - "name": "sort-id", - "value": "sc-05" - } - ], - "parts": [ - { - "id": "sc-5_smt", - "name": "statement", - "prose": "The information system protects against or limits the effects of the following types of denial of service attacks: {{ insert: param, sc-5_prm_1 }} by employing {{ insert: param, sc-5_prm_2 }}." - }, - { - "id": "sc-5_gdn", - "name": "guidance", - "prose": "A variety of technologies exist to limit, or in some cases, eliminate the effects of denial of service attacks. For example, boundary protection devices can filter certain types of packets to protect information system components on internal organizational networks from being directly affected by denial of service attacks. Employing increased capacity and bandwidth combined with service redundancy may also reduce the susceptibility to denial of service attacks.", - "links": [ - { - "href": "#sc-6", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - } - ] - }, - { - "id": "sc-5_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-5[1]" - } - ], - "prose": "the organization defines types of denial of service attacks or reference to source of such information for the information system to protect against or limit the effects;" - }, - { - "id": "sc-5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-5[2]" - } - ], - "prose": "the organization defines security safeguards to be employed by the information system to protect against or limit the effects of organization-defined types of denial of service attacks; and" - }, - { - "id": "sc-5_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-5[3]" - } - ], - "prose": "the information system protects against or limits the effects of the organization-defined denial or service attacks (or reference to source for such information) by employing organization-defined security safeguards." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing denial of service protection\n\ninformation system design documentation\n\nsecurity plan\n\nlist of denial of services attacks requiring employment of security safeguards to protect against or limit effects of such attacks\n\nlist of security safeguards protecting against or limiting the effects of denial of service attacks\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with incident response responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms protecting against or limiting the effects of denial of service attacks" - } - ] - } - ], - "controls": [ - { - "id": "sc-5.1", - "class": "SP800-53-enhancement", - "title": "Restrict Internal Users", - "params": [ - { - "id": "sc-5.1_prm_1", - "label": "organization-defined denial of service attacks" - } - ], - "props": [ - { - "name": "label", - "value": "SC-5(1)" - }, - { - "name": "sort-id", - "value": "sc-05.01" - } - ], - "parts": [ - { - "id": "sc-5.1_smt", - "name": "statement", - "prose": "The information system restricts the ability of individuals to launch {{ insert: param, sc-5.1_prm_1 }} against other information systems." - }, - { - "id": "sc-5.1_gdn", - "name": "guidance", - "prose": "Restricting the ability of individuals to launch denial of service attacks requires that the mechanisms used for such attacks are unavailable. Individuals of concern can include, for example, hostile insiders or external adversaries that have successfully breached the information system and are using the system as a platform to launch cyber attacks on third parties. Organizations can restrict the ability of individuals to connect and transmit arbitrary information on the transport medium (i.e., network, wireless spectrum). Organizations can also limit the ability of individuals to use excessive information system resources. Protection against individuals having the ability to launch denial of service attacks may be implemented on specific information systems or on boundary devices prohibiting egress to potential target systems." - }, - { - "id": "sc-5.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-5.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-5(1)[1]" - } - ], - "prose": "the organization defines denial of service attacks for which the information system is required to restrict the ability of individuals to launch such attacks against other information systems; and" - }, - { - "id": "sc-5.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-5(1)[2]" - } - ], - "prose": "the information system restricts the ability of individuals to launch organization-defined denial of service attacks against other information systems." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing denial of service protection\n\ninformation system design documentation\n\nsecurity plan\n\nlist of denial of service attacks launched by individuals against information systems\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with incident response responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms restricting the ability to launch denial of service attacks against other information systems" - } - ] - } - ] - }, - { - "id": "sc-5.2", - "class": "SP800-53-enhancement", - "title": "Excess Capacity / Bandwidth / Redundancy", - "props": [ - { - "name": "label", - "value": "SC-5(2)" - }, - { - "name": "sort-id", - "value": "sc-05.02" - } - ], - "parts": [ - { - "id": "sc-5.2_smt", - "name": "statement", - "prose": "The information system manages excess capacity, bandwidth, or other redundancy to limit the effects of information flooding denial of service attacks." - }, - { - "id": "sc-5.2_gdn", - "name": "guidance", - "prose": "Managing excess capacity ensures that sufficient capacity is available to counter flooding attacks. Managing excess capacity may include, for example, establishing selected usage priorities, quotas, or partitioning." - }, - { - "id": "sc-5.2_obj", - "name": "objective", - "prose": "Determine if the information system, to limit the effects of information flooding denial of service attacks, manages:", - "parts": [ - { - "id": "sc-5.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-5(2)[1]" - } - ], - "prose": "excess capacity;" - }, - { - "id": "sc-5.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-5(2)[2]" - } - ], - "prose": "bandwidth; or" - }, - { - "id": "sc-5.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-5(2)[3]" - } - ], - "prose": "other redundancy." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing denial of service protection\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with incident response responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing management of information system bandwidth, capacity, and redundancy to limit the effects of information flooding denial of service attacks" - } - ] - } - ] - }, - { - "id": "sc-5.3", - "class": "SP800-53-enhancement", - "title": "Detection / Monitoring", - "params": [ - { - "id": "sc-5.3_prm_1", - "label": "organization-defined monitoring tools" - }, - { - "id": "sc-5.3_prm_2", - "label": "organization-defined information system resources" - } - ], - "props": [ - { - "name": "label", - "value": "SC-5(3)" - }, - { - "name": "sort-id", - "value": "sc-05.03" - } - ], - "parts": [ - { - "id": "sc-5.3_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sc-5.3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Employs {{ insert: param, sc-5.3_prm_1 }} to detect indicators of denial of service attacks against the information system; and" - }, - { - "id": "sc-5.3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Monitors {{ insert: param, sc-5.3_prm_2 }} to determine if sufficient resources exist to prevent effective denial of service attacks." - } - ] - }, - { - "id": "sc-5.3_gdn", - "name": "guidance", - "prose": "Organizations consider utilization and capacity of information system resources when managing risk from denial of service due to malicious attacks. Denial of service attacks can originate from external or internal sources. Information system resources sensitive to denial of service include, for example, physical disk storage, memory, and CPU cycles. Common safeguards to prevent denial of service attacks related to storage utilization and capacity include, for example, instituting disk quotas, configuring information systems to automatically alert administrators when specific storage capacity thresholds are reached, using file compression technologies to maximize available storage space, and imposing separate partitions for system and user data.", - "links": [ - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "sc-5.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-5.3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-5(3)(a)" - } - ], - "parts": [ - { - "id": "sc-5.3.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-5(3)(a)[1]" - } - ], - "prose": "defines monitoring tools to be employed to detect indicators of denial of service attacks against the information system;" - }, - { - "id": "sc-5.3.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-5(3)(a)[2]" - } - ], - "prose": "employs organization-defined monitoring tools to detect indicators of denial of service attacks against the information system;" - } - ], - "links": [ - { - "href": "#sc-5.3_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "sc-5.3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-5(3)(b)" - } - ], - "parts": [ - { - "id": "sc-5.3.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-5(3)(b)[1]" - } - ], - "prose": "defines information system resources to be monitored to determine if sufficient resources exist to prevent effective denial of service attacks; and" - }, - { - "id": "sc-5.3.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-5(3)(b)[2]" - } - ], - "prose": "monitors organization-defined information system resources to determine if sufficient resources exist to prevent effective denial of service attacks." - } - ], - "links": [ - { - "href": "#sc-5.3_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing denial of service protection\n\ninformation system design documentation\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with detection and monitoring responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms/tools implementing information system monitoring for denial of service attacks" - } - ] - } - ] - } - ] - }, - { - "id": "sc-6", - "class": "SP800-53", - "title": "Resource Availability", - "params": [ - { - "id": "sc-6_prm_1", - "label": "organization-defined resources" - }, - { - "id": "sc-6_prm_2", - "select": { - "how-many": "one-or-more", - "choice": [ - "priority", - "quota", - " {{ insert: param, sc-6_prm_3 }} " - ] - } - }, - { - "id": "sc-6_prm_3", - "depends-on": "sc-6_prm_2", - "label": "organization-defined security safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "SC-6" - }, - { - "name": "sort-id", - "value": "sc-06" - } - ], - "parts": [ - { - "id": "sc-6_smt", - "name": "statement", - "prose": "The information system protects the availability of resources by allocating {{ insert: param, sc-6_prm_1 }} by {{ insert: param, sc-6_prm_2 }}." - }, - { - "id": "sc-6_gdn", - "name": "guidance", - "prose": "Priority protection helps prevent lower-priority processes from delaying or interfering with the information system servicing any higher-priority processes. Quotas prevent users or processes from obtaining more than predetermined amounts of resources. This control does not apply to information system components for which there are only single users/roles." - }, - { - "id": "sc-6_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-6[1]" - } - ], - "prose": "the organization defines resources to be allocated to protect the availability of resources;" - }, - { - "id": "sc-6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-6[2]" - } - ], - "prose": "the organization defines security safeguards to be employed to protect the availability of resources;" - }, - { - "id": "sc-6_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-6[3]" - } - ], - "prose": "the information system protects the availability of resources by allocating organization-defined resources by one or more of the following:", - "parts": [ - { - "id": "sc-6_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-6[3][a]" - } - ], - "prose": "priority;" - }, - { - "id": "sc-6_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-6[3][b]" - } - ], - "prose": "quota; and/or" - }, - { - "id": "sc-6_obj.3.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-6[3][c]" - } - ], - "prose": "organization-defined safeguards." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing prioritization of information system resources\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing resource allocation capability\n\nsafeguards employed to protect availability of resources" - } - ] - } - ] - }, - { - "id": "sc-7", - "class": "SP800-53", - "title": "Boundary Protection", - "params": [ - { - "id": "sc-7_prm_1", - "select": { - "choice": [ - "physically", - "logically" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "SC-7" - }, - { - "name": "sort-id", - "value": "sc-07" - } - ], - "links": [ - { - "href": "#e85cdb3f-7f0a-4083-8639-f13f70d3760b", - "rel": "reference" - }, - { - "href": "#756a8e86-57d5-4701-8382-f7a40439665a", - "rel": "reference" - }, - { - "href": "#99f331f2-a9f0-46c2-9856-a3cbb9b89442", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sc-7_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "sc-7_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Monitors and controls communications at the external boundary of the system and at key internal boundaries within the system;" - }, - { - "id": "sc-7_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Implements subnetworks for publicly accessible system components that are {{ insert: param, sc-7_prm_1 }} separated from internal organizational networks; and" - }, - { - "id": "sc-7_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Connects to external networks or information systems only through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security architecture." - } - ] - }, - { - "id": "sc-7_gdn", - "name": "guidance", - "prose": "Managed interfaces include, for example, gateways, routers, firewalls, guards, network-based malicious code analysis and virtualization systems, or encrypted tunnels implemented within a security architecture (e.g., routers protecting firewalls or application gateways residing on protected subnetworks). Subnetworks that are physically or logically separated from internal networks are referred to as demilitarized zones or DMZs. Restricting or prohibiting interfaces within organizational information systems includes, for example, restricting external web traffic to designated web servers within managed interfaces and prohibiting external traffic that appears to be spoofing internal addresses. Organizations consider the shared nature of commercial telecommunications services in the implementation of security controls associated with the use of such services. Commercial telecommunications services are commonly based on network components and consolidated management systems shared by all attached commercial customers, and may also include third party-provided access lines and other service elements. Such transmission services may represent sources of increased risk despite contract security provisions.", - "links": [ - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ca-3", - "rel": "related" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#cp-8", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#sc-5", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "sc-7_obj", - "name": "objective", - "prose": "Determine if the information system:", - "parts": [ - { - "id": "sc-7.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(a)" - } - ], - "parts": [ - { - "id": "sc-7.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(a)[1]" - } - ], - "prose": "monitors communications at the external boundary of the information system;" - }, - { - "id": "sc-7.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(a)[2]" - } - ], - "prose": "monitors communications at key internal boundaries within the system;" - }, - { - "id": "sc-7.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(a)[3]" - } - ], - "prose": "controls communications at the external boundary of the information system;" - }, - { - "id": "sc-7.a_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(a)[4]" - } - ], - "prose": "controls communications at key internal boundaries within the system;" - } - ] - }, - { - "id": "sc-7.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(b)" - } - ], - "prose": "implements subnetworks for publicly accessible system components that are either:", - "parts": [ - { - "id": "sc-7.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(b)[1]" - } - ], - "prose": "physically separated from internal organizational networks; and/or" - }, - { - "id": "sc-7.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(b)[2]" - } - ], - "prose": "logically separated from internal organizational networks; and" - } - ] - }, - { - "id": "sc-7.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(c)" - } - ], - "prose": "connects to external networks or information systems only through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security architecture." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\nlist of key internal boundaries of the information system\n\ninformation system design documentation\n\nboundary protection hardware and software\n\ninformation system configuration settings and associated documentation\n\nenterprise security architecture documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing boundary protection capability" - } - ] - } - ], - "controls": [ - { - "id": "sc-7.1", - "class": "SP800-53-enhancement", - "title": "Physically Separated Subnetworks", - "props": [ - { - "name": "label", - "value": "SC-7(1)" - }, - { - "name": "sort-id", - "value": "sc-07.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-7", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sc-7.2", - "class": "SP800-53-enhancement", - "title": "Public Access", - "props": [ - { - "name": "label", - "value": "SC-7(2)" - }, - { - "name": "sort-id", - "value": "sc-07.02" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-7", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sc-7.3", - "class": "SP800-53-enhancement", - "title": "Access Points", - "props": [ - { - "name": "label", - "value": "SC-7(3)" - }, - { - "name": "sort-id", - "value": "sc-07.03" - } - ], - "parts": [ - { - "id": "sc-7.3_smt", - "name": "statement", - "prose": "The organization limits the number of external network connections to the information system." - }, - { - "id": "sc-7.3_gdn", - "name": "guidance", - "prose": "Limiting the number of external network connections facilitates more comprehensive monitoring of inbound and outbound communications traffic. The Trusted Internet Connection (TIC) initiative is an example of limiting the number of external network connections." - }, - { - "id": "sc-7.3_obj", - "name": "objective", - "prose": "Determine if the organization limits the number of external network connections to the information system." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\ninformation system design documentation\n\nboundary protection hardware and software\n\ninformation system architecture and configuration documentation\n\ninformation system configuration settings and associated documentation\n\ncommunications and network traffic monitoring logs\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing boundary protection capability\n\nautomated mechanisms limiting the number of external network connections to the information system" - } - ] - } - ] - }, - { - "id": "sc-7.4", - "class": "SP800-53-enhancement", - "title": "External Telecommunications Services", - "params": [ - { - "id": "sc-7.4_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "SC-7(4)" - }, - { - "name": "sort-id", - "value": "sc-07.04" - } - ], - "parts": [ - { - "id": "sc-7.4_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sc-7.4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Implements a managed interface for each external telecommunication service;" - }, - { - "id": "sc-7.4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Establishes a traffic flow policy for each managed interface;" - }, - { - "id": "sc-7.4_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Protects the confidentiality and integrity of the information being transmitted across each interface;" - }, - { - "id": "sc-7.4_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "(d)" - } - ], - "prose": "Documents each exception to the traffic flow policy with a supporting mission/business need and duration of that need; and" - }, - { - "id": "sc-7.4_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "(e)" - } - ], - "prose": "Reviews exceptions to the traffic flow policy {{ insert: param, sc-7.4_prm_1 }} and removes exceptions that are no longer supported by an explicit mission/business need." - } - ] - }, - { - "id": "sc-7.4_gdn", - "name": "guidance", - "links": [ - { - "href": "#sc-8", - "rel": "related" - } - ] - }, - { - "id": "sc-7.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-7.4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(4)(a)" - } - ], - "prose": "implements a managed interface for each external telecommunication service;", - "links": [ - { - "href": "#sc-7.4_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "sc-7.4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(4)(b)" - } - ], - "prose": "establishes a traffic flow policy for each managed interface;", - "links": [ - { - "href": "#sc-7.4_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "sc-7.4.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(4)(c)" - } - ], - "prose": "protects the confidentiality and integrity of the information being transmitted across each interface;", - "links": [ - { - "href": "#sc-7.4_smt.c", - "rel": "corresp" - } - ] - }, - { - "id": "sc-7.4.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(4)(d)" - } - ], - "prose": "documents each exception to the traffic flow policy with:", - "parts": [ - { - "id": "sc-7.4.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(4)(d)[1]" - } - ], - "prose": "a supporting mission/business need;" - }, - { - "id": "sc-7.4.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(4)(d)[2]" - } - ], - "prose": "duration of that need;" - } - ], - "links": [ - { - "href": "#sc-7.4_smt.d", - "rel": "corresp" - } - ] - }, - { - "id": "sc-7.4.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(4)(e)" - } - ], - "parts": [ - { - "id": "sc-7.4.e_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(4)(e)[1]" - } - ], - "prose": "defines a frequency to review exceptions to traffic flow policy;" - }, - { - "id": "sc-7.4.e_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(4)(e)[2]" - } - ], - "prose": "reviews exceptions to the traffic flow policy with the organization-defined frequency; and" - }, - { - "id": "sc-7.4.e_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(4)(e)[3]" - } - ], - "prose": "removes traffic flow policy exceptions that are no longer supported by an explicit mission/business need" - } - ], - "links": [ - { - "href": "#sc-7.4_smt.e", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\ntraffic flow policy\n\ninformation flow control policy\n\nprocedures addressing boundary protection\n\ninformation system security architecture\n\ninformation system design documentation\n\nboundary protection hardware and software\n\ninformation system architecture and configuration documentation\n\ninformation system configuration settings and associated documentation\n\nrecords of traffic flow policy exceptions\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for documenting and reviewing exceptions to the traffic flow policy\n\norganizational processes for removing exceptions to the traffic flow policy\n\nautomated mechanisms implementing boundary protection capability\n\nmanaged interfaces implementing traffic flow policy" - } - ] - } - ] - }, - { - "id": "sc-7.5", - "class": "SP800-53-enhancement", - "title": "Deny by Default / Allow by Exception", - "props": [ - { - "name": "label", - "value": "SC-7(5)" - }, - { - "name": "sort-id", - "value": "sc-07.05" - } - ], - "parts": [ - { - "id": "sc-7.5_smt", - "name": "statement", - "prose": "The information system at managed interfaces denies network communications traffic by default and allows network communications traffic by exception (i.e., deny all, permit by exception)." - }, - { - "id": "sc-7.5_gdn", - "name": "guidance", - "prose": "This control enhancement applies to both inbound and outbound network communications traffic. A deny-all, permit-by-exception network communications traffic policy ensures that only those connections which are essential and approved are allowed." - }, - { - "id": "sc-7.5_obj", - "name": "objective", - "prose": "Determine if the information system, at managed interfaces:", - "parts": [ - { - "id": "sc-7.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(5)[1]" - } - ], - "prose": "denies network traffic by default; and" - }, - { - "id": "sc-7.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(5)[2]" - } - ], - "prose": "allows network traffic by exception." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing traffic management at managed interfaces" - } - ] - } - ] - }, - { - "id": "sc-7.6", - "class": "SP800-53-enhancement", - "title": "Response to Recognized Failures", - "props": [ - { - "name": "label", - "value": "SC-7(6)" - }, - { - "name": "sort-id", - "value": "sc-07.06" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-7.18", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sc-7.7", - "class": "SP800-53-enhancement", - "title": "Prevent Split Tunneling for Remote Devices", - "props": [ - { - "name": "label", - "value": "SC-7(7)" - }, - { - "name": "sort-id", - "value": "sc-07.07" - } - ], - "parts": [ - { - "id": "sc-7.7_smt", - "name": "statement", - "prose": "The information system, in conjunction with a remote device, prevents the device from simultaneously establishing non-remote connections with the system and communicating via some other connection to resources in external networks." - }, - { - "id": "sc-7.7_gdn", - "name": "guidance", - "prose": "This control enhancement is implemented within remote devices (e.g., notebook computers) through configuration settings to disable split tunneling in those devices, and by preventing those configuration settings from being readily configurable by users. This control enhancement is implemented within the information system by the detection of split tunneling (or of configuration settings that allow split tunneling) in the remote device, and by prohibiting the connection if the remote device is using split tunneling. Split tunneling might be desirable by remote users to communicate with local information system resources such as printers/file servers. However, split tunneling would in effect allow unauthorized external connections, making the system more vulnerable to attack and to exfiltration of organizational information. The use of VPNs for remote connections, when adequately provisioned with appropriate security controls, may provide the organization with sufficient assurance that it can effectively treat such connections as non-remote connections from the confidentiality and integrity perspective. VPNs thus provide a means for allowing non-remote communications paths from remote devices. The use of an adequately provisioned VPN does not eliminate the need for preventing split tunneling." - }, - { - "id": "sc-7.7_obj", - "name": "objective", - "prose": "Determine if the information system, in conjunction with a remote device, prevents the device from simultaneously establishing non-remote connections with the system and communicating via some other connection to resources in external networks." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\ninformation system design documentation\n\ninformation system hardware and software\n\ninformation system architecture\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing boundary protection capability\n\nautomated mechanisms supporting/restricting non-remote connections" - } - ] - } - ] - }, - { - "id": "sc-7.8", - "class": "SP800-53-enhancement", - "title": "Route Traffic to Authenticated Proxy Servers", - "params": [ - { - "id": "sc-7.8_prm_1", - "label": "organization-defined internal communications traffic" - }, - { - "id": "sc-7.8_prm_2", - "label": "organization-defined external networks" - } - ], - "props": [ - { - "name": "label", - "value": "SC-7(8)" - }, - { - "name": "sort-id", - "value": "sc-07.08" - } - ], - "parts": [ - { - "id": "sc-7.8_smt", - "name": "statement", - "prose": "The information system routes {{ insert: param, sc-7.8_prm_1 }} to {{ insert: param, sc-7.8_prm_2 }} through authenticated proxy servers at managed interfaces." - }, - { - "id": "sc-7.8_gdn", - "name": "guidance", - "prose": "External networks are networks outside of organizational control. A proxy server is a server (i.e., information system or application) that acts as an intermediary for clients requesting information system resources (e.g., files, connections, web pages, or services) from other organizational servers. Client requests established through an initial connection to the proxy server are evaluated to manage complexity and to provide additional protection by limiting direct connectivity. Web content filtering devices are one of the most common proxy servers providing access to the Internet. Proxy servers support logging individual Transmission Control Protocol (TCP) sessions and blocking specific Uniform Resource Locators (URLs), domain names, and Internet Protocol (IP) addresses. Web proxies can be configured with organization-defined lists of authorized and unauthorized websites.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#au-2", - "rel": "related" - } - ] - }, - { - "id": "sc-7.8_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-7.8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(8)[1]" - } - ], - "prose": "the organization defines internal communications traffic to be routed to external networks;" - }, - { - "id": "sc-7.8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(8)[2]" - } - ], - "prose": "the organization defines external networks to which organization-defined internal communications traffic is to be routed; and" - }, - { - "id": "sc-7.8_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(8)[3]" - } - ], - "prose": "the information system routes organization-defined internal communications traffic to organization-defined external networks through authenticated proxy servers at managed interfaces." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\ninformation system design documentation\n\ninformation system hardware and software\n\ninformation system architecture\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing traffic management through authenticated proxy servers at managed interfaces" - } - ] - } - ] - }, - { - "id": "sc-7.9", - "class": "SP800-53-enhancement", - "title": "Restrict Threatening Outgoing Communications Traffic", - "props": [ - { - "name": "label", - "value": "SC-7(9)" - }, - { - "name": "sort-id", - "value": "sc-07.09" - } - ], - "parts": [ - { - "id": "sc-7.9_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "sc-7.9_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Detects and denies outgoing communications traffic posing a threat to external information systems; and" - }, - { - "id": "sc-7.9_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Audits the identity of internal users associated with denied communications." - } - ] - }, - { - "id": "sc-7.9_gdn", - "name": "guidance", - "prose": "Detecting outgoing communications traffic from internal actions that may pose threats to external information systems is sometimes termed extrusion detection. Extrusion detection at information system boundaries as part of managed interfaces includes the analysis of incoming and outgoing communications traffic searching for indications of internal threats to the security of external systems. Such threats include, for example, traffic indicative of denial of service attacks and traffic containing malicious code.", - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#sc-38", - "rel": "related" - }, - { - "href": "#sc-44", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "sc-7.9_obj", - "name": "objective", - "prose": "Determine if the information system:", - "parts": [ - { - "id": "sc-7.9.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(9)(a)" - } - ], - "parts": [ - { - "id": "sc-7.9.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(9)(a)[1]" - } - ], - "prose": "detects outgoing communications traffic posing a threat to external information systems; and" - }, - { - "id": "sc-7.9.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(9)(a)[2]" - } - ], - "prose": "denies outgoing communications traffic posing a threat to external information systems; and" - } - ], - "links": [ - { - "href": "#sc-7.9_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "sc-7.9.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(9)(b)" - } - ], - "prose": "audits the identity of internal users associated with denied communications.", - "links": [ - { - "href": "#sc-7.9_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\ninformation system design documentation\n\ninformation system hardware and software\n\ninformation system architecture\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing boundary protection capability\n\nautomated mechanisms implementing detection and denial of threatening outgoing communications traffic\n\nautomated mechanisms implementing auditing of outgoing communications traffic" - } - ] - } - ] - }, - { - "id": "sc-7.10", - "class": "SP800-53-enhancement", - "title": "Prevent Unauthorized Exfiltration", - "props": [ - { - "name": "label", - "value": "SC-7(10)" - }, - { - "name": "sort-id", - "value": "sc-07.10" - } - ], - "parts": [ - { - "id": "sc-7.10_smt", - "name": "statement", - "prose": "The organization prevents the unauthorized exfiltration of information across managed interfaces." - }, - { - "id": "sc-7.10_gdn", - "name": "guidance", - "prose": "Safeguards implemented by organizations to prevent unauthorized exfiltration of information from information systems include, for example: (i) strict adherence to protocol formats; (ii) monitoring for beaconing from information systems; (iii) monitoring for steganography; (iv) disconnecting external network interfaces except when explicitly needed; (v) disassembling and reassembling packet headers; and (vi) employing traffic profile analysis to detect deviations from the volume/types of traffic expected within organizations or call backs to command and control centers. Devices enforcing strict adherence to protocol formats include, for example, deep packet inspection firewalls and XML gateways. These devices verify adherence to protocol formats and specification at the application layer and serve to identify vulnerabilities that cannot be detected by devices operating at the network or transport layers. This control enhancement is closely associated with cross-domain solutions and system guards enforcing information flow requirements.", - "links": [ - { - "href": "#si-3", - "rel": "related" - } - ] - }, - { - "id": "sc-7.10_obj", - "name": "objective", - "prose": "Determine if the organization prevents the unauthorized exfiltration of information across managed interfaces." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing boundary protection capability\n\npreventing unauthorized exfiltration of information across managed interfaces" - } - ] - } - ] - }, - { - "id": "sc-7.11", - "class": "SP800-53-enhancement", - "title": "Restrict Incoming Communications Traffic", - "params": [ - { - "id": "sc-7.11_prm_1", - "label": "organization-defined authorized sources" - }, - { - "id": "sc-7.11_prm_2", - "label": "organization-defined authorized destinations" - } - ], - "props": [ - { - "name": "label", - "value": "SC-7(11)" - }, - { - "name": "sort-id", - "value": "sc-07.11" - } - ], - "parts": [ - { - "id": "sc-7.11_smt", - "name": "statement", - "prose": "The information system only allows incoming communications from {{ insert: param, sc-7.11_prm_1 }} to be routed to {{ insert: param, sc-7.11_prm_2 }}." - }, - { - "id": "sc-7.11_gdn", - "name": "guidance", - "prose": "This control enhancement provides determinations that source and destination address pairs represent authorized/allowed communications. Such determinations can be based on several factors including, for example, the presence of source/destination address pairs in lists of authorized/allowed communications, the absence of address pairs in lists of unauthorized/disallowed pairs, or meeting more general rules for authorized/allowed source/destination pairs.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - } - ] - }, - { - "id": "sc-7.11_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-7.11_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(11)[1]" - } - ], - "prose": "the organization defines internal communications traffic to be routed to external networks;" - }, - { - "id": "sc-7.11_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(11)[2]" - } - ], - "prose": "the organization defines authorized destinations only to which that incoming communications from organization-defined authorized sources may be routed; and" - }, - { - "id": "sc-7.11_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(11)[3]" - } - ], - "prose": "the information system only allows incoming communications from organization-defined authorized sources to be routed to organization-defined authorized destinations." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing boundary protection capabilities with respect to source/destination address pairs" - } - ] - } - ] - }, - { - "id": "sc-7.12", - "class": "SP800-53-enhancement", - "title": "Host-based Protection", - "params": [ - { - "id": "sc-7.12_prm_1", - "label": "organization-defined host-based boundary protection mechanisms" - }, - { - "id": "sc-7.12_prm_2", - "label": "organization-defined information system components" - } - ], - "props": [ - { - "name": "label", - "value": "SC-7(12)" - }, - { - "name": "sort-id", - "value": "sc-07.12" - } - ], - "parts": [ - { - "id": "sc-7.12_smt", - "name": "statement", - "prose": "The organization implements {{ insert: param, sc-7.12_prm_1 }} at {{ insert: param, sc-7.12_prm_2 }}." - }, - { - "id": "sc-7.12_gdn", - "name": "guidance", - "prose": "Host-based boundary protection mechanisms include, for example, host-based firewalls. Information system components employing host-based boundary protection mechanisms include, for example, servers, workstations, and mobile devices." - }, - { - "id": "sc-7.12_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-7.12_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(12)[1]" - } - ], - "prose": "defines host-based boundary protection mechanisms;" - }, - { - "id": "sc-7.12_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(12)[2]" - } - ], - "prose": "defines information system components where organization-defined host-based boundary protection mechanisms are to be implemented; and" - }, - { - "id": "sc-7.12_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(12)[3]" - } - ], - "prose": "implements organization-defined host-based boundary protection mechanisms at organization-defined information system components." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\ninformation system design documentation\n\nboundary protection hardware and software\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with boundary protection responsibilities\n\ninformation system users" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing host-based boundary protection capabilities" - } - ] - } - ] - }, - { - "id": "sc-7.13", - "class": "SP800-53-enhancement", - "title": "Isolation of Security Tools / Mechanisms / Support Components", - "params": [ - { - "id": "sc-7.13_prm_1", - "label": "organization-defined information security tools, mechanisms, and support components" - } - ], - "props": [ - { - "name": "label", - "value": "SC-7(13)" - }, - { - "name": "sort-id", - "value": "sc-07.13" - } - ], - "parts": [ - { - "id": "sc-7.13_smt", - "name": "statement", - "prose": "The organization isolates {{ insert: param, sc-7.13_prm_1 }} from other internal information system components by implementing physically separate subnetworks with managed interfaces to other components of the system." - }, - { - "id": "sc-7.13_gdn", - "name": "guidance", - "prose": "Physically separate subnetworks with managed interfaces are useful, for example, in isolating computer network defenses from critical operational processing networks to prevent adversaries from discovering the analysis and forensics techniques of organizations.", - "links": [ - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sc-2", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - } - ] - }, - { - "id": "sc-7.13_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-7.13_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(13)[1]" - } - ], - "prose": "defines information security tools, mechanisms, and support components to be isolated from other internal information system components; and" - }, - { - "id": "sc-7.13_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(13)[2]" - } - ], - "prose": "isolates organization-defined information security tools, mechanisms, and support components from other internal information system components by implementing physically separate subnetworks with managed interfaces to other components of the system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\ninformation system design documentation\n\ninformation system hardware and software\n\ninformation system architecture\n\ninformation system configuration settings and associated documentation\n\nlist of security tools and support components to be isolated from other internal information system components\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing isolation of information security tools, mechanisms, and support components" - } - ] - } - ] - }, - { - "id": "sc-7.14", - "class": "SP800-53-enhancement", - "title": "Protects Against Unauthorized Physical Connections", - "params": [ - { - "id": "sc-7.14_prm_1", - "label": "organization-defined managed interfaces" - } - ], - "props": [ - { - "name": "label", - "value": "SC-7(14)" - }, - { - "name": "sort-id", - "value": "sc-07.14" - } - ], - "parts": [ - { - "id": "sc-7.14_smt", - "name": "statement", - "prose": "The organization protects against unauthorized physical connections at {{ insert: param, sc-7.14_prm_1 }}." - }, - { - "id": "sc-7.14_gdn", - "name": "guidance", - "prose": "Information systems operating at different security categories or classification levels may share common physical and environmental controls, since the systems may share space within organizational facilities. In practice, it is possible that these separate information systems may share common equipment rooms, wiring closets, and cable distribution paths. Protection against unauthorized physical connections can be achieved, for example, by employing clearly identified and physically separated cable trays, connection frames, and patch panels for each side of managed interfaces with physical access controls enforcing limited authorized access to these items.", - "links": [ - { - "href": "#pe-4", - "rel": "related" - }, - { - "href": "#pe-19", - "rel": "related" - } - ] - }, - { - "id": "sc-7.14_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-7.14_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(14)[1]" - } - ], - "prose": "defines managed interfaces to be protected against unauthorized physical connections; and" - }, - { - "id": "sc-7.14_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(14)[2]" - } - ], - "prose": "protects against unauthorized physical connections at organization-defined managed interfaces." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\ninformation system design documentation\n\ninformation system hardware and software\n\ninformation system architecture\n\ninformation system configuration settings and associated documentation\n\nfacility communications and wiring diagram\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing protection against unauthorized physical connections" - } - ] - } - ] - }, - { - "id": "sc-7.15", - "class": "SP800-53-enhancement", - "title": "Route Privileged Network Accesses", - "props": [ - { - "name": "label", - "value": "SC-7(15)" - }, - { - "name": "sort-id", - "value": "sc-07.15" - } - ], - "parts": [ - { - "id": "sc-7.15_smt", - "name": "statement", - "prose": "The information system routes all networked, privileged accesses through a dedicated, managed interface for purposes of access control and auditing." - }, - { - "id": "sc-7.15_gdn", - "name": "guidance", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "sc-7.15_obj", - "name": "objective", - "prose": "Determine if the information system routes all networked, privileged accesses through a dedicated, managed interface for the purposes of:", - "parts": [ - { - "id": "sc-7.15_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(15)[1]" - } - ], - "prose": "access control; and" - }, - { - "id": "sc-7.15_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(15)[2]" - } - ], - "prose": "auditing." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\ninformation system design documentation\n\ninformation system hardware and software\n\ninformation system architecture\n\ninformation system configuration settings and associated documentation\n\naudit logs\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing the routing of networked, privileged access through dedicated managed interfaces" - } - ] - } - ] - }, - { - "id": "sc-7.16", - "class": "SP800-53-enhancement", - "title": "Prevent Discovery of Components / Devices", - "props": [ - { - "name": "label", - "value": "SC-7(16)" - }, - { - "name": "sort-id", - "value": "sc-07.16" - } - ], - "parts": [ - { - "id": "sc-7.16_smt", - "name": "statement", - "prose": "The information system prevents discovery of specific system components composing a managed interface." - }, - { - "id": "sc-7.16_gdn", - "name": "guidance", - "prose": "This control enhancement protects network addresses of information system components that are part of managed interfaces from discovery through common tools and techniques used to identify devices on networks. Network addresses are not available for discovery (e.g., network address not published or entered in domain name systems), requiring prior knowledge for access. Another obfuscation technique is to periodically change network addresses." - }, - { - "id": "sc-7.16_obj", - "name": "objective", - "prose": "Determine if the information system prevents discovery of specific system components composing a managed interface." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\ninformation system design documentation\n\ninformation system hardware and software\n\ninformation system architecture\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing the prevention of discovery of system components at managed interfaces" - } - ] - } - ] - }, - { - "id": "sc-7.17", - "class": "SP800-53-enhancement", - "title": "Automated Enforcement of Protocol Formats", - "props": [ - { - "name": "label", - "value": "SC-7(17)" - }, - { - "name": "sort-id", - "value": "sc-07.17" - } - ], - "parts": [ - { - "id": "sc-7.17_smt", - "name": "statement", - "prose": "The information system enforces adherence to protocol formats." - }, - { - "id": "sc-7.17_gdn", - "name": "guidance", - "prose": "Information system components that enforce protocol formats include, for example, deep packet inspection firewalls and XML gateways. Such system components verify adherence to protocol formats/specifications (e.g., IEEE) at the application layer and identify significant vulnerabilities that cannot be detected by devices operating at the network or transport layers.", - "links": [ - { - "href": "#sc-4", - "rel": "related" - } - ] - }, - { - "id": "sc-7.17_obj", - "name": "objective", - "prose": "Determine if the information system enforces adherence to protocol formats." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\ninformation system design documentation\n\ninformation system architecture\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing enforcement of adherence to protocol formats" - } - ] - } - ] - }, - { - "id": "sc-7.18", - "class": "SP800-53-enhancement", - "title": "Fail Secure", - "props": [ - { - "name": "label", - "value": "SC-7(18)" - }, - { - "name": "sort-id", - "value": "sc-07.18" - } - ], - "parts": [ - { - "id": "sc-7.18_smt", - "name": "statement", - "prose": "The information system fails securely in the event of an operational failure of a boundary protection device." - }, - { - "id": "sc-7.18_gdn", - "name": "guidance", - "prose": "Fail secure is a condition achieved by employing information system mechanisms to ensure that in the event of operational failures of boundary protection devices at managed interfaces (e.g., routers, firewalls, guards, and application gateways residing on protected subnetworks commonly referred to as demilitarized zones), information systems do not enter into unsecure states where intended security properties no longer hold. Failures of boundary protection devices cannot lead to, or cause information external to the devices to enter the devices, nor can failures permit unauthorized information releases.", - "links": [ - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#sc-24", - "rel": "related" - } - ] - }, - { - "id": "sc-7.18_obj", - "name": "objective", - "prose": "Determine if the information system fails securely in the event of an operational failure of a boundary protection device." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\ninformation system design documentation\n\ninformation system architecture\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing secure failure" - } - ] - } - ] - }, - { - "id": "sc-7.19", - "class": "SP800-53-enhancement", - "title": "Blocks Communication from Non-organizationally Configured Hosts", - "params": [ - { - "id": "sc-7.19_prm_1", - "label": "organization-defined communication clients" - } - ], - "props": [ - { - "name": "label", - "value": "SC-7(19)" - }, - { - "name": "sort-id", - "value": "sc-07.19" - } - ], - "parts": [ - { - "id": "sc-7.19_smt", - "name": "statement", - "prose": "The information system blocks both inbound and outbound communications traffic between {{ insert: param, sc-7.19_prm_1 }} that are independently configured by end users and external service providers." - }, - { - "id": "sc-7.19_gdn", - "name": "guidance", - "prose": "Communication clients independently configured by end users and external service providers include, for example, instant messaging clients. Traffic blocking does not apply to communication clients that are configured by organizations to perform authorized functions." - }, - { - "id": "sc-7.19_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-7.19_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(19)[1]" - } - ], - "prose": "defines communication clients that are independently configured by end users and external service providers; and" - }, - { - "id": "sc-7.19_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(19)[2]" - } - ], - "prose": "blocks, between organization-defined communication clients that are independently configured by end users and external service providers,:", - "parts": [ - { - "id": "sc-7.19_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(19)[2][a]" - } - ], - "prose": "inbound communications traffic; and" - }, - { - "id": "sc-7.19_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(19)[2][b]" - } - ], - "prose": "outbound communications traffic." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\ninformation system design documentation\n\ninformation system hardware and software\n\ninformation system architecture\n\ninformation system configuration settings and associated documentation\n\nlist of communication clients independently configured by end users and external service providers\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing the blocking of inbound and outbound communications traffic between communication clients independently configured by end users and external service providers" - } - ] - } - ] - }, - { - "id": "sc-7.20", - "class": "SP800-53-enhancement", - "title": "Dynamic Isolation / Segregation", - "params": [ - { - "id": "sc-7.20_prm_1", - "label": "organization-defined information system components" - } - ], - "props": [ - { - "name": "label", - "value": "SC-7(20)" - }, - { - "name": "sort-id", - "value": "sc-07.20" - } - ], - "parts": [ - { - "id": "sc-7.20_smt", - "name": "statement", - "prose": "The information system provides the capability to dynamically isolate/segregate {{ insert: param, sc-7.20_prm_1 }} from other components of the system." - }, - { - "id": "sc-7.20_gdn", - "name": "guidance", - "prose": "The capability to dynamically isolate or segregate certain internal components of organizational information systems is useful when it is necessary to partition or separate certain components of dubious origin from those components possessing greater trustworthiness. Component isolation reduces the attack surface of organizational information systems. Isolation of selected information system components is also a means of limiting the damage from successful cyber attacks when those attacks occur." - }, - { - "id": "sc-7.20_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-7.20_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(20)[1]" - } - ], - "prose": "the organization defines information system components to be dynamically isolated/segregated from other components of the system; and" - }, - { - "id": "sc-7.20_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(20)[2]" - } - ], - "prose": "the information system provides the capability to dynamically isolate/segregate organization-defined information system components from other components of the system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\ninformation system design documentation\n\ninformation system hardware and software\n\ninformation system architecture\n\ninformation system configuration settings and associated documentation\n\nlist of information system components to be dynamically isolated/segregated from other components of the system\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing the capability to dynamically isolate/segregate information system components" - } - ] - } - ] - }, - { - "id": "sc-7.21", - "class": "SP800-53-enhancement", - "title": "Isolation of Information System Components", - "params": [ - { - "id": "sc-7.21_prm_1", - "label": "organization-defined information system components" - }, - { - "id": "sc-7.21_prm_2", - "label": "organization-defined missions and/or business functions" - } - ], - "props": [ - { - "name": "label", - "value": "SC-7(21)" - }, - { - "name": "sort-id", - "value": "sc-07.21" - } - ], - "parts": [ - { - "id": "sc-7.21_smt", - "name": "statement", - "prose": "The organization employs boundary protection mechanisms to separate {{ insert: param, sc-7.21_prm_1 }} supporting {{ insert: param, sc-7.21_prm_2 }}." - }, - { - "id": "sc-7.21_gdn", - "name": "guidance", - "prose": "Organizations can isolate information system components performing different missions and/or business functions. Such isolation limits unauthorized information flows among system components and also provides the opportunity to deploy greater levels of protection for selected components. Separating system components with boundary protection mechanisms provides the capability for increased protection of individual components and to more effectively control information flows between those components. This type of enhanced protection limits the potential harm from cyber attacks and errors. The degree of separation provided varies depending upon the mechanisms chosen. Boundary protection mechanisms include, for example, routers, gateways, and firewalls separating system components into physically separate networks or subnetworks, cross-domain devices separating subnetworks, virtualization techniques, and encrypting information flows among system components using distinct encryption keys.", - "links": [ - { - "href": "#ca-9", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - } - ] - }, - { - "id": "sc-7.21_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-7.21_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(21)[1]" - } - ], - "prose": "defines information system components to be separated by boundary protection mechanisms;" - }, - { - "id": "sc-7.21_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(21)[2]" - } - ], - "prose": "defines missions and/or business functions to be supported by organization-defined information system components separated by boundary protection mechanisms; and" - }, - { - "id": "sc-7.21_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-7(21)[3]" - } - ], - "prose": "employs boundary protection mechanisms to separate organization-defined information system components supporting organization-defined missions and/or business functions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\ninformation system design documentation\n\ninformation system hardware and software\n\nenterprise architecture documentation\n\ninformation system architecture\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing the capability to separate information system components supporting organizational missions and/or business functions" - } - ] - } - ] - }, - { - "id": "sc-7.22", - "class": "SP800-53-enhancement", - "title": "Separate Subnets for Connecting to Different Security Domains", - "props": [ - { - "name": "label", - "value": "SC-7(22)" - }, - { - "name": "sort-id", - "value": "sc-07.22" - } - ], - "parts": [ - { - "id": "sc-7.22_smt", - "name": "statement", - "prose": "The information system implements separate network addresses (i.e., different subnets) to connect to systems in different security domains." - }, - { - "id": "sc-7.22_gdn", - "name": "guidance", - "prose": "Decomposition of information systems into subnets helps to provide the appropriate level of protection for network connections to different security domains containing information with different security categories or classification levels." - }, - { - "id": "sc-7.22_obj", - "name": "objective", - "prose": "Determine if the information system implements separate network addresses (i.e., different subnets) to connect to systems in different security domains." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\ninformation system design documentation\n\ninformation system hardware and software\n\ninformation system architecture\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing separate network addresses/different subnets" - } - ] - } - ] - }, - { - "id": "sc-7.23", - "class": "SP800-53-enhancement", - "title": "Disable Sender Feedback On Protocol Validation Failure", - "props": [ - { - "name": "label", - "value": "SC-7(23)" - }, - { - "name": "sort-id", - "value": "sc-07.23" - } - ], - "parts": [ - { - "id": "sc-7.23_smt", - "name": "statement", - "prose": "The information system disables feedback to senders on protocol format validation failure." - }, - { - "id": "sc-7.23_gdn", - "name": "guidance", - "prose": "Disabling feedback to senders when there is a failure in protocol validation format prevents adversaries from obtaining information which would otherwise be unavailable." - }, - { - "id": "sc-7.23_obj", - "name": "objective", - "prose": "Determine if the information system disables feedback to senders on protocol format validation failure." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\ninformation system design documentation\n\ninformation system hardware and software\n\ninformation system architecture\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing the disabling of feedback to senders on protocol format validation failure" - } - ] - } - ] - } - ] - }, - { - "id": "sc-8", - "class": "SP800-53", - "title": "Transmission Confidentiality and Integrity", - "params": [ - { - "id": "sc-8_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "confidentiality", - "integrity" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "SC-8" - }, - { - "name": "sort-id", - "value": "sc-08" - } - ], - "links": [ - { - "href": "#d715b234-9b5b-4e07-b1ed-99836727664d", - "rel": "reference" - }, - { - "href": "#f2dbd4ec-c413-4714-b85b-6b7184d1c195", - "rel": "reference" - }, - { - "href": "#90c5bc98-f9c4-44c9-98b7-787422f0999c", - "rel": "reference" - }, - { - "href": "#99f331f2-a9f0-46c2-9856-a3cbb9b89442", - "rel": "reference" - }, - { - "href": "#6af1e841-672c-46c4-b121-96f603d04be3", - "rel": "reference" - }, - { - "href": "#349fe082-502d-464a-aa0c-1443c6a5cf40", - "rel": "reference" - }, - { - "href": "#a4aa9645-9a8a-4b51-90a9-e223250f9a75", - "rel": "reference" - }, - { - "href": "#06dff0ea-3848-4945-8d91-e955ee69f05d", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sc-8_smt", - "name": "statement", - "prose": "The information system protects the {{ insert: param, sc-8_prm_1 }} of transmitted information." - }, - { - "id": "sc-8_gdn", - "name": "guidance", - "prose": "This control applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. Protecting the confidentiality and/or integrity of organizational information can be accomplished by physical means (e.g., by employing protected distribution systems) or by logical means (e.g., employing encryption techniques). Organizations relying on commercial providers offering transmission services as commodity services rather than as fully dedicated services (i.e., services which can be highly specialized to individual customer needs), may find it difficult to obtain the necessary assurances regarding the implementation of needed security controls for transmission confidentiality/integrity. In such situations, organizations determine what types of confidentiality/integrity services are available in standard, commercial telecommunication service packages. If it is infeasible or impractical to obtain the necessary security controls and assurances of control effectiveness through appropriate contracting vehicles, organizations implement appropriate compensating security controls or explicitly accept the additional risk.", - "links": [ - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#pe-4", - "rel": "related" - } - ] - }, - { - "id": "sc-8_obj", - "name": "objective", - "prose": "Determine if the information system protects one or more of the following:", - "parts": [ - { - "id": "sc-8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-8[1]" - } - ], - "prose": "confidentiality of transmitted information; and/or" - }, - { - "id": "sc-8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-8[2]" - } - ], - "prose": "integrity of transmitted information." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing transmission confidentiality and integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing transmission confidentiality and/or integrity" - } - ] - } - ], - "controls": [ - { - "id": "sc-8.1", - "class": "SP800-53-enhancement", - "title": "Cryptographic or Alternate Physical Protection", - "params": [ - { - "id": "sc-8.1_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "prevent unauthorized disclosure of information", - "detect changes to information" - ] - } - }, - { - "id": "sc-8.1_prm_2", - "label": "organization-defined alternative physical safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "SC-8(1)" - }, - { - "name": "sort-id", - "value": "sc-08.01" - } - ], - "parts": [ - { - "id": "sc-8.1_smt", - "name": "statement", - "prose": "The information system implements cryptographic mechanisms to {{ insert: param, sc-8.1_prm_1 }} during transmission unless otherwise protected by {{ insert: param, sc-8.1_prm_2 }}." - }, - { - "id": "sc-8.1_gdn", - "name": "guidance", - "prose": "Encrypting information for transmission protects information from unauthorized disclosure and modification. Cryptographic mechanisms implemented to protect information integrity include, for example, cryptographic hash functions which have common application in digital signatures, checksums, and message authentication codes. Alternative physical security safeguards include, for example, protected distribution systems.", - "links": [ - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "sc-8.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-8.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-8(1)[1]" - } - ], - "prose": "the organization defines physical safeguards to be implemented to protect information during transmission when cryptographic mechanisms are not implemented; and" - }, - { - "id": "sc-8.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-8(1)[2]" - } - ], - "prose": "the information system implements cryptographic mechanisms to do one or more of the following during transmission unless otherwise protected by organization-defined alternative physical safeguards:", - "parts": [ - { - "id": "sc-8.1_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-8(1)[2][a]" - } - ], - "prose": "prevent unauthorized disclosure of information; and/or" - }, - { - "id": "sc-8.1_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-8(1)[2][b]" - } - ], - "prose": "detect changes to information." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing transmission confidentiality and integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Cryptographic mechanisms supporting and/or implementing transmission confidentiality and/or integrity\n\nautomated mechanisms supporting and/or implementing alternative physical safeguards\n\norganizational processes for defining and implementing alternative physical safeguards" - } - ] - } - ] - }, - { - "id": "sc-8.2", - "class": "SP800-53-enhancement", - "title": "Pre / Post Transmission Handling", - "params": [ - { - "id": "sc-8.2_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "confidentiality", - "integrity" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "SC-8(2)" - }, - { - "name": "sort-id", - "value": "sc-08.02" - } - ], - "parts": [ - { - "id": "sc-8.2_smt", - "name": "statement", - "prose": "The information system maintains the {{ insert: param, sc-8.2_prm_1 }} of information during preparation for transmission and during reception." - }, - { - "id": "sc-8.2_gdn", - "name": "guidance", - "prose": "Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission or during reception including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information.", - "links": [ - { - "href": "#au-10", - "rel": "related" - } - ] - }, - { - "id": "sc-8.2_obj", - "name": "objective", - "prose": "Determine if the information system maintains one or more of the following:", - "parts": [ - { - "id": "sc-8.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-8(2)[1]" - } - ], - "prose": "confidentiality of information during preparation for transmission;" - }, - { - "id": "sc-8.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-8(2)[2]" - } - ], - "prose": "confidentiality of information during reception; and/or" - }, - { - "id": "sc-8.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-8(2)[3]" - } - ], - "prose": "integrity of information during preparation for transmission;" - }, - { - "id": "sc-8.2_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-8(2)[4]" - } - ], - "prose": "integrity of information during reception." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing transmission confidentiality and integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing transmission confidentiality and/or integrity" - } - ] - } - ] - }, - { - "id": "sc-8.3", - "class": "SP800-53-enhancement", - "title": "Cryptographic Protection for Message Externals", - "params": [ - { - "id": "sc-8.3_prm_1", - "label": "organization-defined alternative physical safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "SC-8(3)" - }, - { - "name": "sort-id", - "value": "sc-08.03" - } - ], - "parts": [ - { - "id": "sc-8.3_smt", - "name": "statement", - "prose": "The information system implements cryptographic mechanisms to protect message externals unless otherwise protected by {{ insert: param, sc-8.3_prm_1 }}." - }, - { - "id": "sc-8.3_gdn", - "name": "guidance", - "prose": "This control enhancement addresses protection against unauthorized disclosure of information. Message externals include, for example, message headers/routing information. This control enhancement prevents the exploitation of message externals and applies to both internal and external networks or links that may be visible to individuals who are not authorized users. Header/routing information is sometimes transmitted unencrypted because the information is not properly identified by organizations as having significant value or because encrypting the information can result in lower network performance and/or higher costs. Alternative physical safeguards include, for example, protected distribution systems.", - "links": [ - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "sc-8.3_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-8.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-8(3)[1]" - } - ], - "prose": "the organization defines alternative physical safeguards to be implemented to protect message externals; and" - }, - { - "id": "sc-8.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-8(3)[2]" - } - ], - "prose": "the information system implements cryptographic mechanisms to protect message externals unless otherwise protected by organization-defined alternative physical safeguards." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing transmission confidentiality and integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Cryptographic mechanisms supporting and/or implementing transmission confidentiality and/or integrity for message externals\n\nautomated mechanisms supporting and/or implementing alternative physical safeguards\n\norganizational processes for defining and implementing alternative physical safeguards" - } - ] - } - ] - }, - { - "id": "sc-8.4", - "class": "SP800-53-enhancement", - "title": "Conceal / Randomize Communications", - "params": [ - { - "id": "sc-8.4_prm_1", - "label": "organization-defined alternative physical safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "SC-8(4)" - }, - { - "name": "sort-id", - "value": "sc-08.04" - } - ], - "parts": [ - { - "id": "sc-8.4_smt", - "name": "statement", - "prose": "The information system implements cryptographic mechanisms to conceal or randomize communication patterns unless otherwise protected by {{ insert: param, sc-8.4_prm_1 }}." - }, - { - "id": "sc-8.4_gdn", - "name": "guidance", - "prose": "This control enhancement addresses protection against unauthorized disclosure of information. Communication patterns include, for example, frequency, periods, amount, and predictability. Changes to communications patterns can reveal information having intelligence value especially when combined with other available information related to missions/business functions supported by organizational information systems. This control enhancement prevents the derivation of intelligence based on communications patterns and applies to both internal and external networks or links that may be visible to individuals who are not authorized users. Encrypting the links and transmitting in continuous, fixed/random patterns prevents the derivation of intelligence from the system communications patterns. Alternative physical safeguards include, for example, protected distribution systems.", - "links": [ - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "sc-8.4_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-8.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-8(4)[1]" - } - ], - "prose": "the organization defines alternative physical safeguards to be implemented to protect against unauthorized disclosure of communication patterns;" - }, - { - "id": "sc-8.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-8(4)[2]" - } - ], - "prose": "the information system, unless otherwise protected by organization-defined alternative physical safeguards, implements cryptographic mechanisms to:", - "parts": [ - { - "id": "sc-8.4_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-8(4)[2][a]" - } - ], - "prose": "conceal communication patterns; or" - }, - { - "id": "sc-8.4_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-8(4)[2][b]" - } - ], - "prose": "randomize communication patterns." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing transmission confidentiality and integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Cryptographic mechanisms supporting and/or implementing concealment or randomization of communications patterns\n\nautomated mechanisms supporting and/or implementing alternative physical safeguards\n\norganizational processes for defining and implementing alternative physical safeguards" - } - ] - } - ] - } - ] - }, - { - "id": "sc-9", - "class": "SP800-53", - "title": "Transmission Confidentiality", - "props": [ - { - "name": "label", - "value": "SC-9" - }, - { - "name": "sort-id", - "value": "sc-09" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-8", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sc-10", - "class": "SP800-53", - "title": "Network Disconnect", - "params": [ - { - "id": "sc-10_prm_1", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "SC-10" - }, - { - "name": "sort-id", - "value": "sc-10" - } - ], - "parts": [ - { - "id": "sc-10_smt", - "name": "statement", - "prose": "The information system terminates the network connection associated with a communications session at the end of the session or after {{ insert: param, sc-10_prm_1 }} of inactivity." - }, - { - "id": "sc-10_gdn", - "name": "guidance", - "prose": "This control applies to both internal and external networks. Terminating network connections associated with communications sessions include, for example, de-allocating associated TCP/IP address/port pairs at the operating system level, or de-allocating networking assignments at the application level if multiple application sessions are using a single, operating system-level network connection. Time periods of inactivity may be established by organizations and include, for example, time periods by type of network access or for specific network accesses." - }, - { - "id": "sc-10_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-10_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-10[1]" - } - ], - "prose": "the organization defines a time period of inactivity after which the information system terminates a network connection associated with a communications session; and" - }, - { - "id": "sc-10_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-10[2]" - } - ], - "prose": "the information system terminates the network connection associated with a communication session at the end of the session or after the organization-defined time period of inactivity." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing network disconnect\n\ninformation system design documentation\n\nsecurity plan\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing network disconnect capability" - } - ] - } - ] - }, - { - "id": "sc-11", - "class": "SP800-53", - "title": "Trusted Path", - "params": [ - { - "id": "sc-11_prm_1", - "label": "organization-defined security functions to include at a minimum, information system authentication and re-authentication" - } - ], - "props": [ - { - "name": "label", - "value": "SC-11" - }, - { - "name": "sort-id", - "value": "sc-11" - } - ], - "parts": [ - { - "id": "sc-11_smt", - "name": "statement", - "prose": "The information system establishes a trusted communications path between the user and the following security functions of the system: {{ insert: param, sc-11_prm_1 }}." - }, - { - "id": "sc-11_gdn", - "name": "guidance", - "prose": "Trusted paths are mechanisms by which users (through input devices) can communicate directly with security functions of information systems with the requisite assurance to support information security policies. The mechanisms can be activated only by users or the security functions of organizational information systems. User responses via trusted paths are protected from modifications by or disclosure to untrusted applications. Organizations employ trusted paths for high-assurance connections between security functions of information systems and users (e.g., during system logons). Enforcement of trusted communications paths is typically provided via an implementation that meets the reference monitor concept.", - "links": [ - { - "href": "#ac-16", - "rel": "related" - }, - { - "href": "#ac-25", - "rel": "related" - } - ] - }, - { - "id": "sc-11_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-11_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-11[1]" - } - ], - "prose": "the organization defines security functions of the information system;" - }, - { - "id": "sc-11_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-11[2]" - } - ], - "prose": "the organization-defined security functions include at a minimum, information system authentication and re-authentication; and" - }, - { - "id": "sc-11_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-11[3]" - } - ], - "prose": "the information system establishes a trusted communications path between the user and the organization-defined security functions of the system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing trusted communications paths\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nassessment results from independent, testing organizations\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing trusted communications paths" - } - ] - } - ], - "controls": [ - { - "id": "sc-11.1", - "class": "SP800-53-enhancement", - "title": "Logical Isolation", - "props": [ - { - "name": "label", - "value": "SC-11(1)" - }, - { - "name": "sort-id", - "value": "sc-11.01" - } - ], - "parts": [ - { - "id": "sc-11.1_smt", - "name": "statement", - "prose": "The information system provides a trusted communications path that is logically isolated and distinguishable from other paths." - }, - { - "id": "sc-11.1_obj", - "name": "objective", - "prose": "Determine if the information system provides a trusted communications path that is:", - "parts": [ - { - "id": "sc-11.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-11(1)[1]" - } - ], - "prose": "logically isolated; and" - }, - { - "id": "sc-11.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-11(1)[2]" - } - ], - "prose": "distinguishable from other paths." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing trusted communications paths\n\nsecurity plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nassessment results from independent, testing organizations\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing trusted communications paths" - } - ] - } - ] - } - ] - }, - { - "id": "sc-12", - "class": "SP800-53", - "title": "Cryptographic Key Establishment and Management", - "params": [ - { - "id": "sc-12_prm_1", - "label": "organization-defined requirements for key generation, distribution, storage, access, and destruction" - } - ], - "props": [ - { - "name": "label", - "value": "SC-12" - }, - { - "name": "sort-id", - "value": "sc-12" - } - ], - "links": [ - { - "href": "#81f09e01-d0b0-4ae2-aa6a-064ed9950070", - "rel": "reference" - }, - { - "href": "#a6c774c0-bf50-4590-9841-2a5c1c91ac6f", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sc-12_smt", - "name": "statement", - "prose": "The organization establishes and manages cryptographic keys for required cryptography employed within the information system in accordance with {{ insert: param, sc-12_prm_1 }}." - }, - { - "id": "sc-12_gdn", - "name": "guidance", - "prose": "Cryptographic key management and establishment can be performed using manual procedures or automated mechanisms with supporting manual procedures. Organizations define key management requirements in accordance with applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance, specifying appropriate options, levels, and parameters. Organizations manage trust stores to ensure that only approved trust anchors are in such trust stores. This includes certificates with visibility external to organizational information systems and certificates related to the internal operations of systems.", - "links": [ - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#sc-17", - "rel": "related" - } - ] - }, - { - "id": "sc-12_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-12_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-12[1]" - } - ], - "prose": "defines requirements for cryptographic key:", - "parts": [ - { - "id": "sc-12_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-12[1][a]" - } - ], - "prose": "generation;" - }, - { - "id": "sc-12_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-12[1][b]" - } - ], - "prose": "distribution;" - }, - { - "id": "sc-12_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-12[1][c]" - } - ], - "prose": "storage;" - }, - { - "id": "sc-12_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-12[1][d]" - } - ], - "prose": "access;" - }, - { - "id": "sc-12_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-12[1][e]" - } - ], - "prose": "destruction; and" - } - ] - }, - { - "id": "sc-12_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-12[2]" - } - ], - "prose": "establishes and manages cryptographic keys for required cryptography employed within the information system in accordance with organization-defined requirements for key generation, distribution, storage, access, and destruction." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing cryptographic key establishment and management\n\ninformation system design documentation\n\ncryptographic mechanisms\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for cryptographic key establishment and/or management" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing cryptographic key establishment and management" - } - ] - } - ], - "controls": [ - { - "id": "sc-12.1", - "class": "SP800-53-enhancement", - "title": "Availability", - "props": [ - { - "name": "label", - "value": "SC-12(1)" - }, - { - "name": "sort-id", - "value": "sc-12.01" - } - ], - "parts": [ - { - "id": "sc-12.1_smt", - "name": "statement", - "prose": "The organization maintains availability of information in the event of the loss of cryptographic keys by users." - }, - { - "id": "sc-12.1_gdn", - "name": "guidance", - "prose": "Escrowing of encryption keys is a common practice for ensuring availability in the event of loss of keys (e.g., due to forgotten passphrase)." - }, - { - "id": "sc-12.1_obj", - "name": "objective", - "prose": "Determine if the organization maintains availability of information in the event of the loss of cryptographic keys by users." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing cryptographic key establishment, management, and recovery\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for cryptographic key establishment or management" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing cryptographic key establishment and management" - } - ] - } - ] - }, - { - "id": "sc-12.2", - "class": "SP800-53-enhancement", - "title": "Symmetric Keys", - "params": [ - { - "id": "sc-12.2_prm_1", - "select": { - "choice": [ - "NIST FIPS-compliant", - "NSA-approved" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "SC-12(2)" - }, - { - "name": "sort-id", - "value": "sc-12.02" - } - ], - "parts": [ - { - "id": "sc-12.2_smt", - "name": "statement", - "prose": "The organization produces, controls, and distributes symmetric cryptographic keys using {{ insert: param, sc-12.2_prm_1 }} key management technology and processes." - }, - { - "id": "sc-12.2_obj", - "name": "objective", - "prose": "Determine if the organization produces, controls, and distributes symmetric cryptographic keys using one of the following:", - "parts": [ - { - "id": "sc-12.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-12(2)[1]" - } - ], - "prose": "NIST FIPS-compliant key management technology and processes; or" - }, - { - "id": "sc-12.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-12(2)[2]" - } - ], - "prose": "NSA-approved key management technology and processes." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing cryptographic key establishment and management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of FIPS validated cryptographic products\n\nlist of NSA-approved cryptographic products\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with responsibilities for cryptographic key establishment or management" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing symmetric cryptographic key establishment and management" - } - ] - } - ] - }, - { - "id": "sc-12.3", - "class": "SP800-53-enhancement", - "title": "Asymmetric Keys", - "params": [ - { - "id": "sc-12.3_prm_1", - "select": { - "choice": [ - "NSA-approved key management technology and processes", - "approved PKI Class 3 certificates or prepositioned keying material", - "approved PKI Class 3 or Class 4 certificates and hardware security tokens that protect the user’s private key" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "SC-12(3)" - }, - { - "name": "sort-id", - "value": "sc-12.03" - } - ], - "parts": [ - { - "id": "sc-12.3_smt", - "name": "statement", - "prose": "The organization produces, controls, and distributes asymmetric cryptographic keys using {{ insert: param, sc-12.3_prm_1 }}." - }, - { - "id": "sc-12.3_obj", - "name": "objective", - "prose": "Determine if the organization produces, controls, and distributes asymmetric cryptographic keys using one of the following:", - "parts": [ - { - "id": "sc-12.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-12(3)[1]" - } - ], - "prose": "NSA-approved key management technology and processes;" - }, - { - "id": "sc-12.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-12(3)[2]" - } - ], - "prose": "approved PKI Class 3 certificates or prepositioned keying material; or" - }, - { - "id": "sc-12.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-12(3)[3]" - } - ], - "prose": "approved PKI Class 3 or Class 4 certificates and hardware security tokens that protect the user’s private key." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing cryptographic key establishment and management\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of NSA-approved cryptographic products\n\nlist of approved PKI Class 3 and Class 4 certificates\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with responsibilities for cryptographic key establishment or management\n\norganizational personnel with responsibilities for PKI certificates" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing asymmetric cryptographic key establishment and management" - } - ] - } - ] - }, - { - "id": "sc-12.4", - "class": "SP800-53-enhancement", - "title": "PKI Certificates", - "props": [ - { - "name": "label", - "value": "SC-12(4)" - }, - { - "name": "sort-id", - "value": "sc-12.04" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-12", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sc-12.5", - "class": "SP800-53-enhancement", - "title": "PKI Certificates / Hardware Tokens", - "props": [ - { - "name": "label", - "value": "SC-12(5)" - }, - { - "name": "sort-id", - "value": "sc-12.05" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-12", - "rel": "incorporated-into" - } - ] - } - ] - }, - { - "id": "sc-13", - "class": "SP800-53", - "title": "Cryptographic Protection", - "params": [ - { - "id": "sc-13_prm_1", - "label": "organization-defined cryptographic uses and type of cryptography required for each use" - } - ], - "props": [ - { - "name": "label", - "value": "SC-13" - }, - { - "name": "sort-id", - "value": "sc-13" - } - ], - "links": [ - { - "href": "#39f9087d-7687-46d2-8eda-b6f4b7a4d8a9", - "rel": "reference" - }, - { - "href": "#6a1041fc-054e-4230-946b-2e6f4f3731bb", - "rel": "reference" - }, - { - "href": "#9b97ed27-3dd6-4f9a-ade5-1b43e9669794", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sc-13_smt", - "name": "statement", - "prose": "The information system implements {{ insert: param, sc-13_prm_1 }} in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards." - }, - { - "id": "sc-13_gdn", - "name": "guidance", - "prose": "Cryptography can be employed to support a variety of security solutions including, for example, the protection of classified and Controlled Unclassified Information, the provision of digital signatures, and the enforcement of information separation when authorized individuals have the necessary clearances for such information but lack the necessary formal access approvals. Cryptography can also be used to support random number generation and hash generation. Generally applicable cryptographic standards include FIPS-validated cryptography and NSA-approved cryptography. This control does not impose any requirements on organizations to use cryptography. However, if cryptography is required based on the selection of other security controls, organizations define each type of cryptographic use and the type of cryptography required (e.g., protection of classified information: NSA-approved cryptography; provision of digital signatures: FIPS-validated cryptography).", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-7", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "#au-10", - "rel": "related" - }, - { - "href": "#cm-11", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ia-7", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-28", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "sc-13_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-13_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-13[1]" - } - ], - "prose": "the organization defines cryptographic uses; and" - }, - { - "id": "sc-13_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-13[2]" - } - ], - "prose": "the organization defines the type of cryptography required for each use; and" - }, - { - "id": "sc-13_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-13[3]" - } - ], - "prose": "the information system implements the organization-defined cryptographic uses and type of cryptography required for each use in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing cryptographic protection\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ncryptographic module validation certificates\n\nlist of FIPS validated cryptographic modules\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with responsibilities for cryptographic protection" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing cryptographic protection" - } - ] - } - ], - "controls": [ - { - "id": "sc-13.1", - "class": "SP800-53-enhancement", - "title": "Fips-validated Cryptography", - "props": [ - { - "name": "label", - "value": "SC-13(1)" - }, - { - "name": "sort-id", - "value": "sc-13.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-13", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sc-13.2", - "class": "SP800-53-enhancement", - "title": "Nsa-approved Cryptography", - "props": [ - { - "name": "label", - "value": "SC-13(2)" - }, - { - "name": "sort-id", - "value": "sc-13.02" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-13", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sc-13.3", - "class": "SP800-53-enhancement", - "title": "Individuals Without Formal Access Approvals", - "props": [ - { - "name": "label", - "value": "SC-13(3)" - }, - { - "name": "sort-id", - "value": "sc-13.03" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-13", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sc-13.4", - "class": "SP800-53-enhancement", - "title": "Digital Signatures", - "props": [ - { - "name": "label", - "value": "SC-13(4)" - }, - { - "name": "sort-id", - "value": "sc-13.04" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-13", - "rel": "incorporated-into" - } - ] - } - ] - }, - { - "id": "sc-14", - "class": "SP800-53", - "title": "Public Access Protections", - "props": [ - { - "name": "label", - "value": "SC-14" - }, - { - "name": "sort-id", - "value": "sc-14" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "incorporated-into" - }, - { - "href": "#ac-3", - "rel": "incorporated-into" - }, - { - "href": "#ac-5", - "rel": "incorporated-into" - }, - { - "href": "#ac-6", - "rel": "incorporated-into" - }, - { - "href": "#si-3", - "rel": "incorporated-into" - }, - { - "href": "#si-4", - "rel": "incorporated-into" - }, - { - "href": "#si-5", - "rel": "incorporated-into" - }, - { - "href": "#si-7", - "rel": "incorporated-into" - }, - { - "href": "#si-10", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sc-15", - "class": "SP800-53", - "title": "Collaborative Computing Devices", - "params": [ - { - "id": "sc-15_prm_1", - "label": "organization-defined exceptions where remote activation is to be allowed" - } - ], - "props": [ - { - "name": "label", - "value": "SC-15" - }, - { - "name": "sort-id", - "value": "sc-15" - } - ], - "parts": [ - { - "id": "sc-15_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "sc-15_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Prohibits remote activation of collaborative computing devices with the following exceptions: {{ insert: param, sc-15_prm_1 }}; and" - }, - { - "id": "sc-15_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Provides an explicit indication of use to users physically present at the devices." - } - ] - }, - { - "id": "sc-15_gdn", - "name": "guidance", - "prose": "Collaborative computing devices include, for example, networked white boards, cameras, and microphones. Explicit indication of use includes, for example, signals to users when collaborative computing devices are activated.", - "links": [ - { - "href": "#ac-21", - "rel": "related" - } - ] - }, - { - "id": "sc-15_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-15.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-15(a)" - } - ], - "parts": [ - { - "id": "sc-15.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-15(a)[1]" - } - ], - "prose": "the organization defines exceptions where remote activation of collaborative computing devices is to be allowed;" - }, - { - "id": "sc-15.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-15(a)[2]" - } - ], - "prose": "the information system prohibits remote activation of collaborative computing devices, except for organization-defined exceptions where remote activation is to be allowed; and" - } - ] - }, - { - "id": "sc-15.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-15(b)" - } - ], - "prose": "the information system provides an explicit indication of use to users physically present at the devices." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing collaborative computing\n\naccess control policy and procedures\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with responsibilities for managing collaborative computing devices" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing management of remote activation of collaborative computing devices\n\nautomated mechanisms providing an indication of use of collaborative computing devices" - } - ] - } - ], - "controls": [ - { - "id": "sc-15.1", - "class": "SP800-53-enhancement", - "title": "Physical Disconnect", - "props": [ - { - "name": "label", - "value": "SC-15(1)" - }, - { - "name": "sort-id", - "value": "sc-15.01" - } - ], - "parts": [ - { - "id": "sc-15.1_smt", - "name": "statement", - "prose": "The information system provides physical disconnect of collaborative computing devices in a manner that supports ease of use." - }, - { - "id": "sc-15.1_gdn", - "name": "guidance", - "prose": "Failing to physically disconnect from collaborative computing devices can result in subsequent compromises of organizational information. Providing easy methods to physically disconnect from such devices after a collaborative computing session helps to ensure that participants actually carry out the disconnect activity without having to go through complex and tedious procedures." - }, - { - "id": "sc-15.1_obj", - "name": "objective", - "prose": "Determine if the information system provides physical disconnect of collaborative computing devices in a manner that supports ease of use." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing collaborative computing\n\naccess control policy and procedures\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with responsibilities for managing collaborative computing devices" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing physical disconnect of collaborative computing devices" - } - ] - } - ] - }, - { - "id": "sc-15.2", - "class": "SP800-53-enhancement", - "title": "Blocking Inbound / Outbound Communications Traffic", - "props": [ - { - "name": "label", - "value": "SC-15(2)" - }, - { - "name": "sort-id", - "value": "sc-15.02" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-7", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sc-15.3", - "class": "SP800-53-enhancement", - "title": "Disabling / Removal in Secure Work Areas", - "params": [ - { - "id": "sc-15.3_prm_1", - "label": "organization-defined information systems or information system components" - }, - { - "id": "sc-15.3_prm_2", - "label": "organization-defined secure work areas" - } - ], - "props": [ - { - "name": "label", - "value": "SC-15(3)" - }, - { - "name": "sort-id", - "value": "sc-15.03" - } - ], - "parts": [ - { - "id": "sc-15.3_smt", - "name": "statement", - "prose": "The organization disables or removes collaborative computing devices from {{ insert: param, sc-15.3_prm_1 }} in {{ insert: param, sc-15.3_prm_2 }}." - }, - { - "id": "sc-15.3_gdn", - "name": "guidance", - "prose": "Failing to disable or remove collaborative computing devices from information systems or information system components can result in subsequent compromises of organizational information including, for example, eavesdropping on conversations." - }, - { - "id": "sc-15.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-15.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-15(3)[1]" - } - ], - "prose": "defines information systems or information system components from which collaborative computing devices are to be disabled or removed;" - }, - { - "id": "sc-15.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-15(3)[2]" - } - ], - "prose": "defines secure work areas where collaborative computing devices are to be disabled or removed from information systems or information system components placed in such work areas; and" - }, - { - "id": "sc-15.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-15(3)[3]" - } - ], - "prose": "disables or removes collaborative computing devices from organization-defined information systems or information system components in organization-defined secure work areas." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing collaborative computing\n\naccess control policy and procedures\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of secure work areas\n\ninformation systems or information system components in secured work areas where collaborative computing devices are to be disabled or removed\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for managing collaborative computing devices" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing the capability to disable collaborative computing devices" - } - ] - } - ] - }, - { - "id": "sc-15.4", - "class": "SP800-53-enhancement", - "title": "Explicitly Indicate Current Participants", - "params": [ - { - "id": "sc-15.4_prm_1", - "label": "organization-defined online meetings and teleconferences" - } - ], - "props": [ - { - "name": "label", - "value": "SC-15(4)" - }, - { - "name": "sort-id", - "value": "sc-15.04" - } - ], - "parts": [ - { - "id": "sc-15.4_smt", - "name": "statement", - "prose": "The information system provides an explicit indication of current participants in {{ insert: param, sc-15.4_prm_1 }}." - }, - { - "id": "sc-15.4_gdn", - "name": "guidance", - "prose": "This control enhancement helps to prevent unauthorized individuals from participating in collaborative computing sessions without the explicit knowledge of other participants." - }, - { - "id": "sc-15.4_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-15.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-15(4)[1]" - } - ], - "prose": "the organization defines online meetings and teleconferences for which an explicit indication of current participants is to be provided; and" - }, - { - "id": "sc-15.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-15(4)[2]" - } - ], - "prose": "the information system provides an explicit indication of current participants in organization-defined meetings and teleconferences." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing collaborative computing\n\naccess control policy and procedures\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nlist of types of meetings and teleconferences requiring explicit indication of current participants\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for managing collaborative computing devices" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing the capability to indicate participants on collaborative computing devices" - } - ] - } - ] - } - ] - }, - { - "id": "sc-16", - "class": "SP800-53", - "title": "Transmission of Security Attributes", - "params": [ - { - "id": "sc-16_prm_1", - "label": "organization-defined security attributes" - } - ], - "props": [ - { - "name": "label", - "value": "SC-16" - }, - { - "name": "sort-id", - "value": "sc-16" - } - ], - "parts": [ - { - "id": "sc-16_smt", - "name": "statement", - "prose": "The information system associates {{ insert: param, sc-16_prm_1 }} with information exchanged between information systems and between system components." - }, - { - "id": "sc-16_gdn", - "name": "guidance", - "prose": "Security attributes can be explicitly or implicitly associated with the information contained in organizational information systems or system components.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-16", - "rel": "related" - } - ] - }, - { - "id": "sc-16_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-16_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-16[1]" - } - ], - "prose": "the organization defines security attributes to be associated with information exchanged:", - "parts": [ - { - "id": "sc-16_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-16[1][a]" - } - ], - "prose": "between information systems;" - }, - { - "id": "sc-16_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-16[1][b]" - } - ], - "prose": "between system components;" - } - ] - }, - { - "id": "sc-16_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-16[2]" - } - ], - "prose": "the information system associates organization-defined security attributes with information exchanged:", - "parts": [ - { - "id": "sc-16_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-16[2][a]" - } - ], - "prose": "between information systems; and" - }, - { - "id": "sc-16_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-16[2][b]" - } - ], - "prose": "between system components." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing transmission of security attributes\n\naccess control policy and procedures\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing transmission of security attributes between information systems" - } - ] - } - ], - "controls": [ - { - "id": "sc-16.1", - "class": "SP800-53-enhancement", - "title": "Integrity Validation", - "props": [ - { - "name": "label", - "value": "SC-16(1)" - }, - { - "name": "sort-id", - "value": "sc-16.01" - } - ], - "parts": [ - { - "id": "sc-16.1_smt", - "name": "statement", - "prose": "The information system validates the integrity of transmitted security attributes." - }, - { - "id": "sc-16.1_gdn", - "name": "guidance", - "prose": "This control enhancement ensures that the verification of the integrity of transmitted information includes security attributes.", - "links": [ - { - "href": "#au-10", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - } - ] - }, - { - "id": "sc-16.1_obj", - "name": "objective", - "prose": "Determine if the information system validates the integrity of transmitted security attributes." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing transmission of security attributes\n\naccess control policy and procedures\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing validation of the integrity of transmitted security attributes" - } - ] - } - ] - } - ] - }, - { - "id": "sc-17", - "class": "SP800-53", - "title": "Public Key Infrastructure Certificates", - "params": [ - { - "id": "sc-17_prm_1", - "label": "organization-defined certificate policy" - } - ], - "props": [ - { - "name": "label", - "value": "SC-17" - }, - { - "name": "sort-id", - "value": "sc-17" - } - ], - "links": [ - { - "href": "#58ad6f27-af99-429f-86a8-8bb767b014b9", - "rel": "reference" - }, - { - "href": "#8f174e91-844e-4cf1-a72a-45c119a3a8dd", - "rel": "reference" - }, - { - "href": "#644f44a9-a2de-4494-9c04-cd37fba45471", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sc-17_smt", - "name": "statement", - "prose": "The organization issues public key certificates under an {{ insert: param, sc-17_prm_1 }} or obtains public key certificates from an approved service provider." - }, - { - "id": "sc-17_gdn", - "name": "guidance", - "prose": "For all certificates, organizations manage information system trust stores to ensure only approved trust anchors are in the trust stores. This control addresses both certificates with visibility external to organizational information systems and certificates related to the internal operations of systems, for example, application-specific time services.", - "links": [ - { - "href": "#sc-12", - "rel": "related" - } - ] - }, - { - "id": "sc-17_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-17_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-17[1]" - } - ], - "prose": "defines a certificate policy for issuing public key certificates;" - }, - { - "id": "sc-17_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-17[2]" - } - ], - "prose": "issues public key certificates:", - "parts": [ - { - "id": "sc-17_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-17[2][a]" - } - ], - "prose": "under an organization-defined certificate policy: or" - }, - { - "id": "sc-17_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-17[2][b]" - } - ], - "prose": "obtains public key certificates from an approved service provider." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing public key infrastructure certificates\n\npublic key certificate policy or policies\n\npublic key issuing process\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for issuing public key certificates\n\nservice providers" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing the management of public key infrastructure certificates" - } - ] - } - ] - }, - { - "id": "sc-18", - "class": "SP800-53", - "title": "Mobile Code", - "props": [ - { - "name": "label", - "value": "SC-18" - }, - { - "name": "sort-id", - "value": "sc-18" - } - ], - "links": [ - { - "href": "#e716cd51-d1d5-4c6a-967a-22e9fbbc42f1", - "rel": "reference" - }, - { - "href": "#e6522953-6714-435d-a0d3-140df554c186", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sc-18_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sc-18_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Defines acceptable and unacceptable mobile code and mobile code technologies;" - }, - { - "id": "sc-18_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Establishes usage restrictions and implementation guidance for acceptable mobile code and mobile code technologies; and" - }, - { - "id": "sc-18_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Authorizes, monitors, and controls the use of mobile code within the information system." - } - ] - }, - { - "id": "sc-18_gdn", - "name": "guidance", - "prose": "Decisions regarding the employment of mobile code within organizational information systems are based on the potential for the code to cause damage to the systems if used maliciously. Mobile code technologies include, for example, Java, JavaScript, ActiveX, Postscript, PDF, Shockwave movies, Flash animations, and VBScript. Usage restrictions and implementation guidance apply to both the selection and use of mobile code installed on servers and mobile code downloaded and executed on individual workstations and devices (e.g., smart phones). Mobile code policy and procedures address preventing the development, acquisition, or introduction of unacceptable mobile code within organizational information systems.", - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - } - ] - }, - { - "id": "sc-18_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-18.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(a)" - } - ], - "prose": "defines acceptable and unacceptable mobile code and mobile code technologies;" - }, - { - "id": "sc-18.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(b)" - } - ], - "parts": [ - { - "id": "sc-18.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(b)[1]" - } - ], - "prose": "establishes usage restrictions for acceptable mobile code and mobile code technologies;" - }, - { - "id": "sc-18.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(b)[2]" - } - ], - "prose": "establishes implementation guidance for acceptable mobile code and mobile code technologies;" - } - ] - }, - { - "id": "sc-18.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(c)" - } - ], - "parts": [ - { - "id": "sc-18.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(c)[1]" - } - ], - "prose": "authorizes the use of mobile code within the information system;" - }, - { - "id": "sc-18.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(c)[2]" - } - ], - "prose": "monitors the use of mobile code within the information system; and" - }, - { - "id": "sc-18.c_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(c)[3]" - } - ], - "prose": "controls the use of mobile code within the information system." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing mobile code\n\nmobile code usage restrictions, mobile code implementation policy and procedures\n\nlist of acceptable mobile code and mobile code technologies\n\nlist of unacceptable mobile code and mobile technologies\n\nauthorization records\n\ninformation system monitoring records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for managing mobile code" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational process for controlling, authorizing, monitoring, and restricting mobile code\n\nautomated mechanisms supporting and/or implementing the management of mobile code\n\nautomated mechanisms supporting and/or implementing the monitoring of mobile code" - } - ] - } - ], - "controls": [ - { - "id": "sc-18.1", - "class": "SP800-53-enhancement", - "title": "Identify Unacceptable Code / Take Corrective Actions", - "params": [ - { - "id": "sc-18.1_prm_1", - "label": "organization-defined unacceptable mobile code" - }, - { - "id": "sc-18.1_prm_2", - "label": "organization-defined corrective actions" - } - ], - "props": [ - { - "name": "label", - "value": "SC-18(1)" - }, - { - "name": "sort-id", - "value": "sc-18.01" - } - ], - "parts": [ - { - "id": "sc-18.1_smt", - "name": "statement", - "prose": "The information system identifies {{ insert: param, sc-18.1_prm_1 }} and takes {{ insert: param, sc-18.1_prm_2 }}." - }, - { - "id": "sc-18.1_gdn", - "name": "guidance", - "prose": "Corrective actions when unacceptable mobile code is detected include, for example, blocking, quarantine, or alerting administrators. Blocking includes, for example, preventing transmission of word processing files with embedded macros when such macros have been defined to be unacceptable mobile code." - }, - { - "id": "sc-18.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-18.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(1)[1]" - } - ], - "prose": "the organization defines unacceptable mobile code to be identified by the information system;" - }, - { - "id": "sc-18.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(1)[2]" - } - ], - "prose": "the organization defines correctives actions to be taken when the information system identifies organization-defined unacceptable mobile code;" - }, - { - "id": "sc-18.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(1)[3]" - } - ], - "prose": "the information system:", - "parts": [ - { - "id": "sc-18.1_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(1)[3][a]" - } - ], - "prose": "identifies organization-defined unacceptable mobile code; and" - }, - { - "id": "sc-18.1_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(1)[3][b]" - } - ], - "prose": "takes organization-defined corrective actions." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing mobile code\n\nmobile code usage restrictions, mobile code implementation policy and procedures\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of unacceptable mobile code\n\nlist of corrective actions to be taken when unacceptable mobile code is identified\n\ninformation system monitoring records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with responsibilities for managing mobile code" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing mobile code detection, inspection, and corrective capability" - } - ] - } - ] - }, - { - "id": "sc-18.2", - "class": "SP800-53-enhancement", - "title": "Acquisition / Development / Use", - "params": [ - { - "id": "sc-18.2_prm_1", - "label": "organization-defined mobile code requirements" - } - ], - "props": [ - { - "name": "label", - "value": "SC-18(2)" - }, - { - "name": "sort-id", - "value": "sc-18.02" - } - ], - "parts": [ - { - "id": "sc-18.2_smt", - "name": "statement", - "prose": "The organization ensures that the acquisition, development, and use of mobile code to be deployed in the information system meets {{ insert: param, sc-18.2_prm_1 }}." - }, - { - "id": "sc-18.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-18.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(2)[1]" - } - ], - "prose": "defines requirements for:", - "parts": [ - { - "id": "sc-18.2_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(2)[1][a]" - } - ], - "prose": "the acquisition of mobile code;" - }, - { - "id": "sc-18.2_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(2)[1][b]" - } - ], - "prose": "the development of mobile code;" - }, - { - "id": "sc-18.2_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(2)[1][c]" - } - ], - "prose": "the use of mobile code; and" - } - ] - }, - { - "id": "sc-18.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(2)[2]" - } - ], - "prose": "ensures that the acquisition, development, and use of mobile code to be deployed in the information system meets organization-defined mobile code requirements." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing mobile code\n\nmobile code requirements\n\nmobile code usage restrictions, mobile code implementation policy and procedures\n\nacquisition documentation\n\nacquisition contracts for information system, system component, or information system service\n\nsystem development life cycle documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for managing mobile code\n\norganizational personnel with acquisition and contracting responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for the acquisition, development, and use of mobile code" - } - ] - } - ] - }, - { - "id": "sc-18.3", - "class": "SP800-53-enhancement", - "title": "Prevent Downloading / Execution", - "params": [ - { - "id": "sc-18.3_prm_1", - "label": "organization-defined unacceptable mobile code" - } - ], - "props": [ - { - "name": "label", - "value": "SC-18(3)" - }, - { - "name": "sort-id", - "value": "sc-18.03" - } - ], - "parts": [ - { - "id": "sc-18.3_smt", - "name": "statement", - "prose": "The information system prevents the download and execution of {{ insert: param, sc-18.3_prm_1 }}." - }, - { - "id": "sc-18.3_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-18.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(3)[1]" - } - ], - "prose": "the organization defines unacceptable mobile code to be prevented from downloading and execution;" - }, - { - "id": "sc-18.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(3)[2]" - } - ], - "prose": "the information system prevents the:", - "parts": [ - { - "id": "sc-18.3_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(3)[2][a]" - } - ], - "prose": "download of organization-defined unacceptable mobile code; and" - }, - { - "id": "sc-18.3_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(3)[2][b]" - } - ], - "prose": "execution of organization-defined unacceptable mobile code." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing mobile code\n\nmobile code usage restrictions, mobile code implementation policy and procedures\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with responsibilities for managing mobile code" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms preventing download and execution of unacceptable mobile code" - } - ] - } - ] - }, - { - "id": "sc-18.4", - "class": "SP800-53-enhancement", - "title": "Prevent Automatic Execution", - "params": [ - { - "id": "sc-18.4_prm_1", - "label": "organization-defined software applications" - }, - { - "id": "sc-18.4_prm_2", - "label": "organization-defined actions" - } - ], - "props": [ - { - "name": "label", - "value": "SC-18(4)" - }, - { - "name": "sort-id", - "value": "sc-18.04" - } - ], - "parts": [ - { - "id": "sc-18.4_smt", - "name": "statement", - "prose": "The information system prevents the automatic execution of mobile code in {{ insert: param, sc-18.4_prm_1 }} and enforces {{ insert: param, sc-18.4_prm_2 }} prior to executing the code." - }, - { - "id": "sc-18.4_gdn", - "name": "guidance", - "prose": "Actions enforced before executing mobile code, include, for example, prompting users prior to opening electronic mail attachments. Preventing automatic execution of mobile code includes, for example, disabling auto execute features on information system components employing portable storage devices such as Compact Disks (CDs), Digital Video Disks (DVDs), and Universal Serial Bus (USB) devices." - }, - { - "id": "sc-18.4_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-18.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(4)[1]" - } - ], - "prose": "the organization defines software applications in which the automatic execution of mobile code is to be prohibited;" - }, - { - "id": "sc-18.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(4)[2]" - } - ], - "prose": "the organization defines actions to be enforced by the information system prior to executing mobile code;" - }, - { - "id": "sc-18.4_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(4)[3]" - } - ], - "prose": "the information system prevents the automatic execution of mobile code in the organization-defined software applications; and" - }, - { - "id": "sc-18.4_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-18(4)[4]" - } - ], - "prose": "the information system enforces organization-defined actions prior to executing the code." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing mobile code\n\nmobile code usage restrictions\n\nmobile code implementation policy and procedures\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of software applications for which automatic execution of mobile code must be prohibited\n\nlist of actions required before execution of mobile code\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with responsibilities for managing mobile code" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms preventing automatic execution of unacceptable mobile code\n\nautomated mechanisms enforcing actions to be taken prior to the execution of the mobile code" - } - ] - } - ] - }, - { - "id": "sc-18.5", - "class": "SP800-53-enhancement", - "title": "Allow Execution Only in Confined Environments", - "props": [ - { - "name": "label", - "value": "SC-18(5)" - }, - { - "name": "sort-id", - "value": "sc-18.05" - } - ], - "parts": [ - { - "id": "sc-18.5_smt", - "name": "statement", - "prose": "The organization allows execution of permitted mobile code only in confined virtual machine environments." - }, - { - "id": "sc-18.5_obj", - "name": "objective", - "prose": "Determine if the organization allows execution of permitted mobile code only in confined virtual machine environments." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing mobile code\n\nmobile code usage allowances\n\nmobile code usage restrictions\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of confined virtual machine environments for which execution of organizationally-acceptable mobile code is allowed\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with responsibilities for managing mobile code" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms allowing execution of permitted mobile code in confined virtual machine environments" - } - ] - } - ] - } - ] - }, - { - "id": "sc-19", - "class": "SP800-53", - "title": "Voice Over Internet Protocol", - "props": [ - { - "name": "label", - "value": "SC-19" - }, - { - "name": "sort-id", - "value": "sc-19" - } - ], - "links": [ - { - "href": "#7783f3e7-09b3-478b-9aa2-4a76dfd0ea90", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sc-19_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sc-19_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Establishes usage restrictions and implementation guidance for Voice over Internet Protocol (VoIP) technologies based on the potential to cause damage to the information system if used maliciously; and" - }, - { - "id": "sc-19_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Authorizes, monitors, and controls the use of VoIP within the information system." - } - ] - }, - { - "id": "sc-19_gdn", - "name": "guidance", - "links": [ - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-15", - "rel": "related" - } - ] - }, - { - "id": "sc-19_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-19.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-19(a)" - } - ], - "parts": [ - { - "id": "sc-19.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-19(a)[1]" - } - ], - "prose": "establishes usage restrictions for Voice over Internet Protocol (VoIP) technologies based on the potential to cause damage to the information system if used maliciously;" - }, - { - "id": "sc-19.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-19(a)[2]" - } - ], - "prose": "establishes implementation guidance for Voice over Internet Protocol (VoIP) technologies based on the potential to cause damage to the information system if used maliciously;" - } - ] - }, - { - "id": "sc-19.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-19(b)" - } - ], - "parts": [ - { - "id": "sc-19.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-19(b)[1]" - } - ], - "prose": "authorizes the use of VoIP within the information system;" - }, - { - "id": "sc-19.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-19(b)[2]" - } - ], - "prose": "monitors the use of VoIP within the information system; and" - }, - { - "id": "sc-19.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-19(b)[3]" - } - ], - "prose": "controls the use of VoIP within the information system." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing VoIP\n\nVoIP usage restrictions\n\nVoIP implementation guidance\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system monitoring records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for managing VoIP" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational process for authorizing, monitoring, and controlling VoIP\n\nautomated mechanisms supporting and/or implementing authorizing, monitoring, and controlling VoIP" - } - ] - } - ] - }, - { - "id": "sc-20", - "class": "SP800-53", - "title": "Secure Name / Address Resolution Service (authoritative Source)", - "props": [ - { - "name": "label", - "value": "SC-20" - }, - { - "name": "sort-id", - "value": "sc-20" - } - ], - "links": [ - { - "href": "#28115a56-da6b-4d44-b1df-51dd7f048a3e", - "rel": "reference" - }, - { - "href": "#6af1e841-672c-46c4-b121-96f603d04be3", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sc-20_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "sc-20_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Provides additional data origin authentication and integrity verification artifacts along with the authoritative name resolution data the system returns in response to external name/address resolution queries; and" - }, - { - "id": "sc-20_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Provides the means to indicate the security status of child zones and (if the child supports secure resolution services) to enable verification of a chain of trust among parent and child domains, when operating as part of a distributed, hierarchical namespace." - } - ] - }, - { - "id": "sc-20_gdn", - "name": "guidance", - "prose": "This control enables external clients including, for example, remote Internet clients, to obtain origin authentication and integrity verification assurances for the host/service name to network address resolution information obtained through the service. Information systems that provide name and address resolution services include, for example, domain name system (DNS) servers. Additional artifacts include, for example, DNS Security (DNSSEC) digital signatures and cryptographic keys. DNS resource records are examples of authoritative data. The means to indicate the security status of child zones includes, for example, the use of delegation signer resource records in the DNS. The DNS security controls reflect (and are referenced from) OMB Memorandum 08-23. Information systems that use technologies other than the DNS to map between host/service names and network addresses provide other means to assure the authenticity and integrity of response data.", - "links": [ - { - "href": "#au-10", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#sc-21", - "rel": "related" - }, - { - "href": "#sc-22", - "rel": "related" - } - ] - }, - { - "id": "sc-20_obj", - "name": "objective", - "prose": "Determine if the information system:", - "parts": [ - { - "id": "sc-20.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-20(a)" - } - ], - "prose": "provides additional data origin and integrity verification artifacts along with the authoritative name resolution data the system returns in response to external name/address resolution queries;" - }, - { - "id": "sc-20.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-20(b)" - } - ], - "prose": "provides the means to, when operating as part of a distributed, hierarchical namespace:", - "parts": [ - { - "id": "sc-20.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-20(b)[1]" - } - ], - "prose": "indicate the security status of child zones; and" - }, - { - "id": "sc-20.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-20(b)[2]" - } - ], - "prose": "enable verification of a chain of trust among parent and child domains (if the child supports secure resolution services)." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing secure name/address resolution service (authoritative source)\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for managing DNS" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing secure name/address resolution service" - } - ] - } - ], - "controls": [ - { - "id": "sc-20.1", - "class": "SP800-53-enhancement", - "title": "Child Subspaces", - "props": [ - { - "name": "label", - "value": "SC-20(1)" - }, - { - "name": "sort-id", - "value": "sc-20.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-20", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sc-20.2", - "class": "SP800-53-enhancement", - "title": "Data Origin / Integrity", - "props": [ - { - "name": "label", - "value": "SC-20(2)" - }, - { - "name": "sort-id", - "value": "sc-20.02" - } - ], - "parts": [ - { - "id": "sc-20.2_smt", - "name": "statement", - "prose": "The information system provides data origin and integrity protection artifacts for internal name/address resolution queries." - }, - { - "id": "sc-20.2_obj", - "name": "objective", - "prose": "Determine if the information system provides data origin and integrity protection artifacts for internal name/address resolution queries." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing secure name/address resolution service (authoritative source)\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for managing DNS" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing data origin and integrity protection for internal name/address resolution service queries" - } - ] - } - ] - } - ] - }, - { - "id": "sc-21", - "class": "SP800-53", - "title": "Secure Name / Address Resolution Service (recursive or Caching Resolver)", - "props": [ - { - "name": "label", - "value": "SC-21" - }, - { - "name": "sort-id", - "value": "sc-21" - } - ], - "links": [ - { - "href": "#6af1e841-672c-46c4-b121-96f603d04be3", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sc-21_smt", - "name": "statement", - "prose": "The information system requests and performs data origin authentication and data integrity verification on the name/address resolution responses the system receives from authoritative sources." - }, - { - "id": "sc-21_gdn", - "name": "guidance", - "prose": "Each client of name resolution services either performs this validation on its own, or has authenticated channels to trusted validation providers. Information systems that provide name and address resolution services for local clients include, for example, recursive resolving or caching domain name system (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. Information systems that use technologies other than the DNS to map between host/service names and network addresses provide other means to enable clients to verify the authenticity and integrity of response data.", - "links": [ - { - "href": "#sc-20", - "rel": "related" - }, - { - "href": "#sc-22", - "rel": "related" - } - ] - }, - { - "id": "sc-21_obj", - "name": "objective", - "prose": "Determine if the information system:", - "parts": [ - { - "id": "sc-21_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-21[1]" - } - ], - "prose": "requests data origin authentication on the name/address resolution responses the system receives from authoritative sources;" - }, - { - "id": "sc-21_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-21[2]" - } - ], - "prose": "requests data integrity verification on the name/address resolution responses the system receives from authoritative sources;" - }, - { - "id": "sc-21_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-21[3]" - } - ], - "prose": "performs data origin authentication on the name/address resolution responses the system receives from authoritative sources; and" - }, - { - "id": "sc-21_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-21[4]" - } - ], - "prose": "performs data integrity verification on the name/address resolution responses the system receives from authoritative sources." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing secure name/address resolution service (recursive or caching resolver)\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for managing DNS" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing data origin authentication and data integrity verification for name/address resolution services" - } - ] - } - ], - "controls": [ - { - "id": "sc-21.1", - "class": "SP800-53-enhancement", - "title": "Data Origin / Integrity", - "props": [ - { - "name": "label", - "value": "SC-21(1)" - }, - { - "name": "sort-id", - "value": "sc-21.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-21", - "rel": "incorporated-into" - } - ] - } - ] - }, - { - "id": "sc-22", - "class": "SP800-53", - "title": "Architecture and Provisioning for Name / Address Resolution Service", - "props": [ - { - "name": "label", - "value": "SC-22" - }, - { - "name": "sort-id", - "value": "sc-22" - } - ], - "links": [ - { - "href": "#6af1e841-672c-46c4-b121-96f603d04be3", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sc-22_smt", - "name": "statement", - "prose": "The information systems that collectively provide name/address resolution service for an organization are fault-tolerant and implement internal/external role separation." - }, - { - "id": "sc-22_gdn", - "name": "guidance", - "prose": "Information systems that provide name and address resolution services include, for example, domain name system (DNS) servers. To eliminate single points of failure and to enhance redundancy, organizations employ at least two authoritative domain name system servers, one configured as the primary server and the other configured as the secondary server. Additionally, organizations typically deploy the servers in two geographically separated network subnetworks (i.e., not located in the same physical facility). For role separation, DNS servers with internal roles only process name and address resolution requests from within organizations (i.e., from internal clients). DNS servers with external roles only process name and address resolution information requests from clients external to organizations (i.e., on external networks including the Internet). Organizations specify clients that can access authoritative DNS servers in particular roles (e.g., by address ranges, explicit lists).", - "links": [ - { - "href": "#sc-2", - "rel": "related" - }, - { - "href": "#sc-20", - "rel": "related" - }, - { - "href": "#sc-21", - "rel": "related" - }, - { - "href": "#sc-24", - "rel": "related" - } - ] - }, - { - "id": "sc-22_obj", - "name": "objective", - "prose": "Determine if the information systems that collectively provide name/address resolution service for an organization:", - "parts": [ - { - "id": "sc-22_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-22[1]" - } - ], - "prose": "are fault tolerant; and" - }, - { - "id": "sc-22_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-22[2]" - } - ], - "prose": "implement internal/external role separation." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing architecture and provisioning for name/address resolution service\n\naccess control policy and procedures\n\ninformation system design documentation\n\nassessment results from independent, testing organizations\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for managing DNS" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing name/address resolution service for fault tolerance and role separation" - } - ] - } - ] - }, - { - "id": "sc-23", - "class": "SP800-53", - "title": "Session Authenticity", - "props": [ - { - "name": "label", - "value": "SC-23" - }, - { - "name": "sort-id", - "value": "sc-23" - } - ], - "links": [ - { - "href": "#90c5bc98-f9c4-44c9-98b7-787422f0999c", - "rel": "reference" - }, - { - "href": "#99f331f2-a9f0-46c2-9856-a3cbb9b89442", - "rel": "reference" - }, - { - "href": "#1ebdf782-d95d-4a7b-8ec7-ee860951eced", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sc-23_smt", - "name": "statement", - "prose": "The information system protects the authenticity of communications sessions." - }, - { - "id": "sc-23_gdn", - "name": "guidance", - "prose": "This control addresses communications protection at the session, versus packet level (e.g., sessions in service-oriented architectures providing web-based services) and establishes grounds for confidence at both ends of communications sessions in ongoing identities of other parties and in the validity of information transmitted. Authenticity protection includes, for example, protecting against man-in-the-middle attacks/session hijacking and the insertion of false information into sessions.", - "links": [ - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-10", - "rel": "related" - }, - { - "href": "#sc-11", - "rel": "related" - } - ] - }, - { - "id": "sc-23_obj", - "name": "objective", - "prose": "Determine if the information system protects the authenticity of communications sessions." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing session authenticity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing session authenticity" - } - ] - } - ], - "controls": [ - { - "id": "sc-23.1", - "class": "SP800-53-enhancement", - "title": "Invalidate Session Identifiers at Logout", - "props": [ - { - "name": "label", - "value": "SC-23(1)" - }, - { - "name": "sort-id", - "value": "sc-23.01" - } - ], - "parts": [ - { - "id": "sc-23.1_smt", - "name": "statement", - "prose": "The information system invalidates session identifiers upon user logout or other session termination." - }, - { - "id": "sc-23.1_gdn", - "name": "guidance", - "prose": "This control enhancement curtails the ability of adversaries from capturing and continuing to employ previously valid session IDs." - }, - { - "id": "sc-23.1_obj", - "name": "objective", - "prose": "Determine if the information system invalidates session identifiers upon user logout or other session termination." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing session authenticity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing session identifier invalidation upon session termination" - } - ] - } - ] - }, - { - "id": "sc-23.2", - "class": "SP800-53-enhancement", - "title": "User-initiated Logouts / Message Displays", - "props": [ - { - "name": "label", - "value": "SC-23(2)" - }, - { - "name": "sort-id", - "value": "sc-23.02" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#ac-12.1", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sc-23.3", - "class": "SP800-53-enhancement", - "title": "Unique Session Identifiers with Randomization", - "params": [ - { - "id": "sc-23.3_prm_1", - "label": "organization-defined randomness requirements" - } - ], - "props": [ - { - "name": "label", - "value": "SC-23(3)" - }, - { - "name": "sort-id", - "value": "sc-23.03" - } - ], - "parts": [ - { - "id": "sc-23.3_smt", - "name": "statement", - "prose": "The information system generates a unique session identifier for each session with {{ insert: param, sc-23.3_prm_1 }} and recognizes only session identifiers that are system-generated." - }, - { - "id": "sc-23.3_gdn", - "name": "guidance", - "prose": "This control enhancement curtails the ability of adversaries from reusing previously valid session IDs. Employing the concept of randomness in the generation of unique session identifiers helps to protect against brute-force attacks to determine future session identifiers.", - "links": [ - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "sc-23.3_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-23.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-23(3)[1]" - } - ], - "prose": "the organization defines randomness requirements for generating a unique session identifier for each session;" - }, - { - "id": "sc-23.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-23(3)[2]" - } - ], - "prose": "the information system generates a unique session identifier for each session with organization-defined randomness requirements; and" - }, - { - "id": "sc-23.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-23(3)[3]" - } - ], - "prose": "the information system recognizes only session identifiers that are system-generated." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing session authenticity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing generating and monitoring unique session identifiers\n\nautomated mechanisms supporting and/or implementing randomness requirements" - } - ] - } - ] - }, - { - "id": "sc-23.4", - "class": "SP800-53-enhancement", - "title": "Unique Session Identifiers with Randomization", - "props": [ - { - "name": "label", - "value": "SC-23(4)" - }, - { - "name": "sort-id", - "value": "sc-23.04" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-23.3", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sc-23.5", - "class": "SP800-53-enhancement", - "title": "Allowed Certificate Authorities", - "params": [ - { - "id": "sc-23.5_prm_1", - "label": "organization-defined certificate authorities" - } - ], - "props": [ - { - "name": "label", - "value": "SC-23(5)" - }, - { - "name": "sort-id", - "value": "sc-23.05" - } - ], - "parts": [ - { - "id": "sc-23.5_smt", - "name": "statement", - "prose": "The information system only allows the use of {{ insert: param, sc-23.5_prm_1 }} for verification of the establishment of protected sessions." - }, - { - "id": "sc-23.5_gdn", - "name": "guidance", - "prose": "Reliance on certificate authorities (CAs) for the establishment of secure sessions includes, for example, the use of Secure Socket Layer (SSL) and/or Transport Layer Security (TLS) certificates. These certificates, after verification by the respective certificate authorities, facilitate the establishment of protected sessions between web clients and web servers.", - "links": [ - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "sc-23.5_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-23.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-23(5)[1]" - } - ], - "prose": "the organization defines certificate authorities to be allowed for verification of the establishment of protected sessions; and" - }, - { - "id": "sc-23.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-23(5)[2]" - } - ], - "prose": "the information system only allows the use of organization-defined certificate authorities for verification of the establishment of protected sessions." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing session authenticity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of certificate authorities allowed for verification of the establishment of protected sessions\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing management of certificate authorities" - } - ] - } - ] - } - ] - }, - { - "id": "sc-24", - "class": "SP800-53", - "title": "Fail in Known State", - "params": [ - { - "id": "sc-24_prm_1", - "label": "organization-defined known-state" - }, - { - "id": "sc-24_prm_2", - "label": "organization-defined types of failures" - }, - { - "id": "sc-24_prm_3", - "label": "organization-defined system state information" - } - ], - "props": [ - { - "name": "label", - "value": "SC-24" - }, - { - "name": "sort-id", - "value": "sc-24" - } - ], - "parts": [ - { - "id": "sc-24_smt", - "name": "statement", - "prose": "The information system fails to a {{ insert: param, sc-24_prm_1 }} for {{ insert: param, sc-24_prm_2 }} preserving {{ insert: param, sc-24_prm_3 }} in failure." - }, - { - "id": "sc-24_gdn", - "name": "guidance", - "prose": "Failure in a known state addresses security concerns in accordance with the mission/business needs of organizations. Failure in a known secure state helps to prevent the loss of confidentiality, integrity, or availability of information in the event of failures of organizational information systems or system components. Failure in a known safe state helps to prevent systems from failing to a state that may cause injury to individuals or destruction to property. Preserving information system state information facilitates system restart and return to the operational mode of organizations with less disruption of mission/business processes.", - "links": [ - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-10", - "rel": "related" - }, - { - "href": "#cp-12", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-22", - "rel": "related" - } - ] - }, - { - "id": "sc-24_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-24_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-24[1]" - } - ], - "prose": "the organization defines a known-state to which the information system is to fail in the event of a system failure;" - }, - { - "id": "sc-24_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-24[2]" - } - ], - "prose": "the organization defines types of failures for which the information system is to fail to an organization-defined known-state;" - }, - { - "id": "sc-24_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-24[3]" - } - ], - "prose": "the organization defines system state information to be preserved in the event of a system failure;" - }, - { - "id": "sc-24_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-24[4]" - } - ], - "prose": "the information system fails to the organization-defined known-state for organization-defined types of failures; and" - }, - { - "id": "sc-24_obj.5", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-24[5]" - } - ], - "prose": "the information system preserves the organization-defined system state information in the event of a system failure." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing information system failure to known state\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of failures requiring information system to fail in a known state\n\nstate information to be preserved in system failure\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing fail-in-known state capability\n\nautomated mechanisms preserving system state information in the event of a system failure" - } - ] - } - ] - }, - { - "id": "sc-25", - "class": "SP800-53", - "title": "Thin Nodes", - "params": [ - { - "id": "sc-25_prm_1", - "label": "organization-defined information system components" - } - ], - "props": [ - { - "name": "label", - "value": "SC-25" - }, - { - "name": "sort-id", - "value": "sc-25" - } - ], - "parts": [ - { - "id": "sc-25_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, sc-25_prm_1 }} with minimal functionality and information storage." - }, - { - "id": "sc-25_gdn", - "name": "guidance", - "prose": "The deployment of information system components with reduced/minimal functionality (e.g., diskless nodes and thin client technologies) reduces the need to secure every user endpoint, and may reduce the exposure of information, information systems, and services to cyber attacks.", - "links": [ - { - "href": "#sc-30", - "rel": "related" - } - ] - }, - { - "id": "sc-25_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-25_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-25[1]" - } - ], - "prose": "defines information system components to be employed with minimal functionality and information storage; and" - }, - { - "id": "sc-25_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-25[2]" - } - ], - "prose": "employs organization-defined information system components with minimal functionality and information storage." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing use of thin nodes\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing thin nodes" - } - ] - } - ] - }, - { - "id": "sc-26", - "class": "SP800-53", - "title": "Honeypots", - "props": [ - { - "name": "label", - "value": "SC-26" - }, - { - "name": "sort-id", - "value": "sc-26" - } - ], - "parts": [ - { - "id": "sc-26_smt", - "name": "statement", - "prose": "The information system includes components specifically designed to be the target of malicious attacks for the purpose of detecting, deflecting, and analyzing such attacks." - }, - { - "id": "sc-26_gdn", - "name": "guidance", - "prose": "A honeypot is set up as a decoy to attract adversaries and to deflect their attacks away from the operational systems supporting organizational missions/business function. Depending upon the specific usage of the honeypot, consultation with the Office of the General Counsel before deployment may be needed.", - "links": [ - { - "href": "#sc-30", - "rel": "related" - }, - { - "href": "#sc-44", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "sc-26_obj", - "name": "objective", - "prose": "Determine if the information system includes components specifically designed to be the target of malicious attacks for the purpose of detecting, deflecting, and analyzing such attacks." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing use of honeypots\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing honey pots" - } - ] - } - ], - "controls": [ - { - "id": "sc-26.1", - "class": "SP800-53-enhancement", - "title": "Detection of Malicious Code", - "props": [ - { - "name": "label", - "value": "SC-26(1)" - }, - { - "name": "sort-id", - "value": "sc-26.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-35", - "rel": "incorporated-into" - } - ] - } - ] - }, - { - "id": "sc-27", - "class": "SP800-53", - "title": "Platform-independent Applications", - "params": [ - { - "id": "sc-27_prm_1", - "label": "organization-defined platform-independent applications" - } - ], - "props": [ - { - "name": "label", - "value": "SC-27" - }, - { - "name": "sort-id", - "value": "sc-27" - } - ], - "parts": [ - { - "id": "sc-27_smt", - "name": "statement", - "prose": "The information system includes: {{ insert: param, sc-27_prm_1 }}." - }, - { - "id": "sc-27_gdn", - "name": "guidance", - "prose": "Platforms are combinations of hardware and software used to run software applications. Platforms include: (i) operating systems; (ii) the underlying computer architectures, or (iii) both. Platform-independent applications are applications that run on multiple platforms. Such applications promote portability and reconstitution on different platforms, increasing the availability of critical functions within organizations while information systems with specific operating systems are under attack.", - "links": [ - { - "href": "#sc-29", - "rel": "related" - } - ] - }, - { - "id": "sc-27_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-27_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-27[1]" - } - ], - "prose": "the organization defines platform-independent applications; and" - }, - { - "id": "sc-27_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-27[2]" - } - ], - "prose": "the information system includes organization-defined platform-independent applications." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing platform-independent applications\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of platform-independent applications\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing platform-independent applications" - } - ] - } - ] - }, - { - "id": "sc-28", - "class": "SP800-53", - "title": "Protection of Information at Rest", - "params": [ - { - "id": "sc-28_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "confidentiality", - "integrity" - ] - } - }, - { - "id": "sc-28_prm_2", - "label": "organization-defined information at rest" - } - ], - "props": [ - { - "name": "label", - "value": "SC-28" - }, - { - "name": "sort-id", - "value": "sc-28" - } - ], - "links": [ - { - "href": "#81f09e01-d0b0-4ae2-aa6a-064ed9950070", - "rel": "reference" - }, - { - "href": "#a6c774c0-bf50-4590-9841-2a5c1c91ac6f", - "rel": "reference" - }, - { - "href": "#3cac5e7b-9ebf-4bbb-9af5-ae032de78e8e", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sc-28_smt", - "name": "statement", - "prose": "The information system protects the {{ insert: param, sc-28_prm_1 }} of {{ insert: param, sc-28_prm_2 }}." - }, - { - "id": "sc-28_gdn", - "name": "guidance", - "prose": "This control addresses the confidentiality and integrity of information at rest and covers user information and system information. Information at rest refers to the state of information when it is located on storage devices as specific components of information systems. System-related information requiring protection includes, for example, configurations or rule sets for firewalls, gateways, intrusion detection/prevention systems, filtering routers, and authenticator content. Organizations may employ different mechanisms to achieve confidentiality and integrity protections, including the use of cryptographic mechanisms and file share scanning. Integrity protection can be achieved, for example, by implementing Write-Once-Read-Many (WORM) technologies. Organizations may also employ other security controls including, for example, secure off-line storage in lieu of online storage when adequate protection of information at rest cannot otherwise be achieved and/or continuous monitoring to identify malicious code at rest.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "sc-28_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-28_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-28[1]" - } - ], - "prose": "the organization defines information at rest requiring one or more of the following:", - "parts": [ - { - "id": "sc-28_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-28[1][a]" - } - ], - "prose": "confidentiality protection; and/or" - }, - { - "id": "sc-28_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-28[1][b]" - } - ], - "prose": "integrity protection;" - } - ] - }, - { - "id": "sc-28_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-28[2]" - } - ], - "prose": "the information system protects:", - "parts": [ - { - "id": "sc-28_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-28[2][a]" - } - ], - "prose": "the confidentiality of organization-defined information at rest; and/or" - }, - { - "id": "sc-28_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-28[2][b]" - } - ], - "prose": "the integrity of organization-defined information at rest." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing protection of information at rest\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ncryptographic mechanisms and associated configuration documentation\n\nlist of information at rest requiring confidentiality and integrity protections\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing confidentiality and integrity protections for information at rest" - } - ] - } - ], - "controls": [ - { - "id": "sc-28.1", - "class": "SP800-53-enhancement", - "title": "Cryptographic Protection", - "params": [ - { - "id": "sc-28.1_prm_1", - "label": "organization-defined information" - }, - { - "id": "sc-28.1_prm_2", - "label": "organization-defined information system components" - } - ], - "props": [ - { - "name": "label", - "value": "SC-28(1)" - }, - { - "name": "sort-id", - "value": "sc-28.01" - } - ], - "parts": [ - { - "id": "sc-28.1_smt", - "name": "statement", - "prose": "The information system implements cryptographic mechanisms to prevent unauthorized disclosure and modification of {{ insert: param, sc-28.1_prm_1 }} on {{ insert: param, sc-28.1_prm_2 }}." - }, - { - "id": "sc-28.1_gdn", - "name": "guidance", - "prose": "Selection of cryptographic mechanisms is based on the need to protect the confidentiality and integrity of organizational information. The strength of mechanism is commensurate with the security category and/or classification of the information. This control enhancement applies to significant concentrations of digital media in organizational areas designated for media storage and also to limited quantities of media generally associated with information system components in operational environments (e.g., portable storage devices, mobile devices). Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). Organizations employing cryptographic mechanisms to protect information at rest also consider cryptographic key management solutions.", - "links": [ - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - } - ] - }, - { - "id": "sc-28.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-28.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-28(1)[1]" - } - ], - "prose": "the organization defines information requiring cryptographic protection;" - }, - { - "id": "sc-28.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-28(1)[2]" - } - ], - "prose": "the organization defines information system components with organization-defined information requiring cryptographic protection; and" - }, - { - "id": "sc-28.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-28(1)[3]" - } - ], - "prose": "the information system employs cryptographic mechanisms to prevent unauthorized disclosure and modification of organization-defined information on organization-defined information system components." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing protection of information at rest\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ncryptographic mechanisms and associated configuration documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Cryptographic mechanisms implementing confidentiality and integrity protections for information at rest" - } - ] - } - ] - }, - { - "id": "sc-28.2", - "class": "SP800-53-enhancement", - "title": "Off-line Storage", - "params": [ - { - "id": "sc-28.2_prm_1", - "label": "organization-defined information" - } - ], - "props": [ - { - "name": "label", - "value": "SC-28(2)" - }, - { - "name": "sort-id", - "value": "sc-28.02" - } - ], - "parts": [ - { - "id": "sc-28.2_smt", - "name": "statement", - "prose": "The organization removes from online storage and stores off-line in a secure location {{ insert: param, sc-28.2_prm_1 }}." - }, - { - "id": "sc-28.2_gdn", - "name": "guidance", - "prose": "Removing organizational information from online information system storage to off-line storage eliminates the possibility of individuals gaining unauthorized access to the information through a network. Therefore, organizations may choose to move information to off-line storage in lieu of protecting such information in online storage." - }, - { - "id": "sc-28.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-28.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-28(2)[1]" - } - ], - "prose": "defines information to be removed from online storage and stored off-line in a secure location; and" - }, - { - "id": "sc-28.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-28(2)[2]" - } - ], - "prose": "removes organization-defined information from online storage; and" - }, - { - "id": "sc-28.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-28(2)[3]" - } - ], - "prose": "stores such information off-line in a secure location." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing protection of information at rest\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ncryptographic mechanisms and associated configuration documentation\n\noff-line storage locations for information at rest\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing removal of information from online storage\n\nautomated mechanisms supporting and/or implementing storage of information off-line" - } - ] - } - ] - } - ] - }, - { - "id": "sc-29", - "class": "SP800-53", - "title": "Heterogeneity", - "params": [ - { - "id": "sc-29_prm_1", - "label": "organization-defined information system components" - } - ], - "props": [ - { - "name": "label", - "value": "SC-29" - }, - { - "name": "sort-id", - "value": "sc-29" - } - ], - "parts": [ - { - "id": "sc-29_smt", - "name": "statement", - "prose": "The organization employs a diverse set of information technologies for {{ insert: param, sc-29_prm_1 }} in the implementation of the information system." - }, - { - "id": "sc-29_gdn", - "name": "guidance", - "prose": "Increasing the diversity of information technologies within organizational information systems reduces the impact of potential exploitations of specific technologies and also defends against common mode failures, including those failures induced by supply chain attacks. Diversity in information technologies also reduces the likelihood that the means adversaries use to compromise one information system component will be equally effective against other system components, thus further increasing the adversary work factor to successfully complete planned cyber attacks. An increase in diversity may add complexity and management overhead which could ultimately lead to mistakes and unauthorized configurations.", - "links": [ - { - "href": "#sa-12", - "rel": "related" - }, - { - "href": "#sa-14", - "rel": "related" - }, - { - "href": "#sc-27", - "rel": "related" - } - ] - }, - { - "id": "sc-29_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-29_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-29[1]" - } - ], - "prose": "defines information system components requiring a diverse set of information technologies to be employed in the implementation of the information system; and" - }, - { - "id": "sc-29_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-29[2]" - } - ], - "prose": "employs a diverse set of information technologies for organization-defined information system components in the implementation of the information system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of technologies deployed in the information system\n\nacquisition documentation\n\nacquisition contracts for information system components or services\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with information system acquisition, development, and implementation responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing employment of a diverse set of information technologies" - } - ] - } - ], - "controls": [ - { - "id": "sc-29.1", - "class": "SP800-53-enhancement", - "title": "Virtualization Techniques", - "params": [ - { - "id": "sc-29.1_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "SC-29(1)" - }, - { - "name": "sort-id", - "value": "sc-29.01" - } - ], - "parts": [ - { - "id": "sc-29.1_smt", - "name": "statement", - "prose": "The organization employs virtualization techniques to support the deployment of a diversity of operating systems and applications that are changed {{ insert: param, sc-29.1_prm_1 }}." - }, - { - "id": "sc-29.1_gdn", - "name": "guidance", - "prose": "While frequent changes to operating systems and applications pose configuration management challenges, the changes can result in an increased work factor for adversaries in order to carry out successful cyber attacks. Changing virtual operating systems or applications, as opposed to changing actual operating systems/applications, provide virtual changes that impede attacker success while reducing configuration management efforts. In addition, virtualization techniques can assist organizations in isolating untrustworthy software and/or software of dubious provenance into confined execution environments." - }, - { - "id": "sc-29.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-29.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-29(1)[1]" - } - ], - "prose": "defines a frequency to change the diversity of operating systems and applications deployed using virtualization techniques; and" - }, - { - "id": "sc-29.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-29(1)[2]" - } - ], - "prose": "employs virtualization techniques to support the deployment of a diversity of operating systems and applications that are changed with the organization-defined frequency." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nconfiguration management policy and procedures\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\nlist of operating systems and applications deployed using virtualization techniques\n\nchange control records\n\nconfiguration management records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for implementing approved virtualization techniques to the information system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing employment of a diverse set of information technologies\n\nautomated mechanisms supporting and/or implementing virtualization techniques" - } - ] - } - ] - } - ] - }, - { - "id": "sc-30", - "class": "SP800-53", - "title": "Concealment and Misdirection", - "params": [ - { - "id": "sc-30_prm_1", - "label": "organization-defined concealment and misdirection techniques" - }, - { - "id": "sc-30_prm_2", - "label": "organization-defined information systems" - }, - { - "id": "sc-30_prm_3", - "label": "organization-defined time periods" - } - ], - "props": [ - { - "name": "label", - "value": "SC-30" - }, - { - "name": "sort-id", - "value": "sc-30" - } - ], - "parts": [ - { - "id": "sc-30_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, sc-30_prm_1 }} for {{ insert: param, sc-30_prm_2 }} at {{ insert: param, sc-30_prm_3 }} to confuse and mislead adversaries." - }, - { - "id": "sc-30_gdn", - "name": "guidance", - "prose": "Concealment and misdirection techniques can significantly reduce the targeting capability of adversaries (i.e., window of opportunity and available attack surface) to initiate and complete cyber attacks. For example, virtualization techniques provide organizations with the ability to disguise information systems, potentially reducing the likelihood of successful attacks without the cost of having multiple platforms. Increased use of concealment/misdirection techniques including, for example, randomness, uncertainty, and virtualization, may sufficiently confuse and mislead adversaries and subsequently increase the risk of discovery and/or exposing tradecraft. Concealment/misdirection techniques may also provide organizations additional time to successfully perform core missions and business functions. Because of the time and effort required to support concealment/misdirection techniques, it is anticipated that such techniques would be used by organizations on a very limited basis.", - "links": [ - { - "href": "#sc-26", - "rel": "related" - }, - { - "href": "#sc-29", - "rel": "related" - }, - { - "href": "#si-14", - "rel": "related" - } - ] - }, - { - "id": "sc-30_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-30_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-30[1]" - } - ], - "prose": "defines concealment and misdirection techniques to be employed to confuse and mislead adversaries potentially targeting organizational information systems;" - }, - { - "id": "sc-30_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-30[2]" - } - ], - "prose": "defines information systems for which organization-defined concealment and misdirection techniques are to be employed;" - }, - { - "id": "sc-30_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-30[3]" - } - ], - "prose": "defines time periods to employ organization-defined concealment and misdirection techniques for organization-defined information systems; and" - }, - { - "id": "sc-30_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-30[4]" - } - ], - "prose": "employs organization-defined concealment and misdirection techniques for organization-defined information systems at organization-defined time periods to confuse and mislead adversaries." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing concealment and misdirection techniques for the information system\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\nlist of concealment and misdirection techniques to be employed for organizational information systems\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for implementing concealment and misdirection techniques for information systems" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing concealment and misdirection techniques" - } - ] - } - ], - "controls": [ - { - "id": "sc-30.1", - "class": "SP800-53-enhancement", - "title": "Virtualization Techniques", - "props": [ - { - "name": "label", - "value": "SC-30(1)" - }, - { - "name": "sort-id", - "value": "sc-30.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-29.1", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sc-30.2", - "class": "SP800-53-enhancement", - "title": "Randomness", - "params": [ - { - "id": "sc-30.2_prm_1", - "label": "organization-defined techniques" - } - ], - "props": [ - { - "name": "label", - "value": "SC-30(2)" - }, - { - "name": "sort-id", - "value": "sc-30.02" - } - ], - "parts": [ - { - "id": "sc-30.2_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, sc-30.2_prm_1 }} to introduce randomness into organizational operations and assets." - }, - { - "id": "sc-30.2_gdn", - "name": "guidance", - "prose": "Randomness introduces increased levels of uncertainty for adversaries regarding the actions organizations take in defending against cyber attacks. Such actions may impede the ability of adversaries to correctly target information resources of organizations supporting critical missions/business functions. Uncertainty may also cause adversaries to hesitate before initiating or continuing attacks. Misdirection techniques involving randomness include, for example, performing certain routine actions at different times of day, employing different information technologies (e.g., browsers, search engines), using different suppliers, and rotating roles and responsibilities of organizational personnel." - }, - { - "id": "sc-30.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-30.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-30(2)[1]" - } - ], - "prose": "defines techniques to be employed to introduce randomness into organizational operations and assets; and" - }, - { - "id": "sc-30.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-30(2)[2]" - } - ], - "prose": "employs organization-defined techniques to introduce randomness into organizational operations and assets." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing concealment and misdirection techniques for the information system\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\nlist of techniques to be employed to introduce randomness into organizational operations and assets\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for implementing concealment and misdirection techniques for information systems" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing randomness as a concealment and misdirection technique" - } - ] - } - ] - }, - { - "id": "sc-30.3", - "class": "SP800-53-enhancement", - "title": "Change Processing / Storage Locations", - "params": [ - { - "id": "sc-30.3_prm_1", - "label": "organization-defined processing and/or storage" - }, - { - "id": "sc-30.3_prm_2", - "select": { - "choice": [ - " {{ insert: param, sc-30.3_prm_3 }} ", - "at random time intervals" - ] - } - }, - { - "id": "sc-30.3_prm_3", - "depends-on": "sc-30.3_prm_2", - "label": "organization-defined time frequency" - } - ], - "props": [ - { - "name": "label", - "value": "SC-30(3)" - }, - { - "name": "sort-id", - "value": "sc-30.03" - } - ], - "parts": [ - { - "id": "sc-30.3_smt", - "name": "statement", - "prose": "The organization changes the location of {{ insert: param, sc-30.3_prm_1 }} {{ insert: param, sc-30.3_prm_2 }}]." - }, - { - "id": "sc-30.3_gdn", - "name": "guidance", - "prose": "Adversaries target critical organizational missions/business functions and the information resources supporting those missions and functions while at the same time, trying to minimize exposure of their existence and tradecraft. The static, homogeneous, and deterministic nature of organizational information systems targeted by adversaries, make such systems more susceptible to cyber attacks with less adversary cost and effort to be successful. Changing organizational processing and storage locations (sometimes referred to as moving target defense) addresses the advanced persistent threat (APT) using techniques such as virtualization, distributed processing, and replication. This enables organizations to relocate the information resources (i.e., processing and/or storage) supporting critical missions and business functions. Changing locations of processing activities and/or storage sites introduces uncertainty into the targeting activities by adversaries. This uncertainty increases the work factor of adversaries making compromises or breaches to organizational information systems much more difficult and time-consuming, and increases the chances that adversaries may inadvertently disclose aspects of tradecraft while attempting to locate critical organizational resources." - }, - { - "id": "sc-30.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-30.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-30(3)[1]" - } - ], - "prose": "defines processing and/or storage locations to be changed at time intervals specified by the organization;" - }, - { - "id": "sc-30.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-30(3)[2]" - } - ], - "prose": "defines a frequency to change the location of organization-defined processing and/or storage; and" - }, - { - "id": "sc-30.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-30(3)[3]" - } - ], - "prose": "changes the location of organization-defined processing and/or storage at one of the following:", - "parts": [ - { - "id": "sc-30.3_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-30(3)[3][a]" - } - ], - "prose": "organization-defined time intervals; or" - }, - { - "id": "sc-30.3_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-30(3)[3][b]" - } - ], - "prose": "random time intervals." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nconfiguration management policy and procedures\n\nprocedures addressing concealment and misdirection techniques for the information system\n\nlist of processing/storage locations to be changed at organizational time intervals\n\nchange control records\n\nconfiguration management records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for changing processing and/or storage locations" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing changing processing and/or storage locations" - } - ] - } - ] - }, - { - "id": "sc-30.4", - "class": "SP800-53-enhancement", - "title": "Misleading Information", - "params": [ - { - "id": "sc-30.4_prm_1", - "label": "organization-defined information system components" - } - ], - "props": [ - { - "name": "label", - "value": "SC-30(4)" - }, - { - "name": "sort-id", - "value": "sc-30.04" - } - ], - "parts": [ - { - "id": "sc-30.4_smt", - "name": "statement", - "prose": "The organization employs realistic, but misleading information in {{ insert: param, sc-30.4_prm_1 }} with regard to its security state or posture." - }, - { - "id": "sc-30.4_gdn", - "name": "guidance", - "prose": "This control enhancement misleads potential adversaries regarding the nature and extent of security safeguards deployed by organizations. As a result, adversaries may employ incorrect (and as a result ineffective) attack techniques. One way of misleading adversaries is for organizations to place misleading information regarding the specific security controls deployed in external information systems that are known to be accessed or targeted by adversaries. Another technique is the use of deception nets (e.g., honeynets, virtualized environments) that mimic actual aspects of organizational information systems but use, for example, out-of-date software configurations." - }, - { - "id": "sc-30.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-30.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-30(4)[1]" - } - ], - "prose": "defines information system components in which to employ realistic, but misleading information regarding its security state or posture; and" - }, - { - "id": "sc-30.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-30(4)[2]" - } - ], - "prose": "employs realistic, but misleading information in organization-defined information system components with regard to its security state or posture." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nconfiguration management policy and procedures\n\nprocedures addressing concealment and misdirection techniques for the information system\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for defining and employing realistic, but misleading information about the security posture of information system components" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing employment of realistic, but misleading information about the security posture of information system components" - } - ] - } - ] - }, - { - "id": "sc-30.5", - "class": "SP800-53-enhancement", - "title": "Concealment of System Components", - "params": [ - { - "id": "sc-30.5_prm_1", - "label": "organization-defined techniques" - }, - { - "id": "sc-30.5_prm_2", - "label": "organization-defined information system components" - } - ], - "props": [ - { - "name": "label", - "value": "SC-30(5)" - }, - { - "name": "sort-id", - "value": "sc-30.05" - } - ], - "parts": [ - { - "id": "sc-30.5_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, sc-30.5_prm_1 }} to hide or conceal {{ insert: param, sc-30.5_prm_2 }}." - }, - { - "id": "sc-30.5_gdn", - "name": "guidance", - "prose": "By hiding, disguising, or otherwise concealing critical information system components, organizations may be able to decrease the probability that adversaries target and successfully compromise those assets. Potential means for organizations to hide and/or conceal information system components include, for example, configuration of routers or the use of honeynets or virtualization techniques." - }, - { - "id": "sc-30.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-30.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-30(5)[1]" - } - ], - "prose": "defines techniques to be employed to hide or conceal information system components;" - }, - { - "id": "sc-30.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-30(5)[2]" - } - ], - "prose": "defines information system components to be hidden or concealed using organization-defined techniques; and" - }, - { - "id": "sc-30.5_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-30(5)[3]" - } - ], - "prose": "employs organization-defined techniques to hide or conceal organization-defined information system components." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nconfiguration management policy and procedures\n\nprocedures addressing concealment and misdirection techniques for the information system\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of techniques employed to hide or conceal information system components\n\nlist of information system components to be hidden or concealed\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for concealment of system components" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing techniques for concealment of system components" - } - ] - } - ] - } - ] - }, - { - "id": "sc-31", - "class": "SP800-53", - "title": "Covert Channel Analysis", - "params": [ - { - "id": "sc-31_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "storage", - "timing" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "SC-31" - }, - { - "name": "sort-id", - "value": "sc-31" - } - ], - "parts": [ - { - "id": "sc-31_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sc-31_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Performs a covert channel analysis to identify those aspects of communications within the information system that are potential avenues for covert {{ insert: param, sc-31_prm_1 }} channels; and" - }, - { - "id": "sc-31_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Estimates the maximum bandwidth of those channels." - } - ] - }, - { - "id": "sc-31_gdn", - "name": "guidance", - "prose": "Developers are in the best position to identify potential areas within systems that might lead to covert channels. Covert channel analysis is a meaningful activity when there is the potential for unauthorized information flows across security domains, for example, in the case of information systems containing export-controlled information and having connections to external networks (i.e., networks not controlled by organizations). Covert channel analysis is also meaningful for multilevel secure (MLS) information systems, multiple security level (MSL) systems, and cross-domain systems.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - } - ] - }, - { - "id": "sc-31_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-31.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-31(a)" - } - ], - "prose": "performs a covert channel analysis to identify those aspects of communications within the information system that are potential avenues for one or more of the following:", - "parts": [ - { - "id": "sc-31.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-31(a)[1]" - } - ], - "prose": "covert storage channels; and/or" - }, - { - "id": "sc-31.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-31(a)[2]" - } - ], - "prose": "covert timing channels; and" - } - ] - }, - { - "id": "sc-31.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-31(b)" - } - ], - "prose": "estimates the maximum bandwidth of those channels." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing covert channel analysis\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ncovert channel analysis documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with covert channel analysis responsibilities\n\ninformation system developers/integrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational process for conducting covert channel analysis\n\nautomated mechanisms supporting and/or implementing covert channel analysis\n\nautomated mechanisms supporting and/or implementing the capability to estimate the bandwidth of covert channels" - } - ] - } - ], - "controls": [ - { - "id": "sc-31.1", - "class": "SP800-53-enhancement", - "title": "Test Covert Channels for Exploitability", - "props": [ - { - "name": "label", - "value": "SC-31(1)" - }, - { - "name": "sort-id", - "value": "sc-31.01" - } - ], - "parts": [ - { - "id": "sc-31.1_smt", - "name": "statement", - "prose": "The organization tests a subset of the identified covert channels to determine which channels are exploitable." - }, - { - "id": "sc-31.1_obj", - "name": "objective", - "prose": "Determine if the organization tests a subset of identified covert channels to determine which channels are exploitable." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing covert channel analysis\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of covert channels\n\ncovert channel analysis documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with covert channel analysis responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational process for testing covert channels\n\nautomated mechanisms supporting and/or implementing testing of covert channels analysis" - } - ] - } - ] - }, - { - "id": "sc-31.2", - "class": "SP800-53-enhancement", - "title": "Maximum Bandwidth", - "params": [ - { - "id": "sc-31.2_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "storage", - "timing" - ] - } - }, - { - "id": "sc-31.2_prm_2", - "label": "organization-defined values" - } - ], - "props": [ - { - "name": "label", - "value": "SC-31(2)" - }, - { - "name": "sort-id", - "value": "sc-31.02" - } - ], - "parts": [ - { - "id": "sc-31.2_smt", - "name": "statement", - "prose": "The organization reduces the maximum bandwidth for identified covert {{ insert: param, sc-31.2_prm_1 }} channels to {{ insert: param, sc-31.2_prm_2 }}." - }, - { - "id": "sc-31.2_gdn", - "name": "guidance", - "prose": "Information system developers are in the best position to reduce the maximum bandwidth for identified covert storage and timing channels." - }, - { - "id": "sc-31.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-31.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-31(2)[1]" - } - ], - "prose": "defines values to be employed as the maximum bandwidth allowed for identified covert channels; and" - }, - { - "id": "sc-31.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-31(2)[2]" - } - ], - "prose": "reduces the maximum bandwidth to organization-defined values for one or more of the following identified:", - "parts": [ - { - "id": "sc-31.2_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-31(2)[2][a]" - } - ], - "prose": "covert storage channels; and/or" - }, - { - "id": "sc-31.2_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-31(2)[2][b]" - } - ], - "prose": "covert timing channels." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing covert channel analysis\n\nacquisition contracts for information systems or services\n\nacquisition documentation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ncovert channel analysis documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with covert channel analysis responsibilities\n\ninformation system developers/integrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational process for conducting covert channel analysis\n\nautomated mechanisms supporting and/or implementing covert channel analysis\n\nautomated mechanisms supporting and/or implementing the capability to reduce the bandwidth of covert channels" - } - ] - } - ] - }, - { - "id": "sc-31.3", - "class": "SP800-53-enhancement", - "title": "Measure Bandwidth in Operational Environments", - "params": [ - { - "id": "sc-31.3_prm_1", - "label": "organization-defined subset of identified covert channels" - } - ], - "props": [ - { - "name": "label", - "value": "SC-31(3)" - }, - { - "name": "sort-id", - "value": "sc-31.03" - } - ], - "parts": [ - { - "id": "sc-31.3_smt", - "name": "statement", - "prose": "The organization measures the bandwidth of {{ insert: param, sc-31.3_prm_1 }} in the operational environment of the information system." - }, - { - "id": "sc-31.3_gdn", - "name": "guidance", - "prose": "This control enhancement addresses covert channel bandwidth in operational environments versus developmental environments. Measuring covert channel bandwidth in operational environments helps organizations to determine how much information can be covertly leaked before such leakage adversely affects organizational missions/business functions. Covert channel bandwidth may be significantly different when measured in those settings that are independent of the particular environments of operation (e.g., laboratories or development environments)." - }, - { - "id": "sc-31.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-31.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-31(3)[1]" - } - ], - "prose": "defines subset of identified covert channels whose bandwidth is to be measured in the operational environment of the information system; and" - }, - { - "id": "sc-31.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-31(3)[2]" - } - ], - "prose": "measures the bandwidth of the organization-defined subset of identified covert channels in the operational environment of the information system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing covert channel analysis\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ncovert channel analysis documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with covert channel analysis responsibilities\n\ninformation system developers/integrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational process for conducting covert channel analysis\n\nautomated mechanisms supporting and/or implementing covert channel analysis\n\nautomated mechanisms supporting and/or implementing the capability to measure the bandwidth of covert channels" - } - ] - } - ] - } - ] - }, - { - "id": "sc-32", - "class": "SP800-53", - "title": "Information System Partitioning", - "params": [ - { - "id": "sc-32_prm_1", - "label": "organization-defined information system components" - }, - { - "id": "sc-32_prm_2", - "label": "organization-defined circumstances for physical separation of components" - } - ], - "props": [ - { - "name": "label", - "value": "SC-32" - }, - { - "name": "sort-id", - "value": "sc-32" - } - ], - "links": [ - { - "href": "#e85cdb3f-7f0a-4083-8639-f13f70d3760b", - "rel": "reference" - } - ], - "parts": [ - { - "id": "sc-32_smt", - "name": "statement", - "prose": "The organization partitions the information system into {{ insert: param, sc-32_prm_1 }} residing in separate physical domains or environments based on {{ insert: param, sc-32_prm_2 }}." - }, - { - "id": "sc-32_gdn", - "name": "guidance", - "prose": "Information system partitioning is a part of a defense-in-depth protection strategy. Organizations determine the degree of physical separation of system components from physically distinct components in separate racks in the same room, to components in separate rooms for the more critical components, to more significant geographical separation of the most critical components. Security categorization can guide the selection of appropriate candidates for domain partitioning. Managed interfaces restrict or prohibit network access and information flow among partitioned information system components.", - "links": [ - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sc-2", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - } - ] - }, - { - "id": "sc-32_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-32_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-32[1]" - } - ], - "prose": "defines circumstances for physical separation of information system components into information system partitions;" - }, - { - "id": "sc-32_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-32[2]" - } - ], - "prose": "defines information system components to reside in separate physical domains or environments based on organization-defined circumstances for physical separation of components; and" - }, - { - "id": "sc-32_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-32[3]" - } - ], - "prose": "partitions the information system into organization-defined information system components residing in separate physical domains or environments based on organization-defined circumstances for physical separation of components." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing information system partitioning\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\nlist of information system physical domains (or environments)\n\ninformation system facility diagrams\n\ninformation system network diagrams\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\ninformation system developers/integrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing physical separation of information system components" - } - ] - } - ] - }, - { - "id": "sc-33", - "class": "SP800-53", - "title": "Transmission Preparation Integrity", - "props": [ - { - "name": "label", - "value": "SC-33" - }, - { - "name": "sort-id", - "value": "sc-33" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sc-8", - "rel": "incorporated-into" - } - ] - }, - { - "id": "sc-34", - "class": "SP800-53", - "title": "Non-modifiable Executable Programs", - "params": [ - { - "id": "sc-34_prm_1", - "label": "organization-defined information system components" - }, - { - "id": "sc-34_prm_2", - "label": "organization-defined applications" - } - ], - "props": [ - { - "name": "label", - "value": "SC-34" - }, - { - "name": "sort-id", - "value": "sc-34" - } - ], - "parts": [ - { - "id": "sc-34_smt", - "name": "statement", - "prose": "The information system at {{ insert: param, sc-34_prm_1 }}:", - "parts": [ - { - "id": "sc-34_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Loads and executes the operating environment from hardware-enforced, read-only media; and" - }, - { - "id": "sc-34_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Loads and executes {{ insert: param, sc-34_prm_2 }} from hardware-enforced, read-only media." - } - ] - }, - { - "id": "sc-34_gdn", - "name": "guidance", - "prose": "The term operating environment is defined as the specific code that hosts applications, for example, operating systems, executives, or monitors including virtual machine monitors (i.e., hypervisors). It can also include certain applications running directly on hardware platforms. Hardware-enforced, read-only media include, for example, Compact Disk-Recordable (CD-R)/Digital Video Disk-Recordable (DVD-R) disk drives and one-time programmable read-only memory. The use of non-modifiable storage ensures the integrity of software from the point of creation of the read-only image. The use of reprogrammable read-only memory can be accepted as read-only media provided: (i) integrity can be adequately protected from the point of initial writing to the insertion of the memory into the information system; and (ii) there are reliable hardware protections against reprogramming the memory while installed in organizational information systems.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "sc-34_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-34_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-34[1]" - } - ], - "prose": "the organization defines information system components for which the operating environment and organization-defined applications are to be loaded and executed from hardware-enforced, read-only media;" - }, - { - "id": "sc-34_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-34[2]" - } - ], - "prose": "the organization defines applications to be loaded and executed from hardware-enforced, read-only media;" - }, - { - "id": "sc-34_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-34[3]" - } - ], - "prose": "the information system, at organization-defined information system components:", - "parts": [ - { - "id": "sc-34.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-34[3](a)" - } - ], - "prose": "loads and executes the operating environment from hardware-enforced, read-only media; and" - }, - { - "id": "sc-34.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-34[3](b)" - } - ], - "prose": "loads and executes organization-defined applications from hardware-enforced, read-only media." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing non-modifiable executable programs\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\nlist of operating system components to be loaded from hardware-enforced, read-only media\n\nlist of applications to be loaded from hardware-enforced, read-only media\n\nmedia used to load and execute information system operating environment\n\nmedia used to load and execute information system applications\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\ninformation system developers/integrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing loading and executing the operating environment from hardware-enforced, read-only media\n\nautomated mechanisms supporting and/or implementing loading and executing applications from hardware-enforced, read-only media" - } - ] - } - ], - "controls": [ - { - "id": "sc-34.1", - "class": "SP800-53-enhancement", - "title": "No Writable Storage", - "params": [ - { - "id": "sc-34.1_prm_1", - "label": "organization-defined information system components" - } - ], - "props": [ - { - "name": "label", - "value": "SC-34(1)" - }, - { - "name": "sort-id", - "value": "sc-34.01" - } - ], - "parts": [ - { - "id": "sc-34.1_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, sc-34.1_prm_1 }} with no writeable storage that is persistent across component restart or power on/off." - }, - { - "id": "sc-34.1_gdn", - "name": "guidance", - "prose": "This control enhancement: (i) eliminates the possibility of malicious code insertion via persistent, writeable storage within the designated information system components; and (ii) applies to both fixed and removable storage, with the latter being addressed directly or as specific restrictions imposed through access controls for mobile devices.", - "links": [ - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#mp-7", - "rel": "related" - } - ] - }, - { - "id": "sc-34.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-34.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-34(1)[1]" - } - ], - "prose": "defines information system components to be employed with no writeable storage; and" - }, - { - "id": "sc-34.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-34(1)[2]" - } - ], - "prose": "employs organization-defined information system components with no writeable storage that is persistent across component restart or power on/off." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing non-modifiable executable programs\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\nlist of information system components to be employed without writeable storage capability\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\ninformation system developers/integrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing employment of components with no writeable storage\n\nautomated mechanisms supporting and/or implementing persistent non-writeable storage across component restart and power on/off" - } - ] - } - ] - }, - { - "id": "sc-34.2", - "class": "SP800-53-enhancement", - "title": "Integrity Protection / Read-only Media", - "props": [ - { - "name": "label", - "value": "SC-34(2)" - }, - { - "name": "sort-id", - "value": "sc-34.02" - } - ], - "parts": [ - { - "id": "sc-34.2_smt", - "name": "statement", - "prose": "The organization protects the integrity of information prior to storage on read-only media and controls the media after such information has been recorded onto the media." - }, - { - "id": "sc-34.2_gdn", - "name": "guidance", - "prose": "Security safeguards prevent the substitution of media into information systems or the reprogramming of programmable read-only media prior to installation into the systems. Security safeguards include, for example, a combination of prevention, detection, and response.", - "links": [ - { - "href": "#ac-5", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-9", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - }, - { - "href": "#sa-12", - "rel": "related" - }, - { - "href": "#sc-28", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - } - ] - }, - { - "id": "sc-34.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-34.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-34(2)[1]" - } - ], - "prose": "protects the integrity of the information prior to storage on read-only media; and" - }, - { - "id": "sc-34.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-34(2)[2]" - } - ], - "prose": "controls the media after such information has been recorded onto the media." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing non-modifiable executable programs\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\ninformation system developers/integrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing capability for protecting information integrity on read-only media prior to storage and after information has been recorded onto the media" - } - ] - } - ] - }, - { - "id": "sc-34.3", - "class": "SP800-53-enhancement", - "title": "Hardware-based Protection", - "params": [ - { - "id": "sc-34.3_prm_1", - "label": "organization-defined information system firmware components" - }, - { - "id": "sc-34.3_prm_2", - "label": "organization-defined authorized individuals" - } - ], - "props": [ - { - "name": "label", - "value": "SC-34(3)" - }, - { - "name": "sort-id", - "value": "sc-34.03" - } - ], - "parts": [ - { - "id": "sc-34.3_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sc-34.3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Employs hardware-based, write-protect for {{ insert: param, sc-34.3_prm_1 }}; and" - }, - { - "id": "sc-34.3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Implements specific procedures for {{ insert: param, sc-34.3_prm_2 }} to manually disable hardware write-protect for firmware modifications and re-enable the write-protect prior to returning to operational mode." - } - ] - }, - { - "id": "sc-34.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-34.3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-34(3)(a)" - } - ], - "parts": [ - { - "id": "sc-34.3.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-34(3)(a)[1]" - } - ], - "prose": "defines information system firmware components for which hardware-based, write-protection is to be employed;" - }, - { - "id": "sc-34.3.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-34(3)(a)[2]" - } - ], - "prose": "employs hardware-based, write-protection for organization-defined information system firmware components;" - } - ], - "links": [ - { - "href": "#sc-34.3_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "sc-34.3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-34(3)(b)" - } - ], - "parts": [ - { - "id": "sc-34.3.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-34(3)(b)[1]" - } - ], - "prose": "defines individuals authorized to manually disable hardware write-protect for firmware modifications and re-enable the write-protect prior to returning to operational mode; and" - }, - { - "id": "sc-34.3.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-34(3)(b)[2]" - } - ], - "prose": "implements specific procedures for organization-defined authorized individuals to manually disable hardware write-protect for firmware modifications and re-enable the write-protect prior to returning to operational mode." - } - ], - "links": [ - { - "href": "#sc-34.3_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing firmware modifications\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\ninformation system developers/integrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for modifying firmware\n\nautomated mechanisms supporting and/or implementing hardware-based, write-protection for firmware" - } - ] - } - ] - } - ] - }, - { - "id": "sc-35", - "class": "SP800-53", - "title": "Honeyclients", - "props": [ - { - "name": "label", - "value": "SC-35" - }, - { - "name": "sort-id", - "value": "sc-35" - } - ], - "parts": [ - { - "id": "sc-35_smt", - "name": "statement", - "prose": "The information system includes components that proactively seek to identify malicious websites and/or web-based malicious code." - }, - { - "id": "sc-35_gdn", - "name": "guidance", - "prose": "Honeyclients differ from honeypots in that the components actively probe the Internet in search of malicious code (e.g., worms) contained on external websites. As with honeypots, honeyclients require some supporting isolation measures (e.g., virtualization) to ensure that any malicious code discovered during the search and subsequently executed does not infect organizational information systems.", - "links": [ - { - "href": "#sc-26", - "rel": "related" - }, - { - "href": "#sc-44", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "sc-35_obj", - "name": "objective", - "prose": "Determine if the information system includes components that proactively seek to identify malicious websites and/or web-based malicious code." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing honeyclients\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system components deployed to identify malicious websites and/or web-based malicious code\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\ninformation system developers/integrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing honeyclients" - } - ] - } - ] - }, - { - "id": "sc-36", - "class": "SP800-53", - "title": "Distributed Processing and Storage", - "params": [ - { - "id": "sc-36_prm_1", - "label": "organization-defined processing and storage" - } - ], - "props": [ - { - "name": "label", - "value": "SC-36" - }, - { - "name": "sort-id", - "value": "sc-36" - } - ], - "parts": [ - { - "id": "sc-36_smt", - "name": "statement", - "prose": "The organization distributes {{ insert: param, sc-36_prm_1 }} across multiple physical locations." - }, - { - "id": "sc-36_gdn", - "name": "guidance", - "prose": "Distributing processing and storage across multiple physical locations provides some degree of redundancy or overlap for organizations, and therefore increases the work factor of adversaries to adversely impact organizational operations, assets, and individuals. This control does not assume a single primary processing or storage location, and thus allows for parallel processing and storage.", - "links": [ - { - "href": "#cp-6", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - } - ] - }, - { - "id": "sc-36_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-36_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-36[1]" - } - ], - "prose": "defines processing and storage to be distributed across multiple physical locations; and" - }, - { - "id": "sc-36_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-36[2]" - } - ], - "prose": "distributes organization-defined processing and storage across multiple physical locations." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\ncontingency planning policy and procedures\n\ncontingency plan\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\nlist of information system physical locations (or environments) with distributed processing and storage\n\ninformation system facility diagrams\n\nprocessing site agreements\n\nstorage site agreements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with contingency planning and plan implementation responsibilities\n\ninformation system developers/integrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for distributing processing and storage across multiple physical locations\n\nautomated mechanisms supporting and/or implementing capability for distributing processing and storage across multiple physical locations" - } - ] - } - ], - "controls": [ - { - "id": "sc-36.1", - "class": "SP800-53-enhancement", - "title": "Polling Techniques", - "params": [ - { - "id": "sc-36.1_prm_1", - "label": "organization-defined distributed processing and storage components" - } - ], - "props": [ - { - "name": "label", - "value": "SC-36(1)" - }, - { - "name": "sort-id", - "value": "sc-36.01" - } - ], - "parts": [ - { - "id": "sc-36.1_smt", - "name": "statement", - "prose": "The organization employs polling techniques to identify potential faults, errors, or compromises to {{ insert: param, sc-36.1_prm_1 }}." - }, - { - "id": "sc-36.1_gdn", - "name": "guidance", - "prose": "Distributed processing and/or storage may be employed to reduce opportunities for adversaries to successfully compromise the confidentiality, integrity, or availability of information and information systems. However, distribution of processing and/or storage components does not prevent adversaries from compromising one (or more) of the distributed components. Polling compares the processing results and/or storage content from the various distributed components and subsequently voting on the outcomes. Polling identifies potential faults, errors, or compromises in distributed processing and/or storage components.", - "links": [ - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "sc-36.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-36.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-36(1)[1]" - } - ], - "prose": "defines distributed processing and storage components for which polling techniques are to be employed to identify potential faults, errors, or compromises; and" - }, - { - "id": "sc-36.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-36(1)[2]" - } - ], - "prose": "employs polling techniques to identify potential faults, errors, or compromises to organization-defined distributed processing and storage components." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\nlist of distributed processing and storage components subject to polling\n\ninformation system polling techniques and associated documentation or records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\ninformation system developers/integrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing polling techniques" - } - ] - } - ] - } - ] - }, - { - "id": "sc-37", - "class": "SP800-53", - "title": "Out-of-band Channels", - "params": [ - { - "id": "sc-37_prm_1", - "label": "organization-defined out-of-band channels" - }, - { - "id": "sc-37_prm_2", - "label": "organization-defined information, information system components, or devices" - }, - { - "id": "sc-37_prm_3", - "label": "organization-defined individuals or information systems" - } - ], - "props": [ - { - "name": "label", - "value": "SC-37" - }, - { - "name": "sort-id", - "value": "sc-37" - } - ], - "parts": [ - { - "id": "sc-37_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, sc-37_prm_1 }} for the physical delivery or electronic transmission of {{ insert: param, sc-37_prm_2 }} to {{ insert: param, sc-37_prm_3 }}." - }, - { - "id": "sc-37_gdn", - "name": "guidance", - "prose": "Out-of-band channels include, for example, local (nonnetwork) accesses to information systems, network paths physically separate from network paths used for operational traffic, or nonelectronic paths such as the US Postal Service. This is in contrast with using the same channels (i.e., in-band channels) that carry routine operational traffic. Out-of-band channels do not have the same vulnerability/exposure as in-band channels, and hence the confidentiality, integrity, or availability compromises of in-band channels will not compromise the out-of-band channels. Organizations may employ out-of-band channels in the delivery or transmission of many organizational items including, for example, identifiers/authenticators, configuration management changes for hardware, firmware, or software, cryptographic key management information, security updates, system/data backups, maintenance information, and malicious code protection updates.", - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "sc-37_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-37_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-37[1]" - } - ], - "prose": "defines out-of-band channels to be employed for the physical delivery or electronic transmission of information, information system components, or devices to individuals or information systems;" - }, - { - "id": "sc-37_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-37[2]" - } - ], - "prose": "defines information, information system components, or devices for which physical delivery or electronic transmission of such information, information system components, or devices to individuals or information systems requires employment of organization-defined out-of-band channels;" - }, - { - "id": "sc-37_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-37[3]" - } - ], - "prose": "defines individuals or information systems to which physical delivery or electronic transmission of organization-defined information, information system components, or devices is to be achieved via employment of organization-defined out-of-band channels; and" - }, - { - "id": "sc-37_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-37[4]" - } - ], - "prose": "employs organization-defined out-of-band channels for the physical delivery or electronic transmission of organization-defined information, information system components, or devices to organization-defined individuals or information systems." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing use of out-of-band channels\n\naccess control policy and procedures\n\nidentification and authentication policy and procedures\n\ninformation system design documentation\n\ninformation system architecture\n\ninformation system configuration settings and associated documentation\n\nlist of out-of-band channels\n\ntypes of information, information system components, or devices requiring use of out-of-band channels for physical delivery or electronic transmission to authorized individuals or information systems\n\nphysical delivery records\n\nelectronic transmission records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel authorizing, installing, configuring, operating, and/or using out-of-band channels\n\ninformation system developers/integrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for use of out-of-band channels\n\nautomated mechanisms supporting and/or implementing use of out-of-band channels" - } - ] - } - ], - "controls": [ - { - "id": "sc-37.1", - "class": "SP800-53-enhancement", - "title": "Ensure Delivery / Transmission", - "params": [ - { - "id": "sc-37.1_prm_1", - "label": "organization-defined security safeguards" - }, - { - "id": "sc-37.1_prm_2", - "label": "organization-defined individuals or information systems" - }, - { - "id": "sc-37.1_prm_3", - "label": "organization-defined information, information system components, or devices" - } - ], - "props": [ - { - "name": "label", - "value": "SC-37(1)" - }, - { - "name": "sort-id", - "value": "sc-37.01" - } - ], - "parts": [ - { - "id": "sc-37.1_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, sc-37.1_prm_1 }} to ensure that only {{ insert: param, sc-37.1_prm_2 }} receive the {{ insert: param, sc-37.1_prm_3 }}." - }, - { - "id": "sc-37.1_gdn", - "name": "guidance", - "prose": "Techniques and/or methods employed by organizations to ensure that only designated information systems or individuals receive particular information, system components, or devices include, for example, sending authenticators via courier service but requiring recipients to show some form of government-issued photographic identification as a condition of receipt." - }, - { - "id": "sc-37.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-37.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-37(1)[1]" - } - ], - "prose": "defines security safeguards to be employed to ensure that only designated individuals or information systems receive specific information, information system components, or devices;" - }, - { - "id": "sc-37.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-37(1)[2]" - } - ], - "prose": "defines individuals or information systems designated to receive specific information, information system components, or devices;" - }, - { - "id": "sc-37.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-37(1)[3]" - } - ], - "prose": "defines information, information system components, or devices that only organization-defined individuals or information systems are designated to receive; and" - }, - { - "id": "sc-37.1_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-37(1)[4]" - } - ], - "prose": "employs organization-defined security safeguards to ensure that only organization-defined individuals or information systems receive the organization-defined information, information system components, or devices." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing use of out-of-band channels\n\naccess control policy and procedures\n\nidentification and authentication policy and procedures\n\ninformation system design documentation\n\ninformation system architecture\n\ninformation system configuration settings and associated documentation\n\nlist of security safeguards to be employed to ensure designated individuals or information systems receive organization-defined information, information system components, or devices\n\nlist of security safeguards for delivering designated information, information system components, or devices to designated individuals or information systems\n\nlist of information, information system components, or devices to be delivered to designated individuals or information systems\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel authorizing, installing, configuring, operating, and/or using out-of-band channels\n\ninformation system developers/integrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for use of out-of-band channels\n\nautomated mechanisms supporting and/or implementing use of out-of-band channels\n\nautomated mechanisms supporting/implementing safeguards to ensure delivery of designated information, system components, or devices" - } - ] - } - ] - } - ] - }, - { - "id": "sc-38", - "class": "SP800-53", - "title": "Operations Security", - "params": [ - { - "id": "sc-38_prm_1", - "label": "organization-defined operations security safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "SC-38" - }, - { - "name": "sort-id", - "value": "sc-38" - } - ], - "parts": [ - { - "id": "sc-38_smt", - "name": "statement", - "prose": "The organization employs {{ insert: param, sc-38_prm_1 }} to protect key organizational information throughout the system development life cycle." - }, - { - "id": "sc-38_gdn", - "name": "guidance", - "prose": "Operations security (OPSEC) is a systematic process by which potential adversaries can be denied information about the capabilities and intentions of organizations by identifying, controlling, and protecting generally unclassified information that specifically relates to the planning and execution of sensitive organizational activities. The OPSEC process involves five steps: (i) identification of critical information (e.g., the security categorization process); (ii) analysis of threats; (iii) analysis of vulnerabilities; (iv) assessment of risks; and (v) the application of appropriate countermeasures. OPSEC safeguards are applied to both organizational information systems and the environments in which those systems operate. OPSEC safeguards help to protect the confidentiality of key information including, for example, limiting the sharing of information with suppliers and potential suppliers of information system components, information technology products and services, and with other non-organizational elements and individuals. Information critical to mission/business success includes, for example, user identities, element uses, suppliers, supply chain processes, functional and security requirements, system design specifications, testing protocols, and security control implementation details.", - "links": [ - { - "href": "#ra-2", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#sa-12", - "rel": "related" - } - ] - }, - { - "id": "sc-38_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-38_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-38[1]" - } - ], - "prose": "defines operations security safeguards to be employed to protect key organizational information throughout the system development life cycle; and" - }, - { - "id": "sc-38_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-38[2]" - } - ], - "prose": "employs organization-defined operations security safeguards to protect key organizational information throughout the system development life cycle." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing operations security\n\nsecurity plan\n\nlist of operations security safeguards\n\nsecurity control assessments\n\nrisk assessments\n\nthreat and vulnerability assessments\n\nplans of action and milestones\n\nsystem development life cycle documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\ninformation system developers/integrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for protecting organizational information throughout the SDLC\n\nautomated mechanisms supporting and/or implementing safeguards to protect organizational information throughout the SDLC" - } - ] - } - ] - }, - { - "id": "sc-39", - "class": "SP800-53", - "title": "Process Isolation", - "props": [ - { - "name": "label", - "value": "SC-39" - }, - { - "name": "sort-id", - "value": "sc-39" - } - ], - "parts": [ - { - "id": "sc-39_smt", - "name": "statement", - "prose": "The information system maintains a separate execution domain for each executing process." - }, - { - "id": "sc-39_gdn", - "name": "guidance", - "prose": "Information systems can maintain separate execution domains for each executing process by assigning each process a separate address space. Each information system process has a distinct address space so that communication between processes is performed in a manner controlled through the security functions, and one process cannot modify the executing code of another process. Maintaining separate execution domains for executing processes can be achieved, for example, by implementing separate address spaces. This capability is available in most commercial operating systems that employ multi-state processor technologies.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sc-2", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - } - ] - }, - { - "id": "sc-39_obj", - "name": "objective", - "prose": "Determine if the information system maintains a separate execution domain for each executing process." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system design documentation\n\ninformation system architecture\n\nindependent verification and validation documentation\n\ntesting and evaluation documentation, other relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system developers/integrators\n\ninformation system security architect" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing separate execution domains for each executing process" - } - ] - } - ], - "controls": [ - { - "id": "sc-39.1", - "class": "SP800-53-enhancement", - "title": "Hardware Separation", - "props": [ - { - "name": "label", - "value": "SC-39(1)" - }, - { - "name": "sort-id", - "value": "sc-39.01" - } - ], - "parts": [ - { - "id": "sc-39.1_smt", - "name": "statement", - "prose": "The information system implements underlying hardware separation mechanisms to facilitate process separation." - }, - { - "id": "sc-39.1_gdn", - "name": "guidance", - "prose": "Hardware-based separation of information system processes is generally less susceptible to compromise than software-based separation, thus providing greater assurance that the separation will be enforced. Underlying hardware separation mechanisms include, for example, hardware memory management." - }, - { - "id": "sc-39.1_obj", - "name": "objective", - "prose": "Determine if the information system implements underlying hardware separation mechanisms to facilitate process separation." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\ninformation system documentation for hardware separation mechanisms\n\ninformation system documentation from vendors, manufacturers or developers\n\nindependent verification and validation documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\ninformation system developers/integrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system capability implementing underlying hardware separation mechanisms for process separation" - } - ] - } - ] - }, - { - "id": "sc-39.2", - "class": "SP800-53-enhancement", - "title": "Thread Isolation", - "params": [ - { - "id": "sc-39.2_prm_1", - "label": "organization-defined multi-threaded processing" - } - ], - "props": [ - { - "name": "label", - "value": "SC-39(2)" - }, - { - "name": "sort-id", - "value": "sc-39.02" - } - ], - "parts": [ - { - "id": "sc-39.2_smt", - "name": "statement", - "prose": "The information system maintains a separate execution domain for each thread in {{ insert: param, sc-39.2_prm_1 }}." - }, - { - "id": "sc-39.2_obj", - "name": "objective", - "prose": "Determine if the information system:", - "parts": [ - { - "id": "sc-39.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-39(2)[1]" - } - ], - "prose": "defines multi-threaded processing for which a separate execution domain is to be maintained for each thread in multi-threaded processing; and" - }, - { - "id": "sc-39.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-39(2)[2]" - } - ], - "prose": "maintains a separate execution domain for each thread in organization-defined multi-threaded processing." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\nlist of information system execution domains for each thread in multi-threaded processing\n\ninformation system documentation for multi-threaded processing\n\ninformation system documentation from vendors, manufacturers or developers\n\nindependent verification and validation documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\ninformation system developers/integrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information system capability implementing a separate execution domain for each thread in multi-threaded processing" - } - ] - } - ] - } - ] - }, - { - "id": "sc-40", - "class": "SP800-53", - "title": "Wireless Link Protection", - "params": [ - { - "id": "sc-40_prm_1", - "label": "organization-defined wireless links" - }, - { - "id": "sc-40_prm_2", - "label": "organization-defined types of signal parameter attacks or references to sources for such attacks" - } - ], - "props": [ - { - "name": "label", - "value": "SC-40" - }, - { - "name": "sort-id", - "value": "sc-40" - } - ], - "parts": [ - { - "id": "sc-40_smt", - "name": "statement", - "prose": "The information system protects external and internal {{ insert: param, sc-40_prm_1 }} from {{ insert: param, sc-40_prm_2 }}." - }, - { - "id": "sc-40_gdn", - "name": "guidance", - "prose": "This control applies to internal and external wireless communication links that may be visible to individuals who are not authorized information system users. Adversaries can exploit the signal parameters of wireless links if such links are not adequately protected. There are many ways to exploit the signal parameters of wireless links to gain intelligence, deny service, or to spoof users of organizational information systems. This control reduces the impact of attacks that are unique to wireless systems. If organizations rely on commercial service providers for transmission services as commodity items rather than as fully dedicated services, it may not be possible to implement this control.", - "links": [ - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#sc-5", - "rel": "related" - } - ] - }, - { - "id": "sc-40_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-40_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-40[1]" - } - ], - "prose": "the organization defines:", - "parts": [ - { - "id": "sc-40_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-40[1][a]" - } - ], - "prose": "internal wireless links to be protected from particular types of signal parameter attacks;" - }, - { - "id": "sc-40_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-40[1][b]" - } - ], - "prose": "external wireless links to be protected from particular types of signal parameter attacks;" - } - ] - }, - { - "id": "sc-40_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-40[2]" - } - ], - "prose": "the organization defines types of signal parameter attacks or references to sources for such attacks that are based upon exploiting the signal parameters of organization-defined internal and external wireless links; and" - }, - { - "id": "sc-40_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-40[3]" - } - ], - "prose": "the information system protects internal and external organization-defined wireless links from organization-defined types of signal parameter attacks or references to sources for such attacks." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\naccess control policy and procedures\n\nprocedures addressing wireless link protection\n\ninformation system design documentation\n\nwireless network diagrams\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\nlist or internal and external wireless links\n\nlist of signal parameter attacks or references to sources for attacks\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel authorizing, installing, configuring and/or maintaining internal and external wireless links" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing protection of wireless links" - } - ] - } - ], - "controls": [ - { - "id": "sc-40.1", - "class": "SP800-53-enhancement", - "title": "Electromagnetic Interference", - "params": [ - { - "id": "sc-40.1_prm_1", - "label": "organization-defined level of protection" - } - ], - "props": [ - { - "name": "label", - "value": "SC-40(1)" - }, - { - "name": "sort-id", - "value": "sc-40.01" - } - ], - "parts": [ - { - "id": "sc-40.1_smt", - "name": "statement", - "prose": "The information system implements cryptographic mechanisms that achieve {{ insert: param, sc-40.1_prm_1 }} against the effects of intentional electromagnetic interference." - }, - { - "id": "sc-40.1_gdn", - "name": "guidance", - "prose": "This control enhancement protects against intentional jamming that might deny or impair communications by ensuring that wireless spread spectrum waveforms used to provide anti-jam protection are not predictable by unauthorized individuals. The control enhancement may also coincidentally help to mitigate the effects of unintentional jamming due to interference from legitimate transmitters sharing the same spectrum. Mission requirements, projected threats, concept of operations, and applicable legislation, directives, regulations, policies, standards, and guidelines determine levels of wireless link availability and performance/cryptography needed.", - "links": [ - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "sc-40.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-40.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-40(1)[1]" - } - ], - "prose": "the organization defines level of protection to be employed against the effects of intentional electromagnetic interference; and" - }, - { - "id": "sc-40.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-40(1)[2]" - } - ], - "prose": "the information system employs cryptographic mechanisms that achieve organization-defined level of protection against the effects of intentional electromagnetic interference." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\naccess control policy and procedures\n\nprocedures addressing wireless link protection\n\ninformation system design documentation\n\nwireless network diagrams\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\ninformation system communications hardware and software\n\nsecurity categorization results\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel authorizing, installing, configuring and/or maintaining internal and external wireless links" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Cryptographic mechanisms enforcing protections against effects of intentional electromagnetic interference" - } - ] - } - ] - }, - { - "id": "sc-40.2", - "class": "SP800-53-enhancement", - "title": "Reduce Detection Potential", - "params": [ - { - "id": "sc-40.2_prm_1", - "label": "organization-defined level of reduction" - } - ], - "props": [ - { - "name": "label", - "value": "SC-40(2)" - }, - { - "name": "sort-id", - "value": "sc-40.02" - } - ], - "parts": [ - { - "id": "sc-40.2_smt", - "name": "statement", - "prose": "The information system implements cryptographic mechanisms to reduce the detection potential of wireless links to {{ insert: param, sc-40.2_prm_1 }}." - }, - { - "id": "sc-40.2_gdn", - "name": "guidance", - "prose": "This control enhancement is needed for covert communications and protecting wireless transmitters from being geo-located by their transmissions. The control enhancement ensures that spread spectrum waveforms used to achieve low probability of detection are not predictable by unauthorized individuals. Mission requirements, projected threats, concept of operations, and applicable legislation, directives, regulations, policies, standards, and guidelines determine the levels to which wireless links should be undetectable.", - "links": [ - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "sc-40.2_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-40.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-40(2)[1]" - } - ], - "prose": "the organization defines level of reduction to be achieved to reduce the detection potential of wireless links; and" - }, - { - "id": "sc-40.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-40(2)[2]" - } - ], - "prose": "the information system implements cryptographic mechanisms to reduce the detection potential of wireless links to organization-defined level of reduction." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\naccess control policy and procedures\n\nprocedures addressing wireless link protection\n\ninformation system design documentation\n\nwireless network diagrams\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\ninformation system communications hardware and software\n\nsecurity categorization results\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel authorizing, installing, configuring and/or maintaining internal and external wireless links" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Cryptographic mechanisms enforcing protections to reduce detection of wireless links" - } - ] - } - ] - }, - { - "id": "sc-40.3", - "class": "SP800-53-enhancement", - "title": "Imitative or Manipulative Communications Deception", - "props": [ - { - "name": "label", - "value": "SC-40(3)" - }, - { - "name": "sort-id", - "value": "sc-40.03" - } - ], - "parts": [ - { - "id": "sc-40.3_smt", - "name": "statement", - "prose": "The information system implements cryptographic mechanisms to identify and reject wireless transmissions that are deliberate attempts to achieve imitative or manipulative communications deception based on signal parameters." - }, - { - "id": "sc-40.3_gdn", - "name": "guidance", - "prose": "This control enhancement ensures that the signal parameters of wireless transmissions are not predictable by unauthorized individuals. Such unpredictability reduces the probability of imitative or manipulative communications deception based upon signal parameters alone.", - "links": [ - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "sc-40.3_obj", - "name": "objective", - "prose": "Determine if the information system implements cryptographic mechanisms to:", - "parts": [ - { - "id": "sc-40.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-40(3)[1]" - } - ], - "prose": "identify wireless transmissions that are deliberate attempts to achieve imitative or manipulative communications deception based on signal parameters; and" - }, - { - "id": "sc-40.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-40(3)[2]" - } - ], - "prose": "reject wireless transmissions that are deliberate attempts to achieve imitative or manipulative communications deception based on signal parameters." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\naccess control policy and procedures\n\nprocedures addressing information system design documentation\n\nwireless network diagrams\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\ninformation system communications hardware and software\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel authorizing, installing, configuring and/or maintaining internal and external wireless links" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Cryptographic mechanisms enforcing wireless link protections against imitative or manipulative communications deception" - } - ] - } - ] - }, - { - "id": "sc-40.4", - "class": "SP800-53-enhancement", - "title": "Signal Parameter Identification", - "params": [ - { - "id": "sc-40.4_prm_1", - "label": "organization-defined wireless transmitters" - } - ], - "props": [ - { - "name": "label", - "value": "SC-40(4)" - }, - { - "name": "sort-id", - "value": "sc-40.04" - } - ], - "parts": [ - { - "id": "sc-40.4_smt", - "name": "statement", - "prose": "The information system implements cryptographic mechanisms to prevent the identification of {{ insert: param, sc-40.4_prm_1 }} by using the transmitter signal parameters." - }, - { - "id": "sc-40.4_gdn", - "name": "guidance", - "prose": "Radio fingerprinting techniques identify the unique signal parameters of transmitters to fingerprint such transmitters for purposes of tracking and mission/user identification. This control enhancement protects against the unique identification of wireless transmitters for purposes of intelligence exploitation by ensuring that anti-fingerprinting alterations to signal parameters are not predictable by unauthorized individuals. This control enhancement helps assure mission success when anonymity is required.", - "links": [ - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "sc-40.4_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-40.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-40(4)[1]" - } - ], - "prose": "the organization defines wireless transmitters for which cryptographic mechanisms are to be implemented to prevent identification of such transmitters by using the transmitter signal parameters; and" - }, - { - "id": "sc-40.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-40(4)[2]" - } - ], - "prose": "the information system implements cryptographic mechanisms to prevent the identification of organization-defined wireless transmitters by using the transmitter signal parameters." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\naccess control policy and procedures\n\nprocedures addressing information system design documentation\n\nwireless network diagrams\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\ninformation system communications hardware and software\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel authorizing, installing, configuring and/or maintaining internal and external wireless links" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Cryptographic mechanisms preventing the identification of wireless transmitters" - } - ] - } - ] - } - ] - }, - { - "id": "sc-41", - "class": "SP800-53", - "title": "Port and I/O Device Access", - "params": [ - { - "id": "sc-41_prm_1", - "label": "organization-defined connection ports or input/output devices" - }, - { - "id": "sc-41_prm_2", - "label": "organization-defined information systems or information system components" - } - ], - "props": [ - { - "name": "label", - "value": "SC-41" - }, - { - "name": "sort-id", - "value": "sc-41" - } - ], - "parts": [ - { - "id": "sc-41_smt", - "name": "statement", - "prose": "The organization physically disables or removes {{ insert: param, sc-41_prm_1 }} on {{ insert: param, sc-41_prm_2 }}." - }, - { - "id": "sc-41_gdn", - "name": "guidance", - "prose": "Connection ports include, for example, Universal Serial Bus (USB) and Firewire (IEEE 1394). Input/output (I/O) devices include, for example, Compact Disk (CD) and Digital Video Disk (DVD) drives. Physically disabling or removing such connection ports and I/O devices helps prevent exfiltration of information from information systems and the introduction of malicious code into systems from those ports/devices." - }, - { - "id": "sc-41_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-41_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-41[1]" - } - ], - "prose": "defines connection ports or input/output devices to be physically disabled or removed on information systems or information system components;" - }, - { - "id": "sc-41_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-41[2]" - } - ], - "prose": "defines information systems or information system components with organization-defined connection ports or input/output devices that are to be physically disabled or removed; and" - }, - { - "id": "sc-41_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-41[3]" - } - ], - "prose": "physically disables or removes organization-defined connection ports or input/output devices on organization-defined information systems or information system components." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\naccess control policy and procedures\n\nprocedures addressing port and input/output device access\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\ninformation systems or information system components list of connection ports or input/output devices to be physically disabled or removed on information systems or information system components\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing disabling of connection ports or input/output devices" - } - ] - } - ] - }, - { - "id": "sc-42", - "class": "SP800-53", - "title": "Sensor Capability and Data", - "params": [ - { - "id": "sc-42_prm_1", - "label": "organization-defined exceptions where remote activation of sensors is allowed" - }, - { - "id": "sc-42_prm_2", - "label": "organization-defined class of users" - } - ], - "props": [ - { - "name": "label", - "value": "SC-42" - }, - { - "name": "sort-id", - "value": "sc-42" - } - ], - "parts": [ - { - "id": "sc-42_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "sc-42_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Prohibits the remote activation of environmental sensing capabilities with the following exceptions: {{ insert: param, sc-42_prm_1 }}; and" - }, - { - "id": "sc-42_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Provides an explicit indication of sensor use to {{ insert: param, sc-42_prm_2 }}." - } - ] - }, - { - "id": "sc-42_gdn", - "name": "guidance", - "prose": "This control often applies to types of information systems or system components characterized as mobile devices, for example, smart phones, tablets, and E-readers. These systems often include sensors that can collect and record data regarding the environment where the system is in use. Sensors that are embedded within mobile devices include, for example, cameras, microphones, Global Positioning System (GPS) mechanisms, and accelerometers. While the sensors on mobiles devices provide an important function, if activated covertly, such devices can potentially provide a means for adversaries to learn valuable information about individuals and organizations. For example, remotely activating the GPS function on a mobile device could provide an adversary with the ability to track the specific movements of an individual." - }, - { - "id": "sc-42_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "sc-42.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-42(a)" - } - ], - "parts": [ - { - "id": "sc-42.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-42(a)[1]" - } - ], - "prose": "the organization defines exceptions where remote activation of sensors is to be allowed;" - }, - { - "id": "sc-42.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-42(a)[2]" - } - ], - "prose": "the information system prohibits the remote activation of sensors, except for organization-defined exceptions where remote activation of sensors is to be allowed;" - } - ] - }, - { - "id": "sc-42.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-42(b)" - } - ], - "parts": [ - { - "id": "sc-42.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-42(b)[1]" - } - ], - "prose": "the organization defines the class of users to whom an explicit indication of sensor use is to be provided; and" - }, - { - "id": "sc-42.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-42(b)[2]" - } - ], - "prose": "the information system provides an explicit indication of sensor use to the organization-defined class of users." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing sensor capability and data collection\n\naccess control policy and procedures\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for sensor capability" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing access controls for remote activation of information system sensor capabilities\n\nautomated mechanisms implementing capability to indicate sensor use" - } - ] - } - ], - "controls": [ - { - "id": "sc-42.1", - "class": "SP800-53-enhancement", - "title": "Reporting to Authorized Individuals or Roles", - "params": [ - { - "id": "sc-42.1_prm_1", - "label": "organization-defined sensors" - } - ], - "props": [ - { - "name": "label", - "value": "SC-42(1)" - }, - { - "name": "sort-id", - "value": "sc-42.01" - } - ], - "parts": [ - { - "id": "sc-42.1_smt", - "name": "statement", - "prose": "The organization ensures that the information system is configured so that data or information collected by the {{ insert: param, sc-42.1_prm_1 }} is only reported to authorized individuals or roles." - }, - { - "id": "sc-42.1_gdn", - "name": "guidance", - "prose": "In situations where sensors are activated by authorized individuals (e.g., end users), it is still possible that the data/information collected by the sensors will be sent to unauthorized entities." - }, - { - "id": "sc-42.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-42.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-42(1)[1]" - } - ], - "prose": "defines sensors to be used to collect data or information only reported to authorized individuals or roles; and" - }, - { - "id": "sc-42.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-42(1)[2]" - } - ], - "prose": "ensures that the information system is configured so that data or information collected by the organization-defined sensors is only reported to authorized individuals or roles." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\naccess control policy and procedures\n\nprocedures addressing sensor capability and data collection\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for sensor capability" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms restricting reporting of sensor information only to those authorized\n\nsensor data collection and reporting capability for the information system" - } - ] - } - ] - }, - { - "id": "sc-42.2", - "class": "SP800-53-enhancement", - "title": "Authorized Use", - "params": [ - { - "id": "sc-42.2_prm_1", - "label": "organization-defined measures" - }, - { - "id": "sc-42.2_prm_2", - "label": "organization-defined sensors" - } - ], - "props": [ - { - "name": "label", - "value": "SC-42(2)" - }, - { - "name": "sort-id", - "value": "sc-42.02" - } - ], - "parts": [ - { - "id": "sc-42.2_smt", - "name": "statement", - "prose": "The organization employs the following measures: {{ insert: param, sc-42.2_prm_1 }}, so that data or information collected by {{ insert: param, sc-42.2_prm_2 }} is only used for authorized purposes." - }, - { - "id": "sc-42.2_gdn", - "name": "guidance", - "prose": "Information collected by sensors for a specific authorized purpose potentially could be misused for some unauthorized purpose. For example, GPS sensors that are used to support traffic navigation could be misused to track movements of individuals. Measures to mitigate such activities include, for example, additional training to ensure that authorized parties do not abuse their authority, or (in the case where sensor data/information is maintained by external parties) contractual restrictions on the use of the data/information." - }, - { - "id": "sc-42.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-42.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-42(2)[1]" - } - ], - "prose": "defines measures to be employed so that data or information collected by sensors is only used for authorized purposes;" - }, - { - "id": "sc-42.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-42(2)[2]" - } - ], - "prose": "defines sensors to be used to collect data or information for authorized purposes only; and" - }, - { - "id": "sc-42.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-42(2)[3]" - } - ], - "prose": "employs organization-defined measures so that data or information collected by organization-defined sensors is only used for authorized purposes." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\naccess control policy and procedures\n\nsensor capability and data collection\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\nlist of measures to be employed to ensure data or information collected by sensors is only used for authorized purposes\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for sensor capability" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing measures to ensure sensor information is only used for authorized purposes\n\nsensor information collection capability for the information system" - } - ] - } - ] - }, - { - "id": "sc-42.3", - "class": "SP800-53-enhancement", - "title": "Prohibit Use of Devices", - "params": [ - { - "id": "sc-42.3_prm_1", - "label": "organization-defined environmental sensing capabilities" - }, - { - "id": "sc-42.3_prm_2", - "label": "organization-defined facilities, areas, or systems" - } - ], - "props": [ - { - "name": "label", - "value": "SC-42(3)" - }, - { - "name": "sort-id", - "value": "sc-42.03" - } - ], - "parts": [ - { - "id": "sc-42.3_smt", - "name": "statement", - "prose": "The organization prohibits the use of devices possessing {{ insert: param, sc-42.3_prm_1 }} in {{ insert: param, sc-42.3_prm_2 }}." - }, - { - "id": "sc-42.3_gdn", - "name": "guidance", - "prose": "For example, organizations may prohibit individuals from bringing cell phones or digital cameras into certain facilities or specific controlled areas within facilities where classified information is stored or sensitive conversations are taking place." - }, - { - "id": "sc-42.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-42.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-42(3)[1]" - } - ], - "prose": "defines environmental sensing capabilities to be prohibited from use in facilities, areas, or systems;" - }, - { - "id": "sc-42.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-42(3)[2]" - } - ], - "prose": "defines facilities, areas, or systems where the use of devices possessing organization-defined environmental sensing capabilities is to be prohibited; and" - }, - { - "id": "sc-42.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-42(3)[3]" - } - ], - "prose": "prohibits the use of devices possessing organization-defined environmental sensing capabilities in organization-defined facilities, areas, or systems." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\naccess control policy and procedures\n\nprocedures addressing sensor capability and data collection\n\ninformation system design documentation\n\nwireless network diagrams\n\ninformation system configuration settings and associated documentation\n\ninformation system architecture\n\nfacilities, areas, or systems where use of devices possessing environmental sensing capabilities is prohibited\n\nlist of devices possessing environmental sensing capabilities\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for sensor capability" - } - ] - } - ] - } - ] - }, - { - "id": "sc-43", - "class": "SP800-53", - "title": "Usage Restrictions", - "params": [ - { - "id": "sc-43_prm_1", - "label": "organization-defined information system components" - } - ], - "props": [ - { - "name": "label", - "value": "SC-43" - }, - { - "name": "sort-id", - "value": "sc-43" - } - ], - "parts": [ - { - "id": "sc-43_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "sc-43_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Establishes usage restrictions and implementation guidance for {{ insert: param, sc-43_prm_1 }} based on the potential to cause damage to the information system if used maliciously; and" - }, - { - "id": "sc-43_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Authorizes, monitors, and controls the use of such components within the information system." - } - ] - }, - { - "id": "sc-43_gdn", - "name": "guidance", - "prose": "Information system components include hardware, software, or firmware components (e.g., Voice Over Internet Protocol, mobile code, digital copiers, printers, scanners, optical devices, wireless technologies, mobile devices).", - "links": [ - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - } - ] - }, - { - "id": "sc-43_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-43.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-43(a)" - } - ], - "parts": [ - { - "id": "sc-43.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-43(a)[1]" - } - ], - "prose": "defines information system components for which usage restrictions and implementation guidance are to be established;" - }, - { - "id": "sc-43.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-43(a)[2]" - } - ], - "prose": "establishes, for organization-defined information system components:", - "parts": [ - { - "id": "sc-43.a_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-43(a)[2][a]" - } - ], - "prose": "usage restrictions based on the potential to cause damage to the information system if used maliciously;" - }, - { - "id": "sc-43.a_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-43(a)[2][b]" - } - ], - "prose": "implementation guidance based on the potential to cause damage to the information system if used maliciously;" - } - ] - } - ] - }, - { - "id": "sc-43.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-43(b)" - } - ], - "parts": [ - { - "id": "sc-43.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-43(b)[1]" - } - ], - "prose": "authorizes the use of such components within the information system;" - }, - { - "id": "sc-43.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-43(b)[2]" - } - ], - "prose": "monitors the use of such components within the information system; and" - }, - { - "id": "sc-43.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-43(b)[3]" - } - ], - "prose": "controls the use of such components within the information system." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing usage restrictions\n\nusage restrictions\n\nimplementation policy and procedures\n\nauthorization records\n\ninformation system monitoring records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for authorizing, monitoring, and controlling use of components with usage restrictions\n\nAutomated mechanisms supporting and/or implementing authorizing, monitoring, and controlling use of components with usage restrictions" - } - ] - } - ] - }, - { - "id": "sc-44", - "class": "SP800-53", - "title": "Detonation Chambers", - "params": [ - { - "id": "sc-44_prm_1", - "label": "organization-defined information system, system component, or location" - } - ], - "props": [ - { - "name": "label", - "value": "SC-44" - }, - { - "name": "sort-id", - "value": "sc-44" - } - ], - "parts": [ - { - "id": "sc-44_smt", - "name": "statement", - "prose": "The organization employs a detonation chamber capability within {{ insert: param, sc-44_prm_1 }}." - }, - { - "id": "sc-44_gdn", - "name": "guidance", - "prose": "Detonation chambers, also known as dynamic execution environments, allow organizations to open email attachments, execute untrusted or suspicious applications, and execute Universal Resource Locator (URL) requests in the safety of an isolated environment or virtualized sandbox. These protected and isolated execution environments provide a means of determining whether the associated attachments/applications contain malicious code. While related to the concept of deception nets, the control is not intended to maintain a long-term environment in which adversaries can operate and their actions can be observed. Rather, it is intended to quickly identify malicious code and reduce the likelihood that the code is propagated to user environments of operation (or prevent such propagation completely).", - "links": [ - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-25", - "rel": "related" - }, - { - "href": "#sc-26", - "rel": "related" - }, - { - "href": "#sc-30", - "rel": "related" - } - ] - }, - { - "id": "sc-44_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "sc-44_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-44[1]" - } - ], - "prose": "defines information system, system component, or location where a detonation chamber capability is to be employed; and" - }, - { - "id": "sc-44_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SC-44[2]" - } - ], - "prose": "employs a detonation chamber capability within organization-defined information system, system component, or location." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and communications protection policy\n\nprocedures addressing detonation chambers\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing detonation chamber capability" - } - ] - } - ] - } - ] - }, - { - "id": "si", - "class": "family", - "title": "System and Information Integrity", - "controls": [ - { - "id": "si-1", - "class": "SP800-53", - "title": "System and Information Integrity Policy and Procedures", - "params": [ - { - "id": "si-1_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "si-1_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "si-1_prm_3", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "SI-1" - }, - { - "name": "sort-id", - "value": "si-01" - } - ], - "links": [ - { - "href": "#5c201b63-0768-417b-ac22-3f014e3941b2", - "rel": "reference" - }, - { - "href": "#9cb3d8fe-2127-48ba-821e-cdd2d7aee921", - "rel": "reference" - } - ], - "parts": [ - { - "id": "si-1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "si-1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops, documents, and disseminates to {{ insert: param, si-1_prm_1 }}:", - "parts": [ - { - "id": "si-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "A system and information integrity policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "si-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the system and information integrity policy and associated system and information integrity controls; and" - } - ] - }, - { - "id": "si-1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews and updates the current:", - "parts": [ - { - "id": "si-1_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "System and information integrity policy {{ insert: param, si-1_prm_2 }}; and" - }, - { - "id": "si-1_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "System and information integrity procedures {{ insert: param, si-1_prm_3 }}." - } - ] - } - ] - }, - { - "id": "si-1_gdn", - "name": "guidance", - "prose": "This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the SI family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures.", - "links": [ - { - "href": "#pm-9", - "rel": "related" - } - ] - }, - { - "id": "si-1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(a)" - } - ], - "parts": [ - { - "id": "si-1.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(a)(1)" - } - ], - "parts": [ - { - "id": "si-1.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(a)(1)[1]" - } - ], - "prose": "develops and documents a system and information integrity policy that addresses:", - "parts": [ - { - "id": "si-1.a.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(a)(1)[1][a]" - } - ], - "prose": "purpose;" - }, - { - "id": "si-1.a.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(a)(1)[1][b]" - } - ], - "prose": "scope;" - }, - { - "id": "si-1.a.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(a)(1)[1][c]" - } - ], - "prose": "roles;" - }, - { - "id": "si-1.a.1_obj.1.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(a)(1)[1][d]" - } - ], - "prose": "responsibilities;" - }, - { - "id": "si-1.a.1_obj.1.e", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(a)(1)[1][e]" - } - ], - "prose": "management commitment;" - }, - { - "id": "si-1.a.1_obj.1.f", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(a)(1)[1][f]" - } - ], - "prose": "coordination among organizational entities;" - }, - { - "id": "si-1.a.1_obj.1.g", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(a)(1)[1][g]" - } - ], - "prose": "compliance;" - } - ] - }, - { - "id": "si-1.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(a)(1)[2]" - } - ], - "prose": "defines personnel or roles to whom the system and information integrity policy is to be disseminated;" - }, - { - "id": "si-1.a.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(a)(1)[3]" - } - ], - "prose": "disseminates the system and information integrity policy to organization-defined personnel or roles;" - } - ] - }, - { - "id": "si-1.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(a)(2)" - } - ], - "parts": [ - { - "id": "si-1.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(a)(2)[1]" - } - ], - "prose": "develops and documents procedures to facilitate the implementation of the system and information integrity policy and associated system and information integrity controls;" - }, - { - "id": "si-1.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(a)(2)[2]" - } - ], - "prose": "defines personnel or roles to whom the procedures are to be disseminated;" - }, - { - "id": "si-1.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(a)(2)[3]" - } - ], - "prose": "disseminates the procedures to organization-defined personnel or roles;" - } - ] - } - ] - }, - { - "id": "si-1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(b)" - } - ], - "parts": [ - { - "id": "si-1.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(b)(1)" - } - ], - "parts": [ - { - "id": "si-1.b.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(b)(1)[1]" - } - ], - "prose": "defines the frequency to review and update the current system and information integrity policy;" - }, - { - "id": "si-1.b.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(b)(1)[2]" - } - ], - "prose": "reviews and updates the current system and information integrity policy with the organization-defined frequency;" - } - ] - }, - { - "id": "si-1.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(b)(2)" - } - ], - "parts": [ - { - "id": "si-1.b.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(b)(2)[1]" - } - ], - "prose": "defines the frequency to review and update the current system and information integrity procedures; and" - }, - { - "id": "si-1.b.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-1(b)(2)[2]" - } - ], - "prose": "reviews and updates the current system and information integrity procedures with the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy and procedures\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with system and information integrity responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "si-2", - "class": "SP800-53", - "title": "Flaw Remediation", - "params": [ - { - "id": "si-2_prm_1", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "SI-2" - }, - { - "name": "sort-id", - "value": "si-02" - } - ], - "links": [ - { - "href": "#bdd14f6c-41ab-4277-8d74-a0ce75a0eb1d", - "rel": "reference" - }, - { - "href": "#080f8068-5e3e-435e-9790-d22ba4722693", - "rel": "reference" - } - ], - "parts": [ - { - "id": "si-2_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "si-2_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Identifies, reports, and corrects information system flaws;" - }, - { - "id": "si-2_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Tests software and firmware updates related to flaw remediation for effectiveness and potential side effects before installation;" - }, - { - "id": "si-2_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Installs security-relevant software and firmware updates within {{ insert: param, si-2_prm_1 }} of the release of the updates; and" - }, - { - "id": "si-2_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Incorporates flaw remediation into the organizational configuration management process." - } - ] - }, - { - "id": "si-2_gdn", - "name": "guidance", - "prose": "Organizations identify information systems affected by announced software flaws including potential vulnerabilities resulting from those flaws, and report this information to designated organizational personnel with information security responsibilities. Security-relevant software updates include, for example, patches, service packs, hot fixes, and anti-virus signatures. Organizations also address flaws discovered during security assessments, continuous monitoring, incident response activities, and system error handling. Organizations take advantage of available resources such as the Common Weakness Enumeration (CWE) or Common Vulnerabilities and Exposures (CVE) databases in remediating flaws discovered in organizational information systems. By incorporating flaw remediation into ongoing configuration management processes, required/anticipated remediation actions can be tracked and verified. Flaw remediation actions that can be tracked and verified include, for example, determining whether organizations follow US-CERT guidance and Information Assurance Vulnerability Alerts. Organization-defined time periods for updating security-relevant software and firmware may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). Some types of flaw remediation may require more testing than other types. Organizations determine the degree and type of testing needed for the specific type of flaw remediation activity under consideration and also the types of changes that are to be configuration-managed. In some situations, organizations may determine that the testing of software and/or firmware updates is not necessary or practical, for example, when implementing simple anti-virus signature updates. Organizations may also consider in testing decisions, whether security-relevant software or firmware updates are obtained from authorized sources with appropriate digital signatures.", - "links": [ - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#ma-2", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - }, - { - "href": "#sa-11", - "rel": "related" - }, - { - "href": "#si-11", - "rel": "related" - } - ] - }, - { - "id": "si-2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-2.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(a)" - } - ], - "parts": [ - { - "id": "si-2.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(a)[1]" - } - ], - "prose": "identifies information system flaws;" - }, - { - "id": "si-2.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(a)[2]" - } - ], - "prose": "reports information system flaws;" - }, - { - "id": "si-2.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(a)[3]" - } - ], - "prose": "corrects information system flaws;" - } - ] - }, - { - "id": "si-2.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(b)" - } - ], - "parts": [ - { - "id": "si-2.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(b)[1]" - } - ], - "prose": "tests software updates related to flaw remediation for effectiveness and potential side effects before installation;" - }, - { - "id": "si-2.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(b)[2]" - } - ], - "prose": "tests firmware updates related to flaw remediation for effectiveness and potential side effects before installation;" - } - ] - }, - { - "id": "si-2.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(c)" - } - ], - "parts": [ - { - "id": "si-2.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(c)[1]" - } - ], - "prose": "defines the time period within which to install security-relevant software updates after the release of the updates;" - }, - { - "id": "si-2.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(c)[2]" - } - ], - "prose": "defines the time period within which to install security-relevant firmware updates after the release of the updates;" - }, - { - "id": "si-2.c_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(c)[3]" - } - ], - "prose": "installs software updates within the organization-defined time period of the release of the updates;" - }, - { - "id": "si-2.c_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(c)[4]" - } - ], - "prose": "installs firmware updates within the organization-defined time period of the release of the updates; and" - } - ] - }, - { - "id": "si-2.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(d)" - } - ], - "prose": "incorporates flaw remediation into the organizational configuration management process." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing flaw remediation\n\nprocedures addressing configuration management\n\nlist of flaws and vulnerabilities potentially affecting the information system\n\nlist of recent security flaw remediation actions performed on the information system (e.g., list of installed patches, service packs, hot fixes, and other software updates to correct information system flaws)\n\ntest results from the installation of software and firmware updates to correct information system flaws\n\ninstallation/change control records for security-relevant software and firmware updates\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for flaw remediation\n\norganizational personnel with configuration management responsibility" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for identifying, reporting, and correcting information system flaws\n\norganizational process for installing software and firmware updates\n\nautomated mechanisms supporting and/or implementing reporting, and correcting information system flaws\n\nautomated mechanisms supporting and/or implementing testing software and firmware updates" - } - ] - } - ], - "controls": [ - { - "id": "si-2.1", - "class": "SP800-53-enhancement", - "title": "Central Management", - "props": [ - { - "name": "label", - "value": "SI-2(1)" - }, - { - "name": "sort-id", - "value": "si-02.01" - } - ], - "parts": [ - { - "id": "si-2.1_smt", - "name": "statement", - "prose": "The organization centrally manages the flaw remediation process." - }, - { - "id": "si-2.1_gdn", - "name": "guidance", - "prose": "Central management is the organization-wide management and implementation of flaw remediation processes. Central management includes planning, implementing, assessing, authorizing, and monitoring the organization-defined, centrally managed flaw remediation security controls." - }, - { - "id": "si-2.1_obj", - "name": "objective", - "prose": "Determine if the organization centrally manages the flaw remediation process." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing flaw remediation\n\nautomated mechanisms supporting centralized management of flaw remediation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for flaw remediation" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for central management of the flaw remediation process\n\nautomated mechanisms supporting and/or implementing central management of the flaw remediation process" - } - ] - } - ] - }, - { - "id": "si-2.2", - "class": "SP800-53-enhancement", - "title": "Automated Flaw Remediation Status", - "params": [ - { - "id": "si-2.2_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "SI-2(2)" - }, - { - "name": "sort-id", - "value": "si-02.02" - } - ], - "parts": [ - { - "id": "si-2.2_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms {{ insert: param, si-2.2_prm_1 }} to determine the state of information system components with regard to flaw remediation." - }, - { - "id": "si-2.2_gdn", - "name": "guidance", - "links": [ - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "si-2.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-2.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(2)[1]" - } - ], - "prose": "defines a frequency to employ automated mechanisms to determine the state of information system components with regard to flaw remediation; and" - }, - { - "id": "si-2.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(2)[2]" - } - ], - "prose": "employs automated mechanisms with the organization-defined frequency to determine the state of information system components with regard to flaw remediation." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing flaw remediation\n\nautomated mechanisms supporting centralized management of flaw remediation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for flaw remediation" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms used to determine the state of information system components with regard to flaw remediation" - } - ] - } - ] - }, - { - "id": "si-2.3", - "class": "SP800-53-enhancement", - "title": "Time to Remediate Flaws / Benchmarks for Corrective Actions", - "params": [ - { - "id": "si-2.3_prm_1", - "label": "organization-defined benchmarks" - } - ], - "props": [ - { - "name": "label", - "value": "SI-2(3)" - }, - { - "name": "sort-id", - "value": "si-02.03" - } - ], - "parts": [ - { - "id": "si-2.3_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "si-2.3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Measures the time between flaw identification and flaw remediation; and" - }, - { - "id": "si-2.3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Establishes {{ insert: param, si-2.3_prm_1 }} for taking corrective actions." - } - ] - }, - { - "id": "si-2.3_gdn", - "name": "guidance", - "prose": "This control enhancement requires organizations to determine the current time it takes on the average to correct information system flaws after such flaws have been identified, and subsequently establish organizational benchmarks (i.e., time frames) for taking corrective actions. Benchmarks can be established by type of flaw and/or severity of the potential vulnerability if the flaw can be exploited." - }, - { - "id": "si-2.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-2.3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(3)(a)" - } - ], - "prose": "measures the time between flaw identification and flaw remediation;", - "links": [ - { - "href": "#si-2.3_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "si-2.3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(3)(b)" - } - ], - "parts": [ - { - "id": "si-2.3.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(3)(b)[1]" - } - ], - "prose": "defines benchmarks for taking corrective actions; and" - }, - { - "id": "si-2.3.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(3)(b)[2]" - } - ], - "prose": "establishes organization-defined benchmarks for taking corrective actions." - } - ], - "links": [ - { - "href": "#si-2.3_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing flaw remediation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of benchmarks for taking corrective action on flaws identified\n\nrecords providing time stamps of flaw identification and subsequent flaw remediation activities\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for flaw remediation" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for identifying, reporting, and correcting information system flaws\n\nautomated mechanisms used to measure the time between flaw identification and flaw remediation" - } - ] - } - ] - }, - { - "id": "si-2.4", - "class": "SP800-53-enhancement", - "title": "Automated Patch Management Tools", - "props": [ - { - "name": "label", - "value": "SI-2(4)" - }, - { - "name": "sort-id", - "value": "si-02.04" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#si-2", - "rel": "incorporated-into" - } - ] - }, - { - "id": "si-2.5", - "class": "SP800-53-enhancement", - "title": "Automatic Software / Firmware Updates", - "params": [ - { - "id": "si-2.5_prm_1", - "label": "organization-defined security-relevant software and firmware updates" - }, - { - "id": "si-2.5_prm_2", - "label": "organization-defined information system components" - } - ], - "props": [ - { - "name": "label", - "value": "SI-2(5)" - }, - { - "name": "sort-id", - "value": "si-02.05" - } - ], - "parts": [ - { - "id": "si-2.5_smt", - "name": "statement", - "prose": "The organization installs {{ insert: param, si-2.5_prm_1 }} automatically to {{ insert: param, si-2.5_prm_2 }}." - }, - { - "id": "si-2.5_gdn", - "name": "guidance", - "prose": "Due to information system integrity and availability concerns, organizations give careful consideration to the methodology used to carry out automatic updates. Organizations must balance the need to ensure that the updates are installed as soon as possible with the need to maintain configuration management and with any mission or operational impacts that automatic updates might impose." - }, - { - "id": "si-2.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-2.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(5)[1]" - } - ], - "parts": [ - { - "id": "si-2.5_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(5)[1][a]" - } - ], - "prose": "defines information system components requiring security-relevant software updates to be automatically installed;" - }, - { - "id": "si-2.5_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(5)[1][b]" - } - ], - "prose": "defines information system components requiring security-relevant firmware updates to be automatically installed;" - } - ] - }, - { - "id": "si-2.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(5)[2]" - } - ], - "parts": [ - { - "id": "si-2.5_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(5)[2][a]" - } - ], - "prose": "defines security-relevant software updates to be automatically installed to organization-defined information system components;" - }, - { - "id": "si-2.5_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(5)[2][b]" - } - ], - "prose": "defines security-relevant firmware updates to be automatically installed to organization-defined information system components;" - } - ] - }, - { - "id": "si-2.5_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(5)[3]" - } - ], - "parts": [ - { - "id": "si-2.5_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(5)[3][a]" - } - ], - "prose": "installs organization-defined security-relevant software updates automatically to organization-defined information system components; and" - }, - { - "id": "si-2.5_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(5)[3][b]" - } - ], - "prose": "installs organization-defined security-relevant firmware updates automatically to organization-defined information system components." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing flaw remediation\n\nautomated mechanisms supporting flaw remediation and automatic software/firmware updates\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nrecords of recent security-relevant software and firmware updates automatically installed to information system components\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for flaw remediation" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms implementing automatic software/firmware updates" - } - ] - } - ] - }, - { - "id": "si-2.6", - "class": "SP800-53-enhancement", - "title": "Removal of Previous Versions of Software / Firmware", - "params": [ - { - "id": "si-2.6_prm_1", - "label": "organization-defined software and firmware components" - } - ], - "props": [ - { - "name": "label", - "value": "SI-2(6)" - }, - { - "name": "sort-id", - "value": "si-02.06" - } - ], - "parts": [ - { - "id": "si-2.6_smt", - "name": "statement", - "prose": "The organization removes {{ insert: param, si-2.6_prm_1 }} after updated versions have been installed." - }, - { - "id": "si-2.6_gdn", - "name": "guidance", - "prose": "Previous versions of software and/or firmware components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some information technology products may remove older versions of software and/or firmware automatically from the information system." - }, - { - "id": "si-2.6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-2.6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(6)[1]" - } - ], - "parts": [ - { - "id": "si-2.6_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(6)[1][a]" - } - ], - "prose": "defines software components to be removed after updated versions have been installed;" - }, - { - "id": "si-2.6_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(6)[1][b]" - } - ], - "prose": "defines firmware components to be removed after updated versions have been installed;" - } - ] - }, - { - "id": "si-2.6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(6)[2]" - } - ], - "parts": [ - { - "id": "si-2.6_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(6)[2][a]" - } - ], - "prose": "removes organization-defined software components after updated versions have been installed; and" - }, - { - "id": "si-2.6_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-2(6)[2][b]" - } - ], - "prose": "removes organization-defined firmware components after updated versions have been installed." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing flaw remediation\n\nautomated mechanisms supporting flaw remediation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nrecords of software and firmware component removals after updated versions are installed\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for flaw remediation" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing removal of previous versions of software/firmware" - } - ] - } - ] - } - ] - }, - { - "id": "si-3", - "class": "SP800-53", - "title": "Malicious Code Protection", - "params": [ - { - "id": "si-3_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "si-3_prm_2", - "select": { - "how-many": "one-or-more", - "choice": [ - "endpoint", - "network entry/exit points" - ] - } - }, - { - "id": "si-3_prm_3", - "select": { - "how-many": "one-or-more", - "choice": [ - "block malicious code", - "quarantine malicious code", - "send alert to administrator", - " {{ insert: param, si-3_prm_4 }} " - ] - } - }, - { - "id": "si-3_prm_4", - "depends-on": "si-3_prm_3", - "label": "organization-defined action" - } - ], - "props": [ - { - "name": "label", - "value": "SI-3" - }, - { - "name": "sort-id", - "value": "si-03" - } - ], - "links": [ - { - "href": "#6d431fee-658f-4a0e-9f2e-a38b5d398fab", - "rel": "reference" - } - ], - "parts": [ - { - "id": "si-3_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "si-3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Employs malicious code protection mechanisms at information system entry and exit points to detect and eradicate malicious code;" - }, - { - "id": "si-3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Updates malicious code protection mechanisms whenever new releases are available in accordance with organizational configuration management policy and procedures;" - }, - { - "id": "si-3_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Configures malicious code protection mechanisms to:", - "parts": [ - { - "id": "si-3_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Perform periodic scans of the information system {{ insert: param, si-3_prm_1 }} and real-time scans of files from external sources at {{ insert: param, si-3_prm_2 }} as the files are downloaded, opened, or executed in accordance with organizational security policy; and" - }, - { - "id": "si-3_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": " {{ insert: param, si-3_prm_3 }} in response to malicious code detection; and" - } - ] - }, - { - "id": "si-3_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Addresses the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the information system." - } - ] - }, - { - "id": "si-3_gdn", - "name": "guidance", - "prose": "Information system entry and exit points include, for example, firewalls, electronic mail servers, web servers, proxy servers, remote-access servers, workstations, notebook computers, and mobile devices. Malicious code includes, for example, viruses, worms, Trojan horses, and spyware. Malicious code can also be encoded in various formats (e.g., UUENCODE, Unicode), contained within compressed or hidden files, or hidden in files using steganography. Malicious code can be transported by different means including, for example, web accesses, electronic mail, electronic mail attachments, and portable storage devices. Malicious code insertions occur through the exploitation of information system vulnerabilities. Malicious code protection mechanisms include, for example, anti-virus signature definitions and reputation-based technologies. A variety of technologies and methods exist to limit or eliminate the effects of malicious code. Pervasive configuration management and comprehensive software integrity controls may be effective in preventing execution of unauthorized code. In addition to commercial off-the-shelf software, malicious code may also be present in custom-built software. This could include, for example, logic bombs, back doors, and other types of cyber attacks that could affect organizational missions/business functions. Traditional malicious code protection mechanisms cannot always detect such code. In these situations, organizations rely instead on other safeguards including, for example, secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to help ensure that software does not perform functions other than the functions intended. Organizations may determine that in response to the detection of malicious code, different actions may be warranted. For example, organizations can define actions in response to malicious code detection during periodic scans, actions in response to detection of malicious downloads, and/or actions in response to detection of maliciousness when attempting to open or execute files.", - "links": [ - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-12", - "rel": "related" - }, - { - "href": "#sa-13", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-26", - "rel": "related" - }, - { - "href": "#sc-44", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "si-3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(a)" - } - ], - "prose": "employs malicious code protection mechanisms to detect and eradicate malicious code at information system:", - "parts": [ - { - "id": "si-3.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(a)[1]" - } - ], - "prose": "entry points;" - }, - { - "id": "si-3.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(a)[2]" - } - ], - "prose": "exit points;" - } - ] - }, - { - "id": "si-3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(b)" - } - ], - "prose": "updates malicious code protection mechanisms whenever new releases are available in accordance with organizational configuration management policy and procedures (as identified in CM-1);" - }, - { - "id": "si-3.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(c)" - } - ], - "parts": [ - { - "id": "si-3.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(c)[1]" - } - ], - "prose": "defines a frequency for malicious code protection mechanisms to perform periodic scans of the information system;" - }, - { - "id": "si-3.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(c)[2]" - } - ], - "prose": "defines action to be initiated by malicious protection mechanisms in response to malicious code detection;" - }, - { - "id": "si-3.c_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(c)[3]" - } - ], - "parts": [ - { - "id": "si-3.c.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(c)[3](1)" - } - ], - "prose": "configures malicious code protection mechanisms to:", - "parts": [ - { - "id": "si-3.c.1_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(c)[3](1)[a]" - } - ], - "prose": "perform periodic scans of the information system with the organization-defined frequency;" - }, - { - "id": "si-3.c.1_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(c)[3](1)[b]" - } - ], - "prose": "perform real-time scans of files from external sources at endpoint and/or network entry/exit points as the files are downloaded, opened, or executed in accordance with organizational security policy;" - } - ] - }, - { - "id": "si-3.c.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(c)[3](2)" - } - ], - "prose": "configures malicious code protection mechanisms to do one or more of the following:", - "parts": [ - { - "id": "si-3.c.2_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(c)[3](2)[a]" - } - ], - "prose": "block malicious code in response to malicious code detection;" - }, - { - "id": "si-3.c.2_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(c)[3](2)[b]" - } - ], - "prose": "quarantine malicious code in response to malicious code detection;" - }, - { - "id": "si-3.c.2_obj.3.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(c)[3](2)[c]" - } - ], - "prose": "send alert to administrator in response to malicious code detection; and/or" - }, - { - "id": "si-3.c.2_obj.3.d", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(c)[3](2)[d]" - } - ], - "prose": "initiate organization-defined action in response to malicious code detection;" - } - ] - } - ] - } - ] - }, - { - "id": "si-3.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(d)" - } - ], - "parts": [ - { - "id": "si-3.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(d)[1]" - } - ], - "prose": "addresses the receipt of false positives during malicious code detection and eradication; and" - }, - { - "id": "si-3.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(d)[2]" - } - ], - "prose": "addresses the resulting potential impact on the availability of the information system." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nconfiguration management policy and procedures\n\nprocedures addressing malicious code protection\n\nmalicious code protection mechanisms\n\nrecords of malicious code protection updates\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nscan results from malicious code protection mechanisms\n\nrecord of actions initiated by malicious code protection mechanisms in response to malicious code detection\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for malicious code protection\n\norganizational personnel with configuration management responsibility" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for employing, updating, and configuring malicious code protection mechanisms\n\norganizational process for addressing false positives and resulting potential impact\n\nautomated mechanisms supporting and/or implementing employing, updating, and configuring malicious code protection mechanisms\n\nautomated mechanisms supporting and/or implementing malicious code scanning and subsequent actions" - } - ] - } - ], - "controls": [ - { - "id": "si-3.1", - "class": "SP800-53-enhancement", - "title": "Central Management", - "props": [ - { - "name": "label", - "value": "SI-3(1)" - }, - { - "name": "sort-id", - "value": "si-03.01" - } - ], - "parts": [ - { - "id": "si-3.1_smt", - "name": "statement", - "prose": "The organization centrally manages malicious code protection mechanisms." - }, - { - "id": "si-3.1_gdn", - "name": "guidance", - "prose": "Central management is the organization-wide management and implementation of malicious code protection mechanisms. Central management includes planning, implementing, assessing, authorizing, and monitoring the organization-defined, centrally managed flaw malicious code protection security controls.", - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#si-8", - "rel": "related" - } - ] - }, - { - "id": "si-3.1_obj", - "name": "objective", - "prose": "Determine if the organization centrally manages malicious code protection mechanisms." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing malicious code protection\n\nautomated mechanisms supporting centralized management of malicious code protection mechanisms\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for malicious code protection" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for central management of malicious code protection mechanisms\n\nautomated mechanisms supporting and/or implementing central management of malicious code protection mechanisms" - } - ] - } - ] - }, - { - "id": "si-3.2", - "class": "SP800-53-enhancement", - "title": "Automatic Updates", - "props": [ - { - "name": "label", - "value": "SI-3(2)" - }, - { - "name": "sort-id", - "value": "si-03.02" - } - ], - "parts": [ - { - "id": "si-3.2_smt", - "name": "statement", - "prose": "The information system automatically updates malicious code protection mechanisms." - }, - { - "id": "si-3.2_gdn", - "name": "guidance", - "prose": "Malicious code protection mechanisms include, for example, signature definitions. Due to information system integrity and availability concerns, organizations give careful consideration to the methodology used to carry out automatic updates.", - "links": [ - { - "href": "#si-8", - "rel": "related" - } - ] - }, - { - "id": "si-3.2_obj", - "name": "objective", - "prose": "Determine if the information system automatically updates malicious code protection mechanisms." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing malicious code protection\n\nautomated mechanisms supporting centralized management of malicious code protection mechanisms\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for malicious code protection" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing automatic updates to malicious code protection capability" - } - ] - } - ] - }, - { - "id": "si-3.3", - "class": "SP800-53-enhancement", - "title": "Non-privileged Users", - "props": [ - { - "name": "label", - "value": "SI-3(3)" - }, - { - "name": "sort-id", - "value": "si-03.03" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#ac-6.10", - "rel": "incorporated-into" - } - ] - }, - { - "id": "si-3.4", - "class": "SP800-53-enhancement", - "title": "Updates Only by Privileged Users", - "props": [ - { - "name": "label", - "value": "SI-3(4)" - }, - { - "name": "sort-id", - "value": "si-03.04" - } - ], - "parts": [ - { - "id": "si-3.4_smt", - "name": "statement", - "prose": "The information system updates malicious code protection mechanisms only when directed by a privileged user." - }, - { - "id": "si-3.4_gdn", - "name": "guidance", - "prose": "This control enhancement may be appropriate for situations where for reasons of security or operational continuity, updates are only applied when selected/approved by designated organizational personnel.", - "links": [ - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - } - ] - }, - { - "id": "si-3.4_obj", - "name": "objective", - "prose": "Determine if the information system updates malicious code protection mechanisms only when directed by a privileged user." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing malicious code protection\n\ninformation system design documentation\n\nmalicious code protection mechanisms\n\nrecords of malicious code protection updates\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for malicious code protection" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing malicious code protection capability" - } - ] - } - ] - }, - { - "id": "si-3.5", - "class": "SP800-53-enhancement", - "title": "Portable Storage Devices", - "props": [ - { - "name": "label", - "value": "SI-3(5)" - }, - { - "name": "sort-id", - "value": "si-03.05" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#mp-7", - "rel": "incorporated-into" - } - ] - }, - { - "id": "si-3.6", - "class": "SP800-53-enhancement", - "title": "Testing / Verification", - "params": [ - { - "id": "si-3.6_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "SI-3(6)" - }, - { - "name": "sort-id", - "value": "si-03.06" - } - ], - "parts": [ - { - "id": "si-3.6_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "si-3.6_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Tests malicious code protection mechanisms {{ insert: param, si-3.6_prm_1 }} by introducing a known benign, non-spreading test case into the information system; and" - }, - { - "id": "si-3.6_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Verifies that both detection of the test case and associated incident reporting occur." - } - ] - }, - { - "id": "si-3.6_gdn", - "name": "guidance", - "links": [ - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - } - ] - }, - { - "id": "si-3.6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-3.6.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(6)(a)" - } - ], - "parts": [ - { - "id": "si-3.6.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(6)(a)[1]" - } - ], - "prose": "defines a frequency to test malicious code protection mechanisms;" - }, - { - "id": "si-3.6.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(6)(a)[2]" - } - ], - "prose": "tests malicious code protection mechanisms with the organization-defined frequency by introducing a known benign, non-spreading test case into the information system;" - } - ], - "links": [ - { - "href": "#si-3.6_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "si-3.6.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(6)(b)" - } - ], - "parts": [ - { - "id": "si-3.6.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(6)(b)[1]" - } - ], - "prose": "verifies that detection of the test case occurs; and" - }, - { - "id": "si-3.6.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(6)(b)[2]" - } - ], - "prose": "verifies that associated incident reporting occurs." - } - ], - "links": [ - { - "href": "#si-3.6_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing malicious code protection\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ntest cases\n\nrecords providing evidence of test cases executed on malicious code protection mechanisms\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for malicious code protection" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing testing and verification of malicious code protection capability" - } - ] - } - ] - }, - { - "id": "si-3.7", - "class": "SP800-53-enhancement", - "title": "Nonsignature-based Detection", - "props": [ - { - "name": "label", - "value": "SI-3(7)" - }, - { - "name": "sort-id", - "value": "si-03.07" - } - ], - "parts": [ - { - "id": "si-3.7_smt", - "name": "statement", - "prose": "The information system implements nonsignature-based malicious code detection mechanisms." - }, - { - "id": "si-3.7_gdn", - "name": "guidance", - "prose": "Nonsignature-based detection mechanisms include, for example, the use of heuristics to detect, analyze, and describe the characteristics or behavior of malicious code and to provide safeguards against malicious code for which signatures do not yet exist or for which existing signatures may not be effective. This includes polymorphic malicious code (i.e., code that changes signatures when it replicates). This control enhancement does not preclude the use of signature-based detection mechanisms." - }, - { - "id": "si-3.7_obj", - "name": "objective", - "prose": "Determine if the information system implements non signature-based malicious code detection mechanisms." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing malicious code protection\n\ninformation system design documentation\n\nmalicious code protection mechanisms\n\nrecords of malicious code protection updates\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for malicious code protection" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing nonsignature-based malicious code protection capability" - } - ] - } - ] - }, - { - "id": "si-3.8", - "class": "SP800-53-enhancement", - "title": "Detect Unauthorized Commands", - "params": [ - { - "id": "si-3.8_prm_1", - "label": "organization-defined unauthorized operating system commands" - }, - { - "id": "si-3.8_prm_2", - "label": "organization-defined information system hardware components" - }, - { - "id": "si-3.8_prm_3", - "select": { - "how-many": "one-or-more", - "choice": [ - "issues a warning", - "audits the command execution", - "prevents the execution of the command" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "SI-3(8)" - }, - { - "name": "sort-id", - "value": "si-03.08" - } - ], - "parts": [ - { - "id": "si-3.8_smt", - "name": "statement", - "prose": "The information system detects {{ insert: param, si-3.8_prm_1 }} through the kernel application programming interface at {{ insert: param, si-3.8_prm_2 }} and {{ insert: param, si-3.8_prm_3 }}." - }, - { - "id": "si-3.8_gdn", - "name": "guidance", - "prose": "This control enhancement can also be applied to critical interfaces other than kernel-based interfaces, including for example, interfaces with virtual machines and privileged applications. Unauthorized operating system commands include, for example, commands for kernel functions from information system processes that are not trusted to initiate such commands, or commands for kernel functions that are suspicious even though commands of that type are reasonable for processes to initiate. Organizations can define the malicious commands to be detected by a combination of command types, command classes, or specific instances of commands. Organizations can define hardware components by specific component, component type, location in the network, or combination therein. Organizations may select different actions for different types/classes/specific instances of potentially malicious commands.", - "links": [ - { - "href": "#au-6", - "rel": "related" - } - ] - }, - { - "id": "si-3.8_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "si-3.8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(8)[1]" - } - ], - "prose": "the organization defines unauthorized operating system commands to be detected by the information system;" - }, - { - "id": "si-3.8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(8)[2]" - } - ], - "prose": "the organization defines information system hardware components for which organization-defined unauthorized operating system commands are to be detected through the kernel application programming interface;" - }, - { - "id": "si-3.8_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(8)[3]" - } - ], - "prose": "the information system detects organization-defined unauthorized operating system commands through the kernel application programming interface at organization-defined information system hardware components, and does one or more of the following:", - "parts": [ - { - "id": "si-3.8_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(8)[3][a]" - } - ], - "prose": "issues a warning;" - }, - { - "id": "si-3.8_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(8)[3][b]" - } - ], - "prose": "audits the command execution; and/or" - }, - { - "id": "si-3.8_obj.3.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(8)[3][c]" - } - ], - "prose": "prevents the execution of the command." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing malicious code protection\n\ninformation system design documentation\n\nmalicious code protection mechanisms\n\nwarning messages sent upon detection of unauthorized operating system command execution\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for malicious code protection" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing malicious code protection capability\n\nautomated mechanisms supporting and/or implementing detection of unauthorized operating system commands through the kernel application programming interface" - } - ] - } - ] - }, - { - "id": "si-3.9", - "class": "SP800-53-enhancement", - "title": "Authenticate Remote Commands", - "params": [ - { - "id": "si-3.9_prm_1", - "label": "organization-defined security safeguards" - }, - { - "id": "si-3.9_prm_2", - "label": "organization-defined remote commands" - } - ], - "props": [ - { - "name": "label", - "value": "SI-3(9)" - }, - { - "name": "sort-id", - "value": "si-03.09" - } - ], - "parts": [ - { - "id": "si-3.9_smt", - "name": "statement", - "prose": "The information system implements {{ insert: param, si-3.9_prm_1 }} to authenticate {{ insert: param, si-3.9_prm_2 }}." - }, - { - "id": "si-3.9_gdn", - "name": "guidance", - "prose": "This control enhancement protects against unauthorized commands and replay of authorized commands. This capability is important for those remote information systems whose loss, malfunction, misdirection, or exploitation would have immediate and/or serious consequences (e.g., injury or death, property damage, loss of high-valued assets or sensitive information, or failure of important missions/business functions). Authentication safeguards for remote commands help to ensure that information systems accept and execute in the order intended, only authorized commands, and that unauthorized commands are rejected. Cryptographic mechanisms can be employed, for example, to authenticate remote commands.", - "links": [ - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#sc-23", - "rel": "related" - } - ] - }, - { - "id": "si-3.9_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "si-3.9_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(9)[1]" - } - ], - "prose": "the organization defines security safeguards to be implemented by the information system to authenticate organization-defined remote commands;" - }, - { - "id": "si-3.9_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(9)[2]" - } - ], - "prose": "the organization defines remote commands to be authenticated by organization-defined security safeguards; and" - }, - { - "id": "si-3.9_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(9)[3]" - } - ], - "prose": "the information system implements organization-defined security safeguards to authenticate organization-defined remote commands." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing malicious code protection\n\ninformation system design documentation\n\nmalicious code protection mechanisms\n\nwarning messages sent upon detection of unauthorized operating system command execution\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for malicious code protection" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing malicious code protection capability\n\nautomated mechanisms implementing authentication of remote commands\n\nautomated mechanisms supporting and/or implementing security safeguards to authenticate remote commands" - } - ] - } - ] - }, - { - "id": "si-3.10", - "class": "SP800-53-enhancement", - "title": "Malicious Code Analysis", - "params": [ - { - "id": "si-3.10_prm_1", - "label": "organization-defined tools and techniques" - } - ], - "props": [ - { - "name": "label", - "value": "SI-3(10)" - }, - { - "name": "sort-id", - "value": "si-03.10" - } - ], - "parts": [ - { - "id": "si-3.10_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "si-3.10_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Employs {{ insert: param, si-3.10_prm_1 }} to analyze the characteristics and behavior of malicious code; and" - }, - { - "id": "si-3.10_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Incorporates the results from malicious code analysis into organizational incident response and flaw remediation processes." - } - ] - }, - { - "id": "si-3.10_gdn", - "name": "guidance", - "prose": "The application of selected malicious code analysis tools and techniques provides organizations with a more in-depth understanding of adversary tradecraft (i.e., tactics, techniques, and procedures) and the functionality and purpose of specific instances of malicious code. Understanding the characteristics of malicious code facilitates more effective organizational responses to current and future threats. Organizations can conduct malicious code analyses by using reverse engineering techniques or by monitoring the behavior of executing code." - }, - { - "id": "si-3.10_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-3.10.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(10)(a)" - } - ], - "parts": [ - { - "id": "si-3.10.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(10)(a)[1]" - } - ], - "prose": "defines tools and techniques to be employed to analyze the characteristics and behavior of malicious code;" - }, - { - "id": "si-3.10.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(10)(a)[2]" - } - ], - "prose": "employs organization-defined tools and techniques to analyze the characteristics and behavior of malicious code; and" - } - ], - "links": [ - { - "href": "#si-3.10_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "si-3.10.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-3(10)(b)" - } - ], - "prose": "incorporates the results from malicious code analysis into incident response and flaw remediate processes.", - "links": [ - { - "href": "#si-3.10_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing malicious code protection\n\nprocedures addressing incident response\n\nprocedures addressing flaw remediation\n\ninformation system design documentation\n\nmalicious code protection mechanisms, tools, and techniques\n\ninformation system configuration settings and associated documentation\n\nresults from malicious code analyses\n\nrecords of flaw remediation events resulting from malicious code analyses\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for malicious code protection\n\norganizational personnel responsible for flaw remediation\n\norganizational personnel responsible for incident response/management" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational process for incident response\n\norganizational process for flaw remediation\n\nautomated mechanisms supporting and/or implementing malicious code protection capability\n\ntools and techniques for analysis of malicious code characteristics and behavior" - } - ] - } - ] - } - ] - }, - { - "id": "si-4", - "class": "SP800-53", - "title": "Information System Monitoring", - "params": [ - { - "id": "si-4_prm_1", - "label": "organization-defined monitoring objectives" - }, - { - "id": "si-4_prm_2", - "label": "organization-defined techniques and methods" - }, - { - "id": "si-4_prm_3", - "label": "organization-defined information system monitoring information" - }, - { - "id": "si-4_prm_4", - "label": "organization-defined personnel or roles" - }, - { - "id": "si-4_prm_5", - "select": { - "how-many": "one-or-more", - "choice": [ - "as needed", - " {{ insert: param, si-4_prm_6 }} " - ] - } - }, - { - "id": "si-4_prm_6", - "depends-on": "si-4_prm_5", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "SI-4" - }, - { - "name": "sort-id", - "value": "si-04" - } - ], - "links": [ - { - "href": "#be95fb85-a53f-4624-bdbb-140075500aa3", - "rel": "reference" - }, - { - "href": "#6d431fee-658f-4a0e-9f2e-a38b5d398fab", - "rel": "reference" - }, - { - "href": "#672fd561-b92b-4713-b9cf-6c9d9456728b", - "rel": "reference" - }, - { - "href": "#d1b1d689-0f66-4474-9924-c81119758dc1", - "rel": "reference" - }, - { - "href": "#cee2c6ca-0261-4a6f-b630-e41d8ffdd82b", - "rel": "reference" - } - ], - "parts": [ - { - "id": "si-4_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "si-4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Monitors the information system to detect:", - "parts": [ - { - "id": "si-4_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Attacks and indicators of potential attacks in accordance with {{ insert: param, si-4_prm_1 }}; and" - }, - { - "id": "si-4_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Unauthorized local, network, and remote connections;" - } - ] - }, - { - "id": "si-4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Identifies unauthorized use of the information system through {{ insert: param, si-4_prm_2 }};" - }, - { - "id": "si-4_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Deploys monitoring devices:", - "parts": [ - { - "id": "si-4_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Strategically within the information system to collect organization-determined essential information; and" - }, - { - "id": "si-4_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "At ad hoc locations within the system to track specific types of transactions of interest to the organization;" - } - ] - }, - { - "id": "si-4_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Protects information obtained from intrusion-monitoring tools from unauthorized access, modification, and deletion;" - }, - { - "id": "si-4_smt.e", - "name": "item", - "props": [ - { - "name": "label", - "value": "e." - } - ], - "prose": "Heightens the level of information system monitoring activity whenever there is an indication of increased risk to organizational operations and assets, individuals, other organizations, or the Nation based on law enforcement information, intelligence information, or other credible sources of information;" - }, - { - "id": "si-4_smt.f", - "name": "item", - "props": [ - { - "name": "label", - "value": "f." - } - ], - "prose": "Obtains legal opinion with regard to information system monitoring activities in accordance with applicable federal laws, Executive Orders, directives, policies, or regulations; and" - }, - { - "id": "si-4_smt.g", - "name": "item", - "props": [ - { - "name": "label", - "value": "g." - } - ], - "prose": "Provides {{ insert: param, si-4_prm_3 }} to {{ insert: param, si-4_prm_4 }} {{ insert: param, si-4_prm_5 }}." - } - ] - }, - { - "id": "si-4_gdn", - "name": "guidance", - "prose": "Information system monitoring includes external and internal monitoring. External monitoring includes the observation of events occurring at the information system boundary (i.e., part of perimeter defense and boundary protection). Internal monitoring includes the observation of events occurring within the information system. Organizations can monitor information systems, for example, by observing audit activities in real time or by observing other system aspects such as access patterns, characteristics of access, and other actions. The monitoring objectives may guide determination of the events. Information system monitoring capability is achieved through a variety of tools and techniques (e.g., intrusion detection systems, intrusion prevention systems, malicious code protection software, scanning tools, audit record monitoring software, network monitoring software). Strategic locations for monitoring devices include, for example, selected perimeter locations and near server farms supporting critical applications, with such devices typically being employed at the managed interfaces associated with controls SC-7 and AC-17. Einstein network monitoring devices from the Department of Homeland Security can also be included as monitoring devices. The granularity of monitoring information collected is based on organizational monitoring objectives and the capability of information systems to support such objectives. Specific types of transactions of interest include, for example, Hyper Text Transfer Protocol (HTTP) traffic that bypasses HTTP proxies. Information system monitoring is an integral part of organizational continuous monitoring and incident response programs. Output from system monitoring serves as input to continuous monitoring and incident response programs. A network connection is any connection with a device that communicates through a network (e.g., local area network, Internet). A remote connection is any connection with a device communicating through an external network (e.g., the Internet). Local, network, and remote connections can be either wired or wireless.", - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-8", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-7", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-26", - "rel": "related" - }, - { - "href": "#sc-35", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "si-4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(a)" - } - ], - "parts": [ - { - "id": "si-4.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(a)(1)" - } - ], - "parts": [ - { - "id": "si-4.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(a)(1)[1]" - } - ], - "prose": "defines monitoring objectives to detect attacks and indicators of potential attacks on the information system;" - }, - { - "id": "si-4.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(a)(1)[2]" - } - ], - "prose": "monitors the information system to detect, in accordance with organization-defined monitoring objectives,:", - "parts": [ - { - "id": "si-4.a.1_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(a)(1)[2][a]" - } - ], - "prose": "attacks;" - }, - { - "id": "si-4.a.1_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(a)(1)[2][b]" - } - ], - "prose": "indicators of potential attacks;" - } - ] - } - ] - }, - { - "id": "si-4.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(a)(2)" - } - ], - "prose": "monitors the information system to detect unauthorized:", - "parts": [ - { - "id": "si-4.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(a)(2)[1]" - } - ], - "prose": "local connections;" - }, - { - "id": "si-4.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(a)(2)[2]" - } - ], - "prose": "network connections;" - }, - { - "id": "si-4.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(a)(2)[3]" - } - ], - "prose": "remote connections;" - } - ] - } - ] - }, - { - "id": "si-4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(b)" - } - ], - "parts": [ - { - "id": "si-4.b.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(b)(1)" - } - ], - "prose": "defines techniques and methods to identify unauthorized use of the information system;" - }, - { - "id": "si-4.b.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(b)(2)" - } - ], - "prose": "identifies unauthorized use of the information system through organization-defined techniques and methods;" - } - ] - }, - { - "id": "si-4.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(c)" - } - ], - "prose": "deploys monitoring devices:", - "parts": [ - { - "id": "si-4.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(c)[1]" - } - ], - "prose": "strategically within the information system to collect organization-determined essential information;" - }, - { - "id": "si-4.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(c)[2]" - } - ], - "prose": "at ad hoc locations within the system to track specific types of transactions of interest to the organization;" - } - ] - }, - { - "id": "si-4.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(d)" - } - ], - "prose": "protects information obtained from intrusion-monitoring tools from unauthorized:", - "parts": [ - { - "id": "si-4.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(d)[1]" - } - ], - "prose": "access;" - }, - { - "id": "si-4.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(d)[2]" - } - ], - "prose": "modification;" - }, - { - "id": "si-4.d_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(d)[3]" - } - ], - "prose": "deletion;" - } - ] - }, - { - "id": "si-4.e_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(e)" - } - ], - "prose": "heightens the level of information system monitoring activity whenever there is an indication of increased risk to organizational operations and assets, individuals, other organizations, or the Nation based on law enforcement information, intelligence information, or other credible sources of information;" - }, - { - "id": "si-4.f_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(f)" - } - ], - "prose": "obtains legal opinion with regard to information system monitoring activities in accordance with applicable federal laws, Executive Orders, directives, policies, or regulations;" - }, - { - "id": "si-4.g_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(g)" - } - ], - "parts": [ - { - "id": "si-4.g_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(g)[1]" - } - ], - "prose": "defines personnel or roles to whom information system monitoring information is to be provided;" - }, - { - "id": "si-4.g_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(g)[2]" - } - ], - "prose": "defines information system monitoring information to be provided to organization-defined personnel or roles;" - }, - { - "id": "si-4.g_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(g)[3]" - } - ], - "prose": "defines a frequency to provide organization-defined information system monitoring to organization-defined personnel or roles;" - }, - { - "id": "si-4.g_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(g)[4]" - } - ], - "prose": "provides organization-defined information system monitoring information to organization-defined personnel or roles one or more of the following:", - "parts": [ - { - "id": "si-4.g_obj.4.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(g)[4][a]" - } - ], - "prose": "as needed; and/or" - }, - { - "id": "si-4.g_obj.4.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(g)[4][b]" - } - ], - "prose": "with the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Continuous monitoring strategy\n\nsystem and information integrity policy\n\nprocedures addressing information system monitoring tools and techniques\n\nfacility diagram/layout\n\ninformation system design documentation\n\ninformation system monitoring tools and techniques documentation\n\nlocations within information system where monitoring devices are deployed\n\ninformation system configuration settings and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility monitoring the information system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for information system monitoring\n\nautomated mechanisms supporting and/or implementing information system monitoring capability" - } - ] - } - ], - "controls": [ - { - "id": "si-4.1", - "class": "SP800-53-enhancement", - "title": "System-wide Intrusion Detection System", - "props": [ - { - "name": "label", - "value": "SI-4(1)" - }, - { - "name": "sort-id", - "value": "si-04.01" - } - ], - "parts": [ - { - "id": "si-4.1_smt", - "name": "statement", - "prose": "The organization connects and configures individual intrusion detection tools into an information system-wide intrusion detection system." - }, - { - "id": "si-4.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-4.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(1)[1]" - } - ], - "prose": "connects individual intrusion detection tools into an information system-wide intrusion detection system; and" - }, - { - "id": "si-4.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(1)[2]" - } - ], - "prose": "configures individual intrusion detection tools into an information system-wide intrusion detection system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring tools and techniques\n\ninformation system design documentation\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system\n\norganizational personnel with responsibility for the intrusion detection system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for intrusion detection/information system monitoring\n\nautomated mechanisms supporting and/or implementing intrusion detection capability" - } - ] - } - ] - }, - { - "id": "si-4.2", - "class": "SP800-53-enhancement", - "title": "Automated Tools for Real-time Analysis", - "props": [ - { - "name": "label", - "value": "SI-4(2)" - }, - { - "name": "sort-id", - "value": "si-04.02" - } - ], - "parts": [ - { - "id": "si-4.2_smt", - "name": "statement", - "prose": "The organization employs automated tools to support near real-time analysis of events." - }, - { - "id": "si-4.2_gdn", - "name": "guidance", - "prose": "Automated tools include, for example, host-based, network-based, transport-based, or storage-based event monitoring tools or Security Information and Event Management (SIEM) technologies that provide real time analysis of alerts and/or notifications generated by organizational information systems." - }, - { - "id": "si-4.2_obj", - "name": "objective", - "prose": "Determine if the organization employs automated tools to support near real-time analysis of events." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring tools and techniques\n\ninformation system design documentation\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system\n\norganizational personnel with responsibility for incident response/management" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for near real-time analysis of events\n\norganizational processes for information system monitoring\n\nautomated mechanisms supporting and/or implementing information system monitoring\n\nautomated mechanisms/tools supporting and/or implementing analysis of events" - } - ] - } - ] - }, - { - "id": "si-4.3", - "class": "SP800-53-enhancement", - "title": "Automated Tool Integration", - "props": [ - { - "name": "label", - "value": "SI-4(3)" - }, - { - "name": "sort-id", - "value": "si-04.03" - } - ], - "parts": [ - { - "id": "si-4.3_smt", - "name": "statement", - "prose": "The organization employs automated tools to integrate intrusion detection tools into access control and flow control mechanisms for rapid response to attacks by enabling reconfiguration of these mechanisms in support of attack isolation and elimination." - }, - { - "id": "si-4.3_obj", - "name": "objective", - "prose": "Determine if the organization, for rapid response to attacks by enabling reconfiguration of intrusion detection tools in support of attack isolation and elimination, employs automated tools to integrate intrusion detection tools into:", - "parts": [ - { - "id": "si-4.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(3)[1]" - } - ], - "prose": "access control mechanisms; and" - }, - { - "id": "si-4.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(3)[2]" - } - ], - "prose": "flow control mechanisms." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\naccess control policy and procedures\n\nprocedures addressing information system monitoring tools and techniques\n\ninformation system design documentation\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system\n\norganizational personnel with responsibility for the intrusion detection system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for intrusion detection/information system monitoring\n\nautomated mechanisms supporting and/or implementing intrusion detection/information system monitoring capability\n\nautomated mechanisms/tools supporting and/or implementing access/flow control capability\n\nautomated mechanisms/tools supporting and/or implementing integration of intrusion detection tools into access/flow control mechanisms" - } - ] - } - ] - }, - { - "id": "si-4.4", - "class": "SP800-53-enhancement", - "title": "Inbound and Outbound Communications Traffic", - "params": [ - { - "id": "si-4.4_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "SI-4(4)" - }, - { - "name": "sort-id", - "value": "si-04.04" - } - ], - "parts": [ - { - "id": "si-4.4_smt", - "name": "statement", - "prose": "The information system monitors inbound and outbound communications traffic {{ insert: param, si-4.4_prm_1 }} for unusual or unauthorized activities or conditions." - }, - { - "id": "si-4.4_gdn", - "name": "guidance", - "prose": "Unusual/unauthorized activities or conditions related to information system inbound and outbound communications traffic include, for example, internal traffic that indicates the presence of malicious code within organizational information systems or propagating among system components, the unauthorized exporting of information, or signaling to external information systems. Evidence of malicious code is used to identify potentially compromised information systems or information system components." - }, - { - "id": "si-4.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-4.4_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(4)[1]" - } - ], - "prose": "defines a frequency to monitor:", - "parts": [ - { - "id": "si-4.4_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(4)[1][a]" - } - ], - "prose": "inbound communications traffic for unusual or unauthorized activities or conditions;" - }, - { - "id": "si-4.4_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(4)[1][b]" - } - ], - "prose": "outbound communications traffic for unusual or unauthorized activities or conditions;" - } - ] - }, - { - "id": "si-4.4_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(4)[2]" - } - ], - "prose": "monitors, with the organization-defined frequency:", - "parts": [ - { - "id": "si-4.4_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(4)[2][a]" - } - ], - "prose": "inbound communications traffic for unusual or unauthorized activities or conditions; and" - }, - { - "id": "si-4.4_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(4)[2][b]" - } - ], - "prose": "outbound communications traffic for unusual or unauthorized activities or conditions." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring tools and techniques\n\ninformation system design documentation\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system protocols\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system\n\norganizational personnel with responsibility for the intrusion detection system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for intrusion detection/information system monitoring\n\nautomated mechanisms supporting and/or implementing intrusion detection capability/information system monitoring\n\nautomated mechanisms supporting and/or implementing monitoring of inbound/outbound communications traffic" - } - ] - } - ] - }, - { - "id": "si-4.5", - "class": "SP800-53-enhancement", - "title": "System-generated Alerts", - "params": [ - { - "id": "si-4.5_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "si-4.5_prm_2", - "label": "organization-defined compromise indicators" - } - ], - "props": [ - { - "name": "label", - "value": "SI-4(5)" - }, - { - "name": "sort-id", - "value": "si-04.05" - } - ], - "parts": [ - { - "id": "si-4.5_smt", - "name": "statement", - "prose": "The information system alerts {{ insert: param, si-4.5_prm_1 }} when the following indications of compromise or potential compromise occur: {{ insert: param, si-4.5_prm_2 }}." - }, - { - "id": "si-4.5_gdn", - "name": "guidance", - "prose": "Alerts may be generated from a variety of sources, including, for example, audit records or inputs from malicious code protection mechanisms, intrusion detection or prevention mechanisms, or boundary protection devices such as firewalls, gateways, and routers. Alerts can be transmitted, for example, telephonically, by electronic mail messages, or by text messaging. Organizational personnel on the notification list can include, for example, system administrators, mission/business owners, system owners, or information system security officers.", - "links": [ - { - "href": "#au-5", - "rel": "related" - }, - { - "href": "#pe-6", - "rel": "related" - } - ] - }, - { - "id": "si-4.5_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "si-4.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(5)[1]" - } - ], - "prose": "the organization defines compromise indicators for the information system;" - }, - { - "id": "si-4.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(5)[2]" - } - ], - "prose": "the organization defines personnel or roles to be alerted when indications of compromise or potential compromise occur; and" - }, - { - "id": "si-4.5_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(5)[3]" - } - ], - "prose": "the information system alerts organization-defined personnel or roles when organization-defined compromise indicators occur." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring tools and techniques\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\nalerts/notifications generated based on compromise indicators\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system\n\norganizational personnel with responsibility for the intrusion detection system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for intrusion detection/information system monitoring\n\nautomated mechanisms supporting and/or implementing intrusion detection/information system monitoring capability\n\nautomated mechanisms supporting and/or implementing alerts for compromise indicators" - } - ] - } - ] - }, - { - "id": "si-4.6", - "class": "SP800-53-enhancement", - "title": "Restrict Non-privileged Users", - "props": [ - { - "name": "label", - "value": "SI-4(6)" - }, - { - "name": "sort-id", - "value": "si-04.06" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#ac-6.10", - "rel": "incorporated-into" - } - ] - }, - { - "id": "si-4.7", - "class": "SP800-53-enhancement", - "title": "Automated Response to Suspicious Events", - "params": [ - { - "id": "si-4.7_prm_1", - "label": "organization-defined incident response personnel (identified by name and/or by role)" - }, - { - "id": "si-4.7_prm_2", - "label": "organization-defined least-disruptive actions to terminate suspicious events" - } - ], - "props": [ - { - "name": "label", - "value": "SI-4(7)" - }, - { - "name": "sort-id", - "value": "si-04.07" - } - ], - "parts": [ - { - "id": "si-4.7_smt", - "name": "statement", - "prose": "The information system notifies {{ insert: param, si-4.7_prm_1 }} of detected suspicious events and takes {{ insert: param, si-4.7_prm_2 }}." - }, - { - "id": "si-4.7_gdn", - "name": "guidance", - "prose": "Least-disruptive actions may include, for example, initiating requests for human responses." - }, - { - "id": "si-4.7_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "si-4.7_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(7)[1]" - } - ], - "prose": "the organization defines incident response personnel (identified by name and/or by role) to be notified of detected suspicious events;" - }, - { - "id": "si-4.7_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(7)[2]" - } - ], - "prose": "the organization defines least-disruptive actions to be taken by the information system to terminate suspicious events;" - }, - { - "id": "si-4.7_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(7)[3]" - } - ], - "prose": "the information system notifies organization-defined incident response personnel of detected suspicious events; and" - }, - { - "id": "si-4.7_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(7)[4]" - } - ], - "prose": "the information system takes organization-defined least-disruptive actions to terminate suspicious events." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring tools and techniques\n\ninformation system design documentation\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\nalerts/notifications generated based on detected suspicious events\n\nrecords of actions taken to terminate suspicious events\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system\n\norganizational personnel with responsibility for the intrusion detection system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for intrusion detection/information system monitoring\n\nautomated mechanisms supporting and/or implementing intrusion detection/information system monitoring capability\n\nautomated mechanisms supporting and/or implementing notifications to incident response personnel\n\nautomated mechanisms supporting and/or implementing actions to terminate suspicious events" - } - ] - } - ] - }, - { - "id": "si-4.8", - "class": "SP800-53-enhancement", - "title": "Protection of Monitoring Information", - "props": [ - { - "name": "label", - "value": "SI-4(8)" - }, - { - "name": "sort-id", - "value": "si-04.08" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#si-4", - "rel": "incorporated-into" - } - ] - }, - { - "id": "si-4.9", - "class": "SP800-53-enhancement", - "title": "Testing of Monitoring Tools", - "params": [ - { - "id": "si-4.9_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "SI-4(9)" - }, - { - "name": "sort-id", - "value": "si-04.09" - } - ], - "parts": [ - { - "id": "si-4.9_smt", - "name": "statement", - "prose": "The organization tests intrusion-monitoring tools {{ insert: param, si-4.9_prm_1 }}." - }, - { - "id": "si-4.9_gdn", - "name": "guidance", - "prose": "Testing intrusion-monitoring tools is necessary to ensure that the tools are operating correctly and continue to meet the monitoring objectives of organizations. The frequency of testing depends on the types of tools used by organizations and methods of deployment.", - "links": [ - { - "href": "#cp-9", - "rel": "related" - } - ] - }, - { - "id": "si-4.9_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-4.9_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(9)[1]" - } - ], - "prose": "defines a frequency to test intrusion-monitoring tools; and" - }, - { - "id": "si-4.9_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(9)[2]" - } - ], - "prose": "tests intrusion-monitoring tools with the organization-defined frequency." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing testing of information system monitoring tools and techniques\n\ndocumentation providing evidence of testing intrusion-monitoring tools\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system\n\norganizational personnel with responsibility for the intrusion detection system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for intrusion detection/information system monitoring\n\nautomated mechanisms supporting and/or implementing intrusion detection/information system monitoring capability\n\nautomated mechanisms supporting and/or implementing testing of intrusion-monitoring tools" - } - ] - } - ] - }, - { - "id": "si-4.10", - "class": "SP800-53-enhancement", - "title": "Visibility of Encrypted Communications", - "params": [ - { - "id": "si-4.10_prm_1", - "label": "organization-defined encrypted communications traffic" - }, - { - "id": "si-4.10_prm_2", - "label": "organization-defined information system monitoring tools" - } - ], - "props": [ - { - "name": "label", - "value": "SI-4(10)" - }, - { - "name": "sort-id", - "value": "si-04.10" - } - ], - "parts": [ - { - "id": "si-4.10_smt", - "name": "statement", - "prose": "The organization makes provisions so that {{ insert: param, si-4.10_prm_1 }} is visible to {{ insert: param, si-4.10_prm_2 }}." - }, - { - "id": "si-4.10_gdn", - "name": "guidance", - "prose": "Organizations balance the potentially conflicting needs for encrypting communications traffic and for having insight into such traffic from a monitoring perspective. For some organizations, the need to ensure the confidentiality of communications traffic is paramount; for others, mission-assurance is of greater concern. Organizations determine whether the visibility requirement applies to internal encrypted traffic, encrypted traffic intended for external destinations, or a subset of the traffic types." - }, - { - "id": "si-4.10_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-4.10_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(10)[1]" - } - ], - "prose": "defines encrypted communications traffic required to be visible to information system monitoring tools;" - }, - { - "id": "si-4.10_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(10)[2]" - } - ], - "prose": "defines information system monitoring tools to be provided access to organization-defined encrypted communications traffic; and" - }, - { - "id": "si-4.10_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(10)[3]" - } - ], - "prose": "makes provisions so that organization-defined encrypted communications traffic is visible to organization-defined information system monitoring tools." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring tools and techniques\n\ninformation system design documentation\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system protocols\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system\n\norganizational personnel with responsibility for the intrusion detection system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for intrusion detection/information system monitoring\n\nautomated mechanisms supporting and/or implementing intrusion detection/information system monitoring capability\n\nautomated mechanisms supporting and/or implementing visibility of encrypted communications traffic to monitoring tools" - } - ] - } - ] - }, - { - "id": "si-4.11", - "class": "SP800-53-enhancement", - "title": "Analyze Communications Traffic Anomalies", - "params": [ - { - "id": "si-4.11_prm_1", - "label": "organization-defined interior points within the system (e.g., subnetworks, subsystems)" - } - ], - "props": [ - { - "name": "label", - "value": "SI-4(11)" - }, - { - "name": "sort-id", - "value": "si-04.11" - } - ], - "parts": [ - { - "id": "si-4.11_smt", - "name": "statement", - "prose": "The organization analyzes outbound communications traffic at the external boundary of the information system and selected {{ insert: param, si-4.11_prm_1 }} to discover anomalies." - }, - { - "id": "si-4.11_gdn", - "name": "guidance", - "prose": "Anomalies within organizational information systems include, for example, large file transfers, long-time persistent connections, unusual protocols and ports in use, and attempted communications with suspected malicious external addresses." - }, - { - "id": "si-4.11_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-4.11_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(11)[1]" - } - ], - "prose": "defines interior points within the system (e.g., subnetworks, subsystems) where communications traffic is to be analyzed;" - }, - { - "id": "si-4.11_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(11)[2]" - } - ], - "prose": "analyzes outbound communications traffic to discover anomalies at:", - "parts": [ - { - "id": "si-4.11_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(11)[2][a]" - } - ], - "prose": "the external boundary of the information system; and" - }, - { - "id": "si-4.11_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(11)[2][b]" - } - ], - "prose": "selected organization-defined interior points within the system." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring tools and techniques\n\ninformation system design documentation\n\nnetwork diagram\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system monitoring logs or records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system\n\norganizational personnel with responsibility for the intrusion detection system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for intrusion detection/information system monitoring\n\nautomated mechanisms supporting and/or implementing intrusion detection/information system monitoring capability\n\nautomated mechanisms supporting and/or implementing analysis of communications traffic" - } - ] - } - ] - }, - { - "id": "si-4.12", - "class": "SP800-53-enhancement", - "title": "Automated Alerts", - "params": [ - { - "id": "si-4.12_prm_1", - "label": "organization-defined activities that trigger alerts" - } - ], - "props": [ - { - "name": "label", - "value": "SI-4(12)" - }, - { - "name": "sort-id", - "value": "si-04.12" - } - ], - "parts": [ - { - "id": "si-4.12_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to alert security personnel of the following inappropriate or unusual activities with security implications: {{ insert: param, si-4.12_prm_1 }}." - }, - { - "id": "si-4.12_gdn", - "name": "guidance", - "prose": "This control enhancement focuses on the security alerts generated by organizations and transmitted using automated means. In contrast to the alerts generated by information systems in SI-4 (5), which tend to focus on information sources internal to the systems (e.g., audit records), the sources of information for this enhancement can include other entities as well (e.g., suspicious activity reports, reports on potential insider threats).", - "links": [ - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - } - ] - }, - { - "id": "si-4.12_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-4.12_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(12)[1]" - } - ], - "prose": "defines activities that trigger alerts to security personnel based on inappropriate or unusual activities with security implications; and" - }, - { - "id": "si-4.12_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(12)[2]" - } - ], - "prose": "employs automated mechanisms to alert security personnel of organization-defined activities that trigger alerts based on inappropriate or unusual activities with security implications." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring tools and techniques\n\ninformation system design documentation\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\nlist of inappropriate or unusual activities (with security implications) that trigger alerts\n\nalerts/notifications provided to security personnel\n\ninformation system monitoring logs or records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system\n\norganizational personnel with responsibility for the intrusion detection system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for intrusion detection/information system monitoring\n\nautomated mechanisms supporting and/or implementing intrusion detection/information system monitoring capability\n\nautomated mechanisms supporting and/or implementing automated alerts to security personnel" - } - ] - } - ] - }, - { - "id": "si-4.13", - "class": "SP800-53-enhancement", - "title": "Analyze Traffic / Event Patterns", - "props": [ - { - "name": "label", - "value": "SI-4(13)" - }, - { - "name": "sort-id", - "value": "si-04.13" - } - ], - "parts": [ - { - "id": "si-4.13_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "si-4.13_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Analyzes communications traffic/event patterns for the information system;" - }, - { - "id": "si-4.13_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Develops profiles representing common traffic patterns and/or events; and" - }, - { - "id": "si-4.13_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Uses the traffic/event profiles in tuning system-monitoring devices to reduce the number of false positives and the number of false negatives." - } - ] - }, - { - "id": "si-4.13_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-4.13.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(13)(a)" - } - ], - "prose": "analyzes communications traffic/event patterns for the information system;", - "links": [ - { - "href": "#si-4.13_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "si-4.13.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(13)(b)" - } - ], - "prose": "develops profiles representing common traffic patterns and/or events;", - "links": [ - { - "href": "#si-4.13_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "si-4.13.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(13)(c)" - } - ], - "prose": "uses the traffic/event profiles in tuning system-monitoring devices to reduce the number of false positives and false negatives.", - "links": [ - { - "href": "#si-4.13_smt.c", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring tools and techniques\n\ninformation system design documentation\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\nlist of profiles representing common traffic patterns and/or events\n\ninformation system protocols documentation\n\nlist of acceptable thresholds for false positives and false negatives\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system\n\norganizational personnel with responsibility for the intrusion detection system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for intrusion detection/information system monitoring\n\nautomated mechanisms supporting and/or implementing intrusion detection/information system monitoring capability\n\nautomated mechanisms supporting and/or implementing analysis of communications traffic/event patterns" - } - ] - } - ] - }, - { - "id": "si-4.14", - "class": "SP800-53-enhancement", - "title": "Wireless Intrusion Detection", - "props": [ - { - "name": "label", - "value": "SI-4(14)" - }, - { - "name": "sort-id", - "value": "si-04.14" - } - ], - "parts": [ - { - "id": "si-4.14_smt", - "name": "statement", - "prose": "The organization employs a wireless intrusion detection system to identify rogue wireless devices and to detect attack attempts and potential compromises/breaches to the information system." - }, - { - "id": "si-4.14_gdn", - "name": "guidance", - "prose": "Wireless signals may radiate beyond the confines of organization-controlled facilities. Organizations proactively search for unauthorized wireless connections including the conduct of thorough scans for unauthorized wireless access points. Scans are not limited to those areas within facilities containing information systems, but also include areas outside of facilities as needed, to verify that unauthorized wireless access points are not connected to the systems.", - "links": [ - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - } - ] - }, - { - "id": "si-4.14_obj", - "name": "objective", - "prose": "Determine if the organization employs a wireless intrusion detection system to:", - "parts": [ - { - "id": "si-4.14_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(14)[1]" - } - ], - "prose": "identify rogue wireless devices;" - }, - { - "id": "si-4.14_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(14)[2]" - } - ], - "prose": "detect attack attempts to the information system; and" - }, - { - "id": "si-4.14_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(14)[3]" - } - ], - "prose": "detect potential compromises/breaches to the information system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring tools and techniques\n\ninformation system design documentation\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system protocols\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system\n\norganizational personnel with responsibility for the intrusion detection system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for intrusion detection\n\nautomated mechanisms supporting and/or implementing wireless intrusion detection capability" - } - ] - } - ] - }, - { - "id": "si-4.15", - "class": "SP800-53-enhancement", - "title": "Wireless to Wireline Communications", - "props": [ - { - "name": "label", - "value": "SI-4(15)" - }, - { - "name": "sort-id", - "value": "si-04.15" - } - ], - "parts": [ - { - "id": "si-4.15_smt", - "name": "statement", - "prose": "The organization employs an intrusion detection system to monitor wireless communications traffic as the traffic passes from wireless to wireline networks." - }, - { - "id": "si-4.15_gdn", - "name": "guidance", - "links": [ - { - "href": "#ac-18", - "rel": "related" - } - ] - }, - { - "id": "si-4.15_obj", - "name": "objective", - "prose": "Determine if the organization employs an intrusion detection system to monitor wireless communications traffic as the traffic passes from wireless to wireline networks." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring tools and techniques\n\ninformation system design documentation\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system protocols documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system\n\norganizational personnel with responsibility for the intrusion detection system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for intrusion detection/information system monitoring\n\nautomated mechanisms supporting and/or implementing intrusion detection/information system monitoring capability\n\nautomated mechanisms supporting and/or implementing wireless intrusion detection capability" - } - ] - } - ] - }, - { - "id": "si-4.16", - "class": "SP800-53-enhancement", - "title": "Correlate Monitoring Information", - "props": [ - { - "name": "label", - "value": "SI-4(16)" - }, - { - "name": "sort-id", - "value": "si-04.16" - } - ], - "parts": [ - { - "id": "si-4.16_smt", - "name": "statement", - "prose": "The organization correlates information from monitoring tools employed throughout the information system." - }, - { - "id": "si-4.16_gdn", - "name": "guidance", - "prose": "Correlating information from different monitoring tools can provide a more comprehensive view of information system activity. The correlation of monitoring tools that usually work in isolation (e.g., host monitoring, network monitoring, anti-virus software) can provide an organization-wide view and in so doing, may reveal otherwise unseen attack patterns. Understanding the capabilities/limitations of diverse monitoring tools and how to maximize the utility of information generated by those tools can help organizations to build, operate, and maintain effective monitoring programs.", - "links": [ - { - "href": "#au-6", - "rel": "related" - } - ] - }, - { - "id": "si-4.16_obj", - "name": "objective", - "prose": "Determine if the organization correlates information from monitoring tools employed throughout the information system." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring tools and techniques\n\ninformation system design documentation\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\nevent correlation logs or records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system\n\norganizational personnel with responsibility for the intrusion detection system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for intrusion detection/information system monitoring\n\nautomated mechanisms supporting and/or implementing intrusion detection/information system monitoring capability\n\nautomated mechanisms supporting and/or implementing correlation of information from monitoring tools" - } - ] - } - ] - }, - { - "id": "si-4.17", - "class": "SP800-53-enhancement", - "title": "Integrated Situational Awareness", - "props": [ - { - "name": "label", - "value": "SI-4(17)" - }, - { - "name": "sort-id", - "value": "si-04.17" - } - ], - "parts": [ - { - "id": "si-4.17_smt", - "name": "statement", - "prose": "The organization correlates information from monitoring physical, cyber, and supply chain activities to achieve integrated, organization-wide situational awareness." - }, - { - "id": "si-4.17_gdn", - "name": "guidance", - "prose": "This control enhancement correlates monitoring information from a more diverse set of information sources to achieve integrated situational awareness. Integrated situational awareness from a combination of physical, cyber, and supply chain monitoring activities enhances the capability of organizations to more quickly detect sophisticated cyber attacks and investigate the methods and techniques employed to carry out such attacks. In contrast to SI-4 (16) which correlates the various cyber monitoring information, this control enhancement correlates monitoring beyond just the cyber domain. Such monitoring may help reveal attacks on organizations that are operating across multiple attack vectors.", - "links": [ - { - "href": "#sa-12", - "rel": "related" - } - ] - }, - { - "id": "si-4.17_obj", - "name": "objective", - "prose": "Determine if the organization, to achieve integrated, organization-wide situational awareness, correlates information from monitoring:", - "parts": [ - { - "id": "si-4.17_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(17)[1]" - } - ], - "prose": "physical activities;" - }, - { - "id": "si-4.17_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(17)[2]" - } - ], - "prose": "cyber activities; and" - }, - { - "id": "si-4.17_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(17)[3]" - } - ], - "prose": "supply chain activities." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring tools and techniques\n\ninformation system design documentation\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\nevent correlation logs or records resulting from physical, cyber, and supply chain activities\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system\n\norganizational personnel with responsibility for the intrusion detection system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for intrusion detection/information system monitoring\n\nautomated mechanisms supporting and/or implementing intrusion detection/system monitoring capability\n\nautomated mechanisms supporting and/or implementing correlation of information from monitoring tools" - } - ] - } - ] - }, - { - "id": "si-4.18", - "class": "SP800-53-enhancement", - "title": "Analyze Traffic / Covert Exfiltration", - "params": [ - { - "id": "si-4.18_prm_1", - "label": "organization-defined interior points within the system (e.g., subsystems, subnetworks)" - } - ], - "props": [ - { - "name": "label", - "value": "SI-4(18)" - }, - { - "name": "sort-id", - "value": "si-04.18" - } - ], - "parts": [ - { - "id": "si-4.18_smt", - "name": "statement", - "prose": "The organization analyzes outbound communications traffic at the external boundary of the information system (i.e., system perimeter) and at {{ insert: param, si-4.18_prm_1 }} to detect covert exfiltration of information." - }, - { - "id": "si-4.18_gdn", - "name": "guidance", - "prose": "Covert means that can be used for the unauthorized exfiltration of organizational information include, for example, steganography." - }, - { - "id": "si-4.18_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-4.18_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(18)[1]" - } - ], - "prose": "defines interior points within the system (e.g., subsystems, subnetworks) where communications traffic is to be analyzed;" - }, - { - "id": "si-4.18_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(18)[2]" - } - ], - "prose": "to detect covert exfiltration of information, analyzes outbound communications traffic at:", - "parts": [ - { - "id": "si-4.18_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(18)[2][a]" - } - ], - "prose": "the external boundary of the information system (i.e., system perimeter); and" - }, - { - "id": "si-4.18_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(18)[2][b]" - } - ], - "prose": "organization-defined interior points within the system." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring tools and techniques\n\ninformation system design documentation\n\nnetwork diagram\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system monitoring logs or records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system\n\norganizational personnel with responsibility for the intrusion detection system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for intrusion detection/information system monitoring\n\nautomated mechanisms supporting and/or implementing intrusion detection/system monitoring capability\n\nautomated mechanisms supporting and/or implementing analysis of outbound communications traffic" - } - ] - } - ] - }, - { - "id": "si-4.19", - "class": "SP800-53-enhancement", - "title": "Individuals Posing Greater Risk", - "params": [ - { - "id": "si-4.19_prm_1", - "label": "organization-defined additional monitoring" - }, - { - "id": "si-4.19_prm_2", - "label": "organization-defined sources" - } - ], - "props": [ - { - "name": "label", - "value": "SI-4(19)" - }, - { - "name": "sort-id", - "value": "si-04.19" - } - ], - "parts": [ - { - "id": "si-4.19_smt", - "name": "statement", - "prose": "The organization implements {{ insert: param, si-4.19_prm_1 }} of individuals who have been identified by {{ insert: param, si-4.19_prm_2 }} as posing an increased level of risk." - }, - { - "id": "si-4.19_gdn", - "name": "guidance", - "prose": "Indications of increased risk from individuals can be obtained from a variety of sources including, for example, human resource records, intelligence agencies, law enforcement organizations, and/or other credible sources. The monitoring of individuals is closely coordinated with management, legal, security, and human resources officials within organizations conducting such monitoring and complies with federal legislation, Executive Orders, policies, directives, regulations, and standards." - }, - { - "id": "si-4.19_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-4.19_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(19)[1]" - } - ], - "prose": "defines sources that identify individuals who pose an increased level of risk;" - }, - { - "id": "si-4.19_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(19)[2]" - } - ], - "prose": "defines additional monitoring to be implemented on individuals who have been identified by organization-defined sources as posing an increased level of risk; and" - }, - { - "id": "si-4.19_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(19)[3]" - } - ], - "prose": "implements organization-defined additional monitoring of individuals who have been identified by organization-defined sources as posing an increased level of risk." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring\n\ninformation system design documentation\n\nlist of individuals who have been identified as posing an increased level of risk\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for information system monitoring\n\nautomated mechanisms supporting and/or implementing system monitoring capability" - } - ] - } - ] - }, - { - "id": "si-4.20", - "class": "SP800-53-enhancement", - "title": "Privileged Users", - "params": [ - { - "id": "si-4.20_prm_1", - "label": "organization-defined additional monitoring" - } - ], - "props": [ - { - "name": "label", - "value": "SI-4(20)" - }, - { - "name": "sort-id", - "value": "si-04.20" - } - ], - "parts": [ - { - "id": "si-4.20_smt", - "name": "statement", - "prose": "The organization implements {{ insert: param, si-4.20_prm_1 }} of privileged users." - }, - { - "id": "si-4.20_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-4.20_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(20)[1]" - } - ], - "prose": "defines additional monitoring to be implemented on privileged users; and" - }, - { - "id": "si-4.20_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(20)[2]" - } - ], - "prose": "implements organization-defined additional monitoring of privileged users;" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring tools and techniques\n\ninformation system design documentation\n\nlist of privileged users\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system monitoring logs or records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for information system monitoring\n\nautomated mechanisms supporting and/or implementing system monitoring capability" - } - ] - } - ] - }, - { - "id": "si-4.21", - "class": "SP800-53-enhancement", - "title": "Probationary Periods", - "params": [ - { - "id": "si-4.21_prm_1", - "label": "organization-defined additional monitoring" - }, - { - "id": "si-4.21_prm_2", - "label": "organization-defined probationary period" - } - ], - "props": [ - { - "name": "label", - "value": "SI-4(21)" - }, - { - "name": "sort-id", - "value": "si-04.21" - } - ], - "parts": [ - { - "id": "si-4.21_smt", - "name": "statement", - "prose": "The organization implements {{ insert: param, si-4.21_prm_1 }} of individuals during {{ insert: param, si-4.21_prm_2 }}." - }, - { - "id": "si-4.21_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-4.21_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(21)[1]" - } - ], - "prose": "defines additional monitoring to be implemented on individuals during probationary periods;" - }, - { - "id": "si-4.21_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(21)[2]" - } - ], - "prose": "defines probationary period during which organization-defined additional monitoring of individuals is to be performed; and" - }, - { - "id": "si-4.21_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(21)[3]" - } - ], - "prose": "implements organization-defined additional monitoring of individuals during organization-defined probationary period." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring\n\ninformation system design documentation\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system monitoring logs or records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for information system monitoring\n\nautomated mechanisms supporting and/or implementing system monitoring capability" - } - ] - } - ] - }, - { - "id": "si-4.22", - "class": "SP800-53-enhancement", - "title": "Unauthorized Network Services", - "params": [ - { - "id": "si-4.22_prm_1", - "label": "organization-defined authorization or approval processes" - }, - { - "id": "si-4.22_prm_2", - "select": { - "how-many": "one-or-more", - "choice": [ - "audits", - "alerts {{ insert: param, si-4.22_prm_3 }} " - ] - } - }, - { - "id": "si-4.22_prm_3", - "depends-on": "si-4.22_prm_2", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "SI-4(22)" - }, - { - "name": "sort-id", - "value": "si-04.22" - } - ], - "parts": [ - { - "id": "si-4.22_smt", - "name": "statement", - "prose": "The information system detects network services that have not been authorized or approved by {{ insert: param, si-4.22_prm_1 }} and {{ insert: param, si-4.22_prm_2 }}." - }, - { - "id": "si-4.22_gdn", - "name": "guidance", - "prose": "Unauthorized or unapproved network services include, for example, services in service-oriented architectures that lack organizational verification or validation and therefore may be unreliable or serve as malicious rogues for valid services.", - "links": [ - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - } - ] - }, - { - "id": "si-4.22_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "si-4.22_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(22)[1]" - } - ], - "prose": "the organization defines authorization or approval processes for network services;" - }, - { - "id": "si-4.22_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(22)[2]" - } - ], - "prose": "the organization defines personnel or roles to be alerted upon detection of network services that have not been authorized or approved by organization-defined authorization or approval processes;" - }, - { - "id": "si-4.22_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(22)[3]" - } - ], - "prose": "the information system detects network services that have not been authorized or approved by organization-defined authorization or approval processes and does one or more of the following:", - "parts": [ - { - "id": "si-4.22_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(22)[3][a]" - } - ], - "prose": "audits; and/or" - }, - { - "id": "si-4.22_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(22)[3][b]" - } - ], - "prose": "alerts organization-defined personnel or roles." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring tools and techniques\n\ninformation system design documentation\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\ndocumented authorization/approval of network services\n\nnotifications or alerts of unauthorized network services\n\ninformation system monitoring logs or records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring the information system" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for information system monitoring\n\nautomated mechanisms supporting and/or implementing system monitoring capability\n\nautomated mechanisms for auditing network services\n\nautomated mechanisms for providing alerts" - } - ] - } - ] - }, - { - "id": "si-4.23", - "class": "SP800-53-enhancement", - "title": "Host-based Devices", - "params": [ - { - "id": "si-4.23_prm_1", - "label": "organization-defined host-based monitoring mechanisms" - }, - { - "id": "si-4.23_prm_2", - "label": "organization-defined information system components" - } - ], - "props": [ - { - "name": "label", - "value": "SI-4(23)" - }, - { - "name": "sort-id", - "value": "si-04.23" - } - ], - "parts": [ - { - "id": "si-4.23_smt", - "name": "statement", - "prose": "The organization implements {{ insert: param, si-4.23_prm_1 }} at {{ insert: param, si-4.23_prm_2 }}." - }, - { - "id": "si-4.23_gdn", - "name": "guidance", - "prose": "Information system components where host-based monitoring can be implemented include, for example, servers, workstations, and mobile devices. Organizations consider employing host-based monitoring mechanisms from multiple information technology product developers." - }, - { - "id": "si-4.23_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-4.23_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(23)[1]" - } - ], - "prose": "defines host-based monitoring mechanisms to be implemented;" - }, - { - "id": "si-4.23_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(23)[2]" - } - ], - "prose": "defines information system components where organization-defined host-based monitoring is to be implemented; and" - }, - { - "id": "si-4.23_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(23)[3]" - } - ], - "prose": "implements organization-defined host-based monitoring mechanisms at organization-defined information system components." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring tools and techniques\n\ninformation system design documentation\n\nhost-based monitoring mechanisms\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\nlist of information system components requiring host-based monitoring\n\ninformation system monitoring logs or records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring information system hosts" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for information system monitoring\n\nautomated mechanisms supporting and/or implementing host-based monitoring capability" - } - ] - } - ] - }, - { - "id": "si-4.24", - "class": "SP800-53-enhancement", - "title": "Indicators of Compromise", - "props": [ - { - "name": "label", - "value": "SI-4(24)" - }, - { - "name": "sort-id", - "value": "si-04.24" - } - ], - "parts": [ - { - "id": "si-4.24_smt", - "name": "statement", - "prose": "The information system discovers, collects, distributes, and uses indicators of compromise." - }, - { - "id": "si-4.24_gdn", - "name": "guidance", - "prose": "Indicators of compromise (IOC) are forensic artifacts from intrusions that are identified on organizational information systems (at the host or network level). IOCs provide organizations with valuable information on objects or information systems that have been compromised. IOCs for the discovery of compromised hosts can include for example, the creation of registry key values. IOCs for network traffic include, for example, Universal Resource Locator (URL) or protocol elements that indicate malware command and control servers. The rapid distribution and adoption of IOCs can improve information security by reducing the time that information systems and organizations are vulnerable to the same exploit or attack." - }, - { - "id": "si-4.24_obj", - "name": "objective", - "prose": "Determine if the information system:", - "parts": [ - { - "id": "si-4.24_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(24)[1]" - } - ], - "prose": "discovers indicators of compromise;" - }, - { - "id": "si-4.24_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(24)[2]" - } - ], - "prose": "collects indicators of compromise;" - }, - { - "id": "si-4.24_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(24)[3]" - } - ], - "prose": "distributes indicators of compromise; and" - }, - { - "id": "si-4.24_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-4(24)[4]" - } - ], - "prose": "uses indicators of compromise." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system monitoring\n\ninformation system design documentation\n\ninformation system monitoring tools and techniques documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system monitoring logs or records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel installing, configuring, and/or maintaining the information system\n\norganizational personnel with responsibility for monitoring information system hosts" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for information system monitoring\n\norganizational processes for discovery, collection, distribution, and use of indicators of compromise\n\nautomated mechanisms supporting and/or implementing system monitoring capability\n\nautomated mechanisms supporting and/or implementing the discovery, collection, distribution, and use of indicators of compromise" - } - ] - } - ] - } - ] - }, - { - "id": "si-5", - "class": "SP800-53", - "title": "Security Alerts, Advisories, and Directives", - "params": [ - { - "id": "si-5_prm_1", - "label": "organization-defined external organizations" - }, - { - "id": "si-5_prm_2", - "select": { - "how-many": "one-or-more", - "choice": [ - " {{ insert: param, si-5_prm_3 }} ", - " {{ insert: param, si-5_prm_4 }} ", - " {{ insert: param, si-5_prm_5 }} " - ] - } - }, - { - "id": "si-5_prm_3", - "depends-on": "si-5_prm_2", - "label": "organization-defined personnel or roles" - }, - { - "id": "si-5_prm_4", - "depends-on": "si-5_prm_2", - "label": "organization-defined elements within the organization" - }, - { - "id": "si-5_prm_5", - "depends-on": "si-5_prm_2", - "label": "organization-defined external organizations" - } - ], - "props": [ - { - "name": "label", - "value": "SI-5" - }, - { - "name": "sort-id", - "value": "si-05" - } - ], - "links": [ - { - "href": "#bdd14f6c-41ab-4277-8d74-a0ce75a0eb1d", - "rel": "reference" - } - ], - "parts": [ - { - "id": "si-5_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "si-5_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Receives information system security alerts, advisories, and directives from {{ insert: param, si-5_prm_1 }} on an ongoing basis;" - }, - { - "id": "si-5_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Generates internal security alerts, advisories, and directives as deemed necessary;" - }, - { - "id": "si-5_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Disseminates security alerts, advisories, and directives to: {{ insert: param, si-5_prm_2 }}; and" - }, - { - "id": "si-5_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Implements security directives in accordance with established time frames, or notifies the issuing organization of the degree of noncompliance." - } - ] - }, - { - "id": "si-5_gdn", - "name": "guidance", - "prose": "The United States Computer Emergency Readiness Team (US-CERT) generates security alerts and advisories to maintain situational awareness across the federal government. Security directives are issued by OMB or other designated organizations with the responsibility and authority to issue such directives. Compliance to security directives is essential due to the critical nature of many of these directives and the potential immediate adverse effects on organizational operations and assets, individuals, other organizations, and the Nation should the directives not be implemented in a timely manner. External organizations include, for example, external mission/business partners, supply chain partners, external service providers, and other peer/supporting organizations.", - "links": [ - { - "href": "#si-2", - "rel": "related" - } - ] - }, - { - "id": "si-5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-5.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-5(a)" - } - ], - "parts": [ - { - "id": "si-5.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-5(a)[1]" - } - ], - "prose": "defines external organizations from whom information system security alerts, advisories and directives are to be received;" - }, - { - "id": "si-5.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-5(a)[2]" - } - ], - "prose": "receives information system security alerts, advisories, and directives from organization-defined external organizations on an ongoing basis;" - } - ] - }, - { - "id": "si-5.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-5(b)" - } - ], - "prose": "generates internal security alerts, advisories, and directives as deemed necessary;" - }, - { - "id": "si-5.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-5(c)" - } - ], - "parts": [ - { - "id": "si-5.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-5(c)[1]" - } - ], - "prose": "defines personnel or roles to whom security alerts, advisories, and directives are to be provided;" - }, - { - "id": "si-5.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-5(c)[2]" - } - ], - "prose": "defines elements within the organization to whom security alerts, advisories, and directives are to be provided;" - }, - { - "id": "si-5.c_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-5(c)[3]" - } - ], - "prose": "defines external organizations to whom security alerts, advisories, and directives are to be provided;" - }, - { - "id": "si-5.c_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-5(c)[4]" - } - ], - "prose": "disseminates security alerts, advisories, and directives to one or more of the following:", - "parts": [ - { - "id": "si-5.c_obj.4.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-5(c)[4][a]" - } - ], - "prose": "organization-defined personnel or roles;" - }, - { - "id": "si-5.c_obj.4.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-5(c)[4][b]" - } - ], - "prose": "organization-defined elements within the organization; and/or" - }, - { - "id": "si-5.c_obj.4.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-5(c)[4][c]" - } - ], - "prose": "organization-defined external organizations; and" - } - ] - } - ] - }, - { - "id": "si-5.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-5(d)" - } - ], - "parts": [ - { - "id": "si-5.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-5(d)[1]" - } - ], - "prose": "implements security directives in accordance with established time frames; or" - }, - { - "id": "si-5.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-5(d)[2]" - } - ], - "prose": "notifies the issuing organization of the degree of noncompliance." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing security alerts, advisories, and directives\n\nrecords of security alerts and advisories\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security alert and advisory responsibilities\n\norganizational personnel implementing, operating, maintaining, and using the information system\n\norganizational personnel, organizational elements, and/or external organizations to whom alerts, advisories, and directives are to be disseminated\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for defining, receiving, generating, disseminating, and complying with security alerts, advisories, and directives\n\nautomated mechanisms supporting and/or implementing definition, receipt, generation, and dissemination of security alerts, advisories, and directives\n\nautomated mechanisms supporting and/or implementing security directives" - } - ] - } - ], - "controls": [ - { - "id": "si-5.1", - "class": "SP800-53-enhancement", - "title": "Automated Alerts and Advisories", - "props": [ - { - "name": "label", - "value": "SI-5(1)" - }, - { - "name": "sort-id", - "value": "si-05.01" - } - ], - "parts": [ - { - "id": "si-5.1_smt", - "name": "statement", - "prose": "The organization employs automated mechanisms to make security alert and advisory information available throughout the organization." - }, - { - "id": "si-5.1_gdn", - "name": "guidance", - "prose": "The significant number of changes to organizational information systems and the environments in which those systems operate requires the dissemination of security-related information to a variety of organizational entities that have a direct interest in the success of organizational missions and business functions. Based on the information provided by the security alerts and advisories, changes may be required at one or more of the three tiers related to the management of information security risk including the governance level, mission/business process/enterprise architecture level, and the information system level." - }, - { - "id": "si-5.1_obj", - "name": "objective", - "prose": "Determine if the organization employs automated mechanisms to make security alert and advisory information available throughout the organization." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing security alerts, advisories, and directives\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nautomated mechanisms supporting the distribution of security alert and advisory information\n\nrecords of security alerts and advisories\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security alert and advisory responsibilities\n\norganizational personnel implementing, operating, maintaining, and using the information system\n\norganizational personnel, organizational elements, and/or external organizations to whom alerts and advisories are to be disseminated\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for defining, receiving, generating, and disseminating security alerts and advisories\n\nautomated mechanisms supporting and/or implementing dissemination of security alerts and advisories" - } - ] - } - ] - } - ] - }, - { - "id": "si-6", - "class": "SP800-53", - "title": "Security Function Verification", - "params": [ - { - "id": "si-6_prm_1", - "label": "organization-defined security functions" - }, - { - "id": "si-6_prm_2", - "select": { - "how-many": "one-or-more", - "choice": [ - " {{ insert: param, si-6_prm_3 }} ", - "upon command by user with appropriate privilege", - " {{ insert: param, si-6_prm_4 }} " - ] - } - }, - { - "id": "si-6_prm_3", - "depends-on": "si-6_prm_2", - "label": "organization-defined system transitional states" - }, - { - "id": "si-6_prm_4", - "depends-on": "si-6_prm_2", - "label": "organization-defined frequency" - }, - { - "id": "si-6_prm_5", - "label": "organization-defined personnel or roles" - }, - { - "id": "si-6_prm_6", - "select": { - "how-many": "one-or-more", - "choice": [ - "shuts the information system down", - "restarts the information system", - " {{ insert: param, si-6_prm_7 }} " - ] - } - }, - { - "id": "si-6_prm_7", - "depends-on": "si-6_prm_6", - "label": "organization-defined alternative action(s)" - } - ], - "props": [ - { - "name": "label", - "value": "SI-6" - }, - { - "name": "sort-id", - "value": "si-06" - } - ], - "parts": [ - { - "id": "si-6_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "si-6_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Verifies the correct operation of {{ insert: param, si-6_prm_1 }};" - }, - { - "id": "si-6_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Performs this verification {{ insert: param, si-6_prm_2 }};" - }, - { - "id": "si-6_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Notifies {{ insert: param, si-6_prm_5 }} of failed security verification tests; and" - }, - { - "id": "si-6_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": " {{ insert: param, si-6_prm_6 }} when anomalies are discovered." - } - ] - }, - { - "id": "si-6_gdn", - "name": "guidance", - "prose": "Transitional states for information systems include, for example, system startup, restart, shutdown, and abort. Notifications provided by information systems include, for example, electronic alerts to system administrators, messages to local computer consoles, and/or hardware indications such as lights.", - "links": [ - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - } - ] - }, - { - "id": "si-6_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "si-6.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(a)" - } - ], - "parts": [ - { - "id": "si-6.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(a)[1]" - } - ], - "prose": "the organization defines security functions to be verified for correct operation;" - }, - { - "id": "si-6.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(a)[2]" - } - ], - "prose": "the information system verifies the correct operation of organization-defined security functions;" - } - ] - }, - { - "id": "si-6.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(b)" - } - ], - "parts": [ - { - "id": "si-6.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(b)[1]" - } - ], - "prose": "the organization defines system transitional states requiring verification of organization-defined security functions;" - }, - { - "id": "si-6.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(b)[2]" - } - ], - "prose": "the organization defines a frequency to verify the correct operation of organization-defined security functions;" - }, - { - "id": "si-6.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(b)[3]" - } - ], - "prose": "the information system performs this verification one or more of the following:", - "parts": [ - { - "id": "si-6.b_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(b)[3][a]" - } - ], - "prose": "at organization-defined system transitional states;" - }, - { - "id": "si-6.b_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(b)[3][b]" - } - ], - "prose": "upon command by user with appropriate privilege; and/or" - }, - { - "id": "si-6.b_obj.3.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(b)[3][c]" - } - ], - "prose": "with the organization-defined frequency;" - } - ] - } - ] - }, - { - "id": "si-6.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(c)" - } - ], - "parts": [ - { - "id": "si-6.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(c)[1]" - } - ], - "prose": "the organization defines personnel or roles to be notified of failed security verification tests;" - }, - { - "id": "si-6.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(c)[2]" - } - ], - "prose": "the information system notifies organization-defined personnel or roles of failed security verification tests;" - } - ] - }, - { - "id": "si-6.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(d)" - } - ], - "parts": [ - { - "id": "si-6.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(d)[1]" - } - ], - "prose": "the organization defines alternative action(s) to be performed when anomalies are discovered;" - }, - { - "id": "si-6.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(d)[2]" - } - ], - "prose": "the information system performs one or more of the following actions when anomalies are discovered:", - "parts": [ - { - "id": "si-6.d_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(d)[2][a]" - } - ], - "prose": "shuts the information system down;" - }, - { - "id": "si-6.d_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(d)[2][b]" - } - ], - "prose": "restarts the information system; and/or" - }, - { - "id": "si-6.d_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(d)[2][c]" - } - ], - "prose": "performs organization-defined alternative action(s)." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing security function verification\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nalerts/notifications of failed security verification tests\n\nlist of system transition states requiring security functionality verification\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security function verification responsibilities\n\norganizational personnel implementing, operating, and maintaining the information system\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for security function verification\n\nautomated mechanisms supporting and/or implementing security function verification capability" - } - ] - } - ], - "controls": [ - { - "id": "si-6.1", - "class": "SP800-53-enhancement", - "title": "Notification of Failed Security Tests", - "props": [ - { - "name": "label", - "value": "SI-6(1)" - }, - { - "name": "sort-id", - "value": "si-06.01" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#si-6", - "rel": "incorporated-into" - } - ] - }, - { - "id": "si-6.2", - "class": "SP800-53-enhancement", - "title": "Automation Support for Distributed Testing", - "props": [ - { - "name": "label", - "value": "SI-6(2)" - }, - { - "name": "sort-id", - "value": "si-06.02" - } - ], - "parts": [ - { - "id": "si-6.2_smt", - "name": "statement", - "prose": "The information system implements automated mechanisms to support the management of distributed security testing." - }, - { - "id": "si-6.2_gdn", - "name": "guidance", - "links": [ - { - "href": "#si-2", - "rel": "related" - } - ] - }, - { - "id": "si-6.2_obj", - "name": "objective", - "prose": "Determine if the information system implements automated mechanisms to support the management of distributed security testing." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing security function verification\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security function verification responsibilities\n\norganizational personnel implementing, operating, and maintaining the information system\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for security function verification\n\nautomated mechanisms supporting and/or implementing the management of distributed security testing" - } - ] - } - ] - }, - { - "id": "si-6.3", - "class": "SP800-53-enhancement", - "title": "Report Verification Results", - "params": [ - { - "id": "si-6.3_prm_1", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "SI-6(3)" - }, - { - "name": "sort-id", - "value": "si-06.03" - } - ], - "parts": [ - { - "id": "si-6.3_smt", - "name": "statement", - "prose": "The organization reports the results of security function verification to {{ insert: param, si-6.3_prm_1 }}." - }, - { - "id": "si-6.3_gdn", - "name": "guidance", - "prose": "Organizational personnel with potential interest in security function verification results include, for example, senior information security officers, information system security managers, and information systems security officers.", - "links": [ - { - "href": "#sa-12", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-5", - "rel": "related" - } - ] - }, - { - "id": "si-6.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-6.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(3)[1]" - } - ], - "prose": "defines personnel or roles designated to receive the results of security function verification; and" - }, - { - "id": "si-6.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-6(3)[2]" - } - ], - "prose": "reports the results of security function verification to organization-defined personnel or roles." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing security function verification\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nrecords of security function verification results\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with security function verification responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for reporting security function verification results\n\nautomated mechanisms supporting and/or implementing the reporting of security function verification results" - } - ] - } - ] - } - ] - }, - { - "id": "si-7", - "class": "SP800-53", - "title": "Software, Firmware, and Information Integrity", - "params": [ - { - "id": "si-7_prm_1", - "label": "organization-defined software, firmware, and information" - } - ], - "props": [ - { - "name": "label", - "value": "SI-7" - }, - { - "name": "sort-id", - "value": "si-07" - } - ], - "links": [ - { - "href": "#6bf8d24a-78dc-4727-a2ac-0e64d71c495c", - "rel": "reference" - }, - { - "href": "#3878cc04-144a-483e-af62-8fe6f4ad6c7a", - "rel": "reference" - } - ], - "parts": [ - { - "id": "si-7_smt", - "name": "statement", - "prose": "The organization employs integrity verification tools to detect unauthorized changes to {{ insert: param, si-7_prm_1 }}." - }, - { - "id": "si-7_gdn", - "name": "guidance", - "prose": "Unauthorized changes to software, firmware, and information can occur due to errors or malicious activity (e.g., tampering). Software includes, for example, operating systems (with key internal components such as kernels, drivers), middleware, and applications. Firmware includes, for example, the Basic Input Output System (BIOS). Information includes metadata such as security attributes associated with information. State-of-the-practice integrity-checking mechanisms (e.g., parity checks, cyclical redundancy checks, cryptographic hashes) and associated tools can automatically monitor the integrity of information systems and hosted applications.", - "links": [ - { - "href": "#sa-12", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - } - ] - }, - { - "id": "si-7_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-7_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7[1]" - } - ], - "parts": [ - { - "id": "si-7_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7[1][a]" - } - ], - "prose": "defines software requiring integrity verification tools to be employed to detect unauthorized changes;" - }, - { - "id": "si-7_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7[1][b]" - } - ], - "prose": "defines firmware requiring integrity verification tools to be employed to detect unauthorized changes;" - }, - { - "id": "si-7_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7[1][c]" - } - ], - "prose": "defines information requiring integrity verification tools to be employed to detect unauthorized changes;" - } - ] - }, - { - "id": "si-7_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7[2]" - } - ], - "prose": "employs integrity verification tools to detect unauthorized changes to organization-defined:", - "parts": [ - { - "id": "si-7_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7[2][a]" - } - ], - "prose": "software;" - }, - { - "id": "si-7_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7[2][b]" - } - ], - "prose": "firmware; and" - }, - { - "id": "si-7_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7[2][c]" - } - ], - "prose": "information." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing software, firmware, and information integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nintegrity verification tools and associated documentation\n\nrecords generated/triggered from integrity verification tools regarding unauthorized software, firmware, and information changes\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for software, firmware, and/or information integrity\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Software, firmware, and information integrity verification tools" - } - ] - } - ], - "controls": [ - { - "id": "si-7.1", - "class": "SP800-53-enhancement", - "title": "Integrity Checks", - "params": [ - { - "id": "si-7.1_prm_1", - "label": "organization-defined software, firmware, and information" - }, - { - "id": "si-7.1_prm_2", - "select": { - "how-many": "one-or-more", - "choice": [ - "at startup", - "at {{ insert: param, si-7.1_prm_3 }} ", - " {{ insert: param, si-7.1_prm_4 }} " - ] - } - }, - { - "id": "si-7.1_prm_3", - "depends-on": "si-7.1_prm_2", - "label": "organization-defined transitional states or security-relevant events" - }, - { - "id": "si-7.1_prm_4", - "depends-on": "si-7.1_prm_2", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "SI-7(1)" - }, - { - "name": "sort-id", - "value": "si-07.01" - } - ], - "parts": [ - { - "id": "si-7.1_smt", - "name": "statement", - "prose": "The information system performs an integrity check of {{ insert: param, si-7.1_prm_1 }} {{ insert: param, si-7.1_prm_2 }}." - }, - { - "id": "si-7.1_gdn", - "name": "guidance", - "prose": "Security-relevant events include, for example, the identification of a new threat to which organizational information systems are susceptible, and the installation of new hardware, software, or firmware. Transitional states include, for example, system startup, restart, shutdown, and abort." - }, - { - "id": "si-7.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "si-7.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(1)[1]" - } - ], - "prose": "the organization defines:", - "parts": [ - { - "id": "si-7.1_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(1)[1][a]" - } - ], - "prose": "software requiring integrity checks to be performed;" - }, - { - "id": "si-7.1_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(1)[1][b]" - } - ], - "prose": "firmware requiring integrity checks to be performed;" - }, - { - "id": "si-7.1_obj.1.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(1)[1][c]" - } - ], - "prose": "information requiring integrity checks to be performed;" - } - ] - }, - { - "id": "si-7.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(1)[2]" - } - ], - "prose": "the organization defines transitional states or security-relevant events requiring integrity checks of organization-defined:", - "parts": [ - { - "id": "si-7.1_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(1)[2][a]" - } - ], - "prose": "software;" - }, - { - "id": "si-7.1_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(1)[2][b]" - } - ], - "prose": "firmware;" - }, - { - "id": "si-7.1_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(1)[2][c]" - } - ], - "prose": "information;" - } - ] - }, - { - "id": "si-7.1_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(1)[3]" - } - ], - "prose": "the organization defines a frequency with which to perform an integrity check of organization-defined:", - "parts": [ - { - "id": "si-7.1_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(1)[3][a]" - } - ], - "prose": "software;" - }, - { - "id": "si-7.1_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(1)[3][b]" - } - ], - "prose": "firmware;" - }, - { - "id": "si-7.1_obj.3.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(1)[3][c]" - } - ], - "prose": "information;" - } - ] - }, - { - "id": "si-7.1_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(1)[4]" - } - ], - "prose": "the information system performs an integrity check of organization-defined software, firmware, and information one or more of the following:", - "parts": [ - { - "id": "si-7.1_obj.4.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(1)[4][a]" - } - ], - "prose": "at startup;" - }, - { - "id": "si-7.1_obj.4.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(1)[4][b]" - } - ], - "prose": "at organization-defined transitional states or security-relevant events; and/or" - }, - { - "id": "si-7.1_obj.4.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(1)[4][c]" - } - ], - "prose": "with the organization-defined frequency." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing software, firmware, and information integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nintegrity verification tools and associated documentation\n\nrecords of integrity scans\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for software, firmware, and/or information integrity\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Software, firmware, and information integrity verification tools" - } - ] - } - ] - }, - { - "id": "si-7.2", - "class": "SP800-53-enhancement", - "title": "Automated Notifications of Integrity Violations", - "params": [ - { - "id": "si-7.2_prm_1", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "SI-7(2)" - }, - { - "name": "sort-id", - "value": "si-07.02" - } - ], - "parts": [ - { - "id": "si-7.2_smt", - "name": "statement", - "prose": "The organization employs automated tools that provide notification to {{ insert: param, si-7.2_prm_1 }} upon discovering discrepancies during integrity verification." - }, - { - "id": "si-7.2_gdn", - "name": "guidance", - "prose": "The use of automated tools to report integrity violations and to notify organizational personnel in a timely matter is an essential precursor to effective risk response. Personnel having an interest in integrity violations include, for example, mission/business owners, information system owners, systems administrators, software developers, systems integrators, and information security officers." - }, - { - "id": "si-7.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-7.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(2)[1]" - } - ], - "prose": "defines personnel or roles to whom notification is to be provided upon discovering discrepancies during integrity verification; and" - }, - { - "id": "si-7.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(2)[2]" - } - ], - "prose": "employs automated tools that provide notification to organization-defined personnel or roles upon discovering discrepancies during integrity verification." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing software, firmware, and information integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nintegrity verification tools and associated documentation\n\nrecords of integrity scans\n\nautomated tools supporting alerts and notifications for integrity discrepancies\n\nalerts/notifications provided upon discovering discrepancies during integrity verifications\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for software, firmware, and/or information integrity\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Software, firmware, and information integrity verification tools\n\nautomated mechanisms providing integrity discrepancy notifications" - } - ] - } - ] - }, - { - "id": "si-7.3", - "class": "SP800-53-enhancement", - "title": "Centrally-managed Integrity Tools", - "props": [ - { - "name": "label", - "value": "SI-7(3)" - }, - { - "name": "sort-id", - "value": "si-07.03" - } - ], - "parts": [ - { - "id": "si-7.3_smt", - "name": "statement", - "prose": "The organization employs centrally managed integrity verification tools." - }, - { - "id": "si-7.3_gdn", - "name": "guidance", - "links": [ - { - "href": "#au-3", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - }, - { - "href": "#si-8", - "rel": "related" - } - ] - }, - { - "id": "si-7.3_obj", - "name": "objective", - "prose": "Determine if the organization employs centrally managed integrity verification tools." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing software, firmware, and information integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nintegrity verification tools and associated documentation\n\nrecords of integrity scans\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for central management of integrity verification tools\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing central management of integrity verification tools" - } - ] - } - ] - }, - { - "id": "si-7.4", - "class": "SP800-53-enhancement", - "title": "Tamper-evident Packaging", - "props": [ - { - "name": "label", - "value": "SI-7(4)" - }, - { - "name": "sort-id", - "value": "si-07.04" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#sa-12", - "rel": "incorporated-into" - } - ] - }, - { - "id": "si-7.5", - "class": "SP800-53-enhancement", - "title": "Automated Response to Integrity Violations", - "params": [ - { - "id": "si-7.5_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "shuts the information system down", - "restarts the information system", - "implements {{ insert: param, si-7.5_prm_2 }} " - ] - } - }, - { - "id": "si-7.5_prm_2", - "depends-on": "si-7.5_prm_1", - "label": "organization-defined security safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "SI-7(5)" - }, - { - "name": "sort-id", - "value": "si-07.05" - } - ], - "parts": [ - { - "id": "si-7.5_smt", - "name": "statement", - "prose": "The information system automatically {{ insert: param, si-7.5_prm_1 }} when integrity violations are discovered." - }, - { - "id": "si-7.5_gdn", - "name": "guidance", - "prose": "Organizations may define different integrity checking and anomaly responses: (i) by type of information (e.g., firmware, software, user data); (ii) by specific information (e.g., boot firmware, boot firmware for a specific types of machines); or (iii) a combination of both. Automatic implementation of specific safeguards within organizational information systems includes, for example, reversing the changes, halting the information system, or triggering audit alerts when unauthorized modifications to critical security files occur." - }, - { - "id": "si-7.5_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "si-7.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(5)[1]" - } - ], - "prose": "the organization defines security safeguards to be implemented when integrity violations are discovered;" - }, - { - "id": "si-7.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(5)[2]" - } - ], - "prose": "the information system automatically performs one or more of the following actions when integrity violations are discovered:", - "parts": [ - { - "id": "si-7.5_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(5)[2][a]" - } - ], - "prose": "shuts the information system down;" - }, - { - "id": "si-7.5_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(5)[2][b]" - } - ], - "prose": "restarts the information system; and/or" - }, - { - "id": "si-7.5_obj.2.c", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(5)[2][c]" - } - ], - "prose": "implements the organization-defined security safeguards." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing software, firmware, and information integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nintegrity verification tools and associated documentation\n\nrecords of integrity scans\n\nrecords of integrity checks and responses to integrity violations\n\ninformation audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for software, firmware, and/or information integrity\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Software, firmware, and information integrity verification tools\n\nautomated mechanisms providing an automated response to integrity violations\n\nautomated mechanisms supporting and/or implementing security safeguards to be implemented when integrity violations are discovered" - } - ] - } - ] - }, - { - "id": "si-7.6", - "class": "SP800-53-enhancement", - "title": "Cryptographic Protection", - "props": [ - { - "name": "label", - "value": "SI-7(6)" - }, - { - "name": "sort-id", - "value": "si-07.06" - } - ], - "parts": [ - { - "id": "si-7.6_smt", - "name": "statement", - "prose": "The information system implements cryptographic mechanisms to detect unauthorized changes to software, firmware, and information." - }, - { - "id": "si-7.6_gdn", - "name": "guidance", - "prose": "Cryptographic mechanisms used for the protection of integrity include, for example, digital signatures and the computation and application of signed hashes using asymmetric cryptography, protecting the confidentiality of the key used to generate the hash, and using the public key to verify the hash information.", - "links": [ - { - "href": "#sc-13", - "rel": "related" - } - ] - }, - { - "id": "si-7.6_obj", - "name": "objective", - "prose": "Determine if the information system employs cryptographic mechanism to detect unauthorized changes to:", - "parts": [ - { - "id": "si-7.6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(6)[1]" - } - ], - "prose": "software;" - }, - { - "id": "si-7.6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(6)[2]" - } - ], - "prose": "firmware; and" - }, - { - "id": "si-7.6_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(6)[3]" - } - ], - "prose": "information." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing software, firmware, and information integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ncryptographic mechanisms and associated documentation\n\nrecords of detected unauthorized changes to software, firmware, and information\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for software, firmware, and/or information integrity\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Software, firmware, and information integrity verification tools\n\ncryptographic mechanisms implementing software, firmware, and information integrity" - } - ] - } - ] - }, - { - "id": "si-7.7", - "class": "SP800-53-enhancement", - "title": "Integration of Detection and Response", - "params": [ - { - "id": "si-7.7_prm_1", - "label": "organization-defined security-relevant changes to the information system" - } - ], - "props": [ - { - "name": "label", - "value": "SI-7(7)" - }, - { - "name": "sort-id", - "value": "si-07.07" - } - ], - "parts": [ - { - "id": "si-7.7_smt", - "name": "statement", - "prose": "The organization incorporates the detection of unauthorized {{ insert: param, si-7.7_prm_1 }} into the organizational incident response capability." - }, - { - "id": "si-7.7_gdn", - "name": "guidance", - "prose": "This control enhancement helps to ensure that detected events are tracked, monitored, corrected, and available for historical purposes. Maintaining historical records is important both for being able to identify and discern adversary actions over an extended period of time and for possible legal actions. Security-relevant changes include, for example, unauthorized changes to established configuration settings or unauthorized elevation of information system privileges.", - "links": [ - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-5", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "si-7.7_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-7.7_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(7)[1]" - } - ], - "prose": "defines unauthorized security-relevant changes to the information system; and" - }, - { - "id": "si-7.7_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(7)[2]" - } - ], - "prose": "incorporates the detection of unauthorized organization-defined security-relevant changes to the information system into the organizational incident response capability." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing software, firmware, and information integrity\n\nprocedures addressing incident response\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nincident response records\n\ninformation audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for software, firmware, and/or information integrity\n\norganizational personnel with information security responsibilities\n\norganizational personnel with incident response responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for incorporating detection of unauthorized security-relevant changes into the incident response capability\n\nsoftware, firmware, and information integrity verification tools\n\nautomated mechanisms supporting and/or implementing incorporation of detection of unauthorized security-relevant changes into the incident response capability" - } - ] - } - ] - }, - { - "id": "si-7.8", - "class": "SP800-53-enhancement", - "title": "Auditing Capability for Significant Events", - "params": [ - { - "id": "si-7.8_prm_1", - "select": { - "how-many": "one-or-more", - "choice": [ - "generates an audit record", - "alerts current user", - "alerts {{ insert: param, si-7.8_prm_2 }} ", - " {{ insert: param, si-7.8_prm_3 }} " - ] - } - }, - { - "id": "si-7.8_prm_2", - "depends-on": "si-7.8_prm_1", - "label": "organization-defined personnel or roles" - }, - { - "id": "si-7.8_prm_3", - "depends-on": "si-7.8_prm_1", - "label": "organization-defined other actions" - } - ], - "props": [ - { - "name": "label", - "value": "SI-7(8)" - }, - { - "name": "sort-id", - "value": "si-07.08" - } - ], - "parts": [ - { - "id": "si-7.8_smt", - "name": "statement", - "prose": "The information system, upon detection of a potential integrity violation, provides the capability to audit the event and initiates the following actions: {{ insert: param, si-7.8_prm_1 }}." - }, - { - "id": "si-7.8_gdn", - "name": "guidance", - "prose": "Organizations select response actions based on types of software, specific software, or information for which there are potential integrity violations.", - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - } - ] - }, - { - "id": "si-7.8_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "si-7.8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(8)[1]" - } - ], - "prose": "the organization defines personnel or roles to be alerted upon detection of a potential integrity violation;" - }, - { - "id": "si-7.8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(8)[2]" - } - ], - "prose": "the organization defines other actions to be taken upon detection of a potential integrity violation;" - }, - { - "id": "si-7.8_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(8)[3]" - } - ], - "parts": [ - { - "id": "si-7.8_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(8)[3][a]" - } - ], - "prose": "the information system, upon detection of a potential integrity violation, provides the capability to audit the event;" - }, - { - "id": "si-7.8_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(8)[3][b]" - } - ], - "prose": "the information system, upon detection of a potential integrity violation, initiates one or more of the following actions:", - "parts": [ - { - "id": "si-7.8_obj.3.b.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(8)[3][b][1]" - } - ], - "prose": "generates an audit record;" - }, - { - "id": "si-7.8_obj.3.b.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(8)[3][b][2]" - } - ], - "prose": "alerts current user;" - }, - { - "id": "si-7.8_obj.3.b.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(8)[3][b][3]" - } - ], - "prose": "alerts organization-defined personnel or roles; and/or" - }, - { - "id": "si-7.8_obj.3.b.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(8)[3][b][4]" - } - ], - "prose": "organization-defined other actions." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing software, firmware, and information integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nintegrity verification tools and associated documentation\n\nrecords of integrity scans\n\nincident response records, list of security-relevant changes to the information system\n\nautomated tools supporting alerts and notifications if unauthorized security changes are detected\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for software, firmware, and/or information integrity\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Software, firmware, and information integrity verification tools\n\nautomated mechanisms supporting and/or implementing the capability to audit potential integrity violations\n\nautomated mechanisms supporting and/or implementing alerts about potential integrity violations" - } - ] - } - ] - }, - { - "id": "si-7.9", - "class": "SP800-53-enhancement", - "title": "Verify Boot Process", - "params": [ - { - "id": "si-7.9_prm_1", - "label": "organization-defined devices" - } - ], - "props": [ - { - "name": "label", - "value": "SI-7(9)" - }, - { - "name": "sort-id", - "value": "si-07.09" - } - ], - "parts": [ - { - "id": "si-7.9_smt", - "name": "statement", - "prose": "The information system verifies the integrity of the boot process of {{ insert: param, si-7.9_prm_1 }}." - }, - { - "id": "si-7.9_gdn", - "name": "guidance", - "prose": "Ensuring the integrity of boot processes is critical to starting devices in known/trustworthy states. Integrity verification mechanisms provide organizational personnel with assurance that only trusted code is executed during boot processes." - }, - { - "id": "si-7.9_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "si-7.9_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(9)[1]" - } - ], - "prose": "the organization defines devices requiring integrity verification of the boot process; and" - }, - { - "id": "si-7.9_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(9)[2]" - } - ], - "prose": "the information system verifies the integrity of the boot process of organization-defined devices." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing software, firmware, and information integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nintegrity verification tools and associated documentation\n\ndocumentation\n\nrecords of integrity verification scans\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for software, firmware, and/or information integrity\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Software, firmware, and information integrity verification tools\n\nautomated mechanisms supporting and/or implementing integrity verification of the boot process" - } - ] - } - ] - }, - { - "id": "si-7.10", - "class": "SP800-53-enhancement", - "title": "Protection of Boot Firmware", - "params": [ - { - "id": "si-7.10_prm_1", - "label": "organization-defined security safeguards" - }, - { - "id": "si-7.10_prm_2", - "label": "organization-defined devices" - } - ], - "props": [ - { - "name": "label", - "value": "SI-7(10)" - }, - { - "name": "sort-id", - "value": "si-07.10" - } - ], - "parts": [ - { - "id": "si-7.10_smt", - "name": "statement", - "prose": "The information system implements {{ insert: param, si-7.10_prm_1 }} to protect the integrity of boot firmware in {{ insert: param, si-7.10_prm_2 }}." - }, - { - "id": "si-7.10_gdn", - "name": "guidance", - "prose": "Unauthorized modifications to boot firmware may be indicative of a sophisticated, targeted cyber attack. These types of cyber attacks can result in a permanent denial of service (e.g., if the firmware is corrupted) or a persistent malicious code presence (e.g., if code is embedded within the firmware). Devices can protect the integrity of the boot firmware in organizational information systems by: (i) verifying the integrity and authenticity of all updates to the boot firmware prior to applying changes to the boot devices; and (ii) preventing unauthorized processes from modifying the boot firmware." - }, - { - "id": "si-7.10_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "si-7.10_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(10)[1]" - } - ], - "prose": "the organization defines security safeguards to be implemented to protect the integrity of boot firmware in devices;" - }, - { - "id": "si-7.10_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(10)[2]" - } - ], - "prose": "the organization defines devices requiring organization-defined security safeguards to be implemented to protect the integrity of boot firmware; and" - }, - { - "id": "si-7.10_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(10)[3]" - } - ], - "prose": "the information system implements organization-defined security safeguards to protect the integrity of boot firmware in organization-defined devices." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing software, firmware, and information integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nintegrity verification tools and associated documentation\n\nrecords of integrity verification scans\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for software, firmware, and/or information integrity\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Software, firmware, and information integrity verification tools\n\nautomated mechanisms supporting and/or implementing protection of the integrity of boot firmware\n\nsafeguards implementing protection of the integrity of boot firmware" - } - ] - } - ] - }, - { - "id": "si-7.11", - "class": "SP800-53-enhancement", - "title": "Confined Environments with Limited Privileges", - "params": [ - { - "id": "si-7.11_prm_1", - "label": "organization-defined user-installed software" - } - ], - "props": [ - { - "name": "label", - "value": "SI-7(11)" - }, - { - "name": "sort-id", - "value": "si-07.11" - } - ], - "parts": [ - { - "id": "si-7.11_smt", - "name": "statement", - "prose": "The organization requires that {{ insert: param, si-7.11_prm_1 }} execute in a confined physical or virtual machine environment with limited privileges." - }, - { - "id": "si-7.11_gdn", - "name": "guidance", - "prose": "Organizations identify software that may be of greater concern with regard to origin or potential for containing malicious code. For this type of software, user installations occur in confined environments of operation to limit or contain damage from malicious code that may be executed." - }, - { - "id": "si-7.11_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-7.11_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(11)[1]" - } - ], - "prose": "defines user-installed software to be executed in a confined physical or virtual machine environment with limited privileges; and" - }, - { - "id": "si-7.11_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(11)[2]" - } - ], - "prose": "requires that organization-defined user-installed software execute in a confined physical or virtual machine environment with limited privileges." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing software, firmware, and information integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for software, firmware, and/or information integrity\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Software, firmware, and information integrity verification tools\n\nautomated mechanisms supporting and/or implementing execution of software in a confined environment (physical and/or virtual)\n\nautomated mechanisms supporting and/or implementing limited privileges in the confined environment" - } - ] - } - ] - }, - { - "id": "si-7.12", - "class": "SP800-53-enhancement", - "title": "Integrity Verification", - "params": [ - { - "id": "si-7.12_prm_1", - "label": "organization-defined user-installed software" - } - ], - "props": [ - { - "name": "label", - "value": "SI-7(12)" - }, - { - "name": "sort-id", - "value": "si-07.12" - } - ], - "parts": [ - { - "id": "si-7.12_smt", - "name": "statement", - "prose": "The organization requires that the integrity of {{ insert: param, si-7.12_prm_1 }} be verified prior to execution." - }, - { - "id": "si-7.12_gdn", - "name": "guidance", - "prose": "Organizations verify the integrity of user-installed software prior to execution to reduce the likelihood of executing malicious code or code that contains errors from unauthorized modifications. Organizations consider the practicality of approaches to verifying software integrity including, for example, availability of checksums of adequate trustworthiness from software developers or vendors." - }, - { - "id": "si-7.12_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-7.12_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(12)[1]" - } - ], - "prose": "defines user-installed software requiring integrity verification prior to execution; and" - }, - { - "id": "si-7.12_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(12)[2]" - } - ], - "prose": "requires that the integrity of organization-defined user-installed software be verified prior to execution." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing software, firmware, and information integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nintegrity verification records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for software, firmware, and/or information integrity\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Software, firmware, and information integrity verification tools\n\nautomated mechanisms supporting and/or implementing verification of the integrity of user-installed software prior to execution" - } - ] - } - ] - }, - { - "id": "si-7.13", - "class": "SP800-53-enhancement", - "title": "Code Execution in Protected Environments", - "params": [ - { - "id": "si-7.13_prm_1", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "SI-7(13)" - }, - { - "name": "sort-id", - "value": "si-07.13" - } - ], - "parts": [ - { - "id": "si-7.13_smt", - "name": "statement", - "prose": "The organization allows execution of binary or machine-executable code obtained from sources with limited or no warranty and without the provision of source code only in confined physical or virtual machine environments and with the explicit approval of {{ insert: param, si-7.13_prm_1 }}." - }, - { - "id": "si-7.13_gdn", - "name": "guidance", - "prose": "This control enhancement applies to all sources of binary or machine-executable code including, for example, commercial software/firmware and open source software." - }, - { - "id": "si-7.13_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-7.13_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(13)[1]" - } - ], - "prose": "allows execution of binary or machine-executable code obtained from sources with limited or no warranty;" - }, - { - "id": "si-7.13_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(13)[2]" - } - ], - "prose": "allows execution of binary or machine-executable code without the provision of source code only in confined physical or virtual machines;" - }, - { - "id": "si-7.13_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(13)[3]" - } - ], - "prose": "defines personnel or roles required to provide explicit approval to allow execution of binary or machine-executable code; and" - }, - { - "id": "si-7.13_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(13)[4]" - } - ], - "prose": "allows execution of binary or machine-executable code with the explicit approval of organization-defined personnel or roles." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing software, firmware, and information integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\napproval records for execution of binary and machine-executable code\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for software, firmware, and/or information integrity\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Software, firmware, and information integrity verification tools\n\nautomated mechanisms supporting and/or implementing approvals for execution of binary or machine-executable code" - } - ] - } - ] - }, - { - "id": "si-7.14", - "class": "SP800-53-enhancement", - "title": "Binary or Machine Executable Code", - "props": [ - { - "name": "label", - "value": "SI-7(14)" - }, - { - "name": "sort-id", - "value": "si-07.14" - } - ], - "parts": [ - { - "id": "si-7.14_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "si-7.14_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Prohibits the use of binary or machine-executable code from sources with limited or no warranty and without the provision of source code; and" - }, - { - "id": "si-7.14_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Provides exceptions to the source code requirement only for compelling mission/operational requirements and with the approval of the authorizing official." - } - ] - }, - { - "id": "si-7.14_gdn", - "name": "guidance", - "prose": "This control enhancement applies to all sources of binary or machine-executable code including, for example, commercial software/firmware and open source software. Organizations assess software products without accompanying source code from sources with limited or no warranty for potential security impacts. The assessments address the fact that these types of software products may be very difficult to review, repair, or extend, given that organizations, in most cases, do not have access to the original source code, and there may be no owners who could make such repairs on behalf of organizations.", - "links": [ - { - "href": "#sa-5", - "rel": "related" - } - ] - }, - { - "id": "si-7.14_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-7.14.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(14)(a)" - } - ], - "parts": [ - { - "id": "si-7.14.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(14)(a)[1]" - } - ], - "prose": "prohibits the use of binary or machine-executable code from sources with limited or no warranty;" - }, - { - "id": "si-7.14.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(14)(a)[2]" - } - ], - "prose": "prohibits the use of binary or machine-executable code without the provision of source code;" - } - ], - "links": [ - { - "href": "#si-7.14_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "si-7.14.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(14)(b)" - } - ], - "parts": [ - { - "id": "si-7.14.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(14)(b)[1]" - } - ], - "prose": "provides exceptions to the source code requirement only for compelling mission/operational requirements; and" - }, - { - "id": "si-7.14.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(14)(b)[2]" - } - ], - "prose": "provides exceptions to the source code requirement only with the approval of the authorizing official." - } - ], - "links": [ - { - "href": "#si-7.14_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing software, firmware, and information integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\napproval records for execution of binary and machine-executable code\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for software, firmware, and/or information integrity\n\norganizational personnel with information security responsibilities\n\nauthorizing official\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing prohibition of the execution of binary or machine-executable code" - } - ] - } - ] - }, - { - "id": "si-7.15", - "class": "SP800-53-enhancement", - "title": "Code Authentication", - "params": [ - { - "id": "si-7.15_prm_1", - "label": "organization-defined software or firmware components" - } - ], - "props": [ - { - "name": "label", - "value": "SI-7(15)" - }, - { - "name": "sort-id", - "value": "si-07.15" - } - ], - "parts": [ - { - "id": "si-7.15_smt", - "name": "statement", - "prose": "The information system implements cryptographic mechanisms to authenticate {{ insert: param, si-7.15_prm_1 }} prior to installation." - }, - { - "id": "si-7.15_gdn", - "name": "guidance", - "prose": "Cryptographic authentication includes, for example, verifying that software or firmware components have been digitally signed using certificates recognized and approved by organizations. Code signing is an effective method to protect against malicious code." - }, - { - "id": "si-7.15_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "si-7.15_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(15)[1]" - } - ], - "parts": [ - { - "id": "si-7.15_obj.1.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(15)[1][a]" - } - ], - "prose": "the organization defines software components to be authenticated by cryptographic mechanisms prior to installation;" - }, - { - "id": "si-7.15_obj.1.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(15)[1][b]" - } - ], - "prose": "the organization defines firmware components to be authenticated by cryptographic mechanisms prior to installation;" - } - ] - }, - { - "id": "si-7.15_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(15)[2]" - } - ], - "parts": [ - { - "id": "si-7.15_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(15)[2][a]" - } - ], - "prose": "the information system implements cryptographic mechanisms to authenticate organization-defined software components prior to installation; and" - }, - { - "id": "si-7.15_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(15)[2][b]" - } - ], - "prose": "the information system implements cryptographic mechanisms to authenticate organization-defined firmware components prior to installation." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing software, firmware, and information integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ncryptographic mechanisms and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for software, firmware, and/or information integrity\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Cryptographic mechanisms authenticating software/firmware prior to installation" - } - ] - } - ] - }, - { - "id": "si-7.16", - "class": "SP800-53-enhancement", - "title": "Time Limit On Process Execution w/o Supervision", - "params": [ - { - "id": "si-7.16_prm_1", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "SI-7(16)" - }, - { - "name": "sort-id", - "value": "si-07.16" - } - ], - "parts": [ - { - "id": "si-7.16_smt", - "name": "statement", - "prose": "The organization does not allow processes to execute without supervision for more than {{ insert: param, si-7.16_prm_1 }}." - }, - { - "id": "si-7.16_gdn", - "name": "guidance", - "prose": "This control enhancement addresses processes for which normal execution periods can be determined and situations in which organizations exceed such periods. Supervision includes, for example, operating system timers, automated responses, or manual oversight and response when information system process anomalies occur." - }, - { - "id": "si-7.16_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-7.16_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(16)[1]" - } - ], - "prose": "defines a time period as the maximum period allowed for processes to execute without supervision; and" - }, - { - "id": "si-7.16_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-7(16)[2]" - } - ], - "prose": "does not allow processes to execute without supervision for more than the organization-defined time period." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing software and information integrity\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for software, firmware, and/or information integrity\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Software, firmware, and information integrity verification tools\n\nautomated mechanisms supporting and/or implementing time limits on process execution without supervision" - } - ] - } - ] - } - ] - }, - { - "id": "si-8", - "class": "SP800-53", - "title": "Spam Protection", - "props": [ - { - "name": "label", - "value": "SI-8" - }, - { - "name": "sort-id", - "value": "si-08" - } - ], - "links": [ - { - "href": "#c6e95ca0-5828-420e-b095-00895b72b5e8", - "rel": "reference" - } - ], - "parts": [ - { - "id": "si-8_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "si-8_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Employs spam protection mechanisms at information system entry and exit points to detect and take action on unsolicited messages; and" - }, - { - "id": "si-8_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Updates spam protection mechanisms when new releases are available in accordance with organizational configuration management policy and procedures." - } - ] - }, - { - "id": "si-8_gdn", - "name": "guidance", - "prose": "Information system entry and exit points include, for example, firewalls, electronic mail servers, web servers, proxy servers, remote-access servers, workstations, mobile devices, and notebook/laptop computers. Spam can be transported by different means including, for example, electronic mail, electronic mail attachments, and web accesses. Spam protection mechanisms include, for example, signature definitions.", - "links": [ - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#sc-5", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - } - ] - }, - { - "id": "si-8_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-8.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-8(a)" - } - ], - "prose": "employs spam protection mechanisms:", - "parts": [ - { - "id": "si-8.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-8(a)[1]" - } - ], - "prose": "at information system entry points to detect unsolicited messages;" - }, - { - "id": "si-8.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-8(a)[2]" - } - ], - "prose": "at information system entry points to take action on unsolicited messages;" - }, - { - "id": "si-8.a_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-8(a)[3]" - } - ], - "prose": "at information system exit points to detect unsolicited messages;" - }, - { - "id": "si-8.a_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-8(a)[4]" - } - ], - "prose": "at information system exit points to take action on unsolicited messages; and" - } - ] - }, - { - "id": "si-8.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-8(b)" - } - ], - "prose": "updates spam protection mechanisms when new releases are available in accordance with organizational configuration management policy and procedures." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nconfiguration management policy and procedures (CM-1)\n\nprocedures addressing spam protection\n\nspam protection mechanisms\n\nrecords of spam protection updates\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for spam protection\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for implementing spam protection\n\nautomated mechanisms supporting and/or implementing spam protection" - } - ] - } - ], - "controls": [ - { - "id": "si-8.1", - "class": "SP800-53-enhancement", - "title": "Central Management", - "props": [ - { - "name": "label", - "value": "SI-8(1)" - }, - { - "name": "sort-id", - "value": "si-08.01" - } - ], - "parts": [ - { - "id": "si-8.1_smt", - "name": "statement", - "prose": "The organization centrally manages spam protection mechanisms." - }, - { - "id": "si-8.1_gdn", - "name": "guidance", - "prose": "Central management is the organization-wide management and implementation of spam protection mechanisms. Central management includes planning, implementing, assessing, authorizing, and monitoring the organization-defined, centrally managed spam protection security controls.", - "links": [ - { - "href": "#au-3", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ] - }, - { - "id": "si-8.1_obj", - "name": "objective", - "prose": "Determine if the organization centrally manages spam protection mechanisms." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing spam protection\n\nspam protection mechanisms\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for spam protection\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for central management of spam protection\n\nautomated mechanisms supporting and/or implementing central management of spam protection" - } - ] - } - ] - }, - { - "id": "si-8.2", - "class": "SP800-53-enhancement", - "title": "Automatic Updates", - "props": [ - { - "name": "label", - "value": "SI-8(2)" - }, - { - "name": "sort-id", - "value": "si-08.02" - } - ], - "parts": [ - { - "id": "si-8.2_smt", - "name": "statement", - "prose": "The information system automatically updates spam protection mechanisms." - }, - { - "id": "si-8.2_obj", - "name": "objective", - "prose": "Determine if the information system automatically updates spam protection mechanisms." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing spam protection\n\nspam protection mechanisms\n\nrecords of spam protection updates\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for spam protection\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for spam protection\n\nautomated mechanisms supporting and/or implementing automatic updates to spam protection mechanisms" - } - ] - } - ] - }, - { - "id": "si-8.3", - "class": "SP800-53-enhancement", - "title": "Continuous Learning Capability", - "props": [ - { - "name": "label", - "value": "SI-8(3)" - }, - { - "name": "sort-id", - "value": "si-08.03" - } - ], - "parts": [ - { - "id": "si-8.3_smt", - "name": "statement", - "prose": "The information system implements spam protection mechanisms with a learning capability to more effectively identify legitimate communications traffic." - }, - { - "id": "si-8.3_gdn", - "name": "guidance", - "prose": "Learning mechanisms include, for example, Bayesian filters that respond to user inputs identifying specific traffic as spam or legitimate by updating algorithm parameters and thereby more accurately separating types of traffic." - }, - { - "id": "si-8.3_obj", - "name": "objective", - "prose": "Determine if the information system implements spam protection mechanisms with a learning capability to more effectively identify legitimate communications traffic." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing spam protection\n\nspam protection mechanisms\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for spam protection\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for spam protection\n\nautomated mechanisms supporting and/or implementing spam protection mechanisms with a learning capability" - } - ] - } - ] - } - ] - }, - { - "id": "si-9", - "class": "SP800-53", - "title": "Information Input Restrictions", - "props": [ - { - "name": "label", - "value": "SI-9" - }, - { - "name": "sort-id", - "value": "si-09" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "incorporated-into" - }, - { - "href": "#ac-3", - "rel": "incorporated-into" - }, - { - "href": "#ac-5", - "rel": "incorporated-into" - }, - { - "href": "#ac-6", - "rel": "incorporated-into" - } - ] - }, - { - "id": "si-10", - "class": "SP800-53", - "title": "Information Input Validation", - "params": [ - { - "id": "si-10_prm_1", - "label": "organization-defined information inputs" - } - ], - "props": [ - { - "name": "label", - "value": "SI-10" - }, - { - "name": "sort-id", - "value": "si-10" - } - ], - "parts": [ - { - "id": "si-10_smt", - "name": "statement", - "prose": "The information system checks the validity of {{ insert: param, si-10_prm_1 }}." - }, - { - "id": "si-10_gdn", - "name": "guidance", - "prose": "Checking the valid syntax and semantics of information system inputs (e.g., character set, length, numerical range, and acceptable values) verifies that inputs match specified definitions for format and content. Software applications typically follow well-defined protocols that use structured messages (i.e., commands or queries) to communicate between software modules or system components. Structured messages can contain raw or unstructured data interspersed with metadata or control information. If software applications use attacker-supplied inputs to construct structured messages without properly encoding such messages, then the attacker could insert malicious commands or special characters that can cause the data to be interpreted as control information or metadata. Consequently, the module or component that receives the tainted output will perform the wrong operations or otherwise interpret the data incorrectly. Prescreening inputs prior to passing to interpreters prevents the content from being unintentionally interpreted as commands. Input validation helps to ensure accurate and correct inputs and prevent attacks such as cross-site scripting and a variety of injection attacks." - }, - { - "id": "si-10_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "si-10_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-10[1]" - } - ], - "prose": "the organization defines information inputs requiring validity checks; and" - }, - { - "id": "si-10_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-10[2]" - } - ], - "prose": "the information system checks the validity of organization-defined information inputs." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\naccess control policy and procedures\n\nseparation of duties policy and procedures\n\nprocedures addressing information input validation\n\ndocumentation for automated tools and applications to verify validity of information\n\nlist of information inputs requiring validity checks\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for information input validation\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing validity checks on information inputs" - } - ] - } - ], - "controls": [ - { - "id": "si-10.1", - "class": "SP800-53-enhancement", - "title": "Manual Override Capability", - "params": [ - { - "id": "si-10.1_prm_1", - "label": "organization-defined inputs" - }, - { - "id": "si-10.1_prm_2", - "label": "organization-defined authorized individuals" - } - ], - "props": [ - { - "name": "label", - "value": "SI-10(1)" - }, - { - "name": "sort-id", - "value": "si-10.01" - } - ], - "parts": [ - { - "id": "si-10.1_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "si-10.1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Provides a manual override capability for input validation of {{ insert: param, si-10.1_prm_1 }};" - }, - { - "id": "si-10.1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Restricts the use of the manual override capability to only {{ insert: param, si-10.1_prm_2 }}; and" - }, - { - "id": "si-10.1_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Audits the use of the manual override capability." - } - ] - }, - { - "id": "si-10.1_gdn", - "name": "guidance", - "links": [ - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - } - ] - }, - { - "id": "si-10.1_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "si-10.1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-10(1)(a)" - } - ], - "parts": [ - { - "id": "si-10.1.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-10(1)(a)[1]" - } - ], - "prose": "the organization defines information inputs for which the information system provides a manual override capability for input validation;" - }, - { - "id": "si-10.1.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-10(1)(a)[2]" - } - ], - "prose": "the information system provides a manual override capability for input validation of organization-defined inputs;" - } - ], - "links": [ - { - "href": "#si-10.1_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "si-10.1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-10(1)(b)" - } - ], - "parts": [ - { - "id": "si-10.1.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-10(1)(b)[1]" - } - ], - "prose": "the organization defines authorized individuals who can use the manual override capability;" - }, - { - "id": "si-10.1.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-10(1)(b)[2]" - } - ], - "prose": "the information system restricts the use of manual override capability to organization-defined authorized individuals; and" - } - ], - "links": [ - { - "href": "#si-10.1_smt.b", - "rel": "corresp" - } - ] - }, - { - "id": "si-10.1.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-10(1)(c)" - } - ], - "prose": "the information system audits the use of the manual override capability.", - "links": [ - { - "href": "#si-10.1_smt.c", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\naccess control policy and procedures\n\nseparation of duties policy and procedures\n\nprocedures addressing information input validation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for information input validation\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for use of manual override capability\n\nautomated mechanisms supporting and/or implementing manual override capability for input validation\n\nautomated mechanisms supporting and/or implementing auditing of the use of manual override capability" - } - ] - } - ] - }, - { - "id": "si-10.2", - "class": "SP800-53-enhancement", - "title": "Review / Resolution of Errors", - "params": [ - { - "id": "si-10.2_prm_1", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "SI-10(2)" - }, - { - "name": "sort-id", - "value": "si-10.02" - } - ], - "parts": [ - { - "id": "si-10.2_smt", - "name": "statement", - "prose": "The organization ensures that input validation errors are reviewed and resolved within {{ insert: param, si-10.2_prm_1 }}." - }, - { - "id": "si-10.2_gdn", - "name": "guidance", - "prose": "Resolution of input validation errors includes, for example, correcting systemic causes of errors and resubmitting transactions with corrected input." - }, - { - "id": "si-10.2_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-10.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-10(2)[1]" - } - ], - "prose": "defines a time period within which input validation errors are to be reviewed and resolved; and" - }, - { - "id": "si-10.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-10(2)[2]" - } - ], - "prose": "ensures that input validation errors are reviewed and resolved within the organization-defined time period." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\naccess control policy and procedures\n\nseparation of duties policy and procedures\n\nprocedures addressing information input validation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nreview records of information input validation errors and resulting resolutions\n\ninformation input validation error logs or records\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for information input validation\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for review and resolution of input validation errors\n\nautomated mechanisms supporting and/or implementing review and resolution of input validation errors" - } - ] - } - ] - }, - { - "id": "si-10.3", - "class": "SP800-53-enhancement", - "title": "Predictable Behavior", - "props": [ - { - "name": "label", - "value": "SI-10(3)" - }, - { - "name": "sort-id", - "value": "si-10.03" - } - ], - "parts": [ - { - "id": "si-10.3_smt", - "name": "statement", - "prose": "The information system behaves in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received." - }, - { - "id": "si-10.3_gdn", - "name": "guidance", - "prose": "A common vulnerability in organizational information systems is unpredictable behavior when invalid inputs are received. This control enhancement ensures that there is predictable behavior in the face of invalid inputs by specifying information system responses that facilitate transitioning the system to known states without adverse, unintended side effects." - }, - { - "id": "si-10.3_obj", - "name": "objective", - "prose": "Determine if the information system behaves in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information input validation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for information input validation\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing predictable behavior when invalid inputs are received" - } - ] - } - ] - }, - { - "id": "si-10.4", - "class": "SP800-53-enhancement", - "title": "Review / Timing Interactions", - "props": [ - { - "name": "label", - "value": "SI-10(4)" - }, - { - "name": "sort-id", - "value": "si-10.04" - } - ], - "parts": [ - { - "id": "si-10.4_smt", - "name": "statement", - "prose": "The organization accounts for timing interactions among information system components in determining appropriate responses for invalid inputs." - }, - { - "id": "si-10.4_gdn", - "name": "guidance", - "prose": "In addressing invalid information system inputs received across protocol interfaces, timing interactions become relevant, where one protocol needs to consider the impact of the error response on other protocols within the protocol stack. For example, 802.11 standard wireless network protocols do not interact well with Transmission Control Protocols (TCP) when packets are dropped (which could be due to invalid packet input). TCP assumes packet losses are due to congestion, while packets lost over 802.11 links are typically dropped due to collisions or noise on the link. If TCP makes a congestion response, it takes precisely the wrong action in response to a collision event. Adversaries may be able to use apparently acceptable individual behaviors of the protocols in concert to achieve adverse effects through suitable construction of invalid input." - }, - { - "id": "si-10.4_obj", - "name": "objective", - "prose": "Determine if the organization accounts for timing interactions among information system components in determining appropriate responses for invalid inputs." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information input validation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for information input validation\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for determining appropriate responses to invalid inputs\n\nautomated mechanisms supporting and/or implementing responses to invalid inputs" - } - ] - } - ] - }, - { - "id": "si-10.5", - "class": "SP800-53-enhancement", - "title": "Restrict Inputs to Trusted Sources and Approved Formats", - "params": [ - { - "id": "si-10.5_prm_1", - "label": "organization-defined trusted sources" - }, - { - "id": "si-10.5_prm_2", - "label": "organization-defined formats" - } - ], - "props": [ - { - "name": "label", - "value": "SI-10(5)" - }, - { - "name": "sort-id", - "value": "si-10.05" - } - ], - "parts": [ - { - "id": "si-10.5_smt", - "name": "statement", - "prose": "The organization restricts the use of information inputs to {{ insert: param, si-10.5_prm_1 }} and/or {{ insert: param, si-10.5_prm_2 }}." - }, - { - "id": "si-10.5_gdn", - "name": "guidance", - "prose": "This control enhancement applies the concept of whitelisting to information inputs. Specifying known trusted sources for information inputs and acceptable formats for such inputs can reduce the probability of malicious activity." - }, - { - "id": "si-10.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-10.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-10(5)[1]" - } - ], - "prose": "defines trusted sources to which the use of information inputs is to be restricted;" - }, - { - "id": "si-10.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-10(5)[2]" - } - ], - "prose": "defines formats to which the use of information inputs is to be restricted;" - }, - { - "id": "si-10.5_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-10(5)[3]" - } - ], - "prose": "restricts the use of information inputs to:", - "parts": [ - { - "id": "si-10.5_obj.3.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-10(5)[3][a]" - } - ], - "prose": "organization-defined trust sources; and/or" - }, - { - "id": "si-10.5_obj.3.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-10(5)[3][b]" - } - ], - "prose": "organization-defined formats." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information input validation\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of trusted sources for information inputs\n\nlist of acceptable formats for input restrictions\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for information input validation\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for restricting information inputs\n\nautomated mechanisms supporting and/or implementing restriction of information inputs" - } - ] - } - ] - } - ] - }, - { - "id": "si-11", - "class": "SP800-53", - "title": "Error Handling", - "params": [ - { - "id": "si-11_prm_1", - "label": "organization-defined personnel or roles" - } - ], - "props": [ - { - "name": "label", - "value": "SI-11" - }, - { - "name": "sort-id", - "value": "si-11" - } - ], - "parts": [ - { - "id": "si-11_smt", - "name": "statement", - "prose": "The information system:", - "parts": [ - { - "id": "si-11_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Generates error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries; and" - }, - { - "id": "si-11_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reveals error messages only to {{ insert: param, si-11_prm_1 }}." - } - ] - }, - { - "id": "si-11_gdn", - "name": "guidance", - "prose": "Organizations carefully consider the structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, erroneous logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information such as account numbers, social security numbers, and credit card numbers. In addition, error messages may provide a covert channel for transmitting information.", - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-3", - "rel": "related" - }, - { - "href": "#sc-31", - "rel": "related" - } - ] - }, - { - "id": "si-11_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "si-11.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-11(a)" - } - ], - "prose": "the information system generates error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries;" - }, - { - "id": "si-11.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-11(b)" - } - ], - "parts": [ - { - "id": "si-11.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-11(b)[1]" - } - ], - "prose": "the organization defines personnel or roles to whom error messages are to be revealed; and" - }, - { - "id": "si-11.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-11(b)[2]" - } - ], - "prose": "the information system reveals error messages only to organization-defined personnel or roles." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information system error handling\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ndocumentation providing structure/content of error messages\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for information input validation\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for error handling\n\nautomated mechanisms supporting and/or implementing error handling\n\nautomated mechanisms supporting and/or implementing management of error messages" - } - ] - } - ] - }, - { - "id": "si-12", - "class": "SP800-53", - "title": "Information Handling and Retention", - "props": [ - { - "name": "label", - "value": "SI-12" - }, - { - "name": "sort-id", - "value": "si-12" - } - ], - "parts": [ - { - "id": "si-12_smt", - "name": "statement", - "prose": "The organization handles and retains information within the information system and information output from the system in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements." - }, - { - "id": "si-12_gdn", - "name": "guidance", - "prose": "Information handling and retention requirements cover the full life cycle of information, in some cases extending beyond the disposal of information systems. The National Archives and Records Administration provides guidance on records retention.", - "links": [ - { - "href": "#ac-16", - "rel": "related" - }, - { - "href": "#au-5", - "rel": "related" - }, - { - "href": "#au-11", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - } - ] - }, - { - "id": "si-12_obj", - "name": "objective", - "prose": "Determine if the organization, in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements:", - "parts": [ - { - "id": "si-12_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-12[1]" - } - ], - "prose": "handles information within the information system;" - }, - { - "id": "si-12_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-12[2]" - } - ], - "prose": "handles output from the information system;" - }, - { - "id": "si-12_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-12[3]" - } - ], - "prose": "retains information within the information system; and" - }, - { - "id": "si-12_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-12[4]" - } - ], - "prose": "retains output from the information system." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nfederal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements applicable to information handling and retention\n\nmedia protection policy and procedures\n\nprocedures addressing information system output handling and retention\n\ninformation retention records, other relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for information handling and retention\n\norganizational personnel with information security responsibilities/network administrators" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for information handling and retention\n\nautomated mechanisms supporting and/or implementing information handling and retention" - } - ] - } - ] - }, - { - "id": "si-13", - "class": "SP800-53", - "title": "Predictable Failure Prevention", - "params": [ - { - "id": "si-13_prm_1", - "label": "organization-defined information system components" - }, - { - "id": "si-13_prm_2", - "label": "organization-defined MTTF substitution criteria" - } - ], - "props": [ - { - "name": "label", - "value": "SI-13" - }, - { - "name": "sort-id", - "value": "si-13" - } - ], - "parts": [ - { - "id": "si-13_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "si-13_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Determines mean time to failure (MTTF) for {{ insert: param, si-13_prm_1 }} in specific environments of operation; and" - }, - { - "id": "si-13_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Provides substitute information system components and a means to exchange active and standby components at {{ insert: param, si-13_prm_2 }}." - } - ] - }, - { - "id": "si-13_gdn", - "name": "guidance", - "prose": "While MTTF is primarily a reliability issue, this control addresses potential failures of specific information system components that provide security capability. Failure rates reflect installation-specific consideration, not industry-average. Organizations define criteria for substitution of information system components based on MTTF value with consideration for resulting potential harm from component failures. Transfer of responsibilities between active and standby components does not compromise safety, operational readiness, or security capability (e.g., preservation of state variables). Standby components remain available at all times except for maintenance issues or recovery failures in progress.", - "links": [ - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-10", - "rel": "related" - }, - { - "href": "#ma-6", - "rel": "related" - } - ] - }, - { - "id": "si-13_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-13.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(a)" - } - ], - "parts": [ - { - "id": "si-13.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(a)[1]" - } - ], - "prose": "defines information system components for which mean time to failure (MTTF) should be determined;" - }, - { - "id": "si-13.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(a)[2]" - } - ], - "prose": "determines MTTF for organization-defined information system components in specific environments of operation;" - } - ] - }, - { - "id": "si-13.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(b)" - } - ], - "parts": [ - { - "id": "si-13.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(b)[1]" - } - ], - "prose": "defines MTTF substitution criteria to be used as a means to exchange active and standby components;" - }, - { - "id": "si-13.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(b)[2]" - } - ], - "prose": "provides substitute information system components at organization-defined MTTF substitution criteria; and" - }, - { - "id": "si-13.b_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(b)[3]" - } - ], - "prose": "provides a means to exchange active and standby components at organization-defined MTTF substitution criteria." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing predictable failure prevention\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of MTTF substitution criteria\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for MTTF determinations and activities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\norganizational personnel with contingency planning responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing MTTF" - } - ] - } - ], - "controls": [ - { - "id": "si-13.1", - "class": "SP800-53-enhancement", - "title": "Transferring Component Responsibilities", - "params": [ - { - "id": "si-13.1_prm_1", - "label": "organization-defined fraction or percentage" - } - ], - "props": [ - { - "name": "label", - "value": "SI-13(1)" - }, - { - "name": "sort-id", - "value": "si-13.01" - } - ], - "parts": [ - { - "id": "si-13.1_smt", - "name": "statement", - "prose": "The organization takes information system components out of service by transferring component responsibilities to substitute components no later than {{ insert: param, si-13.1_prm_1 }} of mean time to failure." - }, - { - "id": "si-13.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-13.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(1)[1]" - } - ], - "prose": "defines maximum fraction or percentage of mean time to failure within which to transfer the responsibilities of an information system component that is out of service to a substitute component; and" - }, - { - "id": "si-13.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(1)[2]" - } - ], - "prose": "takes the information system component out of service by transferring component responsibilities to substitute components no later than organization-defined fraction or percentage of mean time to failure." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing predictable failure prevention\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for MTTF activities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\norganizational personnel with contingency planning responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing MTTF\n\nautomated mechanisms supporting and/or implementing transfer of component responsibilities to substitute components" - } - ] - } - ] - }, - { - "id": "si-13.2", - "class": "SP800-53-enhancement", - "title": "Time Limit On Process Execution Without Supervision", - "props": [ - { - "name": "label", - "value": "SI-13(2)" - }, - { - "name": "sort-id", - "value": "si-13.02" - }, - { - "name": "status", - "value": "Withdrawn" - } - ], - "links": [ - { - "href": "#si-7.16", - "rel": "incorporated-into" - } - ] - }, - { - "id": "si-13.3", - "class": "SP800-53-enhancement", - "title": "Manual Transfer Between Components", - "params": [ - { - "id": "si-13.3_prm_1", - "label": "organization-defined frequency" - }, - { - "id": "si-13.3_prm_2", - "label": "organization-defined time period" - } - ], - "props": [ - { - "name": "label", - "value": "SI-13(3)" - }, - { - "name": "sort-id", - "value": "si-13.03" - } - ], - "parts": [ - { - "id": "si-13.3_smt", - "name": "statement", - "prose": "The organization manually initiates transfers between active and standby information system components {{ insert: param, si-13.3_prm_1 }} if the mean time to failure exceeds {{ insert: param, si-13.3_prm_2 }}." - }, - { - "id": "si-13.3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-13.3_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(3)[1]" - } - ], - "prose": "defines the minimum frequency with which the organization manually initiates a transfer between active and standby information system components if the mean time to failure exceeds the organization-defined time period;" - }, - { - "id": "si-13.3_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(3)[2]" - } - ], - "prose": "defines the time period that the mean time to failure must exceed before the organization manually initiates a transfer between active and standby information system components; and" - }, - { - "id": "si-13.3_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(3)[3]" - } - ], - "prose": "manually initiates transfers between active and standby information system components at the organization-defined frequency if the mean time to failure exceeds the organization-defined time period." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing predictable failure prevention\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for MTTF activities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\norganizational personnel with contingency planning responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing MTTF and conducting the manual transfer between active and standby components" - } - ] - } - ] - }, - { - "id": "si-13.4", - "class": "SP800-53-enhancement", - "title": "Standby Component Installation / Notification", - "params": [ - { - "id": "si-13.4_prm_1", - "label": "organization-defined time period" - }, - { - "id": "si-13.4_prm_2", - "select": { - "how-many": "one-or-more", - "choice": [ - "activates {{ insert: param, si-13.4_prm_3 }} ", - "automatically shuts down the information system" - ] - } - }, - { - "id": "si-13.4_prm_3", - "depends-on": "si-13.4_prm_2", - "label": "organization-defined alarm" - } - ], - "props": [ - { - "name": "label", - "value": "SI-13(4)" - }, - { - "name": "sort-id", - "value": "si-13.04" - } - ], - "parts": [ - { - "id": "si-13.4_smt", - "name": "statement", - "prose": "The organization, if information system component failures are detected:", - "parts": [ - { - "id": "si-13.4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Ensures that the standby components are successfully and transparently installed within {{ insert: param, si-13.4_prm_1 }}; and" - }, - { - "id": "si-13.4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": " {{ insert: param, si-13.4_prm_2 }}." - } - ] - }, - { - "id": "si-13.4_gdn", - "name": "guidance", - "prose": "Automatic or manual transfer of components from standby to active mode can occur, for example, upon detection of component failures." - }, - { - "id": "si-13.4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-13.4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(4)(a)" - } - ], - "parts": [ - { - "id": "si-13.4.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(4)(a)[1]" - } - ], - "prose": "defines a time period for standby information system components to be successfully and transparently installed when information system component failures are detected;" - }, - { - "id": "si-13.4.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(4)(a)[2]" - } - ], - "prose": "ensures that the standby components are successfully and transparently installed within the organization-defined time period;" - } - ], - "links": [ - { - "href": "#si-13.4_smt.a", - "rel": "corresp" - } - ] - }, - { - "id": "si-13.4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(4)(b)" - } - ], - "parts": [ - { - "id": "si-13.4.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(4)(b)[1]" - } - ], - "prose": "defines an alarm to be activated when information system component failures are detected;" - }, - { - "id": "si-13.4.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(4)(b)[2]" - } - ], - "prose": "if information system component failures are detected, does one or more of the following:", - "parts": [ - { - "id": "si-13.4.b_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(4)(b)[2][a]" - } - ], - "prose": "activates the organization-defined alarm; and/or" - }, - { - "id": "si-13.4.b_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(4)(b)[2][b]" - } - ], - "prose": "automatically shuts down the information system." - } - ] - } - ], - "links": [ - { - "href": "#si-13.4_smt.b", - "rel": "corresp" - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing predictable failure prevention\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of actions to be taken once information system component failure is detected\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for MTTF activities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\norganizational personnel with contingency planning responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing MTTF\n\nautomated mechanisms supporting and/or implementing transparent installation of standby components\n\nautomated mechanisms supporting and/or implementing alarms or system shutdown if component failures are detected" - } - ] - } - ] - }, - { - "id": "si-13.5", - "class": "SP800-53-enhancement", - "title": "Failover Capability", - "params": [ - { - "id": "si-13.5_prm_1", - "select": { - "choice": [ - "real-time", - "near real-time" - ] - } - }, - { - "id": "si-13.5_prm_2", - "label": "organization-defined failover capability" - } - ], - "props": [ - { - "name": "label", - "value": "SI-13(5)" - }, - { - "name": "sort-id", - "value": "si-13.05" - } - ], - "parts": [ - { - "id": "si-13.5_smt", - "name": "statement", - "prose": "The organization provides {{ insert: param, si-13.5_prm_1 }} {{ insert: param, si-13.5_prm_2 }} for the information system." - }, - { - "id": "si-13.5_gdn", - "name": "guidance", - "prose": "Failover refers to the automatic switchover to an alternate information system upon the failure of the primary information system. Failover capability includes, for example, incorporating mirrored information system operations at alternate processing sites or periodic data mirroring at regular intervals defined by recovery time periods of organizations." - }, - { - "id": "si-13.5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-13.5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(5)[1]" - } - ], - "prose": "defines failover capability to be provided for the information system;" - }, - { - "id": "si-13.5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(5)[2]" - } - ], - "prose": "provides one of the following organization-defined failover capabilities for the information system:", - "parts": [ - { - "id": "si-13.5_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(5)[2][a]" - } - ], - "prose": "real-time failover capability; and/or" - }, - { - "id": "si-13.5_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-13(5)[2][b]" - } - ], - "prose": "near real-time failover capability." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing predictable failure prevention\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ndocumentation describing failover capability provided for the information system\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for failover capability\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\norganizational personnel with contingency planning responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for managing failover capability\n\nautomated mechanisms supporting and/or implementing failover capability" - } - ] - } - ] - } - ] - }, - { - "id": "si-14", - "class": "SP800-53", - "title": "Non-persistence", - "params": [ - { - "id": "si-14_prm_1", - "label": "organization-defined information system components and services" - }, - { - "id": "si-14_prm_2", - "select": { - "how-many": "one-or-more", - "choice": [ - "upon end of session of use", - "periodically at {{ insert: param, si-14_prm_3 }} " - ] - } - }, - { - "id": "si-14_prm_3", - "depends-on": "si-14_prm_2", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "SI-14" - }, - { - "name": "sort-id", - "value": "si-14" - } - ], - "parts": [ - { - "id": "si-14_smt", - "name": "statement", - "prose": "The organization implements non-persistent {{ insert: param, si-14_prm_1 }} that are initiated in a known state and terminated {{ insert: param, si-14_prm_2 }}." - }, - { - "id": "si-14_gdn", - "name": "guidance", - "prose": "This control mitigates risk from advanced persistent threats (APTs) by significantly reducing the targeting capability of adversaries (i.e., window of opportunity and available attack surface) to initiate and complete cyber attacks. By implementing the concept of non-persistence for selected information system components, organizations can provide a known state computing resource for a specific period of time that does not give adversaries sufficient time on target to exploit vulnerabilities in organizational information systems and the environments in which those systems operate. Since the advanced persistent threat is a high-end threat with regard to capability, intent, and targeting, organizations assume that over an extended period of time, a percentage of cyber attacks will be successful. Non-persistent information system components and services are activated as required using protected information and terminated periodically or upon the end of sessions. Non-persistence increases the work factor of adversaries in attempting to compromise or breach organizational information systems. Non-persistent system components can be implemented, for example, by periodically re-imaging components or by using a variety of common virtualization techniques. Non-persistent services can be implemented using virtualization techniques as part of virtual machines or as new instances of processes on physical machines (either persistent or non-persistent).The benefit of periodic refreshes of information system components/services is that it does not require organizations to first determine whether compromises of components or services have occurred (something that may often be difficult for organizations to determine). The refresh of selected information system components and services occurs with sufficient frequency to prevent the spread or intended impact of attacks, but not with such frequency that it makes the information system unstable. In some instances, refreshes of critical components and services may be done periodically in order to hinder the ability of adversaries to exploit optimum windows of vulnerabilities.", - "links": [ - { - "href": "#sc-30", - "rel": "related" - }, - { - "href": "#sc-34", - "rel": "related" - } - ] - }, - { - "id": "si-14_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-14_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-14[1]" - } - ], - "prose": "defines non-persistent information system components and services to be implemented;" - }, - { - "id": "si-14_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-14[2]" - } - ], - "parts": [ - { - "id": "si-14_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-14[2][a]" - } - ], - "prose": "defines a frequency to terminate non-persistent organization-defined components and services that are initiated in a known state;" - }, - { - "id": "si-14_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-14[2][b]" - } - ], - "prose": "implements non-persistent organization-defined information system components and services that are initiated in a known state and terminated one or more of the following:", - "parts": [ - { - "id": "si-14_obj.2.b.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-14[2][b][1]" - } - ], - "prose": "upon end of session of use; and/or" - }, - { - "id": "si-14_obj.2.b.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-14[2][b][2]" - } - ], - "prose": "periodically at the organization-defined frequency." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing non-persistence for information system components\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for non-persistence\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing initiation and termination of non-persistent components" - } - ] - } - ], - "controls": [ - { - "id": "si-14.1", - "class": "SP800-53-enhancement", - "title": "Refresh from Trusted Sources", - "params": [ - { - "id": "si-14.1_prm_1", - "label": "organization-defined trusted sources" - } - ], - "props": [ - { - "name": "label", - "value": "SI-14(1)" - }, - { - "name": "sort-id", - "value": "si-14.01" - } - ], - "parts": [ - { - "id": "si-14.1_smt", - "name": "statement", - "prose": "The organization ensures that software and data employed during information system component and service refreshes are obtained from {{ insert: param, si-14.1_prm_1 }}." - }, - { - "id": "si-14.1_gdn", - "name": "guidance", - "prose": "Trusted sources include, for example, software/data from write-once, read-only media or from selected off-line secure storage facilities." - }, - { - "id": "si-14.1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "si-14.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-14(1)[1]" - } - ], - "prose": "defines trusted sources from which software and data employed during information system component and service refreshes are to be obtained; and" - }, - { - "id": "si-14.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-14(1)[2]" - } - ], - "prose": "ensures that software and data employed during information system component and service refreshes are obtained from organization-defined trusted sources." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing non-persistence for information system components\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for obtaining component and service refreshes from trusted sources\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for defining and obtaining component and service refreshes from trusted sources\n\nautomated mechanisms supporting and/or implementing component and service refreshes" - } - ] - } - ] - } - ] - }, - { - "id": "si-15", - "class": "SP800-53", - "title": "Information Output Filtering", - "params": [ - { - "id": "si-15_prm_1", - "label": "organization-defined software programs and/or applications" - } - ], - "props": [ - { - "name": "label", - "value": "SI-15" - }, - { - "name": "sort-id", - "value": "si-15" - } - ], - "parts": [ - { - "id": "si-15_smt", - "name": "statement", - "prose": "The information system validates information output from {{ insert: param, si-15_prm_1 }} to ensure that the information is consistent with the expected content." - }, - { - "id": "si-15_gdn", - "name": "guidance", - "prose": "Certain types of cyber attacks (e.g., SQL injections) produce output results that are unexpected or inconsistent with the output results that would normally be expected from software programs or applications. This control enhancement focuses on detecting extraneous content, preventing such extraneous content from being displayed, and alerting monitoring tools that anomalous behavior has been discovered.", - "links": [ - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "si-15_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "si-15_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-15[1]" - } - ], - "prose": "the organization defines software programs and/or applications whose information output requires validation to ensure that the information is consistent with the expected content; and" - }, - { - "id": "si-15_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-15[2]" - } - ], - "prose": "the information system validates information output from organization-defined software programs and/or applications to ensure that the information is consistent with the expected content." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing information output filtering\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for validating information output\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for validating information output\n\nautomated mechanisms supporting and/or implementing information output validation" - } - ] - } - ] - }, - { - "id": "si-16", - "class": "SP800-53", - "title": "Memory Protection", - "params": [ - { - "id": "si-16_prm_1", - "label": "organization-defined security safeguards" - } - ], - "props": [ - { - "name": "label", - "value": "SI-16" - }, - { - "name": "sort-id", - "value": "si-16" - } - ], - "parts": [ - { - "id": "si-16_smt", - "name": "statement", - "prose": "The information system implements {{ insert: param, si-16_prm_1 }} to protect its memory from unauthorized code execution." - }, - { - "id": "si-16_gdn", - "name": "guidance", - "prose": "Some adversaries launch attacks with the intent of executing code in non-executable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism.", - "links": [ - { - "href": "#ac-25", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - } - ] - }, - { - "id": "si-16_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "si-16_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-16[1]" - } - ], - "prose": "the organization defines security safeguards to be implemented to protect information system memory from unauthorized code execution; and" - }, - { - "id": "si-16_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-16[2]" - } - ], - "prose": "the information system implements organization-defined security safeguards to protect its memory from unauthorized code execution." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing memory protection for the information system\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of security safeguards protecting information system memory from unauthorized code execution\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for memory protection\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Automated mechanisms supporting and/or implementing safeguards to protect information system memory from unauthorized code execution" - } - ] - } - ] - }, - { - "id": "si-17", - "class": "SP800-53", - "title": "Fail-safe Procedures", - "params": [ - { - "id": "si-17_prm_1", - "label": "organization-defined fail-safe procedures" - }, - { - "id": "si-17_prm_2", - "label": "organization-defined failure conditions occur" - } - ], - "props": [ - { - "name": "label", - "value": "SI-17" - }, - { - "name": "sort-id", - "value": "si-17" - } - ], - "parts": [ - { - "id": "si-17_smt", - "name": "statement", - "prose": "The information system implements {{ insert: param, si-17_prm_1 }} when {{ insert: param, si-17_prm_2 }}." - }, - { - "id": "si-17_gdn", - "name": "guidance", - "prose": "Failure conditions include, for example, loss of communications among critical system components or between system components and operational facilities. Fail-safe procedures include, for example, alerting operator personnel and providing specific instructions on subsequent steps to take (e.g., do nothing, reestablish system settings, shut down processes, restart the system, or contact designated organizational personnel).", - "links": [ - { - "href": "#cp-12", - "rel": "related" - }, - { - "href": "#cp-13", - "rel": "related" - }, - { - "href": "#sc-24", - "rel": "related" - }, - { - "href": "#si-13", - "rel": "related" - } - ] - }, - { - "id": "si-17_obj", - "name": "objective", - "prose": "Determine if:", - "parts": [ - { - "id": "si-17_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-17[1]" - } - ], - "prose": "the organization defines fail-safe procedures to be implemented when organization-defined failure conditions occur;" - }, - { - "id": "si-17_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-17[2]" - } - ], - "prose": "the organization defines failure conditions resulting in organization-defined fail-safe procedures being implemented when such conditions occur; and" - }, - { - "id": "si-17_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "SI-17[3]" - } - ], - "prose": "the information system implements organization-defined fail-safe procedures when organization-defined failure conditions occur." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "System and information integrity policy\n\nprocedures addressing memory protection for the information system\n\ninformation system design documentation\n\ninformation system configuration settings and associated documentation\n\nlist of security safeguards protecting information system memory from unauthorized code execution\n\ninformation system audit records\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for fail-safe procedures\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational fail-safe procedures\n\nautomated mechanisms supporting and/or implementing fail-safe procedures" - } - ] - } - ] - } - ] - }, - { - "id": "pm", - "class": "family", - "title": "Program Management", - "controls": [ - { - "id": "pm-1", - "class": "SP800-53", - "title": "Information Security Program Plan", - "params": [ - { - "id": "pm-1_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "PM-1" - }, - { - "name": "sort-id", - "value": "pm-01" - } - ], - "parts": [ - { - "id": "pm-1_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pm-1_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops and disseminates an organization-wide information security program plan that:", - "parts": [ - { - "id": "pm-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Provides an overview of the requirements for the security program and a description of the security program management controls and common controls in place or planned for meeting those requirements;" - }, - { - "id": "pm-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Includes the identification and assignment of roles, responsibilities, management commitment, coordination among organizational entities, and compliance;" - }, - { - "id": "pm-1_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Reflects coordination among organizational entities responsible for the different aspects of information security (i.e., technical, physical, personnel, cyber-physical); and" - }, - { - "id": "pm-1_smt.a.4", - "name": "item", - "props": [ - { - "name": "label", - "value": "4." - } - ], - "prose": "Is approved by a senior official with responsibility and accountability for the risk being incurred to organizational operations (including mission, functions, image, and reputation), organizational assets, individuals, other organizations, and the Nation;" - } - ] - }, - { - "id": "pm-1_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews the organization-wide information security program plan {{ insert: param, pm-1_prm_1 }};" - }, - { - "id": "pm-1_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Updates the plan to address organizational changes and problems identified during plan implementation or security control assessments; and" - }, - { - "id": "pm-1_smt.d", - "name": "item", - "props": [ - { - "name": "label", - "value": "d." - } - ], - "prose": "Protects the information security program plan from unauthorized disclosure and modification." - } - ] - }, - { - "id": "pm-1_gdn", - "name": "guidance", - "prose": "Information security program plans can be represented in single documents or compilations of documents at the discretion of organizations. The plans document the program management controls and organization-defined common controls. Information security program plans provide sufficient information about the program management controls/common controls (including specification of parameters for any assignment and selection statements either explicitly or by reference) to enable implementations that are unambiguously compliant with the intent of the plans and a determination of the risk to be incurred if the plans are implemented as intended. The security plans for individual information systems and the organization-wide information security program plan together, provide complete coverage for all security controls employed within the organization. Common controls are documented in an appendix to the organization’s information security program plan unless the controls are included in a separate security plan for an information system (e.g., security controls employed as part of an intrusion detection system providing organization-wide boundary protection inherited by one or more organizational information systems). The organization-wide information security program plan will indicate which separate security plans contain descriptions of common controls. Organizations have the flexibility to describe common controls in a single document or in multiple documents. In the case of multiple documents, the documents describing common controls are included as attachments to the information security program plan. If the information security program plan contains multiple documents, the organization specifies in each document the organizational official or officials responsible for the development, implementation, assessment, authorization, and monitoring of the respective common controls. For example, the organization may require that the Facilities Management Office develop, implement, assess, authorize, and continuously monitor common physical and environmental protection controls from the PE family when such controls are not associated with a particular information system but instead, support multiple information systems.", - "links": [ - { - "href": "#pm-8", - "rel": "related" - } - ] - }, - { - "id": "pm-1_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pm-1.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(a)" - } - ], - "prose": "develops and disseminates an organization-wide information security program plan that:", - "parts": [ - { - "id": "pm-1.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(a)(1)" - } - ], - "parts": [ - { - "id": "pm-1.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(a)(1)[1]" - } - ], - "prose": "provides an overview of the requirements for the security program;" - }, - { - "id": "pm-1.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(a)(1)[2]" - } - ], - "prose": "provides a description of the:", - "parts": [ - { - "id": "pm-1.a.1_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(a)(1)[2][a]" - } - ], - "prose": "security program management controls in place or planned for meeting those requirements;" - }, - { - "id": "pm-1.a.1_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(a)(1)[2][b]" - } - ], - "prose": "common controls in place or planned for meeting those requirements;" - } - ] - } - ] - }, - { - "id": "pm-1.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(a)(2)" - } - ], - "prose": "includes the identification and assignment of:", - "parts": [ - { - "id": "pm-1.a.2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(a)(2)[1]" - } - ], - "prose": "roles;" - }, - { - "id": "pm-1.a.2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(a)(2)[2]" - } - ], - "prose": "responsibilities;" - }, - { - "id": "pm-1.a.2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(a)(2)[3]" - } - ], - "prose": "management commitment;" - }, - { - "id": "pm-1.a.2_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(a)(2)[4]" - } - ], - "prose": "coordination among organizational entities;" - }, - { - "id": "pm-1.a.2_obj.5", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(a)(2)[5]" - } - ], - "prose": "compliance;" - } - ] - }, - { - "id": "pm-1.a.3_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(a)(3)" - } - ], - "prose": "reflects coordination among organizational entities responsible for the different aspects of information security (i.e., technical, physical, personnel, cyber-physical);" - }, - { - "id": "pm-1.a.4_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(a)(4)" - } - ], - "prose": "is approved by a senior official with responsibility and accountability for the risk being incurred to organizational operations, organizational assets, individuals, other organizations, and the Nation;" - } - ] - }, - { - "id": "pm-1.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(b)" - } - ], - "parts": [ - { - "id": "pm-1.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(b)[1]" - } - ], - "prose": "defines the frequency to review the security program plan for the information system;" - }, - { - "id": "pm-1.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(b)[2]" - } - ], - "prose": "reviews the organization-wide information security program plan with the organization-defined frequency;" - } - ] - }, - { - "id": "pm-1.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(c)" - } - ], - "prose": "updates the plan to address organizational:", - "parts": [ - { - "id": "pm-1.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(c)[1]" - } - ], - "prose": "changes identified during plan implementation;" - }, - { - "id": "pm-1.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(c)[2]" - } - ], - "prose": "changes identified during security control assessments;" - }, - { - "id": "pm-1.c_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(c)[3]" - } - ], - "prose": "problems identified during plan implementation;" - }, - { - "id": "pm-1.c_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(c)[4]" - } - ], - "prose": "problems identified during security control assessments;" - } - ] - }, - { - "id": "pm-1.d_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(d)" - } - ], - "prose": "protects the information security program plan from unauthorized:", - "parts": [ - { - "id": "pm-1.d_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(d)[1]" - } - ], - "prose": "disclosure; and" - }, - { - "id": "pm-1.d_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-1(d)[2]" - } - ], - "prose": "modification." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information security program plan\n\nprocedures addressing program plan development and implementation\n\nprocedures addressing program plan reviews and updates\n\nprocedures addressing coordination of the program plan with relevant entities\n\nprocedures for program plan approvals\n\nrecords of program plan reviews and updates\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security program planning and plan implementation responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for information security program plan development/review/update/approval\n\nautomated mechanisms supporting and/or implementing the information security program plan" - } - ] - } - ] - }, - { - "id": "pm-2", - "class": "SP800-53", - "title": "Senior Information Security Officer", - "props": [ - { - "name": "label", - "value": "PM-2" - }, - { - "name": "sort-id", - "value": "pm-02" - } - ], - "parts": [ - { - "id": "pm-2_smt", - "name": "statement", - "prose": "The organization appoints a senior information security officer with the mission and resources to coordinate, develop, implement, and maintain an organization-wide information security program." - }, - { - "id": "pm-2_gdn", - "name": "guidance", - "prose": "The security officer described in this control is an organizational official. For a federal agency (as defined in applicable federal laws, Executive Orders, directives, policies, or regulations) this official is the Senior Agency Information Security Officer. Organizations may also refer to this official as the Senior Information Security Officer or Chief Information Security Officer." - }, - { - "id": "pm-2_obj", - "name": "objective", - "prose": "Determine if the organization appoints a senior information security officer with the mission and resources to:", - "parts": [ - { - "id": "pm-2_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-2[1]" - } - ], - "prose": "coordinate an organization-wide information security program;" - }, - { - "id": "pm-2_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-2[2]" - } - ], - "prose": "develop an organization-wide information security program;" - }, - { - "id": "pm-2_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-2[3]" - } - ], - "prose": "implement an organization-wide information security program; and" - }, - { - "id": "pm-2_obj.4", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-2[4]" - } - ], - "prose": "maintain an organization-wide information security program." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information security program plan\n\nprocedures addressing program plan development and implementation\n\nprocedures addressing program plan reviews and updates\n\nprocedures addressing coordination of the program plan with relevant entities\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security program planning and plan implementation responsibilities\n\nsenior information security officer\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "pm-3", - "class": "SP800-53", - "title": "Information Security Resources", - "props": [ - { - "name": "label", - "value": "PM-3" - }, - { - "name": "sort-id", - "value": "pm-03" - } - ], - "links": [ - { - "href": "#29fcfe59-33cd-494a-8756-5907ae3a8f92", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pm-3_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pm-3_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Ensures that all capital planning and investment requests include the resources needed to implement the information security program and documents all exceptions to this requirement;" - }, - { - "id": "pm-3_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Employs a business case/Exhibit 300/Exhibit 53 to record the resources required; and" - }, - { - "id": "pm-3_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Ensures that information security resources are available for expenditure as planned." - } - ] - }, - { - "id": "pm-3_gdn", - "name": "guidance", - "prose": "Organizations consider establishing champions for information security efforts and as part of including the necessary resources, assign specialized expertise and resources as needed. Organizations may designate and empower an Investment Review Board (or similar group) to manage and provide oversight for the information security-related aspects of the capital planning and investment control process.", - "links": [ - { - "href": "#pm-4", - "rel": "related" - }, - { - "href": "#sa-2", - "rel": "related" - } - ] - }, - { - "id": "pm-3_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pm-3.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-3(a)" - } - ], - "parts": [ - { - "id": "pm-3.a_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-3(a)[1]" - } - ], - "prose": "ensures that all capital planning and investment requests include the resources needed to implement the information security program plan;" - }, - { - "id": "pm-3.a_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-3(a)[2]" - } - ], - "prose": "documents all exceptions to the requirement;" - } - ] - }, - { - "id": "pm-3.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-3(b)" - } - ], - "prose": "employs a business case/Exhibit 300/Exhibit 53 to record the resources required; and" - }, - { - "id": "pm-3.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-3(c)" - } - ], - "prose": "ensures that information security resources are available for expenditure as planned." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information security program plan\n\nExhibits 300\n\nExhibits 53\n\nbusiness cases for capital planning and investment\n\nprocedures for capital planning and investment\n\ndocumentation of exceptions to capital planning requirements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security program planning responsibilities\n\norganizational personnel responsible for capital planning and investment\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for capital planning and investment\n\norganizational processes for business case/Exhibit 300/Exhibit 53 development\n\nautomated mechanisms supporting the capital planning and investment process" - } - ] - } - ] - }, - { - "id": "pm-4", - "class": "SP800-53", - "title": "Plan of Action and Milestones Process", - "props": [ - { - "name": "label", - "value": "PM-4" - }, - { - "name": "sort-id", - "value": "pm-04" - } - ], - "links": [ - { - "href": "#2c5884cd-7b96-425c-862a-99877e1cf909", - "rel": "reference" - }, - { - "href": "#0a0c26b6-fd44-4274-8b36-93442d49d998", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pm-4_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pm-4_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Implements a process for ensuring that plans of action and milestones for the security program and associated organizational information systems:", - "parts": [ - { - "id": "pm-4_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Are developed and maintained;" - }, - { - "id": "pm-4_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Document the remedial information security actions to adequately respond to risk to organizational operations and assets, individuals, other organizations, and the Nation; and" - }, - { - "id": "pm-4_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Are reported in accordance with OMB FISMA reporting requirements." - } - ] - }, - { - "id": "pm-4_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews plans of action and milestones for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions." - } - ] - }, - { - "id": "pm-4_gdn", - "name": "guidance", - "prose": "The plan of action and milestones is a key document in the information security program and is subject to federal reporting requirements established by OMB. With the increasing emphasis on organization-wide risk management across all three tiers in the risk management hierarchy (i.e., organization, mission/business process, and information system), organizations view plans of action and milestones from an organizational perspective, prioritizing risk response actions and ensuring consistency with the goals and objectives of the organization. Plan of action and milestones updates are based on findings from security control assessments and continuous monitoring activities. OMB FISMA reporting guidance contains instructions regarding organizational plans of action and milestones.", - "links": [ - { - "href": "#ca-5", - "rel": "related" - } - ] - }, - { - "id": "pm-4_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pm-4.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-4(a)" - } - ], - "prose": "implements a process for ensuring that plans of action and milestones for the security program and associated organizational information systems:", - "parts": [ - { - "id": "pm-4.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-4(a)(1)" - } - ], - "parts": [ - { - "id": "pm-4.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-4(a)(1)[1]" - } - ], - "prose": "are developed;" - }, - { - "id": "pm-4.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-4(a)(1)[2]" - } - ], - "prose": "are maintained;" - } - ] - }, - { - "id": "pm-4.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-4(a)(2)" - } - ], - "prose": "document the remedial information security actions to adequately respond to risk to organizational operations and assets, individuals, other organizations, and the Nation;" - }, - { - "id": "pm-4.a.3_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-4(a)(3)" - } - ], - "prose": "are reported in accordance with OMB FISMA reporting requirements;" - } - ] - }, - { - "id": "pm-4.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-4(b)" - } - ], - "prose": "reviews plans of action and milestones for consistency with:", - "parts": [ - { - "id": "pm-4.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-4(b)[1]" - } - ], - "prose": "the organizational risk management strategy; and" - }, - { - "id": "pm-4.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-4(b)[2]" - } - ], - "prose": "organization-wide priorities for risk response actions." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information security program plan\n\nplans of action and milestones\n\nprocedures addressing plans of action and milestones development and maintenance\n\nprocedures addressing plans of action and milestones reporting\n\nprocedures for review of plans of action and milestones for consistency with risk management strategy and risk response priorities\n\nresults of risk assessments associated with plans of action and milestones\n\nOMB FISMA reporting requirements\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for developing, maintaining, reviewing, and reporting plans of action and milestones\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for plan of action and milestones development, review, maintenance, reporting\n\nautomated mechanisms supporting plans of action and milestones" - } - ] - } - ] - }, - { - "id": "pm-5", - "class": "SP800-53", - "title": "Information System Inventory", - "props": [ - { - "name": "label", - "value": "PM-5" - }, - { - "name": "sort-id", - "value": "pm-05" - } - ], - "links": [ - { - "href": "#9bd19d23-025f-4a47-935e-44810a0552a4", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pm-5_smt", - "name": "statement", - "prose": "The organization develops and maintains an inventory of its information systems." - }, - { - "id": "pm-5_gdn", - "name": "guidance", - "prose": "This control addresses the inventory requirements in FISMA. OMB provides guidance on developing information systems inventories and associated reporting requirements. For specific information system inventory reporting requirements, organizations consult OMB annual FISMA reporting guidance." - }, - { - "id": "pm-5_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pm-5_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-5[1]" - } - ], - "prose": "develops an inventory of its information systems; and" - }, - { - "id": "pm-5_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-5[2]" - } - ], - "prose": "maintains the inventory of its information systems." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information security program plan\n\ninformation system inventory\n\nprocedures addressing information system inventory development and maintenance\n\nOMB FISMA reporting guidance\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security program planning and plan implementation responsibilities\n\norganizational personnel responsible for developing and maintaining the information system inventory\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for information system inventory development and maintenance\n\nautomated mechanisms supporting the information system inventory" - } - ] - } - ] - }, - { - "id": "pm-6", - "class": "SP800-53", - "title": "Information Security Measures of Performance", - "props": [ - { - "name": "label", - "value": "PM-6" - }, - { - "name": "sort-id", - "value": "pm-06" - } - ], - "links": [ - { - "href": "#83c261f0-e7a1-49f8-95ac-2ab2517644bc", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pm-6_smt", - "name": "statement", - "prose": "The organization develops, monitors, and reports on the results of information security measures of performance." - }, - { - "id": "pm-6_gdn", - "name": "guidance", - "prose": "Measures of performance are outcome-based metrics used by an organization to measure the effectiveness or efficiency of the information security program and the security controls employed in support of the program." - }, - { - "id": "pm-6_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pm-6_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-6[1]" - } - ], - "prose": "develops information security measures of performance;" - }, - { - "id": "pm-6_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-6[2]" - } - ], - "prose": "monitors information security measures of performance; and" - }, - { - "id": "pm-6_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-6[3]" - } - ], - "prose": "reports information security measures of performance." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information security program plan\n\ninformation security measures of performance\n\nprocedures addressing development, monitoring, and reporting of information security measures of performance\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security program planning and plan implementation responsibilities\n\norganizational personnel responsible for developing, monitoring, and reporting information security measures of performance\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for developing, monitoring, and reporting information security measures of performance\n\nautomated mechanisms supporting the development, monitoring, and reporting of information security measures of performance" - } - ] - } - ] - }, - { - "id": "pm-7", - "class": "SP800-53", - "title": "Enterprise Architecture", - "props": [ - { - "name": "label", - "value": "PM-7" - }, - { - "name": "sort-id", - "value": "pm-07" - } - ], - "links": [ - { - "href": "#d480aa6a-7a88-424e-a10c-ad1c7870354b", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pm-7_smt", - "name": "statement", - "prose": "The organization develops an enterprise architecture with consideration for information security and the resulting risk to organizational operations, organizational assets, individuals, other organizations, and the Nation." - }, - { - "id": "pm-7_gdn", - "name": "guidance", - "prose": "The enterprise architecture developed by the organization is aligned with the Federal Enterprise Architecture. The integration of information security requirements and associated security controls into the organization’s enterprise architecture helps to ensure that security considerations are addressed by organizations early in the system development life cycle and are directly and explicitly related to the organization’s mission/business processes. This process of security requirements integration also embeds into the enterprise architecture, an integral information security architecture consistent with organizational risk management and information security strategies. For PM-7, the information security architecture is developed at a system-of-systems level (organization-wide), representing all of the organizational information systems. For PL-8, the information security architecture is developed at a level representing an individual information system but at the same time, is consistent with the information security architecture defined for the organization. Security requirements and security control integration are most effectively accomplished through the application of the Risk Management Framework and supporting security standards and guidelines. The Federal Segment Architecture Methodology provides guidance on integrating information security requirements and security controls into enterprise architectures.", - "links": [ - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#pl-8", - "rel": "related" - }, - { - "href": "#pm-11", - "rel": "related" - }, - { - "href": "#ra-2", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - } - ] - }, - { - "id": "pm-7_obj", - "name": "objective", - "prose": "Determine if the organization develops an enterprise architecture with consideration for:", - "parts": [ - { - "id": "pm-7_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-7[1]" - } - ], - "prose": "information security; and" - }, - { - "id": "pm-7_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-7[2]" - } - ], - "prose": "the resulting risk to organizational operations, organizational assets, individuals, other organizations, and the Nation." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information security program plan\n\nenterprise architecture documentation\n\nprocedures addressing enterprise architecture development\n\nresults of risk assessment of enterprise architecture\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security program planning and plan implementation responsibilities\n\norganizational personnel responsible for developing enterprise architecture\n\norganizational personnel responsible for risk assessment of enterprise architecture\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for enterprise architecture development\n\nautomated mechanisms supporting the enterprise architecture and its development" - } - ] - } - ] - }, - { - "id": "pm-8", - "class": "SP800-53", - "title": "Critical Infrastructure Plan", - "props": [ - { - "name": "label", - "value": "PM-8" - }, - { - "name": "sort-id", - "value": "pm-08" - } - ], - "links": [ - { - "href": "#9680884b-55b7-4015-a5d7-dcb7392cb412", - "rel": "reference" - }, - { - "href": "#bd0c544a-57de-458c-9bbe-6ceac27867c8", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pm-8_smt", - "name": "statement", - "prose": "The organization addresses information security issues in the development, documentation, and updating of a critical infrastructure and key resources protection plan." - }, - { - "id": "pm-8_gdn", - "name": "guidance", - "prose": "Protection strategies are based on the prioritization of critical assets and resources. The requirement and guidance for defining critical infrastructure and key resources and for preparing an associated critical infrastructure protection plan are found in applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.", - "links": [ - { - "href": "#pm-1", - "rel": "related" - }, - { - "href": "#pm-9", - "rel": "related" - }, - { - "href": "#pm-11", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - } - ] - }, - { - "id": "pm-8_obj", - "name": "objective", - "prose": "Determine if the organization addresses information security issues in the:", - "parts": [ - { - "id": "pm-8_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-8[1]" - } - ], - "prose": "development of a critical infrastructure and key resources protection plan;" - }, - { - "id": "pm-8_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-8[2]" - } - ], - "prose": "documentation of a critical infrastructure and key resources protection plan; and" - }, - { - "id": "pm-8_obj.3", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-8[3]" - } - ], - "prose": "updating of the critical infrastructure and key resources protection plan." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information security program plan\n\ncritical infrastructure and key resources protection plan\n\nprocedures addressing development, documentation, and updating of the critical infrastructure and key resources protection plan\n\nHSPD 7\n\nNational Infrastructure Protection Plan\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security program planning and plan implementation responsibilities\n\norganizational personnel responsible for developing, documenting, and updating the critical infrastructure and key resources protection plan\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for developing, documenting, and updating the critical infrastructure and key resources protection plan\n\nautomated mechanisms supporting the development, documentation, and updating of the critical infrastructure and key resources protection plan" - } - ] - } - ] - }, - { - "id": "pm-9", - "class": "SP800-53", - "title": "Risk Management Strategy", - "params": [ - { - "id": "pm-9_prm_1", - "label": "organization-defined frequency" - } - ], - "props": [ - { - "name": "label", - "value": "PM-9" - }, - { - "name": "sort-id", - "value": "pm-09" - } - ], - "links": [ - { - "href": "#a466121b-f0e2-41f0-a5f9-deb0b5fe6b15", - "rel": "reference" - }, - { - "href": "#d480aa6a-7a88-424e-a10c-ad1c7870354b", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pm-9_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pm-9_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Develops a comprehensive strategy to manage risk to organizational operations and assets, individuals, other organizations, and the Nation associated with the operation and use of information systems;" - }, - { - "id": "pm-9_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Implements the risk management strategy consistently across the organization; and" - }, - { - "id": "pm-9_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Reviews and updates the risk management strategy {{ insert: param, pm-9_prm_1 }} or as required, to address organizational changes." - } - ] - }, - { - "id": "pm-9_gdn", - "name": "guidance", - "prose": "An organization-wide risk management strategy includes, for example, an unambiguous expression of the risk tolerance for the organization, acceptable risk assessment methodologies, risk mitigation strategies, a process for consistently evaluating risk across the organization with respect to the organization’s risk tolerance, and approaches for monitoring risk over time. The use of a risk executive function can facilitate consistent, organization-wide application of the risk management strategy. The organization-wide risk management strategy can be informed by risk-related inputs from other sources both internal and external to the organization to ensure the strategy is both broad-based and comprehensive.", - "links": [ - { - "href": "#ra-3", - "rel": "related" - } - ] - }, - { - "id": "pm-9_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pm-9.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-9(a)" - } - ], - "prose": "develops a comprehensive strategy to manage risk to organizational operations and assets, individuals, other organizations, and the Nation associated with the operation and use of information systems;" - }, - { - "id": "pm-9.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-9(b)" - } - ], - "prose": "implements the risk management strategy consistently across the organization;" - }, - { - "id": "pm-9.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-9(c)" - } - ], - "parts": [ - { - "id": "pm-9.c_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-9(c)[1]" - } - ], - "prose": "defines the frequency to review and update the risk management strategy;" - }, - { - "id": "pm-9.c_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-9(c)[2]" - } - ], - "prose": "reviews and updates the risk management strategy to address organizational changes:", - "parts": [ - { - "id": "pm-9.c_obj.2.a", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-9(c)[2][a]" - } - ], - "prose": "with the organization-defined frequency; or" - }, - { - "id": "pm-9.c_obj.2.b", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-9(c)[2][b]" - } - ], - "prose": "as required." - } - ] - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information security program plan\n\nrisk management strategy\n\nprocedures addressing development, implementation, review, and update of the risk management strategy\n\nrisk assessment results relevant to the risk management strategy\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security program planning and plan implementation responsibilities\n\norganizational personnel responsible for development, implementation, review, and update of the risk management strategy\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for development, implementation, review, and update of the risk management strategy\n\nautomated mechanisms supporting the development, implementation, review, and update of the risk management strategy" - } - ] - } - ] - }, - { - "id": "pm-10", - "class": "SP800-53", - "title": "Security Authorization Process", - "props": [ - { - "name": "label", - "value": "PM-10" - }, - { - "name": "sort-id", - "value": "pm-10" - } - ], - "links": [ - { - "href": "#0a0c26b6-fd44-4274-8b36-93442d49d998", - "rel": "reference" - }, - { - "href": "#d480aa6a-7a88-424e-a10c-ad1c7870354b", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pm-10_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pm-10_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Manages (i.e., documents, tracks, and reports) the security state of organizational information systems and the environments in which those systems operate through security authorization processes;" - }, - { - "id": "pm-10_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Designates individuals to fulfill specific roles and responsibilities within the organizational risk management process; and" - }, - { - "id": "pm-10_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "Fully integrates the security authorization processes into an organization-wide risk management program." - } - ] - }, - { - "id": "pm-10_gdn", - "name": "guidance", - "prose": "Security authorization processes for information systems and environments of operation require the implementation of an organization-wide risk management process, a Risk Management Framework, and associated security standards and guidelines. Specific roles within the risk management process include an organizational risk executive (function) and designated authorizing officials for each organizational information system and common control provider. Security authorization processes are integrated with organizational continuous monitoring processes to facilitate ongoing understanding and acceptance of risk to organizational operations and assets, individuals, other organizations, and the Nation.", - "links": [ - { - "href": "#ca-6", - "rel": "related" - } - ] - }, - { - "id": "pm-10_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pm-10.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-10(a)" - } - ], - "prose": "manages (i.e., documents, tracks, and reports) the security state of organizational information systems and the environments in which those systems operate through security authorization processes;" - }, - { - "id": "pm-10.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-10(b)" - } - ], - "prose": "designates individuals to fulfill specific roles and responsibilities within the organizational risk management process; and" - }, - { - "id": "pm-10.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-10(c)" - } - ], - "prose": "fully integrates the security authorization processes into an organization-wide risk management program." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information security program plan\n\nprocedures addressing management (i.e., documentation, tracking, and reporting) of the security authorization process\n\nsecurity authorization documents\n\nlists or other documentation about security authorization process roles and responsibilities\n\nrisk assessment results relevant to the security authorization process and the organization-wide risk management program\n\norganizational risk management strategy\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security program planning and plan implementation responsibilities\n\norganizational personnel responsible for management of the security authorization process\n\nauthorizing officials\n\nsystem owners, senior information security officer\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for security authorization\n\nautomated mechanisms supporting the security authorization process" - } - ] - } - ] - }, - { - "id": "pm-11", - "class": "SP800-53", - "title": "Mission/business Process Definition", - "props": [ - { - "name": "label", - "value": "PM-11" - }, - { - "name": "sort-id", - "value": "pm-11" - } - ], - "links": [ - { - "href": "#e85cdb3f-7f0a-4083-8639-f13f70d3760b", - "rel": "reference" - }, - { - "href": "#f152844f-b1ef-4836-8729-6277078ebee1", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pm-11_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pm-11_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Defines mission/business processes with consideration for information security and the resulting risk to organizational operations, organizational assets, individuals, other organizations, and the Nation; and" - }, - { - "id": "pm-11_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Determines information protection needs arising from the defined mission/business processes and revises the processes as necessary, until achievable protection needs are obtained." - } - ] - }, - { - "id": "pm-11_gdn", - "name": "guidance", - "prose": "Information protection needs are technology-independent, required capabilities to counter threats to organizations, individuals, or the Nation through the compromise of information (i.e., loss of confidentiality, integrity, or availability). Information protection needs are derived from the mission/business needs defined by the organization, the mission/business processes selected to meet the stated needs, and the organizational risk management strategy. Information protection needs determine the required security controls for the organization and the associated information systems supporting the mission/business processes. Inherent in defining an organization’s information protection needs is an understanding of the level of adverse impact that could result if a compromise of information occurs. The security categorization process is used to make such potential impact determinations. Mission/business process definitions and associated information protection requirements are documented by the organization in accordance with organizational policy and procedure.", - "links": [ - { - "href": "#pm-7", - "rel": "related" - }, - { - "href": "#pm-8", - "rel": "related" - }, - { - "href": "#ra-2", - "rel": "related" - } - ] - }, - { - "id": "pm-11_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pm-11.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-11(a)" - } - ], - "prose": "defines mission/business processes with consideration for information security and the resulting risk to organizational operations, organizational assets, individuals, other organizations, and the Nation;" - }, - { - "id": "pm-11.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-11(b)" - } - ], - "parts": [ - { - "id": "pm-11.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-11(b)[1]" - } - ], - "prose": "determines information protection needs arising from the defined mission/business process; and" - }, - { - "id": "pm-11.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-11(b)[2]" - } - ], - "prose": "revises the processes as necessary until achievable protection needs are obtained." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information security program plan\n\nrisk management strategy\n\nprocedures for determining mission/business protection needs\n\nrisk assessment results relevant to determination of mission/business protection needs\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security program planning and plan implementation responsibilities\n\norganizational personnel responsible for mission/business processes\n\norganizational personnel responsible for determining information protection needs for mission/business processes\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for defining mission/business processes and their information protection needs" - } - ] - } - ] - }, - { - "id": "pm-12", - "class": "SP800-53", - "title": "Insider Threat Program", - "props": [ - { - "name": "label", - "value": "PM-12" - }, - { - "name": "sort-id", - "value": "pm-12" - } - ], - "links": [ - { - "href": "#c5034e0c-eba6-4ecd-a541-79f0678f4ba4", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pm-12_smt", - "name": "statement", - "prose": "The organization implements an insider threat program that includes a cross-discipline insider threat incident handling team." - }, - { - "id": "pm-12_gdn", - "name": "guidance", - "prose": "Organizations handling classified information are required, under Executive Order 13587 and the National Policy on Insider Threat, to establish insider threat programs. The standards and guidelines that apply to insider threat programs in classified environments can also be employed effectively to improve the security of Controlled Unclassified Information in non-national security systems. Insider threat programs include security controls to detect and prevent malicious insider activity through the centralized integration and analysis of both technical and non-technical information to identify potential insider threat concerns. A senior organizational official is designated by the department/agency head as the responsible individual to implement and provide oversight for the program. In addition to the centralized integration and analysis capability, insider threat programs as a minimum, prepare department/agency insider threat policies and implementation plans, conduct host-based user monitoring of individual employee activities on government-owned classified computers, provide insider threat awareness training to employees, receive access to information from all offices within the department/agency (e.g., human resources, legal, physical security, personnel security, information technology, information system security, and law enforcement) for insider threat analysis, and conduct self-assessments of department/agency insider threat posture. Insider threat programs can leverage the existence of incident handling teams organizations may already have in place, such as computer security incident response teams. Human resources records are especially important in this effort, as there is compelling evidence to show that some types of insider crimes are often preceded by nontechnical behaviors in the workplace (e.g., ongoing patterns of disgruntled behavior and conflicts with coworkers and other colleagues). These precursors can better inform and guide organizational officials in more focused, targeted monitoring efforts. The participation of a legal team is important to ensure that all monitoring activities are performed in accordance with appropriate legislation, directives, regulations, policies, standards, and guidelines.", - "links": [ - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-7", - "rel": "related" - }, - { - "href": "#au-10", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "#au-13", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#mp-7", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#ps-3", - "rel": "related" - }, - { - "href": "#ps-4", - "rel": "related" - }, - { - "href": "#ps-5", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-38", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#pm-1", - "rel": "related" - }, - { - "href": "#pm-14", - "rel": "related" - } - ] - }, - { - "id": "pm-12_obj", - "name": "objective", - "prose": "Determine if the organization implements an insider threat program that includes a cross-discipline insider threat incident handling team." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information security program plan\n\ninsider threat program documentation\n\nprocedures for the insider threat program\n\nrisk assessment results relevant to insider threats\n\nlist or other documentation on the cross-discipline insider threat incident handling team\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security program planning and plan implementation responsibilities\n\norganizational personnel responsible for the insider threat program\n\nmembers of the cross-discipline insider threat incident handling team\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for implementing the insider threat program and the cross-discipline insider threat incident handling team\n\nautomated mechanisms supporting and/or implementing the insider threat program and the cross-discipline insider threat incident handling team" - } - ] - } - ] - }, - { - "id": "pm-13", - "class": "SP800-53", - "title": "Information Security Workforce", - "props": [ - { - "name": "label", - "value": "PM-13" - }, - { - "name": "sort-id", - "value": "pm-13" - } - ], - "parts": [ - { - "id": "pm-13_smt", - "name": "statement", - "prose": "The organization establishes an information security workforce development and improvement program." - }, - { - "id": "pm-13_gdn", - "name": "guidance", - "prose": "Information security workforce development and improvement programs include, for example: (i) defining the knowledge and skill levels needed to perform information security duties and tasks; (ii) developing role-based training programs for individuals assigned information security roles and responsibilities; and (iii) providing standards for measuring and building individual qualifications for incumbents and applicants for information security-related positions. Such workforce programs can also include associated information security career paths to encourage: (i) information security professionals to advance in the field and fill positions with greater responsibility; and (ii) organizations to fill information security-related positions with qualified personnel. Information security workforce development and improvement programs are complementary to organizational security awareness and training programs. Information security workforce development and improvement programs focus on developing and institutionalizing core information security capabilities of selected personnel needed to protect organizational operations, assets, and individuals.", - "links": [ - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - } - ] - }, - { - "id": "pm-13_obj", - "name": "objective", - "prose": "Determine if the organization establishes an information security workforce development and improvement program." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information security program plan\n\ninformation security workforce development and improvement program documentation\n\nprocedures for the information security workforce development and improvement program\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security program planning and plan implementation responsibilities\n\norganizational personnel responsible for the information security workforce development and improvement program\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for implementing information security workforce development and improvement program\n\nautomated mechanisms supporting and/or implementing the information security workforce development and improvement program" - } - ] - } - ] - }, - { - "id": "pm-14", - "class": "SP800-53", - "title": "Testing, Training, and Monitoring", - "props": [ - { - "name": "label", - "value": "PM-14" - }, - { - "name": "sort-id", - "value": "pm-14" - } - ], - "links": [ - { - "href": "#825438c3-248d-4e30-a51e-246473ce6ada", - "rel": "reference" - }, - { - "href": "#0a0c26b6-fd44-4274-8b36-93442d49d998", - "rel": "reference" - }, - { - "href": "#cd4cf751-3312-4a55-b1a9-fad2f1db9119", - "rel": "reference" - }, - { - "href": "#cee2c6ca-0261-4a6f-b630-e41d8ffdd82b", - "rel": "reference" - } - ], - "parts": [ - { - "id": "pm-14_smt", - "name": "statement", - "prose": "The organization:", - "parts": [ - { - "id": "pm-14_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "Implements a process for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational information systems:", - "parts": [ - { - "id": "pm-14_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Are developed and maintained; and" - }, - { - "id": "pm-14_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Continue to be executed in a timely manner;" - } - ] - }, - { - "id": "pm-14_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "Reviews testing, training, and monitoring plans for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions." - } - ] - }, - { - "id": "pm-14_gdn", - "name": "guidance", - "prose": "This control ensures that organizations provide oversight for the security testing, training, and monitoring activities conducted organization-wide and that those activities are coordinated. With the importance of continuous monitoring programs, the implementation of information security across the three tiers of the risk management hierarchy, and the widespread use of common controls, organizations coordinate and consolidate the testing and monitoring activities that are routinely conducted as part of ongoing organizational assessments supporting a variety of security controls. Security training activities, while typically focused on individual information systems and specific roles, also necessitate coordination across all organizational elements. Testing, training, and monitoring plans and activities are informed by current threat and vulnerability assessments.", - "links": [ - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cp-4", - "rel": "related" - }, - { - "href": "#ir-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ] - }, - { - "id": "pm-14_obj", - "name": "objective", - "prose": "Determine if the organization:", - "parts": [ - { - "id": "pm-14.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-14(a)" - } - ], - "prose": "implements a process for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational information systems:", - "parts": [ - { - "id": "pm-14.a.1_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-14(a)(1)" - } - ], - "parts": [ - { - "id": "pm-14.a.1_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-14(a)(1)[1]" - } - ], - "prose": "are developed;" - }, - { - "id": "pm-14.a.1_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-14(a)(1)[2]" - } - ], - "prose": "are maintained;" - } - ] - }, - { - "id": "pm-14.a.2_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-14(a)(2)" - } - ], - "prose": "continue to be executed in a timely manner;" - } - ] - }, - { - "id": "pm-14.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-14(b)" - } - ], - "prose": "reviews testing, training, and monitoring plans for consistency with:", - "parts": [ - { - "id": "pm-14.b_obj.1", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-14(b)[1]" - } - ], - "prose": "the organizational risk management strategy; and" - }, - { - "id": "pm-14.b_obj.2", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-14(b)[2]" - } - ], - "prose": "organization-wide priorities for risk response actions." - } - ] - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information security program plan\n\nplans for conducting security testing, training, and monitoring activities\n\norganizational procedures addressing development and maintenance of plans for conducting security testing, training, and monitoring activities\n\nrisk management strategy\n\nprocedures for review of plans for conducting security testing, training, and monitoring activities for consistency with risk management strategy and risk response priorities\n\nresults of risk assessments associated with conducting security testing, training, and monitoring activities\n\nevidence that plans for conducting security testing, training, and monitoring activities are executed in a timely manner\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with responsibility for developing and maintaining plans for conducting security testing, training, and monitoring activities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for development and maintenance of plans for conducting security testing, training, and monitoring activities\n\nautomated mechanisms supporting development and maintenance of plans for conducting security testing, training, and monitoring activities" - } - ] - } - ] - }, - { - "id": "pm-15", - "class": "SP800-53", - "title": "Contacts with Security Groups and Associations", - "props": [ - { - "name": "label", - "value": "PM-15" - }, - { - "name": "sort-id", - "value": "pm-15" - } - ], - "parts": [ - { - "id": "pm-15_smt", - "name": "statement", - "prose": "The organization establishes and institutionalizes contact with selected groups and associations within the security community:", - "parts": [ - { - "id": "pm-15_smt.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "a." - } - ], - "prose": "To facilitate ongoing security education and training for organizational personnel;" - }, - { - "id": "pm-15_smt.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "b." - } - ], - "prose": "To maintain currency with recommended security practices, techniques, and technologies; and" - }, - { - "id": "pm-15_smt.c", - "name": "item", - "props": [ - { - "name": "label", - "value": "c." - } - ], - "prose": "To share current security-related information including threats, vulnerabilities, and incidents." - } - ] - }, - { - "id": "pm-15_gdn", - "name": "guidance", - "prose": "Ongoing contact with security groups and associations is of paramount importance in an environment of rapidly changing technologies and threats. Security groups and associations include, for example, special interest groups, forums, professional associations, news groups, and/or peer groups of security professionals in similar organizations. Organizations select groups and associations based on organizational missions/business functions. Organizations share threat, vulnerability, and incident information consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.", - "links": [ - { - "href": "#si-5", - "rel": "related" - } - ] - }, - { - "id": "pm-15_obj", - "name": "objective", - "prose": "Determine if the organization establishes and institutionalizes contact with selected groups and associations with the security community to:", - "parts": [ - { - "id": "pm-15.a_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-15(a)" - } - ], - "prose": "facilitate ongoing security education and training for organizational personnel;" - }, - { - "id": "pm-15.b_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-15(b)" - } - ], - "prose": "maintain currency with recommended security practices, techniques, and technologies; and" - }, - { - "id": "pm-15.c_obj", - "name": "objective", - "props": [ - { - "name": "label", - "value": "PM-15(c)" - } - ], - "prose": "share current security-related information including threats, vulnerabilities, and incidents." - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information security program plan\n\nrisk management strategy\n\nprocedures for contacts with security groups and associations\n\nevidence of established and institutionalized contact with security groups and associations\n\nlists or other documentation about contact with and/or membership in security groups and associations\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security program planning and plan implementation responsibilities\n\norganizational personnel responsible for establishing and institutionalizing contact with security groups and associations\n\norganizational personnel with information security responsibilities\n\npersonnel from selected groups and associations with which the organization has established and institutionalized contact" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for establishing and institutionalizing contact with security groups and associations\n\nautomated mechanisms supporting contacts with security groups and associations" - } - ] - } - ] - }, - { - "id": "pm-16", - "class": "SP800-53", - "title": "Threat Awareness Program", - "props": [ - { - "name": "label", - "value": "PM-16" - }, - { - "name": "sort-id", - "value": "pm-16" - } - ], - "parts": [ - { - "id": "pm-16_smt", - "name": "statement", - "prose": "The organization implements a threat awareness program that includes a cross-organization information-sharing capability." - }, - { - "id": "pm-16_gdn", - "name": "guidance", - "prose": "Because of the constantly changing and increasing sophistication of adversaries, especially the advanced persistent threat (APT), it is becoming more likely that adversaries may successfully breach or compromise organizational information systems. One of the best techniques to address this concern is for organizations to share threat information. This can include, for example, sharing threat events (i.e., tactics, techniques, and procedures) that organizations have experienced, mitigations that organizations have found are effective against certain types of threats, threat intelligence (i.e., indications and warnings about threats that are likely to occur). Threat information sharing may be bilateral (e.g., government-commercial cooperatives, government-government cooperatives), or multilateral (e.g., organizations taking part in threat-sharing consortia). Threat information may be highly sensitive requiring special agreements and protection, or less sensitive and freely shared.", - "links": [ - { - "href": "#pm-12", - "rel": "related" - }, - { - "href": "#pm-16", - "rel": "related" - } - ] - }, - { - "id": "pm-16_obj", - "name": "objective", - "prose": "Determine if the organization implements a threat awareness program that includes a cross-organization information-sharing capability." - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "EXAMINE" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Information security program plan\n\nthreat awareness program documentation\n\nprocedures for the threat awareness program\n\nrisk assessment results relevant to threat awareness\n\nlist or other documentation on the cross-organization information-sharing capability\n\nother relevant documents or records" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "INTERVIEW" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational personnel with information security program planning and plan implementation responsibilities\n\norganizational personnel responsible for the threat awareness program\n\norganizational personnel with responsibility for the cross-organization information-sharing capability\n\norganizational personnel with information security responsibilities\n\npersonnel with whom threat awareness information is shared by the organization" - } - ] - }, - { - "name": "assessment", - "props": [ - { - "name": "method", - "value": "TEST" - } - ], - "parts": [ - { - "name": "objects", - "prose": "Organizational processes for implementing the threat awareness program\n\nOrganizational processes for implementing the cross-organization information-sharing capability\n\nautomated mechanisms supporting and/or implementing the threat awareness program\n\nautomated mechanisms supporting and/or implementing the cross-organization information-sharing capability" - } - ] - } - ] - } - ] - } - ], - "back-matter": { - "resources": [ - { - "uuid": "0c97e60b-325a-4efa-ba2b-90f20ccd5abc", - "title": "5 C.F.R. 731.106", - "citation": { - "text": "Code of Federal Regulations, Title 5, Administrative Personnel, Section 731.106, Designation of Public Trust Positions and Investigative Requirements (5 C.F.R. 731.106)." - }, - "rlinks": [ - { - "href": "http://www.gpo.gov/fdsys/granule/CFR-2012-title5-vol2/CFR-2012-title5-vol2-sec731-106/content-detail.html" - } - ] - }, - { - "uuid": "bb61234b-46c3-4211-8c2b-9869222a720d", - "title": "C.F.R. Part 5 Subpart C (5 C.F.R. 930.301)", - "citation": { - "text": "C.F.R. Part 5 Subpart C (5 C.F.R. 930.301)" - }, - "rlinks": [ - { - "href": "http://www.gpo.gov/fdsys/granule/CFR-2009-title5-vol2/CFR-2009-title5-vol2-sec930-301/content-detail.html" - } - ] - }, - { - "uuid": "a4aa9645-9a8a-4b51-90a9-e223250f9a75", - "title": "CNSS Policy 15", - "citation": { - "text": "CNSS Policy 15" - }, - "rlinks": [ - { - "href": "https://www.cnss.gov/policies.html" - } - ] - }, - { - "uuid": "2d8b14e9-c8b5-4d3d-8bdc-155078f3281b", - "title": "DoD Information Assurance Vulnerability Alerts", - "citation": { - "text": "DoD Information Assurance Vulnerability Alerts" - } - }, - { - "uuid": "61081e7f-041d-4033-96a7-44a439071683", - "title": "DoD Instruction 5200.39", - "citation": { - "text": "DoD Instruction 5200.39" - }, - "rlinks": [ - { - "href": "http://www.dtic.mil/whs/directives/corres/ins1.html" - } - ] - }, - { - "uuid": "e42b2099-3e1c-415b-952c-61c96533c12e", - "title": "DoD Instruction 8551.01", - "citation": { - "text": "DoD Instruction 8551.01" - }, - "rlinks": [ - { - "href": "http://www.dtic.mil/whs/directives/corres/ins1.html" - } - ] - }, - { - "uuid": "e6522953-6714-435d-a0d3-140df554c186", - "title": "DoD Instruction 8552.01", - "citation": { - "text": "DoD Instruction 8552.01" - }, - "rlinks": [ - { - "href": "http://www.dtic.mil/whs/directives/corres/ins1.html" - } - ] - }, - { - "uuid": "c5034e0c-eba6-4ecd-a541-79f0678f4ba4", - "title": "Executive Order 13587", - "citation": { - "text": "Executive Order 13587" - }, - "rlinks": [ - { - "href": "http://www.whitehouse.gov/the-press-office/2011/10/07/executive-order-13587-structural-reforms-improve-security-classified-net" - } - ] - }, - { - "uuid": "56d671da-6b7b-4abf-8296-84b61980390a", - "title": "Federal Acquisition Regulation", - "citation": { - "text": "Federal Acquisition Regulation" - }, - "rlinks": [ - { - "href": "https://acquisition.gov/far" - } - ] - }, - { - "uuid": "023104bc-6f75-4cd5-b7d0-fc92326f8007", - "title": "Federal Continuity Directive 1", - "citation": { - "text": "Federal Continuity Directive 1" - }, - "rlinks": [ - { - "href": "http://www.fema.gov/pdf/about/offices/fcd1.pdf" - } - ] - }, - { - "uuid": "ba557c91-ba3e-4792-adc6-a4ae479b39ff", - "title": "FICAM Roadmap and Implementation Guidance", - "citation": { - "text": "FICAM Roadmap and Implementation Guidance" - }, - "rlinks": [ - { - "href": "http://www.idmanagement.gov/documents/ficam-roadmap-and-implementation-guidance" - } - ] - }, - { - "uuid": "39f9087d-7687-46d2-8eda-b6f4b7a4d8a9", - "title": "FIPS Publication 140", - "citation": { - "text": "FIPS Publication 140" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsFIPS.html" - } - ] - }, - { - "uuid": "d715b234-9b5b-4e07-b1ed-99836727664d", - "title": "FIPS Publication 140-2", - "citation": { - "text": "FIPS Publication 140-2" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsFIPS.html#140-2" - } - ] - }, - { - "uuid": "f2dbd4ec-c413-4714-b85b-6b7184d1c195", - "title": "FIPS Publication 197", - "citation": { - "text": "FIPS Publication 197" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsFIPS.html#197" - } - ] - }, - { - "uuid": "e85cdb3f-7f0a-4083-8639-f13f70d3760b", - "title": "FIPS Publication 199", - "citation": { - "text": "FIPS Publication 199" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsFIPS.html#199" - } - ] - }, - { - "uuid": "aba82822-b6e6-4abe-af2e-3fdd68f0bcf8", - "title": "FIPS Publication 200", - "citation": { - "text": "FIPS Publication 200" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsFIPS.html#200" - } - ] - }, - { - "uuid": "c80c10b3-1294-4984-a4cc-d1733ca432b9", - "title": "FIPS Publication 201", - "citation": { - "text": "FIPS Publication 201" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsFIPS.html#201" - } - ] - }, - { - "uuid": "ad733a42-a7ed-4774-b988-4930c28852f3", - "title": "HSPD-12", - "citation": { - "text": "HSPD-12" - }, - "rlinks": [ - { - "href": "http://www.dhs.gov/homeland-security-presidential-directive-12" - } - ] - }, - { - "uuid": "9680884b-55b7-4015-a5d7-dcb7392cb412", - "title": "HSPD 7", - "citation": { - "text": "HSPD 7" - }, - "rlinks": [ - { - "href": "http://www.fas.org/irp/offdocs/nspd/hspd-7.html" - } - ] - }, - { - "uuid": "4ef539ba-b767-4666-b0d3-168c53005fa3", - "title": "http://capec.mitre.org", - "citation": { - "text": "http://capec.mitre.org" - }, - "rlinks": [ - { - "href": "http://capec.mitre.org" - } - ] - }, - { - "uuid": "e95dd121-2733-413e-bf1e-f1eb49f20a98", - "title": "http://checklists.nist.gov", - "citation": { - "text": "http://checklists.nist.gov" - }, - "rlinks": [ - { - "href": "http://checklists.nist.gov" - } - ] - }, - { - "uuid": "6a1041fc-054e-4230-946b-2e6f4f3731bb", - "title": "http://csrc.nist.gov/cryptval", - "citation": { - "text": "http://csrc.nist.gov/cryptval" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/cryptval" - } - ] - }, - { - "uuid": "b09d1a31-d3c9-4138-a4f4-4c63816afd7d", - "title": "http://csrc.nist.gov/groups/STM/cmvp/index.html", - "citation": { - "text": "http://csrc.nist.gov/groups/STM/cmvp/index.html" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/groups/STM/cmvp/index.html" - } - ] - }, - { - "uuid": "0931209f-00ae-4132-b92c-bc645847e8f9", - "title": "http://cve.mitre.org", - "citation": { - "text": "http://cve.mitre.org" - }, - "rlinks": [ - { - "href": "http://cve.mitre.org" - } - ] - }, - { - "uuid": "15522e92-9192-463d-9646-6a01982db8ca", - "title": "http://cwe.mitre.org", - "citation": { - "text": "http://cwe.mitre.org" - }, - "rlinks": [ - { - "href": "http://cwe.mitre.org" - } - ] - }, - { - "uuid": "5ed1f4d5-1494-421b-97ed-39d3c88ab51f", - "title": "http://fips201ep.cio.gov", - "citation": { - "text": "http://fips201ep.cio.gov" - }, - "rlinks": [ - { - "href": "http://fips201ep.cio.gov" - } - ] - }, - { - "uuid": "85280698-0417-489d-b214-12bb935fb939", - "title": "http://idmanagement.gov", - "citation": { - "text": "http://idmanagement.gov" - }, - "rlinks": [ - { - "href": "http://idmanagement.gov" - } - ] - }, - { - "uuid": "275cc052-0f7f-423c-bdb6-ed503dc36228", - "title": "http://nvd.nist.gov", - "citation": { - "text": "http://nvd.nist.gov" - }, - "rlinks": [ - { - "href": "http://nvd.nist.gov" - } - ] - }, - { - "uuid": "bbd50dd1-54ce-4432-959d-63ea564b1bb4", - "title": "http://www.acquisition.gov/far", - "citation": { - "text": "http://www.acquisition.gov/far" - }, - "rlinks": [ - { - "href": "http://www.acquisition.gov/far" - } - ] - }, - { - "uuid": "9b97ed27-3dd6-4f9a-ade5-1b43e9669794", - "title": "http://www.cnss.gov", - "citation": { - "text": "http://www.cnss.gov" - }, - "rlinks": [ - { - "href": "http://www.cnss.gov" - } - ] - }, - { - "uuid": "3ac12e79-f54f-4a63-9f4b-ee4bcd4df604", - "title": "http://www.dhs.gov/telecommunications-service-priority-tsp", - "citation": { - "text": "http://www.dhs.gov/telecommunications-service-priority-tsp" - }, - "rlinks": [ - { - "href": "http://www.dhs.gov/telecommunications-service-priority-tsp" - } - ] - }, - { - "uuid": "c95a9986-3cd6-4a98-931b-ccfc56cb11e5", - "title": "http://www.niap-ccevs.org", - "citation": { - "text": "http://www.niap-ccevs.org" - }, - "rlinks": [ - { - "href": "http://www.niap-ccevs.org" - } - ] - }, - { - "uuid": "647b6de3-81d0-4d22-bec1-5f1333e34380", - "title": "http://www.nsa.gov", - "citation": { - "text": "http://www.nsa.gov" - }, - "rlinks": [ - { - "href": "http://www.nsa.gov" - } - ] - }, - { - "uuid": "a47466c4-c837-4f06-a39f-e68412a5f73d", - "title": "http://www.nsa.gov/ia/mitigation_guidance/media_destruction_guidance/index.shtml", - "citation": { - "text": "http://www.nsa.gov/ia/mitigation_guidance/media_destruction_guidance/index.shtml" - }, - "rlinks": [ - { - "href": "http://www.nsa.gov/ia/mitigation_guidance/media_destruction_guidance/index.shtml" - } - ] - }, - { - "uuid": "9bd19d23-025f-4a47-935e-44810a0552a4", - "title": "http://www.omb.gov", - "citation": { - "text": "http://www.omb.gov" - }, - "rlinks": [ - { - "href": "http://www.omb.gov" - } - ] - }, - { - "uuid": "02631467-668b-4233-989b-3dfded2fd184", - "title": "http://www.us-cert.gov", - "citation": { - "text": "http://www.us-cert.gov" - }, - "rlinks": [ - { - "href": "http://www.us-cert.gov" - } - ] - }, - { - "uuid": "6caa237b-531b-43ac-9711-d8f6b97b0377", - "title": "ICD 704", - "citation": { - "text": "ICD 704" - }, - "rlinks": [ - { - "href": "http://www.dni.gov/index.php/intelligence-community/ic-policies-reports/intelligence-community-directives" - } - ] - }, - { - "uuid": "398e33fd-f404-4e5c-b90e-2d50d3181244", - "title": "ICD 705", - "citation": { - "text": "ICD 705" - }, - "rlinks": [ - { - "href": "http://www.dni.gov/index.php/intelligence-community/ic-policies-reports/intelligence-community-directives" - } - ] - }, - { - "uuid": "1737a687-52fb-4008-b900-cbfa836f7b65", - "title": "ISO/IEC 15408", - "citation": { - "text": "ISO/IEC 15408" - }, - "rlinks": [ - { - "href": "http://www.iso.org/iso/iso_catalog/catalog_tc/catalog_detail.htm?csnumber=50341" - } - ] - }, - { - "uuid": "fb5844de-ff96-47c0-b258-4f52bcc2f30d", - "title": "National Communications Systems Directive 3-10", - "citation": { - "text": "National Communications Systems Directive 3-10" - } - }, - { - "uuid": "bd0c544a-57de-458c-9bbe-6ceac27867c8", - "title": "National Infrastructure Protection Plan", - "citation": { - "text": "National Infrastructure Protection Plan" - }, - "rlinks": [ - { - "href": "https://www.dhs.gov/national-infrastructure-protection-plan" - } - ] - }, - { - "uuid": "654f21e2-f3bc-43b2-abdc-60ab8d09744b", - "title": "National Strategy for Trusted Identities in Cyberspace", - "citation": { - "text": "National Strategy for Trusted Identities in Cyberspace" - }, - "rlinks": [ - { - "href": "http://www.nist.gov/nstic" - } - ] - }, - { - "uuid": "bdd2f49e-edf7-491f-a178-4487898228f3", - "title": "NIST Interagency Report 7622", - "citation": { - "text": "NIST Interagency Report 7622" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsNISTIRs.html#NIST-IR-7622" - } - ] - }, - { - "uuid": "9cb3d8fe-2127-48ba-821e-cdd2d7aee921", - "title": "NIST Special Publication 800-100", - "document-ids": [ - { - "scheme": "https://www.doi.org/", - "identifier": "10.6028/NIST.SP.800-100" - } - ], - "citation": { - "text": "NIST Special Publication 800-100" - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-100" - } - ] - }, - { - "uuid": "3cac5e7b-9ebf-4bbb-9af5-ae032de78e8e", - "title": "NIST Special Publication 800-111", - "document-ids": [ - { - "scheme": "https://www.doi.org/", - "identifier": "10.6028/NIST.SP.800-111" - } - ], - "citation": { - "text": "NIST Special Publication 800-111" - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-111" - } - ] - }, - { - "uuid": "349fe082-502d-464a-aa0c-1443c6a5cf40", - "title": "NIST Special Publication 800-113", - "document-ids": [ - { - "scheme": "https://www.doi.org/", - "identifier": "10.6028/NIST.SP.800-113" - } - ], - "citation": { - "text": "NIST Special Publication 800-113" - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-113" - } - ] - }, - { - "uuid": "1201fcf3-afb1-4675-915a-fb4ae0435717", - "title": "NIST Special Publication 800-114 Rev. 1", - "document-ids": [ - { - "scheme": "https://www.doi.org/", - "identifier": "10.6028/NIST.SP.800-114r1" - } - ], - "citation": { - "text": "NIST Special Publication 800-114 Rev. 1" - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-114r1" - } - ] - }, - { - "uuid": "c4691b88-57d1-463b-9053-2d0087913f31", - "title": "NIST Special Publication 800-115", - "document-ids": [ - { - "scheme": "https://www.doi.org/", - "identifier": "10.6028/NIST.SP.800-115" - } - ], - "citation": { - "text": "NIST Special Publication 800-115" - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-115" - } - ] - }, - { - "uuid": "2157bb7e-192c-4eaa-877f-93ef6b0a3292", - "title": "NIST Special Publication 800-116 Rev. 1", - "document-ids": [ - { - "scheme": "https://www.doi.org/", - "identifier": "10.6028/NIST.SP.800-116r1" - } - ], - "citation": { - "text": "NIST Special Publication 800-116 Rev. 1" - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-116r1" - } - ] - }, - { - "uuid": "5c201b63-0768-417b-ac22-3f014e3941b2", - "title": "NIST Special Publication 800-12 Rev. 1", - "document-ids": [ - { - "scheme": "https://www.doi.org/", - "identifier": "10.6028/NIST.SP.800-12r1" - } - ], - "citation": { - "text": "NIST Special Publication 800-12 Rev. 1" - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-12r1" - } - ] - }, - { - "uuid": "d1a4e2a9-e512-4132-8795-5357aba29254", - "title": "NIST Special Publication 800-121", - "citation": { - "text": "NIST Special Publication 800-121" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-121" - } - ] - }, - { - "uuid": "0293a393-fbe8-4ed1-b0b4-f6fbd3ae1589", - "title": "NIST Special Publication 800-124", - "citation": { - "text": "NIST Special Publication 800-124" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-124" - } - ] - }, - { - "uuid": "080f8068-5e3e-435e-9790-d22ba4722693", - "title": "NIST Special Publication 800-128", - "citation": { - "text": "NIST Special Publication 800-128" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-128" - } - ] - }, - { - "uuid": "cee2c6ca-0261-4a6f-b630-e41d8ffdd82b", - "title": "NIST Special Publication 800-137", - "citation": { - "text": "NIST Special Publication 800-137" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-137" - } - ] - }, - { - "uuid": "6bf8d24a-78dc-4727-a2ac-0e64d71c495c", - "title": "NIST Special Publication 800-147", - "citation": { - "text": "NIST Special Publication 800-147" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-147" - } - ] - }, - { - "uuid": "3878cc04-144a-483e-af62-8fe6f4ad6c7a", - "title": "NIST Special Publication 800-155", - "citation": { - "text": "NIST Special Publication 800-155" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-155" - } - ] - }, - { - "uuid": "825438c3-248d-4e30-a51e-246473ce6ada", - "title": "NIST Special Publication 800-16", - "citation": { - "text": "NIST Special Publication 800-16" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-16" - } - ] - }, - { - "uuid": "8ab6bcdc-339b-4068-b45e-994814a6e187", - "title": "NIST Special Publication 800-161", - "citation": { - "text": "NIST Special Publication 800-161" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-161" - } - ] - }, - { - "uuid": "6513e480-fada-4876-abba-1397084dfb26", - "title": "NIST Special Publication 800-164", - "citation": { - "text": "NIST Special Publication 800-164" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-164" - } - ] - }, - { - "uuid": "9c5c9e8c-dc81-4f55-a11c-d71d7487790f", - "title": "NIST Special Publication 800-18", - "citation": { - "text": "NIST Special Publication 800-18" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-18" - } - ] - }, - { - "uuid": "0a5db899-f033-467f-8631-f5a8ba971475", - "title": "NIST Special Publication 800-23", - "citation": { - "text": "NIST Special Publication 800-23" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-23" - } - ] - }, - { - "uuid": "21b1ed35-56d2-40a8-bdfe-b461fffe322f", - "title": "NIST Special Publication 800-27", - "citation": { - "text": "NIST Special Publication 800-27" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-27" - } - ] - }, - { - "uuid": "e716cd51-d1d5-4c6a-967a-22e9fbbc42f1", - "title": "NIST Special Publication 800-28", - "citation": { - "text": "NIST Special Publication 800-28" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-28" - } - ] - }, - { - "uuid": "a466121b-f0e2-41f0-a5f9-deb0b5fe6b15", - "title": "NIST Special Publication 800-30", - "citation": { - "text": "NIST Special Publication 800-30" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-30" - } - ] - }, - { - "uuid": "8f174e91-844e-4cf1-a72a-45c119a3a8dd", - "title": "NIST Special Publication 800-32", - "citation": { - "text": "NIST Special Publication 800-32" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-32" - } - ] - }, - { - "uuid": "748a81b9-9cad-463f-abde-8b368167e70d", - "title": "NIST Special Publication 800-34", - "citation": { - "text": "NIST Special Publication 800-34" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-34" - } - ] - }, - { - "uuid": "0c775bc3-bfc3-42c7-a382-88949f503171", - "title": "NIST Special Publication 800-35", - "citation": { - "text": "NIST Special Publication 800-35" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-35" - } - ] - }, - { - "uuid": "d818efd3-db31-4953-8afa-9e76afe83ce2", - "title": "NIST Special Publication 800-36", - "citation": { - "text": "NIST Special Publication 800-36" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-36" - } - ] - }, - { - "uuid": "0a0c26b6-fd44-4274-8b36-93442d49d998", - "title": "NIST Special Publication 800-37", - "citation": { - "text": "NIST Special Publication 800-37" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-37" - } - ] - }, - { - "uuid": "d480aa6a-7a88-424e-a10c-ad1c7870354b", - "title": "NIST Special Publication 800-39", - "citation": { - "text": "NIST Special Publication 800-39" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-39" - } - ] - }, - { - "uuid": "bdd14f6c-41ab-4277-8d74-a0ce75a0eb1d", - "title": "NIST Special Publication 800-40", - "citation": { - "text": "NIST Special Publication 800-40" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-40" - } - ] - }, - { - "uuid": "756a8e86-57d5-4701-8382-f7a40439665a", - "title": "NIST Special Publication 800-41", - "citation": { - "text": "NIST Special Publication 800-41" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-41" - } - ] - }, - { - "uuid": "c6e95ca0-5828-420e-b095-00895b72b5e8", - "title": "NIST Special Publication 800-45", - "citation": { - "text": "NIST Special Publication 800-45" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-45" - } - ] - }, - { - "uuid": "5309d4d0-46f8-4213-a749-e7584164e5e8", - "title": "NIST Special Publication 800-46", - "citation": { - "text": "NIST Special Publication 800-46" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-46" - } - ] - }, - { - "uuid": "2711f068-734e-4afd-94ba-0b22247fbc88", - "title": "NIST Special Publication 800-47", - "citation": { - "text": "NIST Special Publication 800-47" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-47" - } - ] - }, - { - "uuid": "238ed479-eccb-49f6-82ec-ab74a7a428cf", - "title": "NIST Special Publication 800-48", - "citation": { - "text": "NIST Special Publication 800-48" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-48" - } - ] - }, - { - "uuid": "e12b5738-de74-4fb3-8317-a3995a8a1898", - "title": "NIST Special Publication 800-50", - "citation": { - "text": "NIST Special Publication 800-50" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-50" - } - ] - }, - { - "uuid": "90c5bc98-f9c4-44c9-98b7-787422f0999c", - "title": "NIST Special Publication 800-52", - "citation": { - "text": "NIST Special Publication 800-52" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-52" - } - ] - }, - { - "uuid": "07b79057-4b85-471e-bd16-84844917325b", - "title": "NIST Special Publication 800-53", - "citation": { - "text": "NIST Special Publication 800-53" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-53" - } - ] - }, - { - "uuid": "cd4cf751-3312-4a55-b1a9-fad2f1db9119", - "title": "NIST Special Publication 800-53A", - "citation": { - "text": "NIST Special Publication 800-53A" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-53A" - } - ] - }, - { - "uuid": "83c261f0-e7a1-49f8-95ac-2ab2517644bc", - "title": "NIST Special Publication 800-55", - "citation": { - "text": "NIST Special Publication 800-55" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-55" - } - ] - }, - { - "uuid": "81f09e01-d0b0-4ae2-aa6a-064ed9950070", - "title": "NIST Special Publication 800-56", - "citation": { - "text": "NIST Special Publication 800-56" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-56" - } - ] - }, - { - "uuid": "a6c774c0-bf50-4590-9841-2a5c1c91ac6f", - "title": "NIST Special Publication 800-57", - "citation": { - "text": "NIST Special Publication 800-57" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-57" - } - ] - }, - { - "uuid": "7783f3e7-09b3-478b-9aa2-4a76dfd0ea90", - "title": "NIST Special Publication 800-58", - "citation": { - "text": "NIST Special Publication 800-58" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-58" - } - ] - }, - { - "uuid": "f152844f-b1ef-4836-8729-6277078ebee1", - "title": "NIST Special Publication 800-60", - "citation": { - "text": "NIST Special Publication 800-60" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-60" - } - ] - }, - { - "uuid": "be95fb85-a53f-4624-bdbb-140075500aa3", - "title": "NIST Special Publication 800-61", - "citation": { - "text": "NIST Special Publication 800-61" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-61" - } - ] - }, - { - "uuid": "644f44a9-a2de-4494-9c04-cd37fba45471", - "title": "NIST Special Publication 800-63", - "citation": { - "text": "NIST Special Publication 800-63" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-63" - } - ] - }, - { - "uuid": "abd950ae-092f-4b7a-b374-1c7c67fe9350", - "title": "NIST Special Publication 800-64", - "citation": { - "text": "NIST Special Publication 800-64" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-64" - } - ] - }, - { - "uuid": "29fcfe59-33cd-494a-8756-5907ae3a8f92", - "title": "NIST Special Publication 800-65", - "citation": { - "text": "NIST Special Publication 800-65" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-65" - } - ] - }, - { - "uuid": "84a37532-6db6-477b-9ea8-f9085ebca0fc", - "title": "NIST Special Publication 800-70", - "citation": { - "text": "NIST Special Publication 800-70" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-70" - } - ] - }, - { - "uuid": "ead74ea9-4c9c-446d-9b92-bcbf0ad4b655", - "title": "NIST Special Publication 800-73", - "citation": { - "text": "NIST Special Publication 800-73" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-73" - } - ] - }, - { - "uuid": "2a71298a-ee90-490e-80ff-48c967173a47", - "title": "NIST Special Publication 800-76", - "citation": { - "text": "NIST Special Publication 800-76" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-76" - } - ] - }, - { - "uuid": "99f331f2-a9f0-46c2-9856-a3cbb9b89442", - "title": "NIST Special Publication 800-77", - "citation": { - "text": "NIST Special Publication 800-77" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-77" - } - ] - }, - { - "uuid": "2042d97b-f7f6-4c74-84f8-981867684659", - "title": "NIST Special Publication 800-78", - "citation": { - "text": "NIST Special Publication 800-78" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-78" - } - ] - }, - { - "uuid": "6af1e841-672c-46c4-b121-96f603d04be3", - "title": "NIST Special Publication 800-81", - "citation": { - "text": "NIST Special Publication 800-81" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-81" - } - ] - }, - { - "uuid": "6d431fee-658f-4a0e-9f2e-a38b5d398fab", - "title": "NIST Special Publication 800-83", - "citation": { - "text": "NIST Special Publication 800-83" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-83" - } - ] - }, - { - "uuid": "0243a05a-e8a3-4d51-9364-4a9d20b0dcdf", - "title": "NIST Special Publication 800-84", - "citation": { - "text": "NIST Special Publication 800-84" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-84" - } - ] - }, - { - "uuid": "263823e0-a971-4b00-959d-315b26278b22", - "title": "NIST Special Publication 800-88", - "citation": { - "text": "NIST Special Publication 800-88" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-88" - } - ] - }, - { - "uuid": "672fd561-b92b-4713-b9cf-6c9d9456728b", - "title": "NIST Special Publication 800-92", - "citation": { - "text": "NIST Special Publication 800-92" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-92" - } - ] - }, - { - "uuid": "d1b1d689-0f66-4474-9924-c81119758dc1", - "title": "NIST Special Publication 800-94", - "citation": { - "text": "NIST Special Publication 800-94" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-94" - } - ] - }, - { - "uuid": "1ebdf782-d95d-4a7b-8ec7-ee860951eced", - "title": "NIST Special Publication 800-95", - "citation": { - "text": "NIST Special Publication 800-95" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-95" - } - ] - }, - { - "uuid": "6f336ecd-f2a0-4c84-9699-0491d81b6e0d", - "title": "NIST Special Publication 800-97", - "citation": { - "text": "NIST Special Publication 800-97" - }, - "rlinks": [ - { - "href": "http://csrc.nist.gov/publications/PubsSPs.html#800-97" - } - ] - }, - { - "uuid": "06dff0ea-3848-4945-8d91-e955ee69f05d", - "title": "NSTISSI No. 7003", - "citation": { - "text": "NSTISSI No. 7003" - }, - "rlinks": [ - { - "href": "http://www.cnss.gov/Assets/pdf/nstissi_7003.pdf" - } - ] - }, - { - "uuid": "9f77f845-e3ea-4ca4-b2c0-aa9eedc214ab", - "title": "OMB Circular A-130", - "citation": { - "text": "OMB Circular A-130" - }, - "rlinks": [ - { - "href": "http://www.whitehouse.gov/omb/circulars_a130_a130trans4" - } - ] - }, - { - "uuid": "2c5884cd-7b96-425c-862a-99877e1cf909", - "title": "OMB Memorandum 02-01", - "citation": { - "text": "OMB Memorandum 02-01" - }, - "rlinks": [ - { - "href": "http://www.whitehouse.gov/omb/memoranda_m02-01" - } - ] - }, - { - "uuid": "ff3bfb02-79b2-411f-8735-98dfe5af2ab0", - "title": "OMB Memorandum 04-04", - "citation": { - "text": "OMB Memorandum 04-04" - }, - "rlinks": [ - { - "href": "http://www.whitehouse.gov/sites/default/files/omb/assets/omb/memoranda/fy04/m04-04.pdf" - } - ] - }, - { - "uuid": "58ad6f27-af99-429f-86a8-8bb767b014b9", - "title": "OMB Memorandum 05-24", - "citation": { - "text": "OMB Memorandum 05-24" - }, - "rlinks": [ - { - "href": "http://www.whitehouse.gov/sites/default/files/omb/assets/omb/memoranda/fy2005/m05-24.pdf" - } - ] - }, - { - "uuid": "4da24a96-6cf8-435d-9d1f-c73247cad109", - "title": "OMB Memorandum 06-16", - "citation": { - "text": "OMB Memorandum 06-16" - }, - "rlinks": [ - { - "href": "http://www.whitehouse.gov/sites/default/files/omb/assets/omb/memoranda/fy2006/m06-16.pdf" - } - ] - }, - { - "uuid": "990268bf-f4a9-4c81-91ae-dc7d3115f4b1", - "title": "OMB Memorandum 07-11", - "citation": { - "text": "OMB Memorandum 07-11" - }, - "rlinks": [ - { - "href": "http://www.whitehouse.gov/sites/default/files/omb/assets/omb/memoranda/fy2007/m07-11.pdf" - } - ] - }, - { - "uuid": "0b3d8ba9-051f-498d-81ea-97f0f018c612", - "title": "OMB Memorandum 07-18", - "citation": { - "text": "OMB Memorandum 07-18" - }, - "rlinks": [ - { - "href": "http://www.whitehouse.gov/sites/default/files/omb/assets/omb/memoranda/fy2007/m07-18.pdf" - } - ] - }, - { - "uuid": "0916ef02-3618-411b-a525-565c088849a6", - "title": "OMB Memorandum 08-22", - "citation": { - "text": "OMB Memorandum 08-22" - }, - "rlinks": [ - { - "href": "http://www.whitehouse.gov/sites/default/files/omb/assets/omb/memoranda/fy2008/m08-22.pdf" - } - ] - }, - { - "uuid": "28115a56-da6b-4d44-b1df-51dd7f048a3e", - "title": "OMB Memorandum 08-23", - "citation": { - "text": "OMB Memorandum 08-23" - }, - "rlinks": [ - { - "href": "http://www.whitehouse.gov/sites/default/files/omb/assets/omb/memoranda/fy2008/m08-23.pdf" - } - ] - }, - { - "uuid": "599fe9ba-4750-4450-9eeb-b95bd19a5e8f", - "title": "OMB Memorandum 10-06-2011", - "citation": { - "text": "OMB Memorandum 10-06-2011" - } - }, - { - "uuid": "74e740a4-c45d-49f3-a86e-eb747c549e01", - "title": "OMB Memorandum 11-11", - "citation": { - "text": "OMB Memorandum 11-11" - }, - "rlinks": [ - { - "href": "http://www.whitehouse.gov/sites/default/files/omb/memoranda/2011/m11-11.pdf" - } - ] - }, - { - "uuid": "bedb15b7-ec5c-4a68-807f-385125751fcd", - "title": "OMB Memorandum 11-33", - "citation": { - "text": "OMB Memorandum 11-33" - }, - "rlinks": [ - { - "href": "http://www.whitehouse.gov/sites/default/files/omb/memoranda/2011/m11-33.pdf" - } - ] - }, - { - "uuid": "dd2f5acd-08f1-435a-9837-f8203088dc1a", - "title": "Personal Identity Verification (PIV) in Enterprise Physical Access Control System (E-PACS)", - "citation": { - "text": "Personal Identity Verification (PIV) in Enterprise Physical Access Control System (E-PACS)" - } - }, - { - "uuid": "8ade2fbe-e468-4ca8-9a40-54d7f23c32bb", - "title": "US-CERT Technical Cyber Security Alerts", - "citation": { - "text": "US-CERT Technical Cyber Security Alerts" - }, - "rlinks": [ - { - "href": "http://www.us-cert.gov/ncas/alerts" - } - ] - }, - { - "uuid": "16b3b234-3406-44dc-8645-7da61b6e81f1", - "rlinks": [ - { - "href": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf", - "media-type": "application/pdf" - } - ] - }, - { - "uuid": "fb81fb1c-165e-43a4-8264-1dfd3182b630", - "rlinks": [ - { - "href": "http://dx.doi.org/10.6028/NIST.SP.800-53r4", - "media-type": "application/pdf" - } - ] - } - ] - } - } -} diff --git a/data/cds/offering.json b/data/cds/offering.json index 27be34e5..1e7df189 100644 --- a/data/cds/offering.json +++ b/data/cds/offering.json @@ -1,41 +1,142 @@ { - "_note": "Operator-declared editorial values for the CDS certification-overview package (CDS-CSO-PUB / CDS-CSO-SVC / CDS-CSO-FID). scripts/build-cds-overview.py reads this plus the system profile and the canonical inventory to emit /.well-known/certification-overview-package.json. Honest placeholders are used where a value requires sponsorship the PoC does not have (FedRAMP ID, UEI).", - "fedramp_id": "<not assigned — unsponsored self-attested PoC; CDS-CSO-FID placeholder>", - "service_model": "SaaS", + "_note": "Operator-declared editorial values for the Certification Package Overview (CPO-CSO-OVR: CDS-CSO-PUB, CDS-CSO-SVC, CDS-CSO-FID). scripts/build-cpo.py reads this plus the system profile, the CCM calendar and the canonical inventory and writes /.well-known/certification-package-overview.json in FedRAMP's schema. Where a value needs an outside party this proof of concept does not have (a FedRAMP ID, a SAM.gov UEI), the value is SIMULATED, says so, and the CPO flags it under providerExtensions.simulated. No published value here is an email address: contacts point to /.well-known/security.txt or the contact page.", + "provider_name": "Sam Aydlette", + "service_name": "samaydlette.com", + "service_acronym": "SAMCOM", + "fedramp_id": "Sam Aydlette (SAMCOM): PROOF-OF-CONCEPT-NOT-A-REAL-FEDRAMP-ID", + "fedramp_id_simulated": "No FedRAMP ID exists or is coming: nothing has been submitted to FedRAMP. FedRAMP's schema says to use the provider's name and acronym until an ID is assigned; the suffix makes sure nobody mistakes it for one.", + "uei": "NOT-A-REAL-UEI-0000", + "uei_simulated": "Simulated. The operator is not registering on SAM.gov, so there is no Unique Entity Identifier; this value is a placeholder that no SAM.gov lookup will ever find.", + "service_model": [ + "SaaS" + ], "deployment_model": "Public Cloud", - "business_category": "Personal demonstration / compliance-automation reference architecture", - "uei": "<not assigned — no SAM.gov registration>", - "sales_contact": { "name": "Sam Aydlette", "url": "https://samaydlette.com/pages/contact.html" }, - "security_contact": { "name": "Sam Aydlette", "email": "sam.aydlette@gmail.com", "source": "/.well-known/security.txt" }, + "business_category": [ + "Governance, Risk, and Compliance (GRC)", + "Cybersecurity & Risk Management", + "Health & Wellness" + ], + "sales_contact": { + "name": "Sam Aydlette. Nothing here is for sale; say hello through the contact page: https://samaydlette.com/pages/contact.html" + }, + "security_contact": { + "name": "Sam Aydlette, through the security contact in https://samaydlette.com/.well-known/security.txt" + }, + "fedramp_security_inbox": { + "_note": "The FedRAMP Security Inbox contact (AFC-CSO-INB), written in this one place. By the operator's decision the inbox is SIMULATED for this proof of concept: the inbox logic (scripts/_fsi.py) runs on every deploy over synthetic messages and publishes /.well-known/fedramp-inbox-simulation.json, and nothing real is received or sent. The CPO publishes this contact. To change it: change contact and add a history entry whose since is the date of the change. The deploy then files the change notice with the simulated FedRAMP (an entry in /.well-known/package-submission-log.json; nothing is sent) and fails unless the notice is dated within one business day of that date (AFC-CSO-NOC, scripts/check-fsi-notice.py).", + "contact": "Simulated for this proof of concept: there is no FedRAMP Security Inbox, no mail is received or sent, and the inbox is permanently at zero because it does not exist. Hit me up on LinkedIn: https://www.linkedin.com/in/sa2/", + "simulation": "https://samaydlette.com/.well-known/fedramp-inbox-simulation.json", + "runbook": "https://github.com/sam-aydlette/samaydlette.com/blob/main/docs/runbooks/fedramp-security-inbox.md", + "history": [ + { + "contact": "Simulated for this proof of concept: there is no FedRAMP Security Inbox, no mail is received or sent, and the inbox is permanently at zero because it does not exist. Hit me up on LinkedIn: https://www.linkedin.com/in/sa2/", + "since": "2026-11-05", + "basis": "Established. No earlier FedRAMP Security Inbox or Marketplace Security Email is on file with FedRAMP for this unsponsored system, so there was no prior contact to change from." + } + ] + }, "product_website": "https://samaydlette.com", "logo_url": "https://samaydlette.com/assets/images/brand/logo.png", "service_description": "A static personal website on AWS that doubles as a working continuous-compliance pipeline: every deploy derives signed, machine-readable compliance artifacts from one canonical inventory and publishes them under /.well-known/. Includes the Silk Reeling Mirror application, a Cognito-gated Tai Chi coaching API.", "secure_configuration_guidance_url": "https://github.com/sam-aydlette/samaydlette.com/blob/main/docs/policies/secure-configuration-guide.md", "documentation_overview_url": "https://samaydlette.com/trust/index.html", - "current_independent_assessment_service": "None — self-attested; no FedRAMP-Recognized independent assessment service engaged (IVV is N/A for this unsponsored proof of concept).", + "current_independent_assessment_service": "None: no FedRAMP Recognized independent assessment service is engaged. Every deploy is assessed by Totally Real Assessment Services, LLC (simulated), a workflow in this repository that is not a FedRAMP Recognized assessment service; its overall summary is quoted below.", "accountable_official": { "name": "Sam Aydlette", "title": "System Owner / Authorizing Operator", - "contact": "sam.aydlette@gmail.com" + "contact": "https://samaydlette.com/.well-known/security.txt" }, "cryptographic_modules": [ - { "module": "AWS KMS", "validation": "FIPS 140-3 (CMVP, HSM-backed)", "role": "key store for all four customer-managed CMKs: at-rest (the compliance and watchdog Lambdas' environments and log groups, the DNS query log, the alert topic), runtime signing (the runtime signal), DNSSEC KSK, and the Silk Reeling app (its Lambda environment and log groups; the app holds no secrets since SCN-2026-006)", "inherited": true }, - { "module": "ACM TLS termination on CloudFront", "validation": "FIPS-validated cipher suites; TLS 1.2+", "role": "TLS in transit", "inherited": true }, - { "module": "S3 SSE-S3", "validation": "AES-256 (AWS-managed keys)", "role": "at-rest on the public website + log buckets", "inherited": true }, - { "module": "Sigstore Fulcio + Rekor", "validation": "ECDSA P-256 (FIPS-approved algorithm); the implementations are NOT CMVP-validated modules", "role": "deploy-time keyless signing", "inherited": false, "compensating_control": "trust anchored in the public Rekor transparency log" } + { + "module": "AWS KMS", + "validation": "FIPS 140-3 Level 3, CMVP certificate #4884 (AWS Key Management Service HSM)", + "role": "key store for all four customer-managed CMKs: at-rest (the compliance and watchdog Lambdas' environments and log groups, the DNS query log, the alert topic), runtime signing (the runtime signal), DNSSEC KSK, and the Silk Reeling app (its Lambda environment and log groups; the app holds no secrets since SCN-2026-006)", + "inherited": true + }, + { + "module": "ACM TLS termination on CloudFront", + "validation": "TLS 1.2+ (TLSv1.2_2021); AWS publishes no CMVP module for CloudFront viewer TLS (accepted, DEC-152)", + "role": "TLS in transit", + "inherited": true + }, + { + "module": "S3 SSE-S3", + "validation": "AES-256 (AWS-managed keys); AWS publishes no CMVP module for SSE-S3 (accepted, DEC-152)", + "role": "at-rest on the public website + log buckets", + "inherited": true + }, + { + "module": "Sigstore Fulcio + Rekor", + "validation": "ECDSA P-256 (FIPS-approved algorithm); the implementations are NOT CMVP-validated modules", + "role": "deploy-time keyless signing", + "inherited": false, + "compensating_control": "trust anchored in the public Rekor transparency log" + } ], "services": [ { "name": "samaydlette.com static website", - "description": "Public static content (S3 origin behind CloudFront), plus the signed compliance artifacts published under /.well-known/.", - "security_category": "FIPS-199 Moderate (FedRAMP 20x Class C)", + "description": "Public static content (S3 origin behind CloudFront), plus the signed compliance artifacts published under /.well-known/ and the trust center at /trust/.", + "boundary_groups": [ + "website" + ], + "security_category": { + "confidentiality": "low", + "integrity": "moderate", + "availability": "low", + "rationale": "Public content: nothing confidential. Integrity is moderate because defacement or tampering of published evidence would mislead readers. Availability is low: a personal site." + }, "in_mas_scope": true }, { "name": "Silk Reeling Mirror application", "description": "Cognito-gated HTTP API (API Gateway -> Lambda) serving a browser SPA that coaches Tai Chi; writes feedback text from the scores in the Lambda, with no external interconnection (optional LLM feedback is customer-configurable and disabled here).", - "security_category": "FIPS-199 Moderate (FedRAMP 20x Class C)", + "date_available": "2026-06-03", + "boundary_groups": [ + "app" + ], + "security_category": { + "confidentiality": "low", + "integrity": "moderate", + "availability": "low", + "rationale": "Holds invited users' sign-in accounts and the pose scores they submit, no federal data: confidentiality low. Integrity moderate: wrong coaching or tampered accounts are the harm. Availability low." + }, "in_mas_scope": true + }, + { + "name": "Continuous compliance evidence (pipeline trust root, runtime KSI emitter, evidence watchdog)", + "description": "The deploy's trust root (OIDC roles, CloudFront, DNSSEC, remote state), the daily runtime re-validation of live configuration (signed runtime KSI signal), the hourly evidence-freshness watchdog with its alarms, and the audit trail and keys behind them. GitHub Actions and Sigstore, which build and sign the evidence, are third-party information resources inside the boundary.", + "boundary_groups": [ + "compliance", + "watchdog", + "audit", + "trust-root" + ], + "security_category": { + "confidentiality": "low", + "integrity": "moderate", + "availability": "low", + "rationale": "The evidence is public by design. Integrity is moderate: false evidence is the harm this system exists to prevent. Availability is low." + }, + "in_mas_scope": true + } + ], + "not_included": [ + { + "name": "Podcast and video audio hosted by third parties", + "why": "Linked from pages, served by their own hosts; not part of the offering." + }, + { + "name": "MediaPipe libraries and models (cdn.jsdelivr.net, storage.googleapis.com)", + "why": "Loaded by the visitor's browser from third-party hosts at run time; listed as third-party information resources, not services of this offering." + }, + { + "name": "Optional LLM coaching feedback", + "why": "Customer-configurable and disabled; no external AI service is called." + }, + { + "name": "Newsletter, RSS and social feeds", + "why": "None is offered under this certification." } ] } diff --git a/data/crypto-modules.json b/data/crypto-modules.json new file mode 100644 index 00000000..27635f07 --- /dev/null +++ b/data/crypto-modules.json @@ -0,0 +1,215 @@ +{ + "schema": "crypto-modules/1", + "$comment": "Cryptographic modules per service (CMU-CSO-CMD, CMU-CSO-UVM, CMU-CSO-CAT). scripts/build-scg.py joins this with the deploy's inventory and publishes the per-service list inside /.well-known/secure-configuration-guide.json; it fails the build when the inventory holds a component type that is neither mapped here nor listed as using no cryptography. Every certificate number was read from NIST's CMVP pages on the date given; no number is typed from memory. AI-drafted 2026-11-05; for the operator's review.", + "checked_on": "2026-11-05", + "modules": { + "aws-kms-hsm": { + "name": "AWS Key Management Service HSM", + "vendor": "Amazon Web Services, Inc.", + "cmvp_certificate": "4884", + "standard": "FIPS 140-3", + "level": "3", + "status": "Active (sunset 2029-11-17)", + "source": "https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4884" + }, + "not-published": { + "name": "Not published by AWS for this service path", + "vendor": "Amazon Web Services, Inc.", + "cmvp_certificate": null, + "standard": null, + "level": null, + "status": "AWS's FIPS page lists FIPS endpoints and module families but names no CMVP module for this path; treated as not validated (DEC-152).", + "source": "https://aws.amazon.com/compliance/fips/" + }, + "sigstore": { + "name": "Sigstore Fulcio and Rekor (public-good instance), cosign client", + "vendor": "Sigstore (OpenSSF)", + "cmvp_certificate": null, + "standard": null, + "level": null, + "status": "Not a CMVP-validated module. ECDSA P-256 (a FIPS-approved algorithm). Signs published evidence; protects no customer data.", + "source": "https://docs.sigstore.dev/" + } + }, + "services": [ + { + "service": "CloudFront viewer TLS (site and app)", + "types": [ + "cdn_distribution", + "tls_certificate" + ], + "protects": "data in transit between users and the edge, including app sign-in tokens", + "module": "not-published", + "configuration": "Security policy TLSv1.2_2021 (TLS 1.2 or later, forward-secret AES-GCM suites); ACM certificate.", + "customer_data": true, + "tenant_default": "TLSv1.2_2021 on every request; no FIPS-validated viewer TLS option is offered for a distribution." + }, + { + "service": "API Gateway HTTP API TLS (Silk Reeling)", + "types": [ + "api_gateway" + ], + "protects": "the app's API calls in transit (CloudFront to API Gateway)", + "module": "not-published", + "configuration": "HTTPS only; CloudFront connects with TLS 1.2 (origin_ssl_protocols).", + "customer_data": true, + "tenant_default": "HTTPS only; AWS's API Gateway FIPS endpoint covers the management API, not an HTTP API's execute-api endpoint." + }, + { + "service": "Amazon Cognito user pool (Silk Reeling sign-in)", + "types": [ + "identity_provider" + ], + "protects": "app users' credentials and MFA secrets, tokens", + "module": "not-published", + "configuration": "Hosted UI over TLS; tokens signed by Cognito; user records encrypted at rest by Cognito.", + "customer_data": true, + "tenant_default": "The Hosted UI sign-in domain has no FIPS endpoint (AWS lists cognito-idp-fips for the API only)." + }, + { + "service": "AWS KMS customer-managed keys", + "types": [ + "kms_key" + ], + "protects": "the keys that encrypt the app's Lambda environment and log groups, the alert topic, the runtime signing key and the DNSSEC key-signing key", + "module": "aws-kms-hsm", + "configuration": "Four customer-managed keys, automatic rotation enabled on the symmetric keys.", + "customer_data": true, + "tenant_default": "Every app data store that supports a customer-managed key uses one (Lambda environment, log groups)." + }, + { + "service": "AWS Lambda (functions and their environments)", + "types": [ + "function" + ], + "protects": "function environment variables at rest; the app's outbound TLS to Cognito's key endpoint", + "module": "aws-kms-hsm", + "configuration": "Environments encrypted with a customer-managed KMS key (kms_key_arn). Outbound TLS uses the Python runtime's own TLS library, which is not run as a validated module (DEC-152).", + "customer_data": true, + "tenant_default": "kms_key_arn set on the app function." + }, + { + "service": "CloudWatch Logs", + "types": [ + "log_group" + ], + "protects": "application and gateway logs at rest", + "module": "aws-kms-hsm", + "configuration": "Every log group encrypted with a customer-managed KMS key.", + "customer_data": true, + "tenant_default": "kms_key_id set on every app log group." + }, + { + "service": "Amazon SNS (evidence alerts)", + "types": [ + "notification_topic" + ], + "protects": "alert messages at rest", + "module": "aws-kms-hsm", + "configuration": "Topic encrypted with a customer-managed KMS key.", + "customer_data": false, + "tenant_default": null + }, + { + "service": "AWS Secrets Manager", + "types": [ + "secrets_manager" + ], + "protects": "secret values at rest (none exist today: the app holds no secret since SCN-2026-006)", + "module": "aws-kms-hsm", + "configuration": "A secret, if added, is encrypted under a customer-managed KMS key; the app key's policy admits Secrets Manager use only through the service.", + "customer_data": false, + "tenant_default": null + }, + { + "service": "Amazon S3 (site, logs, CloudTrail, Terraform state)", + "types": [ + "object_store" + ], + "protects": "objects at rest; the site's public content, access logs, the audit trail, Terraform state", + "module": "not-published", + "configuration": "SSE-S3 (AES-256, AWS-managed keys); TLS-only bucket policies on the state bucket.", + "customer_data": false, + "tenant_default": null + }, + { + "service": "Amazon SQS (compliance dead-letter queue)", + "types": [ + "message_queue" + ], + "protects": "failed compliance events at rest", + "module": "not-published", + "configuration": "SSE-SQS (AWS-managed keys).", + "customer_data": false, + "tenant_default": null + }, + { + "service": "Amazon DynamoDB (Terraform state lock)", + "types": [ + "kv_table" + ], + "protects": "lock items at rest", + "module": "not-published", + "configuration": "AWS-owned key encryption.", + "customer_data": false, + "tenant_default": null + }, + { + "service": "AWS CloudTrail (management trail)", + "types": [ + "audit_log_trail" + ], + "protects": "the integrity of the audit trail (log file validation digests)", + "module": "not-published", + "configuration": "Management events; delivered to the CloudTrail bucket (SSE-S3).", + "customer_data": false, + "tenant_default": null + }, + { + "service": "Route 53 DNSSEC signing", + "types": [ + "dns_zone" + ], + "protects": "the integrity of the site's DNS answers", + "module": "aws-kms-hsm", + "configuration": "Key-signing key is an asymmetric customer-managed KMS key in us-east-1 (ECC_NIST_P256).", + "customer_data": false, + "tenant_default": null + }, + { + "service": "IAM OIDC provider (GitHub Actions)", + "types": [ + "oidc_provider" + ], + "protects": "CI's federation to AWS (token signature verification by AWS STS)", + "module": "not-published", + "configuration": "Trusts token.actions.githubusercontent.com for sts.amazonaws.com only.", + "customer_data": false, + "tenant_default": null + }, + { + "service": "External services (Sigstore signing and others)", + "types": [ + "external_service" + ], + "protects": "the authenticity of published evidence (keyless signatures); other external services carry no customer data", + "module": "sigstore", + "configuration": "cosign sign-blob with a Fulcio certificate and a Rekor entry; verification pins the workflow identity.", + "customer_data": false, + "tenant_default": null + } + ], + "no_cryptography": { + "types": [ + "npm_package", + "pypi_package", + "html_artifact", + "iam_policy", + "iam_role", + "iam_group", + "metric_alarm", + "event_schedule" + ], + "why": "Software packages, page content, IAM policy documents and alarm or schedule definitions: inventoried components that provide no cryptographic service of their own." + } +} diff --git a/data/decisions.json b/data/decisions.json index 1b4d402f..b57cffdd 100644 --- a/data/decisions.json +++ b/data/decisions.json @@ -95,7 +95,8 @@ "identifier": "CKV_AWS_144", "original_risk_rating": "low", "risk_adjustment": false - } + }, + "confirmed_on": "2026-06-15" }, { "id": "DEC-004", @@ -125,7 +126,8 @@ "identifier": "CKV_AWS_23", "original_risk_rating": "low", "risk_adjustment": false - } + }, + "confirmed_on": "2026-06-15" }, { "id": "DEC-005", @@ -184,7 +186,7 @@ "title": "CloudFront WAF not attached", "disposition": "risk-accepted", "status": "in-force", - "justification": "Cost trade-off (~$120/year). Static personal site has no forms, no auth endpoints, no expensive backend; AWS Shield Standard is the baseline DDoS protection at zero marginal cost.", + "justification": "Cost trade-off (~$120/year). The distribution serves the static site from a private S3 origin, and under /silk-reeling/* the Silk Reeling app on API Gateway: its /api routes require a Cognito-issued token, checked by the API Gateway JWT authorizer and again in the Lambda, and the stage throttles requests (20 per second, burst 10); users sign in through the Cognito Hosted UI, which is not behind this distribution. There are no other forms or server-side code behind it. AWS Shield Standard is the baseline DDoS protection at zero marginal cost; the incremental layer-7 filtering a WAF would add is the accepted residual. (Text corrected 2026-11-06: it used to say the site had no authentication endpoints, which stopped being true when the app was added; the decision itself is unchanged.)", "controls": [ "sc-7", "si-4" @@ -207,7 +209,9 @@ "original_risk_rating": "moderate", "adjusted_risk_rating": "low", "risk_adjustment": true - } + }, + "original_detection_date": "2025-06-14", + "confirmed_on": "2026-05-08" }, { "id": "DEC-008", @@ -237,7 +241,8 @@ "identifier": "CKV_AWS_174; CKV2_AWS_47", "original_risk_rating": "low", "risk_adjustment": false - } + }, + "confirmed_on": "2026-06-15" }, { "id": "DEC-009", @@ -245,7 +250,7 @@ "title": "CloudFront origin failover not configured", "disposition": "risk-accepted", "status": "in-force", - "justification": "Single S3 origin. No secondary origin to fail over to; multi-origin would require multi-region storage (see POAM-016).", + "justification": "Single S3 origin. No secondary origin to fail over to; multi-origin would require multi-region storage, which is not built: cross-region replication is not configured (DEC-003). (Text corrected 2026-11-06: it used to point to a POA&M item retired with the POA&M; the decision itself is unchanged.)", "controls": [ "cp-2", "cp-7" @@ -268,7 +273,9 @@ "identifier": "CKV_AWS_86; CKV_AWS_310", "original_risk_rating": "low", "risk_adjustment": false - } + }, + "original_detection_date": "2025-06-14", + "confirmed_on": "2026-05-08" }, { "id": "DEC-010", @@ -286,7 +293,9 @@ ], "vuln_ids": [], "resources": [ - "aws-lambda::compliance-monitor" + "aws::function::opa_compliance", + "aws::function::evidence_watchdog", + "aws::function::silk_reeling" ] }, "decided_by": "Sam Aydlette", @@ -297,7 +306,9 @@ "identifier": "CKV_AWS_117", "original_risk_rating": "low", "risk_adjustment": false - } + }, + "original_detection_date": "2025-06-14", + "confirmed_on": "2026-05-08" }, { "id": "DEC-011", @@ -352,7 +363,8 @@ "identifier": "CKV_AWS_115", "original_risk_rating": "low", "risk_adjustment": false - } + }, + "confirmed_on": "2026-06-18" }, { "id": "DEC-013", @@ -406,7 +418,8 @@ "identifier": "CKV_AWS_50", "original_risk_rating": "low", "risk_adjustment": false - } + }, + "confirmed_on": "2026-06-15" }, { "id": "DEC-015", @@ -437,7 +450,8 @@ "original_risk_rating": "moderate", "adjusted_risk_rating": "low", "risk_adjustment": true - } + }, + "confirmed_on": "2026-06-18" }, { "id": "DEC-017", @@ -497,7 +511,7 @@ "title": "Secrets Manager automatic rotation not configured", "disposition": "remediated", "status": "closed", - "justification": "Closed (2026-10-27, SCN-2026-006): the check no longer applies. The app's only Secrets Manager secret, the Anthropic API key, was removed with the interconnection (POAM-020) and is scheduled for deletion, so no secret remains and the CKV2_AWS_57 skip was removed from .checkov.yaml. Original record: Reclassified false positive (Task 3): CKV2_AWS_57 flags the absence of automatic rotation, but no control mandates that specific mechanism. The basic-auth secret it shared the finding with was removed under Task 3, leaving only the third-party Anthropic API key, which has no programmatic rotation source (AWS cannot mint a new upstream key), so a Secrets Manager rotation Lambda is infeasible by construction. SC-12 rotation is met by documented annual manual rotation, and rotation currency is verified automatically: the runtime KSI emitter reads the secret's LastChangedDate daily and fails an SC-12 validation if rotation lapses past the cadence (395-day grace). Because rotation is met and self-verifying, this is a false positive, not an accepted risk.", + "justification": "Closed (2026-10-27, SCN-2026-006): the check no longer applies. The app's only Secrets Manager secret, the Anthropic API key, was removed with the interconnection (POAM-020) and is scheduled for deletion, so no secret remains and the CKV2_AWS_57 skip was removed from .checkov.yaml. Original record: Reclassified false positive (Task 3): CKV2_AWS_57 flags the absence of automatic rotation, but no control mandates that specific mechanism. The basic-auth secret it shared the finding with was removed under Task 3, leaving only the third-party Anthropic API key, which has no programmatic rotation source (AWS cannot mint a new upstream key), so a Secrets Manager rotation Lambda is infeasible by construction. SC-12 is met by rotation on compromise: a secret with no programmatic rotation source is rotated when it is exposed or suspected exposed (docs/incident-response.md, containment step 3), not on a calendar, so no recurring manual rotation is committed (DEC-195). No such secret remains. Because no control mandates automatic rotation and rotation on compromise is the stated mechanism, this is a false positive, not an accepted risk.", "controls": [ "sc-12", "sc-28" @@ -518,7 +532,13 @@ "detector": "Checkov", "identifier": "CKV2_AWS_57", "original_risk_rating": "low", - "risk_adjustment": false + "risk_adjustment": false, + "reworded": { + "on": "2026-11-06", + "for": "no recurring manual work (DEC-195): POAM-019 restated as rotate-on-compromise", + "before": "SC-12 rotation is met by documented annual manual rotation, and rotation currency is verified automatically: the runtime KSI emitter reads the secret's LastChangedDate daily and fails an SC-12 validation if rotation lapses past the cadence (395-day grace). Because rotation is met and self-verifying, this is a false positive, not an accepted risk.", + "after": "SC-12 is met by rotation on compromise: a secret with no programmatic rotation source is rotated when it is exposed or suspected exposed (docs/incident-response.md, containment step 3), not on a calendar, so no recurring manual rotation is committed (DEC-195). No such secret remains. Because no control mandates automatic rotation and rotation on compromise is the stated mechanism, this is a false positive, not an accepted risk." + } } }, { @@ -672,7 +692,7 @@ "title": "Root and operator MFA is virtual TOTP, not hardware/phishing-resistant", "disposition": "operational-requirement", "status": "in-force", - "justification": "The root account and the operator IAM user (saydlette-dev) both authenticate with virtual authenticator-app (TOTP) MFA rather than a hardware/phishing-resistant authenticator. Multi-factor authentication (IA-2(1)/(2)) is met - MFA is enabled on both - but the stricter phishing-resistant objective (IA-2(8): hardware token or passkey) is not. Surfaced by the 2026-06-22 Prowler scan. Compensating control: virtual TOTP MFA is enabled on both principals now.", + "justification": "The root account and the operator IAM user both authenticate with virtual authenticator-app (TOTP) MFA rather than a hardware/phishing-resistant authenticator. Multi-factor authentication (IA-2(1)/(2)) is met - MFA is enabled on both - but the stricter phishing-resistant objective (IA-2(8): hardware token or passkey) is not. Surfaced by the 2026-06-22 Prowler scan. Compensating control: virtual TOTP MFA is enabled on both principals now.", "controls": [ "ia-2.1", "ia-2.2", @@ -691,16 +711,21 @@ "decided_on": "2026-09-30", "review_by": "2027-09-30", "original_detection_date": "2026-06-22", - "remediation_plan": "Enroll a hardware security key (FIDO2/WebAuthn) as the MFA device for the root account and the operator IAM user, satisfying the phishing-resistant objective (IA-2(8)).", - "planned_completion": "2026-10-30", "point_of_contact": "Sam Aydlette (operator)", "source": { + "plan_withdrawn": { + "on": "2026-11-06", + "by": "DEC-150 (phishing-resistant MFA accepted as not bought)", + "remediation_plan": "Enroll a hardware security key (FIDO2/WebAuthn) as the MFA device for the root account and the operator IAM user, satisfying the phishing-resistant objective (IA-2(8)).", + "planned_completion": "2026-10-30" + }, "detector": "Prowler", "identifier": "root-account-hardware-mfa-enabled; iam_user_hardware_mfa_enabled", "original_risk_rating": "moderate", "adjusted_risk_rating": "low", "risk_adjustment": true - } + }, + "confirmed_on": "2026-09-30" }, { "id": "DEC-026", @@ -708,7 +733,7 @@ "title": "Operator IAM group holds broad IAM administration privileges", "disposition": "risk-accepted", "status": "in-force", - "justification": "The operators IAM group (the sole human-principal group) carries IAM administration privileges (it manages users, groups, and policies). Surfaced by Checkov CKV2_AWS_56 against infrastructure/bootstrap/main.tf. At this system's Moderate categorization a single principal holding IAM admin is a real least-privilege/separation-of-duties weakness (AC-5/AC-6), accepted on the operating model rather than the categorization: the system is a single-operator PoC with no second human to separate duties against, so IAM administration cannot be delegated to a distinct role. Compensating controls: the operator authenticates with MFA (see POAM-025), all IAM changes flow through version-controlled Terraform reviewed in GitHub, and CloudTrail records every IAM action.", + "justification": "The operators IAM group (the sole human-principal group) carries IAM administration privileges (it manages users, groups, and policies). Surfaced by Checkov CKV2_AWS_56 against infrastructure/bootstrap/main.tf. At this system's Moderate categorization a single principal holding IAM admin is a real least-privilege/separation-of-duties weakness (AC-5/AC-6), accepted on the operating model rather than the categorization: the system is a single-operator PoC with no second human to separate duties against, so IAM administration cannot be delegated to a distinct role. Compensating controls: the operator authenticates with MFA (see DEC-025), all IAM changes flow through version-controlled Terraform reviewed in GitHub, and CloudTrail records every IAM action.", "controls": [ "ac-5", "ac-6", @@ -733,7 +758,8 @@ "original_risk_rating": "moderate", "adjusted_risk_rating": "low", "risk_adjustment": true - } + }, + "confirmed_on": "2026-06-29" }, { "id": "DEC-027", @@ -766,7 +792,8 @@ "detector": "Checkov", "identifier": "CKV_AWS_355; CKV_AWS_287; CKV_AWS_356", "original_risk_rating": "low" - } + }, + "confirmed_on": "2026-06-29" }, { "id": "DEC-028", @@ -796,7 +823,8 @@ "detector": "Checkov; tfsec; Prowler", "identifier": "CKV_AWS_18; AVD-AWS-0089; s3_bucket_server_access_logging_enabled", "original_risk_rating": "low" - } + }, + "confirmed_on": "2026-06-29" }, { "id": "DEC-029", @@ -829,7 +857,8 @@ "detector": "Checkov; tfsec; Prowler", "identifier": "CKV_AWS_145; CKV_AWS_119; AVD-AWS-0132; s3_bucket_default_encryption", "original_risk_rating": "low" - } + }, + "confirmed_on": "2026-06-29" }, { "id": "DEC-030", @@ -858,7 +887,8 @@ "detector": "Checkov", "identifier": "CKV_AWS_374", "original_risk_rating": "low" - } + }, + "confirmed_on": "2026-06-29" }, { "id": "DEC-031", @@ -892,7 +922,7 @@ "title": "CloudTrail trail has no CloudWatch Logs integration or SNS delivery notifications", "disposition": "risk-accepted", "status": "in-force", - "justification": "The CloudTrail management trail (SCN-2026-003) delivers to S3 only: Checkov CKV2_AWS_10 / tfsec AVD-AWS-0162 flag the missing CloudWatch Logs integration and CKV_AWS_252 the missing SNS delivery topic, both inline-skipped in infrastructure/cloudtrail.tf. CloudWatch Logs integration duplicates every management event into paid log-group storage to enable real-time metric filters that this single-operator system replaces with the quarterly audit-log review (KSI-MLA-RVL); per-delivery SNS notifications have no consumer. Residual risk: no real-time alerting on control-plane events — accepted at this scale, revisited if the operating model gains a second principal or an incident shows the review cadence was too slow. Compensating: log-file validation on the trail; the delivery bucket is TLS-only, versioned, public-access-blocked, lifecycle-tiered (AU-11).", + "justification": "The CloudTrail management trail (SCN-2026-003) delivers to S3 only: Checkov CKV2_AWS_10 / tfsec AVD-AWS-0162 flag the missing CloudWatch Logs integration and CKV_AWS_252 the missing SNS delivery topic, both inline-skipped in infrastructure/cloudtrail.tf. CloudWatch Logs integration duplicates every management event into paid log-group storage to enable real-time metric filters that this system replaces with the automated audit-log review every night (scripts/audit-log-review.py, KSI-MLA-RVL), which reads CloudTrail's event history and flags any write by a principal that is not a CI role; per-delivery SNS notifications have no consumer. Residual risk: no real-time alerting on control-plane events, only a nightly one — accepted at this scale, revisited if the operating model gains a second principal or an incident shows the nightly cadence was too slow. Compensating: log-file validation on the trail; the delivery bucket is TLS-only, versioned, public-access-blocked, lifecycle-tiered (AU-11).", "controls": [ "au-6", "si-4" @@ -915,8 +945,15 @@ "detector": "Checkov, tfsec", "identifier": "CKV2_AWS_10, CKV_AWS_252, AVD-AWS-0162", "original_risk_rating": "low", - "risk_adjustment": false - } + "risk_adjustment": false, + "reworded": { + "on": "2026-11-06", + "for": "no recurring manual work (DEC-195)", + "before": "CloudWatch Logs integration duplicates every management event into paid log-group storage to enable real-time metric filters that this single-operator system replaces with the quarterly audit-log review (KSI-MLA-RVL); per-delivery SNS notifications have no consumer. Residual risk: no real-time alerting on control-plane events — accepted at this scale, revisited if the operating model gains a second principal or an incident shows the review cadence was too slow.", + "after": "CloudWatch Logs integration duplicates every management event into paid log-group storage to enable real-time metric filters that this system replaces with the automated audit-log review every night (scripts/audit-log-review.py, KSI-MLA-RVL), which reads CloudTrail's event history and flags any write by a principal that is not a CI role; per-delivery SNS notifications have no consumer. Residual risk: no real-time alerting on control-plane events, only a nightly one — accepted at this scale, revisited if the operating model gains a second principal or an incident shows the nightly cadence was too slow." + } + }, + "confirmed_on": "2026-07-09" }, { "id": "DEC-033", @@ -942,7 +979,8 @@ "identifier": "WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail", "original_risk_rating": "low", "risk_adjustment": false - } + }, + "confirmed_on": "2026-07-11" }, { "id": "DEC-034", @@ -1127,7 +1165,8 @@ "original_detection_date": "2026-10-26", "source": { "detector": "OWASP ZAP baseline scan" - } + }, + "confirmed_on": "2026-11-04" }, { "id": "DEC-040", @@ -1154,6 +1193,676 @@ "original_detection_date": "2026-10-26", "source": { "detector": "OWASP ZAP baseline scan" + }, + "confirmed_on": "2026-11-04" + }, + { + "id": "DEC-100", + "title": "FedRAMP ID and UEI are simulated; the FedRAMP ID is FedRAMP's fallback, stamped on every FedRAMP report", + "disposition": "operational-requirement", + "status": "in-force", + "justification": "The operator has not submitted this offering to FedRAMP and is not registering on SAM.gov. The FedRAMP ID published everywhere is the fallback FedRAMP's CPO schema prescribes until an ID is assigned (the provider name and acronym), suffixed PROOF-OF-CONCEPT-NOT-A-REAL-FEDRAMP-ID so nobody mistakes it for a real one; the UEI is a placeholder no SAM.gov lookup will find. Both are flagged simulated in the CPO. The one value, in data/cds/offering.json, is carried by every report published in a FedRAMP schema (providerExtensions.fedRampId) and by the issue index, logs and snapshot manifests; scripts/check-fedramp-id.py fails the deploy otherwise.", + "controls": [], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "source": { + "detector": "FedRAMP 20x Class C rule records (data/frr-records.json)", + "drafted_by": "AI-drafted (Claude)", + "rules": [ + "CDS-CSO-FID", + "CDS-CSO-PUB" + ] + }, + "confirmed_on": "2026-11-06" + }, + { + "id": "DEC-101", + "title": "Ongoing Certification Reports and Quarterly Review content are published in full", + "disposition": "operational-requirement", + "status": "in-force", + "justification": "The operator determines that publishing each Ongoing Certification Report, and the content prepared for each Quarterly Review (its agenda, published in the report), will not likely have an adverse effect on the offering: the system holds no federal customer or agency data, the reports summarize what the public evidence already shows, and each report passes the automated sensitivity screen (scripts/_sensitivity.py: account IDs, outside email addresses, IP addresses, access keys, tokens, name handles) before it is written. Nothing waits on a person: a report the screen rejects is not written, and the build fails. Each report cites this record.", + "controls": [], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "source": { + "detector": "FedRAMP 20x Class C rule records (data/frr-records.json)", + "drafted_by": "AI-drafted (Claude)", + "rules": [ + "CCM-OCR-RPS", + "CCM-OCR-LSI", + "CCM-QTR-SCR" + ], + "reworded": { + "on": "2026-11-06", + "for": "no recurring manual work (operator's direction, 2026-11-06)", + "before": "The operator reviews anything the screen cannot judge before the report is issued.", + "after": "Nothing waits on a person: a report the screen rejects is not written, and the build fails." + } + }, + "confirmed_on": "2026-11-06" + }, + { + "id": "DEC-102", + "title": "The operator answers Ongoing Certification Report feedback and publishes an anonymized summary in the next report", + "disposition": "superseded", + "status": "closed", + "justification": "Questions and feedback on each issued report arrive through its GitHub issue form (linked from the report, prefilled with the report's date) or, for anything sensitive, the security contact in /.well-known/security.txt. The operator answers each, and before the next issue writes an anonymized, desensitized summary of the questions and answers in data/ocr-feedback.json (no names, agencies or identifying detail); the next report publishes it, and the build screens it and fails on an identifier.", + "controls": [], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "source": { + "detector": "FedRAMP 20x Class C rule records (data/frr-records.json)", + "drafted_by": "AI-drafted (Claude)", + "rules": [ + "CCM-OCR-AFS", + "CCM-OCR-FBM" + ] + }, + "closed_on": "2026-11-06", + "replaced_by": "The feedback intake and anonymized summary, automated: scripts/_quarterly_review.py (intake, qa_summary), exercised each quarter by simulated parties; the summary appears in the next OCR (scripts/build-ocr.py)." + }, + { + "id": "DEC-103", + "title": "The operator hosts a synchronous Quarterly Review after every Ongoing Certification Report", + "disposition": "superseded", + "status": "closed", + "justification": "The operator hosts a Quarterly Review by video call on the date the CCM calendar sets (5 business days after each report's issue), open to all necessary parties who register, and holds it even if nobody registers. It reviews the parts of the latest report most relevant to agencies and covers the standing agenda items the report publishes: KSI results and trend, vulnerability trend, and the plan for the next quarter.", + "controls": [], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "source": { + "detector": "FedRAMP 20x Class C rule records (data/frr-records.json)", + "drafted_by": "AI-drafted (Claude)", + "rules": [ + "CCM-QTR-MTG", + "CCM-QTR-ACT" + ] + }, + "closed_on": "2026-11-06", + "replaced_by": "The Quarterly Review, held on its date with simulated attendees by package-maintenance.yml (step 'Hold the Quarterly Review when due (simulated attendees)'); the deploy and the nightly fail when a review date passes with none published (scripts/check-quarterly-review.py)." + }, + { + "id": "DEC-104", + "title": "The operator records or transcribes each Quarterly Review and shares it", + "disposition": "superseded", + "status": "closed", + "justification": "The operator records or transcribes each Quarterly Review and supplies the recording or transcript to the parties who registered. A transcript published beyond them has every agency comment, question and name removed first, and is published only after the same no-adverse-effect check as the report (DEC-101).", + "controls": [], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "source": { + "detector": "FedRAMP 20x Class C rule records (data/frr-records.json)", + "drafted_by": "AI-drafted (Claude)", + "rules": [ + "CCM-QTR-RTR", + "CCM-QTR-SRR" + ] + }, + "closed_on": "2026-11-06", + "replaced_by": "The review's scripted transcript: the full one supplied to the simulated attendees as a log entry, the published one with every agency line removed (scripts/_quarterly_review.py)." + }, + { + "id": "DEC-105", + "title": "Quarterly Review attendees: agencies, FedRAMP and the assessor; other third parties only with specific relevance", + "disposition": "superseded", + "status": "closed", + "justification": "The operator invites agencies and FedRAMP to Quarterly Reviews, and the assessor by default. No other third party is invited unless it has specific relevance to the review, recorded with the invitation. The registration form states this policy.", + "controls": [], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "source": { + "detector": "FedRAMP 20x Class C rule records (data/frr-records.json)", + "drafted_by": "AI-drafted (Claude)", + "rules": [ + "CCM-QTR-RTP" + ] + }, + "closed_on": "2026-11-06", + "replaced_by": "The attendee policy in code (scripts/_quarterly_review.py check_roster): simulated agencies, the simulated FedRAMP and the simulated assessor; any other party only with its relevance recorded; nobody real (DEC-194)." + }, + { + "id": "DEC-106", + "title": "Quarterly Review content is screened for sensitive information before each review", + "disposition": "superseded", + "status": "closed", + "justification": "Before each Quarterly Review the operator checks the content to be shown against the same screen as the report (no account IDs, internal addresses, credentials, unpublished vulnerability detail beyond the public reports, or identifying information about agencies or people) and removes anything that would likely have an adverse effect on the offering if disclosed. The generated agenda is screened automatically with the report.", + "controls": [], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "source": { + "detector": "FedRAMP 20x Class C rule records (data/frr-records.json)", + "drafted_by": "AI-drafted (Claude)", + "rules": [ + "CCM-QTR-NID" + ] + }, + "closed_on": "2026-11-06", + "replaced_by": "The sensitivity screen run on all of each review's content before it is written (scripts/_quarterly_review.py build, scripts/_sensitivity.py)." + }, + { + "id": "DEC-107", + "title": "This offering seeks FedRAMP 20x certification only", + "disposition": "operational-requirement", + "status": "in-force", + "justification": "The operator seeks, if anything, FedRAMP 20x Program Certification (Class C) for this offering and will not seek FedRAMP Rev5 Program Certification for it. Every report states certificationType 20x; the Rev5 control view in the Security Decision Record explains how the 20x evidence meets the Rev5 objectives and is not a second certification claim. tests/test_certification_cycle.py fails if a published label names the Rev5 program as the certification sought.", + "controls": [], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "source": { + "detector": "FedRAMP 20x Class C rule records (data/frr-records.json)", + "drafted_by": "AI-drafted (Claude)", + "rules": [ + "FRC-CSO-POP" + ] + }, + "confirmed_on": "2026-11-06" + }, + { + "id": "DEC-150", + "title": "Root and operator MFA stays virtual TOTP: phishing-resistant MFA is accepted as not bought", + "disposition": "accepted", + "status": "in-force", + "justification": "Extends DEC-025. The AWS root user and the operator IAM user keep virtual authenticator-app (TOTP) MFA; a FIDO2 security key or passkey (IA-2(8), the Secure Configuration Guide's recommended default) is not being bought for this proof of concept. Residual risk: a TOTP code can be relayed by a real-time phishing site. Why it is accepted: both principals have MFA (IA-2(1)/(2) met); the root user has no access keys and is used only for root-only tasks; the operator user has no console password, so a phished TOTP code alone opens no console session; every production change goes through the reviewed, approval-gated deploy, not either principal; CloudTrail records both. The deploy checks both principals' MFA on every run (scripts/check-secure-config.py) and publishes the deviation against this record.", + "controls": [ + "ia-2.1", + "ia-2.2", + "ia-2.8", + "cm-6" + ], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [ + "aws-account::root", + "aws-iam-group::operators" + ] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "source": { + "drafted_by": "AI-drafted (Claude)" + }, + "confirmed_on": "2026-11-06" + }, + { + "id": "DEC-151", + "title": "Two-factor authentication on the GitHub owner account and no classic personal access tokens: a configuration fact, stated once", + "disposition": "operational-requirement", + "status": "in-force", + "justification": "The GitHub account that owns the repository has two-factor authentication enabled and issues no classic personal access tokens. GitHub exposes these settings only to the account itself, so no token the pipeline holds can read them; this record states them once as a configuration fact, cited by the Secure Configuration Guide setting github.owner-2fa. There is no recurring review. Every repository setting the pipeline can read (environments, branch protection, rulesets, workflow token permissions, Dependabot) is compared with the guide on every deploy and every night (scripts/check-secure-config.py).", + "controls": [ + "ia-2.1", + "ia-5", + "cm-6" + ], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [ + "github-owner" + ] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "source": { + "drafted_by": "AI-drafted (Claude)", + "amended": { + "on": "2026-11-06", + "change": "The quarterly review of sign-in methods, tokens, SSH keys and authorized applications is removed: replaced by the nightly comparison of the readable repository settings." + } + }, + "confirmed_on": "2026-11-06" + }, + { + "id": "DEC-152", + "title": "Service paths with no published CMVP module validation are accepted", + "disposition": "accepted", + "status": "in-force", + "justification": "AWS publishes CMVP certificates for module families (AWS-LC, the KMS HSM) but names no validated module for these paths this system uses: CloudFront viewer TLS, API Gateway HTTP API TLS, the Cognito Hosted UI, S3 SSE-S3, SQS SSE-SQS, the DynamoDB AWS-owned key, CloudTrail digest signing, the IAM OIDC provider, and the Silk Reeling Lambda's outbound TLS from the Python runtime. For the viewer-facing paths AWS offers no validated option (no FIPS endpoint for a distribution's viewer TLS, an HTTP API's execute-api endpoint, or the Hosted UI). The stores on SSE-S3, SSE-SQS and the AWS-owned key hold no customer data (site content, logs, audit trail, Terraform state and lock, failed compliance events); moving them to customer-managed KMS keys would add per-request KMS cost for no customer-data benefit. Every store of app data that supports a customer-managed key uses one, on the KMS HSM (CMVP #4884). The system holds no federal customer data. Listed per service in the Secure Configuration Guide's module list (CMU-CSO-CMD).", + "controls": [ + "sc-13", + "sc-8.1", + "sc-28.1" + ], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [ + "aws-cloudfront-distribution", + "aws-apigatewayv2-api::silk_reeling", + "aws-cognito-user-pool::silk_reeling", + "aws-s3-bucket", + "aws-sqs-queue::compliance_dlq", + "aws-dynamodb-table::tflock", + "aws-cloudtrail::management", + "aws-iam-oidc-provider::github", + "aws-lambda-function::silk_reeling" + ] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "source": { + "drafted_by": "AI-drafted (Claude)" + }, + "confirmed_on": "2026-11-06" + }, + { + "id": "DEC-160", + "title": "Trust-center access records: what is logged, and the lookup of a party's own records", + "disposition": "operational-requirement", + "status": "in-force", + "justification": "Access to the certification data is logged by CloudFront standard logging with a field allowlist that excludes IP address, forwarded-for, port, cookies, query string, user agent and referrer (infrastructure/bootstrap/trust-access-logs.tf); raw records expire after 90 days and only monthly aggregate counts for /.well-known/ and /trust/ are published, kept 13 months (scripts/build-access-summary.py). Because no requester identity is logged, a party's own records can be found only by the times and paths it gives: scripts/build-access-summary.py does that lookup, and every deploy exercises it against a simulated requester and publishes the outcome with the summaries. There is no commitment to any real party and no deadline: no FedRAMP or agency request is answered (DEC-194). Anyone who really, really wants their records can contact the operator through the security contact in /.well-known/security.txt, and he may consider it at his discretion. No agency is identified, and nothing is inferred from network data. This trades per-party attribution (CDS-TRC-ACL's SHOULD) for privacy, at the operator's direction of 2026-11-05.", + "controls": [ + "au-2", + "au-3", + "au-11", + "pt-2" + ], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [ + "aws-cloudfront-distribution" + ] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "point_of_contact": "Sam Aydlette (operator)", + "source": { + "drafted_by": "AI-drafted (Claude)", + "reworded": { + "on": "2026-11-06", + "for": "DEC-194 (no engagement), after confirmation", + "before": "Because no requester identity is logged, the operator provides a party, on request to the security contact, the published summaries and any records matching the times and paths the party identifies, within 10 business days.", + "after": "Because no requester identity is logged, a party's own records can be found only by the times and paths it gives: scripts/build-access-summary.py does that lookup, and every deploy exercises it against a simulated requester and publishes the outcome with the summaries. There is no commitment to any real party and no deadline: no FedRAMP or agency request is answered (DEC-194). Anyone who really, really wants their records can contact the operator through the security contact in /.well-known/security.txt, and he may consider it at his discretion.", + "title_before": "Trust-center access records: what is logged, and a party's own records on request", + "title_after": "Trust-center access records: what is logged, and the lookup of a party's own records" + } + }, + "confirmed_on": "2026-11-06" + }, + { + "id": "DEC-165", + "title": "Agency access to the certification package: decided by code rules over simulated requests; denial notices to the simulated FedRAMP, logged only", + "disposition": "operational-requirement", + "status": "in-force", + "justification": "The package is public, so no agency needs access granted. The access procedure (docs/procedures/agency-access.md) is built as code and exercised on every deploy against simulated agencies only: scripts/agency-access.py decides each simulated request by fixed rules (read access to a public package is granted; anything else, or a party that cannot be shown to exist, is denied with its reason), keeps the inventory and its history, writes each denial notice to the simulated FedRAMP as a log entry within 5 business days, and answers the simulated FedRAMP's inventory request. The deploy fails when a notice is late or overdue, and when data/agency-access.json holds any entry not marked simulated. The operator engages no real agency or FedRAMP about access (DEC-194): nothing is sent to anyone.", + "controls": [ + "ac-21", + "ca-6" + ], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "source": { + "drafted_by": "AI-drafted (Claude)" + }, + "confirmed_on": "2026-11-06" + }, + { + "id": "DEC-166", + "title": "Public sharing of the certification package: disclosure standard and determination of no likely adverse effect", + "disposition": "operational-requirement", + "status": "in-force", + "justification": "The operator has determined that publishing the whole certification package is not likely to have an adverse effect on the offering, because it carries no account IDs, secrets, credentials, personal email addresses, IAM user names, run IDs, raw logs or access-request contacts (each refused by a build gate), and the detail published on purpose (role names and policy summaries, the API and CloudFront hostnames, configurations and findings) grants no access on its own (docs/procedures/information-sharing.md). Re-checked by machine on every publish (the redaction gate, scripts/check-published-redaction.py); a new kind of artifact is added to the publishers' lists in a reviewed pull request, which revisits this determination.", + "controls": [ + "ac-22" + ], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "source": { + "drafted_by": "AI-drafted (Claude)", + "reworded": { + "on": "2026-11-06", + "for": "no recurring manual work (DEC-195)", + "before": "Reviewed annually and when a new kind of artifact is published.", + "after": "Re-checked by machine on every publish (the redaction gate, scripts/check-published-redaction.py); a new kind of artifact is added to the publishers' lists in a reviewed pull request, which revisits this determination." + } + }, + "confirmed_on": "2026-11-06" + }, + { + "id": "DEC-167", + "title": "Verification and validation use full populations, never representative samples", + "disposition": "operational-requirement", + "status": "in-force", + "justification": "The operator does not use representative samples in verification or validation: every check runs over its full population (every inventoried component, every live in-boundary resource, every SBOM, every rule record and every test it cites), and the simulated assessor re-checks every rule and KSI. The assessor guide states this (IVV-CSO-DUS). Any future use of sampling would be documented there and this record revised.", + "controls": [ + "ca-2", + "ca-7" + ], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "source": { + "drafted_by": "AI-drafted (Claude)" + }, + "confirmed_on": "2026-11-06" + }, + { + "id": "DEC-180", + "title": "Governed CVSS vectors for the configuration checks in infrastructure/schemas/check-vectors.json", + "status": "in-force", + "disposition": "operational-requirement", + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "justification": "Configuration checks (Checkov, tfsec) carry no CVE and no published vector, so without a decided vector their likely exploitability rests on Figure 7's last step (no score: LEV) and their impact on the scanner's severity, with no system context (VER-EVA-ELX, VER-EVA-EPA). Each vector in check-vectors.json that names this decision is adopted: it states what exploiting the misconfiguration needs and what it reaches in this system, with its rationale, and the VDR applies it to every finding of that check, so PAIN comes from the CVSS-Environmental derivation with the component's classification and LEV from Figure 7 (floor, no direct impact). A check without an adopted vector keeps the defaults. Revisited when its review_by date lapses (DEC-195); a changed check or a new resource type is re-decided in its pull request.", + "controls": [ + "ra-3", + "ra-5" + ], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [ + "infrastructure/schemas/check-vectors.json" + ] + }, + "source": { + "drafted_by": "AI-drafted (Claude)", + "reworded": { + "on": "2026-11-06", + "for": "no recurring manual work (DEC-195)", + "before": "Reviewed with the register; a changed check or a new resource type is re-decided.", + "after": "Revisited when its review_by date lapses (DEC-195); a changed check or a new resource type is re-decided in its pull request." + } + }, + "confirmed_on": "2026-11-06" + }, + { + "id": "DEC-181", + "title": "Exploitation assessment of detected vulnerabilities (VDR-CSO-RES)", + "status": "in-force", + "disposition": "operational-requirement", + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "justification": "Each VDR build records, per finding, whether exploitation has been observed: active when the source reports it, when the vulnerability is observed exploited, or when an incident record (data/incidents.json, once present) names the finding or its CVE; otherwise none observed, with that basis and the time assessed. Exploitation elsewhere is read from CISA KEV and the exploit-prediction score (known threats), which the triage policy already treats as likely exploitable. No person reviews logs for this assessment: it rests only on these automated sources, and every build records the basis and the time for each finding.", + "controls": [ + "ra-5", + "si-4", + "ir-4" + ], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [] + }, + "source": { + "drafted_by": "AI-drafted (Claude)", + "reworded": { + "on": "2026-11-06", + "for": "no recurring manual work (operator's direction, 2026-11-06)", + "before": "For each open internet-reachable, likely exploitable finding, the operator reviews the edge, API and CloudTrail logs for indicators tied to the advisory as part of incident response (docs/incident-response.md) and records any indication as an incident, which makes the finding's exploitation active in the next build.", + "after": "No person reviews logs for this assessment: it rests only on these automated sources, and every build records the basis and the time for each finding." + } + }, + "confirmed_on": "2026-11-06" + }, + { + "id": "DEC-182", + "title": "Responsible disclosure of vulnerability information (VER-RPT-NID, VER-RPT-RPD)", + "status": "in-force", + "disposition": "operational-requirement", + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "justification": "The provider discloses its vulnerability reports publicly (VER-RPT-RPD) and determines per finding that doing so will not likely lead to exploitation, recorded as public_disclosure on each finding. An open finding that is internet-reachable, likely exploitable and rated N3 or above is published in summary until it is remediated, fully mitigated or dispositioned: tracking ID, ratings, reachability, exploitability, dates, deadline and status stay public, so any party can make a risk-based decision; the description, observed locations, fixed versions and supplementary detail are withheld from the public artifacts (VDR report, detail report, accepted-vulnerability report and their renderings). Every other finding is disclosed in full: a dispositioned or lower-rated finding, or configuration already readable in the public source repository, gives an attacker nothing it would not otherwise have. The path that supplies the withheld detail to a necessary party is built and exercised on every VDR build against a simulated requester, which receives a log entry of what would be supplied and never the detail itself. There is no commitment to any real party and no deadline: no FedRAMP or agency request is answered (DEC-194). Anyone who really, really wants the detail can contact the operator through the security contact in /.well-known/security.txt, and he may consider it at his discretion.", + "controls": [ + "ra-5", + "si-5", + "ir-6" + ], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [] + }, + "source": { + "drafted_by": "AI-drafted (Claude)", + "reworded": { + "on": "2026-11-06", + "for": "DEC-194 (no engagement), after confirmation", + "before": "Necessary parties (FedRAMP, agency customers) receive the withheld detail from the provider on request through the security contact in /.well-known/security.txt.", + "after": "The path that supplies the withheld detail to a necessary party is built and exercised on every VDR build against a simulated requester, which receives a log entry of what would be supplied and never the detail itself. There is no commitment to any real party and no deadline: no FedRAMP or agency request is answered (DEC-194). Anyone who really, really wants the detail can contact the operator through the security contact in /.well-known/security.txt, and he may consider it at his discretion." + } + }, + "confirmed_on": "2026-11-06" + }, + { + "id": "DEC-190", + "title": "Quarterly verification and validation of non-machine resources, 2026-Q4 (VDR-TFR-NMV)", + "disposition": "superseded", + "status": "closed", + "justification": "The operator attests that on 2026-11-05 he verified and validated each non-machine resource listed in data/non-machine-resources.json against current practice, as each entry's 'verifies' states: the family policies, the runbooks, the incident response and recovery procedures, the continuous monitoring plan, the rules of behavior, the operator role and training record, the supply chain and significant change procedures, the privacy threshold analysis, this decision register and the governance domain registry. This replaces the overdue 2026-Q2 review (2026-05-08, next due 2026-08-08) in docs/security-review.md. Anything found out of date is recorded as its own decision or fixed in the resource. scripts/check-non-machine-vv.py fails the deploy when any entry is older than 92 days; the next verification is due by 2027-02-05 and is recorded as a new decision record.", + "controls": [ + "ca-7", + "pl-2", + "pm-31" + ], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [ + "data/non-machine-resources.json" + ] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "point_of_contact": "Sam Aydlette (operator)", + "source": { + "detector": "Quarterly non-machine verification and validation (VDR-TFR-NMV)", + "drafted_by": "AI-drafted (Claude)" + }, + "closed_on": "2026-11-06", + "replaced_by": "Machine verification of every non-machine resource on every deploy and every night (scripts/_nonmachine.py): paths and decision IDs resolve, no retired terms, tagged counts match the code." + }, + { + "id": "DEC-191", + "title": "KSI-CED-RAT has one automated method, not two: the second is accepted as not built (FRC-CSX-VVK)", + "disposition": "superseded", + "status": "closed", + "justification": "Extends the pattern of DEC-150. FRC-CSX-VVK asks Class C providers for at least two automated methods to verify and validate each KSI. KSI-CED-RAT (reviewing all training) has one: on every SDR build, scripts/build-sdr.py checks that the operator's training attestation (DEC-192) exists, is in force and was decided under 12 months ago. A second automated method is not built. Training here is a people-run process for a sole operator: no machine-based resource carries it, so there is nothing for the plan gate or the runtime re-validation to evaluate, and an automated check of training effectiveness (a learning-management system with tracked completions and assessments) would be a purchase and a third-party interconnection out of proportion to a one-person proof of concept. Residual risk: a lapse in training, or training that stops being effective, is caught only by the annual attestation and the quarterly non-machine review (DEC-190), not by a machine check. Why it is accepted: the system has one operator, who holds every role; the attestation's age is checked automatically and the build counts the KSI at one method, publishing this acceptance beside the count; the SDR states the shortfall plainly. Every other KSI has at least two automated methods, and the SDR build fails the package maintenance run when any KSI is short without an accepted record like this one.", + "controls": [ + "at-2", + "at-3", + "ca-2" + ], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [ + "ksi::KSI-CED-RAT" + ] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "point_of_contact": "Sam Aydlette (operator)", + "closed_on": "2026-11-06", + "replaced_by": "Two automated methods for KSI-CED-RAT in the Security Decision Record (scripts/build-sdr.py): the training packet is current against the system's data, and the simulated trainee completed it with a passing, effective score before its due date (scripts/_training.py).", + "source": { + "drafted_by": "AI-drafted (Claude)" + } + }, + { + "id": "DEC-192", + "title": "The operator completes and reviews his security training each year (KSI-CED-RAT attestation)", + "disposition": "superseded", + "status": "closed", + "justification": "The operator attests that he completes the training docs/training-log.md requires (general security, the privileged roles he holds, secure software delivery, and incident response and recovery), reviews whether it is effective at least once a year, and records each review as a dated entry in docs/training-log.md. This record is the attestation the Security Decision Record checks automatically for KSI-CED-RAT: it must be in force and decided under 12 months ago, so it is renewed with a new record each year. The quarterly non-machine verification (DEC-190, data/non-machine-resources.json NMR-REC-TRAINING) checks the training log itself.", + "controls": [ + "at-2", + "at-3", + "at-4" + ], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [ + "docs/training-log.md" + ] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "point_of_contact": "Sam Aydlette (operator)", + "closed_on": "2026-11-06", + "replaced_by": "The annual training packet generated from the system's own data and completed by a simulated trainee (scripts/_training.py), checked by two automated methods in the Security Decision Record.", + "source": { + "drafted_by": "AI-drafted (Claude)" + } + }, + { + "id": "DEC-193", + "title": "CodeQL py/weak-sensitive-data-hashing on the DAST scanner's Cognito SRP sign-in", + "disposition": "false-positive", + "status": "in-force", + "justification": "False positive. scripts/dast-cognito-token.py signs the DAST scanner user in to Cognito with SRP-6a, whose protocol fixes SHA-256 for the password-derived value x = H(salt | H(pool | user | ':' | password)). The hash is the protocol's computation, sent as a proof to Cognito; it is never stored, and a slow password hash would make Cognito reject the sign-in. Password storage is Cognito's.", + "controls": [ + "ra-5", + "sa-11.1" + ], + "applies_to": { + "check_ids": [], + "vuln_ids": [ + "codeql-py/weak-sensitive-data-hashing-107" + ], + "resources": [ + "scripts/dast-cognito-token.py" + ] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-06", + "review_by": "2027-11-06", + "original_detection_date": "2026-11-06", + "source": { + "detector": "CodeQL (GitHub code scanning)", + "drafted_by": "AI-drafted (Claude)" + }, + "confirmed_on": "2026-11-06" + }, + { + "id": "DEC-194", + "title": "No engagement: the operator does not engage FedRAMP or any federal agency about this system", + "disposition": "operational-requirement", + "status": "in-force", + "justification": "This system is a proof of concept. The operator does not engage FedRAMP or any federal agency about it, and makes them no submission, notice, invitation, access grant, meeting or commitment of any kind. Every counterparty a FedRAMP process names is simulated, and labelled as simulated wherever it is published: the assessor (Totally Real Assessment Services, LLC), FedRAMP itself (package submission, certification reports, denial and inbox notices), agencies (access requests, Quarterly Review attendance, feedback), incident-report recipients, the mail system, SAM.gov, and the people a people-run process needs (review attendees, a trainee). The mechanisms are real and run on every deploy or on their schedule; only the parties are not, and nothing is sent to anyone: a delivery is a published log entry. No public form or text invites anyone to file, register, attend or request anything, and nothing filed with or about this system will be acted on as a FedRAMP or agency matter. Anyone who really, really wants something can say hello through the security contact in /.well-known/security.txt (LinkedIn); the operator may consider it at his discretion, with no obligation and no deadline. What the simulations publish (exercise logs, Quarterly Review transcripts, training records, the anonymized feedback) holds no agency information because no agency takes part, and passes the same sensitivity screen as the reports before it is written. This record also states the operator's decision of 2026-11-05 to simulate the assessor and the incident-report recipients.", + "controls": [ + "ca-2", + "ca-6", + "ir-6", + "pm-15" + ], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-06", + "review_by": "2027-11-06", + "confirmed_on": "2026-11-06", + "source": { + "detector": "Operator direction, 2026-11-06", + "drafted_by": "AI-drafted (Claude)" + } + }, + { + "id": "DEC-195", + "title": "Three recurring human acts remain; every other recurring review is a mechanism", + "disposition": "operational-requirement", + "status": "in-force", + "justification": "The operator holds no recurring review by hand. Three recurring acts remain his, and only these: (1) the independent boundary corroboration, run by the operator at least every 30 days with read-only credentials (tools/boundary-map/corroborate.py; the trust center asks for attention when its report is older than 30 days); (2) acting on a decision record when its review_by date lapses (the trust center lists it, the gate that reads a lapsed finding or gate-mode decision fails, and the Annual Security Review fails while one is lapsed); (3) approving deploys in the production environment, which keeps the 30-day freshness windows of the deploy-built artifacts current. Every other review a policy, plan, procedure, KSI or rule record used to ask a person for runs as a mechanism on its own calendar, with a plainly simulated participant where a person is needed (DEC-194): the audit-log review every night (scripts/audit-log-review.py, KSI-MLA-RVL and KSI-CMT-RVP), the recovery exercise every month with a tabletop each November (scripts/hold-recovery-exercise.py, KSI-RPL-TRC), the Annual Security Review with the rules-of-behavior acknowledgement (scripts/hold-security-review.py, KSI-PIY-RIS, KSI-PIY-RES, KSI-SVC-EIS, KSI-INR-RPI, PL-4), the Quarterly Review (scripts/hold-quarterly-review.py), training (scripts/_training.py) and the verification of every policy and procedure (scripts/check-non-machine-vv.py). scripts/check-scheduled-review.py fails the run from the day after a due date with nothing published. A document, decision, rule record or control statement that commits a person to any other recurring review fails the machine checks (scripts/_nonmachine.py, tests/test_no_manual_work.py). A secret with no programmatic rotation source is rotated on compromise, not on a calendar (DEC-019).", + "controls": [ + "au-6", + "ca-7", + "cp-4", + "pl-4", + "pm-14" + ], + "applies_to": { + "check_ids": [], + "vuln_ids": [], + "resources": [] + }, + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-06", + "review_by": "2027-11-06", + "confirmed_on": "2026-11-06", + "source": { + "detector": "Operator direction, 2026-11-06 (no recurring manual work)", + "drafted_by": "AI-drafted (Claude)" } } ] diff --git a/data/dispositions/beyond-moderate.json b/data/dispositions/beyond-moderate.json deleted file mode 100644 index 8ee9aa71..00000000 --- a/data/dispositions/beyond-moderate.json +++ /dev/null @@ -1,176 +0,0 @@ -{ - "_note": "Dispositions for controls required by GovRAMP/TX-RAMP/CMMC above the FedRAMP Moderate baseline. Read by the spoke projections alongside the Moderate hub.", - "controls": { - "ac-3.14": { - "status": "not-applicable", - "origination": "sp-system", - "statement": "No individual data subjects. The system has a single operator and holds no end-user personally identifiable information, so individual-access mechanisms do not apply." - }, - "pe-8.3": { - "status": "not-applicable", - "origination": "inherited", - "statement": "Physical access is inherited from AWS; the system maintains no visitor access records of its own." - }, - "si-12.1": { - "status": "not-applicable", - "origination": "sp-system", - "statement": "The system processes no personally identifiable information, so there are no PII elements to limit." - }, - "si-12.2": { - "status": "not-applicable", - "origination": "sp-system", - "statement": "No PII is used in testing, training, or research; the system processes no PII at all." - }, - "si-12.3": { - "status": "not-applicable", - "origination": "sp-system", - "statement": "No PII is stored, so there is no PII disposal obligation." - }, - "sc-19": { - "status": "not-applicable", - "origination": "sp-system", - "statement": "No Voice over IP technologies are used anywhere in the system." - }, - "si-4.14": { - "status": "not-applicable", - "origination": "inherited", - "statement": "No wireless networks. The system is cloud-hosted on AWS; wireless intrusion detection does not apply and is inherited where relevant." - }, - "sc-7.27": { - "status": "not-applicable", - "origination": "sp-system", - "statement": "Standalone system with no external system interconnections to classify or manage." - }, - "ia-12.4": { - "status": "not-applicable", - "origination": "sp-system", - "statement": "No end users to identity-proof. The sole operator's identity is managed through AWS IAM and the GitHub deploy identity." - }, - "mp-6.2": { - "status": "not-applicable", - "origination": "inherited", - "statement": "No physical media. Media sanitization and its testing are inherited from AWS." - }, - "pe-14.2": { - "status": "not-applicable", - "origination": "inherited", - "statement": "Physical environment monitoring is inherited from AWS data-center operations." - }, - "ac-10": { - "status": "not-applicable", - "origination": "sp-system", - "statement": "Application authentication is HTTP Basic, which is sessionless, and there is a single operator account. There is no session state to limit." - }, - "ac-17.9": { - "status": "implemented", - "origination": "inherited", - "statement": "Administrative reach is AWS IAM and the GitHub deploy identity, both of which support immediate revocation. No long-lived access keys are used." - }, - "sc-6": { - "status": "implemented", - "origination": "inherited", - "statement": "Resource availability is provided by AWS: Shield Standard on CloudFront absorbs volumetric denial of service, and Lambda runs under account concurrency limits." - }, - "sc-7.13": { - "status": "implemented", - "origination": "sp-system", - "statement": "Security functions are isolated from application functions: the OPA gate, scanners, and Sigstore signing run in GitHub Actions CI, and the runtime KSI validator is a separate Lambda from the application Lambda." - }, - "cp-9.3": { - "status": "implemented", - "origination": "sp-system", - "statement": "The canonical source of truth is the GitHub repository, administratively and geographically separate from the AWS deployment, and S3 versioning retains prior object states." - }, - "sc-7.23": { - "status": "implemented", - "origination": "inherited", - "statement": "CloudFront returns standardized error responses and does not leak verbose protocol-validation feedback to senders." - }, - "cm-14": { - "status": "implemented", - "origination": "sp-system", - "statement": "Published artifacts are Sigstore keyless-signed and the deploy verifies signatures, so only signed components are accepted (CM-5(3) / signed components)." - }, - "sa-10.1": { - "status": "implemented", - "origination": "sp-system", - "statement": "Software and firmware integrity is verifiable: every published artifact carries a Sigstore bundle and a Syft SBOM, checkable with cosign." - }, - "sc-12.2": { - "status": "implemented", - "origination": "inherited", - "statement": "Symmetric key management is AWS-managed: S3 server-side encryption uses AES-256 with AWS-managed keys; the system manages no symmetric keys of its own." - }, - "sc-12.3": { - "status": "implemented", - "origination": "inherited", - "statement": "Asymmetric key management for TLS is handled by AWS Certificate Manager, which provisions and rotates the certificate keys." - }, - "au-9.2": { - "status": "implemented", - "origination": "inherited", - "statement": "Audit records are written to CloudWatch Logs, a service separate from the application compute, providing off-box retention." - }, - "cm-10.1": { - "status": "implemented", - "origination": "sp-corporate", - "statement": "Open-source components are inventoried by the Syft SBOM on every deploy and governed by the documented supply-chain policy." - }, - "ca-2.2": { - "status": "implemented", - "origination": "sp-corporate", - "statement": "Specialized assessment is covered by the annual security review plus the per-deploy VDR aggregator, which classifies findings on the FedRAMP 20x PAIN scale." - }, - "ir-7.2": { - "status": "implemented", - "origination": "sp-corporate", - "statement": "Incident-response coordination with AWS as the underlying provider is documented in the incident response plan." - }, - "sa-4.8": { - "status": "implemented", - "origination": "sp-corporate", - "statement": "A continuous monitoring plan is maintained and published; it is the acquisition-time ConMon plan this enhancement asks for." - }, - "sa-9.4": { - "status": "implemented", - "origination": "sp-corporate", - "statement": "Consistency of interests with the external provider (AWS) is addressed through the documented use of the AWS authorization package and operator policy." - }, - "cp-2.2": { - "status": "implemented", - "origination": "inherited", - "statement": "Capacity is handled by serverless auto-scaling: Lambda and CloudFront scale with demand under AWS-managed capacity." - }, - "sa-11.8": { - "status": "implemented", - "origination": "sp-corporate", - "statement": "Dynamic code analysis runs in CI as a scheduled monthly OWASP ZAP baseline scan (.github/workflows/zap-dast.yml) against the live site, with findings tracked via the ZAP issue and triaged into the POA&M. The scan covers the unauthenticated static surface today; authenticated coverage of the Basic-Auth-gated taiji application is a tracked follow-up. SAST (Checkov, tfsec) and SCA (Syft/Grype) run on every deploy alongside it." - }, - "ra-5.8": { - "status": "implemented", - "origination": "sp-corporate", - "statement": "Historic audit records are retained in CloudWatch and the daily Grype re-scan catches newly disclosed CVEs against deployed dependencies; review for prior exploitation is part of the security-review cadence." - }, - "ra-5.6": { - "status": "implemented", - "origination": "sp-system", - "statement": "Automated cross-run vulnerability trend analysis is published as a live chart on the trust dashboard, fed by a CVE-keyed trend ledger (/.well-known/vdr-trend.json) that each VDR build appends to via build-vdr-trend.py." - } - }, - "spoke_not_applicable": { - "ia-0": "No Criminal Justice Information is processed; the CJIS overlay does not apply (Originating Agency Identifier).", - "ia-5.j": "No Criminal Justice Information is processed; CJIS authenticator additions do not apply.", - "ia-5.k": "No Criminal Justice Information is processed; CJIS authenticator additions do not apply.", - "ia-5.l": "No Criminal Justice Information is processed; CJIS authenticator additions do not apply.", - "ia-5.m": "No Criminal Justice Information is processed; CJIS authenticator additions do not apply.", - "ia-5.n": "No Criminal Justice Information is processed; CJIS authenticator additions do not apply.", - "ia-5.o": "No Criminal Justice Information is processed; CJIS authenticator additions do not apply." - }, - "cmmc_requirement_dispositions": { - "3.12.4": { - "class": "customer-responsibility", - "srm": "osc-responsibility", - "statement": "Maintaining a system security plan is the customer's own obligation. 800-171 Rev2 Table D-1 maps 3.12.4 to no 800-53 control, so the CSP does not provide it; the provider publishing its own OSCAL SSP does not discharge a consuming organization's duty to maintain theirs." - } - } -} diff --git a/data/frr-records.json b/data/frr-records.json new file mode 100644 index 00000000..fbc880f9 --- /dev/null +++ b/data/frr-records.json @@ -0,0 +1,4460 @@ +{ + "schema": "frr-records/1", + "$comment": "One record per FedRAMP rule applicable to 20x Program Class C. Validated by scripts/_frr.py; see infrastructure/schemas/frr-records.schema.json.", + "basis": "Drafted 2026-11-05 from a rule-by-rule assessment of the repository and the live site, corrected for the changes since (account IDs redacted, published claims fixed, CR26 vulnerability reports published). AI-drafted; for the operator's review. Each record states the state after a successful deploy of the commit that contains it: what that deploy does counts as done, and a prerequisite it depends on must make the deploy fail when missing, so the record is accurate when published.", + "records": [ + { + "frr_id": "AFC-CSO-ACK", + "status": "Implemented", + "implementation": "SIMULATED FOR THIS PROOF OF CONCEPT: there is no FedRAMP Security Inbox, no mail is received or sent, and FedRAMP is directed to the operator on LinkedIn (https://www.linkedin.com/in/sa2/). The acknowledgement logic (scripts/_fsi.py, build_ack and receive) acknowledges each FedRAMP message once, even when it is redelivered, with headers inbound content cannot inject, and never to auto-replies, bulk mail, bounces, mail without a From address, or mail failing SPF/DKIM/DMARC (FedRAMP's own mail passes them, AFC-FRP-VRE; this keeps a forged sender from using the inbox as a reflector; such mail is still registered and paged). In the simulation each acknowledgement is built and checked for header safety, then filed nowhere. Every deploy runs this logic (scripts/_fsi.py) over committed synthetic messages (data/fsi-simulation/messages.json) in the step 'FedRAMP Security Inbox simulation', fails the deploy if any outcome differs from the expected one, and publishes the signed, dated result, labelled as a simulation, as /.well-known/fedramp-inbox-simulation.json.", + "evidence": [ + { + "kind": "step", + "ref": "deploy-with-opa.yml#FedRAMP Security Inbox simulation (synthetic messages; nothing received or sent)" + }, + { + "kind": "artifact", + "ref": ".well-known/fedramp-inbox-simulation.json" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_inbox.py::test_nothing_from_the_inbound_message_can_inject_a_header" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_inbox.py::test_a_redelivered_message_is_acknowledged_and_paged_once" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_inbox.py::test_unauthenticated_fedramp_mail_is_registered_and_paged_but_not_acknowledged" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_inbox.py::test_no_acknowledgement_to_auto_replies_bulk_mail_or_bounces" + } + ], + "simulated": { + "counterparty": "mail", + "how": "The mail system and FedRAMP's messages are simulated: synthetic messages run through the real inbox logic on every deploy, outbound acknowledgements and pages are recorded, never sent, and the published contact is 'Hit me up on LinkedIn'." + } + }, + { + "frr_id": "AFC-CSO-CRA", + "status": "Implemented", + "implementation": "SIMULATED FOR THIS PROOF OF CONCEPT: there is no FedRAMP Security Inbox, no mail is received or sent, and FedRAMP is directed to the operator on LinkedIn (https://www.linkedin.com/in/sa2/). Emergency and Emergency Test messages (subject designator, AFC-FRP-CDS) get a register item with a deadline: by default 3:00 p.m. ET on the 2nd business day (AFC-FRP-ERT, Class C; the receipt day counts and holidays are not skipped, both erring earlier), replaced at triage by the timeframe the message states; the register reports an item past its deadline until it is closed (scripts/_fsi.py, deadlines, triage, close, overdue). In the simulation the Emergency Test received on a Friday is due 3:00 p.m. ET the following Monday, is reported once that passes, and stops being reported when closed. Every deploy runs this logic (scripts/_fsi.py) over committed synthetic messages (data/fsi-simulation/messages.json) in the step 'FedRAMP Security Inbox simulation', fails the deploy if any outcome differs from the expected one, and publishes the signed, dated result, labelled as a simulation, as /.well-known/fedramp-inbox-simulation.json.", + "evidence": [ + { + "kind": "step", + "ref": "deploy-with-opa.yml#FedRAMP Security Inbox simulation (synthetic messages; nothing received or sent)" + }, + { + "kind": "artifact", + "ref": ".well-known/fedramp-inbox-simulation.json" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_inbox.py::test_class_c_default_deadline_is_3pm_eastern_on_the_second_business_day" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_inbox.py::test_emergency_records_carry_a_deadline_and_important_ones_ask_for_the_messages_own" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_inbox.py::test_overdue_counts_untriaged_unclosed_and_failed_legs" + } + ], + "simulated": { + "counterparty": "mail", + "how": "The mail system and FedRAMP's messages are simulated: synthetic messages run through the real inbox logic on every deploy, outbound acknowledgements and pages are recorded, never sent, and the published contact is 'Hit me up on LinkedIn'." + } + }, + { + "frr_id": "AFC-CSO-EMR", + "status": "Implemented", + "implementation": "SIMULATED FOR THIS PROOF OF CONCEPT: there is no FedRAMP Security Inbox, no mail is received or sent, and FedRAMP is directed to the operator on LinkedIn (https://www.linkedin.com/in/sa2/). Every FedRAMP message, Emergency-designated ones included, produces a page to the senior security official (the accountable official named in the CPO, the operator) naming the designation and the sender's domain (scripts/_fsi.py, receive and page_subject); an Emergency from an address other than FedRAMP's designated Emergency senders (AFC-FRP-UFS) is flagged, not demoted. In the simulation the page is recorded, not delivered: the operator's phone stays blissfully quiet. Every deploy runs this logic (scripts/_fsi.py) over committed synthetic messages (data/fsi-simulation/messages.json) in the step 'FedRAMP Security Inbox simulation', fails the deploy if any outcome differs from the expected one, and publishes the signed, dated result, labelled as a simulation, as /.well-known/fedramp-inbox-simulation.json.", + "evidence": [ + { + "kind": "step", + "ref": "deploy-with-opa.yml#FedRAMP Security Inbox simulation (synthetic messages; nothing received or sent)" + }, + { + "kind": "artifact", + "ref": ".well-known/fedramp-inbox-simulation.json" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_inbox.py::test_an_emergency_from_an_address_other_than_fedramp_security_is_flagged_not_demoted" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_inbox.py::test_the_page_subject_is_ascii_and_names_the_domain_not_the_address" + } + ], + "simulated": { + "counterparty": "mail", + "how": "The mail system and FedRAMP's messages are simulated: synthetic messages run through the real inbox logic on every deploy, outbound acknowledgements and pages are recorded, never sent, and the published contact is 'Hit me up on LinkedIn'." + } + }, + { + "frr_id": "AFC-CSO-IMA", + "status": "Implemented", + "implementation": "SIMULATED FOR THIS PROOF OF CONCEPT: there is no FedRAMP Security Inbox, no mail is received or sent, and FedRAMP is directed to the operator on LinkedIn (https://www.linkedin.com/in/sa2/). Important-designated messages open a register item that cannot be triaged without recording the timeframe the message states; the register reports it while untriaged after 24 hours, triaged without a timeframe, or past that timeframe and not closed (scripts/_fsi.py, triage and overdue). The simulation checks each of these. Every deploy runs this logic (scripts/_fsi.py) over committed synthetic messages (data/fsi-simulation/messages.json) in the step 'FedRAMP Security Inbox simulation', fails the deploy if any outcome differs from the expected one, and publishes the signed, dated result, labelled as a simulation, as /.well-known/fedramp-inbox-simulation.json.", + "evidence": [ + { + "kind": "step", + "ref": "deploy-with-opa.yml#FedRAMP Security Inbox simulation (synthetic messages; nothing received or sent)" + }, + { + "kind": "artifact", + "ref": ".well-known/fedramp-inbox-simulation.json" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_inbox.py::test_an_important_message_cannot_be_triaged_without_its_stated_timeframe" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_inbox.py::test_overdue_counts_untriaged_unclosed_and_failed_legs" + } + ], + "simulated": { + "counterparty": "mail", + "how": "The mail system and FedRAMP's messages are simulated: synthetic messages run through the real inbox logic on every deploy, outbound acknowledgements and pages are recorded, never sent, and the published contact is 'Hit me up on LinkedIn'." + } + }, + { + "frr_id": "AFC-CSO-INB", + "status": "Implemented", + "implementation": "SIMULATED FOR THIS PROOF OF CONCEPT: there is no FedRAMP Security Inbox, no mail is received or sent, and FedRAMP is directed to the operator on LinkedIn (https://www.linkedin.com/in/sa2/). The published FedRAMP Security Inbox contact (data/cds/offering.json, fedramp_security_inbox.contact, published in the CPO's certification_data) says, plainly, that the inbox does not exist and to hit the operator up on LinkedIn. The logic a real inbox would run receives, classifies, registers, acknowledges and pages. Every deploy runs this logic (scripts/_fsi.py) over committed synthetic messages (data/fsi-simulation/messages.json) in the step 'FedRAMP Security Inbox simulation', fails the deploy if any outcome differs from the expected one, and publishes the signed, dated result, labelled as a simulation, as /.well-known/fedramp-inbox-simulation.json.", + "evidence": [ + { + "kind": "step", + "ref": "deploy-with-opa.yml#FedRAMP Security Inbox simulation (synthetic messages; nothing received or sent)" + }, + { + "kind": "artifact", + "ref": ".well-known/fedramp-inbox-simulation.json" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_inbox.py::test_the_simulation_passes_and_publishes_a_labelled_result_without_addresses" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_inbox.py::test_the_cpo_publishes_the_simulated_contact_not_an_email_address" + } + ], + "simulated": { + "counterparty": "mail", + "how": "The mail system and FedRAMP's messages are simulated: synthetic messages run through the real inbox logic on every deploy, outbound acknowledgements and pages are recorded, never sent, and the published contact is 'Hit me up on LinkedIn'." + } + }, + { + "frr_id": "AFC-CSO-NOC", + "status": "Implemented", + "implementation": "SIMULATED FOR THIS PROOF OF CONCEPT: there is no FedRAMP Security Inbox, no mail is received or sent, and the published contact points to the operator on LinkedIn (https://www.linkedin.com/in/sa2/). The contact has one source (data/cds/offering.json, fedramp_security_inbox.contact) with an append-only history; each change is a history entry dated by since. scripts/check-fsi-notice.py, in the unit-test job on every pull request and push, fails a changed contact without a new dated history entry, a hand-recorded notice, or a rewritten history against the merge base. On every deploy, scripts/submit-package.py files a change notice with the simulated FedRAMP for every change not yet filed (an entry in changeNotices of the signed /.well-known/package-submission-log.json, with the simulated FedRAMP's receipt; nothing is sent), carries earlier notices over unchanged, and fails the deploy unless every notice is filed within one business day of the deploy that first published the changed contact. A change takes effect when it is published, so the clock runs from that deploy (recorded in the log's inboxContact and on each notice as publishedOn and publishedIn): the deploy that first publishes a new contact files its notice the same day, a change merged but not yet deployed cannot go stale, and a failed deploy, which publishes nothing, cannot make the next one late. A notice filed later than one business day after the publishing deploy still fails. The contact was established 2026-11-05 with no earlier contact to change from, so no notice has been filed yet. Procedure: docs/runbooks/fedramp-security-inbox.md.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_fsi_notice.py::test_the_deploy_files_a_change_notice_once_and_carries_it_over" + }, + { + "kind": "test", + "ref": "tests/test_fsi_notice.py::test_a_change_first_deployed_ten_business_days_after_it_was_merged_passes" + }, + { + "kind": "test", + "ref": "tests/test_fsi_notice.py::test_a_contact_an_earlier_deploy_published_keeps_that_deploy_as_its_clock" + }, + { + "kind": "test", + "ref": "tests/test_fsi_notice.py::test_known_bad_a_late_notice_on_record_fails_the_deploy" + }, + { + "kind": "test", + "ref": "tests/test_fsi_notice.py::test_a_contact_change_without_a_history_entry_fails" + }, + { + "kind": "test", + "ref": "tests/test_fsi_notice.py::test_rewriting_history_fails_against_the_base" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#FedRAMP Security Inbox change notice (AFC-CSO-NOC)" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Simulated package submission to FedRAMP (nothing is sent)" + }, + { + "kind": "artifact", + "ref": ".well-known/package-submission-log.json" + } + ], + "simulated": { + "counterparty": "fedramp", + "how": "No FedRAMP counterpart exists. A change notice is filed with FedRAMP (simulated): simulated_fedramp_notice_intake() in scripts/submit-package.py, a function that never touches the network, returns the receipt, and the only trace is the entry in the signed submission log. No real FedRAMP is notified (DEC-194)." + } + }, + { + "frr_id": "AFC-CSO-RCV", + "status": "Implemented", + "implementation": "SIMULATED FOR THIS PROOF OF CONCEPT: there is no FedRAMP Security Inbox, no mail is received or sent, and FedRAMP is directed to the operator on LinkedIn (https://www.linkedin.com/in/sa2/). Nothing in the inbox logic asks anything of FedRAMP or drops FedRAMP mail: every FedRAMP message is registered and paged whatever its verdicts (the simulation fails the deploy otherwise), a failed acknowledgement is recorded, reported overdue and sent once on retry, and overdue items are reported by the register (scripts/_fsi.py, receive and overdue). Every deploy runs this logic (scripts/_fsi.py) over committed synthetic messages (data/fsi-simulation/messages.json) in the step 'FedRAMP Security Inbox simulation', fails the deploy if any outcome differs from the expected one, and publishes the signed, dated result, labelled as a simulation, as /.well-known/fedramp-inbox-simulation.json.", + "evidence": [ + { + "kind": "step", + "ref": "deploy-with-opa.yml#FedRAMP Security Inbox simulation (synthetic messages; nothing received or sent)" + }, + { + "kind": "artifact", + "ref": ".well-known/fedramp-inbox-simulation.json" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_inbox.py::test_a_failed_acknowledgement_is_recorded_retried_and_counted_overdue" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_inbox.py::test_overdue_counts_untriaged_unclosed_and_failed_legs" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_inbox.py::test_each_register_check_fails_the_simulation_when_its_outcome_differs" + } + ], + "simulated": { + "counterparty": "mail", + "how": "The mail system and FedRAMP's messages are simulated: synthetic messages run through the real inbox logic on every deploy, outbound acknowledgements and pages are recorded, never sent, and the published contact is 'Hit me up on LinkedIn'." + } + }, + { + "frr_id": "AFC-CSO-TFG", + "status": "Implemented", + "implementation": "SIMULATED FOR THIS PROOF OF CONCEPT: there is no FedRAMP Security Inbox, no mail is received or sent, and FedRAMP is directed to the operator on LinkedIn (https://www.linkedin.com/in/sa2/). Classification (scripts/_fsi.py, classify): a message whose From address or envelope sender is exactly @fedramp.gov or @gsa.gov is FedRAMP, whatever its spam verdict or SPF/DKIM/DMARC result; look-alike domains and display-name spoofs are not; failed authentication is recorded so the operator can confirm the sender, never used to filter. The simulation includes a forged @gsa.gov message (still FedRAMP), a FedRAMP envelope sender behind an unreadable From (still FedRAMP), a look-alike domain and a display-name spoof (neither is FedRAMP). Automated validation of the configuration is the deploy-time simulation itself. Every deploy runs this logic (scripts/_fsi.py) over committed synthetic messages (data/fsi-simulation/messages.json) in the step 'FedRAMP Security Inbox simulation', fails the deploy if any outcome differs from the expected one, and publishes the signed, dated result, labelled as a simulation, as /.well-known/fedramp-inbox-simulation.json.", + "evidence": [ + { + "kind": "step", + "ref": "deploy-with-opa.yml#FedRAMP Security Inbox simulation (synthetic messages; nothing received or sent)" + }, + { + "kind": "artifact", + "ref": ".well-known/fedramp-inbox-simulation.json" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_inbox.py::test_fedramp_senders_are_fedramp_even_when_unauthenticated" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_inbox.py::test_look_alike_domains_and_display_name_spoofs_are_not_fedramp" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_inbox.py::test_a_fedramp_envelope_sender_counts_even_if_the_from_header_is_unparseable" + } + ], + "simulated": { + "counterparty": "mail", + "how": "The mail system and FedRAMP's messages are simulated: synthetic messages run through the real inbox logic on every deploy, outbound acknowledgements and pages are recorded, never sent, and the published contact is 'Hit me up on LinkedIn'." + } + }, + { + "frr_id": "CCM-OCR-AFS", + "status": "Implemented", + "implementation": "Each OCR carries an anonymized, desensitized summary of the questions and answers on the previous issued report (providerExtensions.feedback.summaryOfPreviousReport), built by the same function (scripts/_quarterly_review.py, qa_summary) that writes it into that report's Quarterly Review, once the review date has passed; before then it says the summary appears once the review is held. Submissions carry no party, name or agency into the summary, and the summary passes the OCR's sensitivity screen.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_feedback_summary_covers_the_previous_issue" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_a_feedback_summary_never_carries_a_name_or_an_agency" + }, + { + "kind": "test", + "ref": "tests/test_quarterly_review.py::test_the_ocr_summary_and_the_review_carry_the_same_qa" + }, + { + "kind": "step", + "ref": "package-maintenance.yml#Hold the Quarterly Review when due (simulated attendees)" + }, + { + "kind": "artifact", + "ref": ".well-known/ongoing-certification-report.json" + }, + { + "kind": "artifact", + "ref": ".well-known/quarterly-reviews.json" + }, + { + "kind": "decision", + "ref": "DEC-194" + } + ], + "simulated": { + "counterparty": "agency", + "how": "No real feedback is solicited (DEC-194). Each quarter simulated agencies, the simulated FedRAMP and the simulated assessor submit scripted questions through the intake in scripts/_quarterly_review.py; they are answered by rule and published anonymized." + } + }, + { + "frr_id": "CCM-OCR-AVL", + "status": "Implemented", + "implementation": "On each calendar issue date the maintainer issues the OCR covering the period since the previous issue: frozen ocr-issue-<date>.json and .md, signed, never rewritten, listed with its sha256 in /.well-known/ocr-issues.json. The rolling OCR between issues carries all eight summaries, the incidents from the incident register (or an attestation of none), and the review schedule.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_first_run_on_an_issue_date_freezes_the_report_and_snapshots_the_package" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_an_issued_report_is_carried_over_and_never_rebuilt" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_reportable_incidents_come_from_the_register_and_exercises_say_so" + }, + { + "kind": "step", + "ref": "package-maintenance.yml#Issue the quarterly report when due (frozen, with a snapshot)" + }, + { + "kind": "artifact", + "ref": ".well-known/ocr-issues.json" + } + ] + }, + { + "frr_id": "CCM-OCR-FBM", + "status": "Implemented", + "implementation": "Each OCR names its asynchronous feedback intake (providerExtensions.feedback.channel): a submission names the report's issue date and a question, is validated (it must be about that report and from a party marked simulated), screened, and answered by rule, and the Q&A is published with that report's Quarterly Review. No form or channel is offered to real parties (DEC-194).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_rolling_ocr_validates_and_carries_the_cycle" + }, + { + "kind": "test", + "ref": "tests/test_quarterly_review.py::test_a_submission_not_from_a_simulated_party_is_refused" + }, + { + "kind": "step", + "ref": "package-maintenance.yml#Hold the Quarterly Review when due (simulated attendees)" + }, + { + "kind": "artifact", + "ref": ".well-known/ongoing-certification-report.json" + }, + { + "kind": "artifact", + "ref": ".well-known/quarterly-reviews.json" + }, + { + "kind": "decision", + "ref": "DEC-194" + } + ], + "simulated": { + "counterparty": "agency", + "how": "No real feedback is solicited (DEC-194). Each quarter simulated agencies, the simulated FedRAMP and the simulated assessor submit scripted questions through the intake in scripts/_quarterly_review.py; they are answered by rule and published anonymized." + } + }, + { + "frr_id": "CCM-OCR-LSI", + "status": "Implemented", + "implementation": "Before the OCR is written, every string in it passes a sensitivity screen (account IDs, email addresses outside the system's and FedRAMP's domains, IP addresses, AWS keys, tokens and private keys, @handles); a hit fails the build. The publication redaction gate checks it again before publishing. The public-release determination is DEC-101.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_sensitivity_screen_catches_each_kind" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_an_ocr_carrying_a_personal_address_is_never_built" + }, + { + "kind": "decision", + "ref": "DEC-101" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build Ongoing Certification Report (CCM)" + } + ] + }, + { + "frr_id": "CCM-OCR-NRD", + "status": "Implemented", + "implementation": "The next OCR date comes from the fixed CCM calendar (infrastructure/schemas/ccm-calendar.json), stays the same between issues, and is published in the OCR, the CPO (serviceProperties.nextOngoingCertificationReportDate) and the issue index.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_next_dates_hold_steady_between_issues_and_move_on_the_issue_date" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_cpo_publishes_the_fixed_cycle_dates" + }, + { + "kind": "artifact", + "ref": ".well-known/certification-package-overview.json" + }, + { + "kind": "artifact", + "ref": ".well-known/ongoing-certification-report.json" + } + ] + }, + { + "frr_id": "CCM-OCR-RPS", + "status": "Implemented", + "implementation": "Exercised: each OCR is published in full and records the public-release determination (providerExtensions.publicRelease, DEC-101) after passing the sensitivity screen.", + "evidence": [ + { + "kind": "decision", + "ref": "DEC-101" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_rolling_ocr_validates_and_carries_the_cycle" + }, + { + "kind": "artifact", + "ref": ".well-known/ongoing-certification-report.json" + } + ], + "may_rationale": "Exercised. The system exists to demonstrate FedRAMP 20x in the open, and the OCR carries no federal customer or agency data, so it is published in full, and each report records the no-adverse-effect determination (DEC-101)." + }, + { + "frr_id": "CCM-OCR-SOR", + "status": "Implemented", + "implementation": "The OCR is issued on a regular 3-month cycle of fixed dates set in the CCM calendar, each a business day placed away from the beginning, middle and end of its quarter (late in the second month); the calendar is validated on every build and must keep two dates ahead.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_committed_calendar_is_valid" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_a_bad_calendar_fails_closed" + }, + { + "kind": "step", + "ref": "package-maintenance.yml#Issue the quarterly report when due (frozen, with a snapshot)" + }, + { + "kind": "artifact", + "ref": ".well-known/ocr-issues.json" + } + ] + }, + { + "frr_id": "CCM-QTR-ACT", + "status": "Implemented", + "implementation": "Each Quarterly Review's agenda (scripts/_quarterly_review.py, agenda) is filled from the issued report: its changes, transformative changes and incidents, plus standing agency-relevant items (KSI results and trend, accepted vulnerabilities and trend, the next quarter's planned changes) and the intake's questions. The OCR publishes the standing agenda and the review publishes the filled one.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_rolling_ocr_validates_and_carries_the_cycle" + }, + { + "kind": "test", + "ref": "tests/test_quarterly_review.py::test_the_review_is_simulated_says_so_and_invites_nobody" + }, + { + "kind": "step", + "ref": "package-maintenance.yml#Hold the Quarterly Review when due (simulated attendees)" + }, + { + "kind": "artifact", + "ref": ".well-known/quarterly-reviews.json" + }, + { + "kind": "artifact", + "ref": ".well-known/ongoing-certification-report.json" + }, + { + "kind": "decision", + "ref": "DEC-194" + } + ], + "simulated": { + "counterparty": "personnel", + "how": "No real party attends (DEC-194). On each review date package-maintenance.yml holds the review with a simulated roster (Department of Hypothetical Affairs (simulated), Bureau of Made-Up Statistics (simulated), FedRAMP (simulated), Totally Real Assessment Services, LLC (simulated)), hosted by the workflow itself, and publishes the result; nothing is sent to anyone." + } + }, + { + "frr_id": "CCM-QTR-MTG", + "status": "Implemented", + "implementation": "A Quarterly Review is held 5 business days after each OCR issue: package-maintenance.yml, which runs daily and after every deploy, holds it on its date with simulated attendees (scripts/hold-quarterly-review.py), reading the frozen report whose sha256 the verified issue index records, and publishes /.well-known/quarterly-review-<date>.json and .md (signed, never rewritten) and the index quarterly-reviews.json. The maintainer (called by every deploy) and the evidence nightly fail when a review date has passed with no review published (scripts/check-quarterly-review.py). The schedule is the published calendar file and appears in the OCR and CPO.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_review_is_five_business_days_after_issue_skipping_thanksgiving" + }, + { + "kind": "test", + "ref": "tests/test_quarterly_review.py::test_the_maintainer_holds_a_due_review_and_indexes_it" + }, + { + "kind": "test", + "ref": "tests/test_quarterly_review.py::test_known_bad_a_passed_review_date_with_no_review_fails_the_check" + }, + { + "kind": "step", + "ref": "package-maintenance.yml#Hold the Quarterly Review when due (simulated attendees)" + }, + { + "kind": "step", + "ref": "package-maintenance.yml#No Quarterly Review overdue (published index)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#No Quarterly Review overdue" + }, + { + "kind": "artifact", + "ref": ".well-known/quarterly-reviews.json" + }, + { + "kind": "artifact", + "ref": ".well-known/quarterly-review.ics" + }, + { + "kind": "decision", + "ref": "DEC-194" + } + ], + "simulated": { + "counterparty": "personnel", + "how": "No real party attends (DEC-194). On each review date package-maintenance.yml holds the review with a simulated roster (Department of Hypothetical Affairs (simulated), Bureau of Made-Up Statistics (simulated), FedRAMP (simulated), Totally Real Assessment Services, LLC (simulated)), hosted by the workflow itself, and publishes the result; nothing is sent to anyone." + } + }, + { + "frr_id": "CCM-QTR-NID", + "status": "Implemented", + "implementation": "Everything a Quarterly Review shows is generated: the agenda from the issued report (which passed the OCR's sensitivity screen), the scripted transcript and the screened Q&A. The whole review document passes the same sensitivity screen (scripts/_sensitivity.py) before it is written, and the build fails on a hit.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_sensitivity_screen_catches_each_kind" + }, + { + "kind": "test", + "ref": "tests/test_quarterly_review.py::test_the_review_passes_the_sensitivity_screen" + }, + { + "kind": "step", + "ref": "package-maintenance.yml#Hold the Quarterly Review when due (simulated attendees)" + }, + { + "kind": "artifact", + "ref": ".well-known/quarterly-reviews.json" + }, + { + "kind": "decision", + "ref": "DEC-194" + } + ], + "simulated": { + "counterparty": "personnel", + "how": "No real party attends (DEC-194). On each review date package-maintenance.yml holds the review with a simulated roster (Department of Hypothetical Affairs (simulated), Bureau of Made-Up Statistics (simulated), FedRAMP (simulated), Totally Real Assessment Services, LLC (simulated)), hosted by the workflow itself, and publishes the result; nothing is sent to anyone." + } + }, + { + "frr_id": "CCM-QTR-NRD", + "status": "Implemented", + "implementation": "The next Quarterly Review date is the latest issue's review date from the CCM calendar (issue + 5 business days, holiday-aware), stable between issues, published in the OCR, the CPO and the calendar file.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_next_dates_hold_steady_between_issues_and_move_on_the_issue_date" + }, + { + "kind": "artifact", + "ref": ".well-known/certification-package-overview.json" + }, + { + "kind": "artifact", + "ref": ".well-known/quarterly-review.ics" + } + ] + }, + { + "frr_id": "CCM-QTR-REG", + "status": "Implemented", + "implementation": "/.well-known/quarterly-review.ics (RFC 5545, one event per review) is built from the CCM calendar on every deploy and maintenance run; each event carries the meeting information and links the report and the review as published once held. The simulated attendees take their meeting information from it; it invites no real party and says so (DEC-194).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_review_calendar_file_is_rfc5545" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build CDS certification-data artifacts (availability, policy index, review calendar)" + }, + { + "kind": "artifact", + "ref": ".well-known/quarterly-review.ics" + }, + { + "kind": "decision", + "ref": "DEC-194" + } + ], + "simulated": { + "counterparty": "personnel", + "how": "No real party attends (DEC-194). On each review date package-maintenance.yml holds the review with a simulated roster (Department of Hypothetical Affairs (simulated), Bureau of Made-Up Statistics (simulated), FedRAMP (simulated), Totally Real Assessment Services, LLC (simulated)), hosted by the workflow itself, and publishes the result; nothing is sent to anyone." + } + }, + { + "frr_id": "CCM-QTR-RTP", + "status": "Implemented", + "implementation": "The attendee policy is enforced in code (scripts/_quarterly_review.py, check_roster): simulated agencies, the simulated FedRAMP and the simulated assessor attend by default; any other attendee needs its specific relevance recorded, and every attendee must be marked simulated, or the review is not held.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_quarterly_review.py::test_known_bad_the_attendee_policy_is_enforced_in_code" + }, + { + "kind": "step", + "ref": "package-maintenance.yml#Hold the Quarterly Review when due (simulated attendees)" + }, + { + "kind": "artifact", + "ref": ".well-known/quarterly-reviews.json" + }, + { + "kind": "decision", + "ref": "DEC-194" + } + ], + "simulated": { + "counterparty": "personnel", + "how": "No real party attends (DEC-194). On each review date package-maintenance.yml holds the review with a simulated roster (Department of Hypothetical Affairs (simulated), Bureau of Made-Up Statistics (simulated), FedRAMP (simulated), Totally Real Assessment Services, LLC (simulated)), hosted by the workflow itself, and publishes the result; nothing is sent to anyone." + } + }, + { + "frr_id": "CCM-QTR-RTR", + "status": "Implemented", + "implementation": "Each Quarterly Review is transcribed (a scripted transcript) and supplied to every attendee, all simulated, as a log entry: the review records the sha256 of the full transcript and the attendees it is supplied to. Nothing is sent to anyone (DEC-194).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_quarterly_review.py::test_the_published_transcript_removes_every_agency_comment_and_name" + }, + { + "kind": "step", + "ref": "package-maintenance.yml#Hold the Quarterly Review when due (simulated attendees)" + }, + { + "kind": "artifact", + "ref": ".well-known/quarterly-reviews.json" + }, + { + "kind": "decision", + "ref": "DEC-194" + } + ], + "simulated": { + "counterparty": "personnel", + "how": "No real party attends (DEC-194). On each review date package-maintenance.yml holds the review with a simulated roster (Department of Hypothetical Affairs (simulated), Bureau of Made-Up Statistics (simulated), FedRAMP (simulated), Totally Real Assessment Services, LLC (simulated)), hosted by the workflow itself, and publishes the result; nothing is sent to anyone." + } + }, + { + "frr_id": "CCM-QTR-SAR", + "status": "Implemented", + "implementation": "Each review is scheduled 5 business days after its OCR issue, counting only weekdays that are not federal holidays; the calendar rejects an offset outside 3 to 10 business days.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_review_is_five_business_days_after_issue_skipping_thanksgiving" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_a_bad_calendar_fails_closed" + }, + { + "kind": "artifact", + "ref": ".well-known/quarterly-review.ics" + } + ] + }, + { + "frr_id": "CCM-QTR-SCR", + "status": "Implemented", + "implementation": "Exercised: the content prepared for each review (its agenda and the report it reviews) is published with the OCR after the no-adverse-effect determination (DEC-101).", + "evidence": [ + { + "kind": "decision", + "ref": "DEC-101" + }, + { + "kind": "artifact", + "ref": ".well-known/ongoing-certification-report.json" + } + ], + "may_rationale": "Exercised: content prepared for each Quarterly Review is published with that quarter's OCR, for the same reason the OCR is public, after the same no-adverse-effect check (DEC-101)." + }, + { + "frr_id": "CCM-QTR-SRR", + "status": "Implemented", + "implementation": "Exercised: each review's transcript is published with every agency comment, question and name removed (scripts/_quarterly_review.py, public_transcript and public_roster), after the sensitivity screen.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_quarterly_review.py::test_the_published_transcript_removes_every_agency_comment_and_name" + }, + { + "kind": "step", + "ref": "package-maintenance.yml#Hold the Quarterly Review when due (simulated attendees)" + }, + { + "kind": "artifact", + "ref": ".well-known/quarterly-reviews.json" + }, + { + "kind": "decision", + "ref": "DEC-194" + } + ], + "may_rationale": "Exercised: each review's transcript is published after all agency comments, questions and names are removed, so the review is as open as the rest of the package.", + "simulated": { + "counterparty": "personnel", + "how": "No real party attends (DEC-194). On each review date package-maintenance.yml holds the review with a simulated roster (Department of Hypothetical Affairs (simulated), Bureau of Made-Up Statistics (simulated), FedRAMP (simulated), Totally Real Assessment Services, LLC (simulated)), hosted by the workflow itself, and publishes the result; nothing is sent to anyone." + } + }, + { + "frr_id": "CDS-CSO-AVR", + "status": "Implemented", + "implementation": "An availability monitor on GitHub Actions, independent of AWS (.github/workflows/availability-probe.yml, scripts/availability-probe.py), probes the website, the trust center, the certification data under /.well-known/, the Silk Reeling application and its Cognito sign-in every 15 minutes, keeps 35 days of history, and derives availability incidents (two or more consecutive failed probes of a service: start, end, failing check). It publishes JSON and a human-readable page to the repository's availability-status branch, served by GitHub, so the status stays readable when the offering is down; an ongoing incident fails the run, which notifies the operator. The deploy fails when that feed is missing or more than 2 hours old, and republishes it signed as /.well-known/availability.json with a Markdown twin (scripts/build-availability.py), which no longer records deploys as availability. History begins at the monitor's first run.", + "evidence": [ + { + "kind": "step", + "ref": "availability-probe.yml#Probe the core services" + }, + { + "kind": "step", + "ref": "availability-probe.yml#Publish the status feed to the availability-status branch" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Read the independent availability feed (fails when missing or stale)" + }, + { + "kind": "artifact", + "ref": ".well-known/availability.json" + }, + { + "kind": "test", + "ref": "tests/test_availability_probe.py::test_consecutive_failures_make_an_incident_and_a_single_one_is_transient" + }, + { + "kind": "test", + "ref": "tests/test_availability_probe.py::test_the_known_bad_stale_feed_fails_the_deploy_guard" + }, + { + "kind": "test", + "ref": "tests/test_availability_probe.py::test_the_monitor_runs_outside_aws_on_a_schedule_and_pushes_only_its_branch" + } + ] + }, + { + "frr_id": "CDS-CSO-CBF", + "status": "Implemented", + "implementation": "Every JSON and CSV file any workflow publishes under /.well-known/ gets a complete human-readable view, <name>.view.md, beside it, giving every value under its JSON Pointer path (scripts/build-human-views.py): the deploy for everything it publishes (the freshness-config list, every incident report, the inventory's JSON Schema and every certification report), the evidence nightly for the VDR files, the package maintainer for the package it rewrites and every issued report, snapshot and Quarterly Review, and the incident publisher for the incident logs and every report. Each build parses each view back and fails unless it reproduces the JSON exactly, before anything is signed or published, and each workflow's redaction gate scans the views it puts. tests/test_human_views_published.py runs each workflow's view, gate and publish steps and fails if any JSON or CSV is put without its view. The curated .md summaries are written from the same in-memory data in the same run. The policies are published as the Markdown documents themselves, indexed by the machine-readable policy index.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_human_views_published.py::test_every_json_a_publisher_puts_has_its_view_put_too" + }, + { + "kind": "test", + "ref": "tests/test_human_views_published.py::test_known_bad_a_publish_step_without_views_fails" + }, + { + "kind": "test", + "ref": "tests/test_trust_data.py::test_a_view_reproduces_its_json_exactly" + }, + { + "kind": "test", + "ref": "tests/test_trust_data.py::test_known_bad_a_view_that_differs_from_its_json_fails" + }, + { + "kind": "test", + "ref": "tests/test_trust_data.py::test_a_json_the_view_cannot_represent_fails_closed" + }, + { + "kind": "test", + "ref": "tests/test_trust_data.py::test_views_cover_every_deploy_published_json_in_the_governed_list" + }, + { + "kind": "test", + "ref": "tests/test_trust_data.py::test_the_nightly_rebuilds_the_views_of_what_it_republishes" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build the human-readable views and the trust manifest (format parity)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Rebuild the human-readable views (format parity)" + }, + { + "kind": "artifact", + "ref": ".well-known/trust-manifest.json" + } + ] + }, + { + "frr_id": "CDS-CSO-FID", + "status": "Implemented", + "implementation": "data/cds/offering.json is the one source of the FedRAMP ID (scripts/_offering.py). No ID is assigned, so it is FedRAMP's fallback, the provider name and acronym, suffixed so it cannot be mistaken for a real one, and flagged simulated (DEC-100). Every builder that publishes certification data stamps it through scripts/_offering.stamp_fedramp_id: under providerExtensions.fedRampId in reports in a FedRAMP schema (the SDR, OCR and issued OCRs; the VDT, AVI and vulnerability history; each Significant Change Notification; each Initial, Ongoing and Final incident report), in serviceIdentification.fedRampPackageId in the CPO, and as a top-level fedRampId in every other published JSON file (the VDR report, trend, monthly report and non-machine V&V status; the KSI signal, which the runtime emitter copies into the runtime signal; the SCN index and evaluation log; the incident log and simulated delivery log; the simulated inbox run; the trust center, manifest, scope, configuration, boundary, reconciliation, conformance, access, assessor and agency files; the issue index, snapshots, FedRAMP Certification Reports index and package submission log). The SCN Atom feed carries it in its subtitle. The gate scripts/check-fedramp-id.py fails the run when a file it is given lacks the ID or carries another: the deploy runs it over its REPORTS list before anything is published, and the nightly, the incident publisher and the package maintainer run it over what each republishes. A test holds every freshness-governed JSON artifact to be in REPORTS or listed in the gate's EXEMPT map with its reason: the runtime signal (written by the Lambda, copied from the checked KSI signal), the nightly's status beacon (stamped where it is written), the issue index (checked by the package maintainer) and the independent boundary corroboration (another party's record, published unmodified).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_fedramp_id_and_uei_are_the_offerings_and_flagged_simulated" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_gate_fails_a_report_with_another_fedramp_id" + }, + { + "kind": "test", + "ref": "tests/test_sdr_ksi_metrics.py::test_the_sdr_carries_the_offerings_fedramp_id" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#FedRAMP ID in every FedRAMP report (CDS-CSO-FID)" + }, + { + "kind": "decision", + "ref": "DEC-100" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_id_trust.py::test_known_bad_a_site_file_without_a_fedramp_id_fails" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_id_coverage.py::test_every_governed_json_artifact_is_checked_or_exempt_with_a_reason" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_id_coverage.py::test_known_bad_an_unlisted_artifact_and_an_unexplained_exemption_fail" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_id_coverage.py::test_known_bad_a_fedramp_schema_report_without_the_id_fails" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_id_coverage.py::test_scn_notifications_index_log_and_feed_carry_it" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_id_coverage.py::test_incident_log_reports_and_deliveries_carry_it" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_id_coverage.py::test_the_nightly_and_the_incident_publisher_run_the_gate_on_what_they_publish" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#FedRAMP ID in every republished report (CDS-CSO-FID)" + }, + { + "kind": "step", + "ref": "incident-reports.yml#FedRAMP ID in every incident report (CDS-CSO-FID)" + } + ] + }, + { + "frr_id": "CDS-CSO-FRC", + "status": "Implemented", + "implementation": "FedRAMP is simulated, and the system is not certified. The simulated FedRAMP issues a stand-in certification report only in response to a simulated package submission (scripts/submit-package.py): for the first submission, then after any adaptive or transformative Significant Change Notification no earlier report covered, and once a year; an ordinary deploy issues none. Each report is logged verbatim, with the date received and its sha256, in its submission's entry of the append-only /.well-known/package-submission-log.json. On every deploy scripts/publish-certification-reports.py publishes every logged report byte-identical under /.well-known/fedramp-certification-reports/ (an edited report fails the deploy), keeps each report's first publication date from the previously published index, and fails the deploy if a report would be first published more than 2 weeks after receipt. The previous log and index are fetched fail-closed: anything but a 404 fails the deploy rather than restarting either history. Every report's title and first line say it is a simulated report NOT ISSUED BY FEDRAMP and that the system is not certified, and one that does not is never published; the CPO and the SDR both state providerExtensions.certification.status 'not certified (proof of concept)', from one source (scripts/_offering.py), and a package without it is never submitted.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_first_submission_gets_a_simulated_report_and_ordinary_deploys_do_not" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_an_adaptive_or_transformative_scn_brings_a_new_report" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_a_report_is_issued_annually_even_when_the_package_is_unchanged" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_logged_reports_are_published_byte_identical_and_their_first_date_kept" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_known_bad_a_report_published_more_than_two_weeks_after_receipt_fails_the_deploy" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_known_bad_a_modified_or_unlabelled_report_is_never_published" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_report_says_first_that_it_is_simulated_not_issued_by_fedramp_and_not_certified" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_cpo_json_says_the_system_is_not_certified" + }, + { + "kind": "test", + "ref": "tests/test_sdr.py::test_the_sdr_json_says_the_system_is_not_certified_like_the_cpo" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_known_bad_a_cpo_or_sdr_without_the_not_certified_status_is_never_submitted" + }, + { + "kind": "test", + "ref": "tests/test_published_history.py::test_known_bad_a_failed_or_truncated_fetch_fails_and_keeps_nothing" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Simulated package submission to FedRAMP (nothing is sent)" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#FedRAMP Certification Reports published unmodified (simulated FedRAMP)" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Publish FedRAMP Certification Reports byte-identical" + }, + { + "kind": "artifact", + "ref": ".well-known/fedramp-certification-reports.json" + }, + { + "kind": "artifact", + "ref": ".well-known/package-submission-log.json" + } + ], + "simulated": { + "counterparty": "fedramp", + "how": "No FedRAMP counterpart exists. A Python function in scripts/submit-package.py stands in for FedRAMP and writes each report in response to a simulated package submission; every report says in its title and first line that it is NOT ISSUED BY FEDRAMP and that the system is not certified. Nothing is sent to or received from FedRAMP (DEC-194)." + } + }, + { + "frr_id": "CDS-CSO-HAD", + "status": "Implemented", + "implementation": "On each OCR issue date the maintainer snapshots the certification data as published (with signatures) to /.well-known/snapshots/<date>/ and writes a signed manifest of sha256s, listed in /.well-known/ocr-issues.json with an explanation of access; an issue fails if the core files are missing. The publishing role cannot delete, issued files are never overwritten, and the website sync excludes /.well-known/, so snapshots stay for the duration of certification.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_first_run_on_an_issue_date_freezes_the_report_and_snapshots_the_package" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_no_issue_without_the_certification_data_to_snapshot" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_a_tampered_issue_index_fails" + }, + { + "kind": "step", + "ref": "package-maintenance.yml#Issue the quarterly report when due (frozen, with a snapshot)" + }, + { + "kind": "artifact", + "ref": ".well-known/ocr-issues.json" + } + ] + }, + { + "frr_id": "CDS-CSO-IRP", + "status": "Implemented", + "implementation": "policy-index.json and policy-index.md under /.well-known/ (scripts/build-policy-index.py) list every policy (docs/policies) and procedure (docs/procedures, docs/runbooks, the verification and deploy procedures) with its name, file and URL, summary, word count, version (git:<commit>) and date of last update from its own last commit (a shallow checkout is refused), and related FedRAMP practices as concrete rule and KSI IDs from the pinned corpus and KSI catalog (a mapping that matches nothing fails the build). The documents themselves are published beside the index under /.well-known/policies/, and the index states how to access them.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_policy_index.py::test_every_entry_has_the_seven_fields_and_a_url" + }, + { + "kind": "test", + "ref": "tests/test_policy_index.py::test_procedures_are_indexed_beside_policies" + }, + { + "kind": "test", + "ref": "tests/test_policy_index.py::test_related_practices_are_real_rule_and_ksi_ids" + }, + { + "kind": "test", + "ref": "tests/test_policy_index.py::test_a_practice_prefix_that_matches_nothing_fails" + }, + { + "kind": "test", + "ref": "tests/test_policy_index.py::test_the_markdown_carries_every_field_of_every_entry" + }, + { + "kind": "test", + "ref": "tests/test_policy_index.py::test_the_deploy_publishes_the_documents" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build CDS certification-data artifacts (availability, policy index, review calendar)" + }, + { + "kind": "artifact", + "ref": ".well-known/policy-index.json" + } + ] + }, + { + "frr_id": "CDS-CSO-PSM", + "status": "Not Applicable", + "implementation": "Permissive (MAY). Checked: no per-service materials are supplied; nothing in the rule requires them.", + "evidence": [], + "not_applicable": "A MAY permission that is not exercised; see the rationale.", + "may_rationale": "Not exercised. The two services (the website and Silk Reeling) share one boundary, one inventory and one pipeline; separate per-service packages would repeat the same evidence." + }, + { + "frr_id": "CDS-CSO-PUB", + "status": "Implemented", + "implementation": "The CPO (JSON and Markdown, public under /.well-known/) publishes every listed item that applies: the FedRAMP ID (FedRAMP's fallback, flagged simulated), service and deployment model, business categories, a UEI (simulated, flagged sam-gov: no SAM.gov registration), sales and security contacts (the contact page and security.txt; no email address), the product website, the logo, the description, each service with its security category, the secure configuration guidance link, the documentation overview, the trust center landing page (https://samaydlette.com/trust/index.html) with access instructions, the next OCR date from the fixed calendar, and the current independent assessment service: none FedRAMP Recognized, stated as such, with the simulated assessor named. It is rebuilt on every deploy and daily by the package maintainer.", + "evidence": [ + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build Certification Package Overview (CPO)" + }, + { + "kind": "step", + "ref": "package-maintenance.yml#Rebuild the SDR, OCR and CPO at the deployed commit" + }, + { + "kind": "artifact", + "ref": ".well-known/certification-package-overview.json" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_cpo_publishes_the_fixed_cycle_dates" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_fedramp_id_and_uei_are_the_offerings_and_flagged_simulated" + }, + { + "kind": "test", + "ref": "tests/test_cpo_trust_fields.py::test_the_trust_center_entry_is_the_landing_page_with_access_instructions" + }, + { + "kind": "test", + "ref": "tests/test_cpo_trust_fields.py::test_the_secure_configuration_guidance_links_the_published_guide" + } + ], + "simulated": { + "counterparty": "sam-gov", + "how": "No SAM.gov registration exists, so the UEI is a plainly fake placeholder from data/cds/offering.json, flagged under providerExtensions.simulated in the published CPO. Nothing is registered or sent; every other item is real." + } + }, + { + "frr_id": "CDS-CSO-RIS", + "status": "Implemented", + "implementation": "Sufficiency: the package carries the SDR with every applicable rule and KSI and the simulated assessor's independent results, the CPO, the boundary map, inventory, vulnerability reports and the policies, indexed in the signed trust manifest. Sensitivity: the information sharing and disclosure standard (docs/procedures/information-sharing.md, DEC-166) says what is never published (account IDs, secrets, personal email addresses, IAM user names, raw logs, requester identities), what is published on purpose and why that is not likely to enable an attacker. The publication redaction gate fails the deploy on an AWS account ID in anything published, including the views and the policy documents.", + "evidence": [ + { + "kind": "decision", + "ref": "DEC-166" + }, + { + "kind": "test", + "ref": "tests/test_published_redaction.py::test_gate_fails_the_known_bad_fixture_without_printing_the_number" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Publication redaction gate (no AWS account ID)" + }, + { + "kind": "artifact", + "ref": ".well-known/trust-manifest.json" + } + ] + }, + { + "frr_id": "CDS-CSO-RPS", + "status": "Implemented", + "implementation": "The whole package is public. The information sharing and disclosure standard (docs/procedures/information-sharing.md, published under /.well-known/policies/) explains what is shared, with whom (everyone, by HTTPS GET), and records the operator's determination (DEC-166) that public sharing will not likely have an adverse effect on the offering. The trust page links it.", + "evidence": [ + { + "kind": "decision", + "ref": "DEC-166" + }, + { + "kind": "test", + "ref": "tests/test_trust_data.py::test_the_trust_page_indexes_the_data_and_says_how_to_get_access" + }, + { + "kind": "artifact", + "ref": ".well-known/policy-index.json" + } + ], + "may_rationale": "Exercised. The whole package is public: the system demonstrates 20x openly and holds no federal customer data. The determination that public sharing will not likely harm the offering is DEC-166, published with the sharing statement." + }, + { + "frr_id": "CDS-CSO-SVC", + "status": "Implemented", + "implementation": "The CPO lists each service (certifiedServices) with its own FIPS 199 category, high-water mark and rationale, and the boundary groups it is made of (providerExtensions.services), plus an explicit list of what is not included (providerExtensions.notIncluded); its Markdown rendering shows the same table. The builder fails when a service's category exceeds the system's or names a boundary group that is not in the boundary classification.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_each_service_has_its_own_category_and_the_list_says_what_is_not_included" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_a_bad_service_list_fails" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build Certification Package Overview (CPO)" + }, + { + "kind": "artifact", + "ref": ".well-known/certification-package-overview.json" + } + ] + }, + { + "frr_id": "CDS-CSO-UTC", + "status": "Implemented", + "implementation": "The trust center is https://samaydlette.com/trust/index.html with the certification data under /.well-known/. It is the single definitive source: the signed trust manifest (trust-manifest.json, generated from the governed artifact list on every deploy) lists every artifact with URL, media type, cadence, signature and signer and its human-readable forms, plus every policy and procedure, served from the same site. It meets the trust-center rules recorded here: agency access inventory (CDS-TRC-AAI), access logging with summaries (CDS-TRC-ACL), human-readable and machine-readable formats (CDS-TRC-HMR), documented programmatic access (CDS-TRC-PAC), self-service access (CDS-TRC-SSM) and uptime reported from outside AWS (CDS-TRC-USH).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_trust_data.py::test_the_manifest_lists_every_governed_artifact_with_its_signature" + }, + { + "kind": "test", + "ref": "tests/test_trust_data.py::test_the_trust_page_indexes_the_data_and_says_how_to_get_access" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build the human-readable views and the trust manifest (format parity)" + }, + { + "kind": "artifact", + "ref": ".well-known/trust-manifest.json" + }, + { + "kind": "artifact", + "ref": ".well-known/trust-center.json" + } + ] + }, + { + "frr_id": "CDS-TRC-AAI", + "status": "Implemented", + "implementation": "data/agency-access.json is the append-only register of agency access requests, grants, denials and withdrawals, naming agencies and systems, never people (a record with an email address fails). scripts/agency-access.py derives the inventory and the full history from it; every deploy validates it and fails on an overdue denial notice or on any entry not marked simulated for an agency named '(simulated)' (DEC-194). It is empty. The inventory and history are exercised on every deploy over the simulated scenario, whose inventory request from the simulated FedRAMP is answered in the published log (procedure: docs/procedures/agency-access.md, DEC-165).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_agency_access.py::test_inventory_and_history_follow_grants_and_withdrawals" + }, + { + "kind": "test", + "ref": "tests/test_agency_access.py::test_known_bad_the_register_never_names_a_person" + }, + { + "kind": "test", + "ref": "tests/test_agency_access.py::test_known_bad_a_register_entry_not_marked_simulated_fails" + }, + { + "kind": "test", + "ref": "tests/test_agency_access.py::test_the_committed_register_is_valid_and_has_nothing_overdue" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Agency access register check and simulated-agency exercise" + }, + { + "kind": "artifact", + "ref": ".well-known/agency-access-exercise.json" + }, + { + "kind": "decision", + "ref": "DEC-165" + } + ], + "simulated": { + "counterparty": "agency", + "how": "No real agency request is taken (DEC-194). Every deploy runs the access procedure against plainly fictional agencies (data/agency-access-exercise.json: 'Department of Hypothetical Affairs (simulated)' and others): code rules decide each request, the automated notifier writes each denial notice to the simulated FedRAMP after a simulated delay or outage, and the deploy fails unless the 5-business-day clock (weekends and US federal holidays skipped) reports every outcome expected, including a late and an overdue notice. Nothing is sent to anyone; the log is published as agency-access-exercise.json." + } + }, + { + "frr_id": "CDS-TRC-ACL", + "status": "Implemented", + "implementation": "CloudFront standard logging (v2) records every request to the site with a field allowlist that excludes IP address, forwarded-for, port, cookies, query string, user agent and referrer (infrastructure/bootstrap/trust-access-logs.tf). Records go to the encrypted, non-public access-log bucket and expire after 90 days (infrastructure/logging.tf). On every deploy, scripts/check-edge-access-logging.py fails the deploy unless that delivery exists and logs only allowlisted fields, and scripts/build-access-summary.py counts the requests to /.well-known/ and /trust/ (CloudFront cannot limit logging by path, so the limit is applied here and every other record is discarded) into monthly summaries per artifact, response class and country, published signed at /.well-known/access-summary.json with a Markdown twin and carried forward for 13 months. The lookup of a party's own records, by the times and paths it gives (no requester identity is logged), is built into scripts/build-access-summary.py and exercised on every deploy against a simulated requester: it must find exactly the known answer in fixed synthetic records or the deploy fails, and the count it finds in the real records is logged in the summary (ownRecordsExercise). Nothing is delivered and no real request is answered (DEC-160, DEC-194); the trust page's privacy notice says so.", + "evidence": [ + { + "kind": "step", + "ref": "deploy-with-opa.yml#Check edge access logging and build the access summary" + }, + { + "kind": "artifact", + "ref": ".well-known/access-summary.json" + }, + { + "kind": "test", + "ref": "tests/test_edge_access_logging.py::test_the_known_bad_fixture_fails_for_identifying_fields" + }, + { + "kind": "test", + "ref": "tests/test_edge_access_logging.py::test_only_trust_paths_are_counted_and_nothing_identifying_survives" + }, + { + "kind": "test", + "ref": "tests/test_edge_access_logging.py::test_a_month_younger_than_six_is_never_dropped" + }, + { + "kind": "test", + "ref": "tests/test_edge_access_logging.py::test_raw_edge_records_expire_after_90_days" + }, + { + "kind": "decision", + "ref": "DEC-160" + }, + { + "kind": "test", + "ref": "tests/test_edge_access_logging.py::test_every_build_exercises_the_lookup_and_delivers_nothing" + }, + { + "kind": "test", + "ref": "tests/test_edge_access_logging.py::test_known_bad_a_lookup_that_misses_fails_the_build" + } + ], + "simulated": { + "counterparty": "personnel", + "how": "The requester is simulated ('A. Reader (simulated)'); its request runs through the real lookup on every deploy and the result is a log entry in access-summary.json. No real request is answered (DEC-194)." + } + }, + { + "frr_id": "CDS-TRC-HMR", + "status": "Implemented", + "implementation": "Every JSON and CSV file any workflow publishes has a complete human-readable view (.view.md, checked to reproduce the JSON, published by the same workflows that publish the file), most have a curated .md summary, and the policies and procedures are published as Markdown. The trust manifest lists both formats for each artifact, the view from the publisher table in scripts/_signers.py (so a file only the package maintainer writes lists its view too), and fails the build if a JSON built without its view and the trust page links the manifest; everything can be viewed in a browser and downloaded with a GET. The runtime signal and the nightly beacon, published outside the deploy, are rendered human-readably by the trust page from the live JSON.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_human_views_published.py::test_the_manifest_lists_the_view_of_every_json_another_workflow_publishes" + }, + { + "kind": "test", + "ref": "tests/test_human_views_published.py::test_every_json_a_publisher_puts_has_its_view_put_too" + }, + { + "kind": "test", + "ref": "tests/test_human_views_published.py::test_known_bad_a_publish_step_without_views_fails" + }, + { + "kind": "test", + "ref": "tests/test_trust_data.py::test_a_view_reproduces_its_json_exactly" + }, + { + "kind": "test", + "ref": "tests/test_trust_data.py::test_the_manifest_names_only_human_views_that_exist" + }, + { + "kind": "test", + "ref": "tests/test_trust_data.py::test_views_cover_every_deploy_published_json_in_the_governed_list" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build the human-readable views and the trust manifest (format parity)" + }, + { + "kind": "artifact", + "ref": ".well-known/trust-manifest.json" + } + ] + }, + { + "frr_id": "CDS-TRC-PAC", + "status": "Implemented", + "implementation": "The signed trust manifest (/.well-known/trust-manifest.json and .md) is the documented programmatic index of all certification data: each artifact's URL, media type, cadence, schema, signature bundle and signing identity, its human-readable forms, every policy and procedure (Markdown under /.well-known/policies/), and how to fetch and verify (HTTPS GET with read-only CORS; cosign verify-blob against the named identity). The assessor guide gives the command for each piece of evidence.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_trust_data.py::test_the_manifest_lists_every_governed_artifact_with_its_signature" + }, + { + "kind": "test", + "ref": "tests/test_trust_data.py::test_the_manifest_names_only_human_views_that_exist" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build the human-readable views and the trust manifest (format parity)" + }, + { + "kind": "artifact", + "ref": ".well-known/trust-manifest.json" + }, + { + "kind": "artifact", + "ref": ".well-known/assessor-guide.json" + } + ] + }, + { + "frr_id": "CDS-TRC-SSM", + "status": "Implemented", + "implementation": "Parties provision their own access directly: all data is public, so a user or service needs no account or key (the trust manifest documents how to fetch and verify). Requests and withdrawals are processed without a person: scripts/agency-access.py decides each request by fixed rules and records it; the trust page's Access section says so (docs/procedures/agency-access.md, DEC-165). No real agency request is taken (DEC-194).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_trust_data.py::test_the_trust_page_indexes_the_data_and_says_how_to_get_access" + }, + { + "kind": "test", + "ref": "tests/test_agency_access.py::test_code_rules_decide_each_request" + }, + { + "kind": "test", + "ref": "tests/test_agency_access.py::test_inventory_and_history_follow_grants_and_withdrawals" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Agency access register check and simulated-agency exercise" + }, + { + "kind": "artifact", + "ref": ".well-known/agency-access-exercise.json" + }, + { + "kind": "decision", + "ref": "DEC-165" + } + ], + "simulated": { + "counterparty": "agency", + "how": "No real agency request is taken (DEC-194). Every deploy runs the access procedure against plainly fictional agencies (data/agency-access-exercise.json: 'Department of Hypothetical Affairs (simulated)' and others): code rules decide each request, the automated notifier writes each denial notice to the simulated FedRAMP after a simulated delay or outage, and the deploy fails unless the 5-business-day clock (weekends and US federal holidays skipped) reports every outcome expected, including a late and an overdue notice. Nothing is sent to anyone; the log is published as agency-access-exercise.json." + } + }, + { + "frr_id": "CDS-TRC-USH", + "status": "Implemented", + "implementation": "The certification data is static, signed files under /.well-known/ served from the CloudFront edge (cached, with AWS Shield Standard), readable as plain JSON and Markdown without JavaScript and, since the deploy checks it, with CORS for programs on any origin. Interruptions are measured from outside AWS every 15 minutes, and an ongoing one fails the monitor's run, which notifies the operator (CDS-CSO-AVR); the status itself is served by GitHub, so it stays available during an outage. The single origin without failover is an accepted risk (DEC-009).", + "evidence": [ + { + "kind": "step", + "ref": "availability-probe.yml#Alert on an ongoing availability incident" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Read the independent availability feed (fails when missing or stale)" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Check /.well-known/ JSON response headers (CORS, Content-Type, nosniff)" + }, + { + "kind": "artifact", + "ref": ".well-known/availability.json" + }, + { + "kind": "test", + "ref": "tests/test_availability_probe.py::test_an_ongoing_incident_fails_the_monitor_run_after_publishing" + }, + { + "kind": "decision", + "ref": "DEC-009" + } + ] + }, + { + "frr_id": "CDS-UTC-AAD", + "status": "Implemented", + "implementation": "When a request is denied (by rule), the automated notifier writes a notice to the simulated FedRAMP as a log entry, and the clock requires it within 5 business days of the denial (docs/procedures/agency-access.md, DEC-165). scripts/agency-access.py computes each deadline (weekends and US federal holidays skipped) and every deploy fails when a notice is late or overdue. The clock and the notifier, with a simulated outage, are exercised on every deploy.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_agency_access.py::test_business_days_skip_weekends_and_federal_holidays" + }, + { + "kind": "test", + "ref": "tests/test_agency_access.py::test_known_bad_an_unnotified_denial_past_five_business_days_fails" + }, + { + "kind": "test", + "ref": "tests/test_agency_access.py::test_the_notifier_outage_leaves_a_denial_overdue_and_a_slow_queue_late" + }, + { + "kind": "test", + "ref": "tests/test_agency_access.py::test_the_exercise_observes_every_expected_outcome_on_any_day" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Agency access register check and simulated-agency exercise" + }, + { + "kind": "artifact", + "ref": ".well-known/agency-access-exercise.json" + }, + { + "kind": "decision", + "ref": "DEC-165" + } + ], + "simulated": { + "counterparty": "agency", + "how": "No real agency request is taken (DEC-194). Every deploy runs the access procedure against plainly fictional agencies (data/agency-access-exercise.json: 'Department of Hypothetical Affairs (simulated)' and others): code rules decide each request, the automated notifier writes each denial notice to the simulated FedRAMP after a simulated delay or outage, and the deploy fails unless the 5-business-day clock (weekends and US federal holidays skipped) reports every outcome expected, including a late and an overdue notice. Nothing is sent to anyone; the log is published as agency-access-exercise.json." + } + }, + { + "frr_id": "CDS-UTC-AGA", + "status": "Implemented", + "implementation": "Agencies get the whole package without asking, since it is public. Access requests are decided by fixed rules in scripts/agency-access.py (granted unless they ask for write access, delivery other than HTTPS, data beyond the public package, or come from an agency that cannot be verified); the trust page's Access section says what is provided and links the procedure (DEC-165) and the sharing standard that explains how sharing is decided (DEC-166). No real agency request is taken (DEC-194).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_trust_data.py::test_the_trust_page_indexes_the_data_and_says_how_to_get_access" + }, + { + "kind": "test", + "ref": "tests/test_agency_access.py::test_code_rules_decide_each_request" + }, + { + "kind": "test", + "ref": "tests/test_agency_access.py::test_the_exercise_writes_a_log_that_says_it_is_simulated" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Agency access register check and simulated-agency exercise" + }, + { + "kind": "artifact", + "ref": ".well-known/agency-access-exercise.json" + }, + { + "kind": "decision", + "ref": "DEC-165" + } + ], + "simulated": { + "counterparty": "agency", + "how": "No real agency request is taken (DEC-194). Every deploy runs the access procedure against plainly fictional agencies (data/agency-access-exercise.json: 'Department of Hypothetical Affairs (simulated)' and others): code rules decide each request, the automated notifier writes each denial notice to the simulated FedRAMP after a simulated delay or outage, and the deploy fails unless the 5-business-day clock (weekends and US federal holidays skipped) reports every outcome expected, including a late and an overdue notice. Nothing is sent to anyone; the log is published as agency-access-exercise.json." + } + }, + { + "frr_id": "CMU-CSO-CAT", + "status": "Implemented", + "implementation": "The app's tenants (Silk Reeling users) get validated cryptography by default where AWS offers it, set in Terraform: the app's Lambda environment and every app log group are encrypted with a customer-managed key on the AWS KMS HSM (CMVP #4884) with rotation on, and viewer and origin TLS are fixed at TLS 1.2 or later. AWS offers no validated-module option for a distribution's viewer TLS, an HTTP API's endpoint or the Cognito Hosted UI (DEC-152). The published module list marks each service's agency-tenant default.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_secure_configuration.py::test_agency_tenant_defaults_use_the_validated_kms_hsm_in_terraform" + }, + { + "kind": "artifact", + "ref": ".well-known/secure-configuration-guide.json" + }, + { + "kind": "decision", + "ref": "DEC-152" + } + ] + }, + { + "frr_id": "CMU-CSO-CMD", + "status": "Implemented", + "implementation": "The Secure Configuration Guide publishes the cryptographic module used by each service (CloudFront and API Gateway TLS, Cognito, KMS, Lambda, CloudWatch Logs, SNS, Secrets Manager, S3, SQS, DynamoDB, CloudTrail, Route 53 DNSSEC, the IAM OIDC provider, Sigstore signing), with the CMVP certificate and its status where AWS publishes one (the AWS KMS HSM, FIPS 140-3 Level 3, certificate #4884, read from NIST's CMVP page) and says plainly where AWS publishes none. The list is generated each deploy from data/crypto-modules.json joined with the inventory; the build fails when the inventory holds a component type with no module mapping.", + "evidence": [ + { + "kind": "artifact", + "ref": ".well-known/secure-configuration-guide.json" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build the secure configuration guide (SCG, cryptographic modules)" + }, + { + "kind": "test", + "ref": "tests/test_secure_configuration.py::test_an_unmapped_component_type_fails_the_build" + }, + { + "kind": "test", + "ref": "tests/test_secure_configuration.py::test_every_validated_module_cites_its_cmvp_certificate_page" + }, + { + "kind": "test", + "ref": "tests/test_secure_configuration.py::test_every_inventory_type_the_builder_knows_is_mapped" + } + ] + }, + { + "frr_id": "CMU-CSO-UVM", + "status": "Implemented", + "implementation": "Where a validated module is available for data the app holds, it is used: the app's Lambda environment and log groups, the alert topic and the signing keys are protected by customer-managed keys on the AWS KMS HSM (CMVP #4884, FIPS 140-3 Level 3). The paths where AWS publishes no CMVP module (viewer TLS on CloudFront, the HTTP API, the Cognito Hosted UI; SSE-S3, SSE-SQS and AWS-owned keys on stores that hold no customer data; the Lambda runtime's outbound TLS) are listed per service and accepted by decision (DEC-152). The system holds no federal customer data.", + "evidence": [ + { + "kind": "artifact", + "ref": ".well-known/secure-configuration-guide.json" + }, + { + "kind": "decision", + "ref": "DEC-152" + }, + { + "kind": "test", + "ref": "tests/test_secure_configuration.py::test_paths_without_a_published_validation_are_covered_by_a_decision" + }, + { + "kind": "test", + "ref": "tests/test_secure_configuration.py::test_agency_tenant_defaults_use_the_validated_kms_hsm_in_terraform" + } + ] + }, + { + "frr_id": "CPO-CSO-MTD", + "status": "Implemented", + "implementation": "The CPO carries metadata.accountableOfficial (name, title, contact), metadata.version (semver: unchanged content keeps its version, changed content bumps it, judged by a sha256 of the content), metadata.lastUpdated and metadata.updateSource.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_cpo_version_is_semver_and_bumps_only_on_change" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_cpo_validates_against_fedramps_schema" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build Certification Package Overview (CPO)" + }, + { + "kind": "artifact", + "ref": ".well-known/certification-package-overview.json" + } + ] + }, + { + "frr_id": "CPO-CSO-OSA", + "status": "Implemented", + "implementation": "The CPO (certification-package-overview.json and .md) carries the assessor's overall summary (IVV-IAS-OSA) under providerExtensions.independentAssessment.overallSummary, quoted verbatim from the signed assessment set: rule and KSI pass, observation and fail counts, failures, areas of dispute and observations. scripts/build-cpo.py requires the set, verifies it (scripts/_assessor.load_assessment) and fails without a summary; the daily package maintainer rebuilds the CPO from the same published set. The schema's `assessor` object is left out because the simulated assessor has no FedRAMP assessor ID, and none is invented.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_cpo_trust_fields.py::test_the_overall_summary_is_the_assessors_record_verbatim" + }, + { + "kind": "test", + "ref": "tests/test_cpo_trust_fields.py::test_known_bad_an_assessment_without_a_summary_fails" + }, + { + "kind": "test", + "ref": "tests/test_cpo_trust_fields.py::test_the_cpo_refuses_to_build_without_the_assessment" + }, + { + "kind": "test", + "ref": "tests/test_cpo_trust_fields.py::test_the_deploy_and_the_maintainer_give_the_cpo_the_assessment" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build Certification Package Overview (CPO)" + }, + { + "kind": "step", + "ref": "package-maintenance.yml#Rebuild the SDR, OCR and CPO at the deployed commit" + }, + { + "kind": "artifact", + "ref": ".well-known/certification-package-overview.json" + }, + { + "kind": "artifact", + "ref": ".well-known/simulated-assessment.json" + } + ], + "simulated": { + "counterparty": "assessor", + "how": "The overall summary is written on every deploy by Totally Real Assessment Services, LLC (simulated), a reusable workflow in this repository (simulated-assessor.yml) that signs its set keylessly under its own pinned workflow identity. build-cpo.py quotes the summary record only after the set's signature verifies against that identity and every record's hash matches, and refuses to build without it. It is not a FedRAMP Recognized assessment service and the CPO says so; only the assessor is simulated." + } + }, + { + "frr_id": "CPO-CSO-OVR", + "status": "Implemented", + "implementation": "scripts/build-cpo.py writes the CPO in FedRAMP's 2026-06-24 schema through write_validated, with JSON and Markdown from the same data, carrying what each listed rule requires: metadata (CPO-CSO-MTD); the public information (CDS-CSO-PUB) including the trust center and secure configuration guidance; each service and its security category (CDS-CSO-SVC); the policy and procedure index (CDS-CSO-IRP), the KSI signal inventory and the Minimum Assessment Scope (MAS-CSO-IIR, MAS-CSO-FLO) as repositories; thirdPartyInformationResources (MAS-CSO-TPR); the cryptographic modules (CMU-CSO-CMD); and the assessment results with the assessor's overall summary (IVV-CSO-ICP, CPO-CSO-OSA). The simulated package submission refuses a CPO missing the trust center, secure configuration guidance, third-party resources or assessor summary.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_cpo_validates_against_fedramps_schema" + }, + { + "kind": "test", + "ref": "tests/test_cpo_trust_fields.py::test_the_cpo_with_group_5_fields_validates_against_fedramps_schema" + }, + { + "kind": "test", + "ref": "tests/test_cpo_trust_fields.py::test_third_party_resources_are_the_decided_records" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_an_incomplete_or_inconsistent_package_is_not_submitted" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build Certification Package Overview (CPO)" + }, + { + "kind": "step", + "ref": "package-maintenance.yml#Rebuild the SDR, OCR and CPO at the deployed commit" + }, + { + "kind": "artifact", + "ref": ".well-known/certification-package-overview.json" + } + ] + }, + { + "frr_id": "CPO-CSX-CPM", + "status": "Implemented", + "implementation": "package-maintenance.yml runs daily, unattended, in its own environment: it fetches the published package and its inputs, verifies their signatures (fail closed), rebuilds the SDR, OCR and CPO at the deployed commit, signs and publishes them with a role that may write only those objects, and checks the edge serves them. Every deploy also runs it. The deploy's preflight fails if the role variable or environment is missing. The SDR, CPO and OCR have 14-day freshness windows (metadata.lastUpdated), alarmed by the evidence watchdog.", + "evidence": [ + { + "kind": "step", + "ref": "package-maintenance.yml#Rebuild the SDR, OCR and CPO at the deployed commit" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Package maintainer preflight" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_maintainer_runs_daily_and_the_package_windows_are_two_weeks_at_most" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_maintainer_preflight_fails_when_not_in_place" + }, + { + "kind": "artifact", + "ref": ".well-known/certification-package-overview.json" + } + ] + }, + { + "frr_id": "FRC-APP-AFC", + "status": "Not Applicable", + "implementation": "Checked: no application form completed or drafted in the repo.", + "evidence": [], + "not_applicable": "FedRAMP scopes the application rules to providers who have met all other relevant rules and are ready to apply. No application is made (operator's decision of 2026-11-05: build to apply, don't apply); the rule applies from the day one is." + }, + { + "frr_id": "FRC-APP-FCP", + "status": "Not Applicable", + "implementation": "The package is rebuilt on every deploy (deploy-with-opa.yml steps 'Build Security Decision Record (SDR — 20x SSP replacement)' and 'Build Certification Package Overview (CPO)') and daily by the package maintainer (package-maintenance.yml), and the runtime emitter re-validates the deployed system daily (the trust center's runtime check).", + "evidence": [], + "not_applicable": "FedRAMP scopes the application rules to providers who have met all other relevant rules and are ready to apply. No application is made (operator's decision of 2026-11-05: build to apply, don't apply); the rule applies from the day one is." + }, + { + "frr_id": "FRC-APP-FIA", + "status": "Not Applicable", + "implementation": "No FedRAMP Recognized assessor has assessed this system. Every deploy is assessed by the simulated assessor, whose overall summary the CPO carries in providerExtensions.independentAssessment (flagged simulated) and whose records the SDR quotes in providerExtensions.assessorRecords; neither is a FedRAMP initial assessment.", + "evidence": [], + "not_applicable": "FedRAMP scopes the application rules to providers who have met all other relevant rules and are ready to apply. No application is made (operator's decision of 2026-11-05: build to apply, don't apply); the rule applies from the day one is." + }, + { + "frr_id": "FRC-APP-MLF", + "status": "Not Applicable", + "implementation": "Not listed in the FedRAMP Marketplace, and no listing is sought (docs/cr26-applicability.md, MKT).", + "evidence": [], + "not_applicable": "FedRAMP scopes the application rules to providers who have met all other relevant rules and are ready to apply. No application is made (operator's decision of 2026-11-05: build to apply, don't apply); the rule applies from the day one is." + }, + { + "frr_id": "FRC-APP-NTP", + "status": "Not Applicable", + "implementation": "No application exists, and the CPO names the operator as the accountable official, the person who would apply.", + "evidence": [], + "not_applicable": "FedRAMP scopes the application rules to providers who have met all other relevant rules and are ready to apply. No application is made (operator's decision of 2026-11-05: build to apply, don't apply); the rule applies from the day one is." + }, + { + "frr_id": "FRC-APP-USA", + "status": "Not Applicable", + "implementation": "Permissive (MAY). Checked: no initial assessment exists, so there is nothing stale to freshen.", + "evidence": [], + "not_applicable": "FedRAMP scopes the application rules to providers who have met all other relevant rules and are ready to apply. No application is made (operator's decision of 2026-11-05: build to apply, don't apply); the rule applies from the day one is.", + "may_rationale": "Not exercised: no initial independent assessment exists, so there is nothing stale to freshen." + }, + { + "frr_id": "FRC-CSO-FCP", + "status": "Implemented", + "implementation": "The target profile is identified: FedRAMP 20x, Program path, Class C, Moderate (data/system-profile.json; the CPO's certificationType and providerExtensions). Every applicable rule has a record in data/frr-records.json, and the deploy's completeness gate stops every deploy unless each record is Implemented or Not Applicable, so a deployed system applies all relevant FedRAMP practices.", + "evidence": [ + { + "kind": "step", + "ref": "deploy-with-opa.yml#FedRAMP rules complete (no gaps)" + }, + { + "kind": "test", + "ref": "tests/test_frr_records.py::test_any_open_record_keeps_the_deploy_from_proceeding" + }, + { + "kind": "test", + "ref": "tests/test_frr_records.py::test_the_gate_runs_before_anything_is_applied" + }, + { + "kind": "artifact", + "ref": ".well-known/security-decision-record.json" + } + ] + }, + { + "frr_id": "FRC-CSO-JSN", + "status": "Implemented", + "implementation": "Every JSON document this offering supplies under a FedRAMP JSON schema (CPO, SDR, OCR and issued OCRs; the VDT, AVI and vulnerability history) is written through scripts/_fedramp_schema.write_validated against the vendored 2026-06-24 schemas: a document that fails is not written and the deploy stops, and the package submission re-validates the CPO, SDR and OCR. Public JSON under /.well-known/ is served by a CloudFront response-headers policy with read-only CORS (Access-Control-Allow-Origin: *, GET/HEAD/OPTIONS), Content-Type application/json and X-Content-Type-Options: nosniff (infrastructure/bootstrap/cloudfront.tf); every deploy checks those headers live and fails, before the SDR is built, when any is missing. Significant Change Notifications (scripts/build-scn.py, the SCN schema) and incident reports (scripts/build-incident-report.py, the incident schema) are written the same way: a notification or report that fails its schema is not written and the build stops.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_cpo_validates_against_fedramps_schema" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_rolling_ocr_validates_and_carries_the_cycle" + }, + { + "kind": "test", + "ref": "tests/test_sdr.py::test_it_validates_against_fedramps_schema" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_an_incomplete_or_inconsistent_package_is_not_submitted" + }, + { + "kind": "test", + "ref": "tests/test_wellknown_headers.py::test_the_known_bad_fixture_fails_for_missing_cors" + }, + { + "kind": "test", + "ref": "tests/test_wellknown_headers.py::test_the_well_known_behaviour_sends_read_only_cors_and_nosniff" + }, + { + "kind": "test", + "ref": "tests/test_wellknown_headers.py::test_the_deploy_checks_the_headers_before_the_sdr" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Check /.well-known/ JSON response headers (CORS, Content-Type, nosniff)" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_build_publishes_every_register_row_in_the_fedramp_schema" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_id_coverage.py::test_a_scn_notification_that_fails_the_schema_is_not_written" + }, + { + "kind": "test", + "ref": "tests/test_incidents.py::test_every_report_validates_against_fedramps_schema_and_is_listed_with_its_hash" + }, + { + "kind": "test", + "ref": "tests/test_fedramp_id_coverage.py::test_an_incident_report_that_fails_the_schema_is_not_written" + } + ] + }, + { + "frr_id": "FRC-CSO-MRA", + "status": "Implemented", + "implementation": "The operator keeps the package accurate with gates that fail the deploy: schema validation of the CPO, SDR and OCR; the reconciliation gate (one impact level and one inventory binding across the CPO, SDR, VDR and signal); one FedRAMP ID across the reports (check-fedramp-id.py); the package submission's completeness check (every applicable rule exactly once, one program); the FedRAMP Certification Reports' recorded sha256s; and a test that every link the CPO and OCR give resolves to something this repository publishes. The CCM calendar is validated on every build. Third-party-supplied records stay 'not recorded' until the operator decides them.", + "evidence": [ + { + "kind": "step", + "ref": "deploy-with-opa.yml#Reconciliation gate (fail closed on drift)" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#FedRAMP ID in every FedRAMP report (CDS-CSO-FID)" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Simulated package submission to FedRAMP (nothing is sent)" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_every_link_in_the_cpo_and_ocr_resolves" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_an_incomplete_or_inconsistent_package_is_not_submitted" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_a_bad_calendar_fails_closed" + } + ] + }, + { + "frr_id": "FRC-CSO-PKG", + "status": "Implemented", + "implementation": "scripts/submit-package.py checks the package on every deploy: the CPO (complete per CPO-CSO-OVR, including the trust center, secure configuration guidance, third-party resources and assessor summary), the SDR with every applicable rule exactly once, and the OCR, each valid against FedRAMP's schema, one FedRAMP ID across them and certificationType 20x. It then supplies the package to a simulated FedRAMP intake and appends a signed entry to /.well-known/package-submission-log.json for each content change. Nothing is sent.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_a_complete_package_is_logged_once_per_content_change" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_an_incomplete_or_inconsistent_package_is_not_submitted" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Simulated package submission to FedRAMP (nothing is sent)" + }, + { + "kind": "artifact", + "ref": ".well-known/package-submission-log.json" + } + ], + "simulated": { + "counterparty": "fedramp", + "how": "FedRAMP is simulated: the package goes to simulated_fedramp_intake() in scripts/submit-package.py, a function that never touches the network and returns an obviously fake receipt. The only trace is the signed, published submission log; any unexpected outcome fails the deploy." + } + }, + { + "frr_id": "FRC-CSO-POP", + "status": "Implemented", + "implementation": "The offering seeks FedRAMP 20x Program Certification only (DEC-107). The CPO states certificationType 20x; the package submission refuses any other; no label in the CPO or OCR names Rev5 as a program (the SDR's Rev5 view is the Moderate control baseline the 20x evidence maps onto).", + "evidence": [ + { + "kind": "decision", + "ref": "DEC-107" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_the_cpo_seeks_20x_only" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_no_cpo_or_ocr_label_names_rev5_as_a_program" + }, + { + "kind": "test", + "ref": "tests/test_certification_cycle.py::test_an_incomplete_or_inconsistent_package_is_not_submitted" + } + ] + }, + { + "frr_id": "FRC-CSX-MAS", + "status": "Implemented", + "implementation": "Every KSI is applied to the whole Minimum Assessment Scope. The inventory now includes the external services the app and the VDR depend on (MAS-CSO-IIR), and each KSI's evidence domain names the component types it covers. KSIs with a per-component domain apply to every component of those types; inventory and documentation KSIs (PIY, CED) apply over the whole set. scripts/build-mas.py publishes the application per KSI and per component type in .well-known/minimum-assessment-scope.json, and fails the deploy when a component type is in no KSI's per-component domain and has no stated whole-set reason (static pages and the state lock table carry one).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_mas.py::test_every_ksi_applies_and_every_component_type_is_covered" + }, + { + "kind": "test", + "ref": "tests/test_mas.py::test_component_type_in_no_ksi_domain_fails" + }, + { + "kind": "test", + "ref": "tests/test_mas.py::test_audit_trail_is_in_the_logging_ksi_domain" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build the Minimum Assessment Scope" + }, + { + "kind": "artifact", + "ref": ".well-known/minimum-assessment-scope.json" + } + ] + }, + { + "frr_id": "FRC-CSX-VVK", + "status": "Implemented", + "implementation": "The Security Decision Record counts, per KSI, the automated methods that verify and validate it (scripts/build-sdr.py; providerExtensions.automatedMethods): (1) the OPA plan gate on every deploy (rules annotated with ksi_ids in infrastructure/policy/*.rego, covering IAM, identity, keys, logging, network, compute, API and packages); (2) the daily signed runtime re-validation of the same Rego against live configuration for every machine component type (ksi-signal-runtime.json), credited to a KSI when its component refs intersect and only when the signal verifies and is fresh; (3) for a KSI whose components include npm or PyPI packages, dependency vulnerability scanning: the VDR report built from this inventory's Syft SBOM and Grype scans, counted only when it is bound to this inventory's signal_id, its Sigstore signature verifies, it is inside its 24-hour freshness window and every Grype scan passed the detection gate; (4) and (5) for KSI-CED-RAT, the two training checks of scripts/_training.py: the training packet is generated from the system's own data (every decision of the last 12 months, every incident and exercise, the rule and KSI counts and a fixed core) and completed by a simulated trainee whenever it changes; (4) checks that the latest completed packet covers everything the current data requires, and (5) that the current packet was completed by its due date with a score of at least 0.8 and a steady score trend. The history is carried forward in the SDR (providerExtensions.training). On the 2026-11-05 plan and a local run of the runtime readers, (1) and (2) give 43 of the 46 KSIs two methods; dependency scanning brings KSI-SCR-MIT and KSI-SCR-MON to two, and the training checks bring KSI-CED-RAT to two. No KSI relies on an accepted shortfall. The SDR publishes the count on each KSI. After apply and before it builds anything it publishes, the deploy stages its signed inventory and invokes the runtime emitter synchronously; the emitter re-validates the deployed system against that inventory and writes its signed signal beside it, and the deploy reads it back. The deploy's SDR build counts the runtime method only for that signal (it must have re-validated this commit) and fails the deploy, before anything is published, when any KSI has fewer than two automated methods and no in-force accepted decision record names it. The package maintainer, which runs after every deploy and daily, applies the same requirement to the SDR it rebuilds.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_validation_mapping.py::test_every_plan_validated_type_has_a_rule" + }, + { + "kind": "test", + "ref": "tests/test_runtime_readers.py::test_every_drift_is_caught_by_the_gate_rule" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Policy parity test (CLI vs Wasm)" + }, + { + "kind": "artifact", + "ref": ".well-known/ksi-signal-runtime.json" + }, + { + "kind": "test", + "ref": "tests/test_sdr_vvk.py::test_dependency_scanning_counts_only_for_ksis_with_package_components" + }, + { + "kind": "test", + "ref": "tests/test_sdr_vvk.py::test_known_bad_vdrs_do_not_count_each_for_its_reason" + }, + { + "kind": "test", + "ref": "tests/test_sdr_vvk.py::test_the_package_maintainer_requires_two_methods_and_the_deploy_supplies_the_vdr_signature" + }, + { + "kind": "step", + "ref": "package-maintenance.yml#Rebuild the SDR, OCR and CPO at the deployed commit" + }, + { + "kind": "artifact", + "ref": ".well-known/security-decision-record.json" + }, + { + "kind": "test", + "ref": "tests/test_sdr_vvk.py::test_known_bad_the_deploys_sdr_step_fails_on_a_shortfall_and_writes_nothing" + }, + { + "kind": "test", + "ref": "tests/test_sdr_vvk.py::test_the_deploy_invokes_the_emitter_after_apply_and_requires_two_methods_before_publishing" + }, + { + "kind": "test", + "ref": "tests/test_sdr_vvk.py::test_the_runtime_signal_counts_only_for_this_commits_inventory" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Re-validate the deployed system against this inventory (runtime emitter, FRC-CSX-VVK)" + }, + { + "kind": "test", + "ref": "tests/test_sdr_vvk.py::test_with_the_committed_register_every_ksi_has_two_methods_and_none_is_accepted_short" + }, + { + "kind": "test", + "ref": "tests/test_sdr_vvk.py::test_known_bad_without_the_training_methods_ksi_ced_rat_is_a_shortfall" + }, + { + "kind": "test", + "ref": "tests/test_training.py::test_known_bad_a_packet_missing_a_new_decision_fails_currency" + }, + { + "kind": "test", + "ref": "tests/test_training.py::test_known_bad_a_late_or_failing_completion_fails_completion" + } + ], + "simulated": { + "counterparty": "personnel", + "how": "The trainee is simulated ('Pat Placeholder (simulated)', DEC-194): it takes the generated quiz on every SDR build where the packet changed, in the deploy and the package maintainer, and misses every ninth question on purpose. No person is enrolled." + } + }, + { + "frr_id": "FRC-CSX-VVR", + "status": "Implemented", + "implementation": "scripts/_frr.py validates the rule records on every build (set matches the pinned corpus, every cited piece of evidence resolves). In addition the unit-test job runs pytest with JUnit output and scripts/check-frr-evidence.py fails the deploy unless every test cited as evidence for a rule passed (a skipped or missing cited test is not a pass), and publishes the result per record (frr-evidence.json). The simulated assessor then re-runs the cited tests and re-checks every step, decision and artifact independently.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_frr_evidence.py::test_known_bad_a_failing_cited_test_fails_the_build" + }, + { + "kind": "test", + "ref": "tests/test_frr_evidence.py::test_a_skipped_or_missing_cited_test_is_not_a_pass" + }, + { + "kind": "test", + "ref": "tests/test_frr_evidence.py::test_the_unit_test_job_runs_the_check_on_its_own_results" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#FedRAMP rule evidence passed (cited tests)" + }, + { + "kind": "artifact", + "ref": ".well-known/frr-evidence.json" + } + ] + }, + { + "frr_id": "IEC-CSO-AIR", + "status": "Implemented", + "implementation": ".github/workflows/incident-reports.yml runs on every push of data/incidents.json to main, by hand, twice a day and after each nightly VDR refresh: it validates the register, verifies the published VDR, builds every report against FedRAMP's schema, signs, redaction-gates and publishes under /.well-known/incident-* with its own least-privilege role (infrastructure/bootstrap/incident-reports.tf), and fails with a GitHub issue when a report is overdue; the evidence watchdog pages on the same deadlines hourly. A person records the facts in the register; nothing else is done by hand. Every deploy checks the publisher's prerequisites before it applies anything (scripts/check-incident-publisher.py: the role variable names the bootstrap role and the incident-reports environment deploys only from main), assumes the publisher's role from the deploy job before the SDR is built (scripts/check-incident-role.py, step 'Incident report publisher role can be assumed'), so a deploy whose publisher role does not work stops before anything is published, and after the deploy job runs this workflow on its own role (job incident-publisher). Delivery is SIMULATED: on every deploy and every unattended publish, scripts/deliver-incident-reports.py reads back each report the incident log lists, checks it against the published sha256 and FedRAMP's incident report schema, and 'delivers' it to a simulated FedRAMP recipient ('FedRAMP Incident Desk (simulated)') and to each affected agency, also simulated; a delivery that fails stops publication. The signed delivery log is /.well-known/incident-deliveries.json. Nothing is sent to FedRAMP or to any agency: there is no FedRAMP certification and no agency customer to send to.", + "evidence": [ + { + "kind": "step", + "ref": "incident-reports.yml#Build incident reports (IIR, OIR, FIR)" + }, + { + "kind": "step", + "ref": "incident-reports.yml#Incident report clocks (fail when a report is due and missing)" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Incident report publisher preflight" + }, + { + "kind": "test", + "ref": "tests/test_incidents.py::test_deploy_proves_the_publisher_by_calling_it_after_the_deploy" + }, + { + "kind": "test", + "ref": "tests/test_incidents.py::test_air_workflow_validates_builds_signs_publishes_and_checks_the_clock_in_order" + }, + { + "kind": "artifact", + "ref": ".well-known/incident-reports.json" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build incident reports (IIR, OIR, FIR)" + }, + { + "kind": "artifact", + "ref": ".well-known/incident-deliveries.json" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Incident report publisher role can be assumed" + }, + { + "kind": "test", + "ref": "tests/test_incident_delivery.py::test_the_role_check_runs_in_the_deploy_job_before_the_sdr_build" + }, + { + "kind": "test", + "ref": "tests/test_incident_delivery.py::test_a_role_that_cannot_be_assumed_fails_the_deploy" + }, + { + "kind": "test", + "ref": "tests/test_incident_delivery.py::test_delivery_runs_before_signing_in_the_deploy_and_before_publishing_in_the_publisher" + } + ], + "simulated": { + "counterparty": "incident-recipient", + "how": "FedRAMP and the affected agencies are simulated recipients: each report is read back, hash- and schema-checked and recorded as delivered in /.well-known/incident-deliveries.json on every deploy and every unattended publish; nothing is sent." + } + }, + { + "frr_id": "IEC-CSO-DPR", + "status": "Implemented", + "implementation": "data/incidents.json (the incident register; shape infrastructure/schemas/incidents.schema.json) is read through scripts/_incidents.py, which fails closed. scripts/build-incident-report.py renders the Initial, Ongoing and Final reports in FedRAMP's 2026-06-24 incident report schema (validated before write) and the incident log, published signed as /.well-known/incident-reports.json by every deploy and by .github/workflows/incident-reports.yml on every change to the register. Class C report clocks and the Incident Rating scale are read from the pinned rules (scripts/_rules.py). A reportable incident is rated at the default the IEC-CSO-DPR text states (N5, read from the rule) until an IEC-CSO-EFI estimate record exists, and the report clocks use the rating in force at each start time. Exercised once, 2026-11-05: INC-2026-001 (simulated, exercise: true) runs IIR, two OIRs and an FIR on a simulated timeline, all inside their clocks; INC-2026-002 (simulated) is evaluated not reportable with its reason. ", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_incidents.py::test_an_unrated_incident_is_n5_and_its_initial_report_is_due_in_an_hour" + }, + { + "kind": "test", + "ref": "tests/test_incidents.py::test_exercise_shows_the_default_rating_then_the_estimate" + }, + { + "kind": "artifact", + "ref": ".well-known/incident-reports.json" + } + ] + }, + { + "frr_id": "IEC-CSO-EFI", + "status": "Implemented", + "implementation": "data/incidents.json (the incident register; shape infrastructure/schemas/incidents.schema.json) is read through scripts/_incidents.py, which fails closed. scripts/build-incident-report.py renders the Initial, Ongoing and Final reports in FedRAMP's 2026-06-24 incident report schema (validated before write) and the incident log, published signed as /.well-known/incident-reports.json by every deploy and by .github/workflows/incident-reports.yml on every change to the register. Class C report clocks and the Incident Rating scale are read from the pinned rules (scripts/_rules.py). An estimate record carries rating, customer effect (minimal/narrow/disruptive/debilitating), one or several agencies, reason and time; the loader refuses a rating that is not the one the IEC-CSO-EFI bullets give for that effect and agency count (the rubric is parsed from the rule text). Exercised once, 2026-11-05: INC-2026-001 (simulated, exercise: true) runs IIR, two OIRs and an FIR on a simulated timeline, all inside their clocks; INC-2026-002 (simulated) is evaluated not reportable with its reason. ", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_incidents.py::test_each_known_bad_register_fails_closed_for_its_reason" + }, + { + "kind": "test", + "ref": "tests/test_incidents.py::test_rating_scale_and_default_come_from_the_rules" + }, + { + "kind": "test", + "ref": "tests/test_incidents.py::test_exercise_shows_the_default_rating_then_the_estimate" + }, + { + "kind": "artifact", + "ref": ".well-known/incident-reports.json" + } + ] + }, + { + "frr_id": "IEC-CSO-EFR", + "status": "Implemented", + "implementation": "data/incidents.json (the incident register; shape infrastructure/schemas/incidents.schema.json) is read through scripts/_incidents.py, which fails closed. scripts/build-incident-report.py renders the Initial, Ongoing and Final reports in FedRAMP's 2026-06-24 incident report schema (validated before write) and the incident log, published signed as /.well-known/incident-reports.json by every deploy and by .github/workflows/incident-reports.yml on every change to the register. Class C report clocks and the Incident Rating scale are read from the pinned rules (scripts/_rules.py). Every incident record must carry an evaluation (evaluated_at, reportable true/false, basis, reason, the federal customer data considered); a record without one does not load. docs/incident-response.md triage now evaluates reportability before containment. Exercised once, 2026-11-05: INC-2026-001 (simulated, exercise: true) runs IIR, two OIRs and an FIR on a simulated timeline, all inside their clocks; INC-2026-002 (simulated) is evaluated not reportable with its reason. The published incident log is the artifact the rule asks for.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_incidents.py::test_each_known_bad_register_fails_closed_for_its_reason" + }, + { + "kind": "test", + "ref": "tests/test_incidents.py::test_exercise_logs_a_not_reportable_evaluation_with_its_reason" + }, + { + "kind": "artifact", + "ref": ".well-known/incident-reports.json" + } + ] + }, + { + "frr_id": "IEC-CSO-FIR", + "status": "Implemented", + "implementation": "data/incidents.json (the incident register; shape infrastructure/schemas/incidents.schema.json) is read through scripts/_incidents.py, which fails closed. scripts/build-incident-report.py renders the Initial, Ongoing and Final reports in FedRAMP's 2026-06-24 incident report schema (validated before write) and the incident log, published signed as /.well-known/incident-reports.json by every deploy and by .github/workflows/incident-reports.yml on every change to the register. Class C report clocks and the Incident Rating scale are read from the pinned rules (scripts/_rules.py). A Final report is allowed only after resolved_at and recovery_complete_at, restates final values for every earlier item, carries resolvedAt, and is due an FIR period after recovery (6 hours at N3-N5, 1 business day at N1-N2); overdue fails the workflow and pages. Exercised once, 2026-11-05: INC-2026-001 (simulated, exercise: true) runs IIR, two OIRs and an FIR on a simulated timeline, all inside their clocks; INC-2026-002 (simulated) is evaluated not reportable with its reason. Delivery is SIMULATED: on every deploy and every unattended publish, scripts/deliver-incident-reports.py reads back each report the incident log lists, checks it against the published sha256 and FedRAMP's incident report schema, and 'delivers' it to a simulated FedRAMP recipient ('FedRAMP Incident Desk (simulated)') and to each affected agency, also simulated; a delivery that fails stops publication. The signed delivery log is /.well-known/incident-deliveries.json. Nothing is sent to FedRAMP or to any agency: there is no FedRAMP certification and no agency customer to send to.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_incidents.py::test_the_final_report_is_due_after_recovery_and_ongoing_reports_stop" + }, + { + "kind": "test", + "ref": "tests/test_incidents.py::test_ongoing_and_final_reports_restate_every_earlier_item" + }, + { + "kind": "artifact", + "ref": ".well-known/incident-reports.json" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build incident reports (IIR, OIR, FIR)" + }, + { + "kind": "artifact", + "ref": ".well-known/incident-deliveries.json" + }, + { + "kind": "test", + "ref": "tests/test_incident_delivery.py::test_every_report_is_delivered_to_a_simulated_fedramp_and_agency_recipient" + } + ], + "simulated": { + "counterparty": "incident-recipient", + "how": "FedRAMP and the affected agencies are simulated recipients: each report is read back, hash- and schema-checked and recorded as delivered in /.well-known/incident-deliveries.json on every deploy and every unattended publish; nothing is sent." + } + }, + { + "frr_id": "IEC-CSO-IIR", + "status": "Implemented", + "implementation": "data/incidents.json (the incident register; shape infrastructure/schemas/incidents.schema.json) is read through scripts/_incidents.py, which fails closed. scripts/build-incident-report.py renders the Initial, Ongoing and Final reports in FedRAMP's 2026-06-24 incident report schema (validated before write) and the incident log, published signed as /.well-known/incident-reports.json by every deploy and by .github/workflows/incident-reports.yml on every change to the register. Class C report clocks and the Incident Rating scale are read from the pinned rules (scripts/_rules.py). The Initial report carries all eight items (coordinator, tracking ID, description, timeline with start/detection/evaluation/milestones, historical and current rating with the EFI explanation, functional impact, recovery plan, likely affected agencies). Its clock (1 hour at N3-N5, 24 hours at N2, 1 business day at N1) runs from the evaluation; the incident-reports workflow fails and the evidence watchdog pages (IncidentReportsOverdue) once it passes. Exercised once, 2026-11-05: INC-2026-001 (simulated, exercise: true) runs IIR, two OIRs and an FIR on a simulated timeline, all inside their clocks; INC-2026-002 (simulated) is evaluated not reportable with its reason. Delivery is SIMULATED: on every deploy and every unattended publish, scripts/deliver-incident-reports.py reads back each report the incident log lists, checks it against the published sha256 and FedRAMP's incident report schema, and 'delivers' it to a simulated FedRAMP recipient ('FedRAMP Incident Desk (simulated)') and to each affected agency, also simulated; a delivery that fails stops publication. The signed delivery log is /.well-known/incident-deliveries.json. Nothing is sent to FedRAMP or to any agency: there is no FedRAMP certification and no agency customer to send to.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_incidents.py::test_exercise_runs_initial_ongoing_final_all_on_time" + }, + { + "kind": "test", + "ref": "tests/test_incidents.py::test_every_report_validates_against_fedramps_schema_and_is_listed_with_its_hash" + }, + { + "kind": "test", + "ref": "tests/test_incidents.py::test_an_unrated_incident_is_n5_and_its_initial_report_is_due_in_an_hour" + }, + { + "kind": "artifact", + "ref": ".well-known/incident-reports.json" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build incident reports (IIR, OIR, FIR)" + }, + { + "kind": "artifact", + "ref": ".well-known/incident-deliveries.json" + }, + { + "kind": "test", + "ref": "tests/test_incident_delivery.py::test_every_report_is_delivered_to_a_simulated_fedramp_and_agency_recipient" + }, + { + "kind": "test", + "ref": "tests/test_incident_delivery.py::test_known_bad_logs_fail_delivery_and_write_nothing" + } + ], + "simulated": { + "counterparty": "incident-recipient", + "how": "FedRAMP and the affected agencies are simulated recipients: each report is read back, hash- and schema-checked and recorded as delivered in /.well-known/incident-deliveries.json on every deploy and every unattended publish; nothing is sent." + } + }, + { + "frr_id": "IEC-CSO-OIR", + "status": "Implemented", + "implementation": "data/incidents.json (the incident register; shape infrastructure/schemas/incidents.schema.json) is read through scripts/_incidents.py, which fails closed. scripts/build-incident-report.py renders the Initial, Ongoing and Final reports in FedRAMP's 2026-06-24 incident report schema (validated before write) and the incident log, published signed as /.well-known/incident-reports.json by every deploy and by .github/workflows/incident-reports.yml on every change to the register. Class C report clocks and the Incident Rating scale are read from the pinned rules (scripts/_rules.py). Each Ongoing report restates every earlier item with its latest value and marks each 'updated' or 'no update', and adds observed activity, indicators of compromise, related CVEs, root cause and response/recovery activities. The next one is due an OIR period (6 hours at N3-N5, 24 at N2, 1 business day at N1) after the previous report until the incident is resolved; overdue fails the workflow and pages. Exercised once, 2026-11-05: INC-2026-001 (simulated, exercise: true) runs IIR, two OIRs and an FIR on a simulated timeline, all inside their clocks; INC-2026-002 (simulated) is evaluated not reportable with its reason. Delivery is SIMULATED: on every deploy and every unattended publish, scripts/deliver-incident-reports.py reads back each report the incident log lists, checks it against the published sha256 and FedRAMP's incident report schema, and 'delivers' it to a simulated FedRAMP recipient ('FedRAMP Incident Desk (simulated)') and to each affected agency, also simulated; a delivery that fails stops publication. The signed delivery log is /.well-known/incident-deliveries.json. Nothing is sent to FedRAMP or to any agency: there is no FedRAMP certification and no agency customer to send to.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_incidents.py::test_ongoing_reports_are_due_every_oir_period_until_resolved" + }, + { + "kind": "test", + "ref": "tests/test_incidents.py::test_ongoing_and_final_reports_restate_every_earlier_item" + }, + { + "kind": "artifact", + "ref": ".well-known/incident-reports.json" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build incident reports (IIR, OIR, FIR)" + }, + { + "kind": "artifact", + "ref": ".well-known/incident-deliveries.json" + }, + { + "kind": "test", + "ref": "tests/test_incident_delivery.py::test_every_report_is_delivered_to_a_simulated_fedramp_and_agency_recipient" + } + ], + "simulated": { + "counterparty": "incident-recipient", + "how": "FedRAMP and the affected agencies are simulated recipients: each report is read back, hash- and schema-checked and recorded as delivered in /.well-known/incident-deliveries.json on every deploy and every unattended publish; nothing is sent." + } + }, + { + "frr_id": "IVV-CSO-DUS", + "status": "Implemented", + "implementation": "No representative samples are used: every check runs over its full population, and the assessor guide states this with what each population is (the sampling section). The operator's decision DEC-167 records it, and requires the guide and this record to change before any sampling is introduced.", + "evidence": [ + { + "kind": "decision", + "ref": "DEC-167" + }, + { + "kind": "test", + "ref": "tests/test_assessor_guide.py::test_the_guide_states_that_no_samples_are_used" + }, + { + "kind": "artifact", + "ref": ".well-known/assessor-guide.json" + } + ] + }, + { + "frr_id": "IVV-CSO-FIA", + "status": "Implemented", + "implementation": "Every deploy is independently verified and validated, across all applicable rules and KSIs, twice by the simulated assessor workflow; the cadence is far more frequent than once a year. Before the deploy (a gate): it verifies the repository at the commit being deployed and validates the published state that commit replaces, and its signed set names that commit and the KSI signal it validated. The deploy reads the live KSI signal itself (signature verified against the deploy identity), scripts/_assessor.load_assessment refuses a set covering any other commit or signal, the deploy does not proceed on any failed check, and the SDR states which commit and signal the assessment covered (providerExtensions.assessmentCoverage). After the deploy has published, and the unattended package and incident publishers have run, the same assessor assesses the just-published state, which must carry the deployed commit; its set must verify against the pinned assessor identity and cover this commit and the KSI signal this deploy published. A failure there fails the run and raises the deployment-failure issue; what was published is not withdrawn. The pre-deploy set (simulated-assessment.json) is published and its per-rule results are carried in the SDR; the post-deploy set is kept with the run. The assessor is simulated: no FedRAMP Recognized assessment service is engaged (operator's decision of 2026-11-05).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_a_sound_package_passes_every_rule_and_ksi" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_every_rule_and_ksi_gets_its_independent_result_and_t74_holds" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_main_exits_non_zero_on_any_failure" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_the_simulation_is_labelled_and_claims_no_fedramp_recognition" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_the_deploy_needs_the_assessor_and_builds_the_sdr_from_its_set" + }, + { + "kind": "step", + "ref": "simulated-assessor.yml#Assess every rule and KSI (verification and validation)" + }, + { + "kind": "step", + "ref": "simulated-assessor.yml#Sign the assessment (keyless, the assessor's own identity)" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Download the simulated assessment" + }, + { + "kind": "artifact", + "ref": ".well-known/simulated-assessment.json" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_known_bad_a_set_covering_another_commit_or_signal_is_refused" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_the_deploy_binds_the_pre_deploy_set_to_this_commit_and_the_live_signal" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_a_post_deploy_assessment_runs_after_publish_and_its_failure_alerts" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_after_the_deploy_the_live_signal_must_carry_the_deployed_commit" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Bind the pre-deploy assessment to the state it covered" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Verify the post-deploy assessment covers the just-published state" + } + ], + "simulated": { + "counterparty": "assessor", + "how": "Totally Real Assessment Services, LLC (simulated) is a reusable GitHub Actions workflow in this repository (simulated-assessor.yml) that runs twice on every deploy: before the SDR is built (the commit being deployed and the published state it replaces) and after publish (the just-published state, which must carry the deployed commit). Each run follows the provider's assessor guide, re-runs every cited test, checks every workflow step and decision, fetches and cosign-verifies every published artifact, and signs its results keylessly under its own workflow identity, which infrastructure/keys/assessor-identity.json pins; each signed set names the commit and KSI signal it covered. The run fails if the assessor finds a failure, if its signature does not verify against that identity, if a record was altered, or if the set covers any other commit or signal. It is not a FedRAMP Recognized assessment service and its set says so (fedramp_recognized: false); only the assessor is simulated, the mechanism is real." + } + }, + { + "frr_id": "IVV-CSO-ICP", + "status": "Implemented", + "implementation": "The assessment results are published unmodified: the signed pre-deploy set itself (simulated-assessment.json with its cosign bundle), and in the SDR, where scripts/_assessor.py admits the set only if its keyless signature verifies against the pinned assessor identity, every record's hash matches, and the set covers the commit being deployed and the published KSI signal the deploy itself read; it carries each record verbatim, and verify_output fails the build if the SDR's copy differs in any byte. The SDR states which commit and signal the carried results covered (providerExtensions.assessmentCoverage).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_the_set_round_trips_through_the_provider_port" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_known_bad_tampered_record_fails" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_set_whose_signature_does_not_verify_fails" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_every_rule_and_ksi_gets_its_independent_result_and_t74_holds" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build Security Decision Record (SDR — 20x SSP replacement)" + }, + { + "kind": "artifact", + "ref": ".well-known/simulated-assessment.json" + }, + { + "kind": "artifact", + "ref": ".well-known/security-decision-record.json" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_known_bad_a_set_covering_another_commit_or_signal_is_refused" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_the_sdr_states_which_commit_and_signal_its_assessment_covered" + } + ], + "simulated": { + "counterparty": "assessor", + "how": "Totally Real Assessment Services, LLC (simulated) is a reusable GitHub Actions workflow in this repository (simulated-assessor.yml) that runs twice on every deploy: before the SDR is built (the commit being deployed and the published state it replaces) and after publish (the just-published state, which must carry the deployed commit). Each run follows the provider's assessor guide, re-runs every cited test, checks every workflow step and decision, fetches and cosign-verifies every published artifact, and signs its results keylessly under its own workflow identity, which infrastructure/keys/assessor-identity.json pins; each signed set names the commit and KSI signal it covered. The run fails if the assessor finds a failure, if its signature does not verify against that identity, if a record was altered, or if the set covers any other commit or signal. It is not a FedRAMP Recognized assessment service and its set says so (fedramp_recognized: false); only the assessor is simulated, the mechanism is real." + } + }, + { + "frr_id": "IVV-CSO-RAA", + "status": "Not Applicable", + "implementation": "The only assessor is the simulated one (Totally Real Assessment Services, LLC (simulated)), which reports results and offers no advice; no FedRAMP Recognized assessor is engaged.", + "evidence": [], + "not_applicable": "A MAY permission that is not exercised; see the rationale.", + "may_rationale": "Not exercised: the simulated assessor reports results and gives no advice to accept, and no FedRAMP Recognized assessor is engaged for this proof of concept." + }, + { + "frr_id": "IVV-CSO-SEE", + "status": "Implemented", + "implementation": "Every rule record in the SDR states, for each piece of evidence, how it validates the measure and on what cycle (a test on every pull request and deploy, a workflow step each run, a published artifact on its freshness cadence with the watchdog's alarm window, or a decision record with its review date); every KSI states its deploy-time validations and failures and its daily runtime re-validation. The SDR is signed and published, so an assessor reads it without a request.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_sdr_ksi_metrics.py::test_each_rule_states_how_each_piece_of_evidence_verifies_it" + }, + { + "kind": "test", + "ref": "tests/test_sdr_ksi_metrics.py::test_artifact_evidence_states_its_cycle" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build Security Decision Record (SDR — 20x SSP replacement)" + }, + { + "kind": "artifact", + "ref": ".well-known/security-decision-record.json" + } + ], + "simulated": { + "counterparty": "assessor", + "how": "No FedRAMP Recognized assessor is engaged. The evidence is supplied by publishing the signed SDR at /.well-known/, where any assessor reads it without a request; the simulated assessor (Totally Real Assessment Services, LLC (simulated), simulated-assessor.yml) reads it from there on every deploy." + } + }, + { + "frr_id": "IVV-CSO-SEI", + "status": "Implemented", + "implementation": "Every rule record in the SDR names the test, workflow step, published artifact or decision record that verifies its implementation, and every KSI names its measures (the OPA rules annotated to it, by file and rule), the components they cover, how the annotations and the automation are verified, or why there is no measure and the risk. The SDR is signed and published with verification instructions (docs/verification.md, scripts/verify-published.sh).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_sdr_ksi_metrics.py::test_each_rule_states_how_each_piece_of_evidence_verifies_it" + }, + { + "kind": "test", + "ref": "tests/test_sdr_ksi_metrics.py::test_each_ksi_states_its_own_measures_cycle_and_validation" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build Security Decision Record (SDR — 20x SSP replacement)" + }, + { + "kind": "artifact", + "ref": ".well-known/security-decision-record.json" + } + ], + "simulated": { + "counterparty": "assessor", + "how": "No FedRAMP Recognized assessor is engaged. The evidence is supplied by publishing the signed SDR at /.well-known/, where any assessor reads it without a request; the simulated assessor (Totally Real Assessment Services, LLC (simulated), simulated-assessor.yml) reads it from there on every deploy." + } + }, + { + "frr_id": "IVV-CSO-STE", + "status": "Implemented", + "implementation": "The assessor guide (assessor-guide.json and .md, built on every deploy from the rule records) gives, for every applicable rule and KSI, the rule text, the provider's explanation, and for each piece of evidence a command that reproduces it plus the same check in machine form (pytest node, workflow step, artifact URL with its signature bundle, signing identity and maximum age, or decision ID). The simulated assessor runs exactly these checks. Demonstrations are offered through the security contact.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_assessor_guide.py::test_every_rule_and_ksi_is_in_the_guide_with_a_reproducible_check" + }, + { + "kind": "test", + "ref": "tests/test_assessor_guide.py::test_signed_artifacts_name_the_identity_that_signed_them" + }, + { + "kind": "test", + "ref": "tests/test_assessor_guide.py::test_the_deploy_builds_the_guide_and_the_assessor_follows_it" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build the assessor guide" + }, + { + "kind": "artifact", + "ref": ".well-known/assessor-guide.json" + } + ] + }, + { + "frr_id": "IVV-CSO-USR", + "status": "Not Applicable", + "implementation": "No sampling in use.", + "evidence": [], + "not_applicable": "A MAY permission that is not exercised; see the rationale.", + "may_rationale": "Not exercised. The system is small enough to verify and validate every resource, and full coverage is a stronger claim than a sample." + }, + { + "frr_id": "IVV-CSX-AIA", + "status": "Implemented", + "implementation": "The simulated assessor checks every Key Security Indicator in the catalog alongside every rule, twice on every deploy: it fetches the published KSI signal, verifies its signature against the deploy identity, and fails a KSI the signal does not report passing (before the deploy, one missing from the signal is an observation). Before the deploy the signal is the published one the deploy replaces; its signal_id is bound into the signed set, the deploy refuses a set naming any other, and the SDR states it. After publish the check runs again on the just-published signal, which must carry the deployed commit and be the signal this deploy published; a failure fails the run and raises the deployment-failure issue. The pre-deploy result per KSI is carried verbatim in the SDR.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_every_rule_and_ksi_gets_its_independent_result_and_t74_holds" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_a_sound_package_passes_every_rule_and_ksi" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_a_ksi_the_signal_does_not_report_passing_is_a_failure" + }, + { + "kind": "step", + "ref": "simulated-assessor.yml#Assess every rule and KSI (verification and validation)" + }, + { + "kind": "artifact", + "ref": ".well-known/simulated-assessment.json" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_after_the_deploy_the_live_signal_must_carry_the_deployed_commit" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_known_bad_a_set_covering_another_commit_or_signal_is_refused" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Verify the post-deploy assessment covers the just-published state" + } + ], + "simulated": { + "counterparty": "assessor", + "how": "Totally Real Assessment Services, LLC (simulated) is a reusable GitHub Actions workflow in this repository (simulated-assessor.yml) that runs twice on every deploy: before the SDR is built (the commit being deployed and the published state it replaces) and after publish (the just-published state, which must carry the deployed commit). Each run follows the provider's assessor guide, re-runs every cited test, checks every workflow step and decision, fetches and cosign-verifies every published artifact, and signs its results keylessly under its own workflow identity, which infrastructure/keys/assessor-identity.json pins; each signed set names the commit and KSI signal it covered. The run fails if the assessor finds a failure, if its signature does not verify against that identity, if a record was altered, or if the set covers any other commit or signal. It is not a FedRAMP Recognized assessment service and its set says so (fedramp_recognized: false); only the assessor is simulated, the mechanism is real." + } + }, + { + "frr_id": "MAS-CSO-FLO", + "status": "Implemented", + "implementation": "The boundary classification's data-flow table (docs/boundary/boundary-classification.json) covers every external service and every data store or log in the inventory, including sign-in to the Cognito Hosted UI, the browser loads from jsDelivr and Google Cloud Storage, log delivery to the access-log and CloudTrail buckets and the log groups, the dead-letter queue, operator administration with MFA, Terraform state and lock, and the vulnerability feeds. scripts/build-mas.py resolves each flow against this build's inventory, gives each the high-water mark of its endpoints' FIPS 199 security categories, and fails the deploy when a flow names a component the inventory lacks or an external service or data store is in no flow. Published in .well-known/minimum-assessment-scope.json (flows with categories, protocol, authentication, encryption and data) and drawn on the boundary map.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_mas.py::test_flow_gaps_fail" + }, + { + "kind": "test", + "ref": "tests/test_mas.py::test_every_external_service_and_data_store_in_the_inventory_is_in_a_flow" + }, + { + "kind": "test", + "ref": "tests/test_mas.py::test_flow_category_is_the_high_water_mark_of_its_endpoints" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build the Minimum Assessment Scope" + }, + { + "kind": "artifact", + "ref": ".well-known/minimum-assessment-scope.json" + }, + { + "kind": "artifact", + "ref": ".well-known/boundary-map.json" + } + ] + }, + { + "frr_id": "MAS-CSO-IIR", + "status": "Implemented", + "implementation": "Every deploy publishes the set of information resources that make up the offering: the canonical inventory (.well-known/ksi-signal.json, derived from Terraform state, the SBOMs, the site's HTML and the declared external services; reconcile invariant (a) holds every live in-boundary resource to it) and its summary in .well-known/minimum-assessment-scope.json with a human-readable twin and the derivation. The external services include every origin the Silk Reeling app loads code or data from in the user's browser (jsDelivr for the MediaPipe runtime, Google Cloud Storage for the pose model) and every vulnerability feed the VDR reads (GitHub Advisory Database, CISA KEV, FIRST EPSS, the Grype database). scripts/build-mas.py parses the Content Security Policies the edge serves (infrastructure/bootstrap/cloudfront.tf) and fails the deploy, before the SDR is built, when an allowed off-origin host is neither an inventoried component nor out of scope with a stated reason; the podcast audio hosts (media only, no code or data from this system) are out of scope with that reason.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_mas.py::test_unplaced_csp_host_fails" + }, + { + "kind": "test", + "ref": "tests/test_mas.py::test_unresolvable_csp_source_fails_closed" + }, + { + "kind": "test", + "ref": "tests/test_mas.py::test_the_app_origins_are_inventoried_external_services" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build the Minimum Assessment Scope" + }, + { + "kind": "artifact", + "ref": ".well-known/minimum-assessment-scope.json" + }, + { + "kind": "artifact", + "ref": ".well-known/ksi-signal.json" + } + ] + }, + { + "frr_id": "MAS-CSO-MDI", + "status": "Implemented", + "implementation": "The metadata the offering collects is in scope and inventoried: every data store and log in the inventory (buckets, log groups, the CloudTrail trail, the state lock table, the dead-letter queue, the Cognito user pool, the alert topic) and the request metadata third parties see when the app loads code or models (jsDelivr, Google Cloud Storage) has an entry stating what it holds, which personal data (for example IP addresses, user agents, the app users' email addresses), its retention and its location. scripts/build-mas.py joins data/minimum-assessment-scope.json with this build's inventory and fails the deploy when a data store or log has no entry; a test holds each stated retention equal to the Terraform. Published, with the explanation of its derivation, in .well-known/minimum-assessment-scope.json and its Markdown twin.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_mas.py::test_data_store_without_metadata_fails" + }, + { + "kind": "test", + "ref": "tests/test_mas.py::test_metadata_retention_matches_the_terraform" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build the Minimum Assessment Scope" + }, + { + "kind": "artifact", + "ref": ".well-known/minimum-assessment-scope.json" + } + ] + }, + { + "frr_id": "MAS-CSO-SUP", + "status": "Not Applicable", + "implementation": "Permissive (MAY). Checked: the package supplies no supplement; CPO package_contents lists only in-scope artifacts.", + "evidence": [], + "not_applicable": "A MAY permission that is not exercised; see the rationale.", + "may_rationale": "Not exercised. The package covers only the offering. The other-framework views on the trust page are derived from the same controls and evidence, not separate resources." + }, + { + "frr_id": "MAS-CSO-TPR", + "status": "Implemented", + "implementation": "Each of the 11 third-party information resources (Sigstore Fulcio and Rekor, GitHub repository and Actions, GitHub OIDC, the operator's MFA authenticator, the GitHub Advisory Database, CISA KEV, FIRST EPSS, the Grype database, jsDelivr, Google Cloud Storage) has a decided record in data/third-party-components.json with its general usage and configuration, justification for use, mitigation measures and compensating controls. The inventory builder fails when a decided record lacks any of the four, and scripts/build-mas.py fails the deploy when an inventoried external service has no decided record. Machine-readable output: the external_service components in .well-known/ksi-signal.json and the third-party section of .well-known/minimum-assessment-scope.json; the human-readable derivation is in its Markdown twin; the code is scripts/build-ksi-signal.py and scripts/build-mas.py. The CPO lists each, none FedRAMP certified, in thirdPartyInformationResources.nonCertified (scripts/_tpr.py).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_mas.py::test_decided_third_party_record_without_the_four_fields_fails_the_inventory" + }, + { + "kind": "test", + "ref": "tests/test_mas.py::test_every_third_party_resource_is_decided_with_the_four_fields" + }, + { + "kind": "test", + "ref": "tests/test_mas.py::test_published_inventory_carries_the_four_fields" + }, + { + "kind": "test", + "ref": "tests/test_mas.py::test_cpo_helper_matches_the_cpo_schema" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build the Minimum Assessment Scope" + }, + { + "kind": "artifact", + "ref": ".well-known/minimum-assessment-scope.json" + }, + { + "kind": "test", + "ref": "tests/test_cpo_trust_fields.py::test_third_party_resources_are_the_decided_records" + } + ] + }, + { + "frr_id": "MKT-CSO-MLR", + "status": "Not Applicable", + "implementation": "The CDS-CSO-PUB data a listing would need exists (see CDS-CSO-PUB); no listing is requested.", + "evidence": [], + "not_applicable": "FedRAMP scopes the Marketplace rules to providers seeking a listing in the FedRAMP Marketplace. No listing is sought, by statutory scope: the offering has no agency use case within 44 USC § 3506, which MKT-IIP-AGU requires, so it is outside FedRAMP's scope and no listing request is made (docs/cr26-applicability.md). The rule would apply from the day a listing were sought." + }, + { + "frr_id": "MKT-CSO-PML", + "status": "Not Applicable", + "implementation": "Checked: no listing request has been sent (docs/cr26-applicability.md records MKT as Not Applicable).", + "evidence": [], + "not_applicable": "FedRAMP scopes the Marketplace rules to providers seeking a listing in the FedRAMP Marketplace. No listing is sought, by statutory scope: the offering has no agency use case within 44 USC § 3506, which MKT-IIP-AGU requires, so it is outside FedRAMP's scope and no listing request is made (docs/cr26-applicability.md). The rule would apply from the day a listing were sought." + }, + { + "frr_id": "SCG-CSO-AUP", + "status": "Implemented", + "implementation": "The certification package explains how to obtain and use the Secure Configuration Guide: the guide itself opens with obtain, use and change instructions (where it is, that it is public and signed, how to compare a system's values with it, and that the operator's own comparison is published at /.well-known/security-settings.json), and the policy index lists it with its URL. Every deploy builds it from data/secure-configuration.json (scripts/build-scg.py) and publishes it signed at https://samaydlette.com/.well-known/secure-configuration-guide.json and .md.", + "evidence": [ + { + "kind": "artifact", + "ref": ".well-known/secure-configuration-guide.json" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build the secure configuration guide (SCG, cryptographic modules)" + }, + { + "kind": "test", + "ref": "tests/test_secure_configuration.py::test_the_committed_guide_is_released_and_builds" + } + ] + }, + { + "frr_id": "SCG-CSO-PUB", + "status": "Implemented", + "implementation": "The Secure Configuration Guide is public, with no account or request: human-readable at https://samaydlette.com/.well-known/secure-configuration-guide.md and machine-readable at https://samaydlette.com/.well-known/secure-configuration-guide.json, signed with the deploy's keyless identity, rebuilt and republished on every deploy.", + "evidence": [ + { + "kind": "artifact", + "ref": ".well-known/secure-configuration-guide.json" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build the secure configuration guide (SCG, cryptographic modules)" + } + ] + }, + { + "frr_id": "SCG-CSO-RSC", + "status": "Implemented", + "implementation": "The Secure Configuration Guide (one source, data/secure-configuration.json; published at https://samaydlette.com/.well-known/secure-configuration-guide.md and .json) names each top-level administrative account (the AWS root user, the GitHub repository owner) and privileged account (the operator IAM user, the five CI roles, user-pool administration), says how each is named, and gives secure access, configuration, operation and decommissioning instructions for each. For every security setting it states who can operate it (root-only and owner-only settings marked), the recommended value and its security implication. It states the system as it is (virtual TOTP MFA on root and the operator user, an accepted finding, DEC-150); the build fails if the guide names a retired mechanism (the old shared app credential, a deployer access key, Duo-enforced root MFA).", + "evidence": [ + { + "kind": "artifact", + "ref": ".well-known/secure-configuration-guide.json" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build the secure configuration guide (SCG, cryptographic modules)" + }, + { + "kind": "test", + "ref": "tests/test_secure_configuration.py::test_the_committed_guide_is_released_and_builds" + }, + { + "kind": "test", + "ref": "tests/test_secure_configuration.py::test_a_guide_naming_a_retired_mechanism_fails_the_build" + }, + { + "kind": "test", + "ref": "tests/test_secure_configuration.py::test_the_policy_page_names_no_retired_mechanism" + } + ] + }, + { + "frr_id": "SCG-CSO-SDF", + "status": "Implemented", + "implementation": "Privileged accounts created by code start in their recommended state: the CI roles' trust policies (infrastructure/bootstrap) and the Silk Reeling user pool (MFA required, admin-created users only, 14-character passwords; infrastructure/cognito.tf). The accounts not created by code (the AWS root user, the GitHub owner, the operator IAM user) are read on every deploy and compared with the guide's defaults (scripts/check-secure-config.py); the deploy fails on any deviation no decision covers. The one deviation is the MFA type on root and the operator user: virtual TOTP rather than the phishing-resistant default, an accepted finding (DEC-150, extending DEC-025), published against that record in /.well-known/security-settings.json.", + "evidence": [ + { + "kind": "step", + "ref": "deploy-with-opa.yml#Compare live security settings with the secure configuration guide" + }, + { + "kind": "artifact", + "ref": ".well-known/security-settings.json" + }, + { + "kind": "decision", + "ref": "DEC-150" + }, + { + "kind": "test", + "ref": "tests/test_secure_configuration.py::test_mfa_deviation_is_the_accepted_finding" + }, + { + "kind": "test", + "ref": "tests/test_secure_configuration.py::test_a_matching_account_passes_with_mfa_as_the_accepted_deviation" + } + ] + }, + { + "frr_id": "SCG-ENH-API", + "status": "Implemented", + "implementation": "Every setting in the Secure Configuration Guide names the API or CLI call that reads it and the one that changes it (AWS IAM, S3 Control, Cognito and STS APIs; GitHub's REST API), and the deploy uses those read calls itself to compare the live settings. Changes go through Terraform or the repository settings in reviewed pull requests.", + "evidence": [ + { + "kind": "artifact", + "ref": ".well-known/secure-configuration-guide.json" + }, + { + "kind": "test", + "ref": "tests/test_secure_configuration.py::test_every_setting_says_how_to_read_and_change_it" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Compare live security settings with the secure configuration guide" + } + ] + }, + { + "frr_id": "SCG-ENH-CMP", + "status": "Implemented", + "implementation": "Every deploy reads the current settings of the top-level administrative and privileged accounts (root MFA and access keys, MFA type, account password policy, account-level S3 Block Public Access, other IAM users' permissions, the operator user's MFA, console password and access-key age, the CI roles' trust subjects, the user-pool sign-in policy, and the GitHub environment and branch settings) and compares each with the guide's recommended default (scripts/check-secure-config.py). A deviation no in-force decision covers, or a setting that cannot be read, fails the deploy before the SDR is built. The repository settings the workflow token can read (rulesets and their bypass actors, Dependabot alerts, Dependabot version updates, and every workflow's top-level token permissions) are compared on every deploy and every night (evidence-nightly.yml). The GitHub owner's two-factor setting and personal access tokens, which no token the pipeline holds can read, are a one-time configuration fact with no recurring review (DEC-151, amended). The comparison is published at /.well-known/security-settings.json and .md.", + "evidence": [ + { + "kind": "step", + "ref": "deploy-with-opa.yml#Compare live security settings with the secure configuration guide" + }, + { + "kind": "artifact", + "ref": ".well-known/security-settings.json" + }, + { + "kind": "test", + "ref": "tests/test_secure_configuration.py::test_the_known_bad_account_fails_the_deploy" + }, + { + "kind": "test", + "ref": "tests/test_secure_configuration.py::test_an_unreadable_setting_fails_the_deploy" + }, + { + "kind": "decision", + "ref": "DEC-151" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Compare repository settings with the secure configuration guide (SCG-ENH-CMP)" + }, + { + "kind": "test", + "ref": "tests/test_repo_settings.py::test_known_bad_a_workflow_without_permissions_or_with_write_all_is_a_deviation" + }, + { + "kind": "test", + "ref": "tests/test_repo_settings.py::test_the_committed_workflows_and_dependabot_match_the_guide" + } + ] + }, + { + "frr_id": "SCG-ENH-EXP", + "status": "Implemented", + "implementation": "Every deploy exports the current security settings of the top-level administrative and privileged accounts as signed JSON at /.well-known/security-settings.json (with a Markdown view): each setting's current value, recommended value and result. Values only: no account ID, ARN, IAM user or role name.", + "evidence": [ + { + "kind": "artifact", + "ref": ".well-known/security-settings.json" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Compare live security settings with the secure configuration guide" + }, + { + "kind": "test", + "ref": "tests/test_secure_configuration.py::test_the_export_carries_no_user_name_or_account_id" + } + ] + }, + { + "frr_id": "SCG-ENH-MRG", + "status": "Implemented", + "implementation": "The Secure Configuration Guide is machine-readable at https://samaydlette.com/.well-known/secure-configuration-guide.json: per setting, an ID, the account, who can operate it, the recommended value (literal or bound), the implication, the read and change calls and the check ID. The deploy's own comparison consumes it.", + "evidence": [ + { + "kind": "artifact", + "ref": ".well-known/secure-configuration-guide.json" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Compare live security settings with the secure configuration guide" + } + ] + }, + { + "frr_id": "SCG-ENH-VRH", + "status": "Implemented", + "implementation": "The recommended defaults carry a version and a release history (the guide's release_history). Each release records a digest of the defaults it fixes; the build fails when a default changes without a new version and a changelog entry carrying the new digest.", + "evidence": [ + { + "kind": "artifact", + "ref": ".well-known/secure-configuration-guide.json" + }, + { + "kind": "test", + "ref": "tests/test_secure_configuration.py::test_a_default_changed_without_a_release_fails_the_build" + }, + { + "kind": "test", + "ref": "tests/test_secure_configuration.py::test_a_release_with_a_new_digest_is_accepted" + } + ] + }, + { + "frr_id": "SCN-ADP-NTF", + "status": "Implemented", + "implementation": "Each adaptive record's notice, carrying its new-risks summary (required by the register), is due 10 business days after date_finished, counted with US federal holidays (scripts/_bizdays.py). It is given by publication in the certification data, the method FedRAMP's rules name; nothing is sent to FedRAMP or anyone else. Every deploy builds and publishes all notices (a build or publish failure fails the deploy, and the post-publish round-trip compares the served index and feed), and the index records each notice's deadline and the date it was first published. The scheduled SCN deadline check fails and raises an issue when a notice is unpublished past its deadline. History: the six adaptive notices were first published by the deploy that introduced this mechanism. SCN-2026-001, SCN-2026-002, SCN-2026-003, SCN-2026-004 and SCN-2026-005 were published after their deadlines (2026-06-22, 2026-07-07, 2026-07-23, 2026-10-09, 2026-10-13) and are marked late (onTime false, lateNotices). SCN-2026-006 (deadline 2026-11-10) is on time only if that deploy ran by its deadline; the published index records which.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_scn.py::test_adaptive_notice_is_due_ten_business_days_after_finishing" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_a_new_notice_is_dated_today_and_late_ones_say_so" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_an_unpublished_notice_is_overdue_until_a_deploy_publishes_it" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_the_published_outputs_are_listed_signed_and_governed" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build Significant Change Notifications and the evaluation log" + }, + { + "kind": "step", + "ref": "scn-deadlines.yml#Check SCN deadlines" + }, + { + "kind": "artifact", + "ref": ".well-known/significant-change-notifications.json" + } + ] + }, + { + "frr_id": "SCN-CSO-ARI", + "status": "Implemented", + "implementation": "Each published notification adds, beyond the required items, the change's status, initiation/finish/verification dates, the pull requests that made it, the new-risks summary, its notices with deadlines and publication dates, and a link to the full record (boundary change, impact by control family, verification result).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_scn.py::test_build_publishes_every_register_row_in_the_fedramp_schema" + }, + { + "kind": "artifact", + "ref": ".well-known/significant-change-notifications.json" + } + ], + "may_rationale": "Exercised. Change records add the boundary change, the security impact by control family and the verification result, so a reviewer can see why a change was classified as it was." + }, + { + "frr_id": "SCN-CSO-EMG", + "status": "Implemented", + "implementation": "docs/incident-response.md (Emergency-change procedure), linked from the Certification Package Overview: an emergency change carries SCN-Type emergency with its SCN-Record; the gate accepts it and states the record is due; the retroactive register row (emergency = yes) is due within 5 business days of the change merging, enforced by the scheduled SCN deadline check, and the published notification marks each retroactive notice against that deadline. Notification is publication. Not yet invoked.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_scn.py::test_an_emergency_change_owes_its_record_within_five_business_days" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_emergency_notices_are_retroactive_within_five_business_days" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_each_good_evaluation_passes" + }, + { + "kind": "step", + "ref": "scn-deadlines.yml#Check SCN deadlines" + } + ], + "may_rationale": "Kept available for emergencies: a security fix may need to ship before notice can be given. When it is used, the retroactive records the rule requires are produced within its timeframe." + }, + { + "frr_id": "SCN-CSO-EVA", + "status": "Implemented", + "implementation": "Every pull request (or direct push) must carry SCN-Type (not-significant, routine-recurring, adaptive, transformative, emergency, class-change), a one-line SCN-Rationale and, for adaptive/transformative/emergency, the SCN-Record that will document it; the required scn-tag check (scripts/scn-evaluate.py, rules in scripts/_scn.py) fails a change without them, with no default, and always fails class-change. A change named adaptive, transformative or emergency whose record is not in the register by its deadline fails the scheduled SCN deadline check. docs/scn/evaluation-examples.md gives one example per type (real for adaptive, fictitious otherwise), each checked against the gate. Changes merged before this gate mostly carry no evaluation; the evaluation log starts at the change that introduced it. SCN-2026-001's categorization (adaptive, at the upper edge, for a new external interconnection since removed by SCN-2026-006) is unchanged and left to the operator's review.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_scn.py::test_each_known_bad_evaluation_fails_for_its_reason" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_an_empty_description_fails_there_is_no_default" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_the_workflow_runs_the_tested_gate_with_no_default" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_every_type_has_a_documented_example" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_an_adaptive_change_with_no_record_is_overdue_after_ten_business_days" + }, + { + "kind": "step", + "ref": "scn-tag.yml#Validate the SCN evaluation" + } + ] + }, + { + "frr_id": "SCN-CSO-HIS", + "status": "Implemented", + "implementation": "Every notification is published with the certification data at /.well-known/significant-change-notifications.json (+ .md, Atom feed), listed in the Certification Package Overview, and never pruned: a deploy that would drop a published notification or re-date a notice fails (retention exceeds 12 months). The register rows are never deleted.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_scn.py::test_a_build_that_would_drop_a_published_notification_fails" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_a_published_notice_keeps_its_first_publication_date" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_the_cpo_lists_the_notification_mechanism" + }, + { + "kind": "artifact", + "ref": ".well-known/significant-change-notifications.json" + } + ] + }, + { + "frr_id": "SCN-CSO-HRM", + "status": "Implemented", + "implementation": "Notifications are published in JSON (FedRAMP SCN schema) and as a Markdown view; the related audit records (the evaluation log) likewise in JSON and Markdown. The index and the Certification Package Overview state that everything is public with no request needed, and how sharing is decided (everything is shared: no federal data, no agency customer).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_scn.py::test_build_publishes_every_register_row_in_the_fedramp_schema" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_the_log_appends_to_the_previous_published_version" + }, + { + "kind": "artifact", + "ref": ".well-known/significant-change-notifications.json" + }, + { + "kind": "artifact", + "ref": ".well-known/scn-evaluations.json" + } + ] + }, + { + "frr_id": "SCN-CSO-INF", + "status": "Implemented", + "implementation": "docs/scn/scn-register.csv carries the ten items for every record and scripts/_scn.py refuses a row missing one; each deploy writes every row as a notification in FedRAMP's SCN schema (scripts/build-scn.py via _fedramp_schema.write_validated) inside /.well-known/significant-change-notifications.json, with the security impact analysis linked. The Service Offering FedRAMP ID is published as not assigned, with the reason (the offering is not certified). SCN-2026-006's verification is recorded (2026-10-27). Older records' plans name artifacts since retired (the OSCAL SSP/POA&M); they describe the plan as it was.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_scn.py::test_build_publishes_every_register_row_in_the_fedramp_schema" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_the_committed_register_is_valid" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_each_known_bad_register_fails_for_its_reason" + }, + { + "kind": "artifact", + "ref": ".well-known/significant-change-notifications.json" + } + ] + }, + { + "frr_id": "SCN-CSO-MAR", + "status": "Implemented", + "implementation": "Each deploy appends the evaluation of every first-parent commit on main since the last entry (commit, merge date, pull request, SCN type, rationale, record, who merged it) to /.well-known/scn-evaluations.json (+ .md), signed with Sigstore and freshness-governed. The log is append-only against the previous published version: a build that would drop or rewrite an entry, or whose last entry has left main's history, fails. A change merged without a valid evaluation is logged with the problem, not skipped. The Certification Package Overview states how to obtain the records (public, no request needed). The log starts at the change that introduced it; earlier evaluations exist only for the six records in docs/scn.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_scn.py::test_the_log_appends_to_the_previous_published_version" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_the_append_only_check_fails_each_known_bad_log" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_collect_logs_every_first_parent_commit_from_the_builder_onward" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_collect_fails_when_the_last_logged_commit_left_history" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_the_cpo_lists_the_notification_mechanism" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build Significant Change Notifications and the evaluation log" + }, + { + "kind": "artifact", + "ref": ".well-known/scn-evaluations.json" + } + ] + }, + { + "frr_id": "SCN-CSO-NOM", + "status": "Implemented", + "implementation": "Mechanisms: an Atom feed (/.well-known/significant-change-notifications.atom, one entry per notice, subscribable with any feed reader), the signed JSON index and its Markdown view. They are listed, with how to obtain the evaluation records, in the Certification Package Overview's significant_change_notifications section. Notification is publication only, the method FedRAMP's rules name (an update to the Certification Data); nothing is sent to FedRAMP or anyone else.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_scn.py::test_the_cpo_lists_the_notification_mechanism" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_the_feed_is_atom_with_one_entry_per_notice" + }, + { + "kind": "artifact", + "ref": ".well-known/significant-change-notifications.atom" + } + ], + "may_rationale": "Exercised. Notice is given by a published, signed feed rather than email, because there are no agency customers to address; the mechanism is documented in the certification package." + }, + { + "frr_id": "SCN-RTR-NNR", + "status": "Implemented", + "implementation": "No formal notification for routine recurring changes: the register refuses a routine-recurring (or not-significant) row, and the evaluation gate refuses an SCN-Record on a routine-recurring or not-significant change.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_scn.py::test_each_known_bad_register_fails_for_its_reason" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_each_known_bad_evaluation_fails_for_its_reason" + } + ] + }, + { + "frr_id": "SCN-TRF-NAF", + "status": "Implemented", + "implementation": "date_finished adds the after-finish notice, due 5 business days later and published with the record's current information; the scheduled SCN deadline check fails while it is unpublished past the deadline. No transformative change has occurred.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_scn.py::test_transformative_notices_and_deadlines" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_transformative_notices_after_finish_and_verification_are_overdue_unpublished" + }, + { + "kind": "step", + "ref": "scn-deadlines.yml#Check SCN deadlines" + } + ] + }, + { + "frr_id": "SCN-TRF-NAV", + "status": "Implemented", + "implementation": "verified_on adds the after-verification notice, due 5 business days later; the register requires the new-risks summary and sar_reference (the assessment report, or why there is none) once verified_on is set; the scheduled SCN deadline check fails while the notice is unpublished past the deadline. No transformative change has occurred.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_scn.py::test_transformative_notices_and_deadlines" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_transformative_notices_after_finish_and_verification_are_overdue_unpublished" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_an_incomplete_transformative_row_names_every_template_field" + }, + { + "kind": "step", + "ref": "scn-deadlines.yml#Check SCN deadlines" + } + ] + }, + { + "frr_id": "SCN-TRF-NFP", + "status": "Implemented", + "implementation": "plan_final = yes publishes the final-plan notice, which carries the record's current information (every notice republishes all of it). The evaluation gate blocks the merge until it has been published at least 10 business days. No transformative change has occurred.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_scn.py::test_each_known_bad_evaluation_fails_for_its_reason" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_each_good_evaluation_passes" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_transformative_notices_and_deadlines" + }, + { + "kind": "step", + "ref": "scn-tag.yml#Validate the SCN evaluation" + } + ] + }, + { + "frr_id": "SCN-TRF-NIP", + "status": "Implemented", + "implementation": "A transformative record (docs/scn/TEMPLATE-transformative.md) requires its planned start and a summary of likely security impacts; its initial-plan notice is published with the next deploy and dated. The evaluation gate blocks the merge of the transformative change until the initial-plan notice has been published at least 30 business days (read from the published index; fails closed when the index cannot be read). No transformative change has occurred.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_scn.py::test_each_known_bad_evaluation_fails_for_its_reason" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_each_good_evaluation_passes" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_transformative_fails_closed_without_the_published_index" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_transformative_notices_and_deadlines" + }, + { + "kind": "step", + "ref": "scn-tag.yml#Validate the SCN evaluation" + } + ] + }, + { + "frr_id": "SCN-TRF-TPR", + "status": "Implemented", + "implementation": "A transformative record must state whether the change needs human validation (tpr_human_validation) and name the third-party assessor engaged or why none was (tpr_assessor_or_reason); the register refuses a transformative row without them, and the published notification carries both. No transformative change has occurred.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_scn.py::test_an_incomplete_transformative_row_names_every_template_field" + }, + { + "kind": "test", + "ref": "tests/test_scn.py::test_each_known_bad_register_fails_for_its_reason" + } + ] + }, + { + "frr_id": "SCN-TRF-UPD", + "status": "Implemented", + "implementation": "A finished transformative record must list the service documentation to update (docs_to_update) or say how it was determined none was needed; the published notification carries the 30-business-day deadline and docs_updated_on, and the scheduled SCN deadline check fails when the deadline passes without an update. No transformative change has occurred.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_scn.py::test_transformative_documentation_update_is_overdue_after_thirty_business_days" + }, + { + "kind": "step", + "ref": "scn-deadlines.yml#Check SCN deadlines" + } + ] + }, + { + "frr_id": "SDR-CSO-FRR", + "status": "Implemented", + "implementation": "data/frr-records.json holds one record per applicable rule (154, derived from the pinned corpus's applicability metadata); scripts/_frr.py fails the build on a missing or extra record, an Implemented record without evidence, or evidence that does not resolve. The published SDR carries every record in fedRampRequirements with its status, implementation, evidence and gap. Each rule's independent verification and validation (frrAssessment) is the simulated assessor's signed pre-deploy result for it, carried verbatim. The SDR states which commit and published KSI signal that assessment covered (providerExtensions.assessmentCoverage): the commit the SDR was built from, and the published state that commit replaced; a set covering anything else is refused. The post-deploy assessment of the just-published state runs after publish and fails the run on any failure. The human-readable form is the SDR's .md summary and its complete .view.md.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_sdr.py::test_every_applicable_rule_is_listed_once" + }, + { + "kind": "test", + "ref": "tests/test_sdr.py::test_an_invalid_record_set_never_reaches_the_sdr" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build Security Decision Record (SDR — 20x SSP replacement)" + }, + { + "kind": "artifact", + "ref": ".well-known/security-decision-record.json" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_the_deploy_needs_the_assessor_and_builds_the_sdr_from_its_set" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Download the simulated assessment" + }, + { + "kind": "artifact", + "ref": ".well-known/simulated-assessment.json" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_the_sdr_states_which_commit_and_signal_its_assessment_covered" + }, + { + "kind": "test", + "ref": "tests/test_simulated_assessor.py::test_the_deploy_binds_the_pre_deploy_set_to_this_commit_and_the_live_signal" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Bind the pre-deploy assessment to the state it covered" + } + ], + "simulated": { + "counterparty": "assessor", + "how": "Totally Real Assessment Services, LLC (simulated) is a reusable GitHub Actions workflow in this repository (simulated-assessor.yml) that runs twice on every deploy: before the SDR is built (the commit being deployed and the published state it replaces) and after publish (the just-published state, which must carry the deployed commit). Each run follows the provider's assessor guide, re-runs every cited test, checks every workflow step and decision, fetches and cosign-verifies every published artifact, and signs its results keylessly under its own workflow identity, which infrastructure/keys/assessor-identity.json pins; each signed set names the commit and KSI signal it covered. The run fails if the assessor finds a failure, if its signature does not verify against that identity, if a record was altered, or if the set covers any other commit or signal. It is not a FedRAMP Recognized assessment service and its set says so (fedramp_recognized: false); only the assessor is simulated, the mechanism is real." + } + }, + { + "frr_id": "SDR-CSO-MTD", + "status": "Implemented", + "implementation": "The SDR carries metadata.version, metadata.lastUpdated and metadata.updateSource in FedRAMP's schema. The version is semver: unchanged content keeps the previous version and a content change bumps it, judged by a sha256 of the content excluding metadata.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_sdr.py::test_version_starts_at_1_0_0_after_the_unversioned_record" + }, + { + "kind": "test", + "ref": "tests/test_sdr.py::test_unchanged_content_keeps_its_version_and_a_change_bumps_it" + }, + { + "kind": "test", + "ref": "tests/test_sdr.py::test_it_validates_against_fedramps_schema" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build Security Decision Record (SDR — 20x SSP replacement)" + }, + { + "kind": "artifact", + "ref": ".well-known/security-decision-record.json" + } + ] + }, + { + "frr_id": "SDR-CSX-KMT", + "status": "Implemented", + "implementation": "The SDR's daily metric data carries, for every KSI, its status, deploy-time validations and failures, automated methods and whether the runtime signal re-validated it, carried forward from the published SDR for up to a year; per KSI it summarizes the past 30 days and up to the past year. The unattended maintainer rebuilds the SDR daily, so there is a point for every day, not only deploy days.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_sdr_ksi_metrics.py::test_todays_point_carries_every_ksi" + }, + { + "kind": "test", + "ref": "tests/test_sdr_ksi_metrics.py::test_per_ksi_history_is_carried_forward_and_summarized_over_30_days_and_a_year" + }, + { + "kind": "test", + "ref": "tests/test_sdr_ksi_metrics.py::test_a_summary_counts_the_days_a_ksi_was_not_implemented" + }, + { + "kind": "step", + "ref": "package-maintenance.yml#Rebuild the SDR, OCR and CPO at the deployed commit" + }, + { + "kind": "artifact", + "ref": ".well-known/security-decision-record.json" + } + ] + }, + { + "frr_id": "SDR-CSX-KSI", + "status": "Implemented", + "implementation": "Each KSI in the SDR has its own statement, built from its own measures and results: the measures (OPA rules annotated to it) and their objective, or the reason there are none and the risk to customers; their cycle (every deploy against the plan, daily at runtime where re-validated); verification that the measures demonstrate the KSI (the annotation check) and that the automation is accurate (the rules' own tests with a coverage floor and the CLI/Wasm parity test), or that the reason for no measure is not accepted; and validation that they are in place (this deploy's validations and failures, the runtime re-validation).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_sdr_ksi_metrics.py::test_each_ksi_states_its_own_measures_cycle_and_validation" + }, + { + "kind": "test", + "ref": "tests/test_sdr_ksi_metrics.py::test_a_ksi_without_a_measure_says_why_and_the_risk" + }, + { + "kind": "test", + "ref": "tests/test_sdr_ksi_metrics.py::test_no_two_ksis_share_the_same_statement" + }, + { + "kind": "test", + "ref": "tests/test_sdr.py::test_every_ksi_is_listed_with_tests_and_evidence" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build Security Decision Record (SDR — 20x SSP replacement)" + }, + { + "kind": "artifact", + "ref": ".well-known/security-decision-record.json" + } + ] + }, + { + "frr_id": "VDR-CSO-ADT", + "status": "Implemented", + "implementation": "Automated on schedules and triggers: evidence-nightly.yml (cron '17 7 * * *' and '17 19 * * *', plus once after every successful deploy), deploy-with-opa.yml (every push to main, behind the prod approval), zap-dast.yml (daily, cron '23 7 * * *', plus after every successful deploy to main), the runtime emitter on its EventBridge schedule (aws_cloudwatch_event_rule.opa_compliance in infrastructure/main.tf, rate(1 day) from var.compliance_check_schedule) and the evidence watchdog (aws_cloudwatch_event_rule.evidence_watchdog in infrastructure/watchdog.tf, rate(1 hour)). Detection, evaluation (policies/triage.rego via OPA), gating, signing and publication are all automated; the nightly publishes its outcome on every run in vdr-status.json.", + "evidence": [ + { + "kind": "step", + "ref": "deploy-with-opa.yml#Detection gate (G7)" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Vulnerability gate (fix or categorize every vuln)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-status.json" + } + ] + }, + { + "frr_id": "VDR-CSO-AKE", + "status": "Implemented", + "implementation": "scripts/kev-gate.py runs in the deploy after the detection gate and before the Terraform plan, apply and website sync: it intersects every Grype scan (Python, JS, the Lambda package, a11y tooling) and the open Dependabot alerts with the CISA KEV catalog and stops the deploy on any match, naming the catalog due date, under the governed mode of G1's check vdr.kev (block). A missing or unreadable input stops it. G1 in the VDR build still blocks any KEV finding afterwards.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_kev.py::test_a_kev_in_a_grype_scan_stops_the_deploy_with_its_due_date" + }, + { + "kind": "test", + "ref": "tests/test_kev.py::test_a_kev_in_a_dependabot_alert_stops_the_deploy" + }, + { + "kind": "test", + "ref": "tests/test_kev.py::test_a_missing_input_stops_the_kev_gate" + }, + { + "kind": "test", + "ref": "tests/test_kev.py::test_the_kev_gate_runs_before_anything_is_activated" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#KEV gate before apply (VDR-CSO-AKE)" + } + ] + }, + { + "frr_id": "VDR-CSO-DAC", + "status": "Implemented", + "implementation": "Every change is scanned when it lands: the deploy runs IaC static analysis (Checkov, tfsec), Grype over every dependency tree and the KEV gate before apply, and the detection gate (G7) requires fresh CodeQL and DAST results; CodeQL (.github/workflows/codeql.yml) analyzes this repository's code and the Silk Reeling application on push and after each deploy; the ZAP baseline scan of the site and the authenticated ZAP scan of the Silk Reeling API (a dedicated Cognito scanner user, credentials in repository secrets, the deploy fails when they are missing) run after each successful deploy.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_detect_wiring.py::test_codeql_runs_on_change_after_deploy_and_daily" + }, + { + "kind": "test", + "ref": "tests/test_detect_wiring.py::test_zap_runs_at_least_every_three_days_and_after_each_deploy" + }, + { + "kind": "test", + "ref": "tests/test_detect_wiring.py::test_publishers_fetch_gate_and_build_with_codeql_and_the_api_scan[deploy-with-opa.yml-deploy]" + }, + { + "kind": "step", + "ref": "codeql.yml#Analyze" + }, + { + "kind": "step", + "ref": "zap-dast.yml#ZAP API Scan (authenticated)" + }, + { + "kind": "step", + "ref": "zap-dast.yml#ZAP Baseline Scan" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Detection gate (G7)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-report.json" + } + ] + }, + { + "frr_id": "VDR-CSO-DET", + "status": "Implemented", + "implementation": "Detection uses scanning (Grype over every dependency tree and Dependabot, twice daily; Checkov and tfsec over all Terraform; CodeQL over this repository and the Silk Reeling application; the ZAP site scan and an authenticated ZAP scan of the Silk Reeling API, daily and after each deploy), threat intelligence (CISA KEV, FIRST EPSS), a vulnerability disclosure mechanism (/.well-known/security.txt), automated control testing (the OPA plan gate, reconciliation --live) and supply-chain monitoring (Dependabot, package integrity at runtime). Persistent verification and validation: every machine component re-validated live daily (VDR-TFR-MVX) and non-machine resources on every deploy and every night (VDR-TFR-NMV). The detection gate (G7) fails the run when a feed is missing or stale, coverage is published per component (VDR-TFR-PCD) and gaps become process findings (VDR-CSO-FAV). No penetration test or cloud-native threat detection service is used; the rule lists these as examples, not requirements.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_detect_wiring.py::test_api_scan_is_authenticated_and_never_prints_the_token" + }, + { + "kind": "test", + "ref": "tests/test_detect_wiring.py::test_codeql_covers_this_repos_code_and_the_silk_reeling_app" + }, + { + "kind": "test", + "ref": "tests/test_codeql_zap_api_ingest.py::test_codeql_finding_is_published_in_the_report" + }, + { + "kind": "test", + "ref": "tests/test_reconcile_runtime_vv.py::test_known_bad_fixture_fails_every_way" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_known_bad_components_no_technique_reached_this_month_are_uncovered" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Detection gate (G7)" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Detection gate (G7)" + }, + { + "kind": "step", + "ref": "zap-dast.yml#ZAP API Scan (authenticated)" + }, + { + "kind": "step", + "ref": "codeql.yml#Analyze" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-report.json" + } + ] + }, + { + "frr_id": "VDR-CSO-DFR", + "status": "Implemented", + "implementation": "Architecture: static content on private S3 behind CloudFront (infrastructure/main.tf, infrastructure/bootstrap/cloudfront.tf), serverless Silk Reeling (API Gateway -> Lambda, Cognito-gated; infrastructure/silk-reeling.tf, cognito.tf); no servers or operating systems to patch, so detection is SCA, IaC analysis, DAST and CodeQL, with no host scanning; all infrastructure is Terraform, gated by OPA at plan time (deploy-with-opa.yml 'Run OPA Compliance Check'), and the same Rego re-validates the deployed system as Wasm (the policy parity test, and the runtime readers for every machine type). The published inventory (ksi-signal.json) has no compute instances or containers. The residual risks this design leaves are accepted separately and are not evidence for this rule (DEC-007 WAF, DEC-009 origin failover, DEC-026 operator IAM privileges).", + "evidence": [ + { + "kind": "step", + "ref": "deploy-with-opa.yml#Run OPA Compliance Check" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Policy parity test (CLI vs Wasm)" + }, + { + "kind": "test", + "ref": "tests/test_validation_mapping.py::test_every_plan_validated_type_has_a_rule" + }, + { + "kind": "test", + "ref": "tests/test_runtime_readers.py::test_every_machine_type_has_a_reader_or_existing_check" + }, + { + "kind": "artifact", + "ref": ".well-known/ksi-signal.json" + } + ] + }, + { + "frr_id": "VDR-CSO-FAV", + "status": "Implemented", + "implementation": "A detect-and-recover failure recorded in the run (e.g. runtime-divergence.observer-fault), a detection coverage gap (vdr.coverage), a finding that resolves to no component (vdr.unresolved-component) and a finding still on a default after the VER-TFR-EVU window each become a VDR finding with source 'process': tracking ID, clock from the failure, rating (severity proxy N2), Class C deadline, disposition and VDT record, remediated when the check passes. A block-mode failure stops the run (and the deploy opens an issue); each stopped run of the deploy, nightly or ZAP workflow on main is listed in the next report's process_failures with its times, from the 'Collect failed pipeline runs' step. scripts/build-vdr-report.py with scripts/_evaluation.py.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_a_detect_and_recover_event_becomes_one_process_finding_per_check" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_a_finding_on_a_default_past_the_window_becomes_a_process_finding" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_an_unresolved_finding_becomes_a_process_finding_in_the_build" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_stopped_runs_on_main_since_the_previous_report_are_listed_without_ids" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_the_deploy_and_nightly_pass_failed_runs_to_the_vdr_build" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Collect failed pipeline runs (VDR-CSO-FAV)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Collect failed pipeline runs (VDR-CSO-FAV)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-report.json" + } + ] + }, + { + "frr_id": "VDR-CSO-MSP", + "status": "Implemented", + "implementation": "security/zap/allowlist.json has no entries: no edge allowlist exists for the scanner, and the VDR builder flags any DAST finding observed only at allowlisted URLs (scripts/build-vdr-report.py load_zap_allowlist and _zap_location, REQ-IRV-11). The nightly's AWS access for the reconciliation sweep is read-only (infrastructure/bootstrap/evidence-nightly.tf, policy document evidence_nightly_reconcile_reads: List, Describe and GET calls only; the audit-log review's separate grant, evidence_nightly_audit_reads, is cloudtrail:LookupEvents only). ZAP runs two scans of production (zap-dast.yml): an unauthenticated baseline of the site, as a stranger sees it, and an authenticated scan of the Silk Reeling API signed in as a dedicated, standing Cognito scanner user. That user is an ordinary user of the pool, created like every other user and holding the TOTP MFA the pool requires; it signs in with the flows the app client already allows (scripts/dast-cognito-token.py, docs/runbooks/dast-scanner-user.md). No app-client flow, authorizer or edge control was widened, disabled or opened for scanning.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_zap_allowlist.py::test_allowlist_entry_without_a_decision_fails_closed" + }, + { + "kind": "test", + "ref": "tests/test_zap_allowlist.py::test_allowlist_status_is_published_in_the_report" + } + ] + }, + { + "frr_id": "VDR-CSO-RES", + "status": "Implemented", + "implementation": "Each VDR build tracks every finding through the ledger (detection, evaluation, clock, rating history), evaluates it in policies/triage.rego (IRV, LEV, PAIN, group, deadline, acceptance, blocking), verifies mitigations against the signed runtime signal, forces fix-or-decide (vuln-gate.py, decision register) and reports it (VDR, VDT, AVI, MRH, monthly report). Exploitation is assessed per finding under DEC-181: evaluation.exploitation is active when the source reports it or an incident record names the finding or its CVE, otherwise none observed, with its basis and time; exploitation elsewhere is read from KEV and EPSS. No person reviews logs for this assessment (DEC-181).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_an_incident_naming_the_finding_makes_exploitation_active" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_the_policies_named_are_in_force_in_the_register" + }, + { + "kind": "test", + "ref": "tests/test_triage_policy.py::test_golden_report_is_unchanged" + }, + { + "kind": "decision", + "ref": "DEC-181" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-report.json" + } + ] + }, + { + "frr_id": "VDR-CSO-SIR", + "status": "Not Applicable", + "implementation": "Checked: no sampling is used. Grype scans every SBOM'd dependency tree, Checkov/tfsec scan all Terraform, and the runtime emitter validates every machine component individually, one validation per component, across the 20 machine types in infrastructure/schemas/runtime-vv-config.json (VDR-TFR-MVX).", + "evidence": [], + "not_applicable": "A MAY permission that is not exercised; see the rationale.", + "may_rationale": "Not exercised. Every resource is scanned individually; the inventory is small and sampling would reduce assurance for no gain." + }, + { + "frr_id": "VDR-TFR-KEV", + "status": "Implemented", + "implementation": "The VDR keeps each KEV entry's dueDate and dateAdded: a KEV finding's remediation deadline is the earlier of the Class C deadline and the catalog's due date, even when fully mitigated, and it is overdue once the catalog date passes; kev_due_at, kev_date_added and kev_overdue are published per finding and in the VDT's providerExtensions (kevDueAt, kevDateAdded, kevOverdue). A KEV blocks before activation (VDR-CSO-AKE) and in the VDR build (G1).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_kev.py::test_the_catalog_due_date_is_kept_and_bounds_the_deadline" + }, + { + "kind": "test", + "ref": "tests/test_kev.py::test_the_vdt_names_the_kev_due_date" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-report.json" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-detail-report.json" + } + ] + }, + { + "frr_id": "VDR-TFR-MVX", + "status": "Implemented", + "implementation": "The runtime emitter (infrastructure/lambda, daily, signed with a KMS ECDSA key) re-validates every machine-based component live against the same gate policy the deploy enforces: live readers for each of the 20 machine types in infrastructure/schemas/runtime-vv-config.json (IAM roles, groups and the OIDC provider, Lambda, API Gateway, Cognito, KMS, log groups, SNS, SQS, alarms, rules, CloudTrail, DynamoDB, Route 53, ACM, S3, CloudFront), with read-only grants scoped by ARN. Reconciliation invariant (n) in the nightly fails closed unless every machine component was validated by a verified runtime run within 72 hours (Class C: 3 days); a denied read is unassessed, never a pass. Packages, static content and external services are excluded with their reasons (scans, content hashing, outside the boundary).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_reconcile_runtime_vv.py::test_known_bad_fixture_fails_every_way" + }, + { + "kind": "test", + "ref": "tests/test_reconcile_runtime_vv.py::test_unverified_or_stale_signal_fails" + }, + { + "kind": "test", + "ref": "tests/test_reconcile_runtime_vv.py::test_missing_runtime_signal_fails_main" + }, + { + "kind": "test", + "ref": "tests/test_reconcile_runtime_vv.py::test_every_live_inventory_type_is_classified" + }, + { + "kind": "test", + "ref": "tests/test_runtime_readers.py::test_every_machine_type_has_a_reader_or_existing_check" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Reconciliation gate (fail closed on drift)" + }, + { + "kind": "artifact", + "ref": ".well-known/ksi-signal-runtime.json" + } + ] + }, + { + "frr_id": "VDR-TFR-NMV", + "status": "Implemented", + "implementation": "data/non-machine-resources.json registers every non-machine resource (policies and standards, runbooks, procedures, incident response, recovery, the continuous monitoring plan, the operator role and training record, rules of behavior, supply chain and significant change procedures, the PTA, the security review record, the decision register and the governance registry). Nobody verifies them by hand: scripts/_nonmachine.py runs machine checks on each (the file exists; every repository path and DEC ID it cites resolves; it names no retired mechanism such as the POA&M, the SSP or Basic Auth; every tagged count matches the code; a register validates). scripts/check-non-machine-vv.py runs them on every deploy, failing it, and every night, publishing the record (.well-known/vdr-non-machine-vv.json): verifiedAt is the run's time when everything passes and the epoch when anything fails, so the 26-hour freshness window the watchdog reads turns red at once. A policy, runbook or procedure without an entry fails too.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_non_machine_vv.py::test_every_committed_resource_passes_its_machine_checks" + }, + { + "kind": "test", + "ref": "tests/test_non_machine_vv.py::test_the_register_lists_every_policy_runbook_and_procedure" + }, + { + "kind": "test", + "ref": "tests/test_non_machine_vv.py::test_known_bad_documents_fail_for_their_reason" + }, + { + "kind": "test", + "ref": "tests/test_non_machine_vv.py::test_enforce_fails_on_a_failing_check_and_writes_the_status" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Non-machine verification and validation (VDR-TFR-NMV)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Non-machine verification and validation status (VDR-TFR-NMV)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-non-machine-vv.json" + } + ] + }, + { + "frr_id": "VDR-TFR-PCD", + "status": "Implemented", + "implementation": "The VDR publishes coverage: each inventory component, the detection techniques that reach it (IaC SAST for every Terraform resource, SCA for every package and function, the ZAP site scan for every page, the authenticated API scan and CodeQL for the API and functions) and when each last ran. A component no technique reached in a month is recorded as vdr.coverage and becomes a process finding (VDR-CSO-FAV). The 11 external services the inventory declares (the ext:: components from scripts/build-ksi-signal.py build_external_components) are listed as the third party's to detect. Non-machine resources are verified on every deploy and every night (VDR-TFR-NMV).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_known_bad_components_no_technique_reached_this_month_are_uncovered" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_a_fresh_feed_covers_its_components" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_coverage_and_unresolved_components_are_governed_detect_and_recover_checks" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-report.json" + } + ] + }, + { + "frr_id": "VDR-TFR-PDD", + "status": "Implemented", + "implementation": "infrastructure/schemas/runtime-vv-config.json marks each machine type likely_to_drift or not, with the reason, and sets drift_window_days 14. Every machine type, drifting or not, is re-validated live daily by the runtime emitter, and invariant (n) fails the nightly when any machine component goes 72 hours without a verified run; dependency trees are scanned twice daily and IaC on every change. A config that would weaken the window is rejected.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_reconcile_runtime_vv.py::test_config_that_would_weaken_the_gate_is_rejected" + }, + { + "kind": "test", + "ref": "tests/test_reconcile_runtime_vv.py::test_known_bad_fixture_fails_every_way" + }, + { + "kind": "test", + "ref": "tests/test_runtime_readers.py::test_every_drift_is_caught_by_the_gate_rule" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Reconciliation gate (fail closed on drift)" + }, + { + "kind": "artifact", + "ref": ".well-known/ksi-signal-runtime.json" + } + ] + }, + { + "frr_id": "VDR-TFR-PSD", + "status": "Implemented", + "implementation": "Similar machine-based resources are sampled well inside 3 days: the runtime emitter re-validates every machine component daily (not a sample: all of them), invariant (n) enforces 72 hours; CodeQL and the authenticated ZAP API scan run daily and after each deploy and the detection gate fails the run when either is older than 72 hours; the ZAP site scan is held to 3 days (--zap-max-age-days 3, fractional days).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_detection_gate.py::test_codeql_and_zap_api_windows_are_the_class_c_three_days" + }, + { + "kind": "test", + "ref": "tests/test_detect_wiring.py::test_zap_runs_at_least_every_three_days_and_after_each_deploy" + }, + { + "kind": "test", + "ref": "tests/test_runtime_readers.py::test_every_drift_is_caught_by_the_gate_rule" + }, + { + "kind": "test", + "ref": "tests/test_runtime_readers.py::test_denied_reads_are_unassessed_not_findings" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_zap_age_is_not_floored_to_whole_days" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Detection gate (G7)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Reconciliation gate (fail closed on drift)" + }, + { + "kind": "artifact", + "ref": ".well-known/ksi-signal-runtime.json" + } + ] + }, + { + "frr_id": "VDR-TFR-PVR", + "status": "Implemented", + "implementation": "policies/triage.rego timeframe() reads the Class C matrix from the pinned FedRAMP rules (data.rules ... VDR-TFR-PVR.varies_by_class.c, hash-checked by scripts/_rules.py) by PAIN x IRV x LEV; the deadline runs from the finding's clock start (triage.rego deadline(), item.clock.start_ns), which only a verified mitigation moves (scripts/build-vdr-report.py clock_facts()); re-evaluation re-selects the timeframe; G3 'vdr.past-deadline' blocks publication (gate-modes.json mode block); likely-overdue margin (vdr-pain-config.json). The published vdr-report.json carries remediation_due_at per finding.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_triage_policy.py::test_timeframe_comes_from_data_rules" + }, + { + "kind": "test", + "ref": "tests/test_triage_policy.py::test_rules_missing_a_timeframe_cell_fail_closed" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-report.json" + } + ] + }, + { + "frr_id": "VDR-TFR-RMN", + "status": "Implemented", + "implementation": "N1 findings get no timeframe (policies/triage.rego timeframe(): 'null for a level with no timeframe (N1: routine operations)'), yet scripts/vuln-gate.py and reconcile.py invariant (h) still need every finding fixed or dispositioned by an in-force decision with review_by. Both N1 findings (tfsec-AVD-AWS-0162, zap-10036-2) carry decisions DEC-032/DEC-040.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_rules_as_data.py::test_t19_n1_has_no_timeframe" + }, + { + "kind": "test", + "ref": "tests/test_vuln_gate.py::test_remediate_disposition_does_not_pass" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Vulnerability gate (fix or categorize every vuln)" + }, + { + "kind": "decision", + "ref": "DEC-040" + } + ] + }, + { + "frr_id": "VER-EVA-AIA", + "status": "Implemented", + "implementation": "Every finding's evaluation record carries automatable (VER-EVA-AIA): yes by default; no only from a decision record carrying the evidence (decisions.schema.json 'automatable', and _decisions.py refuses 'no' without evidence) or a CVSS 4.0 AU:N. Figure 7's floor reads the vector as the automatable proxy, and a finding with no prediction score is LEV, as the method states; an EPSS score below the governed threshold (published with its rationale, REQ-LEV-2) is the method's evidence for NLEV.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_automatable_by_default" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_only_a_decision_with_evidence_says_not_automatable" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_cvss4_automatable_is_read" + }, + { + "kind": "test", + "ref": "tests/test_decisions.py::test_each_known_bad_register_fails_closed_for_its_reason[automatable-no-evidence.json-'no' needs its evidence]" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-report.json" + } + ] + }, + { + "frr_id": "VER-EVA-EFA", + "status": "Implemented", + "implementation": "Each finding carries an evaluation record with every factor VER-EVA-EFA names, each with its basis: criticality (the component's classification, which PAIN is computed from), reachability (IRV and basis), exploitability (LEV and basis), detectability (outside-in, public advisory, public source), prevalence (findings and components in its group, share of the inventory), privilege (CVSS PR/S and identity or key components), proximate vulnerabilities (other findings and verified mitigations on the component, read with the group) and known threats (KEV, EPSS). The VDR methodology publishes what each factor means (methodology.evaluation_factors). The factors are recorded, not fed into the global impact tables (REQ-PAI-4); grouping feeds the policy.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_triage_policy.py::test_golden_report_is_unchanged" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_group_is_evaluated_at_its_most_exposed_open_member" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-report.json" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-detail-report.json" + } + ] + }, + { + "frr_id": "VER-EVA-EFP", + "status": "Implemented", + "implementation": "False-positive is a governed disposition: decision records with justification, decided_by/on, review_by (data/decisions.json: 14 in-force false-positive records, e.g. DEC-039 ZAP 10099 'pattern matched prose', DEC-040 'Server: AmazonS3 carries no version', DEC-193 CodeQL on the SRP sign-in); policies/triage.rego record_status() rejects a false positive that names a control (it must be 'mitigated') and lapses it at review_by; every VDR finding whose final disposition is false-positive carries its decision_id.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_dispositions_mitigations.py::test_t15_false_positive_naming_a_control_is_refused" + }, + { + "kind": "test", + "ref": "tests/test_vuln_gate.py::test_false_positive_passes" + }, + { + "kind": "decision", + "ref": "DEC-039" + }, + { + "kind": "decision", + "ref": "DEC-040" + } + ] + }, + { + "frr_id": "VER-EVA-EIR", + "status": "Implemented", + "implementation": "policies/triage.rego decides IRV from an outside-in observation, the resolved inventory component's declared internet_reachable, or a verified not-reachable mitigation, with irv_basis per finding. Suppressions resolve to the resources their decision names, a site-root DAST finding resolves to its page, and a finding that still resolves to no component is rated at the method's fail-safe (IRV) and recorded as vdr.unresolved-component, a process finding with a deadline until it resolves.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_resolution_identity.py::test_t7_unresolved_finding_is_irv_failsafe_and_flagged" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_a_site_root_resolves_to_its_index_page" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_an_unresolved_finding_becomes_a_process_finding_in_the_build" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-report.json" + } + ] + }, + { + "frr_id": "VER-EVA-ELX", + "status": "Implemented", + "implementation": "Figure 7 in policies/triage.rego, first match deciding, with lev_basis per finding. Configuration checks carry no CVE, so each recurring check has a governed CVSS vector (infrastructure/schemas/check-vectors.json) adopted by decision record DEC-180; a decided vector whose record is not in force stops the build. The vector drives the floor and the no-direct-impact rule, so LEV reflects what exploiting the misconfiguration needs in this system; DAST findings are evaluated by their decision records (DEC-039, DEC-040); anything unevaluated keeps the default (LEV).", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_figure7_lev.py::test_in_force_vector_is_applied_and_drives_lev_and_pain" + }, + { + "kind": "test", + "ref": "tests/test_figure7_lev.py::test_known_bad_decided_vector_without_a_decision_record_fails_closed" + }, + { + "kind": "test", + "ref": "tests/test_figure7_lev.py::test_the_committed_vectors_are_in_force_through_their_decision" + }, + { + "kind": "decision", + "ref": "DEC-180" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-report.json" + } + ] + }, + { + "frr_id": "VER-EVA-EPA", + "status": "Implemented", + "implementation": "PAIN is computed by the CVSS-Environmental derivation from the vector (the advisory's, or the governed check vector adopted by DEC-180) and the component's classification, onto the rules' scale; a fully mitigated finding takes N0, read from VER-EVA-EPA in the rules. Each finding states its likely agency effect and what the rating rests on (impact_rationale), which the VDT carries as potentialAgencyImpact.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_fully_mitigated_takes_n0_from_the_rules_scale" + }, + { + "kind": "test", + "ref": "tests/test_dispositions_mitigations.py::test_t15_control_protected_finding_is_fully_mitigated_at_the_lowest_level" + }, + { + "kind": "test", + "ref": "tests/test_figure7_lev.py::test_the_committed_vectors_are_in_force_through_their_decision" + }, + { + "kind": "decision", + "ref": "DEC-180" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build CR26 vulnerability reports (VDT, AVI, history)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-report.json" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-detail-report.json" + } + ] + }, + { + "frr_id": "VER-EVA-GRV", + "status": "Implemented", + "implementation": "Each finding belongs to a group: its CVE, else the decision record that decided it, else its check. policies/triage.rego evaluates the group at its most exposed open member (highest PAIN, LEV or IRV if any member is) with the clock of its earliest member, and the group's deadline binds every open member, so a new instance of an old group does not get a new clock. The VDR publishes groups[] (members, components, rating, deadline) and each finding's group; the VDT carries groupId and groupDueAt.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_known_bad_new_instance_of_an_old_group_is_on_the_groups_clock_and_blocks" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_group_is_evaluated_at_its_most_exposed_open_member" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_a_closed_member_does_not_set_the_groups_rating" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_group_keys" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-report.json" + } + ] + }, + { + "frr_id": "VER-RPT-AVI", + "status": "Implemented", + "implementation": "vdr-accepted-vulnerabilities.json and .md under /.well-known/ (scripts/build-cr26-vdr.py): each accepted vulnerability's detail and acceptance rationale from its decision record (the build fails if a rationale is missing), supplementary information from the decision, and its detection time. A .checkov.yaml suppression resolves to the resources its decision names, so its IRV is decided from the inventory: DEC-010 (CKV_AWS_117) names the three Lambda components it covers and resolves; DEC-007, DEC-009 and DEC-010 record their original detection date (2025-06-14, from git history; AI-drafted for Sam's confirmation). Early acceptance (VER-TFR-MAV 'will not be') is included with its basis.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_cr26_vdr.py::test_outputs_validate_and_name_their_schema" + }, + { + "kind": "test", + "ref": "tests/test_decisions.py::test_the_post_migration_amendments_are_the_stated_ones" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build CR26 vulnerability reports (VDT, AVI, history)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Build and sign CR26 vulnerability reports (VDT, AVI, history)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-accepted-vulnerabilities.json" + }, + { + "kind": "decision", + "ref": "DEC-010" + } + ] + }, + { + "frr_id": "VER-RPT-HLO", + "status": "Implemented", + "implementation": "scripts/build-vdr-monthly.py publishes .well-known/vdr-monthly.json and .md for the calendar month to date (and the last 12 finished months): an overview of every activity type (software composition analysis, IaC static analysis, CodeQL, the ZAP site scan and the authenticated API scan, KEV and EPSS feeds, runtime verification, non-machine V&V, the vulnerability disclosure program, bug bounty, penetration testing and assessments), each with its runs and counts or an explicit 'none this period'. Activities outside the pipeline come from data/vdr-activities.json, which the operator records (seeded with the 2026-05-08 self-assessment and the 2026-10-26/27 manual ZAP scans). The VDT and AVI also carry the period's activity summary.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_vdr_monthly.py::test_every_activity_type_is_stated_with_none_this_period_when_quiet" + }, + { + "kind": "test", + "ref": "tests/test_vdr_monthly.py::test_the_period_is_the_calendar_month_to_date" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build monthly VDR activity report (VER-TFR-MHR)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Build monthly VDR activity report (VER-TFR-MHR)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-monthly.json" + } + ] + }, + { + "frr_id": "VER-RPT-NID", + "status": "Implemented", + "implementation": "Disclosure policy DEC-182: each finding carries public_disclosure (full or summary, with reason). An open finding that is IRV, LEV and N3 or above is published in summary until remediated, fully mitigated or dispositioned: ID, ratings, dates, deadline and status stay public (sufficient for a risk-based decision); description, observed locations, fixed versions and supplementary detail are withheld from the VDR and every report built from it. The path by which a necessary party would receive the withheld detail is exercised on every VDR build against a simulated requester (vdr-report.json withheld_detail_exercise): it logs, per withheld finding, the field names and a sha256 of the detail, never the detail, and a canned simulated finding keeps the path running when nothing is withheld. No real party receives anything (DEC-194). All published artifacts also pass the account-ID redaction gate.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_open_irv_lev_n3_is_summarized_and_redacted" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_dispositioned_or_lower_rated_findings_are_disclosed_in_full" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_the_policies_named_are_in_force_in_the_register" + }, + { + "kind": "decision", + "ref": "DEC-182" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-report.json" + }, + { + "kind": "test", + "ref": "tests/test_vdr_disclosure_exercise.py::test_a_withheld_finding_is_logged_without_its_detail" + }, + { + "kind": "test", + "ref": "tests/test_vdr_disclosure_exercise.py::test_known_bad_a_disclosure_rule_that_stops_withholding_fails_the_exercise" + } + ], + "simulated": { + "counterparty": "personnel", + "how": "The necessary party is simulated ('Necessary Party, Esq. (simulated)'); its request for the withheld detail runs on every VDR build and is answered with a log entry only (DEC-194)." + } + }, + { + "frr_id": "VER-RPT-PER", + "status": "Implemented", + "implementation": "Reports are refreshed by every deploy and twice-daily nightly and each summarizes all activity since the previous report: the VDT and AVI carry providerExtensions.activitySummary for their period (detections, evaluations, rating changes, reductions, records no longer reported, remediations, decisions, every scan and feed run), and the monthly report covers the month. Runtime V&V runs are all counted: the emitter signs a bounded run history into its signal, carried forward only from a previous signal that verifies, and the VDR passes it to the period reports. Activities outside the pipeline (VDP reports, penetration tests, assessments) come from data/vdr-activities.json, with 'none this period' when none.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_cr26_vdr.py::test_each_period_report_summarizes_the_periods_activity" + }, + { + "kind": "test", + "ref": "tests/test_cr26_vdr.py::test_every_retained_runtime_run_in_the_period_is_counted" + }, + { + "kind": "test", + "ref": "tests/test_vdr_monthly.py::test_the_signed_run_history_the_vdr_carries_is_counted" + }, + { + "kind": "test", + "ref": "tests/test_runtime_history.py::test_tampered_previous_restarts_history" + }, + { + "kind": "test", + "ref": "tests/test_runtime_history.py::test_history_is_bounded_keeping_the_newest" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build CR26 vulnerability reports (VDT, AVI, history)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Build and sign CR26 vulnerability reports (VDT, AVI, history)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Build monthly VDR activity report (VER-TFR-MHR)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-detail-report.json" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-monthly.json" + } + ] + }, + { + "frr_id": "VER-RPT-RPD", + "status": "Implemented", + "implementation": "The provider discloses its vulnerability reports publicly and records, per finding, the determination that doing so will not likely lead to exploitation (public_disclosure, under policy DEC-182); a finding where it would is published in summary until it is not.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_open_irv_lev_n3_is_summarized_and_redacted" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_dispositioned_or_lower_rated_findings_are_disclosed_in_full" + }, + { + "kind": "decision", + "ref": "DEC-182" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-report.json" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-detail-report.json" + } + ], + "may_rationale": "Exercised. Vulnerability reports are public to demonstrate the method; detail that could enable exploitation is withheld by a recorded disclosure policy until remediation." + }, + { + "frr_id": "VER-RPT-VDT", + "status": "Implemented", + "implementation": "vdr-detail-report.json and .md under /.well-known/ (scripts/build-cr26-vdr.py), validated against the vendored VDT schema before writing: tracking ID; detection time (the earliest evidence: the scanner's first report, or the original_detection_date of a decision naming that record, e.g. DEC-039/040 for the manual ZAP scans) and source; evaluation time; IRV; LEV; current rating, with the historical rating and full rating history under providerExtensions (the schema has no field for them); PAIN reductions; projected next reduction from the decision's planned_reduction, else the remediation deadline; overdue status whose explanation explains the overdue status (and likely-to-become-overdue); supplementary information from the decision (justification, dates, resources, plan, mitigation); final disposition. Each report carries an activity summary for its period.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_cr26_vdr.py::test_records_carry_their_historical_rating_and_rating_history" + }, + { + "kind": "test", + "ref": "tests/test_cr26_vdr.py::test_a_decision_sets_the_next_reduction_and_the_deadline_is_only_the_fallback" + }, + { + "kind": "test", + "ref": "tests/test_cr26_vdr.py::test_supplementary_information_comes_from_the_decision" + }, + { + "kind": "test", + "ref": "tests/test_cr26_vdr.py::test_overdue_explanations_explain_the_overdue_status_not_the_suppression" + }, + { + "kind": "test", + "ref": "tests/test_cr26_vdr.py::test_detection_time_comes_from_a_decision_that_names_the_record" + }, + { + "kind": "test", + "ref": "tests/test_cr26_vdr.py::test_outputs_validate_and_name_their_schema" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build CR26 vulnerability reports (VDT, AVI, history)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Build and sign CR26 vulnerability reports (VDT, AVI, history)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-detail-report.json" + } + ] + }, + { + "frr_id": "VER-TFR-EVU", + "status": "Implemented", + "implementation": "policies/triage.rego reads the evaluation window from the rules (scripts/_rules.py evaluation_days(), passed in by the builder) and flags each finding evaluated more than 5 days after the source detected it (a decision made earlier counts as the evaluation), or still resting on a default 5 days after detection (evaluation_late, published per finding and in the VDT). A finding still on a default becomes a process finding (VDR-CSO-FAV). Feeds are fetched twice daily, so first evaluation follows detection within a day.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_evaluation_days_come_from_the_rules" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_evaluated_more_than_five_days_after_detection_is_late" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_a_decision_before_the_pipeline_saw_it_counts_as_the_evaluation" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_still_on_a_default_after_the_window_is_late" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-report.json" + } + ] + }, + { + "frr_id": "VER-TFR-IRI", + "status": "Implemented", + "implementation": "policies/triage.rego (incident_triggers) names every VDR finding that is internet-reachable, likely exploitable and above the N-rating the VER-TFR-IRI Class C text states (read from the rule; a changed text fails closed), unless it is a false positive or fully mitigated; once partially mitigated to N3 or below it no longer triggers. scripts/build-incident-report.py publishes each trigger in the incident log and, while no unresolved incident in data/incidents.json names it, puts an Initial report due from the finding's first evaluation at the default N5 clock: the incident-reports workflow fails and the evidence watchdog pages when that passes. Opening the incident record is the operator's act; its reports then follow IEC-CSO-IIR/OIR/FIR. Reconciliation invariant (m) fails a build whose open incident names a finding the VDR does not carry. Adopted in data/incidents.json policy.adopted_vulnerability_rules.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_incidents.py::test_an_irv_lev_n4_finding_with_no_incident_is_due_an_initial_report" + }, + { + "kind": "test", + "ref": "tests/test_incidents.py::test_a_partially_mitigated_finding_at_n3_is_no_longer_an_incident" + }, + { + "kind": "test", + "ref": "tests/test_incidents.py::test_reconcile_m_fails_the_known_bad_register" + }, + { + "kind": "artifact", + "ref": ".well-known/incident-reports.json" + } + ] + }, + { + "frr_id": "VER-TFR-MAV", + "status": "Implemented", + "implementation": "policies/triage.rego marks a finding accepted once 192 days (VER-TFR-MAV, from the rules) have passed since its first evaluation, with no reset, and also as soon as its projected remediation (a decision's planned reduction to N0) falls after that day ('will not be'); accepted_basis is published, the acceptance explanation is the decision's justification, and the AVI reports it. A closed finding is never accepted.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_projected_remediation_past_the_maximum_period_is_accepted_now" + }, + { + "kind": "test", + "ref": "tests/test_evaluation.py::test_a_closed_finding_is_never_accepted_early" + }, + { + "kind": "test", + "ref": "tests/test_clock.py::test_t14_past_maximum_period_is_reported_accepted_with_unrecorded_explanation" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build VDR Report (FedRAMP 20x Class C)" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build CR26 vulnerability reports (VDT, AVI, history)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-report.json" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-accepted-vulnerabilities.json" + } + ] + }, + { + "frr_id": "VER-TFR-MHR", + "status": "Implemented", + "implementation": "A consistent, human-readable monthly activity report: .well-known/vdr-monthly.md (with .json), rebuilt and signed by every deploy and nightly, covers the calendar month to date and keeps the previous 12 months: detections, evaluations, rating changes, reductions, remediations, decisions, every scan and feed run, runtime verification runs, non-machine V&V and the non-pipeline activities. The current-state vdr-report.md, vdr-detail-report.md and vdr-accepted-vulnerabilities.md are published beside it.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_vdr_monthly.py::test_runs_accumulate_over_the_month_from_the_previous_report" + }, + { + "kind": "test", + "ref": "tests/test_vdr_monthly.py::test_a_finished_month_moves_to_previous_months" + }, + { + "kind": "test", + "ref": "tests/test_vdr_monthly.py::test_the_nightly_and_deploy_build_sign_and_publish_it" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build monthly VDR activity report (VER-TFR-MHR)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Build monthly VDR activity report (VER-TFR-MHR)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-monthly.json" + } + ] + }, + { + "frr_id": "VER-TFR-MRH", + "status": "Implemented", + "implementation": "vdr-history.json under /.well-known/ in FedRAMP's history schema (scripts/build-cr26-vdr.py), rebuilt twice daily with 366-day retention, alongside vdr-report.json and vdr-trend.json. A record that leaves the VDR keeps the time it stopped being reported and gets a final disposition only from evidence (a closed decision, a false-positive suppression of its check, or its scanner running again over the same scope without reporting it), recorded in providerExtensions.dispositionBasis; otherwise noLongerReportedReason says why (suppressed, reported again, or unknown) and no final disposition is given. An unsupported Remediated carried from an earlier history is withdrawn. Closed (remediated) decisions from data/decisions.json are carried as history records (backfilledFromDecision) for 366 days from closing.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_cr26_vdr.py::test_history_keeps_a_finding_that_left_the_vdr_then_drops_it_after_a_year" + }, + { + "kind": "test", + "ref": "tests/test_cr26_vdr.py::test_a_record_that_vanished_without_evidence_has_no_final_disposition" + }, + { + "kind": "test", + "ref": "tests/test_cr26_vdr.py::test_an_unsupported_remediated_from_an_earlier_history_is_withdrawn" + }, + { + "kind": "test", + "ref": "tests/test_cr26_vdr.py::test_a_check_that_became_a_suppression_is_not_remediated" + }, + { + "kind": "test", + "ref": "tests/test_cr26_vdr.py::test_closed_decisions_are_backfilled_into_the_history_once" + }, + { + "kind": "step", + "ref": "deploy-with-opa.yml#Build CR26 vulnerability reports (VDT, AVI, history)" + }, + { + "kind": "step", + "ref": "evidence-nightly.yml#Build and sign CR26 vulnerability reports (VDT, AVI, history)" + }, + { + "kind": "artifact", + "ref": ".well-known/vdr-history.json" + } + ] + }, + { + "frr_id": "VER-TFR-NRI", + "status": "Implemented", + "implementation": "Adopted (docs/policies/ir-policy.md; data/incidents.json policy.adopted_vulnerability_rules). policies/triage.rego names every likely exploitable, not internet-reachable VDR finding at the N-rating the VER-TFR-NRI Class C text states (N5), until partially mitigated to N4 or below; the incident log and clocks treat it exactly as VER-TFR-IRI does. An unadopted rule's triggers are still shown but start no clock.", + "evidence": [ + { + "kind": "test", + "ref": "tests/test_incidents.py::test_an_nirv_lev_n5_finding_opens_under_nri_and_n4_does_not" + }, + { + "kind": "test", + "ref": "tests/test_incidents.py::test_an_unadopted_rule_is_shown_but_starts_no_clock" + }, + { + "kind": "artifact", + "ref": ".well-known/incident-reports.json" + } + ], + "may_rationale": "Adopted, as the incident response policy states: treating a likely exploitable, non-internet-reachable N5 vulnerability as reportable is stricter than required and costs little at this scale." + } + ] +} diff --git a/data/fsi-simulation/messages.json b/data/fsi-simulation/messages.json new file mode 100644 index 00000000..4e556857 --- /dev/null +++ b/data/fsi-simulation/messages.json @@ -0,0 +1,366 @@ +{ + "_note": "SIMULATION INPUT. Synthetic messages for the simulated FedRAMP Security Inbox (this proof of concept receives and sends no mail, by the operator's decision). scripts/build-fsi-simulation.py runs scripts/_fsi.py over these on every deploy and fails the deploy if any observed outcome differs from 'expected'. Addresses here are synthetic test values and are never published; the published result carries sender domains only.", + "inbox": "fedramp-security-inbox@simulation.invalid", + "register_check": { + "now": "2026-11-06T17:00:00Z", + "expected_overdue": [ + "sim-ack-send-fails", + "sim-emergency-other-sender", + "sim-emergency-test", + "sim-forged-gsa" + ], + "expected_retry": { + "acknowledgements_sent_again": 1, + "pages_sent_again": 0 + }, + "important_case": "sim-important", + "important_respond_by": "2026-11-10T22:00:00Z", + "later": "2026-11-09T21:00:00Z", + "emergency_case": "sim-emergency-test", + "untriaged_important_case": "sim-envelope-only" + }, + "messages": [ + { + "case": "emergency-test", + "description": "Emergency Test from FedRAMP's Emergency sender (AFC-FRP-UFS), authenticated", + "message_id": "sim-emergency-test", + "received_at": "2026-11-06T14:05:00Z", + "from": "FedRAMP Security <fedramp_security@fedramp.gov>", + "envelope": "fedramp_security@fedramp.gov", + "subject": "EMERGENCY TEST: FedRAMP Security Inbox exercise", + "headers": { + "Message-ID": "<sim-emergency-test@fedramp.gov>" + }, + "auth": { + "spf": "PASS", + "dkim": "PASS", + "dmarc": "PASS" + }, + "expected": { + "kind": "fedramp", + "designation": "EMERGENCY_TEST", + "sender_domain": "fedramp.gov", + "authenticated": true, + "emergency_sender_ok": true, + "ack": "sent", + "in_reply_to": true, + "page": true, + "triage_by": "2026-11-06T16:05:00Z", + "respond_by": "2026-11-09T20:00:00Z" + } + }, + { + "case": "important", + "description": "Important message whose subject and Message-ID try to inject a Bcc header", + "message_id": "sim-important", + "received_at": "2026-11-06T14:10:00Z", + "from": "FedRAMP PMO <info@fedramp.gov>", + "envelope": "info@fedramp.gov", + "subject": "IMPORTANT: action requested\r\nBcc: injected@attacker.invalid", + "headers": { + "Message-ID": "<a@b>\r\nBcc: injected@attacker.invalid" + }, + "auth": { + "spf": "PASS", + "dkim": "PASS", + "dmarc": "PASS" + }, + "expected": { + "kind": "fedramp", + "designation": "IMPORTANT", + "sender_domain": "fedramp.gov", + "authenticated": true, + "emergency_sender_ok": null, + "ack": "sent", + "in_reply_to": false, + "page": true, + "triage_by": "2026-11-07T14:10:00Z", + "respond_by": null + } + }, + { + "case": "general", + "description": "General communication from @gsa.gov, no designator", + "message_id": "sim-general", + "received_at": "2026-11-06T14:15:00Z", + "from": "info@gsa.gov", + "envelope": "info@gsa.gov", + "subject": "FedRAMP program update", + "headers": { + "Message-ID": "<sim-general@gsa.gov>" + }, + "auth": { + "spf": "PASS", + "dkim": "PASS", + "dmarc": "PASS" + }, + "expected": { + "kind": "fedramp", + "designation": "GENERAL", + "sender_domain": "gsa.gov", + "authenticated": true, + "emergency_sender_ok": null, + "ack": "sent", + "in_reply_to": true, + "page": true, + "triage_by": "2026-11-09T14:15:00Z", + "respond_by": null + } + }, + { + "case": "forged-gsa", + "description": "Forged Emergency claiming to be from the gsa.gov Emergency sender; SPF, DKIM and DMARC fail. Still FedRAMP by default (AFC-CSO-TFG) and paged, but not acknowledged", + "message_id": "sim-forged-gsa", + "received_at": "2026-11-06T14:20:00Z", + "from": "FedRAMP Security <fedramp_security@gsa.gov>", + "envelope": "bounce@attacker.invalid", + "subject": "EMERGENCY: reply with your credentials", + "headers": { + "Message-ID": "<sim-forged@attacker.invalid>" + }, + "auth": { + "spf": "FAIL", + "dkim": "FAIL", + "dmarc": "FAIL" + }, + "expected": { + "kind": "fedramp", + "designation": "EMERGENCY", + "sender_domain": "gsa.gov", + "authenticated": false, + "emergency_sender_ok": true, + "ack": "suppressed:unauthenticated", + "in_reply_to": null, + "page": true, + "triage_by": "2026-11-06T16:20:00Z", + "respond_by": "2026-11-09T20:00:00Z" + } + }, + { + "case": "auto-reply", + "description": "An auto-reply from @fedramp.gov: registered, never answered (no mail loop)", + "message_id": "sim-auto-reply", + "received_at": "2026-11-06T14:25:00Z", + "from": "info@fedramp.gov", + "envelope": "info@fedramp.gov", + "subject": "Automatic reply: Received: FedRAMP Security Inbox exercise", + "headers": { + "Auto-Submitted": "auto-replied", + "Message-ID": "<sim-auto@fedramp.gov>" + }, + "auth": { + "spf": "PASS", + "dkim": "PASS", + "dmarc": "PASS" + }, + "expected": { + "kind": "fedramp", + "designation": "GENERAL", + "sender_domain": "fedramp.gov", + "authenticated": true, + "emergency_sender_ok": null, + "ack": "suppressed:auto-submitted", + "in_reply_to": null, + "page": true, + "triage_by": "2026-11-09T14:25:00Z", + "respond_by": null + } + }, + { + "case": "look-alike", + "description": "Emergency from a look-alike domain (fedramp.gov.attacker.invalid): not FedRAMP, exact domains only", + "message_id": "sim-look-alike", + "received_at": "2026-11-06T14:30:00Z", + "from": "fedramp_security@fedramp.gov.attacker.invalid", + "envelope": "fedramp_security@fedramp.gov.attacker.invalid", + "subject": "EMERGENCY: act now", + "headers": {}, + "auth": { + "spf": "PASS", + "dkim": "PASS", + "dmarc": "PASS" + }, + "expected": { + "kind": "other", + "designation": "GENERAL", + "sender_domain": "fedramp.gov.attacker.invalid", + "authenticated": true, + "emergency_sender_ok": null, + "ack": "none", + "in_reply_to": null, + "page": false, + "triage_by": null, + "respond_by": null + } + }, + { + "case": "display-name-spoof", + "description": "Display name impersonates the gsa.gov Emergency sender, actual address does not: not FedRAMP", + "message_id": "sim-display-name-spoof", + "received_at": "2026-11-06T14:35:00Z", + "from": "\"fedramp_security@gsa.gov\" <attacker@attacker.invalid>", + "envelope": "attacker@attacker.invalid", + "subject": "EMERGENCY: trust me", + "headers": {}, + "auth": { + "spf": "PASS", + "dkim": "PASS", + "dmarc": "PASS" + }, + "expected": { + "kind": "other", + "designation": "GENERAL", + "sender_domain": "attacker.invalid", + "authenticated": true, + "emergency_sender_ok": null, + "ack": "none", + "in_reply_to": null, + "page": false, + "triage_by": null, + "respond_by": null + } + }, + { + "case": "envelope-only", + "description": "Unreadable From header, @gsa.gov envelope sender: still FedRAMP, registered and paged; no reply without a From address", + "message_id": "sim-envelope-only", + "received_at": "2026-11-06T14:40:00Z", + "from": "garbage <<>>", + "envelope": "bounces@gsa.gov", + "subject": "Important: please confirm", + "headers": {}, + "auth": { + "spf": "PASS", + "dkim": "PASS", + "dmarc": "PASS" + }, + "expected": { + "kind": "fedramp", + "designation": "IMPORTANT", + "sender_domain": "gsa.gov", + "authenticated": true, + "emergency_sender_ok": null, + "ack": "suppressed:no-from-address", + "in_reply_to": null, + "page": true, + "triage_by": "2026-11-07T14:40:00Z", + "respond_by": null + } + }, + { + "case": "emergency-other-sender", + "description": "Emergency from an @gsa.gov address other than the designated Emergency senders (AFC-FRP-UFS): flagged, not demoted, still paged", + "message_id": "sim-emergency-other-sender", + "received_at": "2026-11-06T14:45:00Z", + "from": "Someone <someone@gsa.gov>", + "envelope": "someone@gsa.gov", + "subject": "EMERGENCY: rotate your keys", + "headers": { + "Message-ID": "<sim-other@gsa.gov>" + }, + "auth": { + "spf": "PASS", + "dkim": "PASS", + "dmarc": "PASS" + }, + "expected": { + "kind": "fedramp", + "designation": "EMERGENCY", + "sender_domain": "gsa.gov", + "authenticated": true, + "emergency_sender_ok": false, + "ack": "sent", + "in_reply_to": true, + "page": true, + "triage_by": "2026-11-06T16:45:00Z", + "respond_by": "2026-11-09T20:00:00Z" + } + }, + { + "case": "bulk", + "description": "Bulk mail from @gsa.gov: registered, not answered", + "message_id": "sim-bulk", + "received_at": "2026-11-06T14:50:00Z", + "from": "news@gsa.gov", + "envelope": "news@gsa.gov", + "subject": "Newsletter", + "headers": { + "Precedence": "bulk" + }, + "auth": { + "spf": "PASS", + "dkim": "PASS", + "dmarc": "PASS" + }, + "expected": { + "kind": "fedramp", + "designation": "GENERAL", + "sender_domain": "gsa.gov", + "authenticated": true, + "emergency_sender_ok": null, + "ack": "suppressed:precedence", + "in_reply_to": null, + "page": true, + "triage_by": "2026-11-09T14:50:00Z", + "respond_by": null + } + }, + { + "case": "bounce", + "description": "A bounce (null envelope sender) from @gsa.gov: registered, not answered", + "message_id": "sim-bounce", + "received_at": "2026-11-06T14:55:00Z", + "from": "mailer-daemon@gsa.gov", + "envelope": "<>", + "subject": "Undeliverable: Received: FedRAMP program update", + "headers": {}, + "auth": { + "spf": "PASS", + "dkim": "PASS", + "dmarc": "PASS" + }, + "expected": { + "kind": "fedramp", + "designation": "GENERAL", + "sender_domain": "gsa.gov", + "authenticated": true, + "emergency_sender_ok": null, + "ack": "suppressed:null-sender", + "in_reply_to": null, + "page": true, + "triage_by": "2026-11-09T14:55:00Z", + "respond_by": null + } + }, + { + "case": "ack-send-fails", + "description": "The first acknowledgement attempt fails: recorded as failed, reported overdue, and sent exactly once on the retry", + "message_id": "sim-ack-send-fails", + "received_at": "2026-11-06T15:00:00Z", + "simulate_send_failure": true, + "from": "info@fedramp.gov", + "envelope": "info@fedramp.gov", + "subject": "Checking in", + "headers": { + "Message-ID": "<sim-fail@fedramp.gov>" + }, + "auth": { + "spf": "PASS", + "dkim": "PASS", + "dmarc": "PASS" + }, + "expected": { + "kind": "fedramp", + "designation": "GENERAL", + "sender_domain": "fedramp.gov", + "authenticated": true, + "emergency_sender_ok": null, + "ack": "failed", + "in_reply_to": null, + "page": true, + "triage_by": "2026-11-09T15:00:00Z", + "respond_by": null + } + } + ] +} diff --git a/data/incidents.json b/data/incidents.json new file mode 100644 index 00000000..0bd171dc --- /dev/null +++ b/data/incidents.json @@ -0,0 +1,109 @@ +{ + "$comment": "The incident register (IEC-CSO-EFR/DPR/EFI/IIR/OIR/FIR). Every incident is recorded here once, with its FedRAMP reportability evaluation and reason; a reportable one carries its Incident Rating estimates and the Initial, Ongoing and Final reports issued, each with when it was issued and what it set. scripts/_incidents.py validates it (fail-closed) and scripts/build-incident-report.py renders the reports and the incident log; .github/workflows/incident-reports.yml publishes them on every change to this file. The report clocks are FedRAMP's Class C timeframes, read from the pinned rules, never set here. Everything in this file is published. Exercises are marked exercise: true. Shape: infrastructure/schemas/incidents.schema.json.", + "schema": "incidents/1", + "policy": { + "federal_incident_coordinator": "Sam Aydlette, System Owner and incident response lead; contact through https://samaydlette.com/.well-known/security.txt", + "notification": "published-only", + "notification_text": "Published, and delivered to SIMULATED recipients. Each report is signed and published under https://samaydlette.com/.well-known/ (incident-reports.json lists every report and its sha256) and 'delivered' to a simulated FedRAMP and agency recipient, recorded in incident-deliveries.json. Nothing is sent to FedRAMP or to any agency: this system has no FedRAMP certification and no agency customers.", + "adopted_vulnerability_rules": ["VER-TFR-IRI", "VER-TFR-NRI"], + "federal_customer_data": "None. This system holds no federal customer data (FRD-FCD) and has no agency customers. Were an agency to use the Silk Reeling application, what its users supply to it (pose landmarks) would be the federal customer data to consider; the operator's public site content, account information and the published evidence are not.", + "decided_by": "Operator", + "decided_on": "2026-11-05", + "review_by": "2027-11-05" + }, + "incidents": [ + { + "id": "INC-2026-001", + "title": "Exercise: internet-reachable likely exploitable N5 vulnerability in the Silk Reeling API", + "exercise": true, + "started_at": "2026-11-05T02:40:00Z", + "detected_at": "2026-11-05T03:00:00Z", + "detection_source": "Exercise inject: a simulated VDR finding that policies/triage.rego flags under VER-TFR-IRI", + "evaluation": { + "evaluated_at": "2026-11-05T03:10:00Z", + "reportable": true, + "basis": "VER-TFR-IRI", + "reason": "Simulated timeline. An internet-reachable, likely exploitable vulnerability rated N5 in a dependency of the Silk Reeling API. The operator treats such a vulnerability as a FedRAMP Reportable Incident (VER-TFR-IRI) until it is partially mitigated to N3 or below. The scenario assumes one agency whose users supply data to the application.", + "federal_customer_data_considered": "Scenario assumption: pose landmarks supplied by one agency's users of the Silk Reeling application. In reality the system holds no federal customer data." + }, + "findings": ["CVE-2099-0001"], + "estimates": [ + { + "estimated_at": "2026-11-05T04:30:00Z", + "rating": 3, + "customer_effect": "disruptive", + "agencies": "single", + "reason": "Exploitation could expose the landmark data of many of the assumed agency's users without interrupting the service for long; no other agency is assumed." + } + ], + "reports": [ + { + "type": "Initial", + "at": "2026-11-05T03:40:00Z", + "set": { + "description": "A request-parsing dependency of the Silk Reeling API has a vulnerability (simulated CVE-2099-0001) that an unauthenticated client could exploit over the internet to read other users' submitted data.", + "functional_impact": "Potential loss of confidentiality of pose landmarks submitted by the assumed agency's users; no integrity or availability effect is expected.", + "recovery_plan": "Throttle the affected endpoint now; upgrade the dependency to the fixed release and redeploy through the reviewed pipeline. Targets: partial mitigation within 3 hours, remediation within 1 day.", + "affected_agencies": ["Hypothetical agency A (exercise assumption)"], + "related_cves": ["CVE-2099-0001"], + "milestones": [ + {"at": "2026-11-05T03:00:00Z", "description": "Triage flagged the finding under VER-TFR-IRI (simulated)"} + ] + } + }, + { + "type": "Ongoing", + "at": "2026-11-05T09:20:00Z", + "set": { + "observed_activity": "No exploitation attempts in the API Gateway access logs since the vulnerable release was deployed (simulated review).", + "indicators_of_compromise": ["None observed (simulated)"], + "root_cause": "A vulnerable release of a request-parsing dependency (simulated CVE-2099-0001).", + "response_and_recovery_activities": "Endpoint throttled at 04:15 (simulated), a partial mitigation; Incident Rating estimated at N3; fixed release identified.", + "milestones": [ + {"at": "2026-11-05T04:15:00Z", "description": "Partial mitigation: affected endpoint throttled (simulated)"} + ] + } + }, + { + "type": "Ongoing", + "at": "2026-11-05T15:00:00Z", + "set": { + "response_and_recovery_activities": "Fixed release built and passing the pipeline's gates; deploy awaiting approval (simulated)." + } + }, + { + "type": "Final", + "at": "2026-11-05T17:45:00Z", + "set": { + "response_and_recovery_activities": "Fixed release deployed at 16:30 and the finding no longer appears in the VDR (simulated); recovery verified at 17:00.", + "recovery_plan": "Complete.", + "milestones": [ + {"at": "2026-11-05T16:30:00Z", "description": "Fixed release deployed (simulated)"} + ] + } + } + ], + "resolved_at": "2026-11-05T16:30:00Z", + "recovery_complete_at": "2026-11-05T17:00:00Z" + }, + { + "id": "INC-2026-002", + "title": "Exercise: unauthorized change to a page of the public site", + "exercise": true, + "started_at": "2026-11-05T10:00:00Z", + "detected_at": "2026-11-05T10:20:00Z", + "detection_source": "Exercise inject: simulated drift of a website HTML artifact between the deploy-time and runtime KSI signals", + "evaluation": { + "evaluated_at": "2026-11-05T10:35:00Z", + "reportable": false, + "basis": "IEC-CSO-EFR", + "reason": "Simulated timeline. The changed content is the operator's public site content, which is not federal customer data (FRD-FCD), and the change is not likely to affect the confidentiality or integrity of any federal customer data. Not a FedRAMP Reportable Incident; handled under the incident response runbook without FedRAMP reports.", + "federal_customer_data_considered": "None present: public website content only." + }, + "estimates": [], + "reports": [], + "resolved_at": "2026-11-05T11:30:00Z", + "recovery_complete_at": "2026-11-05T11:45:00Z" + } + ] +} diff --git a/data/mappings/SP800-171r2-to-SP800-53r4.mapping.json b/data/mappings/SP800-171r2-to-SP800-53r4.mapping.json deleted file mode 100644 index 5b990ca0..00000000 --- a/data/mappings/SP800-171r2-to-SP800-53r4.mapping.json +++ /dev/null @@ -1,2515 +0,0 @@ -{ - "mapping-collection": { - "uuid": "e4b10a6d-c68d-5040-9134-7672a570036f", - "metadata": { - "title": "NIST SP 800-171 Rev2 -> 800-53 Rev4 control mapping (Appendix D, Table D-1)", - "last-modified": "2026-06-10T00:00:00Z", - "version": "1.0.0", - "oscal-version": "1.2.2", - "remarks": "From 800-171 Rev2 Appendix D Table D-1 (a 171 requirement is a tailored subset of the relevant 800-53 control). 109 requirements mapped; 1 explicit no-800-53-mapping (['3.12.4']); RESIDUE pending verification: []." - }, - "provenance": { - "method": "hybrid", - "matching-rationale": "functional", - "status": "complete", - "mapping-description": "NIST's authoritative 171->53 tailoring mapping (Table D-1); 171 requirements are tailored subsets of the 800-53 controls." - }, - "mappings": [ - { - "uuid": "23d9ca80-5834-588e-9ea7-d95524024983", - "source-resource": { - "type": "resource", - "href": "#res-171r2" - }, - "target-resource": { - "type": "resource", - "href": "#res-53r4" - }, - "maps": [ - { - "uuid": "e94ab2a4-6484-50d9-ba51-f73db4971a05", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-2" - } - ] - }, - { - "uuid": "1d0c85d9-f320-54d4-960b-e344b39094ad", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-11" - } - ] - }, - { - "uuid": "6bea23f4-1a3a-5c41-ab05-78c8735c86e7", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-11.1" - } - ] - }, - { - "uuid": "fc93aae5-39d6-5373-9a4f-df84b6cb909f", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-12" - } - ] - }, - { - "uuid": "cd25b300-eb69-511f-b0ba-fe67c93baae7", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.12" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-17.1" - } - ] - }, - { - "uuid": "32616d1b-5dd2-5afe-a2af-57e698959ac1", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.13" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-17.2" - } - ] - }, - { - "uuid": "80c96d9f-dff6-5234-b586-1e90f3c02ebf", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.14" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-17.3" - } - ] - }, - { - "uuid": "b847b9bb-9bdb-5407-8310-f04bdc9ad47c", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.15" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-17.4" - } - ] - }, - { - "uuid": "0882c403-e4dd-51d3-8058-ec69ea5e6732", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.16" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-18" - } - ] - }, - { - "uuid": "89ac2d9e-ab01-5610-bd2f-b54bd20c3ca1", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.17" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-18.1" - } - ] - }, - { - "uuid": "f5c8d007-ba9b-5a10-9610-7e23a89543ed", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.18" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-19" - } - ] - }, - { - "uuid": "2d021921-8676-5167-b608-1a7aa370f8fb", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.19" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-19.5" - } - ] - }, - { - "uuid": "8a2b6b85-cb94-5f72-aae9-dd91cc9a3895", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-17" - } - ] - }, - { - "uuid": "a74f069a-cdf4-5df9-ac0b-42e16f29a24d", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-3" - } - ] - }, - { - "uuid": "23548b61-b4ff-5ac3-ad8f-310ef1bbdca4", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.20" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-20" - } - ] - }, - { - "uuid": "e7b2aa67-266d-5393-b034-6d3b9802dd3c", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.20" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-20.1" - } - ] - }, - { - "uuid": "ebcbae08-953a-530f-8e5a-e01274793533", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.21" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-20.2" - } - ] - }, - { - "uuid": "f86eec94-d922-5a3d-b48f-6b904bf9bd93", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.22" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-22" - } - ] - }, - { - "uuid": "4ca29346-a066-5771-9b18-46d8a0ffa6a4", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4" - } - ] - }, - { - "uuid": "e816422d-8577-5f54-896b-4c4327da8ad1", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-5" - } - ] - }, - { - "uuid": "688d0842-c9a7-5f13-93fa-e7ec810a2f03", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6" - } - ] - }, - { - "uuid": "b08f285b-b220-5bea-b4af-68a09ae0d1ee", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6.1" - } - ] - }, - { - "uuid": "46675c2f-4c7d-546d-80d8-f59cd7c22aae", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6.5" - } - ] - }, - { - "uuid": "75ed5d2c-8867-5d6b-a6d8-c3e758439c0f", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6.2" - } - ] - }, - { - "uuid": "1baf9bb4-a29f-5122-acb0-bb9f0da58546", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6.10" - } - ] - }, - { - "uuid": "638f87d1-de49-57c8-bc4d-c3dc3a5ec2ce", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6.9" - } - ] - }, - { - "uuid": "a88ed7c3-db5c-59fe-944b-f68d33b2337c", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-7" - } - ] - }, - { - "uuid": "fc09c84d-aa61-5d5d-987b-cfef5474f1f6", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.1.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-8" - } - ] - }, - { - "uuid": "200fc8e6-7736-5fd4-a7d4-f6028ec05a67", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.10.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-2" - } - ] - }, - { - "uuid": "6d7bf13b-1225-5d32-940b-ffe0ddc6ef95", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.10.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-4" - } - ] - }, - { - "uuid": "1a0501fc-e3af-57d6-aff3-e2deacb6b5cf", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.10.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-5" - } - ] - }, - { - "uuid": "ece84119-9b5d-5587-98e4-3689e9d7c556", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.10.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-6" - } - ] - }, - { - "uuid": "42b61b05-94f0-5b4b-b358-8fb499691270", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.10.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-3" - } - ] - }, - { - "uuid": "43cacb45-28c2-5ee6-a450-0e80883bb3fc", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.10.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-3" - } - ] - }, - { - "uuid": "f5de65df-9c0a-599b-903c-d08df4ecee27", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.10.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-3" - } - ] - }, - { - "uuid": "0815cdc7-fac5-56d6-8503-cbee6d740472", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.10.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-17" - } - ] - }, - { - "uuid": "23fea1aa-1150-52b7-914c-07f85da50570", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.11.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-3" - } - ] - }, - { - "uuid": "89d3c065-cf4c-5cda-82eb-865acb9cde38", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.11.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-5" - } - ] - }, - { - "uuid": "05b687d0-971c-5d35-9944-48245a13020c", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.11.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-5.5" - } - ] - }, - { - "uuid": "9289ff19-c1a6-57d2-908a-c827870cfe81", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.11.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-5" - } - ] - }, - { - "uuid": "1ba837c6-4df0-5f5e-b3e5-fd92a917cf94", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.12.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-2" - } - ] - }, - { - "uuid": "f8093607-e571-593d-8396-638c7092b440", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.12.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-5" - } - ] - }, - { - "uuid": "1a60f889-3aed-5c6b-b172-6555843b5294", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.12.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-7" - } - ] - }, - { - "uuid": "38622f21-ec7d-5d44-83b7-7d28b11e5a05", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.12.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-2" - } - ] - }, - { - "uuid": "8a233e90-474d-5cbd-875e-c2399c25a467", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.12.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-2" - } - ] - }, - { - "uuid": "bdbe1596-4bf7-521d-b1b8-f2df76af740f", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.12.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-5" - } - ] - }, - { - "uuid": "9d514d54-297f-5c22-a6f3-ebd7619c5515", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.12.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-7" - } - ] - }, - { - "uuid": "7933145c-a9e5-5a58-93e9-3efea04ce849", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.12.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-2" - } - ] - }, - { - "uuid": "375ffb57-5d60-56a5-99e8-69e4a1ecad6f", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.13.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7" - } - ] - }, - { - "uuid": "4d1aadd6-c9c0-506b-8ec4-eca3040ec422", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.13.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-12" - } - ] - }, - { - "uuid": "dc51b56e-092b-5ef3-ab96-17fb59161fe2", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.13.11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-13" - } - ] - }, - { - "uuid": "a97f2281-a708-5f9b-9457-399fc2096a63", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.13.12" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-15" - } - ] - }, - { - "uuid": "df69f116-d272-5c91-86ef-9763ce96aab8", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.13.13" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-18" - } - ] - }, - { - "uuid": "d04c8015-aa71-572d-aebd-b5269f28358e", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.13.14" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-19" - } - ] - }, - { - "uuid": "6c8b518a-22fa-5b82-a6bd-58c025c6ff22", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.13.15" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-23" - } - ] - }, - { - "uuid": "86abc3ea-467c-5a20-90e0-8bbd952e940e", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.13.16" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-28" - } - ] - }, - { - "uuid": "825169be-4452-5fc0-aa4d-9469783a3dee", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.13.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-8" - } - ] - }, - { - "uuid": "49b79f37-dff1-5150-9a1d-1f355d622396", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.13.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-2" - } - ] - }, - { - "uuid": "223fa861-3ddb-5ce9-abfb-187b0c4dc1b9", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.13.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-4" - } - ] - }, - { - "uuid": "72c338cc-f3ab-5a1d-bc80-3d9e6b79c131", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.13.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7" - } - ] - }, - { - "uuid": "d25e85d9-ef16-53ca-a776-9d7ee9b8e368", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.13.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.5" - } - ] - }, - { - "uuid": "95e2c467-d74b-5c11-b0f4-c67b6f38a05a", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.13.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.7" - } - ] - }, - { - "uuid": "a6d4a502-7b7f-5ac8-bf84-1921e0074aae", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.13.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-8" - } - ] - }, - { - "uuid": "106425f8-c943-5de8-a0f9-6e825da337ed", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.13.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-8.1" - } - ] - }, - { - "uuid": "5136b867-51e0-5601-b8f5-3ad8e70aa081", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.13.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-10" - } - ] - }, - { - "uuid": "ba2ce64a-262d-5ab9-9700-64fc041bab3f", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.14.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-2" - } - ] - }, - { - "uuid": "9152cfcd-7a36-52ea-821b-43546cbb5981", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.14.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-2" - } - ] - }, - { - "uuid": "359f77a6-7449-5a2a-9e79-9a9d82a9881e", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.14.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-3" - } - ] - }, - { - "uuid": "52de0c80-8d2e-57e5-846b-4f2b05a765ea", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.14.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-5" - } - ] - }, - { - "uuid": "ba0861cd-62a7-5649-bceb-004a819f910b", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.14.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-3" - } - ] - }, - { - "uuid": "4f88ef08-4497-5e93-a135-fcac60be824b", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.14.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-5" - } - ] - }, - { - "uuid": "9bb2aee9-dbff-5e9b-a56a-804a7dfbf36a", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.14.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-3" - } - ] - }, - { - "uuid": "397afbfd-a58e-58d8-b160-6a5344e5057b", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.14.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-3" - } - ] - }, - { - "uuid": "ba75426c-ed68-5dbc-9562-a733de642a41", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.14.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4" - } - ] - }, - { - "uuid": "8b670f19-6a07-57ee-80d8-7aca4bc1e09d", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.14.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.4" - } - ] - }, - { - "uuid": "1d067000-d6d9-53cc-a2ac-ba535a0953f7", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.14.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4" - } - ] - }, - { - "uuid": "e134f1dc-1608-59cb-a628-0340bbdd9004", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.2.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "at-2" - } - ] - }, - { - "uuid": "f0c2050b-59cd-55c9-b51d-ad82c89e28c3", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.2.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "at-3" - } - ] - }, - { - "uuid": "6ec6fe96-fa67-5fe4-bfa0-a8e3448464e1", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.2.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "at-2" - } - ] - }, - { - "uuid": "5b60eefb-e19d-51eb-8021-49cd95db23a8", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.2.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "at-3" - } - ] - }, - { - "uuid": "d56372d2-e3f8-5991-a983-f6ae0064291f", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.2.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "at-2.2" - } - ] - }, - { - "uuid": "d807b60d-752f-5b0c-9b67-230f9268a179", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.3.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-2" - } - ] - }, - { - "uuid": "38bc3078-df88-52f9-86cc-976d881cb5d0", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.3.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-3" - } - ] - }, - { - "uuid": "551867af-9bc7-59a0-a77d-58f1298c00c0", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.3.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-3.1" - } - ] - }, - { - "uuid": "f4c06386-c998-5e07-91f4-b9371920d8e2", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.3.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-11" - } - ] - }, - { - "uuid": "67700f98-a005-58f5-9798-47b5e3b7aed4", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.3.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-12" - } - ] - }, - { - "uuid": "8091c610-5f61-585b-b5d5-1bb7c5ddddf6", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.3.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-6" - } - ] - }, - { - "uuid": "0368907a-d42c-59c0-88eb-04d006590dbb", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.3.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-2.3" - } - ] - }, - { - "uuid": "ca64cca3-acec-5ba5-8b39-48fb0e3f8a24", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.3.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-5" - } - ] - }, - { - "uuid": "f90fdf82-bb88-5032-982a-ef91836ccdda", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.3.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-6.3" - } - ] - }, - { - "uuid": "a3465bfe-a48a-5bb8-a7d3-ea30861b5dd1", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.3.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-7" - } - ] - }, - { - "uuid": "7af68d39-a68e-5539-a00c-3114df8c7b0b", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.3.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-8" - } - ] - }, - { - "uuid": "5d21e1aa-ffcf-5bbf-950c-2e59f912e694", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.3.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-8.1" - } - ] - }, - { - "uuid": "53132b86-e967-5470-a506-c925eb4827cd", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.3.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-9" - } - ] - }, - { - "uuid": "d22fe167-efab-5a27-9244-624bcfd1f339", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.3.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-9.4" - } - ] - }, - { - "uuid": "89e5cd4a-6c37-5d14-901f-211e8df3a31d", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.4.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-2" - } - ] - }, - { - "uuid": "7defb7c9-6411-531f-a3fd-bc4653e8b7fd", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.4.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-6" - } - ] - }, - { - "uuid": "d94113c4-ea1d-5bb9-8092-99353a831df8", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.4.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-8" - } - ] - }, - { - "uuid": "a5e0af3d-0237-5143-acd3-0e49e529c7df", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.4.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-8.1" - } - ] - }, - { - "uuid": "3d7ab234-c082-5628-adf7-994304999a79", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.4.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-2" - } - ] - }, - { - "uuid": "80e41eaf-fcfa-51b8-ac3e-2d8cd8229f82", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.4.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-6" - } - ] - }, - { - "uuid": "a5a775db-ca7f-5633-8f1b-0cda683534e1", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.4.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-8" - } - ] - }, - { - "uuid": "a648ad3c-b702-585f-a6cb-5c22ec73209e", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.4.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-8.1" - } - ] - }, - { - "uuid": "e1e5ddc2-d588-5d19-81c0-af4b4c071239", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.4.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-3" - } - ] - }, - { - "uuid": "eb89698b-b6bd-537c-bc66-3c078e2c3e5a", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.4.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-4" - } - ] - }, - { - "uuid": "08726a0f-4f80-5aa7-b9d5-810552259b88", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.4.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-5" - } - ] - }, - { - "uuid": "f7cba726-feee-543b-b4da-66a1521754f1", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.4.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-7" - } - ] - }, - { - "uuid": "65ed12b2-4307-5973-8a0a-7bc4f74b9c49", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.4.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-7.1" - } - ] - }, - { - "uuid": "00467565-a74d-519e-9fd7-d0b45c696b49", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.4.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-7.2" - } - ] - }, - { - "uuid": "be491918-36e0-5003-b825-db2bc571a86b", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.4.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-7.4" - } - ] - }, - { - "uuid": "002049ed-b277-56ea-8e16-c2ae60ac0d92", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.4.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-7.5" - } - ] - }, - { - "uuid": "cd330bc4-95b5-50f4-88e0-0aef9f8b9a56", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.4.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-11" - } - ] - }, - { - "uuid": "5b3259f4-d602-5ed1-a405-a69f943efbb4", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.5.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2" - } - ] - }, - { - "uuid": "41cc56d3-8280-53eb-87bd-6788aa0aae48", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.5.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-5.1" - } - ] - }, - { - "uuid": "3c9fff4e-eec0-5279-8394-f4c13f4db28f", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.5.11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-6" - } - ] - }, - { - "uuid": "fd064018-c5f8-523c-bb5c-3e12157e29cf", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.5.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-3" - } - ] - }, - { - "uuid": "efee6eb9-0937-5e6b-9f2b-cf19cee18fac", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.5.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-5" - } - ] - }, - { - "uuid": "bb7325a6-4017-574f-a79b-70c011a4f216", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.5.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2.1" - } - ] - }, - { - "uuid": "5a100629-51ca-5cd1-ae6d-c8d8c3db1fc7", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.5.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2.2" - } - ] - }, - { - "uuid": "ff78588e-a8b1-5a56-a929-de98be7caa87", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.5.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2.3" - } - ] - }, - { - "uuid": "112bc590-983b-54cf-a963-c49fd262c3dc", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.5.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2.8" - } - ] - }, - { - "uuid": "fa4f8382-43da-56be-9cdb-7013319a0292", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.5.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2.9" - } - ] - }, - { - "uuid": "0136a143-80bd-57ce-84af-a146fef5e152", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.5.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-4" - } - ] - }, - { - "uuid": "02ac4865-ae89-500c-bddc-c6d3fb2b12cf", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.5.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-4" - } - ] - }, - { - "uuid": "ed9c62fe-4a95-5651-9a7c-53b9e2382320", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.5.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-5.1" - } - ] - }, - { - "uuid": "aa498ba8-43a1-52f8-8210-91519d93994d", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.5.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-5.1" - } - ] - }, - { - "uuid": "b87c9ac0-3ccd-5bcb-b606-29fc2451703f", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.5.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-5.1" - } - ] - }, - { - "uuid": "75ec30d8-6ba6-5a14-b9b7-9777317a3a6f", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.6.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-2" - } - ] - }, - { - "uuid": "14d6abb4-b735-53ad-bd23-fc534cca2610", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.6.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-4" - } - ] - }, - { - "uuid": "b3b24350-e3bd-528d-b502-a9861ea4835f", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.6.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-5" - } - ] - }, - { - "uuid": "684dd0bc-2c78-5e41-8e5a-a7fdbefd6b79", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.6.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-6" - } - ] - }, - { - "uuid": "f4041a00-b437-5fc5-8c30-d1636ec9d152", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.6.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-7" - } - ] - }, - { - "uuid": "e23a177b-cade-5331-9771-1686c935ae27", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.6.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-3" - } - ] - }, - { - "uuid": "46cf3acc-f84f-5080-b85d-4b7f96b7effb", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.7.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-2" - } - ] - }, - { - "uuid": "78f5e1ab-d539-5228-a7ae-24331aa7a59e", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.7.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-3" - } - ] - }, - { - "uuid": "6d557cad-5e9e-560b-a539-284f16eac1d6", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.7.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-3.1" - } - ] - }, - { - "uuid": "82610a95-ed6d-5478-9d71-6f63716fd051", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.7.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-3.2" - } - ] - }, - { - "uuid": "4dd3aa28-a272-5d15-941a-937e3e067da1", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.7.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-2" - } - ] - }, - { - "uuid": "68618b33-3f51-580e-871f-9466cc8965e6", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.7.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-3.2" - } - ] - }, - { - "uuid": "c99b659d-b3c4-568e-9c29-ecaa49c6dad9", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.7.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-4" - } - ] - }, - { - "uuid": "99e2901e-12e8-5eca-a470-934155d1e5d2", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.7.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-5" - } - ] - }, - { - "uuid": "6f334557-403f-5671-b91b-93ee6a529b09", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.8.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-2" - } - ] - }, - { - "uuid": "b1e11c6e-35f6-5139-8c87-b46fd5723bdb", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.8.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-4" - } - ] - }, - { - "uuid": "66ce32b6-68b9-5b23-80b5-65d56e30246c", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.8.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-6" - } - ] - }, - { - "uuid": "e4b14c83-8369-5ad0-ac26-6375c6730dc6", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.8.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-3" - } - ] - }, - { - "uuid": "db69eda2-5bc2-5a4f-bfdc-cc25964d72d7", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.8.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-5" - } - ] - }, - { - "uuid": "9960a657-8ae3-563c-a50d-5d42845e7a82", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.8.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-5.4" - } - ] - }, - { - "uuid": "7c6ab30d-68d5-5315-bb54-4360d77c09db", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.8.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-7" - } - ] - }, - { - "uuid": "de000942-e76e-5fe9-9b55-c260fabe63c4", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.8.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-7.1" - } - ] - }, - { - "uuid": "f33ebf33-573e-5e6e-8d09-93744efff2ac", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.8.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-9" - } - ] - }, - { - "uuid": "ce5eddc8-adb3-5b51-a0f1-6f9910319dd9", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.9.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ps-3" - } - ] - }, - { - "uuid": "21ef5f6b-0ec7-586a-879c-363cf0d1a31c", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.9.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ps-4" - } - ] - }, - { - "uuid": "8c3880a3-0caa-5113-a238-4ca26c552069", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "3.9.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ps-5" - } - ] - } - ] - } - ], - "back-matter": { - "resources": [ - { - "uuid": "689934d0-9c4c-562f-879d-5d0276611215", - "title": "NIST SP 800-171 Rev2 catalog", - "props": [ - { - "name": "id", - "value": "res-171r2" - } - ], - "rlinks": [ - { - "href": "../catalogs/NIST_SP-800-171_rev2_catalog.json" - } - ] - }, - { - "uuid": "2b315c4f-8371-5ba6-b88c-0b3de6a577ab", - "title": "NIST SP 800-53 Rev4 catalog", - "props": [ - { - "name": "id", - "value": "res-53r4" - } - ], - "rlinks": [ - { - "href": "../catalogs/NIST_SP-800-53_rev4_catalog.json" - } - ] - } - ] - } - } -} diff --git a/data/mappings/SP800-171r2-to-SP800-53r4.source.json b/data/mappings/SP800-171r2-to-SP800-53r4.source.json deleted file mode 100644 index 37b53936..00000000 --- a/data/mappings/SP800-171r2-to-SP800-53r4.source.json +++ /dev/null @@ -1,381 +0,0 @@ -{ - "_provenance": "NIST SP 800-171 Rev2 Appendix D Table D-1 (171 req -> 800-53 Rev4); extracted via pdfplumber word-geometry + manual verification of spanning cells from the publication PDF.", - "mapping": { - "3.1.1": [ - "ac-2" - ], - "3.1.10": [ - "ac-11", - "ac-11.1" - ], - "3.1.11": [ - "ac-12" - ], - "3.1.12": [ - "ac-17.1" - ], - "3.1.13": [ - "ac-17.2" - ], - "3.1.14": [ - "ac-17.3" - ], - "3.1.15": [ - "ac-17.4" - ], - "3.1.16": [ - "ac-18" - ], - "3.1.17": [ - "ac-18.1" - ], - "3.1.18": [ - "ac-19" - ], - "3.1.19": [ - "ac-19.5" - ], - "3.1.2": [ - "ac-17", - "ac-3" - ], - "3.1.20": [ - "ac-20", - "ac-20.1" - ], - "3.1.21": [ - "ac-20.2" - ], - "3.1.22": [ - "ac-22" - ], - "3.1.3": [ - "ac-4" - ], - "3.1.4": [ - "ac-5" - ], - "3.1.5": [ - "ac-6", - "ac-6.1", - "ac-6.5" - ], - "3.1.6": [ - "ac-6.2" - ], - "3.1.7": [ - "ac-6.10", - "ac-6.9" - ], - "3.1.8": [ - "ac-7" - ], - "3.1.9": [ - "ac-8" - ], - "3.10.1": [ - "pe-2", - "pe-4", - "pe-5" - ], - "3.10.2": [ - "pe-6" - ], - "3.10.3": [ - "pe-3" - ], - "3.10.4": [ - "pe-3" - ], - "3.10.5": [ - "pe-3" - ], - "3.10.6": [ - "pe-17" - ], - "3.11.1": [ - "ra-3" - ], - "3.11.2": [ - "ra-5", - "ra-5.5" - ], - "3.11.3": [ - "ra-5" - ], - "3.12.1": [ - "ca-2" - ], - "3.12.2": [ - "ca-5", - "ca-7", - "pl-2" - ], - "3.12.3": [ - "ca-2", - "ca-5", - "ca-7", - "pl-2" - ], - "3.13.1": [ - "sc-7" - ], - "3.13.10": [ - "sc-12" - ], - "3.13.11": [ - "sc-13" - ], - "3.13.12": [ - "sc-15" - ], - "3.13.13": [ - "sc-18" - ], - "3.13.14": [ - "sc-19" - ], - "3.13.15": [ - "sc-23" - ], - "3.13.16": [ - "sc-28" - ], - "3.13.2": [ - "sa-8" - ], - "3.13.3": [ - "sc-2" - ], - "3.13.4": [ - "sc-4" - ], - "3.13.5": [ - "sc-7" - ], - "3.13.6": [ - "sc-7.5" - ], - "3.13.7": [ - "sc-7.7" - ], - "3.13.8": [ - "sc-8", - "sc-8.1" - ], - "3.13.9": [ - "sc-10" - ], - "3.14.1": [ - "si-2" - ], - "3.14.2": [ - "si-2", - "si-3", - "si-5" - ], - "3.14.3": [ - "si-3", - "si-5" - ], - "3.14.4": [ - "si-3" - ], - "3.14.5": [ - "si-3" - ], - "3.14.6": [ - "si-4", - "si-4.4" - ], - "3.14.7": [ - "si-4" - ], - "3.2.1": [ - "at-2", - "at-3" - ], - "3.2.2": [ - "at-2", - "at-3" - ], - "3.2.3": [ - "at-2.2" - ], - "3.3.1": [ - "au-2", - "au-3", - "au-3.1" - ], - "3.3.2": [ - "au-11", - "au-12", - "au-6" - ], - "3.3.3": [ - "au-2.3" - ], - "3.3.4": [ - "au-5" - ], - "3.3.5": [ - "au-6.3" - ], - "3.3.6": [ - "au-7" - ], - "3.3.7": [ - "au-8", - "au-8.1" - ], - "3.3.8": [ - "au-9" - ], - "3.3.9": [ - "au-9.4" - ], - "3.4.1": [ - "cm-2", - "cm-6", - "cm-8", - "cm-8.1" - ], - "3.4.2": [ - "cm-2", - "cm-6", - "cm-8", - "cm-8.1" - ], - "3.4.3": [ - "cm-3" - ], - "3.4.4": [ - "cm-4" - ], - "3.4.5": [ - "cm-5" - ], - "3.4.6": [ - "cm-7" - ], - "3.4.7": [ - "cm-7.1", - "cm-7.2" - ], - "3.4.8": [ - "cm-7.4", - "cm-7.5" - ], - "3.4.9": [ - "cm-11" - ], - "3.5.1": [ - "ia-2" - ], - "3.5.10": [ - "ia-5.1" - ], - "3.5.11": [ - "ia-6" - ], - "3.5.2": [ - "ia-3", - "ia-5" - ], - "3.5.3": [ - "ia-2.1", - "ia-2.2", - "ia-2.3" - ], - "3.5.4": [ - "ia-2.8", - "ia-2.9" - ], - "3.5.5": [ - "ia-4" - ], - "3.5.6": [ - "ia-4" - ], - "3.5.7": [ - "ia-5.1" - ], - "3.5.8": [ - "ia-5.1" - ], - "3.5.9": [ - "ia-5.1" - ], - "3.6.1": [ - "ir-2", - "ir-4" - ], - "3.6.2": [ - "ir-5", - "ir-6", - "ir-7" - ], - "3.6.3": [ - "ir-3" - ], - "3.7.1": [ - "ma-2" - ], - "3.7.2": [ - "ma-3", - "ma-3.1", - "ma-3.2" - ], - "3.7.3": [ - "ma-2" - ], - "3.7.4": [ - "ma-3.2" - ], - "3.7.5": [ - "ma-4" - ], - "3.7.6": [ - "ma-5" - ], - "3.8.1": [ - "mp-2" - ], - "3.8.2": [ - "mp-4" - ], - "3.8.3": [ - "mp-6" - ], - "3.8.4": [ - "mp-3" - ], - "3.8.5": [ - "mp-5" - ], - "3.8.6": [ - "mp-5.4" - ], - "3.8.7": [ - "mp-7" - ], - "3.8.8": [ - "mp-7.1" - ], - "3.8.9": [ - "cp-9" - ], - "3.9.1": [ - "ps-3", - "ps-4" - ], - "3.9.2": [ - "ps-5" - ] - }, - "no_800_53_mapping": [ - "3.12.4" - ], - "residue_unconfirmed": [], - "_confirmation": "The 7 spanning/ambiguous requirements were confirmed by the operator against 800-171 Rev2 Table D-1 (pages 78/81/90/92/96) on 2026-06-10." -} \ No newline at end of file diff --git a/data/mappings/SP800-53_rev4-to-rev5.mapping.json b/data/mappings/SP800-53_rev4-to-rev5.mapping.json deleted file mode 100644 index a873ff87..00000000 --- a/data/mappings/SP800-53_rev4-to-rev5.mapping.json +++ /dev/null @@ -1,14950 +0,0 @@ -{ - "mapping-collection": { - "uuid": "3ceb9008-8f79-5e0f-9116-07366066db6a", - "metadata": { - "title": "NIST SP 800-53 Rev 4 \u2192 Rev 5 control mapping", - "last-modified": "2026-06-09T00:00:00Z", - "version": "1.0.0", - "oscal-version": "1.2.2", - "remarks": "Derived deterministically from the vendored NIST OSCAL Rev4 and Rev5 catalogs (data/catalogs/, see data/PROVENANCE.md). Same-id active controls are mapped equivalent; controls withdrawn in Rev5 follow the Rev5 catalog's own incorporated-into / moved-to link. Note: 'equivalent' is catalog-level id equivalence; a subset of same-id controls have substantive text changes between revisions (FedRAMP's Rev4\u2192Rev5 comparison flags these) and could be refined to intersects-with. RESIDUE \u2014 3 Rev4 control(s) with no clean single Rev5 successor (recorded, not silently dropped): cp-10.3 (withdrawn in Rev5 with no successor (NIST: addressed generally / N-A)); sa-12 (withdrawn; incorporated into 'sr' (family-level, not a single control)); sc-19 (withdrawn in Rev5 with no successor (NIST: addressed generally / N-A))." - }, - "provenance": { - "method": "automation", - "matching-rationale": "syntactic", - "status": "complete", - "mapping-description": "NIST SP 800-53 Rev 4 to Rev 5 control mapping, derived deterministically (automation) from the two vendored NIST OSCAL catalogs: same-id active controls map equivalent; controls withdrawn in Rev5 follow the Rev5 catalog's own incorporated-into / moved-to link. No hand-keyed crosswalk." - }, - "mappings": [ - { - "uuid": "465a8049-0174-5221-bde8-8828f37a2458", - "source-resource": { - "type": "resource", - "href": "#resource-rev4-catalog" - }, - "target-resource": { - "type": "resource", - "href": "#resource-rev5-catalog" - }, - "maps": [ - { - "uuid": "6df69211-dac2-5dda-9fdd-e2a479808584", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-1" - } - ] - }, - { - "uuid": "09be65d5-5932-5cd1-809d-168a56745d3a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-10" - } - ] - }, - { - "uuid": "e0386a52-5fa6-5cca-816a-3e21f5bef9ac", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-11" - } - ] - }, - { - "uuid": "283c7da3-1baa-5890-a333-355fa9a91514", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-11.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-11.1" - } - ] - }, - { - "uuid": "4998958a-6b23-5251-bce7-9bf7a95cfa53", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-12" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-12" - } - ] - }, - { - "uuid": "c3809c19-2636-5b9c-8508-aec728a8ab59", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-12.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-12.1" - } - ] - }, - { - "uuid": "74ca919b-47b8-521b-879e-3d10b28c6c8e", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ac-13" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-2" - } - ], - "remarks": "Rev4 ac-13 withdrawn in Rev5; NIST disposition: incorporated-into ac-2." - }, - { - "uuid": "f723b18f-9f81-545a-ab64-1e4bef9fc4fb", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-14" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-14" - } - ] - }, - { - "uuid": "33977857-9069-5671-8900-9d5856a8aca7", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ac-14.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-14" - } - ], - "remarks": "Rev4 ac-14.1 withdrawn in Rev5; NIST disposition: incorporated-into ac-14." - }, - { - "uuid": "16764517-1fb4-5ab8-9e42-675e3939fc61", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ac-15" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-3" - } - ], - "remarks": "Rev4 ac-15 withdrawn in Rev5; NIST disposition: incorporated-into mp-3." - }, - { - "uuid": "25dca3c7-af28-5006-95e2-fd5a2ca8de81", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-16" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-16" - } - ] - }, - { - "uuid": "1925b932-ada8-527e-ac36-1cf65a3a8aeb", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-16.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-16.1" - } - ] - }, - { - "uuid": "1fe7e1b8-3ea5-5766-81de-1d55db253b0a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-16.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-16.10" - } - ] - }, - { - "uuid": "2d8df189-ea1f-5eff-a7dd-c7be0525b3d2", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-16.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-16.2" - } - ] - }, - { - "uuid": "a3e68e0f-1b90-5b2a-bdd3-1dee6798f2f3", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-16.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-16.3" - } - ] - }, - { - "uuid": "65253c41-6604-5426-984c-6bafc5867acf", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-16.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-16.4" - } - ] - }, - { - "uuid": "bcd12321-8117-5dbc-9449-910def51cd38", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-16.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-16.5" - } - ] - }, - { - "uuid": "b4fd7114-1240-54b5-9b14-1e9953d662fb", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-16.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-16.6" - } - ] - }, - { - "uuid": "42ac6743-eb26-5b83-888a-f4f70791490e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-16.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-16.7" - } - ] - }, - { - "uuid": "b0d2ffaa-0d44-5254-a345-0f4a911fd4ac", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-16.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-16.8" - } - ] - }, - { - "uuid": "3c03f26e-6fb5-5231-a193-6572fe091e88", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-16.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-16.9" - } - ] - }, - { - "uuid": "6b8b3a14-d25e-53c1-8fe5-18e16e1fe76b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-17" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-17" - } - ] - }, - { - "uuid": "4186bcc0-ec0a-5f1d-9840-72dba0f24996", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-17.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-17.1" - } - ] - }, - { - "uuid": "8d2b4700-d0bd-567f-b57a-9cac25406526", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-17.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-17.2" - } - ] - }, - { - "uuid": "c60ceb31-fbab-57bb-981d-e24824fca341", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-17.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-17.3" - } - ] - }, - { - "uuid": "c2aadcee-3876-5acf-9a89-38a1ef0fdf53", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-17.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-17.4" - } - ] - }, - { - "uuid": "821d7ba4-d2df-5e56-bc53-a9b4513e98c7", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ac-17.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4" - } - ], - "remarks": "Rev4 ac-17.5 withdrawn in Rev5; NIST disposition: incorporated-into si-4." - }, - { - "uuid": "7ac276b1-c77b-53a7-8177-b40f0d6bae15", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-17.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-17.6" - } - ] - }, - { - "uuid": "d65d1779-3c78-5c0b-91b8-158cd112518f", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ac-17.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-3.10" - } - ], - "remarks": "Rev4 ac-17.7 withdrawn in Rev5; NIST disposition: incorporated-into ac-3.10." - }, - { - "uuid": "bf19ea80-3640-547e-a162-f47d94f5315b", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ac-17.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-7" - } - ], - "remarks": "Rev4 ac-17.8 withdrawn in Rev5; NIST disposition: incorporated-into cm-7." - }, - { - "uuid": "f7e7cb37-f7dd-5e2d-9799-e60599a985e4", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-17.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-17.9" - } - ] - }, - { - "uuid": "783331b9-674c-54dc-8db8-7216e7a53b0a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-18" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-18" - } - ] - }, - { - "uuid": "0427a34b-e6b4-5a00-b13d-858bac9ba332", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-18.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-18.1" - } - ] - }, - { - "uuid": "7bf2291b-661c-5994-b5f8-a5074672b961", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ac-18.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4" - } - ], - "remarks": "Rev4 ac-18.2 withdrawn in Rev5; NIST disposition: incorporated-into si-4." - }, - { - "uuid": "5b9502cf-598a-5033-bd41-afda9e30dcde", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-18.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-18.3" - } - ] - }, - { - "uuid": "efb64c93-d3c7-534f-a574-4a08f015a7d1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-18.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-18.4" - } - ] - }, - { - "uuid": "72457909-eeb5-5cb0-8eb0-5a49fbccd95b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-18.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-18.5" - } - ] - }, - { - "uuid": "08c9606f-e5f2-5e46-a84e-e3b583053c43", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-19" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-19" - } - ] - }, - { - "uuid": "8a926ee1-4f0d-52eb-8d7f-ccc4132dbfee", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ac-19.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-7" - } - ], - "remarks": "Rev4 ac-19.1 withdrawn in Rev5; NIST disposition: incorporated-into mp-7." - }, - { - "uuid": "98e9ee45-c174-5ecb-84f7-cc6374f9e2d4", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ac-19.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-7" - } - ], - "remarks": "Rev4 ac-19.2 withdrawn in Rev5; NIST disposition: incorporated-into mp-7." - }, - { - "uuid": "cb9bb084-a5d2-56bc-a90d-7cae39ddcfc2", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ac-19.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-7" - } - ], - "remarks": "Rev4 ac-19.3 withdrawn in Rev5; NIST disposition: incorporated-into mp-7." - }, - { - "uuid": "da23be39-205d-51bc-a8b2-50f2824b12c7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-19.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-19.4" - } - ] - }, - { - "uuid": "775a0198-cdd0-5eab-89cb-84693e038fea", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-19.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-19.5" - } - ] - }, - { - "uuid": "52d8bc01-4a88-5c91-8a97-2ea12ef863c2", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-2" - } - ] - }, - { - "uuid": "ee0e0bb9-5753-5cc7-8fdb-6cb09ff7c14f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-2.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-2.1" - } - ] - }, - { - "uuid": "b132bff2-8dea-582e-8b03-6c999047c823", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ac-2.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-2" - } - ], - "remarks": "Rev4 ac-2.10 withdrawn in Rev5; NIST disposition: incorporated-into ac-2." - }, - { - "uuid": "3e00045a-747d-5fbd-8949-764ef67687b3", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-2.11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-2.11" - } - ] - }, - { - "uuid": "643e0d9d-0391-53d9-a996-076e359d7a72", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-2.12" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-2.12" - } - ] - }, - { - "uuid": "e625cbe5-b520-5b88-b36e-25a56a7efb4f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-2.13" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-2.13" - } - ] - }, - { - "uuid": "4dd546d1-f844-5b0d-9888-dbff4198e860", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-2.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-2.2" - } - ] - }, - { - "uuid": "2a1eed65-bd42-5287-86f7-973d2a348cda", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-2.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-2.3" - } - ] - }, - { - "uuid": "1fd9dc5e-aed5-5a9f-b4c5-c537a2459bf1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-2.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-2.4" - } - ] - }, - { - "uuid": "5db0f961-2990-572e-aba6-28e3e2637386", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-2.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-2.5" - } - ] - }, - { - "uuid": "d446496c-0985-5bae-b312-65d40c7115c4", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-2.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-2.6" - } - ] - }, - { - "uuid": "3f2c118d-ebbd-5df2-b552-347028f54e2c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-2.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-2.7" - } - ] - }, - { - "uuid": "1e10e9d7-45cf-5c5e-8c2c-ac8f8c730408", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-2.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-2.8" - } - ] - }, - { - "uuid": "94b59f1c-c94a-5208-acfb-8eb46142e42f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-2.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-2.9" - } - ] - }, - { - "uuid": "61c4bb38-8dc0-52f6-a80e-3a05c95bb25f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-20" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-20" - } - ] - }, - { - "uuid": "749f0da3-88ff-5567-84eb-7d3e19f4a4b6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-20.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-20.1" - } - ] - }, - { - "uuid": "9e5cc218-ad32-59c6-a52c-e8b67cdc3dab", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-20.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-20.2" - } - ] - }, - { - "uuid": "5a1f447e-bd9a-5049-9e42-d8caf309f4eb", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-20.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-20.3" - } - ] - }, - { - "uuid": "ebf51777-470e-523e-a5f2-6f379d1cab03", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-20.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-20.4" - } - ] - }, - { - "uuid": "e41bf30c-97b1-5a68-8e77-a777f67461bb", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-21" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-21" - } - ] - }, - { - "uuid": "a8320a81-b733-5efd-ab75-a96db0d5bbb4", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-21.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-21.1" - } - ] - }, - { - "uuid": "52d40caf-9637-5042-a9d1-5f9ed831af40", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-21.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-21.2" - } - ] - }, - { - "uuid": "291690ec-d366-5b00-8a30-e8d9d40222e9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-22" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-22" - } - ] - }, - { - "uuid": "d6e49ed1-7688-543e-9d0c-dd99b25e7a2c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-23" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-23" - } - ] - }, - { - "uuid": "42b96994-eeb4-5e5d-ae95-d1ff8a5a8b74", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-24" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-24" - } - ] - }, - { - "uuid": "3543b490-c0c0-5977-b235-b1796d8a795a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-24.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-24.1" - } - ] - }, - { - "uuid": "38f0ccd5-1ce1-5a03-a9fe-1b24dd552a0e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-24.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-24.2" - } - ] - }, - { - "uuid": "65508379-302a-5263-b7e1-56cc1c2e3091", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-25" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-25" - } - ] - }, - { - "uuid": "71e73d25-72ce-5391-a596-e69e151835fb", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-3" - } - ] - }, - { - "uuid": "bd244882-78fc-5ab8-bd37-b452a29a0423", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ac-3.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6" - } - ], - "remarks": "Rev4 ac-3.1 withdrawn in Rev5; NIST disposition: incorporated-into ac-6." - }, - { - "uuid": "61e8eade-dfd4-5143-ad9f-efa3313a18e2", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-3.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-3.10" - } - ] - }, - { - "uuid": "aad9515a-3909-5cd0-b953-0d810d085df8", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-3.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-3.2" - } - ] - }, - { - "uuid": "e45feaeb-4c55-56b2-855b-1bfe6c49ff5a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-3.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-3.3" - } - ] - }, - { - "uuid": "47913198-70ec-51e2-92d7-64fc080739d0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-3.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-3.4" - } - ] - }, - { - "uuid": "eb854d67-9071-5ba4-93d2-c6a5c3b4b1bd", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-3.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-3.5" - } - ] - }, - { - "uuid": "d41f77df-e030-5e34-baa6-57c3111171ce", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ac-3.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-4" - } - ], - "remarks": "Rev4 ac-3.6 withdrawn in Rev5; NIST disposition: incorporated-into mp-4." - }, - { - "uuid": "43cb8404-4335-530d-86e1-077c50e235d6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-3.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-3.7" - } - ] - }, - { - "uuid": "30d8a716-afa0-5d05-b003-1688541045a0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-3.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-3.8" - } - ] - }, - { - "uuid": "db5f5bc3-9b53-517f-89ca-ba4b4e02ed12", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-3.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-3.9" - } - ] - }, - { - "uuid": "e0524850-20fa-5a38-bab1-b7b097ccf134", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4" - } - ] - }, - { - "uuid": "1916708d-9474-51e0-9321-5b719c58a4ff", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.1" - } - ] - }, - { - "uuid": "e79a1a5d-f2b1-5d91-a2e4-6e48005fb2d3", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.10" - } - ] - }, - { - "uuid": "5bc2fbd5-eb09-5984-9caf-1bff0ea43c41", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.11" - } - ] - }, - { - "uuid": "46ab8336-1e07-5a44-97cc-092bf1df72d8", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.12" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.12" - } - ] - }, - { - "uuid": "08a8eeca-6413-531a-9579-09ff7e18949c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.13" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.13" - } - ] - }, - { - "uuid": "40d40592-2b48-553d-961b-fb9514169419", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.14" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.14" - } - ] - }, - { - "uuid": "dc633e36-9b01-5a94-bae2-df2128d272da", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.15" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.15" - } - ] - }, - { - "uuid": "2e26c369-dbf2-586b-9cc2-6d0d1435f342", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.16" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4" - } - ], - "remarks": "Rev4 ac-4.16 withdrawn in Rev5; NIST disposition: incorporated-into ac-4." - }, - { - "uuid": "dc6d6fe7-38bf-5474-9ae6-22be74a3a5c6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.17" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.17" - } - ] - }, - { - "uuid": "cb11a60e-70ae-5f33-869b-0119aeed2dd2", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.18" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-16" - } - ], - "remarks": "Rev4 ac-4.18 withdrawn in Rev5; NIST disposition: incorporated-into ac-16." - }, - { - "uuid": "f87d5ba5-96ac-5704-a3d2-40d18c62f50b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.19" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.19" - } - ] - }, - { - "uuid": "96583538-0814-55dc-8b5c-557ab94a08df", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.2" - } - ] - }, - { - "uuid": "12dc6d3f-1899-53cd-b603-fb0bdcee35e5", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.20" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.20" - } - ] - }, - { - "uuid": "b5453cb2-7b11-5e73-8350-50dfbcf0604f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.21" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.21" - } - ] - }, - { - "uuid": "343def9d-22c1-5066-9877-8e808de14780", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.22" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.22" - } - ] - }, - { - "uuid": "16eb4e51-72ed-5412-b9fe-dfdd59610cbc", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.3" - } - ] - }, - { - "uuid": "97256f86-95ac-529d-bab3-769446706531", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.4" - } - ] - }, - { - "uuid": "6dcd45a7-4d12-5d7b-bd02-36c8cac322f8", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.5" - } - ] - }, - { - "uuid": "dc2640be-2bfb-503b-8c84-5dd9a76e494b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.6" - } - ] - }, - { - "uuid": "912070ab-d459-548a-b565-83d8f5474c98", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.7" - } - ] - }, - { - "uuid": "b7c404b8-36a9-56ed-8287-bab6667f5129", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.8" - } - ] - }, - { - "uuid": "4525ca4e-2762-5999-83ce-bf6a90dd76d3", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-4.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-4.9" - } - ] - }, - { - "uuid": "220083c3-57fb-57f5-b8b5-a10b6bfe3fb5", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-5" - } - ] - }, - { - "uuid": "9804ab1d-b234-5b83-b6b4-0f32334b1fe6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6" - } - ] - }, - { - "uuid": "f3d49243-12e4-5e40-b425-031049b52528", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-6.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6.1" - } - ] - }, - { - "uuid": "d6f90ac3-3194-53fd-9207-468bf19a91da", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-6.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6.10" - } - ] - }, - { - "uuid": "02afb41f-cb7c-5cbb-9cfd-94f219e5f13d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-6.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6.2" - } - ] - }, - { - "uuid": "f530935b-5221-53bd-932d-ad9b4696aca8", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-6.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6.3" - } - ] - }, - { - "uuid": "8ba31eaf-deb9-511c-9082-5592704dd9e9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-6.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6.4" - } - ] - }, - { - "uuid": "a7c5d754-a5b4-57a2-b6e4-7b1b09512d87", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-6.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6.5" - } - ] - }, - { - "uuid": "3c98a5b5-aa9a-5c5a-93b2-d10aa8705543", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-6.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6.6" - } - ] - }, - { - "uuid": "d17d015d-3891-50ba-b598-8f6b0aed09a9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-6.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6.7" - } - ] - }, - { - "uuid": "dd3c1162-b8e5-5a3b-b755-2e4aed99b4e3", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-6.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6.8" - } - ] - }, - { - "uuid": "e7e6e72c-d3c4-536f-b767-a8cc915967c5", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-6.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6.9" - } - ] - }, - { - "uuid": "55f039e9-c6a4-5b4e-9ce9-0fa6dfd4bf08", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-7" - } - ] - }, - { - "uuid": "0058067f-ff5e-50d0-a708-cd72a3bedb11", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ac-7.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-7" - } - ], - "remarks": "Rev4 ac-7.1 withdrawn in Rev5; NIST disposition: incorporated-into ac-7." - }, - { - "uuid": "ab88da82-cc02-5f56-8f46-cfdba38e2e12", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-7.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-7.2" - } - ] - }, - { - "uuid": "34598cb3-8b5a-5bcd-97a9-462d935c91f8", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-8" - } - ] - }, - { - "uuid": "094980ac-d63e-5e15-9d1e-3a21b562abc6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-9" - } - ] - }, - { - "uuid": "0edf7a18-34a7-53e3-9863-64b643eaf0bf", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-9.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-9.1" - } - ] - }, - { - "uuid": "43ca8045-63c4-5649-848e-010828fbe26c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-9.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-9.2" - } - ] - }, - { - "uuid": "d9364a54-c93f-5864-824a-83bb4cc1f8dd", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-9.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-9.3" - } - ] - }, - { - "uuid": "fa78b128-4b71-550a-b9fa-b9cddf15b864", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ac-9.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-9.4" - } - ] - }, - { - "uuid": "dc3fb068-3919-53c8-b439-3c1d41b8c27a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "at-1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "at-1" - } - ] - }, - { - "uuid": "31c2fab0-ea5e-556a-8a12-b3db6a9f204e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "at-2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "at-2" - } - ] - }, - { - "uuid": "8f7f292b-8b93-59ae-9c0a-7be383569158", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "at-2.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "at-2.1" - } - ] - }, - { - "uuid": "b2407412-3fa0-5ecb-a7ff-eb5045f94d39", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "at-2.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "at-2.2" - } - ] - }, - { - "uuid": "aad4cb9b-6ad7-57fd-a93c-673e7e0b33df", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "at-3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "at-3" - } - ] - }, - { - "uuid": "abfc87bc-2fc8-5efa-a44b-9b0f9302b033", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "at-3.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "at-3.1" - } - ] - }, - { - "uuid": "09d0bc74-4794-5079-962c-3accf663be22", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "at-3.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "at-3.2" - } - ] - }, - { - "uuid": "7d6f812a-aaa9-5e9e-bc79-636bc1c94739", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "at-3.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "at-3.3" - } - ] - }, - { - "uuid": "eb9ada16-cbe2-5e37-9a67-d1e9ee0b6a30", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "at-3.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "at-2.4" - } - ], - "remarks": "Rev4 at-3.4 withdrawn in Rev5; NIST disposition: moved-to at-2.4." - }, - { - "uuid": "0dbf276f-1bfb-5d70-9648-6217482421b3", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "at-4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "at-4" - } - ] - }, - { - "uuid": "2832990c-cc19-5073-816f-3271549bbcad", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "at-5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pm-15" - } - ], - "remarks": "Rev4 at-5 withdrawn in Rev5; NIST disposition: incorporated-into pm-15." - }, - { - "uuid": "ea173466-7bc6-5f7e-9109-c52ac52f0511", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-1" - } - ] - }, - { - "uuid": "0207a619-7a3b-546a-aca3-f54576726595", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-10" - } - ] - }, - { - "uuid": "619a0ca3-bb1b-594c-bf35-ce73888fed3a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-10.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-10.1" - } - ] - }, - { - "uuid": "d0ad0c44-a1de-5631-9add-7689724a3465", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-10.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-10.2" - } - ] - }, - { - "uuid": "1bdd8463-2986-5e32-b1fe-3d56d243d193", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-10.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-10.3" - } - ] - }, - { - "uuid": "e39e4ad3-81fc-5fea-b1ce-48f9d9c40c66", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-10.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-10.4" - } - ] - }, - { - "uuid": "730a6861-a86a-5867-b56a-3c81c7224221", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "au-10.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-7" - } - ], - "remarks": "Rev4 au-10.5 withdrawn in Rev5; NIST disposition: incorporated-into si-7." - }, - { - "uuid": "f8a3d25c-9b0d-5a3e-b469-16c32665a375", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-11" - } - ] - }, - { - "uuid": "71fab5c4-373e-59ec-a10e-3db2c42c572c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-11.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-11.1" - } - ] - }, - { - "uuid": "aed1e43c-6810-54e9-8837-60f7344c043d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-12" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-12" - } - ] - }, - { - "uuid": "9887c4e7-5cae-5e76-9ce1-3d793eb5f1f1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-12.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-12.1" - } - ] - }, - { - "uuid": "ca5701a6-32fa-57a7-aa37-195ae8ccced1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-12.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-12.2" - } - ] - }, - { - "uuid": "689f6d4e-fbe1-536d-aaee-972e8bcb98b1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-12.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-12.3" - } - ] - }, - { - "uuid": "ce6732f3-4665-5caf-bfdc-e36759c9142d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-13" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-13" - } - ] - }, - { - "uuid": "b7b60600-661a-5473-a31f-486f0e12f709", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-13.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-13.1" - } - ] - }, - { - "uuid": "d192bfce-baca-5864-a760-19dfd6e1bed7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-13.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-13.2" - } - ] - }, - { - "uuid": "f3508662-8241-5785-94ec-46d63feac178", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-14" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-14" - } - ] - }, - { - "uuid": "405ddc00-0454-5419-84f5-d8e48bbba281", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-14.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-14.1" - } - ] - }, - { - "uuid": "1e5e95a1-2a24-5a07-be50-ccc25babf68b", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "au-14.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-14" - } - ], - "remarks": "Rev4 au-14.2 withdrawn in Rev5; NIST disposition: incorporated-into au-14." - }, - { - "uuid": "1e610ef9-ace3-531c-895a-e37004a3481b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-14.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-14.3" - } - ] - }, - { - "uuid": "279cec36-3d95-5914-a23d-148918df4a84", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-15" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-5.5" - } - ], - "remarks": "Rev4 au-15 withdrawn in Rev5; NIST disposition: moved-to au-5.5." - }, - { - "uuid": "a4ce5539-607f-5f10-9fd0-1e5788cb5329", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-16" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-16" - } - ] - }, - { - "uuid": "c960b60b-ccfd-58fa-b5b4-2a22aae71357", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-16.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-16.1" - } - ] - }, - { - "uuid": "26429e30-a789-5703-8a28-c5271cfff31a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-16.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-16.2" - } - ] - }, - { - "uuid": "166e7840-34c1-53a8-883c-485f95c6f5ea", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-2" - } - ] - }, - { - "uuid": "73fc77c3-33e6-5024-aec3-c8ed10f40d11", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "au-2.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-12" - } - ], - "remarks": "Rev4 au-2.1 withdrawn in Rev5; NIST disposition: incorporated-into au-12." - }, - { - "uuid": "2d53e189-1239-5e01-b220-da9905f82721", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "au-2.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-12" - } - ], - "remarks": "Rev4 au-2.2 withdrawn in Rev5; NIST disposition: incorporated-into au-12." - }, - { - "uuid": "4f3e5e71-040e-548e-9f0a-bee1f5f16375", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "au-2.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-2" - } - ], - "remarks": "Rev4 au-2.3 withdrawn in Rev5; NIST disposition: incorporated-into au-2." - }, - { - "uuid": "74d6b350-e7a0-59b9-ae51-0a94318a8e55", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "au-2.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6.9" - } - ], - "remarks": "Rev4 au-2.4 withdrawn in Rev5; NIST disposition: incorporated-into ac-6.9." - }, - { - "uuid": "4c08e113-9ad5-5203-a4d8-1b8640670d3f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-3" - } - ] - }, - { - "uuid": "a462ab87-962a-5a7f-8768-83bde0d87ccb", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-3.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-3.1" - } - ] - }, - { - "uuid": "e62cfa6c-c408-5e44-af0e-eedf9b87eabc", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "au-3.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-9" - } - ], - "remarks": "Rev4 au-3.2 withdrawn in Rev5; NIST disposition: incorporated-into pl-9." - }, - { - "uuid": "f766aa67-5a62-539f-93e1-e9a02fc1135f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-4" - } - ] - }, - { - "uuid": "f8d4c63d-3cc8-507b-a477-d28f23a20be1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-4.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-4.1" - } - ] - }, - { - "uuid": "36fa49fc-f591-5d2e-a618-c736b21d9d81", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-5" - } - ] - }, - { - "uuid": "c4498ed2-5957-5ffe-a87e-6780d5f4f2ed", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-5.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-5.1" - } - ] - }, - { - "uuid": "0f95baf6-a79b-56a1-908c-0b6a61dcf59d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-5.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-5.2" - } - ] - }, - { - "uuid": "452d2e91-4796-5206-8393-5b6cbee680da", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-5.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-5.3" - } - ] - }, - { - "uuid": "e248d73c-0a1d-5e02-a4c2-191fe9f8944a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-5.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-5.4" - } - ] - }, - { - "uuid": "70b92b44-b777-5a15-8f99-0eaceb7b8837", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-6" - } - ] - }, - { - "uuid": "39f66c52-24ee-50c4-a4f4-026b4a4c3d19", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-6.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-6.1" - } - ] - }, - { - "uuid": "d47bd814-ec5c-597e-bfb6-e4d3b8d84893", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "au-6.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-6" - } - ], - "remarks": "Rev4 au-6.10 withdrawn in Rev5; NIST disposition: incorporated-into au-6." - }, - { - "uuid": "689de090-357d-5df3-a669-684fdcbcfc69", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "au-6.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4" - } - ], - "remarks": "Rev4 au-6.2 withdrawn in Rev5; NIST disposition: incorporated-into si-4." - }, - { - "uuid": "c6f7fb00-40f2-5225-aa13-971a9c1208c9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-6.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-6.3" - } - ] - }, - { - "uuid": "79815ff5-411a-5b95-b3ba-79b8089294c8", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-6.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-6.4" - } - ] - }, - { - "uuid": "d6ac3b41-9c96-5beb-9e08-7f0218a1f02e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-6.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-6.5" - } - ] - }, - { - "uuid": "6c3848e0-c1e2-5166-9429-aaa65b75bf1c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-6.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-6.6" - } - ] - }, - { - "uuid": "85a0d66a-2460-5620-85bd-5bedc1acb19f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-6.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-6.7" - } - ] - }, - { - "uuid": "e3de47d0-86c1-5872-bba6-c967d75db6c1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-6.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-6.8" - } - ] - }, - { - "uuid": "726e91b9-5c12-5868-b40f-6ff552887708", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-6.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-6.9" - } - ] - }, - { - "uuid": "a615f07e-2ccc-561d-b59c-1364dc06e676", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-7" - } - ] - }, - { - "uuid": "9d8c1781-3342-59fb-a6f1-4da8303b08e6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-7.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-7.1" - } - ] - }, - { - "uuid": "2fcc5bcc-bc35-5264-a7a5-741d979a6982", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "au-7.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-7.1" - } - ], - "remarks": "Rev4 au-7.2 withdrawn in Rev5; NIST disposition: incorporated-into au-7.1." - }, - { - "uuid": "dc910aeb-9856-5626-ad6b-18c63d1709fe", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-8" - } - ] - }, - { - "uuid": "82802bbe-b0dd-59fa-8b9b-a7fb4cda83d0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-8.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-45.1" - } - ], - "remarks": "Rev4 au-8.1 withdrawn in Rev5; NIST disposition: moved-to sc-45.1." - }, - { - "uuid": "418c33f2-e8d0-5867-95b3-b0592fb87461", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-8.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-45.2" - } - ], - "remarks": "Rev4 au-8.2 withdrawn in Rev5; NIST disposition: moved-to sc-45.2." - }, - { - "uuid": "67c724d4-1115-5ac3-94cb-81ce7800540e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-9" - } - ] - }, - { - "uuid": "88410565-f821-54a0-b390-1e48466b2316", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-9.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-9.1" - } - ] - }, - { - "uuid": "cee0e442-d99b-5412-b3e8-39c27b4c4bae", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-9.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-9.2" - } - ] - }, - { - "uuid": "9cb26610-23c9-5933-a15a-2bbd842fa034", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-9.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-9.3" - } - ] - }, - { - "uuid": "abe56e3b-255d-557d-bcad-733683b20d17", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-9.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-9.4" - } - ] - }, - { - "uuid": "51bfea72-5844-5c59-ba3b-fb7b0f086c4f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-9.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-9.5" - } - ] - }, - { - "uuid": "a95543d3-c85c-58ea-a67b-6f96cb08ecf3", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "au-9.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "au-9.6" - } - ] - }, - { - "uuid": "fa7f5b04-caae-5e93-8eb4-059d50016056", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-1" - } - ] - }, - { - "uuid": "dbed7000-9461-5064-95cb-495e11583412", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-2" - } - ] - }, - { - "uuid": "4ddf0e3d-aec2-5905-877f-e703e6c5a1d0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-2.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-2.1" - } - ] - }, - { - "uuid": "827242c9-acfa-54ad-8a73-3f6e3704149b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-2.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-2.2" - } - ] - }, - { - "uuid": "24dca9af-9552-57ae-9145-5f6664eccfcc", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-2.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-2.3" - } - ] - }, - { - "uuid": "baeb1f75-6a42-5f63-a67d-2aacfc0389a1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-3" - } - ] - }, - { - "uuid": "30c8b38d-b4f4-5be1-b89e-c8be6dae848d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-3.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.25" - } - ], - "remarks": "Rev4 ca-3.1 withdrawn in Rev5; NIST disposition: moved-to sc-7.25." - }, - { - "uuid": "fe474de2-f6bd-5083-8c91-3447a3decd35", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-3.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.26" - } - ], - "remarks": "Rev4 ca-3.2 withdrawn in Rev5; NIST disposition: moved-to sc-7.26." - }, - { - "uuid": "d21d2598-183d-5f55-95e5-84ea574dd016", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-3.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.27" - } - ], - "remarks": "Rev4 ca-3.3 withdrawn in Rev5; NIST disposition: moved-to sc-7.27." - }, - { - "uuid": "ca01ddef-c4eb-56d2-b304-668bbca52b25", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-3.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.28" - } - ], - "remarks": "Rev4 ca-3.4 withdrawn in Rev5; NIST disposition: moved-to sc-7.28." - }, - { - "uuid": "5c47a0e2-35be-5fb3-ab8f-3e2557a7e905", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-3.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.5" - } - ], - "remarks": "Rev4 ca-3.5 withdrawn in Rev5; NIST disposition: moved-to sc-7.5." - }, - { - "uuid": "f5c91efa-0d07-5601-aa34-678d07622a10", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ca-4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-2" - } - ], - "remarks": "Rev4 ca-4 withdrawn in Rev5; NIST disposition: incorporated-into ca-2." - }, - { - "uuid": "3df39104-1adf-5799-923c-789303680825", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-5" - } - ] - }, - { - "uuid": "211282cd-9861-5c19-b1b6-954e6161b1d5", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-5.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-5.1" - } - ] - }, - { - "uuid": "d4d69b7d-8320-50f9-9733-cd2c346b0c42", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-6" - } - ] - }, - { - "uuid": "656f410b-97e5-5b77-887c-edfddddd71f7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-7" - } - ] - }, - { - "uuid": "5d770a3e-beec-53fd-91dc-b31af879fb8e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-7.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-7.1" - } - ] - }, - { - "uuid": "b3935820-ab8a-5d56-b77b-ec6ba5e9e0f4", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ca-7.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-2" - } - ], - "remarks": "Rev4 ca-7.2 withdrawn in Rev5; NIST disposition: incorporated-into ca-2." - }, - { - "uuid": "945971c7-c6d3-5dcc-9a01-88db42a0348d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-7.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-7.3" - } - ] - }, - { - "uuid": "2bd0f021-d97e-5035-bfc7-8a7c28509cdf", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-8" - } - ] - }, - { - "uuid": "8869bae8-1292-594e-bf8e-a541a042b4b2", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-8.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-8.1" - } - ] - }, - { - "uuid": "67347494-8cc7-538c-8dd4-ef6a050baafa", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-8.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-8.2" - } - ] - }, - { - "uuid": "c38d5275-6c20-510f-81b9-cd4a8ef465f5", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-9" - } - ] - }, - { - "uuid": "108fd2ed-58bf-508c-9a53-741ead22c31f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ca-9.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-9.1" - } - ] - }, - { - "uuid": "9e97f7a0-4fd1-53f2-be66-8d45c5e40049", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-1" - } - ] - }, - { - "uuid": "e2b07f4f-6a3b-5c28-95a8-bfd0dae74016", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-10" - } - ] - }, - { - "uuid": "33d0dd17-ef7a-5f14-8a0c-6de7a905b313", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-10.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-10.1" - } - ] - }, - { - "uuid": "080177fc-f224-5e11-9688-7c79aa177931", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-11" - } - ] - }, - { - "uuid": "1cdec3de-8df4-5122-9a6e-53f16eab1ab8", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "cm-11.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-8.3" - } - ], - "remarks": "Rev4 cm-11.1 withdrawn in Rev5; NIST disposition: incorporated-into cm-8.3." - }, - { - "uuid": "cb0f98c5-cfe3-5226-b393-275751d56cb3", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-11.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-11.2" - } - ] - }, - { - "uuid": "dcd268d0-f57d-5ce5-b36e-828caadecadb", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-2" - } - ] - }, - { - "uuid": "d1f843b8-7b74-550d-a644-6ab71de22d2e", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "cm-2.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-2" - } - ], - "remarks": "Rev4 cm-2.1 withdrawn in Rev5; NIST disposition: incorporated-into cm-2." - }, - { - "uuid": "9e3f7b00-fd0c-5fea-94cf-e10098a56075", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-2.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-2.2" - } - ] - }, - { - "uuid": "18212f09-b7aa-563a-8e6c-2d94589d40fa", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-2.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-2.3" - } - ] - }, - { - "uuid": "700bc36a-da61-5d39-8fb7-a0ffeb37960a", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "cm-2.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-7.4" - } - ], - "remarks": "Rev4 cm-2.4 withdrawn in Rev5; NIST disposition: incorporated-into cm-7.4." - }, - { - "uuid": "c1367011-64db-5592-b14a-19a3cf1628e5", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "cm-2.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-7.5" - } - ], - "remarks": "Rev4 cm-2.5 withdrawn in Rev5; NIST disposition: incorporated-into cm-7.5." - }, - { - "uuid": "944edbdd-88e9-549c-9377-0809b42af8c9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-2.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-2.6" - } - ] - }, - { - "uuid": "702ddeb1-1519-5f58-8f92-2a9bcce59929", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-2.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-2.7" - } - ] - }, - { - "uuid": "4ae3b35f-3847-5e2e-aa1d-67a25cd0cafe", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-3" - } - ] - }, - { - "uuid": "4c2a1a37-01a5-524c-8b66-98e717445236", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-3.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-3.1" - } - ] - }, - { - "uuid": "643444d4-a9d9-5285-9c02-b8543fb150b4", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-3.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-3.2" - } - ] - }, - { - "uuid": "afd96fac-9355-53ca-8291-bd904ebf7d99", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-3.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-3.3" - } - ] - }, - { - "uuid": "cf0a0b6b-9c7d-5627-9088-69d9210a4a03", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-3.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-3.4" - } - ] - }, - { - "uuid": "53197cc4-dea1-58a6-9870-3b96ee52ea83", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-3.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-3.5" - } - ] - }, - { - "uuid": "d007af9b-f5e3-5bb9-9429-3ae97e12c72d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-3.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-3.6" - } - ] - }, - { - "uuid": "f70863f9-cc94-5c83-a315-5a37a08dfa54", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-4" - } - ] - }, - { - "uuid": "3b3ea58f-3e0c-595d-8308-f7d24e75bcba", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-4.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-4.1" - } - ] - }, - { - "uuid": "4c1fcf59-f1e0-59cd-97f8-999ade423d35", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-4.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-4.2" - } - ] - }, - { - "uuid": "a4bfa5d8-91d2-5443-80f8-e71658a90310", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-5" - } - ] - }, - { - "uuid": "dc62f298-e2cd-5cb9-830e-4f0faa375a5d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-5.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-5.1" - } - ] - }, - { - "uuid": "355bf47a-0dbb-5ab7-9cfe-4400924ff13b", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "cm-5.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-3.7" - } - ], - "remarks": "Rev4 cm-5.2 withdrawn in Rev5; NIST disposition: incorporated-into cm-3.7." - }, - { - "uuid": "90f194be-14d8-55ee-9f14-27d05f3c1144", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-5.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-14" - } - ], - "remarks": "Rev4 cm-5.3 withdrawn in Rev5; NIST disposition: moved-to cm-14." - }, - { - "uuid": "82d24905-2178-5f84-b488-c5b289c1297b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-5.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-5.4" - } - ] - }, - { - "uuid": "291461e8-2c62-5894-a9d3-fcaf68fc7d88", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-5.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-5.5" - } - ] - }, - { - "uuid": "3f47201e-f0b6-5717-8841-08bbbff837dd", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-5.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-5.6" - } - ] - }, - { - "uuid": "660bc0e7-c563-5dce-9260-e2ec10efed33", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "cm-5.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-7" - } - ], - "remarks": "Rev4 cm-5.7 withdrawn in Rev5; NIST disposition: incorporated-into si-7." - }, - { - "uuid": "96f7d9f8-d91d-5ad3-9022-9339335113df", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-6" - } - ] - }, - { - "uuid": "fad97e0e-7f7d-586a-b166-4f6d93ad7894", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-6.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-6.1" - } - ] - }, - { - "uuid": "58964dee-eb02-546b-b243-97cbec8c76ef", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-6.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-6.2" - } - ] - }, - { - "uuid": "009834a8-d6d4-5e1e-a51c-5f23541c0f28", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "cm-6.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-7" - } - ], - "remarks": "Rev4 cm-6.3 withdrawn in Rev5; NIST disposition: incorporated-into si-7." - }, - { - "uuid": "b5aa2ce8-7e81-52bd-b658-6b8106d4dbe4", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "cm-6.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-4" - } - ], - "remarks": "Rev4 cm-6.4 withdrawn in Rev5; NIST disposition: incorporated-into cm-4." - }, - { - "uuid": "a24fe262-598a-555f-9831-0c55d85ad8fd", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-7" - } - ] - }, - { - "uuid": "defab5a4-421b-5686-a00b-ad7a15e89e02", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-7.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-7.1" - } - ] - }, - { - "uuid": "37e48181-e94f-5249-8255-b6ffbfa19fde", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-7.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-7.2" - } - ] - }, - { - "uuid": "6ff8bab5-19ab-5456-b075-b70697eb28e7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-7.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-7.3" - } - ] - }, - { - "uuid": "53a4bc69-d796-50ea-b578-e8c2bf076b29", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-7.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-7.4" - } - ] - }, - { - "uuid": "7593cddb-bafa-5c90-98c8-5d1695084e25", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-7.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-7.5" - } - ] - }, - { - "uuid": "97aa4323-c9d8-5da4-bef2-4395195b821e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-8" - } - ] - }, - { - "uuid": "aad869c1-f92f-5c20-956d-67d23aef1119", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-8.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-8.1" - } - ] - }, - { - "uuid": "5764308a-1003-55d9-b094-43059263bb1d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-8.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-8.2" - } - ] - }, - { - "uuid": "a6548a52-7b44-55cc-b990-2264818107a6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-8.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-8.3" - } - ] - }, - { - "uuid": "85be7757-7b5b-5fe9-8372-05de3db65640", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-8.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-8.4" - } - ] - }, - { - "uuid": "7b746942-a9ee-5441-aec0-efdf8fdbae05", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "cm-8.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-8" - } - ], - "remarks": "Rev4 cm-8.5 withdrawn in Rev5; NIST disposition: incorporated-into cm-8." - }, - { - "uuid": "fb3db5bd-879f-5e82-93c8-c5b9dfb9304d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-8.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-8.6" - } - ] - }, - { - "uuid": "f9576600-189e-59de-96a6-015d24ace2d7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-8.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-8.7" - } - ] - }, - { - "uuid": "5756a71c-853d-57fd-b7cc-c5429357b9e6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-8.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-8.8" - } - ] - }, - { - "uuid": "b1090005-5cc2-5799-8be5-fcb4ddab7923", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-8.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-8.9" - } - ] - }, - { - "uuid": "01c268e8-14f2-59bd-96af-7418ed4bd9f9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-9" - } - ] - }, - { - "uuid": "c5116ab4-9a54-54ce-998a-3c4a5704e4e5", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cm-9.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-9.1" - } - ] - }, - { - "uuid": "b94daa89-3f2f-573c-b998-094e7a8df95a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-1" - } - ] - }, - { - "uuid": "d14cb560-9972-597c-b52d-748b2d70896b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-10" - } - ] - }, - { - "uuid": "34303a00-9407-5581-bfce-81f0197ac796", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "cp-10.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-4" - } - ], - "remarks": "Rev4 cp-10.1 withdrawn in Rev5; NIST disposition: incorporated-into cp-4." - }, - { - "uuid": "1a74ce5b-7502-5b06-8cd7-9fa31c007f91", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-10.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-10.2" - } - ] - }, - { - "uuid": "fa9cb36a-d232-5271-a830-cb26d5c6f4a1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-10.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-10.4" - } - ] - }, - { - "uuid": "dbbb45fb-de9d-5921-9e1a-6f732f445595", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "cp-10.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-13" - } - ], - "remarks": "Rev4 cp-10.5 withdrawn in Rev5; NIST disposition: incorporated-into si-13." - }, - { - "uuid": "b45b1552-6d44-53a6-b816-dccef6ad20c7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-10.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-10.6" - } - ] - }, - { - "uuid": "e6581025-8df6-519a-b690-d1e277c4a745", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-11" - } - ] - }, - { - "uuid": "1dd064ba-fb12-5f66-84dd-c2e888a1fb48", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-12" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-12" - } - ] - }, - { - "uuid": "554e6c4f-bb60-5397-acf2-d44b6d6c2897", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-13" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-13" - } - ] - }, - { - "uuid": "51cc402e-2b47-5924-9aff-9fe52736e27d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-2" - } - ] - }, - { - "uuid": "01c90be0-fae9-58c8-b4bc-389064ba01a7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-2.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-2.1" - } - ] - }, - { - "uuid": "e73b4dc2-2d7a-5214-9ce2-8c3dd0fa7728", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-2.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-2.2" - } - ] - }, - { - "uuid": "07dc9df6-b523-5e3e-98fb-31b6681e9938", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-2.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-2.3" - } - ] - }, - { - "uuid": "d3b9a3a0-09c6-5755-ae19-5c5a671861df", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "cp-2.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-2.3" - } - ], - "remarks": "Rev4 cp-2.4 withdrawn in Rev5; NIST disposition: incorporated-into cp-2.3." - }, - { - "uuid": "7011605d-5b5f-582f-9949-6e3d903e8407", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-2.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-2.5" - } - ] - }, - { - "uuid": "dce63ffe-83c4-544b-9d61-4bab4910b954", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-2.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-2.6" - } - ] - }, - { - "uuid": "ea3d9254-a484-5b53-bbcb-f57daeabfad7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-2.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-2.7" - } - ] - }, - { - "uuid": "76f55ae5-90d9-5b1d-8eee-96ba36a6991a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-2.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-2.8" - } - ] - }, - { - "uuid": "97e320a2-ae22-5a35-ae35-489a13681b69", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-3" - } - ] - }, - { - "uuid": "ed5d2e7e-93c6-5bc4-822d-e8e80a7b8646", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-3.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-3.1" - } - ] - }, - { - "uuid": "b5adffef-fa1f-5ebd-97d8-c6a5d53ef062", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-3.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-3.2" - } - ] - }, - { - "uuid": "9c3d14d3-c6ab-510b-8e7d-c2b7ca9a3c5d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-4" - } - ] - }, - { - "uuid": "2d915ddb-19ff-5abb-a092-05df45ed2bc1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-4.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-4.1" - } - ] - }, - { - "uuid": "8a77624b-e666-5612-8eeb-c63792ec1a95", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-4.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-4.2" - } - ] - }, - { - "uuid": "3bc28abd-79ef-5c18-85e5-9af34a73232b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-4.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-4.3" - } - ] - }, - { - "uuid": "86824db4-8468-5a13-a757-931525e909f7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-4.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-4.4" - } - ] - }, - { - "uuid": "8f26a940-6f3e-504e-a06d-689f5cc9fdab", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "cp-5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-2" - } - ], - "remarks": "Rev4 cp-5 withdrawn in Rev5; NIST disposition: incorporated-into cp-2." - }, - { - "uuid": "6e34c671-9342-599f-92a0-4b0d5b4c4e75", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-6" - } - ] - }, - { - "uuid": "464f9860-5923-5e45-95f2-b51be54d3f9f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-6.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-6.1" - } - ] - }, - { - "uuid": "b47800a9-df1b-52b5-b999-3434491cbca4", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-6.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-6.2" - } - ] - }, - { - "uuid": "340b45ef-5c1b-5e85-8c95-00d5e0534ab1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-6.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-6.3" - } - ] - }, - { - "uuid": "f0992d1f-5489-5884-89a5-a3b93e96fdf0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-7" - } - ] - }, - { - "uuid": "3addaa3a-0e21-5df4-80f8-cae455dc5e4f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-7.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-7.1" - } - ] - }, - { - "uuid": "b31af9d1-f672-50b4-a722-8cc0306b6a87", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-7.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-7.2" - } - ] - }, - { - "uuid": "27673306-8c09-56d8-bff5-56194dcb2d47", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-7.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-7.3" - } - ] - }, - { - "uuid": "9971f30a-8a4f-541a-920f-07c91310c080", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-7.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-7.4" - } - ] - }, - { - "uuid": "e170ee6f-27bc-56da-9b74-487d90eb3a9c", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "cp-7.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-7" - } - ], - "remarks": "Rev4 cp-7.5 withdrawn in Rev5; NIST disposition: incorporated-into cp-7." - }, - { - "uuid": "221ef993-7120-5593-b04e-6c3e546d9053", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-7.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-7.6" - } - ] - }, - { - "uuid": "d3a77482-b7aa-5439-8436-2d7cff38e5de", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-8" - } - ] - }, - { - "uuid": "6a1900a0-90c2-5f3c-bc3a-60852a24edb1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-8.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-8.1" - } - ] - }, - { - "uuid": "8f33c868-355c-5343-9605-e90459ed5ff8", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-8.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-8.2" - } - ] - }, - { - "uuid": "4d51436b-6374-5a10-a337-e441aba64932", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-8.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-8.3" - } - ] - }, - { - "uuid": "1942866d-8b72-541a-9d49-3342252a30ee", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-8.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-8.4" - } - ] - }, - { - "uuid": "1dd907cd-1949-5748-88a2-8a74ad24b815", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-8.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-8.5" - } - ] - }, - { - "uuid": "e9453b0c-9951-5ab2-8a85-ee23a5f64fec", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-9" - } - ] - }, - { - "uuid": "75e0bbf5-d20e-5646-af03-b03754a41a19", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-9.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-9.1" - } - ] - }, - { - "uuid": "b24ada23-d7c3-54dc-b1fc-c2612d905824", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-9.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-9.2" - } - ] - }, - { - "uuid": "f1cde8d4-9578-5add-910a-d911cdbb8e1e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-9.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-9.3" - } - ] - }, - { - "uuid": "d03869ce-1bd8-5df9-b723-5b1f7232dea6", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "cp-9.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-9" - } - ], - "remarks": "Rev4 cp-9.4 withdrawn in Rev5; NIST disposition: incorporated-into cp-9." - }, - { - "uuid": "834d22d5-541a-5efc-9b85-d7e40d77a2a0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-9.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-9.5" - } - ] - }, - { - "uuid": "e390cb92-7e85-572b-b8b8-72a6e7bf90e0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-9.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-9.6" - } - ] - }, - { - "uuid": "d709b3c9-68ef-50a7-97c3-f77dc7aa2375", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "cp-9.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cp-9.7" - } - ] - }, - { - "uuid": "ec6188c6-8603-5ff5-8829-6085d511e8e9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-1" - } - ] - }, - { - "uuid": "a437fdaf-8a7d-54c1-9f2a-24cfd0b29631", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-10" - } - ] - }, - { - "uuid": "932261cb-0a13-5629-9214-a15bdfe12614", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-11" - } - ] - }, - { - "uuid": "ca7cc30e-f93b-5b9f-b9f6-0ceceaca4a80", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2" - } - ] - }, - { - "uuid": "0acf7f7e-2bb2-512e-bf0f-5a257eccd697", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-2.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2.1" - } - ] - }, - { - "uuid": "d20a5d87-8673-5727-8350-caa9fc8c7a9f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-2.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2.10" - } - ] - }, - { - "uuid": "7ca5e1df-f4f1-5959-aecf-52fcd11f3b33", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ia-2.11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2.6" - } - ], - "remarks": "Rev4 ia-2.11 withdrawn in Rev5; NIST disposition: incorporated-into ia-2.6." - }, - { - "uuid": "463588e3-99dd-538b-af31-fd59f49fdfe9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-2.12" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2.12" - } - ] - }, - { - "uuid": "7ae95a74-fb50-5517-91d6-b49efab7c882", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-2.13" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2.13" - } - ] - }, - { - "uuid": "855ad66a-e3a1-521e-903f-de8ad82bb445", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-2.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2.2" - } - ] - }, - { - "uuid": "f2e52df2-0912-5d0c-b992-f88abecffae3", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ia-2.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2.1" - } - ], - "remarks": "Rev4 ia-2.3 withdrawn in Rev5; NIST disposition: incorporated-into ia-2.1." - }, - { - "uuid": "7a5bedf4-892f-5860-a373-6751b5a9af18", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ia-2.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2.2" - } - ], - "remarks": "Rev4 ia-2.4 withdrawn in Rev5; NIST disposition: incorporated-into ia-2.2." - }, - { - "uuid": "ec9e76eb-c881-5aa9-bf63-3e6ed8eb23eb", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-2.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2.5" - } - ] - }, - { - "uuid": "deaabe80-e94c-55ef-831b-accb02217477", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-2.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2.6" - } - ] - }, - { - "uuid": "7b0d1e2f-bc63-54b8-b3c9-0a45008b4221", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ia-2.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2.6" - } - ], - "remarks": "Rev4 ia-2.7 withdrawn in Rev5; NIST disposition: incorporated-into ia-2.6." - }, - { - "uuid": "f2a59dc7-80c8-5b9a-84a6-5ebf6e79ac83", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-2.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2.8" - } - ] - }, - { - "uuid": "269e9ad4-041c-5227-8e26-f223f2e4eeae", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ia-2.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2.8" - } - ], - "remarks": "Rev4 ia-2.9 withdrawn in Rev5; NIST disposition: incorporated-into ia-2.8." - }, - { - "uuid": "3e3cc0dc-0234-5570-9537-32ad5c5cf6f2", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-3" - } - ] - }, - { - "uuid": "ee9199c3-1abe-53d4-9c2b-0df5439cc9ba", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-3.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-3.1" - } - ] - }, - { - "uuid": "90bb1542-ee9b-5f5b-9c3f-e2f1e87d553c", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ia-3.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-3.1" - } - ], - "remarks": "Rev4 ia-3.2 withdrawn in Rev5; NIST disposition: incorporated-into ia-3.1." - }, - { - "uuid": "6b53a042-585b-5b0f-ab64-ee06caff999b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-3.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-3.3" - } - ] - }, - { - "uuid": "5ff38749-9f59-592d-a064-38e54a24927c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-3.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-3.4" - } - ] - }, - { - "uuid": "1828a5ea-e93c-5052-a782-752098ffa4de", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-4" - } - ] - }, - { - "uuid": "83792690-8e32-5447-a20a-489bb0513fc9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-4.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-4.1" - } - ] - }, - { - "uuid": "06060826-5b23-5732-8b58-1257b8cf5304", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ia-4.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-12.1" - } - ], - "remarks": "Rev4 ia-4.2 withdrawn in Rev5; NIST disposition: incorporated-into ia-12.1." - }, - { - "uuid": "a203b263-2a53-5e45-92de-4ccd3d6a696a", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ia-4.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-12.2" - } - ], - "remarks": "Rev4 ia-4.3 withdrawn in Rev5; NIST disposition: incorporated-into ia-12.2." - }, - { - "uuid": "850b2961-991a-5259-b1e6-cbc98a49e0a7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-4.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-4.4" - } - ] - }, - { - "uuid": "e161df1b-d19d-5660-b37c-68322433ecae", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-4.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-4.5" - } - ] - }, - { - "uuid": "e3237e45-cc17-5c9b-8d60-90fd09a9bb0a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-4.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-4.6" - } - ] - }, - { - "uuid": "ee500af7-2fd4-5c23-9897-c337614d92e4", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ia-4.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-12.4" - } - ], - "remarks": "Rev4 ia-4.7 withdrawn in Rev5; NIST disposition: incorporated-into ia-12.4." - }, - { - "uuid": "ce239b22-051f-50c1-8e4f-2f43523a701d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-5" - } - ] - }, - { - "uuid": "ca679945-786d-54c3-9ef0-8b32b2c97e56", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-5.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-5.1" - } - ] - }, - { - "uuid": "88752853-7234-5bcd-aba4-49534b713ca1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-5.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-5.10" - } - ] - }, - { - "uuid": "48770c19-f839-59bd-9ca7-884999082da0", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ia-5.11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-2.1" - } - ], - "remarks": "Rev4 ia-5.11 withdrawn in Rev5; NIST disposition: incorporated-into ia-2.1." - }, - { - "uuid": "f14551d2-d08b-595e-bc59-2d807b77f605", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-5.12" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-5.12" - } - ] - }, - { - "uuid": "455801a3-a1e4-5bdf-a818-c1129dc73a1f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-5.13" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-5.13" - } - ] - }, - { - "uuid": "28485b62-1df5-5cb5-ae02-95f5c0bf8165", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-5.14" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-5.14" - } - ] - }, - { - "uuid": "dfad795e-2a25-5fcd-8035-c5abba46048a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-5.15" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-5.15" - } - ] - }, - { - "uuid": "da908465-b823-558e-9507-55f36d8a1dea", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-5.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-5.2" - } - ] - }, - { - "uuid": "787eba40-ea46-50d7-aa9e-1c190b746daa", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ia-5.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-12.4" - } - ], - "remarks": "Rev4 ia-5.3 withdrawn in Rev5; NIST disposition: incorporated-into ia-12.4." - }, - { - "uuid": "9922e2e7-7431-5395-a2cc-65569cc35eb1", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ia-5.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-5.1" - } - ], - "remarks": "Rev4 ia-5.4 withdrawn in Rev5; NIST disposition: incorporated-into ia-5.1." - }, - { - "uuid": "d5d19866-5679-5838-a1c3-694eb51752ce", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-5.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-5.5" - } - ] - }, - { - "uuid": "3ea1b186-b88a-5fbd-a7b3-f2cfa53677a2", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-5.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-5.6" - } - ] - }, - { - "uuid": "293b6adf-354b-58fd-a334-6dbd40e81f9d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-5.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-5.7" - } - ] - }, - { - "uuid": "88ea44b3-4a93-5a72-89c0-58c7b7b3a3f8", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-5.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-5.8" - } - ] - }, - { - "uuid": "d22a2371-2bdd-5241-9060-e295cae996cb", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-5.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-5.9" - } - ] - }, - { - "uuid": "de22647b-7102-5e8b-8d99-3da3fbda90ca", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-6" - } - ] - }, - { - "uuid": "b598d131-216c-5224-8718-675c5dd893fa", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-7" - } - ] - }, - { - "uuid": "06da3d26-ecf1-51d1-b1da-7e9db8beac0a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-8" - } - ] - }, - { - "uuid": "8bdc9d20-9b9e-5d32-97a0-c436c1eae83e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-8.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-8.1" - } - ] - }, - { - "uuid": "24d4c3a8-c82f-5e22-85ac-e4310dbf3193", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-8.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-8.2" - } - ] - }, - { - "uuid": "eb11508e-0c9e-56c7-a41a-63feac8628a9", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ia-8.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-8.2" - } - ], - "remarks": "Rev4 ia-8.3 withdrawn in Rev5; NIST disposition: incorporated-into ia-8.2." - }, - { - "uuid": "bc77c979-7b88-586d-bd16-4ff1fd1c73d5", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-8.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-8.4" - } - ] - }, - { - "uuid": "b107d8a0-735c-54ab-a92d-3c9f94651869", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-8.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-8.5" - } - ] - }, - { - "uuid": "4738a424-269d-53ca-8081-461b4ac8c778", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ia-9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-9" - } - ] - }, - { - "uuid": "78f2afe8-8c18-5712-9b75-6e44cdbf79b3", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ia-9.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-9" - } - ], - "remarks": "Rev4 ia-9.1 withdrawn in Rev5; NIST disposition: incorporated-into ia-9." - }, - { - "uuid": "68fc4dcc-396e-518b-8a70-4e49300254d9", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ia-9.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ia-9" - } - ], - "remarks": "Rev4 ia-9.2 withdrawn in Rev5; NIST disposition: incorporated-into ia-9." - }, - { - "uuid": "925f12a2-29f5-5c5e-97ce-4b823c8fc643", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-1" - } - ] - }, - { - "uuid": "aaf60fb7-b699-5ec8-abdb-6c5029a0ecc6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-4.11" - } - ], - "remarks": "Rev4 ir-10 withdrawn in Rev5; NIST disposition: moved-to ir-4.11." - }, - { - "uuid": "85ced22b-2cac-515e-8dff-5cb44c723cd0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-2" - } - ] - }, - { - "uuid": "189c068b-79a7-5edc-b456-3d910499e504", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-2.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-2.1" - } - ] - }, - { - "uuid": "e205a4cf-fe81-5304-8094-1ffb6ba4237a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-2.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-2.2" - } - ] - }, - { - "uuid": "1387193f-446d-5473-b96e-4efc1365c93f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-3" - } - ] - }, - { - "uuid": "ed9ffed9-a2a6-5e4f-9f8e-57dcb83d486f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-3.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-3.1" - } - ] - }, - { - "uuid": "586fd3c3-1a06-5388-ad25-9b1fa9f27727", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-3.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-3.2" - } - ] - }, - { - "uuid": "4d0eb70d-c45c-570d-ab1d-024b511d9188", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-4" - } - ] - }, - { - "uuid": "0eee43d8-b260-5fcf-aa05-0dc4f6fd4eee", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-4.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-4.1" - } - ] - }, - { - "uuid": "ef3870e1-38af-5efc-818b-357343d8cd10", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-4.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-4.10" - } - ] - }, - { - "uuid": "b49f0193-dce9-538d-bcf2-f655586f2846", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-4.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-4.2" - } - ] - }, - { - "uuid": "d7403153-40e5-565f-8845-45c49122d8bc", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-4.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-4.3" - } - ] - }, - { - "uuid": "1f8594bb-a8f0-532e-a0a7-155ad19f649d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-4.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-4.4" - } - ] - }, - { - "uuid": "2957de56-6217-5000-9fdd-5c1f15da3351", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-4.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-4.5" - } - ] - }, - { - "uuid": "1ea1dee4-8a36-5328-b8dc-1661d32410fb", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-4.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-4.6" - } - ] - }, - { - "uuid": "6be894f7-7821-580e-87d9-b1909cfea2ad", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-4.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-4.7" - } - ] - }, - { - "uuid": "8ad3c748-bf9e-544c-91f3-1b7ebd775a3f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-4.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-4.8" - } - ] - }, - { - "uuid": "436ab5d1-8cd0-598f-ba6a-cf246f34fccd", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-4.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-4.9" - } - ] - }, - { - "uuid": "8e766c36-6be0-5081-9cd3-f725c05e09aa", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-5" - } - ] - }, - { - "uuid": "435ed563-eda4-50c3-9f77-ddaef164ade1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-5.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-5.1" - } - ] - }, - { - "uuid": "f294e002-4044-50d7-af1f-1f92e2e33950", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-6" - } - ] - }, - { - "uuid": "0d5f42d4-1667-574b-b0a7-abe09a5c7dfa", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-6.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-6.1" - } - ] - }, - { - "uuid": "f8ccd6c1-5638-5902-b118-21d147de6c6b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-6.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-6.2" - } - ] - }, - { - "uuid": "6e3583a9-d394-51f1-b713-a4a6e84372ce", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-6.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-6.3" - } - ] - }, - { - "uuid": "45fe3367-84c1-5492-8688-a41ae4bfb166", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-7" - } - ] - }, - { - "uuid": "61c66d97-ae36-5219-a00a-12b8207faac7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-7.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-7.1" - } - ] - }, - { - "uuid": "3f0abb75-0f63-5765-bc5b-4b14ac1b59dd", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-7.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-7.2" - } - ] - }, - { - "uuid": "f31e32b0-f426-5618-abd4-3623b843b426", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-8" - } - ] - }, - { - "uuid": "cb4abfac-d221-5756-9418-5467ba034cc9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-9" - } - ] - }, - { - "uuid": "6f718a3d-5249-5c98-837d-7ac958a9054e", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ir-9.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-9" - } - ], - "remarks": "Rev4 ir-9.1 withdrawn in Rev5; NIST disposition: incorporated-into ir-9." - }, - { - "uuid": "b970ad14-2e29-508a-a343-10389c899e5c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-9.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-9.2" - } - ] - }, - { - "uuid": "6f46460d-1ac6-5ea5-9277-2cc566cbe496", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-9.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-9.3" - } - ] - }, - { - "uuid": "285db963-b14b-5292-96c9-dce5c7c98035", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ir-9.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ir-9.4" - } - ] - }, - { - "uuid": "a3a51cb8-ef71-5a5f-80b9-10ff2d030c3c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-1" - } - ] - }, - { - "uuid": "314092da-5c9a-50fe-906f-6e949fa7445b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-2" - } - ] - }, - { - "uuid": "fe8a22cf-75c6-51a3-81cc-dc9daca8e328", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ma-2.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-2" - } - ], - "remarks": "Rev4 ma-2.1 withdrawn in Rev5; NIST disposition: incorporated-into ma-2." - }, - { - "uuid": "c58ac0ca-aa86-5e44-aef8-29abef913647", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-2.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-2.2" - } - ] - }, - { - "uuid": "a22a7dfe-13d1-56f6-bd72-8f58d6a6f0ad", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-3" - } - ] - }, - { - "uuid": "985d80e2-f221-515f-893f-5836078c146c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-3.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-3.1" - } - ] - }, - { - "uuid": "755d5ab8-c118-555a-bb4d-3d62489287db", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-3.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-3.2" - } - ] - }, - { - "uuid": "96f63646-2be8-55aa-b59a-4af9ec960204", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-3.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-3.3" - } - ] - }, - { - "uuid": "89e5efd4-d46b-520b-9fdb-0a2a0c2c2c23", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-3.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-3.4" - } - ] - }, - { - "uuid": "74cbe60d-e3db-54fd-a70f-dc477669e119", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-4" - } - ] - }, - { - "uuid": "4eab0250-a5d8-5745-ab1d-32d330d03f5c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-4.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-4.1" - } - ] - }, - { - "uuid": "d22ea216-6449-5deb-99bc-7d02b45b1ec5", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ma-4.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-1" - } - ], - "remarks": "Rev4 ma-4.2 withdrawn in Rev5; NIST disposition: incorporated-into ma-1." - }, - { - "uuid": "31c67f01-a792-5204-a3e4-f9c44b1d4a01", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-4.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-4.3" - } - ] - }, - { - "uuid": "cd309b5f-18e1-5290-bbe5-fbc3106f7f67", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-4.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-4.4" - } - ] - }, - { - "uuid": "854f4f5b-c16f-5c3d-97b6-12d98a75642c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-4.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-4.5" - } - ] - }, - { - "uuid": "c1b432a2-3852-5f60-b71d-01398b9e134e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-4.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-4.6" - } - ] - }, - { - "uuid": "9964857a-a50e-585c-9596-7f9b0347ab50", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-4.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-4.7" - } - ] - }, - { - "uuid": "41d223ad-8bff-5e51-a253-407cb01d79bd", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-5" - } - ] - }, - { - "uuid": "65620538-d3fc-58c6-9084-b2ff9eb7c4cd", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-5.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-5.1" - } - ] - }, - { - "uuid": "ff208bda-a21a-591b-a365-99ffa8e30ba4", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-5.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-5.2" - } - ] - }, - { - "uuid": "f90657e4-584e-53ad-8a7a-7e0c79198857", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-5.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-5.3" - } - ] - }, - { - "uuid": "03bfa09e-8bf6-56d8-b99a-3ca9c713d08e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-5.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-5.4" - } - ] - }, - { - "uuid": "d188e3d9-9f7b-5b13-8226-1b586cb75b86", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-5.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-5.5" - } - ] - }, - { - "uuid": "66e94ead-6081-59ca-bbe7-8e7c57dbc764", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-6" - } - ] - }, - { - "uuid": "b9c9ab2c-3eeb-5bb6-82d6-b1f88971b58e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-6.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-6.1" - } - ] - }, - { - "uuid": "13a92a4f-849a-555b-ae35-703ba8eff1bb", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-6.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-6.2" - } - ] - }, - { - "uuid": "bc5e34f6-fc8f-5ec4-9933-e50a0c77d2ca", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ma-6.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-6.3" - } - ] - }, - { - "uuid": "f9fde01a-82fa-5b7e-a563-84259fc55227", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-1" - } - ] - }, - { - "uuid": "8a820ae9-635d-5a99-bd80-e22c15577e6b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-2" - } - ] - }, - { - "uuid": "4308afcd-6059-5fa1-b257-46f1b5341ee1", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "mp-2.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-4.2" - } - ], - "remarks": "Rev4 mp-2.1 withdrawn in Rev5; NIST disposition: incorporated-into mp-4.2." - }, - { - "uuid": "c0e1074c-9415-5210-bf23-04997e607e94", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "mp-2.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-28.1" - } - ], - "remarks": "Rev4 mp-2.2 withdrawn in Rev5; NIST disposition: incorporated-into sc-28.1." - }, - { - "uuid": "7112abea-7d89-57a6-bed9-35f6cf5cce68", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-3" - } - ] - }, - { - "uuid": "40d0a528-7312-50a0-bf7b-5d4c4891c973", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-4" - } - ] - }, - { - "uuid": "52fc6154-af69-5579-8a61-c6281fdc7f01", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "mp-4.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-28.1" - } - ], - "remarks": "Rev4 mp-4.1 withdrawn in Rev5; NIST disposition: incorporated-into sc-28.1." - }, - { - "uuid": "5d64e1c7-cf06-50df-b576-6082a61df75d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-4.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-4.2" - } - ] - }, - { - "uuid": "fd169c37-dd5d-58c3-926f-56589a09a325", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-5" - } - ] - }, - { - "uuid": "139526e6-6cb3-5d7f-aee4-6fb3939bf80b", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "mp-5.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-5" - } - ], - "remarks": "Rev4 mp-5.1 withdrawn in Rev5; NIST disposition: incorporated-into mp-5." - }, - { - "uuid": "02387343-86e4-5f76-a3b2-3bc7fcc7b6ac", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "mp-5.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-5" - } - ], - "remarks": "Rev4 mp-5.2 withdrawn in Rev5; NIST disposition: incorporated-into mp-5." - }, - { - "uuid": "f29eea22-5689-535a-a79a-aaf360a04865", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-5.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-5.3" - } - ] - }, - { - "uuid": "2e6c1e44-1917-57cd-8a44-1827efcd2fde", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "mp-5.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-28.1" - } - ], - "remarks": "Rev4 mp-5.4 withdrawn in Rev5; NIST disposition: incorporated-into sc-28.1." - }, - { - "uuid": "94fe6533-15c9-5eb6-9364-b2f16feecf4e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-6" - } - ] - }, - { - "uuid": "7427bb0d-65a3-5122-90f4-b1eaa9719157", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-6.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-6.1" - } - ] - }, - { - "uuid": "b978d7a0-6877-5300-95bb-c77d361f2b9d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-6.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-6.2" - } - ] - }, - { - "uuid": "d5f2dd5e-6821-574c-ad2c-dbd4e4d27bb1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-6.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-6.3" - } - ] - }, - { - "uuid": "f766df3b-1722-5cfc-82cc-ce477ffcfbfa", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "mp-6.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-6" - } - ], - "remarks": "Rev4 mp-6.4 withdrawn in Rev5; NIST disposition: incorporated-into mp-6." - }, - { - "uuid": "0c943e90-a889-58f0-af5b-9d1e9f6211c9", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "mp-6.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-6" - } - ], - "remarks": "Rev4 mp-6.5 withdrawn in Rev5; NIST disposition: incorporated-into mp-6." - }, - { - "uuid": "4a046b64-86a9-5df8-8202-407096a300bb", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "mp-6.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-6" - } - ], - "remarks": "Rev4 mp-6.6 withdrawn in Rev5; NIST disposition: incorporated-into mp-6." - }, - { - "uuid": "dbc1a62f-ea6d-5f3e-94d3-38496178688d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-6.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-6.7" - } - ] - }, - { - "uuid": "f8c50a1f-f9ae-56d6-884a-6e4bfc1e60a7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-6.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-6.8" - } - ] - }, - { - "uuid": "7e3645b4-8fa1-5bbe-8902-a681c93b738b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-7" - } - ] - }, - { - "uuid": "bb33f43c-aca7-5e3e-9abc-aead733586d2", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "mp-7.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-7" - } - ], - "remarks": "Rev4 mp-7.1 withdrawn in Rev5; NIST disposition: incorporated-into mp-7." - }, - { - "uuid": "2f798471-c49d-5a9c-8f39-eb841eac213d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-7.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-7.2" - } - ] - }, - { - "uuid": "61259248-2222-5014-8974-507e71f34dc8", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-8" - } - ] - }, - { - "uuid": "447ba463-c0f0-5645-b262-716dc96eb713", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-8.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-8.1" - } - ] - }, - { - "uuid": "6cde0dcf-81e8-54a9-8d2d-51ba683ffdf1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-8.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-8.2" - } - ] - }, - { - "uuid": "dc33bde7-580f-521e-bf9c-bcdd3661442a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-8.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-8.3" - } - ] - }, - { - "uuid": "68cb1088-806d-5795-9328-15b9d9d96cbc", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "mp-8.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-8.4" - } - ] - }, - { - "uuid": "a069c10d-0841-5987-8e37-7acd67b5134f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-1" - } - ] - }, - { - "uuid": "4fa4f0a9-5c9d-54ad-8f5e-36ec22cd56ef", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-10" - } - ] - }, - { - "uuid": "28b94eaf-4d4c-5814-a41a-bddaac632d0b", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "pe-10.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-10" - } - ], - "remarks": "Rev4 pe-10.1 withdrawn in Rev5; NIST disposition: incorporated-into pe-10." - }, - { - "uuid": "89c4a0aa-015f-5511-9935-a92e27864c54", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-11" - } - ] - }, - { - "uuid": "2bd2804f-047b-5eba-9bc5-051b31a04413", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-11.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-11.1" - } - ] - }, - { - "uuid": "10b3523e-145c-5b18-aa25-f8a06aa41195", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-11.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-11.2" - } - ] - }, - { - "uuid": "c0b010f4-89ac-5621-bf3e-908968d05786", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-12" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-12" - } - ] - }, - { - "uuid": "d052ca1f-8559-5ace-9f26-e074a0f32ffd", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-12.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-12.1" - } - ] - }, - { - "uuid": "20df7fd7-9f5e-55cd-aba4-0adc5a40e7b6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-13" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-13" - } - ] - }, - { - "uuid": "76107099-4ef5-54f8-bff5-f22b409c6f04", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-13.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-13.1" - } - ] - }, - { - "uuid": "cdff6542-8952-5eab-9d62-a5f7e0d71616", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-13.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-13.2" - } - ] - }, - { - "uuid": "2a3d5ca2-2a90-5646-ab74-0ce6a8cb3471", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "pe-13.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-13.2" - } - ], - "remarks": "Rev4 pe-13.3 withdrawn in Rev5; NIST disposition: incorporated-into pe-13.2." - }, - { - "uuid": "97463e12-727d-5b96-a8a7-b745aca70a2f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-13.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-13.4" - } - ] - }, - { - "uuid": "61836d1f-3cdd-5825-b962-13262b5c7eae", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-14" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-14" - } - ] - }, - { - "uuid": "2d0cce06-b659-5334-b85f-07103c4ba775", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-14.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-14.1" - } - ] - }, - { - "uuid": "240224f7-0c44-552e-bf68-fb7bc005ae4c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-14.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-14.2" - } - ] - }, - { - "uuid": "378e561d-5227-5c83-ab3f-57e869155f97", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-15" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-15" - } - ] - }, - { - "uuid": "6d9f5cd8-ec76-5430-b080-50ba81b5666b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-15.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-15.1" - } - ] - }, - { - "uuid": "1911e54e-0a04-5ae2-a589-8780c3eb44c0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-16" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-16" - } - ] - }, - { - "uuid": "4e79a8b4-15fa-5b36-9e18-b110ea2a41da", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-17" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-17" - } - ] - }, - { - "uuid": "ce4792ac-58c8-5fd2-aef3-aa51bb49004f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-18" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-18" - } - ] - }, - { - "uuid": "01ee7344-0d1d-5f0f-bdfc-05b3eca5d72a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-18.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-23" - } - ], - "remarks": "Rev4 pe-18.1 withdrawn in Rev5; NIST disposition: moved-to pe-23." - }, - { - "uuid": "b021c229-b8da-5857-b842-4e50c0d0a2f6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-19" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-19" - } - ] - }, - { - "uuid": "07027e53-a42e-5917-a6cf-ce1caf91bc13", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-19.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-19.1" - } - ] - }, - { - "uuid": "d134a768-eb4d-543a-ba82-cc98ee6cd66a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-2" - } - ] - }, - { - "uuid": "da5735d3-4ea1-5007-b8af-60a4dc062e86", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-2.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-2.1" - } - ] - }, - { - "uuid": "b3749934-60f9-575c-a615-68b91ac8a9b0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-2.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-2.2" - } - ] - }, - { - "uuid": "ee4badeb-25fe-5b4c-8425-77afdf6322e6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-2.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-2.3" - } - ] - }, - { - "uuid": "f09ab4ee-2fbd-5943-85de-66a474b12dab", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-20" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-20" - } - ] - }, - { - "uuid": "4a69f0fc-e180-5b79-bbfb-1fabffae9298", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-3" - } - ] - }, - { - "uuid": "688ebd5a-f397-52b7-9242-804342d0fad6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-3.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-3.1" - } - ] - }, - { - "uuid": "45a7d892-4e89-5069-9965-b6d7b9cec120", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-3.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-3.2" - } - ] - }, - { - "uuid": "b42133a4-d937-522a-992b-a23974e3677f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-3.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-3.3" - } - ] - }, - { - "uuid": "802e41ac-f5b4-5264-bbbb-c0e74a5265ef", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-3.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-3.4" - } - ] - }, - { - "uuid": "052c4a12-aac3-58b0-9271-cf57f7e80a42", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-3.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-3.5" - } - ] - }, - { - "uuid": "4e56e722-55ab-5026-a5f7-157e2fd34c5c", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "pe-3.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-8" - } - ], - "remarks": "Rev4 pe-3.6 withdrawn in Rev5; NIST disposition: incorporated-into ca-8." - }, - { - "uuid": "7ee15e6a-2932-53c8-8889-06389a05f7a9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-4" - } - ] - }, - { - "uuid": "55fd8a9f-6c33-5bd6-841d-fdc1caf951bb", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-5" - } - ] - }, - { - "uuid": "553cb149-17d2-5591-8a5b-40adbe53db47", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "pe-5.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-5" - } - ], - "remarks": "Rev4 pe-5.1 withdrawn in Rev5; NIST disposition: incorporated-into pe-5." - }, - { - "uuid": "a59778bc-a49d-5e5a-8d72-a1b83c075f90", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-5.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-5.2" - } - ] - }, - { - "uuid": "770d5338-9dc0-5387-86e7-9af7c3958c62", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "pe-5.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-22" - } - ], - "remarks": "Rev4 pe-5.3 withdrawn in Rev5; NIST disposition: incorporated-into pe-22." - }, - { - "uuid": "c5ec1737-a14d-569a-9782-a57ed6bed8bb", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-6" - } - ] - }, - { - "uuid": "f275fe62-7ce0-5dc9-a9cb-d08075321886", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-6.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-6.1" - } - ] - }, - { - "uuid": "378acd6b-9663-5c64-99a7-d0563096a754", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-6.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-6.2" - } - ] - }, - { - "uuid": "e3847654-e48a-5aa8-92c1-09f24dd005bd", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-6.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-6.3" - } - ] - }, - { - "uuid": "21b1bb77-8b23-5115-b3ec-ad5fa6fb17ea", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-6.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-6.4" - } - ] - }, - { - "uuid": "3d3fa2aa-ecf3-5db7-a5e5-47f57b889622", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "pe-7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-2" - } - ], - "remarks": "Rev4 pe-7 withdrawn in Rev5; NIST disposition: incorporated-into pe-2." - }, - { - "uuid": "7011698d-fb85-50e2-9f8a-7c295d242a72", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-8" - } - ] - }, - { - "uuid": "21711412-d93c-5fa9-976d-0157cdb4c2ce", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-8.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-8.1" - } - ] - }, - { - "uuid": "fecec55c-c299-5984-954a-62ddb571285f", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "pe-8.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-2" - } - ], - "remarks": "Rev4 pe-8.2 withdrawn in Rev5; NIST disposition: incorporated-into pe-2." - }, - { - "uuid": "ea83b1f2-f259-55a4-b0d8-76558fe544e0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-9" - } - ] - }, - { - "uuid": "607ec5c1-b1b9-5cc2-9f90-bcc23138b526", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-9.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-9.1" - } - ] - }, - { - "uuid": "8ac9fde0-84fa-5265-bab4-6dd1bc6341d2", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pe-9.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pe-9.2" - } - ] - }, - { - "uuid": "f8a9f791-dd89-55b6-beb8-6a3e2a36a2a7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pl-1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-1" - } - ] - }, - { - "uuid": "c22d245e-4ce8-568b-810d-8db5fcfc00ba", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pl-2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-2" - } - ] - }, - { - "uuid": "1910288a-8ca6-5db3-8ead-d5b54b1efcf3", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "pl-2.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-7" - } - ], - "remarks": "Rev4 pl-2.1 withdrawn in Rev5; NIST disposition: incorporated-into pl-7." - }, - { - "uuid": "937f2877-7005-5f57-a2da-4778bc31426a", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "pl-2.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-8" - } - ], - "remarks": "Rev4 pl-2.2 withdrawn in Rev5; NIST disposition: incorporated-into pl-8." - }, - { - "uuid": "d17b5c93-56ee-53fd-a048-14c99abbe938", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "pl-2.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-2" - } - ], - "remarks": "Rev4 pl-2.3 withdrawn in Rev5; NIST disposition: incorporated-into pl-2." - }, - { - "uuid": "c2aa4a49-8092-5476-8ee2-63d741c01157", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "pl-3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-2" - } - ], - "remarks": "Rev4 pl-3 withdrawn in Rev5; NIST disposition: incorporated-into pl-2." - }, - { - "uuid": "4a7fab2a-d7a5-597c-88c2-ee710544bd62", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pl-4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-4" - } - ] - }, - { - "uuid": "07500391-ba0c-5a45-a81c-e63978f2647a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pl-4.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-4.1" - } - ] - }, - { - "uuid": "8ca99741-7d7c-57ed-8ff9-f28eef16ffcc", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "pl-5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-8" - } - ], - "remarks": "Rev4 pl-5 withdrawn in Rev5; NIST disposition: incorporated-into ra-8." - }, - { - "uuid": "b9295dc7-72a3-5071-a312-4869f29a8800", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "pl-6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-2" - } - ], - "remarks": "Rev4 pl-6 withdrawn in Rev5; NIST disposition: incorporated-into pl-2." - }, - { - "uuid": "3214f93a-0ae2-513d-8c4c-e50b11ec69d1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pl-7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-7" - } - ] - }, - { - "uuid": "aaea8b13-9f91-5a06-bd8d-1fba62861526", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pl-8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-8" - } - ] - }, - { - "uuid": "4741f2f2-735a-52e8-840f-3a86c293c471", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pl-8.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-8.1" - } - ] - }, - { - "uuid": "0d80b410-54ad-5f3f-843a-3110a51873b0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pl-8.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-8.2" - } - ] - }, - { - "uuid": "f335e6dc-423a-5ab2-80fa-a47b551795bd", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pl-9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-9" - } - ] - }, - { - "uuid": "1cdd77c6-f608-5fec-9d6f-2205bca48d13", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pm-1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pm-1" - } - ] - }, - { - "uuid": "3e459510-0df7-5cce-b661-face3dc42aa9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pm-10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pm-10" - } - ] - }, - { - "uuid": "6196a48c-9d96-5e71-b8b7-b79101c9eb65", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pm-11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pm-11" - } - ] - }, - { - "uuid": "48d70420-995e-5401-8a5a-8a22c6c91d0f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pm-12" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pm-12" - } - ] - }, - { - "uuid": "1a90dd06-7f5d-5aef-bc44-59b28521348f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pm-13" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pm-13" - } - ] - }, - { - "uuid": "8d9b7adc-6310-52f4-bbe4-582941056f2a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pm-14" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pm-14" - } - ] - }, - { - "uuid": "f03b8157-f26a-5573-9872-da636dc48a52", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pm-15" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pm-15" - } - ] - }, - { - "uuid": "093d01e6-b882-54c5-9d0c-d21028e1bda0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pm-16" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pm-16" - } - ] - }, - { - "uuid": "0222b73c-ebab-5546-af09-c13eddfb532b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pm-2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pm-2" - } - ] - }, - { - "uuid": "8904219d-1a3c-5686-b345-b12f42a4b940", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pm-3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pm-3" - } - ] - }, - { - "uuid": "e23f299f-6b37-5fe9-a087-98bac9da049c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pm-4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pm-4" - } - ] - }, - { - "uuid": "2987acd1-2611-5823-bece-e071d6fe2d94", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pm-5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pm-5" - } - ] - }, - { - "uuid": "b51bd868-61f4-592d-9183-78cb6392339b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pm-6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pm-6" - } - ] - }, - { - "uuid": "b384a3c0-155e-5b17-8ee5-2ffaa665181d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pm-7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pm-7" - } - ] - }, - { - "uuid": "959aff64-dd83-5bdc-858c-1a82935286c8", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pm-8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pm-8" - } - ] - }, - { - "uuid": "fed4c7a1-796a-5944-8090-e8bb79a9078a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "pm-9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pm-9" - } - ] - }, - { - "uuid": "03a67959-d170-5599-a13e-41a3f64f6719", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ps-1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ps-1" - } - ] - }, - { - "uuid": "9f045f5b-7739-5ce1-b8d6-2d7c01560dbd", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ps-2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ps-2" - } - ] - }, - { - "uuid": "a1e73e5e-741f-5548-b320-e9506818a692", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ps-3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ps-3" - } - ] - }, - { - "uuid": "5857afb8-9921-525a-ab6f-2e3ea1c24ab1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ps-3.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ps-3.1" - } - ] - }, - { - "uuid": "5ee5efec-3492-5154-8bd0-837f28d7f6d9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ps-3.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ps-3.2" - } - ] - }, - { - "uuid": "5cc0d45f-8a2e-58d6-a8ca-60f521ba74a4", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ps-3.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ps-3.3" - } - ] - }, - { - "uuid": "56c1f437-f174-56df-82ae-040ed1eae51c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ps-4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ps-4" - } - ] - }, - { - "uuid": "04ed32cb-2e4a-5db6-b688-50b428c8c074", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ps-4.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ps-4.1" - } - ] - }, - { - "uuid": "af5aa9de-87fe-5dbd-aeee-2bfa97172d06", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ps-4.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ps-4.2" - } - ] - }, - { - "uuid": "35347b86-f321-5917-add6-a4918869c90b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ps-5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ps-5" - } - ] - }, - { - "uuid": "0d631c47-50e8-5945-9297-80d9ee6a2f0f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ps-6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ps-6" - } - ] - }, - { - "uuid": "df170f1d-2cbd-5dbf-a602-a9c573bd0963", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ps-6.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ps-3" - } - ], - "remarks": "Rev4 ps-6.1 withdrawn in Rev5; NIST disposition: incorporated-into ps-3." - }, - { - "uuid": "6b0f45bb-0910-59c5-8602-2bf8fea91b9a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ps-6.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ps-6.2" - } - ] - }, - { - "uuid": "7f68d481-fe0c-5c88-8fe0-a16fbf508014", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ps-6.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ps-6.3" - } - ] - }, - { - "uuid": "efc4babf-a02f-5c4a-aa0a-8ca1711356f5", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ps-7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ps-7" - } - ] - }, - { - "uuid": "1631acda-a31b-5706-aac2-45ff54ed44cd", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ps-8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ps-8" - } - ] - }, - { - "uuid": "d955bc7c-510c-5d25-b764-7a94e9b6fb40", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ra-1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-1" - } - ] - }, - { - "uuid": "e37c1ba4-87a3-5fdf-9860-4edc54264d81", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ra-2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-2" - } - ] - }, - { - "uuid": "0ff13543-408b-5f36-8af5-419c184cf818", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ra-3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-3" - } - ] - }, - { - "uuid": "971bb141-f1d1-561f-8f7d-1991e5b3ad9f", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ra-4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-3" - } - ], - "remarks": "Rev4 ra-4 withdrawn in Rev5; NIST disposition: incorporated-into ra-3." - }, - { - "uuid": "fd62fb77-807f-545a-9a38-5b318b1aac0b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ra-5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-5" - } - ] - }, - { - "uuid": "72f5bfc5-5815-58ed-b998-d95c2bee9cc1", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ra-5.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-5" - } - ], - "remarks": "Rev4 ra-5.1 withdrawn in Rev5; NIST disposition: incorporated-into ra-5." - }, - { - "uuid": "2e80b4a0-ab9c-5bcc-b5e3-46315025e526", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ra-5.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-5.10" - } - ] - }, - { - "uuid": "c58b93f2-3cfc-5850-9eca-547342c266c1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ra-5.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-5.2" - } - ] - }, - { - "uuid": "ef59de77-a68a-506e-be7a-dc25e02a07d8", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ra-5.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-5.3" - } - ] - }, - { - "uuid": "65924d39-4923-5fe7-bbb3-1824df44db3f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ra-5.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-5.4" - } - ] - }, - { - "uuid": "46fd76f9-2bb5-5176-9d1c-655d980db383", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ra-5.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-5.5" - } - ] - }, - { - "uuid": "14547f94-18ac-5e28-9899-c552005b9cac", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ra-5.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-5.6" - } - ] - }, - { - "uuid": "af58f291-9aae-5d55-9052-30833621a612", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ra-5.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-8" - } - ], - "remarks": "Rev4 ra-5.7 withdrawn in Rev5; NIST disposition: incorporated-into cm-8." - }, - { - "uuid": "3762550e-4faf-5085-93c5-698d878e914a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ra-5.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-5.8" - } - ] - }, - { - "uuid": "7f34ceba-6ab5-5df5-b56e-e365e087ddd2", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "ra-5.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ca-8" - } - ], - "remarks": "Rev4 ra-5.9 withdrawn in Rev5; NIST disposition: incorporated-into ca-8." - }, - { - "uuid": "230eb4c8-6553-5d27-8548-99e737f88cf9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "ra-6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-6" - } - ] - }, - { - "uuid": "ed53dbca-0966-5e2e-8b69-6a116d82097f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-1" - } - ] - }, - { - "uuid": "66af7732-2e97-5803-8e53-0b255c363c04", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-10" - } - ] - }, - { - "uuid": "75cbc964-4cd2-5417-a3a9-49d6189a8f79", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-10.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-10.1" - } - ] - }, - { - "uuid": "892a6ec7-dcdf-5191-adf3-2562d0d6d1a5", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-10.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-10.2" - } - ] - }, - { - "uuid": "2be75870-4024-591a-94be-f79c3fc39d29", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-10.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-10.3" - } - ] - }, - { - "uuid": "5fc9679f-0c2c-511d-a1cb-307980a860e5", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-10.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-10.4" - } - ] - }, - { - "uuid": "6fecfb18-5ed0-52ce-9996-e001d6bc2e25", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-10.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-10.5" - } - ] - }, - { - "uuid": "45f26bd2-eb60-59e1-9b2e-cac496423559", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-10.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-10.6" - } - ] - }, - { - "uuid": "5c284440-1ca0-5d6d-92a7-16d17d61d16e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-11" - } - ] - }, - { - "uuid": "dd4bf62f-49d9-500a-8701-84bcb61e8f81", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-11.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-11.1" - } - ] - }, - { - "uuid": "b17db696-51bc-5c44-a0a8-71affe87cded", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-11.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-11.2" - } - ] - }, - { - "uuid": "789e19cc-4d6c-5f5f-861e-89af3e491da2", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-11.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-11.3" - } - ] - }, - { - "uuid": "f30ade15-9c93-5258-bd40-958940e53486", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-11.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-11.4" - } - ] - }, - { - "uuid": "c84ce97f-6b59-5f78-b94b-3aaa34925d1c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-11.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-11.5" - } - ] - }, - { - "uuid": "bc91d781-c4e4-585a-9de1-cebca5c48e1b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-11.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-11.6" - } - ] - }, - { - "uuid": "27f6f815-65e0-5b93-b4f5-706b8a29bbb0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-11.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-11.7" - } - ] - }, - { - "uuid": "b3cd4cd2-3cea-55f8-a27a-94e61b9a11d7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-11.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-11.8" - } - ] - }, - { - "uuid": "d18b44de-d961-5580-8159-74aab9561f53", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-12.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-5" - } - ], - "remarks": "Rev4 sa-12.1 withdrawn in Rev5; NIST disposition: moved-to sr-5." - }, - { - "uuid": "f57752d0-cf59-518a-a737-e5ab7eebaff0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-12.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-4.3" - } - ], - "remarks": "Rev4 sa-12.10 withdrawn in Rev5; NIST disposition: moved-to sr-4.3." - }, - { - "uuid": "90a6d9da-f0a3-511b-a08a-9b379fe5f645", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-12.11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-6.1" - } - ], - "remarks": "Rev4 sa-12.11 withdrawn in Rev5; NIST disposition: moved-to sr-6.1." - }, - { - "uuid": "a8377025-9e25-5a41-90f5-052e42588d62", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-12.12" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-8" - } - ], - "remarks": "Rev4 sa-12.12 withdrawn in Rev5; NIST disposition: moved-to sr-8." - }, - { - "uuid": "313fdd48-7483-5cf3-9730-d4e9aff36bd0", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-12.13" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ma-6" - } - ], - "remarks": "Rev4 sa-12.13 withdrawn in Rev5; NIST disposition: incorporated-into ma-6." - }, - { - "uuid": "af372c7f-ac3f-554f-80dc-b6e68c52911f", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-12.14" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-4.1" - } - ], - "remarks": "Rev4 sa-12.14 withdrawn in Rev5; NIST disposition: incorporated-into sr-4.1." - }, - { - "uuid": "b158180e-c612-5771-9399-a302b31ff656", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-12.15" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-3" - } - ], - "remarks": "Rev4 sa-12.15 withdrawn in Rev5; NIST disposition: incorporated-into sr-3." - }, - { - "uuid": "a36f3a2e-5486-5ad5-b002-3a04b300155e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-12.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-6" - } - ], - "remarks": "Rev4 sa-12.2 withdrawn in Rev5; NIST disposition: moved-to sr-6." - }, - { - "uuid": "5e238573-2c48-55ac-a887-fb3e3462168e", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-12.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-3" - } - ], - "remarks": "Rev4 sa-12.3 withdrawn in Rev5; NIST disposition: incorporated-into sr-3." - }, - { - "uuid": "d8d6bf4c-ac68-5942-9ba3-198122b601ce", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-12.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-3.1" - } - ], - "remarks": "Rev4 sa-12.4 withdrawn in Rev5; NIST disposition: moved-to sr-3.1." - }, - { - "uuid": "1c458d10-b2ed-5dd4-94e3-b26a2ea9c438", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-12.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-3.2" - } - ], - "remarks": "Rev4 sa-12.5 withdrawn in Rev5; NIST disposition: moved-to sr-3.2." - }, - { - "uuid": "03d0606b-2cc3-5b32-af87-e246f272b0cc", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-12.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-5.1" - } - ], - "remarks": "Rev4 sa-12.6 withdrawn in Rev5; NIST disposition: incorporated-into sr-5.1." - }, - { - "uuid": "19ca14fd-c428-5676-86fb-1f23b100aa4a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-12.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-5.2" - } - ], - "remarks": "Rev4 sa-12.7 withdrawn in Rev5; NIST disposition: moved-to sr-5.2." - }, - { - "uuid": "628d09f0-42a7-5828-a916-ab476f828bad", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-12.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-3.2" - } - ], - "remarks": "Rev4 sa-12.8 withdrawn in Rev5; NIST disposition: incorporated-into ra-3.2." - }, - { - "uuid": "9dde0b85-fcd7-5723-a218-95248249cb9b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-12.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-7" - } - ], - "remarks": "Rev4 sa-12.9 withdrawn in Rev5; NIST disposition: moved-to sr-7." - }, - { - "uuid": "c086fbb0-170a-54cb-9c28-3fb41021bf66", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-13" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-8" - } - ], - "remarks": "Rev4 sa-13 withdrawn in Rev5; NIST disposition: incorporated-into sa-8." - }, - { - "uuid": "d1357732-b5e7-5aee-bea6-dac3afdaa47f", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-14" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ra-9" - } - ], - "remarks": "Rev4 sa-14 withdrawn in Rev5; NIST disposition: incorporated-into ra-9." - }, - { - "uuid": "36e9886d-8408-5d57-a7e9-16b4fff51f64", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-14.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-20" - } - ], - "remarks": "Rev4 sa-14.1 withdrawn in Rev5; NIST disposition: incorporated-into sa-20." - }, - { - "uuid": "2b350666-e248-5390-ba47-9c2686e15fbe", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-15" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-15" - } - ] - }, - { - "uuid": "84e812d5-aaaa-50ac-872c-7b34aeff0eaf", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-15.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-15.1" - } - ] - }, - { - "uuid": "ff0fdc92-8fce-589d-9b9c-cf7d78efbe14", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-15.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-15.10" - } - ] - }, - { - "uuid": "78c6d457-1ea9-5ad0-9a6a-ebba9bacae20", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-15.11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-15.11" - } - ] - }, - { - "uuid": "faf5b9b9-2ba8-5c63-8286-1db37bd06eaf", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-15.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-15.2" - } - ] - }, - { - "uuid": "82c0242a-ea12-5e93-b07b-ea11b122cbbb", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-15.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-15.3" - } - ] - }, - { - "uuid": "3d282a04-be53-5d1b-81cf-a266f124a88f", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-15.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-11.2" - } - ], - "remarks": "Rev4 sa-15.4 withdrawn in Rev5; NIST disposition: incorporated-into sa-11.2." - }, - { - "uuid": "64296050-df20-573d-b3a3-15c27a60d55b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-15.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-15.5" - } - ] - }, - { - "uuid": "7e8ba85d-4667-5d8f-bd03-6c9799f4eae2", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-15.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-15.6" - } - ] - }, - { - "uuid": "57b3c64e-177a-5948-a23d-f43d749bb79c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-15.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-15.7" - } - ] - }, - { - "uuid": "7db6c550-6d21-53f7-a93e-44aad4b02d89", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-15.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-15.8" - } - ] - }, - { - "uuid": "c7d329dd-f6b0-56d8-97c2-e30ef85808ed", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-15.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-3.2" - } - ], - "remarks": "Rev4 sa-15.9 withdrawn in Rev5; NIST disposition: incorporated-into sa-3.2." - }, - { - "uuid": "e2aa5079-11ca-5856-9cc6-6181c7a16a63", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-16" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-16" - } - ] - }, - { - "uuid": "f9690426-c1df-5c01-a8b7-5dbc9612a021", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-17" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-17" - } - ] - }, - { - "uuid": "558d8d17-4aa8-54d3-951c-a04b4dc9bc20", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-17.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-17.1" - } - ] - }, - { - "uuid": "add762d8-d7ce-5ce1-93b9-e7e2f7e8a4a0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-17.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-17.2" - } - ] - }, - { - "uuid": "4ea7f4f6-dfef-52a3-956e-4b8e37f32ad7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-17.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-17.3" - } - ] - }, - { - "uuid": "2de62f44-c10d-52b2-95f7-8945de9d237b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-17.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-17.4" - } - ] - }, - { - "uuid": "e274cfcc-6be1-56b0-8234-d29bfbfbb5c1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-17.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-17.5" - } - ] - }, - { - "uuid": "795503ff-cad5-5f7e-bdc3-0a8ce8e14270", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-17.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-17.6" - } - ] - }, - { - "uuid": "d43f1cd5-fce6-5dd1-8b3b-7b36758ec1c9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-17.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-17.7" - } - ] - }, - { - "uuid": "bfd8ea01-30ef-5957-8a91-77042e0e30f7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-18" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-9" - } - ], - "remarks": "Rev4 sa-18 withdrawn in Rev5; NIST disposition: moved-to sr-9." - }, - { - "uuid": "f1e7feb1-8a5a-5d92-9e41-2864bbc081bd", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-18.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-9.1" - } - ], - "remarks": "Rev4 sa-18.1 withdrawn in Rev5; NIST disposition: moved-to sr-9.1." - }, - { - "uuid": "e52a5ad3-f30e-567b-bbaa-d85e0d6ffa37", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-18.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-10" - } - ], - "remarks": "Rev4 sa-18.2 withdrawn in Rev5; NIST disposition: moved-to sr-10." - }, - { - "uuid": "dfb80473-9e8a-5de3-942e-3070cbaf992b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-19" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-11" - } - ], - "remarks": "Rev4 sa-19 withdrawn in Rev5; NIST disposition: moved-to sr-11." - }, - { - "uuid": "a0b56bcc-99c8-5efc-a3ce-921acc6e4d94", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-19.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-11.1" - } - ], - "remarks": "Rev4 sa-19.1 withdrawn in Rev5; NIST disposition: moved-to sr-11.1." - }, - { - "uuid": "2dcbccbd-ed84-5086-b815-cfcbc567596c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-19.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-11.2" - } - ], - "remarks": "Rev4 sa-19.2 withdrawn in Rev5; NIST disposition: moved-to sr-11.2." - }, - { - "uuid": "22f0642e-e20a-5293-8123-bb2df15076e0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-19.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-12" - } - ], - "remarks": "Rev4 sa-19.3 withdrawn in Rev5; NIST disposition: moved-to sr-12." - }, - { - "uuid": "5416ad5b-acf7-50fb-a508-24260e42be16", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-19.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-11.3" - } - ], - "remarks": "Rev4 sa-19.4 withdrawn in Rev5; NIST disposition: moved-to sr-11.3." - }, - { - "uuid": "2af1bb48-9d7b-519e-95a4-ca682e608dfc", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-2" - } - ] - }, - { - "uuid": "e0443009-ff0b-530d-b1bf-7e813b7b74c2", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-20" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-20" - } - ] - }, - { - "uuid": "cb336f8d-575c-59d6-aa6e-04b735971e54", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-21" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-21" - } - ] - }, - { - "uuid": "960bd2d7-334f-5815-9974-b0133226caf9", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-21.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-21" - } - ], - "remarks": "Rev4 sa-21.1 withdrawn in Rev5; NIST disposition: incorporated-into sa-21." - }, - { - "uuid": "a7ef5941-be48-5085-9c4f-b082e9eaafd0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-22" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-22" - } - ] - }, - { - "uuid": "94c50861-9c84-5bd3-b1a2-1b50275617eb", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-22.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-22" - } - ], - "remarks": "Rev4 sa-22.1 withdrawn in Rev5; NIST disposition: incorporated-into sa-22." - }, - { - "uuid": "eb384dbd-7337-59a1-80d0-9ef945b1c613", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-3" - } - ] - }, - { - "uuid": "6cbb15b2-a827-51b9-b8eb-98b070fcd320", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-4" - } - ] - }, - { - "uuid": "47289b23-f4a6-595f-b25d-ecf39dbc4e75", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-4.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-4.1" - } - ] - }, - { - "uuid": "4761ff03-05e9-5791-941c-9f970e58f7a1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-4.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-4.10" - } - ] - }, - { - "uuid": "d262c9c7-7899-5bf9-9e81-bf5cf4591804", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-4.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-4.2" - } - ] - }, - { - "uuid": "7b44b3b1-1e48-5437-beef-f2aab520f531", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-4.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-4.3" - } - ] - }, - { - "uuid": "990594fa-08d4-5ff4-9334-31a52adc60cd", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-4.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-8.9" - } - ], - "remarks": "Rev4 sa-4.4 withdrawn in Rev5; NIST disposition: incorporated-into cm-8.9." - }, - { - "uuid": "8c5c3beb-92b7-5078-9204-9c46a48eabb7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-4.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-4.5" - } - ] - }, - { - "uuid": "399deb27-f39f-5046-9d4e-75a80fd67579", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-4.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-4.6" - } - ] - }, - { - "uuid": "10364f8c-4db5-5dd6-a30c-647da5614c34", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-4.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-4.7" - } - ] - }, - { - "uuid": "2e6fc88e-9e78-5dbb-a3a3-5118a344cb57", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-4.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-4.8" - } - ] - }, - { - "uuid": "33d9139a-07e4-5f63-8468-7f826d3e168e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-4.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-4.9" - } - ] - }, - { - "uuid": "59fa25a9-dbf5-58e3-8015-71139dcf91c2", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-5" - } - ] - }, - { - "uuid": "869d6850-87c8-5576-bd7a-c7b88d55947e", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-5.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-4.1" - } - ], - "remarks": "Rev4 sa-5.1 withdrawn in Rev5; NIST disposition: incorporated-into sa-4.1." - }, - { - "uuid": "884c8ce7-fd92-5932-b519-98a28c38383a", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-5.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-4.2" - } - ], - "remarks": "Rev4 sa-5.2 withdrawn in Rev5; NIST disposition: incorporated-into sa-4.2." - }, - { - "uuid": "008956c3-9731-5dc5-8aca-b352c2c058a9", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-5.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-4.2" - } - ], - "remarks": "Rev4 sa-5.3 withdrawn in Rev5; NIST disposition: incorporated-into sa-4.2." - }, - { - "uuid": "af9a4927-5075-5a3c-bfd4-3a71fd930819", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-5.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-4.2" - } - ], - "remarks": "Rev4 sa-5.4 withdrawn in Rev5; NIST disposition: incorporated-into sa-4.2." - }, - { - "uuid": "04d2cae5-b387-5bff-9425-86c55d51d7f1", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-5.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-4.2" - } - ], - "remarks": "Rev4 sa-5.5 withdrawn in Rev5; NIST disposition: incorporated-into sa-4.2." - }, - { - "uuid": "6f7b1669-4ddf-52f0-8038-e758da43258f", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-10" - } - ], - "remarks": "Rev4 sa-6 withdrawn in Rev5; NIST disposition: incorporated-into cm-10." - }, - { - "uuid": "58d62254-c414-5dec-bdd5-815d2d842365", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sa-7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-11" - } - ], - "remarks": "Rev4 sa-7 withdrawn in Rev5; NIST disposition: incorporated-into cm-11." - }, - { - "uuid": "faa4333d-dd68-51fc-bdc8-54671c5bdbe4", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-8" - } - ] - }, - { - "uuid": "73bde5e6-363f-5d9d-8639-db12e5c20f5f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-9" - } - ] - }, - { - "uuid": "b4afa13a-e725-587d-a47f-878cee36a658", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-9.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-9.1" - } - ] - }, - { - "uuid": "29a50dd2-ed75-5823-851b-88084e3b41b0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-9.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-9.2" - } - ] - }, - { - "uuid": "f6b71ded-d9d3-5d36-9754-32d527e17a24", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-9.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-9.3" - } - ] - }, - { - "uuid": "d8eab7c9-bcca-5adb-98e7-4bf9d50e9508", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-9.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-9.4" - } - ] - }, - { - "uuid": "5fb09e1d-82de-55c5-aff5-06e1ebf8c4c6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sa-9.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sa-9.5" - } - ] - }, - { - "uuid": "bfd1f451-7965-59b1-b43c-1c74a4a02cc8", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-1" - } - ] - }, - { - "uuid": "feeb49a3-999e-5aff-b53d-a1ee6253414a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-10" - } - ] - }, - { - "uuid": "8abacb8c-2ded-557b-9a17-9de0d79d94fa", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-11" - } - ] - }, - { - "uuid": "0a3f15ff-e29f-54e0-b953-71699b93743c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-11.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-11.1" - } - ] - }, - { - "uuid": "9b45034c-648e-53f2-b000-ac06e06d150c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-12" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-12" - } - ] - }, - { - "uuid": "0a4c5d29-14e8-5af0-8b42-19c565879d5e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-12.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-12.1" - } - ] - }, - { - "uuid": "fd55689d-778d-5bdb-9a02-7f2b631b4e59", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-12.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-12.2" - } - ] - }, - { - "uuid": "f1545dfc-297c-5f52-93ab-33b1c18a6b76", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-12.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-12.3" - } - ] - }, - { - "uuid": "05dd1c5d-4f2c-5fe9-acf1-50384e084270", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-12.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-12.3" - } - ], - "remarks": "Rev4 sc-12.4 withdrawn in Rev5; NIST disposition: incorporated-into sc-12.3." - }, - { - "uuid": "741b276f-717d-5385-8be7-1c1b773d5447", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-12.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-12.3" - } - ], - "remarks": "Rev4 sc-12.5 withdrawn in Rev5; NIST disposition: incorporated-into sc-12.3." - }, - { - "uuid": "fe0e9892-ff87-5c8e-9dbb-ebef6207a61c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-13" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-13" - } - ] - }, - { - "uuid": "b87ea111-d336-5b1d-9b89-ca648c9aec0d", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-13.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-13" - } - ], - "remarks": "Rev4 sc-13.1 withdrawn in Rev5; NIST disposition: incorporated-into sc-13." - }, - { - "uuid": "220b3016-2ee5-57d4-b7c1-5c18ad0305d4", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-13.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-13" - } - ], - "remarks": "Rev4 sc-13.2 withdrawn in Rev5; NIST disposition: incorporated-into sc-13." - }, - { - "uuid": "9f66773d-3f32-536c-98fe-60c236dac880", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-13.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-13" - } - ], - "remarks": "Rev4 sc-13.3 withdrawn in Rev5; NIST disposition: incorporated-into sc-13." - }, - { - "uuid": "67e106ab-3a5b-5d84-810f-a0ca3858e092", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-13.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-13" - } - ], - "remarks": "Rev4 sc-13.4 withdrawn in Rev5; NIST disposition: incorporated-into sc-13." - }, - { - "uuid": "e0c03bca-5414-5970-920e-bbaed32ab505", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-14" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-2" - } - ], - "remarks": "Rev4 sc-14 withdrawn in Rev5; NIST disposition: incorporated-into ac-2." - }, - { - "uuid": "1c8ea9b7-c9f9-595c-a315-856cf9bc78c7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-15" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-15" - } - ] - }, - { - "uuid": "fa82c255-c77d-5b58-84b0-c9a950836fde", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-15.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-15.1" - } - ] - }, - { - "uuid": "ce2ba398-c6de-5b9a-b781-122e74b4a840", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-15.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7" - } - ], - "remarks": "Rev4 sc-15.2 withdrawn in Rev5; NIST disposition: incorporated-into sc-7." - }, - { - "uuid": "5954ea67-a458-5980-9d83-5df664dbb2ee", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-15.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-15.3" - } - ] - }, - { - "uuid": "80a6a9b0-b1b6-542f-8076-6405298802ad", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-15.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-15.4" - } - ] - }, - { - "uuid": "5efd3d65-d905-5214-b4af-96d8b14c72d2", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-16" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-16" - } - ] - }, - { - "uuid": "04476950-8fc2-53f4-a569-cd0183a9b366", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-16.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-16.1" - } - ] - }, - { - "uuid": "9f7fc844-fe1c-57d1-ad79-83981db74a3c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-17" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-17" - } - ] - }, - { - "uuid": "08727056-904e-5a79-bbc9-b910494a00dd", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-18" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-18" - } - ] - }, - { - "uuid": "8c17058d-070d-5ce3-addf-d36a19e821a7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-18.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-18.1" - } - ] - }, - { - "uuid": "6b4bb55c-8317-5e36-a639-84376156fe71", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-18.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-18.2" - } - ] - }, - { - "uuid": "b2f20ae4-3e69-5c54-b67c-ad2c6743c91a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-18.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-18.3" - } - ] - }, - { - "uuid": "465a4f9b-027f-54f9-b90a-0825cc1f629b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-18.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-18.4" - } - ] - }, - { - "uuid": "0f5b6622-28d4-5b26-b282-5ab9d3902aba", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-18.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-18.5" - } - ] - }, - { - "uuid": "d049eae8-177f-56c1-87a4-e064ce9ef721", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-2" - } - ] - }, - { - "uuid": "ea2e39b0-0e10-5ea4-a6dc-3cb246bc0ca3", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-2.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-2.1" - } - ] - }, - { - "uuid": "ee6cf654-38eb-52a4-a4e6-cc890edd3755", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-20" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-20" - } - ] - }, - { - "uuid": "b0bf39ce-d68f-5ee7-a5d1-6a0a0efa59a8", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-20.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-20" - } - ], - "remarks": "Rev4 sc-20.1 withdrawn in Rev5; NIST disposition: incorporated-into sc-20." - }, - { - "uuid": "6ee3261b-4e84-5988-b257-797dafe284bd", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-20.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-20.2" - } - ] - }, - { - "uuid": "febcf635-b19f-510c-bd0f-a439435dd47a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-21" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-21" - } - ] - }, - { - "uuid": "3f8a6b9d-09c0-5523-8b7d-36a90adcb1b6", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-21.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-21" - } - ], - "remarks": "Rev4 sc-21.1 withdrawn in Rev5; NIST disposition: incorporated-into sc-21." - }, - { - "uuid": "6629b6c0-b92d-5cb1-8118-5698d2f4c991", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-22" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-22" - } - ] - }, - { - "uuid": "6fe58277-0eca-5d7b-bf83-8469e26d4134", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-23" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-23" - } - ] - }, - { - "uuid": "40b939ab-e13f-5e34-b3b9-76a82cb40e78", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-23.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-23.1" - } - ] - }, - { - "uuid": "466b58c5-f235-5b44-965e-3f385b24d453", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-23.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-12.1" - } - ], - "remarks": "Rev4 sc-23.2 withdrawn in Rev5; NIST disposition: incorporated-into ac-12.1." - }, - { - "uuid": "a90e4524-0990-59f8-83ee-af060d7b716b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-23.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-23.3" - } - ] - }, - { - "uuid": "1448e0b5-850a-53f0-a372-e0ffc2d1ed90", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-23.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-23.3" - } - ], - "remarks": "Rev4 sc-23.4 withdrawn in Rev5; NIST disposition: incorporated-into sc-23.3." - }, - { - "uuid": "123e14c9-da64-5ae5-81bd-8b9f939ad7e4", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-23.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-23.5" - } - ] - }, - { - "uuid": "02d8a2c8-1537-5b61-b833-d26da20b3177", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-24" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-24" - } - ] - }, - { - "uuid": "77b7e8c2-be15-585c-9c3d-add01fc82c9f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-25" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-25" - } - ] - }, - { - "uuid": "150023d6-10b1-5087-bb5f-5efabb533753", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-26" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-26" - } - ] - }, - { - "uuid": "527fbed2-0554-5dd2-9823-9df395d1b6d5", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-26.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-35" - } - ], - "remarks": "Rev4 sc-26.1 withdrawn in Rev5; NIST disposition: incorporated-into sc-35." - }, - { - "uuid": "552674ff-a896-5c9e-a925-e8e738908e23", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-27" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-27" - } - ] - }, - { - "uuid": "ed64d813-59c0-5af6-8d6c-6f87dcc78569", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-28" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-28" - } - ] - }, - { - "uuid": "6f8f8434-941f-5cb0-bab4-dc1ac8532305", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-28.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-28.1" - } - ] - }, - { - "uuid": "bb03c735-30c8-52c4-a50f-c8512d1486ea", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-28.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-28.2" - } - ] - }, - { - "uuid": "c840dfaa-95dc-5c30-96ef-c6689ed1615a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-29" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-29" - } - ] - }, - { - "uuid": "84387d67-8e28-5463-8e08-b348215dd349", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-29.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-29.1" - } - ] - }, - { - "uuid": "15bf509e-8988-5047-ac19-9d2f65de1d64", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-3" - } - ] - }, - { - "uuid": "c9118467-a5bb-5cee-ae8e-389f8ed9b87d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-3.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-3.1" - } - ] - }, - { - "uuid": "2ef7c8d7-ed9b-56fe-b1bf-3e13c8601b49", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-3.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-3.2" - } - ] - }, - { - "uuid": "ef144143-afb6-5279-9d10-2b90840b767b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-3.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-3.3" - } - ] - }, - { - "uuid": "e602d959-d5f4-53c0-9131-d5f95ae47213", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-3.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-3.4" - } - ] - }, - { - "uuid": "c2675e02-f4cf-58da-8668-198afc344431", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-3.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-3.5" - } - ] - }, - { - "uuid": "0b04b390-e203-525b-8a97-a0b9f07882b5", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-30" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-30" - } - ] - }, - { - "uuid": "e4a2d427-da6a-53cf-8e33-376e1912f5f0", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-30.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-29.1" - } - ], - "remarks": "Rev4 sc-30.1 withdrawn in Rev5; NIST disposition: incorporated-into sc-29.1." - }, - { - "uuid": "1a4b7667-49ac-5ed4-9b77-72e485dd7bbb", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-30.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-30.2" - } - ] - }, - { - "uuid": "1d9c7962-1bfc-5c68-a76d-48f59af55d1e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-30.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-30.3" - } - ] - }, - { - "uuid": "b92204ef-4928-50d7-9460-2f74dacd8574", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-30.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-30.4" - } - ] - }, - { - "uuid": "971bdf92-ea18-511a-8110-df052b8b3844", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-30.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-30.5" - } - ] - }, - { - "uuid": "973a1f06-11f5-5a1e-83cc-560067caea17", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-31" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-31" - } - ] - }, - { - "uuid": "ad0c64bb-2305-5839-ab1b-2bfd89905f45", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-31.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-31.1" - } - ] - }, - { - "uuid": "00b98bc2-0cab-5aeb-a8e7-8c6fa1b411be", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-31.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-31.2" - } - ] - }, - { - "uuid": "f0dbca8e-7fc8-5a48-bbfe-9514cd7eea05", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-31.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-31.3" - } - ] - }, - { - "uuid": "10cfc25c-aded-53ba-b38b-cbea62bae795", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-32" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-32" - } - ] - }, - { - "uuid": "7b5beba9-000d-58d2-b298-ecc8de5fdd05", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-33" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-8" - } - ], - "remarks": "Rev4 sc-33 withdrawn in Rev5; NIST disposition: incorporated-into sc-8." - }, - { - "uuid": "bf0c14d5-d2b5-5c75-8363-aa30d774c540", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-34" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-34" - } - ] - }, - { - "uuid": "2bab8cc6-3c5e-5497-98d6-f14435a5e8f9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-34.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-34.1" - } - ] - }, - { - "uuid": "99709a19-96d3-5653-80ec-7c9481500447", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-34.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-34.2" - } - ] - }, - { - "uuid": "1dba54b9-d595-5a1e-b627-5754a85742bc", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-34.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-51" - } - ], - "remarks": "Rev4 sc-34.3 withdrawn in Rev5; NIST disposition: moved-to sc-51." - }, - { - "uuid": "49ee248a-e634-5e73-85d5-fcdd93b5570b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-35" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-35" - } - ] - }, - { - "uuid": "d8c64e0e-a88e-529e-bf25-553397a944dc", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-36" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-36" - } - ] - }, - { - "uuid": "5f672076-02a5-50b7-b459-9ecde15e0828", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-36.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-36.1" - } - ] - }, - { - "uuid": "27a08e92-888b-5423-880f-9a4a1f670e1d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-37" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-37" - } - ] - }, - { - "uuid": "037f9dac-6e8f-5448-b6dd-dde393b3f8e3", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-37.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-37.1" - } - ] - }, - { - "uuid": "3e5b6c94-a2a3-52c7-a948-400e9b072b70", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-38" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-38" - } - ] - }, - { - "uuid": "f4a0c6d4-5395-5052-ad1a-0cd5b9a92a62", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-39" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-39" - } - ] - }, - { - "uuid": "a095fac8-394c-57d4-9e2f-e423279040ab", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-39.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-39.1" - } - ] - }, - { - "uuid": "56d2e953-d503-51c2-a333-55254fb497d6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-39.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-39.2" - } - ] - }, - { - "uuid": "59883eaa-f8a4-5868-8b27-9ec8f1b967ca", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-4" - } - ] - }, - { - "uuid": "07c03768-8752-5983-ac58-12e725934294", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-4.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-4" - } - ], - "remarks": "Rev4 sc-4.1 withdrawn in Rev5; NIST disposition: incorporated-into sc-4." - }, - { - "uuid": "cc12e55d-697f-581e-a88c-0cfeefb65477", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-4.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-4.2" - } - ] - }, - { - "uuid": "d470b8d1-b329-50b5-8633-43449edd74b3", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-40" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-40" - } - ] - }, - { - "uuid": "b6379148-b948-5912-9596-7a927445a7da", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-40.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-40.1" - } - ] - }, - { - "uuid": "0c50aa52-0e85-5b23-9f1d-7bc9b2e47426", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-40.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-40.2" - } - ] - }, - { - "uuid": "9a32b662-2135-5d64-b947-e6fbd4340216", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-40.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-40.3" - } - ] - }, - { - "uuid": "f31bda55-2540-5e54-8672-a843b61fad4e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-40.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-40.4" - } - ] - }, - { - "uuid": "ff7cd889-c86d-5819-8c03-5cc3269bc814", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-41" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-41" - } - ] - }, - { - "uuid": "7c6b8be1-ec18-5a90-9d0a-1d54589b0c7a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-42" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-42" - } - ] - }, - { - "uuid": "1e261081-e176-5e89-9c93-58fbec25e7b6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-42.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-42.1" - } - ] - }, - { - "uuid": "bb0f10fe-3939-5028-9006-68a6d04cbe37", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-42.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-42.2" - } - ] - }, - { - "uuid": "8f492b9e-9166-5b42-9dca-891aa2ac659d", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-42.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-42" - } - ], - "remarks": "Rev4 sc-42.3 withdrawn in Rev5; NIST disposition: incorporated-into sc-42." - }, - { - "uuid": "1c5c25a9-c12f-5882-93d0-734e83ab04b2", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-43" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-43" - } - ] - }, - { - "uuid": "139e573b-19ac-5408-91eb-a832820b5c34", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-44" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-44" - } - ] - }, - { - "uuid": "5c91e7bf-b210-5e02-9f69-645b7f1dc675", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-5" - } - ] - }, - { - "uuid": "ef2e292f-3c0e-58ed-b899-509a36161b6f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-5.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-5.1" - } - ] - }, - { - "uuid": "1d0a9388-d69b-56f7-af0f-a49c4f56e64d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-5.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-5.2" - } - ] - }, - { - "uuid": "c705fa17-3f09-5ecb-b884-f1d939048ac1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-5.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-5.3" - } - ] - }, - { - "uuid": "91a2618e-cfec-5eb3-a288-0de191525d4e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-6" - } - ] - }, - { - "uuid": "6d1e5100-3685-5df3-b5a7-b3c6c1ce8f27", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7" - } - ] - }, - { - "uuid": "1e351c07-2713-5d03-b972-f5ceca925bb6", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7" - } - ], - "remarks": "Rev4 sc-7.1 withdrawn in Rev5; NIST disposition: incorporated-into sc-7." - }, - { - "uuid": "113b5cf7-43ad-57f3-aaf9-47e3fcbb66f9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.10" - } - ] - }, - { - "uuid": "9e0375d6-2065-5d6b-8b9d-325fcbd16e14", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.11" - } - ] - }, - { - "uuid": "c26e69d0-ff63-5960-9a19-8a420e8e7d43", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.12" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.12" - } - ] - }, - { - "uuid": "a703f598-e85c-5078-93b1-7c368055b8bd", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.13" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.13" - } - ] - }, - { - "uuid": "0a357d78-8a0a-59c4-ae87-d6c8d9f11780", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.14" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.14" - } - ] - }, - { - "uuid": "3ad8e717-b9d6-57c9-95f7-5cbd1f979605", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.15" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.15" - } - ] - }, - { - "uuid": "ab0324cb-14f7-5f03-9e67-6015e5a026c9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.16" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.16" - } - ] - }, - { - "uuid": "bc0696e4-952e-5e2f-9adc-6b995faa05be", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.17" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.17" - } - ] - }, - { - "uuid": "35fd7dc1-97c1-5255-a29d-dd2758cfe864", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.18" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.18" - } - ] - }, - { - "uuid": "6c97d6ce-0611-531c-abbe-19c38a036dfd", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.19" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.19" - } - ] - }, - { - "uuid": "3ad5294e-e850-564b-a1aa-898a1d68d262", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7" - } - ], - "remarks": "Rev4 sc-7.2 withdrawn in Rev5; NIST disposition: incorporated-into sc-7." - }, - { - "uuid": "daa03774-9cda-566d-804c-8806793fdd20", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.20" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.20" - } - ] - }, - { - "uuid": "af1868e4-0fef-5585-b03a-494228fba133", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.21" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.21" - } - ] - }, - { - "uuid": "34ea5da3-f524-5b2b-b9d9-8ce9c5ea19d6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.22" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.22" - } - ] - }, - { - "uuid": "7b5a7928-be1b-5770-824b-7d085b566a62", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.23" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.23" - } - ] - }, - { - "uuid": "85fd7dd8-a53a-5a32-a35c-a45594bc5487", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.3" - } - ] - }, - { - "uuid": "478763a1-fbfc-5f19-a478-f00ab057cd65", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.4" - } - ] - }, - { - "uuid": "0a155c3d-f3af-5b22-aaa5-96df3fb9ed12", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.5" - } - ] - }, - { - "uuid": "44335414-6909-5b38-9451-40436da32d46", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.18" - } - ], - "remarks": "Rev4 sc-7.6 withdrawn in Rev5; NIST disposition: incorporated-into sc-7.18." - }, - { - "uuid": "be1daae0-eff4-5455-af52-a1456feacfb4", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.7" - } - ] - }, - { - "uuid": "1009820b-8794-502c-92b7-8595dcd0f53e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.8" - } - ] - }, - { - "uuid": "af43e406-6dea-5a4b-849b-70aa66b2e15a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-7.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-7.9" - } - ] - }, - { - "uuid": "f2a894bb-8346-5b97-9be4-a98c763c42cb", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-8" - } - ] - }, - { - "uuid": "e5b6afa0-b637-5c01-973d-57742dc5da09", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-8.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-8.1" - } - ] - }, - { - "uuid": "d6eb8356-11e5-53c8-be84-ea355c47607d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-8.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-8.2" - } - ] - }, - { - "uuid": "da8f0d35-d1af-5a9f-b830-00d02983d4a8", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-8.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-8.3" - } - ] - }, - { - "uuid": "ddbb4f54-5a43-50b6-83a2-447e8fdd1670", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "sc-8.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-8.4" - } - ] - }, - { - "uuid": "f56a45ea-150e-5b8a-8838-52e06ea1b798", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "sc-9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sc-8" - } - ], - "remarks": "Rev4 sc-9 withdrawn in Rev5; NIST disposition: incorporated-into sc-8." - }, - { - "uuid": "df10e0c4-221d-5569-8603-04347a6d562f", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-1" - } - ] - }, - { - "uuid": "094fd110-c6b5-5188-8d88-f3af6bce852e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-10" - } - ] - }, - { - "uuid": "6e953b81-617c-51c7-a23e-f84e034c70a5", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-10.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-10.1" - } - ] - }, - { - "uuid": "9939bf62-52f8-54a5-9547-691f8ff0b910", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-10.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-10.2" - } - ] - }, - { - "uuid": "7be7c060-05e5-5953-8876-01f435823d36", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-10.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-10.3" - } - ] - }, - { - "uuid": "c1e64d24-4bd8-5b61-9378-f76188e426a7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-10.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-10.4" - } - ] - }, - { - "uuid": "4b6147ed-e4f9-5da1-bbc1-736444e74ae6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-10.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-10.5" - } - ] - }, - { - "uuid": "6d54b9a2-9515-5343-adb9-a548ede6ef7e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-11" - } - ] - }, - { - "uuid": "177f2a2d-3aed-5fd4-9c5a-e504fb2bb997", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-12" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-12" - } - ] - }, - { - "uuid": "7e18b5c4-05fc-5b5f-b57c-87fdbeee5376", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-13" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-13" - } - ] - }, - { - "uuid": "8fdd8726-c50e-5cd2-8373-bbe065d7a7e7", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-13.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-13.1" - } - ] - }, - { - "uuid": "04b29e34-91df-53e1-b918-4576c7b0d246", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "si-13.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-7.16" - } - ], - "remarks": "Rev4 si-13.2 withdrawn in Rev5; NIST disposition: incorporated-into si-7.16." - }, - { - "uuid": "ec7c862f-4d25-5885-873e-0d08b7e4f836", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-13.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-13.3" - } - ] - }, - { - "uuid": "58a5fa60-0a74-5d88-83ea-acf40b73773b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-13.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-13.4" - } - ] - }, - { - "uuid": "eb0cd25a-5460-51f6-bf77-25843e8efbec", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-13.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-13.5" - } - ] - }, - { - "uuid": "c4d356d1-dc37-5744-8472-39d6110a3fa9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-14" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-14" - } - ] - }, - { - "uuid": "e2664743-48d5-58c9-b8bd-5c99aa00682b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-14.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-14.1" - } - ] - }, - { - "uuid": "0986be1a-e8e3-57c1-b12e-abfa3effd914", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-15" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-15" - } - ] - }, - { - "uuid": "a923d683-dd21-552d-b386-387e54a9ba0d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-16" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-16" - } - ] - }, - { - "uuid": "25bafb6e-3d0b-5f8b-9322-7b4cacbcb758", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-17" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-17" - } - ] - }, - { - "uuid": "4ac9f61a-b6b7-52ef-a2f2-c895e973490e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-2" - } - ] - }, - { - "uuid": "fcc62aa3-2528-5725-895d-d60c2e42e450", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "si-2.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-9" - } - ], - "remarks": "Rev4 si-2.1 withdrawn in Rev5; NIST disposition: incorporated-into pl-9." - }, - { - "uuid": "f1b1345b-91a5-5551-96a1-670e43d84e45", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-2.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-2.2" - } - ] - }, - { - "uuid": "561669cb-4931-5e65-a8cc-9db3a68612dd", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-2.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-2.3" - } - ] - }, - { - "uuid": "db4bb41c-65e5-5631-b8fb-10393a93a86e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-2.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-2.4" - } - ] - }, - { - "uuid": "ad79f7ad-39be-5b46-bf82-ce5637a654c6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-2.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-2.5" - } - ] - }, - { - "uuid": "92c8991b-f1dc-5ab2-a162-c16e47e30078", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-2.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-2.6" - } - ] - }, - { - "uuid": "35819b8a-dc79-5105-bbf1-b3ea35bf91c5", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-3" - } - ] - }, - { - "uuid": "84fa4d27-190c-5406-b1b0-59cdcf23bc01", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "si-3.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-9" - } - ], - "remarks": "Rev4 si-3.1 withdrawn in Rev5; NIST disposition: incorporated-into pl-9." - }, - { - "uuid": "9e76edb1-7720-5897-925a-8fc7a7c82347", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-3.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-3.10" - } - ] - }, - { - "uuid": "2720ad28-332b-5126-b9e1-71d657b9e5f4", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "si-3.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-3" - } - ], - "remarks": "Rev4 si-3.2 withdrawn in Rev5; NIST disposition: incorporated-into si-3." - }, - { - "uuid": "965565f1-51ab-5220-885b-5ff5e9c10dd4", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "si-3.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6.10" - } - ], - "remarks": "Rev4 si-3.3 withdrawn in Rev5; NIST disposition: incorporated-into ac-6.10." - }, - { - "uuid": "cdd28a11-53c8-54bf-88ba-8154b081a2b3", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-3.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-3.4" - } - ] - }, - { - "uuid": "ca7269ed-fd11-5760-ab9b-63882d6dde9a", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "si-3.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "mp-7" - } - ], - "remarks": "Rev4 si-3.5 withdrawn in Rev5; NIST disposition: incorporated-into mp-7." - }, - { - "uuid": "3cf56456-d8e5-5638-9571-f27b9e4c9e9e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-3.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-3.6" - } - ] - }, - { - "uuid": "a91c866e-f91b-5fc2-aae1-d2810134cb10", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "si-3.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-3" - } - ], - "remarks": "Rev4 si-3.7 withdrawn in Rev5; NIST disposition: incorporated-into si-3." - }, - { - "uuid": "ba646d10-260a-53a3-baad-085b57281b64", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-3.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-3.8" - } - ] - }, - { - "uuid": "5bc84e77-fab4-5d67-8a9b-fe70bfb1d439", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-3.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-17.10" - } - ], - "remarks": "Rev4 si-3.9 withdrawn in Rev5; NIST disposition: moved-to ac-17.10." - }, - { - "uuid": "d1c12e31-195f-5970-acc3-41d89504cfcc", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4" - } - ] - }, - { - "uuid": "76b17add-999f-53f7-901a-12c927eb32d0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.1" - } - ] - }, - { - "uuid": "eb91fd85-7ff1-5ade-9ab7-3c19aa15d03a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.10" - } - ] - }, - { - "uuid": "98f473bb-7598-5d3c-a609-dbd4291d377a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.11" - } - ] - }, - { - "uuid": "09eaa78b-ef01-5463-9288-906b02d07eb2", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.12" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.12" - } - ] - }, - { - "uuid": "100f86df-4c80-5be2-bf7c-3e2791ac8043", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.13" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.13" - } - ] - }, - { - "uuid": "b869302b-9a75-5181-ac63-b8bd50806de9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.14" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.14" - } - ] - }, - { - "uuid": "f9de9d7d-bf01-58e3-a271-d4a22db568c4", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.15" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.15" - } - ] - }, - { - "uuid": "54572347-3249-5608-935b-92adf168879c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.16" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.16" - } - ] - }, - { - "uuid": "82c0a172-285e-5a54-8e3d-aef51d386a22", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.17" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.17" - } - ] - }, - { - "uuid": "2d7ce5d0-7b1c-53a5-8998-e303b9f2155e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.18" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.18" - } - ] - }, - { - "uuid": "71f6bb65-5b7d-56a8-9a3d-bdc3cac3ce6c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.19" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.19" - } - ] - }, - { - "uuid": "00ba05d6-86d1-5403-8c68-c4384a502179", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.2" - } - ] - }, - { - "uuid": "4382ca0f-3f8b-5cb7-ac13-6685278c18e9", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.20" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.20" - } - ] - }, - { - "uuid": "b1caf37d-f9da-5ffb-8270-8cef799ff710", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.21" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.21" - } - ] - }, - { - "uuid": "cb929328-cb53-57b5-b932-c8968811aa20", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.22" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.22" - } - ] - }, - { - "uuid": "f57e58b1-2b1a-5d9c-b20d-c109f9b93fbb", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.23" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.23" - } - ] - }, - { - "uuid": "5ee3d7b8-17bf-577e-82d0-d92b72f7a8fc", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.24" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.24" - } - ] - }, - { - "uuid": "d367bbaf-70a8-51b5-aaee-9a1a1858c854", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.3" - } - ] - }, - { - "uuid": "d46cea0e-57f1-5bc0-b46d-179e8b6e40ae", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.4" - } - ] - }, - { - "uuid": "2230e207-9cb1-5977-b5de-7512b839c31a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.5" - } - ] - }, - { - "uuid": "00a746bb-b638-5aaf-902d-d9b2943ab815", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "si-4.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-6.10" - } - ], - "remarks": "Rev4 si-4.6 withdrawn in Rev5; NIST disposition: incorporated-into ac-6.10." - }, - { - "uuid": "79a08beb-e637-51fa-b16a-7367f2e8e009", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.7" - } - ] - }, - { - "uuid": "d054c252-b656-531e-9b77-62aceb49f594", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "si-4.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4" - } - ], - "remarks": "Rev4 si-4.8 withdrawn in Rev5; NIST disposition: incorporated-into si-4." - }, - { - "uuid": "b16dddd1-2076-594f-821d-e72225c2f468", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-4.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-4.9" - } - ] - }, - { - "uuid": "3fee97d3-6bbd-5838-bcf8-597888352590", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-5" - } - ] - }, - { - "uuid": "429c7b86-b6f9-5122-8949-4bcfa1bbca3e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-5.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-5.1" - } - ] - }, - { - "uuid": "ab8bd2df-a5d2-58a6-9912-ff13b09b093e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-6" - } - ] - }, - { - "uuid": "4002b3d7-56cb-5dbf-81cc-e7cdd0e06f5b", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "si-6.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-6" - } - ], - "remarks": "Rev4 si-6.1 withdrawn in Rev5; NIST disposition: incorporated-into si-6." - }, - { - "uuid": "c1435e02-3dca-5467-ae0d-7af6e682b634", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-6.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-6.2" - } - ] - }, - { - "uuid": "bb20217f-69f8-5922-8c2c-f98c4322095b", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-6.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-6.3" - } - ] - }, - { - "uuid": "eafe1e9f-e53a-5fb6-93da-dd2d661e1bc2", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-7" - } - ] - }, - { - "uuid": "5c3f3303-4980-51af-9c7d-93ef8be399c1", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-7.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-7.1" - } - ] - }, - { - "uuid": "a65fc079-7782-5e24-b559-53ef8339dc5d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-7.10" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-7.10" - } - ] - }, - { - "uuid": "109115bc-5165-57f4-a467-5aae2a31bc20", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-7.11" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-7.6" - } - ], - "remarks": "Rev4 si-7.11 withdrawn in Rev5; NIST disposition: moved-to cm-7.6." - }, - { - "uuid": "29b48169-92cd-5c51-a5e6-6a0700591262", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-7.12" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-7.12" - } - ] - }, - { - "uuid": "43148bc2-fa55-5417-a5b1-7d6b8f84d07e", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-7.13" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-7.7" - } - ], - "remarks": "Rev4 si-7.13 withdrawn in Rev5; NIST disposition: moved-to cm-7.7." - }, - { - "uuid": "cfb3021b-bd40-509a-9e41-727ca53d0b12", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-7.14" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "cm-7.8" - } - ], - "remarks": "Rev4 si-7.14 withdrawn in Rev5; NIST disposition: moved-to cm-7.8." - }, - { - "uuid": "7ef0afd3-fa73-5b35-b308-0ca3dd01b42a", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-7.15" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-7.15" - } - ] - }, - { - "uuid": "d91bab62-8182-5e90-b654-1991d47e9c7d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-7.16" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-7.16" - } - ] - }, - { - "uuid": "6f8dda8c-ef80-5b0f-96fb-30380c5432b8", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-7.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-7.2" - } - ] - }, - { - "uuid": "5eae7662-19dd-5cad-b10b-d8a09ce11b28", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-7.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-7.3" - } - ] - }, - { - "uuid": "fb320946-c56d-53dc-bd27-982035f73589", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "si-7.4" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "sr-9" - } - ], - "remarks": "Rev4 si-7.4 withdrawn in Rev5; NIST disposition: incorporated-into sr-9." - }, - { - "uuid": "9218b0b4-d49b-53da-9798-c5a807ee5fa6", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-7.5" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-7.5" - } - ] - }, - { - "uuid": "450e9ef4-1679-5624-9add-e4dff98185ba", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-7.6" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-7.6" - } - ] - }, - { - "uuid": "51da3c61-ae05-548e-87b4-91bf85e06377", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-7.7" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-7.7" - } - ] - }, - { - "uuid": "102ad5f6-1a63-5e04-a549-9b49aa16ca6c", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-7.8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-7.8" - } - ] - }, - { - "uuid": "8c91ad1d-75ad-54cf-b906-90f81074d81d", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-7.9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-7.9" - } - ] - }, - { - "uuid": "3e4518e7-13f7-55e9-860c-7c20da5fd0b0", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-8" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-8" - } - ] - }, - { - "uuid": "f4edb9ca-4d47-5b62-90bb-6816e2697976", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "si-8.1" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "pl-9" - } - ], - "remarks": "Rev4 si-8.1 withdrawn in Rev5; NIST disposition: incorporated-into pl-9." - }, - { - "uuid": "a900cf63-a767-55b2-9d16-1026be5a0718", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-8.2" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-8.2" - } - ] - }, - { - "uuid": "758589c6-2c98-57f3-b330-fcb17c9f91a8", - "relationship": "equivalent", - "sources": [ - { - "type": "control", - "id-ref": "si-8.3" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "si-8.3" - } - ] - }, - { - "uuid": "30b3889b-3a9e-5638-9c13-2d817ff969f9", - "relationship": "subset-of", - "sources": [ - { - "type": "control", - "id-ref": "si-9" - } - ], - "targets": [ - { - "type": "control", - "id-ref": "ac-2" - } - ], - "remarks": "Rev4 si-9 withdrawn in Rev5; NIST disposition: incorporated-into ac-2." - } - ] - } - ], - "back-matter": { - "resources": [ - { - "uuid": "7849a1b7-afc2-5790-93a0-f621db8a1790", - "title": "NIST SP 800-53 Rev 4 catalog (OSCAL)", - "props": [ - { - "name": "id", - "value": "resource-rev4-catalog" - } - ], - "rlinks": [ - { - "href": "../catalogs/NIST_SP-800-53_rev4_catalog.json" - } - ] - }, - { - "uuid": "e3c6233f-b5a4-5d0c-af24-35504b65ab52", - "title": "NIST SP 800-53 Rev 5 catalog (OSCAL)", - "props": [ - { - "name": "id", - "value": "resource-rev5-catalog" - } - ], - "rlinks": [ - { - "href": "../catalogs/NIST_SP-800-53_rev5_catalog.json" - } - ] - } - ] - } - } -} diff --git a/data/minimum-assessment-scope.json b/data/minimum-assessment-scope.json new file mode 100644 index 00000000..60af1833 --- /dev/null +++ b/data/minimum-assessment-scope.json @@ -0,0 +1,36 @@ +{ + "schema": "mas-inputs/1", + "$comment": "Operator-owned inputs to scripts/build-mas.py, which joins them with the canonical inventory (ksi-signal.json), the boundary classification and the third-party records to produce /.well-known/minimum-assessment-scope.json (MAS-CSO-IIR, MAS-CSO-FLO, MAS-CSO-MDI, MAS-CSO-TPR, FRC-CSX-MAS). The builder fails the deploy when an off-origin host in a CSP is not placed here, when a data store or log in the inventory has no metadata entry, or when a component type is in no KSI evidence domain and has no whole-set reason. AI-drafted 2026-11-05 from the Terraform and the CSPs, for the operator's review.", + "off_origin_hosts": { + "cdn.jsdelivr.net": {"component": "ext::jsdelivr"}, + "storage.googleapis.com": {"component": "ext::google-cloud-storage"}, + "samaydlette-com-silk-reeling.auth.us-east-2.amazoncognito.com": {"component": "aws::identity_provider::silk_reeling"}, + "ochelli.com": {"out_of_scope": "Podcast audio on the activities page (CSP media-src only): the reader's browser streams a public episode directly from the host. Media cannot run code in the page, the host receives nothing from this system, and it is unrelated to the Silk Reeling app or the published evidence, so it neither handles nor affects federal customer data."}, + "traffic.libsyn.com": {"out_of_scope": "Podcast audio redirect host (CSP media-src only), as for ochelli.com: public episode audio streamed directly by the reader's browser; no code, no data from this system."}, + "content.libsyn.com": {"out_of_scope": "Podcast audio file host behind traffic.libsyn.com (CSP media-src only), as for ochelli.com."} + }, + "data_store_types": ["object_store", "log_group", "kv_table", "message_queue", "identity_provider", "notification_topic", "secrets_manager", "audit_log_trail"], + "metadata": { + "aws::object_store::website": {"holds": "Site content and the published /.well-known/ evidence", "personal_data": [], "retention": "Current objects kept; replaced versions expire after 90 days", "retention_days": 90}, + "aws::object_store::logs": {"holds": "S3 server access logs for the site bucket (origin reads; flow O), and CloudFront edge access records (flow O2: date, time, edge location, country, method, path, status, bytes and cache result only; no client IP, user agent, referrer, query string or cookie). The deploy role reads the edge records to build the aggregate access summary (flow O3); only monthly counts are published.", "personal_data": ["requester IP address", "user agent"], "retention": "S3 server access logs 400 days; CloudFront edge access records 90 days; then expired", "retention_days": 400}, + "aws::object_store::cloudtrail": {"holds": "CloudTrail management-event log files", "personal_data": ["operator source IP address", "IAM principal names", "user agent"], "retention": "913 days (moved to infrequent access after 365)", "retention_days": 913}, + "aws::object_store::tfstate": {"holds": "Terraform state: resource configuration and attributes, including secret values", "personal_data": [], "retention": "Current state kept; replaced versions expire after 90 days", "retention_days": 90}, + "aws::kv_table::tflock": {"holds": "Terraform state lock: lock ID, holder and timestamp", "personal_data": [], "retention": "Deleted when the lock is released"}, + "aws::log_group::opa_compliance": {"holds": "Runtime KSI emitter run logs", "personal_data": [], "retention": "365 days", "retention_days": 365}, + "aws::log_group::evidence_watchdog": {"holds": "Evidence-freshness watchdog run logs (artifact ages)", "personal_data": [], "retention": "365 days", "retention_days": 365}, + "aws::log_group::silk_reeling": {"holds": "Silk Reeling app Lambda runtime logs: invocations, errors", "personal_data": [], "retention": "365 days", "retention_days": 365}, + "aws::log_group::silk_apigw": {"holds": "Silk Reeling API access log: request ID, source IP, time, method, route, status, response length", "personal_data": ["source IP address"], "retention": "365 days", "retention_days": 365}, + "aws::log_group::route53_query_log": {"holds": "Route 53 DNS query logs (created only when DNS query logging is enabled)", "personal_data": ["resolver IP address"], "retention": "365 days", "retention_days": 365}, + "aws::message_queue::compliance_dlq": {"holds": "Scheduled events whose emitter invocation failed", "personal_data": [], "retention": "14 days", "retention_days": 14}, + "aws::identity_provider::silk_reeling": {"holds": "App user records: email address, TOTP enrollment, sign-in events", "personal_data": ["email address", "sign-in IP address and device data"], "retention": "Until the operator deletes the user"}, + "aws::notification_topic::evidence_alerts": {"holds": "The operator's email subscription and in-flight alarm notifications", "personal_data": ["operator email address (subscription endpoint, set out of band; never in Terraform or published)"], "retention": "Until the subscription is removed"}, + "aws::audit_log_trail::management": {"holds": "Management events for the account, delivered to the CloudTrail bucket (flow P)", "personal_data": ["operator source IP address", "IAM principal names"], "retention": "As the CloudTrail bucket (913 days)", "retention_days": 913}, + "aws::secrets_manager::*": {"holds": "Application secrets (none today)", "personal_data": [], "retention": "Until deleted, then a 7 to 30 day recovery window"}, + "ext::jsdelivr": {"holds": "Third-party observation: jsDelivr's request logs when a user's browser fetches the MediaPipe runtime", "personal_data": ["user IP address", "user agent"], "retention": "Set by the third party; not controlled by this provider"}, + "ext::google-cloud-storage": {"holds": "Third-party observation: Google's request logs when a user's browser fetches the pose model", "personal_data": ["user IP address", "user agent"], "retention": "Set by the third party; not controlled by this provider"} + }, + "whole_set_types": { + "html_artifact": "Static pages are content of the website bucket: the whole-inventory KSIs (PIY) cover them, and every page is sha256-hashed into the inventory so any change is a recorded change.", + "kv_table": "The state lock table holds lock metadata only; it is covered by the whole-inventory KSIs (PIY) and by the trust-root review of the bootstrap stack." + } +} diff --git a/data/non-machine-resources.json b/data/non-machine-resources.json new file mode 100644 index 00000000..29072e26 --- /dev/null +++ b/data/non-machine-resources.json @@ -0,0 +1,320 @@ +{ + "$schema": "../infrastructure/schemas/non-machine-resources.schema.json", + "schema": "non-machine-resources/2", + "$comment": "VDR-TFR-NMV: the non-machine information resources (policies, procedures, plans, the operator role, records and registers). Nobody verifies them by hand: scripts/_nonmachine.py runs machine checks on each (the file exists; every path and DEC ID it cites resolves; it names no retired mechanism; every tagged count matches the code; a register validates), and scripts/check-non-machine-vv.py runs them on every deploy (failing it) and every night, publishing the status as /.well-known/vdr-non-machine-vv.json. A policy or runbook without an entry fails too. Replaces the operator attestation of DEC-190.", + "max_age_days": 92, + "resources": [ + { + "id": "NMR-POL-AC", + "path": "docs/policies/ac-policy.md", + "kind": "policy", + "title": "AC — Access Control", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-AT", + "path": "docs/policies/at-policy.md", + "kind": "policy", + "title": "AT — Awareness and Training", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-AU", + "path": "docs/policies/au-policy.md", + "kind": "policy", + "title": "AU — Audit and Accountability", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-CA", + "path": "docs/policies/ca-policy.md", + "kind": "policy", + "title": "CA — Assessment, Authorization, and Monitoring", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-CM", + "path": "docs/policies/cm-policy.md", + "kind": "policy", + "title": "CM — Configuration Management", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-CP", + "path": "docs/policies/cp-policy.md", + "kind": "policy", + "title": "CP — Contingency Planning", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-IA", + "path": "docs/policies/ia-policy.md", + "kind": "policy", + "title": "IA — Identification and Authentication", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-IR", + "path": "docs/policies/ir-policy.md", + "kind": "policy", + "title": "IR — Incident Response", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-MA", + "path": "docs/policies/ma-policy.md", + "kind": "policy", + "title": "MA — Maintenance", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-MP", + "path": "docs/policies/mp-policy.md", + "kind": "policy", + "title": "MP — Media Protection", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-PE", + "path": "docs/policies/pe-policy.md", + "kind": "policy", + "title": "PE — Physical and Environmental Protection", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-PL", + "path": "docs/policies/pl-policy.md", + "kind": "policy", + "title": "PL — Planning", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-PS", + "path": "docs/policies/ps-policy.md", + "kind": "policy", + "title": "PS — Personnel Security", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-PT", + "path": "docs/policies/pt-policy.md", + "kind": "policy", + "title": "PT — PII Processing and Transparency", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-RA", + "path": "docs/policies/ra-policy.md", + "kind": "policy", + "title": "RA — Risk Assessment", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-RESOURCE-TAGGING-STANDARD", + "path": "docs/policies/resource-tagging-standard.md", + "kind": "policy", + "title": "Resource Tagging Standard", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-SA", + "path": "docs/policies/sa-policy.md", + "kind": "policy", + "title": "SA — System and Services Acquisition", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-SC", + "path": "docs/policies/sc-policy.md", + "kind": "policy", + "title": "SC — System and Communications Protection", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-SECURE-CONFIGURATION-GUIDE", + "path": "docs/policies/secure-configuration-guide.md", + "kind": "policy", + "title": "Secure Configuration Guide (FedRAMP 20x SCG)", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-SI", + "path": "docs/policies/si-policy.md", + "kind": "policy", + "title": "SI — System and Information Integrity", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-POL-SR", + "path": "docs/policies/sr-policy.md", + "kind": "policy", + "title": "SR — Supply Chain Risk Management", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-RUN-EVIDENCE-SLA-ALARM", + "path": "docs/runbooks/evidence-sla-alarm.md", + "kind": "procedure", + "title": "Runbook: an evidence SLA alarm fired", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-RUN-VULN-GATE-FAILURE", + "path": "docs/runbooks/vuln-gate-failure.md", + "kind": "procedure", + "title": "Runbook: the vulnerability gate failed", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-RUN-DAST-SCANNER-USER", + "path": "docs/runbooks/dast-scanner-user.md", + "kind": "procedure", + "title": "Runbook: the authenticated DAST scanner user and its secrets", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-RUN-FEDRAMP-SECURITY-INBOX", + "path": "docs/runbooks/fedramp-security-inbox.md", + "kind": "procedure", + "title": "Runbook: the FedRAMP Security Inbox (simulated)", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-PROC-IR", + "path": "docs/incident-response.md", + "kind": "procedure", + "title": "Incident Response Runbook", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-PLAN-RECOVERY", + "path": "docs/recovery-plan.md", + "kind": "plan", + "title": "Recovery Plan", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-PLAN-CONMON", + "path": "docs/continuous-monitoring-plan.md", + "kind": "plan", + "title": "Continuous Monitoring Plan", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-ROLE-OPERATOR", + "path": "docs/continuous-monitoring-plan.md", + "kind": "role", + "title": "Operator role (sole operator)", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-PROC-ROB", + "path": "docs/rules-of-behavior.md", + "kind": "procedure", + "title": "Rules of Behavior", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-REC-TRAINING", + "path": "docs/training-log.md", + "kind": "record", + "title": "Training Log", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-PROC-SUPPLY", + "path": "docs/supply-chain.md", + "kind": "procedure", + "title": "Supply Chain Risk Management", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-PROC-SCN", + "path": "docs/scn/README.md", + "kind": "procedure", + "title": "Significant Change Notification (SCN) records", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-REC-PTA", + "path": "docs/privacy-threshold-analysis.md", + "kind": "record", + "title": "Privacy Threshold Analysis (PTA)", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-REG-DECISIONS", + "path": "data/decisions.json", + "kind": "register", + "title": "Decision register", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine check: the register loads under its own validator (the decision register under scripts/_decisions.py) or parses as JSON." + }, + { + "id": "NMR-REG-GOVERNANCE", + "path": "docs/governance/domains.json", + "kind": "register", + "title": "Governance domain registry", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine check: the register loads under its own validator (the decision register under scripts/_decisions.py) or parses as JSON." + }, + { + "id": "NMR-PROC-AGENCY-ACCESS", + "path": "docs/procedures/agency-access.md", + "kind": "procedure", + "title": "Agency Access to the Certification Package", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-PROC-INFO-SHARING", + "path": "docs/procedures/information-sharing.md", + "kind": "procedure", + "title": "Information Sharing and Disclosure Standard", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + }, + { + "id": "NMR-REC-SECURITY-REVIEW", + "path": "docs/security-review.md", + "kind": "record", + "title": "Annual Security Review: how it is generated (scripts/hold-security-review.py), and its history", + "owner": "Sam Aydlette (operator)", + "verifies": "Machine checks: the file exists, every repository path and DEC ID it cites resolves, it names no retired mechanism, and every tagged count matches the code." + } + ] +} diff --git a/data/profiles/FedRAMP_rev5_HIGH-baseline-resolved-profile_catalog.json b/data/profiles/FedRAMP_rev5_HIGH-baseline-resolved-profile_catalog.json deleted file mode 100644 index 3e661ae8..00000000 --- a/data/profiles/FedRAMP_rev5_HIGH-baseline-resolved-profile_catalog.json +++ /dev/null @@ -1,151025 +0,0 @@ -{ - "catalog": { - "uuid": "12d35e21-5659-4909-a313-cad67cba9e18", - "metadata": { - "title": "FedRAMP Rev 5 High Baseline", - "last-modified": "2026-02-10T21:06:15.239744513Z", - "version": "fedramp-3.0.0rc1-oscal-1.1.2", - "oscal-version": "1.1.3", - "props": [ - { - "name": "resolution-tool", - "value": "libOSCAL-Java" - } - ], - "links": [ - { - "href": "file:FedRAMP_rev5_HIGH-baseline_profile.xml", - "rel": "source-profile" - } - ] - }, - "groups": [ - { - "id": "ac", - "class": "family", - "title": "Access Control", - "controls": [ - { - "id": "ac-1", - "class": "SP800-53", - "title": "Policy and Procedures", - "params": [ - { - "id": "ac-1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ac-01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ac-01_odp.02" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "ac-01_odp.01", - "props": [ - { - "name": "label", - "value": "AC-01_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the access control policy is to be disseminated is/are defined;" - } - ] - }, - { - "id": "ac-01_odp.02", - "props": [ - { - "name": "label", - "value": "AC-01_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the access control procedures are to be disseminated is/are defined;" - } - ] - }, - { - "id": "ac-01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ac-1_prm_2" - }, - { - "name": "label", - "value": "AC-01_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "organization-level", - "mission/business process-level", - "system-level" - ] - } - }, - { - "id": "ac-01_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "ac-1_prm_3" - }, - { - "name": "label", - "value": "AC-01_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "official", - "guidelines": [ - { - "prose": "an official to manage the access control policy and procedures is defined;" - } - ] - }, - { - "id": "ac-01_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "ac-1_prm_4" - }, - { - "name": "label", - "value": "AC-01_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current access control policy is reviewed and updated is defined;" - } - ] - }, - { - "id": "ac-01_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "ac-1_prm_5" - }, - { - "name": "label", - "value": "AC-01_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that would require the current access control policy to be reviewed and updated are defined;" - } - ] - }, - { - "id": "ac-01_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "ac-1_prm_6" - }, - { - "name": "label", - "value": "AC-01_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current access control procedures are reviewed and updated is defined;" - } - ] - }, - { - "id": "ac-01_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "ac-1_prm_7" - }, - { - "name": "label", - "value": "AC-01_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "events", - "constraints": [ - { - "description": "significant changes" - } - ], - "guidelines": [ - { - "prose": "events that would require procedures to be reviewed and updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AC-01", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-1" - }, - { - "name": "label", - "value": "AC-01", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#c7ac44e8-10db-4b64-b2b9-9e32ec1efed0", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#4c0ec2ee-a0d6-428a-9043-4504bc3ade6f", - "rel": "reference" - }, - { - "href": "#7f473f21-fdbf-4a6c-81a1-0ab95919609d", - "rel": "reference" - }, - { - "href": "#ia-1", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-24", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-1_smt", - "name": "statement", - "parts": [ - { - "id": "ac-1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, a policy that addresses Access Control MUST be associated with AC-1 part a.", - "class": "policy" - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, at least one procedure that addresses Access Control MUST be associated with AC-1 part a.", - "class": "procedure" - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, document, and disseminate to {{ insert: param, ac-1_prm_1 }}:", - "parts": [ - { - "id": "ac-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, ac-01_odp.03 }} access control policy that:", - "parts": [ - { - "id": "ac-1_smt.a.1.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "ac-1_smt.a.1.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and" - } - ] - }, - { - "id": "ac-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the access control policy and the associated access controls;" - } - ] - }, - { - "id": "ac-1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Designate an {{ insert: param, ac-01_odp.04 }} to manage the development, documentation, and dissemination of the access control policy and procedures; and" - }, - { - "id": "ac-1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the current access control:", - "parts": [ - { - "id": "ac-1_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Policy {{ insert: param, ac-01_odp.05 }} and following {{ insert: param, ac-01_odp.06 }} ; and" - }, - { - "id": "ac-1_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures {{ insert: param, ac-01_odp.07 }} and following {{ insert: param, ac-01_odp.08 }}." - } - ] - } - ] - }, - { - "id": "ac-1_gdn", - "name": "guidance", - "prose": "Access control policy and procedures address the controls in the AC family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of access control policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies reflecting the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to access control policy and procedures include assessment or audit findings, security incidents or breaches, or changes in laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure." - }, - { - "id": "ac-1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-01a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-01a.[01]", - "class": "sp800-53a" - } - ], - "prose": "an access control policy is developed and documented;", - "links": [ - { - "href": "#ac-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-01a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the access control policy is disseminated to {{ insert: param, ac-01_odp.01 }};", - "links": [ - { - "href": "#ac-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-1_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-01a.[03]", - "class": "sp800-53a" - } - ], - "prose": "access control procedures to facilitate the implementation of the access control policy and associated controls are developed and documented;", - "links": [ - { - "href": "#ac-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-1_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-01a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the access control procedures are disseminated to {{ insert: param, ac-01_odp.02 }};", - "links": [ - { - "href": "#ac-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-1_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-01a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-1_obj.a.1.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-01a.01(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-1_obj.a.1.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-01a.01(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ac-01_odp.03 }} access control policy addresses purpose;", - "links": [ - { - "href": "#ac-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-1_obj.a.1.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-01a.01(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ac-01_odp.03 }} access control policy addresses scope;", - "links": [ - { - "href": "#ac-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-1_obj.a.1.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-01a.01(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ac-01_odp.03 }} access control policy addresses roles;", - "links": [ - { - "href": "#ac-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-1_obj.a.1.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-01a.01(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ac-01_odp.03 }} access control policy addresses responsibilities;", - "links": [ - { - "href": "#ac-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-1_obj.a.1.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-01a.01(a)[05]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ac-01_odp.03 }} access control policy addresses management commitment;", - "links": [ - { - "href": "#ac-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-1_obj.a.1.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-01a.01(a)[06]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ac-01_odp.03 }} access control policy addresses coordination among organizational entities;", - "links": [ - { - "href": "#ac-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-1_obj.a.1.a-7", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-01a.01(a)[07]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ac-01_odp.03 }} access control policy addresses compliance;", - "links": [ - { - "href": "#ac-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-1_obj.a.1.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-01a.01(b)", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ac-01_odp.03 }} access control policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines;", - "links": [ - { - "href": "#ac-1_smt.a.1.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-1_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-01b.", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ac-01_odp.04 }} is designated to manage the development, documentation, and dissemination of the access control policy and procedures;", - "links": [ - { - "href": "#ac-1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-01c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-1_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-01c.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-1_obj.c.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-01c.01[01]", - "class": "sp800-53a" - } - ], - "prose": "the current access control policy is reviewed and updated {{ insert: param, ac-01_odp.05 }};", - "links": [ - { - "href": "#ac-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-1_obj.c.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-01c.01[02]", - "class": "sp800-53a" - } - ], - "prose": "the current access control policy is reviewed and updated following {{ insert: param, ac-01_odp.06 }};", - "links": [ - { - "href": "#ac-1_smt.c.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-1_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-01c.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-1_obj.c.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-01c.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the current access control procedures are reviewed and updated {{ insert: param, ac-01_odp.07 }};", - "links": [ - { - "href": "#ac-1_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-1_obj.c.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-01c.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the current access control procedures are reviewed and updated following {{ insert: param, ac-01_odp.08 }}.", - "links": [ - { - "href": "#ac-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-1_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-01-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy and procedures\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-01-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with access control responsibilities\n\norganizational personnel with information security with information security and privacy responsibilities" - } - ] - } - ] - }, - { - "id": "ac-2", - "class": "SP800-53", - "title": "Account Management", - "params": [ - { - "id": "ac-02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2_prm_1" - }, - { - "name": "label", - "value": "AC-02_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "prerequisites and criteria", - "guidelines": [ - { - "prose": "prerequisites and criteria for group and role membership are defined;" - } - ] - }, - { - "id": "ac-02_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2_prm_2" - }, - { - "name": "label", - "value": "AC-02_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "attributes (as required)", - "guidelines": [ - { - "prose": "attributes (as required) for each account are defined;" - } - ] - }, - { - "id": "ac-02_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2_prm_3" - }, - { - "name": "label", - "value": "AC-02_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles required to approve requests to create accounts is/are defined;" - } - ] - }, - { - "id": "ac-02_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2_prm_4" - }, - { - "name": "label", - "value": "AC-02_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "policy, procedures, prerequisites, and criteria", - "guidelines": [ - { - "prose": "policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined;" - } - ] - }, - { - "id": "ac-02_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2_prm_5" - }, - { - "name": "label", - "value": "AC-02_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to be notified is/are defined;" - } - ] - }, - { - "id": "ac-02_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2_prm_6" - }, - { - "name": "label", - "value": "AC-02_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "twenty-four (24) hours" - } - ], - "guidelines": [ - { - "prose": "time period within which to notify account managers when accounts are no longer required is defined;" - } - ] - }, - { - "id": "ac-02_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2_prm_7" - }, - { - "name": "label", - "value": "AC-02_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "eight (8) hours" - } - ], - "guidelines": [ - { - "prose": "time period within which to notify account managers when users are terminated or transferred is defined;" - } - ] - }, - { - "id": "ac-02_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2_prm_8" - }, - { - "name": "label", - "value": "AC-02_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "eight (8) hours" - } - ], - "guidelines": [ - { - "prose": "time period within which to notify account managers when system usage or the need to know changes for an individual is defined;" - } - ] - }, - { - "id": "ac-02_odp.09", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2_prm_9" - }, - { - "name": "label", - "value": "AC-02_ODP[09]", - "class": "sp800-53a" - } - ], - "label": "attributes (as required)", - "guidelines": [ - { - "prose": "attributes needed to authorize system access (as required) are defined;" - } - ] - }, - { - "id": "ac-02_odp.10", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2_prm_10" - }, - { - "name": "label", - "value": "AC-02_ODP[10]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "monthly for privileged accessed, every six (6) months for non-privileged access" - } - ], - "guidelines": [ - { - "prose": "the frequency of account review is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AC-02", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-2" - }, - { - "name": "label", - "value": "AC-02", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#2956e175-f674-43f4-b1b9-e074ad9fc39c", - "rel": "reference" - }, - { - "href": "#388a3aa2-5d85-4bad-b8a3-77db80d63c4f", - "rel": "reference" - }, - { - "href": "#53df282b-8b3f-483a-bad1-6a8b8ac00114", - "rel": "reference" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-5", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-20", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ac-24", - "rel": "related" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "#ma-3", - "rel": "related" - }, - { - "href": "#ma-5", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#ps-2", - "rel": "related" - }, - { - "href": "#ps-4", - "rel": "related" - }, - { - "href": "#ps-5", - "rel": "related" - }, - { - "href": "#ps-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-3", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-37", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-2_smt", - "name": "statement", - "parts": [ - { - "id": "ac-2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Define and document the types of accounts allowed and specifically prohibited for use within the system;" - }, - { - "id": "ac-2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Assign account managers;" - }, - { - "id": "ac-2_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Require {{ insert: param, ac-02_odp.01 }} for group and role membership;" - }, - { - "id": "ac-2_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Specify:", - "parts": [ - { - "id": "ac-2_smt.d.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Authorized users of the system;" - }, - { - "id": "ac-2_smt.d.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Group and role membership; and" - }, - { - "id": "ac-2_smt.d.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Access authorizations (i.e., privileges) and {{ insert: param, ac-02_odp.02 }} for each account;" - } - ] - }, - { - "id": "ac-2_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Require approvals by {{ insert: param, ac-02_odp.03 }} for requests to create accounts;" - }, - { - "id": "ac-2_smt.f", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "f." - } - ], - "prose": "Create, enable, modify, disable, and remove accounts in accordance with {{ insert: param, ac-02_odp.04 }};" - }, - { - "id": "ac-2_smt.g", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "g." - } - ], - "prose": "Monitor the use of accounts;" - }, - { - "id": "ac-2_smt.h", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "h." - } - ], - "prose": "Notify account managers and {{ insert: param, ac-02_odp.05 }} within:", - "parts": [ - { - "id": "ac-2_smt.h.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, ac-02_odp.06 }} when accounts are no longer required;" - }, - { - "id": "ac-2_smt.h.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "{{ insert: param, ac-02_odp.07 }} when users are terminated or transferred; and" - }, - { - "id": "ac-2_smt.h.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "{{ insert: param, ac-02_odp.08 }} when system usage or need-to-know changes for an individual;" - } - ] - }, - { - "id": "ac-2_smt.i", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "i." - } - ], - "prose": "Authorize access to the system based on:", - "parts": [ - { - "id": "ac-2_smt.i.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "A valid access authorization;" - }, - { - "id": "ac-2_smt.i.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Intended system usage; and" - }, - { - "id": "ac-2_smt.i.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "{{ insert: param, ac-02_odp.09 }};" - } - ] - }, - { - "id": "ac-2_smt.j", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "j." - } - ], - "prose": "Review accounts for compliance with account management requirements {{ insert: param, ac-02_odp.10 }};" - }, - { - "id": "ac-2_smt.k", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "k." - } - ], - "prose": "Establish and implement a process for changing shared or group account authenticators (if deployed) when individuals are removed from the group; and" - }, - { - "id": "ac-2_smt.l", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "l." - } - ], - "prose": "Align account management processes with personnel termination and transfer processes." - } - ] - }, - { - "id": "ac-2_gdn", - "name": "guidance", - "prose": "Examples of system account types include individual, shared, group, system, guest, anonymous, emergency, developer, temporary, and service. Identification of authorized system users and the specification of access privileges reflect the requirements in other controls in the security plan. Users requiring administrative privileges on system accounts receive additional scrutiny by organizational personnel responsible for approving such accounts and privileged access, including system owner, mission or business owner, senior agency information security officer, or senior agency official for privacy. Types of accounts that organizations may wish to prohibit due to increased risk include shared, group, emergency, anonymous, temporary, and guest accounts.\n\nWhere access involves personally identifiable information, security programs collaborate with the senior agency official for privacy to establish the specific conditions for group and role membership; specify authorized users, group and role membership, and access authorizations for each account; and create, adjust, or remove system accounts in accordance with organizational policies. Policies can include such information as account expiration dates or other factors that trigger the disabling of accounts. Organizations may choose to define access privileges or other attributes by account, type of account, or a combination of the two. Examples of other attributes required for authorizing access include restrictions on time of day, day of week, and point of origin. In defining other system account attributes, organizations consider system-related requirements and mission/business requirements. Failure to consider these factors could affect system availability.\n\nTemporary and emergency accounts are intended for short-term use. Organizations establish temporary accounts as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. Organizations establish emergency accounts in response to crisis situations and with the need for rapid account activation. Therefore, emergency account activation may bypass normal account authorization processes. Emergency and temporary accounts are not to be confused with infrequently used accounts, including local logon accounts used for special tasks or when network resources are unavailable (may also be known as accounts of last resort). Such accounts remain available and are not subject to automatic disabling or removal dates. Conditions for disabling or deactivating accounts include when shared/group, emergency, or temporary accounts are no longer required and when individuals are transferred or terminated. Changing shared/group authenticators when members leave the group is intended to ensure that former group members do not retain access to the shared or group account. Some types of system accounts may require specialized training." - }, - { - "id": "ac-2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-2_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02a.[01]", - "class": "sp800-53a" - } - ], - "prose": "account types allowed for use within the system are defined and documented;", - "links": [ - { - "href": "#ac-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02a.[02]", - "class": "sp800-53a" - } - ], - "prose": "account types specifically prohibited for use within the system are defined and documented;", - "links": [ - { - "href": "#ac-2_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02b.", - "class": "sp800-53a" - } - ], - "prose": "account managers are assigned;", - "links": [ - { - "href": "#ac-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02c.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ac-02_odp.01 }} for group and role membership are required;", - "links": [ - { - "href": "#ac-2_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02d.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-2_obj.d.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02d.01", - "class": "sp800-53a" - } - ], - "prose": "authorized users of the system are specified;", - "links": [ - { - "href": "#ac-2_smt.d.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.d.2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02d.02", - "class": "sp800-53a" - } - ], - "prose": "group and role membership are specified;", - "links": [ - { - "href": "#ac-2_smt.d.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.d.3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02d.03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-2_obj.d.3-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02d.03[01]", - "class": "sp800-53a" - } - ], - "prose": "access authorizations (i.e., privileges) are specified for each account;", - "links": [ - { - "href": "#ac-2_smt.d.3", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.d.3-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02d.03[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ac-02_odp.02 }} are specified for each account;", - "links": [ - { - "href": "#ac-2_smt.d.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-2_smt.d.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-2_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02e.", - "class": "sp800-53a" - } - ], - "prose": "approvals are required by {{ insert: param, ac-02_odp.03 }} for requests to create accounts;", - "links": [ - { - "href": "#ac-2_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.f", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02f.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-2_obj.f-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02f.[01]", - "class": "sp800-53a" - } - ], - "prose": "accounts are created in accordance with {{ insert: param, ac-02_odp.04 }};", - "links": [ - { - "href": "#ac-2_smt.f", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.f-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02f.[02]", - "class": "sp800-53a" - } - ], - "prose": "accounts are enabled in accordance with {{ insert: param, ac-02_odp.04 }};", - "links": [ - { - "href": "#ac-2_smt.f", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.f-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02f.[03]", - "class": "sp800-53a" - } - ], - "prose": "accounts are modified in accordance with {{ insert: param, ac-02_odp.04 }};", - "links": [ - { - "href": "#ac-2_smt.f", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.f-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02f.[04]", - "class": "sp800-53a" - } - ], - "prose": "accounts are disabled in accordance with {{ insert: param, ac-02_odp.04 }};", - "links": [ - { - "href": "#ac-2_smt.f", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.f-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02f.[05]", - "class": "sp800-53a" - } - ], - "prose": "accounts are removed in accordance with {{ insert: param, ac-02_odp.04 }};", - "links": [ - { - "href": "#ac-2_smt.f", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-2_smt.f", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.g", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02g.", - "class": "sp800-53a" - } - ], - "prose": "the use of accounts is monitored;", - "links": [ - { - "href": "#ac-2_smt.g", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.h", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02h.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-2_obj.h.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02h.01", - "class": "sp800-53a" - } - ], - "prose": "account managers and {{ insert: param, ac-02_odp.05 }} are notified within {{ insert: param, ac-02_odp.06 }} when accounts are no longer required;", - "links": [ - { - "href": "#ac-2_smt.h.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.h.2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02h.02", - "class": "sp800-53a" - } - ], - "prose": "account managers and {{ insert: param, ac-02_odp.05 }} are notified within {{ insert: param, ac-02_odp.07 }} when users are terminated or transferred;", - "links": [ - { - "href": "#ac-2_smt.h.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.h.3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02h.03", - "class": "sp800-53a" - } - ], - "prose": "account managers and {{ insert: param, ac-02_odp.05 }} are notified within {{ insert: param, ac-02_odp.08 }} when system usage or the need to know changes for an individual;", - "links": [ - { - "href": "#ac-2_smt.h.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-2_smt.h", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.i", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02i.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-2_obj.i.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02i.01", - "class": "sp800-53a" - } - ], - "prose": "access to the system is authorized based on a valid access authorization;", - "links": [ - { - "href": "#ac-2_smt.i.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.i.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02i.02", - "class": "sp800-53a" - } - ], - "prose": "access to the system is authorized based on intended system usage;", - "links": [ - { - "href": "#ac-2_smt.i.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.i.3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02i.03", - "class": "sp800-53a" - } - ], - "prose": "access to the system is authorized based on {{ insert: param, ac-02_odp.09 }};", - "links": [ - { - "href": "#ac-2_smt.i.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-2_smt.i", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.j", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02j.", - "class": "sp800-53a" - } - ], - "prose": "accounts are reviewed for compliance with account management requirements {{ insert: param, ac-02_odp.10 }};", - "links": [ - { - "href": "#ac-2_smt.j", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.k", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02k.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-2_obj.k-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02k.[01]", - "class": "sp800-53a" - } - ], - "prose": "a process is established for changing shared or group account authenticators (if deployed) when individuals are removed from the group;", - "links": [ - { - "href": "#ac-2_smt.k", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.k-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02k.[02]", - "class": "sp800-53a" - } - ], - "prose": "a process is implemented for changing shared or group account authenticators (if deployed) when individuals are removed from the group;", - "links": [ - { - "href": "#ac-2_smt.k", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-2_smt.k", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.l", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02l.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-2_obj.l-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02l.[01]", - "class": "sp800-53a" - } - ], - "prose": "account management processes are aligned with personnel termination processes;", - "links": [ - { - "href": "#ac-2_smt.l", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_obj.l-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02l.[02]", - "class": "sp800-53a" - } - ], - "prose": "account management processes are aligned with personnel transfer processes.", - "links": [ - { - "href": "#ac-2_smt.l", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-2_smt.l", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-02-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\npersonnel termination policy and procedure\n\npersonnel transfer policy and procedure\n\nprocedures for addressing account management\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of active system accounts along with the name of the individual associated with each account\n\nlist of recently disabled system accounts and the name of the individual associated with each account\n\nlist of conditions for group and role membership\n\nnotifications of recent transfers, separations, or terminations of employees\n\naccess authorization records\n\naccount management compliance reviews\n\nsystem monitoring records\n\nsystem audit records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-02-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security with information security and privacy responsibilities" - } - ] - }, - { - "id": "ac-2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-02-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for account management on the system\n\nmechanisms for implementing account management" - } - ] - } - ], - "controls": [ - { - "id": "ac-2.1", - "class": "SP800-53-enhancement", - "title": "Automated System Account Management", - "params": [ - { - "id": "ac-02.01_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2.1_prm_1" - }, - { - "name": "label", - "value": "AC-02(01)_ODP", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used to support the management of system accounts are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AC-02(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-2(1)" - }, - { - "name": "label", - "value": "AC-02(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-02.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "required" - } - ], - "parts": [ - { - "id": "ac-2.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Support the management of system accounts using {{ insert: param, ac-02.01_odp }}." - }, - { - "id": "ac-2.1_gdn", - "name": "guidance", - "prose": "Automated system account management includes using automated mechanisms to create, enable, modify, disable, and remove accounts; notify account managers when an account is created, enabled, modified, disabled, or removed, or when users are terminated or transferred; monitor system account usage; and report atypical system account usage. Automated mechanisms can include internal system functions and email, telephonic, and text messaging notifications." - }, - { - "id": "ac-2.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02(01)", - "class": "sp800-53a" - } - ], - "prose": "the management of system accounts is supported using {{ insert: param, ac-02.01_odp }}.", - "links": [ - { - "href": "#ac-2.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-02(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures for addressing account management\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-2.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-02(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "ac-2.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-02(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Automated mechanisms for implementing account management functions" - } - ] - } - ] - }, - { - "id": "ac-2.2", - "class": "SP800-53-enhancement", - "title": "Automated Temporary and Emergency Account Management", - "params": [ - { - "id": "ac-02.02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2.2_prm_1" - }, - { - "name": "label", - "value": "AC-02(02)_ODP[01]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "Selection: disables" - } - ] - }, - { - "id": "ac-02.02_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2.2_prm_2" - }, - { - "name": "alt-label", - "value": "time period for each type of account", - "class": "sp800-53" - }, - { - "name": "label", - "value": "AC-02(02)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "no more than 24 hours from last use" - } - ], - "guidelines": [ - { - "prose": "the time period after which to automatically remove or disable temporary or emergency accounts is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AC-02(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-2(2)" - }, - { - "name": "label", - "value": "AC-02(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-02.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "required" - } - ], - "parts": [ - { - "id": "ac-2.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Automatically {{ insert: param, ac-02.02_odp.01 }} temporary and emergency accounts after {{ insert: param, ac-02.02_odp.02 }}." - }, - { - "id": "ac-2.2_gdn", - "name": "guidance", - "prose": "Management of temporary and emergency accounts includes the removal or disabling of such accounts automatically after a predefined time period rather than at the convenience of the system administrator. Automatic removal or disabling of accounts provides a more consistent implementation." - }, - { - "id": "ac-2.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02(02)", - "class": "sp800-53a" - } - ], - "prose": "temporary and emergency accounts are automatically {{ insert: param, ac-02.02_odp.01 }} after {{ insert: param, ac-02.02_odp.02 }}.", - "links": [ - { - "href": "#ac-2.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-02(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures for addressing account management\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem-generated list of temporary accounts removed and/or disabled\n\nsystem-generated list of emergency accounts removed and/or disabled\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-2.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-02(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "ac-2.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-02(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Automated mechanisms for implementing account management functions" - } - ] - } - ] - }, - { - "id": "ac-2.3", - "class": "SP800-53-enhancement", - "title": "Disable Accounts", - "params": [ - { - "id": "ac-02.03_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2.3_prm_1" - }, - { - "name": "label", - "value": "AC-02(03)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "24 hours for user accounts" - } - ], - "guidelines": [ - { - "prose": "time period within which to disable accounts is defined;" - } - ] - }, - { - "id": "ac-02.03_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2.3_prm_2" - }, - { - "name": "label", - "value": "AC-02(03)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "thirty-five (35) days (See additional requirements and guidance.)" - } - ], - "guidelines": [ - { - "prose": "time period for account inactivity before disabling is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AC-02(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-2(3)" - }, - { - "name": "label", - "value": "AC-02(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-02.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "required" - } - ], - "parts": [ - { - "id": "ac-2.3_smt", - "name": "statement", - "prose": "Disable accounts within {{ insert: param, ac-02.03_odp.01 }} when the accounts:", - "parts": [ - { - "id": "ac-2.3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Have expired;" - }, - { - "id": "ac-2.3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Are no longer associated with a user or individual;" - }, - { - "id": "ac-2.3_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Are in violation of organizational policy; or" - }, - { - "id": "ac-2.3_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(d)" - } - ], - "prose": "Have been inactive for {{ insert: param, ac-02.03_odp.02 }}." - } - ] - }, - { - "id": "ac-2.3_gdn", - "name": "guidance", - "prose": "Disabling expired, inactive, or otherwise anomalous accounts supports the concepts of least privilege and least functionality which reduce the attack surface of the system." - }, - { - "id": "ac-2.3_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "AC-2 (3) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ac-2.3_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "The service provider defines the time period for non-user accounts (e.g., accounts associated with devices). The time periods are approved and accepted by the AO. Where user management is a function of the service, reports of activity of consumer users shall be made available." - }, - { - "id": "ac-2.3_fr_smt.2", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(d) Requirement:" - } - ], - "prose": "The service provider defines the time period of inactivity for device identifiers." - }, - { - "id": "ac-2.3_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "For DoD clouds, see DoD cloud website for specific DoD requirements that go above and beyond FedRAMP https://public.cyber.mil/dccs/." - } - ] - }, - { - "id": "ac-2.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02(03)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-2.3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02(03)(a)", - "class": "sp800-53a" - } - ], - "prose": "accounts are disabled within {{ insert: param, ac-02.03_odp.01 }} when the accounts have expired;", - "links": [ - { - "href": "#ac-2.3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02(03)(b)", - "class": "sp800-53a" - } - ], - "prose": "accounts are disabled within {{ insert: param, ac-02.03_odp.01 }} when the accounts are no longer associated with a user or individual;", - "links": [ - { - "href": "#ac-2.3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.3_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02(03)(c)", - "class": "sp800-53a" - } - ], - "prose": "accounts are disabled within {{ insert: param, ac-02.03_odp.01 }} when the accounts are in violation of organizational policy;", - "links": [ - { - "href": "#ac-2.3_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.3_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02(03)(d)", - "class": "sp800-53a" - } - ], - "prose": "accounts are disabled within {{ insert: param, ac-02.03_odp.01 }} when the accounts have been inactive for {{ insert: param, ac-02.03_odp.02 }}.", - "links": [ - { - "href": "#ac-2.3_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-2.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-02(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures for addressing account management\n\nsystem security plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem-generated list of accounts removed\n\nsystem-generated list of emergency accounts disabled\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-2.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-02(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "ac-2.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-02(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms for implementing account management functions" - } - ] - } - ] - }, - { - "id": "ac-2.4", - "class": "SP800-53-enhancement", - "title": "Automated Audit Actions", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AC-02(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-2(4)" - }, - { - "name": "label", - "value": "AC-02(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-02.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "required" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-2.4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Automatically audit account creation, modification, enabling, disabling, and removal actions." - }, - { - "id": "ac-2.4_gdn", - "name": "guidance", - "prose": "Account management audit records are defined in accordance with [AU-02](#au-2) and reviewed, analyzed, and reported in accordance with [AU-06](#au-6)." - }, - { - "id": "ac-2.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02(04)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-2.4_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02(04)[01]", - "class": "sp800-53a" - } - ], - "prose": "account creation is automatically audited;", - "links": [ - { - "href": "#ac-2.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.4_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02(04)[02]", - "class": "sp800-53a" - } - ], - "prose": "account modification is automatically audited;", - "links": [ - { - "href": "#ac-2.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.4_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02(04)[03]", - "class": "sp800-53a" - } - ], - "prose": "account enabling is automatically audited;", - "links": [ - { - "href": "#ac-2.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.4_obj-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02(04)[04]", - "class": "sp800-53a" - } - ], - "prose": "account disabling is automatically audited;", - "links": [ - { - "href": "#ac-2.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.4_obj-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02(04)[05]", - "class": "sp800-53a" - } - ], - "prose": "account removal actions are automatically audited.", - "links": [ - { - "href": "#ac-2.4_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-2.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-02(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nnotifications/alerts of account creation, modification, enabling, disabling, and removal actions\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-2.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-02(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ac-2.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-02(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Automated mechanisms implementing account management functions" - } - ] - } - ] - }, - { - "id": "ac-2.5", - "class": "SP800-53-enhancement", - "title": "Inactivity Logout", - "params": [ - { - "id": "ac-02.05_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2.5_prm_1" - }, - { - "name": "label", - "value": "AC-02(05)_ODP", - "class": "sp800-53a" - } - ], - "label": "time period of expected inactivity or description of when to log out", - "constraints": [ - { - "description": "inactivity is anticipated to exceed Fifteen (15) minutes" - } - ], - "guidelines": [ - { - "prose": "the time period of expected inactivity or description of when to log out is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AC-02(05)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-2(5)" - }, - { - "name": "label", - "value": "AC-02(05)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-02.05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "required" - }, - { - "href": "#ac-11", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-2.5_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Require that users log out when {{ insert: param, ac-02.05_odp }}." - }, - { - "id": "ac-2.5_gdn", - "name": "guidance", - "prose": "Inactivity logout is behavior- or policy-based and requires users to take physical action to log out when they are expecting inactivity longer than the defined period. Automatic enforcement of inactivity logout is addressed by [AC-11](#ac-11)." - }, - { - "id": "ac-2.5_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "AC-2 (5) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ac-2.5_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Should use a shorter timeframe than AC-12." - } - ] - }, - { - "id": "ac-2.5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02(05)", - "class": "sp800-53a" - } - ], - "prose": "users are required to log out when {{ insert: param, ac-02.05_odp }}.", - "links": [ - { - "href": "#ac-2.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-02(05)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsecurity violation reports\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-2.5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-02(05)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nusers that must comply with inactivity logout policy" - } - ] - } - ] - }, - { - "id": "ac-2.7", - "class": "SP800-53-enhancement", - "title": "Privileged User Accounts", - "params": [ - { - "id": "ac-02.07_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2.7_prm_1" - }, - { - "name": "label", - "value": "AC-02(07)_ODP", - "class": "sp800-53a" - } - ], - "select": { - "choice": [ - "a role-based access scheme", - "an attribute-based access scheme" - ] - } - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AC-02(07)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-2(7)" - }, - { - "name": "label", - "value": "AC-02(07)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-02.07" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "required" - } - ], - "parts": [ - { - "id": "ac-2.7_smt", - "name": "statement", - "parts": [ - { - "id": "ac-2.7_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Establish and administer privileged user accounts in accordance with {{ insert: param, ac-02.07_odp }};" - }, - { - "id": "ac-2.7_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Monitor privileged role or attribute assignments;" - }, - { - "id": "ac-2.7_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Monitor changes to roles or attributes; and" - }, - { - "id": "ac-2.7_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(d)" - } - ], - "prose": "Revoke access when privileged role or attribute assignments are no longer appropriate." - } - ] - }, - { - "id": "ac-2.7_gdn", - "name": "guidance", - "prose": "Privileged roles are organization-defined roles assigned to individuals that allow those individuals to perform certain security-relevant functions that ordinary users are not authorized to perform. Privileged roles include key management, account management, database administration, system and network administration, and web administration. A role-based access scheme organizes permitted system access and privileges into roles. In contrast, an attribute-based access scheme specifies allowed system access and privileges based on attributes." - }, - { - "id": "ac-2.7_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02(07)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-2.7_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02(07)(a)", - "class": "sp800-53a" - } - ], - "prose": "privileged user accounts are established and administered in accordance with {{ insert: param, ac-02.07_odp }};", - "links": [ - { - "href": "#ac-2.7_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.7_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02(07)(b)", - "class": "sp800-53a" - } - ], - "prose": "privileged role or attribute assignments are monitored;", - "links": [ - { - "href": "#ac-2.7_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.7_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02(07)(c)", - "class": "sp800-53a" - } - ], - "prose": "changes to roles or attributes are monitored;", - "links": [ - { - "href": "#ac-2.7_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.7_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02(07)(d)", - "class": "sp800-53a" - } - ], - "prose": "access is revoked when privileged role or attribute assignments are no longer appropriate.", - "links": [ - { - "href": "#ac-2.7_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-2.7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.7_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-02(07)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem-generated list of privileged user accounts and associated roles\n\nrecords of actions taken when privileged role assignments are no longer appropriate\n\nsystem audit records\n\naudit tracking and monitoring reports\n\nsystem monitoring records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-2.7_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-02(07)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ac-2.7_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-02(07)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing account management functions\n\nmechanisms monitoring privileged role assignments" - } - ] - } - ] - }, - { - "id": "ac-2.9", - "class": "SP800-53-enhancement", - "title": "Restrictions on Use of Shared and Group Accounts", - "params": [ - { - "id": "ac-02.09_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2.9_prm_1" - }, - { - "name": "alt-label", - "value": "conditions for establishing shared and group accounts", - "class": "sp800-53" - }, - { - "name": "label", - "value": "AC-02(09)_ODP", - "class": "sp800-53a" - } - ], - "label": "conditions", - "constraints": [ - { - "description": "organization-defined need with justification statement that explains why such accounts are necessary" - } - ], - "guidelines": [ - { - "prose": "conditions for establishing shared and group accounts are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AC-02(09)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-2(9)" - }, - { - "name": "label", - "value": "AC-02(09)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-02.09" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "required" - } - ], - "parts": [ - { - "id": "ac-2.9_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Only permit the use of shared and group accounts that meet {{ insert: param, ac-02.09_odp }}." - }, - { - "id": "ac-2.9_gdn", - "name": "guidance", - "prose": "Before permitting the use of shared or group accounts, organizations consider the increased risk due to the lack of accountability with such accounts." - }, - { - "id": "ac-2.9_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "AC-2 (9) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ac-2.9_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Required if shared/group accounts are deployed." - } - ] - }, - { - "id": "ac-2.9_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02(09)", - "class": "sp800-53a" - } - ], - "prose": "the use of shared and group accounts is only permitted if {{ insert: param, ac-02.09_odp }} are met.", - "links": [ - { - "href": "#ac-2.9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.9_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-02(09)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem-generated list of shared/group accounts and associated roles\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-2.9_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-02(09)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ac-2.9_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-02(09)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing management of shared/group accounts" - } - ] - } - ] - }, - { - "id": "ac-2.11", - "class": "SP800-53-enhancement", - "title": "Usage Conditions", - "params": [ - { - "id": "ac-02.11_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2.11_prm_1" - }, - { - "name": "label", - "value": "AC-02(11)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "circumstances and/or usage conditions", - "guidelines": [ - { - "prose": "circumstances and/or usage conditions to be enforced for system accounts are defined;" - } - ] - }, - { - "id": "ac-02.11_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2.11_prm_2" - }, - { - "name": "label", - "value": "AC-02(11)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "system accounts", - "guidelines": [ - { - "prose": "system accounts subject to enforcement of circumstances and/or usage conditions are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AC-02(11)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-2(11)" - }, - { - "name": "label", - "value": "AC-02(11)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-02.11" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "required" - } - ], - "parts": [ - { - "id": "ac-2.11_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Enforce {{ insert: param, ac-02.11_odp.01 }} for {{ insert: param, ac-02.11_odp.02 }}." - }, - { - "id": "ac-2.11_gdn", - "name": "guidance", - "prose": "Specifying and enforcing usage conditions helps to enforce the principle of least privilege, increase user accountability, and enable effective account monitoring. Account monitoring includes alerts generated if the account is used in violation of organizational parameters. Organizations can describe specific conditions or circumstances under which system accounts can be used, such as by restricting usage to certain days of the week, time of day, or specific durations of time." - }, - { - "id": "ac-2.11_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02(11)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ac-02.11_odp.01 }} for {{ insert: param, ac-02.11_odp.02 }} are enforced.", - "links": [ - { - "href": "#ac-2.11_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.11_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-02(11)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem-generated list of system accounts and associated assignments of usage circumstances and/or usage conditions\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-2.11_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-02(11)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "ac-2.11_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-02(11)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing account management functions" - } - ] - } - ] - }, - { - "id": "ac-2.12", - "class": "SP800-53-enhancement", - "title": "Account Monitoring for Atypical Usage", - "params": [ - { - "id": "ac-02.12_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2.12_prm_1" - }, - { - "name": "label", - "value": "AC-02(12)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "atypical usage", - "guidelines": [ - { - "prose": "atypical usage for which to monitor system accounts is defined;" - } - ] - }, - { - "id": "ac-02.12_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2.12_prm_2" - }, - { - "name": "label", - "value": "AC-02(12)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "constraints": [ - { - "description": "at a minimum, the ISSO and/or similar role within the organization" - } - ], - "guidelines": [ - { - "prose": "personnel or roles to report atypical usage is/are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AC-02(12)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-2(12)" - }, - { - "name": "label", - "value": "AC-02(12)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-02.12" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "required" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-7", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-2.12_smt", - "name": "statement", - "parts": [ - { - "id": "ac-2.12_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Monitor system accounts for {{ insert: param, ac-02.12_odp.01 }} ; and" - }, - { - "id": "ac-2.12_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Report atypical usage of system accounts to {{ insert: param, ac-02.12_odp.02 }}." - } - ] - }, - { - "id": "ac-2.12_gdn", - "name": "guidance", - "prose": "Atypical usage includes accessing systems at certain times of the day or from locations that are not consistent with the normal usage patterns of individuals. Monitoring for atypical usage may reveal rogue behavior by individuals or an attack in progress. Account monitoring may inadvertently create privacy risks since data collected to identify atypical usage may reveal previously unknown information about the behavior of individuals. Organizations assess and document privacy risks from monitoring accounts for atypical usage in their privacy impact assessment and make determinations that are in alignment with their privacy program plan." - }, - { - "id": "ac-2.12_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "AC-2 (12) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ac-2.12_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(a) Requirement:" - } - ], - "prose": "Required for privileged accounts." - }, - { - "id": "ac-2.12_fr_smt.2", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(b) Requirement:" - } - ], - "prose": "Required for privileged accounts." - } - ] - }, - { - "id": "ac-2.12_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-02(12)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-2.12_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02(12)(a)", - "class": "sp800-53a" - } - ], - "prose": "system accounts are monitored for {{ insert: param, ac-02.12_odp.01 }};", - "links": [ - { - "href": "#ac-2.12_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.12_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02(12)(b)", - "class": "sp800-53a" - } - ], - "prose": "atypical usage of system accounts is reported to {{ insert: param, ac-02.12_odp.02 }}.", - "links": [ - { - "href": "#ac-2.12_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-2.12_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.12_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-02(12)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem monitoring records\n\nsystem audit records\n\naudit tracking and monitoring reports\n\nprivacy impact assessment\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-2.12_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-02(12)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ac-2.12_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-02(12)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing account management functions" - } - ] - } - ] - }, - { - "id": "ac-2.13", - "class": "SP800-53-enhancement", - "title": "Disable Accounts for High-risk Individuals", - "params": [ - { - "id": "ac-02.13_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2.13_prm_1" - }, - { - "name": "label", - "value": "AC-02(13)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "one (1) hour" - } - ], - "guidelines": [ - { - "prose": "time period within which to disable accounts of individuals who are discovered to pose significant risk is defined;" - } - ] - }, - { - "id": "ac-02.13_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ac-2.13_prm_2" - }, - { - "name": "label", - "value": "AC-02(13)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "significant risks", - "guidelines": [ - { - "prose": "significant risks leading to disabling accounts are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AC-02(13)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-2(13)" - }, - { - "name": "label", - "value": "AC-02(13)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-02.13" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "required" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-2.13_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Disable accounts of individuals within {{ insert: param, ac-02.13_odp.01 }} of discovery of {{ insert: param, ac-02.13_odp.02 }}." - }, - { - "id": "ac-2.13_gdn", - "name": "guidance", - "prose": "Users who pose a significant security and/or privacy risk include individuals for whom reliable evidence indicates either the intention to use authorized access to systems to cause harm or through whom adversaries will cause harm. Such harm includes adverse impacts to organizational operations, organizational assets, individuals, other organizations, or the Nation. Close coordination among system administrators, legal staff, human resource managers, and authorizing officials is essential when disabling system accounts for high-risk individuals." - }, - { - "id": "ac-2.13_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-02(13)", - "class": "sp800-53a" - } - ], - "prose": "accounts of individuals are disabled within {{ insert: param, ac-02.13_odp.01 }} of discovery of {{ insert: param, ac-02.13_odp.02 }}.", - "links": [ - { - "href": "#ac-2.13_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-2.13_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-02(13)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing account management\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem-generated list of disabled accounts\n\nlist of user activities posing significant organizational risk\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-2.13_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-02(13)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ac-2.13_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-02(13)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing account management functions" - } - ] - } - ] - } - ] - }, - { - "id": "ac-3", - "class": "SP800-53", - "title": "Access Enforcement", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AC-03", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-3" - }, - { - "name": "label", - "value": "AC-03", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#18e71fec-c6fd-475a-925a-5d8495cf8455", - "rel": "reference" - }, - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#110e26af-4765-49e1-8740-6750f83fcda1", - "rel": "reference" - }, - { - "href": "#e7942589-e267-4a5a-a3d9-f39a7aae81f0", - "rel": "reference" - }, - { - "href": "#8306620b-1920-4d73-8b21-12008528595f", - "rel": "reference" - }, - { - "href": "#2956e175-f674-43f4-b1b9-e074ad9fc39c", - "rel": "reference" - }, - { - "href": "#388a3aa2-5d85-4bad-b8a3-77db80d63c4f", - "rel": "reference" - }, - { - "href": "#7f473f21-fdbf-4a6c-81a1-0ab95919609d", - "rel": "reference" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-5", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ac-16", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#ac-20", - "rel": "related" - }, - { - "href": "#ac-21", - "rel": "related" - }, - { - "href": "#ac-22", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ac-24", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ac-25", - "rel": "related" - }, - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "#ca-9", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-11", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#ia-6", - "rel": "related" - }, - { - "href": "#ia-7", - "rel": "related" - }, - { - "href": "#ia-11", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ia-13", - "rel": "related" - }, - { - "href": "#ma-3", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#ma-5", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-2", - "rel": "related" - }, - { - "href": "#ps-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-3", - "rel": "related" - }, - { - "href": "#sa-17", - "rel": "related" - }, - { - "href": "#sc-2", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - }, - { - "href": "#sc-4", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#sc-28", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-31", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-34", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-8", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies." - }, - { - "id": "ac-3_gdn", - "name": "guidance", - "prose": "Access control policies control access between active entities or subjects (i.e., users or processes acting on behalf of users) and passive entities or objects (i.e., devices, files, records, domains) in organizational systems. In addition to enforcing authorized access at the system level and recognizing that systems can host many applications and services in support of mission and business functions, access enforcement mechanisms can also be employed at the application and service level to provide increased information security and privacy. In contrast to logical access controls that are implemented within the system, physical access controls are addressed by the controls in the Physical and Environmental Protection ( [PE](#pe) ) family." - }, - { - "id": "ac-3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-03", - "class": "sp800-53a" - } - ], - "prose": "approved authorizations for logical access to information and system resources are enforced in accordance with applicable access control policies.", - "links": [ - { - "href": "#ac-3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-03-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing access enforcement\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of approved authorizations (user privileges)\n\nsystem audit records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-03-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with access enforcement responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security and privacy responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "ac-3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-03-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing access control policy" - } - ] - } - ] - }, - { - "id": "ac-4", - "class": "SP800-53", - "title": "Information Flow Enforcement", - "params": [ - { - "id": "ac-04_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ac-4_prm_1" - }, - { - "name": "label", - "value": "AC-04_ODP", - "class": "sp800-53a" - } - ], - "label": "information flow control policies", - "guidelines": [ - { - "prose": "information flow control policies within the system and between connected systems are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AC-04", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-4" - }, - { - "name": "label", - "value": "AC-04", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "#2956e175-f674-43f4-b1b9-e074ad9fc39c", - "rel": "reference" - }, - { - "href": "#388a3aa2-5d85-4bad-b8a3-77db80d63c4f", - "rel": "reference" - }, - { - "href": "#a2590922-82f3-4277-83c0-ca5bee06dba4", - "rel": "reference" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ac-16", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#ac-21", - "rel": "related" - }, - { - "href": "#au-10", - "rel": "related" - }, - { - "href": "#ca-3", - "rel": "related" - }, - { - "href": "#ca-9", - "rel": "related" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pl-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-24", - "rel": "related" - }, - { - "href": "#sa-17", - "rel": "related" - }, - { - "href": "#sc-4", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-16", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-31", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Enforce approved authorizations for controlling the flow of information within the system and between connected systems based on {{ insert: param, ac-04_odp }}." - }, - { - "id": "ac-4_gdn", - "name": "guidance", - "prose": "Information flow control regulates where information can travel within a system and between systems (in contrast to who is allowed to access the information) and without regard to subsequent accesses to that information. Flow control restrictions include blocking external traffic that claims to be from within the organization, keeping export-controlled information from being transmitted in the clear to the Internet, restricting web requests that are not from the internal web proxy server, and limiting information transfers between organizations based on data structures and content. Transferring information between organizations may require an agreement specifying how the information flow is enforced (see [CA-3](#ca-3) ). Transferring information between systems in different security or privacy domains with different security or privacy policies introduces the risk that such transfers violate one or more domain security or privacy policies. In such situations, information owners/stewards provide guidance at designated policy enforcement points between connected systems. Organizations consider mandating specific architectural solutions to enforce specific security and privacy policies. Enforcement includes prohibiting information transfers between connected systems (i.e., allowing access only), verifying write permissions before accepting information from another security or privacy domain or connected system, employing hardware mechanisms to enforce one-way information flows, and implementing trustworthy regrading mechanisms to reassign security or privacy attributes and labels.\n\nOrganizations commonly employ information flow control policies and enforcement mechanisms to control the flow of information between designated sources and destinations within systems and between connected systems. Flow control is based on the characteristics of the information and/or the information path. Enforcement occurs, for example, in boundary protection devices that employ rule sets or establish configuration settings that restrict system services, provide a packet-filtering capability based on header information, or provide a message-filtering capability based on message content. Organizations also consider the trustworthiness of filtering and/or inspection mechanisms (i.e., hardware, firmware, and software components) that are critical to information flow enforcement. Control enhancements 3 through 32 primarily address cross-domain solution needs that focus on more advanced filtering techniques, in-depth analysis, and stronger flow enforcement mechanisms implemented in cross-domain products, such as high-assurance guards. Such capabilities are generally not available in commercial off-the-shelf products. Information flow enforcement also applies to control plane traffic (e.g., routing and DNS)." - }, - { - "id": "ac-4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-04", - "class": "sp800-53a" - } - ], - "prose": "approved authorizations are enforced for controlling the flow of information within the system and between connected systems based on {{ insert: param, ac-04_odp }}.", - "links": [ - { - "href": "#ac-4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-04-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\nsecurity architecture documentation\n\nprivacy architecture documentation\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem baseline configuration\n\nlist of information flow authorizations\n\nsystem audit records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-04-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security and privacy architecture development responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "ac-4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-04-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing information flow enforcement policy" - } - ] - } - ], - "controls": [ - { - "id": "ac-4.4", - "class": "SP800-53-enhancement", - "title": "Flow Control of Encrypted Information", - "params": [ - { - "id": "ac-04.04_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ac-4.4_prm_1" - }, - { - "name": "label", - "value": "AC-04(04)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "information flow control mechanisms", - "constraints": [ - { - "description": "intrusion detection mechanisms" - } - ], - "guidelines": [ - { - "prose": "information flow control mechanisms that encrypted information is prevented from bypassing are defined;" - } - ] - }, - { - "id": "ac-04.04_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ac-4.4_prm_2" - }, - { - "name": "label", - "value": "AC-04(04)_ODP[02]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "decrypting the information", - "blocking the flow of the encrypted information", - "terminating communications sessions attempting to pass encrypted information", - "{{ insert: param, ac-04.04_odp.03 }}" - ] - } - }, - { - "id": "ac-04.04_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ac-4.4_prm_3" - }, - { - "name": "alt-label", - "value": "procedure or method", - "class": "sp800-53" - }, - { - "name": "label", - "value": "AC-04(04)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "organization-defined procedure or method", - "guidelines": [ - { - "prose": "the organization-defined procedure or method used to prevent encrypted information from bypassing information flow control mechanisms is defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AC-04(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-4(4)" - }, - { - "name": "label", - "value": "AC-04(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-04.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-4", - "rel": "required" - }, - { - "href": "#si-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-4.4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Prevent encrypted information from bypassing {{ insert: param, ac-04.04_odp.01 }} by {{ insert: param, ac-04.04_odp.02 }}." - }, - { - "id": "ac-4.4_gdn", - "name": "guidance", - "prose": "Flow control mechanisms include content checking, security policy filters, and data type identifiers. The term encryption is extended to cover encoded data not recognized by filtering mechanisms." - }, - { - "id": "ac-4.4_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "AC-4 (4) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ac-4.4_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "The service provider must support Agency requirements to comply with M-21-31 (https://www.whitehouse.gov/wp-content/uploads/2021/08/M-21-31-Improving-the-Federal-Governments-Investigative-and-Remediation-Capabilities-Related-to-Cybersecurity-Incidents.pdf) and M-22-09 (https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf)." - } - ] - }, - { - "id": "ac-4.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-04(04)", - "class": "sp800-53a" - } - ], - "prose": "encrypted information is prevented from bypassing {{ insert: param, ac-04.04_odp.01 }} by {{ insert: param, ac-04.04_odp.02 }}.", - "links": [ - { - "href": "#ac-4.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-4.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-04(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-4.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-04(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "ac-4.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-04(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing information flow enforcement policy" - } - ] - } - ] - }, - { - "id": "ac-4.21", - "class": "SP800-53-enhancement", - "title": "Physical or Logical Separation of Information Flows", - "params": [ - { - "id": "ac-4.21_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ac-04.21_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ac-04.21_odp.02" - } - ], - "label": "organization-defined mechanisms and/or techniques" - }, - { - "id": "ac-04.21_odp.01", - "props": [ - { - "name": "label", - "value": "AC-04(21)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "mechanisms and/or techniques", - "guidelines": [ - { - "prose": "mechanisms and/or techniques used to logically separate information flows are defined (if selected);" - } - ] - }, - { - "id": "ac-04.21_odp.02", - "props": [ - { - "name": "label", - "value": "AC-04(21)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "mechanisms and/or techniques", - "guidelines": [ - { - "prose": "mechanisms and/or techniques used to physically separate information flows are defined (if selected);" - } - ] - }, - { - "id": "ac-04.21_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ac-4.21_prm_2" - }, - { - "name": "alt-label", - "value": "required separations by types of information", - "class": "sp800-53" - }, - { - "name": "label", - "value": "AC-04(21)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "required separations", - "guidelines": [ - { - "prose": "required separations by types of information are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AC-04(21)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-4(21)" - }, - { - "name": "label", - "value": "AC-04(21)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-04.21" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-4", - "rel": "required" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-32", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-4.21_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Separate information flows logically or physically using {{ insert: param, ac-4.21_prm_1 }} to accomplish {{ insert: param, ac-04.21_odp.03 }}." - }, - { - "id": "ac-4.21_gdn", - "name": "guidance", - "prose": "Enforcing the separation of information flows associated with defined types of data can enhance protection by ensuring that information is not commingled while in transit and by enabling flow control by transmission paths that are not otherwise achievable. Types of separable information include inbound and outbound communications traffic, service requests and responses, and information of differing security impact or classification levels." - }, - { - "id": "ac-4.21_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-04(21)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-4.21_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-04(21)[01]", - "class": "sp800-53a" - } - ], - "prose": "information flows are separated logically using {{ insert: param, ac-04.21_odp.01 }} to accomplish {{ insert: param, ac-04.21_odp.03 }};", - "links": [ - { - "href": "#ac-4.21_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-4.21_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-04(21)[02]", - "class": "sp800-53a" - } - ], - "prose": "information flows are separated physically using {{ insert: param, ac-04.21_odp.02 }} to accomplish {{ insert: param, ac-04.21_odp.03 }}.", - "links": [ - { - "href": "#ac-4.21_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-4.21_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-4.21_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-04(21)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Information flow enforcement policy\n\ninformation flow control policies\n\nprocedures addressing information flow enforcement\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of required separation of information flows by information types\n\nlist of mechanisms and/or techniques used to logically or physically separate information flows\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-4.21_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-04(21)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with information flow enforcement responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "ac-4.21_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-04(21)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing information flow enforcement functions" - } - ] - } - ] - } - ] - }, - { - "id": "ac-5", - "class": "SP800-53", - "title": "Separation of Duties", - "params": [ - { - "id": "ac-05_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ac-5_prm_1" - }, - { - "name": "alt-label", - "value": "duties of individuals requiring separation", - "class": "sp800-53" - }, - { - "name": "label", - "value": "AC-05_ODP", - "class": "sp800-53a" - } - ], - "label": "duties of individuals", - "guidelines": [ - { - "prose": "duties of individuals requiring separation are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AC-05", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-5" - }, - { - "name": "label", - "value": "AC-05", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-11", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#ia-12", - "rel": "related" - }, - { - "href": "#ma-3", - "rel": "related" - }, - { - "href": "#ma-5", - "rel": "related" - }, - { - "href": "#ps-2", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-17", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-5_smt", - "name": "statement", - "parts": [ - { - "id": "ac-5_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Identify and document {{ insert: param, ac-05_odp }} ; and" - }, - { - "id": "ac-5_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Define system access authorizations to support separation of duties." - } - ] - }, - { - "id": "ac-5_gdn", - "name": "guidance", - "prose": "Separation of duties addresses the potential for abuse of authorized privileges and helps to reduce the risk of malevolent activity without collusion. Separation of duties includes dividing mission or business functions and support functions among different individuals or roles, conducting system support functions with different individuals, and ensuring that security personnel who administer access control functions do not also administer audit functions. Because separation of duty violations can span systems and application domains, organizations consider the entirety of systems and system components when developing policy on separation of duties. Separation of duties is enforced through the account management activities in [AC-2](#ac-2) , access control mechanisms in [AC-3](#ac-3) , and identity management activities in [IA-2](#ia-2), [IA-4](#ia-4) , and [IA-12](#ia-12)." - }, - { - "id": "ac-5_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "AC-5 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ac-5_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "CSPs have the option to provide a separation of duties matrix as an attachment to the SSP." - } - ] - }, - { - "id": "ac-5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-05", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-5_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-05a.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ac-05_odp }} are identified and documented;", - "links": [ - { - "href": "#ac-5_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-5_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-05b.", - "class": "sp800-53a" - } - ], - "prose": "system access authorizations to support separation of duties are defined.", - "links": [ - { - "href": "#ac-5_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-05-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing divisions of responsibility and separation of duties\n\nsystem configuration settings and associated documentation\n\nlist of divisions of responsibility and separation of duties\n\nsystem access authorizations\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-05-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for defining appropriate divisions of responsibility and separation of duties\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "ac-5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-05-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing separation of duties policy" - } - ] - } - ] - }, - { - "id": "ac-6", - "class": "SP800-53", - "title": "Least Privilege", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AC-06", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-6" - }, - { - "name": "label", - "value": "AC-06", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-06" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-5", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ac-16", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-11", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-12", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "#sa-17", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-38", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-6_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Employ the principle of least privilege, allowing only authorized accesses for users (or processes acting on behalf of users) that are necessary to accomplish assigned organizational tasks." - }, - { - "id": "ac-6_gdn", - "name": "guidance", - "prose": "Organizations employ least privilege for specific duties and systems. The principle of least privilege is also applied to system processes, ensuring that the processes have access to systems and operate at privilege levels no higher than necessary to accomplish organizational missions or business functions. Organizations consider the creation of additional processes, roles, and accounts as necessary to achieve least privilege. Organizations apply least privilege to the development, implementation, and operation of organizational systems." - }, - { - "id": "ac-6_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-06", - "class": "sp800-53a" - } - ], - "prose": "the principle of least privilege is employed, allowing only authorized accesses for users (or processes acting on behalf of users) that are necessary to accomplish assigned organizational tasks.", - "links": [ - { - "href": "#ac-6_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-6_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-06-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\nlist of assigned access authorizations (user privileges)\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-6_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-06-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for defining least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "ac-6_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-06-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing least privilege functions" - } - ] - } - ], - "controls": [ - { - "id": "ac-6.1", - "class": "SP800-53-enhancement", - "title": "Authorize Access to Security Functions", - "params": [ - { - "id": "ac-6.1_prm_2", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ac-06.01_odp.02" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ac-06.01_odp.03" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ac-06.01_odp.04" - } - ], - "label": "organization-defined security functions (deployed in hardware, software, and firmware)" - }, - { - "id": "ac-06.01_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ac-6.1_prm_1" - }, - { - "name": "alt-label", - "value": "individuals or roles", - "class": "sp800-53" - }, - { - "name": "label", - "value": "AC-06(01)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "individuals and roles", - "guidelines": [ - { - "prose": "individuals and roles with authorized access to security functions and security-relevant information are defined;" - } - ] - }, - { - "id": "ac-06.01_odp.02", - "props": [ - { - "name": "label", - "value": "AC-06(01)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "security functions (deployed in hardware)", - "constraints": [ - { - "description": "all functions not publicly accessible" - } - ], - "guidelines": [ - { - "prose": "security functions (deployed in hardware) for authorized access are defined;" - } - ] - }, - { - "id": "ac-06.01_odp.03", - "props": [ - { - "name": "label", - "value": "AC-06(01)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "security functions (deployed in software)", - "constraints": [ - { - "description": "all functions not publicly accessible" - } - ], - "guidelines": [ - { - "prose": "security functions (deployed in software) for authorized access are defined;" - } - ] - }, - { - "id": "ac-06.01_odp.04", - "props": [ - { - "name": "label", - "value": "AC-06(01)_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "security functions (deployed in firmware)", - "constraints": [ - { - "description": "all functions not publicly accessible" - } - ], - "guidelines": [ - { - "prose": "security functions (deployed in firmware) for authorized access are defined;" - } - ] - }, - { - "id": "ac-06.01_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "ac-6.1_prm_3" - }, - { - "name": "label", - "value": "AC-06(01)_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "security-relevant information", - "constraints": [ - { - "description": "all security-relevant information not publicly available" - } - ], - "guidelines": [ - { - "prose": "security-relevant information for authorized access is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AC-06(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-6(1)" - }, - { - "name": "label", - "value": "AC-06(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-06.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-6", - "rel": "required" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-6.1_smt", - "name": "statement", - "prose": "Authorize access for {{ insert: param, ac-06.01_odp.01 }} to:", - "parts": [ - { - "id": "ac-6.1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "{{ insert: param, ac-6.1_prm_2 }} ; and" - }, - { - "id": "ac-6.1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "{{ insert: param, ac-06.01_odp.05 }}." - } - ] - }, - { - "id": "ac-6.1_gdn", - "name": "guidance", - "prose": "Security functions include establishing system accounts, configuring access authorizations (i.e., permissions, privileges), configuring settings for events to be audited, and establishing intrusion detection parameters. Security-relevant information includes filtering rules for routers or firewalls, configuration parameters for security services, cryptographic key management information, and access control lists. Authorized personnel include security administrators, system administrators, system security officers, system programmers, and other privileged users." - }, - { - "id": "ac-6.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-06(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-6.1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-06(01)(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-6.1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-06(01)(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "access is authorized for {{ insert: param, ac-06.01_odp.01 }} to {{ insert: param, ac-06.01_odp.02 }};", - "links": [ - { - "href": "#ac-6.1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-6.1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-06(01)(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "access is authorized for {{ insert: param, ac-06.01_odp.01 }} to {{ insert: param, ac-06.01_odp.03 }};", - "links": [ - { - "href": "#ac-6.1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-6.1_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-06(01)(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "access is authorized for {{ insert: param, ac-06.01_odp.01 }} to {{ insert: param, ac-06.01_odp.04 }};", - "links": [ - { - "href": "#ac-6.1_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-6.1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-6.1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-06(01)(b)", - "class": "sp800-53a" - } - ], - "prose": "access is authorized for {{ insert: param, ac-06.01_odp.01 }} to {{ insert: param, ac-06.01_odp.05 }}.", - "links": [ - { - "href": "#ac-6.1_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-6.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-6.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-06(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\nlist of security functions (deployed in hardware, software, and firmware) and security-relevant information for which access must be explicitly authorized\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-6.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-06(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for defining least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "ac-6.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-06(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing least privilege functions" - } - ] - } - ] - }, - { - "id": "ac-6.2", - "class": "SP800-53-enhancement", - "title": "Non-privileged Access for Nonsecurity Functions", - "params": [ - { - "id": "ac-06.02_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ac-6.2_prm_1" - }, - { - "name": "label", - "value": "AC-06(02)_ODP", - "class": "sp800-53a" - } - ], - "label": "security functions or security-relevant information", - "constraints": [ - { - "description": "all security functions" - } - ], - "guidelines": [ - { - "prose": "security functions or security-relevant information, the access to which requires users to use non-privileged accounts to access non-security functions, are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AC-06(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-6(2)" - }, - { - "name": "label", - "value": "AC-06(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-06.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-6", - "rel": "required" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-6.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Require that users of system accounts (or roles) with access to {{ insert: param, ac-06.02_odp }} use non-privileged accounts or roles, when accessing nonsecurity functions." - }, - { - "id": "ac-6.2_gdn", - "name": "guidance", - "prose": "Requiring the use of non-privileged accounts when accessing nonsecurity functions limits exposure when operating from within privileged accounts or roles. The inclusion of roles addresses situations where organizations implement access control policies, such as role-based access control, and where a change of role provides the same degree of assurance in the change of access authorizations for the user and the processes acting on behalf of the user as would be provided by a change between a privileged and non-privileged account." - }, - { - "id": "ac-6.2_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "AC-6 (2) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ac-6.2_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Examples of security functions include but are not limited to: establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters, system programming, system and security administration, other privileged functions." - } - ] - }, - { - "id": "ac-6.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-06(02)", - "class": "sp800-53a" - } - ], - "prose": "users of system accounts (or roles) with access to {{ insert: param, ac-06.02_odp }} are required to use non-privileged accounts or roles when accessing non-security functions.", - "links": [ - { - "href": "#ac-6.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-6.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-06(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\nlist of system-generated security functions or security-relevant information assigned to system accounts or roles\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-6.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-06(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for defining least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "ac-6.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-06(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing least privilege functions" - } - ] - } - ] - }, - { - "id": "ac-6.3", - "class": "SP800-53-enhancement", - "title": "Network Access to Privileged Commands", - "params": [ - { - "id": "ac-06.03_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ac-6.3_prm_1" - }, - { - "name": "label", - "value": "AC-06(03)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "privileged commands", - "constraints": [ - { - "description": "all privileged commands" - } - ], - "guidelines": [ - { - "prose": "privileged commands to which network access is to be authorized only for compelling operational needs are defined;" - } - ] - }, - { - "id": "ac-06.03_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ac-6.3_prm_2" - }, - { - "name": "label", - "value": "AC-06(03)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "compelling operational needs", - "guidelines": [ - { - "prose": "compelling operational needs necessitating network access to privileged commands are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AC-06(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-6(3)" - }, - { - "name": "label", - "value": "AC-06(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-06.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-6", - "rel": "required" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-6.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Authorize network access to {{ insert: param, ac-06.03_odp.01 }} only for {{ insert: param, ac-06.03_odp.02 }} and document the rationale for such access in the security plan for the system." - }, - { - "id": "ac-6.3_gdn", - "name": "guidance", - "prose": "Network access is any access across a network connection in lieu of local access (i.e., user being physically present at the device)." - }, - { - "id": "ac-6.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-06(03)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-6.3_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-06(03)[01]", - "class": "sp800-53a" - } - ], - "prose": "network access to {{ insert: param, ac-06.03_odp.01 }} is authorized only for {{ insert: param, ac-06.03_odp.02 }};", - "links": [ - { - "href": "#ac-6.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-6.3_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-06(03)[02]", - "class": "sp800-53a" - } - ], - "prose": "the rationale for authorizing network access to privileged commands is documented in the security plan for the system.", - "links": [ - { - "href": "#ac-6.3_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-6.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-6.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-06(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nlist of operational needs for authorizing network access to privileged commands\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-6.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-06(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for defining least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ac-6.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-06(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing least privilege functions" - } - ] - } - ] - }, - { - "id": "ac-6.5", - "class": "SP800-53-enhancement", - "title": "Privileged Accounts", - "params": [ - { - "id": "ac-06.05_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ac-6.5_prm_1" - }, - { - "name": "label", - "value": "AC-06(05)_ODP", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to which privileged accounts on the system are to be restricted is/are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AC-06(05)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-6(5)" - }, - { - "name": "label", - "value": "AC-06(05)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-06.05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-6", - "rel": "required" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ma-3", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-6.5_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Restrict privileged accounts on the system to {{ insert: param, ac-06.05_odp }}." - }, - { - "id": "ac-6.5_gdn", - "name": "guidance", - "prose": "Privileged accounts, including super user accounts, are typically described as system administrator for various types of commercial off-the-shelf operating systems. Restricting privileged accounts to specific personnel or roles prevents day-to-day users from accessing privileged information or privileged functions. Organizations may differentiate in the application of restricting privileged accounts between allowed privileges for local accounts and for domain accounts provided that they retain the ability to control system configurations for key parameters and as otherwise necessary to sufficiently mitigate risk." - }, - { - "id": "ac-6.5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-06(05)", - "class": "sp800-53a" - } - ], - "prose": "privileged accounts on the system are restricted to {{ insert: param, ac-06.05_odp }}.", - "links": [ - { - "href": "#ac-6.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-6.5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-06(05)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\nlist of system-generated privileged accounts\n\nlist of system administration personnel\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-6.5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-06(05)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for defining least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "ac-6.5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-06(05)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing least privilege functions" - } - ] - } - ] - }, - { - "id": "ac-6.7", - "class": "SP800-53-enhancement", - "title": "Review of User Privileges", - "params": [ - { - "id": "ac-06.07_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ac-6.7_prm_1" - }, - { - "name": "label", - "value": "AC-06(07)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at a minimum, annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to review the privileges assigned to roles or classes of users is defined;" - } - ] - }, - { - "id": "ac-06.07_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ac-6.7_prm_2" - }, - { - "name": "alt-label", - "value": "roles or classes of users", - "class": "sp800-53" - }, - { - "name": "label", - "value": "AC-06(07)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "roles and classes", - "constraints": [ - { - "description": "all users with privileges" - } - ], - "guidelines": [ - { - "prose": "roles or classes of users to which privileges are assigned are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AC-06(07)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-6(7)" - }, - { - "name": "label", - "value": "AC-06(07)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-06.07" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-6", - "rel": "required" - }, - { - "href": "#ca-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-6.7_smt", - "name": "statement", - "parts": [ - { - "id": "ac-6.7_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Review {{ insert: param, ac-06.07_odp.01 }} the privileges assigned to {{ insert: param, ac-06.07_odp.02 }} to validate the need for such privileges; and" - }, - { - "id": "ac-6.7_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Reassign or remove privileges, if necessary, to correctly reflect organizational mission and business needs." - } - ] - }, - { - "id": "ac-6.7_gdn", - "name": "guidance", - "prose": "The need for certain assigned user privileges may change over time to reflect changes in organizational mission and business functions, environments of operation, technologies, or threats. A periodic review of assigned user privileges is necessary to determine if the rationale for assigning such privileges remains valid. If the need cannot be revalidated, organizations take appropriate corrective actions." - }, - { - "id": "ac-6.7_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-06(07)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-6.7_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-06(07)(a)", - "class": "sp800-53a" - } - ], - "prose": "privileges assigned to {{ insert: param, ac-06.07_odp.02 }} are reviewed {{ insert: param, ac-06.07_odp.01 }} to validate the need for such privileges;", - "links": [ - { - "href": "#ac-6.7_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-6.7_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-06(07)(b)", - "class": "sp800-53a" - } - ], - "prose": "privileges are reassigned or removed, if necessary, to correctly reflect organizational mission and business needs.", - "links": [ - { - "href": "#ac-6.7_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-6.7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-6.7_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-06(07)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\nlist of system-generated roles or classes of users and assigned privileges\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nvalidation reviews of privileges assigned to roles or classes or users\n\nrecords of privilege removals or reassignments for roles or classes of users\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-6.7_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-06(07)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for reviewing least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "ac-6.7_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-06(07)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing review of user privileges" - } - ] - } - ] - }, - { - "id": "ac-6.8", - "class": "SP800-53-enhancement", - "title": "Privilege Levels for Code Execution", - "params": [ - { - "id": "ac-06.08_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ac-6.8_prm_1" - }, - { - "name": "label", - "value": "AC-06(08)_ODP", - "class": "sp800-53a" - } - ], - "label": "software", - "constraints": [ - { - "description": "any software except software explicitly documented" - } - ], - "guidelines": [ - { - "prose": "software to be prevented from executing at higher privilege levels than users executing the software is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AC-06(08)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-6(8)" - }, - { - "name": "label", - "value": "AC-06(08)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-06.08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-6", - "rel": "required" - } - ], - "parts": [ - { - "id": "ac-6.8_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Prevent the following software from executing at higher privilege levels than users executing the software: {{ insert: param, ac-06.08_odp }}." - }, - { - "id": "ac-6.8_gdn", - "name": "guidance", - "prose": "In certain situations, software applications or programs need to execute with elevated privileges to perform required functions. However, depending on the software functionality and configuration, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking such applications or programs, those users may indirectly be provided with greater privileges than assigned." - }, - { - "id": "ac-6.8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-06(08)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ac-06.08_odp }} is prevented from executing at higher privilege levels than users executing the software.", - "links": [ - { - "href": "#ac-6.8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-6.8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-06(08)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\nlist of software that should not execute at higher privilege levels than users executing software\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-6.8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-06(08)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for defining least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "ac-6.8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-06(08)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing least privilege functions for software execution" - } - ] - } - ] - }, - { - "id": "ac-6.9", - "class": "SP800-53-enhancement", - "title": "Log Use of Privileged Functions", - "props": [ - { - "name": "label", - "value": "AC-06(09)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-6(9)" - }, - { - "name": "label", - "value": "AC-06(09)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-06.09" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-6", - "rel": "required" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-3", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-6.9_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Log the execution of privileged functions." - }, - { - "id": "ac-6.9_gdn", - "name": "guidance", - "prose": "The misuse of privileged functions, either intentionally or unintentionally by authorized users or by unauthorized external entities that have compromised system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Logging and analyzing the use of privileged functions is one way to detect such misuse and, in doing so, help mitigate the risk from insider threats and the advanced persistent threat." - }, - { - "id": "ac-6.9_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-06(09)", - "class": "sp800-53a" - } - ], - "prose": "the execution of privileged functions is logged.", - "links": [ - { - "href": "#ac-6.9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-6.9_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-06(09)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of privileged functions to be audited\n\nlist of audited events\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-6.9_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-06(09)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for reviewing least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "ac-6.9_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-06(09)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms auditing the execution of least privilege functions" - } - ] - } - ] - }, - { - "id": "ac-6.10", - "class": "SP800-53-enhancement", - "title": "Prohibit Non-privileged Users from Executing Privileged Functions", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AC-06(10)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-6(10)" - }, - { - "name": "label", - "value": "AC-06(10)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-06.10" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-6", - "rel": "required" - } - ], - "parts": [ - { - "id": "ac-6.10_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Prevent non-privileged users from executing privileged functions." - }, - { - "id": "ac-6.10_gdn", - "name": "guidance", - "prose": "Privileged functions include disabling, circumventing, or altering implemented security or privacy controls, establishing system accounts, performing system integrity checks, and administering cryptographic key management activities. Non-privileged users are individuals who do not possess appropriate authorizations. Privileged functions that require protection from non-privileged users include circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms. Preventing non-privileged users from executing privileged functions is enforced by [AC-3](#ac-3)." - }, - { - "id": "ac-6.10_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-06(10)", - "class": "sp800-53a" - } - ], - "prose": "non-privileged users are prevented from executing privileged functions.", - "links": [ - { - "href": "#ac-6.10_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-6.10_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-06(10)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing least privilege\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of privileged functions and associated user account assignments\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-6.10_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-06(10)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for defining least privileges necessary to accomplish specified tasks\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "ac-6.10_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-06(10)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing least privilege functions for non-privileged users" - } - ] - } - ] - } - ] - }, - { - "id": "ac-7", - "class": "SP800-53", - "title": "Unsuccessful Logon Attempts", - "params": [ - { - "id": "ac-07_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ac-7_prm_1" - }, - { - "name": "label", - "value": "AC-07_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "number", - "guidelines": [ - { - "prose": "the number of consecutive invalid logon attempts by a user allowed during a time period is defined;" - } - ] - }, - { - "id": "ac-07_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ac-7_prm_2" - }, - { - "name": "label", - "value": "AC-07_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "time period", - "guidelines": [ - { - "prose": "the time period to which the number of consecutive invalid logon attempts by a user is limited is defined;" - } - ] - }, - { - "id": "ac-07_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ac-7_prm_3" - }, - { - "name": "label", - "value": "AC-07_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "lock the account or node for {{ insert: param, ac-07_odp.04 }}", - "lock the account or node until released by an administrator", - "delay next logon prompt per {{ insert: param, ac-07_odp.05 }}", - "notify system administrator", - "take other {{ insert: param, ac-07_odp.06 }}" - ] - } - }, - { - "id": "ac-07_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "ac-7_prm_4" - }, - { - "name": "label", - "value": "AC-07_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "time period", - "guidelines": [ - { - "prose": "time period for an account or node to be locked is defined (if selected);" - } - ] - }, - { - "id": "ac-07_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "ac-7_prm_5" - }, - { - "name": "label", - "value": "AC-07_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "delay algorithm", - "guidelines": [ - { - "prose": "delay algorithm for the next logon prompt is defined (if selected);" - } - ] - }, - { - "id": "ac-07_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "ac-7_prm_6" - }, - { - "name": "label", - "value": "AC-07_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "action", - "guidelines": [ - { - "prose": "other action to be taken when the maximum number of unsuccessful attempts is exceeded is defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AC-07", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-7" - }, - { - "name": "label", - "value": "AC-07", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-07" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#737513fa-6758-403f-831d-5ddab5e23cb3", - "rel": "reference" - }, - { - "href": "#0f66be67-85e7-4ca6-bd19-39453e9f4394", - "rel": "reference" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ac-9", - "rel": "related" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-7_smt", - "name": "statement", - "parts": [ - { - "id": "ac-7_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Enforce a limit of {{ insert: param, ac-07_odp.01 }} consecutive invalid logon attempts by a user during a {{ insert: param, ac-07_odp.02 }} ; and" - }, - { - "id": "ac-7_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Automatically {{ insert: param, ac-07_odp.03 }} when the maximum number of unsuccessful attempts is exceeded." - } - ] - }, - { - "id": "ac-7_gdn", - "name": "guidance", - "prose": "The need to limit unsuccessful logon attempts and take subsequent action when the maximum number of attempts is exceeded applies regardless of whether the logon occurs via a local or network connection. Due to the potential for denial of service, automatic lockouts initiated by systems are usually temporary and automatically release after a predetermined, organization-defined time period. If a delay algorithm is selected, organizations may employ different algorithms for different components of the system based on the capabilities of those components. Responses to unsuccessful logon attempts may be implemented at the operating system and the application levels. Organization-defined actions that may be taken when the number of allowed consecutive invalid logon attempts is exceeded include prompting the user to answer a secret question in addition to the username and password, invoking a lockdown mode with limited user capabilities (instead of full lockout), allowing users to only logon from specified Internet Protocol (IP) addresses, requiring a CAPTCHA to prevent automated attacks, or applying user profiles such as location, time of day, IP address, device, or Media Access Control (MAC) address. If automatic system lockout or execution of a delay algorithm is not implemented in support of the availability objective, organizations consider a combination of other actions to help prevent brute force attacks. In addition to the above, organizations can prompt users to respond to a secret question before the number of allowed unsuccessful logon attempts is exceeded. Automatically unlocking an account after a specified period of time is generally not permitted. However, exceptions may be required based on operational mission or need." - }, - { - "id": "ac-7_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "AC-7 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ac-7_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "In alignment with NIST SP 800-63B." - } - ] - }, - { - "id": "ac-7_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-07", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-7_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-07a.", - "class": "sp800-53a" - } - ], - "prose": "a limit of {{ insert: param, ac-07_odp.01 }} consecutive invalid logon attempts by a user during {{ insert: param, ac-07_odp.02 }} is enforced;", - "links": [ - { - "href": "#ac-7_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-7_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-07b.", - "class": "sp800-53a" - } - ], - "prose": "automatically {{ insert: param, ac-07_odp.03 }} when the maximum number of unsuccessful attempts is exceeded.", - "links": [ - { - "href": "#ac-7_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-7_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-07-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing unsuccessful logon attempts\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-7_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-07-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem developers\n\nsystem/network administrators" - } - ] - }, - { - "id": "ac-7_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-07-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing access control policy for unsuccessful logon attempts" - } - ] - } - ] - }, - { - "id": "ac-8", - "class": "SP800-53", - "title": "System Use Notification", - "params": [ - { - "id": "ac-08_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ac-8_prm_1" - }, - { - "name": "alt-label", - "value": "system use notification message or banner", - "class": "sp800-53" - }, - { - "name": "label", - "value": "AC-08_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "system use notification", - "constraints": [ - { - "description": "see additional Requirements and Guidance" - } - ], - "guidelines": [ - { - "prose": "system use notification message or banner to be displayed by the system to users before granting access to the system is defined;" - } - ] - }, - { - "id": "ac-08_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ac-8_prm_2" - }, - { - "name": "label", - "value": "AC-08_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "conditions", - "constraints": [ - { - "description": "see additional Requirements and Guidance" - } - ], - "guidelines": [ - { - "prose": "conditions for system use to be displayed by the system before granting further access are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AC-08", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-8" - }, - { - "name": "label", - "value": "AC-08", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-14", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-8_smt", - "name": "statement", - "parts": [ - { - "id": "ac-8_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Display {{ insert: param, ac-08_odp.01 }} to users before granting access to the system that provides privacy and security notices consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines and state that:", - "parts": [ - { - "id": "ac-8_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Users are accessing a U.S. Government system;" - }, - { - "id": "ac-8_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "System usage may be monitored, recorded, and subject to audit;" - }, - { - "id": "ac-8_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Unauthorized use of the system is prohibited and subject to criminal and civil penalties; and" - }, - { - "id": "ac-8_smt.a.4", - "name": "item", - "props": [ - { - "name": "label", - "value": "4." - } - ], - "prose": "Use of the system indicates consent to monitoring and recording;" - } - ] - }, - { - "id": "ac-8_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Retain the notification message or banner on the screen until users acknowledge the usage conditions and take explicit actions to log on to or further access the system; and" - }, - { - "id": "ac-8_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "For publicly accessible systems:", - "parts": [ - { - "id": "ac-8_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Display system use information {{ insert: param, ac-08_odp.02 }} , before granting further access to the publicly accessible system;" - }, - { - "id": "ac-8_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Display references, if any, to monitoring, recording, or auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities; and" - }, - { - "id": "ac-8_smt.c.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Include a description of the authorized uses of the system." - } - ] - } - ] - }, - { - "id": "ac-8_gdn", - "name": "guidance", - "prose": "System use notifications can be implemented using messages or warning banners displayed before individuals log in to systems. System use notifications are used only for access via logon interfaces with human users. Notifications are not required when human interfaces do not exist. Based on an assessment of risk, organizations consider whether or not a secondary system use notification is needed to access applications or other system resources after the initial network logon. Organizations consider system use notification messages or banners displayed in multiple languages based on organizational needs and the demographics of system users. Organizations consult with the privacy office for input regarding privacy messaging and the Office of the General Counsel or organizational equivalent for legal review and approval of warning banner content." - }, - { - "id": "ac-8_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "AC-8 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ac-8_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "The service provider shall determine elements of the cloud environment that require the System Use Notification control. The elements of the cloud environment that require System Use Notification are approved and accepted by the AO." - }, - { - "id": "ac-8_fr_smt.2", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "The service provider shall determine how System Use Notification is going to be verified and provide appropriate periodicity of the check. The System Use Notification verification and periodicity are approved and accepted by the AO." - }, - { - "id": "ac-8_fr_smt.3", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "If not performed as part of a Configuration Baseline check, then there must be documented agreement on how to provide results of verification and the necessary periodicity of the verification by the service provider. The documented agreement on how to provide verification of the results are approved and accepted by the AO." - }, - { - "id": "ac-8_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "If performed as part of a Configuration Baseline check, then the % of items requiring setting that are checked and that pass (or fail) check can be provided." - } - ] - }, - { - "id": "ac-8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-08", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-8_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-08a.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ac-08_odp.01 }} is displayed to users before granting access to the system that provides privacy and security notices consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines;", - "parts": [ - { - "id": "ac-8_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-08a.01", - "class": "sp800-53a" - } - ], - "prose": "the system use notification states that users are accessing a U.S. Government system;", - "links": [ - { - "href": "#ac-8_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-8_obj.a.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-08a.02", - "class": "sp800-53a" - } - ], - "prose": "the system use notification states that system usage may be monitored, recorded, and subject to audit;", - "links": [ - { - "href": "#ac-8_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-8_obj.a.3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-08a.03", - "class": "sp800-53a" - } - ], - "prose": "the system use notification states that unauthorized use of the system is prohibited and subject to criminal and civil penalties; and", - "links": [ - { - "href": "#ac-8_smt.a.3", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-8_obj.a.4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-08a.04", - "class": "sp800-53a" - } - ], - "prose": "the system use notification states that use of the system indicates consent to monitoring and recording;", - "links": [ - { - "href": "#ac-8_smt.a.4", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-8_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-8_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-08b.", - "class": "sp800-53a" - } - ], - "prose": "the notification message or banner is retained on the screen until users acknowledge the usage conditions and take explicit actions to log on to or further access the system;", - "links": [ - { - "href": "#ac-8_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-8_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-08c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-8_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-08c.01", - "class": "sp800-53a" - } - ], - "prose": "for publicly accessible systems, system use information {{ insert: param, ac-08_odp.02 }} is displayed before granting further access to the publicly accessible system;", - "links": [ - { - "href": "#ac-8_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-8_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-08c.02", - "class": "sp800-53a" - } - ], - "prose": "for publicly accessible systems, any references to monitoring, recording, or auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities are displayed;", - "links": [ - { - "href": "#ac-8_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-8_obj.c.3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-08c.03", - "class": "sp800-53a" - } - ], - "prose": "for publicly accessible systems, a description of the authorized uses of the system is included.", - "links": [ - { - "href": "#ac-8_smt.c.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-8_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-08-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprivacy and security policies, procedures addressing system use notification\n\ndocumented approval of system use notification messages or banners\n\nsystem audit records\n\nuser acknowledgements of notification message or banner\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem use notification messages\n\nsystem security plan\n\nprivacy plan\n\nprivacy impact assessment\n\nprivacy assessment report\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-08-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security and privacy responsibilities\n\nlegal counsel\n\nsystem developers" - } - ] - }, - { - "id": "ac-8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-08-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing system use notification" - } - ] - } - ] - }, - { - "id": "ac-10", - "class": "SP800-53", - "title": "Concurrent Session Control", - "params": [ - { - "id": "ac-10_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ac-10_prm_1" - }, - { - "name": "alt-label", - "value": "account and/or account type", - "class": "sp800-53" - }, - { - "name": "label", - "value": "AC-10_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "account and/or account types", - "guidelines": [ - { - "prose": "accounts and/or account types for which to limit the number of concurrent sessions is defined;" - } - ] - }, - { - "id": "ac-10_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ac-10_prm_2" - }, - { - "name": "label", - "value": "AC-10_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "number", - "constraints": [ - { - "description": "three (3) sessions for privileged access and two (2) sessions for non-privileged access" - } - ], - "guidelines": [ - { - "prose": "the number of concurrent sessions to be allowed for each account and/or account type is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AC-10", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-10" - }, - { - "name": "label", - "value": "AC-10", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-10" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#sc-23", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-10_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Limit the number of concurrent sessions for each {{ insert: param, ac-10_odp.01 }} to {{ insert: param, ac-10_odp.02 }}." - }, - { - "id": "ac-10_gdn", - "name": "guidance", - "prose": "Organizations may define the maximum number of concurrent sessions for system accounts globally, by account type, by account, or any combination thereof. For example, organizations may limit the number of concurrent sessions for system administrators or other individuals working in particularly sensitive domains or mission-critical applications. Concurrent session control addresses concurrent sessions for system accounts. It does not, however, address concurrent sessions by single users via multiple system accounts." - }, - { - "id": "ac-10_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-10", - "class": "sp800-53a" - } - ], - "prose": "the number of concurrent sessions for each {{ insert: param, ac-10_odp.01 }} is limited to {{ insert: param, ac-10_odp.02 }}.", - "links": [ - { - "href": "#ac-10_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-10_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-10-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing concurrent session control\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsecurity plan\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-10_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-10-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "ac-10_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-10-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing access control policy for concurrent session control" - } - ] - } - ] - }, - { - "id": "ac-11", - "class": "SP800-53", - "title": "Device Lock", - "params": [ - { - "id": "ac-11_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ac-11_prm_1" - }, - { - "name": "label", - "value": "AC-11_ODP[01]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "initiating a device lock after {{ insert: param, ac-11_odp.02 }} of inactivity", - "requiring the user to initiate a device lock before leaving the system unattended" - ] - } - }, - { - "id": "ac-11_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ac-11_prm_2" - }, - { - "name": "label", - "value": "AC-11_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "fifteen (15) minutes" - } - ], - "guidelines": [ - { - "prose": "time period of inactivity after which a device lock is initiated is defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AC-11", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-11" - }, - { - "name": "label", - "value": "AC-11", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-11" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-7", - "rel": "related" - }, - { - "href": "#ia-11", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-11_smt", - "name": "statement", - "parts": [ - { - "id": "ac-11_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Prevent further access to the system by {{ insert: param, ac-11_odp.01 }} ; and" - }, - { - "id": "ac-11_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Retain the device lock until the user reestablishes access using established identification and authentication procedures." - } - ] - }, - { - "id": "ac-11_gdn", - "name": "guidance", - "prose": "Device locks are temporary actions taken to prevent logical access to organizational systems when users stop work and move away from the immediate vicinity of those systems but do not want to log out because of the temporary nature of their absences. Device locks can be implemented at the operating system level or at the application level. A proximity lock may be used to initiate the device lock (e.g., via a Bluetooth-enabled device or dongle). User-initiated device locking is behavior or policy-based and, as such, requires users to take physical action to initiate the device lock. Device locks are not an acceptable substitute for logging out of systems, such as when organizations require users to log out at the end of workdays." - }, - { - "id": "ac-11_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-11", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-11_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-11a.", - "class": "sp800-53a" - } - ], - "prose": "further access to the system is prevented by {{ insert: param, ac-11_odp.01 }};", - "links": [ - { - "href": "#ac-11_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-11_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-11b.", - "class": "sp800-53a" - } - ], - "prose": "device lock is retained until the user re-establishes access using established identification and authentication procedures.", - "links": [ - { - "href": "#ac-11_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-11_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-11_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-11-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing session lock\n\nprocedures addressing identification and authentication\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsecurity plan\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-11_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-11-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "ac-11_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-11-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing access control policy for session lock" - } - ] - } - ], - "controls": [ - { - "id": "ac-11.1", - "class": "SP800-53-enhancement", - "title": "Pattern-hiding Displays", - "props": [ - { - "name": "label", - "value": "AC-11(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-11(1)" - }, - { - "name": "label", - "value": "AC-11(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-11.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-11", - "rel": "required" - } - ], - "parts": [ - { - "id": "ac-11.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Conceal, via the device lock, information previously visible on the display with a publicly viewable image." - }, - { - "id": "ac-11.1_gdn", - "name": "guidance", - "prose": "The pattern-hiding display can include static or dynamic images, such as patterns used with screen savers, photographic images, solid colors, clock, battery life indicator, or a blank screen with the caveat that controlled unclassified information is not displayed." - }, - { - "id": "ac-11.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-11(01)", - "class": "sp800-53a" - } - ], - "prose": "information previously visible on the display is concealed, via device lock, with a publicly viewable image.", - "links": [ - { - "href": "#ac-11.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-11.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-11(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing session lock\n\ndisplay screen with session lock activated\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-11.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-11(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "ac-11.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-11(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System session lock mechanisms" - } - ] - } - ] - } - ] - }, - { - "id": "ac-12", - "class": "SP800-53", - "title": "Session Termination", - "params": [ - { - "id": "ac-12_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ac-12_prm_1" - }, - { - "name": "alt-label", - "value": "conditions or trigger events requiring session disconnect", - "class": "sp800-53" - }, - { - "name": "label", - "value": "AC-12_ODP", - "class": "sp800-53a" - } - ], - "label": "conditions or trigger events", - "guidelines": [ - { - "prose": "conditions or trigger events requiring session disconnect are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AC-12", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-12" - }, - { - "name": "label", - "value": "AC-12", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-12" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#sc-10", - "rel": "related" - }, - { - "href": "#sc-23", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-12_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Automatically terminate a user session after {{ insert: param, ac-12_odp }}." - }, - { - "id": "ac-12_gdn", - "name": "guidance", - "prose": "Session termination addresses the termination of user-initiated logical sessions (in contrast to [SC-10](#sc-10) , which addresses the termination of network connections associated with communications sessions (i.e., network disconnect)). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational system. Such user sessions can be terminated without terminating network sessions. Session termination ends all processes associated with a user’s logical session except for those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated. Conditions or trigger events that require automatic termination of the session include organization-defined periods of user inactivity, targeted responses to certain types of incidents, or time-of-day restrictions on system use." - }, - { - "id": "ac-12_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-12", - "class": "sp800-53a" - } - ], - "prose": "a user session is automatically terminated after {{ insert: param, ac-12_odp }}.", - "links": [ - { - "href": "#ac-12_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-12_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-12-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing session termination\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of conditions or trigger events requiring session disconnect\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-12_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-12-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "ac-12_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-12-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Automated mechanisms implementing user session termination" - } - ] - } - ] - }, - { - "id": "ac-14", - "class": "SP800-53", - "title": "Permitted Actions Without Identification or Authentication", - "params": [ - { - "id": "ac-14_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ac-14_prm_1" - }, - { - "name": "label", - "value": "AC-14_ODP", - "class": "sp800-53a" - } - ], - "label": "user actions", - "guidelines": [ - { - "prose": "user actions that can be performed on the system without identification or authentication are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AC-14", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-14" - }, - { - "name": "label", - "value": "AC-14", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-14" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-8", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-14_smt", - "name": "statement", - "parts": [ - { - "id": "ac-14_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Identify {{ insert: param, ac-14_odp }} that can be performed on the system without identification or authentication consistent with organizational mission and business functions; and" - }, - { - "id": "ac-14_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Document and provide supporting rationale in the security plan for the system, user actions not requiring identification or authentication." - } - ] - }, - { - "id": "ac-14_gdn", - "name": "guidance", - "prose": "Specific user actions may be permitted without identification or authentication if organizations determine that identification and authentication are not required for the specified user actions. Organizations may allow a limited number of user actions without identification or authentication, including when individuals access public websites or other publicly accessible federal systems, when individuals use mobile phones to receive calls, or when facsimiles are received. Organizations identify actions that normally require identification or authentication but may, under certain circumstances, allow identification or authentication mechanisms to be bypassed. Such bypasses may occur, for example, via a software-readable physical switch that commands bypass of the logon functionality and is protected from accidental or unmonitored use. Permitting actions without identification or authentication does not apply to situations where identification and authentication have already occurred and are not repeated but rather to situations where identification and authentication have not yet occurred. Organizations may decide that there are no user actions that can be performed on organizational systems without identification and authentication, and therefore, the value for the assignment operation can be \"none.\"" - }, - { - "id": "ac-14_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-14", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-14_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-14a.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ac-14_odp }} that can be performed on the system without identification or authentication consistent with organizational mission and business functions are identified;", - "links": [ - { - "href": "#ac-14_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-14_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-14b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-14_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-14b.[01]", - "class": "sp800-53a" - } - ], - "prose": "user actions not requiring identification or authentication are documented in the security plan for the system;", - "links": [ - { - "href": "#ac-14_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-14_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-14b.[02]", - "class": "sp800-53a" - } - ], - "prose": "a rationale for user actions not requiring identification or authentication is provided in the security plan for the system.", - "links": [ - { - "href": "#ac-14_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-14_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-14_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-14_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-14-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing permitted actions without identification or authentication\n\nsystem configuration settings and associated documentation\n\nsecurity plan\n\nlist of user actions that can be performed without identification or authentication\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-14_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-14-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "ac-17", - "class": "SP800-53", - "title": "Remote Access", - "props": [ - { - "name": "label", - "value": "AC-17", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-17" - }, - { - "name": "label", - "value": "AC-17", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-17" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#83b9d63b-66b1-467c-9f3b-3a0b108771e9", - "rel": "reference" - }, - { - "href": "#d4d7c760-2907-403b-8b2a-767ca5370ecd", - "rel": "reference" - }, - { - "href": "#6bc4d137-aece-42a8-8081-9ecb1ebe9fb4", - "rel": "reference" - }, - { - "href": "#42e37e51-7cc0-4ffa-81c9-0ac942da7e99", - "rel": "reference" - }, - { - "href": "#d17ebd7a-ffab-499d-bfff-e705bbb01fa6", - "rel": "reference" - }, - { - "href": "#3915a084-b87b-4f02-83d4-c369e746292f", - "rel": "reference" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#ac-20", - "rel": "related" - }, - { - "href": "#ca-3", - "rel": "related" - }, - { - "href": "#cm-10", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#pe-17", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#sc-10", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-17_smt", - "name": "statement", - "parts": [ - { - "id": "ac-17_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Establish and document usage restrictions, configuration/connection requirements, and implementation guidance for each type of remote access allowed; and" - }, - { - "id": "ac-17_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Authorize each type of remote access to the system prior to allowing such connections." - } - ] - }, - { - "id": "ac-17_gdn", - "name": "guidance", - "prose": "Remote access is access to organizational systems (or processes acting on behalf of users) that communicate through external networks such as the Internet. Types of remote access include dial-up, broadband, and wireless. Organizations use encrypted virtual private networks (VPNs) to enhance confidentiality and integrity for remote connections. The use of encrypted VPNs provides sufficient assurance to the organization that it can effectively treat such connections as internal networks if the cryptographic mechanisms used are implemented in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Still, VPN connections traverse external networks, and the encrypted VPN does not enhance the availability of remote connections. VPNs with encrypted tunnels can also affect the ability to adequately monitor network communications traffic for malicious code. Remote access controls apply to systems other than public web servers or systems designed for public access. Authorization of each remote access type addresses authorization prior to allowing remote access without specifying the specific formats for such authorization. While organizations may use information exchange and system connection security agreements to manage remote access connections to other systems, such agreements are addressed as part of [CA-3](#ca-3) . Enforcing access restrictions for remote access is addressed via [AC-3](#ac-3)." - }, - { - "id": "ac-17_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-17", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-17_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-17a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-17_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-17a.[01]", - "class": "sp800-53a" - } - ], - "prose": "usage restrictions are established and documented for each type of remote access allowed;", - "links": [ - { - "href": "#ac-17_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-17_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-17a.[02]", - "class": "sp800-53a" - } - ], - "prose": "configuration/connection requirements are established and documented for each type of remote access allowed;", - "links": [ - { - "href": "#ac-17_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-17_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-17a.[03]", - "class": "sp800-53a" - } - ], - "prose": "implementation guidance is established and documented for each type of remote access allowed;", - "links": [ - { - "href": "#ac-17_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-17_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-17_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-17b.", - "class": "sp800-53a" - } - ], - "prose": "each type of remote access to the system is authorized prior to allowing such connections.", - "links": [ - { - "href": "#ac-17_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-17_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-17_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-17-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing remote access implementation and usage (including restrictions)\n\nconfiguration management plan\n\nsystem configuration settings and associated documentation\n\nremote access authorizations\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-17_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-17-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for managing remote access connections\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ac-17_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-17-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Remote access management capability for the system" - } - ] - } - ], - "controls": [ - { - "id": "ac-17.1", - "class": "SP800-53-enhancement", - "title": "Monitoring and Control", - "props": [ - { - "name": "label", - "value": "AC-17(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-17(1)" - }, - { - "name": "label", - "value": "AC-17(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-17.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-17", - "rel": "required" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-14", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-17.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Employ automated mechanisms to monitor and control remote access methods." - }, - { - "id": "ac-17.1_gdn", - "name": "guidance", - "prose": "Monitoring and control of remote access methods allows organizations to detect attacks and help ensure compliance with remote access policies by auditing the connection activities of remote users on a variety of system components, including servers, notebook computers, workstations, smart phones, and tablets. Audit logging for remote access is enforced by [AU-2](#au-2) . Audit events are defined in [AU-2a](#au-2_smt.a)." - }, - { - "id": "ac-17.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-17(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-17.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-17(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "automated mechanisms are employed to monitor remote access methods;", - "links": [ - { - "href": "#ac-17.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-17.1_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-17(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "automated mechanisms are employed to control remote access methods.", - "links": [ - { - "href": "#ac-17.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-17.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-17.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-17(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing remote access to the system\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem monitoring records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-17.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-17(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "ac-17.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-17(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Automated mechanisms monitoring and controlling remote access methods" - } - ] - } - ] - }, - { - "id": "ac-17.2", - "class": "SP800-53-enhancement", - "title": "Protection of Confidentiality and Integrity Using Encryption", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AC-17(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-17(2)" - }, - { - "name": "label", - "value": "AC-17(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-17.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-17", - "rel": "required" - }, - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-17.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement cryptographic mechanisms to protect the confidentiality and integrity of remote access sessions." - }, - { - "id": "ac-17.2_gdn", - "name": "guidance", - "prose": "Virtual private networks can be used to protect the confidentiality and integrity of remote access sessions. Transport Layer Security (TLS) is an example of a cryptographic protocol that provides end-to-end communications security over networks and is used for Internet communications and online transactions." - }, - { - "id": "ac-17.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-17(02)", - "class": "sp800-53a" - } - ], - "prose": "cryptographic mechanisms are implemented to protect the confidentiality and integrity of remote access sessions.", - "links": [ - { - "href": "#ac-17.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-17.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-17(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing remote access to the system\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\ncryptographic mechanisms and associated configuration documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-17.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-17(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "ac-17.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-17(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Cryptographic mechanisms protecting confidentiality and integrity of remote access sessions" - } - ] - } - ] - }, - { - "id": "ac-17.3", - "class": "SP800-53-enhancement", - "title": "Managed Access Control Points", - "props": [ - { - "name": "label", - "value": "AC-17(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-17(3)" - }, - { - "name": "label", - "value": "AC-17(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-17.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-17", - "rel": "required" - }, - { - "href": "#sc-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-17.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Route remote accesses through authorized and managed network access control points." - }, - { - "id": "ac-17.3_gdn", - "name": "guidance", - "prose": "Organizations consider the Trusted Internet Connections (TIC) initiative [DHS TIC](#4f42ee6e-86cc-403b-a51f-76c2b4f81b54) requirements for external network connections since limiting the number of access control points for remote access reduces attack surfaces." - }, - { - "id": "ac-17.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-17(03)", - "class": "sp800-53a" - } - ], - "prose": "remote accesses are routed through authorized and managed network access control points.", - "links": [ - { - "href": "#ac-17.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-17.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-17(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing remote access to the system\n\nsystem design documentation\n\nlist of all managed network access control points\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-17.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-17(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ac-17.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-17(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms routing all remote accesses through managed network access control points" - } - ] - } - ] - }, - { - "id": "ac-17.4", - "class": "SP800-53-enhancement", - "title": "Privileged Commands and Access", - "params": [ - { - "id": "ac-17.4_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ac-17.04_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ac-17.04_odp.02" - } - ], - "label": "organization-defined needs" - }, - { - "id": "ac-17.04_odp.01", - "props": [ - { - "name": "label", - "value": "AC-17(04)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "needs requiring remote access", - "guidelines": [ - { - "prose": "needs requiring execution of privileged commands via remote access are defined;" - } - ] - }, - { - "id": "ac-17.04_odp.02", - "props": [ - { - "name": "label", - "value": "AC-17(04)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "needs requiring remote access", - "guidelines": [ - { - "prose": "needs requiring access to security-relevant information via remote access are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AC-17(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-17(4)" - }, - { - "name": "label", - "value": "AC-17(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-17.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-17", - "rel": "required" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-17.4_smt", - "name": "statement", - "parts": [ - { - "id": "ac-17.4_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Authorize the execution of privileged commands and access to security-relevant information via remote access only in a format that provides assessable evidence and for the following needs: {{ insert: param, ac-17.4_prm_1 }} ; and" - }, - { - "id": "ac-17.4_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Document the rationale for remote access in the security plan for the system." - } - ] - }, - { - "id": "ac-17.4_gdn", - "name": "guidance", - "prose": "Remote access to systems represents a significant potential vulnerability that can be exploited by adversaries. As such, restricting the execution of privileged commands and access to security-relevant information via remote access reduces the exposure of the organization and the susceptibility to threats by adversaries to the remote access capability." - }, - { - "id": "ac-17.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-17(04)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-17.4_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-17(04)(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-17.4_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-17(04)(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the execution of privileged commands via remote access is authorized only in a format that provides assessable evidence;", - "links": [ - { - "href": "#ac-17.4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-17.4_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-17(04)(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "access to security-relevant information via remote access is authorized only in a format that provides assessable evidence;", - "links": [ - { - "href": "#ac-17.4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-17.4_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-17(04)(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the execution of privileged commands via remote access is authorized only for the following needs: {{ insert: param, ac-17.04_odp.01 }};", - "links": [ - { - "href": "#ac-17.4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-17.4_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-17(04)(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "access to security-relevant information via remote access is authorized only for the following needs: {{ insert: param, ac-17.04_odp.02 }};", - "links": [ - { - "href": "#ac-17.4_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-17.4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-17.4_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-17(04)(b)", - "class": "sp800-53a" - } - ], - "prose": "the rationale for remote access is documented in the security plan for the system.", - "links": [ - { - "href": "#ac-17.4_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-17.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-17.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-17(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing remote access to the system\n\nsystem configuration settings and associated documentation\n\nsecurity plan\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-17.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-17(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ac-17.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-17(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing remote access management" - } - ] - } - ] - } - ] - }, - { - "id": "ac-18", - "class": "SP800-53", - "title": "Wireless Access", - "props": [ - { - "name": "label", - "value": "AC-18", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-18" - }, - { - "name": "label", - "value": "AC-18", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-18" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#25e3e57b-dc2f-4934-af9b-050b020c6f0e", - "rel": "reference" - }, - { - "href": "#03fb73bc-1b12-4182-bd96-e5719254ea61", - "rel": "reference" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#ca-9", - "rel": "related" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-40", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-43", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-18_smt", - "name": "statement", - "parts": [ - { - "id": "ac-18_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Establish configuration requirements, connection requirements, and implementation guidance for each type of wireless access; and" - }, - { - "id": "ac-18_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Authorize each type of wireless access to the system prior to allowing such connections." - } - ] - }, - { - "id": "ac-18_gdn", - "name": "guidance", - "prose": "Wireless technologies include microwave, packet radio (ultra-high frequency or very high frequency), 802.11x, and Bluetooth. Wireless networks use authentication protocols that provide authenticator protection and mutual authentication." - }, - { - "id": "ac-18_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-18", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-18_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-18a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-18_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-18a.[01]", - "class": "sp800-53a" - } - ], - "prose": "configuration requirements are established for each type of wireless access;", - "links": [ - { - "href": "#ac-18_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-18_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-18a.[02]", - "class": "sp800-53a" - } - ], - "prose": "connection requirements are established for each type of wireless access;", - "links": [ - { - "href": "#ac-18_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-18_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-18a.[03]", - "class": "sp800-53a" - } - ], - "prose": "implementation guidance is established for each type of wireless access;", - "links": [ - { - "href": "#ac-18_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-18_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-18_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-18b.", - "class": "sp800-53a" - } - ], - "prose": "each type of wireless access to the system is authorized prior to allowing such connections.", - "links": [ - { - "href": "#ac-18_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-18_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-18_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-18-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing wireless access implementation and usage (including restrictions)\n\nconfiguration management plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nwireless access authorizations\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-18_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-18-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for managing wireless access connections\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ac-18_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-18-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Wireless access management capability for the system" - } - ] - } - ], - "controls": [ - { - "id": "ac-18.1", - "class": "SP800-53-enhancement", - "title": "Authentication and Encryption", - "params": [ - { - "id": "ac-18.01_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ac-18.1_prm_1" - }, - { - "name": "label", - "value": "AC-18(01)_ODP", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "users", - "devices" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "AC-18(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-18(1)" - }, - { - "name": "label", - "value": "AC-18(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-18.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-18", - "rel": "required" - }, - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-18.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Protect wireless access to the system using authentication of {{ insert: param, ac-18.01_odp }} and encryption." - }, - { - "id": "ac-18.1_gdn", - "name": "guidance", - "prose": "Wireless networking capabilities represent a significant potential vulnerability that can be exploited by adversaries. To protect systems with wireless access points, strong authentication of users and devices along with strong encryption can reduce susceptibility to threats by adversaries involving wireless technologies." - }, - { - "id": "ac-18.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-18(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-18.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-18(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "wireless access to the system is protected using authentication of {{ insert: param, ac-18.01_odp }};", - "links": [ - { - "href": "#ac-18.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-18.1_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-18(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "wireless access to the system is protected using encryption.", - "links": [ - { - "href": "#ac-18.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-18.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-18.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-18(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing wireless implementation and usage (including restrictions)\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-18.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-18(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "ac-18.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-18(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing wireless access protections to the system" - } - ] - } - ] - }, - { - "id": "ac-18.3", - "class": "SP800-53-enhancement", - "title": "Disable Wireless Networking", - "props": [ - { - "name": "label", - "value": "AC-18(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-18(3)" - }, - { - "name": "label", - "value": "AC-18(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-18.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-18", - "rel": "required" - } - ], - "parts": [ - { - "id": "ac-18.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Disable, when not intended for use, wireless networking capabilities embedded within system components prior to issuance and deployment." - }, - { - "id": "ac-18.3_gdn", - "name": "guidance", - "prose": "Wireless networking capabilities that are embedded within system components represent a significant potential vulnerability that can be exploited by adversaries. Disabling wireless capabilities when not needed for essential organizational missions or functions can reduce susceptibility to threats by adversaries involving wireless technologies." - }, - { - "id": "ac-18.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-18(03)", - "class": "sp800-53a" - } - ], - "prose": "when not intended for use, wireless networking capabilities embedded within system components are disabled prior to issuance and deployment.", - "links": [ - { - "href": "#ac-18.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-18.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-18(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing wireless implementation and usage (including restrictions)\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-18.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-18(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ac-18.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-18(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms managing the disabling of wireless networking capabilities internally embedded within system components" - } - ] - } - ] - }, - { - "id": "ac-18.4", - "class": "SP800-53-enhancement", - "title": "Restrict Configurations by Users", - "props": [ - { - "name": "label", - "value": "AC-18(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-18(4)" - }, - { - "name": "label", - "value": "AC-18(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-18.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-18", - "rel": "required" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-15", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-18.4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Identify and explicitly authorize users allowed to independently configure wireless networking capabilities." - }, - { - "id": "ac-18.4_gdn", - "name": "guidance", - "prose": "Organizational authorizations to allow selected users to configure wireless networking capabilities are enforced, in part, by the access enforcement mechanisms employed within organizational systems." - }, - { - "id": "ac-18.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-18(04)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-18.4_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-18(04)[01]", - "class": "sp800-53a" - } - ], - "prose": "users allowed to independently configure wireless networking capabilities are identified;", - "links": [ - { - "href": "#ac-18.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-18.4_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-18(04)[02]", - "class": "sp800-53a" - } - ], - "prose": "users allowed to independently configure wireless networking capabilities are explicitly authorized.", - "links": [ - { - "href": "#ac-18.4_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-18.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-18.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-18(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing wireless implementation and usage (including restrictions)\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-18.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-18(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ac-18.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-18(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms authorizing independent user configuration of wireless networking capabilities" - } - ] - } - ] - }, - { - "id": "ac-18.5", - "class": "SP800-53-enhancement", - "title": "Antennas and Transmission Power Levels", - "props": [ - { - "name": "label", - "value": "AC-18(05)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-18(5)" - }, - { - "name": "label", - "value": "AC-18(05)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-18.05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-18", - "rel": "required" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pe-19", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-18.5_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Select radio antennas and calibrate transmission power levels to reduce the probability that signals from wireless access points can be received outside of organization-controlled boundaries." - }, - { - "id": "ac-18.5_gdn", - "name": "guidance", - "prose": "Actions that may be taken to limit unauthorized use of wireless communications outside of organization-controlled boundaries include reducing the power of wireless transmissions so that the transmissions are less likely to emit a signal that can be captured outside of the physical perimeters of the organization, employing measures such as emissions security to control wireless emanations, and using directional or beamforming antennas that reduce the likelihood that unintended receivers will be able to intercept signals. Prior to taking such mitigating actions, organizations can conduct periodic wireless surveys to understand the radio frequency profile of organizational systems as well as other systems that may be operating in the area." - }, - { - "id": "ac-18.5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-18(05)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-18.5_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-18(05)[01]", - "class": "sp800-53a" - } - ], - "prose": "radio antennas are selected to reduce the probability that signals from wireless access points can be received outside of organization-controlled boundaries;", - "links": [ - { - "href": "#ac-18.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-18.5_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-18(05)[02]", - "class": "sp800-53a" - } - ], - "prose": "transmission power levels are calibrated to reduce the probability that signals from wireless access points can be received outside of organization-controlled boundaries.", - "links": [ - { - "href": "#ac-18.5_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-18.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-18.5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-18(05)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing wireless implementation and usage (including restrictions)\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-18.5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-18(05)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ac-18.5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-18(05)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Calibration of transmission power levels for wireless access\n\nradio antenna signals for wireless access\n\nwireless access reception outside of organization-controlled boundaries" - } - ] - } - ] - } - ] - }, - { - "id": "ac-19", - "class": "SP800-53", - "title": "Access Control for Mobile Devices", - "props": [ - { - "name": "label", - "value": "AC-19", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-19" - }, - { - "name": "label", - "value": "AC-19", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-19" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#42e37e51-7cc0-4ffa-81c9-0ac942da7e99", - "rel": "reference" - }, - { - "href": "#0f66be67-85e7-4ca6-bd19-39453e9f4394", - "rel": "reference" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-7", - "rel": "related" - }, - { - "href": "#ac-11", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-20", - "rel": "related" - }, - { - "href": "#ca-9", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - }, - { - "href": "#mp-7", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-34", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-43", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-19_smt", - "name": "statement", - "parts": [ - { - "id": "ac-19_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Establish configuration requirements, connection requirements, and implementation guidance for organization-controlled mobile devices, to include when such devices are outside of controlled areas; and" - }, - { - "id": "ac-19_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Authorize the connection of mobile devices to organizational systems." - } - ] - }, - { - "id": "ac-19_gdn", - "name": "guidance", - "prose": "A mobile device is a computing device that has a small form factor such that it can easily be carried by a single individual; is designed to operate without a physical connection; possesses local, non-removable or removable data storage; and includes a self-contained power source. Mobile device functionality may also include voice communication capabilities, on-board sensors that allow the device to capture information, and/or built-in features for synchronizing local data with remote locations. Examples include smart phones and tablets. Mobile devices are typically associated with a single individual. The processing, storage, and transmission capability of the mobile device may be comparable to or merely a subset of notebook/desktop systems, depending on the nature and intended purpose of the device. Protection and control of mobile devices is behavior or policy-based and requires users to take physical action to protect and control such devices when outside of controlled areas. Controlled areas are spaces for which organizations provide physical or procedural controls to meet the requirements established for protecting information and systems.\n\nDue to the large variety of mobile devices with different characteristics and capabilities, organizational restrictions may vary for the different classes or types of such devices. Usage restrictions and specific implementation guidance for mobile devices include configuration management, device identification and authentication, implementation of mandatory protective software, scanning devices for malicious code, updating virus protection software, scanning for critical software updates and patches, conducting primary operating system (and possibly other resident software) integrity checks, and disabling unnecessary hardware.\n\nUsage restrictions and authorization to connect may vary among organizational systems. For example, the organization may authorize the connection of mobile devices to its network and impose a set of usage restrictions, while a system owner may withhold authorization for mobile device connection to specific applications or impose additional usage restrictions before allowing mobile device connections to a system. Adequate security for mobile devices goes beyond the requirements specified in [AC-19](#ac-19) . Many safeguards for mobile devices are reflected in other controls. [AC-20](#ac-20) addresses mobile devices that are not organization-controlled." - }, - { - "id": "ac-19_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-19", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-19_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-19a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-19_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-19a.[01]", - "class": "sp800-53a" - } - ], - "prose": "configuration requirements are established for organization-controlled mobile devices, including when such devices are outside of the controlled area;", - "links": [ - { - "href": "#ac-19_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-19_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-19a.[02]", - "class": "sp800-53a" - } - ], - "prose": "connection requirements are established for organization-controlled mobile devices, including when such devices are outside of the controlled area;", - "links": [ - { - "href": "#ac-19_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-19_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-19a.[03]", - "class": "sp800-53a" - } - ], - "prose": "implementation guidance is established for organization-controlled mobile devices, including when such devices are outside of the controlled area;", - "links": [ - { - "href": "#ac-19_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-19_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-19_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-19b.", - "class": "sp800-53a" - } - ], - "prose": "the connection of mobile devices to organizational systems is authorized.", - "links": [ - { - "href": "#ac-19_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-19_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-19_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-19-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing access control for mobile device usage (including restrictions)\n\nconfiguration management plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nauthorizations for mobile device connections to organizational systems\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-19_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-19-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel using mobile devices to access organizational systems\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ac-19_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-19-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control capability for mobile device connections to organizational systems\n\nconfigurations of mobile devices" - } - ] - } - ], - "controls": [ - { - "id": "ac-19.5", - "class": "SP800-53-enhancement", - "title": "Full Device or Container-based Encryption", - "params": [ - { - "id": "ac-19.05_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ac-19.5_prm_1" - }, - { - "name": "label", - "value": "AC-19(05)_ODP[01]", - "class": "sp800-53a" - } - ], - "select": { - "choice": [ - "full-device encryption", - "container-based encryption" - ] - } - }, - { - "id": "ac-19.05_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ac-19.5_prm_2" - }, - { - "name": "label", - "value": "AC-19(05)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "mobile devices", - "guidelines": [ - { - "prose": "mobile devices on which to employ encryption are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AC-19(05)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-19(5)" - }, - { - "name": "label", - "value": "AC-19(05)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-19.05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-19", - "rel": "required" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#sc-28", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-19.5_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Employ {{ insert: param, ac-19.05_odp.01 }} to protect the confidentiality and integrity of information on {{ insert: param, ac-19.05_odp.02 }}." - }, - { - "id": "ac-19.5_gdn", - "name": "guidance", - "prose": "Container-based encryption provides a more fine-grained approach to data and information encryption on mobile devices, including encrypting selected data structures such as files, records, or fields." - }, - { - "id": "ac-19.5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-19(05)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ac-19.05_odp.01 }} is employed to protect the confidentiality and integrity of information on {{ insert: param, ac-19.05_odp.02 }}.", - "links": [ - { - "href": "#ac-19.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-19.5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-19(05)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing access control for mobile devices\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nencryption mechanisms and associated configuration documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-19.5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-19(05)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with access control responsibilities for mobile devices\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ac-19.5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-19(05)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Encryption mechanisms protecting confidentiality and integrity of information on mobile devices" - } - ] - } - ] - } - ] - }, - { - "id": "ac-20", - "class": "SP800-53", - "title": "Use of External Systems", - "params": [ - { - "id": "ac-20_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ac-20_prm_1" - }, - { - "name": "label", - "value": "AC-20_ODP[01]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "establish {{ insert: param, ac-20_odp.02 }}", - "identify {{ insert: param, ac-20_odp.03 }}" - ] - } - }, - { - "id": "ac-20_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ac-20_prm_2" - }, - { - "name": "label", - "value": "AC-20_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "terms and conditions", - "guidelines": [ - { - "prose": "terms and conditions consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems are defined (if selected);" - } - ] - }, - { - "id": "ac-20_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ac-20_prm_3" - }, - { - "name": "alt-label", - "value": "controls asserted to be implemented on external systems", - "class": "sp800-53" - }, - { - "name": "label", - "value": "AC-20_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "controls asserted", - "guidelines": [ - { - "prose": "controls asserted to be implemented on external systems consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems are defined (if selected);" - } - ] - }, - { - "id": "ac-20_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "ac-20_prm_4" - }, - { - "name": "alt-label", - "value": "organizationally-defined types of external systems", - "class": "sp800-53" - }, - { - "name": "label", - "value": "AC-20_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "prohibited types of external systems", - "guidelines": [ - { - "prose": "types of external systems prohibited from use are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AC-20", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-20" - }, - { - "name": "label", - "value": "AC-20", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-20" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#628d22a1-6a11-4784-bc59-5cd9497b5445", - "rel": "reference" - }, - { - "href": "#7dbd6d9f-29d6-4d1d-9766-f2d77ff3c849", - "rel": "reference" - }, - { - "href": "#f26af0d0-6d72-4a9d-8ecd-01bc21fd4f0e", - "rel": "reference" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#ca-3", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-20_smt", - "name": "statement", - "parts": [ - { - "id": "ac-20_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "{{ insert: param, ac-20_odp.01 }} , consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to:", - "parts": [ - { - "id": "ac-20_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Access the system from external systems; and" - }, - { - "id": "ac-20_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Process, store, or transmit organization-controlled information using external systems; or" - } - ] - }, - { - "id": "ac-20_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Prohibit the use of {{ insert: param, ac-20_odp.04 }}." - } - ] - }, - { - "id": "ac-20_gdn", - "name": "guidance", - "prose": "External systems are systems that are used by but not part of organizational systems, and for which the organization has no direct control over the implementation of required controls or the assessment of control effectiveness. External systems include personally owned systems, components, or devices; privately owned computing and communications devices in commercial or public facilities; systems owned or controlled by nonfederal organizations; systems managed by contractors; and federal information systems that are not owned by, operated by, or under the direct supervision or authority of the organization. External systems also include systems owned or operated by other components within the same organization and systems within the organization with different authorization boundaries. Organizations have the option to prohibit the use of any type of external system or prohibit the use of specified types of external systems, (e.g., prohibit the use of any external system that is not organizationally owned or prohibit the use of personally-owned systems).\n\nFor some external systems (i.e., systems operated by other organizations), the trust relationships that have been established between those organizations and the originating organization may be such that no explicit terms and conditions are required. Systems within these organizations may not be considered external. These situations occur when, for example, there are pre-existing information exchange agreements (either implicit or explicit) established between organizations or components or when such agreements are specified by applicable laws, executive orders, directives, regulations, policies, or standards. Authorized individuals include organizational personnel, contractors, or other individuals with authorized access to organizational systems and over which organizations have the authority to impose specific rules of behavior regarding system access. Restrictions that organizations impose on authorized individuals need not be uniform, as the restrictions may vary depending on trust relationships between organizations. Therefore, organizations may choose to impose different security restrictions on contractors than on state, local, or tribal governments.\n\nExternal systems used to access public interfaces to organizational systems are outside the scope of [AC-20](#ac-20) . Organizations establish specific terms and conditions for the use of external systems in accordance with organizational security policies and procedures. At a minimum, terms and conditions address the specific types of applications that can be accessed on organizational systems from external systems and the highest security category of information that can be processed, stored, or transmitted on external systems. If the terms and conditions with the owners of the external systems cannot be established, organizations may impose restrictions on organizational personnel using those external systems." - }, - { - "id": "ac-20_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "AC-20 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ac-20_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "The interrelated controls of AC-20, CA-3, and SA-9 should be differentiated as follows:\n\nAC-20 describes system access to and from external systems.\n\nCA-3 describes documentation of an agreement between the respective system owners when data is exchanged between the CSO and an external system.\n\nSA-9 describes the responsibilities of external system owners. These responsibilities would typically be captured in the agreement required by CA-3." - } - ] - }, - { - "id": "ac-20_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-20", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-20_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-20a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-20_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-20a.01", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ac-20_odp.01 }} is/are consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to access the system from external systems (if applicable);", - "links": [ - { - "href": "#ac-20_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-20_obj.a.2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-20a.02", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ac-20_odp.01 }} is/are consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to process, store, or transmit organization-controlled information using external systems (if applicable);", - "links": [ - { - "href": "#ac-20_smt.a.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-20_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-20_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-20b.", - "class": "sp800-53a" - } - ], - "prose": "the use of {{ insert: param, ac-20_odp.04 }} is prohibited (if applicable).", - "links": [ - { - "href": "#ac-20_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-20_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-20_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-20-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing the use of external systems\n\nexternal systems terms and conditions\n\nlist of types of applications accessible from external systems\n\nmaximum security categorization for information processed, stored, or transmitted on external systems\n\nsystem configuration settings and associated documentation\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-20_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-20-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for defining terms and conditions for use of external systems to access organizational systems\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ac-20_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-20-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing terms and conditions on the use of external systems" - } - ] - } - ], - "controls": [ - { - "id": "ac-20.1", - "class": "SP800-53-enhancement", - "title": "Limits on Authorized Use", - "props": [ - { - "name": "label", - "value": "AC-20(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-20(1)" - }, - { - "name": "label", - "value": "AC-20(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-20.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-20", - "rel": "required" - }, - { - "href": "#ca-2", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-20.1_smt", - "name": "statement", - "prose": "Permit authorized individuals to use an external system to access the system or to process, store, or transmit organization-controlled information only after:", - "parts": [ - { - "id": "ac-20.1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Verification of the implementation of controls on the external system as specified in the organization’s security and privacy policies and security and privacy plans; or" - }, - { - "id": "ac-20.1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Retention of approved system connection or processing agreements with the organizational entity hosting the external system." - } - ] - }, - { - "id": "ac-20.1_gdn", - "name": "guidance", - "prose": "Limiting authorized use recognizes circumstances where individuals using external systems may need to access organizational systems. Organizations need assurance that the external systems contain the necessary controls so as not to compromise, damage, or otherwise harm organizational systems. Verification that the required controls have been implemented can be achieved by external, independent assessments, attestations, or other means, depending on the confidence level required by organizations." - }, - { - "id": "ac-20.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-20(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-20.1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-20(01)(a)", - "class": "sp800-53a" - } - ], - "prose": "authorized individuals are permitted to use an external system to access the system or to process, store, or transmit organization-controlled information only after verification of the implementation of controls on the external system as specified in the organization’s security and privacy policies and security and privacy plans (if applicable);", - "links": [ - { - "href": "#ac-20.1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-20.1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-20(01)(b)", - "class": "sp800-53a" - } - ], - "prose": "authorized individuals are permitted to use an external system to access the system or to process, store, or transmit organization-controlled information only after retention of approved system connection or processing agreements with the organizational entity hosting the external system (if applicable).", - "links": [ - { - "href": "#ac-20.1_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-20.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-20.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-20(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing the use of external systems\n\nsystem connection or processing agreements\n\naccount management documents\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-20.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-20(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ac-20.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-20(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing limits on use of external systems" - } - ] - } - ] - }, - { - "id": "ac-20.2", - "class": "SP800-53-enhancement", - "title": "Portable Storage Devices — Restricted Use", - "params": [ - { - "id": "ac-20.02_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ac-20.2_prm_1" - }, - { - "name": "label", - "value": "AC-20(02)_ODP", - "class": "sp800-53a" - } - ], - "label": "restrictions", - "guidelines": [ - { - "prose": "restrictions on the use of organization-controlled portable storage devices by authorized individuals on external systems are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AC-20(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-20(2)" - }, - { - "name": "label", - "value": "AC-20(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-20.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-20", - "rel": "required" - }, - { - "href": "#mp-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-41", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-20.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Restrict the use of organization-controlled portable storage devices by authorized individuals on external systems using {{ insert: param, ac-20.02_odp }}." - }, - { - "id": "ac-20.2_gdn", - "name": "guidance", - "prose": "Limits on the use of organization-controlled portable storage devices in external systems include restrictions on how the devices may be used and under what conditions the devices may be used." - }, - { - "id": "ac-20.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-20(02)", - "class": "sp800-53a" - } - ], - "prose": "the use of organization-controlled portable storage devices by authorized individuals is restricted on external systems using {{ insert: param, ac-20.02_odp }}.", - "links": [ - { - "href": "#ac-20.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-20.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-20(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing the use of external systems\n\nsystem configuration settings and associated documentation\n\nsystem connection or processing agreements\n\naccount management documents\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-20.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-20(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for restricting or prohibiting the use of organization-controlled storage devices on external systems\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ac-20.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-20(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing restrictions on the use of portable storage devices" - } - ] - } - ] - } - ] - }, - { - "id": "ac-21", - "class": "SP800-53", - "title": "Information Sharing", - "params": [ - { - "id": "ac-21_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ac-21_prm_1" - }, - { - "name": "alt-label", - "value": "information sharing circumstances where user discretion is required", - "class": "sp800-53" - }, - { - "name": "label", - "value": "AC-21_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "information-sharing circumstances", - "guidelines": [ - { - "prose": "information-sharing circumstances where user discretion is required to determine whether access authorizations assigned to a sharing partner match the information’s access and use restrictions are defined;" - } - ] - }, - { - "id": "ac-21_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ac-21_prm_2" - }, - { - "name": "alt-label", - "value": "automated mechanisms or manual processes", - "class": "sp800-53" - }, - { - "name": "label", - "value": "AC-21_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms or manual processes that assist users in making information-sharing and collaboration decisions are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AC-21", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-21" - }, - { - "name": "label", - "value": "AC-21", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-21" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#9ef4b43c-42a4-4316-87dc-ffaf528bc05c", - "rel": "reference" - }, - { - "href": "#98d415ca-7281-4064-9931-0c366637e324", - "rel": "reference" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ac-16", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-7", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#sc-15", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-21_smt", - "name": "statement", - "parts": [ - { - "id": "ac-21_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Enable authorized users to determine whether access authorizations assigned to a sharing partner match the information’s access and use restrictions for {{ insert: param, ac-21_odp.01 }} ; and" - }, - { - "id": "ac-21_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Employ {{ insert: param, ac-21_odp.02 }} to assist users in making information sharing and collaboration decisions." - } - ] - }, - { - "id": "ac-21_gdn", - "name": "guidance", - "prose": "Information sharing applies to information that may be restricted in some manner based on some formal or administrative determination. Examples of such information include, contract-sensitive information, classified information related to special access programs or compartments, privileged information, proprietary information, and personally identifiable information. Security and privacy risk assessments as well as applicable laws, regulations, and policies can provide useful inputs to these determinations. Depending on the circumstances, sharing partners may be defined at the individual, group, or organizational level. Information may be defined by content, type, security category, or special access program or compartment. Access restrictions may include non-disclosure agreements (NDA). Information flow techniques and security attributes may be used to provide automated assistance to users making sharing and collaboration decisions." - }, - { - "id": "ac-21_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-21", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-21_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-21a.", - "class": "sp800-53a" - } - ], - "prose": "authorized users are enabled to determine whether access authorizations assigned to a sharing partner match the information’s access and use restrictions for {{ insert: param, ac-21_odp.01 }};", - "links": [ - { - "href": "#ac-21_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-21_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-21b.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ac-21_odp.02 }} are employed to assist users in making information-sharing and collaboration decisions.", - "links": [ - { - "href": "#ac-21_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-21_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-21_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-21-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing user-based collaboration and information sharing (including restrictions)\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of users authorized to make information-sharing/collaboration decisions\n\nlist of information-sharing circumstances requiring user discretion\n\nnon-disclosure agreements\n\nacquisitions/contractual agreements\n\nsystem security plan\n\nprivacy plan\n\nprivacy impact assessment\n\nsecurity and privacy risk assessments\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-21_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-21-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel responsible for information-sharing/collaboration decisions\n\norganizational personnel with responsibility for acquisitions/contractual agreements\n\nsystem/network administrators\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "ac-21_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-21-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Automated mechanisms or manual process implementing access authorizations supporting information-sharing/user collaboration decisions" - } - ] - } - ] - }, - { - "id": "ac-22", - "class": "SP800-53", - "title": "Publicly Accessible Content", - "params": [ - { - "id": "ac-22_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ac-22_prm_1" - }, - { - "name": "label", - "value": "AC-22_ODP", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least quarterly" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to review the content on the publicly accessible system for non-public information is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AC-22", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AC-22" - }, - { - "name": "label", - "value": "AC-22", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ac-22" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#18e71fec-c6fd-475a-925a-5d8495cf8455", - "rel": "reference" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-13", - "rel": "related" - } - ], - "parts": [ - { - "id": "ac-22_smt", - "name": "statement", - "parts": [ - { - "id": "ac-22_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Designate individuals authorized to make information publicly accessible;" - }, - { - "id": "ac-22_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Train authorized individuals to ensure that publicly accessible information does not contain nonpublic information;" - }, - { - "id": "ac-22_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review the proposed content of information prior to posting onto the publicly accessible system to ensure that nonpublic information is not included; and" - }, - { - "id": "ac-22_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Review the content on the publicly accessible system for nonpublic information {{ insert: param, ac-22_odp }} and remove such information, if discovered." - } - ] - }, - { - "id": "ac-22_gdn", - "name": "guidance", - "prose": "In accordance with applicable laws, executive orders, directives, policies, regulations, standards, and guidelines, the public is not authorized to have access to nonpublic information, including information protected under the [PRIVACT](#18e71fec-c6fd-475a-925a-5d8495cf8455) and proprietary information. Publicly accessible content addresses systems that are controlled by the organization and accessible to the public, typically without identification or authentication. Posting information on non-organizational systems (e.g., non-organizational public websites, forums, and social media) is covered by organizational policy. While organizations may have individuals who are responsible for developing and implementing policies about the information that can be made publicly accessible, publicly accessible content addresses the management of the individuals who make such information publicly accessible." - }, - { - "id": "ac-22_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-22", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-22_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-22a.", - "class": "sp800-53a" - } - ], - "prose": "designated individuals are authorized to make information publicly accessible;", - "links": [ - { - "href": "#ac-22_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-22_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-22b.", - "class": "sp800-53a" - } - ], - "prose": "authorized individuals are trained to ensure that publicly accessible information does not contain non-public information;", - "links": [ - { - "href": "#ac-22_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-22_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-22c.", - "class": "sp800-53a" - } - ], - "prose": "the proposed content of information is reviewed prior to posting onto the publicly accessible system to ensure that non-public information is not included;", - "links": [ - { - "href": "#ac-22_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-22_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AC-22d.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ac-22_obj.d-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-22d.[01]", - "class": "sp800-53a" - } - ], - "prose": "the content on the publicly accessible system is reviewed for non-public information {{ insert: param, ac-22_odp }};", - "links": [ - { - "href": "#ac-22_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-22_obj.d-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AC-22d.[02]", - "class": "sp800-53a" - } - ], - "prose": "non-public information is removed from the publicly accessible system, if discovered.", - "links": [ - { - "href": "#ac-22_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-22_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ac-22_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ac-22_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AC-22-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing publicly accessible content\n\nlist of users authorized to post publicly accessible content on organizational systems\n\ntraining materials and/or records\n\nrecords of publicly accessible information reviews\n\nrecords of response to non-public information on public websites\n\nsystem audit logs\n\nsecurity awareness training records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ac-22_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AC-22-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for managing publicly accessible information posted on organizational systems\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ac-22_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AC-22-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing management of publicly accessible content" - } - ] - } - ] - } - ] - }, - { - "id": "at", - "class": "family", - "title": "Awareness and Training", - "controls": [ - { - "id": "at-1", - "class": "SP800-53", - "title": "Policy and Procedures", - "params": [ - { - "id": "at-1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "at-01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "at-01_odp.02" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "at-01_odp.01", - "props": [ - { - "name": "label", - "value": "AT-01_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the awareness and training policy is to be disseminated is/are defined;" - } - ] - }, - { - "id": "at-01_odp.02", - "props": [ - { - "name": "label", - "value": "AT-01_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the awareness and training procedures are to be disseminated is/are defined;" - } - ] - }, - { - "id": "at-01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "at-1_prm_2" - }, - { - "name": "label", - "value": "AT-01_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "organization-level", - "mission/business process-level", - "system-level" - ] - } - }, - { - "id": "at-01_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "at-1_prm_3" - }, - { - "name": "label", - "value": "AT-01_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "official", - "guidelines": [ - { - "prose": "an official to manage the awareness and training policy and procedures is defined;" - } - ] - }, - { - "id": "at-01_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "at-1_prm_4" - }, - { - "name": "label", - "value": "AT-01_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current awareness and training policy is reviewed and updated is defined;" - } - ] - }, - { - "id": "at-01_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "at-1_prm_5" - }, - { - "name": "label", - "value": "AT-01_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that would require the current awareness and training policy to be reviewed and updated are defined;" - } - ] - }, - { - "id": "at-01_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "at-1_prm_6" - }, - { - "name": "label", - "value": "AT-01_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current awareness and training procedures are reviewed and updated is defined;" - } - ] - }, - { - "id": "at-01_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "at-1_prm_7" - }, - { - "name": "label", - "value": "AT-01_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "events", - "constraints": [ - { - "description": "significant changes" - } - ], - "guidelines": [ - { - "prose": "events that would require procedures to be reviewed and updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AT-01", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AT-1" - }, - { - "name": "label", - "value": "AT-01", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "at-01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#c7ac44e8-10db-4b64-b2b9-9e32ec1efed0", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#511f6832-23ca-49a3-8c0f-ce493373cab8", - "rel": "reference" - }, - { - "href": "#4c0ec2ee-a0d6-428a-9043-4504bc3ade6f", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "at-1_smt", - "name": "statement", - "parts": [ - { - "id": "at-1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, a policy that addresses Awareness and Training MUST be associated with AT-1 part a.", - "class": "policy" - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, at least one procedure that addresses Awareness and Training MUST be associated with AT-1 part a.", - "class": "procedure" - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, document, and disseminate to {{ insert: param, at-1_prm_1 }}:", - "parts": [ - { - "id": "at-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, at-01_odp.03 }} awareness and training policy that:", - "parts": [ - { - "id": "at-1_smt.a.1.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "at-1_smt.a.1.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and" - } - ] - }, - { - "id": "at-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the awareness and training policy and the associated awareness and training controls;" - } - ] - }, - { - "id": "at-1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Designate an {{ insert: param, at-01_odp.04 }} to manage the development, documentation, and dissemination of the awareness and training policy and procedures; and" - }, - { - "id": "at-1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the current awareness and training:", - "parts": [ - { - "id": "at-1_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Policy {{ insert: param, at-01_odp.05 }} and following {{ insert: param, at-01_odp.06 }} ; and" - }, - { - "id": "at-1_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures {{ insert: param, at-01_odp.07 }} and following {{ insert: param, at-01_odp.08 }}." - } - ] - } - ] - }, - { - "id": "at-1_gdn", - "name": "guidance", - "prose": "Awareness and training policy and procedures address the controls in the AT family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of awareness and training policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to awareness and training policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure." - }, - { - "id": "at-1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-01a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-01a.[01]", - "class": "sp800-53a" - } - ], - "prose": "an awareness and training policy is developed and documented;", - "links": [ - { - "href": "#at-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-01a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the awareness and training policy is disseminated to {{ insert: param, at-01_odp.01 }};", - "links": [ - { - "href": "#at-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-1_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-01a.[03]", - "class": "sp800-53a" - } - ], - "prose": "awareness and training procedures to facilitate the implementation of the awareness and training policy and associated access controls are developed and documented;", - "links": [ - { - "href": "#at-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-1_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-01a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the awareness and training procedures are disseminated to {{ insert: param, at-01_odp.02 }}.", - "links": [ - { - "href": "#at-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-1_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-01a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-1_obj.a.1.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-01a.01(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-1_obj.a.1.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-01a.01(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, at-01_odp.03 }} awareness and training policy addresses purpose;", - "links": [ - { - "href": "#at-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-1_obj.a.1.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-01a.01(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, at-01_odp.03 }} awareness and training policy addresses scope;", - "links": [ - { - "href": "#at-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-1_obj.a.1.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-01a.01(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, at-01_odp.03 }} awareness and training policy addresses roles;", - "links": [ - { - "href": "#at-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-1_obj.a.1.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-01a.01(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, at-01_odp.03 }} awareness and training policy addresses responsibilities;", - "links": [ - { - "href": "#at-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-1_obj.a.1.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-01a.01(a)[05]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, at-01_odp.03 }} awareness and training policy addresses management commitment;", - "links": [ - { - "href": "#at-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-1_obj.a.1.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-01a.01(a)[06]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, at-01_odp.03 }} awareness and training policy addresses coordination among organizational entities;", - "links": [ - { - "href": "#at-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-1_obj.a.1.a-7", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-01a.01(a)[07]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, at-01_odp.03 }} awareness and training policy addresses compliance; and", - "links": [ - { - "href": "#at-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-1_obj.a.1.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-01a.01(b)", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, at-01_odp.03 }} awareness and training policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines; and", - "links": [ - { - "href": "#at-1_smt.a.1.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-1_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-01b.", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, at-01_odp.04 }} is designated to manage the development, documentation, and dissemination of the awareness and training policy and procedures;", - "links": [ - { - "href": "#at-1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-01c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-1_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-01c.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-1_obj.c.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-01c.01[01]", - "class": "sp800-53a" - } - ], - "prose": "the current awareness and training policy is reviewed and updated {{ insert: param, at-01_odp.05 }};", - "links": [ - { - "href": "#at-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-1_obj.c.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-01c.01[02]", - "class": "sp800-53a" - } - ], - "prose": "the current awareness and training policy is reviewed and updated following {{ insert: param, at-01_odp.06 }};", - "links": [ - { - "href": "#at-1_smt.c.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-1_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-01c.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-1_obj.c.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-01c.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the current awareness and training procedures are reviewed and updated {{ insert: param, at-01_odp.07 }};", - "links": [ - { - "href": "#at-1_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-1_obj.c.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-01c.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the current awareness and training procedures are reviewed and updated following {{ insert: param, at-01_odp.08 }}.", - "links": [ - { - "href": "#at-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-1_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AT-01-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System security plan\n\nprivacy plan\n\nawareness and training policy and procedures\n\nother relevant documents or records" - } - ] - }, - { - "id": "at-1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AT-01-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with awareness and training responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - }, - { - "id": "at-2", - "class": "SP800-53", - "title": "Literacy Training and Awareness", - "params": [ - { - "id": "at-2_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "at-02_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "at-02_odp.02" - } - ], - "label": "organization-defined frequency" - }, - { - "id": "at-2_prm_2", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "at-02_odp.03" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "at-02_odp.04" - } - ], - "label": "organization-defined events" - }, - { - "id": "at-02_odp.01", - "props": [ - { - "name": "label", - "value": "AT-02_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to provide security literacy training to system users (including managers, senior executives, and contractors) after initial training is defined;" - } - ] - }, - { - "id": "at-02_odp.02", - "props": [ - { - "name": "label", - "value": "AT-02_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to provide privacy literacy training to system users (including managers, senior executives, and contractors) after initial training is defined;" - } - ] - }, - { - "id": "at-02_odp.03", - "props": [ - { - "name": "label", - "value": "AT-02_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that require security literacy training for system users are defined;" - } - ] - }, - { - "id": "at-02_odp.04", - "props": [ - { - "name": "label", - "value": "AT-02_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that require privacy literacy training for system users are defined;" - } - ] - }, - { - "id": "at-02_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "at-2_prm_3" - }, - { - "name": "label", - "value": "AT-02_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "awareness techniques", - "guidelines": [ - { - "prose": "techniques to be employed to increase the security and privacy awareness of system users are defined;" - } - ] - }, - { - "id": "at-02_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "at-2_prm_4" - }, - { - "name": "label", - "value": "AT-02_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to update literacy training and awareness content is defined;" - } - ] - }, - { - "id": "at-02_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "at-2_prm_5" - }, - { - "name": "label", - "value": "AT-02_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that would require literacy training and awareness content to be updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AT-02", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AT-2" - }, - { - "name": "label", - "value": "AT-02", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "at-02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#511f6832-23ca-49a3-8c0f-ce493373cab8", - "rel": "reference" - }, - { - "href": "#61ccf0f4-d3e7-42db-9796-ce6cb1c85989", - "rel": "reference" - }, - { - "href": "#276bd50a-7e58-48e5-a405-8c8cb91d7a5f", - "rel": "reference" - }, - { - "href": "#89f2a08d-fc49-46d0-856e-bf974c9b1573", - "rel": "reference" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-22", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#at-4", - "rel": "related" - }, - { - "href": "#cp-3", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ir-2", - "rel": "related" - }, - { - "href": "#ir-7", - "rel": "related" - }, - { - "href": "#ir-9", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-13", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-21", - "rel": "related" - }, - { - "href": "#ps-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-2", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-16", - "rel": "related" - } - ], - "parts": [ - { - "id": "at-2_smt", - "name": "statement", - "parts": [ - { - "id": "at-2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Provide security and privacy literacy training to system users (including managers, senior executives, and contractors):", - "parts": [ - { - "id": "at-2_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "As part of initial training for new users and {{ insert: param, at-2_prm_1 }} thereafter; and" - }, - { - "id": "at-2_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "When required by system changes or following {{ insert: param, at-2_prm_2 }};" - } - ] - }, - { - "id": "at-2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Employ the following techniques to increase the security and privacy awareness of system users {{ insert: param, at-02_odp.05 }};" - }, - { - "id": "at-2_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Update literacy training and awareness content {{ insert: param, at-02_odp.06 }} and following {{ insert: param, at-02_odp.07 }} ; and" - }, - { - "id": "at-2_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Incorporate lessons learned from internal or external security incidents or breaches into literacy training and awareness techniques." - } - ] - }, - { - "id": "at-2_gdn", - "name": "guidance", - "prose": "Organizations provide basic and advanced levels of literacy training to system users, including measures to test the knowledge level of users. Organizations determine the content of literacy training and awareness based on specific organizational requirements, the systems to which personnel have authorized access, and work environments (e.g., telework). The content includes an understanding of the need for security and privacy as well as actions by users to maintain security and personal privacy and to respond to suspected incidents. The content addresses the need for operations security and the handling of personally identifiable information.\n\nAwareness techniques include displaying posters, offering supplies inscribed with security and privacy reminders, displaying logon screen messages, generating email advisories or notices from organizational officials, and conducting awareness events. Literacy training after the initial training described in [AT-2a.1](#at-2_smt.a.1) is conducted at a minimum frequency consistent with applicable laws, directives, regulations, and policies. Subsequent literacy training may be satisfied by one or more short ad hoc sessions and include topical information on recent attack schemes, changes to organizational security and privacy policies, revised security and privacy expectations, or a subset of topics from the initial training. Updating literacy training and awareness content on a regular basis helps to ensure that the content remains relevant. Events that may precipitate an update to literacy training and awareness content include, but are not limited to, assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines." - }, - { - "id": "at-2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-02a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-2_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-02a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-2_obj.a.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-02a.01[01]", - "class": "sp800-53a" - } - ], - "prose": "security literacy training is provided to system users (including managers, senior executives, and contractors) as part of initial training for new users;", - "links": [ - { - "href": "#at-2_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-2_obj.a.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-02a.01[02]", - "class": "sp800-53a" - } - ], - "prose": "privacy literacy training is provided to system users (including managers, senior executives, and contractors) as part of initial training for new users;", - "links": [ - { - "href": "#at-2_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-2_obj.a.1-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-02a.01[03]", - "class": "sp800-53a" - } - ], - "prose": "security literacy training is provided to system users (including managers, senior executives, and contractors) {{ insert: param, at-02_odp.01 }} thereafter;", - "links": [ - { - "href": "#at-2_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-2_obj.a.1-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-02a.01[04]", - "class": "sp800-53a" - } - ], - "prose": "privacy literacy training is provided to system users (including managers, senior executives, and contractors) {{ insert: param, at-02_odp.02 }} thereafter;", - "links": [ - { - "href": "#at-2_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-2_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-2_obj.a.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-02a.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-2_obj.a.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-02a.02[01]", - "class": "sp800-53a" - } - ], - "prose": "security literacy training is provided to system users (including managers, senior executives, and contractors) when required by system changes or following {{ insert: param, at-02_odp.03 }};", - "links": [ - { - "href": "#at-2_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-2_obj.a.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-02a.02[02]", - "class": "sp800-53a" - } - ], - "prose": "privacy literacy training is provided to system users (including managers, senior executives, and contractors) when required by system changes or following {{ insert: param, at-02_odp.04 }};", - "links": [ - { - "href": "#at-2_smt.a.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-2_smt.a.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-02b.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, at-02_odp.05 }} are employed to increase the security and privacy awareness of system users;", - "links": [ - { - "href": "#at-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-2_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-02c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-2_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-02c.[01]", - "class": "sp800-53a" - } - ], - "prose": "literacy training and awareness content is updated {{ insert: param, at-02_odp.06 }};", - "links": [ - { - "href": "#at-2_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-2_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-02c.[02]", - "class": "sp800-53a" - } - ], - "prose": "literacy training and awareness content is updated following {{ insert: param, at-02_odp.07 }};", - "links": [ - { - "href": "#at-2_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-2_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-2_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-02d.", - "class": "sp800-53a" - } - ], - "prose": "lessons learned from internal or external security incidents or breaches are incorporated into literacy training and awareness techniques.", - "links": [ - { - "href": "#at-2_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AT-02-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System security plan\n\nprivacy plan\n\nliteracy training and awareness policy\n\nprocedures addressing literacy training and awareness implementation\n\nappropriate codes of federal regulations\n\nsecurity and privacy literacy training curriculum\n\nsecurity and privacy literacy training materials\n\ntraining records\n\nother relevant documents or records" - } - ] - }, - { - "id": "at-2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AT-02-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for literacy training and awareness\n\norganizational personnel with information security and privacy responsibilities\n\norganizational personnel comprising the general system user community" - } - ] - }, - { - "id": "at-2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AT-02-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms managing information security and privacy literacy training" - } - ] - } - ], - "controls": [ - { - "id": "at-2.2", - "class": "SP800-53-enhancement", - "title": "Insider Threat", - "props": [ - { - "name": "label", - "value": "AT-02(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AT-2(2)" - }, - { - "name": "label", - "value": "AT-02(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "at-02.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#at-2", - "rel": "required" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "at-2.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Provide literacy training on recognizing and reporting potential indicators of insider threat." - }, - { - "id": "at-2.2_gdn", - "name": "guidance", - "prose": "Potential indicators and possible precursors of insider threat can include behaviors such as inordinate, long-term job dissatisfaction; attempts to gain access to information not required for job performance; unexplained access to financial resources; bullying or harassment of fellow employees; workplace violence; and other serious violations of policies, procedures, directives, regulations, rules, or practices. Literacy training includes how to communicate the concerns of employees and management regarding potential indicators of insider threat through channels established by the organization and in accordance with established policies and procedures. Organizations may consider tailoring insider threat awareness topics to the role. For example, training for managers may be focused on changes in the behavior of team members, while training for employees may be focused on more general observations." - }, - { - "id": "at-2.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-02(02)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-2.2_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-02(02)[01]", - "class": "sp800-53a" - } - ], - "prose": "literacy training on recognizing potential indicators of insider threat is provided;", - "links": [ - { - "href": "#at-2.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-2.2_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-02(02)[02]", - "class": "sp800-53a" - } - ], - "prose": "literacy training on reporting potential indicators of insider threat is provided.", - "links": [ - { - "href": "#at-2.2_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-2.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-2.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AT-02(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System security plan\n\nprivacy plan\n\nliteracy training and awareness policy\n\nprocedures addressing literacy training and awareness implementation\n\nliteracy training and awareness curriculum\n\nliteracy training and awareness materials\n\nother relevant documents or records" - } - ] - }, - { - "id": "at-2.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AT-02(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel who receive literacy training and awareness\n\norganizational personnel with responsibilities for literacy training and awareness\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - }, - { - "id": "at-2.3", - "class": "SP800-53-enhancement", - "title": "Social Engineering and Mining", - "props": [ - { - "name": "label", - "value": "AT-02(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AT-2(3)" - }, - { - "name": "label", - "value": "AT-02(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "at-02.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#at-2", - "rel": "required" - } - ], - "parts": [ - { - "id": "at-2.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Provide literacy training on recognizing and reporting potential and actual instances of social engineering and social mining." - }, - { - "id": "at-2.3_gdn", - "name": "guidance", - "prose": "Social engineering is an attempt to trick an individual into revealing information or taking an action that can be used to breach, compromise, or otherwise adversely impact a system. Social engineering includes phishing, pretexting, impersonation, baiting, quid pro quo, thread-jacking, social media exploitation, and tailgating. Social mining is an attempt to gather information about the organization that may be used to support future attacks. Literacy training includes information on how to communicate the concerns of employees and management regarding potential and actual instances of social engineering and data mining through organizational channels based on established policies and procedures." - }, - { - "id": "at-2.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-02(03)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-2.3_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-02(03)[01]", - "class": "sp800-53a" - } - ], - "prose": "literacy training on recognizing potential and actual instances of social engineering is provided;", - "links": [ - { - "href": "#at-2.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-2.3_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-02(03)[02]", - "class": "sp800-53a" - } - ], - "prose": "literacy training on reporting potential and actual instances of social engineering is provided;", - "links": [ - { - "href": "#at-2.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-2.3_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-02(03)[03]", - "class": "sp800-53a" - } - ], - "prose": "literacy training on recognizing potential and actual instances of social mining is provided;", - "links": [ - { - "href": "#at-2.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-2.3_obj-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-02(03)[04]", - "class": "sp800-53a" - } - ], - "prose": "literacy training on reporting potential and actual instances of social mining is provided.", - "links": [ - { - "href": "#at-2.3_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-2.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-2.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AT-02(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System security plan\n\nprivacy plan\n\nliteracy training and awareness policy\n\nprocedures addressing literacy training and awareness implementation\n\nliteracy training and awareness curriculum\n\nliteracy training and awareness materials\n\nother relevant documents or records" - } - ] - }, - { - "id": "at-2.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AT-02(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel who receive literacy training and awareness\n\norganizational personnel with responsibilities for literacy training and awareness\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "at-3", - "class": "SP800-53", - "title": "Role-based Training", - "params": [ - { - "id": "at-3_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "at-03_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "at-03_odp.02" - } - ], - "label": "organization-defined roles and responsibilities" - }, - { - "id": "at-03_odp.01", - "props": [ - { - "name": "label", - "value": "AT-03_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "roles and responsibilities", - "guidelines": [ - { - "prose": "roles and responsibilities for role-based security training are defined;" - } - ] - }, - { - "id": "at-03_odp.02", - "props": [ - { - "name": "label", - "value": "AT-03_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "roles and responsibilities", - "guidelines": [ - { - "prose": "roles and responsibilities for role-based privacy training are defined;" - } - ] - }, - { - "id": "at-03_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "at-3_prm_2" - }, - { - "name": "label", - "value": "AT-03_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to provide role-based security and privacy training to assigned personnel after initial training is defined;" - } - ] - }, - { - "id": "at-03_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "at-3_prm_3" - }, - { - "name": "label", - "value": "AT-03_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to update role-based training content is defined;" - } - ] - }, - { - "id": "at-03_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "at-3_prm_4" - }, - { - "name": "label", - "value": "AT-03_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that require role-based training content to be updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AT-03", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AT-3" - }, - { - "name": "label", - "value": "AT-03", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "at-03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#511f6832-23ca-49a3-8c0f-ce493373cab8", - "rel": "reference" - }, - { - "href": "#276bd50a-7e58-48e5-a405-8c8cb91d7a5f", - "rel": "reference" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-22", - "rel": "related" - }, - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-4", - "rel": "related" - }, - { - "href": "#cp-3", - "rel": "related" - }, - { - "href": "#ir-2", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-7", - "rel": "related" - }, - { - "href": "#ir-9", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-13", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-23", - "rel": "related" - }, - { - "href": "#ps-7", - "rel": "related" - }, - { - "href": "#ps-9", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-11", - "rel": "related" - }, - { - "href": "#sa-16", - "rel": "related" - }, - { - "href": "#sr-5", - "rel": "related" - }, - { - "href": "#sr-6", - "rel": "related" - }, - { - "href": "#sr-11", - "rel": "related" - } - ], - "parts": [ - { - "id": "at-3_smt", - "name": "statement", - "parts": [ - { - "id": "at-3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Provide role-based security and privacy training to personnel with the following roles and responsibilities: {{ insert: param, at-3_prm_1 }}:", - "parts": [ - { - "id": "at-3_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Before authorizing access to the system, information, or performing assigned duties, and {{ insert: param, at-03_odp.03 }} thereafter; and" - }, - { - "id": "at-3_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "When required by system changes;" - } - ] - }, - { - "id": "at-3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Update role-based training content {{ insert: param, at-03_odp.04 }} and following {{ insert: param, at-03_odp.05 }} ; and" - }, - { - "id": "at-3_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Incorporate lessons learned from internal or external security incidents or breaches into role-based training." - } - ] - }, - { - "id": "at-3_gdn", - "name": "guidance", - "prose": "Organizations determine the content of training based on the assigned roles and responsibilities of individuals as well as the security and privacy requirements of organizations and the systems to which personnel have authorized access, including technical training specifically tailored for assigned duties. Roles that may require role-based training include senior leaders or management officials (e.g., head of agency/chief executive officer, chief information officer, senior accountable official for risk management, senior agency information security officer, senior agency official for privacy), system owners; authorizing officials; system security officers; privacy officers; acquisition and procurement officials; enterprise architects; systems engineers; software developers; systems security engineers; privacy engineers; system, network, and database administrators; auditors; personnel conducting configuration management activities; personnel performing verification and validation activities; personnel with access to system-level software; control assessors; personnel with contingency planning and incident response duties; personnel with privacy management responsibilities; and personnel with access to personally identifiable information.\n\nComprehensive role-based training addresses management, operational, and technical roles and responsibilities covering physical, personnel, and technical controls. Role-based training also includes policies, procedures, tools, methods, and artifacts for the security and privacy roles defined. Organizations provide the training necessary for individuals to fulfill their responsibilities related to operations and supply chain risk management within the context of organizational security and privacy programs. Role-based training also applies to contractors who provide services to federal agencies. Types of training include web-based and computer-based training, classroom-style training, and hands-on training (including micro-training). Updating role-based training on a regular basis helps to ensure that the content remains relevant and effective. Events that may precipitate an update to role-based training content include, but are not limited to, assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines." - }, - { - "id": "at-3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-03a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-3_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-03a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-3_obj.a.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-03a.01[01]", - "class": "sp800-53a" - } - ], - "prose": "role-based security training is provided to {{ insert: param, at-03_odp.01 }} before authorizing access to the system, information, or performing assigned duties;", - "links": [ - { - "href": "#at-3_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-3_obj.a.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-03a.01[02]", - "class": "sp800-53a" - } - ], - "prose": "role-based privacy training is provided to {{ insert: param, at-03_odp.02 }} before authorizing access to the system, information, or performing assigned duties;", - "links": [ - { - "href": "#at-3_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-3_obj.a.1-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-03a.01[03]", - "class": "sp800-53a" - } - ], - "prose": "role-based security training is provided to {{ insert: param, at-03_odp.01 }} {{ insert: param, at-03_odp.03 }} thereafter;", - "links": [ - { - "href": "#at-3_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-3_obj.a.1-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-03a.01[04]", - "class": "sp800-53a" - } - ], - "prose": "role-based privacy training is provided to {{ insert: param, at-03_odp.02 }} {{ insert: param, at-03_odp.03 }} thereafter;", - "links": [ - { - "href": "#at-3_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-3_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-3_obj.a.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-03a.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-3_obj.a.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-03a.02[01]", - "class": "sp800-53a" - } - ], - "prose": "role-based security training is provided to personnel with assigned security roles and responsibilities when required by system changes;", - "links": [ - { - "href": "#at-3_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-3_obj.a.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-03a.02[02]", - "class": "sp800-53a" - } - ], - "prose": "role-based privacy training is provided to personnel with assigned security roles and responsibilities when required by system changes;", - "links": [ - { - "href": "#at-3_smt.a.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-3_smt.a.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-03b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-3_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-03b.[01]", - "class": "sp800-53a" - } - ], - "prose": "role-based training content is updated {{ insert: param, at-03_odp.04 }};", - "links": [ - { - "href": "#at-3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-3_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-03b.[02]", - "class": "sp800-53a" - } - ], - "prose": "role-based training content is updated following {{ insert: param, at-03_odp.05 }};", - "links": [ - { - "href": "#at-3_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-3_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-03c.", - "class": "sp800-53a" - } - ], - "prose": "lessons learned from internal or external security incidents or breaches are incorporated into role-based training.", - "links": [ - { - "href": "#at-3_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AT-03-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System security plan\n\nprivacy plan\n\nsecurity and privacy awareness and training policy\n\nprocedures addressing security and privacy training implementation\n\ncodes of federal regulations\n\nsecurity and privacy training curriculum\n\nsecurity and privacy training materials\n\ntraining records\n\nother relevant documents or records" - } - ] - }, - { - "id": "at-3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AT-03-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for role-based security and privacy training\n\norganizational personnel with assigned system security and privacy roles and responsibilities" - } - ] - }, - { - "id": "at-3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AT-03-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms managing role-based security and privacy training" - } - ] - } - ] - }, - { - "id": "at-4", - "class": "SP800-53", - "title": "Training Records", - "params": [ - { - "id": "at-04_odp", - "props": [ - { - "name": "alt-identifier", - "value": "at-4_prm_1" - }, - { - "name": "label", - "value": "AT-04_ODP", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "five (5) years or 5 years after completion of a specific training program" - } - ], - "guidelines": [ - { - "prose": "time period for retaining individual training records is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AT-04", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AT-4" - }, - { - "name": "label", - "value": "AT-04", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "at-04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#cp-3", - "rel": "related" - }, - { - "href": "#ir-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-14", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "at-4_smt", - "name": "statement", - "parts": [ - { - "id": "at-4_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Document and monitor information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training; and" - }, - { - "id": "at-4_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Retain individual training records for {{ insert: param, at-04_odp }}." - } - ] - }, - { - "id": "at-4_gdn", - "name": "guidance", - "prose": "Documentation for specialized training may be maintained by individual supervisors at the discretion of the organization. The National Archives and Records Administration provides guidance on records retention for federal agencies." - }, - { - "id": "at-4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-04", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-4_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-04a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "at-4_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-04a.[01]", - "class": "sp800-53a" - } - ], - "prose": "information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training, are documented;", - "links": [ - { - "href": "#at-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-4_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AT-04a.[02]", - "class": "sp800-53a" - } - ], - "prose": "information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training, are monitored;", - "links": [ - { - "href": "#at-4_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-4_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AT-04b.", - "class": "sp800-53a" - } - ], - "prose": "individual training records are retained for {{ insert: param, at-04_odp }}.", - "links": [ - { - "href": "#at-4_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#at-4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "at-4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AT-04-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Security and privacy awareness and training policy\n\nprocedures addressing security and privacy training records\n\nsecurity and privacy awareness and training records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "at-4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AT-04-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with information security and privacy training record retention responsibilities" - } - ] - }, - { - "id": "at-4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AT-04-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting the management of security and privacy training records" - } - ] - } - ] - } - ] - }, - { - "id": "au", - "class": "family", - "title": "Audit and Accountability", - "controls": [ - { - "id": "au-1", - "class": "SP800-53", - "title": "Policy and Procedures", - "params": [ - { - "id": "au-1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "au-01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "au-01_odp.02" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "au-01_odp.01", - "props": [ - { - "name": "label", - "value": "AU-01_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the audit and accountability policy is to be disseminated is/are defined;" - } - ] - }, - { - "id": "au-01_odp.02", - "props": [ - { - "name": "label", - "value": "AU-01_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the audit and accountability procedures are to be disseminated is/are defined;" - } - ] - }, - { - "id": "au-01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "au-1_prm_2" - }, - { - "name": "label", - "value": "AU-01_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "organization-level", - "mission/business process-level", - "system-level" - ] - } - }, - { - "id": "au-01_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "au-1_prm_3" - }, - { - "name": "label", - "value": "AU-01_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "official", - "guidelines": [ - { - "prose": "an official to manage the audit and accountability policy and procedures is defined;" - } - ] - }, - { - "id": "au-01_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "au-1_prm_4" - }, - { - "name": "label", - "value": "AU-01_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current audit and accountability policy is reviewed and updated is defined;" - } - ] - }, - { - "id": "au-01_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "au-1_prm_5" - }, - { - "name": "label", - "value": "AU-01_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that would require the current audit and accountability policy to be reviewed and updated are defined;" - } - ] - }, - { - "id": "au-01_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "au-1_prm_6" - }, - { - "name": "label", - "value": "AU-01_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current audit and accountability procedures are reviewed and updated is defined;" - } - ] - }, - { - "id": "au-01_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "au-1_prm_7" - }, - { - "name": "label", - "value": "AU-01_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "events", - "constraints": [ - { - "description": "significant changes" - } - ], - "guidelines": [ - { - "prose": "events that would require audit and accountability procedures to be reviewed and updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AU-01", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-1" - }, - { - "name": "label", - "value": "AU-01", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#c7ac44e8-10db-4b64-b2b9-9e32ec1efed0", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#4c0ec2ee-a0d6-428a-9043-4504bc3ade6f", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-1_smt", - "name": "statement", - "parts": [ - { - "id": "au-1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, a policy that addresses Audit and Accountability MUST be associated with AU-1 part a.", - "class": "policy" - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, at least one procedure that addresses Audit and Accountability MUST be associated with AU-1 part a.", - "class": "procedure" - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, document, and disseminate to {{ insert: param, au-1_prm_1 }}:", - "parts": [ - { - "id": "au-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, au-01_odp.03 }} audit and accountability policy that:", - "parts": [ - { - "id": "au-1_smt.a.1.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "au-1_smt.a.1.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and" - } - ] - }, - { - "id": "au-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the audit and accountability policy and the associated audit and accountability controls;" - } - ] - }, - { - "id": "au-1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Designate an {{ insert: param, au-01_odp.04 }} to manage the development, documentation, and dissemination of the audit and accountability policy and procedures; and" - }, - { - "id": "au-1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the current audit and accountability:", - "parts": [ - { - "id": "au-1_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Policy {{ insert: param, au-01_odp.05 }} and following {{ insert: param, au-01_odp.06 }} ; and" - }, - { - "id": "au-1_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures {{ insert: param, au-01_odp.07 }} and following {{ insert: param, au-01_odp.08 }}." - } - ] - } - ] - }, - { - "id": "au-1_gdn", - "name": "guidance", - "prose": "Audit and accountability policy and procedures address the controls in the AU family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of audit and accountability policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to audit and accountability policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure." - }, - { - "id": "au-1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-01a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-01a.[01]", - "class": "sp800-53a" - } - ], - "prose": "an audit and accountability policy is developed and documented;", - "links": [ - { - "href": "#au-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-01a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the audit and accountability policy is disseminated to {{ insert: param, au-01_odp.01 }};", - "links": [ - { - "href": "#au-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-1_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-01a.[03]", - "class": "sp800-53a" - } - ], - "prose": "audit and accountability procedures to facilitate the implementation of the audit and accountability policy and associated audit and accountability controls are developed and documented;", - "links": [ - { - "href": "#au-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-1_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-01a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the audit and accountability procedures are disseminated to {{ insert: param, au-01_odp.02 }};", - "links": [ - { - "href": "#au-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-1_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-01a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-1_obj.a.1.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-01a.01(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-1_obj.a.1.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-01a.01(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, au-01_odp.03 }} of the audit and accountability policy addresses purpose;", - "links": [ - { - "href": "#au-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-1_obj.a.1.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-01a.01(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, au-01_odp.03 }} of the audit and accountability policy addresses scope;", - "links": [ - { - "href": "#au-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-1_obj.a.1.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-01a.01(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, au-01_odp.03 }} of the audit and accountability policy addresses roles;", - "links": [ - { - "href": "#au-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-1_obj.a.1.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-01a.01(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, au-01_odp.03 }} of the audit and accountability policy addresses responsibilities;", - "links": [ - { - "href": "#au-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-1_obj.a.1.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-01a.01(a)[05]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, au-01_odp.03 }} of the audit and accountability policy addresses management commitment;", - "links": [ - { - "href": "#au-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-1_obj.a.1.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-01a.01(a)[06]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, au-01_odp.03 }} of the audit and accountability policy addresses coordination among organizational entities;", - "links": [ - { - "href": "#au-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-1_obj.a.1.a-7", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-01a.01(a)[07]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, au-01_odp.03 }} of the audit and accountability policy addresses compliance;", - "links": [ - { - "href": "#au-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-1_obj.a.1.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-01a.01(b)", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, au-01_odp.03 }} of the audit and accountability policy is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines;", - "links": [ - { - "href": "#au-1_smt.a.1.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-1_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-01b.", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, au-01_odp.04 }} is designated to manage the development, documentation, and dissemination of the audit and accountability policy and procedures;", - "links": [ - { - "href": "#au-1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-01c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-1_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-01c.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-1_obj.c.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-01c.01[01]", - "class": "sp800-53a" - } - ], - "prose": "the current audit and accountability policy is reviewed and updated {{ insert: param, au-01_odp.05 }};", - "links": [ - { - "href": "#au-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-1_obj.c.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-01c.01[02]", - "class": "sp800-53a" - } - ], - "prose": "the current audit and accountability policy is reviewed and updated following {{ insert: param, au-01_odp.06 }};", - "links": [ - { - "href": "#au-1_smt.c.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-1_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-01c.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-1_obj.c.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-01c.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the current audit and accountability procedures are reviewed and updated {{ insert: param, au-01_odp.07 }};", - "links": [ - { - "href": "#au-1_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-1_obj.c.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-01c.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the current audit and accountability procedures are reviewed and updated following {{ insert: param, au-01_odp.08 }}.", - "links": [ - { - "href": "#au-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-1_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-01-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy and procedures\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-01-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - }, - { - "id": "au-2", - "class": "SP800-53", - "title": "Event Logging", - "params": [ - { - "id": "au-2_prm_2", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "au-02_odp.02" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "au-02_odp.03" - } - ], - "label": "organization-defined event types (subset of the event types defined in [AU-2a.](#au-2_smt.a)) along with the frequency of (or situation requiring) logging for each identified event type" - }, - { - "id": "au-02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "au-2_prm_1" - }, - { - "name": "alt-label", - "value": "event types that the system is capable of logging", - "class": "sp800-53" - }, - { - "name": "label", - "value": "AU-02_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "event types", - "constraints": [ - { - "description": "successful and unsuccessful account logon events, account management events, object access, policy change, privilege functions, process tracking, and system events. For Web applications: all administrator activity, authentication checks, authorization checks, data deletions, data access, data changes, and permission changes" - } - ], - "guidelines": [ - { - "prose": "the event types that the system is capable of logging in support of the audit function are defined;" - } - ] - }, - { - "id": "au-02_odp.02", - "props": [ - { - "name": "label", - "value": "AU-02_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "event types (subset of AU-02_ODP\\[01\\])", - "constraints": [ - { - "description": "organization-defined subset of the auditable events defined in AU-2a to be audited continually for each identified event." - } - ], - "guidelines": [ - { - "prose": "the event types (subset of AU-02_ODP\\[01\\]) for logging within the system are defined;" - } - ] - }, - { - "id": "au-02_odp.03", - "props": [ - { - "name": "label", - "value": "AU-02_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "frequency or situation", - "constraints": [ - { - "description": "organization-defined subset of the auditable events defined in AU-2a to be audited continually for each identified event." - } - ], - "guidelines": [ - { - "prose": "the frequency or situation requiring logging for each specified event type is defined;" - } - ] - }, - { - "id": "au-02_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "au-2_prm_3" - }, - { - "name": "label", - "value": "AU-02_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "annually and whenever there is a change in the threat environment" - } - ], - "guidelines": [ - { - "prose": "the frequency of event types selected for logging are reviewed and updated;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-02", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-2" - }, - { - "name": "label", - "value": "AU-02", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#5eee45d8-3313-4fdc-8d54-1742092bbdd6", - "rel": "reference" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ac-7", - "rel": "related" - }, - { - "href": "#ac-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ac-16", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#au-3", - "rel": "related" - }, - { - "href": "#au-4", - "rel": "related" - }, - { - "href": "#au-5", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-7", - "rel": "related" - }, - { - "href": "#au-11", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#cm-13", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-21", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ra-8", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-18", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - }, - { - "href": "#si-10", - "rel": "related" - }, - { - "href": "#si-11", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-2_smt", - "name": "statement", - "parts": [ - { - "id": "au-2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Identify the types of events that the system is capable of logging in support of the audit function: {{ insert: param, au-02_odp.01 }};" - }, - { - "id": "au-2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Coordinate the event logging function with other organizational entities requiring audit-related information to guide and inform the selection criteria for events to be logged;" - }, - { - "id": "au-2_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Specify the following event types for logging within the system: {{ insert: param, au-2_prm_2 }};" - }, - { - "id": "au-2_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Provide a rationale for why the event types selected for logging are deemed to be adequate to support after-the-fact investigations of incidents; and" - }, - { - "id": "au-2_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Review and update the event types selected for logging {{ insert: param, au-02_odp.04 }}." - } - ] - }, - { - "id": "au-2_gdn", - "name": "guidance", - "prose": "An event is an observable occurrence in a system. The types of events that require logging are those events that are significant and relevant to the security of systems and the privacy of individuals. Event logging also supports specific monitoring and auditing needs. Event types include password changes, failed logons or failed accesses related to systems, security or privacy attribute changes, administrative privilege usage, PIV credential usage, data action changes, query parameters, or external credential usage. In determining the set of event types that require logging, organizations consider the monitoring and auditing appropriate for each of the controls to be implemented. For completeness, event logging includes all protocols that are operational and supported by the system.\n\nTo balance monitoring and auditing requirements with other system needs, event logging requires identifying the subset of event types that are logged at a given point in time. For example, organizations may determine that systems need the capability to log every file access successful and unsuccessful, but not activate that capability except for specific circumstances due to the potential burden on system performance. The types of events that organizations desire to be logged may change. Reviewing and updating the set of logged events is necessary to help ensure that the events remain relevant and continue to support the needs of the organization. Organizations consider how the types of logging events can reveal information about individuals that may give rise to privacy risk and how best to mitigate such risks. For example, there is the potential to reveal personally identifiable information in the audit trail, especially if the logging event is based on patterns or time of usage.\n\nEvent logging requirements, including the need to log specific event types, may be referenced in other controls and control enhancements. These include [AC-2(4)](#ac-2.4), [AC-3(10)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ac-3.10), [AC-6(9)](#ac-6.9), [AC-17(1)](#ac-17.1), [CM-3f](#cm-3_smt.f), [CM-5(1)](#cm-5.1), [IA-3(3)(b)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ia-3.3_smt.b), [MA-4(1)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ma-4.1), [MP-4(2)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#mp-4.2), [PE-3](#pe-3), [PM-21](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-21), [PT-7](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-7), [RA-8](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ra-8), [SC-7(9)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-7.9), [SC-7(15)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-7.15), [SI-3(8)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#si-3.8), [SI-4(22)](#si-4.22), [SI-7(8)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#si-7.8) , and [SI-10(1)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#si-10.1) . Organizations include event types that are required by applicable laws, executive orders, directives, policies, regulations, standards, and guidelines. Audit records can be generated at various levels, including at the packet level as information traverses the network. Selecting the appropriate level of event logging is an important part of a monitoring and auditing capability and can identify the root causes of problems. When defining event types, organizations consider the logging necessary to cover related event types, such as the steps in distributed, transaction-based processes and the actions that occur in service-oriented architectures." - }, - { - "id": "au-2_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "AU-2 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "au-2_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Coordination between service provider and consumer shall be documented and accepted by the AO." - }, - { - "id": "au-2_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(e) Guidance:" - } - ], - "prose": "Annually or whenever changes in the threat environment are communicated to the service provider by the AO." - } - ] - }, - { - "id": "au-2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-02a.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, au-02_odp.01 }} that the system is capable of logging are identified in support of the audit logging function;", - "links": [ - { - "href": "#au-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-02b.", - "class": "sp800-53a" - } - ], - "prose": "the event logging function is coordinated with other organizational entities requiring audit-related information to guide and inform the selection criteria for events to be logged;", - "links": [ - { - "href": "#au-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-2_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-02c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-2_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-02c.[01]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, au-02_odp.02 }} are specified for logging within the system;", - "links": [ - { - "href": "#au-2_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-2_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-02c.[02]", - "class": "sp800-53a" - } - ], - "prose": "the specified event types are logged within the system {{ insert: param, au-02_odp.03 }};", - "links": [ - { - "href": "#au-2_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-2_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-2_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-02d.", - "class": "sp800-53a" - } - ], - "prose": "a rationale is provided for why the event types selected for logging are deemed to be adequate to support after-the-fact investigations of incidents;", - "links": [ - { - "href": "#au-2_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-2_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-02e.", - "class": "sp800-53a" - } - ], - "prose": "the event types selected for logging are reviewed and updated {{ insert: param, au-02_odp.04 }}.", - "links": [ - { - "href": "#au-2_smt.e", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-02-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nprocedures addressing auditable events\n\nsystem security plan\n\nprivacy plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem auditable events\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-02-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "au-2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-02-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing system auditing" - } - ] - } - ] - }, - { - "id": "au-3", - "class": "SP800-53", - "title": "Content of Audit Records", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-03", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-3" - }, - { - "name": "label", - "value": "AU-03", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#98d415ca-7281-4064-9931-0c366637e324", - "rel": "reference" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-8", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-14", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pl-9", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - }, - { - "href": "#si-11", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-3_smt", - "name": "statement", - "prose": "Ensure that audit records contain information that establishes the following:", - "parts": [ - { - "id": "au-3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "What type of event occurred;" - }, - { - "id": "au-3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "When the event occurred;" - }, - { - "id": "au-3_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Where the event occurred;" - }, - { - "id": "au-3_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Source of the event;" - }, - { - "id": "au-3_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Outcome of the event; and" - }, - { - "id": "au-3_smt.f", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "f." - } - ], - "prose": "Identity of any individuals, subjects, or objects/entities associated with the event." - } - ] - }, - { - "id": "au-3_gdn", - "name": "guidance", - "prose": "Audit record content that may be necessary to support the auditing function includes event descriptions (item a), time stamps (item b), source and destination addresses (item c), user or process identifiers (items d and f), success or fail indications (item e), and filenames involved (items a, c, e, and f) . Event outcomes include indicators of event success or failure and event-specific results, such as the system security and privacy posture after the event occurred. Organizations consider how audit records can reveal information about individuals that may give rise to privacy risks and how best to mitigate such risks. For example, there is the potential to reveal personally identifiable information in the audit trail, especially if the trail records inputs or is based on patterns or time of usage." - }, - { - "id": "au-3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-03a.", - "class": "sp800-53a" - } - ], - "prose": "audit records contain information that establishes what type of event occurred;", - "links": [ - { - "href": "#au-3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-03b.", - "class": "sp800-53a" - } - ], - "prose": "audit records contain information that establishes when the event occurred;", - "links": [ - { - "href": "#au-3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-3_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-03c.", - "class": "sp800-53a" - } - ], - "prose": "audit records contain information that establishes where the event occurred;", - "links": [ - { - "href": "#au-3_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-3_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-03d.", - "class": "sp800-53a" - } - ], - "prose": "audit records contain information that establishes the source of the event;", - "links": [ - { - "href": "#au-3_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-3_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-03e.", - "class": "sp800-53a" - } - ], - "prose": "audit records contain information that establishes the outcome of the event;", - "links": [ - { - "href": "#au-3_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-3_obj.f", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-03f.", - "class": "sp800-53a" - } - ], - "prose": "audit records contain information that establishes the identity of any individuals, subjects, or objects/entities associated with the event.", - "links": [ - { - "href": "#au-3_smt.f", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-03-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nsystem security plan\n\nprivacy plan\n\nprocedures addressing content of audit records\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of organization-defined auditable events\n\nsystem audit records\n\nsystem incident reports\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-03-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "au-3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-03-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing system auditing of auditable events" - } - ] - } - ], - "controls": [ - { - "id": "au-3.1", - "class": "SP800-53-enhancement", - "title": "Additional Audit Information", - "params": [ - { - "id": "au-03.01_odp", - "props": [ - { - "name": "alt-identifier", - "value": "au-3.1_prm_1" - }, - { - "name": "label", - "value": "AU-03(01)_ODP", - "class": "sp800-53a" - } - ], - "label": "additional information", - "constraints": [ - { - "description": "session, connection, transaction, or activity duration; for client-server transactions, the number of bytes received and bytes sent; additional informational messages to diagnose or identify the event; characteristics that describe or identify the object or resource being acted upon; individual identities of group account users; full-text of privileged commands" - } - ], - "guidelines": [ - { - "prose": "additional information to be included in audit records is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-03(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-3(1)" - }, - { - "name": "label", - "value": "AU-03(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-03.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#au-3", - "rel": "required" - } - ], - "parts": [ - { - "id": "au-3.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Generate audit records containing the following additional information: {{ insert: param, au-03.01_odp }}." - }, - { - "id": "au-3.1_gdn", - "name": "guidance", - "prose": "The ability to add information generated in audit records is dependent on system functionality to configure the audit record content. Organizations may consider additional information in audit records including, but not limited to, access control or flow control rules invoked and individual identities of group account users. Organizations may also consider limiting additional audit record information to only information that is explicitly needed for audit requirements. This facilitates the use of audit trails and audit logs by not including information in audit records that could potentially be misleading, make it more difficult to locate information of interest, or increase the risk to individuals' privacy." - }, - { - "id": "au-3.1_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "AU-3 (1) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "au-3.1_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "For client-server transactions, the number of bytes sent and received gives bidirectional transfer information that can be helpful during an investigation or inquiry." - } - ] - }, - { - "id": "au-3.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-03(01)", - "class": "sp800-53a" - } - ], - "prose": "generated audit records contain the following {{ insert: param, au-03.01_odp }}.", - "links": [ - { - "href": "#au-3.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-3.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-03(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nprocedures addressing content of audit records\n\nsystem security plan\n\nprivacy plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of organization-defined auditable events\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-3.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-03(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "au-3.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-03(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "system audit capability" - } - ] - } - ] - } - ] - }, - { - "id": "au-4", - "class": "SP800-53", - "title": "Audit Log Storage Capacity", - "params": [ - { - "id": "au-04_odp", - "props": [ - { - "name": "alt-identifier", - "value": "au-4_prm_1" - }, - { - "name": "label", - "value": "AU-04_ODP", - "class": "sp800-53a" - } - ], - "label": "audit log retention requirements", - "guidelines": [ - { - "prose": "audit log retention requirements are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-04", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-4" - }, - { - "name": "label", - "value": "AU-04", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-5", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-7", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "#au-11", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-14", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Allocate audit log storage capacity to accommodate {{ insert: param, au-04_odp }}." - }, - { - "id": "au-4_gdn", - "name": "guidance", - "prose": "Organizations consider the types of audit logging to be performed and the audit log processing requirements when allocating audit log storage capacity. Allocating sufficient audit log storage capacity reduces the likelihood of such capacity being exceeded and resulting in the potential loss or reduction of audit logging capability." - }, - { - "id": "au-4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-04", - "class": "sp800-53a" - } - ], - "prose": "audit log storage capacity is allocated to accommodate {{ insert: param, au-04_odp }}.", - "links": [ - { - "href": "#au-4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-04-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit storage capacity\n\nsystem security plan\n\nprivacy plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\naudit record storage requirements\n\naudit record storage capability for system components\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-04-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "au-4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-04-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit record storage capacity and related configuration settings" - } - ] - } - ] - }, - { - "id": "au-5", - "class": "SP800-53", - "title": "Response to Audit Logging Process Failures", - "params": [ - { - "id": "au-05_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "au-5_prm_1" - }, - { - "name": "label", - "value": "AU-05_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles receiving audit logging process failure alerts are defined;" - } - ] - }, - { - "id": "au-05_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "au-5_prm_2" - }, - { - "name": "label", - "value": "AU-05_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "time period", - "guidelines": [ - { - "prose": "time period for personnel or roles receiving audit logging process failure alerts is defined;" - } - ] - }, - { - "id": "au-05_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "au-5_prm_3" - }, - { - "name": "label", - "value": "AU-05_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "additional actions", - "constraints": [ - { - "description": "overwrite oldest record" - } - ], - "guidelines": [ - { - "prose": "additional actions to be taken in the event of an audit logging process failure are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-05", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-5" - }, - { - "name": "label", - "value": "AU-05", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-4", - "rel": "related" - }, - { - "href": "#au-7", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "#au-11", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-14", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-5_smt", - "name": "statement", - "parts": [ - { - "id": "au-5_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Alert {{ insert: param, au-05_odp.01 }} within {{ insert: param, au-05_odp.02 }} in the event of an audit logging process failure; and" - }, - { - "id": "au-5_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Take the following additional actions: {{ insert: param, au-05_odp.03 }}." - } - ] - }, - { - "id": "au-5_gdn", - "name": "guidance", - "prose": "Audit logging process failures include software and hardware errors, failures in audit log capturing mechanisms, and reaching or exceeding audit log storage capacity. Organization-defined actions include overwriting oldest audit records, shutting down the system, and stopping the generation of audit records. Organizations may choose to define additional actions for audit logging process failures based on the type of failure, the location of the failure, the severity of the failure, or a combination of such factors. When the audit logging process failure is related to storage, the response is carried out for the audit log storage repository (i.e., the distinct system component where the audit logs are stored), the system on which the audit logs reside, the total audit log storage capacity of the organization (i.e., all audit log storage repositories combined), or all three. Organizations may decide to take no additional actions after alerting designated roles or personnel." - }, - { - "id": "au-5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-05", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-5_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-05a.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, au-05_odp.01 }} are alerted in the event of an audit logging process failure within {{ insert: param, au-05_odp.02 }};", - "links": [ - { - "href": "#au-5_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-5_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-05b.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, au-05_odp.03 }} are taken in the event of an audit logging process failure.", - "links": [ - { - "href": "#au-5_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-05-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nprocedures addressing response to audit processing failures\n\nsystem design documentation\n\nsystem security plan\n\nprivacy plan\n\nsystem configuration settings and associated documentation\n\nlist of personnel to be notified in case of an audit processing failure\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-05-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "au-5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-05-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing system response to audit processing failures" - } - ] - } - ], - "controls": [ - { - "id": "au-5.1", - "class": "SP800-53-enhancement", - "title": "Storage Capacity Warning", - "params": [ - { - "id": "au-05.01_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "au-5.1_prm_1" - }, - { - "name": "label", - "value": "AU-05(01)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel, roles, and/or locations", - "guidelines": [ - { - "prose": "personnel, roles, and/or locations to be warned when allocated audit log storage volume reaches a percentage of repository maximum audit log storage capacity." - } - ] - }, - { - "id": "au-05.01_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "au-5.1_prm_2" - }, - { - "name": "label", - "value": "AU-05(01)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "time period", - "guidelines": [ - { - "prose": "time period for defined personnel, roles, and/or locations to be warned when allocated audit log storage volume reaches a percentage of repository maximum audit log storage capacity is defined;" - } - ] - }, - { - "id": "au-05.01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "au-5.1_prm_3" - }, - { - "name": "label", - "value": "AU-05(01)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "percentage", - "constraints": [ - { - "description": "75%, or one month before expected negative impact" - } - ], - "guidelines": [ - { - "prose": "percentage of repository maximum audit log storage capacity is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-05(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-5(1)" - }, - { - "name": "label", - "value": "AU-05(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-05.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#au-5", - "rel": "required" - } - ], - "parts": [ - { - "id": "au-5.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Provide a warning to {{ insert: param, au-05.01_odp.01 }} within {{ insert: param, au-05.01_odp.02 }} when allocated audit log storage volume reaches {{ insert: param, au-05.01_odp.03 }} of repository maximum audit log storage capacity." - }, - { - "id": "au-5.1_gdn", - "name": "guidance", - "prose": "Organizations may have multiple audit log storage repositories distributed across multiple system components with each repository having different storage volume capacities." - }, - { - "id": "au-5.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-05(01)", - "class": "sp800-53a" - } - ], - "prose": "a warning is provided to {{ insert: param, au-05.01_odp.01 }} within {{ insert: param, au-05.01_odp.02 }} when allocated audit log storage volume reaches {{ insert: param, au-05.01_odp.03 }} of repository maximum audit log storage capacity.", - "links": [ - { - "href": "#au-5.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-5.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-05(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nprocedures addressing response to audit processing failures\n\nsystem design documentation\n\nsystem security plan\n\nprivacy system configuration settings and associated documentation\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-5.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-05(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "au-5.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-05(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing audit storage limit warnings" - } - ] - } - ] - }, - { - "id": "au-5.2", - "class": "SP800-53-enhancement", - "title": "Real-time Alerts", - "params": [ - { - "id": "au-05.02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "au-5.2_prm_1" - }, - { - "name": "label", - "value": "AU-05(02)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "real-time period", - "constraints": [ - { - "description": "real-time" - } - ], - "guidelines": [ - { - "prose": "real-time period requiring alerts when audit failure events (defined in AU-05(02)_ODP\\[03\\]) occur is defined;" - } - ] - }, - { - "id": "au-05.02_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "au-5.2_prm_2" - }, - { - "name": "label", - "value": "AU-05(02)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel, roles, and/or locations", - "constraints": [ - { - "description": "service provider personnel with authority to address failed audit events" - } - ], - "guidelines": [ - { - "prose": "personnel, roles, and/or locations to be alerted in real time when audit failure events (defined in AU-05(02)_ODP\\[03\\]) occur is/are defined;" - } - ] - }, - { - "id": "au-05.02_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "au-5.2_prm_3" - }, - { - "name": "label", - "value": "AU-05(02)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "audit logging failure events requiring real-time alerts", - "constraints": [ - { - "description": "audit failure events requiring real-time alerts, as defined by organization audit policy" - } - ], - "guidelines": [ - { - "prose": "audit logging failure events requiring real-time alerts are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-05(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-5(2)" - }, - { - "name": "label", - "value": "AU-05(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-05.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#au-5", - "rel": "required" - } - ], - "parts": [ - { - "id": "au-5.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Provide an alert within {{ insert: param, au-05.02_odp.01 }} to {{ insert: param, au-05.02_odp.02 }} when the following audit failure events occur: {{ insert: param, au-05.02_odp.03 }}." - }, - { - "id": "au-5.2_gdn", - "name": "guidance", - "prose": "Alerts provide organizations with urgent messages. Real-time alerts provide these messages at information technology speed (i.e., the time from event detection to alert occurs in seconds or less)." - }, - { - "id": "au-5.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-05(02)", - "class": "sp800-53a" - } - ], - "prose": "an alert is provided within {{ insert: param, au-05.02_odp.01 }} to {{ insert: param, au-05.02_odp.02 }} when {{ insert: param, au-05.02_odp.03 }} occur.", - "links": [ - { - "href": "#au-5.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-5.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-05(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nprocedures addressing response to audit processing failures\n\nsystem design documentation\n\nsystem security plan\n\nprivacy plan\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-5.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-05(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - } - ] - } - ] - }, - { - "id": "au-6", - "class": "SP800-53", - "title": "Audit Record Review, Analysis, and Reporting", - "params": [ - { - "id": "au-06_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "au-6_prm_1" - }, - { - "name": "label", - "value": "AU-06_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least weekly" - } - ], - "guidelines": [ - { - "prose": "frequency at which system audit records are reviewed and analyzed is defined;" - } - ] - }, - { - "id": "au-06_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "au-6_prm_2" - }, - { - "name": "label", - "value": "AU-06_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "inappropriate or unusual activity", - "guidelines": [ - { - "prose": "inappropriate or unusual activity is defined;" - } - ] - }, - { - "id": "au-06_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "au-6_prm_3" - }, - { - "name": "label", - "value": "AU-06_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to receive findings from reviews and analyses of system records is/are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-06", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-6" - }, - { - "name": "label", - "value": "AU-06", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-06" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#cfdb1858-c473-46b3-89f9-a700308d0be2", - "rel": "reference" - }, - { - "href": "#10cf2fad-a216-41f9-bb1a-531b7e3119e3", - "rel": "reference" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-5", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ac-7", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#au-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-16", - "rel": "related" - }, - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-10", - "rel": "related" - }, - { - "href": "#cm-11", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "#ir-5", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pe-6", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-6_smt", - "name": "statement", - "parts": [ - { - "id": "au-6_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Review and analyze system audit records {{ insert: param, au-06_odp.01 }} for indications of {{ insert: param, au-06_odp.02 }} and the potential impact of the inappropriate or unusual activity;" - }, - { - "id": "au-6_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Report findings to {{ insert: param, au-06_odp.03 }} ; and" - }, - { - "id": "au-6_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Adjust the level of audit record review, analysis, and reporting within the system when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information." - } - ] - }, - { - "id": "au-6_gdn", - "name": "guidance", - "prose": "Audit record review, analysis, and reporting covers information security- and privacy-related logging performed by organizations, including logging that results from the monitoring of account usage, remote access, wireless connectivity, mobile device connection, configuration settings, system component inventory, use of maintenance tools and non-local maintenance, physical access, temperature and humidity, equipment delivery and removal, communications at system interfaces, and use of mobile code or Voice over Internet Protocol (VoIP). Findings can be reported to organizational entities that include the incident response team, help desk, and security or privacy offices. If organizations are prohibited from reviewing and analyzing audit records or unable to conduct such activities, the review or analysis may be carried out by other organizations granted such authority. The frequency, scope, and/or depth of the audit record review, analysis, and reporting may be adjusted to meet organizational needs based on new information received." - }, - { - "id": "au-6_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "AU-6 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "au-6_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Coordination between service provider and consumer shall be documented and accepted by the AO. In multi-tenant environments, capability and means for providing review, analysis, and reporting to consumer for data pertaining to consumer shall be documented." - } - ] - }, - { - "id": "au-6_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-06", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-6_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-06a.", - "class": "sp800-53a" - } - ], - "prose": "system audit records are reviewed and analyzed {{ insert: param, au-06_odp.01 }} for indications of {{ insert: param, au-06_odp.02 }} and the potential impact of the inappropriate or unusual activity;", - "links": [ - { - "href": "#au-6_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-6_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-06b.", - "class": "sp800-53a" - } - ], - "prose": "findings are reported to {{ insert: param, au-06_odp.03 }};", - "links": [ - { - "href": "#au-6_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-6_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-06c.", - "class": "sp800-53a" - } - ], - "prose": "the level of audit record review, analysis, and reporting within the system is adjusted when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information.", - "links": [ - { - "href": "#au-6_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-6_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-6_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-06-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nsystem security plan\n\nprivacy plan\n\nprocedures addressing audit review, analysis, and reporting\n\nreports of audit findings\n\nrecords of actions taken in response to reviews/analyses of audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-6_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-06-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit review, analysis, and reporting responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ], - "controls": [ - { - "id": "au-6.1", - "class": "SP800-53-enhancement", - "title": "Automated Process Integration", - "params": [ - { - "id": "au-06.01_odp", - "props": [ - { - "name": "alt-identifier", - "value": "au-6.1_prm_1" - }, - { - "name": "label", - "value": "AU-06(01)_ODP", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used for integrating audit record review, analysis, and reporting processes are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-06(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-6(1)" - }, - { - "name": "label", - "value": "AU-06(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-06.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#au-6", - "rel": "required" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-6.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Integrate audit record review, analysis, and reporting processes using {{ insert: param, au-06.01_odp }}." - }, - { - "id": "au-6.1_gdn", - "name": "guidance", - "prose": "Organizational processes that benefit from integrated audit record review, analysis, and reporting include incident response, continuous monitoring, contingency planning, investigation and response to suspicious activities, and Inspector General audits." - }, - { - "id": "au-6.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-06(01)", - "class": "sp800-53a" - } - ], - "prose": "audit record review, analysis, and reporting processes are integrated using {{ insert: param, au-06.01_odp }}.", - "links": [ - { - "href": "#au-6.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-6.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-06(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nsystem security plan\n\nprivacy plan\n\nprocedures addressing audit review, analysis, and reporting\n\nprocedures addressing investigation and response to suspicious activities\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-6.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-06(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit review, analysis, and reporting responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "au-6.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-06(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Automated mechanisms integrating audit review, analysis, and reporting processes" - } - ] - } - ] - }, - { - "id": "au-6.3", - "class": "SP800-53-enhancement", - "title": "Correlate Audit Record Repositories", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-06(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-6(3)" - }, - { - "name": "label", - "value": "AU-06(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-06.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#au-6", - "rel": "required" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-6.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Analyze and correlate audit records across different repositories to gain organization-wide situational awareness." - }, - { - "id": "au-6.3_gdn", - "name": "guidance", - "prose": "Organization-wide situational awareness includes awareness across all three levels of risk management (i.e., organizational level, mission/business process level, and information system level) and supports cross-organization awareness." - }, - { - "id": "au-6.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-06(03)", - "class": "sp800-53a" - } - ], - "prose": "audit records across different repositories are analyzed and correlated to gain organization-wide situational awareness.", - "links": [ - { - "href": "#au-6.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-6.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-06(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nsystem security plan\n\nprivacy plan\n\nprocedures addressing audit review, analysis, and reporting\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records across different repositories\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-6.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-06(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit review, analysis, and reporting responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "au-6.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-06(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting the analysis and correlation of audit records" - } - ] - } - ] - }, - { - "id": "au-6.4", - "class": "SP800-53-enhancement", - "title": "Central Review and Analysis", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-06(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-6(4)" - }, - { - "name": "label", - "value": "AU-06(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-06.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#au-6", - "rel": "required" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-6.4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Provide and implement the capability to centrally review and analyze audit records from multiple components within the system." - }, - { - "id": "au-6.4_gdn", - "name": "guidance", - "prose": "Automated mechanisms for centralized reviews and analyses include Security Information and Event Management products." - }, - { - "id": "au-6.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-06(04)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-6.4_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-06(04)[01]", - "class": "sp800-53a" - } - ], - "prose": "the capability to centrally review and analyze audit records from multiple components within the system is provided;", - "links": [ - { - "href": "#au-6.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-6.4_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-06(04)[02]", - "class": "sp800-53a" - } - ], - "prose": "the capability to centrally review and analyze audit records from multiple components within the system is implemented.", - "links": [ - { - "href": "#au-6.4_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-6.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-6.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-06(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit review, analysis, and reporting\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem security plan\n\nprivacy plan\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-6.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-06(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit review, analysis, and reporting responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "au-6.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-06(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System capability to centralize review and analysis of audit records" - } - ] - } - ] - }, - { - "id": "au-6.5", - "class": "SP800-53-enhancement", - "title": "Integrated Analysis of Audit Records", - "params": [ - { - "id": "au-06.05_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "au-6.5_prm_1" - }, - { - "name": "label", - "value": "AU-06(05)_ODP[01]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "vulnerability scanning information; performance data; information system monitoring information; penetration test data; {{ insert: param, au-06.05_odp.02 }}" - } - ] - }, - { - "id": "au-06.05_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "au-6.5_prm_2" - }, - { - "name": "label", - "value": "AU-06(05)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "data/information collected from other sources", - "guidelines": [ - { - "prose": "data/information collected from other sources to be analyzed is defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-06(05)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-6(5)" - }, - { - "name": "label", - "value": "AU-06(05)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-06.05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#au-6", - "rel": "required" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-6.5_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Integrate analysis of audit records with analysis of {{ insert: param, au-06.05_odp.01 }} to further enhance the ability to identify inappropriate or unusual activity." - }, - { - "id": "au-6.5_gdn", - "name": "guidance", - "prose": "Integrated analysis of audit records does not require vulnerability scanning, the generation of performance data, or system monitoring. Rather, integrated analysis requires that the analysis of information generated by scanning, monitoring, or other data collection activities is integrated with the analysis of audit record information. Security Information and Event Management tools can facilitate audit record aggregation or consolidation from multiple system components as well as audit record correlation and analysis. The use of standardized audit record analysis scripts developed by organizations (with localized script adjustments, as necessary) provides more cost-effective approaches for analyzing audit record information collected. The correlation of audit record information with vulnerability scanning information is important in determining the veracity of vulnerability scans of the system and in correlating attack detection events with scanning results. Correlation with performance data can uncover denial-of-service attacks or other types of attacks that result in the unauthorized use of resources. Correlation with system monitoring information can assist in uncovering attacks and in better relating audit information to operational situations." - }, - { - "id": "au-6.5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-06(05)", - "class": "sp800-53a" - } - ], - "prose": "analysis of audit records is integrated with analysis of {{ insert: param, au-06.05_odp.01 }} to further enhance the ability to identify inappropriate or unusual activity.", - "links": [ - { - "href": "#au-6.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-6.5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-06(05)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nsystem security plan\n\nprivacy plan\n\nprocedures addressing audit review, analysis, and reporting\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nintegrated analysis of audit records, vulnerability scanning information, performance data, network monitoring information, and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-6.5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-06(05)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit review, analysis, and reporting responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "au-6.5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-06(05)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing the capability to integrate analysis of audit records with analysis of data/information sources" - } - ] - } - ] - }, - { - "id": "au-6.6", - "class": "SP800-53-enhancement", - "title": "Correlation with Physical Monitoring", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-06(06)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-6(6)" - }, - { - "name": "label", - "value": "AU-06(06)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-06.06" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#au-6", - "rel": "required" - } - ], - "parts": [ - { - "id": "au-6.6_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Correlate information from audit records with information obtained from monitoring physical access to further enhance the ability to identify suspicious, inappropriate, unusual, or malevolent activity." - }, - { - "id": "au-6.6_gdn", - "name": "guidance", - "prose": "The correlation of physical audit record information and the audit records from systems may assist organizations in identifying suspicious behavior or supporting evidence of such behavior. For example, the correlation of an individual’s identity for logical access to certain systems with the additional physical security information that the individual was present at the facility when the logical access occurred may be useful in investigations." - }, - { - "id": "au-6.6_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "AU-6 (6) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "au-6.6_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Coordination between service provider and consumer shall be documented and accepted by the AO." - } - ] - }, - { - "id": "au-6.6_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-06(06)", - "class": "sp800-53a" - } - ], - "prose": "information from audit records is correlated with information obtained from monitoring physical access to further enhance the ability to identify suspicious, inappropriate, unusual, or malevolent activity.", - "links": [ - { - "href": "#au-6.6_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-6.6_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-06(06)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit review, analysis, and reporting\n\nprocedures addressing physical access monitoring\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\ndocumentation providing evidence of correlated information obtained from audit records and physical access monitoring records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-6.6_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-06(06)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit review, analysis, and reporting responsibilities\n\norganizational personnel with physical access monitoring responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "au-6.6_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-06(06)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing the capability to correlate information from audit records with information from monitoring physical access" - } - ] - } - ] - }, - { - "id": "au-6.7", - "class": "SP800-53-enhancement", - "title": "Permitted Actions", - "params": [ - { - "id": "au-06.07_odp", - "props": [ - { - "name": "alt-identifier", - "value": "au-6.7_prm_1" - }, - { - "name": "label", - "value": "AU-06(07)_ODP", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "information system process; role; user" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-06(07)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-6(7)" - }, - { - "name": "label", - "value": "AU-06(07)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-06.07" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#au-6", - "rel": "required" - } - ], - "parts": [ - { - "id": "au-6.7_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Specify the permitted actions for each {{ insert: param, au-06.07_odp }} associated with the review, analysis, and reporting of audit record information." - }, - { - "id": "au-6.7_gdn", - "name": "guidance", - "prose": "Organizations specify permitted actions for system processes, roles, and users associated with the review, analysis, and reporting of audit records through system account management activities. Specifying permitted actions on audit record information is a way to enforce the principle of least privilege. Permitted actions are enforced by the system and include read, write, execute, append, and delete." - }, - { - "id": "au-6.7_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-06(07)", - "class": "sp800-53a" - } - ], - "prose": "the permitted actions for each {{ insert: param, au-06.07_odp }} associated with the review, analysis, and reporting of audit record information are specified.", - "links": [ - { - "href": "#au-6.7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-6.7_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-06(07)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nprocedures addressing process, role and/or user permitted actions from audit review, analysis, and reporting\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-6.7_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-06(07)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit review, analysis, and reporting responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "au-6.7_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-06(07)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting permitted actions for the review, analysis, and reporting of audit information" - } - ] - } - ] - } - ] - }, - { - "id": "au-7", - "class": "SP800-53", - "title": "Audit Record Reduction and Report Generation", - "props": [ - { - "name": "label", - "value": "AU-07", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-7" - }, - { - "name": "label", - "value": "AU-07", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-07" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-3", - "rel": "related" - }, - { - "href": "#au-4", - "rel": "related" - }, - { - "href": "#au-5", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-16", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-12", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-7_smt", - "name": "statement", - "prose": "Provide and implement an audit record reduction and report generation capability that:", - "parts": [ - { - "id": "au-7_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents; and" - }, - { - "id": "au-7_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Does not alter the original content or time ordering of audit records." - } - ] - }, - { - "id": "au-7_gdn", - "name": "guidance", - "prose": "Audit record reduction is a process that manipulates collected audit log information and organizes it into a summary format that is more meaningful to analysts. Audit record reduction and report generation capabilities do not always emanate from the same system or from the same organizational entities that conduct audit logging activities. The audit record reduction capability includes modern data mining techniques with advanced data filters to identify anomalous behavior in audit records. The report generation capability provided by the system can generate customizable reports. Time ordering of audit records can be an issue if the granularity of the timestamp in the record is insufficient." - }, - { - "id": "au-7_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-07", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-7_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-07a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-7_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-07a.[01]", - "class": "sp800-53a" - } - ], - "prose": "an audit record reduction and report generation capability is provided that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents;", - "links": [ - { - "href": "#au-7_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-7_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-07a.[02]", - "class": "sp800-53a" - } - ], - "prose": "an audit record reduction and report generation capability is implemented that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents;", - "links": [ - { - "href": "#au-7_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-7_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-7_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-07b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-7_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-07b.[01]", - "class": "sp800-53a" - } - ], - "prose": "an audit record reduction and report generation capability is provided that does not alter the original content or time ordering of audit records;", - "links": [ - { - "href": "#au-7_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-7_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-07b.[02]", - "class": "sp800-53a" - } - ], - "prose": "an audit record reduction and report generation capability is implemented that does not alter the original content or time ordering of audit records.", - "links": [ - { - "href": "#au-7_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-7_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-7_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-07-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nsystem security plan\n\nprivacy plan\n\nprocedures addressing audit reduction and report generation\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\naudit reduction, review, analysis, and reporting tools\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-7_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-07-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit reduction and report generation responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "au-7_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-07-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit reduction and report generation capability" - } - ] - } - ], - "controls": [ - { - "id": "au-7.1", - "class": "SP800-53-enhancement", - "title": "Automatic Processing", - "params": [ - { - "id": "au-07.01_odp", - "props": [ - { - "name": "alt-identifier", - "value": "au-7.1_prm_1" - }, - { - "name": "label", - "value": "AU-07(01)_ODP", - "class": "sp800-53a" - } - ], - "label": "fields within audit records", - "guidelines": [ - { - "prose": "fields within audit records that can be processed, sorted, or searched are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AU-07(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-7(1)" - }, - { - "name": "label", - "value": "AU-07(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-07.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#au-7", - "rel": "required" - } - ], - "parts": [ - { - "id": "au-7.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Provide and implement the capability to process, sort, and search audit records for events of interest based on the following content: {{ insert: param, au-07.01_odp }}." - }, - { - "id": "au-7.1_gdn", - "name": "guidance", - "prose": "Events of interest can be identified by the content of audit records, including system resources involved, information objects accessed, identities of individuals, event types, event locations, event dates and times, Internet Protocol addresses involved, or event success or failure. Organizations may define event criteria to any degree of granularity required, such as locations selectable by a general networking location or by specific system component." - }, - { - "id": "au-7.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-07(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-7.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-07(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "the capability to process, sort, and search audit records for events of interest based on {{ insert: param, au-07.01_odp }} are provided;", - "links": [ - { - "href": "#au-7.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-7.1_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-07(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "the capability to process, sort, and search audit records for events of interest based on {{ insert: param, au-07.01_odp }} are implemented.", - "links": [ - { - "href": "#au-7.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-7.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-7.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-07(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nsystem security plan\n\nprivacy plan\n\nprocedures addressing audit reduction and report generation\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\naudit reduction, review, analysis, and reporting tools\n\naudit record criteria (fields) establishing events of interest\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-7.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-07(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit reduction and report generation responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "au-7.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-07(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit reduction and report generation capability" - } - ] - } - ] - } - ] - }, - { - "id": "au-8", - "class": "SP800-53", - "title": "Time Stamps", - "params": [ - { - "id": "au-08_odp", - "props": [ - { - "name": "alt-identifier", - "value": "au-8_prm_1" - }, - { - "name": "label", - "value": "AU-08_ODP", - "class": "sp800-53a" - } - ], - "label": "granularity of time measurement", - "constraints": [ - { - "description": "one second granularity of time measurement" - } - ], - "guidelines": [ - { - "prose": "granularity of time measurement for audit record timestamps is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-08", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-8" - }, - { - "name": "label", - "value": "AU-08", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#au-3", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-14", - "rel": "related" - }, - { - "href": "#sc-45", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-8_smt", - "name": "statement", - "parts": [ - { - "id": "au-8_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Use internal system clocks to generate time stamps for audit records; and" - }, - { - "id": "au-8_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Record time stamps for audit records that meet {{ insert: param, au-08_odp }} and that use Coordinated Universal Time, have a fixed local time offset from Coordinated Universal Time, or that include the local time offset as part of the time stamp." - } - ] - }, - { - "id": "au-8_gdn", - "name": "guidance", - "prose": "Time stamps generated by the system include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. Granularity of time measurements refers to the degree of synchronization between system clocks and reference clocks (e.g., clocks synchronizing within hundreds of milliseconds or tens of milliseconds). Organizations may define different time granularities for different system components. Time service can be critical to other security capabilities such as access control and identification and authentication, depending on the nature of the mechanisms used to support those capabilities." - }, - { - "id": "au-8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-08", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-8_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-08a.", - "class": "sp800-53a" - } - ], - "prose": "internal system clocks are used to generate timestamps for audit records;", - "links": [ - { - "href": "#au-8_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-8_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-08b.", - "class": "sp800-53a" - } - ], - "prose": "timestamps are recorded for audit records that meet {{ insert: param, au-08_odp }} and that use Coordinated Universal Time, have a fixed local time offset from Coordinated Universal Time, or include the local time offset as part of the timestamp.", - "links": [ - { - "href": "#au-8_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-08-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nsystem security plan\n\nprivacy plan\n\nprocedures addressing timestamp generation\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-08-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "au-8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-08-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing timestamp generation" - } - ] - } - ] - }, - { - "id": "au-9", - "class": "SP800-53", - "title": "Protection of Audit Information", - "params": [ - { - "id": "au-09_odp", - "props": [ - { - "name": "alt-identifier", - "value": "au-9_prm_1" - }, - { - "name": "label", - "value": "AU-09_ODP", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to be alerted upon detection of unauthorized access, modification, or deletion of audit information is/are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AU-09", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-9" - }, - { - "name": "label", - "value": "AU-09", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-09" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#678e3d6c-150b-4393-aec5-6e3481eb1e00", - "rel": "reference" - }, - { - "href": "#eea3c092-42ed-4382-a6f4-1adadef01b9d", - "rel": "reference" - }, - { - "href": "#a295ca19-8c75-4b4c-8800-98024732e181", - "rel": "reference" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-11", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-14", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-15", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pe-6", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-9_smt", - "name": "statement", - "parts": [ - { - "id": "au-9_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Protect audit information and audit logging tools from unauthorized access, modification, and deletion; and" - }, - { - "id": "au-9_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Alert {{ insert: param, au-09_odp }} upon detection of unauthorized access, modification, or deletion of audit information." - } - ] - }, - { - "id": "au-9_gdn", - "name": "guidance", - "prose": "Audit information includes all information needed to successfully audit system activity, such as audit records, audit log settings, audit reports, and personally identifiable information. Audit logging tools are those programs and devices used to conduct system audit and logging activities. Protection of audit information focuses on technical protection and limits the ability to access and execute audit logging tools to authorized individuals. Physical protection of audit information is addressed by both media protection controls and physical and environmental protection controls." - }, - { - "id": "au-9_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-09", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-9_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-09a.", - "class": "sp800-53a" - } - ], - "prose": "audit information and audit logging tools are protected from unauthorized access, modification, and deletion;", - "links": [ - { - "href": "#au-9_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-9_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-09b.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, au-09_odp }} are alerted upon detection of unauthorized access, modification, or deletion of audit information.", - "links": [ - { - "href": "#au-9_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-9_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-09-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nsystem security plan\n\nprivacy plan\n\naccess control policy and procedures\n\nprocedures addressing protection of audit information\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\naudit tools\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-9_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-09-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "au-9_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-09-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing audit information protection" - } - ] - } - ], - "controls": [ - { - "id": "au-9.2", - "class": "SP800-53-enhancement", - "title": "Store on Separate Physical Systems or Components", - "params": [ - { - "id": "au-09.02_odp", - "props": [ - { - "name": "alt-identifier", - "value": "au-9.2_prm_1" - }, - { - "name": "label", - "value": "AU-09(02)_ODP", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least weekly" - } - ], - "guidelines": [ - { - "prose": "the frequency of storing audit records in a repository is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AU-09(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-9(2)" - }, - { - "name": "label", - "value": "AU-09(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-09.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#au-9", - "rel": "required" - }, - { - "href": "#au-4", - "rel": "related" - }, - { - "href": "#au-5", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-9.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Store audit records {{ insert: param, au-09.02_odp }} in a repository that is part of a physically different system or system component than the system or component being audited." - }, - { - "id": "au-9.2_gdn", - "name": "guidance", - "prose": "Storing audit records in a repository separate from the audited system or system component helps to ensure that a compromise of the system being audited does not also result in a compromise of the audit records. Storing audit records on separate physical systems or components also preserves the confidentiality and integrity of audit records and facilitates the management of audit records as an organization-wide activity. Storing audit records on separate systems or components applies to initial generation as well as backup or long-term storage of audit records." - }, - { - "id": "au-9.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-09(02)", - "class": "sp800-53a" - } - ], - "prose": "audit records are stored {{ insert: param, au-09.02_odp }} in a repository that is part of a physically different system or system component than the system or component being audited.", - "links": [ - { - "href": "#au-9.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-9.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-09(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nsystem security plan\n\nprivacy plan\n\nprocedures addressing protection of audit information\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem or media storing backups of system audit records\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-9.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-09(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "au-9.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-09(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing the backing up of audit records" - } - ] - } - ] - }, - { - "id": "au-9.3", - "class": "SP800-53-enhancement", - "title": "Cryptographic Protection", - "props": [ - { - "name": "label", - "value": "AU-09(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-9(3)" - }, - { - "name": "label", - "value": "AU-09(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-09.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#au-9", - "rel": "required" - }, - { - "href": "#au-10", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-9.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement cryptographic mechanisms to protect the integrity of audit information and audit tools." - }, - { - "id": "au-9.3_gdn", - "name": "guidance", - "prose": "Cryptographic mechanisms used for protecting the integrity of audit information include signed hash functions using asymmetric cryptography. This enables the distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash." - }, - { - "id": "au-9.3_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "AU-9 (3) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "au-9.3_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Note that this enhancement requires the use of cryptography which must be compliant with Federal requirements and utilize FIPS validated or NSA approved cryptography (see SC-13.)" - } - ] - }, - { - "id": "au-9.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-09(03)", - "class": "sp800-53a" - } - ], - "prose": "cryptographic mechanisms to protect the integrity of audit information and audit tools are implemented.", - "links": [ - { - "href": "#au-9.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-9.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-09(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nsystem security plan\n\nprivacy plan\n\naccess control policy and procedures\n\nprocedures addressing protection of audit information\n\nsystem design documentation\n\nsystem hardware settings\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-9.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-09(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "au-9.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-09(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Cryptographic mechanisms protecting the integrity of audit information and tools" - } - ] - } - ] - }, - { - "id": "au-9.4", - "class": "SP800-53-enhancement", - "title": "Access by Subset of Privileged Users", - "params": [ - { - "id": "au-09.04_odp", - "props": [ - { - "name": "alt-identifier", - "value": "au-9.4_prm_1" - }, - { - "name": "label", - "value": "AU-09(04)_ODP", - "class": "sp800-53a" - } - ], - "label": "subset of privileged users or roles", - "guidelines": [ - { - "prose": "a subset of privileged users or roles authorized to access management of audit logging functionality is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "AU-09(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-9(4)" - }, - { - "name": "label", - "value": "AU-09(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-09.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#au-9", - "rel": "required" - }, - { - "href": "#ac-5", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-9.4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Authorize access to management of audit logging functionality to only {{ insert: param, au-09.04_odp }}." - }, - { - "id": "au-9.4_gdn", - "name": "guidance", - "prose": "Individuals or roles with privileged access to a system and who are also the subject of an audit by that system may affect the reliability of the audit information by inhibiting audit activities or modifying audit records. Requiring privileged access to be further defined between audit-related privileges and other privileges limits the number of users or roles with audit-related privileges." - }, - { - "id": "au-9.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-09(04)", - "class": "sp800-53a" - } - ], - "prose": "access to management of audit logging functionality is authorized only to {{ insert: param, au-09.04_odp }}.", - "links": [ - { - "href": "#au-9.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-9.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-09(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nsystem security plan\n\nprivacy plan\n\naccess control policy and procedures\n\nprocedures addressing protection of audit information\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem-generated list of privileged users with access to management of audit functionality\n\naccess authorizations\n\naccess control list\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-9.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-09(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit and accountability responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "au-9.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-09(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms managing access to audit functionality" - } - ] - } - ] - } - ] - }, - { - "id": "au-10", - "class": "SP800-53", - "title": "Non-repudiation", - "params": [ - { - "id": "au-10_odp", - "props": [ - { - "name": "alt-identifier", - "value": "au-10_prm_1" - }, - { - "name": "alt-label", - "value": "actions to be covered by non-repudiation", - "class": "sp800-53" - }, - { - "name": "label", - "value": "AU-10_ODP", - "class": "sp800-53a" - } - ], - "label": "actions", - "constraints": [ - { - "description": "minimum actions including the addition, modification, deletion, approval, sending, or receiving of data" - } - ], - "guidelines": [ - { - "prose": "actions to be covered by non-repudiation are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-10", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-10" - }, - { - "name": "label", - "value": "AU-10", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-10" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#678e3d6c-150b-4393-aec5-6e3481eb1e00", - "rel": "reference" - }, - { - "href": "#eea3c092-42ed-4382-a6f4-1adadef01b9d", - "rel": "reference" - }, - { - "href": "#7c37a38d-21d7-40d8-bc3d-b5e27eac17e1", - "rel": "reference" - }, - { - "href": "#a295ca19-8c75-4b4c-8800-98024732e181", - "rel": "reference" - }, - { - "href": "#1c71b420-2bd9-4e52-9fc8-390f58b85b59", - "rel": "reference" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-12", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-16", - "rel": "related" - }, - { - "href": "#sc-17", - "rel": "related" - }, - { - "href": "#sc-23", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-10_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Provide irrefutable evidence that an individual (or process acting on behalf of an individual) has performed {{ insert: param, au-10_odp }}." - }, - { - "id": "au-10_gdn", - "name": "guidance", - "prose": "Types of individual actions covered by non-repudiation include creating information, sending and receiving messages, and approving information. Non-repudiation protects against claims by authors of not having authored certain documents, senders of not having transmitted messages, receivers of not having received messages, and signatories of not having signed documents. Non-repudiation services can be used to determine if information originated from an individual or if an individual took specific actions (e.g., sending an email, signing a contract, approving a procurement request, or receiving specific information). Organizations obtain non-repudiation services by employing various techniques or mechanisms, including digital signatures and digital message receipts." - }, - { - "id": "au-10_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-10", - "class": "sp800-53a" - } - ], - "prose": "irrefutable evidence is provided that an individual (or process acting on behalf of an individual) has performed {{ insert: param, au-10_odp }}.", - "links": [ - { - "href": "#au-10_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-10_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-10-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nsystem security plan\n\nprivacy plan\n\nprocedures addressing non-repudiation\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-10_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-10-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "au-10_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-10-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing non-repudiation capability" - } - ] - } - ] - }, - { - "id": "au-11", - "class": "SP800-53", - "title": "Audit Record Retention", - "params": [ - { - "id": "au-11_odp", - "props": [ - { - "name": "alt-identifier", - "value": "au-11_prm_1" - }, - { - "name": "alt-label", - "value": "time period consistent with records retention policy", - "class": "sp800-53" - }, - { - "name": "label", - "value": "AU-11_ODP", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "a time period in compliance with M-21-31" - } - ], - "guidelines": [ - { - "prose": "a time period to retain audit records that is consistent with the records retention policy is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-11", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-11" - }, - { - "name": "label", - "value": "AU-11", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-11" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-4", - "rel": "related" - }, - { - "href": "#au-5", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-14", - "rel": "related" - }, - { - "href": "#mp-6", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-11_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Retain audit records for {{ insert: param, au-11_odp }} to provide support for after-the-fact investigations of incidents and to meet regulatory and organizational information retention requirements." - }, - { - "id": "au-11_gdn", - "name": "guidance", - "prose": "Organizations retain audit records until it is determined that the records are no longer needed for administrative, legal, audit, or other operational purposes. This includes the retention and availability of audit records relative to Freedom of Information Act (FOIA) requests, subpoenas, and law enforcement actions. Organizations develop standard categories of audit records relative to such types of actions and standard response processes for each type of action. The National Archives and Records Administration (NARA) General Records Schedules provide federal policy on records retention." - }, - { - "id": "au-11_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "AU-11 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "au-11_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "The service provider retains audit records on-line for at least ninety days and further preserves audit records off-line for a period that is in accordance with NARA requirements." - }, - { - "id": "au-11_fr_smt.2", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "The service provider must support Agency requirements to comply with M-21-31 (https://www.whitehouse.gov/wp-content/uploads/2021/08/M-21-31-Improving-the-Federal-Governments-Investigative-and-Remediation-Capabilities-Related-to-Cybersecurity-Incidents.pdf)" - }, - { - "id": "au-11_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "The service provider is encouraged to align with M-21-31 where possible" - } - ] - }, - { - "id": "au-11_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-11", - "class": "sp800-53a" - } - ], - "prose": "audit records are retained for {{ insert: param, au-11_odp }} to provide support for after-the-fact investigations of incidents and to meet regulatory and organizational information retention requirements.", - "links": [ - { - "href": "#au-11_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-11_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-11-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nsystem security plan\n\nprivacy plan\n\naudit record retention policy and procedures\n\nsecurity plan\n\norganization-defined retention period for audit records\n\naudit record archives\n\naudit logs\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-11_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-11-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit record retention responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators" - } - ] - } - ] - }, - { - "id": "au-12", - "class": "SP800-53", - "title": "Audit Record Generation", - "params": [ - { - "id": "au-12_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "au-12_prm_1" - }, - { - "name": "label", - "value": "AU-12_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "system components", - "constraints": [ - { - "description": "all information system and network components where audit capability is deployed/available" - } - ], - "guidelines": [ - { - "prose": "system components that provide an audit record generation capability for the events types (defined in AU-02_ODP\\[02\\]) are defined;" - } - ] - }, - { - "id": "au-12_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "au-12_prm_2" - }, - { - "name": "label", - "value": "AU-12_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles allowed to select the event types that are to be logged by specific components of the system is/are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-12", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-12" - }, - { - "name": "label", - "value": "AU-12", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-12" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-3", - "rel": "related" - }, - { - "href": "#au-4", - "rel": "related" - }, - { - "href": "#au-5", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-14", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-12", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sc-18", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - }, - { - "href": "#si-10", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-12_smt", - "name": "statement", - "parts": [ - { - "id": "au-12_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Provide audit record generation capability for the event types the system is capable of auditing as defined in [AU-2a](#au-2_smt.a) on {{ insert: param, au-12_odp.01 }};" - }, - { - "id": "au-12_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Allow {{ insert: param, au-12_odp.02 }} to select the event types that are to be logged by specific components of the system; and" - }, - { - "id": "au-12_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Generate audit records for the event types defined in [AU-2c](#au-2_smt.c) that include the audit record content defined in [AU-3](#au-3)." - } - ] - }, - { - "id": "au-12_gdn", - "name": "guidance", - "prose": "Audit records can be generated from many different system components. The event types specified in [AU-2d](#au-2_smt.d) are the event types for which audit logs are to be generated and are a subset of all event types for which the system can generate audit records." - }, - { - "id": "au-12_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-12", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-12_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-12a.", - "class": "sp800-53a" - } - ], - "prose": "audit record generation capability for the event types the system is capable of auditing (defined in AU-02_ODP\\[01\\]) is provided by {{ insert: param, au-12_odp.01 }};", - "links": [ - { - "href": "#au-12_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-12_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-12b.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, au-12_odp.02 }} is/are allowed to select the event types that are to be logged by specific components of the system;", - "links": [ - { - "href": "#au-12_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-12_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-12c.", - "class": "sp800-53a" - } - ], - "prose": "audit records for the event types defined in AU-02_ODP\\[02\\] that include the audit record content defined in AU-03 are generated.", - "links": [ - { - "href": "#au-12_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-12_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-12_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-12-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nprocedures addressing audit record generation\n\nsystem security plan\n\nprivacy plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of auditable events\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-12_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-12-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit record generation responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "au-12_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-12-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing audit record generation capability" - } - ] - } - ], - "controls": [ - { - "id": "au-12.1", - "class": "SP800-53-enhancement", - "title": "System-wide and Time-correlated Audit Trail", - "params": [ - { - "id": "au-12.01_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "au-12.1_prm_1" - }, - { - "name": "label", - "value": "AU-12(01)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "system components", - "constraints": [ - { - "description": "all network, data storage, and computing devices" - } - ], - "guidelines": [ - { - "prose": "system components from which audit records are to be compiled into a system-wide (logical or physical) audit trail are defined;" - } - ] - }, - { - "id": "au-12.01_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "au-12.1_prm_2" - }, - { - "name": "alt-label", - "value": "level of tolerance for the relationship between time stamps of individual records in the audit trail", - "class": "sp800-53" - }, - { - "name": "label", - "value": "AU-12(01)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "level of tolerance", - "guidelines": [ - { - "prose": "level of tolerance for the relationship between timestamps of individual records in the audit trail is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-12(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-12(1)" - }, - { - "name": "label", - "value": "AU-12(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-12.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#au-12", - "rel": "required" - }, - { - "href": "#au-8", - "rel": "related" - }, - { - "href": "#sc-45", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-12.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Compile audit records from {{ insert: param, au-12.01_odp.01 }} into a system-wide (logical or physical) audit trail that is time-correlated to within {{ insert: param, au-12.01_odp.02 }}." - }, - { - "id": "au-12.1_gdn", - "name": "guidance", - "prose": "Audit trails are time-correlated if the time stamps in the individual audit records can be reliably related to the time stamps in other audit records to achieve a time ordering of the records within organizational tolerances." - }, - { - "id": "au-12.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-12(01)", - "class": "sp800-53a" - } - ], - "prose": "audit records from {{ insert: param, au-12.01_odp.01 }} are compiled into a system-wide (logical or physical) audit trail that is time-correlated to within {{ insert: param, au-12.01_odp.02 }}.", - "links": [ - { - "href": "#au-12.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-12.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-12(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nsystem security plan\n\nprivacy plan\n\nprocedures addressing audit record generation\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem-wide audit trail (logical or physical)\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-12.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-12(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit record generation responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "au-12.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-12(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing audit record generation capability" - } - ] - } - ] - }, - { - "id": "au-12.3", - "class": "SP800-53-enhancement", - "title": "Changes by Authorized Individuals", - "params": [ - { - "id": "au-12.03_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "au-12.3_prm_1" - }, - { - "name": "label", - "value": "AU-12(03)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "individuals or roles", - "constraints": [ - { - "description": "service provider-defined individuals or roles with audit configuration responsibilities" - } - ], - "guidelines": [ - { - "prose": "individuals or roles authorized to change the logging on system components are defined;" - } - ] - }, - { - "id": "au-12.03_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "au-12.3_prm_2" - }, - { - "name": "label", - "value": "AU-12(03)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "system components", - "constraints": [ - { - "description": "all network, data storage, and computing devices" - } - ], - "guidelines": [ - { - "prose": "system components on which logging is to be performed are defined;" - } - ] - }, - { - "id": "au-12.03_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "au-12.3_prm_3" - }, - { - "name": "label", - "value": "AU-12(03)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "selectable event criteria", - "guidelines": [ - { - "prose": "selectable event criteria with which change logging is to be performed are defined;" - } - ] - }, - { - "id": "au-12.03_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "au-12.3_prm_4" - }, - { - "name": "label", - "value": "AU-12(03)_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "time thresholds", - "guidelines": [ - { - "prose": "time thresholds in which logging actions are to change is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "AU-12(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "AU-12(3)" - }, - { - "name": "label", - "value": "AU-12(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "au-12.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#au-12", - "rel": "required" - }, - { - "href": "#ac-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "au-12.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Provide and implement the capability for {{ insert: param, au-12.03_odp.01 }} to change the logging to be performed on {{ insert: param, au-12.03_odp.02 }} based on {{ insert: param, au-12.03_odp.03 }} within {{ insert: param, au-12.03_odp.04 }}." - }, - { - "id": "au-12.3_gdn", - "name": "guidance", - "prose": "Permitting authorized individuals to make changes to system logging enables organizations to extend or limit logging as necessary to meet organizational requirements. Logging that is limited to conserve system resources may be extended (either temporarily or permanently) to address certain threat situations. In addition, logging may be limited to a specific set of event types to facilitate audit reduction, analysis, and reporting. Organizations can establish time thresholds in which logging actions are changed (e.g., near real-time, within minutes, or within hours)." - }, - { - "id": "au-12.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "AU-12(03)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "au-12.3_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-12(03)[01]", - "class": "sp800-53a" - } - ], - "prose": "the capability for {{ insert: param, au-12.03_odp.01 }} to change the logging to be performed on {{ insert: param, au-12.03_odp.02 }} based on {{ insert: param, au-12.03_odp.03 }} within {{ insert: param, au-12.03_odp.04 }} is provided;", - "links": [ - { - "href": "#au-12.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-12.3_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "AU-12(03)[02]", - "class": "sp800-53a" - } - ], - "prose": "the capability for {{ insert: param, au-12.03_odp.01 }} to change the logging to be performed on {{ insert: param, au-12.03_odp.02 }} based on {{ insert: param, au-12.03_odp.03 }} within {{ insert: param, au-12.03_odp.04 }} is implemented.", - "links": [ - { - "href": "#au-12.3_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#au-12.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "au-12.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "AU-12(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Audit and accountability policy\n\nsystem security plan\n\nprivacy plan\n\nprocedures addressing audit record generation\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem-generated list of individuals or roles authorized to change auditing to be performed\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "au-12.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "AU-12(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with audit record generation responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "au-12.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "AU-12(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing audit record generation capability" - } - ] - } - ] - } - ] - } - ] - }, - { - "id": "ca", - "class": "family", - "title": "Assessment, Authorization, and Monitoring", - "controls": [ - { - "id": "ca-1", - "class": "SP800-53", - "title": "Policy and Procedures", - "params": [ - { - "id": "ca-1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ca-01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ca-01_odp.02" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "ca-01_odp.01", - "props": [ - { - "name": "label", - "value": "CA-01_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the assessment, authorization, and monitoring policy is to be disseminated is/are defined;" - } - ] - }, - { - "id": "ca-01_odp.02", - "props": [ - { - "name": "label", - "value": "CA-01_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the assessment, authorization, and monitoring procedures are to be disseminated is/are defined;" - } - ] - }, - { - "id": "ca-01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ca-1_prm_2" - }, - { - "name": "label", - "value": "CA-01_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "organization-level", - "mission/business process-level", - "system-level" - ] - } - }, - { - "id": "ca-01_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "ca-1_prm_3" - }, - { - "name": "label", - "value": "CA-01_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "official", - "guidelines": [ - { - "prose": "an official to manage the assessment, authorization, and monitoring policy and procedures is defined;" - } - ] - }, - { - "id": "ca-01_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "ca-1_prm_4" - }, - { - "name": "label", - "value": "CA-01_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current assessment, authorization, and monitoring policy is reviewed and updated is defined;" - } - ] - }, - { - "id": "ca-01_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "ca-1_prm_5" - }, - { - "name": "label", - "value": "CA-01_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that would require the current assessment, authorization, and monitoring policy to be reviewed and updated are defined;" - } - ] - }, - { - "id": "ca-01_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "ca-1_prm_6" - }, - { - "name": "label", - "value": "CA-01_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current assessment, authorization, and monitoring procedures are reviewed and updated is defined;" - } - ] - }, - { - "id": "ca-01_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "ca-1_prm_7" - }, - { - "name": "label", - "value": "CA-01_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "events", - "constraints": [ - { - "description": "significant changes" - } - ], - "guidelines": [ - { - "prose": "events that would require assessment, authorization, and monitoring procedures to be reviewed and updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CA-01", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CA-1" - }, - { - "name": "label", - "value": "CA-01", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ca-01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#c7ac44e8-10db-4b64-b2b9-9e32ec1efed0", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#482e4c99-9dc4-41ad-bba8-0f3f0032c1f8", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#a21aef46-7330-48a0-b2e1-c5bb8b2dd11d", - "rel": "reference" - }, - { - "href": "#4c0ec2ee-a0d6-428a-9043-4504bc3ade6f", - "rel": "reference" - }, - { - "href": "#067223d8-1ec7-45c5-b21b-c848da6de8fb", - "rel": "reference" - }, - { - "href": "#62ea77ca-e450-4323-b210-e0d75390e785", - "rel": "reference" - }, - { - "href": "#98d415ca-7281-4064-9931-0c366637e324", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "ca-1_smt", - "name": "statement", - "parts": [ - { - "id": "ca-1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, a policy that addresses Assessment, Authorization, and Monitoring MUST be associated with CA-1 part a.", - "class": "policy" - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, at least one procedure that addresses Assessment, Authorization, and Monitoring MUST be associated with CA-1 part a.", - "class": "procedure" - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, document, and disseminate to {{ insert: param, ca-1_prm_1 }}:", - "parts": [ - { - "id": "ca-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, ca-01_odp.03 }} assessment, authorization, and monitoring policy that:", - "parts": [ - { - "id": "ca-1_smt.a.1.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "ca-1_smt.a.1.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and" - } - ] - }, - { - "id": "ca-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the assessment, authorization, and monitoring policy and the associated assessment, authorization, and monitoring controls;" - } - ] - }, - { - "id": "ca-1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Designate an {{ insert: param, ca-01_odp.04 }} to manage the development, documentation, and dissemination of the assessment, authorization, and monitoring policy and procedures; and" - }, - { - "id": "ca-1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the current assessment, authorization, and monitoring:", - "parts": [ - { - "id": "ca-1_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Policy {{ insert: param, ca-01_odp.05 }} and following {{ insert: param, ca-01_odp.06 }} ; and" - }, - { - "id": "ca-1_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures {{ insert: param, ca-01_odp.07 }} and following {{ insert: param, ca-01_odp.08 }}." - } - ] - } - ] - }, - { - "id": "ca-1_gdn", - "name": "guidance", - "prose": "Assessment, authorization, and monitoring policy and procedures address the controls in the CA family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of assessment, authorization, and monitoring policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to assessment, authorization, and monitoring policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure." - }, - { - "id": "ca-1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-01a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-01a.[01]", - "class": "sp800-53a" - } - ], - "prose": "an assessment, authorization, and monitoring policy is developed and documented;", - "links": [ - { - "href": "#ca-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-01a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the assessment, authorization, and monitoring policy is disseminated to {{ insert: param, ca-01_odp.01 }};", - "links": [ - { - "href": "#ca-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-1_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-01a.[03]", - "class": "sp800-53a" - } - ], - "prose": "assessment, authorization, and monitoring procedures to facilitate the implementation of the assessment, authorization, and monitoring policy and associated assessment, authorization, and monitoring controls are developed and documented;", - "links": [ - { - "href": "#ca-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-1_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-01a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the assessment, authorization, and monitoring procedures are disseminated to {{ insert: param, ca-01_odp.02 }};", - "links": [ - { - "href": "#ca-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-1_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-01a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-1_obj.a.1.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-01a.01(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-1_obj.a.1.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-01a.01(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ca-01_odp.03 }} assessment, authorization, and monitoring policy addresses purpose;", - "links": [ - { - "href": "#ca-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-1_obj.a.1.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-01a.01(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ca-01_odp.03 }} assessment, authorization, and monitoring policy addresses scope;", - "links": [ - { - "href": "#ca-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-1_obj.a.1.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-01a.01(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ca-01_odp.03 }} assessment, authorization, and monitoring policy addresses roles;", - "links": [ - { - "href": "#ca-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-1_obj.a.1.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-01a.01(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ca-01_odp.03 }} assessment, authorization, and monitoring policy addresses responsibilities;", - "links": [ - { - "href": "#ca-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-1_obj.a.1.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-01a.01(a)[05]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ca-01_odp.03 }} assessment, authorization, and monitoring policy addresses management commitment;", - "links": [ - { - "href": "#ca-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-1_obj.a.1.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-01a.01(a)[06]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ca-01_odp.03 }} assessment, authorization, and monitoring policy addresses coordination among organizational entities;", - "links": [ - { - "href": "#ca-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-1_obj.a.1.a-7", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-01a.01(a)[07]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ca-01_odp.03 }} assessment, authorization, and monitoring policy addresses compliance;", - "links": [ - { - "href": "#ca-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-1_obj.a.1.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-01a.01(b)", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ca-01_odp.03 }} assessment, authorization, and monitoring policy is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines;", - "links": [ - { - "href": "#ca-1_smt.a.1.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-1_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-01b.", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ca-01_odp.04 }} is designated to manage the development, documentation, and dissemination of the assessment, authorization, and monitoring policy and procedures;", - "links": [ - { - "href": "#ca-1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-01c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-1_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-01c.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-1_obj.c.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-01c.01[01]", - "class": "sp800-53a" - } - ], - "prose": "the current assessment, authorization, and monitoring policy is reviewed and updated {{ insert: param, ca-01_odp.05 }};", - "links": [ - { - "href": "#ca-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-1_obj.c.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-01c.01[02]", - "class": "sp800-53a" - } - ], - "prose": "the current assessment, authorization, and monitoring policy is reviewed and updated following {{ insert: param, ca-01_odp.06 }};", - "links": [ - { - "href": "#ca-1_smt.c.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-1_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-01c.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-1_obj.c.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-01c.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the current assessment, authorization, and monitoring procedures are reviewed and updated {{ insert: param, ca-01_odp.07 }};", - "links": [ - { - "href": "#ca-1_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-1_obj.c.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-01c.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the current assessment, authorization, and monitoring procedures are reviewed and updated following {{ insert: param, ca-01_odp.08 }}.", - "links": [ - { - "href": "#ca-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-1_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CA-01-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Assessment, authorization, and monitoring policy and procedures\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ca-1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CA-01-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with assessment, authorization, and monitoring policy responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - }, - { - "id": "ca-2", - "class": "SP800-53", - "title": "Control Assessments", - "params": [ - { - "id": "ca-02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ca-2_prm_1" - }, - { - "name": "alt-label", - "value": "frequency", - "class": "sp800-53" - }, - { - "name": "label", - "value": "CA-02_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "assessment frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to assess controls in the system and its environment of operation is defined;" - } - ] - }, - { - "id": "ca-02_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ca-2_prm_2" - }, - { - "name": "label", - "value": "CA-02_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "individuals or roles", - "constraints": [ - { - "description": "individuals or roles to include FedRAMP PMO" - } - ], - "guidelines": [ - { - "prose": "individuals or roles to whom control assessment results are to be provided are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CA-02", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CA-2" - }, - { - "name": "label", - "value": "CA-02", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ca-02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#628d22a1-6a11-4784-bc59-5cd9497b5445", - "rel": "reference" - }, - { - "href": "#30eb758a-2707-4bca-90ad-949a74d4eb16", - "rel": "reference" - }, - { - "href": "#482e4c99-9dc4-41ad-bba8-0f3f0032c1f8", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#a21aef46-7330-48a0-b2e1-c5bb8b2dd11d", - "rel": "reference" - }, - { - "href": "#122177fa-c4ed-485d-8345-3082c0fb9a06", - "rel": "reference" - }, - { - "href": "#067223d8-1ec7-45c5-b21b-c848da6de8fb", - "rel": "reference" - }, - { - "href": "#bbac9fc2-df5b-4f2d-bf99-90d0ade45349", - "rel": "reference" - }, - { - "href": "#98d415ca-7281-4064-9931-0c366637e324", - "rel": "reference" - }, - { - "href": "#ac-20", - "rel": "related" - }, - { - "href": "#ca-5", - "rel": "related" - }, - { - "href": "#ca-6", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ra-10", - "rel": "related" - }, - { - "href": "#sa-11", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-38", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - }, - { - "href": "#sr-2", - "rel": "related" - }, - { - "href": "#sr-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "ca-2_smt", - "name": "statement", - "parts": [ - { - "id": "ca-2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Select the appropriate assessor or assessment team for the type of assessment to be conducted;" - }, - { - "id": "ca-2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Develop a control assessment plan that describes the scope of the assessment including:", - "parts": [ - { - "id": "ca-2_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Controls and control enhancements under assessment;" - }, - { - "id": "ca-2_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Assessment procedures to be used to determine control effectiveness; and" - }, - { - "id": "ca-2_smt.b.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Assessment environment, assessment team, and assessment roles and responsibilities;" - } - ] - }, - { - "id": "ca-2_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Ensure the control assessment plan is reviewed and approved by the authorizing official or designated representative prior to conducting the assessment;" - }, - { - "id": "ca-2_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Assess the controls in the system and its environment of operation {{ insert: param, ca-02_odp.01 }} to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting established security and privacy requirements;" - }, - { - "id": "ca-2_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Produce a control assessment report that document the results of the assessment; and" - }, - { - "id": "ca-2_smt.f", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "f." - } - ], - "prose": "Provide the results of the control assessment to {{ insert: param, ca-02_odp.02 }}." - } - ] - }, - { - "id": "ca-2_gdn", - "name": "guidance", - "prose": "Organizations ensure that control assessors possess the required skills and technical expertise to develop effective assessment plans and to conduct assessments of system-specific, hybrid, common, and program management controls, as appropriate. The required skills include general knowledge of risk management concepts and approaches as well as comprehensive knowledge of and experience with the hardware, software, and firmware system components implemented.\n\nOrganizations assess controls in systems and the environments in which those systems operate as part of initial and ongoing authorizations, continuous monitoring, FISMA annual assessments, system design and development, systems security engineering, privacy engineering, and the system development life cycle. Assessments help to ensure that organizations meet information security and privacy requirements, identify weaknesses and deficiencies in the system design and development process, provide essential information needed to make risk-based decisions as part of authorization processes, and comply with vulnerability mitigation procedures. Organizations conduct assessments on the implemented controls as documented in security and privacy plans. Assessments can also be conducted throughout the system development life cycle as part of systems engineering and systems security engineering processes. The design for controls can be assessed as RFPs are developed, responses assessed, and design reviews conducted. If a design to implement controls and subsequent implementation in accordance with the design are assessed during development, the final control testing can be a simple confirmation utilizing previously completed control assessment and aggregating the outcomes.\n\nOrganizations may develop a single, consolidated security and privacy assessment plan for the system or maintain separate plans. A consolidated assessment plan clearly delineates the roles and responsibilities for control assessment. If multiple organizations participate in assessing a system, a coordinated approach can reduce redundancies and associated costs.\n\nOrganizations can use other types of assessment activities, such as vulnerability scanning and system monitoring, to maintain the security and privacy posture of systems during the system life cycle. Assessment reports document assessment results in sufficient detail, as deemed necessary by organizations, to determine the accuracy and completeness of the reports and whether the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting requirements. Assessment results are provided to the individuals or roles appropriate for the types of assessments being conducted. For example, assessments conducted in support of authorization decisions are provided to authorizing officials, senior agency officials for privacy, senior agency information security officers, and authorizing official designated representatives.\n\nTo satisfy annual assessment requirements, organizations can use assessment results from the following sources: initial or ongoing system authorizations, continuous monitoring, systems engineering processes, or system development life cycle activities. Organizations ensure that assessment results are current, relevant to the determination of control effectiveness, and obtained with the appropriate level of assessor independence. Existing control assessment results can be reused to the extent that the results are still valid and can also be supplemented with additional assessments as needed. After the initial authorizations, organizations assess controls during continuous monitoring. Organizations also establish the frequency for ongoing assessments in accordance with organizational continuous monitoring strategies. External audits, including audits by external entities such as regulatory agencies, are outside of the scope of [CA-2](#ca-2)." - }, - { - "id": "ca-2_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CA-2 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ca-2_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Reference FedRAMP Annual Assessment Guidance." - } - ] - }, - { - "id": "ca-2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-02a.", - "class": "sp800-53a" - } - ], - "prose": "an appropriate assessor or assessment team is selected for the type of assessment to be conducted;", - "links": [ - { - "href": "#ca-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-02b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-2_obj.b.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-02b.01", - "class": "sp800-53a" - } - ], - "prose": "a control assessment plan is developed that describes the scope of the assessment, including controls and control enhancements under assessment;", - "links": [ - { - "href": "#ca-2_smt.b.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-2_obj.b.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-02b.02", - "class": "sp800-53a" - } - ], - "prose": "a control assessment plan is developed that describes the scope of the assessment, including assessment procedures to be used to determine control effectiveness;", - "links": [ - { - "href": "#ca-2_smt.b.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-2_obj.b.3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-02b.03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-2_obj.b.3-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-02b.03[01]", - "class": "sp800-53a" - } - ], - "prose": "a control assessment plan is developed that describes the scope of the assessment, including the assessment environment;", - "links": [ - { - "href": "#ca-2_smt.b.3", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-2_obj.b.3-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-02b.03[02]", - "class": "sp800-53a" - } - ], - "prose": "a control assessment plan is developed that describes the scope of the assessment, including the assessment team;", - "links": [ - { - "href": "#ca-2_smt.b.3", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-2_obj.b.3-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-02b.03[03]", - "class": "sp800-53a" - } - ], - "prose": "a control assessment plan is developed that describes the scope of the assessment, including assessment roles and responsibilities;", - "links": [ - { - "href": "#ca-2_smt.b.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-2_smt.b.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-2_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-02c.", - "class": "sp800-53a" - } - ], - "prose": "the control assessment plan is reviewed and approved by the authorizing official or designated representative prior to conducting the assessment;", - "links": [ - { - "href": "#ca-2_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-2_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-02d.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-2_obj.d-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-02d.[01]", - "class": "sp800-53a" - } - ], - "prose": "controls are assessed in the system and its environment of operation {{ insert: param, ca-02_odp.01 }} to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting established security requirements;", - "links": [ - { - "href": "#ca-2_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-2_obj.d-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-02d.[02]", - "class": "sp800-53a" - } - ], - "prose": "controls are assessed in the system and its environment of operation {{ insert: param, ca-02_odp.01 }} to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting established privacy requirements;", - "links": [ - { - "href": "#ca-2_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-2_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-2_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-02e.", - "class": "sp800-53a" - } - ], - "prose": "a control assessment report is produced that documents the results of the assessment;", - "links": [ - { - "href": "#ca-2_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-2_obj.f", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-02f.", - "class": "sp800-53a" - } - ], - "prose": "the results of the control assessment are provided to {{ insert: param, ca-02_odp.02 }}.", - "links": [ - { - "href": "#ca-2_smt.f", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CA-02-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Assessment, authorization, and monitoring policy\n\nprocedures addressing assessment planning\n\nprocedures addressing control assessments\n\ncontrol assessment plan\n\ncontrol assessment report\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ca-2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CA-02-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with control assessment responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "ca-2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CA-02-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting control assessment, control assessment plan development, and/or control assessment reporting" - } - ] - } - ], - "controls": [ - { - "id": "ca-2.1", - "class": "SP800-53-enhancement", - "title": "Independent Assessors", - "props": [ - { - "name": "label", - "value": "CA-02(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CA-2(1)" - }, - { - "name": "label", - "value": "CA-02(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ca-02.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ca-2", - "rel": "required" - } - ], - "parts": [ - { - "id": "ca-2.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Employ independent assessors or assessment teams to conduct control assessments." - }, - { - "id": "ca-2.1_gdn", - "name": "guidance", - "prose": "Independent assessors or assessment teams are individuals or groups who conduct impartial assessments of systems. Impartiality means that assessors are free from any perceived or actual conflicts of interest regarding the development, operation, sustainment, or management of the systems under assessment or the determination of control effectiveness. To achieve impartiality, assessors do not create a mutual or conflicting interest with the organizations where the assessments are being conducted, assess their own work, act as management or employees of the organizations they are serving, or place themselves in positions of advocacy for the organizations acquiring their services.\n\nIndependent assessments can be obtained from elements within organizations or be contracted to public or private sector entities outside of organizations. Authorizing officials determine the required level of independence based on the security categories of systems and/or the risk to organizational operations, organizational assets, or individuals. Authorizing officials also determine if the level of assessor independence provides sufficient assurance that the results are sound and can be used to make credible, risk-based decisions. Assessor independence determination includes whether contracted assessment services have sufficient independence, such as when system owners are not directly involved in contracting processes or cannot influence the impartiality of the assessors conducting the assessments. During the system design and development phase, having independent assessors is analogous to having independent SMEs involved in design reviews.\n\nWhen organizations that own the systems are small or the structures of the organizations require that assessments be conducted by individuals that are in the developmental, operational, or management chain of the system owners, independence in assessment processes can be achieved by ensuring that assessment results are carefully reviewed and analyzed by independent teams of experts to validate the completeness, accuracy, integrity, and reliability of the results. Assessments performed for purposes other than to support authorization decisions are more likely to be useable for such decisions when performed by assessors with sufficient independence, thereby reducing the need to repeat assessments." - }, - { - "id": "ca-2.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-02(01)", - "class": "sp800-53a" - } - ], - "prose": "independent assessors or assessment teams are employed to conduct control assessments.", - "links": [ - { - "href": "#ca-2.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-2.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CA-02(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Assessment, authorization, and monitoring policy\n\nprocedures addressing control assessments\n\nprevious control assessment plan\n\nprevious control assessment report\n\nplan of action and milestones\n\nexisting authorization statement\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ca-2.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CA-02(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with security assessment responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - }, - { - "id": "ca-2.2", - "class": "SP800-53-enhancement", - "title": "Specialized Assessments", - "params": [ - { - "id": "ca-02.02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ca-2.2_prm_1" - }, - { - "name": "alt-label", - "value": "frequency", - "class": "sp800-53" - }, - { - "name": "label", - "value": "CA-02(02)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "specialized assessment frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "frequency at which to include specialized assessments as part of the control assessment is defined;" - } - ] - }, - { - "id": "ca-02.02_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ca-2.2_prm_2" - }, - { - "name": "label", - "value": "CA-02(02)_ODP[02]", - "class": "sp800-53a" - } - ], - "select": { - "choice": [ - "announced", - "unannounced" - ] - } - }, - { - "id": "ca-02.02_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ca-2.2_prm_3" - }, - { - "name": "label", - "value": "CA-02(02)_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "in-depth monitoring", - "security instrumentation", - "automated security test cases", - "vulnerability scanning", - "malicious user testing", - "insider threat assessment", - "performance and load testing", - "data leakage or data loss assessment", - "{{ insert: param, ca-02.02_odp.04 }}" - ] - } - }, - { - "id": "ca-02.02_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "ca-2.2_prm_4" - }, - { - "name": "label", - "value": "CA-02(02)_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "other forms of assessment", - "guidelines": [ - { - "prose": "other forms of assessment are defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CA-02(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CA-2(2)" - }, - { - "name": "label", - "value": "CA-02(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ca-02.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ca-2", - "rel": "required" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - } - ], - "parts": [ - { - "id": "ca-2.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Include as part of control assessments, {{ insert: param, ca-02.02_odp.01 }}, {{ insert: param, ca-02.02_odp.02 }}, {{ insert: param, ca-02.02_odp.03 }}." - }, - { - "id": "ca-2.2_gdn", - "name": "guidance", - "prose": "Organizations can conduct specialized assessments, including verification and validation, system monitoring, insider threat assessments, malicious user testing, and other forms of testing. These assessments can improve readiness by exercising organizational capabilities and indicating current levels of performance as a means of focusing actions to improve security and privacy. Organizations conduct specialized assessments in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Authorizing officials approve the assessment methods in coordination with the organizational risk executive function. Organizations can include vulnerabilities uncovered during assessments into vulnerability remediation processes. Specialized assessments can also be conducted early in the system development life cycle (e.g., during initial design, development, and unit testing)." - }, - { - "id": "ca-2.2_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CA-2 (2) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ca-2.2_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "To include ‘announced’, ‘vulnerability scanning’" - } - ] - }, - { - "id": "ca-2.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-02(02)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ca-02.02_odp.01 }} {{ insert: param, ca-02.02_odp.02 }} {{ insert: param, ca-02.02_odp.03 }} are included as part of control assessments.", - "links": [ - { - "href": "#ca-2.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-2.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CA-02(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Assessment, authorization, and monitoring policy\n\nprocedures addressing control assessments\n\ncontrol assessment plan\n\ncontrol assessment report\n\ncontrol assessment evidence\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ca-2.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CA-02(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with control assessment responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "ca-2.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CA-02(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting control assessment" - } - ] - } - ] - }, - { - "id": "ca-2.3", - "class": "SP800-53-enhancement", - "title": "Leveraging Results from External Organizations", - "params": [ - { - "id": "ca-02.03_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ca-2.3_prm_1" - }, - { - "name": "alt-label", - "value": "external organization", - "class": "sp800-53" - }, - { - "name": "label", - "value": "CA-02(03)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "external organization(s)", - "constraints": [ - { - "description": "any FedRAMP Accredited 3PAO" - } - ], - "guidelines": [ - { - "prose": "external organization(s) from which the results of control assessments are leveraged are defined;" - } - ] - }, - { - "id": "ca-02.03_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ca-2.3_prm_2" - }, - { - "name": "label", - "value": "CA-02(03)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "system", - "guidelines": [ - { - "prose": "system on which a control assessment was performed by an external organization is defined;" - } - ] - }, - { - "id": "ca-02.03_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ca-2.3_prm_3" - }, - { - "name": "label", - "value": "CA-02(03)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "requirements", - "constraints": [ - { - "description": "the conditions of the AO in the FedRAMP Repository" - } - ], - "guidelines": [ - { - "prose": "requirements to be met by the control assessment performed by an external organization on the system are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CA-02(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CA-2(3)" - }, - { - "name": "label", - "value": "CA-02(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ca-02.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ca-2", - "rel": "required" - }, - { - "href": "#sa-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "ca-2.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Leverage the results of control assessments performed by {{ insert: param, ca-02.03_odp.01 }} on {{ insert: param, ca-02.03_odp.02 }} when the assessment meets {{ insert: param, ca-02.03_odp.03 }}." - }, - { - "id": "ca-2.3_gdn", - "name": "guidance", - "prose": "Organizations may rely on control assessments of organizational systems by other (external) organizations. Using such assessments and reusing existing assessment evidence can decrease the time and resources required for assessments by limiting the independent assessment activities that organizations need to perform. The factors that organizations consider in determining whether to accept assessment results from external organizations can vary. Such factors include the organization’s past experience with the organization that conducted the assessment, the reputation of the assessment organization, the level of detail of supporting assessment evidence provided, and mandates imposed by applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Accredited testing laboratories that support the Common Criteria Program [ISO 15408-1](#6afc1b04-c9d6-4023-adbc-f8fbe33a3c73) , the NIST Cryptographic Module Validation Program (CMVP), or the NIST Cryptographic Algorithm Validation Program (CAVP) can provide independent assessment results that organizations can leverage." - }, - { - "id": "ca-2.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-02(03)", - "class": "sp800-53a" - } - ], - "prose": "the results of control assessments performed by {{ insert: param, ca-02.03_odp.01 }} on {{ insert: param, ca-02.03_odp.02 }} are leveraged when the assessment meets {{ insert: param, ca-02.03_odp.03 }}.", - "links": [ - { - "href": "#ca-2.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-2.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CA-02(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Assessment, authorization, and monitoring policy\n\nprocedures addressing control assessments\n\ncontrol assessment requirements\n\ncontrol assessment plan\n\ncontrol assessment report\n\ncontrol assessment evidence\n\nplan of action and milestones\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ca-2.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CA-02(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with control assessment responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\npersonnel performing control assessments for the specified external organization" - } - ] - } - ] - } - ] - }, - { - "id": "ca-3", - "class": "SP800-53", - "title": "Information Exchange", - "params": [ - { - "id": "ca-03_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ca-3_prm_1" - }, - { - "name": "label", - "value": "CA-03_ODP[01]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "interconnection security agreements", - "information exchange security agreements", - "memoranda of understanding or agreement", - "service level agreements", - "user agreements", - "non-disclosure agreements", - "{{ insert: param, ca-03_odp.02 }}" - ] - } - }, - { - "id": "ca-03_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ca-3_prm_2" - }, - { - "name": "label", - "value": "CA-03_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "type of agreement", - "guidelines": [ - { - "prose": "the type of agreement used to approve and manage the exchange of information is defined (if selected);" - } - ] - }, - { - "id": "ca-03_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ca-3_prm_3" - }, - { - "name": "label", - "value": "CA-03_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually and on input from AO" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to review and update agreements is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CA-03", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CA-3" - }, - { - "name": "label", - "value": "CA-03", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ca-03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#628d22a1-6a11-4784-bc59-5cd9497b5445", - "rel": "reference" - }, - { - "href": "#c3a76872-e160-4267-99e8-6952de967d04", - "rel": "reference" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-20", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-16", - "rel": "related" - }, - { - "href": "#ca-6", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-7", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "ca-3_smt", - "name": "statement", - "parts": [ - { - "id": "ca-3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Approve and manage the exchange of information between the system and other systems using {{ insert: param, ca-03_odp.01 }};" - }, - { - "id": "ca-3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Document, as part of each exchange agreement, the interface characteristics, security and privacy requirements, controls, and responsibilities for each system, and the impact level of the information communicated; and" - }, - { - "id": "ca-3_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the agreements {{ insert: param, ca-03_odp.03 }}." - } - ] - }, - { - "id": "ca-3_gdn", - "name": "guidance", - "prose": "System information exchange requirements apply to information exchanges between two or more systems. System information exchanges include connections via leased lines or virtual private networks, connections to internet service providers, database sharing or exchanges of database transaction information, connections and exchanges with cloud services, exchanges via web-based services, or exchanges of files via file transfer protocols, network protocols (e.g., IPv4, IPv6), email, or other organization-to-organization communications. Organizations consider the risk related to new or increased threats that may be introduced when systems exchange information with other systems that may have different security and privacy requirements and controls. This includes systems within the same organization and systems that are external to the organization. A joint authorization of the systems exchanging information, as described in [CA-6(1)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ca-6.1) or [CA-6(2)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ca-6.2) , may help to communicate and reduce risk.\n\nAuthorizing officials determine the risk associated with system information exchange and the controls needed for appropriate risk mitigation. The types of agreements selected are based on factors such as the impact level of the information being exchanged, the relationship between the organizations exchanging information (e.g., government to government, government to business, business to business, government or business to service provider, government or business to individual), or the level of access to the organizational system by users of the other system. If systems that exchange information have the same authorizing official, organizations need not develop agreements. Instead, the interface characteristics between the systems (e.g., how the information is being exchanged. how the information is protected) are described in the respective security and privacy plans. If the systems that exchange information have different authorizing officials within the same organization, the organizations can develop agreements or provide the same information that would be provided in the appropriate agreement type from [CA-3a](#ca-3_smt.a) in the respective security and privacy plans for the systems. Organizations may incorporate agreement information into formal contracts, especially for information exchanges established between federal agencies and nonfederal organizations (including service providers, contractors, system developers, and system integrators). Risk considerations include systems that share the same networks." - }, - { - "id": "ca-3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-03a.", - "class": "sp800-53a" - } - ], - "prose": "the exchange of information between the system and other systems is approved and managed using {{ insert: param, ca-03_odp.01 }};", - "links": [ - { - "href": "#ca-3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-03b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-3_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-03b.[01]", - "class": "sp800-53a" - } - ], - "prose": "the interface characteristics are documented as part of each exchange agreement;", - "links": [ - { - "href": "#ca-3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-3_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-03b.[02]", - "class": "sp800-53a" - } - ], - "prose": "security requirements are documented as part of each exchange agreement;", - "links": [ - { - "href": "#ca-3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-3_obj.b-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-03b.[03]", - "class": "sp800-53a" - } - ], - "prose": "privacy requirements are documented as part of each exchange agreement;", - "links": [ - { - "href": "#ca-3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-3_obj.b-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-03b.[04]", - "class": "sp800-53a" - } - ], - "prose": "controls are documented as part of each exchange agreement;", - "links": [ - { - "href": "#ca-3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-3_obj.b-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-03b.[05]", - "class": "sp800-53a" - } - ], - "prose": "responsibilities for each system are documented as part of each exchange agreement;", - "links": [ - { - "href": "#ca-3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-3_obj.b-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-03b.[06]", - "class": "sp800-53a" - } - ], - "prose": "the impact level of the information communicated is documented as part of each exchange agreement;", - "links": [ - { - "href": "#ca-3_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-3_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-03c.", - "class": "sp800-53a" - } - ], - "prose": "agreements are reviewed and updated {{ insert: param, ca-03_odp.03 }}.", - "links": [ - { - "href": "#ca-3_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CA-03-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing system connections\n\nsystem and communications protection policy\n\nsystem interconnection security agreements\n\ninformation exchange security agreements\n\nmemoranda of understanding or agreements\n\nservice level agreements\n\nnon-disclosure agreements\n\nsystem design documentation\n\nenterprise architecture\n\nsystem architecture\n\nsystem configuration settings and associated documentation\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ca-3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CA-03-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for developing, implementing, or approving system interconnection agreements\n\norganizational personnel with information security and privacy responsibilities\n\npersonnel managing the system(s) to which the interconnection security agreement applies" - } - ] - } - ], - "controls": [ - { - "id": "ca-3.6", - "class": "SP800-53-enhancement", - "title": "Transfer Authorizations", - "props": [ - { - "name": "label", - "value": "CA-03(06)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CA-3(6)" - }, - { - "name": "label", - "value": "CA-03(06)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ca-03.06" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ca-3", - "rel": "required" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "ca-3.6_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Verify that individuals or systems transferring data between interconnecting systems have the requisite authorizations (i.e., write permissions or privileges) prior to accepting such data." - }, - { - "id": "ca-3.6_gdn", - "name": "guidance", - "prose": "To prevent unauthorized individuals and systems from making information transfers to protected systems, the protected system verifies—via independent means— whether the individual or system attempting to transfer information is authorized to do so. Verification of the authorization to transfer information also applies to control plane traffic (e.g., routing and DNS) and services (e.g., authenticated SMTP relays)." - }, - { - "id": "ca-3.6_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-03(06)", - "class": "sp800-53a" - } - ], - "prose": "individuals or systems transferring data between interconnecting systems have the requisite authorizations (i.e., write permissions or privileges) prior to accepting such data.", - "links": [ - { - "href": "#ca-3.6_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-3.6_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CA-03(06)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Access control policy\n\nprocedures addressing system connections\n\nsystem and communications protection policy\n\nsystem interconnection agreements\n\ninformation exchange security agreements\n\nmemoranda of understanding or agreements\n\nservice level agreements\n\nnon-disclosure agreements\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\ncontrol assessment report\n\nsystem audit records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ca-3.6_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CA-03(06)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for managing connections to external systems\n\nnetwork administrators\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "ca-3.6_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CA-03(06)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing restrictions on external system connections" - } - ] - } - ] - } - ] - }, - { - "id": "ca-5", - "class": "SP800-53", - "title": "Plan of Action and Milestones", - "params": [ - { - "id": "ca-05_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ca-5_prm_1" - }, - { - "name": "label", - "value": "CA-05_ODP", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least monthly" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to update an existing plan of action and milestones based on the findings from control assessments, independent audits or reviews, and continuous monitoring activities is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CA-05", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CA-5" - }, - { - "name": "label", - "value": "CA-05", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ca-05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#482e4c99-9dc4-41ad-bba8-0f3f0032c1f8", - "rel": "reference" - }, - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "#ra-7", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "ca-5_smt", - "name": "statement", - "parts": [ - { - "id": "ca-5_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop a plan of action and milestones for the system to document the planned remediation actions of the organization to correct weaknesses or deficiencies noted during the assessment of the controls and to reduce or eliminate known vulnerabilities in the system; and" - }, - { - "id": "ca-5_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Update existing plan of action and milestones {{ insert: param, ca-05_odp }} based on the findings from control assessments, independent audits or reviews, and continuous monitoring activities." - } - ] - }, - { - "id": "ca-5_gdn", - "name": "guidance", - "prose": "Plans of action and milestones are useful for any type of organization to track planned remedial actions. Plans of action and milestones are required in authorization packages and subject to federal reporting requirements established by OMB." - }, - { - "id": "ca-5_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CA-5 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ca-5_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "POA\\&Ms must be provided at least monthly." - }, - { - "id": "ca-5_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Reference FedRAMP-POAM-Template" - } - ] - }, - { - "id": "ca-5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-05", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-5_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-05a.", - "class": "sp800-53a" - } - ], - "prose": "a plan of action and milestones for the system is developed to document the planned remediation actions of the organization to correct weaknesses or deficiencies noted during the assessment of the controls and to reduce or eliminate known vulnerabilities in the system;", - "links": [ - { - "href": "#ca-5_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-5_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-05b.", - "class": "sp800-53a" - } - ], - "prose": "existing plan of action and milestones are updated {{ insert: param, ca-05_odp }} based on the findings from control assessments, independent audits or reviews, and continuous monitoring activities.", - "links": [ - { - "href": "#ca-5_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CA-05-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Assessment, authorization, and monitoring policy\n\nprocedures addressing plan of action and milestones\n\ncontrol assessment plan\n\ncontrol assessment report\n\ncontrol assessment evidence\n\nplan of action and milestones\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ca-5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CA-05-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with plan of action and milestones development and implementation responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "ca-5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CA-05-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms for developing, implementing, and maintaining plan of action and milestones" - } - ] - } - ] - }, - { - "id": "ca-6", - "class": "SP800-53", - "title": "Authorization", - "params": [ - { - "id": "ca-06_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ca-6_prm_1" - }, - { - "name": "label", - "value": "CA-06_ODP", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "in accordance with OMB A-130 requirements or when a significant change occurs" - } - ], - "guidelines": [ - { - "prose": "frequency at which to update the authorizations is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CA-06", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CA-6" - }, - { - "name": "label", - "value": "CA-06", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ca-06" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#482e4c99-9dc4-41ad-bba8-0f3f0032c1f8", - "rel": "reference" - }, - { - "href": "#067223d8-1ec7-45c5-b21b-c848da6de8fb", - "rel": "reference" - }, - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-3", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-10", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "ca-6_smt", - "name": "statement", - "parts": [ - { - "id": "ca-6_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Assign a senior official as the authorizing official for the system;" - }, - { - "id": "ca-6_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Assign a senior official as the authorizing official for common controls available for inheritance by organizational systems;" - }, - { - "id": "ca-6_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Ensure that the authorizing official for the system, before commencing operations:", - "parts": [ - { - "id": "ca-6_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Accepts the use of common controls inherited by the system; and" - }, - { - "id": "ca-6_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Authorizes the system to operate;" - } - ] - }, - { - "id": "ca-6_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Ensure that the authorizing official for common controls authorizes the use of those controls for inheritance by organizational systems;" - }, - { - "id": "ca-6_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Update the authorizations {{ insert: param, ca-06_odp }}." - } - ] - }, - { - "id": "ca-6_gdn", - "name": "guidance", - "prose": "Authorizations are official management decisions by senior officials to authorize operation of systems, authorize the use of common controls for inheritance by organizational systems, and explicitly accept the risk to organizational operations and assets, individuals, other organizations, and the Nation based on the implementation of agreed-upon controls. Authorizing officials provide budgetary oversight for organizational systems and common controls or assume responsibility for the mission and business functions supported by those systems or common controls. The authorization process is a federal responsibility, and therefore, authorizing officials must be federal employees. Authorizing officials are both responsible and accountable for security and privacy risks associated with the operation and use of organizational systems. Nonfederal organizations may have similar processes to authorize systems and senior officials that assume the authorization role and associated responsibilities.\n\nAuthorizing officials issue ongoing authorizations of systems based on evidence produced from implemented continuous monitoring programs. Robust continuous monitoring programs reduce the need for separate reauthorization processes. Through the employment of comprehensive continuous monitoring processes, the information contained in authorization packages (i.e., security and privacy plans, assessment reports, and plans of action and milestones) is updated on an ongoing basis. This provides authorizing officials, common control providers, and system owners with an up-to-date status of the security and privacy posture of their systems, controls, and operating environments. To reduce the cost of reauthorization, authorizing officials can leverage the results of continuous monitoring processes to the maximum extent possible as the basis for rendering reauthorization decisions." - }, - { - "id": "ca-6_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CA-6 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ca-6_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(e) Guidance:" - } - ], - "prose": "Significant change is defined in NIST Special Publication 800-37 Revision 2, Appendix F and according to FedRAMP Significant Change Policies and Procedures. The service provider describes the types of changes to the information system or the environment of operations that would impact the risk posture. The types of changes are approved and accepted by the AO." - } - ] - }, - { - "id": "ca-6_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-06", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-6_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-06a.", - "class": "sp800-53a" - } - ], - "prose": "a senior official is assigned as the authorizing official for the system;", - "links": [ - { - "href": "#ca-6_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-6_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-06b.", - "class": "sp800-53a" - } - ], - "prose": "a senior official is assigned as the authorizing official for common controls available for inheritance by organizational systems;", - "links": [ - { - "href": "#ca-6_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-6_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-06c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-6_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-06c.01", - "class": "sp800-53a" - } - ], - "prose": "before commencing operations, the authorizing official for the system accepts the use of common controls inherited by the system;", - "links": [ - { - "href": "#ca-6_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-6_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-06c.02", - "class": "sp800-53a" - } - ], - "prose": "before commencing operations, the authorizing official for the system authorizes the system to operate;", - "links": [ - { - "href": "#ca-6_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-6_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-6_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-06d.", - "class": "sp800-53a" - } - ], - "prose": "the authorizing official for common controls authorizes the use of those controls for inheritance by organizational systems;", - "links": [ - { - "href": "#ca-6_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-6_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-06e.", - "class": "sp800-53a" - } - ], - "prose": "the authorizations are updated {{ insert: param, ca-06_odp }}.", - "links": [ - { - "href": "#ca-6_smt.e", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-6_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-6_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CA-06-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Assessment, authorization, and monitoring policy\n\nprocedures addressing authorization\n\nsystem security plan, privacy plan, assessment report, plan of action and milestones\n\nauthorization statement\n\nother relevant documents or records" - } - ] - }, - { - "id": "ca-6_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CA-06-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with authorization responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "ca-6_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CA-06-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms that facilitate authorizations and updates" - } - ] - } - ] - }, - { - "id": "ca-7", - "class": "SP800-53", - "title": "Continuous Monitoring", - "params": [ - { - "id": "ca-7_prm_4", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ca-07_odp.04" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ca-07_odp.06" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "ca-7_prm_5", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ca-07_odp.05" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ca-07_odp.07" - } - ], - "label": "organization-defined frequency" - }, - { - "id": "ca-07_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ca-7_prm_1" - }, - { - "name": "label", - "value": "CA-07_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "system-level metrics", - "guidelines": [ - { - "prose": "system-level metrics to be monitored are defined;" - } - ] - }, - { - "id": "ca-07_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ca-7_prm_2" - }, - { - "name": "label", - "value": "CA-07_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequencies", - "guidelines": [ - { - "prose": "frequencies at which to monitor control effectiveness are defined;" - } - ] - }, - { - "id": "ca-07_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ca-7_prm_3" - }, - { - "name": "label", - "value": "CA-07_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "frequencies", - "guidelines": [ - { - "prose": "frequencies at which to assess control effectiveness are defined;" - } - ] - }, - { - "id": "ca-07_odp.04", - "props": [ - { - "name": "label", - "value": "CA-07_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "constraints": [ - { - "description": "to include AO" - } - ], - "guidelines": [ - { - "prose": "personnel or roles to whom the security status of the system is reported are defined;" - } - ] - }, - { - "id": "ca-07_odp.05", - "props": [ - { - "name": "label", - "value": "CA-07_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "guidelines": [ - { - "prose": "frequency at which the security status of the system is reported is defined;" - } - ] - }, - { - "id": "ca-07_odp.06", - "props": [ - { - "name": "label", - "value": "CA-07_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "constraints": [ - { - "description": "to include AO" - } - ], - "guidelines": [ - { - "prose": "personnel or roles to whom the privacy status of the system is reported are defined;" - } - ] - }, - { - "id": "ca-07_odp.07", - "props": [ - { - "name": "label", - "value": "CA-07_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "guidelines": [ - { - "prose": "frequency at which the privacy status of the system is reported is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CA-07", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CA-7" - }, - { - "name": "label", - "value": "CA-07", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ca-07" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#482e4c99-9dc4-41ad-bba8-0f3f0032c1f8", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#a21aef46-7330-48a0-b2e1-c5bb8b2dd11d", - "rel": "reference" - }, - { - "href": "#122177fa-c4ed-485d-8345-3082c0fb9a06", - "rel": "reference" - }, - { - "href": "#067223d8-1ec7-45c5-b21b-c848da6de8fb", - "rel": "reference" - }, - { - "href": "#bbac9fc2-df5b-4f2d-bf99-90d0ade45349", - "rel": "reference" - }, - { - "href": "#98d415ca-7281-4064-9931-0c366637e324", - "rel": "reference" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#at-4", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-13", - "rel": "related" - }, - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-5", - "rel": "related" - }, - { - "href": "#ca-6", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-11", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#ir-5", - "rel": "related" - }, - { - "href": "#ma-2", - "rel": "related" - }, - { - "href": "#ma-3", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pe-6", - "rel": "related" - }, - { - "href": "#pe-14", - "rel": "related" - }, - { - "href": "#pe-16", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pe-20", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-6", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-10", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-12", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-14", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-23", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-28", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-31", - "rel": "related" - }, - { - "href": "#ps-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-7", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#ra-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ra-10", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - }, - { - "href": "#sa-11", - "rel": "related" - }, - { - "href": "#sc-5", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-18", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-38", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-43", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - }, - { - "href": "#sr-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "ca-7_smt", - "name": "statement", - "prose": "Develop a system-level continuous monitoring strategy and implement continuous monitoring in accordance with the organization-level continuous monitoring strategy that includes:", - "parts": [ - { - "id": "ca-7_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Establishing the following system-level metrics to be monitored: {{ insert: param, ca-07_odp.01 }};" - }, - { - "id": "ca-7_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Establishing {{ insert: param, ca-07_odp.02 }} for monitoring and {{ insert: param, ca-07_odp.03 }} for assessment of control effectiveness;" - }, - { - "id": "ca-7_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Ongoing control assessments in accordance with the continuous monitoring strategy;" - }, - { - "id": "ca-7_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Ongoing monitoring of system and organization-defined metrics in accordance with the continuous monitoring strategy;" - }, - { - "id": "ca-7_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Correlation and analysis of information generated by control assessments and monitoring;" - }, - { - "id": "ca-7_smt.f", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "f." - } - ], - "prose": "Response actions to address results of the analysis of control assessment and monitoring information; and" - }, - { - "id": "ca-7_smt.g", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "g." - } - ], - "prose": "Reporting the security and privacy status of the system to {{ insert: param, ca-7_prm_4 }} {{ insert: param, ca-7_prm_5 }}." - } - ] - }, - { - "id": "ca-7_gdn", - "name": "guidance", - "prose": "Continuous monitoring at the system level facilitates ongoing awareness of the system security and privacy posture to support organizational risk management decisions. The terms \"continuous\" and \"ongoing\" imply that organizations assess and monitor their controls and risks at a frequency sufficient to support risk-based decisions. Different types of controls may require different monitoring frequencies. The results of continuous monitoring generate risk response actions by organizations. When monitoring the effectiveness of multiple controls that have been grouped into capabilities, a root-cause analysis may be needed to determine the specific control that has failed. Continuous monitoring programs allow organizations to maintain the authorizations of systems and common controls in highly dynamic environments of operation with changing mission and business needs, threats, vulnerabilities, and technologies. Having access to security and privacy information on a continuing basis through reports and dashboards gives organizational officials the ability to make effective and timely risk management decisions, including ongoing authorization decisions.\n\nAutomation supports more frequent updates to hardware, software, and firmware inventories, authorization packages, and other system information. Effectiveness is further enhanced when continuous monitoring outputs are formatted to provide information that is specific, measurable, actionable, relevant, and timely. Continuous monitoring activities are scaled in accordance with the security categories of systems. Monitoring requirements, including the need for specific monitoring, may be referenced in other controls and control enhancements, such as [AC-2g](#ac-2_smt.g), [AC-2(7)](#ac-2.7), [AC-2(12)(a)](#ac-2.12_smt.a), [AC-2(7)(b)](#ac-2.7_smt.b), [AC-2(7)(c)](#ac-2.7_smt.c), [AC-17(1)](#ac-17.1), [AT-4a](#at-4_smt.a), [AU-13](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-13), [AU-13(1)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-13.1), [AU-13(2)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-13.2), [CM-3f](#cm-3_smt.f), [CM-6d](#cm-6_smt.d), [CM-11c](#cm-11_smt.c), [IR-5](#ir-5), [MA-2b](#ma-2_smt.b), [MA-3a](#ma-3_smt.a), [MA-4a](#ma-4_smt.a), [PE-3d](#pe-3_smt.d), [PE-6](#pe-6), [PE-14b](#pe-14_smt.b), [PE-16](#pe-16), [PE-20](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pe-20), [PM-6](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-6), [PM-23](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-23), [PM-31](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-31), [PS-7e](#ps-7_smt.e), [SA-9c](#sa-9_smt.c), [SR-4](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sr-4), [SC-5(3)(b)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-5.3_smt.b), [SC-7a](#sc-7_smt.a), [SC-7(24)(b)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-7.24_smt.b), [SC-18b](#sc-18_smt.b), [SC-43b](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-43_smt.b) , and [SI-4](#si-4)." - }, - { - "id": "ca-7_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CA-7 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ca-7_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Operating System, Database, Web Application, Container, and Service Configuration Scans: at least monthly. All scans performed by Independent Assessor: at least annually." - }, - { - "id": "ca-7_fr_smt.2", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "CSOs with more than one agency ATO must implement a collaborative Continuous Monitoring (ConMon) approach described in the FedRAMP Guide for Multi-Agency Continuous Monitoring. This requirement applies to CSOs authorized via the Agency path as each agency customer is responsible for performing ConMon oversight." - }, - { - "id": "ca-7_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "FedRAMP does not provide a template for the Continuous Monitoring Plan. CSPs should reference the FedRAMP Continuous Monitoring Strategy Guide when developing the Continuous Monitoring Plan." - } - ] - }, - { - "id": "ca-7_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-07", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-7_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-07[01]", - "class": "sp800-53a" - } - ], - "prose": "a system-level continuous monitoring strategy is developed;", - "links": [ - { - "href": "#ca-7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-7_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-07[02]", - "class": "sp800-53a" - } - ], - "prose": "system-level continuous monitoring is implemented in accordance with the organization-level continuous monitoring strategy;", - "links": [ - { - "href": "#ca-7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-7_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-07a.", - "class": "sp800-53a" - } - ], - "prose": "system-level continuous monitoring includes establishment of the following system-level metrics to be monitored: {{ insert: param, ca-07_odp.01 }};", - "links": [ - { - "href": "#ca-7_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-7_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-07b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-7_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-07b.[01]", - "class": "sp800-53a" - } - ], - "prose": "system-level continuous monitoring includes established {{ insert: param, ca-07_odp.02 }} for monitoring;", - "links": [ - { - "href": "#ca-7_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-7_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-07b.[02]", - "class": "sp800-53a" - } - ], - "prose": "system-level continuous monitoring includes established {{ insert: param, ca-07_odp.03 }} for assessment of control effectiveness;", - "links": [ - { - "href": "#ca-7_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-7_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-7_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-07c.", - "class": "sp800-53a" - } - ], - "prose": "system-level continuous monitoring includes ongoing control assessments in accordance with the continuous monitoring strategy;", - "links": [ - { - "href": "#ca-7_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-7_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-07d.", - "class": "sp800-53a" - } - ], - "prose": "system-level continuous monitoring includes ongoing monitoring of system and organization-defined metrics in accordance with the continuous monitoring strategy;", - "links": [ - { - "href": "#ca-7_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-7_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-07e.", - "class": "sp800-53a" - } - ], - "prose": "system-level continuous monitoring includes correlation and analysis of information generated by control assessments and monitoring;", - "links": [ - { - "href": "#ca-7_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-7_obj.f", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-07f.", - "class": "sp800-53a" - } - ], - "prose": "system-level continuous monitoring includes response actions to address the results of the analysis of control assessment and monitoring information;", - "links": [ - { - "href": "#ca-7_smt.f", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-7_obj.g", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-07g.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-7_obj.g-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-07g.[01]", - "class": "sp800-53a" - } - ], - "prose": "system-level continuous monitoring includes reporting the security status of the system to {{ insert: param, ca-07_odp.04 }} {{ insert: param, ca-07_odp.05 }};", - "links": [ - { - "href": "#ca-7_smt.g", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-7_obj.g-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-07g.[02]", - "class": "sp800-53a" - } - ], - "prose": "system-level continuous monitoring includes reporting the privacy status of the system to {{ insert: param, ca-07_odp.06 }} {{ insert: param, ca-07_odp.07 }}.", - "links": [ - { - "href": "#ca-7_smt.g", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-7_smt.g", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-7_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CA-07-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Assessment, authorization, and monitoring policy\n\norganizational continuous monitoring strategy\n\nsystem-level continuous monitoring strategy\n\nprocedures addressing continuous monitoring of system controls\n\nprocedures addressing configuration management\n\ncontrol assessment report\n\nplan of action and milestones\n\nsystem monitoring records\n\nconfiguration management records\n\nimpact analyses\n\nstatus reports\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ca-7_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CA-07-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with continuous monitoring responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "ca-7_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CA-07-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing continuous monitoring\n\nmechanisms supporting response actions to address assessment and monitoring results\n\nmechanisms supporting security and privacy status reporting" - } - ] - } - ], - "controls": [ - { - "id": "ca-7.1", - "class": "SP800-53-enhancement", - "title": "Independent Assessment", - "props": [ - { - "name": "label", - "value": "CA-07(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CA-7(1)" - }, - { - "name": "label", - "value": "CA-07(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ca-07.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ca-7", - "rel": "required" - } - ], - "parts": [ - { - "id": "ca-7.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Employ independent assessors or assessment teams to monitor the controls in the system on an ongoing basis." - }, - { - "id": "ca-7.1_gdn", - "name": "guidance", - "prose": "Organizations maximize the value of control assessments by requiring that assessments be conducted by assessors with appropriate levels of independence. The level of required independence is based on organizational continuous monitoring strategies. Assessor independence provides a degree of impartiality to the monitoring process. To achieve such impartiality, assessors do not create a mutual or conflicting interest with the organizations where the assessments are being conducted, assess their own work, act as management or employees of the organizations they are serving, or place themselves in advocacy positions for the organizations acquiring their services." - }, - { - "id": "ca-7.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-07(01)", - "class": "sp800-53a" - } - ], - "prose": "independent assessors or assessment teams are employed to monitor the controls in the system on an ongoing basis.", - "links": [ - { - "href": "#ca-7.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-7.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CA-07(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Assessment, authorization, and monitoring policy\n\norganizational continuous monitoring strategy\n\nsystem-level continuous monitoring strategy\n\nprocedures addressing continuous monitoring of system controls\n\ncontrol assessment report\n\nplan of action and milestones\n\nsystem monitoring records\n\nimpact analyses\n\nstatus reports\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ca-7.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CA-07(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with continuous monitoring responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - }, - { - "id": "ca-7.4", - "class": "SP800-53-enhancement", - "title": "Risk Monitoring", - "props": [ - { - "name": "label", - "value": "CA-07(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CA-7(4)" - }, - { - "name": "label", - "value": "CA-07(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ca-07.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ca-7", - "rel": "required" - } - ], - "parts": [ - { - "id": "ca-7.4_smt", - "name": "statement", - "prose": "Ensure risk monitoring is an integral part of the continuous monitoring strategy that includes the following:", - "parts": [ - { - "id": "ca-7.4_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Effectiveness monitoring;" - }, - { - "id": "ca-7.4_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Compliance monitoring; and" - }, - { - "id": "ca-7.4_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Change monitoring." - } - ] - }, - { - "id": "ca-7.4_gdn", - "name": "guidance", - "prose": "Risk monitoring is informed by the established organizational risk tolerance. Effectiveness monitoring determines the ongoing effectiveness of the implemented risk response measures. Compliance monitoring verifies that required risk response measures are implemented. It also verifies that security and privacy requirements are satisfied. Change monitoring identifies changes to organizational systems and environments of operation that may affect security and privacy risk." - }, - { - "id": "ca-7.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-07(04)", - "class": "sp800-53a" - } - ], - "prose": "risk monitoring is an integral part of the continuous monitoring strategy;", - "parts": [ - { - "id": "ca-7.4_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-07(04)(a)", - "class": "sp800-53a" - } - ], - "prose": "effectiveness monitoring is included in risk monitoring;", - "links": [ - { - "href": "#ca-7.4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-7.4_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-07(04)(b)", - "class": "sp800-53a" - } - ], - "prose": "compliance monitoring is included in risk monitoring;", - "links": [ - { - "href": "#ca-7.4_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-7.4_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-07(04)(c)", - "class": "sp800-53a" - } - ], - "prose": "change monitoring is included in risk monitoring.", - "links": [ - { - "href": "#ca-7.4_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-7.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-7.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CA-07(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Assessment, authorization, and monitoring policy\n\norganizational continuous monitoring strategy\n\nsystem-level continuous monitoring strategy\n\nprocedures addressing continuous monitoring of system controls\n\nassessment report\n\nplan of action and milestones\n\nsystem monitoring records\n\nimpact analyses\n\nstatus reports\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ca-7.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CA-07(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with continuous monitoring responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "ca-7.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CA-07(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting risk monitoring" - } - ] - } - ] - } - ] - }, - { - "id": "ca-8", - "class": "SP800-53", - "title": "Penetration Testing", - "params": [ - { - "id": "ca-08_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ca-8_prm_1" - }, - { - "name": "label", - "value": "CA-08_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "frequency at which to conduct penetration testing on systems or system components is defined;" - } - ] - }, - { - "id": "ca-08_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ca-8_prm_2" - }, - { - "name": "alt-label", - "value": "systems or system components", - "class": "sp800-53" - }, - { - "name": "label", - "value": "CA-08_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "system(s) or system components", - "guidelines": [ - { - "prose": "systems or system components on which penetration testing is to be conducted are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CA-08", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CA-8" - }, - { - "name": "label", - "value": "CA-08", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ca-08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ra-10", - "rel": "related" - }, - { - "href": "#sa-11", - "rel": "related" - }, - { - "href": "#sr-5", - "rel": "related" - }, - { - "href": "#sr-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "ca-8_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Conduct penetration testing {{ insert: param, ca-08_odp.01 }} on {{ insert: param, ca-08_odp.02 }}." - }, - { - "id": "ca-8_gdn", - "name": "guidance", - "prose": "Penetration testing is a specialized type of assessment conducted on systems or individual system components to identify vulnerabilities that could be exploited by adversaries. Penetration testing goes beyond automated vulnerability scanning and is conducted by agents and teams with demonstrable skills and experience that include technical expertise in network, operating system, and/or application level security. Penetration testing can be used to validate vulnerabilities or determine the degree of penetration resistance of systems to adversaries within specified constraints. Such constraints include time, resources, and skills. Penetration testing attempts to duplicate the actions of adversaries and provides a more in-depth analysis of security- and privacy-related weaknesses or deficiencies. Penetration testing is especially important when organizations are transitioning from older technologies to newer technologies (e.g., transitioning from IPv4 to IPv6 network protocols).\n\nOrganizations can use the results of vulnerability analyses to support penetration testing activities. Penetration testing can be conducted internally or externally on the hardware, software, or firmware components of a system and can exercise both physical and technical controls. A standard method for penetration testing includes a pretest analysis based on full knowledge of the system, pretest identification of potential vulnerabilities based on the pretest analysis, and testing designed to determine the exploitability of vulnerabilities. All parties agree to the rules of engagement before commencing penetration testing scenarios. Organizations correlate the rules of engagement for the penetration tests with the tools, techniques, and procedures that are anticipated to be employed by adversaries. Penetration testing may result in the exposure of information that is protected by laws or regulations, to individuals conducting the testing. Rules of engagement, contracts, or other appropriate mechanisms can be used to communicate expectations for how to protect this information. Risk assessments guide the decisions on the level of independence required for the personnel conducting penetration testing." - }, - { - "id": "ca-8_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CA-8 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ca-8_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Reference the FedRAMP Penetration Test Guidance." - } - ] - }, - { - "id": "ca-8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-08", - "class": "sp800-53a" - } - ], - "prose": "penetration testing is conducted {{ insert: param, ca-08_odp.01 }} on {{ insert: param, ca-08_odp.02 }}.", - "links": [ - { - "href": "#ca-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CA-08-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Assessment, authorization, and monitoring policy\n\nprocedures addressing penetration testing\n\nassessment plan\n\npenetration test report\n\nassessment report\n\nassessment evidence\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ca-8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CA-08-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with control assessment responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "ca-8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CA-08-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting penetration testing" - } - ] - } - ], - "controls": [ - { - "id": "ca-8.1", - "class": "SP800-53-enhancement", - "title": "Independent Penetration Testing Agent or Team", - "props": [ - { - "name": "label", - "value": "CA-08(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CA-8(1)" - }, - { - "name": "label", - "value": "CA-08(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ca-08.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ca-8", - "rel": "required" - }, - { - "href": "#ca-2", - "rel": "related" - } - ], - "parts": [ - { - "id": "ca-8.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Employ an independent penetration testing agent or team to perform penetration testing on the system or system components." - }, - { - "id": "ca-8.1_gdn", - "name": "guidance", - "prose": "Independent penetration testing agents or teams are individuals or groups who conduct impartial penetration testing of organizational systems. Impartiality implies that penetration testing agents or teams are free from perceived or actual conflicts of interest with respect to the development, operation, or management of the systems that are the targets of the penetration testing. [CA-2(1)](#ca-2.1) provides additional information on independent assessments that can be applied to penetration testing." - }, - { - "id": "ca-8.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-08(01)", - "class": "sp800-53a" - } - ], - "prose": "an independent penetration testing agent or team is employed to perform penetration testing on the system or system components.", - "links": [ - { - "href": "#ca-8.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-8.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CA-08(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Assessment, authorization, and monitoring policy\n\nprocedures addressing penetration testing\n\nassessment plan\n\npenetration test report\n\nassessment report\n\nsecurity assessment evidence\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ca-8.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CA-08(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with assessment responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - }, - { - "id": "ca-8.2", - "class": "SP800-53-enhancement", - "title": "Red Team Exercises", - "params": [ - { - "id": "ca-08.02_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ca-8.2_prm_1" - }, - { - "name": "label", - "value": "CA-08(02)_ODP", - "class": "sp800-53a" - } - ], - "label": "red team exercises", - "guidelines": [ - { - "prose": "red team exercises to simulate attempts by adversaries to compromise organizational systems are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "CA-08(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CA-8(2)" - }, - { - "name": "label", - "value": "CA-08(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ca-08.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ca-8", - "rel": "required" - } - ], - "parts": [ - { - "id": "ca-8.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Employ the following red-team exercises to simulate attempts by adversaries to compromise organizational systems in accordance with applicable rules of engagement: {{ insert: param, ca-08.02_odp }}." - }, - { - "id": "ca-8.2_gdn", - "name": "guidance", - "prose": "Red team exercises extend the objectives of penetration testing by examining the security and privacy posture of organizations and the capability to implement effective cyber defenses. Red team exercises simulate attempts by adversaries to compromise mission and business functions and provide a comprehensive assessment of the security and privacy posture of systems and organizations. Such attempts may include technology-based attacks and social engineering-based attacks. Technology-based attacks include interactions with hardware, software, or firmware components and/or mission and business processes. Social engineering-based attacks include interactions via email, telephone, shoulder surfing, or personal conversations. Red team exercises are most effective when conducted by penetration testing agents and teams with knowledge of and experience with current adversarial tactics, techniques, procedures, and tools. While penetration testing may be primarily laboratory-based testing, organizations can use red team exercises to provide more comprehensive assessments that reflect real-world conditions. The results from red team exercises can be used by organizations to improve security and privacy awareness and training and to assess control effectiveness." - }, - { - "id": "ca-8.2_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CA-8(2) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ca-8.2_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "See the FedRAMP Documents page\\> Penetration Test Guidance\n\nhttps://www.FedRAMP.gov/documents/" - } - ] - }, - { - "id": "ca-8.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-08(02)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ca-08.02_odp }} are employed to simulate attempts by adversaries to compromise organizational systems in accordance with applicable rules of engagement.", - "links": [ - { - "href": "#ca-8.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-8.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CA-08(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Assessment, authorization, and monitoring policy\n\nprocedures addressing penetration testing\n\nprocedures addressing red team exercises\n\nassessment plan\n\nresults of red team exercises\n\npenetration test report\n\nassessment report\n\nrules of engagement\n\nassessment evidence\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ca-8.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CA-08(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with assessment responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "ca-8.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CA-08(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting the employment of red team exercises" - } - ] - } - ] - } - ] - }, - { - "id": "ca-9", - "class": "SP800-53", - "title": "Internal System Connections", - "params": [ - { - "id": "ca-09_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ca-9_prm_1" - }, - { - "name": "alt-label", - "value": "system components or classes of components", - "class": "sp800-53" - }, - { - "name": "label", - "value": "CA-09_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "system components", - "guidelines": [ - { - "prose": "system components or classes of components requiring internal connections to the system are defined;" - } - ] - }, - { - "id": "ca-09_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ca-9_prm_2" - }, - { - "name": "label", - "value": "CA-09_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "conditions", - "guidelines": [ - { - "prose": "conditions requiring termination of internal connections are defined;" - } - ] - }, - { - "id": "ca-09_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ca-9_prm_3" - }, - { - "name": "label", - "value": "CA-09_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "frequency at which to review the continued need for each internal connection is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CA-09", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CA-9" - }, - { - "name": "label", - "value": "CA-09", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ca-09" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#0f66be67-85e7-4ca6-bd19-39453e9f4394", - "rel": "reference" - }, - { - "href": "#4c501da5-9d79-4cb6-ba80-97260e1ce327", - "rel": "reference" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "ca-9_smt", - "name": "statement", - "parts": [ - { - "id": "ca-9_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Authorize internal connections of {{ insert: param, ca-09_odp.01 }} to the system;" - }, - { - "id": "ca-9_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Document, for each internal connection, the interface characteristics, security and privacy requirements, and the nature of the information communicated;" - }, - { - "id": "ca-9_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Terminate internal system connections after {{ insert: param, ca-09_odp.02 }} ; and" - }, - { - "id": "ca-9_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Review {{ insert: param, ca-09_odp.03 }} the continued need for each internal connection." - } - ] - }, - { - "id": "ca-9_gdn", - "name": "guidance", - "prose": "Internal system connections are connections between organizational systems and separate constituent system components (i.e., connections between components that are part of the same system) including components used for system development. Intra-system connections include connections with mobile devices, notebook and desktop computers, tablets, printers, copiers, facsimile machines, scanners, sensors, and servers. Instead of authorizing each internal system connection individually, organizations can authorize internal connections for a class of system components with common characteristics and/or configurations, including printers, scanners, and copiers with a specified processing, transmission, and storage capability or smart phones and tablets with a specific baseline configuration. The continued need for an internal system connection is reviewed from the perspective of whether it provides support for organizational missions or business functions." - }, - { - "id": "ca-9_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-09", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-9_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-09a.", - "class": "sp800-53a" - } - ], - "prose": "internal connections of {{ insert: param, ca-09_odp.01 }} to the system are authorized;", - "links": [ - { - "href": "#ca-9_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-9_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-09b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ca-9_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-09b.[01]", - "class": "sp800-53a" - } - ], - "prose": "for each internal connection, the interface characteristics are documented;", - "links": [ - { - "href": "#ca-9_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-9_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-09b.[02]", - "class": "sp800-53a" - } - ], - "prose": "for each internal connection, the security requirements are documented;", - "links": [ - { - "href": "#ca-9_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-9_obj.b-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-09b.[03]", - "class": "sp800-53a" - } - ], - "prose": "for each internal connection, the privacy requirements are documented;", - "links": [ - { - "href": "#ca-9_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-9_obj.b-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CA-09b.[04]", - "class": "sp800-53a" - } - ], - "prose": "for each internal connection, the nature of the information communicated is documented;", - "links": [ - { - "href": "#ca-9_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-9_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-9_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-09c.", - "class": "sp800-53a" - } - ], - "prose": "internal system connections are terminated after {{ insert: param, ca-09_odp.02 }};", - "links": [ - { - "href": "#ca-9_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-9_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CA-09d.", - "class": "sp800-53a" - } - ], - "prose": "the continued need for each internal connection is reviewed {{ insert: param, ca-09_odp.03 }}.", - "links": [ - { - "href": "#ca-9_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ca-9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ca-9_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CA-09-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Assessment, authorization, and monitoring policy\n\naccess control policy\n\nprocedures addressing system connections\n\nsystem and communications protection policy\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of components or classes of components authorized as internal system connections\n\nassessment report\n\nsystem audit records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ca-9_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CA-09-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for developing, implementing, or authorizing internal system connections\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "ca-9_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CA-09-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting internal system connections" - } - ] - } - ] - } - ] - }, - { - "id": "cm", - "class": "family", - "title": "Configuration Management", - "controls": [ - { - "id": "cm-1", - "class": "SP800-53", - "title": "Policy and Procedures", - "params": [ - { - "id": "cm-1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-01_odp.02" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "cm-01_odp.01", - "props": [ - { - "name": "label", - "value": "CM-01_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the configuration management policy is to be disseminated is/are defined;" - } - ] - }, - { - "id": "cm-01_odp.02", - "props": [ - { - "name": "label", - "value": "CM-01_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the configuration management procedures are to be disseminated is/are defined;" - } - ] - }, - { - "id": "cm-01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "cm-1_prm_2" - }, - { - "name": "label", - "value": "CM-01_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "organization-level", - "mission/business process-level", - "system-level" - ] - } - }, - { - "id": "cm-01_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "cm-1_prm_3" - }, - { - "name": "label", - "value": "CM-01_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "official", - "guidelines": [ - { - "prose": "an official to manage the configuration management policy and procedures is defined;" - } - ] - }, - { - "id": "cm-01_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "cm-1_prm_4" - }, - { - "name": "label", - "value": "CM-01_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current configuration management policy is reviewed and updated is defined;" - } - ] - }, - { - "id": "cm-01_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "cm-1_prm_5" - }, - { - "name": "label", - "value": "CM-01_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that would require the current configuration management policy to be reviewed and updated are defined;" - } - ] - }, - { - "id": "cm-01_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "cm-1_prm_6" - }, - { - "name": "label", - "value": "CM-01_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current configuration management procedures are reviewed and updated is defined;" - } - ] - }, - { - "id": "cm-01_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "cm-1_prm_7" - }, - { - "name": "label", - "value": "CM-01_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "events", - "constraints": [ - { - "description": "significant changes" - } - ], - "guidelines": [ - { - "prose": "events that would require configuration management procedures to be reviewed and updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CM-01", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-1" - }, - { - "name": "label", - "value": "CM-01", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#c7ac44e8-10db-4b64-b2b9-9e32ec1efed0", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#4c0ec2ee-a0d6-428a-9043-4504bc3ade6f", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-1_smt", - "name": "statement", - "parts": [ - { - "id": "cm-1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, a policy that addresses Configuration Management MUST be associated with CM-1 part a.", - "class": "policy" - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, at least one procedure that addresses Configuration Management MUST be associated with CM-1 part a.", - "class": "procedure" - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, document, and disseminate to {{ insert: param, cm-1_prm_1 }}:", - "parts": [ - { - "id": "cm-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, cm-01_odp.03 }} configuration management policy that:", - "parts": [ - { - "id": "cm-1_smt.a.1.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "cm-1_smt.a.1.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and" - } - ] - }, - { - "id": "cm-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the configuration management policy and the associated configuration management controls;" - } - ] - }, - { - "id": "cm-1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Designate an {{ insert: param, cm-01_odp.04 }} to manage the development, documentation, and dissemination of the configuration management policy and procedures; and" - }, - { - "id": "cm-1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the current configuration management:", - "parts": [ - { - "id": "cm-1_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Policy {{ insert: param, cm-01_odp.05 }} and following {{ insert: param, cm-01_odp.06 }} ; and" - }, - { - "id": "cm-1_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures {{ insert: param, cm-01_odp.07 }} and following {{ insert: param, cm-01_odp.08 }}." - } - ] - } - ] - }, - { - "id": "cm-1_gdn", - "name": "guidance", - "prose": "Configuration management policy and procedures address the controls in the CM family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of configuration management policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission/business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to configuration management policy and procedures include, but are not limited to, assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure." - }, - { - "id": "cm-1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-01a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-01a.[01]", - "class": "sp800-53a" - } - ], - "prose": "a configuration management policy is developed and documented;", - "links": [ - { - "href": "#cm-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-01a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the configuration management policy is disseminated to {{ insert: param, cm-01_odp.01 }};", - "links": [ - { - "href": "#cm-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-1_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-01a.[03]", - "class": "sp800-53a" - } - ], - "prose": "configuration management procedures to facilitate the implementation of the configuration management policy and associated configuration management controls are developed and documented;", - "links": [ - { - "href": "#cm-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-1_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-01a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the configuration management procedures are disseminated to {{ insert: param, cm-01_odp.02 }};", - "links": [ - { - "href": "#cm-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-1_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-01a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-1_obj.a.1.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-01a.01(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-1_obj.a.1.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-01a.01(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, cm-01_odp.03 }} of the configuration management policy addresses purpose;", - "links": [ - { - "href": "#cm-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-1_obj.a.1.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-01a.01(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, cm-01_odp.03 }} of the configuration management policy addresses scope;", - "links": [ - { - "href": "#cm-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-1_obj.a.1.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-01a.01(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, cm-01_odp.03 }} of the configuration management policy addresses roles;", - "links": [ - { - "href": "#cm-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-1_obj.a.1.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-01a.01(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, cm-01_odp.03 }} of the configuration management policy addresses responsibilities;", - "links": [ - { - "href": "#cm-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-1_obj.a.1.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-01a.01(a)[05]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, cm-01_odp.03 }} of the configuration management policy addresses management commitment;", - "links": [ - { - "href": "#cm-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-1_obj.a.1.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-01a.01(a)[06]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, cm-01_odp.03 }} of the configuration management policy addresses coordination among organizational entities;", - "links": [ - { - "href": "#cm-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-1_obj.a.1.a-7", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-01a.01(a)[07]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, cm-01_odp.03 }} of the configuration management policy addresses compliance;", - "links": [ - { - "href": "#cm-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-1_obj.a.1.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-01a.01(b)", - "class": "sp800-53a" - } - ], - "prose": "the configuration management policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines;", - "links": [ - { - "href": "#cm-1_smt.a.1.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-1_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-01b.", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, cm-01_odp.04 }} is designated to manage the development, documentation, and dissemination of the configuration management policy and procedures;", - "links": [ - { - "href": "#cm-1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-01c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-1_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-01c.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-1_obj.c.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-01c.01[01]", - "class": "sp800-53a" - } - ], - "prose": "the current configuration management policy is reviewed and updated {{ insert: param, cm-01_odp.05 }};", - "links": [ - { - "href": "#cm-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-1_obj.c.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-01c.01[02]", - "class": "sp800-53a" - } - ], - "prose": "the current configuration management policy is reviewed and updated following {{ insert: param, cm-01_odp.06 }};", - "links": [ - { - "href": "#cm-1_smt.c.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-1_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-01c.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-1_obj.c.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-01c.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the current configuration management procedures are reviewed and updated {{ insert: param, cm-01_odp.07 }};", - "links": [ - { - "href": "#cm-1_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-1_obj.c.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-01c.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the current configuration management procedures are reviewed and updated following {{ insert: param, cm-01_odp.08 }}.", - "links": [ - { - "href": "#cm-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-1_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-01-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy and procedures\n\nsecurity and privacy program policies and procedures\n\nassessment or audit findings\n\ndocumentation of security incidents or breaches\n\nsystem security plan\n\nprivacy plan\n\nrisk management strategy\n\nother relevant artifacts, documents, or records" - } - ] - }, - { - "id": "cm-1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-01-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with configuration management responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - }, - { - "id": "cm-2", - "class": "SP800-53", - "title": "Baseline Configuration", - "params": [ - { - "id": "cm-02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cm-2_prm_1" - }, - { - "name": "label", - "value": "CM-02_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually and when a significant change occurs" - } - ], - "guidelines": [ - { - "prose": "the frequency of baseline configuration review and update is defined;" - } - ] - }, - { - "id": "cm-02_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "cm-2_prm_2" - }, - { - "name": "label", - "value": "CM-02_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "circumstances", - "constraints": [ - { - "description": "to include when directed by the AO" - } - ], - "guidelines": [ - { - "prose": "the circumstances requiring baseline configuration review and update are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CM-02", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-2" - }, - { - "name": "label", - "value": "CM-02", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#0f66be67-85e7-4ca6-bd19-39453e9f4394", - "rel": "reference" - }, - { - "href": "#20db4e66-e257-450c-b2e4-2bb9a62a2c88", - "rel": "reference" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#ca-9", - "rel": "related" - }, - { - "href": "#cm-1", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#cm-9", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#cp-10", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#cp-12", - "rel": "related" - }, - { - "href": "#ma-2", - "rel": "related" - }, - { - "href": "#pl-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-5", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "#sc-18", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-2_smt", - "name": "statement", - "parts": [ - { - "id": "cm-2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, document, and maintain under configuration control, a current baseline configuration of the system; and" - }, - { - "id": "cm-2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Review and update the baseline configuration of the system:", - "parts": [ - { - "id": "cm-2_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, cm-02_odp.01 }};" - }, - { - "id": "cm-2_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "When required due to {{ insert: param, cm-02_odp.02 }} ; and" - }, - { - "id": "cm-2_smt.b.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "When system components are installed or upgraded." - } - ] - } - ] - }, - { - "id": "cm-2_gdn", - "name": "guidance", - "prose": "Baseline configurations for systems and system components include connectivity, operational, and communications aspects of systems. Baseline configurations are documented, formally reviewed, and agreed-upon specifications for systems or configuration items within those systems. Baseline configurations serve as a basis for future builds, releases, or changes to systems and include security and privacy control implementations, operational procedures, information about system components, network topology, and logical placement of components in the system architecture. Maintaining baseline configurations requires creating new baselines as organizational systems change over time. Baseline configurations of systems reflect the current enterprise architecture." - }, - { - "id": "cm-2_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CM-2 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "cm-2_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(b)(1) Guidance:" - } - ], - "prose": "Significant change is defined in NIST Special Publication 800-37 Revision 2, Appendix F." - } - ] - }, - { - "id": "cm-2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-02a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-2_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-02a.[01]", - "class": "sp800-53a" - } - ], - "prose": "a current baseline configuration of the system is developed and documented;", - "links": [ - { - "href": "#cm-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-2_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-02a.[02]", - "class": "sp800-53a" - } - ], - "prose": "a current baseline configuration of the system is maintained under configuration control;", - "links": [ - { - "href": "#cm-2_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-02b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-2_obj.b.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-02b.01", - "class": "sp800-53a" - } - ], - "prose": "the baseline configuration of the system is reviewed and updated {{ insert: param, cm-02_odp.01 }};", - "links": [ - { - "href": "#cm-2_smt.b.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-2_obj.b.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-02b.02", - "class": "sp800-53a" - } - ], - "prose": "the baseline configuration of the system is reviewed and updated when required due to {{ insert: param, cm-02_odp.02 }};", - "links": [ - { - "href": "#cm-2_smt.b.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-2_obj.b.3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-02b.03", - "class": "sp800-53a" - } - ], - "prose": "the baseline configuration of the system is reviewed and updated when system components are installed or upgraded.", - "links": [ - { - "href": "#cm-2_smt.b.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-2_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-02-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing the baseline configuration of the system\n\nconfiguration management plan\n\nenterprise architecture documentation\n\nsystem design documentation\n\nsystem security plan\n\nprivacy plan\n\nsystem architecture and configuration documentation\n\nsystem configuration settings and associated documentation\n\nsystem component inventory\n\nchange control records\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-02-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with configuration management responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "cm-2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-02-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for managing baseline configurations\n\nmechanisms supporting configuration control of the baseline configuration" - } - ] - } - ], - "controls": [ - { - "id": "cm-2.2", - "class": "SP800-53-enhancement", - "title": "Automation Support for Accuracy and Currency", - "params": [ - { - "id": "cm-02.02_odp", - "props": [ - { - "name": "alt-identifier", - "value": "cm-2.2_prm_1" - }, - { - "name": "label", - "value": "CM-02(02)_ODP", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms for maintaining baseline configuration of the system are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CM-02(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-2(2)" - }, - { - "name": "label", - "value": "CM-02(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-02.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#cm-2", - "rel": "required" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-2.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Maintain the currency, completeness, accuracy, and availability of the baseline configuration of the system using {{ insert: param, cm-02.02_odp }}." - }, - { - "id": "cm-2.2_gdn", - "name": "guidance", - "prose": "Automated mechanisms that help organizations maintain consistent baseline configurations for systems include configuration management tools, hardware, software, firmware inventory tools, and network management tools. Automated tools can be used at the organization level, mission and business process level, or system level on workstations, servers, notebook computers, network components, or mobile devices. Tools can be used to track version numbers on operating systems, applications, types of software installed, and current patch levels. Automation support for accuracy and currency can be satisfied by the implementation of [CM-8(2)](#cm-8.2) for organizations that combine system component inventory and baseline configuration activities." - }, - { - "id": "cm-2.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-02(02)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-2.2_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-02(02)[01]", - "class": "sp800-53a" - } - ], - "prose": "the currency of the baseline configuration of the system is maintained using {{ insert: param, cm-02.02_odp }};", - "links": [ - { - "href": "#cm-2.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-2.2_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-02(02)[02]", - "class": "sp800-53a" - } - ], - "prose": "the completeness of the baseline configuration of the system is maintained using {{ insert: param, cm-02.02_odp }};", - "links": [ - { - "href": "#cm-2.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-2.2_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-02(02)[03]", - "class": "sp800-53a" - } - ], - "prose": "the accuracy of the baseline configuration of the system is maintained using {{ insert: param, cm-02.02_odp }};", - "links": [ - { - "href": "#cm-2.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-2.2_obj-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-02(02)[04]", - "class": "sp800-53a" - } - ], - "prose": "the availability of the baseline configuration of the system is maintained using {{ insert: param, cm-02.02_odp }}.", - "links": [ - { - "href": "#cm-2.2_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-2.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-2.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-02(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing the baseline configuration of the system\n\nconfiguration management plan\n\nsystem design documentation\n\nsystem architecture and configuration documentation\n\nsystem configuration settings and associated documentation\n\nsystem component inventory\n\nconfiguration change control records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-2.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-02(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with configuration management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "cm-2.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-02(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for managing baseline configurations\n\nautomated mechanisms implementing baseline configuration maintenance" - } - ] - } - ] - }, - { - "id": "cm-2.3", - "class": "SP800-53-enhancement", - "title": "Retention of Previous Configurations", - "params": [ - { - "id": "cm-02.03_odp", - "props": [ - { - "name": "alt-identifier", - "value": "cm-2.3_prm_1" - }, - { - "name": "label", - "value": "CM-02(03)_ODP", - "class": "sp800-53a" - } - ], - "label": "number", - "constraints": [ - { - "description": "organization-defined number of previous versions of baseline configurations of the previously approved baseline configuration of IS components" - } - ], - "guidelines": [ - { - "prose": "the number of previous baseline configuration versions to be retained is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CM-02(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-2(3)" - }, - { - "name": "label", - "value": "CM-02(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-02.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#cm-2", - "rel": "required" - } - ], - "parts": [ - { - "id": "cm-2.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Retain {{ insert: param, cm-02.03_odp }} of previous versions of baseline configurations of the system to support rollback." - }, - { - "id": "cm-2.3_gdn", - "name": "guidance", - "prose": "Retaining previous versions of baseline configurations to support rollback include hardware, software, firmware, configuration files, configuration records, and associated documentation." - }, - { - "id": "cm-2.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-02(03)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-02.03_odp }} of previous baseline configuration version(s) of the system is/are retained to support rollback.", - "links": [ - { - "href": "#cm-2.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-2.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-02(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing the baseline configuration of the system\n\nconfiguration management plan\n\nsystem architecture and configuration documentation\n\nsystem configuration settings and associated documentation\n\ncopies of previous baseline configuration versions\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-2.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-02(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with configuration management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "cm-2.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-02(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for managing baseline configurations" - } - ] - } - ] - }, - { - "id": "cm-2.7", - "class": "SP800-53-enhancement", - "title": "Configure Systems and Components for High-risk Areas", - "params": [ - { - "id": "cm-02.07_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cm-2.7_prm_1" - }, - { - "name": "label", - "value": "CM-02(07)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "systems or system components", - "guidelines": [ - { - "prose": "the systems or system components to be issued when individuals travel to high-risk areas are defined;" - } - ] - }, - { - "id": "cm-02.07_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "cm-2.7_prm_2" - }, - { - "name": "label", - "value": "CM-02(07)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "configurations", - "guidelines": [ - { - "prose": "configurations for systems or system components to be issued when individuals travel to high-risk areas are defined;" - } - ] - }, - { - "id": "cm-02.07_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "cm-2.7_prm_3" - }, - { - "name": "label", - "value": "CM-02(07)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "controls", - "guidelines": [ - { - "prose": "the controls to be applied when the individuals return from travel are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CM-02(07)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-2(7)" - }, - { - "name": "label", - "value": "CM-02(07)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-02.07" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#cm-2", - "rel": "required" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-2.7_smt", - "name": "statement", - "parts": [ - { - "id": "cm-2.7_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Issue {{ insert: param, cm-02.07_odp.01 }} with {{ insert: param, cm-02.07_odp.02 }} to individuals traveling to locations that the organization deems to be of significant risk; and" - }, - { - "id": "cm-2.7_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Apply the following controls to the systems or components when the individuals return from travel: {{ insert: param, cm-02.07_odp.03 }}." - } - ] - }, - { - "id": "cm-2.7_gdn", - "name": "guidance", - "prose": "When it is known that systems or system components will be in high-risk areas external to the organization, additional controls may be implemented to counter the increased threat in such areas. For example, organizations can take actions for notebook computers used by individuals departing on and returning from travel. Actions include determining the locations that are of concern, defining the required configurations for the components, ensuring that components are configured as intended before travel is initiated, and applying controls to the components after travel is completed. Specially configured notebook computers include computers with sanitized hard drives, limited applications, and more stringent configuration settings. Controls applied to mobile devices upon return from travel include examining the mobile device for signs of physical tampering and purging and reimaging disk drives. Protecting information that resides on mobile devices is addressed in the [MP](#mp) (Media Protection) family." - }, - { - "id": "cm-2.7_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-02(07)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-2.7_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-02(07)(a)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-02.07_odp.01 }} with {{ insert: param, cm-02.07_odp.02 }} are issued to individuals traveling to locations that the organization deems to be of significant risk;", - "links": [ - { - "href": "#cm-2.7_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-2.7_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-02(07)(b)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-02.07_odp.03 }} are applied to the systems or system components when the individuals return from travel.", - "links": [ - { - "href": "#cm-2.7_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-2.7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-2.7_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-02(07)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nconfiguration management plan\n\nprocedures addressing the baseline configuration of the system\n\nprocedures addressing system component installations and upgrades\n\nsystem architecture and configuration documentation\n\nsystem configuration settings and associated documentation\n\nsystem component inventory\n\nrecords of system baseline configuration reviews and updates\n\nsystem component installations/upgrades and associated records\n\nchange control records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-2.7_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-02(07)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with configuration management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "cm-2.7_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-02(07)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for managing baseline configurations" - } - ] - } - ] - } - ] - }, - { - "id": "cm-3", - "class": "SP800-53", - "title": "Configuration Change Control", - "params": [ - { - "id": "cm-03_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cm-3_prm_1" - }, - { - "name": "label", - "value": "CM-03_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "time period", - "guidelines": [ - { - "prose": "the time period to retain records of configuration-controlled changes is defined;" - } - ] - }, - { - "id": "cm-03_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "cm-3_prm_2" - }, - { - "name": "label", - "value": "CM-03_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "configuration change control element", - "guidelines": [ - { - "prose": "the configuration change control element responsible for coordinating and overseeing change control activities is defined;" - } - ] - }, - { - "id": "cm-03_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "cm-3_prm_3" - }, - { - "name": "label", - "value": "CM-03_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "{{ insert: param, cm-03_odp.04 }}", - "when {{ insert: param, cm-03_odp.05 }}" - ] - } - }, - { - "id": "cm-03_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "cm-3_prm_4" - }, - { - "name": "label", - "value": "CM-03_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "guidelines": [ - { - "prose": "the frequency at which the configuration control element convenes is defined (if selected);" - } - ] - }, - { - "id": "cm-03_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "cm-3_prm_5" - }, - { - "name": "label", - "value": "CM-03_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "configuration change conditions", - "guidelines": [ - { - "prose": "configuration change conditions that prompt the configuration control element to convene are defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CM-03", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-3" - }, - { - "name": "label", - "value": "CM-03", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#0f66be67-85e7-4ca6-bd19-39453e9f4394", - "rel": "reference" - }, - { - "href": "#20db4e66-e257-450c-b2e4-2bb9a62a2c88", - "rel": "reference" - }, - { - "href": "#98d415ca-7281-4064-9931-0c366637e324", - "rel": "reference" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-9", - "rel": "related" - }, - { - "href": "#cm-11", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ma-2", - "rel": "related" - }, - { - "href": "#pe-16", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-6", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ra-8", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - }, - { - "href": "#sc-28", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-34", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-37", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - }, - { - "href": "#si-10", - "rel": "related" - }, - { - "href": "#sr-11", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-3_smt", - "name": "statement", - "parts": [ - { - "id": "cm-3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Determine and document the types of changes to the system that are configuration-controlled;" - }, - { - "id": "cm-3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Review proposed configuration-controlled changes to the system and approve or disapprove such changes with explicit consideration for security and privacy impact analyses;" - }, - { - "id": "cm-3_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Document configuration change decisions associated with the system;" - }, - { - "id": "cm-3_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Implement approved configuration-controlled changes to the system;" - }, - { - "id": "cm-3_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Retain records of configuration-controlled changes to the system for {{ insert: param, cm-03_odp.01 }};" - }, - { - "id": "cm-3_smt.f", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "f." - } - ], - "prose": "Monitor and review activities associated with configuration-controlled changes to the system; and" - }, - { - "id": "cm-3_smt.g", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "g." - } - ], - "prose": "Coordinate and provide oversight for configuration change control activities through {{ insert: param, cm-03_odp.02 }} that convenes {{ insert: param, cm-03_odp.03 }}." - } - ] - }, - { - "id": "cm-3_gdn", - "name": "guidance", - "prose": "Configuration change control for organizational systems involves the systematic proposal, justification, implementation, testing, review, and disposition of system changes, including system upgrades and modifications. Configuration change control includes changes to baseline configurations, configuration items of systems, operational procedures, configuration settings for system components, remediate vulnerabilities, and unscheduled or unauthorized changes. Processes for managing configuration changes to systems include Configuration Control Boards or Change Advisory Boards that review and approve proposed changes. For changes that impact privacy risk, the senior agency official for privacy updates privacy impact assessments and system of records notices. For new systems or major upgrades, organizations consider including representatives from the development organizations on the Configuration Control Boards or Change Advisory Boards. Auditing of changes includes activities before and after changes are made to systems and the auditing activities required to implement such changes. See also [SA-10](#sa-10)." - }, - { - "id": "cm-3_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CM-3 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "cm-3_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "The service provider establishes a central means of communicating major changes to or developments in the information system or environment of operations that may affect its services to the federal government and associated service consumers (e.g., electronic bulletin board, web status page). The means of communication are approved and accepted by the AO." - }, - { - "id": "cm-3_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(e) Guidance:" - } - ], - "prose": "In accordance with record retention policies and procedures." - } - ] - }, - { - "id": "cm-3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-03a.", - "class": "sp800-53a" - } - ], - "prose": "the types of changes to the system that are configuration-controlled are determined and documented;", - "links": [ - { - "href": "#cm-3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-03b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-3_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-03b.[01]", - "class": "sp800-53a" - } - ], - "prose": "proposed configuration-controlled changes to the system are reviewed;", - "links": [ - { - "href": "#cm-3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-03b.[02]", - "class": "sp800-53a" - } - ], - "prose": "proposed configuration-controlled changes to the system are approved or disapproved with explicit consideration for security and privacy impact analyses;", - "links": [ - { - "href": "#cm-3_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-03c.", - "class": "sp800-53a" - } - ], - "prose": "configuration change decisions associated with the system are documented;", - "links": [ - { - "href": "#cm-3_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-03d.", - "class": "sp800-53a" - } - ], - "prose": "approved configuration-controlled changes to the system are implemented;", - "links": [ - { - "href": "#cm-3_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-03e.", - "class": "sp800-53a" - } - ], - "prose": "records of configuration-controlled changes to the system are retained for {{ insert: param, cm-03_odp.01 }};", - "links": [ - { - "href": "#cm-3_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3_obj.f", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-03f.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-3_obj.f-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-03f.[01]", - "class": "sp800-53a" - } - ], - "prose": "activities associated with configuration-controlled changes to the system are monitored;", - "links": [ - { - "href": "#cm-3_smt.f", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3_obj.f-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-03f.[02]", - "class": "sp800-53a" - } - ], - "prose": "activities associated with configuration-controlled changes to the system are reviewed;", - "links": [ - { - "href": "#cm-3_smt.f", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-3_smt.f", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3_obj.g", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-03g.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-3_obj.g-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-03g.[01]", - "class": "sp800-53a" - } - ], - "prose": "configuration change control activities are coordinated and overseen by {{ insert: param, cm-03_odp.02 }};", - "links": [ - { - "href": "#cm-3_smt.g", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3_obj.g-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-03g.[02]", - "class": "sp800-53a" - } - ], - "prose": "the configuration control element convenes {{ insert: param, cm-03_odp.03 }}.", - "links": [ - { - "href": "#cm-3_smt.g", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-3_smt.g", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-03-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing system configuration change control\n\nconfiguration management plan\n\nsystem architecture and configuration documentation\n\nchange control records\n\nsystem audit records\n\nchange control audit and review reports\n\nagenda/minutes/documentation from configuration change control oversight meetings\n\nsystem security plan\n\nprivacy plan\n\nprivacy impact assessments\n\nsystem of records notices\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-03-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with configuration change control responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\nmembers of change control board or similar" - } - ] - }, - { - "id": "cm-3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-03-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for configuration change control\n\nmechanisms that implement configuration change control" - } - ] - } - ], - "controls": [ - { - "id": "cm-3.1", - "class": "SP800-53-enhancement", - "title": "Automated Documentation, Notification, and Prohibition of Changes", - "params": [ - { - "id": "cm-03.01_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cm-3.1_prm_1" - }, - { - "name": "label", - "value": "CM-03(01)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "mechanisms used to automate configuration change control are defined;" - } - ] - }, - { - "id": "cm-03.01_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "cm-3.1_prm_2" - }, - { - "name": "label", - "value": "CM-03(01)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "approval authorities", - "guidelines": [ - { - "prose": "approval authorities to be notified of and request approval for proposed changes to the system are defined;" - } - ] - }, - { - "id": "cm-03.01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "cm-3.1_prm_3" - }, - { - "name": "label", - "value": "CM-03(01)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "organization agreed upon time period" - } - ], - "guidelines": [ - { - "prose": "the time period after which to highlight changes that have not been approved or disapproved is defined;" - } - ] - }, - { - "id": "cm-03.01_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "cm-3.1_prm_4" - }, - { - "name": "label", - "value": "CM-03(01)_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "personnel", - "constraints": [ - { - "description": "organization defined configuration management approval authorities" - } - ], - "guidelines": [ - { - "prose": "personnel to be notified when approved changes are complete is/are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CM-03(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-3(1)" - }, - { - "name": "label", - "value": "CM-03(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-03.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#cm-3", - "rel": "required" - } - ], - "parts": [ - { - "id": "cm-3.1_smt", - "name": "statement", - "prose": "Use {{ insert: param, cm-03.01_odp.01 }} to:", - "parts": [ - { - "id": "cm-3.1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Document proposed changes to the system;" - }, - { - "id": "cm-3.1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Notify {{ insert: param, cm-03.01_odp.02 }} of proposed changes to the system and request change approval;" - }, - { - "id": "cm-3.1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Highlight proposed changes to the system that have not been approved or disapproved within {{ insert: param, cm-03.01_odp.03 }};" - }, - { - "id": "cm-3.1_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(d)" - } - ], - "prose": "Prohibit changes to the system until designated approvals are received;" - }, - { - "id": "cm-3.1_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(e)" - } - ], - "prose": "Document all changes to the system; and" - }, - { - "id": "cm-3.1_smt.f", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(f)" - } - ], - "prose": "Notify {{ insert: param, cm-03.01_odp.04 }} when approved changes to the system are completed." - } - ] - }, - { - "id": "cm-3.1_gdn", - "name": "guidance", - "prose": "None." - }, - { - "id": "cm-3.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-03(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-3.1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-03(01)(a)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-03.01_odp.01 }} are used to document proposed changes to the system;", - "links": [ - { - "href": "#cm-3.1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3.1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-03(01)(b)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-03.01_odp.01 }} are used to notify {{ insert: param, cm-03.01_odp.02 }} of proposed changes to the system and request change approval;", - "links": [ - { - "href": "#cm-3.1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3.1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-03(01)(c)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-03.01_odp.01 }} are used to highlight proposed changes to the system that have not been approved or disapproved within {{ insert: param, cm-03.01_odp.03 }};", - "links": [ - { - "href": "#cm-3.1_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3.1_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-03(01)(d)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-03.01_odp.01 }} are used to prohibit changes to the system until designated approvals are received;", - "links": [ - { - "href": "#cm-3.1_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3.1_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-03(01)(e)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-03.01_odp.01 }} are used to document all changes to the system;", - "links": [ - { - "href": "#cm-3.1_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3.1_obj.f", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-03(01)(f)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-03.01_odp.01 }} are used to notify {{ insert: param, cm-03.01_odp.04 }} when approved changes to the system are completed.", - "links": [ - { - "href": "#cm-3.1_smt.f", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-3.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-03(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing system configuration change control\n\nconfiguration management plan\n\nsystem design documentation\n\nsystem architecture and configuration documentation\n\nautomated configuration control mechanisms\n\nsystem configuration settings and associated documentation\n\nchange control records\n\nsystem audit records\n\nchange approval requests\n\nchange approvals\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-3.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-03(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with configuration change control responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers\n\nmembers of change control board or similar" - } - ] - }, - { - "id": "cm-3.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-03(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for configuration change control\n\nautomated mechanisms implementing configuration change control activities" - } - ] - } - ] - }, - { - "id": "cm-3.2", - "class": "SP800-53-enhancement", - "title": "Testing, Validation, and Documentation of Changes", - "props": [ - { - "name": "label", - "value": "CM-03(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-3(2)" - }, - { - "name": "label", - "value": "CM-03(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-03.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#cm-3", - "rel": "required" - } - ], - "parts": [ - { - "id": "cm-3.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Test, validate, and document changes to the system before finalizing the implementation of the changes." - }, - { - "id": "cm-3.2_gdn", - "name": "guidance", - "prose": "Changes to systems include modifications to hardware, software, or firmware components and configuration settings defined in [CM-6](#cm-6) . Organizations ensure that testing does not interfere with system operations that support organizational mission and business functions. Individuals or groups conducting tests understand security and privacy policies and procedures, system security and privacy policies and procedures, and the health, safety, and environmental risks associated with specific facilities or processes. Operational systems may need to be taken offline, or replicated to the extent feasible, before testing can be conducted. If systems must be taken offline for testing, the tests are scheduled to occur during planned system outages whenever possible. If the testing cannot be conducted on operational systems, organizations employ compensating controls." - }, - { - "id": "cm-3.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-03(02)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-3.2_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-03(02)[01]", - "class": "sp800-53a" - } - ], - "prose": "changes to the system are tested before finalizing the implementation of the changes;", - "links": [ - { - "href": "#cm-3.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3.2_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-03(02)[02]", - "class": "sp800-53a" - } - ], - "prose": "changes to the system are validated before finalizing the implementation of the changes;", - "links": [ - { - "href": "#cm-3.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3.2_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-03(02)[03]", - "class": "sp800-53a" - } - ], - "prose": "changes to the system are documented before finalizing the implementation of the changes.", - "links": [ - { - "href": "#cm-3.2_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-3.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-03(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nconfiguration management plan\n\nprocedures addressing system configuration change control\n\nsystem design documentation\n\nsystem architecture and configuration documentation\n\nsystem configuration settings and associated documentation\n\ntest records\n\nvalidation records\n\nchange control records\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-3.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-03(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with configuration change control responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers\n\nmembers of change control board or similar" - } - ] - }, - { - "id": "cm-3.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-03(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for configuration change control\n\nmechanisms supporting and/or implementing, testing, validating, and documenting system changes" - } - ] - } - ] - }, - { - "id": "cm-3.4", - "class": "SP800-53-enhancement", - "title": "Security and Privacy Representatives", - "params": [ - { - "id": "cm-3.4_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-03.04_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-03.04_odp.02" - } - ], - "label": "organization-defined security and privacy representatives" - }, - { - "id": "cm-03.04_odp.01", - "props": [ - { - "name": "label", - "value": "CM-03(04)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "security representatives", - "guidelines": [ - { - "prose": "security representatives required to be members of the change control element are defined;" - } - ] - }, - { - "id": "cm-03.04_odp.02", - "props": [ - { - "name": "label", - "value": "CM-03(04)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "privacy representatives", - "guidelines": [ - { - "prose": "privacy representatives required to be members of the change control element are defined;" - } - ] - }, - { - "id": "cm-03.04_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "cm-3.4_prm_2" - }, - { - "name": "label", - "value": "CM-03(04)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "configuration change control element", - "constraints": [ - { - "description": "Configuration control board (CCB) or similar (as defined in CM-3)" - } - ], - "guidelines": [ - { - "prose": "the configuration change control element of which the security and privacy representatives are to be members is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CM-03(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-3(4)" - }, - { - "name": "label", - "value": "CM-03(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-03.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cm-3", - "rel": "required" - } - ], - "parts": [ - { - "id": "cm-3.4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Require {{ insert: param, cm-3.4_prm_1 }} to be members of the {{ insert: param, cm-03.04_odp.03 }}." - }, - { - "id": "cm-3.4_gdn", - "name": "guidance", - "prose": "Information security and privacy representatives include system security officers, senior agency information security officers, senior agency officials for privacy, or system privacy officers. Representation by personnel with information security and privacy expertise is important because changes to system configurations can have unintended side effects, some of which may be security- or privacy-relevant. Detecting such changes early in the process can help avoid unintended, negative consequences that could ultimately affect the security and privacy posture of systems. The configuration change control element referred to in the second organization-defined parameter reflects the change control elements defined by organizations in [CM-3g](#cm-3_smt.g)." - }, - { - "id": "cm-3.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-03(04)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-3.4_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-03(04)[01]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-03.04_odp.01 }} are required to be members of the {{ insert: param, cm-03.04_odp.03 }};", - "links": [ - { - "href": "#cm-3.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3.4_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-03(04)[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-03.04_odp.02 }} are required to be members of the {{ insert: param, cm-03.04_odp.03 }}.", - "links": [ - { - "href": "#cm-3.4_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-3.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-03(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing system configuration change control\n\nconfiguration management plan\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-3.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-03(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with configuration change control responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nmembers of change control board or similar" - } - ] - }, - { - "id": "cm-3.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-03(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for configuration change control" - } - ] - } - ] - }, - { - "id": "cm-3.6", - "class": "SP800-53-enhancement", - "title": "Cryptography Management", - "params": [ - { - "id": "cm-03.06_odp", - "props": [ - { - "name": "alt-identifier", - "value": "cm-3.6_prm_1" - }, - { - "name": "label", - "value": "CM-03(06)_ODP", - "class": "sp800-53a" - } - ], - "label": "controls", - "constraints": [ - { - "description": "All security safeguards that rely on cryptography" - } - ], - "guidelines": [ - { - "prose": "controls provided by cryptographic mechanisms that are to be under configuration management are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CM-03(06)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-3(6)" - }, - { - "name": "label", - "value": "CM-03(06)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-03.06" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cm-3", - "rel": "required" - }, - { - "href": "#sc-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-3.6_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Ensure that cryptographic mechanisms used to provide the following controls are under configuration management: {{ insert: param, cm-03.06_odp }}." - }, - { - "id": "cm-3.6_gdn", - "name": "guidance", - "prose": "The controls referenced in the control enhancement refer to security and privacy controls from the control catalog. Regardless of the cryptographic mechanisms employed, processes and procedures are in place to manage those mechanisms. For example, if system components use certificates for identification and authentication, a process is implemented to address the expiration of those certificates." - }, - { - "id": "cm-3.6_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-03(06)", - "class": "sp800-53a" - } - ], - "prose": "cryptographic mechanisms used to provide {{ insert: param, cm-03.06_odp }} are under configuration management.", - "links": [ - { - "href": "#cm-3.6_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-3.6_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-03(06)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing system configuration change control\n\nconfiguration management plan\n\nsystem design documentation\n\nsystem architecture and configuration documentation\n\nsystem configuration settings and associated documentation\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-3.6_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-03(06)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with configuration change control responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers\n\nmembers of change control board or similar" - } - ] - }, - { - "id": "cm-3.6_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-03(06)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for configuration change control\n\ncryptographic mechanisms implementing organizational security safeguards (controls)" - } - ] - } - ] - } - ] - }, - { - "id": "cm-4", - "class": "SP800-53", - "title": "Impact Analyses", - "props": [ - { - "name": "label", - "value": "CM-04", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-4" - }, - { - "name": "label", - "value": "CM-04", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#20db4e66-e257-450c-b2e4-2bb9a62a2c88", - "rel": "reference" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#cm-9", - "rel": "related" - }, - { - "href": "#ma-2", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ra-8", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Analyze changes to the system to determine potential security and privacy impacts prior to change implementation." - }, - { - "id": "cm-4_gdn", - "name": "guidance", - "prose": "Organizational personnel with security or privacy responsibilities conduct impact analyses. Individuals conducting impact analyses possess the necessary skills and technical expertise to analyze the changes to systems as well as the security or privacy ramifications. Impact analyses include reviewing security and privacy plans, policies, and procedures to understand control requirements; reviewing system design documentation and operational procedures to understand control implementation and how specific system changes might affect the controls; reviewing the impact of changes on organizational supply chain partners with stakeholders; and determining how potential changes to a system create new risks to the privacy of individuals and the ability of implemented controls to mitigate those risks. Impact analyses also include risk assessments to understand the impact of the changes and determine if additional controls are required." - }, - { - "id": "cm-4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-04", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-4_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-04[01]", - "class": "sp800-53a" - } - ], - "prose": "changes to the system are analyzed to determine potential security impacts prior to change implementation;", - "links": [ - { - "href": "#cm-4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-4_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-04[02]", - "class": "sp800-53a" - } - ], - "prose": "changes to the system are analyzed to determine potential privacy impacts prior to change implementation.", - "links": [ - { - "href": "#cm-4_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-04-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing security impact analyses for changes to the system\n\nprocedures addressing privacy impact analyses for changes to the system\n\nconfiguration management plan\n\nsecurity impact analysis documentation\n\nprivacy impact analysis documentation\n\nprivacy impact assessment\n\nprivacy risk assessment documentation, system design documentation\n\nanalysis tools and associated outputs\n\nchange control records\n\nsystem audit records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-04-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibility for conducting security impact analyses\n\norganizational personnel with responsibility for conducting privacy impact analyses\n\norganizational personnel with information security and privacy responsibilities\n\nsystem developer\n\nsystem/network administrators\n\nmembers of change control board or similar" - } - ] - }, - { - "id": "cm-4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-04-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for security impact analyses\n\norganizational processes for privacy impact analyses" - } - ] - } - ], - "controls": [ - { - "id": "cm-4.1", - "class": "SP800-53-enhancement", - "title": "Separate Test Environments", - "props": [ - { - "name": "label", - "value": "CM-04(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-4(1)" - }, - { - "name": "label", - "value": "CM-04(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-04.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#cm-4", - "rel": "required" - }, - { - "href": "#sa-11", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-4.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Analyze changes to the system in a separate test environment before implementation in an operational environment, looking for security and privacy impacts due to flaws, weaknesses, incompatibility, or intentional malice." - }, - { - "id": "cm-4.1_gdn", - "name": "guidance", - "prose": "A separate test environment requires an environment that is physically or logically separate and distinct from the operational environment. The separation is sufficient to ensure that activities in the test environment do not impact activities in the operational environment and that information in the operational environment is not inadvertently transmitted to the test environment. Separate environments can be achieved by physical or logical means. If physically separate test environments are not implemented, organizations determine the strength of mechanism required when implementing logical separation." - }, - { - "id": "cm-4.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-04(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-4.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-04(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "changes to the system are analyzed in a separate test environment before implementation in an operational environment;", - "links": [ - { - "href": "#cm-4.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-4.1_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-04(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "changes to the system are analyzed for security impacts due to flaws;", - "links": [ - { - "href": "#cm-4.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-4.1_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-04(01)[03]", - "class": "sp800-53a" - } - ], - "prose": "changes to the system are analyzed for privacy impacts due to flaws;", - "links": [ - { - "href": "#cm-4.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-4.1_obj-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-04(01)[04]", - "class": "sp800-53a" - } - ], - "prose": "changes to the system are analyzed for security impacts due to weaknesses;", - "links": [ - { - "href": "#cm-4.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-4.1_obj-5", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-04(01)[05]", - "class": "sp800-53a" - } - ], - "prose": "changes to the system are analyzed for privacy impacts due to weaknesses;", - "links": [ - { - "href": "#cm-4.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-4.1_obj-6", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-04(01)[06]", - "class": "sp800-53a" - } - ], - "prose": "changes to the system are analyzed for security impacts due to incompatibility;", - "links": [ - { - "href": "#cm-4.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-4.1_obj-7", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-04(01)[07]", - "class": "sp800-53a" - } - ], - "prose": "changes to the system are analyzed for privacy impacts due to incompatibility;", - "links": [ - { - "href": "#cm-4.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-4.1_obj-8", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-04(01)[08]", - "class": "sp800-53a" - } - ], - "prose": "changes to the system are analyzed for security impacts due to intentional malice;", - "links": [ - { - "href": "#cm-4.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-4.1_obj-9", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-04(01)[09]", - "class": "sp800-53a" - } - ], - "prose": "changes to the system are analyzed for privacy impacts due to intentional malice.", - "links": [ - { - "href": "#cm-4.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-4.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-4.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-04(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing security impact analyses for changes to the system\n\nprocedures addressing privacy impact analyses for changes to the system\n\nconfiguration management plan\n\nsecurity impact analysis documentation\n\nprivacy impact analysis documentation\n\nprivacy impact assessment\n\nprivacy risk assessment documentation\n\nanalysis tools and associated outputs system design documentation\n\nsystem architecture and configuration documentation\n\nchange control records\n\nprocedures addressing the authority to test with PII\n\nsystem audit records\n\ndocumentation of separate test and operational environments\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-4.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-04(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibility for conducting security and privacy impact analyses\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\nmembers of change control board or similar" - } - ] - }, - { - "id": "cm-4.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-04(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for security and privacy impact analyses\n\nmechanisms supporting and/or implementing security and privacy impact analyses of changes" - } - ] - } - ] - }, - { - "id": "cm-4.2", - "class": "SP800-53-enhancement", - "title": "Verification of Controls", - "props": [ - { - "name": "label", - "value": "CM-04(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-4(2)" - }, - { - "name": "label", - "value": "CM-04(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-04.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#cm-4", - "rel": "required" - }, - { - "href": "#sa-11", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - }, - { - "href": "#si-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-4.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "After system changes, verify that the impacted controls are implemented correctly, operating as intended, and producing the desired outcome with regard to meeting the security and privacy requirements for the system." - }, - { - "id": "cm-4.2_gdn", - "name": "guidance", - "prose": "Implementation in this context refers to installing changed code in the operational system that may have an impact on security or privacy controls." - }, - { - "id": "cm-4.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-04(02)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-4.2_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-04(02)[01]", - "class": "sp800-53a" - } - ], - "prose": "the impacted controls are implemented correctly with regard to meeting the security requirements for the system after system changes;", - "links": [ - { - "href": "#cm-4.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-4.2_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-04(02)[02]", - "class": "sp800-53a" - } - ], - "prose": "the impacted controls are implemented correctly with regard to meeting the privacy requirements for the system after system changes;", - "links": [ - { - "href": "#cm-4.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-4.2_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-04(02)[03]", - "class": "sp800-53a" - } - ], - "prose": "the impacted controls are operating as intended with regard to meeting the security requirements for the system after system changes;", - "links": [ - { - "href": "#cm-4.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-4.2_obj-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-04(02)[04]", - "class": "sp800-53a" - } - ], - "prose": "the impacted controls are operating as intended with regard to meeting the privacy requirements for the system after system changes;", - "links": [ - { - "href": "#cm-4.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-4.2_obj-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-04(02)[05]", - "class": "sp800-53a" - } - ], - "prose": "the impacted controls are producing the desired outcome with regard to meeting the security requirements for the system after system changes;", - "links": [ - { - "href": "#cm-4.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-4.2_obj-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-04(02)[06]", - "class": "sp800-53a" - } - ], - "prose": "the impacted controls are producing the desired outcome with regard to meeting the privacy requirements for the system after system changes.", - "links": [ - { - "href": "#cm-4.2_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-4.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-4.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-04(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing security impact analyses for changes to the system\n\nprocedures addressing privacy impact analyses for changes to the system\n\nprivacy risk assessment documentation\n\nconfiguration management plan\n\nsecurity and privacy impact analysis documentation\n\nprivacy impact assessment\n\nanalysis tools and associated outputs\n\nchange control records\n\ncontrol assessment results\n\nsystem audit records\n\nsystem component inventory\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-4.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-04(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibility for conducting security and privacy impact analyses\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\nsecurity and privacy assessors" - } - ] - }, - { - "id": "cm-4.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-04(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for security and privacy impact analyses\n\nmechanisms supporting and/or implementing security and privacy impact analyses of changes" - } - ] - } - ] - } - ] - }, - { - "id": "cm-5", - "class": "SP800-53", - "title": "Access Restrictions for Change", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "CM-05", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-5" - }, - { - "name": "label", - "value": "CM-05", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#678e3d6c-150b-4393-aec5-6e3481eb1e00", - "rel": "reference" - }, - { - "href": "#7c37a38d-21d7-40d8-bc3d-b5e27eac17e1", - "rel": "reference" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-5", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#cm-9", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#sc-28", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-34", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-37", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - }, - { - "href": "#si-10", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-5_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Define, document, approve, and enforce physical and logical access restrictions associated with changes to the system." - }, - { - "id": "cm-5_gdn", - "name": "guidance", - "prose": "Changes to the hardware, software, or firmware components of systems or the operational procedures related to the system can potentially have significant effects on the security of the systems or individuals’ privacy. Therefore, organizations permit only qualified and authorized individuals to access systems for purposes of initiating changes. Access restrictions include physical and logical access controls (see [AC-3](#ac-3) and [PE-3](#pe-3) ), software libraries, workflow automation, media libraries, abstract layers (i.e., changes implemented into external interfaces rather than directly into systems), and change windows (i.e., changes occur only during specified times)." - }, - { - "id": "cm-5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-05", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-5_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-05[01]", - "class": "sp800-53a" - } - ], - "prose": "physical access restrictions associated with changes to the system are defined and documented;", - "links": [ - { - "href": "#cm-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-5_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-05[02]", - "class": "sp800-53a" - } - ], - "prose": "physical access restrictions associated with changes to the system are approved;", - "links": [ - { - "href": "#cm-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-5_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-05[03]", - "class": "sp800-53a" - } - ], - "prose": "physical access restrictions associated with changes to the system are enforced;", - "links": [ - { - "href": "#cm-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-5_obj-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-05[04]", - "class": "sp800-53a" - } - ], - "prose": "logical access restrictions associated with changes to the system are defined and documented;", - "links": [ - { - "href": "#cm-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-5_obj-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-05[05]", - "class": "sp800-53a" - } - ], - "prose": "logical access restrictions associated with changes to the system are approved;", - "links": [ - { - "href": "#cm-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-5_obj-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-05[06]", - "class": "sp800-53a" - } - ], - "prose": "logical access restrictions associated with changes to the system are enforced.", - "links": [ - { - "href": "#cm-5_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-05-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing access restrictions for changes to the system\n\nconfiguration management plan\n\nsystem design documentation\n\nsystem architecture and configuration documentation\n\nsystem configuration settings and associated documentation\n\nlogical access approvals\n\nphysical access approvals\n\naccess credentials\n\nchange control records\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-05-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with logical access control responsibilities\n\norganizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "cm-5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-05-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for managing access restrictions to change\n\nmechanisms supporting, implementing, or enforcing access restrictions associated with changes to the system" - } - ] - } - ], - "controls": [ - { - "id": "cm-5.1", - "class": "SP800-53-enhancement", - "title": "Automated Access Enforcement and Audit Records", - "params": [ - { - "id": "cm-05.01_odp", - "props": [ - { - "name": "alt-identifier", - "value": "cm-5.1_prm_1" - }, - { - "name": "label", - "value": "CM-05(01)_ODP", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "mechanisms used to automate the enforcement of access restrictions are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CM-05(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-5(1)" - }, - { - "name": "label", - "value": "CM-05(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-05.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#cm-5", - "rel": "required" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-7", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-11", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-5.1_smt", - "name": "statement", - "parts": [ - { - "id": "cm-5.1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Enforce access restrictions using {{ insert: param, cm-05.01_odp }} ; and" - }, - { - "id": "cm-5.1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Automatically generate audit records of the enforcement actions." - } - ] - }, - { - "id": "cm-5.1_gdn", - "name": "guidance", - "prose": "Organizations log system accesses associated with applying configuration changes to ensure that configuration change control is implemented and to support after-the-fact actions should organizations discover any unauthorized changes." - }, - { - "id": "cm-5.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-05(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-5.1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-05(01)(a)", - "class": "sp800-53a" - } - ], - "prose": "access restrictions for change are enforced using {{ insert: param, cm-05.01_odp }};", - "links": [ - { - "href": "#cm-5.1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-5.1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-05(01)(b)", - "class": "sp800-53a" - } - ], - "prose": "audit records of enforcement actions are automatically generated.", - "links": [ - { - "href": "#cm-5.1_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-5.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-5.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-05(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing access restrictions for changes to the system\n\nsystem design documentation\n\nsystem architecture and configuration documentation\n\nsystem configuration settings and associated documentation\n\nchange control records\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-5.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-05(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with logical access control responsibilities\n\norganizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "cm-5.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-05(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for managing access restrictions to change\n\nautomated mechanisms implementing the enforcement of access restrictions for changes to the system\n\nautomated mechanisms supporting auditing of enforcement actions" - } - ] - } - ] - }, - { - "id": "cm-5.5", - "class": "SP800-53-enhancement", - "title": "Privilege Limitation for Production and Operation", - "params": [ - { - "id": "cm-5.5_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-05.05_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-05.05_odp.02" - } - ], - "label": "organization-defined frequency" - }, - { - "id": "cm-05.05_odp.01", - "props": [ - { - "name": "label", - "value": "CM-05(05)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least quarterly" - } - ], - "guidelines": [ - { - "prose": "frequency at which to review privileges is defined;" - } - ] - }, - { - "id": "cm-05.05_odp.02", - "props": [ - { - "name": "label", - "value": "CM-05(05)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least quarterly" - } - ], - "guidelines": [ - { - "prose": "frequency at which to reevaluate privileges is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CM-05(05)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-5(5)" - }, - { - "name": "label", - "value": "CM-05(05)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-05.05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cm-5", - "rel": "required" - }, - { - "href": "#ac-2", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-5.5_smt", - "name": "statement", - "parts": [ - { - "id": "cm-5.5_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Limit privileges to change system components and system-related information within a production or operational environment; and" - }, - { - "id": "cm-5.5_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Review and reevaluate privileges {{ insert: param, cm-5.5_prm_1 }}." - } - ] - }, - { - "id": "cm-5.5_gdn", - "name": "guidance", - "prose": "In many organizations, systems support multiple mission and business functions. Limiting privileges to change system components with respect to operational systems is necessary because changes to a system component may have far-reaching effects on mission and business processes supported by the system. The relationships between systems and mission/business processes are, in some cases, unknown to developers. System-related information includes operational procedures." - }, - { - "id": "cm-5.5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-05(05)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-5.5_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-05(05)(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-5.5_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-05(05)(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "privileges to change system components within a production or operational environment are limited;", - "links": [ - { - "href": "#cm-5.5_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-5.5_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-05(05)(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "privileges to change system-related information within a production or operational environment are limited;", - "links": [ - { - "href": "#cm-5.5_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-5.5_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-5.5_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-05(05)(b)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-5.5_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-05(05)(b)[01]", - "class": "sp800-53a" - } - ], - "prose": "privileges are reviewed {{ insert: param, cm-05.05_odp.01 }};", - "links": [ - { - "href": "#cm-5.5_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-5.5_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-05(05)(b)[02]", - "class": "sp800-53a" - } - ], - "prose": "privileges are reevaluated {{ insert: param, cm-05.05_odp.02 }}.", - "links": [ - { - "href": "#cm-5.5_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-5.5_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-5.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-5.5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-05(05)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing access restrictions for changes to the system\n\nconfiguration management plan\n\nsystem design documentation\n\nsystem architecture and configuration documentation\n\nsystem configuration settings and associated documentation\n\nuser privilege reviews\n\nuser privilege recertifications\n\nsystem component inventory\n\nchange control records\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-5.5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-05(05)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "cm-5.5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-05(05)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for managing access restrictions to change\n\nmechanisms supporting and/or implementing access restrictions for change" - } - ] - } - ] - } - ] - }, - { - "id": "cm-6", - "class": "SP800-53", - "title": "Configuration Settings", - "params": [ - { - "id": "cm-06_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cm-6_prm_1" - }, - { - "name": "label", - "value": "CM-06_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "common secure configurations", - "guidelines": [ - { - "prose": "common secure configurations to establish and document configuration settings for components employed within the system are defined;" - } - ] - }, - { - "id": "cm-06_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "cm-6_prm_2" - }, - { - "name": "label", - "value": "CM-06_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "system components", - "guidelines": [ - { - "prose": "system components for which approval of deviations is needed are defined;" - } - ] - }, - { - "id": "cm-06_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "cm-6_prm_3" - }, - { - "name": "label", - "value": "CM-06_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "operational requirements", - "guidelines": [ - { - "prose": "operational requirements necessitating approval of deviations are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "CM-06", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-6" - }, - { - "name": "label", - "value": "CM-06", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-06" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#4895b4cd-34c5-4667-bf8a-27d443c12047", - "rel": "reference" - }, - { - "href": "#8016d2ed-d30f-4416-9c45-0f42c7aa3232", - "rel": "reference" - }, - { - "href": "#20db4e66-e257-450c-b2e4-2bb9a62a2c88", - "rel": "reference" - }, - { - "href": "#98498928-3ca3-44b3-8b1e-f48685373087", - "rel": "reference" - }, - { - "href": "#d744d9a3-73eb-4085-b9ff-79e82e9e2d6e", - "rel": "reference" - }, - { - "href": "#aa66e14f-e7cb-4a37-99d2-07578dfd4608", - "rel": "reference" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#ca-9", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#cm-11", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#cp-10", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#pl-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pl-9", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - }, - { - "href": "#sc-18", - "rel": "related" - }, - { - "href": "#sc-28", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-43", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-6_smt", - "name": "statement", - "parts": [ - { - "id": "cm-6_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Establish and document configuration settings for components employed within the system that reflect the most restrictive mode consistent with operational requirements using {{ insert: param, cm-06_odp.01 }};" - }, - { - "id": "cm-6_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Implement the configuration settings;" - }, - { - "id": "cm-6_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Identify, document, and approve any deviations from established configuration settings for {{ insert: param, cm-06_odp.02 }} based on {{ insert: param, cm-06_odp.03 }} ; and" - }, - { - "id": "cm-6_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Monitor and control changes to the configuration settings in accordance with organizational policies and procedures." - } - ] - }, - { - "id": "cm-6_gdn", - "name": "guidance", - "prose": "Configuration settings are the parameters that can be changed in the hardware, software, or firmware components of the system that affect the security and privacy posture or functionality of the system. Information technology products for which configuration settings can be defined include mainframe computers, servers, workstations, operating systems, mobile devices, input/output devices, protocols, and applications. Parameters that impact the security posture of systems include registry settings; account, file, or directory permission settings; and settings for functions, protocols, ports, services, and remote connections. Privacy parameters are parameters impacting the privacy posture of systems, including the parameters required to satisfy other privacy controls. Privacy parameters include settings for access controls, data processing preferences, and processing and retention permissions. Organizations establish organization-wide configuration settings and subsequently derive specific configuration settings for systems. The established settings become part of the configuration baseline for the system.\n\nCommon secure configurations (also known as security configuration checklists, lockdown and hardening guides, and security reference guides) provide recognized, standardized, and established benchmarks that stipulate secure configuration settings for information technology products and platforms as well as instructions for configuring those products or platforms to meet operational requirements. Common secure configurations can be developed by a variety of organizations, including information technology product developers, manufacturers, vendors, federal agencies, consortia, academia, industry, and other organizations in the public and private sectors.\n\nImplementation of a common secure configuration may be mandated at the organization level, mission and business process level, system level, or at a higher level, including by a regulatory agency. Common secure configurations include the United States Government Configuration Baseline [USGCB](#98498928-3ca3-44b3-8b1e-f48685373087) and security technical implementation guides (STIGs), which affect the implementation of [CM-6](#cm-6) and other controls such as [AC-19](#ac-19) and [CM-7](#cm-7) . The Security Content Automation Protocol (SCAP) and the defined standards within the protocol provide an effective method to uniquely identify, track, and control configuration settings." - }, - { - "id": "cm-6_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CM-6 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "cm-6_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(a) Requirement 1:" - } - ], - "prose": "The service provider shall use the DoD STIGs to establish configuration settings; Center for Internet Security up to Level 2 (CIS Level 2) guidelines shall be used if STIGs are not available; Custom baselines shall be used if CIS is not available." - }, - { - "id": "cm-6_fr_smt.2", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(a) Requirement 2:" - } - ], - "prose": "The service provider shall ensure that checklists for configuration settings are Security Content Automation Protocol (SCAP) validated or SCAP compatible (if validated checklists are not available)." - }, - { - "id": "cm-6_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Compliance checks are used to evaluate configuration settings and provide general insight into the overall effectiveness of configuration management activities. CSPs and 3PAOs typically combine compliance check findings into a single CM-6 finding, which is acceptable. However, for initial assessments, annual assessments, and significant change requests, FedRAMP requires a clear understanding, on a per-control basis, where risks exist. Therefore, 3PAOs must also analyze compliance check findings as part of the controls assessment. Where a direct mapping exists, the 3PAO must document additional findings per control in the corresponding SAR Risk Exposure Table (RET), which are then documented in the CSP's Plan of Action and Milestones (POA\\&M). This will likely result in the details of individual control findings overlapping with those in the combined CM-6 finding, which is acceptable.\n\nDuring monthly continuous monitoring, new findings from CSP compliance checks may be combined into a single CM-6 POA\\&M item. CSPs are not required to map the findings to specific controls because controls are only assessed during initial assessments, annual assessments, and significant change requests." - } - ] - }, - { - "id": "cm-6_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-06", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-6_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-06a.", - "class": "sp800-53a" - } - ], - "prose": "configuration settings that reflect the most restrictive mode consistent with operational requirements are established and documented for components employed within the system using {{ insert: param, cm-06_odp.01 }};", - "links": [ - { - "href": "#cm-6_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-6_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-06b.", - "class": "sp800-53a" - } - ], - "prose": "the configuration settings documented in CM-06a are implemented;", - "links": [ - { - "href": "#cm-6_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-6_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-06c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-6_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-06c.[01]", - "class": "sp800-53a" - } - ], - "prose": "any deviations from established configuration settings for {{ insert: param, cm-06_odp.02 }} are identified and documented based on {{ insert: param, cm-06_odp.03 }};", - "links": [ - { - "href": "#cm-6_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-6_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-06c.[02]", - "class": "sp800-53a" - } - ], - "prose": "any deviations from established configuration settings for {{ insert: param, cm-06_odp.02 }} are approved;", - "links": [ - { - "href": "#cm-6_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-6_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-6_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-06d.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-6_obj.d-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-06d.[01]", - "class": "sp800-53a" - } - ], - "prose": "changes to the configuration settings are monitored in accordance with organizational policies and procedures;", - "links": [ - { - "href": "#cm-6_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-6_obj.d-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-06d.[02]", - "class": "sp800-53a" - } - ], - "prose": "changes to the configuration settings are controlled in accordance with organizational policies and procedures.", - "links": [ - { - "href": "#cm-6_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-6_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-6_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-6_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-06-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing configuration settings for the system\n\nconfiguration management plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\ncommon secure configuration checklists\n\nsystem component inventory\n\nevidence supporting approved deviations from established configuration settings\n\nchange control records\n\nsystem data processing and retention permissions\n\nsystem audit records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-6_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-06-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with security configuration management responsibilities\n\norganizational personnel with privacy configuration management responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "cm-6_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-06-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for managing configuration settings\n\nmechanisms that implement, monitor, and/or control system configuration settings\n\nmechanisms that identify and/or document deviations from established configuration settings" - } - ] - } - ], - "controls": [ - { - "id": "cm-6.1", - "class": "SP800-53-enhancement", - "title": "Automated Management, Application, and Verification", - "params": [ - { - "id": "cm-6.1_prm_2", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-06.01_odp.02" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-06.01_odp.03" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-06.01_odp.04" - } - ], - "label": "organization-defined automated mechanisms" - }, - { - "id": "cm-06.01_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cm-6.1_prm_1" - }, - { - "name": "label", - "value": "CM-06(01)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "system components", - "guidelines": [ - { - "prose": "system components for which to manage, apply, and verify configuration settings are defined;" - } - ] - }, - { - "id": "cm-06.01_odp.02", - "props": [ - { - "name": "label", - "value": "CM-06(01)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms to manage configuration settings are defined;" - } - ] - }, - { - "id": "cm-06.01_odp.03", - "props": [ - { - "name": "label", - "value": "CM-06(01)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms to apply configuration settings are defined;" - } - ] - }, - { - "id": "cm-06.01_odp.04", - "props": [ - { - "name": "label", - "value": "CM-06(01)_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms to verify configuration settings are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "CM-06(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-6(1)" - }, - { - "name": "label", - "value": "CM-06(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-06.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cm-6", - "rel": "required" - }, - { - "href": "#ca-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-6.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Manage, apply, and verify configuration settings for {{ insert: param, cm-06.01_odp.01 }} using {{ insert: param, cm-6.1_prm_2 }}." - }, - { - "id": "cm-6.1_gdn", - "name": "guidance", - "prose": "Automated tools (e.g., hardening tools, baseline configuration tools) can improve the accuracy, consistency, and availability of configuration settings information. Automation can also provide data aggregation and data correlation capabilities, alerting mechanisms, and dashboards to support risk-based decision-making within the organization." - }, - { - "id": "cm-6.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-06(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-6.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-06(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "configuration settings for {{ insert: param, cm-06.01_odp.01 }} are managed using {{ insert: param, cm-06.01_odp.02 }};", - "links": [ - { - "href": "#cm-6.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-6.1_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-06(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "configuration settings for {{ insert: param, cm-06.01_odp.01 }} are applied using {{ insert: param, cm-06.01_odp.03 }};", - "links": [ - { - "href": "#cm-6.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-6.1_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-06(01)[03]", - "class": "sp800-53a" - } - ], - "prose": "configuration settings for {{ insert: param, cm-06.01_odp.01 }} are verified using {{ insert: param, cm-06.01_odp.04 }}.", - "links": [ - { - "href": "#cm-6.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-6.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-6.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-06(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing configuration settings for the system\n\nconfiguration management plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem component inventory\n\ncommon secure configuration checklists\n\nchange control records\n\nsystem audit records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-6.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-06(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with security configuration management responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "cm-6.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-06(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for managing configuration settings\n\nautomated mechanisms implemented to manage, apply, and verify system configuration settings" - } - ] - } - ] - }, - { - "id": "cm-6.2", - "class": "SP800-53-enhancement", - "title": "Respond to Unauthorized Changes", - "params": [ - { - "id": "cm-06.02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cm-6.2_prm_2" - }, - { - "name": "label", - "value": "CM-06(02)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "actions", - "guidelines": [ - { - "prose": "actions to be taken upon an unauthorized change are defined;" - } - ] - }, - { - "id": "cm-06.02_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "cm-6.2_prm_1" - }, - { - "name": "label", - "value": "CM-06(02)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "configuration settings", - "guidelines": [ - { - "prose": "configuration settings requiring action upon an unauthorized change are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "CM-06(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-6(2)" - }, - { - "name": "label", - "value": "CM-06(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-06.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cm-6", - "rel": "required" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-6", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-6.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Take the following actions in response to unauthorized changes to {{ insert: param, cm-06.02_odp.02 }}: {{ insert: param, cm-06.02_odp.01 }}." - }, - { - "id": "cm-6.2_gdn", - "name": "guidance", - "prose": "Responses to unauthorized changes to configuration settings include alerting designated organizational personnel, restoring established configuration settings, or—in extreme cases—halting affected system processing." - }, - { - "id": "cm-6.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-06(02)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-06.02_odp.01 }} are taken in response to unauthorized changes to {{ insert: param, cm-06.02_odp.02 }}.", - "links": [ - { - "href": "#cm-6.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-6.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-06(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System security plan\n\nprivacy plan\n\nconfiguration management policy\n\nprocedures addressing configuration settings for the system\n\nconfiguration management plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nalerts/notifications of unauthorized changes to system configuration settings\n\nsystem component inventory\n\ndocumented responses to unauthorized changes to system configuration settings\n\nchange control records\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-6.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-06(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with security configuration management responsibilities\n\norganizational personnel with security and privacy responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "cm-6.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-06(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational process for responding to unauthorized changes to system configuration settings\n\nmechanisms supporting and/or implementing actions in response to unauthorized changes" - } - ] - } - ] - } - ] - }, - { - "id": "cm-7", - "class": "SP800-53", - "title": "Least Functionality", - "params": [ - { - "id": "cm-7_prm_2", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-07_odp.02" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-07_odp.03" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-07_odp.04" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-07_odp.05" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-07_odp.06" - } - ], - "label": "organization-defined prohibited or restricted functions, system ports, protocols, software, and/or services" - }, - { - "id": "cm-07_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cm-7_prm_1" - }, - { - "name": "alt-label", - "value": "mission essential capabilities", - "class": "sp800-53" - }, - { - "name": "label", - "value": "CM-07_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "mission-essential capabilities", - "guidelines": [ - { - "prose": "mission-essential capabilities for the system are defined;" - } - ] - }, - { - "id": "cm-07_odp.02", - "props": [ - { - "name": "label", - "value": "CM-07_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "functions", - "guidelines": [ - { - "prose": "functions to be prohibited or restricted are defined;" - } - ] - }, - { - "id": "cm-07_odp.03", - "props": [ - { - "name": "label", - "value": "CM-07_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "ports", - "guidelines": [ - { - "prose": "ports to be prohibited or restricted are defined;" - } - ] - }, - { - "id": "cm-07_odp.04", - "props": [ - { - "name": "label", - "value": "CM-07_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "protocols", - "guidelines": [ - { - "prose": "protocols to be prohibited or restricted are defined;" - } - ] - }, - { - "id": "cm-07_odp.05", - "props": [ - { - "name": "label", - "value": "CM-07_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "software", - "guidelines": [ - { - "prose": "software to be prohibited or restricted is defined;" - } - ] - }, - { - "id": "cm-07_odp.06", - "props": [ - { - "name": "label", - "value": "CM-07_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "services", - "guidelines": [ - { - "prose": "services to be prohibited or restricted are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "CM-07", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-7" - }, - { - "name": "label", - "value": "CM-07", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-07" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#678e3d6c-150b-4393-aec5-6e3481eb1e00", - "rel": "reference" - }, - { - "href": "#eea3c092-42ed-4382-a6f4-1adadef01b9d", - "rel": "reference" - }, - { - "href": "#7c37a38d-21d7-40d8-bc3d-b5e27eac17e1", - "rel": "reference" - }, - { - "href": "#a295ca19-8c75-4b4c-8800-98024732e181", - "rel": "reference" - }, - { - "href": "#38f39739-1ebd-43b1-8b8c-00f591d89ebd", - "rel": "reference" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-11", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "#sc-2", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-37", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-7_smt", - "name": "statement", - "parts": [ - { - "id": "cm-7_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Configure the system to provide only {{ insert: param, cm-07_odp.01 }} ; and" - }, - { - "id": "cm-7_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Prohibit or restrict the use of the following functions, ports, protocols, software, and/or services: {{ insert: param, cm-7_prm_2 }}." - } - ] - }, - { - "id": "cm-7_gdn", - "name": "guidance", - "prose": "Systems provide a wide variety of functions and services. Some of the functions and services routinely provided by default may not be necessary to support essential organizational missions, functions, or operations. Additionally, it is sometimes convenient to provide multiple services from a single system component, but doing so increases risk over limiting the services provided by that single component. Where feasible, organizations limit component functionality to a single function per component. Organizations consider removing unused or unnecessary software and disabling unused or unnecessary physical and logical ports and protocols to prevent unauthorized connection of components, transfer of information, and tunneling. Organizations employ network scanning tools, intrusion detection and prevention systems, and end-point protection technologies, such as firewalls and host-based intrusion detection systems, to identify and prevent the use of prohibited functions, protocols, ports, and services. Least functionality can also be achieved as part of the fundamental design and development of the system (see [SA-8](#sa-8), [SC-2](#sc-2) , and [SC-3](#sc-3))." - }, - { - "id": "cm-7_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CM-7 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "cm-7_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(b) Requirement:" - } - ], - "prose": "The service provider shall use Security guidelines (See CM-6) to establish list of prohibited or restricted functions, ports, protocols, and/or services or establishes its own list of prohibited or restricted functions, ports, protocols, and/or services if STIGs or CIS is not available." - } - ] - }, - { - "id": "cm-7_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-07", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-7_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-07a.", - "class": "sp800-53a" - } - ], - "prose": "the system is configured to provide only {{ insert: param, cm-07_odp.01 }};", - "links": [ - { - "href": "#cm-7_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-7_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-07b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-7_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-07b.[01]", - "class": "sp800-53a" - } - ], - "prose": "the use of {{ insert: param, cm-07_odp.02 }} is prohibited or restricted;", - "links": [ - { - "href": "#cm-7_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-7_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-07b.[02]", - "class": "sp800-53a" - } - ], - "prose": "the use of {{ insert: param, cm-07_odp.03 }} is prohibited or restricted;", - "links": [ - { - "href": "#cm-7_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-7_obj.b-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-07b.[03]", - "class": "sp800-53a" - } - ], - "prose": "the use of {{ insert: param, cm-07_odp.04 }} is prohibited or restricted;", - "links": [ - { - "href": "#cm-7_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-7_obj.b-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-07b.[04]", - "class": "sp800-53a" - } - ], - "prose": "the use of {{ insert: param, cm-07_odp.05 }} is prohibited or restricted;", - "links": [ - { - "href": "#cm-7_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-7_obj.b-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-07b.[05]", - "class": "sp800-53a" - } - ], - "prose": "the use of {{ insert: param, cm-07_odp.06 }} is prohibited or restricted.", - "links": [ - { - "href": "#cm-7_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-7_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-7_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-07-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing least functionality in the system\n\nconfiguration management plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem component inventory\n\ncommon secure configuration checklists\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-7_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-07-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with security configuration management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "cm-7_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-07-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes prohibiting or restricting functions, ports, protocols, software, and/or services\n\nmechanisms implementing restrictions or prohibition of functions, ports, protocols, software, and/or services" - } - ] - } - ], - "controls": [ - { - "id": "cm-7.1", - "class": "SP800-53-enhancement", - "title": "Periodic Review", - "params": [ - { - "id": "cm-7.1_prm_2", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-07.01_odp.02" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-07.01_odp.03" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-07.01_odp.04" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-07.01_odp.05" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-07.01_odp.06" - } - ], - "label": "organization-defined functions, ports, protocols, software, and services within the system deemed to be unnecessary and/or nonsecure" - }, - { - "id": "cm-07.01_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cm-7.1_prm_1" - }, - { - "name": "label", - "value": "CM-07(01)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to review the system to identify unnecessary and/or non-secure functions, ports, protocols, software, and/or services is defined;" - } - ] - }, - { - "id": "cm-07.01_odp.02", - "props": [ - { - "name": "label", - "value": "CM-07(01)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "functions", - "guidelines": [ - { - "prose": "functions to be disabled or removed when deemed unnecessary or non-secure are defined;" - } - ] - }, - { - "id": "cm-07.01_odp.03", - "props": [ - { - "name": "label", - "value": "CM-07(01)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "ports", - "guidelines": [ - { - "prose": "ports to be disabled or removed when deemed unnecessary or non-secure are defined;" - } - ] - }, - { - "id": "cm-07.01_odp.04", - "props": [ - { - "name": "label", - "value": "CM-07(01)_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "protocols", - "guidelines": [ - { - "prose": "protocols to be disabled or removed when deemed unnecessary or non-secure are defined;" - } - ] - }, - { - "id": "cm-07.01_odp.05", - "props": [ - { - "name": "label", - "value": "CM-07(01)_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "software", - "guidelines": [ - { - "prose": "software to be disabled or removed when deemed unnecessary or non-secure is defined;" - } - ] - }, - { - "id": "cm-07.01_odp.06", - "props": [ - { - "name": "label", - "value": "CM-07(01)_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "services", - "guidelines": [ - { - "prose": "services to be disabled or removed when deemed unnecessary or non-secure are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "CM-07(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-7(1)" - }, - { - "name": "label", - "value": "CM-07(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-07.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#cm-7", - "rel": "required" - }, - { - "href": "#ac-18", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-7.1_smt", - "name": "statement", - "parts": [ - { - "id": "cm-7.1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Review the system {{ insert: param, cm-07.01_odp.01 }} to identify unnecessary and/or nonsecure functions, ports, protocols, software, and services; and" - }, - { - "id": "cm-7.1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Disable or remove {{ insert: param, cm-7.1_prm_2 }}." - } - ] - }, - { - "id": "cm-7.1_gdn", - "name": "guidance", - "prose": "Organizations review functions, ports, protocols, and services provided by systems or system components to determine the functions and services that are candidates for elimination. Such reviews are especially important during transition periods from older technologies to newer technologies (e.g., transition from IPv4 to IPv6). These technology transitions may require implementing the older and newer technologies simultaneously during the transition period and returning to minimum essential functions, ports, protocols, and services at the earliest opportunity. Organizations can either decide the relative security of the function, port, protocol, and/or service or base the security decision on the assessment of other entities. Unsecure protocols include Bluetooth, FTP, and peer-to-peer networking." - }, - { - "id": "cm-7.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-07(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-7.1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-07(01)(a)", - "class": "sp800-53a" - } - ], - "prose": "the system is reviewed {{ insert: param, cm-07.01_odp.01 }} to identify unnecessary and/or non-secure functions, ports, protocols, software, and services:", - "links": [ - { - "href": "#cm-7.1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-7.1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-07(01)(b)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-7.1_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-07(01)(b)[01]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-07.01_odp.02 }} deemed to be unnecessary and/or non-secure are disabled or removed;", - "links": [ - { - "href": "#cm-7.1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-7.1_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-07(01)(b)[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-07.01_odp.03 }} deemed to be unnecessary and/or non-secure are disabled or removed;", - "links": [ - { - "href": "#cm-7.1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-7.1_obj.b-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-07(01)(b)[03]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-07.01_odp.04 }} deemed to be unnecessary and/or non-secure are disabled or removed;", - "links": [ - { - "href": "#cm-7.1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-7.1_obj.b-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-07(01)(b)[04]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-07.01_odp.05 }} deemed to be unnecessary and/or non-secure is disabled or removed;", - "links": [ - { - "href": "#cm-7.1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-7.1_obj.b-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-07(01)(b)[05]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-07.01_odp.06 }} deemed to be unnecessary and/or non-secure are disabled or removed.", - "links": [ - { - "href": "#cm-7.1_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-7.1_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-7.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-7.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-07(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing least functionality in the system\n\nconfiguration management plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\ncommon secure configuration checklists\n\ndocumented reviews of functions, ports, protocols, and/or services\n\nchange control records\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-7.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-07(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for reviewing functions, ports, protocols, and services on the system\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "cm-7.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-07(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for reviewing or disabling functions, ports, protocols, and services on the system\n\nmechanisms implementing review and disabling of functions, ports, protocols, and/or services" - } - ] - } - ] - }, - { - "id": "cm-7.2", - "class": "SP800-53-enhancement", - "title": "Prevent Program Execution", - "params": [ - { - "id": "cm-07.02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cm-7.2_prm_1" - }, - { - "name": "label", - "value": "CM-07(02)_ODP[01]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "{{ insert: param, cm-07.02_odp.02 }}", - "rules authorizing the terms and conditions of software program usage" - ] - } - }, - { - "id": "cm-07.02_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "cm-7.2_prm_2" - }, - { - "name": "label", - "value": "CM-07(02)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "policies, rules of behavior, and/or access agreements regarding software program usage and restrictions", - "guidelines": [ - { - "prose": "policies, rules of behavior, and/or access agreements regarding software program usage and restrictions are defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "CM-07(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-7(2)" - }, - { - "name": "label", - "value": "CM-07(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-07.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#cm-7", - "rel": "required" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pl-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-5", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-7.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Prevent program execution in accordance with {{ insert: param, cm-07.02_odp.01 }}." - }, - { - "id": "cm-7.2_gdn", - "name": "guidance", - "prose": "Prevention of program execution addresses organizational policies, rules of behavior, and/or access agreements that restrict software usage and the terms and conditions imposed by the developer or manufacturer, including software licensing and copyrights. Restrictions include prohibiting auto-execute features, restricting roles allowed to approve program execution, permitting or prohibiting specific software programs, or restricting the number of program instances executed at the same time." - }, - { - "id": "cm-7.2_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CM-7 (2) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "cm-7.2_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "This control refers to software deployment by CSP personnel into the production environment. The control requires a policy that states conditions for deploying software. This control shall be implemented in a technical manner on the information system to only allow programs to run that adhere to the policy (i.e. allow-listing). This control is not to be based off of strictly written policy on what is allowed or not allowed to run." - } - ] - }, - { - "id": "cm-7.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-07(02)", - "class": "sp800-53a" - } - ], - "prose": "program execution is prevented in accordance with {{ insert: param, cm-07.02_odp.01 }}.", - "links": [ - { - "href": "#cm-7.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-7.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-07(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing least functionality in the system\n\nconfiguration management plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem component inventory\n\ncommon secure configuration checklists\n\nspecifications for preventing software program execution\n\nchange control records\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-7.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-07(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "cm-7.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-07(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes preventing program execution on the system\n\norganizational processes for software program usage and restrictions\n\nmechanisms preventing program execution on the system\n\nmechanisms supporting and/or implementing software program usage and restrictions" - } - ] - } - ] - }, - { - "id": "cm-7.5", - "class": "SP800-53-enhancement", - "title": "Authorized Software — Allow-by-exception", - "params": [ - { - "id": "cm-07.05_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cm-7.5_prm_1" - }, - { - "name": "alt-label", - "value": "software programs authorized to execute on the system", - "class": "sp800-53" - }, - { - "name": "label", - "value": "CM-07(05)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "software programs", - "guidelines": [ - { - "prose": "software programs authorized to execute on the system are defined;" - } - ] - }, - { - "id": "cm-07.05_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "cm-7.5_prm_2" - }, - { - "name": "label", - "value": "CM-07(05)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least quarterly or when there is a change" - } - ], - "guidelines": [ - { - "prose": "frequency at which to review and update the list of authorized software programs is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "CM-07(05)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-7(5)" - }, - { - "name": "label", - "value": "CM-07(05)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-07.05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#cm-7", - "rel": "required" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#cm-10", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pl-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-5", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-34", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-7.5_smt", - "name": "statement", - "parts": [ - { - "id": "cm-7.5_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Identify {{ insert: param, cm-07.05_odp.01 }};" - }, - { - "id": "cm-7.5_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the system; and" - }, - { - "id": "cm-7.5_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Review and update the list of authorized software programs {{ insert: param, cm-07.05_odp.02 }}." - } - ] - }, - { - "id": "cm-7.5_gdn", - "name": "guidance", - "prose": "Authorized software programs can be limited to specific versions or from a specific source. To facilitate a comprehensive authorized software process and increase the strength of protection for attacks that bypass application level authorized software, software programs may be decomposed into and monitored at different levels of detail. These levels include applications, application programming interfaces, application modules, scripts, system processes, system services, kernel functions, registries, drivers, and dynamic link libraries. The concept of permitting the execution of authorized software may also be applied to user actions, system ports and protocols, IP addresses/ranges, websites, and MAC addresses. Organizations consider verifying the integrity of authorized software programs using digital signatures, cryptographic checksums, or hash functions. Verification of authorized software can occur either prior to execution or at system startup. The identification of authorized URLs for websites is addressed in [CA-3(5)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ca-3.5) and [SC-7](#sc-7)." - }, - { - "id": "cm-7.5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-07(05)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-7.5_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-07(05)(a)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-07.05_odp.01 }} are identified;", - "links": [ - { - "href": "#cm-7.5_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-7.5_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-07(05)(b)", - "class": "sp800-53a" - } - ], - "prose": "a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the system is employed;", - "links": [ - { - "href": "#cm-7.5_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-7.5_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-07(05)(c)", - "class": "sp800-53a" - } - ], - "prose": "the list of authorized software programs is reviewed and updated {{ insert: param, cm-07.05_odp.02 }}.", - "links": [ - { - "href": "#cm-7.5_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-7.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-7.5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-07(05)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing least functionality in the system\n\nconfiguration management plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of software programs authorized to execute on the system\n\nsystem component inventory\n\ncommon secure configuration checklists\n\nreview and update records associated with list of authorized software programs\n\nchange control records\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-7.5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-07(05)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for identifying software authorized to execute on the system\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "cm-7.5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-07(05)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational process for identifying, reviewing, and updating programs authorized to execute on the system\n\norganizational process for implementing authorized software policy\n\nmechanisms supporting and/or implementing authorized software policy" - } - ] - } - ] - } - ] - }, - { - "id": "cm-8", - "class": "SP800-53", - "title": "System Component Inventory", - "params": [ - { - "id": "cm-08_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cm-8_prm_1" - }, - { - "name": "alt-label", - "value": "information deemed necessary to achieve effective system component accountability", - "class": "sp800-53" - }, - { - "name": "label", - "value": "CM-08_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "information", - "guidelines": [ - { - "prose": "information deemed necessary to achieve effective system component accountability is defined;" - } - ] - }, - { - "id": "cm-08_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "cm-8_prm_2" - }, - { - "name": "label", - "value": "CM-08_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least monthly" - } - ], - "guidelines": [ - { - "prose": "frequency at which to review and update the system component inventory is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "CM-08", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-8" - }, - { - "name": "label", - "value": "CM-08", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#110e26af-4765-49e1-8740-6750f83fcda1", - "rel": "reference" - }, - { - "href": "#e7942589-e267-4a5a-a3d9-f39a7aae81f0", - "rel": "reference" - }, - { - "href": "#8306620b-1920-4d73-8b21-12008528595f", - "rel": "reference" - }, - { - "href": "#20db4e66-e257-450c-b2e4-2bb9a62a2c88", - "rel": "reference" - }, - { - "href": "#70402863-5078-43af-9a6c-e11b0f3ec370", - "rel": "reference" - }, - { - "href": "#996241f8-f692-42d5-91f1-ce8b752e39e6", - "rel": "reference" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#cm-9", - "rel": "related" - }, - { - "href": "#cm-10", - "rel": "related" - }, - { - "href": "#cm-11", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#cm-13", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#ma-2", - "rel": "related" - }, - { - "href": "#ma-6", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pe-20", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pl-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-5", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sr-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-8_smt", - "name": "statement", - "parts": [ - { - "id": "cm-8_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop and document an inventory of system components that:", - "parts": [ - { - "id": "cm-8_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Accurately reflects the system;" - }, - { - "id": "cm-8_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Includes all components within the system;" - }, - { - "id": "cm-8_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Does not include duplicate accounting of components or components assigned to any other system;" - }, - { - "id": "cm-8_smt.a.4", - "name": "item", - "props": [ - { - "name": "label", - "value": "4." - } - ], - "prose": "Is at the level of granularity deemed necessary for tracking and reporting; and" - }, - { - "id": "cm-8_smt.a.5", - "name": "item", - "props": [ - { - "name": "label", - "value": "5." - } - ], - "prose": "Includes the following information to achieve system component accountability: {{ insert: param, cm-08_odp.01 }} ; and" - } - ] - }, - { - "id": "cm-8_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Review and update the system component inventory {{ insert: param, cm-08_odp.02 }}." - } - ] - }, - { - "id": "cm-8_gdn", - "name": "guidance", - "prose": "System components are discrete, identifiable information technology assets that include hardware, software, and firmware. Organizations may choose to implement centralized system component inventories that include components from all organizational systems. In such situations, organizations ensure that the inventories include system-specific information required for component accountability. The information necessary for effective accountability of system components includes the system name, software owners, software version numbers, hardware inventory specifications, software license information, and for networked components, the machine names and network addresses across all implemented protocols (e.g., IPv4, IPv6). Inventory specifications include date of receipt, cost, model, serial number, manufacturer, supplier information, component type, and physical location.\n\nPreventing duplicate accounting of system components addresses the lack of accountability that occurs when component ownership and system association is not known, especially in large or complex connected systems. Effective prevention of duplicate accounting of system components necessitates use of a unique identifier for each component. For software inventory, centrally managed software that is accessed via other systems is addressed as a component of the system on which it is installed and managed. Software installed on multiple organizational systems and managed at the system level is addressed for each individual system and may appear more than once in a centralized component inventory, necessitating a system association for each software instance in the centralized inventory to avoid duplicate accounting of components. Scanning systems implementing multiple network protocols (e.g., IPv4 and IPv6) can result in duplicate components being identified in different address spaces. The implementation of [CM-8(7)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#cm-8.7) can help to eliminate duplicate accounting of components." - }, - { - "id": "cm-8_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CM-8 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "cm-8_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "must be provided at least monthly or when there is a change." - } - ] - }, - { - "id": "cm-8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-08", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-8_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-08a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-8_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-08a.01", - "class": "sp800-53a" - } - ], - "prose": "an inventory of system components that accurately reflects the system is developed and documented;", - "links": [ - { - "href": "#cm-8_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8_obj.a.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-08a.02", - "class": "sp800-53a" - } - ], - "prose": "an inventory of system components that includes all components within the system is developed and documented;", - "links": [ - { - "href": "#cm-8_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8_obj.a.3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-08a.03", - "class": "sp800-53a" - } - ], - "prose": "an inventory of system components that does not include duplicate accounting of components or components assigned to any other system is developed and documented;", - "links": [ - { - "href": "#cm-8_smt.a.3", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8_obj.a.4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-08a.04", - "class": "sp800-53a" - } - ], - "prose": "an inventory of system components that is at the level of granularity deemed necessary for tracking and reporting is developed and documented;", - "links": [ - { - "href": "#cm-8_smt.a.4", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8_obj.a.5", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-08a.05", - "class": "sp800-53a" - } - ], - "prose": "an inventory of system components that includes {{ insert: param, cm-08_odp.01 }} is developed and documented;", - "links": [ - { - "href": "#cm-8_smt.a.5", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-8_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-08b.", - "class": "sp800-53a" - } - ], - "prose": "the system component inventory is reviewed and updated {{ insert: param, cm-08_odp.02 }}.", - "links": [ - { - "href": "#cm-8_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-08-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing system component inventory\n\nconfiguration management plan\n\nsystem security plan\n\nsystem design documentation\n\nsystem component inventory\n\ninventory reviews and update records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-08-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with component inventory management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "cm-8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-08-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for managing the system component inventory\n\nmechanisms supporting and/or implementing system component inventory" - } - ] - } - ], - "controls": [ - { - "id": "cm-8.1", - "class": "SP800-53-enhancement", - "title": "Updates During Installation and Removal", - "props": [ - { - "name": "label", - "value": "CM-08(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-8(1)" - }, - { - "name": "label", - "value": "CM-08(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-08.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#cm-8", - "rel": "required" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-16", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-8.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Update the inventory of system components as part of component installations, removals, and system updates." - }, - { - "id": "cm-8.1_gdn", - "name": "guidance", - "prose": "Organizations can improve the accuracy, completeness, and consistency of system component inventories if the inventories are updated as part of component installations or removals or during general system updates. If inventories are not updated at these key times, there is a greater likelihood that the information will not be appropriately captured and documented. System updates include hardware, software, and firmware components." - }, - { - "id": "cm-8.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-08(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-8.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-08(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "the inventory of system components is updated as part of component installations;", - "links": [ - { - "href": "#cm-8.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8.1_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-08(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "the inventory of system components is updated as part of component removals;", - "links": [ - { - "href": "#cm-8.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8.1_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-08(01)[03]", - "class": "sp800-53a" - } - ], - "prose": "the inventory of system components is updated as part of system updates.", - "links": [ - { - "href": "#cm-8.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-8.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-08(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing system component inventory\n\nconfiguration management plan\n\nsystem security plan\n\nsystem component inventory\n\ninventory reviews and update records\n\nchange control records\n\ncomponent installation records\n\ncomponent removal records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-8.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-08(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with component inventory updating responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "cm-8.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-08(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for updating the system component inventory\n\nmechanisms supporting and/or implementing system component inventory updates" - } - ] - } - ] - }, - { - "id": "cm-8.2", - "class": "SP800-53-enhancement", - "title": "Automated Maintenance", - "params": [ - { - "id": "cm-8.2_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-08.02_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-08.02_odp.02" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-08.02_odp.03" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-08.02_odp.04" - } - ], - "label": "organization-defined automated mechanisms" - }, - { - "id": "cm-08.02_odp.01", - "props": [ - { - "name": "label", - "value": "CM-08(02)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used to maintain the currency of the system component inventory are defined;" - } - ] - }, - { - "id": "cm-08.02_odp.02", - "props": [ - { - "name": "label", - "value": "CM-08(02)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used to maintain the completeness of the system component inventory are defined;" - } - ] - }, - { - "id": "cm-08.02_odp.03", - "props": [ - { - "name": "label", - "value": "CM-08(02)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used to maintain the accuracy of the system component inventory are defined;" - } - ] - }, - { - "id": "cm-08.02_odp.04", - "props": [ - { - "name": "label", - "value": "CM-08(02)_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used to maintain the availability of the system component inventory are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CM-08(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-8(2)" - }, - { - "name": "label", - "value": "CM-08(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-08.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#cm-8", - "rel": "required" - } - ], - "parts": [ - { - "id": "cm-8.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Maintain the currency, completeness, accuracy, and availability of the inventory of system components using {{ insert: param, cm-8.2_prm_1 }}." - }, - { - "id": "cm-8.2_gdn", - "name": "guidance", - "prose": "Organizations maintain system inventories to the extent feasible. For example, virtual machines can be difficult to monitor because such machines are not visible to the network when not in use. In such cases, organizations maintain as up-to-date, complete, and accurate an inventory as is deemed reasonable. Automated maintenance can be achieved by the implementation of [CM-2(2)](#cm-2.2) for organizations that combine system component inventory and baseline configuration activities." - }, - { - "id": "cm-8.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-08(02)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-8.2_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-08(02)[01]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-08.02_odp.01 }} are used to maintain the currency of the system component inventory;", - "links": [ - { - "href": "#cm-8.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8.2_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-08(02)[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-08.02_odp.02 }} are used to maintain the completeness of the system component inventory;", - "links": [ - { - "href": "#cm-8.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8.2_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-08(02)[03]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-08.02_odp.03 }} are used to maintain the accuracy of the system component inventory;", - "links": [ - { - "href": "#cm-8.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8.2_obj-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-08(02)[04]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-08.02_odp.04 }} are used to maintain the availability of the system component inventory.", - "links": [ - { - "href": "#cm-8.2_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-8.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-08(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing system component inventory\n\nconfiguration management plan\n\nsystem design documentation\n\nsystem security plan\n\nsystem component inventory\n\nchange control records\n\nsystem maintenance records\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-8.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-08(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with component inventory management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "cm-8.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-08(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for maintaining the system component inventory\n\nautomated mechanisms supporting and/or implementing the system component inventory" - } - ] - } - ] - }, - { - "id": "cm-8.3", - "class": "SP800-53-enhancement", - "title": "Automated Unauthorized Component Detection", - "params": [ - { - "id": "cm-8.3_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-08.03_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-08.03_odp.02" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-08.03_odp.03" - } - ], - "label": "organization-defined automated mechanisms" - }, - { - "id": "cm-08.03_odp.01", - "props": [ - { - "name": "label", - "value": "CM-08(03)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "constraints": [ - { - "description": "automated mechanisms with a maximum five-minute delay in detection" - } - ], - "guidelines": [ - { - "prose": "automated mechanisms used to detect the presence of unauthorized hardware within the system are defined;" - } - ] - }, - { - "id": "cm-08.03_odp.02", - "props": [ - { - "name": "label", - "value": "CM-08(03)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "constraints": [ - { - "description": "automated mechanisms with a maximum five-minute delay in detection" - } - ], - "guidelines": [ - { - "prose": "automated mechanisms used to detect the presence of unauthorized software within the system are defined;" - } - ] - }, - { - "id": "cm-08.03_odp.03", - "props": [ - { - "name": "label", - "value": "CM-08(03)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "constraints": [ - { - "description": "automated mechanisms with a maximum five-minute delay in detection" - } - ], - "guidelines": [ - { - "prose": "automated mechanisms used to detect the presence of unauthorized firmware within the system are defined;" - } - ] - }, - { - "id": "cm-08.03_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "cm-8.3_prm_2" - }, - { - "name": "label", - "value": "CM-08(03)_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "continuously" - } - ], - "guidelines": [ - { - "prose": "frequency at which automated mechanisms are used to detect the presence of unauthorized system components within the system is defined;" - } - ] - }, - { - "id": "cm-08.03_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "cm-8.3_prm_3" - }, - { - "name": "label", - "value": "CM-08(03)_ODP[05]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "disable network access by unauthorized components", - "isolate unauthorized components", - "notify {{ insert: param, cm-08.03_odp.06 }}" - ] - } - }, - { - "id": "cm-08.03_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "cm-8.3_prm_4" - }, - { - "name": "label", - "value": "CM-08(03)_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to be notified when unauthorized components are detected is/are defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CM-08(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-8(3)" - }, - { - "name": "label", - "value": "CM-08(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-08.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#cm-8", - "rel": "required" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - }, - { - "href": "#sc-39", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-44", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-8.3_smt", - "name": "statement", - "parts": [ - { - "id": "cm-8.3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Detect the presence of unauthorized hardware, software, and firmware components within the system using {{ insert: param, cm-8.3_prm_1 }} {{ insert: param, cm-08.03_odp.04 }} ; and" - }, - { - "id": "cm-8.3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Take the following actions when unauthorized components are detected: {{ insert: param, cm-08.03_odp.05 }}." - } - ] - }, - { - "id": "cm-8.3_gdn", - "name": "guidance", - "prose": "Automated unauthorized component detection is applied in addition to the monitoring for unauthorized remote connections and mobile devices. Monitoring for unauthorized system components may be accomplished on an ongoing basis or by the periodic scanning of systems for that purpose. Automated mechanisms may also be used to prevent the connection of unauthorized components (see [CM-7(9)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#cm-7.9) ). Automated mechanisms can be implemented in systems or in separate system components. When acquiring and implementing automated mechanisms, organizations consider whether such mechanisms depend on the ability of the system component to support an agent or supplicant in order to be detected since some types of components do not have or cannot support agents (e.g., IoT devices, sensors). Isolation can be achieved , for example, by placing unauthorized system components in separate domains or subnets or quarantining such components. This type of component isolation is commonly referred to as \"sandboxing.\"" - }, - { - "id": "cm-8.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-08(03)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-8.3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-08(03)(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-8.3_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-08(03)(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the presence of unauthorized hardware within the system is detected using {{ insert: param, cm-08.03_odp.01 }} {{ insert: param, cm-08.03_odp.04 }};", - "links": [ - { - "href": "#cm-8.3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8.3_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-08(03)(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the presence of unauthorized software within the system is detected using {{ insert: param, cm-08.03_odp.02 }} {{ insert: param, cm-08.03_odp.04 }};", - "links": [ - { - "href": "#cm-8.3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8.3_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-08(03)(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the presence of unauthorized firmware within the system is detected using {{ insert: param, cm-08.03_odp.03 }} {{ insert: param, cm-08.03_odp.04 }};", - "links": [ - { - "href": "#cm-8.3_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-8.3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8.3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-08(03)(b)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-8.3_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-08(03)(b)[01]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-08.03_odp.05 }} are taken when unauthorized hardware is detected;", - "links": [ - { - "href": "#cm-8.3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8.3_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-08(03)(b)[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-08.03_odp.05 }} are taken when unauthorized software is detected;", - "links": [ - { - "href": "#cm-8.3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8.3_obj.b-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-08(03)(b)[03]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-08.03_odp.05 }} are taken when unauthorized firmware is detected.", - "links": [ - { - "href": "#cm-8.3_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-8.3_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-8.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-08(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing system component inventory\n\nconfiguration management plan\n\nsystem design documentation\n\nsystem security plan\n\nsystem component inventory\n\nchange control records\n\nalerts/notifications of unauthorized components within the system\n\nsystem monitoring records\n\nsystem maintenance records\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-8.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-08(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with component inventory management responsibilities\n\norganizational personnel with responsibilities for managing the automated mechanisms implementing unauthorized system component detection\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "cm-8.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-08(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for detection of unauthorized system components\n\norganizational processes for taking action when unauthorized system components are detected\n\nautomated mechanisms supporting and/or implementing the detection of unauthorized system components\n\nautomated mechanisms supporting and/or implementing actions taken when unauthorized system components are detected" - } - ] - } - ] - }, - { - "id": "cm-8.4", - "class": "SP800-53-enhancement", - "title": "Accountability Information", - "params": [ - { - "id": "cm-08.04_odp", - "props": [ - { - "name": "alt-identifier", - "value": "cm-8.4_prm_1" - }, - { - "name": "label", - "value": "CM-08(04)_ODP", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "position and role" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CM-08(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-8(4)" - }, - { - "name": "label", - "value": "CM-08(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-08.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#cm-8", - "rel": "required" - }, - { - "href": "#ac-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-8.4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Include in the system component inventory information, a means for identifying by {{ insert: param, cm-08.04_odp }} , individuals responsible and accountable for administering those components." - }, - { - "id": "cm-8.4_gdn", - "name": "guidance", - "prose": "Identifying individuals who are responsible and accountable for administering system components ensures that the assigned components are properly administered and that organizations can contact those individuals if some action is required (e.g., when the component is determined to be the source of a breach, needs to be recalled or replaced, or needs to be relocated)." - }, - { - "id": "cm-8.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-08(04)", - "class": "sp800-53a" - } - ], - "prose": "individuals responsible and accountable for administering system components are identified by {{ insert: param, cm-08.04_odp }} in the system component inventory.", - "links": [ - { - "href": "#cm-8.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-8.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-08(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing system component inventory\n\nconfiguration management plan\n\nsystem security plan\n\nsystem component inventory\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-8.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-08(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with component inventory management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "cm-8.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-08(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for managing the system component inventory\n\nmechanisms supporting and/or implementing the system component inventory" - } - ] - } - ] - } - ] - }, - { - "id": "cm-9", - "class": "SP800-53", - "title": "Configuration Management Plan", - "params": [ - { - "id": "cm-09_odp", - "props": [ - { - "name": "alt-identifier", - "value": "cm-9_prm_1" - }, - { - "name": "label", - "value": "CM-09_ODP", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to review and approve the configuration management plan is/are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CM-09", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-9" - }, - { - "name": "label", - "value": "CM-09", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-09" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#20db4e66-e257-450c-b2e4-2bb9a62a2c88", - "rel": "reference" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ra-8", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-9_smt", - "name": "statement", - "prose": "Develop, document, and implement a configuration management plan for the system that:", - "parts": [ - { - "id": "cm-9_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Addresses roles, responsibilities, and configuration management processes and procedures;" - }, - { - "id": "cm-9_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Establishes a process for identifying configuration items throughout the system development life cycle and for managing the configuration of the configuration items;" - }, - { - "id": "cm-9_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Defines the configuration items for the system and places the configuration items under configuration management;" - }, - { - "id": "cm-9_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Is reviewed and approved by {{ insert: param, cm-09_odp }} ; and" - }, - { - "id": "cm-9_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Protects the configuration management plan from unauthorized disclosure and modification." - } - ] - }, - { - "id": "cm-9_gdn", - "name": "guidance", - "prose": "Configuration management activities occur throughout the system development life cycle. As such, there are developmental configuration management activities (e.g., the control of code and software libraries) and operational configuration management activities (e.g., control of installed components and how the components are configured). Configuration management plans satisfy the requirements in configuration management policies while being tailored to individual systems. Configuration management plans define processes and procedures for how configuration management is used to support system development life cycle activities.\n\nConfiguration management plans are generated during the development and acquisition stage of the system development life cycle. The plans describe how to advance changes through change management processes; update configuration settings and baselines; maintain component inventories; control development, test, and operational environments; and develop, release, and update key documents.\n\nOrganizations can employ templates to help ensure the consistent and timely development and implementation of configuration management plans. Templates can represent a configuration management plan for the organization with subsets of the plan implemented on a system by system basis. Configuration management approval processes include the designation of key stakeholders responsible for reviewing and approving proposed changes to systems, and personnel who conduct security and privacy impact analyses prior to the implementation of changes to the systems. Configuration items are the system components, such as the hardware, software, firmware, and documentation to be configuration-managed. As systems continue through the system development life cycle, new configuration items may be identified, and some existing configuration items may no longer need to be under configuration control." - }, - { - "id": "cm-9_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "FedRAMP does not provide a template for the Configuration Management Plan. However, NIST SP 800-128, Guide for Security-Focused Configuration Management of Information Systems, provides guidelines for the implementation of CM controls as well as a sample CMP outline in Appendix D of the Guide" - }, - { - "id": "cm-9_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-09", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-9_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-09[01]", - "class": "sp800-53a" - } - ], - "prose": "a configuration management plan for the system is developed and documented;", - "links": [ - { - "href": "#cm-9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-9_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-09[02]", - "class": "sp800-53a" - } - ], - "prose": "a configuration management plan for the system is implemented;", - "links": [ - { - "href": "#cm-9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-9_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-09a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-9_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-09a.[01]", - "class": "sp800-53a" - } - ], - "prose": "the configuration management plan addresses roles;", - "links": [ - { - "href": "#cm-9_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-9_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-09a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the configuration management plan addresses responsibilities;", - "links": [ - { - "href": "#cm-9_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-9_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-09a.[03]", - "class": "sp800-53a" - } - ], - "prose": "the configuration management plan addresses configuration management processes and procedures;", - "links": [ - { - "href": "#cm-9_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-9_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-9_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-09b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-9_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-09b.[01]", - "class": "sp800-53a" - } - ], - "prose": "the configuration management plan establishes a process for identifying configuration items throughout the system development life cycle;", - "links": [ - { - "href": "#cm-9_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-9_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-09b.[02]", - "class": "sp800-53a" - } - ], - "prose": "the configuration management plan establishes a process for managing the configuration of the configuration items;", - "links": [ - { - "href": "#cm-9_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-9_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-9_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-09c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-9_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-09c.[01]", - "class": "sp800-53a" - } - ], - "prose": "the configuration management plan defines the configuration items for the system;", - "links": [ - { - "href": "#cm-9_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-9_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-09c.[02]", - "class": "sp800-53a" - } - ], - "prose": "the configuration management plan places the configuration items under configuration management;", - "links": [ - { - "href": "#cm-9_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-9_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-9_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-09d.", - "class": "sp800-53a" - } - ], - "prose": "the configuration management plan is reviewed and approved by {{ insert: param, cm-09_odp }};", - "links": [ - { - "href": "#cm-9_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-9_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-09e.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-9_obj.e-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-09e.[01]", - "class": "sp800-53a" - } - ], - "prose": "the configuration management plan is protected from unauthorized disclosure;", - "links": [ - { - "href": "#cm-9_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-9_obj.e-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-09e.[02]", - "class": "sp800-53a" - } - ], - "prose": "the configuration management plan is protected from unauthorized modification.", - "links": [ - { - "href": "#cm-9_smt.e", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-9_smt.e", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-9_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-09-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing configuration management planning\n\nconfiguration management plan\n\nsystem design documentation\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-9_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-09-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for developing the configuration management plan\n\norganizational personnel with responsibilities for implementing and managing processes defined in the configuration management plan\n\norganizational personnel with responsibilities for protecting the configuration management plan\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "cm-9_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-09-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for developing and documenting the configuration management plan\n\norganizational processes for identifying and managing configuration items\n\norganizational processes for protecting the configuration management plan\n\nmechanisms implementing the configuration management plan\n\nmechanisms for managing configuration items\n\nmechanisms for protecting the configuration management plan" - } - ] - } - ] - }, - { - "id": "cm-10", - "class": "SP800-53", - "title": "Software Usage Restrictions", - "props": [ - { - "name": "label", - "value": "CM-10", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-10" - }, - { - "name": "label", - "value": "CM-10", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-10" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-30", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-10_smt", - "name": "statement", - "parts": [ - { - "id": "cm-10_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Use software and associated documentation in accordance with contract agreements and copyright laws;" - }, - { - "id": "cm-10_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Track the use of software and associated documentation protected by quantity licenses to control copying and distribution; and" - }, - { - "id": "cm-10_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Control and document the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work." - } - ] - }, - { - "id": "cm-10_gdn", - "name": "guidance", - "prose": "Software license tracking can be accomplished by manual or automated methods, depending on organizational needs. Examples of contract agreements include software license agreements and non-disclosure agreements." - }, - { - "id": "cm-10_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-10", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-10_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-10a.", - "class": "sp800-53a" - } - ], - "prose": "software and associated documentation are used in accordance with contract agreements and copyright laws;", - "links": [ - { - "href": "#cm-10_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-10_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-10b.", - "class": "sp800-53a" - } - ], - "prose": "the use of software and associated documentation protected by quantity licenses is tracked to control copying and distribution;", - "links": [ - { - "href": "#cm-10_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-10_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-10c.", - "class": "sp800-53a" - } - ], - "prose": "the use of peer-to-peer file sharing technology is controlled and documented to ensure that peer-to-peer file sharing is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work.", - "links": [ - { - "href": "#cm-10_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-10_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-10_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-10-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nsoftware usage restrictions\n\nsoftware contract agreements and copyright laws\n\nsite license documentation\n\nlist of software usage restrictions\n\nsoftware license tracking reports\n\nconfiguration management plan\n\nsystem security plan\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-10_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-10-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel operating, using, and/or maintaining the system\n\norganizational personnel with software license management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "cm-10_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-10-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for tracking the use of software protected by quantity licenses\n\norganizational processes for controlling/documenting the use of peer-to-peer file sharing technology\n\nmechanisms implementing software license tracking\n\nmechanisms implementing and controlling the use of peer-to-peer files sharing technology" - } - ] - } - ] - }, - { - "id": "cm-11", - "class": "SP800-53", - "title": "User-installed Software", - "params": [ - { - "id": "cm-11_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cm-11_prm_1" - }, - { - "name": "label", - "value": "CM-11_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "policies", - "guidelines": [ - { - "prose": "policies governing the installation of software by users are defined;" - } - ] - }, - { - "id": "cm-11_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "cm-11_prm_2" - }, - { - "name": "label", - "value": "CM-11_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "methods", - "guidelines": [ - { - "prose": "methods used to enforce software installation policies are defined;" - } - ] - }, - { - "id": "cm-11_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "cm-11_prm_3" - }, - { - "name": "label", - "value": "CM-11_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "Continuously (via CM-7 (5))" - } - ], - "guidelines": [ - { - "prose": "frequency with which to monitor compliance is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CM-11", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-11" - }, - { - "name": "label", - "value": "CM-11", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-11" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-11_smt", - "name": "statement", - "parts": [ - { - "id": "cm-11_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Establish {{ insert: param, cm-11_odp.01 }} governing the installation of software by users;" - }, - { - "id": "cm-11_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Enforce software installation policies through the following methods: {{ insert: param, cm-11_odp.02 }} ; and" - }, - { - "id": "cm-11_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Monitor policy compliance {{ insert: param, cm-11_odp.03 }}." - } - ] - }, - { - "id": "cm-11_gdn", - "name": "guidance", - "prose": "If provided the necessary privileges, users can install software in organizational systems. To maintain control over the software installed, organizations identify permitted and prohibited actions regarding software installation. Permitted software installations include updates and security patches to existing software and downloading new applications from organization-approved \"app stores.\" Prohibited software installations include software with unknown or suspect pedigrees or software that organizations consider potentially malicious. Policies selected for governing user-installed software are organization-developed or provided by some external entity. Policy enforcement methods can include procedural methods and automated methods." - }, - { - "id": "cm-11_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-11", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-11_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-11a.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cm-11_odp.01 }} governing the installation of software by users are established;", - "links": [ - { - "href": "#cm-11_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-11_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-11b.", - "class": "sp800-53a" - } - ], - "prose": "software installation policies are enforced through {{ insert: param, cm-11_odp.02 }};", - "links": [ - { - "href": "#cm-11_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-11_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-11c.", - "class": "sp800-53a" - } - ], - "prose": "compliance with {{ insert: param, cm-11_odp.01 }} is monitored {{ insert: param, cm-11_odp.03 }}.", - "links": [ - { - "href": "#cm-11_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-11_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-11_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-11-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing user-installed software\n\nconfiguration management plan\n\nsystem security plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of rules governing user installed software\n\nsystem monitoring records\n\nsystem audit records\n\ncontinuous monitoring strategy\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-11_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-11-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for governing user-installed software\n\norganizational personnel operating, using, and/or maintaining the system\n\norganizational personnel monitoring compliance with user-installed software policy\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "cm-11_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-11-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes governing user-installed software on the system\n\nmechanisms enforcing policies and methods for governing the installation of software by users\n\nmechanisms monitoring policy compliance" - } - ] - } - ] - }, - { - "id": "cm-12", - "class": "SP800-53", - "title": "Information Location", - "params": [ - { - "id": "cm-12_odp", - "props": [ - { - "name": "alt-identifier", - "value": "cm-12_prm_1" - }, - { - "name": "label", - "value": "CM-12_ODP", - "class": "sp800-53a" - } - ], - "label": "information", - "guidelines": [ - { - "prose": "information for which the location is to be identified and documented is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CM-12", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-12" - }, - { - "name": "label", - "value": "CM-12", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-12" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#628d22a1-6a11-4784-bc59-5cd9497b5445", - "rel": "reference" - }, - { - "href": "#e72fde0b-6fc2-497e-a9db-d8fce5a11b8a", - "rel": "reference" - }, - { - "href": "#9be5d661-421f-41ad-854e-86f98b811891", - "rel": "reference" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ac-23", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-5", - "rel": "related" - }, - { - "href": "#ra-2", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-17", - "rel": "related" - }, - { - "href": "#sc-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-16", - "rel": "related" - }, - { - "href": "#sc-28", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-12_smt", - "name": "statement", - "parts": [ - { - "id": "cm-12_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Identify and document the location of {{ insert: param, cm-12_odp }} and the specific system components on which the information is processed and stored;" - }, - { - "id": "cm-12_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Identify and document the users who have access to the system and system components where the information is processed and stored; and" - }, - { - "id": "cm-12_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Document changes to the location (i.e., system or system components) where the information is processed and stored." - } - ] - }, - { - "id": "cm-12_gdn", - "name": "guidance", - "prose": "Information location addresses the need to understand where information is being processed and stored. Information location includes identifying where specific information types and information reside in system components and how information is being processed so that information flow can be understood and adequate protection and policy management provided for such information and system components. The security category of the information is also a factor in determining the controls necessary to protect the information and the system component where the information resides (see [FIPS 199](#628d22a1-6a11-4784-bc59-5cd9497b5445) ). The location of the information and system components is also a factor in the architecture and design of the system (see [SA-4](#sa-4), [SA-8](#sa-8), [SA-17](#sa-17))." - }, - { - "id": "cm-12_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CM-12 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "cm-12_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "According to FedRAMP Authorization Boundary Guidance" - } - ] - }, - { - "id": "cm-12_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-12", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-12_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-12a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-12_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-12a.[01]", - "class": "sp800-53a" - } - ], - "prose": "the location of {{ insert: param, cm-12_odp }} is identified and documented;", - "links": [ - { - "href": "#cm-12_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-12_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-12a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the specific system components on which {{ insert: param, cm-12_odp }} is processed are identified and documented;", - "links": [ - { - "href": "#cm-12_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-12_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-12a.[03]", - "class": "sp800-53a" - } - ], - "prose": "the specific system components on which {{ insert: param, cm-12_odp }} is stored are identified and documented;", - "links": [ - { - "href": "#cm-12_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-12_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-12_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-12b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-12_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-12b.[01]", - "class": "sp800-53a" - } - ], - "prose": "the users who have access to the system and system components where {{ insert: param, cm-12_odp }} is processed are identified and documented;", - "links": [ - { - "href": "#cm-12_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-12_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-12b.[02]", - "class": "sp800-53a" - } - ], - "prose": "the users who have access to the system and system components where {{ insert: param, cm-12_odp }} is stored are identified and documented;", - "links": [ - { - "href": "#cm-12_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-12_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-12_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-12c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-12_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-12c.[01]", - "class": "sp800-53a" - } - ], - "prose": "changes to the location (i.e., system or system components) where {{ insert: param, cm-12_odp }} is processed are documented;", - "links": [ - { - "href": "#cm-12_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-12_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-12c.[02]", - "class": "sp800-53a" - } - ], - "prose": "changes to the location (i.e., system or system components) where {{ insert: param, cm-12_odp }} is stored are documented.", - "links": [ - { - "href": "#cm-12_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-12_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-12_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-12_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-12-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing identification and documentation of information location\n\nconfiguration management plan\n\nsystem design documentation\n\nsystem architecture documentation\n\nPII inventory documentation\n\ndata mapping documentation\n\naudit records\n\nlist of users with system and system component access\n\nchange control records\n\nsystem component inventory\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-12_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-12-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for managing information location and user access to information\n\norganizational personnel with responsibilities for operating, using, and/or maintaining the system\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "cm-12_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-12-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes governing information location\n\nmechanisms enforcing policies and methods for governing information location" - } - ] - } - ], - "controls": [ - { - "id": "cm-12.1", - "class": "SP800-53-enhancement", - "title": "Automated Tools to Support Information Location", - "params": [ - { - "id": "cm-12.01_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cm-12.1_prm_1" - }, - { - "name": "label", - "value": "CM-12(01)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "information by information type", - "constraints": [ - { - "description": "Federal data and system data that must be protected at the High or Moderate impact levels" - } - ], - "guidelines": [ - { - "prose": "information to be protected is defined by information type;" - } - ] - }, - { - "id": "cm-12.01_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "cm-12.1_prm_2" - }, - { - "name": "label", - "value": "CM-12(01)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "system components", - "guidelines": [ - { - "prose": "system components where the information is located are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CM-12(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-12(1)" - }, - { - "name": "label", - "value": "CM-12(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-12.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#cm-12", - "rel": "required" - } - ], - "parts": [ - { - "id": "cm-12.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Use automated tools to identify {{ insert: param, cm-12.01_odp.01 }} on {{ insert: param, cm-12.01_odp.02 }} to ensure controls are in place to protect organizational information and individual privacy." - }, - { - "id": "cm-12.1_gdn", - "name": "guidance", - "prose": "The use of automated tools helps to increase the effectiveness and efficiency of the information location capability implemented within the system. Automation also helps organizations manage the data produced during information location activities and share such information across the organization. The output of automated information location tools can be used to guide and inform system architecture and design decisions." - }, - { - "id": "cm-12.1_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CM-12 (1) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "cm-12.1_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "According to FedRAMP Authorization Boundary Guidance." - } - ] - }, - { - "id": "cm-12.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-12(01)", - "class": "sp800-53a" - } - ], - "prose": "automated tools are used to identify {{ insert: param, cm-12.01_odp.01 }} on {{ insert: param, cm-12.01_odp.02 }} to ensure that controls are in place to protect organizational information and individual privacy.", - "links": [ - { - "href": "#cm-12.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-12.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-12(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing identification and documentation of information location\n\nconfiguration management plan\n\nsystem design documentation\n\nPII inventory documentation\n\ndata mapping documentation\n\nchange control records\n\nsystem component inventory\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-12.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-12(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for managing information location\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "cm-12.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-12(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes governing information location\n\nautomated mechanisms enforcing policies and methods for governing information location\n\nautomated tools used to identify information on system components" - } - ] - } - ] - } - ] - }, - { - "id": "cm-14", - "class": "SP800-53", - "title": "Signed Components", - "params": [ - { - "id": "cm-14_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-14_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cm-14_odp.02" - } - ], - "label": "organization-defined software and firmware components" - }, - { - "id": "cm-14_odp.01", - "props": [ - { - "name": "label", - "value": "CM-14_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "software components", - "guidelines": [ - { - "prose": "software components requiring verification of a digitally signed certificate before installation are defined;" - } - ] - }, - { - "id": "cm-14_odp.02", - "props": [ - { - "name": "label", - "value": "CM-14_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "firmware components", - "guidelines": [ - { - "prose": "firmware components requiring verification of a digitally signed certificate before installation are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CM-14", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CM-14" - }, - { - "name": "label", - "value": "CM-14", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cm-14" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#98d415ca-7281-4064-9931-0c366637e324", - "rel": "reference" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "cm-14_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Prevent the installation of {{ insert: param, cm-14_prm_1 }} without verification that the component has been digitally signed using a certificate that is recognized and approved by the organization." - }, - { - "id": "cm-14_gdn", - "name": "guidance", - "prose": "Software and firmware components prevented from installation unless signed with recognized and approved certificates include software and firmware version updates, patches, service packs, device drivers, and basic input/output system updates. Organizations can identify applicable software and firmware components by type, by specific items, or a combination of both. Digital signatures and organizational verification of such signatures is a method of code authentication." - }, - { - "id": "cm-14_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "If digital signatures/certificates are unavailable, alternative cryptographic integrity checks (hashes, self-signed certs, etc.) can be utilized." - }, - { - "id": "cm-14_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CM-14", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cm-14_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-14[01]", - "class": "sp800-53a" - } - ], - "prose": "the installation of {{ insert: param, cm-14_odp.01 }} is prevented unless it is verified that the software has been digitally signed using a certificate recognized and approved by the organization;", - "links": [ - { - "href": "#cm-14_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-14_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CM-14[02]", - "class": "sp800-53a" - } - ], - "prose": "the installation of {{ insert: param, cm-14_odp.02 }} is prevented unless it is verified that the firmware has been digitally signed using a certificate recognized and approved by the organization.", - "links": [ - { - "href": "#cm-14_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cm-14_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cm-14_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CM-14-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Configuration management policy\n\nprocedures addressing digitally signed certificates for software and firmware components\n\nconfiguration management plan\n\nsystem security plan\n\nsystem design documentation\n\nchange control records\n\nsystem component inventory\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cm-14_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CM-14-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for verifying digitally signed certificates for software and firmware component installation\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "cm-14_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CM-14-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes governing information location\n\nmechanisms enforcing policies and methods for governing information location\n\nautomated tools supporting or implementing digitally signatures for software and firmware components\n\nautomated tools supporting or implementing verification of digital signatures for software and firmware component installation" - } - ] - } - ] - } - ] - }, - { - "id": "cp", - "class": "family", - "title": "Contingency Planning", - "controls": [ - { - "id": "cp-1", - "class": "SP800-53", - "title": "Policy and Procedures", - "params": [ - { - "id": "cp-1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cp-01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cp-01_odp.02" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "cp-01_odp.01", - "props": [ - { - "name": "label", - "value": "CP-01_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the contingency planning policy is to be disseminated is/are defined;" - } - ] - }, - { - "id": "cp-01_odp.02", - "props": [ - { - "name": "label", - "value": "CP-01_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the contingency planning procedures are to be disseminated is/are defined;" - } - ] - }, - { - "id": "cp-01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "cp-1_prm_2" - }, - { - "name": "label", - "value": "CP-01_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "organization-level", - "mission/business process-level", - "system-level" - ] - } - }, - { - "id": "cp-01_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "cp-1_prm_3" - }, - { - "name": "label", - "value": "CP-01_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "official", - "guidelines": [ - { - "prose": "an official to manage the contingency planning policy and procedures is defined;" - } - ] - }, - { - "id": "cp-01_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "cp-1_prm_4" - }, - { - "name": "label", - "value": "CP-01_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current contingency planning policy is reviewed and updated is defined;" - } - ] - }, - { - "id": "cp-01_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "cp-1_prm_5" - }, - { - "name": "label", - "value": "CP-01_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that would require the current contingency planning policy to be reviewed and updated are defined;" - } - ] - }, - { - "id": "cp-01_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "cp-1_prm_6" - }, - { - "name": "label", - "value": "CP-01_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current contingency planning procedures are reviewed and updated is defined;" - } - ] - }, - { - "id": "cp-01_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "cp-1_prm_7" - }, - { - "name": "label", - "value": "CP-01_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "events", - "constraints": [ - { - "description": "significant changes" - } - ], - "guidelines": [ - { - "prose": "events that would require procedures to be reviewed and updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CP-01", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-1" - }, - { - "name": "label", - "value": "CP-01", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#c7ac44e8-10db-4b64-b2b9-9e32ec1efed0", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#bc39f179-c735-4da2-b7a7-b2b622119755", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#511f6832-23ca-49a3-8c0f-ce493373cab8", - "rel": "reference" - }, - { - "href": "#4c0ec2ee-a0d6-428a-9043-4504bc3ade6f", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-1_smt", - "name": "statement", - "parts": [ - { - "id": "cp-1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, a policy that addresses Contingency Planning MUST be associated with CP-1 part a.", - "class": "policy" - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, at least one procedure that addresses Contingency Planning MUST be associated with CP-1 part a.", - "class": "procedure" - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, document, and disseminate to {{ insert: param, cp-1_prm_1 }}:", - "parts": [ - { - "id": "cp-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, cp-01_odp.03 }} contingency planning policy that:", - "parts": [ - { - "id": "cp-1_smt.a.1.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "cp-1_smt.a.1.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and" - } - ] - }, - { - "id": "cp-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the contingency planning policy and the associated contingency planning controls;" - } - ] - }, - { - "id": "cp-1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Designate an {{ insert: param, cp-01_odp.04 }} to manage the development, documentation, and dissemination of the contingency planning policy and procedures; and" - }, - { - "id": "cp-1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the current contingency planning:", - "parts": [ - { - "id": "cp-1_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Policy {{ insert: param, cp-01_odp.05 }} and following {{ insert: param, cp-01_odp.06 }} ; and" - }, - { - "id": "cp-1_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures {{ insert: param, cp-01_odp.07 }} and following {{ insert: param, cp-01_odp.08 }}." - } - ] - } - ] - }, - { - "id": "cp-1_gdn", - "name": "guidance", - "prose": "Contingency planning policy and procedures address the controls in the CP family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of contingency planning policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to contingency planning policy and procedures include assessment or audit findings, security incidents or breaches, or changes in laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure." - }, - { - "id": "cp-1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-01a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-01a.[01]", - "class": "sp800-53a" - } - ], - "prose": "a contingency planning policy is developed and documented;", - "links": [ - { - "href": "#cp-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-01a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the contingency planning policy is disseminated to {{ insert: param, cp-01_odp.01 }};", - "links": [ - { - "href": "#cp-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-1_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-01a.[03]", - "class": "sp800-53a" - } - ], - "prose": "contingency planning procedures to facilitate the implementation of the contingency planning policy and associated contingency planning controls are developed and documented;", - "links": [ - { - "href": "#cp-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-1_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-01a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the contingency planning procedures are disseminated to {{ insert: param, cp-01_odp.02 }};", - "links": [ - { - "href": "#cp-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-1_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-01a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-1_obj.a.1.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-01a.01(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-1_obj.a.1.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-01a.01(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, cp-01_odp.03 }} contingency planning policy addresses purpose;", - "links": [ - { - "href": "#cp-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-1_obj.a.1.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-01a.01(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, cp-01_odp.03 }} contingency planning policy addresses scope;", - "links": [ - { - "href": "#cp-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-1_obj.a.1.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-01a.01(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, cp-01_odp.03 }} contingency planning policy addresses roles;", - "links": [ - { - "href": "#cp-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-1_obj.a.1.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-01a.01(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, cp-01_odp.03 }} contingency planning policy addresses responsibilities;", - "links": [ - { - "href": "#cp-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-1_obj.a.1.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-01a.01(a)[05]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, cp-01_odp.03 }} contingency planning policy addresses management commitment;", - "links": [ - { - "href": "#cp-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-1_obj.a.1.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-01a.01(a)[06]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, cp-01_odp.03 }} contingency planning policy addresses coordination among organizational entities;", - "links": [ - { - "href": "#cp-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-1_obj.a.1.a-7", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-01a.01(a)[07]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, cp-01_odp.03 }} contingency planning policy addresses compliance;", - "links": [ - { - "href": "#cp-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-1_obj.a.1.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-01a.01(b)", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, cp-01_odp.03 }} contingency planning policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines;", - "links": [ - { - "href": "#cp-1_smt.a.1.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-1_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-01b.", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, cp-01_odp.04 }} is designated to manage the development, documentation, and dissemination of the contingency planning policy and procedures;", - "links": [ - { - "href": "#cp-1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-01c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-1_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-01c.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-1_obj.c.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-01c.01[01]", - "class": "sp800-53a" - } - ], - "prose": "the current contingency planning policy is reviewed and updated {{ insert: param, cp-01_odp.05 }};", - "links": [ - { - "href": "#cp-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-1_obj.c.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-01c.01[02]", - "class": "sp800-53a" - } - ], - "prose": "the current contingency planning policy is reviewed and updated following {{ insert: param, cp-01_odp.06 }};", - "links": [ - { - "href": "#cp-1_smt.c.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-1_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-01c.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-1_obj.c.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-01c.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the current contingency planning procedures are reviewed and updated {{ insert: param, cp-01_odp.07 }};", - "links": [ - { - "href": "#cp-1_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-1_obj.c.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-01c.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the current contingency planning procedures are reviewed and updated following {{ insert: param, cp-01_odp.08 }}.", - "links": [ - { - "href": "#cp-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-1_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-01-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy and procedures\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-01-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency planning responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - }, - { - "id": "cp-2", - "class": "SP800-53", - "title": "Contingency Plan", - "params": [ - { - "id": "cp-2_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cp-02_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cp-02_odp.02" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "cp-2_prm_2", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cp-02_odp.03" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cp-02_odp.04" - } - ], - "label": "organization-defined key contingency personnel (identified by name and/or by role) and organizational elements" - }, - { - "id": "cp-2_prm_4", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cp-02_odp.06" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cp-02_odp.07" - } - ], - "label": "organization-defined key contingency personnel (identified by name and/or by role) and organizational elements" - }, - { - "id": "cp-02_odp.01", - "props": [ - { - "name": "label", - "value": "CP-02_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to review a contingency plan is/are defined;" - } - ] - }, - { - "id": "cp-02_odp.02", - "props": [ - { - "name": "label", - "value": "CP-02_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to approve a contingency plan is/are defined;" - } - ] - }, - { - "id": "cp-02_odp.03", - "props": [ - { - "name": "label", - "value": "CP-02_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "key contingency personnel", - "guidelines": [ - { - "prose": "key contingency personnel (identified by name and/or by role) to whom copies of the contingency plan are distributed are defined;" - } - ] - }, - { - "id": "cp-02_odp.04", - "props": [ - { - "name": "label", - "value": "CP-02_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "organizational elements", - "guidelines": [ - { - "prose": "key contingency organizational elements to which copies of the contingency plan are distributed are defined;" - } - ] - }, - { - "id": "cp-02_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "cp-2_prm_3" - }, - { - "name": "label", - "value": "CP-02_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "frequency of contingency plan review is defined;" - } - ] - }, - { - "id": "cp-02_odp.06", - "props": [ - { - "name": "label", - "value": "CP-02_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "key contingency personnel", - "guidelines": [ - { - "prose": "key contingency personnel (identified by name and/or by role) to communicate changes to are defined;" - } - ] - }, - { - "id": "cp-02_odp.07", - "props": [ - { - "name": "label", - "value": "CP-02_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "organizational elements", - "guidelines": [ - { - "prose": "key contingency organizational elements to communicate changes to are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CP-02", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-2" - }, - { - "name": "label", - "value": "CP-02", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#bc39f179-c735-4da2-b7a7-b2b622119755", - "rel": "reference" - }, - { - "href": "#d4296805-2dca-4c63-a95f-eeccaa826aec", - "rel": "reference" - }, - { - "href": "#cp-3", - "rel": "related" - }, - { - "href": "#cp-4", - "rel": "related" - }, - { - "href": "#cp-6", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - }, - { - "href": "#cp-8", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#cp-10", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#cp-11", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#cp-13", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-6", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - }, - { - "href": "#ir-9", - "rel": "related" - }, - { - "href": "#ma-6", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-11", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sa-20", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-23", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-2_smt", - "name": "statement", - "parts": [ - { - "id": "cp-2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop a contingency plan for the system that:", - "parts": [ - { - "id": "cp-2_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Identifies essential mission and business functions and associated contingency requirements;" - }, - { - "id": "cp-2_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Provides recovery objectives, restoration priorities, and metrics;" - }, - { - "id": "cp-2_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Addresses contingency roles, responsibilities, assigned individuals with contact information;" - }, - { - "id": "cp-2_smt.a.4", - "name": "item", - "props": [ - { - "name": "label", - "value": "4." - } - ], - "prose": "Addresses maintaining essential mission and business functions despite a system disruption, compromise, or failure;" - }, - { - "id": "cp-2_smt.a.5", - "name": "item", - "props": [ - { - "name": "label", - "value": "5." - } - ], - "prose": "Addresses eventual, full system restoration without deterioration of the controls originally planned and implemented;" - }, - { - "id": "cp-2_smt.a.6", - "name": "item", - "props": [ - { - "name": "label", - "value": "6." - } - ], - "prose": "Addresses the sharing of contingency information; and" - }, - { - "id": "cp-2_smt.a.7", - "name": "item", - "props": [ - { - "name": "label", - "value": "7." - } - ], - "prose": "Is reviewed and approved by {{ insert: param, cp-2_prm_1 }};" - } - ] - }, - { - "id": "cp-2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Distribute copies of the contingency plan to {{ insert: param, cp-2_prm_2 }};" - }, - { - "id": "cp-2_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Coordinate contingency planning activities with incident handling activities;" - }, - { - "id": "cp-2_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Review the contingency plan for the system {{ insert: param, cp-02_odp.05 }};" - }, - { - "id": "cp-2_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Update the contingency plan to address changes to the organization, system, or environment of operation and problems encountered during contingency plan implementation, execution, or testing;" - }, - { - "id": "cp-2_smt.f", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "f." - } - ], - "prose": "Communicate contingency plan changes to {{ insert: param, cp-2_prm_4 }};" - }, - { - "id": "cp-2_smt.g", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "g." - } - ], - "prose": "Incorporate lessons learned from contingency plan testing, training, or actual contingency activities into contingency testing and training; and" - }, - { - "id": "cp-2_smt.h", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "h." - } - ], - "prose": "Protect the contingency plan from unauthorized disclosure and modification." - } - ] - }, - { - "id": "cp-2_gdn", - "name": "guidance", - "prose": "Contingency planning for systems is part of an overall program for achieving continuity of operations for organizational mission and business functions. Contingency planning addresses system restoration and implementation of alternative mission or business processes when systems are compromised or breached. Contingency planning is considered throughout the system development life cycle and is a fundamental part of the system design. Systems can be designed for redundancy, to provide backup capabilities, and for resilience. Contingency plans reflect the degree of restoration required for organizational systems since not all systems need to fully recover to achieve the level of continuity of operations desired. System recovery objectives reflect applicable laws, executive orders, directives, regulations, policies, standards, guidelines, organizational risk tolerance, and system impact level.\n\nActions addressed in contingency plans include orderly system degradation, system shutdown, fallback to a manual mode, alternate information flows, and operating in modes reserved for when systems are under attack. By coordinating contingency planning with incident handling activities, organizations ensure that the necessary planning activities are in place and activated in the event of an incident. Organizations consider whether continuity of operations during an incident conflicts with the capability to automatically disable the system, as specified in [IR-4(5)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ir-4.5) . Incident response planning is part of contingency planning for organizations and is addressed in the [IR](#ir) (Incident Response) family." - }, - { - "id": "cp-2_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CP-2 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "cp-2_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "CSPs must use the FedRAMP Information System Contingency Plan (ISCP) Template (available on the fedramp.gov: https://www.fedramp.gov/assets/resources/templates/SSP-A06-FedRAMP-ISCP-Template.docx)." - } - ] - }, - { - "id": "cp-2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-2_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02a.01", - "class": "sp800-53a" - } - ], - "prose": "a contingency plan for the system is developed that identifies essential mission and business functions and associated contingency requirements;", - "links": [ - { - "href": "#cp-2_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.a.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02a.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-2_obj.a.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02a.02[01]", - "class": "sp800-53a" - } - ], - "prose": "a contingency plan for the system is developed that provides recovery objectives;", - "links": [ - { - "href": "#cp-2_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.a.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02a.02[02]", - "class": "sp800-53a" - } - ], - "prose": "a contingency plan for the system is developed that provides restoration priorities;", - "links": [ - { - "href": "#cp-2_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.a.2-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02a.02[03]", - "class": "sp800-53a" - } - ], - "prose": "a contingency plan for the system is developed that provides metrics;", - "links": [ - { - "href": "#cp-2_smt.a.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-2_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.a.3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02a.03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-2_obj.a.3-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02a.03[01]", - "class": "sp800-53a" - } - ], - "prose": "a contingency plan for the system is developed that addresses contingency roles;", - "links": [ - { - "href": "#cp-2_smt.a.3", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.a.3-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02a.03[02]", - "class": "sp800-53a" - } - ], - "prose": "a contingency plan for the system is developed that addresses contingency responsibilities;", - "links": [ - { - "href": "#cp-2_smt.a.3", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.a.3-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02a.03[03]", - "class": "sp800-53a" - } - ], - "prose": "a contingency plan for the system is developed that addresses assigned individuals with contact information;", - "links": [ - { - "href": "#cp-2_smt.a.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-2_smt.a.3", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.a.4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02a.04", - "class": "sp800-53a" - } - ], - "prose": "a contingency plan for the system is developed that addresses maintaining essential mission and business functions despite a system disruption, compromise, or failure;", - "links": [ - { - "href": "#cp-2_smt.a.4", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.a.5", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02a.05", - "class": "sp800-53a" - } - ], - "prose": "a contingency plan for the system is developed that addresses eventual, full-system restoration without deterioration of the controls originally planned and implemented;", - "links": [ - { - "href": "#cp-2_smt.a.5", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.a.6", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02a.06", - "class": "sp800-53a" - } - ], - "prose": "a contingency plan for the system is developed that addresses the sharing of contingency information;", - "links": [ - { - "href": "#cp-2_smt.a.6", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.a.7", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02a.07", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-2_obj.a.7-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02a.07[01]", - "class": "sp800-53a" - } - ], - "prose": "a contingency plan for the system is developed that is reviewed by {{ insert: param, cp-02_odp.01 }};", - "links": [ - { - "href": "#cp-2_smt.a.7", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.a.7-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02a.07[02]", - "class": "sp800-53a" - } - ], - "prose": "a contingency plan for the system is developed that is approved by {{ insert: param, cp-02_odp.02 }};", - "links": [ - { - "href": "#cp-2_smt.a.7", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-2_smt.a.7", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-2_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02b.[01]", - "class": "sp800-53a" - } - ], - "prose": "copies of the contingency plan are distributed to {{ insert: param, cp-02_odp.03 }};", - "links": [ - { - "href": "#cp-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02b.[02]", - "class": "sp800-53a" - } - ], - "prose": "copies of the contingency plan are distributed to {{ insert: param, cp-02_odp.04 }};", - "links": [ - { - "href": "#cp-2_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02c.", - "class": "sp800-53a" - } - ], - "prose": "contingency planning activities are coordinated with incident handling activities;", - "links": [ - { - "href": "#cp-2_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02d.", - "class": "sp800-53a" - } - ], - "prose": "the contingency plan for the system is reviewed {{ insert: param, cp-02_odp.05 }};", - "links": [ - { - "href": "#cp-2_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02e.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-2_obj.e-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02e.[01]", - "class": "sp800-53a" - } - ], - "prose": "the contingency plan is updated to address changes to the organization, system, or environment of operation;", - "links": [ - { - "href": "#cp-2_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.e-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02e.[02]", - "class": "sp800-53a" - } - ], - "prose": "the contingency plan is updated to address problems encountered during contingency plan implementation, execution, or testing;", - "links": [ - { - "href": "#cp-2_smt.e", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-2_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.f", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02f.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-2_obj.f-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02f.[01]", - "class": "sp800-53a" - } - ], - "prose": "contingency plan changes are communicated to {{ insert: param, cp-02_odp.06 }};", - "links": [ - { - "href": "#cp-2_smt.f", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.f-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02f.[02]", - "class": "sp800-53a" - } - ], - "prose": "contingency plan changes are communicated to {{ insert: param, cp-02_odp.07 }};", - "links": [ - { - "href": "#cp-2_smt.f", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-2_smt.f", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.g", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02g.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-2_obj.g-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02g.[01]", - "class": "sp800-53a" - } - ], - "prose": "lessons learned from contingency plan testing or actual contingency activities are incorporated into contingency testing;", - "links": [ - { - "href": "#cp-2_smt.g", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.g-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02g.[02]", - "class": "sp800-53a" - } - ], - "prose": "lessons learned from contingency plan training or actual contingency activities are incorporated into contingency testing and training;", - "links": [ - { - "href": "#cp-2_smt.g", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-2_smt.g", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.h", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02h.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-2_obj.h-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02h.[01]", - "class": "sp800-53a" - } - ], - "prose": "the contingency plan is protected from unauthorized disclosure;", - "links": [ - { - "href": "#cp-2_smt.h", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_obj.h-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02h.[02]", - "class": "sp800-53a" - } - ], - "prose": "the contingency plan is protected from unauthorized modification.", - "links": [ - { - "href": "#cp-2_smt.h", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-2_smt.h", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-02-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency operations for the system\n\ncontingency plan\n\nevidence of contingency plan reviews and updates\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-02-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\norganizational personnel with incident handling responsibilities\n\norganizational personnel with knowledge of requirements for mission and business functions\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "cp-2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-02-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for contingency plan development, review, update, and protection\n\nmechanisms for developing, reviewing, updating, and/or protecting the contingency plan" - } - ] - } - ], - "controls": [ - { - "id": "cp-2.1", - "class": "SP800-53-enhancement", - "title": "Coordinate with Related Plans", - "props": [ - { - "name": "label", - "value": "CP-02(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-2(1)" - }, - { - "name": "label", - "value": "CP-02(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-02.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-2", - "rel": "required" - } - ], - "parts": [ - { - "id": "cp-2.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Coordinate contingency plan development with organizational elements responsible for related plans." - }, - { - "id": "cp-2.1_gdn", - "name": "guidance", - "prose": "Plans that are related to contingency plans include Business Continuity Plans, Disaster Recovery Plans, Critical Infrastructure Plans, Continuity of Operations Plans, Crisis Communications Plans, Insider Threat Implementation Plans, Data Breach Response Plans, Cyber Incident Response Plans, Breach Response Plans, and Occupant Emergency Plans." - }, - { - "id": "cp-2.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02(01)", - "class": "sp800-53a" - } - ], - "prose": "contingency plan development is coordinated with organizational elements responsible for related plans.", - "links": [ - { - "href": "#cp-2.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-02(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency operations for the system\n\ncontingency plan\n\nbusiness contingency plans\n\ndisaster recovery plans\n\ncontinuity of operations plans\n\ncrisis communications plans\n\ncritical infrastructure plans\n\ncyber incident response plan\n\ninsider threat implementation plans\n\noccupant emergency plans\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-2.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-02(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\norganizational personnel with information security responsibilities\n\npersonnel with responsibility for related plans" - } - ] - } - ] - }, - { - "id": "cp-2.2", - "class": "SP800-53-enhancement", - "title": "Capacity Planning", - "props": [ - { - "name": "label", - "value": "CP-02(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-2(2)" - }, - { - "name": "label", - "value": "CP-02(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-02.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-2", - "rel": "required" - }, - { - "href": "#pe-11", - "rel": "related" - }, - { - "href": "#pe-12", - "rel": "related" - }, - { - "href": "#pe-13", - "rel": "related" - }, - { - "href": "#pe-14", - "rel": "related" - }, - { - "href": "#pe-18", - "rel": "related" - }, - { - "href": "#sc-5", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-2.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Conduct capacity planning so that necessary capacity for information processing, telecommunications, and environmental support exists during contingency operations." - }, - { - "id": "cp-2.2_gdn", - "name": "guidance", - "prose": "Capacity planning is needed because different threats can result in a reduction of the available processing, telecommunications, and support services intended to support essential mission and business functions. Organizations anticipate degraded operations during contingency operations and factor the degradation into capacity planning. For capacity planning, environmental support refers to any environmental factor for which the organization determines that it needs to provide support in a contingency situation, even if in a degraded state. Such determinations are based on an organizational assessment of risk, system categorization (impact level), and organizational risk tolerance." - }, - { - "id": "cp-2.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02(02)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-2.2_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02(02)[01]", - "class": "sp800-53a" - } - ], - "prose": "capacity planning is conducted so that the necessary capacity exists during contingency operations for information processing;", - "links": [ - { - "href": "#cp-2.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2.2_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02(02)[02]", - "class": "sp800-53a" - } - ], - "prose": "capacity planning is conducted so that the necessary capacity exists during contingency operations for telecommunications;", - "links": [ - { - "href": "#cp-2.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2.2_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02(02)[03]", - "class": "sp800-53a" - } - ], - "prose": "capacity planning is conducted so that the necessary capacity exists during contingency operations for environmental support.", - "links": [ - { - "href": "#cp-2.2_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-2.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-02(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency operations for the system\n\ncontingency plan\n\ncapacity planning documents\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-2.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-02(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\norganizational personnel responsible for capacity planning\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "cp-2.3", - "class": "SP800-53-enhancement", - "title": "Resume Mission and Business Functions", - "params": [ - { - "id": "cp-02.03_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cp-2.3_prm_1" - }, - { - "name": "label", - "value": "CP-02(03)_ODP[01]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "all" - } - ] - }, - { - "id": "cp-02.03_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "cp-2.3_prm_2" - }, - { - "name": "label", - "value": "CP-02(03)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "time period defined in service provider and organization SLA" - } - ], - "guidelines": [ - { - "prose": "the contingency plan activation time period within which to resume mission and business functions is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CP-02(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-2(3)" - }, - { - "name": "label", - "value": "CP-02(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-02.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-2", - "rel": "required" - } - ], - "parts": [ - { - "id": "cp-2.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Plan for the resumption of {{ insert: param, cp-02.03_odp.01 }} mission and business functions within {{ insert: param, cp-02.03_odp.02 }} of contingency plan activation." - }, - { - "id": "cp-2.3_gdn", - "name": "guidance", - "prose": "Organizations may choose to conduct contingency planning activities to resume mission and business functions as part of business continuity planning or as part of business impact analyses. Organizations prioritize the resumption of mission and business functions. The time period for resuming mission and business functions may be dependent on the severity and extent of the disruptions to the system and its supporting infrastructure." - }, - { - "id": "cp-2.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02(03)", - "class": "sp800-53a" - } - ], - "prose": "the resumption of {{ insert: param, cp-02.03_odp.01 }} mission and business functions are planned for within {{ insert: param, cp-02.03_odp.02 }} of contingency plan activation.", - "links": [ - { - "href": "#cp-2.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-02(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency operations for the system\n\ncontingency plan\n\nbusiness impact assessment\n\nsystem security plan\n\nprivacy plan\n\nother related plans\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-2.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-02(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\norganizational personnel with knowledge of requirements for mission and business functions" - } - ] - }, - { - "id": "cp-2.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-02(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for resumption of missions and business functions" - } - ] - } - ] - }, - { - "id": "cp-2.5", - "class": "SP800-53-enhancement", - "title": "Continue Mission and Business Functions", - "params": [ - { - "id": "cp-02.05_odp", - "props": [ - { - "name": "alt-identifier", - "value": "cp-2.5_prm_1" - }, - { - "name": "label", - "value": "CP-02(05)_ODP", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "essential" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CP-02(05)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-2(5)" - }, - { - "name": "label", - "value": "CP-02(05)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-02.05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-2", - "rel": "required" - } - ], - "parts": [ - { - "id": "cp-2.5_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Plan for the continuance of {{ insert: param, cp-02.05_odp }} mission and business functions with minimal or no loss of operational continuity and sustains that continuity until full system restoration at primary processing and/or storage sites." - }, - { - "id": "cp-2.5_gdn", - "name": "guidance", - "prose": "Organizations may choose to conduct the contingency planning activities to continue mission and business functions as part of business continuity planning or business impact analyses. Primary processing and/or storage sites defined by organizations as part of contingency planning may change depending on the circumstances associated with the contingency." - }, - { - "id": "cp-2.5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-02(05)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-2.5_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02(05)[01]", - "class": "sp800-53a" - } - ], - "prose": "the continuance of {{ insert: param, cp-02.05_odp }} mission and business functions with minimal or no loss of operational continuity is planned for;", - "links": [ - { - "href": "#cp-2.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2.5_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02(05)[02]", - "class": "sp800-53a" - } - ], - "prose": "continuity is sustained until full system restoration at primary processing and/or storage sites.", - "links": [ - { - "href": "#cp-2.5_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-2.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2.5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-02(05)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency operations for the system\n\ncontingency plan\n\nbusiness impact assessment\n\nprimary processing site agreements\n\nprimary storage site agreements\n\nalternate processing site agreements\n\nalternate storage site agreements\n\ncontingency plan test documentation\n\ncontingency plan test results\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-2.5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-02(05)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\norganizational personnel with knowledge of requirements for mission and business functions\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "cp-2.5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-02(05)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for continuing missions and business functions" - } - ] - } - ] - }, - { - "id": "cp-2.8", - "class": "SP800-53-enhancement", - "title": "Identify Critical Assets", - "params": [ - { - "id": "cp-02.08_odp", - "props": [ - { - "name": "alt-identifier", - "value": "cp-2.8_prm_1" - }, - { - "name": "label", - "value": "CP-02(08)_ODP", - "class": "sp800-53a" - } - ], - "select": { - "choice": [ - "all", - "essential" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "CP-02(08)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-2(8)" - }, - { - "name": "label", - "value": "CP-02(08)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-02.08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-2", - "rel": "required" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#ra-9", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-2.8_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Identify critical system assets supporting {{ insert: param, cp-02.08_odp }} mission and business functions." - }, - { - "id": "cp-2.8_gdn", - "name": "guidance", - "prose": "Organizations may choose to identify critical assets as part of criticality analysis, business continuity planning, or business impact analyses. Organizations identify critical system assets so that additional controls can be employed (beyond the controls routinely implemented) to help ensure that organizational mission and business functions can continue to be conducted during contingency operations. The identification of critical information assets also facilitates the prioritization of organizational resources. Critical system assets include technical and operational aspects. Technical aspects include system components, information technology services, information technology products, and mechanisms. Operational aspects include procedures (i.e., manually executed operations) and personnel (i.e., individuals operating technical controls and/or executing manual procedures). Organizational program protection plans can assist in identifying critical assets. If critical assets are resident within or supported by external service providers, organizations consider implementing [CP-2(7)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#cp-2.7) as a control enhancement." - }, - { - "id": "cp-2.8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-02(08)", - "class": "sp800-53a" - } - ], - "prose": "critical system assets supporting {{ insert: param, cp-02.08_odp }} mission and business functions are identified.", - "links": [ - { - "href": "#cp-2.8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-2.8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-02(08)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency operations for the system\n\ncontingency plan\n\nbusiness impact assessment\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-2.8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-02(08)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\norganizational personnel with knowledge of requirements for mission and business functions\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "cp-3", - "class": "SP800-53", - "title": "Contingency Training", - "params": [ - { - "id": "cp-03_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cp-3_prm_1" - }, - { - "name": "label", - "value": "CP-03_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "\\*See Additional Requirements" - } - ], - "guidelines": [ - { - "prose": "the time period within which to provide contingency training after assuming a contingency role or responsibility is defined;" - } - ] - }, - { - "id": "cp-03_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "cp-3_prm_2" - }, - { - "name": "label", - "value": "CP-03_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "frequency at which to provide training to system users with a contingency role or responsibility is defined;" - } - ] - }, - { - "id": "cp-03_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "cp-3_prm_3" - }, - { - "name": "label", - "value": "CP-03_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "frequency at which to review and update contingency training content is defined;" - } - ] - }, - { - "id": "cp-03_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "cp-3_prm_4" - }, - { - "name": "label", - "value": "CP-03_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events necessitating review and update of contingency training are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CP-03", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-3" - }, - { - "name": "label", - "value": "CP-03", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#511f6832-23ca-49a3-8c0f-ce493373cab8", - "rel": "reference" - }, - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#at-4", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-4", - "rel": "related" - }, - { - "href": "#cp-8", - "rel": "related" - }, - { - "href": "#ir-2", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-9", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-3_smt", - "name": "statement", - "parts": [ - { - "id": "cp-3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Provide contingency training to system users consistent with assigned roles and responsibilities:", - "parts": [ - { - "id": "cp-3_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Within {{ insert: param, cp-03_odp.01 }} of assuming a contingency role or responsibility;" - }, - { - "id": "cp-3_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "When required by system changes; and" - }, - { - "id": "cp-3_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "{{ insert: param, cp-03_odp.02 }} thereafter; and" - } - ] - }, - { - "id": "cp-3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Review and update contingency training content {{ insert: param, cp-03_odp.03 }} and following {{ insert: param, cp-03_odp.04 }}." - } - ] - }, - { - "id": "cp-3_gdn", - "name": "guidance", - "prose": "Contingency training provided by organizations is linked to the assigned roles and responsibilities of organizational personnel to ensure that the appropriate content and level of detail is included in such training. For example, some individuals may only need to know when and where to report for duty during contingency operations and if normal duties are affected; system administrators may require additional training on how to establish systems at alternate processing and storage sites; and organizational officials may receive more specific training on how to conduct mission-essential functions in designated off-site locations and how to establish communications with other governmental entities for purposes of coordination on contingency-related activities. Training for contingency roles or responsibilities reflects the specific continuity requirements in the contingency plan. Events that may precipitate an update to contingency training content include, but are not limited to, contingency plan testing or an actual contingency (lessons learned), assessment or audit findings, security incidents or breaches, or changes in laws, executive orders, directives, regulations, policies, standards, and guidelines. At the discretion of the organization, participation in a contingency plan test or exercise, including lessons learned sessions subsequent to the test or exercise, may satisfy contingency plan training requirements." - }, - { - "id": "cp-3_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CP-3 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "cp-3_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(a) Requirement:" - } - ], - "prose": "Privileged admins and engineers must take the basic contingency training within 10 days. Consideration must be given for those privileged admins and engineers with critical contingency-related roles, to gain enough system context and situational awareness to understand the full impact of contingency training as it applies to their respective level. Newly hired critical contingency personnel must take this more in-depth training within 60 days of hire date when the training will have more impact." - } - ] - }, - { - "id": "cp-3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-03a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-3_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-03a.01", - "class": "sp800-53a" - } - ], - "prose": "contingency training is provided to system users consistent with assigned roles and responsibilities within {{ insert: param, cp-03_odp.01 }} of assuming a contingency role or responsibility;", - "links": [ - { - "href": "#cp-3_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-3_obj.a.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-03a.02", - "class": "sp800-53a" - } - ], - "prose": "contingency training is provided to system users consistent with assigned roles and responsibilities when required by system changes;", - "links": [ - { - "href": "#cp-3_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-3_obj.a.3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-03a.03", - "class": "sp800-53a" - } - ], - "prose": "contingency training is provided to system users consistent with assigned roles and responsibilities {{ insert: param, cp-03_odp.02 }} thereafter;", - "links": [ - { - "href": "#cp-3_smt.a.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-03b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-3_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-03b.[01]", - "class": "sp800-53a" - } - ], - "prose": "the contingency plan training content is reviewed and updated {{ insert: param, cp-03_odp.03 }};", - "links": [ - { - "href": "#cp-3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-3_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-03b.[02]", - "class": "sp800-53a" - } - ], - "prose": "the contingency plan training content is reviewed and updated following {{ insert: param, cp-03_odp.04 }}.", - "links": [ - { - "href": "#cp-3_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-3_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-03-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency training\n\ncontingency plan\n\ncontingency training curriculum\n\ncontingency training material\n\ncontingency training records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-03-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency planning, plan implementation, and training responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "cp-3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-03-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for contingency training" - } - ] - } - ], - "controls": [ - { - "id": "cp-3.1", - "class": "SP800-53-enhancement", - "title": "Simulated Events", - "props": [ - { - "name": "label", - "value": "CP-03(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-3(1)" - }, - { - "name": "label", - "value": "CP-03(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-03.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#cp-3", - "rel": "required" - } - ], - "parts": [ - { - "id": "cp-3.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Incorporate simulated events into contingency training to facilitate effective response by personnel in crisis situations." - }, - { - "id": "cp-3.1_gdn", - "name": "guidance", - "prose": "The use of simulated events creates an environment for personnel to experience actual threat events, including cyber-attacks that disable websites, ransomware attacks that encrypt organizational data on servers, hurricanes that damage or destroy organizational facilities, or hardware or software failures." - }, - { - "id": "cp-3.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-03(01)", - "class": "sp800-53a" - } - ], - "prose": "simulated events are incorporated into contingency training to facilitate effective response by personnel in crisis situations.", - "links": [ - { - "href": "#cp-3.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-3.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-03(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency training\n\ncontingency plan\n\ncontingency training curriculum\n\ncontingency training material\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-3.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-03(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency planning, plan implementation, and training responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "cp-3.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-03(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for contingency training\n\nmechanisms for simulating contingency events" - } - ] - } - ] - } - ] - }, - { - "id": "cp-4", - "class": "SP800-53", - "title": "Contingency Plan Testing", - "params": [ - { - "id": "cp-4_prm_2", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cp-04_odp.02" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cp-04_odp.03" - } - ], - "label": "organization-defined tests" - }, - { - "id": "cp-04_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cp-4_prm_1" - }, - { - "name": "label", - "value": "CP-04_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "frequency of testing the contingency plan for the system is defined;" - } - ] - }, - { - "id": "cp-04_odp.02", - "props": [ - { - "name": "label", - "value": "CP-04_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "tests", - "constraints": [ - { - "description": "functional exercises" - } - ], - "guidelines": [ - { - "prose": "tests for determining the effectiveness of the contingency plan are defined;" - } - ] - }, - { - "id": "cp-04_odp.03", - "props": [ - { - "name": "label", - "value": "CP-04_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "tests", - "constraints": [ - { - "description": "functional exercises" - } - ], - "guidelines": [ - { - "prose": "tests for determining readiness to execute the contingency plan are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "CP-04", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-4" - }, - { - "name": "label", - "value": "CP-04", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#628d22a1-6a11-4784-bc59-5cd9497b5445", - "rel": "reference" - }, - { - "href": "#bc39f179-c735-4da2-b7a7-b2b622119755", - "rel": "reference" - }, - { - "href": "#53be2fcf-cfd1-4bcb-896b-9a3b65c22098", - "rel": "reference" - }, - { - "href": "#61ccf0f4-d3e7-42db-9796-ce6cb1c85989", - "rel": "reference" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-3", - "rel": "related" - }, - { - "href": "#cp-8", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#ir-3", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-14", - "rel": "related" - }, - { - "href": "#sr-2", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-4_smt", - "name": "statement", - "parts": [ - { - "id": "cp-4_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Test the contingency plan for the system {{ insert: param, cp-04_odp.01 }} using the following tests to determine the effectiveness of the plan and the readiness to execute the plan: {{ insert: param, cp-4_prm_2 }}." - }, - { - "id": "cp-4_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Review the contingency plan test results; and" - }, - { - "id": "cp-4_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Initiate corrective actions, if needed." - } - ] - }, - { - "id": "cp-4_gdn", - "name": "guidance", - "prose": "Methods for testing contingency plans to determine the effectiveness of the plans and identify potential weaknesses include checklists, walk-through and tabletop exercises, simulations (parallel or full interrupt), and comprehensive exercises. Organizations conduct testing based on the requirements in contingency plans and include a determination of the effects on organizational operations, assets, and individuals due to contingency operations. Organizations have flexibility and discretion in the breadth, depth, and timelines of corrective actions." - }, - { - "id": "cp-4_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CP-4 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "cp-4_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(a) Requirement:" - } - ], - "prose": "The service provider develops test plans in accordance with NIST Special Publication 800-34 (as amended); plans are approved by the AO prior to initiating testing." - }, - { - "id": "cp-4_fr_smt.2", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(b) Requirement:" - } - ], - "prose": "The service provider must include the Contingency Plan test results with the security package within the Contingency Plan-designated appendix (Appendix G, Contingency Plan Test Report)." - } - ] - }, - { - "id": "cp-4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-04", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-4_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-04a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-4_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-04a.[01]", - "class": "sp800-53a" - } - ], - "prose": "the contingency plan for the system is tested {{ insert: param, cp-04_odp.01 }};", - "links": [ - { - "href": "#cp-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-4_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-04a.[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cp-04_odp.02 }} are used to determine the effectiveness of the plan;", - "links": [ - { - "href": "#cp-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-4_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-04a.[03]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, cp-04_odp.03 }} are used to determine the readiness to execute the plan;", - "links": [ - { - "href": "#cp-4_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-4_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-04b.", - "class": "sp800-53a" - } - ], - "prose": "the contingency plan test results are reviewed;", - "links": [ - { - "href": "#cp-4_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-4_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-04c.", - "class": "sp800-53a" - } - ], - "prose": "corrective actions are initiated, if needed.", - "links": [ - { - "href": "#cp-4_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-04-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency plan testing\n\ncontingency plan\n\ncontingency plan test documentation\n\ncontingency plan test results\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-04-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for contingency plan testing, reviewing, or responding to contingency plan tests\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "cp-4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-04-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for contingency plan testing\n\nmechanisms supporting the contingency plan and/or contingency plan testing" - } - ] - } - ], - "controls": [ - { - "id": "cp-4.1", - "class": "SP800-53-enhancement", - "title": "Coordinate with Related Plans", - "props": [ - { - "name": "label", - "value": "CP-04(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-4(1)" - }, - { - "name": "label", - "value": "CP-04(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-04.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#cp-4", - "rel": "required" - }, - { - "href": "#ir-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-8", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-4.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Coordinate contingency plan testing with organizational elements responsible for related plans." - }, - { - "id": "cp-4.1_gdn", - "name": "guidance", - "prose": "Plans related to contingency planning for organizational systems include Business Continuity Plans, Disaster Recovery Plans, Continuity of Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, Cyber Incident Response Plans, and Occupant Emergency Plans. Coordination of contingency plan testing does not require organizations to create organizational elements to handle related plans or to align such elements with specific plans. However, it does require that if such organizational elements are responsible for related plans, organizations coordinate with those elements." - }, - { - "id": "cp-4.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-04(01)", - "class": "sp800-53a" - } - ], - "prose": "contingency plan testing is coordinated with organizational elements responsible for related plans.", - "links": [ - { - "href": "#cp-4.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-4.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-04(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nincident response policy\n\nprocedures addressing contingency plan testing\n\ncontingency plan testing documentation\n\ncontingency plan\n\nbusiness continuity plans\n\ndisaster recovery plans\n\ncontinuity of operations plans\n\ncrisis communications plans\n\ncritical infrastructure plans\n\ncyber incident response plans\n\noccupant emergency plans\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-4.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-04(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency plan testing responsibilities\n\npersonnel with responsibilities for related plans\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "cp-4.2", - "class": "SP800-53-enhancement", - "title": "Alternate Processing Site", - "props": [ - { - "name": "label", - "value": "CP-04(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-4(2)" - }, - { - "name": "label", - "value": "CP-04(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-04.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#cp-4", - "rel": "required" - }, - { - "href": "#cp-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-4.2_smt", - "name": "statement", - "prose": "Test the contingency plan at the alternate processing site:", - "parts": [ - { - "id": "cp-4.2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "To familiarize contingency personnel with the facility and available resources; and" - }, - { - "id": "cp-4.2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "To evaluate the capabilities of the alternate processing site to support contingency operations." - } - ] - }, - { - "id": "cp-4.2_gdn", - "name": "guidance", - "prose": "Conditions at the alternate processing site may be significantly different than the conditions at the primary site. Having the opportunity to visit the alternate site and experience the actual capabilities available at the site can provide valuable information on potential vulnerabilities that could affect essential organizational mission and business functions. The on-site visit can also provide an opportunity to refine the contingency plan to address the vulnerabilities discovered during testing." - }, - { - "id": "cp-4.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-04(02)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-4.2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-04(02)(a)", - "class": "sp800-53a" - } - ], - "prose": "the contingency plan is tested at the alternate processing site to familiarize contingency personnel with the facility and available resources;", - "links": [ - { - "href": "#cp-4.2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-4.2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-04(02)(b)", - "class": "sp800-53a" - } - ], - "prose": "the contingency plan is tested at the alternate processing site to evaluate the capabilities of the alternate processing site to support contingency operations.", - "links": [ - { - "href": "#cp-4.2_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-4.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-4.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-04(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing contingency plan testing\n\ncontingency plan\n\ncontingency plan test documentation\n\ncontingency plan test results\n\nalternate processing site agreements\n\nservice-level agreements\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-4.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-04(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "cp-4.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-04(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for contingency plan testing\n\nmechanisms supporting the contingency plan and/or contingency plan testing" - } - ] - } - ] - } - ] - }, - { - "id": "cp-6", - "class": "SP800-53", - "title": "Alternate Storage Site", - "props": [ - { - "name": "label", - "value": "CP-06", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-6" - }, - { - "name": "label", - "value": "CP-06", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-06" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#bc39f179-c735-4da2-b7a7-b2b622119755", - "rel": "reference" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - }, - { - "href": "#cp-8", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#cp-10", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-36", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#si-13", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-6_smt", - "name": "statement", - "parts": [ - { - "id": "cp-6_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Establish an alternate storage site, including necessary agreements to permit the storage and retrieval of system backup information; and" - }, - { - "id": "cp-6_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Ensure that the alternate storage site provides controls equivalent to that of the primary site." - } - ] - }, - { - "id": "cp-6_gdn", - "name": "guidance", - "prose": "Alternate storage sites are geographically distinct from primary storage sites and maintain duplicate copies of information and data if the primary storage site is not available. Similarly, alternate processing sites provide processing capability if the primary processing site is not available. Geographically distributed architectures that support contingency requirements may be considered alternate storage sites. Items covered by alternate storage site agreements include environmental conditions at the alternate sites, access rules for systems and facilities, physical and environmental protection requirements, and coordination of delivery and retrieval of backup media. Alternate storage sites reflect the requirements in contingency plans so that organizations can maintain essential mission and business functions despite compromise, failure, or disruption in organizational systems." - }, - { - "id": "cp-6_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-06", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-6_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-06a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-6_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-06a.[01]", - "class": "sp800-53a" - } - ], - "prose": "an alternate storage site is established;", - "links": [ - { - "href": "#cp-6_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-6_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-06a.[02]", - "class": "sp800-53a" - } - ], - "prose": "establishment of the alternate storage site includes necessary agreements to permit the storage and retrieval of system backup information;", - "links": [ - { - "href": "#cp-6_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-6_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-6_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-06b.", - "class": "sp800-53a" - } - ], - "prose": "the alternate storage site provides controls equivalent to that of the primary site.", - "links": [ - { - "href": "#cp-6_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-6_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-6_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-06-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate storage sites\n\ncontingency plan\n\nalternate storage site agreements\n\nprimary storage site agreements\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-6_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-06-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency plan alternate storage site responsibilities\n\norganizational personnel with system recovery responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "cp-6_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-06-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for storing and retrieving system backup information at the alternate storage site\n\nmechanisms supporting and/or implementing the storage and retrieval of system backup information at the alternate storage site" - } - ] - } - ], - "controls": [ - { - "id": "cp-6.1", - "class": "SP800-53-enhancement", - "title": "Separation from Primary Site", - "props": [ - { - "name": "label", - "value": "CP-06(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-6(1)" - }, - { - "name": "label", - "value": "CP-06(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-06.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-6", - "rel": "required" - }, - { - "href": "#ra-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-6.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Identify an alternate storage site that is sufficiently separated from the primary storage site to reduce susceptibility to the same threats." - }, - { - "id": "cp-6.1_gdn", - "name": "guidance", - "prose": "Threats that affect alternate storage sites are defined in organizational risk assessments and include natural disasters, structural failures, hostile attacks, and errors of omission or commission. Organizations determine what is considered a sufficient degree of separation between primary and alternate storage sites based on the types of threats that are of concern. For threats such as hostile attacks, the degree of separation between sites is less relevant." - }, - { - "id": "cp-6.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-06(01)", - "class": "sp800-53a" - } - ], - "prose": "an alternate storage site that is sufficiently separated from the primary storage site is identified to reduce susceptibility to the same threats.", - "links": [ - { - "href": "#cp-6.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-6.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-06(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate storage sites\n\ncontingency plan\n\nalternate storage site\n\nalternate storage site agreements\n\nprimary storage site agreements\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-6.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-06(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency plan alternate storage site responsibilities\n\norganizational personnel with system recovery responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "cp-6.2", - "class": "SP800-53-enhancement", - "title": "Recovery Time and Recovery Point Objectives", - "props": [ - { - "name": "label", - "value": "CP-06(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-6(2)" - }, - { - "name": "label", - "value": "CP-06(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-06.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-6", - "rel": "required" - } - ], - "parts": [ - { - "id": "cp-6.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Configure the alternate storage site to facilitate recovery operations in accordance with recovery time and recovery point objectives." - }, - { - "id": "cp-6.2_gdn", - "name": "guidance", - "prose": "Organizations establish recovery time and recovery point objectives as part of contingency planning. Configuration of the alternate storage site includes physical facilities and the systems supporting recovery operations that ensure accessibility and correct execution." - }, - { - "id": "cp-6.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-06(02)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-6.2_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-06(02)[01]", - "class": "sp800-53a" - } - ], - "prose": "the alternate storage site is configured to facilitate recovery operations in accordance with recovery time objectives;", - "links": [ - { - "href": "#cp-6.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-6.2_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-06(02)[02]", - "class": "sp800-53a" - } - ], - "prose": "the alternate storage site is configured to facilitate recovery operations in accordance with recovery point objectives.", - "links": [ - { - "href": "#cp-6.2_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-6.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-6.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-06(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate storage sites\n\ncontingency plan\n\nalternate storage site\n\nalternate storage site agreements\n\nalternate storage site configurations\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-6.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-06(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency plan testing responsibilities\n\norganizational personnel with responsibilities for testing related plans\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "cp-6.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-06(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for contingency plan testing\n\nmechanisms supporting recovery time and point objectives" - } - ] - } - ] - }, - { - "id": "cp-6.3", - "class": "SP800-53-enhancement", - "title": "Accessibility", - "props": [ - { - "name": "label", - "value": "CP-06(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-6(3)" - }, - { - "name": "label", - "value": "CP-06(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-06.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-6", - "rel": "required" - }, - { - "href": "#ra-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-6.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Identify potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster and outline explicit mitigation actions." - }, - { - "id": "cp-6.3_gdn", - "name": "guidance", - "prose": "Area-wide disruptions refer to those types of disruptions that are broad in geographic scope with such determinations made by organizations based on organizational assessments of risk. Explicit mitigation actions include duplicating backup information at other alternate storage sites if access problems occur at originally designated alternate sites or planning for physical access to retrieve backup information if electronic accessibility to the alternate site is disrupted." - }, - { - "id": "cp-6.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-06(03)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-6.3_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-06(03)[01]", - "class": "sp800-53a" - } - ], - "prose": "potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster are identified;", - "links": [ - { - "href": "#cp-6.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-6.3_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-06(03)[02]", - "class": "sp800-53a" - } - ], - "prose": "explicit mitigation actions to address identified accessibility problems are outlined.", - "links": [ - { - "href": "#cp-6.3_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-6.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-6.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-06(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate storage sites\n\ncontingency plan\n\nalternate storage site\n\nlist of potential accessibility problems to alternate storage site\n\nmitigation actions for accessibility problems to alternate storage site\n\norganizational risk assessments\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-6.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-06(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency plan alternate storage site responsibilities\n\norganizational personnel with system recovery responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "cp-7", - "class": "SP800-53", - "title": "Alternate Processing Site", - "params": [ - { - "id": "cp-07_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cp-7_prm_1" - }, - { - "name": "label", - "value": "CP-07_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "system operations", - "guidelines": [ - { - "prose": "system operations for essential mission and business functions are defined;" - } - ] - }, - { - "id": "cp-07_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "cp-7_prm_2" - }, - { - "name": "alt-label", - "value": "time period consistent with recovery time and recovery point objectives", - "class": "sp800-53" - }, - { - "name": "label", - "value": "CP-07_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "time period", - "guidelines": [ - { - "prose": "time period consistent with recovery time and recovery point objectives is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CP-07", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-7" - }, - { - "name": "label", - "value": "CP-07", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-07" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#bc39f179-c735-4da2-b7a7-b2b622119755", - "rel": "reference" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-6", - "rel": "related" - }, - { - "href": "#cp-8", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#cp-10", - "rel": "related" - }, - { - "href": "#ma-6", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pe-11", - "rel": "related" - }, - { - "href": "#pe-12", - "rel": "related" - }, - { - "href": "#pe-17", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-36", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#si-13", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-7_smt", - "name": "statement", - "parts": [ - { - "id": "cp-7_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Establish an alternate processing site, including necessary agreements to permit the transfer and resumption of {{ insert: param, cp-07_odp.01 }} for essential mission and business functions within {{ insert: param, cp-07_odp.02 }} when the primary processing capabilities are unavailable;" - }, - { - "id": "cp-7_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Make available at the alternate processing site, the equipment and supplies required to transfer and resume operations or put contracts in place to support delivery to the site within the organization-defined time period for transfer and resumption; and" - }, - { - "id": "cp-7_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Provide controls at the alternate processing site that are equivalent to those at the primary site." - } - ] - }, - { - "id": "cp-7_gdn", - "name": "guidance", - "prose": "Alternate processing sites are geographically distinct from primary processing sites and provide processing capability if the primary processing site is not available. The alternate processing capability may be addressed using a physical processing site or other alternatives, such as failover to a cloud-based service provider or other internally or externally provided processing service. Geographically distributed architectures that support contingency requirements may also be considered alternate processing sites. Controls that are covered by alternate processing site agreements include the environmental conditions at alternate sites, access rules, physical and environmental protection requirements, and the coordination for the transfer and assignment of personnel. Requirements are allocated to alternate processing sites that reflect the requirements in contingency plans to maintain essential mission and business functions despite disruption, compromise, or failure in organizational systems." - }, - { - "id": "cp-7_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CP-7 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "cp-7_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(a) Requirement:" - } - ], - "prose": "The service provider defines a time period consistent with the recovery time objectives and business impact analysis." - } - ] - }, - { - "id": "cp-7_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-07", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-7_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-07a.", - "class": "sp800-53a" - } - ], - "prose": "an alternate processing site, including necessary agreements to permit the transfer and resumption of {{ insert: param, cp-07_odp.01 }} for essential mission and business functions, is established within {{ insert: param, cp-07_odp.02 }} when the primary processing capabilities are unavailable;", - "links": [ - { - "href": "#cp-7_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-7_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-07b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-7_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-07b.[01]", - "class": "sp800-53a" - } - ], - "prose": "the equipment and supplies required to transfer operations are made available at the alternate processing site or if contracts are in place to support delivery to the site within {{ insert: param, cp-07_odp.02 }} for transfer;", - "links": [ - { - "href": "#cp-7_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-7_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-07b.[02]", - "class": "sp800-53a" - } - ], - "prose": "the equipment and supplies required to resume operations are made available at the alternate processing site or if contracts are in place to support delivery to the site within {{ insert: param, cp-07_odp.02 }} for resumption;", - "links": [ - { - "href": "#cp-7_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-7_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-7_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-07c.", - "class": "sp800-53a" - } - ], - "prose": "controls provided at the alternate processing site are equivalent to those at the primary site.", - "links": [ - { - "href": "#cp-7_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-7_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-07-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate processing sites\n\ncontingency plan\n\nalternate processing site agreements\n\nprimary processing site agreements\n\nspare equipment and supplies inventory at alternate processing site\n\nequipment and supply contracts\n\nservice-level agreements\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-7_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-07-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for contingency planning and/or alternate site arrangements\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "cp-7_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-07-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for recovery at the alternate site\n\nmechanisms supporting and/or implementing recovery at the alternate processing site" - } - ] - } - ], - "controls": [ - { - "id": "cp-7.1", - "class": "SP800-53-enhancement", - "title": "Separation from Primary Site", - "props": [ - { - "name": "label", - "value": "CP-07(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-7(1)" - }, - { - "name": "label", - "value": "CP-07(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-07.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-7", - "rel": "required" - }, - { - "href": "#ra-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-7.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Identify an alternate processing site that is sufficiently separated from the primary processing site to reduce susceptibility to the same threats." - }, - { - "id": "cp-7.1_gdn", - "name": "guidance", - "prose": "Threats that affect alternate processing sites are defined in organizational assessments of risk and include natural disasters, structural failures, hostile attacks, and errors of omission or commission. Organizations determine what is considered a sufficient degree of separation between primary and alternate processing sites based on the types of threats that are of concern. For threats such as hostile attacks, the degree of separation between sites is less relevant." - }, - { - "id": "cp-7.1_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CP-7 (1) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "cp-7.1_fr_smt.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "The service provider may determine what is considered a sufficient degree of separation between the primary and alternate processing sites, based on the types of threats that are of concern. For one particular type of threat (i.e., hostile cyber attack), the degree of separation between sites will be less relevant." - } - ] - }, - { - "id": "cp-7.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-07(01)", - "class": "sp800-53a" - } - ], - "prose": "an alternate processing site that is sufficiently separated from the primary processing site to reduce susceptibility to the same threats is identified.", - "links": [ - { - "href": "#cp-7.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-7.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-07(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate processing sites\n\ncontingency plan\n\nalternate processing site\n\nalternate processing site agreements\n\nprimary processing site agreements\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-7.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-07(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency plan alternate processing site responsibilities\n\norganizational personnel with system recovery responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "cp-7.2", - "class": "SP800-53-enhancement", - "title": "Accessibility", - "props": [ - { - "name": "label", - "value": "CP-07(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-7(2)" - }, - { - "name": "label", - "value": "CP-07(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-07.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-7", - "rel": "required" - }, - { - "href": "#ra-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-7.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Identify potential accessibility problems to alternate processing sites in the event of an area-wide disruption or disaster and outlines explicit mitigation actions." - }, - { - "id": "cp-7.2_gdn", - "name": "guidance", - "prose": "Area-wide disruptions refer to those types of disruptions that are broad in geographic scope with such determinations made by organizations based on organizational assessments of risk." - }, - { - "id": "cp-7.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-07(02)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-7.2_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-07(02)[01]", - "class": "sp800-53a" - } - ], - "prose": "potential accessibility problems to alternate processing sites in the event of an area-wide disruption or disaster are identified;", - "links": [ - { - "href": "#cp-7.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-7.2_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-07(02)[02]", - "class": "sp800-53a" - } - ], - "prose": "explicit mitigation actions to address identified accessibility problems are outlined.", - "links": [ - { - "href": "#cp-7.2_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-7.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-7.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-07(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate processing sites\n\ncontingency plan\n\nalternate processing site\n\nalternate processing site agreements\n\nprimary processing site agreements\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-7.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-07(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency plan alternate processing site responsibilities\n\norganizational personnel with system recovery responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "cp-7.3", - "class": "SP800-53-enhancement", - "title": "Priority of Service", - "props": [ - { - "name": "label", - "value": "CP-07(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-7(3)" - }, - { - "name": "label", - "value": "CP-07(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-07.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-7", - "rel": "required" - } - ], - "parts": [ - { - "id": "cp-7.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Develop alternate processing site agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives)." - }, - { - "id": "cp-7.3_gdn", - "name": "guidance", - "prose": "Priority of service agreements refer to negotiated agreements with service providers that ensure that organizations receive priority treatment consistent with their availability requirements and the availability of information resources for logical alternate processing and/or at the physical alternate processing site. Organizations establish recovery time objectives as part of contingency planning." - }, - { - "id": "cp-7.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-07(03)", - "class": "sp800-53a" - } - ], - "prose": "alternate processing site agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives) are developed.", - "links": [ - { - "href": "#cp-7.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-7.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-07(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate processing sites\n\ncontingency plan\n\nalternate processing site agreements\n\nservice-level agreements\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-7.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-07(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency plan alternate processing site responsibilities\n\norganizational personnel with system recovery responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for acquisitions/contractual agreements" - } - ] - } - ] - }, - { - "id": "cp-7.4", - "class": "SP800-53-enhancement", - "title": "Preparation for Use", - "props": [ - { - "name": "label", - "value": "CP-07(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-7(4)" - }, - { - "name": "label", - "value": "CP-07(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-07.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-7", - "rel": "required" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cp-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-7.4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Prepare the alternate processing site so that the site can serve as the operational site supporting essential mission and business functions." - }, - { - "id": "cp-7.4_gdn", - "name": "guidance", - "prose": "Site preparation includes establishing configuration settings for systems at the alternate processing site consistent with the requirements for such settings at the primary site and ensuring that essential supplies and logistical considerations are in place." - }, - { - "id": "cp-7.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-07(04)", - "class": "sp800-53a" - } - ], - "prose": "the alternate processing site is prepared so that the site can serve as the operational site supporting essential mission and business functions.", - "links": [ - { - "href": "#cp-7.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-7.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-07(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate processing sites\n\ncontingency plan\n\nalternate processing site\n\nalternate processing site agreements\n\nalternate processing site configurations\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-7.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-07(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency plan alternate processing site responsibilities\n\norganizational personnel with system recovery responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "cp-7.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-07(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing recovery at the alternate processing site" - } - ] - } - ] - } - ] - }, - { - "id": "cp-8", - "class": "SP800-53", - "title": "Telecommunications Services", - "params": [ - { - "id": "cp-08_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cp-8_prm_1" - }, - { - "name": "label", - "value": "CP-08_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "system operations", - "guidelines": [ - { - "prose": "system operations to be resumed for essential mission and business functions are defined;" - } - ] - }, - { - "id": "cp-08_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "cp-8_prm_2" - }, - { - "name": "label", - "value": "CP-08_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "time period", - "guidelines": [ - { - "prose": "time period within which to resume essential mission and business functions when the primary telecommunications capabilities are unavailable is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CP-08", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-8" - }, - { - "name": "label", - "value": "CP-08", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#bc39f179-c735-4da2-b7a7-b2b622119755", - "rel": "reference" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-6", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#cp-11", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-8_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Establish alternate telecommunications services, including necessary agreements to permit the resumption of {{ insert: param, cp-08_odp.01 }} for essential mission and business functions within {{ insert: param, cp-08_odp.02 }} when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites." - }, - { - "id": "cp-8_gdn", - "name": "guidance", - "prose": "Telecommunications services (for data and voice) for primary and alternate processing and storage sites are in scope for [CP-8](#cp-8) . Alternate telecommunications services reflect the continuity requirements in contingency plans to maintain essential mission and business functions despite the loss of primary telecommunications services. Organizations may specify different time periods for primary or alternate sites. Alternate telecommunications services include additional organizational or commercial ground-based circuits or lines, network-based approaches to telecommunications, or the use of satellites. Organizations consider factors such as availability, quality of service, and access when entering into alternate telecommunications agreements." - }, - { - "id": "cp-8_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CP-8 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "cp-8_fr_gdn.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "The service provider defines a time period consistent with the recovery time objectives and business impact analysis." - } - ] - }, - { - "id": "cp-8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-08", - "class": "sp800-53a" - } - ], - "prose": "alternate telecommunications services, including necessary agreements to permit the resumption of {{ insert: param, cp-08_odp.01 }} , are established for essential mission and business functions within {{ insert: param, cp-08_odp.02 }} when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.", - "links": [ - { - "href": "#cp-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-08-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing alternate telecommunications services\n\ncontingency plan\n\nprimary and alternate telecommunications service agreements\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-08-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency plan telecommunications responsibilities\n\norganizational personnel with system recovery responsibilities\n\norganizational personnel with knowledge of requirements for mission and business functions\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for acquisitions/contractual agreements" - } - ] - }, - { - "id": "cp-8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-08-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting telecommunications" - } - ] - } - ], - "controls": [ - { - "id": "cp-8.1", - "class": "SP800-53-enhancement", - "title": "Priority of Service Provisions", - "props": [ - { - "name": "label", - "value": "CP-08(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-8(1)" - }, - { - "name": "label", - "value": "CP-08(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-08.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-8", - "rel": "required" - } - ], - "parts": [ - { - "id": "cp-8.1_smt", - "name": "statement", - "parts": [ - { - "id": "cp-8.1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Develop primary and alternate telecommunications service agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives); and" - }, - { - "id": "cp-8.1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Request Telecommunications Service Priority for all telecommunications services used for national security emergency preparedness if the primary and/or alternate telecommunications services are provided by a common carrier." - } - ] - }, - { - "id": "cp-8.1_gdn", - "name": "guidance", - "prose": "Organizations consider the potential mission or business impact in situations where telecommunications service providers are servicing other organizations with similar priority of service provisions. Telecommunications Service Priority (TSP) is a Federal Communications Commission (FCC) program that directs telecommunications service providers (e.g., wireline and wireless phone companies) to give preferential treatment to users enrolled in the program when they need to add new lines or have their lines restored following a disruption of service, regardless of the cause. The FCC sets the rules and policies for the TSP program, and the Department of Homeland Security manages the TSP program. The TSP program is always in effect and not contingent on a major disaster or attack taking place. Federal sponsorship is required to enroll in the TSP program." - }, - { - "id": "cp-8.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-08(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-8.1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-08(01)(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-8.1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-08(01)(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "primary telecommunications service agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives) are developed;", - "links": [ - { - "href": "#cp-8.1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-8.1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-08(01)(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "alternate telecommunications service agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives) are developed;", - "links": [ - { - "href": "#cp-8.1_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-8.1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-8.1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-08(01)(b)", - "class": "sp800-53a" - } - ], - "prose": "Telecommunications Service Priority is requested for all telecommunications services used for national security emergency preparedness if the primary and/or alternate telecommunications services are provided by a common carrier.", - "links": [ - { - "href": "#cp-8.1_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-8.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-8.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-08(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing primary and alternate telecommunications services\n\ncontingency plan\n\nprimary and alternate telecommunications service agreements\n\nTelecommunications Service Priority documentation\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-8.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-08(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency plan telecommunications responsibilities\n\norganizational personnel with system recovery responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for acquisitions/contractual agreements" - } - ] - }, - { - "id": "cp-8.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-08(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting telecommunications" - } - ] - } - ] - }, - { - "id": "cp-8.2", - "class": "SP800-53-enhancement", - "title": "Single Points of Failure", - "props": [ - { - "name": "label", - "value": "CP-08(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-8(2)" - }, - { - "name": "label", - "value": "CP-08(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-08.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-8", - "rel": "required" - } - ], - "parts": [ - { - "id": "cp-8.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Obtain alternate telecommunications services to reduce the likelihood of sharing a single point of failure with primary telecommunications services." - }, - { - "id": "cp-8.2_gdn", - "name": "guidance", - "prose": "In certain circumstances, telecommunications service providers or services may share the same physical lines, which increases the vulnerability of a single failure point. It is important to have provider transparency for the actual physical transmission capability for telecommunication services." - }, - { - "id": "cp-8.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-08(02)", - "class": "sp800-53a" - } - ], - "prose": "alternate telecommunications services to reduce the likelihood of sharing a single point of failure with primary telecommunications services are obtained.", - "links": [ - { - "href": "#cp-8.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-8.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-08(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing primary and alternate telecommunications services\n\ncontingency plan\n\nprimary and alternate telecommunications service agreements\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-8.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-08(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency plan telecommunications responsibilities\n\norganizational personnel with system recovery responsibilities\n\nprimary and alternate telecommunications service providers\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "cp-8.3", - "class": "SP800-53-enhancement", - "title": "Separation of Primary and Alternate Providers", - "props": [ - { - "name": "label", - "value": "CP-08(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-8(3)" - }, - { - "name": "label", - "value": "CP-08(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-08.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-8", - "rel": "required" - } - ], - "parts": [ - { - "id": "cp-8.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Obtain alternate telecommunications services from providers that are separated from primary service providers to reduce susceptibility to the same threats." - }, - { - "id": "cp-8.3_gdn", - "name": "guidance", - "prose": "Threats that affect telecommunications services are defined in organizational assessments of risk and include natural disasters, structural failures, cyber or physical attacks, and errors of omission or commission. Organizations can reduce common susceptibilities by minimizing shared infrastructure among telecommunications service providers and achieving sufficient geographic separation between services. Organizations may consider using a single service provider in situations where the service provider can provide alternate telecommunications services that meet the separation needs addressed in the risk assessment." - }, - { - "id": "cp-8.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-08(03)", - "class": "sp800-53a" - } - ], - "prose": "alternate telecommunications services from providers that are separated from primary service providers are obtained to reduce susceptibility to the same threats.", - "links": [ - { - "href": "#cp-8.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-8.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-08(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing primary and alternate telecommunications services\n\ncontingency plan\n\nprimary and alternate telecommunications service agreements\n\nalternate telecommunications service provider site\n\nprimary telecommunications service provider site\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-8.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-08(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency plan telecommunications responsibilities\n\norganizational personnel with system recovery responsibilities\n\nprimary and alternate telecommunications service providers\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "cp-8.4", - "class": "SP800-53-enhancement", - "title": "Provider Contingency Plan", - "params": [ - { - "id": "cp-8.4_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cp-08.04_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cp-08.04_odp.02" - } - ], - "label": "organization-defined frequency" - }, - { - "id": "cp-08.04_odp.01", - "props": [ - { - "name": "label", - "value": "CP-08(04)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "annually" - } - ], - "guidelines": [ - { - "prose": "frequency at which to obtain evidence of contingency testing by providers is defined;" - } - ] - }, - { - "id": "cp-08.04_odp.02", - "props": [ - { - "name": "label", - "value": "CP-08(04)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "annually" - } - ], - "guidelines": [ - { - "prose": "frequency at which to obtain evidence of contingency training by providers is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CP-08(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-8(4)" - }, - { - "name": "label", - "value": "CP-08(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-08.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-8", - "rel": "required" - }, - { - "href": "#cp-3", - "rel": "related" - }, - { - "href": "#cp-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-8.4_smt", - "name": "statement", - "parts": [ - { - "id": "cp-8.4_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Require primary and alternate telecommunications service providers to have contingency plans;" - }, - { - "id": "cp-8.4_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Review provider contingency plans to ensure that the plans meet organizational contingency requirements; and" - }, - { - "id": "cp-8.4_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Obtain evidence of contingency testing and training by providers {{ insert: param, cp-8.4_prm_1 }}." - } - ] - }, - { - "id": "cp-8.4_gdn", - "name": "guidance", - "prose": "Reviews of provider contingency plans consider the proprietary nature of such plans. In some situations, a summary of provider contingency plans may be sufficient evidence for organizations to satisfy the review requirement. Telecommunications service providers may also participate in ongoing disaster recovery exercises in coordination with the Department of Homeland Security and state and local governments. Organizations may use these types of activities to satisfy evidentiary requirements related to service provider contingency plan reviews, testing, and training." - }, - { - "id": "cp-8.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-08(04)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-8.4_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-08(04)(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-8.4_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-08(04)(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "primary telecommunications service providers are required to have contingency plans;", - "links": [ - { - "href": "#cp-8.4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-8.4_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-08(04)(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "alternate telecommunications service providers are required to have contingency plans;", - "links": [ - { - "href": "#cp-8.4_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-8.4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-8.4_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-08(04)(b)", - "class": "sp800-53a" - } - ], - "prose": "provider contingency plans are reviewed to ensure that the plans meet organizational contingency requirements;", - "links": [ - { - "href": "#cp-8.4_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-8.4_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-08(04)(c)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-8.4_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-08(04)(c)[01]", - "class": "sp800-53a" - } - ], - "prose": "evidence of contingency testing by providers is obtained {{ insert: param, cp-08.04_odp.01 }}.", - "links": [ - { - "href": "#cp-8.4_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-8.4_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-08(04)(c)[02]", - "class": "sp800-53a" - } - ], - "prose": "evidence of contingency training by providers is obtained {{ insert: param, cp-08.04_odp.02 }}.", - "links": [ - { - "href": "#cp-8.4_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-8.4_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-8.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-8.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-08(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing primary and alternate telecommunications services\n\ncontingency plan\n\nprovider contingency plans\n\nevidence of contingency testing/training by providers\n\nprimary and alternate telecommunications service agreements\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-8.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-08(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency planning, plan implementation, and testing responsibilities\n\nprimary and alternate telecommunications service providers\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibility for acquisitions/contractual agreements" - } - ] - } - ] - } - ] - }, - { - "id": "cp-9", - "class": "SP800-53", - "title": "System Backup", - "params": [ - { - "id": "cp-09_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "cp-9_prm_1" - }, - { - "name": "label", - "value": "CP-09_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "system components", - "guidelines": [ - { - "prose": "system components for which to conduct backups of user-level information is defined;" - } - ] - }, - { - "id": "cp-09_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "cp-9_prm_2" - }, - { - "name": "alt-label", - "value": "frequency consistent with recovery time and recovery point objectives", - "class": "sp800-53" - }, - { - "name": "label", - "value": "CP-09_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "daily incremental; weekly full" - } - ], - "guidelines": [ - { - "prose": "frequency at which to conduct backups of user-level information consistent with recovery time and recovery point objectives is defined;" - } - ] - }, - { - "id": "cp-09_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "cp-9_prm_3" - }, - { - "name": "alt-label", - "value": "frequency consistent with recovery time and recovery point objectives", - "class": "sp800-53" - }, - { - "name": "label", - "value": "CP-09_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "daily incremental; weekly full" - } - ], - "guidelines": [ - { - "prose": "frequency at which to conduct backups of system-level information consistent with recovery time and recovery point objectives is defined;" - } - ] - }, - { - "id": "cp-09_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "cp-9_prm_4" - }, - { - "name": "alt-label", - "value": "frequency consistent with recovery time and recovery point objectives", - "class": "sp800-53" - }, - { - "name": "label", - "value": "CP-09_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "daily incremental; weekly full" - } - ], - "guidelines": [ - { - "prose": "frequency at which to conduct backups of system documentation consistent with recovery time and recovery point objectives is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CP-09", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-9" - }, - { - "name": "label", - "value": "CP-09", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-09" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#678e3d6c-150b-4393-aec5-6e3481eb1e00", - "rel": "reference" - }, - { - "href": "#7c37a38d-21d7-40d8-bc3d-b5e27eac17e1", - "rel": "reference" - }, - { - "href": "#bc39f179-c735-4da2-b7a7-b2b622119755", - "rel": "reference" - }, - { - "href": "#3653e316-8923-430e-8943-b3b2b2562fc6", - "rel": "reference" - }, - { - "href": "#2494df28-9049-4196-b233-540e7440993f", - "rel": "reference" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-6", - "rel": "related" - }, - { - "href": "#cp-10", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#si-13", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-9_smt", - "name": "statement", - "parts": [ - { - "id": "cp-9_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Conduct backups of user-level information contained in {{ insert: param, cp-09_odp.01 }} {{ insert: param, cp-09_odp.02 }};" - }, - { - "id": "cp-9_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Conduct backups of system-level information contained in the system {{ insert: param, cp-09_odp.03 }};" - }, - { - "id": "cp-9_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Conduct backups of system documentation, including security- and privacy-related documentation {{ insert: param, cp-09_odp.04 }} ; and" - }, - { - "id": "cp-9_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Protect the confidentiality, integrity, and availability of backup information." - } - ] - }, - { - "id": "cp-9_gdn", - "name": "guidance", - "prose": "System-level information includes system state information, operating system software, middleware, application software, and licenses. User-level information includes information other than system-level information. Mechanisms employed to protect the integrity of system backups include digital signatures and cryptographic hashes. Protection of system backup information while in transit is addressed by [MP-5](#mp-5) and [SC-8](#sc-8) . System backups reflect the requirements in contingency plans as well as other organizational requirements for backing up information. Organizations may be subject to laws, executive orders, directives, regulations, or policies with requirements regarding specific categories of information (e.g., personal health information). Organizational personnel consult with the senior agency official for privacy and legal counsel regarding such requirements." - }, - { - "id": "cp-9_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CP-9 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "cp-9_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "The service provider shall determine what elements of the cloud environment require the Information System Backup control. The service provider shall determine how Information System Backup is going to be verified and appropriate periodicity of the check." - }, - { - "id": "cp-9_fr_smt.2", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(a) Requirement:" - } - ], - "prose": "The service provider maintains at least three backup copies of user-level information (at least one of which is available online) or provides an equivalent alternative." - }, - { - "id": "cp-9_fr_smt.3", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(b) Requirement:" - } - ], - "prose": "The service provider maintains at least three backup copies of system-level information (at least one of which is available online) or provides an equivalent alternative." - }, - { - "id": "cp-9_fr_smt.4", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(c) Requirement:" - } - ], - "prose": "The service provider maintains at least three backup copies of information system documentation including security information (at least one of which is available online) or provides an equivalent alternative." - } - ] - }, - { - "id": "cp-9_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-09", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-9_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-09a.", - "class": "sp800-53a" - } - ], - "prose": "backups of user-level information contained in {{ insert: param, cp-09_odp.01 }} are conducted {{ insert: param, cp-09_odp.02 }};", - "links": [ - { - "href": "#cp-9_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-9_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-09b.", - "class": "sp800-53a" - } - ], - "prose": "backups of system-level information contained in the system are conducted {{ insert: param, cp-09_odp.03 }};", - "links": [ - { - "href": "#cp-9_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-9_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-09c.", - "class": "sp800-53a" - } - ], - "prose": "backups of system documentation, including security- and privacy-related documentation are conducted {{ insert: param, cp-09_odp.04 }};", - "links": [ - { - "href": "#cp-9_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-9_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-09d.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-9_obj.d-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-09d.[01]", - "class": "sp800-53a" - } - ], - "prose": "the confidentiality of backup information is protected;", - "links": [ - { - "href": "#cp-9_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-9_obj.d-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-09d.[02]", - "class": "sp800-53a" - } - ], - "prose": "the integrity of backup information is protected;", - "links": [ - { - "href": "#cp-9_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-9_obj.d-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-09d.[03]", - "class": "sp800-53a" - } - ], - "prose": "the availability of backup information is protected.", - "links": [ - { - "href": "#cp-9_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-9_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-9_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-09-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing system backup\n\ncontingency plan\n\nbackup storage location(s)\n\nsystem backup logs or records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-9_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-09-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system backup responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "cp-9_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-09-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for conducting system backups\n\nmechanisms supporting and/or implementing system backups" - } - ] - } - ], - "controls": [ - { - "id": "cp-9.1", - "class": "SP800-53-enhancement", - "title": "Testing for Reliability and Integrity", - "params": [ - { - "id": "cp-9.1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cp-09.01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cp-09.01_odp.02" - } - ], - "label": "organization-defined frequency" - }, - { - "id": "cp-09.01_odp.01", - "props": [ - { - "name": "label", - "value": "CP-09(01)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least monthly" - } - ], - "guidelines": [ - { - "prose": "frequency at which to test backup information for media reliability is defined;" - } - ] - }, - { - "id": "cp-09.01_odp.02", - "props": [ - { - "name": "label", - "value": "CP-09(01)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least monthly" - } - ], - "guidelines": [ - { - "prose": "frequency at which to test backup information for information integrity is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CP-09(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-9(1)" - }, - { - "name": "label", - "value": "CP-09(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-09.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-9", - "rel": "required" - }, - { - "href": "#cp-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-9.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Test backup information {{ insert: param, cp-9.1_prm_1 }} to verify media reliability and information integrity." - }, - { - "id": "cp-9.1_gdn", - "name": "guidance", - "prose": "Organizations need assurance that backup information can be reliably retrieved. Reliability pertains to the systems and system components where the backup information is stored, the operations used to retrieve the information, and the integrity of the information being retrieved. Independent and specialized tests can be used for each of the aspects of reliability. For example, decrypting and transporting (or transmitting) a random sample of backup files from the alternate storage or backup site and comparing the information to the same information at the primary processing site can provide such assurance." - }, - { - "id": "cp-9.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-09(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-9.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-09(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "backup information is tested {{ insert: param, cp-09.01_odp.01 }} to verify media reliability;", - "links": [ - { - "href": "#cp-9.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-9.1_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-09(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "backup information is tested {{ insert: param, cp-09.01_odp.02 }} to verify information integrity.", - "links": [ - { - "href": "#cp-9.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-9.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-9.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-09(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing system backup\n\ncontingency plan\n\nsystem backup test results\n\ncontingency plan test documentation\n\ncontingency plan test results\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-9.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-09(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system backup responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "cp-9.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-09(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for conducting system backups\n\nmechanisms supporting and/or implementing system backups" - } - ] - } - ] - }, - { - "id": "cp-9.2", - "class": "SP800-53-enhancement", - "title": "Test Restoration Using Sampling", - "props": [ - { - "name": "label", - "value": "CP-09(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-9(2)" - }, - { - "name": "label", - "value": "CP-09(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-09.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-9", - "rel": "required" - }, - { - "href": "#cp-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-9.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Use a sample of backup information in the restoration of selected system functions as part of contingency plan testing." - }, - { - "id": "cp-9.2_gdn", - "name": "guidance", - "prose": "Organizations need assurance that system functions can be restored correctly and can support established organizational missions. To ensure that the selected system functions are thoroughly exercised during contingency plan testing, a sample of backup information is retrieved to determine whether the functions are operating as intended. Organizations can determine the sample size for the functions and backup information based on the level of assurance needed." - }, - { - "id": "cp-9.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-09(02)", - "class": "sp800-53a" - } - ], - "prose": "a sample of backup information in the restoration of selected system functions is used as part of contingency plan testing.", - "links": [ - { - "href": "#cp-9.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-9.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-09(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing system backup\n\ncontingency plan\n\nsystem backup test results\n\ncontingency plan test documentation\n\ncontingency plan test results\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-9.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-09(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system backup responsibilities\n\norganizational personnel with contingency planning/contingency plan testing responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "cp-9.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-09(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for conducting system backups\n\nmechanisms supporting and/or implementing system backups" - } - ] - } - ] - }, - { - "id": "cp-9.3", - "class": "SP800-53-enhancement", - "title": "Separate Storage for Critical Information", - "params": [ - { - "id": "cp-09.03_odp", - "props": [ - { - "name": "alt-identifier", - "value": "cp-9.3_prm_1" - }, - { - "name": "label", - "value": "CP-09(03)_ODP", - "class": "sp800-53a" - } - ], - "label": "critical system software and other security-related information", - "guidelines": [ - { - "prose": "critical system software and other security-related information backups to be stored in a separate facility are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CP-09(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-9(3)" - }, - { - "name": "label", - "value": "CP-09(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-09.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-9", - "rel": "required" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-9.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Store backup copies of {{ insert: param, cp-09.03_odp }} in a separate facility or in a fire rated container that is not collocated with the operational system." - }, - { - "id": "cp-9.3_gdn", - "name": "guidance", - "prose": "Separate storage for critical information applies to all critical information regardless of the type of backup storage media. Critical system software includes operating systems, middleware, cryptographic key management systems, and intrusion detection systems. Security-related information includes inventories of system hardware, software, and firmware components. Alternate storage sites, including geographically distributed architectures, serve as separate storage facilities for organizations. Organizations may provide separate storage by implementing automated backup processes at alternative storage sites (e.g., data centers). The General Services Administration (GSA) establishes standards and specifications for security and fire rated containers." - }, - { - "id": "cp-9.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-09(03)", - "class": "sp800-53a" - } - ], - "prose": "backup copies of {{ insert: param, cp-09.03_odp }} are stored in a separate facility or in a fire rated container that is not collocated with the operational system.", - "links": [ - { - "href": "#cp-9.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-9.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-09(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing system backup\n\ncontingency plan\n\nbackup storage location(s)\n\nsystem backup configurations and associated documentation\n\nsystem backup logs or records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-9.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-09(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency planning and plan implementation responsibilities\n\norganizational personnel with system backup responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "cp-9.5", - "class": "SP800-53-enhancement", - "title": "Transfer to Alternate Storage Site", - "params": [ - { - "id": "cp-9.5_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cp-09.05_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cp-09.05_odp.02" - } - ], - "label": "organization-defined time period and transfer rate consistent with the recovery time and recovery point objectives" - }, - { - "id": "cp-09.05_odp.01", - "props": [ - { - "name": "label", - "value": "CP-09(05)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "time period and transfer rate consistent with the recovery time and recovery point objectives defined in the service provider and organization SLA." - } - ], - "guidelines": [ - { - "prose": "time period consistent with recovery time and recovery point objectives is defined;" - } - ] - }, - { - "id": "cp-09.05_odp.02", - "props": [ - { - "name": "label", - "value": "CP-09(05)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "transfer rate", - "constraints": [ - { - "description": "time period and transfer rate consistent with the recovery time and recovery point objectives defined in the service provider and organization SLA." - } - ], - "guidelines": [ - { - "prose": "transfer rate consistent with recovery time and recovery point objectives is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CP-09(05)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-9(5)" - }, - { - "name": "label", - "value": "CP-09(05)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-09.05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-9", - "rel": "required" - }, - { - "href": "#cp-7", - "rel": "related" - }, - { - "href": "#mp-3", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-9.5_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Transfer system backup information to the alternate storage site {{ insert: param, cp-9.5_prm_1 }}." - }, - { - "id": "cp-9.5_gdn", - "name": "guidance", - "prose": "System backup information can be transferred to alternate storage sites either electronically or by the physical shipment of storage media." - }, - { - "id": "cp-9.5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-09(05)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-9.5_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-09(05)[01]", - "class": "sp800-53a" - } - ], - "prose": "system backup information is transferred to the alternate storage site for {{ insert: param, cp-09.05_odp.01 }};", - "links": [ - { - "href": "#cp-9.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-9.5_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-09(05)[02]", - "class": "sp800-53a" - } - ], - "prose": "system backup information is transferred to the alternate storage site {{ insert: param, cp-09.05_odp.02 }}.", - "links": [ - { - "href": "#cp-9.5_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-9.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-9.5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-09(05)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing system backup\n\ncontingency plan\n\nsystem backup logs or records\n\nevidence of system backup information transferred to alternate storage site\n\nalternate storage site agreements\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-9.5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-09(05)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system backup responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "cp-9.5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-09(05)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for transferring system backups to the alternate storage site\n\nmechanisms supporting and/or implementing system backups\n\nmechanisms supporting and/or implementing information transfer to the alternate storage site" - } - ] - } - ] - }, - { - "id": "cp-9.8", - "class": "SP800-53-enhancement", - "title": "Cryptographic Protection", - "params": [ - { - "id": "cp-09.08_odp", - "props": [ - { - "name": "alt-identifier", - "value": "cp-9.8_prm_1" - }, - { - "name": "label", - "value": "CP-09(08)_ODP", - "class": "sp800-53a" - } - ], - "label": "backup information", - "constraints": [ - { - "description": "all backup files" - } - ], - "guidelines": [ - { - "prose": "backup information to protect against unauthorized disclosure and modification is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CP-09(08)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-9(8)" - }, - { - "name": "label", - "value": "CP-09(08)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-09.08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-9", - "rel": "required" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#sc-28", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-9.8_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of {{ insert: param, cp-09.08_odp }}." - }, - { - "id": "cp-9.8_gdn", - "name": "guidance", - "prose": "The selection of cryptographic mechanisms is based on the need to protect the confidentiality and integrity of backup information. The strength of mechanisms selected is commensurate with the security category or classification of the information. Cryptographic protection applies to system backup information in storage at both primary and alternate locations. Organizations that implement cryptographic mechanisms to protect information at rest also consider cryptographic key management solutions." - }, - { - "id": "cp-9.8_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "CP-9 (8) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "cp-9.8_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Note that this enhancement requires the use of cryptography which must be compliant with Federal requirements and utilize FIPS validated or NSA approved cryptography (see SC-13.)" - } - ] - }, - { - "id": "cp-9.8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-09(08)", - "class": "sp800-53a" - } - ], - "prose": "cryptographic mechanisms are implemented to prevent unauthorized disclosure and modification of {{ insert: param, cp-09.08_odp }}.", - "links": [ - { - "href": "#cp-9.8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-9.8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-09(08)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing system backup\n\ncontingency plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-9.8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-09(08)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system backup responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "cp-9.8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-09(08)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing cryptographic protection of backup information" - } - ] - } - ] - } - ] - }, - { - "id": "cp-10", - "class": "SP800-53", - "title": "System Recovery and Reconstitution", - "params": [ - { - "id": "cp-10_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cp-10_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "cp-10_odp.02" - } - ], - "label": "organization-defined time period consistent with recovery time and recovery point objectives" - }, - { - "id": "cp-10_odp.01", - "props": [ - { - "name": "label", - "value": "CP-10_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "time period", - "guidelines": [ - { - "prose": "time period consistent with recovery time and recovery point objectives for the recovery of the system is determined;" - } - ] - }, - { - "id": "cp-10_odp.02", - "props": [ - { - "name": "label", - "value": "CP-10_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "time period", - "guidelines": [ - { - "prose": "time period consistent with recovery time and recovery point objectives for the reconstitution of the system is determined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CP-10", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-10" - }, - { - "name": "label", - "value": "CP-10", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-10" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#bc39f179-c735-4da2-b7a7-b2b622119755", - "rel": "reference" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-4", - "rel": "related" - }, - { - "href": "#cp-6", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sc-24", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#si-13", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-10_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Provide for the recovery and reconstitution of the system to a known state within {{ insert: param, cp-10_prm_1 }} after a disruption, compromise, or failure." - }, - { - "id": "cp-10_gdn", - "name": "guidance", - "prose": "Recovery is executing contingency plan activities to restore organizational mission and business functions. Reconstitution takes place following recovery and includes activities for returning systems to fully operational states. Recovery and reconstitution operations reflect mission and business priorities; recovery point, recovery time, and reconstitution objectives; and organizational metrics consistent with contingency plan requirements. Reconstitution includes the deactivation of interim system capabilities that may have been needed during recovery operations. Reconstitution also includes assessments of fully restored system capabilities, reestablishment of continuous monitoring activities, system reauthorization (if required), and activities to prepare the system and organization for future disruptions, breaches, compromises, or failures. Recovery and reconstitution capabilities can include automated mechanisms and manual procedures. Organizations establish recovery time and recovery point objectives as part of contingency planning." - }, - { - "id": "cp-10_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-10", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "cp-10_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-10[01]", - "class": "sp800-53a" - } - ], - "prose": "the recovery of the system to a known state is provided within {{ insert: param, cp-10_odp.01 }} after a disruption, compromise, or failure;", - "links": [ - { - "href": "#cp-10_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-10_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "CP-10[02]", - "class": "sp800-53a" - } - ], - "prose": "a reconstitution of the system to a known state is provided within {{ insert: param, cp-10_odp.02 }} after a disruption, compromise, or failure.", - "links": [ - { - "href": "#cp-10_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#cp-10_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-10_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-10-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing system backup\n\ncontingency plan\n\nsystem backup test results\n\ncontingency plan test results\n\ncontingency plan test documentation\n\nredundant secondary system for system backups\n\nlocation(s) of redundant secondary backup system(s)\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-10_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-10-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with contingency planning, recovery, and/or reconstitution responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "cp-10_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-10-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes implementing system recovery and reconstitution operations\n\nmechanisms supporting and/or implementing system recovery and reconstitution operations" - } - ] - } - ], - "controls": [ - { - "id": "cp-10.2", - "class": "SP800-53-enhancement", - "title": "Transaction Recovery", - "props": [ - { - "name": "label", - "value": "CP-10(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-10(2)" - }, - { - "name": "label", - "value": "CP-10(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-10.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-10", - "rel": "required" - } - ], - "parts": [ - { - "id": "cp-10.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement transaction recovery for systems that are transaction-based." - }, - { - "id": "cp-10.2_gdn", - "name": "guidance", - "prose": "Transaction-based systems include database management systems and transaction processing systems. Mechanisms supporting transaction recovery include transaction rollback and transaction journaling." - }, - { - "id": "cp-10.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-10(02)", - "class": "sp800-53a" - } - ], - "prose": "transaction recovery is implemented for systems that are transaction-based.", - "links": [ - { - "href": "#cp-10.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-10.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-10(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing system recovery and reconstitution\n\ncontingency plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\ncontingency plan test documentation\n\ncontingency plan test results\n\nsystem transaction recovery records\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-10.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-10(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibility for transaction recovery\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "cp-10.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-10(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing transaction recovery capability" - } - ] - } - ] - }, - { - "id": "cp-10.4", - "class": "SP800-53-enhancement", - "title": "Restore Within Time Period", - "params": [ - { - "id": "cp-10.04_odp", - "props": [ - { - "name": "alt-identifier", - "value": "cp-10.4_prm_1" - }, - { - "name": "label", - "value": "CP-10(04)_ODP", - "class": "sp800-53a" - } - ], - "label": "restoration time periods", - "constraints": [ - { - "description": "time period consistent with the restoration time-periods defined in the service provider and organization SLA" - } - ], - "guidelines": [ - { - "prose": "restoration time period within which to restore system components to a known, operational state is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "CP-10(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "CP-10(4)" - }, - { - "name": "label", - "value": "CP-10(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "cp-10.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-10", - "rel": "required" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "cp-10.4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Provide the capability to restore system components within {{ insert: param, cp-10.04_odp }} from configuration-controlled and integrity-protected information representing a known, operational state for the components." - }, - { - "id": "cp-10.4_gdn", - "name": "guidance", - "prose": "Restoration of system components includes reimaging, which restores the components to known, operational states." - }, - { - "id": "cp-10.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "CP-10(04)", - "class": "sp800-53a" - } - ], - "prose": "the capability to restore system components within {{ insert: param, cp-10.04_odp }} from configuration-controlled and integrity-protected information representing a known, operational state for the components is provided.", - "links": [ - { - "href": "#cp-10.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "cp-10.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "CP-10(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Contingency planning policy\n\nprocedures addressing system recovery and reconstitution\n\ncontingency plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\ncontingency plan test documentation\n\ncontingency plan test results\n\nevidence of system recovery and reconstitution operations\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "cp-10.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "CP-10(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system recovery and reconstitution responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "cp-10.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "CP-10(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing the recovery/reconstitution of system information" - } - ] - } - ] - } - ] - } - ] - }, - { - "id": "ia", - "class": "family", - "title": "Identification and Authentication", - "controls": [ - { - "id": "ia-1", - "class": "SP800-53", - "title": "Policy and Procedures", - "params": [ - { - "id": "ia-1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ia-01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ia-01_odp.02" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "ia-01_odp.01", - "props": [ - { - "name": "label", - "value": "IA-01_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the identification and authentication policy is to be disseminated are defined;" - } - ] - }, - { - "id": "ia-01_odp.02", - "props": [ - { - "name": "label", - "value": "IA-01_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the identification and authentication procedures are to be disseminated is/are defined;" - } - ] - }, - { - "id": "ia-01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ia-1_prm_2" - }, - { - "name": "label", - "value": "IA-01_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "organization-level", - "mission/business process-level", - "system-level" - ] - } - }, - { - "id": "ia-01_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "ia-1_prm_3" - }, - { - "name": "label", - "value": "IA-01_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "official", - "guidelines": [ - { - "prose": "an official to manage the identification and authentication policy and procedures is defined;" - } - ] - }, - { - "id": "ia-01_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "ia-1_prm_4" - }, - { - "name": "label", - "value": "IA-01_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current identification and authentication policy is reviewed and updated is defined;" - } - ] - }, - { - "id": "ia-01_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "ia-1_prm_5" - }, - { - "name": "label", - "value": "IA-01_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that would require the current identification and authentication policy to be reviewed and updated are defined;" - } - ] - }, - { - "id": "ia-01_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "ia-1_prm_6" - }, - { - "name": "label", - "value": "IA-01_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current identification and authentication procedures are reviewed and updated is defined;" - } - ] - }, - { - "id": "ia-01_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "ia-1_prm_7" - }, - { - "name": "label", - "value": "IA-01_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "events", - "constraints": [ - { - "description": "significant changes" - } - ], - "guidelines": [ - { - "prose": "events that would require identification and authentication procedures to be reviewed and updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IA-01", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-1" - }, - { - "name": "label", - "value": "IA-01", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#7ba1d91c-3934-4d5a-8532-b32f864ad34c", - "rel": "reference" - }, - { - "href": "#c7ac44e8-10db-4b64-b2b9-9e32ec1efed0", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#737513fa-6758-403f-831d-5ddab5e23cb3", - "rel": "reference" - }, - { - "href": "#858705be-3c1f-48aa-a328-0ce398d95ef0", - "rel": "reference" - }, - { - "href": "#7af2e6ec-9f7e-4232-ad3f-09888eb0793a", - "rel": "reference" - }, - { - "href": "#828856bd-d7c4-427b-8b51-815517ec382d", - "rel": "reference" - }, - { - "href": "#4c0ec2ee-a0d6-428a-9043-4504bc3ade6f", - "rel": "reference" - }, - { - "href": "#7f473f21-fdbf-4a6c-81a1-0ab95919609d", - "rel": "reference" - }, - { - "href": "#ac-1", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "ia-1_smt", - "name": "statement", - "parts": [ - { - "id": "ia-1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, a policy that addresses Identification and Authentication MUST be associated with IA-1 part a.", - "class": "policy" - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, at least one procedure that addresses Incident Response MUST be associated with IA-1 part a.", - "class": "procedure" - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, document, and disseminate to {{ insert: param, ia-1_prm_1 }}:", - "parts": [ - { - "id": "ia-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, ia-01_odp.03 }} identification and authentication policy that:", - "parts": [ - { - "id": "ia-1_smt.a.1.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "ia-1_smt.a.1.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and" - } - ] - }, - { - "id": "ia-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the identification and authentication policy and the associated identification and authentication controls;" - } - ] - }, - { - "id": "ia-1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Designate an {{ insert: param, ia-01_odp.04 }} to manage the development, documentation, and dissemination of the identification and authentication policy and procedures; and" - }, - { - "id": "ia-1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the current identification and authentication:", - "parts": [ - { - "id": "ia-1_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Policy {{ insert: param, ia-01_odp.05 }} and following {{ insert: param, ia-01_odp.06 }} ; and" - }, - { - "id": "ia-1_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures {{ insert: param, ia-01_odp.07 }} and following {{ insert: param, ia-01_odp.08 }}." - } - ] - } - ] - }, - { - "id": "ia-1_gdn", - "name": "guidance", - "prose": "Identification and authentication policy and procedures address the controls in the IA family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of identification and authentication policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to identification and authentication policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure." - }, - { - "id": "ia-1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-01a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-01a.[01]", - "class": "sp800-53a" - } - ], - "prose": "an identification and authentication policy is developed and documented;", - "links": [ - { - "href": "#ia-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-01a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the identification and authentication policy is disseminated to {{ insert: param, ia-01_odp.01 }};", - "links": [ - { - "href": "#ia-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-1_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-01a.[03]", - "class": "sp800-53a" - } - ], - "prose": "identification and authentication procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls are developed and documented;", - "links": [ - { - "href": "#ia-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-1_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-01a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the identification and authentication procedures are disseminated to {{ insert: param, ia-01_odp.02 }};", - "links": [ - { - "href": "#ia-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-1_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-01a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-1_obj.a.1.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-01a.01(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-1_obj.a.1.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-01a.01(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ia-01_odp.03 }} identification and authentication policy addresses purpose;", - "links": [ - { - "href": "#ia-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-1_obj.a.1.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-01a.01(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ia-01_odp.03 }} identification and authentication policy addresses scope;", - "links": [ - { - "href": "#ia-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-1_obj.a.1.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-01a.01(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ia-01_odp.03 }} identification and authentication policy addresses roles;", - "links": [ - { - "href": "#ia-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-1_obj.a.1.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-01a.01(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ia-01_odp.03 }} identification and authentication policy addresses responsibilities;", - "links": [ - { - "href": "#ia-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-1_obj.a.1.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-01a.01(a)[05]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ia-01_odp.03 }} identification and authentication policy addresses management commitment;", - "links": [ - { - "href": "#ia-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-1_obj.a.1.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-01a.01(a)[06]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ia-01_odp.03 }} identification and authentication policy addresses coordination among organizational entities;", - "links": [ - { - "href": "#ia-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-1_obj.a.1.a-7", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-01a.01(a)[07]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ia-01_odp.03 }} identification and authentication policy addresses compliance;", - "links": [ - { - "href": "#ia-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-1_obj.a.1.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-01a.01(b)", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ia-01_odp.03 }} identification and authentication policy is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines;", - "links": [ - { - "href": "#ia-1_smt.a.1.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-1_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-01b.", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ia-01_odp.04 }} is designated to manage the development, documentation, and dissemination of the identification and authentication policy and procedures;", - "links": [ - { - "href": "#ia-1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-01c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-1_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-01c.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-1_obj.c.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-01c.01[01]", - "class": "sp800-53a" - } - ], - "prose": "the current identification and authentication policy is reviewed and updated {{ insert: param, ia-01_odp.05 }};", - "links": [ - { - "href": "#ia-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-1_obj.c.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-01c.01[02]", - "class": "sp800-53a" - } - ], - "prose": "the current identification and authentication policy is reviewed and updated following {{ insert: param, ia-01_odp.06 }};", - "links": [ - { - "href": "#ia-1_smt.c.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-1_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-01c.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-1_obj.c.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-01c.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the current identification and authentication procedures are reviewed and updated {{ insert: param, ia-01_odp.07 }};", - "links": [ - { - "href": "#ia-1_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-1_obj.c.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-01c.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the current identification and authentication procedures are reviewed and updated following {{ insert: param, ia-01_odp.08 }}.", - "links": [ - { - "href": "#ia-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-1_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-01-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy and procedures\n\nsystem security plan\n\nprivacy plan\n\nrisk management strategy documentation\n\nlist of events requiring identification and authentication procedures to be reviewed and updated (e.g., audit findings)\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-01-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with identification and authentication responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - }, - { - "id": "ia-2", - "class": "SP800-53", - "title": "Identification and Authentication (Organizational Users)", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "IA-02", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-2" - }, - { - "name": "label", - "value": "IA-02", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#678e3d6c-150b-4393-aec5-6e3481eb1e00", - "rel": "reference" - }, - { - "href": "#7ba1d91c-3934-4d5a-8532-b32f864ad34c", - "rel": "reference" - }, - { - "href": "#a295ca19-8c75-4b4c-8800-98024732e181", - "rel": "reference" - }, - { - "href": "#737513fa-6758-403f-831d-5ddab5e23cb3", - "rel": "reference" - }, - { - "href": "#858705be-3c1f-48aa-a328-0ce398d95ef0", - "rel": "reference" - }, - { - "href": "#7af2e6ec-9f7e-4232-ad3f-09888eb0793a", - "rel": "reference" - }, - { - "href": "#828856bd-d7c4-427b-8b51-815517ec382d", - "rel": "reference" - }, - { - "href": "#10963761-58fc-4b20-b3d6-b44a54daba03", - "rel": "reference" - }, - { - "href": "#d9e036ba-6eec-46a6-9340-b0bf1fea23b4", - "rel": "reference" - }, - { - "href": "#e8552d48-cf41-40aa-8b06-f45f7fb4706c", - "rel": "reference" - }, - { - "href": "#15dc76ff-b17a-4eeb-8948-8ea8de3ccc2c", - "rel": "reference" - }, - { - "href": "#4b38e961-1125-4a5b-aa35-1d6c02846dad", - "rel": "reference" - }, - { - "href": "#91701292-8bcd-4d2e-a5bd-59ab61e34b3c", - "rel": "reference" - }, - { - "href": "#4f5f51ac-2b8d-4b90-a3c7-46f56e967617", - "rel": "reference" - }, - { - "href": "#604774da-9e1d-48eb-9c62-4e959dc80737", - "rel": "reference" - }, - { - "href": "#7f473f21-fdbf-4a6c-81a1-0ab95919609d", - "rel": "reference" - }, - { - "href": "#3915a084-b87b-4f02-83d4-c369e746292f", - "rel": "reference" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-14", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#au-1", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ia-13", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#ma-5", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - } - ], - "parts": [ - { - "id": "ia-2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Uniquely identify and authenticate organizational users and associate that unique identification with processes acting on behalf of those users." - }, - { - "id": "ia-2_gdn", - "name": "guidance", - "prose": "Organizations can satisfy the identification and authentication requirements by complying with the requirements in [HSPD 12](#f16e438e-7114-4144-bfe2-2dfcad8cb2d0) . Organizational users include employees or individuals who organizations consider to have an equivalent status to employees (e.g., contractors and guest researchers). Unique identification and authentication of users applies to all accesses other than those that are explicitly identified in [AC-14](#ac-14) and that occur through the authorized use of group authenticators without individual authentication. Since processes execute on behalf of groups and roles, organizations may require unique identification of individuals in group accounts or for detailed accountability of individual activity.\n\nOrganizations employ passwords, physical authenticators, or biometrics to authenticate user identities or, in the case of multi-factor authentication, some combination thereof. Access to organizational systems is defined as either local access or network access. Local access is any access to organizational systems by users or processes acting on behalf of users, where access is obtained through direct connections without the use of networks. Network access is access to organizational systems by users (or processes acting on behalf of users) where access is obtained through network connections (i.e., nonlocal accesses). Remote access is a type of network access that involves communication through external networks. Internal networks include local area networks and wide area networks.\n\nThe use of encrypted virtual private networks for network connections between organization-controlled endpoints and non-organization-controlled endpoints may be treated as internal networks with respect to protecting the confidentiality and integrity of information traversing the network. Identification and authentication requirements for non-organizational users are described in [IA-8](#ia-8)." - }, - { - "id": "ia-2_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "IA-2 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ia-2_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "For all control enhancements that specify multifactor authentication, the implementation must adhere to the Digital Identity Guidelines specified in NIST Special Publication 800-63B." - }, - { - "id": "ia-2_fr_smt.2", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Multi-factor authentication must be phishing-resistant." - }, - { - "id": "ia-2_fr_smt.3", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "All uses of encrypted virtual private networks must meet all applicable Federal requirements and architecture, dataflow, and security and privacy controls must be documented, assessed, and authorized to operate." - }, - { - "id": "ia-2_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "\"Phishing-resistant\" authentication refers to authentication processes designed to detect and prevent disclosure of authentication secrets and outputs to a website or application masquerading as a legitimate system." - } - ] - }, - { - "id": "ia-2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-2_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-02[01]", - "class": "sp800-53a" - } - ], - "prose": "organizational users are uniquely identified and authenticated;", - "links": [ - { - "href": "#ia-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-2_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-02[02]", - "class": "sp800-53a" - } - ], - "prose": "the unique identification of authenticated organizational users is associated with processes acting on behalf of those users.", - "links": [ - { - "href": "#ia-2_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-02-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user identification and authentication\n\nsystem security plan, system design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nlist of system accounts\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-02-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system operations responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\norganizational personnel with account management responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "ia-2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-02-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for uniquely identifying and authenticating users\n\nmechanisms supporting and/or implementing identification and authentication capabilities" - } - ] - } - ], - "controls": [ - { - "id": "ia-2.1", - "class": "SP800-53-enhancement", - "title": "Multi-factor Authentication to Privileged Accounts", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "IA-02(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-2(1)" - }, - { - "name": "label", - "value": "IA-02(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-02.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ia-2", - "rel": "required" - }, - { - "href": "#ac-5", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "ia-2.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement multi-factor authentication for access to privileged accounts." - }, - { - "id": "ia-2.1_gdn", - "name": "guidance", - "prose": "Multi-factor authentication requires the use of two or more different factors to achieve authentication. The authentication factors are defined as follows: something you know (e.g., a personal identification number \\[PIN\\]), something you have (e.g., a physical authenticator such as a cryptographic private key), or something you are (e.g., a biometric). Multi-factor authentication solutions that feature physical authenticators include hardware authenticators that provide time-based or challenge-response outputs and smart cards such as the U.S. Government Personal Identity Verification (PIV) card or the Department of Defense (DoD) Common Access Card (CAC). In addition to authenticating users at the system level (i.e., at logon), organizations may employ authentication mechanisms at the application level, at their discretion, to provide increased security. Regardless of the type of access (i.e., local, network, remote), privileged accounts are authenticated using multi-factor options appropriate for the level of risk. Organizations can add additional security measures, such as additional or more rigorous authentication mechanisms, for specific types of access." - }, - { - "id": "ia-2.1_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "IA-2 (1) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ia-2.1_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "According to SP 800-63-3, SP 800-63A (IAL), SP 800-63B (AAL), and SP 800-63C (FAL)." - }, - { - "id": "ia-2.1_fr_smt.2", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Multi-factor authentication must be phishing-resistant." - }, - { - "id": "ia-2.1_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Multi-factor authentication to subsequent components in the same user domain is not required." - } - ] - }, - { - "id": "ia-2.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-02(01)", - "class": "sp800-53a" - } - ], - "prose": "multi-factor authentication is implemented for access to privileged accounts.", - "links": [ - { - "href": "#ia-2.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-2.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-02(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user identification and authentication\n\nsystem security plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nlist of system accounts\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-2.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-02(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system operations responsibilities\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "ia-2.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-02(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing a multi-factor authentication capability" - } - ] - } - ] - }, - { - "id": "ia-2.2", - "class": "SP800-53-enhancement", - "title": "Multi-factor Authentication to Non-privileged Accounts", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "IA-02(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-2(2)" - }, - { - "name": "label", - "value": "IA-02(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-02.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ia-2", - "rel": "required" - }, - { - "href": "#ac-5", - "rel": "related" - } - ], - "parts": [ - { - "id": "ia-2.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement multi-factor authentication for access to non-privileged accounts." - }, - { - "id": "ia-2.2_gdn", - "name": "guidance", - "prose": "Multi-factor authentication requires the use of two or more different factors to achieve authentication. The authentication factors are defined as follows: something you know (e.g., a personal identification number \\[PIN\\]), something you have (e.g., a physical authenticator such as a cryptographic private key), or something you are (e.g., a biometric). Multi-factor authentication solutions that feature physical authenticators include hardware authenticators that provide time-based or challenge-response outputs and smart cards such as the U.S. Government Personal Identity Verification card or the DoD Common Access Card. In addition to authenticating users at the system level, organizations may also employ authentication mechanisms at the application level, at their discretion, to provide increased information security. Regardless of the type of access (i.e., local, network, remote), non-privileged accounts are authenticated using multi-factor options appropriate for the level of risk. Organizations can provide additional security measures, such as additional or more rigorous authentication mechanisms, for specific types of access." - }, - { - "id": "ia-2.2_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "IA-2 (2) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ia-2.2_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "According to SP 800-63-3, SP 800-63A (IAL), SP 800-63B (AAL), and SP 800-63C (FAL)." - }, - { - "id": "ia-2.2_fr_smt.2", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Multi-factor authentication must be phishing-resistant." - }, - { - "id": "ia-2.2_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Multi-factor authentication to subsequent components in the same user domain is not required." - } - ] - }, - { - "id": "ia-2.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-02(02)", - "class": "sp800-53a" - } - ], - "prose": "multi-factor authentication for access to non-privileged accounts is implemented.", - "links": [ - { - "href": "#ia-2.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-2.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-02(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nsystem security plan\n\nprocedures addressing user identification and authentication\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nlist of system accounts\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-2.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-02(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system operations responsibilities\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "ia-2.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-02(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing a multi-factor authentication capability" - } - ] - } - ] - }, - { - "id": "ia-2.5", - "class": "SP800-53-enhancement", - "title": "Individual Authentication with Group Authentication", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "IA-02(05)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-2(5)" - }, - { - "name": "label", - "value": "IA-02(05)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-02.05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ia-2", - "rel": "required" - } - ], - "parts": [ - { - "id": "ia-2.5_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "When shared accounts or authenticators are employed, require users to be individually authenticated before granting access to the shared accounts or resources." - }, - { - "id": "ia-2.5_gdn", - "name": "guidance", - "prose": "Individual authentication prior to shared group authentication mitigates the risk of using group accounts or authenticators." - }, - { - "id": "ia-2.5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-02(05)", - "class": "sp800-53a" - } - ], - "prose": "users are required to be individually authenticated before granting access to the shared accounts or resources when shared accounts or authenticators are employed.", - "links": [ - { - "href": "#ia-2.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-2.5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-02(05)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nsystem security plan\n\nprocedures addressing user identification and authentication\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nlist of system accounts\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-2.5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-02(05)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system operations responsibilities\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "ia-2.5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-02(05)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing an authentication capability for group accounts" - } - ] - } - ] - }, - { - "id": "ia-2.6", - "class": "SP800-53-enhancement", - "title": "Access to Accounts —separate Device", - "params": [ - { - "id": "ia-02.06_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ia-2.6_prm_1" - }, - { - "name": "label", - "value": "IA-02(06)_ODP[01]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "local, network and remote" - } - ] - }, - { - "id": "ia-02.06_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ia-2.6_prm_2" - }, - { - "name": "label", - "value": "IA-02(06)_ODP[02]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "privileged accounts; non-privileged accounts" - } - ] - }, - { - "id": "ia-02.06_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ia-2.6_prm_3" - }, - { - "name": "label", - "value": "IA-02(06)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "strength of mechanism requirements", - "constraints": [ - { - "description": "FIPS-validated or NSA-approved cryptography" - } - ], - "guidelines": [ - { - "prose": "the strength of mechanism requirements to be enforced by a device separate from the system gaining access to accounts is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "IA-02(06)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-2(6)" - }, - { - "name": "label", - "value": "IA-02(06)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-02.06" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ia-2", - "rel": "required" - }, - { - "href": "#ac-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "ia-2.6_smt", - "name": "statement", - "prose": "Implement multi-factor authentication for {{ insert: param, ia-02.06_odp.01 }} access to {{ insert: param, ia-02.06_odp.02 }} such that:", - "parts": [ - { - "id": "ia-2.6_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "One of the factors is provided by a device separate from the system gaining access; and" - }, - { - "id": "ia-2.6_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "The device meets {{ insert: param, ia-02.06_odp.03 }}." - } - ] - }, - { - "id": "ia-2.6_gdn", - "name": "guidance", - "prose": "The purpose of requiring a device that is separate from the system to which the user is attempting to gain access for one of the factors during multi-factor authentication is to reduce the likelihood of compromising authenticators or credentials stored on the system. Adversaries may be able to compromise such authenticators or credentials and subsequently impersonate authorized users. Implementing one of the factors on a separate device (e.g., a hardware token), provides a greater strength of mechanism and an increased level of assurance in the authentication process." - }, - { - "id": "ia-2.6_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "IA-2 (6) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ia-2.6_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "PIV=separate device. Please refer to NIST SP 800-157 Guidelines for Derived Personal Identity Verification (PIV) Credentials." - }, - { - "id": "ia-2.6_fr_gdn.2", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "See SC-13 Guidance for more information on FIPS-validated or NSA-approved cryptography." - } - ] - }, - { - "id": "ia-2.6_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-02(06)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-2.6_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-02(06)(a)", - "class": "sp800-53a" - } - ], - "prose": "multi-factor authentication is implemented for {{ insert: param, ia-02.06_odp.01 }} access to {{ insert: param, ia-02.06_odp.02 }} such that one of the factors is provided by a device separate from the system gaining access;", - "links": [ - { - "href": "#ia-2.6_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-2.6_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-02(06)(b)", - "class": "sp800-53a" - } - ], - "prose": "multi-factor authentication is implemented for {{ insert: param, ia-02.06_odp.01 }} access to {{ insert: param, ia-02.06_odp.02 }} such that the device meets {{ insert: param, ia-02.06_odp.03 }}.", - "links": [ - { - "href": "#ia-2.6_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-2.6_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-2.6_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-02(06)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nsystem security plan\n\nprocedures addressing user identification and authentication\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nlist of system accounts\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-2.6_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-02(06)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system operations responsibilities\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "ia-2.6_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-02(06)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing multi-factor authentication capability" - } - ] - } - ] - }, - { - "id": "ia-2.8", - "class": "SP800-53-enhancement", - "title": "Access to Accounts — Replay Resistant", - "params": [ - { - "id": "ia-02.08_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ia-2.8_prm_1" - }, - { - "name": "label", - "value": "IA-02(08)_ODP", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "privileged accounts; non-privileged accounts" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "IA-02(08)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-2(8)" - }, - { - "name": "label", - "value": "IA-02(08)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-02.08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ia-2", - "rel": "required" - } - ], - "parts": [ - { - "id": "ia-2.8_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement replay-resistant authentication mechanisms for access to {{ insert: param, ia-02.08_odp }}." - }, - { - "id": "ia-2.8_gdn", - "name": "guidance", - "prose": "Authentication processes resist replay attacks if it is impractical to achieve successful authentications by replaying previous authentication messages. Replay-resistant techniques include protocols that use nonces or challenges such as time synchronous or cryptographic authenticators." - }, - { - "id": "ia-2.8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-02(08)", - "class": "sp800-53a" - } - ], - "prose": "replay-resistant authentication mechanisms for access to {{ insert: param, ia-02.08_odp }} are implemented.", - "links": [ - { - "href": "#ia-2.8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-2.8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-02(08)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nsystem security plan\n\nprocedures addressing user identification and authentication\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nlist of privileged system accounts\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-2.8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-02(08)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system operations responsibilities\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "ia-2.8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-02(08)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing identification and authentication capabilities\n\nMechanisms supporting and/or implementing replay-resistant authentication mechanisms" - } - ] - } - ] - }, - { - "id": "ia-2.12", - "class": "SP800-53-enhancement", - "title": "Acceptance of PIV Credentials", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "IA-02(12)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-2(12)" - }, - { - "name": "label", - "value": "IA-02(12)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-02.12" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ia-2", - "rel": "required" - } - ], - "parts": [ - { - "id": "ia-2.12_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Accept and electronically verify Personal Identity Verification-compliant credentials." - }, - { - "id": "ia-2.12_gdn", - "name": "guidance", - "prose": "Acceptance of Personal Identity Verification (PIV)-compliant credentials applies to organizations implementing logical access control and physical access control systems. PIV-compliant credentials are those credentials issued by federal agencies that conform to FIPS Publication 201 and supporting guidance documents. The adequacy and reliability of PIV card issuers are authorized using [SP 800-79-2](#10963761-58fc-4b20-b3d6-b44a54daba03) . Acceptance of PIV-compliant credentials includes derived PIV credentials, the use of which is addressed in [SP 800-166](#e8552d48-cf41-40aa-8b06-f45f7fb4706c) . The DOD Common Access Card (CAC) is an example of a PIV credential." - }, - { - "id": "ia-2.12_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "IA-2 (12) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ia-2.12_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Include Common Access Card (CAC), i.e., the DoD technical implementation of PIV/FIPS 201/HSPD-12." - } - ] - }, - { - "id": "ia-2.12_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-02(12)", - "class": "sp800-53a" - } - ], - "prose": "Personal Identity Verification-compliant credentials are accepted and electronically verified.", - "links": [ - { - "href": "#ia-2.12_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-2.12_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-02(12)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nsystem security plan\n\nprocedures addressing user identification and authentication\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nPIV verification records\n\nevidence of PIV credentials\n\nPIV credential authorizations\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-2.12_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-02(12)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system operations responsibilities\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "ia-2.12_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-02(12)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing acceptance and verification of PIV credentials" - } - ] - } - ] - } - ] - }, - { - "id": "ia-3", - "class": "SP800-53", - "title": "Device Identification and Authentication", - "params": [ - { - "id": "ia-03_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ia-3_prm_1" - }, - { - "name": "label", - "value": "IA-03_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "devices and/or types of devices", - "guidelines": [ - { - "prose": "devices and/or types of devices to be uniquely identified and authenticated before establishing a connection are defined;" - } - ] - }, - { - "id": "ia-03_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ia-3_prm_2" - }, - { - "name": "label", - "value": "IA-03_ODP[02]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "local", - "remote", - "network" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "IA-03", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-3" - }, - { - "name": "label", - "value": "IA-03", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#ca-3", - "rel": "related" - }, - { - "href": "#ca-9", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ia-9", - "rel": "related" - }, - { - "href": "#ia-11", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ia-13", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "ia-3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Uniquely identify and authenticate {{ insert: param, ia-03_odp.01 }} before establishing a {{ insert: param, ia-03_odp.02 }} connection." - }, - { - "id": "ia-3_gdn", - "name": "guidance", - "prose": "Devices that require unique device-to-device identification and authentication are defined by type, device, or a combination of type and device. Organization-defined device types include devices that are not owned by the organization. Systems use shared known information (e.g., Media Access Control \\[MAC\\], Transmission Control Protocol/Internet Protocol \\[TCP/IP\\] addresses) for device identification or organizational authentication solutions (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.1x and Extensible Authentication Protocol \\[EAP\\], RADIUS server with EAP-Transport Layer Security \\[TLS\\] authentication, Kerberos) to identify and authenticate devices on local and wide area networks. Organizations determine the required strength of authentication mechanisms based on the security categories of systems and mission or business requirements. Because of the challenges of implementing device authentication on a large scale, organizations can restrict the application of the control to a limited number/type of devices based on mission or business needs." - }, - { - "id": "ia-3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-03", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ia-03_odp.01 }} are uniquely identified and authenticated before establishing a {{ insert: param, ia-03_odp.02 }} connection.", - "links": [ - { - "href": "#ia-3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-03-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nsystem security plan\n\nprocedures addressing device identification and authentication\n\nsystem design documentation\n\nlist of devices requiring unique identification and authentication\n\ndevice connection reports\n\nsystem configuration settings and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-03-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with operational responsibilities for device identification and authentication\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "ia-3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-03-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing device identification and authentication capabilities" - } - ] - } - ] - }, - { - "id": "ia-4", - "class": "SP800-53", - "title": "Identifier Management", - "params": [ - { - "id": "ia-04_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ia-4_prm_1" - }, - { - "name": "label", - "value": "IA-04_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "constraints": [ - { - "description": "at a minimum, the ISSO (or similar role within the organization)" - } - ], - "guidelines": [ - { - "prose": "personnel or roles from whom authorization must be received to assign an identifier are defined;" - } - ] - }, - { - "id": "ia-04_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ia-4_prm_2" - }, - { - "name": "label", - "value": "IA-04_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "at least two (2) years" - } - ], - "guidelines": [ - { - "prose": "a time period for preventing reuse of identifiers is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "IA-04", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-4" - }, - { - "name": "label", - "value": "IA-04", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#7ba1d91c-3934-4d5a-8532-b32f864ad34c", - "rel": "reference" - }, - { - "href": "#737513fa-6758-403f-831d-5ddab5e23cb3", - "rel": "reference" - }, - { - "href": "#858705be-3c1f-48aa-a328-0ce398d95ef0", - "rel": "reference" - }, - { - "href": "#7af2e6ec-9f7e-4232-ad3f-09888eb0793a", - "rel": "reference" - }, - { - "href": "#828856bd-d7c4-427b-8b51-815517ec382d", - "rel": "reference" - }, - { - "href": "#ac-5", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ia-9", - "rel": "related" - }, - { - "href": "#ia-12", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pe-4", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-12", - "rel": "related" - }, - { - "href": "#ps-3", - "rel": "related" - }, - { - "href": "#ps-4", - "rel": "related" - }, - { - "href": "#ps-5", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-37", - "rel": "related" - } - ], - "parts": [ - { - "id": "ia-4_smt", - "name": "statement", - "prose": "Manage system identifiers by:", - "parts": [ - { - "id": "ia-4_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Receiving authorization from {{ insert: param, ia-04_odp.01 }} to assign an individual, group, role, service, or device identifier;" - }, - { - "id": "ia-4_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Selecting an identifier that identifies an individual, group, role, service, or device;" - }, - { - "id": "ia-4_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Assigning the identifier to the intended individual, group, role, service, or device; and" - }, - { - "id": "ia-4_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Preventing reuse of identifiers for {{ insert: param, ia-04_odp.02 }}." - } - ] - }, - { - "id": "ia-4_gdn", - "name": "guidance", - "prose": "Common device identifiers include Media Access Control (MAC) addresses, Internet Protocol (IP) addresses, or device-unique token identifiers. The management of individual identifiers is not applicable to shared system accounts. Typically, individual identifiers are the usernames of the system accounts assigned to those individuals. In such instances, the account management activities of [AC-2](#ac-2) use account names provided by [IA-4](#ia-4) . Identifier management also addresses individual identifiers not necessarily associated with system accounts. Preventing the reuse of identifiers implies preventing the assignment of previously used individual, group, role, service, or device identifiers to different individuals, groups, roles, services, or devices." - }, - { - "id": "ia-4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-04", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-4_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-04a.", - "class": "sp800-53a" - } - ], - "prose": "system identifiers are managed by receiving authorization from {{ insert: param, ia-04_odp.01 }} to assign to an individual, group, role, or device identifier;", - "links": [ - { - "href": "#ia-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-4_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-04b.", - "class": "sp800-53a" - } - ], - "prose": "system identifiers are managed by selecting an identifier that identifies an individual, group, role, service, or device;", - "links": [ - { - "href": "#ia-4_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-4_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-04c.", - "class": "sp800-53a" - } - ], - "prose": "system identifiers are managed by assigning the identifier to the intended individual, group, role, service, or device;", - "links": [ - { - "href": "#ia-4_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-4_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-04d.", - "class": "sp800-53a" - } - ], - "prose": "system identifiers are managed by preventing reuse of identifiers for {{ insert: param, ia-04_odp.02 }}.", - "links": [ - { - "href": "#ia-4_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-04-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nprocedures addressing identifier management\n\nprocedures addressing account management\n\nsystem security plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of system accounts\n\nlist of identifiers generated from physical access control devices\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-04-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with identifier management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "ia-4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-04-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing identifier management" - } - ] - } - ], - "controls": [ - { - "id": "ia-4.4", - "class": "SP800-53-enhancement", - "title": "Identify User Status", - "params": [ - { - "id": "ia-04.04_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ia-4.4_prm_1" - }, - { - "name": "alt-label", - "value": "characteristic identifying individual status", - "class": "sp800-53" - }, - { - "name": "label", - "value": "IA-04(04)_ODP", - "class": "sp800-53a" - } - ], - "label": "characteristics", - "constraints": [ - { - "description": "contractors; foreign nationals" - } - ], - "guidelines": [ - { - "prose": "characteristics used to identify individual status is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IA-04(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-4(4)" - }, - { - "name": "label", - "value": "IA-04(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-04.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ia-4", - "rel": "required" - } - ], - "parts": [ - { - "id": "ia-4.4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Manage individual identifiers by uniquely identifying each individual as {{ insert: param, ia-04.04_odp }}." - }, - { - "id": "ia-4.4_gdn", - "name": "guidance", - "prose": "Characteristics that identify the status of individuals include contractors, foreign nationals, and non-organizational users. Identifying the status of individuals by these characteristics provides additional information about the people with whom organizational personnel are communicating. For example, it might be useful for a government employee to know that one of the individuals on an email message is a contractor." - }, - { - "id": "ia-4.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-04(04)", - "class": "sp800-53a" - } - ], - "prose": "individual identifiers are managed by uniquely identifying each individual as {{ insert: param, ia-04.04_odp }}.", - "links": [ - { - "href": "#ia-4.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-4.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-04(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nsystem security plan\n\nprocedures addressing identifier management\n\nprocedures addressing account management\n\nlist of characteristics identifying individual status\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-4.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-04(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with identifier management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "ia-4.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-04(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing identifier management" - } - ] - } - ] - } - ] - }, - { - "id": "ia-5", - "class": "SP800-53", - "title": "Authenticator Management", - "params": [ - { - "id": "ia-05_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ia-5_prm_1" - }, - { - "name": "label", - "value": "IA-05_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "time period by authenticator type", - "guidelines": [ - { - "prose": "a time period for changing or refreshing authenticators by authenticator type is defined;" - } - ] - }, - { - "id": "ia-05_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ia-5_prm_2" - }, - { - "name": "label", - "value": "IA-05_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that trigger the change or refreshment of authenticators are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "IA-05", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-5" - }, - { - "name": "label", - "value": "IA-05", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#678e3d6c-150b-4393-aec5-6e3481eb1e00", - "rel": "reference" - }, - { - "href": "#eea3c092-42ed-4382-a6f4-1adadef01b9d", - "rel": "reference" - }, - { - "href": "#7ba1d91c-3934-4d5a-8532-b32f864ad34c", - "rel": "reference" - }, - { - "href": "#a295ca19-8c75-4b4c-8800-98024732e181", - "rel": "reference" - }, - { - "href": "#737513fa-6758-403f-831d-5ddab5e23cb3", - "rel": "reference" - }, - { - "href": "#858705be-3c1f-48aa-a328-0ce398d95ef0", - "rel": "reference" - }, - { - "href": "#7af2e6ec-9f7e-4232-ad3f-09888eb0793a", - "rel": "reference" - }, - { - "href": "#828856bd-d7c4-427b-8b51-815517ec382d", - "rel": "reference" - }, - { - "href": "#15dc76ff-b17a-4eeb-8948-8ea8de3ccc2c", - "rel": "reference" - }, - { - "href": "#91701292-8bcd-4d2e-a5bd-59ab61e34b3c", - "rel": "reference" - }, - { - "href": "#4f5f51ac-2b8d-4b90-a3c7-46f56e967617", - "rel": "reference" - }, - { - "href": "#604774da-9e1d-48eb-9c62-4e959dc80737", - "rel": "reference" - }, - { - "href": "#81aeb0a3-d0ee-4e44-b842-6bf28d2bd7f5", - "rel": "reference" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-7", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ia-9", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ], - "parts": [ - { - "id": "ia-5_smt", - "name": "statement", - "prose": "Manage system authenticators by:", - "parts": [ - { - "id": "ia-5_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Verifying, as part of the initial authenticator distribution, the identity of the individual, group, role, service, or device receiving the authenticator;" - }, - { - "id": "ia-5_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Establishing initial authenticator content for any authenticators issued by the organization;" - }, - { - "id": "ia-5_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Ensuring that authenticators have sufficient strength of mechanism for their intended use;" - }, - { - "id": "ia-5_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Establishing and implementing administrative procedures for initial authenticator distribution, for lost or compromised or damaged authenticators, and for revoking authenticators;" - }, - { - "id": "ia-5_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Changing default authenticators prior to first use;" - }, - { - "id": "ia-5_smt.f", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "f." - } - ], - "prose": "Changing or refreshing authenticators {{ insert: param, ia-05_odp.01 }} or when {{ insert: param, ia-05_odp.02 }} occur;" - }, - { - "id": "ia-5_smt.g", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "g." - } - ], - "prose": "Protecting authenticator content from unauthorized disclosure and modification;" - }, - { - "id": "ia-5_smt.h", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "h." - } - ], - "prose": "Requiring individuals to take, and having devices implement, specific controls to protect authenticators; and" - }, - { - "id": "ia-5_smt.i", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "i." - } - ], - "prose": "Changing authenticators for group or role accounts when membership to those accounts changes." - } - ] - }, - { - "id": "ia-5_gdn", - "name": "guidance", - "prose": "Authenticators include passwords, cryptographic devices, biometrics, certificates, one-time password devices, and ID badges. Device authenticators include certificates and passwords. Initial authenticator content is the actual content of the authenticator (e.g., the initial password). In contrast, the requirements for authenticator content contain specific criteria or characteristics (e.g., minimum password length). Developers may deliver system components with factory default authentication credentials (i.e., passwords) to allow for initial installation and configuration. Default authentication credentials are often well known, easily discoverable, and present a significant risk. The requirement to protect individual authenticators may be implemented via control [PL-4](#pl-4) or [PS-6](#ps-6) for authenticators in the possession of individuals and by controls [AC-3](#ac-3), [AC-6](#ac-6) , and [SC-28](#sc-28) for authenticators stored in organizational systems, including passwords stored in hashed or encrypted formats or files containing encrypted or hashed passwords accessible with administrator privileges.\n\nSystems support authenticator management by organization-defined settings and restrictions for various authenticator characteristics (e.g., minimum password length, validation time window for time synchronous one-time tokens, and number of allowed rejections during the verification stage of biometric authentication). Actions can be taken to safeguard individual authenticators, including maintaining possession of authenticators, not sharing authenticators with others, and immediately reporting lost, stolen, or compromised authenticators. Authenticator management includes issuing and revoking authenticators for temporary access when no longer needed." - }, - { - "id": "ia-5_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "IA-5 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ia-5_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Authenticators must be compliant with NIST SP 800-63-3 Digital Identity Guidelines IAL, AAL, FAL level 3. Link https://pages.nist.gov/800-63-3" - }, - { - "id": "ia-5_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "SP 800-63C Section 6.2.3 Encrypted Assertion requires that authentication assertions be encrypted when passed through third parties, such as a browser. For example, a SAML assertion can be encrypted using XML-Encryption, or an OpenID Connect ID Token can be encrypted using JSON Web Encryption (JWE)." - } - ] - }, - { - "id": "ia-5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-05", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-5_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05a.", - "class": "sp800-53a" - } - ], - "prose": "system authenticators are managed through the verification of the identity of the individual, group, role, service, or device receiving the authenticator as part of the initial authenticator distribution;", - "links": [ - { - "href": "#ia-5_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05b.", - "class": "sp800-53a" - } - ], - "prose": "system authenticators are managed through the establishment of initial authenticator content for any authenticators issued by the organization;", - "links": [ - { - "href": "#ia-5_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05c.", - "class": "sp800-53a" - } - ], - "prose": "system authenticators are managed to ensure that authenticators have sufficient strength of mechanism for their intended use;", - "links": [ - { - "href": "#ia-5_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05d.", - "class": "sp800-53a" - } - ], - "prose": "system authenticators are managed through the establishment and implementation of administrative procedures for initial authenticator distribution; lost, compromised, or damaged authenticators; and the revocation of authenticators;", - "links": [ - { - "href": "#ia-5_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05e.", - "class": "sp800-53a" - } - ], - "prose": "system authenticators are managed through the change of default authenticators prior to first use;", - "links": [ - { - "href": "#ia-5_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5_obj.f", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05f.", - "class": "sp800-53a" - } - ], - "prose": "system authenticators are managed through the change or refreshment of authenticators {{ insert: param, ia-05_odp.01 }} or when {{ insert: param, ia-05_odp.02 }} occur;", - "links": [ - { - "href": "#ia-5_smt.f", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5_obj.g", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05g.", - "class": "sp800-53a" - } - ], - "prose": "system authenticators are managed through the protection of authenticator content from unauthorized disclosure and modification;", - "links": [ - { - "href": "#ia-5_smt.g", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5_obj.h", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-05h.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-5_obj.h-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05h.[01]", - "class": "sp800-53a" - } - ], - "prose": "system authenticators are managed through the requirement for individuals to take specific controls to protect authenticators;", - "links": [ - { - "href": "#ia-5_smt.h", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5_obj.h-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05h.[02]", - "class": "sp800-53a" - } - ], - "prose": "system authenticators are managed through the requirement for devices to implement specific controls to protect authenticators;", - "links": [ - { - "href": "#ia-5_smt.h", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-5_smt.h", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5_obj.i", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05i.", - "class": "sp800-53a" - } - ], - "prose": "system authenticators are managed through the change of authenticators for group or role accounts when membership to those accounts changes.", - "links": [ - { - "href": "#ia-5_smt.i", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-05-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nsystem security plan\n\naddressing authenticator management\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of system authenticator types\n\nchange control records associated with managing system authenticators\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-05-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with authenticator management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "ia-5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-05-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing authenticator management capability" - } - ] - } - ], - "controls": [ - { - "id": "ia-5.1", - "class": "SP800-53-enhancement", - "title": "Password-based Authentication", - "params": [ - { - "id": "ia-05.01_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ia-5.1_prm_1" - }, - { - "name": "label", - "value": "IA-05(01)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "guidelines": [ - { - "prose": "the frequency at which to update the list of commonly used, expected, or compromised passwords is defined;" - } - ] - }, - { - "id": "ia-05.01_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ia-5.1_prm_2" - }, - { - "name": "label", - "value": "IA-05(01)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "composition and complexity rules", - "guidelines": [ - { - "prose": "authenticator composition and complexity rules are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IA-05(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-5(1)" - }, - { - "name": "label", - "value": "IA-05(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-05.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ia-5", - "rel": "required" - }, - { - "href": "#ia-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "ia-5.1_smt", - "name": "statement", - "prose": "For password-based authentication:", - "parts": [ - { - "id": "ia-5.1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Maintain a list of commonly-used, expected, or compromised passwords and update the list {{ insert: param, ia-05.01_odp.01 }} and when organizational passwords are suspected to have been compromised directly or indirectly;" - }, - { - "id": "ia-5.1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Verify, when users create or update passwords, that the passwords are not found on the list of commonly-used, expected, or compromised passwords in IA-5(1)(a);" - }, - { - "id": "ia-5.1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Transmit passwords only over cryptographically-protected channels;" - }, - { - "id": "ia-5.1_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(d)" - } - ], - "prose": "Store passwords using an approved salted key derivation function, preferably using a keyed hash;" - }, - { - "id": "ia-5.1_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(e)" - } - ], - "prose": "Require immediate selection of a new password upon account recovery;" - }, - { - "id": "ia-5.1_smt.f", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(f)" - } - ], - "prose": "Allow user selection of long passwords and passphrases, including spaces and all printable characters;" - }, - { - "id": "ia-5.1_smt.g", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(g)" - } - ], - "prose": "Employ automated tools to assist the user in selecting strong password authenticators; and" - }, - { - "id": "ia-5.1_smt.h", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(h)" - } - ], - "prose": "Enforce the following composition and complexity rules: {{ insert: param, ia-05.01_odp.02 }}." - } - ] - }, - { - "id": "ia-5.1_gdn", - "name": "guidance", - "prose": "Password-based authentication applies to passwords regardless of whether they are used in single-factor or multi-factor authentication. Long passwords or passphrases are preferable over shorter passwords. Enforced composition rules provide marginal security benefits while decreasing usability. However, organizations may choose to establish certain rules for password generation (e.g., minimum character length for long passwords) under certain circumstances and can enforce this requirement in IA-5(1)(h). Account recovery can occur, for example, in situations when a password is forgotten. Cryptographically protected passwords include salted one-way cryptographic hashes of passwords. The list of commonly used, compromised, or expected passwords includes passwords obtained from previous breach corpuses, dictionary words, and repetitive or sequential characters. The list includes context-specific words, such as the name of the service, username, and derivatives thereof." - }, - { - "id": "ia-5.1_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "IA-5 (1) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ia-5.1_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Password policies must be compliant with NIST SP 800-63B for all memorized, lookup, out-of-band, or One-Time-Passwords (OTP). Password policies shall not enforce special character or minimum password rotation requirements for memorized secrets of users." - }, - { - "id": "ia-5.1_fr_smt.2", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(h) Requirement:" - } - ], - "prose": "For cases where technology doesn't allow multi-factor authentication, these rules should be enforced: must have a minimum length of 14 characters and must support all printable ASCII characters.\n\nFor emergency use accounts, these rules should be enforced: must have a minimum length of 14 characters, must support all printable ASCII characters, and passwords must be changed if used." - }, - { - "id": "ia-5.1_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Note that (c) and (d) require the use of cryptography which must be compliant with Federal requirements and utilize FIPS validated or NSA approved cryptography (see SC-13)." - } - ] - }, - { - "id": "ia-5.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-05(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-5.1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05(01)(a)", - "class": "sp800-53a" - } - ], - "prose": "for password-based authentication, a list of commonly used, expected, or compromised passwords is maintained and updated {{ insert: param, ia-05.01_odp.01 }} and when organizational passwords are suspected to have been compromised directly or indirectly;", - "links": [ - { - "href": "#ia-5.1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5.1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05(01)(b)", - "class": "sp800-53a" - } - ], - "prose": "for password-based authentication when passwords are created or updated by users, the passwords are verified not to be found on the list of commonly used, expected, or compromised passwords in IA-05(01)(a);", - "links": [ - { - "href": "#ia-5.1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5.1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05(01)(c)", - "class": "sp800-53a" - } - ], - "prose": "for password-based authentication, passwords are only transmitted over cryptographically protected channels;", - "links": [ - { - "href": "#ia-5.1_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5.1_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05(01)(d)", - "class": "sp800-53a" - } - ], - "prose": "for password-based authentication, passwords are stored using an approved salted key derivation function, preferably using a keyed hash;", - "links": [ - { - "href": "#ia-5.1_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5.1_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05(01)(e)", - "class": "sp800-53a" - } - ], - "prose": "for password-based authentication, immediate selection of a new password is required upon account recovery;", - "links": [ - { - "href": "#ia-5.1_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5.1_obj.f", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05(01)(f)", - "class": "sp800-53a" - } - ], - "prose": "for password-based authentication, user selection of long passwords and passphrases is allowed, including spaces and all printable characters;", - "links": [ - { - "href": "#ia-5.1_smt.f", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5.1_obj.g", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05(01)(g)", - "class": "sp800-53a" - } - ], - "prose": "for password-based authentication, automated tools are employed to assist the user in selecting strong password authenticators;", - "links": [ - { - "href": "#ia-5.1_smt.g", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5.1_obj.h", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05(01)(h)", - "class": "sp800-53a" - } - ], - "prose": "for password-based authentication, {{ insert: param, ia-05.01_odp.02 }} are enforced.", - "links": [ - { - "href": "#ia-5.1_smt.h", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-5.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-05(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\npassword policy\n\nprocedures addressing authenticator management\n\nsystem security plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\npassword configurations and associated documentation\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-5.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-05(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with authenticator management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "ia-5.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-05(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing password-based authenticator management capability" - } - ] - } - ] - }, - { - "id": "ia-5.2", - "class": "SP800-53-enhancement", - "title": "Public Key-based Authentication", - "props": [ - { - "name": "label", - "value": "IA-05(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-5(2)" - }, - { - "name": "label", - "value": "IA-05(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-05.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ia-5", - "rel": "required" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#sc-17", - "rel": "related" - } - ], - "parts": [ - { - "id": "ia-5.2_smt", - "name": "statement", - "parts": [ - { - "id": "ia-5.2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "For public key-based authentication:", - "parts": [ - { - "id": "ia-5.2_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "(1)" - } - ], - "prose": "Enforce authorized access to the corresponding private key; and" - }, - { - "id": "ia-5.2_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "(2)" - } - ], - "prose": "Map the authenticated identity to the account of the individual or group; and" - } - ] - }, - { - "id": "ia-5.2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "When public key infrastructure (PKI) is used:", - "parts": [ - { - "id": "ia-5.2_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "(1)" - } - ], - "prose": "Validate certificates by constructing and verifying a certification path to an accepted trust anchor, including checking certificate status information; and" - }, - { - "id": "ia-5.2_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "(2)" - } - ], - "prose": "Implement a local cache of revocation data to support path discovery and validation." - } - ] - } - ] - }, - { - "id": "ia-5.2_gdn", - "name": "guidance", - "prose": "Public key cryptography is a valid authentication mechanism for individuals, machines, and devices. For PKI solutions, status information for certification paths includes certificate revocation lists or certificate status protocol responses. For PIV cards, certificate validation involves the construction and verification of a certification path to the Common Policy Root trust anchor, which includes certificate policy processing. Implementing a local cache of revocation data to support path discovery and validation also supports system availability in situations where organizations are unable to access revocation information via the network." - }, - { - "id": "ia-5.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-05(02)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-5.2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-05(02)(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-5.2_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05(02)(a)(01)", - "class": "sp800-53a" - } - ], - "prose": "authorized access to the corresponding private key is enforced for public key-based authentication;", - "links": [ - { - "href": "#ia-5.2_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5.2_obj.a.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05(02)(a)(02)", - "class": "sp800-53a" - } - ], - "prose": "the authenticated identity is mapped to the account of the individual or group for public key-based authentication;", - "links": [ - { - "href": "#ia-5.2_smt.a.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-5.2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5.2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-05(02)(b)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-5.2_obj.b.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05(02)(b)(01)", - "class": "sp800-53a" - } - ], - "prose": "when public key infrastructure (PKI) is used, certificates are validated by constructing and verifying a certification path to an accepted trust anchor, including checking certificate status information;", - "links": [ - { - "href": "#ia-5.2_smt.b.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5.2_obj.b.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05(02)(b)(02)", - "class": "sp800-53a" - } - ], - "prose": "when public key infrastructure (PKI) is used, a local cache of revocation data is implemented to support path discovery and validation.", - "links": [ - { - "href": "#ia-5.2_smt.b.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-5.2_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-5.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-05(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nprocedures addressing authenticator management\n\nsystem security plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nPKI certification validation records\n\nPKI certification revocation lists\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-5.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-05(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with PKI-based, authenticator management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "ia-5.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-05(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing PKI-based, authenticator management capability" - } - ] - } - ] - }, - { - "id": "ia-5.6", - "class": "SP800-53-enhancement", - "title": "Protection of Authenticators", - "props": [ - { - "name": "label", - "value": "IA-05(06)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-5(6)" - }, - { - "name": "label", - "value": "IA-05(06)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-05.06" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ia-5", - "rel": "required" - }, - { - "href": "#ra-2", - "rel": "related" - } - ], - "parts": [ - { - "id": "ia-5.6_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Protect authenticators commensurate with the security category of the information to which use of the authenticator permits access." - }, - { - "id": "ia-5.6_gdn", - "name": "guidance", - "prose": "For systems that contain multiple security categories of information without reliable physical or logical separation between categories, authenticators used to grant access to the systems are protected commensurate with the highest security category of information on the systems. Security categories of information are determined as part of the security categorization process." - }, - { - "id": "ia-5.6_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05(06)", - "class": "sp800-53a" - } - ], - "prose": "authenticators are protected commensurate with the security category of the information to which use of the authenticator permits access.", - "links": [ - { - "href": "#ia-5.6_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5.6_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-05(06)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nprocedures addressing authenticator management\n\nsecurity categorization documentation for the system\n\nsecurity assessments of authenticator protections\n\nrisk assessment results\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-5.6_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-05(06)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with authenticator management responsibilities\n\norganizational personnel implementing and/or maintaining authenticator protections\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "ia-5.6_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-05(06)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing authenticator management capability\n\nmechanisms protecting authenticators" - } - ] - } - ] - }, - { - "id": "ia-5.7", - "class": "SP800-53-enhancement", - "title": "No Embedded Unencrypted Static Authenticators", - "props": [ - { - "name": "label", - "value": "IA-05(07)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-5(7)" - }, - { - "name": "label", - "value": "IA-05(07)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-05.07" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ia-5", - "rel": "required" - } - ], - "parts": [ - { - "id": "ia-5.7_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Ensure that unencrypted static authenticators are not embedded in applications or other forms of static storage." - }, - { - "id": "ia-5.7_gdn", - "name": "guidance", - "prose": "In addition to applications, other forms of static storage include access scripts and function keys. Organizations exercise caution when determining whether embedded or stored authenticators are in encrypted or unencrypted form. If authenticators are used in the manner stored, then those representations are considered unencrypted authenticators." - }, - { - "id": "ia-5.7_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "IA-5 (7) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ia-5.7_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "In this context, prohibited static storage refers to any storage where unencrypted authenticators, such as passwords, persist beyond the time required to complete the access process." - } - ] - }, - { - "id": "ia-5.7_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05(07)", - "class": "sp800-53a" - } - ], - "prose": "unencrypted static authenticators are not embedded in applications or other forms of static storage.", - "links": [ - { - "href": "#ia-5.7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5.7_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-05(07)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nsystem security plan\n\nprocedures addressing authenticator management\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlogical access scripts\n\napplication code reviews for detecting unencrypted static authenticators\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-5.7_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-05(07)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with authenticator management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "ia-5.7_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-05(07)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing authenticator management capability\n\nmechanisms implementing authentication in applications" - } - ] - } - ] - }, - { - "id": "ia-5.8", - "class": "SP800-53-enhancement", - "title": "Multiple System Accounts", - "params": [ - { - "id": "ia-05.08_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ia-5.8_prm_1" - }, - { - "name": "label", - "value": "IA-05(08)_ODP", - "class": "sp800-53a" - } - ], - "label": "security controls", - "constraints": [ - { - "description": "different authenticators in different user authentication domains" - } - ], - "guidelines": [ - { - "prose": "security controls implemented to manage the risk of compromise due to individuals having accounts on multiple systems are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IA-05(08)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-5(8)" - }, - { - "name": "label", - "value": "IA-05(08)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-05.08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ia-5", - "rel": "required" - }, - { - "href": "#ps-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "ia-5.8_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement {{ insert: param, ia-05.08_odp }} to manage the risk of compromise due to individuals having accounts on multiple systems." - }, - { - "id": "ia-5.8_gdn", - "name": "guidance", - "prose": "When individuals have accounts on multiple systems and use the same authenticators such as passwords, there is the risk that a compromise of one account may lead to the compromise of other accounts. Alternative approaches include having different authenticators (passwords) on all systems, employing a single sign-on or federation mechanism, or using some form of one-time passwords on all systems. Organizations can also use rules of behavior (see [PL-4](#pl-4) ) and access agreements (see [PS-6](#ps-6) ) to mitigate the risk of multiple system accounts." - }, - { - "id": "ia-5.8_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "IA-5 (8) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ia-5.8_fr_gdn.x", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "If a single user authentication domain is used to access multiple systems, such as in single-sign-on, then only a single authenticator is required." - } - ] - }, - { - "id": "ia-5.8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05(08)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ia-05.08_odp }} are implemented to manage the risk of compromise due to individuals having accounts on multiple systems.", - "links": [ - { - "href": "#ia-5.8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5.8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-05(08)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nprocedures addressing authenticator management\n\nsystem security plan\n\nlist of individuals having accounts on multiple systems\n\nlist of security safeguards intended to manage risk of compromise due to individuals having accounts on multiple systems\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-5.8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-05(08)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with authenticator management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "ia-5.8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-05(08)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing safeguards for authenticator management" - } - ] - } - ] - }, - { - "id": "ia-5.13", - "class": "SP800-53-enhancement", - "title": "Expiration of Cached Authenticators", - "params": [ - { - "id": "ia-05.13_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ia-5.13_prm_1" - }, - { - "name": "label", - "value": "IA-05(13)_ODP", - "class": "sp800-53a" - } - ], - "label": "time period", - "guidelines": [ - { - "prose": "the time period after which the use of cached authenticators is prohibited is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IA-05(13)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-5(13)" - }, - { - "name": "label", - "value": "IA-05(13)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-05.13" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ia-5", - "rel": "required" - } - ], - "parts": [ - { - "id": "ia-5.13_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Prohibit the use of cached authenticators after {{ insert: param, ia-05.13_odp }}." - }, - { - "id": "ia-5.13_gdn", - "name": "guidance", - "prose": "Cached authenticators are used to authenticate to the local machine when the network is not available. If cached authentication information is out of date, the validity of the authentication information may be questionable." - }, - { - "id": "ia-5.13_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "IA-5 (13) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ia-5.13_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "For components subject to configuration baseline(s) (such as STIG or CIS,) the time period should conform to the baseline standard." - } - ] - }, - { - "id": "ia-5.13_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-05(13)", - "class": "sp800-53a" - } - ], - "prose": "the use of cached authenticators is prohibited after {{ insert: param, ia-05.13_odp }}.", - "links": [ - { - "href": "#ia-5.13_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-5.13_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-05(13)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nprocedures addressing authenticator management\n\nsystem security plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-5.13_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-05(13)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with authenticator management responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "ia-5.13_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-05(13)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing authenticator management capability" - } - ] - } - ] - } - ] - }, - { - "id": "ia-6", - "class": "SP800-53", - "title": "Authentication Feedback", - "props": [ - { - "name": "label", - "value": "IA-06", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-6" - }, - { - "name": "label", - "value": "IA-06", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-06" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "ia-6_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Obscure feedback of authentication information during the authentication process to protect the information from possible exploitation and use by unauthorized individuals." - }, - { - "id": "ia-6_gdn", - "name": "guidance", - "prose": "Authentication feedback from systems does not provide information that would allow unauthorized individuals to compromise authentication mechanisms. For some types of systems, such as desktops or notebooks with relatively large monitors, the threat (referred to as shoulder surfing) may be significant. For other types of systems, such as mobile devices with small displays, the threat may be less significant and is balanced against the increased likelihood of typographic input errors due to small keyboards. Thus, the means for obscuring authentication feedback is selected accordingly. Obscuring authentication feedback includes displaying asterisks when users type passwords into input devices or displaying feedback for a very limited time before obscuring it." - }, - { - "id": "ia-6_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-06", - "class": "sp800-53a" - } - ], - "prose": "the feedback of authentication information is obscured during the authentication process to protect the information from possible exploitation and use by unauthorized individuals.", - "links": [ - { - "href": "#ia-6_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-6_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-06-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nsystem security plan\n\nprocedures addressing authenticator feedback\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-6_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-06-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "ia-6_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-06-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing the obscuring of feedback of authentication information during authentication" - } - ] - } - ] - }, - { - "id": "ia-7", - "class": "SP800-53", - "title": "Cryptographic Module Authentication", - "props": [ - { - "name": "label", - "value": "IA-07", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-7" - }, - { - "name": "label", - "value": "IA-07", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-07" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#678e3d6c-150b-4393-aec5-6e3481eb1e00", - "rel": "reference" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ], - "parts": [ - { - "id": "ia-7_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement mechanisms for authentication to a cryptographic module that meet the requirements of applicable laws, executive orders, directives, policies, regulations, standards, and guidelines for such authentication." - }, - { - "id": "ia-7_gdn", - "name": "guidance", - "prose": "Authentication mechanisms may be required within a cryptographic module to authenticate an operator accessing the module and to verify that the operator is authorized to assume the requested role and perform services within that role." - }, - { - "id": "ia-7_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-07", - "class": "sp800-53a" - } - ], - "prose": "mechanisms for authentication to a cryptographic module are implemented that meet the requirements of applicable laws, executive orders, directives, policies, regulations, standards, and guidelines for such authentication.", - "links": [ - { - "href": "#ia-7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-7_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-07-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nsystem security plan\n\nprocedures addressing cryptographic module authentication\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-7_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-07-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibility for cryptographic module authentication\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers" - } - ] - }, - { - "id": "ia-7_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-07-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing cryptographic module authentication" - } - ] - } - ] - }, - { - "id": "ia-8", - "class": "SP800-53", - "title": "Identification and Authentication (Non-organizational Users)", - "props": [ - { - "name": "label", - "value": "IA-08", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-8" - }, - { - "name": "label", - "value": "IA-08", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#a1555677-2b9d-4868-a97b-a1363aff32f5", - "rel": "reference" - }, - { - "href": "#7ba1d91c-3934-4d5a-8532-b32f864ad34c", - "rel": "reference" - }, - { - "href": "#737513fa-6758-403f-831d-5ddab5e23cb3", - "rel": "reference" - }, - { - "href": "#10963761-58fc-4b20-b3d6-b44a54daba03", - "rel": "reference" - }, - { - "href": "#2100332a-16a5-4598-bacf-7261baea9711", - "rel": "reference" - }, - { - "href": "#98d415ca-7281-4064-9931-0c366637e324", - "rel": "reference" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ac-14", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ia-10", - "rel": "related" - }, - { - "href": "#ia-11", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ia-13", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - } - ], - "parts": [ - { - "id": "ia-8_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Uniquely identify and authenticate non-organizational users or processes acting on behalf of non-organizational users." - }, - { - "id": "ia-8_gdn", - "name": "guidance", - "prose": "Non-organizational users include system users other than organizational users explicitly covered by [IA-2](#ia-2) . Non-organizational users are uniquely identified and authenticated for accesses other than those explicitly identified and documented in [AC-14](#ac-14) . Identification and authentication of non-organizational users accessing federal systems may be required to protect federal, proprietary, or privacy-related information (with exceptions noted for national security systems). Organizations consider many factors—including security, privacy, scalability, and practicality—when balancing the need to ensure ease of use for access to federal information and systems with the need to protect and adequately mitigate risk." - }, - { - "id": "ia-8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-08", - "class": "sp800-53a" - } - ], - "prose": "non-organizational users or processes acting on behalf of non-organizational users are uniquely identified and authenticated.", - "links": [ - { - "href": "#ia-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-08-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nsystem security plan\n\nprivacy plan\n\nprocedures addressing user identification and authentication\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nlist of system accounts\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-08-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system operations responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\norganizational personnel with account management responsibilities" - } - ] - }, - { - "id": "ia-8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-08-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing identification and authentication capabilities" - } - ] - } - ], - "controls": [ - { - "id": "ia-8.1", - "class": "SP800-53-enhancement", - "title": "Acceptance of PIV Credentials from Other Agencies", - "props": [ - { - "name": "label", - "value": "IA-08(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-8(1)" - }, - { - "name": "label", - "value": "IA-08(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-08.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ia-8", - "rel": "required" - }, - { - "href": "#pe-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "ia-8.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Accept and electronically verify Personal Identity Verification-compliant credentials from other federal agencies." - }, - { - "id": "ia-8.1_gdn", - "name": "guidance", - "prose": "Acceptance of Personal Identity Verification (PIV) credentials from other federal agencies applies to both logical and physical access control systems. PIV credentials are those credentials issued by federal agencies that conform to FIPS Publication 201 and supporting guidelines. The adequacy and reliability of PIV card issuers are addressed and authorized using [SP 800-79-2](#10963761-58fc-4b20-b3d6-b44a54daba03)." - }, - { - "id": "ia-8.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-08(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-8.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-08(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "Personal Identity Verification-compliant credentials from other federal agencies are accepted;", - "links": [ - { - "href": "#ia-8.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-8.1_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-08(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "Personal Identity Verification-compliant credentials from other federal agencies are electronically verified.", - "links": [ - { - "href": "#ia-8.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-8.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-8.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-08(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nsystem security plan\n\nprocedures addressing user identification and authentication\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nPIV verification records\n\nevidence of PIV credentials\n\nPIV credential authorizations\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-8.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-08(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system operations responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers\n\norganizational personnel with account management responsibilities" - } - ] - }, - { - "id": "ia-8.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-08(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing identification and authentication capabilities\n\nmechanisms that accept and verify PIV credentials" - } - ] - } - ] - }, - { - "id": "ia-8.2", - "class": "SP800-53-enhancement", - "title": "Acceptance of External Authenticators", - "props": [ - { - "name": "label", - "value": "IA-08(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-8(2)" - }, - { - "name": "label", - "value": "IA-08(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-08.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ia-8", - "rel": "required" - } - ], - "parts": [ - { - "id": "ia-8.2_smt", - "name": "statement", - "parts": [ - { - "id": "ia-8.2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Accept only external authenticators that are NIST-compliant; and" - }, - { - "id": "ia-8.2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Document and maintain a list of accepted external authenticators." - } - ] - }, - { - "id": "ia-8.2_gdn", - "name": "guidance", - "prose": "Acceptance of only NIST-compliant external authenticators applies to organizational systems that are accessible to the public (e.g., public-facing websites). External authenticators are issued by nonfederal government entities and are compliant with [SP 800-63B](#e59c5a7c-8b1f-49ca-8de0-6ee0882180ce) . Approved external authenticators meet or exceed the minimum Federal Government-wide technical, security, privacy, and organizational maturity requirements. Meeting or exceeding Federal requirements allows Federal Government relying parties to trust external authenticators in connection with an authentication transaction at a specified authenticator assurance level." - }, - { - "id": "ia-8.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-08(02)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-8.2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-08(02)(a)", - "class": "sp800-53a" - } - ], - "prose": "only external authenticators that are NIST-compliant are accepted;", - "links": [ - { - "href": "#ia-8.2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-8.2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-08(02)(b)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-8.2_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-08(02)(b)[01]", - "class": "sp800-53a" - } - ], - "prose": "a list of accepted external authenticators is documented;", - "links": [ - { - "href": "#ia-8.2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-8.2_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-08(02)(b)[02]", - "class": "sp800-53a" - } - ], - "prose": "a list of accepted external authenticators is maintained.", - "links": [ - { - "href": "#ia-8.2_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-8.2_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-8.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-8.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-08(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nsystem security plan\n\nprocedures addressing user identification and authentication\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nlist of third-party credentialing products, components, or services procured and implemented by organization\n\nthird-party credential verification records\n\nevidence of third-party credentials\n\nthird-party credential authorizations\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-8.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-08(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system operations responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers\n\norganizational personnel with account management responsibilities" - } - ] - }, - { - "id": "ia-8.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-08(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing identification and authentication capabilities\n\nmechanisms that accept external credentials" - } - ] - } - ] - }, - { - "id": "ia-8.4", - "class": "SP800-53-enhancement", - "title": "Use of Defined Profiles", - "params": [ - { - "id": "ia-08.04_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ia-8.4_prm_1" - }, - { - "name": "label", - "value": "IA-08(04)_ODP", - "class": "sp800-53a" - } - ], - "label": "identity management profiles", - "guidelines": [ - { - "prose": "identity management profiles are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IA-08(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-8(4)" - }, - { - "name": "label", - "value": "IA-08(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-08.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ia-8", - "rel": "required" - } - ], - "parts": [ - { - "id": "ia-8.4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Conform to the following profiles for identity management {{ insert: param, ia-08.04_odp }}." - }, - { - "id": "ia-8.4_gdn", - "name": "guidance", - "prose": "Organizations define profiles for identity management based on open identity management standards. To ensure that open identity management standards are viable, robust, reliable, sustainable, and interoperable as documented, the Federal Government assesses and scopes the standards and technology implementations against applicable laws, executive orders, directives, policies, regulations, standards, and guidelines." - }, - { - "id": "ia-8.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-08(04)", - "class": "sp800-53a" - } - ], - "prose": "there is conformance with {{ insert: param, ia-08.04_odp }} for identity management.", - "links": [ - { - "href": "#ia-8.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-8.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-08(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nsystem security plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-8.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-08(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system operations responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers\n\norganizational personnel with account management responsibilities" - } - ] - }, - { - "id": "ia-8.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-08(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing identification and authentication capabilities\n\nmechanisms supporting and/or implementing conformance with profiles" - } - ] - } - ] - } - ] - }, - { - "id": "ia-11", - "class": "SP800-53", - "title": "Re-authentication", - "params": [ - { - "id": "ia-11_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ia-11_prm_1" - }, - { - "name": "alt-label", - "value": "circumstances or situations requiring re-authentication", - "class": "sp800-53" - }, - { - "name": "label", - "value": "IA-11_ODP", - "class": "sp800-53a" - } - ], - "label": "circumstances or situations", - "guidelines": [ - { - "prose": "circumstances or situations requiring re-authentication are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IA-11", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-11" - }, - { - "name": "label", - "value": "IA-11", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-11" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-11", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - } - ], - "parts": [ - { - "id": "ia-11_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Require users to re-authenticate when {{ insert: param, ia-11_odp }}." - }, - { - "id": "ia-11_gdn", - "name": "guidance", - "prose": "In addition to the re-authentication requirements associated with device locks, organizations may require re-authentication of individuals in certain situations, including when roles, authenticators or credentials change, when security categories of systems change, when the execution of privileged functions occurs, after a fixed time period, or periodically." - }, - { - "id": "ia-11_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "IA-11 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ia-11_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "The fixed time period cannot exceed the limits set in SP 800-63. At this writing they are:\n\n- AAL3 (high baseline)\n - 12 hours or\n - 15 minutes of inactivity" - } - ] - }, - { - "id": "ia-11_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-11", - "class": "sp800-53a" - } - ], - "prose": "users are required to re-authenticate when {{ insert: param, ia-11_odp }}.", - "links": [ - { - "href": "#ia-11_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-11_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-11-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nprocedures addressing user and device re-authentication\n\nsystem security plan\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of circumstances or situations requiring re-authentication\n\nsystem audit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-11_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-11-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system operations responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers\n\norganizational personnel with identification and authentication responsibilities" - } - ] - }, - { - "id": "ia-11_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-11-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing identification and authentication capabilities" - } - ] - } - ] - }, - { - "id": "ia-12", - "class": "SP800-53", - "title": "Identity Proofing", - "props": [ - { - "name": "label", - "value": "IA-12", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-12" - }, - { - "name": "label", - "value": "IA-12", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-12" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#7ba1d91c-3934-4d5a-8532-b32f864ad34c", - "rel": "reference" - }, - { - "href": "#737513fa-6758-403f-831d-5ddab5e23cb3", - "rel": "reference" - }, - { - "href": "#9099ed2c-922a-493d-bcb4-d896192243ff", - "rel": "reference" - }, - { - "href": "#10963761-58fc-4b20-b3d6-b44a54daba03", - "rel": "reference" - }, - { - "href": "#ac-5", - "rel": "related" - }, - { - "href": "#ia-1", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#ia-6", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ia-13", - "rel": "related" - } - ], - "parts": [ - { - "id": "ia-12_smt", - "name": "statement", - "parts": [ - { - "id": "ia-12_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Identity proof users that require accounts for logical access to systems based on appropriate identity assurance level requirements as specified in applicable standards and guidelines;" - }, - { - "id": "ia-12_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Resolve user identities to a unique individual; and" - }, - { - "id": "ia-12_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Collect, validate, and verify identity evidence." - } - ] - }, - { - "id": "ia-12_gdn", - "name": "guidance", - "prose": "Identity proofing is the process of collecting, validating, and verifying a user’s identity information for the purposes of establishing credentials for accessing a system. Identity proofing is intended to mitigate threats to the registration of users and the establishment of their accounts. Standards and guidelines specifying identity assurance levels for identity proofing include [SP 800-63-3](#737513fa-6758-403f-831d-5ddab5e23cb3) and [SP 800-63A](#9099ed2c-922a-493d-bcb4-d896192243ff) . Organizations may be subject to laws, executive orders, directives, regulations, or policies that address the collection of identity evidence. Organizational personnel consult with the senior agency official for privacy and legal counsel regarding such requirements." - }, - { - "id": "ia-12_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "IA-12 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ia-12_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "In accordance with NIST SP 800-63A Enrollment and Identity Proofing" - } - ] - }, - { - "id": "ia-12_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-12", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-12_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-12a.", - "class": "sp800-53a" - } - ], - "prose": "users who require accounts for logical access to systems based on appropriate identity assurance level requirements as specified in applicable standards and guidelines are identity proofed;", - "links": [ - { - "href": "#ia-12_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-12_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-12b.", - "class": "sp800-53a" - } - ], - "prose": "user identities are resolved to a unique individual;", - "links": [ - { - "href": "#ia-12_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-12_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-12c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ia-12_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-12c.[01]", - "class": "sp800-53a" - } - ], - "prose": "identity evidence is collected;", - "links": [ - { - "href": "#ia-12_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-12_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-12c.[02]", - "class": "sp800-53a" - } - ], - "prose": "identity evidence is validated;", - "links": [ - { - "href": "#ia-12_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-12_obj.c-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IA-12c.[03]", - "class": "sp800-53a" - } - ], - "prose": "identity evidence is verified.", - "links": [ - { - "href": "#ia-12_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-12_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ia-12_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-12_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-12-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nprocedures addressing identity proofing\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-12_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-12-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system operations responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nlegal counsel\n\nsystem/network administrators\n\nsystem developers\n\norganizational personnel with identification and authentication responsibilities" - } - ] - }, - { - "id": "ia-12_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-12-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing identification and authentication capabilities" - } - ] - } - ], - "controls": [ - { - "id": "ia-12.2", - "class": "SP800-53-enhancement", - "title": "Identity Evidence", - "props": [ - { - "name": "label", - "value": "IA-12(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-12(2)" - }, - { - "name": "label", - "value": "IA-12(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-12.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ia-12", - "rel": "required" - } - ], - "parts": [ - { - "id": "ia-12.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Require evidence of individual identification be presented to the registration authority." - }, - { - "id": "ia-12.2_gdn", - "name": "guidance", - "prose": "Identity evidence, such as documentary evidence or a combination of documents and biometrics, reduces the likelihood of individuals using fraudulent identification to establish an identity or at least increases the work factor of potential adversaries. The forms of acceptable evidence are consistent with the risks to the systems, roles, and privileges associated with the user’s account." - }, - { - "id": "ia-12.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-12(02)", - "class": "sp800-53a" - } - ], - "prose": "evidence of individual identification is presented to the registration authority.", - "links": [ - { - "href": "#ia-12.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-12.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-12(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nprocedures addressing identity proofing\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-12.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-12(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system operations responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers\n\norganizational personnel with identification and authentication responsibilities" - } - ] - }, - { - "id": "ia-12.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-12(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing identification and authentication capabilities" - } - ] - } - ] - }, - { - "id": "ia-12.3", - "class": "SP800-53-enhancement", - "title": "Identity Evidence Validation and Verification", - "params": [ - { - "id": "ia-12.03_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ia-12.3_prm_1" - }, - { - "name": "alt-label", - "value": "organizational defined methods of validation and verification", - "class": "sp800-53" - }, - { - "name": "label", - "value": "IA-12(03)_ODP", - "class": "sp800-53a" - } - ], - "label": "methods of validation and verification", - "guidelines": [ - { - "prose": "methods of validation and verification of identity evidence are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IA-12(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-12(3)" - }, - { - "name": "label", - "value": "IA-12(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-12.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ia-12", - "rel": "required" - } - ], - "parts": [ - { - "id": "ia-12.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Require that the presented identity evidence be validated and verified through {{ insert: param, ia-12.03_odp }}." - }, - { - "id": "ia-12.3_gdn", - "name": "guidance", - "prose": "Validation and verification of identity evidence increases the assurance that accounts and identifiers are being established for the correct user and authenticators are being bound to that user. Validation refers to the process of confirming that the evidence is genuine and authentic, and the data contained in the evidence is correct, current, and related to an individual. Verification confirms and establishes a linkage between the claimed identity and the actual existence of the user presenting the evidence. Acceptable methods for validating and verifying identity evidence are consistent with the risks to the systems, roles, and privileges associated with the users account." - }, - { - "id": "ia-12.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-12(03)", - "class": "sp800-53a" - } - ], - "prose": "the presented identity evidence is validated and verified through {{ insert: param, ia-12.03_odp }}.", - "links": [ - { - "href": "#ia-12.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-12.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-12(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nprocedures addressing identity proofing\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-12.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-12(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system operations responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers\n\norganizational personnel with identification and authentication responsibilities" - } - ] - }, - { - "id": "ia-12.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-12(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing identification and authentication capabilities" - } - ] - } - ] - }, - { - "id": "ia-12.4", - "class": "SP800-53-enhancement", - "title": "In-person Validation and Verification", - "props": [ - { - "name": "label", - "value": "IA-12(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-12(4)" - }, - { - "name": "label", - "value": "IA-12(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-12.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ia-12", - "rel": "required" - } - ], - "parts": [ - { - "id": "ia-12.4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Require that the validation and verification of identity evidence be conducted in person before a designated registration authority." - }, - { - "id": "ia-12.4_gdn", - "name": "guidance", - "prose": "In-person proofing reduces the likelihood of fraudulent credentials being issued because it requires the physical presence of individuals, the presentation of physical identity documents, and actual face-to-face interactions with designated registration authorities." - }, - { - "id": "ia-12.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-12(04)", - "class": "sp800-53a" - } - ], - "prose": "the validation and verification of identity evidence is conducted in person before a designated registration authority.", - "links": [ - { - "href": "#ia-12.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-12.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-12(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nprocedures addressing identity proofing\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-12.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-12(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system operations responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers\n\norganizational personnel with identification and authentication responsibilities" - } - ] - }, - { - "id": "ia-12.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-12(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing identification and authentication capabilities" - } - ] - } - ] - }, - { - "id": "ia-12.5", - "class": "SP800-53-enhancement", - "title": "Address Confirmation", - "params": [ - { - "id": "ia-12.05_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ia-12.5_prm_1" - }, - { - "name": "label", - "value": "IA-12(05)_ODP", - "class": "sp800-53a" - } - ], - "select": { - "choice": [ - "registration code", - "notice of proofing" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "IA-12(05)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IA-12(5)" - }, - { - "name": "label", - "value": "IA-12(05)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ia-12.05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ia-12", - "rel": "required" - }, - { - "href": "#ia-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "ia-12.5_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Require that a {{ insert: param, ia-12.05_odp }} be delivered through an out-of-band channel to verify the users address (physical or digital) of record." - }, - { - "id": "ia-12.5_gdn", - "name": "guidance", - "prose": "To make it more difficult for adversaries to pose as legitimate users during the identity proofing process, organizations can use out-of-band methods to ensure that the individual associated with an address of record is the same individual that participated in the registration. Confirmation can take the form of a temporary enrollment code or a notice of proofing. The delivery address for these artifacts is obtained from records and not self-asserted by the user. The address can include a physical or digital address. A home address is an example of a physical address. Email addresses and telephone numbers are examples of digital addresses." - }, - { - "id": "ia-12.5_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "IA-12 (5) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ia-12.5_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "In accordance with NIST SP 800-63A Enrollment and Identity Proofing" - } - ] - }, - { - "id": "ia-12.5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IA-12(05)", - "class": "sp800-53a" - } - ], - "prose": "a {{ insert: param, ia-12.05_odp }} is delivered through an out-of-band channel to verify the user’s address (physical or digital) of record.", - "links": [ - { - "href": "#ia-12.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ia-12.5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IA-12(05)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Identification and authentication policy\n\nprocedures addressing identity proofing\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ia-12.5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IA-12(05)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system operations responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developers\n\norganizational personnel with identification and authentication responsibilities" - } - ] - }, - { - "id": "ia-12.5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IA-12(05)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing identification and authentication capabilities" - } - ] - } - ] - } - ] - } - ] - }, - { - "id": "ir", - "class": "family", - "title": "Incident Response", - "controls": [ - { - "id": "ir-1", - "class": "SP800-53", - "title": "Policy and Procedures", - "params": [ - { - "id": "ir-1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ir-01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ir-01_odp.02" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "ir-01_odp.01", - "props": [ - { - "name": "label", - "value": "IR-01_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the incident response policy is to be disseminated is/are defined;" - } - ] - }, - { - "id": "ir-01_odp.02", - "props": [ - { - "name": "label", - "value": "IR-01_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the incident response procedures are to be disseminated is/are defined;" - } - ] - }, - { - "id": "ir-01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ir-1_prm_2" - }, - { - "name": "label", - "value": "IR-01_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "organization-level", - "mission/business process-level", - "system-level" - ] - } - }, - { - "id": "ir-01_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "ir-1_prm_3" - }, - { - "name": "label", - "value": "IR-01_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "official", - "guidelines": [ - { - "prose": "an official to manage the incident response policy and procedures is defined;" - } - ] - }, - { - "id": "ir-01_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "ir-1_prm_4" - }, - { - "name": "label", - "value": "IR-01_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current incident response policy is reviewed and updated is defined;" - } - ] - }, - { - "id": "ir-01_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "ir-1_prm_5" - }, - { - "name": "label", - "value": "IR-01_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that would require the current incident response policy to be reviewed and updated are defined;" - } - ] - }, - { - "id": "ir-01_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "ir-1_prm_6" - }, - { - "name": "label", - "value": "IR-01_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current incident response procedures are reviewed and updated is defined;" - } - ] - }, - { - "id": "ir-01_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "ir-1_prm_7" - }, - { - "name": "label", - "value": "IR-01_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "events", - "constraints": [ - { - "description": "significant changes" - } - ], - "guidelines": [ - { - "prose": "events that would require the incident response procedures to be reviewed and updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IR-01", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-1" - }, - { - "name": "label", - "value": "IR-01", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#c7ac44e8-10db-4b64-b2b9-9e32ec1efed0", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#511f6832-23ca-49a3-8c0f-ce493373cab8", - "rel": "reference" - }, - { - "href": "#49b8aa2d-a88c-4bff-9f20-876ccb8f7dcb", - "rel": "reference" - }, - { - "href": "#3dd249b0-f57d-44ba-a03e-c3eab1b835ff", - "rel": "reference" - }, - { - "href": "#4c0ec2ee-a0d6-428a-9043-4504bc3ade6f", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "ir-1_smt", - "name": "statement", - "parts": [ - { - "id": "ir-1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, a policy that addresses Incident Response MUST be associated with IR-1 part a.", - "class": "policy" - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, at least one procedure that addresses Incident Response MUST be associated with IR-1 part a.", - "class": "procedure" - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, document, and disseminate to {{ insert: param, ir-1_prm_1 }}:", - "parts": [ - { - "id": "ir-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, ir-01_odp.03 }} incident response policy that:", - "parts": [ - { - "id": "ir-1_smt.a.1.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "ir-1_smt.a.1.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and" - } - ] - }, - { - "id": "ir-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the incident response policy and the associated incident response controls;" - } - ] - }, - { - "id": "ir-1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Designate an {{ insert: param, ir-01_odp.04 }} to manage the development, documentation, and dissemination of the incident response policy and procedures; and" - }, - { - "id": "ir-1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the current incident response:", - "parts": [ - { - "id": "ir-1_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Policy {{ insert: param, ir-01_odp.05 }} and following {{ insert: param, ir-01_odp.06 }} ; and" - }, - { - "id": "ir-1_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures {{ insert: param, ir-01_odp.07 }} and following {{ insert: param, ir-01_odp.08 }}." - } - ] - } - ] - }, - { - "id": "ir-1_gdn", - "name": "guidance", - "prose": "Incident response policy and procedures address the controls in the IR family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of incident response policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to incident response policy and procedures include assessment or audit findings, security incidents or breaches, or changes in laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure." - }, - { - "id": "ir-1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-01a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-01a.[01]", - "class": "sp800-53a" - } - ], - "prose": "an incident response policy is developed and documented;", - "links": [ - { - "href": "#ir-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-01a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the incident response policy is disseminated to {{ insert: param, ir-01_odp.01 }};", - "links": [ - { - "href": "#ir-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-1_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-01a.[03]", - "class": "sp800-53a" - } - ], - "prose": "incident response procedures to facilitate the implementation of the incident response policy and associated incident response controls are developed and documented;", - "links": [ - { - "href": "#ir-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-1_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-01a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the incident response procedures are disseminated to {{ insert: param, ir-01_odp.02 }};", - "links": [ - { - "href": "#ir-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-1_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-01a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-1_obj.a.1.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-01a.01(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-1_obj.a.1.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-01a.01(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ir-01_odp.03 }} incident response policy addresses purpose;", - "links": [ - { - "href": "#ir-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-1_obj.a.1.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-01a.01(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ir-01_odp.03 }} incident response policy addresses scope;", - "links": [ - { - "href": "#ir-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-1_obj.a.1.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-01a.01(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ir-01_odp.03 }} incident response policy addresses roles;", - "links": [ - { - "href": "#ir-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-1_obj.a.1.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-01a.01(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ir-01_odp.03 }} incident response policy addresses responsibilities;", - "links": [ - { - "href": "#ir-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-1_obj.a.1.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-01a.01(a)[05]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ir-01_odp.03 }} incident response policy addresses management commitment;", - "links": [ - { - "href": "#ir-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-1_obj.a.1.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-01a.01(a)[06]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ir-01_odp.03 }} incident response policy addresses coordination among organizational entities;", - "links": [ - { - "href": "#ir-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-1_obj.a.1.a-7", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-01a.01(a)[07]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ir-01_odp.03 }} incident response policy addresses compliance;", - "links": [ - { - "href": "#ir-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-1_obj.a.1.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-01a.01(b)", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ir-01_odp.03 }} incident response policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines;", - "links": [ - { - "href": "#ir-1_smt.a.1.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-1_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-01b.", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ir-01_odp.04 }} is designated to manage the development, documentation, and dissemination of the incident response policy and procedures;", - "links": [ - { - "href": "#ir-1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-01c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-1_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-01c.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-1_obj.c.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-01c.01[01]", - "class": "sp800-53a" - } - ], - "prose": "the current incident response policy is reviewed and updated {{ insert: param, ir-01_odp.05 }};", - "links": [ - { - "href": "#ir-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-1_obj.c.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-01c.01[02]", - "class": "sp800-53a" - } - ], - "prose": "the current incident response policy is reviewed and updated following {{ insert: param, ir-01_odp.06 }};", - "links": [ - { - "href": "#ir-1_smt.c.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-1_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-01c.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-1_obj.c.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-01c.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the current incident response procedures are reviewed and updated {{ insert: param, ir-01_odp.07 }};", - "links": [ - { - "href": "#ir-1_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-1_obj.c.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-01c.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the current incident response procedures are reviewed and updated following {{ insert: param, ir-01_odp.08 }}.", - "links": [ - { - "href": "#ir-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-1_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-01-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy and procedures\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-01-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident response responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - }, - { - "id": "ir-2", - "class": "SP800-53", - "title": "Incident Response Training", - "params": [ - { - "id": "ir-02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ir-2_prm_1" - }, - { - "name": "label", - "value": "IR-02_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "ten (10) days for privileged users, thirty (30) days for Incident Response roles" - } - ], - "guidelines": [ - { - "prose": "a time period within which incident response training is to be provided to system users assuming an incident response role or responsibility is defined;" - } - ] - }, - { - "id": "ir-02_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ir-2_prm_2" - }, - { - "name": "label", - "value": "IR-02_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "frequency at which to provide incident response training to users is defined;" - } - ] - }, - { - "id": "ir-02_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ir-2_prm_3" - }, - { - "name": "label", - "value": "IR-02_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "frequency at which to review and update incident response training content is defined;" - } - ] - }, - { - "id": "ir-02_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "ir-2_prm_4" - }, - { - "name": "label", - "value": "IR-02_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that initiate a review of the incident response training content are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IR-02", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-2" - }, - { - "name": "label", - "value": "IR-02", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#5f4705ac-8d17-438c-b23a-ac7f12362ae4", - "rel": "reference" - }, - { - "href": "#511f6832-23ca-49a3-8c0f-ce493373cab8", - "rel": "reference" - }, - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#at-4", - "rel": "related" - }, - { - "href": "#cp-3", - "rel": "related" - }, - { - "href": "#ir-3", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - }, - { - "href": "#ir-9", - "rel": "related" - } - ], - "parts": [ - { - "id": "ir-2_smt", - "name": "statement", - "parts": [ - { - "id": "ir-2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Provide incident response training to system users consistent with assigned roles and responsibilities:", - "parts": [ - { - "id": "ir-2_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Within {{ insert: param, ir-02_odp.01 }} of assuming an incident response role or responsibility or acquiring system access;" - }, - { - "id": "ir-2_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "When required by system changes; and" - }, - { - "id": "ir-2_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "{{ insert: param, ir-02_odp.02 }} thereafter; and" - } - ] - }, - { - "id": "ir-2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Review and update incident response training content {{ insert: param, ir-02_odp.03 }} and following {{ insert: param, ir-02_odp.04 }}." - } - ] - }, - { - "id": "ir-2_gdn", - "name": "guidance", - "prose": "Incident response training is associated with the assigned roles and responsibilities of organizational personnel to ensure that the appropriate content and level of detail are included in such training. For example, users may only need to know who to call or how to recognize an incident; system administrators may require additional training on how to handle incidents; and incident responders may receive more specific training on forensics, data collection techniques, reporting, system recovery, and system restoration. Incident response training includes user training in identifying and reporting suspicious activities from external and internal sources. Incident response training for users may be provided as part of [AT-2](#at-2) or [AT-3](#at-3) . Events that may precipitate an update to incident response training content include, but are not limited to, incident response plan testing or response to an actual incident (lessons learned), assessment or audit findings, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines." - }, - { - "id": "ir-2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-02a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-2_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-02a.01", - "class": "sp800-53a" - } - ], - "prose": "incident response training is provided to system users consistent with assigned roles and responsibilities within {{ insert: param, ir-02_odp.01 }} of assuming an incident response role or responsibility or acquiring system access;", - "links": [ - { - "href": "#ir-2_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-2_obj.a.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-02a.02", - "class": "sp800-53a" - } - ], - "prose": "incident response training is provided to system users consistent with assigned roles and responsibilities when required by system changes;", - "links": [ - { - "href": "#ir-2_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-2_obj.a.3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-02a.03", - "class": "sp800-53a" - } - ], - "prose": "incident response training is provided to system users consistent with assigned roles and responsibilities {{ insert: param, ir-02_odp.02 }} thereafter;", - "links": [ - { - "href": "#ir-2_smt.a.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-02b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-2_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-02b.[01]", - "class": "sp800-53a" - } - ], - "prose": "incident response training content is reviewed and updated {{ insert: param, ir-02_odp.03 }};", - "links": [ - { - "href": "#ir-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-2_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-02b.[02]", - "class": "sp800-53a" - } - ], - "prose": "incident response training content is reviewed and updated following {{ insert: param, ir-02_odp.04 }}.", - "links": [ - { - "href": "#ir-2_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-2_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-02-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing incident response training\n\nincident response training curriculum\n\nincident response training materials\n\nprivacy plan\n\nincident response plan\n\nincident response training records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-02-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident response training and operational responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ], - "controls": [ - { - "id": "ir-2.1", - "class": "SP800-53-enhancement", - "title": "Simulated Events", - "props": [ - { - "name": "label", - "value": "IR-02(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-2(1)" - }, - { - "name": "label", - "value": "IR-02(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-02.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ir-2", - "rel": "required" - } - ], - "parts": [ - { - "id": "ir-2.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Incorporate simulated events into incident response training to facilitate the required response by personnel in crisis situations." - }, - { - "id": "ir-2.1_gdn", - "name": "guidance", - "prose": "Organizations establish requirements for responding to incidents in incident response plans. Incorporating simulated events into incident response training helps to ensure that personnel understand their individual responsibilities and what specific actions to take in crisis situations." - }, - { - "id": "ir-2.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-02(01)", - "class": "sp800-53a" - } - ], - "prose": "simulated events are incorporated into incident response training to facilitate the required response by personnel in crisis situations.", - "links": [ - { - "href": "#ir-2.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-2.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-02(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing incident response training\n\nincident response training curriculum\n\nincident response training materials\n\nincident response plan\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-2.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-02(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident response training and operational responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "ir-2.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IR-02(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms that support and/or implement simulated events for incident response training" - } - ] - } - ] - }, - { - "id": "ir-2.2", - "class": "SP800-53-enhancement", - "title": "Automated Training Environments", - "params": [ - { - "id": "ir-02.02_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ir-2.2_prm_1" - }, - { - "name": "label", - "value": "IR-02(02)_ODP", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used in an incident response training environment are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IR-02(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-2(2)" - }, - { - "name": "label", - "value": "IR-02(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-02.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ir-2", - "rel": "required" - } - ], - "parts": [ - { - "id": "ir-2.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Provide an incident response training environment using {{ insert: param, ir-02.02_odp }}." - }, - { - "id": "ir-2.2_gdn", - "name": "guidance", - "prose": "Automated mechanisms can provide a more thorough and realistic incident response training environment. This can be accomplished, for example, by providing more complete coverage of incident response issues, selecting more realistic training scenarios and environments, and stressing the response capability." - }, - { - "id": "ir-2.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-02(02)", - "class": "sp800-53a" - } - ], - "prose": "an incident response training environment is provided using {{ insert: param, ir-02.02_odp }}.", - "links": [ - { - "href": "#ir-2.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-2.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-02(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing incident response training\n\nincident response training curriculum\n\nincident response training materials\n\nautomated mechanisms supporting incident response training\n\nincident response plan\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-2.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-02(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident response training and operational responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "ir-2.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IR-02(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Automated mechanisms that provide a thorough and realistic incident response training environment" - } - ] - } - ] - } - ] - }, - { - "id": "ir-3", - "class": "SP800-53", - "title": "Incident Response Testing", - "params": [ - { - "id": "ir-03_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ir-3_prm_1" - }, - { - "name": "label", - "value": "IR-03_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least every six (6) months, including functional at least annually" - } - ], - "guidelines": [ - { - "prose": "frequency at which to test the effectiveness of the incident response capability for the system is defined;" - } - ] - }, - { - "id": "ir-03_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ir-3_prm_2" - }, - { - "name": "label", - "value": "IR-03_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "tests", - "guidelines": [ - { - "prose": "tests used to test the effectiveness of the incident response capability for the system are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "IR-03", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-3" - }, - { - "name": "label", - "value": "IR-03", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#53be2fcf-cfd1-4bcb-896b-9a3b65c22098", - "rel": "reference" - }, - { - "href": "#122177fa-c4ed-485d-8345-3082c0fb9a06", - "rel": "reference" - }, - { - "href": "#cp-3", - "rel": "related" - }, - { - "href": "#cp-4", - "rel": "related" - }, - { - "href": "#ir-2", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-14", - "rel": "related" - } - ], - "parts": [ - { - "id": "ir-3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Test the effectiveness of the incident response capability for the system {{ insert: param, ir-03_odp.01 }} using the following tests: {{ insert: param, ir-03_odp.02 }}." - }, - { - "id": "ir-3_gdn", - "name": "guidance", - "prose": "Organizations test incident response capabilities to determine their effectiveness and identify potential weaknesses or deficiencies. Incident response testing includes the use of checklists, walk-through or tabletop exercises, and simulations (parallel or full interrupt). Incident response testing can include a determination of the effects on organizational operations and assets and individuals due to incident response. The use of qualitative and quantitative data aids in determining the effectiveness of incident response processes." - }, - { - "id": "ir-3_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "IR-3-2 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ir-3_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "The service provider defines tests and/or exercises in accordance with NIST Special Publication 800-61 (as amended). Functional testing must occur prior to testing for initial authorization. Annual functional testing may be concurrent with required penetration tests (see CA-8). The service provider provides test plans to the AO annually. Test plans are approved and accepted by the AO prior to test commencing." - } - ] - }, - { - "id": "ir-3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-03", - "class": "sp800-53a" - } - ], - "prose": "the effectiveness of the incident response capability for the system is tested {{ insert: param, ir-03_odp.01 }} using {{ insert: param, ir-03_odp.02 }}.", - "links": [ - { - "href": "#ir-3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-03-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\ncontingency planning policy\n\nprocedures addressing incident response testing\n\nprocedures addressing contingency plan testing\n\nincident response testing material\n\nincident response test results\n\nincident response test plan\n\nincident response plan\n\ncontingency plan\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-03-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident response testing responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ], - "controls": [ - { - "id": "ir-3.2", - "class": "SP800-53-enhancement", - "title": "Coordination with Related Plans", - "props": [ - { - "name": "label", - "value": "IR-03(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-3(2)" - }, - { - "name": "label", - "value": "IR-03(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-03.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ir-3", - "rel": "required" - } - ], - "parts": [ - { - "id": "ir-3.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Coordinate incident response testing with organizational elements responsible for related plans." - }, - { - "id": "ir-3.2_gdn", - "name": "guidance", - "prose": "Organizational plans related to incident response testing include business continuity plans, disaster recovery plans, continuity of operations plans, contingency plans, crisis communications plans, critical infrastructure plans, and occupant emergency plans." - }, - { - "id": "ir-3.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-03(02)", - "class": "sp800-53a" - } - ], - "prose": "incident response testing is coordinated with organizational elements responsible for related plans.", - "links": [ - { - "href": "#ir-3.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-3.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-03(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\ncontingency planning policy\n\nprocedures addressing incident response testing\n\nincident response testing documentation\n\nincident response plan\n\nbusiness continuity plans\n\ncontingency plans\n\ndisaster recovery plans\n\ncontinuity of operations plans\n\ncrisis communications plans\n\ncritical infrastructure plans\n\noccupant emergency plans\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-3.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-03(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident response testing responsibilities\n\norganizational personnel with responsibilities for testing organizational plans related to incident response testing\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "ir-4", - "class": "SP800-53", - "title": "Incident Handling", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "IR-04", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-4" - }, - { - "name": "label", - "value": "IR-04", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#4ff10ed3-d8fe-4246-99e3-443045e27482", - "rel": "reference" - }, - { - "href": "#0f963c17-ab5a-432a-a867-91eac550309b", - "rel": "reference" - }, - { - "href": "#5f4705ac-8d17-438c-b23a-ac7f12362ae4", - "rel": "reference" - }, - { - "href": "#49b8aa2d-a88c-4bff-9f20-876ccb8f7dcb", - "rel": "reference" - }, - { - "href": "#cfdb1858-c473-46b3-89f9-a700308d0be2", - "rel": "reference" - }, - { - "href": "#10cf2fad-a216-41f9-bb1a-531b7e3119e3", - "rel": "reference" - }, - { - "href": "#9ef4b43c-42a4-4316-87dc-ffaf528bc05c", - "rel": "reference" - }, - { - "href": "#61ccf0f4-d3e7-42db-9796-ce6cb1c85989", - "rel": "reference" - }, - { - "href": "#31ae65ab-3f26-46b7-9d64-f25a4dac5778", - "rel": "reference" - }, - { - "href": "#2be7b163-e50a-435c-8906-f1162f2a457a", - "rel": "reference" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-7", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-3", - "rel": "related" - }, - { - "href": "#cp-4", - "rel": "related" - }, - { - "href": "#ir-2", - "rel": "related" - }, - { - "href": "#ir-3", - "rel": "related" - }, - { - "href": "#ir-5", - "rel": "related" - }, - { - "href": "#ir-6", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - }, - { - "href": "#pe-6", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-12", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sc-5", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "ir-4_smt", - "name": "statement", - "parts": [ - { - "id": "ir-4_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Implement an incident handling capability for incidents that is consistent with the incident response plan and includes preparation, detection and analysis, containment, eradication, and recovery;" - }, - { - "id": "ir-4_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Coordinate incident handling activities with contingency planning activities;" - }, - { - "id": "ir-4_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Incorporate lessons learned from ongoing incident handling activities into incident response procedures, training, and testing, and implement the resulting changes accordingly; and" - }, - { - "id": "ir-4_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Ensure the rigor, intensity, scope, and results of incident handling activities are comparable and predictable across the organization." - } - ] - }, - { - "id": "ir-4_gdn", - "name": "guidance", - "prose": "Organizations recognize that incident response capabilities are dependent on the capabilities of organizational systems and the mission and business processes being supported by those systems. Organizations consider incident response as part of the definition, design, and development of mission and business processes and systems. Incident-related information can be obtained from a variety of sources, including audit monitoring, physical access monitoring, and network monitoring; user or administrator reports; and reported supply chain events. An effective incident handling capability includes coordination among many organizational entities (e.g., mission or business owners, system owners, authorizing officials, human resources offices, physical security offices, personnel security offices, legal departments, risk executive \\[function\\], operations personnel, procurement offices). Suspected security incidents include the receipt of suspicious email communications that can contain malicious code. Suspected supply chain incidents include the insertion of counterfeit hardware or malicious code into organizational systems or system components. For federal agencies, an incident that involves personally identifiable information is considered a breach. A breach results in unauthorized disclosure, the loss of control, unauthorized acquisition, compromise, or a similar occurrence where a person other than an authorized user accesses or potentially accesses personally identifiable information or an authorized user accesses or potentially accesses such information for other than authorized purposes." - }, - { - "id": "ir-4_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "IR-4 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ir-4_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "The FISMA definition of \"incident\" shall be used: \"An occurrence that actually or imminently jeopardizes, without lawful authority, the confidentiality, integrity, or availability of information or an information system; or constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies.\"" - }, - { - "id": "ir-4_fr_smt.2", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "The service provider ensures that individuals conducting incident handling meet personnel security requirements commensurate with the criticality/sensitivity of the information being processed, stored, and transmitted by the information system." - } - ] - }, - { - "id": "ir-4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-04", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-4_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-04a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-4_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-04a.[01]", - "class": "sp800-53a" - } - ], - "prose": "an incident handling capability for incidents is implemented that is consistent with the incident response plan;", - "links": [ - { - "href": "#ir-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-4_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-04a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the incident handling capability for incidents includes preparation;", - "links": [ - { - "href": "#ir-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-4_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-04a.[03]", - "class": "sp800-53a" - } - ], - "prose": "the incident handling capability for incidents includes detection and analysis;", - "links": [ - { - "href": "#ir-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-4_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-04a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the incident handling capability for incidents includes containment;", - "links": [ - { - "href": "#ir-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-4_obj.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-04a.[05]", - "class": "sp800-53a" - } - ], - "prose": "the incident handling capability for incidents includes eradication;", - "links": [ - { - "href": "#ir-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-4_obj.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-04a.[06]", - "class": "sp800-53a" - } - ], - "prose": "the incident handling capability for incidents includes recovery;", - "links": [ - { - "href": "#ir-4_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-4_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-04b.", - "class": "sp800-53a" - } - ], - "prose": "incident handling activities are coordinated with contingency planning activities;", - "links": [ - { - "href": "#ir-4_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-4_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-04c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-4_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-04c.[01]", - "class": "sp800-53a" - } - ], - "prose": "lessons learned from ongoing incident handling activities are incorporated into incident response procedures, training, and testing;", - "links": [ - { - "href": "#ir-4_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-4_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-04c.[02]", - "class": "sp800-53a" - } - ], - "prose": "the changes resulting from the incorporated lessons learned are implemented accordingly;", - "links": [ - { - "href": "#ir-4_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-4_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-4_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-04d.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-4_obj.d-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-04d.[01]", - "class": "sp800-53a" - } - ], - "prose": "the rigor of incident handling activities is comparable and predictable across the organization;", - "links": [ - { - "href": "#ir-4_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-4_obj.d-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-04d.[02]", - "class": "sp800-53a" - } - ], - "prose": "the intensity of incident handling activities is comparable and predictable across the organization;", - "links": [ - { - "href": "#ir-4_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-4_obj.d-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-04d.[03]", - "class": "sp800-53a" - } - ], - "prose": "the scope of incident handling activities is comparable and predictable across the organization;", - "links": [ - { - "href": "#ir-4_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-4_obj.d-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-04d.[04]", - "class": "sp800-53a" - } - ], - "prose": "the results of incident handling activities are comparable and predictable across the organization.", - "links": [ - { - "href": "#ir-4_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-4_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-04-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\ncontingency planning policy\n\nprocedures addressing incident handling\n\nincident response plan\n\ncontingency plan\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-04-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident handling responsibilities\n\norganizational personnel with contingency planning responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "ir-4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IR-04-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident handling capability for the organization" - } - ] - } - ], - "controls": [ - { - "id": "ir-4.1", - "class": "SP800-53-enhancement", - "title": "Automated Incident Handling Processes", - "params": [ - { - "id": "ir-04.01_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ir-4.1_prm_1" - }, - { - "name": "label", - "value": "IR-04(01)_ODP", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used to support the incident handling process are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "IR-04(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-4(1)" - }, - { - "name": "label", - "value": "IR-04(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-04.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ir-4", - "rel": "required" - } - ], - "parts": [ - { - "id": "ir-4.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Support the incident handling process using {{ insert: param, ir-04.01_odp }}." - }, - { - "id": "ir-4.1_gdn", - "name": "guidance", - "prose": "Automated mechanisms that support incident handling processes include online incident management systems and tools that support the collection of live response data, full network packet capture, and forensic analysis." - }, - { - "id": "ir-4.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-04(01)", - "class": "sp800-53a" - } - ], - "prose": "the incident handling process is supported using {{ insert: param, ir-04.01_odp }}.", - "links": [ - { - "href": "#ir-4.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-4.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-04(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing incident handling\n\nautomated mechanisms supporting incident handling\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nincident response plan\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-4.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-04(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident handling responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ir-4.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IR-04(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Automated mechanisms that support and/or implement the incident handling process" - } - ] - } - ] - }, - { - "id": "ir-4.2", - "class": "SP800-53-enhancement", - "title": "Dynamic Reconfiguration", - "params": [ - { - "id": "ir-04.02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ir-4.2_prm_2" - }, - { - "name": "label", - "value": "IR-04(02)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "types of dynamic reconfiguration", - "guidelines": [ - { - "prose": "types of dynamic reconfiguration for system components are defined;" - } - ] - }, - { - "id": "ir-04.02_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ir-4.2_prm_1" - }, - { - "name": "label", - "value": "IR-04(02)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "system components", - "constraints": [ - { - "description": "all network, data storage, and computing devices" - } - ], - "guidelines": [ - { - "prose": "system components that require dynamic reconfiguration are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "IR-04(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-4(2)" - }, - { - "name": "label", - "value": "IR-04(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-04.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ir-4", - "rel": "required" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - } - ], - "parts": [ - { - "id": "ir-4.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Include the following types of dynamic reconfiguration for {{ insert: param, ir-04.02_odp.02 }} as part of the incident response capability: {{ insert: param, ir-04.02_odp.01 }}." - }, - { - "id": "ir-4.2_gdn", - "name": "guidance", - "prose": "Dynamic reconfiguration includes changes to router rules, access control lists, intrusion detection or prevention system parameters, and filter rules for guards or firewalls. Organizations may perform dynamic reconfiguration of systems to stop attacks, misdirect attackers, and isolate components of systems, thus limiting the extent of the damage from breaches or compromises. Organizations include specific time frames for achieving the reconfiguration of systems in the definition of the reconfiguration capability, considering the potential need for rapid response to effectively address cyber threats." - }, - { - "id": "ir-4.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-04(02)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ir-04.02_odp.01 }} for {{ insert: param, ir-04.02_odp.02 }} are included as part of the incident response capability.", - "links": [ - { - "href": "#ir-4.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-4.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-04(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing incident handling\n\nmechanisms supporting incident handling\n\nlist of system components to be dynamically reconfigured as part of incident response capability\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nincident response plan\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-4.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-04(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident handling responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ir-4.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IR-04(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms that support and/or implement the dynamic reconfiguration of components as part of incident response" - } - ] - } - ] - }, - { - "id": "ir-4.4", - "class": "SP800-53-enhancement", - "title": "Information Correlation", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "IR-04(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-4(4)" - }, - { - "name": "label", - "value": "IR-04(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-04.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ir-4", - "rel": "required" - } - ], - "parts": [ - { - "id": "ir-4.4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Correlate incident information and individual incident responses to achieve an organization-wide perspective on incident awareness and response." - }, - { - "id": "ir-4.4_gdn", - "name": "guidance", - "prose": "Sometimes, a threat event, such as a hostile cyber-attack, can only be observed by bringing together information from different sources, including various reports and reporting procedures established by organizations." - }, - { - "id": "ir-4.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-04(04)", - "class": "sp800-53a" - } - ], - "prose": "incident information and individual incident responses are correlated to achieve an organization-wide perspective on incident awareness and response.", - "links": [ - { - "href": "#ir-4.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-4.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-04(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing incident handling\n\nincident response plan\n\nprivacy plan\n\nmechanisms supporting incident and event correlation\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem security plan\n\nprivacy plan\n\nincident management correlation logs\n\nevent management correlation logs\n\nsecurity information and event management logs\n\nincident management correlation reports\n\nevent management correlation reports\n\nsecurity information and event management reports\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-4.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-04(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident handling responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\norganizational personnel with whom incident information and individual incident responses are to be correlated" - } - ] - }, - { - "id": "ir-4.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IR-04(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for correlating incident information and individual incident responses\n\nmechanisms that support and or implement the correlation of incident response information with individual incident responses" - } - ] - } - ] - }, - { - "id": "ir-4.6", - "class": "SP800-53-enhancement", - "title": "Insider Threats", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "IR-04(06)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-4(6)" - }, - { - "name": "label", - "value": "IR-04(06)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-04.06" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ir-4", - "rel": "required" - } - ], - "parts": [ - { - "id": "ir-4.6_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement an incident handling capability for incidents involving insider threats." - }, - { - "id": "ir-4.6_gdn", - "name": "guidance", - "prose": "Explicit focus on handling incidents involving insider threats provides additional emphasis on this type of threat and the need for specific incident handling capabilities to provide appropriate and timely responses." - }, - { - "id": "ir-4.6_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-04(06)", - "class": "sp800-53a" - } - ], - "prose": "an incident handling capability is implemented for incidents involving insider threats.", - "links": [ - { - "href": "#ir-4.6_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-4.6_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-04(06)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing incident handling\n\nmechanisms supporting incident handling\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nincident response plan\n\nsystem security plan\n\naudit records\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-4.6_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-04(06)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident handling responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ir-4.6_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IR-04(06)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident handling capability for the organization" - } - ] - } - ] - }, - { - "id": "ir-4.11", - "class": "SP800-53-enhancement", - "title": "Integrated Incident Response Team", - "params": [ - { - "id": "ir-04.11_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ir-4.11_prm_1" - }, - { - "name": "label", - "value": "IR-04(11)_ODP", - "class": "sp800-53a" - } - ], - "label": "time period", - "guidelines": [ - { - "prose": "the time period within which an integrated incident response team can be deployed is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IR-04(11)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-4(11)" - }, - { - "name": "label", - "value": "IR-04(11)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-04.11" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ir-4", - "rel": "required" - }, - { - "href": "#at-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "ir-4.11_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Establish and maintain an integrated incident response team that can be deployed to any location identified by the organization in {{ insert: param, ir-04.11_odp }}." - }, - { - "id": "ir-4.11_gdn", - "name": "guidance", - "prose": "An integrated incident response team is a team of experts that assesses, documents, and responds to incidents so that organizational systems and networks can recover quickly and implement the necessary controls to avoid future incidents. Incident response team personnel include forensic and malicious code analysts, tool developers, systems security and privacy engineers, and real-time operations personnel. The incident handling capability includes performing rapid forensic preservation of evidence and analysis of and response to intrusions. For some organizations, the incident response team can be a cross-organizational entity.\n\nAn integrated incident response team facilitates information sharing and allows organizational personnel (e.g., developers, implementers, and operators) to leverage team knowledge of the threat and implement defensive measures that enable organizations to deter intrusions more effectively. Moreover, integrated teams promote the rapid detection of intrusions, the development of appropriate mitigations, and the deployment of effective defensive measures. For example, when an intrusion is detected, the integrated team can rapidly develop an appropriate response for operators to implement, correlate the new incident with information on past intrusions, and augment ongoing cyber intelligence development. Integrated incident response teams are better able to identify adversary tactics, techniques, and procedures that are linked to the operations tempo or specific mission and business functions and to define responsive actions in a way that does not disrupt those mission and business functions. Incident response teams can be distributed within organizations to make the capability resilient." - }, - { - "id": "ir-4.11_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-04(11)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-4.11_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-04(11)[01]", - "class": "sp800-53a" - } - ], - "prose": "an integrated incident response team is established and maintained;", - "links": [ - { - "href": "#ir-4.11_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-4.11_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-04(11)[02]", - "class": "sp800-53a" - } - ], - "prose": "the integrated incident response team can be deployed to any location identified by the organization in {{ insert: param, ir-04.11_odp }}.", - "links": [ - { - "href": "#ir-4.11_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-4.11_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-4.11_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-04(11)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing incident handling\n\nprocedures addressing incident response planning\n\nincident response plan\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-4.11_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-04(11)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident handling responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nmembers of the integrated incident response team" - } - ] - } - ] - } - ] - }, - { - "id": "ir-5", - "class": "SP800-53", - "title": "Incident Monitoring", - "props": [ - { - "name": "label", - "value": "IR-05", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-5" - }, - { - "name": "label", - "value": "IR-05", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#49b8aa2d-a88c-4bff-9f20-876ccb8f7dcb", - "rel": "reference" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-7", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-6", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - }, - { - "href": "#pe-6", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-5", - "rel": "related" - }, - { - "href": "#sc-5", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "ir-5_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Track and document incidents." - }, - { - "id": "ir-5_gdn", - "name": "guidance", - "prose": "Documenting incidents includes maintaining records about each incident, the status of the incident, and other pertinent information necessary for forensics as well as evaluating incident details, trends, and handling. Incident information can be obtained from a variety of sources, including network monitoring, incident reports, incident response teams, user complaints, supply chain partners, audit monitoring, physical access monitoring, and user and administrator reports. [IR-4](#ir-4) provides information on the types of incidents that are appropriate for monitoring." - }, - { - "id": "ir-5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-05", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-5_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-05[01]", - "class": "sp800-53a" - } - ], - "prose": "incidents are tracked;", - "links": [ - { - "href": "#ir-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-5_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-05[02]", - "class": "sp800-53a" - } - ], - "prose": "incidents are documented.", - "links": [ - { - "href": "#ir-5_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-05-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing incident monitoring\n\nincident response records and documentation\n\nincident response plan\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-05-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident monitoring responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "ir-5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IR-05-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident monitoring capability for the organization\n\nmechanisms supporting and/or implementing the tracking and documenting of system security incidents" - } - ] - } - ], - "controls": [ - { - "id": "ir-5.1", - "class": "SP800-53-enhancement", - "title": "Automated Tracking, Data Collection, and Analysis", - "params": [ - { - "id": "ir-5.1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ir-05.01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ir-05.01_odp.02" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ir-05.01_odp.03" - } - ], - "label": "organization-defined automated mechanisms" - }, - { - "id": "ir-05.01_odp.01", - "props": [ - { - "name": "label", - "value": "IR-05(01)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used to track incidents are defined;" - } - ] - }, - { - "id": "ir-05.01_odp.02", - "props": [ - { - "name": "label", - "value": "IR-05(01)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used to collect incident information are defined;" - } - ] - }, - { - "id": "ir-05.01_odp.03", - "props": [ - { - "name": "label", - "value": "IR-05(01)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used to analyze incident information are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IR-05(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-5(1)" - }, - { - "name": "label", - "value": "IR-05(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-05.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ir-5", - "rel": "required" - } - ], - "parts": [ - { - "id": "ir-5.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Track incidents and collect and analyze incident information using {{ insert: param, ir-5.1_prm_1 }}." - }, - { - "id": "ir-5.1_gdn", - "name": "guidance", - "prose": "Automated mechanisms for tracking incidents and collecting and analyzing incident information include Computer Incident Response Centers or other electronic databases of incidents and network monitoring devices." - }, - { - "id": "ir-5.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-05(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-5.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-05(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "incidents are tracked using {{ insert: param, ir-05.01_odp.01 }};", - "links": [ - { - "href": "#ir-5.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-5.1_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-05(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "incident information is collected using {{ insert: param, ir-05.01_odp.02 }};", - "links": [ - { - "href": "#ir-5.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-5.1_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-05(01)[03]", - "class": "sp800-53a" - } - ], - "prose": "incident information is analyzed using {{ insert: param, ir-05.01_odp.03 }}.", - "links": [ - { - "href": "#ir-5.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-5.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-5.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-05(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing incident monitoring\n\nincident response records and documentation\n\nsystem security plan\n\nincident response plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-5.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-05(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident monitoring responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ir-5.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IR-05(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident monitoring capability for the organization\n\nautomated mechanisms supporting and/or implementing the tracking and documenting of system security incidents" - } - ] - } - ] - } - ] - }, - { - "id": "ir-6", - "class": "SP800-53", - "title": "Incident Reporting", - "params": [ - { - "id": "ir-06_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ir-6_prm_1" - }, - { - "name": "label", - "value": "IR-06_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "US-CERT incident reporting timelines as specified in NIST Special Publication 800-61 (as amended)" - } - ], - "guidelines": [ - { - "prose": "time period for personnel to report suspected incidents to the organizational incident response capability is defined;" - } - ] - }, - { - "id": "ir-06_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ir-6_prm_2" - }, - { - "name": "label", - "value": "IR-06_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "authorities", - "guidelines": [ - { - "prose": "authorities to whom incident information is to be reported are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IR-06", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-6" - }, - { - "name": "label", - "value": "IR-06", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-06" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#4ff10ed3-d8fe-4246-99e3-443045e27482", - "rel": "reference" - }, - { - "href": "#0f963c17-ab5a-432a-a867-91eac550309b", - "rel": "reference" - }, - { - "href": "#40b78258-c892-480e-9af8-77ac36648301", - "rel": "reference" - }, - { - "href": "#49b8aa2d-a88c-4bff-9f20-876ccb8f7dcb", - "rel": "reference" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-5", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - }, - { - "href": "#ir-9", - "rel": "related" - } - ], - "parts": [ - { - "id": "ir-6_smt", - "name": "statement", - "parts": [ - { - "id": "ir-6_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Require personnel to report suspected incidents to the organizational incident response capability within {{ insert: param, ir-06_odp.01 }} ; and" - }, - { - "id": "ir-6_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Report incident information to {{ insert: param, ir-06_odp.02 }}." - } - ] - }, - { - "id": "ir-6_gdn", - "name": "guidance", - "prose": "The types of incidents reported, the content and timeliness of the reports, and the designated reporting authorities reflect applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Incident information can inform risk assessments, control effectiveness assessments, security requirements for acquisitions, and selection criteria for technology products." - }, - { - "id": "ir-6_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "IR-6 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ir-6_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Reports security incident information according to FedRAMP Incident Communications Procedure." - } - ] - }, - { - "id": "ir-6_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-06", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-6_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-06a.", - "class": "sp800-53a" - } - ], - "prose": "personnel is/are required to report suspected incidents to the organizational incident response capability within {{ insert: param, ir-06_odp.01 }};", - "links": [ - { - "href": "#ir-6_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-6_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-06b.", - "class": "sp800-53a" - } - ], - "prose": "incident information is reported to {{ insert: param, ir-06_odp.02 }}.", - "links": [ - { - "href": "#ir-6_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-6_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-6_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-06-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing incident reporting\n\nincident reporting records and documentation\n\nincident response plan\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-6_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-06-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident reporting responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\npersonnel who have/should have reported incidents\n\npersonnel (authorities) to whom incident information is to be reported\n\nsystem users" - } - ] - }, - { - "id": "ir-6_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IR-06-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for incident reporting\n\nmechanisms supporting and/or implementing incident reporting" - } - ] - } - ], - "controls": [ - { - "id": "ir-6.1", - "class": "SP800-53-enhancement", - "title": "Automated Reporting", - "params": [ - { - "id": "ir-06.01_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ir-6.1_prm_1" - }, - { - "name": "label", - "value": "IR-06(01)_ODP", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used for reporting incidents are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IR-06(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-6(1)" - }, - { - "name": "label", - "value": "IR-06(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-06.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ir-6", - "rel": "required" - }, - { - "href": "#ir-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "ir-6.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Report incidents using {{ insert: param, ir-06.01_odp }}." - }, - { - "id": "ir-6.1_gdn", - "name": "guidance", - "prose": "The recipients of incident reports are specified in [IR-6b](#ir-6_smt.b) . Automated reporting mechanisms include email, posting on websites (with automatic updates), and automated incident response tools and programs." - }, - { - "id": "ir-6.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-06(01)", - "class": "sp800-53a" - } - ], - "prose": "incidents are reported using {{ insert: param, ir-06.01_odp }}.", - "links": [ - { - "href": "#ir-6.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-6.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-06(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing incident reporting\n\nautomated mechanisms supporting incident reporting\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nincident response plan\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-6.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-06(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident reporting responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ir-6.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IR-06(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for incident reporting\n\nautomated mechanisms supporting and/or implementing the reporting of security incidents" - } - ] - } - ] - }, - { - "id": "ir-6.3", - "class": "SP800-53-enhancement", - "title": "Supply Chain Coordination", - "props": [ - { - "name": "label", - "value": "IR-06(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-6(3)" - }, - { - "name": "label", - "value": "IR-06(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-06.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ir-6", - "rel": "required" - }, - { - "href": "#sr-8", - "rel": "related" - } - ], - "parts": [ - { - "id": "ir-6.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Provide incident information to the provider of the product or service and other organizations involved in the supply chain or supply chain governance for systems or system components related to the incident." - }, - { - "id": "ir-6.3_gdn", - "name": "guidance", - "prose": "Organizations involved in supply chain activities include product developers, system integrators, manufacturers, packagers, assemblers, distributors, vendors, and resellers. Entities that provide supply chain governance include the Federal Acquisition Security Council (FASC). Supply chain incidents include compromises or breaches that involve information technology products, system components, development processes or personnel, distribution processes, or warehousing facilities. Organizations determine the appropriate information to share and consider the value gained from informing external organizations about supply chain incidents, including the ability to improve processes or to identify the root cause of an incident." - }, - { - "id": "ir-6.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-06(03)", - "class": "sp800-53a" - } - ], - "prose": "incident information is provided to the provider of the product or service and other organizations involved in the supply chain or supply chain governance for systems or system components related to the incident.", - "links": [ - { - "href": "#ir-6.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-6.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-06(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing supply chain coordination and supply chain risk information sharing with the Federal Acquisition Security Council\n\nacquisition policy\n\nacquisition contracts\n\nservice-level agreements\n\nincident response plan\n\nsupply chain risk management plan\n\nsystem security plan\n\nplans of other organizations involved in supply chain activities\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-6.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-06(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident reporting responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain risk management responsibilities\n\norganization personnel with acquisition responsibilities" - } - ] - }, - { - "id": "ir-6.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IR-06(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for incident reporting\n\norganizational processes for supply chain risk information sharing\n\nmechanisms supporting and/or implementing the reporting of incident information involved in the supply chain" - } - ] - } - ] - } - ] - }, - { - "id": "ir-7", - "class": "SP800-53", - "title": "Incident Response Assistance", - "props": [ - { - "name": "label", - "value": "IR-07", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-7" - }, - { - "name": "label", - "value": "IR-07", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-07" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#2be7b163-e50a-435c-8906-f1162f2a457a", - "rel": "reference" - }, - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-6", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-22", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-26", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#si-18", - "rel": "related" - } - ], - "parts": [ - { - "id": "ir-7_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Provide an incident response support resource, integral to the organizational incident response capability, that offers advice and assistance to users of the system for the handling and reporting of incidents." - }, - { - "id": "ir-7_gdn", - "name": "guidance", - "prose": "Incident response support resources provided by organizations include help desks, assistance groups, automated ticketing systems to open and track incident response tickets, and access to forensics services or consumer redress services, when required." - }, - { - "id": "ir-7_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-07", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-7_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-07[01]", - "class": "sp800-53a" - } - ], - "prose": "an incident response support resource, integral to the organizational incident response capability, is provided;", - "links": [ - { - "href": "#ir-7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-7_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-07[02]", - "class": "sp800-53a" - } - ], - "prose": "the incident response support resource offers advice and assistance to users of the system for the response and reporting of incidents.", - "links": [ - { - "href": "#ir-7_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-7_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-07-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing incident response assistance\n\nincident response plan\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-7_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-07-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident response assistance and support responsibilities\n\norganizational personnel with access to incident response support and assistance capability\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "ir-7_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IR-07-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for incident response assistance\n\nmechanisms supporting and/or implementing incident response assistance" - } - ] - } - ], - "controls": [ - { - "id": "ir-7.1", - "class": "SP800-53-enhancement", - "title": "Automation Support for Availability of Information and Support", - "params": [ - { - "id": "ir-07.01_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ir-7.1_prm_1" - }, - { - "name": "label", - "value": "IR-07(01)_ODP", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used to increase the availability of incident response information and support are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IR-07(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-7(1)" - }, - { - "name": "label", - "value": "IR-07(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-07.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ir-7", - "rel": "required" - } - ], - "parts": [ - { - "id": "ir-7.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Increase the availability of incident response information and support using {{ insert: param, ir-07.01_odp }}." - }, - { - "id": "ir-7.1_gdn", - "name": "guidance", - "prose": "Automated mechanisms can provide a push or pull capability for users to obtain incident response assistance. For example, individuals may have access to a website to query the assistance capability, or the assistance capability can proactively send incident response information to users (general distribution or targeted) as part of increasing understanding of current response capabilities and support." - }, - { - "id": "ir-7.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-07(01)", - "class": "sp800-53a" - } - ], - "prose": "the availability of incident response information and support is increased using {{ insert: param, ir-07.01_odp }}.", - "links": [ - { - "href": "#ir-7.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-7.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-07(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing incident response assistance\n\nautomated mechanisms supporting incident response support and assistance\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nincident response plan\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-7.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-07(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident response support and assistance responsibilities\n\norganizational personnel with access to incident response support and assistance capability\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ir-7.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IR-07(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for incident response assistance\n\nautomated mechanisms supporting and/or implementing an increase in the availability of incident response information and support" - } - ] - } - ] - } - ] - }, - { - "id": "ir-8", - "class": "SP800-53", - "title": "Incident Response Plan", - "params": [ - { - "id": "ir-8_prm_5", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ir-08_odp.06" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ir-08_odp.05" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ir-08_odp.07" - } - ], - "label": "organization-defined incident response personnel (identified by name and/or by role) and organizational elements" - }, - { - "id": "ir-08_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ir-8_prm_1" - }, - { - "name": "label", - "value": "IR-08_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles that review and approve the incident response plan is/are identified;" - } - ] - }, - { - "id": "ir-08_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ir-8_prm_2" - }, - { - "name": "label", - "value": "IR-08_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to review and approve the incident response plan is defined;" - } - ] - }, - { - "id": "ir-08_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ir-8_prm_3" - }, - { - "name": "label", - "value": "IR-08_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "entities, personnel, or roles", - "guidelines": [ - { - "prose": "entities, personnel, or roles with designated responsibility for incident response are defined;" - } - ] - }, - { - "id": "ir-08_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "ir-8_prm_4" - }, - { - "name": "alt-label", - "value": "incident response personnel (identified by name and/or by role) and organizational elements", - "class": "sp800-53" - }, - { - "name": "label", - "value": "IR-08_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "incident response personnel", - "constraints": [ - { - "description": "see additional FedRAMP Requirements and Guidance" - } - ], - "guidelines": [ - { - "prose": "incident response personnel (identified by name and/or by role) to whom copies of the incident response plan are to be distributed is/are defined;" - } - ] - }, - { - "id": "ir-08_odp.05", - "props": [ - { - "name": "label", - "value": "IR-08_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "organizational elements", - "constraints": [ - { - "description": "see additional FedRAMP Requirements and Guidance" - } - ], - "guidelines": [ - { - "prose": "organizational elements to which copies of the incident response plan are to be distributed are defined;" - } - ] - }, - { - "id": "ir-08_odp.06", - "props": [ - { - "name": "label", - "value": "IR-08_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "incident response personnel", - "constraints": [ - { - "description": "see additional FedRAMP Requirements and Guidance" - } - ], - "guidelines": [ - { - "prose": "incident response personnel (identified by name and/or by role) to whom changes to the incident response plan is/are communicated are defined;" - } - ] - }, - { - "id": "ir-08_odp.07", - "props": [ - { - "name": "label", - "value": "IR-08_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "organizational elements", - "constraints": [ - { - "description": "see additional FedRAMP Requirements and Guidance" - } - ], - "guidelines": [ - { - "prose": "organizational elements to which changes to the incident response plan are communicated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IR-08", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-8" - }, - { - "name": "label", - "value": "IR-08", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#49b8aa2d-a88c-4bff-9f20-876ccb8f7dcb", - "rel": "reference" - }, - { - "href": "#5f4705ac-8d17-438c-b23a-ac7f12362ae4", - "rel": "reference" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-4", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-7", - "rel": "related" - }, - { - "href": "#ir-9", - "rel": "related" - }, - { - "href": "#pe-6", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - }, - { - "href": "#sr-8", - "rel": "related" - } - ], - "parts": [ - { - "id": "ir-8_smt", - "name": "statement", - "parts": [ - { - "id": "ir-8_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop an incident response plan that:", - "parts": [ - { - "id": "ir-8_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Provides the organization with a roadmap for implementing its incident response capability;" - }, - { - "id": "ir-8_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Describes the structure and organization of the incident response capability;" - }, - { - "id": "ir-8_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Provides a high-level approach for how the incident response capability fits into the overall organization;" - }, - { - "id": "ir-8_smt.a.4", - "name": "item", - "props": [ - { - "name": "label", - "value": "4." - } - ], - "prose": "Meets the unique requirements of the organization, which relate to mission, size, structure, and functions;" - }, - { - "id": "ir-8_smt.a.5", - "name": "item", - "props": [ - { - "name": "label", - "value": "5." - } - ], - "prose": "Defines reportable incidents;" - }, - { - "id": "ir-8_smt.a.6", - "name": "item", - "props": [ - { - "name": "label", - "value": "6." - } - ], - "prose": "Provides metrics for measuring the incident response capability within the organization;" - }, - { - "id": "ir-8_smt.a.7", - "name": "item", - "props": [ - { - "name": "label", - "value": "7." - } - ], - "prose": "Defines the resources and management support needed to effectively maintain and mature an incident response capability;" - }, - { - "id": "ir-8_smt.a.8", - "name": "item", - "props": [ - { - "name": "label", - "value": "8." - } - ], - "prose": "Addresses the sharing of incident information;" - }, - { - "id": "ir-8_smt.a.9", - "name": "item", - "props": [ - { - "name": "label", - "value": "9." - } - ], - "prose": "Is reviewed and approved by {{ insert: param, ir-08_odp.01 }} {{ insert: param, ir-08_odp.02 }} ; and" - }, - { - "id": "ir-8_smt.a.10", - "name": "item", - "props": [ - { - "name": "label", - "value": "10." - } - ], - "prose": "Explicitly designates responsibility for incident response to {{ insert: param, ir-08_odp.03 }}." - } - ] - }, - { - "id": "ir-8_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Distribute copies of the incident response plan to {{ insert: param, ir-08_odp.04 }};" - }, - { - "id": "ir-8_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Update the incident response plan to address system and organizational changes or problems encountered during plan implementation, execution, or testing;" - }, - { - "id": "ir-8_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Communicate incident response plan changes to {{ insert: param, ir-8_prm_5 }} ; and" - }, - { - "id": "ir-8_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Protect the incident response plan from unauthorized disclosure and modification." - } - ] - }, - { - "id": "ir-8_gdn", - "name": "guidance", - "prose": "It is important that organizations develop and implement a coordinated approach to incident response. Organizational mission and business functions determine the structure of incident response capabilities. As part of the incident response capabilities, organizations consider the coordination and sharing of information with external organizations, including external service providers and other organizations involved in the supply chain. For incidents involving personally identifiable information (i.e., breaches), include a process to determine whether notice to oversight organizations or affected individuals is appropriate and provide that notice accordingly." - }, - { - "id": "ir-8_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "IR-8 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ir-8_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(b) Requirement:" - } - ], - "prose": "The service provider defines a list of incident response personnel (identified by name and/or by role) and organizational elements. The incident response list includes designated FedRAMP personnel." - }, - { - "id": "ir-8_fr_smt.2", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(d) Requirement:" - } - ], - "prose": "The service provider defines a list of incident response personnel (identified by name and/or by role) and organizational elements. The incident response list includes designated FedRAMP personnel." - } - ] - }, - { - "id": "ir-8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-08", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-8_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-08a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-8_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-08a.01", - "class": "sp800-53a" - } - ], - "prose": "an incident response plan is developed that provides the organization with a roadmap for implementing its incident response capability;", - "links": [ - { - "href": "#ir-8_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-8_obj.a.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-08a.02", - "class": "sp800-53a" - } - ], - "prose": "an incident response plan is developed that describes the structure and organization of the incident response capability;", - "links": [ - { - "href": "#ir-8_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-8_obj.a.3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-08a.03", - "class": "sp800-53a" - } - ], - "prose": "an incident response plan is developed that provides a high-level approach for how the incident response capability fits into the overall organization;", - "links": [ - { - "href": "#ir-8_smt.a.3", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-8_obj.a.4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-08a.04", - "class": "sp800-53a" - } - ], - "prose": "an incident response plan is developed that meets the unique requirements of the organization with regard to mission, size, structure, and functions;", - "links": [ - { - "href": "#ir-8_smt.a.4", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-8_obj.a.5", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-08a.05", - "class": "sp800-53a" - } - ], - "prose": "an incident response plan is developed that defines reportable incidents;", - "links": [ - { - "href": "#ir-8_smt.a.5", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-8_obj.a.6", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-08a.06", - "class": "sp800-53a" - } - ], - "prose": "an incident response plan is developed that provides metrics for measuring the incident response capability within the organization;", - "links": [ - { - "href": "#ir-8_smt.a.6", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-8_obj.a.7", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-08a.07", - "class": "sp800-53a" - } - ], - "prose": "an incident response plan is developed that defines the resources and management support needed to effectively maintain and mature an incident response capability;", - "links": [ - { - "href": "#ir-8_smt.a.7", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-8_obj.a.8", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-08a.08", - "class": "sp800-53a" - } - ], - "prose": "an incident response plan is developed that addresses the sharing of incident information;", - "links": [ - { - "href": "#ir-8_smt.a.8", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-8_obj.a.9", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-08a.09", - "class": "sp800-53a" - } - ], - "prose": "an incident response plan is developed that is reviewed and approved by {{ insert: param, ir-08_odp.01 }} {{ insert: param, ir-08_odp.02 }};", - "links": [ - { - "href": "#ir-8_smt.a.9", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-8_obj.a.10", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-08a.10", - "class": "sp800-53a" - } - ], - "prose": "an incident response plan is developed that explicitly designates responsibility for incident response to {{ insert: param, ir-08_odp.03 }}.", - "links": [ - { - "href": "#ir-8_smt.a.10", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-8_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-8_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-08b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-8_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-08b.[01]", - "class": "sp800-53a" - } - ], - "prose": "copies of the incident response plan are distributed to {{ insert: param, ir-08_odp.04 }};", - "links": [ - { - "href": "#ir-8_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-8_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-08b.[02]", - "class": "sp800-53a" - } - ], - "prose": "copies of the incident response plan are distributed to {{ insert: param, ir-08_odp.05 }};", - "links": [ - { - "href": "#ir-8_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-8_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-8_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-08c.", - "class": "sp800-53a" - } - ], - "prose": "the incident response plan is updated to address system and organizational changes or problems encountered during plan implementation, execution, or testing;", - "links": [ - { - "href": "#ir-8_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-8_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-08d.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-8_obj.d-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-08d.[01]", - "class": "sp800-53a" - } - ], - "prose": "incident response plan changes are communicated to {{ insert: param, ir-08_odp.06 }};", - "links": [ - { - "href": "#ir-8_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-8_obj.d-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-08d.[02]", - "class": "sp800-53a" - } - ], - "prose": "incident response plan changes are communicated to {{ insert: param, ir-08_odp.07 }};", - "links": [ - { - "href": "#ir-8_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-8_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-8_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-08e.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-8_obj.e-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-08e.[01]", - "class": "sp800-53a" - } - ], - "prose": "the incident response plan is protected from unauthorized disclosure;", - "links": [ - { - "href": "#ir-8_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-8_obj.e-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-08e.[02]", - "class": "sp800-53a" - } - ], - "prose": "the incident response plan is protected from unauthorized modification.", - "links": [ - { - "href": "#ir-8_smt.e", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-8_smt.e", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-08-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing incident response planning\n\nincident response plan\n\nsystem security plan\n\nprivacy plan\n\nrecords of incident response plan reviews and approvals\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-08-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident response planning responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "ir-8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IR-08-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational incident response plan and related organizational processes" - } - ] - } - ] - }, - { - "id": "ir-9", - "class": "SP800-53", - "title": "Information Spillage Response", - "params": [ - { - "id": "ir-09_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ir-9_prm_1" - }, - { - "name": "label", - "value": "IR-09_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles assigned the responsibility for responding to information spills is/are defined;" - } - ] - }, - { - "id": "ir-09_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ir-9_prm_2" - }, - { - "name": "label", - "value": "IR-09_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to be alerted of the information spill using a method of communication not associated with the spill is/are defined;" - } - ] - }, - { - "id": "ir-09_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ir-9_prm_3" - }, - { - "name": "label", - "value": "IR-09_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "actions", - "guidelines": [ - { - "prose": "actions to be performed are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IR-09", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-9" - }, - { - "name": "label", - "value": "IR-09", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-09" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#ir-6", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-26", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-27", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-7", - "rel": "related" - }, - { - "href": "#ra-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "ir-9_smt", - "name": "statement", - "prose": "Respond to information spills by:", - "parts": [ - { - "id": "ir-9_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Assigning {{ insert: param, ir-09_odp.01 }} with responsibility for responding to information spills;" - }, - { - "id": "ir-9_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Identifying the specific information involved in the system contamination;" - }, - { - "id": "ir-9_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Alerting {{ insert: param, ir-09_odp.02 }} of the information spill using a method of communication not associated with the spill;" - }, - { - "id": "ir-9_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Isolating the contaminated system or system component;" - }, - { - "id": "ir-9_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Eradicating the information from the contaminated system or component;" - }, - { - "id": "ir-9_smt.f", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "f." - } - ], - "prose": "Identifying other systems or system components that may have been subsequently contaminated; and" - }, - { - "id": "ir-9_smt.g", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "g." - } - ], - "prose": "Performing the following additional actions: {{ insert: param, ir-09_odp.03 }}." - } - ] - }, - { - "id": "ir-9_gdn", - "name": "guidance", - "prose": "Information spillage refers to instances where information is placed on systems that are not authorized to process such information. Information spills occur when information that is thought to be a certain classification or impact level is transmitted to a system and subsequently is determined to be of a higher classification or impact level. At that point, corrective action is required. The nature of the response is based on the classification or impact level of the spilled information, the security capabilities of the system, the specific nature of the contaminated storage media, and the access authorizations of individuals with authorized access to the contaminated system. The methods used to communicate information about the spill after the fact do not involve methods directly associated with the actual spill to minimize the risk of further spreading the contamination before such contamination is isolated and eradicated." - }, - { - "id": "ir-9_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "IR-09", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ir-9_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-09a.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ir-09_odp.01 }} is/are assigned the responsibility to respond to information spills;", - "links": [ - { - "href": "#ir-9_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-9_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-09b.", - "class": "sp800-53a" - } - ], - "prose": "the specific information involved in the system contamination is identified in response to information spills;", - "links": [ - { - "href": "#ir-9_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-9_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-09c.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ir-09_odp.02 }} is/are alerted of the information spill using a method of communication not associated with the spill;", - "links": [ - { - "href": "#ir-9_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-9_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-09d.", - "class": "sp800-53a" - } - ], - "prose": "the contaminated system or system component is isolated in response to information spills;", - "links": [ - { - "href": "#ir-9_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-9_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-09e.", - "class": "sp800-53a" - } - ], - "prose": "the information is eradicated from the contaminated system or component in response to information spills;", - "links": [ - { - "href": "#ir-9_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-9_obj.f", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-09f.", - "class": "sp800-53a" - } - ], - "prose": "other systems or system components that may have been subsequently contaminated are identified in response to information spills;", - "links": [ - { - "href": "#ir-9_smt.f", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-9_obj.g", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-09g.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ir-09_odp.03 }} are performed in response to information spills.", - "links": [ - { - "href": "#ir-9_smt.g", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ir-9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-9_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-09-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing information spillage\n\nincident response plan\n\nsystem security plan\n\nrecords of information spillage alerts/notifications\n\nlist of personnel who should receive alerts of information spillage\n\nlist of actions to be performed regarding information spillage\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-9_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-09-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident response responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ir-9_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IR-09-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for information spillage response\n\nmechanisms supporting and/or implementing information spillage response actions and related communications" - } - ] - } - ], - "controls": [ - { - "id": "ir-9.2", - "class": "SP800-53-enhancement", - "title": "Training", - "params": [ - { - "id": "ir-09.02_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ir-9.2_prm_1" - }, - { - "name": "label", - "value": "IR-09(02)_ODP", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "frequency at which to provide information spillage response training is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IR-09(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-9(2)" - }, - { - "name": "label", - "value": "IR-09(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-09.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ir-9", - "rel": "required" - }, - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#cp-3", - "rel": "related" - }, - { - "href": "#ir-2", - "rel": "related" - } - ], - "parts": [ - { - "id": "ir-9.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Provide information spillage response training {{ insert: param, ir-09.02_odp }}." - }, - { - "id": "ir-9.2_gdn", - "name": "guidance", - "prose": "Organizations establish requirements for responding to information spillage incidents in incident response plans. Incident response training on a regular basis helps to ensure that organizational personnel understand their individual responsibilities and what specific actions to take when spillage incidents occur." - }, - { - "id": "ir-9.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-09(02)", - "class": "sp800-53a" - } - ], - "prose": "information spillage response training is provided {{ insert: param, ir-09.02_odp }}.", - "links": [ - { - "href": "#ir-9.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-9.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-09(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing information spillage response training\n\ninformation spillage response training curriculum\n\ninformation spillage response training materials\n\nincident response plan\n\nsystem security plan\n\ninformation spillage response training records\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-9.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-09(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident response training responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "ir-9.3", - "class": "SP800-53-enhancement", - "title": "Post-spill Operations", - "params": [ - { - "id": "ir-09.03_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ir-9.3_prm_1" - }, - { - "name": "label", - "value": "IR-09(03)_ODP", - "class": "sp800-53a" - } - ], - "label": "procedures", - "guidelines": [ - { - "prose": "procedures to be implemented to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IR-09(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-9(3)" - }, - { - "name": "label", - "value": "IR-09(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-09.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ir-9", - "rel": "required" - } - ], - "parts": [ - { - "id": "ir-9.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement the following procedures to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions: {{ insert: param, ir-09.03_odp }}." - }, - { - "id": "ir-9.3_gdn", - "name": "guidance", - "prose": "Corrective actions for systems contaminated due to information spillages may be time-consuming. Personnel may not have access to the contaminated systems while corrective actions are being taken, which may potentially affect their ability to conduct organizational business." - }, - { - "id": "ir-9.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-09(03)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ir-09.03_odp }} are implemented to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions.", - "links": [ - { - "href": "#ir-9.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-9.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-09(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing incident response\n\nprocedures addressing information spillage\n\nincident response plan\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-9.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-09(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident response responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ir-9.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IR-09(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for post-spill operations" - } - ] - } - ] - }, - { - "id": "ir-9.4", - "class": "SP800-53-enhancement", - "title": "Exposure to Unauthorized Personnel", - "params": [ - { - "id": "ir-09.04_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ir-9.4_prm_1" - }, - { - "name": "label", - "value": "IR-09(04)_ODP", - "class": "sp800-53a" - } - ], - "label": "controls", - "guidelines": [ - { - "prose": "controls employed for personnel exposed to information not within assigned access authorizations are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "IR-09(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "IR-9(4)" - }, - { - "name": "label", - "value": "IR-09(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ir-09.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ir-9", - "rel": "required" - } - ], - "parts": [ - { - "id": "ir-9.4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Employ the following controls for personnel exposed to information not within assigned access authorizations: {{ insert: param, ir-09.04_odp }}." - }, - { - "id": "ir-9.4_gdn", - "name": "guidance", - "prose": "Controls include ensuring that personnel who are exposed to spilled information are made aware of the laws, executive orders, directives, regulations, policies, standards, and guidelines regarding the information and the restrictions imposed based on exposure to such information." - }, - { - "id": "ir-9.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "IR-09(04)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ir-09.04_odp }} are employed for personnel exposed to information not within assigned access authorizations.", - "links": [ - { - "href": "#ir-9.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ir-9.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "IR-09(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Incident response policy\n\nprocedures addressing incident response\n\nprocedures addressing information spillage\n\nincident response plan\n\nsystem security plan\n\nsecurity safeguards regarding information spillage/exposure to unauthorized personnel\n\nother relevant documents or records" - } - ] - }, - { - "id": "ir-9.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "IR-09(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with incident response responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ir-9.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "IR-09(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for dealing with information exposed to unauthorized personnel\n\nmechanisms supporting and/or implementing safeguards for personnel exposed to information not within assigned access authorizations" - } - ] - } - ] - } - ] - } - ] - }, - { - "id": "ma", - "class": "family", - "title": "Maintenance", - "controls": [ - { - "id": "ma-1", - "class": "SP800-53", - "title": "Policy and Procedures", - "params": [ - { - "id": "ma-1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ma-01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ma-01_odp.02" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "ma-01_odp.01", - "props": [ - { - "name": "label", - "value": "MA-01_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the maintenance policy is to be disseminated is/are defined;" - } - ] - }, - { - "id": "ma-01_odp.02", - "props": [ - { - "name": "label", - "value": "MA-01_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the maintenance procedures are to be disseminated is/are defined;" - } - ] - }, - { - "id": "ma-01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ma-1_prm_2" - }, - { - "name": "label", - "value": "MA-01_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "organization-level", - "mission/business process-level", - "system-level" - ] - } - }, - { - "id": "ma-01_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "ma-1_prm_3" - }, - { - "name": "label", - "value": "MA-01_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "official", - "guidelines": [ - { - "prose": "an official to manage the maintenance policy and procedures is defined;" - } - ] - }, - { - "id": "ma-01_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "ma-1_prm_4" - }, - { - "name": "label", - "value": "MA-01_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency with which the current maintenance policy is reviewed and updated is defined;" - } - ] - }, - { - "id": "ma-01_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "ma-1_prm_5" - }, - { - "name": "label", - "value": "MA-01_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that would require the current maintenance policy to be reviewed and updated are defined;" - } - ] - }, - { - "id": "ma-01_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "ma-1_prm_6" - }, - { - "name": "label", - "value": "MA-01_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency with which the current maintenance procedures are reviewed and updated is defined;" - } - ] - }, - { - "id": "ma-01_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "ma-1_prm_7" - }, - { - "name": "label", - "value": "MA-01_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "events", - "constraints": [ - { - "description": "significant changes" - } - ], - "guidelines": [ - { - "prose": "events that would require the maintenance procedures to be reviewed and updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "MA-01", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MA-1" - }, - { - "name": "label", - "value": "MA-01", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ma-01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#c7ac44e8-10db-4b64-b2b9-9e32ec1efed0", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#4c0ec2ee-a0d6-428a-9043-4504bc3ade6f", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "ma-1_smt", - "name": "statement", - "parts": [ - { - "id": "ma-1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, a policy that addresses Maintenance MUST be associated with MA-1 part a.", - "class": "policy" - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, at least one procedure that addresses Maintenance MUST be associated with MA-1 part a.", - "class": "procedure" - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, document, and disseminate to {{ insert: param, ma-1_prm_1 }}:", - "parts": [ - { - "id": "ma-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, ma-01_odp.03 }} maintenance policy that:", - "parts": [ - { - "id": "ma-1_smt.a.1.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "ma-1_smt.a.1.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and" - } - ] - }, - { - "id": "ma-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the maintenance policy and the associated maintenance controls;" - } - ] - }, - { - "id": "ma-1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Designate an {{ insert: param, ma-01_odp.04 }} to manage the development, documentation, and dissemination of the maintenance policy and procedures; and" - }, - { - "id": "ma-1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the current maintenance:", - "parts": [ - { - "id": "ma-1_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Policy {{ insert: param, ma-01_odp.05 }} and following {{ insert: param, ma-01_odp.06 }} ; and" - }, - { - "id": "ma-1_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures {{ insert: param, ma-01_odp.07 }} and following {{ insert: param, ma-01_odp.08 }}." - } - ] - } - ] - }, - { - "id": "ma-1_gdn", - "name": "guidance", - "prose": "Maintenance policy and procedures address the controls in the MA family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of maintenance policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to maintenance policy and procedures assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure." - }, - { - "id": "ma-1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-01a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-01a.[01]", - "class": "sp800-53a" - } - ], - "prose": "a maintenance policy is developed and documented;", - "links": [ - { - "href": "#ma-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-01a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the maintenance policy is disseminated to {{ insert: param, ma-01_odp.01 }};", - "links": [ - { - "href": "#ma-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-1_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-01a.[03]", - "class": "sp800-53a" - } - ], - "prose": "maintenance procedures to facilitate the implementation of the maintenance policy and associated maintenance controls are developed and documented;", - "links": [ - { - "href": "#ma-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-1_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-01a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the maintenance procedures are disseminated to {{ insert: param, ma-01_odp.02 }};", - "links": [ - { - "href": "#ma-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-1_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-01a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-1_obj.a.1.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-01a.01(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-1_obj.a.1.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-01a.01(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ma-01_odp.03 }} maintenance policy addresses purpose;", - "links": [ - { - "href": "#ma-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-1_obj.a.1.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-01a.01(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ma-01_odp.03 }} maintenance policy addresses scope;", - "links": [ - { - "href": "#ma-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-1_obj.a.1.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-01a.01(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ma-01_odp.03 }} maintenance policy addresses roles;", - "links": [ - { - "href": "#ma-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-1_obj.a.1.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-01a.01(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ma-01_odp.03 }} maintenance policy addresses responsibilities;", - "links": [ - { - "href": "#ma-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-1_obj.a.1.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-01a.01(a)[05]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ma-01_odp.03 }} maintenance policy addresses management commitment;", - "links": [ - { - "href": "#ma-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-1_obj.a.1.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-01a.01(a)[06]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ma-01_odp.03 }} maintenance policy addresses coordination among organizational entities;", - "links": [ - { - "href": "#ma-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-1_obj.a.1.a-7", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-01a.01(a)[07]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ma-01_odp.03 }} maintenance policy addresses compliance;", - "links": [ - { - "href": "#ma-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-1_obj.a.1.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-01a.01(b)", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ma-01_odp.03 }} maintenance policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines;", - "links": [ - { - "href": "#ma-1_smt.a.1.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-1_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-01b.", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ma-01_odp.04 }} is designated to manage the development, documentation, and dissemination of the maintenance policy and procedures;", - "links": [ - { - "href": "#ma-1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-01c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-1_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-01c.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-1_obj.c.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-01c.01[01]", - "class": "sp800-53a" - } - ], - "prose": "the current maintenance policy is reviewed and updated {{ insert: param, ma-01_odp.05 }};", - "links": [ - { - "href": "#ma-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-1_obj.c.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-01c.01[02]", - "class": "sp800-53a" - } - ], - "prose": "the current maintenance policy is reviewed and updated following {{ insert: param, ma-01_odp.06 }};", - "links": [ - { - "href": "#ma-1_smt.c.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-1_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-01c.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-1_obj.c.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-01c.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the current maintenance procedures are reviewed and updated {{ insert: param, ma-01_odp.07 }};", - "links": [ - { - "href": "#ma-1_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-1_obj.c.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-01c.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the current maintenance procedures are reviewed and updated following {{ insert: param, ma-01_odp.08 }}.", - "links": [ - { - "href": "#ma-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-1_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MA-01-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Maintenance policy and procedures\n\nsystem security plan\n\nprivacy plan\n\norganizational risk management strategy\n\nother relevant documents or records" - } - ] - }, - { - "id": "ma-1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MA-01-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with maintenance responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - }, - { - "id": "ma-2", - "class": "SP800-53", - "title": "Controlled Maintenance", - "params": [ - { - "id": "ma-02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ma-2_prm_1" - }, - { - "name": "label", - "value": "MA-02_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles required to explicitly approve the removal of the system or system components from organizational facilities for off-site maintenance or repairs is/are defined;" - } - ] - }, - { - "id": "ma-02_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ma-2_prm_2" - }, - { - "name": "label", - "value": "MA-02_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "information", - "guidelines": [ - { - "prose": "information to be removed from associated media prior to removal from organizational facilities for off-site maintenance, repair, or replacement is defined;" - } - ] - }, - { - "id": "ma-02_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ma-2_prm_3" - }, - { - "name": "label", - "value": "MA-02_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "information", - "guidelines": [ - { - "prose": "information to be included in organizational maintenance records is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "MA-02", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MA-2" - }, - { - "name": "label", - "value": "MA-02", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ma-02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#4c501da5-9d79-4cb6-ba80-97260e1ce327", - "rel": "reference" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#mp-6", - "rel": "related" - }, - { - "href": "#pe-16", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - }, - { - "href": "#sr-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sr-4", - "rel": "related" - }, - { - "href": "#sr-11", - "rel": "related" - } - ], - "parts": [ - { - "id": "ma-2_smt", - "name": "statement", - "parts": [ - { - "id": "ma-2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Schedule, document, and review records of maintenance, repair, and replacement on system components in accordance with manufacturer or vendor specifications and/or organizational requirements;" - }, - { - "id": "ma-2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Approve and monitor all maintenance activities, whether performed on site or remotely and whether the system or system components are serviced on site or removed to another location;" - }, - { - "id": "ma-2_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Require that {{ insert: param, ma-02_odp.01 }} explicitly approve the removal of the system or system components from organizational facilities for off-site maintenance, repair, or replacement;" - }, - { - "id": "ma-2_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Sanitize equipment to remove the following information from associated media prior to removal from organizational facilities for off-site maintenance, repair, or replacement: {{ insert: param, ma-02_odp.02 }};" - }, - { - "id": "ma-2_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Check all potentially impacted controls to verify that the controls are still functioning properly following maintenance, repair, or replacement actions; and" - }, - { - "id": "ma-2_smt.f", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "f." - } - ], - "prose": "Include the following information in organizational maintenance records: {{ insert: param, ma-02_odp.03 }}." - } - ] - }, - { - "id": "ma-2_gdn", - "name": "guidance", - "prose": "Controlling system maintenance addresses the information security aspects of the system maintenance program and applies to all types of maintenance to system components conducted by local or nonlocal entities. Maintenance includes peripherals such as scanners, copiers, and printers. Information necessary for creating effective maintenance records includes the date and time of maintenance, a description of the maintenance performed, names of the individuals or group performing the maintenance, name of the escort, and system components or equipment that are removed or replaced. Organizations consider supply chain-related risks associated with replacement components for systems." - }, - { - "id": "ma-2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-02a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-2_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-02a.[01]", - "class": "sp800-53a" - } - ], - "prose": "maintenance, repair, and replacement of system components are scheduled in accordance with manufacturer or vendor specifications and/or organizational requirements;", - "links": [ - { - "href": "#ma-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-2_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-02a.[02]", - "class": "sp800-53a" - } - ], - "prose": "maintenance, repair, and replacement of system components are documented in accordance with manufacturer or vendor specifications and/or organizational requirements;", - "links": [ - { - "href": "#ma-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-2_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-02a.[03]", - "class": "sp800-53a" - } - ], - "prose": "records of maintenance, repair, and replacement of system components are reviewed in accordance with manufacturer or vendor specifications and/or organizational requirements;", - "links": [ - { - "href": "#ma-2_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-02b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-2_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-02b.[01]", - "class": "sp800-53a" - } - ], - "prose": "all maintenance activities, whether performed on site or remotely and whether the system or system components are serviced on site or removed to another location, are approved;", - "links": [ - { - "href": "#ma-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-2_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-02b.[02]", - "class": "sp800-53a" - } - ], - "prose": "all maintenance activities, whether performed on site or remotely and whether the system or system components are serviced on site or removed to another location, are monitored;", - "links": [ - { - "href": "#ma-2_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-2_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-02c.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ma-02_odp.01 }} is/are required to explicitly approve the removal of the system or system components from organizational facilities for off-site maintenance, repair, or replacement;", - "links": [ - { - "href": "#ma-2_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-2_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-02d.", - "class": "sp800-53a" - } - ], - "prose": "equipment is sanitized to remove {{ insert: param, ma-02_odp.02 }} from associated media prior to removal from organizational facilities for off-site maintenance, repair, or replacement;", - "links": [ - { - "href": "#ma-2_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-2_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-02e.", - "class": "sp800-53a" - } - ], - "prose": "all potentially impacted controls are checked to verify that the controls are still functioning properly following maintenance, repair, or replacement actions;", - "links": [ - { - "href": "#ma-2_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-2_obj.f", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-02f.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ma-02_odp.03 }} is included in organizational maintenance records.", - "links": [ - { - "href": "#ma-2_smt.f", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MA-02-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Maintenance policy\n\nprocedures addressing controlled system maintenance\n\nmaintenance records\n\nmanufacturer/vendor maintenance specifications\n\nequipment sanitization records\n\nmedia sanitization records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ma-2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MA-02-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system maintenance responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel responsible for media sanitization\n\nsystem/network administrators" - } - ] - }, - { - "id": "ma-2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MA-02-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for scheduling, performing, documenting, reviewing, approving, and monitoring maintenance and repairs for the system\n\norganizational processes for sanitizing system components\n\nmechanisms supporting and/or implementing controlled maintenance\n\nmechanisms implementing the sanitization of system components" - } - ] - } - ], - "controls": [ - { - "id": "ma-2.2", - "class": "SP800-53-enhancement", - "title": "Automated Maintenance Activities", - "params": [ - { - "id": "ma-2.2_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ma-02.02_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ma-02.02_odp.02" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ma-02.02_odp.03" - } - ], - "label": "organization-defined automated mechanisms" - }, - { - "id": "ma-02.02_odp.01", - "props": [ - { - "name": "label", - "value": "MA-02(02)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used to schedule maintenance, repair, and replacement actions for the system are defined;" - } - ] - }, - { - "id": "ma-02.02_odp.02", - "props": [ - { - "name": "label", - "value": "MA-02(02)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used to conduct maintenance, repair, and replacement actions for the system are defined;" - } - ] - }, - { - "id": "ma-02.02_odp.03", - "props": [ - { - "name": "label", - "value": "MA-02(02)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used to document maintenance, repair, and replacement actions for the system are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "MA-02(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MA-2(2)" - }, - { - "name": "label", - "value": "MA-02(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ma-02.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ma-2", - "rel": "required" - }, - { - "href": "#ma-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "ma-2.2_smt", - "name": "statement", - "parts": [ - { - "id": "ma-2.2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Schedule, conduct, and document maintenance, repair, and replacement actions for the system using {{ insert: param, ma-2.2_prm_1 }} ; and" - }, - { - "id": "ma-2.2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Produce up-to date, accurate, and complete records of all maintenance, repair, and replacement actions requested, scheduled, in process, and completed." - } - ] - }, - { - "id": "ma-2.2_gdn", - "name": "guidance", - "prose": "The use of automated mechanisms to manage and control system maintenance programs and activities helps to ensure the generation of timely, accurate, complete, and consistent maintenance records." - }, - { - "id": "ma-2.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-02(02)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-2.2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-02(02)(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-2.2_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-02(02)(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ma-02.02_odp.01 }} are used to schedule maintenance, repair, and replacement actions for the system;", - "links": [ - { - "href": "#ma-2.2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-2.2_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-02(02)(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ma-02.02_odp.02 }} are used to conduct maintenance, repair, and replacement actions for the system;", - "links": [ - { - "href": "#ma-2.2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-2.2_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-02(02)(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ma-02.02_odp.03 }} are used to document maintenance, repair, and replacement actions for the system;", - "links": [ - { - "href": "#ma-2.2_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-2.2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-2.2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-02(02)(b)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-2.2_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-02(02)(b)[01]", - "class": "sp800-53a" - } - ], - "prose": "up-to date, accurate, and complete records of all maintenance actions requested, scheduled, in process, and completed are produced.", - "links": [ - { - "href": "#ma-2.2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-2.2_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-02(02)(b)[02]", - "class": "sp800-53a" - } - ], - "prose": "up-to date, accurate, and complete records of all repair actions requested, scheduled, in process, and completed are produced.", - "links": [ - { - "href": "#ma-2.2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-2.2_obj.b-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-02(02)(b)[03]", - "class": "sp800-53a" - } - ], - "prose": "up-to date, accurate, and complete records of all replacement actions requested, scheduled, in process, and completed are produced.", - "links": [ - { - "href": "#ma-2.2_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-2.2_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-2.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-2.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MA-02(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Maintenance policy\n\nprocedures addressing controlled system maintenance\n\nautomated mechanisms supporting system maintenance activities\n\nsystem configuration settings and associated documentation\n\nmaintenance records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ma-2.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MA-02(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system maintenance responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "ma-2.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MA-02(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Automated mechanisms supporting and/or implementing controlled maintenance\n\nautomated mechanisms supporting and/or implementing the production of records of maintenance and repair actions" - } - ] - } - ] - } - ] - }, - { - "id": "ma-3", - "class": "SP800-53", - "title": "Maintenance Tools", - "params": [ - { - "id": "ma-03_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ma-3_prm_1" - }, - { - "name": "label", - "value": "MA-03_ODP", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "frequency at which to review previously approved system maintenance tools is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "MA-03", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MA-3" - }, - { - "name": "label", - "value": "MA-03", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ma-03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#a5b1d18d-e670-4586-9e6d-4a88b7ba3df6", - "rel": "reference" - }, - { - "href": "#ma-2", - "rel": "related" - }, - { - "href": "#pe-16", - "rel": "related" - } - ], - "parts": [ - { - "id": "ma-3_smt", - "name": "statement", - "parts": [ - { - "id": "ma-3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Approve, control, and monitor the use of system maintenance tools; and" - }, - { - "id": "ma-3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Review previously approved system maintenance tools {{ insert: param, ma-03_odp }}." - } - ] - }, - { - "id": "ma-3_gdn", - "name": "guidance", - "prose": "Approving, controlling, monitoring, and reviewing maintenance tools address security-related issues associated with maintenance tools that are not within system authorization boundaries and are used specifically for diagnostic and repair actions on organizational systems. Organizations have flexibility in determining roles for the approval of maintenance tools and how that approval is documented. A periodic review of maintenance tools facilitates the withdrawal of approval for outdated, unsupported, irrelevant, or no-longer-used tools. Maintenance tools can include hardware, software, and firmware items and may be pre-installed, brought in with maintenance personnel on media, cloud-based, or downloaded from a website. Such tools can be vehicles for transporting malicious code, either intentionally or unintentionally, into a facility and subsequently into systems. Maintenance tools can include hardware and software diagnostic test equipment and packet sniffers. The hardware and software components that support maintenance and are a part of the system (including the software implementing utilities such as \"ping,\" \"ls,\" \"ipconfig,\" or the hardware and software implementing the monitoring port of an Ethernet switch) are not addressed by maintenance tools." - }, - { - "id": "ma-3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-03a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-3_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-03a.[01]", - "class": "sp800-53a" - } - ], - "prose": "the use of system maintenance tools is approved;", - "links": [ - { - "href": "#ma-3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-3_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-03a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the use of system maintenance tools is controlled;", - "links": [ - { - "href": "#ma-3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-3_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-03a.[03]", - "class": "sp800-53a" - } - ], - "prose": "the use of system maintenance tools is monitored;", - "links": [ - { - "href": "#ma-3_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-03b.", - "class": "sp800-53a" - } - ], - "prose": "previously approved system maintenance tools are reviewed {{ insert: param, ma-03_odp }}.", - "links": [ - { - "href": "#ma-3_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MA-03-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Maintenance policy\n\nprocedures addressing system maintenance tools\n\nsystem maintenance tools and associated documentation\n\nmaintenance records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ma-3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MA-03-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system maintenance responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ma-3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MA-03-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for approving, controlling, and monitoring maintenance tools\n\nmechanisms supporting and/or implementing the approval, control, and/or monitoring of maintenance tools" - } - ] - } - ], - "controls": [ - { - "id": "ma-3.1", - "class": "SP800-53-enhancement", - "title": "Inspect Tools", - "props": [ - { - "name": "label", - "value": "MA-03(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MA-3(1)" - }, - { - "name": "label", - "value": "MA-03(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ma-03.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ma-3", - "rel": "required" - }, - { - "href": "#si-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "ma-3.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Inspect the maintenance tools used by maintenance personnel for improper or unauthorized modifications." - }, - { - "id": "ma-3.1_gdn", - "name": "guidance", - "prose": "Maintenance tools can be directly brought into a facility by maintenance personnel or downloaded from a vendor’s website. If, upon inspection of the maintenance tools, organizations determine that the tools have been modified in an improper manner or the tools contain malicious code, the incident is handled consistent with organizational policies and procedures for incident handling." - }, - { - "id": "ma-3.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-03(01)", - "class": "sp800-53a" - } - ], - "prose": "maintenance tools used by maintenance personnel are inspected for improper or unauthorized modifications.", - "links": [ - { - "href": "#ma-3.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-3.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MA-03(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Maintenance policy\n\nprocedures addressing system maintenance tools\n\nsystem maintenance tools and associated documentation\n\nmaintenance tool inspection records\n\nmaintenance records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ma-3.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MA-03(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system maintenance responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ma-3.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MA-03(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for inspecting maintenance tools\n\nmechanisms supporting and/or implementing the inspection of maintenance tools" - } - ] - } - ] - }, - { - "id": "ma-3.2", - "class": "SP800-53-enhancement", - "title": "Inspect Media", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "MA-03(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MA-3(2)" - }, - { - "name": "label", - "value": "MA-03(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ma-03.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ma-3", - "rel": "required" - }, - { - "href": "#si-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "ma-3.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Check media containing diagnostic and test programs for malicious code before the media are used in the system." - }, - { - "id": "ma-3.2_gdn", - "name": "guidance", - "prose": "If, upon inspection of media containing maintenance, diagnostic, and test programs, organizations determine that the media contains malicious code, the incident is handled consistent with organizational incident handling policies and procedures." - }, - { - "id": "ma-3.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-03(02)", - "class": "sp800-53a" - } - ], - "prose": "media containing diagnostic and test programs are checked for malicious code before the media are used in the system.", - "links": [ - { - "href": "#ma-3.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-3.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MA-03(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Maintenance policy\n\nprocedures addressing system maintenance tools\n\nsystem maintenance tools and associated documentation\n\nmaintenance records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ma-3.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MA-03(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system maintenance responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ma-3.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MA-03(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational process for inspecting media for malicious code\n\nmechanisms supporting and/or implementing the inspection of media used for maintenance" - } - ] - } - ] - }, - { - "id": "ma-3.3", - "class": "SP800-53-enhancement", - "title": "Prevent Unauthorized Removal", - "params": [ - { - "id": "ma-03.03_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ma-3.3_prm_1" - }, - { - "name": "label", - "value": "MA-03(03)_ODP", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "constraints": [ - { - "description": "the information owner" - } - ], - "guidelines": [ - { - "prose": "personnel or roles who can authorize removal of equipment from the facility is/are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "MA-03(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MA-3(3)" - }, - { - "name": "label", - "value": "MA-03(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ma-03.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ma-3", - "rel": "required" - }, - { - "href": "#mp-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "ma-3.3_smt", - "name": "statement", - "prose": "Prevent the removal of maintenance equipment containing organizational information by:", - "parts": [ - { - "id": "ma-3.3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Verifying that there is no organizational information contained on the equipment;" - }, - { - "id": "ma-3.3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Sanitizing or destroying the equipment;" - }, - { - "id": "ma-3.3_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Retaining the equipment within the facility; or" - }, - { - "id": "ma-3.3_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(d)" - } - ], - "prose": "Obtaining an exemption from {{ insert: param, ma-03.03_odp }} explicitly authorizing removal of the equipment from the facility." - } - ] - }, - { - "id": "ma-3.3_gdn", - "name": "guidance", - "prose": "Organizational information includes all information owned by organizations and any information provided to organizations for which the organizations serve as information stewards." - }, - { - "id": "ma-3.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-03(03)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-3.3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-03(03)(a)", - "class": "sp800-53a" - } - ], - "prose": "the removal of maintenance equipment containing organizational information is prevented by verifying that there is no organizational information contained on the equipment; or", - "links": [ - { - "href": "#ma-3.3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-3.3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-03(03)(b)", - "class": "sp800-53a" - } - ], - "prose": "the removal of maintenance equipment containing organizational information is prevented by sanitizing or destroying the equipment; or", - "links": [ - { - "href": "#ma-3.3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-3.3_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-03(03)(c)", - "class": "sp800-53a" - } - ], - "prose": "the removal of maintenance equipment containing organizational information is prevented by retaining the equipment within the facility; or", - "links": [ - { - "href": "#ma-3.3_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-3.3_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-03(03)(d)", - "class": "sp800-53a" - } - ], - "prose": "the removal of maintenance equipment containing organizational information is prevented by obtaining an exemption from {{ insert: param, ma-03.03_odp }} explicitly authorizing removal of the equipment from the facility.", - "links": [ - { - "href": "#ma-3.3_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-3.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-3.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MA-03(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Maintenance policy\n\nprocedures addressing system maintenance tools\n\nsystem maintenance tools and associated documentation\n\nmaintenance records\n\nequipment sanitization records\n\nmedia sanitization records\n\nexemptions for equipment removal\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ma-3.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MA-03(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system maintenance responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel responsible for media sanitization" - } - ] - }, - { - "id": "ma-3.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MA-03(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational process for preventing unauthorized removal of information\n\nmechanisms supporting media sanitization or destruction of equipment\n\nmechanisms supporting verification of media sanitization" - } - ] - } - ] - } - ] - }, - { - "id": "ma-4", - "class": "SP800-53", - "title": "Nonlocal Maintenance", - "props": [ - { - "name": "label", - "value": "MA-04", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MA-4" - }, - { - "name": "label", - "value": "MA-04", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ma-04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#678e3d6c-150b-4393-aec5-6e3481eb1e00", - "rel": "reference" - }, - { - "href": "#736d6310-e403-4b57-a79d-9967970c66d7", - "rel": "reference" - }, - { - "href": "#7ba1d91c-3934-4d5a-8532-b32f864ad34c", - "rel": "reference" - }, - { - "href": "#737513fa-6758-403f-831d-5ddab5e23cb3", - "rel": "reference" - }, - { - "href": "#a5b1d18d-e670-4586-9e6d-4a88b7ba3df6", - "rel": "reference" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-3", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "#ma-2", - "rel": "related" - }, - { - "href": "#ma-5", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-10", - "rel": "related" - } - ], - "parts": [ - { - "id": "ma-4_smt", - "name": "statement", - "parts": [ - { - "id": "ma-4_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Approve and monitor nonlocal maintenance and diagnostic activities;" - }, - { - "id": "ma-4_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Allow the use of nonlocal maintenance and diagnostic tools only as consistent with organizational policy and documented in the security plan for the system;" - }, - { - "id": "ma-4_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Employ strong authentication in the establishment of nonlocal maintenance and diagnostic sessions;" - }, - { - "id": "ma-4_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Maintain records for nonlocal maintenance and diagnostic activities; and" - }, - { - "id": "ma-4_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Terminate session and network connections when nonlocal maintenance is completed." - } - ] - }, - { - "id": "ma-4_gdn", - "name": "guidance", - "prose": "Nonlocal maintenance and diagnostic activities are conducted by individuals who communicate through either an external or internal network. Local maintenance and diagnostic activities are carried out by individuals who are physically present at the system location and not communicating across a network connection. Authentication techniques used to establish nonlocal maintenance and diagnostic sessions reflect the network access requirements in [IA-2](#ia-2) . Strong authentication requires authenticators that are resistant to replay attacks and employ multi-factor authentication. Strong authenticators include PKI where certificates are stored on a token protected by a password, passphrase, or biometric. Enforcing requirements in [MA-4](#ma-4) is accomplished, in part, by other controls. [SP 800-63B](#e59c5a7c-8b1f-49ca-8de0-6ee0882180ce) provides additional guidance on strong authentication and authenticators." - }, - { - "id": "ma-4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-04", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-4_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-04a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-4_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-04a.[01]", - "class": "sp800-53a" - } - ], - "prose": "nonlocal maintenance and diagnostic activities are approved;", - "links": [ - { - "href": "#ma-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-4_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-04a.[02]", - "class": "sp800-53a" - } - ], - "prose": "nonlocal maintenance and diagnostic activities are monitored;", - "links": [ - { - "href": "#ma-4_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-4_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-04b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-4_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-04b.[01]", - "class": "sp800-53a" - } - ], - "prose": "the use of nonlocal maintenance and diagnostic tools are allowed only as consistent with organizational policy;", - "links": [ - { - "href": "#ma-4_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-4_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-04b.[02]", - "class": "sp800-53a" - } - ], - "prose": "the use of nonlocal maintenance and diagnostic tools are documented in the security plan for the system;", - "links": [ - { - "href": "#ma-4_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-4_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-4_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-04c.", - "class": "sp800-53a" - } - ], - "prose": "strong authentication is employed in the establishment of nonlocal maintenance and diagnostic sessions;", - "links": [ - { - "href": "#ma-4_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-4_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-04d.", - "class": "sp800-53a" - } - ], - "prose": "records for nonlocal maintenance and diagnostic activities are maintained;", - "links": [ - { - "href": "#ma-4_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-4_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-04e.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-4_obj.e-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-04e.[01]", - "class": "sp800-53a" - } - ], - "prose": "session connections are terminated when nonlocal maintenance is completed;", - "links": [ - { - "href": "#ma-4_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-4_obj.e-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-04e.[02]", - "class": "sp800-53a" - } - ], - "prose": "network connections are terminated when nonlocal maintenance is completed.", - "links": [ - { - "href": "#ma-4_smt.e", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-4_smt.e", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MA-04-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Maintenance policy\n\nprocedures addressing nonlocal system maintenance\n\nremote access policy\n\nremote access procedures\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nmaintenance records\n\nrecords of remote access\n\ndiagnostic records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ma-4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MA-04-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system maintenance responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "ma-4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MA-04-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for managing nonlocal maintenance\n\nmechanisms implementing, supporting, and/or managing nonlocal maintenance\n\nmechanisms for strong authentication of nonlocal maintenance diagnostic sessions\n\nmechanisms for terminating nonlocal maintenance sessions and network connections" - } - ] - } - ], - "controls": [ - { - "id": "ma-4.3", - "class": "SP800-53-enhancement", - "title": "Comparable Security and Sanitization", - "props": [ - { - "name": "label", - "value": "MA-04(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MA-4(3)" - }, - { - "name": "label", - "value": "MA-04(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ma-04.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ma-4", - "rel": "required" - }, - { - "href": "#mp-6", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "ma-4.3_smt", - "name": "statement", - "parts": [ - { - "id": "ma-4.3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Require that nonlocal maintenance and diagnostic services be performed from a system that implements a security capability comparable to the capability implemented on the system being serviced; or" - }, - { - "id": "ma-4.3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Remove the component to be serviced from the system prior to nonlocal maintenance or diagnostic services; sanitize the component (for organizational information); and after the service is performed, inspect and sanitize the component (for potentially malicious software) before reconnecting the component to the system." - } - ] - }, - { - "id": "ma-4.3_gdn", - "name": "guidance", - "prose": "Comparable security capability on systems, diagnostic tools, and equipment providing maintenance services implies that the implemented controls on those systems, tools, and equipment are at least as comprehensive as the controls on the system being serviced." - }, - { - "id": "ma-4.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-04(03)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-4.3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-04(03)(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-4.3_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-04(03)(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "nonlocal maintenance services are required to be performed from a system that implements a security capability comparable to the capability implemented on the system being serviced;", - "links": [ - { - "href": "#ma-4.3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-4.3_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-04(03)(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "nonlocal diagnostic services are required to be performed from a system that implements a security capability comparable to the capability implemented on the system being serviced; or", - "links": [ - { - "href": "#ma-4.3_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-4.3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-4.3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-04(03)(b)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-4.3_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-04(03)(b)[01]", - "class": "sp800-53a" - } - ], - "prose": "the component to be serviced is removed from the system prior to nonlocal maintenance or diagnostic services;", - "links": [ - { - "href": "#ma-4.3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-4.3_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-04(03)(b)[02]", - "class": "sp800-53a" - } - ], - "prose": "the component to be serviced is sanitized (for organizational information);", - "links": [ - { - "href": "#ma-4.3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-4.3_obj.b-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-04(03)(b)[03]", - "class": "sp800-53a" - } - ], - "prose": "the component is inspected and sanitized (for potentially malicious software) after the service is performed and before reconnecting the component to the system.", - "links": [ - { - "href": "#ma-4.3_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-4.3_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-4.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-4.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MA-04(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Maintenance policy\n\nprocedures addressing nonlocal system maintenance\n\nservice provider contracts and/or service-level agreements\n\nmaintenance records\n\ninspection records\n\naudit records\n\nequipment sanitization records\n\nmedia sanitization records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ma-4.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MA-04(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system maintenance responsibilities\n\nsystem maintenance provider\n\norganizational personnel with information security responsibilities\n\norganizational personnel responsible for media sanitization\n\nsystem/network administrators" - } - ] - }, - { - "id": "ma-4.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MA-04(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for comparable security and sanitization for nonlocal maintenance\n\norganizational processes for the removal, sanitization, and inspection of components serviced via nonlocal maintenance\n\nmechanisms supporting and/or implementing component sanitization and inspection" - } - ] - } - ] - } - ] - }, - { - "id": "ma-5", - "class": "SP800-53", - "title": "Maintenance Personnel", - "props": [ - { - "name": "label", - "value": "MA-05", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MA-5" - }, - { - "name": "label", - "value": "MA-05", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ma-05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-5", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#ps-7", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "ma-5_smt", - "name": "statement", - "parts": [ - { - "id": "ma-5_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Establish a process for maintenance personnel authorization and maintain a list of authorized maintenance organizations or personnel;" - }, - { - "id": "ma-5_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Verify that non-escorted personnel performing maintenance on the system possess the required access authorizations; and" - }, - { - "id": "ma-5_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Designate organizational personnel with required access authorizations and technical competence to supervise the maintenance activities of personnel who do not possess the required access authorizations." - } - ] - }, - { - "id": "ma-5_gdn", - "name": "guidance", - "prose": "Maintenance personnel refers to individuals who perform hardware or software maintenance on organizational systems, while [PE-2](#pe-2) addresses physical access for individuals whose maintenance duties place them within the physical protection perimeter of the systems. Technical competence of supervising individuals relates to the maintenance performed on the systems, while having required access authorizations refers to maintenance on and near the systems. Individuals not previously identified as authorized maintenance personnel—such as information technology manufacturers, vendors, systems integrators, and consultants—may require privileged access to organizational systems, such as when they are required to conduct maintenance activities with little or no notice. Based on organizational assessments of risk, organizations may issue temporary credentials to these individuals. Temporary credentials may be for one-time use or for very limited time periods." - }, - { - "id": "ma-5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-05", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-5_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-05a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-5_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-05a.[01]", - "class": "sp800-53a" - } - ], - "prose": "a process for maintenance personnel authorization is established;", - "links": [ - { - "href": "#ma-5_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-5_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-05a.[02]", - "class": "sp800-53a" - } - ], - "prose": "a list of authorized maintenance organizations or personnel is maintained;", - "links": [ - { - "href": "#ma-5_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-5_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-5_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-05b.", - "class": "sp800-53a" - } - ], - "prose": "non-escorted personnel performing maintenance on the system possess the required access authorizations;", - "links": [ - { - "href": "#ma-5_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-5_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-05c.", - "class": "sp800-53a" - } - ], - "prose": "organizational personnel with required access authorizations and technical competence is/are designated to supervise the maintenance activities of personnel who do not possess the required access authorizations.", - "links": [ - { - "href": "#ma-5_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MA-05-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Maintenance policy\n\nprocedures addressing maintenance personnel\n\nservice provider contracts\n\nservice-level agreements\n\nlist of authorized personnel\n\nmaintenance records\n\naccess control records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ma-5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MA-05-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system maintenance responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ma-5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MA-05-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for authorizing and managing maintenance personnel\n\nmechanisms supporting and/or implementing authorization of maintenance personnel" - } - ] - } - ], - "controls": [ - { - "id": "ma-5.1", - "class": "SP800-53-enhancement", - "title": "Individuals Without Appropriate Access", - "params": [ - { - "id": "ma-05.01_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ma-5.1_prm_1" - }, - { - "name": "label", - "value": "MA-05(01)_ODP", - "class": "sp800-53a" - } - ], - "label": "alternate controls", - "guidelines": [ - { - "prose": "alternate controls to be developed and implemented in the event that a system component cannot be sanitized, removed, or disconnected from the system are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "MA-05(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MA-5(1)" - }, - { - "name": "label", - "value": "MA-05(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ma-05.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ma-5", - "rel": "required" - }, - { - "href": "#mp-6", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - } - ], - "parts": [ - { - "id": "ma-5.1_smt", - "name": "statement", - "parts": [ - { - "id": "ma-5.1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Implement procedures for the use of maintenance personnel that lack appropriate security clearances or are not U.S. citizens, that include the following requirements:", - "parts": [ - { - "id": "ma-5.1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "(1)" - } - ], - "prose": "Maintenance personnel who do not have needed access authorizations, clearances, or formal access approvals are escorted and supervised during the performance of maintenance and diagnostic activities on the system by approved organizational personnel who are fully cleared, have appropriate access authorizations, and are technically qualified; and" - }, - { - "id": "ma-5.1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "(2)" - } - ], - "prose": "Prior to initiating maintenance or diagnostic activities by personnel who do not have needed access authorizations, clearances or formal access approvals, all volatile information storage components within the system are sanitized and all nonvolatile storage media are removed or physically disconnected from the system and secured; and" - } - ] - }, - { - "id": "ma-5.1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Develop and implement {{ insert: param, ma-05.01_odp }} in the event a system component cannot be sanitized, removed, or disconnected from the system." - } - ] - }, - { - "id": "ma-5.1_gdn", - "name": "guidance", - "prose": "Procedures for individuals who lack appropriate security clearances or who are not U.S. citizens are intended to deny visual and electronic access to classified or controlled unclassified information contained on organizational systems. Procedures for the use of maintenance personnel can be documented in security plans for the systems." - }, - { - "id": "ma-5.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-05(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-5.1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MA-05(01)(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ma-5.1_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-05(01)(a)(01)", - "class": "sp800-53a" - } - ], - "prose": "procedures for the use of maintenance personnel who lack appropriate security clearances or are not U.S. citizens are implemented and include approved organizational personnel who are fully cleared, have appropriate access authorizations, and are technically qualified escorting and supervising maintenance personnel without the needed access authorization during the performance of maintenance and diagnostic activities;", - "links": [ - { - "href": "#ma-5.1_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-5.1_obj.a.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-05(01)(a)(02)", - "class": "sp800-53a" - } - ], - "prose": "procedures for the use of maintenance personnel who lack appropriate security clearances or are not U.S. citizens are implemented and include all volatile information storage components within the system being sanitized and all non-volatile storage media being removed or physically disconnected from the system and secured prior to initiating maintenance or diagnostic activities;", - "links": [ - { - "href": "#ma-5.1_smt.a.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-5.1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-5.1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-05(01)(b)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ma-05.01_odp }} are developed and implemented in the event that a system cannot be sanitized, removed, or disconnected from the system.", - "links": [ - { - "href": "#ma-5.1_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ma-5.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-5.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MA-05(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Maintenance policy\n\nprocedures addressing maintenance personnel\n\nsystem media protection policy\n\nphysical and environmental protection policy\n\nlist of maintenance personnel requiring escort/supervision\n\nmaintenance records\n\naccess control records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ma-5.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MA-05(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system maintenance responsibilities\n\norganizational personnel with personnel security responsibilities\n\norganizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel responsible for media sanitization\n\nsystem/network administrators" - } - ] - }, - { - "id": "ma-5.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MA-05(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for managing maintenance personnel without appropriate access\n\nmechanisms supporting and/or implementing alternative security safeguards\n\nmechanisms supporting and/or implementing information storage component sanitization" - } - ] - } - ] - } - ] - }, - { - "id": "ma-6", - "class": "SP800-53", - "title": "Timely Maintenance", - "params": [ - { - "id": "ma-06_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ma-6_prm_1" - }, - { - "name": "label", - "value": "MA-06_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "system components", - "guidelines": [ - { - "prose": "system components for which maintenance support and/or spare parts are obtained are defined;" - } - ] - }, - { - "id": "ma-06_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ma-6_prm_2" - }, - { - "name": "label", - "value": "MA-06_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "a timeframe to support advertised uptime and availability" - } - ], - "guidelines": [ - { - "prose": "time period within which maintenance support and/or spare parts are to be obtained after a failure are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "MA-06", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MA-6" - }, - { - "name": "label", - "value": "MA-06", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ma-06" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - }, - { - "href": "#ra-7", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#si-13", - "rel": "related" - }, - { - "href": "#sr-2", - "rel": "related" - }, - { - "href": "#sr-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sr-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "ma-6_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Obtain maintenance support and/or spare parts for {{ insert: param, ma-06_odp.01 }} within {{ insert: param, ma-06_odp.02 }} of failure." - }, - { - "id": "ma-6_gdn", - "name": "guidance", - "prose": "Organizations specify the system components that result in increased risk to organizational operations and assets, individuals, other organizations, or the Nation when the functionality provided by those components is not operational. Organizational actions to obtain maintenance support include having appropriate contracts in place." - }, - { - "id": "ma-6_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MA-06", - "class": "sp800-53a" - } - ], - "prose": "maintenance support and/or spare parts are obtained for {{ insert: param, ma-06_odp.01 }} within {{ insert: param, ma-06_odp.02 }} of failure.", - "links": [ - { - "href": "#ma-6_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ma-6_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MA-06-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Maintenance policy\n\nprocedures addressing system maintenance\n\nservice provider contracts\n\nservice-level agreements\n\ninventory and availability of spare parts\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ma-6_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MA-06-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system maintenance responsibilities\n\norganizational personnel with acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "ma-6_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MA-06-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for ensuring timely maintenance" - } - ] - } - ] - } - ] - }, - { - "id": "mp", - "class": "family", - "title": "Media Protection", - "controls": [ - { - "id": "mp-1", - "class": "SP800-53", - "title": "Policy and Procedures", - "params": [ - { - "id": "mp-1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-01_odp.02" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "mp-01_odp.01", - "props": [ - { - "name": "label", - "value": "MP-01_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the media protection policy is to be disseminated is/are defined;" - } - ] - }, - { - "id": "mp-01_odp.02", - "props": [ - { - "name": "label", - "value": "MP-01_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the media protection procedures are to be disseminated is/are defined;" - } - ] - }, - { - "id": "mp-01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "mp-1_prm_2" - }, - { - "name": "label", - "value": "MP-01_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "organization-level", - "mission/business process-level", - "system-level" - ] - } - }, - { - "id": "mp-01_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "mp-1_prm_3" - }, - { - "name": "label", - "value": "MP-01_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "official", - "guidelines": [ - { - "prose": "an official to manage the media protection policy and procedures is defined;" - } - ] - }, - { - "id": "mp-01_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "mp-1_prm_4" - }, - { - "name": "label", - "value": "MP-01_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency with which the current media protection policy is reviewed and updated is defined;" - } - ] - }, - { - "id": "mp-01_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "mp-1_prm_5" - }, - { - "name": "label", - "value": "MP-01_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that would require the current media protection policy to be reviewed and updated are defined;" - } - ] - }, - { - "id": "mp-01_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "mp-1_prm_6" - }, - { - "name": "label", - "value": "MP-01_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency with which the current media protection procedures are reviewed and updated is defined;" - } - ] - }, - { - "id": "mp-01_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "mp-1_prm_7" - }, - { - "name": "label", - "value": "MP-01_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "events", - "constraints": [ - { - "description": "significant changes" - } - ], - "guidelines": [ - { - "prose": "events that would require media protection procedures to be reviewed and updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "MP-01", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MP-1" - }, - { - "name": "label", - "value": "MP-01", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "mp-01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#c7ac44e8-10db-4b64-b2b9-9e32ec1efed0", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#4c0ec2ee-a0d6-428a-9043-4504bc3ade6f", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "mp-1_smt", - "name": "statement", - "parts": [ - { - "id": "mp-1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, a policy that addresses Media Protection MUST be associated with MP-1 part a.", - "class": "policy" - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, at least one procedure that addresses Media Protection MUST be associated with MP-1 part a.", - "class": "procedure" - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, document, and disseminate to {{ insert: param, mp-1_prm_1 }}:", - "parts": [ - { - "id": "mp-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, mp-01_odp.03 }} media protection policy that:", - "parts": [ - { - "id": "mp-1_smt.a.1.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "mp-1_smt.a.1.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and" - } - ] - }, - { - "id": "mp-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the media protection policy and the associated media protection controls;" - } - ] - }, - { - "id": "mp-1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Designate an {{ insert: param, mp-01_odp.04 }} to manage the development, documentation, and dissemination of the media protection policy and procedures; and" - }, - { - "id": "mp-1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the current media protection:", - "parts": [ - { - "id": "mp-1_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Policy {{ insert: param, mp-01_odp.05 }} and following {{ insert: param, mp-01_odp.06 }} ; and" - }, - { - "id": "mp-1_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures {{ insert: param, mp-01_odp.07 }} and following {{ insert: param, mp-01_odp.08 }}." - } - ] - } - ] - }, - { - "id": "mp-1_gdn", - "name": "guidance", - "prose": "Media protection policy and procedures address the controls in the MP family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of media protection policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to media protection policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure." - }, - { - "id": "mp-1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "mp-1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-01a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "mp-1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-01a.[01]", - "class": "sp800-53a" - } - ], - "prose": "a media protection policy is developed and documented;", - "links": [ - { - "href": "#mp-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-01a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the media protection policy is disseminated to {{ insert: param, mp-01_odp.01 }};", - "links": [ - { - "href": "#mp-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-1_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-01a.[03]", - "class": "sp800-53a" - } - ], - "prose": "media protection procedures to facilitate the implementation of the media protection policy and associated media protection controls are developed and documented;", - "links": [ - { - "href": "#mp-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-1_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-01a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the media protection procedures are disseminated to {{ insert: param, mp-01_odp.02 }};", - "links": [ - { - "href": "#mp-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-1_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-01a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "mp-1_obj.a.1.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-01a.01(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "mp-1_obj.a.1.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-01a.01(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, mp-01_odp.03 }} media protection policy addresses purpose;", - "links": [ - { - "href": "#mp-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-1_obj.a.1.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-01a.01(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, mp-01_odp.03 }} media protection policy addresses scope;", - "links": [ - { - "href": "#mp-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-1_obj.a.1.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-01a.01(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, mp-01_odp.03 }} media protection policy addresses roles;", - "links": [ - { - "href": "#mp-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-1_obj.a.1.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-01a.01(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, mp-01_odp.03 }} media protection policy addresses responsibilities;", - "links": [ - { - "href": "#mp-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-1_obj.a.1.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-01a.01(a)[05]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, mp-01_odp.03 }} media protection policy addresses management commitment;", - "links": [ - { - "href": "#mp-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-1_obj.a.1.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-01a.01(a)[06]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, mp-01_odp.03 }} media protection policy addresses coordination among organizational entities;", - "links": [ - { - "href": "#mp-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-1_obj.a.1.a-7", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-01a.01(a)[07]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, mp-01_odp.03 }} media protection policy compliance;", - "links": [ - { - "href": "#mp-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#mp-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-1_obj.a.1.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-01a.01(b)", - "class": "sp800-53a" - } - ], - "prose": "the media protection policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines;", - "links": [ - { - "href": "#mp-1_smt.a.1.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#mp-1_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#mp-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-01b.", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, mp-01_odp.04 }} is designated to manage the development, documentation, and dissemination of the media protection policy and procedures.", - "links": [ - { - "href": "#mp-1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-01c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "mp-1_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-01c.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "mp-1_obj.c.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-01c.01[01]", - "class": "sp800-53a" - } - ], - "prose": "the current media protection policy is reviewed and updated {{ insert: param, mp-01_odp.05 }};", - "links": [ - { - "href": "#mp-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-1_obj.c.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-01c.01[02]", - "class": "sp800-53a" - } - ], - "prose": "the current media protection policy is reviewed and updated following {{ insert: param, mp-01_odp.06 }};", - "links": [ - { - "href": "#mp-1_smt.c.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#mp-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-1_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-01c.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "mp-1_obj.c.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-01c.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the current media protection procedures are reviewed and updated {{ insert: param, mp-01_odp.07 }};", - "links": [ - { - "href": "#mp-1_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-1_obj.c.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-01c.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the current media protection procedures are reviewed and updated following {{ insert: param, mp-01_odp.08 }}.", - "links": [ - { - "href": "#mp-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#mp-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#mp-1_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#mp-1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MP-01-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Media protection policy and procedures\n\norganizational risk management strategy\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "mp-1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MP-01-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with media protection responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - }, - { - "id": "mp-2", - "class": "SP800-53", - "title": "Media Access", - "params": [ - { - "id": "mp-2_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-02_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-02_odp.03" - } - ], - "label": "organization-defined types of digital and/or non-digital media" - }, - { - "id": "mp-2_prm_2", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-02_odp.02" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-02_odp.04" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "mp-02_odp.01", - "props": [ - { - "name": "label", - "value": "MP-02_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "types of digital media", - "constraints": [ - { - "description": "all types of digital and/or non-digital media containing sensitive information" - } - ], - "guidelines": [ - { - "prose": "types of digital media to which access is restricted are defined;" - } - ] - }, - { - "id": "mp-02_odp.02", - "props": [ - { - "name": "label", - "value": "MP-02_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles authorized to access digital media is/are defined;" - } - ] - }, - { - "id": "mp-02_odp.03", - "props": [ - { - "name": "label", - "value": "MP-02_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "types of non-digital media", - "constraints": [ - { - "description": "all types of digital and/or non-digital media containing sensitive information" - } - ], - "guidelines": [ - { - "prose": "types of non-digital media to which access is restricted are defined;" - } - ] - }, - { - "id": "mp-02_odp.04", - "props": [ - { - "name": "label", - "value": "MP-02_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles authorized to access non-digital media is/are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "MP-02", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MP-2" - }, - { - "name": "label", - "value": "MP-02", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "mp-02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#628d22a1-6a11-4784-bc59-5cd9497b5445", - "rel": "reference" - }, - { - "href": "#22f2d4f0-4365-4e88-a30d-275c1f5473ea", - "rel": "reference" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#cp-10", - "rel": "related" - }, - { - "href": "#ma-5", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#mp-6", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-34", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "mp-2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Restrict access to {{ insert: param, mp-2_prm_1 }} to {{ insert: param, mp-2_prm_2 }}." - }, - { - "id": "mp-2_gdn", - "name": "guidance", - "prose": "System media includes digital and non-digital media. Digital media includes flash drives, diskettes, magnetic tapes, external or removable hard disk drives (e.g., solid state, magnetic), compact discs, and digital versatile discs. Non-digital media includes paper and microfilm. Denying access to patient medical records in a community hospital unless the individuals seeking access to such records are authorized healthcare providers is an example of restricting access to non-digital media. Limiting access to the design specifications stored on compact discs in the media library to individuals on the system development team is an example of restricting access to digital media." - }, - { - "id": "mp-2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "mp-2_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-02[01]", - "class": "sp800-53a" - } - ], - "prose": "access to {{ insert: param, mp-02_odp.01 }} is restricted to {{ insert: param, mp-02_odp.02 }};", - "links": [ - { - "href": "#mp-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-2_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-02[02]", - "class": "sp800-53a" - } - ], - "prose": "access to {{ insert: param, mp-02_odp.03 }} is restricted to {{ insert: param, mp-02_odp.04 }}.", - "links": [ - { - "href": "#mp-2_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#mp-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MP-02-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System media protection policy\n\nprocedures addressing media access restrictions\n\naccess control policy and procedures\n\nphysical and environmental protection policy and procedures\n\nmedia storage facilities\n\naccess control records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "mp-2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MP-02-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system media protection responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "mp-2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MP-02-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for restricting information media\n\nmechanisms supporting and/or implementing media access restrictions" - } - ] - } - ] - }, - { - "id": "mp-3", - "class": "SP800-53", - "title": "Media Marking", - "params": [ - { - "id": "mp-03_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "mp-3_prm_1" - }, - { - "name": "alt-label", - "value": "types of system media", - "class": "sp800-53" - }, - { - "name": "label", - "value": "MP-03_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "types of media exempted from marking", - "constraints": [ - { - "description": "no removable media types" - } - ], - "guidelines": [ - { - "prose": "types of system media exempt from marking when remaining in controlled areas are defined;" - } - ] - }, - { - "id": "mp-03_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "mp-3_prm_2" - }, - { - "name": "label", - "value": "MP-03_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "controlled areas", - "constraints": [ - { - "description": "organization-defined security safeguards not applicable" - } - ], - "guidelines": [ - { - "prose": "controlled areas where media is exempt from marking are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "MP-03", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MP-3" - }, - { - "name": "label", - "value": "MP-03", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "mp-03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#34a5571f-e252-4309-a8a1-2fdb2faefbcd", - "rel": "reference" - }, - { - "href": "#91f992fb-f668-4c91-a50f-0f05b95ccee3", - "rel": "reference" - }, - { - "href": "#628d22a1-6a11-4784-bc59-5cd9497b5445", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ac-16", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pe-22", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "mp-3_smt", - "name": "statement", - "parts": [ - { - "id": "mp-3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Mark system media indicating the distribution limitations, handling caveats, and applicable security markings (if any) of the information; and" - }, - { - "id": "mp-3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Exempt {{ insert: param, mp-03_odp.01 }} from marking if the media remain within {{ insert: param, mp-03_odp.02 }}." - } - ] - }, - { - "id": "mp-3_gdn", - "name": "guidance", - "prose": "Security marking refers to the application or use of human-readable security attributes. Digital media includes diskettes, magnetic tapes, external or removable hard disk drives (e.g., solid state, magnetic), flash drives, compact discs, and digital versatile discs. Non-digital media includes paper and microfilm. Controlled unclassified information is defined by the National Archives and Records Administration along with the appropriate safeguarding and dissemination requirements for such information and is codified in [32 CFR 2002](#91f992fb-f668-4c91-a50f-0f05b95ccee3) . Security markings are generally not required for media that contains information determined by organizations to be in the public domain or to be publicly releasable. Some organizations may require markings for public information indicating that the information is publicly releasable. System media marking reflects applicable laws, executive orders, directives, policies, regulations, standards, and guidelines." - }, - { - "id": "mp-3_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "MP-3 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "mp-3_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(b) Guidance:" - } - ], - "prose": "Second parameter not-applicable" - } - ] - }, - { - "id": "mp-3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "mp-3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-03a.", - "class": "sp800-53a" - } - ], - "prose": "system media is marked to indicate distribution limitations, handling caveats, and applicable security markings (if any) of the information;", - "links": [ - { - "href": "#mp-3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-03b.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, mp-03_odp.01 }} remain within {{ insert: param, mp-03_odp.02 }}.", - "links": [ - { - "href": "#mp-3_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#mp-3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MP-03-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System media protection policy\n\nprocedures addressing media marking\n\nphysical and environmental protection policy and procedures\n\nlist of system media marking security attributes\n\ndesignated controlled areas\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "mp-3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MP-03-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system media protection and marking responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "mp-3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MP-03-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for marking information media\n\nmechanisms supporting and/or implementing media marking" - } - ] - } - ] - }, - { - "id": "mp-4", - "class": "SP800-53", - "title": "Media Storage", - "params": [ - { - "id": "mp-4_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-04_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-04_odp.02" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-04_odp.03" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-04_odp.04" - } - ], - "label": "organization-defined types of digital and/or non-digital media" - }, - { - "id": "mp-4_prm_2", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-04_odp.05" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-04_odp.06" - } - ], - "label": "organization-defined controlled areas" - }, - { - "id": "mp-04_odp.01", - "props": [ - { - "name": "label", - "value": "MP-04_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "types of digital media", - "constraints": [ - { - "description": "all types of digital and non-digital media with sensitive information" - } - ], - "guidelines": [ - { - "prose": "types of digital media to be physically controlled are defined (if selected);" - } - ] - }, - { - "id": "mp-04_odp.02", - "props": [ - { - "name": "label", - "value": "MP-04_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "types of non-digital media", - "constraints": [ - { - "description": "all types of digital and non-digital media with sensitive information" - } - ], - "guidelines": [ - { - "prose": "types of non-digital media to be physically controlled are defined (if selected);" - } - ] - }, - { - "id": "mp-04_odp.03", - "props": [ - { - "name": "label", - "value": "MP-04_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "types of digital media", - "constraints": [ - { - "description": "all types of digital and non-digital media with sensitive information" - } - ], - "guidelines": [ - { - "prose": "types of digital media to be securely stored are defined (if selected);" - } - ] - }, - { - "id": "mp-04_odp.04", - "props": [ - { - "name": "label", - "value": "MP-04_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "types of non-digital media", - "constraints": [ - { - "description": "all types of digital and non-digital media with sensitive information" - } - ], - "guidelines": [ - { - "prose": "types of non-digital media to be securely stored are defined (if selected);" - } - ] - }, - { - "id": "mp-04_odp.05", - "props": [ - { - "name": "label", - "value": "MP-04_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "controlled areas", - "constraints": [ - { - "description": "see additional FedRAMP requirements and guidance" - } - ], - "guidelines": [ - { - "prose": "controlled areas within which to securely store digital media are defined;" - } - ] - }, - { - "id": "mp-04_odp.06", - "props": [ - { - "name": "label", - "value": "MP-04_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "controlled areas", - "constraints": [ - { - "description": "see additional FedRAMP requirements and guidance" - } - ], - "guidelines": [ - { - "prose": "controlled areas within which to securely store non-digital media are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "MP-04", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MP-4" - }, - { - "name": "label", - "value": "MP-04", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "mp-04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#628d22a1-6a11-4784-bc59-5cd9497b5445", - "rel": "reference" - }, - { - "href": "#20957dbb-6a1e-40a2-b38a-66f67d33ac2e", - "rel": "reference" - }, - { - "href": "#0d083d8a-5cc6-46f1-8d79-3081d42bcb75", - "rel": "reference" - }, - { - "href": "#eef62b16-c796-4554-955c-505824135b8a", - "rel": "reference" - }, - { - "href": "#110e26af-4765-49e1-8740-6750f83fcda1", - "rel": "reference" - }, - { - "href": "#e7942589-e267-4a5a-a3d9-f39a7aae81f0", - "rel": "reference" - }, - { - "href": "#8306620b-1920-4d73-8b21-12008528595f", - "rel": "reference" - }, - { - "href": "#22f2d4f0-4365-4e88-a30d-275c1f5473ea", - "rel": "reference" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-6", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#cp-10", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-7", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#sc-28", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-34", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "mp-4_smt", - "name": "statement", - "parts": [ - { - "id": "mp-4_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Physically control and securely store {{ insert: param, mp-4_prm_1 }} within {{ insert: param, mp-4_prm_2 }} ; and" - }, - { - "id": "mp-4_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Protect system media types defined in MP-4a until the media are destroyed or sanitized using approved equipment, techniques, and procedures." - } - ] - }, - { - "id": "mp-4_gdn", - "name": "guidance", - "prose": "System media includes digital and non-digital media. Digital media includes flash drives, diskettes, magnetic tapes, external or removable hard disk drives (e.g., solid state, magnetic), compact discs, and digital versatile discs. Non-digital media includes paper and microfilm. Physically controlling stored media includes conducting inventories, ensuring procedures are in place to allow individuals to check out and return media to the library, and maintaining accountability for stored media. Secure storage includes a locked drawer, desk, or cabinet or a controlled media library. The type of media storage is commensurate with the security category or classification of the information on the media. Controlled areas are spaces that provide physical and procedural controls to meet the requirements established for protecting information and systems. Fewer controls may be needed for media that contains information determined to be in the public domain, publicly releasable, or have limited adverse impacts on organizations, operations, or individuals if accessed by other than authorized personnel. In these situations, physical access controls provide adequate protection." - }, - { - "id": "mp-4_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "MP-4 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "mp-4_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(a) Requirement:" - } - ], - "prose": "The service provider defines controlled areas within facilities where the information and information system reside." - } - ] - }, - { - "id": "mp-4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-04", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "mp-4_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-04a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "mp-4_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-04a.[01]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, mp-04_odp.01 }} are physically controlled;", - "links": [ - { - "href": "#mp-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-4_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-04a.[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, mp-04_odp.02 }} are physically controlled;", - "links": [ - { - "href": "#mp-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-4_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-04a.[03]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, mp-04_odp.03 }} are securely stored within {{ insert: param, mp-04_odp.05 }};", - "links": [ - { - "href": "#mp-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-4_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-04a.[04]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, mp-04_odp.04 }} are securely stored within {{ insert: param, mp-04_odp.06 }};", - "links": [ - { - "href": "#mp-4_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#mp-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-4_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-04b.", - "class": "sp800-53a" - } - ], - "prose": "system media types (defined in MP-04_ODP\\[01\\], MP-04_ODP\\[02\\], MP-04_ODP\\[03\\], MP-04_ODP\\[04\\]) are protected until the media are destroyed or sanitized using approved equipment, techniques, and procedures.", - "links": [ - { - "href": "#mp-4_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#mp-4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MP-04-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System media protection policy\n\nprocedures addressing media storage\n\nphysical and environmental protection policy and procedures\n\naccess control policy and procedures\n\nsystem media\n\ndesignated controlled areas\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "mp-4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MP-04-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system media protection and storage responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "mp-4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MP-04-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for storing information media\n\nmechanisms supporting and/or implementing secure media storage/media protection" - } - ] - } - ] - }, - { - "id": "mp-5", - "class": "SP800-53", - "title": "Media Transport", - "params": [ - { - "id": "mp-5_prm_2", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-05_odp.02" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-05_odp.03" - } - ], - "label": "organization-defined controls" - }, - { - "id": "mp-05_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "mp-5_prm_1" - }, - { - "name": "label", - "value": "MP-05_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "types of system media", - "constraints": [ - { - "description": "all media with sensitive information" - } - ], - "guidelines": [ - { - "prose": "types of system media to protect and control during transport outside of controlled areas are defined;" - } - ] - }, - { - "id": "mp-05_odp.02", - "props": [ - { - "name": "label", - "value": "MP-05_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "controls", - "constraints": [ - { - "description": "prior to leaving secure/controlled environment: for digital media, encryption in compliance with Federal requirements and utilizes FIPS validated or NSA approved cryptography (see SC-13.); for non-digital media, secured in locked container" - } - ], - "guidelines": [ - { - "prose": "controls used to protect system media outside of controlled areas are defined;" - } - ] - }, - { - "id": "mp-05_odp.03", - "props": [ - { - "name": "label", - "value": "MP-05_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "controls", - "constraints": [ - { - "description": "prior to leaving secure/controlled environment: for digital media, encryption in compliance with Federal requirements and utilizes FIPS validated or NSA approved cryptography (see SC-13.); for non-digital media, secured in locked container" - } - ], - "guidelines": [ - { - "prose": "controls used to control system media outside of controlled areas are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "MP-05", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MP-5" - }, - { - "name": "label", - "value": "MP-05", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "mp-05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#628d22a1-6a11-4784-bc59-5cd9497b5445", - "rel": "reference" - }, - { - "href": "#e72fde0b-6fc2-497e-a9db-d8fce5a11b8a", - "rel": "reference" - }, - { - "href": "#9be5d661-421f-41ad-854e-86f98b811891", - "rel": "reference" - }, - { - "href": "#ac-7", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#mp-3", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#pe-16", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#sc-28", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-34", - "rel": "related" - } - ], - "parts": [ - { - "id": "mp-5_smt", - "name": "statement", - "parts": [ - { - "id": "mp-5_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Protect and control {{ insert: param, mp-05_odp.01 }} during transport outside of controlled areas using {{ insert: param, mp-5_prm_2 }};" - }, - { - "id": "mp-5_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Maintain accountability for system media during transport outside of controlled areas;" - }, - { - "id": "mp-5_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Document activities associated with the transport of system media; and" - }, - { - "id": "mp-5_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Restrict the activities associated with the transport of system media to authorized personnel." - } - ] - }, - { - "id": "mp-5_gdn", - "name": "guidance", - "prose": "System media includes digital and non-digital media. Digital media includes flash drives, diskettes, magnetic tapes, external or removable hard disk drives (e.g., solid state and magnetic), compact discs, and digital versatile discs. Non-digital media includes microfilm and paper. Controlled areas are spaces for which organizations provide physical or procedural controls to meet requirements established for protecting information and systems. Controls to protect media during transport include cryptography and locked containers. Cryptographic mechanisms can provide confidentiality and integrity protections depending on the mechanisms implemented. Activities associated with media transport include releasing media for transport, ensuring that media enters the appropriate transport processes, and the actual transport. Authorized transport and courier personnel may include individuals external to the organization. Maintaining accountability of media during transport includes restricting transport activities to authorized personnel and tracking and/or obtaining records of transport activities as the media moves through the transportation system to prevent and detect loss, destruction, or tampering. Organizations establish documentation requirements for activities associated with the transport of system media in accordance with organizational assessments of risk. Organizations maintain the flexibility to define record-keeping methods for the different types of media transport as part of a system of transport-related records." - }, - { - "id": "mp-5_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "MP-5 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "mp-5_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(a) Requirement:" - } - ], - "prose": "The service provider defines security measures to protect digital and non-digital media in transport. The security measures are approved and accepted by the AO." - } - ] - }, - { - "id": "mp-5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-05", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "mp-5_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-05a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "mp-5_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-05a.[01]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, mp-05_odp.01 }} are protected during transport outside of controlled areas using {{ insert: param, mp-05_odp.02 }};", - "links": [ - { - "href": "#mp-5_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-5_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-05a.[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, mp-05_odp.01 }} are controlled during transport outside of controlled areas using {{ insert: param, mp-05_odp.03 }};", - "links": [ - { - "href": "#mp-5_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#mp-5_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-5_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-05b.", - "class": "sp800-53a" - } - ], - "prose": "accountability for system media is maintained during transport outside of controlled areas;", - "links": [ - { - "href": "#mp-5_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-5_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-05c.", - "class": "sp800-53a" - } - ], - "prose": "activities associated with the transport of system media are documented;", - "links": [ - { - "href": "#mp-5_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-5_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-05d.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "mp-5_obj.d-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-05d.[01]", - "class": "sp800-53a" - } - ], - "prose": "personnel authorized to conduct media transport activities is/are identified;", - "links": [ - { - "href": "#mp-5_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-5_obj.d-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-05d.[02]", - "class": "sp800-53a" - } - ], - "prose": "activities associated with the transport of system media are restricted to identified authorized personnel.", - "links": [ - { - "href": "#mp-5_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#mp-5_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#mp-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MP-05-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System media protection policy\n\nprocedures addressing media storage\n\nphysical and environmental protection policy and procedures\n\naccess control policy and procedures\n\nauthorized personnel list\n\nsystem media\n\ndesignated controlled areas\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "mp-5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MP-05-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system media protection and storage responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "mp-5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MP-05-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for storing information media\n\nmechanisms supporting and/or implementing media storage/media protection" - } - ] - } - ] - }, - { - "id": "mp-6", - "class": "SP800-53", - "title": "Media Sanitization", - "params": [ - { - "id": "mp-6_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-06_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-06_odp.02" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-06_odp.03" - } - ], - "label": "organization-defined system media" - }, - { - "id": "mp-6_prm_2", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-06_odp.04" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-06_odp.05" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-06_odp.06" - } - ], - "label": "organization-defined sanitization techniques and procedures" - }, - { - "id": "mp-06_odp.01", - "props": [ - { - "name": "label", - "value": "MP-06_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "system media", - "constraints": [ - { - "description": "techniques and procedures IAW NIST SP 800-88 Section 4: Reuse and Disposal of Storage Media and Hardware" - } - ], - "guidelines": [ - { - "prose": "system media to be sanitized prior to disposal is defined;" - } - ] - }, - { - "id": "mp-06_odp.02", - "props": [ - { - "name": "label", - "value": "MP-06_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "system media", - "constraints": [ - { - "description": "techniques and procedures IAW NIST SP 800-88 Section 4: Reuse and Disposal of Storage Media and Hardware" - } - ], - "guidelines": [ - { - "prose": "system media to be sanitized prior to release from organizational control is defined;" - } - ] - }, - { - "id": "mp-06_odp.03", - "props": [ - { - "name": "label", - "value": "MP-06_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "system media", - "constraints": [ - { - "description": "techniques and procedures IAW NIST SP 800-88 Section 4: Reuse and Disposal of Storage Media and Hardware" - } - ], - "guidelines": [ - { - "prose": "system media to be sanitized prior to release for reuse is defined;" - } - ] - }, - { - "id": "mp-06_odp.04", - "props": [ - { - "name": "label", - "value": "MP-06_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "sanitization techniques and procedures", - "guidelines": [ - { - "prose": "sanitization techniques and procedures to be used for sanitization prior to disposal are defined;" - } - ] - }, - { - "id": "mp-06_odp.05", - "props": [ - { - "name": "label", - "value": "MP-06_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "sanitization techniques and procedures", - "guidelines": [ - { - "prose": "sanitization techniques and procedures to be used for sanitization prior to release from organizational control are defined;" - } - ] - }, - { - "id": "mp-06_odp.06", - "props": [ - { - "name": "label", - "value": "MP-06_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "sanitization techniques and procedures", - "guidelines": [ - { - "prose": "sanitization techniques and procedures to be used for sanitization prior to release for reuse are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "MP-06", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MP-6" - }, - { - "name": "label", - "value": "MP-06", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "mp-06" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#91f992fb-f668-4c91-a50f-0f05b95ccee3", - "rel": "reference" - }, - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#c28ae9a8-1121-42a9-a85e-00cfcc9b9a94", - "rel": "reference" - }, - { - "href": "#628d22a1-6a11-4784-bc59-5cd9497b5445", - "rel": "reference" - }, - { - "href": "#e72fde0b-6fc2-497e-a9db-d8fce5a11b8a", - "rel": "reference" - }, - { - "href": "#9be5d661-421f-41ad-854e-86f98b811891", - "rel": "reference" - }, - { - "href": "#a5b1d18d-e670-4586-9e6d-4a88b7ba3df6", - "rel": "reference" - }, - { - "href": "#0f66be67-85e7-4ca6-bd19-39453e9f4394", - "rel": "reference" - }, - { - "href": "#4c501da5-9d79-4cb6-ba80-97260e1ce327", - "rel": "reference" - }, - { - "href": "#df9f87e9-71e7-4c74-9ac3-3cabd4e92f21", - "rel": "reference" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-7", - "rel": "related" - }, - { - "href": "#au-11", - "rel": "related" - }, - { - "href": "#ma-2", - "rel": "related" - }, - { - "href": "#ma-3", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#ma-5", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-22", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#si-18", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#si-19", - "rel": "related" - }, - { - "href": "#sr-11", - "rel": "related" - } - ], - "parts": [ - { - "id": "mp-6_smt", - "name": "statement", - "parts": [ - { - "id": "mp-6_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Sanitize {{ insert: param, mp-6_prm_1 }} prior to disposal, release out of organizational control, or release for reuse using {{ insert: param, mp-6_prm_2 }} ; and" - }, - { - "id": "mp-6_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Employ sanitization mechanisms with the strength and integrity commensurate with the security category or classification of the information." - } - ] - }, - { - "id": "mp-6_gdn", - "name": "guidance", - "prose": "Media sanitization applies to all digital and non-digital system media subject to disposal or reuse, whether or not the media is considered removable. Examples include digital media in scanners, copiers, printers, notebook computers, workstations, network components, mobile devices, and non-digital media (e.g., paper and microfilm). The sanitization process removes information from system media such that the information cannot be retrieved or reconstructed. Sanitization techniques—including clearing, purging, cryptographic erase, de-identification of personally identifiable information, and destruction—prevent the disclosure of information to unauthorized individuals when such media is reused or released for disposal. Organizations determine the appropriate sanitization methods, recognizing that destruction is sometimes necessary when other methods cannot be applied to media requiring sanitization. Organizations use discretion on the employment of approved sanitization techniques and procedures for media that contains information deemed to be in the public domain or publicly releasable or information deemed to have no adverse impact on organizations or individuals if released for reuse or disposal. Sanitization of non-digital media includes destruction, removing a classified appendix from an otherwise unclassified document, or redacting selected sections or words from a document by obscuring the redacted sections or words in a manner equivalent in effectiveness to removing them from the document. NSA standards and policies control the sanitization process for media that contains classified information. NARA policies control the sanitization process for controlled unclassified information." - }, - { - "id": "mp-6_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-06", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "mp-6_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-06a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "mp-6_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-06a.[01]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, mp-06_odp.01 }} is sanitized using {{ insert: param, mp-06_odp.04 }} prior to disposal;", - "links": [ - { - "href": "#mp-6_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-6_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-06a.[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, mp-06_odp.02 }} is sanitized using {{ insert: param, mp-06_odp.05 }} prior to release from organizational control;", - "links": [ - { - "href": "#mp-6_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-6_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-06a.[03]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, mp-06_odp.03 }} is sanitized using {{ insert: param, mp-06_odp.06 }} prior to release for reuse;", - "links": [ - { - "href": "#mp-6_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#mp-6_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-6_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-06b.", - "class": "sp800-53a" - } - ], - "prose": "sanitization mechanisms with strength and integrity commensurate with the security category or classification of the information are employed.", - "links": [ - { - "href": "#mp-6_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#mp-6_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-6_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MP-06-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System media protection policy\n\nprocedures addressing media sanitization and disposal\n\napplicable federal standards and policies addressing media sanitization policy\n\nmedia sanitization records\n\nsystem audit records\n\nsystem design documentation\n\nrecords retention and disposition policy\n\nrecords retention and disposition procedures\n\nsystem configuration settings and associated documentation\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "mp-6_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MP-06-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with media sanitization responsibilities\n\norganizational personnel with records retention and disposition responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "mp-6_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MP-06-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for media sanitization\n\nmechanisms supporting and/or implementing media sanitization" - } - ] - } - ], - "controls": [ - { - "id": "mp-6.1", - "class": "SP800-53-enhancement", - "title": "Review, Approve, Track, Document, and Verify", - "props": [ - { - "name": "label", - "value": "MP-06(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MP-6(1)" - }, - { - "name": "label", - "value": "MP-06(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "mp-06.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#mp-6", - "rel": "required" - } - ], - "parts": [ - { - "id": "mp-6.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Review, approve, track, document, and verify media sanitization and disposal actions." - }, - { - "id": "mp-6.1_gdn", - "name": "guidance", - "prose": "Organizations review and approve media to be sanitized to ensure compliance with records retention policies. Tracking and documenting actions include listing personnel who reviewed and approved sanitization and disposal actions, types of media sanitized, files stored on the media, sanitization methods used, date and time of the sanitization actions, personnel who performed the sanitization, verification actions taken and personnel who performed the verification, and the disposal actions taken. Organizations verify that the sanitization of the media was effective prior to disposal." - }, - { - "id": "mp-6.1_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "MP-6 (1) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "mp-6.1_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Must comply with NIST SP 800-88" - } - ] - }, - { - "id": "mp-6.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-06(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "mp-6.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-06(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "media sanitization and disposal actions are reviewed;", - "links": [ - { - "href": "#mp-6.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-6.1_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-06(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "media sanitization and disposal actions are approved;", - "links": [ - { - "href": "#mp-6.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-6.1_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-06(01)[03]", - "class": "sp800-53a" - } - ], - "prose": "media sanitization and disposal actions are tracked;", - "links": [ - { - "href": "#mp-6.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-6.1_obj-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-06(01)[04]", - "class": "sp800-53a" - } - ], - "prose": "media sanitization and disposal actions are documented;", - "links": [ - { - "href": "#mp-6.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-6.1_obj-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-06(01)[05]", - "class": "sp800-53a" - } - ], - "prose": "media sanitization and disposal actions are verified.", - "links": [ - { - "href": "#mp-6.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#mp-6.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-6.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MP-06(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System media protection policy\n\nprocedures addressing media sanitization and disposal\n\nrecords retention and disposition policy\n\nrecords retention and disposition procedures\n\nmedia sanitization and disposal records\n\nreview records for media sanitization and disposal actions\n\napprovals for media sanitization and disposal actions\n\ntracking records\n\nverification records\n\nsystem audit records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "mp-6.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MP-06(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system media sanitization and disposal responsibilities\n\norganizational personnel with records retention and disposition responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "mp-6.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MP-06(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for media sanitization\n\nmechanisms supporting and/or implementing media sanitization\n\nmechanisms supporting and/or implementing verification of media sanitization" - } - ] - } - ] - }, - { - "id": "mp-6.2", - "class": "SP800-53-enhancement", - "title": "Equipment Testing", - "params": [ - { - "id": "mp-6.2_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-06.02_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "mp-06.02_odp.02" - } - ], - "label": "organization-defined frequency" - }, - { - "id": "mp-06.02_odp.01", - "props": [ - { - "name": "label", - "value": "MP-06(02)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least every six (6) months" - } - ], - "guidelines": [ - { - "prose": "frequency with which to test sanitization equipment is defined;" - } - ] - }, - { - "id": "mp-06.02_odp.02", - "props": [ - { - "name": "label", - "value": "MP-06(02)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least every six (6) months" - } - ], - "guidelines": [ - { - "prose": "frequency with which to test sanitization procedures is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "MP-06(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MP-6(2)" - }, - { - "name": "label", - "value": "MP-06(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "mp-06.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#mp-6", - "rel": "required" - } - ], - "parts": [ - { - "id": "mp-6.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Test sanitization equipment and procedures {{ insert: param, mp-6.2_prm_1 }} to ensure that the intended sanitization is being achieved." - }, - { - "id": "mp-6.2_gdn", - "name": "guidance", - "prose": "Testing of sanitization equipment and procedures may be conducted by qualified and authorized external entities, including federal agencies or external service providers." - }, - { - "id": "mp-6.2_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "MP-6 (2) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "mp-6.2_fr_smt.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Equipment and procedures may be tested or validated for effectiveness" - } - ] - }, - { - "id": "mp-6.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-06(02)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "mp-6.2_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-06(02)[01]", - "class": "sp800-53a" - } - ], - "prose": "sanitization equipment is tested {{ insert: param, mp-06.02_odp.01 }} to ensure that the intended sanitization is being achieved;", - "links": [ - { - "href": "#mp-6.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-6.2_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-06(02)[02]", - "class": "sp800-53a" - } - ], - "prose": "sanitization procedures are tested {{ insert: param, mp-06.02_odp.02 }} to ensure that the intended sanitization is being achieved.", - "links": [ - { - "href": "#mp-6.2_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#mp-6.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-6.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MP-06(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System media protection policy\n\nprocedures addressing media sanitization and disposal\n\nprocedures addressing testing of media sanitization equipment\n\nresults of media sanitization equipment and procedures testing\n\nsystem audit records\n\nrecords retention and disposition policy\n\nrecords retention and disposition procedures\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "mp-6.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MP-06(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system media sanitization responsibilities\n\norganizational personnel with records retention and disposition responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "mp-6.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MP-06(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for media sanitization\n\nautomated mechanisms supporting and/or implementing media sanitization\n\nautomated mechanisms supporting and/or implementing media sanitization procedures\n\nsanitization equipment" - } - ] - } - ] - }, - { - "id": "mp-6.3", - "class": "SP800-53-enhancement", - "title": "Nondestructive Techniques", - "params": [ - { - "id": "mp-06.03_odp", - "props": [ - { - "name": "alt-identifier", - "value": "mp-6.3_prm_1" - }, - { - "name": "alt-label", - "value": "circumstances requiring sanitization of portable storage devices", - "class": "sp800-53" - }, - { - "name": "label", - "value": "MP-06(03)_ODP", - "class": "sp800-53a" - } - ], - "label": "circumstances", - "guidelines": [ - { - "prose": "circumstances requiring sanitization of portable storage devices are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "MP-06(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MP-6(3)" - }, - { - "name": "label", - "value": "MP-06(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "mp-06.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#mp-6", - "rel": "required" - } - ], - "parts": [ - { - "id": "mp-6.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Apply nondestructive sanitization techniques to portable storage devices prior to connecting such devices to the system under the following circumstances: {{ insert: param, mp-06.03_odp }}." - }, - { - "id": "mp-6.3_gdn", - "name": "guidance", - "prose": "Portable storage devices include external or removable hard disk drives (e.g., solid state, magnetic), optical discs, magnetic or optical tapes, flash memory devices, flash memory cards, and other external or removable disks. Portable storage devices can be obtained from untrustworthy sources and contain malicious code that can be inserted into or transferred to organizational systems through USB ports or other entry portals. While scanning storage devices is recommended, sanitization provides additional assurance that such devices are free of malicious code. Organizations consider nondestructive sanitization of portable storage devices when the devices are purchased from manufacturers or vendors prior to initial use or when organizations cannot maintain a positive chain of custody for the devices." - }, - { - "id": "mp-6.3_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "MP-6 (3) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "mp-6.3_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Must comply with NIST SP 800-88" - } - ] - }, - { - "id": "mp-6.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-06(03)", - "class": "sp800-53a" - } - ], - "prose": "non-destructive sanitization techniques are applied to portable storage devices prior to connecting such devices to the system under {{ insert: param, mp-06.03_odp }}.", - "links": [ - { - "href": "#mp-6.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-6.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MP-06(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System media protection policy\n\nprocedures addressing media sanitization and disposal\n\ninformation on portable storage devices for the system\n\nlist of circumstances requiring sanitization of portable storage devices\n\nmedia sanitization records\n\naudit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "mp-6.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MP-06(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system media sanitization responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "mp-6.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MP-06(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for media sanitization of portable storage devices\n\nmechanisms supporting and/or implementing media sanitization" - } - ] - } - ] - } - ] - }, - { - "id": "mp-7", - "class": "SP800-53", - "title": "Media Use", - "params": [ - { - "id": "mp-07_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "mp-7_prm_2" - }, - { - "name": "label", - "value": "MP-07_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "types of system media", - "guidelines": [ - { - "prose": "types of system media to be restricted or prohibited from use on systems or system components are defined;" - } - ] - }, - { - "id": "mp-07_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "mp-7_prm_1" - }, - { - "name": "label", - "value": "MP-07_ODP[02]", - "class": "sp800-53a" - } - ], - "select": { - "choice": [ - "restrict", - "prohibit" - ] - } - }, - { - "id": "mp-07_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "mp-7_prm_3" - }, - { - "name": "label", - "value": "MP-07_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "systems or system components", - "guidelines": [ - { - "prose": "systems or system components on which the use of specific types of system media to be restricted or prohibited are defined;" - } - ] - }, - { - "id": "mp-07_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "mp-7_prm_4" - }, - { - "name": "label", - "value": "MP-07_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "controls", - "guidelines": [ - { - "prose": "controls to restrict or prohibit the use of specific types of system media on systems or system components are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "MP-07", - "class": "zero-padded" - }, - { - "name": "label", - "value": "MP-7" - }, - { - "name": "label", - "value": "MP-07", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "mp-07" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#628d22a1-6a11-4784-bc59-5cd9497b5445", - "rel": "reference" - }, - { - "href": "#22f2d4f0-4365-4e88-a30d-275c1f5473ea", - "rel": "reference" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#ac-20", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-12", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-34", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-41", - "rel": "related" - } - ], - "parts": [ - { - "id": "mp-7_smt", - "name": "statement", - "parts": [ - { - "id": "mp-7_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "{{ insert: param, mp-07_odp.02 }} the use of {{ insert: param, mp-07_odp.01 }} on {{ insert: param, mp-07_odp.03 }} using {{ insert: param, mp-07_odp.04 }} ; and" - }, - { - "id": "mp-7_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Prohibit the use of portable storage devices in organizational systems when such devices have no identifiable owner." - } - ] - }, - { - "id": "mp-7_gdn", - "name": "guidance", - "prose": "System media includes both digital and non-digital media. Digital media includes diskettes, magnetic tapes, flash drives, compact discs, digital versatile discs, and removable hard disk drives. Non-digital media includes paper and microfilm. Media use protections also apply to mobile devices with information storage capabilities. In contrast to [MP-2](#mp-2) , which restricts user access to media, MP-7 restricts the use of certain types of media on systems, for example, restricting or prohibiting the use of flash drives or external hard disk drives. Organizations use technical and nontechnical controls to restrict the use of system media. Organizations may restrict the use of portable storage devices, for example, by using physical cages on workstations to prohibit access to certain external ports or disabling or removing the ability to insert, read, or write to such devices. Organizations may also limit the use of portable storage devices to only approved devices, including devices provided by the organization, devices provided by other approved organizations, and devices that are not personally owned. Finally, organizations may restrict the use of portable storage devices based on the type of device, such as by prohibiting the use of writeable, portable storage devices and implementing this restriction by disabling or removing the capability to write to such devices. Requiring identifiable owners for storage devices reduces the risk of using such devices by allowing organizations to assign responsibility for addressing known vulnerabilities in the devices." - }, - { - "id": "mp-7_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "MP-07", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "mp-7_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-07a.", - "class": "sp800-53a" - } - ], - "prose": "the use of {{ insert: param, mp-07_odp.01 }} is {{ insert: param, mp-07_odp.02 }} on {{ insert: param, mp-07_odp.03 }} using {{ insert: param, mp-07_odp.04 }};", - "links": [ - { - "href": "#mp-7_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-7_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "MP-07b.", - "class": "sp800-53a" - } - ], - "prose": "the use of portable storage devices in organizational systems is prohibited when such devices have no identifiable owner.", - "links": [ - { - "href": "#mp-7_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#mp-7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "mp-7_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "MP-07-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System media protection policy\n\nsystem use policy\n\nprocedures addressing media usage restrictions\n\nrules of behavior\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\naudit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "mp-7_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "MP-07-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system media use responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "mp-7_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "MP-07-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for media use\n\nmechanisms restricting or prohibiting the use of system media on systems or system components" - } - ] - } - ] - } - ] - }, - { - "id": "pe", - "class": "family", - "title": "Physical and Environmental Protection", - "controls": [ - { - "id": "pe-1", - "class": "SP800-53", - "title": "Policy and Procedures", - "params": [ - { - "id": "pe-1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "pe-01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "pe-01_odp.02" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "pe-01_odp.01", - "props": [ - { - "name": "label", - "value": "PE-01_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the physical and environmental protection policy is to be disseminated is/are defined;" - } - ] - }, - { - "id": "pe-01_odp.02", - "props": [ - { - "name": "label", - "value": "PE-01_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the physical and environmental protection procedures are to be disseminated is/are defined;" - } - ] - }, - { - "id": "pe-01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "pe-1_prm_2" - }, - { - "name": "label", - "value": "PE-01_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "organization-level", - "mission/business process-level", - "system-level" - ] - } - }, - { - "id": "pe-01_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "pe-1_prm_3" - }, - { - "name": "label", - "value": "PE-01_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "official", - "guidelines": [ - { - "prose": "an official to manage the physical and environmental protection policy and procedures is defined;" - } - ] - }, - { - "id": "pe-01_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "pe-1_prm_4" - }, - { - "name": "label", - "value": "PE-01_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current physical and environmental protection policy is reviewed and updated is defined;" - } - ] - }, - { - "id": "pe-01_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "pe-1_prm_5" - }, - { - "name": "label", - "value": "PE-01_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that would require the current physical and environmental protection policy to be reviewed and updated are defined;" - } - ] - }, - { - "id": "pe-01_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "pe-1_prm_6" - }, - { - "name": "label", - "value": "PE-01_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current physical and environmental protection procedures are reviewed and updated is defined;" - } - ] - }, - { - "id": "pe-01_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "pe-1_prm_7" - }, - { - "name": "label", - "value": "PE-01_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "events", - "constraints": [ - { - "description": "significant changes" - } - ], - "guidelines": [ - { - "prose": "events that would require the physical and environmental protection procedures to be reviewed and updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PE-01", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-1" - }, - { - "name": "label", - "value": "PE-01", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#c7ac44e8-10db-4b64-b2b9-9e32ec1efed0", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#4c0ec2ee-a0d6-428a-9043-4504bc3ade6f", - "rel": "reference" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "pe-1_smt", - "name": "statement", - "parts": [ - { - "id": "pe-1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, a policy that addresses Physical and Environmental Protection MUST be associated with PE-1 part a.", - "class": "policy" - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, at least one procedure that addresses Physical and Environmental Protection MUST be associated with PE-1 part a.", - "class": "procedure" - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, document, and disseminate to {{ insert: param, pe-1_prm_1 }}:", - "parts": [ - { - "id": "pe-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, pe-01_odp.03 }} physical and environmental protection policy that:", - "parts": [ - { - "id": "pe-1_smt.a.1.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "pe-1_smt.a.1.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and" - } - ] - }, - { - "id": "pe-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the physical and environmental protection policy and the associated physical and environmental protection controls;" - } - ] - }, - { - "id": "pe-1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Designate an {{ insert: param, pe-01_odp.04 }} to manage the development, documentation, and dissemination of the physical and environmental protection policy and procedures; and" - }, - { - "id": "pe-1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the current physical and environmental protection:", - "parts": [ - { - "id": "pe-1_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Policy {{ insert: param, pe-01_odp.05 }} and following {{ insert: param, pe-01_odp.06 }} ; and" - }, - { - "id": "pe-1_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures {{ insert: param, pe-01_odp.07 }} and following {{ insert: param, pe-01_odp.08 }}." - } - ] - } - ] - }, - { - "id": "pe-1_gdn", - "name": "guidance", - "prose": "Physical and environmental protection policy and procedures address the controls in the PE family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of physical and environmental protection policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to physical and environmental protection policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure." - }, - { - "id": "pe-1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-01a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-01a.[01]", - "class": "sp800-53a" - } - ], - "prose": "a physical and environmental protection policy is developed and documented;", - "links": [ - { - "href": "#pe-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-01a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the physical and environmental protection policy is disseminated to {{ insert: param, pe-01_odp.01 }};", - "links": [ - { - "href": "#pe-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-1_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-01a.[03]", - "class": "sp800-53a" - } - ], - "prose": "physical and environmental protection procedures to facilitate the implementation of the physical and environmental protection policy and associated physical and environmental protection controls are developed and documented;", - "links": [ - { - "href": "#pe-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-1_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-01a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the physical and environmental protection procedures are disseminated to {{ insert: param, pe-01_odp.02 }};", - "links": [ - { - "href": "#pe-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-1_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-01a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-1_obj.a.1.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-01a.01(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-1_obj.a.1.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-01a.01(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, pe-01_odp.03 }} physical and environmental protection policy addresses purpose;", - "links": [ - { - "href": "#pe-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-1_obj.a.1.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-01a.01(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, pe-01_odp.03 }} physical and environmental protection policy addresses scope;", - "links": [ - { - "href": "#pe-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-1_obj.a.1.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-01a.01(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, pe-01_odp.03 }} physical and environmental protection policy addresses roles;", - "links": [ - { - "href": "#pe-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-1_obj.a.1.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-01a.01(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, pe-01_odp.03 }} physical and environmental protection policy addresses responsibilities;", - "links": [ - { - "href": "#pe-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-1_obj.a.1.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-01a.01(a)[05]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, pe-01_odp.03 }} physical and environmental protection policy addresses management commitment;", - "links": [ - { - "href": "#pe-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-1_obj.a.1.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-01a.01(a)[06]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, pe-01_odp.03 }} physical and environmental protection policy addresses coordination among organizational entities;", - "links": [ - { - "href": "#pe-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-1_obj.a.1.a-7", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-01a.01(a)[07]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, pe-01_odp.03 }} physical and environmental protection policy addresses compliance;", - "links": [ - { - "href": "#pe-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-1_obj.a.1.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-01a.01(b)", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, pe-01_odp.03 }} physical and environmental protection policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines;", - "links": [ - { - "href": "#pe-1_smt.a.1.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-1_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-01b.", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, pe-01_odp.04 }} is designated to manage the development, documentation, and dissemination of the physical and environmental protection policy and procedures;", - "links": [ - { - "href": "#pe-1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-01c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-1_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-01c.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-1_obj.c.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-01c.01[01]", - "class": "sp800-53a" - } - ], - "prose": "the current physical and environmental protection policy is reviewed and updated {{ insert: param, pe-01_odp.05 }};", - "links": [ - { - "href": "#pe-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-1_obj.c.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-01c.01[02]", - "class": "sp800-53a" - } - ], - "prose": "the current physical and environmental protection policy is reviewed and updated following {{ insert: param, pe-01_odp.06 }};", - "links": [ - { - "href": "#pe-1_smt.c.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-1_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-01c.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-1_obj.c.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-01c.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the current physical and environmental protection procedures are reviewed and updated {{ insert: param, pe-01_odp.07 }};", - "links": [ - { - "href": "#pe-1_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-1_obj.c.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-01c.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the current physical and environmental protection procedures are reviewed and updated following {{ insert: param, pe-01_odp.08 }}.", - "links": [ - { - "href": "#pe-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-1_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-01-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy and procedures\n\nsystem security plan\n\nprivacy plan\n\norganizational risk management strategy\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-01-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with physical and environmental protection responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - }, - { - "id": "pe-2", - "class": "SP800-53", - "title": "Physical Access Authorizations", - "params": [ - { - "id": "pe-02_odp", - "props": [ - { - "name": "alt-identifier", - "value": "pe-2_prm_1" - }, - { - "name": "label", - "value": "PE-02_ODP", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least every ninety (90) days" - } - ], - "guidelines": [ - { - "prose": "frequency at which to review the access list detailing authorized facility access by individuals is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PE-02", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-2" - }, - { - "name": "label", - "value": "PE-02", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#7ba1d91c-3934-4d5a-8532-b32f864ad34c", - "rel": "reference" - }, - { - "href": "#858705be-3c1f-48aa-a328-0ce398d95ef0", - "rel": "reference" - }, - { - "href": "#7af2e6ec-9f7e-4232-ad3f-09888eb0793a", - "rel": "reference" - }, - { - "href": "#828856bd-d7c4-427b-8b51-815517ec382d", - "rel": "reference" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ma-5", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pe-4", - "rel": "related" - }, - { - "href": "#pe-5", - "rel": "related" - }, - { - "href": "#pe-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-12", - "rel": "related" - }, - { - "href": "#ps-3", - "rel": "related" - }, - { - "href": "#ps-4", - "rel": "related" - }, - { - "href": "#ps-5", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "pe-2_smt", - "name": "statement", - "parts": [ - { - "id": "pe-2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, approve, and maintain a list of individuals with authorized access to the facility where the system resides;" - }, - { - "id": "pe-2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Issue authorization credentials for facility access;" - }, - { - "id": "pe-2_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review the access list detailing authorized facility access by individuals {{ insert: param, pe-02_odp }} ; and" - }, - { - "id": "pe-2_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Remove individuals from the facility access list when access is no longer required." - } - ] - }, - { - "id": "pe-2_gdn", - "name": "guidance", - "prose": "Physical access authorizations apply to employees and visitors. Individuals with permanent physical access authorization credentials are not considered visitors. Authorization credentials include ID badges, identification cards, and smart cards. Organizations determine the strength of authorization credentials needed consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Physical access authorizations may not be necessary to access certain areas within facilities that are designated as publicly accessible." - }, - { - "id": "pe-2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-02a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-2_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-02a.[01]", - "class": "sp800-53a" - } - ], - "prose": "a list of individuals with authorized access to the facility where the system resides has been developed;", - "links": [ - { - "href": "#pe-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-2_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-02a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the list of individuals with authorized access to the facility where the system resides has been approved;", - "links": [ - { - "href": "#pe-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-2_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-02a.[03]", - "class": "sp800-53a" - } - ], - "prose": "the list of individuals with authorized access to the facility where the system resides has been maintained;", - "links": [ - { - "href": "#pe-2_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-02b.", - "class": "sp800-53a" - } - ], - "prose": "authorization credentials are issued for facility access;", - "links": [ - { - "href": "#pe-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-2_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-02c.", - "class": "sp800-53a" - } - ], - "prose": "the access list detailing authorized facility access by individuals is reviewed {{ insert: param, pe-02_odp }};", - "links": [ - { - "href": "#pe-2_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-2_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-02d.", - "class": "sp800-53a" - } - ], - "prose": "individuals are removed from the facility access list when access is no longer required.", - "links": [ - { - "href": "#pe-2_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-02-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access authorizations\n\nauthorized personnel access list\n\nauthorization credentials\n\nphysical access list reviews\n\nphysical access termination records and associated documentation\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-02-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with physical access authorization responsibilities\n\norganizational personnel with physical access to system facility\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-02-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for physical access authorizations\n\nmechanisms supporting and/or implementing physical access authorizations" - } - ] - } - ] - }, - { - "id": "pe-3", - "class": "SP800-53", - "title": "Physical Access Control", - "params": [ - { - "id": "pe-3_prm_9", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "pe-03_odp.09" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "pe-03_odp.10" - } - ], - "label": "organization-defined frequency" - }, - { - "id": "pe-03_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "pe-3_prm_1" - }, - { - "name": "alt-label", - "value": "entry and exit points to the facility where the system resides", - "class": "sp800-53" - }, - { - "name": "label", - "value": "PE-03_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "entry and exit points", - "guidelines": [ - { - "prose": "entry and exit points to the facility in which the system resides are defined;" - } - ] - }, - { - "id": "pe-03_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "pe-3_prm_2" - }, - { - "name": "label", - "value": "PE-03_ODP[02]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "CSP defined physical access control systems/devices AND guards" - } - ] - }, - { - "id": "pe-03_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "pe-3_prm_3" - }, - { - "name": "alt-label", - "value": "physical access control systems or devices", - "class": "sp800-53" - }, - { - "name": "label", - "value": "PE-03_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "systems or devices", - "guidelines": [ - { - "prose": "physical access control systems or devices used to control ingress and egress to the facility are defined (if selected);" - } - ] - }, - { - "id": "pe-03_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "pe-3_prm_4" - }, - { - "name": "label", - "value": "PE-03_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "entry or exit points", - "guidelines": [ - { - "prose": "entry or exit points for which physical access logs are maintained are defined;" - } - ] - }, - { - "id": "pe-03_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "pe-3_prm_5" - }, - { - "name": "label", - "value": "PE-03_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "physical access controls", - "guidelines": [ - { - "prose": "physical access controls to control access to areas within the facility designated as publicly accessible are defined;" - } - ] - }, - { - "id": "pe-03_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "pe-3_prm_6" - }, - { - "name": "alt-label", - "value": "circumstances requiring visitor escorts and control of visitor activity", - "class": "sp800-53" - }, - { - "name": "label", - "value": "PE-03_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "circumstances", - "constraints": [ - { - "description": "in all circumstances within restricted access area where the information system resides" - } - ], - "guidelines": [ - { - "prose": "circumstances requiring visitor escorts and control of visitor activity are defined;" - } - ] - }, - { - "id": "pe-03_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "pe-3_prm_7" - }, - { - "name": "label", - "value": "PE-03_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "physical access devices", - "guidelines": [ - { - "prose": "physical access devices to be inventoried are defined;" - } - ] - }, - { - "id": "pe-03_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "pe-3_prm_8" - }, - { - "name": "label", - "value": "PE-03_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "frequency at which to inventory physical access devices is defined;" - } - ] - }, - { - "id": "pe-03_odp.09", - "props": [ - { - "name": "label", - "value": "PE-03_ODP[09]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually or earlier as required by a security relevant event." - } - ], - "guidelines": [ - { - "prose": "frequency at which to change combinations is defined;" - } - ] - }, - { - "id": "pe-03_odp.10", - "props": [ - { - "name": "label", - "value": "PE-03_ODP[10]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually or earlier as required by a security relevant event." - } - ], - "guidelines": [ - { - "prose": "frequency at which to change keys is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "PE-03", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-3" - }, - { - "name": "label", - "value": "PE-03", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#7ba1d91c-3934-4d5a-8532-b32f864ad34c", - "rel": "reference" - }, - { - "href": "#858705be-3c1f-48aa-a328-0ce398d95ef0", - "rel": "reference" - }, - { - "href": "#7af2e6ec-9f7e-4232-ad3f-09888eb0793a", - "rel": "reference" - }, - { - "href": "#828856bd-d7c4-427b-8b51-815517ec382d", - "rel": "reference" - }, - { - "href": "#2100332a-16a5-4598-bacf-7261baea9711", - "rel": "reference" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-13", - "rel": "related" - }, - { - "href": "#cp-10", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "#ma-5", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pe-4", - "rel": "related" - }, - { - "href": "#pe-5", - "rel": "related" - }, - { - "href": "#pe-8", - "rel": "related" - }, - { - "href": "#ps-2", - "rel": "related" - }, - { - "href": "#ps-3", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - }, - { - "href": "#ps-7", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#sc-28", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#sr-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "pe-3_smt", - "name": "statement", - "parts": [ - { - "id": "pe-3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Enforce physical access authorizations at {{ insert: param, pe-03_odp.01 }} by:", - "parts": [ - { - "id": "pe-3_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Verifying individual access authorizations before granting access to the facility; and" - }, - { - "id": "pe-3_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Controlling ingress and egress to the facility using {{ insert: param, pe-03_odp.02 }};" - } - ] - }, - { - "id": "pe-3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Maintain physical access audit logs for {{ insert: param, pe-03_odp.04 }};" - }, - { - "id": "pe-3_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Control access to areas within the facility designated as publicly accessible by implementing the following controls: {{ insert: param, pe-03_odp.05 }};" - }, - { - "id": "pe-3_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Escort visitors and control visitor activity {{ insert: param, pe-03_odp.06 }};" - }, - { - "id": "pe-3_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Secure keys, combinations, and other physical access devices;" - }, - { - "id": "pe-3_smt.f", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "f." - } - ], - "prose": "Inventory {{ insert: param, pe-03_odp.07 }} every {{ insert: param, pe-03_odp.08 }} ; and" - }, - { - "id": "pe-3_smt.g", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "g." - } - ], - "prose": "Change combinations and keys {{ insert: param, pe-3_prm_9 }} and/or when keys are lost, combinations are compromised, or when individuals possessing the keys or combinations are transferred or terminated." - } - ] - }, - { - "id": "pe-3_gdn", - "name": "guidance", - "prose": "Physical access control applies to employees and visitors. Individuals with permanent physical access authorizations are not considered visitors. Physical access controls for publicly accessible areas may include physical access control logs/records, guards, or physical access devices and barriers to prevent movement from publicly accessible areas to non-public areas. Organizations determine the types of guards needed, including professional security staff, system users, or administrative staff. Physical access devices include keys, locks, combinations, biometric readers, and card readers. Physical access control systems comply with applicable laws, executive orders, directives, policies, regulations, standards, and guidelines. Organizations have flexibility in the types of audit logs employed. Audit logs can be procedural, automated, or some combination thereof. Physical access points can include facility access points, interior access points to systems that require supplemental access controls, or both. Components of systems may be in areas designated as publicly accessible with organizations controlling access to the components." - }, - { - "id": "pe-3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-03a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-3_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-03a.01", - "class": "sp800-53a" - } - ], - "prose": "physical access authorizations are enforced at {{ insert: param, pe-03_odp.01 }} by verifying individual access authorizations before granting access to the facility;", - "links": [ - { - "href": "#pe-3_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-3_obj.a.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-03a.02", - "class": "sp800-53a" - } - ], - "prose": "physical access authorizations are enforced at {{ insert: param, pe-03_odp.01 }} by controlling ingress and egress to the facility using {{ insert: param, pe-03_odp.02 }};", - "links": [ - { - "href": "#pe-3_smt.a.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-03b.", - "class": "sp800-53a" - } - ], - "prose": "physical access audit logs are maintained for {{ insert: param, pe-03_odp.04 }};", - "links": [ - { - "href": "#pe-3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-3_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-03c.", - "class": "sp800-53a" - } - ], - "prose": "access to areas within the facility designated as publicly accessible are maintained by implementing {{ insert: param, pe-03_odp.05 }};", - "links": [ - { - "href": "#pe-3_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-3_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-03d.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-3_obj.d-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-03d.[01]", - "class": "sp800-53a" - } - ], - "prose": "visitors are escorted;", - "links": [ - { - "href": "#pe-3_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-3_obj.d-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-03d.[02]", - "class": "sp800-53a" - } - ], - "prose": "visitor activity is controlled {{ insert: param, pe-03_odp.06 }};", - "links": [ - { - "href": "#pe-3_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-3_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-3_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-03e.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-3_obj.e-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-03e.[01]", - "class": "sp800-53a" - } - ], - "prose": "keys are secured;", - "links": [ - { - "href": "#pe-3_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-3_obj.e-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-03e.[02]", - "class": "sp800-53a" - } - ], - "prose": "combinations are secured;", - "links": [ - { - "href": "#pe-3_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-3_obj.e-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-03e.[03]", - "class": "sp800-53a" - } - ], - "prose": "other physical access devices are secured;", - "links": [ - { - "href": "#pe-3_smt.e", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-3_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-3_obj.f", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-03f.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, pe-03_odp.07 }} are inventoried {{ insert: param, pe-03_odp.08 }};", - "links": [ - { - "href": "#pe-3_smt.f", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-3_obj.g", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-03g.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-3_obj.g-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-03g.[01]", - "class": "sp800-53a" - } - ], - "prose": "combinations are changed {{ insert: param, pe-03_odp.09 }} , when combinations are compromised, or when individuals possessing the combinations are transferred or terminated;", - "links": [ - { - "href": "#pe-3_smt.g", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-3_obj.g-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-03g.[02]", - "class": "sp800-53a" - } - ], - "prose": "keys are changed {{ insert: param, pe-03_odp.10 }} , when keys are lost, or when individuals possessing the keys are transferred or terminated.", - "links": [ - { - "href": "#pe-3_smt.g", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-3_smt.g", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-03-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access control\n\nphysical access control logs or records\n\ninventory records of physical access control devices\n\nsystem entry and exit points\n\nrecords of key and lock combination changes\n\nstorage locations for physical access control devices\n\nphysical access control devices\n\nlist of security safeguards controlling access to designated publicly accessible areas within facility\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-03-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-03-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for physical access control\n\nmechanisms supporting and/or implementing physical access control\n\nphysical access control devices" - } - ] - } - ], - "controls": [ - { - "id": "pe-3.1", - "class": "SP800-53-enhancement", - "title": "System Access", - "params": [ - { - "id": "pe-03.01_odp", - "props": [ - { - "name": "alt-identifier", - "value": "pe-3.1_prm_1" - }, - { - "name": "alt-label", - "value": "physical spaces containing one or more components of the system", - "class": "sp800-53" - }, - { - "name": "label", - "value": "PE-03(01)_ODP", - "class": "sp800-53a" - } - ], - "label": "physical spaces", - "guidelines": [ - { - "prose": "physical spaces containing one or more components of the system are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PE-03(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-3(1)" - }, - { - "name": "label", - "value": "PE-03(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-03.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#pe-3", - "rel": "required" - } - ], - "parts": [ - { - "id": "pe-3.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Enforce physical access authorizations to the system in addition to the physical access controls for the facility at {{ insert: param, pe-03.01_odp }}." - }, - { - "id": "pe-3.1_gdn", - "name": "guidance", - "prose": "Control of physical access to the system provides additional physical security for those areas within facilities where there is a concentration of system components." - }, - { - "id": "pe-3.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-03(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-3.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-03(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "physical access authorizations to the system are enforced;", - "links": [ - { - "href": "#pe-3.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-3.1_obj.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-03(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "physical access controls are enforced for the facility at {{ insert: param, pe-03.01_odp }}.", - "links": [ - { - "href": "#pe-3.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-3.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-3.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-03(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access control\n\nphysical access control logs or records\n\nphysical access control devices\n\naccess authorizations\n\naccess credentials\n\nsystem entry and exit points\n\nlist of areas within the facility containing concentrations of system components or system components requiring additional physical protection\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-3.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-03(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with physical access authorization responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-3.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-03(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for physical access control to the information system/components\n\nmechanisms supporting and/or implementing physical access control for facility areas containing system components" - } - ] - } - ] - } - ] - }, - { - "id": "pe-4", - "class": "SP800-53", - "title": "Access Control for Transmission", - "params": [ - { - "id": "pe-04_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "pe-4_prm_1" - }, - { - "name": "label", - "value": "PE-04_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "system distribution and transmission lines", - "guidelines": [ - { - "prose": "system distribution and transmission lines requiring physical access controls are defined;" - } - ] - }, - { - "id": "pe-04_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "pe-4_prm_2" - }, - { - "name": "label", - "value": "PE-04_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "security controls", - "guidelines": [ - { - "prose": "security controls to be implemented to control physical access to system distribution and transmission lines within the organizational facility are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PE-04", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-4" - }, - { - "name": "label", - "value": "PE-04", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pe-5", - "rel": "related" - }, - { - "href": "#pe-9", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - } - ], - "parts": [ - { - "id": "pe-4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Control physical access to {{ insert: param, pe-04_odp.01 }} within organizational facilities using {{ insert: param, pe-04_odp.02 }}." - }, - { - "id": "pe-4_gdn", - "name": "guidance", - "prose": "Security controls applied to system distribution and transmission lines prevent accidental damage, disruption, and physical tampering. Such controls may also be necessary to prevent eavesdropping or modification of unencrypted transmissions. Security controls used to control physical access to system distribution and transmission lines include disconnected or locked spare jacks, locked wiring closets, protection of cabling by conduit or cable trays, and wiretapping sensors." - }, - { - "id": "pe-4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-04", - "class": "sp800-53a" - } - ], - "prose": "physical access to {{ insert: param, pe-04_odp.01 }} within organizational facilities is controlled using {{ insert: param, pe-04_odp.02 }}.", - "links": [ - { - "href": "#pe-4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-04-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing access control for transmission mediums\n\nsystem design documentation\n\nfacility communications and wiring diagrams\n\nlist of physical security safeguards applied to system distribution and transmission lines\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-04-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-04-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for access control to distribution and transmission lines\n\nmechanisms/security safeguards supporting and/or implementing access control to distribution and transmission lines" - } - ] - } - ] - }, - { - "id": "pe-5", - "class": "SP800-53", - "title": "Access Control for Output Devices", - "params": [ - { - "id": "pe-05_odp", - "props": [ - { - "name": "alt-identifier", - "value": "pe-5_prm_1" - }, - { - "name": "label", - "value": "PE-05_ODP", - "class": "sp800-53a" - } - ], - "label": "output devices", - "guidelines": [ - { - "prose": "output devices that require physical access control to output are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PE-05", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-5" - }, - { - "name": "label", - "value": "PE-05", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#4c501da5-9d79-4cb6-ba80-97260e1ce327", - "rel": "reference" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pe-4", - "rel": "related" - }, - { - "href": "#pe-18", - "rel": "related" - } - ], - "parts": [ - { - "id": "pe-5_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Control physical access to output from {{ insert: param, pe-05_odp }} to prevent unauthorized individuals from obtaining the output." - }, - { - "id": "pe-5_gdn", - "name": "guidance", - "prose": "Controlling physical access to output devices includes placing output devices in locked rooms or other secured areas with keypad or card reader access controls and allowing access to authorized individuals only, placing output devices in locations that can be monitored by personnel, installing monitor or screen filters, and using headphones. Examples of output devices include monitors, printers, scanners, audio devices, facsimile machines, and copiers." - }, - { - "id": "pe-5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-05", - "class": "sp800-53a" - } - ], - "prose": "physical access to output from {{ insert: param, pe-05_odp }} is controlled to prevent unauthorized individuals from obtaining the output.", - "links": [ - { - "href": "#pe-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-05-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing access control for display medium\n\nfacility layout of system components\n\nactual displays from system components\n\nlist of output devices and associated outputs requiring physical access controls\n\nphysical access control logs or records for areas containing output devices and related outputs\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-05-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with physical access control responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-05-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for access control to output devices\n\nmechanisms supporting and/or implementing access control to output devices" - } - ] - } - ] - }, - { - "id": "pe-6", - "class": "SP800-53", - "title": "Monitoring Physical Access", - "params": [ - { - "id": "pe-06_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "pe-6_prm_1" - }, - { - "name": "label", - "value": "PE-06_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least monthly" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to review physical access logs is defined;" - } - ] - }, - { - "id": "pe-06_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "pe-6_prm_2" - }, - { - "name": "alt-label", - "value": "events or potential indications of events", - "class": "sp800-53" - }, - { - "name": "label", - "value": "PE-06_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events or potential indication of events requiring physical access logs to be reviewed are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PE-06", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-6" - }, - { - "name": "label", - "value": "PE-06", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-06" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cp-10", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - } - ], - "parts": [ - { - "id": "pe-6_smt", - "name": "statement", - "parts": [ - { - "id": "pe-6_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Monitor physical access to the facility where the system resides to detect and respond to physical security incidents;" - }, - { - "id": "pe-6_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Review physical access logs {{ insert: param, pe-06_odp.01 }} and upon occurrence of {{ insert: param, pe-06_odp.02 }} ; and" - }, - { - "id": "pe-6_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Coordinate results of reviews and investigations with the organizational incident response capability." - } - ] - }, - { - "id": "pe-6_gdn", - "name": "guidance", - "prose": "Physical access monitoring includes publicly accessible areas within organizational facilities. Examples of physical access monitoring include the employment of guards, video surveillance equipment (i.e., cameras), and sensor devices. Reviewing physical access logs can help identify suspicious activity, anomalous events, or potential threats. The reviews can be supported by audit logging controls, such as [AU-2](#au-2) , if the access logs are part of an automated system. Organizational incident response capabilities include investigations of physical security incidents and responses to the incidents. Incidents include security violations or suspicious physical access activities. Suspicious physical access activities include accesses outside of normal work hours, repeated accesses to areas not normally accessed, accesses for unusual lengths of time, and out-of-sequence accesses." - }, - { - "id": "pe-6_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-06", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-6_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-06a.", - "class": "sp800-53a" - } - ], - "prose": "physical access to the facility where the system resides is monitored to detect and respond to physical security incidents;", - "links": [ - { - "href": "#pe-6_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-6_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-06b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-6_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-06b.[01]", - "class": "sp800-53a" - } - ], - "prose": "physical access logs are reviewed {{ insert: param, pe-06_odp.01 }};", - "links": [ - { - "href": "#pe-6_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-6_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-06b.[02]", - "class": "sp800-53a" - } - ], - "prose": "physical access logs are reviewed upon occurrence of {{ insert: param, pe-06_odp.02 }};", - "links": [ - { - "href": "#pe-6_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-6_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-6_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-06c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-6_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-06c.[01]", - "class": "sp800-53a" - } - ], - "prose": "results of reviews are coordinated with organizational incident response capabilities;", - "links": [ - { - "href": "#pe-6_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-6_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-06c.[02]", - "class": "sp800-53a" - } - ], - "prose": "results of investigations are coordinated with organizational incident response capabilities.", - "links": [ - { - "href": "#pe-6_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-6_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-6_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-6_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-06-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access monitoring\n\nphysical access logs or records\n\nphysical access monitoring records\n\nphysical access log reviews\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-6_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-06-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with physical access monitoring responsibilities\n\norganizational personnel with incident response responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-6_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-06-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for monitoring physical access\n\nmechanisms supporting and/or implementing physical access monitoring\n\nmechanisms supporting and/or implementing the review of physical access logs" - } - ] - } - ], - "controls": [ - { - "id": "pe-6.1", - "class": "SP800-53-enhancement", - "title": "Intrusion Alarms and Surveillance Equipment", - "props": [ - { - "name": "label", - "value": "PE-06(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-6(1)" - }, - { - "name": "label", - "value": "PE-06(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-06.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#pe-6", - "rel": "required" - } - ], - "parts": [ - { - "id": "pe-6.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Monitor physical access to the facility where the system resides using physical intrusion alarms and surveillance equipment." - }, - { - "id": "pe-6.1_gdn", - "name": "guidance", - "prose": "Physical intrusion alarms can be employed to alert security personnel when unauthorized access to the facility is attempted. Alarm systems work in conjunction with physical barriers, physical access control systems, and security guards by triggering a response when these other forms of security have been compromised or breached. Physical intrusion alarms can include different types of sensor devices, such as motion sensors, contact sensors, and broken glass sensors. Surveillance equipment includes video cameras installed at strategic locations throughout the facility." - }, - { - "id": "pe-6.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-06(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-6.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-06(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "physical access to the facility where the system resides is monitored using physical intrusion alarms;", - "links": [ - { - "href": "#pe-6.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-6.1_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-06(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "physical access to the facility where the system resides is monitored using physical surveillance equipment.", - "links": [ - { - "href": "#pe-6.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-6.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-6.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-06(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access monitoring\n\nphysical access logs or records\n\nphysical access monitoring records\n\nphysical access log reviews\n\nsystem security plan\n\nprivacy plan\n\nprivacy impact assessment\n\nprivacy risk assessment documentation\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-6.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-06(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with physical access monitoring responsibilities\n\norganizational personnel with incident response responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "pe-6.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-06(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for monitoring physical intrusion alarms and surveillance equipment\n\nmechanisms supporting and/or implementing physical access monitoring\n\nmechanisms supporting and/or implementing physical intrusion alarms and surveillance equipment" - } - ] - } - ] - }, - { - "id": "pe-6.4", - "class": "SP800-53-enhancement", - "title": "Monitoring Physical Access to Systems", - "params": [ - { - "id": "pe-06.04_odp", - "props": [ - { - "name": "alt-identifier", - "value": "pe-6.4_prm_1" - }, - { - "name": "alt-label", - "value": "physical spaces containing one or more components of the system", - "class": "sp800-53" - }, - { - "name": "label", - "value": "PE-06(04)_ODP", - "class": "sp800-53a" - } - ], - "label": "physical spaces", - "guidelines": [ - { - "prose": "physical spaces containing one or more components of the system are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PE-06(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-6(4)" - }, - { - "name": "label", - "value": "PE-06(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-06.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#pe-6", - "rel": "required" - } - ], - "parts": [ - { - "id": "pe-6.4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Monitor physical access to the system in addition to the physical access monitoring of the facility at {{ insert: param, pe-06.04_odp }}." - }, - { - "id": "pe-6.4_gdn", - "name": "guidance", - "prose": "Monitoring physical access to systems provides additional monitoring for those areas within facilities where there is a concentration of system components, including server rooms, media storage areas, and communications centers. Physical access monitoring can be coordinated with intrusion detection systems and system monitoring capabilities to provide comprehensive and integrated threat coverage for the organization." - }, - { - "id": "pe-6.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-06(04)", - "class": "sp800-53a" - } - ], - "prose": "physical access to the system is monitored in addition to the physical access monitoring of the facility at {{ insert: param, pe-06.04_odp }}.", - "links": [ - { - "href": "#pe-6.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-6.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-06(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing physical access monitoring\n\nphysical access control logs or records\n\nphysical access control devices\n\naccess authorizations\n\naccess credentials\n\nlist of areas within the facility containing concentrations of system components or system components requiring additional physical access monitoring\n\nsystem security plan\n\nprivacy plan\n\nprivacy impact assessment\n\nprivacy risk assessment documentation\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-6.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-06(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with physical access monitoring responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "pe-6.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-06(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for monitoring physical access to the system\n\nmechanisms supporting and/or implementing physical access monitoring for facility areas containing system components" - } - ] - } - ] - } - ] - }, - { - "id": "pe-8", - "class": "SP800-53", - "title": "Visitor Access Records", - "params": [ - { - "id": "pe-08_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "pe-8_prm_1" - }, - { - "name": "label", - "value": "PE-08_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "for a minimum of one (1) year" - } - ], - "guidelines": [ - { - "prose": "time period for which to maintain visitor access records for the facility where the system resides is defined;" - } - ] - }, - { - "id": "pe-08_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "pe-8_prm_2" - }, - { - "name": "label", - "value": "PE-08_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least monthly" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to review visitor access records is defined;" - } - ] - }, - { - "id": "pe-08_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "pe-8_prm_3" - }, - { - "name": "label", - "value": "PE-08_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "personnel", - "guidelines": [ - { - "prose": "personnel to whom visitor access records anomalies are reported to is/are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PE-08", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-8" - }, - { - "name": "label", - "value": "PE-08", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pe-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "pe-8_smt", - "name": "statement", - "parts": [ - { - "id": "pe-8_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Maintain visitor access records to the facility where the system resides for {{ insert: param, pe-08_odp.01 }};" - }, - { - "id": "pe-8_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Review visitor access records {{ insert: param, pe-08_odp.02 }} ; and" - }, - { - "id": "pe-8_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Report anomalies in visitor access records to {{ insert: param, pe-08_odp.03 }}." - } - ] - }, - { - "id": "pe-8_gdn", - "name": "guidance", - "prose": "Visitor access records include the names and organizations of individuals visiting, visitor signatures, forms of identification, dates of access, entry and departure times, purpose of visits, and the names and organizations of individuals visited. Access record reviews determine if access authorizations are current and are still required to support organizational mission and business functions. Access records are not required for publicly accessible areas." - }, - { - "id": "pe-8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-08", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-8_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-08a.", - "class": "sp800-53a" - } - ], - "prose": "visitor access records for the facility where the system resides are maintained for {{ insert: param, pe-08_odp.01 }};", - "links": [ - { - "href": "#pe-8_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-8_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-08b.", - "class": "sp800-53a" - } - ], - "prose": "visitor access records are reviewed {{ insert: param, pe-08_odp.02 }};", - "links": [ - { - "href": "#pe-8_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-8_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-08c.", - "class": "sp800-53a" - } - ], - "prose": "visitor access records anomalies are reported to {{ insert: param, pe-08_odp.03 }}.", - "links": [ - { - "href": "#pe-8_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-08-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing visitor access records\n\nvisitor access control logs or records\n\nvisitor access record or log reviews\n\nsystem security plan\n\nprivacy plan\n\nprivacy impact assessment\n\nprivacy risk assessment documentation\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-08-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with visitor access record responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "pe-8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-08-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for maintaining and reviewing visitor access records\n\nmechanisms supporting and/or implementing the maintenance and review of visitor access records" - } - ] - } - ], - "controls": [ - { - "id": "pe-8.1", - "class": "SP800-53-enhancement", - "title": "Automated Records Maintenance and Review", - "params": [ - { - "id": "pe-8.1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "pe-08.01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "pe-08.01_odp.02" - } - ], - "label": "organization-defined automated mechanisms" - }, - { - "id": "pe-08.01_odp.01", - "props": [ - { - "name": "label", - "value": "PE-08(01)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used to maintain visitor access records are defined;" - } - ] - }, - { - "id": "pe-08.01_odp.02", - "props": [ - { - "name": "label", - "value": "PE-08(01)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used to review visitor access records are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PE-08(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-8(1)" - }, - { - "name": "label", - "value": "PE-08(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-08.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#pe-8", - "rel": "required" - } - ], - "parts": [ - { - "id": "pe-8.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Maintain and review visitor access records using {{ insert: param, pe-8.1_prm_1 }}." - }, - { - "id": "pe-8.1_gdn", - "name": "guidance", - "prose": "Visitor access records may be stored and maintained in a database management system that is accessible by organizational personnel. Automated access to such records facilitates record reviews on a regular basis to determine if access authorizations are current and still required to support organizational mission and business functions." - }, - { - "id": "pe-8.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-08(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-8.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-08(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "visitor access records are maintained using {{ insert: param, pe-08.01_odp.01 }};", - "links": [ - { - "href": "#pe-8.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-8.1_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-08(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "visitor access records are reviewed using {{ insert: param, pe-08.01_odp.02 }}.", - "links": [ - { - "href": "#pe-8.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-8.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-8.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-08(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing visitor access records\n\nautomated mechanisms supporting management of visitor access records\n\nvisitor access control logs or records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-8.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-08(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with visitor access record responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "pe-8.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-08(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for maintaining and reviewing visitor access records\n\nautomated mechanisms supporting and/or implementing the maintenance and review of visitor access records" - } - ] - } - ] - } - ] - }, - { - "id": "pe-9", - "class": "SP800-53", - "title": "Power Equipment and Cabling", - "props": [ - { - "name": "label", - "value": "PE-09", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-9" - }, - { - "name": "label", - "value": "PE-09", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-09" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#pe-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "pe-9_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Protect power equipment and power cabling for the system from damage and destruction." - }, - { - "id": "pe-9_gdn", - "name": "guidance", - "prose": "Organizations determine the types of protection necessary for the power equipment and cabling employed at different locations that are both internal and external to organizational facilities and environments of operation. Types of power equipment and cabling include internal cabling and uninterruptable power sources in offices or data centers, generators and power cabling outside of buildings, and power sources for self-contained components such as satellites, vehicles, and other deployable systems." - }, - { - "id": "pe-9_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-09", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-9_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-09[01]", - "class": "sp800-53a" - } - ], - "prose": "power equipment for the system is protected from damage and destruction;", - "links": [ - { - "href": "#pe-9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-9_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-09[02]", - "class": "sp800-53a" - } - ], - "prose": "power cabling for the system is protected from damage and destruction.", - "links": [ - { - "href": "#pe-9_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-9_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-09-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing power equipment/cabling protection\n\nfacilities housing power equipment/cabling\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-9_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-09-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with the responsibility to protect power equipment/cabling\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-9_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-09-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing the protection of power equipment/cabling" - } - ] - } - ] - }, - { - "id": "pe-10", - "class": "SP800-53", - "title": "Emergency Shutoff", - "params": [ - { - "id": "pe-10_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "pe-10_prm_1" - }, - { - "name": "label", - "value": "PE-10_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "system or individual system components", - "guidelines": [ - { - "prose": "system or individual system components that require the capability to shut off power in emergency situations is/are defined;" - } - ] - }, - { - "id": "pe-10_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "pe-10_prm_2" - }, - { - "name": "alt-label", - "value": "location by system or system component", - "class": "sp800-53" - }, - { - "name": "label", - "value": "PE-10_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "location", - "constraints": [ - { - "description": "near more than one egress point of the IT area and ensures it is labeled and protected by a cover to prevent accidental shut-off" - } - ], - "guidelines": [ - { - "prose": "location of emergency shutoff switches or devices by system or system component is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PE-10", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-10" - }, - { - "name": "label", - "value": "PE-10", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-10" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#pe-15", - "rel": "related" - } - ], - "parts": [ - { - "id": "pe-10_smt", - "name": "statement", - "parts": [ - { - "id": "pe-10_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Provide the capability of shutting off power to {{ insert: param, pe-10_odp.01 }} in emergency situations;" - }, - { - "id": "pe-10_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Place emergency shutoff switches or devices in {{ insert: param, pe-10_odp.02 }} to facilitate access for authorized personnel; and" - }, - { - "id": "pe-10_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Protect emergency power shutoff capability from unauthorized activation." - } - ] - }, - { - "id": "pe-10_gdn", - "name": "guidance", - "prose": "Emergency power shutoff primarily applies to organizational facilities that contain concentrations of system resources, including data centers, mainframe computer rooms, server rooms, and areas with computer-controlled machinery." - }, - { - "id": "pe-10_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-10", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-10_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-10a.", - "class": "sp800-53a" - } - ], - "prose": "the capability to shut off power to {{ insert: param, pe-10_odp.01 }} in emergency situations is provided;", - "links": [ - { - "href": "#pe-10_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-10_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-10b.", - "class": "sp800-53a" - } - ], - "prose": "emergency shutoff switches or devices are placed in {{ insert: param, pe-10_odp.02 }} to facilitate access for authorized personnel;", - "links": [ - { - "href": "#pe-10_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-10_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-10c.", - "class": "sp800-53a" - } - ], - "prose": "the emergency power shutoff capability is protected from unauthorized activation.", - "links": [ - { - "href": "#pe-10_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-10_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-10_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-10-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing power source emergency shutoff\n\nemergency shutoff controls or switches\n\nlocations housing emergency shutoff switches and devices\n\nsecurity safeguards protecting the emergency power shutoff capability from unauthorized activation\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-10_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-10-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with the responsibility for the emergency power shutoff capability (both implementing and using the capability)\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-10_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-10-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing emergency power shutoff" - } - ] - } - ] - }, - { - "id": "pe-11", - "class": "SP800-53", - "title": "Emergency Power", - "params": [ - { - "id": "pe-11_odp", - "props": [ - { - "name": "alt-identifier", - "value": "pe-11_prm_1" - }, - { - "name": "label", - "value": "PE-11_ODP", - "class": "sp800-53a" - } - ], - "select": { - "choice": [ - "an orderly shutdown of the system", - "transition of the system to long-term alternate power" - ] - } - } - ], - "props": [ - { - "name": "label", - "value": "PE-11", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-11" - }, - { - "name": "label", - "value": "PE-11", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-11" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "pe-11_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Provide an uninterruptible power supply to facilitate {{ insert: param, pe-11_odp }} in the event of a primary power source loss." - }, - { - "id": "pe-11_gdn", - "name": "guidance", - "prose": "An uninterruptible power supply (UPS) is an electrical system or mechanism that provides emergency power when there is a failure of the main power source. A UPS is typically used to protect computers, data centers, telecommunication equipment, or other electrical equipment where an unexpected power disruption could cause injuries, fatalities, serious mission or business disruption, or loss of data or information. A UPS differs from an emergency power system or backup generator in that the UPS provides near-instantaneous protection from unanticipated power interruptions from the main power source by providing energy stored in batteries, supercapacitors, or flywheels. The battery duration of a UPS is relatively short but provides sufficient time to start a standby power source, such as a backup generator, or properly shut down the system." - }, - { - "id": "pe-11_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-11", - "class": "sp800-53a" - } - ], - "prose": "an uninterruptible power supply is provided to facilitate {{ insert: param, pe-11_odp }} in the event of a primary power source loss.", - "links": [ - { - "href": "#pe-11_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-11_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-11-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing emergency power\n\nuninterruptible power supply\n\nuninterruptible power supply documentation\n\nuninterruptible power supply test records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-11_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-11-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with the responsibility for emergency power and/or planning\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-11_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-11-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing an uninterruptible power supply\n\nthe uninterruptable power supply" - } - ] - } - ], - "controls": [ - { - "id": "pe-11.1", - "class": "SP800-53-enhancement", - "title": "Alternate Power Supply — Minimal Operational Capability", - "params": [ - { - "id": "pe-11.01_odp", - "props": [ - { - "name": "alt-identifier", - "value": "pe-11.1_prm_1" - }, - { - "name": "label", - "value": "PE-11(01)_ODP", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "automatically" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PE-11(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-11(1)" - }, - { - "name": "label", - "value": "PE-11(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-11.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#pe-11", - "rel": "required" - } - ], - "parts": [ - { - "id": "pe-11.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Provide an alternate power supply for the system that is activated {{ insert: param, pe-11.01_odp }} and that can maintain minimally required operational capability in the event of an extended loss of the primary power source." - }, - { - "id": "pe-11.1_gdn", - "name": "guidance", - "prose": "Provision of an alternate power supply with minimal operating capability can be satisfied by accessing a secondary commercial power supply or other external power supply." - }, - { - "id": "pe-11.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-11(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-11.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-11(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "an alternate power supply provided for the system is activated {{ insert: param, pe-11.01_odp }};", - "links": [ - { - "href": "#pe-11.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-11.1_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-11(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "the alternate power supply provided for the system can maintain minimally required operational capability in the event of an extended loss of the primary power source.", - "links": [ - { - "href": "#pe-11.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-11.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-11.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-11(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing emergency power\n\nalternate power supply\n\nalternate power supply documentation\n\nalternate power supply test records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-11.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-11(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with the responsibility for emergency power and/or planning\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-11.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-11(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing an alternate power supply\n\nthe alternate power supply" - } - ] - } - ] - } - ] - }, - { - "id": "pe-12", - "class": "SP800-53", - "title": "Emergency Lighting", - "props": [ - { - "name": "label", - "value": "PE-12", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-12" - }, - { - "name": "label", - "value": "PE-12", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-12" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "pe-12_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Employ and maintain automatic emergency lighting for the system that activates in the event of a power outage or disruption and that covers emergency exits and evacuation routes within the facility." - }, - { - "id": "pe-12_gdn", - "name": "guidance", - "prose": "The provision of emergency lighting applies primarily to organizational facilities that contain concentrations of system resources, including data centers, server rooms, and mainframe computer rooms. Emergency lighting provisions for the system are described in the contingency plan for the organization. If emergency lighting for the system fails or cannot be provided, organizations consider alternate processing sites for power-related contingencies." - }, - { - "id": "pe-12_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-12", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-12_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-12[01]", - "class": "sp800-53a" - } - ], - "prose": "automatic emergency lighting that activates in the event of a power outage or disruption is employed for the system;", - "links": [ - { - "href": "#pe-12_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-12_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-12[02]", - "class": "sp800-53a" - } - ], - "prose": "automatic emergency lighting that activates in the event of a power outage or disruption is maintained for the system;", - "links": [ - { - "href": "#pe-12_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-12_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-12[03]", - "class": "sp800-53a" - } - ], - "prose": "automatic emergency lighting for the system covers emergency exits within the facility;", - "links": [ - { - "href": "#pe-12_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-12_obj-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-12[04]", - "class": "sp800-53a" - } - ], - "prose": "automatic emergency lighting for the system covers evacuation routes within the facility.", - "links": [ - { - "href": "#pe-12_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-12_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-12_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-12-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing emergency lighting\n\nemergency lighting documentation\n\nemergency lighting test records\n\nemergency exits and evacuation routes\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-12_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-12-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with the responsibility for emergency lighting and/or planning\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-12_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-12-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing an emergency lighting capability" - } - ] - } - ] - }, - { - "id": "pe-13", - "class": "SP800-53", - "title": "Fire Protection", - "props": [ - { - "name": "label", - "value": "PE-13", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-13" - }, - { - "name": "label", - "value": "PE-13", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-13" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#at-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "pe-13_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Employ and maintain fire detection and suppression systems that are supported by an independent energy source." - }, - { - "id": "pe-13_gdn", - "name": "guidance", - "prose": "The provision of fire detection and suppression systems applies primarily to organizational facilities that contain concentrations of system resources, including data centers, server rooms, and mainframe computer rooms. Fire detection and suppression systems that may require an independent energy source include sprinkler systems and smoke detectors. An independent energy source is an energy source, such as a microgrid, that is separate, or can be separated, from the energy sources providing power for the other parts of the facility." - }, - { - "id": "pe-13_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-13", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-13_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-13[01]", - "class": "sp800-53a" - } - ], - "prose": "fire detection systems are employed;", - "links": [ - { - "href": "#pe-13_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-13_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-13[02]", - "class": "sp800-53a" - } - ], - "prose": "employed fire detection systems are supported by an independent energy source;", - "links": [ - { - "href": "#pe-13_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-13_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-13[03]", - "class": "sp800-53a" - } - ], - "prose": "employed fire detection systems are maintained;", - "links": [ - { - "href": "#pe-13_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-13_obj-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-13[04]", - "class": "sp800-53a" - } - ], - "prose": "fire suppression systems are employed;", - "links": [ - { - "href": "#pe-13_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-13_obj-5", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-13[05]", - "class": "sp800-53a" - } - ], - "prose": "employed fire suppression systems are supported by an independent energy source;", - "links": [ - { - "href": "#pe-13_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-13_obj-6", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-13[06]", - "class": "sp800-53a" - } - ], - "prose": "employed fire suppression systems are maintained.", - "links": [ - { - "href": "#pe-13_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-13_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-13_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-13-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing fire protection\n\nfire suppression and detection devices/systems\n\nfire suppression and detection devices/systems documentation\n\ntest records of fire suppression and detection devices/systems\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-13_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-13-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for fire detection and suppression devices/systems\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-13_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-13-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing fire suppression/detection devices/systems" - } - ] - } - ], - "controls": [ - { - "id": "pe-13.1", - "class": "SP800-53-enhancement", - "title": "Detection Systems — Automatic Activation and Notification", - "params": [ - { - "id": "pe-13.01_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "pe-13.1_prm_1" - }, - { - "name": "label", - "value": "PE-13(01)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "constraints": [ - { - "description": "service provider building maintenance/physical security personnel" - } - ], - "guidelines": [ - { - "prose": "personnel or roles to be notified in the event of a fire is/are defined;" - } - ] - }, - { - "id": "pe-13.01_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "pe-13.1_prm_2" - }, - { - "name": "label", - "value": "PE-13(01)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "emergency responders", - "constraints": [ - { - "description": "service provider emergency responders with incident response responsibilities" - } - ], - "guidelines": [ - { - "prose": "emergency responders to be notified in the event of a fire are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PE-13(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-13(1)" - }, - { - "name": "label", - "value": "PE-13(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-13.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#pe-13", - "rel": "required" - } - ], - "parts": [ - { - "id": "pe-13.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Employ fire detection systems that activate automatically and notify {{ insert: param, pe-13.01_odp.01 }} and {{ insert: param, pe-13.01_odp.02 }} in the event of a fire." - }, - { - "id": "pe-13.1_gdn", - "name": "guidance", - "prose": "Organizations can identify personnel, roles, and emergency responders if individuals on the notification list need to have access authorizations or clearances (e.g., to enter to facilities where access is restricted due to the classification or impact level of information within the facility). Notification mechanisms may require independent energy sources to ensure that the notification capability is not adversely affected by the fire." - }, - { - "id": "pe-13.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-13(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-13.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-13(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "fire detection systems that activate automatically are employed in the event of a fire;", - "links": [ - { - "href": "#pe-13.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-13.1_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-13(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "fire detection systems that notify {{ insert: param, pe-13.01_odp.01 }} automatically are employed in the event of a fire;", - "links": [ - { - "href": "#pe-13.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-13.1_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-13(01)[03]", - "class": "sp800-53a" - } - ], - "prose": "fire detection systems that notify {{ insert: param, pe-13.01_odp.02 }} automatically are employed in the event of a fire.", - "links": [ - { - "href": "#pe-13.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-13.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-13.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-13(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing fire protection\n\nfacility housing the information system\n\nalarm service-level agreements\n\ntest records of fire suppression and detection devices/systems\n\nfire suppression and detection devices/systems documentation\n\nalerts/notifications of fire events\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-13.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-13(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for fire detection and suppression devices/systems\n\norganizational personnel with responsibilities for notifying appropriate personnel, roles, and emergency responders of fires\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-13.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-13(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing fire detection devices/systems\n\nactivation of fire detection devices/systems (simulated)\n\nautomated notifications" - } - ] - } - ] - }, - { - "id": "pe-13.2", - "class": "SP800-53-enhancement", - "title": "Suppression Systems — Automatic Activation and Notification", - "params": [ - { - "id": "pe-13.02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "pe-13.2_prm_1" - }, - { - "name": "label", - "value": "PE-13(02)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to be notified in the event of a fire is/are defined;" - } - ] - }, - { - "id": "pe-13.02_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "pe-13.2_prm_2" - }, - { - "name": "label", - "value": "PE-13(02)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "emergency responders", - "guidelines": [ - { - "prose": "emergency responders to be notified in the event of a fire are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PE-13(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-13(2)" - }, - { - "name": "label", - "value": "PE-13(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-13.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#pe-13", - "rel": "required" - } - ], - "parts": [ - { - "id": "pe-13.2_smt", - "name": "statement", - "parts": [ - { - "id": "pe-13.2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Employ fire suppression systems that activate automatically and notify {{ insert: param, pe-13.02_odp.01 }} and {{ insert: param, pe-13.02_odp.02 }} ; and" - }, - { - "id": "pe-13.2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Employ an automatic fire suppression capability when the facility is not staffed on a continuous basis." - } - ] - }, - { - "id": "pe-13.2_gdn", - "name": "guidance", - "prose": "Organizations can identify specific personnel, roles, and emergency responders if individuals on the notification list need to have appropriate access authorizations and/or clearances (e.g., to enter to facilities where access is restricted due to the impact level or classification of information within the facility). Notification mechanisms may require independent energy sources to ensure that the notification capability is not adversely affected by the fire." - }, - { - "id": "pe-13.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-13(02)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-13.2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-13(02)(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-13.2_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-13(02)(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "fire suppression systems that activate automatically are employed;", - "links": [ - { - "href": "#pe-13.2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-13.2_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-13(02)(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "fire suppression systems that notify {{ insert: param, pe-13.02_odp.01 }} automatically are employed;", - "links": [ - { - "href": "#pe-13.2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-13.2_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-13(02)(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "fire suppression systems that notify {{ insert: param, pe-13.02_odp.02 }} automatically are employed;", - "links": [ - { - "href": "#pe-13.2_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-13.2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-13.2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-13(02)(b)", - "class": "sp800-53a" - } - ], - "prose": "an automatic fire suppression capability is employed when the facility is not staffed on a continuous basis.", - "links": [ - { - "href": "#pe-13.2_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-13.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-13.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-13(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing fire protection\n\nfire suppression and detection devices/systems documentation\n\nfacility housing the system\n\nalarm service-level agreements\n\ntest records of fire suppression and detection devices/systems\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-13.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-13(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for fire detection and suppression devices/systems\n\norganizational personnel with responsibilities for providing automatic notifications of any activation of fire suppression devices/systems to appropriate personnel, roles, and emergency responders\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-13.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-13(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Automated mechanisms supporting and/or implementing fire suppression devices/systems\n\nactivation of fire suppression devices/systems (simulated)\n\nautomated notifications" - } - ] - } - ] - } - ] - }, - { - "id": "pe-14", - "class": "SP800-53", - "title": "Environmental Controls", - "params": [ - { - "id": "pe-14_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "pe-14_prm_1" - }, - { - "name": "label", - "value": "PE-14_ODP[01]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "consistent with American Society of Heating, Refrigerating and Air-conditioning Engineers (ASHRAE) document entitled Thermal Guidelines for Data Processing Environments" - } - ] - }, - { - "id": "pe-14_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "pe-14_prm_2" - }, - { - "name": "label", - "value": "PE-14_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "environmental control", - "guidelines": [ - { - "prose": "environmental control(s) for which to maintain a specified level in the facility where the system resides are defined (if selected);" - } - ] - }, - { - "id": "pe-14_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "pe-14_prm_3" - }, - { - "name": "label", - "value": "PE-14_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "acceptable levels", - "guidelines": [ - { - "prose": "acceptable levels for environmental controls are defined;" - } - ] - }, - { - "id": "pe-14_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "pe-14_prm_4" - }, - { - "name": "label", - "value": "PE-14_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "continuously" - } - ], - "guidelines": [ - { - "prose": "frequency at which to monitor environmental control levels is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PE-14", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-14" - }, - { - "name": "label", - "value": "PE-14", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-14" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - } - ], - "parts": [ - { - "id": "pe-14_smt", - "name": "statement", - "parts": [ - { - "id": "pe-14_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Maintain {{ insert: param, pe-14_odp.01 }} levels within the facility where the system resides at {{ insert: param, pe-14_odp.03 }} ; and" - }, - { - "id": "pe-14_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Monitor environmental control levels {{ insert: param, pe-14_odp.04 }}." - } - ] - }, - { - "id": "pe-14_gdn", - "name": "guidance", - "prose": "The provision of environmental controls applies primarily to organizational facilities that contain concentrations of system resources (e.g., data centers, mainframe computer rooms, and server rooms). Insufficient environmental controls, especially in very harsh environments, can have a significant adverse impact on the availability of systems and system components that are needed to support organizational mission and business functions." - }, - { - "id": "pe-14_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "PE-14 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "pe-14_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(a) Requirement:" - } - ], - "prose": "The service provider measures temperature at server inlets and humidity levels by dew point." - } - ] - }, - { - "id": "pe-14_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-14", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-14_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-14a.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, pe-14_odp.01 }} levels are maintained at {{ insert: param, pe-14_odp.03 }} within the facility where the system resides;", - "links": [ - { - "href": "#pe-14_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-14_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-14b.", - "class": "sp800-53a" - } - ], - "prose": "environmental control levels are monitored {{ insert: param, pe-14_odp.04 }}.", - "links": [ - { - "href": "#pe-14_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-14_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-14_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-14-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing temperature and humidity control\n\ntemperature and humidity controls\n\nfacility housing the system\n\ntemperature and humidity controls documentation\n\ntemperature and humidity records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-14_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-14-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for system environmental controls\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-14_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-14-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing the maintenance and monitoring of temperature and humidity levels" - } - ] - } - ], - "controls": [ - { - "id": "pe-14.2", - "class": "SP800-53-enhancement", - "title": "Monitoring with Alarms and Notifications", - "params": [ - { - "id": "pe-14.02_odp", - "props": [ - { - "name": "alt-identifier", - "value": "pe-14.2_prm_1" - }, - { - "name": "label", - "value": "PE-14(02)_ODP", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to be notified by environmental control monitoring when environmental changes are potentially harmful to personnel or equipment is/are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PE-14(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-14(2)" - }, - { - "name": "label", - "value": "PE-14(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-14.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#pe-14", - "rel": "required" - } - ], - "parts": [ - { - "id": "pe-14.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Employ environmental control monitoring that provides an alarm or notification of changes potentially harmful to personnel or equipment to {{ insert: param, pe-14.02_odp }}." - }, - { - "id": "pe-14.2_gdn", - "name": "guidance", - "prose": "The alarm or notification may be an audible alarm or a visual message in real time to personnel or roles defined by the organization. Such alarms and notifications can help minimize harm to individuals and damage to organizational assets by facilitating a timely incident response." - }, - { - "id": "pe-14.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-14(02)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-14.2_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-14(02)[01]", - "class": "sp800-53a" - } - ], - "prose": "environmental control monitoring is employed;", - "links": [ - { - "href": "#pe-14.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-14.2_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-14(02)[02]", - "class": "sp800-53a" - } - ], - "prose": "the environmental control monitoring capability provides an alarm or notification to {{ insert: param, pe-14.02_odp }} when changes are potentially harmful to personnel or equipment.", - "links": [ - { - "href": "#pe-14.2_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-14.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-14.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-14(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing temperature and humidity monitoring\n\nfacility housing the system\n\nlogs or records of temperature and humidity monitoring\n\nrecords of changes to temperature and humidity levels that generate alarms or notifications\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-14.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-14(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for system environmental controls\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-14.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-14(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing temperature and humidity monitoring" - } - ] - } - ] - } - ] - }, - { - "id": "pe-15", - "class": "SP800-53", - "title": "Water Damage Protection", - "props": [ - { - "name": "label", - "value": "PE-15", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-15" - }, - { - "name": "label", - "value": "PE-15", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-15" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#pe-10", - "rel": "related" - } - ], - "parts": [ - { - "id": "pe-15_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Protect the system from damage resulting from water leakage by providing master shutoff or isolation valves that are accessible, working properly, and known to key personnel." - }, - { - "id": "pe-15_gdn", - "name": "guidance", - "prose": "The provision of water damage protection primarily applies to organizational facilities that contain concentrations of system resources, including data centers, server rooms, and mainframe computer rooms. Isolation valves can be employed in addition to or in lieu of master shutoff valves to shut off water supplies in specific areas of concern without affecting entire organizations." - }, - { - "id": "pe-15_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-15", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-15_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-15[01]", - "class": "sp800-53a" - } - ], - "prose": "the system is protected from damage resulting from water leakage by providing master shutoff or isolation valves;", - "links": [ - { - "href": "#pe-15_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-15_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-15[02]", - "class": "sp800-53a" - } - ], - "prose": "the master shutoff or isolation valves are accessible;", - "links": [ - { - "href": "#pe-15_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-15_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-15[03]", - "class": "sp800-53a" - } - ], - "prose": "the master shutoff or isolation valves are working properly;", - "links": [ - { - "href": "#pe-15_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-15_obj-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-15[04]", - "class": "sp800-53a" - } - ], - "prose": "the master shutoff or isolation valves are known to key personnel.", - "links": [ - { - "href": "#pe-15_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-15_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-15_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-15-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing water damage protection\n\nfacility housing the system\n\nmaster shutoff valves\n\nlist of key personnel with knowledge of location and activation procedures for master shutoff valves for the plumbing system\n\nmaster shutoff valve documentation\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-15_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-15-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for system environmental controls\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-15_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-15-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Master water-shutoff valves\n\norganizational process for activating master water shutoff" - } - ] - } - ], - "controls": [ - { - "id": "pe-15.1", - "class": "SP800-53-enhancement", - "title": "Automation Support", - "params": [ - { - "id": "pe-15.01_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "pe-15.1_prm_1" - }, - { - "name": "label", - "value": "PE-15(01)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "constraints": [ - { - "description": "service provider building maintenance/physical security personnel" - } - ], - "guidelines": [ - { - "prose": "personnel or roles to be alerted when the presence of water is detected near the system is/are defined;" - } - ] - }, - { - "id": "pe-15.01_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "pe-15.1_prm_2" - }, - { - "name": "label", - "value": "PE-15(01)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used to detect the presence of water near the system are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PE-15(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-15(1)" - }, - { - "name": "label", - "value": "PE-15(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-15.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#pe-15", - "rel": "required" - } - ], - "parts": [ - { - "id": "pe-15.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Detect the presence of water near the system and alert {{ insert: param, pe-15.01_odp.01 }} using {{ insert: param, pe-15.01_odp.02 }}." - }, - { - "id": "pe-15.1_gdn", - "name": "guidance", - "prose": "Automated mechanisms include notification systems, water detection sensors, and alarms." - }, - { - "id": "pe-15.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-15(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-15.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-15(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "the presence of water near the system can be detected automatically;", - "links": [ - { - "href": "#pe-15.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-15.1_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-15(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, pe-15.01_odp.01 }} is/are alerted using {{ insert: param, pe-15.01_odp.02 }}.", - "links": [ - { - "href": "#pe-15.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-15.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-15.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-15(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing water damage protection\n\nfacility housing the system\n\nautomated mechanisms for water shutoff valves\n\nautomated mechanisms for detecting the presence of water in the vicinity of the system\n\nalerts/notifications of water detection in system facility\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-15.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-15(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for system environmental controls\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-15.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-15(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Automated mechanisms supporting and/or implementing water detection capabilities and alerts for the system" - } - ] - } - ] - } - ] - }, - { - "id": "pe-16", - "class": "SP800-53", - "title": "Delivery and Removal", - "params": [ - { - "id": "pe-16_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "pe-16_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "pe-16_odp.02" - } - ], - "label": "organization-defined types of system components" - }, - { - "id": "pe-16_odp.01", - "props": [ - { - "name": "label", - "value": "PE-16_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "types of system components", - "constraints": [ - { - "description": "all information system components" - } - ], - "guidelines": [ - { - "prose": "types of system components to be authorized and controlled when entering the facility are defined;" - } - ] - }, - { - "id": "pe-16_odp.02", - "props": [ - { - "name": "label", - "value": "PE-16_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "types of system components", - "constraints": [ - { - "description": "all information system components" - } - ], - "guidelines": [ - { - "prose": "types of system components to be authorized and controlled when exiting the facility are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PE-16", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-16" - }, - { - "name": "label", - "value": "PE-16", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-16" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#ma-2", - "rel": "related" - }, - { - "href": "#ma-3", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pe-20", - "rel": "related" - }, - { - "href": "#sr-2", - "rel": "related" - }, - { - "href": "#sr-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sr-4", - "rel": "related" - }, - { - "href": "#sr-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "pe-16_smt", - "name": "statement", - "parts": [ - { - "id": "pe-16_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Authorize and control {{ insert: param, pe-16_prm_1 }} entering and exiting the facility; and" - }, - { - "id": "pe-16_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Maintain records of the system components." - } - ] - }, - { - "id": "pe-16_gdn", - "name": "guidance", - "prose": "Enforcing authorizations for entry and exit of system components may require restricting access to delivery areas and isolating the areas from the system and media libraries." - }, - { - "id": "pe-16_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-16", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-16_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-16a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-16_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-16a.[01]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, pe-16_odp.01 }} are authorized when entering the facility;", - "links": [ - { - "href": "#pe-16_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-16_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-16a.[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, pe-16_odp.01 }} are controlled when entering the facility;", - "links": [ - { - "href": "#pe-16_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-16_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-16a.[03]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, pe-16_odp.02 }} are authorized when exiting the facility;", - "links": [ - { - "href": "#pe-16_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-16_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-16a.[04]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, pe-16_odp.02 }} are controlled when exiting the facility;", - "links": [ - { - "href": "#pe-16_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-16_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-16_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-16b.", - "class": "sp800-53a" - } - ], - "prose": "records of the system components are maintained.", - "links": [ - { - "href": "#pe-16_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-16_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-16_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-16-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing the delivery and removal of system components from the facility\n\nfacility housing the system\n\nrecords of items entering and exiting the facility\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-16_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-16-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for controlling system components entering and exiting the facility\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-16_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-16-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational process for authorizing, monitoring, and controlling system-related items entering and exiting the facility\n\nmechanisms supporting and/or implementing, authorizing, monitoring, and controlling system-related items entering and exiting the facility" - } - ] - } - ] - }, - { - "id": "pe-17", - "class": "SP800-53", - "title": "Alternate Work Site", - "params": [ - { - "id": "pe-17_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "pe-17_prm_1" - }, - { - "name": "label", - "value": "PE-17_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "alternate work sites", - "guidelines": [ - { - "prose": "alternate work sites allowed for use by employees are defined;" - } - ] - }, - { - "id": "pe-17_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "pe-17_prm_2" - }, - { - "name": "label", - "value": "PE-17_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "controls", - "guidelines": [ - { - "prose": "controls to be employed at alternate work sites are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PE-17", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-17" - }, - { - "name": "label", - "value": "PE-17", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-17" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#83b9d63b-66b1-467c-9f3b-3a0b108771e9", - "rel": "reference" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "pe-17_smt", - "name": "statement", - "parts": [ - { - "id": "pe-17_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Determine and document the {{ insert: param, pe-17_odp.01 }} allowed for use by employees;" - }, - { - "id": "pe-17_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Employ the following controls at alternate work sites: {{ insert: param, pe-17_odp.02 }};" - }, - { - "id": "pe-17_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Assess the effectiveness of controls at alternate work sites; and" - }, - { - "id": "pe-17_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Provide a means for employees to communicate with information security and privacy personnel in case of incidents." - } - ] - }, - { - "id": "pe-17_gdn", - "name": "guidance", - "prose": "Alternate work sites include government facilities or the private residences of employees. While distinct from alternative processing sites, alternate work sites can provide readily available alternate locations during contingency operations. Organizations can define different sets of controls for specific alternate work sites or types of sites depending on the work-related activities conducted at the sites. Implementing and assessing the effectiveness of organization-defined controls and providing a means to communicate incidents at alternate work sites supports the contingency planning activities of organizations." - }, - { - "id": "pe-17_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PE-17", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pe-17_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-17a.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, pe-17_odp.01 }} are determined and documented;", - "links": [ - { - "href": "#pe-17_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-17_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-17b.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, pe-17_odp.02 }} are employed at alternate work sites;", - "links": [ - { - "href": "#pe-17_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-17_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-17c.", - "class": "sp800-53a" - } - ], - "prose": "the effectiveness of controls at alternate work sites is assessed;", - "links": [ - { - "href": "#pe-17_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-17_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-17d.", - "class": "sp800-53a" - } - ], - "prose": "a means for employees to communicate with information security and privacy personnel in case of incidents is provided.", - "links": [ - { - "href": "#pe-17_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pe-17_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-17_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-17-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing alternate work sites for organizational personnel\n\nlist of security controls required for alternate work sites\n\nassessments of security controls at alternate work sites\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-17_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-17-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel approving the use of alternate work sites\n\norganizational personnel using alternate work sites\n\norganizational personnel assessing controls at alternate work sites\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "pe-17_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-17-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for security and privacy at alternate work sites\n\nmechanisms supporting alternate work sites\n\nsecurity and privacy controls employed at alternate work sites\n\nmeans of communication between personnel at alternate work sites and security and privacy personnel" - } - ] - } - ] - }, - { - "id": "pe-18", - "class": "SP800-53", - "title": "Location of System Components", - "params": [ - { - "id": "pe-18_odp", - "props": [ - { - "name": "alt-identifier", - "value": "pe-18_prm_1" - }, - { - "name": "label", - "value": "PE-18_ODP", - "class": "sp800-53a" - } - ], - "label": "physical and environmental hazards", - "constraints": [ - { - "description": "physical and environmental hazards identified during threat assessment" - } - ], - "guidelines": [ - { - "prose": "physical and environmental hazards that could result in potential damage to system components within the facility are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PE-18", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PE-18" - }, - { - "name": "label", - "value": "PE-18", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pe-18" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#pe-5", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pe-19", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pe-20", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "pe-18_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Position system components within the facility to minimize potential damage from {{ insert: param, pe-18_odp }} and to minimize the opportunity for unauthorized access." - }, - { - "id": "pe-18_gdn", - "name": "guidance", - "prose": "Physical and environmental hazards include floods, fires, tornadoes, earthquakes, hurricanes, terrorism, vandalism, an electromagnetic pulse, electrical interference, and other forms of incoming electromagnetic radiation. Organizations consider the location of entry points where unauthorized individuals, while not being granted access, might nonetheless be near systems. Such proximity can increase the risk of unauthorized access to organizational communications using wireless packet sniffers or microphones, or unauthorized disclosure of information." - }, - { - "id": "pe-18_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PE-18", - "class": "sp800-53a" - } - ], - "prose": "system components are positioned within the facility to minimize potential damage from {{ insert: param, pe-18_odp }} and to minimize the opportunity for unauthorized access.", - "links": [ - { - "href": "#pe-18_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pe-18_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PE-18-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Physical and environmental protection policy\n\nprocedures addressing the positioning of system components\n\ndocumentation providing the location and position of system components within the facility\n\nlocations housing system components within the facility\n\nlist of physical and environmental hazards with the potential to damage system components within the facility\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pe-18_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PE-18-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibilities for positioning system components\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "pe-18_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PE-18-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for positioning system components" - } - ] - } - ] - } - ] - }, - { - "id": "pl", - "class": "family", - "title": "Planning", - "controls": [ - { - "id": "pl-1", - "class": "SP800-53", - "title": "Policy and Procedures", - "params": [ - { - "id": "pl-1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "pl-01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "pl-01_odp.02" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "pl-01_odp.01", - "props": [ - { - "name": "label", - "value": "PL-01_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the planning policy is to be disseminated is/are defined;" - } - ] - }, - { - "id": "pl-01_odp.02", - "props": [ - { - "name": "label", - "value": "PL-01_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the planning procedures are to be disseminated is/are defined;" - } - ] - }, - { - "id": "pl-01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "pl-1_prm_2" - }, - { - "name": "label", - "value": "PL-01_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "organization-level", - "mission/business process-level", - "system-level" - ] - } - }, - { - "id": "pl-01_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "pl-1_prm_3" - }, - { - "name": "label", - "value": "PL-01_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "official", - "guidelines": [ - { - "prose": "an official to manage the planning policy and procedures is defined;" - } - ] - }, - { - "id": "pl-01_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "pl-1_prm_4" - }, - { - "name": "label", - "value": "PL-01_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency with which the current planning policy is reviewed and updated is defined;" - } - ] - }, - { - "id": "pl-01_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "pl-1_prm_5" - }, - { - "name": "label", - "value": "PL-01_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that would require the current planning policy to be reviewed and updated are defined;" - } - ] - }, - { - "id": "pl-01_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "pl-1_prm_6" - }, - { - "name": "label", - "value": "PL-01_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency with which the current planning procedures are reviewed and updated is defined;" - } - ] - }, - { - "id": "pl-01_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "pl-1_prm_7" - }, - { - "name": "label", - "value": "PL-01_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "events", - "constraints": [ - { - "description": "significant changes" - } - ], - "guidelines": [ - { - "prose": "events that would require procedures to be reviewed and updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PL-01", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PL-1" - }, - { - "name": "label", - "value": "PL-01", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pl-01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#c7ac44e8-10db-4b64-b2b9-9e32ec1efed0", - "rel": "reference" - }, - { - "href": "#30eb758a-2707-4bca-90ad-949a74d4eb16", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#4c0ec2ee-a0d6-428a-9043-4504bc3ade6f", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "pl-1_smt", - "name": "statement", - "parts": [ - { - "id": "pl-1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, a policy that addresses Planning MUST be associated with PL-1 part a.", - "class": "policy" - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, at least one procedure that addresses Planning MUST be associated with PL-1 part a.", - "class": "procedure" - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, document, and disseminate to {{ insert: param, pl-1_prm_1 }}:", - "parts": [ - { - "id": "pl-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, pl-01_odp.03 }} planning policy that:", - "parts": [ - { - "id": "pl-1_smt.a.1.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "pl-1_smt.a.1.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and" - } - ] - }, - { - "id": "pl-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the planning policy and the associated planning controls;" - } - ] - }, - { - "id": "pl-1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Designate an {{ insert: param, pl-01_odp.04 }} to manage the development, documentation, and dissemination of the planning policy and procedures; and" - }, - { - "id": "pl-1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the current planning:", - "parts": [ - { - "id": "pl-1_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Policy {{ insert: param, pl-01_odp.05 }} and following {{ insert: param, pl-01_odp.06 }} ; and" - }, - { - "id": "pl-1_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures {{ insert: param, pl-01_odp.07 }} and following {{ insert: param, pl-01_odp.08 }}." - } - ] - } - ] - }, - { - "id": "pl-1_gdn", - "name": "guidance", - "prose": "Planning policy and procedures for the controls in the PL family implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on their development. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission level or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission/business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to planning policy and procedures include, but are not limited to, assessment or audit findings, security incidents or breaches, or changes in laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure." - }, - { - "id": "pl-1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-01a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-01a.[01]", - "class": "sp800-53a" - } - ], - "prose": "a planning policy is developed and documented.", - "links": [ - { - "href": "#pl-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-01a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the planning policy is disseminated to {{ insert: param, pl-01_odp.01 }};", - "links": [ - { - "href": "#pl-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-1_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-01a.[03]", - "class": "sp800-53a" - } - ], - "prose": "planning procedures to facilitate the implementation of the planning policy and associated planning controls are developed and documented;", - "links": [ - { - "href": "#pl-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-1_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-01a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the planning procedures are disseminated to {{ insert: param, pl-01_odp.02 }};", - "links": [ - { - "href": "#pl-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-1_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-01a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-1_obj.a.1.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-01a.01(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-1_obj.a.1.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-01a.01(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, pl-01_odp.03 }} planning policy addresses purpose;", - "links": [ - { - "href": "#pl-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-1_obj.a.1.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-01a.01(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, pl-01_odp.03 }} planning policy addresses scope;", - "links": [ - { - "href": "#pl-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-1_obj.a.1.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-01a.01(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, pl-01_odp.03 }} planning policy addresses roles;", - "links": [ - { - "href": "#pl-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-1_obj.a.1.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-01a.01(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, pl-01_odp.03 }} planning policy addresses responsibilities;", - "links": [ - { - "href": "#pl-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-1_obj.a.1.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-01a.01(a)[05]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, pl-01_odp.03 }} planning policy addresses management commitment;", - "links": [ - { - "href": "#pl-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-1_obj.a.1.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-01a.01(a)[06]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, pl-01_odp.03 }} planning policy addresses coordination among organizational entities;", - "links": [ - { - "href": "#pl-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-1_obj.a.1.a-7", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-01a.01(a)[07]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, pl-01_odp.03 }} planning policy addresses compliance;", - "links": [ - { - "href": "#pl-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-1_obj.a.1.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-01a.01(b)", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, pl-01_odp.03 }} planning policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines;", - "links": [ - { - "href": "#pl-1_smt.a.1.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-1_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-01b.", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, pl-01_odp.04 }} is designated to manage the development, documentation, and dissemination of the planning policy and procedures;", - "links": [ - { - "href": "#pl-1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-01c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-1_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-01c.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-1_obj.c.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-01c.01[01]", - "class": "sp800-53a" - } - ], - "prose": "the current planning policy is reviewed and updated {{ insert: param, pl-01_odp.05 }};", - "links": [ - { - "href": "#pl-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-1_obj.c.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-01c.01[02]", - "class": "sp800-53a" - } - ], - "prose": "the current planning policy is reviewed and updated following {{ insert: param, pl-01_odp.06 }};", - "links": [ - { - "href": "#pl-1_smt.c.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-1_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-01c.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-1_obj.c.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-01c.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the current planning procedures are reviewed and updated {{ insert: param, pl-01_odp.07 }};", - "links": [ - { - "href": "#pl-1_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-1_obj.c.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-01c.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the current planning procedures are reviewed and updated following {{ insert: param, pl-01_odp.08 }}.", - "links": [ - { - "href": "#pl-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-1_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PL-01-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Planning policy and procedures\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pl-1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PL-01-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with planning responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - }, - { - "id": "pl-2", - "class": "SP800-53", - "title": "System Security and Privacy Plans", - "params": [ - { - "id": "pl-02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "pl-2_prm_1" - }, - { - "name": "label", - "value": "PL-02_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "individuals or groups", - "constraints": [ - { - "description": "to include chief privacy and ISSO and/or similar role or designees" - } - ], - "guidelines": [ - { - "prose": "individuals or groups with whom security and privacy-related activities affecting the system that require planning and coordination is/are assigned;" - } - ] - }, - { - "id": "pl-02_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "pl-2_prm_2" - }, - { - "name": "label", - "value": "PL-02_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "constraints": [ - { - "description": "to include chief privacy and ISSO and/or similar role" - } - ], - "guidelines": [ - { - "prose": "personnel or roles to receive distributed copies of the system security and privacy plans is/are assigned;" - } - ] - }, - { - "id": "pl-02_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "pl-2_prm_3" - }, - { - "name": "label", - "value": "PL-02_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "frequency to review system security and privacy plans is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PL-02", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PL-2" - }, - { - "name": "label", - "value": "PL-02", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pl-02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#30eb758a-2707-4bca-90ad-949a74d4eb16", - "rel": "reference" - }, - { - "href": "#482e4c99-9dc4-41ad-bba8-0f3f0032c1f8", - "rel": "reference" - }, - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "#61ccf0f4-d3e7-42db-9796-ce6cb1c85989", - "rel": "reference" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ac-14", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-20", - "rel": "related" - }, - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-3", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#cm-13", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-4", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#ma-5", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pl-7", - "rel": "related" - }, - { - "href": "#pl-8", - "rel": "related" - }, - { - "href": "#pl-10", - "rel": "related" - }, - { - "href": "#pl-11", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-1", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-10", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-11", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ra-8", - "rel": "related" - }, - { - "href": "#ra-9", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-17", - "rel": "related" - }, - { - "href": "#sa-22", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - }, - { - "href": "#sr-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sr-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "pl-2_smt", - "name": "statement", - "parts": [ - { - "id": "pl-2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop security and privacy plans for the system that:", - "parts": [ - { - "id": "pl-2_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Are consistent with the organization’s enterprise architecture;" - }, - { - "id": "pl-2_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Explicitly define the constituent system components;" - }, - { - "id": "pl-2_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Describe the operational context of the system in terms of mission and business processes;" - }, - { - "id": "pl-2_smt.a.4", - "name": "item", - "props": [ - { - "name": "label", - "value": "4." - } - ], - "prose": "Identify the individuals that fulfill system roles and responsibilities;" - }, - { - "id": "pl-2_smt.a.5", - "name": "item", - "props": [ - { - "name": "label", - "value": "5." - } - ], - "prose": "Identify the information types processed, stored, and transmitted by the system;" - }, - { - "id": "pl-2_smt.a.6", - "name": "item", - "props": [ - { - "name": "label", - "value": "6." - } - ], - "prose": "Provide the security categorization of the system, including supporting rationale;" - }, - { - "id": "pl-2_smt.a.7", - "name": "item", - "props": [ - { - "name": "label", - "value": "7." - } - ], - "prose": "Describe any specific threats to the system that are of concern to the organization;" - }, - { - "id": "pl-2_smt.a.8", - "name": "item", - "props": [ - { - "name": "label", - "value": "8." - } - ], - "prose": "Provide the results of a privacy risk assessment for systems processing personally identifiable information;" - }, - { - "id": "pl-2_smt.a.9", - "name": "item", - "props": [ - { - "name": "label", - "value": "9." - } - ], - "prose": "Describe the operational environment for the system and any dependencies on or connections to other systems or system components;" - }, - { - "id": "pl-2_smt.a.10", - "name": "item", - "props": [ - { - "name": "label", - "value": "10." - } - ], - "prose": "Provide an overview of the security and privacy requirements for the system;" - }, - { - "id": "pl-2_smt.a.11", - "name": "item", - "props": [ - { - "name": "label", - "value": "11." - } - ], - "prose": "Identify any relevant control baselines or overlays, if applicable;" - }, - { - "id": "pl-2_smt.a.12", - "name": "item", - "props": [ - { - "name": "label", - "value": "12." - } - ], - "prose": "Describe the controls in place or planned for meeting the security and privacy requirements, including a rationale for any tailoring decisions;" - }, - { - "id": "pl-2_smt.a.13", - "name": "item", - "props": [ - { - "name": "label", - "value": "13." - } - ], - "prose": "Include risk determinations for security and privacy architecture and design decisions;" - }, - { - "id": "pl-2_smt.a.14", - "name": "item", - "props": [ - { - "name": "label", - "value": "14." - } - ], - "prose": "Include security- and privacy-related activities affecting the system that require planning and coordination with {{ insert: param, pl-02_odp.01 }} ; and" - }, - { - "id": "pl-2_smt.a.15", - "name": "item", - "props": [ - { - "name": "label", - "value": "15." - } - ], - "prose": "Are reviewed and approved by the authorizing official or designated representative prior to plan implementation." - } - ] - }, - { - "id": "pl-2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Distribute copies of the plans and communicate subsequent changes to the plans to {{ insert: param, pl-02_odp.02 }};" - }, - { - "id": "pl-2_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review the plans {{ insert: param, pl-02_odp.03 }};" - }, - { - "id": "pl-2_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Update the plans to address changes to the system and environment of operation or problems identified during plan implementation or control assessments; and" - }, - { - "id": "pl-2_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Protect the plans from unauthorized disclosure and modification." - } - ] - }, - { - "id": "pl-2_gdn", - "name": "guidance", - "prose": "System security and privacy plans are scoped to the system and system components within the defined authorization boundary and contain an overview of the security and privacy requirements for the system and the controls selected to satisfy the requirements. The plans describe the intended application of each selected control in the context of the system with a sufficient level of detail to correctly implement the control and to subsequently assess the effectiveness of the control. The control documentation describes how system-specific and hybrid controls are implemented and the plans and expectations regarding the functionality of the system. System security and privacy plans can also be used in the design and development of systems in support of life cycle-based security and privacy engineering processes. System security and privacy plans are living documents that are updated and adapted throughout the system development life cycle (e.g., during capability determination, analysis of alternatives, requests for proposal, and design reviews). [Section 2.1](#c3397cc9-83c6-4459-adb2-836739dc1b94) describes the different types of requirements that are relevant to organizations during the system development life cycle and the relationship between requirements and controls.\n\nOrganizations may develop a single, integrated security and privacy plan or maintain separate plans. Security and privacy plans relate security and privacy requirements to a set of controls and control enhancements. The plans describe how the controls and control enhancements meet the security and privacy requirements but do not provide detailed, technical descriptions of the design or implementation of the controls and control enhancements. Security and privacy plans contain sufficient information (including specifications of control parameter values for selection and assignment operations explicitly or by reference) to enable a design and implementation that is unambiguously compliant with the intent of the plans and subsequent determinations of risk to organizational operations and assets, individuals, other organizations, and the Nation if the plan is implemented.\n\nSecurity and privacy plans need not be single documents. The plans can be a collection of various documents, including documents that already exist. Effective security and privacy plans make extensive use of references to policies, procedures, and additional documents, including design and implementation specifications where more detailed information can be obtained. The use of references helps reduce the documentation associated with security and privacy programs and maintains the security- and privacy-related information in other established management and operational areas, including enterprise architecture, system development life cycle, systems engineering, and acquisition. Security and privacy plans need not contain detailed contingency plan or incident response plan information but can instead provide—explicitly or by reference—sufficient information to define what needs to be accomplished by those plans.\n\nSecurity- and privacy-related activities that may require coordination and planning with other individuals or groups within the organization include assessments, audits, inspections, hardware and software maintenance, acquisition and supply chain risk management, patch management, and contingency plan testing. Planning and coordination include emergency and nonemergency (i.e., planned or non-urgent unplanned) situations. The process defined by organizations to plan and coordinate security- and privacy-related activities can also be included in other documents, as appropriate." - }, - { - "id": "pl-2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.a.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.01[01]", - "class": "sp800-53a" - } - ], - "prose": "a security plan for the system is developed that is consistent with the organization’s enterprise architecture;", - "links": [ - { - "href": "#pl-2_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.01[02]", - "class": "sp800-53a" - } - ], - "prose": "a privacy plan for the system is developed that is consistent with the organization’s enterprise architecture;", - "links": [ - { - "href": "#pl-2_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.a.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.02[01]", - "class": "sp800-53a" - } - ], - "prose": "a security plan for the system is developed that explicitly defines the constituent system components;", - "links": [ - { - "href": "#pl-2_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.02[02]", - "class": "sp800-53a" - } - ], - "prose": "a privacy plan for the system is developed that explicitly defines the constituent system components;", - "links": [ - { - "href": "#pl-2_smt.a.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.a.3-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.03[01]", - "class": "sp800-53a" - } - ], - "prose": "a security plan for the system is developed that describes the operational context of the system in terms of mission and business processes;", - "links": [ - { - "href": "#pl-2_smt.a.3", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.3-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.03[02]", - "class": "sp800-53a" - } - ], - "prose": "a privacy plan for the system is developed that describes the operational context of the system in terms of mission and business processes;", - "links": [ - { - "href": "#pl-2_smt.a.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt.a.3", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.04", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.a.4-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.04[01]", - "class": "sp800-53a" - } - ], - "prose": "a security plan for the system is developed that identifies the individuals that fulfill system roles and responsibilities;", - "links": [ - { - "href": "#pl-2_smt.a.4", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.4-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.04[02]", - "class": "sp800-53a" - } - ], - "prose": "a privacy plan for the system is developed that identifies the individuals that fulfill system roles and responsibilities;", - "links": [ - { - "href": "#pl-2_smt.a.4", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt.a.4", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.5", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.05", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.a.5-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.05[01]", - "class": "sp800-53a" - } - ], - "prose": "a security plan for the system is developed that identifies the information types processed, stored, and transmitted by the system;", - "links": [ - { - "href": "#pl-2_smt.a.5", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.5-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.05[02]", - "class": "sp800-53a" - } - ], - "prose": "a privacy plan for the system is developed that identifies the information types processed, stored, and transmitted by the system;", - "links": [ - { - "href": "#pl-2_smt.a.5", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt.a.5", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.6", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.06", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.a.6-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.06[01]", - "class": "sp800-53a" - } - ], - "prose": "a security plan for the system is developed that provides the security categorization of the system, including supporting rationale;", - "links": [ - { - "href": "#pl-2_smt.a.6", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.6-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.06[02]", - "class": "sp800-53a" - } - ], - "prose": "a privacy plan for the system is developed that provides the security categorization of the system, including supporting rationale;", - "links": [ - { - "href": "#pl-2_smt.a.6", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt.a.6", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.7", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.07", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.a.7-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.07[01]", - "class": "sp800-53a" - } - ], - "prose": "a security plan for the system is developed that describes any specific threats to the system that are of concern to the organization;", - "links": [ - { - "href": "#pl-2_smt.a.7", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.7-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.07[02]", - "class": "sp800-53a" - } - ], - "prose": "a privacy plan for the system is developed that describes any specific threats to the system that are of concern to the organization;", - "links": [ - { - "href": "#pl-2_smt.a.7", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt.a.7", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.8", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.08", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.a.8-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.08[01]", - "class": "sp800-53a" - } - ], - "prose": "a security plan for the system is developed that provides the results of a privacy risk assessment for systems processing personally identifiable information;", - "links": [ - { - "href": "#pl-2_smt.a.8", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.8-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.08[02]", - "class": "sp800-53a" - } - ], - "prose": "a privacy plan for the system is developed that provides the results of a privacy risk assessment for systems processing personally identifiable information;", - "links": [ - { - "href": "#pl-2_smt.a.8", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt.a.8", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.9", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.09", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.a.9-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.09[01]", - "class": "sp800-53a" - } - ], - "prose": "a security plan for the system is developed that describes the operational environment for the system and any dependencies on or connections to other systems or system components;", - "links": [ - { - "href": "#pl-2_smt.a.9", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.9-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.09[02]", - "class": "sp800-53a" - } - ], - "prose": "a privacy plan for the system is developed that describes the operational environment for the system and any dependencies on or connections to other systems or system components;", - "links": [ - { - "href": "#pl-2_smt.a.9", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt.a.9", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.10", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.10", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.a.10-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.10[01]", - "class": "sp800-53a" - } - ], - "prose": "a security plan for the system is developed that provides an overview of the security requirements for the system;", - "links": [ - { - "href": "#pl-2_smt.a.10", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.10-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.10[02]", - "class": "sp800-53a" - } - ], - "prose": "a privacy plan for the system is developed that provides an overview of the privacy requirements for the system;", - "links": [ - { - "href": "#pl-2_smt.a.10", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt.a.10", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.11", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.11", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.a.11-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.11[01]", - "class": "sp800-53a" - } - ], - "prose": "a security plan for the system is developed that identifies any relevant control baselines or overlays, if applicable;", - "links": [ - { - "href": "#pl-2_smt.a.11", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.11-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.11[02]", - "class": "sp800-53a" - } - ], - "prose": "a privacy plan for the system is developed that identifies any relevant control baselines or overlays, if applicable;", - "links": [ - { - "href": "#pl-2_smt.a.11", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt.a.11", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.12", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.12", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.a.12-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.12[01]", - "class": "sp800-53a" - } - ], - "prose": "a security plan for the system is developed that describes the controls in place or planned for meeting the security requirements, including rationale for any tailoring decisions;", - "links": [ - { - "href": "#pl-2_smt.a.12", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.12-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.12[02]", - "class": "sp800-53a" - } - ], - "prose": "a privacy plan for the system is developed that describes the controls in place or planned for meeting the privacy requirements, including rationale for any tailoring decisions;", - "links": [ - { - "href": "#pl-2_smt.a.12", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt.a.12", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.13", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.13", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.a.13-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.13[01]", - "class": "sp800-53a" - } - ], - "prose": "a security plan for the system is developed that includes risk determinations for security architecture and design decisions;", - "links": [ - { - "href": "#pl-2_smt.a.13", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.13-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.13[02]", - "class": "sp800-53a" - } - ], - "prose": "a privacy plan for the system is developed that includes risk determinations for privacy architecture and design decisions;", - "links": [ - { - "href": "#pl-2_smt.a.13", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt.a.13", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.14", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.14", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.a.14-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.14[01]", - "class": "sp800-53a" - } - ], - "prose": "a security plan for the system is developed that includes security-related activities affecting the system that require planning and coordination with {{ insert: param, pl-02_odp.01 }};", - "links": [ - { - "href": "#pl-2_smt.a.14", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.14-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.14[02]", - "class": "sp800-53a" - } - ], - "prose": "a privacy plan for the system is developed that includes privacy-related activities affecting the system that require planning and coordination with {{ insert: param, pl-02_odp.01 }};", - "links": [ - { - "href": "#pl-2_smt.a.14", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt.a.14", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.15", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02a.15", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.a.15-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.15[01]", - "class": "sp800-53a" - } - ], - "prose": "a security plan for the system is developed that is reviewed and approved by the authorizing official or designated representative prior to plan implementation;", - "links": [ - { - "href": "#pl-2_smt.a.15", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.a.15-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02a.15[02]", - "class": "sp800-53a" - } - ], - "prose": "a privacy plan for the system is developed that is reviewed and approved by the authorizing official or designated representative prior to plan implementation.", - "links": [ - { - "href": "#pl-2_smt.a.15", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt.a.15", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02b.[01]", - "class": "sp800-53a" - } - ], - "prose": "copies of the plans are distributed to {{ insert: param, pl-02_odp.02 }};", - "links": [ - { - "href": "#pl-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02b.[02]", - "class": "sp800-53a" - } - ], - "prose": "subsequent changes to the plans are communicated to {{ insert: param, pl-02_odp.02 }};", - "links": [ - { - "href": "#pl-2_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02c.", - "class": "sp800-53a" - } - ], - "prose": "plans are reviewed {{ insert: param, pl-02_odp.03 }};", - "links": [ - { - "href": "#pl-2_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02d.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.d-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02d.[01]", - "class": "sp800-53a" - } - ], - "prose": "plans are updated to address changes to the system and environment of operations;", - "links": [ - { - "href": "#pl-2_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.d-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02d.[02]", - "class": "sp800-53a" - } - ], - "prose": "plans are updated to address problems identified during the plan implementation;", - "links": [ - { - "href": "#pl-2_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.d-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02d.[03]", - "class": "sp800-53a" - } - ], - "prose": "plans are updated to address problems identified during control assessments;", - "links": [ - { - "href": "#pl-2_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-02e.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-2_obj.e-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02e.[01]", - "class": "sp800-53a" - } - ], - "prose": "plans are protected from unauthorized disclosure;", - "links": [ - { - "href": "#pl-2_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_obj.e-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-02e.[02]", - "class": "sp800-53a" - } - ], - "prose": "plans are protected from unauthorized modification.", - "links": [ - { - "href": "#pl-2_smt.e", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt.e", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PL-02-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Security and privacy planning policy\n\nprocedures addressing system security and privacy plan development and implementation\n\nprocedures addressing security and privacy plan reviews and updates\n\nenterprise architecture documentation\n\nsystem security plan\n\nprivacy plan\n\nrecords of system security and privacy plan reviews and updates\n\nsecurity and privacy architecture and design documentation\n\nrisk assessments\n\nrisk assessment results\n\ncontrol assessment documentation\n\nother relevant documents or records" - } - ] - }, - { - "id": "pl-2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PL-02-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system security and privacy planning and plan implementation responsibilities\n\nsystem developers\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "pl-2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PL-02-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for system security and privacy plan development, review, update, and approval\n\nmechanisms supporting the system security and privacy plan" - } - ] - } - ] - }, - { - "id": "pl-4", - "class": "SP800-53", - "title": "Rules of Behavior", - "params": [ - { - "id": "pl-04_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "pl-4_prm_1" - }, - { - "name": "label", - "value": "PL-04_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "frequency for reviewing and updating the rules of behavior is defined;" - } - ] - }, - { - "id": "pl-04_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "pl-4_prm_2" - }, - { - "name": "label", - "value": "PL-04_ODP[02]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "at least annually and when the rules are revised or changed" - } - ] - }, - { - "id": "pl-04_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "pl-4_prm_3" - }, - { - "name": "label", - "value": "PL-04_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "guidelines": [ - { - "prose": "frequency for individuals to read and re-acknowledge the rules of behavior is defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PL-04", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PL-4" - }, - { - "name": "label", - "value": "PL-04", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pl-04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#30eb758a-2707-4bca-90ad-949a74d4eb16", - "rel": "reference" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ac-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ac-9", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#ac-20", - "rel": "related" - }, - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#cm-11", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#mp-7", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "pl-4_smt", - "name": "statement", - "parts": [ - { - "id": "pl-4_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Establish and provide to individuals requiring access to the system, the rules that describe their responsibilities and expected behavior for information and system usage, security, and privacy;" - }, - { - "id": "pl-4_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Receive a documented acknowledgment from such individuals, indicating that they have read, understand, and agree to abide by the rules of behavior, before authorizing access to information and the system;" - }, - { - "id": "pl-4_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the rules of behavior {{ insert: param, pl-04_odp.01 }} ; and" - }, - { - "id": "pl-4_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Require individuals who have acknowledged a previous version of the rules of behavior to read and re-acknowledge {{ insert: param, pl-04_odp.02 }}." - } - ] - }, - { - "id": "pl-4_gdn", - "name": "guidance", - "prose": "Rules of behavior represent a type of access agreement for organizational users. Other types of access agreements include nondisclosure agreements, conflict-of-interest agreements, and acceptable use agreements (see [PS-6](#ps-6) ). Organizations consider rules of behavior based on individual user roles and responsibilities and differentiate between rules that apply to privileged users and rules that apply to general users. Establishing rules of behavior for some types of non-organizational users, including individuals who receive information from federal systems, is often not feasible given the large number of such users and the limited nature of their interactions with the systems. Rules of behavior for organizational and non-organizational users can also be established in [AC-8](#ac-8) . The related controls section provides a list of controls that are relevant to organizational rules of behavior. [PL-4b](#pl-4_smt.b) , the documented acknowledgment portion of the control, may be satisfied by the literacy training and awareness and role-based training programs conducted by organizations if such training includes rules of behavior. Documented acknowledgements for rules of behavior include electronic or physical signatures and electronic agreement check boxes or radio buttons." - }, - { - "id": "pl-4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-04", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-4_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-04a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-4_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-04a.[01]", - "class": "sp800-53a" - } - ], - "prose": "rules that describe responsibilities and expected behavior for information and system usage, security, and privacy are established for individuals requiring access to the system;", - "links": [ - { - "href": "#pl-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-4_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-04a.[02]", - "class": "sp800-53a" - } - ], - "prose": "rules that describe responsibilities and expected behavior for information and system usage, security, and privacy are provided to individuals requiring access to the system;", - "links": [ - { - "href": "#pl-4_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-4_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-04b.", - "class": "sp800-53a" - } - ], - "prose": "before authorizing access to information and the system, a documented acknowledgement from such individuals indicating that they have read, understand, and agree to abide by the rules of behavior is received;", - "links": [ - { - "href": "#pl-4_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-4_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-04c.", - "class": "sp800-53a" - } - ], - "prose": "rules of behavior are reviewed and updated {{ insert: param, pl-04_odp.01 }};", - "links": [ - { - "href": "#pl-4_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-4_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-04d.", - "class": "sp800-53a" - } - ], - "prose": "individuals who have acknowledged a previous version of the rules of behavior are required to read and reacknowledge {{ insert: param, pl-04_odp.02 }}.", - "links": [ - { - "href": "#pl-4_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PL-04-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Security and privacy planning policy\n\nprocedures addressing rules of behavior for system users\n\nrules of behavior\n\nsigned acknowledgements\n\nrecords for rules of behavior reviews and updates\n\nother relevant documents or records" - } - ] - }, - { - "id": "pl-4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PL-04-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibility for establishing, reviewing, and updating rules of behavior\n\norganizational personnel with responsibility for literacy training and awareness and role-based training\n\norganizational personnel who are authorized users of the system and have signed and resigned rules of behavior\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "pl-4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PL-04-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for establishing, reviewing, disseminating, and updating rules of behavior\n\nmechanisms supporting and/or implementing the establishment, review, dissemination, and update of rules of behavior" - } - ] - } - ], - "controls": [ - { - "id": "pl-4.1", - "class": "SP800-53-enhancement", - "title": "Social Media and External Site/Application Usage Restrictions", - "props": [ - { - "name": "label", - "value": "PL-04(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PL-4(1)" - }, - { - "name": "label", - "value": "PL-04(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pl-04.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#pl-4", - "rel": "required" - }, - { - "href": "#ac-22", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-13", - "rel": "related" - } - ], - "parts": [ - { - "id": "pl-4.1_smt", - "name": "statement", - "prose": "Include in the rules of behavior, restrictions on:", - "parts": [ - { - "id": "pl-4.1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Use of social media, social networking sites, and external sites/applications;" - }, - { - "id": "pl-4.1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Posting organizational information on public websites; and" - }, - { - "id": "pl-4.1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Use of organization-provided identifiers (e.g., email addresses) and authentication secrets (e.g., passwords) for creating accounts on external sites/applications." - } - ] - }, - { - "id": "pl-4.1_gdn", - "name": "guidance", - "prose": "Social media, social networking, and external site/application usage restrictions address rules of behavior related to the use of social media, social networking, and external sites when organizational personnel are using such sites for official duties or in the conduct of official business, when organizational information is involved in social media and social networking transactions, and when personnel access social media and networking sites from organizational systems. Organizations also address specific rules that prevent unauthorized entities from obtaining non-public organizational information from social media and networking sites either directly or through inference. Non-public information includes personally identifiable information and system account information." - }, - { - "id": "pl-4.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-04(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-4.1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-04(01)(a)", - "class": "sp800-53a" - } - ], - "prose": "the rules of behavior include restrictions on the use of social media, social networking sites, and external sites/applications;", - "links": [ - { - "href": "#pl-4.1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-4.1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-04(01)(b)", - "class": "sp800-53a" - } - ], - "prose": "the rules of behavior include restrictions on posting organizational information on public websites;", - "links": [ - { - "href": "#pl-4.1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-4.1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-04(01)(c)", - "class": "sp800-53a" - } - ], - "prose": "the rules of behavior include restrictions on the use of organization-provided identifiers (e.g., email addresses) and authentication secrets (e.g., passwords) for creating accounts on external sites/applications.", - "links": [ - { - "href": "#pl-4.1_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-4.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-4.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PL-04(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Security and privacy planning policy\n\nprocedures addressing rules of behavior for system users\n\nrules of behavior\n\ntraining policy\n\nother relevant documents or records" - } - ] - }, - { - "id": "pl-4.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PL-04(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with responsibility for establishing, reviewing, and updating rules of behavior\n\norganizational personnel with responsibility for literacy training and awareness and role-based training\n\norganizational personnel who are authorized users of the system and have signed rules of behavior\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "pl-4.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PL-04(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for establishing rules of behavior\n\nmechanisms supporting and/or implementing the establishment of rules of behavior" - } - ] - } - ] - } - ] - }, - { - "id": "pl-8", - "class": "SP800-53", - "title": "Security and Privacy Architectures", - "params": [ - { - "id": "pl-08_odp", - "props": [ - { - "name": "alt-identifier", - "value": "pl-8_prm_1" - }, - { - "name": "label", - "value": "PL-08_ODP", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually and when a significant change occurs" - } - ], - "guidelines": [ - { - "prose": "frequency for review and update to reflect changes in the enterprise architecture;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PL-08", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PL-8" - }, - { - "name": "label", - "value": "PL-08", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pl-08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "#61ccf0f4-d3e7-42db-9796-ce6cb1c85989", - "rel": "reference" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pl-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pl-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-5", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-7", - "rel": "related" - }, - { - "href": "#ra-9", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-17", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "pl-8_smt", - "name": "statement", - "parts": [ - { - "id": "pl-8_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop security and privacy architectures for the system that:", - "parts": [ - { - "id": "pl-8_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Describe the requirements and approach to be taken for protecting the confidentiality, integrity, and availability of organizational information;" - }, - { - "id": "pl-8_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Describe the requirements and approach to be taken for processing personally identifiable information to minimize privacy risk to individuals;" - }, - { - "id": "pl-8_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Describe how the architectures are integrated into and support the enterprise architecture; and" - }, - { - "id": "pl-8_smt.a.4", - "name": "item", - "props": [ - { - "name": "label", - "value": "4." - } - ], - "prose": "Describe any assumptions about, and dependencies on, external systems and services;" - } - ] - }, - { - "id": "pl-8_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Review and update the architectures {{ insert: param, pl-08_odp }} to reflect changes in the enterprise architecture; and" - }, - { - "id": "pl-8_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Reflect planned architecture changes in security and privacy plans, Concept of Operations (CONOPS), criticality analysis, organizational procedures, and procurements and acquisitions." - } - ] - }, - { - "id": "pl-8_gdn", - "name": "guidance", - "prose": "The security and privacy architectures at the system level are consistent with the organization-wide security and privacy architectures described in [PM-7](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-7) , which are integral to and developed as part of the enterprise architecture. The architectures include an architectural description, the allocation of security and privacy functionality (including controls), security- and privacy-related information for external interfaces, information being exchanged across the interfaces, and the protection mechanisms associated with each interface. The architectures can also include other information, such as user roles and the access privileges assigned to each role; security and privacy requirements; types of information processed, stored, and transmitted by the system; supply chain risk management requirements; restoration priorities of information and system services; and other protection needs.\n\n[SP 800-160-1](#e3cc0520-a366-4fc9-abc2-5272db7e3564) provides guidance on the use of security architectures as part of the system development life cycle process. [OMB M-19-03](#c5e11048-1d38-4af3-b00b-0d88dc26860c) requires the use of the systems security engineering concepts described in [SP 800-160-1](#e3cc0520-a366-4fc9-abc2-5272db7e3564) for high value assets. Security and privacy architectures are reviewed and updated throughout the system development life cycle, from analysis of alternatives through review of the proposed architecture in the RFP responses to the design reviews before and during implementation (e.g., during preliminary design reviews and critical design reviews).\n\nIn today’s modern computing architectures, it is becoming less common for organizations to control all information resources. There may be key dependencies on external information services and service providers. Describing such dependencies in the security and privacy architectures is necessary for developing a comprehensive mission and business protection strategy. Establishing, developing, documenting, and maintaining under configuration control a baseline configuration for organizational systems is critical to implementing and maintaining effective architectures. The development of the architectures is coordinated with the senior agency information security officer and the senior agency official for privacy to ensure that the controls needed to support security and privacy requirements are identified and effectively implemented. In many circumstances, there may be no distinction between the security and privacy architecture for a system. In other circumstances, security objectives may be adequately satisfied, but privacy objectives may only be partially satisfied by the security requirements. In these cases, consideration of the privacy requirements needed to achieve satisfaction will result in a distinct privacy architecture. The documentation, however, may simply reflect the combined architectures.\n\n[PL-8](#pl-8) is primarily directed at organizations to ensure that architectures are developed for the system and, moreover, that the architectures are integrated with or tightly coupled to the enterprise architecture. In contrast, [SA-17](#sa-17) is primarily directed at the external information technology product and system developers and integrators. [SA-17](#sa-17) , which is complementary to [PL-8](#pl-8) , is selected when organizations outsource the development of systems or components to external entities and when there is a need to demonstrate consistency with the organization’s enterprise architecture and security and privacy architectures." - }, - { - "id": "pl-8_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "PL-8 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "pl-8_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(b) Guidance:" - } - ], - "prose": "Significant change is defined in NIST Special Publication 800-37 Revision 2, Appendix F." - } - ] - }, - { - "id": "pl-8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-08", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-8_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-08a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-8_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-08a.01", - "class": "sp800-53a" - } - ], - "prose": "a security architecture for the system describes the requirements and approach to be taken for protecting the confidentiality, integrity, and availability of organizational information;", - "links": [ - { - "href": "#pl-8_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-8_obj.a.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-08a.02", - "class": "sp800-53a" - } - ], - "prose": "a privacy architecture describes the requirements and approach to be taken for processing personally identifiable information to minimize privacy risk to individuals;", - "links": [ - { - "href": "#pl-8_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-8_obj.a.3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-08a.03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-8_obj.a.3-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-08a.03[01]", - "class": "sp800-53a" - } - ], - "prose": "a security architecture for the system describes how the architecture is integrated into and supports the enterprise architecture;", - "links": [ - { - "href": "#pl-8_smt.a.3", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-8_obj.a.3-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-08a.03[02]", - "class": "sp800-53a" - } - ], - "prose": "a privacy architecture for the system describes how the architecture is integrated into and supports the enterprise architecture;", - "links": [ - { - "href": "#pl-8_smt.a.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-8_smt.a.3", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-8_obj.a.4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-08a.04", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-8_obj.a.4-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-08a.04[01]", - "class": "sp800-53a" - } - ], - "prose": "a security architecture for the system describes any assumptions about and dependencies on external systems and services;", - "links": [ - { - "href": "#pl-8_smt.a.4", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-8_obj.a.4-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-08a.04[02]", - "class": "sp800-53a" - } - ], - "prose": "a privacy architecture for the system describes any assumptions about and dependencies on external systems and services;", - "links": [ - { - "href": "#pl-8_smt.a.4", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-8_smt.a.4", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-8_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-8_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-08b.", - "class": "sp800-53a" - } - ], - "prose": "changes in the enterprise architecture are reviewed and updated {{ insert: param, pl-08_odp }} to reflect changes in the enterprise architecture;", - "links": [ - { - "href": "#pl-8_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-8_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PL-08c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "pl-8_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-08c.[01]", - "class": "sp800-53a" - } - ], - "prose": "planned architecture changes are reflected in the security plan;", - "links": [ - { - "href": "#pl-8_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-8_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-08c.[02]", - "class": "sp800-53a" - } - ], - "prose": "planned architecture changes are reflected in the privacy plan;", - "links": [ - { - "href": "#pl-8_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-8_obj.c-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-08c.[03]", - "class": "sp800-53a" - } - ], - "prose": "planned architecture changes are reflected in the Concept of Operations (CONOPS);", - "links": [ - { - "href": "#pl-8_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-8_obj.c-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-08c.[04]", - "class": "sp800-53a" - } - ], - "prose": "planned architecture changes are reflected in criticality analysis;", - "links": [ - { - "href": "#pl-8_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-8_obj.c-5", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-08c.[05]", - "class": "sp800-53a" - } - ], - "prose": "planned architecture changes are reflected in organizational procedures;", - "links": [ - { - "href": "#pl-8_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-8_obj.c-6", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-08c.[06]", - "class": "sp800-53a" - } - ], - "prose": "planned architecture changes are reflected in procurements and acquisitions.", - "links": [ - { - "href": "#pl-8_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-8_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#pl-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PL-08-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Security and privacy planning policy\n\nprocedures addressing information security and privacy architecture development\n\nprocedures addressing information security and privacy architecture reviews and updates\n\nenterprise architecture documentation\n\ninformation security and privacy architecture documentation\n\nsystem security plan\n\nprivacy plan\n\nsecurity and privacy CONOPS for the system\n\nrecords of information security and privacy architecture reviews and updates\n\nother relevant documents or records" - } - ] - }, - { - "id": "pl-8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PL-08-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with security and privacy planning and plan implementation responsibilities\n\norganizational personnel with information security and privacy architecture development responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "pl-8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PL-08-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for developing, reviewing, and updating the information security and privacy architecture\n\nmechanisms supporting and/or implementing the development, review, and update of the information security and privacy architecture" - } - ] - } - ] - }, - { - "id": "pl-10", - "class": "SP800-53", - "title": "Baseline Selection", - "props": [ - { - "name": "label", - "value": "PL-10", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PL-10" - }, - { - "name": "label", - "value": "PL-10", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pl-10" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#628d22a1-6a11-4784-bc59-5cd9497b5445", - "rel": "reference" - }, - { - "href": "#599fb53d-5041-444e-a7fe-640d6d30ad05", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#482e4c99-9dc4-41ad-bba8-0f3f0032c1f8", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#46d9e201-840e-440e-987c-2c773333c752", - "rel": "reference" - }, - { - "href": "#e72fde0b-6fc2-497e-a9db-d8fce5a11b8a", - "rel": "reference" - }, - { - "href": "#9be5d661-421f-41ad-854e-86f98b811891", - "rel": "reference" - }, - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "#4e4fbc93-333d-45e6-a875-de36b878b6b9", - "rel": "reference" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#pl-11", - "rel": "related" - }, - { - "href": "#ra-2", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - } - ], - "parts": [ - { - "id": "pl-10_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Select a control baseline for the system." - }, - { - "id": "pl-10_gdn", - "name": "guidance", - "prose": "Control baselines are predefined sets of controls specifically assembled to address the protection needs of a group, organization, or community of interest. Controls are chosen for baselines to either satisfy mandates imposed by laws, executive orders, directives, regulations, policies, standards, and guidelines or address threats common to all users of the baseline under the assumptions specific to the baseline. Baselines represent a starting point for the protection of individuals’ privacy, information, and information systems with subsequent tailoring actions to manage risk in accordance with mission, business, or other constraints (see [PL-11](#pl-11) ). Federal control baselines are provided in [SP 800-53B](#46d9e201-840e-440e-987c-2c773333c752) . The selection of a control baseline is determined by the needs of stakeholders. Stakeholder needs consider mission and business requirements as well as mandates imposed by applicable laws, executive orders, directives, policies, regulations, standards, and guidelines. For example, the control baselines in [SP 800-53B](#46d9e201-840e-440e-987c-2c773333c752) are based on the requirements from [FISMA](#0c67b2a9-bede-43d2-b86d-5f35b8be36e9) and [PRIVACT](#18e71fec-c6fd-475a-925a-5d8495cf8455) . The requirements, along with the NIST standards and guidelines implementing the legislation, direct organizations to select one of the control baselines after the reviewing the information types and the information that is processed, stored, and transmitted on the system; analyzing the potential adverse impact of the loss or compromise of the information or system on the organization’s operations and assets, individuals, other organizations, or the Nation; and considering the results from system and organizational risk assessments. [CNSSI 1253](#4e4fbc93-333d-45e6-a875-de36b878b6b9) provides guidance on control baselines for national security systems." - }, - { - "id": "pl-10_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "PL-10 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "pl-10_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Select the appropriate FedRAMP Baseline" - } - ] - }, - { - "id": "pl-10_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-10", - "class": "sp800-53a" - } - ], - "prose": "a control baseline for the system is selected.", - "links": [ - { - "href": "#pl-10_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-10_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PL-10-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Security and privacy planning policy\n\nprocedures addressing system security and privacy plan development and implementation\n\nprocedures addressing system security and privacy plan reviews and updates\n\nsystem design documentation\n\nsystem architecture and configuration documentation\n\nsystem categorization decision\n\ninformation types stored, transmitted, and processed by the system\n\nsystem element/component information\n\nstakeholder needs analysis\n\nlist of security and privacy requirements allocated to the system, system elements, and environment of operation\n\nlist of contractual requirements allocated to external providers of the system or system element\n\nbusiness impact analysis or criticality analysis\n\nrisk assessments\n\nrisk management strategy\n\norganizational security and privacy policy\n\nfederal or organization-approved or mandated baselines or overlays\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "pl-10_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PL-10-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with security and privacy planning and plan implementation responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\norganizational personnel with responsibility for organizational risk management activities" - } - ] - } - ] - }, - { - "id": "pl-11", - "class": "SP800-53", - "title": "Baseline Tailoring", - "props": [ - { - "name": "label", - "value": "PL-11", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PL-11" - }, - { - "name": "label", - "value": "PL-11", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "pl-11" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#628d22a1-6a11-4784-bc59-5cd9497b5445", - "rel": "reference" - }, - { - "href": "#599fb53d-5041-444e-a7fe-640d6d30ad05", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#482e4c99-9dc4-41ad-bba8-0f3f0032c1f8", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#46d9e201-840e-440e-987c-2c773333c752", - "rel": "reference" - }, - { - "href": "#e72fde0b-6fc2-497e-a9db-d8fce5a11b8a", - "rel": "reference" - }, - { - "href": "#9be5d661-421f-41ad-854e-86f98b811891", - "rel": "reference" - }, - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "#4e4fbc93-333d-45e6-a875-de36b878b6b9", - "rel": "reference" - }, - { - "href": "#pl-10", - "rel": "related" - }, - { - "href": "#ra-2", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#ra-9", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - } - ], - "parts": [ - { - "id": "pl-11_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Tailor the selected control baseline by applying specified tailoring actions." - }, - { - "id": "pl-11_gdn", - "name": "guidance", - "prose": "The concept of tailoring allows organizations to specialize or customize a set of baseline controls by applying a defined set of tailoring actions. Tailoring actions facilitate such specialization and customization by allowing organizations to develop security and privacy plans that reflect their specific mission and business functions, the environments where their systems operate, the threats and vulnerabilities that can affect their systems, and any other conditions or situations that can impact their mission or business success. Tailoring guidance is provided in [SP 800-53B](#46d9e201-840e-440e-987c-2c773333c752) . Tailoring a control baseline is accomplished by identifying and designating common controls, applying scoping considerations, selecting compensating controls, assigning values to control parameters, supplementing the control baseline with additional controls as needed, and providing information for control implementation. The general tailoring actions in [SP 800-53B](#46d9e201-840e-440e-987c-2c773333c752) can be supplemented with additional actions based on the needs of organizations. Tailoring actions can be applied to the baselines in [SP 800-53B](#46d9e201-840e-440e-987c-2c773333c752) in accordance with the security and privacy requirements from [FISMA](#0c67b2a9-bede-43d2-b86d-5f35b8be36e9), [PRIVACT](#18e71fec-c6fd-475a-925a-5d8495cf8455) , and [OMB A-130](#27847491-5ce1-4f6a-a1e4-9e483782f0ef) . Alternatively, other communities of interest adopting different control baselines can apply the tailoring actions in [SP 800-53B](#46d9e201-840e-440e-987c-2c773333c752) to specialize or customize the controls that represent the specific needs and concerns of those entities." - }, - { - "id": "pl-11_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PL-11", - "class": "sp800-53a" - } - ], - "prose": "the selected control baseline is tailored by applying specified tailoring actions.", - "links": [ - { - "href": "#pl-11_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "pl-11_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PL-11-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Security and privacy planning policy\n\nprocedures addressing system security and privacy plan development and implementation\n\nsystem design documentation\n\nsystem categorization decision\n\ninformation types stored, transmitted, and processed by the system\n\nsystem element/component information\n\nstakeholder needs analysis\n\nlist of security and privacy requirements allocated to the system, system elements, and environment of operation\n\nlist of contractual requirements allocated to external providers of the system or system element\n\nbusiness impact analysis or criticality analysis\n\nrisk assessments\n\nrisk management strategy\n\norganizational security and privacy policy\n\nfederal or organization-approved or mandated baselines or overlays\n\nbaseline tailoring rationale\n\nsystem security plan\n\nprivacy plan\n\nrecords of system security and privacy plan reviews and updates\n\nother relevant documents or records" - } - ] - }, - { - "id": "pl-11_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PL-11-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with security and privacy planning and plan implementation responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "ps", - "class": "family", - "title": "Personnel Security", - "controls": [ - { - "id": "ps-1", - "class": "SP800-53", - "title": "Policy and Procedures", - "params": [ - { - "id": "ps-1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ps-01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ps-01_odp.02" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "ps-01_odp.01", - "props": [ - { - "name": "label", - "value": "PS-01_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the personnel security policy is to be disseminated is/are defined;" - } - ] - }, - { - "id": "ps-01_odp.02", - "props": [ - { - "name": "label", - "value": "PS-01_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the personnel security procedures are to be disseminated is/are defined;" - } - ] - }, - { - "id": "ps-01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ps-1_prm_2" - }, - { - "name": "label", - "value": "PS-01_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "organization-level", - "mission/business process-level", - "system-level" - ] - } - }, - { - "id": "ps-01_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "ps-1_prm_3" - }, - { - "name": "label", - "value": "PS-01_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "official", - "guidelines": [ - { - "prose": "an official to manage the personnel security policy and procedures is defined;" - } - ] - }, - { - "id": "ps-01_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "ps-1_prm_4" - }, - { - "name": "label", - "value": "PS-01_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current personnel security policy is reviewed and updated is defined;" - } - ] - }, - { - "id": "ps-01_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "ps-1_prm_5" - }, - { - "name": "label", - "value": "PS-01_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that would require the current personnel security policy to be reviewed and updated are defined;" - } - ] - }, - { - "id": "ps-01_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "ps-1_prm_6" - }, - { - "name": "label", - "value": "PS-01_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current personnel security procedures are reviewed and updated is defined;" - } - ] - }, - { - "id": "ps-01_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "ps-1_prm_7" - }, - { - "name": "label", - "value": "PS-01_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "events", - "constraints": [ - { - "description": "significant changes" - } - ], - "guidelines": [ - { - "prose": "events that would require the personnel security procedures to be reviewed and updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PS-01", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PS-1" - }, - { - "name": "label", - "value": "PS-01", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ps-01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#c7ac44e8-10db-4b64-b2b9-9e32ec1efed0", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#4c0ec2ee-a0d6-428a-9043-4504bc3ade6f", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "ps-1_smt", - "name": "statement", - "parts": [ - { - "id": "ps-1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, a policy that addresses Personnel Security MUST be associated with PS-1 part a.", - "class": "policy" - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, at least one procedure that addresses Personnel Security MUST be associated with PS-1 part a.", - "class": "procedure" - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, document, and disseminate to {{ insert: param, ps-1_prm_1 }}:", - "parts": [ - { - "id": "ps-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, ps-01_odp.03 }} personnel security policy that:", - "parts": [ - { - "id": "ps-1_smt.a.1.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "ps-1_smt.a.1.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and" - } - ] - }, - { - "id": "ps-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the personnel security policy and the associated personnel security controls;" - } - ] - }, - { - "id": "ps-1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Designate an {{ insert: param, ps-01_odp.04 }} to manage the development, documentation, and dissemination of the personnel security policy and procedures; and" - }, - { - "id": "ps-1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the current personnel security:", - "parts": [ - { - "id": "ps-1_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Policy {{ insert: param, ps-01_odp.05 }} and following {{ insert: param, ps-01_odp.06 }} ; and" - }, - { - "id": "ps-1_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures {{ insert: param, ps-01_odp.07 }} and following {{ insert: param, ps-01_odp.08 }}." - } - ] - } - ] - }, - { - "id": "ps-1_gdn", - "name": "guidance", - "prose": "Personnel security policy and procedures for the controls in the PS family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on their development. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission level or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies reflecting the complex nature of organizations. Procedures can be established for security and privacy programs, for mission/business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to personnel security policy and procedures include, but are not limited to, assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure." - }, - { - "id": "ps-1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ps-1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-01a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ps-1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-01a.[01]", - "class": "sp800-53a" - } - ], - "prose": "a personnel security policy is developed and documented;", - "links": [ - { - "href": "#ps-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-01a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the personnel security policy is disseminated to {{ insert: param, ps-01_odp.01 }};", - "links": [ - { - "href": "#ps-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-1_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-01a.[03]", - "class": "sp800-53a" - } - ], - "prose": "personnel security procedures to facilitate the implementation of the personnel security policy and associated personnel security controls are developed and documented;", - "links": [ - { - "href": "#ps-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-1_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-01a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the personnel security procedures are disseminated to {{ insert: param, ps-01_odp.02 }};", - "links": [ - { - "href": "#ps-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-1_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-01a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ps-1_obj.a.1.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-01a.01(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ps-1_obj.a.1.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-01a.01(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ps-01_odp.03 }} personnel security policy addresses purpose;", - "links": [ - { - "href": "#ps-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-1_obj.a.1.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-01a.01(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ps-01_odp.03 }} personnel security policy addresses scope;", - "links": [ - { - "href": "#ps-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-1_obj.a.1.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-01a.01(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ps-01_odp.03 }} personnel security policy addresses roles;", - "links": [ - { - "href": "#ps-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-1_obj.a.1.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-01a.01(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ps-01_odp.03 }} personnel security policy addresses responsibilities;", - "links": [ - { - "href": "#ps-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-1_obj.a.1.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-01a.01(a)[05]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ps-01_odp.03 }} personnel security policy addresses management commitment;", - "links": [ - { - "href": "#ps-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-1_obj.a.1.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-01a.01(a)[06]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ps-01_odp.03 }} personnel security policy addresses coordination among organizational entities;", - "links": [ - { - "href": "#ps-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-1_obj.a.1.a-7", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-01a.01(a)[07]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ps-01_odp.03 }} personnel security policy addresses compliance;", - "links": [ - { - "href": "#ps-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ps-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-1_obj.a.1.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-01a.01(b)", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ps-01_odp.03 }} personnel security policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines;", - "links": [ - { - "href": "#ps-1_smt.a.1.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ps-1_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ps-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-01b.", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ps-01_odp.04 }} is designated to manage the development, documentation, and dissemination of the personnel security policy and procedures;", - "links": [ - { - "href": "#ps-1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-01c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ps-1_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-01c.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ps-1_obj.c.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-01c.01[01]", - "class": "sp800-53a" - } - ], - "prose": "the current personnel security policy is reviewed and updated {{ insert: param, ps-01_odp.05 }};", - "links": [ - { - "href": "#ps-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-1_obj.c.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-01c.01[02]", - "class": "sp800-53a" - } - ], - "prose": "the current personnel security policy is reviewed and updated following {{ insert: param, ps-01_odp.06 }};", - "links": [ - { - "href": "#ps-1_smt.c.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ps-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-1_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-01c.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ps-1_obj.c.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-01c.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the current personnel security procedures are reviewed and updated {{ insert: param, ps-01_odp.07 }};", - "links": [ - { - "href": "#ps-1_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-1_obj.c.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-01c.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the current personnel security procedures are reviewed and updated following {{ insert: param, ps-01_odp.08 }}.", - "links": [ - { - "href": "#ps-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ps-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ps-1_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ps-1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PS-01-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Personnel security policy\n\npersonnel security procedures\n\nsystem security plan\n\nprivacy plan\n\nrisk management strategy documentation\n\naudit findings\n\nother relevant documents or records" - } - ] - }, - { - "id": "ps-1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PS-01-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "ps-2", - "class": "SP800-53", - "title": "Position Risk Designation", - "params": [ - { - "id": "ps-02_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ps-2_prm_1" - }, - { - "name": "label", - "value": "PS-02_ODP", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to review and update position risk designations is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PS-02", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PS-2" - }, - { - "name": "label", - "value": "PS-02", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ps-02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#a5ef5e56-5c1a-4911-b419-37dddc1b3581", - "rel": "reference" - }, - { - "href": "#276bd50a-7e58-48e5-a405-8c8cb91d7a5f", - "rel": "reference" - }, - { - "href": "#ac-5", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#ps-3", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-21", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "ps-2_smt", - "name": "statement", - "parts": [ - { - "id": "ps-2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Assign a risk designation to all organizational positions;" - }, - { - "id": "ps-2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Establish screening criteria for individuals filling those positions; and" - }, - { - "id": "ps-2_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update position risk designations {{ insert: param, ps-02_odp }}." - } - ] - }, - { - "id": "ps-2_gdn", - "name": "guidance", - "prose": "Position risk designations reflect Office of Personnel Management (OPM) policy and guidance. Proper position designation is the foundation of an effective and consistent suitability and personnel security program. The Position Designation System (PDS) assesses the duties and responsibilities of a position to determine the degree of potential damage to the efficiency or integrity of the service due to misconduct of an incumbent of a position and establishes the risk level of that position. The PDS assessment also determines if the duties and responsibilities of the position present the potential for position incumbents to bring about a material adverse effect on national security and the degree of that potential effect, which establishes the sensitivity level of a position. The results of the assessment determine what level of investigation is conducted for a position. Risk designations can guide and inform the types of authorizations that individuals receive when accessing organizational information and information systems. Position screening criteria include explicit information security role appointment requirements. Parts 1400 and 731 of Title 5, Code of Federal Regulations, establish the requirements for organizations to evaluate relevant covered positions for a position sensitivity and position risk designation commensurate with the duties and responsibilities of those positions." - }, - { - "id": "ps-2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ps-2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-02a.", - "class": "sp800-53a" - } - ], - "prose": "a risk designation is assigned to all organizational positions;", - "links": [ - { - "href": "#ps-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-02b.", - "class": "sp800-53a" - } - ], - "prose": "screening criteria are established for individuals filling organizational positions;", - "links": [ - { - "href": "#ps-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-2_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-02c.", - "class": "sp800-53a" - } - ], - "prose": "position risk designations are reviewed and updated {{ insert: param, ps-02_odp }}.", - "links": [ - { - "href": "#ps-2_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ps-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PS-02-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Personnel security policy\n\nprocedures addressing position categorization\n\nappropriate codes of federal regulations\n\nlist of risk designations for organizational positions\n\nrecords of position risk designation reviews and updates\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ps-2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PS-02-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ps-2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PS-02-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for assigning, reviewing, and updating position risk designations\n\norganizational processes for establishing screening criteria" - } - ] - } - ] - }, - { - "id": "ps-3", - "class": "SP800-53", - "title": "Personnel Screening", - "params": [ - { - "id": "ps-3_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ps-03_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ps-03_odp.02" - } - ], - "label": "organization-defined conditions requiring rescreening and, where rescreening is so indicated, the frequency of rescreening" - }, - { - "id": "ps-03_odp.01", - "props": [ - { - "name": "label", - "value": "PS-03_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "conditions requiring rescreening", - "constraints": [ - { - "description": "for national security clearances; a reinvestigation is required during the fifth (5th) year for top secret security clearance, the tenth (10th) year for secret security clearance, and fifteenth (15th) year for confidential security clearance.\n\nFor moderate risk law enforcement and high impact public trust level, a reinvestigation is required during the fifth (5th) year. There is no reinvestigation for other moderate risk positions or any low risk positions" - } - ], - "guidelines": [ - { - "prose": "conditions requiring rescreening of individuals are defined;" - } - ] - }, - { - "id": "ps-03_odp.02", - "props": [ - { - "name": "label", - "value": "PS-03_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "for national security clearances; a reinvestigation is required during the fifth (5th) year for top secret security clearance, the tenth (10th) year for secret security clearance, and fifteenth (15th) year for confidential security clearance.\n\nFor moderate risk law enforcement and high impact public trust level, a reinvestigation is required during the fifth (5th) year. There is no reinvestigation for other moderate risk positions or any low risk positions" - } - ], - "guidelines": [ - { - "prose": "the frequency of rescreening individuals where it is so indicated is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PS-03", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PS-3" - }, - { - "name": "label", - "value": "PS-03", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ps-03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#55b0c93a-5e48-457a-baa6-5ce81c239c49", - "rel": "reference" - }, - { - "href": "#0af071a6-cf8e-48ee-8c82-fe91efa20f94", - "rel": "reference" - }, - { - "href": "#628d22a1-6a11-4784-bc59-5cd9497b5445", - "rel": "reference" - }, - { - "href": "#7ba1d91c-3934-4d5a-8532-b32f864ad34c", - "rel": "reference" - }, - { - "href": "#e72fde0b-6fc2-497e-a9db-d8fce5a11b8a", - "rel": "reference" - }, - { - "href": "#9be5d661-421f-41ad-854e-86f98b811891", - "rel": "reference" - }, - { - "href": "#858705be-3c1f-48aa-a328-0ce398d95ef0", - "rel": "reference" - }, - { - "href": "#7af2e6ec-9f7e-4232-ad3f-09888eb0793a", - "rel": "reference" - }, - { - "href": "#828856bd-d7c4-427b-8b51-815517ec382d", - "rel": "reference" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#ma-5", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-12", - "rel": "related" - }, - { - "href": "#ps-2", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - }, - { - "href": "#ps-7", - "rel": "related" - }, - { - "href": "#sa-21", - "rel": "related" - } - ], - "parts": [ - { - "id": "ps-3_smt", - "name": "statement", - "parts": [ - { - "id": "ps-3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Screen individuals prior to authorizing access to the system; and" - }, - { - "id": "ps-3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Rescreen individuals in accordance with {{ insert: param, ps-3_prm_1 }}." - } - ] - }, - { - "id": "ps-3_gdn", - "name": "guidance", - "prose": "Personnel screening and rescreening activities reflect applicable laws, executive orders, directives, regulations, policies, standards, guidelines, and specific criteria established for the risk designations of assigned positions. Examples of personnel screening include background investigations and agency checks. Organizations may define different rescreening conditions and frequencies for personnel accessing systems based on types of information processed, stored, or transmitted by the systems." - }, - { - "id": "ps-3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ps-3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-03a.", - "class": "sp800-53a" - } - ], - "prose": "individuals are screened prior to authorizing access to the system;", - "links": [ - { - "href": "#ps-3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-03b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ps-3_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-03b.[01]", - "class": "sp800-53a" - } - ], - "prose": "individuals are rescreened in accordance with {{ insert: param, ps-03_odp.01 }};", - "links": [ - { - "href": "#ps-3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-3_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-03b.[02]", - "class": "sp800-53a" - } - ], - "prose": "where rescreening is so indicated, individuals are rescreened {{ insert: param, ps-03_odp.02 }}.", - "links": [ - { - "href": "#ps-3_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ps-3_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ps-3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PS-03-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Personnel security policy\n\nprocedures addressing personnel screening\n\nrecords of screened personnel\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ps-3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PS-03-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ps-3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PS-03-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for personnel screening" - } - ] - } - ], - "controls": [ - { - "id": "ps-3.3", - "class": "SP800-53-enhancement", - "title": "Information Requiring Special Protective Measures", - "params": [ - { - "id": "ps-03.03_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ps-3.3_prm_1" - }, - { - "name": "label", - "value": "PS-03(03)_ODP", - "class": "sp800-53a" - } - ], - "label": "additional personnel screening criteria", - "constraints": [ - { - "description": "personnel screening criteria - as required by specific information" - } - ], - "guidelines": [ - { - "prose": "additional personnel screening criteria to be satisfied for individuals accessing a system processing, storing, or transmitting information requiring special protection are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PS-03(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PS-3(3)" - }, - { - "name": "label", - "value": "PS-03(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ps-03.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ps-3", - "rel": "required" - } - ], - "parts": [ - { - "id": "ps-3.3_smt", - "name": "statement", - "prose": "Verify that individuals accessing a system processing, storing, or transmitting information requiring special protection:", - "parts": [ - { - "id": "ps-3.3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Have valid access authorizations that are demonstrated by assigned official government duties; and" - }, - { - "id": "ps-3.3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Satisfy {{ insert: param, ps-03.03_odp }}." - } - ] - }, - { - "id": "ps-3.3_gdn", - "name": "guidance", - "prose": "Organizational information that requires special protection includes controlled unclassified information. Personnel security criteria include position sensitivity background screening requirements." - }, - { - "id": "ps-3.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-03(03)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ps-3.3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-03(03)(a)", - "class": "sp800-53a" - } - ], - "prose": "individuals accessing a system processing, storing, or transmitting information requiring special protection have valid access authorizations that are demonstrated by assigned official government duties;", - "links": [ - { - "href": "#ps-3.3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-3.3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-03(03)(b)", - "class": "sp800-53a" - } - ], - "prose": "individuals accessing a system processing, storing, or transmitting information requiring special protection satisfy {{ insert: param, ps-03.03_odp }}.", - "links": [ - { - "href": "#ps-3.3_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ps-3.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-3.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PS-03(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Personnel security policy\n\naccess control policy, procedures addressing personnel screening\n\nrecords of screened personnel\n\nscreening criteria\n\nrecords of access authorizations\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ps-3.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PS-03(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ps-3.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PS-03(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for ensuring valid access authorizations for information requiring special protection\n\norganizational process for additional personnel screening for information requiring special protection" - } - ] - } - ] - } - ] - }, - { - "id": "ps-4", - "class": "SP800-53", - "title": "Personnel Termination", - "params": [ - { - "id": "ps-04_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ps-4_prm_1" - }, - { - "name": "label", - "value": "PS-04_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "one (1) hour" - } - ], - "guidelines": [ - { - "prose": "a time period within which to disable system access is defined;" - } - ] - }, - { - "id": "ps-04_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ps-4_prm_2" - }, - { - "name": "label", - "value": "PS-04_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "information security topics", - "guidelines": [ - { - "prose": "information security topics to be discussed when conducting exit interviews are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PS-04", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PS-4" - }, - { - "name": "label", - "value": "PS-04", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ps-04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-12", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - }, - { - "href": "#ps-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "ps-4_smt", - "name": "statement", - "prose": "Upon termination of individual employment:", - "parts": [ - { - "id": "ps-4_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Disable system access within {{ insert: param, ps-04_odp.01 }};" - }, - { - "id": "ps-4_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Terminate or revoke any authenticators and credentials associated with the individual;" - }, - { - "id": "ps-4_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Conduct exit interviews that include a discussion of {{ insert: param, ps-04_odp.02 }};" - }, - { - "id": "ps-4_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Retrieve all security-related organizational system-related property; and" - }, - { - "id": "ps-4_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Retain access to organizational information and systems formerly controlled by terminated individual." - } - ] - }, - { - "id": "ps-4_gdn", - "name": "guidance", - "prose": "System property includes hardware authentication tokens, system administration technical manuals, keys, identification cards, and building passes. Exit interviews ensure that terminated individuals understand the security constraints imposed by being former employees and that proper accountability is achieved for system-related property. Security topics at exit interviews include reminding individuals of nondisclosure agreements and potential limitations on future employment. Exit interviews may not always be possible for some individuals, including in cases related to the unavailability of supervisors, illnesses, or job abandonment. Exit interviews are important for individuals with security clearances. The timely execution of termination actions is essential for individuals who have been terminated for cause. In certain situations, organizations consider disabling the system accounts of individuals who are being terminated prior to the individuals being notified." - }, - { - "id": "ps-4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-04", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ps-4_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-04a.", - "class": "sp800-53a" - } - ], - "prose": "upon termination of individual employment, system access is disabled within {{ insert: param, ps-04_odp.01 }};", - "links": [ - { - "href": "#ps-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-4_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-04b.", - "class": "sp800-53a" - } - ], - "prose": "upon termination of individual employment, any authenticators and credentials are terminated or revoked;", - "links": [ - { - "href": "#ps-4_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-4_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-04c.", - "class": "sp800-53a" - } - ], - "prose": "upon termination of individual employment, exit interviews that include a discussion of {{ insert: param, ps-04_odp.02 }} are conducted;", - "links": [ - { - "href": "#ps-4_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-4_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-04d.", - "class": "sp800-53a" - } - ], - "prose": "upon termination of individual employment, all security-related organizational system-related property is retrieved;", - "links": [ - { - "href": "#ps-4_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-4_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-04e.", - "class": "sp800-53a" - } - ], - "prose": "upon termination of individual employment, access to organizational information and systems formerly controlled by the terminated individual are retained.", - "links": [ - { - "href": "#ps-4_smt.e", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ps-4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PS-04-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Personnel security policy\n\nprocedures addressing personnel termination\n\nrecords of personnel termination actions\n\nlist of system accounts\n\nrecords of terminated or revoked authenticators/credentials\n\nrecords of exit interviews\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ps-4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PS-04-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ps-4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PS-04-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for personnel termination\n\nmechanisms supporting and/or implementing personnel termination notifications\n\nmechanisms for disabling system access/revoking authenticators" - } - ] - } - ], - "controls": [ - { - "id": "ps-4.2", - "class": "SP800-53-enhancement", - "title": "Automated Actions", - "params": [ - { - "id": "ps-04.02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ps-4.2_prm_1" - }, - { - "name": "label", - "value": "PS-04(02)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms to notify personnel or roles of individual termination actions and/or to disable access to system resources are defined;" - } - ] - }, - { - "id": "ps-04.02_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ps-4.2_prm_2" - }, - { - "name": "label", - "value": "PS-04(02)_ODP[02]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "access control personnel responsible for disabling access to the system" - } - ] - }, - { - "id": "ps-04.02_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ps-4.2_prm_3" - }, - { - "name": "label", - "value": "PS-04(02)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to be notified upon termination of an individual is/are defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PS-04(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PS-4(2)" - }, - { - "name": "label", - "value": "PS-04(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ps-04.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ps-4", - "rel": "required" - } - ], - "parts": [ - { - "id": "ps-4.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Use {{ insert: param, ps-04.02_odp.01 }} to {{ insert: param, ps-04.02_odp.02 }}." - }, - { - "id": "ps-4.2_gdn", - "name": "guidance", - "prose": "In organizations with many employees, not all personnel who need to know about termination actions receive the appropriate notifications, or if such notifications are received, they may not occur in a timely manner. Automated mechanisms can be used to send automatic alerts or notifications to organizational personnel or roles when individuals are terminated. Such automatic alerts or notifications can be conveyed in a variety of ways, including via telephone, electronic mail, text message, or websites. Automated mechanisms can also be employed to quickly and thoroughly disable access to system resources after an employee is terminated." - }, - { - "id": "ps-4.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-04(02)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ps-04.02_odp.01 }} are used to {{ insert: param, ps-04.02_odp.02 }}.", - "links": [ - { - "href": "#ps-4.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-4.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PS-04(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Personnel security policy\n\nprocedures addressing personnel termination\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nrecords of personnel termination actions\n\nautomated notifications of employee terminations\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ps-4.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PS-04(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ps-4.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PS-04(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for personnel termination\n\nautomated mechanisms supporting and/or implementing personnel termination notifications" - } - ] - } - ] - } - ] - }, - { - "id": "ps-5", - "class": "SP800-53", - "title": "Personnel Transfer", - "params": [ - { - "id": "ps-05_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ps-5_prm_1" - }, - { - "name": "label", - "value": "PS-05_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "transfer or reassignment actions", - "guidelines": [ - { - "prose": "transfer or reassignment actions to be initiated following transfer or reassignment are defined;" - } - ] - }, - { - "id": "ps-05_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ps-5_prm_2" - }, - { - "name": "label", - "value": "PS-05_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "time period following the formal transfer action", - "constraints": [ - { - "description": "twenty-four (24) hours" - } - ], - "guidelines": [ - { - "prose": "the time period within which transfer or reassignment actions must occur following transfer or reassignment is defined;" - } - ] - }, - { - "id": "ps-05_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ps-5_prm_3" - }, - { - "name": "label", - "value": "PS-05_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "constraints": [ - { - "description": "including access control personnel responsible for the system" - } - ], - "guidelines": [ - { - "prose": "personnel or roles to be notified when individuals are reassigned or transferred to other positions within the organization is/are defined;" - } - ] - }, - { - "id": "ps-05_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "ps-5_prm_4" - }, - { - "name": "label", - "value": "PS-05_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "twenty-four (24) hours" - } - ], - "guidelines": [ - { - "prose": "time period within which to notify organization-defined personnel or roles when individuals are reassigned or transferred to other positions within the organization is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PS-05", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PS-5" - }, - { - "name": "label", - "value": "PS-05", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ps-05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ia-4", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-12", - "rel": "related" - }, - { - "href": "#ps-4", - "rel": "related" - }, - { - "href": "#ps-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "ps-5_smt", - "name": "statement", - "parts": [ - { - "id": "ps-5_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Review and confirm ongoing operational need for current logical and physical access authorizations to systems and facilities when individuals are reassigned or transferred to other positions within the organization;" - }, - { - "id": "ps-5_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Initiate {{ insert: param, ps-05_odp.01 }} within {{ insert: param, ps-05_odp.02 }};" - }, - { - "id": "ps-5_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Modify access authorization as needed to correspond with any changes in operational need due to reassignment or transfer; and" - }, - { - "id": "ps-5_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Notify {{ insert: param, ps-05_odp.03 }} within {{ insert: param, ps-05_odp.04 }}." - } - ] - }, - { - "id": "ps-5_gdn", - "name": "guidance", - "prose": "Personnel transfer applies when reassignments or transfers of individuals are permanent or of such extended duration as to make the actions warranted. Organizations define actions appropriate for the types of reassignments or transfers, whether permanent or extended. Actions that may be required for personnel transfers or reassignments to other positions within organizations include returning old and issuing new keys, identification cards, and building passes; closing system accounts and establishing new accounts; changing system access authorizations (i.e., privileges); and providing for access to official records to which individuals had access at previous work locations and in previous system accounts." - }, - { - "id": "ps-5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-05", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ps-5_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-05a.", - "class": "sp800-53a" - } - ], - "prose": "the ongoing operational need for current logical and physical access authorizations to systems and facilities are reviewed and confirmed when individuals are reassigned or transferred to other positions within the organization;", - "links": [ - { - "href": "#ps-5_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-5_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-05b.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ps-05_odp.01 }} are initiated within {{ insert: param, ps-05_odp.02 }};", - "links": [ - { - "href": "#ps-5_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-5_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-05c.", - "class": "sp800-53a" - } - ], - "prose": "access authorization is modified as needed to correspond with any changes in operational need due to reassignment or transfer;", - "links": [ - { - "href": "#ps-5_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-5_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-05d.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ps-05_odp.03 }} are notified within {{ insert: param, ps-05_odp.04 }}.", - "links": [ - { - "href": "#ps-5_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ps-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PS-05-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Personnel security policy\n\nprocedures addressing personnel transfer\n\nrecords of personnel transfer actions\n\nlist of system and facility access authorizations\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ps-5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PS-05-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel with account management responsibilities\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ps-5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PS-05-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for personnel transfer\n\nmechanisms supporting and/or implementing personnel transfer notifications\n\nmechanisms for disabling system access/revoking authenticators" - } - ] - } - ] - }, - { - "id": "ps-6", - "class": "SP800-53", - "title": "Access Agreements", - "params": [ - { - "id": "ps-06_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ps-6_prm_1" - }, - { - "name": "label", - "value": "PS-06_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to review and update access agreements is defined;" - } - ] - }, - { - "id": "ps-06_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ps-6_prm_2" - }, - { - "name": "label", - "value": "PS-06_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually and any time there is a change to the user's level of access" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to re-sign access agreements to maintain access to organizational information is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PS-06", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PS-6" - }, - { - "name": "label", - "value": "PS-06", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ps-06" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#pe-2", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#ps-2", - "rel": "related" - }, - { - "href": "#ps-3", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - }, - { - "href": "#ps-7", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#sa-21", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "ps-6_smt", - "name": "statement", - "parts": [ - { - "id": "ps-6_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop and document access agreements for organizational systems;" - }, - { - "id": "ps-6_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Review and update the access agreements {{ insert: param, ps-06_odp.01 }} ; and" - }, - { - "id": "ps-6_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Verify that individuals requiring access to organizational information and systems:", - "parts": [ - { - "id": "ps-6_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Sign appropriate access agreements prior to being granted access; and" - }, - { - "id": "ps-6_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Re-sign access agreements to maintain access to organizational systems when access agreements have been updated or {{ insert: param, ps-06_odp.02 }}." - } - ] - } - ] - }, - { - "id": "ps-6_gdn", - "name": "guidance", - "prose": "Access agreements include nondisclosure agreements, acceptable use agreements, rules of behavior, and conflict-of-interest agreements. Signed access agreements include an acknowledgement that individuals have read, understand, and agree to abide by the constraints associated with organizational systems to which access is authorized. Organizations can use electronic signatures to acknowledge access agreements unless specifically prohibited by organizational policy." - }, - { - "id": "ps-6_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-06", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ps-6_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-06a.", - "class": "sp800-53a" - } - ], - "prose": "access agreements are developed and documented for organizational systems;", - "links": [ - { - "href": "#ps-6_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-6_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-06b.", - "class": "sp800-53a" - } - ], - "prose": "the access agreements are reviewed and updated {{ insert: param, ps-06_odp.01 }};", - "links": [ - { - "href": "#ps-6_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-6_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-06c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ps-6_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-06c.01", - "class": "sp800-53a" - } - ], - "prose": "individuals requiring access to organizational information and systems sign appropriate access agreements prior to being granted access;", - "links": [ - { - "href": "#ps-6_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-6_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-06c.02", - "class": "sp800-53a" - } - ], - "prose": "individuals requiring access to organizational information and systems re-sign access agreements to maintain access to organizational systems when access agreements have been updated or {{ insert: param, ps-06_odp.02 }}.", - "links": [ - { - "href": "#ps-6_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ps-6_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ps-6_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-6_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PS-06-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Personnel security policy\n\npersonnel security procedures\n\nprocedures addressing access agreements for organizational information and systems\n\naccess control policy\n\naccess control procedures\n\naccess agreements (including non-disclosure agreements, acceptable use agreements, rules of behavior, and conflict-of-interest agreements)\n\ndocumentation of access agreement reviews, updates, and re-signing\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ps-6_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PS-06-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel who have signed/resigned access agreements\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "ps-6_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PS-06-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for reviewing, updating, and re-signing access agreements\n\nmechanisms supporting the reviewing, updating, and re-signing of access agreements" - } - ] - } - ] - }, - { - "id": "ps-7", - "class": "SP800-53", - "title": "External Personnel Security", - "params": [ - { - "id": "ps-07_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ps-7_prm_1" - }, - { - "name": "label", - "value": "PS-07_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "constraints": [ - { - "description": "including access control personnel responsible for the system and/or facilities, as appropriate" - } - ], - "guidelines": [ - { - "prose": "personnel or roles to be notified of any personnel transfers or terminations of external personnel who possess organizational credentials and/or badges or who have system privileges is/are defined;" - } - ] - }, - { - "id": "ps-07_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ps-7_prm_2" - }, - { - "name": "label", - "value": "PS-07_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "terminations: immediately; transfers: within twenty-four (24) hours" - } - ], - "guidelines": [ - { - "prose": "time period within which third-party providers are required to notify organization-defined personnel or roles of any personnel transfers or terminations of external personnel who possess organizational credentials and/or badges or who have system privileges is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PS-07", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PS-7" - }, - { - "name": "label", - "value": "PS-07", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ps-07" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#77faf0bc-c394-44ad-9154-bbac3b79c8ad", - "rel": "reference" - }, - { - "href": "#737513fa-6758-403f-831d-5ddab5e23cb3", - "rel": "reference" - }, - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#ma-5", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#ps-2", - "rel": "related" - }, - { - "href": "#ps-3", - "rel": "related" - }, - { - "href": "#ps-4", - "rel": "related" - }, - { - "href": "#ps-5", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - }, - { - "href": "#sa-21", - "rel": "related" - } - ], - "parts": [ - { - "id": "ps-7_smt", - "name": "statement", - "parts": [ - { - "id": "ps-7_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Establish personnel security requirements, including security roles and responsibilities for external providers;" - }, - { - "id": "ps-7_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Require external providers to comply with personnel security policies and procedures established by the organization;" - }, - { - "id": "ps-7_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Document personnel security requirements;" - }, - { - "id": "ps-7_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Require external providers to notify {{ insert: param, ps-07_odp.01 }} of any personnel transfers or terminations of external personnel who possess organizational credentials and/or badges, or who have system privileges within {{ insert: param, ps-07_odp.02 }} ; and" - }, - { - "id": "ps-7_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Monitor provider compliance with personnel security requirements." - } - ] - }, - { - "id": "ps-7_gdn", - "name": "guidance", - "prose": "External provider refers to organizations other than the organization operating or acquiring the system. External providers include service bureaus, contractors, and other organizations that provide system development, information technology services, testing or assessment services, outsourced applications, and network/security management. Organizations explicitly include personnel security requirements in acquisition-related documents. External providers may have personnel working at organizational facilities with credentials, badges, or system privileges issued by organizations. Notifications of external personnel changes ensure the appropriate termination of privileges and credentials. Organizations define the transfers and terminations deemed reportable by security-related characteristics that include functions, roles, and the nature of credentials or privileges associated with transferred or terminated individuals." - }, - { - "id": "ps-7_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-07", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ps-7_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-07a.", - "class": "sp800-53a" - } - ], - "prose": "personnel security requirements are established, including security roles and responsibilities for external providers;", - "links": [ - { - "href": "#ps-7_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-7_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-07b.", - "class": "sp800-53a" - } - ], - "prose": "external providers are required to comply with personnel security policies and procedures established by the organization;", - "links": [ - { - "href": "#ps-7_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-7_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-07c.", - "class": "sp800-53a" - } - ], - "prose": "personnel security requirements are documented;", - "links": [ - { - "href": "#ps-7_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-7_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-07d.", - "class": "sp800-53a" - } - ], - "prose": "external providers are required to notify {{ insert: param, ps-07_odp.01 }} of any personnel transfers or terminations of external personnel who possess organizational credentials and/or badges or who have system privileges within {{ insert: param, ps-07_odp.02 }};", - "links": [ - { - "href": "#ps-7_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-7_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-07e.", - "class": "sp800-53a" - } - ], - "prose": "provider compliance with personnel security requirements is monitored.", - "links": [ - { - "href": "#ps-7_smt.e", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ps-7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-7_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PS-07-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Personnel security policy\n\nprocedures addressing external personnel security\n\nlist of personnel security requirements\n\nacquisition documents\n\nservice-level agreements\n\ncompliance monitoring process\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ps-7_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PS-07-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with personnel security responsibilities\n\nexternal providers\n\nsystem/network administrators\n\norganizational personnel with account management responsibilities\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "ps-7_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PS-07-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for managing and monitoring external personnel security\n\nmechanisms supporting and/or implementing the monitoring of provider compliance" - } - ] - } - ] - }, - { - "id": "ps-8", - "class": "SP800-53", - "title": "Personnel Sanctions", - "params": [ - { - "id": "ps-08_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ps-8_prm_1" - }, - { - "name": "label", - "value": "PS-08_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "constraints": [ - { - "description": "to include the ISSO and/or similar role within the organization" - } - ], - "guidelines": [ - { - "prose": "personnel or roles to be notified when a formal employee sanctions process is initiated is/are defined;" - } - ] - }, - { - "id": "ps-08_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ps-8_prm_2" - }, - { - "name": "label", - "value": "PS-08_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "24 hours" - } - ], - "guidelines": [ - { - "prose": "the time period within which organization-defined personnel or roles must be notified when a formal employee sanctions process is initiated is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "PS-08", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PS-8" - }, - { - "name": "label", - "value": "PS-08", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ps-08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-12", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-1", - "rel": "related" - } - ], - "parts": [ - { - "id": "ps-8_smt", - "name": "statement", - "parts": [ - { - "id": "ps-8_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Employ a formal sanctions process for individuals failing to comply with established information security and privacy policies and procedures; and" - }, - { - "id": "ps-8_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Notify {{ insert: param, ps-08_odp.01 }} within {{ insert: param, ps-08_odp.02 }} when a formal employee sanctions process is initiated, identifying the individual sanctioned and the reason for the sanction." - } - ] - }, - { - "id": "ps-8_gdn", - "name": "guidance", - "prose": "Organizational sanctions reflect applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Sanctions processes are described in access agreements and can be included as part of general personnel policies for organizations and/or specified in security and privacy policies. Organizations consult with the Office of the General Counsel regarding matters of employee sanctions." - }, - { - "id": "ps-8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-08", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ps-8_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-08a.", - "class": "sp800-53a" - } - ], - "prose": "a formal sanctions process is employed for individuals failing to comply with established information security and privacy policies and procedures;", - "links": [ - { - "href": "#ps-8_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-8_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-08b.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ps-08_odp.01 }} is/are notified within {{ insert: param, ps-08_odp.02 }} when a formal employee sanctions process is initiated, identifying the individual sanctioned and the reason for the sanction.", - "links": [ - { - "href": "#ps-8_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ps-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PS-08-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Personnel security policy\n\npersonnel security procedures\n\nprocedures addressing personnel sanctions\n\naccess agreements (including non-disclosure agreements, acceptable use agreements, rules of behavior, and conflict-of-interest agreements)\n\nlist of personnel or roles to be notified of formal employee sanctions\n\nrecords or notifications of formal employee sanctions\n\nsystem security plan\n\nprivacy plan\n\npersonally identifiable information processing policy\n\nother relevant documents or records" - } - ] - }, - { - "id": "ps-8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PS-08-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with personnel security responsibilities\n\nlegal counsel\n\norganizational personnel with information security and privacy responsibilities" - } - ] - }, - { - "id": "ps-8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PS-08-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for managing formal employee sanctions\n\nmechanisms supporting and/or implementing formal employee sanctions notifications" - } - ] - } - ] - }, - { - "id": "ps-9", - "class": "SP800-53", - "title": "Position Descriptions", - "props": [ - { - "name": "label", - "value": "PS-09", - "class": "zero-padded" - }, - { - "name": "label", - "value": "PS-9" - }, - { - "name": "label", - "value": "PS-09", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ps-09" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#276bd50a-7e58-48e5-a405-8c8cb91d7a5f", - "rel": "reference" - } - ], - "parts": [ - { - "id": "ps-9_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Incorporate security and privacy roles and responsibilities into organizational position descriptions." - }, - { - "id": "ps-9_gdn", - "name": "guidance", - "prose": "Specification of security and privacy roles in individual organizational position descriptions facilitates clarity in understanding the security or privacy responsibilities associated with the roles and the role-based security and privacy training requirements for the roles." - }, - { - "id": "ps-9_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "PS-09", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ps-9_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-09[01]", - "class": "sp800-53a" - } - ], - "prose": "security roles and responsibilities are incorporated into organizational position descriptions;", - "links": [ - { - "href": "#ps-9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-9_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "PS-09[02]", - "class": "sp800-53a" - } - ], - "prose": "privacy roles and responsibilities are incorporated into organizational position descriptions.", - "links": [ - { - "href": "#ps-9_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ps-9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ps-9_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "PS-09-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Personnel security policy\n\npersonnel security procedures\n\nprocedures addressing position descriptions\n\nsecurity and privacy position descriptions\n\nsystem security plan\n\nprivacy plan\n\nprivacy program plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ps-9_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "PS-09-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with personnel security responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\norganizational personnel with human capital management responsibilities" - } - ] - }, - { - "id": "ps-9_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "PS-09-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for managing position descriptions" - } - ] - } - ] - } - ] - }, - { - "id": "ra", - "class": "family", - "title": "Risk Assessment", - "controls": [ - { - "id": "ra-1", - "class": "SP800-53", - "title": "Policy and Procedures", - "params": [ - { - "id": "ra-1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ra-01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ra-01_odp.02" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "ra-01_odp.01", - "props": [ - { - "name": "label", - "value": "RA-01_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the risk assessment policy is to be disseminated is/are defined;" - } - ] - }, - { - "id": "ra-01_odp.02", - "props": [ - { - "name": "label", - "value": "RA-01_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the risk assessment procedures are to be disseminated is/are defined;" - } - ] - }, - { - "id": "ra-01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ra-1_prm_2" - }, - { - "name": "label", - "value": "RA-01_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "organization-level", - "mission/business process-level", - "system-level" - ] - } - }, - { - "id": "ra-01_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "ra-1_prm_3" - }, - { - "name": "label", - "value": "RA-01_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "official", - "guidelines": [ - { - "prose": "an official to manage the risk assessment policy and procedures is defined;" - } - ] - }, - { - "id": "ra-01_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "ra-1_prm_4" - }, - { - "name": "label", - "value": "RA-01_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current risk assessment policy is reviewed and updated is defined;" - } - ] - }, - { - "id": "ra-01_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "ra-1_prm_5" - }, - { - "name": "label", - "value": "RA-01_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that would require the current risk assessment policy to be reviewed and updated are defined;" - } - ] - }, - { - "id": "ra-01_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "ra-1_prm_6" - }, - { - "name": "label", - "value": "RA-01_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current risk assessment procedures are reviewed and updated is defined;" - } - ] - }, - { - "id": "ra-01_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "ra-1_prm_7" - }, - { - "name": "label", - "value": "RA-01_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "events", - "constraints": [ - { - "description": "significant changes" - } - ], - "guidelines": [ - { - "prose": "events that would require risk assessment procedures to be reviewed and updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "RA-01", - "class": "zero-padded" - }, - { - "name": "label", - "value": "RA-1" - }, - { - "name": "label", - "value": "RA-01", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ra-01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#c7ac44e8-10db-4b64-b2b9-9e32ec1efed0", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#4c0ec2ee-a0d6-428a-9043-4504bc3ade6f", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "ra-1_smt", - "name": "statement", - "parts": [ - { - "id": "ra-1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, a policy that addresses Risk Assessment MUST be associated with RA-1 part a.", - "class": "policy" - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, at least one procedure that addresses Risk Assessment MUST be associated with RA-1 part a.", - "class": "procedure" - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, document, and disseminate to {{ insert: param, ra-1_prm_1 }}:", - "parts": [ - { - "id": "ra-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, ra-01_odp.03 }} risk assessment policy that:", - "parts": [ - { - "id": "ra-1_smt.a.1.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "ra-1_smt.a.1.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and" - } - ] - }, - { - "id": "ra-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the risk assessment policy and the associated risk assessment controls;" - } - ] - }, - { - "id": "ra-1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Designate an {{ insert: param, ra-01_odp.04 }} to manage the development, documentation, and dissemination of the risk assessment policy and procedures; and" - }, - { - "id": "ra-1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the current risk assessment:", - "parts": [ - { - "id": "ra-1_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Policy {{ insert: param, ra-01_odp.05 }} and following {{ insert: param, ra-01_odp.06 }} ; and" - }, - { - "id": "ra-1_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures {{ insert: param, ra-01_odp.07 }} and following {{ insert: param, ra-01_odp.08 }}." - } - ] - } - ] - }, - { - "id": "ra-1_gdn", - "name": "guidance", - "prose": "Risk assessment policy and procedures address the controls in the RA family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of risk assessment policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies reflecting the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to risk assessment policy and procedures include assessment or audit findings, security incidents or breaches, or changes in laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure." - }, - { - "id": "ra-1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ra-1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-01a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ra-1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-01a.[01]", - "class": "sp800-53a" - } - ], - "prose": "a risk assessment policy is developed and documented;", - "links": [ - { - "href": "#ra-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-01a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the risk assessment policy is disseminated to {{ insert: param, ra-01_odp.01 }};", - "links": [ - { - "href": "#ra-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-1_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-01a.[03]", - "class": "sp800-53a" - } - ], - "prose": "risk assessment procedures to facilitate the implementation of the risk assessment policy and associated risk assessment controls are developed and documented;", - "links": [ - { - "href": "#ra-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-1_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-01a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the risk assessment procedures are disseminated to {{ insert: param, ra-01_odp.02 }};", - "links": [ - { - "href": "#ra-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-1_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-01a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ra-1_obj.a.1.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-01a.01(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ra-1_obj.a.1.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-01a.01(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ra-01_odp.03 }} risk assessment policy addresses purpose;", - "links": [ - { - "href": "#ra-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-1_obj.a.1.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-01a.01(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ra-01_odp.03 }} risk assessment policy addresses scope;", - "links": [ - { - "href": "#ra-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-1_obj.a.1.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-01a.01(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ra-01_odp.03 }} risk assessment policy addresses roles;", - "links": [ - { - "href": "#ra-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-1_obj.a.1.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-01a.01(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ra-01_odp.03 }} risk assessment policy addresses responsibilities;", - "links": [ - { - "href": "#ra-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-1_obj.a.1.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-01a.01(a)[05]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ra-01_odp.03 }} risk assessment policy addresses management commitment;", - "links": [ - { - "href": "#ra-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-1_obj.a.1.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-01a.01(a)[06]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ra-01_odp.03 }} risk assessment policy addresses coordination among organizational entities;", - "links": [ - { - "href": "#ra-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-1_obj.a.1.a-7", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-01a.01(a)[07]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ra-01_odp.03 }} risk assessment policy addresses compliance;", - "links": [ - { - "href": "#ra-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ra-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-1_obj.a.1.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-01a.01(b)", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ra-01_odp.03 }} risk assessment policy is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines;", - "links": [ - { - "href": "#ra-1_smt.a.1.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ra-1_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ra-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-01b.", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, ra-01_odp.04 }} is designated to manage the development, documentation, and dissemination of the risk assessment policy and procedures;", - "links": [ - { - "href": "#ra-1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-01c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ra-1_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-01c.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ra-1_obj.c.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-01c.01[01]", - "class": "sp800-53a" - } - ], - "prose": "the current risk assessment policy is reviewed and updated {{ insert: param, ra-01_odp.05 }};", - "links": [ - { - "href": "#ra-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-1_obj.c.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-01c.01[02]", - "class": "sp800-53a" - } - ], - "prose": "the current risk assessment policy is reviewed and updated following {{ insert: param, ra-01_odp.06 }};", - "links": [ - { - "href": "#ra-1_smt.c.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ra-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-1_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-01c.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ra-1_obj.c.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-01c.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the current risk assessment procedures are reviewed and updated {{ insert: param, ra-01_odp.07 }};", - "links": [ - { - "href": "#ra-1_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-1_obj.c.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-01c.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the current risk assessment procedures are reviewed and updated following {{ insert: param, ra-01_odp.08 }}.", - "links": [ - { - "href": "#ra-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ra-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ra-1_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ra-1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "RA-01-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Risk assessment policy and procedures\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ra-1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "RA-01-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with risk assessment responsibilities\n\norganizational personnel with security and privacy responsibilities" - } - ] - } - ] - }, - { - "id": "ra-2", - "class": "SP800-53", - "title": "Security Categorization", - "props": [ - { - "name": "label", - "value": "RA-02", - "class": "zero-padded" - }, - { - "name": "label", - "value": "RA-2" - }, - { - "name": "label", - "value": "RA-02", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ra-02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#628d22a1-6a11-4784-bc59-5cd9497b5445", - "rel": "reference" - }, - { - "href": "#599fb53d-5041-444e-a7fe-640d6d30ad05", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#482e4c99-9dc4-41ad-bba8-0f3f0032c1f8", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#e72fde0b-6fc2-497e-a9db-d8fce5a11b8a", - "rel": "reference" - }, - { - "href": "#9be5d661-421f-41ad-854e-86f98b811891", - "rel": "reference" - }, - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "#4e4fbc93-333d-45e6-a875-de36b878b6b9", - "rel": "reference" - }, - { - "href": "#c28ae9a8-1121-42a9-a85e-00cfcc9b9a94", - "rel": "reference" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#pl-10", - "rel": "related" - }, - { - "href": "#pl-11", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-7", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#ra-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ra-8", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-38", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "ra-2_smt", - "name": "statement", - "parts": [ - { - "id": "ra-2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Categorize the system and information it processes, stores, and transmits;" - }, - { - "id": "ra-2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Document the security categorization results, including supporting rationale, in the security plan for the system; and" - }, - { - "id": "ra-2_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Verify that the authorizing official or authorizing official designated representative reviews and approves the security categorization decision." - } - ] - }, - { - "id": "ra-2_gdn", - "name": "guidance", - "prose": "Security categories describe the potential adverse impacts or negative consequences to organizational operations, organizational assets, and individuals if organizational information and systems are compromised through a loss of confidentiality, integrity, or availability. Security categorization is also a type of asset loss characterization in systems security engineering processes that is carried out throughout the system development life cycle. Organizations can use privacy risk assessments or privacy impact assessments to better understand the potential adverse effects on individuals. [CNSSI 1253](#4e4fbc93-333d-45e6-a875-de36b878b6b9) provides additional guidance on categorization for national security systems.\n\nOrganizations conduct the security categorization process as an organization-wide activity with the direct involvement of chief information officers, senior agency information security officers, senior agency officials for privacy, system owners, mission and business owners, and information owners or stewards. Organizations consider the potential adverse impacts to other organizations and, in accordance with [USA PATRIOT](#13f0c39d-eaf7-417a-baef-69a041878bb5) and Homeland Security Presidential Directives, potential national-level adverse impacts.\n\nSecurity categorization processes facilitate the development of inventories of information assets and, along with [CM-8](#cm-8) , mappings to specific system components where information is processed, stored, or transmitted. The security categorization process is revisited throughout the system development life cycle to ensure that the security categories remain accurate and relevant." - }, - { - "id": "ra-2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ra-2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-02a.", - "class": "sp800-53a" - } - ], - "prose": "the system and the information it processes, stores, and transmits are categorized;", - "links": [ - { - "href": "#ra-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-02b.", - "class": "sp800-53a" - } - ], - "prose": "the security categorization results, including supporting rationale, are documented in the security plan for the system;", - "links": [ - { - "href": "#ra-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-2_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-02c.", - "class": "sp800-53a" - } - ], - "prose": "the authorizing official or authorizing official designated representative reviews and approves the security categorization decision.", - "links": [ - { - "href": "#ra-2_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ra-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "RA-02-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Risk assessment policy\n\nsecurity planning policy and procedures\n\nprocedures addressing security categorization of organizational information and systems\n\nsecurity categorization documentation\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ra-2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "RA-02-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with security categorization and risk assessment responsibilities\n\norganizational personnel with security and privacy responsibilities" - } - ] - }, - { - "id": "ra-2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "RA-02-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for security categorization" - } - ] - } - ] - }, - { - "id": "ra-3", - "class": "SP800-53", - "title": "Risk Assessment", - "params": [ - { - "id": "ra-03_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ra-3_prm_1" - }, - { - "name": "label", - "value": "RA-03_ODP[01]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "security assessment report" - } - ] - }, - { - "id": "ra-03_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ra-3_prm_2" - }, - { - "name": "label", - "value": "RA-03_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "document", - "guidelines": [ - { - "prose": "a document in which risk assessment results are to be documented (if not documented in the security and privacy plans or risk assessment report) is defined (if selected);" - } - ] - }, - { - "id": "ra-03_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ra-3_prm_3" - }, - { - "name": "label", - "value": "RA-03_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually and whenever a significant change occurs" - } - ], - "guidelines": [ - { - "prose": "the frequency to review risk assessment results is defined;" - } - ] - }, - { - "id": "ra-03_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "ra-3_prm_4" - }, - { - "name": "label", - "value": "RA-03_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom risk assessment results are to be disseminated is/are defined;" - } - ] - }, - { - "id": "ra-03_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "ra-3_prm_5" - }, - { - "name": "label", - "value": "RA-03_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "annually" - } - ], - "guidelines": [ - { - "prose": "the frequency to update the risk assessment is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "RA-03", - "class": "zero-padded" - }, - { - "name": "label", - "value": "RA-3" - }, - { - "name": "label", - "value": "RA-03", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ra-03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#e8e84963-14fc-4c3a-be05-b412a5d37cd2", - "rel": "reference" - }, - { - "href": "#4c501da5-9d79-4cb6-ba80-97260e1ce327", - "rel": "reference" - }, - { - "href": "#98d415ca-7281-4064-9931-0c366637e324", - "rel": "reference" - }, - { - "href": "#38ff38f0-1366-4f50-a4c9-26a39aacee16", - "rel": "reference" - }, - { - "href": "#ca-3", - "rel": "related" - }, - { - "href": "#ca-6", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#cm-13", - "rel": "related" - }, - { - "href": "#cp-6", - "rel": "related" - }, - { - "href": "#cp-7", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "#ma-5", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pe-8", - "rel": "related" - }, - { - "href": "#pe-18", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#pl-10", - "rel": "related" - }, - { - "href": "#pl-11", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-28", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-7", - "rel": "related" - }, - { - "href": "#ra-2", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#ra-7", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-38", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "ra-3_smt", - "name": "statement", - "parts": [ - { - "id": "ra-3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Conduct a risk assessment, including:", - "parts": [ - { - "id": "ra-3_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Identifying threats to and vulnerabilities in the system;" - }, - { - "id": "ra-3_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Determining the likelihood and magnitude of harm from unauthorized access, use, disclosure, disruption, modification, or destruction of the system, the information it processes, stores, or transmits, and any related information; and" - }, - { - "id": "ra-3_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Determining the likelihood and impact of adverse effects on individuals arising from the processing of personally identifiable information;" - } - ] - }, - { - "id": "ra-3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Integrate risk assessment results and risk management decisions from the organization and mission or business process perspectives with system-level risk assessments;" - }, - { - "id": "ra-3_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Document risk assessment results in {{ insert: param, ra-03_odp.01 }};" - }, - { - "id": "ra-3_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Review risk assessment results {{ insert: param, ra-03_odp.03 }};" - }, - { - "id": "ra-3_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Disseminate risk assessment results to {{ insert: param, ra-03_odp.04 }} ; and" - }, - { - "id": "ra-3_smt.f", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "f." - } - ], - "prose": "Update the risk assessment {{ insert: param, ra-03_odp.05 }} or when there are significant changes to the system, its environment of operation, or other conditions that may impact the security or privacy state of the system." - } - ] - }, - { - "id": "ra-3_gdn", - "name": "guidance", - "prose": "Risk assessments consider threats, vulnerabilities, likelihood, and impact to organizational operations and assets, individuals, other organizations, and the Nation. Risk assessments also consider risk from external parties, including contractors who operate systems on behalf of the organization, individuals who access organizational systems, service providers, and outsourcing entities.\n\nOrganizations can conduct risk assessments at all three levels in the risk management hierarchy (i.e., organization level, mission/business process level, or information system level) and at any stage in the system development life cycle. Risk assessments can also be conducted at various steps in the Risk Management Framework, including preparation, categorization, control selection, control implementation, control assessment, authorization, and control monitoring. Risk assessment is an ongoing activity carried out throughout the system development life cycle.\n\nRisk assessments can also address information related to the system, including system design, the intended use of the system, testing results, and supply chain-related information or artifacts. Risk assessments can play an important role in control selection processes, particularly during the application of tailoring guidance and in the earliest phases of capability determination." - }, - { - "id": "ra-3_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "RA-3 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ra-3_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Significant change is defined in NIST Special Publication 800-37 Revision 2, Appendix F." - }, - { - "id": "ra-3_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(e) Requirement:" - } - ], - "prose": "Include all Authorizing Officials." - } - ] - }, - { - "id": "ra-3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ra-3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-03a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ra-3_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-03a.01", - "class": "sp800-53a" - } - ], - "prose": "a risk assessment is conducted to identify threats to and vulnerabilities in the system;", - "links": [ - { - "href": "#ra-3_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-3_obj.a.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-03a.02", - "class": "sp800-53a" - } - ], - "prose": "a risk assessment is conducted to determine the likelihood and magnitude of harm from unauthorized access, use, disclosure, disruption, modification, or destruction of the system; the information it processes, stores, or transmits; and any related information;", - "links": [ - { - "href": "#ra-3_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-3_obj.a.3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-03a.03", - "class": "sp800-53a" - } - ], - "prose": "a risk assessment is conducted to determine the likelihood and impact of adverse effects on individuals arising from the processing of personally identifiable information;", - "links": [ - { - "href": "#ra-3_smt.a.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ra-3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-03b.", - "class": "sp800-53a" - } - ], - "prose": "risk assessment results and risk management decisions from the organization and mission or business process perspectives are integrated with system-level risk assessments;", - "links": [ - { - "href": "#ra-3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-3_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-03c.", - "class": "sp800-53a" - } - ], - "prose": "risk assessment results are documented in {{ insert: param, ra-03_odp.01 }};", - "links": [ - { - "href": "#ra-3_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-3_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-03d.", - "class": "sp800-53a" - } - ], - "prose": "risk assessment results are reviewed {{ insert: param, ra-03_odp.03 }};", - "links": [ - { - "href": "#ra-3_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-3_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-03e.", - "class": "sp800-53a" - } - ], - "prose": "risk assessment results are disseminated to {{ insert: param, ra-03_odp.04 }};", - "links": [ - { - "href": "#ra-3_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-3_obj.f", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-03f.", - "class": "sp800-53a" - } - ], - "prose": "the risk assessment is updated {{ insert: param, ra-03_odp.05 }} or when there are significant changes to the system, its environment of operation, or other conditions that may impact the security or privacy state of the system.", - "links": [ - { - "href": "#ra-3_smt.f", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ra-3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "RA-03-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Risk assessment policy\n\nrisk assessment procedures\n\nsecurity and privacy planning policy and procedures\n\nprocedures addressing organizational assessments of risk\n\nrisk assessment\n\nrisk assessment results\n\nrisk assessment reviews\n\nrisk assessment updates\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ra-3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "RA-03-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with risk assessment responsibilities\n\norganizational personnel with security and privacy responsibilities" - } - ] - }, - { - "id": "ra-3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "RA-03-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for risk assessment\n\nmechanisms supporting and/or conducting, documenting, reviewing, disseminating, and updating the risk assessment" - } - ] - } - ], - "controls": [ - { - "id": "ra-3.1", - "class": "SP800-53-enhancement", - "title": "Supply Chain Risk Assessment", - "params": [ - { - "id": "ra-03.01_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ra-3.1_prm_1" - }, - { - "name": "label", - "value": "RA-03(01)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "systems, system components, and system services", - "guidelines": [ - { - "prose": "systems, system components, and system services to assess supply chain risks are defined;" - } - ] - }, - { - "id": "ra-03.01_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ra-3.1_prm_2" - }, - { - "name": "label", - "value": "RA-03(01)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "guidelines": [ - { - "prose": "the frequency at which to update the supply chain risk assessment is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "RA-03(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "RA-3(1)" - }, - { - "name": "label", - "value": "RA-03(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ra-03.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ra-3", - "rel": "required" - }, - { - "href": "#ra-2", - "rel": "related" - }, - { - "href": "#ra-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-17", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-30", - "rel": "related" - }, - { - "href": "#sr-2", - "rel": "related" - } - ], - "parts": [ - { - "id": "ra-3.1_smt", - "name": "statement", - "parts": [ - { - "id": "ra-3.1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Assess supply chain risks associated with {{ insert: param, ra-03.01_odp.01 }} ; and" - }, - { - "id": "ra-3.1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Update the supply chain risk assessment {{ insert: param, ra-03.01_odp.02 }} , when there are significant changes to the relevant supply chain, or when changes to the system, environments of operation, or other conditions may necessitate a change in the supply chain." - } - ] - }, - { - "id": "ra-3.1_gdn", - "name": "guidance", - "prose": "Supply chain-related events include disruption, use of defective components, insertion of counterfeits, theft, malicious development practices, improper delivery practices, and insertion of malicious code. These events can have a significant impact on the confidentiality, integrity, or availability of a system and its information and, therefore, can also adversely impact organizational operations (including mission, functions, image, or reputation), organizational assets, individuals, other organizations, and the Nation. The supply chain-related events may be unintentional or malicious and can occur at any point during the system life cycle. An analysis of supply chain risk can help an organization identify systems or components for which additional supply chain risk mitigations are required." - }, - { - "id": "ra-3.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-03(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ra-3.1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-03(01)(a)", - "class": "sp800-53a" - } - ], - "prose": "supply chain risks associated with {{ insert: param, ra-03.01_odp.01 }} are assessed;", - "links": [ - { - "href": "#ra-3.1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-3.1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-03(01)(b)", - "class": "sp800-53a" - } - ], - "prose": "the supply chain risk assessment is updated {{ insert: param, ra-03.01_odp.02 }} , when there are significant changes to the relevant supply chain, or when changes to the system, environments of operation, or other conditions may necessitate a change in the supply chain.", - "links": [ - { - "href": "#ra-3.1_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ra-3.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-3.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "RA-03(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Supply chain risk management policy\n\ninventory of critical systems, system components, and system services\n\nrisk assessment policy\n\nsecurity planning policy and procedures\n\nprocedures addressing organizational assessments of supply chain risk\n\nrisk assessment\n\nrisk assessment results\n\nrisk assessment reviews\n\nrisk assessment updates\n\nacquisition policy\n\nsystem security plan\n\nsupply chain risk management plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ra-3.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "RA-03(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with risk assessment responsibilities\n\norganizational personnel with security responsibilities\n\norganizational personnel with supply chain risk management responsibilities" - } - ] - }, - { - "id": "ra-3.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "RA-03(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for risk assessment\n\nmechanisms supporting and/or conducting, documenting, reviewing, disseminating, and updating the supply chain risk assessment" - } - ] - } - ] - } - ] - }, - { - "id": "ra-5", - "class": "SP800-53", - "title": "Vulnerability Monitoring and Scanning", - "params": [ - { - "id": "ra-5_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ra-05_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "ra-05_odp.02" - } - ], - "label": "organization-defined frequency and/or randomly in accordance with organization-defined process" - }, - { - "id": "ra-05_odp.01", - "props": [ - { - "name": "label", - "value": "RA-05_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency and/or randomly in accordance with organization-defined process", - "constraints": [ - { - "description": "monthly operating system/infrastructure; monthly web applications (including APIs) and databases" - } - ], - "guidelines": [ - { - "prose": "frequency for monitoring systems and hosted applications for vulnerabilities is defined;" - } - ] - }, - { - "id": "ra-05_odp.02", - "props": [ - { - "name": "label", - "value": "RA-05_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency and/or randomly in accordance with organization-defined process", - "constraints": [ - { - "description": "monthly operating system/infrastructure; monthly web applications (including APIs) and databases" - } - ], - "guidelines": [ - { - "prose": "frequency for scanning systems and hosted applications for vulnerabilities is defined;" - } - ] - }, - { - "id": "ra-05_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "ra-5_prm_2" - }, - { - "name": "label", - "value": "RA-05_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "response times", - "constraints": [ - { - "description": "high-risk vulnerabilities mitigated within thirty (30) days from date of discovery; moderate-risk vulnerabilities mitigated within ninety (90) days from date of discovery; low risk vulnerabilities mitigated within one hundred and eighty (180) days from date of discovery" - } - ], - "guidelines": [ - { - "prose": "response times to remediate legitimate vulnerabilities in accordance with an organizational assessment of risk are defined;" - } - ] - }, - { - "id": "ra-05_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "ra-5_prm_3" - }, - { - "name": "label", - "value": "RA-05_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles with whom information obtained from the vulnerability scanning process and control assessments is to be shared;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "RA-05", - "class": "zero-padded" - }, - { - "name": "label", - "value": "RA-5" - }, - { - "name": "label", - "value": "RA-05", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ra-05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#8df72805-2e5c-4731-a73e-81db0f0318d0", - "rel": "reference" - }, - { - "href": "#155f941a-cba9-4afd-9ca6-5d040d697ba9", - "rel": "reference" - }, - { - "href": "#a21aef46-7330-48a0-b2e1-c5bb8b2dd11d", - "rel": "reference" - }, - { - "href": "#4895b4cd-34c5-4667-bf8a-27d443c12047", - "rel": "reference" - }, - { - "href": "#122177fa-c4ed-485d-8345-3082c0fb9a06", - "rel": "reference" - }, - { - "href": "#8016d2ed-d30f-4416-9c45-0f42c7aa3232", - "rel": "reference" - }, - { - "href": "#aa5d04e0-6090-4e17-84d4-b9963d55fc2c", - "rel": "reference" - }, - { - "href": "#d2ebec9b-f868-4ee1-a2bd-0b2282aed248", - "rel": "reference" - }, - { - "href": "#4c501da5-9d79-4cb6-ba80-97260e1ce327", - "rel": "reference" - }, - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#ca-8", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#ra-2", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#sa-11", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-38", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - }, - { - "href": "#sr-11", - "rel": "related" - } - ], - "parts": [ - { - "id": "ra-5_smt", - "name": "statement", - "parts": [ - { - "id": "ra-5_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Monitor and scan for vulnerabilities in the system and hosted applications {{ insert: param, ra-5_prm_1 }} and when new vulnerabilities potentially affecting the system are identified and reported;" - }, - { - "id": "ra-5_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Employ vulnerability monitoring tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for:", - "parts": [ - { - "id": "ra-5_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Enumerating platforms, software flaws, and improper configurations;" - }, - { - "id": "ra-5_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Formatting checklists and test procedures; and" - }, - { - "id": "ra-5_smt.b.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Measuring vulnerability impact;" - } - ] - }, - { - "id": "ra-5_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Analyze vulnerability scan reports and results from vulnerability monitoring;" - }, - { - "id": "ra-5_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Remediate legitimate vulnerabilities {{ insert: param, ra-05_odp.03 }} in accordance with an organizational assessment of risk;" - }, - { - "id": "ra-5_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Share information obtained from the vulnerability monitoring process and control assessments with {{ insert: param, ra-05_odp.04 }} to help eliminate similar vulnerabilities in other systems; and" - }, - { - "id": "ra-5_smt.f", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "f." - } - ], - "prose": "Employ vulnerability monitoring tools that include the capability to readily update the vulnerabilities to be scanned." - } - ] - }, - { - "id": "ra-5_gdn", - "name": "guidance", - "prose": "Security categorization of information and systems guides the frequency and comprehensiveness of vulnerability monitoring (including scans). Organizations determine the required vulnerability monitoring for system components, ensuring that the potential sources of vulnerabilities—such as infrastructure components (e.g., switches, routers, guards, sensors), networked printers, scanners, and copiers—are not overlooked. The capability to readily update vulnerability monitoring tools as new vulnerabilities are discovered and announced and as new scanning methods are developed helps to ensure that new vulnerabilities are not missed by employed vulnerability monitoring tools. The vulnerability monitoring tool update process helps to ensure that potential vulnerabilities in the system are identified and addressed as quickly as possible. Vulnerability monitoring and analyses for custom software may require additional approaches, such as static analysis, dynamic analysis, binary analysis, or a hybrid of the three approaches. Organizations can use these analysis approaches in source code reviews and in a variety of tools, including web-based application scanners, static analysis tools, and binary analyzers.\n\nVulnerability monitoring includes scanning for patch levels; scanning for functions, ports, protocols, and services that should not be accessible to users or devices; and scanning for flow control mechanisms that are improperly configured or operating incorrectly. Vulnerability monitoring may also include continuous vulnerability monitoring tools that use instrumentation to continuously analyze components. Instrumentation-based tools may improve accuracy and may be run throughout an organization without scanning. Vulnerability monitoring tools that facilitate interoperability include tools that are Security Content Automated Protocol (SCAP)-validated. Thus, organizations consider using scanning tools that express vulnerabilities in the Common Vulnerabilities and Exposures (CVE) naming convention and that employ the Open Vulnerability Assessment Language (OVAL) to determine the presence of vulnerabilities. Sources for vulnerability information include the Common Weakness Enumeration (CWE) listing and the National Vulnerability Database (NVD). Control assessments, such as red team exercises, provide additional sources of potential vulnerabilities for which to scan. Organizations also consider using scanning tools that express vulnerability impact by the Common Vulnerability Scoring System (CVSS).\n\nVulnerability monitoring includes a channel and process for receiving reports of security vulnerabilities from the public at-large. Vulnerability disclosure programs can be as simple as publishing a monitored email address or web form that can receive reports, including notification authorizing good-faith research and disclosure of security vulnerabilities. Organizations generally expect that such research is happening with or without their authorization and can use public vulnerability disclosure channels to increase the likelihood that discovered vulnerabilities are reported directly to the organization for remediation.\n\nOrganizations may also employ the use of financial incentives (also known as \"bug bounties\" ) to further encourage external security researchers to report discovered vulnerabilities. Bug bounty programs can be tailored to the organization’s needs. Bounties can be operated indefinitely or over a defined period of time and can be offered to the general public or to a curated group. Organizations may run public and private bounties simultaneously and could choose to offer partially credentialed access to certain participants in order to evaluate security vulnerabilities from privileged vantage points." - }, - { - "id": "ra-5_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "RA-5 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "ra-5_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "See the FedRAMP Documents page\\> Vulnerability Scanning Requirements https://www.FedRAMP.gov/documents/" - }, - { - "id": "ra-5_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(a) Requirement:" - } - ], - "prose": "an accredited independent assessor scans operating systems/infrastructure, web applications, and databases once annually." - }, - { - "id": "ra-5_fr_smt.2", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(d) Requirement:" - } - ], - "prose": "If a vulnerability is listed among the CISA Known Exploited Vulnerability (KEV) Catalog (https://www.cisa.gov/known-exploited-vulnerabilities-catalog) the KEV remediation date supersedes the FedRAMP parameter requirement." - }, - { - "id": "ra-5_fr_smt.3", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(e) Requirement:" - } - ], - "prose": "to include all Authorizing Officials." - }, - { - "id": "ra-5_fr_gdn.2", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Informational findings from a scanner are detailed as a returned result that holds no vulnerability risk or severity and for FedRAMP does not require an entry onto the POA\\&M or entry onto the RET during any assessment phase.\n\nWarning findings, on the other hand, are given a risk rating (low, moderate, high or critical) by the scanning solution and should be treated like any other finding with a risk or severity rating for tracking purposes onto either the POA\\&M or RET depending on when the findings originated (during assessments or during monthly continuous monitoring). If a warning is received during scanning, but further validation turns up no actual issue then this item should be categorized as a false positive. If this situation presents itself during an assessment phase (initial assessment, annual assessment or any SCR), follow guidance on how to report false positives in the Security Assessment Report (SAR). If this situation happens during monthly continuous monitoring, a deviation request will need to be submitted per the FedRAMP Vulnerability Deviation Request Form.\n\nWarnings are commonly associated with scanning solutions that also perform compliance scans, and if the scanner reports a \"warning\" as part of the compliance scanning of a CSO, follow guidance surrounding the tracking of compliance findings during either the assessment phases (initial assessment, annual assessment or any SCR) or monthly continuous monitoring as it applies. Guidance on compliance scan findings can be found by searching on \"Tracking of Compliance Scans\" in FAQs." - } - ] - }, - { - "id": "ra-5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-05", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ra-5_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-05a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ra-5_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-05a.[01]", - "class": "sp800-53a" - } - ], - "prose": "systems and hosted applications are monitored for vulnerabilities {{ insert: param, ra-05_odp.01 }} and when new vulnerabilities potentially affecting the system are identified and reported;", - "links": [ - { - "href": "#ra-5_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-5_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-05a.[02]", - "class": "sp800-53a" - } - ], - "prose": "systems and hosted applications are scanned for vulnerabilities {{ insert: param, ra-05_odp.02 }} and when new vulnerabilities potentially affecting the system are identified and reported;", - "links": [ - { - "href": "#ra-5_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ra-5_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-5_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-05b.", - "class": "sp800-53a" - } - ], - "prose": "vulnerability monitoring tools and techniques are employed to facilitate interoperability among tools;", - "parts": [ - { - "id": "ra-5_obj.b.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-05b.01", - "class": "sp800-53a" - } - ], - "prose": "vulnerability monitoring tools and techniques are employed to automate parts of the vulnerability management process by using standards for enumerating platforms, software flaws, and improper configurations;", - "links": [ - { - "href": "#ra-5_smt.b.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-5_obj.b.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-05b.02", - "class": "sp800-53a" - } - ], - "prose": "vulnerability monitoring tools and techniques are employed to facilitate interoperability among tools and to automate parts of the vulnerability management process by using standards for formatting checklists and test procedures;", - "links": [ - { - "href": "#ra-5_smt.b.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-5_obj.b.3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-05b.03", - "class": "sp800-53a" - } - ], - "prose": "vulnerability monitoring tools and techniques are employed to facilitate interoperability among tools and to automate parts of the vulnerability management process by using standards for measuring vulnerability impact;", - "links": [ - { - "href": "#ra-5_smt.b.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ra-5_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-5_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-05c.", - "class": "sp800-53a" - } - ], - "prose": "vulnerability scan reports and results from vulnerability monitoring are analyzed;", - "links": [ - { - "href": "#ra-5_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-5_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-05d.", - "class": "sp800-53a" - } - ], - "prose": "legitimate vulnerabilities are remediated {{ insert: param, ra-05_odp.03 }} in accordance with an organizational assessment of risk;", - "links": [ - { - "href": "#ra-5_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-5_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-05e.", - "class": "sp800-53a" - } - ], - "prose": "information obtained from the vulnerability monitoring process and control assessments is shared with {{ insert: param, ra-05_odp.04 }} to help eliminate similar vulnerabilities in other systems;", - "links": [ - { - "href": "#ra-5_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-5_obj.f", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-05f.", - "class": "sp800-53a" - } - ], - "prose": "vulnerability monitoring tools that include the capability to readily update the vulnerabilities to be scanned are employed.", - "links": [ - { - "href": "#ra-5_smt.f", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ra-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "RA-05-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Risk assessment policy\n\nprocedures addressing vulnerability scanning\n\nrisk assessment\n\nassessment report\n\nvulnerability scanning tools and associated configuration documentation\n\nvulnerability scanning results\n\npatch and vulnerability management records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ra-5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "RA-05-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with risk assessment, control assessment, and vulnerability scanning responsibilities\n\norganizational personnel with vulnerability scan analysis responsibilities\n\norganizational personnel with vulnerability remediation responsibilities\n\norganizational personnel with security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "ra-5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "RA-05-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for vulnerability scanning, analysis, remediation, and information sharing\n\nmechanisms supporting and/or implementing vulnerability scanning, analysis, remediation, and information sharing" - } - ] - } - ], - "controls": [ - { - "id": "ra-5.2", - "class": "SP800-53-enhancement", - "title": "Update Vulnerabilities to Be Scanned", - "params": [ - { - "id": "ra-05.02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ra-5.2_prm_1" - }, - { - "name": "label", - "value": "RA-05(02)_ODP[01]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "within 24 hours prior to running scans" - } - ] - }, - { - "id": "ra-05.02_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ra-5.2_prm_2" - }, - { - "name": "label", - "value": "RA-05(02)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "guidelines": [ - { - "prose": "the frequency for updating the system vulnerabilities to be scanned is defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "RA-05(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "RA-5(2)" - }, - { - "name": "label", - "value": "RA-05(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ra-05.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ra-5", - "rel": "required" - }, - { - "href": "#si-5", - "rel": "related" - } - ], - "parts": [ - { - "id": "ra-5.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Update the system vulnerabilities to be scanned {{ insert: param, ra-05.02_odp.01 }}." - }, - { - "id": "ra-5.2_gdn", - "name": "guidance", - "prose": "Due to the complexity of modern software, systems, and other factors, new vulnerabilities are discovered on a regular basis. It is important that newly discovered vulnerabilities are added to the list of vulnerabilities to be scanned to ensure that the organization can take steps to mitigate those vulnerabilities in a timely manner." - }, - { - "id": "ra-5.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-05(02)", - "class": "sp800-53a" - } - ], - "prose": "the system vulnerabilities to be scanned are updated {{ insert: param, ra-05.02_odp.01 }}.", - "links": [ - { - "href": "#ra-5.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-5.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "RA-05(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Procedures addressing vulnerability scanning\n\nassessment report\n\nvulnerability scanning tools and associated configuration documentation\n\nvulnerability scanning results\n\npatch and vulnerability management records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ra-5.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "RA-05(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with vulnerability scanning responsibilities\n\norganizational personnel with vulnerability scan analysis responsibilities\n\norganizational personnel with security responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "ra-5.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "RA-05(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for vulnerability scanning\n\nmechanisms/tools supporting and/or implementing vulnerability scanning" - } - ] - } - ] - }, - { - "id": "ra-5.3", - "class": "SP800-53-enhancement", - "title": "Breadth and Depth of Coverage", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "RA-05(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "RA-5(3)" - }, - { - "name": "label", - "value": "RA-05(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ra-05.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ra-5", - "rel": "required" - } - ], - "parts": [ - { - "id": "ra-5.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Define the breadth and depth of vulnerability scanning coverage." - }, - { - "id": "ra-5.3_gdn", - "name": "guidance", - "prose": "The breadth of vulnerability scanning coverage can be expressed as a percentage of components within the system, by the particular types of systems, by the criticality of systems, or by the number of vulnerabilities to be checked. Conversely, the depth of vulnerability scanning coverage can be expressed as the level of the system design that the organization intends to monitor (e.g., component, module, subsystem, element). Organizations can determine the sufficiency of vulnerability scanning coverage with regard to its risk tolerance and other factors. Scanning tools and how the tools are configured may affect the depth and coverage. Multiple scanning tools may be needed to achieve the desired depth and coverage. [SP 800-53A](#a21aef46-7330-48a0-b2e1-c5bb8b2dd11d) provides additional information on the breadth and depth of coverage." - }, - { - "id": "ra-5.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-05(03)", - "class": "sp800-53a" - } - ], - "prose": "the breadth and depth of vulnerability scanning coverage are defined.", - "links": [ - { - "href": "#ra-5.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-5.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "RA-05(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Procedures addressing vulnerability scanning\n\nassessment report\n\nvulnerability scanning tools and associated configuration documentation\n\nvulnerability scanning results\n\npatch and vulnerability management records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ra-5.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "RA-05(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with vulnerability scanning responsibilities\n\norganizational personnel with vulnerability scan analysis responsibilities\n\norganizational personnel with security responsibilities" - } - ] - }, - { - "id": "ra-5.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "RA-05(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for vulnerability scanning\n\nmechanisms/tools supporting and/or implementing vulnerability scanning" - } - ] - } - ] - }, - { - "id": "ra-5.4", - "class": "SP800-53-enhancement", - "title": "Discoverable Information", - "params": [ - { - "id": "ra-05.04_odp", - "props": [ - { - "name": "alt-identifier", - "value": "ra-5.4_prm_1" - }, - { - "name": "label", - "value": "RA-05(04)_ODP", - "class": "sp800-53a" - } - ], - "label": "corrective actions", - "constraints": [ - { - "description": "notify appropriate service provider personnel and follow procedures for organization and service provider-defined corrective actions" - } - ], - "guidelines": [ - { - "prose": "corrective actions to be taken if information about the system is discoverable are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "RA-05(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "RA-5(4)" - }, - { - "name": "label", - "value": "RA-05(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ra-05.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ra-5", - "rel": "required" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-13", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-26", - "rel": "related" - } - ], - "parts": [ - { - "id": "ra-5.4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Determine information about the system that is discoverable and take {{ insert: param, ra-05.04_odp }}." - }, - { - "id": "ra-5.4_gdn", - "name": "guidance", - "prose": "Discoverable information includes information that adversaries could obtain without compromising or breaching the system, such as by collecting information that the system is exposing or by conducting extensive web searches. Corrective actions include notifying appropriate organizational personnel, removing designated information, or changing the system to make the designated information less relevant or attractive to adversaries. This enhancement excludes intentionally discoverable information that may be part of a decoy capability (e.g., honeypots, honeynets, or deception nets) deployed by the organization." - }, - { - "id": "ra-5.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-05(04)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ra-5.4_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-05(04)[01]", - "class": "sp800-53a" - } - ], - "prose": "information about the system is discoverable;", - "links": [ - { - "href": "#ra-5.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-5.4_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-05(04)[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, ra-05.04_odp }} are taken when information about the system is confirmed as discoverable.", - "links": [ - { - "href": "#ra-5.4_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ra-5.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-5.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "RA-05(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Procedures addressing vulnerability scanning\n\nassessment report\n\npenetration test results\n\nvulnerability scanning results\n\nrisk assessment report\n\nrecords of corrective actions taken\n\nincident response records\n\naudit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ra-5.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "RA-05(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with vulnerability scanning and/or penetration testing responsibilities\n\norganizational personnel with vulnerability scan analysis responsibilities\n\norganizational personnel responsible for risk response\n\norganizational personnel responsible for incident management and response\n\norganizational personnel with security responsibilities" - } - ] - }, - { - "id": "ra-5.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "RA-05(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for vulnerability scanning\n\norganizational processes for risk response\n\norganizational processes for incident management and response\n\nmechanisms/tools supporting and/or implementing vulnerability scanning\n\nmechanisms supporting and/or implementing risk response\n\nmechanisms supporting and/or implementing incident management and response" - } - ] - } - ] - }, - { - "id": "ra-5.5", - "class": "SP800-53-enhancement", - "title": "Privileged Access", - "params": [ - { - "id": "ra-05.05_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ra-5.5_prm_1" - }, - { - "name": "label", - "value": "RA-05(05)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "system components", - "constraints": [ - { - "description": "all components that support authentication" - } - ], - "guidelines": [ - { - "prose": "system components to which privileged access is authorized for selected vulnerability scanning activities are defined;" - } - ] - }, - { - "id": "ra-05.05_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ra-5.5_prm_2" - }, - { - "name": "label", - "value": "RA-05(05)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "vulnerability scanning activities", - "constraints": [ - { - "description": "all scans" - } - ], - "guidelines": [ - { - "prose": "vulnerability scanning activities selected for privileged access authorization to system components are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "RA-05(05)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "RA-5(5)" - }, - { - "name": "label", - "value": "RA-05(05)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ra-05.05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ra-5", - "rel": "required" - } - ], - "parts": [ - { - "id": "ra-5.5_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement privileged access authorization to {{ insert: param, ra-05.05_odp.01 }} for {{ insert: param, ra-05.05_odp.02 }}." - }, - { - "id": "ra-5.5_gdn", - "name": "guidance", - "prose": "In certain situations, the nature of the vulnerability scanning may be more intrusive, or the system component that is the subject of the scanning may contain classified or controlled unclassified information, such as personally identifiable information. Privileged access authorization to selected system components facilitates more thorough vulnerability scanning and protects the sensitive nature of such scanning." - }, - { - "id": "ra-5.5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-05(05)", - "class": "sp800-53a" - } - ], - "prose": "privileged access authorization is implemented to {{ insert: param, ra-05.05_odp.01 }} for {{ insert: param, ra-05.05_odp.02 }}.", - "links": [ - { - "href": "#ra-5.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-5.5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "RA-05(05)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Risk assessment policy\n\nprocedures addressing vulnerability scanning\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of system components for vulnerability scanning\n\npersonnel access authorization list\n\nauthorization credentials\n\naccess authorization records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ra-5.5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "RA-05(05)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with vulnerability scanning responsibilities\n\nsystem/network administrators\n\norganizational personnel responsible for access control to the system\n\norganizational personnel responsible for configuration management of the system\n\nsystem developers\n\norganizational personnel with security responsibilities" - } - ] - }, - { - "id": "ra-5.5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "RA-05(05)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for vulnerability scanning\n\norganizational processes for access control\n\nmechanisms supporting and/or implementing access control\n\nmechanisms/tools supporting and/or implementing vulnerability scanning" - } - ] - } - ] - }, - { - "id": "ra-5.8", - "class": "SP800-53-enhancement", - "title": "Review Historic Audit Logs", - "params": [ - { - "id": "ra-05.08_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ra-5.8_prm_1" - }, - { - "name": "label", - "value": "RA-05(08)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "system", - "guidelines": [ - { - "prose": "a system whose historic audit logs are to be reviewed is defined;" - } - ] - }, - { - "id": "ra-05.08_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ra-5.8_prm_2" - }, - { - "name": "label", - "value": "RA-05(08)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "time period", - "guidelines": [ - { - "prose": "a time period for a potential previous exploit of a system is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "RA-05(08)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "RA-5(8)" - }, - { - "name": "label", - "value": "RA-05(08)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ra-05.08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ra-5", - "rel": "required" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-11", - "rel": "related" - } - ], - "parts": [ - { - "id": "ra-5.8_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Review historic audit logs to determine if a vulnerability identified in a {{ insert: param, ra-05.08_odp.01 }} has been previously exploited within an {{ insert: param, ra-05.08_odp.02 }}." - }, - { - "id": "ra-5.8_gdn", - "name": "guidance", - "prose": "Reviewing historic audit logs to determine if a recently detected vulnerability in a system has been previously exploited by an adversary can provide important information for forensic analyses. Such analyses can help identify, for example, the extent of a previous intrusion, the trade craft employed during the attack, organizational information exfiltrated or modified, mission or business capabilities affected, and the duration of the attack." - }, - { - "id": "ra-5.8_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "RA-5(8) Additional FedRAMP Requirement", - "parts": [ - { - "id": "ra-5.8_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "This enhancement is required for all high (or critical) vulnerability scan findings." - } - ] - }, - { - "id": "ra-5.8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-05(08)", - "class": "sp800-53a" - } - ], - "prose": "historic audit logs are reviewed to determine if a vulnerability identified in a {{ insert: param, ra-05.08_odp.01 }} has been previously exploited within {{ insert: param, ra-05.08_odp.02 }}.", - "links": [ - { - "href": "#ra-5.8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-5.8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "RA-05(08)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Risk assessment policy\n\nprocedures addressing vulnerability scanning\n\naudit logs\n\nrecords of audit log reviews\n\nvulnerability scanning results\n\npatch and vulnerability management records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ra-5.8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "RA-05(08)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with vulnerability scanning responsibilities\n\norganizational personnel with vulnerability scan analysis responsibilities\n\norganizational personnel with audit record review responsibilities\n\nsystem/network administrators\n\norganizational personnel with security responsibilities" - } - ] - }, - { - "id": "ra-5.8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "RA-05(08)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for vulnerability scanning\n\norganizational process for audit record review and response\n\nmechanisms/tools supporting and/or implementing vulnerability scanning\n\nmechanisms supporting and/or implementing audit record review" - } - ] - } - ] - }, - { - "id": "ra-5.11", - "class": "SP800-53-enhancement", - "title": "Public Disclosure Program", - "props": [ - { - "name": "label", - "value": "RA-05(11)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "RA-5(11)" - }, - { - "name": "label", - "value": "RA-05(11)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ra-05.11" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ra-5", - "rel": "required" - } - ], - "parts": [ - { - "id": "ra-5.11_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Establish a public reporting channel for receiving reports of vulnerabilities in organizational systems and system components." - }, - { - "id": "ra-5.11_gdn", - "name": "guidance", - "prose": "The reporting channel is publicly discoverable and contains clear language authorizing good-faith research and the disclosure of vulnerabilities to the organization. The organization does not condition its authorization on an expectation of indefinite non-disclosure to the public by the reporting entity but may request a specific time period to properly remediate the vulnerability." - }, - { - "id": "ra-5.11_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-05(11)", - "class": "sp800-53a" - } - ], - "prose": "a public reporting channel is established for receiving reports of vulnerabilities in organizational systems and system components.", - "links": [ - { - "href": "#ra-5.11_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-5.11_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "RA-05(11)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Risk assessment policy\n\nprocedures addressing vulnerability scanning\n\nrisk assessment\n\nvulnerability scanning tools and techniques documentation\n\nvulnerability scanning results\n\nvulnerability management records\n\naudit records\n\npublic reporting channel\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ra-5.11_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "RA-05(11)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with vulnerability scanning responsibilities\n\norganizational personnel with vulnerability scan analysis responsibilities\n\norganizational personnel with security responsibilities" - } - ] - }, - { - "id": "ra-5.11_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "RA-05(11)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for vulnerability scanning\n\nmechanisms/tools supporting and/or implementing vulnerability scanning\n\nmechanisms implementing the public reporting of vulnerabilities" - } - ] - } - ] - } - ] - }, - { - "id": "ra-7", - "class": "SP800-53", - "title": "Risk Response", - "props": [ - { - "name": "label", - "value": "RA-07", - "class": "zero-padded" - }, - { - "name": "label", - "value": "RA-7" - }, - { - "name": "label", - "value": "RA-07", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ra-07" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#628d22a1-6a11-4784-bc59-5cd9497b5445", - "rel": "reference" - }, - { - "href": "#599fb53d-5041-444e-a7fe-640d6d30ad05", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#482e4c99-9dc4-41ad-bba8-0f3f0032c1f8", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "#ca-5", - "rel": "related" - }, - { - "href": "#ir-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-28", - "rel": "related" - }, - { - "href": "#ra-2", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#sr-2", - "rel": "related" - } - ], - "parts": [ - { - "id": "ra-7_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Respond to findings from security and privacy assessments, monitoring, and audits in accordance with organizational risk tolerance." - }, - { - "id": "ra-7_gdn", - "name": "guidance", - "prose": "Organizations have many options for responding to risk including mitigating risk by implementing new controls or strengthening existing controls, accepting risk with appropriate justification or rationale, sharing or transferring risk, or avoiding risk. The risk tolerance of the organization influences risk response decisions and actions. Risk response addresses the need to determine an appropriate response to risk before generating a plan of action and milestones entry. For example, the response may be to accept risk or reject risk, or it may be possible to mitigate the risk immediately so that a plan of action and milestones entry is not needed. However, if the risk response is to mitigate the risk, and the mitigation cannot be completed immediately, a plan of action and milestones entry is generated." - }, - { - "id": "ra-7_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-07", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "ra-7_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-07[01]", - "class": "sp800-53a" - } - ], - "prose": "findings from security assessments are responded to in accordance with organizational risk tolerance;", - "links": [ - { - "href": "#ra-7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-7_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-07[02]", - "class": "sp800-53a" - } - ], - "prose": "findings from privacy assessments are responded to in accordance with organizational risk tolerance;", - "links": [ - { - "href": "#ra-7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-7_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-07[03]", - "class": "sp800-53a" - } - ], - "prose": "findings from monitoring are responded to in accordance with organizational risk tolerance;", - "links": [ - { - "href": "#ra-7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-7_obj-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "RA-07[04]", - "class": "sp800-53a" - } - ], - "prose": "findings from audits are responded to in accordance with organizational risk tolerance.", - "links": [ - { - "href": "#ra-7_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#ra-7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-7_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "RA-07-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Risk assessment policy\n\nassessment reports\n\naudit records/event logs\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ra-7_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "RA-07-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with assessment and auditing responsibilities\n\nsystem/network administrators\n\norganizational personnel with security and privacy responsibilities" - } - ] - }, - { - "id": "ra-7_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "RA-07-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for assessments and audits\n\nmechanisms/tools supporting and/or implementing assessments and auditing" - } - ] - } - ] - }, - { - "id": "ra-9", - "class": "SP800-53", - "title": "Criticality Analysis", - "params": [ - { - "id": "ra-09_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "ra-9_prm_1" - }, - { - "name": "label", - "value": "RA-09_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "systems, system components, or system services", - "guidelines": [ - { - "prose": "systems, system components, or system services to be analyzed for criticality are defined;" - } - ] - }, - { - "id": "ra-09_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "ra-9_prm_2" - }, - { - "name": "label", - "value": "RA-09_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "decision points in the system development life cycle", - "guidelines": [ - { - "prose": "decision points in the system development life cycle when a criticality analysis is to be performed are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "RA-09", - "class": "zero-padded" - }, - { - "name": "label", - "value": "RA-9" - }, - { - "name": "label", - "value": "RA-09", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "ra-09" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#d4296805-2dca-4c63-a95f-eeccaa826aec", - "rel": "reference" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#pl-8", - "rel": "related" - }, - { - "href": "#pl-11", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-1", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-11", - "rel": "related" - }, - { - "href": "#ra-2", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sa-20", - "rel": "related" - }, - { - "href": "#sr-5", - "rel": "related" - } - ], - "parts": [ - { - "id": "ra-9_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Identify critical system components and functions by performing a criticality analysis for {{ insert: param, ra-09_odp.01 }} at {{ insert: param, ra-09_odp.02 }}." - }, - { - "id": "ra-9_gdn", - "name": "guidance", - "prose": "Not all system components, functions, or services necessarily require significant protections. For example, criticality analysis is a key tenet of supply chain risk management and informs the prioritization of protection activities. The identification of critical system components and functions considers applicable laws, executive orders, regulations, directives, policies, standards, system functionality requirements, system and component interfaces, and system and component dependencies. Systems engineers conduct a functional decomposition of a system to identify mission-critical functions and components. The functional decomposition includes the identification of organizational missions supported by the system, decomposition into the specific functions to perform those missions, and traceability to the hardware, software, and firmware components that implement those functions, including when the functions are shared by many components within and external to the system.\n\nThe operational environment of a system or a system component may impact the criticality, including the connections to and dependencies on cyber-physical systems, devices, system-of-systems, and outsourced IT services. System components that allow unmediated access to critical system components or functions are considered critical due to the inherent vulnerabilities that such components create. Component and function criticality are assessed in terms of the impact of a component or function failure on the organizational missions that are supported by the system that contains the components and functions.\n\nCriticality analysis is performed when an architecture or design is being developed, modified, or upgraded. If such analysis is performed early in the system development life cycle, organizations may be able to modify the system design to reduce the critical nature of these components and functions, such as by adding redundancy or alternate paths into the system design. Criticality analysis can also influence the protection measures required by development contractors. In addition to criticality analysis for systems, system components, and system services, criticality analysis of information is an important consideration. Such analysis is conducted as part of security categorization in [RA-2](#ra-2)." - }, - { - "id": "ra-9_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "RA-09", - "class": "sp800-53a" - } - ], - "prose": "critical system components and functions are identified by performing a criticality analysis for {{ insert: param, ra-09_odp.01 }} at {{ insert: param, ra-09_odp.02 }}.", - "links": [ - { - "href": "#ra-9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "ra-9_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "RA-09-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Risk assessment policy\n\nassessment reports\n\ncriticality analysis/finalized criticality for each component/subcomponent\n\naudit records/event logs\n\nanalysis reports\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "ra-9_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "RA-09-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with assessment and auditing responsibilities\n\norganizational personnel with criticality analysis responsibilities\n\nsystem/network administrators\n\norganizational personnel with security responsibilities" - } - ] - }, - { - "id": "ra-9_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "RA-09-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for assessments and audits\n\nmechanisms/tools supporting and/or implementing assessments and auditing" - } - ] - } - ] - } - ] - }, - { - "id": "sa", - "class": "family", - "title": "System and Services Acquisition", - "controls": [ - { - "id": "sa-1", - "class": "SP800-53", - "title": "Policy and Procedures", - "params": [ - { - "id": "sa-1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "sa-01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "sa-01_odp.02" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "sa-01_odp.01", - "props": [ - { - "name": "label", - "value": "SA-01_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the system and services acquisition policy is to be disseminated is/are defined;" - } - ] - }, - { - "id": "sa-01_odp.02", - "props": [ - { - "name": "label", - "value": "SA-01_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the system and services acquisition procedures are to be disseminated is/are defined;" - } - ] - }, - { - "id": "sa-01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "sa-1_prm_2" - }, - { - "name": "label", - "value": "SA-01_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "organization-level", - "mission/business process-level", - "system-level" - ] - } - }, - { - "id": "sa-01_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "sa-1_prm_3" - }, - { - "name": "label", - "value": "SA-01_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "official", - "guidelines": [ - { - "prose": "an official to manage the system and services acquisition policy and procedures is defined;" - } - ] - }, - { - "id": "sa-01_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "sa-1_prm_4" - }, - { - "name": "label", - "value": "SA-01_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current system and services acquisition policy is reviewed and updated is defined;" - } - ] - }, - { - "id": "sa-01_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "sa-1_prm_5" - }, - { - "name": "label", - "value": "SA-01_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that would require the current system and services acquisition policy to be reviewed and updated are defined;" - } - ] - }, - { - "id": "sa-01_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "sa-1_prm_6" - }, - { - "name": "label", - "value": "SA-01_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current system and services acquisition procedures are reviewed and updated is defined;" - } - ] - }, - { - "id": "sa-01_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "sa-1_prm_7" - }, - { - "name": "label", - "value": "SA-01_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "events", - "constraints": [ - { - "description": "significant changes" - } - ], - "guidelines": [ - { - "prose": "events that would require the system and services acquisition procedures to be reviewed and updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SA-01", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-1" - }, - { - "name": "label", - "value": "SA-01", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#c7ac44e8-10db-4b64-b2b9-9e32ec1efed0", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#4c0ec2ee-a0d6-428a-9043-4504bc3ade6f", - "rel": "reference" - }, - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-1_smt", - "name": "statement", - "parts": [ - { - "id": "sa-1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, a policy that addresses System and Services Acquisition MUST be associated with SA-1 part a.", - "class": "policy" - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, at least one procedure that addresses System and Services Acquisition MUST be associated with SA-1 part a.", - "class": "procedure" - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, document, and disseminate to {{ insert: param, sa-1_prm_1 }}:", - "parts": [ - { - "id": "sa-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, sa-01_odp.03 }} system and services acquisition policy that:", - "parts": [ - { - "id": "sa-1_smt.a.1.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "sa-1_smt.a.1.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and" - } - ] - }, - { - "id": "sa-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the system and services acquisition policy and the associated system and services acquisition controls;" - } - ] - }, - { - "id": "sa-1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Designate an {{ insert: param, sa-01_odp.04 }} to manage the development, documentation, and dissemination of the system and services acquisition policy and procedures; and" - }, - { - "id": "sa-1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the current system and services acquisition:", - "parts": [ - { - "id": "sa-1_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Policy {{ insert: param, sa-01_odp.05 }} and following {{ insert: param, sa-01_odp.06 }} ; and" - }, - { - "id": "sa-1_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures {{ insert: param, sa-01_odp.07 }} and following {{ insert: param, sa-01_odp.08 }}." - } - ] - } - ] - }, - { - "id": "sa-1_gdn", - "name": "guidance", - "prose": "System and services acquisition policy and procedures address the controls in the SA family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of system and services acquisition policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to system and services acquisition policy and procedures include assessment or audit findings, security incidents or breaches, or changes in laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure." - }, - { - "id": "sa-1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-01a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-01a.[01]", - "class": "sp800-53a" - } - ], - "prose": "a system and services acquisition policy is developed and documented;", - "links": [ - { - "href": "#sa-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-01a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the system and services acquisition policy is disseminated to {{ insert: param, sa-01_odp.01 }};", - "links": [ - { - "href": "#sa-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-1_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-01a.[03]", - "class": "sp800-53a" - } - ], - "prose": "system and services acquisition procedures to facilitate the implementation of the system and services acquisition policy and associated system and services acquisition controls are developed and documented;", - "links": [ - { - "href": "#sa-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-1_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-01a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the system and services acquisition procedures are disseminated to {{ insert: param, sa-01_odp.02 }};", - "links": [ - { - "href": "#sa-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-1_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-01a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-1_obj.a.1.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-01a.01(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-1_obj.a.1.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-01a.01(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sa-01_odp.03 }} system and services acquisition policy addresses purpose;", - "links": [ - { - "href": "#sa-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-1_obj.a.1.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-01a.01(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sa-01_odp.03 }} system and services acquisition policy addresses scope;", - "links": [ - { - "href": "#sa-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-1_obj.a.1.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-01a.01(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sa-01_odp.03 }} system and services acquisition policy addresses roles;", - "links": [ - { - "href": "#sa-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-1_obj.a.1.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-01a.01(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sa-01_odp.03 }} system and services acquisition policy addresses responsibilities;", - "links": [ - { - "href": "#sa-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-1_obj.a.1.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-01a.01(a)[05]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sa-01_odp.03 }} system and services acquisition policy addresses management commitment;", - "links": [ - { - "href": "#sa-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-1_obj.a.1.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-01a.01(a)[06]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sa-01_odp.03 }} system and services acquisition policy addresses coordination among organizational entities;", - "links": [ - { - "href": "#sa-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-1_obj.a.1.a-7", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-01a.01(a)[07]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sa-01_odp.03 }} system and services acquisition policy addresses compliance;", - "links": [ - { - "href": "#sa-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-1_obj.a.1.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-01a.01(b)", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sa-01_odp.03 }} system and services acquisition policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines;", - "links": [ - { - "href": "#sa-1_smt.a.1.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-1_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-01b.", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sa-01_odp.04 }} is designated to manage the development, documentation, and dissemination of the system and services acquisition policy and procedures;", - "links": [ - { - "href": "#sa-1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-01c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-1_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-01c.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-1_obj.c.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-01c.01[01]", - "class": "sp800-53a" - } - ], - "prose": "the system and services acquisition policy is reviewed and updated {{ insert: param, sa-01_odp.05 }};", - "links": [ - { - "href": "#sa-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-1_obj.c.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-01c.01[02]", - "class": "sp800-53a" - } - ], - "prose": "the current system and services acquisition policy is reviewed and updated following {{ insert: param, sa-01_odp.06 }};", - "links": [ - { - "href": "#sa-1_smt.c.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-1_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-01c.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-1_obj.c.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-01c.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the current system and services acquisition procedures are reviewed and updated {{ insert: param, sa-01_odp.07 }};", - "links": [ - { - "href": "#sa-1_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-1_obj.c.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-01c.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the current system and services acquisition procedures are reviewed and updated following {{ insert: param, sa-01_odp.08 }}.", - "links": [ - { - "href": "#sa-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-1_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-01-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nsystem and services acquisition procedures\n\nsupply chain risk management policy\n\nsupply chain risk management procedures\n\nsupply chain risk management plan\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-01-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\norganizational personnel with supply chain risk management responsibilities" - } - ] - } - ] - }, - { - "id": "sa-2", - "class": "SP800-53", - "title": "Allocation of Resources", - "props": [ - { - "name": "label", - "value": "SA-02", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-2" - }, - { - "name": "label", - "value": "SA-02", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#482e4c99-9dc4-41ad-bba8-0f3f0032c1f8", - "rel": "reference" - }, - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pl-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-11", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - }, - { - "href": "#sr-3", - "rel": "related" - }, - { - "href": "#sr-5", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-2_smt", - "name": "statement", - "parts": [ - { - "id": "sa-2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Determine the high-level information security and privacy requirements for the system or system service in mission and business process planning;" - }, - { - "id": "sa-2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Determine, document, and allocate the resources required to protect the system or system service as part of the organizational capital planning and investment control process; and" - }, - { - "id": "sa-2_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Establish a discrete line item for information security and privacy in organizational programming and budgeting documentation." - } - ] - }, - { - "id": "sa-2_gdn", - "name": "guidance", - "prose": "Resource allocation for information security and privacy includes funding for system and services acquisition, sustainment, and supply chain-related risks throughout the system development life cycle." - }, - { - "id": "sa-2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-02a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-2_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-02a.[01]", - "class": "sp800-53a" - } - ], - "prose": "the high-level information security requirements for the system or system service are determined in mission and business process planning;", - "links": [ - { - "href": "#sa-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-2_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-02a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the high-level privacy requirements for the system or system service are determined in mission and business process planning;", - "links": [ - { - "href": "#sa-2_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-02b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-2_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-02b.[01]", - "class": "sp800-53a" - } - ], - "prose": "the resources required to protect the system or system service are determined and documented as part of the organizational capital planning and investment control process;", - "links": [ - { - "href": "#sa-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-2_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-02b.[02]", - "class": "sp800-53a" - } - ], - "prose": "the resources required to protect the system or system service are allocated as part of the organizational capital planning and investment control process;", - "links": [ - { - "href": "#sa-2_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-2_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-02c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-2_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-02c.[01]", - "class": "sp800-53a" - } - ], - "prose": "a discrete line item for information security is established in organizational programming and budgeting documentation;", - "links": [ - { - "href": "#sa-2_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-2_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-02c.[02]", - "class": "sp800-53a" - } - ], - "prose": "a discrete line item for privacy is established in organizational programming and budgeting documentation.", - "links": [ - { - "href": "#sa-2_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-2_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-02-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nsystem and services acquisition procedures\n\nsystem and services acquisition strategy and plans\n\nprocedures addressing the allocation of resources to information security and privacy requirements\n\nprocedures addressing capital planning and investment control\n\norganizational programming and budgeting documentation\n\nsystem security plan\n\nprivacy plan\n\nsupply chain risk management policy\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-02-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with capital planning, investment control, organizational programming, and budgeting responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\norganizational personnel with supply chain risk management responsibilities" - } - ] - }, - { - "id": "sa-2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SA-02-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for determining information security and privacy requirements\n\norganizational processes for capital planning, programming, and budgeting\n\nmechanisms supporting and/or implementing organizational capital planning, programming, and budgeting" - } - ] - } - ] - }, - { - "id": "sa-3", - "class": "SP800-53", - "title": "System Development Life Cycle", - "params": [ - { - "id": "sa-03_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sa-3_prm_1" - }, - { - "name": "alt-label", - "value": "system development life cycle", - "class": "sp800-53" - }, - { - "name": "label", - "value": "SA-03_ODP", - "class": "sp800-53a" - } - ], - "label": "system-development life cycle", - "guidelines": [ - { - "prose": "system development life cycle is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SA-03", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-3" - }, - { - "name": "label", - "value": "SA-03", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#482e4c99-9dc4-41ad-bba8-0f3f0032c1f8", - "rel": "reference" - }, - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "#7dbd6d9f-29d6-4d1d-9766-f2d77ff3c849", - "rel": "reference" - }, - { - "href": "#f26af0d0-6d72-4a9d-8ecd-01bc21fd4f0e", - "rel": "reference" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#pl-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-7", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-11", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "#sa-17", - "rel": "related" - }, - { - "href": "#sa-22", - "rel": "related" - }, - { - "href": "#sr-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sr-4", - "rel": "related" - }, - { - "href": "#sr-5", - "rel": "related" - }, - { - "href": "#sr-9", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-3_smt", - "name": "statement", - "parts": [ - { - "id": "sa-3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Acquire, develop, and manage the system using {{ insert: param, sa-03_odp }} that incorporates information security and privacy considerations;" - }, - { - "id": "sa-3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Define and document information security and privacy roles and responsibilities throughout the system development life cycle;" - }, - { - "id": "sa-3_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Identify individuals having information security and privacy roles and responsibilities; and" - }, - { - "id": "sa-3_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Integrate the organizational information security and privacy risk management process into system development life cycle activities." - } - ] - }, - { - "id": "sa-3_gdn", - "name": "guidance", - "prose": "A system development life cycle process provides the foundation for the successful development, implementation, and operation of organizational systems. The integration of security and privacy considerations early in the system development life cycle is a foundational principle of systems security engineering and privacy engineering. To apply the required controls within the system development life cycle requires a basic understanding of information security and privacy, threats, vulnerabilities, adverse impacts, and risk to critical mission and business functions. The security engineering principles in [SA-8](#sa-8) help individuals properly design, code, and test systems and system components. Organizations include qualified personnel (e.g., senior agency information security officers, senior agency officials for privacy, security and privacy architects, and security and privacy engineers) in system development life cycle processes to ensure that established security and privacy requirements are incorporated into organizational systems. Role-based security and privacy training programs can ensure that individuals with key security and privacy roles and responsibilities have the experience, skills, and expertise to conduct assigned system development life cycle activities.\n\nThe effective integration of security and privacy requirements into enterprise architecture also helps to ensure that important security and privacy considerations are addressed throughout the system life cycle and that those considerations are directly related to organizational mission and business processes. This process also facilitates the integration of the information security and privacy architectures into the enterprise architecture, consistent with the risk management strategy of the organization. Because the system development life cycle involves multiple organizations, (e.g., external suppliers, developers, integrators, service providers), acquisition and supply chain risk management functions and controls play significant roles in the effective management of the system during the life cycle." - }, - { - "id": "sa-3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-03a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-3_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-03a.[01]", - "class": "sp800-53a" - } - ], - "prose": "the system is acquired, developed, and managed using {{ insert: param, sa-03_odp }} that incorporates information security considerations;", - "links": [ - { - "href": "#sa-3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-3_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-03a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the system is acquired, developed, and managed using {{ insert: param, sa-03_odp }} that incorporates privacy considerations;", - "links": [ - { - "href": "#sa-3_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-03b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-3_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-03b.[01]", - "class": "sp800-53a" - } - ], - "prose": "information security roles and responsibilities are defined and documented throughout the system development life cycle;", - "links": [ - { - "href": "#sa-3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-3_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-03b.[02]", - "class": "sp800-53a" - } - ], - "prose": "privacy roles and responsibilities are defined and documented throughout the system development life cycle;", - "links": [ - { - "href": "#sa-3_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-3_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-03c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-3_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-03c.[01]", - "class": "sp800-53a" - } - ], - "prose": "individuals with information security roles and responsibilities are identified;", - "links": [ - { - "href": "#sa-3_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-3_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-03c.[02]", - "class": "sp800-53a" - } - ], - "prose": "individuals with privacy roles and responsibilities are identified;", - "links": [ - { - "href": "#sa-3_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-3_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-3_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-03d.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-3_obj.d-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-03d.[01]", - "class": "sp800-53a" - } - ], - "prose": "organizational information security risk management processes are integrated into system development life cycle activities;", - "links": [ - { - "href": "#sa-3_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-3_obj.d-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-03d.[02]", - "class": "sp800-53a" - } - ], - "prose": "organizational privacy risk management processes are integrated into system development life cycle activities.", - "links": [ - { - "href": "#sa-3_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-3_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-03-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nsystem and services acquisition procedures\n\nprocedures addressing the integration of information security and privacy and supply chain risk management into the system development life cycle process\n\nsystem development life cycle documentation\n\norganizational risk management strategy\n\ninformation security and privacy risk management strategy documentation\n\nsystem security plan\n\nprivacy plan\n\nprivacy program plan\n\nenterprise architecture documentation\n\nrole-based security and privacy training program documentation\n\ndata mapping documentation\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-03-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with information security and privacy responsibilities\n\norganizational personnel with system life cycle development responsibilities\n\norganizational personnel with supply chain risk management responsibilities" - } - ] - }, - { - "id": "sa-3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SA-03-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for defining and documenting the system development life cycle\n\norganizational processes for identifying system development life cycle roles and responsibilities\n\norganizational processes for integrating information security and privacy and supply chain risk management into the system development life cycle\n\nmechanisms supporting and/or implementing the system development life cycle" - } - ] - } - ] - }, - { - "id": "sa-4", - "class": "SP800-53", - "title": "Acquisition Process", - "params": [ - { - "id": "sa-04_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sa-4_prm_1" - }, - { - "name": "label", - "value": "SA-04_ODP[01]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "standardized contract language", - "{{ insert: param, sa-04_odp.02 }}" - ] - } - }, - { - "id": "sa-04_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sa-4_prm_2" - }, - { - "name": "label", - "value": "SA-04_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "contract language", - "guidelines": [ - { - "prose": "contract language is defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SA-04", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-4" - }, - { - "name": "label", - "value": "SA-04", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#18e71fec-c6fd-475a-925a-5d8495cf8455", - "rel": "reference" - }, - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#6afc1b04-c9d6-4023-adbc-f8fbe33a3c73", - "rel": "reference" - }, - { - "href": "#87087451-2af5-43d4-88c1-d66ad850f614", - "rel": "reference" - }, - { - "href": "#4452efc0-e79e-47b8-aa30-b54f3ef61c2f", - "rel": "reference" - }, - { - "href": "#06ce9216-bd54-4054-a422-94f358b50a5d", - "rel": "reference" - }, - { - "href": "#678e3d6c-150b-4393-aec5-6e3481eb1e00", - "rel": "reference" - }, - { - "href": "#7ba1d91c-3934-4d5a-8532-b32f864ad34c", - "rel": "reference" - }, - { - "href": "#77faf0bc-c394-44ad-9154-bbac3b79c8ad", - "rel": "reference" - }, - { - "href": "#482e4c99-9dc4-41ad-bba8-0f3f0032c1f8", - "rel": "reference" - }, - { - "href": "#4895b4cd-34c5-4667-bf8a-27d443c12047", - "rel": "reference" - }, - { - "href": "#858705be-3c1f-48aa-a328-0ce398d95ef0", - "rel": "reference" - }, - { - "href": "#067223d8-1ec7-45c5-b21b-c848da6de8fb", - "rel": "reference" - }, - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "#e8e84963-14fc-4c3a-be05-b412a5d37cd2", - "rel": "reference" - }, - { - "href": "#15dc76ff-b17a-4eeb-8948-8ea8de3ccc2c", - "rel": "reference" - }, - { - "href": "#e24b06cc-9129-4998-a76a-65c3d7a576ba", - "rel": "reference" - }, - { - "href": "#4b38e961-1125-4a5b-aa35-1d6c02846dad", - "rel": "reference" - }, - { - "href": "#604774da-9e1d-48eb-9c62-4e959dc80737", - "rel": "reference" - }, - { - "href": "#98d415ca-7281-4064-9931-0c366637e324", - "rel": "reference" - }, - { - "href": "#795aff72-3e6c-4b6b-a80a-b14d84b7f544", - "rel": "reference" - }, - { - "href": "#3d575737-98cb-459d-b41c-d7e82b73ad78", - "rel": "reference" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#ps-7", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-11", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "#sa-16", - "rel": "related" - }, - { - "href": "#sa-17", - "rel": "related" - }, - { - "href": "#sa-21", - "rel": "related" - }, - { - "href": "#sr-3", - "rel": "related" - }, - { - "href": "#sr-5", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-4_smt", - "name": "statement", - "prose": "Include the following requirements, descriptions, and criteria, explicitly or by reference, using {{ insert: param, sa-04_odp.01 }} in the acquisition contract for the system, system component, or system service:", - "parts": [ - { - "id": "sa-4_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Security and privacy functional requirements;" - }, - { - "id": "sa-4_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Strength of mechanism requirements;" - }, - { - "id": "sa-4_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Security and privacy assurance requirements;" - }, - { - "id": "sa-4_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Controls needed to satisfy the security and privacy requirements." - }, - { - "id": "sa-4_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Security and privacy documentation requirements;" - }, - { - "id": "sa-4_smt.f", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "f." - } - ], - "prose": "Requirements for protecting security and privacy documentation;" - }, - { - "id": "sa-4_smt.g", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "g." - } - ], - "prose": "Description of the system development environment and environment in which the system is intended to operate;" - }, - { - "id": "sa-4_smt.h", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "h." - } - ], - "prose": "Allocation of responsibility or identification of parties responsible for information security, privacy, and supply chain risk management; and" - }, - { - "id": "sa-4_smt.i", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "i." - } - ], - "prose": "Acceptance criteria." - } - ] - }, - { - "id": "sa-4_gdn", - "name": "guidance", - "prose": "Security and privacy functional requirements are typically derived from the high-level security and privacy requirements described in [SA-2](#sa-2) . The derived requirements include security and privacy capabilities, functions, and mechanisms. Strength requirements associated with such capabilities, functions, and mechanisms include degree of correctness, completeness, resistance to tampering or bypass, and resistance to direct attack. Assurance requirements include development processes, procedures, and methodologies as well as the evidence from development and assessment activities that provide grounds for confidence that the required functionality is implemented and possesses the required strength of mechanism. [SP 800-160-1](#e3cc0520-a366-4fc9-abc2-5272db7e3564) describes the process of requirements engineering as part of the system development life cycle.\n\nControls can be viewed as descriptions of the safeguards and protection capabilities appropriate for achieving the particular security and privacy objectives of the organization and for reflecting the security and privacy requirements of stakeholders. Controls are selected and implemented in order to satisfy system requirements and include developer and organizational responsibilities. Controls can include technical, administrative, and physical aspects. In some cases, the selection and implementation of a control may necessitate additional specification by the organization in the form of derived requirements or instantiated control parameter values. The derived requirements and control parameter values may be necessary to provide the appropriate level of implementation detail for controls within the system development life cycle.\n\nSecurity and privacy documentation requirements address all stages of the system development life cycle. Documentation provides user and administrator guidance for the implementation and operation of controls. The level of detail required in such documentation is based on the security categorization or classification level of the system and the degree to which organizations depend on the capabilities, functions, or mechanisms to meet risk response expectations. Requirements can include mandated configuration settings that specify allowed functions, ports, protocols, and services. Acceptance criteria for systems, system components, and system services are defined in the same manner as the criteria for any organizational acquisition or procurement." - }, - { - "id": "sa-4_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SA-4 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "sa-4_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "The service provider must comply with Federal Acquisition Regulation (FAR) Subpart 7.103, and Section 889 of the John S. McCain National Defense Authorization Act (NDAA) for Fiscal Year 2019 (Pub. L. 115-232), and FAR Subpart 4.21, which implements Section 889 (as well as any added updates related to FISMA to address security concerns in the system acquisitions process)." - }, - { - "id": "sa-4_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "The use of Common Criteria (ISO/IEC 15408) evaluated products is strongly preferred.\n\nSee https://www.niap-ccevs.org/Product/index.cfm or https://www.commoncriteriaportal.org/products/." - } - ] - }, - { - "id": "sa-4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-4_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-4_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-04a.[01]", - "class": "sp800-53a" - } - ], - "prose": "security functional requirements, descriptions, and criteria are included explicitly or by reference using {{ insert: param, sa-04_odp.01 }} in the acquisition contract for the system, system component, or system service;", - "links": [ - { - "href": "#sa-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-04a.[02]", - "class": "sp800-53a" - } - ], - "prose": "privacy functional requirements, descriptions, and criteria are included explicitly or by reference using {{ insert: param, sa-04_odp.01 }} in the acquisition contract for the system, system component, or system service;", - "links": [ - { - "href": "#sa-4_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-04b.", - "class": "sp800-53a" - } - ], - "prose": "strength of mechanism requirements, descriptions, and criteria are included explicitly or by reference using {{ insert: param, sa-04_odp.01 }} in the acquisition contract for the system, system component, or system service;", - "links": [ - { - "href": "#sa-4_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-4_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04c.[01]", - "class": "sp800-53a" - } - ], - "prose": "security assurance requirements, descriptions, and criteria are included explicitly or by reference using {{ insert: param, sa-04_odp.01 }} in the acquisition contract for the system, system component, or system service;", - "links": [ - { - "href": "#sa-4_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04c.[02]", - "class": "sp800-53a" - } - ], - "prose": "privacy assurance requirements, descriptions, and criteria are included explicitly or by reference using {{ insert: param, sa-04_odp.01 }} in the acquisition contract for the system, system component, or system service;", - "links": [ - { - "href": "#sa-4_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-4_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04d.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-4_obj.d-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04d.[01]", - "class": "sp800-53a" - } - ], - "prose": "controls needed to satisfy the security requirements, descriptions, and criteria are included explicitly or by reference using {{ insert: param, sa-04_odp.01 }} in the acquisition contract for the system, system component, or system service;", - "links": [ - { - "href": "#sa-4_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4_obj.d-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04d.[02]", - "class": "sp800-53a" - } - ], - "prose": "controls needed to satisfy the privacy requirements, descriptions, and criteria are included explicitly or by reference using {{ insert: param, sa-04_odp.01 }} in the acquisition contract for the system, system component, or system service;", - "links": [ - { - "href": "#sa-4_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-4_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-04e.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-4_obj.e-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04e.[01]", - "class": "sp800-53a" - } - ], - "prose": "security documentation requirements, descriptions, and criteria are included explicitly or by reference using {{ insert: param, sa-04_odp.01 }} in the acquisition contract for the system, system component, or system service;", - "links": [ - { - "href": "#sa-4_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4_obj.e-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04e.[02]", - "class": "sp800-53a" - } - ], - "prose": "privacy documentation requirements, descriptions, and criteria are included explicitly or by reference using {{ insert: param, sa-04_odp.01 }} in the acquisition contract for the system, system component, or system service;", - "links": [ - { - "href": "#sa-4_smt.e", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-4_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4_obj.f", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-04f.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-4_obj.f-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04f.[01]", - "class": "sp800-53a" - } - ], - "prose": "requirements for protecting security documentation, descriptions, and criteria are included explicitly or by reference using {{ insert: param, sa-04_odp.01 }} in the acquisition contract for the system, system component, or system service;", - "links": [ - { - "href": "#sa-4_smt.f", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4_obj.f-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04f.[02]", - "class": "sp800-53a" - } - ], - "prose": "requirements for protecting privacy documentation, descriptions, and criteria are included explicitly or by reference using {{ insert: param, sa-04_odp.01 }} in the acquisition contract for the system, system component, or system service;", - "links": [ - { - "href": "#sa-4_smt.f", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-4_smt.f", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4_obj.g", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-04g.", - "class": "sp800-53a" - } - ], - "prose": "the description of the system development environment and environment in which the system is intended to operate, requirements, and criteria are included explicitly or by reference using {{ insert: param, sa-04_odp.01 }} in the acquisition contract for the system, system component, or system service;", - "links": [ - { - "href": "#sa-4_smt.g", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4_obj.h", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-04h.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-4_obj.h-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04h.[01]", - "class": "sp800-53a" - } - ], - "prose": "the allocation of responsibility or identification of parties responsible for information security requirements, descriptions, and criteria are included explicitly or by reference using {{ insert: param, sa-04_odp.01 }} in the acquisition contract for the system, system component, or system service;", - "links": [ - { - "href": "#sa-4_smt.h", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4_obj.h-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04h.[02]", - "class": "sp800-53a" - } - ], - "prose": "the allocation of responsibility or identification of parties responsible for privacy requirements, descriptions, and criteria are included explicitly or by reference using {{ insert: param, sa-04_odp.01 }};", - "links": [ - { - "href": "#sa-4_smt.h", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4_obj.h-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04h.[03]", - "class": "sp800-53a" - } - ], - "prose": "the allocation of responsibility or identification of parties responsible for supply chain risk management requirements, descriptions, and criteria are included explicitly or by reference using {{ insert: param, sa-04_odp.01 }};", - "links": [ - { - "href": "#sa-4_smt.h", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-4_smt.h", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4_obj.i", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-04i.", - "class": "sp800-53a" - } - ], - "prose": "acceptance criteria requirements and descriptions are included explicitly or by reference using {{ insert: param, sa-04_odp.01 }} in the acquisition contract for the system, system component, or system service.", - "links": [ - { - "href": "#sa-4_smt.i", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-04-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nsystem and services acquisition procedures\n\nprocedures addressing the integration of information security and privacy and supply chain risk management into the acquisition process\n\nconfiguration management plan\n\nacquisition contracts for the system, system component, or system service\n\nsystem design documentation\n\nsystem security plan\n\nsupply chain risk management plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-04-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators\n\norganizational personnel with supply chain risk management responsibilities" - } - ] - }, - { - "id": "sa-4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SA-04-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for determining system security and privacy functional, strength, and assurance requirements\n\norganizational processes for developing acquisition contracts\n\nmechanisms supporting and/or implementing acquisitions and the inclusion of security and privacy requirements in contracts" - } - ] - } - ], - "controls": [ - { - "id": "sa-4.1", - "class": "SP800-53-enhancement", - "title": "Functional Properties of Controls", - "props": [ - { - "name": "label", - "value": "SA-04(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-4(1)" - }, - { - "name": "label", - "value": "SA-04(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-04.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#sa-4", - "rel": "required" - } - ], - "parts": [ - { - "id": "sa-4.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Require the developer of the system, system component, or system service to provide a description of the functional properties of the controls to be implemented." - }, - { - "id": "sa-4.1_gdn", - "name": "guidance", - "prose": "Functional properties of security and privacy controls describe the functionality (i.e., security or privacy capability, functions, or mechanisms) visible at the interfaces of the controls and specifically exclude functionality and data structures internal to the operation of the controls." - }, - { - "id": "sa-4.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-04(01)", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to provide a description of the functional properties of the controls to be implemented.", - "links": [ - { - "href": "#sa-4.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-04(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nsystem and services acquisition procedures\n\nprocedures addressing the integration of security and privacy requirements, descriptions, and criteria into the acquisition process\n\nsolicitation documents\n\nacquisition documentation\n\nacquisition contracts for the system, system component, or system services\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-4.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-04(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "sa-4.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SA-04(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for determining system security functional requirements\n\norganizational processes for developing acquisition contracts\n\nmechanisms supporting and/or implementing acquisitions and the inclusion of security and privacy requirements in contracts" - } - ] - } - ] - }, - { - "id": "sa-4.2", - "class": "SP800-53-enhancement", - "title": "Design and Implementation Information for Controls", - "params": [ - { - "id": "sa-04.02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sa-4.2_prm_1" - }, - { - "name": "label", - "value": "SA-04(02)_ODP[01]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "at a minimum to include security-relevant external system interfaces; high-level design; low-level design; source code or network and data flow diagram;\n\norganization-defined design/implementation information" - } - ] - }, - { - "id": "sa-04.02_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sa-4.2_prm_2" - }, - { - "name": "label", - "value": "SA-04(02)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "design and implementation information", - "guidelines": [ - { - "prose": "design and implementation information is defined (if selected);" - } - ] - }, - { - "id": "sa-04.02_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "sa-4.2_prm_3" - }, - { - "name": "label", - "value": "SA-04(02)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "level of detail", - "guidelines": [ - { - "prose": "level of detail is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SA-04(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-4(2)" - }, - { - "name": "label", - "value": "SA-04(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-04.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#sa-4", - "rel": "required" - } - ], - "parts": [ - { - "id": "sa-4.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Require the developer of the system, system component, or system service to provide design and implementation information for the controls that includes: {{ insert: param, sa-04.02_odp.01 }} at {{ insert: param, sa-04.02_odp.03 }}." - }, - { - "id": "sa-4.2_gdn", - "name": "guidance", - "prose": "Organizations may require different levels of detail in the documentation for the design and implementation of controls in organizational systems, system components, or system services based on mission and business requirements, requirements for resiliency and trustworthiness, and requirements for analysis and testing. Systems can be partitioned into multiple subsystems. Each subsystem within the system can contain one or more modules. The high-level design for the system is expressed in terms of subsystems and the interfaces between subsystems providing security-relevant functionality. The low-level design for the system is expressed in terms of modules and the interfaces between modules providing security-relevant functionality. Design and implementation documentation can include manufacturer, version, serial number, verification hash signature, software libraries used, date of purchase or download, and the vendor or download source. Source code and hardware schematics are referred to as the implementation representation of the system." - }, - { - "id": "sa-4.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-04(02)", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to provide design and implementation information for the controls that includes using {{ insert: param, sa-04.02_odp.01 }} at {{ insert: param, sa-04.02_odp.03 }}.", - "links": [ - { - "href": "#sa-4.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-04(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nsystem and services acquisition procedures\n\nprocedures addressing the integration of security requirements, descriptions, and criteria into the acquisition process\n\nsolicitation documents\n\nacquisition documentation\n\nacquisition contracts for the system, system components, or system services\n\ndesign and implementation information for controls employed in the system, system component, or system service\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-4.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-04(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with the responsibility to determine system security requirements\n\nsystem developers or service provider\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "sa-4.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SA-04(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for determining the level of detail for system design and controls\n\norganizational processes for developing acquisition contracts\n\nmechanisms supporting and/or implementing the development of system design details" - } - ] - } - ] - }, - { - "id": "sa-4.5", - "class": "SP800-53-enhancement", - "title": "System, Component, and Service Configurations", - "params": [ - { - "id": "sa-04.05_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sa-4.5_prm_1" - }, - { - "name": "label", - "value": "SA-04(05)_ODP", - "class": "sp800-53a" - } - ], - "label": "security configurations", - "constraints": [ - { - "description": "The service provider shall use the DoD STIGs to establish configuration settings; Center for Internet Security up to Level 2 (CIS Level 2) guidelines shall be used if STIGs are not available; Custom baselines shall be used if CIS is not available." - } - ], - "guidelines": [ - { - "prose": "security configurations for the system, component, or service are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SA-04(05)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-4(5)" - }, - { - "name": "label", - "value": "SA-04(05)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-04.05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#sa-4", - "rel": "required" - } - ], - "parts": [ - { - "id": "sa-4.5_smt", - "name": "statement", - "prose": "Require the developer of the system, system component, or system service to:", - "parts": [ - { - "id": "sa-4.5_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Deliver the system, component, or service with {{ insert: param, sa-04.05_odp }} implemented; and" - }, - { - "id": "sa-4.5_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Use the configurations as the default for any subsequent system, component, or service reinstallation or upgrade." - } - ] - }, - { - "id": "sa-4.5_gdn", - "name": "guidance", - "prose": "Examples of security configurations include the U.S. Government Configuration Baseline (USGCB), Security Technical Implementation Guides (STIGs), and any limitations on functions, ports, protocols, and services. Security characteristics can include requiring that default passwords have been changed." - }, - { - "id": "sa-4.5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04(05)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-4.5_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-04(05)(a)", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to deliver the system, component, or service with {{ insert: param, sa-04.05_odp }} implemented;", - "links": [ - { - "href": "#sa-4.5_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4.5_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-04(05)(b)", - "class": "sp800-53a" - } - ], - "prose": "the configurations are used as the default for any subsequent system, component, or service reinstallation or upgrade.", - "links": [ - { - "href": "#sa-4.5_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-4.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4.5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-04(05)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nprocedures addressing the integration of security requirements, descriptions, and criteria into the acquisition process\n\nsolicitation documents\n\nacquisition documentation\n\nacquisition contracts for the system, system component, or system service\n\nsecurity configurations to be implemented by the developer of the system, system component, or system service\n\nservice level agreements\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-4.5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-04(05)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with the responsibility to determine system security requirements\n\nsystem developers or service provider\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "sa-4.5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SA-04(05)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms used to verify that the configuration of the system, component, or service is delivered as specified" - } - ] - } - ] - }, - { - "id": "sa-4.9", - "class": "SP800-53-enhancement", - "title": "Functions, Ports, Protocols, and Services in Use", - "props": [ - { - "name": "label", - "value": "SA-04(09)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-4(9)" - }, - { - "name": "label", - "value": "SA-04(09)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-04.09" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#sa-4", - "rel": "required" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-4.9_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Require the developer of the system, system component, or system service to identify the functions, ports, protocols, and services intended for organizational use." - }, - { - "id": "sa-4.9_gdn", - "name": "guidance", - "prose": "The identification of functions, ports, protocols, and services early in the system development life cycle (e.g., during the initial requirements definition and design stages) allows organizations to influence the design of the system, system component, or system service. This early involvement in the system development life cycle helps organizations avoid or minimize the use of functions, ports, protocols, or services that pose unnecessarily high risks and understand the trade-offs involved in blocking specific ports, protocols, or services or requiring system service providers to do so. Early identification of functions, ports, protocols, and services avoids costly retrofitting of controls after the system, component, or system service has been implemented. [SA-9](#sa-9) describes the requirements for external system services. Organizations identify which functions, ports, protocols, and services are provided from external sources." - }, - { - "id": "sa-4.9_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-04(09)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-4.9_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04(09)[01]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to identify the functions intended for organizational use;", - "links": [ - { - "href": "#sa-4.9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4.9_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04(09)[02]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to identify the ports intended for organizational use;", - "links": [ - { - "href": "#sa-4.9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4.9_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04(09)[03]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to identify the protocols intended for organizational use;", - "links": [ - { - "href": "#sa-4.9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4.9_obj-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-04(09)[04]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to identify the services intended for organizational use.", - "links": [ - { - "href": "#sa-4.9_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-4.9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4.9_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-04(09)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nprocedures addressing the integration of security requirements, descriptions, and criteria into the acquisition process\n\nsystem design documentation\n\nsystem documentation, including functions, ports, protocols, and services intended for organizational use\n\nacquisition contracts for systems or services\n\nacquisition documentation\n\nsolicitation documentation\n\nservice level agreements\n\norganizational security requirements, descriptions, and criteria for developers of systems, system components, and system services\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-4.9_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-04(09)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with the responsibility for determining system security requirements\n\nsystem/network administrators\n\norganizational personnel operating, using, and/or maintaining the system\n\nsystem developers\n\norganizational personnel with information security responsibilities" - } - ] - } - ] - }, - { - "id": "sa-4.10", - "class": "SP800-53-enhancement", - "title": "Use of Approved PIV Products", - "props": [ - { - "name": "label", - "value": "SA-04(10)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-4(10)" - }, - { - "name": "label", - "value": "SA-04(10)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-04.10" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#sa-4", - "rel": "required" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-4.10_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Employ only information technology products on the FIPS 201-approved products list for Personal Identity Verification (PIV) capability implemented within organizational systems." - }, - { - "id": "sa-4.10_gdn", - "name": "guidance", - "prose": "Products on the FIPS 201-approved products list meet NIST requirements for Personal Identity Verification (PIV) of Federal Employees and Contractors. PIV cards are used for multi-factor authentication in systems and organizations." - }, - { - "id": "sa-4.10_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-04(10)", - "class": "sp800-53a" - } - ], - "prose": "only information technology products on the FIPS 201-approved products list for the Personal Identity Verification (PIV) capability implemented within organizational systems are employed.", - "links": [ - { - "href": "#sa-4.10_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-4.10_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-04(10)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Supply chain risk management plan\n\nsystem and services acquisition policy\n\nprocedures addressing the integration of security requirements, descriptions, and criteria into the acquisition process\n\nsolicitation documentation\n\nacquisition documentation\n\nacquisition contracts for the system, system component, or system service\n\nservice level agreements\n\nFIPS 201 approved products list\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-4.10_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-04(10)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with the responsibility for determining system security requirements\n\norganizational personnel with the responsibility for ensuring that only FIPS 201- approved products are implemented\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "sa-4.10_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SA-04(10)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for selecting and employing FIPS 201-approved products" - } - ] - } - ] - } - ] - }, - { - "id": "sa-5", - "class": "SP800-53", - "title": "System Documentation", - "params": [ - { - "id": "sa-05_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sa-5_prm_1" - }, - { - "name": "label", - "value": "SA-05_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "actions", - "guidelines": [ - { - "prose": "actions to take when system, system component, or system service documentation is either unavailable or nonexistent are defined;" - } - ] - }, - { - "id": "sa-05_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sa-5_prm_2" - }, - { - "name": "label", - "value": "SA-05_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "constraints": [ - { - "description": "at a minimum, the ISSO (or similar role within the organization)" - } - ], - "guidelines": [ - { - "prose": "personnel or roles to distribute system documentation to is/are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SA-05", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-5" - }, - { - "name": "label", - "value": "SA-05", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "#pl-8", - "rel": "related" - }, - { - "href": "#ps-2", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - }, - { - "href": "#sa-11", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "#sa-16", - "rel": "related" - }, - { - "href": "#sa-17", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - }, - { - "href": "#sr-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-5_smt", - "name": "statement", - "parts": [ - { - "id": "sa-5_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Obtain or develop administrator documentation for the system, system component, or system service that describes:", - "parts": [ - { - "id": "sa-5_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Secure configuration, installation, and operation of the system, component, or service;" - }, - { - "id": "sa-5_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Effective use and maintenance of security and privacy functions and mechanisms; and" - }, - { - "id": "sa-5_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Known vulnerabilities regarding configuration and use of administrative or privileged functions;" - } - ] - }, - { - "id": "sa-5_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Obtain or develop user documentation for the system, system component, or system service that describes:", - "parts": [ - { - "id": "sa-5_smt.b.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "User-accessible security and privacy functions and mechanisms and how to effectively use those functions and mechanisms;" - }, - { - "id": "sa-5_smt.b.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Methods for user interaction, which enables individuals to use the system, component, or service in a more secure manner and protect individual privacy; and" - }, - { - "id": "sa-5_smt.b.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "User responsibilities in maintaining the security of the system, component, or service and privacy of individuals;" - } - ] - }, - { - "id": "sa-5_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Document attempts to obtain system, system component, or system service documentation when such documentation is either unavailable or nonexistent and take {{ insert: param, sa-05_odp.01 }} in response; and" - }, - { - "id": "sa-5_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Distribute documentation to {{ insert: param, sa-05_odp.02 }}." - } - ] - }, - { - "id": "sa-5_gdn", - "name": "guidance", - "prose": "System documentation helps personnel understand the implementation and operation of controls. Organizations consider establishing specific measures to determine the quality and completeness of the content provided. System documentation may be used to support the management of supply chain risk, incident response, and other functions. Personnel or roles that require documentation include system owners, system security officers, and system administrators. Attempts to obtain documentation include contacting manufacturers or suppliers and conducting web-based searches. The inability to obtain documentation may occur due to the age of the system or component or the lack of support from developers and contractors. When documentation cannot be obtained, organizations may need to recreate the documentation if it is essential to the implementation or operation of the controls. The protection provided for the documentation is commensurate with the security category or classification of the system. Documentation that addresses system vulnerabilities may require an increased level of protection. Secure operation of the system includes initially starting the system and resuming secure system operation after a lapse in system operation." - }, - { - "id": "sa-5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-05", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-5_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-05a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-5_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-05a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-5_obj.a.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-05a.01[01]", - "class": "sp800-53a" - } - ], - "prose": "administrator documentation for the system, system component, or system service that describes the secure configuration of the system, component, or service is obtained or developed;", - "links": [ - { - "href": "#sa-5_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_obj.a.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-05a.01[02]", - "class": "sp800-53a" - } - ], - "prose": "administrator documentation for the system, system component, or system service that describes the secure installation of the system, component, or service is obtained or developed;", - "links": [ - { - "href": "#sa-5_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_obj.a.1-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-05a.01[03]", - "class": "sp800-53a" - } - ], - "prose": "administrator documentation for the system, system component, or system service that describes the secure operation of the system, component, or service is obtained or developed;", - "links": [ - { - "href": "#sa-5_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-5_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_obj.a.2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-05a.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-5_obj.a.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-05a.02[01]", - "class": "sp800-53a" - } - ], - "prose": "administrator documentation for the system, system component, or system service that describes the effective use of security functions and mechanisms is obtained or developed;", - "links": [ - { - "href": "#sa-5_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_obj.a.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-05a.02[02]", - "class": "sp800-53a" - } - ], - "prose": "administrator documentation for the system, system component, or system service that describes the effective maintenance of security functions and mechanisms is obtained or developed;", - "links": [ - { - "href": "#sa-5_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_obj.a.2-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-05a.02[03]", - "class": "sp800-53a" - } - ], - "prose": "administrator documentation for the system, system component, or system service that describes the effective use of privacy functions and mechanisms is obtained or developed;", - "links": [ - { - "href": "#sa-5_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_obj.a.2-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-05a.02[04]", - "class": "sp800-53a" - } - ], - "prose": "administrator documentation for the system, system component, or system service that describes the effective maintenance of privacy functions and mechanisms is obtained or developed;", - "links": [ - { - "href": "#sa-5_smt.a.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-5_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_obj.a.3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-05a.03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-5_obj.a.3-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-05a.03[01]", - "class": "sp800-53a" - } - ], - "prose": "administrator documentation for the system, system component, or system service that describes known vulnerabilities regarding the configuration of administrative or privileged functions is obtained or developed;", - "links": [ - { - "href": "#sa-5_smt.a.3", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_obj.a.3-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-05a.03[02]", - "class": "sp800-53a" - } - ], - "prose": "administrator documentation for the system, system component, or system service that describes known vulnerabilities regarding the use of administrative or privileged functions is obtained or developed;", - "links": [ - { - "href": "#sa-5_smt.a.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-5_smt.a.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-5_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-05b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-5_obj.b.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-05b.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-5_obj.b.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-05b.01[01]", - "class": "sp800-53a" - } - ], - "prose": "user documentation for the system, system component, or system service that describes user-accessible security functions and mechanisms is obtained or developed;", - "links": [ - { - "href": "#sa-5_smt.b.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_obj.b.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-05b.01[02]", - "class": "sp800-53a" - } - ], - "prose": "user documentation for the system, system component, or system service that describes how to effectively use those (user-accessible security) functions and mechanisms is obtained or developed;", - "links": [ - { - "href": "#sa-5_smt.b.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_obj.b.1-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-05b.01[03]", - "class": "sp800-53a" - } - ], - "prose": "user documentation for the system, system component, or system service that describes user-accessible privacy functions and mechanisms is obtained or developed;", - "links": [ - { - "href": "#sa-5_smt.b.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_obj.b.1-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-05b.01[04]", - "class": "sp800-53a" - } - ], - "prose": "user documentation for the system, system component, or system service that describes how to effectively use those (user-accessible privacy) functions and mechanisms is obtained or developed;", - "links": [ - { - "href": "#sa-5_smt.b.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-5_smt.b.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_obj.b.2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-05b.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-5_obj.b.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-05b.02[01]", - "class": "sp800-53a" - } - ], - "prose": "user documentation for the system, system component, or system service that describes methods for user interaction, which enable individuals to use the system, component, or service in a more secure manner is obtained or developed;", - "links": [ - { - "href": "#sa-5_smt.b.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_obj.b.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-05b.02[02]", - "class": "sp800-53a" - } - ], - "prose": "user documentation for the system, system component, or system service that describes methods for user interaction, which enable individuals to use the system, component, or service to protect individual privacy is obtained or developed;", - "links": [ - { - "href": "#sa-5_smt.b.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-5_smt.b.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_obj.b.3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-05b.03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-5_obj.b.3-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-05b.03[01]", - "class": "sp800-53a" - } - ], - "prose": "user documentation for the system, system component, or system service that describes user responsibilities for maintaining the security of the system, component, or service is obtained or developed;", - "links": [ - { - "href": "#sa-5_smt.b.3", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_obj.b.3-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-05b.03[02]", - "class": "sp800-53a" - } - ], - "prose": "user documentation for the system, system component, or system service that describes user responsibilities for maintaining the privacy of individuals is obtained or developed;", - "links": [ - { - "href": "#sa-5_smt.b.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-5_smt.b.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-5_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-05c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-5_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-05c.[01]", - "class": "sp800-53a" - } - ], - "prose": "attempts to obtain system, system component, or system service documentation when such documentation is either unavailable or nonexistent is documented;", - "links": [ - { - "href": "#sa-5_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-05c.[02]", - "class": "sp800-53a" - } - ], - "prose": "after attempts to obtain system, system component, or system service documentation when such documentation is either unavailable or nonexistent, {{ insert: param, sa-05_odp.01 }} are taken in response;", - "links": [ - { - "href": "#sa-5_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-5_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-05d.", - "class": "sp800-53a" - } - ], - "prose": "documentation is distributed to {{ insert: param, sa-05_odp.02 }}.", - "links": [ - { - "href": "#sa-5_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-05-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nsystem and services acquisition procedures\n\nprocedures addressing system documentation\n\nsystem documentation, including administrator and user guides\n\nsystem design documentation\n\nrecords documenting attempts to obtain unavailable or nonexistent system documentation\n\nlist of actions to be taken in response to documented attempts to obtain system, system component, or system service documentation\n\nrisk management strategy documentation\n\nsystem security plan\n\nprivacy plan\n\nprivacy impact assessment\n\nprivacy risk assessment documentation\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-05-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem administrators\n\norganizational personnel responsible for operating, using, and/or maintaining the system\n\nsystem developers" - } - ] - }, - { - "id": "sa-5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SA-05-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for obtaining, protecting, and distributing system administrator and user documentation" - } - ] - } - ] - }, - { - "id": "sa-8", - "class": "SP800-53", - "title": "Security and Privacy Engineering Principles", - "params": [ - { - "id": "sa-8_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "sa-08_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "sa-08_odp.02" - } - ], - "label": "organization-defined systems security and privacy engineering principles" - }, - { - "id": "sa-08_odp.01", - "props": [ - { - "name": "label", - "value": "SA-08_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "systems security engineering principles", - "guidelines": [ - { - "prose": "systems security engineering principles are defined;" - } - ] - }, - { - "id": "sa-08_odp.02", - "props": [ - { - "name": "label", - "value": "SA-08_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "privacy engineering principles", - "guidelines": [ - { - "prose": "privacy engineering principles are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SA-08", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-8" - }, - { - "name": "label", - "value": "SA-08", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#18e71fec-c6fd-475a-925a-5d8495cf8455", - "rel": "reference" - }, - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#628d22a1-6a11-4784-bc59-5cd9497b5445", - "rel": "reference" - }, - { - "href": "#599fb53d-5041-444e-a7fe-640d6d30ad05", - "rel": "reference" - }, - { - "href": "#482e4c99-9dc4-41ad-bba8-0f3f0032c1f8", - "rel": "reference" - }, - { - "href": "#a21aef46-7330-48a0-b2e1-c5bb8b2dd11d", - "rel": "reference" - }, - { - "href": "#e72fde0b-6fc2-497e-a9db-d8fce5a11b8a", - "rel": "reference" - }, - { - "href": "#9be5d661-421f-41ad-854e-86f98b811891", - "rel": "reference" - }, - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "#98d415ca-7281-4064-9931-0c366637e324", - "rel": "reference" - }, - { - "href": "#pl-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-7", - "rel": "related" - }, - { - "href": "#ra-2", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#ra-9", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "#sa-17", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sa-20", - "rel": "related" - }, - { - "href": "#sc-2", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-32", - "rel": "related" - }, - { - "href": "#sc-39", - "rel": "related" - }, - { - "href": "#sr-2", - "rel": "related" - }, - { - "href": "#sr-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sr-4", - "rel": "related" - }, - { - "href": "#sr-5", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-8_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Apply the following systems security and privacy engineering principles in the specification, design, development, implementation, and modification of the system and system components: {{ insert: param, sa-8_prm_1 }}." - }, - { - "id": "sa-8_gdn", - "name": "guidance", - "prose": "Systems security and privacy engineering principles are closely related to and implemented throughout the system development life cycle (see [SA-3](#sa-3) ). Organizations can apply systems security and privacy engineering principles to new systems under development or to systems undergoing upgrades. For existing systems, organizations apply systems security and privacy engineering principles to system upgrades and modifications to the extent feasible, given the current state of hardware, software, and firmware components within those systems.\n\nThe application of systems security and privacy engineering principles helps organizations develop trustworthy, secure, and resilient systems and reduces the susceptibility to disruptions, hazards, threats, and the creation of privacy problems for individuals. Examples of system security engineering principles include: developing layered protections; establishing security and privacy policies, architecture, and controls as the foundation for design and development; incorporating security and privacy requirements into the system development life cycle; delineating physical and logical security boundaries; ensuring that developers are trained on how to build secure software; tailoring controls to meet organizational needs; and performing threat modeling to identify use cases, threat agents, attack vectors and patterns, design patterns, and compensating controls needed to mitigate risk.\n\nOrganizations that apply systems security and privacy engineering concepts and principles can facilitate the development of trustworthy, secure systems, system components, and system services; reduce risk to acceptable levels; and make informed risk management decisions. System security engineering principles can also be used to protect against certain supply chain risks, including incorporating tamper-resistant hardware into a design." - }, - { - "id": "sa-8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-08", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-8_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-08[01]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sa-08_odp.01 }} are applied in the specification of the system and system components;", - "links": [ - { - "href": "#sa-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-8_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-08[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sa-08_odp.01 }} are applied in the design of the system and system components;", - "links": [ - { - "href": "#sa-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-8_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-08[03]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sa-08_odp.01 }} are applied in the development of the system and system components;", - "links": [ - { - "href": "#sa-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-8_obj-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-08[04]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sa-08_odp.01 }} are applied in the implementation of the system and system components;", - "links": [ - { - "href": "#sa-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-8_obj-5", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-08[05]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sa-08_odp.01 }} are applied in the modification of the system and system components;", - "links": [ - { - "href": "#sa-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-8_obj-6", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-08[06]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sa-08_odp.02 }} are applied in the specification of the system and system components;", - "links": [ - { - "href": "#sa-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-8_obj-7", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-08[07]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sa-08_odp.02 }} are applied in the design of the system and system components;", - "links": [ - { - "href": "#sa-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-8_obj-8", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-08[08]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sa-08_odp.02 }} are applied in the development of the system and system components;", - "links": [ - { - "href": "#sa-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-8_obj-9", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-08[09]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sa-08_odp.02 }} are applied in the implementation of the system and system components;", - "links": [ - { - "href": "#sa-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-8_obj-10", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-08[10]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sa-08_odp.02 }} are applied in the modification of the system and system components.", - "links": [ - { - "href": "#sa-8_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-08-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nsystem and services acquisition procedures\n\nassessment and authorization procedures\n\nprocedures addressing security and privacy engineering principles used in the specification, design, development, implementation, and modification of the system\n\nsystem design documentation\n\nsecurity and privacy requirements and specifications for the system\n\nsystem security plan\n\nprivacy plan\n\nprivacy impact assessment\n\nprivacy risk assessment documentation\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-08-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with acquisition/contracting responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\norganizational personnel with system specification, design, development, implementation, and modification responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "sa-8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SA-08-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for applying security and privacy engineering principles in system specification, design, development, implementation, and modification\n\nmechanisms supporting the application of security and privacy engineering principles in system specification, design, development, implementation, and modification" - } - ] - } - ] - }, - { - "id": "sa-9", - "class": "SP800-53", - "title": "External System Services", - "params": [ - { - "id": "sa-09_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sa-9_prm_1" - }, - { - "name": "label", - "value": "SA-09_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "controls", - "constraints": [ - { - "description": "Appropriate FedRAMP Security Controls Baseline (s) if Federal information is processed or stored within the external system" - } - ], - "guidelines": [ - { - "prose": "controls to be employed by external system service providers are defined;" - } - ] - }, - { - "id": "sa-09_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sa-9_prm_2" - }, - { - "name": "label", - "value": "SA-09_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "processes, methods, and techniques", - "constraints": [ - { - "description": "Federal/FedRAMP Continuous Monitoring requirements must be met for external systems where Federal information is processed or stored" - } - ], - "guidelines": [ - { - "prose": "processes, methods, and techniques employed to monitor control compliance by external service providers are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SA-09", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-9" - }, - { - "name": "label", - "value": "SA-09", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-09" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#77faf0bc-c394-44ad-9154-bbac3b79c8ad", - "rel": "reference" - }, - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "#e8e84963-14fc-4c3a-be05-b412a5d37cd2", - "rel": "reference" - }, - { - "href": "#7dbd6d9f-29d6-4d1d-9766-f2d77ff3c849", - "rel": "reference" - }, - { - "href": "#ac-20", - "rel": "related" - }, - { - "href": "#ca-3", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-7", - "rel": "related" - }, - { - "href": "#pl-10", - "rel": "related" - }, - { - "href": "#pl-11", - "rel": "related" - }, - { - "href": "#ps-7", - "rel": "related" - }, - { - "href": "#sa-2", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sr-3", - "rel": "related" - }, - { - "href": "#sr-5", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-9_smt", - "name": "statement", - "parts": [ - { - "id": "sa-9_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Require that providers of external system services comply with organizational security and privacy requirements and employ the following controls: {{ insert: param, sa-09_odp.01 }};" - }, - { - "id": "sa-9_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Define and document organizational oversight and user roles and responsibilities with regard to external system services; and" - }, - { - "id": "sa-9_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Employ the following processes, methods, and techniques to monitor control compliance by external service providers on an ongoing basis: {{ insert: param, sa-09_odp.02 }}." - } - ] - }, - { - "id": "sa-9_gdn", - "name": "guidance", - "prose": "External system services are provided by an external provider, and the organization has no direct control over the implementation of the required controls or the assessment of control effectiveness. Organizations establish relationships with external service providers in a variety of ways, including through business partnerships, contracts, interagency agreements, lines of business arrangements, licensing agreements, joint ventures, and supply chain exchanges. The responsibility for managing risks from the use of external system services remains with authorizing officials. For services external to organizations, a chain of trust requires that organizations establish and retain a certain level of confidence that each provider in the consumer-provider relationship provides adequate protection for the services rendered. The extent and nature of this chain of trust vary based on relationships between organizations and the external providers. Organizations document the basis for the trust relationships so that the relationships can be monitored. External system services documentation includes government, service providers, end user security roles and responsibilities, and service-level agreements. Service-level agreements define the expectations of performance for implemented controls, describe measurable outcomes, and identify remedies and response requirements for identified instances of noncompliance." - }, - { - "id": "sa-9_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-09", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-9_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-09a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-9_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-09a.[01]", - "class": "sp800-53a" - } - ], - "prose": "providers of external system services comply with organizational security requirements;", - "links": [ - { - "href": "#sa-9_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-9_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-09a.[02]", - "class": "sp800-53a" - } - ], - "prose": "providers of external system services comply with organizational privacy requirements;", - "links": [ - { - "href": "#sa-9_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-9_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-09a.[03]", - "class": "sp800-53a" - } - ], - "prose": "providers of external system services employ {{ insert: param, sa-09_odp.01 }};", - "links": [ - { - "href": "#sa-9_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-9_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-9_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-09b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-9_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-09b.[01]", - "class": "sp800-53a" - } - ], - "prose": "organizational oversight with regard to external system services are defined and documented;", - "links": [ - { - "href": "#sa-9_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-9_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-09b.[02]", - "class": "sp800-53a" - } - ], - "prose": "user roles and responsibilities with regard to external system services are defined and documented;", - "links": [ - { - "href": "#sa-9_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-9_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-9_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-09c.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sa-09_odp.02 }} are employed to monitor control compliance by external service providers on an ongoing basis.", - "links": [ - { - "href": "#sa-9_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-9_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-09-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nsystem and services acquisition procedures\n\nprocedures addressing methods and techniques for monitoring control compliance by external service providers of system services\n\nacquisition documentation\n\ncontracts\n\nservice level agreements\n\ninteragency agreements\n\nlicensing agreements\n\nlist of organizational security and privacy requirements for external provider services\n\ncontrol assessment results or reports from external providers of system services\n\nsystem security plan\n\nprivacy plan\n\nsupply chain risk management plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-9_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-09-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with acquisition responsibilities\n\nexternal providers of system services\n\norganizational personnel with information security and privacy responsibilities\n\norganizational personnel with supply chain risk management responsibilities" - } - ] - }, - { - "id": "sa-9_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SA-09-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for monitoring security and privacy control compliance by external service providers on an ongoing basis\n\nmechanisms for monitoring security and privacy control compliance by external service providers on an ongoing basis" - } - ] - } - ], - "controls": [ - { - "id": "sa-9.1", - "class": "SP800-53-enhancement", - "title": "Risk Assessments and Organizational Approvals", - "params": [ - { - "id": "sa-09.01_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sa-9.1_prm_1" - }, - { - "name": "label", - "value": "SA-09(01)_ODP", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles that approve the acquisition or outsourcing of dedicated information security services is/are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SA-09(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-9(1)" - }, - { - "name": "label", - "value": "SA-09(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-09.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#sa-9", - "rel": "required" - }, - { - "href": "#ca-6", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ra-8", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-9.1_smt", - "name": "statement", - "parts": [ - { - "id": "sa-9.1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Conduct an organizational assessment of risk prior to the acquisition or outsourcing of information security services; and" - }, - { - "id": "sa-9.1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Verify that the acquisition or outsourcing of dedicated information security services is approved by {{ insert: param, sa-09.01_odp }}." - } - ] - }, - { - "id": "sa-9.1_gdn", - "name": "guidance", - "prose": "Information security services include the operation of security devices, such as firewalls or key management services as well as incident monitoring, analysis, and response. Risks assessed can include system, mission or business, security, privacy, or supply chain risks." - }, - { - "id": "sa-9.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-09(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-9.1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-09(01)(a)", - "class": "sp800-53a" - } - ], - "prose": "an organizational assessment of risk is conducted prior to the acquisition or outsourcing of information security services;", - "links": [ - { - "href": "#sa-9.1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-9.1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-09(01)(b)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sa-09.01_odp }} approve the acquisition or outsourcing of dedicated information security services.", - "links": [ - { - "href": "#sa-9.1_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-9.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-9.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-09(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nsupply chain risk management policy and procedures\n\nprocedures addressing external system services\n\nacquisition documentation\n\nacquisition contracts for the system, system component, or system service\n\nrisk assessment reports\n\napproval records for the acquisition or outsourcing of dedicated security services\n\nsystem security plan\n\nsupply chain risk management plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-9.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-09(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and service acquisition responsibilities\n\norganizational personnel with system security responsibilities\n\nexternal providers of system services\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain risk management responsibilities" - } - ] - }, - { - "id": "sa-9.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SA-09(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for conducting a risk assessment prior to acquiring or outsourcing dedicated security services\n\norganizational processes for approving the outsourcing of dedicated security services\n\nmechanisms supporting and/or implementing risk assessment\n\nmechanisms supporting and/or implementing approval processes" - } - ] - } - ] - }, - { - "id": "sa-9.2", - "class": "SP800-53-enhancement", - "title": "Identification of Functions, Ports, Protocols, and Services", - "params": [ - { - "id": "sa-09.02_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sa-9.2_prm_1" - }, - { - "name": "label", - "value": "SA-09(02)_ODP", - "class": "sp800-53a" - } - ], - "label": "external system services", - "constraints": [ - { - "description": "all external systems where Federal information is processed or stored" - } - ], - "guidelines": [ - { - "prose": "external system services that require the identification of functions, ports, protocols, and other services are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SA-09(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-9(2)" - }, - { - "name": "label", - "value": "SA-09(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-09.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#sa-9", - "rel": "required" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-9.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Require providers of the following external system services to identify the functions, ports, protocols, and other services required for the use of such services: {{ insert: param, sa-09.02_odp }}." - }, - { - "id": "sa-9.2_gdn", - "name": "guidance", - "prose": "Information from external service providers regarding the specific functions, ports, protocols, and services used in the provision of such services can be useful when the need arises to understand the trade-offs involved in restricting certain functions and services or blocking certain ports and protocols." - }, - { - "id": "sa-9.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-09(02)", - "class": "sp800-53a" - } - ], - "prose": "providers of {{ insert: param, sa-09.02_odp }} are required to identify the functions, ports, protocols, and other services required for the use of such services.", - "links": [ - { - "href": "#sa-9.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-9.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-09(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nsupply chain risk management policy and procedures\n\nprocedures addressing external system services\n\nacquisition contracts for the system, system component, or system service\n\nacquisition documentation\n\nsolicitation documentation\n\nservice level agreements\n\norganizational security requirements and security specifications for external service providers\n\nlist of required functions, ports, protocols, and other services\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-9.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-09(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and service acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nexternal providers of system services" - } - ] - } - ] - }, - { - "id": "sa-9.5", - "class": "SP800-53-enhancement", - "title": "Processing, Storage, and Service Location", - "params": [ - { - "id": "sa-09.05_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sa-9.5_prm_1" - }, - { - "name": "label", - "value": "SA-09(05)_ODP[01]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "information processing, information or data, AND system services" - } - ] - }, - { - "id": "sa-09.05_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sa-9.5_prm_2" - }, - { - "name": "label", - "value": "SA-09(05)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "locations", - "constraints": [ - { - "description": "U.S./U.S. Territories or geographic locations where there is U.S. jurisdiction" - } - ], - "guidelines": [ - { - "prose": "locations where {{ insert: param, sa-09.05_odp.01 }} is/are to be restricted are defined;" - } - ] - }, - { - "id": "sa-09.05_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "sa-9.5_prm_3" - }, - { - "name": "alt-label", - "value": "requirements or conditions", - "class": "sp800-53" - }, - { - "name": "label", - "value": "SA-09(05)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "requirements", - "constraints": [ - { - "description": "all High impact data, systems, or services" - } - ], - "guidelines": [ - { - "prose": "requirements or conditions for restricting the location of {{ insert: param, sa-09.05_odp.01 }} are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SA-09(05)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-9(5)" - }, - { - "name": "label", - "value": "SA-09(05)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-09.05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#sa-9", - "rel": "required" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sr-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-9.5_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Restrict the location of {{ insert: param, sa-09.05_odp.01 }} to {{ insert: param, sa-09.05_odp.02 }} based on {{ insert: param, sa-09.05_odp.03 }}." - }, - { - "id": "sa-9.5_gdn", - "name": "guidance", - "prose": "The location of information processing, information and data storage, or system services can have a direct impact on the ability of organizations to successfully execute their mission and business functions. The impact occurs when external providers control the location of processing, storage, or services. The criteria that external providers use for the selection of processing, storage, or service locations may be different from the criteria that organizations use. For example, organizations may desire that data or information storage locations be restricted to certain locations to help facilitate incident response activities in case of information security incidents or breaches. Incident response activities, including forensic analyses and after-the-fact investigations, may be adversely affected by the governing laws, policies, or protocols in the locations where processing and storage occur and/or the locations from which system services emanate." - }, - { - "id": "sa-9.5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-09(05)", - "class": "sp800-53a" - } - ], - "prose": "based on {{ insert: param, sa-09.05_odp.03 }}, {{ insert: param, sa-09.05_odp.01 }} is/are restricted to {{ insert: param, sa-09.05_odp.02 }}.", - "links": [ - { - "href": "#sa-9.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-9.5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-09(05)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nprocedures addressing external system services\n\nacquisition contracts for the system, system component, or system service\n\nsolicitation documentation\n\nacquisition documentation\n\nservice level agreements\n\nrestricted locations for information processing\n\ninformation/data and/or system services\n\ninformation processing, information/data, and/or system services to be maintained in restricted locations\n\norganizational security requirements or conditions for external providers\n\nsystem security plan\n\nsupply chain risk management plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-9.5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-09(05)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and service acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\nexternal providers of system services\n\norganizational personnel with supply chain risk management responsibilities" - } - ] - }, - { - "id": "sa-9.5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SA-09(05)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for defining the requirements to restrict locations of information processing, information/data, or information services\n\norganizational processes for ensuring the location is restricted in accordance with requirements or conditions" - } - ] - } - ] - } - ] - }, - { - "id": "sa-10", - "class": "SP800-53", - "title": "Developer Configuration Management", - "params": [ - { - "id": "sa-10_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sa-10_prm_1" - }, - { - "name": "label", - "value": "SA-10_ODP[01]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "development, implementation, AND operation" - } - ] - }, - { - "id": "sa-10_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sa-10_prm_2" - }, - { - "name": "alt-label", - "value": "configuration items under configuration management", - "class": "sp800-53" - }, - { - "name": "label", - "value": "SA-10_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "configuration items", - "guidelines": [ - { - "prose": "configuration items under configuration management are defined;" - } - ] - }, - { - "id": "sa-10_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "sa-10_prm_3" - }, - { - "name": "label", - "value": "SA-10_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "personnel", - "guidelines": [ - { - "prose": "personnel to whom security flaws and flaw resolutions within the system, component, or service are reported is/are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SA-10", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-10" - }, - { - "name": "label", - "value": "SA-10", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-10" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#678e3d6c-150b-4393-aec5-6e3481eb1e00", - "rel": "reference" - }, - { - "href": "#eea3c092-42ed-4382-a6f4-1adadef01b9d", - "rel": "reference" - }, - { - "href": "#a295ca19-8c75-4b4c-8800-98024732e181", - "rel": "reference" - }, - { - "href": "#20db4e66-e257-450c-b2e4-2bb9a62a2c88", - "rel": "reference" - }, - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#cm-9", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - }, - { - "href": "#sr-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sr-4", - "rel": "related" - }, - { - "href": "#sr-5", - "rel": "related" - }, - { - "href": "#sr-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-10_smt", - "name": "statement", - "prose": "Require the developer of the system, system component, or system service to:", - "parts": [ - { - "id": "sa-10_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Perform configuration management during system, component, or service {{ insert: param, sa-10_odp.01 }};" - }, - { - "id": "sa-10_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Document, manage, and control the integrity of changes to {{ insert: param, sa-10_odp.02 }};" - }, - { - "id": "sa-10_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Implement only organization-approved changes to the system, component, or service;" - }, - { - "id": "sa-10_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Document approved changes to the system, component, or service and the potential security and privacy impacts of such changes; and" - }, - { - "id": "sa-10_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Track security flaws and flaw resolution within the system, component, or service and report findings to {{ insert: param, sa-10_odp.03 }}." - } - ] - }, - { - "id": "sa-10_gdn", - "name": "guidance", - "prose": "Organizations consider the quality and completeness of configuration management activities conducted by developers as direct evidence of applying effective security controls. Controls include protecting the master copies of material used to generate security-relevant portions of the system hardware, software, and firmware from unauthorized modification or destruction. Maintaining the integrity of changes to the system, system component, or system service requires strict configuration control throughout the system development life cycle to track authorized changes and prevent unauthorized changes.\n\nThe configuration items that are placed under configuration management include the formal model; the functional, high-level, and low-level design specifications; other design data; implementation documentation; source code and hardware schematics; the current running version of the object code; tools for comparing new versions of security-relevant hardware descriptions and source code with previous versions; and test fixtures and documentation. Depending on the mission and business needs of organizations and the nature of the contractual relationships in place, developers may provide configuration management support during the operations and maintenance stage of the system development life cycle." - }, - { - "id": "sa-10_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SA-10 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "sa-10_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(e) Requirement:" - } - ], - "prose": "track security flaws and flaw resolution within the system, component, or service and report findings to organization-defined personnel, to include FedRAMP." - } - ] - }, - { - "id": "sa-10_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-10", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-10_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-10a.", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to perform configuration management during system, component, or service {{ insert: param, sa-10_odp.01 }};", - "links": [ - { - "href": "#sa-10_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-10_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-10b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-10_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-10b.[01]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to document the integrity of changes to {{ insert: param, sa-10_odp.02 }};", - "links": [ - { - "href": "#sa-10_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-10_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-10b.[02]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to manage the integrity of changes to {{ insert: param, sa-10_odp.02 }};", - "links": [ - { - "href": "#sa-10_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-10_obj.b-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-10b.[03]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to control the integrity of changes to {{ insert: param, sa-10_odp.02 }};", - "links": [ - { - "href": "#sa-10_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-10_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-10_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-10c.", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to implement only organization-approved changes to the system, component, or service;", - "links": [ - { - "href": "#sa-10_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-10_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-10d.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-10_obj.d-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-10d.[01]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to document approved changes to the system, component, or service;", - "links": [ - { - "href": "#sa-10_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-10_obj.d-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-10d.[02]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to document the potential security impacts of approved changes;", - "links": [ - { - "href": "#sa-10_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-10_obj.d-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-10d.[03]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to document the potential privacy impacts of approved changes;", - "links": [ - { - "href": "#sa-10_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-10_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-10_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-10e.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-10_obj.e-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-10e.[01]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to track security flaws within the system, component, or service;", - "links": [ - { - "href": "#sa-10_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-10_obj.e-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-10e.[02]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to track security flaw resolutions within the system, component, or service;", - "links": [ - { - "href": "#sa-10_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-10_obj.e-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-10e.[03]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to report findings to {{ insert: param, sa-10_odp.03 }}.", - "links": [ - { - "href": "#sa-10_smt.e", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-10_smt.e", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-10_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-10_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-10-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nprocedures addressing system developer configuration management\n\nsolicitation documentation\n\nacquisition documentation\n\nservice level agreements\n\nacquisition contracts for the system, system component, or system service\n\nsystem developer configuration management plan\n\nsecurity flaw and flaw resolution tracking records\n\nsystem change authorization records\n\nchange control records\n\nconfiguration management records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-10_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-10-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and service acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with configuration management responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "sa-10_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SA-10-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for monitoring developer configuration management\n\nmechanisms supporting and/or implementing the monitoring of developer configuration management" - } - ] - } - ] - }, - { - "id": "sa-11", - "class": "SP800-53", - "title": "Developer Testing and Evaluation", - "params": [ - { - "id": "sa-11_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sa-11_prm_1" - }, - { - "name": "label", - "value": "SA-11_ODP[01]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "unit", - "integration", - "system", - "regression" - ] - } - }, - { - "id": "sa-11_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sa-11_prm_2" - }, - { - "name": "alt-label", - "value": "frequency", - "class": "sp800-53" - }, - { - "name": "label", - "value": "SA-11_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency to conduct", - "guidelines": [ - { - "prose": "frequency at which to conduct {{ insert: param, sa-11_odp.01 }} testing/evaluation is defined;" - } - ] - }, - { - "id": "sa-11_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "sa-11_prm_3" - }, - { - "name": "label", - "value": "SA-11_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "depth and coverage", - "guidelines": [ - { - "prose": "depth and coverage of {{ insert: param, sa-11_odp.01 }} testing/evaluation is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SA-11", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-11" - }, - { - "name": "label", - "value": "SA-11", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-11" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#4452efc0-e79e-47b8-aa30-b54f3ef61c2f", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#a21aef46-7330-48a0-b2e1-c5bb8b2dd11d", - "rel": "reference" - }, - { - "href": "#708b94e1-3d5e-4b22-ab43-1c69f3a97e37", - "rel": "reference" - }, - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "#sa-17", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - }, - { - "href": "#sr-5", - "rel": "related" - }, - { - "href": "#sr-6", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sr-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-11_smt", - "name": "statement", - "prose": "Require the developer of the system, system component, or system service, at all post-design stages of the system development life cycle, to:", - "parts": [ - { - "id": "sa-11_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop and implement a plan for ongoing security and privacy control assessments;" - }, - { - "id": "sa-11_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Perform {{ insert: param, sa-11_odp.01 }} testing/evaluation {{ insert: param, sa-11_odp.02 }} at {{ insert: param, sa-11_odp.03 }};" - }, - { - "id": "sa-11_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Produce evidence of the execution of the assessment plan and the results of the testing and evaluation;" - }, - { - "id": "sa-11_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Implement a verifiable flaw remediation process; and" - }, - { - "id": "sa-11_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Correct flaws identified during testing and evaluation." - } - ] - }, - { - "id": "sa-11_gdn", - "name": "guidance", - "prose": "Developmental testing and evaluation confirms that the required controls are implemented correctly, operating as intended, enforcing the desired security and privacy policies, and meeting established security and privacy requirements. Security properties of systems and the privacy of individuals may be affected by the interconnection of system components or changes to those components. The interconnections or changes—including upgrading or replacing applications, operating systems, and firmware—may adversely affect previously implemented controls. Ongoing assessment during development allows for additional types of testing and evaluation that developers can conduct to reduce or eliminate potential flaws. Testing custom software applications may require approaches such as manual code review, security architecture review, and penetration testing, as well as and static analysis, dynamic analysis, binary analysis, or a hybrid of the three analysis approaches.\n\nDevelopers can use the analysis approaches, along with security instrumentation and fuzzing, in a variety of tools and in source code reviews. The security and privacy assessment plans include the specific activities that developers plan to carry out, including the types of analyses, testing, evaluation, and reviews of software and firmware components; the degree of rigor to be applied; the frequency of the ongoing testing and evaluation; and the types of artifacts produced during those processes. The depth of testing and evaluation refers to the rigor and level of detail associated with the assessment process. The coverage of testing and evaluation refers to the scope (i.e., number and type) of the artifacts included in the assessment process. Contracts specify the acceptance criteria for security and privacy assessment plans, flaw remediation processes, and the evidence that the plans and processes have been diligently applied. Methods for reviewing and protecting assessment plans, evidence, and documentation are commensurate with the security category or classification level of the system. Contracts may specify protection requirements for documentation." - }, - { - "id": "sa-11_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-11", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-11_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-11a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-11_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11a.[01]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to develop a plan for ongoing security assessments;", - "links": [ - { - "href": "#sa-11_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to implement a plan for ongoing security assessments;", - "links": [ - { - "href": "#sa-11_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11a.[03]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to develop a plan for privacy assessments;", - "links": [ - { - "href": "#sa-11_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to implement a plan for ongoing privacy assessments;", - "links": [ - { - "href": "#sa-11_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-11_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11b.", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to perform {{ insert: param, sa-11_odp.01 }} testing/evaluation {{ insert: param, sa-11_odp.02 }} at {{ insert: param, sa-11_odp.03 }};", - "links": [ - { - "href": "#sa-11_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-11_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-11c.[01]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to produce evidence of the execution of the assessment plan;", - "links": [ - { - "href": "#sa-11_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-11c.[02]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to produce the results of the testing and evaluation;", - "links": [ - { - "href": "#sa-11_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-11_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11d.", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to implement a verifiable flaw remediation process;", - "links": [ - { - "href": "#sa-11_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11e.", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to correct flaws identified during testing and evaluation.", - "links": [ - { - "href": "#sa-11_smt.e", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-11_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-11-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nsystem and services acquisition procedures\n\nprocedures addressing system developer security and privacy testing\n\nprocedures addressing flaw remediation\n\nsolicitation documentation\n\nacquisition documentation\n\nservice level agreements\n\nacquisition contracts for the system, system component, or system service\n\nsecurity and privacy architecture\n\nsystem design documentation\n\nsystem developer security and privacy assessment plans\n\nresults of developer security and privacy assessments for the system, system component, or system service\n\nsecurity and privacy flaw and remediation tracking records\n\nsystem security plan\n\nprivacy plan\n\nprivacy impact assessment\n\nprivacy risk assessment documentation\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-11_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-11-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and service acquisition responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\norganizational personnel with developer security and privacy testing responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "sa-11_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SA-11-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for monitoring developer security testing and evaluation\n\nmechanisms supporting and/or implementing the monitoring of developer security and privacy testing and evaluation" - } - ] - } - ], - "controls": [ - { - "id": "sa-11.1", - "class": "SP800-53-enhancement", - "title": "Static Code Analysis", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SA-11(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-11(1)" - }, - { - "name": "label", - "value": "SA-11(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-11.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#sa-11", - "rel": "required" - } - ], - "parts": [ - { - "id": "sa-11.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "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 the analysis." - }, - { - "id": "sa-11.1_gdn", - "name": "guidance", - "prose": "Static code analysis provides a technology and methodology for security reviews and includes checking for weaknesses in the code as well as for the incorporation of libraries or other included code with known vulnerabilities or that are out-of-date and not supported. Static code analysis can be used to identify vulnerabilities and enforce secure coding practices. It is most effective when used early in the development process, when each code change can automatically be scanned for potential weaknesses. Static code analysis can provide clear remediation guidance and identify defects for developers to fix. Evidence of the correct implementation of static analysis can include aggregate defect density for critical defect types, evidence that defects were inspected by developers or security professionals, and evidence that defects were remediated. A high density of ignored findings, commonly referred to as false positives, indicates a potential problem with the analysis process or the analysis tool. In such cases, organizations weigh the validity of the evidence against evidence from other sources." - }, - { - "id": "sa-11.1_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SA-11(1) Additional FedRAMP Requirements", - "parts": [ - { - "id": "sa-11.1_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "The service provider must document its methodology for reviewing newly developed code for the Service in its Continuous Monitoring Plan.\n\nIf Static code analysis cannot be performed (for example, when the source code is not available), then dynamic code analysis must be performed (see SA-11 (8))" - } - ] - }, - { - "id": "sa-11.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-11.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-11(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to employ static code analysis tools to identify common flaws;", - "links": [ - { - "href": "#sa-11.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11.1_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-11(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to employ static code analysis tools to document the results of the analysis.", - "links": [ - { - "href": "#sa-11.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-11.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-11(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nsystem and services acquisition procedures\n\nprocedures addressing system developer security testing\n\nprocedures addressing flaw remediation\n\nsolicitation documentation\n\nacquisition documentation\n\nservice level agreements\n\nacquisition contracts for the system, system component, or system service\n\nsecurity and privacy architecture\n\nsystem design documentation\n\nsystem developer security and privacy assessment plans\n\nresults of system developer security and privacy assessments\n\nsecurity flaw and remediation tracking records\n\nsystem security plan\n\nprivacy plan\n\nprivacy impact assessment\n\nprivacy risk assessment documentation\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-11.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-11(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and service acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with developer security and privacy testing responsibilities\n\norganizational personnel with configuration management responsibilities\n\nsystem developers" - } - ] - }, - { - "id": "sa-11.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SA-11(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for monitoring developer security testing and evaluation\n\nmechanisms supporting and/or implementing the monitoring of developer security testing and evaluation\n\nstatic code analysis tools" - } - ] - } - ] - }, - { - "id": "sa-11.2", - "class": "SP800-53-enhancement", - "title": "Threat Modeling and Vulnerability Analyses", - "params": [ - { - "id": "sa-11.2_prm_3", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "sa-11.02_odp.03" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "sa-11.02_odp.04" - } - ], - "label": "organization-defined breadth and depth of modeling and analyses" - }, - { - "id": "sa-11.2_prm_4", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "sa-11.02_odp.05" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "sa-11.02_odp.06" - } - ], - "label": "organization-defined acceptance criteria" - }, - { - "id": "sa-11.02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sa-11.2_prm_1" - }, - { - "name": "alt-label", - "value": "information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels", - "class": "sp800-53" - }, - { - "name": "label", - "value": "SA-11(02)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "information", - "guidelines": [ - { - "prose": "information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels to be used as contextual information for threat modeling and vulnerability analyses is defined;" - } - ] - }, - { - "id": "sa-11.02_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sa-11.2_prm_2" - }, - { - "name": "label", - "value": "SA-11(02)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "tools and methods", - "guidelines": [ - { - "prose": "the tools and methods to be employed for threat modeling and vulnerability analyses are defined;" - } - ] - }, - { - "id": "sa-11.02_odp.03", - "props": [ - { - "name": "label", - "value": "SA-11(02)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "breadth and depth", - "guidelines": [ - { - "prose": "the breadth and depth of threat modeling to be conducted is defined;" - } - ] - }, - { - "id": "sa-11.02_odp.04", - "props": [ - { - "name": "label", - "value": "SA-11(02)_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "breadth and depth", - "guidelines": [ - { - "prose": "the breadth and depth of vulnerability analyses to be conducted is defined;" - } - ] - }, - { - "id": "sa-11.02_odp.05", - "props": [ - { - "name": "label", - "value": "SA-11(02)_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "acceptance criteria", - "guidelines": [ - { - "prose": "acceptance criteria to be met by produced evidence for threat modeling are defined;" - } - ] - }, - { - "id": "sa-11.02_odp.06", - "props": [ - { - "name": "label", - "value": "SA-11(02)_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "acceptance criteria", - "guidelines": [ - { - "prose": "acceptance criteria to be met by produced evidence for vulnerability analyses are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SA-11(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-11(2)" - }, - { - "name": "label", - "value": "SA-11(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-11.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#sa-11", - "rel": "required" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-15", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-11.2_smt", - "name": "statement", - "prose": "Require the developer of the system, system component, or system service to perform threat modeling and vulnerability analyses during development and the subsequent testing and evaluation of the system, component, or service that:", - "parts": [ - { - "id": "sa-11.2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Uses the following contextual information: {{ insert: param, sa-11.02_odp.01 }};" - }, - { - "id": "sa-11.2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Employs the following tools and methods: {{ insert: param, sa-11.02_odp.02 }};" - }, - { - "id": "sa-11.2_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Conducts the modeling and analyses at the following level of rigor: {{ insert: param, sa-11.2_prm_3 }} ; and" - }, - { - "id": "sa-11.2_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(d)" - } - ], - "prose": "Produces evidence that meets the following acceptance criteria: {{ insert: param, sa-11.2_prm_4 }}." - } - ] - }, - { - "id": "sa-11.2_gdn", - "name": "guidance", - "prose": "Systems, system components, and system services may deviate significantly from the functional and design specifications created during the requirements and design stages of the system development life cycle. Therefore, updates to threat modeling and vulnerability analyses of those systems, system components, and system services during development and prior to delivery are critical to the effective operation of those systems, components, and services. Threat modeling and vulnerability analyses at this stage of the system development life cycle ensure that design and implementation changes have been accounted for and that vulnerabilities created because of those changes have been reviewed and mitigated." - }, - { - "id": "sa-11.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-11(02)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-11.2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-11(02)(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-11.2_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11(02)(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that uses {{ insert: param, sa-11.02_odp.01 }};", - "links": [ - { - "href": "#sa-11.2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11.2_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11(02)(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to perform vulnerability analyses during development of the system, component, or service that uses {{ insert: param, sa-11.02_odp.01 }};", - "links": [ - { - "href": "#sa-11.2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11.2_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11(02)(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that uses {{ insert: param, sa-11.02_odp.01 }};", - "links": [ - { - "href": "#sa-11.2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11.2_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11(02)(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that uses {{ insert: param, sa-11.02_odp.01 }};", - "links": [ - { - "href": "#sa-11.2_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-11.2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11.2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-11(02)(b)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-11.2_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11(02)(b)[01]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that employs {{ insert: param, sa-11.02_odp.02 }};", - "links": [ - { - "href": "#sa-11.2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11.2_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11(02)(b)[02]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that employs {{ insert: param, sa-11.02_odp.02 }};", - "links": [ - { - "href": "#sa-11.2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11.2_obj.b-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11(02)(b)[03]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to perform vulnerability analyses during development of the system, component, or service that employs {{ insert: param, sa-11.02_odp.02 }};", - "links": [ - { - "href": "#sa-11.2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11.2_obj.b-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11(02)(b)[04]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that employs {{ insert: param, sa-11.02_odp.02 }};", - "links": [ - { - "href": "#sa-11.2_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-11.2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11.2_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-11(02)(c)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-11.2_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11(02)(c)[01]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to perform threat modeling at {{ insert: param, sa-11.02_odp.03 }} during development of the system, component, or service;", - "links": [ - { - "href": "#sa-11.2_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11.2_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11(02)(c)[02]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that conducts modeling and analyses at {{ insert: param, sa-11.02_odp.04 }};", - "links": [ - { - "href": "#sa-11.2_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-11.2_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11.2_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-11(02)(d)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-11.2_obj.d-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11(02)(d)[01]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that produces evidence that meets {{ insert: param, sa-11.02_odp.05 }};", - "links": [ - { - "href": "#sa-11.2_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11.2_obj.d-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11(02)(d)[02]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that produces evidence that meets {{ insert: param, sa-11.02_odp.05 }};", - "links": [ - { - "href": "#sa-11.2_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11.2_obj.d-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11(02)(d)[03]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to perform vulnerability analyses during development of the system, component, or service that produces evidence that meets {{ insert: param, sa-11.02_odp.06 }};", - "links": [ - { - "href": "#sa-11.2_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11.2_obj.d-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-11(02)(d)[04]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that produces evidence that meets {{ insert: param, sa-11.02_odp.06 }}.", - "links": [ - { - "href": "#sa-11.2_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-11.2_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-11.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-11.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-11(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nprocedures addressing system developer security testing\n\nsolicitation documentation\n\nacquisition documentation\n\nservice level agreements\n\nacquisition contracts for the system, system component, or system service\n\nsystem developer security test plans\n\nrecords of developer security testing results for the system, system component, or system service\n\nvulnerability scanning results\n\nsystem risk assessment reports\n\nthreat and vulnerability analysis reports\n\nsystem security plan\n\nsupply chain risk management plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-11.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-11(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and service acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with developer security testing responsibilities\n\nsystem developers\n\norganizational personnel with supply chain risk management responsibilities" - } - ] - }, - { - "id": "sa-11.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SA-11(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for monitoring developer security testing and evaluation\n\nmechanisms supporting and/or implementing the monitoring of developer security testing and evaluation" - } - ] - } - ] - } - ] - }, - { - "id": "sa-15", - "class": "SP800-53", - "title": "Development Process, Standards, and Tools", - "params": [ - { - "id": "sa-15_prm_2", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "sa-15_odp.02" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "sa-15_odp.03" - } - ], - "label": "organization-defined security and privacy requirements" - }, - { - "id": "sa-15_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sa-15_prm_1" - }, - { - "name": "label", - "value": "SA-15_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "frequency as before first use and annually thereafter" - } - ], - "guidelines": [ - { - "prose": "frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined;" - } - ] - }, - { - "id": "sa-15_odp.02", - "props": [ - { - "name": "label", - "value": "SA-15_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "security requirements", - "constraints": [ - { - "description": "FedRAMP Security Authorization requirements" - } - ], - "guidelines": [ - { - "prose": "security requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined;" - } - ] - }, - { - "id": "sa-15_odp.03", - "props": [ - { - "name": "label", - "value": "SA-15_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "privacy requirements", - "guidelines": [ - { - "prose": "privacy requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SA-15", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-15" - }, - { - "name": "label", - "value": "SA-15", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-15" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "#d4296805-2dca-4c63-a95f-eeccaa826aec", - "rel": "reference" - }, - { - "href": "#ma-6", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - }, - { - "href": "#sa-11", - "rel": "related" - }, - { - "href": "#sr-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sr-4", - "rel": "related" - }, - { - "href": "#sr-5", - "rel": "related" - }, - { - "href": "#sr-6", - "rel": "related" - }, - { - "href": "#sr-9", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-15_smt", - "name": "statement", - "parts": [ - { - "id": "sa-15_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Require the developer of the system, system component, or system service to follow a documented development process that:", - "parts": [ - { - "id": "sa-15_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Explicitly addresses security and privacy requirements;" - }, - { - "id": "sa-15_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Identifies the standards and tools used in the development process;" - }, - { - "id": "sa-15_smt.a.3", - "name": "item", - "props": [ - { - "name": "label", - "value": "3." - } - ], - "prose": "Documents the specific tool options and tool configurations used in the development process; and" - }, - { - "id": "sa-15_smt.a.4", - "name": "item", - "props": [ - { - "name": "label", - "value": "4." - } - ], - "prose": "Documents, manages, and ensures the integrity of changes to the process and/or tools used in development; and" - } - ] - }, - { - "id": "sa-15_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Review the development process, standards, tools, tool options, and tool configurations {{ insert: param, sa-15_odp.01 }} to determine if the process, standards, tools, tool options and tool configurations selected and employed can satisfy the following security and privacy requirements: {{ insert: param, sa-15_prm_2 }}." - } - ] - }, - { - "id": "sa-15_gdn", - "name": "guidance", - "prose": "Development tools include programming languages and computer-aided design systems. Reviews of development processes include the use of maturity models to determine the potential effectiveness of such processes. Maintaining the integrity of changes to tools and processes facilitates effective supply chain risk assessment and mitigation. Such integrity requires configuration control throughout the system development life cycle to track authorized changes and prevent unauthorized changes." - }, - { - "id": "sa-15_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-15", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-15_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-15a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-15_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-15a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-15_obj.a.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-15a.01[01]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to follow a documented development process that explicitly addresses security requirements;", - "links": [ - { - "href": "#sa-15_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-15_obj.a.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-15a.01[02]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to follow a documented development process that explicitly addresses privacy requirements;", - "links": [ - { - "href": "#sa-15_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-15_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-15_obj.a.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-15a.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-15_obj.a.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-15a.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to follow a documented development process that identifies the standards used in the development process;", - "links": [ - { - "href": "#sa-15_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-15_obj.a.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-15a.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to follow a documented development process that identifies the tools used in the development process;", - "links": [ - { - "href": "#sa-15_smt.a.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-15_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-15_obj.a.3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-15a.03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-15_obj.a.3-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-15a.03[01]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to follow a documented development process that documents the specific tool used in the development process;", - "links": [ - { - "href": "#sa-15_smt.a.3", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-15_obj.a.3-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-15a.03[02]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to follow a documented development process that documents the specific tool configurations used in the development process;", - "links": [ - { - "href": "#sa-15_smt.a.3", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-15_smt.a.3", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-15_obj.a.4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-15a.04", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to follow a documented development process that documents, manages, and ensures the integrity of changes to the process and/or tools used in development;", - "links": [ - { - "href": "#sa-15_smt.a.4", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-15_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-15_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-15b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-15_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-15b.[01]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed {{ insert: param, sa-15_odp.01 }} to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy {{ insert: param, sa-15_odp.02 }};", - "links": [ - { - "href": "#sa-15_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-15_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-15b.[02]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed {{ insert: param, sa-15_odp.01 }} to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy {{ insert: param, sa-15_odp.03 }}.", - "links": [ - { - "href": "#sa-15_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-15_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-15_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-15_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-15-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nsystem and services acquisition procedures\n\nprocedures addressing development process, standards, and tools\n\nprocedures addressing the integration of security and privacy requirements during the development process\n\nsolicitation documentation\n\nacquisition documentation\n\ncritical component inventory documentation\n\nservice level agreements\n\nacquisition contracts for the system, system component, or system service\n\nsystem developer documentation listing tool options/configuration guides\n\nconfiguration management policy\n\nconfiguration management records\n\ndocumentation of development process reviews using maturity models\n\nchange control records\n\nconfiguration control records\n\ndocumented reviews of the development process, standards, tools, and tool options/configurations\n\nsystem security plan\n\nprivacy plan\n\nprivacy impact assessment\n\nprivacy risk assessment documentation\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-15_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-15-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and service acquisition responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem developer" - } - ] - } - ], - "controls": [ - { - "id": "sa-15.3", - "class": "SP800-53-enhancement", - "title": "Criticality Analysis", - "params": [ - { - "id": "sa-15.3_prm_2", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "sa-15.03_odp.02" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "sa-15.03_odp.03" - } - ], - "label": "organization-defined breadth and depth of criticality analysis" - }, - { - "id": "sa-15.03_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sa-15.3_prm_1" - }, - { - "name": "alt-label", - "value": "decision points in the system development life cycle", - "class": "sp800-53" - }, - { - "name": "label", - "value": "SA-15(03)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "decision points", - "guidelines": [ - { - "prose": "decision points in the system development life cycle are defined;" - } - ] - }, - { - "id": "sa-15.03_odp.02", - "props": [ - { - "name": "label", - "value": "SA-15(03)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "breadth", - "guidelines": [ - { - "prose": "the breadth of criticality analysis is defined;" - } - ] - }, - { - "id": "sa-15.03_odp.03", - "props": [ - { - "name": "label", - "value": "SA-15(03)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "depth", - "guidelines": [ - { - "prose": "the depth of criticality analysis is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SA-15(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-15(3)" - }, - { - "name": "label", - "value": "SA-15(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-15.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#sa-15", - "rel": "required" - }, - { - "href": "#ra-9", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-15.3_smt", - "name": "statement", - "prose": "Require the developer of the system, system component, or system service to perform a criticality analysis:", - "parts": [ - { - "id": "sa-15.3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "At the following decision points in the system development life cycle: {{ insert: param, sa-15.03_odp.01 }} ; and" - }, - { - "id": "sa-15.3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "At the following level of rigor: {{ insert: param, sa-15.3_prm_2 }}." - } - ] - }, - { - "id": "sa-15.3_gdn", - "name": "guidance", - "prose": "Criticality analysis performed by the developer provides input to the criticality analysis performed by organizations. Developer input is essential to organizational criticality analysis because organizations may not have access to detailed design documentation for system components that are developed as commercial off-the-shelf products. Such design documentation includes functional specifications, high-level designs, low-level designs, source code, and hardware schematics. Criticality analysis is important for organizational systems that are designated as high value assets. High value assets can be moderate- or high-impact systems due to heightened adversarial interest or potential adverse effects on the federal enterprise. Developer input is especially important when organizations conduct supply chain criticality analyses." - }, - { - "id": "sa-15.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-15(03)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-15.3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-15(03)(a)", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to perform a criticality analysis at {{ insert: param, sa-15.03_odp.01 }} in the system development life cycle;", - "links": [ - { - "href": "#sa-15.3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-15.3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-15(03)(b)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-15.3_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-15(03)(b)[01]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to perform a criticality analysis at the following rigor level: {{ insert: param, sa-15.03_odp.02 }};", - "links": [ - { - "href": "#sa-15.3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-15.3_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-15(03)(b)[02]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to perform a criticality analysis at the following rigor level: {{ insert: param, sa-15.03_odp.03 }} .", - "links": [ - { - "href": "#sa-15.3_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-15.3_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-15.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-15.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-15(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Supply chain risk management plan\n\nsystem and services acquisition policy\n\nprocedures addressing development process, standards, and tools\n\nprocedures addressing criticality analysis requirements for the system, system component, or system service\n\nsolicitation documentation\n\nacquisition documentation\n\nservice level agreements\n\nacquisition contracts for the system, system component, or system service\n\ncriticality analysis documentation\n\nbusiness impact analysis documentation\n\nsoftware development life cycle documentation\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-15.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-15(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and service acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel responsible for performing criticality analysis\n\nsystem developer\n\norganizational personnel with supply chain risk management responsibilities" - } - ] - }, - { - "id": "sa-15.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SA-15(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for performing criticality analysis\n\nmechanisms supporting and/or implementing criticality analysis" - } - ] - } - ] - } - ] - }, - { - "id": "sa-16", - "class": "SP800-53", - "title": "Developer-provided Training", - "params": [ - { - "id": "sa-16_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sa-16_prm_1" - }, - { - "name": "label", - "value": "SA-16_ODP", - "class": "sp800-53a" - } - ], - "label": "training", - "guidelines": [ - { - "prose": "training on the correct use and operation of the implemented security and privacy functions, controls, and/or mechanisms provided by the developer of the system, system component, or system service is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SA-16", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-16" - }, - { - "name": "label", - "value": "SA-16", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-16" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#at-2", - "rel": "related" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-16_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Require the developer of the system, system component, or system service to provide the following training on the correct use and operation of the implemented security and privacy functions, controls, and/or mechanisms: {{ insert: param, sa-16_odp }}." - }, - { - "id": "sa-16_gdn", - "name": "guidance", - "prose": "Developer-provided training applies to external and internal (in-house) developers. Training personnel is essential to ensuring the effectiveness of the controls implemented within organizational systems. Types of training include web-based and computer-based training, classroom-style training, and hands-on training (including micro-training). Organizations can also request training materials from developers to conduct in-house training or offer self-training to organizational personnel. Organizations determine the type of training necessary and may require different types of training for different security and privacy functions, controls, and mechanisms." - }, - { - "id": "sa-16_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-16", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to provide {{ insert: param, sa-16_odp }} on the correct use and operation of the implemented security and privacy functions, controls, and/or mechanisms.", - "links": [ - { - "href": "#sa-16_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-16_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-16-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nsystem and services acquisition procedures\n\nprocedures addressing developer-provided training\n\nsolicitation documentation\n\nacquisition documentation\n\nservice level agreements\n\nacquisition contracts for the system, system component, or system service\n\norganizational security and privacy training policy\n\ndeveloper-provided training materials\n\ntraining records\n\nsystem security plan\n\nprivacy plan\n\nprivacy impact assessment\n\nprivacy risk assessment documentation\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-16_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-16-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and service acquisition responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem developer\n\nexternal or internal (in-house) developers with training responsibilities for the system, system component, or information system service" - } - ] - } - ] - }, - { - "id": "sa-17", - "class": "SP800-53", - "title": "Developer Security and Privacy Architecture and Design", - "props": [ - { - "name": "label", - "value": "SA-17", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-17" - }, - { - "name": "label", - "value": "SA-17", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-17" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#87087451-2af5-43d4-88c1-d66ad850f614", - "rel": "reference" - }, - { - "href": "#4452efc0-e79e-47b8-aa30-b54f3ef61c2f", - "rel": "reference" - }, - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#pl-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-7", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-17_smt", - "name": "statement", - "prose": "Require the developer of the system, system component, or system service to produce a design specification and security and privacy architecture that:", - "parts": [ - { - "id": "sa-17_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Is consistent with the organization’s security and privacy architecture that is an integral part the organization’s enterprise architecture;" - }, - { - "id": "sa-17_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Accurately and completely describes the required security and privacy functionality, and the allocation of controls among physical and logical components; and" - }, - { - "id": "sa-17_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Expresses how individual security and privacy functions, mechanisms, and services work together to provide required security and privacy capabilities and a unified approach to protection." - } - ] - }, - { - "id": "sa-17_gdn", - "name": "guidance", - "prose": "Developer security and privacy architecture and design are directed at external developers, although they could also be applied to internal (in-house) development. In contrast, [PL-8](#pl-8) is directed at internal developers to ensure that organizations develop a security and privacy architecture that is integrated with the enterprise architecture. The distinction between SA-17 and [PL-8](#pl-8) is especially important when organizations outsource the development of systems, system components, or system services and when there is a requirement to demonstrate consistency with the enterprise architecture and security and privacy architecture of the organization. [ISO 15408-2](#87087451-2af5-43d4-88c1-d66ad850f614), [ISO 15408-3](#4452efc0-e79e-47b8-aa30-b54f3ef61c2f) , and [SP 800-160-1](#e3cc0520-a366-4fc9-abc2-5272db7e3564) provide information on security architecture and design, including formal policy models, security-relevant components, formal and informal correspondence, conceptually simple design, and structuring for least privilege and testing." - }, - { - "id": "sa-17_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-17", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-17_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-17(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-17_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-17(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to produce a design specification and security architecture that are consistent with the organization’s security architecture, which is an integral part the organization’s enterprise architecture;", - "links": [ - { - "href": "#sa-17_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-17_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-17(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to produce a design specification and privacy architecture that are consistent with the organization’s privacy architecture, which is an integral part the organization’s enterprise architecture;", - "links": [ - { - "href": "#sa-17_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-17_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-17_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-17(b)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-17_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-17(b)[01]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to produce a design specification and security architecture that accurately and completely describe the required security functionality and the allocation of controls among physical and logical components;", - "links": [ - { - "href": "#sa-17_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-17_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-17(b)[02]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to produce a design specification and privacy architecture that accurately and completely describe the required privacy functionality and the allocation of controls among physical and logical components;", - "links": [ - { - "href": "#sa-17_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-17_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-17_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-17(c)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-17_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-17(c)[01]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to produce a design specification and security architecture that express how individual security functions, mechanisms, and services work together to provide required security capabilities and a unified approach to protection;", - "links": [ - { - "href": "#sa-17_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-17_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-17(c)[02]", - "class": "sp800-53a" - } - ], - "prose": "the developer of the system, system component, or system service is required to produce a design specification and privacy architecture that express how individual privacy functions, mechanisms, and services work together to provide required privacy capabilities and a unified approach to protection.", - "links": [ - { - "href": "#sa-17_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-17_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-17_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-17_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-17-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nsystem and services acquisition procedures\n\nenterprise architecture policy\n\nenterprise architecture documentation\n\nprocedures addressing developer security and privacy architecture and design specifications for the system\n\nsolicitation documentation\n\nacquisition documentation\n\nservice level agreements\n\nacquisition contracts for the system, system component, or system service\n\nsystem design documentation\n\ninformation system configuration settings and associated documentation\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-17_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-17-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with acquisition responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nsystem developer" - } - ] - } - ] - }, - { - "id": "sa-21", - "class": "SP800-53", - "title": "Developer Screening", - "params": [ - { - "id": "sa-21_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sa-21_prm_1" - }, - { - "name": "alt-label", - "value": "system, system component, or system service", - "class": "sp800-53" - }, - { - "name": "label", - "value": "SA-21_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "system, systems component, or system service", - "guidelines": [ - { - "prose": "the system, systems component, or system service that the developer has access to is/are defined;" - } - ] - }, - { - "id": "sa-21_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sa-21_prm_2" - }, - { - "name": "label", - "value": "SA-21_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "official government duties", - "guidelines": [ - { - "prose": "official government duties assigned to the developer are defined;" - } - ] - }, - { - "id": "sa-21_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "sa-21_prm_3" - }, - { - "name": "label", - "value": "SA-21_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "additional personnel screening criteria", - "guidelines": [ - { - "prose": "additional personnel screening criteria for the developer are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SA-21", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-21" - }, - { - "name": "label", - "value": "SA-21", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-21" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ps-2", - "rel": "related" - }, - { - "href": "#ps-3", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - }, - { - "href": "#ps-7", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sr-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-21_smt", - "name": "statement", - "prose": "Require that the developer of {{ insert: param, sa-21_odp.01 }}:", - "parts": [ - { - "id": "sa-21_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Has appropriate access authorizations as determined by assigned {{ insert: param, sa-21_odp.02 }} ; and" - }, - { - "id": "sa-21_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Satisfies the following additional personnel screening criteria: {{ insert: param, sa-21_odp.03 }}." - } - ] - }, - { - "id": "sa-21_gdn", - "name": "guidance", - "prose": "Developer screening is directed at external developers. Internal developer screening is addressed by [PS-3](#ps-3) . Because the system, system component, or system service may be used in critical activities essential to the national or economic security interests of the United States, organizations have a strong interest in ensuring that developers are trustworthy. The degree of trust required of developers may need to be consistent with that of the individuals who access the systems, system components, or system services once deployed. Authorization and personnel screening criteria include clearances, background checks, citizenship, and nationality. Developer trustworthiness may also include a review and analysis of company ownership and relationships that the company has with entities that may potentially affect the quality and reliability of the systems, components, or services being developed. Satisfying the required access authorizations and personnel screening criteria includes providing a list of all individuals who are authorized to perform development activities on the selected system, system component, or system service so that organizations can validate that the developer has satisfied the authorization and screening requirements." - }, - { - "id": "sa-21_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-21", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-21_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-21a.", - "class": "sp800-53a" - } - ], - "prose": "the developer of {{ insert: param, sa-21_odp.01 }} is required to have appropriate access authorizations as determined by assigned {{ insert: param, sa-21_odp.02 }};", - "links": [ - { - "href": "#sa-21_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-21_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-21b.", - "class": "sp800-53a" - } - ], - "prose": "the developer of {{ insert: param, sa-21_odp.01 }} is required to satisfy {{ insert: param, sa-21_odp.03 }}.", - "links": [ - { - "href": "#sa-21_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-21_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-21_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-21-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\npersonnel security policy and procedures\n\nprocedures addressing personnel screening\n\nsystem design documentation\n\nacquisition documentation\n\nservice level agreements\n\nacquisition contracts for developer services\n\nsystem configuration settings and associated documentation\n\nlist of appropriate access authorizations required by the developers of the system\n\npersonnel screening criteria and associated documentation\n\nsystem security plan\n\nsupply chain risk management plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-21_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-21-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and service acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel responsible for developer screening" - } - ] - }, - { - "id": "sa-21_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SA-21-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for developer screening\n\nmechanisms supporting developer screening" - } - ] - } - ] - }, - { - "id": "sa-22", - "class": "SP800-53", - "title": "Unsupported System Components", - "params": [ - { - "id": "sa-22_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sa-22_prm_1" - }, - { - "name": "label", - "value": "SA-22_ODP[01]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "in-house support", - "{{ insert: param, sa-22_odp.02 }}" - ] - } - }, - { - "id": "sa-22_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sa-22_prm_2" - }, - { - "name": "label", - "value": "SA-22_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "support from external providers", - "guidelines": [ - { - "prose": "support from external providers is defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SA-22", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SA-22" - }, - { - "name": "label", - "value": "SA-22", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sa-22" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "sa-22_smt", - "name": "statement", - "parts": [ - { - "id": "sa-22_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Replace system components when support for the components is no longer available from the developer, vendor, or manufacturer; or" - }, - { - "id": "sa-22_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Provide the following options for alternative sources for continued support for unsupported components {{ insert: param, sa-22_odp.01 }}." - } - ] - }, - { - "id": "sa-22_gdn", - "name": "guidance", - "prose": "Support for system components includes software patches, firmware updates, replacement parts, and maintenance contracts. An example of unsupported components includes when vendors no longer provide critical software patches or product updates, which can result in an opportunity for adversaries to exploit weaknesses in the installed components. Exceptions to replacing unsupported system components include systems that provide critical mission or business capabilities where newer technologies are not available or where the systems are so isolated that installing replacement components is not an option.\n\nAlternative sources for support address the need to provide continued support for system components that are no longer supported by the original manufacturers, developers, or vendors when such components remain essential to organizational mission and business functions. If necessary, organizations can establish in-house support by developing customized patches for critical software components or, alternatively, obtain the services of external providers who provide ongoing support for the designated unsupported components through contractual relationships. Such contractual relationships can include open-source software value-added vendors. The increased risk of using unsupported system components can be mitigated, for example, by prohibiting the connection of such components to public or uncontrolled networks, or implementing other forms of isolation." - }, - { - "id": "sa-22_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SA-22", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sa-22_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-22a.", - "class": "sp800-53a" - } - ], - "prose": "system components are replaced when support for the components is no longer available from the developer, vendor, or manufacturer;", - "links": [ - { - "href": "#sa-22_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-22_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SA-22b.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sa-22_odp.01 }} provide options for alternative sources for continued support for unsupported components.", - "links": [ - { - "href": "#sa-22_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sa-22_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sa-22_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SA-22-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and services acquisition policy\n\nprocedures addressing the replacement or continued use of unsupported system components\n\ndocumented evidence of replacing unsupported system components\n\ndocumented approvals (including justification) for the continued use of unsupported system components\n\nsystem security plan\n\nsupply chain risk management plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sa-22_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SA-22-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and service acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with the responsibility for the system development life cycle\n\norganizational personnel responsible for component replacement" - } - ] - }, - { - "id": "sa-22_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SA-22-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for replacing unsupported system components\n\nmechanisms supporting and/or implementing the replacement of unsupported system components" - } - ] - } - ] - } - ] - }, - { - "id": "sc", - "class": "family", - "title": "System and Communications Protection", - "controls": [ - { - "id": "sc-1", - "class": "SP800-53", - "title": "Policy and Procedures", - "params": [ - { - "id": "sc-1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "sc-01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "sc-01_odp.02" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "sc-01_odp.01", - "props": [ - { - "name": "label", - "value": "SC-01_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the system and communications protection policy is to be disseminated is/are defined;" - } - ] - }, - { - "id": "sc-01_odp.02", - "props": [ - { - "name": "label", - "value": "SC-01_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the system and communications protection procedures are to be disseminated is/are defined;" - } - ] - }, - { - "id": "sc-01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "sc-1_prm_2" - }, - { - "name": "label", - "value": "SC-01_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "organization-level", - "mission/business-process-level", - "system-level" - ] - } - }, - { - "id": "sc-01_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "sc-1_prm_3" - }, - { - "name": "label", - "value": "SC-01_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "official", - "guidelines": [ - { - "prose": "an official to manage the system and communications protection policy and procedures is defined;" - } - ] - }, - { - "id": "sc-01_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "sc-1_prm_4" - }, - { - "name": "label", - "value": "SC-01_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current system and communications protection policy is reviewed and updated is defined;" - } - ] - }, - { - "id": "sc-01_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "sc-1_prm_5" - }, - { - "name": "label", - "value": "SC-01_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that would require the current system and communications protection policy to be reviewed and updated are defined;" - } - ] - }, - { - "id": "sc-01_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "sc-1_prm_6" - }, - { - "name": "label", - "value": "SC-01_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current system and communications protection procedures are reviewed and updated is defined;" - } - ] - }, - { - "id": "sc-01_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "sc-1_prm_7" - }, - { - "name": "label", - "value": "SC-01_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "events", - "constraints": [ - { - "description": "significant changes" - } - ], - "guidelines": [ - { - "prose": "events that would require the system and communications protection procedures to be reviewed and updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SC-01", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-1" - }, - { - "name": "label", - "value": "SC-01", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#c7ac44e8-10db-4b64-b2b9-9e32ec1efed0", - "rel": "reference" - }, - { - "href": "#4c0ec2ee-a0d6-428a-9043-4504bc3ade6f", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-1_smt", - "name": "statement", - "parts": [ - { - "id": "sc-1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, a policy that addresses System and Communications Protection MUST be associated with SC-1 part a.", - "class": "policy" - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, at least one procedure that addresses System and Communications Protection MUST be associated with SC-1 part a.", - "class": "procedure" - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, document, and disseminate to {{ insert: param, sc-1_prm_1 }}:", - "parts": [ - { - "id": "sc-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, sc-01_odp.03 }} system and communications protection policy that:", - "parts": [ - { - "id": "sc-1_smt.a.1.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "sc-1_smt.a.1.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and" - } - ] - }, - { - "id": "sc-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the system and communications protection policy and the associated system and communications protection controls;" - } - ] - }, - { - "id": "sc-1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Designate an {{ insert: param, sc-01_odp.04 }} to manage the development, documentation, and dissemination of the system and communications protection policy and procedures; and" - }, - { - "id": "sc-1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the current system and communications protection:", - "parts": [ - { - "id": "sc-1_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Policy {{ insert: param, sc-01_odp.05 }} and following {{ insert: param, sc-01_odp.06 }} ; and" - }, - { - "id": "sc-1_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures {{ insert: param, sc-01_odp.07 }} and following {{ insert: param, sc-01_odp.08 }}." - } - ] - } - ] - }, - { - "id": "sc-1_gdn", - "name": "guidance", - "prose": "System and communications protection policy and procedures address the controls in the SC family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of system and communications protection policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to system and communications protection policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure." - }, - { - "id": "sc-1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-01a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-01a.[01]", - "class": "sp800-53a" - } - ], - "prose": "a system and communications protection policy is developed and documented;", - "links": [ - { - "href": "#sc-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-01a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the system and communications protection policy is disseminated to {{ insert: param, sc-01_odp.01 }};", - "links": [ - { - "href": "#sc-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-1_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-01a.[03]", - "class": "sp800-53a" - } - ], - "prose": "system and communications protection procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls are developed and documented;", - "links": [ - { - "href": "#sc-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-1_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-01a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the system and communications protection procedures are disseminated to {{ insert: param, sc-01_odp.02 }};", - "links": [ - { - "href": "#sc-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-1_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-01a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-1_obj.a.1.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-01a.01(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-1_obj.a.1.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-01a.01(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sc-01_odp.03 }} system and communications protection policy addresses purpose;", - "links": [ - { - "href": "#sc-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-1_obj.a.1.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-01a.01(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sc-01_odp.03 }} system and communications protection policy addresses scope;", - "links": [ - { - "href": "#sc-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-1_obj.a.1.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-01a.01(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sc-01_odp.03 }} system and communications protection policy addresses roles;", - "links": [ - { - "href": "#sc-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-1_obj.a.1.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-01a.01(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sc-01_odp.03 }} system and communications protection policy addresses responsibilities;", - "links": [ - { - "href": "#sc-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-1_obj.a.1.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-01a.01(a)[05]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sc-01_odp.03 }} system and communications protection policy addresses management commitment;", - "links": [ - { - "href": "#sc-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-1_obj.a.1.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-01a.01(a)[06]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sc-01_odp.03 }} system and communications protection policy addresses coordination among organizational entities;", - "links": [ - { - "href": "#sc-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-1_obj.a.1.a-7", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-01a.01(a)[07]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sc-01_odp.03 }} system and communications protection policy addresses compliance;", - "links": [ - { - "href": "#sc-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-1_obj.a.1.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-01a.01(b)", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sc-01_odp.03 }} system and communications protection policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines;", - "links": [ - { - "href": "#sc-1_smt.a.1.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-1_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-01b.", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sc-01_odp.04 }} is designated to manage the development, documentation, and dissemination of the system and communications protection policy and procedures;", - "links": [ - { - "href": "#sc-1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-01c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-1_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-01c.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-1_obj.c.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-01c.01[01]", - "class": "sp800-53a" - } - ], - "prose": "the current system and communications protection policy is reviewed and updated {{ insert: param, sc-01_odp.05 }};", - "links": [ - { - "href": "#sc-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-1_obj.c.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-01c.01[02]", - "class": "sp800-53a" - } - ], - "prose": "the current system and communications protection policy is reviewed and updated following {{ insert: param, sc-01_odp.06 }};", - "links": [ - { - "href": "#sc-1_smt.c.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-1_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-01c.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-1_obj.c.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-01c.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the current system and communications protection procedures are reviewed and updated {{ insert: param, sc-01_odp.07 }};", - "links": [ - { - "href": "#sc-1_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-1_obj.c.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-01c.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the current system and communications protection procedures are reviewed and updated following {{ insert: param, sc-01_odp.08 }}.", - "links": [ - { - "href": "#sc-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-1_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-01-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nsystem and communications protection procedures\n\nsystem security plan\n\nprivacy plan\n\nrisk management strategy documentation\n\naudit findings\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-01-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and communications protection responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - }, - { - "id": "sc-2", - "class": "SP800-53", - "title": "Separation of System and User Functionality", - "props": [ - { - "name": "label", - "value": "SC-02", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-2" - }, - { - "name": "label", - "value": "SC-02", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-22", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-32", - "rel": "related" - }, - { - "href": "#sc-39", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Separate user functionality, including user interface services, from system management functionality." - }, - { - "id": "sc-2_gdn", - "name": "guidance", - "prose": "System management functionality includes functions that are necessary to administer databases, network components, workstations, or servers. These functions typically require privileged user access. The separation of user functions from system management functions is physical or logical. Organizations may separate system management functions from user functions by using different computers, instances of operating systems, central processing units, or network addresses; by employing virtualization techniques; or some combination of these or other methods. Separation of system management functions from user functions includes web administrative interfaces that employ separate authentication methods for users of any other system resources. Separation of system and user functions may include isolating administrative interfaces on different domains and with additional access controls. The separation of system and user functionality can be achieved by applying the systems security engineering design principles in [SA-8](#sa-8) , including [SA-8(1)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sa-8.1), [SA-8(3)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sa-8.3), [SA-8(4)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sa-8.4), [SA-8(10)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sa-8.10), [SA-8(12)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sa-8.12), [SA-8(13)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sa-8.13), [SA-8(14)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sa-8.14) , and [SA-8(18)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sa-8.18)." - }, - { - "id": "sc-2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-02", - "class": "sp800-53a" - } - ], - "prose": "user functionality, including user interface services, is separated from system management functionality.", - "links": [ - { - "href": "#sc-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-02-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing application partitioning\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-02-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "id": "sc-2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-02-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Separation of user functionality from system management functionality" - } - ] - } - ] - }, - { - "id": "sc-3", - "class": "SP800-53", - "title": "Security Function Isolation", - "props": [ - { - "name": "label", - "value": "SC-03", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-3" - }, - { - "name": "label", - "value": "SC-03", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ac-25", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "#sa-17", - "rel": "related" - }, - { - "href": "#sc-2", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-32", - "rel": "related" - }, - { - "href": "#sc-39", - "rel": "related" - }, - { - "href": "#si-16", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Isolate security functions from nonsecurity functions." - }, - { - "id": "sc-3_gdn", - "name": "guidance", - "prose": "Security functions are isolated from nonsecurity functions by means of an isolation boundary implemented within a system via partitions and domains. The isolation boundary controls access to and protects the integrity of the hardware, software, and firmware that perform system security functions. Systems implement code separation in many ways, such as through the provision of security kernels via processor rings or processor modes. For non-kernel code, security function isolation is often achieved through file system protections that protect the code on disk and address space protections that protect executing code. Systems can restrict access to security functions using access control mechanisms and by implementing least privilege capabilities. While the ideal is for all code within the defined security function isolation boundary to only contain security-relevant code, it is sometimes necessary to include nonsecurity functions as an exception. The isolation of security functions from nonsecurity functions can be achieved by applying the systems security engineering design principles in [SA-8](#sa-8) , including [SA-8(1)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sa-8.1), [SA-8(3)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sa-8.3), [SA-8(4)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sa-8.4), [SA-8(10)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sa-8.10), [SA-8(12)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sa-8.12), [SA-8(13)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sa-8.13), [SA-8(14)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sa-8.14) , and [SA-8(18)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sa-8.18)." - }, - { - "id": "sc-3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-03", - "class": "sp800-53a" - } - ], - "prose": "security functions are isolated from non-security functions.", - "links": [ - { - "href": "#sc-3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-03-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing security function isolation\n\nlist of security functions to be isolated from non-security functions\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-03-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "id": "sc-3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-03-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Separation of security functions from non-security functions within the system" - } - ] - } - ] - }, - { - "id": "sc-4", - "class": "SP800-53", - "title": "Information in Shared System Resources", - "props": [ - { - "name": "label", - "value": "SC-04", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-4" - }, - { - "name": "label", - "value": "SC-04", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-4_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Prevent unauthorized and unintended information transfer via shared system resources." - }, - { - "id": "sc-4_gdn", - "name": "guidance", - "prose": "Preventing unauthorized and unintended information transfer via shared system resources stops information produced by the actions of prior users or roles (or the actions of processes acting on behalf of prior users or roles) from being available to current users or roles (or current processes acting on behalf of current users or roles) that obtain access to shared system resources after those resources have been released back to the system. Information in shared system resources also applies to encrypted representations of information. In other contexts, control of information in shared system resources is referred to as object reuse and residual information protection. Information in shared system resources does not address information remanence, which refers to the residual representation of data that has been nominally deleted; covert channels (including storage and timing channels), where shared system resources are manipulated to violate information flow restrictions; or components within systems for which there are only single users or roles." - }, - { - "id": "sc-4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-04", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-4_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-04[01]", - "class": "sp800-53a" - } - ], - "prose": "unauthorized information transfer via shared system resources is prevented;", - "links": [ - { - "href": "#sc-4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-4_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-04[02]", - "class": "sp800-53a" - } - ], - "prose": "unintended information transfer via shared system resources is prevented.", - "links": [ - { - "href": "#sc-4_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-04-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing information protection in shared system resources\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-04-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "id": "sc-4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-04-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms preventing the unauthorized and unintended transfer of information via shared system resources" - } - ] - } - ] - }, - { - "id": "sc-5", - "class": "SP800-53", - "title": "Denial-of-service Protection", - "params": [ - { - "id": "sc-05_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sc-5_prm_2" - }, - { - "name": "label", - "value": "SC-05_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "types of denial-of-service events", - "constraints": [ - { - "description": "at a minimum: ICMP (ping) flood, SYN flood, slowloris, buffer overflow attack, and volume attack" - } - ], - "guidelines": [ - { - "prose": "types of denial-of-service events to be protected against or limited are defined;" - } - ] - }, - { - "id": "sc-05_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sc-5_prm_1" - }, - { - "name": "label", - "value": "SC-05_ODP[02]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "Protect against" - } - ] - }, - { - "id": "sc-05_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "sc-5_prm_3" - }, - { - "name": "label", - "value": "SC-05_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "controls by type of denial-of-service event", - "guidelines": [ - { - "prose": "controls to achieve the denial-of-service objective by type of denial-of-service event are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SC-05", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-5" - }, - { - "name": "label", - "value": "SC-05", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#f5edfe51-d1f2-422e-9b27-5d0e90b49c72", - "rel": "reference" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-6", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-40", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-5_smt", - "name": "statement", - "parts": [ - { - "id": "sc-5_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "{{ insert: param, sc-05_odp.02 }} the effects of the following types of denial-of-service events: {{ insert: param, sc-05_odp.01 }} ; and" - }, - { - "id": "sc-5_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Employ the following controls to achieve the denial-of-service objective: {{ insert: param, sc-05_odp.03 }}." - } - ] - }, - { - "id": "sc-5_gdn", - "name": "guidance", - "prose": "Denial-of-service events may occur due to a variety of internal and external causes, such as an attack by an adversary or a lack of planning to support organizational needs with respect to capacity and bandwidth. Such attacks can occur across a wide range of network protocols (e.g., IPv4, IPv6). A variety of technologies are available to limit or eliminate the origination and effects of denial-of-service events. For example, boundary protection devices can filter certain types of packets to protect system components on internal networks from being directly affected by or the source of denial-of-service attacks. Employing increased network capacity and bandwidth combined with service redundancy also reduces the susceptibility to denial-of-service events." - }, - { - "id": "sc-5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-05", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-5_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-05a.", - "class": "sp800-53a" - } - ], - "prose": "the effects of {{ insert: param, sc-05_odp.01 }} are {{ insert: param, sc-05_odp.02 }};", - "links": [ - { - "href": "#sc-5_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-5_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-05b.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sc-05_odp.03 }} are employed to achieve the denial-of-service protection objective.", - "links": [ - { - "href": "#sc-5_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-05-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing denial-of-service protection\n\nsystem design documentation\n\nlist of denial-of-service attacks requiring employment of security safeguards to protect against or limit effects of such attacks\n\nlist of security safeguards protecting against or limiting the effects of denial-of-service attacks\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-05-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with incident response responsibilities\n\nsystem developer" - } - ] - }, - { - "id": "sc-5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-05-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms protecting against or limiting the effects of denial-of-service attacks" - } - ] - } - ] - }, - { - "id": "sc-7", - "class": "SP800-53", - "title": "Boundary Protection", - "params": [ - { - "id": "sc-07_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sc-7_prm_1" - }, - { - "name": "label", - "value": "SC-07_ODP", - "class": "sp800-53a" - } - ], - "select": { - "choice": [ - "physically", - "logically" - ] - } - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SC-07", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-7" - }, - { - "name": "label", - "value": "SC-07", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-07" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#628d22a1-6a11-4784-bc59-5cd9497b5445", - "rel": "reference" - }, - { - "href": "#482e4c99-9dc4-41ad-bba8-0f3f0032c1f8", - "rel": "reference" - }, - { - "href": "#a7f0e897-29a3-45c4-bd88-40dfef0e034a", - "rel": "reference" - }, - { - "href": "#d4d7c760-2907-403b-8b2a-767ca5370ecd", - "rel": "reference" - }, - { - "href": "#f5edfe51-d1f2-422e-9b27-5d0e90b49c72", - "rel": "reference" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#ac-20", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-13", - "rel": "related" - }, - { - "href": "#ca-3", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#cm-10", - "rel": "related" - }, - { - "href": "#cp-8", - "rel": "related" - }, - { - "href": "#cp-10", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pl-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-12", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-17", - "rel": "related" - }, - { - "href": "#sc-5", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-26", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-32", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-35", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-43", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-7_smt", - "name": "statement", - "parts": [ - { - "id": "sc-7_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Monitor and control communications at the external managed interfaces to the system and at key internal managed interfaces within the system;" - }, - { - "id": "sc-7_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Implement subnetworks for publicly accessible system components that are {{ insert: param, sc-07_odp }} separated from internal organizational networks; and" - }, - { - "id": "sc-7_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Connect to external networks or systems only through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security and privacy architecture." - } - ] - }, - { - "id": "sc-7_gdn", - "name": "guidance", - "prose": "Managed interfaces include gateways, routers, firewalls, guards, network-based malicious code analysis, virtualization systems, or encrypted tunnels implemented within a security architecture. Subnetworks that are physically or logically separated from internal networks are referred to as demilitarized zones or DMZs. Restricting or prohibiting interfaces within organizational systems includes restricting external web traffic to designated web servers within managed interfaces, prohibiting external traffic that appears to be spoofing internal addresses, and prohibiting internal traffic that appears to be spoofing external addresses. [SP 800-189](#f5edfe51-d1f2-422e-9b27-5d0e90b49c72) provides additional information on source address validation techniques to prevent ingress and egress of traffic with spoofed addresses. Commercial telecommunications services are provided by network components and consolidated management systems shared by customers. These services may also include third party-provided access lines and other service elements. Such services may represent sources of increased risk despite contract security provisions. Boundary protection may be implemented as a common control for all or part of an organizational network such that the boundary to be protected is greater than a system-specific boundary (i.e., an authorization boundary)." - }, - { - "id": "sc-7_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SC-7 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "sc-7_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "(b) Guidance:" - } - ], - "prose": "SC-7 (b) should be met by subnet isolation. A subnetwork (subnet) is a physically or logically segmented section of a larger network defined at TCP/IP Layer 3, to both minimize traffic and, important for a FedRAMP Authorization, add a crucial layer of network isolation. Subnets are distinct from VLANs (Layer 2), security groups, and VPCs and are specifically required to satisfy SC-7 part b and other controls. See the FedRAMP Subnets White Paper (https://www.fedramp.gov/assets/resources/documents/FedRAMP_subnets_white_paper.pdf) for additional information." - } - ] - }, - { - "id": "sc-7_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-07", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-7_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-07a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-7_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07a.[01]", - "class": "sp800-53a" - } - ], - "prose": "communications at external managed interfaces to the system are monitored;", - "links": [ - { - "href": "#sc-7_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07a.[02]", - "class": "sp800-53a" - } - ], - "prose": "communications at external managed interfaces to the system are controlled;", - "links": [ - { - "href": "#sc-7_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07a.[03]", - "class": "sp800-53a" - } - ], - "prose": "communications at key internal managed interfaces within the system are monitored;", - "links": [ - { - "href": "#sc-7_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07a.[04]", - "class": "sp800-53a" - } - ], - "prose": "communications at key internal managed interfaces within the system are controlled;", - "links": [ - { - "href": "#sc-7_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-7_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07b.", - "class": "sp800-53a" - } - ], - "prose": "subnetworks for publicly accessible system components are {{ insert: param, sc-07_odp }} separated from internal organizational networks;", - "links": [ - { - "href": "#sc-7_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07c.", - "class": "sp800-53a" - } - ], - "prose": "external networks or systems are only connected to through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security and privacy architecture.", - "links": [ - { - "href": "#sc-7_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-07-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\nlist of key internal boundaries of the system\n\nsystem design documentation\n\nboundary protection hardware and software\n\nsystem configuration settings and associated documentation\n\nenterprise security architecture documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-7_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-07-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "id": "sc-7_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-07-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing boundary protection capabilities" - } - ] - } - ], - "controls": [ - { - "id": "sc-7.3", - "class": "SP800-53-enhancement", - "title": "Access Points", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SC-07(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-7(3)" - }, - { - "name": "label", - "value": "SC-07(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-07.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#sc-7", - "rel": "required" - } - ], - "parts": [ - { - "id": "sc-7.3_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Limit the number of external network connections to the system." - }, - { - "id": "sc-7.3_gdn", - "name": "guidance", - "prose": "Limiting the number of external network connections facilitates monitoring of inbound and outbound communications traffic. The Trusted Internet Connection [DHS TIC](#4f42ee6e-86cc-403b-a51f-76c2b4f81b54) initiative is an example of a federal guideline that requires limits on the number of external network connections. Limiting the number of external network connections to the system is important during transition periods from older to newer technologies (e.g., transitioning from IPv4 to IPv6 network protocols). Such transitions may require implementing the older and newer technologies simultaneously during the transition period and thus increase the number of access points to the system." - }, - { - "id": "sc-7.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07(03)", - "class": "sp800-53a" - } - ], - "prose": "the number of external network connections to the system is limited.", - "links": [ - { - "href": "#sc-7.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-07(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\nsystem design documentation\n\nboundary protection hardware and software\n\nsystem architecture and configuration documentation\n\nsystem configuration settings and associated documentation\n\ncommunications and network traffic monitoring logs\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-7.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-07(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "id": "sc-7.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-07(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing boundary protection capabilities\n\nmechanisms limiting the number of external network connections to the system" - } - ] - } - ] - }, - { - "id": "sc-7.4", - "class": "SP800-53-enhancement", - "title": "External Telecommunications Services", - "params": [ - { - "id": "sc-07.04_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sc-7.4_prm_1" - }, - { - "name": "label", - "value": "SC-07(04)_ODP", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least every ninety (90) days or whenever there is a change in the threat environment that warrants a review of the exceptions" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to review exceptions to traffic flow policy is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SC-07(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-7(4)" - }, - { - "name": "label", - "value": "SC-07(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-07.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#sc-7", - "rel": "required" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-20", - "rel": "related" - }, - { - "href": "#sc-21", - "rel": "related" - }, - { - "href": "#sc-22", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-7.4_smt", - "name": "statement", - "parts": [ - { - "id": "sc-7.4_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Implement a managed interface for each external telecommunication service;" - }, - { - "id": "sc-7.4_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Establish a traffic flow policy for each managed interface;" - }, - { - "id": "sc-7.4_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(c)" - } - ], - "prose": "Protect the confidentiality and integrity of the information being transmitted across each interface;" - }, - { - "id": "sc-7.4_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(d)" - } - ], - "prose": "Document each exception to the traffic flow policy with a supporting mission or business need and duration of that need;" - }, - { - "id": "sc-7.4_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(e)" - } - ], - "prose": "Review exceptions to the traffic flow policy {{ insert: param, sc-07.04_odp }} and remove exceptions that are no longer supported by an explicit mission or business need;" - }, - { - "id": "sc-7.4_smt.f", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(f)" - } - ], - "prose": "Prevent unauthorized exchange of control plane traffic with external networks;" - }, - { - "id": "sc-7.4_smt.g", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(g)" - } - ], - "prose": "Publish information to enable remote networks to detect unauthorized control plane traffic from internal networks; and" - }, - { - "id": "sc-7.4_smt.h", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(h)" - } - ], - "prose": "Filter unauthorized control plane traffic from external networks." - } - ] - }, - { - "id": "sc-7.4_gdn", - "name": "guidance", - "prose": "External telecommunications services can provide data and/or voice communications services. Examples of control plane traffic include Border Gateway Protocol (BGP) routing, Domain Name System (DNS), and management protocols. See [SP 800-189](#f5edfe51-d1f2-422e-9b27-5d0e90b49c72) for additional information on the use of the resource public key infrastructure (RPKI) to protect BGP routes and detect unauthorized BGP announcements." - }, - { - "id": "sc-7.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-07(04)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-7.4_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07(04)(a)", - "class": "sp800-53a" - } - ], - "prose": "a managed interface is implemented for each external telecommunication service;", - "links": [ - { - "href": "#sc-7.4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.4_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07(04)(b)", - "class": "sp800-53a" - } - ], - "prose": "a traffic flow policy is established for each managed interface;", - "links": [ - { - "href": "#sc-7.4_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.4_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07(04)(c)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-7.4_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-07(04)(c)[01]", - "class": "sp800-53a" - } - ], - "prose": "the confidentiality of the information being transmitted across each interface is protected;", - "links": [ - { - "href": "#sc-7.4_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.4_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-07(04)(c)[02]", - "class": "sp800-53a" - } - ], - "prose": "the integrity of the information being transmitted across each interface is protected;", - "links": [ - { - "href": "#sc-7.4_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-7.4_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.4_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07(04)(d)", - "class": "sp800-53a" - } - ], - "prose": "each exception to the traffic flow policy is documented with a supporting mission or business need and duration of that need;", - "links": [ - { - "href": "#sc-7.4_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.4_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07(04)(e)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-7.4_obj.e-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-07(04)(e)[01]", - "class": "sp800-53a" - } - ], - "prose": "exceptions to the traffic flow policy are reviewed {{ insert: param, sc-07.04_odp }};", - "links": [ - { - "href": "#sc-7.4_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.4_obj.e-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-07(04)(e)[02]", - "class": "sp800-53a" - } - ], - "prose": "exceptions to the traffic flow policy that are no longer supported by an explicit mission or business need are removed;", - "links": [ - { - "href": "#sc-7.4_smt.e", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-7.4_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.4_obj.f", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07(04)(f)", - "class": "sp800-53a" - } - ], - "prose": "unauthorized exchanges of control plan traffic with external networks are prevented;", - "links": [ - { - "href": "#sc-7.4_smt.f", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.4_obj.g", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07(04)(g)", - "class": "sp800-53a" - } - ], - "prose": "information is published to enable remote networks to detect unauthorized control plane traffic from internal networks;", - "links": [ - { - "href": "#sc-7.4_smt.g", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.4_obj.h", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07(04)(h)", - "class": "sp800-53a" - } - ], - "prose": "unauthorized control plane traffic is filtered from external networks.", - "links": [ - { - "href": "#sc-7.4_smt.h", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-7.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-07(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\ntraffic flow policy\n\ninformation flow control policy\n\nprocedures addressing boundary protection\n\nsystem security architecture\n\nsystem design documentation\n\nboundary protection hardware and software\n\nsystem architecture and configuration documentation\n\nsystem configuration settings and associated documentation\n\nrecords of traffic flow policy exceptions\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-7.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-07(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "id": "sc-7.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-07(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for documenting and reviewing exceptions to the traffic flow policy\n\norganizational processes for removing exceptions to the traffic flow policy\n\nmechanisms implementing boundary protection capabilities\n\nmanaged interfaces implementing traffic flow policy" - } - ] - } - ] - }, - { - "id": "sc-7.5", - "class": "SP800-53-enhancement", - "title": "Deny by Default — Allow by Exception", - "params": [ - { - "id": "sc-07.05_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sc-7.5_prm_1" - }, - { - "name": "label", - "value": "SC-07(05)_ODP[01]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "any systems" - } - ] - }, - { - "id": "sc-07.05_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sc-7.5_prm_2" - }, - { - "name": "label", - "value": "SC-07(05)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "systems", - "guidelines": [ - { - "prose": "systems for which network communications traffic is denied by default and network communications traffic is allowed by exception are defined (if selected)." - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SC-07(05)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-7(5)" - }, - { - "name": "label", - "value": "SC-07(05)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-07.05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#sc-7", - "rel": "required" - } - ], - "parts": [ - { - "id": "sc-7.5_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Deny network communications traffic by default and allow network communications traffic by exception {{ insert: param, sc-07.05_odp.01 }}." - }, - { - "id": "sc-7.5_gdn", - "name": "guidance", - "prose": "Denying by default and allowing by exception applies to inbound and outbound network communications traffic. A deny-all, permit-by-exception network communications traffic policy ensures that only those system connections that are essential and approved are allowed. Deny by default, allow by exception also applies to a system that is connected to an external system." - }, - { - "id": "sc-7.5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07(05)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-7.5_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-07(05)[01]", - "class": "sp800-53a" - } - ], - "prose": "network communications traffic is denied by default {{ insert: param, sc-07.05_odp.01 }};", - "links": [ - { - "href": "#sc-7.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.5_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-07(05)[02]", - "class": "sp800-53a" - } - ], - "prose": "network communications traffic is allowed by exception {{ insert: param, sc-07.05_odp.01 }}.", - "links": [ - { - "href": "#sc-7.5_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-7.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-07(05)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-7.5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-07(05)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "id": "sc-7.5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-07(05)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing traffic management at managed interfaces" - } - ] - } - ] - }, - { - "id": "sc-7.7", - "class": "SP800-53-enhancement", - "title": "Split Tunneling for Remote Devices", - "params": [ - { - "id": "sc-07.07_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sc-7.7_prm_1" - }, - { - "name": "label", - "value": "SC-07(07)_ODP", - "class": "sp800-53a" - } - ], - "label": "safeguards", - "guidelines": [ - { - "prose": "safeguards to securely provision split tunneling are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SC-07(07)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-7(7)" - }, - { - "name": "label", - "value": "SC-07(07)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-07.07" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#sc-7", - "rel": "required" - } - ], - "parts": [ - { - "id": "sc-7.7_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Prevent split tunneling for remote devices connecting to organizational systems unless the split tunnel is securely provisioned using {{ insert: param, sc-07.07_odp }}." - }, - { - "id": "sc-7.7_gdn", - "name": "guidance", - "prose": "Split tunneling is the process of allowing a remote user or device to establish a non-remote connection with a system and simultaneously communicate via some other connection to a resource in an external network. This method of network access enables a user to access remote devices and simultaneously, access uncontrolled networks. Split tunneling might be desirable by remote users to communicate with local system resources, such as printers or file servers. However, split tunneling can facilitate unauthorized external connections, making the system vulnerable to attack and to exfiltration of organizational information. Split tunneling can be prevented by disabling configuration settings that allow such capability in remote devices and by preventing those configuration settings from being configurable by users. Prevention can also be achieved by the detection of split tunneling (or of configuration settings that allow split tunneling) in the remote device, and by prohibiting the connection if the remote device is using split tunneling. A virtual private network (VPN) can be used to securely provision a split tunnel. A securely provisioned VPN includes locking connectivity to exclusive, managed, and named environments, or to a specific set of pre-approved addresses, without user control." - }, - { - "id": "sc-7.7_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07(07)", - "class": "sp800-53a" - } - ], - "prose": "split tunneling is prevented for remote devices connecting to organizational systems unless the split tunnel is securely provisioned using {{ insert: param, sc-07.07_odp }}.", - "links": [ - { - "href": "#sc-7.7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.7_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-07(07)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\nsystem design documentation\n\nsystem hardware and software\n\nsystem architecture\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-7.7_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-07(07)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "id": "sc-7.7_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-07(07)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing boundary protection capabilities\n\nmechanisms supporting/restricting non-remote connections" - } - ] - } - ] - }, - { - "id": "sc-7.8", - "class": "SP800-53-enhancement", - "title": "Route Traffic to Authenticated Proxy Servers", - "params": [ - { - "id": "sc-07.08_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sc-7.8_prm_1" - }, - { - "name": "label", - "value": "SC-07(08)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "internal communications traffic", - "guidelines": [ - { - "prose": "internal communications traffic to be routed to external networks is defined;" - } - ] - }, - { - "id": "sc-07.08_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sc-7.8_prm_2" - }, - { - "name": "label", - "value": "SC-07(08)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "external networks", - "constraints": [ - { - "description": "any network outside of organizational control and any network outside the authorization boundary" - } - ], - "guidelines": [ - { - "prose": "external networks to which internal communications traffic is to be routed are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SC-07(08)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-7(8)" - }, - { - "name": "label", - "value": "SC-07(08)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-07.08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#sc-7", - "rel": "required" - }, - { - "href": "#ac-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-7.8_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Route {{ insert: param, sc-07.08_odp.01 }} to {{ insert: param, sc-07.08_odp.02 }} through authenticated proxy servers at managed interfaces." - }, - { - "id": "sc-7.8_gdn", - "name": "guidance", - "prose": "External networks are networks outside of organizational control. A proxy server is a server (i.e., system or application) that acts as an intermediary for clients requesting system resources from non-organizational or other organizational servers. System resources that may be requested include files, connections, web pages, or services. Client requests established through a connection to a proxy server are assessed to manage complexity and provide additional protection by limiting direct connectivity. Web content filtering devices are one of the most common proxy servers that provide access to the Internet. Proxy servers can support the logging of Transmission Control Protocol sessions and the blocking of specific Uniform Resource Locators, Internet Protocol addresses, and domain names. Web proxies can be configured with organization-defined lists of authorized and unauthorized websites. Note that proxy servers may inhibit the use of virtual private networks (VPNs) and create the potential for \"man-in-the-middle\" attacks (depending on the implementation)." - }, - { - "id": "sc-7.8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07(08)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sc-07.08_odp.01 }} is routed to {{ insert: param, sc-07.08_odp.02 }} through authenticated proxy servers at managed interfaces.", - "links": [ - { - "href": "#sc-7.8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-07(08)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\nsystem design documentation\n\nsystem hardware and software\n\nsystem architecture\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-7.8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-07(08)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "id": "sc-7.8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-07(08)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing traffic management through authenticated proxy servers at managed interfaces" - } - ] - } - ] - }, - { - "id": "sc-7.10", - "class": "SP800-53-enhancement", - "title": "Prevent Exfiltration", - "params": [ - { - "id": "sc-07.10_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sc-7.10_prm_1" - }, - { - "name": "label", - "value": "SC-07(10)_ODP", - "class": "sp800-53a" - } - ], - "label": "frequency", - "guidelines": [ - { - "prose": "the frequency for conducting exfiltration tests is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SC-07(10)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-7(10)" - }, - { - "name": "label", - "value": "SC-07(10)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-07.10" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#sc-7", - "rel": "required" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ca-8", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-7.10_smt", - "name": "statement", - "parts": [ - { - "id": "sc-7.10_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Prevent the exfiltration of information; and" - }, - { - "id": "sc-7.10_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Conduct exfiltration tests {{ insert: param, sc-07.10_odp }}." - } - ] - }, - { - "id": "sc-7.10_gdn", - "name": "guidance", - "prose": "Prevention of exfiltration applies to both the intentional and unintentional exfiltration of information. Techniques used to prevent the exfiltration of information from systems may be implemented at internal endpoints, external boundaries, and across managed interfaces and include adherence to protocol formats, monitoring for beaconing activity from systems, disconnecting external network interfaces except when explicitly needed, employing traffic profile analysis to detect deviations from the volume and types of traffic expected, call backs to command and control centers, conducting penetration testing, monitoring for steganography, disassembling and reassembling packet headers, and using data loss and data leakage prevention tools. Devices that enforce strict adherence to protocol formats include deep packet inspection firewalls and Extensible Markup Language (XML) gateways. The devices verify adherence to protocol formats and specifications at the application layer and identify vulnerabilities that cannot be detected by devices that operate at the network or transport layers. The prevention of exfiltration is similar to data loss prevention or data leakage prevention and is closely associated with cross-domain solutions and system guards that enforce information flow requirements." - }, - { - "id": "sc-7.10_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-07(10)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-7.10_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07(10)(a)", - "class": "sp800-53a" - } - ], - "prose": "the exfiltration of information is prevented;", - "links": [ - { - "href": "#sc-7.10_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.10_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07(10)(b)", - "class": "sp800-53a" - } - ], - "prose": "exfiltration tests are conducted {{ insert: param, sc-07.10_odp }}.", - "links": [ - { - "href": "#sc-7.10_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-7.10_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.10_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-07(10)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-7.10_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-07(10)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "id": "sc-7.10_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-07(10)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing boundary protection capabilities that prevent the unauthorized exfiltration of information across managed interfaces" - } - ] - } - ] - }, - { - "id": "sc-7.12", - "class": "SP800-53-enhancement", - "title": "Host-based Protection", - "params": [ - { - "id": "sc-07.12_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sc-7.12_prm_1" - }, - { - "name": "label", - "value": "SC-07(12)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "host-based boundary protection mechanisms", - "constraints": [ - { - "description": "Host Intrusion Prevention System (HIPS), Host Intrusion Detection System (HIDS), or minimally a host-based firewall" - } - ], - "guidelines": [ - { - "prose": "host-based boundary protection mechanisms to be implemented are defined;" - } - ] - }, - { - "id": "sc-07.12_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sc-7.12_prm_2" - }, - { - "name": "label", - "value": "SC-07(12)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "system components", - "guidelines": [ - { - "prose": "system components where host-based boundary protection mechanisms are to be implemented are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SC-07(12)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-7(12)" - }, - { - "name": "label", - "value": "SC-07(12)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-07.12" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#sc-7", - "rel": "required" - } - ], - "parts": [ - { - "id": "sc-7.12_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement {{ insert: param, sc-07.12_odp.01 }} at {{ insert: param, sc-07.12_odp.02 }}." - }, - { - "id": "sc-7.12_gdn", - "name": "guidance", - "prose": "Host-based boundary protection mechanisms include host-based firewalls. System components that employ host-based boundary protection mechanisms include servers, workstations, notebook computers, and mobile devices." - }, - { - "id": "sc-7.12_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07(12)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sc-07.12_odp.01 }} are implemented at {{ insert: param, sc-07.12_odp.02 }}.", - "links": [ - { - "href": "#sc-7.12_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.12_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-07(12)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\nsystem design documentation\n\nboundary protection hardware and software\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-7.12_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-07(12)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with boundary protection responsibilities\n\nsystem users" - } - ] - }, - { - "id": "sc-7.12_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-07(12)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms implementing host-based boundary protection capabilities" - } - ] - } - ] - }, - { - "id": "sc-7.18", - "class": "SP800-53-enhancement", - "title": "Fail Secure", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SC-07(18)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-7(18)" - }, - { - "name": "label", - "value": "SC-07(18)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-07.18" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#sc-7", - "rel": "required" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#cp-12", - "rel": "related" - }, - { - "href": "#sc-24", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-7.18_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Prevent systems from entering unsecure states in the event of an operational failure of a boundary protection device." - }, - { - "id": "sc-7.18_gdn", - "name": "guidance", - "prose": "Fail secure is a condition achieved by employing mechanisms to ensure that in the event of operational failures of boundary protection devices at managed interfaces, systems do not enter into unsecure states where intended security properties no longer hold. Managed interfaces include routers, firewalls, and application gateways that reside on protected subnetworks (commonly referred to as demilitarized zones). Failures of boundary protection devices cannot lead to or cause information external to the devices to enter the devices nor can failures permit unauthorized information releases." - }, - { - "id": "sc-7.18_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07(18)", - "class": "sp800-53a" - } - ], - "prose": "systems are prevented from entering unsecure states in the event of an operational failure of a boundary protection device.", - "links": [ - { - "href": "#sc-7.18_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.18_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-07(18)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\nsystem design documentation\n\nsystem architecture\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-7.18_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-07(18)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "id": "sc-7.18_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-07(18)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing secure failure" - } - ] - } - ] - }, - { - "id": "sc-7.20", - "class": "SP800-53-enhancement", - "title": "Dynamic Isolation and Segregation", - "params": [ - { - "id": "sc-07.20_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sc-7.20_prm_1" - }, - { - "name": "label", - "value": "SC-07(20)_ODP", - "class": "sp800-53a" - } - ], - "label": "system components", - "guidelines": [ - { - "prose": "system components to be dynamically isolated from other system components are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SC-07(20)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-7(20)" - }, - { - "name": "label", - "value": "SC-07(20)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-07.20" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#sc-7", - "rel": "required" - } - ], - "parts": [ - { - "id": "sc-7.20_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Provide the capability to dynamically isolate {{ insert: param, sc-07.20_odp }} from other system components." - }, - { - "id": "sc-7.20_gdn", - "name": "guidance", - "prose": "The capability to dynamically isolate certain internal system components is useful when it is necessary to partition or separate system components of questionable origin from components that possess greater trustworthiness. Component isolation reduces the attack surface of organizational systems. Isolating selected system components can also limit the damage from successful attacks when such attacks occur." - }, - { - "id": "sc-7.20_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07(20)", - "class": "sp800-53a" - } - ], - "prose": "the capability to dynamically isolate {{ insert: param, sc-07.20_odp }} from other system components is provided.", - "links": [ - { - "href": "#sc-7.20_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.20_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-07(20)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\nsystem design documentation\n\nsystem hardware and software\n\nsystem architecture\n\nsystem configuration settings and associated documentation\n\nlist of system components to be dynamically isolated/segregated from other components of the system\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-7.20_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-07(20)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "id": "sc-7.20_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-07(20)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing the capability to dynamically isolate/segregate system components" - } - ] - } - ] - }, - { - "id": "sc-7.21", - "class": "SP800-53-enhancement", - "title": "Isolation of System Components", - "params": [ - { - "id": "sc-07.21_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sc-7.21_prm_1" - }, - { - "name": "label", - "value": "SC-07(21)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "system components", - "guidelines": [ - { - "prose": "system components to be isolated by boundary protection mechanisms are defined;" - } - ] - }, - { - "id": "sc-07.21_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sc-7.21_prm_2" - }, - { - "name": "label", - "value": "SC-07(21)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "missions and/or business functions", - "guidelines": [ - { - "prose": "missions and/or business functions to be supported by system components isolated by boundary protection mechanisms are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SC-07(21)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-7(21)" - }, - { - "name": "label", - "value": "SC-07(21)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-07.21" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#sc-7", - "rel": "required" - }, - { - "href": "#ca-9", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-7.21_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Employ boundary protection mechanisms to isolate {{ insert: param, sc-07.21_odp.01 }} supporting {{ insert: param, sc-07.21_odp.02 }}." - }, - { - "id": "sc-7.21_gdn", - "name": "guidance", - "prose": "Organizations can isolate system components that perform different mission or business functions. Such isolation limits unauthorized information flows among system components and provides the opportunity to deploy greater levels of protection for selected system components. Isolating system components with boundary protection mechanisms provides the capability for increased protection of individual system components and to more effectively control information flows between those components. Isolating system components provides enhanced protection that limits the potential harm from hostile cyber-attacks and errors. The degree of isolation varies depending upon the mechanisms chosen. Boundary protection mechanisms include routers, gateways, and firewalls that separate system components into physically separate networks or subnetworks; cross-domain devices that separate subnetworks; virtualization techniques; and the encryption of information flows among system components using distinct encryption keys." - }, - { - "id": "sc-7.21_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-07(21)", - "class": "sp800-53a" - } - ], - "prose": "boundary protection mechanisms are employed to isolate {{ insert: param, sc-07.21_odp.01 }} supporting {{ insert: param, sc-07.21_odp.02 }}.", - "links": [ - { - "href": "#sc-7.21_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-7.21_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-07(21)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing boundary protection\n\nsystem design documentation\n\nsystem hardware and software\n\nenterprise architecture documentation\n\nsystem architecture\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-7.21_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-07(21)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with boundary protection responsibilities" - } - ] - }, - { - "id": "sc-7.21_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-07(21)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing the capability to separate system components supporting organizational missions and/or business functions" - } - ] - } - ] - } - ] - }, - { - "id": "sc-8", - "class": "SP800-53", - "title": "Transmission Confidentiality and Integrity", - "params": [ - { - "id": "sc-08_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sc-8_prm_1" - }, - { - "name": "label", - "value": "SC-08_ODP", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "confidentiality AND integrity" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SC-08", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-8" - }, - { - "name": "label", - "value": "SC-08", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#678e3d6c-150b-4393-aec5-6e3481eb1e00", - "rel": "reference" - }, - { - "href": "#736d6310-e403-4b57-a79d-9967970c66d7", - "rel": "reference" - }, - { - "href": "#7537638e-2837-407d-844b-40fb3fafdd99", - "rel": "reference" - }, - { - "href": "#d4d7c760-2907-403b-8b2a-767ca5370ecd", - "rel": "reference" - }, - { - "href": "#fe209006-bfd4-4033-a79a-9fee1adaf372", - "rel": "reference" - }, - { - "href": "#6bc4d137-aece-42a8-8081-9ecb1ebe9fb4", - "rel": "reference" - }, - { - "href": "#1c71b420-2bd9-4e52-9fc8-390f58b85b59", - "rel": "reference" - }, - { - "href": "#4c501da5-9d79-4cb6-ba80-97260e1ce327", - "rel": "reference" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#au-10", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ia-9", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#pe-4", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-16", - "rel": "related" - }, - { - "href": "#sc-20", - "rel": "related" - }, - { - "href": "#sc-23", - "rel": "related" - }, - { - "href": "#sc-28", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-8_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Protect the {{ insert: param, sc-08_odp }} of transmitted information." - }, - { - "id": "sc-8_gdn", - "name": "guidance", - "prose": "Protecting the confidentiality and integrity of transmitted information applies to internal and external networks as well as any system components that can transmit information, including servers, notebook computers, desktop computers, mobile devices, printers, copiers, scanners, facsimile machines, and radios. Unprotected communication paths are exposed to the possibility of interception and modification. Protecting the confidentiality and integrity of information can be accomplished by physical or logical means. Physical protection can be achieved by using protected distribution systems. A protected distribution system is a wireline or fiber-optics telecommunications system that includes terminals and adequate electromagnetic, acoustical, electrical, and physical controls to permit its use for the unencrypted transmission of classified information. Logical protection can be achieved by employing encryption techniques.\n\nOrganizations that rely on commercial providers who offer transmission services as commodity services rather than as fully dedicated services may find it difficult to obtain the necessary assurances regarding the implementation of needed controls for transmission confidentiality and integrity. In such situations, organizations determine what types of confidentiality or integrity services are available in standard, commercial telecommunications service packages. If it is not feasible to obtain the necessary controls and assurances of control effectiveness through appropriate contracting vehicles, organizations can implement appropriate compensating controls." - }, - { - "id": "sc-8_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SC-8 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "sc-8_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "For each instance of data in transit, confidentiality AND integrity should be through cryptography as specified in SC-8 (1), physical means as specified in SC-8 (5), or in combination.\n\nFor clarity, this control applies to all data in transit. Examples include the following data flows:\n\n- Crossing the system boundary\n- Between compute instances - including containers\n- From a compute instance to storage\n- Replication between availability zones\n- Transmission of backups to storage\n- From a load balancer to a compute instance\n- Flows from management tools required for their work - e.g. log collection, scanning, etc.\n\nThe following applies only when choosing SC-8 (5) in lieu of SC-8 (1).\n\nFedRAMP-Defined Assignment / Selection Parameters\n\nSC-8 (5)-1 \\[a hardened or alarmed carrier Protective Distribution System (PDS) when outside of Controlled Access Area (CAA)\\]\n\nSC-8 (5)-2 \\[prevent unauthorized disclosure of information AND detect changes to information\\]" - }, - { - "id": "sc-8_fr_gdn.2", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "SC-8 (5) applies when physical protection has been selected as the method to protect confidentiality and integrity. For physical protection, data in transit must be in either a Controlled Access Area (CAA), or a Hardened or alarmed PDS.\n\nHardened or alarmed PDS: Shall be as defined in SECTION X - CATEGORY 2 PDS INSTALLATION GUIDANCE of CNSSI No.7003, titled PROTECTED DISTRIBUTION SYSTEMS (PDS). Per the CNSSI No. 7003 Section VIII, PDS must originate and terminate in a Controlled Access Area (CAA).\n\nControlled Access Area (CAA): Data will be considered physically protected, and in a CAA if it meets Section 2.3 of the DHS's Recommended Practice: Improving Industrial Control System Cybersecurity with Defense-in-Depth Strategies. CSPs can meet Section 2.3 of the DHS' recommended practice by satisfactory implementation of the following controls PE-2 (1), PE-2 (2), PE-2 (3), PE-3 (2), PE-3 (3), PE-6 (2), and PE-6 (3).\n\nNote: When selecting SC-8 (5), the above SC-8(5), and the above referenced PE controls must be added to the SSP.\n\nCNSSI No.7003 can be accessed here:\n\nhttps://www.dcsa.mil/Portals/91/documents/ctp/nao/CNSSI_7003_PDS_September_2015.pdf\n\nDHS Recommended Practice: Improving Industrial Control System Cybersecurity with Defense-in-Depth Strategies can be accessed here:\n\nhttps://us-cert.cisa.gov/sites/default/files/FactSheets/NCCIC%20ICS_FactSheet_Defense_in_Depth_Strategies_S508C.pdf" - } - ] - }, - { - "id": "sc-8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-08", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sc-08_odp }} of transmitted information is/are protected.", - "links": [ - { - "href": "#sc-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-08-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing transmission confidentiality and integrity\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-08-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "id": "sc-8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-08-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing transmission confidentiality and/or integrity" - } - ] - } - ], - "controls": [ - { - "id": "sc-8.1", - "class": "SP800-53-enhancement", - "title": "Cryptographic Protection", - "params": [ - { - "id": "sc-08.01_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sc-8.1_prm_1" - }, - { - "name": "label", - "value": "SC-08(01)_ODP", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "prevent unauthorized disclosure of information AND detect changes to information" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SC-08(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-8(1)" - }, - { - "name": "label", - "value": "SC-08(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-08.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#sc-8", - "rel": "required" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-8.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement cryptographic mechanisms to {{ insert: param, sc-08.01_odp }} during transmission." - }, - { - "id": "sc-8.1_gdn", - "name": "guidance", - "prose": "Encryption protects information from unauthorized disclosure and modification during transmission. Cryptographic mechanisms that protect the confidentiality and integrity of information during transmission include TLS and IPSec. Cryptographic mechanisms used to protect information integrity include cryptographic hash functions that have applications in digital signatures, checksums, and message authentication codes." - }, - { - "id": "sc-8.1_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SC-8 (1) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "sc-8.1_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Please ensure SSP Section 10.3 Cryptographic Modules Implemented for Data At Rest (DAR) and Data In Transit (DIT) is fully populated for reference in this control." - }, - { - "id": "sc-8.1_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "See M-22-09, including \"Agencies encrypt all DNS requests and HTTP traffic within their environment\"\n\nSC-8 (1) applies when encryption has been selected as the method to protect confidentiality and integrity. Otherwise refer to SC-8 (5). SC-8 (1) is strongly encouraged." - }, - { - "id": "sc-8.1_fr_gdn.2", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Note that this enhancement requires the use of cryptography which must be compliant with Federal requirements and utilize FIPS validated or NSA approved cryptography (see SC-13.)" - }, - { - "id": "sc-8.1_fr_gdn.3", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "When leveraging encryption from the underlying IaaS/PaaS: While some IaaS/PaaS services provide encryption by default, many require encryption to be configured, and enabled by the customer. The CSP has the responsibility to verify encryption is properly configured." - } - ] - }, - { - "id": "sc-8.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-08(01)", - "class": "sp800-53a" - } - ], - "prose": "cryptographic mechanisms are implemented to {{ insert: param, sc-08.01_odp }} during transmission.", - "links": [ - { - "href": "#sc-8.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-8.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-08(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing transmission confidentiality and integrity\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-8.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-08(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "id": "sc-8.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-08(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Cryptographic mechanisms supporting and/or implementing transmission confidentiality and/or integrity\n\nmechanisms supporting and/or implementing alternative physical safeguards\n\norganizational processes for defining and implementing alternative physical safeguards" - } - ] - } - ] - } - ] - }, - { - "id": "sc-10", - "class": "SP800-53", - "title": "Network Disconnect", - "params": [ - { - "id": "sc-10_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sc-10_prm_1" - }, - { - "name": "label", - "value": "SC-10_ODP", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "no longer than ten (10) minutes for privileged sessions and no longer than fifteen (15) minutes for user sessions" - } - ], - "guidelines": [ - { - "prose": "a time period of inactivity after which the system terminates a network connection associated with a communication session is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SC-10", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-10" - }, - { - "name": "label", - "value": "SC-10", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-10" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#sc-23", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-10_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Terminate the network connection associated with a communications session at the end of the session or after {{ insert: param, sc-10_odp }} of inactivity." - }, - { - "id": "sc-10_gdn", - "name": "guidance", - "prose": "Network disconnect applies to internal and external networks. Terminating network connections associated with specific communications sessions includes de-allocating TCP/IP address or port pairs at the operating system level and de-allocating the networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. Periods of inactivity may be established by organizations and include time periods by type of network access or for specific network accesses." - }, - { - "id": "sc-10_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-10", - "class": "sp800-53a" - } - ], - "prose": "the network connection associated with a communication session is terminated at the end of the session or after {{ insert: param, sc-10_odp }} of inactivity.", - "links": [ - { - "href": "#sc-10_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-10_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-10-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing network disconnect\n\nsystem design documentation\n\nsecurity plan\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-10_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-10-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "id": "sc-10_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-10-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing a network disconnect capability" - } - ] - } - ] - }, - { - "id": "sc-12", - "class": "SP800-53", - "title": "Cryptographic Key Establishment and Management", - "params": [ - { - "id": "sc-12_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sc-12_prm_1" - }, - { - "name": "alt-label", - "value": "requirements for key generation, distribution, storage, access, and destruction", - "class": "sp800-53" - }, - { - "name": "label", - "value": "SC-12_ODP", - "class": "sp800-53a" - } - ], - "label": "requirements", - "constraints": [ - { - "description": "In accordance with Federal requirements" - } - ], - "guidelines": [ - { - "prose": "requirements for key generation, distribution, storage, access, and destruction are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SC-12", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-12" - }, - { - "name": "label", - "value": "SC-12", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-12" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#678e3d6c-150b-4393-aec5-6e3481eb1e00", - "rel": "reference" - }, - { - "href": "#20957dbb-6a1e-40a2-b38a-66f67d33ac2e", - "rel": "reference" - }, - { - "href": "#0d083d8a-5cc6-46f1-8d79-3081d42bcb75", - "rel": "reference" - }, - { - "href": "#eef62b16-c796-4554-955c-505824135b8a", - "rel": "reference" - }, - { - "href": "#110e26af-4765-49e1-8740-6750f83fcda1", - "rel": "reference" - }, - { - "href": "#e7942589-e267-4a5a-a3d9-f39a7aae81f0", - "rel": "reference" - }, - { - "href": "#8306620b-1920-4d73-8b21-12008528595f", - "rel": "reference" - }, - { - "href": "#737513fa-6758-403f-831d-5ddab5e23cb3", - "rel": "reference" - }, - { - "href": "#849b2358-683f-4d97-b111-1cc3d522ded5", - "rel": "reference" - }, - { - "href": "#3915a084-b87b-4f02-83d4-c369e746292f", - "rel": "reference" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "#au-10", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ia-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ia-13", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-11", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#sc-17", - "rel": "related" - }, - { - "href": "#sc-20", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-37", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-40", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-12_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Establish and manage cryptographic keys when cryptography is employed within the system in accordance with the following key management requirements: {{ insert: param, sc-12_odp }}." - }, - { - "id": "sc-12_gdn", - "name": "guidance", - "prose": "Cryptographic key management and establishment can be performed using manual procedures or automated mechanisms with supporting manual procedures. Organizations define key management requirements in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines and specify appropriate options, parameters, and levels. Organizations manage trust stores to ensure that only approved trust anchors are part of such trust stores. This includes certificates with visibility external to organizational systems and certificates related to the internal operations of systems. [NIST CMVP](#1acdc775-aafb-4d11-9341-dc6a822e9d38) and [NIST CAVP](#84dc1b0c-acb7-4269-84c4-00dbabacd78c) provide additional information on validated cryptographic modules and algorithms that can be used in cryptographic key management and establishment." - }, - { - "id": "sc-12_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SC-12 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "sc-12_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "See references in NIST 800-53 documentation." - }, - { - "id": "sc-12_fr_gdn.2", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Must meet applicable Federal Cryptographic Requirements. See References Section of control." - }, - { - "id": "sc-12_fr_gdn.3", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Wildcard certificates may be used internally within the system, but are not permitted for external customer access to the system." - } - ] - }, - { - "id": "sc-12_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-12", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-12_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-12[01]", - "class": "sp800-53a" - } - ], - "prose": "cryptographic keys are established when cryptography is employed within the system in accordance with {{ insert: param, sc-12_odp }};", - "links": [ - { - "href": "#sc-12_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-12_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-12[02]", - "class": "sp800-53a" - } - ], - "prose": "cryptographic keys are managed when cryptography is employed within the system in accordance with {{ insert: param, sc-12_odp }}.", - "links": [ - { - "href": "#sc-12_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-12_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-12_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-12-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing cryptographic key establishment and management\n\nsystem design documentation\n\ncryptographic mechanisms\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-12_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-12-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for cryptographic key establishment and/or management" - } - ] - }, - { - "id": "sc-12_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-12-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing cryptographic key establishment and management" - } - ] - } - ], - "controls": [ - { - "id": "sc-12.1", - "class": "SP800-53-enhancement", - "title": "Availability", - "props": [ - { - "name": "label", - "value": "SC-12(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-12(1)" - }, - { - "name": "label", - "value": "SC-12(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-12.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#sc-12", - "rel": "required" - } - ], - "parts": [ - { - "id": "sc-12.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Maintain availability of information in the event of the loss of cryptographic keys by users." - }, - { - "id": "sc-12.1_gdn", - "name": "guidance", - "prose": "Escrowing of encryption keys is a common practice for ensuring availability in the event of key loss. A forgotten passphrase is an example of losing a cryptographic key." - }, - { - "id": "sc-12.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-12(01)", - "class": "sp800-53a" - } - ], - "prose": "information availability is maintained in the event of the loss of cryptographic keys by users.", - "links": [ - { - "href": "#sc-12.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-12.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-12(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing cryptographic key establishment, management, and recovery\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-12.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-12(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for cryptographic key establishment or management" - } - ] - }, - { - "id": "sc-12.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-12(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing cryptographic key establishment and management" - } - ] - } - ] - } - ] - }, - { - "id": "sc-13", - "class": "SP800-53", - "title": "Cryptographic Protection", - "params": [ - { - "id": "sc-13_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sc-13_prm_1" - }, - { - "name": "label", - "value": "SC-13_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "cryptographic uses", - "guidelines": [ - { - "prose": "cryptographic uses are defined;" - } - ] - }, - { - "id": "sc-13_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sc-13_prm_2" - }, - { - "name": "alt-label", - "value": "types of cryptography for each specified cryptographic use", - "class": "sp800-53" - }, - { - "name": "label", - "value": "SC-13_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "types of cryptography", - "constraints": [ - { - "description": "FIPS-validated or NSA-approved cryptography" - } - ], - "guidelines": [ - { - "prose": "types of cryptography for each specified cryptographic use are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SC-13", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-13" - }, - { - "name": "label", - "value": "SC-13", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-13" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#678e3d6c-150b-4393-aec5-6e3481eb1e00", - "rel": "reference" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-7", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "#au-10", - "rel": "related" - }, - { - "href": "#cm-11", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#ia-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ia-13", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-20", - "rel": "related" - }, - { - "href": "#sc-23", - "rel": "related" - }, - { - "href": "#sc-28", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-40", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-13_smt", - "name": "statement", - "parts": [ - { - "id": "sc-13_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Determine the {{ insert: param, sc-13_odp.01 }} ; and" - }, - { - "id": "sc-13_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Implement the following types of cryptography required for each specified cryptographic use: {{ insert: param, sc-13_odp.02 }}." - } - ] - }, - { - "id": "sc-13_gdn", - "name": "guidance", - "prose": "Cryptography can be employed to support a variety of security solutions, including the protection of classified information and controlled unclassified information, the provision and implementation of digital signatures, and the enforcement of information separation when authorized individuals have the necessary clearances but lack the necessary formal access approvals. Cryptography can also be used to support random number and hash generation. Generally applicable cryptographic standards include FIPS-validated cryptography and NSA-approved cryptography. For example, organizations that need to protect classified information may specify the use of NSA-approved cryptography. Organizations that need to provision and implement digital signatures may specify the use of FIPS-validated cryptography. Cryptography is implemented in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines." - }, - { - "id": "sc-13_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SC-13 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "sc-13_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "This control applies to all use of cryptography. In addition to encryption, this includes functions such as hashing, random number generation, and key generation. Examples include the following:\n\n- Encryption of data\n- Decryption of data\n- Generation of one time passwords (OTPs) for MFA\n- Protocols such as TLS, SSH, and HTTPS\n\nThe requirement for FIPS 140 validation, as well as timelines for acceptance of FIPS 140-2, and 140-3 can be found at the NIST Cryptographic Module Validation Program (CMVP).\n\nhttps://csrc.nist.gov/projects/cryptographic-module-validation-program" - }, - { - "id": "sc-13_fr_gdn.2", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "For NSA-approved cryptography, the National Information Assurance Partnership (NIAP) oversees a national program to evaluate Commercial IT Products for Use in National Security Systems. The NIAP Product Compliant List can be found at the following location:\n\nhttps://www.niap-ccevs.org/Product/index.cfm" - }, - { - "id": "sc-13_fr_gdn.3", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "When leveraging encryption from underlying IaaS/PaaS: While some IaaS/PaaS provide encryption by default, many require encryption to be configured, and enabled by the customer. The CSP has the responsibility to verify encryption is properly configured." - }, - { - "id": "sc-13_fr_gdn.4", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Moving to non-FIPS CM or product is acceptable when:\n\n- FIPS validated version has a known vulnerability\n- Feature with vulnerability is in use\n- Non-FIPS version fixes the vulnerability\n- Non-FIPS version is submitted to NIST for FIPS validation\n- POA\\&M is added to track approval, and deployment when ready" - }, - { - "id": "sc-13_fr_gdn.5", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "At a minimum, this control applies to cryptography in use for the following controls: AU-9(3), CP-9(8), IA-2(6), IA-5(1), MP-5, SC-8(1), and SC-28(1)." - } - ] - }, - { - "id": "sc-13_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-13", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-13_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-13a.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sc-13_odp.01 }} are identified;", - "links": [ - { - "href": "#sc-13_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-13_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-13b.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sc-13_odp.02 }} for each specified cryptographic use (defined in SC-13_ODP\\[01\\]) are implemented.", - "links": [ - { - "href": "#sc-13_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-13_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-13_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-13-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing cryptographic protection\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\ncryptographic module validation certificates\n\nlist of FIPS-validated cryptographic modules\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-13_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-13-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with responsibilities for cryptographic protection" - } - ] - }, - { - "id": "sc-13_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-13-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing cryptographic protection" - } - ] - } - ] - }, - { - "id": "sc-15", - "class": "SP800-53", - "title": "Collaborative Computing Devices and Applications", - "params": [ - { - "id": "sc-15_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sc-15_prm_1" - }, - { - "name": "label", - "value": "SC-15_ODP", - "class": "sp800-53a" - } - ], - "label": "exceptions where remote activation is to be allowed", - "constraints": [ - { - "description": "no exceptions for computing devices" - } - ], - "guidelines": [ - { - "prose": "exceptions where remote activation is to be allowed are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SC-15", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-15" - }, - { - "name": "label", - "value": "SC-15", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-15" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#ac-21", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-42", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-15_smt", - "name": "statement", - "parts": [ - { - "id": "sc-15_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Prohibit remote activation of collaborative computing devices and applications with the following exceptions: {{ insert: param, sc-15_odp }} ; and" - }, - { - "id": "sc-15_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Provide an explicit indication of use to users physically present at the devices." - } - ] - }, - { - "id": "sc-15_gdn", - "name": "guidance", - "prose": "Collaborative computing devices and applications include remote meeting devices and applications, networked white boards, cameras, and microphones. The explicit indication of use includes signals to users when collaborative computing devices and applications are activated." - }, - { - "id": "sc-15_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SC-15 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "sc-15_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "The information system provides disablement (instead of physical disconnect) of collaborative computing devices in a manner that supports ease of use." - } - ] - }, - { - "id": "sc-15_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-15", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-15_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-15a.", - "class": "sp800-53a" - } - ], - "prose": "remote activation of collaborative computing devices and applications is prohibited except {{ insert: param, sc-15_odp }};", - "links": [ - { - "href": "#sc-15_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-15_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-15b.", - "class": "sp800-53a" - } - ], - "prose": "an explicit indication of use is provided to users physically present at the devices.", - "links": [ - { - "href": "#sc-15_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-15_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-15_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-15-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing collaborative computing\n\naccess control policy and procedures\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-15_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-15-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel with responsibilities for managing collaborative computing devices" - } - ] - }, - { - "id": "sc-15_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-15-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing the management of remote activation of collaborative computing devices\n\nmechanisms providing an indication of use of collaborative computing devices" - } - ] - } - ] - }, - { - "id": "sc-17", - "class": "SP800-53", - "title": "Public Key Infrastructure Certificates", - "params": [ - { - "id": "sc-17_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sc-17_prm_1" - }, - { - "name": "label", - "value": "SC-17_ODP", - "class": "sp800-53a" - } - ], - "label": "certificate policy", - "guidelines": [ - { - "prose": "a certificate policy for issuing public key certificates is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SC-17", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-17" - }, - { - "name": "label", - "value": "SC-17", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-17" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#8cb338a4-e493-4177-818f-3af18983ddc5", - "rel": "reference" - }, - { - "href": "#110e26af-4765-49e1-8740-6750f83fcda1", - "rel": "reference" - }, - { - "href": "#e7942589-e267-4a5a-a3d9-f39a7aae81f0", - "rel": "reference" - }, - { - "href": "#8306620b-1920-4d73-8b21-12008528595f", - "rel": "reference" - }, - { - "href": "#737513fa-6758-403f-831d-5ddab5e23cb3", - "rel": "reference" - }, - { - "href": "#au-10", - "rel": "related" - }, - { - "href": "#ia-5", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-17_smt", - "name": "statement", - "parts": [ - { - "id": "sc-17_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Issue public key certificates under an {{ insert: param, sc-17_odp }} or obtain public key certificates from an approved service provider; and" - }, - { - "id": "sc-17_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Include only approved trust anchors in trust stores or certificate stores managed by the organization." - } - ] - }, - { - "id": "sc-17_gdn", - "name": "guidance", - "prose": "Public key infrastructure (PKI) certificates are certificates with visibility external to organizational systems and certificates related to the internal operations of systems, such as application-specific time services. In cryptographic systems with a hierarchical structure, a trust anchor is an authoritative source (i.e., a certificate authority) for which trust is assumed and not derived. A root certificate for a PKI system is an example of a trust anchor. A trust store or certificate store maintains a list of trusted root certificates." - }, - { - "id": "sc-17_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-17", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-17_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-17a.", - "class": "sp800-53a" - } - ], - "prose": "public key certificates are issued under {{ insert: param, sc-17_odp }} , or public key certificates are obtained from an approved service provider;", - "links": [ - { - "href": "#sc-17_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-17_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-17b.", - "class": "sp800-53a" - } - ], - "prose": "only approved trust anchors are included in trust stores or certificate stores managed by the organization.", - "links": [ - { - "href": "#sc-17_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-17_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-17_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-17-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing public key infrastructure certificates\n\npublic key certificate policy or policies\n\npublic key issuing process\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-17_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-17-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for issuing public key certificates\n\nservice providers" - } - ] - }, - { - "id": "sc-17_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-17-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing the management of public key infrastructure certificates" - } - ] - } - ] - }, - { - "id": "sc-18", - "class": "SP800-53", - "title": "Mobile Code", - "props": [ - { - "name": "label", - "value": "SC-18", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-18" - }, - { - "name": "label", - "value": "SC-18", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-18" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#f641309f-a3ad-48be-8c67-2b318648b2f5", - "rel": "reference" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "#cm-2", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-18_smt", - "name": "statement", - "parts": [ - { - "id": "sc-18_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Define acceptable and unacceptable mobile code and mobile code technologies; and" - }, - { - "id": "sc-18_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Authorize, monitor, and control the use of mobile code within the system." - } - ] - }, - { - "id": "sc-18_gdn", - "name": "guidance", - "prose": "Mobile code includes any program, application, or content that can be transmitted across a network (e.g., embedded in an email, document, or website) and executed on a remote system. Decisions regarding the use of mobile code within organizational systems are based on the potential for the code to cause damage to the systems if used maliciously. Mobile code technologies include Java applets, JavaScript, HTML5, WebGL, and VBScript. Usage restrictions and implementation guidelines apply to both the selection and use of mobile code installed on servers and mobile code downloaded and executed on individual workstations and devices, including notebook computers and smart phones. Mobile code policy and procedures address specific actions taken to prevent the development, acquisition, and introduction of unacceptable mobile code within organizational systems, including requiring mobile code to be digitally signed by a trusted source." - }, - { - "id": "sc-18_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-18", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-18_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-18a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-18_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-18a.[01]", - "class": "sp800-53a" - } - ], - "prose": "acceptable mobile code is defined;", - "links": [ - { - "href": "#sc-18_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-18_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-18a.[02]", - "class": "sp800-53a" - } - ], - "prose": "unacceptable mobile code is defined;", - "links": [ - { - "href": "#sc-18_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-18_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-18a.[03]", - "class": "sp800-53a" - } - ], - "prose": "acceptable mobile code technologies are defined;", - "links": [ - { - "href": "#sc-18_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-18_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-18a.[04]", - "class": "sp800-53a" - } - ], - "prose": "unacceptable mobile code technologies are defined;", - "links": [ - { - "href": "#sc-18_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-18_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-18_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-18b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-18_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-18b.[01]", - "class": "sp800-53a" - } - ], - "prose": "the use of mobile code is authorized within the system;", - "links": [ - { - "href": "#sc-18_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-18_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-18b.[02]", - "class": "sp800-53a" - } - ], - "prose": "the use of mobile code is monitored within the system;", - "links": [ - { - "href": "#sc-18_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-18_obj.b-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-18b.[03]", - "class": "sp800-53a" - } - ], - "prose": "the use of mobile code is controlled within the system.", - "links": [ - { - "href": "#sc-18_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-18_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-18_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-18_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-18-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing mobile code\n\nmobile code implementation policy and procedures\n\nlist of acceptable mobile code and mobile code technologies\n\nlist of unacceptable mobile code and mobile technologies\n\nauthorization records\n\nsystem monitoring records\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-18_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-18-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for managing mobile code" - } - ] - }, - { - "id": "sc-18_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-18-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational process for authorizing, monitoring, and controlling mobile code\n\nmechanisms supporting and/or implementing the management of mobile code\n\nmechanisms supporting and/or implementing the monitoring of mobile code" - } - ] - } - ] - }, - { - "id": "sc-20", - "class": "SP800-53", - "title": "Secure Name/Address Resolution Service (Authoritative Source)", - "props": [ - { - "name": "label", - "value": "SC-20", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-20" - }, - { - "name": "label", - "value": "SC-20", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-20" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#678e3d6c-150b-4393-aec5-6e3481eb1e00", - "rel": "reference" - }, - { - "href": "#7c37a38d-21d7-40d8-bc3d-b5e27eac17e1", - "rel": "reference" - }, - { - "href": "#fe209006-bfd4-4033-a79a-9fee1adaf372", - "rel": "reference" - }, - { - "href": "#au-10", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#sc-21", - "rel": "related" - }, - { - "href": "#sc-22", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-20_smt", - "name": "statement", - "parts": [ - { - "id": "sc-20_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Provide additional data origin authentication and integrity verification artifacts along with the authoritative name resolution data the system returns in response to external name/address resolution queries; and" - }, - { - "id": "sc-20_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Provide the means to indicate the security status of child zones and (if the child supports secure resolution services) to enable verification of a chain of trust among parent and child domains, when operating as part of a distributed, hierarchical namespace." - } - ] - }, - { - "id": "sc-20_gdn", - "name": "guidance", - "prose": "Providing authoritative source information enables external clients, including remote Internet clients, to obtain origin authentication and integrity verification assurances for the host/service name to network address resolution information obtained through the service. Systems that provide name and address resolution services include domain name system (DNS) servers. Additional artifacts include DNS Security Extensions (DNSSEC) digital signatures and cryptographic keys. Authoritative data includes DNS resource records. The means for indicating the security status of child zones include the use of delegation signer resource records in the DNS. Systems that use technologies other than the DNS to map between host and service names and network addresses provide other means to assure the authenticity and integrity of response data." - }, - { - "id": "sc-20_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SC-20 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "sc-20_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Control Description should include how DNSSEC is implemented on authoritative DNS servers to supply valid responses to external DNSSEC requests." - }, - { - "id": "sc-20_fr_smt.2", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Authoritative DNS servers must be geolocated in accordance with SA-9 (5)." - }, - { - "id": "sc-20_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "SC-20 applies to use of external authoritative DNS to access a CSO from outside the boundary." - }, - { - "id": "sc-20_fr_gdn.2", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "External authoritative DNS servers may be located outside an authorized environment. Positioning these servers inside an authorized boundary is encouraged." - }, - { - "id": "sc-20_fr_gdn.3", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "CSPs are recommended to self-check DNSSEC configuration through one of many available analyzers such as Sandia National Labs (https://dnsviz.net)" - } - ] - }, - { - "id": "sc-20_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-20", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-20_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-20a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-20_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-20a.[01]", - "class": "sp800-53a" - } - ], - "prose": "additional data origin authentication is provided along with the authoritative name resolution data that the system returns in response to external name/address resolution queries;", - "links": [ - { - "href": "#sc-20_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-20_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-20a.[02]", - "class": "sp800-53a" - } - ], - "prose": "integrity verification artifacts are provided along with the authoritative name resolution data that the system returns in response to external name/address resolution queries;", - "links": [ - { - "href": "#sc-20_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-20_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-20_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-20b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-20_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-20b.[01]", - "class": "sp800-53a" - } - ], - "prose": "the means to indicate the security status of child zones (and if the child supports secure resolution services) is provided when operating as part of a distributed, hierarchical namespace;", - "links": [ - { - "href": "#sc-20_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-20_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-20b.[02]", - "class": "sp800-53a" - } - ], - "prose": "the means to enable verification of a chain of trust among parent and child domains when operating as part of a distributed, hierarchical namespace is provided.", - "links": [ - { - "href": "#sc-20_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-20_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-20_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-20_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-20-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing secure name/address resolution services (authoritative source)\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-20_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-20-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for managing DNS" - } - ] - }, - { - "id": "sc-20_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-20-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing secure name/address resolution services" - } - ] - } - ] - }, - { - "id": "sc-21", - "class": "SP800-53", - "title": "Secure Name/Address Resolution Service (Recursive or Caching Resolver)", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SC-21", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-21" - }, - { - "name": "label", - "value": "SC-21", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-21" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#fe209006-bfd4-4033-a79a-9fee1adaf372", - "rel": "reference" - }, - { - "href": "#sc-20", - "rel": "related" - }, - { - "href": "#sc-22", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-21_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Request and perform data origin authentication and data integrity verification on the name/address resolution responses the system receives from authoritative sources." - }, - { - "id": "sc-21_gdn", - "name": "guidance", - "prose": "Each client of name resolution services either performs this validation on its own or has authenticated channels to trusted validation providers. Systems that provide name and address resolution services for local clients include recursive resolving or caching domain name system (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. Systems that use technologies other than the DNS to map between host and service names and network addresses provide some other means to enable clients to verify the authenticity and integrity of response data." - }, - { - "id": "sc-21_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SC-21 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "sc-21_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Control description should include how DNSSEC is implemented on recursive DNS servers to make DNSSEC requests when resolving DNS requests from internal components to domains external to the CSO boundary.\n\n- If the reply is signed, and fails DNSSEC, do not use the reply\n- If the reply is unsigned:\n - CSP chooses the policy to apply" - }, - { - "id": "sc-21_fr_smt.2", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Internal recursive DNS servers must be located inside an authorized environment. It is typically within the boundary, or leveraged from an underlying IaaS/PaaS." - }, - { - "id": "sc-21_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Accepting an unsigned reply is acceptable" - }, - { - "id": "sc-21_fr_gdn.2", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "SC-21 applies to use of internal recursive DNS to access a domain outside the boundary by a component inside the boundary.\n\n- DNSSEC resolution to access a component inside the boundary is excluded." - } - ] - }, - { - "id": "sc-21_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-21", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-21_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-21[01]", - "class": "sp800-53a" - } - ], - "prose": "data origin authentication is requested for the name/address resolution responses that the system receives from authoritative sources;", - "links": [ - { - "href": "#sc-21_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-21_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-21[02]", - "class": "sp800-53a" - } - ], - "prose": "data origin authentication is performed on the name/address resolution responses that the system receives from authoritative sources;", - "links": [ - { - "href": "#sc-21_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-21_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-21[03]", - "class": "sp800-53a" - } - ], - "prose": "data integrity verification is requested for the name/address resolution responses that the system receives from authoritative sources;", - "links": [ - { - "href": "#sc-21_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-21_obj-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-21[04]", - "class": "sp800-53a" - } - ], - "prose": "data integrity verification is performed on the name/address resolution responses that the system receives from authoritative sources.", - "links": [ - { - "href": "#sc-21_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-21_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-21_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-21-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing secure name/address resolution services (recursive or caching resolver)\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-21_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-21-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for managing DNS" - } - ] - }, - { - "id": "sc-21_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-21-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing data origin authentication and data integrity verification for name/address resolution services" - } - ] - } - ] - }, - { - "id": "sc-22", - "class": "SP800-53", - "title": "Architecture and Provisioning for Name/Address Resolution Service", - "props": [ - { - "name": "label", - "value": "SC-22", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-22" - }, - { - "name": "label", - "value": "SC-22", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-22" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#fe209006-bfd4-4033-a79a-9fee1adaf372", - "rel": "reference" - }, - { - "href": "#sc-2", - "rel": "related" - }, - { - "href": "#sc-20", - "rel": "related" - }, - { - "href": "#sc-21", - "rel": "related" - }, - { - "href": "#sc-24", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-22_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Ensure the systems that collectively provide name/address resolution service for an organization are fault-tolerant and implement internal and external role separation." - }, - { - "id": "sc-22_gdn", - "name": "guidance", - "prose": "Systems that provide name and address resolution services include domain name system (DNS) servers. To eliminate single points of failure in systems and enhance redundancy, organizations employ at least two authoritative domain name system servers—one configured as the primary server and the other configured as the secondary server. Additionally, organizations typically deploy the servers in two geographically separated network subnetworks (i.e., not located in the same physical facility). For role separation, DNS servers with internal roles only process name and address resolution requests from within organizations (i.e., from internal clients). DNS servers with external roles only process name and address resolution information requests from clients external to organizations (i.e., on external networks, including the Internet). Organizations specify clients that can access authoritative DNS servers in certain roles (e.g., by address ranges and explicit lists)." - }, - { - "id": "sc-22_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-22", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-22_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-22[01]", - "class": "sp800-53a" - } - ], - "prose": "the systems that collectively provide name/address resolution services for an organization are fault-tolerant;", - "links": [ - { - "href": "#sc-22_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-22_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-22[02]", - "class": "sp800-53a" - } - ], - "prose": "the systems that collectively provide name/address resolution services for an organization implement internal role separation;", - "links": [ - { - "href": "#sc-22_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-22_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-22[03]", - "class": "sp800-53a" - } - ], - "prose": "the systems that collectively provide name/address resolution services for an organization implement external role separation.", - "links": [ - { - "href": "#sc-22_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-22_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-22_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-22-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing architecture and provisioning for name/address resolution services\n\naccess control policy and procedures\n\nsystem design documentation\n\nassessment results from independent testing organizations\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-22_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-22-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel with responsibilities for managing DNS" - } - ] - }, - { - "id": "sc-22_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-22-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing name/address resolution services for fault tolerance and role separation" - } - ] - } - ] - }, - { - "id": "sc-23", - "class": "SP800-53", - "title": "Session Authenticity", - "props": [ - { - "name": "label", - "value": "SC-23", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-23" - }, - { - "name": "label", - "value": "SC-23", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-23" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#7537638e-2837-407d-844b-40fb3fafdd99", - "rel": "reference" - }, - { - "href": "#d4d7c760-2907-403b-8b2a-767ca5370ecd", - "rel": "reference" - }, - { - "href": "#a6b9907a-2a14-4bb4-a142-d4c73026a8b4", - "rel": "reference" - }, - { - "href": "#6bc4d137-aece-42a8-8081-9ecb1ebe9fb4", - "rel": "reference" - }, - { - "href": "#au-10", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-10", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-11", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-23_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Protect the authenticity of communications sessions." - }, - { - "id": "sc-23_gdn", - "name": "guidance", - "prose": "Protecting session authenticity addresses communications protection at the session level, not at the packet level. Such protection establishes grounds for confidence at both ends of communications sessions in the ongoing identities of other parties and the validity of transmitted information. Authenticity protection includes protecting against \"man-in-the-middle\" attacks, session hijacking, and the insertion of false information into sessions." - }, - { - "id": "sc-23_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-23", - "class": "sp800-53a" - } - ], - "prose": "the authenticity of communication sessions is protected.", - "links": [ - { - "href": "#sc-23_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-23_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-23-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing session authenticity\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-23_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-23-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "sc-23_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-23-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing session authenticity" - } - ] - } - ] - }, - { - "id": "sc-24", - "class": "SP800-53", - "title": "Fail in Known State", - "params": [ - { - "id": "sc-24_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sc-24_prm_3" - }, - { - "name": "alt-label", - "value": "list of organization-defined types of system failures on organization-defined system components", - "class": "sp800-53" - }, - { - "name": "label", - "value": "SC-24_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "types of system failures on system components", - "guidelines": [ - { - "prose": "types of system failures for which the system components fail to a known state are defined;" - } - ] - }, - { - "id": "sc-24_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sc-24_prm_1" - }, - { - "name": "label", - "value": "SC-24_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "known system state", - "guidelines": [ - { - "prose": "known system state to which system components fail in the event of a system failure is defined;" - } - ] - }, - { - "id": "sc-24_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "sc-24_prm_2" - }, - { - "name": "label", - "value": "SC-24_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "system state information", - "guidelines": [ - { - "prose": "system state information to be preserved in the event of a system failure is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SC-24", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-24" - }, - { - "name": "label", - "value": "SC-24", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-24" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#cp-4", - "rel": "related" - }, - { - "href": "#cp-10", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#cp-12", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-22", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#si-13", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-24_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Fail to a {{ insert: param, sc-24_odp.02 }} for the following failures on the indicated components while preserving {{ insert: param, sc-24_odp.03 }} in failure: {{ insert: param, sc-24_odp.01 }}." - }, - { - "id": "sc-24_gdn", - "name": "guidance", - "prose": "Failure in a known state addresses security concerns in accordance with the mission and business needs of organizations. Failure in a known state prevents the loss of confidentiality, integrity, or availability of information in the event of failures of organizational systems or system components. Failure in a known safe state helps to prevent systems from failing to a state that may cause injury to individuals or destruction to property. Preserving system state information facilitates system restart and return to the operational mode with less disruption of mission and business processes." - }, - { - "id": "sc-24_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-24", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sc-24_odp.01 }} fail to a {{ insert: param, sc-24_odp.02 }} while preserving {{ insert: param, sc-24_odp.03 }} in failure.", - "links": [ - { - "href": "#sc-24_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-24_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-24-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing system failure to known state\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of failures requiring system to fail in a known state\n\nstate information to be preserved in system failure\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-24_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-24-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "id": "sc-24_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-24-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing the fail in known state capability\n\nmechanisms preserving system state information in the event of a system failure" - } - ] - } - ] - }, - { - "id": "sc-28", - "class": "SP800-53", - "title": "Protection of Information at Rest", - "params": [ - { - "id": "sc-28_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sc-28_prm_1" - }, - { - "name": "label", - "value": "SC-28_ODP[01]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "confidentiality AND integrity" - } - ] - }, - { - "id": "sc-28_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sc-28_prm_2" - }, - { - "name": "label", - "value": "SC-28_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "information at rest", - "guidelines": [ - { - "prose": "information at rest requiring protection is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SC-28", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-28" - }, - { - "name": "label", - "value": "SC-28", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-28" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#20957dbb-6a1e-40a2-b38a-66f67d33ac2e", - "rel": "reference" - }, - { - "href": "#0d083d8a-5cc6-46f1-8d79-3081d42bcb75", - "rel": "reference" - }, - { - "href": "#eef62b16-c796-4554-955c-505824135b8a", - "rel": "reference" - }, - { - "href": "#110e26af-4765-49e1-8740-6750f83fcda1", - "rel": "reference" - }, - { - "href": "#e7942589-e267-4a5a-a3d9-f39a7aae81f0", - "rel": "reference" - }, - { - "href": "#8306620b-1920-4d73-8b21-12008528595f", - "rel": "reference" - }, - { - "href": "#22f2d4f0-4365-4e88-a30d-275c1f5473ea", - "rel": "reference" - }, - { - "href": "#0f66be67-85e7-4ca6-bd19-39453e9f4394", - "rel": "reference" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cp-9", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#mp-5", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-34", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - }, - { - "href": "#si-16", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-28_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Protect the {{ insert: param, sc-28_odp.01 }} of the following information at rest: {{ insert: param, sc-28_odp.02 }}." - }, - { - "id": "sc-28_gdn", - "name": "guidance", - "prose": "Information at rest refers to the state of information when it is not in process or in transit and is located on system components. Such components include internal or external hard disk drives, storage area network devices, or databases. However, the focus of protecting information at rest is not on the type of storage device or frequency of access but rather on the state of the information. Information at rest addresses the confidentiality and integrity of information and covers user information and system information. System-related information that requires protection includes configurations or rule sets for firewalls, intrusion detection and prevention systems, filtering routers, and authentication information. Organizations may employ different mechanisms to achieve confidentiality and integrity protections, including the use of cryptographic mechanisms and file share scanning. Integrity protection can be achieved, for example, by implementing write-once-read-many (WORM) technologies. When adequate protection of information at rest cannot otherwise be achieved, organizations may employ other controls, including frequent scanning to identify malicious code at rest and secure offline storage in lieu of online storage." - }, - { - "id": "sc-28_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SC-28 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "sc-28_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "The organization supports the capability to use cryptographic mechanisms to protect information at rest." - }, - { - "id": "sc-28_fr_gdn.2", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "When leveraging encryption from underlying IaaS/PaaS: While some IaaS/PaaS services provide encryption by default, many require encryption to be configured, and enabled by the customer. The CSP has the responsibility to verify encryption is properly configured." - }, - { - "id": "sc-28_fr_gdn.3", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Note that this enhancement requires the use of cryptography in accordance with SC-13." - } - ] - }, - { - "id": "sc-28_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-28", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sc-28_odp.01 }} of {{ insert: param, sc-28_odp.02 }} is/are protected.", - "links": [ - { - "href": "#sc-28_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-28_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-28-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing the protection of information at rest\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\ncryptographic mechanisms and associated configuration documentation\n\nlist of information at rest requiring confidentiality and integrity protections\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-28_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-28-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "id": "sc-28_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-28-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing confidentiality and integrity protections for information at rest" - } - ] - } - ], - "controls": [ - { - "id": "sc-28.1", - "class": "SP800-53-enhancement", - "title": "Cryptographic Protection", - "params": [ - { - "id": "sc-28.01_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sc-28.1_prm_2" - }, - { - "name": "label", - "value": "SC-28(01)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "information", - "guidelines": [ - { - "prose": "information requiring cryptographic protection is defined;" - } - ] - }, - { - "id": "sc-28.01_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sc-28.1_prm_1" - }, - { - "name": "label", - "value": "SC-28(01)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "system components or media", - "constraints": [ - { - "description": "all information system components storing Federal data or system data that must be protected at the High or Moderate impact levels" - } - ], - "guidelines": [ - { - "prose": "system components or media requiring cryptographic protection is/are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SC-28(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-28(1)" - }, - { - "name": "label", - "value": "SC-28(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-28.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#sc-28", - "rel": "required" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-28.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of the following information at rest on {{ insert: param, sc-28.01_odp.02 }}: {{ insert: param, sc-28.01_odp.01 }}." - }, - { - "id": "sc-28.1_gdn", - "name": "guidance", - "prose": "The selection of cryptographic mechanisms is based on the need to protect the confidentiality and integrity of organizational information. The strength of mechanism is commensurate with the security category or classification of the information. Organizations have the flexibility to encrypt information on system components or media or encrypt data structures, including files, records, or fields." - }, - { - "id": "sc-28.1_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SC-28 (1) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "sc-28.1_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Organizations should select a mode of protection that is targeted towards the relevant threat scenarios.\n\nExamples:\n\nA. Organizations may apply full disk encryption (FDE) to a mobile device where the primary threat is loss of the device while storage is locked.\n\nB. For a database application housing data for a single customer, encryption at the file system level would often provide more protection than FDE against the more likely threat of an intruder on the operating system accessing the storage.\n\nC. For a database application housing data for multiple customers, encryption with unique keys for each customer at the database record level may be more appropriate." - } - ] - }, - { - "id": "sc-28.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-28(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-28.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-28(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "cryptographic mechanisms are implemented to prevent unauthorized disclosure of {{ insert: param, sc-28.01_odp.01 }} at rest on {{ insert: param, sc-28.01_odp.02 }};", - "links": [ - { - "href": "#sc-28.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-28.1_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-28(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "cryptographic mechanisms are implemented to prevent unauthorized modification of {{ insert: param, sc-28.01_odp.01 }} at rest on {{ insert: param, sc-28.01_odp.02 }}.", - "links": [ - { - "href": "#sc-28.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-28.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-28.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-28(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing the protection of information at rest\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\ncryptographic mechanisms and associated configuration documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-28.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-28(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer" - } - ] - }, - { - "id": "sc-28.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-28(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Cryptographic mechanisms implementing confidentiality and integrity protections for information at rest" - } - ] - } - ] - } - ] - }, - { - "id": "sc-39", - "class": "SP800-53", - "title": "Process Isolation", - "props": [ - { - "name": "label", - "value": "SC-39", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-39" - }, - { - "name": "label", - "value": "SC-39", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-39" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-6", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ac-25", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sc-2", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - }, - { - "href": "#si-16", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-39_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Maintain a separate execution domain for each executing system process." - }, - { - "id": "sc-39_gdn", - "name": "guidance", - "prose": "Systems can maintain separate execution domains for each executing process by assigning each process a separate address space. Each system process has a distinct address space so that communication between processes is performed in a manner controlled through the security functions, and one process cannot modify the executing code of another process. Maintaining separate execution domains for executing processes can be achieved, for example, by implementing separate address spaces. Process isolation technologies, including sandboxing or virtualization, logically separate software and firmware from other software, firmware, and data. Process isolation helps limit the access of potentially untrusted software to other system resources. The capability to maintain separate execution domains is available in commercial operating systems that employ multi-state processor technologies." - }, - { - "id": "sc-39_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-39", - "class": "sp800-53a" - } - ], - "prose": "a separate execution domain is maintained for each executing system process.", - "links": [ - { - "href": "#sc-39_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-39_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-39-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System design documentation\n\nsystem architecture\n\nindependent verification and validation documentation\n\ntesting and evaluation documentation\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-39_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-39-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System developers/integrators\n\nsystem security architect" - } - ] - }, - { - "id": "sc-39_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-39-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing separate execution domains for each executing process" - } - ] - } - ] - }, - { - "id": "sc-45", - "class": "SP800-53", - "title": "System Time Synchronization", - "props": [ - { - "name": "label", - "value": "SC-45", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-45" - }, - { - "name": "label", - "value": "SC-45", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-45" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#e4d37285-1e79-4029-8b6a-42df39cace30", - "rel": "reference" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#au-8", - "rel": "related" - }, - { - "href": "#ia-2", - "rel": "related" - }, - { - "href": "#ia-8", - "rel": "related" - } - ], - "parts": [ - { - "id": "sc-45_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Synchronize system clocks within and between systems and system components." - }, - { - "id": "sc-45_gdn", - "name": "guidance", - "prose": "Time synchronization of system clocks is essential for the correct execution of many system services, including identification and authentication processes that involve certificates and time-of-day restrictions as part of access control. Denial of service or failure to deny expired credentials may result without properly synchronized clocks within and between systems and system components. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. The granularity of time measurements refers to the degree of synchronization between system clocks and reference clocks, such as clocks synchronizing within hundreds of milliseconds or tens of milliseconds. Organizations may define different time granularities for system components. Time service can be critical to other security capabilities—such as access control and identification and authentication—depending on the nature of the mechanisms used to support the capabilities." - }, - { - "id": "sc-45_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-45", - "class": "sp800-53a" - } - ], - "prose": "system clocks are synchronized within and between systems and system components.", - "links": [ - { - "href": "#sc-45_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-45_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-45-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing time synchronization\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-45_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-45-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the system" - } - ] - }, - { - "id": "sc-45_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-45-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing system time synchronization" - } - ] - } - ], - "controls": [ - { - "id": "sc-45.1", - "class": "SP800-53-enhancement", - "title": "Synchronization with Authoritative Time Source", - "params": [ - { - "id": "sc-45.01_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sc-45.1_prm_1" - }, - { - "name": "label", - "value": "SC-45(01)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "At least hourly" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to compare the internal system clocks with the authoritative time source is defined;" - } - ] - }, - { - "id": "sc-45.01_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sc-45.1_prm_2" - }, - { - "name": "label", - "value": "SC-45(01)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "authoritative time source", - "constraints": [ - { - "description": "http://tf.nist.gov/tf-cgi/servers.cgi" - } - ], - "guidelines": [ - { - "prose": "the authoritative time source to which internal system clocks are to be compared is defined;" - } - ] - }, - { - "id": "sc-45.01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "sc-45.1_prm_3" - }, - { - "name": "label", - "value": "SC-45(01)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "any difference" - } - ], - "guidelines": [ - { - "prose": "the time period to compare the internal system clocks with the authoritative time source is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SC-45(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SC-45(1)" - }, - { - "name": "label", - "value": "SC-45(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sc-45.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#sc-45", - "rel": "required" - } - ], - "parts": [ - { - "id": "sc-45.1_smt", - "name": "statement", - "parts": [ - { - "id": "sc-45.1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Compare the internal system clocks {{ insert: param, sc-45.01_odp.01 }} with {{ insert: param, sc-45.01_odp.02 }} ; and" - }, - { - "id": "sc-45.1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Synchronize the internal system clocks to the authoritative time source when the time difference is greater than {{ insert: param, sc-45.01_odp.03 }}." - } - ] - }, - { - "id": "sc-45.1_gdn", - "name": "guidance", - "prose": "Synchronization of internal system clocks with an authoritative source provides uniformity of time stamps for systems with multiple system clocks and systems connected over a network." - }, - { - "id": "sc-45.1_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SC-45(1) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "sc-45.1_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "The service provider selects primary and secondary time servers used by the NIST Internet time service. The secondary server is selected from a different geographic region than the primary server." - }, - { - "id": "sc-45.1_fr_smt.2", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "The service provider synchronizes the system clocks of network computers that run operating systems other than Windows to the Windows Server Domain Controller emulator or to the same time source for that server." - }, - { - "id": "sc-45.1_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "Synchronization of system clocks improves the accuracy of log analysis." - } - ] - }, - { - "id": "sc-45.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SC-45(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sc-45.1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-45(01)(a)", - "class": "sp800-53a" - } - ], - "prose": "the internal system clocks are compared {{ insert: param, sc-45.01_odp.01 }} with {{ insert: param, sc-45.01_odp.02 }};", - "links": [ - { - "href": "#sc-45.1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-45.1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SC-45(01)(b)", - "class": "sp800-53a" - } - ], - "prose": "the internal system clocks are synchronized with the authoritative time source when the time difference is greater than {{ insert: param, sc-45.01_odp.03 }}.", - "links": [ - { - "href": "#sc-45.1_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sc-45.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sc-45.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SC-45(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and communications protection policy\n\nprocedures addressing time synchronization\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sc-45.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SC-45(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the system" - } - ] - }, - { - "id": "sc-45.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SC-45(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing system time synchronization" - } - ] - } - ] - } - ] - } - ] - }, - { - "id": "si", - "class": "family", - "title": "System and Information Integrity", - "controls": [ - { - "id": "si-1", - "class": "SP800-53", - "title": "Policy and Procedures", - "params": [ - { - "id": "si-1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-01_odp.02" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "si-01_odp.01", - "props": [ - { - "name": "label", - "value": "SI-01_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the system and information integrity policy is to be disseminated is/are defined;" - } - ] - }, - { - "id": "si-01_odp.02", - "props": [ - { - "name": "label", - "value": "SI-01_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom the system and information integrity procedures are to be disseminated is/are defined;" - } - ] - }, - { - "id": "si-01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "si-1_prm_2" - }, - { - "name": "label", - "value": "SI-01_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "organization-level", - "mission/business process-level", - "system-level" - ] - } - }, - { - "id": "si-01_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "si-1_prm_3" - }, - { - "name": "label", - "value": "SI-01_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "official", - "guidelines": [ - { - "prose": "an official to manage the system and information integrity policy and procedures is defined;" - } - ] - }, - { - "id": "si-01_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "si-1_prm_4" - }, - { - "name": "label", - "value": "SI-01_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current system and information integrity policy is reviewed and updated is defined;" - } - ] - }, - { - "id": "si-01_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "si-1_prm_5" - }, - { - "name": "label", - "value": "SI-01_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that would require the current system and information integrity policy to be reviewed and updated are defined;" - } - ] - }, - { - "id": "si-01_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "si-1_prm_6" - }, - { - "name": "label", - "value": "SI-01_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current system and information integrity procedures are reviewed and updated is defined;" - } - ] - }, - { - "id": "si-01_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "si-1_prm_7" - }, - { - "name": "label", - "value": "SI-01_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "events", - "constraints": [ - { - "description": "significant changes" - } - ], - "guidelines": [ - { - "prose": "events that would require the system and information integrity procedures to be reviewed and updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-01", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-1" - }, - { - "name": "label", - "value": "SI-01", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#c7ac44e8-10db-4b64-b2b9-9e32ec1efed0", - "rel": "reference" - }, - { - "href": "#4c0ec2ee-a0d6-428a-9043-4504bc3ade6f", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-1_smt", - "name": "statement", - "parts": [ - { - "id": "si-1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, a policy that addresses System and Information Integrity MUST be associated with SI-1 part a.", - "class": "policy" - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, at least one procedure that addresses System and Information Integrity MUST be associated with SI-1 part a.", - "class": "procedure" - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, document, and disseminate to {{ insert: param, si-1_prm_1 }}:", - "parts": [ - { - "id": "si-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, si-01_odp.03 }} system and information integrity policy that:", - "parts": [ - { - "id": "si-1_smt.a.1.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "si-1_smt.a.1.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and" - } - ] - }, - { - "id": "si-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the system and information integrity policy and the associated system and information integrity controls;" - } - ] - }, - { - "id": "si-1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Designate an {{ insert: param, si-01_odp.04 }} to manage the development, documentation, and dissemination of the system and information integrity policy and procedures; and" - }, - { - "id": "si-1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the current system and information integrity:", - "parts": [ - { - "id": "si-1_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Policy {{ insert: param, si-01_odp.05 }} and following {{ insert: param, si-01_odp.06 }} ; and" - }, - { - "id": "si-1_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures {{ insert: param, si-01_odp.07 }} and following {{ insert: param, si-01_odp.08 }}." - } - ] - } - ] - }, - { - "id": "si-1_gdn", - "name": "guidance", - "prose": "System and information integrity policy and procedures address the controls in the SI family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of system and information integrity policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to system and information integrity policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure." - }, - { - "id": "si-1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-01a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-01a.[01]", - "class": "sp800-53a" - } - ], - "prose": "a system and information integrity policy is developed and documented;", - "links": [ - { - "href": "#si-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-01a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the system and information integrity policy is disseminated to {{ insert: param, si-01_odp.01 }};", - "links": [ - { - "href": "#si-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-1_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-01a.[03]", - "class": "sp800-53a" - } - ], - "prose": "system and information integrity procedures to facilitate the implementation of the system and information integrity policy and associated system and information integrity controls are developed and documented;", - "links": [ - { - "href": "#si-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-1_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-01a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the system and information integrity procedures are disseminated to {{ insert: param, si-01_odp.02 }};", - "links": [ - { - "href": "#si-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-1_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-01a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-1_obj.a.1.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-01a.01(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-1_obj.a.1.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-01a.01(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, si-01_odp.03 }} system and information integrity policy addresses purpose;", - "links": [ - { - "href": "#si-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-1_obj.a.1.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-01a.01(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, si-01_odp.03 }} system and information integrity policy addresses scope;", - "links": [ - { - "href": "#si-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-1_obj.a.1.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-01a.01(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, si-01_odp.03 }} system and information integrity policy addresses roles;", - "links": [ - { - "href": "#si-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-1_obj.a.1.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-01a.01(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, si-01_odp.03 }} system and information integrity policy addresses responsibilities;", - "links": [ - { - "href": "#si-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-1_obj.a.1.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-01a.01(a)[05]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, si-01_odp.03 }} system and information integrity policy addresses management commitment;", - "links": [ - { - "href": "#si-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-1_obj.a.1.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-01a.01(a)[06]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, si-01_odp.03 }} system and information integrity policy addresses coordination among organizational entities;", - "links": [ - { - "href": "#si-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-1_obj.a.1.a-7", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-01a.01(a)[07]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, si-01_odp.03 }} system and information integrity policy addresses compliance;", - "links": [ - { - "href": "#si-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-1_obj.a.1.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-01a.01(b)", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, si-01_odp.03 }} system and information integrity policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines;", - "links": [ - { - "href": "#si-1_smt.a.1.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-1_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-01b.", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, si-01_odp.04 }} is designated to manage the development, documentation, and dissemination of the system and information integrity policy and procedures;", - "links": [ - { - "href": "#si-1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-01c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-1_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-01c.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-1_obj.c.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-01c.01[01]", - "class": "sp800-53a" - } - ], - "prose": "the current system and information integrity policy is reviewed and updated {{ insert: param, si-01_odp.05 }};", - "links": [ - { - "href": "#si-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-1_obj.c.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-01c.01[02]", - "class": "sp800-53a" - } - ], - "prose": "the current system and information integrity policy is reviewed and updated following {{ insert: param, si-01_odp.06 }};", - "links": [ - { - "href": "#si-1_smt.c.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-1_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-01c.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-1_obj.c.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-01c.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the current system and information integrity procedures are reviewed and updated {{ insert: param, si-01_odp.07 }};", - "links": [ - { - "href": "#si-1_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-1_obj.c.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-01c.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the current system and information integrity procedures are reviewed and updated following {{ insert: param, si-01_odp.08 }}.", - "links": [ - { - "href": "#si-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-1_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-01-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-01-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and information integrity responsibilities\n\norganizational personnel with information security and privacy responsibilities" - } - ] - } - ] - }, - { - "id": "si-2", - "class": "SP800-53", - "title": "Flaw Remediation", - "params": [ - { - "id": "si-02_odp", - "props": [ - { - "name": "alt-identifier", - "value": "si-2_prm_1" - }, - { - "name": "label", - "value": "SI-02_ODP", - "class": "sp800-53a" - } - ], - "label": "time period", - "constraints": [ - { - "description": "within thirty (30) days of release of updates" - } - ], - "guidelines": [ - { - "prose": "time period within which to install security-relevant software updates after the release of the updates is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-02", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-2" - }, - { - "name": "label", - "value": "SI-02", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#678e3d6c-150b-4393-aec5-6e3481eb1e00", - "rel": "reference" - }, - { - "href": "#7c37a38d-21d7-40d8-bc3d-b5e27eac17e1", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#155f941a-cba9-4afd-9ca6-5d040d697ba9", - "rel": "reference" - }, - { - "href": "#20db4e66-e257-450c-b2e4-2bb9a62a2c88", - "rel": "reference" - }, - { - "href": "#aa5d04e0-6090-4e17-84d4-b9963d55fc2c", - "rel": "reference" - }, - { - "href": "#ca-5", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#ma-2", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - }, - { - "href": "#sa-11", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-5", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - }, - { - "href": "#si-11", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-2_smt", - "name": "statement", - "parts": [ - { - "id": "si-2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Identify, report, and correct system flaws;" - }, - { - "id": "si-2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Test software and firmware updates related to flaw remediation for effectiveness and potential side effects before installation;" - }, - { - "id": "si-2_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Install security-relevant software and firmware updates within {{ insert: param, si-02_odp }} of the release of the updates; and" - }, - { - "id": "si-2_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Incorporate flaw remediation into the organizational configuration management process." - } - ] - }, - { - "id": "si-2_gdn", - "name": "guidance", - "prose": "The need to remediate system flaws applies to all types of software and firmware. Organizations identify systems affected by software flaws, including potential vulnerabilities resulting from those flaws, and report this information to designated organizational personnel with information security and privacy responsibilities. Security-relevant updates include patches, service packs, and malicious code signatures. Organizations also address flaws discovered during assessments, continuous monitoring, incident response activities, and system error handling. By incorporating flaw remediation into configuration management processes, required remediation actions can be tracked and verified.\n\nOrganization-defined time periods for updating security-relevant software and firmware may vary based on a variety of risk factors, including the security category of the system, the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw), the organizational risk tolerance, the mission supported by the system, or the threat environment. Some types of flaw remediation may require more testing than other types. Organizations determine the type of testing needed for the specific type of flaw remediation activity under consideration and the types of changes that are to be configuration-managed. In some situations, organizations may determine that the testing of software or firmware updates is not necessary or practical, such as when implementing simple malicious code signature updates. In testing decisions, organizations consider whether security-relevant software or firmware updates are obtained from authorized sources with appropriate digital signatures." - }, - { - "id": "si-2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-02a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-2_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-02a.[01]", - "class": "sp800-53a" - } - ], - "prose": "system flaws are identified;", - "links": [ - { - "href": "#si-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-2_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-02a.[02]", - "class": "sp800-53a" - } - ], - "prose": "system flaws are reported;", - "links": [ - { - "href": "#si-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-2_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-02a.[03]", - "class": "sp800-53a" - } - ], - "prose": "system flaws are corrected;", - "links": [ - { - "href": "#si-2_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-02b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-2_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-02b.[01]", - "class": "sp800-53a" - } - ], - "prose": "software updates related to flaw remediation are tested for effectiveness before installation;", - "links": [ - { - "href": "#si-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-2_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-02b.[02]", - "class": "sp800-53a" - } - ], - "prose": "software updates related to flaw remediation are tested for potential side effects before installation;", - "links": [ - { - "href": "#si-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-2_obj.b-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-02b.[03]", - "class": "sp800-53a" - } - ], - "prose": "firmware updates related to flaw remediation are tested for effectiveness before installation;", - "links": [ - { - "href": "#si-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-2_obj.b-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-02b.[04]", - "class": "sp800-53a" - } - ], - "prose": "firmware updates related to flaw remediation are tested for potential side effects before installation;", - "links": [ - { - "href": "#si-2_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-2_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-02c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-2_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-02c.[01]", - "class": "sp800-53a" - } - ], - "prose": "security-relevant software updates are installed within {{ insert: param, si-02_odp }} of the release of the updates;", - "links": [ - { - "href": "#si-2_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-2_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-02c.[02]", - "class": "sp800-53a" - } - ], - "prose": "security-relevant firmware updates are installed within {{ insert: param, si-02_odp }} of the release of the updates;", - "links": [ - { - "href": "#si-2_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-2_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-2_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-02d.", - "class": "sp800-53a" - } - ], - "prose": "flaw remediation is incorporated into the organizational configuration management process.", - "links": [ - { - "href": "#si-2_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-02-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing flaw remediation\n\nprocedures addressing configuration management\n\nlist of flaws and vulnerabilities potentially affecting the system\n\nlist of recent security flaw remediation actions performed on the system (e.g., list of installed patches, service packs, hot fixes, and other software updates to correct system flaws)\n\ntest results from the installation of software and firmware updates to correct system flaws\n\ninstallation/change control records for security-relevant software and firmware updates\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-02-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security and privacy responsibilities\n\norganizational personnel responsible for installing, configuring, and/or maintaining the system\n\norganizational personnel responsible for flaw remediation\n\norganizational personnel with configuration management responsibilities" - } - ] - }, - { - "id": "si-2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-02-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for identifying, reporting, and correcting system flaws\n\norganizational process for installing software and firmware updates\n\nmechanisms supporting and/or implementing the reporting and correcting of system flaws\n\nmechanisms supporting and/or implementing testing software and firmware updates" - } - ] - } - ], - "controls": [ - { - "id": "si-2.2", - "class": "SP800-53-enhancement", - "title": "Automated Flaw Remediation Status", - "params": [ - { - "id": "si-02.02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "si-2.2_prm_1" - }, - { - "name": "label", - "value": "SI-02(02)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms to determine if applicable security-relevant software and firmware updates are installed on system components are defined;" - } - ] - }, - { - "id": "si-02.02_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "si-2.2_prm_2" - }, - { - "name": "label", - "value": "SI-02(02)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least monthly" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to determine if applicable security-relevant software and firmware updates are installed on system components is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-02(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-2(2)" - }, - { - "name": "label", - "value": "SI-02(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-02.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#si-2", - "rel": "required" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-2.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Determine if system components have applicable security-relevant software and firmware updates installed using {{ insert: param, si-02.02_odp.01 }} {{ insert: param, si-02.02_odp.02 }}." - }, - { - "id": "si-2.2_gdn", - "name": "guidance", - "prose": "Automated mechanisms can track and determine the status of known flaws for system components." - }, - { - "id": "si-2.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-02(02)", - "class": "sp800-53a" - } - ], - "prose": "system components have applicable security-relevant software and firmware updates installed {{ insert: param, si-02.02_odp.02 }} using {{ insert: param, si-02.02_odp.01 }}.", - "links": [ - { - "href": "#si-2.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-2.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-02(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing flaw remediation\n\nautomated mechanisms supporting centralized management of flaw remediation\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-2.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-02(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the system\n\norganizational personnel responsible for flaw remediation" - } - ] - }, - { - "id": "si-2.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-02(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Automated mechanisms used to determine the state of system components with regard to flaw remediation" - } - ] - } - ] - }, - { - "id": "si-2.3", - "class": "SP800-53-enhancement", - "title": "Time to Remediate Flaws and Benchmarks for Corrective Actions", - "params": [ - { - "id": "si-02.03_odp", - "props": [ - { - "name": "alt-identifier", - "value": "si-2.3_prm_1" - }, - { - "name": "label", - "value": "SI-02(03)_ODP", - "class": "sp800-53a" - } - ], - "label": "benchmarks", - "guidelines": [ - { - "prose": "the benchmarks for taking corrective actions are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-02(03)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-2(3)" - }, - { - "name": "label", - "value": "SI-02(03)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-02.03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#si-2", - "rel": "required" - } - ], - "parts": [ - { - "id": "si-2.3_smt", - "name": "statement", - "parts": [ - { - "id": "si-2.3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Measure the time between flaw identification and flaw remediation; and" - }, - { - "id": "si-2.3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Establish the following benchmarks for taking corrective actions: {{ insert: param, si-02.03_odp }}." - } - ] - }, - { - "id": "si-2.3_gdn", - "name": "guidance", - "prose": "Organizations determine the time it takes on average to correct system flaws after such flaws have been identified and subsequently establish organizational benchmarks (i.e., time frames) for taking corrective actions. Benchmarks can be established by the type of flaw or the severity of the potential vulnerability if the flaw can be exploited." - }, - { - "id": "si-2.3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-02(03)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-2.3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-02(03)(a)", - "class": "sp800-53a" - } - ], - "prose": "the time between flaw identification and flaw remediation is measured;", - "links": [ - { - "href": "#si-2.3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-2.3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-02(03)(b)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-02.03_odp }} for taking corrective actions have been established.", - "links": [ - { - "href": "#si-2.3_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-2.3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-2.3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-02(03)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing flaw remediation\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of benchmarks for taking corrective action on identified flaws\n\nrecords that provide timestamps of flaw identification and subsequent flaw remediation activities\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-2.3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-02(03)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the system\n\norganizational personnel responsible for flaw remediation" - } - ] - }, - { - "id": "si-2.3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-02(03)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for identifying, reporting, and correcting system flaws\n\nmechanisms used to measure the time between flaw identification and flaw remediation" - } - ] - } - ] - } - ] - }, - { - "id": "si-3", - "class": "SP800-53", - "title": "Malicious Code Protection", - "params": [ - { - "id": "si-03_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "si-3_prm_1" - }, - { - "name": "label", - "value": "SI-03_ODP[01]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "signature based and non-signature based" - } - ] - }, - { - "id": "si-03_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "si-3_prm_2" - }, - { - "name": "label", - "value": "SI-03_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least weekly" - } - ], - "guidelines": [ - { - "prose": "the frequency at which malicious code protection mechanisms perform scans is defined;" - } - ] - }, - { - "id": "si-03_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "si-3_prm_3" - }, - { - "name": "label", - "value": "SI-03_ODP[03]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "to include endpoints and network entry and exit points" - } - ] - }, - { - "id": "si-03_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "si-3_prm_4" - }, - { - "name": "label", - "value": "SI-03_ODP[04]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "to include blocking and quarantining malicious code" - } - ] - }, - { - "id": "si-03_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "si-3_prm_5" - }, - { - "name": "label", - "value": "SI-03_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "action", - "guidelines": [ - { - "prose": "action to be taken in response to malicious code detection are defined (if selected);" - } - ] - }, - { - "id": "si-03_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "si-3_prm_6" - }, - { - "name": "label", - "value": "SI-03_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "constraints": [ - { - "description": "administrator or defined security personnel near-realtime" - } - ], - "guidelines": [ - { - "prose": "personnel or roles to be alerted when malicious code is detected is/are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SI-03", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-3" - }, - { - "name": "label", - "value": "SI-03", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#3dd249b0-f57d-44ba-a03e-c3eab1b835ff", - "rel": "reference" - }, - { - "href": "#88660532-2dcf-442e-845c-03340ce48999", - "rel": "reference" - }, - { - "href": "#1c71b420-2bd9-4e52-9fc8-390f58b85b59", - "rel": "reference" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ma-3", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pl-9", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-23", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-26", - "rel": "related" - }, - { - "href": "#sc-28", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-44", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - }, - { - "href": "#si-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#si-15", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-3_smt", - "name": "statement", - "parts": [ - { - "id": "si-3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Implement {{ insert: param, si-03_odp.01 }} malicious code protection mechanisms at system entry and exit points to detect and eradicate malicious code;" - }, - { - "id": "si-3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Automatically update malicious code protection mechanisms as new releases are available in accordance with organizational configuration management policy and procedures;" - }, - { - "id": "si-3_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Configure malicious code protection mechanisms to:", - "parts": [ - { - "id": "si-3_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Perform periodic scans of the system {{ insert: param, si-03_odp.02 }} and real-time scans of files from external sources at {{ insert: param, si-03_odp.03 }} as the files are downloaded, opened, or executed in accordance with organizational policy; and" - }, - { - "id": "si-3_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "{{ insert: param, si-03_odp.04 }} ; and send alert to {{ insert: param, si-03_odp.06 }} in response to malicious code detection; and" - } - ] - }, - { - "id": "si-3_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Address the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the system." - } - ] - }, - { - "id": "si-3_gdn", - "name": "guidance", - "prose": "System entry and exit points include firewalls, remote access servers, workstations, electronic mail servers, web servers, proxy servers, notebook computers, and mobile devices. Malicious code includes viruses, worms, Trojan horses, and spyware. Malicious code can also be encoded in various formats contained within compressed or hidden files or hidden in files using techniques such as steganography. Malicious code can be inserted into systems in a variety of ways, including by electronic mail, the world-wide web, and portable storage devices. Malicious code insertions occur through the exploitation of system vulnerabilities. A variety of technologies and methods exist to limit or eliminate the effects of malicious code.\n\nMalicious code protection mechanisms include both signature- and nonsignature-based technologies. Nonsignature-based detection mechanisms include artificial intelligence techniques that use heuristics to detect, analyze, and describe the characteristics or behavior of malicious code and to provide controls against such code for which signatures do not yet exist or for which existing signatures may not be effective. Malicious code for which active signatures do not yet exist or may be ineffective includes polymorphic malicious code (i.e., code that changes signatures when it replicates). Nonsignature-based mechanisms also include reputation-based technologies. In addition to the above technologies, pervasive configuration management, comprehensive software integrity controls, and anti-exploitation software may be effective in preventing the execution of unauthorized code. Malicious code may be present in commercial off-the-shelf software as well as custom-built software and could include logic bombs, backdoors, and other types of attacks that could affect organizational mission and business functions.\n\nIn situations where malicious code cannot be detected by detection methods or technologies, organizations rely on other types of controls, including secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to ensure that software does not perform functions other than the functions intended. Organizations may determine that, in response to the detection of malicious code, different actions may be warranted. For example, organizations can define actions in response to malicious code detection during periodic scans, the detection of malicious downloads, or the detection of maliciousness when attempting to open or execute files." - }, - { - "id": "si-3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-03a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-3_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-03a.[01]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-03_odp.01 }} malicious code protection mechanisms are implemented at system entry and exit points to detect malicious code;", - "links": [ - { - "href": "#si-3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-3_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-03a.[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-03_odp.01 }} malicious code protection mechanisms are implemented at system entry and exit points to eradicate malicious code;", - "links": [ - { - "href": "#si-3_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-03b.", - "class": "sp800-53a" - } - ], - "prose": "malicious code protection mechanisms are updated automatically as new releases are available in accordance with organizational configuration management policy and procedures;", - "links": [ - { - "href": "#si-3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-3_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-03c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-3_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-03c.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-3_obj.c.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-03c.01[01]", - "class": "sp800-53a" - } - ], - "prose": "malicious code protection mechanisms are configured to perform periodic scans of the system {{ insert: param, si-03_odp.02 }};", - "links": [ - { - "href": "#si-3_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-3_obj.c.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-03c.01[02]", - "class": "sp800-53a" - } - ], - "prose": "malicious code protection mechanisms are configured to perform real-time scans of files from external sources at {{ insert: param, si-03_odp.03 }} as the files are downloaded, opened, or executed in accordance with organizational policy;", - "links": [ - { - "href": "#si-3_smt.c.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-3_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-3_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-03c.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-3_obj.c.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-03c.02[01]", - "class": "sp800-53a" - } - ], - "prose": "malicious code protection mechanisms are configured to {{ insert: param, si-03_odp.04 }} in response to malicious code detection;", - "links": [ - { - "href": "#si-3_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-3_obj.c.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-03c.02[02]", - "class": "sp800-53a" - } - ], - "prose": "malicious code protection mechanisms are configured to send alerts to {{ insert: param, si-03_odp.06 }} in response to malicious code detection;", - "links": [ - { - "href": "#si-3_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-3_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-3_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-3_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-03d.", - "class": "sp800-53a" - } - ], - "prose": "the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the system are addressed.", - "links": [ - { - "href": "#si-3_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-03-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nconfiguration management policy and procedures\n\nprocedures addressing malicious code protection\n\nmalicious code protection mechanisms\n\nrecords of malicious code protection updates\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nscan results from malicious code protection mechanisms\n\nrecord of actions initiated by malicious code protection mechanisms in response to malicious code detection\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-03-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the system\n\norganizational personnel responsible for malicious code protection\n\norganizational personnel with configuration management responsibilities" - } - ] - }, - { - "id": "si-3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-03-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for employing, updating, and configuring malicious code protection mechanisms\n\norganizational processes for addressing false positives and resulting potential impacts\n\nmechanisms supporting and/or implementing, employing, updating, and configuring malicious code protection mechanisms\n\nmechanisms supporting and/or implementing malicious code scanning and subsequent actions" - } - ] - } - ] - }, - { - "id": "si-4", - "class": "SP800-53", - "title": "System Monitoring", - "params": [ - { - "id": "si-04_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "si-4_prm_1" - }, - { - "name": "label", - "value": "SI-04_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "monitoring objectives", - "guidelines": [ - { - "prose": "monitoring objectives to detect attacks and indicators of potential attacks on the system are defined;" - } - ] - }, - { - "id": "si-04_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "si-4_prm_2" - }, - { - "name": "label", - "value": "SI-04_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "techniques and methods", - "guidelines": [ - { - "prose": "techniques and methods used to identify unauthorized use of the system are defined;" - } - ] - }, - { - "id": "si-04_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "si-4_prm_3" - }, - { - "name": "label", - "value": "SI-04_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "system monitoring information", - "guidelines": [ - { - "prose": "system monitoring information to be provided to personnel or roles is defined;" - } - ] - }, - { - "id": "si-04_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "si-4_prm_4" - }, - { - "name": "label", - "value": "SI-04_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom system monitoring information is to be provided is/are defined;" - } - ] - }, - { - "id": "si-04_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "si-4_prm_5" - }, - { - "name": "label", - "value": "SI-04_ODP[05]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "as needed", - "{{ insert: param, si-04_odp.06 }}" - ] - } - }, - { - "id": "si-04_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "si-4_prm_6" - }, - { - "name": "label", - "value": "SI-04_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "guidelines": [ - { - "prose": "a frequency for providing system monitoring to personnel or roles is defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-04", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-4" - }, - { - "name": "label", - "value": "SI-04", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#678e3d6c-150b-4393-aec5-6e3481eb1e00", - "rel": "reference" - }, - { - "href": "#49b8aa2d-a88c-4bff-9f20-876ccb8f7dcb", - "rel": "reference" - }, - { - "href": "#3dd249b0-f57d-44ba-a03e-c3eab1b835ff", - "rel": "reference" - }, - { - "href": "#5eee45d8-3313-4fdc-8d54-1742092bbdd6", - "rel": "reference" - }, - { - "href": "#25e3e57b-dc2f-4934-af9b-050b020c6f0e", - "rel": "reference" - }, - { - "href": "#067223d8-1ec7-45c5-b21b-c848da6de8fb", - "rel": "reference" - }, - { - "href": "#ac-2", - "rel": "related" - }, - { - "href": "#ac-3", - "rel": "related" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#ac-8", - "rel": "related" - }, - { - "href": "#ac-17", - "rel": "related" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#au-7", - "rel": "related" - }, - { - "href": "#au-9", - "rel": "related" - }, - { - "href": "#au-12", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-13", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-14", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#cm-11", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ia-10", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ma-3", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pl-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-12", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ra-10", - "rel": "related" - }, - { - "href": "#sc-5", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "#sc-18", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-26", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-31", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-35", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-36", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-37", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-43", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-6", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - }, - { - "href": "#sr-9", - "rel": "related" - }, - { - "href": "#sr-10", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-4_smt", - "name": "statement", - "parts": [ - { - "id": "si-4_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Monitor the system to detect:", - "parts": [ - { - "id": "si-4_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Attacks and indicators of potential attacks in accordance with the following monitoring objectives: {{ insert: param, si-04_odp.01 }} ; and" - }, - { - "id": "si-4_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Unauthorized local, network, and remote connections;" - } - ] - }, - { - "id": "si-4_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Identify unauthorized use of the system through the following techniques and methods: {{ insert: param, si-04_odp.02 }};" - }, - { - "id": "si-4_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Invoke internal monitoring capabilities or deploy monitoring devices:", - "parts": [ - { - "id": "si-4_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Strategically within the system to collect organization-determined essential information; and" - }, - { - "id": "si-4_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "At ad hoc locations within the system to track specific types of transactions of interest to the organization;" - } - ] - }, - { - "id": "si-4_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Analyze detected events and anomalies;" - }, - { - "id": "si-4_smt.e", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "e." - } - ], - "prose": "Adjust the level of system monitoring activity when there is a change in risk to organizational operations and assets, individuals, other organizations, or the Nation;" - }, - { - "id": "si-4_smt.f", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "f." - } - ], - "prose": "Obtain legal opinion regarding system monitoring activities; and" - }, - { - "id": "si-4_smt.g", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "g." - } - ], - "prose": "Provide {{ insert: param, si-04_odp.03 }} to {{ insert: param, si-04_odp.04 }} {{ insert: param, si-04_odp.05 }}." - } - ] - }, - { - "id": "si-4_gdn", - "name": "guidance", - "prose": "System monitoring includes external and internal monitoring. External monitoring includes the observation of events occurring at external interfaces to the system. Internal monitoring includes the observation of events occurring within the system. Organizations monitor systems by observing audit activities in real time or by observing other system aspects such as access patterns, characteristics of access, and other actions. The monitoring objectives guide and inform the determination of the events. System monitoring capabilities are achieved through a variety of tools and techniques, including intrusion detection and prevention systems, malicious code protection software, scanning tools, audit record monitoring software, and network monitoring software.\n\nDepending on the security architecture, the distribution and configuration of monitoring devices may impact throughput at key internal and external boundaries as well as at other locations across a network due to the introduction of network throughput latency. If throughput management is needed, such devices are strategically located and deployed as part of an established organization-wide security architecture. Strategic locations for monitoring devices include selected perimeter locations and near key servers and server farms that support critical applications. Monitoring devices are typically employed at the managed interfaces associated with controls [SC-7](#sc-7) and [AC-17](#ac-17) . The information collected is a function of the organizational monitoring objectives and the capability of systems to support such objectives. Specific types of transactions of interest include Hypertext Transfer Protocol (HTTP) traffic that bypasses HTTP proxies. System monitoring is an integral part of organizational continuous monitoring and incident response programs, and output from system monitoring serves as input to those programs. System monitoring requirements, including the need for specific types of system monitoring, may be referenced in other controls (e.g., [AC-2g](#ac-2_smt.g), [AC-2(7)](#ac-2.7), [AC-2(12)(a)](#ac-2.12_smt.a), [AC-17(1)](#ac-17.1), [AU-13](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-13), [AU-13(1)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-13.1), [AU-13(2)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#au-13.2), [CM-3f](#cm-3_smt.f), [CM-6d](#cm-6_smt.d), [MA-3a](#ma-3_smt.a), [MA-4a](#ma-4_smt.a), [SC-5(3)(b)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-5.3_smt.b), [SC-7a](#sc-7_smt.a), [SC-7(24)(b)](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-7.24_smt.b), [SC-18b](#sc-18_smt.b), [SC-43b](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-43_smt.b) ). Adjustments to levels of system monitoring are based on law enforcement information, intelligence information, or other sources of information. The legality of system monitoring activities is based on applicable laws, executive orders, directives, regulations, policies, standards, and guidelines." - }, - { - "id": "si-4_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SI-4 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "si-4_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "See US-CERT Incident Response Reporting Guidelines." - } - ] - }, - { - "id": "si-4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-4_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-4_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04a.01", - "class": "sp800-53a" - } - ], - "prose": "the system is monitored to detect attacks and indicators of potential attacks in accordance with {{ insert: param, si-04_odp.01 }};", - "links": [ - { - "href": "#si-4_smt.a.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4_obj.a.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04a.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-4_obj.a.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04a.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the system is monitored to detect unauthorized local connections;", - "links": [ - { - "href": "#si-4_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4_obj.a.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04a.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the system is monitored to detect unauthorized network connections;", - "links": [ - { - "href": "#si-4_smt.a.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4_obj.a.2-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04a.02[03]", - "class": "sp800-53a" - } - ], - "prose": "the system is monitored to detect unauthorized remote connections;", - "links": [ - { - "href": "#si-4_smt.a.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-4_smt.a.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04b.", - "class": "sp800-53a" - } - ], - "prose": "unauthorized use of the system is identified through {{ insert: param, si-04_odp.02 }};", - "links": [ - { - "href": "#si-4_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-4_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04c.01", - "class": "sp800-53a" - } - ], - "prose": "internal monitoring capabilities are invoked or monitoring devices are deployed strategically within the system to collect organization-determined essential information;", - "links": [ - { - "href": "#si-4_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04c.02", - "class": "sp800-53a" - } - ], - "prose": "internal monitoring capabilities are invoked or monitoring devices are deployed at ad hoc locations within the system to track specific types of transactions of interest to the organization;", - "links": [ - { - "href": "#si-4_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-4_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04d.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-4_obj.d-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04d.[01]", - "class": "sp800-53a" - } - ], - "prose": "detected events are analyzed;", - "links": [ - { - "href": "#si-4_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4_obj.d-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04d.[02]", - "class": "sp800-53a" - } - ], - "prose": "detected anomalies are analyzed;", - "links": [ - { - "href": "#si-4_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-4_smt.d", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4_obj.e", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04e.", - "class": "sp800-53a" - } - ], - "prose": "the level of system monitoring activity is adjusted when there is a change in risk to organizational operations and assets, individuals, other organizations, or the Nation;", - "links": [ - { - "href": "#si-4_smt.e", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4_obj.f", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04f.", - "class": "sp800-53a" - } - ], - "prose": "a legal opinion regarding system monitoring activities is obtained;", - "links": [ - { - "href": "#si-4_smt.f", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4_obj.g", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04g.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-04_odp.03 }} is provided to {{ insert: param, si-04_odp.04 }} {{ insert: param, si-04_odp.05 }}.", - "links": [ - { - "href": "#si-4_smt.g", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-04-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing system monitoring tools and techniques\n\ncontinuous monitoring strategy\n\nfacility diagram/layout\n\nsystem design documentation\n\nsystem monitoring tools and techniques documentation\n\nlocations within the system where monitoring devices are deployed\n\nsystem configuration settings and associated documentation\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-04-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the system\n\norganizational personnel responsible for monitoring the system" - } - ] - }, - { - "id": "si-4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-04-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for system monitoring\n\nmechanisms supporting and/or implementing system monitoring capabilities" - } - ] - } - ], - "controls": [ - { - "id": "si-4.1", - "class": "SP800-53-enhancement", - "title": "System-wide Intrusion Detection System", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SI-04(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-4(1)" - }, - { - "name": "label", - "value": "SI-04(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-04.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-4", - "rel": "required" - } - ], - "parts": [ - { - "id": "si-4.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Connect and configure individual intrusion detection tools into a system-wide intrusion detection system." - }, - { - "id": "si-4.1_gdn", - "name": "guidance", - "prose": "Linking individual intrusion detection tools into a system-wide intrusion detection system provides additional coverage and effective detection capabilities. The information contained in one intrusion detection tool can be shared widely across the organization, making the system-wide detection capability more robust and powerful." - }, - { - "id": "si-4.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-4.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "individual intrusion detection tools are connected to a system-wide intrusion detection system;", - "links": [ - { - "href": "#si-4.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.1_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "individual intrusion detection tools are configured into a system-wide intrusion detection system.", - "links": [ - { - "href": "#si-4.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-4.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-04(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing system monitoring tools and techniques\n\nsystem design documentation\n\nsystem monitoring tools and techniques documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-4.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-04(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the system\n\norganizational personnel responsible for monitoring the system\n\norganizational personnel responsible for the intrusion detection system" - } - ] - }, - { - "id": "si-4.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-04(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for intrusion detection and system monitoring\n\nmechanisms supporting and/or implementing intrusion detection capabilities" - } - ] - } - ] - }, - { - "id": "si-4.2", - "class": "SP800-53-enhancement", - "title": "Automated Tools and Mechanisms for Real-time Analysis", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SI-04(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-4(2)" - }, - { - "name": "label", - "value": "SI-04(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-04.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-4", - "rel": "required" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-23", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-25", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-4.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Employ automated tools and mechanisms to support near real-time analysis of events." - }, - { - "id": "si-4.2_gdn", - "name": "guidance", - "prose": "Automated tools and mechanisms include host-based, network-based, transport-based, or storage-based event monitoring tools and mechanisms or security information and event management (SIEM) technologies that provide real-time analysis of alerts and notifications generated by organizational systems. Automated monitoring techniques can create unintended privacy risks because automated controls may connect to external or otherwise unrelated systems. The matching of records between these systems may create linkages with unintended consequences. Organizations assess and document these risks in their privacy impact assessment and make determinations that are in alignment with their privacy program plan." - }, - { - "id": "si-4.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04(02)", - "class": "sp800-53a" - } - ], - "prose": "automated tools and mechanisms are employed to support a near real-time analysis of events.", - "links": [ - { - "href": "#si-4.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-04(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing system monitoring tools and techniques\n\nsystem design documentation\n\nsystem monitoring tools and techniques documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nprivacy plan\n\nprivacy program plan\n\nprivacy impact assessment\n\nprivacy risk management documentation\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-4.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-04(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security and privacy responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the system\n\norganizational personnel responsible for monitoring the system\n\norganizational personnel responsible for incident response/management" - } - ] - }, - { - "id": "si-4.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-04(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for the near real-time analysis of events\n\norganizational processes for system monitoring\n\nmechanisms supporting and/or implementing system monitoring\n\nmechanisms/tools supporting and/or implementing an analysis of events" - } - ] - } - ] - }, - { - "id": "si-4.4", - "class": "SP800-53-enhancement", - "title": "Inbound and Outbound Communications Traffic", - "params": [ - { - "id": "si-4.4_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-04.04_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-04.04_odp.03" - } - ], - "label": "organization-defined frequency" - }, - { - "id": "si-4.4_prm_2", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-04.04_odp.02" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-04.04_odp.04" - } - ], - "label": "organization-defined unusual or unauthorized activities or conditions" - }, - { - "id": "si-04.04_odp.01", - "props": [ - { - "name": "label", - "value": "SI-04(04)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "continuously" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to monitor inbound communications traffic for unusual or unauthorized activities or conditions is defined;" - } - ] - }, - { - "id": "si-04.04_odp.02", - "props": [ - { - "name": "label", - "value": "SI-04(04)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "unusual or unauthorized activities or conditions", - "guidelines": [ - { - "prose": "unusual or unauthorized activities or conditions that are to be monitored in inbound communications traffic are defined;" - } - ] - }, - { - "id": "si-04.04_odp.03", - "props": [ - { - "name": "label", - "value": "SI-04(04)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "continuously" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to monitor outbound communications traffic for unusual or unauthorized activities or conditions is defined;" - } - ] - }, - { - "id": "si-04.04_odp.04", - "props": [ - { - "name": "label", - "value": "SI-04(04)_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "unusual or unauthorized activities or conditions", - "guidelines": [ - { - "prose": "unusual or unauthorized activities or conditions that are to be monitored in outbound communications traffic are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-04(04)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-4(4)" - }, - { - "name": "label", - "value": "SI-04(04)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-04.04" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-4", - "rel": "required" - } - ], - "parts": [ - { - "id": "si-4.4_smt", - "name": "statement", - "parts": [ - { - "id": "si-4.4_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Determine criteria for unusual or unauthorized activities or conditions for inbound and outbound communications traffic;" - }, - { - "id": "si-4.4_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Monitor inbound and outbound communications traffic {{ insert: param, si-4.4_prm_1 }} for {{ insert: param, si-4.4_prm_2 }}." - } - ] - }, - { - "id": "si-4.4_gdn", - "name": "guidance", - "prose": "Unusual or unauthorized activities or conditions related to system inbound and outbound communications traffic includes internal traffic that indicates the presence of malicious code or unauthorized use of legitimate code or credentials within organizational systems or propagating among system components, signaling to external systems, and the unauthorized exporting of information. Evidence of malicious code or unauthorized use of legitimate code or credentials is used to identify potentially compromised systems or system components." - }, - { - "id": "si-4.4_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04(04)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-4.4_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04(04)(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-4.4_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04(04)(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "criteria for unusual or unauthorized activities or conditions for inbound communications traffic are defined;", - "links": [ - { - "href": "#si-4.4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.4_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04(04)(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "criteria for unusual or unauthorized activities or conditions for outbound communications traffic are defined;", - "links": [ - { - "href": "#si-4.4_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-4.4_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.4_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04(04)(b)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-4.4_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04(04)(b)[01]", - "class": "sp800-53a" - } - ], - "prose": "inbound communications traffic is monitored {{ insert: param, si-04.04_odp.01 }} for {{ insert: param, si-04.04_odp.02 }};", - "links": [ - { - "href": "#si-4.4_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.4_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04(04)(b)[02]", - "class": "sp800-53a" - } - ], - "prose": "outbound communications traffic is monitored {{ insert: param, si-04.04_odp.03 }} for {{ insert: param, si-04.04_odp.04 }}.", - "links": [ - { - "href": "#si-4.4_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-4.4_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-4.4_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.4_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-04(04)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing system monitoring tools and techniques\n\nsystem design documentation\n\nsystem monitoring tools and techniques documentation\n\nsystem configuration settings and associated documentation\n\nsystem protocols\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-4.4_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-04(04)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the system\n\norganizational personnel responsible for monitoring the system\n\norganizational personnel responsible for the intrusion detection system" - } - ] - }, - { - "id": "si-4.4_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-04(04)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for intrusion detection and system monitoring\n\nmechanisms supporting and/or implementing intrusion detection and system monitoring capabilities\n\nmechanisms supporting and/or implementing the monitoring of inbound and outbound communications traffic" - } - ] - } - ] - }, - { - "id": "si-4.5", - "class": "SP800-53-enhancement", - "title": "System-generated Alerts", - "params": [ - { - "id": "si-04.05_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "si-4.5_prm_1" - }, - { - "name": "label", - "value": "SI-04(05)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to be alerted when indications of compromise or potential compromise occur is/are defined;" - } - ] - }, - { - "id": "si-04.05_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "si-4.5_prm_2" - }, - { - "name": "label", - "value": "SI-04(05)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "compromise indicators", - "guidelines": [ - { - "prose": "compromise indicators are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-04(05)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-4(5)" - }, - { - "name": "label", - "value": "SI-04(05)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-04.05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-4", - "rel": "required" - }, - { - "href": "#au-4", - "rel": "related" - }, - { - "href": "#au-5", - "rel": "related" - }, - { - "href": "#pe-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-4.5_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Alert {{ insert: param, si-04.05_odp.01 }} when the following system-generated indications of compromise or potential compromise occur: {{ insert: param, si-04.05_odp.02 }}." - }, - { - "id": "si-4.5_gdn", - "name": "guidance", - "prose": "Alerts may be generated from a variety of sources, including audit records or inputs from malicious code protection mechanisms, intrusion detection or prevention mechanisms, or boundary protection devices such as firewalls, gateways, and routers. Alerts can be automated and may be transmitted telephonically, by electronic mail messages, or by text messaging. Organizational personnel on the alert notification list can include system administrators, mission or business owners, system owners, information owners/stewards, senior agency information security officers, senior agency officials for privacy, system security officers, or privacy officers. In contrast to alerts generated by the system, alerts generated by organizations in [SI-4(12)](#si-4.12) focus on information sources external to the system, such as suspicious activity reports and reports on potential insider threats." - }, - { - "id": "si-4.5_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SI-4 (5) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "si-4.5_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "In accordance with the incident response plan." - } - ] - }, - { - "id": "si-4.5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04(05)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-04.05_odp.01 }} are alerted when system-generated {{ insert: param, si-04.05_odp.02 }} occur.", - "links": [ - { - "href": "#si-4.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-04(05)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing system monitoring tools and techniques\n\nsystem monitoring tools and techniques documentation\n\nsystem configuration settings and associated documentation\n\nlist of personnel selected to receive alerts\n\ndocumentation of alerts generated based on compromise indicators\n\nsystem audit records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-4.5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-04(05)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security and privacy responsibilities\n\nsystem developers\n\norganizational personnel installing, configuring, and/or maintaining the system\n\norganizational personnel responsible for monitoring the system\n\norganizational personnel on the system alert notification list\n\norganizational personnel responsible for the intrusion detection system" - } - ] - }, - { - "id": "si-4.5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-04(05)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for intrusion detection and system monitoring\n\nmechanisms supporting and/or implementing intrusion detection and system monitoring capabilities\n\nmechanisms supporting and/or implementing alerts for compromise indicators" - } - ] - } - ] - }, - { - "id": "si-4.10", - "class": "SP800-53-enhancement", - "title": "Visibility of Encrypted Communications", - "params": [ - { - "id": "si-04.10_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "si-4.10_prm_1" - }, - { - "name": "label", - "value": "SI-04(10)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "encrypted communications traffic", - "guidelines": [ - { - "prose": "encrypted communications traffic to be made visible to system monitoring tools and mechanisms is defined;" - } - ] - }, - { - "id": "si-04.10_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "si-4.10_prm_2" - }, - { - "name": "label", - "value": "SI-04(10)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "system monitoring tools and mechanisms", - "guidelines": [ - { - "prose": "system monitoring tools and mechanisms to be provided access to encrypted communications traffic are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SI-04(10)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-4(10)" - }, - { - "name": "label", - "value": "SI-04(10)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-04.10" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-4", - "rel": "required" - } - ], - "parts": [ - { - "id": "si-4.10_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Make provisions so that {{ insert: param, si-04.10_odp.01 }} is visible to {{ insert: param, si-04.10_odp.02 }}." - }, - { - "id": "si-4.10_gdn", - "name": "guidance", - "prose": "Organizations balance the need to encrypt communications traffic to protect data confidentiality with the need to maintain visibility into such traffic from a monitoring perspective. Organizations determine whether the visibility requirement applies to internal encrypted traffic, encrypted traffic intended for external destinations, or a subset of the traffic types." - }, - { - "id": "si-4.10_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SI-4 (10) Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "si-4.10_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "The service provider must support Agency requirements to comply with M-21-31 (https://www.whitehouse.gov/wp-content/uploads/2021/08/M-21-31-Improving-the-Federal-Governments-Investigative-and-Remediation-Capabilities-Related-to-Cybersecurity-Incidents.pdf) and M-22-09 (https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf)." - } - ] - }, - { - "id": "si-4.10_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04(10)", - "class": "sp800-53a" - } - ], - "prose": "provisions are made so that {{ insert: param, si-04.10_odp.01 }} is visible to {{ insert: param, si-04.10_odp.02 }}.", - "links": [ - { - "href": "#si-4.10_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.10_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-04(10)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing system monitoring tools and techniques\n\nsystem design documentation\n\nsystem monitoring tools and techniques documentation\n\nsystem configuration settings and associated documentation\n\nsystem protocols\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-4.10_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-04(10)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the system\n\norganizational personnel responsible for monitoring the system\n\norganizational personnel responsible for the intrusion detection system" - } - ] - }, - { - "id": "si-4.10_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-04(10)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for intrusion detection and system monitoring\n\nmechanisms supporting and/or implementing intrusion detection and system monitoring capabilities\n\nmechanisms supporting and/or implementing the visibility of encrypted communications traffic to monitoring tools" - } - ] - } - ] - }, - { - "id": "si-4.11", - "class": "SP800-53-enhancement", - "title": "Analyze Communications Traffic Anomalies", - "params": [ - { - "id": "si-04.11_odp", - "props": [ - { - "name": "alt-identifier", - "value": "si-4.11_prm_1" - }, - { - "name": "alt-label", - "value": "interior points within the system", - "class": "sp800-53" - }, - { - "name": "label", - "value": "SI-04(11)_ODP", - "class": "sp800-53a" - } - ], - "label": "interior points", - "guidelines": [ - { - "prose": "interior points within the system where communications traffic is to be analyzed are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-04(11)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-4(11)" - }, - { - "name": "label", - "value": "SI-04(11)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-04.11" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-4", - "rel": "required" - } - ], - "parts": [ - { - "id": "si-4.11_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Analyze outbound communications traffic at the external interfaces to the system and selected {{ insert: param, si-04.11_odp }} to discover anomalies." - }, - { - "id": "si-4.11_gdn", - "name": "guidance", - "prose": "Organization-defined interior points include subnetworks and subsystems. Anomalies within organizational systems include large file transfers, long-time persistent connections, attempts to access information from unexpected locations, the use of unusual protocols and ports, the use of unmonitored network protocols (e.g., IPv6 usage during IPv4 transition), and attempted communications with suspected malicious external addresses." - }, - { - "id": "si-4.11_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04(11)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-4.11_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04(11)[01]", - "class": "sp800-53a" - } - ], - "prose": "outbound communications traffic at the external interfaces to the system is analyzed to discover anomalies;", - "links": [ - { - "href": "#si-4.11_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.11_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04(11)[02]", - "class": "sp800-53a" - } - ], - "prose": "outbound communications traffic at {{ insert: param, si-04.11_odp }} is analyzed to discover anomalies.", - "links": [ - { - "href": "#si-4.11_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-4.11_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.11_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-04(11)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing system monitoring tools and techniques\n\nsystem design documentation\n\nnetwork diagram\n\nsystem monitoring tools and techniques documentation\n\nsystem configuration settings and associated documentation\n\nsystem monitoring logs or records\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-4.11_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-04(11)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the system\n\norganizational personnel responsible for monitoring the system\n\norganizational personnel responsible for the intrusion detection system" - } - ] - }, - { - "id": "si-4.11_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-04(11)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for intrusion detection and system monitoring\n\nmechanisms supporting and/or implementing intrusion detection and system monitoring capabilities\n\nmechanisms supporting and/or implementing the analysis of communications traffic" - } - ] - } - ] - }, - { - "id": "si-4.12", - "class": "SP800-53-enhancement", - "title": "Automated Organization-generated Alerts", - "params": [ - { - "id": "si-04.12_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "si-4.12_prm_1" - }, - { - "name": "label", - "value": "SI-04(12)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to be alerted when indications of inappropriate or unusual activity with security or privacy implications occur is/are defined;" - } - ] - }, - { - "id": "si-04.12_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "si-4.12_prm_2" - }, - { - "name": "label", - "value": "SI-04(12)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used to alert personnel or roles are defined;" - } - ] - }, - { - "id": "si-04.12_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "si-4.12_prm_3" - }, - { - "name": "label", - "value": "SI-04(12)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "activities that trigger alerts", - "guidelines": [ - { - "prose": "activities that trigger alerts to personnel or are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-04(12)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-4(12)" - }, - { - "name": "label", - "value": "SI-04(12)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-04.12" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-4", - "rel": "required" - } - ], - "parts": [ - { - "id": "si-4.12_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Alert {{ insert: param, si-04.12_odp.01 }} using {{ insert: param, si-04.12_odp.02 }} when the following indications of inappropriate or unusual activities with security or privacy implications occur: {{ insert: param, si-04.12_odp.03 }}." - }, - { - "id": "si-4.12_gdn", - "name": "guidance", - "prose": "Organizational personnel on the system alert notification list include system administrators, mission or business owners, system owners, senior agency information security officer, senior agency official for privacy, system security officers, or privacy officers. Automated organization-generated alerts are the security alerts generated by organizations and transmitted using automated means. The sources for organization-generated alerts are focused on other entities such as suspicious activity reports and reports on potential insider threats. In contrast to alerts generated by the organization, alerts generated by the system in [SI-4(5)](#si-4.5) focus on information sources that are internal to the systems, such as audit records." - }, - { - "id": "si-4.12_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04(12)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-04.12_odp.01 }} is/are alerted using {{ insert: param, si-04.12_odp.02 }} when {{ insert: param, si-04.12_odp.03 }} indicate inappropriate or unusual activities with security or privacy implications.", - "links": [ - { - "href": "#si-4.12_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.12_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-04(12)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing system monitoring tools and techniques\n\nsystem design documentation\n\nsystem monitoring tools and techniques documentation\n\nsystem configuration settings and associated documentation\n\nlist of inappropriate or unusual activities with security and privacy implications that trigger alerts\n\nsuspicious activity reports\n\nalerts provided to security and privacy personnel\n\nsystem monitoring logs or records\n\nsystem audit records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-4.12_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-04(12)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security and privacy responsibilities\n\nsystem developers\n\norganizational personnel installing, configuring, and/or maintaining the system\n\norganizational personnel responsible for monitoring the system\n\norganizational personnel responsible for the intrusion detection system" - } - ] - }, - { - "id": "si-4.12_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-04(12)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for intrusion detection and system monitoring\n\nautomated mechanisms supporting and/or implementing intrusion detection and system monitoring capabilities\n\nautomated mechanisms supporting and/or implementing automated alerts to security personnel" - } - ] - } - ] - }, - { - "id": "si-4.14", - "class": "SP800-53-enhancement", - "title": "Wireless Intrusion Detection", - "props": [ - { - "name": "label", - "value": "SI-04(14)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-4(14)" - }, - { - "name": "label", - "value": "SI-04(14)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-04.14" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-4", - "rel": "required" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ia-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-4.14_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Employ a wireless intrusion detection system to identify rogue wireless devices and to detect attack attempts and potential compromises or breaches to the system." - }, - { - "id": "si-4.14_gdn", - "name": "guidance", - "prose": "Wireless signals may radiate beyond organizational facilities. Organizations proactively search for unauthorized wireless connections, including the conduct of thorough scans for unauthorized wireless access points. Wireless scans are not limited to those areas within facilities containing systems but also include areas outside of facilities to verify that unauthorized wireless access points are not connected to organizational systems." - }, - { - "id": "si-4.14_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04(14)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-4.14_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04(14)[01]", - "class": "sp800-53a" - } - ], - "prose": "a wireless intrusion detection system is employed to identify rogue wireless devices;", - "links": [ - { - "href": "#si-4.14_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.14_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04(14)[02]", - "class": "sp800-53a" - } - ], - "prose": "a wireless intrusion detection system is employed to detect attack attempts on the system;", - "links": [ - { - "href": "#si-4.14_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.14_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04(14)[03]", - "class": "sp800-53a" - } - ], - "prose": "a wireless intrusion detection system is employed to detect potential compromises or breaches to the system.", - "links": [ - { - "href": "#si-4.14_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-4.14_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.14_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-04(14)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing system monitoring tools and techniques\n\nsystem design documentation\n\nsystem monitoring tools and techniques documentation\n\nsystem configuration settings and associated documentation\n\nsystem protocols\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-4.14_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-04(14)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the system\n\norganizational personnel responsible for monitoring the system\n\norganizational personnel responsible for the intrusion detection system" - } - ] - }, - { - "id": "si-4.14_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-04(14)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for intrusion detection\n\nmechanisms supporting and/or implementing a wireless intrusion detection capability" - } - ] - } - ] - }, - { - "id": "si-4.16", - "class": "SP800-53-enhancement", - "title": "Correlate Monitoring Information", - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SI-04(16)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-4(16)" - }, - { - "name": "label", - "value": "SI-04(16)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-04.16" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-4", - "rel": "required" - }, - { - "href": "#au-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-4.16_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Correlate information from monitoring tools and mechanisms employed throughout the system." - }, - { - "id": "si-4.16_gdn", - "name": "guidance", - "prose": "Correlating information from different system monitoring tools and mechanisms can provide a more comprehensive view of system activity. Correlating system monitoring tools and mechanisms that typically work in isolation—including malicious code protection software, host monitoring, and network monitoring—can provide an organization-wide monitoring view and may reveal otherwise unseen attack patterns. Understanding the capabilities and limitations of diverse monitoring tools and mechanisms and how to maximize the use of information generated by those tools and mechanisms can help organizations develop, operate, and maintain effective monitoring programs. The correlation of monitoring information is especially important during the transition from older to newer technologies (e.g., transitioning from IPv4 to IPv6 network protocols)." - }, - { - "id": "si-4.16_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04(16)", - "class": "sp800-53a" - } - ], - "prose": "information from monitoring tools and mechanisms employed throughout the system is correlated.", - "links": [ - { - "href": "#si-4.16_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.16_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-04(16)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing system monitoring tools and techniques\n\nsystem design documentation\n\nsystem monitoring tools and techniques documentation\n\nsystem configuration settings and associated documentation\n\nevent correlation logs or records\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-4.16_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-04(16)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the system\n\norganizational personnel responsible for monitoring the system\n\norganizational personnel responsible for the intrusion detection system" - } - ] - }, - { - "id": "si-4.16_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-04(16)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for intrusion detection and system monitoring\n\nmechanisms supporting and/or implementing intrusion detection and system monitoring capabilities\n\nmechanisms supporting and/or implementing the correlation of information from monitoring tools" - } - ] - } - ] - }, - { - "id": "si-4.18", - "class": "SP800-53-enhancement", - "title": "Analyze Traffic and Covert Exfiltration", - "params": [ - { - "id": "si-04.18_odp", - "props": [ - { - "name": "alt-identifier", - "value": "si-4.18_prm_1" - }, - { - "name": "alt-label", - "value": "interior points within the system", - "class": "sp800-53" - }, - { - "name": "label", - "value": "SI-04(18)_ODP", - "class": "sp800-53a" - } - ], - "label": "interior points", - "guidelines": [ - { - "prose": "interior points within the system where communications traffic is to be analyzed are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-04(18)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-4(18)" - }, - { - "name": "label", - "value": "SI-04(18)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-04.18" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-4", - "rel": "required" - } - ], - "parts": [ - { - "id": "si-4.18_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Analyze outbound communications traffic at external interfaces to the system and at the following interior points to detect covert exfiltration of information: {{ insert: param, si-04.18_odp }}." - }, - { - "id": "si-4.18_gdn", - "name": "guidance", - "prose": "Organization-defined interior points include subnetworks and subsystems. Covert means that can be used to exfiltrate information include steganography." - }, - { - "id": "si-4.18_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04(18)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-4.18_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04(18)[01]", - "class": "sp800-53a" - } - ], - "prose": "outbound communications traffic is analyzed at interfaces external to the system to detect covert exfiltration of information;", - "links": [ - { - "href": "#si-4.18_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.18_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04(18)[02]", - "class": "sp800-53a" - } - ], - "prose": "outbound communications traffic is analyzed at {{ insert: param, si-04.18_odp }} to detect covert exfiltration of information.", - "links": [ - { - "href": "#si-4.18_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-4.18_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.18_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-04(18)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing system monitoring tools and techniques\n\nsystem design documentation\n\nnetwork diagram\n\nsystem monitoring tools and techniques documentation\n\nsystem configuration settings and associated documentation\n\nsystem monitoring logs or records\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-4.18_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-04(18)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the system\n\norganizational personnel responsible for monitoring the system\n\norganizational personnel responsible for the intrusion detection system" - } - ] - }, - { - "id": "si-4.18_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-04(18)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for intrusion detection and system monitoring\n\nmechanisms supporting and/or implementing intrusion detection and system monitoring capabilities\n\nmechanisms supporting and/or implementing an analysis of outbound communications traffic" - } - ] - } - ] - }, - { - "id": "si-4.19", - "class": "SP800-53-enhancement", - "title": "Risk for Individuals", - "params": [ - { - "id": "si-04.19_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "si-4.19_prm_1" - }, - { - "name": "label", - "value": "SI-04(19)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "additional monitoring", - "guidelines": [ - { - "prose": "additional monitoring of individuals who have been identified as posing an increased level of risk is defined;" - } - ] - }, - { - "id": "si-04.19_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "si-4.19_prm_2" - }, - { - "name": "label", - "value": "SI-04(19)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "sources", - "guidelines": [ - { - "prose": "sources that identify individuals who pose an increased level of risk are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SI-04(19)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-4(19)" - }, - { - "name": "label", - "value": "SI-04(19)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-04.19" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-4", - "rel": "required" - } - ], - "parts": [ - { - "id": "si-4.19_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement {{ insert: param, si-04.19_odp.01 }} of individuals who have been identified by {{ insert: param, si-04.19_odp.02 }} as posing an increased level of risk." - }, - { - "id": "si-4.19_gdn", - "name": "guidance", - "prose": "Indications of increased risk from individuals can be obtained from different sources, including personnel records, intelligence agencies, law enforcement organizations, and other sources. The monitoring of individuals is coordinated with the management, legal, security, privacy, and human resource officials who conduct such monitoring. Monitoring is conducted in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines." - }, - { - "id": "si-4.19_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04(19)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-04.19_odp.01 }} is implemented on individuals who have been identified by {{ insert: param, si-04.19_odp.02 }} as posing an increased level of risk.", - "links": [ - { - "href": "#si-4.19_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.19_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-04(19)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing system monitoring\n\nsystem design documentation\n\nsystem monitoring tools and techniques documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-4.19_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-04(19)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security and privacy responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the system\n\norganizational personnel responsible for monitoring the system\n\nlegal counsel\n\nhuman resource officials\n\norganizational personnel with personnel security responsibilities" - } - ] - }, - { - "id": "si-4.19_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-04(19)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for system monitoring\n\nmechanisms supporting and/or implementing a system monitoring capability" - } - ] - } - ] - }, - { - "id": "si-4.20", - "class": "SP800-53-enhancement", - "title": "Privileged Users", - "params": [ - { - "id": "si-04.20_odp", - "props": [ - { - "name": "alt-identifier", - "value": "si-4.20_prm_1" - }, - { - "name": "label", - "value": "SI-04(20)_ODP", - "class": "sp800-53a" - } - ], - "label": "additional monitoring", - "guidelines": [ - { - "prose": "additional monitoring of privileged users is defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SI-04(20)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-4(20)" - }, - { - "name": "label", - "value": "SI-04(20)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-04.20" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-4", - "rel": "required" - }, - { - "href": "#ac-18", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-4.20_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement the following additional monitoring of privileged users: {{ insert: param, si-04.20_odp }}." - }, - { - "id": "si-4.20_gdn", - "name": "guidance", - "prose": "Privileged users have access to more sensitive information, including security-related information, than the general user population. Access to such information means that privileged users can potentially do greater damage to systems and organizations than non-privileged users. Therefore, implementing additional monitoring on privileged users helps to ensure that organizations can identify malicious activity at the earliest possible time and take appropriate actions." - }, - { - "id": "si-4.20_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04(20)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-04.20_odp }} of privileged users is implemented.", - "links": [ - { - "href": "#si-4.20_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.20_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-04(20)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing system monitoring tools and techniques\n\nsystem design documentation\n\nsystem monitoring tools and techniques documentation\n\nsystem configuration settings and associated documentation\n\nsystem monitoring logs or records\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-4.20_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-04(20)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the system\n\norganizational personnel responsible for monitoring the system" - } - ] - }, - { - "id": "si-4.20_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-04(20)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for system monitoring\n\nmechanisms supporting and/or implementing a system monitoring capability" - } - ] - } - ] - }, - { - "id": "si-4.22", - "class": "SP800-53-enhancement", - "title": "Unauthorized Network Services", - "params": [ - { - "id": "si-04.22_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "si-4.22_prm_1" - }, - { - "name": "label", - "value": "SI-04(22)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "authorization or approval processes", - "guidelines": [ - { - "prose": "authorization or approval processes for network services are defined;" - } - ] - }, - { - "id": "si-04.22_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "si-4.22_prm_2" - }, - { - "name": "label", - "value": "SI-04(22)_ODP[02]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "audit", - "alert {{ insert: param, si-04.22_odp.03 }}" - ] - } - }, - { - "id": "si-04.22_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "si-4.22_prm_3" - }, - { - "name": "label", - "value": "SI-04(22)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to be alerted upon the detection of network services that have not been authorized or approved by authorization or approval processes is/are defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-04(22)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-4(22)" - }, - { - "name": "label", - "value": "SI-04(22)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-04.22" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-4", - "rel": "required" - }, - { - "href": "#cm-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-4.22_smt", - "name": "statement", - "parts": [ - { - "id": "si-4.22_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Detect network services that have not been authorized or approved by {{ insert: param, si-04.22_odp.01 }} ; and" - }, - { - "id": "si-4.22_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "(b)" - } - ], - "prose": "{{ insert: param, si-04.22_odp.02 }} when detected." - } - ] - }, - { - "id": "si-4.22_gdn", - "name": "guidance", - "prose": "Unauthorized or unapproved network services include services in service-oriented architectures that lack organizational verification or validation and may therefore be unreliable or serve as malicious rogues for valid services." - }, - { - "id": "si-4.22_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-04(22)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-4.22_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04(22)(a)", - "class": "sp800-53a" - } - ], - "prose": "network services that have not been authorized or approved by {{ insert: param, si-04.22_odp.01 }} are detected;", - "links": [ - { - "href": "#si-4.22_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.22_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04(22)(b)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-04.22_odp.02 }} is/are initiated when network services that have not been authorized or approved by authorization or approval processes are detected.", - "links": [ - { - "href": "#si-4.22_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-4.22_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.22_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-04(22)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing system monitoring tools and techniques\n\nsystem design documentation\n\nsystem monitoring tools and techniques documentation\n\nsystem configuration settings and associated documentation\n\ndocumented authorization/approval of network services\n\nnotifications or alerts of unauthorized network services\n\nsystem monitoring logs or records\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-4.22_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-04(22)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\nsystem developer\n\norganizational personnel installing, configuring, and/or maintaining the system\n\norganizational personnel responsible for monitoring the system" - } - ] - }, - { - "id": "si-4.22_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-04(22)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for system monitoring\n\nmechanisms supporting and/or implementing a system monitoring capability\n\nmechanisms for auditing network services\n\nmechanisms for providing alerts" - } - ] - } - ] - }, - { - "id": "si-4.23", - "class": "SP800-53-enhancement", - "title": "Host-based Devices", - "params": [ - { - "id": "si-04.23_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "si-4.23_prm_2" - }, - { - "name": "label", - "value": "SI-04(23)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "host-based monitoring mechanisms", - "guidelines": [ - { - "prose": "host-based monitoring mechanisms to be implemented on system components are defined;" - } - ] - }, - { - "id": "si-04.23_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "si-4.23_prm_1" - }, - { - "name": "label", - "value": "SI-04(23)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "system components", - "guidelines": [ - { - "prose": "system components where host-based monitoring is to be implemented are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SI-04(23)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-4(23)" - }, - { - "name": "label", - "value": "SI-04(23)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-04.23" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-4", - "rel": "required" - }, - { - "href": "#ac-18", - "rel": "related" - }, - { - "href": "#ac-19", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-4.23_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement the following host-based monitoring mechanisms at {{ insert: param, si-04.23_odp.02 }}: {{ insert: param, si-04.23_odp.01 }}." - }, - { - "id": "si-4.23_gdn", - "name": "guidance", - "prose": "Host-based monitoring collects information about the host (or system in which it resides). System components in which host-based monitoring can be implemented include servers, notebook computers, and mobile devices. Organizations may consider employing host-based monitoring mechanisms from multiple product developers or vendors." - }, - { - "id": "si-4.23_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-04(23)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-04.23_odp.01 }} are implemented on {{ insert: param, si-04.23_odp.02 }}.", - "links": [ - { - "href": "#si-4.23_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-4.23_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-04(23)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing system monitoring tools and techniques\n\nsystem design documentation\n\nhost-based monitoring mechanisms\n\nsystem monitoring tools and techniques documentation\n\nsystem configuration settings and associated documentation\n\nlist of system components requiring host-based monitoring\n\nsystem monitoring logs or records\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-4.23_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-04(23)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System/network administrators\n\norganizational personnel with information security responsibilities\n\norganizational personnel installing, configuring, and/or maintaining the system\n\norganizational personnel responsible for monitoring system hosts" - } - ] - }, - { - "id": "si-4.23_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-04(23)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for system monitoring\n\nmechanisms supporting and/or implementing a host-based monitoring capability" - } - ] - } - ] - } - ] - }, - { - "id": "si-5", - "class": "SP800-53", - "title": "Security Alerts, Advisories, and Directives", - "params": [ - { - "id": "si-05_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "si-5_prm_1" - }, - { - "name": "label", - "value": "SI-05_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "external organizations", - "constraints": [ - { - "description": "to include US-CERT and Cybersecurity and Infrastructure Security Agency (CISA) Directives" - } - ], - "guidelines": [ - { - "prose": "external organizations from whom system security alerts, advisories, and directives are to be received on an ongoing basis are defined;" - } - ] - }, - { - "id": "si-05_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "si-5_prm_2" - }, - { - "name": "label", - "value": "SI-05_ODP[02]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "to include system security personnel and administrators with configuration/patch-management responsibilities" - } - ] - }, - { - "id": "si-05_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "si-5_prm_3" - }, - { - "name": "label", - "value": "SI-05_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom security alerts, advisories, and directives are to be disseminated is/are defined (if selected);" - } - ] - }, - { - "id": "si-05_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "si-5_prm_4" - }, - { - "name": "alt-label", - "value": "elements within the organization", - "class": "sp800-53" - }, - { - "name": "label", - "value": "SI-05_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "elements", - "guidelines": [ - { - "prose": "elements within the organization to whom security alerts, advisories, and directives are to be disseminated are defined (if selected);" - } - ] - }, - { - "id": "si-05_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "si-5_prm_5" - }, - { - "name": "label", - "value": "SI-05_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "external organizations", - "guidelines": [ - { - "prose": "external organizations to whom security alerts, advisories, and directives are to be disseminated are defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-05", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-5" - }, - { - "name": "label", - "value": "SI-05", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#155f941a-cba9-4afd-9ca6-5d040d697ba9", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-15", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-5_smt", - "name": "statement", - "parts": [ - { - "id": "si-5_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Receive system security alerts, advisories, and directives from {{ insert: param, si-05_odp.01 }} on an ongoing basis;" - }, - { - "id": "si-5_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Generate internal security alerts, advisories, and directives as deemed necessary;" - }, - { - "id": "si-5_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Disseminate security alerts, advisories, and directives to: {{ insert: param, si-05_odp.02 }} ; and" - }, - { - "id": "si-5_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "Implement security directives in accordance with established time frames, or notify the issuing organization of the degree of noncompliance." - } - ] - }, - { - "id": "si-5_gdn", - "name": "guidance", - "prose": "The Cybersecurity and Infrastructure Security Agency (CISA) generates security alerts and advisories to maintain situational awareness throughout the Federal Government. Security directives are issued by OMB or other designated organizations with the responsibility and authority to issue such directives. Compliance with security directives is essential due to the critical nature of many of these directives and the potential (immediate) adverse effects on organizational operations and assets, individuals, other organizations, and the Nation should the directives not be implemented in a timely manner. External organizations include supply chain partners, external mission or business partners, external service providers, and other peer or supporting organizations." - }, - { - "id": "si-5_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SI-5 Additional FedRAMP Requirements and Guidance", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Service Providers must address the CISA Emergency and Binding Operational Directives applicable to their cloud service offering per FedRAMP guidance. This includes listing the applicable directives and stating compliance status." - }, - { - "id": "si-5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-05", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-5_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-05a.", - "class": "sp800-53a" - } - ], - "prose": "system security alerts, advisories, and directives are received from {{ insert: param, si-05_odp.01 }} on an ongoing basis;", - "links": [ - { - "href": "#si-5_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-5_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-05b.", - "class": "sp800-53a" - } - ], - "prose": "internal security alerts, advisories, and directives are generated as deemed necessary;", - "links": [ - { - "href": "#si-5_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-5_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-05c.", - "class": "sp800-53a" - } - ], - "prose": "security alerts, advisories, and directives are disseminated to {{ insert: param, si-05_odp.02 }};", - "links": [ - { - "href": "#si-5_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-5_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-05d.", - "class": "sp800-53a" - } - ], - "prose": "security directives are implemented in accordance with established time frames or if the issuing organization is notified of the degree of noncompliance.", - "links": [ - { - "href": "#si-5_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-05-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing security alerts, advisories, and directives\n\nrecords of security alerts and advisories\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-05-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with security alert and advisory responsibilities\n\norganizational personnel implementing, operating, maintaining, and using the system\n\norganizational personnel, organizational elements, and/or external organizations to whom alerts, advisories, and directives are to be disseminated\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "si-5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-05-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for defining, receiving, generating, disseminating, and complying with security alerts, advisories, and directives\n\nmechanisms supporting and/or implementing the definition, receipt, generation, and dissemination of security alerts, advisories, and directives\n\nmechanisms supporting and/or implementing security directives" - } - ] - } - ], - "controls": [ - { - "id": "si-5.1", - "class": "SP800-53-enhancement", - "title": "Automated Alerts and Advisories", - "params": [ - { - "id": "si-05.01_odp", - "props": [ - { - "name": "alt-identifier", - "value": "si-5.1_prm_1" - }, - { - "name": "label", - "value": "SI-05(01)_ODP", - "class": "sp800-53a" - } - ], - "label": "automated mechanisms", - "guidelines": [ - { - "prose": "automated mechanisms used to broadcast security alert and advisory information throughout the organization are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-05(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-5(1)" - }, - { - "name": "label", - "value": "SI-05(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-05.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-5", - "rel": "required" - } - ], - "parts": [ - { - "id": "si-5.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Broadcast security alert and advisory information throughout the organization using {{ insert: param, si-05.01_odp }}." - }, - { - "id": "si-5.1_gdn", - "name": "guidance", - "prose": "The significant number of changes to organizational systems and environments of operation requires the dissemination of security-related information to a variety of organizational entities that have a direct interest in the success of organizational mission and business functions. Based on information provided by security alerts and advisories, changes may be required at one or more of the three levels related to the management of risk, including the governance level, mission and business process level, and the information system level." - }, - { - "id": "si-5.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-05(01)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-05.01_odp }} are used to broadcast security alert and advisory information throughout the organization.", - "links": [ - { - "href": "#si-5.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-5.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-05(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing security alerts, advisories, and directives\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nautomated mechanisms supporting the distribution of security alert and advisory information\n\nrecords of security alerts and advisories\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-5.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-05(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with security alert and advisory responsibilities\n\norganizational personnel implementing, operating, maintaining, and using the system\n\norganizational personnel, organizational elements, and/or external organizations to whom alerts and advisories are to be disseminated\n\nsystem/network administrators\n\norganizational personnel with information security responsibilities" - } - ] - }, - { - "id": "si-5.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-05(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for defining, receiving, generating, and disseminating security alerts and advisories\n\nautomated mechanisms supporting and/or implementing the dissemination of security alerts and advisories" - } - ] - } - ] - } - ] - }, - { - "id": "si-6", - "class": "SP800-53", - "title": "Security and Privacy Function Verification", - "params": [ - { - "id": "si-6_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-06_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-06_odp.02" - } - ], - "label": "organization-defined security and privacy functions" - }, - { - "id": "si-06_odp.01", - "props": [ - { - "name": "label", - "value": "SI-06_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "security functions", - "guidelines": [ - { - "prose": "security functions to be verified for correct operation are defined;" - } - ] - }, - { - "id": "si-06_odp.02", - "props": [ - { - "name": "label", - "value": "SI-06_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "privacy functions", - "guidelines": [ - { - "prose": "privacy functions to be verified for correct operation are defined;" - } - ] - }, - { - "id": "si-06_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "si-6_prm_2" - }, - { - "name": "label", - "value": "SI-06_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "{{ insert: param, si-06_odp.04 }}", - "upon command by user with appropriate privilege", - "{{ insert: param, si-06_odp.05 }}" - ] - } - }, - { - "id": "si-06_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "si-6_prm_3" - }, - { - "name": "label", - "value": "SI-06_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "system transitional states", - "constraints": [ - { - "description": "to include upon system startup and/or restart" - } - ], - "guidelines": [ - { - "prose": "system transitional states requiring the verification of security and privacy functions are defined; (if selected)" - } - ] - }, - { - "id": "si-06_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "si-6_prm_4" - }, - { - "name": "label", - "value": "SI-06_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least monthly" - } - ], - "guidelines": [ - { - "prose": "frequency at which to verify the correct operation of security and privacy functions is defined; (if selected)" - } - ] - }, - { - "id": "si-06_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "si-6_prm_5" - }, - { - "name": "label", - "value": "SI-06_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "constraints": [ - { - "description": "to include system administrators and security personnel" - } - ], - "guidelines": [ - { - "prose": "personnel or roles to be alerted of failed security and privacy verification tests is/are defined;" - } - ] - }, - { - "id": "si-06_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "si-6_prm_6" - }, - { - "name": "label", - "value": "SI-06_ODP[07]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "shut the system down", - "restart the system", - "{{ insert: param, si-06_odp.08 }}" - ] - } - }, - { - "id": "si-06_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "si-6_prm_7" - }, - { - "name": "label", - "value": "SI-06_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "alternative action(s)", - "guidelines": [ - { - "prose": "alternative action(s) to be performed when anomalies are discovered are defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SI-06", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-6" - }, - { - "name": "label", - "value": "SI-06", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-06" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#cm-4", - "rel": "related" - }, - { - "href": "#cm-6", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-6_smt", - "name": "statement", - "parts": [ - { - "id": "si-6_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Verify the correct operation of {{ insert: param, si-6_prm_1 }};" - }, - { - "id": "si-6_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Perform the verification of the functions specified in SI-6a {{ insert: param, si-06_odp.03 }};" - }, - { - "id": "si-6_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Alert {{ insert: param, si-06_odp.06 }} to failed security and privacy verification tests; and" - }, - { - "id": "si-6_smt.d", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "d." - } - ], - "prose": "{{ insert: param, si-06_odp.07 }} when anomalies are discovered." - } - ] - }, - { - "id": "si-6_gdn", - "name": "guidance", - "prose": "Transitional states for systems include system startup, restart, shutdown, and abort. System notifications include hardware indicator lights, electronic alerts to system administrators, and messages to local computer consoles. In contrast to security function verification, privacy function verification ensures that privacy functions operate as expected and are approved by the senior agency official for privacy or that privacy attributes are applied or used as expected." - }, - { - "id": "si-6_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-06", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-6_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-06a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-6_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-06a.[01]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-06_odp.01 }} are verified to be operating correctly;", - "links": [ - { - "href": "#si-6_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-6_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-06a.[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-06_odp.02 }} are verified to be operating correctly;", - "links": [ - { - "href": "#si-6_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-6_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-6_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-06b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-6_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-06b.[01]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-06_odp.01 }} are verified {{ insert: param, si-06_odp.03 }};", - "links": [ - { - "href": "#si-6_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-6_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-06b.[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-06_odp.02 }} are verified {{ insert: param, si-06_odp.03 }};", - "links": [ - { - "href": "#si-6_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-6_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-6_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-06c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-6_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-06c.[01]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-06_odp.06 }} is/are alerted to failed security verification tests;", - "links": [ - { - "href": "#si-6_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-6_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-06c.[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-06_odp.06 }} is/are alerted to failed privacy verification tests;", - "links": [ - { - "href": "#si-6_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-6_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-6_obj.d", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-06d.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-06_odp.07 }} is/are initiated when anomalies are discovered.", - "links": [ - { - "href": "#si-6_smt.d", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-6_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-6_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-06-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing security and privacy function verification\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nalerts/notifications of failed security verification tests\n\nlist of system transition states requiring security functionality verification\n\nsystem audit records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-6_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-06-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with security and privacy function verification responsibilities\n\norganizational personnel implementing, operating, and maintaining the system\n\nsystem/network administrators\n\norganizational personnel with information security and privacy responsibilities\n\nsystem developer" - } - ] - }, - { - "id": "si-6_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-06-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for security and privacy function verification\n\nmechanisms supporting and/or implementing the security and privacy function verification capability" - } - ] - } - ] - }, - { - "id": "si-7", - "class": "SP800-53", - "title": "Software, Firmware, and Information Integrity", - "params": [ - { - "id": "si-7_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-07_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-07_odp.02" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-07_odp.03" - } - ], - "label": "organization-defined software, firmware, and information" - }, - { - "id": "si-7_prm_2", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-07_odp.04" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-07_odp.05" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-07_odp.06" - } - ], - "label": "organization-defined actions" - }, - { - "id": "si-07_odp.01", - "props": [ - { - "name": "label", - "value": "SI-07_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "software", - "guidelines": [ - { - "prose": "software requiring integrity verification tools to be employed to detect unauthorized changes is defined;" - } - ] - }, - { - "id": "si-07_odp.02", - "props": [ - { - "name": "label", - "value": "SI-07_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "firmware", - "guidelines": [ - { - "prose": "firmware requiring integrity verification tools to be employed to detect unauthorized changes is defined;" - } - ] - }, - { - "id": "si-07_odp.03", - "props": [ - { - "name": "label", - "value": "SI-07_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "information", - "guidelines": [ - { - "prose": "information requiring integrity verification tools to be employed to detect unauthorized changes is defined;" - } - ] - }, - { - "id": "si-07_odp.04", - "props": [ - { - "name": "label", - "value": "SI-07_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "actions", - "guidelines": [ - { - "prose": "actions to be taken when unauthorized changes to software are detected are defined;" - } - ] - }, - { - "id": "si-07_odp.05", - "props": [ - { - "name": "label", - "value": "SI-07_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "actions", - "guidelines": [ - { - "prose": "actions to be taken when unauthorized changes to firmware are detected are defined;" - } - ] - }, - { - "id": "si-07_odp.06", - "props": [ - { - "name": "label", - "value": "SI-07_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "actions", - "guidelines": [ - { - "prose": "actions to be taken when unauthorized changes to information are detected are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SI-07", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-7" - }, - { - "name": "label", - "value": "SI-07", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-07" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "#678e3d6c-150b-4393-aec5-6e3481eb1e00", - "rel": "reference" - }, - { - "href": "#eea3c092-42ed-4382-a6f4-1adadef01b9d", - "rel": "reference" - }, - { - "href": "#7c37a38d-21d7-40d8-bc3d-b5e27eac17e1", - "rel": "reference" - }, - { - "href": "#a295ca19-8c75-4b4c-8800-98024732e181", - "rel": "reference" - }, - { - "href": "#4895b4cd-34c5-4667-bf8a-27d443c12047", - "rel": "reference" - }, - { - "href": "#e47ee630-9cbc-4133-880e-e013f83ccd51", - "rel": "reference" - }, - { - "href": "#ac-4", - "rel": "related" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#cm-7", - "rel": "related" - }, - { - "href": "#cm-8", - "rel": "related" - }, - { - "href": "#ma-3", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#ra-5", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - }, - { - "href": "#sc-8", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - }, - { - "href": "#sc-28", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-37", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#sr-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sr-4", - "rel": "related" - }, - { - "href": "#sr-5", - "rel": "related" - }, - { - "href": "#sr-6", - "rel": "related" - }, - { - "href": "#sr-9", - "rel": "related" - }, - { - "href": "#sr-10", - "rel": "related" - }, - { - "href": "#sr-11", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-7_smt", - "name": "statement", - "parts": [ - { - "id": "si-7_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Employ integrity verification tools to detect unauthorized changes to the following software, firmware, and information: {{ insert: param, si-7_prm_1 }} ; and" - }, - { - "id": "si-7_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Take the following actions when unauthorized changes to the software, firmware, and information are detected: {{ insert: param, si-7_prm_2 }}." - } - ] - }, - { - "id": "si-7_gdn", - "name": "guidance", - "prose": "Unauthorized changes to software, firmware, and information can occur due to errors or malicious activity. Software includes operating systems (with key internal components, such as kernels or drivers), middleware, and applications. Firmware interfaces include Unified Extensible Firmware Interface (UEFI) and Basic Input/Output System (BIOS). Information includes personally identifiable information and metadata that contains security and privacy attributes associated with information. Integrity-checking mechanisms—including parity checks, cyclical redundancy checks, cryptographic hashes, and associated tools—can automatically monitor the integrity of systems and hosted applications." - }, - { - "id": "si-7_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-07", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-7_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-07a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-7_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-07a.[01]", - "class": "sp800-53a" - } - ], - "prose": "integrity verification tools are employed to detect unauthorized changes to {{ insert: param, si-07_odp.01 }};", - "links": [ - { - "href": "#si-7_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-7_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-07a.[02]", - "class": "sp800-53a" - } - ], - "prose": "integrity verification tools are employed to detect unauthorized changes to {{ insert: param, si-07_odp.02 }};", - "links": [ - { - "href": "#si-7_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-7_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-07a.[03]", - "class": "sp800-53a" - } - ], - "prose": "integrity verification tools are employed to detect unauthorized changes to {{ insert: param, si-07_odp.03 }};", - "links": [ - { - "href": "#si-7_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-7_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-7_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-07b.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-7_obj.b-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-07b.[01]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-07_odp.04 }} are taken when unauthorized changes to the software, are detected;", - "links": [ - { - "href": "#si-7_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-7_obj.b-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-07b.[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-07_odp.05 }} are taken when unauthorized changes to the firmware are detected;", - "links": [ - { - "href": "#si-7_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-7_obj.b-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-07b.[03]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-07_odp.06 }} are taken when unauthorized changes to the information are detected.", - "links": [ - { - "href": "#si-7_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-7_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-7_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-07-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing software, firmware, and information integrity\n\npersonally identifiable information processing policy\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nintegrity verification tools and associated documentation\n\nrecords generated or triggered by integrity verification tools regarding unauthorized software, firmware, and information changes\n\nsystem audit records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-7_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-07-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel responsible for software, firmware, and/or information integrity\n\norganizational personnel with information security and privacy responsibilities\n\nsystem/network administrators" - } - ] - }, - { - "id": "si-7_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-07-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Software, firmware, and information integrity verification tools" - } - ] - } - ], - "controls": [ - { - "id": "si-7.1", - "class": "SP800-53-enhancement", - "title": "Integrity Checks", - "params": [ - { - "id": "si-7.1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-07.01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-07.01_odp.05" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-07.01_odp.09" - } - ], - "label": "organization-defined software, firmware, and information" - }, - { - "id": "si-7.1_prm_2", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-07.01_odp.02" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-07.01_odp.06" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-07.01_odp.10" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "at startup", - "at {{ insert: param, si-7.1_prm_3 }}", - "{{ insert: param, si-7.1_prm_4 }}" - ] - } - }, - { - "id": "si-7.1_prm_3", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-07.01_odp.03" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-07.01_odp.07" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-07.01_odp.11" - } - ], - "label": "organization-defined transitional states or security-relevant events" - }, - { - "id": "si-7.1_prm_4", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-07.01_odp.04" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-07.01_odp.08" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "si-07.01_odp.12" - } - ], - "label": "organization-defined frequency" - }, - { - "id": "si-07.01_odp.01", - "props": [ - { - "name": "label", - "value": "SI-07(01)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "software", - "guidelines": [ - { - "prose": "software on which an integrity check is to be performed is defined;" - } - ] - }, - { - "id": "si-07.01_odp.02", - "props": [ - { - "name": "label", - "value": "SI-07(01)_ODP[02]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "at startup", - "at {{ insert: param, si-07.01_odp.03 }}", - "{{ insert: param, si-07.01_odp.04 }}" - ] - } - }, - { - "id": "si-07.01_odp.03", - "props": [ - { - "name": "label", - "value": "SI-07(01)_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "transitional states or security-relevant events", - "constraints": [ - { - "description": "selection to include security relevant event" - } - ], - "guidelines": [ - { - "prose": "transitional states or security-relevant events requiring integrity checks (on software) are defined (if selected);" - } - ] - }, - { - "id": "si-07.01_odp.04", - "props": [ - { - "name": "label", - "value": "SI-07(01)_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least monthly" - } - ], - "guidelines": [ - { - "prose": "frequency with which to perform an integrity check (on software) is defined (if selected);" - } - ] - }, - { - "id": "si-07.01_odp.05", - "props": [ - { - "name": "label", - "value": "SI-07(01)_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "firmware", - "guidelines": [ - { - "prose": "firmware on which an integrity check is to be performed is defined;" - } - ] - }, - { - "id": "si-07.01_odp.06", - "props": [ - { - "name": "label", - "value": "SI-07(01)_ODP[06]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "at startup", - "at {{ insert: param, si-07.01_odp.07 }}", - "{{ insert: param, si-07.01_odp.08 }}" - ] - } - }, - { - "id": "si-07.01_odp.07", - "props": [ - { - "name": "label", - "value": "SI-07(01)_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "transitional states or security-relevant events", - "constraints": [ - { - "description": "selection to include security relevant event" - } - ], - "guidelines": [ - { - "prose": "transitional states or security-relevant events requiring integrity checks (on firmware) are defined (if selected);" - } - ] - }, - { - "id": "si-07.01_odp.08", - "props": [ - { - "name": "label", - "value": "SI-07(01)_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least monthly" - } - ], - "guidelines": [ - { - "prose": "frequency with which to perform an integrity check (on firmware) is defined (if selected);" - } - ] - }, - { - "id": "si-07.01_odp.09", - "props": [ - { - "name": "label", - "value": "SI-07(01)_ODP[09]", - "class": "sp800-53a" - } - ], - "label": "information", - "guidelines": [ - { - "prose": "information on which an integrity check is to be performed is defined;" - } - ] - }, - { - "id": "si-07.01_odp.10", - "props": [ - { - "name": "label", - "value": "SI-07(01)_ODP[10]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "at startup", - "at {{ insert: param, si-07.01_odp.11 }}", - "{{ insert: param, si-07.01_odp.12 }}" - ] - } - }, - { - "id": "si-07.01_odp.11", - "props": [ - { - "name": "label", - "value": "SI-07(01)_ODP[11]", - "class": "sp800-53a" - } - ], - "label": "transitional states or security-relevant events", - "constraints": [ - { - "description": "selection to include security relevant event" - } - ], - "guidelines": [ - { - "prose": "transitional states or security-relevant events requiring integrity checks (of information) are defined (if selected);" - } - ] - }, - { - "id": "si-07.01_odp.12", - "props": [ - { - "name": "label", - "value": "SI-07(01)_ODP[12]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least monthly" - } - ], - "guidelines": [ - { - "prose": "frequency with which to perform an integrity check (of information) is defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SI-07(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-7(1)" - }, - { - "name": "label", - "value": "SI-07(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-07.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-7", - "rel": "required" - } - ], - "parts": [ - { - "id": "si-7.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Perform an integrity check of {{ insert: param, si-7.1_prm_1 }} {{ insert: param, si-7.1_prm_2 }}." - }, - { - "id": "si-7.1_gdn", - "name": "guidance", - "prose": "Security-relevant events include the identification of new threats to which organizational systems are susceptible and the installation of new hardware, software, or firmware. Transitional states include system startup, restart, shutdown, and abort." - }, - { - "id": "si-7.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-07(01)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-7.1_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-07(01)[01]", - "class": "sp800-53a" - } - ], - "prose": "an integrity check of {{ insert: param, si-07.01_odp.01 }} is performed {{ insert: param, si-07.01_odp.02 }};", - "links": [ - { - "href": "#si-7.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-7.1_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-07(01)[02]", - "class": "sp800-53a" - } - ], - "prose": "an integrity check of {{ insert: param, si-07.01_odp.05 }} is performed {{ insert: param, si-07.01_odp.06 }};", - "links": [ - { - "href": "#si-7.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-7.1_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-07(01)[03]", - "class": "sp800-53a" - } - ], - "prose": "an integrity check of {{ insert: param, si-07.01_odp.09 }} is performed {{ insert: param, si-07.01_odp.10 }}.", - "links": [ - { - "href": "#si-7.1_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-7.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-7.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-07(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing software, firmware, and information integrity testing\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nintegrity verification tools and associated documentation\n\nrecords of integrity scans\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-7.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-07(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel responsible for software, firmware, and/or information integrity\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "id": "si-7.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-07(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Software, firmware, and information integrity verification tools" - } - ] - } - ] - }, - { - "id": "si-7.2", - "class": "SP800-53-enhancement", - "title": "Automated Notifications of Integrity Violations", - "params": [ - { - "id": "si-07.02_odp", - "props": [ - { - "name": "alt-identifier", - "value": "si-7.2_prm_1" - }, - { - "name": "label", - "value": "SI-07(02)_ODP", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "constraints": [ - { - "description": "to include the ISSO and/or similar role within the organization" - } - ], - "guidelines": [ - { - "prose": "personnel or roles to whom notification is to be provided upon discovering discrepancies during integrity verification is/are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-07(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-7(2)" - }, - { - "name": "label", - "value": "SI-07(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-07.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-7", - "rel": "required" - } - ], - "parts": [ - { - "id": "si-7.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Employ automated tools that provide notification to {{ insert: param, si-07.02_odp }} upon discovering discrepancies during integrity verification." - }, - { - "id": "si-7.2_gdn", - "name": "guidance", - "prose": "The employment of automated tools to report system and information integrity violations and to notify organizational personnel in a timely matter is essential to effective risk response. Personnel with an interest in system and information integrity violations include mission and business owners, system owners, senior agency information security official, senior agency official for privacy, system administrators, software developers, systems integrators, information security officers, and privacy officers." - }, - { - "id": "si-7.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-07(02)", - "class": "sp800-53a" - } - ], - "prose": "automated tools that provide notification to {{ insert: param, si-07.02_odp }} upon discovering discrepancies during integrity verification are employed.", - "links": [ - { - "href": "#si-7.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-7.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-07(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing software, firmware, and information integrity\n\npersonally identifiable information processing policy\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nintegrity verification tools and associated documentation\n\nrecords of integrity scans\n\nautomated tools supporting alerts and notifications for integrity discrepancies\n\nnotifications provided upon discovering discrepancies during integrity verifications\n\nsystem audit records\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-7.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-07(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel responsible for software, firmware, and/or information integrity\n\norganizational personnel with information security and privacy responsibilities\n\nsystem administrators\n\nsoftware developers" - } - ] - }, - { - "id": "si-7.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-07(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Software, firmware, and information integrity verification tools\n\nmechanisms providing integrity discrepancy notifications" - } - ] - } - ] - }, - { - "id": "si-7.5", - "class": "SP800-53-enhancement", - "title": "Automated Response to Integrity Violations", - "params": [ - { - "id": "si-07.05_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "si-7.5_prm_1" - }, - { - "name": "label", - "value": "SI-07(05)_ODP[01]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "shut down the system", - "restart the system", - "implement {{ insert: param, si-07.05_odp.02 }}" - ] - } - }, - { - "id": "si-07.05_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "si-7.5_prm_2" - }, - { - "name": "label", - "value": "SI-07(05)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "controls", - "guidelines": [ - { - "prose": "controls to be implemented automatically when integrity violations are discovered are defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-07(05)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-7(5)" - }, - { - "name": "label", - "value": "SI-07(05)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-07.05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-7", - "rel": "required" - } - ], - "parts": [ - { - "id": "si-7.5_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Automatically {{ insert: param, si-07.05_odp.01 }} when integrity violations are discovered." - }, - { - "id": "si-7.5_gdn", - "name": "guidance", - "prose": "Organizations may define different integrity-checking responses by type of information, specific information, or a combination of both. Types of information include firmware, software, and user data. Specific information includes boot firmware for certain types of machines. The automatic implementation of controls within organizational systems includes reversing the changes, halting the system, or triggering audit alerts when unauthorized modifications to critical security files occur." - }, - { - "id": "si-7.5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-07(05)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-07.05_odp.01 }} are automatically performed when integrity violations are discovered.", - "links": [ - { - "href": "#si-7.5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-7.5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-07(05)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing software, firmware, and information integrity\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nintegrity verification tools and associated documentation\n\nrecords of integrity scans\n\nrecords of integrity checks and responses to integrity violations\n\naudit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-7.5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-07(05)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel responsible for software, firmware, and/or information integrity\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "id": "si-7.5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-07(05)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Software, firmware, and information integrity verification tools\n\nmechanisms providing an automated response to integrity violations\n\nmechanisms supporting and/or implementing security safeguards to be implemented when integrity violations are discovered" - } - ] - } - ] - }, - { - "id": "si-7.7", - "class": "SP800-53-enhancement", - "title": "Integration of Detection and Response", - "params": [ - { - "id": "si-07.07_odp", - "props": [ - { - "name": "alt-identifier", - "value": "si-7.7_prm_1" - }, - { - "name": "alt-label", - "value": "security-relevant changes to the system", - "class": "sp800-53" - }, - { - "name": "label", - "value": "SI-07(07)_ODP", - "class": "sp800-53a" - } - ], - "label": "changes", - "guidelines": [ - { - "prose": "security-relevant changes to the system are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-07(07)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-7(7)" - }, - { - "name": "label", - "value": "SI-07(07)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-07.07" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-7", - "rel": "required" - }, - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-6", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-5", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-7.7_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Incorporate the detection of the following unauthorized changes into the organizational incident response capability: {{ insert: param, si-07.07_odp }}." - }, - { - "id": "si-7.7_gdn", - "name": "guidance", - "prose": "Integrating detection and response helps to ensure that detected events are tracked, monitored, corrected, and available for historical purposes. Maintaining historical records is important for being able to identify and discern adversary actions over an extended time period and for possible legal actions. Security-relevant changes include unauthorized changes to established configuration settings or the unauthorized elevation of system privileges." - }, - { - "id": "si-7.7_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-07(07)", - "class": "sp800-53a" - } - ], - "prose": "the detection of {{ insert: param, si-07.07_odp }} are incorporated into the organizational incident response capability.", - "links": [ - { - "href": "#si-7.7_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-7.7_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-07(07)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing software, firmware, and information integrity\n\nprocedures addressing incident response\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nincident response records\n\naudit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-7.7_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-07(07)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel responsible for software, firmware, and/or information integrity\n\norganizational personnel with information security responsibilities\n\norganizational personnel with incident response responsibilities" - } - ] - }, - { - "id": "si-7.7_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-07(07)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for incorporating the detection of unauthorized security-relevant changes into the incident response capability\n\nsoftware, firmware, and information integrity verification tools\n\nmechanisms supporting and/or implementing the incorporation of detection of unauthorized security-relevant changes into the incident response capability" - } - ] - } - ] - }, - { - "id": "si-7.15", - "class": "SP800-53-enhancement", - "title": "Code Authentication", - "params": [ - { - "id": "si-07.15_odp", - "props": [ - { - "name": "alt-identifier", - "value": "si-7.15_prm_1" - }, - { - "name": "label", - "value": "SI-07(15)_ODP", - "class": "sp800-53a" - } - ], - "label": "software or firmware components", - "constraints": [ - { - "description": "to include all software and firmware inside the boundary" - } - ], - "guidelines": [ - { - "prose": "software or firmware components to be authenticated by cryptographic mechanisms prior to installation are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-07(15)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-7(15)" - }, - { - "name": "label", - "value": "SI-07(15)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-07.15" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#si-7", - "rel": "required" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#sc-12", - "rel": "related" - }, - { - "href": "#sc-13", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-7.15_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement cryptographic mechanisms to authenticate the following software or firmware components prior to installation: {{ insert: param, si-07.15_odp }}." - }, - { - "id": "si-7.15_gdn", - "name": "guidance", - "prose": "Cryptographic authentication includes verifying that software or firmware components have been digitally signed using certificates recognized and approved by organizations. Code signing is an effective method to protect against malicious code. Organizations that employ cryptographic mechanisms also consider cryptographic key management solutions." - }, - { - "id": "si-7.15_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-07(15)", - "class": "sp800-53a" - } - ], - "prose": "cryptographic mechanisms are implemented to authenticate {{ insert: param, si-07.15_odp }} prior to installation.", - "links": [ - { - "href": "#si-7.15_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-7.15_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-07(15)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing software, firmware, and information integrity\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\ncryptographic mechanisms and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-7.15_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-07(15)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel responsible for software, firmware, and/or information integrity\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "id": "si-7.15_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-07(15)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Cryptographic mechanisms authenticating software and firmware prior to installation" - } - ] - } - ] - } - ] - }, - { - "id": "si-8", - "class": "SP800-53", - "title": "Spam Protection", - "props": [ - { - "name": "label", - "value": "SI-08", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-8" - }, - { - "name": "label", - "value": "SI-08", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#314e33cb-3681-4b50-a2a2-3fae9604accd", - "rel": "reference" - }, - { - "href": "#1c71b420-2bd9-4e52-9fc8-390f58b85b59", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pl-9", - "rel": "related" - }, - { - "href": "#sc-5", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-38", - "rel": "related" - }, - { - "href": "#si-3", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-8_smt", - "name": "statement", - "parts": [ - { - "id": "si-8_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Employ spam protection mechanisms at system entry and exit points to detect and act on unsolicited messages; and" - }, - { - "id": "si-8_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Update spam protection mechanisms when new releases are available in accordance with organizational configuration management policy and procedures." - } - ] - }, - { - "id": "si-8_gdn", - "name": "guidance", - "prose": "System entry and exit points include firewalls, remote-access servers, electronic mail servers, web servers, proxy servers, workstations, notebook computers, and mobile devices. Spam can be transported by different means, including email, email attachments, and web accesses. Spam protection mechanisms include signature definitions." - }, - { - "id": "si-8_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SI-8 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "si-8_fr_gdn.1", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "When CSO sends email on behalf of the government as part of the business offering, Control Description should include implementation of Domain-based Message Authentication, Reporting \\& Conformance (DMARC) on the sending domain for outgoing messages as described in DHS Binding Operational Directive (BOD) 18-01.\n\nhttps://cyber.dhs.gov/bod/18-01/" - }, - { - "id": "si-8_fr_gdn.2", - "name": "guidance", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Guidance:" - } - ], - "prose": "CSPs should confirm DMARC configuration (where appropriate) to ensure that policy=reject and the rua parameter includes reports@dmarc.cyber.dhs.gov. DMARC compliance should be documented in the SI-08 control implementation solution description, and list the FROM: domain(s) that will be seen by email recipients." - } - ] - }, - { - "id": "si-8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-08", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-8_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-08a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-8_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-08a.[01]", - "class": "sp800-53a" - } - ], - "prose": "spam protection mechanisms are employed at system entry points to detect unsolicited messages;", - "links": [ - { - "href": "#si-8_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-8_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-08a.[02]", - "class": "sp800-53a" - } - ], - "prose": "spam protection mechanisms are employed at system exit points to detect unsolicited messages;", - "links": [ - { - "href": "#si-8_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-8_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-08a.[03]", - "class": "sp800-53a" - } - ], - "prose": "spam protection mechanisms are employed at system entry points to act on unsolicited messages;", - "links": [ - { - "href": "#si-8_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-8_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-08a.[04]", - "class": "sp800-53a" - } - ], - "prose": "spam protection mechanisms are employed at system exit points to act on unsolicited messages;", - "links": [ - { - "href": "#si-8_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-8_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-8_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-08b.", - "class": "sp800-53a" - } - ], - "prose": "spam protection mechanisms are updated when new releases are available in accordance with organizational configuration management policies and procedures.", - "links": [ - { - "href": "#si-8_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-08-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nconfiguration management policies and procedures (CM-01)\n\nprocedures addressing spam protection\n\nspam protection mechanisms\n\nrecords of spam protection updates\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-08-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel responsible for spam protection\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "id": "si-8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-08-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for implementing spam protection\n\nmechanisms supporting and/or implementing spam protection" - } - ] - } - ], - "controls": [ - { - "id": "si-8.2", - "class": "SP800-53-enhancement", - "title": "Automatic Updates", - "params": [ - { - "id": "si-08.02_odp", - "props": [ - { - "name": "alt-identifier", - "value": "si-8.2_prm_1" - }, - { - "name": "label", - "value": "SI-08(02)_ODP", - "class": "sp800-53a" - } - ], - "label": "frequency", - "guidelines": [ - { - "prose": "the frequency at which to automatically update spam protection mechanisms is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-08(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-8(2)" - }, - { - "name": "label", - "value": "SI-08(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-08.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#si-8", - "rel": "required" - } - ], - "parts": [ - { - "id": "si-8.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Automatically update spam protection mechanisms {{ insert: param, si-08.02_odp }}." - }, - { - "id": "si-8.2_gdn", - "name": "guidance", - "prose": "Using automated mechanisms to update spam protection mechanisms helps to ensure that updates occur on a regular basis and provide the latest content and protection capabilities." - }, - { - "id": "si-8.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-08(02)", - "class": "sp800-53a" - } - ], - "prose": "spam protection mechanisms are automatically updated {{ insert: param, si-08.02_odp }}.", - "links": [ - { - "href": "#si-8.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-8.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-08(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing spam protection\n\nspam protection mechanisms\n\nrecords of spam protection updates\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-8.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-08(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel responsible for spam protection\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "id": "si-8.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-08(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for spam protection\n\nmechanisms supporting and/or implementing automatic updates to spam protection mechanisms" - } - ] - } - ] - } - ] - }, - { - "id": "si-10", - "class": "SP800-53", - "title": "Information Input Validation", - "params": [ - { - "id": "si-10_odp", - "props": [ - { - "name": "alt-identifier", - "value": "si-10_prm_1" - }, - { - "name": "alt-identifier", - "value": "si-10.1_prm_1" - }, - { - "name": "alt-label", - "value": "information inputs to the system", - "class": "sp800-53" - }, - { - "name": "label", - "value": "SI-10_ODP", - "class": "sp800-53a" - } - ], - "label": "information inputs", - "guidelines": [ - { - "prose": "information inputs to the system requiring validity checks are defined;" - } - ] - } - ], - "props": [ - { - "name": "CORE", - "ns": "http://fedramp.gov/ns/oscal", - "value": "true" - }, - { - "name": "label", - "value": "SI-10", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-10" - }, - { - "name": "label", - "value": "SI-10", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-10" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - } - ], - "parts": [ - { - "id": "si-10_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Check the validity of the following information inputs: {{ insert: param, si-10_odp }}." - }, - { - "id": "si-10_gdn", - "name": "guidance", - "prose": "Checking the valid syntax and semantics of system inputs—including character set, length, numerical range, and acceptable values—verifies that inputs match specified definitions for format and content. For example, if the organization specifies that numerical values between 1-100 are the only acceptable inputs for a field in a given application, inputs of \"387,\" \"abc,\" or \"%K%\" are invalid inputs and are not accepted as input to the system. Valid inputs are likely to vary from field to field within a software application. Applications typically follow well-defined protocols that use structured messages (i.e., commands or queries) to communicate between software modules or system components. Structured messages can contain raw or unstructured data interspersed with metadata or control information. If software applications use attacker-supplied inputs to construct structured messages without properly encoding such messages, then the attacker could insert malicious commands or special characters that can cause the data to be interpreted as control information or metadata. Consequently, the module or component that receives the corrupted output will perform the wrong operations or otherwise interpret the data incorrectly. Prescreening inputs prior to passing them to interpreters prevents the content from being unintentionally interpreted as commands. Input validation ensures accurate and correct inputs and prevents attacks such as cross-site scripting and a variety of injection attacks." - }, - { - "id": "si-10_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SI-10 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "si-10_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "Validate all information inputs and document any exceptions" - } - ] - }, - { - "id": "si-10_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-10", - "class": "sp800-53a" - } - ], - "prose": "the validity of the {{ insert: param, si-10_odp }} is checked.", - "links": [ - { - "href": "#si-10_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-10_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-10-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\naccess control policy and procedures\n\nseparation of duties policy and procedures\n\nprocedures addressing information input validation\n\ndocumentation for automated tools and applications to verify the validity of information\n\nlist of information inputs requiring validity checks\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-10_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-10-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel responsible for information input validation\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "id": "si-10_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-10-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Mechanisms supporting and/or implementing validity checks on information inputs" - } - ] - } - ] - }, - { - "id": "si-11", - "class": "SP800-53", - "title": "Error Handling", - "params": [ - { - "id": "si-11_odp", - "props": [ - { - "name": "alt-identifier", - "value": "si-11_prm_1" - }, - { - "name": "label", - "value": "SI-11_ODP", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "constraints": [ - { - "description": "to include the ISSO and/or similar role within the organization" - } - ], - "guidelines": [ - { - "prose": "personnel or roles to whom error messages are to be revealed is/are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-11", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-11" - }, - { - "name": "label", - "value": "SI-11", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-11" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - } - ], - "links": [ - { - "href": "#au-2", - "rel": "related" - }, - { - "href": "#au-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-31", - "rel": "related" - }, - { - "href": "#si-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#si-15", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-11_smt", - "name": "statement", - "parts": [ - { - "id": "si-11_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Generate error messages that provide information necessary for corrective actions without revealing information that could be exploited; and" - }, - { - "id": "si-11_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Reveal error messages only to {{ insert: param, si-11_odp }}." - } - ] - }, - { - "id": "si-11_gdn", - "name": "guidance", - "prose": "Organizations consider the structure and content of error messages. The extent to which systems can handle error conditions is guided and informed by organizational policy and operational requirements. Exploitable information includes stack traces and implementation details; erroneous logon attempts with passwords mistakenly entered as the username; mission or business information that can be derived from, if not stated explicitly by, the information recorded; and personally identifiable information, such as account numbers, social security numbers, and credit card numbers. Error messages may also provide a covert channel for transmitting information." - }, - { - "id": "si-11_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-11", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-11_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-11a.", - "class": "sp800-53a" - } - ], - "prose": "error messages that provide the information necessary for corrective actions are generated without revealing information that could be exploited;", - "links": [ - { - "href": "#si-11_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-11_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-11b.", - "class": "sp800-53a" - } - ], - "prose": "error messages are revealed only to {{ insert: param, si-11_odp }}.", - "links": [ - { - "href": "#si-11_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-11_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-11_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-11-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing system error handling\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\ndocumentation providing the structure and content of error messages\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-11_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-11-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel responsible for information input validation\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "id": "si-11_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-11-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for error handling\n\nautomated mechanisms supporting and/or implementing error handling\n\nautomated mechanisms supporting and/or implementing the management of error messages" - } - ] - } - ] - }, - { - "id": "si-12", - "class": "SP800-53", - "title": "Information Management and Retention", - "props": [ - { - "name": "label", - "value": "SI-12", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-12" - }, - { - "name": "label", - "value": "SI-12", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-12" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - } - ], - "links": [ - { - "href": "#e922fc50-b1f9-469f-92ef-ed7d9803611c", - "rel": "reference" - }, - { - "href": "#27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ac-16", - "rel": "related" - }, - { - "href": "#au-5", - "rel": "related" - }, - { - "href": "#au-11", - "rel": "related" - }, - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ca-3", - "rel": "related" - }, - { - "href": "#ca-5", - "rel": "related" - }, - { - "href": "#ca-6", - "rel": "related" - }, - { - "href": "#ca-7", - "rel": "related" - }, - { - "href": "#ca-9", - "rel": "related" - }, - { - "href": "#cm-5", - "rel": "related" - }, - { - "href": "#cm-9", - "rel": "related" - }, - { - "href": "#cp-2", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - }, - { - "href": "#mp-2", - "rel": "related" - }, - { - "href": "#mp-3", - "rel": "related" - }, - { - "href": "#mp-4", - "rel": "related" - }, - { - "href": "#mp-6", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "#pl-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-4", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "#ps-2", - "rel": "related" - }, - { - "href": "#ps-6", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-3", - "rel": "related" - }, - { - "href": "#ra-2", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sr-2", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-12_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Manage and retain information within the system and information output from the system in accordance with applicable laws, executive orders, directives, regulations, policies, standards, guidelines and operational requirements." - }, - { - "id": "si-12_gdn", - "name": "guidance", - "prose": "Information management and retention requirements cover the full life cycle of information, in some cases extending beyond system disposal. Information to be retained may also include policies, procedures, plans, reports, data output from control implementation, and other types of administrative information. The National Archives and Records Administration (NARA) provides federal policy and guidance on records retention and schedules. If organizations have a records management office, consider coordinating with records management personnel. Records produced from the output of implemented controls that may require management and retention include, but are not limited to: All XX-1, [AC-6(9)](#ac-6.9), [AT-4](#at-4), [AU-12](#au-12), [CA-2](#ca-2), [CA-3](#ca-3), [CA-5](#ca-5), [CA-6](#ca-6), [CA-7](#ca-7), [CA-8](#ca-8), [CA-9](#ca-9), [CM-2](#cm-2), [CM-3](#cm-3), [CM-4](#cm-4), [CM-6](#cm-6), [CM-8](#cm-8), [CM-9](#cm-9), [CM-12](#cm-12), [CM-13](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#cm-13), [CP-2](#cp-2), [IR-6](#ir-6), [IR-8](#ir-8), [MA-2](#ma-2), [MA-4](#ma-4), [PE-2](#pe-2), [PE-8](#pe-8), [PE-16](#pe-16), [PE-17](#pe-17), [PL-2](#pl-2), [PL-4](#pl-4), [PL-7](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pl-7), [PL-8](#pl-8), [PM-5](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-5), [PM-8](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-8), [PM-9](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9), [PM-18](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-18), [PM-21](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-21), [PM-27](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-27), [PM-28](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-28), [PM-30](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-30), [PM-31](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-31), [PS-2](#ps-2), [PS-6](#ps-6), [PS-7](#ps-7), [PT-2](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-2), [PT-3](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-3), [PT-7](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pt-7), [RA-2](#ra-2), [RA-3](#ra-3), [RA-5](#ra-5), [RA-8](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ra-8), [SA-4](#sa-4), [SA-5](#sa-5), [SA-8](#sa-8), [SA-10](#sa-10), [SI-4](#si-4), [SR-2](#sr-2), [SR-4](file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sr-4), [SR-8](#sr-8)." - }, - { - "id": "si-12_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-12", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "si-12_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-12[01]", - "class": "sp800-53a" - } - ], - "prose": "information within the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements;", - "links": [ - { - "href": "#si-12_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-12_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-12[02]", - "class": "sp800-53a" - } - ], - "prose": "information within the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements;", - "links": [ - { - "href": "#si-12_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-12_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-12[03]", - "class": "sp800-53a" - } - ], - "prose": "information output from the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements;", - "links": [ - { - "href": "#si-12_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-12_obj-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SI-12[04]", - "class": "sp800-53a" - } - ], - "prose": "information output from the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.", - "links": [ - { - "href": "#si-12_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#si-12_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-12_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-12-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\npersonally identifiable information processing policy\n\nrecords retention and disposition policy\n\nrecords retention and disposition procedures\n\nfederal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements applicable to information management and retention\n\nmedia protection policy\n\nmedia protection procedures\n\naudit findings\n\nsystem security plan\n\nprivacy plan\n\nprivacy program plan\n\npersonally identifiable information inventory\n\nprivacy impact assessment\n\nprivacy risk assessment documentation\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-12_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-12-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with information and records management, retention, and disposition responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\nnetwork administrators" - } - ] - }, - { - "id": "si-12_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-12-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for information management, retention, and disposition\n\nautomated mechanisms supporting and/or implementing information management, retention, and disposition" - } - ] - } - ] - }, - { - "id": "si-16", - "class": "SP800-53", - "title": "Memory Protection", - "params": [ - { - "id": "si-16_odp", - "props": [ - { - "name": "alt-identifier", - "value": "si-16_prm_1" - }, - { - "name": "label", - "value": "SI-16_ODP", - "class": "sp800-53a" - } - ], - "label": "controls", - "guidelines": [ - { - "prose": "controls to be implemented to protect the system memory from unauthorized code execution are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SI-16", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SI-16" - }, - { - "name": "label", - "value": "SI-16", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "si-16" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#ac-25", - "rel": "related" - }, - { - "href": "#sc-3", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - } - ], - "parts": [ - { - "id": "si-16_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement the following controls to protect the system memory from unauthorized code execution: {{ insert: param, si-16_odp }}." - }, - { - "id": "si-16_gdn", - "name": "guidance", - "prose": "Some adversaries launch attacks with the intent of executing code in non-executable regions of memory or in memory locations that are prohibited. Controls employed to protect memory include data execution prevention and address space layout randomization. Data execution prevention controls can either be hardware-enforced or software-enforced with hardware enforcement providing the greater strength of mechanism." - }, - { - "id": "si-16_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SI-16", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, si-16_odp }} are implemented to protect the system memory from unauthorized code execution.", - "links": [ - { - "href": "#si-16_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "si-16_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SI-16-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "System and information integrity policy\n\nsystem and information integrity procedures\n\nprocedures addressing memory protection for the system\n\nsystem design documentation\n\nsystem configuration settings and associated documentation\n\nlist of security safeguards protecting system memory from unauthorized code execution\n\nsystem audit records\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "si-16_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SI-16-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel responsible for memory protection\n\norganizational personnel with information security responsibilities\n\nsystem/network administrators\n\nsystem developer" - } - ] - }, - { - "id": "si-16_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SI-16-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Automated mechanisms supporting and/or implementing safeguards to protect the system memory from unauthorized code execution" - } - ] - } - ] - } - ] - }, - { - "id": "sr", - "class": "family", - "title": "Supply Chain Risk Management", - "controls": [ - { - "id": "sr-1", - "class": "SP800-53", - "title": "Policy and Procedures", - "params": [ - { - "id": "sr-1_prm_1", - "props": [ - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "sr-01_odp.01" - }, - { - "name": "aggregates", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "sr-01_odp.02" - } - ], - "label": "organization-defined personnel or roles" - }, - { - "id": "sr-01_odp.01", - "props": [ - { - "name": "label", - "value": "SR-01_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "constraints": [ - { - "description": "to include chief privacy and ISSO and/or similar role or designees" - } - ], - "guidelines": [ - { - "prose": "personnel or roles to whom supply chain risk management policy is to be disseminated to is/are defined;" - } - ] - }, - { - "id": "sr-01_odp.02", - "props": [ - { - "name": "label", - "value": "SR-01_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "constraints": [ - { - "description": "to include chief privacy and ISSO and/or similar role or designees" - } - ], - "guidelines": [ - { - "prose": "personnel or roles to whom supply chain risk management procedures are disseminated to is/are defined;" - } - ] - }, - { - "id": "sr-01_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "sr-1_prm_2" - }, - { - "name": "label", - "value": "SR-01_ODP[03]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "organization-level", - "mission/business process-level", - "system-level" - ] - } - }, - { - "id": "sr-01_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "sr-1_prm_3" - }, - { - "name": "label", - "value": "SR-01_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "official", - "guidelines": [ - { - "prose": "an official to manage the development, documentation, and dissemination of the supply chain risk management policy and procedures is defined;" - } - ] - }, - { - "id": "sr-01_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "sr-1_prm_4" - }, - { - "name": "label", - "value": "SR-01_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current supply chain risk management policy is reviewed and updated is defined;" - } - ] - }, - { - "id": "sr-01_odp.06", - "props": [ - { - "name": "alt-identifier", - "value": "sr-1_prm_5" - }, - { - "name": "label", - "value": "SR-01_ODP[06]", - "class": "sp800-53a" - } - ], - "label": "events", - "guidelines": [ - { - "prose": "events that require the current supply chain risk management policy to be reviewed and updated are defined;" - } - ] - }, - { - "id": "sr-01_odp.07", - "props": [ - { - "name": "alt-identifier", - "value": "sr-1_prm_6" - }, - { - "name": "label", - "value": "SR-01_ODP[07]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which the current supply chain risk management procedure is reviewed and updated is defined;" - } - ] - }, - { - "id": "sr-01_odp.08", - "props": [ - { - "name": "alt-identifier", - "value": "sr-1_prm_7" - }, - { - "name": "label", - "value": "SR-01_ODP[08]", - "class": "sp800-53a" - } - ], - "label": "events", - "constraints": [ - { - "description": "significant changes" - } - ], - "guidelines": [ - { - "prose": "events that require the supply chain risk management procedures to be reviewed and updated are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SR-01", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SR-1" - }, - { - "name": "label", - "value": "SR-01", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sr-01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#4ff10ed3-d8fe-4246-99e3-443045e27482", - "rel": "reference" - }, - { - "href": "#0f963c17-ab5a-432a-a867-91eac550309b", - "rel": "reference" - }, - { - "href": "#21caa535-1154-4369-ba7b-32c309fee0f7", - "rel": "reference" - }, - { - "href": "#031cc4b7-9adf-4835-98f1-f1ca493519cf", - "rel": "reference" - }, - { - "href": "#c7ac44e8-10db-4b64-b2b9-9e32ec1efed0", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#4c0ec2ee-a0d6-428a-9043-4504bc3ade6f", - "rel": "reference" - }, - { - "href": "#e8e84963-14fc-4c3a-be05-b412a5d37cd2", - "rel": "reference" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-30", - "rel": "related" - }, - { - "href": "#ps-8", - "rel": "related" - }, - { - "href": "#si-12", - "rel": "related" - } - ], - "parts": [ - { - "id": "sr-1_smt", - "name": "statement", - "parts": [ - { - "id": "sr-1_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, a policy that addresses Supply Chain Risk Management MUST be associated with SR-1 part a.", - "class": "policy" - }, - { - "name": "required-attachment", - "ns": "http://fedramp.gov/ns/oscal", - "value": "In a FedRAMP SSP, at least one procedure that addresses Supply Chain Risk Management MUST be associated with SR-1 part a.", - "class": "procedure" - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop, document, and disseminate to {{ insert: param, sr-1_prm_1 }}:", - "parts": [ - { - "id": "sr-1_smt.a.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "{{ insert: param, sr-01_odp.03 }} supply chain risk management policy that:", - "parts": [ - { - "id": "sr-1_smt.a.1.a", - "name": "item", - "props": [ - { - "name": "label", - "value": "(a)" - } - ], - "prose": "Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and" - }, - { - "id": "sr-1_smt.a.1.b", - "name": "item", - "props": [ - { - "name": "label", - "value": "(b)" - } - ], - "prose": "Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and" - } - ] - }, - { - "id": "sr-1_smt.a.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures to facilitate the implementation of the supply chain risk management policy and the associated supply chain risk management controls;" - } - ] - }, - { - "id": "sr-1_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Designate an {{ insert: param, sr-01_odp.04 }} to manage the development, documentation, and dissemination of the supply chain risk management policy and procedures; and" - }, - { - "id": "sr-1_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point.", - "remarks": "This response must address all control sub-statement requirements." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Review and update the current supply chain risk management:", - "parts": [ - { - "id": "sr-1_smt.c.1", - "name": "item", - "props": [ - { - "name": "label", - "value": "1." - } - ], - "prose": "Policy {{ insert: param, sr-01_odp.05 }} and following {{ insert: param, sr-01_odp.06 }} ; and" - }, - { - "id": "sr-1_smt.c.2", - "name": "item", - "props": [ - { - "name": "label", - "value": "2." - } - ], - "prose": "Procedures {{ insert: param, sr-01_odp.07 }} and following {{ insert: param, sr-01_odp.08 }}." - } - ] - } - ] - }, - { - "id": "sr-1_gdn", - "name": "guidance", - "prose": "Supply chain risk management policy and procedures address the controls in the SR family as well as supply chain-related controls in other families that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of supply chain risk management policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to supply chain risk management policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure." - }, - { - "id": "sr-1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sr-1_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-01a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sr-1_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-01a.[01]", - "class": "sp800-53a" - } - ], - "prose": "a supply chain risk management policy is developed and documented;", - "links": [ - { - "href": "#sr-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-1_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-01a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the supply chain risk management policy is disseminated to {{ insert: param, sr-01_odp.01 }};", - "links": [ - { - "href": "#sr-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-1_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-01a.[03]", - "class": "sp800-53a" - } - ], - "prose": "supply chain risk management procedures to facilitate the implementation of the supply chain risk management policy and the associated supply chain risk management controls are developed and documented;", - "links": [ - { - "href": "#sr-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-1_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-01a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the supply chain risk management procedures are disseminated to {{ insert: param, sr-01_odp.02 }}.", - "links": [ - { - "href": "#sr-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-1_obj.a.1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-01a.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sr-1_obj.a.1.a", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-01a.01(a)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sr-1_obj.a.1.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-01a.01(a)[01]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sr-01_odp.03 }} supply chain risk management policy addresses purpose;", - "links": [ - { - "href": "#sr-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-1_obj.a.1.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-01a.01(a)[02]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sr-01_odp.03 }} supply chain risk management policy addresses scope;", - "links": [ - { - "href": "#sr-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-1_obj.a.1.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-01a.01(a)[03]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sr-01_odp.03 }} supply chain risk management policy addresses roles;", - "links": [ - { - "href": "#sr-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-1_obj.a.1.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-01a.01(a)[04]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sr-01_odp.03 }} supply chain risk management policy addresses responsibilities;", - "links": [ - { - "href": "#sr-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-1_obj.a.1.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-01a.01(a)[05]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sr-01_odp.03 }} supply chain risk management policy addresses management commitment;", - "links": [ - { - "href": "#sr-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-1_obj.a.1.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-01a.01(a)[06]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sr-01_odp.03 }} supply chain risk management policy addresses coordination among organizational entities;", - "links": [ - { - "href": "#sr-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-1_obj.a.1.a-7", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-01a.01(a)[07]", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sr-01_odp.03 }} supply chain risk management policy addresses compliance.", - "links": [ - { - "href": "#sr-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sr-1_smt.a.1.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-1_obj.a.1.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-01a.01(b)", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sr-01_odp.03 }} supply chain risk management policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines;", - "links": [ - { - "href": "#sr-1_smt.a.1.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sr-1_smt.a.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sr-1_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-1_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-01b.", - "class": "sp800-53a" - } - ], - "prose": "the {{ insert: param, sr-01_odp.04 }} is designated to manage the development, documentation, and dissemination of the supply chain risk management policy and procedures;", - "links": [ - { - "href": "#sr-1_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-1_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-01c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sr-1_obj.c.1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-01c.01", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sr-1_obj.c.1-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-01c.01[01]", - "class": "sp800-53a" - } - ], - "prose": "the current supply chain risk management policy is reviewed and updated {{ insert: param, sr-01_odp.05 }};", - "links": [ - { - "href": "#sr-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-1_obj.c.1-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-01c.01[02]", - "class": "sp800-53a" - } - ], - "prose": "the current supply chain risk management policy is reviewed and updated following {{ insert: param, sr-01_odp.06 }};", - "links": [ - { - "href": "#sr-1_smt.c.1", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sr-1_smt.c.1", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-1_obj.c.2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-01c.02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sr-1_obj.c.2-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-01c.02[01]", - "class": "sp800-53a" - } - ], - "prose": "the current supply chain risk management procedures are reviewed and updated {{ insert: param, sr-01_odp.07 }};", - "links": [ - { - "href": "#sr-1_smt.c.2", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-1_obj.c.2-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-01c.02[02]", - "class": "sp800-53a" - } - ], - "prose": "the current supply chain risk management procedures are reviewed and updated following {{ insert: param, sr-01_odp.08 }}.", - "links": [ - { - "href": "#sr-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sr-1_smt.c.2", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sr-1_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sr-1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SR-01-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Supply chain risk management policy\n\nsupply chain risk management procedures\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sr-1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SR-01-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with supply chain risk management responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\norganizational personnel with acquisition responsibilities\n\norganizational personnel with enterprise risk management responsibilities" - } - ] - } - ] - }, - { - "id": "sr-2", - "class": "SP800-53", - "title": "Supply Chain Risk Management Plan", - "params": [ - { - "id": "sr-02_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sr-2_prm_1" - }, - { - "name": "label", - "value": "SR-02_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "systems, system components, or system services", - "guidelines": [ - { - "prose": "systems, system components, or system services for which a supply chain risk management plan is developed are defined;" - } - ] - }, - { - "id": "sr-02_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sr-2_prm_2" - }, - { - "name": "label", - "value": "SR-02_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to review and update the supply chain risk management plan is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SR-02", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SR-2" - }, - { - "name": "label", - "value": "SR-02", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sr-02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#4ff10ed3-d8fe-4246-99e3-443045e27482", - "rel": "reference" - }, - { - "href": "#0f963c17-ab5a-432a-a867-91eac550309b", - "rel": "reference" - }, - { - "href": "#21caa535-1154-4369-ba7b-32c309fee0f7", - "rel": "reference" - }, - { - "href": "#031cc4b7-9adf-4835-98f1-f1ca493519cf", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#cec037f3-8aba-4c97-84b4-4082f9e515d2", - "rel": "reference" - }, - { - "href": "#e3cc0520-a366-4fc9-abc2-5272db7e3564", - "rel": "reference" - }, - { - "href": "#e8e84963-14fc-4c3a-be05-b412a5d37cd2", - "rel": "reference" - }, - { - "href": "#276bd50a-7e58-48e5-a405-8c8cb91d7a5f", - "rel": "reference" - }, - { - "href": "#e24b06cc-9129-4998-a76a-65c3d7a576ba", - "rel": "reference" - }, - { - "href": "#38ff38f0-1366-4f50-a4c9-26a39aacee16", - "rel": "reference" - }, - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#cp-4", - "rel": "related" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ma-2", - "rel": "related" - }, - { - "href": "#ma-6", - "rel": "related" - }, - { - "href": "#pe-16", - "rel": "related" - }, - { - "href": "#pl-2", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-9", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-30", - "rel": "related" - }, - { - "href": "#ra-3", - "rel": "related" - }, - { - "href": "#ra-7", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - } - ], - "parts": [ - { - "id": "sr-2_smt", - "name": "statement", - "parts": [ - { - "id": "sr-2_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop a plan for managing supply chain risks associated with the research and development, design, manufacturing, acquisition, delivery, integration, operations and maintenance, and disposal of the following systems, system components or system services: {{ insert: param, sr-02_odp.01 }};" - }, - { - "id": "sr-2_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Review and update the supply chain risk management plan {{ insert: param, sr-02_odp.02 }} or as required, to address threat, organizational or environmental changes; and" - }, - { - "id": "sr-2_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Protect the supply chain risk management plan from unauthorized disclosure and modification." - } - ] - }, - { - "id": "sr-2_gdn", - "name": "guidance", - "prose": "The dependence on products, systems, and services from external providers, as well as the nature of the relationships with those providers, present an increasing level of risk to an organization. Threat actions that may increase security or privacy risks include unauthorized production, the insertion or use of counterfeits, tampering, theft, insertion of malicious software and hardware, and poor manufacturing and development practices in the supply chain. Supply chain risks can be endemic or systemic within a system element or component, a system, an organization, a sector, or the Nation. Managing supply chain risk is a complex, multifaceted undertaking that requires a coordinated effort across an organization to build trust relationships and communicate with internal and external stakeholders. Supply chain risk management (SCRM) activities include identifying and assessing risks, determining appropriate risk response actions, developing SCRM plans to document response actions, and monitoring performance against plans. The SCRM plan (at the system-level) is implementation specific, providing policy implementation, requirements, constraints and implications. It can either be stand-alone, or incorporated into system security and privacy plans. The SCRM plan addresses managing, implementation, and monitoring of SCRM controls and the development/sustainment of systems across the SDLC to support mission and business functions.\n\nBecause supply chains can differ significantly across and within organizations, SCRM plans are tailored to the individual program, organizational, and operational contexts. Tailored SCRM plans provide the basis for determining whether a technology, service, system component, or system is fit for purpose, and as such, the controls need to be tailored accordingly. Tailored SCRM plans help organizations focus their resources on the most critical mission and business functions based on mission and business requirements and their risk environment. Supply chain risk management plans include an expression of the supply chain risk tolerance for the organization, acceptable supply chain risk mitigation strategies or controls, a process for consistently evaluating and monitoring supply chain risk, approaches for implementing and communicating the plan, a description of and justification for supply chain risk mitigation measures taken, and associated roles and responsibilities. Finally, supply chain risk management plans address requirements for developing trustworthy, secure, privacy-protective, and resilient system components and systems, including the application of the security design principles implemented as part of life cycle-based systems security engineering processes (see [SA-8](#sa-8))." - }, - { - "id": "sr-2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-02", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sr-2_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-02a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sr-2_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-02a.[01]", - "class": "sp800-53a" - } - ], - "prose": "a plan for managing supply chain risks is developed;", - "links": [ - { - "href": "#sr-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-2_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-02a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the supply chain risk management plan addresses risks associated with the research and development of {{ insert: param, sr-02_odp.01 }};", - "links": [ - { - "href": "#sr-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-2_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-02a.[03]", - "class": "sp800-53a" - } - ], - "prose": "the supply chain risk management plan addresses risks associated with the design of {{ insert: param, sr-02_odp.01 }};", - "links": [ - { - "href": "#sr-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-2_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-02a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the supply chain risk management plan addresses risks associated with the manufacturing of {{ insert: param, sr-02_odp.01 }};", - "links": [ - { - "href": "#sr-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-2_obj.a-5", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-02a.[05]", - "class": "sp800-53a" - } - ], - "prose": "the supply chain risk management plan addresses risks associated with the acquisition of {{ insert: param, sr-02_odp.01 }};", - "links": [ - { - "href": "#sr-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-2_obj.a-6", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-02a.[06]", - "class": "sp800-53a" - } - ], - "prose": "the supply chain risk management plan addresses risks associated with the delivery of {{ insert: param, sr-02_odp.01 }};", - "links": [ - { - "href": "#sr-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-2_obj.a-7", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-02a.[07]", - "class": "sp800-53a" - } - ], - "prose": "the supply chain risk management plan addresses risks associated with the integration of {{ insert: param, sr-02_odp.01 }};", - "links": [ - { - "href": "#sr-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-2_obj.a-8", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-02a.[08]", - "class": "sp800-53a" - } - ], - "prose": "the supply chain risk management plan addresses risks associated with the operation and maintenance of {{ insert: param, sr-02_odp.01 }};", - "links": [ - { - "href": "#sr-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-2_obj.a-9", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-02a.[09]", - "class": "sp800-53a" - } - ], - "prose": "the supply chain risk management plan addresses risks associated with the disposal of {{ insert: param, sr-02_odp.01 }};", - "links": [ - { - "href": "#sr-2_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sr-2_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-2_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-02b.", - "class": "sp800-53a" - } - ], - "prose": "the supply chain risk management plan is reviewed and updated {{ insert: param, sr-02_odp.02 }} or as required to address threat, organizational, or environmental changes;", - "links": [ - { - "href": "#sr-2_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-2_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-02c.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sr-2_obj.c-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-02c.[01]", - "class": "sp800-53a" - } - ], - "prose": "the supply chain risk management plan is protected from unauthorized disclosure;", - "links": [ - { - "href": "#sr-2_smt.c", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-2_obj.c-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-02c.[02]", - "class": "sp800-53a" - } - ], - "prose": "the supply chain risk management plan is protected from unauthorized modification.", - "links": [ - { - "href": "#sr-2_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sr-2_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sr-2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SR-02-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Supply chain risk management policy\n\nsupply chain risk management procedures\n\nsupply chain risk management plan\n\nsystem and services acquisition policy\n\nsystem and services acquisition procedures\n\nprocedures addressing supply chain protection\n\nprocedures for protecting the supply chain risk management plan from unauthorized disclosure and modification\n\nsystem development life cycle procedures\n\nprocedures addressing the integration of information security and privacy requirements into the acquisition process\n\nacquisition documentation\n\nservice level agreements\n\nacquisition contracts for the system, system component, or system service\n\nlist of supply chain threats\n\nlist of safeguards to be taken against supply chain threats\n\nsystem life cycle documentation\n\ninter-organizational agreements and procedures\n\nsystem security plan\n\nprivacy plan\n\nprivacy program plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sr-2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SR-02-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with acquisition responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\norganizational personnel with supply chain risk management responsibilities" - } - ] - }, - { - "id": "sr-2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SR-02-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for defining and documenting the system development life cycle (SDLC)\n\norganizational processes for identifying SDLC roles and responsibilities\n\norganizational processes for integrating supply chain risk management into the SDLC\n\nmechanisms supporting and/or implementing the SDLC" - } - ] - } - ], - "controls": [ - { - "id": "sr-2.1", - "class": "SP800-53-enhancement", - "title": "Establish SCRM Team", - "params": [ - { - "id": "sr-02.01_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sr-2.1_prm_1" - }, - { - "name": "alt-label", - "value": "personnel, roles, and responsibilities", - "class": "sp800-53" - }, - { - "name": "label", - "value": "SR-02(01)_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "personnel, roles and responsibilities", - "guidelines": [ - { - "prose": "the personnel, roles, and responsibilities of the supply chain risk management team are defined;" - } - ] - }, - { - "id": "sr-02.01_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sr-2.1_prm_2" - }, - { - "name": "label", - "value": "SR-02(01)_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "supply chain risk management activities", - "guidelines": [ - { - "prose": "supply chain risk management activities are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SR-02(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SR-2(1)" - }, - { - "name": "label", - "value": "SR-02(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sr-02.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#sr-2", - "rel": "required" - } - ], - "parts": [ - { - "id": "sr-2.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Establish a supply chain risk management team consisting of {{ insert: param, sr-02.01_odp.01 }} to lead and support the following SCRM activities: {{ insert: param, sr-02.01_odp.02 }}." - }, - { - "id": "sr-2.1_gdn", - "name": "guidance", - "prose": "To implement supply chain risk management plans, organizations establish a coordinated, team-based approach to identify and assess supply chain risks and manage these risks by using programmatic and technical mitigation techniques. The team approach enables organizations to conduct an analysis of their supply chain, communicate with internal and external partners or stakeholders, and gain broad consensus regarding the appropriate resources for SCRM. The SCRM team consists of organizational personnel with diverse roles and responsibilities for leading and supporting SCRM activities, including risk executive, information technology, contracting, information security, privacy, mission or business, legal, supply chain and logistics, acquisition, business continuity, and other relevant functions. Members of the SCRM team are involved in various aspects of the SDLC and, collectively, have an awareness of and provide expertise in acquisition processes, legal practices, vulnerabilities, threats, and attack vectors, as well as an understanding of the technical aspects and dependencies of systems. The SCRM team can be an extension of the security and privacy risk management processes or be included as part of an organizational risk management team." - }, - { - "id": "sr-2.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-02(01)", - "class": "sp800-53a" - } - ], - "prose": "a supply chain risk management team consisting of {{ insert: param, sr-02.01_odp.01 }} is established to lead and support {{ insert: param, sr-02.01_odp.02 }}.", - "links": [ - { - "href": "#sr-2.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-2.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SR-02(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Supply chain risk management policy\n\nsupply chain risk management procedures\n\nsupply chain risk management team charter documentation\n\nsupply chain risk management strategy\n\nsupply chain risk management implementation plan\n\nprocedures addressing supply chain protection\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sr-2.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SR-02(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with acquisition responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\norganizational personnel with supply chain risk management responsibilities\n\norganizational personnel with enterprise risk management responsibilities\n\nlegal counsel\n\norganizational personnel with business continuity responsibilities" - } - ] - } - ] - } - ] - }, - { - "id": "sr-3", - "class": "SP800-53", - "title": "Supply Chain Controls and Processes", - "params": [ - { - "id": "sr-03_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sr-3_prm_1" - }, - { - "name": "label", - "value": "SR-03_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "system or system component", - "guidelines": [ - { - "prose": "the system or system component requiring a process or processes to identify and address weaknesses or deficiencies is defined;" - } - ] - }, - { - "id": "sr-03_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sr-3_prm_2" - }, - { - "name": "label", - "value": "SR-03_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "supply chain personnel", - "guidelines": [ - { - "prose": "supply chain personnel with whom to coordinate the process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes is/are defined;" - } - ] - }, - { - "id": "sr-03_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "sr-3_prm_3" - }, - { - "name": "label", - "value": "SR-03_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "supply chain controls", - "guidelines": [ - { - "prose": "supply chain controls employed to protect against supply chain risks to the system, system component, or system service and to limit the harm or consequences from supply chain-related events are defined;" - } - ] - }, - { - "id": "sr-03_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "sr-3_prm_4" - }, - { - "name": "label", - "value": "SR-03_ODP[04]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "security and privacy plans", - "supply chain risk management plan", - "{{ insert: param, sr-03_odp.05 }}" - ] - } - }, - { - "id": "sr-03_odp.05", - "props": [ - { - "name": "alt-identifier", - "value": "sr-3_prm_5" - }, - { - "name": "label", - "value": "SR-03_ODP[05]", - "class": "sp800-53a" - } - ], - "label": "document", - "guidelines": [ - { - "prose": "the document identifying the selected and implemented supply chain processes and controls is defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SR-03", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SR-3" - }, - { - "name": "label", - "value": "SR-03", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sr-03" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "system" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#4ff10ed3-d8fe-4246-99e3-443045e27482", - "rel": "reference" - }, - { - "href": "#0f963c17-ab5a-432a-a867-91eac550309b", - "rel": "reference" - }, - { - "href": "#21caa535-1154-4369-ba7b-32c309fee0f7", - "rel": "reference" - }, - { - "href": "#15a95e24-65b6-4686-bc18-90855a10457d", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#e8e84963-14fc-4c3a-be05-b412a5d37cd2", - "rel": "reference" - }, - { - "href": "#e24b06cc-9129-4998-a76a-65c3d7a576ba", - "rel": "reference" - }, - { - "href": "#ca-2", - "rel": "related" - }, - { - "href": "#ma-2", - "rel": "related" - }, - { - "href": "#ma-6", - "rel": "related" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#pe-16", - "rel": "related" - }, - { - "href": "#pl-8", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-30", - "rel": "related" - }, - { - "href": "#sa-2", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "#sc-7", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-29", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-30", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sc-38", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - }, - { - "href": "#sr-6", - "rel": "related" - }, - { - "href": "#sr-9", - "rel": "related" - }, - { - "href": "#sr-11", - "rel": "related" - } - ], - "parts": [ - { - "id": "sr-3_smt", - "name": "statement", - "parts": [ - { - "id": "sr-3_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Establish a process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes of {{ insert: param, sr-03_odp.01 }} in coordination with {{ insert: param, sr-03_odp.02 }};" - }, - { - "id": "sr-3_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Employ the following controls to protect against supply chain risks to the system, system component, or system service and to limit the harm or consequences from supply chain-related events: {{ insert: param, sr-03_odp.03 }} ; and" - }, - { - "id": "sr-3_smt.c", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "c." - } - ], - "prose": "Document the selected and implemented supply chain processes and controls in {{ insert: param, sr-03_odp.04 }}." - } - ] - }, - { - "id": "sr-3_gdn", - "name": "guidance", - "prose": "Supply chain elements include organizations, entities, or tools employed for the research and development, design, manufacturing, acquisition, delivery, integration, operations and maintenance, and disposal of systems and system components. Supply chain processes include hardware, software, and firmware development processes; shipping and handling procedures; personnel security and physical security programs; configuration management tools, techniques, and measures to maintain provenance; or other programs, processes, or procedures associated with the development, acquisition, maintenance and disposal of systems and system components. Supply chain elements and processes may be provided by organizations, system integrators, or external providers. Weaknesses or deficiencies in supply chain elements or processes represent potential vulnerabilities that can be exploited by adversaries to cause harm to the organization and affect its ability to carry out its core missions or business functions. Supply chain personnel are individuals with roles and responsibilities in the supply chain." - }, - { - "id": "sr-3_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SR-3 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "sr-3_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "CSO must document and maintain the supply chain custody, including replacement devices, to ensure the integrity of the devices before being introduced to the boundary." - } - ] - }, - { - "id": "sr-3_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-03", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sr-3_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-03a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sr-3_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-03a.[01]", - "class": "sp800-53a" - } - ], - "prose": "a process or processes is/are established to identify and address weaknesses or deficiencies in the supply chain elements and processes of {{ insert: param, sr-03_odp.01 }};", - "links": [ - { - "href": "#sr-3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-3_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-03a.[02]", - "class": "sp800-53a" - } - ], - "prose": "the process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes of {{ insert: param, sr-03_odp.01 }} is/are coordinated with {{ insert: param, sr-03_odp.02 }};", - "links": [ - { - "href": "#sr-3_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sr-3_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-3_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-03b.", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sr-03_odp.03 }} are employed to protect against supply chain risks to the system, system component, or system service and to limit the harm or consequences from supply chain-related events;", - "links": [ - { - "href": "#sr-3_smt.b", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-3_obj.c", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-03c.", - "class": "sp800-53a" - } - ], - "prose": "the selected and implemented supply chain processes and controls are documented in {{ insert: param, sr-03_odp.04 }}.", - "links": [ - { - "href": "#sr-3_smt.c", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sr-3_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-3_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SR-03-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Supply chain risk management policy\n\nsupply chain risk management procedures\n\nsupply chain risk management strategy\n\nsupply chain risk management plan\n\nsystems and critical system components inventory documentation\n\nsystem and services acquisition policy\n\nsystem and services acquisition procedures\n\nprocedures addressing the integration of information security and privacy requirements into the acquisition process\n\nsolicitation documentation\n\nacquisition documentation (including purchase orders)\n\nservice level agreements\n\nacquisition contracts for systems or services\n\nrisk register documentation\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sr-3_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SR-03-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with acquisition responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\norganizational personnel with supply chain risk management responsibilities" - } - ] - }, - { - "id": "sr-3_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SR-03-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for identifying and addressing supply chain element and process deficiencies" - } - ] - } - ] - }, - { - "id": "sr-5", - "class": "SP800-53", - "title": "Acquisition Strategies, Tools, and Methods", - "params": [ - { - "id": "sr-05_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sr-5_prm_1" - }, - { - "name": "alt-label", - "value": "acquisition strategies, contract tools, and procurement methods", - "class": "sp800-53" - }, - { - "name": "label", - "value": "SR-05_ODP", - "class": "sp800-53a" - } - ], - "label": "strategies, tools, and methods", - "guidelines": [ - { - "prose": "acquisition strategies, contract tools, and procurement methods to protect against, identify, and mitigate supply chain risks are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SR-05", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SR-5" - }, - { - "name": "label", - "value": "SR-05", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sr-05" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#4ff10ed3-d8fe-4246-99e3-443045e27482", - "rel": "reference" - }, - { - "href": "#0f963c17-ab5a-432a-a867-91eac550309b", - "rel": "reference" - }, - { - "href": "#21caa535-1154-4369-ba7b-32c309fee0f7", - "rel": "reference" - }, - { - "href": "#863caf2a-978a-4260-9e8d-4a8929bce40c", - "rel": "reference" - }, - { - "href": "#15a95e24-65b6-4686-bc18-90855a10457d", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#e8e84963-14fc-4c3a-be05-b412a5d37cd2", - "rel": "reference" - }, - { - "href": "#e24b06cc-9129-4998-a76a-65c3d7a576ba", - "rel": "reference" - }, - { - "href": "#38ff38f0-1366-4f50-a4c9-26a39aacee16", - "rel": "reference" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "#sa-2", - "rel": "related" - }, - { - "href": "#sa-3", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#sa-5", - "rel": "related" - }, - { - "href": "#sa-8", - "rel": "related" - }, - { - "href": "#sa-9", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "#sr-6", - "rel": "related" - }, - { - "href": "#sr-9", - "rel": "related" - }, - { - "href": "#sr-10", - "rel": "related" - }, - { - "href": "#sr-11", - "rel": "related" - } - ], - "parts": [ - { - "id": "sr-5_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Employ the following acquisition strategies, contract tools, and procurement methods to protect against, identify, and mitigate supply chain risks: {{ insert: param, sr-05_odp }}." - }, - { - "id": "sr-5_gdn", - "name": "guidance", - "prose": "The use of the acquisition process provides an important vehicle to protect the supply chain. There are many useful tools and techniques available, including obscuring the end use of a system or system component, using blind or filtered buys, requiring tamper-evident packaging, or using trusted or controlled distribution. The results from a supply chain risk assessment can guide and inform the strategies, tools, and methods that are most applicable to the situation. Tools and techniques may provide protections against unauthorized production, theft, tampering, insertion of counterfeits, insertion of malicious software or backdoors, and poor development practices throughout the system development life cycle. Organizations also consider providing incentives for suppliers who implement controls, promote transparency into their processes and security and privacy practices, provide contract language that addresses the prohibition of tainted or counterfeit components, and restrict purchases from untrustworthy suppliers. Organizations consider providing training, education, and awareness programs for personnel regarding supply chain risk, available mitigation strategies, and when the programs should be employed. Methods for reviewing and protecting development plans, documentation, and evidence are commensurate with the security and privacy requirements of the organization. Contracts may specify documentation protection requirements." - }, - { - "id": "sr-5_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-05", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sr-5_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-05[01]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sr-05_odp }} are employed to protect against supply chain risks;", - "links": [ - { - "href": "#sr-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-5_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-05[02]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sr-05_odp }} are employed to identify supply chain risks;", - "links": [ - { - "href": "#sr-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-5_obj-3", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-05[03]", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sr-05_odp }} are employed to mitigate supply chain risks.", - "links": [ - { - "href": "#sr-5_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sr-5_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-5_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SR-05-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Supply chain risk management policy\n\nsupply chain risk management procedures\n\nsupply chain risk management plan\n\nsystem and services acquisition policy\n\nsystem and services acquisition procedures\n\nprocedures addressing supply chain protection\n\nprocedures addressing the integration of information security and privacy requirements into the acquisition process\n\nsolicitation documentation\n\nacquisition documentation (including purchase orders)\n\nservice level agreements\n\nacquisition contracts for systems, system components, or services\n\ndocumentation of training, education, and awareness programs for personnel regarding supply chain risk\n\nsystem security plan\n\nprivacy plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sr-5_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SR-05-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with acquisition responsibilities\n\norganizational personnel with information security and privacy responsibilities\n\norganizational personnel with supply chain risk management responsibilities" - } - ] - }, - { - "id": "sr-5_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SR-05-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for defining and employing tailored acquisition strategies, contract tools, and procurement methods\n\nmechanisms supporting and/or implementing the definition and employment of tailored acquisition strategies, contract tools, and procurement methods" - } - ] - } - ] - }, - { - "id": "sr-6", - "class": "SP800-53", - "title": "Supplier Assessments and Reviews", - "params": [ - { - "id": "sr-06_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sr-6_prm_1" - }, - { - "name": "label", - "value": "SR-06_ODP", - "class": "sp800-53a" - } - ], - "label": "frequency", - "constraints": [ - { - "description": "at least annually" - } - ], - "guidelines": [ - { - "prose": "the frequency at which to assess and review the supply chain-related risks associated with suppliers or contractors and the systems, system components, or system services they provide is defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SR-06", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SR-6" - }, - { - "name": "label", - "value": "SR-06", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sr-06" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#4ff10ed3-d8fe-4246-99e3-443045e27482", - "rel": "reference" - }, - { - "href": "#0f963c17-ab5a-432a-a867-91eac550309b", - "rel": "reference" - }, - { - "href": "#21caa535-1154-4369-ba7b-32c309fee0f7", - "rel": "reference" - }, - { - "href": "#863caf2a-978a-4260-9e8d-4a8929bce40c", - "rel": "reference" - }, - { - "href": "#15a95e24-65b6-4686-bc18-90855a10457d", - "rel": "reference" - }, - { - "href": "#678e3d6c-150b-4393-aec5-6e3481eb1e00", - "rel": "reference" - }, - { - "href": "#eea3c092-42ed-4382-a6f4-1adadef01b9d", - "rel": "reference" - }, - { - "href": "#7c37a38d-21d7-40d8-bc3d-b5e27eac17e1", - "rel": "reference" - }, - { - "href": "#a295ca19-8c75-4b4c-8800-98024732e181", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#e8e84963-14fc-4c3a-be05-b412a5d37cd2", - "rel": "reference" - }, - { - "href": "#e24b06cc-9129-4998-a76a-65c3d7a576ba", - "rel": "reference" - }, - { - "href": "#38ff38f0-1366-4f50-a4c9-26a39aacee16", - "rel": "reference" - }, - { - "href": "#sr-3", - "rel": "related" - }, - { - "href": "#sr-5", - "rel": "related" - } - ], - "parts": [ - { - "id": "sr-6_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Assess and review the supply chain-related risks associated with suppliers or contractors and the system, system component, or system service they provide {{ insert: param, sr-06_odp }}." - }, - { - "id": "sr-6_gdn", - "name": "guidance", - "prose": "An assessment and review of supplier risk includes security and supply chain risk management processes, foreign ownership, control or influence (FOCI), and the ability of the supplier to effectively assess subordinate second-tier and third-tier suppliers and contractors. The reviews may be conducted by the organization or by an independent third party. The reviews consider documented processes, documented controls, all-source intelligence, and publicly available information related to the supplier or contractor. Organizations can use open-source information to monitor for indications of stolen information, poor development and quality control practices, information spillage, or counterfeits. In some cases, it may be appropriate or required to share assessment and review results with other organizations in accordance with any applicable rules, policies, or inter-organizational agreements or contracts." - }, - { - "id": "sr-6_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SR-6 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "sr-6_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "CSOs must ensure that their supply chain vendors build and test their systems in alignment with NIST SP 800-171 or a commensurate security and compliance framework. CSOs must ensure that vendors are compliant with physical facility access and logical access controls to supplied products." - } - ] - }, - { - "id": "sr-6_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "TEST", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-06", - "class": "sp800-53a" - } - ], - "prose": "the supply chain-related risks associated with suppliers or contractors and the systems, system components, or system services they provide are assessed and reviewed {{ insert: param, sr-06_odp }}.", - "links": [ - { - "href": "#sr-6_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-6_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SR-06-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Supply chain risk management policy and procedures\n\nsupply chain risk management strategy\n\nsupply chain risk management plan\n\nsystem and services acquisition policy\n\nprocedures addressing supply chain protection\n\nprocedures addressing the integration of information security requirements into the acquisition process\n\nrecords of supplier due diligence reviews\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sr-6_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SR-06-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain protection responsibilities" - } - ] - }, - { - "id": "sr-6_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SR-06-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for conducting supplier reviews\n\nmechanisms supporting and/or implementing supplier reviews" - } - ] - } - ] - }, - { - "id": "sr-8", - "class": "SP800-53", - "title": "Notification Agreements", - "params": [ - { - "id": "sr-08_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sr-8_prm_1" - }, - { - "name": "label", - "value": "SR-08_ODP[01]", - "class": "sp800-53a" - } - ], - "constraints": [ - { - "description": "notification of supply chain compromises and results of assessment or audits" - } - ] - }, - { - "id": "sr-08_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sr-8_prm_2" - }, - { - "name": "alt-label", - "value": "information", - "class": "sp800-53" - }, - { - "name": "label", - "value": "SR-08_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "results of assessments or audits", - "guidelines": [ - { - "prose": "information for which agreements and procedures are to be established are defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SR-08", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SR-8" - }, - { - "name": "label", - "value": "SR-08", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sr-08" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#4ff10ed3-d8fe-4246-99e3-443045e27482", - "rel": "reference" - }, - { - "href": "#0f963c17-ab5a-432a-a867-91eac550309b", - "rel": "reference" - }, - { - "href": "#21caa535-1154-4369-ba7b-32c309fee0f7", - "rel": "reference" - }, - { - "href": "#863caf2a-978a-4260-9e8d-4a8929bce40c", - "rel": "reference" - }, - { - "href": "#08b07465-dbdc-48d6-8a0b-37279602ac16", - "rel": "reference" - }, - { - "href": "#e8e84963-14fc-4c3a-be05-b412a5d37cd2", - "rel": "reference" - }, - { - "href": "#e24b06cc-9129-4998-a76a-65c3d7a576ba", - "rel": "reference" - }, - { - "href": "#ir-4", - "rel": "related" - }, - { - "href": "#ir-6", - "rel": "related" - }, - { - "href": "#ir-8", - "rel": "related" - } - ], - "parts": [ - { - "id": "sr-8_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Establish agreements and procedures with entities involved in the supply chain for the system, system component, or system service for the {{ insert: param, sr-08_odp.01 }}." - }, - { - "id": "sr-8_gdn", - "name": "guidance", - "prose": "The establishment of agreements and procedures facilitates communications among supply chain entities. Early notification of compromises and potential compromises in the supply chain that can potentially adversely affect or have adversely affected organizational systems or system components is essential for organizations to effectively respond to such incidents. The results of assessments or audits may include open-source information that contributed to a decision or result and could be used to help the supply chain entity resolve a concern or improve its processes." - }, - { - "id": "sr-8_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SR-8 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "sr-8_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "CSOs must ensure and document how they receive notifications from their supply chain vendor of newly discovered vulnerabilities including zero-day vulnerabilities." - } - ] - }, - { - "id": "sr-8_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-08", - "class": "sp800-53a" - } - ], - "prose": "agreements and procedures are established with entities involved in the supply chain for the system, system components, or system service for {{ insert: param, sr-08_odp.01 }}.", - "links": [ - { - "href": "#sr-8_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-8_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SR-08-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Supply chain risk management policy and procedures\n\nsupply chain risk management plan\n\nsystem and services acquisition policy\n\nprocedures addressing supply chain protection\n\nacquisition documentation\n\nservice level agreements\n\nacquisition contracts for the system, system component, or system service\n\ninter-organizational agreements and procedures\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sr-8_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SR-08-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and service acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain risk management responsibilities" - } - ] - }, - { - "id": "sr-8_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SR-08-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for establishing inter-organizational agreements and procedures with supply chain entities" - } - ] - } - ] - }, - { - "id": "sr-9", - "class": "SP800-53", - "title": "Tamper Resistance and Detection", - "props": [ - { - "name": "label", - "value": "SR-09", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SR-9" - }, - { - "name": "label", - "value": "SR-09", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sr-09" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#15a95e24-65b6-4686-bc18-90855a10457d", - "rel": "reference" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-30", - "rel": "related" - }, - { - "href": "#sa-15", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - }, - { - "href": "#sr-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sr-4", - "rel": "related" - }, - { - "href": "#sr-5", - "rel": "related" - }, - { - "href": "#sr-10", - "rel": "related" - }, - { - "href": "#sr-11", - "rel": "related" - } - ], - "parts": [ - { - "id": "sr-9_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Implement a tamper protection program for the system, system component, or system service." - }, - { - "id": "sr-9_gdn", - "name": "guidance", - "prose": "Anti-tamper technologies, tools, and techniques provide a level of protection for systems, system components, and services against many threats, including reverse engineering, modification, and substitution. Strong identification combined with tamper resistance and/or tamper detection is essential to protecting systems and components during distribution and when in use." - }, - { - "id": "sr-9_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SR-9 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "sr-9_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "CSOs must ensure vendors provide authenticity of software and patches supplied to the service provider including documenting the safeguards in place." - } - ] - }, - { - "id": "sr-9_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-09", - "class": "sp800-53a" - } - ], - "prose": "a tamper protection program is implemented for the system, system component, or system service.", - "links": [ - { - "href": "#sr-9_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-9_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SR-09-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Supply chain risk management policy and procedures\n\nsupply chain risk management plan\n\nsystem and services acquisition policy\n\nprocedures addressing supply chain protection\n\nprocedures addressing tamper resistance and detection\n\ntamper protection program documentation\n\ntamper protection tools and techniques documentation\n\ntamper resistance and detection tools and techniques documentation\n\nacquisition documentation\n\nservice level agreements\n\nacquisition contracts for the system, system component, or system service\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sr-9_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SR-09-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with tamper protection program responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain risk management responsibilities" - } - ] - }, - { - "id": "sr-9_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SR-09-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for the implementation of the tamper protection program\n\nmechanisms supporting and/or implementing the tamper protection program" - } - ] - } - ], - "controls": [ - { - "id": "sr-9.1", - "class": "SP800-53-enhancement", - "title": "Multiple Stages of System Development Life Cycle", - "props": [ - { - "name": "label", - "value": "SR-09(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SR-9(1)" - }, - { - "name": "label", - "value": "SR-09(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sr-09.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#sr-9", - "rel": "required" - }, - { - "href": "#sa-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "sr-9.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Employ anti-tamper technologies, tools, and techniques throughout the system development life cycle." - }, - { - "id": "sr-9.1_gdn", - "name": "guidance", - "prose": "The system development life cycle includes research and development, design, manufacturing, acquisition, delivery, integration, operations and maintenance, and disposal. Organizations use a combination of hardware and software techniques for tamper resistance and detection. Organizations use obfuscation and self-checking to make reverse engineering and modifications more difficult, time-consuming, and expensive for adversaries. The customization of systems and system components can make substitutions easier to detect and therefore limit damage." - }, - { - "id": "sr-9.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-09(01)", - "class": "sp800-53a" - } - ], - "prose": "anti-tamper technologies, tools, and techniques are employed throughout the system development life cycle.", - "links": [ - { - "href": "#sr-9.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-9.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SR-09(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Supply chain risk management policy and procedures\n\nsupply chain risk management plan\n\nsystem and services acquisition policy\n\nprocedures addressing tamper resistance and detection\n\ntamper protection program documentation\n\ntamper protection tools and techniques documentation\n\ntamper resistance and detection tools (technologies) and techniques documentation\n\nsystem development life cycle documentation\n\nprocedures addressing supply chain protection\n\nsystem development life cycle procedures\n\nacquisition documentation\n\nservice level agreements\n\nacquisition contracts for the system, system component, or system service\n\ninter-organizational agreements and procedures\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sr-9.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SR-09(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain risk management responsibilities\n\norganizational personnel with SDLC responsibilities" - } - ] - }, - { - "id": "sr-9.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SR-09(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for employing anti-tamper technologies\n\nmechanisms supporting and/or implementing anti-tamper technologies" - } - ] - } - ] - } - ] - }, - { - "id": "sr-10", - "class": "SP800-53", - "title": "Inspection of Systems or Components", - "params": [ - { - "id": "sr-10_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sr-10_prm_4" - }, - { - "name": "label", - "value": "SR-10_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "systems or system components", - "guidelines": [ - { - "prose": "systems or system components that require inspection are defined;" - } - ] - }, - { - "id": "sr-10_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sr-10_prm_1" - }, - { - "name": "label", - "value": "SR-10_ODP[02]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "at random", - "at {{ insert: param, sr-10_odp.03 }}", - "upon {{ insert: param, sr-10_odp.04 }}" - ] - } - }, - { - "id": "sr-10_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "sr-10_prm_2" - }, - { - "name": "label", - "value": "SR-10_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "frequency", - "guidelines": [ - { - "prose": "frequency at which to inspect systems or system components is defined (if selected);" - } - ] - }, - { - "id": "sr-10_odp.04", - "props": [ - { - "name": "alt-identifier", - "value": "sr-10_prm_3" - }, - { - "name": "label", - "value": "SR-10_ODP[04]", - "class": "sp800-53a" - } - ], - "label": "indications of need for inspection", - "guidelines": [ - { - "prose": "indications of the need for an inspection of systems or system components are defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SR-10", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SR-10" - }, - { - "name": "label", - "value": "SR-10", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sr-10" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#15a95e24-65b6-4686-bc18-90855a10457d", - "rel": "reference" - }, - { - "href": "#at-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#pm-30", - "rel": "related" - }, - { - "href": "#si-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - }, - { - "href": "#sr-3", - "rel": "related" - }, - { - "href": "file:/home/brian/src/fedramp-resources/baselines/rev5/xml/FedRAMP_rev5_catalog_tailoring_profile.xml#sr-4", - "rel": "related" - }, - { - "href": "#sr-5", - "rel": "related" - }, - { - "href": "#sr-9", - "rel": "related" - }, - { - "href": "#sr-11", - "rel": "related" - } - ], - "parts": [ - { - "id": "sr-10_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Inspect the following systems or system components {{ insert: param, sr-10_odp.02 }} to detect tampering: {{ insert: param, sr-10_odp.01 }}." - }, - { - "id": "sr-10_gdn", - "name": "guidance", - "prose": "The inspection of systems or systems components for tamper resistance and detection addresses physical and logical tampering and is applied to systems and system components removed from organization-controlled areas. Indications of a need for inspection include changes in packaging, specifications, factory location, or entity in which the part is purchased, and when individuals return from travel to high-risk locations." - }, - { - "id": "sr-10_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-10", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sr-10_odp.01 }} are inspected {{ insert: param, sr-10_odp.02 }} to detect tampering.", - "links": [ - { - "href": "#sr-10_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-10_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SR-10-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Supply chain risk management policy and procedures\n\nsupply chain risk management plan\n\nsystem and services acquisition policy\n\nrecords of random inspections\n\ninspection reports/results\n\nassessment reports/results\n\nacquisition documentation\n\nservice level agreements\n\nacquisition contracts for the system, system component, or system service\n\ninter-organizational agreements and procedures\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sr-10_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SR-10-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain risk management responsibilities" - } - ] - }, - { - "id": "sr-10_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SR-10-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for establishing inter-organizational agreements and procedures with supply chain entities\n\norganizational processes to inspect for tampering" - } - ] - } - ] - }, - { - "id": "sr-11", - "class": "SP800-53", - "title": "Component Authenticity", - "params": [ - { - "id": "sr-11_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sr-11_prm_1" - }, - { - "name": "label", - "value": "SR-11_ODP[01]", - "class": "sp800-53a" - } - ], - "select": { - "how-many": "one-or-more", - "choice": [ - "source of counterfeit component", - "{{ insert: param, sr-11_odp.02 }}", - "{{ insert: param, sr-11_odp.03 }}" - ] - } - }, - { - "id": "sr-11_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sr-11_prm_2" - }, - { - "name": "label", - "value": "SR-11_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "external reporting organizations", - "guidelines": [ - { - "prose": "external reporting organizations to whom counterfeit system components are to be reported is/are defined (if selected);" - } - ] - }, - { - "id": "sr-11_odp.03", - "props": [ - { - "name": "alt-identifier", - "value": "sr-11_prm_3" - }, - { - "name": "label", - "value": "SR-11_ODP[03]", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles to whom counterfeit system components are to be reported is/are defined (if selected);" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SR-11", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SR-11" - }, - { - "name": "label", - "value": "SR-11", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sr-11" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#15a95e24-65b6-4686-bc18-90855a10457d", - "rel": "reference" - }, - { - "href": "#pe-3", - "rel": "related" - }, - { - "href": "#sa-4", - "rel": "related" - }, - { - "href": "#si-7", - "rel": "related" - }, - { - "href": "#sr-9", - "rel": "related" - }, - { - "href": "#sr-10", - "rel": "related" - } - ], - "parts": [ - { - "id": "sr-11_smt", - "name": "statement", - "parts": [ - { - "id": "sr-11_smt.a", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "a." - } - ], - "prose": "Develop and implement anti-counterfeit policy and procedures that include the means to detect and prevent counterfeit components from entering the system; and" - }, - { - "id": "sr-11_smt.b", - "name": "item", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "label", - "value": "b." - } - ], - "prose": "Report counterfeit system components to {{ insert: param, sr-11_odp.01 }}." - } - ] - }, - { - "id": "sr-11_gdn", - "name": "guidance", - "prose": "Sources of counterfeit components include manufacturers, developers, vendors, and contractors. Anti-counterfeiting policies and procedures support tamper resistance and provide a level of protection against the introduction of malicious code. External reporting organizations include CISA." - }, - { - "id": "sr-11_fr", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "title": "SR-11 Additional FedRAMP Requirements and Guidance", - "parts": [ - { - "id": "sr-11_fr_smt.1", - "name": "item", - "ns": "http://fedramp.gov/ns/oscal", - "props": [ - { - "name": "label", - "value": "Requirement:" - } - ], - "prose": "CSOs must ensure that their supply chain vendors provide authenticity of software and patches and the vendor must have a plan to protect the development pipeline." - } - ] - }, - { - "id": "sr-11_obj", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-11", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sr-11_obj.a", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-11a.", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sr-11_obj.a-1", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-11a.[01]", - "class": "sp800-53a" - } - ], - "prose": "an anti-counterfeit policy is developed and implemented;", - "links": [ - { - "href": "#sr-11_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-11_obj.a-2", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-11a.[02]", - "class": "sp800-53a" - } - ], - "prose": "anti-counterfeit procedures are developed and implemented;", - "links": [ - { - "href": "#sr-11_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-11_obj.a-3", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-11a.[03]", - "class": "sp800-53a" - } - ], - "prose": "the anti-counterfeit procedures include the means to detect counterfeit components entering the system;", - "links": [ - { - "href": "#sr-11_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-11_obj.a-4", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-11a.[04]", - "class": "sp800-53a" - } - ], - "prose": "the anti-counterfeit procedures include the means to prevent counterfeit components from entering the system;", - "links": [ - { - "href": "#sr-11_smt.a", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sr-11_smt.a", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-11_obj.b", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-11b.", - "class": "sp800-53a" - } - ], - "prose": "counterfeit system components are reported to {{ insert: param, sr-11_odp.01 }}.", - "links": [ - { - "href": "#sr-11_smt.b", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sr-11_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-11_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SR-11-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Supply chain risk management policy and procedures\n\nsupply chain risk management plan\n\nsystem and services acquisition policy\n\nanti-counterfeit plan\n\nanti-counterfeit policy and procedures\n\nmedia disposal policy\n\nmedia protection policy\n\nincident response policy\n\nreports notifying developers, manufacturers, vendors, contractors, and/or external reporting organizations of counterfeit system components\n\nacquisition documentation\n\nservice level agreements\n\nacquisition contracts for the system, system component, or system service\n\ninter-organizational agreements and procedures\n\nrecords of reported counterfeit system components\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sr-11_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SR-11-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and service acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain risk management responsibilities\n\norganizational personnel with responsibilities for anti-counterfeit policies, procedures, and reporting" - } - ] - }, - { - "id": "sr-11_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SR-11-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for counterfeit prevention, detection, and reporting\n\nmechanisms supporting and/or implementing anti-counterfeit detection, prevention, and reporting" - } - ] - } - ], - "controls": [ - { - "id": "sr-11.1", - "class": "SP800-53-enhancement", - "title": "Anti-counterfeit Training", - "params": [ - { - "id": "sr-11.01_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sr-11.1_prm_1" - }, - { - "name": "label", - "value": "SR-11(01)_ODP", - "class": "sp800-53a" - } - ], - "label": "personnel or roles", - "guidelines": [ - { - "prose": "personnel or roles requiring training to detect counterfeit system components (including hardware, software, and firmware) is/are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SR-11(01)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SR-11(1)" - }, - { - "name": "label", - "value": "SR-11(01)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sr-11.01" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#sr-11", - "rel": "required" - }, - { - "href": "#at-3", - "rel": "related" - } - ], - "parts": [ - { - "id": "sr-11.1_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Train {{ insert: param, sr-11.01_odp }} to detect counterfeit system components (including hardware, software, and firmware)." - }, - { - "id": "sr-11.1_gdn", - "name": "guidance", - "prose": "None." - }, - { - "id": "sr-11.1_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-11(01)", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sr-11.01_odp }} are trained to detect counterfeit system components (including hardware, software, and firmware).", - "links": [ - { - "href": "#sr-11.1_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-11.1_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SR-11(01)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Supply chain risk management policy and procedures\n\nsupply chain risk management plan\n\nsystem and services acquisition policy\n\nanti-counterfeit plan\n\nanti-counterfeit policy and procedures\n\nmedia disposal policy\n\nmedia protection policy\n\nincident response policy\n\ntraining materials addressing counterfeit system components\n\ntraining records on the detection and prevention of counterfeit components entering the system\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sr-11.1_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SR-11(01)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with information security responsibilities\n\norganizational personnel with supply chain risk management responsibilities\n\norganizational personnel with responsibilities for anti-counterfeit policies, procedures, and training" - } - ] - }, - { - "id": "sr-11.1_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SR-11(01)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for anti-counterfeit training" - } - ] - } - ] - }, - { - "id": "sr-11.2", - "class": "SP800-53-enhancement", - "title": "Configuration Control for Component Service and Repair", - "params": [ - { - "id": "sr-11.02_odp", - "props": [ - { - "name": "alt-identifier", - "value": "sr-11.2_prm_1" - }, - { - "name": "label", - "value": "SR-11(02)_ODP", - "class": "sp800-53a" - } - ], - "label": "system components", - "constraints": [ - { - "description": "all" - } - ], - "guidelines": [ - { - "prose": "system components requiring configuration control are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SR-11(02)", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SR-11(2)" - }, - { - "name": "label", - "value": "SR-11(02)", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sr-11.02" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#sr-11", - "rel": "required" - }, - { - "href": "#cm-3", - "rel": "related" - }, - { - "href": "#ma-2", - "rel": "related" - }, - { - "href": "#ma-4", - "rel": "related" - }, - { - "href": "#sa-10", - "rel": "related" - } - ], - "parts": [ - { - "id": "sr-11.2_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Maintain configuration control over the following system components awaiting service or repair and serviced or repaired components awaiting return to service: {{ insert: param, sr-11.02_odp }}." - }, - { - "id": "sr-11.2_gdn", - "name": "guidance", - "prose": "None." - }, - { - "id": "sr-11.2_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-11(02)", - "class": "sp800-53a" - } - ], - "parts": [ - { - "id": "sr-11.2_obj-1", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-11(02)[01]", - "class": "sp800-53a" - } - ], - "prose": "configuration control over {{ insert: param, sr-11.02_odp }} awaiting service or repair is maintained;", - "links": [ - { - "href": "#sr-11.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-11.2_obj-2", - "name": "assessment-objective", - "props": [ - { - "name": "label", - "value": "SR-11(02)[02]", - "class": "sp800-53a" - } - ], - "prose": "configuration control over serviced or repaired {{ insert: param, sr-11.02_odp }} awaiting return to service is maintained.", - "links": [ - { - "href": "#sr-11.2_smt", - "rel": "assessment-for" - } - ] - } - ], - "links": [ - { - "href": "#sr-11.2_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-11.2_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SR-11(02)-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Supply chain risk management policy and procedures\n\nsupply chain risk management plan\n\nconfiguration control procedures\n\nacquisition documentation\n\nservice level agreements\n\nacquisition contracts for the system component\n\ninter-organizational agreements and procedures\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sr-11.2_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SR-11(02)-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system and services acquisition responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain risk management responsibilities" - } - ] - }, - { - "id": "sr-11.2_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SR-11(02)-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational processes for establishing inter-organizational agreements and procedures with supply chain entities\n\norganizational configuration control processes" - } - ] - } - ] - } - ] - }, - { - "id": "sr-12", - "class": "SP800-53", - "title": "Component Disposal", - "params": [ - { - "id": "sr-12_odp.01", - "props": [ - { - "name": "alt-identifier", - "value": "sr-12_prm_1" - }, - { - "name": "label", - "value": "SR-12_ODP[01]", - "class": "sp800-53a" - } - ], - "label": "data, documentation, tools, or system components", - "guidelines": [ - { - "prose": "data, documentation, tools, or system components to be disposed of are defined;" - } - ] - }, - { - "id": "sr-12_odp.02", - "props": [ - { - "name": "alt-identifier", - "value": "sr-12_prm_2" - }, - { - "name": "label", - "value": "SR-12_ODP[02]", - "class": "sp800-53a" - } - ], - "label": "techniques and methods", - "guidelines": [ - { - "prose": "techniques and methods for disposing of data, documentation, tools, or system components are defined;" - } - ] - } - ], - "props": [ - { - "name": "label", - "value": "SR-12", - "class": "zero-padded" - }, - { - "name": "label", - "value": "SR-12" - }, - { - "name": "label", - "value": "SR-12", - "class": "sp800-53a" - }, - { - "name": "sort-id", - "value": "sr-12" - }, - { - "name": "implementation-level", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "organization" - }, - { - "name": "contributes-to-assurance", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "true" - } - ], - "links": [ - { - "href": "#mp-6", - "rel": "related" - } - ], - "parts": [ - { - "id": "sr-12_smt", - "name": "statement", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - } - ], - "prose": "Dispose of {{ insert: param, sr-12_odp.01 }} using the following techniques and methods: {{ insert: param, sr-12_odp.02 }}." - }, - { - "id": "sr-12_gdn", - "name": "guidance", - "prose": "Data, documentation, tools, or system components can be disposed of at any time during the system development life cycle (not only in the disposal or retirement phase of the life cycle). For example, disposal can occur during research and development, design, prototyping, or operations/maintenance and include methods such as disk cleaning, removal of cryptographic keys, partial reuse of components. Opportunities for compromise during disposal affect physical and logical data, including system documentation in paper-based or digital files; shipping and delivery documentation; memory sticks with software code; or complete routers or servers that include permanent media, which contain sensitive or proprietary information. Additionally, proper disposal of system components helps to prevent such components from entering the gray market." - }, - { - "id": "sr-12_obj", - "name": "assessment-objective", - "props": [ - { - "name": "response-point", - "ns": "http://fedramp.gov/ns/oscal", - "value": "You must fill in this response point." - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "EXAMINE", - "class": "fedramp" - }, - { - "name": "method", - "ns": "http://fedramp.gov/ns/oscal", - "value": "INTERVIEW", - "class": "fedramp" - }, - { - "name": "label", - "value": "SR-12", - "class": "sp800-53a" - } - ], - "prose": "{{ insert: param, sr-12_odp.01 }} are disposed of using {{ insert: param, sr-12_odp.02 }}.", - "links": [ - { - "href": "#sr-12_smt", - "rel": "assessment-for" - } - ] - }, - { - "id": "sr-12_asm-examine", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "EXAMINE" - }, - { - "name": "label", - "value": "SR-12-Examine", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Supply chain risk management policy and procedures\n\nsupply chain risk management plan\n\ndisposal procedures addressing supply chain protection\n\nmedia disposal policy\n\nmedia protection policy\n\ndisposal records for system components\n\ndocumentation of the system components identified for disposal\n\ndocumentation of the disposal techniques and methods employed for system components\n\nsystem security plan\n\nother relevant documents or records" - } - ] - }, - { - "id": "sr-12_asm-interview", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "INTERVIEW" - }, - { - "name": "label", - "value": "SR-12-Interview", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational personnel with system component disposal responsibilities\n\norganizational personnel with information security responsibilities\n\norganizational personnel with supply chain protection responsibilities" - } - ] - }, - { - "id": "sr-12_asm-test", - "name": "assessment-method", - "props": [ - { - "name": "method", - "ns": "http://csrc.nist.gov/ns/rmf", - "value": "TEST" - }, - { - "name": "label", - "value": "SR-12-Test", - "class": "sp800-53a" - } - ], - "parts": [ - { - "name": "assessment-objects", - "prose": "Organizational techniques and methods for system component disposal\n\nmechanisms supporting and/or implementing system component disposal" - } - ] - } - ] - } - ] - } - ], - "back-matter": { - "resources": [ - { - "uuid": "91f992fb-f668-4c91-a50f-0f05b95ccee3", - "title": "32 CFR 2002", - "citation": { - "text": "Code of Federal Regulations, Title 32, *Controlled Unclassified Information* (32 C.F.R. 2002)." - }, - "rlinks": [ - { - "href": "https://www.federalregister.gov/documents/2016/09/14/2016-21665/controlled-unclassified-information" - } - ] - }, - { - "uuid": "0f963c17-ab5a-432a-a867-91eac550309b", - "title": "41 CFR 201", - "citation": { - "text": "\"Federal Acquisition Supply Chain Security Act; Rule,\" 85 Federal Register 54263 (September 1, 2020), pp 54263-54271." - }, - "rlinks": [ - { - "href": "https://www.federalregister.gov/d/2020-18939" - } - ] - }, - { - "uuid": "a5ef5e56-5c1a-4911-b419-37dddc1b3581", - "title": "5 CFR 731", - "citation": { - "text": "Code of Federal Regulations, Title 5, *Administrative Personnel* , Section 731.106, *Designation of Public Trust Positions and Investigative Requirements* (5 C.F.R. 731.106)." - }, - "rlinks": [ - { - "href": "https://www.govinfo.gov/content/pkg/CFR-2012-title5-vol2/pdf/CFR-2012-title5-vol2-sec731-106.pdf" - } - ] - }, - { - "uuid": "031cc4b7-9adf-4835-98f1-f1ca493519cf", - "title": "CNSSD 505", - "citation": { - "text": "Committee on National Security Systems Directive No. 505, *Supply Chain Risk Management (SCRM)* , August 2017." - }, - "rlinks": [ - { - "href": "https://www.cnss.gov/CNSS/issuances/Directives.cfm" - } - ] - }, - { - "uuid": "4e4fbc93-333d-45e6-a875-de36b878b6b9", - "title": "CNSSI 1253", - "citation": { - "text": "Committee on National Security Systems Instruction No. 1253, *Security Categorization and Control Selection for National Security Systems* , March 2014." - }, - "rlinks": [ - { - "href": "https://www.cnss.gov/CNSS/issuances/Instructions.cfm" - } - ] - }, - { - "uuid": "4f42ee6e-86cc-403b-a51f-76c2b4f81b54", - "title": "DHS TIC", - "citation": { - "text": "Department of Homeland Security, *Trusted Internet Connections (TIC)*." - }, - "rlinks": [ - { - "href": "https://www.dhs.gov/trusted-internet-connections" - } - ] - }, - { - "uuid": "aa66e14f-e7cb-4a37-99d2-07578dfd4608", - "title": "DOD STIG", - "citation": { - "text": "Defense Information Systems Agency, *Security Technical Implementation Guides (STIG)*." - }, - "rlinks": [ - { - "href": "https://public.cyber.mil/stigs" - } - ] - }, - { - "uuid": "55b0c93a-5e48-457a-baa6-5ce81c239c49", - "title": "EO 13526", - "citation": { - "text": "Executive Order 13526, *Classified National Security Information* , December 2009." - }, - "rlinks": [ - { - "href": "https://www.archives.gov/isoo/policy-documents/cnsi-eo.html" - } - ] - }, - { - "uuid": "34a5571f-e252-4309-a8a1-2fdb2faefbcd", - "title": "EO 13556", - "citation": { - "text": "Executive Order 13556, *Controlled Unclassified Information* , November 2010." - }, - "rlinks": [ - { - "href": "https://obamawhitehouse.archives.gov/the-press-office/2010/11/04/executive-order-13556-controlled-unclassified-information" - } - ] - }, - { - "uuid": "0af071a6-cf8e-48ee-8c82-fe91efa20f94", - "title": "EO 13587", - "citation": { - "text": "Executive Order 13587, *Structural Reforms to Improve the Security of Classified Networks and the Responsible Sharing and Safeguarding of Classified Information* , October 2011." - }, - "rlinks": [ - { - "href": "https://obamawhitehouse.archives.gov/the-press-office/2011/10/07/executive-order-13587-structural-reforms-improve-security-classified-net" - } - ] - }, - { - "uuid": "21caa535-1154-4369-ba7b-32c309fee0f7", - "title": "EO 13873", - "citation": { - "text": "Executive Order 13873, *Executive Order on Securing the Information and Communications Technology and Services Supply Chain* , May 2019." - }, - "rlinks": [ - { - "href": "https://www.whitehouse.gov/presidential-actions/executive-order-securing-information-communications-technology-services-supply-chain" - } - ] - }, - { - "uuid": "4ff10ed3-d8fe-4246-99e3-443045e27482", - "title": "FASC18", - "citation": { - "text": "Secure Technology Act \\[includes Federal Acquisition Supply Chain Security Act\\] (P.L. 115-390), December 2018." - }, - "rlinks": [ - { - "href": "https://www.congress.gov/bill/115th-congress/senate-bill/3085" - } - ] - }, - { - "uuid": "a1555677-2b9d-4868-a97b-a1363aff32f5", - "title": "FED PKI", - "citation": { - "text": "General Services Administration, *Federal Public Key Infrastructure*." - }, - "rlinks": [ - { - "href": "https://www.idmanagement.gov/topics/fpki" - } - ] - }, - { - "uuid": "678e3d6c-150b-4393-aec5-6e3481eb1e00", - "title": "FIPS 140-3", - "citation": { - "text": "National Institute of Standards and Technology (2019) Security Requirements for Cryptographic Modules. (U.S. Department of Commerce, Washington, D.C.), Federal Information Processing Standards Publication (FIPS) 140-3." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.FIPS.140-3" - } - ] - }, - { - "uuid": "eea3c092-42ed-4382-a6f4-1adadef01b9d", - "title": "FIPS 180-4", - "citation": { - "text": "National Institute of Standards and Technology (2015) Secure Hash Standard (SHS). (U.S. Department of Commerce, Washington, D.C.), Federal Information Processing Standards Publication (FIPS) 180-4." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.FIPS.180-4" - } - ] - }, - { - "uuid": "7c37a38d-21d7-40d8-bc3d-b5e27eac17e1", - "title": "FIPS 186-4", - "citation": { - "text": "National Institute of Standards and Technology (2013) Digital Signature Standard (DSS). (U.S. Department of Commerce, Washington, D.C.), Federal Information Processing Standards Publication (FIPS) 186-4." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.FIPS.186-4" - } - ] - }, - { - "uuid": "736d6310-e403-4b57-a79d-9967970c66d7", - "title": "FIPS 197", - "citation": { - "text": "National Institute of Standards and Technology (2001) Advanced Encryption Standard (AES). (U.S. Department of Commerce, Washington, D.C.), Federal Information Processing Standards Publication (FIPS) 197." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.FIPS.197" - } - ] - }, - { - "uuid": "628d22a1-6a11-4784-bc59-5cd9497b5445", - "title": "FIPS 199", - "citation": { - "text": "National Institute of Standards and Technology (2004) Standards for Security Categorization of Federal Information and Information Systems. (U.S. Department of Commerce, Washington, D.C.), Federal Information Processing Standards Publication (FIPS) 199." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.FIPS.199" - } - ] - }, - { - "uuid": "599fb53d-5041-444e-a7fe-640d6d30ad05", - "title": "FIPS 200", - "citation": { - "text": "National Institute of Standards and Technology (2006) Minimum Security Requirements for Federal Information and Information Systems. (U.S. Department of Commerce, Washington, D.C.), Federal Information Processing Standards Publication (FIPS) 200." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.FIPS.200" - } - ] - }, - { - "uuid": "7ba1d91c-3934-4d5a-8532-b32f864ad34c", - "title": "FIPS 201-2", - "citation": { - "text": "National Institute of Standards and Technology (2013) Personal Identity Verification (PIV) of Federal Employees and Contractors. (U.S. Department of Commerce, Washington, D.C.), Federal Information Processing Standards Publication (FIPS) 201-2." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.FIPS.201-2" - } - ] - }, - { - "uuid": "a295ca19-8c75-4b4c-8800-98024732e181", - "title": "FIPS 202", - "citation": { - "text": "National Institute of Standards and Technology (2015) SHA-3 Standard: Permutation-Based Hash and Extendable-Output Functions. (U.S. Department of Commerce, Washington, D.C.), Federal Information Processing Standards Publication (FIPS) 202." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.FIPS.202" - } - ] - }, - { - "uuid": "0c67b2a9-bede-43d2-b86d-5f35b8be36e9", - "title": "FISMA", - "citation": { - "text": "Federal Information Security Modernization Act (P.L. 113-283), December 2014." - }, - "rlinks": [ - { - "href": "https://www.congress.gov/113/plaws/publ283/PLAW-113publ283.pdf" - } - ] - }, - { - "uuid": "f16e438e-7114-4144-bfe2-2dfcad8cb2d0", - "title": "HSPD 12", - "citation": { - "text": "Homeland Security Presidential Directive 12, Policy for a Common Identification Standard for Federal Employees and Contractors, August 2004." - }, - "rlinks": [ - { - "href": "https://www.dhs.gov/homeland-security-presidential-directive-12" - } - ] - }, - { - "uuid": "e4d37285-1e79-4029-8b6a-42df39cace30", - "title": "IETF 5905", - "citation": { - "text": "Internet Engineering Task Force (IETF), Request for Comments: 5905, *Network Time Protocol Version 4: Protocol and Algorithms Specification* , June 2010." - }, - "rlinks": [ - { - "href": "https://tools.ietf.org/pdf/rfc5905.pdf" - } - ] - }, - { - "uuid": "15dc76ff-b17a-4eeb-8948-8ea8de3ccc2c", - "title": "IR 7539", - "citation": { - "text": "Cooper DA, MacGregor WI (2008) Symmetric Key Injection onto Smart Cards. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 7539." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.7539" - } - ] - }, - { - "uuid": "2be7b163-e50a-435c-8906-f1162f2a457a", - "title": "IR 7559", - "citation": { - "text": "Singhal A, Gunestas M, Wijesekera D (2010) Forensics Web Services (FWS). (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 7559." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.7559" - } - ] - }, - { - "uuid": "e24b06cc-9129-4998-a76a-65c3d7a576ba", - "title": "IR 7622", - "citation": { - "text": "Boyens JM, Paulsen C, Bartol N, Shankles S, Moorthy R (2012) Notional Supply Chain Risk Management Practices for Federal Information Systems. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 7622." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.7622" - } - ] - }, - { - "uuid": "4b38e961-1125-4a5b-aa35-1d6c02846dad", - "title": "IR 7676", - "citation": { - "text": "Cooper DA (2010) Maintaining and Using Key History on Personal Identity Verification (PIV) Cards. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 7676." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.7676" - } - ] - }, - { - "uuid": "aa5d04e0-6090-4e17-84d4-b9963d55fc2c", - "title": "IR 7788", - "citation": { - "text": "Singhal A, Ou X (2011) Security Risk Analysis of Enterprise Networks Using Probabilistic Attack Graphs. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 7788." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.7788" - } - ] - }, - { - "uuid": "91701292-8bcd-4d2e-a5bd-59ab61e34b3c", - "title": "IR 7817", - "citation": { - "text": "Ferraiolo H (2012) A Credential Reliability and Revocation Model for Federated Identities. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 7817." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.7817" - } - ] - }, - { - "uuid": "4f5f51ac-2b8d-4b90-a3c7-46f56e967617", - "title": "IR 7849", - "citation": { - "text": "Chandramouli R (2014) A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 7849." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.7849" - } - ] - }, - { - "uuid": "604774da-9e1d-48eb-9c62-4e959dc80737", - "title": "IR 7870", - "citation": { - "text": "Cooper DA (2012) NIST Test Personal Identity Verification (PIV) Cards. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 7870." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.7870" - } - ] - }, - { - "uuid": "7f473f21-fdbf-4a6c-81a1-0ab95919609d", - "title": "IR 7874", - "citation": { - "text": "Hu VC, Scarfone KA (2012) Guidelines for Access Control System Evaluation Metrics. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 7874." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.7874" - } - ] - }, - { - "uuid": "849b2358-683f-4d97-b111-1cc3d522ded5", - "title": "IR 7956", - "citation": { - "text": "Chandramouli R, Iorga M, Chokhani S (2013) Cryptographic Key Management Issues \\& Challenges in Cloud Services. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 7956." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.7956" - } - ] - }, - { - "uuid": "3915a084-b87b-4f02-83d4-c369e746292f", - "title": "IR 7966", - "citation": { - "text": "Ylonen T, Turner P, Scarfone KA, Souppaya MP (2015) Security of Interactive and Automated Access Management Using Secure Shell (SSH). (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 7966." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.7966" - } - ] - }, - { - "uuid": "bbac9fc2-df5b-4f2d-bf99-90d0ade45349", - "title": "IR 8011-1", - "citation": { - "text": "Dempsey KL, Eavy P, Moore G (2017) Automation Support for Security Control Assessments: Volume 1: Overview. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 8011, Volume 1." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.8011-1" - } - ] - }, - { - "uuid": "70402863-5078-43af-9a6c-e11b0f3ec370", - "title": "IR 8011-2", - "citation": { - "text": "Dempsey KL, Eavy P, Moore G (2017) Automation Support for Security Control Assessments: Volume 2: Hardware Asset Management. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 8011, Volume 2." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.8011-2" - } - ] - }, - { - "uuid": "996241f8-f692-42d5-91f1-ce8b752e39e6", - "title": "IR 8011-3", - "citation": { - "text": "Dempsey KL, Eavy P, Goren N, Moore G (2018) Automation Support for Security Control Assessments: Volume 3: Software Asset Management. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 8011, Volume 3." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.8011-3" - } - ] - }, - { - "uuid": "d2ebec9b-f868-4ee1-a2bd-0b2282aed248", - "title": "IR 8011-4", - "citation": { - "text": "Dempsey KL, Takamura E, Eavy P, Moore G (2020) Automation Support for Security Control Assessments: Volume 4: Software Vulnerability Management. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 8011, Volume 4." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.8011-4" - } - ] - }, - { - "uuid": "4c501da5-9d79-4cb6-ba80-97260e1ce327", - "title": "IR 8023", - "citation": { - "text": "Dempsey KL, Paulsen C (2015) Risk Management for Replication Devices. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 8023." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.8023" - } - ] - }, - { - "uuid": "81aeb0a3-d0ee-4e44-b842-6bf28d2bd7f5", - "title": "IR 8040", - "citation": { - "text": "Greene KK, Kelsey JM, Franklin JM (2016) Measuring the Usability and Security of Permuted Passwords on Mobile Platforms. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 8040." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.8040" - } - ] - }, - { - "uuid": "98d415ca-7281-4064-9931-0c366637e324", - "title": "IR 8062", - "citation": { - "text": "Brooks S, Garcia M, Lefkovitz N, Lightman S, Nadeau E (2017) An Introduction to Privacy Engineering and Risk Management in Federal Systems. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 8062." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.8062" - } - ] - }, - { - "uuid": "a2590922-82f3-4277-83c0-ca5bee06dba4", - "title": "IR 8112", - "citation": { - "text": "Grassi P, Lefkovitz N, Nadeau E, Galluzzo R, Dinh, A (2018) Attribute Metadata: A Proposed Schema for Evaluating Federated Attributes. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 8112." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.8112" - } - ] - }, - { - "uuid": "d4296805-2dca-4c63-a95f-eeccaa826aec", - "title": "IR 8179", - "citation": { - "text": "Paulsen C, Boyens JM, Bartol N, Winkler K (2018) Criticality Analysis Process Model: Prioritizing Systems and Components. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 8179." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.8179" - } - ] - }, - { - "uuid": "38ff38f0-1366-4f50-a4c9-26a39aacee16", - "title": "IR 8272", - "citation": { - "text": "Paulsen C, Winkler K, Boyens JM, Ng J, Gimbi J (2020) Impact Analysis Tool for Interdependent Cyber Supply Chain Risks. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 8272." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.IR.8272" - } - ] - }, - { - "uuid": "6afc1b04-c9d6-4023-adbc-f8fbe33a3c73", - "title": "ISO 15408-1", - "citation": { - "text": "International Organization for Standardization/International Electrotechnical Commission 15408-1:2009, *Information technology —Security techniques — Evaluation criteria for IT security — Part 1: Introduction and general model* , April 2017." - }, - "rlinks": [ - { - "href": "https://www.commoncriteriaportal.org/files/ccfiles/CCPART1V3.1R5.pdf" - } - ] - }, - { - "uuid": "87087451-2af5-43d4-88c1-d66ad850f614", - "title": "ISO 15408-2", - "citation": { - "text": "International Organization for Standardization/International Electrotechnical Commission 15408-2:2008, *Information technology —Security techniques — Evaluation criteria for IT security — Part 2: Security functional requirements* , April 2017." - }, - "rlinks": [ - { - "href": "https://www.commoncriteriaportal.org/files/ccfiles/CCPART2V3.1R5.pdf" - } - ] - }, - { - "uuid": "4452efc0-e79e-47b8-aa30-b54f3ef61c2f", - "title": "ISO 15408-3", - "citation": { - "text": "International Organization for Standardization/International Electrotechnical Commission 15408-3:2008, *Information technology—Security techniques — Evaluation criteria for IT security — Part 3: Security assurance requirements* , April 2017." - }, - "rlinks": [ - { - "href": "https://www.commoncriteriaportal.org/files/ccfiles/CCPART3V3.1R5.pdf" - } - ] - }, - { - "uuid": "15a95e24-65b6-4686-bc18-90855a10457d", - "title": "ISO 20243", - "citation": { - "text": "International Organization for Standardization/International Electrotechnical Commission 20243-1:2018, *Information technology — Open Trusted Technology Provider™ Standard (O-TTPS) — Mitigating maliciously tainted and counterfeit products — Part 1: Requirements and recommendations* , February 2018." - }, - "rlinks": [ - { - "href": "https://www.iso.org/standard/74399.html" - } - ] - }, - { - "uuid": "863caf2a-978a-4260-9e8d-4a8929bce40c", - "title": "ISO 27036", - "citation": { - "text": "International Organization for Standardization/International Electrotechnical Commission 27036-1:2014, *Information technology—Security techniques—Information security for supplier relationships, Part 1: Overview and concepts* , April 2014." - }, - "rlinks": [ - { - "href": "https://www.iso.org/standard/59648.html" - } - ] - }, - { - "uuid": "8df72805-2e5c-4731-a73e-81db0f0318d0", - "title": "ISO 29147", - "citation": { - "text": "International Organization for Standardization/International Electrotechnical Commission 29147:2018, *Information technology—Security techniques—Vulnerability disclosure* , October 2018." - }, - "rlinks": [ - { - "href": "https://www.iso.org/standard/72311.html" - } - ] - }, - { - "uuid": "06ce9216-bd54-4054-a422-94f358b50a5d", - "title": "ISO 29148", - "citation": { - "text": "International Organization for Standardization/International Electrotechnical Commission/Institute of Electrical and Electronics Engineers (ISO/IEC/IEEE) 29148:2018, *Systems and software engineering—Life cycle processes—Requirements engineering* , November 2018." - }, - "rlinks": [ - { - "href": "https://www.iso.org/standard/72089.html" - } - ] - }, - { - "uuid": "c28ae9a8-1121-42a9-a85e-00cfcc9b9a94", - "title": "NARA CUI", - "citation": { - "text": "National Archives and Records Administration, Controlled Unclassified Information (CUI) Registry." - }, - "rlinks": [ - { - "href": "https://www.archives.gov/cui" - } - ] - }, - { - "uuid": "d744d9a3-73eb-4085-b9ff-79e82e9e2d6e", - "title": "NCPR", - "citation": { - "text": "National Institute of Standards and Technology (2020) *National Checklist Program Repository* . Available at" - }, - "rlinks": [ - { - "href": "https://nvd.nist.gov/ncp/repository" - } - ] - }, - { - "uuid": "795aff72-3e6c-4b6b-a80a-b14d84b7f544", - "title": "NIAP CCEVS", - "citation": { - "text": "National Information Assurance Partnership, *Common Criteria Evaluation and Validation Scheme*." - }, - "rlinks": [ - { - "href": "https://www.niap-ccevs.org" - } - ] - }, - { - "uuid": "84dc1b0c-acb7-4269-84c4-00dbabacd78c", - "title": "NIST CAVP", - "citation": { - "text": "National Institute of Standards and Technology (2020) *Cryptographic Algorithm Validation Program* . Available at" - }, - "rlinks": [ - { - "href": "https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program" - } - ] - }, - { - "uuid": "1acdc775-aafb-4d11-9341-dc6a822e9d38", - "title": "NIST CMVP", - "citation": { - "text": "National Institute of Standards and Technology (2020) *Cryptographic Module Validation Program* . Available at" - }, - "rlinks": [ - { - "href": "https://csrc.nist.gov/projects/cryptographic-module-validation-program" - } - ] - }, - { - "uuid": "3d575737-98cb-459d-b41c-d7e82b73ad78", - "title": "NSA CSFC", - "citation": { - "text": "National Security Agency, *Commercial Solutions for Classified Program (CSfC)*." - }, - "rlinks": [ - { - "href": "https://www.nsa.gov/resources/everyone/csfc" - } - ] - }, - { - "uuid": "df9f87e9-71e7-4c74-9ac3-3cabd4e92f21", - "title": "NSA MEDIA", - "citation": { - "text": "National Security Agency, *Media Destruction Guidance*." - }, - "rlinks": [ - { - "href": "https://www.nsa.gov/resources/everyone/media-destruction" - } - ] - }, - { - "uuid": "89f2a08d-fc49-46d0-856e-bf974c9b1573", - "title": "ODNI CTF", - "citation": { - "text": "Office of the Director of National Intelligence (ODNI) Cyber Threat Framework." - }, - "rlinks": [ - { - "href": "https://www.dni.gov/index.php/cyber-threat-framework" - } - ] - }, - { - "uuid": "27847491-5ce1-4f6a-a1e4-9e483782f0ef", - "title": "OMB A-130", - "citation": { - "text": "Office of Management and Budget Memorandum Circular A-130, *Managing Information as a Strategic Resource* , July 2016." - }, - "rlinks": [ - { - "href": "https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/circulars/A130/a130revised.pdf" - } - ] - }, - { - "uuid": "5f4705ac-8d17-438c-b23a-ac7f12362ae4", - "title": "OMB M-17-12", - "citation": { - "text": "Office of Management and Budget Memorandum M-17-12, *Preparing for and Responding to a Breach of Personally Identifiable Information* , January 2017." - }, - "rlinks": [ - { - "href": "https://obamawhitehouse.archives.gov/sites/default/files/omb/memoranda/2017/m-17-12_0.pdf" - } - ] - }, - { - "uuid": "c5e11048-1d38-4af3-b00b-0d88dc26860c", - "title": "OMB M-19-03", - "citation": { - "text": "Office of Management and Budget Memorandum M-19-03, *Strengthening the Cybersecurity of Federal Agencies by Enhancing the High Value Asset Program* , December 2018." - }, - "rlinks": [ - { - "href": "https://www.whitehouse.gov/wp-content/uploads/2018/12/M-19-03.pdf" - } - ] - }, - { - "uuid": "18e71fec-c6fd-475a-925a-5d8495cf8455", - "title": "PRIVACT", - "citation": { - "text": "Privacy Act (P.L. 93-579), December 1974." - }, - "rlinks": [ - { - "href": "https://www.govinfo.gov/content/pkg/STATUTE-88/pdf/STATUTE-88-Pg1896.pdf" - } - ] - }, - { - "uuid": "4c0ec2ee-a0d6-428a-9043-4504bc3ade6f", - "title": "SP 800-100", - "citation": { - "text": "Bowen P, Hash J, Wilson M (2006) Information Security Handbook: A Guide for Managers. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-100, Includes updates as of March 7, 2007." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-100" - } - ] - }, - { - "uuid": "10cf2fad-a216-41f9-bb1a-531b7e3119e3", - "title": "SP 800-101", - "citation": { - "text": "Ayers RP, Brothers S, Jansen W (2014) Guidelines on Mobile Device Forensics. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-101, Rev. 1." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-101r1" - } - ] - }, - { - "uuid": "22f2d4f0-4365-4e88-a30d-275c1f5473ea", - "title": "SP 800-111", - "citation": { - "text": "Scarfone KA, Souppaya MP, Sexton M (2007) Guide to Storage Encryption Technologies for End User Devices. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-111." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-111" - } - ] - }, - { - "uuid": "6bc4d137-aece-42a8-8081-9ecb1ebe9fb4", - "title": "SP 800-113", - "citation": { - "text": "Frankel SE, Hoffman P, Orebaugh AD, Park R (2008) Guide to SSL VPNs. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-113." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-113" - } - ] - }, - { - "uuid": "42e37e51-7cc0-4ffa-81c9-0ac942da7e99", - "title": "SP 800-114", - "citation": { - "text": "Souppaya MP, Scarfone KA (2016) User's Guide to Telework and Bring Your Own Device (BYOD) Security. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-114, Rev. 1." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-114r1" - } - ] - }, - { - "uuid": "122177fa-c4ed-485d-8345-3082c0fb9a06", - "title": "SP 800-115", - "citation": { - "text": "Scarfone KA, Souppaya MP, Cody A, Orebaugh AD (2008) Technical Guide to Information Security Testing and Assessment. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-115." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-115" - } - ] - }, - { - "uuid": "2100332a-16a5-4598-bacf-7261baea9711", - "title": "SP 800-116", - "citation": { - "text": "Ferraiolo H, Mehta KL, Ghadiali N, Mohler J, Johnson V, Brady S (2018) A Recommendation for the Use of PIV Credentials in Physical Access Control Systems (PACS). (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-116, Rev. 1." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-116r1" - } - ] - }, - { - "uuid": "d17ebd7a-ffab-499d-bfff-e705bbb01fa6", - "title": "SP 800-121", - "citation": { - "text": "Padgette J, Bahr J, Holtmann M, Batra M, Chen L, Smithbey R, Scarfone KA (2017) Guide to Bluetooth Security. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-121, Rev. 2." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-121r2" - } - ] - }, - { - "uuid": "0f66be67-85e7-4ca6-bd19-39453e9f4394", - "title": "SP 800-124", - "citation": { - "text": "Souppaya MP, Scarfone KA (2013) Guidelines for Managing the Security of Mobile Devices in the Enterprise. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-124, Rev. 1." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-124r1" - } - ] - }, - { - "uuid": "88660532-2dcf-442e-845c-03340ce48999", - "title": "SP 800-125B", - "citation": { - "text": "Chandramouli R (2016) Secure Virtual Network Configuration for Virtual Machine (VM) Protection. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-125B." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-125B" - } - ] - }, - { - "uuid": "8016d2ed-d30f-4416-9c45-0f42c7aa3232", - "title": "SP 800-126", - "citation": { - "text": "Waltermire DA, Quinn SD, Booth H, III, Scarfone KA, Prisaca D (2018) The Technical Specification for the Security Content Automation Protocol (SCAP): SCAP Version 1.3. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-126, Rev. 3." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-126r3" - } - ] - }, - { - "uuid": "20db4e66-e257-450c-b2e4-2bb9a62a2c88", - "title": "SP 800-128", - "citation": { - "text": "Johnson LA, Dempsey KL, Ross RS, Gupta S, Bailey D (2011) Guide for Security-Focused Configuration Management of Information Systems. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-128, Includes updates as of October 10, 2019." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-128" - } - ] - }, - { - "uuid": "c7ac44e8-10db-4b64-b2b9-9e32ec1efed0", - "title": "SP 800-12", - "citation": { - "text": "Nieles M, Pillitteri VY, Dempsey KL (2017) An Introduction to Information Security. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-12, Rev. 1." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-12r1" - } - ] - }, - { - "uuid": "3653e316-8923-430e-8943-b3b2b2562fc6", - "title": "SP 800-130", - "citation": { - "text": "Barker EB, Smid ME, Branstad DK, Chokhani S (2013) A Framework for Designing Cryptographic Key Management Systems. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-130." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-130" - } - ] - }, - { - "uuid": "62ea77ca-e450-4323-b210-e0d75390e785", - "title": "SP 800-137A", - "citation": { - "text": "Dempsey KL, Pillitteri VY, Baer C, Niemeyer R, Rudman R, Urban S (2020) Assessing Information Security Continuous Monitoring (ISCM) Programs: Developing an ISCM Program Assessment. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-137A." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-137A" - } - ] - }, - { - "uuid": "067223d8-1ec7-45c5-b21b-c848da6de8fb", - "title": "SP 800-137", - "citation": { - "text": "Dempsey KL, Chawla NS, Johnson LA, Johnston R, Jones AC, Orebaugh AD, Scholl MA, Stine KM (2011) Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-137." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-137" - } - ] - }, - { - "uuid": "e47ee630-9cbc-4133-880e-e013f83ccd51", - "title": "SP 800-147", - "citation": { - "text": "Cooper DA, Polk T, Regenscheid AR, Souppaya MP (2011) BIOS Protection Guidelines. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-147." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-147" - } - ] - }, - { - "uuid": "9ef4b43c-42a4-4316-87dc-ffaf528bc05c", - "title": "SP 800-150", - "citation": { - "text": "Johnson CS, Waltermire DA, Badger ML, Skorupka C, Snyder J (2016) Guide to Cyber Threat Information Sharing. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-150." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-150" - } - ] - }, - { - "uuid": "2494df28-9049-4196-b233-540e7440993f", - "title": "SP 800-152", - "citation": { - "text": "Barker EB, Branstad DK, Smid ME (2015) A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS). (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-152." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-152" - } - ] - }, - { - "uuid": "708b94e1-3d5e-4b22-ab43-1c69f3a97e37", - "title": "SP 800-154", - "citation": { - "text": "Souppaya MP, Scarfone KA (2016) Guide to Data-Centric System Threat Modeling. (National Institute of Standards and Technology, Gaithersburg, MD), Draft NIST Special Publication (SP) 800-154." - }, - "rlinks": [ - { - "href": "https://csrc.nist.gov/publications/detail/sp/800-154/draft" - } - ] - }, - { - "uuid": "d9e036ba-6eec-46a6-9340-b0bf1fea23b4", - "title": "SP 800-156", - "citation": { - "text": "Ferraiolo H, Chandramouli R, Mehta KL, Mohler J, Skordinski S, Brady S (2016) Representation of PIV Chain-of-Trust for Import and Export. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-156." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-156" - } - ] - }, - { - "uuid": "e3cc0520-a366-4fc9-abc2-5272db7e3564", - "title": "SP 800-160-1", - "citation": { - "text": "Ross RS, Oren JC, McEvilley M (2016) Systems Security Engineering: Considerations for a Multidisciplinary Approach in the Engineering of Trustworthy Secure Systems. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-160, Vol. 1, Includes updates as of March 21, 2018." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-160v1" - } - ] - }, - { - "uuid": "61ccf0f4-d3e7-42db-9796-ce6cb1c85989", - "title": "SP 800-160-2", - "citation": { - "text": "Ross RS, Pillitteri VY, Graubart R, Bodeau D, McQuaid R (2019) Developing Cyber Resilient Systems: A Systems Security Engineering Approach. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-160, Vol. 2." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-160v2" - } - ] - }, - { - "uuid": "e8e84963-14fc-4c3a-be05-b412a5d37cd2", - "title": "SP 800-161", - "citation": { - "text": "Boyens JM, Paulsen C, Moorthy R, Bartol N (2015) Supply Chain Risk Management Practices for Federal Information Systems and Organizations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-161." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-161" - } - ] - }, - { - "uuid": "2956e175-f674-43f4-b1b9-e074ad9fc39c", - "title": "SP 800-162", - "citation": { - "text": "Hu VC, Ferraiolo DF, Kuhn R, Schnitzer A, Sandlin K, Miller R, Scarfone KA (2014) Guide to Attribute Based Access Control (ABAC) Definition and Considerations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-162, Includes updates as of August 2, 2019." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-162" - } - ] - }, - { - "uuid": "e8552d48-cf41-40aa-8b06-f45f7fb4706c", - "title": "SP 800-166", - "citation": { - "text": "Cooper DA, Ferraiolo H, Chandramouli R, Ghadiali N, Mohler J, Brady S (2016) Derived PIV Application and Data Model Test Guidelines. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-166." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-166" - } - ] - }, - { - "uuid": "38f39739-1ebd-43b1-8b8c-00f591d89ebd", - "title": "SP 800-167", - "citation": { - "text": "Sedgewick A, Souppaya MP, Scarfone KA (2015) Guide to Application Whitelisting. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-167." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-167" - } - ] - }, - { - "uuid": "7dbd6d9f-29d6-4d1d-9766-f2d77ff3c849", - "title": "SP 800-171", - "citation": { - "text": "Ross RS, Pillitteri VY, Dempsey KL, Riddle M, Guissanie G (2020) Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-171, Rev. 2." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-171r2" - } - ] - }, - { - "uuid": "f26af0d0-6d72-4a9d-8ecd-01bc21fd4f0e", - "title": "SP 800-172", - "citation": { - "text": "Ross RS, Pillitteri VY, Graubart RD, Guissanie G, Wagner R, Bodeau D (2020) Enhanced Security Requirements for Protecting Controlled Unclassified Information: A Supplement to NIST Special Publication 800-171 (Final Public Draft). (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-172." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-172-draft" - } - ] - }, - { - "uuid": "1c71b420-2bd9-4e52-9fc8-390f58b85b59", - "title": "SP 800-177", - "citation": { - "text": "Rose SW, Nightingale S, Garfinkel SL, Chandramouli R (2019) Trustworthy Email. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-177, Rev. 1." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-177r1" - } - ] - }, - { - "uuid": "388a3aa2-5d85-4bad-b8a3-77db80d63c4f", - "title": "SP 800-178", - "citation": { - "text": "Ferraiolo DF, Hu VC, Kuhn R, Chandramouli R (2016) A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications: Extensible Access Control Markup Language (XACML) and Next Generation Access Control (NGAC). (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-178." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-178" - } - ] - }, - { - "uuid": "276bd50a-7e58-48e5-a405-8c8cb91d7a5f", - "title": "SP 800-181", - "citation": { - "text": "Petersen R, Santos D, Smith MC, Wetzel KA, Witte G (2020) Workforce Framework for Cybersecurity (NICE Framework). (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-181, Rev. 1." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-181r1" - } - ] - }, - { - "uuid": "31ae65ab-3f26-46b7-9d64-f25a4dac5778", - "title": "SP 800-184", - "citation": { - "text": "Bartock M, Scarfone KA, Smith MC, Witte GA, Cichonski JA, Souppaya MP (2016) Guide for Cybersecurity Event Recovery. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-184." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-184" - } - ] - }, - { - "uuid": "f5edfe51-d1f2-422e-9b27-5d0e90b49c72", - "title": "SP 800-189", - "citation": { - "text": "Sriram K, Montgomery D (2019) Resilient Interdomain Traffic Exchange: BGP Security and DDoS Mitigation. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-189." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-189" - } - ] - }, - { - "uuid": "30eb758a-2707-4bca-90ad-949a74d4eb16", - "title": "SP 800-18", - "citation": { - "text": "Swanson MA, Hash J, Bowen P (2006) Guide for Developing Security Plans for Federal Information Systems. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-18, Rev. 1." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-18r1" - } - ] - }, - { - "uuid": "53df282b-8b3f-483a-bad1-6a8b8ac00114", - "title": "SP 800-192", - "citation": { - "text": "Yaga DJ, Kuhn R, Hu VC (2017) Verification and Test Methods for Access Control Policies/Models. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-192." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-192" - } - ] - }, - { - "uuid": "f641309f-a3ad-48be-8c67-2b318648b2f5", - "title": "SP 800-28", - "citation": { - "text": "Jansen W, Winograd T, Scarfone KA (2008) Guidelines on Active Content and Mobile Code. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-28, Version 2." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-28ver2" - } - ] - }, - { - "uuid": "08b07465-dbdc-48d6-8a0b-37279602ac16", - "title": "SP 800-30", - "citation": { - "text": "Joint Task Force Transformation Initiative (2012) Guide for Conducting Risk Assessments. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-30, Rev. 1." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-30r1" - } - ] - }, - { - "uuid": "8cb338a4-e493-4177-818f-3af18983ddc5", - "title": "SP 800-32", - "citation": { - "text": "Kuhn R, Hu VC, Polk T, Chang S-J (2001) Introduction to Public Key Technology and the Federal PKI Infrastructure. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-32." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-32" - } - ] - }, - { - "uuid": "bc39f179-c735-4da2-b7a7-b2b622119755", - "title": "SP 800-34", - "citation": { - "text": "Swanson MA, Bowen P, Phillips AW, Gallup D, Lynes D (2010) Contingency Planning Guide for Federal Information Systems. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-34, Rev. 1, Includes updates as of November 11, 2010." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-34r1" - } - ] - }, - { - "uuid": "77faf0bc-c394-44ad-9154-bbac3b79c8ad", - "title": "SP 800-35", - "citation": { - "text": "Grance T, Hash J, Stevens M, O'Neal K, Bartol N (2003) Guide to Information Technology Security Services. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-35." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-35" - } - ] - }, - { - "uuid": "482e4c99-9dc4-41ad-bba8-0f3f0032c1f8", - "title": "SP 800-37", - "citation": { - "text": "Joint Task Force (2018) Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-37, Rev. 2." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-37r2" - } - ] - }, - { - "uuid": "cec037f3-8aba-4c97-84b4-4082f9e515d2", - "title": "SP 800-39", - "citation": { - "text": "Joint Task Force Transformation Initiative (2011) Managing Information Security Risk: Organization, Mission, and Information System View. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-39." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-39" - } - ] - }, - { - "uuid": "155f941a-cba9-4afd-9ca6-5d040d697ba9", - "title": "SP 800-40", - "citation": { - "text": "Souppaya MP, Scarfone KA (2013) Guide to Enterprise Patch Management Technologies. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-40, Rev. 3." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-40r3" - } - ] - }, - { - "uuid": "a7f0e897-29a3-45c4-bd88-40dfef0e034a", - "title": "SP 800-41", - "citation": { - "text": "Scarfone KA, Hoffman P (2009) Guidelines on Firewalls and Firewall Policy. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-41, Rev. 1." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-41r1" - } - ] - }, - { - "uuid": "314e33cb-3681-4b50-a2a2-3fae9604accd", - "title": "SP 800-45", - "citation": { - "text": "Tracy MC, Jansen W, Scarfone KA, Butterfield J (2007) Guidelines on Electronic Mail Security. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-45, Version 2." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-45ver2" - } - ] - }, - { - "uuid": "83b9d63b-66b1-467c-9f3b-3a0b108771e9", - "title": "SP 800-46", - "citation": { - "text": "Souppaya MP, Scarfone KA (2016) Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-46, Rev. 2." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-46r2" - } - ] - }, - { - "uuid": "c3a76872-e160-4267-99e8-6952de967d04", - "title": "SP 800-47", - "citation": { - "text": "Grance T, Hash J, Peck S, Smith J, Korow-Diks K (2002) Security Guide for Interconnecting Information Technology Systems. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-47." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-47" - } - ] - }, - { - "uuid": "511f6832-23ca-49a3-8c0f-ce493373cab8", - "title": "SP 800-50", - "citation": { - "text": "Wilson M, Hash J (2003) Building an Information Technology Security Awareness and Training Program. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-50." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-50" - } - ] - }, - { - "uuid": "7537638e-2837-407d-844b-40fb3fafdd99", - "title": "SP 800-52", - "citation": { - "text": "McKay KA, Cooper DA (2019) Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-52, Rev. 2." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-52r2" - } - ] - }, - { - "uuid": "a21aef46-7330-48a0-b2e1-c5bb8b2dd11d", - "title": "SP 800-53A", - "citation": { - "text": "Joint Task Force Transformation Initiative (2014) Assessing Security and Privacy Controls in Federal Information Systems and Organizations: Building Effective Assessment Plans. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-53A, Rev. 4, Includes updates as of December 18, 2014." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-53Ar4" - } - ] - }, - { - "uuid": "46d9e201-840e-440e-987c-2c773333c752", - "title": "SP 800-53B", - "citation": { - "text": "Joint Task Force (2020) Control Baselines and Tailoring Guidance for Federal Information Systems and Organizations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-53B." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-53B" - } - ] - }, - { - "uuid": "20957dbb-6a1e-40a2-b38a-66f67d33ac2e", - "title": "SP 800-56A", - "citation": { - "text": "Barker EB, Chen L, Roginsky A, Vassilev A, Davis R (2018) Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-56A, Rev. 3." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-56Ar3" - } - ] - }, - { - "uuid": "0d083d8a-5cc6-46f1-8d79-3081d42bcb75", - "title": "SP 800-56B", - "citation": { - "text": "Barker EB, Chen L, Roginsky A, Vassilev A, Davis R, Simon S (2019) Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-56B, Rev. 2." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-56Br2" - } - ] - }, - { - "uuid": "eef62b16-c796-4554-955c-505824135b8a", - "title": "SP 800-56C", - "citation": { - "text": "Barker EB, Chen L, Davis R (2020) Recommendation for Key-Derivation Methods in Key-Establishment Schemes. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-56C, Rev. 2." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-56Cr2" - } - ] - }, - { - "uuid": "110e26af-4765-49e1-8740-6750f83fcda1", - "title": "SP 800-57-1", - "citation": { - "text": "Barker EB (2020) Recommendation for Key Management: Part 1 – General. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-57 Part 1, Rev. 5." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-57pt1r5" - } - ] - }, - { - "uuid": "e7942589-e267-4a5a-a3d9-f39a7aae81f0", - "title": "SP 800-57-2", - "citation": { - "text": "Barker EB, Barker WC (2019) Recommendation for Key Management: Part 2 – Best Practices for Key Management Organizations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-57 Part 2, Rev. 1." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-57pt2r1" - } - ] - }, - { - "uuid": "8306620b-1920-4d73-8b21-12008528595f", - "title": "SP 800-57-3", - "citation": { - "text": "Barker EB, Dang QH (2015) Recommendation for Key Management, Part 3: Application-Specific Key Management Guidance. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-57 Part 3, Rev. 1." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-57pt3r1" - } - ] - }, - { - "uuid": "e72fde0b-6fc2-497e-a9db-d8fce5a11b8a", - "title": "SP 800-60-1", - "citation": { - "text": "Stine KM, Kissel RL, Barker WC, Fahlsing J, Gulick J (2008) Guide for Mapping Types of Information and Information Systems to Security Categories. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-60, Vol. 1, Rev. 1." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-60v1r1" - } - ] - }, - { - "uuid": "9be5d661-421f-41ad-854e-86f98b811891", - "title": "SP 800-60-2", - "citation": { - "text": "Stine KM, Kissel RL, Barker WC, Lee A, Fahlsing J (2008) Guide for Mapping Types of Information and Information Systems to Security Categories: Appendices. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-60, Vol. 2, Rev. 1." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-60v2r1" - } - ] - }, - { - "uuid": "49b8aa2d-a88c-4bff-9f20-876ccb8f7dcb", - "title": "SP 800-61", - "citation": { - "text": "Cichonski PR, Millar T, Grance T, Scarfone KA (2012) Computer Security Incident Handling Guide. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-61, Rev. 2." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-61r2" - } - ] - }, - { - "uuid": "737513fa-6758-403f-831d-5ddab5e23cb3", - "title": "SP 800-63-3", - "citation": { - "text": "Grassi PA, Garcia ME, Fenton JL (2017) Digital Identity Guidelines. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-63-3, Includes updates as of March 2, 2020." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-63-3" - } - ] - }, - { - "uuid": "9099ed2c-922a-493d-bcb4-d896192243ff", - "title": "SP 800-63A", - "citation": { - "text": "Grassi PA, Fenton JL, Lefkovitz NB, Danker JM, Choong Y-Y, Greene KK, Theofanos MF (2017) Digital Identity Guidelines: Enrollment and Identity Proofing. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-63A, Includes updates as of March 2, 2020." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-63a" - } - ] - }, - { - "uuid": "e59c5a7c-8b1f-49ca-8de0-6ee0882180ce", - "title": "SP 800-63B", - "citation": { - "text": "Grassi PA, Fenton JL, Newton EM, Perlner RA, Regenscheid AR, Burr WE, Richer, JP, Lefkovitz NB, Danker JM, Choong Y-Y, Greene KK, Theofanos MF (2017) Digital Identity Guidelines: Authentication and Lifecycle Management. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-63B, Includes updates as of March 2, 2020." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-63b" - } - ] - }, - { - "uuid": "4895b4cd-34c5-4667-bf8a-27d443c12047", - "title": "SP 800-70", - "citation": { - "text": "Quinn SD, Souppaya MP, Cook MR, Scarfone KA (2018) National Checklist Program for IT Products: Guidelines for Checklist Users and Developers. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-70, Rev. 4." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-70r4" - } - ] - }, - { - "uuid": "858705be-3c1f-48aa-a328-0ce398d95ef0", - "title": "SP 800-73-4", - "citation": { - "text": "Cooper DA, Ferraiolo H, Mehta KL, Francomacaro S, Chandramouli R, Mohler J (2015) Interfaces for Personal Identity Verification. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-73-4, Includes updates as of February 8, 2016." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-73-4" - } - ] - }, - { - "uuid": "7af2e6ec-9f7e-4232-ad3f-09888eb0793a", - "title": "SP 800-76-2", - "citation": { - "text": "Grother PJ, Salamon WJ, Chandramouli R (2013) Biometric Specifications for Personal Identity Verification. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-76-2." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-76-2" - } - ] - }, - { - "uuid": "d4d7c760-2907-403b-8b2a-767ca5370ecd", - "title": "SP 800-77", - "citation": { - "text": "Barker EB, Dang QH, Frankel SE, Scarfone KA, Wouters P (2020) Guide to IPsec VPNs. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-77, Rev. 1." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-77r1" - } - ] - }, - { - "uuid": "828856bd-d7c4-427b-8b51-815517ec382d", - "title": "SP 800-78-4", - "citation": { - "text": "Polk T, Dodson DF, Burr WE, Ferraiolo H, Cooper DA (2015) Cryptographic Algorithms and Key Sizes for Personal Identity Verification. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-78-4." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-78-4" - } - ] - }, - { - "uuid": "10963761-58fc-4b20-b3d6-b44a54daba03", - "title": "SP 800-79-2", - "citation": { - "text": "Ferraiolo H, Chandramouli R, Ghadiali N, Mohler J, Shorter S (2015) Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI). (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-79-2." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-79-2" - } - ] - }, - { - "uuid": "fe209006-bfd4-4033-a79a-9fee1adaf372", - "title": "SP 800-81-2", - "citation": { - "text": "Chandramouli R, Rose SW (2013) Secure Domain Name System (DNS) Deployment Guide. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-81-2." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-81-2" - } - ] - }, - { - "uuid": "3dd249b0-f57d-44ba-a03e-c3eab1b835ff", - "title": "SP 800-83", - "citation": { - "text": "Souppaya MP, Scarfone KA (2013) Guide to Malware Incident Prevention and Handling for Desktops and Laptops. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-83, Rev. 1." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-83r1" - } - ] - }, - { - "uuid": "53be2fcf-cfd1-4bcb-896b-9a3b65c22098", - "title": "SP 800-84", - "citation": { - "text": "Grance T, Nolan T, Burke K, Dudley R, White G, Good T (2006) Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-84." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-84" - } - ] - }, - { - "uuid": "cfdb1858-c473-46b3-89f9-a700308d0be2", - "title": "SP 800-86", - "citation": { - "text": "Kent K, Chevalier S, Grance T, Dang H (2006) Guide to Integrating Forensic Techniques into Incident Response. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-86." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-86" - } - ] - }, - { - "uuid": "a5b1d18d-e670-4586-9e6d-4a88b7ba3df6", - "title": "SP 800-88", - "citation": { - "text": "Kissel RL, Regenscheid AR, Scholl MA, Stine KM (2014) Guidelines for Media Sanitization. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-88, Rev. 1." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-88r1" - } - ] - }, - { - "uuid": "5eee45d8-3313-4fdc-8d54-1742092bbdd6", - "title": "SP 800-92", - "citation": { - "text": "Kent K, Souppaya MP (2006) Guide to Computer Security Log Management. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-92." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-92" - } - ] - }, - { - "uuid": "25e3e57b-dc2f-4934-af9b-050b020c6f0e", - "title": "SP 800-94", - "citation": { - "text": "Scarfone KA, Mell PM (2007) Guide to Intrusion Detection and Prevention Systems (IDPS). (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-94." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-94" - } - ] - }, - { - "uuid": "a6b9907a-2a14-4bb4-a142-d4c73026a8b4", - "title": "SP 800-95", - "citation": { - "text": "Singhal A, Winograd T, Scarfone KA (2007) Guide to Secure Web Services. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-95." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-95" - } - ] - }, - { - "uuid": "03fb73bc-1b12-4182-bd96-e5719254ea61", - "title": "SP 800-97", - "citation": { - "text": "Frankel SE, Eydt B, Owens L, Scarfone KA (2007) Establishing Wireless Robust Security Networks: A Guide to IEEE 802.11i. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-97." - }, - "rlinks": [ - { - "href": "https://doi.org/10.6028/NIST.SP.800-97" - } - ] - }, - { - "uuid": "13f0c39d-eaf7-417a-baef-69a041878bb5", - "title": "USA PATRIOT", - "citation": { - "text": "USA Patriot Act (P.L. 107-56), October 2001." - }, - "rlinks": [ - { - "href": "https://www.congress.gov/107/plaws/publ56/PLAW-107publ56.pdf" - } - ] - }, - { - "uuid": "e922fc50-b1f9-469f-92ef-ed7d9803611c", - "title": "USC 2901", - "citation": { - "text": "United States Code, 2008 Edition, Title 44 - *Public Printing and Documents* , Chapters 29, 31, and 33, January 2012." - }, - "rlinks": [ - { - "href": "https://www.govinfo.gov/content/pkg/USCODE-2011-title44/pdf/USCODE-2011-title44-chap29-sec2901.pdf" - } - ] - }, - { - "uuid": "40b78258-c892-480e-9af8-77ac36648301", - "title": "USCERT IR", - "citation": { - "text": "Department of Homeland Security, *US-CERT Federal Incident Notification Guidelines* , April 2017." - }, - "rlinks": [ - { - "href": "https://us-cert.cisa.gov/incident-notification-guidelines" - } - ] - }, - { - "uuid": "98498928-3ca3-44b3-8b1e-f48685373087", - "title": "USGCB", - "citation": { - "text": "National Institute of Standards and Technology (2020) *United States Government Configuration Baseline* . Available at" - }, - "rlinks": [ - { - "href": "https://csrc.nist.gov/projects/united-states-government-configuration-baseline" - } - ] - }, - { - "uuid": "c3397cc9-83c6-4459-adb2-836739dc1b94", - "title": "NIST Special Publication 800-53, Revision 5: *Security and Privacy Controls for Information Systems and Organizations* (PDF)", - "rlinks": [ - { - "href": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r5.pdf", - "media-type": "application/pdf" - } - ] - } - ] - } - } -} diff --git a/data/profiles/FedRAMP_rev5_HIGH-baseline_profile.json b/data/profiles/FedRAMP_rev5_HIGH-baseline_profile.json deleted file mode 100644 index 7b311df3..00000000 --- a/data/profiles/FedRAMP_rev5_HIGH-baseline_profile.json +++ /dev/null @@ -1,3018 +0,0 @@ -{ - "profile": { - "uuid": "5d92f565-7fa2-4bd8-acf7-5c49e26723c4", - "metadata": { - "title": "FedRAMP Rev 5 High Baseline", - "published": "2024-09-24T02:24:00Z", - "last-modified": "2025-02-28T00:00:00Z", - "version": "fedramp-3.0.0rc1-oscal-1.1.2", - "oscal-version": "1.1.3", - "roles": [ - { - "id": "prepared-by", - "title": "Document creator" - }, - { - "id": "fedramp-pmo", - "title": "The FedRAMP Program Management Office (PMO)", - "short-name": "PMO" - } - ], - "parties": [ - { - "uuid": "8cc0b8e5-9650-4d5f-9796-316f05fa9a2d", - "type": "organization", - "name": "Federal Risk and Authorization Management Program: Program Management Office", - "short-name": "FedRAMP PMO", - "links": [ - { - "href": "https://fedramp.gov", - "rel": "homepage" - }, - { - "href": "#a2381e87-3d04-4108-a30b-b4d2f36d001f", - "rel": "logo" - }, - { - "href": "#985475ee-d4d6-4581-8fdf-d84d3d8caa48", - "rel": "reference" - } - ], - "email-addresses": [ - "info@fedramp.gov" - ], - "addresses": [ - { - "addr-lines": [ - "1800 F St. NW" - ], - "postal-code": "20006", - "type": "work", - "state": "DC", - "city": "Washington", - "country": "US" - } - ] - } - ], - "responsible-parties": [ - { - "role-id": "prepared-by", - "party-uuids": [ - "8cc0b8e5-9650-4d5f-9796-316f05fa9a2d" - ] - }, - { - "role-id": "fedramp-pmo", - "party-uuids": [ - "8cc0b8e5-9650-4d5f-9796-316f05fa9a2d" - ] - } - ] - }, - "imports": [ - { - "href": "#051a77c1-b61d-4995-8275-dacfe688d510", - "include-controls": [ - { - "with-ids": [ - "ac-1", - "ac-2", - "ac-2.1", - "ac-2.2", - "ac-2.3", - "ac-2.4", - "ac-2.5", - "ac-2.7", - "ac-2.9", - "ac-2.11", - "ac-2.12", - "ac-2.13", - "ac-3", - "ac-4", - "ac-4.4", - "ac-4.21", - "ac-5", - "ac-6", - "ac-6.1", - "ac-6.2", - "ac-6.3", - "ac-6.5", - "ac-6.7", - "ac-6.8", - "ac-6.9", - "ac-6.10", - "ac-7", - "ac-8", - "ac-10", - "ac-11", - "ac-11.1", - "ac-12", - "ac-14", - "ac-17", - "ac-17.1", - "ac-17.2", - "ac-17.3", - "ac-17.4", - "ac-18", - "ac-18.1", - "ac-18.3", - "ac-18.4", - "ac-18.5", - "ac-19", - "ac-19.5", - "ac-20", - "ac-20.1", - "ac-20.2", - "ac-21", - "ac-22", - "at-1", - "at-2", - "at-2.2", - "at-2.3", - "at-3", - "at-4", - "au-1", - "au-2", - "au-3", - "au-3.1", - "au-4", - "au-5", - "au-5.1", - "au-5.2", - "au-6", - "au-6.1", - "au-6.3", - "au-6.4", - "au-6.5", - "au-6.6", - "au-6.7", - "au-7", - "au-7.1", - "au-8", - "au-9", - "au-9.2", - "au-9.3", - "au-9.4", - "au-10", - "au-11", - "au-12", - "au-12.1", - "au-12.3", - "ca-1", - "ca-2", - "ca-2.1", - "ca-2.2", - "ca-2.3", - "ca-3", - "ca-3.6", - "ca-5", - "ca-6", - "ca-7", - "ca-7.1", - "ca-7.4", - "ca-8", - "ca-8.1", - "ca-8.2", - "ca-9", - "cm-1", - "cm-2", - "cm-2.2", - "cm-2.3", - "cm-2.7", - "cm-3", - "cm-3.1", - "cm-3.2", - "cm-3.4", - "cm-3.6", - "cm-4", - "cm-4.1", - "cm-4.2", - "cm-5", - "cm-5.1", - "cm-5.5", - "cm-6", - "cm-6.1", - "cm-6.2", - "cm-7", - "cm-7.1", - "cm-7.2", - "cm-7.5", - "cm-8", - "cm-8.1", - "cm-8.2", - "cm-8.3", - "cm-8.4", - "cm-9", - "cm-10", - "cm-11", - "cm-12", - "cm-12.1", - "cm-14", - "cp-1", - "cp-2", - "cp-2.1", - "cp-2.2", - "cp-2.3", - "cp-2.5", - "cp-2.8", - "cp-3", - "cp-3.1", - "cp-4", - "cp-4.1", - "cp-4.2", - "cp-6", - "cp-6.1", - "cp-6.2", - "cp-6.3", - "cp-7", - "cp-7.1", - "cp-7.2", - "cp-7.3", - "cp-7.4", - "cp-8", - "cp-8.1", - "cp-8.2", - "cp-8.3", - "cp-8.4", - "cp-9", - "cp-9.1", - "cp-9.2", - "cp-9.3", - "cp-9.5", - "cp-9.8", - "cp-10", - "cp-10.2", - "cp-10.4", - "ia-1", - "ia-2", - "ia-2.1", - "ia-2.2", - "ia-2.5", - "ia-2.6", - "ia-2.8", - "ia-2.12", - "ia-3", - "ia-4", - "ia-4.4", - "ia-5", - "ia-5.1", - "ia-5.2", - "ia-5.6", - "ia-5.7", - "ia-5.8", - "ia-5.13", - "ia-6", - "ia-7", - "ia-8", - "ia-8.1", - "ia-8.2", - "ia-8.4", - "ia-11", - "ia-12", - "ia-12.2", - "ia-12.3", - "ia-12.4", - "ia-12.5", - "ir-1", - "ir-2", - "ir-2.1", - "ir-2.2", - "ir-3", - "ir-3.2", - "ir-4", - "ir-4.1", - "ir-4.2", - "ir-4.4", - "ir-4.6", - "ir-4.11", - "ir-5", - "ir-5.1", - "ir-6", - "ir-6.1", - "ir-6.3", - "ir-7", - "ir-7.1", - "ir-8", - "ir-9", - "ir-9.2", - "ir-9.3", - "ir-9.4", - "ma-1", - "ma-2", - "ma-2.2", - "ma-3", - "ma-3.1", - "ma-3.2", - "ma-3.3", - "ma-4", - "ma-4.3", - "ma-5", - "ma-5.1", - "ma-6", - "mp-1", - "mp-2", - "mp-3", - "mp-4", - "mp-5", - "mp-6", - "mp-6.1", - "mp-6.2", - "mp-6.3", - "mp-7", - "pe-1", - "pe-2", - "pe-3", - "pe-3.1", - "pe-4", - "pe-5", - "pe-6", - "pe-6.1", - "pe-6.4", - "pe-8", - "pe-8.1", - "pe-9", - "pe-10", - "pe-11", - "pe-11.1", - "pe-12", - "pe-13", - "pe-13.1", - "pe-13.2", - "pe-14", - "pe-14.2", - "pe-15", - "pe-15.1", - "pe-16", - "pe-17", - "pe-18", - "pl-1", - "pl-2", - "pl-4", - "pl-4.1", - "pl-8", - "pl-10", - "pl-11", - "ps-1", - "ps-2", - "ps-3", - "ps-3.3", - "ps-4", - "ps-4.2", - "ps-5", - "ps-6", - "ps-7", - "ps-8", - "ps-9", - "ra-1", - "ra-2", - "ra-3", - "ra-3.1", - "ra-5", - "ra-5.2", - "ra-5.3", - "ra-5.4", - "ra-5.5", - "ra-5.8", - "ra-5.11", - "ra-7", - "ra-9", - "sa-1", - "sa-2", - "sa-3", - "sa-4", - "sa-4.1", - "sa-4.2", - "sa-4.5", - "sa-4.9", - "sa-4.10", - "sa-5", - "sa-8", - "sa-9", - "sa-9.1", - "sa-9.2", - "sa-9.5", - "sa-10", - "sa-11", - "sa-11.1", - "sa-11.2", - "sa-15", - "sa-15.3", - "sa-16", - "sa-17", - "sa-21", - "sa-22", - "sc-1", - "sc-2", - "sc-3", - "sc-4", - "sc-5", - "sc-7", - "sc-7.3", - "sc-7.4", - "sc-7.5", - "sc-7.7", - "sc-7.8", - "sc-7.10", - "sc-7.12", - "sc-7.18", - "sc-7.20", - "sc-7.21", - "sc-8", - "sc-8.1", - "sc-10", - "sc-12", - "sc-12.1", - "sc-13", - "sc-15", - "sc-17", - "sc-18", - "sc-20", - "sc-21", - "sc-22", - "sc-23", - "sc-24", - "sc-28", - "sc-28.1", - "sc-39", - "sc-45", - "sc-45.1", - "si-1", - "si-2", - "si-2.2", - "si-2.3", - "si-3", - "si-4", - "si-4.1", - "si-4.2", - "si-4.4", - "si-4.5", - "si-4.10", - "si-4.11", - "si-4.12", - "si-4.14", - "si-4.16", - "si-4.18", - "si-4.19", - "si-4.20", - "si-4.22", - "si-4.23", - "si-5", - "si-5.1", - "si-6", - "si-7", - "si-7.1", - "si-7.2", - "si-7.5", - "si-7.7", - "si-7.15", - "si-8", - "si-8.2", - "si-10", - "si-11", - "si-12", - "si-16", - "sr-1", - "sr-2", - "sr-2.1", - "sr-3", - "sr-5", - "sr-6", - "sr-8", - "sr-9", - "sr-9.1", - "sr-10", - "sr-11", - "sr-11.1", - "sr-11.2", - "sr-12" - ] - } - ] - } - ], - "merge": { - "as-is": true - }, - "modify": { - "set-parameters": [ - { - "param-id": "ac-01_odp.05", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ac-01_odp.07", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ac-01_odp.08", - "constraints": [ - { - "description": "significant changes" - } - ] - }, - { - "param-id": "ac-02_odp.06", - "constraints": [ - { - "description": "twenty-four (24) hours" - } - ] - }, - { - "param-id": "ac-02_odp.07", - "constraints": [ - { - "description": "eight (8) hours" - } - ] - }, - { - "param-id": "ac-02_odp.08", - "constraints": [ - { - "description": "eight (8) hours" - } - ] - }, - { - "param-id": "ac-02_odp.10", - "constraints": [ - { - "description": "monthly for privileged accessed, every six (6) months for non-privileged access" - } - ] - }, - { - "param-id": "ac-02.02_odp.01", - "constraints": [ - { - "description": "Selection: disables" - } - ] - }, - { - "param-id": "ac-02.02_odp.02", - "constraints": [ - { - "description": "no more than 24 hours from last use" - } - ] - }, - { - "param-id": "ac-02.03_odp.01", - "constraints": [ - { - "description": "24 hours for user accounts" - } - ] - }, - { - "param-id": "ac-02.03_odp.02", - "constraints": [ - { - "description": "thirty-five (35) days (See additional requirements and guidance.)" - } - ] - }, - { - "param-id": "ac-02.05_odp", - "constraints": [ - { - "description": "inactivity is anticipated to exceed Fifteen (15) minutes" - } - ] - }, - { - "param-id": "ac-02.09_odp", - "constraints": [ - { - "description": "organization-defined need with justification statement that explains why such accounts are necessary" - } - ] - }, - { - "param-id": "ac-02.12_odp.02", - "constraints": [ - { - "description": "at a minimum, the ISSO and/or similar role within the organization" - } - ] - }, - { - "param-id": "ac-02.13_odp.01", - "constraints": [ - { - "description": "one (1) hour" - } - ] - }, - { - "param-id": "ac-04.04_odp.01", - "constraints": [ - { - "description": "intrusion detection mechanisms" - } - ] - }, - { - "param-id": "ac-06.01_odp.02", - "constraints": [ - { - "description": "all functions not publicly accessible" - } - ] - }, - { - "param-id": "ac-06.01_odp.03", - "constraints": [ - { - "description": "all functions not publicly accessible" - } - ] - }, - { - "param-id": "ac-06.01_odp.04", - "constraints": [ - { - "description": "all functions not publicly accessible" - } - ] - }, - { - "param-id": "ac-06.01_odp.05", - "constraints": [ - { - "description": "all security-relevant information not publicly available" - } - ] - }, - { - "param-id": "ac-06.02_odp", - "constraints": [ - { - "description": "all security functions" - } - ] - }, - { - "param-id": "ac-06.03_odp.01", - "constraints": [ - { - "description": "all privileged commands" - } - ] - }, - { - "param-id": "ac-06.07_odp.01", - "constraints": [ - { - "description": "at a minimum, annually" - } - ] - }, - { - "param-id": "ac-06.07_odp.02", - "constraints": [ - { - "description": "all users with privileges" - } - ] - }, - { - "param-id": "ac-06.08_odp", - "constraints": [ - { - "description": "any software except software explicitly documented" - } - ] - }, - { - "param-id": "ac-08_odp.01", - "constraints": [ - { - "description": "see additional Requirements and Guidance" - } - ] - }, - { - "param-id": "ac-08_odp.02", - "constraints": [ - { - "description": "see additional Requirements and Guidance" - } - ] - }, - { - "param-id": "ac-10_odp.02", - "constraints": [ - { - "description": "three (3) sessions for privileged access and two (2) sessions for non-privileged access" - } - ] - }, - { - "param-id": "ac-11_odp.02", - "constraints": [ - { - "description": "fifteen (15) minutes" - } - ] - }, - { - "param-id": "ac-22_odp", - "constraints": [ - { - "description": "at least quarterly" - } - ] - }, - { - "param-id": "at-01_odp.05", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "at-01_odp.07", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "at-01_odp.08", - "constraints": [ - { - "description": "significant changes" - } - ] - }, - { - "param-id": "at-02_odp.01", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "at-02_odp.02", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "at-02_odp.06", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "at-03_odp.03", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "at-03_odp.04", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "at-04_odp", - "constraints": [ - { - "description": "five (5) years or 5 years after completion of a specific training program" - } - ] - }, - { - "param-id": "au-01_odp.05", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "au-01_odp.07", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "au-01_odp.08", - "constraints": [ - { - "description": "significant changes" - } - ] - }, - { - "param-id": "au-02_odp.01", - "constraints": [ - { - "description": "successful and unsuccessful account logon events, account management events, object access, policy change, privilege functions, process tracking, and system events. For Web applications: all administrator activity, authentication checks, authorization checks, data deletions, data access, data changes, and permission changes" - } - ] - }, - { - "param-id": "au-02_odp.02", - "constraints": [ - { - "description": "organization-defined subset of the auditable events defined in AU-2a to be audited continually for each identified event." - } - ] - }, - { - "param-id": "au-02_odp.03", - "constraints": [ - { - "description": "organization-defined subset of the auditable events defined in AU-2a to be audited continually for each identified event." - } - ] - }, - { - "param-id": "au-02_odp.04", - "constraints": [ - { - "description": "annually and whenever there is a change in the threat environment" - } - ] - }, - { - "param-id": "au-03.01_odp", - "constraints": [ - { - "description": "session, connection, transaction, or activity duration; for client-server transactions, the number of bytes received and bytes sent; additional informational messages to diagnose or identify the event; characteristics that describe or identify the object or resource being acted upon; individual identities of group account users; full-text of privileged commands" - } - ] - }, - { - "param-id": "au-05_odp.03", - "constraints": [ - { - "description": "overwrite oldest record" - } - ] - }, - { - "param-id": "au-05.01_odp.03", - "constraints": [ - { - "description": "75%, or one month before expected negative impact" - } - ] - }, - { - "param-id": "au-05.02_odp.01", - "constraints": [ - { - "description": "real-time" - } - ] - }, - { - "param-id": "au-05.02_odp.02", - "constraints": [ - { - "description": "service provider personnel with authority to address failed audit events" - } - ] - }, - { - "param-id": "au-05.02_odp.03", - "constraints": [ - { - "description": "audit failure events requiring real-time alerts, as defined by organization audit policy" - } - ] - }, - { - "param-id": "au-06_odp.01", - "constraints": [ - { - "description": "at least weekly" - } - ] - }, - { - "param-id": "au-06.05_odp.01", - "constraints": [ - { - "description": "vulnerability scanning information; performance data; information system monitoring information; penetration test data; {{ insert: param, au-06.05_odp.02 }}" - } - ] - }, - { - "param-id": "au-06.07_odp", - "constraints": [ - { - "description": "information system process; role; user" - } - ] - }, - { - "param-id": "au-08_odp", - "constraints": [ - { - "description": "one second granularity of time measurement" - } - ] - }, - { - "param-id": "au-09.02_odp", - "constraints": [ - { - "description": "at least weekly" - } - ] - }, - { - "param-id": "au-10_odp", - "constraints": [ - { - "description": "minimum actions including the addition, modification, deletion, approval, sending, or receiving of data" - } - ] - }, - { - "param-id": "au-11_odp", - "constraints": [ - { - "description": "a time period in compliance with M-21-31" - } - ] - }, - { - "param-id": "au-12_odp.01", - "constraints": [ - { - "description": "all information system and network components where audit capability is deployed/available" - } - ] - }, - { - "param-id": "au-12.01_odp.01", - "constraints": [ - { - "description": "all network, data storage, and computing devices" - } - ] - }, - { - "param-id": "au-12.03_odp.01", - "constraints": [ - { - "description": "service provider-defined individuals or roles with audit configuration responsibilities" - } - ] - }, - { - "param-id": "au-12.03_odp.02", - "constraints": [ - { - "description": "all network, data storage, and computing devices" - } - ] - }, - { - "param-id": "ca-01_odp.05", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ca-01_odp.07", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ca-01_odp.08", - "constraints": [ - { - "description": "significant changes" - } - ] - }, - { - "param-id": "ca-02_odp.01", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ca-02_odp.02", - "constraints": [ - { - "description": "individuals or roles to include FedRAMP PMO" - } - ] - }, - { - "param-id": "ca-02.02_odp.01", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ca-02.03_odp.01", - "constraints": [ - { - "description": "any FedRAMP Accredited 3PAO" - } - ] - }, - { - "param-id": "ca-02.03_odp.03", - "constraints": [ - { - "description": "the conditions of the AO in the FedRAMP Repository" - } - ] - }, - { - "param-id": "ca-03_odp.03", - "constraints": [ - { - "description": "at least annually and on input from AO" - } - ] - }, - { - "param-id": "ca-05_odp", - "constraints": [ - { - "description": "at least monthly" - } - ] - }, - { - "param-id": "ca-06_odp", - "constraints": [ - { - "description": "in accordance with OMB A-130 requirements or when a significant change occurs" - } - ] - }, - { - "param-id": "ca-07_odp.04", - "constraints": [ - { - "description": "to include AO" - } - ] - }, - { - "param-id": "ca-07_odp.06", - "constraints": [ - { - "description": "to include AO" - } - ] - }, - { - "param-id": "ca-08_odp.01", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ca-09_odp.03", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "cm-01_odp.05", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "cm-01_odp.07", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "cm-01_odp.08", - "constraints": [ - { - "description": "significant changes" - } - ] - }, - { - "param-id": "cm-02_odp.01", - "constraints": [ - { - "description": "at least annually and when a significant change occurs" - } - ] - }, - { - "param-id": "cm-02_odp.02", - "constraints": [ - { - "description": "to include when directed by the AO" - } - ] - }, - { - "param-id": "cm-02.03_odp", - "constraints": [ - { - "description": "organization-defined number of previous versions of baseline configurations of the previously approved baseline configuration of IS components" - } - ] - }, - { - "param-id": "cm-03.01_odp.03", - "constraints": [ - { - "description": "organization agreed upon time period" - } - ] - }, - { - "param-id": "cm-03.01_odp.04", - "constraints": [ - { - "description": "organization defined configuration management approval authorities" - } - ] - }, - { - "param-id": "cm-03.04_odp.03", - "constraints": [ - { - "description": "Configuration control board (CCB) or similar (as defined in CM-3)" - } - ] - }, - { - "param-id": "cm-03.06_odp", - "constraints": [ - { - "description": "All security safeguards that rely on cryptography" - } - ] - }, - { - "param-id": "cm-05.05_odp.01", - "constraints": [ - { - "description": "at least quarterly" - } - ] - }, - { - "param-id": "cm-05.05_odp.02", - "constraints": [ - { - "description": "at least quarterly" - } - ] - }, - { - "param-id": "cm-07.01_odp.01", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "cm-07.05_odp.02", - "constraints": [ - { - "description": "at least quarterly or when there is a change" - } - ] - }, - { - "param-id": "cm-08_odp.02", - "constraints": [ - { - "description": "at least monthly" - } - ] - }, - { - "param-id": "cm-08.03_odp.01", - "constraints": [ - { - "description": "automated mechanisms with a maximum five-minute delay in detection" - } - ] - }, - { - "param-id": "cm-08.03_odp.02", - "constraints": [ - { - "description": "automated mechanisms with a maximum five-minute delay in detection" - } - ] - }, - { - "param-id": "cm-08.03_odp.03", - "constraints": [ - { - "description": "automated mechanisms with a maximum five-minute delay in detection" - } - ] - }, - { - "param-id": "cm-08.03_odp.04", - "constraints": [ - { - "description": "continuously" - } - ] - }, - { - "param-id": "cm-08.04_odp", - "constraints": [ - { - "description": "position and role" - } - ] - }, - { - "param-id": "cm-11_odp.03", - "constraints": [ - { - "description": "Continuously (via CM-7 (5))" - } - ] - }, - { - "param-id": "cm-12.01_odp.01", - "constraints": [ - { - "description": "Federal data and system data that must be protected at the High or Moderate impact levels" - } - ] - }, - { - "param-id": "cp-01_odp.05", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "cp-01_odp.07", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "cp-01_odp.08", - "constraints": [ - { - "description": "significant changes" - } - ] - }, - { - "param-id": "cp-02_odp.05", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "cp-02.03_odp.01", - "constraints": [ - { - "description": "all" - } - ] - }, - { - "param-id": "cp-02.03_odp.02", - "constraints": [ - { - "description": "time period defined in service provider and organization SLA" - } - ] - }, - { - "param-id": "cp-02.05_odp", - "constraints": [ - { - "description": "essential" - } - ] - }, - { - "param-id": "cp-03_odp.01", - "constraints": [ - { - "description": "\\*See Additional Requirements" - } - ] - }, - { - "param-id": "cp-03_odp.02", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "cp-03_odp.03", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "cp-04_odp.01", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "cp-04_odp.02", - "constraints": [ - { - "description": "functional exercises" - } - ] - }, - { - "param-id": "cp-04_odp.03", - "constraints": [ - { - "description": "functional exercises" - } - ] - }, - { - "param-id": "cp-08.04_odp.01", - "constraints": [ - { - "description": "annually" - } - ] - }, - { - "param-id": "cp-08.04_odp.02", - "constraints": [ - { - "description": "annually" - } - ] - }, - { - "param-id": "cp-09_odp.02", - "constraints": [ - { - "description": "daily incremental; weekly full" - } - ] - }, - { - "param-id": "cp-09_odp.03", - "constraints": [ - { - "description": "daily incremental; weekly full" - } - ] - }, - { - "param-id": "cp-09_odp.04", - "constraints": [ - { - "description": "daily incremental; weekly full" - } - ] - }, - { - "param-id": "cp-09.01_odp.01", - "constraints": [ - { - "description": "at least monthly" - } - ] - }, - { - "param-id": "cp-09.01_odp.02", - "constraints": [ - { - "description": "at least monthly" - } - ] - }, - { - "param-id": "cp-09.05_odp.01", - "constraints": [ - { - "description": "time period and transfer rate consistent with the recovery time and recovery point objectives defined in the service provider and organization SLA." - } - ] - }, - { - "param-id": "cp-09.05_odp.02", - "constraints": [ - { - "description": "time period and transfer rate consistent with the recovery time and recovery point objectives defined in the service provider and organization SLA." - } - ] - }, - { - "param-id": "cp-09.08_odp", - "constraints": [ - { - "description": "all backup files" - } - ] - }, - { - "param-id": "cp-10.04_odp", - "constraints": [ - { - "description": "time period consistent with the restoration time-periods defined in the service provider and organization SLA" - } - ] - }, - { - "param-id": "ia-01_odp.05", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ia-01_odp.07", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ia-01_odp.08", - "constraints": [ - { - "description": "significant changes" - } - ] - }, - { - "param-id": "ia-02.06_odp.01", - "constraints": [ - { - "description": "local, network and remote" - } - ] - }, - { - "param-id": "ia-02.06_odp.02", - "constraints": [ - { - "description": "privileged accounts; non-privileged accounts" - } - ] - }, - { - "param-id": "ia-02.06_odp.03", - "constraints": [ - { - "description": "FIPS-validated or NSA-approved cryptography" - } - ] - }, - { - "param-id": "ia-02.08_odp", - "constraints": [ - { - "description": "privileged accounts; non-privileged accounts" - } - ] - }, - { - "param-id": "ia-04_odp.01", - "constraints": [ - { - "description": "at a minimum, the ISSO (or similar role within the organization)" - } - ] - }, - { - "param-id": "ia-04_odp.02", - "constraints": [ - { - "description": "at least two (2) years" - } - ] - }, - { - "param-id": "ia-04.04_odp", - "constraints": [ - { - "description": "contractors; foreign nationals" - } - ] - }, - { - "param-id": "ia-05.08_odp", - "constraints": [ - { - "description": "different authenticators in different user authentication domains" - } - ] - }, - { - "param-id": "ir-01_odp.05", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ir-01_odp.07", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ir-01_odp.08", - "constraints": [ - { - "description": "significant changes" - } - ] - }, - { - "param-id": "ir-02_odp.01", - "constraints": [ - { - "description": "ten (10) days for privileged users, thirty (30) days for Incident Response roles" - } - ] - }, - { - "param-id": "ir-02_odp.02", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ir-02_odp.03", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ir-03_odp.01", - "constraints": [ - { - "description": "at least every six (6) months, including functional at least annually" - } - ] - }, - { - "param-id": "ir-04.02_odp.02", - "constraints": [ - { - "description": "all network, data storage, and computing devices" - } - ] - }, - { - "param-id": "ir-06_odp.01", - "constraints": [ - { - "description": "US-CERT incident reporting timelines as specified in NIST Special Publication 800-61 (as amended)" - } - ] - }, - { - "param-id": "ir-08_odp.02", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ir-08_odp.04", - "constraints": [ - { - "description": "see additional FedRAMP Requirements and Guidance" - } - ] - }, - { - "param-id": "ir-08_odp.05", - "constraints": [ - { - "description": "see additional FedRAMP Requirements and Guidance" - } - ] - }, - { - "param-id": "ir-08_odp.06", - "constraints": [ - { - "description": "see additional FedRAMP Requirements and Guidance" - } - ] - }, - { - "param-id": "ir-08_odp.07", - "constraints": [ - { - "description": "see additional FedRAMP Requirements and Guidance" - } - ] - }, - { - "param-id": "ir-09.02_odp", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ma-01_odp.05", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ma-01_odp.07", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ma-01_odp.08", - "constraints": [ - { - "description": "significant changes" - } - ] - }, - { - "param-id": "ma-03_odp", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ma-03.03_odp", - "constraints": [ - { - "description": "the information owner" - } - ] - }, - { - "param-id": "ma-06_odp.02", - "constraints": [ - { - "description": "a timeframe to support advertised uptime and availability" - } - ] - }, - { - "param-id": "mp-01_odp.05", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "mp-01_odp.07", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "mp-01_odp.08", - "constraints": [ - { - "description": "significant changes" - } - ] - }, - { - "param-id": "mp-02_odp.01", - "constraints": [ - { - "description": "all types of digital and/or non-digital media containing sensitive information" - } - ] - }, - { - "param-id": "mp-02_odp.03", - "constraints": [ - { - "description": "all types of digital and/or non-digital media containing sensitive information" - } - ] - }, - { - "param-id": "mp-03_odp.01", - "constraints": [ - { - "description": "no removable media types" - } - ] - }, - { - "param-id": "mp-03_odp.02", - "constraints": [ - { - "description": "organization-defined security safeguards not applicable" - } - ] - }, - { - "param-id": "mp-04_odp.01", - "constraints": [ - { - "description": "all types of digital and non-digital media with sensitive information" - } - ] - }, - { - "param-id": "mp-04_odp.02", - "constraints": [ - { - "description": "all types of digital and non-digital media with sensitive information" - } - ] - }, - { - "param-id": "mp-04_odp.03", - "constraints": [ - { - "description": "all types of digital and non-digital media with sensitive information" - } - ] - }, - { - "param-id": "mp-04_odp.04", - "constraints": [ - { - "description": "all types of digital and non-digital media with sensitive information" - } - ] - }, - { - "param-id": "mp-04_odp.05", - "constraints": [ - { - "description": "see additional FedRAMP requirements and guidance" - } - ] - }, - { - "param-id": "mp-04_odp.06", - "constraints": [ - { - "description": "see additional FedRAMP requirements and guidance" - } - ] - }, - { - "param-id": "mp-05_odp.01", - "constraints": [ - { - "description": "all media with sensitive information" - } - ] - }, - { - "param-id": "mp-05_odp.02", - "constraints": [ - { - "description": "prior to leaving secure/controlled environment: for digital media, encryption in compliance with Federal requirements and utilizes FIPS validated or NSA approved cryptography (see SC-13.); for non-digital media, secured in locked container" - } - ] - }, - { - "param-id": "mp-05_odp.03", - "constraints": [ - { - "description": "prior to leaving secure/controlled environment: for digital media, encryption in compliance with Federal requirements and utilizes FIPS validated or NSA approved cryptography (see SC-13.); for non-digital media, secured in locked container" - } - ] - }, - { - "param-id": "mp-06_odp.01", - "constraints": [ - { - "description": "techniques and procedures IAW NIST SP 800-88 Section 4: Reuse and Disposal of Storage Media and Hardware" - } - ] - }, - { - "param-id": "mp-06_odp.02", - "constraints": [ - { - "description": "techniques and procedures IAW NIST SP 800-88 Section 4: Reuse and Disposal of Storage Media and Hardware" - } - ] - }, - { - "param-id": "mp-06_odp.03", - "constraints": [ - { - "description": "techniques and procedures IAW NIST SP 800-88 Section 4: Reuse and Disposal of Storage Media and Hardware" - } - ] - }, - { - "param-id": "mp-06.02_odp.01", - "constraints": [ - { - "description": "at least every six (6) months" - } - ] - }, - { - "param-id": "mp-06.02_odp.02", - "constraints": [ - { - "description": "at least every six (6) months" - } - ] - }, - { - "param-id": "pe-01_odp.05", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "pe-01_odp.07", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "pe-01_odp.08", - "constraints": [ - { - "description": "significant changes" - } - ] - }, - { - "param-id": "pe-02_odp", - "constraints": [ - { - "description": "at least every ninety (90) days" - } - ] - }, - { - "param-id": "pe-03_odp.02", - "constraints": [ - { - "description": "CSP defined physical access control systems/devices AND guards" - } - ] - }, - { - "param-id": "pe-03_odp.06", - "constraints": [ - { - "description": "in all circumstances within restricted access area where the information system resides" - } - ] - }, - { - "param-id": "pe-03_odp.08", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "pe-03_odp.09", - "constraints": [ - { - "description": "at least annually or earlier as required by a security relevant event." - } - ] - }, - { - "param-id": "pe-03_odp.10", - "constraints": [ - { - "description": "at least annually or earlier as required by a security relevant event." - } - ] - }, - { - "param-id": "pe-06_odp.01", - "constraints": [ - { - "description": "at least monthly" - } - ] - }, - { - "param-id": "pe-08_odp.01", - "constraints": [ - { - "description": "for a minimum of one (1) year" - } - ] - }, - { - "param-id": "pe-08_odp.02", - "constraints": [ - { - "description": "at least monthly" - } - ] - }, - { - "param-id": "pe-10_odp.02", - "constraints": [ - { - "description": "near more than one egress point of the IT area and ensures it is labeled and protected by a cover to prevent accidental shut-off" - } - ] - }, - { - "param-id": "pe-11.01_odp", - "constraints": [ - { - "description": "automatically" - } - ] - }, - { - "param-id": "pe-13.01_odp.01", - "constraints": [ - { - "description": "service provider building maintenance/physical security personnel" - } - ] - }, - { - "param-id": "pe-13.01_odp.02", - "constraints": [ - { - "description": "service provider emergency responders with incident response responsibilities" - } - ] - }, - { - "param-id": "pe-14_odp.01", - "constraints": [ - { - "description": "consistent with American Society of Heating, Refrigerating and Air-conditioning Engineers (ASHRAE) document entitled Thermal Guidelines for Data Processing Environments" - } - ] - }, - { - "param-id": "pe-14_odp.04", - "constraints": [ - { - "description": "continuously" - } - ] - }, - { - "param-id": "pe-15.01_odp.01", - "constraints": [ - { - "description": "service provider building maintenance/physical security personnel" - } - ] - }, - { - "param-id": "pe-16_odp.01", - "constraints": [ - { - "description": "all information system components" - } - ] - }, - { - "param-id": "pe-16_odp.02", - "constraints": [ - { - "description": "all information system components" - } - ] - }, - { - "param-id": "pe-18_odp", - "constraints": [ - { - "description": "physical and environmental hazards identified during threat assessment" - } - ] - }, - { - "param-id": "pl-01_odp.05", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "pl-01_odp.07", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "pl-01_odp.08", - "constraints": [ - { - "description": "significant changes" - } - ] - }, - { - "param-id": "pl-02_odp.01", - "constraints": [ - { - "description": "to include chief privacy and ISSO and/or similar role or designees" - } - ] - }, - { - "param-id": "pl-02_odp.02", - "constraints": [ - { - "description": "to include chief privacy and ISSO and/or similar role" - } - ] - }, - { - "param-id": "pl-02_odp.03", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "pl-04_odp.01", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "pl-04_odp.02", - "constraints": [ - { - "description": "at least annually and when the rules are revised or changed" - } - ] - }, - { - "param-id": "pl-08_odp", - "constraints": [ - { - "description": "at least annually and when a significant change occurs" - } - ] - }, - { - "param-id": "ps-01_odp.05", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ps-01_odp.07", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ps-01_odp.08", - "constraints": [ - { - "description": "significant changes" - } - ] - }, - { - "param-id": "ps-02_odp", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ps-03_odp.01", - "constraints": [ - { - "description": "for national security clearances; a reinvestigation is required during the fifth (5th) year for top secret security clearance, the tenth (10th) year for secret security clearance, and fifteenth (15th) year for confidential security clearance.\n\nFor moderate risk law enforcement and high impact public trust level, a reinvestigation is required during the fifth (5th) year. There is no reinvestigation for other moderate risk positions or any low risk positions" - } - ] - }, - { - "param-id": "ps-03_odp.02", - "constraints": [ - { - "description": "for national security clearances; a reinvestigation is required during the fifth (5th) year for top secret security clearance, the tenth (10th) year for secret security clearance, and fifteenth (15th) year for confidential security clearance.\n\nFor moderate risk law enforcement and high impact public trust level, a reinvestigation is required during the fifth (5th) year. There is no reinvestigation for other moderate risk positions or any low risk positions" - } - ] - }, - { - "param-id": "ps-03.03_odp", - "constraints": [ - { - "description": "personnel screening criteria - as required by specific information" - } - ] - }, - { - "param-id": "ps-04_odp.01", - "constraints": [ - { - "description": "one (1) hour" - } - ] - }, - { - "param-id": "ps-04.02_odp.02", - "constraints": [ - { - "description": "access control personnel responsible for disabling access to the system" - } - ] - }, - { - "param-id": "ps-05_odp.02", - "constraints": [ - { - "description": "twenty-four (24) hours" - } - ] - }, - { - "param-id": "ps-05_odp.03", - "constraints": [ - { - "description": "including access control personnel responsible for the system" - } - ] - }, - { - "param-id": "ps-05_odp.04", - "constraints": [ - { - "description": "twenty-four (24) hours" - } - ] - }, - { - "param-id": "ps-06_odp.01", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ps-06_odp.02", - "constraints": [ - { - "description": "at least annually and any time there is a change to the user's level of access" - } - ] - }, - { - "param-id": "ps-07_odp.01", - "constraints": [ - { - "description": "including access control personnel responsible for the system and/or facilities, as appropriate" - } - ] - }, - { - "param-id": "ps-07_odp.02", - "constraints": [ - { - "description": "terminations: immediately; transfers: within twenty-four (24) hours" - } - ] - }, - { - "param-id": "ps-08_odp.01", - "constraints": [ - { - "description": "to include the ISSO and/or similar role within the organization" - } - ] - }, - { - "param-id": "ps-08_odp.02", - "constraints": [ - { - "description": "24 hours" - } - ] - }, - { - "param-id": "ra-01_odp.05", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ra-01_odp.07", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "ra-01_odp.08", - "constraints": [ - { - "description": "significant changes" - } - ] - }, - { - "param-id": "ra-03_odp.01", - "constraints": [ - { - "description": "security assessment report" - } - ] - }, - { - "param-id": "ra-03_odp.03", - "constraints": [ - { - "description": "at least annually and whenever a significant change occurs" - } - ] - }, - { - "param-id": "ra-03_odp.05", - "constraints": [ - { - "description": "annually" - } - ] - }, - { - "param-id": "ra-05_odp.01", - "constraints": [ - { - "description": "monthly operating system/infrastructure; monthly web applications (including APIs) and databases" - } - ] - }, - { - "param-id": "ra-05_odp.02", - "constraints": [ - { - "description": "monthly operating system/infrastructure; monthly web applications (including APIs) and databases" - } - ] - }, - { - "param-id": "ra-05_odp.03", - "constraints": [ - { - "description": "high-risk vulnerabilities mitigated within thirty (30) days from date of discovery; moderate-risk vulnerabilities mitigated within ninety (90) days from date of discovery; low risk vulnerabilities mitigated within one hundred and eighty (180) days from date of discovery" - } - ] - }, - { - "param-id": "ra-05.02_odp.01", - "constraints": [ - { - "description": "within 24 hours prior to running scans" - } - ] - }, - { - "param-id": "ra-05.04_odp", - "constraints": [ - { - "description": "notify appropriate service provider personnel and follow procedures for organization and service provider-defined corrective actions" - } - ] - }, - { - "param-id": "ra-05.05_odp.01", - "constraints": [ - { - "description": "all components that support authentication" - } - ] - }, - { - "param-id": "ra-05.05_odp.02", - "constraints": [ - { - "description": "all scans" - } - ] - }, - { - "param-id": "sa-01_odp.05", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "sa-01_odp.07", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "sa-01_odp.08", - "constraints": [ - { - "description": "significant changes" - } - ] - }, - { - "param-id": "sa-04.02_odp.01", - "constraints": [ - { - "description": "at a minimum to include security-relevant external system interfaces; high-level design; low-level design; source code or network and data flow diagram;\n\norganization-defined design/implementation information" - } - ] - }, - { - "param-id": "sa-04.05_odp", - "constraints": [ - { - "description": "The service provider shall use the DoD STIGs to establish configuration settings; Center for Internet Security up to Level 2 (CIS Level 2) guidelines shall be used if STIGs are not available; Custom baselines shall be used if CIS is not available." - } - ] - }, - { - "param-id": "sa-05_odp.02", - "constraints": [ - { - "description": "at a minimum, the ISSO (or similar role within the organization)" - } - ] - }, - { - "param-id": "sa-09_odp.01", - "constraints": [ - { - "description": "Appropriate FedRAMP Security Controls Baseline (s) if Federal information is processed or stored within the external system" - } - ] - }, - { - "param-id": "sa-09_odp.02", - "constraints": [ - { - "description": "Federal/FedRAMP Continuous Monitoring requirements must be met for external systems where Federal information is processed or stored" - } - ] - }, - { - "param-id": "sa-09.02_odp", - "constraints": [ - { - "description": "all external systems where Federal information is processed or stored" - } - ] - }, - { - "param-id": "sa-09.05_odp.01", - "constraints": [ - { - "description": "information processing, information or data, AND system services" - } - ] - }, - { - "param-id": "sa-09.05_odp.02", - "constraints": [ - { - "description": "U.S./U.S. Territories or geographic locations where there is U.S. jurisdiction" - } - ] - }, - { - "param-id": "sa-09.05_odp.03", - "constraints": [ - { - "description": "all High impact data, systems, or services" - } - ] - }, - { - "param-id": "sa-10_odp.01", - "constraints": [ - { - "description": "development, implementation, AND operation" - } - ] - }, - { - "param-id": "sa-15_odp.01", - "constraints": [ - { - "description": "frequency as before first use and annually thereafter" - } - ] - }, - { - "param-id": "sa-15_odp.02", - "constraints": [ - { - "description": "FedRAMP Security Authorization requirements" - } - ] - }, - { - "param-id": "sc-01_odp.05", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "sc-01_odp.07", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "sc-01_odp.08", - "constraints": [ - { - "description": "significant changes" - } - ] - }, - { - "param-id": "sc-05_odp.02", - "constraints": [ - { - "description": "Protect against" - } - ] - }, - { - "param-id": "sc-05_odp.01", - "constraints": [ - { - "description": "at a minimum: ICMP (ping) flood, SYN flood, slowloris, buffer overflow attack, and volume attack" - } - ] - }, - { - "param-id": "sc-07.04_odp", - "constraints": [ - { - "description": "at least every ninety (90) days or whenever there is a change in the threat environment that warrants a review of the exceptions" - } - ] - }, - { - "param-id": "sc-07.05_odp.01", - "constraints": [ - { - "description": "any systems" - } - ] - }, - { - "param-id": "sc-07.08_odp.02", - "constraints": [ - { - "description": "any network outside of organizational control and any network outside the authorization boundary" - } - ] - }, - { - "param-id": "sc-07.12_odp.01", - "constraints": [ - { - "description": "Host Intrusion Prevention System (HIPS), Host Intrusion Detection System (HIDS), or minimally a host-based firewall" - } - ] - }, - { - "param-id": "sc-08_odp", - "constraints": [ - { - "description": "confidentiality AND integrity" - } - ] - }, - { - "param-id": "sc-08.01_odp", - "constraints": [ - { - "description": "prevent unauthorized disclosure of information AND detect changes to information" - } - ] - }, - { - "param-id": "sc-10_odp", - "constraints": [ - { - "description": "no longer than ten (10) minutes for privileged sessions and no longer than fifteen (15) minutes for user sessions" - } - ] - }, - { - "param-id": "sc-12_odp", - "constraints": [ - { - "description": "In accordance with Federal requirements" - } - ] - }, - { - "param-id": "sc-13_odp.02", - "constraints": [ - { - "description": "FIPS-validated or NSA-approved cryptography" - } - ] - }, - { - "param-id": "sc-15_odp", - "constraints": [ - { - "description": "no exceptions for computing devices" - } - ] - }, - { - "param-id": "sc-28_odp.01", - "constraints": [ - { - "description": "confidentiality AND integrity" - } - ] - }, - { - "param-id": "sc-28.01_odp.02", - "constraints": [ - { - "description": "all information system components storing Federal data or system data that must be protected at the High or Moderate impact levels" - } - ] - }, - { - "param-id": "sc-45.01_odp.01", - "constraints": [ - { - "description": "At least hourly" - } - ] - }, - { - "param-id": "sc-45.01_odp.02", - "constraints": [ - { - "description": "http://tf.nist.gov/tf-cgi/servers.cgi" - } - ] - }, - { - "param-id": "sc-45.01_odp.03", - "constraints": [ - { - "description": "any difference" - } - ] - }, - { - "param-id": "si-01_odp.05", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "si-01_odp.07", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "si-01_odp.08", - "constraints": [ - { - "description": "significant changes" - } - ] - }, - { - "param-id": "si-02_odp", - "constraints": [ - { - "description": "within thirty (30) days of release of updates" - } - ] - }, - { - "param-id": "si-02.02_odp.02", - "constraints": [ - { - "description": "at least monthly" - } - ] - }, - { - "param-id": "si-03_odp.01", - "constraints": [ - { - "description": "signature based and non-signature based" - } - ] - }, - { - "param-id": "si-03_odp.02", - "constraints": [ - { - "description": "at least weekly" - } - ] - }, - { - "param-id": "si-03_odp.03", - "constraints": [ - { - "description": "to include endpoints and network entry and exit points" - } - ] - }, - { - "param-id": "si-03_odp.04", - "constraints": [ - { - "description": "to include blocking and quarantining malicious code" - } - ] - }, - { - "param-id": "si-03_odp.06", - "constraints": [ - { - "description": "administrator or defined security personnel near-realtime" - } - ] - }, - { - "param-id": "si-04.04_odp.01", - "constraints": [ - { - "description": "continuously" - } - ] - }, - { - "param-id": "si-04.04_odp.03", - "constraints": [ - { - "description": "continuously" - } - ] - }, - { - "param-id": "si-05_odp.01", - "constraints": [ - { - "description": "to include US-CERT and Cybersecurity and Infrastructure Security Agency (CISA) Directives" - } - ] - }, - { - "param-id": "si-05_odp.02", - "constraints": [ - { - "description": "to include system security personnel and administrators with configuration/patch-management responsibilities" - } - ] - }, - { - "param-id": "si-06_odp.04", - "constraints": [ - { - "description": "to include upon system startup and/or restart" - } - ] - }, - { - "param-id": "si-06_odp.05", - "constraints": [ - { - "description": "at least monthly" - } - ] - }, - { - "param-id": "si-06_odp.06", - "constraints": [ - { - "description": "to include system administrators and security personnel" - } - ] - }, - { - "param-id": "si-07.01_odp.03", - "constraints": [ - { - "description": "selection to include security relevant event" - } - ] - }, - { - "param-id": "si-07.01_odp.07", - "constraints": [ - { - "description": "selection to include security relevant event" - } - ] - }, - { - "param-id": "si-07.01_odp.11", - "constraints": [ - { - "description": "selection to include security relevant event" - } - ] - }, - { - "param-id": "si-07.01_odp.04", - "constraints": [ - { - "description": "at least monthly" - } - ] - }, - { - "param-id": "si-07.01_odp.08", - "constraints": [ - { - "description": "at least monthly" - } - ] - }, - { - "param-id": "si-07.01_odp.12", - "constraints": [ - { - "description": "at least monthly" - } - ] - }, - { - "param-id": "si-07.02_odp", - "constraints": [ - { - "description": "to include the ISSO and/or similar role within the organization" - } - ] - }, - { - "param-id": "si-07.15_odp", - "constraints": [ - { - "description": "to include all software and firmware inside the boundary" - } - ] - }, - { - "param-id": "si-11_odp", - "constraints": [ - { - "description": "to include the ISSO and/or similar role within the organization" - } - ] - }, - { - "param-id": "sr-01_odp.01", - "constraints": [ - { - "description": "to include chief privacy and ISSO and/or similar role or designees" - } - ] - }, - { - "param-id": "sr-01_odp.02", - "constraints": [ - { - "description": "to include chief privacy and ISSO and/or similar role or designees" - } - ] - }, - { - "param-id": "sr-01_odp.05", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "sr-01_odp.07", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "sr-01_odp.08", - "constraints": [ - { - "description": "significant changes" - } - ] - }, - { - "param-id": "sr-02_odp.02", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "sr-06_odp", - "constraints": [ - { - "description": "at least annually" - } - ] - }, - { - "param-id": "sr-08_odp.01", - "constraints": [ - { - "description": "notification of supply chain compromises and results of assessment or audits" - } - ] - }, - { - "param-id": "sr-11.02_odp", - "constraints": [ - { - "description": "all" - } - ] - } - ] - }, - "back-matter": { - "resources": [ - { - "uuid": "985475ee-d4d6-4581-8fdf-d84d3d8caa48", - "title": "FedRAMP Applicable Laws and Regulations", - "rlinks": [ - { - "href": "https://www.fedramp.gov/assets/resources/templates/SSP-A12-FedRAMP-Laws-and-Regulations-Template.xlsx" - } - ] - }, - { - "uuid": "a2381e87-3d04-4108-a30b-b4d2f36d001f", - "description": "FedRAMP Logo", - "props": [ - { - "name": "type", - "value": "logo" - } - ], - "rlinks": [ - { - "href": "https://www.fedramp.gov/assets/img/logo-main-fedramp.png" - } - ] - }, - { - "uuid": "051a77c1-b61d-4995-8275-dacfe688d510", - "title": "NIST Special Publication (SP) 800-53 revision 5", - "props": [ - { - "name": "version", - "value": "5.1.1" - } - ], - "rlinks": [ - { - "href": "./FedRAMP_rev5_catalog_tailoring_profile.json", - "media-type": "application/oscal+json" - } - ] - } - ] - } - } -} diff --git a/data/profiles/govramp_moderate_cjis_profile.json b/data/profiles/govramp_moderate_cjis_profile.json deleted file mode 100644 index 1dca9414..00000000 --- a/data/profiles/govramp_moderate_cjis_profile.json +++ /dev/null @@ -1,364 +0,0 @@ -{ - "profile": { - "uuid": "87d72b1b-cc5f-5e90-bcf6-a90d235e8211", - "metadata": { - "title": "GovRAMP Moderate (Rev5) + CJIS overlay", - "last-modified": "2026-06-10T00:00:00Z", - "version": "1.0.0", - "oscal-version": "1.2.2" - }, - "imports": [ - { - "href": "../catalogs/NIST_SP-800-53_rev5_catalog.json", - "include-controls": [ - { - "with-ids": [ - "ac-1", - "ac-11", - "ac-11.1", - "ac-12", - "ac-14", - "ac-17", - "ac-17.1", - "ac-17.2", - "ac-17.3", - "ac-17.4", - "ac-18", - "ac-18.1", - "ac-18.3", - "ac-19", - "ac-19.5", - "ac-2", - "ac-2.1", - "ac-2.12", - "ac-2.13", - "ac-2.2", - "ac-2.3", - "ac-2.4", - "ac-2.5", - "ac-2.7", - "ac-2.9", - "ac-20", - "ac-20.1", - "ac-20.2", - "ac-21", - "ac-22", - "ac-3", - "ac-3.14", - "ac-4", - "ac-4.21", - "ac-5", - "ac-6", - "ac-6.1", - "ac-6.10", - "ac-6.2", - "ac-6.5", - "ac-6.7", - "ac-6.9", - "ac-7", - "ac-8", - "at-1", - "at-2", - "at-2.2", - "at-2.3", - "at-3", - "at-3.5", - "at-4", - "au-1", - "au-11", - "au-12", - "au-2", - "au-3", - "au-3.1", - "au-3.3", - "au-4", - "au-5", - "au-6", - "au-6.1", - "au-6.3", - "au-7", - "au-7.1", - "au-8", - "au-9", - "au-9.4", - "ca-1", - "ca-2", - "ca-2.1", - "ca-2.3", - "ca-3", - "ca-5", - "ca-6", - "ca-7", - "ca-7.1", - "ca-7.4", - "ca-8", - "ca-8.1", - "ca-9", - "cm-1", - "cm-10", - "cm-11", - "cm-12", - "cm-12.1", - "cm-2", - "cm-2.2", - "cm-2.3", - "cm-2.7", - "cm-3", - "cm-3.2", - "cm-3.4", - "cm-4", - "cm-4.2", - "cm-5", - "cm-5.1", - "cm-5.5", - "cm-6", - "cm-6.1", - "cm-7", - "cm-7.1", - "cm-7.2", - "cm-7.5", - "cm-8", - "cm-8.1", - "cm-8.3", - "cm-9", - "cp-1", - "cp-10", - "cp-10.2", - "cp-2", - "cp-2.1", - "cp-2.3", - "cp-2.8", - "cp-3", - "cp-4", - "cp-4.1", - "cp-6", - "cp-6.1", - "cp-6.3", - "cp-7", - "cp-7.1", - "cp-7.2", - "cp-7.3", - "cp-8", - "cp-8.1", - "cp-8.2", - "cp-9", - "cp-9.1", - "cp-9.8", - "ia-0", - "ia-1", - "ia-11", - "ia-12", - "ia-12.2", - "ia-12.3", - "ia-12.5", - "ia-2", - "ia-2.1", - "ia-2.12", - "ia-2.2", - "ia-2.5", - "ia-2.6", - "ia-2.8", - "ia-3", - "ia-4", - "ia-4.4", - "ia-5", - "ia-5.1", - "ia-5.2", - "ia-5.6", - "ia-5.7", - "ia-5.j", - "ia-5.k", - "ia-5.l", - "ia-5.m", - "ia-5.n", - "ia-5.o", - "ia-6", - "ia-7", - "ia-8", - "ia-8.1", - "ia-8.2", - "ia-8.4", - "ir-1", - "ir-2", - "ir-2.3", - "ir-3", - "ir-3.2", - "ir-4", - "ir-4.1", - "ir-5", - "ir-6", - "ir-6.1", - "ir-6.3", - "ir-7", - "ir-7.1", - "ir-8", - "ir-8.1", - "ir-9", - "ir-9.2", - "ir-9.3", - "ir-9.4", - "ma-1", - "ma-2", - "ma-3", - "ma-3.1", - "ma-3.2", - "ma-3.3", - "ma-4", - "ma-5", - "ma-5.1", - "ma-6", - "mp-1", - "mp-2", - "mp-3", - "mp-4", - "mp-5", - "mp-6", - "mp-7", - "pe-1", - "pe-10", - "pe-11", - "pe-12", - "pe-13", - "pe-13.1", - "pe-13.2", - "pe-14", - "pe-15", - "pe-16", - "pe-17", - "pe-2", - "pe-3", - "pe-4", - "pe-5", - "pe-6", - "pe-6.1", - "pe-8", - "pe-8.3", - "pe-9", - "pl-1", - "pl-10", - "pl-11", - "pl-2", - "pl-4", - "pl-4.1", - "pl-8", - "pl-9", - "ps-1", - "ps-2", - "ps-3", - "ps-3.3", - "ps-4", - "ps-5", - "ps-6", - "ps-7", - "ps-8", - "ps-9", - "ra-1", - "ra-2", - "ra-3", - "ra-3.1", - "ra-5", - "ra-5.11", - "ra-5.2", - "ra-5.3", - "ra-5.5", - "ra-7", - "ra-9", - "sa-1", - "sa-10", - "sa-11", - "sa-11.1", - "sa-11.2", - "sa-15", - "sa-15.3", - "sa-2", - "sa-22", - "sa-3", - "sa-4", - "sa-4.1", - "sa-4.2", - "sa-4.9", - "sa-5", - "sa-8", - "sa-9", - "sa-9.1", - "sa-9.2", - "sa-9.5", - "sc-1", - "sc-10", - "sc-12", - "sc-13", - "sc-15", - "sc-17", - "sc-18", - "sc-2", - "sc-20", - "sc-21", - "sc-22", - "sc-23", - "sc-28", - "sc-28.1", - "sc-39", - "sc-4", - "sc-45", - "sc-45.1", - "sc-5", - "sc-7", - "sc-7.12", - "sc-7.18", - "sc-7.23", - "sc-7.3", - "sc-7.4", - "sc-7.5", - "sc-7.7", - "sc-7.8", - "sc-8", - "sc-8.1", - "si-1", - "si-10", - "si-11", - "si-12", - "si-12.1", - "si-12.2", - "si-12.3", - "si-16", - "si-2", - "si-2.2", - "si-2.3", - "si-3", - "si-4", - "si-4.1", - "si-4.16", - "si-4.18", - "si-4.2", - "si-4.23", - "si-4.4", - "si-4.5", - "si-5", - "si-6", - "si-7", - "si-7.1", - "si-7.7", - "si-8", - "si-8.2", - "sr-1", - "sr-10", - "sr-11", - "sr-11.1", - "sr-11.2", - "sr-12", - "sr-2", - "sr-2.1", - "sr-3", - "sr-5", - "sr-6", - "sr-8" - ] - } - ] - } - ], - "merge": { - "as-is": true - } - } -} diff --git a/data/profiles/txramp_level1_profile.json b/data/profiles/txramp_level1_profile.json deleted file mode 100644 index 7f1c1a6d..00000000 --- a/data/profiles/txramp_level1_profile.json +++ /dev/null @@ -1,147 +0,0 @@ -{ - "profile": { - "uuid": "7c8f564d-3ee8-5f4d-ae66-88bbdc21657d", - "metadata": { - "title": "TX-RAMP Level 1 (Rev4 baseline)", - "last-modified": "2026-06-10T00:00:00Z", - "version": "1.0.0", - "oscal-version": "1.2.2" - }, - "imports": [ - { - "href": "../catalogs/NIST_SP-800-53_rev4_catalog.json", - "include-controls": [ - { - "with-ids": [ - "ac-1", - "ac-14", - "ac-17", - "ac-18", - "ac-19", - "ac-2", - "ac-20", - "ac-22", - "ac-3", - "ac-7", - "ac-8", - "at-1", - "at-2", - "at-3", - "at-4", - "au-1", - "au-11", - "au-12", - "au-2", - "au-3", - "au-4", - "au-5", - "au-6", - "au-8", - "au-9", - "ca-1", - "ca-2", - "ca-2.1", - "ca-3", - "ca-5", - "ca-6", - "ca-7", - "ca-9", - "cm-1", - "cm-10", - "cm-11", - "cm-2", - "cm-4", - "cm-6", - "cm-7", - "cm-8", - "cp-1", - "cp-10", - "cp-2", - "cp-3", - "cp-4", - "cp-9", - "ia-1", - "ia-2", - "ia-2.1", - "ia-2.12", - "ia-4", - "ia-5", - "ia-5.1", - "ia-5.11", - "ia-6", - "ia-7", - "ia-8", - "ia-8.2", - "ia-8.3", - "ir-1", - "ir-2", - "ir-4", - "ir-5", - "ir-6", - "ir-7", - "ir-8", - "ir-9", - "ma-1", - "ma-2", - "ma-4", - "ma-5", - "mp-1", - "mp-2", - "mp-6", - "mp-7", - "pe-1", - "pe-13", - "pe-14", - "pe-15", - "pe-16", - "pe-2", - "pe-3", - "pe-6", - "pe-8", - "pl-1", - "pl-2", - "pl-4", - "ps-1", - "ps-2", - "ps-3", - "ps-4", - "ps-5", - "ps-6", - "ps-7", - "ps-8", - "ra-1", - "ra-2", - "ra-3", - "ra-5", - "sa-1", - "sa-2", - "sa-3", - "sa-4", - "sa-4.1", - "sa-5", - "sa-9", - "sc-1", - "sc-15", - "sc-20", - "sc-21", - "sc-22", - "sc-39", - "sc-5", - "sc-7", - "si-1", - "si-12", - "si-16", - "si-2", - "si-3", - "si-4", - "si-5" - ] - } - ] - } - ], - "merge": { - "as-is": true - } - } -} diff --git a/data/profiles/txramp_level2_profile.json b/data/profiles/txramp_level2_profile.json deleted file mode 100644 index 2121504b..00000000 --- a/data/profiles/txramp_level2_profile.json +++ /dev/null @@ -1,347 +0,0 @@ -{ - "profile": { - "uuid": "c66b0169-8241-5622-95ce-6722a1deac6b", - "metadata": { - "title": "TX-RAMP Level 2 (Rev4 baseline)", - "last-modified": "2026-06-10T00:00:00Z", - "version": "1.0.0", - "oscal-version": "1.2.2" - }, - "imports": [ - { - "href": "../catalogs/NIST_SP-800-53_rev4_catalog.json", - "include-controls": [ - { - "with-ids": [ - "ac-1", - "ac-10", - "ac-11", - "ac-11.1", - "ac-12", - "ac-14", - "ac-17", - "ac-17.1", - "ac-17.2", - "ac-17.3", - "ac-17.4", - "ac-17.9", - "ac-18", - "ac-18.1", - "ac-19", - "ac-19.5", - "ac-2", - "ac-2.1", - "ac-2.10", - "ac-2.12", - "ac-2.2", - "ac-2.3", - "ac-2.4", - "ac-2.5", - "ac-2.7", - "ac-2.9", - "ac-20", - "ac-20.1", - "ac-20.2", - "ac-21", - "ac-22", - "ac-3", - "ac-4", - "ac-4.21", - "ac-5", - "ac-6", - "ac-6.1", - "ac-6.10", - "ac-6.2", - "ac-6.5", - "ac-6.9", - "ac-7", - "ac-8", - "at-1", - "at-2", - "at-2.2", - "at-3", - "at-4", - "au-1", - "au-11", - "au-12", - "au-2", - "au-2.3", - "au-3", - "au-3.1", - "au-4", - "au-5", - "au-6", - "au-6.1", - "au-6.3", - "au-7", - "au-7.1", - "au-8", - "au-8.1", - "au-9", - "au-9.2", - "au-9.4", - "ca-1", - "ca-2", - "ca-2.1", - "ca-2.2", - "ca-2.3", - "ca-3", - "ca-3.3", - "ca-3.5", - "ca-5", - "ca-6", - "ca-7", - "ca-7.1", - "ca-8", - "ca-8.1", - "ca-9", - "cm-1", - "cm-10", - "cm-10.1", - "cm-11", - "cm-2", - "cm-2.1", - "cm-2.2", - "cm-2.3", - "cm-2.7", - "cm-3", - "cm-3.2", - "cm-4", - "cm-5", - "cm-5.1", - "cm-5.3", - "cm-5.5", - "cm-6", - "cm-6.1", - "cm-7", - "cm-7.1", - "cm-7.2", - "cm-7.5", - "cm-8", - "cm-8.1", - "cm-8.3", - "cm-8.5", - "cm-9", - "cp-1", - "cp-10", - "cp-10.2", - "cp-2", - "cp-2.1", - "cp-2.2", - "cp-2.3", - "cp-2.8", - "cp-3", - "cp-4", - "cp-4.1", - "cp-6", - "cp-6.1", - "cp-6.3", - "cp-7", - "cp-7.1", - "cp-7.2", - "cp-7.3", - "cp-8", - "cp-8.1", - "cp-8.2", - "cp-9", - "cp-9.1", - "cp-9.3", - "ia-1", - "ia-2", - "ia-2.1", - "ia-2.11", - "ia-2.12", - "ia-2.2", - "ia-2.3", - "ia-2.5", - "ia-2.8", - "ia-3", - "ia-4", - "ia-4.4", - "ia-5", - "ia-5.1", - "ia-5.11", - "ia-5.2", - "ia-5.3", - "ia-5.4", - "ia-5.6", - "ia-5.7", - "ia-6", - "ia-7", - "ia-8", - "ia-8.2", - "ia-8.3", - "ir-1", - "ir-2", - "ir-3", - "ir-3.2", - "ir-4", - "ir-4.1", - "ir-5", - "ir-6", - "ir-6.1", - "ir-7", - "ir-7.1", - "ir-7.2", - "ir-8", - "ir-9", - "ir-9.1", - "ir-9.2", - "ir-9.3", - "ir-9.4", - "ma-1", - "ma-2", - "ma-3", - "ma-3.1", - "ma-3.2", - "ma-3.3", - "ma-4", - "ma-4.2", - "ma-5", - "ma-5.1", - "ma-6", - "mp-1", - "mp-2", - "mp-3", - "mp-4", - "mp-5", - "mp-5.4", - "mp-6", - "mp-6.2", - "mp-7", - "mp-7.1", - "pe-1", - "pe-10", - "pe-11", - "pe-12", - "pe-13", - "pe-13.2", - "pe-13.3", - "pe-14", - "pe-14.2", - "pe-15", - "pe-16", - "pe-17", - "pe-2", - "pe-3", - "pe-4", - "pe-5", - "pe-6", - "pe-6.1", - "pe-8", - "pe-9", - "pl-1", - "pl-2", - "pl-2.3", - "pl-4", - "pl-4.1", - "pl-8", - "ps-1", - "ps-2", - "ps-3", - "ps-4", - "ps-5", - "ps-6", - "ps-7", - "ps-8", - "ra-1", - "ra-2", - "ra-3", - "ra-5", - "ra-5.1", - "ra-5.2", - "ra-5.3", - "ra-5.5", - "ra-5.6", - "ra-5.8", - "sa-1", - "sa-10", - "sa-10.1", - "sa-11", - "sa-11.1", - "sa-11.2", - "sa-11.8", - "sa-2", - "sa-3", - "sa-4", - "sa-4.1", - "sa-4.2", - "sa-4.8", - "sa-4.9", - "sa-5", - "sa-8", - "sa-9", - "sa-9.1", - "sa-9.2", - "sa-9.4", - "sa-9.5", - "sc-1", - "sc-10", - "sc-12", - "sc-12.2", - "sc-12.3", - "sc-13", - "sc-15", - "sc-17", - "sc-18", - "sc-19", - "sc-2", - "sc-20", - "sc-21", - "sc-22", - "sc-23", - "sc-28", - "sc-28.1", - "sc-39", - "sc-4", - "sc-5", - "sc-6", - "sc-7", - "sc-7.12", - "sc-7.13", - "sc-7.18", - "sc-7.3", - "sc-7.4", - "sc-7.5", - "sc-7.7", - "sc-7.8", - "sc-8", - "sc-8.1", - "si-1", - "si-10", - "si-11", - "si-12", - "si-16", - "si-2", - "si-2.2", - "si-2.3", - "si-3", - "si-3.1", - "si-3.2", - "si-3.7", - "si-4", - "si-4.1", - "si-4.14", - "si-4.16", - "si-4.2", - "si-4.23", - "si-4.4", - "si-4.5", - "si-5", - "si-6", - "si-7", - "si-7.1", - "si-7.7", - "si-8", - "si-8.1", - "si-8.2" - ] - } - ] - } - ], - "merge": { - "as-is": true - } - } -} diff --git a/data/recurring-costs.json b/data/recurring-costs.json new file mode 100644 index 00000000..d621d83e --- /dev/null +++ b/data/recurring-costs.json @@ -0,0 +1,24 @@ +{ + "schema": "recurring-costs/1", + "$comment": "The recurring cost of the system, one line per thing that can bill, each with the repository file that creates it (or external:<what> for something outside the repository). Read by scripts/hold-security-review.py, which publishes it in the Annual Security Review (KSI-PIY-RIS) and fails on a line with no source. Every figure was AI-drafted on 2026-11-06 from what the repository shows (the resources in Terraform, the domain, the services the workflows use), not from a bill: they are estimates for the operator to correct. A line whose figure is not known says 'unknown' and carries no number.", + "status": "AI-drafted estimate; operator to correct", + "currency": "USD", + "period": "year", + "drafted_by": "AI-drafted (Claude)", + "drafted_on": "2026-11-06", + "lines": [ + {"id": "COST-KMS", "item": "Four customer-managed KMS keys (at-rest, runtime signing, DNSSEC key-signing, Silk Reeling)", "source": "infrastructure/main.tf", "estimate_usd_per_year": 48, "estimate": "about $48", "basis": "AWS's published list price of about $1 per customer-managed key per month, times four keys; request charges assumed negligible at this volume. Not checked against a bill."}, + {"id": "COST-ROUTE53", "item": "Route 53 hosted zone with DNSSEC, and its queries", "source": "infrastructure/main.tf", "estimate_usd_per_year": 6, "estimate": "about $6", "basis": "AWS's published list price of about $0.50 per hosted zone per month; query charges assumed small. Not checked against a bill."}, + {"id": "COST-ALARMS", "item": "CloudWatch metric alarms of the evidence watchdog", "source": "infrastructure/watchdog.tf", "estimate_usd_per_year": null, "estimate": "unknown", "basis": "A few standard alarms; the free tier may cover them. Not checked against a bill."}, + {"id": "COST-LOGS", "item": "CloudWatch Logs: five log groups kept 365 days, and Route 53 query logging", "source": "infrastructure/main.tf", "estimate_usd_per_year": null, "estimate": "unknown", "basis": "Ingestion and storage depend on traffic; small at current volume."}, + {"id": "COST-S3", "item": "S3 storage and requests: the site, access-log, CloudTrail and Terraform state buckets", "source": "infrastructure/cloudtrail.tf", "estimate_usd_per_year": null, "estimate": "unknown", "basis": "Depends on stored volume and requests; versioning and log retention grow it slowly."}, + {"id": "COST-CLOUDFRONT", "item": "CloudFront distribution (Shield Standard included at no charge)", "source": "infrastructure/bootstrap/main.tf", "estimate_usd_per_year": null, "estimate": "unknown", "basis": "Depends on traffic; may fall within the free tier."}, + {"id": "COST-CLOUDTRAIL", "item": "CloudTrail management-event trail", "source": "infrastructure/cloudtrail.tf", "estimate_usd_per_year": 0, "estimate": "about $0", "basis": "The first copy of management events is not charged by CloudTrail; its S3 storage is in COST-S3. LookupEvents (the audit-log review) is not charged. Not checked against a bill."}, + {"id": "COST-SERVERLESS", "item": "Lambda (three functions), EventBridge schedules, API Gateway HTTP API, SQS, SNS and DynamoDB on demand with point-in-time recovery", "source": "infrastructure/silk-reeling.tf", "estimate_usd_per_year": null, "estimate": "unknown", "basis": "Usage-priced; expected near zero at this volume, much of it inside the free tier."}, + {"id": "COST-COGNITO", "item": "Cognito user pool for Silk Reeling", "source": "infrastructure/cognito.tf", "estimate_usd_per_year": null, "estimate": "unknown", "basis": "Priced per monthly active user; a handful of users may fall within the free tier."}, + {"id": "COST-ACM", "item": "ACM public TLS certificate", "source": "external:AWS Certificate Manager", "estimate_usd_per_year": 0, "estimate": "about $0", "basis": "Public ACM certificates are not charged. Not checked against a bill."}, + {"id": "COST-DOMAIN", "item": "Registration of samaydlette.com", "source": "external:domain registrar", "estimate_usd_per_year": null, "estimate": "unknown", "basis": "The registrar and its price are not in the repository."}, + {"id": "COST-GITHUB", "item": "GitHub: public repository, Actions on standard hosted runners, code scanning", "source": ".github/workflows/deploy-with-opa.yml", "estimate_usd_per_year": 0, "estimate": "about $0", "basis": "GitHub does not bill Actions minutes on standard hosted runners for public repositories. Not checked against a bill."}, + {"id": "COST-SIGSTORE", "item": "Sigstore public-good signing (Fulcio, Rekor)", "source": "external:Sigstore public-good instance", "estimate_usd_per_year": 0, "estimate": "about $0", "basis": "A free public service."} + ] +} diff --git a/data/schemas/oscal/oscal_assessment-results_schema.json b/data/schemas/oscal/oscal_assessment-results_schema.json deleted file mode 100644 index 75764ed4..00000000 --- a/data/schemas/oscal/oscal_assessment-results_schema.json +++ /dev/null @@ -1,3470 +0,0 @@ - - { "$schema" : "http://json-schema.org/draft-07/schema#", - "$id" : "http://csrc.nist.gov/ns/oscal/1.2.2/oscal-ar-schema.json", - "$comment" : "OSCAL Assessment Results Model: JSON Schema", - "type" : "object", - "definitions" : - { "json-schema-directive" : - { "title" : "Schema Directive", - "description" : "A JSON Schema directive to bind a specific schema to its document instance.", - "$id" : "#/definitions/json-schema-directive", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "oscal-ar-oscal-ar:assessment-results" : - { "title" : "Security Assessment Results (SAR)", - "description" : "Security assessment results, such as those provided by a FedRAMP assessor in the FedRAMP Security Assessment Report.", - "$id" : "#/definitions/oscal-ar-oscal-ar:assessment-results", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Assessment Results Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment results instance in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "metadata" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:metadata" }, - "import-ap" : - { "$ref" : "#/definitions/oscal-ar-oscal-ar:import-ap" }, - "local-definitions" : - { "title" : "Local Definitions", - "description" : "Used to define data objects that are used in the assessment plan, that do not appear in the referenced SSP.", - "type" : "object", - "properties" : - { "objectives-and-methods" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:local-objective" } }, - "activities" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:activity" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - "results" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-ar:result" } }, - "back-matter" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:back-matter" } }, - "required" : - [ "uuid", - "metadata", - "import-ap", - "results" ], - "additionalProperties" : false }, - "oscal-ar-oscal-ar:result" : - { "title" : "Assessment Result", - "description" : "Used by the assessment results and POA&M. In the assessment results, this identifies all of the assessment observations and findings, initial and residual risks, deviations, and disposition. In the POA&M, this identifies initial and residual risks, deviations, and disposition.", - "$id" : "#/definitions/oscal-ar-oscal-ar:result", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Results Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this set of results in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Results Title", - "description" : "The title for this set of results.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Results Description", - "description" : "A human-readable description of this set of test results.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "start" : - { "title" : "start field", - "description" : "Date/time stamp identifying the start of the evidence collection reflected in these results.", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "end" : - { "title" : "end field", - "description" : "Date/time stamp identifying the end of the evidence collection reflected in these results. In a continuous motoring scenario, this may contain the same value as start if appropriate.", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "local-definitions" : - { "title" : "Local Definitions", - "description" : "Used to define data objects that are used in the assessment plan, that do not appear in the referenced SSP.", - "type" : "object", - "properties" : - { "components" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-implementation-common:system-component" } }, - "inventory-items" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-implementation-common:inventory-item" } }, - "users" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-implementation-common:system-user" } }, - "assessment-assets" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:assessment-assets" }, - "tasks" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:task" } } }, - "additionalProperties" : false }, - "reviewed-controls" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:reviewed-controls" }, - "attestations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Attestation Statements", - "description" : "A set of textual statements, typically written by the assessor.", - "type" : "object", - "properties" : - { "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:responsible-party" } }, - "parts" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:assessment-part" } } }, - "required" : - [ "parts" ], - "additionalProperties" : false } }, - "assessment-log" : - { "title" : "Assessment Log", - "description" : "A log of all assessment-related actions taken.", - "type" : "object", - "properties" : - { "entries" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Assessment Log Entry", - "description" : "Identifies the result of an action and/or task that occurred as part of executing an assessment plan or an assessment event that occurred in producing the assessment results.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Assessment Log Entry Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference an assessment event in this or other OSCAL instances. The locally defined UUID of the assessment log entry can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Action Title", - "description" : "The title for this event.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Action Description", - "description" : "A human-readable description of this event.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "start" : - { "title" : "Start", - "description" : "Identifies the start date and time of an event.", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "end" : - { "title" : "End", - "description" : "Identifies the end date and time of an event. If the event is a point in time, the start and end will be the same date and time.", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "logged-by" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:logged-by" } }, - "related-tasks" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:related-task" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "start" ], - "additionalProperties" : false } } }, - "required" : - [ "entries" ], - "additionalProperties" : false }, - "observations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:observation" } }, - "risks" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:risk" } }, - "findings" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:finding" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "title", - "description", - "start", - "reviewed-controls" ], - "additionalProperties" : false }, - "oscal-ar-oscal-ar:import-ap" : - { "title" : "Import Assessment Plan", - "description" : "Used by assessment-results to import information about the original plan for assessing the system.", - "$id" : "#/definitions/oscal-ar-oscal-ar:import-ap", - "type" : "object", - "properties" : - { "href" : - { "title" : "Assessment Plan Reference", - "description" : "A resolvable URL reference to the assessment plan governing the assessment activities.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "href" ], - "additionalProperties" : false }, - "oscal-ar-oscal-metadata:metadata" : - { "title" : "Document Metadata", - "description" : "Provides information about the containing document, and defines concepts that are shared across the document.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:metadata", - "type" : "object", - "properties" : - { "title" : - { "title" : "Document Title", - "description" : "A name given to the document, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "published" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:published" }, - "last-modified" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:last-modified" }, - "version" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:version" }, - "oscal-version" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:oscal-version" }, - "revisions" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Revision History Entry", - "description" : "An entry in a sequential list of revisions to the containing document, expected to be in reverse chronological order (i.e. latest first).", - "type" : "object", - "properties" : - { "title" : - { "title" : "Document Title", - "description" : "A name given to the document revision, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "published" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:published" }, - "last-modified" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:last-modified" }, - "version" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:version" }, - "oscal-version" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:oscal-version" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "version" ], - "additionalProperties" : false } }, - "document-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:document-id" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Role", - "description" : "Defines a function, which might be assigned to a party in a specific situation.", - "type" : "object", - "properties" : - { "id" : - { "title" : "Role Identifier", - "description" : "A unique identifier for the role.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Role Title", - "description" : "A name given to the role, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "short-name" : - { "title" : "Role Short Name", - "description" : "A short common name, abbreviation, or acronym for the role.", - "$ref" : "#/definitions/StringDatatype" }, - "description" : - { "title" : "Role Description", - "description" : "A summary of the role's purpose and associated responsibilities.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "id", - "title" ], - "additionalProperties" : false } }, - "locations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Location", - "description" : "A physical point of presence, which may be associated with people, organizations, or other concepts within the current or linked OSCAL document.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Location Universally Unique Identifier", - "description" : "A unique ID for the location, for reference.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Location Title", - "description" : "A name given to the location, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "address" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:address" }, - "email-addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:email-address" } }, - "telephone-numbers" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:telephone-number" } }, - "urls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Location URL", - "description" : "The uniform resource locator (URL) for a web site or other resource associated with the location.", - "$ref" : "#/definitions/URIDatatype" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "uuid" ], - "additionalProperties" : false } }, - "parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Party", - "description" : "An organization or person, which may be associated with roles or other concepts within the current or linked OSCAL document.", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "uuid" : - { "title" : "Party Universally Unique Identifier", - "description" : "A unique identifier for the party.", - "$ref" : "#/definitions/UUIDDatatype" }, - "type" : - { "title" : "Party Type", - "description" : "A category describing the kind of party the object describes.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "person", - "organization" ] } ] }, - "name" : - { "title" : "Party Name", - "description" : "The full name of the party. This is typically the legal name associated with the party.", - "$ref" : "#/definitions/StringDatatype" }, - "short-name" : - { "title" : "Party Short Name", - "description" : "A short common name, abbreviation, or acronym for the party.", - "$ref" : "#/definitions/StringDatatype" }, - "external-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Party External Identifier", - "description" : "An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).", - "type" : "object", - "properties" : - { "scheme" : - { "title" : "External Identifier Schema", - "description" : "Indicates the type of external identifier.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://orcid.org/" ] } ] }, - "id" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "id", - "scheme" ], - "additionalProperties" : false } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "email-addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:email-address" } }, - "telephone-numbers" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:telephone-number" } }, - "addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:address" } }, - "member-of-organizations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Organizational Affiliation", - "description" : "A reference to another party by UUID, typically an organization, that this subject is associated with.", - "$ref" : "#/definitions/UUIDDatatype" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - - { "properties" : - { "uuid" : - { "title" : "Party Universally Unique Identifier", - "description" : "A unique identifier for the party.", - "$ref" : "#/definitions/UUIDDatatype" }, - "type" : - { "title" : "Party Type", - "description" : "A category describing the kind of party the object describes.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "person", - "organization" ] } ] }, - "name" : - { "title" : "Party Name", - "description" : "The full name of the party. This is typically the legal name associated with the party.", - "$ref" : "#/definitions/StringDatatype" }, - "short-name" : - { "title" : "Party Short Name", - "description" : "A short common name, abbreviation, or acronym for the party.", - "$ref" : "#/definitions/StringDatatype" }, - "external-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Party External Identifier", - "description" : "An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).", - "type" : "object", - "properties" : - { "scheme" : - { "title" : "External Identifier Schema", - "description" : "Indicates the type of external identifier.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://orcid.org/" ] } ] }, - "id" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "id", - "scheme" ], - "additionalProperties" : false } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "email-addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:email-address" } }, - "telephone-numbers" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:telephone-number" } }, - "location-uuids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:location-uuid" } }, - "member-of-organizations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Organizational Affiliation", - "description" : "A reference to another party by UUID, typically an organization, that this subject is associated with.", - "$ref" : "#/definitions/UUIDDatatype" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "additionalProperties" : false } ] } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:responsible-party" } }, - "actions" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:action" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "title", - "last-modified", - "version", - "oscal-version" ], - "additionalProperties" : false }, - "oscal-ar-oscal-metadata:location-uuid" : - { "title" : "Location Universally Unique Identifier Reference", - "description" : "Reference to a location by UUID.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:location-uuid", - "$ref" : "#/definitions/UUIDDatatype" }, - "oscal-ar-oscal-metadata:party-uuid" : - { "title" : "Party Universally Unique Identifier Reference", - "description" : "Reference to a party by UUID.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:party-uuid", - "$ref" : "#/definitions/UUIDDatatype" }, - "oscal-ar-oscal-metadata:role-id" : - { "title" : "Role Identifier Reference", - "description" : "Reference to a role by UUID.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:role-id", - "$ref" : "#/definitions/TokenDatatype" }, - "oscal-ar-oscal-metadata:back-matter" : - { "title" : "Back matter", - "description" : "A collection of resources that may be referenced from within the OSCAL document instance.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:back-matter", - "type" : "object", - "properties" : - { "resources" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Resource", - "description" : "A resource associated with content in the containing document instance. A resource may be directly included in the document using base64 encoding or may point to one or more equivalent internet resources.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Resource Universally Unique Identifier", - "description" : "A unique identifier for a resource.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Resource Title", - "description" : "An optional name given to the resource, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Resource Description", - "description" : "An optional short summary of the resource used to indicate the purpose of the resource.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "document-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:document-id" } }, - "citation" : - { "title" : "Citation", - "description" : "An optional citation consisting of end note text using structured markup.", - "type" : "object", - "properties" : - { "text" : - { "title" : "Citation Text", - "description" : "A line of citation text.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } } }, - "required" : - [ "text" ], - "additionalProperties" : false }, - "rlinks" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Resource link", - "description" : "A URL-based pointer to an external resource with an optional hash for verification and change detection.", - "type" : "object", - "properties" : - { "href" : - { "title" : "Hypertext Reference", - "description" : "A resolvable URL pointing to the referenced resource.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "media-type" : - { "title" : "Media Type", - "description" : "A label that indicates the nature of a resource, as a data serialization or format.", - "$ref" : "#/definitions/StringDatatype" }, - "hashes" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:hash" } } }, - "required" : - [ "href" ], - "additionalProperties" : false } }, - "base64" : - { "title" : "Base64", - "description" : "A resource encoded using the Base64 alphabet defined by RFC 2045.", - "type" : "object", - "properties" : - { "filename" : - { "title" : "File Name", - "description" : "Name of the file before it was encoded as Base64 to be embedded in a resource. This is the name that will be assigned to the file when the file is decoded.", - "$ref" : "#/definitions/TokenDatatype" }, - "media-type" : - { "title" : "Media Type", - "description" : "A label that indicates the nature of a resource, as a data serialization or format.", - "$ref" : "#/definitions/StringDatatype" }, - "value" : - { "$ref" : "#/definitions/Base64Datatype" } }, - "required" : - [ "value" ], - "additionalProperties" : false }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "uuid" ], - "additionalProperties" : false } } }, - "additionalProperties" : false }, - "oscal-ar-oscal-metadata:property" : - { "title" : "Property", - "description" : "An attribute, characteristic, or quality of the containing object expressed as a namespace qualified name/value pair.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:property", - "type" : "object", - "properties" : - { "name" : - { "title" : "Property Name", - "description" : "A textual label, within a namespace, that identifies a specific attribute, characteristic, or quality of the property's containing object.", - "$ref" : "#/definitions/TokenDatatype" }, - "uuid" : - { "title" : "Property Universally Unique Identifier", - "description" : "A unique identifier for a property.", - "$ref" : "#/definitions/UUIDDatatype" }, - "ns" : - { "title" : "Property Namespace", - "description" : "A namespace qualifying the property's name. This allows different organizations to associate distinct semantics with the same name.", - "$ref" : "#/definitions/URIDatatype" }, - "value" : - { "title" : "Property Value", - "description" : "Indicates the value of the attribute, characteristic, or quality.", - "$ref" : "#/definitions/StringDatatype" }, - "class" : - { "title" : "Property Class", - "description" : "A textual label that provides a sub-type or characterization of the property's name.", - "$ref" : "#/definitions/TokenDatatype" }, - "group" : - { "title" : "Property Group", - "description" : "An identifier for relating distinct sets of properties.", - "$ref" : "#/definitions/TokenDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "name", - "value" ], - "additionalProperties" : false }, - "oscal-ar-oscal-metadata:link" : - { "title" : "Link", - "description" : "A reference to a local or remote resource, that has a specific relation to the containing object.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:link", - "type" : "object", - "properties" : - { "href" : - { "title" : "Hypertext Reference", - "description" : "A resolvable URL reference to a resource.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "rel" : - { "title" : "Link Relation Type", - "description" : "Describes the type of relationship provided by the link's hypertext reference. This can be an indicator of the link's purpose.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "reference" ] } ] }, - "media-type" : - { "title" : "Media Type", - "description" : "A label that indicates the nature of a resource, as a data serialization or format.", - "$ref" : "#/definitions/StringDatatype" }, - "resource-fragment" : - { "title" : "Resource Fragment", - "description" : "In case where the href points to a back-matter/resource, this value will indicate the URI fragment to append to any rlink associated with the resource. This value MUST be URI encoded.", - "$ref" : "#/definitions/StringDatatype" }, - "text" : - { "title" : "Link Text", - "description" : "A textual label to associate with the link, which may be used for presentation in a tool.", - "$ref" : "#/definitions/MarkupLineDatatype" } }, - "required" : - [ "href" ], - "additionalProperties" : false }, - "oscal-ar-oscal-metadata:responsible-party" : - { "title" : "Responsible Party", - "description" : "A reference to a set of persons and/or organizations that have responsibility for performing the referenced role in the context of the containing object.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:responsible-party", - "type" : "object", - "properties" : - { "role-id" : - { "title" : "Responsible Role", - "description" : "A reference to a role performed by a party.", - "$ref" : "#/definitions/TokenDatatype" }, - "party-uuids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:party-uuid" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "role-id", - "party-uuids" ], - "additionalProperties" : false }, - "oscal-ar-oscal-metadata:action" : - { "title" : "Action", - "description" : "An action applied by a role within a given party to the content.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:action", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Action Universally Unique Identifier", - "description" : "A unique identifier that can be used to reference this defined action elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "date" : - { "title" : "Action Occurrence Date", - "description" : "The date and time when the action occurred.", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "type" : - { "title" : "Action Type", - "description" : "The type of action documented by the assembly, such as an approval.", - "$ref" : "#/definitions/TokenDatatype" }, - "system" : - { "title" : "Action Type System", - "description" : "Specifies the action type system used.", - "$ref" : "#/definitions/URIDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:responsible-party" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "type", - "system" ], - "additionalProperties" : false }, - "oscal-ar-oscal-metadata:responsible-role" : - { "title" : "Responsible Role", - "description" : "A reference to a role with responsibility for performing a function relative to the containing object, optionally associated with a set of persons and/or organizations that perform that role.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:responsible-role", - "type" : "object", - "properties" : - { "role-id" : - { "title" : "Responsible Role ID", - "description" : "A human-oriented identifier reference to a role performed.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "party-uuids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:party-uuid" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "role-id" ], - "additionalProperties" : false }, - "oscal-ar-oscal-metadata:hash" : - { "title" : "Hash", - "description" : "A representation of a cryptographic digest generated over a resource using a specified hash algorithm.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:hash", - "type" : "object", - "properties" : - { "algorithm" : - { "title" : "Hash algorithm", - "description" : "The digest method by which a hash is derived.", - "anyOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "SHA-224", - "SHA-256", - "SHA-384", - "SHA-512", - "SHA3-224", - "SHA3-256", - "SHA3-384", - "SHA3-512" ] } ] }, - "value" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "value", - "algorithm" ], - "additionalProperties" : false }, - "oscal-ar-oscal-metadata:remarks" : - { "title" : "Remarks", - "description" : "Additional commentary about the containing object.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:remarks", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "oscal-ar-oscal-metadata:published" : - { "title" : "Publication Timestamp", - "description" : "The date and time the document was last made available.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:published", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "oscal-ar-oscal-metadata:last-modified" : - { "title" : "Last Modified Timestamp", - "description" : "The date and time the document was last stored for later retrieval.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:last-modified", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "oscal-ar-oscal-metadata:version" : - { "title" : "Document Version", - "description" : "Used to distinguish a specific revision of an OSCAL document from other previous and future versions.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:version", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-ar-oscal-metadata:oscal-version" : - { "title" : "OSCAL Version", - "description" : "The OSCAL model version the document was authored against and will conform to as valid.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:oscal-version", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-ar-oscal-metadata:email-address" : - { "title" : "Email Address", - "description" : "An email address as defined by RFC 5322 Section 3.4.1.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:email-address", - "$ref" : "#/definitions/EmailAddressDatatype" }, - "oscal-ar-oscal-metadata:telephone-number" : - { "title" : "Telephone Number", - "description" : "A telephone service number as defined by ITU-T E.164.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:telephone-number", - "type" : "object", - "properties" : - { "type" : - { "title" : "type flag", - "description" : "Indicates the type of phone number.", - "anyOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "home", - "office", - "mobile" ] } ] }, - "number" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "number" ], - "additionalProperties" : false }, - "oscal-ar-oscal-metadata:address" : - { "title" : "Address", - "description" : "A postal address for the location.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:address", - "type" : "object", - "properties" : - { "type" : - { "title" : "Address Type", - "description" : "Indicates the type of address.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "home", - "work" ] } ] }, - "addr-lines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:addr-line" } }, - "city" : - { "title" : "City", - "description" : "City, town or geographical region for the mailing address.", - "$ref" : "#/definitions/StringDatatype" }, - "state" : - { "title" : "State", - "description" : "State, province or analogous geographical region for a mailing address.", - "$ref" : "#/definitions/StringDatatype" }, - "postal-code" : - { "title" : "Postal Code", - "description" : "Postal or ZIP code for mailing address.", - "$ref" : "#/definitions/StringDatatype" }, - "country" : - { "title" : "Country Code", - "description" : "The ISO 3166-1 alpha-2 country code for the mailing address.", - "$ref" : "#/definitions/StringDatatype" } }, - "additionalProperties" : false }, - "oscal-ar-oscal-metadata:addr-line" : - { "title" : "Address line", - "description" : "A single line of an address.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:addr-line", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-ar-oscal-metadata:document-id" : - { "title" : "Document Identifier", - "description" : "A document identifier qualified by an identifier scheme.", - "$id" : "#/definitions/oscal-ar-oscal-metadata:document-id", - "type" : "object", - "properties" : - { "scheme" : - { "title" : "Document Identification Scheme", - "description" : "Qualifies the kind of document identifier using a URI. If the scheme is not provided the value of the element will be interpreted as a string of characters.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://www.doi.org/" ] } ] }, - "identifier" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "identifier" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:import-ssp" : - { "title" : "Import System Security Plan", - "description" : "Used by the assessment plan and POA&M to import information about the system.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:import-ssp", - "type" : "object", - "properties" : - { "href" : - { "title" : "System Security Plan Reference", - "description" : "A resolvable URL reference to the system security plan for the system being assessed.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "href" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:local-objective" : - { "title" : "Assessment-Specific Control Objective", - "description" : "A local definition of a control objective for this assessment. Uses catalog syntax for control objective and assessment actions.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:local-objective", - "type" : "object", - "properties" : - { "control-id" : - { "title" : "Control Identifier Reference", - "description" : "A reference to a control with a corresponding id value. When referencing an externally defined control, the Control Identifier Reference must be used in the context of the external / imported OSCAL instance (e.g., uri-reference).", - "$ref" : "#/definitions/TokenDatatype" }, - "description" : - { "title" : "Objective Description", - "description" : "A human-readable description of this control objective.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "parts" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-control-common:part" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "control-id", - "parts" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:assessment-method" : - { "title" : "Assessment Method", - "description" : "A local definition of a control objective. Uses catalog syntax for control objective and assessment activities.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:assessment-method", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Assessment Method Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "description" : - { "title" : "Assessment Method Description", - "description" : "A human-readable description of this assessment method.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "part" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:assessment-part" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "part" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:activity" : - { "title" : "Activity", - "description" : "Identifies an assessment or related process that can be performed. In the assessment plan, this is an intended activity which may be associated with an assessment task. In the assessment results, this an activity that was actually performed as part of an assessment.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:activity", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Assessment Activity Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Included Activity Title", - "description" : "The title for this included activity.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Included Activity Description", - "description" : "A human-readable description of this included activity.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "steps" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Step", - "description" : "Identifies an individual step in a series of steps related to an activity, such as an assessment test or examination procedure.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Step Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Step Title", - "description" : "The title for this step.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Step Description", - "description" : "A human-readable description of this step.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "reviewed-controls" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:reviewed-controls" }, - "responsible-roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:responsible-role" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "description" ], - "additionalProperties" : false } }, - "related-controls" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:reviewed-controls" }, - "responsible-roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:responsible-role" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "description" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:task" : - { "title" : "Task", - "description" : "Represents a scheduled event or milestone, which may be associated with a series of assessment actions.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:task", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Task Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "type" : - { "title" : "Task Type", - "description" : "The type of task.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "milestone", - "action" ] } ] }, - "title" : - { "title" : "Task Title", - "description" : "The title for this task.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Task Description", - "description" : "A human-readable description of this task.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "timing" : - { "title" : "Event Timing", - "description" : "The timing under which the task is intended to occur.", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "on-date" : - { "title" : "On Date Condition", - "description" : "The task is intended to occur on the specified date.", - "type" : "object", - "properties" : - { "date" : - { "title" : "On Date Condition", - "description" : "The task must occur on the specified date.", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "date" ], - "additionalProperties" : false } }, - "required" : - [ "on-date" ], - "additionalProperties" : false }, - - { "properties" : - { "within-date-range" : - { "title" : "On Date Range Condition", - "description" : "The task is intended to occur within the specified date range.", - "type" : "object", - "properties" : - { "start" : - { "title" : "Start Date Condition", - "description" : "The task must occur on or after the specified date.", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "end" : - { "title" : "End Date Condition", - "description" : "The task must occur on or before the specified date.", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "start", - "end" ], - "additionalProperties" : false } }, - "required" : - [ "within-date-range" ], - "additionalProperties" : false }, - - { "properties" : - { "at-frequency" : - { "title" : "Frequency Condition", - "description" : "The task is intended to occur at the specified frequency.", - "type" : "object", - "properties" : - { "period" : - { "title" : "Period", - "description" : "The task must occur after the specified period has elapsed.", - "$ref" : "#/definitions/PositiveIntegerDatatype" }, - "unit" : - { "title" : "Time Unit", - "description" : "The unit of time for the period.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "seconds", - "minutes", - "hours", - "days", - "months", - "years" ] } ] }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "period", - "unit" ], - "additionalProperties" : false } }, - "required" : - [ "at-frequency" ], - "additionalProperties" : false } ] }, - "dependencies" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Task Dependency", - "description" : "Used to indicate that a task is dependent on another task.", - "type" : "object", - "properties" : - { "task-uuid" : - { "title" : "Task Universally Unique Identifier Reference", - "description" : "A machine-oriented identifier reference to a unique task.", - "$ref" : "#/definitions/UUIDDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "task-uuid" ], - "additionalProperties" : false } }, - "tasks" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:task" } }, - "associated-activities" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Associated Activity", - "description" : "Identifies an individual activity to be performed as part of a task.", - "type" : "object", - "properties" : - { "activity-uuid" : - { "title" : "Activity Universally Unique Identifier Reference", - "description" : "A machine-oriented identifier reference to an activity defined in the list of activities.", - "$ref" : "#/definitions/UUIDDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "responsible-roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:responsible-role" } }, - "subjects" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:assessment-subject" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "activity-uuid", - "subjects" ], - "additionalProperties" : false } }, - "subjects" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:assessment-subject" } }, - "responsible-roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:responsible-role" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "type", - "title" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:reviewed-controls" : - { "title" : "Reviewed Controls and Control Objectives", - "description" : "Identifies the controls being assessed and their control objectives.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:reviewed-controls", - "type" : "object", - "properties" : - { "description" : - { "title" : "Control Objective Description", - "description" : "A human-readable description of control objectives.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "control-selections" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Assessed Controls", - "description" : "Identifies the controls being assessed. In the assessment plan, these are the planned controls. In the assessment results, these are the actual controls, and reflects any changes from the plan.", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "description" : - { "title" : "Assessed Controls Description", - "description" : "A human-readable description of in-scope controls specified for assessment.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "include-all" : - { "$ref" : "#/definitions/oscal-ar-oscal-control-common:include-all" }, - "exclude-controls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:select-control-by-id" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "include-all" ], - "additionalProperties" : false }, - - { "properties" : - { "description" : - { "title" : "Assessed Controls Description", - "description" : "A human-readable description of in-scope controls specified for assessment.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "include-controls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:select-control-by-id" } }, - "exclude-controls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:select-control-by-id" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "include-controls" ], - "additionalProperties" : false } ] } }, - "control-objective-selections" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Referenced Control Objectives", - "description" : "Identifies the control objectives of the assessment. In the assessment plan, these are the planned objectives. In the assessment results, these are the assessed objectives, and reflects any changes from the plan.", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "description" : - { "title" : "Control Objectives Description", - "description" : "A human-readable description of this collection of control objectives.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "include-all" : - { "$ref" : "#/definitions/oscal-ar-oscal-control-common:include-all" }, - "exclude-objectives" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:select-objective-by-id" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "include-all" ], - "additionalProperties" : false }, - - { "properties" : - { "description" : - { "title" : "Control Objectives Description", - "description" : "A human-readable description of this collection of control objectives.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "include-objectives" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:select-objective-by-id" } }, - "exclude-objectives" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:select-objective-by-id" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "include-objectives" ], - "additionalProperties" : false } ] } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "control-selections" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:select-control-by-id" : - { "title" : "Select Control", - "description" : "Used to select a control for inclusion/exclusion based on one or more control identifiers. A set of statement identifiers can be used to target the inclusion/exclusion to only specific control statements providing more granularity over the specific statements that are within the assessment scope.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:select-control-by-id", - "type" : "object", - "properties" : - { "control-id" : - { "title" : "Control Identifier Reference", - "description" : "A reference to a control with a corresponding id value. When referencing an externally defined control, the Control Identifier Reference must be used in the context of the external / imported OSCAL instance (e.g., uri-reference).", - "$ref" : "#/definitions/TokenDatatype" }, - "statement-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Include Specific Statements", - "description" : "Used to constrain the selection to only specificity identified statements.", - "$ref" : "#/definitions/TokenDatatype" } } }, - "required" : - [ "control-id" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:select-objective-by-id" : - { "title" : "Select Objective", - "description" : "Used to select a control objective for inclusion/exclusion based on the control objective's identifier.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:select-objective-by-id", - "type" : "object", - "properties" : - { "objective-id" : - { "title" : "Objective ID", - "description" : "Points to an assessment objective.", - "$ref" : "#/definitions/TokenDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "objective-id" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:assessment-subject-placeholder" : - { "title" : "Assessment Subject Placeholder", - "description" : "Used when the assessment subjects will be determined as part of one or more other assessment activities. These assessment subjects will be recorded in the assessment results in the assessment log.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:assessment-subject-placeholder", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Assessment Subject Placeholder Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "description" : - { "title" : "Assessment Subject Placeholder Description", - "description" : "A human-readable description of intent of this assessment subject placeholder.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "sources" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Assessment Subject Source", - "description" : "Assessment subjects will be identified while conducting the referenced activity-instance.", - "type" : "object", - "properties" : - { "task-uuid" : - { "title" : "Task Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "task-uuid" ], - "additionalProperties" : false } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "sources" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:assessment-subject" : - { "title" : "Subject of Assessment", - "description" : "Identifies system elements being assessed, such as components, inventory items, and locations. In the assessment plan, this identifies a planned assessment subject. In the assessment results this is an actual assessment subject, and reflects any changes from the plan. exactly what will be the focus of this assessment. Any subjects not identified in this way are out-of-scope.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:assessment-subject", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "type" : - { "title" : "Subject Type", - "description" : "Indicates the type of assessment subject, such as a component, inventory, item, location, or party represented by this selection statement.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "component", - "inventory-item", - "location", - "party", - "user" ] } ] }, - "description" : - { "title" : "Include Subjects Description", - "description" : "A human-readable description of the collection of subjects being included in this assessment.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "include-all" : - { "$ref" : "#/definitions/oscal-ar-oscal-control-common:include-all" }, - "exclude-subjects" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:select-subject-by-id" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "include-all" ], - "additionalProperties" : false }, - - { "properties" : - { "type" : - { "title" : "Subject Type", - "description" : "Indicates the type of assessment subject, such as a component, inventory, item, location, or party represented by this selection statement.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "component", - "inventory-item", - "location", - "party", - "user" ] } ] }, - "description" : - { "title" : "Include Subjects Description", - "description" : "A human-readable description of the collection of subjects being included in this assessment.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "include-subjects" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:select-subject-by-id" } }, - "exclude-subjects" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:select-subject-by-id" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "include-subjects" ], - "additionalProperties" : false } ] }, - "oscal-ar-oscal-assessment-common:select-subject-by-id" : - { "title" : "Select Assessment Subject", - "description" : "Identifies a set of assessment subjects to include/exclude by UUID.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:select-subject-by-id", - "type" : "object", - "properties" : - { "subject-uuid" : - { "title" : "Subject Universally Unique Identifier Reference", - "description" : "A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID.", - "$ref" : "#/definitions/UUIDDatatype" }, - "type" : - { "title" : "Subject Universally Unique Identifier Reference Type", - "description" : "Used to indicate the type of object pointed to by the uuid-ref within a subject.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "component", - "inventory-item", - "location", - "party", - "user", - "resource" ] } ] }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "subject-uuid", - "type" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:subject-reference" : - { "title" : "Identifies the Subject", - "description" : "A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:subject-reference", - "type" : "object", - "properties" : - { "subject-uuid" : - { "title" : "Subject Universally Unique Identifier Reference", - "description" : "A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID.", - "$ref" : "#/definitions/UUIDDatatype" }, - "type" : - { "title" : "Subject Universally Unique Identifier Reference Type", - "description" : "Used to indicate the type of object pointed to by the uuid-ref within a subject.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "component", - "inventory-item", - "location", - "party", - "user", - "resource" ] } ] }, - "title" : - { "title" : "Subject Reference Title", - "description" : "The title or name for the referenced subject.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "subject-uuid", - "type" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:assessment-assets" : - { "title" : "Assessment Assets", - "description" : "Identifies the assets used to perform this assessment, such as the assessment team, scanning tools, and assumptions.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:assessment-assets", - "type" : "object", - "properties" : - { "components" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-implementation-common:system-component" } }, - "assessment-platforms" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Assessment Platform", - "description" : "Used to represent the toolset used to perform aspects of the assessment.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Assessment Platform Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Assessment Platform Title", - "description" : "The title or name for the assessment platform.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "uses-components" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Uses Component", - "description" : "The set of components that are used by the assessment platform.", - "type" : "object", - "properties" : - { "component-uuid" : - { "title" : "Component Universally Unique Identifier Reference", - "description" : "A machine-oriented identifier reference to a component that is implemented as part of an inventory item.", - "$ref" : "#/definitions/UUIDDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:responsible-party" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "component-uuid" ], - "additionalProperties" : false } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "uuid" ], - "additionalProperties" : false } } }, - "required" : - [ "assessment-platforms" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:finding-target" : - { "title" : "Objective Status", - "description" : "Captures an assessor's conclusions regarding the degree to which an objective is satisfied.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:finding-target", - "type" : "object", - "properties" : - { "type" : - { "title" : "Finding Target Type", - "description" : "Identifies the type of the target.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "statement-id", - "objective-id" ] } ] }, - "target-id" : - { "title" : "Finding Target Identifier Reference", - "description" : "A machine-oriented identifier reference for a specific target qualified by the type.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Objective Status Title", - "description" : "The title for this objective status.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Objective Status Description", - "description" : "A human-readable description of the assessor's conclusions regarding the degree to which an objective is satisfied.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "status" : - { "title" : "Objective Status", - "description" : "A determination of if the objective is satisfied or not within a given system.", - "type" : "object", - "properties" : - { "state" : - { "title" : "Objective Status State", - "description" : "An indication as to whether the objective is satisfied or not.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "satisfied", - "not-satisfied" ] } ] }, - "reason" : - { "title" : "Objective Status Reason", - "description" : "The reason the objective was given it's status.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "pass", - "fail", - "other" ] } ] }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "state" ], - "additionalProperties" : false }, - "implementation-status" : - { "$ref" : "#/definitions/oscal-ar-oscal-implementation-common:implementation-status" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "type", - "target-id", - "status" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:finding" : - { "title" : "Finding", - "description" : "Describes an individual finding.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:finding", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Finding Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. The locally defined UUID of the finding can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Finding Title", - "description" : "The title for this finding.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Finding Description", - "description" : "A human-readable description of this finding.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "origins" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:origin" } }, - "target" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:finding-target" }, - "implementation-statement-uuid" : - { "title" : "Implementation Statement UUID", - "description" : "A machine-oriented identifier reference to the implementation statement in the SSP to which this finding is related.", - "$ref" : "#/definitions/UUIDDatatype" }, - "related-observations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:related-observation" } }, - "related-risks" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:associated-risk" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "title", - "description", - "target" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:related-observation" : - { "title" : "Related Observation", - "description" : "Relates the identified element to a set of referenced observations that were used to support its determination.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:related-observation", - "type" : "object", - "properties" : - { "observation-uuid" : - { "title" : "Observation Universally Unique Identifier Reference", - "description" : "A machine-oriented identifier reference to an observation defined in the list of observations.", - "$ref" : "#/definitions/UUIDDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "observation-uuid" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:associated-risk" : - { "title" : "Associated Risk", - "description" : "Relates the finding to a set of referenced risks that were used to determine the finding.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:associated-risk", - "type" : "object", - "properties" : - { "risk-uuid" : - { "title" : "Risk Universally Unique Identifier Reference", - "description" : "A machine-oriented identifier reference to a risk defined in the list of risks.", - "$ref" : "#/definitions/UUIDDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "risk-uuid" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:observation" : - { "title" : "Observation", - "description" : "Describes an individual observation.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:observation", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Observation Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Observation Title", - "description" : "The title for this observation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Observation Description", - "description" : "A human-readable description of this assessment observation.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "methods" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Observation Method", - "description" : "Identifies how the observation was made.", - "anyOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "EXAMINE", - "INTERVIEW", - "TEST", - "UNKNOWN" ] } ] } }, - "types" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Observation Type", - "description" : "Identifies the nature of the observation. More than one may be used to further qualify and enable filtering.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "ssp-statement-issue", - "control-objective", - "mitigation", - "finding", - "discovery", - "historic" ] } ] } }, - "origins" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:origin" } }, - "subjects" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:subject-reference" } }, - "relevant-evidence" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Relevant Evidence", - "description" : "Links this observation to relevant evidence.", - "type" : "object", - "properties" : - { "href" : - { "title" : "Relevant Evidence Reference", - "description" : "A resolvable URL reference to relevant evidence.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "description" : - { "title" : "Relevant Evidence Description", - "description" : "A human-readable description of this evidence.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "description" ], - "additionalProperties" : false } }, - "collected" : - { "title" : "Collected Field", - "description" : "Date/time stamp identifying when the finding information was collected.", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "expires" : - { "title" : "Expires Field", - "description" : "Date/time identifying when the finding information is out-of-date and no longer valid. Typically used with continuous assessment scenarios.", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "description", - "methods", - "collected" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:origin" : - { "title" : "Origin", - "description" : "Identifies the source of the finding, such as a tool, interviewed person, or activity.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:origin", - "type" : "object", - "properties" : - { "actors" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:origin-actor" } }, - "related-tasks" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:related-task" } } }, - "required" : - [ "actors" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:origin-actor" : - { "title" : "Originating Actor", - "description" : "The actor that produces an observation, a finding, or a risk. One or more actor type can be used to specify a person that is using a tool.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:origin-actor", - "type" : "object", - "properties" : - { "type" : - { "title" : "Actor Type", - "description" : "The kind of actor.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "tool", - "assessment-platform", - "party" ] } ] }, - "actor-uuid" : - { "title" : "Actor Universally Unique Identifier Reference", - "description" : "A machine-oriented identifier reference to the tool or person based on the associated type.", - "$ref" : "#/definitions/UUIDDatatype" }, - "role-id" : - { "title" : "Actor Role", - "description" : "For a party, this can optionally be used to specify the role the actor was performing.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } } }, - "required" : - [ "type", - "actor-uuid" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:related-task" : - { "title" : "Task Reference", - "description" : "Identifies an individual task for which the containing object is a consequence of.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:related-task", - "type" : "object", - "properties" : - { "task-uuid" : - { "title" : "Task Universally Unique Identifier Reference", - "description" : "A machine-oriented identifier reference to a unique task.", - "$ref" : "#/definitions/UUIDDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:responsible-party" } }, - "subjects" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:assessment-subject" } }, - "identified-subject" : - { "title" : "Identified Subject", - "description" : "Used to detail assessment subjects that were identified by this task.", - "type" : "object", - "properties" : - { "subject-placeholder-uuid" : - { "title" : "Assessment Subject Placeholder Universally Unique Identifier Reference", - "description" : "A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task.", - "$ref" : "#/definitions/UUIDDatatype" }, - "subjects" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:assessment-subject" } } }, - "required" : - [ "subject-placeholder-uuid", - "subjects" ], - "additionalProperties" : false }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "task-uuid" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:threat-id" : - { "title" : "Threat ID", - "description" : "A pointer, by ID, to an externally-defined threat.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:threat-id", - "type" : "object", - "properties" : - { "system" : - { "title" : "Threat Type Identification System", - "description" : "Specifies the source of the threat information.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://fedramp.gov", - "http://fedramp.gov/ns/oscal" ] } ] }, - "href" : - { "title" : "Threat Information Resource Reference", - "description" : "An optional location for the threat data, from which this ID originates.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "id" : - { "$ref" : "#/definitions/URIDatatype" } }, - "required" : - [ "id", - "system" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:risk" : - { "title" : "Identified Risk", - "description" : "An identified risk.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:risk", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Risk Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Risk Title", - "description" : "The title for this risk.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Risk Description", - "description" : "A human-readable summary of the identified risk, to include a statement of how the risk impacts the system.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "statement" : - { "title" : "Risk Statement", - "description" : "An summary of impact for how the risk affects the system.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "status" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:risk-status" }, - "origins" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:origin" } }, - "threat-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:threat-id" } }, - "characterizations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:characterization" } }, - "mitigating-factors" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Mitigating Factor", - "description" : "Describes an existing mitigating factor that may affect the overall determination of the risk, with an optional link to an implementation statement in the SSP.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Mitigating Factor Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "implementation-uuid" : - { "title" : "Implementation UUID", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instancess. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "description" : - { "title" : "Mitigating Factor Description", - "description" : "A human-readable description of this mitigating factor.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "subjects" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:subject-reference" } } }, - "required" : - [ "uuid", - "description" ], - "additionalProperties" : false } }, - "deadline" : - { "title" : "Risk Resolution Deadline", - "description" : "The date/time by which the risk must be resolved.", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "remediations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:response" } }, - "risk-log" : - { "title" : "Risk Log", - "description" : "A log of all risk-related tasks taken.", - "type" : "object", - "properties" : - { "entries" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Risk Log Entry", - "description" : "Identifies an individual risk response that occurred as part of managing an identified risk.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Risk Log Entry Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Title", - "description" : "The title for this risk log entry.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Risk Task Description", - "description" : "A human-readable description of what was done regarding the risk.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "start" : - { "title" : "Start", - "description" : "Identifies the start date and time of the event.", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "end" : - { "title" : "End", - "description" : "Identifies the end date and time of the event. If the event is a point in time, the start and end will be the same date and time.", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "logged-by" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:logged-by" } }, - "status-change" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:risk-status" }, - "related-responses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Risk Response Reference", - "description" : "Identifies an individual risk response that this log entry is for.", - "type" : "object", - "properties" : - { "response-uuid" : - { "title" : "Response Universally Unique Identifier Reference", - "description" : "A machine-oriented identifier reference to a unique risk response.", - "$ref" : "#/definitions/UUIDDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "related-tasks" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:related-task" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "response-uuid" ], - "additionalProperties" : false } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "start" ], - "additionalProperties" : false } } }, - "required" : - [ "entries" ], - "additionalProperties" : false }, - "related-observations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:related-observation" } } }, - "required" : - [ "uuid", - "title", - "description", - "statement", - "status" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:logged-by" : - { "title" : "Logged By", - "description" : "Used to indicate who created a log entry in what role.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:logged-by", - "type" : "object", - "properties" : - { "party-uuid" : - { "title" : "Party UUID Reference", - "description" : "A machine-oriented identifier reference to the party who is making the log entry.", - "$ref" : "#/definitions/UUIDDatatype" }, - "role-id" : - { "title" : "Actor Role", - "description" : "A point to the role-id of the role in which the party is making the log entry.", - "$ref" : "#/definitions/TokenDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "party-uuid" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:risk-status" : - { "title" : "Risk Status", - "description" : "Describes the status of the associated risk.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:risk-status", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "open", - "investigating", - "remediating", - "deviation-requested", - "deviation-approved", - "closed" ] } ] }, - "oscal-ar-oscal-assessment-common:characterization" : - { "title" : "Characterization", - "description" : "A collection of descriptive data about the containing object from a specific origin.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:characterization", - "type" : "object", - "properties" : - { "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "origin" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:origin" }, - "facets" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Facet", - "description" : "An individual characteristic that is part of a larger set produced by the same actor.", - "type" : "object", - "properties" : - { "name" : - { "title" : "Facet Name", - "description" : "The name of the risk metric within the specified system.", - "$ref" : "#/definitions/TokenDatatype" }, - "system" : - { "title" : "Naming System", - "description" : "Specifies the naming system under which this risk metric is organized, which allows for the same names to be used in different systems controlled by different parties. This avoids the potential of a name clash.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://fedramp.gov", - "http://fedramp.gov/ns/oscal", - "http://csrc.nist.gov/ns/oscal", - "http://csrc.nist.gov/ns/oscal/unknown", - "http://cve.mitre.org", - "http://www.first.org/cvss/v2.0", - "http://www.first.org/cvss/v3.0", - "http://www.first.org/cvss/v3.1", - "https://www.first.org/cvss/v4-0" ] } ] }, - "value" : - { "title" : "Facet Value", - "description" : "Indicates the value of the facet.", - "$ref" : "#/definitions/StringDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "name", - "system", - "value" ], - "additionalProperties" : false } } }, - "required" : - [ "origin", - "facets" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:response" : - { "title" : "Risk Response", - "description" : "Describes either recommended or an actual plan for addressing the risk.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:response", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Remediation Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "lifecycle" : - { "title" : "Remediation Intent", - "description" : "Identifies whether this is a recommendation, such as from an assessor or tool, or an actual plan accepted by the system owner.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "recommendation", - "planned", - "completed" ] } ] }, - "title" : - { "title" : "Response Title", - "description" : "The title for this response activity.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Response Description", - "description" : "A human-readable description of this response plan.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "origins" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:origin" } }, - "required-assets" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Required Asset", - "description" : "Identifies an asset required to achieve remediation.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Required Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "subjects" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:subject-reference" } }, - "title" : - { "title" : "Title for Required Asset", - "description" : "The title for this required asset.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Description of Required Asset", - "description" : "A human-readable description of this required asset.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "description" ], - "additionalProperties" : false } }, - "tasks" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:task" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "lifecycle", - "title", - "description" ], - "additionalProperties" : false }, - "oscal-ar-oscal-assessment-common:assessment-part" : - { "title" : "Assessment Part", - "description" : "A partition of an assessment plan or results or a child of another part.", - "$id" : "#/definitions/oscal-ar-oscal-assessment-common:assessment-part", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Part Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an ported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "name" : - { "title" : "Part Name", - "description" : "A textual label that uniquely identifies the part's semantic type.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "asset", - "method", - "objective" ] } ] }, - "ns" : - { "title" : "Part Namespace", - "description" : "A namespace qualifying the part's name. This allows different organizations to associate distinct semantics with the same name.", - "$ref" : "#/definitions/URIDatatype" }, - "class" : - { "title" : "Part Class", - "description" : "A textual label that provides a sub-type or characterization of the part's name. This can be used to further distinguish or discriminate between the semantics of multiple parts of the same control with the same name and ns.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Part Title", - "description" : "A name given to the part, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "prose" : - { "title" : "Part Text", - "description" : "Permits multiple paragraphs, lists, tables etc.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "parts" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-assessment-common:assessment-part" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } } }, - "required" : - [ "name" ], - "additionalProperties" : false }, - "oscal-ar-oscal-control-common:part" : - { "title" : "Part", - "description" : "An annotated, markup-based textual element of a control's or catalog group's definition, or a child of another part.", - "$id" : "#/definitions/oscal-ar-oscal-control-common:part", - "type" : "object", - "properties" : - { "id" : - { "title" : "Part Identifier", - "description" : "A unique identifier for the part.", - "$ref" : "#/definitions/TokenDatatype" }, - "name" : - { "title" : "Part Name", - "description" : "A textual label that uniquely identifies the part's semantic type, which exists in a value space qualified by the ns.", - "$ref" : "#/definitions/TokenDatatype" }, - "ns" : - { "title" : "Part Namespace", - "description" : "An optional namespace qualifying the part's name. This allows different organizations to associate distinct semantics with the same name.", - "$ref" : "#/definitions/URIDatatype" }, - "class" : - { "title" : "Part Class", - "description" : "An optional textual providing a sub-type or characterization of the part's name, or a category to which the part belongs.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Part Title", - "description" : "An optional name given to the part, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "prose" : - { "title" : "Part Text", - "description" : "Permits multiple paragraphs, lists, tables etc.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "parts" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-control-common:part" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } } }, - "required" : - [ "name" ], - "additionalProperties" : false }, - "oscal-ar-oscal-control-common:parameter" : - { "title" : "Parameter", - "description" : "Parameters provide a mechanism for the dynamic assignment of value(s) in a control.", - "$id" : "#/definitions/oscal-ar-oscal-control-common:parameter", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "id" : - { "title" : "Parameter Identifier", - "description" : "A unique identifier for the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "class" : - { "title" : "Parameter Class", - "description" : "A textual label that provides a characterization of the type, purpose, use or scope of the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "depends-on" : - { "title" : "Depends on", - "description" : "(deprecated) Another parameter invoking this one. This construct has been deprecated and should not be used.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "label" : - { "title" : "Parameter Label", - "description" : "A short, placeholder name for the parameter, which can be used as a substitute for a value if no value is assigned.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "usage" : - { "title" : "Parameter Usage Description", - "description" : "Describes the purpose and use of a parameter.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "constraints" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-control-common:parameter-constraint" } }, - "guidelines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-control-common:parameter-guideline" } }, - "values" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-control-common:parameter-value" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - - { "properties" : - { "id" : - { "title" : "Parameter Identifier", - "description" : "A unique identifier for the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "class" : - { "title" : "Parameter Class", - "description" : "A textual label that provides a characterization of the type, purpose, use or scope of the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "depends-on" : - { "title" : "Depends on", - "description" : "(deprecated) Another parameter invoking this one. This construct has been deprecated and should not be used.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "label" : - { "title" : "Parameter Label", - "description" : "A short, placeholder name for the parameter, which can be used as a substitute for a value if no value is assigned.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "usage" : - { "title" : "Parameter Usage Description", - "description" : "Describes the purpose and use of a parameter.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "constraints" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-control-common:parameter-constraint" } }, - "guidelines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-control-common:parameter-guideline" } }, - "select" : - { "$ref" : "#/definitions/oscal-ar-oscal-control-common:parameter-selection" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "additionalProperties" : false } ] }, - "oscal-ar-oscal-control-common:parameter-constraint" : - { "title" : "Constraint", - "description" : "A formal or informal expression of a constraint or test.", - "$id" : "#/definitions/oscal-ar-oscal-control-common:parameter-constraint", - "type" : "object", - "properties" : - { "description" : - { "title" : "Constraint Description", - "description" : "A textual summary of the constraint to be applied.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "tests" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Constraint Test", - "description" : "A test expression which is expected to be evaluated by a tool.", - "type" : "object", - "properties" : - { "expression" : - { "title" : "Constraint test", - "description" : "A formal (executable) expression of a constraint.", - "$ref" : "#/definitions/StringDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "expression" ], - "additionalProperties" : false } } }, - "additionalProperties" : false }, - "oscal-ar-oscal-control-common:parameter-guideline" : - { "title" : "Guideline", - "description" : "A prose statement that provides a recommendation for the use of a parameter.", - "$id" : "#/definitions/oscal-ar-oscal-control-common:parameter-guideline", - "type" : "object", - "properties" : - { "prose" : - { "title" : "Guideline Text", - "description" : "Prose permits multiple paragraphs, lists, tables etc.", - "$ref" : "#/definitions/MarkupMultilineDatatype" } }, - "required" : - [ "prose" ], - "additionalProperties" : false }, - "oscal-ar-oscal-control-common:parameter-value" : - { "title" : "Parameter Value", - "description" : "A parameter value or set of values.", - "$id" : "#/definitions/oscal-ar-oscal-control-common:parameter-value", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-ar-oscal-control-common:parameter-selection" : - { "title" : "Selection", - "description" : "Presenting a choice among alternatives.", - "$id" : "#/definitions/oscal-ar-oscal-control-common:parameter-selection", - "type" : "object", - "properties" : - { "how-many" : - { "title" : "Parameter Cardinality", - "description" : "Describes the number of selections that must occur. Without this setting, only one value should be assumed to be permitted.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "one", - "one-or-more" ] } ] }, - "choice" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Choice", - "description" : "A value selection among several such options.", - "$ref" : "#/definitions/MarkupLineDatatype" } } }, - "additionalProperties" : false }, - "oscal-ar-oscal-control-common:include-all" : - { "title" : "Include All", - "description" : "Include all controls from the imported catalog or profile resources.", - "$id" : "#/definitions/oscal-ar-oscal-control-common:include-all", - "type" : "object", - "additionalProperties" : false }, - "oscal-ar-oscal-control-common:with-id" : - { "title" : "Match Controls by Identifier", - "description" : "Selecting a control by its ID given as a literal.", - "$id" : "#/definitions/oscal-ar-oscal-control-common:with-id", - "$ref" : "#/definitions/TokenDatatype" }, - "oscal-ar-oscal-control-common:matching" : - { "title" : "Match Controls by Pattern", - "description" : "Selecting a set of controls by matching their IDs with a wildcard pattern.", - "$id" : "#/definitions/oscal-ar-oscal-control-common:matching", - "type" : "object", - "properties" : - { "pattern" : - { "title" : "Pattern", - "description" : "A glob expression matching the IDs of one or more controls to be selected.", - "$ref" : "#/definitions/StringDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - "oscal-ar-oscal-control-common:select-control-by-id" : - { "title" : "Select Control", - "description" : "Select a control or controls from an imported control set.", - "$id" : "#/definitions/oscal-ar-oscal-control-common:select-control-by-id", - "type" : "object", - "properties" : - { "with-child-controls" : - { "title" : "Include Contained Controls with Control", - "description" : "When a control is included, whether its child (dependent) controls are also included.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "yes", - "no" ] } ] }, - "with-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-control-common:with-id" } }, - "matching" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-control-common:matching" } } }, - "additionalProperties" : false }, - "oscal-ar-oscal-implementation-common:system-component" : - { "title" : "Component", - "description" : "A defined component that can be part of an implemented system.", - "$id" : "#/definitions/oscal-ar-oscal-implementation-common:system-component", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Component Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "type" : - { "title" : "Component Type", - "description" : "A category describing the purpose of the component.", - "anyOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "this-system", - "system", - "interconnection", - "software", - "hardware", - "service", - "policy", - "physical", - "process-procedure", - "plan", - "guidance", - "standard", - "validation", - "network" ] } ] }, - "title" : - { "title" : "Component Title", - "description" : "A human readable name for the system component.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Component Description", - "description" : "A description of the component, including information about its function.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "purpose" : - { "title" : "Purpose", - "description" : "A summary of the technological or business purpose of the component.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "status" : - { "title" : "Status", - "description" : "Describes the operational status of the system component.", - "type" : "object", - "properties" : - { "state" : - { "title" : "State", - "description" : "The operational status.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "under-development", - "operational", - "disposition", - "other" ] } ] }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "state" ], - "additionalProperties" : false }, - "responsible-roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:responsible-role" } }, - "protocols" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-implementation-common:protocol" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "type", - "title", - "description", - "status" ], - "additionalProperties" : false }, - "oscal-ar-oscal-implementation-common:protocol" : - { "title" : "Service Protocol Information", - "description" : "Information about the protocol used to provide a service.", - "$id" : "#/definitions/oscal-ar-oscal-implementation-common:protocol", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Service Protocol Information Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "name" : - { "title" : "Protocol Name", - "description" : "The common name of the protocol, which should be the appropriate \"service name\" from the IANA Service Name and Transport Protocol Port Number Registry.", - "$ref" : "#/definitions/StringDatatype" }, - "title" : - { "title" : "Protocol Title", - "description" : "A human readable name for the protocol (e.g., Transport Layer Security).", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "port-ranges" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-implementation-common:port-range" } } }, - "additionalProperties" : false }, - "oscal-ar-oscal-implementation-common:port-range" : - { "title" : "Port Range", - "description" : "Where applicable this is the transport layer protocol port range an IPv4-based or IPv6-based service uses.", - "$id" : "#/definitions/oscal-ar-oscal-implementation-common:port-range", - "type" : "object", - "properties" : - { "start" : - { "title" : "Start", - "description" : "Indicates the starting port number in a port range for a transport layer protocol", - "$ref" : "#/definitions/NonNegativeIntegerDatatype" }, - "end" : - { "title" : "End", - "description" : "Indicates the ending port number in a port range for a transport layer protocol", - "$ref" : "#/definitions/NonNegativeIntegerDatatype" }, - "transport" : - { "title" : "Transport", - "description" : "Indicates the transport type.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "TCP", - "UDP" ] } ] }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - "oscal-ar-oscal-implementation-common:implementation-status" : - { "title" : "Implementation Status", - "description" : "Indicates the degree to which the a given control is implemented.", - "$id" : "#/definitions/oscal-ar-oscal-implementation-common:implementation-status", - "type" : "object", - "properties" : - { "state" : - { "title" : "Implementation State", - "description" : "Identifies the implementation status of the control or control objective.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "implemented", - "partial", - "planned", - "alternative", - "not-applicable" ] } ] }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "state" ], - "additionalProperties" : false }, - "oscal-ar-oscal-implementation-common:system-user" : - { "title" : "System User", - "description" : "A type of user that interacts with the system based on an associated role.", - "$id" : "#/definitions/oscal-ar-oscal-implementation-common:system-user", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "User Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "User Title", - "description" : "A name given to the user, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "short-name" : - { "title" : "User Short Name", - "description" : "A short common name, abbreviation, or acronym for the user.", - "$ref" : "#/definitions/StringDatatype" }, - "description" : - { "title" : "User Description", - "description" : "A summary of the user's purpose within the system.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "role-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:role-id" } }, - "authorized-privileges" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-implementation-common:authorized-privilege" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "uuid" ], - "additionalProperties" : false }, - "oscal-ar-oscal-implementation-common:authorized-privilege" : - { "title" : "Privilege", - "description" : "Identifies a specific system privilege held by the user, along with an associated description and/or rationale for the privilege.", - "$id" : "#/definitions/oscal-ar-oscal-implementation-common:authorized-privilege", - "type" : "object", - "properties" : - { "title" : - { "title" : "Privilege Title", - "description" : "A human readable name for the privilege.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Privilege Description", - "description" : "A summary of the privilege's purpose within the system.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "functions-performed" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-implementation-common:function-performed" } } }, - "required" : - [ "title", - "functions-performed" ], - "additionalProperties" : false }, - "oscal-ar-oscal-implementation-common:function-performed" : - { "title" : "Functions Performed", - "description" : "Describes a function performed for a given authorized privilege by this user class.", - "$id" : "#/definitions/oscal-ar-oscal-implementation-common:function-performed", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-ar-oscal-implementation-common:inventory-item" : - { "title" : "Inventory Item", - "description" : "A single managed inventory item within the system.", - "$id" : "#/definitions/oscal-ar-oscal-implementation-common:inventory-item", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Inventory Item Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "description" : - { "title" : "Inventory Item Description", - "description" : "A summary of the inventory item stating its purpose within the system.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:responsible-party" } }, - "implemented-components" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Implemented Component", - "description" : "The set of components that are implemented in a given system inventory item.", - "type" : "object", - "properties" : - { "component-uuid" : - { "title" : "Component Universally Unique Identifier Reference", - "description" : "A machine-oriented identifier reference to a component that is implemented as part of an inventory item.", - "$ref" : "#/definitions/UUIDDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:link" } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:responsible-party" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "component-uuid" ], - "additionalProperties" : false } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "description" ], - "additionalProperties" : false }, - "oscal-ar-oscal-implementation-common:set-parameter" : - { "title" : "Set Parameter Value", - "description" : "Identifies the parameter that will be set by the enclosed value.", - "$id" : "#/definitions/oscal-ar-oscal-implementation-common:set-parameter", - "type" : "object", - "properties" : - { "param-id" : - { "title" : "Parameter ID", - "description" : "A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context.", - "$ref" : "#/definitions/TokenDatatype" }, - "values" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Parameter Value", - "description" : "A parameter value or set of values.", - "$ref" : "#/definitions/StringDatatype" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ar-oscal-metadata:remarks" } }, - "required" : - [ "param-id", - "values" ], - "additionalProperties" : false }, - "oscal-ar-oscal-implementation-common:system-id" : - { "title" : "System Identification", - "description" : "A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document.", - "$id" : "#/definitions/oscal-ar-oscal-implementation-common:system-id", - "type" : "object", - "properties" : - { "identifier-type" : - { "title" : "Identification System Type", - "description" : "Identifies the identification system from which the provided identifier was assigned.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://fedramp.gov", - "http://fedramp.gov/ns/oscal", - "https://ietf.org/rfc/rfc4122", - "http://ietf.org/rfc/rfc4122", - "http://datatracker.ietf.org/doc/html/rfc4122" ] } ] }, - "id" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "id" ], - "additionalProperties" : false }, - "Base64Datatype" : - { "description" : "Binary data encoded using the Base 64 encoding algorithm as defined by RFC4648.", - "type" : "string", - "pattern" : "^[0-9A-Za-z+/]+={0,2}$", - "contentEncoding" : "base64" }, - "DateTimeWithTimezoneDatatype" : - { "description" : "A string representing a point in time with a required timezone.", - "type" : "string", - "format" : "date-time", - "pattern" : "^(((2000|2400|2800|(19|2[0-9](0[48]|[2468][048]|[13579][26])))-02-29)|(((19|2[0-9])[0-9]{2})-02-(0[1-9]|1[0-9]|2[0-8]))|(((19|2[0-9])[0-9]{2})-(0[13578]|10|12)-(0[1-9]|[12][0-9]|3[01]))|(((19|2[0-9])[0-9]{2})-(0[469]|11)-(0[1-9]|[12][0-9]|30)))T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])(\\.[0-9]+)?(Z|(-((0[0-9]|1[0-2]):00|0[39]:30)|\\+((0[0-9]|1[0-4]):00|(0[34569]|10):30|(0[58]|12):45)))$" }, - "EmailAddressDatatype" : - { "description" : "An email address string formatted according to RFC 6531.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "type" : "string", - "format" : "email", - "pattern" : "^.+@.+$" } ] }, - "IntegerDatatype" : - { "description" : "A whole number value.", - "type" : "integer" }, - "MarkupLineDatatype" : - { "description" : "A single line of Markdown content conformant to the Commonmark specification.", - "type" : "string", - "pattern" : "^[^\n]+$" }, - "MarkupMultilineDatatype" : - { "description" : "A multiple lines of Markdown content conformant to the Commonmark specification.", - "type" : "string" }, - "NonNegativeIntegerDatatype" : - { "description" : "An integer value that is equal to or greater than 0.", - "allOf" : - [ - { "$ref" : "#/definitions/IntegerDatatype" }, - - { "type" : "number", - "minimum" : 0 } ] }, - "PositiveIntegerDatatype" : - { "description" : "An integer value that is greater than 0.", - "allOf" : - [ - { "$ref" : "#/definitions/IntegerDatatype" }, - - { "type" : "number", - "minimum" : 1 } ] }, - "StringDatatype" : - { "description" : "A non-empty string with leading and trailing whitespace disallowed. Whitespace is: U+9, U+10, U+32 or [ \n\t]+", - "type" : "string", - "pattern" : "^\\S(.*\\S)?$" }, - "TokenDatatype" : - { "description" : "A non-colonized name as defined by XML Schema Part 2: Datatypes Second Edition. https://www.w3.org/TR/xmlschema11-2/#NCName.", - "type" : "string", - "pattern" : "^(\\p{L}|_)(\\p{L}|\\p{N}|[.\\-_])*$" }, - "URIDatatype" : - { "description" : "A universal resource identifier (URI) formatted according to RFC3986.", - "type" : "string", - "format" : "uri", - "pattern" : "^[a-zA-Z][a-zA-Z0-9+\\-.]+:.+$" }, - "URIReferenceDatatype" : - { "description" : "A URI Reference, either a URI or a relative-reference, formatted according to section 4.1 of RFC3986.", - "type" : "string", - "format" : "uri-reference" }, - "UUIDDatatype" : - { "description" : "A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.", - "type" : "string", - "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-[45][0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" } }, - "properties" : - { "$schema" : - { "$ref" : "#/definitions/json-schema-directive" }, - "assessment-results" : - { "$ref" : "#/definitions/oscal-ar-oscal-ar:assessment-results" } }, - "required" : - [ "assessment-results" ], - "additionalProperties" : false } \ No newline at end of file diff --git a/data/schemas/oscal/oscal_catalog_schema.json b/data/schemas/oscal/oscal_catalog_schema.json deleted file mode 100644 index b86125d7..00000000 --- a/data/schemas/oscal/oscal_catalog_schema.json +++ /dev/null @@ -1,1295 +0,0 @@ - - { "$schema" : "http://json-schema.org/draft-07/schema#", - "$id" : "http://csrc.nist.gov/ns/oscal/1.2.2/oscal-catalog-schema.json", - "$comment" : "OSCAL Control Catalog Model: JSON Schema", - "type" : "object", - "definitions" : - { "json-schema-directive" : - { "title" : "Schema Directive", - "description" : "A JSON Schema directive to bind a specific schema to its document instance.", - "$id" : "#/definitions/json-schema-directive", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "oscal-catalog-oscal-catalog:catalog" : - { "title" : "Catalog", - "description" : "A structured, organized collection of control information.", - "$id" : "#/definitions/oscal-catalog-oscal-catalog:catalog", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Catalog Universally Unique Identifier", - "description" : "Provides a globally unique means to identify a given catalog instance.", - "$ref" : "#/definitions/UUIDDatatype" }, - "metadata" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:metadata" }, - "params" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-control-common:parameter" } }, - "controls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-catalog:control" } }, - "groups" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-catalog:group" } }, - "back-matter" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:back-matter" } }, - "required" : - [ "uuid", - "metadata" ], - "additionalProperties" : false }, - "oscal-catalog-oscal-catalog:group" : - { "title" : "Control Group", - "description" : "A group of controls, or of groups of controls.", - "$id" : "#/definitions/oscal-catalog-oscal-catalog:group", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "id" : - { "title" : "Group Identifier", - "description" : "Identifies the group for the purpose of cross-linking within the defining instance or from other instances that reference the catalog.", - "$ref" : "#/definitions/TokenDatatype" }, - "class" : - { "title" : "Group Class", - "description" : "A textual label that provides a sub-type or characterization of the group.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Group Title", - "description" : "A name given to the group, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "params" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-control-common:parameter" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:link" } }, - "parts" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-control-common:part" } }, - "groups" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-catalog:group" } } }, - "required" : - [ "title" ], - "additionalProperties" : false }, - - { "properties" : - { "id" : - { "title" : "Group Identifier", - "description" : "Identifies the group for the purpose of cross-linking within the defining instance or from other instances that reference the catalog.", - "$ref" : "#/definitions/TokenDatatype" }, - "class" : - { "title" : "Group Class", - "description" : "A textual label that provides a sub-type or characterization of the group.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Group Title", - "description" : "A name given to the group, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "params" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-control-common:parameter" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:link" } }, - "parts" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-control-common:part" } }, - "controls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-catalog:control" } } }, - "required" : - [ "title" ], - "additionalProperties" : false } ] }, - "oscal-catalog-oscal-catalog:control" : - { "title" : "Control", - "description" : "A structured object representing a requirement or guideline, which when implemented will reduce an aspect of risk related to an information system and its information.", - "$id" : "#/definitions/oscal-catalog-oscal-catalog:control", - "type" : "object", - "properties" : - { "id" : - { "title" : "Control Identifier", - "description" : "Identifies a control such that it can be referenced in the defining catalog and other OSCAL instances (e.g., profiles).", - "$ref" : "#/definitions/TokenDatatype" }, - "class" : - { "title" : "Control Class", - "description" : "A textual label that provides a sub-type or characterization of the control.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Control Title", - "description" : "A name given to the control, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "params" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-control-common:parameter" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:link" } }, - "parts" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-control-common:part" } }, - "controls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-catalog:control" } } }, - "required" : - [ "id", - "title" ], - "additionalProperties" : false }, - "oscal-catalog-oscal-control-common:part" : - { "title" : "Part", - "description" : "An annotated, markup-based textual element of a control's or catalog group's definition, or a child of another part.", - "$id" : "#/definitions/oscal-catalog-oscal-control-common:part", - "type" : "object", - "properties" : - { "id" : - { "title" : "Part Identifier", - "description" : "A unique identifier for the part.", - "$ref" : "#/definitions/TokenDatatype" }, - "name" : - { "title" : "Part Name", - "description" : "A textual label that uniquely identifies the part's semantic type, which exists in a value space qualified by the ns.", - "$ref" : "#/definitions/TokenDatatype" }, - "ns" : - { "title" : "Part Namespace", - "description" : "An optional namespace qualifying the part's name. This allows different organizations to associate distinct semantics with the same name.", - "$ref" : "#/definitions/URIDatatype" }, - "class" : - { "title" : "Part Class", - "description" : "An optional textual providing a sub-type or characterization of the part's name, or a category to which the part belongs.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Part Title", - "description" : "An optional name given to the part, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:property" } }, - "prose" : - { "title" : "Part Text", - "description" : "Permits multiple paragraphs, lists, tables etc.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "parts" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-control-common:part" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:link" } } }, - "required" : - [ "name" ], - "additionalProperties" : false }, - "oscal-catalog-oscal-control-common:parameter" : - { "title" : "Parameter", - "description" : "Parameters provide a mechanism for the dynamic assignment of value(s) in a control.", - "$id" : "#/definitions/oscal-catalog-oscal-control-common:parameter", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "id" : - { "title" : "Parameter Identifier", - "description" : "A unique identifier for the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "class" : - { "title" : "Parameter Class", - "description" : "A textual label that provides a characterization of the type, purpose, use or scope of the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "depends-on" : - { "title" : "Depends on", - "description" : "(deprecated) Another parameter invoking this one. This construct has been deprecated and should not be used.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:link" } }, - "label" : - { "title" : "Parameter Label", - "description" : "A short, placeholder name for the parameter, which can be used as a substitute for a value if no value is assigned.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "usage" : - { "title" : "Parameter Usage Description", - "description" : "Describes the purpose and use of a parameter.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "constraints" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-control-common:parameter-constraint" } }, - "guidelines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-control-common:parameter-guideline" } }, - "values" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-control-common:parameter-value" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - - { "properties" : - { "id" : - { "title" : "Parameter Identifier", - "description" : "A unique identifier for the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "class" : - { "title" : "Parameter Class", - "description" : "A textual label that provides a characterization of the type, purpose, use or scope of the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "depends-on" : - { "title" : "Depends on", - "description" : "(deprecated) Another parameter invoking this one. This construct has been deprecated and should not be used.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:link" } }, - "label" : - { "title" : "Parameter Label", - "description" : "A short, placeholder name for the parameter, which can be used as a substitute for a value if no value is assigned.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "usage" : - { "title" : "Parameter Usage Description", - "description" : "Describes the purpose and use of a parameter.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "constraints" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-control-common:parameter-constraint" } }, - "guidelines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-control-common:parameter-guideline" } }, - "select" : - { "$ref" : "#/definitions/oscal-catalog-oscal-control-common:parameter-selection" }, - "remarks" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:remarks" } }, - "additionalProperties" : false } ] }, - "oscal-catalog-oscal-control-common:parameter-constraint" : - { "title" : "Constraint", - "description" : "A formal or informal expression of a constraint or test.", - "$id" : "#/definitions/oscal-catalog-oscal-control-common:parameter-constraint", - "type" : "object", - "properties" : - { "description" : - { "title" : "Constraint Description", - "description" : "A textual summary of the constraint to be applied.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "tests" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Constraint Test", - "description" : "A test expression which is expected to be evaluated by a tool.", - "type" : "object", - "properties" : - { "expression" : - { "title" : "Constraint test", - "description" : "A formal (executable) expression of a constraint.", - "$ref" : "#/definitions/StringDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:remarks" } }, - "required" : - [ "expression" ], - "additionalProperties" : false } } }, - "additionalProperties" : false }, - "oscal-catalog-oscal-control-common:parameter-guideline" : - { "title" : "Guideline", - "description" : "A prose statement that provides a recommendation for the use of a parameter.", - "$id" : "#/definitions/oscal-catalog-oscal-control-common:parameter-guideline", - "type" : "object", - "properties" : - { "prose" : - { "title" : "Guideline Text", - "description" : "Prose permits multiple paragraphs, lists, tables etc.", - "$ref" : "#/definitions/MarkupMultilineDatatype" } }, - "required" : - [ "prose" ], - "additionalProperties" : false }, - "oscal-catalog-oscal-control-common:parameter-value" : - { "title" : "Parameter Value", - "description" : "A parameter value or set of values.", - "$id" : "#/definitions/oscal-catalog-oscal-control-common:parameter-value", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-catalog-oscal-control-common:parameter-selection" : - { "title" : "Selection", - "description" : "Presenting a choice among alternatives.", - "$id" : "#/definitions/oscal-catalog-oscal-control-common:parameter-selection", - "type" : "object", - "properties" : - { "how-many" : - { "title" : "Parameter Cardinality", - "description" : "Describes the number of selections that must occur. Without this setting, only one value should be assumed to be permitted.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "one", - "one-or-more" ] } ] }, - "choice" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Choice", - "description" : "A value selection among several such options.", - "$ref" : "#/definitions/MarkupLineDatatype" } } }, - "additionalProperties" : false }, - "oscal-catalog-oscal-control-common:include-all" : - { "title" : "Include All", - "description" : "Include all controls from the imported catalog or profile resources.", - "$id" : "#/definitions/oscal-catalog-oscal-control-common:include-all", - "type" : "object", - "additionalProperties" : false }, - "oscal-catalog-oscal-control-common:with-id" : - { "title" : "Match Controls by Identifier", - "description" : "Selecting a control by its ID given as a literal.", - "$id" : "#/definitions/oscal-catalog-oscal-control-common:with-id", - "$ref" : "#/definitions/TokenDatatype" }, - "oscal-catalog-oscal-control-common:matching" : - { "title" : "Match Controls by Pattern", - "description" : "Selecting a set of controls by matching their IDs with a wildcard pattern.", - "$id" : "#/definitions/oscal-catalog-oscal-control-common:matching", - "type" : "object", - "properties" : - { "pattern" : - { "title" : "Pattern", - "description" : "A glob expression matching the IDs of one or more controls to be selected.", - "$ref" : "#/definitions/StringDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - "oscal-catalog-oscal-control-common:select-control-by-id" : - { "title" : "Select Control", - "description" : "Select a control or controls from an imported control set.", - "$id" : "#/definitions/oscal-catalog-oscal-control-common:select-control-by-id", - "type" : "object", - "properties" : - { "with-child-controls" : - { "title" : "Include Contained Controls with Control", - "description" : "When a control is included, whether its child (dependent) controls are also included.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "yes", - "no" ] } ] }, - "with-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-control-common:with-id" } }, - "matching" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-control-common:matching" } } }, - "additionalProperties" : false }, - "oscal-catalog-oscal-metadata:metadata" : - { "title" : "Document Metadata", - "description" : "Provides information about the containing document, and defines concepts that are shared across the document.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:metadata", - "type" : "object", - "properties" : - { "title" : - { "title" : "Document Title", - "description" : "A name given to the document, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "published" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:published" }, - "last-modified" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:last-modified" }, - "version" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:version" }, - "oscal-version" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:oscal-version" }, - "revisions" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Revision History Entry", - "description" : "An entry in a sequential list of revisions to the containing document, expected to be in reverse chronological order (i.e. latest first).", - "type" : "object", - "properties" : - { "title" : - { "title" : "Document Title", - "description" : "A name given to the document revision, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "published" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:published" }, - "last-modified" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:last-modified" }, - "version" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:version" }, - "oscal-version" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:oscal-version" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:remarks" } }, - "required" : - [ "version" ], - "additionalProperties" : false } }, - "document-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:document-id" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:link" } }, - "roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Role", - "description" : "Defines a function, which might be assigned to a party in a specific situation.", - "type" : "object", - "properties" : - { "id" : - { "title" : "Role Identifier", - "description" : "A unique identifier for the role.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Role Title", - "description" : "A name given to the role, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "short-name" : - { "title" : "Role Short Name", - "description" : "A short common name, abbreviation, or acronym for the role.", - "$ref" : "#/definitions/StringDatatype" }, - "description" : - { "title" : "Role Description", - "description" : "A summary of the role's purpose and associated responsibilities.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:remarks" } }, - "required" : - [ "id", - "title" ], - "additionalProperties" : false } }, - "locations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Location", - "description" : "A physical point of presence, which may be associated with people, organizations, or other concepts within the current or linked OSCAL document.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Location Universally Unique Identifier", - "description" : "A unique ID for the location, for reference.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Location Title", - "description" : "A name given to the location, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "address" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:address" }, - "email-addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:email-address" } }, - "telephone-numbers" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:telephone-number" } }, - "urls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Location URL", - "description" : "The uniform resource locator (URL) for a web site or other resource associated with the location.", - "$ref" : "#/definitions/URIDatatype" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:remarks" } }, - "required" : - [ "uuid" ], - "additionalProperties" : false } }, - "parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Party", - "description" : "An organization or person, which may be associated with roles or other concepts within the current or linked OSCAL document.", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "uuid" : - { "title" : "Party Universally Unique Identifier", - "description" : "A unique identifier for the party.", - "$ref" : "#/definitions/UUIDDatatype" }, - "type" : - { "title" : "Party Type", - "description" : "A category describing the kind of party the object describes.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "person", - "organization" ] } ] }, - "name" : - { "title" : "Party Name", - "description" : "The full name of the party. This is typically the legal name associated with the party.", - "$ref" : "#/definitions/StringDatatype" }, - "short-name" : - { "title" : "Party Short Name", - "description" : "A short common name, abbreviation, or acronym for the party.", - "$ref" : "#/definitions/StringDatatype" }, - "external-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Party External Identifier", - "description" : "An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).", - "type" : "object", - "properties" : - { "scheme" : - { "title" : "External Identifier Schema", - "description" : "Indicates the type of external identifier.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://orcid.org/" ] } ] }, - "id" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "id", - "scheme" ], - "additionalProperties" : false } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:link" } }, - "email-addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:email-address" } }, - "telephone-numbers" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:telephone-number" } }, - "addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:address" } }, - "member-of-organizations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Organizational Affiliation", - "description" : "A reference to another party by UUID, typically an organization, that this subject is associated with.", - "$ref" : "#/definitions/UUIDDatatype" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - - { "properties" : - { "uuid" : - { "title" : "Party Universally Unique Identifier", - "description" : "A unique identifier for the party.", - "$ref" : "#/definitions/UUIDDatatype" }, - "type" : - { "title" : "Party Type", - "description" : "A category describing the kind of party the object describes.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "person", - "organization" ] } ] }, - "name" : - { "title" : "Party Name", - "description" : "The full name of the party. This is typically the legal name associated with the party.", - "$ref" : "#/definitions/StringDatatype" }, - "short-name" : - { "title" : "Party Short Name", - "description" : "A short common name, abbreviation, or acronym for the party.", - "$ref" : "#/definitions/StringDatatype" }, - "external-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Party External Identifier", - "description" : "An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).", - "type" : "object", - "properties" : - { "scheme" : - { "title" : "External Identifier Schema", - "description" : "Indicates the type of external identifier.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://orcid.org/" ] } ] }, - "id" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "id", - "scheme" ], - "additionalProperties" : false } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:link" } }, - "email-addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:email-address" } }, - "telephone-numbers" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:telephone-number" } }, - "location-uuids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:location-uuid" } }, - "member-of-organizations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Organizational Affiliation", - "description" : "A reference to another party by UUID, typically an organization, that this subject is associated with.", - "$ref" : "#/definitions/UUIDDatatype" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:remarks" } }, - "additionalProperties" : false } ] } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:responsible-party" } }, - "actions" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:action" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:remarks" } }, - "required" : - [ "title", - "last-modified", - "version", - "oscal-version" ], - "additionalProperties" : false }, - "oscal-catalog-oscal-metadata:location-uuid" : - { "title" : "Location Universally Unique Identifier Reference", - "description" : "Reference to a location by UUID.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:location-uuid", - "$ref" : "#/definitions/UUIDDatatype" }, - "oscal-catalog-oscal-metadata:party-uuid" : - { "title" : "Party Universally Unique Identifier Reference", - "description" : "Reference to a party by UUID.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:party-uuid", - "$ref" : "#/definitions/UUIDDatatype" }, - "oscal-catalog-oscal-metadata:role-id" : - { "title" : "Role Identifier Reference", - "description" : "Reference to a role by UUID.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:role-id", - "$ref" : "#/definitions/TokenDatatype" }, - "oscal-catalog-oscal-metadata:back-matter" : - { "title" : "Back matter", - "description" : "A collection of resources that may be referenced from within the OSCAL document instance.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:back-matter", - "type" : "object", - "properties" : - { "resources" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Resource", - "description" : "A resource associated with content in the containing document instance. A resource may be directly included in the document using base64 encoding or may point to one or more equivalent internet resources.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Resource Universally Unique Identifier", - "description" : "A unique identifier for a resource.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Resource Title", - "description" : "An optional name given to the resource, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Resource Description", - "description" : "An optional short summary of the resource used to indicate the purpose of the resource.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:property" } }, - "document-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:document-id" } }, - "citation" : - { "title" : "Citation", - "description" : "An optional citation consisting of end note text using structured markup.", - "type" : "object", - "properties" : - { "text" : - { "title" : "Citation Text", - "description" : "A line of citation text.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:link" } } }, - "required" : - [ "text" ], - "additionalProperties" : false }, - "rlinks" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Resource link", - "description" : "A URL-based pointer to an external resource with an optional hash for verification and change detection.", - "type" : "object", - "properties" : - { "href" : - { "title" : "Hypertext Reference", - "description" : "A resolvable URL pointing to the referenced resource.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "media-type" : - { "title" : "Media Type", - "description" : "A label that indicates the nature of a resource, as a data serialization or format.", - "$ref" : "#/definitions/StringDatatype" }, - "hashes" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:hash" } } }, - "required" : - [ "href" ], - "additionalProperties" : false } }, - "base64" : - { "title" : "Base64", - "description" : "A resource encoded using the Base64 alphabet defined by RFC 2045.", - "type" : "object", - "properties" : - { "filename" : - { "title" : "File Name", - "description" : "Name of the file before it was encoded as Base64 to be embedded in a resource. This is the name that will be assigned to the file when the file is decoded.", - "$ref" : "#/definitions/TokenDatatype" }, - "media-type" : - { "title" : "Media Type", - "description" : "A label that indicates the nature of a resource, as a data serialization or format.", - "$ref" : "#/definitions/StringDatatype" }, - "value" : - { "$ref" : "#/definitions/Base64Datatype" } }, - "required" : - [ "value" ], - "additionalProperties" : false }, - "remarks" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:remarks" } }, - "required" : - [ "uuid" ], - "additionalProperties" : false } } }, - "additionalProperties" : false }, - "oscal-catalog-oscal-metadata:property" : - { "title" : "Property", - "description" : "An attribute, characteristic, or quality of the containing object expressed as a namespace qualified name/value pair.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:property", - "type" : "object", - "properties" : - { "name" : - { "title" : "Property Name", - "description" : "A textual label, within a namespace, that identifies a specific attribute, characteristic, or quality of the property's containing object.", - "$ref" : "#/definitions/TokenDatatype" }, - "uuid" : - { "title" : "Property Universally Unique Identifier", - "description" : "A unique identifier for a property.", - "$ref" : "#/definitions/UUIDDatatype" }, - "ns" : - { "title" : "Property Namespace", - "description" : "A namespace qualifying the property's name. This allows different organizations to associate distinct semantics with the same name.", - "$ref" : "#/definitions/URIDatatype" }, - "value" : - { "title" : "Property Value", - "description" : "Indicates the value of the attribute, characteristic, or quality.", - "$ref" : "#/definitions/StringDatatype" }, - "class" : - { "title" : "Property Class", - "description" : "A textual label that provides a sub-type or characterization of the property's name.", - "$ref" : "#/definitions/TokenDatatype" }, - "group" : - { "title" : "Property Group", - "description" : "An identifier for relating distinct sets of properties.", - "$ref" : "#/definitions/TokenDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:remarks" } }, - "required" : - [ "name", - "value" ], - "additionalProperties" : false }, - "oscal-catalog-oscal-metadata:link" : - { "title" : "Link", - "description" : "A reference to a local or remote resource, that has a specific relation to the containing object.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:link", - "type" : "object", - "properties" : - { "href" : - { "title" : "Hypertext Reference", - "description" : "A resolvable URL reference to a resource.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "rel" : - { "title" : "Link Relation Type", - "description" : "Describes the type of relationship provided by the link's hypertext reference. This can be an indicator of the link's purpose.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "reference" ] } ] }, - "media-type" : - { "title" : "Media Type", - "description" : "A label that indicates the nature of a resource, as a data serialization or format.", - "$ref" : "#/definitions/StringDatatype" }, - "resource-fragment" : - { "title" : "Resource Fragment", - "description" : "In case where the href points to a back-matter/resource, this value will indicate the URI fragment to append to any rlink associated with the resource. This value MUST be URI encoded.", - "$ref" : "#/definitions/StringDatatype" }, - "text" : - { "title" : "Link Text", - "description" : "A textual label to associate with the link, which may be used for presentation in a tool.", - "$ref" : "#/definitions/MarkupLineDatatype" } }, - "required" : - [ "href" ], - "additionalProperties" : false }, - "oscal-catalog-oscal-metadata:responsible-party" : - { "title" : "Responsible Party", - "description" : "A reference to a set of persons and/or organizations that have responsibility for performing the referenced role in the context of the containing object.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:responsible-party", - "type" : "object", - "properties" : - { "role-id" : - { "title" : "Responsible Role", - "description" : "A reference to a role performed by a party.", - "$ref" : "#/definitions/TokenDatatype" }, - "party-uuids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:party-uuid" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:remarks" } }, - "required" : - [ "role-id", - "party-uuids" ], - "additionalProperties" : false }, - "oscal-catalog-oscal-metadata:action" : - { "title" : "Action", - "description" : "An action applied by a role within a given party to the content.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:action", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Action Universally Unique Identifier", - "description" : "A unique identifier that can be used to reference this defined action elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "date" : - { "title" : "Action Occurrence Date", - "description" : "The date and time when the action occurred.", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "type" : - { "title" : "Action Type", - "description" : "The type of action documented by the assembly, such as an approval.", - "$ref" : "#/definitions/TokenDatatype" }, - "system" : - { "title" : "Action Type System", - "description" : "Specifies the action type system used.", - "$ref" : "#/definitions/URIDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:link" } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:responsible-party" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "type", - "system" ], - "additionalProperties" : false }, - "oscal-catalog-oscal-metadata:responsible-role" : - { "title" : "Responsible Role", - "description" : "A reference to a role with responsibility for performing a function relative to the containing object, optionally associated with a set of persons and/or organizations that perform that role.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:responsible-role", - "type" : "object", - "properties" : - { "role-id" : - { "title" : "Responsible Role ID", - "description" : "A human-oriented identifier reference to a role performed.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:link" } }, - "party-uuids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:party-uuid" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:remarks" } }, - "required" : - [ "role-id" ], - "additionalProperties" : false }, - "oscal-catalog-oscal-metadata:hash" : - { "title" : "Hash", - "description" : "A representation of a cryptographic digest generated over a resource using a specified hash algorithm.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:hash", - "type" : "object", - "properties" : - { "algorithm" : - { "title" : "Hash algorithm", - "description" : "The digest method by which a hash is derived.", - "anyOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "SHA-224", - "SHA-256", - "SHA-384", - "SHA-512", - "SHA3-224", - "SHA3-256", - "SHA3-384", - "SHA3-512" ] } ] }, - "value" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "value", - "algorithm" ], - "additionalProperties" : false }, - "oscal-catalog-oscal-metadata:remarks" : - { "title" : "Remarks", - "description" : "Additional commentary about the containing object.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:remarks", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "oscal-catalog-oscal-metadata:published" : - { "title" : "Publication Timestamp", - "description" : "The date and time the document was last made available.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:published", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "oscal-catalog-oscal-metadata:last-modified" : - { "title" : "Last Modified Timestamp", - "description" : "The date and time the document was last stored for later retrieval.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:last-modified", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "oscal-catalog-oscal-metadata:version" : - { "title" : "Document Version", - "description" : "Used to distinguish a specific revision of an OSCAL document from other previous and future versions.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:version", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-catalog-oscal-metadata:oscal-version" : - { "title" : "OSCAL Version", - "description" : "The OSCAL model version the document was authored against and will conform to as valid.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:oscal-version", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-catalog-oscal-metadata:email-address" : - { "title" : "Email Address", - "description" : "An email address as defined by RFC 5322 Section 3.4.1.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:email-address", - "$ref" : "#/definitions/EmailAddressDatatype" }, - "oscal-catalog-oscal-metadata:telephone-number" : - { "title" : "Telephone Number", - "description" : "A telephone service number as defined by ITU-T E.164.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:telephone-number", - "type" : "object", - "properties" : - { "type" : - { "title" : "type flag", - "description" : "Indicates the type of phone number.", - "anyOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "home", - "office", - "mobile" ] } ] }, - "number" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "number" ], - "additionalProperties" : false }, - "oscal-catalog-oscal-metadata:address" : - { "title" : "Address", - "description" : "A postal address for the location.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:address", - "type" : "object", - "properties" : - { "type" : - { "title" : "Address Type", - "description" : "Indicates the type of address.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "home", - "work" ] } ] }, - "addr-lines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-catalog-oscal-metadata:addr-line" } }, - "city" : - { "title" : "City", - "description" : "City, town or geographical region for the mailing address.", - "$ref" : "#/definitions/StringDatatype" }, - "state" : - { "title" : "State", - "description" : "State, province or analogous geographical region for a mailing address.", - "$ref" : "#/definitions/StringDatatype" }, - "postal-code" : - { "title" : "Postal Code", - "description" : "Postal or ZIP code for mailing address.", - "$ref" : "#/definitions/StringDatatype" }, - "country" : - { "title" : "Country Code", - "description" : "The ISO 3166-1 alpha-2 country code for the mailing address.", - "$ref" : "#/definitions/StringDatatype" } }, - "additionalProperties" : false }, - "oscal-catalog-oscal-metadata:addr-line" : - { "title" : "Address line", - "description" : "A single line of an address.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:addr-line", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-catalog-oscal-metadata:document-id" : - { "title" : "Document Identifier", - "description" : "A document identifier qualified by an identifier scheme.", - "$id" : "#/definitions/oscal-catalog-oscal-metadata:document-id", - "type" : "object", - "properties" : - { "scheme" : - { "title" : "Document Identification Scheme", - "description" : "Qualifies the kind of document identifier using a URI. If the scheme is not provided the value of the element will be interpreted as a string of characters.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://www.doi.org/" ] } ] }, - "identifier" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "identifier" ], - "additionalProperties" : false }, - "Base64Datatype" : - { "description" : "Binary data encoded using the Base 64 encoding algorithm as defined by RFC4648.", - "type" : "string", - "pattern" : "^[0-9A-Za-z+/]+={0,2}$", - "contentEncoding" : "base64" }, - "DateTimeWithTimezoneDatatype" : - { "description" : "A string representing a point in time with a required timezone.", - "type" : "string", - "format" : "date-time", - "pattern" : "^(((2000|2400|2800|(19|2[0-9](0[48]|[2468][048]|[13579][26])))-02-29)|(((19|2[0-9])[0-9]{2})-02-(0[1-9]|1[0-9]|2[0-8]))|(((19|2[0-9])[0-9]{2})-(0[13578]|10|12)-(0[1-9]|[12][0-9]|3[01]))|(((19|2[0-9])[0-9]{2})-(0[469]|11)-(0[1-9]|[12][0-9]|30)))T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])(\\.[0-9]+)?(Z|(-((0[0-9]|1[0-2]):00|0[39]:30)|\\+((0[0-9]|1[0-4]):00|(0[34569]|10):30|(0[58]|12):45)))$" }, - "EmailAddressDatatype" : - { "description" : "An email address string formatted according to RFC 6531.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "type" : "string", - "format" : "email", - "pattern" : "^.+@.+$" } ] }, - "MarkupLineDatatype" : - { "description" : "A single line of Markdown content conformant to the Commonmark specification.", - "type" : "string", - "pattern" : "^[^\n]+$" }, - "MarkupMultilineDatatype" : - { "description" : "A multiple lines of Markdown content conformant to the Commonmark specification.", - "type" : "string" }, - "StringDatatype" : - { "description" : "A non-empty string with leading and trailing whitespace disallowed. Whitespace is: U+9, U+10, U+32 or [ \n\t]+", - "type" : "string", - "pattern" : "^\\S(.*\\S)?$" }, - "TokenDatatype" : - { "description" : "A non-colonized name as defined by XML Schema Part 2: Datatypes Second Edition. https://www.w3.org/TR/xmlschema11-2/#NCName.", - "type" : "string", - "pattern" : "^(\\p{L}|_)(\\p{L}|\\p{N}|[.\\-_])*$" }, - "URIDatatype" : - { "description" : "A universal resource identifier (URI) formatted according to RFC3986.", - "type" : "string", - "format" : "uri", - "pattern" : "^[a-zA-Z][a-zA-Z0-9+\\-.]+:.+$" }, - "URIReferenceDatatype" : - { "description" : "A URI Reference, either a URI or a relative-reference, formatted according to section 4.1 of RFC3986.", - "type" : "string", - "format" : "uri-reference" }, - "UUIDDatatype" : - { "description" : "A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.", - "type" : "string", - "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-[45][0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" } }, - "properties" : - { "$schema" : - { "$ref" : "#/definitions/json-schema-directive" }, - "catalog" : - { "$ref" : "#/definitions/oscal-catalog-oscal-catalog:catalog" } }, - "required" : - [ "catalog" ], - "additionalProperties" : false } \ No newline at end of file diff --git a/data/schemas/oscal/oscal_component_schema.json b/data/schemas/oscal/oscal_component_schema.json deleted file mode 100644 index d53912d1..00000000 --- a/data/schemas/oscal/oscal_component_schema.json +++ /dev/null @@ -1,1814 +0,0 @@ - - { "$schema" : "http://json-schema.org/draft-07/schema#", - "$id" : "http://csrc.nist.gov/ns/oscal/1.2.2/oscal-component-definition-schema.json", - "$comment" : "OSCAL Component Definition Model: JSON Schema", - "type" : "object", - "definitions" : - { "json-schema-directive" : - { "title" : "Schema Directive", - "description" : "A JSON Schema directive to bind a specific schema to its document instance.", - "$id" : "#/definitions/json-schema-directive", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "oscal-component-definition-oscal-component-definition:component-definition" : - { "title" : "Component Definition", - "description" : "A collection of component descriptions, which may optionally be grouped by capability.", - "$id" : "#/definitions/oscal-component-definition-oscal-component-definition:component-definition", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Component Definition Universally Unique Identifier", - "description" : "Provides a globally unique means to identify a given component definition instance.", - "$ref" : "#/definitions/UUIDDatatype" }, - "metadata" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:metadata" }, - "import-component-definitions" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-component-definition:import-component-definition" } }, - "components" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-component-definition:defined-component" } }, - "capabilities" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-component-definition:capability" } }, - "back-matter" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:back-matter" } }, - "required" : - [ "uuid", - "metadata" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-component-definition:import-component-definition" : - { "title" : "Import Component Definition", - "description" : "Loads a component definition from another resource.", - "$id" : "#/definitions/oscal-component-definition-oscal-component-definition:import-component-definition", - "type" : "object", - "properties" : - { "href" : - { "title" : "Hyperlink Reference", - "description" : "A link to a resource that defines a set of components and/or capabilities to import into this collection.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "href" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-component-definition:defined-component" : - { "title" : "Component", - "description" : "A defined component that can be part of an implemented system.", - "$id" : "#/definitions/oscal-component-definition-oscal-component-definition:defined-component", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Component Identifier", - "description" : "Provides a globally unique means to identify a given component.", - "$ref" : "#/definitions/UUIDDatatype" }, - "type" : - { "title" : "Component Type", - "description" : "A category describing the purpose of the component.", - "anyOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "interconnection", - "software", - "hardware", - "service", - "policy", - "physical", - "process-procedure", - "plan", - "guidance", - "standard", - "validation" ] } ] }, - "title" : - { "title" : "Component Title", - "description" : "A human readable name for the component.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Component Description", - "description" : "A description of the component, including information about its function.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "purpose" : - { "title" : "Purpose", - "description" : "A summary of the technological or business purpose of the component.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "responsible-roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:responsible-role" } }, - "protocols" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-implementation-common:protocol" } }, - "control-implementations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-component-definition:control-implementation" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "type", - "title", - "description" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-component-definition:capability" : - { "title" : "Capability", - "description" : "A grouping of other components and/or capabilities.", - "$id" : "#/definitions/oscal-component-definition-oscal-component-definition:capability", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Capability Identifier", - "description" : "Provides a globally unique means to identify a given capability.", - "$ref" : "#/definitions/UUIDDatatype" }, - "name" : - { "title" : "Capability Name", - "description" : "The capability's human-readable name.", - "$ref" : "#/definitions/StringDatatype" }, - "description" : - { "title" : "Capability Description", - "description" : "A summary of the capability.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "incorporates-components" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-component-definition:incorporates-component" } }, - "control-implementations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-component-definition:control-implementation" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "name", - "description" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-component-definition:incorporates-component" : - { "title" : "Incorporates Component", - "description" : "The collection of components comprising this capability.", - "$id" : "#/definitions/oscal-component-definition-oscal-component-definition:incorporates-component", - "type" : "object", - "properties" : - { "component-uuid" : - { "title" : "Component Reference", - "description" : "A machine-oriented identifier reference to a component.", - "$ref" : "#/definitions/UUIDDatatype" }, - "description" : - { "title" : "Component Description", - "description" : "A description of the component, including information about its function.", - "$ref" : "#/definitions/MarkupMultilineDatatype" } }, - "required" : - [ "component-uuid", - "description" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-component-definition:control-implementation" : - { "title" : "Control Implementation Set", - "description" : "Defines how the component or capability supports a set of controls.", - "$id" : "#/definitions/oscal-component-definition-oscal-component-definition:control-implementation", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Control Implementation Set Identifier", - "description" : "Provides a means to identify a set of control implementations that are supported by a given component or capability.", - "$ref" : "#/definitions/UUIDDatatype" }, - "source" : - { "title" : "Source Resource Reference", - "description" : "A reference to an OSCAL catalog or profile providing the referenced control or subcontrol definition.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "description" : - { "title" : "Control Implementation Description", - "description" : "A description of how the specified set of controls are implemented for the containing component or capability.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "set-parameters" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-implementation-common:set-parameter" } }, - "implemented-requirements" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-component-definition:implemented-requirement" } } }, - "required" : - [ "uuid", - "source", - "description", - "implemented-requirements" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-component-definition:implemented-requirement" : - { "title" : "Control Implementation", - "description" : "Describes how the containing component or capability implements an individual control.", - "$id" : "#/definitions/oscal-component-definition-oscal-component-definition:implemented-requirement", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Control Implementation Identifier", - "description" : "Provides a globally unique means to identify a given control implementation by a component.", - "$ref" : "#/definitions/UUIDDatatype" }, - "control-id" : - { "title" : "Control Identifier Reference", - "description" : "A reference to a control with a corresponding id value. When referencing an externally defined control, the Control Identifier Reference must be used in the context of the external / imported OSCAL instance (e.g., uri-reference).", - "$ref" : "#/definitions/TokenDatatype" }, - "description" : - { "title" : "Control Implementation Description", - "description" : "A suggestion from the supplier (e.g., component vendor or author) for how the specified control may be implemented if the containing component or capability is instantiated in a system security plan.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "set-parameters" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-implementation-common:set-parameter" } }, - "responsible-roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:responsible-role" } }, - "statements" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-component-definition:statement" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "control-id", - "description" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-component-definition:statement" : - { "title" : "Control Statement Implementation", - "description" : "Identifies which statements within a control are addressed.", - "$id" : "#/definitions/oscal-component-definition-oscal-component-definition:statement", - "type" : "object", - "properties" : - { "statement-id" : - { "title" : "Control Statement Reference", - "description" : "A human-oriented identifier reference to a control statement.", - "$ref" : "#/definitions/TokenDatatype" }, - "uuid" : - { "title" : "Control Statement Reference Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance).", - "$ref" : "#/definitions/UUIDDatatype" }, - "description" : - { "title" : "Statement Implementation Description", - "description" : "A summary of how the containing control statement is implemented by the component or capability.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "responsible-roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:responsible-role" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "statement-id", - "uuid", - "description" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-implementation-common:system-component" : - { "title" : "Component", - "description" : "A defined component that can be part of an implemented system.", - "$id" : "#/definitions/oscal-component-definition-oscal-implementation-common:system-component", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Component Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "type" : - { "title" : "Component Type", - "description" : "A category describing the purpose of the component.", - "anyOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "this-system", - "system", - "interconnection", - "software", - "hardware", - "service", - "policy", - "physical", - "process-procedure", - "plan", - "guidance", - "standard", - "validation", - "network" ] } ] }, - "title" : - { "title" : "Component Title", - "description" : "A human readable name for the system component.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Component Description", - "description" : "A description of the component, including information about its function.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "purpose" : - { "title" : "Purpose", - "description" : "A summary of the technological or business purpose of the component.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "status" : - { "title" : "Status", - "description" : "Describes the operational status of the system component.", - "type" : "object", - "properties" : - { "state" : - { "title" : "State", - "description" : "The operational status.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "under-development", - "operational", - "disposition", - "other" ] } ] }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "state" ], - "additionalProperties" : false }, - "responsible-roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:responsible-role" } }, - "protocols" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-implementation-common:protocol" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "type", - "title", - "description", - "status" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-implementation-common:protocol" : - { "title" : "Service Protocol Information", - "description" : "Information about the protocol used to provide a service.", - "$id" : "#/definitions/oscal-component-definition-oscal-implementation-common:protocol", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Service Protocol Information Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "name" : - { "title" : "Protocol Name", - "description" : "The common name of the protocol, which should be the appropriate \"service name\" from the IANA Service Name and Transport Protocol Port Number Registry.", - "$ref" : "#/definitions/StringDatatype" }, - "title" : - { "title" : "Protocol Title", - "description" : "A human readable name for the protocol (e.g., Transport Layer Security).", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "port-ranges" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-implementation-common:port-range" } } }, - "additionalProperties" : false }, - "oscal-component-definition-oscal-implementation-common:port-range" : - { "title" : "Port Range", - "description" : "Where applicable this is the transport layer protocol port range an IPv4-based or IPv6-based service uses.", - "$id" : "#/definitions/oscal-component-definition-oscal-implementation-common:port-range", - "type" : "object", - "properties" : - { "start" : - { "title" : "Start", - "description" : "Indicates the starting port number in a port range for a transport layer protocol", - "$ref" : "#/definitions/NonNegativeIntegerDatatype" }, - "end" : - { "title" : "End", - "description" : "Indicates the ending port number in a port range for a transport layer protocol", - "$ref" : "#/definitions/NonNegativeIntegerDatatype" }, - "transport" : - { "title" : "Transport", - "description" : "Indicates the transport type.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "TCP", - "UDP" ] } ] }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - "oscal-component-definition-oscal-implementation-common:implementation-status" : - { "title" : "Implementation Status", - "description" : "Indicates the degree to which the a given control is implemented.", - "$id" : "#/definitions/oscal-component-definition-oscal-implementation-common:implementation-status", - "type" : "object", - "properties" : - { "state" : - { "title" : "Implementation State", - "description" : "Identifies the implementation status of the control or control objective.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "implemented", - "partial", - "planned", - "alternative", - "not-applicable" ] } ] }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "state" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-implementation-common:system-user" : - { "title" : "System User", - "description" : "A type of user that interacts with the system based on an associated role.", - "$id" : "#/definitions/oscal-component-definition-oscal-implementation-common:system-user", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "User Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "User Title", - "description" : "A name given to the user, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "short-name" : - { "title" : "User Short Name", - "description" : "A short common name, abbreviation, or acronym for the user.", - "$ref" : "#/definitions/StringDatatype" }, - "description" : - { "title" : "User Description", - "description" : "A summary of the user's purpose within the system.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "role-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:role-id" } }, - "authorized-privileges" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-implementation-common:authorized-privilege" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "uuid" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-implementation-common:authorized-privilege" : - { "title" : "Privilege", - "description" : "Identifies a specific system privilege held by the user, along with an associated description and/or rationale for the privilege.", - "$id" : "#/definitions/oscal-component-definition-oscal-implementation-common:authorized-privilege", - "type" : "object", - "properties" : - { "title" : - { "title" : "Privilege Title", - "description" : "A human readable name for the privilege.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Privilege Description", - "description" : "A summary of the privilege's purpose within the system.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "functions-performed" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-implementation-common:function-performed" } } }, - "required" : - [ "title", - "functions-performed" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-implementation-common:function-performed" : - { "title" : "Functions Performed", - "description" : "Describes a function performed for a given authorized privilege by this user class.", - "$id" : "#/definitions/oscal-component-definition-oscal-implementation-common:function-performed", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-component-definition-oscal-implementation-common:inventory-item" : - { "title" : "Inventory Item", - "description" : "A single managed inventory item within the system.", - "$id" : "#/definitions/oscal-component-definition-oscal-implementation-common:inventory-item", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Inventory Item Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "description" : - { "title" : "Inventory Item Description", - "description" : "A summary of the inventory item stating its purpose within the system.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:responsible-party" } }, - "implemented-components" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Implemented Component", - "description" : "The set of components that are implemented in a given system inventory item.", - "type" : "object", - "properties" : - { "component-uuid" : - { "title" : "Component Universally Unique Identifier Reference", - "description" : "A machine-oriented identifier reference to a component that is implemented as part of an inventory item.", - "$ref" : "#/definitions/UUIDDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:responsible-party" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "component-uuid" ], - "additionalProperties" : false } }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "description" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-implementation-common:set-parameter" : - { "title" : "Set Parameter Value", - "description" : "Identifies the parameter that will be set by the enclosed value.", - "$id" : "#/definitions/oscal-component-definition-oscal-implementation-common:set-parameter", - "type" : "object", - "properties" : - { "param-id" : - { "title" : "Parameter ID", - "description" : "A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context.", - "$ref" : "#/definitions/TokenDatatype" }, - "values" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Parameter Value", - "description" : "A parameter value or set of values.", - "$ref" : "#/definitions/StringDatatype" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "param-id", - "values" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-implementation-common:system-id" : - { "title" : "System Identification", - "description" : "A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document.", - "$id" : "#/definitions/oscal-component-definition-oscal-implementation-common:system-id", - "type" : "object", - "properties" : - { "identifier-type" : - { "title" : "Identification System Type", - "description" : "Identifies the identification system from which the provided identifier was assigned.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://fedramp.gov", - "http://fedramp.gov/ns/oscal", - "https://ietf.org/rfc/rfc4122", - "http://ietf.org/rfc/rfc4122", - "http://datatracker.ietf.org/doc/html/rfc4122" ] } ] }, - "id" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "id" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-metadata:metadata" : - { "title" : "Document Metadata", - "description" : "Provides information about the containing document, and defines concepts that are shared across the document.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:metadata", - "type" : "object", - "properties" : - { "title" : - { "title" : "Document Title", - "description" : "A name given to the document, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "published" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:published" }, - "last-modified" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:last-modified" }, - "version" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:version" }, - "oscal-version" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:oscal-version" }, - "revisions" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Revision History Entry", - "description" : "An entry in a sequential list of revisions to the containing document, expected to be in reverse chronological order (i.e. latest first).", - "type" : "object", - "properties" : - { "title" : - { "title" : "Document Title", - "description" : "A name given to the document revision, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "published" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:published" }, - "last-modified" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:last-modified" }, - "version" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:version" }, - "oscal-version" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:oscal-version" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "version" ], - "additionalProperties" : false } }, - "document-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:document-id" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Role", - "description" : "Defines a function, which might be assigned to a party in a specific situation.", - "type" : "object", - "properties" : - { "id" : - { "title" : "Role Identifier", - "description" : "A unique identifier for the role.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Role Title", - "description" : "A name given to the role, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "short-name" : - { "title" : "Role Short Name", - "description" : "A short common name, abbreviation, or acronym for the role.", - "$ref" : "#/definitions/StringDatatype" }, - "description" : - { "title" : "Role Description", - "description" : "A summary of the role's purpose and associated responsibilities.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "id", - "title" ], - "additionalProperties" : false } }, - "locations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Location", - "description" : "A physical point of presence, which may be associated with people, organizations, or other concepts within the current or linked OSCAL document.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Location Universally Unique Identifier", - "description" : "A unique ID for the location, for reference.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Location Title", - "description" : "A name given to the location, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "address" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:address" }, - "email-addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:email-address" } }, - "telephone-numbers" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:telephone-number" } }, - "urls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Location URL", - "description" : "The uniform resource locator (URL) for a web site or other resource associated with the location.", - "$ref" : "#/definitions/URIDatatype" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "uuid" ], - "additionalProperties" : false } }, - "parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Party", - "description" : "An organization or person, which may be associated with roles or other concepts within the current or linked OSCAL document.", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "uuid" : - { "title" : "Party Universally Unique Identifier", - "description" : "A unique identifier for the party.", - "$ref" : "#/definitions/UUIDDatatype" }, - "type" : - { "title" : "Party Type", - "description" : "A category describing the kind of party the object describes.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "person", - "organization" ] } ] }, - "name" : - { "title" : "Party Name", - "description" : "The full name of the party. This is typically the legal name associated with the party.", - "$ref" : "#/definitions/StringDatatype" }, - "short-name" : - { "title" : "Party Short Name", - "description" : "A short common name, abbreviation, or acronym for the party.", - "$ref" : "#/definitions/StringDatatype" }, - "external-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Party External Identifier", - "description" : "An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).", - "type" : "object", - "properties" : - { "scheme" : - { "title" : "External Identifier Schema", - "description" : "Indicates the type of external identifier.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://orcid.org/" ] } ] }, - "id" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "id", - "scheme" ], - "additionalProperties" : false } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "email-addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:email-address" } }, - "telephone-numbers" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:telephone-number" } }, - "addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:address" } }, - "member-of-organizations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Organizational Affiliation", - "description" : "A reference to another party by UUID, typically an organization, that this subject is associated with.", - "$ref" : "#/definitions/UUIDDatatype" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - - { "properties" : - { "uuid" : - { "title" : "Party Universally Unique Identifier", - "description" : "A unique identifier for the party.", - "$ref" : "#/definitions/UUIDDatatype" }, - "type" : - { "title" : "Party Type", - "description" : "A category describing the kind of party the object describes.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "person", - "organization" ] } ] }, - "name" : - { "title" : "Party Name", - "description" : "The full name of the party. This is typically the legal name associated with the party.", - "$ref" : "#/definitions/StringDatatype" }, - "short-name" : - { "title" : "Party Short Name", - "description" : "A short common name, abbreviation, or acronym for the party.", - "$ref" : "#/definitions/StringDatatype" }, - "external-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Party External Identifier", - "description" : "An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).", - "type" : "object", - "properties" : - { "scheme" : - { "title" : "External Identifier Schema", - "description" : "Indicates the type of external identifier.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://orcid.org/" ] } ] }, - "id" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "id", - "scheme" ], - "additionalProperties" : false } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "email-addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:email-address" } }, - "telephone-numbers" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:telephone-number" } }, - "location-uuids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:location-uuid" } }, - "member-of-organizations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Organizational Affiliation", - "description" : "A reference to another party by UUID, typically an organization, that this subject is associated with.", - "$ref" : "#/definitions/UUIDDatatype" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "additionalProperties" : false } ] } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:responsible-party" } }, - "actions" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:action" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "title", - "last-modified", - "version", - "oscal-version" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-metadata:location-uuid" : - { "title" : "Location Universally Unique Identifier Reference", - "description" : "Reference to a location by UUID.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:location-uuid", - "$ref" : "#/definitions/UUIDDatatype" }, - "oscal-component-definition-oscal-metadata:party-uuid" : - { "title" : "Party Universally Unique Identifier Reference", - "description" : "Reference to a party by UUID.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:party-uuid", - "$ref" : "#/definitions/UUIDDatatype" }, - "oscal-component-definition-oscal-metadata:role-id" : - { "title" : "Role Identifier Reference", - "description" : "Reference to a role by UUID.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:role-id", - "$ref" : "#/definitions/TokenDatatype" }, - "oscal-component-definition-oscal-metadata:back-matter" : - { "title" : "Back matter", - "description" : "A collection of resources that may be referenced from within the OSCAL document instance.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:back-matter", - "type" : "object", - "properties" : - { "resources" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Resource", - "description" : "A resource associated with content in the containing document instance. A resource may be directly included in the document using base64 encoding or may point to one or more equivalent internet resources.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Resource Universally Unique Identifier", - "description" : "A unique identifier for a resource.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Resource Title", - "description" : "An optional name given to the resource, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Resource Description", - "description" : "An optional short summary of the resource used to indicate the purpose of the resource.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "document-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:document-id" } }, - "citation" : - { "title" : "Citation", - "description" : "An optional citation consisting of end note text using structured markup.", - "type" : "object", - "properties" : - { "text" : - { "title" : "Citation Text", - "description" : "A line of citation text.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } } }, - "required" : - [ "text" ], - "additionalProperties" : false }, - "rlinks" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Resource link", - "description" : "A URL-based pointer to an external resource with an optional hash for verification and change detection.", - "type" : "object", - "properties" : - { "href" : - { "title" : "Hypertext Reference", - "description" : "A resolvable URL pointing to the referenced resource.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "media-type" : - { "title" : "Media Type", - "description" : "A label that indicates the nature of a resource, as a data serialization or format.", - "$ref" : "#/definitions/StringDatatype" }, - "hashes" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:hash" } } }, - "required" : - [ "href" ], - "additionalProperties" : false } }, - "base64" : - { "title" : "Base64", - "description" : "A resource encoded using the Base64 alphabet defined by RFC 2045.", - "type" : "object", - "properties" : - { "filename" : - { "title" : "File Name", - "description" : "Name of the file before it was encoded as Base64 to be embedded in a resource. This is the name that will be assigned to the file when the file is decoded.", - "$ref" : "#/definitions/TokenDatatype" }, - "media-type" : - { "title" : "Media Type", - "description" : "A label that indicates the nature of a resource, as a data serialization or format.", - "$ref" : "#/definitions/StringDatatype" }, - "value" : - { "$ref" : "#/definitions/Base64Datatype" } }, - "required" : - [ "value" ], - "additionalProperties" : false }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "uuid" ], - "additionalProperties" : false } } }, - "additionalProperties" : false }, - "oscal-component-definition-oscal-metadata:property" : - { "title" : "Property", - "description" : "An attribute, characteristic, or quality of the containing object expressed as a namespace qualified name/value pair.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:property", - "type" : "object", - "properties" : - { "name" : - { "title" : "Property Name", - "description" : "A textual label, within a namespace, that identifies a specific attribute, characteristic, or quality of the property's containing object.", - "$ref" : "#/definitions/TokenDatatype" }, - "uuid" : - { "title" : "Property Universally Unique Identifier", - "description" : "A unique identifier for a property.", - "$ref" : "#/definitions/UUIDDatatype" }, - "ns" : - { "title" : "Property Namespace", - "description" : "A namespace qualifying the property's name. This allows different organizations to associate distinct semantics with the same name.", - "$ref" : "#/definitions/URIDatatype" }, - "value" : - { "title" : "Property Value", - "description" : "Indicates the value of the attribute, characteristic, or quality.", - "$ref" : "#/definitions/StringDatatype" }, - "class" : - { "title" : "Property Class", - "description" : "A textual label that provides a sub-type or characterization of the property's name.", - "$ref" : "#/definitions/TokenDatatype" }, - "group" : - { "title" : "Property Group", - "description" : "An identifier for relating distinct sets of properties.", - "$ref" : "#/definitions/TokenDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "name", - "value" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-metadata:link" : - { "title" : "Link", - "description" : "A reference to a local or remote resource, that has a specific relation to the containing object.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:link", - "type" : "object", - "properties" : - { "href" : - { "title" : "Hypertext Reference", - "description" : "A resolvable URL reference to a resource.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "rel" : - { "title" : "Link Relation Type", - "description" : "Describes the type of relationship provided by the link's hypertext reference. This can be an indicator of the link's purpose.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "reference" ] } ] }, - "media-type" : - { "title" : "Media Type", - "description" : "A label that indicates the nature of a resource, as a data serialization or format.", - "$ref" : "#/definitions/StringDatatype" }, - "resource-fragment" : - { "title" : "Resource Fragment", - "description" : "In case where the href points to a back-matter/resource, this value will indicate the URI fragment to append to any rlink associated with the resource. This value MUST be URI encoded.", - "$ref" : "#/definitions/StringDatatype" }, - "text" : - { "title" : "Link Text", - "description" : "A textual label to associate with the link, which may be used for presentation in a tool.", - "$ref" : "#/definitions/MarkupLineDatatype" } }, - "required" : - [ "href" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-metadata:responsible-party" : - { "title" : "Responsible Party", - "description" : "A reference to a set of persons and/or organizations that have responsibility for performing the referenced role in the context of the containing object.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:responsible-party", - "type" : "object", - "properties" : - { "role-id" : - { "title" : "Responsible Role", - "description" : "A reference to a role performed by a party.", - "$ref" : "#/definitions/TokenDatatype" }, - "party-uuids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:party-uuid" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "role-id", - "party-uuids" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-metadata:action" : - { "title" : "Action", - "description" : "An action applied by a role within a given party to the content.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:action", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Action Universally Unique Identifier", - "description" : "A unique identifier that can be used to reference this defined action elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "date" : - { "title" : "Action Occurrence Date", - "description" : "The date and time when the action occurred.", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "type" : - { "title" : "Action Type", - "description" : "The type of action documented by the assembly, such as an approval.", - "$ref" : "#/definitions/TokenDatatype" }, - "system" : - { "title" : "Action Type System", - "description" : "Specifies the action type system used.", - "$ref" : "#/definitions/URIDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:responsible-party" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "type", - "system" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-metadata:responsible-role" : - { "title" : "Responsible Role", - "description" : "A reference to a role with responsibility for performing a function relative to the containing object, optionally associated with a set of persons and/or organizations that perform that role.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:responsible-role", - "type" : "object", - "properties" : - { "role-id" : - { "title" : "Responsible Role ID", - "description" : "A human-oriented identifier reference to a role performed.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "party-uuids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:party-uuid" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "role-id" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-metadata:hash" : - { "title" : "Hash", - "description" : "A representation of a cryptographic digest generated over a resource using a specified hash algorithm.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:hash", - "type" : "object", - "properties" : - { "algorithm" : - { "title" : "Hash algorithm", - "description" : "The digest method by which a hash is derived.", - "anyOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "SHA-224", - "SHA-256", - "SHA-384", - "SHA-512", - "SHA3-224", - "SHA3-256", - "SHA3-384", - "SHA3-512" ] } ] }, - "value" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "value", - "algorithm" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-metadata:remarks" : - { "title" : "Remarks", - "description" : "Additional commentary about the containing object.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:remarks", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "oscal-component-definition-oscal-metadata:published" : - { "title" : "Publication Timestamp", - "description" : "The date and time the document was last made available.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:published", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "oscal-component-definition-oscal-metadata:last-modified" : - { "title" : "Last Modified Timestamp", - "description" : "The date and time the document was last stored for later retrieval.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:last-modified", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "oscal-component-definition-oscal-metadata:version" : - { "title" : "Document Version", - "description" : "Used to distinguish a specific revision of an OSCAL document from other previous and future versions.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:version", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-component-definition-oscal-metadata:oscal-version" : - { "title" : "OSCAL Version", - "description" : "The OSCAL model version the document was authored against and will conform to as valid.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:oscal-version", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-component-definition-oscal-metadata:email-address" : - { "title" : "Email Address", - "description" : "An email address as defined by RFC 5322 Section 3.4.1.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:email-address", - "$ref" : "#/definitions/EmailAddressDatatype" }, - "oscal-component-definition-oscal-metadata:telephone-number" : - { "title" : "Telephone Number", - "description" : "A telephone service number as defined by ITU-T E.164.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:telephone-number", - "type" : "object", - "properties" : - { "type" : - { "title" : "type flag", - "description" : "Indicates the type of phone number.", - "anyOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "home", - "office", - "mobile" ] } ] }, - "number" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "number" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-metadata:address" : - { "title" : "Address", - "description" : "A postal address for the location.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:address", - "type" : "object", - "properties" : - { "type" : - { "title" : "Address Type", - "description" : "Indicates the type of address.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "home", - "work" ] } ] }, - "addr-lines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:addr-line" } }, - "city" : - { "title" : "City", - "description" : "City, town or geographical region for the mailing address.", - "$ref" : "#/definitions/StringDatatype" }, - "state" : - { "title" : "State", - "description" : "State, province or analogous geographical region for a mailing address.", - "$ref" : "#/definitions/StringDatatype" }, - "postal-code" : - { "title" : "Postal Code", - "description" : "Postal or ZIP code for mailing address.", - "$ref" : "#/definitions/StringDatatype" }, - "country" : - { "title" : "Country Code", - "description" : "The ISO 3166-1 alpha-2 country code for the mailing address.", - "$ref" : "#/definitions/StringDatatype" } }, - "additionalProperties" : false }, - "oscal-component-definition-oscal-metadata:addr-line" : - { "title" : "Address line", - "description" : "A single line of an address.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:addr-line", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-component-definition-oscal-metadata:document-id" : - { "title" : "Document Identifier", - "description" : "A document identifier qualified by an identifier scheme.", - "$id" : "#/definitions/oscal-component-definition-oscal-metadata:document-id", - "type" : "object", - "properties" : - { "scheme" : - { "title" : "Document Identification Scheme", - "description" : "Qualifies the kind of document identifier using a URI. If the scheme is not provided the value of the element will be interpreted as a string of characters.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://www.doi.org/" ] } ] }, - "identifier" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "identifier" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-control-common:part" : - { "title" : "Part", - "description" : "An annotated, markup-based textual element of a control's or catalog group's definition, or a child of another part.", - "$id" : "#/definitions/oscal-component-definition-oscal-control-common:part", - "type" : "object", - "properties" : - { "id" : - { "title" : "Part Identifier", - "description" : "A unique identifier for the part.", - "$ref" : "#/definitions/TokenDatatype" }, - "name" : - { "title" : "Part Name", - "description" : "A textual label that uniquely identifies the part's semantic type, which exists in a value space qualified by the ns.", - "$ref" : "#/definitions/TokenDatatype" }, - "ns" : - { "title" : "Part Namespace", - "description" : "An optional namespace qualifying the part's name. This allows different organizations to associate distinct semantics with the same name.", - "$ref" : "#/definitions/URIDatatype" }, - "class" : - { "title" : "Part Class", - "description" : "An optional textual providing a sub-type or characterization of the part's name, or a category to which the part belongs.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Part Title", - "description" : "An optional name given to the part, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "prose" : - { "title" : "Part Text", - "description" : "Permits multiple paragraphs, lists, tables etc.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "parts" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-control-common:part" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } } }, - "required" : - [ "name" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-control-common:parameter" : - { "title" : "Parameter", - "description" : "Parameters provide a mechanism for the dynamic assignment of value(s) in a control.", - "$id" : "#/definitions/oscal-component-definition-oscal-control-common:parameter", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "id" : - { "title" : "Parameter Identifier", - "description" : "A unique identifier for the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "class" : - { "title" : "Parameter Class", - "description" : "A textual label that provides a characterization of the type, purpose, use or scope of the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "depends-on" : - { "title" : "Depends on", - "description" : "(deprecated) Another parameter invoking this one. This construct has been deprecated and should not be used.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "label" : - { "title" : "Parameter Label", - "description" : "A short, placeholder name for the parameter, which can be used as a substitute for a value if no value is assigned.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "usage" : - { "title" : "Parameter Usage Description", - "description" : "Describes the purpose and use of a parameter.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "constraints" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-control-common:parameter-constraint" } }, - "guidelines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-control-common:parameter-guideline" } }, - "values" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-control-common:parameter-value" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - - { "properties" : - { "id" : - { "title" : "Parameter Identifier", - "description" : "A unique identifier for the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "class" : - { "title" : "Parameter Class", - "description" : "A textual label that provides a characterization of the type, purpose, use or scope of the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "depends-on" : - { "title" : "Depends on", - "description" : "(deprecated) Another parameter invoking this one. This construct has been deprecated and should not be used.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:link" } }, - "label" : - { "title" : "Parameter Label", - "description" : "A short, placeholder name for the parameter, which can be used as a substitute for a value if no value is assigned.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "usage" : - { "title" : "Parameter Usage Description", - "description" : "Describes the purpose and use of a parameter.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "constraints" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-control-common:parameter-constraint" } }, - "guidelines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-control-common:parameter-guideline" } }, - "select" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-control-common:parameter-selection" }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "additionalProperties" : false } ] }, - "oscal-component-definition-oscal-control-common:parameter-constraint" : - { "title" : "Constraint", - "description" : "A formal or informal expression of a constraint or test.", - "$id" : "#/definitions/oscal-component-definition-oscal-control-common:parameter-constraint", - "type" : "object", - "properties" : - { "description" : - { "title" : "Constraint Description", - "description" : "A textual summary of the constraint to be applied.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "tests" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Constraint Test", - "description" : "A test expression which is expected to be evaluated by a tool.", - "type" : "object", - "properties" : - { "expression" : - { "title" : "Constraint test", - "description" : "A formal (executable) expression of a constraint.", - "$ref" : "#/definitions/StringDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "required" : - [ "expression" ], - "additionalProperties" : false } } }, - "additionalProperties" : false }, - "oscal-component-definition-oscal-control-common:parameter-guideline" : - { "title" : "Guideline", - "description" : "A prose statement that provides a recommendation for the use of a parameter.", - "$id" : "#/definitions/oscal-component-definition-oscal-control-common:parameter-guideline", - "type" : "object", - "properties" : - { "prose" : - { "title" : "Guideline Text", - "description" : "Prose permits multiple paragraphs, lists, tables etc.", - "$ref" : "#/definitions/MarkupMultilineDatatype" } }, - "required" : - [ "prose" ], - "additionalProperties" : false }, - "oscal-component-definition-oscal-control-common:parameter-value" : - { "title" : "Parameter Value", - "description" : "A parameter value or set of values.", - "$id" : "#/definitions/oscal-component-definition-oscal-control-common:parameter-value", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-component-definition-oscal-control-common:parameter-selection" : - { "title" : "Selection", - "description" : "Presenting a choice among alternatives.", - "$id" : "#/definitions/oscal-component-definition-oscal-control-common:parameter-selection", - "type" : "object", - "properties" : - { "how-many" : - { "title" : "Parameter Cardinality", - "description" : "Describes the number of selections that must occur. Without this setting, only one value should be assumed to be permitted.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "one", - "one-or-more" ] } ] }, - "choice" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Choice", - "description" : "A value selection among several such options.", - "$ref" : "#/definitions/MarkupLineDatatype" } } }, - "additionalProperties" : false }, - "oscal-component-definition-oscal-control-common:include-all" : - { "title" : "Include All", - "description" : "Include all controls from the imported catalog or profile resources.", - "$id" : "#/definitions/oscal-component-definition-oscal-control-common:include-all", - "type" : "object", - "additionalProperties" : false }, - "oscal-component-definition-oscal-control-common:with-id" : - { "title" : "Match Controls by Identifier", - "description" : "Selecting a control by its ID given as a literal.", - "$id" : "#/definitions/oscal-component-definition-oscal-control-common:with-id", - "$ref" : "#/definitions/TokenDatatype" }, - "oscal-component-definition-oscal-control-common:matching" : - { "title" : "Match Controls by Pattern", - "description" : "Selecting a set of controls by matching their IDs with a wildcard pattern.", - "$id" : "#/definitions/oscal-component-definition-oscal-control-common:matching", - "type" : "object", - "properties" : - { "pattern" : - { "title" : "Pattern", - "description" : "A glob expression matching the IDs of one or more controls to be selected.", - "$ref" : "#/definitions/StringDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - "oscal-component-definition-oscal-control-common:select-control-by-id" : - { "title" : "Select Control", - "description" : "Select a control or controls from an imported control set.", - "$id" : "#/definitions/oscal-component-definition-oscal-control-common:select-control-by-id", - "type" : "object", - "properties" : - { "with-child-controls" : - { "title" : "Include Contained Controls with Control", - "description" : "When a control is included, whether its child (dependent) controls are also included.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "yes", - "no" ] } ] }, - "with-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-control-common:with-id" } }, - "matching" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-control-common:matching" } } }, - "additionalProperties" : false }, - "Base64Datatype" : - { "description" : "Binary data encoded using the Base 64 encoding algorithm as defined by RFC4648.", - "type" : "string", - "pattern" : "^[0-9A-Za-z+/]+={0,2}$", - "contentEncoding" : "base64" }, - "DateTimeWithTimezoneDatatype" : - { "description" : "A string representing a point in time with a required timezone.", - "type" : "string", - "format" : "date-time", - "pattern" : "^(((2000|2400|2800|(19|2[0-9](0[48]|[2468][048]|[13579][26])))-02-29)|(((19|2[0-9])[0-9]{2})-02-(0[1-9]|1[0-9]|2[0-8]))|(((19|2[0-9])[0-9]{2})-(0[13578]|10|12)-(0[1-9]|[12][0-9]|3[01]))|(((19|2[0-9])[0-9]{2})-(0[469]|11)-(0[1-9]|[12][0-9]|30)))T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])(\\.[0-9]+)?(Z|(-((0[0-9]|1[0-2]):00|0[39]:30)|\\+((0[0-9]|1[0-4]):00|(0[34569]|10):30|(0[58]|12):45)))$" }, - "EmailAddressDatatype" : - { "description" : "An email address string formatted according to RFC 6531.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "type" : "string", - "format" : "email", - "pattern" : "^.+@.+$" } ] }, - "IntegerDatatype" : - { "description" : "A whole number value.", - "type" : "integer" }, - "MarkupLineDatatype" : - { "description" : "A single line of Markdown content conformant to the Commonmark specification.", - "type" : "string", - "pattern" : "^[^\n]+$" }, - "MarkupMultilineDatatype" : - { "description" : "A multiple lines of Markdown content conformant to the Commonmark specification.", - "type" : "string" }, - "NonNegativeIntegerDatatype" : - { "description" : "An integer value that is equal to or greater than 0.", - "allOf" : - [ - { "$ref" : "#/definitions/IntegerDatatype" }, - - { "type" : "number", - "minimum" : 0 } ] }, - "StringDatatype" : - { "description" : "A non-empty string with leading and trailing whitespace disallowed. Whitespace is: U+9, U+10, U+32 or [ \n\t]+", - "type" : "string", - "pattern" : "^\\S(.*\\S)?$" }, - "TokenDatatype" : - { "description" : "A non-colonized name as defined by XML Schema Part 2: Datatypes Second Edition. https://www.w3.org/TR/xmlschema11-2/#NCName.", - "type" : "string", - "pattern" : "^(\\p{L}|_)(\\p{L}|\\p{N}|[.\\-_])*$" }, - "URIDatatype" : - { "description" : "A universal resource identifier (URI) formatted according to RFC3986.", - "type" : "string", - "format" : "uri", - "pattern" : "^[a-zA-Z][a-zA-Z0-9+\\-.]+:.+$" }, - "URIReferenceDatatype" : - { "description" : "A URI Reference, either a URI or a relative-reference, formatted according to section 4.1 of RFC3986.", - "type" : "string", - "format" : "uri-reference" }, - "UUIDDatatype" : - { "description" : "A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.", - "type" : "string", - "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-[45][0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" } }, - "properties" : - { "$schema" : - { "$ref" : "#/definitions/json-schema-directive" }, - "component-definition" : - { "$ref" : "#/definitions/oscal-component-definition-oscal-component-definition:component-definition" } }, - "required" : - [ "component-definition" ], - "additionalProperties" : false } \ No newline at end of file diff --git a/data/schemas/oscal/oscal_mapping_schema.json b/data/schemas/oscal/oscal_mapping_schema.json deleted file mode 100644 index a1bdafb4..00000000 --- a/data/schemas/oscal/oscal_mapping_schema.json +++ /dev/null @@ -1,1569 +0,0 @@ - - { "$schema" : "http://json-schema.org/draft-07/schema#", - "$id" : "http://csrc.nist.gov/ns/oscal/1.2.2/oscal-mapping-schema.json", - "$comment" : "OSCAL Control Mapping Model: JSON Schema", - "type" : "object", - "definitions" : - { "json-schema-directive" : - { "title" : "Schema Directive", - "description" : "A JSON Schema directive to bind a specific schema to its document instance.", - "$id" : "#/definitions/json-schema-directive", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "oscal-mapping-oscal-mapping:mapping-collection" : - { "title" : "Mapping Collection", - "description" : "A collection of relationship-based control and/or control statement mappings.", - "$id" : "#/definitions/oscal-mapping-oscal-mapping:mapping-collection", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Mapping Collection Universally Unique Identifier", - "description" : "A globally unique identifier with cross-instance scope for this catalog instance. This UUID should be changed when this document is revised.", - "$ref" : "#/definitions/UUIDDatatype" }, - "metadata" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:metadata" }, - "provenance" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:mapping-provenance" }, - "mappings" : - { "anyOf" : - [ - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:mapping" }, - - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:mapping" } } ] }, - "back-matter" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:back-matter" } }, - "required" : - [ "uuid", - "metadata", - "provenance", - "mappings" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-metadata:metadata" : - { "title" : "Document Metadata", - "description" : "Provides information about the containing document, and defines concepts that are shared across the document.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:metadata", - "type" : "object", - "properties" : - { "title" : - { "title" : "Document Title", - "description" : "A name given to the document, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "published" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:published" }, - "last-modified" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:last-modified" }, - "version" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:version" }, - "oscal-version" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:oscal-version" }, - "revisions" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Revision History Entry", - "description" : "An entry in a sequential list of revisions to the containing document, expected to be in reverse chronological order (i.e. latest first).", - "type" : "object", - "properties" : - { "title" : - { "title" : "Document Title", - "description" : "A name given to the document revision, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "published" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:published" }, - "last-modified" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:last-modified" }, - "version" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:version" }, - "oscal-version" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:oscal-version" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "required" : - [ "version" ], - "additionalProperties" : false } }, - "document-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:document-id" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:link" } }, - "roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Role", - "description" : "Defines a function, which might be assigned to a party in a specific situation.", - "type" : "object", - "properties" : - { "id" : - { "title" : "Role Identifier", - "description" : "A unique identifier for the role.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Role Title", - "description" : "A name given to the role, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "short-name" : - { "title" : "Role Short Name", - "description" : "A short common name, abbreviation, or acronym for the role.", - "$ref" : "#/definitions/StringDatatype" }, - "description" : - { "title" : "Role Description", - "description" : "A summary of the role's purpose and associated responsibilities.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "required" : - [ "id", - "title" ], - "additionalProperties" : false } }, - "locations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Location", - "description" : "A physical point of presence, which may be associated with people, organizations, or other concepts within the current or linked OSCAL document.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Location Universally Unique Identifier", - "description" : "A unique ID for the location, for reference.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Location Title", - "description" : "A name given to the location, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "address" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:address" }, - "email-addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:email-address" } }, - "telephone-numbers" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:telephone-number" } }, - "urls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Location URL", - "description" : "The uniform resource locator (URL) for a web site or other resource associated with the location.", - "$ref" : "#/definitions/URIDatatype" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "required" : - [ "uuid" ], - "additionalProperties" : false } }, - "parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Party", - "description" : "An organization or person, which may be associated with roles or other concepts within the current or linked OSCAL document.", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "uuid" : - { "title" : "Party Universally Unique Identifier", - "description" : "A unique identifier for the party.", - "$ref" : "#/definitions/UUIDDatatype" }, - "type" : - { "title" : "Party Type", - "description" : "A category describing the kind of party the object describes.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "person", - "organization" ] } ] }, - "name" : - { "title" : "Party Name", - "description" : "The full name of the party. This is typically the legal name associated with the party.", - "$ref" : "#/definitions/StringDatatype" }, - "short-name" : - { "title" : "Party Short Name", - "description" : "A short common name, abbreviation, or acronym for the party.", - "$ref" : "#/definitions/StringDatatype" }, - "external-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Party External Identifier", - "description" : "An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).", - "type" : "object", - "properties" : - { "scheme" : - { "title" : "External Identifier Schema", - "description" : "Indicates the type of external identifier.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://orcid.org/" ] } ] }, - "id" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "id", - "scheme" ], - "additionalProperties" : false } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:link" } }, - "email-addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:email-address" } }, - "telephone-numbers" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:telephone-number" } }, - "addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:address" } }, - "member-of-organizations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Organizational Affiliation", - "description" : "A reference to another party by UUID, typically an organization, that this subject is associated with.", - "$ref" : "#/definitions/UUIDDatatype" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - - { "properties" : - { "uuid" : - { "title" : "Party Universally Unique Identifier", - "description" : "A unique identifier for the party.", - "$ref" : "#/definitions/UUIDDatatype" }, - "type" : - { "title" : "Party Type", - "description" : "A category describing the kind of party the object describes.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "person", - "organization" ] } ] }, - "name" : - { "title" : "Party Name", - "description" : "The full name of the party. This is typically the legal name associated with the party.", - "$ref" : "#/definitions/StringDatatype" }, - "short-name" : - { "title" : "Party Short Name", - "description" : "A short common name, abbreviation, or acronym for the party.", - "$ref" : "#/definitions/StringDatatype" }, - "external-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Party External Identifier", - "description" : "An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).", - "type" : "object", - "properties" : - { "scheme" : - { "title" : "External Identifier Schema", - "description" : "Indicates the type of external identifier.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://orcid.org/" ] } ] }, - "id" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "id", - "scheme" ], - "additionalProperties" : false } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:link" } }, - "email-addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:email-address" } }, - "telephone-numbers" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:telephone-number" } }, - "location-uuids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:location-uuid" } }, - "member-of-organizations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Organizational Affiliation", - "description" : "A reference to another party by UUID, typically an organization, that this subject is associated with.", - "$ref" : "#/definitions/UUIDDatatype" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "additionalProperties" : false } ] } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:responsible-party" } }, - "actions" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:action" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "required" : - [ "title", - "last-modified", - "version", - "oscal-version" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-metadata:location-uuid" : - { "title" : "Location Universally Unique Identifier Reference", - "description" : "Reference to a location by UUID.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:location-uuid", - "$ref" : "#/definitions/UUIDDatatype" }, - "oscal-mapping-oscal-metadata:party-uuid" : - { "title" : "Party Universally Unique Identifier Reference", - "description" : "Reference to a party by UUID.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:party-uuid", - "$ref" : "#/definitions/UUIDDatatype" }, - "oscal-mapping-oscal-metadata:role-id" : - { "title" : "Role Identifier Reference", - "description" : "Reference to a role by UUID.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:role-id", - "$ref" : "#/definitions/TokenDatatype" }, - "oscal-mapping-oscal-metadata:back-matter" : - { "title" : "Back matter", - "description" : "A collection of resources that may be referenced from within the OSCAL document instance.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:back-matter", - "type" : "object", - "properties" : - { "resources" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Resource", - "description" : "A resource associated with content in the containing document instance. A resource may be directly included in the document using base64 encoding or may point to one or more equivalent internet resources.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Resource Universally Unique Identifier", - "description" : "A unique identifier for a resource.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Resource Title", - "description" : "An optional name given to the resource, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Resource Description", - "description" : "An optional short summary of the resource used to indicate the purpose of the resource.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:property" } }, - "document-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:document-id" } }, - "citation" : - { "title" : "Citation", - "description" : "An optional citation consisting of end note text using structured markup.", - "type" : "object", - "properties" : - { "text" : - { "title" : "Citation Text", - "description" : "A line of citation text.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:link" } } }, - "required" : - [ "text" ], - "additionalProperties" : false }, - "rlinks" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Resource link", - "description" : "A URL-based pointer to an external resource with an optional hash for verification and change detection.", - "type" : "object", - "properties" : - { "href" : - { "title" : "Hypertext Reference", - "description" : "A resolvable URL pointing to the referenced resource.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "media-type" : - { "title" : "Media Type", - "description" : "A label that indicates the nature of a resource, as a data serialization or format.", - "$ref" : "#/definitions/StringDatatype" }, - "hashes" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:hash" } } }, - "required" : - [ "href" ], - "additionalProperties" : false } }, - "base64" : - { "title" : "Base64", - "description" : "A resource encoded using the Base64 alphabet defined by RFC 2045.", - "type" : "object", - "properties" : - { "filename" : - { "title" : "File Name", - "description" : "Name of the file before it was encoded as Base64 to be embedded in a resource. This is the name that will be assigned to the file when the file is decoded.", - "$ref" : "#/definitions/TokenDatatype" }, - "media-type" : - { "title" : "Media Type", - "description" : "A label that indicates the nature of a resource, as a data serialization or format.", - "$ref" : "#/definitions/StringDatatype" }, - "value" : - { "$ref" : "#/definitions/Base64Datatype" } }, - "required" : - [ "value" ], - "additionalProperties" : false }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "required" : - [ "uuid" ], - "additionalProperties" : false } } }, - "additionalProperties" : false }, - "oscal-mapping-oscal-metadata:property" : - { "title" : "Property", - "description" : "An attribute, characteristic, or quality of the containing object expressed as a namespace qualified name/value pair.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:property", - "type" : "object", - "properties" : - { "name" : - { "title" : "Property Name", - "description" : "A textual label, within a namespace, that identifies a specific attribute, characteristic, or quality of the property's containing object.", - "$ref" : "#/definitions/TokenDatatype" }, - "uuid" : - { "title" : "Property Universally Unique Identifier", - "description" : "A unique identifier for a property.", - "$ref" : "#/definitions/UUIDDatatype" }, - "ns" : - { "title" : "Property Namespace", - "description" : "A namespace qualifying the property's name. This allows different organizations to associate distinct semantics with the same name.", - "$ref" : "#/definitions/URIDatatype" }, - "value" : - { "title" : "Property Value", - "description" : "Indicates the value of the attribute, characteristic, or quality.", - "$ref" : "#/definitions/StringDatatype" }, - "class" : - { "title" : "Property Class", - "description" : "A textual label that provides a sub-type or characterization of the property's name.", - "$ref" : "#/definitions/TokenDatatype" }, - "group" : - { "title" : "Property Group", - "description" : "An identifier for relating distinct sets of properties.", - "$ref" : "#/definitions/TokenDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "required" : - [ "name", - "value" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-metadata:link" : - { "title" : "Link", - "description" : "A reference to a local or remote resource, that has a specific relation to the containing object.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:link", - "type" : "object", - "properties" : - { "href" : - { "title" : "Hypertext Reference", - "description" : "A resolvable URL reference to a resource.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "rel" : - { "title" : "Link Relation Type", - "description" : "Describes the type of relationship provided by the link's hypertext reference. This can be an indicator of the link's purpose.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "reference" ] } ] }, - "media-type" : - { "title" : "Media Type", - "description" : "A label that indicates the nature of a resource, as a data serialization or format.", - "$ref" : "#/definitions/StringDatatype" }, - "resource-fragment" : - { "title" : "Resource Fragment", - "description" : "In case where the href points to a back-matter/resource, this value will indicate the URI fragment to append to any rlink associated with the resource. This value MUST be URI encoded.", - "$ref" : "#/definitions/StringDatatype" }, - "text" : - { "title" : "Link Text", - "description" : "A textual label to associate with the link, which may be used for presentation in a tool.", - "$ref" : "#/definitions/MarkupLineDatatype" } }, - "required" : - [ "href" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-metadata:responsible-party" : - { "title" : "Responsible Party", - "description" : "A reference to a set of persons and/or organizations that have responsibility for performing the referenced role in the context of the containing object.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:responsible-party", - "type" : "object", - "properties" : - { "role-id" : - { "title" : "Responsible Role", - "description" : "A reference to a role performed by a party.", - "$ref" : "#/definitions/TokenDatatype" }, - "party-uuids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:party-uuid" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "required" : - [ "role-id", - "party-uuids" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-metadata:action" : - { "title" : "Action", - "description" : "An action applied by a role within a given party to the content.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:action", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Action Universally Unique Identifier", - "description" : "A unique identifier that can be used to reference this defined action elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "date" : - { "title" : "Action Occurrence Date", - "description" : "The date and time when the action occurred.", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "type" : - { "title" : "Action Type", - "description" : "The type of action documented by the assembly, such as an approval.", - "$ref" : "#/definitions/TokenDatatype" }, - "system" : - { "title" : "Action Type System", - "description" : "Specifies the action type system used.", - "$ref" : "#/definitions/URIDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:link" } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:responsible-party" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "type", - "system" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-metadata:responsible-role" : - { "title" : "Responsible Role", - "description" : "A reference to a role with responsibility for performing a function relative to the containing object, optionally associated with a set of persons and/or organizations that perform that role.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:responsible-role", - "type" : "object", - "properties" : - { "role-id" : - { "title" : "Responsible Role ID", - "description" : "A human-oriented identifier reference to a role performed.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:link" } }, - "party-uuids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:party-uuid" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "required" : - [ "role-id" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-metadata:hash" : - { "title" : "Hash", - "description" : "A representation of a cryptographic digest generated over a resource using a specified hash algorithm.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:hash", - "type" : "object", - "properties" : - { "algorithm" : - { "title" : "Hash algorithm", - "description" : "The digest method by which a hash is derived.", - "anyOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "SHA-224", - "SHA-256", - "SHA-384", - "SHA-512", - "SHA3-224", - "SHA3-256", - "SHA3-384", - "SHA3-512" ] } ] }, - "value" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "value", - "algorithm" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-metadata:remarks" : - { "title" : "Remarks", - "description" : "Additional commentary about the containing object.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:remarks", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "oscal-mapping-oscal-metadata:published" : - { "title" : "Publication Timestamp", - "description" : "The date and time the document was last made available.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:published", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "oscal-mapping-oscal-metadata:last-modified" : - { "title" : "Last Modified Timestamp", - "description" : "The date and time the document was last stored for later retrieval.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:last-modified", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "oscal-mapping-oscal-metadata:version" : - { "title" : "Document Version", - "description" : "Used to distinguish a specific revision of an OSCAL document from other previous and future versions.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:version", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-mapping-oscal-metadata:oscal-version" : - { "title" : "OSCAL Version", - "description" : "The OSCAL model version the document was authored against and will conform to as valid.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:oscal-version", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-mapping-oscal-metadata:email-address" : - { "title" : "Email Address", - "description" : "An email address as defined by RFC 5322 Section 3.4.1.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:email-address", - "$ref" : "#/definitions/EmailAddressDatatype" }, - "oscal-mapping-oscal-metadata:telephone-number" : - { "title" : "Telephone Number", - "description" : "A telephone service number as defined by ITU-T E.164.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:telephone-number", - "type" : "object", - "properties" : - { "type" : - { "title" : "type flag", - "description" : "Indicates the type of phone number.", - "anyOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "home", - "office", - "mobile" ] } ] }, - "number" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "number" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-metadata:address" : - { "title" : "Address", - "description" : "A postal address for the location.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:address", - "type" : "object", - "properties" : - { "type" : - { "title" : "Address Type", - "description" : "Indicates the type of address.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "home", - "work" ] } ] }, - "addr-lines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:addr-line" } }, - "city" : - { "title" : "City", - "description" : "City, town or geographical region for the mailing address.", - "$ref" : "#/definitions/StringDatatype" }, - "state" : - { "title" : "State", - "description" : "State, province or analogous geographical region for a mailing address.", - "$ref" : "#/definitions/StringDatatype" }, - "postal-code" : - { "title" : "Postal Code", - "description" : "Postal or ZIP code for mailing address.", - "$ref" : "#/definitions/StringDatatype" }, - "country" : - { "title" : "Country Code", - "description" : "The ISO 3166-1 alpha-2 country code for the mailing address.", - "$ref" : "#/definitions/StringDatatype" } }, - "additionalProperties" : false }, - "oscal-mapping-oscal-metadata:addr-line" : - { "title" : "Address line", - "description" : "A single line of an address.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:addr-line", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-mapping-oscal-metadata:document-id" : - { "title" : "Document Identifier", - "description" : "A document identifier qualified by an identifier scheme.", - "$id" : "#/definitions/oscal-mapping-oscal-metadata:document-id", - "type" : "object", - "properties" : - { "scheme" : - { "title" : "Document Identification Scheme", - "description" : "Qualifies the kind of document identifier using a URI. If the scheme is not provided the value of the element will be interpreted as a string of characters.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://www.doi.org/" ] } ] }, - "identifier" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "identifier" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-mapping-common:mapping" : - { "title" : "Control Mapping", - "description" : "A mapping between two target resources.", - "$id" : "#/definitions/oscal-mapping-oscal-mapping-common:mapping", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Mapping Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mapping definition elsewhere in this or other OSCAL instances. The locally defined UUID of the mapping can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same mapping across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "method" : - { "title" : "Method", - "description" : "The method used to complete the overall mapping.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "human", - "automation", - "hybrid" ] } ] }, - "matching-rationale" : - { "title" : "Matching", - "description" : "The method used for relating controls within the mapping. The supported methods are aligned with the NIST Interagency Report (IR) 8477, Section 4.3 Set Theory Relationship Mapping.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "syntactic", - "semantic", - "functional" ] } ] }, - "status" : - { "title" : "Status", - "description" : "The current status of this mapping document.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "complete", - "not-complete", - "draft", - "deprecated", - "superseded" ] } ] }, - "source-resource" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:mapping-resource-reference" }, - "target-resource" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:mapping-resource-reference" }, - "maps" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:map" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" }, - "mapping-description" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:mapping-description" }, - "source-gap-summary" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:gap-summary" }, - "target-gap-summary" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:gap-summary" }, - "confidence-score" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:confidence-score" }, - "coverage" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:coverage" } }, - "required" : - [ "uuid", - "source-resource", - "target-resource", - "maps" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-mapping-common:map" : - { "title" : "Mapping Entry", - "description" : "A relationship-based mapping between a source and target set consisting of members (i.e., controls, control statements) from the respective source and target.", - "$id" : "#/definitions/oscal-mapping-oscal-mapping-common:map", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Mapping Entry Identifier", - "description" : "The unique identifier for the mapping entry.", - "$ref" : "#/definitions/UUIDDatatype" }, - "ns" : - { "title" : "Relationship Value Namespace", - "description" : "A namespace qualifying the relationship's value. This allows different organizations to associate distinct semantics for relationships with the same name.", - "$ref" : "#/definitions/URIDatatype" }, - "matching-rationale" : - { "title" : "Matching", - "description" : "The method used for relating controls within the mapping. The supported methods are aligned with the NIST Interagency Report (IR) 8477, Section 4.3 Set Theory Relationship Mapping.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "syntactic", - "semantic", - "functional" ] } ] }, - "relationship" : - { "title" : "Mapping Entry Relationship", - "description" : "The relationship type for the mapping entry, which describes the relationship between the effective requirements of the specified source and target sets in the context of the matching-rationale method globaly defined in the provenance unless overwritten locally in the map. The relationship type and the matching-rationale must be used together. However, more than one matching-rationale method may apply to a source and target pair.", - "$ref" : "#/definitions/TokenDatatype" }, - "sources" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:mapping-item" } }, - "targets" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:mapping-item" } }, - "qualifiers" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:qualifier-item" } }, - "confidence-score" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:confidence-score" }, - "coverage" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:coverage" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "relationship", - "sources", - "targets" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-mapping-common:mapping-item" : - { "title" : "Mapping Entry Item (source or target)", - "description" : "A specific edge within a source or target that is the subject of a mapping.", - "$id" : "#/definitions/oscal-mapping-oscal-mapping-common:mapping-item", - "type" : "object", - "properties" : - { "type" : - { "title" : "Subject Type", - "description" : "The semantic type of the subject.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "control", - "statement" ] } ] }, - "id-ref" : - { "title" : "Subject Identifier Reference", - "description" : "A reference to an identified subject that is of the specified type .", - "$ref" : "#/definitions/StringDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "required" : - [ "type", - "id-ref" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-mapping-common:mapping-resource-reference" : - { "title" : "Mapped Resource Reference", - "description" : "A reference to a resource that is either the source or the target of a mapping.", - "$id" : "#/definitions/oscal-mapping-oscal-mapping-common:mapping-resource-reference", - "type" : "object", - "properties" : - { "ns" : - { "title" : "Resource Type Namespace", - "description" : "An optional namespace qualifying the resource's type.", - "$ref" : "#/definitions/URIDatatype" }, - "type" : - { "title" : "Resource Type", - "description" : "The semantic type of the resource.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "catalog", - "profile" ] } ] }, - "href" : - { "title" : "Catalog or Profile Reference", - "description" : "A resolvable URL reference to the base catalog or profile that this profile is tailoring.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "required" : - [ "type", - "href" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-mapping-common:qualifier-item" : - { "title" : "Relationship Qualifier", - "description" : "Describes requirements, incompatibilities and gaps that are identified between a target and source in a mapping item.", - "$id" : "#/definitions/oscal-mapping-oscal-mapping-common:qualifier-item", - "type" : "object", - "properties" : - { "subject" : - { "title" : "Subject", - "description" : "The focus of the qualifier.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "source", - "target", - "both" ] } ] }, - "predicate" : - { "title" : "Predicate", - "description" : "The predicate describes how the qualifer applies to the subject.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "has-requirement", - "has-incompatibility" ] } ] }, - "category" : - { "title" : "Category", - "description" : "The category expresses the resolvable nature of the predicate.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "restricted", - "addressable", - "blocked" ] } ] }, - "description" : - { "title" : "Description of the qualifier", - "description" : "Details that outline what requirements must be met, or cannot be met. If the qualifier identifies a gap, this should idenfity the gap, and any incompatibilities.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "required" : - [ "subject", - "predicate", - "category", - "description" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-mapping-common:mapping-provenance" : - { "title" : "Mapping Provenance", - "description" : "Describes requirements, incompatibilities and gaps that are identified between a target and source in a mapping item.", - "$id" : "#/definitions/oscal-mapping-oscal-mapping-common:mapping-provenance", - "type" : "object", - "properties" : - { "method" : - { "title" : "Method", - "description" : "The method used to complete the overall mapping.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "human", - "automation", - "hybrid" ] } ] }, - "matching-rationale" : - { "title" : "Matching", - "description" : "The method used for relating controls within the mapping. The supported methods are aligned with the NIST Interagency Report (IR) 8477, Section 4.3 Set Theory Relationship Mapping.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "syntactic", - "semantic", - "functional" ] } ] }, - "status" : - { "title" : "Status", - "description" : "The current status of this mapping document.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "complete", - "not-complete", - "draft", - "deprecated", - "superseded" ] } ] }, - "confidence-score" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:confidence-score" }, - "coverage" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:coverage" }, - "mapping-description" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:mapping-description" }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:responsible-party" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "required" : - [ "method", - "matching-rationale", - "status", - "mapping-description" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-mapping-common:gap-summary" : - { "title" : "Gap Summary", - "description" : "A by-id collection of all controls that were not mapped at all in this mapping-collection. If a control is partially mapped, the parts of the control are not mappable, the gap and discrepancies should be documented in the relationship-gal.", - "$id" : "#/definitions/oscal-mapping-oscal-mapping-common:gap-summary", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Gap Summary Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mapping gap summary elsewhere in this or other OSCAL instances. The locally defined UUID of the SSP can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance).This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "unmapped-controls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-control-common:select-control-by-id" } } }, - "required" : - [ "uuid", - "unmapped-controls" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-mapping-common:confidence-score" : - { "title" : "Confidence Score", - "description" : "This records either a string category or a decimal value from 0-1 representing a percentage. Both of these values describe an estimation of the author's confidence that this mapping is correct and accurate.", - "$id" : "#/definitions/oscal-mapping-oscal-mapping-common:confidence-score", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "category" : - { "$ref" : "#/definitions/StringDatatype" } }, - "additionalProperties" : false }, - - { "properties" : - { "percentage" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping-common:percentage" } }, - "additionalProperties" : false } ] }, - "oscal-mapping-oscal-mapping-common:coverage" : - { "title" : "Coverage", - "description" : "A decimal value from 0-1, representing the percentage coverage of the targets by the sources.", - "$id" : "#/definitions/oscal-mapping-oscal-mapping-common:coverage", - "type" : "object", - "properties" : - { "generation-method" : - { "title" : "Coverage Generation Method", - "description" : "The method used to determine the coverage value.", - "anyOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "arbitrary" ] } ] }, - "target-coverage" : - { "$ref" : "#/definitions/DecimalDatatype" } }, - "required" : - [ "target-coverage" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-mapping-common:percentage" : - { "title" : "Percentage", - "description" : "A decimal value from 0-1, representing a percentage.", - "$id" : "#/definitions/oscal-mapping-oscal-mapping-common:percentage", - "$ref" : "#/definitions/DecimalDatatype" }, - "oscal-mapping-oscal-mapping-common:mapping-description" : - { "title" : "Mapping Description", - "description" : "Description of the context and intended use of the mapping set.", - "$id" : "#/definitions/oscal-mapping-oscal-mapping-common:mapping-description", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "oscal-mapping-oscal-control-common:part" : - { "title" : "Part", - "description" : "An annotated, markup-based textual element of a control's or catalog group's definition, or a child of another part.", - "$id" : "#/definitions/oscal-mapping-oscal-control-common:part", - "type" : "object", - "properties" : - { "id" : - { "title" : "Part Identifier", - "description" : "A unique identifier for the part.", - "$ref" : "#/definitions/TokenDatatype" }, - "name" : - { "title" : "Part Name", - "description" : "A textual label that uniquely identifies the part's semantic type, which exists in a value space qualified by the ns.", - "$ref" : "#/definitions/TokenDatatype" }, - "ns" : - { "title" : "Part Namespace", - "description" : "An optional namespace qualifying the part's name. This allows different organizations to associate distinct semantics with the same name.", - "$ref" : "#/definitions/URIDatatype" }, - "class" : - { "title" : "Part Class", - "description" : "An optional textual providing a sub-type or characterization of the part's name, or a category to which the part belongs.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Part Title", - "description" : "An optional name given to the part, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:property" } }, - "prose" : - { "title" : "Part Text", - "description" : "Permits multiple paragraphs, lists, tables etc.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "parts" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-control-common:part" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:link" } } }, - "required" : - [ "name" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-control-common:parameter" : - { "title" : "Parameter", - "description" : "Parameters provide a mechanism for the dynamic assignment of value(s) in a control.", - "$id" : "#/definitions/oscal-mapping-oscal-control-common:parameter", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "id" : - { "title" : "Parameter Identifier", - "description" : "A unique identifier for the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "class" : - { "title" : "Parameter Class", - "description" : "A textual label that provides a characterization of the type, purpose, use or scope of the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "depends-on" : - { "title" : "Depends on", - "description" : "(deprecated) Another parameter invoking this one. This construct has been deprecated and should not be used.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:link" } }, - "label" : - { "title" : "Parameter Label", - "description" : "A short, placeholder name for the parameter, which can be used as a substitute for a value if no value is assigned.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "usage" : - { "title" : "Parameter Usage Description", - "description" : "Describes the purpose and use of a parameter.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "constraints" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-control-common:parameter-constraint" } }, - "guidelines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-control-common:parameter-guideline" } }, - "values" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-control-common:parameter-value" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - - { "properties" : - { "id" : - { "title" : "Parameter Identifier", - "description" : "A unique identifier for the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "class" : - { "title" : "Parameter Class", - "description" : "A textual label that provides a characterization of the type, purpose, use or scope of the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "depends-on" : - { "title" : "Depends on", - "description" : "(deprecated) Another parameter invoking this one. This construct has been deprecated and should not be used.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:link" } }, - "label" : - { "title" : "Parameter Label", - "description" : "A short, placeholder name for the parameter, which can be used as a substitute for a value if no value is assigned.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "usage" : - { "title" : "Parameter Usage Description", - "description" : "Describes the purpose and use of a parameter.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "constraints" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-control-common:parameter-constraint" } }, - "guidelines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-control-common:parameter-guideline" } }, - "select" : - { "$ref" : "#/definitions/oscal-mapping-oscal-control-common:parameter-selection" }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "additionalProperties" : false } ] }, - "oscal-mapping-oscal-control-common:parameter-constraint" : - { "title" : "Constraint", - "description" : "A formal or informal expression of a constraint or test.", - "$id" : "#/definitions/oscal-mapping-oscal-control-common:parameter-constraint", - "type" : "object", - "properties" : - { "description" : - { "title" : "Constraint Description", - "description" : "A textual summary of the constraint to be applied.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "tests" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Constraint Test", - "description" : "A test expression which is expected to be evaluated by a tool.", - "type" : "object", - "properties" : - { "expression" : - { "title" : "Constraint test", - "description" : "A formal (executable) expression of a constraint.", - "$ref" : "#/definitions/StringDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "required" : - [ "expression" ], - "additionalProperties" : false } } }, - "additionalProperties" : false }, - "oscal-mapping-oscal-control-common:parameter-guideline" : - { "title" : "Guideline", - "description" : "A prose statement that provides a recommendation for the use of a parameter.", - "$id" : "#/definitions/oscal-mapping-oscal-control-common:parameter-guideline", - "type" : "object", - "properties" : - { "prose" : - { "title" : "Guideline Text", - "description" : "Prose permits multiple paragraphs, lists, tables etc.", - "$ref" : "#/definitions/MarkupMultilineDatatype" } }, - "required" : - [ "prose" ], - "additionalProperties" : false }, - "oscal-mapping-oscal-control-common:parameter-value" : - { "title" : "Parameter Value", - "description" : "A parameter value or set of values.", - "$id" : "#/definitions/oscal-mapping-oscal-control-common:parameter-value", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-mapping-oscal-control-common:parameter-selection" : - { "title" : "Selection", - "description" : "Presenting a choice among alternatives.", - "$id" : "#/definitions/oscal-mapping-oscal-control-common:parameter-selection", - "type" : "object", - "properties" : - { "how-many" : - { "title" : "Parameter Cardinality", - "description" : "Describes the number of selections that must occur. Without this setting, only one value should be assumed to be permitted.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "one", - "one-or-more" ] } ] }, - "choice" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Choice", - "description" : "A value selection among several such options.", - "$ref" : "#/definitions/MarkupLineDatatype" } } }, - "additionalProperties" : false }, - "oscal-mapping-oscal-control-common:include-all" : - { "title" : "Include All", - "description" : "Include all controls from the imported catalog or profile resources.", - "$id" : "#/definitions/oscal-mapping-oscal-control-common:include-all", - "type" : "object", - "additionalProperties" : false }, - "oscal-mapping-oscal-control-common:with-id" : - { "title" : "Match Controls by Identifier", - "description" : "Selecting a control by its ID given as a literal.", - "$id" : "#/definitions/oscal-mapping-oscal-control-common:with-id", - "$ref" : "#/definitions/TokenDatatype" }, - "oscal-mapping-oscal-control-common:matching" : - { "title" : "Match Controls by Pattern", - "description" : "Selecting a set of controls by matching their IDs with a wildcard pattern.", - "$id" : "#/definitions/oscal-mapping-oscal-control-common:matching", - "type" : "object", - "properties" : - { "pattern" : - { "title" : "Pattern", - "description" : "A glob expression matching the IDs of one or more controls to be selected.", - "$ref" : "#/definitions/StringDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-mapping-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - "oscal-mapping-oscal-control-common:select-control-by-id" : - { "title" : "Select Control", - "description" : "Select a control or controls from an imported control set.", - "$id" : "#/definitions/oscal-mapping-oscal-control-common:select-control-by-id", - "type" : "object", - "properties" : - { "with-child-controls" : - { "title" : "Include Contained Controls with Control", - "description" : "When a control is included, whether its child (dependent) controls are also included.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "yes", - "no" ] } ] }, - "with-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-control-common:with-id" } }, - "matching" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-mapping-oscal-control-common:matching" } } }, - "additionalProperties" : false }, - "Base64Datatype" : - { "description" : "Binary data encoded using the Base 64 encoding algorithm as defined by RFC4648.", - "type" : "string", - "pattern" : "^[0-9A-Za-z+/]+={0,2}$", - "contentEncoding" : "base64" }, - "DateTimeWithTimezoneDatatype" : - { "description" : "A string representing a point in time with a required timezone.", - "type" : "string", - "format" : "date-time", - "pattern" : "^(((2000|2400|2800|(19|2[0-9](0[48]|[2468][048]|[13579][26])))-02-29)|(((19|2[0-9])[0-9]{2})-02-(0[1-9]|1[0-9]|2[0-8]))|(((19|2[0-9])[0-9]{2})-(0[13578]|10|12)-(0[1-9]|[12][0-9]|3[01]))|(((19|2[0-9])[0-9]{2})-(0[469]|11)-(0[1-9]|[12][0-9]|30)))T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])(\\.[0-9]+)?(Z|(-((0[0-9]|1[0-2]):00|0[39]:30)|\\+((0[0-9]|1[0-4]):00|(0[34569]|10):30|(0[58]|12):45)))$" }, - "DecimalDatatype" : - { "description" : "A real number expressed using a whole and optional fractional part separated by a period.", - "type" : "number", - "pattern" : "^(\\+|-)?([0-9]+(\\.[0-9]*)?|\\.[0-9]+)$" }, - "EmailAddressDatatype" : - { "description" : "An email address string formatted according to RFC 6531.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "type" : "string", - "format" : "email", - "pattern" : "^.+@.+$" } ] }, - "MarkupLineDatatype" : - { "description" : "A single line of Markdown content conformant to the Commonmark specification.", - "type" : "string", - "pattern" : "^[^\n]+$" }, - "MarkupMultilineDatatype" : - { "description" : "A multiple lines of Markdown content conformant to the Commonmark specification.", - "type" : "string" }, - "StringDatatype" : - { "description" : "A non-empty string with leading and trailing whitespace disallowed. Whitespace is: U+9, U+10, U+32 or [ \n\t]+", - "type" : "string", - "pattern" : "^\\S(.*\\S)?$" }, - "TokenDatatype" : - { "description" : "A non-colonized name as defined by XML Schema Part 2: Datatypes Second Edition. https://www.w3.org/TR/xmlschema11-2/#NCName.", - "type" : "string", - "pattern" : "^(\\p{L}|_)(\\p{L}|\\p{N}|[.\\-_])*$" }, - "URIDatatype" : - { "description" : "A universal resource identifier (URI) formatted according to RFC3986.", - "type" : "string", - "format" : "uri", - "pattern" : "^[a-zA-Z][a-zA-Z0-9+\\-.]+:.+$" }, - "URIReferenceDatatype" : - { "description" : "A URI Reference, either a URI or a relative-reference, formatted according to section 4.1 of RFC3986.", - "type" : "string", - "format" : "uri-reference" }, - "UUIDDatatype" : - { "description" : "A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.", - "type" : "string", - "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-[45][0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" } }, - "properties" : - { "$schema" : - { "$ref" : "#/definitions/json-schema-directive" }, - "mapping-collection" : - { "$ref" : "#/definitions/oscal-mapping-oscal-mapping:mapping-collection" } }, - "required" : - [ "mapping-collection" ], - "additionalProperties" : false } \ No newline at end of file diff --git a/data/schemas/oscal/oscal_profile_schema.json b/data/schemas/oscal/oscal_profile_schema.json deleted file mode 100644 index 88d7e970..00000000 --- a/data/schemas/oscal/oscal_profile_schema.json +++ /dev/null @@ -1,1616 +0,0 @@ - - { "$schema" : "http://json-schema.org/draft-07/schema#", - "$id" : "http://csrc.nist.gov/ns/oscal/1.2.2/oscal-profile-schema.json", - "$comment" : "OSCAL Profile Model: JSON Schema", - "type" : "object", - "definitions" : - { "json-schema-directive" : - { "title" : "Schema Directive", - "description" : "A JSON Schema directive to bind a specific schema to its document instance.", - "$id" : "#/definitions/json-schema-directive", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "oscal-profile-oscal-profile:profile" : - { "title" : "Profile", - "description" : "Each OSCAL profile is defined by a profile element.", - "$id" : "#/definitions/oscal-profile-oscal-profile:profile", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Profile Universally Unique Identifier", - "description" : "Provides a globally unique means to identify a given profile instance.", - "$ref" : "#/definitions/UUIDDatatype" }, - "metadata" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:metadata" }, - "imports" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-profile:import" } }, - "merge" : - { "$ref" : "#/definitions/oscal-profile-oscal-profile:merge" }, - "modify" : - { "$ref" : "#/definitions/oscal-profile-oscal-profile:modify" }, - "back-matter" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:back-matter" } }, - "required" : - [ "uuid", - "metadata", - "imports" ], - "additionalProperties" : false }, - "oscal-profile-oscal-profile:import" : - { "title" : "Import Resource", - "description" : "Designates a referenced source catalog or profile that provides a source of control information for use in creating a new overlay or baseline.", - "$id" : "#/definitions/oscal-profile-oscal-profile:import", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "href" : - { "title" : "Catalog or Profile Reference", - "description" : "A resolvable URL reference to the base catalog or profile that this profile is tailoring.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "include-all" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:include-all" }, - "exclude-controls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:select-control-by-id" } } }, - "required" : - [ "include-all" ], - "additionalProperties" : false }, - - { "properties" : - { "href" : - { "title" : "Catalog or Profile Reference", - "description" : "A resolvable URL reference to the base catalog or profile that this profile is tailoring.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "include-controls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:select-control-by-id" } }, - "exclude-controls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:select-control-by-id" } } }, - "required" : - [ "include-controls" ], - "additionalProperties" : false } ] }, - "oscal-profile-oscal-profile:merge" : - { "title" : "Merge Controls", - "description" : "Provides structuring directives that instruct how controls are organized after profile resolution.", - "$id" : "#/definitions/oscal-profile-oscal-profile:merge", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "combine" : - { "title" : "Combination Rule", - "description" : "A Combine element defines how to resolve duplicate instances of the same control (e.g., controls with the same ID).", - "type" : "object", - "additionalProperties" : false }, - "flat" : - { "title" : "Flat Without Grouping", - "description" : "Directs that controls appear without any grouping structure.", - "type" : "object", - "additionalProperties" : false } }, - "required" : - [ "flat" ], - "additionalProperties" : false }, - - { "properties" : - { "combine" : - { "title" : "Combination Rule", - "description" : "A Combine element defines how to resolve duplicate instances of the same control (e.g., controls with the same ID).", - "type" : "object", - "additionalProperties" : false }, - "as-is" : - { "title" : "Group As-Is", - "description" : "Indicates that the controls selected should retain their original grouping as defined in the import source.", - "$ref" : "#/definitions/BooleanDatatype" } }, - "required" : - [ "as-is" ], - "additionalProperties" : false }, - - { "properties" : - { "combine" : - { "title" : "Combination Rule", - "description" : "A Combine element defines how to resolve duplicate instances of the same control (e.g., controls with the same ID).", - "type" : "object", - "additionalProperties" : false }, - "custom" : - { "title" : "Custom Grouping", - "description" : "Provides an alternate grouping structure that selected controls will be placed in.", - "type" : "object", - "properties" : - { "groups" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-profile:group" } }, - "insert-controls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-profile:insert-controls" } } }, - "additionalProperties" : false } }, - "required" : - [ "custom" ], - "additionalProperties" : false } ] }, - "oscal-profile-oscal-profile:group" : - { "title" : "Control Group", - "description" : "A group of (selected) controls or of groups of controls.", - "$id" : "#/definitions/oscal-profile-oscal-profile:group", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "id" : - { "title" : "Group Identifier", - "description" : "Identifies the group.", - "$ref" : "#/definitions/TokenDatatype" }, - "class" : - { "title" : "Group Class", - "description" : "A textual label that provides a sub-type or characterization of the group.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Group Title", - "description" : "A name to be given to the group for use in display.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "params" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:parameter" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:link" } }, - "parts" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:part" } }, - "groups" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-profile:group" } } }, - "required" : - [ "title" ], - "additionalProperties" : false }, - - { "properties" : - { "id" : - { "title" : "Group Identifier", - "description" : "Identifies the group.", - "$ref" : "#/definitions/TokenDatatype" }, - "class" : - { "title" : "Group Class", - "description" : "A textual label that provides a sub-type or characterization of the group.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Group Title", - "description" : "A name to be given to the group for use in display.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "params" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:parameter" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:link" } }, - "parts" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:part" } }, - "insert-controls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-profile:insert-controls" } } }, - "required" : - [ "title" ], - "additionalProperties" : false } ] }, - "oscal-profile-oscal-profile:modify" : - { "title" : "Modify Controls", - "description" : "Set parameters or amend controls in resolution.", - "$id" : "#/definitions/oscal-profile-oscal-profile:modify", - "type" : "object", - "properties" : - { "set-parameters" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Parameter Setting", - "description" : "A parameter setting, to be propagated to points of insertion.", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "param-id" : - { "title" : "Parameter ID", - "description" : "An identifier for the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "class" : - { "title" : "Parameter Class", - "description" : "A textual label that provides a characterization of the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "depends-on" : - { "title" : "Depends On", - "description" : "**(deprecated)** Another parameter invoking this one. This construct has been deprecated and should not be used.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:link" } }, - "label" : - { "title" : "Parameter Label", - "description" : "A short, placeholder name for the parameter, which can be used as a substitute for a value if no value is assigned.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "usage" : - { "title" : "Parameter Usage Description", - "description" : "Describes the purpose and use of a parameter.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "constraints" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:parameter-constraint" } }, - "guidelines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:parameter-guideline" } }, - "values" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:parameter-value" } } }, - "additionalProperties" : false }, - - { "properties" : - { "param-id" : - { "title" : "Parameter ID", - "description" : "An identifier for the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "class" : - { "title" : "Parameter Class", - "description" : "A textual label that provides a characterization of the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "depends-on" : - { "title" : "Depends On", - "description" : "**(deprecated)** Another parameter invoking this one. This construct has been deprecated and should not be used.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:link" } }, - "label" : - { "title" : "Parameter Label", - "description" : "A short, placeholder name for the parameter, which can be used as a substitute for a value if no value is assigned.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "usage" : - { "title" : "Parameter Usage Description", - "description" : "Describes the purpose and use of a parameter.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "constraints" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:parameter-constraint" } }, - "guidelines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:parameter-guideline" } }, - "select" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:parameter-selection" } }, - "additionalProperties" : false } ] } }, - "alters" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Alteration", - "description" : "Specifies changes to be made to an included control when a profile is resolved.", - "type" : "object", - "properties" : - { "control-id" : - { "title" : "Control Identifier Reference", - "description" : "A reference to a control with a corresponding id value. When referencing an externally defined control, the Control Identifier Reference must be used in the context of the external / imported OSCAL instance (e.g., uri-reference).", - "$ref" : "#/definitions/TokenDatatype" }, - "removes" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Removal", - "description" : "Specifies objects to be removed from a control based on specific aspects of the object that must all match.", - "type" : "object", - "properties" : - { "by-name" : - { "title" : "Reference by (assigned) name", - "description" : "Identify items remove by matching their assigned name.", - "$ref" : "#/definitions/TokenDatatype" }, - "by-class" : - { "title" : "Reference by class", - "description" : "Identify items to remove by matching their class.", - "$ref" : "#/definitions/TokenDatatype" }, - "by-id" : - { "title" : "Reference by ID", - "description" : "Identify items to remove indicated by their id.", - "$ref" : "#/definitions/TokenDatatype" }, - "by-item-name" : - { "title" : "Item Name Reference", - "description" : "Identify items to remove by the name of the item's information object name, e.g. title or prop.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "param", - "prop", - "link", - "part", - "mapping", - "map" ] } ] }, - "by-ns" : - { "title" : "Item Namespace Reference", - "description" : "Identify items to remove by the item's ns, which is the namespace associated with a part, or prop.", - "$ref" : "#/definitions/URIDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:remarks" } }, - "additionalProperties" : false } }, - "adds" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Addition", - "description" : "Specifies contents to be added into controls, in resolution.", - "type" : "object", - "properties" : - { "position" : - { "title" : "Position", - "description" : "Where to add the new content with respect to the targeted element (beside it or inside it).", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "before", - "after", - "starting", - "ending" ] } ] }, - "by-id" : - { "title" : "Reference by ID", - "description" : "Target location of the addition.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Title Change", - "description" : "A name given to the control, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "params" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:parameter" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:link" } }, - "parts" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:part" } } }, - "additionalProperties" : false } } }, - "required" : - [ "control-id" ], - "additionalProperties" : false } } }, - "additionalProperties" : false }, - "oscal-profile-oscal-profile:insert-controls" : - { "title" : "Insert Controls", - "description" : "Specifies which controls to use in the containing context.", - "$id" : "#/definitions/oscal-profile-oscal-profile:insert-controls", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "order" : - { "title" : "Order", - "description" : "A designation of how a selection of controls in a profile is to be ordered.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "keep", - "ascending", - "descending" ] } ] }, - "include-all" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:include-all" }, - "exclude-controls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:select-control-by-id" } } }, - "required" : - [ "include-all" ], - "additionalProperties" : false }, - - { "properties" : - { "order" : - { "title" : "Order", - "description" : "A designation of how a selection of controls in a profile is to be ordered.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "keep", - "ascending", - "descending" ] } ] }, - "include-controls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:select-control-by-id" } }, - "exclude-controls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:select-control-by-id" } } }, - "required" : - [ "include-controls" ], - "additionalProperties" : false } ] }, - "oscal-profile-oscal-metadata:metadata" : - { "title" : "Document Metadata", - "description" : "Provides information about the containing document, and defines concepts that are shared across the document.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:metadata", - "type" : "object", - "properties" : - { "title" : - { "title" : "Document Title", - "description" : "A name given to the document, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "published" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:published" }, - "last-modified" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:last-modified" }, - "version" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:version" }, - "oscal-version" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:oscal-version" }, - "revisions" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Revision History Entry", - "description" : "An entry in a sequential list of revisions to the containing document, expected to be in reverse chronological order (i.e. latest first).", - "type" : "object", - "properties" : - { "title" : - { "title" : "Document Title", - "description" : "A name given to the document revision, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "published" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:published" }, - "last-modified" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:last-modified" }, - "version" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:version" }, - "oscal-version" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:oscal-version" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:remarks" } }, - "required" : - [ "version" ], - "additionalProperties" : false } }, - "document-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:document-id" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:link" } }, - "roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Role", - "description" : "Defines a function, which might be assigned to a party in a specific situation.", - "type" : "object", - "properties" : - { "id" : - { "title" : "Role Identifier", - "description" : "A unique identifier for the role.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Role Title", - "description" : "A name given to the role, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "short-name" : - { "title" : "Role Short Name", - "description" : "A short common name, abbreviation, or acronym for the role.", - "$ref" : "#/definitions/StringDatatype" }, - "description" : - { "title" : "Role Description", - "description" : "A summary of the role's purpose and associated responsibilities.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:remarks" } }, - "required" : - [ "id", - "title" ], - "additionalProperties" : false } }, - "locations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Location", - "description" : "A physical point of presence, which may be associated with people, organizations, or other concepts within the current or linked OSCAL document.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Location Universally Unique Identifier", - "description" : "A unique ID for the location, for reference.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Location Title", - "description" : "A name given to the location, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "address" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:address" }, - "email-addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:email-address" } }, - "telephone-numbers" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:telephone-number" } }, - "urls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Location URL", - "description" : "The uniform resource locator (URL) for a web site or other resource associated with the location.", - "$ref" : "#/definitions/URIDatatype" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:remarks" } }, - "required" : - [ "uuid" ], - "additionalProperties" : false } }, - "parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Party", - "description" : "An organization or person, which may be associated with roles or other concepts within the current or linked OSCAL document.", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "uuid" : - { "title" : "Party Universally Unique Identifier", - "description" : "A unique identifier for the party.", - "$ref" : "#/definitions/UUIDDatatype" }, - "type" : - { "title" : "Party Type", - "description" : "A category describing the kind of party the object describes.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "person", - "organization" ] } ] }, - "name" : - { "title" : "Party Name", - "description" : "The full name of the party. This is typically the legal name associated with the party.", - "$ref" : "#/definitions/StringDatatype" }, - "short-name" : - { "title" : "Party Short Name", - "description" : "A short common name, abbreviation, or acronym for the party.", - "$ref" : "#/definitions/StringDatatype" }, - "external-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Party External Identifier", - "description" : "An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).", - "type" : "object", - "properties" : - { "scheme" : - { "title" : "External Identifier Schema", - "description" : "Indicates the type of external identifier.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://orcid.org/" ] } ] }, - "id" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "id", - "scheme" ], - "additionalProperties" : false } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:link" } }, - "email-addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:email-address" } }, - "telephone-numbers" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:telephone-number" } }, - "addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:address" } }, - "member-of-organizations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Organizational Affiliation", - "description" : "A reference to another party by UUID, typically an organization, that this subject is associated with.", - "$ref" : "#/definitions/UUIDDatatype" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - - { "properties" : - { "uuid" : - { "title" : "Party Universally Unique Identifier", - "description" : "A unique identifier for the party.", - "$ref" : "#/definitions/UUIDDatatype" }, - "type" : - { "title" : "Party Type", - "description" : "A category describing the kind of party the object describes.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "person", - "organization" ] } ] }, - "name" : - { "title" : "Party Name", - "description" : "The full name of the party. This is typically the legal name associated with the party.", - "$ref" : "#/definitions/StringDatatype" }, - "short-name" : - { "title" : "Party Short Name", - "description" : "A short common name, abbreviation, or acronym for the party.", - "$ref" : "#/definitions/StringDatatype" }, - "external-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Party External Identifier", - "description" : "An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).", - "type" : "object", - "properties" : - { "scheme" : - { "title" : "External Identifier Schema", - "description" : "Indicates the type of external identifier.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://orcid.org/" ] } ] }, - "id" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "id", - "scheme" ], - "additionalProperties" : false } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:link" } }, - "email-addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:email-address" } }, - "telephone-numbers" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:telephone-number" } }, - "location-uuids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:location-uuid" } }, - "member-of-organizations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Organizational Affiliation", - "description" : "A reference to another party by UUID, typically an organization, that this subject is associated with.", - "$ref" : "#/definitions/UUIDDatatype" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:remarks" } }, - "additionalProperties" : false } ] } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:responsible-party" } }, - "actions" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:action" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:remarks" } }, - "required" : - [ "title", - "last-modified", - "version", - "oscal-version" ], - "additionalProperties" : false }, - "oscal-profile-oscal-metadata:location-uuid" : - { "title" : "Location Universally Unique Identifier Reference", - "description" : "Reference to a location by UUID.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:location-uuid", - "$ref" : "#/definitions/UUIDDatatype" }, - "oscal-profile-oscal-metadata:party-uuid" : - { "title" : "Party Universally Unique Identifier Reference", - "description" : "Reference to a party by UUID.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:party-uuid", - "$ref" : "#/definitions/UUIDDatatype" }, - "oscal-profile-oscal-metadata:role-id" : - { "title" : "Role Identifier Reference", - "description" : "Reference to a role by UUID.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:role-id", - "$ref" : "#/definitions/TokenDatatype" }, - "oscal-profile-oscal-metadata:back-matter" : - { "title" : "Back matter", - "description" : "A collection of resources that may be referenced from within the OSCAL document instance.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:back-matter", - "type" : "object", - "properties" : - { "resources" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Resource", - "description" : "A resource associated with content in the containing document instance. A resource may be directly included in the document using base64 encoding or may point to one or more equivalent internet resources.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Resource Universally Unique Identifier", - "description" : "A unique identifier for a resource.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Resource Title", - "description" : "An optional name given to the resource, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Resource Description", - "description" : "An optional short summary of the resource used to indicate the purpose of the resource.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:property" } }, - "document-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:document-id" } }, - "citation" : - { "title" : "Citation", - "description" : "An optional citation consisting of end note text using structured markup.", - "type" : "object", - "properties" : - { "text" : - { "title" : "Citation Text", - "description" : "A line of citation text.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:link" } } }, - "required" : - [ "text" ], - "additionalProperties" : false }, - "rlinks" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Resource link", - "description" : "A URL-based pointer to an external resource with an optional hash for verification and change detection.", - "type" : "object", - "properties" : - { "href" : - { "title" : "Hypertext Reference", - "description" : "A resolvable URL pointing to the referenced resource.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "media-type" : - { "title" : "Media Type", - "description" : "A label that indicates the nature of a resource, as a data serialization or format.", - "$ref" : "#/definitions/StringDatatype" }, - "hashes" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:hash" } } }, - "required" : - [ "href" ], - "additionalProperties" : false } }, - "base64" : - { "title" : "Base64", - "description" : "A resource encoded using the Base64 alphabet defined by RFC 2045.", - "type" : "object", - "properties" : - { "filename" : - { "title" : "File Name", - "description" : "Name of the file before it was encoded as Base64 to be embedded in a resource. This is the name that will be assigned to the file when the file is decoded.", - "$ref" : "#/definitions/TokenDatatype" }, - "media-type" : - { "title" : "Media Type", - "description" : "A label that indicates the nature of a resource, as a data serialization or format.", - "$ref" : "#/definitions/StringDatatype" }, - "value" : - { "$ref" : "#/definitions/Base64Datatype" } }, - "required" : - [ "value" ], - "additionalProperties" : false }, - "remarks" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:remarks" } }, - "required" : - [ "uuid" ], - "additionalProperties" : false } } }, - "additionalProperties" : false }, - "oscal-profile-oscal-metadata:property" : - { "title" : "Property", - "description" : "An attribute, characteristic, or quality of the containing object expressed as a namespace qualified name/value pair.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:property", - "type" : "object", - "properties" : - { "name" : - { "title" : "Property Name", - "description" : "A textual label, within a namespace, that identifies a specific attribute, characteristic, or quality of the property's containing object.", - "$ref" : "#/definitions/TokenDatatype" }, - "uuid" : - { "title" : "Property Universally Unique Identifier", - "description" : "A unique identifier for a property.", - "$ref" : "#/definitions/UUIDDatatype" }, - "ns" : - { "title" : "Property Namespace", - "description" : "A namespace qualifying the property's name. This allows different organizations to associate distinct semantics with the same name.", - "$ref" : "#/definitions/URIDatatype" }, - "value" : - { "title" : "Property Value", - "description" : "Indicates the value of the attribute, characteristic, or quality.", - "$ref" : "#/definitions/StringDatatype" }, - "class" : - { "title" : "Property Class", - "description" : "A textual label that provides a sub-type or characterization of the property's name.", - "$ref" : "#/definitions/TokenDatatype" }, - "group" : - { "title" : "Property Group", - "description" : "An identifier for relating distinct sets of properties.", - "$ref" : "#/definitions/TokenDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:remarks" } }, - "required" : - [ "name", - "value" ], - "additionalProperties" : false }, - "oscal-profile-oscal-metadata:link" : - { "title" : "Link", - "description" : "A reference to a local or remote resource, that has a specific relation to the containing object.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:link", - "type" : "object", - "properties" : - { "href" : - { "title" : "Hypertext Reference", - "description" : "A resolvable URL reference to a resource.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "rel" : - { "title" : "Link Relation Type", - "description" : "Describes the type of relationship provided by the link's hypertext reference. This can be an indicator of the link's purpose.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "reference" ] } ] }, - "media-type" : - { "title" : "Media Type", - "description" : "A label that indicates the nature of a resource, as a data serialization or format.", - "$ref" : "#/definitions/StringDatatype" }, - "resource-fragment" : - { "title" : "Resource Fragment", - "description" : "In case where the href points to a back-matter/resource, this value will indicate the URI fragment to append to any rlink associated with the resource. This value MUST be URI encoded.", - "$ref" : "#/definitions/StringDatatype" }, - "text" : - { "title" : "Link Text", - "description" : "A textual label to associate with the link, which may be used for presentation in a tool.", - "$ref" : "#/definitions/MarkupLineDatatype" } }, - "required" : - [ "href" ], - "additionalProperties" : false }, - "oscal-profile-oscal-metadata:responsible-party" : - { "title" : "Responsible Party", - "description" : "A reference to a set of persons and/or organizations that have responsibility for performing the referenced role in the context of the containing object.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:responsible-party", - "type" : "object", - "properties" : - { "role-id" : - { "title" : "Responsible Role", - "description" : "A reference to a role performed by a party.", - "$ref" : "#/definitions/TokenDatatype" }, - "party-uuids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:party-uuid" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:remarks" } }, - "required" : - [ "role-id", - "party-uuids" ], - "additionalProperties" : false }, - "oscal-profile-oscal-metadata:action" : - { "title" : "Action", - "description" : "An action applied by a role within a given party to the content.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:action", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Action Universally Unique Identifier", - "description" : "A unique identifier that can be used to reference this defined action elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "date" : - { "title" : "Action Occurrence Date", - "description" : "The date and time when the action occurred.", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "type" : - { "title" : "Action Type", - "description" : "The type of action documented by the assembly, such as an approval.", - "$ref" : "#/definitions/TokenDatatype" }, - "system" : - { "title" : "Action Type System", - "description" : "Specifies the action type system used.", - "$ref" : "#/definitions/URIDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:link" } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:responsible-party" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "type", - "system" ], - "additionalProperties" : false }, - "oscal-profile-oscal-metadata:responsible-role" : - { "title" : "Responsible Role", - "description" : "A reference to a role with responsibility for performing a function relative to the containing object, optionally associated with a set of persons and/or organizations that perform that role.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:responsible-role", - "type" : "object", - "properties" : - { "role-id" : - { "title" : "Responsible Role ID", - "description" : "A human-oriented identifier reference to a role performed.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:link" } }, - "party-uuids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:party-uuid" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:remarks" } }, - "required" : - [ "role-id" ], - "additionalProperties" : false }, - "oscal-profile-oscal-metadata:hash" : - { "title" : "Hash", - "description" : "A representation of a cryptographic digest generated over a resource using a specified hash algorithm.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:hash", - "type" : "object", - "properties" : - { "algorithm" : - { "title" : "Hash algorithm", - "description" : "The digest method by which a hash is derived.", - "anyOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "SHA-224", - "SHA-256", - "SHA-384", - "SHA-512", - "SHA3-224", - "SHA3-256", - "SHA3-384", - "SHA3-512" ] } ] }, - "value" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "value", - "algorithm" ], - "additionalProperties" : false }, - "oscal-profile-oscal-metadata:remarks" : - { "title" : "Remarks", - "description" : "Additional commentary about the containing object.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:remarks", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "oscal-profile-oscal-metadata:published" : - { "title" : "Publication Timestamp", - "description" : "The date and time the document was last made available.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:published", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "oscal-profile-oscal-metadata:last-modified" : - { "title" : "Last Modified Timestamp", - "description" : "The date and time the document was last stored for later retrieval.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:last-modified", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "oscal-profile-oscal-metadata:version" : - { "title" : "Document Version", - "description" : "Used to distinguish a specific revision of an OSCAL document from other previous and future versions.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:version", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-profile-oscal-metadata:oscal-version" : - { "title" : "OSCAL Version", - "description" : "The OSCAL model version the document was authored against and will conform to as valid.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:oscal-version", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-profile-oscal-metadata:email-address" : - { "title" : "Email Address", - "description" : "An email address as defined by RFC 5322 Section 3.4.1.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:email-address", - "$ref" : "#/definitions/EmailAddressDatatype" }, - "oscal-profile-oscal-metadata:telephone-number" : - { "title" : "Telephone Number", - "description" : "A telephone service number as defined by ITU-T E.164.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:telephone-number", - "type" : "object", - "properties" : - { "type" : - { "title" : "type flag", - "description" : "Indicates the type of phone number.", - "anyOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "home", - "office", - "mobile" ] } ] }, - "number" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "number" ], - "additionalProperties" : false }, - "oscal-profile-oscal-metadata:address" : - { "title" : "Address", - "description" : "A postal address for the location.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:address", - "type" : "object", - "properties" : - { "type" : - { "title" : "Address Type", - "description" : "Indicates the type of address.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "home", - "work" ] } ] }, - "addr-lines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:addr-line" } }, - "city" : - { "title" : "City", - "description" : "City, town or geographical region for the mailing address.", - "$ref" : "#/definitions/StringDatatype" }, - "state" : - { "title" : "State", - "description" : "State, province or analogous geographical region for a mailing address.", - "$ref" : "#/definitions/StringDatatype" }, - "postal-code" : - { "title" : "Postal Code", - "description" : "Postal or ZIP code for mailing address.", - "$ref" : "#/definitions/StringDatatype" }, - "country" : - { "title" : "Country Code", - "description" : "The ISO 3166-1 alpha-2 country code for the mailing address.", - "$ref" : "#/definitions/StringDatatype" } }, - "additionalProperties" : false }, - "oscal-profile-oscal-metadata:addr-line" : - { "title" : "Address line", - "description" : "A single line of an address.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:addr-line", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-profile-oscal-metadata:document-id" : - { "title" : "Document Identifier", - "description" : "A document identifier qualified by an identifier scheme.", - "$id" : "#/definitions/oscal-profile-oscal-metadata:document-id", - "type" : "object", - "properties" : - { "scheme" : - { "title" : "Document Identification Scheme", - "description" : "Qualifies the kind of document identifier using a URI. If the scheme is not provided the value of the element will be interpreted as a string of characters.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://www.doi.org/" ] } ] }, - "identifier" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "identifier" ], - "additionalProperties" : false }, - "oscal-profile-oscal-control-common:part" : - { "title" : "Part", - "description" : "An annotated, markup-based textual element of a control's or catalog group's definition, or a child of another part.", - "$id" : "#/definitions/oscal-profile-oscal-control-common:part", - "type" : "object", - "properties" : - { "id" : - { "title" : "Part Identifier", - "description" : "A unique identifier for the part.", - "$ref" : "#/definitions/TokenDatatype" }, - "name" : - { "title" : "Part Name", - "description" : "A textual label that uniquely identifies the part's semantic type, which exists in a value space qualified by the ns.", - "$ref" : "#/definitions/TokenDatatype" }, - "ns" : - { "title" : "Part Namespace", - "description" : "An optional namespace qualifying the part's name. This allows different organizations to associate distinct semantics with the same name.", - "$ref" : "#/definitions/URIDatatype" }, - "class" : - { "title" : "Part Class", - "description" : "An optional textual providing a sub-type or characterization of the part's name, or a category to which the part belongs.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Part Title", - "description" : "An optional name given to the part, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:property" } }, - "prose" : - { "title" : "Part Text", - "description" : "Permits multiple paragraphs, lists, tables etc.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "parts" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:part" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:link" } } }, - "required" : - [ "name" ], - "additionalProperties" : false }, - "oscal-profile-oscal-control-common:parameter" : - { "title" : "Parameter", - "description" : "Parameters provide a mechanism for the dynamic assignment of value(s) in a control.", - "$id" : "#/definitions/oscal-profile-oscal-control-common:parameter", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "id" : - { "title" : "Parameter Identifier", - "description" : "A unique identifier for the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "class" : - { "title" : "Parameter Class", - "description" : "A textual label that provides a characterization of the type, purpose, use or scope of the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "depends-on" : - { "title" : "Depends on", - "description" : "(deprecated) Another parameter invoking this one. This construct has been deprecated and should not be used.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:link" } }, - "label" : - { "title" : "Parameter Label", - "description" : "A short, placeholder name for the parameter, which can be used as a substitute for a value if no value is assigned.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "usage" : - { "title" : "Parameter Usage Description", - "description" : "Describes the purpose and use of a parameter.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "constraints" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:parameter-constraint" } }, - "guidelines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:parameter-guideline" } }, - "values" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:parameter-value" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - - { "properties" : - { "id" : - { "title" : "Parameter Identifier", - "description" : "A unique identifier for the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "class" : - { "title" : "Parameter Class", - "description" : "A textual label that provides a characterization of the type, purpose, use or scope of the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "depends-on" : - { "title" : "Depends on", - "description" : "(deprecated) Another parameter invoking this one. This construct has been deprecated and should not be used.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:link" } }, - "label" : - { "title" : "Parameter Label", - "description" : "A short, placeholder name for the parameter, which can be used as a substitute for a value if no value is assigned.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "usage" : - { "title" : "Parameter Usage Description", - "description" : "Describes the purpose and use of a parameter.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "constraints" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:parameter-constraint" } }, - "guidelines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:parameter-guideline" } }, - "select" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:parameter-selection" }, - "remarks" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:remarks" } }, - "additionalProperties" : false } ] }, - "oscal-profile-oscal-control-common:parameter-constraint" : - { "title" : "Constraint", - "description" : "A formal or informal expression of a constraint or test.", - "$id" : "#/definitions/oscal-profile-oscal-control-common:parameter-constraint", - "type" : "object", - "properties" : - { "description" : - { "title" : "Constraint Description", - "description" : "A textual summary of the constraint to be applied.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "tests" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Constraint Test", - "description" : "A test expression which is expected to be evaluated by a tool.", - "type" : "object", - "properties" : - { "expression" : - { "title" : "Constraint test", - "description" : "A formal (executable) expression of a constraint.", - "$ref" : "#/definitions/StringDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:remarks" } }, - "required" : - [ "expression" ], - "additionalProperties" : false } } }, - "additionalProperties" : false }, - "oscal-profile-oscal-control-common:parameter-guideline" : - { "title" : "Guideline", - "description" : "A prose statement that provides a recommendation for the use of a parameter.", - "$id" : "#/definitions/oscal-profile-oscal-control-common:parameter-guideline", - "type" : "object", - "properties" : - { "prose" : - { "title" : "Guideline Text", - "description" : "Prose permits multiple paragraphs, lists, tables etc.", - "$ref" : "#/definitions/MarkupMultilineDatatype" } }, - "required" : - [ "prose" ], - "additionalProperties" : false }, - "oscal-profile-oscal-control-common:parameter-value" : - { "title" : "Parameter Value", - "description" : "A parameter value or set of values.", - "$id" : "#/definitions/oscal-profile-oscal-control-common:parameter-value", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-profile-oscal-control-common:parameter-selection" : - { "title" : "Selection", - "description" : "Presenting a choice among alternatives.", - "$id" : "#/definitions/oscal-profile-oscal-control-common:parameter-selection", - "type" : "object", - "properties" : - { "how-many" : - { "title" : "Parameter Cardinality", - "description" : "Describes the number of selections that must occur. Without this setting, only one value should be assumed to be permitted.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "one", - "one-or-more" ] } ] }, - "choice" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Choice", - "description" : "A value selection among several such options.", - "$ref" : "#/definitions/MarkupLineDatatype" } } }, - "additionalProperties" : false }, - "oscal-profile-oscal-control-common:include-all" : - { "title" : "Include All", - "description" : "Include all controls from the imported catalog or profile resources.", - "$id" : "#/definitions/oscal-profile-oscal-control-common:include-all", - "type" : "object", - "additionalProperties" : false }, - "oscal-profile-oscal-control-common:with-id" : - { "title" : "Match Controls by Identifier", - "description" : "Selecting a control by its ID given as a literal.", - "$id" : "#/definitions/oscal-profile-oscal-control-common:with-id", - "$ref" : "#/definitions/TokenDatatype" }, - "oscal-profile-oscal-control-common:matching" : - { "title" : "Match Controls by Pattern", - "description" : "Selecting a set of controls by matching their IDs with a wildcard pattern.", - "$id" : "#/definitions/oscal-profile-oscal-control-common:matching", - "type" : "object", - "properties" : - { "pattern" : - { "title" : "Pattern", - "description" : "A glob expression matching the IDs of one or more controls to be selected.", - "$ref" : "#/definitions/StringDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-profile-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - "oscal-profile-oscal-control-common:select-control-by-id" : - { "title" : "Select Control", - "description" : "Select a control or controls from an imported control set.", - "$id" : "#/definitions/oscal-profile-oscal-control-common:select-control-by-id", - "type" : "object", - "properties" : - { "with-child-controls" : - { "title" : "Include Contained Controls with Control", - "description" : "When a control is included, whether its child (dependent) controls are also included.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "yes", - "no" ] } ] }, - "with-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:with-id" } }, - "matching" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-profile-oscal-control-common:matching" } } }, - "additionalProperties" : false }, - "Base64Datatype" : - { "description" : "Binary data encoded using the Base 64 encoding algorithm as defined by RFC4648.", - "type" : "string", - "pattern" : "^[0-9A-Za-z+/]+={0,2}$", - "contentEncoding" : "base64" }, - "BooleanDatatype" : - { "description" : "A binary value that is either: true or false.", - "type" : "boolean" }, - "DateTimeWithTimezoneDatatype" : - { "description" : "A string representing a point in time with a required timezone.", - "type" : "string", - "format" : "date-time", - "pattern" : "^(((2000|2400|2800|(19|2[0-9](0[48]|[2468][048]|[13579][26])))-02-29)|(((19|2[0-9])[0-9]{2})-02-(0[1-9]|1[0-9]|2[0-8]))|(((19|2[0-9])[0-9]{2})-(0[13578]|10|12)-(0[1-9]|[12][0-9]|3[01]))|(((19|2[0-9])[0-9]{2})-(0[469]|11)-(0[1-9]|[12][0-9]|30)))T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])(\\.[0-9]+)?(Z|(-((0[0-9]|1[0-2]):00|0[39]:30)|\\+((0[0-9]|1[0-4]):00|(0[34569]|10):30|(0[58]|12):45)))$" }, - "EmailAddressDatatype" : - { "description" : "An email address string formatted according to RFC 6531.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "type" : "string", - "format" : "email", - "pattern" : "^.+@.+$" } ] }, - "MarkupLineDatatype" : - { "description" : "A single line of Markdown content conformant to the Commonmark specification.", - "type" : "string", - "pattern" : "^[^\n]+$" }, - "MarkupMultilineDatatype" : - { "description" : "A multiple lines of Markdown content conformant to the Commonmark specification.", - "type" : "string" }, - "StringDatatype" : - { "description" : "A non-empty string with leading and trailing whitespace disallowed. Whitespace is: U+9, U+10, U+32 or [ \n\t]+", - "type" : "string", - "pattern" : "^\\S(.*\\S)?$" }, - "TokenDatatype" : - { "description" : "A non-colonized name as defined by XML Schema Part 2: Datatypes Second Edition. https://www.w3.org/TR/xmlschema11-2/#NCName.", - "type" : "string", - "pattern" : "^(\\p{L}|_)(\\p{L}|\\p{N}|[.\\-_])*$" }, - "URIDatatype" : - { "description" : "A universal resource identifier (URI) formatted according to RFC3986.", - "type" : "string", - "format" : "uri", - "pattern" : "^[a-zA-Z][a-zA-Z0-9+\\-.]+:.+$" }, - "URIReferenceDatatype" : - { "description" : "A URI Reference, either a URI or a relative-reference, formatted according to section 4.1 of RFC3986.", - "type" : "string", - "format" : "uri-reference" }, - "UUIDDatatype" : - { "description" : "A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.", - "type" : "string", - "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-[45][0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" } }, - "properties" : - { "$schema" : - { "$ref" : "#/definitions/json-schema-directive" }, - "profile" : - { "$ref" : "#/definitions/oscal-profile-oscal-profile:profile" } }, - "required" : - [ "profile" ], - "additionalProperties" : false } \ No newline at end of file diff --git a/data/schemas/oscal/oscal_ssp_schema.json b/data/schemas/oscal/oscal_ssp_schema.json deleted file mode 100644 index 76c95754..00000000 --- a/data/schemas/oscal/oscal_ssp_schema.json +++ /dev/null @@ -1,2328 +0,0 @@ - - { "$schema" : "http://json-schema.org/draft-07/schema#", - "$id" : "http://csrc.nist.gov/ns/oscal/1.2.2/oscal-ssp-schema.json", - "$comment" : "OSCAL System Security Plan (SSP) Model: JSON Schema", - "type" : "object", - "definitions" : - { "json-schema-directive" : - { "title" : "Schema Directive", - "description" : "A JSON Schema directive to bind a specific schema to its document instance.", - "$id" : "#/definitions/json-schema-directive", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "oscal-ssp-oscal-ssp:system-security-plan" : - { "title" : "System Security Plan (SSP)", - "description" : "A system security plan, such as those described in NIST SP 800-18.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:system-security-plan", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "System Security Plan Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this system security plan (SSP) elsewhere in this or other OSCAL instances. The locally defined UUID of the SSP can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance).This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "metadata" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:metadata" }, - "import-profile" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:import-profile" }, - "system-characteristics" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:system-characteristics" }, - "system-implementation" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:system-implementation" }, - "control-implementation" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:control-implementation" }, - "back-matter" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:back-matter" } }, - "required" : - [ "uuid", - "metadata", - "import-profile", - "system-characteristics", - "system-implementation", - "control-implementation" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-ssp:import-profile" : - { "title" : "Import Profile", - "description" : "Used to import the OSCAL profile representing the system's control baseline.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:import-profile", - "type" : "object", - "properties" : - { "href" : - { "title" : "Profile Reference", - "description" : "A resolvable URL reference to the profile or catalog to use as the system's control baseline.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "href" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-ssp:system-characteristics" : - { "title" : "System Characteristics", - "description" : "Contains the characteristics of the system, such as its name, purpose, and security impact level.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:system-characteristics", - "type" : "object", - "properties" : - { "system-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-implementation-common:system-id" } }, - "system-name" : - { "title" : "System Name - Full", - "description" : "The full name of the system.", - "$ref" : "#/definitions/StringDatatype" }, - "system-name-short" : - { "title" : "System Name - Short", - "description" : "A short name for the system, such as an acronym, that is suitable for display in a data table or summary list.", - "$ref" : "#/definitions/StringDatatype" }, - "description" : - { "title" : "System Description", - "description" : "A summary of the system.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "date-authorized" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:date-authorized" }, - "security-sensitivity-level" : - { "title" : "Security Sensitivity Level", - "description" : "The overall information system sensitivity categorization, such as defined by FIPS-199.", - "$ref" : "#/definitions/StringDatatype" }, - "system-information" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:system-information" }, - "security-impact-level" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:security-impact-level" }, - "status" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:status" }, - "authorization-boundary" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:authorization-boundary" }, - "network-architecture" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:network-architecture" }, - "data-flow" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:data-flow" }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:responsible-party" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "system-ids", - "system-name", - "description", - "system-information", - "status", - "authorization-boundary" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-ssp:system-information" : - { "title" : "System Information", - "description" : "Contains details about all information types that are stored, processed, or transmitted by the system, such as privacy information, and those defined in NIST SP 800-60.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:system-information", - "type" : "object", - "properties" : - { "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "information-types" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Information Type", - "description" : "Contains details about one information type that is stored, processed, or transmitted by the system, such as privacy information, and those defined in NIST SP 800-60.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Information Type Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this information type elsewhere in this or other OSCAL instances. The locally defined UUID of the information type can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "title field", - "description" : "A human readable name for the information type. This title should be meaningful within the context of the system.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Information Type Description", - "description" : "A summary of how this information type is used within the system.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "categorizations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Information Type Categorization", - "description" : "A set of information type identifiers qualified by the given identification system used, such as NIST SP 800-60.", - "type" : "object", - "properties" : - { "system" : - { "title" : "Information Type Identification System", - "description" : "Specifies the information type identification system used.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://doi.org/10.6028/NIST.SP.800-60v2r1" ] } ] }, - "information-type-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Information Type Systematized Identifier", - "description" : "A human-oriented, globally unique identifier qualified by the given identification system used, such as NIST SP 800-60. This identifier has cross-instance scope and can be used to reference this system elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/StringDatatype" } } }, - "required" : - [ "system" ], - "additionalProperties" : false } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "confidentiality-impact" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:impact" }, - "integrity-impact" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:impact" }, - "availability-impact" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:impact" } }, - "required" : - [ "title", - "description" ], - "additionalProperties" : false } } }, - "required" : - [ "information-types" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-ssp:impact" : - { "title" : "Impact Level", - "description" : "The expected level of impact resulting from the described information.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:impact", - "type" : "object", - "properties" : - { "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "base" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:base" }, - "selected" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:selected" }, - "adjustment-justification" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:adjustment-justification" } }, - "required" : - [ "base" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-ssp:base" : - { "title" : "Base Level (Confidentiality, Integrity, or Availability)", - "description" : "The prescribed base (Confidentiality, Integrity, or Availability) security impact level.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:base", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-ssp-oscal-ssp:selected" : - { "title" : "Selected Level (Confidentiality, Integrity, or Availability)", - "description" : "The selected (Confidentiality, Integrity, or Availability) security impact level.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:selected", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-ssp-oscal-ssp:adjustment-justification" : - { "title" : "Adjustment Justification", - "description" : "If the selected security level is different from the base security level, this contains the justification for the change.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:adjustment-justification", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "oscal-ssp-oscal-ssp:security-impact-level" : - { "title" : "Security Impact Level", - "description" : "The overall level of expected impact resulting from unauthorized disclosure, modification, or loss of access to information.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:security-impact-level", - "type" : "object", - "properties" : - { "security-objective-confidentiality" : - { "title" : "Security Objective: Confidentiality", - "description" : "A target-level of confidentiality for the system, based on the sensitivity of information within the system.", - "$ref" : "#/definitions/StringDatatype" }, - "security-objective-integrity" : - { "title" : "Security Objective: Integrity", - "description" : "A target-level of integrity for the system, based on the sensitivity of information within the system.", - "$ref" : "#/definitions/StringDatatype" }, - "security-objective-availability" : - { "title" : "Security Objective: Availability", - "description" : "A target-level of availability for the system, based on the sensitivity of information within the system.", - "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "security-objective-confidentiality", - "security-objective-integrity", - "security-objective-availability" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-ssp:status" : - { "title" : "Status", - "description" : "Describes the operational status of the system.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:status", - "type" : "object", - "properties" : - { "state" : - { "title" : "State", - "description" : "The current operating status.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "operational", - "under-development", - "under-major-modification", - "disposition", - "other" ] } ] }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "state" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-ssp:date-authorized" : - { "title" : "System Authorization Date", - "description" : "The date the system received its authorization.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:date-authorized", - "$ref" : "#/definitions/DateDatatype" }, - "oscal-ssp-oscal-ssp:authorization-boundary" : - { "title" : "Authorization Boundary", - "description" : "A description of this system's authorization boundary, optionally supplemented by diagrams that illustrate the authorization boundary.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:authorization-boundary", - "type" : "object", - "properties" : - { "description" : - { "title" : "Authorization Boundary Description", - "description" : "A summary of the system's authorization boundary.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "diagrams" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:diagram" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "description" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-ssp:diagram" : - { "title" : "Diagram", - "description" : "A graphic that provides a visual representation the system, or some aspect of it.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:diagram", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Diagram ID", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this diagram elsewhere in this or other OSCAL instances. The locally defined UUID of the diagram can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "description" : - { "title" : "Diagram Description", - "description" : "A summary of the diagram.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "caption" : - { "title" : "Caption", - "description" : "A brief caption to annotate the diagram.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "uuid" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-ssp:network-architecture" : - { "title" : "Network Architecture", - "description" : "A description of the system's network architecture, optionally supplemented by diagrams that illustrate the network architecture.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:network-architecture", - "type" : "object", - "properties" : - { "description" : - { "title" : "Network Architecture Description", - "description" : "A summary of the system's network architecture.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "diagrams" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:diagram" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "description" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-ssp:data-flow" : - { "title" : "Data Flow", - "description" : "A description of the logical flow of information within the system and across its boundaries, optionally supplemented by diagrams that illustrate these flows.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:data-flow", - "type" : "object", - "properties" : - { "description" : - { "title" : "Data Flow Description", - "description" : "A summary of the system's data flow.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "diagrams" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:diagram" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "description" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-ssp:system-implementation" : - { "title" : "System Implementation", - "description" : "Provides information as to how the system is implemented.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:system-implementation", - "type" : "object", - "properties" : - { "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "leveraged-authorizations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Leveraged Authorization", - "description" : "A description of another authorized system from which this system inherits capabilities that satisfy security requirements. Another term for this concept is a common control provider.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Leveraged Authorization Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope and can be used to reference this leveraged authorization elsewhere in this or other OSCAL instances. The locally defined UUID of the leveraged authorization can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "title field", - "description" : "A human readable name for the leveraged authorization in the context of the system.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "party-uuid" : - { "title" : "party-uuid field", - "description" : "A machine-oriented identifier reference to the party that manages the leveraged system.", - "$ref" : "#/definitions/UUIDDatatype" }, - "date-authorized" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:date-authorized" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "title", - "party-uuid", - "date-authorized" ], - "additionalProperties" : false } }, - "users" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-implementation-common:system-user" } }, - "components" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-implementation-common:system-component" } }, - "inventory-items" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-implementation-common:inventory-item" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "components" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-ssp:control-implementation" : - { "title" : "Control Implementation", - "description" : "Describes how the system satisfies a set of controls.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:control-implementation", - "type" : "object", - "properties" : - { "description" : - { "title" : "Control Implementation Description", - "description" : "A statement describing important things to know about how this set of control satisfaction documentation is approached.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "set-parameters" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-implementation-common:set-parameter" } }, - "implemented-requirements" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:implemented-requirement" } } }, - "required" : - [ "description", - "implemented-requirements" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-ssp:implemented-requirement" : - { "title" : "Control-based Requirement", - "description" : "Describes how the system satisfies the requirements of an individual control.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:implemented-requirement", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Control Requirement Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control requirement elsewhere in this or other OSCAL instances. The locally defined UUID of the control requirement can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "control-id" : - { "title" : "Control Identifier Reference", - "description" : "A reference to a control with a corresponding id value. When referencing an externally defined control, the Control Identifier Reference must be used in the context of the external / imported OSCAL instance (e.g., uri-reference).", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "set-parameters" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-implementation-common:set-parameter" } }, - "responsible-roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:responsible-role" } }, - "statements" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:statement" } }, - "by-components" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:by-component" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "control-id" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-ssp:statement" : - { "title" : "Specific Control Statement", - "description" : "Identifies which statements within a control are addressed.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:statement", - "type" : "object", - "properties" : - { "statement-id" : - { "title" : "Control Statement Reference", - "description" : "A human-oriented identifier reference to a control statement.", - "$ref" : "#/definitions/TokenDatatype" }, - "uuid" : - { "title" : "Control Statement Reference Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance).", - "$ref" : "#/definitions/UUIDDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "responsible-roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:responsible-role" } }, - "by-components" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:by-component" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "statement-id", - "uuid" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-ssp:by-component" : - { "title" : "Component Control Implementation", - "description" : "Defines how the referenced component implements a set of controls.", - "$id" : "#/definitions/oscal-ssp-oscal-ssp:by-component", - "type" : "object", - "properties" : - { "component-uuid" : - { "title" : "Component Universally Unique Identifier Reference", - "description" : "A machine-oriented identifier reference to the component that is implementing a given control.", - "$ref" : "#/definitions/UUIDDatatype" }, - "uuid" : - { "title" : "By-Component Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this by-component entry elsewhere in this or other OSCAL instances. The locally defined UUID of the by-component entry can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "description" : - { "title" : "Control Implementation Description", - "description" : "An implementation statement that describes how a control or a control statement is implemented within the referenced system component.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "set-parameters" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-implementation-common:set-parameter" } }, - "implementation-status" : - { "$ref" : "#/definitions/oscal-ssp-oscal-implementation-common:implementation-status" }, - "export" : - { "title" : "Export", - "description" : "Identifies content intended for external consumption, such as with leveraged organizations.", - "type" : "object", - "properties" : - { "description" : - { "title" : "Control Implementation Export Description", - "description" : "An implementation statement that describes the aspects of the control or control statement implementation that can be available to another system leveraging this system.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "provided" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Provided Control Implementation", - "description" : "Describes a capability which may be inherited by a leveraging system.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Provided Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this provided entry elsewhere in this or other OSCAL instances. The locally defined UUID of the provided entry can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "description" : - { "title" : "Provided Control Implementation Description", - "description" : "An implementation statement that describes the aspects of the control or control statement implementation that can be provided to another system leveraging this system.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "responsible-roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:responsible-role" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "description" ], - "additionalProperties" : false } }, - "responsibilities" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Control Implementation Responsibility", - "description" : "Describes a control implementation responsibility imposed on a leveraging system.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Responsibility Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this responsibility elsewhere in this or other OSCAL instances. The locally defined UUID of the responsibility can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "provided-uuid" : - { "title" : "Provided UUID", - "description" : "A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system.", - "$ref" : "#/definitions/UUIDDatatype" }, - "description" : - { "title" : "Control Implementation Responsibility Description", - "description" : "An implementation statement that describes the aspects of the control or control statement implementation that a leveraging system must implement to satisfy the control provided by a leveraged system.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "responsible-roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:responsible-role" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "description" ], - "additionalProperties" : false } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - "inherited" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Inherited Control Implementation", - "description" : "Describes a control implementation inherited by a leveraging system.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Inherited Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inherited entry elsewhere in this or other OSCAL instances. The locally defined UUID of the inherited control implementation can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "provided-uuid" : - { "title" : "Provided UUID", - "description" : "A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system.", - "$ref" : "#/definitions/UUIDDatatype" }, - "description" : - { "title" : "Inherited Control Implementation Description", - "description" : "An implementation statement that describes the aspects of a control or control statement implementation that a leveraging system is inheriting from a leveraged system.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "responsible-roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:responsible-role" } } }, - "required" : - [ "uuid", - "description" ], - "additionalProperties" : false } }, - "satisfied" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Satisfied Control Implementation Responsibility", - "description" : "Describes how this system satisfies a responsibility imposed by a leveraged system.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Satisfied Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this satisfied control implementation entry elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "responsibility-uuid" : - { "title" : "Responsibility UUID", - "description" : "A machine-oriented identifier reference to a control implementation that satisfies a responsibility imposed by a leveraged system.", - "$ref" : "#/definitions/UUIDDatatype" }, - "description" : - { "title" : "Satisfied Control Implementation Responsibility Description", - "description" : "An implementation statement that describes the aspects of a control or control statement implementation that a leveraging system is implementing based on a requirement from a leveraged system.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "responsible-roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:responsible-role" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "description" ], - "additionalProperties" : false } }, - "responsible-roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:responsible-role" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "component-uuid", - "uuid", - "description" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-metadata:metadata" : - { "title" : "Document Metadata", - "description" : "Provides information about the containing document, and defines concepts that are shared across the document.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:metadata", - "type" : "object", - "properties" : - { "title" : - { "title" : "Document Title", - "description" : "A name given to the document, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "published" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:published" }, - "last-modified" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:last-modified" }, - "version" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:version" }, - "oscal-version" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:oscal-version" }, - "revisions" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Revision History Entry", - "description" : "An entry in a sequential list of revisions to the containing document, expected to be in reverse chronological order (i.e. latest first).", - "type" : "object", - "properties" : - { "title" : - { "title" : "Document Title", - "description" : "A name given to the document revision, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "published" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:published" }, - "last-modified" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:last-modified" }, - "version" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:version" }, - "oscal-version" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:oscal-version" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "version" ], - "additionalProperties" : false } }, - "document-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:document-id" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Role", - "description" : "Defines a function, which might be assigned to a party in a specific situation.", - "type" : "object", - "properties" : - { "id" : - { "title" : "Role Identifier", - "description" : "A unique identifier for the role.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Role Title", - "description" : "A name given to the role, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "short-name" : - { "title" : "Role Short Name", - "description" : "A short common name, abbreviation, or acronym for the role.", - "$ref" : "#/definitions/StringDatatype" }, - "description" : - { "title" : "Role Description", - "description" : "A summary of the role's purpose and associated responsibilities.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "id", - "title" ], - "additionalProperties" : false } }, - "locations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Location", - "description" : "A physical point of presence, which may be associated with people, organizations, or other concepts within the current or linked OSCAL document.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Location Universally Unique Identifier", - "description" : "A unique ID for the location, for reference.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Location Title", - "description" : "A name given to the location, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "address" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:address" }, - "email-addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:email-address" } }, - "telephone-numbers" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:telephone-number" } }, - "urls" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Location URL", - "description" : "The uniform resource locator (URL) for a web site or other resource associated with the location.", - "$ref" : "#/definitions/URIDatatype" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "uuid" ], - "additionalProperties" : false } }, - "parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Party", - "description" : "An organization or person, which may be associated with roles or other concepts within the current or linked OSCAL document.", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "uuid" : - { "title" : "Party Universally Unique Identifier", - "description" : "A unique identifier for the party.", - "$ref" : "#/definitions/UUIDDatatype" }, - "type" : - { "title" : "Party Type", - "description" : "A category describing the kind of party the object describes.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "person", - "organization" ] } ] }, - "name" : - { "title" : "Party Name", - "description" : "The full name of the party. This is typically the legal name associated with the party.", - "$ref" : "#/definitions/StringDatatype" }, - "short-name" : - { "title" : "Party Short Name", - "description" : "A short common name, abbreviation, or acronym for the party.", - "$ref" : "#/definitions/StringDatatype" }, - "external-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Party External Identifier", - "description" : "An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).", - "type" : "object", - "properties" : - { "scheme" : - { "title" : "External Identifier Schema", - "description" : "Indicates the type of external identifier.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://orcid.org/" ] } ] }, - "id" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "id", - "scheme" ], - "additionalProperties" : false } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "email-addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:email-address" } }, - "telephone-numbers" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:telephone-number" } }, - "addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:address" } }, - "member-of-organizations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Organizational Affiliation", - "description" : "A reference to another party by UUID, typically an organization, that this subject is associated with.", - "$ref" : "#/definitions/UUIDDatatype" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - - { "properties" : - { "uuid" : - { "title" : "Party Universally Unique Identifier", - "description" : "A unique identifier for the party.", - "$ref" : "#/definitions/UUIDDatatype" }, - "type" : - { "title" : "Party Type", - "description" : "A category describing the kind of party the object describes.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "person", - "organization" ] } ] }, - "name" : - { "title" : "Party Name", - "description" : "The full name of the party. This is typically the legal name associated with the party.", - "$ref" : "#/definitions/StringDatatype" }, - "short-name" : - { "title" : "Party Short Name", - "description" : "A short common name, abbreviation, or acronym for the party.", - "$ref" : "#/definitions/StringDatatype" }, - "external-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Party External Identifier", - "description" : "An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).", - "type" : "object", - "properties" : - { "scheme" : - { "title" : "External Identifier Schema", - "description" : "Indicates the type of external identifier.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://orcid.org/" ] } ] }, - "id" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "id", - "scheme" ], - "additionalProperties" : false } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "email-addresses" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:email-address" } }, - "telephone-numbers" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:telephone-number" } }, - "location-uuids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:location-uuid" } }, - "member-of-organizations" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Organizational Affiliation", - "description" : "A reference to another party by UUID, typically an organization, that this subject is associated with.", - "$ref" : "#/definitions/UUIDDatatype" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "additionalProperties" : false } ] } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:responsible-party" } }, - "actions" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:action" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "title", - "last-modified", - "version", - "oscal-version" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-metadata:location-uuid" : - { "title" : "Location Universally Unique Identifier Reference", - "description" : "Reference to a location by UUID.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:location-uuid", - "$ref" : "#/definitions/UUIDDatatype" }, - "oscal-ssp-oscal-metadata:party-uuid" : - { "title" : "Party Universally Unique Identifier Reference", - "description" : "Reference to a party by UUID.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:party-uuid", - "$ref" : "#/definitions/UUIDDatatype" }, - "oscal-ssp-oscal-metadata:role-id" : - { "title" : "Role Identifier Reference", - "description" : "Reference to a role by UUID.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:role-id", - "$ref" : "#/definitions/TokenDatatype" }, - "oscal-ssp-oscal-metadata:back-matter" : - { "title" : "Back matter", - "description" : "A collection of resources that may be referenced from within the OSCAL document instance.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:back-matter", - "type" : "object", - "properties" : - { "resources" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Resource", - "description" : "A resource associated with content in the containing document instance. A resource may be directly included in the document using base64 encoding or may point to one or more equivalent internet resources.", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Resource Universally Unique Identifier", - "description" : "A unique identifier for a resource.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "Resource Title", - "description" : "An optional name given to the resource, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Resource Description", - "description" : "An optional short summary of the resource used to indicate the purpose of the resource.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "document-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:document-id" } }, - "citation" : - { "title" : "Citation", - "description" : "An optional citation consisting of end note text using structured markup.", - "type" : "object", - "properties" : - { "text" : - { "title" : "Citation Text", - "description" : "A line of citation text.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } } }, - "required" : - [ "text" ], - "additionalProperties" : false }, - "rlinks" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Resource link", - "description" : "A URL-based pointer to an external resource with an optional hash for verification and change detection.", - "type" : "object", - "properties" : - { "href" : - { "title" : "Hypertext Reference", - "description" : "A resolvable URL pointing to the referenced resource.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "media-type" : - { "title" : "Media Type", - "description" : "A label that indicates the nature of a resource, as a data serialization or format.", - "$ref" : "#/definitions/StringDatatype" }, - "hashes" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:hash" } } }, - "required" : - [ "href" ], - "additionalProperties" : false } }, - "base64" : - { "title" : "Base64", - "description" : "A resource encoded using the Base64 alphabet defined by RFC 2045.", - "type" : "object", - "properties" : - { "filename" : - { "title" : "File Name", - "description" : "Name of the file before it was encoded as Base64 to be embedded in a resource. This is the name that will be assigned to the file when the file is decoded.", - "$ref" : "#/definitions/TokenDatatype" }, - "media-type" : - { "title" : "Media Type", - "description" : "A label that indicates the nature of a resource, as a data serialization or format.", - "$ref" : "#/definitions/StringDatatype" }, - "value" : - { "$ref" : "#/definitions/Base64Datatype" } }, - "required" : - [ "value" ], - "additionalProperties" : false }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "uuid" ], - "additionalProperties" : false } } }, - "additionalProperties" : false }, - "oscal-ssp-oscal-metadata:property" : - { "title" : "Property", - "description" : "An attribute, characteristic, or quality of the containing object expressed as a namespace qualified name/value pair.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:property", - "type" : "object", - "properties" : - { "name" : - { "title" : "Property Name", - "description" : "A textual label, within a namespace, that identifies a specific attribute, characteristic, or quality of the property's containing object.", - "$ref" : "#/definitions/TokenDatatype" }, - "uuid" : - { "title" : "Property Universally Unique Identifier", - "description" : "A unique identifier for a property.", - "$ref" : "#/definitions/UUIDDatatype" }, - "ns" : - { "title" : "Property Namespace", - "description" : "A namespace qualifying the property's name. This allows different organizations to associate distinct semantics with the same name.", - "$ref" : "#/definitions/URIDatatype" }, - "value" : - { "title" : "Property Value", - "description" : "Indicates the value of the attribute, characteristic, or quality.", - "$ref" : "#/definitions/StringDatatype" }, - "class" : - { "title" : "Property Class", - "description" : "A textual label that provides a sub-type or characterization of the property's name.", - "$ref" : "#/definitions/TokenDatatype" }, - "group" : - { "title" : "Property Group", - "description" : "An identifier for relating distinct sets of properties.", - "$ref" : "#/definitions/TokenDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "name", - "value" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-metadata:link" : - { "title" : "Link", - "description" : "A reference to a local or remote resource, that has a specific relation to the containing object.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:link", - "type" : "object", - "properties" : - { "href" : - { "title" : "Hypertext Reference", - "description" : "A resolvable URL reference to a resource.", - "$ref" : "#/definitions/URIReferenceDatatype" }, - "rel" : - { "title" : "Link Relation Type", - "description" : "Describes the type of relationship provided by the link's hypertext reference. This can be an indicator of the link's purpose.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "reference" ] } ] }, - "media-type" : - { "title" : "Media Type", - "description" : "A label that indicates the nature of a resource, as a data serialization or format.", - "$ref" : "#/definitions/StringDatatype" }, - "resource-fragment" : - { "title" : "Resource Fragment", - "description" : "In case where the href points to a back-matter/resource, this value will indicate the URI fragment to append to any rlink associated with the resource. This value MUST be URI encoded.", - "$ref" : "#/definitions/StringDatatype" }, - "text" : - { "title" : "Link Text", - "description" : "A textual label to associate with the link, which may be used for presentation in a tool.", - "$ref" : "#/definitions/MarkupLineDatatype" } }, - "required" : - [ "href" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-metadata:responsible-party" : - { "title" : "Responsible Party", - "description" : "A reference to a set of persons and/or organizations that have responsibility for performing the referenced role in the context of the containing object.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:responsible-party", - "type" : "object", - "properties" : - { "role-id" : - { "title" : "Responsible Role", - "description" : "A reference to a role performed by a party.", - "$ref" : "#/definitions/TokenDatatype" }, - "party-uuids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:party-uuid" } }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "role-id", - "party-uuids" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-metadata:action" : - { "title" : "Action", - "description" : "An action applied by a role within a given party to the content.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:action", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Action Universally Unique Identifier", - "description" : "A unique identifier that can be used to reference this defined action elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "date" : - { "title" : "Action Occurrence Date", - "description" : "The date and time when the action occurred.", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "type" : - { "title" : "Action Type", - "description" : "The type of action documented by the assembly, such as an approval.", - "$ref" : "#/definitions/TokenDatatype" }, - "system" : - { "title" : "Action Type System", - "description" : "Specifies the action type system used.", - "$ref" : "#/definitions/URIDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:responsible-party" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "type", - "system" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-metadata:responsible-role" : - { "title" : "Responsible Role", - "description" : "A reference to a role with responsibility for performing a function relative to the containing object, optionally associated with a set of persons and/or organizations that perform that role.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:responsible-role", - "type" : "object", - "properties" : - { "role-id" : - { "title" : "Responsible Role ID", - "description" : "A human-oriented identifier reference to a role performed.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "party-uuids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:party-uuid" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "role-id" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-metadata:hash" : - { "title" : "Hash", - "description" : "A representation of a cryptographic digest generated over a resource using a specified hash algorithm.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:hash", - "type" : "object", - "properties" : - { "algorithm" : - { "title" : "Hash algorithm", - "description" : "The digest method by which a hash is derived.", - "anyOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "SHA-224", - "SHA-256", - "SHA-384", - "SHA-512", - "SHA3-224", - "SHA3-256", - "SHA3-384", - "SHA3-512" ] } ] }, - "value" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "value", - "algorithm" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-metadata:remarks" : - { "title" : "Remarks", - "description" : "Additional commentary about the containing object.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:remarks", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "oscal-ssp-oscal-metadata:published" : - { "title" : "Publication Timestamp", - "description" : "The date and time the document was last made available.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:published", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "oscal-ssp-oscal-metadata:last-modified" : - { "title" : "Last Modified Timestamp", - "description" : "The date and time the document was last stored for later retrieval.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:last-modified", - "$ref" : "#/definitions/DateTimeWithTimezoneDatatype" }, - "oscal-ssp-oscal-metadata:version" : - { "title" : "Document Version", - "description" : "Used to distinguish a specific revision of an OSCAL document from other previous and future versions.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:version", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-ssp-oscal-metadata:oscal-version" : - { "title" : "OSCAL Version", - "description" : "The OSCAL model version the document was authored against and will conform to as valid.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:oscal-version", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-ssp-oscal-metadata:email-address" : - { "title" : "Email Address", - "description" : "An email address as defined by RFC 5322 Section 3.4.1.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:email-address", - "$ref" : "#/definitions/EmailAddressDatatype" }, - "oscal-ssp-oscal-metadata:telephone-number" : - { "title" : "Telephone Number", - "description" : "A telephone service number as defined by ITU-T E.164.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:telephone-number", - "type" : "object", - "properties" : - { "type" : - { "title" : "type flag", - "description" : "Indicates the type of phone number.", - "anyOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "home", - "office", - "mobile" ] } ] }, - "number" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "number" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-metadata:address" : - { "title" : "Address", - "description" : "A postal address for the location.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:address", - "type" : "object", - "properties" : - { "type" : - { "title" : "Address Type", - "description" : "Indicates the type of address.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "home", - "work" ] } ] }, - "addr-lines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:addr-line" } }, - "city" : - { "title" : "City", - "description" : "City, town or geographical region for the mailing address.", - "$ref" : "#/definitions/StringDatatype" }, - "state" : - { "title" : "State", - "description" : "State, province or analogous geographical region for a mailing address.", - "$ref" : "#/definitions/StringDatatype" }, - "postal-code" : - { "title" : "Postal Code", - "description" : "Postal or ZIP code for mailing address.", - "$ref" : "#/definitions/StringDatatype" }, - "country" : - { "title" : "Country Code", - "description" : "The ISO 3166-1 alpha-2 country code for the mailing address.", - "$ref" : "#/definitions/StringDatatype" } }, - "additionalProperties" : false }, - "oscal-ssp-oscal-metadata:addr-line" : - { "title" : "Address line", - "description" : "A single line of an address.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:addr-line", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-ssp-oscal-metadata:document-id" : - { "title" : "Document Identifier", - "description" : "A document identifier qualified by an identifier scheme.", - "$id" : "#/definitions/oscal-ssp-oscal-metadata:document-id", - "type" : "object", - "properties" : - { "scheme" : - { "title" : "Document Identification Scheme", - "description" : "Qualifies the kind of document identifier using a URI. If the scheme is not provided the value of the element will be interpreted as a string of characters.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://www.doi.org/" ] } ] }, - "identifier" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "identifier" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-implementation-common:system-component" : - { "title" : "Component", - "description" : "A defined component that can be part of an implemented system.", - "$id" : "#/definitions/oscal-ssp-oscal-implementation-common:system-component", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Component Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "type" : - { "title" : "Component Type", - "description" : "A category describing the purpose of the component.", - "anyOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "enum" : - [ "this-system", - "system", - "interconnection", - "software", - "hardware", - "service", - "policy", - "physical", - "process-procedure", - "plan", - "guidance", - "standard", - "validation", - "network" ] } ] }, - "title" : - { "title" : "Component Title", - "description" : "A human readable name for the system component.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Component Description", - "description" : "A description of the component, including information about its function.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "purpose" : - { "title" : "Purpose", - "description" : "A summary of the technological or business purpose of the component.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "status" : - { "title" : "Status", - "description" : "Describes the operational status of the system component.", - "type" : "object", - "properties" : - { "state" : - { "title" : "State", - "description" : "The operational status.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "under-development", - "operational", - "disposition", - "other" ] } ] }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "state" ], - "additionalProperties" : false }, - "responsible-roles" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:responsible-role" } }, - "protocols" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-implementation-common:protocol" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "type", - "title", - "description", - "status" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-implementation-common:protocol" : - { "title" : "Service Protocol Information", - "description" : "Information about the protocol used to provide a service.", - "$id" : "#/definitions/oscal-ssp-oscal-implementation-common:protocol", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Service Protocol Information Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "name" : - { "title" : "Protocol Name", - "description" : "The common name of the protocol, which should be the appropriate \"service name\" from the IANA Service Name and Transport Protocol Port Number Registry.", - "$ref" : "#/definitions/StringDatatype" }, - "title" : - { "title" : "Protocol Title", - "description" : "A human readable name for the protocol (e.g., Transport Layer Security).", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "port-ranges" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-implementation-common:port-range" } } }, - "additionalProperties" : false }, - "oscal-ssp-oscal-implementation-common:port-range" : - { "title" : "Port Range", - "description" : "Where applicable this is the transport layer protocol port range an IPv4-based or IPv6-based service uses.", - "$id" : "#/definitions/oscal-ssp-oscal-implementation-common:port-range", - "type" : "object", - "properties" : - { "start" : - { "title" : "Start", - "description" : "Indicates the starting port number in a port range for a transport layer protocol", - "$ref" : "#/definitions/NonNegativeIntegerDatatype" }, - "end" : - { "title" : "End", - "description" : "Indicates the ending port number in a port range for a transport layer protocol", - "$ref" : "#/definitions/NonNegativeIntegerDatatype" }, - "transport" : - { "title" : "Transport", - "description" : "Indicates the transport type.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "TCP", - "UDP" ] } ] }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - "oscal-ssp-oscal-implementation-common:implementation-status" : - { "title" : "Implementation Status", - "description" : "Indicates the degree to which the a given control is implemented.", - "$id" : "#/definitions/oscal-ssp-oscal-implementation-common:implementation-status", - "type" : "object", - "properties" : - { "state" : - { "title" : "Implementation State", - "description" : "Identifies the implementation status of the control or control objective.", - "anyOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "implemented", - "partial", - "planned", - "alternative", - "not-applicable" ] } ] }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "state" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-implementation-common:system-user" : - { "title" : "System User", - "description" : "A type of user that interacts with the system based on an associated role.", - "$id" : "#/definitions/oscal-ssp-oscal-implementation-common:system-user", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "User Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "title" : - { "title" : "User Title", - "description" : "A name given to the user, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "short-name" : - { "title" : "User Short Name", - "description" : "A short common name, abbreviation, or acronym for the user.", - "$ref" : "#/definitions/StringDatatype" }, - "description" : - { "title" : "User Description", - "description" : "A summary of the user's purpose within the system.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "role-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:role-id" } }, - "authorized-privileges" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-implementation-common:authorized-privilege" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "uuid" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-implementation-common:authorized-privilege" : - { "title" : "Privilege", - "description" : "Identifies a specific system privilege held by the user, along with an associated description and/or rationale for the privilege.", - "$id" : "#/definitions/oscal-ssp-oscal-implementation-common:authorized-privilege", - "type" : "object", - "properties" : - { "title" : - { "title" : "Privilege Title", - "description" : "A human readable name for the privilege.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "description" : - { "title" : "Privilege Description", - "description" : "A summary of the privilege's purpose within the system.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "functions-performed" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-implementation-common:function-performed" } } }, - "required" : - [ "title", - "functions-performed" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-implementation-common:function-performed" : - { "title" : "Functions Performed", - "description" : "Describes a function performed for a given authorized privilege by this user class.", - "$id" : "#/definitions/oscal-ssp-oscal-implementation-common:function-performed", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-ssp-oscal-implementation-common:inventory-item" : - { "title" : "Inventory Item", - "description" : "A single managed inventory item within the system.", - "$id" : "#/definitions/oscal-ssp-oscal-implementation-common:inventory-item", - "type" : "object", - "properties" : - { "uuid" : - { "title" : "Inventory Item Universally Unique Identifier", - "description" : "A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.", - "$ref" : "#/definitions/UUIDDatatype" }, - "description" : - { "title" : "Inventory Item Description", - "description" : "A summary of the inventory item stating its purpose within the system.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:responsible-party" } }, - "implemented-components" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Implemented Component", - "description" : "The set of components that are implemented in a given system inventory item.", - "type" : "object", - "properties" : - { "component-uuid" : - { "title" : "Component Universally Unique Identifier Reference", - "description" : "A machine-oriented identifier reference to a component that is implemented as part of an inventory item.", - "$ref" : "#/definitions/UUIDDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "responsible-parties" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:responsible-party" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "component-uuid" ], - "additionalProperties" : false } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "uuid", - "description" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-implementation-common:set-parameter" : - { "title" : "Set Parameter Value", - "description" : "Identifies the parameter that will be set by the enclosed value.", - "$id" : "#/definitions/oscal-ssp-oscal-implementation-common:set-parameter", - "type" : "object", - "properties" : - { "param-id" : - { "title" : "Parameter ID", - "description" : "A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context.", - "$ref" : "#/definitions/TokenDatatype" }, - "values" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Parameter Value", - "description" : "A parameter value or set of values.", - "$ref" : "#/definitions/StringDatatype" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "param-id", - "values" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-implementation-common:system-id" : - { "title" : "System Identification", - "description" : "A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document.", - "$id" : "#/definitions/oscal-ssp-oscal-implementation-common:system-id", - "type" : "object", - "properties" : - { "identifier-type" : - { "title" : "Identification System Type", - "description" : "Identifies the identification system from which the provided identifier was assigned.", - "anyOf" : - [ - { "$ref" : "#/definitions/URIDatatype" }, - - { "enum" : - [ "http://fedramp.gov", - "http://fedramp.gov/ns/oscal", - "https://ietf.org/rfc/rfc4122", - "http://ietf.org/rfc/rfc4122", - "http://datatracker.ietf.org/doc/html/rfc4122" ] } ] }, - "id" : - { "$ref" : "#/definitions/StringDatatype" } }, - "required" : - [ "id" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-control-common:part" : - { "title" : "Part", - "description" : "An annotated, markup-based textual element of a control's or catalog group's definition, or a child of another part.", - "$id" : "#/definitions/oscal-ssp-oscal-control-common:part", - "type" : "object", - "properties" : - { "id" : - { "title" : "Part Identifier", - "description" : "A unique identifier for the part.", - "$ref" : "#/definitions/TokenDatatype" }, - "name" : - { "title" : "Part Name", - "description" : "A textual label that uniquely identifies the part's semantic type, which exists in a value space qualified by the ns.", - "$ref" : "#/definitions/TokenDatatype" }, - "ns" : - { "title" : "Part Namespace", - "description" : "An optional namespace qualifying the part's name. This allows different organizations to associate distinct semantics with the same name.", - "$ref" : "#/definitions/URIDatatype" }, - "class" : - { "title" : "Part Class", - "description" : "An optional textual providing a sub-type or characterization of the part's name, or a category to which the part belongs.", - "$ref" : "#/definitions/TokenDatatype" }, - "title" : - { "title" : "Part Title", - "description" : "An optional name given to the part, which may be used by a tool for display and navigation.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "prose" : - { "title" : "Part Text", - "description" : "Permits multiple paragraphs, lists, tables etc.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "parts" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-control-common:part" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } } }, - "required" : - [ "name" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-control-common:parameter" : - { "title" : "Parameter", - "description" : "Parameters provide a mechanism for the dynamic assignment of value(s) in a control.", - "$id" : "#/definitions/oscal-ssp-oscal-control-common:parameter", - "type" : "object", - "anyOf" : - [ - { "properties" : - { "id" : - { "title" : "Parameter Identifier", - "description" : "A unique identifier for the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "class" : - { "title" : "Parameter Class", - "description" : "A textual label that provides a characterization of the type, purpose, use or scope of the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "depends-on" : - { "title" : "Depends on", - "description" : "(deprecated) Another parameter invoking this one. This construct has been deprecated and should not be used.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "label" : - { "title" : "Parameter Label", - "description" : "A short, placeholder name for the parameter, which can be used as a substitute for a value if no value is assigned.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "usage" : - { "title" : "Parameter Usage Description", - "description" : "Describes the purpose and use of a parameter.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "constraints" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-control-common:parameter-constraint" } }, - "guidelines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-control-common:parameter-guideline" } }, - "values" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-control-common:parameter-value" } }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - - { "properties" : - { "id" : - { "title" : "Parameter Identifier", - "description" : "A unique identifier for the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "class" : - { "title" : "Parameter Class", - "description" : "A textual label that provides a characterization of the type, purpose, use or scope of the parameter.", - "$ref" : "#/definitions/TokenDatatype" }, - "depends-on" : - { "title" : "Depends on", - "description" : "(deprecated) Another parameter invoking this one. This construct has been deprecated and should not be used.", - "$ref" : "#/definitions/TokenDatatype" }, - "props" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:property" } }, - "links" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:link" } }, - "label" : - { "title" : "Parameter Label", - "description" : "A short, placeholder name for the parameter, which can be used as a substitute for a value if no value is assigned.", - "$ref" : "#/definitions/MarkupLineDatatype" }, - "usage" : - { "title" : "Parameter Usage Description", - "description" : "Describes the purpose and use of a parameter.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "constraints" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-control-common:parameter-constraint" } }, - "guidelines" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-control-common:parameter-guideline" } }, - "select" : - { "$ref" : "#/definitions/oscal-ssp-oscal-control-common:parameter-selection" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "additionalProperties" : false } ] }, - "oscal-ssp-oscal-control-common:parameter-constraint" : - { "title" : "Constraint", - "description" : "A formal or informal expression of a constraint or test.", - "$id" : "#/definitions/oscal-ssp-oscal-control-common:parameter-constraint", - "type" : "object", - "properties" : - { "description" : - { "title" : "Constraint Description", - "description" : "A textual summary of the constraint to be applied.", - "$ref" : "#/definitions/MarkupMultilineDatatype" }, - "tests" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Constraint Test", - "description" : "A test expression which is expected to be evaluated by a tool.", - "type" : "object", - "properties" : - { "expression" : - { "title" : "Constraint test", - "description" : "A formal (executable) expression of a constraint.", - "$ref" : "#/definitions/StringDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "required" : - [ "expression" ], - "additionalProperties" : false } } }, - "additionalProperties" : false }, - "oscal-ssp-oscal-control-common:parameter-guideline" : - { "title" : "Guideline", - "description" : "A prose statement that provides a recommendation for the use of a parameter.", - "$id" : "#/definitions/oscal-ssp-oscal-control-common:parameter-guideline", - "type" : "object", - "properties" : - { "prose" : - { "title" : "Guideline Text", - "description" : "Prose permits multiple paragraphs, lists, tables etc.", - "$ref" : "#/definitions/MarkupMultilineDatatype" } }, - "required" : - [ "prose" ], - "additionalProperties" : false }, - "oscal-ssp-oscal-control-common:parameter-value" : - { "title" : "Parameter Value", - "description" : "A parameter value or set of values.", - "$id" : "#/definitions/oscal-ssp-oscal-control-common:parameter-value", - "$ref" : "#/definitions/StringDatatype" }, - "oscal-ssp-oscal-control-common:parameter-selection" : - { "title" : "Selection", - "description" : "Presenting a choice among alternatives.", - "$id" : "#/definitions/oscal-ssp-oscal-control-common:parameter-selection", - "type" : "object", - "properties" : - { "how-many" : - { "title" : "Parameter Cardinality", - "description" : "Describes the number of selections that must occur. Without this setting, only one value should be assumed to be permitted.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "one", - "one-or-more" ] } ] }, - "choice" : - { "type" : "array", - "minItems" : 1, - "items" : - { "title" : "Choice", - "description" : "A value selection among several such options.", - "$ref" : "#/definitions/MarkupLineDatatype" } } }, - "additionalProperties" : false }, - "oscal-ssp-oscal-control-common:include-all" : - { "title" : "Include All", - "description" : "Include all controls from the imported catalog or profile resources.", - "$id" : "#/definitions/oscal-ssp-oscal-control-common:include-all", - "type" : "object", - "additionalProperties" : false }, - "oscal-ssp-oscal-control-common:with-id" : - { "title" : "Match Controls by Identifier", - "description" : "Selecting a control by its ID given as a literal.", - "$id" : "#/definitions/oscal-ssp-oscal-control-common:with-id", - "$ref" : "#/definitions/TokenDatatype" }, - "oscal-ssp-oscal-control-common:matching" : - { "title" : "Match Controls by Pattern", - "description" : "Selecting a set of controls by matching their IDs with a wildcard pattern.", - "$id" : "#/definitions/oscal-ssp-oscal-control-common:matching", - "type" : "object", - "properties" : - { "pattern" : - { "title" : "Pattern", - "description" : "A glob expression matching the IDs of one or more controls to be selected.", - "$ref" : "#/definitions/StringDatatype" }, - "remarks" : - { "$ref" : "#/definitions/oscal-ssp-oscal-metadata:remarks" } }, - "additionalProperties" : false }, - "oscal-ssp-oscal-control-common:select-control-by-id" : - { "title" : "Select Control", - "description" : "Select a control or controls from an imported control set.", - "$id" : "#/definitions/oscal-ssp-oscal-control-common:select-control-by-id", - "type" : "object", - "properties" : - { "with-child-controls" : - { "title" : "Include Contained Controls with Control", - "description" : "When a control is included, whether its child (dependent) controls are also included.", - "allOf" : - [ - { "$ref" : "#/definitions/TokenDatatype" }, - - { "enum" : - [ "yes", - "no" ] } ] }, - "with-ids" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-control-common:with-id" } }, - "matching" : - { "type" : "array", - "minItems" : 1, - "items" : - { "$ref" : "#/definitions/oscal-ssp-oscal-control-common:matching" } } }, - "additionalProperties" : false }, - "Base64Datatype" : - { "description" : "Binary data encoded using the Base 64 encoding algorithm as defined by RFC4648.", - "type" : "string", - "pattern" : "^[0-9A-Za-z+/]+={0,2}$", - "contentEncoding" : "base64" }, - "DateDatatype" : - { "description" : "A string representing a 24-hour period with an optional timezone.", - "type" : "string", - "pattern" : "^(((2000|2400|2800|(19|2[0-9](0[48]|[2468][048]|[13579][26])))-02-29)|(((19|2[0-9])[0-9]{2})-02-(0[1-9]|1[0-9]|2[0-8]))|(((19|2[0-9])[0-9]{2})-(0[13578]|10|12)-(0[1-9]|[12][0-9]|3[01]))|(((19|2[0-9])[0-9]{2})-(0[469]|11)-(0[1-9]|[12][0-9]|30)))(Z|(-((0[0-9]|1[0-2]):00|0[39]:30)|\\+((0[0-9]|1[0-4]):00|(0[34569]|10):30|(0[58]|12):45)))?$" }, - "DateTimeWithTimezoneDatatype" : - { "description" : "A string representing a point in time with a required timezone.", - "type" : "string", - "format" : "date-time", - "pattern" : "^(((2000|2400|2800|(19|2[0-9](0[48]|[2468][048]|[13579][26])))-02-29)|(((19|2[0-9])[0-9]{2})-02-(0[1-9]|1[0-9]|2[0-8]))|(((19|2[0-9])[0-9]{2})-(0[13578]|10|12)-(0[1-9]|[12][0-9]|3[01]))|(((19|2[0-9])[0-9]{2})-(0[469]|11)-(0[1-9]|[12][0-9]|30)))T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])(\\.[0-9]+)?(Z|(-((0[0-9]|1[0-2]):00|0[39]:30)|\\+((0[0-9]|1[0-4]):00|(0[34569]|10):30|(0[58]|12):45)))$" }, - "EmailAddressDatatype" : - { "description" : "An email address string formatted according to RFC 6531.", - "allOf" : - [ - { "$ref" : "#/definitions/StringDatatype" }, - - { "type" : "string", - "format" : "email", - "pattern" : "^.+@.+$" } ] }, - "IntegerDatatype" : - { "description" : "A whole number value.", - "type" : "integer" }, - "MarkupLineDatatype" : - { "description" : "A single line of Markdown content conformant to the Commonmark specification.", - "type" : "string", - "pattern" : "^[^\n]+$" }, - "MarkupMultilineDatatype" : - { "description" : "A multiple lines of Markdown content conformant to the Commonmark specification.", - "type" : "string" }, - "NonNegativeIntegerDatatype" : - { "description" : "An integer value that is equal to or greater than 0.", - "allOf" : - [ - { "$ref" : "#/definitions/IntegerDatatype" }, - - { "type" : "number", - "minimum" : 0 } ] }, - "StringDatatype" : - { "description" : "A non-empty string with leading and trailing whitespace disallowed. Whitespace is: U+9, U+10, U+32 or [ \n\t]+", - "type" : "string", - "pattern" : "^\\S(.*\\S)?$" }, - "TokenDatatype" : - { "description" : "A non-colonized name as defined by XML Schema Part 2: Datatypes Second Edition. https://www.w3.org/TR/xmlschema11-2/#NCName.", - "type" : "string", - "pattern" : "^(\\p{L}|_)(\\p{L}|\\p{N}|[.\\-_])*$" }, - "URIDatatype" : - { "description" : "A universal resource identifier (URI) formatted according to RFC3986.", - "type" : "string", - "format" : "uri", - "pattern" : "^[a-zA-Z][a-zA-Z0-9+\\-.]+:.+$" }, - "URIReferenceDatatype" : - { "description" : "A URI Reference, either a URI or a relative-reference, formatted according to section 4.1 of RFC3986.", - "type" : "string", - "format" : "uri-reference" }, - "UUIDDatatype" : - { "description" : "A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.", - "type" : "string", - "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-[45][0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" } }, - "properties" : - { "$schema" : - { "$ref" : "#/definitions/json-schema-directive" }, - "system-security-plan" : - { "$ref" : "#/definitions/oscal-ssp-oscal-ssp:system-security-plan" } }, - "required" : - [ "system-security-plan" ], - "additionalProperties" : false } \ No newline at end of file diff --git a/data/secure-configuration.json b/data/secure-configuration.json new file mode 100644 index 00000000..47c04a92 --- /dev/null +++ b/data/secure-configuration.json @@ -0,0 +1,432 @@ +{ + "schema": "secure-configuration/1", + "$comment": "The Secure Configuration Guide's single source (SCG-CSO-RSC, SCG-ENH-MRG). scripts/build-scg.py publishes it as /.well-known/secure-configuration-guide.json and .md; scripts/check-secure-config.py compares the live settings with `recommended` on every deploy (SCG-ENH-CMP/EXP). Changing a recommended default needs a new version and a changelog entry carrying the new defaults_sha256 (SCG-ENH-VRH); the builder and tests/test_secure_configuration.py fail otherwise. AI-drafted 2026-11-05 from the repository and read-only reads of the live account; for the operator's review.", + "title": "Secure Configuration Guide: samaydlette.com", + "version": "2.4.0", + "obtain_and_use": [ + "Obtain: the guide is public. Human-readable: https://samaydlette.com/.well-known/secure-configuration-guide.md. Machine-readable: https://samaydlette.com/.well-known/secure-configuration-guide.json, signed (secure-configuration-guide.bundle; verify with cosign verify-blob against the deploy workflow's identity, as https://samaydlette.com/trust/ shows). No account or request is needed.", + "Use: each setting names the account that operates it, the recommended value, why it matters, and the API or CLI call that reads and changes it. Compare a system's live values with `recommended`; the operator's own comparison, run on every deploy, is published at https://samaydlette.com/.well-known/security-settings.json (current values, the result per setting, and the decision record that covers any accepted deviation).", + "Change: every setting here is changed only through a reviewed pull request (Terraform for AWS resources, the repository settings for GitHub), never by hand in a console, except the root and owner settings that AWS and GitHub expose only to those accounts, which the operator applies and the deploy then checks." + ], + "accounts": [ + { + "id": "aws-root", + "level": "top-level", + "name": "AWS root user", + "how_named": "The root user of the single AWS account that holds every production resource. It signs in with the account's email address, which is not published. AWS calls it the root user; this guide calls it aws-root.", + "access": "Console only, with MFA, from the operator's own device. No access keys. Used only for the tasks AWS reserves to the root user (account settings, closing the account, restoring IAM administrator access); day-to-day work never uses it.", + "configure": "The settings below under aws-root. AWS exposes the root user's own credentials (MFA device, access keys) only to the root user.", + "operate": "Sign in only for a root-only task, finish it, and sign out. CloudTrail records every root sign-in and action in the account's management trail.", + "decommission": "To retire the system: delete the deployed resources through Terraform, remove the root user's MFA device and any access keys, then close the account from the root user's account settings. Closing the account ends access for every IAM principal in it." + }, + { + "id": "github-owner", + "level": "top-level", + "name": "GitHub repository owner", + "how_named": "The operator's personal GitHub account, which owns the repository sam-aydlette/samaydlette.com and so holds every repository and Actions setting, the environments and their reviewers, and the secrets.", + "access": "github.com sign-in with two-factor authentication. Local git pushes go to branches, never to main; main changes only through pull requests that pass the required checks.", + "configure": "The settings below under github-owner, in the repository's Settings (Branches, Environments, Actions, Code security).", + "operate": "Review and merge pull requests; approve each production deploy in the prod environment. The deploy's checks re-read the environment and branch settings every run.", + "decommission": "Transfer the repository with GitHub's transfer flow, or archive it. Before either, remove the AWS OIDC trust (infrastructure/bootstrap) so no workflow can assume an AWS role afterwards." + }, + { + "id": "aws-operator-user", + "level": "privileged", + "name": "Operator IAM user", + "how_named": "The one IAM user that belongs to the IAM group `operators`. It is the operator's day-to-day administrative identity (bootstrap applies, read-only verification). Its user name is not published; this guide calls it aws-operator-user.", + "access": "AWS CLI with an access key; the user also has an MFA device, and no console password.", + "configure": "Membership of the `operators` group gives its permissions; the settings below under aws-operator-user.", + "operate": "Used for the bootstrap stack (applied by hand) and read-only checks. Production changes to the main stack go through the reviewed deploy, never this user.", + "decommission": "Deactivate and delete its access keys, remove its MFA device and group membership, then delete the user." + }, + { + "id": "ci-roles", + "level": "privileged", + "name": "CI roles (deploy, plan, nightly, package maintenance, incident reports)", + "how_named": "Five IAM roles that GitHub Actions assumes through OIDC: the deploy role (aws_iam_role.deploy), the plan role (aws_iam_role.plan), the nightly evidence role (aws_iam_role.evidence_nightly), the package maintenance role (aws_iam_role.package_maintenance) and the incident reports role (aws_iam_role.incident_reports), all in infrastructure/bootstrap. No long-lived credential exists for any of them.", + "access": "Only through GitHub's OIDC token, and only for the workflow subjects in each role's trust policy.", + "configure": "infrastructure/bootstrap (operator-applied, reviewed). The settings below under ci-roles.", + "operate": "The deploy role exists only inside an approved prod deploy; the plan role is read-only; the nightly role writes only .well-known/vdr-* objects; the package maintenance role writes only the certification package objects; the incident reports role writes only .well-known/incident-* objects.", + "decommission": "Delete the roles and the OIDC provider from infrastructure/bootstrap and apply." + }, + { + "id": "cognito-admin", + "level": "privileged", + "name": "Silk Reeling user-pool administration", + "how_named": "Administration of the Silk Reeling Cognito user pool (aws_cognito_user_pool.silk_reeling): creating users, and the pool's sign-in policy. Only the deploy role (through Terraform) and the operator user can administer it; app users cannot sign themselves up.", + "access": "Through Terraform in the reviewed deploy, or the operator user's CLI for creating an app user.", + "configure": "infrastructure/cognito.tf. The settings below under cognito-admin.", + "operate": "Create an app user with `aws cognito-idp admin-create-user`; the user sets a password meeting the policy and enrolls TOTP MFA at first sign-in.", + "decommission": "Delete the app users, then remove the pool from Terraform." + } + ], + "settings": [ + { + "id": "aws-root.mfa-enabled", + "account": "aws-root", + "operable_by": "aws-root only", + "setting": "MFA on the root user", + "recommended": true, + "implication": "Without MFA, the root user's password alone controls the whole account, including closing it.", + "read": "aws iam get-account-summary (SummaryMap.AccountMFAEnabled)", + "change": "Root user console: Security credentials, Assign MFA device.", + "check": "aws-root-mfa-enabled" + }, + { + "id": "aws-root.mfa-phishing-resistant", + "account": "aws-root", + "operable_by": "aws-root only", + "setting": "Root user MFA is phishing-resistant (FIDO2 security key or passkey)", + "recommended": true, + "implication": "A TOTP code can be relayed by a phishing site in real time; a FIDO2 credential is bound to the AWS sign-in origin and cannot be.", + "read": "aws iam list-virtual-mfa-devices --assignment-status Assigned (a root entry means virtual TOTP)", + "change": "Root user console: Security credentials, Assign MFA device, Passkey or security key; then remove the virtual device.", + "check": "aws-root-mfa-type", + "accepted_deviation": "DEC-150" + }, + { + "id": "aws-root.access-keys", + "account": "aws-root", + "operable_by": "aws-root only", + "setting": "Root user access keys", + "recommended": 0, + "implication": "A root access key is an unrestricted, long-lived credential that no IAM policy can limit.", + "read": "aws iam get-account-summary (SummaryMap.AccountAccessKeysPresent)", + "change": "Root user console: Security credentials, Access keys, Delete.", + "check": "aws-root-access-keys" + }, + { + "id": "aws-account.password-policy", + "account": "aws-root", + "operable_by": "aws-root and aws-operator-user", + "setting": "Account password policy for IAM users", + "recommended": {"MinimumPasswordLength": {"at_least": 14}, "RequireSymbols": true, "RequireNumbers": true, + "RequireUppercaseCharacters": true, "RequireLowercaseCharacters": true, + "PasswordReusePrevention": {"at_least": 24}, "MaxPasswordAge": {"at_most": 90}}, + "implication": "Applies to any IAM user given a console password; weaker values make guessed or reused passwords work.", + "read": "aws iam get-account-password-policy", + "change": "aws iam update-account-password-policy", + "check": "aws-account-password-policy" + }, + { + "id": "aws-account.s3-block-public-access", + "account": "aws-root", + "operable_by": "aws-root and aws-operator-user", + "setting": "Account-level S3 Block Public Access", + "recommended": {"BlockPublicAcls": true, "IgnorePublicAcls": true, "BlockPublicPolicy": true, "RestrictPublicBuckets": true}, + "implication": "Stops any bucket in the account being made public by an ACL or bucket policy, whatever its own settings. The site is served through CloudFront's origin access control, never a public bucket.", + "read": "aws s3control get-public-access-block --account-id <account>", + "change": "aws s3control put-public-access-block --account-id <account> --public-access-block-configuration ...", + "check": "aws-account-s3-bpa" + }, + { + "id": "aws-account.iam-users", + "account": "aws-root", + "operable_by": "aws-root and aws-operator-user", + "setting": "IAM users other than the operator user hold no write permission and no console password", + "recommended": 0, + "implication": "Every other IAM user is a read-only collector (an AWS read-only or SecurityAudit policy) or has no permissions and no credentials. A second user with write access would be an unreviewed administrative path.", + "read": "aws iam list-users; for each: list-groups-for-user, list-attached-user-policies, list-user-policies, get-login-profile", + "change": "aws iam detach-user-policy / remove-user-from-group / delete-login-profile (operator user)", + "check": "aws-iam-users" + }, + { + "id": "github.prod-reviewer", + "account": "github-owner", + "operable_by": "github-owner only", + "setting": "The prod environment requires a reviewer before a deploy", + "recommended": {"at_least": 1}, + "implication": "Without a reviewer, a merged change would apply Terraform to production unattended.", + "read": "GET /repos/{owner}/{repo}/environments", + "change": "Repository Settings, Environments, prod, Required reviewers (or PUT /repos/{owner}/{repo}/environments/prod)", + "check": "github-prod-reviewer" + }, + { + "id": "github.nightly-main-only", + "account": "github-owner", + "operable_by": "github-owner only", + "setting": "The evidence-nightly environment deploys only from main", + "recommended": ["main"], + "implication": "The nightly role writes published evidence unattended; another branch must not be able to use it.", + "read": "GET /repos/{owner}/{repo}/environments/evidence-nightly/deployment-branch-policies", + "change": "Repository Settings, Environments, evidence-nightly, Deployment branches", + "check": "github-nightly-branches" + }, + { + "id": "github.main-required-checks", + "account": "github-owner", + "operable_by": "github-owner only", + "setting": "main requires the four gate checks, for administrators too", + "recommended": {"required": ["OPA Compliance Check", "Security Scan", "Unit tests (pytest + opa test)", "scn-tag"], "enforced_for": "everyone"}, + "implication": "These checks are the policy, test, scanner and change-classification gates; without them a change could reach main unchecked.", + "read": "GET /repos/{owner}/{repo}/branches/main", + "change": "Repository Settings, Branches, main (or PUT /repos/{owner}/{repo}/branches/main/protection)", + "check": "github-main-checks" + }, + { + "id": "github.owner-2fa", + "account": "github-owner", + "operable_by": "github-owner only", + "setting": "Two-factor authentication on the owner account, no classic personal access tokens", + "recommended": true, + "implication": "The owner account can change every setting above and the workflows that hold AWS trust.", + "read": "Not readable by any token the pipeline holds (GitHub exposes a user's two-factor setting and tokens only to that user). Stated once by the operator as a configuration fact (DEC-151); nothing recurs.", + "change": "github.com Settings, Password and authentication; Developer settings, Personal access tokens.", + "check": "attested", + "attested_by": "DEC-151" + }, + { + "id": "github.workflow-token-permissions", + "account": "github-owner", + "operable_by": "github-owner only", + "setting": "Every workflow declares its token permissions; none grants write-all", + "recommended": {"undeclared": [], "write_all": []}, + "implication": "A workflow that declares its permissions never falls back to the repository's default token permissions, so the repository-level Actions setting (readable only by an administrator) governs nothing; write-all would give every step every write.", + "read": "The top-level permissions block of each file in .github/workflows/ (the repository the run checked out)", + "change": "Edit the workflow's permissions block, through a reviewed pull request", + "check": "github-workflow-permissions" + }, + { + "id": "github.rulesets", + "account": "github-owner", + "operable_by": "github-owner only", + "setting": "No repository ruleset lets anyone bypass it", + "recommended": {"with_bypass": 0}, + "implication": "A ruleset with bypass actors would let those actors skip the protections it adds; main's required checks are branch protection, compared above.", + "read": "GET /repos/{owner}/{repo}/rulesets", + "change": "Repository Settings, Rules, Rulesets", + "check": "github-rulesets" + }, + { + "id": "github.dependabot-alerts", + "account": "github-owner", + "operable_by": "github-owner only", + "setting": "Dependabot alerts are enabled", + "recommended": true, + "implication": "Dependabot alerts are one of the detection feeds the vulnerability report reads; off, a known-vulnerable dependency raises no alert.", + "read": "GET /repos/{owner}/{repo}/dependabot/alerts with the token the detection feeds use (403 means disabled)", + "change": "Repository Settings, Code security, Dependabot alerts", + "check": "github-dependabot-alerts" + }, + { + "id": "github.dependabot-updates", + "account": "github-owner", + "operable_by": "github-owner only", + "setting": "Dependabot version updates cover the Lambda's and the accessibility tool's npm packages, the GitHub Actions and the main Terraform stack", + "recommended": ["github-actions:/", "npm:/infrastructure/lambda", "npm:/tools/a11y", "terraform:/infrastructure"], + "implication": "These are the dependency manifests in this repository that reach production or the pipeline; an entry removed stops update pull requests for it (docs/supply-chain.md).", + "read": ".github/dependabot.yml (the repository the run checked out)", + "change": "Edit .github/dependabot.yml, through a reviewed pull request", + "check": "github-dependabot-updates" + }, + { + "id": "aws-operator-user.mfa-enabled", + "account": "aws-operator-user", + "operable_by": "aws-operator-user and aws-root", + "setting": "MFA on the operator user", + "recommended": true, + "implication": "The operator user can administer IAM; its access key alone must not be enough.", + "read": "aws iam list-mfa-devices --user-name <operator user>", + "change": "aws iam enable-mfa-device", + "check": "operator-mfa-enabled" + }, + { + "id": "aws-operator-user.mfa-phishing-resistant", + "account": "aws-operator-user", + "operable_by": "aws-operator-user and aws-root", + "setting": "Operator user MFA is phishing-resistant (FIDO2 security key or passkey)", + "recommended": true, + "implication": "As for the root user: a TOTP code can be relayed by a phishing site; a FIDO2 credential cannot.", + "read": "aws iam list-virtual-mfa-devices --assignment-status Assigned (an entry for the user means virtual TOTP)", + "change": "IAM console: the user's Security credentials, Assign MFA device, Passkey or security key.", + "check": "operator-mfa-type", + "accepted_deviation": "DEC-150" + }, + { + "id": "aws-operator-user.console-password", + "account": "aws-operator-user", + "operable_by": "aws-operator-user and aws-root", + "setting": "No console password on the operator user", + "recommended": false, + "implication": "The operator works from the CLI; a console password would add a second sign-in path to protect.", + "read": "aws iam get-login-profile --user-name <operator user> (NoSuchEntity means none)", + "change": "aws iam delete-login-profile", + "check": "operator-console-password" + }, + { + "id": "aws-operator-user.access-keys", + "account": "aws-operator-user", + "operable_by": "aws-operator-user and aws-root", + "setting": "At most one active access key, no older than 90 days", + "recommended": {"active": {"at_most": 1}, "oldest_age_days": {"at_most": 90}}, + "implication": "A long-lived key is the operator user's standing credential; rotating it every 90 days bounds the life of a leaked key.", + "read": "aws iam list-access-keys --user-name <operator user>", + "change": "aws iam create-access-key, then update-access-key --status Inactive and delete-access-key for the old one", + "check": "operator-access-keys" + }, + { + "id": "ci-roles.deploy-trust", + "account": "ci-roles", + "operable_by": "aws-operator-user (bootstrap apply)", + "setting": "The deploy role trusts only this repository's prod environment", + "recommended": ["repo:sam-aydlette/samaydlette.com:environment:prod"], + "implication": "The prod environment requires a reviewer, so deploy credentials exist only inside an approved deploy.", + "read": "aws iam get-role (AssumeRolePolicyDocument, token.actions.githubusercontent.com:sub)", + "change": "infrastructure/bootstrap/main.tf, data.aws_iam_policy_document.trust; operator-applied", + "check": "role-trust-deploy" + }, + { + "id": "ci-roles.plan-trust", + "account": "ci-roles", + "operable_by": "aws-operator-user (bootstrap apply)", + "setting": "The read-only plan role trusts only this repository's pull requests and main", + "recommended": ["repo:sam-aydlette/samaydlette.com:pull_request", "repo:sam-aydlette/samaydlette.com:ref:refs/heads/main"], + "implication": "Pull request runs get read-only credentials, never deploy permissions.", + "read": "aws iam get-role (AssumeRolePolicyDocument)", + "change": "infrastructure/bootstrap/plan-role.tf; operator-applied", + "check": "role-trust-plan" + }, + { + "id": "ci-roles.nightly-trust", + "account": "ci-roles", + "operable_by": "aws-operator-user (bootstrap apply)", + "setting": "The nightly role trusts only this repository's evidence-nightly environment", + "recommended": ["repo:sam-aydlette/samaydlette.com:environment:evidence-nightly"], + "implication": "The unattended write path stays limited to the one environment that deploys only from main.", + "read": "aws iam get-role (AssumeRolePolicyDocument)", + "change": "infrastructure/bootstrap/evidence-nightly.tf; operator-applied", + "check": "role-trust-nightly" + }, + { + "id": "ci-roles.maintenance-trust", + "account": "ci-roles", + "operable_by": "aws-operator-user (bootstrap apply)", + "setting": "The package maintenance role trusts only this repository's package-maintenance environment", + "recommended": [ + "repo:sam-aydlette/samaydlette.com:environment:package-maintenance" + ], + "implication": "The unattended package write path stays limited to the one environment that deploys only from main.", + "read": "aws iam get-role (AssumeRolePolicyDocument)", + "change": "infrastructure/bootstrap/package-maintenance.tf; operator-applied", + "check": "role-trust-maintenance" + }, + { + "id": "ci-roles.incident-trust", + "account": "ci-roles", + "operable_by": "aws-operator-user (bootstrap apply)", + "setting": "The incident reports role trusts only this repository's incident-reports environment, and its prod environment so the deploy can prove the role can be assumed", + "recommended": [ + "repo:sam-aydlette/samaydlette.com:environment:incident-reports", + "repo:sam-aydlette/samaydlette.com:environment:prod" + ], + "implication": "The incident write path stays limited to two environments that deploy only from main: incident-reports, which publishes, and prod, whose deploy step 'Incident report publisher role can be assumed' (scripts/check-incident-role.py) proves the role works before the SDR states it.", + "read": "aws iam get-role (AssumeRolePolicyDocument)", + "change": "infrastructure/bootstrap/incident-reports.tf; operator-applied", + "check": "role-trust-incident" + }, + { + "id": "ci-roles.maintenance-publish-scope", + "account": "ci-roles", + "operable_by": "aws-operator-user (bootstrap apply)", + "setting": "The package maintenance role may put exactly the certification package objects its workflow publishes", + "recommended": [ + ".well-known/certification-package-overview.bundle", + ".well-known/certification-package-overview.json", + ".well-known/certification-package-overview.md", + ".well-known/certification-package-overview.view.md", + ".well-known/ocr-issue-*", + ".well-known/ocr-issues.bundle", + ".well-known/ocr-issues.json", + ".well-known/ocr-issues.view.md", + ".well-known/ongoing-certification-report.bundle", + ".well-known/ongoing-certification-report.json", + ".well-known/ongoing-certification-report.md", + ".well-known/ongoing-certification-report.view.md", + ".well-known/quarterly-review-*", + ".well-known/quarterly-review.ics", + ".well-known/quarterly-reviews.bundle", + ".well-known/quarterly-reviews.json", + ".well-known/quarterly-reviews.view.md", + ".well-known/security-decision-record.bundle", + ".well-known/security-decision-record.json", + ".well-known/security-decision-record.json.intoto.jsonl", + ".well-known/security-decision-record.md", + ".well-known/security-decision-record.view.md", + ".well-known/security-review-*", + ".well-known/security-reviews.bundle", + ".well-known/security-reviews.json", + ".well-known/security-reviews.view.md", + ".well-known/snapshot-*", + ".well-known/snapshots/*" + ], + "implication": "The unattended maintainer can write nothing else, and it can write every file it republishes, readable views included, so a run never fails half-published.", + "read": "aws iam get-role-policy (package-maintenance-publish; s3:PutObject resources, bucket removed)", + "change": "infrastructure/bootstrap/package-maintenance.tf, local.package_maintenance_keys; operator-applied", + "check": "role-scope-maintenance" + }, + { + "id": "ci-roles.nightly-audit-reads", + "account": "ci-roles", + "operable_by": "aws-operator-user (bootstrap apply)", + "setting": "The evidence nightly role may read CloudTrail's event history for the automated audit-log review, and nothing more in that policy", + "recommended": ["cloudtrail:LookupEvents"], + "implication": "The nightly's audit-log review (scripts/audit-log-review.py, KSI-MLA-RVL) can read the write events it judges; it is a read on the unattended path and adds no write.", + "read": "aws iam get-role-policy (evidence-nightly-audit-log-review; allowed actions)", + "change": "infrastructure/bootstrap/evidence-nightly.tf, aws_iam_role_policy.evidence_nightly_audit_reads; operator-applied", + "check": "role-reads-nightly" + }, + { + "id": "cognito-admin.sign-in-policy", + "account": "cognito-admin", + "operable_by": "ci-roles (Terraform) and aws-operator-user", + "setting": "Silk Reeling user pool: MFA required, admin-created users only, 14-character passwords with every character class", + "recommended": {"MfaConfiguration": "ON", "AllowAdminCreateUserOnly": true, "MinimumLength": {"at_least": 14}, + "RequireUppercase": true, "RequireLowercase": true, "RequireNumbers": true, "RequireSymbols": true}, + "implication": "App users cannot sign themselves up, and every app user signs in with a strong password and TOTP MFA.", + "read": "aws cognito-idp describe-user-pool --user-pool-id <pool>", + "change": "infrastructure/cognito.tf (reviewed deploy)", + "check": "cognito-pool-policy" + } + ], + "changelog": [ + { + "version": "2.0.0", + "date": "2026-11-05", + "changes": [ + "First machine-readable release, replacing the prose guide in docs/policies.", + "Root and operator MFA stated as it is: virtual TOTP, an accepted deviation from the phishing-resistant default (DEC-150).", + "Deployer access-key rotation removed: CI uses OIDC roles and has no access key.", + "The retired Silk Reeling shared credential removed: app users sign in through Cognito with MFA.", + "Added the account-level settings, the operator user, the CI roles and the user-pool administration, each with the call that reads and changes it." + ], + "defaults_sha256": "a21ebfa28dc9e0b8b12a2f0029e163d782d92848c422b85702bec6de65352727" + }, + {"version": "2.1.0", "date": "2026-11-06", "changes": ["Added the repository settings the pipeline can read and now compares on every deploy and every night: workflow token permissions, rulesets, Dependabot alerts and Dependabot version updates.", "The owner's two-factor setting is stated once as a configuration fact (DEC-151, amended); no recurring review."], "defaults_sha256": "375b980783ca802f16b31bba794c5f42e56169ec0eb76b993053a6687ebec3c3"}, + { + "version": "2.2.0", + "date": "2026-11-06", + "changes": [ + "Added the trust settings of the package maintenance and incident reports roles, compared on every deploy like the other CI roles.", + "Added the package maintenance role's write scope: exactly the objects its workflow publishes, the readable views included." + ], + "defaults_sha256": "cdbe9f627541a32b68cfec16be8782b5f352d05b8d239dc7c6ac5be08d6daad1" + }, + { + "version": "2.3.0", + "date": "2026-11-06", + "changes": [ + "The incident reports role's recommended trust adds the prod environment. The bootstrap already grants it so the deploy can prove the role can be assumed; the guide listed incident-reports only, so the deploy's comparison would have reported a deviation." + ], + "defaults_sha256": "436268d507aa31417d5b92c2615e8106f393bbbbba879375cbda4121201f89af" + }, + { + "version": "2.4.0", + "date": "2026-11-06", + "changes": [ + "The package maintenance role's write scope adds the Annual Security Review: its index (security-reviews.json, view and signature) and each held review (security-review-*).", + "Added the evidence nightly role's audit-log read: cloudtrail:LookupEvents, for the automated audit-log review (DEC-195), compared on every deploy like the maintainer's scope." + ], + "defaults_sha256": "ca8968b522af43b3736f1444d0f93de75f434a9277b4f20d150aabec2717be57" + } + ] +} diff --git a/data/sources/sp800-171r2-security-reqs.csv b/data/sources/sp800-171r2-security-reqs.csv deleted file mode 100644 index 6e6a8d2f..00000000 --- a/data/sources/sp800-171r2-security-reqs.csv +++ /dev/null @@ -1,124 +0,0 @@ -Family,Basic/Derived Security Requirement,Identifier,Sort-As, Security Requirement,Discussion -Access Control,Basic,3.1.1,03.01.01,"Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems).","Access control policies (e.g., identity- or role-based policies, control matrices, and cryptography) control access between active entities or subjects (i.e., users or processes acting on behalf of users) and passive entities or objects (e.g., devices, files, records, and domains) in systems. Access enforcement mechanisms can be employed at the application and service level to provide increased information security. Other systems include systems internal and external to the organization. This requirement focuses on account management for systems and applications. The definition of and enforcement of access authorizations, other than those determined by account type (e.g., privileged verses non-privileged) are addressed in requirement 3.1.2." -Access Control,Basic,3.1.2,03.01.02,Limit system access to the types of transactions and functions that authorized users are permitted to execute.,"Organizations may choose to define access privileges or other attributes by account, by type of account, or a combination of both. System account types include individual, shared, group, system, anonymous, guest, emergency, developer, manufacturer, vendor, and temporary. Other attributes required for authorizing access include restrictions on time-of-day, day-of-week, and point-of-origin. In defining other account attributes, organizations consider system-related requirements (e.g., system upgrades scheduled maintenance,) and mission or business requirements, (e.g., time zone differences, customer requirements, remote access to support travel requirements)." -Access Control,Derived,3.1.3,03.01.03,Control the flow of CUI in accordance with approved authorizations.,"Information flow control regulates where information can travel within a system and between systems (versus who can access the information) and without explicit regard to subsequent accesses to that information. Flow control restrictions include the following: keeping export-controlled information from being transmitted in the clear to the Internet; blocking outside traffic that claims to be from within the organization; restricting requests to the Internet that are not from the internal web proxy server; and limiting information transfers between organizations based on data structures and content. Organizations commonly use information flow control policies and enforcement mechanisms to control the flow of information between designated sources and destinations (e.g., networks, individuals, and devices) within systems and between interconnected systems. Flow control is based on characteristics of the information or the information path. Enforcement occurs in boundary protection devices (e.g., gateways, routers, guards, encrypted tunnels, firewalls) that employ rule sets or establish configuration settings that restrict system services, provide a packet-filtering capability based on header information, or message-filtering capability based on message content (e.g., implementing key word searches or using document characteristics). Organizations also consider the trustworthiness of filtering and inspection mechanisms (i.e., hardware, firmware, and software components) that are critical to information flow enforcement. Transferring information between systems representing different security domains with different security policies introduces risk that such transfers violate one or more domain security policies. In such situations, information owners or stewards provide guidance at designated policy enforcement points between interconnected systems. Organizations consider mandating specific architectural solutions when required to enforce specific security policies. Enforcement includes: prohibiting information transfers between interconnected systems (i.e., allowing access only); employing hardware mechanisms to enforce one-way information flows; and implementing trustworthy regrading mechanisms to reassign security attributes and security labels." -Access Control,Derived,3.1.4,03.01.04,Separate the duties of individuals to reduce the risk of malevolent activity without collusion.,"Separation of duties addresses the potential for abuse of authorized privileges and helps to reduce the risk of malevolent activity without collusion. Separation of duties includes dividing mission functions and system support functions among different individuals or roles; conducting system support functions with different individuals (e.g., configuration management, quality assurance and testing, system management, programming, and network security); and ensuring that security personnel administering access control functions do not also administer audit functions. Because separation of duty violations can span systems and application domains, organizations consider the entirety of organizational systems and system components when developing policy on separation of duties." -Access Control,Derived,3.1.5,03.01.05,"Employ the principle of least privilege, including for specific security functions and privileged accounts.","Organizations employ the principle of least privilege for specific duties and authorized accesses for users and processes. The principle of least privilege is applied with the goal of authorized privileges no higher than necessary to accomplish required organizational missions or business functions. Organizations consider the creation of additional processes, roles, and system accounts as necessary, to achieve least privilege. Organizations also apply least privilege to the development, implementation, and operation of organizational systems. Security functions include establishing system accounts, setting events to be logged, setting intrusion detection parameters, and configuring access authorizations (i.e., permissions, privileges). Privileged accounts, including super user accounts, are typically described as system administrator for various types of commercial off-the-shelf operating systems. Restricting privileged accounts to specific personnel or roles prevents day-to-day users from having access to privileged information or functions. Organizations may differentiate in the application of this requirement between allowed privileges for local accounts and for domain accounts provided organizations retain the ability to control system configurations for key security parameters and as otherwise necessary to sufficiently mitigate risk." -Access Control,Derived,3.1.6,03.01.06,Use non-privileged accounts or roles when accessing nonsecurity functions,This requirement limits exposure when operating from within privileged accounts or roles. The inclusion of roles addresses situations where organizations implement access control policies such as role-based access control and where a change of role provides the same degree of assurance in the change of access authorizations for the user and all processes acting on behalf of the user as would be provided by a change between a privileged and non-privileged account. -Access Control,Derived,3.1.7,03.01.07,Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.,"Privileged functions include establishing system accounts, performing system integrity checks, conducting patching operations, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. Note that this requirement represents a condition to be achieved by the definition of authorized privileges in 3.1.2. Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Logging the use of privileged functions is one way to detect such misuse, and in doing so, help mitigate the risk from insider threats and the advanced persistent threat." -Access Control,Derived,3.1.8,03.01.08,Limit unsuccessful logon attempts.,"This requirement applies regardless of whether the logon occurs via a local or network connection. Due to the potential for denial of service, automatic lockouts initiated by systems are, in most cases, temporary and automatically release after a predetermined period established by the organization (i.e., a delay algorithm). If a delay algorithm is selected, organizations may employ different algorithms for different system components based on the capabilities of the respective components. Responses to unsuccessful logon attempts may be implemented at the operating system and application levels." -Access Control,Derived,3.1.9,03.01.09,Provide privacy and security notices consistent with applicable CUI rules.,"System use notifications can be implemented using messages or warning banners displayed before individuals log in to organizational systems. System use notifications are used only for access via logon interfaces with human users and are not required when such human interfaces do not exist. Based on a risk assessment, organizations consider whether a secondary system use notification is needed to access applications or other system resources after the initial network logon. Where necessary, posters or other printed materials may be used in lieu of an automated system banner. Organizations consult with the Office of General Counsel for legal review and approval of warning banner content" -Access Control,Derived,3.1.10,03.01.10,Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity,"Session locks are temporary actions taken when users stop work and move away from the immediate vicinity of the system but do not want to log out because of the temporary nature of their absences. Session locks are implemented where session activities can be determined, typically at the operating system level (but can also be at the application level). Session locks are not an acceptable substitute for logging out of the system, for example, if organizations require users to log out at the end of the workday. Pattern-hiding displays can include static or dynamic images, for example, patterns used with screen savers, photographic images, solid colors, clock, battery life indicator, or a blank screen, with the additional caveat that none of the images convey controlled unclassified information." -Access Control,Derived,3.1.11,03.01.11,Terminate (automatically) a user session after a defined condition.,"This requirement addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., disconnecting from the network). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. Session termination terminates all processes associated with a user’s logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated. Conditions or trigger events requiring automatic session termination can include organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on system use" -Access Control,Derived,3.1.12,03.01.12,Monitor and control remote access sessions.,"Remote access is access to organizational systems by users (or processes acting on behalf of users) communicating through external networks (e.g., the Internet). Remote access methods include dial-up, broadband, and wireless. Organizations often employ encrypted virtual private networks (VPNs) to enhance confidentiality over remote connections. The use of encrypted VPNs does not make the access non-remote; however, the use of VPNs, when adequately provisioned with appropriate control (e.g., employing encryption techniques for confidentiality protection), may provide sufficient assurance to the organization that it can effectively treat such connections as internal networks. VPNs with encrypted tunnels can affect the capability to adequately monitor network communications traffic for malicious code. Automated monitoring and control of remote access sessions allows organizations to detect cyber-attacks and help to ensure ongoing compliance with remote access policies by auditing connection activities of remote users on a variety of system components (e.g., servers, workstations, notebook computers, smart phones, and tablets). [SP 800-46], [SP 800-77], and [SP 800-113] provide guidance on secure remote access and virtual private networks." -Access Control,Derived,3.1.13,03.01.13,Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.,Cryptographic standards include FIPS-validated cryptography and NSA-approved cryptography. See [NIST CRYPTO]; [NIST CAVP]; [NIST CMVP]; National Security Agency Cryptographic Standards. -Access Control,Derived,3.1.14,03.01.14,Route remote access via managed access control points.,"Routing remote access through managed access control points enhances explicit, organizational control over such connections, reducing the susceptibility to unauthorized access to organizational systems resulting in the unauthorized disclosure of CUI." -Access Control,Derived,3.1.15,03.01.15,Authorize remote execution of privileged commands and remote access to security-relevant information.,"A privileged command is a human-initiated (interactively or via a process operating on behalf of the human) command executed on a system involving the control, monitoring, or administration of the system including security functions and associated security-relevant information. Security-relevant information is any information within the system that can potentially impact the operation of security functions or the provision of security services in a manner that could result in failure to enforce the system security policy or maintain isolation of code and data. Privileged commands give individuals the ability to execute sensitive, security-critical, or security-relevant system functions. Controlling such access from remote locations helps to ensure that unauthorized individuals are not able to execute such commands freely with the potential to do serious or catastrophic damage to organizational systems. Note that the ability to affect the integrity of the system is considered security-relevant as that could enable the means to by-pass security functions although not directly impacting the function itself." -Access Control,Derived,3.1.16,03.01.16,Authorize wireless access prior to allowing such connections,Establishing usage restrictions and configuration/connection requirements for wireless access to the system provides criteria for organizations to support wireless access authorization decisions. Such restrictions and requirements reduce the susceptibility to unauthorized access to the system through wireless technologies. Wireless networks use authentication protocols which provide credential protection and mutual authentication. [SP 800-97] provides guidance on secure wireless networks. -Access Control,Derived,3.1.17,03.01.17,Protect wireless access using authentication and encryption,Organizations authenticate individuals and devices to help protect wireless access to the system. Special attention is given to the wide variety of devices that are part of the Internet of Things with potential wireless access to organizational systems. See [NIST CRYPTO]. -Access Control,Derived,3.1.18,03.01.18,Control connection of mobile devices.,"A mobile device is a computing device that has a small form factor such that it can easily be carried by a single individual; is designed to operate without a physical connection (e.g., wirelessly transmit or receive information); possesses local, non-removable or removable data storage; and includes a self-contained power source. Mobile devices may also include voice communication capabilities, on-board sensors that allow the device to capture information, or built-in features for synchronizing local data with remote locations. Examples of mobile devices include smart phones, e-readers, and tablets. Due to the large variety of mobile devices with different technical characteristics and capabilities, organizational restrictions may vary for the different types of devices. Usage restrictions and implementation guidance for mobile devices include: device identification and authentication; configuration management; implementation of mandatory protective software (e.g., malicious code detection, firewall); scanning devices for malicious code; updating virus protection software; scanning for critical software updates and patches; conducting primary operating system (and possibly other resident software) integrity checks; and disabling unnecessary hardware (e.g., wireless, infrared). The need to provide adequate security for mobile devices goes beyond this requirement. Many controls for mobile devices are reflected in other CUI security requirements. [SP 800-124] provides guidance on mobile device security." -Access Control,Derived,3.1.19,03.01.19,Encrypt CUI on mobile devices and mobile computing platforms.[23] ,"Organizations can employ full-device encryption or container-based encryption to protect the confidentiality of CUI on mobile devices and computing platforms. Container-based encryption provides a more fine-grained approach to the encryption of data and information including encrypting selected data structures such as files, records, or fields. See [NIST CRYPTO]. - -[23] Mobile devices and computing platforms include, for example, smartphones and tablets." -Access Control,Derived,3.1.20,03.01.20,Verify and control/limit connections to and use of external systems.,"External systems are systems or components of systems for which organizations typically have no direct supervision and authority over the application of security requirements and controls or the determination of the effectiveness of implemented controls on those systems. External systems include personally owned systems, components, or devices and privately-owned computing and communications devices resident in commercial or public facilities. This requirement also addresses the use of external systems for the processing, storage, or transmission of CUI, including accessing cloud services (e.g., infrastructure as a service, platform as a service, or software as a service) from organizational systems. Organizations establish terms and conditions for the use of external systems in accordance with organizational security policies and procedures. Terms and conditions address as a minimum, the types of applications that can be accessed on organizational systems from external systems. If terms and conditions with the owners of external systems cannot be established, organizations may impose restrictions on organizational personnel using those external systems. This requirement recognizes that there are circumstances where individuals using external systems (e.g., contractors, coalition partners) need to access organizational systems. In those situations, organizations need confidence that the external systems contain the necessary controls so as not to compromise, damage, or otherwise harm organizational systems. Verification that the required controls have been effectively implemented can be achieved by third-party, independent assessments, attestations, or other means, depending on the assurance or confidence level required by organizations. Note that while “external” typically refers to outside of the organization’s direct supervision and authority, that is not always the case. Regarding the protection of CUI across an organization, the organization may have systems that process CUI and others that do not. And among the systems that process CUI there are likely access restrictions for CUI that apply between systems. Therefore, from the perspective of a given system, other systems within the organization may be considered “external"" to that system." -Access Control,Derived,3.1.21,03.01.21,Limit use of portable storage devices on external systems.,"Limits on the use of organization-controlled portable storage devices in external systems include complete prohibition of the use of such devices or restrictions on how the devices may be used and under what conditions the devices may be used. Note that while “external” typically refers to outside of the organization’s direct supervision and authority, that is not always the case. Regarding the protection of CUI across an organization, the organization may have systems that process CUI and others that do not. Among the systems that process CUI there are likely access restrictions for CUI that apply between systems. Therefore, from the perspective of a given system, other systems within the organization may be considered “external"" to that system." -Access Control,Derived,3.1.22,03.01.22,Control CUI posted or processed on publicly accessible systems.,"In accordance with laws, Executive Orders, directives, policies, regulations, or standards, the public is not authorized access to nonpublic information (e.g., information protected under the Privacy Act, CUI, and proprietary information). This requirement addresses systems that are controlled by the organization and accessible to the public, typically without identification or authentication. Individuals authorized to post CUI onto publicly accessible systems are designated. The content of information is reviewed prior to posting onto publicly accessible systems to ensure that nonpublic information is not included." -Awareness and Training,Basic,3.2.1,03.02.01,"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.",Organizations determine the content and frequency of security awareness training and security awareness techniques based on the specific organizational requirements and the systems to which personnel have authorized access. The content includes a basic understanding of the need for information security and user actions to maintain security and to respond to suspected security incidents. The content also addresses awareness of the need for operations security. Security awareness techniques include: formal training; offering supplies inscribed with security reminders; generating email advisories or notices from organizational officials; displaying logon screen messages; displaying security awareness posters; and conducting information security awareness events. [SP 800-50] provides guidance on security awareness and training programs. -Awareness and Training,Basic,3.2.2,03.02.02,Ensure that personnel are trained to carry out their assigned information security-related duties and responsibilities.,"Organizations determine the content and frequency of security training based on the assigned duties, roles, and responsibilities of individuals and the security requirements of organizations and the systems to which personnel have authorized access. In addition, organizations provide system developers, enterprise architects, security architects, acquisition/procurement officials, software developers, system developers, systems integrators, system/network administrators, personnel conducting configuration management and auditing activities, personnel performing independent verification and validation, security assessors, and other personnel having access to system-level software, security-related technical training specifically tailored for their assigned duties. Comprehensive role-based training addresses management, operational, and technical roles and responsibilities covering physical, personnel, and technical controls. Such training can include policies, procedures, tools, and artifacts for the security roles defined. Organizations also provide the training necessary for individuals to carry out their responsibilities related to operations and supply chain security within the context of organizational information security programs. [SP 800-181] provides guidance on role-based information security training in the workplace. [SP 800-161] provides guidance on supply chain risk management." -Awareness and Training,Derived,3.2.3,03.02.03,Provide security awareness training on recognizing and reporting potential indicators of insider threat.,"Potential indicators and possible precursors of insider threat include behaviors such as: inordinate, long-term job dissatisfaction; attempts to gain access to information that is not required for job performance; unexplained access to financial resources; bullying or sexual harassment of fellow employees; workplace violence; and other serious violations of the policies, procedures, directives, rules, or practices of organizations. Security awareness training includes how to communicate employee and management concerns regarding potential indicators of insider threat through appropriate organizational channels in accordance with established organizational policies and procedures. Organizations may consider tailoring insider threat awareness topics to the role (e.g., training for managers may be focused on specific changes in behavior of team members, while training for employees may be focused on more general observations)." -Audit and Accountability,Basic,3.3.1,03.03.01,"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","An event is any observable occurrence in a system, which includes unlawful or unauthorized system activity. Organizations identify event types for which a logging functionality is needed as those events which are significant and relevant to the security of systems and the environments in which those systems operate to meet specific and ongoing auditing needs. Event types can include password changes, failed logons or failed accesses related to systems, administrative privilege usage, or third-party credential usage. In determining event types that require logging, organizations consider the monitoring and auditing appropriate for each of the CUI security requirements. Monitoring and auditing requirements can be balanced with other system needs. For example, organizations may determine that systems must have the capability to log every file access both successful and unsuccessful, but not activate that capability except for specific circumstances due to the potential burden on system performance. Audit records can be generated at various levels of abstraction, including at the packet level as information traverses the network. Selecting the appropriate level of abstraction is a critical aspect of an audit logging capability and can facilitate the identification of root causes to problems. Organizations consider in the definition of event types, the logging necessary to cover related events such as the steps in distributed, transaction-based processes (e.g., processes that are distributed across multiple organizations) and actions that occur in service-oriented or cloud-based architectures. Audit record content that may be necessary to satisfy this requirement includes time stamps, source and destination addresses, user or process identifiers, event descriptions, success or fail indications, filenames involved, and access control or flow control rules invoked. Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the system after the event occurred). Detailed information that organizations may consider in audit records includes full text recording of privileged commands or the individual identities of group account users. Organizations consider limiting the additional audit log information to only that information explicitly needed for specific audit requirements. This facilitates the use of audit trails and audit logs by not including information that could potentially be misleading or could make it more difficult to locate information of interest. Audit logs are reviewed and analyzed as often as needed to provide important information to organizations to facilitate risk-based decision making. [SP 800-92] provides guidance on security log management." -Audit and Accountability,Basic,3.3.2,03.03.02,"Ensure that the actions of individual system users can be uniquely traced to those users, so they can be held accountable for their actions.","This requirement ensures that the contents of the audit record include the information needed to link the audit event to the actions of an individual to the extent feasible. Organizations consider logging for traceability including results from monitoring of account usage, remote access, wireless connectivity, mobile device connection, communications at system boundaries, configuration settings, physical access, nonlocal maintenance, use of maintenance tools, temperature and humidity, equipment delivery and removal, system component inventory, use of mobile code, and use of Voice over Internet Protocol (VoIP)." -Audit and Accountability,Derived,3.3.3,03.03.03,Review and update logged events.,The intent of this requirement is to periodically re-evaluate which logged events will continue to be included in the list of events to be logged. The event types that are logged by organizations may change over time. Reviewing and updating the set of logged event types periodically is necessary to ensure that the current set remains necessary and sufficient. -Audit and Accountability,Derived,3.3.4,03.03.04,Alert in the event of an audit logging process failure.,"Audit logging process failures include software and hardware errors, failures in the audit record capturing mechanisms, and audit record storage capacity being reached or exceeded. This requirement applies to each audit record data storage repository (i.e., distinct system component where audit records are stored), the total audit record storage capacity of organizations (i.e., all audit record data storage repositories combined), or both." -Audit and Accountability,Derived,3.3.5,03.03.05,"Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity.","Correlating audit record review, analysis, and reporting processes helps to ensure that they do not operate independently, but rather collectively. Regarding the assessment of a given organizational system, the requirement is agnostic as to whether this correlation is applied at the system level or at the organization level across all systems." -Audit and Accountability,Derived,3.3.6,03.03.06,Provide audit record reduction and report generation to support on-demand analysis and reporting.,"Audit record reduction is a process that manipulates collected audit information and organizes such information in a summary format that is more meaningful to analysts. Audit record reduction and report generation capabilities do not always emanate from the same system or organizational entities conducting auditing activities. Audit record reduction capability can include, for example, modern data mining techniques with advanced data filters to identify anomalous behavior in audit records. The report generation capability provided by the system can help generate customizable reports. Time ordering of audit records can be a significant issue if the granularity of the time stamp in the record is insufficient." -Audit and Accountability,Derived,3.3.7,03.03.07,Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records,"Internal system clocks are used to generate time stamps, which include date and time. Time is expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. The granularity of time measurements refers to the degree of synchronization between system clocks and reference clocks, for example, clocks synchronizing within hundreds of milliseconds or within tens of milliseconds. Organizations may define different time granularities for different system components. Time service can also be critical to other security capabilities such as access control and identification and authentication, depending on the nature of the mechanisms used to support those capabilities. This requirement provides uniformity of time stamps for systems with multiple system clocks and systems connected over a network. See [IETF 5905]. " -Audit and Accountability,Derived,3.3.8,03.03.08,"Protect audit information and audit logging tools from unauthorized access, modification, and deletion.","Audit information includes all information (e.g., audit records, audit log settings, and audit reports) needed to successfully audit system activity. Audit logging tools are those programs and devices used to conduct audit and logging activities. This requirement focuses on the technical protection of audit information and limits the ability to access and execute audit logging tools to authorized individuals. Physical protection of audit information is addressed by media protection and physical and environmental protection requirements." -Audit and Accountability,Derived,3.3.9,03.03.09,Limit management of audit logging functionality to a subset of privileged users.,"Individuals with privileged access to a system and who are also the subject of an audit by that system, may affect the reliability of audit information by inhibiting audit logging activities or modifying audit records. This requirement specifies that privileged access be further defined between audit-related privileges and other privileges, thus limiting the users with audit-related privileges" -Configuration Management,Basic,3.4.1,03.04.01,"Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles.","Baseline configurations are documented, formally reviewed, and agreed-upon specifications for systems or configuration items within those systems. Baseline configurations serve as a basis for future builds, releases, and changes to systems. Baseline configurations include information about system components (e.g., standard software packages installed on workstations, notebook computers, servers, network components, or mobile devices; current version numbers and update and patch information on operating systems and applications; and configuration settings and parameters), network topology, and the logical placement of those components within the system architecture. Baseline configurations of systems also reflect the current enterprise architecture. Maintaining effective baseline configurations requires creating new baselines as organizational systems change over time. Baseline configuration maintenance includes reviewing and updating the baseline configuration when changes are made based on security risks and deviations from the established baseline configuration. Organizations can implement centralized system component inventories that include components from multiple organizational systems. In such situations, organizations ensure that the resulting inventories include system-specific information required for proper component accountability (e.g., system association, system owner). Information deemed necessary for effective accountability of system components includes hardware inventory specifications, software license information, software version numbers, component owners, and for networked components or devices, machine names and network addresses. Inventory specifications include manufacturer, device type, model, serial number, and physical location. [SP 800-128] provides guidance on security-focused configuration management. " -Configuration Management,Basic,3.4.2,03.04.02,Establish and enforce security configuration settings for information technology products employed in organizational systems.,"Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture or functionality of the system. Information technology products for which security-related configuration settings can be defined include mainframe computers, servers, workstations, input and output devices (e.g., scanners, copiers, and printers), network components (e.g., firewalls, routers, gateways, voice and data switches, wireless access points, network appliances, sensors), operating systems, middleware, and applications. Security parameters are those parameters impacting the security state of systems including the parameters required to satisfy other security requirements. Security parameters include: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, and remote connections. Organizations establish organization-wide configuration settings and subsequently derive specific configuration settings for systems. The established settings become part of the systems configuration baseline. Common secure configurations (also referred to as security configuration checklists, lockdown and hardening guides, security reference guides, security technical implementation guides) provide recognized, standardized, and established benchmarks that stipulate secure configuration settings for specific information technology platforms/products and instructions for configuring those system components to meet operational requirements. Common secure configurations can be developed by a variety of organizations including information technology product developers, manufacturers, vendors, consortia, academia, industry, federal agencies, and other organizations in the public and private sectors. [SP 800-70] and [SP 800-128] provide guidance on security configuration settings." -Configuration Management,Derived,3.4.3,03.04.03,"Track, review, approve or disapprove, and log changes to organizational systems.","Tracking, reviewing, approving/disapproving, and logging changes is called configuration change control. Configuration change control for organizational systems involves the systematic proposal, justification, implementation, testing, review, and disposition of changes to the systems, including system upgrades and modifications. Configuration change control includes changes to baseline configurations for components and configuration items of systems, changes to configuration settings for information technology products (e.g., operating systems, applications, firewalls, routers, and mobile devices), unscheduled and unauthorized changes, and changes to remediate vulnerabilities. Processes for managing configuration changes to systems include Configuration Control Boards or Change Advisory Boards that review and approve proposed changes to systems. For new development systems or systems undergoing major upgrades, organizations consider including representatives from development organizations on the Configuration Control Boards or Change Advisory Boards. Audit logs of changes include activities before and after changes are made to organizational systems and the activities required to implement such changes. [SP 800-128] provides guidance on configuration change control." -Configuration Management,Derived,3.4.4,03.04.04,Analyze the security impact of changes prior to implementation.,"Organizational personnel with information security responsibilities (e.g., system administrators, system security officers, system security managers, and systems security engineers) conduct security impact analyses. Individuals conducting security impact analyses possess the necessary skills and technical expertise to analyze the changes to systems and the associated security ramifications. Security impact analysis may include reviewing security plans to understand security requirements and reviewing system design documentation to understand the implementation of controls and how specific changes might affect the controls. Security impact analyses may also include risk assessments to better understand the impact of the changes and to determine if additional controls are required. [SP 800-128] provides guidance on configuration change control and security impact analysis." -Configuration Management,Derived,3.4.5,03.04.05,"Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.","Any changes to the hardware, software, or firmware components of systems can potentially have significant effects on the overall security of the systems. Therefore, organizations permit only qualified and authorized individuals to access systems for purposes of initiating changes, including upgrades and modifications. Access restrictions for change also include software libraries. Access restrictions include physical and logical access control requirements, workflow automation, media libraries, abstract layers (e.g., changes implemented into external interfaces rather than directly into systems), and change windows (e.g., changes occur only during certain specified times). In addition to security concerns, commonly-accepted due diligence for configuration management includes access restrictions as an essential part in ensuring the ability to effectively manage the configuration. [SP 800-128] provides guidance on configuration change control." -Configuration Management,Derived,3.4.6,03.04.06,Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities.,"Systems can provide a wide variety of functions and services. Some of the functions and services routinely provided by default, may not be necessary to support essential organizational missions, functions, or operations. It is sometimes convenient to provide multiple services from single system components. However, doing so increases risk over limiting the services provided by any one component. Where feasible, organizations limit component functionality to a single function per component. Organizations review functions and services provided by systems or components of systems, to determine which functions and services are candidates for elimination. Organizations disable unused or unnecessary physical and logical ports and protocols to prevent unauthorized connection of devices, transfer of information, and tunneling. Organizations can utilize network scanning tools, intrusion detection and prevention systems, and end-point protections such as firewalls and host-based intrusion detection systems to identify and prevent the use of prohibited functions, ports, protocols, and services." -Configuration Management,Derived,3.4.7,03.04.07,"Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.","Restricting the use of nonessential software (programs) includes restricting the roles allowed to approve program execution; prohibiting auto-execute; program blacklisting and whitelisting; or restricting the number of program instances executed at the same time. The organization makes a security-based determination which functions, ports, protocols, and/or services are restricted. Bluetooth, File Transfer Protocol (FTP), and peer-to-peer networking are examples of protocols organizations consider preventing the use of, restricting, or disabling." -Configuration Management,Derived,3.4.8,03.04.08,"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.","The process used to identify software programs that are not authorized to execute on systems is commonly referred to as blacklisting. The process used to identify software programs that are authorized to execute on systems is commonly referred to as whitelisting. Whitelisting is the stronger of the two policies for restricting software program execution. In addition to whitelisting, organizations consider verifying the integrity of whitelisted software programs using, for example, cryptographic checksums, digital signatures, or hash functions. Verification of whitelisted software can occur either prior to execution or at system startup. [SP 800-167] provides guidance on application whitelisting." -Configuration Management,Derived,3.4.9,03.04.09,Control and monitor user-installed software.,"Users can install software in organizational systems if provided the necessary privileges. To maintain control over the software installed, organizations identify permitted and prohibited actions regarding software installation through policies. Permitted software installations include updates and security patches to existing software and applications from organization-approved “app stores.” Prohibited software installations may include software with unknown or suspect pedigrees or software that organizations consider potentially malicious. The policies organizations select governing user-installed software may be organization-developed or provided by some external entity. Policy enforcement methods include procedural methods, automated methods, or both." -Identification and Authentication,Basic,3.5.1,03.05.01,"Identify system users, processes acting on behalf of users, and devices.","Common device identifiers include Media Access Control (MAC), Internet Protocol (IP) addresses, or device-unique token identifiers. Management of individual identifiers is not applicable to shared system accounts. Typically, individual identifiers are the user names associated with the system accounts assigned to those individuals. Organizations may require unique identification of individuals in group accounts or for detailed accountability of individual activity. In addition, this requirement addresses individual identifiers that are not necessarily associated with system accounts. Organizational devices requiring identification may be defined by type, by device, or by a combination of type/device. [SP 800-63-3] provides guidance on digital identities. " -Identification and Authentication,Basic,3.5.2,03.05.02,"Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems.","Individual authenticators include the following: passwords, key cards, cryptographic devices, and one-time password devices. Initial authenticator content is the actual content of the authenticator, for example, the initial password. In contrast, the requirements about authenticator content include the minimum password length. Developers ship system components with factory default authentication credentials to allow for initial installation and configuration. Default authentication credentials are often well known, easily discoverable, and present a significant security risk. Systems support authenticator management by organization-defined settings and restrictions for various authenticator characteristics including minimum password length, validation time window for time synchronous one-time tokens, and number of allowed rejections during the verification stage of biometric authentication. Authenticator management includes issuing and revoking, when no longer needed, authenticators for temporary access such as that required for remote maintenance. Device authenticators include certificates and passwords. [SP 800-63-3] provides guidance on digital identities." -Identification and Authentication,Derived,3.5.3,03.05.03,Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.[24] [25]. ,"Multifactor authentication requires the use of two or more different factors to authenticate. The factors are defined as something you know (e.g., password, personal identification number [PIN]); something you have (e.g., cryptographic identification device, token); or something you are (e.g., biometric). Multifactor authentication solutions that feature physical authenticators include hardware authenticators providing time-based or challenge-response authenticators and smart cards. In addition to authenticating users at the system level (i.e., at logon), organizations may also employ authentication mechanisms at the application level, when necessary, to provide increased information security. Access to organizational systems is defined as local access or network access. Local access is any access to organizational systems by users (or processes acting on behalf of users) where such access is obtained by direct connections without the use of networks. Network access is access to systems by users (or processes acting on behalf of users) where such access is obtained through network connections (i.e., nonlocal accesses). Remote access is a type of network access that involves communication through external networks. The use of encrypted virtual private networks for connections between organization-controlled and non-organization controlled endpoints may be treated as internal networks with regard to protecting the confidentiality of information. [SP 800-63-3] provides guidance on digital identities. - -[24] Multifactor authentication requires two or more different factors to achieve authentication. The factors include: something you know (e.g., password/PIN); something you have (e.g., cryptographic identification device, token); or something you are (e.g., biometric). The requirement for multifactor authentication should not be interpreted as requiring federal Personal Identity Verification (PIV) card or Department of Defense Common Access Card (CAC)-like solutions. A variety of multifactor solutions (including those with replay resistance) using tokens and biometrics are commercially available. Such solutions may employ hard tokens (e.g., smartcards, key fobs, or dongles) or soft tokens to store user credentials. -[25] Local access is any access to a system by a user (or process acting on behalf of a user) communicating through a direct connection without the use of a network. Network access is any access to a system by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, Internet)." -Identification and Authentication,Derived,3.5.4,03.05.04,Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts.,Authentication processes resist replay attacks if it is impractical to successfully authenticate by recording or replaying previous authentication messages. Replay-resistant techniques include protocols that use nonces or challenges such as time synchronous or challenge-response one-time authenticators. [SP 800-63-3] provides guidance on digital identities. -Identification and Authentication,Derived,3.5.5,03.05.05,Prevent reuse of identifiers for a defined period.,"Identifiers are provided for users, processes acting on behalf of users, or devices (3.5.1). Preventing reuse of identifiers implies preventing the assignment of previously used individual, group, role, or device identifiers to different individuals, groups, roles, or devices." -Identification and Authentication,Derived,3.5.6,03.05.06,Disable identifiers after a defined period of inactivity.,Inactive identifiers pose a risk to organizational information because attackers may exploit an inactive identifier to gain undetected access to organizational devices. The owners of the inactive accounts may not notice if unauthorized access to the account has been obtained. -Identification and Authentication,Derived,3.5.7,03.05.07,Enforce a minimum password complexity and change of characters when new passwords are created.,"This requirement applies to single-factor authentication of individuals using passwords as individual or group authenticators, and in a similar manner, when passwords are used as part of multifactor authenticators. The number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. To mitigate certain brute force attacks against passwords, organizations may also consider salting passwords." -Identification and Authentication,Derived,3.5.8,03.05.08,Prohibit password reuse for a specified number of generations.,Password lifetime restrictions do not apply to temporary passwords -Identification and Authentication,Derived,3.5.9,03.05.09,Allow temporary password use for system logons with an immediate change to a permanent password.,"Changing temporary passwords to permanent passwords immediately after system logon ensures that the necessary strength of the authentication mechanism is implemented at the earliest opportunity, reducing the susceptibility to authenticator compromises." -Identification and Authentication,Derived,3.5.10,03.05.10,Store and transmit only cryptographically-protected passwords.,Cryptographically-protected passwords use salted one-way cryptographic hashes of passwords. See [NIST CRYPTO]. -Identification and Authentication,Derived,3.5.11,03.05.11,Obscure feedback of authentication information,"The feedback from systems does not provide any information that would allow unauthorized individuals to compromise authentication mechanisms. For some types of systems or system components, for example, desktop or notebook computers with relatively large monitors, the threat (often referred to as shoulder surfing) may be significant. For other types of systems or components, for example, mobile devices with small displays, this threat may be less significant, and is balanced against the increased likelihood of typographic input errors due to the small keyboards. Therefore, the means for obscuring the authenticator feedback is selected accordingly. Obscuring authenticator feedback includes displaying asterisks when users type passwords into input devices or displaying feedback for a very limited time before fully obscuring it." -Incident response,Basic,3.6.1,03.06.01,"Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.","Organizations recognize that incident handling capability is dependent on the capabilities of organizational systems and the mission/business processes being supported by those systems. Organizations consider incident handling as part of the definition, design, and development of mission/business processes and systems. Incident-related information can be obtained from a variety of sources including audit monitoring, network monitoring, physical access monitoring, user and administrator reports, and reported supply chain events. Effective incident handling capability includes coordination among many organizational entities including mission/business owners, system owners, authorizing officials, human resources offices, physical and personnel security offices, legal departments, operations personnel, procurement offices, and the risk executive. As part of user response activities, incident response training is provided by organizations and is linked directly to the assigned roles and responsibilities of organizational personnel to ensure that the appropriate content and level of detail is included in such training. For example, regular users may only need to know who to call or how to recognize an incident on the system; system administrators may require additional training on how to handle or remediate incidents; and incident responders may receive more specific training on forensics, reporting, system recovery, and restoration. Incident response training includes user training in the identification/reporting of suspicious activities from external and internal sources. User response activities also includes incident response assistance which may consist of help desk support, assistance groups, and access to forensics services or consumer redress services, when required. [SP 800-61] provides guidance on incident handling. [SP 800-86] and [SP 800-101] provide guidance on integrating forensic techniques into incident response. [SP 800-161] provides guidance on supply chain risk management." -Incident response,Basic,3.6.2,03.06.02,"Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.","Tracking and documenting system security incidents includes maintaining records about each incident, the status of the incident, and other pertinent information necessary for forensics, evaluating incident details, trends, and handling. Incident information can be obtained from a variety of sources including incident reports, incident response teams, audit monitoring, network monitoring, physical access monitoring, and user/administrator reports. Reporting incidents addresses specific incident reporting requirements within an organization and the formal incident reporting requirements for the organization. Suspected security incidents may also be reported and include the receipt of suspicious email communications that can potentially contain malicious code. The types of security incidents reported, the content and timeliness of the reports, and the designated reporting authorities reflect applicable laws, Executive Orders, directives, regulations, and policies. [SP 800-61] provides guidance on incident handling." -Incident response,Derived,3.6.3,03.06.03,Test the organizational incident response capability.,"Organizations test incident response capabilities to determine the effectiveness of the capabilities and to identify potential weaknesses or deficiencies. Incident response testing includes the use of checklists, walk-through or tabletop exercises, simulations (both parallel and full interrupt), and comprehensive exercises. Incident response testing can also include a determination of the effects on organizational operations (e.g., reduction in mission capabilities), organizational assets, and individuals due to incident response. [SP 800-84] provides guidance on testing programs for information technology capabilities." -Maintenance,Basic,3.7.1,03.07.01,Perform maintenance on organizational systems.[26]. ,"This requirement addresses the information security aspects of the system maintenance program and applies to all types of maintenance to any system component (including hardware, firmware, applications) conducted by any local or nonlocal entity. System maintenance also includes those components not directly associated with information processing and data or information retention such as scanners, copiers, and printers. - -[26] In general, system maintenance requirements tend to support the security objective of availability. However, improper system maintenance or a failure to perform maintenance can result in the unauthorized disclosure of CUI, thus compromising confidentiality of that information." -Maintenance,Basic,3.7.2,03.07.02,"Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance.","This requirement addresses security-related issues with maintenance tools that are not within the organizational system boundaries that process, store, or transmit CUI, but are used specifically for diagnostic and repair actions on those systems. Organizations have flexibility in determining the controls in place for maintenance tools, but can include approving, controlling, and monitoring the use of such tools. Maintenance tools are potential vehicles for transporting malicious code, either intentionally or unintentionally, into a facility and into organizational systems. Maintenance tools can include hardware, software, and firmware items, for example, hardware and software diagnostic test equipment and hardware and software packet sniffers." -Maintenance,Derived,3.7.3,03.07.03,Ensure equipment removed for off-site maintenance is sanitized of any CUI.,"This requirement addresses the information security aspects of system maintenance that are performed off-site and applies to all types of maintenance to any system component (including applications) conducted by a local or nonlocal entity (e.g., in-contract, warranty, in- house, software maintenance agreement). [SP 800-88] provides guidance on media sanitization." -Maintenance,Derived,3.7.4,03.07.04,Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems.,"If, upon inspection of media containing maintenance diagnostic and test programs, organizations determine that the media contain malicious code, the incident is handled consistent with incident handling policies and procedures." -Maintenance,Derived,3.7.5,03.07.05,Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete.,Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through an external network. The authentication techniques employed in the establishment of these nonlocal maintenance and diagnostic sessions reflect the network access requirements in 3.5.3. -Maintenance,Derived,3.7.6,03.07.06,Supervise the maintenance activities of maintenance personnel without required access authorization.,"This requirement applies to individuals who are performing hardware or software maintenance on organizational systems, while 3.10.1 addresses physical access for individuals whose maintenance duties place them within the physical protection perimeter of the systems (e.g., custodial staff, physical plant maintenance personnel). Individuals not previously identified as authorized maintenance personnel, such as information technology manufacturers, vendors, consultants, and systems integrators, may require privileged access to organizational systems, for example, when required to conduct maintenance activities with little or no notice. Organizations may choose to issue temporary credentials to these individuals based on organizational risk assessments. Temporary credentials may be for one-time use or for very limited time periods." -Media Protection,Basic,3.8.1,03.08.01,"Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital.","System media includes digital and non-digital media. Digital media includes diskettes, magnetic tapes, external and removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes paper and microfilm. Protecting digital media includes limiting access to design specifications stored on compact disks or flash drives in the media library to the project leader and any individuals on the development team. Physically controlling system media includes conducting inventories, maintaining accountability for stored media, and ensuring procedures are in place to allow individuals to check out and return media to the media library. Secure storage includes a locked drawer, desk, or cabinet, or a controlled media library. Access to CUI on system media can be limited by physically controlling such media, which includes conducting inventories, ensuring procedures are in place to allow individuals to check out and return media to the media library, and maintaining accountability for all stored media. [SP 800-111] provides guidance on storage encryption technologies for end user devices." -Media Protection,Basic,3.8.2,03.08.02,Limit access to CUI on system media to authorized users,"Access can be limited by physically controlling system media and secure storage areas. Physically controlling system media includes conducting inventories, ensuring procedures are in place to allow individuals to check out and return system media to the media library, and maintaining accountability for all stored media. Secure storage includes a locked drawer, desk, or cabinet, or a controlled media library" -Media Protection,Basic,3.8.3,03.08.03,Sanitize or destroy system media containing CUI before disposal or release for reuse.,"This requirement applies to all system media, digital and non-digital, subject to disposal or reuse. Examples include: digital media found in workstations, network components, scanners, copiers, printers, notebook computers, and mobile devices; and non-digital media such as paper and microfilm. The sanitization process removes information from the media such that the information cannot be retrieved or reconstructed. Sanitization techniques, including clearing, purging, cryptographic erase, and destruction, prevent the disclosure of information to unauthorized individuals when such media is released for reuse or disposal. Organizations determine the appropriate sanitization methods, recognizing that destruction may be necessary when other methods cannot be applied to the media requiring sanitization. Organizations use discretion on the employment of sanitization techniques and procedures for media containing information that is in the public domain or publicly releasable or deemed to have no adverse impact on organizations or individuals if released for reuse or disposal. Sanitization of non-digital media includes destruction, removing CUI from documents, or redacting selected sections or words from a document by obscuring the redacted sections or words in a manner equivalent in effectiveness to removing the words or sections from the document. NARA policy and guidance control sanitization processes for controlled unclassified information. [SP 800-88] provides guidance on media sanitization." -Media Protection,Derived,3.8.4,03.08.04,Mark media with necessary CUI markings and distribution limitations.[27] ,"The term security marking refers to the application or use of human-readable security attributes. System media includes digital and non-digital media. Marking of system media reflects applicable federal laws, Executive Orders, directives, policies, and regulations. See [NARA MARK]. - -[27] The implementation of this requirement is per marking guidance in [32 CFR 2002] and [NARA CUI]. Standard Form (SF) 902 (approximate size 2.125” x 1.25”) and SF 903 (approximate size 2.125” x .625”) can be used on media that contains CUI such as hard drives, or USB devices. Both forms are available from https://www.gsaadvantage.gov." -Media Protection,Derived,3.8.5,03.08.05,Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas.,"Controlled areas are areas or spaces for which organizations provide physical or procedural controls to meet the requirements established for protecting systems and information. Controls to maintain accountability for media during transport include locked containers and cryptography. Cryptographic mechanisms can provide confidentiality and integrity protections depending upon the mechanisms used. Activities associated with transport include the actual transport as well as those activities such as releasing media for transport and ensuring that media enters the appropriate transport processes. For the actual transport, authorized transport and courier personnel may include individuals external to the organization. Maintaining accountability of media during transport includes restricting transport activities to authorized personnel and tracking and obtaining explicit records of transport activities as the media moves through the transportation system to prevent and detect loss, destruction, or tampering." -Media Protection,Derived,3.8.6,03.08.06,Implement cryptographic mechanisms to protect the confidentiality of CUI stored on digital media during transport unless otherwise protected by alternative physical safeguards.,"This requirement applies to portable storage devices (e.g., USB memory sticks, digital video disks, compact disks, external or removable hard disk drives). See [NIST CRYPTO]. [SP 800-111] provides guidance on storage encryption technologies for end user devices." -Media Protection,Derived,3.8.7,03.08.07,Control the use of removable media on system components.,"In contrast to requirement 3.8.1, which restricts user access to media, this requirement restricts the use of certain types of media on systems, for example, restricting or prohibiting the use of flash drives or external hard disk drives. Organizations can employ technical and nontechnical controls (e.g., policies, procedures, and rules of behavior) to control the use of system media. Organizations may control the use of portable storage devices, for example, by using physical cages on workstations to prohibit access to certain external ports, or disabling or removing the ability to insert, read, or write to such devices. Organizations may also limit the use of portable storage devices to only approved devices including devices provided by the organization, devices provided by other approved organizations, and devices that are not personally owned. Finally, organizations may control the use of portable storage devices based on the type of device, prohibiting the use of writeable, portable devices, and implementing this restriction by disabling or removing the capability to write to such devices." -Media Protection,Derived,3.8.8,03.08.08,Prohibit the use of portable storage devices when such devices have no identifiable owner.,"Requiring identifiable owners (e.g., individuals, organizations, or projects) for portable storage devices reduces the overall risk of using such technologies by allowing organizations to assign responsibility and accountability for addressing known vulnerabilities in the devices (e.g., insertion of malicious code)." -Media Protection,Derived,3.8.9,03.08.09,Protect the confidentiality of backup CUI at storage locations.,"Organizations can employ cryptographic mechanisms or alternative physical controls to protect the confidentiality of backup information at designated storage locations. Backed-up information containing CUI may include system-level information and user-level information. System-level information includes system-state information, operating system software, application software, and licenses. User-level information includes information other than system-level information." -Personnel Security,Basic,3.9.1,03.09.01,Screen individuals prior to authorizing access to organizational systems containing CUI.,"Personnel security screening (vetting) activities involve the evaluation/assessment of individual’s conduct, integrity, judgment, loyalty, reliability, and stability (i.e., the trustworthiness of the individual) prior to authorizing access to organizational systems containing CUI. The screening activities reflect applicable federal laws, Executive Orders, directives, policies, regulations, and specific criteria established for the level of access required for assigned positions." -Personnel Security,Basic,3.9.2,03.09.02,Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers,"Protecting CUI during and after personnel actions may include returning system-related property and conducting exit interviews. System-related property includes hardware authentication tokens, identification cards, system administration technical manuals, keys, and building passes. Exit interviews ensure that individuals who have been terminated understand the security constraints imposed by being former employees and that proper accountability is achieved for system-related property. Security topics of interest at exit interviews can include reminding terminated individuals of nondisclosure agreements and potential limitations on future employment. Exit interviews may not be possible for some terminated individuals, for example, in cases related to job abandonment, illnesses, and non-availability of supervisors. For termination actions, timely execution is essential for individuals terminated for cause. In certain situations, organizations consider disabling the system accounts of individuals that are being terminated prior to the individuals being notified. This requirement applies to reassignments or transfers of individuals when the personnel action is permanent or of such extended durations as to require protection. Organizations define the CUI protections appropriate for the types of reassignments or transfers, whether permanent or extended. Protections that may be required for transfers or reassignments to other positions within organizations include returning old and issuing new keys, identification cards, and building passes; changing system access authorizations (i.e., privileges); closing system accounts and establishing new accounts; and providing for access to official records to which individuals had access at previous work locations and in previous system accounts." -Physical Protection,Basic,3.10.1,03.10.01,"Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals.","This requirement applies to employees, individuals with permanent physical access authorization credentials, and visitors. Authorized individuals have credentials that include badges, identification cards, and smart cards. Organizations determine the strength of authorization credentials needed consistent with applicable laws, directives, policies, regulations, standards, procedures, and guidelines. This requirement applies only to areas within facilities that have not been designated as publicly accessible. Limiting physical access to equipment may include placing equipment in locked rooms or other secured areas and allowing access to authorized individuals only; and placing equipment in locations that can be monitored by organizational personnel. Computing devices, external disk drives, networking devices, monitors, printers, copiers, scanners, facsimile machines, and audio devices are examples of equipment." -Physical Protection,Basic,3.10.2,03.10.02,Protect and monitor the physical facility and support infrastructure for organizational systems.,"Monitoring of physical access includes publicly accessible areas within organizational facilities. This can be accomplished, for example, by the employment of guards; the use of sensor devices; or the use of video surveillance equipment such as cameras. Examples of support infrastructure include system distribution, transmission, and power lines. Security controls applied to the support infrastructure prevent accidental damage, disruption, and physical tampering. Such controls may also be necessary to prevent eavesdropping or modification of unencrypted transmissions. Physical access controls to support infrastructure include locked wiring closets; disconnected or locked spare jacks; protection of cabling by conduit or cable trays; and wiretapping sensors." -Physical Protection,Derived,3.10.3,03.10.03,Escort visitors and monitor visitor activity.,Individuals with permanent physical access authorization credentials are not considered visitors. Audit logs can be used to monitor visitor activity. -Physical Protection,Derived,3.10.4,03.10.04,Maintain audit logs of physical access.,"Organizations have flexibility in the types of audit logs employed. Audit logs can be procedural (e.g., a written log of individuals accessing the facility), automated (e.g., capturing ID provided by a PIV card), or some combination thereof. Physical access points can include facility access points, interior access points to systems or system components requiring supplemental access controls, or both. System components (e.g., workstations, notebook computers) may be in areas designated as publicly accessible with organizations safeguarding access to such devices." -Physical Protection,Derived,3.10.5,03.10.05,Control and manage physical access devices.,"Physical access devices include keys, locks, combinations, and card readers." -Physical Protection,Derived,3.10.6,03.10.06,Enforce safeguarding measures for CUI at alternate work sites.,Alternate work sites may include government facilities or the private residences of employees. Organizations may define different security requirements for specific alternate work sites or types of sites depending on the work-related activities conducted at those sites. [SP 800-46] and [SP 800-114] provide guidance on enterprise and user security when teleworking. -Risk Assessment,Basic,3.11.1,03.11.01,"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","Clearly defined system boundaries are a prerequisite for effective risk assessments. Such risk assessments consider threats, vulnerabilities, likelihood, and impact to organizational operations, organizational assets, and individuals based on the operation and use of organizational systems. Risk assessments also consider risk from external parties (e.g., service providers, contractors operating systems on behalf of the organization, individuals accessing organizational systems, outsourcing entities). Risk assessments, either formal or informal, can be conducted at the organization level, the mission or business process level, or the system level, and at any phase in the system development life cycle. [SP 800-30] provides guidance on conducting risk assessments." -Risk Assessment,Derived,3.11.2,03.11.02,Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.,"Organizations determine the required vulnerability scanning for all system components, ensuring that potential sources of vulnerabilities such as networked printers, scanners, and copiers are not overlooked. The vulnerabilities to be scanned are readily updated as new vulnerabilities are discovered, announced, and scanning methods developed. This process ensures that potential vulnerabilities in the system are identified and addressed as quickly as possible. Vulnerability analyses for custom software applications may require additional approaches such as static analysis, dynamic analysis, binary analysis, or a hybrid of the three approaches. Organizations can employ these analysis approaches in source code reviews and in a variety of tools (e.g., static analysis tools, web-based application scanners, binary analyzers) and in source code reviews. Vulnerability scanning includes: scanning for patch levels; scanning for functions, ports, protocols, and services that should not be accessible to users or devices; and scanning for improperly configured or incorrectly operating information flow control mechanisms. To facilitate interoperability, organizations consider using products that are Security Content Automated Protocol (SCAP)-validated, scanning tools that express vulnerabilities in the Common Vulnerabilities and Exposures (CVE) naming convention, and that employ the Open Vulnerability Assessment Language (OVAL) to determine the presence of system vulnerabilities. Sources for vulnerability information include the Common Weakness Enumeration (CWE) listing and the National Vulnerability Database (NVD). Security assessments, such as red team exercises, provide additional sources of potential vulnerabilities for which to scan. Organizations also consider using scanning tools that express vulnerability impact by the Common Vulnerability Scoring System (CVSS). In certain situations, the nature of the vulnerability scanning may be more intrusive or the system component that is the subject of the scanning may contain highly sensitive information. Privileged access authorization to selected system components facilitates thorough vulnerability scanning and protects the sensitive nature of such scanning. [SP 800-40] provides guidance on vulnerability management." -Risk Assessment,Derived,3.11.3,03.11.03,Remediate vulnerabilities in accordance with risk assessments.,"Vulnerabilities discovered, for example, via the scanning conducted in response to 3.11.2, are remediated with consideration of the related assessment of risk. The consideration of risk influences the prioritization of remediation efforts and the level of effort to be expended in the remediation for specific vulnerabilities." -Security Assessment,Basic,3.12.1,03.12.01,Periodically assess the security controls in organizational systems to determine if the controls are effective in their application.,"Organizations assess security controls in organizational systems and the environments in which those systems operate as part of the system development life cycle. Security controls are the safeguards or countermeasures organizations implement to satisfy security requirements. By assessing the implemented security controls, organizations determine if the security safeguards or countermeasures are in place and operating as intended. Security control assessments ensure that information security is built into organizational systems; identify weaknesses and deficiencies early in the development process; provide essential information needed to make risk-based decisions; and ensure compliance to vulnerability mitigation procedures. Assessments are conducted on the implemented security controls as documented in system security plans. Security assessment reports document assessment results in sufficient detail as deemed necessary by organizations, to determine the accuracy and completeness of the reports and whether the security controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting security requirements. Security assessment results are provided to the individuals or roles appropriate for the types of assessments being conducted. Organizations ensure that security assessment results are current, relevant to the determination of security control effectiveness, and obtained with the appropriate level of assessor independence. Organizations can choose to use other types of assessment activities such as vulnerability scanning and system monitoring to maintain the security posture of systems during the system life cycle. [SP 800-53] provides guidance on security and privacy controls for systems and organizations. [SP 800-53A] provides guidance on developing security assessment plans and conducting assessments." -Security Assessment,Basic,3.12.2,03.12.02,Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems.,"The plan of action is a key document in the information security program. Organizations develop plans of action that describe how any unimplemented security requirements will be met and how any planned mitigations will be implemented. Organizations can document the system security plan and plan of action as separate or combined documents and in any chosen format. Federal agencies may consider the submitted system security plans and plans of action as critical inputs to an overall risk management decision to process, store, or transmit CUI on a system hosted by a nonfederal organization and whether it is advisable to pursue an agreement or contract with the nonfederal organization. [NIST CUI] provides supplemental material for Special Publication 800-171 including templates for plans of action." -Security Assessment,Basic,3.12.3,03.12.03,Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls.,"Continuous monitoring programs facilitate ongoing awareness of threats, vulnerabilities, and information security to support organizational risk management decisions. The terms continuous and ongoing imply that organizations assess and analyze security controls and information security-related risks at a frequency sufficient to support risk-based decisions. The results of continuous monitoring programs generate appropriate risk response actions by organizations. Providing access to security information on a continuing basis through reports or dashboards gives organizational officials the capability to make effective and timely risk management decisions. Automation supports more frequent updates to hardware, software, firmware inventories, and other system information. Effectiveness is further enhanced when continuous monitoring outputs are formatted to provide information that is specific, measurable, actionable, relevant, and timely. Monitoring requirements, including the need for specific monitoring, may also be referenced in other requirements. [SP 800-137] provides guidance on continuous monitoring." -Security Assessment,Basic,3.12.4,03.12.04,"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.[28] ","System security plans relate security requirements to a set of security controls. System security plans also describe, at a high level, how the security controls meet those security requirements, but do not provide detailed, technical descriptions of the design or implementation of the controls. System security plans contain sufficient information to enable a design and implementation that is unambiguously compliant with the intent of the plans and subsequent determinations of risk if the plan is implemented as intended. Security plans need not be single documents; the plans can be a collection of various documents including documents that already exist. Effective security plans make extensive use of references to policies, procedures, and additional documents (e.g., design and implementation specifications) where more detailed information can be obtained. This reduces the documentation requirements associated with security programs and maintains security-related information in other established management/operational areas related to enterprise architecture, system development life cycle, systems engineering, and acquisition. Federal agencies may consider the submitted system security plans and plans of action as critical inputs to an overall risk management decision to process, store, or transmit CUI on a system hosted by a nonfederal organization and whether it is advisable to pursue an agreement or contract with the nonfederal organization. [SP 800-18] provides guidance on developing security plans. [NIST CUI] provides supplemental material for Special Publication 800-171 including templates for system security plans." -System and Communications Protection,Basic,3.13.1,03.13.01,"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.","Communications can be monitored, controlled, and protected at boundary components and by restricting or prohibiting interfaces in organizational systems. Boundary components include gateways, routers, firewalls, guards, network-based malicious code analysis and virtualization systems, or encrypted tunnels implemented within a system security architecture (e.g., routers protecting firewalls or application gateways residing on protected subnetworks). Restricting or prohibiting interfaces in organizational systems includes restricting external web communications traffic to designated web servers within managed interfaces and prohibiting external traffic that appears to be spoofing internal addresses. Organizations consider the shared nature of commercial telecommunications services in the implementation of security requirements associated with the use of such services. Commercial telecommunications services are commonly based on network components and consolidated management systems shared by all attached commercial customers and may also include third party-provided access lines and other service elements. Such transmission services may represent sources of increased risk despite contract security provisions. [SP 800-41] provides guidance on firewalls and firewall policy. [SP 800-125B] provides guidance on security for virtualization technologies. - -[28] There is no prescribed format or specified level of detail for system security plans. However, organizations ensure that the required information in 3.12.4 is conveyed in those plans." -System and Communications Protection,Basic,3.13.2,03.13.02,"Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.","Organizations apply systems security engineering principles to new development systems or systems undergoing major upgrades. For legacy systems, organizations apply systems security engineering principles to system upgrades and modifications to the extent feasible, given the current state of hardware, software, and firmware components within those systems. The application of systems security engineering concepts and principles helps to develop trustworthy, secure, and resilient systems and system components and reduce the susceptibility of organizations to disruptions, hazards, and threats. Examples of these concepts and principles include developing layered protections; establishing security policies, architecture, and controls as the foundation for design; incorporating security requirements into the system development life cycle; delineating physical and logical security boundaries; ensuring that developers are trained on how to build secure software; and performing threat modeling to identify use cases, threat agents, attack vectors and patterns, design patterns, and compensating controls needed to mitigate risk. Organizations that apply security engineering concepts and principles can facilitate the development of trustworthy, secure systems, system components, and system services; reduce risk to acceptable levels; and make informed risk-management decisions. [SP 800-160-1] provides guidance on systems security engineering." -System and Communications Protection,Derived,3.13.3,03.13.03,Separate user functionality from system management functionality.,"System management functionality includes functions necessary to administer databases, network components, workstations, or servers, and typically requires privileged user access. The separation of user functionality from system management functionality is physical or logical. Organizations can implement separation of system management functionality from user functionality by using different computers, different central processing units, different instances of operating systems, or different network addresses; virtualization techniques; or combinations of these or other methods, as appropriate. This type of separation includes web administrative interfaces that use separate authentication methods for users of any other system resources. Separation of system and user functionality may include isolating administrative interfaces on different domains and with additional access controls." -System and Communications Protection,Derived,3.13.4,03.13.04,Prevent unauthorized and unintended information transfer via shared system resources.,"The control of information in shared system resources (e.g., registers, cache memory, main memory, hard disks) is also commonly referred to as object reuse and residual information protection. This requirement prevents information produced by the actions of prior users or roles (or the actions of processes acting on behalf of prior users or roles) from being available to any current users or roles (or current processes acting on behalf of current users or roles) that obtain access to shared system resources after those resources have been released back to the system. This requirement also applies to encrypted representations of information. This requirement does not address information remanence, which refers to residual representation of data that has been nominally deleted; covert channels (including storage or timing channels) where shared resources are manipulated to violate information flow restrictions; or components within systems for which there are only single users or roles." -System and Communications Protection,Derived,3.13.5,03.13.05,Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.,"Subnetworks that are physically or logically separated from internal networks are referred to as demilitarized zones (DMZs). DMZs are typically implemented with boundary control devices and techniques that include routers, gateways, firewalls, virtualization, or cloud-based technologies. [SP 800-41] provides guidance on firewalls and firewall policy. [SP 800-125B] provides guidance on security for virtualization technologies" -System and Communications Protection,Derived,3.13.6,03.13.06,"Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception).","This requirement applies to inbound and outbound network communications traffic at the system boundary and at identified points within the system. A deny-all, permit-by-exception network communications traffic policy ensures that only those connections which are essential and approved are allowed." -System and Communications Protection,Derived,3.13.7,03.13.07,"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 might be desirable by remote users to communicate with local system resources such as printers or file servers. However, split tunneling allows unauthorized external connections, making the system more vulnerable to attack and to exfiltration of organizational information. This requirement is implemented in remote devices (e.g., notebook computers, smart phones, and tablets) through configuration settings to disable split tunneling in those devices, and by preventing configuration settings from being readily configurable by users. This requirement is implemented in the system by the detection of split tunneling (or of configuration settings that allow split tunneling) in the remote device, and by prohibiting the connection if the remote device is using split tunneling." -System and Communications Protection,Derived,3.13.8,03.13.08,Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.,"This requirement applies to internal and external networks and any system components that can transmit information including servers, notebook computers, desktop computers, mobile devices, printers, copiers, scanners, and facsimile machines. Communication paths outside the physical protection of controlled boundaries are susceptible to both interception and modification. Organizations relying on commercial providers offering transmission services as commodity services rather than as fully dedicated services (i.e., services which can be highly specialized to individual customer needs), may find it difficult to obtain the necessary assurances regarding the implementation of the controls for transmission confidentiality. In such situations, organizations determine what types of confidentiality services are available in commercial telecommunication service packages. If it is infeasible or impractical to obtain the necessary safeguards and assurances of the effectiveness of the safeguards through appropriate contracting vehicles, organizations implement compensating safeguards or explicitly accept the additional risk. An example of an alternative physical safeguard is a protected distribution system (PDS) where the distribution medium is protected against electronic or physical intercept, thereby ensuring the confidentiality of the information being transmitted. See [NIST CRYPTO]." -System and Communications Protection,Derived,3.13.9,03.13.09,Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity.,"This requirement applies to internal and external networks. Terminating network connections associated with communications sessions include de-allocating associated TCP/IP address or port pairs at the operating system level, or de-allocating networking assignments at the application level if multiple application sessions are using a single, operating system-level network connection. Time periods of user inactivity may be established by organizations and include time periods by type of network access or for specific network accesses" -System and Communications Protection,Derived,3.13.10,03.13.10,Establish and manage cryptographic keys for cryptography employed in organizational systems.,"Cryptographic key management and establishment can be performed using manual procedures or mechanisms supported by manual procedures. Organizations define key management requirements in accordance with applicable federal laws, Executive Orders, policies, directives, regulations, and standards specifying appropriate options, levels, and parameters. [SP 800-56A] and [SP 800-57-1] provide guidance on cryptographic key management and key establishment." -System and Communications Protection,Derived,3.13.11,03.13.11,Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.,"Cryptography can be employed to support many security solutions including the protection of controlled unclassified information, the provision of digital signatures, and the enforcement of information separation when authorized individuals have the necessary clearances for such information but lack the necessary formal access approvals. Cryptography can also be used to support random number generation and hash generation. Cryptographic standards include FIPS-validated cryptography and/or NSA-approved cryptography. See [NIST CRYPTO]; [NIST CAVP]; and [NIST CMVP]." -System and Communications Protection,Derived,3.13.12,03.13.12,Prohibit remote activation of collaborative computing devices and provide indication of devices in use to users present at the device.[29]. ,"Collaborative computing devices include networked white boards, cameras, and microphones. Indication of use includes signals to users when collaborative computing devices are activated. Dedicated video conferencing systems, which rely on one of the participants calling or connecting to the other party to activate the video conference, are excluded. - -[29] Dedicated video conferencing systems, which rely on one of the participants calling or connecting to the other party to activate the video conference, are excluded." -System and Communications Protection,Derived,3.13.13,03.13.13,Control and monitor the use of mobile code.,"Mobile code technologies include Java, JavaScript, ActiveX, Postscript, PDF, Flash animations, and VBScript. Decisions regarding the use of mobile code in organizational systems are based on the potential for the code to cause damage to the systems if used maliciously. Usage restrictions and implementation guidance apply to the selection and use of mobile code installed on servers and mobile code downloaded and executed on individual workstations, notebook computers, and devices (e.g., smart phones). Mobile code policy and procedures address controlling or preventing the development, acquisition, or introduction of unacceptable mobile code in systems, including requiring mobile code to be digitally signed by a trusted source. [SP 800-28] provides guidance on mobile code." -System and Communications Protection,Derived,3.13.14,03.13.14,Control and monitor the use of Voice over Internet Protocol (VoIP) technologies.,"VoIP has different requirements, features, functionality, availability, and service limitations when compared with the Plain Old Telephone Service (POTS) (i.e., the standard telephone service). In contrast, other telephone services are based on high-speed, digital communications lines, such as Integrated Services Digital Network (ISDN) and Fiber Distributed Data Interface (FDDI). The main distinctions between POTS and non-POTS services are speed and bandwidth. To address the threats associated with VoIP, usage restrictions and implementation guidelines are based on the potential for the VoIP technology to cause damage to the system if it is used maliciously. Threats to VoIP are similar to those inherent with any Internet-based application. [SP 800-58] provides guidance on Voice Over IP Systems." -System and Communications Protection,Derived,3.13.15,03.13.15,Protect the authenticity of communications sessions.,"Authenticity protection includes protecting against man-in-the-middle attacks, session hijacking, and the insertion of false information into communications sessions. This requirement addresses communications protection at the session versus packet level (e.g., sessions in service-oriented architectures providing web-based services) and establishes grounds for confidence at both ends of communications sessions in ongoing identities of other parties and in the validity of information transmitted. [SP 800-77], [SP 800-95], and [SP 800-113] provide guidance on secure communications sessions." -System and Communications Protection,Derived,3.13.16,03.13.16,Protect the confidentiality of CUI at rest.,"Information at rest refers to the state of information when it is not in process or in transit and is located on storage devices as specific components of systems. The focus of protection at rest is not on the type of storage device or the frequency of access but rather the state of the information. Organizations can use different mechanisms to achieve confidentiality protections, including the use of cryptographic mechanisms and file share scanning. Organizations may also use other controls including secure off-line storage in lieu of online storage when adequate protection of information at rest cannot otherwise be achieved or continuous monitoring to identify malicious code at rest. See [NIST CRYPTO]." -System and Information Integrity,Basic,3.14.1,03.14.01,"Identify, report, and correct system flaws in a timely manner.","Organizations identify systems that are affected by announced software and firmware flaws including potential vulnerabilities resulting from those flaws and report this information to designated personnel with information security responsibilities. Security-relevant updates include patches, service packs, hot fixes, and anti-virus signatures. Organizations address flaws discovered during security assessments, continuous monitoring, incident response activities, and system error handling. Organizations can take advantage of available resources such as the Common Weakness Enumeration (CWE) database or Common Vulnerabilities and Exposures (CVE) database in remediating flaws discovered in organizational systems. Organization-defined time periods for updating security-relevant software and firmware may vary based on a variety of factors including the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). Some types of flaw remediation may require more testing than other types of remediation. [SP 800-40] provides guidance on patch management technologies." -System and Information Integrity,Basic,3.14.2,03.14.02,Provide protection from malicious code at designated locations within organizational systems.,"Designated locations include system entry and exit points which may include firewalls, remote-access servers, workstations, electronic mail servers, web servers, proxy servers, notebook computers, and mobile devices. Malicious code includes viruses, worms, Trojan horses, and spyware. Malicious code can be encoded in various formats (e.g., UUENCODE, Unicode), contained within compressed or hidden files, or hidden in files using techniques such as steganography. Malicious code can be inserted into systems in a variety of ways including web accesses, electronic mail, electronic mail attachments, and portable storage devices. Malicious code insertions occur through the exploitation of system vulnerabilities. Malicious code protection mechanisms include anti-virus signature definitions and reputation-based technologies. A variety of technologies and methods exist to limit or eliminate the effects of malicious code. Pervasive configuration management and comprehensive software integrity controls may be effective in preventing execution of unauthorized code. In addition to commercial off-the-shelf software, malicious code may also be present in custom-built software. This could include logic bombs, back doors, and other types of cyber-attacks that could affect organizational missions/business functions. Traditional malicious code protection mechanisms cannot always detect such code. In these situations, organizations rely instead on other safeguards including secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to help ensure that software does not perform functions other than the functions intended. [SP 800-83] provides guidance on malware incident prevention." -System and Information Integrity,Basic,3.14.3,03.14.03,Monitor system security alerts and advisories and take action in response.,"There are many publicly available sources of system security alerts and advisories. For example, the Department of Homeland Security’s Cybersecurity and Infrastructure Security Agency (CISA) generates security alerts and advisories to maintain situational awareness across the federal government and in nonfederal organizations. Software vendors, subscription services, and industry information sharing and analysis centers (ISACs) may also provide security alerts and advisories. Examples of response actions include notifying relevant external organizations, for example, external mission/business partners, supply chain partners, external service providers, and peer or supporting organizations. [SP 800-161] provides guidance on supply chain risk management." -System and Information Integrity,Derived,3.14.4,03.14.04,Update malicious code protection mechanisms when new releases are available.,"Malicious code protection mechanisms include anti-virus signature definitions and reputation-based technologies. A variety of technologies and methods exist to limit or eliminate the effects of malicious code. Pervasive configuration management and comprehensive software integrity controls may be effective in preventing execution of unauthorized code. In addition to commercial off-the-shelf software, malicious code may also be present in custom-built software. This could include logic bombs, back doors, and other types of cyber-attacks that could affect organizational missions/business functions. Traditional malicious code protection mechanisms cannot always detect such code. In these situations, organizations rely instead on other safeguards including secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to help ensure that software does not perform functions other than the functions intended. " -System and Information Integrity,Derived,3.14.5,03.14.05,"Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed.","Periodic scans of organizational systems and real-time scans of files from external sources can detect malicious code. Malicious code can be encoded in various formats (e.g., UUENCODE, Unicode), contained within compressed or hidden files, or hidden in files using techniques such as steganography. Malicious code can be inserted into systems in a variety of ways including web accesses, electronic mail, electronic mail attachments, and portable storage devices. Malicious code insertions occur through the exploitation of system vulnerabilities." -System and Information Integrity,Derived,3.14.6,03.14.06,"Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks.","System monitoring includes external and internal monitoring. External monitoring includes the observation of events occurring at the system boundary (i.e., part of perimeter defense and boundary protection). Internal monitoring includes the observation of events occurring within the system. Organizations can monitor systems, for example, by observing audit record activities in real time or by observing other system aspects such as access patterns, characteristics of access, and other actions. The monitoring objectives may guide determination of the events. System monitoring capability is achieved through a variety of tools and techniques (e.g., intrusion detection systems, intrusion prevention systems, malicious code protection software, scanning tools, audit record monitoring software, network monitoring software). Strategic locations for monitoring devices include selected perimeter locations and near server farms supporting critical applications, with such devices being employed at managed system interfaces. The granularity of monitoring information collected is based on organizational monitoring objectives and the capability of systems to support such objectives. System monitoring is an integral part of continuous monitoring and incident response programs. Output from system monitoring serves as input to continuous monitoring and incident response programs. A network connection is any connection with a device that communicates through a network (e.g., local area network, Internet). A remote connection is any connection with a device communicating through an external network (e.g., the Internet). Local, network, and remote connections can be either wired or wireless. Unusual or unauthorized activities or conditions related to inbound/outbound communications traffic include internal traffic that indicates the presence of malicious code in systems or propagating among system components, the unauthorized exporting of information, or signaling to external systems. Evidence of malicious code is used to identify potentially compromised systems or system components. System monitoring requirements, including the need for specific types of system monitoring, may be referenced in other requirements. [SP 800-94] provides guidance on intrusion detection and prevention systems." -System and Information Integrity,Derived,3.14.7,03.14.07,Identify unauthorized use of organizational systems.,"System monitoring includes external and internal monitoring. System monitoring can detect unauthorized use of organizational systems. System monitoring is an integral part of continuous monitoring and incident response programs. Monitoring is achieved through a variety of tools and techniques (e.g., intrusion detection systems, intrusion prevention systems, malicious code protection software, scanning tools, audit record monitoring software, network monitoring software). Output from system monitoring serves as input to continuous monitoring and incident response programs. Unusual/unauthorized activities or conditions related to inbound and outbound communications traffic include internal traffic that indicates the presence of malicious code in systems or propagating among system components, the unauthorized exporting of information, or signaling to external systems. Evidence of malicious code is used to identify potentially compromised systems or system components. System monitoring requirements, including the need for specific types of system monitoring, may be referenced in other requirements. [SP 800-94] provides guidance on intrusion detection and prevention systems. " diff --git a/data/third-party-components.json b/data/third-party-components.json index ff41a57a..98592c15 100644 --- a/data/third-party-components.json +++ b/data/third-party-components.json @@ -1,86 +1,233 @@ { - "_note": "REQ-TPR-1 records for the external services the inventory declares (scripts/build-ksi-signal.py build_external_components). Each names the upstream offering, the upstream component's identifier, and the split between what the upstream runs and what this provider configures. A record is published only once it carries decided_by and decided_on; until then the inventory publishes every field as \"not recorded\". A record for a service the inventory does not declare fails the build. AI-drafted entries (drafted_by) are proposals from the evidence listed; none is in force until the operator records a decision. A null value is unknown and is published as \"not recorded\" even after a decision.", + "_note": "REQ-TPR-1 and MAS-CSO-TPR records for the external services the inventory declares (scripts/build-ksi-signal.py build_external_components). Each names the upstream offering, the upstream component's identifier, the split between what the upstream runs and what this provider configures, and the four things FedRAMP requires documented for each third-party information resource (MAS-CSO-TPR): general usage and configuration, justification for use, mitigation measures, and compensating controls. A record is published only once it carries decided_by and decided_on, and a decided record must carry all four MAS-CSO-TPR fields or the build fails; until a decision, the inventory publishes every field as \"not recorded\". A record for a service the inventory does not declare fails the build. AI-drafted entries (drafted_by) were proposed from the evidence listed; the decision fields on the 2026-11-05 drafts are for the operator to confirm. A null value is unknown and is published as \"not recorded\" even after a decision.", "components": { "ext::sigstore-fulcio": { + "provider": "OpenSSF Sigstore project (public-good instance)", + "website": "https://www.sigstore.dev/", "upstream_offering": "Sigstore public-good instance: Fulcio certificate authority", "upstream_component_id": "https://fulcio.sigstore.dev", "responsibility_split": { "upstream_runs": "The certificate authority that issues short-lived signing certificates bound to the CI run's OIDC identity.", "provider_configures": "Keyless signing in CI (cosign sign-blob), and the certificate identity and OIDC issuer every verification pins." }, - "evidence": [".github/workflows/evidence-nightly.yml (cosign sign-blob; --certificate-identity, --certificate-oidc-issuer)", "scripts/verify-published.sh (--certificate-identity, --certificate-oidc-issuer)"], - "drafted_by": "Claude (AI-drafted), 2026-11-03", - "decided_by": null, - "decided_on": null + "usage_and_configuration": "Every deploy and nightly signs each published artifact keylessly: cosign obtains a short-lived certificate from Fulcio bound to the workflow's GitHub OIDC identity. No account or configuration exists on Fulcio's side.", + "justification": "Keyless signing removes long-lived signing keys from the pipeline and binds every signature to the exact workflow and commit that produced it, which any reader can verify.", + "mitigations": "Every verification pins the certificate identity (the workflow path and ref) and the OIDC issuer, so a certificate issued to anyone else does not verify. Fulcio sees only the CSR and the OIDC token claims (repository, workflow, ref), never artifact content. No federal customer data is in this offering; the resource never receives app-user data.", + "compensating_controls": "The post-publish round-trip verify and scripts/verify-published.sh re-verify every signature from outside; a Fulcio outage stops the deploy (fail closed) rather than publishing unsigned evidence.", + "evidence": [ + ".github/workflows/evidence-nightly.yml (cosign sign-blob; --certificate-identity, --certificate-oidc-issuer)", + "scripts/verify-published.sh (--certificate-identity, --certificate-oidc-issuer)" + ], + "drafted_by": "Claude (AI-drafted), 2026-11-03; MAS-CSO-TPR fields and decision fields AI-drafted 2026-11-05 for the operator to confirm", + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05" }, "ext::sigstore-rekor": { + "provider": "OpenSSF Sigstore project (public-good instance)", + "website": "https://www.sigstore.dev/", "upstream_offering": "Sigstore public-good instance: Rekor transparency log", "upstream_component_id": "https://rekor.sigstore.dev", "responsibility_split": { "upstream_runs": "The append-only transparency log and its inclusion proofs.", "provider_configures": "Signing with transparency-log upload (cosign defaults, not disabled) and verification that checks the inclusion proof in each bundle." }, - "evidence": [".github/workflows/evidence-nightly.yml (cosign sign-blob --new-bundle-format)", "scripts/verify-published.sh (cosign verify-blob)"], - "drafted_by": "Claude (AI-drafted), 2026-11-03", - "decided_by": null, - "decided_on": null + "usage_and_configuration": "Each keyless signature is recorded in Rekor (cosign default, not disabled); the bundle published next to each artifact carries the inclusion proof.", + "justification": "The transparency log makes every signature publicly auditable, so a signature made outside the pipeline would be visible.", + "mitigations": "Rekor receives only the signature, certificate and artifact digest, never artifact content. Verification checks the inclusion proof offline from the bundle. No federal customer data is in this offering; the resource never receives app-user data.", + "compensating_controls": "Signature verification against the pinned identity does not depend on Rekor being reachable later; the published bundles carry the proofs.", + "evidence": [ + ".github/workflows/evidence-nightly.yml (cosign sign-blob --new-bundle-format)", + "scripts/verify-published.sh (cosign verify-blob)" + ], + "drafted_by": "Claude (AI-drafted), 2026-11-03; MAS-CSO-TPR fields and decision fields AI-drafted 2026-11-05 for the operator to confirm", + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05" }, "ext::github-oidc": { + "provider": "GitHub, Inc.", + "website": "https://docs.github.com/actions/security-for-github-actions/security-hardening-your-deployments/about-security-hardening-with-openid-connect", "upstream_offering": "GitHub Actions OIDC token issuer", "upstream_component_id": "https://token.actions.githubusercontent.com", "responsibility_split": { "upstream_runs": "The token issuer and its signing keys (JWKS).", "provider_configures": "Which workflows may request a token (permissions: id-token: write), the AWS IAM OIDC trust conditions, and the issuer pinned in cosign verification." }, - "evidence": [".github/workflows/deploy-with-opa.yml:105 (id-token: write)", "infrastructure/bootstrap/plan-role.tf, evidence-nightly.tf, main.tf (OIDC trust)", ".github/workflows/evidence-nightly.yml:118 (COSIGN_OIDC_ISSUER)"], - "drafted_by": "Claude (AI-drafted), 2026-11-03", - "decided_by": null, - "decided_on": null + "usage_and_configuration": "Workflows granted id-token: write obtain per-run identity tokens, which AWS STS exchanges for the deploy, plan and nightly roles and which Fulcio binds into signing certificates.", + "justification": "Workload identity replaces static cloud credentials in CI: there is no long-lived access key to leak.", + "mitigations": "The AWS role trust policies pin the repository and, for the deploy role, the prod environment (reviewer-gated); only named workflows request tokens. No federal customer data is in this offering; the resource never receives app-user data.", + "compensating_controls": "The deploy needs a human approval in the prod environment before its token can assume the deploy role; role permissions are least-privilege and reviewed in the bootstrap stack.", + "evidence": [ + ".github/workflows/deploy-with-opa.yml:105 (id-token: write)", + "infrastructure/bootstrap/plan-role.tf, evidence-nightly.tf, main.tf (OIDC trust)", + ".github/workflows/evidence-nightly.yml:118 (COSIGN_OIDC_ISSUER)" + ], + "drafted_by": "Claude (AI-drafted), 2026-11-03; MAS-CSO-TPR fields and decision fields AI-drafted 2026-11-05 for the operator to confirm", + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05" }, "ext::github-repo": { + "provider": "GitHub, Inc.", + "website": "https://github.com/sam-aydlette/samaydlette.com", "upstream_offering": "GitHub repository and GitHub Actions", "upstream_component_id": "https://github.com/sam-aydlette/samaydlette.com", "responsibility_split": { "upstream_runs": "Repository hosting, the Actions runners, Dependabot, and secret scanning.", "provider_configures": "Branch protection on main, the workflows and their permissions, the OPA gate, the SCN tag validator, and secret scanning with push protection." }, - "evidence": ["scripts/build-ksi-signal.py (ext::github-repo verification text)", ".github/workflows/"], - "drafted_by": "Claude (AI-drafted), 2026-11-03", - "decided_by": null, - "decided_on": null + "usage_and_configuration": "Hosts the source of record and runs the CI/CD workflows (deploy, nightly evidence, scans) on GitHub-hosted runners.", + "justification": "The repository is the system of record for infrastructure as code and evidence generation; hosted runners give an ephemeral, reproducible build environment.", + "mitigations": "Branch protection on main, required checks, a reviewer-gated prod environment for every deploy, secret scanning with push protection, and least-privilege workflow permissions. No federal customer data is in this offering; the resource never receives app-user data.", + "compensating_controls": "Every published artifact is signed under the deploy workflow's pinned identity and re-verified from outside; the hand-applied GitHub settings are checked live on every deploy (scripts/check-manual-settings.py).", + "evidence": [ + "scripts/build-ksi-signal.py (ext::github-repo verification text)", + ".github/workflows/" + ], + "drafted_by": "Claude (AI-drafted), 2026-11-03; MAS-CSO-TPR fields and decision fields AI-drafted 2026-11-05 for the operator to confirm", + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05" }, "ext::duo-mfa": { - "upstream_offering": null, + "provider": "Cisco Systems, Inc. (Duo)", + "website": "https://duo.com/", + "upstream_offering": "Duo Mobile authenticator app", "upstream_component_id": null, - "responsibility_split": null, - "evidence": ["scripts/build-ksi-signal.py (ext::duo-mfa: tenant identifier intentionally not published)"], - "drafted_by": "Claude (AI-drafted), 2026-11-03; the repository does not show the Duo edition, its identifier, or how it is configured, so nothing is drafted", - "decided_by": null, - "decided_on": null + "responsibility_split": { + "upstream_runs": "The authenticator app that generates the time-based one-time codes.", + "provider_configures": "Enrollment of the TOTP device as the MFA factor on the AWS root account, the operator IAM user and the GitHub account." + }, + "usage_and_configuration": "Generates the TOTP codes the operator enters as the second factor for the AWS root account, the operator IAM user and the GitHub account. AWS records both principals' MFA as virtual (TOTP) devices (DEC-025, DEC-150), which the deploy checks on every run; Duo does not enforce anything.", + "justification": "A second factor on every top-level administrative and privileged account, as IA-2(1) and IA-2(2) require.", + "mitigations": "TOTP seeds stay on the operator's device; no tenant identifier is published. MFA is enabled on every privileged human account. No federal customer data is in this offering; the resource never receives app-user data.", + "compensating_controls": "The weaker-than-phishing-resistant factor is a recorded decision (DEC-025); CloudTrail records every console sign-in and privileged API call.", + "evidence": [ + "scripts/build-ksi-signal.py (ext::duo-mfa: tenant identifier intentionally not published)" + ], + "drafted_by": "Claude (AI-drafted), 2026-11-05; decided by the operator 2026-11-05. The repository records virtual TOTP MFA on the root user and the operator user (DEC-025, DEC-150); that Duo Mobile is the app generating the codes is the operator's statement (docs/rules-of-behavior.md, docs/policies/ia-policy.md).", + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05" }, "ext::github-advisory-db": { + "provider": "GitHub, Inc.", + "website": "https://github.com/advisories", "upstream_offering": "GitHub Advisory Database, read through Dependabot alerts", "upstream_component_id": "https://github.com/advisories", "responsibility_split": { "upstream_runs": "The advisory database and the matching of advisories to this repository's dependencies.", "provider_configures": "The fetch of open Dependabot alerts in the deploy and nightly workflows, and how a failed fetch is handled." }, - "evidence": [".github/workflows/evidence-nightly.yml:435 (dependabot/alerts)", ".github/workflows/deploy-with-opa.yml:1399"], - "drafted_by": "Claude (AI-drafted), 2026-11-03", - "decided_by": null, - "decided_on": null + "usage_and_configuration": "The deploy and the nightly read open Dependabot alerts for this repository, which GitHub matches from the Advisory Database.", + "justification": "An independent source of dependency vulnerabilities alongside the Grype scan.", + "mitigations": "A failed fetch fails the detection gate (G7) rather than reading as zero findings. Only public advisory data is read. No federal customer data is in this offering; the resource never receives app-user data.", + "compensating_controls": "Findings are corroborated with the Grype scan and CISA KEV; the VDR records each source.", + "evidence": [ + ".github/workflows/evidence-nightly.yml:435 (dependabot/alerts)", + ".github/workflows/deploy-with-opa.yml:1399" + ], + "drafted_by": "Claude (AI-drafted), 2026-11-03; MAS-CSO-TPR fields and decision fields AI-drafted 2026-11-05 for the operator to confirm", + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05" }, "ext::cisa-kev": { + "provider": "Cybersecurity and Infrastructure Security Agency (CISA)", + "website": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog", "upstream_offering": "CISA Known Exploited Vulnerabilities catalog (JSON feed)", "upstream_component_id": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json", "responsibility_split": { "upstream_runs": "The catalog and its JSON feed.", "provider_configures": "The fetch in the deploy and nightly workflows, and how a failed fetch is handled." }, - "evidence": [".github/workflows/evidence-nightly.yml:447 (KEV_URL)", ".github/workflows/deploy-with-opa.yml:1415"], - "drafted_by": "Claude (AI-drafted), 2026-11-03", - "decided_by": null, - "decided_on": null + "usage_and_configuration": "The deploy and the nightly fetch the KEV JSON feed and mark each finding that appears in it.", + "justification": "The authoritative U.S. government list of vulnerabilities known to be exploited, which drives remediation priority.", + "mitigations": "A failed fetch fails the detection gate (G7). Only public data is read. No federal customer data is in this offering; the resource never receives app-user data.", + "compensating_controls": "EPSS and the Grype and Dependabot sources still rate findings; the VDR states which feeds it read.", + "evidence": [ + ".github/workflows/evidence-nightly.yml:447 (KEV_URL)", + ".github/workflows/deploy-with-opa.yml:1415" + ], + "drafted_by": "Claude (AI-drafted), 2026-11-03; MAS-CSO-TPR fields and decision fields AI-drafted 2026-11-05 for the operator to confirm", + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05" + }, + "ext::first-epss": { + "provider": "FIRST (Forum of Incident Response and Security Teams); file served from epss.cyentia.com", + "website": "https://www.first.org/epss/", + "upstream_offering": "FIRST Exploit Prediction Scoring System, daily scores file", + "upstream_component_id": "https://epss.cyentia.com/epss_scores-current.csv.gz", + "responsibility_split": { + "upstream_runs": "The EPSS model and the daily scores file.", + "provider_configures": "The fetch in scripts/fetch-detection-feeds.sh and how a failed fetch is handled (the detection gate fails)." + }, + "usage_and_configuration": "The deploy and the nightly download the current scores file and attach each finding's exploit probability.", + "justification": "Exploit likelihood is one input to the finding's rating (likely exploitable), alongside KEV.", + "mitigations": "A failed fetch fails the detection gate (G7). Only public data is read. No federal customer data is in this offering; the resource never receives app-user data.", + "compensating_controls": "KEV membership still marks known exploitation; the rating method is recorded in the VDR.", + "evidence": [ + "scripts/fetch-detection-feeds.sh (EPSS_URL)" + ], + "drafted_by": "Claude (AI-drafted), 2026-11-05, for the operator to confirm", + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05" + }, + "ext::anchore-grype-db": { + "provider": "Anchore, Inc.", + "website": "https://github.com/anchore/grype", + "upstream_offering": "Grype vulnerability database, distributed by Anchore", + "upstream_component_id": "https://grype.anchore.io/databases", + "responsibility_split": { + "upstream_runs": "Building and publishing the vulnerability database from upstream advisory sources.", + "provider_configures": "The pinned Grype version (GRYPE_VERSION) and the scans of each SBOM in the deploy and the nightly." + }, + "usage_and_configuration": "Grype downloads the current database at scan time and matches every SBOM the pipeline builds against it.", + "justification": "The primary software-composition scan behind the VDR.", + "mitigations": "The Grype version is pinned; Grype checks the database download against the checksum in its published index. Only the SBOMs are scanned, locally; nothing is uploaded. No federal customer data is in this offering; the resource never receives app-user data.", + "compensating_controls": "Dependabot alerts and CISA KEV are independent sources the VDR corroborates against.", + "evidence": [ + ".github/workflows/evidence-nightly.yml (grype sbom:...)", + ".github/workflows/deploy-with-opa.yml (GRYPE_VERSION)" + ], + "drafted_by": "Claude (AI-drafted), 2026-11-05, for the operator to confirm", + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05" + }, + "ext::jsdelivr": { + "provider": "jsDelivr", + "website": "https://www.jsdelivr.com/", + "upstream_offering": "jsDelivr open-source CDN, npm endpoint", + "upstream_component_id": "https://cdn.jsdelivr.net/npm/@mediapipe/tasks-vision/", + "responsibility_split": { + "upstream_runs": "Serving the published npm package files over its CDN.", + "provider_configures": "The pinned MediaPipe Tasks Vision version in the app bundle and the CSP script-src and connect-src paths that allow only that package." + }, + "usage_and_configuration": "The Silk Reeling app's browser code loads the MediaPipe Tasks Vision JavaScript and WebAssembly from jsDelivr at the version the bundle pins.", + "justification": "MediaPipe runs pose estimation in the user's browser, so camera frames never leave the device; jsDelivr is the distribution MediaPipe documents.", + "mitigations": "The CSP allows only the pinned package path; camera frames stay in the browser and only pose landmarks reach the app's API. jsDelivr sees the user's IP address and user agent when the file is fetched. No federal customer data is in this offering; the resource never receives app-user data.", + "compensating_controls": "The app requires Cognito sign-in with TOTP MFA; the API accepts only landmark data and returns scores. Self-hosting the runtime is the further step if a stronger integrity guarantee is needed.", + "evidence": [ + "infrastructure/bootstrap/cloudfront.tf (silk_reeling_mediapipe, CSP script-src)" + ], + "drafted_by": "Claude (AI-drafted), 2026-11-05, for the operator to confirm", + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05" + }, + "ext::google-cloud-storage": { + "provider": "Google LLC", + "website": "https://ai.google.dev/edge/mediapipe/solutions/vision/pose_landmarker", + "upstream_offering": "Google Cloud Storage, MediaPipe public model bucket", + "upstream_component_id": "https://storage.googleapis.com/mediapipe-models/", + "responsibility_split": { + "upstream_runs": "Hosting and serving the published MediaPipe model files.", + "provider_configures": "The model path the app requests and the CSP connect-src path that allows only the mediapipe-models bucket." + }, + "usage_and_configuration": "The MediaPipe runtime in the user's browser downloads the pose-landmarker model file from Google's public model bucket.", + "justification": "The model Google publishes for MediaPipe pose landmarking; running it in the browser keeps camera frames on the device.", + "mitigations": "The CSP allows only the mediapipe-models path; the model is data loaded by the pinned runtime, not script. Google sees the user's IP address and user agent when the file is fetched. No federal customer data is in this offering; the resource never receives app-user data.", + "compensating_controls": "Pose scores are computed server-side from landmarks only; a tampered model could degrade scores but cannot read data beyond the camera frames already in the browser.", + "evidence": [ + "infrastructure/bootstrap/cloudfront.tf (CSP connect-src)" + ], + "drafted_by": "Claude (AI-drafted), 2026-11-05, for the operator to confirm", + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05" } } } diff --git a/data/vdr-activities.json b/data/vdr-activities.json new file mode 100644 index 00000000..492bcdba --- /dev/null +++ b/data/vdr-activities.json @@ -0,0 +1,40 @@ +{ + "$schema": "../infrastructure/schemas/vdr-activities.schema.json", + "schema": "vdr-activities/1", + "$comment": "Historical vulnerability detection and response activity from outside the pipeline (VER-RPT-HLO), kept as a record; nothing is added here by hand. The month's activities are generated from run records by scripts/build-vdr-monthly.py (generated_runs): the scans and feeds the VDR build read, the runtime runs, the non-machine verification, the simulated assessor's runs, and the incident, inbox and recovery exercises and the audit-log review's planted intruder, all with simulated participants (DEC-194, DEC-195). It states 'none this period' for each kind with no run. The two entries below were AI-drafted from the repository on 2026-11-05 (docs/security-review.md; DEC-039 and DEC-040) and are history: no confirmation is pending.", + "programs": { + "vdp": { + "active": true, + "note": "reports to the contact in /.well-known/security.txt" + }, + "bug-bounty": { + "active": false, + "note": "no bug bounty program" + }, + "penetration-testing": { + "active": false, + "note": "no penetration test has been performed or scheduled" + } + }, + "activities": [ + { + "id": "ACT-001", + "kind": "assessment", + "date": "2026-05-08", + "performed_by": "Sam Aydlette (operator; self-performed)", + "summary": "Independent-assessment-style external assessment, self-performed; findings SAR-001 to SAR-009", + "evidence": "docs/security-review.md (History: the 2026-Q2 entry)", + "recorded_by": "AI-drafted from the repository, 2026-11-05; historical record (no confirmation pending)" + }, + { + "id": "ACT-002", + "kind": "manual-scan", + "date": "2026-10-26", + "end_date": "2026-10-27", + "performed_by": "Sam Aydlette (operator)", + "summary": "Manual OWASP ZAP scans of https://samaydlette.com; alerts 10099 and 10036-2 assessed as false positives", + "evidence": "data/decisions.json DEC-039, DEC-040 (original_detection_date 2026-10-26)", + "recorded_by": "AI-drafted from the repository, 2026-11-05; historical record (no confirmation pending)" + } + ] +} diff --git a/docs/architecture-decisions.md b/docs/architecture-decisions.md index 6fb7682e..e1778bd5 100644 --- a/docs/architecture-decisions.md +++ b/docs/architecture-decisions.md @@ -8,7 +8,7 @@ Change management is GitOps, full stop. Every change to infrastructure or conten There is no separate change-management ticketing system because there is no separate change-management team. The PR is the change request, the review (when applicable), and the approval. For solo work, the diff itself serves all three roles. -**Effectiveness review:** monthly, by checking that no commits have reached `main` outside the workflow. The git log makes this trivial; the runtime KSI signal makes drift detectable. +**Effectiveness check:** automated, every night. The audit-log review (`scripts/audit-log-review.py`, published as `/.well-known/vdr-audit-log-review.json`) lists every commit on `main` since the previous run and flags any without a merged pull request, any workflow change outside one, and any ruleset or environment changed in the window; the runtime KSI signal makes drift detectable. ## Ingress and egress restriction (KSI-CNA-RNT) @@ -27,7 +27,7 @@ The system has three logical paths: viewer→CloudFront→S3 (read-only, all vie CloudFront includes AWS Shield Standard at no cost; this is the baseline protection. AWS WAF was evaluated and consciously excluded as a cost trade-off (~$120/year) documented in the README and POAM-007. Since the Silk Reeling app was added, the system does have an authentication endpoint and an API — those are protected by API Gateway stage throttling (20 req/s, burst 10), Cognito account lockout, and Shield Standard, which together cover the SC-5 cases at this scale. POAM-023's closure keeps a standing trigger: credential-guessing evidence in the app's logs forces the WAF rate-rule immediately. -**Effectiveness review:** annually (see [`security-review.md`](security-review.md)). If traffic patterns change or the threat profile shifts (e.g., the site starts serving forms or APIs), the WAF decision is revisited. +**Effectiveness check:** the Annual Security Review (`scripts/hold-security-review.py`, [`security-review.md`](security-review.md)) fails when a component type added since the previous review, such as a new form or API, is not named in this section or the threat model, so a change in the threat profile reopens the WAF decision through a reviewed pull request. ## High availability (KSI-CNA-OFA) @@ -61,15 +61,16 @@ cannot silence the audit record. Alerting today is scoped to evidence freshness: the evidence SLA watchdog (`infrastructure/watchdog.tf`) pages the operator by email when published reporting goes stale or the nightly refresh fails. If the system grew to require true SIEM features (correlation rules, alerting on control-plane events, longer retention), the next step would be Amazon Security Lake or a third-party SIEM ingesting from CloudWatch. Out of scope today. -## Audit log review cadence (KSI-MLA-RVL) +## Audit log review (KSI-MLA-RVL) -Quarterly. Specifically: +Automated, every night: `scripts/audit-log-review.py` runs in `evidence-nightly.yml` and publishes `/.well-known/vdr-audit-log-review.json`, signed. It: -- Review CloudTrail records for any unexpected API calls, especially IAM and CloudFront writes from non-CI principals (capture depth is documented in the SIEM section above) -- Review Lambda execution logs for runtime KSI emitter failures -- Review GitHub Actions workflow run history for unexpected workflow modifications +- reads CloudTrail's event history (`cloudtrail:LookupEvents`, write events only, in us-east-1 and us-east-2) for IAM, CloudFront, KMS, Lambda, Cognito, CloudTrail and S3 bucket-policy or public-access writes, and flags any whose principal is not one of the five CI roles, AWS itself, or a Cognito app user's own sign-in (capture depth is documented in the SIEM section above); +- reads GitHub's record of `main` (commits and their merged pull requests, workflow changes, rulesets and environments) and flags any change outside a merged pull request; +- evaluates each flagged event by rule (IEC-CSO-EFR): one that stops or reconfigures the trail, creates long-lived credentials or a user, disables a key or removes a public access block is a possible FedRAMP Reportable Incident and fails the nightly; any other is a process finding in the VDR (gate check `audit-log.unexpected`); +- plants two events from a plainly simulated intruder, Mallory McHypothetical (simulated), on every run and fails unless both are caught and evaluated reportable. -A no-finding review does not require a commit. Anomalies are recorded in [`security-review.md`](security-review.md) with a date and disposition. +The emitter's failures are covered by the evidence watchdog and the runtime signal's freshness, not by reading its logs. Nobody reads the logs by hand. ## Log access scoping (KSI-MLA-ALA) @@ -92,7 +93,7 @@ The CISA Secure-by-Design pledge has 7 goals; this system addresses or trivially Continuous improvement is mechanized through the runtime KSI signal. Drift between the deploy-time signal and the runtime signal is the primary improvement signal. Each detected drift event triggers a fix in the policy or the implementation, recorded in the git log. -The annual security review (see [`security-review.md`](security-review.md)) is the human-layer continuous improvement loop. +The Annual Security Review (`scripts/hold-security-review.py`, see [`security-review.md`](security-review.md)) is the yearly loop: it re-checks every document, the component types against the threat model, decisions, findings, incident patterns and recurring cost, and a failing item fails the run until a pull request fixes it. ## Secret management (KSI-SVC-ASM) @@ -137,7 +138,7 @@ Token threat model, sized to the system's actual blast radius. Methodology: STRI - Side-channel attacks on the underlying AWS infrastructure (inherited from AWS authorization) - Insider threat on the operator's personal endpoints (operator's laptop is outside system boundary) -**Vulnerability analysis** is automated through the SAST/SCA tools described under SA-11 (Checkov, tfsec, Dependabot). Annual review of the threat model occurs in [`security-review.md`](security-review.md). +**Vulnerability analysis** is automated through the SAST/SCA tools described under SA-11 (Checkov, tfsec, Dependabot). The Annual Security Review (`scripts/hold-security-review.py`) fails when a component type added since the previous review is not named in this threat model, so the model is kept current through pull requests ([`security-review.md`](security-review.md)). ## Communication integrity (KSI-SVC-VCM, mod-only) diff --git a/docs/boundary/boundary-classification.json b/docs/boundary/boundary-classification.json index 69d1e17c..9db60ce3 100644 --- a/docs/boundary/boundary-classification.json +++ b/docs/boundary/boundary-classification.json @@ -20,7 +20,7 @@ {"key": "audit", "zone": "system", "label": "Audit and shared keys", "match": ["aws::audit_log_trail::*", "aws::object_store::cloudtrail", "aws::kms_key::at_rest"]}, {"key": "trust-root", "zone": "system", "label": "CI/CD trust root (operator-applied bootstrap stack)", - "match": ["aws::oidc_provider::*", "aws::iam_role::deploy", "aws::iam_role::evidence_nightly", "aws::iam_role::plan", "aws::iam_group::*", "aws::iam_policy::*", "aws::object_store::tfstate", "aws::kv_table::*"]}, + "match": ["aws::oidc_provider::*", "aws::iam_role::deploy", "aws::iam_role::evidence_nightly", "aws::iam_role::incident_reports", "aws::iam_role::package_maintenance", "aws::iam_role::plan", "aws::iam_group::*", "aws::iam_policy::*", "aws::object_store::tfstate", "aws::kv_table::*"]}, {"key": "github", "zone": "external", "label": "GitHub repository, Actions and OIDC", "match": ["ext::github-repo", "ext::github-oidc"]}, {"key": "sigstore", "zone": "external", "label": "Sigstore (Fulcio CA and Rekor log)", @@ -28,7 +28,9 @@ {"key": "operator-mfa", "zone": "external", "label": "Operator MFA", "match": ["ext::duo-mfa"]}, {"key": "vuln-feeds", "zone": "external", "label": "Vulnerability metadata sources", - "match": ["ext::github-advisory-db", "ext::cisa-kev"]} + "match": ["ext::github-advisory-db", "ext::cisa-kev", "ext::first-epss", "ext::anchore-grype-db"]}, + {"key": "app-delivery", "zone": "external", "label": "Code and models the app loads in the user's browser", + "match": ["ext::jsdelivr", "ext::google-cloud-storage"]} ], "declared": [ {"key": "operator", "label": "Operator (dev machine)", "zone": "outside", "kind": "actor", @@ -49,7 +51,7 @@ }, "flows": [ {"id": "A", "label": "Operator → GitHub repository and Actions", "path": [{"declared": "operator"}, {"component": "ext::github-repo"}], - "protocol": "HTTPS 443 (TLS 1.2+)", "auth": "Password + Duo TOTP MFA (privileged)", "encryption": "In transit: TLS", "data": "Source code, IaC configuration, content"}, + "protocol": "HTTPS 443 (TLS 1.2+)", "auth": "Password + virtual TOTP MFA (privileged)", "encryption": "In transit: TLS", "data": "Source code, IaC configuration, content"}, {"id": "B", "label": "GitHub Actions → AWS APIs (deploy role)", "path": [{"component": "ext::github-oidc"}, {"component": "aws::iam_role::deploy"}], "protocol": "HTTPS 443 (TLS 1.2+, SigV4)", "auth": "GitHub OIDC → STS role; no static keys (privileged)", "encryption": "In transit: TLS", "data": "Terraform plan and apply, AWS API calls"}, {"id": "C", "label": "Deploy → S3 (site and /.well-known/)", "path": [{"component": "aws::iam_role::deploy"}, {"component": "aws::object_store::website"}], @@ -67,8 +69,50 @@ {"id": "I", "label": "Alarms → SNS topic → operator email (out)", "path": [{"component": "aws::metric_alarm::evidence*"}, {"component": "aws::notification_topic::evidence_alerts"}, {"declared": "operator-email"}], "protocol": "AWS-internal; then email (SMTP)", "auth": "Topic policy: evidence alarms only", "encryption": "At rest: CMK · email not end-to-end encrypted", "data": "Alarm metadata only (name, state, reason)"}, {"id": "J", "label": "Evidence Nightly → S3 (.well-known/vdr-*)", "path": [{"component": "ext::github-oidc"}, {"component": "aws::iam_role::evidence_nightly"}, {"component": "aws::object_store::website"}], - "protocol": "HTTPS 443 (TLS 1.2+, SigV4)", "auth": "GitHub OIDC → STS; the role can write only .well-known/vdr-* (unattended)", "encryption": "In transit TLS; at rest SSE-S3", "data": "Refreshed VDR and trend (Sigstore-signed)"}, + "protocol": "HTTPS 443 (TLS 1.2+, SigV4)", "auth": "GitHub OIDC → STS; the role can write only .well-known/vdr-* (unattended)", "encryption": "In transit TLS; at rest SSE-S3", "data": "Refreshed VDR and trend, the nightly audit-log review and the monthly recovery exercises (Sigstore-signed); the audit-log review reads CloudTrail event history with cloudtrail:LookupEvents only"}, {"id": "K", "label": "Watchdog → S3 (evidence freshness read)", "path": [{"component": "aws::event_schedule::evidence_watchdog"}, {"component": "aws::function::evidence_watchdog"}, {"component": "aws::object_store::website"}], - "protocol": "AWS-internal", "auth": "Watchdog Lambda role: s3:GetObject on the published evidence keys only", "encryption": "In transit: TLS", "data": "Published evidence timestamps; results go out as CloudWatch metrics that drive flow I's alarms"} + "protocol": "AWS-internal", "auth": "Watchdog Lambda role: s3:GetObject on the published evidence keys only", "encryption": "In transit: TLS", "data": "Published evidence timestamps; results go out as CloudWatch metrics that drive flow I's alarms"}, + {"id": "L", "label": "App user → Cognito Hosted UI (sign-in)", "path": [{"declared": "app-users"}, {"component": "aws::identity_provider::silk_reeling"}], + "protocol": "HTTPS 443 (TLS 1.2+)", "auth": "Password + required TOTP MFA; OAuth2 authorization code with PKCE", "encryption": "In transit: TLS; user records at rest encrypted by Cognito", "data": "Sign-in credentials and MFA code in; ID and access tokens out (email address in the user record)"}, + {"id": "M", "label": "App user's browser → jsDelivr (MediaPipe runtime)", "path": [{"declared": "app-users"}, {"component": "ext::jsdelivr"}], + "protocol": "HTTPS 443 (TLS)", "auth": "Anonymous public GET", "encryption": "In transit: TLS", "data": "Pinned MediaPipe JavaScript and WebAssembly in; the request carries the user's IP address and user agent only"}, + {"id": "N", "label": "App user's browser → Google Cloud Storage (pose model)", "path": [{"declared": "app-users"}, {"component": "ext::google-cloud-storage"}], + "protocol": "HTTPS 443 (TLS)", "auth": "Anonymous public GET", "encryption": "In transit: TLS", "data": "Pose-landmarker model file in; the request carries the user's IP address and user agent only"}, + {"id": "O", "label": "Site bucket → access-log bucket (S3 server access logs)", "path": [{"component": "aws::object_store::website"}, {"component": "aws::object_store::logs"}], + "protocol": "AWS-internal (S3 log delivery)", "auth": "Log bucket policy admits only the S3 logging service", "encryption": "At rest: SSE-S3", "data": "Request records for origin reads: requester IP, user agent, key, status"}, + {"id": "O2", "label": "CloudFront → access-log bucket (edge access records, 90 days)", "path": [{"component": "aws::cdn_distribution::website"}, {"component": "aws::object_store::logs"}], + "protocol": "AWS internal (CloudWatch vended-log delivery)", "auth": "Log delivery service, admitted by the log bucket policy for this account only", "encryption": "In transit TLS; at rest SSE-S3", "data": "Per request: date, time, edge location, country, method, path, status, bytes, cache result; no client IP, user agent, referrer, query string or cookie"}, + {"id": "O3", "label": "Deploy → access-log bucket (reads edge access records)", "path": [{"component": "aws::iam_role::deploy"}, {"component": "aws::object_store::logs"}], + "protocol": "HTTPS 443 (TLS 1.2+, SigV4)", "auth": "Deploy role (GitHub OIDC); read-only on the CloudFront log prefixes", "encryption": "In transit TLS; at rest SSE-S3", "data": "Edge access records in; only aggregate monthly counts of /.well-known/ and /trust/ requests are published"}, + {"id": "P", "label": "CloudTrail → CloudTrail log bucket", "path": [{"component": "aws::audit_log_trail::management"}, {"component": "aws::object_store::cloudtrail"}], + "protocol": "AWS-internal (CloudTrail delivery)", "auth": "Bucket policy admits only CloudTrail for this trail", "encryption": "At rest: SSE-S3; log-file validation on", "data": "Management events: API caller identity, source IP, action, parameters"}, + {"id": "Q", "label": "KSI emitter → its log group", "path": [{"component": "aws::function::opa_compliance"}, {"component": "aws::log_group::opa_compliance"}], + "protocol": "AWS-internal", "auth": "Lambda execution role", "encryption": "At rest: CMK", "data": "Emitter run logs (no customer data)", "note": "Failed asynchronous invocations go to the dead-letter queue (flow R)."}, + {"id": "R", "label": "KSI emitter → dead-letter queue (failed invocations)", "path": [{"component": "aws::function::opa_compliance"}, {"component": "aws::message_queue::compliance_dlq"}], + "protocol": "AWS-internal", "auth": "Lambda execution role (sqs:SendMessage on the queue only)", "encryption": "At rest: SQS-managed server-side encryption", "data": "The failed scheduled event (no customer data); kept 14 days"}, + {"id": "S", "label": "App Lambda → its log group", "path": [{"component": "aws::function::silk_reeling"}, {"component": "aws::log_group::silk_reeling"}], + "protocol": "AWS-internal", "auth": "Lambda execution role", "encryption": "At rest: CMK", "data": "Application logs: request metadata, errors"}, + {"id": "T", "label": "API Gateway → access log group", "path": [{"component": "aws::api_gateway::silk_reeling"}, {"component": "aws::log_group::silk_apigw"}], + "protocol": "AWS-internal", "auth": "Log resource policy admits API Gateway delivery", "encryption": "At rest: CMK", "data": "API access records: request ID, source IP, time, method, route, status, response length"}, + {"id": "U", "label": "Watchdog → its log group", "path": [{"component": "aws::function::evidence_watchdog"}, {"component": "aws::log_group::evidence_watchdog"}], + "protocol": "AWS-internal", "auth": "Lambda execution role", "encryption": "At rest: CMK", "data": "Watchdog run logs (artifact ages; no customer data)"}, + {"id": "V", "label": "Operator → AWS console and APIs (with TOTP MFA)", "path": [{"declared": "operator"}, {"component": "ext::duo-mfa"}, {"component": "aws::iam_group::operators"}], + "protocol": "HTTPS 443 (TLS 1.2+)", "auth": "Password + TOTP MFA (root and the operator IAM user; privileged)", "encryption": "In transit: TLS", "data": "Administrative sign-in and AWS API calls (recorded by CloudTrail, flow P)"}, + {"id": "W", "label": "Deploy and plan → Terraform state bucket", "path": [{"component": "aws::iam_role::deploy"}, {"component": "aws::object_store::tfstate"}], + "protocol": "HTTPS 443 (TLS 1.2+, SigV4)", "auth": "Deploy and plan roles (GitHub OIDC)", "encryption": "In transit TLS; at rest SSE-S3", "data": "Terraform state (configuration and resource attributes, including secret values)"}, + {"id": "X", "label": "Deploy and plan → state lock table", "path": [{"component": "aws::iam_role::deploy"}, {"component": "aws::kv_table::tflock"}], + "protocol": "HTTPS 443 (TLS 1.2+, SigV4)", "auth": "Deploy and plan roles (GitHub OIDC)", "encryption": "In transit TLS; at rest AWS-owned key", "data": "Lock ID, holder and timestamp only"}, + {"id": "Y1", "label": "Deploy and nightly → GitHub Advisory Database (Dependabot alerts)", "path": [{"component": "ext::github-repo"}, {"component": "ext::github-advisory-db"}], + "protocol": "HTTPS 443 (TLS)", "auth": "Repository token that can read Dependabot alerts", "encryption": "In transit: TLS", "data": "Open dependency alerts in (public advisory data)"}, + {"id": "Y2", "label": "Deploy and nightly → CISA KEV catalog", "path": [{"component": "ext::github-repo"}, {"component": "ext::cisa-kev"}], + "protocol": "HTTPS 443 (TLS)", "auth": "Anonymous public GET", "encryption": "In transit: TLS", "data": "KEV catalog in (public)"}, + {"id": "Y3", "label": "Deploy and nightly → FIRST EPSS scores", "path": [{"component": "ext::github-repo"}, {"component": "ext::first-epss"}], + "protocol": "HTTPS 443 (TLS)", "auth": "Anonymous public GET", "encryption": "In transit: TLS", "data": "EPSS scores file in (public)"}, + {"id": "Y4", "label": "Deploy and nightly → Grype vulnerability database", "path": [{"component": "ext::github-repo"}, {"component": "ext::anchore-grype-db"}], + "protocol": "HTTPS 443 (TLS)", "auth": "Anonymous public GET", "encryption": "In transit: TLS; checksum verified", "data": "Vulnerability database in (public)"}, + {"id": "Z", "label": "Incident Reports → S3 (.well-known/incident-*)", "path": [{"component": "ext::github-oidc"}, {"component": "aws::iam_role::incident_reports"}, {"component": "aws::object_store::website"}], + "protocol": "HTTPS 443 (TLS 1.2+, SigV4)", "auth": "GitHub OIDC → STS; the role can write only .well-known/incident-* (unattended)", "encryption": "In transit TLS; at rest SSE-S3", "data": "Incident log and IIR/OIR/FIR reports (Sigstore-signed)"}, + {"id": "Z2", "label": "Package Maintenance → S3 (certification package objects)", "path": [{"component": "ext::github-oidc"}, {"component": "aws::iam_role::package_maintenance"}, {"component": "aws::object_store::website"}], + "protocol": "HTTPS 443 (TLS 1.2+, SigV4)", "auth": "GitHub OIDC → STS; the role can write only the named certification package objects and the quarterly issue prefixes (unattended)", "encryption": "In transit TLS; at rest SSE-S3", "data": "SDR, CPO, OCR, their readable views, the quarterly issue index, issued reports and snapshots (Sigstore-signed)"} ] } diff --git a/docs/continuous-monitoring-plan.md b/docs/continuous-monitoring-plan.md index 4f7a6afa..ef57cbbc 100644 --- a/docs/continuous-monitoring-plan.md +++ b/docs/continuous-monitoring-plan.md @@ -22,30 +22,30 @@ Five mechanisms operate concurrently: **4. Evidence freshness alerting (hourly).** Published reporting must be under 24 hours old, and an alert that only lands in a GitHub notifications tab is not an alert: from 2026-09-09 to 2026-09-24 the nightly VDR refresh failed every night without reaching the operator. The evidence SLA watchdog ([`infrastructure/watchdog.tf`](../infrastructure/watchdog.tf)) runs hourly on AWS's clock, reads every artifact listed in the governed freshness configuration ([`infrastructure/schemas/freshness-config.json`](../infrastructure/schemas/freshness-config.json): the VDR, the runtime signal, the nightly's status beacon `vdr-status.json` and every other signed output under `/.well-known/`) from the site bucket, and publishes the VDR's and runtime signal's ages, the nightly's last result and the number of artifacts past their window as CloudWatch metrics. Four alarms page the operator by email through a CMK-encrypted SNS topic, with a recovery email when each clears: the VDR older than its window (24 hours), the runtime signal older than its window (26 hours), the nightly failed or silent for 26 hours, and any listed artifact past its governed window (24 hours for nightly evidence, 26 for the runtime signal and beacon, 30 days for deploy-generated artifacts and the operator-run corroboration). Missing data counts as a breach, so a dead watchdog pages too. The nightly runs twice a day, which keeps the VDR well inside the 24-hour policy so the alarm fires on real misses, not on GitHub's late crons. Response: [`docs/runbooks/evidence-sla-alarm.md`](runbooks/evidence-sla-alarm.md). Frequency: hourly. -**5. Annual structural review.** Documented in [`docs/security-review.md`](security-review.md). The review re-examines (a) cost/benefit of risk-accepted items, (b) whether the threat model still holds, (c) whether the conscious trade-offs in the README still apply. Frequency: annual, plus after any Transformative significant change per SCN. +**5. Annual Security Review (generated).** `scripts/hold-security-review.py`, run by `package-maintenance.yml` on its due date, re-checks every document, the component types against the threat model, decisions, findings, incident patterns and the recurring cost of every billable line, with a simulated reviewer's sign-off (DEC-194), and publishes `/.well-known/security-review-<date>.json`; `scripts/check-scheduled-review.py` fails the run when one is overdue. A Transformative significant change (SCN) revisits the threat model and trade-offs in its own pull request. Detail: [`docs/security-review.md`](security-review.md). -**6. Independent corroboration (operator-run, at least every 30 days).** [`tools/boundary-map/corroborate.py`](../tools/boundary-map/corroborate.py) checks the published evidence against sources the pipeline does not control: RAMPART on TAP (The Analogy Platform) reading AWS and GitHub with read-only credentials, and FedRAMP's rules read directly. It compares the boundary map with the live account, re-verifies every published signature with an independent Sigstore verifier, matches each signing run to GitHub's record of it, compares the configuration the artifacts claim with what AWS reports, checks the runtime signing key in KMS against its published and pinned copies, compares open Dependabot alerts with the VDR, and checks the claimed KSIs against FedRAMP's current catalog. A section that could not be checked is reported as such, never as agreement. The signed report is published at `/.well-known/boundary-corroboration.json`; the trust center shows each section and asks for attention on any difference, any unchecked section, or a report older than 30 days. Detail: [`tools/boundary-map/README.md`](../tools/boundary-map/README.md). Frequency: at least every 30 days. +**6. Independent corroboration (operator-run, at least every 30 days; one of the three recurring human acts of DEC-195).** [`tools/boundary-map/corroborate.py`](../tools/boundary-map/corroborate.py) checks the published evidence against sources the pipeline does not control: RAMPART on TAP (The Analogy Platform) reading AWS and GitHub with read-only credentials, and FedRAMP's rules read directly. It compares the boundary map with the live account, re-verifies every published signature with an independent Sigstore verifier, matches each signing run to GitHub's record of it, compares the configuration the artifacts claim with what AWS reports, checks the runtime signing key in KMS against its published and pinned copies, compares open Dependabot alerts with the VDR, and checks the claimed KSIs against FedRAMP's current catalog. A section that could not be checked is reported as such, never as agreement. The signed report is published at `/.well-known/boundary-corroboration.json`; the trust center shows each section and asks for attention on any difference, any unchecked section, or a report older than 30 days. Detail: [`tools/boundary-map/README.md`](../tools/boundary-map/README.md). Frequency: at least every 30 days. ## Reporting These artifacts are published continuously at `/.well-known/`: - `ksi-signal.json` — the FedRAMP 20x KSI signal (Sigstore-signed); per-deploy emission -- `ksi-signal-runtime.json` — the daily runtime revalidation, signed with an asymmetric KMS key (ECC NIST P-256); the signature is carried in `provenance.attestation` and verifiable against `runtime-signing-pubkey.pem` (POAM-002) +- `ksi-signal-runtime.json` — the daily runtime revalidation, signed with an asymmetric KMS key (ECC NIST P-256); the signature is carried in `provenance.attestation` and verifiable against `runtime-signing-pubkey.pem` (DEC-002, remediated) - `runtime-signing-pubkey.pem` — the public key for verifying the runtime signal's signature - `security-decision-record.json` — the CR26 Security Decision Record (per-KSI and per-Rev5-control records; replaces the SSP), Sigstore-signed with an in-toto attestation; per-deploy emission - `certification-package-overview.json` — the CR26 Certification Package Overview, Sigstore-signed; per-deploy emission - `vdr-report.json` — the FedRAMP 20x VDR report; per-deploy emission - `vdr-report.md` — human-readable VDR rendering (VER-TFR-MHR) -- `ongoing-certification-report.json` / `.md` — the quarterly Ongoing Certification Report (CCM-OCR-AVL), Sigstore-signed; carries the eight required summaries plus the target dates for the next report (CCM-OCR-NRD) and next quarterly review (CCM-QTR-NRD) +- `ongoing-certification-report.json` / `.md` — the quarterly Ongoing Certification Report (CCM-OCR-AVL), Sigstore-signed; carries the eight required summaries plus the target dates for the next report (CCM-OCR-NRD) and next Quarterly Review (CCM-QTR-NRD) All artifacts carry FedRAMP-namespaced provenance (deploy chain identity, system-id, ownership block). The deploy-time signal is signed via Sigstore keyless with verification anchored in the public Rekor transparency log; an external consumer can verify integrity via `cosign verify-blob` without trusting this site. -**Quarterly Ongoing Certification Report.** CR26 CCM is a quarterly cycle, not a stream. `ongoing-certification-report.json` (CCM-OCR-AVL) is regenerated on every deploy from the system's own artifacts and carries the eight required summaries — changes to certification data (from the SCN register), planned changes (open POA&M items), accepted vulnerabilities (from the VDR), transformative changes, updated recommendations, agencies using the product (none), a FedRAMP-Reportable-Incident attestation (none — no federal data), and lessons learned (none) — plus the next-report and next-review target dates. The five monitoring mechanisms above feed it; per-deploy emission keeps it current and overshoots the 3-month floor. +**Quarterly Ongoing Certification Report.** CR26 CCM is a quarterly cycle, not a stream. `ongoing-certification-report.json` (CCM-OCR-AVL) is regenerated on every deploy from the system's own artifacts and carries the eight required summaries — changes to certification data (from the SCN register), planned changes (from the decision register and the SCN register), accepted vulnerabilities (from the VDR), transformative changes, updated recommendations, agencies using the product (none), a FedRAMP-Reportable-Incident attestation (none — no federal data), and lessons learned (none) — plus the next-report and next-review target dates. The five monitoring mechanisms above feed it; per-deploy emission keeps it current and overshoots the 3-month floor. -This implements the **publication half** of FedRAMP 20x Collaborative Continuous Monitoring (CCM): every monitoring artifact is publicly retrievable and signature-verifiable, and the quarterly Ongoing Certification Report is produced as a distinct deliverable, so any reviewer can fetch and verify the current posture without trusting this site. The relationship-dependent rules — the synchronous Quarterly Review (CCM-QTR-MTG), the feedback channel (CCM-OCR-FBM), and the anonymized feedback summary (CCM-OCR-AFS) — are N/A absent a consuming agency, as the scope note below explains. +This implements the **publication half** of FedRAMP 20x Collaborative Continuous Monitoring (CCM): every monitoring artifact is publicly retrievable and signature-verifiable, and the quarterly Ongoing Certification Report is produced as a distinct deliverable, so any reviewer can fetch and verify the current posture without trusting this site. The relationship-dependent rules — the Quarterly Review (CCM-QTR-MTG), the feedback channel (CCM-OCR-FBM) and the anonymized feedback summary (CCM-OCR-AFS) — are built and run with simulated parties (DEC-194): `package-maintenance.yml` holds each Quarterly Review on its calendar date with simulated attendees, collects simulated feedback, and writes the anonymized summary into the next report. -**Honest scope — the collaborative half is N/A here, not done.** CCM is a two-party relationship: a CSP publishes, and a *consuming agency / authorizing official* reviews on an agreed cadence, raises significant-change and finding concerns, and makes risk decisions that feed back into the CSP's posture. This system has **no agency sponsor and no consuming agency** (it is a public proof of concept with no federal data). So the relationship-dependent obligations — the agency-side review cadence, the collaborative finding-disposition loop, the authorizing-official sign-off — are **not applicable**, because there is no counterparty to exercise them. What is built is the mechanism a CSP would use to *support* CCM; what is absent is the relationship that gives it meaning. Claiming CCM is "satisfied" would overstate it: the closed monitoring loop does not exist, and cannot, until a consuming party is onboarded. +**Honest scope: the collaborative half runs against simulated parties.** CCM is a two-party relationship: a CSP publishes, and a *consuming agency / authorizing official* reviews on an agreed cadence, raises significant-change and finding concerns, and makes risk decisions that feed back into the CSP's posture. This system has **no agency sponsor and no consuming agency**, and the operator engages none (DEC-194). The mechanisms a CSP would use are built and exercised on schedule against simulated agencies, a simulated FedRAMP and a simulated assessor, each labelled as simulated where it is published. The relationship itself does not exist: no real party reviews the output or makes a risk decision from it. ## Vulnerability Detection and Response (VDR) cadence (Class C) @@ -82,19 +82,22 @@ The compensating controls that stand in for a second human are **automated and n Together these provide *machine* independence in place of *human* independence: the operator can author changes but cannot unilaterally push an unreviewed, noncompliant, or tampered state to production without the automation refusing. This bounds the sole-operator risk; it does not eliminate the structural single-person constraint, which is recorded here as a residual. -## Effectiveness review +## Effectiveness checks -Quarterly review of the runtime KSI signal against the deploy-time signal: are they reconciling? Are any drift events recorded? Are any findings persisting past their Class C SLAs? +Automated; nobody reviews the signals by hand (DEC-195 lists the only recurring human acts): -Annual structural review per [`docs/security-review.md`](security-review.md). +- The evidence nightly checks the runtime KSI signal against the deploy-time inventory on every run (`scripts/reconcile.py`, invariant (n)) and fails on a gap; the runtime emitter's validations record drift. +- A finding past its Class C deadline is blocked by the VDR's deadline gate (`scripts/build-vdr-report.py`). +- The audit-log review (`scripts/audit-log-review.py`) runs every night, and the recovery exercise (`scripts/hold-recovery-exercise.py`) every month, with an annual simulated tabletop. +- The Annual Security Review is generated per [`docs/security-review.md`](security-review.md). ## Reference: 20x rules and NIST controls satisfied -- FedRAMP 20x Collaborative Continuous Monitoring (CCM-OCR-* and CCM-QTR-* rules) — the quarterly Ongoing Certification Report (`CCM-OCR-AVL`) and the next-report/next-review dates (`CCM-OCR-NRD` / `CCM-QTR-NRD`) are produced and published; mechanisms 1-4 feed it. The synchronous Quarterly Review (`CCM-QTR-MTG`), feedback channel (`CCM-OCR-FBM`), and feedback summary (`CCM-OCR-AFS`) are **N/A** absent a consuming agency (see scope note above) +- FedRAMP 20x Collaborative Continuous Monitoring (CCM-OCR-* and CCM-QTR-* rules) — the Ongoing Certification Report (`CCM-OCR-AVL`) and the dates of the next report and the next Quarterly Review (`CCM-OCR-NRD` / `CCM-QTR-NRD`) are produced and published; mechanisms 1-4 feed it. The Quarterly Review (`CCM-QTR-MTG`), feedback channel (`CCM-OCR-FBM`), and feedback summary (`CCM-OCR-AFS`) are held and built by `package-maintenance.yml` with simulated parties (DEC-194) - FedRAMP 20x Vulnerability Detection and Response (VDR-* rules) — covered by mechanism 2 - FedRAMP 20x Significant Change Notifications (SCN-* rules) — covered by SCN PR tag - KSI-MLA family (Monitoring, Logging, Auditing) — covered across all mechanisms -- KSI-SVC-EIS (Continuous Improvement) — covered by drift detection + annual review +- KSI-SVC-EIS (Continuous Improvement) — covered by drift detection and the generated Annual Security Review (`scripts/hold-security-review.py`) - NIST CA-7 (Continuous Monitoring) — primary control implemented by this plan - NIST CA-7.4 (Risk Monitoring) — covered by VDR cadence - NIST CM-3 (Configuration Change Control) — covered by SCN diff --git a/docs/cr26-applicability.md b/docs/cr26-applicability.md index 0d20e28d..aba042c6 100644 --- a/docs/cr26-applicability.md +++ b/docs/cr26-applicability.md @@ -11,20 +11,23 @@ This system is a **self-attested proof of concept** — one operator, no agency | **MAS** — Minimum Assessment Scope | Every inventory component carries a FIPS 199 category and information-flow tag; third-party AWS resources documented at the inheritance level | `MAS-CSO-IIR/FLO/TPR` (`MDI`/`SUP` N/A — no federal customer data, no supplemental materials) | | **SCN** — Significant Change Notifications | Commit-time `SCN-Type` gate (routine/adaptive/transformative/emergency), per-change SCN records + register, full transformative timeframe set | `SCN-CSO-*`, `SCN-RTR-NNR`, `SCN-ADP-NTF`, `SCN-TRF-NIP/NFP/NAF/NAV/UPD/TPR` | | **VDR / VER** — Vulnerability Detection, Evaluation & Reporting | Per-deploy and nightly VDR report (PAIN/IRV/LEV, Class C SLA, KEV gate) + human-readable rendering; from it, the FedRAMP-schema Vulnerability Detail Report (`vdr-detail-report.json`), Accepted Vulnerability Info (`vdr-accepted-vulnerabilities.json`) and history (`vdr-history.json`), each validated against the vendored 2026-06-24 schema before it is written; 14-day drift cadence | `VDR-TFR-PVR/KEV/PDD`, `VER-EVA-*`, `VER-RPT-VDT/AVI/PER`, `VER-TFR-MHR/MRH/IRI/NRI` | -| **CCM** — Collaborative Continuous Monitoring | Quarterly Ongoing Certification Report (8 summaries + incident attestation) + next-report/review dates | `CCM-OCR-AVL/NRD`, `CCM-QTR-NRD` | -| **CDS** — Certification Data Sharing | Certification-overview package (15 fields), service list, availability feed, policy index — all signed + human-readable | `CDS-CSO-PUB/SVC/FID/CBF/AVR/IRP` | +| **CCM** — Collaborative Continuous Monitoring | Quarterly Ongoing Certification Report (8 summaries + incident attestation) + the dates of the next report and Quarterly Review | `CCM-OCR-AVL/NRD`, `CCM-QTR-NRD` | +| **CDS** — Certification Data Sharing | The CDS fields published in the Certification Package Overview (the separate certification-overview package is retired), service list, availability feed, policy index, trust manifest — all signed + human-readable | `CDS-CSO-PUB/SVC/FID/CBF/AVR/IRP` | | **CMU** — Cryptographic Module Use | Each module documented with CMVP-validation status (the authorization-boundary FIPS section); validated modules used for sensitive crypto | `CMU-CSO-CMD/UVM` (`CAT` N/A — no agency tenants) | | **SDR** — Security Decision Record | Per-KSI records (explanation, verification, validation, artifacts) + metric history; the 20x SSP replacement | `SDR-CSO-FRR/MTD`, `SDR-CSX-KSI/KMT` | | **CPO** — Certification Package Overview | Rollup of CDS/MAS/CMU/IVV + named accountable official; with the SDR, the SSP replacement | `CPO-CSO-OVR/MTD`, `CPO-CSX-CPM` | | **SCG** — Secure Configuration Guide | Public, versioned guide for top-level administrative accounts; secure-by-default provisioning | `SCG-CSO-RSC/PUB/SDF`, `SCG-ENH-*` | -The POA&M is retired (2026-11-04): CR26 has no POA&M. Open findings and their deadlines are in the VDR report; vulnerabilities not remediated within the maximum period are reported as Accepted (`VER-RPT-AVI`); and every human decision about a finding (false positive, accepted risk, operational requirement, remediation history) is a record in `data/decisions.json`, read by the VDR builder, the vulnerability gate, reconciliation and the trust center. The published `oscal-poam.json` was deleted. The OSCAL Rev 5 SSP is retired too (2026-11-05): CR26 has no SSP. The Security Decision Record and the Certification Package Overview replace it. CR26 gives the two certification types the **same rule families**; the only material difference is the evidence shape. The Rev5 Security Decision Record summarizes each applicable Rev5 control (`SDR-CSF-CTF`, "for each applicable Rev5 Control"), and the 20x record summarizes each Key Security Indicator (`SDR-CSX-KSI`). `scripts/build-sdr.py` produces both in one record (`rev5_controls` and `rule_records`) from one control projection (`scripts/_controls.py`), so the automation is demonstrated under both paradigms. The published `oscal-ssp.json` was deleted. The remaining Rev5-only IDs (`IVV-CSF-*`, `CDS-CSF-TCM`, `VDR-TFR-MVF`) are control-vs-KSI assessment variants; IVV is N/A here regardless, and the Class C VDR remediation timeframes are identical across both tracks. +The POA&M is retired (2026-11-04): CR26 has no POA&M. Open findings and their deadlines are in the VDR report; vulnerabilities not remediated within the maximum period are reported as Accepted (`VER-RPT-AVI`); and every human decision about a finding (false positive, accepted risk, operational requirement, remediation history) is a record in `data/decisions.json`, read by the VDR builder, the vulnerability gate, reconciliation and the trust center. The published `oscal-poam.json` was deleted. The OSCAL Rev 5 SSP is retired too (2026-11-05): CR26 has no SSP. The Security Decision Record and the Certification Package Overview replace it. CR26 gives the two certification types the **same rule families**; the only material difference is the evidence shape. The Rev5 Security Decision Record summarizes each applicable Rev5 control (`SDR-CSF-CTF`, "for each applicable Rev5 Control"), and the 20x record summarizes each Key Security Indicator (`SDR-CSX-KSI`). `scripts/build-sdr.py` produces both in one record (`rev5_controls` and `rule_records`) from one control projection (`scripts/_controls.py`), so the automation is demonstrated under both paradigms. The published `oscal-ssp.json` was deleted. The remaining Rev5-only IDs (`IVV-CSF-*`, `CDS-CSF-TCM`, `VDR-TFR-MVF`) are control-vs-KSI assessment variants that this 20x system does not use, and the Class C VDR remediation timeframes are identical across both tracks. ## Not Applicable (structurally unavailable to an unsponsored, unlisted, self-attested system) -- **IVV — Independent Verification and Validation.** `IVV-CSO-FIA` (Class C MUST) requires a persistent independent assessment by a **FedRAMP Recognized independent assessment service** (the artifact formerly called a 3PAO) or by FedRAMP. This system is self-attested and has engaged no such assessor, so the *independent* half cannot be met. The provider-side verification and validation an assessor would consume **are** produced (in the Security Decision Record); the independent half is unmet by design and recorded N/A. -- **MKT — Marketplace Listing.** `MKT-IIP-AGU` requires demonstrating the offering is for agency use within 44 USC § 3506 scope, and the rule text is explicit that *"services used by private companies to meet other compliance requirements (such as CMMC) that do not also meet one of the above use cases are outside the scope of FedRAMP."* There is no agency use case and no intent to list, so MKT is N/A by statutory scope. -- **AFC — Addressing FedRAMP Communication.** `AFC-CSO-INB` and the rest require maintaining a FedRAMP Security Inbox and handling FedRAMP correspondence. With no listing and no sponsor, FedRAMP has no reason to correspond, so there is no channel to maintain. AFC's grace period already ended **2026-07-01**; it is recorded N/A absent a sponsor. -- **IEC — Incident Evaluation and Communication.** A FedRAMP Reportable Incident under `IEC-CSO-EFR` is triggered by an effect on the confidentiality or integrity of **federal customer data**. This system holds none, so no incident is FedRAMP-reportable and the `IEC-CSO-IIR` reporting clocks never start. The evaluation step still runs — the VDR aggregator assigns a PAIN rating to every finding — so the machinery is in place the moment federal data ever enters scope. +- **MKT — Marketplace Listing.** FedRAMP scopes the Marketplace rules to providers seeking a listing in the FedRAMP Marketplace, and no listing is sought, by statutory scope: `MKT-IIP-AGU` requires demonstrating the offering is for agency use within 44 USC § 3506 scope, and the rule text is explicit that *"services used by private companies to meet other compliance requirements (such as CMMC) that do not also meet one of the above use cases are outside the scope of FedRAMP."* There is no agency use case, so the offering is outside that scope and no listing request is made. The rule records `MKT-CSO-MLR` and `MKT-CSO-PML` give the same reason. -These four are N/A because of *what this system is*, not because of an engineering gap. If the system were ever sponsored, listed, assessed, or handling federal data, each would activate, and the mechanisms above (the SDR's V&V evidence, the CDS overview package, the PAIN evaluation) are the inputs those activated obligations would consume. +MKT is N/A because of *what this system is*, not because of an engineering gap. If the system were ever sponsored, listed or handling federal data, it would activate, and the certification data under `/.well-known/` (the CPO, the SDR, the VDR reports) is the input a listing would consume. + +**IVV — Independent Verification and Validation** is no longer recorded N/A. No FedRAMP Recognized independent assessment service (the artifact formerly called a 3PAO) has assessed this system. The assessor port is exercised instead: every deploy is assessed by a *simulated* assessor, a workflow in this repository signing under its own identity, whose signed results are published at `/.well-known/simulated-assessment.json` and quoted in the Security Decision Record. It is labelled as simulated and is not a FedRAMP assessment. + +**AFC — Addressing FedRAMP Communication** is no longer recorded N/A (operator's decision, 2026-11-05): it is implemented against a *simulated* FedRAMP Security Inbox. The inbox logic (`scripts/_fsi.py`) runs on every deploy over committed synthetic messages and publishes `/.well-known/fedramp-inbox-simulation.json`, labelled as a simulation; no mail is received or sent, and the published contact sends FedRAMP to the operator on LinkedIn. See `docs/runbooks/fedramp-security-inbox.md`. + +**IEC — Incident Evaluation and Communication** is not recorded N/A either. This system holds no federal customer data, so in practice no incident is FedRAMP-reportable, but every incident is evaluated and recorded in `data/incidents.json`, and reportable ones get Initial, Ongoing and Final reports in FedRAMP's schema, on the Class C clocks, published under `/.well-known/` and delivered to *simulated* FedRAMP and agency recipients (`/.well-known/incident-deliveries.json`; nothing is sent). Exercised 2026-11-05 with simulated incidents marked as exercises; see `docs/incident-response.md`. diff --git a/docs/incident-response.md b/docs/incident-response.md index 6a3f8f34..224fd14a 100644 --- a/docs/incident-response.md +++ b/docs/incident-response.md @@ -15,9 +15,10 @@ In-scope incidents: Out of scope: -- Any incident involving federal customer data, end-user accounts, or downstream agencies — this system has none of those - Service-level incidents around availability promises to anyone, since none exist +Federal customer data, end-user accounts and downstream agencies: this system has none, so no incident here is expected to be a FedRAMP Reportable Incident. Every incident is still evaluated for it (step 2 below) and the determination is recorded, because the evaluation is what the rules ask for, and because a wrong assumption would otherwise go unrecorded. + ## Detection Active detection sources: @@ -25,21 +26,38 @@ Active detection sources: - **GitHub:** Dependabot vulnerability alerts, secret scanning push protection, security advisories — all auto-emailed to the repository owner - **AWS:** root-account email for billing anomalies, AWS Health Dashboard, CloudTrail (account-wide) - **The runtime KSI emitter:** publishes `/.well-known/ksi-signal-runtime.json` daily; drift against the deploy-time signal is the strongest single drift indicator the system produces -- **The evidence SLA watchdog:** CloudWatch alarms email the operator through SNS when the published VDR passes 24 hours old, the runtime signal passes 26 hours, or the evidence nightly fails or stops reporting. Response steps: [`docs/runbooks/evidence-sla-alarm.md`](runbooks/evidence-sla-alarm.md) +- **The evidence SLA watchdog:** five CloudWatch alarms email the operator through SNS: when the published VDR is older than its governed freshness window, the runtime signal is older than its window, the evidence nightly fails or stops reporting, any published `/.well-known/` artifact is past its window or unreadable, or an incident report is past its Class C deadline (`infrastructure/watchdog.tf`; windows in `infrastructure/schemas/freshness-config.json`). Response steps: [`docs/runbooks/evidence-sla-alarm.md`](runbooks/evidence-sla-alarm.md) - **External report:** the mailbox listed in [`/.well-known/security.txt`](../website/.well-known/security.txt) - **Personal vigilance:** reading the actual site ## Triage and response procedures 1. **Confirm.** Compare the runtime KSI signal at `/.well-known/ksi-signal-runtime.json` against the deploy-time signal. Any unexplained `result: "fail"` validation, or any component drift, is high-confidence signal of a real change. -2. **Contain.** - - **Credential compromise (AWS):** rotate the IAM access keys via the IAM console; revoke any active sessions; rotate the GitHub Actions secret holding the credentials. +2. **Record and evaluate FedRAMP reportability (IEC-CSO-EFR).** Add the incident to [`data/incidents.json`](../data/incidents.json) with `detected_at`, `detection_source` and an `evaluation`: when it was evaluated, `reportable` true or false, the `basis` (`IEC-CSO-EFR`, or `VER-TFR-IRI` / `VER-TFR-NRI` for a vulnerability), the `reason`, and the federal customer data considered. Does it affect, or is it likely to affect, the confidentiality or integrity of federal customer data (data an agency or its users supply to the service, not account information or telemetry)? If yes it is a FedRAMP Reportable Incident: continue with [Reporting](#reporting-fedramp-reportable-incidents-iec) in parallel with containment. Push the record; the incident log republishes within minutes. +3. **Contain.** + - **Credential compromise (AWS):** rotate the operator IAM user's access keys via the IAM console and revoke the CI roles' active sessions. CI authenticates through OIDC and holds no stored AWS keys, so there is no GitHub secret to rotate. - **Credential compromise (GitHub):** revoke any compromised PATs; rotate the workflow's `GITHUB_TOKEN` is automatic per-run; reset OAuth grants if external apps are involved. - **Content compromise:** revert via `git`, push to `main`, and approve the `prod` deploy. S3 versioning preserves the prior state; CloudFront invalidation refreshes the edge. - **Supply-chain compromise:** pin the offending dependency to a known-good version, redeploy, and file a Dependabot suppression if the alert source is the GitHub Advisory Database. -3. **Eradicate.** Identify the root cause (credential, code, or config) and patch it. Confirm the patch holds via a fresh approved deploy. -4. **Recover.** Verify the runtime signal returns to clean. Verify `cosign verify-blob` still passes against the new signal and bundle. Confirm the site is reachable end-to-end. -5. **Lessons learned.** Append an after-action entry to the section below. +4. **Eradicate.** Identify the root cause (credential, code, or config) and patch it. Confirm the patch holds via a fresh approved deploy. +5. **Recover.** Verify the runtime signal returns to clean. Verify `cosign verify-blob` still passes against the new signal and bundle. Confirm the site is reachable end-to-end. +6. **Lessons learned.** Append an after-action entry to the section below. + +## Reporting FedRAMP Reportable Incidents (IEC) + +_AI-drafted (2026-11-05) to describe what is now built; for the operator's review._ + +Reporting is automated from the incident register. A person records facts; the pipeline renders, validates, signs, publishes and keeps the clocks. + +- **Register.** [`data/incidents.json`](../data/incidents.json), read through `scripts/_incidents.py` (fails closed; shape in `infrastructure/schemas/incidents.schema.json`). Each report is an entry in the incident's `reports` list (`Initial`, then `Ongoing`, then `Final`) with the time it is issued and the items it sets: description, functional impact, recovery plan, likely affected agencies, observed activity, indicators of compromise, related CVEs, root cause, response and recovery activities, milestones. A report restates everything set before it. +- **Rating.** Until an `estimates` entry exists, the incident is rated N5 (`IEC-CSO-DPR`). An estimate (`IEC-CSO-EFI`) records the customer effect (minimal, narrow, disruptive, debilitating), whether one agency or more than one is likely affected, the reason and the time; the register refuses a rating that is not the one the rules give for that combination (N1 minimal, N2 narrow, N3 disruptive on one agency, N4 debilitating on one or disruptive on several, N5 debilitating on several). +- **Clocks.** Read from FedRAMP's Class C rules: the Initial report is due from the evaluation, each Ongoing report from the previous report until the incident is resolved, and the Final report from `recovery_complete_at` (hours at N3-N5; 24 hours or one business day at N1-N2; business days skip weekends, and holidays are counted, which can only make a deadline earlier). The rating in force when each clock starts sets its length. +- **Build and publish.** `scripts/build-incident-report.py` writes each report in FedRAMP's incident report schema (`incident-<ID>-<NN>-<type>.json`, validated before it is written) and the incident log (`incident-reports.json` and `.md`: every incident, its evaluation and reason, its rating history, each report with its sha256 and what changed, and each clock). `.github/workflows/incident-reports.yml` runs it on every push of the register to `main`, by hand, twice a day and after each nightly VDR refresh; it signs, redaction-gates and publishes under `/.well-known/incident-*` with a role that can write nothing else. Every deploy republishes the same set. +- **Alarms.** The workflow's last step fails, and raises a GitHub issue, when a report is past its deadline. The evidence SLA watchdog reads the published log hourly and pages by email (`incident-report-overdue`, [`runbooks/evidence-sla-alarm.md`](runbooks/evidence-sla-alarm.md)). +- **Vulnerabilities as incidents.** The operator adopts `VER-TFR-IRI` and `VER-TFR-NRI` (`policy.adopted_vulnerability_rules`). The VDR triage policy names each finding they cover; until an unresolved incident in the register lists it under `findings`, its Initial report is due from the finding's first evaluation at N5, so the alarms fire. Open the incident with basis `VER-TFR-IRI` or `VER-TFR-NRI` and the finding's tracking ID or CVE. Reconciliation invariant (m) fails a build whose open incident names a finding the VDR no longer carries: close it with a Final report. +- **Delivery is simulated.** FedRAMP and the affected agencies are "all affected parties" under the rules. This system has no certification and no agency customers, so they are simulated recipients: on every deploy and every run of the incident reports workflow, `scripts/deliver-incident-reports.py` reads back each report the log lists, checks its sha256 and FedRAMP's schema, and records its "delivery" to "FedRAMP Incident Desk (simulated)" and to each affected agency (simulated) in `/.well-known/incident-deliveries.json`. A delivery that fails stops publication. Nothing is sent to anyone. +- **The publisher's role is proved on every deploy.** Before the Security Decision Record is built, the deploy job assumes the incident reports role (`scripts/check-incident-role.py`); if it cannot, the deploy stops. +- **Exercises.** A simulated incident is recorded with `exercise: true` and is published marked as one. Exercised 2026-11-05: `INC-2026-001` (a simulated internet-reachable N5 vulnerability: Initial, two Ongoing and a Final report on a simulated timeline, all on time; rated N5 by default, then estimated N3) and `INC-2026-002` (a simulated page change, evaluated not reportable with its reason). `tests/test_incidents.py` runs the same exercise through the builder on every `make check`. ## After-action reports (KSI-INR-AAR) @@ -77,7 +95,7 @@ Response procedure: 4. **Preserve evidence.** Record the timeline, the surface, and the actions taken before the public surface is updated. Record in the after-action template. 5. **Notify if applicable.** External notification is generally not required for a personal site; this section exists for the case where it ever is. -(IR-9.2) Training: spillage scenarios are part of the annual review of this runbook (see [`docs/training-log.md`](training-log.md), KSI-CED-RAT section). +(IR-9.2) Training: spillage scenarios are part of the generated training packet's fixed core (`scripts/_training.py`; see [`docs/training-log.md`](training-log.md), KSI-CED-RAT section), taken by a simulated trainee whenever the packet changes. (IR-9.3) Post-spill operations: the spillage scope is bounded by the public-static-site surface. After containment, normal site operation continues; there is no production environment to quarantine because the production environment is the public site itself. @@ -91,23 +109,23 @@ CR26 `SCN-CSO-EMG` permits the operator to execute significant changes — inclu **What gets bypassed.** During an emergency the operator may: -- Push directly to `main` without the usual SCN-Type categorization deliberation (an `emergency` label is still required on the commit message — see below). +- Merge without the usual categorization deliberation (an `SCN-Type: emergency` evaluation is still required — see below). - Skip the standard advance-notification timing for Adaptive (`SCN-ADP-NTF`, 10 business days) or Transformative (`SCN-TRF-NIP`/`NFP`/`NAF`/`NAV`, 30 / 10 / 5 / 5 business days, plus the 30-business-day documentation update in `SCN-TRF-UPD`) changes. - Defer the threat-model review and per-control implementation-statement updates that a Transformative change would normally trigger. **What still applies.** During and after an emergency the operator must: -1. Tag the commit message with `SCN-Type: emergency` so the SCN audit record reflects the emergency disposition. The CI workflow recognizes `emergency` as a fourth valid SCN-Type value alongside `routine-recurring`, `adaptive`, and `transformative`. +1. Carry `SCN-Type: emergency`, a one-line `SCN-Rationale:` and the `SCN-Record:` the retroactive record will use in the pull request description (or the commit message of a direct push), so the evaluation log records the emergency disposition. The `scn-tag` check accepts it and says the record is due. 2. Follow the rest of this IR runbook: detect, contain, eradicate, recover, after-action. -3. Within 5 business days of incident closure, retroactively produce the SCN materials that would have been produced in advance for the equivalent non-emergency change (per `SCN-CSO-EMG`): summary of the change, summary of new risks identified, copy of the security impact analysis, plan for any verification or assessment of impacted KSIs. +3. Within 5 business days, retroactively produce the SCN materials that would have been produced in advance for the equivalent non-emergency change (per `SCN-CSO-EMG`): summary of the change, summary of new risks identified, copy of the security impact analysis, plan for any verification or assessment of impacted KSIs. Count the 5 business days from the day the emergency change merged. The materials are a row in `docs/scn/scn-register.csv` with `emergency` = `yes` and the change in `evaluation_prs`, plus its record; the next deploy publishes them, which is the notification to all necessary parties. The scheduled SCN deadline check (`.github/workflows/scn-deadlines.yml`) fails and raises an issue if the record is not in the register within 5 business days of the emergency change merging, and the published index marks each retroactive notice against that deadline. 4. Append an after-action entry to the section above with the emergency-procedure invocation noted in the timeline. -5. Reopen the threat model in `docs/architecture-decisions.md` if the emergency change altered the threat surface, and update before the next security review. +5. Reopen the threat model in `docs/architecture-decisions.md` if the emergency change altered the threat surface, and update it in a follow-up pull request; the Annual Security Review (`scripts/hold-security-review.py`) fails while a component type added since the previous review is not named there. -**Documentation evidence.** Emergency-change procedures are documented in this section, in `docs/policies/cm-policy.md` (referenced under SCN integration), and in the `.github/workflows/scn-tag.yml` validator (which accepts `emergency` as a valid tag). Together these satisfy `SCN-CSO-EMG`'s "procedures should be documented in the FedRAMP Certification package" requirement. +**Documentation evidence.** Emergency-change procedures are documented in this section, in `docs/policies/cm-policy.md` (referenced under SCN integration), in the `.github/workflows/scn-tag.yml` gate (which accepts `emergency`), and in the Certification Package Overview, which links this section. Together these satisfy `SCN-CSO-EMG`'s "procedures should be documented in the FedRAMP Certification package" requirement. ## Pattern review (KSI-INR-RPI) -KSI-INR-RPI calls for persistent review of past incidents for patterns. With zero incidents to date, the review is short. The cadence is annual, conducted as part of [`security-review.md`](security-review.md). When the incident count is greater than zero, the review will look for: repeated root causes, common detection-time gaps, and any patterns that suggest systemic rather than individual fixes. +KSI-INR-RPI calls for persistent review of past incidents for patterns. It is generated: the Annual Security Review (`scripts/hold-security-review.py`, [`security-review.md`](security-review.md)) groups the incidents of the last 12 months by their evaluation basis, exercises excluded, and fails when a basis recurs, so a systemic cause is fixed in a pull request rather than noted in a meeting. Each incident's own after-action record is written when it closes. ## Escalation @@ -117,5 +135,5 @@ Single-tier. Author → author. External escalations: - **GitHub Support** — if the issue is GitHub-side (account, repo, workflow infrastructure) - The mailbox in `security.txt` for acknowledging external reporters -There is no actual FedRAMP authorization in scope, so the FedRAMP Security Inbox (FSI) and Incident Communications Procedures (ICP) do not apply. +There is no actual FedRAMP certification in scope. Incident reports under the FedRAMP Incident Evaluation and Communication rules are generated and published as described above; they are not sent. The FedRAMP Security Inbox (FSI) is simulated for this proof of concept: no mail is received or sent, and its published contact directs FedRAMP to the operator on LinkedIn (`docs/runbooks/fedramp-security-inbox.md`). diff --git a/docs/ksi-signal.md b/docs/ksi-signal.md index 37017d26..035ded26 100644 --- a/docs/ksi-signal.md +++ b/docs/ksi-signal.md @@ -94,7 +94,6 @@ These queries are the actual job of an Authorizing Official, an SRE handling a C "provenance": { "builder": { "id": "https://github.com/sam-aydlette/samaydlette.com/.github/workflows/deploy-with-opa.yml", - "run_id": "<github actions run id>", "version": "github-actions" }, "source": { @@ -163,7 +162,7 @@ It yields one entry per control in scope (the FedRAMP Rev 5 Moderate baseline, t - an implementation statement naming the contributing KSIs; - the FedRAMP-defined parameter values from the vendored Moderate profile. -The projection is published in the CR26 **Security Decision Record** (`/.well-known/security-decision-record.json`, built by [`scripts/build-sdr.py`](../scripts/build-sdr.py)): `rule_records` summarize each KSI (`SDR-CSX-KSI`) and `rev5_controls` summarize each applicable Rev5 control (`SDR-CSF-CTF`). The same projection feeds the framework coverage figures and the CMMC projection. The SDR carries `ksi_signal_id`, and reconciliation invariant (e) fails the deploy if it names a different inventory than the signal. Until 2026-11-05 this view was published as an OSCAL Rev 5 SSP (`oscal-ssp.json`); CR26 retired the SSP and the deploy deleted it. +The projection is published in the CR26 **Security Decision Record** (`/.well-known/security-decision-record.json`, built by [`scripts/build-sdr.py`](../scripts/build-sdr.py)): `rule_records` summarize each KSI (`SDR-CSX-KSI`) and `rev5_controls` summarize each applicable Rev5 control (`SDR-CSF-CTF`). The same projection feeds the trust center's Rev5 Moderate figures. The SDR carries `ksi_signal_id`, and reconciliation invariant (e) fails the deploy if it names a different inventory than the signal. Until 2026-11-05 this view was published as an OSCAL Rev 5 SSP (`oscal-ssp.json`); CR26 retired the SSP and the deploy deleted it. ```bash # Fetch and inspect the per-control record at any time: diff --git a/docs/policies/README.md b/docs/policies/README.md index 571cff45..6c593456 100644 --- a/docs/policies/README.md +++ b/docs/policies/README.md @@ -16,7 +16,7 @@ These policies reference operational documents elsewhere in `docs/`: - [`incident-response.md`](../incident-response.md) — IR procedures - [`recovery-plan.md`](../recovery-plan.md) — CP procedures -- [`security-review.md`](../security-review.md) — annual review record +- [`security-review.md`](../security-review.md) — how the Annual Security Review is generated (`scripts/hold-security-review.py`), and its history - [`supply-chain.md`](../supply-chain.md) — SR procedures - [`training-log.md`](../training-log.md) — AT records - [`architecture-decisions.md`](../architecture-decisions.md) — system design rationale, threat model @@ -25,4 +25,4 @@ These policies reference operational documents elsewhere in `docs/`: ## Review -The full family-policy set is reviewed annually as part of [`security-review.md`](../security-review.md), and after any Transformative significant change per SCN. +The full family-policy set is machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`) and re-checked, with each file's sha256, in the Annual Security Review ([`security-review.md`](../security-review.md), `scripts/hold-security-review.py`); a Transformative significant change (SCN) revisits it in the same pull request. diff --git a/docs/policies/ac-policy.md b/docs/policies/ac-policy.md index 619cdacf..ef546f3b 100644 --- a/docs/policies/ac-policy.md +++ b/docs/policies/ac-policy.md @@ -8,6 +8,6 @@ Operator access uses GitHub branch protection on `main` plus AWS IAM with fixed- **20x rule integration.** SCG-CSO-RSC and SCG-CSO-AUP are satisfied by the [Secure Configuration Guide](secure-configuration-guide.md). This family is the operator-side complement to KSI-IAM (Identity and Access Management). -Operator behavior (PL-4 Rules of Behavior) is documented in [`docs/rules-of-behavior.md`](../rules-of-behavior.md), which the operator acknowledges annually as part of the security review. +Operator behavior (PL-4 Rules of Behavior) is documented in [`docs/rules-of-behavior.md`](../rules-of-behavior.md), whose acknowledgement is recorded by machine with each Annual Security Review and whenever the document changes (`scripts/hold-security-review.py`; the acknowledging person is simulated, DEC-194). -**Review cadence.** Annually with the [security review](../security-review.md). +**Verification.** Machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`), and re-checked, with its sha256, in each Annual Security Review (`scripts/hold-security-review.py`); a change is a reviewed pull request. diff --git a/docs/policies/at-policy.md b/docs/policies/at-policy.md index 03f3b7e3..781d4a25 100644 --- a/docs/policies/at-policy.md +++ b/docs/policies/at-policy.md @@ -1,7 +1,7 @@ # AT — Awareness and Training -Training is the annual review and update of the operational runbooks ([incident response](../incident-response.md), [recovery plan](../recovery-plan.md), [supply chain](../supply-chain.md), and this set of family policies). Information-spillage scenarios are covered as part of that review (NIST IR-9.2). The training record is [`training-log.md`](../training-log.md). +Training is generated and taken by machine (`scripts/_training.py`). The training packet is built from the system's own data on every build of the Security Decision Record: a lesson for every decision of the last 12 months, every incident and exercise, the applicable FedRAMP rules and KSIs, and a fixed core covering the operational runbooks ([incident response](../incident-response.md), [recovery plan](../recovery-plan.md), [supply chain](../supply-chain.md)) and information spillage (NIST IR-9.2). A simulated trainee, Pat Placeholder (simulated), takes its quiz whenever the packet changes (DEC-194), and the SDR counts the packet's currency and the trainee's completion as two automated methods for KSI-CED-RAT. The areas are listed in [`training-log.md`](../training-log.md). **20x rule integration.** Aligns with KSI-CED (Cybersecurity Education). -**Review cadence.** Annually with the [security review](../security-review.md). +**Verification.** Machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`), and re-checked, with its sha256, in each Annual Security Review (`scripts/hold-security-review.py`); a change is a reviewed pull request. diff --git a/docs/policies/au-policy.md b/docs/policies/au-policy.md index 85be0217..921f204d 100644 --- a/docs/policies/au-policy.md +++ b/docs/policies/au-policy.md @@ -4,6 +4,6 @@ Three log sources comprise the auditable record: CloudWatch Logs (Lambda executi The runtime KSI emitter publishes a daily artifact at `/.well-known/ksi-signal-runtime.json` that constitutes a public, signed audit summary of the system's live state. The build-time VDR report (see RA) is similarly public per deploy. -**20x rule integration.** Aligns with KSI-MLA (Monitoring, Logging, and Auditing). Persistent log review cadence is in [`security-review.md`](../security-review.md). +**20x rule integration.** Aligns with KSI-MLA (Monitoring, Logging, and Auditing). The persistent log review (KSI-MLA-RVL) is automated: `scripts/audit-log-review.py` runs every night ([`architecture-decisions.md`](../architecture-decisions.md#audit-log-review-ksi-mla-rvl)). -**Review cadence.** Quarterly review of CloudTrail; annual structural review. +**Verification.** Machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`), and re-checked, with its sha256, in each Annual Security Review (`scripts/hold-security-review.py`); a change is a reviewed pull request. The audit log itself is reviewed every night by `scripts/audit-log-review.py`. diff --git a/docs/policies/ca-policy.md b/docs/policies/ca-policy.md index 07b3243d..6a064732 100644 --- a/docs/policies/ca-policy.md +++ b/docs/policies/ca-policy.md @@ -6,8 +6,8 @@ There is no formal authorization process or independent assessor in scope for th - The deploy-time OPA gate — every PR re-evaluates the Terraform plan, the website tree, and the IAM policy against in-house Rego. - The build-time VDR aggregator (see RA) — every CI run re-aggregates vulnerability state across SAST/SCA tools and blocks the build if any finding exceeds Class C remediation timeframes. The build is the report. -**20x rule integration.** This family carries Vulnerability Detection and Response (VDR-*) and Collaborative Continuous Monitoring (CCM). VDR is satisfied as described above and in RA. CCM is satisfied by the public-by-default publication of all KSI/SSP/runtime/VDR artifacts at `/.well-known/`, signed via Sigstore, verifiable from anywhere — anyone can run continuous monitoring of this system without privileged access. +**20x rule integration.** This family carries Vulnerability Detection and Response (VDR-*) and Collaborative Continuous Monitoring (CCM). VDR is satisfied as described above and in RA. CCM is satisfied by the public-by-default publication of all KSI, Security Decision Record, runtime and VDR artifacts at `/.well-known/`, signed via Sigstore, verifiable from anywhere — anyone can run continuous monitoring of this system without privileged access. The consolidated continuous-monitoring strategy (mechanisms, cadences, reporting, role mapping, NIST control coverage) is documented in [`docs/continuous-monitoring-plan.md`](../continuous-monitoring-plan.md), the document that backs CA-7 specifically. -**Review cadence.** Continuous (automated); annual structural review. +**Verification.** Machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`), and re-checked, with its sha256, in each Annual Security Review (`scripts/hold-security-review.py`); a change is a reviewed pull request. diff --git a/docs/policies/cm-policy.md b/docs/policies/cm-policy.md index 0ce6d58c..37604a37 100644 --- a/docs/policies/cm-policy.md +++ b/docs/policies/cm-policy.md @@ -1,11 +1,11 @@ # CM — Configuration Management -Configuration management is GitOps. Every change to infrastructure or content reaches `main` through a commit that triggers the OPA gate, the Terraform plan, the apply, the canonical inventory build, the Sigstore signing, and the publish. The default workflow for the sole operator is **direct push to `main`**; pull requests are used only when collaboration or staged review is desired (rare). The commit (or PR description, when a PR is used) is the change request, the review when applicable, the approval, and the audit record. +Configuration management is GitOps. Every change to infrastructure or content reaches `main` through a commit that triggers the OPA gate, the Terraform plan, the apply, the canonical inventory build, the Sigstore signing, and the publish. Changes reach `main` through pull requests; branch protection requires the status checks, `scn-tag` among them, to pass. The PR description is the change request and carries the significant-change evaluation; the merge is the approval. -The **Significant Change Notification (SCN) category** for any change is **Routine Recurring by default; no label is required for routine work**. The operator upgrades the categorization explicitly only when the change meets Adaptive or Transformative criteria per `SCN-CSO-EVA`, by including a line like `SCN-Type: adaptive` or `SCN-Type: transformative` in the commit message (or in the PR description, if a PR is used). A fourth value, `SCN-Type: emergency`, is reserved for emergency-change scenarios per `SCN-CSO-EMG` (see [`docs/incident-response.md`](../incident-response.md) for procedures and retroactive-documentation requirements). The CI workflow validates the tag on every push to `main` and every PR — it fails the build only on a malformed value (a recognized `SCN-Type:` line with a value that isn't one of the four recognized values). Missing tags are treated as Routine Recurring per the default. Audit records of these evaluations are the git history (`SCN-CSO-MAR`). Adaptive and Transformative changes — which produce a security impact analysis — additionally get a durable, structured record in [`docs/scn/`](../scn/): a per-change SCN record carrying the `SCN-CSO-INF` fields plus a copy of the SIA, and a row in the machine-and-human-readable register [`docs/scn/scn-register.csv`](../scn/scn-register.csv) (`SCN-CSO-HRM`), retained for at least 12 months (`SCN-CSO-HIS`). +The **Significant Change Notification (SCN) evaluation** is explicit on every change (`SCN-CSO-EVA`). Each pull request description (or direct-push commit message) carries an `SCN-Type:` line (`not-significant`, `routine-recurring`, `adaptive`, `transformative`, `emergency` or `class-change`), a one-line `SCN-Rationale:`, and for adaptive, transformative and emergency changes the `SCN-Record:` that will document it. The required `scn-tag` check fails a change without them; there is no default. `class-change` always fails: a change of certification class is a new certification and needs a new assessment. A transformative change cannot merge until its initial plan has been published for 30 business days and its final plan for 10. The format and one example per type are in [`docs/scn/evaluation-examples.md`](../scn/evaluation-examples.md); emergency changes follow [`docs/incident-response.md`](../incident-response.md). Each deploy appends every merged evaluation to the signed, append-only evaluation log at `/.well-known/scn-evaluations.json` (`SCN-CSO-MAR`). Adaptive and transformative changes get a row in [`docs/scn/scn-register.csv`](../scn/scn-register.csv) and a record with the security impact analysis; each deploy publishes them in FedRAMP's SCN schema with an Atom feed, which is how notice is given (`SCN-CSO-NOM`, `SCN-CSO-HIS`, `SCN-CSO-HRM`). A scheduled check fails on any record or notice past its deadline. See [`docs/scn/README.md`](../scn/README.md). The canonical inventory at `/.well-known/ksi-signal.json` is the authoritative system inventory (CM-8 family). It is generated automatically from Terraform state, Lambda package locks, and content hashes — see [`docs/ksi-signal.md`](../ksi-signal.md). Each component carries a normalized identifier (PURL/ARN/SHA-256/HBOM ref), a security category (per FIPS 199), and an information-flow tag (per `MAS-CSO-FLO`). **20x rule integration.** Significant Change Notifications (full SCN-* family — `SCN-CSO-MAR`/`INF`/`HIS`/`HRM`/`ARI`/`NOM`/`EMG`/`EVA` plus the Adaptive/Routine-Recurring/Transformative tier rules. Transformative changes carry five notification windows: 30 business days before starting (initial plans, `SCN-TRF-NIP`), 10 before starting (final plans, `SCN-TRF-NFP`), 5 after finishing (`SCN-TRF-NAF`), 5 after the verification/validation completes (`SCN-TRF-NAV`), and updated service documentation within 30 (`SCN-TRF-UPD`); a recognized-assessor human-validation review (`SCN-TRF-TPR`) is a SHOULD. Minimum Assessment Scope (`MAS-CSO-IIR`/`FLO`/`TPR`; third-party AWS resources documented at the inheritance level per `MAS-CSO-TPR`). `MAS-CSO-MDI` (federal-customer-data metadata) is **N/A** — its `MAS-CSO-IIR` trigger does not fire with no federal customer data held — and `MAS-CSO-SUP` (supplemental, non-offering materials) carries nothing for this system. KSI-CMT (Change Management). -**Review cadence.** Continuous; effectiveness review monthly via the no-out-of-band-commits check on `main`. +**Verification.** Machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`), and re-checked, with its sha256, in each Annual Security Review (`scripts/hold-security-review.py`); a change is a reviewed pull request. Its effectiveness is checked every night by the audit-log review (`scripts/audit-log-review.py`), which flags any commit on `main` without a merged pull request. diff --git a/docs/policies/cp-policy.md b/docs/policies/cp-policy.md index 18bc44b8..076f872c 100644 --- a/docs/policies/cp-policy.md +++ b/docs/policies/cp-policy.md @@ -6,4 +6,4 @@ CP enhancements covering alternate processing site, alternate storage site, and **20x rule integration.** Aligns with KSI-CPL (Recovery Planning). Plan exercise cadence is in [`security-review.md`](../security-review.md). -**Review cadence.** Annually, plus after any Transformative change per SCN. +**Verification.** Machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`), and re-checked, with its sha256, in each Annual Security Review (`scripts/hold-security-review.py`); a change is a reviewed pull request; a Transformative change (SCN) revisits it in the same pull request. diff --git a/docs/policies/ia-policy.md b/docs/policies/ia-policy.md index 636414f3..fb4cf494 100644 --- a/docs/policies/ia-policy.md +++ b/docs/policies/ia-policy.md @@ -2,8 +2,8 @@ Three authentication chains exist: -1. **Operator → GitHub:** username + password + MFA via Duo. All pushes to `main` require this chain plus passing branch protection checks. -2. **GitHub Actions → AWS:** long-lived AWS access keys stored as GitHub Actions encrypted secrets. Migration to GitHub OIDC role assumption is tracked as POAM-001 (now DEC-001) in [`data/decisions.json`](../../data/decisions.json). Until that migration completes, the deployer principal is the largest standing-privilege surface in the system. As an active compensating control while POAM-001 remains open, the AWS access key is rotated every 90 days per the procedure in the [Secure Configuration Guide](secure-configuration-guide.md); rotation events are logged in [`security-review.md`](../security-review.md). +1. **Operator → GitHub:** username + password + two-factor authentication (virtual TOTP from an authenticator app), which GitHub enforces on the owner account (DEC-151). All pushes to `main` require this chain plus passing branch protection checks. +2. **GitHub Actions → AWS:** GitHub OIDC role assumption. Each workflow assumes its own role (deploy, plan, nightly, package maintenance, incident reports) with short-lived credentials; no AWS access key exists for CI. The deployer access key this replaced was deleted (DEC-001, remediated, in [`data/decisions.json`](../../data/decisions.json)). 3. **Lambda → AWS:** AWS IAM execution role with no human-assumable trust policy. The role's only invoker is the EventBridge scheduled rule. Sigstore keyless signing uses GitHub Actions OIDC for ephemeral identity proof; no signing keys are stored anywhere. Fulcio issues a short-lived X.509 certificate per workflow run, the signature is recorded in Rekor, and verification is anchored in the public transparency log. @@ -12,4 +12,4 @@ Several IA enhancements (network access for non-privileged accounts in AWS infra **20x rule integration.** Operator-side complement to KSI-IAM. Cryptographic primitives used in authentication are governed under SC and the Using Cryptographic Modules (UCM) rule. -**Review cadence.** Annually. +**Verification.** Machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`), and re-checked, with its sha256, in each Annual Security Review (`scripts/hold-security-review.py`); a change is a reviewed pull request. diff --git a/docs/policies/ir-policy.md b/docs/policies/ir-policy.md index 81be6cb0..7d61b682 100644 --- a/docs/policies/ir-policy.md +++ b/docs/policies/ir-policy.md @@ -1,15 +1,24 @@ # IR — Incident Response -Incident response procedures are documented in [`incident-response.md`](../incident-response.md), which satisfies KSI-INR-RIR through KSI-INR-AAR and the IR-9 family (information spillage). The runbook covers detection sources, triage, containment, eradication, recovery, and after-action reporting. The IR lead is the operator; escalation is single-tier. +Incident response procedures are documented in [`incident-response.md`](../incident-response.md), which satisfies KSI-INR-RIR through KSI-INR-AAR and the IR-9 family (information spillage). The runbook covers detection sources, triage (including the FedRAMP reportability evaluation), containment, eradication, recovery, FedRAMP incident reporting, and after-action reporting. The IR lead is the operator; escalation is single-tier. External communication paths: - **Public reporter:** [`/.well-known/security.txt`](../../website/.well-known/security.txt) is the published vulnerability-reporting mailbox. -- **Incident Communications Procedures (ICP, 20x):** the ICP rules apply at the procedure-documented level even though the system has no actual FedRAMP-customer reporting obligation. The runbook describes what would be communicated and to whom for a real FedRAMP-certified service. -- **FedRAMP Security Inbox (FSI, 20x):** the system is not FedRAMP-certified; no actual FSI obligation applies. Notification path is documented in the runbook for reference. +- **FedRAMP incident reports (IEC):** every incident is recorded in the incident register, [`data/incidents.json`](../../data/incidents.json), with its reportability evaluation. Initial, Ongoing and Final Incident Reports for a FedRAMP Reportable Incident are generated from it, validated against FedRAMP's incident report schema, signed, and published under `/.well-known/` (the incident log is `/.well-known/incident-reports.json`) by an unattended workflow on every change to the register. +- **Delivery is simulated.** Nothing is sent to FedRAMP or to any agency: the system has no FedRAMP certification and no agency customers. Each report is published and "delivered" to simulated FedRAMP and agency recipients, recorded in `/.well-known/incident-deliveries.json`; a delivery that fails stops publication. +- **FedRAMP Security Inbox (FSI, 20x):** simulated for this proof of concept. No mail is received or sent; the inbox logic runs on every deploy over synthetic messages and its result is published as `/.well-known/fedramp-inbox-simulation.json`. The published contact directs FedRAMP to the operator on LinkedIn. Procedure: `docs/runbooks/fedramp-security-inbox.md`. -**20x rule integration.** KSI-INR (Incident Response), ICP (Incident Communications Procedures), FSI (FedRAMP Security Inbox). +**20x rule integration.** KSI-INR (Incident Response), IEC (Incident Evaluation and Communication), FSI (FedRAMP Security Inbox). -**Review cadence.** Annually with the [security review](../security-review.md); after every actual incident (currently zero). VDR thresholds (Class C) treat internet-reachable likely-exploitable vulnerabilities above PAIN N3 (i.e. N4 or N5) as FedRAMP Reportable Incidents per `VER-TFR-IRI`, until they are partially mitigated to N3 or below; non-internet-reachable likely-exploitable vulnerabilities at PAIN N5 are reportable until N4 or below per `VER-TFR-NRI`. +**Reportability (IEC-CSO-EFR).** Every incident is evaluated, promptly and before containment, for whether it affects or is likely to affect the confidentiality or integrity of **federal customer data**; such an incident is a FedRAMP Reportable Incident. The determination, its reason and the federal customer data considered are recorded in the register and published in the incident log. This system holds no federal customer data, so in practice the evaluation is "not reportable"; the machinery runs either way, and it was exercised on 2026-11-05 with one simulated reportable incident and one simulated non-reportable one, both marked as exercises. -**Reportability trigger (IEC).** A FedRAMP Reportable Incident under `IEC-CSO-EFR` is triggered by an effect on the confidentiality or integrity of **federal customer data**. This system holds none, so no finding here is FedRAMP-reportable in practice and the `IEC-CSO-IIR` reporting clocks (Class C: 1 hour for PAIN 3/4/5) never start. The evaluation step still runs — the VDR aggregator assigns the PAIN rating to every finding — so the machinery is in place the moment federal data ever enters scope. +**Rating (IEC-CSO-DPR, IEC-CSO-EFI).** A reportable incident is rated at the default the rules set (N5) until the operator records an Incident Rating estimate: a likely minimal, narrow, disruptive or debilitating customer effect on one or more than one agency, with a reason. The register refuses an estimate whose rating is not the one the rules give for that effect. + +**Report clocks.** The Initial, Ongoing and Final report deadlines are FedRAMP's Class C timeframes, read from the pinned rules and never restated. An overdue report fails the incident reports workflow (raising a GitHub issue) and pages the operator through the evidence SLA watchdog. + +**Vulnerabilities as incidents (VER-TFR-IRI, VER-TFR-NRI).** The operator adopts both rules. An internet-reachable likely exploitable vulnerability above PAIN N3 (i.e. N4 or N5) is a FedRAMP Reportable Incident until it is partially mitigated to N3 or below (`VER-TFR-IRI`), and a non-internet-reachable likely exploitable vulnerability at PAIN N5 is one until it is N4 or below (`VER-TFR-NRI`, a MAY the operator has chosen to use). The VDR triage policy names each such finding; the incident log shows it, and until an incident in the register names it, its Initial report is due and the alarms above apply. + +**Verification.** Machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`), and re-checked, with its sha256, in each Annual Security Review (`scripts/hold-security-review.py`); a change is a reviewed pull request; an actual incident's after-action record revisits it (currently zero; the recorded incidents are exercises). + +_AI-drafted (2026-11-05) to describe what the incident register, report builder and workflow now do; for the operator's review._ diff --git a/docs/policies/pl-policy.md b/docs/policies/pl-policy.md index 5e6d8b64..4306beda 100644 --- a/docs/policies/pl-policy.md +++ b/docs/policies/pl-policy.md @@ -2,10 +2,10 @@ Under CR26 the system security plan is replaced by the Security Decision Record at `/.well-known/security-decision-record.json` and the Certification Package Overview at `/.well-known/certification-package-overview.json`. The SDR records how each KSI is met and, in `rev5_controls`, each applicable Rev5 control's parameters, status, mechanisms, verification and validation (`SDR-CSF-CTF`). Both are generated deterministically from the canonical inventory and the FedRAMP KSI catalog through the control projection (`scripts/_controls.py`) and signed via Sigstore keyless on every deploy; the SDR also carries an in-toto provenance attestation. The OSCAL SSP that used to fill this role was retired on 2026-11-05. -The KSI signal at [`/.well-known/ksi-signal.json`](../../website/.well-known/ksi-signal.json) is the FedRAMP 20x companion artifact, also signed and published per deploy. +The KSI signal at [`/.well-known/ksi-signal.json`](https://samaydlette.com/.well-known/ksi-signal.json) is the FedRAMP 20x companion artifact, also signed and published per deploy. The architectural decision record [`architecture-decisions.md`](../architecture-decisions.md) captures the rationale for system-level decisions (PL-2 approach, threat model under SA-11.2, KSI-aligned justifications). The full set of family policies in this folder satisfies the per-family `-1` controls. **20x rule integration.** KSI-PIY (Policy and Inventory). The 20x meta-process rules — FedRAMP Certification (`CRT-*`), Certification Data Sharing (`CDS-*`), and Marketplace Listing (`MKT-*`) — are documented in this PoC at the procedure level. The system is not actually FedRAMP-certified, so the obligations these rules impose (data sharing to FedRAMP, marketplace metadata accuracy) are demonstrated rather than executed. -**Review cadence.** Annually with the [security review](../security-review.md), plus after Transformative changes per SCN. +**Verification.** Machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`), and re-checked, with its sha256, in each Annual Security Review (`scripts/hold-security-review.py`); a change is a reviewed pull request; a Transformative change (SCN) revisits it in the same pull request. diff --git a/docs/policies/ps-policy.md b/docs/policies/ps-policy.md index 7237c40a..5fa051f3 100644 --- a/docs/policies/ps-policy.md +++ b/docs/policies/ps-policy.md @@ -4,4 +4,4 @@ Personnel screening, position-risk designation, separation-of-duty, and terminat **20x rule integration.** No 20x rule maps to PS specifically. -**Review cadence.** Annually with the [security review](../security-review.md). +**Verification.** Machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`), and re-checked, with its sha256, in each Annual Security Review (`scripts/hold-security-review.py`); a change is a reviewed pull request. diff --git a/docs/policies/pt-policy.md b/docs/policies/pt-policy.md index 817b969b..cbc35876 100644 --- a/docs/policies/pt-policy.md +++ b/docs/policies/pt-policy.md @@ -4,6 +4,6 @@ The system processes no personally identifiable information. There are no end us All PT controls in the Moderate baseline are therefore not-applicable as scoped, with this policy doc itself satisfying PT-1. The formal Privacy Threshold Analysis with the negative determination is recorded in [`docs/privacy-threshold-analysis.md`](../privacy-threshold-analysis.md). If the system's data-processing posture ever changes (forms, accounts, analytics that collect PII), the PT family is reactivated, the PTA is re-determined, a full PIA is produced, and this doc is rewritten before the change is deployed. -**20x rule integration.** None directly. Operator awareness of PII obligations is part of the annual training reading-list under AT. +**20x rule integration.** None directly. PII obligations are part of the generated training packet's fixed core under AT (`scripts/_training.py`). -**Review cadence.** Annually; review whether the system's data processing posture has changed. +**Verification.** Machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`), and re-checked, with its sha256, in each Annual Security Review (`scripts/hold-security-review.py`); a change is a reviewed pull request; a change to the system's data processing revisits it, and the privacy threshold analysis, in the same pull request. diff --git a/docs/policies/ra-policy.md b/docs/policies/ra-policy.md index 50dcc3e6..c73982eb 100644 --- a/docs/policies/ra-policy.md +++ b/docs/policies/ra-policy.md @@ -24,4 +24,4 @@ KEVs (CISA Known Exploited Vulnerabilities) are remediated according to the BOD **20x rule integration.** Vulnerability Detection and Response (full VDR-* family at Class C cadence). KSI-PIY-RVD (Reviewing Vulnerability Disclosures). -**Review cadence.** Continuous (per-PR + per-deploy); structural review annually. +**Verification.** Machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`), and re-checked, with its sha256, in each Annual Security Review (`scripts/hold-security-review.py`); a change is a reviewed pull request. Risk is re-evaluated on every pull request and every deploy. diff --git a/docs/policies/resource-tagging-standard.md b/docs/policies/resource-tagging-standard.md index 2f2a11b4..c1ff7cc8 100644 --- a/docs/policies/resource-tagging-standard.md +++ b/docs/policies/resource-tagging-standard.md @@ -91,8 +91,11 @@ true`, `agency_scope: single`) so it scores loudly and surfaces itself for classification rather than hiding. Silence never makes a resource look safer than it is. -## Review cadence +## Verification -Annually with the security review, and after any Transformative change that adds -a resource type or changes a resource's reachability, data sensitivity, or -criticality. +Machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`), +and re-checked in each Annual Security Review (`scripts/hold-security-review.py`), +which fails when a component type added since the previous review is not named in +the threat model. A Transformative change that adds a resource type or changes a +resource's reachability, data sensitivity, or criticality revisits this standard +in the same pull request. diff --git a/docs/policies/sa-policy.md b/docs/policies/sa-policy.md index 020f9efe..fa29f8e3 100644 --- a/docs/policies/sa-policy.md +++ b/docs/policies/sa-policy.md @@ -6,4 +6,4 @@ The system has no acquisition relationships beyond AWS services and GitHub Actio **20x rule integration.** KSI-PIY-RSD (Reviewing Security in the SDLC) is satisfied by the OPA gate + threat model + signing chain combination. SCN evaluation (CM family) gates every code change before it reaches production. -**Review cadence.** Annually with the [security review](../security-review.md); threat model revisited after Transformative changes. +**Verification.** Machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`), and re-checked, with its sha256, in each Annual Security Review (`scripts/hold-security-review.py`); a change is a reviewed pull request; a Transformative change (SCN) revisits the threat model in the same pull request. diff --git a/docs/policies/sc-policy.md b/docs/policies/sc-policy.md index 261b9b74..f63b3ee9 100644 --- a/docs/policies/sc-policy.md +++ b/docs/policies/sc-policy.md @@ -14,4 +14,4 @@ Several SC controls are inherited from AWS East/West Moderate FedRAMP authorizat **20x rule integration.** Using Cryptographic Modules (`UCM-*`) — covered by AWS KMS/ACM and Sigstore. Communication integrity (KSI-SVC-VCM). -**Review cadence.** Annually with the [security review](../security-review.md); after any Transformative change to the TLS or signing posture. +**Verification.** Machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`), and re-checked, with its sha256, in each Annual Security Review (`scripts/hold-security-review.py`); a change is a reviewed pull request; a Transformative change (SCN) to the TLS or signing posture revisits it in the same pull request. diff --git a/docs/policies/secure-configuration-guide.md b/docs/policies/secure-configuration-guide.md index da9d97d8..281da443 100644 --- a/docs/policies/secure-configuration-guide.md +++ b/docs/policies/secure-configuration-guide.md @@ -1,94 +1,21 @@ -# Secure Configuration Guide (FedRAMP 20x SCG) +# Secure Configuration Guide -This guide describes the secure access, configuration, operation, and decommissioning of the **top-level administrative accounts** for the system, per `SCG-CSO-RSC`. It is published publicly (`SCG-CSO-PUB`) and lives in the repository so it is versioned alongside the code (`SCG-ENH-VRH`). +The Secure Configuration Guide for samaydlette.com (`SCG-CSO-RSC`) is published on the site in two forms, generated on every deploy from one source: -For this system, "top-level administrative accounts" map to two real-world accounts: the AWS root account, and the GitHub repository owner. +- **Human-readable:** https://samaydlette.com/.well-known/secure-configuration-guide.md +- **Machine-readable:** https://samaydlette.com/.well-known/secure-configuration-guide.json (signed; `secure-configuration-guide.bundle`) +- **Live comparison and export:** https://samaydlette.com/.well-known/security-settings.json (and `.md`): every setting read from the live accounts during the deploy and compared with the guide's recommended defaults. -## 1. AWS root account +The source is [`data/secure-configuration.json`](../../data/secure-configuration.json), with the per-service cryptographic module list in [`data/crypto-modules.json`](../../data/crypto-modules.json). `scripts/build-scg.py` publishes the guide and `scripts/check-secure-config.py` runs the comparison; the deploy fails on a changed default without a new version and changelog entry, on a deviation that no in-force decision covers, and on a setting it cannot read. -**Naming.** The root account is the operator's email address registered against the AWS account holding all production resources. +## What the guide covers -**Secure access.** MFA enforced via Duo. Access is interactive only — there are no API keys generated for root. Sessions are minimal: root is used only for billing, service quotas, and IAM-policy-of-last-resort actions. Day-to-day deploys use the IAM deployer principal, not root. +- **Top-level administrative accounts:** the AWS root user and the GitHub repository owner: how each is named, and how to securely access, configure, operate and decommission it; the settings only those accounts can operate and what each means for security. +- **Privileged accounts:** the operator IAM user, the five CI roles GitHub Actions assumes through OIDC (deploy, plan, nightly, package maintenance, incident reports), and administration of the Silk Reeling user pool. +- **For every setting:** the recommended secure default, its security implication, and the API or CLI call that reads and changes it. +- **Versioning:** a version number and a release history of the recommended defaults; each release records a digest of the defaults it fixes. +- **Cryptographic modules:** the module each service uses to protect data, with its CMVP certificate where AWS publishes one, and the agency-tenant defaults. -**Secure configuration.** AWS-default secure settings are kept. CloudTrail is account-wide and management-event logging is enabled. The S3 bucket public-access block is on at the account level. +## Accepted deviation -**Secure operation.** Sessions are short. Any root-level action is recorded in CloudTrail. Routine operations do not use root. - -**Decommissioning.** If the operator transfers stewardship of the site, the AWS root account is closed and the domain is transferred per AWS's account-closure procedures. All API keys for the deployer principal are rotated and deleted before account closure. - -## 2. GitHub repository owner - -**Naming.** The operator's GitHub account, which is the owner of the `samaydlette.com` repository. - -**Secure access.** MFA enforced via Duo. All pushes to `main` require an authenticated session; `main` has branch protection requiring PR review and OPA-gate passage. - -**Secure configuration.** Repository settings: branch protection on `main`; required status checks (OPA gate, build); secret scanning with push protection; Dependabot enabled. GitHub Actions settings: workflow permissions are read-only by default; mutation is granted per-job. Encrypted secrets used for AWS credentials are scoped per-environment. - -**Secure operation.** No long-lived PATs are issued; the workflow's ephemeral `GITHUB_TOKEN` and the OIDC token for cosign are the only GitHub-issued tokens used. - -**AWS access key rotation (90-day cadence).** While the OIDC migration in [POAM-001](../../data/decisions.json) remains deferred, the AWS access key used by the deployer IAM user is rotated every 90 days. The rotation procedure: - -1. **Calendar trigger.** A recurring 90-day calendar event on the operator's calendar is the rotation trigger. -2. **Generate the new key.** In the AWS console (IAM → Users → `<deployer-user>` → Security credentials → Create access key) or via CLI: `aws iam create-access-key --user-name <deployer-user>`. -3. **Update the GitHub Actions secrets.** Repository Settings → Secrets and variables → Actions → update `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` with the new values. -4. **Verify a deploy.** Push a small no-op PR (or open and close one) to trigger the workflow. Confirm the compliance-check and deploy jobs both pass with the new key. -5. **Delete the old key.** In AWS console (IAM → Users → `<deployer-user>` → Security credentials → Delete previous access key) or via CLI: `aws iam delete-access-key --user-name <deployer-user> --access-key-id <old-key-id>`. -6. **Log the rotation.** Append a one-line entry to [`docs/security-review.md`](../security-review.md) under the rotation log: date, action, outcome. - -**Emergency rotation.** If a key is suspected compromised at any time, rotation happens immediately, not on the 90-day cadence. Same procedure as above, plus the IR runbook ([`docs/incident-response.md`](../incident-response.md)) is followed. - -**Decommissioning.** If the operator transfers stewardship, repository ownership is transferred per GitHub's transfer flow. Encrypted secrets are rotated before transfer; AWS access keys held in those secrets are deleted on the AWS side immediately after. - -## 3. Silk Reeling Mirror app (operator-configured security settings) - -Active in production (`create_silk_reeling = true` in the main deploy pipeline; live -since 2026-06-03). The app adds one operator-configured security setting and a fixed -secure-by-default resource baseline. Introduced under -[SCN-2026-001](../scn/SCN-2026-001-silk-reeling.md). - -**Operator-set Basic Auth credential (the one configurable security setting).** Access -to the app is gated by a single HTTP Basic Auth credential the operator sets, stored in -Secrets Manager and CMK-encrypted. It is the access-control setting for the app -(POAM-021; single-factor, shared, no MFA, no lockout — risk-accepted operational item). - -- **Set / rotate securely.** The secret *value* is injected out of band — never via Terraform (Terraform manages only the secret container, so plaintext never enters state). Set or rotate it with `aws secretsmanager put-secret-value` from the CI-held GitHub secret; use a long, random password. Rotate on the same 90-day cadence as the deployer key (and immediately on suspected compromise), logging the rotation in [`docs/security-review.md`](../security-review.md). Automatic rotation is not configured (POAM-019). -- **Upgrade path (available on request).** SAML/OIDC federation to a customer IdP — or native WebAuthn/FIDO2 (phishing-resistant MFA) — is offered on request and would move authentication to a `customer-configured` control; not pre-built. The current single-factor credential is an **operator-accepted residual risk** for the sole-customer demo (POAM-021); any customer onboarded must accept this risk or adopt federation. - -**Fixed secure-by-default baseline (not operator-tunable, recorded here for the SCG inventory).** - -- **KMS CMK** with key rotation enabled; an explicit least-privilege key policy (account root-enable + Secrets-Manager-via-service condition only). -- **Secrets Manager:** none. The basic-auth credential was removed in Task 3 and the Anthropic API key in SCN-2026-006, so the app role holds no `GetSecretValue`; it keeps `kms:Decrypt` on the one CMK for its encrypted environment. -- **Lambda** runs with that least-privilege role; non-sensitive config only in environment variables; CORS locked to the site origin; constant-time credential compare. -- **API Gateway HTTP API** has no authorizer by design (app-layer Basic Auth is the gate, POAM-022); TLS-only; access logging deferred (POAM-024). -- **Egress:** no third-party service. The app Lambda's only outbound call is to the Cognito user pool's public JWKS endpoint (TLS) to validate tokens; feedback text is written from the scores in the Lambda. It runs outside a VPC, so this is enforced by code and configuration, not a network control. -- **LLM-written feedback (customer-configurable, off).** The app can have an LLM write its feedback (`SRM_ENABLE_LLM_FEEDBACK=1` plus a provider key). It is disabled in this deployment. Enabling it adds an external interconnection and a secret, so it is a significant change that needs an SCN and SA-9/CA-3 treatment first (see SCN-2026-006). -- **Logs** go to an explicit CloudWatch log group with managed retention. - -## What this guide does NOT cover - -Apart from the operator-set app credential in section 3, this system has no -customer-configurable surface. There are no agency-customer accounts, no per-tenant -settings, no provisioning APIs. The "customer" experience is the public read of the -static site plus the single-credential gated app — there is otherwise nothing to -configure. The standard SCG content about agency-customer security settings -(`SCG-CSO-RSC` items 2 and 3 — settings operated by top-level administrative accounts on -behalf of customers, and settings operated by privileged accounts) is not-applicable as -scoped. - -## Enhanced capabilities (`SCG-ENH-*`) - -- **Comparison capability (`SCG-ENH-CMP`):** the runtime KSI emitter is the comparison capability — it reads the live cloud configuration and compares against the deploy-time signal. The drift detection is the SCG comparison. -- **Export capability (`SCG-ENH-EXP`):** all configuration is in Terraform code, fully exportable. -- **Machine-readable guidance (`SCG-ENH-MRG`):** this guide is in markdown; the configuration the guide describes is in `infrastructure/main.tf` (machine-readable Terraform). -- **API capability (`SCG-ENH-API`):** AWS APIs and GitHub APIs are the upstream APIs that govern these accounts; both are fully API-driven. -- **Versioning (`SCG-ENH-VRH`):** maintained in git with full history. - -## Secure defaults (`SCG-CSO-SDF`) - -All settings ship in their recommended secure state when a resource is first provisioned, because there is no manual provisioning step: every account, key, bucket, and policy is created from version-controlled Terraform with the hardened configuration baked in (S3 public-access block, SSE encryption, TLS 1.2+, mandatory MFA on the Cognito pool, least-privilege IAM, the FSBP account password policy). There is no "default-then-harden" window — the first applied state is the secure state, which is what `SCG-CSO-SDF` (a SHOULD) asks for. - -## Public availability - -Published at this path within the repository and rendered as part of the public site (`SCG-CSO-PUB`). Linked from [`docs/policies/README.md`](README.md) and from the SDR's per-control records (`rev5_controls`) for the AC and SC families. - -> **Effective dates.** The Secure Configuration Guide rules (`SCG-*`) and the Addressing-FedRAMP-Communication rules (`AFC-*`) carry the earliest CR26 deadlines: their grace period ended **2026-07-01**. The SCG obligations above are met; AFC is N/A for this unsponsored system (see [`docs/cr26-applicability.md`](../cr26-applicability.md)). +The recommended default for the AWS root user and the operator IAM user is phishing-resistant MFA (a FIDO2 security key or passkey). Both use virtual authenticator-app (TOTP) MFA; that deviation is an accepted finding, [DEC-150](../../data/decisions.json), extending DEC-025, and the published comparison shows it against that record on every deploy. diff --git a/docs/policies/si-policy.md b/docs/policies/si-policy.md index 5cee99c1..50c85ee8 100644 --- a/docs/policies/si-policy.md +++ b/docs/policies/si-policy.md @@ -10,4 +10,4 @@ Information input validation, error handling, and memory protections (SI-10/11/1 **20x rule integration.** Vulnerability Detection and Response (VDR) — see RA. KSI-MLA monitoring boundary. -**Review cadence.** Continuous (automated); annual structural review. +**Verification.** Machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`), and re-checked, with its sha256, in each Annual Security Review (`scripts/hold-security-review.py`); a change is a reviewed pull request. diff --git a/docs/policies/sr-policy.md b/docs/policies/sr-policy.md index e46c601b..c159b7d6 100644 --- a/docs/policies/sr-policy.md +++ b/docs/policies/sr-policy.md @@ -10,4 +10,4 @@ Significant changes to any supply-chain input trigger SCN evaluation per the cri **20x rule integration.** Significant Change Notifications applied to supply-chain changes (`SCN-* family`). KSI-SCR (Supply Chain Risk). -**Review cadence.** Continuous via Dependabot; annual structural review. +**Verification.** Machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`), and re-checked, with its sha256, in each Annual Security Review (`scripts/hold-security-review.py`); a change is a reviewed pull request. Dependencies are scanned continuously (Dependabot, and Grype on every deploy and night). diff --git a/docs/portfolio/service-model.json b/docs/portfolio/service-model.json deleted file mode 100644 index 4aeb5726..00000000 --- a/docs/portfolio/service-model.json +++ /dev/null @@ -1,141 +0,0 @@ -{ - "version": 1, - "about": "The operator-owned service model: CSP -> CSO -> feature -> service -> inventory component -> owner. One authorization boundary contains both offerings. A service places components either by naming a boundary group in docs/boundary/boundary-classification.json (which already places every AWS and external component) or by selectors for the inventory types the boundary map leaves out (software packages and HTML pages). A service consumed by more than one CSO is a shared service: it is published once, as the shared-services product, and each CSO references it rather than copying it. An empty features list means the service supports the whole offering rather than one feature. Owners are domains from docs/governance/domains.json.", - "csp": { - "id": "urn:samaydlette:csp", - "name": "samaydlette.com operator" - }, - "shared_services": { - "id": "urn:samaydlette:shared-services", - "name": "Shared services" - }, - "csos": [ - { - "key": "website", - "id": "urn:samaydlette:cso:website", - "name": "samaydlette.com website", - "owner_domain": "website" - }, - { - "key": "silk-reeling", - "id": "urn:samaydlette:cso:silk-reeling", - "name": "Silk Reeling", - "owner_domain": "silk-reeling" - } - ], - "features": [ - {"key": "public-site", "cso": "website", "name": "Public site: articles, research and pages"}, - {"key": "trust-center", "cso": "website", "name": "Trust Center and published evidence"}, - {"key": "movement-feedback", "cso": "silk-reeling", "name": "Movement analysis and feedback"}, - {"key": "sign-in", "cso": "silk-reeling", "name": "Sign-in with MFA"} - ], - "sources": [ - {"key": "compliance-lambda-npm", "description": "infrastructure/lambda/package-lock.json", "repo_path": "infrastructure/lambda/package-lock.json"}, - {"key": "a11y-npm", "description": "tools/a11y/package-lock.json", "repo_path": "tools/a11y/package-lock.json"}, - {"key": "silk-reeling-frontend", "description": "silk-reeling-mirror frontend, scanned by the deploy as sbom-js.json"}, - {"key": "silk-reeling-backend", "description": "silk-reeling-mirror Lambda package, scanned by the deploy as sbom-python.json"} - ], - "services": [ - { - "key": "edge-delivery", - "name": "Content delivery, DNS and TLS", - "group": "website", - "owner_domain": "edge-delivery", - "consumed_by": ["website", "silk-reeling"], - "features": ["public-site", "trust-center", "movement-feedback", "sign-in"] - }, - { - "key": "website-content", - "name": "Website pages", - "selectors": [{"type": "html_artifact", "id_glob": "html::*"}], - "owner_domain": "website", - "consumed_by": ["website"], - "features": ["public-site", "trust-center"] - }, - { - "key": "accessibility-gate", - "name": "Accessibility gate (build time)", - "selectors": [{"type": "npm_package", "source": "a11y-npm"}], - "owner_domain": "platform", - "consumed_by": ["website"], - "features": [] - }, - { - "key": "compliance", - "name": "Runtime KSI emitter", - "group": "compliance", - "selectors": [{"type": "npm_package", "source": "compliance-lambda-npm"}], - "owner_domain": "observability", - "consumed_by": ["website", "silk-reeling"], - "features": [] - }, - { - "key": "watchdog", - "name": "Evidence-freshness watchdog and alerting", - "group": "watchdog", - "owner_domain": "observability", - "consumed_by": ["website", "silk-reeling"], - "features": [] - }, - { - "key": "audit", - "name": "Audit trail and shared keys", - "group": "audit", - "owner_domain": "observability", - "consumed_by": ["website", "silk-reeling"], - "features": [] - }, - { - "key": "trust-root", - "name": "CI/CD trust root", - "group": "trust-root", - "owner_domain": "platform", - "consumed_by": ["website", "silk-reeling"], - "features": [] - }, - { - "key": "source-and-ci", - "name": "Source control, CI and workload identity", - "group": "github", - "owner_domain": "platform", - "consumed_by": ["website", "silk-reeling"], - "features": [] - }, - { - "key": "signing", - "name": "Artifact signing and transparency log", - "group": "sigstore", - "owner_domain": "platform", - "consumed_by": ["website", "silk-reeling"], - "features": [] - }, - { - "key": "operator-mfa", - "name": "Operator MFA", - "group": "operator-mfa", - "owner_domain": "identity", - "consumed_by": ["website", "silk-reeling"], - "features": [] - }, - { - "key": "vulnerability-intel", - "name": "Vulnerability metadata sources", - "group": "vuln-feeds", - "owner_domain": "vulnerability", - "consumed_by": ["website", "silk-reeling"], - "features": [] - }, - { - "key": "silk-reeling-app", - "name": "Silk Reeling API, sign-in and app", - "group": "app", - "selectors": [ - {"type": "npm_package", "source": "silk-reeling-frontend"}, - {"type": "pypi_package", "source": "silk-reeling-backend"} - ], - "owner_domain": "silk-reeling", - "consumed_by": ["silk-reeling"], - "features": ["movement-feedback", "sign-in"] - } - ] -} diff --git a/docs/privacy-threshold-analysis.md b/docs/privacy-threshold-analysis.md index bfe226c9..394d3dfb 100644 --- a/docs/privacy-threshold-analysis.md +++ b/docs/privacy-threshold-analysis.md @@ -14,11 +14,11 @@ The following surfaces of the system were examined for PII handling: - **Public site content** (`website/**/*.html`): static personal-portfolio content, blog posts, research papers. No PII collected from readers. - **Forms / interactive endpoints**: the base site has no forms, no comment systems, no contact submission forms, and no user accounts. The one interactive endpoint is the gated **Silk Reeling Mirror** app (see its dedicated bullet below), added under [SCN-2026-001](scn/SCN-2026-001-silk-reeling.md). -- **Silk Reeling Mirror app** (`infrastructure/silk-reeling.tf`, active in production — `create_silk_reeling = true` in the main deploy pipeline, live since 2026-06-03): a movement-feedback app gated by HTTP Basic Auth. - - **Authentication**: a single **operator-set shared credential** (username/password) in Secrets Manager. It is not collected from end users, is not tied to a person, and there are no end-user accounts — so it is operator-administered configuration, not third-party PII. +- **Silk Reeling Mirror app** (`infrastructure/silk-reeling.tf`, active in production — `create_silk_reeling = true` in the main deploy pipeline, live since 2026-06-03): a movement-feedback app gated by Amazon Cognito sign-in (`infrastructure/cognito.tf`). + - **Authentication**: Amazon Cognito accounts that only the operator can create (`allow_admin_create_user_only`; no self-registration), with required TOTP MFA; the API Gateway JWT authorizer and the app both validate the token. No reader can sign up, so nothing is collected from the public. - **Pose input**: the camera feed and pose extraction run **client-side in the browser**; raw video never leaves the device. The per-frame body landmarks the browser extracts (33 points per frame, no images) are sent over TLS to the app Lambda, which scores them and writes the feedback text itself. Nothing is sent to a third party: the app's optional LLM-written feedback is disabled in this deployment, and the Anthropic interconnection it used was removed under [SCN-2026-006](scn/SCN-2026-006-remove-anthropic-interconnection.md). - **Persistence**: requests are stateless; pose frames are transient and not persisted. No user profile, history, or biometric template is stored. -- **Analytics**: none. No JavaScript analytics, no tracking pixels, no third-party tracking. CloudFront access logs are excluded for cost. +- **Analytics**: none. No JavaScript analytics, no tracking pixels, no third-party tracking. CloudFront access logs record no IP address, user agent, referrer, cookies or query string, and are deleted after 90 days (`infrastructure/bootstrap/trust-access-logs.tf`, CDS-TRC-ACL). - **Cookies**: none set by the site. The only cookies that could touch a reader's browser are AWS-default CloudFront request-routing cookies (no user identification, no persistence beyond request). - **Lambda runtime KSI emitter**: processes only AWS configuration metadata (S3 bucket configuration, CloudFront distribution settings). No PII inputs, no PII outputs. - **CI/CD chain**: GitHub Actions, AWS API calls, Sigstore signing. No PII transits this chain. @@ -50,10 +50,10 @@ Per the FedRAMP 20x Significant Change Notifications rule, any change that intro | Determination date | 2026-05-08 | | Re-determined | 2026-06-07 — re-determination under [SCN-2026-001](scn/SCN-2026-001-silk-reeling.md) (Silk Reeling Mirror app). Determination unchanged: **no PII processed.** Pose video is processed client-side and never leaves the device; only derived non-PII metrics cross the boundary; the app credential is an operator-set shared secret, not third-party PII. No PIA triggered. | | Reviewer | Sam Aydlette (operator) | -| Next review | 2027-05-08 (annual), or upon SCN trigger | +| Re-check | every deploy and night by machine (`scripts/check-non-machine-vv.py`), each Annual Security Review (`scripts/hold-security-review.py`), and any SCN that changes data processing | | Full PIA required | No | -This determination is reviewed annually as part of [`docs/security-review.md`](security-review.md), and re-determined if the system's data-processing posture changes. +This determination is re-checked, with its sha256, in each Annual Security Review ([`docs/security-review.md`](security-review.md), `scripts/hold-security-review.py`), and re-determined in the pull request of any change to the system's data-processing posture. ## Reference diff --git a/docs/procedures/agency-access.md b/docs/procedures/agency-access.md new file mode 100644 index 00000000..df345ba7 --- /dev/null +++ b/docs/procedures/agency-access.md @@ -0,0 +1,19 @@ +# Agency Access to the Certification Package + +This procedure covers how the certification package is made available, how an access request is decided, what happens when one is denied, and how the inventory of agencies with access is kept. It implements CDS-UTC-AGA, CDS-UTC-AAD, CDS-TRC-AAI and CDS-TRC-SSM. Decision records: DEC-165 (this procedure) and DEC-194 (no engagement). + +**No engagement (DEC-194).** This system is a proof of concept. The operator does not engage FedRAMP or any federal agency about it: no real request is taken, decided, answered or notified. Every requester below is simulated, and the register `data/agency-access.json` may hold only entries marked `simulated: true` for an agency whose name ends "(simulated)"; `scripts/agency-access.py validate` fails the deploy on anything else. Anyone who really, really wants something can say hello on LinkedIn (the security contact in `/.well-known/security.txt`); the operator may consider it, with no obligation and no deadline. + +**The package is public.** Every piece of certification data is served without authentication from the trust center (https://samaydlette.com/trust/) and listed, with its URL, media type, signature and human-readable view, in the signed manifest https://samaydlette.com/.well-known/trust-manifest.json. Nobody needs to ask, register or hold an account to read or download any of it. + +**Decision by rule.** Nobody decides a request by hand. `scripts/agency-access.py` decides each access request on the day it arrives by fixed rules applied to what it asks for: a request for write access, for delivery other than HTTPS, for data beyond the public package, or from an agency that cannot be verified is denied, with the rule and its reason recorded; anything else is granted, because everything is already public. A withdrawal removes a grant from the inventory. + +**Denial notice.** The automated notifier writes a notice of every denial to the simulated FedRAMP as a log entry, and the clock requires it within 5 business days (US federal holidays excluded). The deploy computes each deadline and fails when a notice is late or overdue. Nothing is sent to FedRAMP or anyone: the notice is the log entry. + +**Inventory and history.** `scripts/agency-access.py inventory` prints the agencies and systems on record and the full history of requests, decisions, withdrawals and notices. With no real entries, it is empty. + +**Exercise.** On every deploy, `scripts/agency-access.py exercise` runs the rules and the notifier over a scenario of plainly fictional agencies (`data/agency-access-exercise.json`) dated relative to that day, with a simulated notifier outage and a slow notifier queue, so the late and overdue notices it must catch occur. It fails the deploy unless every outcome is the expected one. The signed log, headed by the no-engagement statement, is published at https://samaydlette.com/.well-known/agency-access-exercise.json. + +**Access records.** Viewers are never identified in the trust center's access records (CDS-TRC-ACL); beyond the 90-day raw records, only the published monthly access summaries are kept. + +**Verification.** Machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`), and re-checked, with its sha256, in each Annual Security Review (`scripts/hold-security-review.py`); a change is a reviewed pull request. diff --git a/docs/procedures/information-sharing.md b/docs/procedures/information-sharing.md new file mode 100644 index 00000000..6388d41a --- /dev/null +++ b/docs/procedures/information-sharing.md @@ -0,0 +1,23 @@ +# Information Sharing and Disclosure Standard + +This standard says what certification data is published, what is never published, and why publishing it is not likely to harm the offering. It implements CDS-CSO-RIS and records the determination CDS-CSO-RPS permits. Decision record: DEC-166. + +**What is public.** The whole FedRAMP certification package: every artifact the signed manifest (https://samaydlette.com/.well-known/trust-manifest.json) lists, the policies and procedures it links, and the repository that builds them. It is public because the offering has no federal data and no agency sponsor, and because showing the evidence openly is the purpose of this proof of concept. Anyone may read, download and verify it. + +**What is never published.** The deploy refuses to publish, and the gates named here fail the build on: + +- AWS account IDs, and ARNs that carry one (publication redaction gate, `scripts/check-published-redaction.py`; ARNs are published with the account replaced by `ACCOUNT`); +- secret values, keys, tokens and credentials of any kind (never placed in the inventory; Terraform state is read owner-only and deleted after use); +- personal email addresses and IAM user names (the rule records, trust center and boundary map refuse them); +- GitHub run IDs and raw logs, including CloudFront access logs: only aggregate counts are published (CDS-TRC-ACL); +- the contacts behind an agency access request: the register names agencies and systems, never people. + +**What is public on purpose, after consideration.** Some published detail could look sensitive. Each is published because an authorizing official needs it to judge the system, and none grants access by itself: + +- IAM role names and summaries of their least-privilege policies: they show who can change what; assuming a role needs the GitHub OIDC trust bound to this repository's reviewed environment; +- the API Gateway endpoint host and the CloudFront domain: both are already discoverable through DNS and every page load; +- component configuration, scanner findings with their dispositions, and vulnerability reports: they show how the system is built and how each finding was decided, which an authorizing official cannot judge without. + +**Determination.** The operator has determined that sharing the package publicly in this form is not likely to have an adverse effect on the offering, because it carries none of the items listed above and the items published on purpose give no access on their own. The determination is re-checked by machine: the redaction gate (`scripts/check-published-redaction.py`) screens every published file on every publish, and a new kind of artifact is a pull request that adds it to the publishers' lists, where this determination is revisited. + +**Verification.** Machine-checked on every deploy and every night (`scripts/check-non-machine-vv.py`), and re-checked, with its sha256, in each Annual Security Review (`scripts/hold-security-review.py`); a change is a reviewed pull request. diff --git a/docs/recovery-plan.md b/docs/recovery-plan.md index a44166c5..fd1df905 100644 --- a/docs/recovery-plan.md +++ b/docs/recovery-plan.md @@ -61,7 +61,7 @@ The full procedure is bounded by AWS resource creation latency (CloudFront takes - **Source code:** Distributed across every git clone in existence. RPO is "the time since the last fetch on any clone," which in practice is minutes. - **Site content:** Source-controlled and additionally backed up in the S3 bucket itself, which has versioning enabled. Any object can be rolled back to a prior version within S3's standard retention. -- **Infrastructure config:** Terraform configuration is in the repo. State for managed resources (Lambda, IAM role, EventBridge rule) is in `infrastructure/terraform.tfstate`; for a hard recovery into a new account it can be reconstructed via `terraform import` against the recreated resources. +- **Infrastructure config:** Terraform configuration is in the repo. State for managed resources (Lambda, IAM role, EventBridge rule) is in the S3 backend (`infrastructure/backend.tf`: bucket samaydlette-com-tfstate, object key "infrastructure/terraform.tfstate"); for a hard recovery into a new account it can be reconstructed via `terraform import` against the recreated resources. - **Build artifacts (KSI signals, bundles):** Reproducible from any commit on `main` by re-running the pipeline. No backup required because they are deterministically regenerable. The 24-hour RPO is comfortably met. Any change committed to `main` reaches the bucket within the time of one CI run (~5 minutes). The data loss window in the worst case is "whatever is in flight in an open editor at the moment of catastrophe," which is upper-bounded by the operator's typing speed, not by any backup cadence. @@ -70,17 +70,17 @@ The 24-hour RPO is comfortably met. Any change committed to `main` reaches the b KSI-RPL-TRC calls for persistent testing of recovery capability. The site's infrastructure was rebuilt from `terraform.tfvars.example` during the construction of this implementation; effective wall-clock time from "git clone" to "curl returns content" was under one hour, well inside RTO. That counts as a real recovery exercise with a much-larger-than-tabletop scope. -A formal tabletop is run annually, recorded below using this template: +Recovery is exercised by machine every month (DEC-195: nobody runs it by hand). `scripts/hold-recovery-exercise.py` runs in `evidence-nightly.yml` on the first of each month (first due 2026-11-01) and publishes `/.well-known/vdr-recovery-exercise-<date>.json`, signed, with the index `/.well-known/vdr-recovery-exercises.json`. Each exercise checks: -``` -## YYYY-MM-DD: Recovery tabletop +- **Restore point:** every file the deploy uploads is rebuilt from the deployed commit in git and compared byte for byte (sha256, the deploy's cache-busting query string aside) with what the site serves. The source of a restore and the live site are proved identical without writing to production. +- **Configuration:** versioning on every bucket and point-in-time recovery on the state-lock table are re-validated by the signed runtime signal of the deployed commit. +- **Tabletop (each November):** every in-scope loss scenario above is walked through with a simulated incident commander, Bea Kupp (simulated), and a simulated scenario injector, Dee Saster (simulated) (DEC-194); a scenario without a stated recovery, or a plan without its Recovery procedure section, fails the tabletop. -- **Scenario:** <e.g., "S3 bucket deleted"> -- **Steps executed:** <what was actually done, in order> -- **Wall-clock time to recover:** <duration> -- **Issues found:** <gaps or surprises> -- **Follow-up items:** <issues filed> -``` +A failing exercise fails the nightly and is not published; it is held again on the next run once fixed. `scripts/check-scheduled-review.py` fails the nightly from the day after a due date with no exercise published. + +## History: recovery tests recorded by hand + +The entry below was written by hand before the exercise was automated, and is kept as a record. ### 2026-05-06: Initial implementation as recovery test diff --git a/docs/rules-of-behavior.md b/docs/rules-of-behavior.md index d0163144..b838a0a0 100644 --- a/docs/rules-of-behavior.md +++ b/docs/rules-of-behavior.md @@ -9,7 +9,7 @@ Per NIST SP 800-53 PL-4, this document records the rules of behavior the system' Privileged accounts in scope: - AWS root account (operator's email) -- AWS IAM deployer principal (used by GitHub Actions; transitioning to OIDC role per POAM-001) +- GitHub Actions OIDC roles (the deploy, plan, nightly and maintenance roles; short-lived credentials, no access key) - AWS Lambda runtime IAM role (machine identity; non-privileged on most operations) - GitHub repository owner (operator's GitHub account) - GitHub Actions workflow identity (per-run OIDC token) @@ -21,19 +21,19 @@ The Lambda runtime role and the per-run GitHub OIDC token are machine identities By operating this system, the operator commits to the following: **Authentication.** -- Multi-factor authentication is enforced via Duo on AWS root and on the GitHub account. The operator does not disable MFA. +- Multi-factor authentication (virtual TOTP from an authenticator app; DEC-025, DEC-150) is enforced by AWS on the root and operator users and by GitHub on the owner account (DEC-151). The operator does not disable MFA. - Long-lived credentials (AWS access keys, GitHub PATs) are not generated unless required, and when required they are stored only in GitHub Actions encrypted secrets. -- The deployer's long-lived AWS access key is rotated every 90 days per the procedure in the [Secure Configuration Guide](policies/secure-configuration-guide.md) as a compensating control while [POAM-001](../data/decisions.json) (OIDC migration) remains open. Each rotation event is logged in [`docs/security-review.md`](security-review.md). +- CI reaches AWS only through GitHub OIDC role assumption with short-lived credentials; the deployer access key it replaced was deleted (DEC-001, remediated). - The operator does not share credentials, sessions, or MFA devices with any other person. **Access discipline.** -- AWS root is used only for billing, service quotas, and IAM-policy-of-last-resort actions. Day-to-day deploys use the IAM deployer principal. +- AWS root is used only for billing, service quotas, and IAM-policy-of-last-resort actions. Deploys run in GitHub Actions under OIDC roles. - The operator does not perform routine operations from AWS root. - The operator's GitHub session is the only authenticated path to push to `main`. Branch protection plus the OPA gate plus the SCN-Type validator constitute the technical enforcement. **Change management.** -- The default workflow is direct push to `main`. Pull requests are used only when collaboration or staged review is desired (rare). -- Every change is Routine Recurring by default; no SCN-Type label is required for routine work. The operator adds `SCN-Type: adaptive` or `SCN-Type: transformative` to the commit message (or PR description when a PR is used) only when the change meets those criteria per `SCN-CSO-EVA`. The fourth recognized value, `SCN-Type: emergency`, is reserved for emergency-change scenarios per `SCN-CSO-EMG`; see [`docs/incident-response.md`](incident-response.md) for the retroactive-documentation obligations that follow. +- Changes reach `main` through pull requests. Branch protection requires the four gate checks for everyone, administrators included, so a commit that has not passed them through a pull request is refused (see the [CM policy](policies/cm-policy.md) and the Secure Configuration Guide setting `github.main-required-checks`). +- Every change carries an explicit SCN evaluation (`SCN-CSO-EVA`): an `SCN-Type:` line, an `SCN-Rationale:` line and, where a notification is needed, an `SCN-Record:` line, in the commit message or PR description; there is no default, and the required `scn-tag` check fails a change without them (see the [CM policy](policies/cm-policy.md)). `SCN-Type: emergency` is reserved for emergency changes per `SCN-CSO-EMG`; see [`docs/incident-response.md`](incident-response.md) for the retroactive-documentation obligations that follow. - The operator does not bypass the OPA gate, the schema validators, the VDR aggregator, or the SCN tag validator with `--no-verify`-style overrides. **Information handling.** @@ -46,8 +46,8 @@ By operating this system, the operator commits to the following: - Spillage scenarios trigger the IR-9 procedure regardless of severity. **Continuous monitoring.** -- The operator reviews the runtime KSI signal at least weekly and reconciles any drift against the deploy-time signal. -- The operator runs the annual security review per [`docs/security-review.md`](security-review.md). +- The operator does not read the runtime KSI signal by hand: the evidence nightly verifies it and checks it against the deploy-time inventory on every run (`scripts/reconcile.py`, invariant (n)), and the run fails on a gap. +- The operator does not hold the Annual Security Review: `scripts/hold-security-review.py` holds it on its due date with a simulated reviewer ([`docs/security-review.md`](security-review.md)). DEC-195 lists the only recurring acts left to the operator. **Acceptable use of the system's outputs.** - Published artifacts at `/.well-known/` are public. The operator does not publish anything to `/.well-known/` that would be confidential, sensitive, or restricted. @@ -55,14 +55,14 @@ By operating this system, the operator commits to the following: ## Acknowledgment -The Rules of Behavior are acknowledged by the operator on initial system stand-up and on each annual security review. The acknowledgment record is the security review entry for the corresponding year. +The acknowledgement is recorded by machine. `scripts/hold-security-review.py` records it in `/.well-known/security-reviews.json` (`rulesOfBehavior`) with each Annual Security Review, and again whenever this document's sha256 changes; the person acknowledging is simulated, Pat Placeholder (simulated) (DEC-194). `scripts/check-scheduled-review.py --rules-of-behavior` fails the package maintainer's run, which every deploy calls, while the current version of this document has no acknowledgement. | Field | Value | | --- | --- | | Operator | Sam Aydlette | -| Initial acknowledgment | 2026-05-08 | -| Next review | 2027-05-08 (annual) | -| Re-acknowledgment trigger | Any Transformative change per SCN | +| Initial acknowledgment | 2026-05-08 (by hand, before the acknowledgement was automated) | +| Acknowledged by | Pat Placeholder (simulated), recorded by `scripts/hold-security-review.py` | +| Re-acknowledgment trigger | the Annual Security Review, and any change to this document (its sha256) | ## Reference diff --git a/docs/runbooks/dast-scanner-user.md b/docs/runbooks/dast-scanner-user.md new file mode 100644 index 00000000..d85f70d4 --- /dev/null +++ b/docs/runbooks/dast-scanner-user.md @@ -0,0 +1,90 @@ +# DAST scanner user (authenticated ZAP API scan) + +The authenticated ZAP API scan of the Silk Reeling API +(`.github/workflows/zap-dast.yml`, job `zap_api`) signs in as a dedicated +Cognito user in the Silk Reeling user pool. The user, like every user of that +pool, is created by the operator (the pool allows admin-created users only) and +must use TOTP MFA (the pool requires it). The workflow signs in with SRP and a +TOTP code (`scripts/dast-cognito-token.py`), the flows the SPA's app client +already allows; no app-client setting changes for it. + +Four repository secrets carry what the sign-in needs: + +| Secret | Value | +|---|---| +| `SILK_DAST_USERNAME` | the scanner user's username (an email-form name; no mailbox is needed) | +| `SILK_DAST_PASSWORD` | its password | +| `SILK_DAST_TOTP_SECRET` | its TOTP seed, from the one-time enrolment below | +| `SILK_DAST_USER_POOL_ID` | the Silk Reeling user pool id (SRP signs with it) | + +The deploy fails before `terraform apply` if any of them is missing (step +"Require the DAST scanner credentials"); the scan fails without them, and 72 +hours later so does every VDR build (`detection.zap-api`). + +## Create the user and the secrets (once) + +Run from a checkout of `main`, with AWS credentials that can administer the +pool and a `gh` login that can set repository secrets. Nothing secret is +echoed: the password is generated into a shell variable and the TOTP seed goes +straight into its secret. + +```bash +set -euo pipefail +export AWS_REGION=us-east-2 +REPO=sam-aydlette/samaydlette.com +POOL=$(aws cognito-idp list-user-pools --max-results 60 \ + --query "UserPools[?Name=='samaydlette-com-silk-reeling-users'].Id | [0]" --output text) +SCANNER='zap-dast-scanner@samaydlette.com' # any email-form name; no mail is sent to it +PW="$(python3 -c 'import secrets; print(secrets.token_urlsafe(24) + "aA1!")')" + +aws cognito-idp admin-create-user --user-pool-id "$POOL" --username "$SCANNER" \ + --user-attributes Name=email,Value="$SCANNER" Name=email_verified,Value=true \ + --message-action SUPPRESS > /dev/null +# The password goes in on stdin (printf is a shell builtin), never on a command line. +printf '{"UserPoolId":"%s","Username":"%s","Password":"%s","Permanent":true}' "$POOL" "$SCANNER" "$PW" \ + | aws cognito-idp admin-set-user-password --cli-input-json file:///dev/stdin + +printf '%s' "$SCANNER" | gh secret set SILK_DAST_USERNAME -R "$REPO" +printf '%s' "$PW" | gh secret set SILK_DAST_PASSWORD -R "$REPO" +printf '%s' "$POOL" | gh secret set SILK_DAST_USER_POOL_ID -R "$REPO" + +# TOTP enrolment: answers the MFA_SETUP challenge with a new authenticator seed +# (Cognito's public user APIs, no AWS credentials) and writes only that seed, +# to a file readable only by you. +curl -sf https://samaydlette.com/.well-known/silk-reeling-auth.json > /tmp/silk-auth.json +SECRET_DIR=$(mktemp -d) +SILK_DAST_USERNAME="$SCANNER" SILK_DAST_PASSWORD="$PW" SILK_DAST_USER_POOL_ID="$POOL" \ + python3 scripts/dast-cognito-token.py enroll --auth-config /tmp/silk-auth.json --out "$SECRET_DIR/seed" +SEED=$(cat "$SECRET_DIR/seed") +printf '%s' "$SEED" | gh secret set SILK_DAST_TOTP_SECRET -R "$REPO" + +# Check: a full sign-in works (shows the token's length, not the token). The +# wait moves past the enrolment's TOTP window: Cognito refuses a reused code. +sleep 31 +SILK_DAST_USERNAME="$SCANNER" SILK_DAST_PASSWORD="$PW" SILK_DAST_USER_POOL_ID="$POOL" \ + SILK_DAST_TOTP_SECRET="$SEED" \ + python3 scripts/dast-cognito-token.py token --auth-config /tmp/silk-auth.json --out "$SECRET_DIR/token" +wc -c < "$SECRET_DIR/token" +rm -rf "${SECRET_DIR:?}" +unset PW SEED +``` + +## First deploy after the change that introduced this + +The deploy and the nightly now require a successful ZAP run that includes the +API scan, and a CodeQL analysis of every category (`.github/workflows/codeql.yml`) +in the last 72 hours. After merging, before approving the deploy: + +1. Let **CodeQL** finish on the merge commit (it runs on push to `main`). +2. Run **ZAP DAST Scan** from the Actions tab and let it pass. +3. Approve the deploy. + +## Rotation and removal + +- Password: generate a new value and set it as above (`admin-set-user-password` + from stdin, `Permanent: true`), then update `SILK_DAST_PASSWORD`. +- TOTP seed: `aws cognito-idp admin-set-user-mfa-preference` cannot replace a + seed; delete and recreate the user, then repeat the steps above. +- Disable the scanner without deleting it: + `aws cognito-idp admin-disable-user --user-pool-id "$POOL" --username "$SCANNER"` + (the next ZAP run then fails, which is the intended signal). diff --git a/docs/runbooks/evidence-sla-alarm.md b/docs/runbooks/evidence-sla-alarm.md index 4057bb84..bfe560c3 100644 --- a/docs/runbooks/evidence-sla-alarm.md +++ b/docs/runbooks/evidence-sla-alarm.md @@ -7,15 +7,16 @@ The evidence SLA watchdog (`infrastructure/watchdog.tf`) emails the operator thr | `nightly-failed` | the evidence nightly's last run failed, or no run has reported in 26h | a gate failed; or the cron is disabled or stuck | | `vdr-age` | the published VDR is more than 24h old | the reporting policy is breached; nightly runs have failed or stopped | | `runtime-age` | the runtime signal is more than 26h old | the daily runtime-check Lambda has failed or stopped | +| `incident-report-overdue` | an incident report listed as due in `/.well-known/incident-reports.json` is past its Class C deadline, or the incident log is missing or unreadable | an Initial, Ongoing or Final incident report was not issued in time; or a vulnerability that is a FedRAMP Reportable Incident (VER-TFR-IRI/NRI) has no incident opened | | `artifact-stale` | any artifact listed in `infrastructure/schemas/freshness-config.json` is past its window, missing, or has no readable timestamp | no deploy within the deploy-cadence window; the corroboration was not re-run; or one of the above | The windows are governed values in `infrastructure/schemas/freshness-config.json`; the thresholds above are read from it. Change a window there, through review, never in the alarm. -Any alarm also fires if the watchdog stops publishing metrics, because missing data counts as a breach. If all four fire together, check the watchdog itself first (a missing or invalid freshness config stops it before it publishes anything). +Any alarm also fires if the watchdog stops publishing metrics, because missing data counts as a breach. If all five <!-- nmv-count watchdog-alarms=5 --> fire together, check the watchdog itself first (a missing or invalid freshness config stops it before it publishes anything). ## `nightly-failed` -1. Open the latest **Evidence Nightly** run in GitHub Actions. The status beacon at `/.well-known/vdr-status.json` gives its URL (`run_url`), the overall `result`, and each gate's outcome. +1. Open the latest **Evidence Nightly** run in GitHub Actions. The status beacon at `/.well-known/vdr-status.json` gives its workflow and commit (`run`; no run ID is published), its finish time, the overall `result`, and each gate's outcome; find the run in the Actions list by that time. 2. The GitHub issue labelled `evidence-freshness` names the gate and, for a vulnerability-gate failure, each finding with its advisory and any open Dependabot PR. - **Vulnerability gate failed:** follow [`vuln-gate-failure.md`](vuln-gate-failure.md). - **Reconciliation gate failed:** the live system and its documentation disagree. The step log names the failing invariant. Fix the drift through the reviewed deploy path; never weaken the gate. @@ -30,15 +31,21 @@ The policy is already breached, so treat this as the priority. It usually follow Check the compliance Lambda (`samaydlette-com-opa-compliance`): its CloudWatch logs, its EventBridge rule, and the shared dead-letter queue `samaydlette-com-opa-compliance-dlq` for failed invocations. +## `incident-report-overdue` + +The published incident log (`/.well-known/incident-reports.json`, `obligations_due`) names each report still due, for which incident or finding, and its deadline. Follow [`docs/incident-response.md`](../incident-response.md#reporting-fedramp-reportable-incidents-iec): record the report (or, for a finding with no incident, open the incident) in `data/incidents.json` and push it; the **Incident Reports** workflow validates, builds, signs and publishes within minutes, and the alarm clears once the republished log no longer lists the report as due. If the log itself is missing or unreadable, run the workflow by hand and check its publish step. + ## `artifact-stale` The watchdog's log line for the run lists the stale artifacts under `stale`. To see the same from outside, run `python3 scripts/check-evidence-freshness.py --all https://samaydlette.com`. -- **Deploy-cadence artifacts** (KSI signal, SSP, POA&M, trust center, boundary map, CDS artifacts): no deploy has run inside the window. Start and approve a deploy. +- **Deploy-cadence artifacts** (KSI signal, trust center, boundary map, CDS artifacts): no deploy has run inside the window. Start and approve a deploy. +- **Package artifacts** (Security Decision Record, Certification Package Overview, Ongoing Certification Report and its issue index, Quarterly Review index): `package-maintenance.yml` rewrites them daily. Follow its alert issue, fix the cause, and re-run the workflow (it can be started by hand); no deploy is needed unless the fix is a code change. +- **`vdr-non-machine-vv.json`:** a machine check of a policy, procedure or register failed, so `verifiedAt` is the epoch. The nightly's "Non-machine verification and validation status" step names the resource and line; fix the document and push. - **`boundary-corroboration.json`:** re-run `tools/boundary-map/corroborate.py`, commit the result, and deploy. - **Nightly artifacts** (`vdr-*`): follow `nightly-failed` / `vdr-age` above. -## All four at once +## All five at once Check the watchdog: its log group `/aws/lambda/samaydlette-com-evidence-watchdog`, the dead-letter queue, and its EventBridge rule. Each run logs one JSON line with the values it published, the config version, and the stale artifacts. diff --git a/docs/runbooks/fedramp-security-inbox.md b/docs/runbooks/fedramp-security-inbox.md new file mode 100644 index 00000000..b592a434 --- /dev/null +++ b/docs/runbooks/fedramp-security-inbox.md @@ -0,0 +1,79 @@ +# FedRAMP Security Inbox (simulated) + +> **This inbox is a simulation.** By the operator's decision, the FedRAMP Security Inbox does not exist for this proof of concept. No mail is received and none is sent. Its published contact reads: "Hit me up on LinkedIn: https://www.linkedin.com/in/sa2/". + +Rules: AFC-CSO-INB, TFG, RCV, CRA, EMR, IMA, ACK and NOC (FedRAMP Consolidated Rules 2026, AFC family). + +## What is real and what is simulated + +| Part | Real or simulated | +|---|---| +| Inbox logic (`scripts/_fsi.py`): classification, designators, deadlines, register, acknowledgement, paging | Real code, tested | +| Messages from FedRAMP | Simulated: synthetic messages in `data/fsi-simulation/messages.json` | +| Mail system (receiving, sending acknowledgements, delivering pages) | Simulated: outbound legs are recorded, never sent | +| Published contact (`data/cds/offering.json`, `fedramp_security_inbox.contact`, published in the CPO) | Real, and it says it is a simulation | +| Change-notice check and filing (AFC-CSO-NOC, `scripts/check-fsi-notice.py`) | Real: the check runs on every pull request and push; the deploy files each notice with the simulated FedRAMP (a log entry; nothing is sent) | + +## What runs on every deploy + +The deploy step "FedRAMP Security Inbox simulation (synthetic messages; nothing received or sent)" runs before the Security Decision Record is built. It calls `scripts/build-fsi-simulation.py`, which: + +1. Runs each synthetic message through the inbox logic: + - an Emergency Test from FedRAMP's Emergency sender; + - an Important message that tries to inject a header; + - a general message; + - a forged @gsa.gov Emergency that fails SPF, DKIM and DMARC; + - an auto-reply, bulk mail and a bounce; + - a message with an unreadable From line and a FedRAMP envelope sender; + - an Emergency from a non-designated sender; + - a look-alike domain and a display-name spoof; + - a message whose first acknowledgement attempt fails. +2. Compares every outcome with the expected one written beside the message: + - classification, designation and sender checks; + - whether the acknowledgement is sent or suppressed, and why; + - the page; + - the deadlines. +3. Checks each acknowledgement for header safety. Then it runs the messages again, and the retry pass must send only the failed acknowledgement and nothing twice. +4. Exercises the register: + - overdue items; + - an Important message refused triage until its stated timeframe is recorded; + - an Emergency reported once past its deadline until it is closed. +5. Exits 1 and writes nothing if any outcome differs. That fails the deploy before anything is published. + +On success, the deploy signs `fedramp-inbox-simulation.json` and publishes it at `/.well-known/fedramp-inbox-simulation.json`. The file is labelled `"simulation": true` and holds sender domains only. Its freshness is governed by `infrastructure/schemas/freshness-config.json`. + +## Reading the published result + +- `result` is `pass` on every published copy, because a failing run publishes nothing. +- `cases[].observed` shows what the logic did with each synthetic message. +- `register_check.checks[]` lists each register behaviour with its expected and observed values. +- `retry_pass` shows that redelivery sends nothing twice. + +## Changing a simulated outcome or adding a case + +Edit `data/fsi-simulation/messages.json`, including the `expected` block, and run: + + python3 scripts/build-fsi-simulation.py --output /tmp/fsi-sim.json + python3 -m pytest tests/test_fedramp_inbox.py + +`tests/fixtures/fsi/simulation-wrong-expectation.json` must stay identical to the messages file except for its one wrong expectation. A test enforces this. + +## Changing the published contact (AFC-CSO-NOC) + +1. In `data/cds/offering.json`, change `contact` and append a `history` entry with the new contact and `since`, the date of the change. +2. Merge it. The change takes effect when a deploy first publishes it; nothing has to happen by a date. + +`scripts/check-fsi-notice.py` fails the pull request if the contact changes without that entry, or if the history is rewritten. + +On every deploy, `scripts/submit-package.py` files a change notice with the simulated FedRAMP for each change in the history that has none yet. The deploy that first publishes a new contact files its notice that day, recording the deploy's date and commit (`publishedOn`, `publishedIn`); the log's `inboxContact` records which deploy first published the contact in force. The notice is an entry in `changeNotices` of the signed `/.well-known/package-submission-log.json`, with the simulated FedRAMP's receipt. Earlier notices are carried over unchanged. The deploy fails if any notice was filed more than one business day after the deploy that first published its change. The clock runs from publication, not from `since`, so a change merged but not deployed for a while is still notified on time, and a failed deploy (which publishes nothing) cannot make later deploys late. Nothing is sent to anyone, and no real FedRAMP is notified (DEC-194). + +## What a real inbox would need + +A real inbox would need four things: + +- a mail receiver for an address on the system's domain; +- storage for received messages; +- authenticated outbound mail for acknowledgements; +- delivery of pages to the operator. + +`scripts/_fsi.py` is written to be the logic behind them. None of this is deployed, by decision. diff --git a/docs/scn/README.md b/docs/scn/README.md index 037ab83a..6406be62 100644 --- a/docs/scn/README.md +++ b/docs/scn/README.md @@ -5,31 +5,49 @@ per the SCN rules in the CR26 corpus (`providers/20x/rules/significant-change-no ## Contents -- **[`scn-register.csv`](scn-register.csv)** — the machine-readable **and** human-readable - SCN register (`SCN-CSO-HRM`). One row per significant change, carrying the - `SCN-CSO-INF` required fields. CSV is the format the FedRAMP SCN beta used to satisfy - both readability requirements simultaneously. -- **`SCN-<year>-<n>-<slug>.md`** — the human-readable SCN record + copy of the security - impact analysis for each change (`SCN-CSO-INF`, including item 9, the SIA). - -## How this relates to the rest of the system - -- **Audit records (`SCN-CSO-MAR`):** the git history is the audit record of SCN - evaluation activity. Every commit to `main` carries an `SCN-Type:` categorization - validated by [`.github/workflows/scn-tag.yml`](../../.github/workflows/scn-tag.yml); - the default is `routine-recurring` per [`docs/policies/cm-policy.md`](../policies/cm-policy.md), - and the operator upgrades to `adaptive` / `transformative` / `emergency` explicitly. - The register and the per-change records here are the durable, structured complement to - that history for Adaptive and Transformative changes (which produce a SIA). -- **Historical notifications (`SCN-CSO-HIS`):** at least **12 months** of SCNs are kept - here with the FedRAMP Certification data. Rows are never deleted; superseded records - are retained. -- **Notification mechanism (`SCN-CSO-NOM`):** the system has no agency customers today, - so notification is met by publishing the updated certification data — the KSI signal, - SDR, CPO and VDR report at `/.well-known/` — alongside these records. -- **Emergency changes (`SCN-CSO-EMG`):** handled per the IR runbook - ([`docs/incident-response.md`](../incident-response.md)); retroactive SCN materials are - added here within the required window. +- **[`scn-register.csv`](scn-register.csv)** — the register, and the source every published + notification is built from. One row per adaptive or transformative change, carrying the + `SCN-CSO-INF` fields, the dates the notice deadlines count from (`date_started`, + `date_finished`, `verified_on`), and for transformative changes the plan, third-party-review and + documentation-update fields. `scripts/_scn.py` validates it (`tests/test_scn.py`); a + routine-recurring row is refused (`SCN-RTR-NNR`). A change that ships with the deploy that publishes + its record has `status` `on-deploy` and no `date_finished`: the deploy's SCN build records it as + implemented on the date of the first deploy that publishes it (`resolve_on_deploy`). +- **`SCN-<year>-<n>-<slug>.md`** — the human-readable record and copy of the security impact + analysis for each change (`SCN-CSO-INF` item 9). +- **[`evaluation-examples.md`](evaluation-examples.md)** — the evaluation format and one example + per type (`SCN-CSO-EVA`). +- **[`TEMPLATE-transformative.md`](TEMPLATE-transformative.md)** — the transformative record + template: notice windows, third-party review, verification and documentation update. + +## How the process runs + +- **Evaluation (`SCN-CSO-EVA`).** Every pull request carries `SCN-Type:`, `SCN-Rationale:` and, + for adaptive, transformative and emergency changes, `SCN-Record:`. The required `scn-tag` + check ([`.github/workflows/scn-tag.yml`](../../.github/workflows/scn-tag.yml)) fails without + them; there is no default. `class-change` always fails. A transformative change fails until its + initial plan has been published 30 business days and its final plan 10. +- **Audit records (`SCN-CSO-MAR`).** Each deploy appends the evaluation of every change merged + since the last one (commit, type, rationale, record, who merged it, when) to the signed, + append-only log at `/.well-known/scn-evaluations.json` (and `.md`). A deploy that would drop or + rewrite an entry fails. +- **Notification (`SCN-CSO-NOM`).** FedRAMP's rules name the notification method as an update to + the Certification Data. Each deploy publishes every register row in FedRAMP's SCN schema at + `/.well-known/significant-change-notifications.json` (signed), its human-readable view (`.md`) + and an Atom feed (`significant-change-notifications.atom`) anyone can subscribe to; the + Certification Package Overview lists them. A notice is given when it is first published, and + the index records that date beside its deadline. **Nothing is sent by email or to FedRAMP.** +- **Deadlines.** Business days exclude weekends and US federal holidays (`scripts/_bizdays.py`). + Adaptive: 10 after finishing (`SCN-ADP-NTF`). Transformative: initial plan 30 before starting, + final plan 10 before, 5 after finishing, 5 after verification, documentation within 30 + (`SCN-TRF-*`). Emergency: the retroactive record within 5 (`SCN-CSO-EMG`). The scheduled + [`scn-deadlines`](../../.github/workflows/scn-deadlines.yml) workflow fails and raises an issue + on anything overdue. +- **History (`SCN-CSO-HIS`).** Notifications are never pruned; a deploy that would drop one or + re-date a notice fails. Rows here are never deleted. + +The six records below predate the published index: their notices were first published by the +deploy that introduced it, after their deadlines, and the index says so. ## Index @@ -41,3 +59,4 @@ per the SCN rules in the CR26 corpus (`providers/20x/rules/significant-change-no | [SCN-2026-004](SCN-2026-004-evidence-alerting.md) | Adaptive | Evidence SLA watchdog and operator email alerting (backfilled record) | Implemented + post-impl. verified 2026-09-25 | | [SCN-2026-005](SCN-2026-005-ci-identity-split.md) | Adaptive | CI identity split: read-only plan role; deploy role trusts only the prod environment | Implemented and verified 2026-09-28 | | [SCN-2026-006](SCN-2026-006-remove-anthropic-interconnection.md) | Adaptive | Remove the Anthropic API interconnection; LLM feedback customer-configurable, off | Implemented (2026-10-27) | +| [SCN-2026-007](SCN-2026-007-fedramp-20x-rule-completeness.md) | Adaptive | FedRAMP 20x rule records and completeness gate; unattended publisher roles, edge access logging, DAST scanner user | Implemented on the first deploy that publishes it (`on-deploy`) | diff --git a/docs/scn/SCN-2026-003-cloudtrail.md b/docs/scn/SCN-2026-003-cloudtrail.md index b4edd66a..014fa072 100644 --- a/docs/scn/SCN-2026-003-cloudtrail.md +++ b/docs/scn/SCN-2026-003-cloudtrail.md @@ -38,8 +38,9 @@ lower edge of Adaptive: purely internal detective tooling). Strictly additive detective coverage. Tamper resistance: log-file validation; the deploy role cannot stop or delete the trail. Residuals (documented as inline checkov-skip rationales): SSE-S3 rather than a CMK (POAM-029-consistent), -no CloudWatch Logs integration or SNS notifications (quarterly review reads the -bucket; KSI-MLA-RVL). +no CloudWatch Logs integration or SNS notifications (KSI-MLA-RVL: at the time a +quarterly manual review of the bucket; since replaced by the nightly automated +audit-log review, `scripts/audit-log-review.py`, under SCN-2026-007). ### Verification plan (post-implementation) diff --git a/docs/scn/SCN-2026-007-fedramp-20x-rule-completeness.md b/docs/scn/SCN-2026-007-fedramp-20x-rule-completeness.md new file mode 100644 index 00000000..201abfd1 --- /dev/null +++ b/docs/scn/SCN-2026-007-fedramp-20x-rule-completeness.md @@ -0,0 +1,60 @@ +# SCN-2026-007 — Significant Change Notification & Security Impact Analysis +## FedRAMP 20x rule completeness: every applicable rule Implemented or Not Applicable + +<!-- AI-drafted for the operator's review. --> + +| | | +| --- | --- | +| **SCN ID** | SCN-2026-007 | +| **System** | samaydlette.com (FedRAMP 20x Class C proof of concept; not FedRAMP-certified) | +| **SCN type** | **Adaptive** (`SCN-ADP`) | +| **Status** | Implemented on the first deploy that publishes this record: the register row says `on-deploy`, and the deploy's SCN build records the finish date (`scripts/_scn.py` `resolve_on_deploy`). | +| **Date initiated** | 2026-11-05 | +| **Approver** | Sam Aydlette — System Owner / Authorizing Operator | + +## 1. Categorization (SCN-CSO-EVA) + +The change adds privileged identities, unattended publishing paths, broader read-only grants, a new trusted signer and a new store of access logs. That is more than routine-recurring maintenance. + +- **Two new IAM roles**, each assumable only from a GitHub Environment restricted to `main`: package maintenance and incident-report publishing. +- **Runtime emitter:** additional read-only grants (IAM, Lambda, API Gateway, Cognito, KMS) and one PutObject grant on `deploy-staging/*/ksi-signal-runtime.json`. +- **CloudFront access logging** (`infrastructure/bootstrap/trust-access-logs.tf`), into the existing encrypted log bucket with a 90-day expiry. CloudFront cannot log by path, so every request is logged, with a field allowlist that drops the client IP, forwarded-for, port, user agent, referrer, cookies and query string at the edge. The deploy role reads the records and counts only `/.well-known/` and `/trust/`; only aggregate counts are published. +- **Account-wide read-only reads on the deploy role** (`infrastructure/bootstrap/deploy-config-reads.tf`): IAM account summary, password policy, users, virtual MFA devices and the account-level S3 Block Public Access setting, plus user and group policy reads, so the deploy can compare the privileged accounts' settings with the Secure Configuration Guide. Metadata only; no secret value is readable. +- **Read-only CORS on `/.well-known/`** (`infrastructure/bootstrap/cloudfront.tf`): `Access-Control-Allow-Origin: *` with GET, HEAD and OPTIONS and no credentials, so a program on any origin can read the certification data. +- **A new trusted signing identity:** the simulated assessor workflow (`.github/workflows/simulated-assessor.yml`) signs its assessment results keylessly under its own identity, and the SDR and CPO builders accept assessment results only from that identity. +- **Scheduled publishing workflows** on GitHub Actions (package maintenance, incident publisher, availability probe, SCN deadlines). +- **A DAST scanner user** in the existing Cognito user pool. +- **Nightly audit-log read:** the evidence nightly role gains `cloudtrail:LookupEvents`, read-only (`infrastructure/bootstrap/evidence-nightly.tf`), and the deploy role may read that role's inline policy so the secure-configuration comparison can check the grant. The package maintenance role may also write the Annual Security Review's objects (`security-review*`). +- **Changes to the compliance engine** (pull request #518). Each changes how the security posture is verified, so each is adaptive: + - **Assessor binding:** each simulated assessment set names the commit and published KSI signal it covered. The SDR and CPO builders refuse a set covering any other. The deploy reads the live signal itself before the SDR is built, and the SDR states what was covered (`providerExtensions.assessmentCoverage`). + - **Post-deploy assessment:** after every deploy, the same simulated assessor assesses the just-published state, which must carry the deployed commit. Its set must cover this commit and the signal this deploy published. A failure fails the run and raises the deployment-failure issue. + - **History fetches:** the access summary, the certification-report index and the package submission log are fetched fail-closed. Only a 404 starts a history; any other failure stops the deploy. + - **Certification reports:** the simulated FedRAMP issues a stand-in certification report only in response to a simulated package submission: the first, after an adaptive or transformative SCN, and once a year. The report is logged with the date it was received. A report first published more than 14 days after receipt fails the deploy. Every report says it is not issued by FedRAMP and that the system is not certified. + - **Inbox change notices (AFC-CSO-NOC):** each FedRAMP Security Inbox contact change is filed with the simulated FedRAMP as a log entry; nothing is sent. The change takes effect when a deploy first publishes it: that deploy files the notice and is recorded in the submission log, and the deploy fails when a notice was filed more than one business day after it. A change merged but not yet deployed cannot go stale. + - **Exploitation assessment (DEC-181):** rests on automated sources only; a screen fails any in-force decision or rule record that commits the operator to a manual review. + - **Package history:** the SDR, CPO and OCR previous copies are fetched fail-closed, like the other histories. + - **Failure alerts:** the deployment-failure notification also covers the unit tests (which hold the rule-completeness gate) and the security scan on `main`. + - **Human-readable views:** every publishing workflow (deploy, evidence nightly, package maintainer, incident publisher) puts a complete `.view.md` beside every JSON or CSV it puts, including incident reports, certification reports, issued Ongoing Certification Reports, snapshots and Quarterly Reviews. The trust manifest lists views from the publisher table (`scripts/_signers.py`) and fails if a JSON was built without one. + - **Email addresses:** the publication redaction gate fails any published file carrying an email address outside the site's domain. + - **No-engagement statement (DEC-194):** every simulated output (package submission log, certification-report index, inbox simulation, incident log, delivery log and reports, SCN index) carries the statement. + - **Corroboration:** the operator-run corroboration checks each signature against the workflows that write the file, not against its refresh cadence. + - **Scheduled reviews (DEC-195):** every recurring review a person used to hold is a mechanism with simulated participants. The audit-log review runs every night (`scripts/audit-log-review.py`): CloudTrail write events and GitHub's record of `main`, judged by rule, with a planted simulated intruder that must be caught on every run; a write evaluated as a possible reportable incident fails the nightly, and any other unexpected write is a process finding. The recovery exercise runs every month (`scripts/hold-recovery-exercise.py`): the live site is compared byte for byte with the deployed commit, versioning and point-in-time recovery are re-read from the runtime signal, and a simulated tabletop is held each November. The Annual Security Review (`scripts/hold-security-review.py`) re-checks documents, new component types against the threat model, decisions, findings, incident patterns and recurring cost, and records the rules-of-behavior acknowledgement. An overdue review fails the run (`scripts/check-scheduled-review.py`). Each counts as an automated method for its KSIs in the SDR only when its signed record verifies and is current. A document, decision, rule record or control statement that commits a person to recurring manual work fails the machine checks. + - **Not-certified status:** the CPO, the SDR and the trust center data state `certification.status` "not certified (proof of concept)", from one source. A package without it is never submitted. + +It is not Transformative: +- no new external service: GitHub and AWS are already in the boundary; +- no new data flow carrying federal data; there is no federal data; +- no customer-responsibility or certification-class change. + +## 2. Required information (SCN-CSO-INF) + +- **Short description:** the rule register, its completeness gate and the work that brings every applicable FedRAMP 20x Class C rule to Implemented or Not Applicable. Outside parties (assessor, FedRAMP, agencies, incident recipients, mail, SAM.gov) are simulated and flagged; nothing is sent to anyone. +- **Reason for change:** show FedRAMP 20x adherence as evidence built from code, with the deploy refusing to publish any gap. +- **Customer impact:** none. There are no agency customers. +- **Plan and timeline:** bootstrap applies by the operator, then repository variables, environments, secrets and labels, then the merge to `main` and one gated deploy, then post-deploy verification (`verify-published.sh`, storycheck on the live site). + +## 3. Security impact + +- **New risks:** the two unattended roles can write published artifacts without a reviewer. Each is limited to its own key prefixes and to runs on `main`. The access logs hold no client IP address or other client identifier (they are dropped at the edge); the raw records expire after 90 days and are read by the deploy role to build the monthly counts. The operator's administrative access also reaches the bucket. The deploy role can read IAM and S3 account-setting metadata account-wide, but no secret value. Any origin can read `/.well-known/` without credentials, which publishes nothing that is not already public. The builders accept assessment results signed by one more identity, the simulated assessor's, and nothing else from it. The DAST user is a real account in the app's user pool, with TOTP MFA. +- **New risks (scheduled reviews):** the nightly role can read CloudTrail's event history, which names the principals of every write; the review publishes only principal categories, never names or ARNs, and passes the redaction gate. A planted intruder event is plainly simulated and dated 1999-12-31 so it cannot be mistaken for a real one. +- **Reductions:** the audit log is reviewed by machine every night (`scripts/audit-log-review.py`), replacing the quarterly manual review, and a stopped trail, a new access key or user, a disabled key or a removed public access block fails the nightly. IAM user names, GitHub run IDs and the personal email address leave published output, each with a gate; any email address outside the site's domain fails the publication gate. An assessment of any commit or signal other than the one stated is refused. A failed post-deploy assessment fails the run; what was published stays until the next deploy. A failed history fetch stops the deploy instead of restarting the history. The CPO and SDR state in their JSON that the system is not certified. The deploy fails when any rule record is open or any KSI is short of two automated methods without an in-force accepted decision record for the shortfall. diff --git a/docs/scn/TEMPLATE-transformative.md b/docs/scn/TEMPLATE-transformative.md new file mode 100644 index 00000000..2c5ecdfd --- /dev/null +++ b/docs/scn/TEMPLATE-transformative.md @@ -0,0 +1,51 @@ +# SCN-YYYY-NNN — Transformative change: <title> + +Copy this file to `SCN-YYYY-NNN-<slug>.md` and add the row to +[`scn-register.csv`](scn-register.csv) **before** the change starts. The +register row is what the deploy publishes and what the checks read; the columns +named below are required by [`scripts/_scn.py`](../../scripts/_scn.py) for a +transformative row. + +## Timeline and notices + +| Notice | Rule | When | Register column that drives it | +| --- | --- | --- | --- | +| Initial plan | SCN-TRF-NIP | published ≥ 30 business days before `date_started` | the row exists with `date_started` | +| Final plan | SCN-TRF-NFP | published ≥ 10 business days before `date_started` | `plan_final` = `yes` | +| After finishing | SCN-TRF-NAF | within 5 business days of `date_finished` | `date_finished` | +| After verification | SCN-TRF-NAV | within 5 business days of `verified_on` | `verified_on`, `sar_reference`, `new_risks_summary` | +| Documentation updated | SCN-TRF-UPD | within 30 business days of `date_finished` | `docs_to_update`, `docs_updated_on` (or `docs_update_not_required`) | + +A notice is given when a deploy publishes it: the index records each notice's +deadline and the date it was first published. The SCN gate blocks the merge of +the change until the initial and final plans have been published long enough. +Business days exclude weekends and US federal holidays. + +## 1. Categorization (SCN-CSO-EVA) + +Why this change is transformative (FRD-TRF), and why it is not a class change. + +## 2. Required information (SCN-CSO-INF) + +Register columns: `fedramp_id`, `assessor_name`, `related_vulnerability`, +`categorization_rationale`, `short_description`, `reason_for_change`, +`customer_impact`, `plan_and_timeline`, `sia_reference` (this file), +`approver_name`, `approver_title`. + +## 3. Likely security impacts and changes in risk (SCN-TRF-NIP) + +Summary in `new_risks_summary`; detail here. + +## 4. Third-party review (SCN-TRF-TPR) + +- `tpr_human_validation`: `yes` or `no` — does the scope or impact need human validation? +- `tpr_assessor_or_reason`: the assessor engaged to review the scope and impact before the change starts, or why none was engaged. + +## 5. Verification, assessment and validation (SCN-TRF-NAV) + +The plan, the result, and `sar_reference`: the security assessment report, or why there is none. + +## 6. Documentation updates (SCN-TRF-UPD) + +`docs_to_update` (semicolon-separated paths) and, once done, `docs_updated_on`. +If none is needed, `docs_update_not_required` says how that was determined. diff --git a/docs/scn/evaluation-examples.md b/docs/scn/evaluation-examples.md new file mode 100644 index 00000000..0afe8ffe --- /dev/null +++ b/docs/scn/evaluation-examples.md @@ -0,0 +1,98 @@ +# Significant-change evaluation: format and one example per type (SCN-CSO-EVA) + +Every pull request (or direct push) to `main` carries an evaluation in its +description. [`.github/workflows/scn-tag.yml`](../../.github/workflows/scn-tag.yml) +fails the change without one; there is no default. The rules are in +[`scripts/_scn.py`](../../scripts/_scn.py). + +``` +SCN-Type: <not-significant | routine-recurring | adaptive | transformative | emergency | class-change> +SCN-Rationale: <one line: why the change is this type> +SCN-Record: SCN-YYYY-NNN (adaptive, transformative and emergency only) +``` + +The deploy copies every merged evaluation into the append-only log at +`/.well-known/scn-evaluations.json` (SCN-CSO-MAR). + +The types follow FedRAMP's definitions (FRD-SGC, FRD-RTR, FRD-ADP, FRD-TRF). A +change that is not likely to substantively affect the security or privacy +posture is **not-significant**. Examples marked *fictitious* are permitted by the +SCN-CSO-EVA artifact; they show the reasoning and are not changes to this system. + +## not-significant + +*Fictitious.* A typo fix on the about page. + +``` +SCN-Type: not-significant +SCN-Rationale: content-only edit to a public page; no component, boundary, data flow or access change. +``` + +## routine-recurring + +*Fictitious.* The weekly Dependabot patch bump of a library already in the +inventory, with no breaking change. + +``` +SCN-Type: routine-recurring +SCN-Rationale: weekly patch bump of an inventoried library, part of ongoing vulnerability remediation; no breaking change. +``` + +No notification is made (SCN-RTR-NNR): the gate refuses an `SCN-Record` on this +type, and the register refuses a routine-recurring row. + +## adaptive + +*Real:* [SCN-2026-006](SCN-2026-006-remove-anthropic-interconnection.md), the +removal of the Anthropic API interconnection. + +``` +SCN-Type: adaptive +SCN-Rationale: removes an external interconnection, a boundary-crossing flow and a secret; no new service or data, no class change. +SCN-Record: SCN-2026-006 +``` + +The record goes into [`scn-register.csv`](scn-register.csv) and is published +within 10 business days of the change finishing (SCN-ADP-NTF). + +## transformative + +*Fictitious.* The offering begins accepting agency user accounts and storing +their data: a new capability that changes how customers use the service. + +``` +SCN-Type: transformative +SCN-Rationale: introduces federal customer data and agency accounts, which changes existing risk determinations. +SCN-Record: SCN-2027-001 +``` + +The record is written from [`TEMPLATE-transformative.md`](TEMPLATE-transformative.md) +first. The gate blocks the merge until the initial plan has been published 30 +business days and the final plan 10 (SCN-TRF-NIP, SCN-TRF-NFP). + +## emergency + +*Fictitious.* A leaked credential is rotated immediately. + +``` +SCN-Type: emergency +SCN-Rationale: rotates a leaked credential now; waiting for notice windows would itself raise risk. +SCN-Record: SCN-2026-099 +``` + +The retroactive record is due within 5 business days +([`docs/incident-response.md`](../incident-response.md)); the scheduled deadline +check ([`.github/workflows/scn-deadlines.yml`](../../.github/workflows/scn-deadlines.yml)) +fails until it is in the register. + +## class-change + +*Fictitious.* A change that would move the offering out of Class C. + +``` +SCN-Type: class-change +SCN-Rationale: the offering would hold data that takes it above Class C. +``` + +The gate always fails this type: a class change is a new certification and +needs a new assessment, not a significant change notification. diff --git a/docs/scn/scn-register.csv b/docs/scn/scn-register.csv index a0842d96..a035f5e4 100644 --- a/docs/scn/scn-register.csv +++ b/docs/scn/scn-register.csv @@ -1,7 +1,8 @@ -scn_id,fedramp_id,assessor_name,related_vulnerability,scn_type,categorization_rationale,short_description,reason_for_change,customer_impact,plan_and_timeline,sia_reference,new_risks_summary,approver_name,approver_title,status,date_initiated,date_finished,notify_by -SCN-2026-001,<FR-CERT-ID>,N/A (sole-operator self-attestation; no 3PAO engaged),None (proactive feature addition),adaptive,"Net-new service component with new public ingress and new external egress; no FedRAMP Certification class change and no federal customer data introduced, so not transformative and not a class change; not regular/routine maintenance, so not routine-recurring. Resolves to Adaptive per SCN-CSO-EVA. Sits at the upper edge of Adaptive due to the new non-FedRAMP-authorized external interconnection (Anthropic); the absence of federal customer data is what keeps it out of Transformative.","Adds the gated ""Silk Reeling Mirror"" app: a public, HTTP-Basic-Auth-gated API Gateway HTTP API -> Python 3.13 ZIP Lambda serving a browser SPA; the Lambda calls the Anthropic API to generate movement-feedback text.",New self-service capability addition to the site.,New customer/operator-responsibility control: operator-set HTTP Basic Auth credential (POAM-021). SAML/IdP federation is the recommended upgrade. No change to existing customers' configuration responsibilities.,"Gated deploy (create_silk_reeling=true) -> OPA + Checkov + tfsec gate -> Syft/Grype SCA over the built artifact -> VDR report regenerated -> post-implementation secure-configuration verification (Adaptive requirement) -> KSI signal + OSCAL SSP re-emitted. Controls/KSIs to re-verify: RA-5/VDR-*, SA-9/CA-3, SC-7, AC-3/IA-2, AU-2/AU-3, SC-12/SC-28.",docs/scn/SCN-2026-001-silk-reeling.md,"POAM-019..024 (all risk-accepted, Low residual) plus the new-ecosystem SCA blind-spot, remediated by adding Syft/Grype SCA of the built Lambda+SPA artifact to CI feeding the VDR aggregator (RA-5/VDR-CSO-DET).",Sam Aydlette,System Owner / Authorizing Operator,Implemented — live in production (first prod deploy 2026-06-03 via PR #82); post-implementation verification COMPLETE 2026-06-08 at prod commit 354da59 (pass: KEV 0 / blocking 0; SSP data-flow + interconnection rendered; deployed Python/JS deps CVE-free; CM-8 inventory complete),2026-06-03,2026-06-06,No necessary parties (no sponsor/customers); the public GitHub push that publishes the certification data is the notification (SCN-CSO-NOM / SCN-ADP-NTF) -SCN-2026-002,<FR-CERT-ID>,N/A (sole-operator self-attestation; no 3PAO engaged),POAM-021 / POAM-022 / POAM-023 (single-factor shared credential; authorizer-less API; unthrottled credential endpoint),adaptive,"Replaces the end-user authentication mechanism of an existing public-facing component (HTTP Basic Auth -> Cognito with mandatory TOTP MFA + API Gateway JWT authorizer). No class change, no federal customer data, no new external interconnection, so not Transformative; an authentication-model change is not routine-recurring maintenance. Resolves to Adaptive per SCN-CSO-EVA. Backfilled record: the change shipped 2026-06-22 via the gated PR flow; this row completes the register (SCN-CSO-HIS).","Silk Reeling auth replacement: Basic Auth retired; Cognito user pool (mandatory TOTP MFA, 14-char minimum, admin-only creation) with Hosted UI (code + PKCE); JWT authorizer on ANY /api/{proxy+}; $default stays open serving the SPA shell only; stage throttling 20 rps / burst 10; API access logging to a CMK-encrypted log group.",Remediate POAM-021/022/023: retire the single-factor shared credential and gate the data API at the edge with rate limiting.,App users sign in with an invited individual account and mandatory TOTP MFA instead of a shared password. No agency customers exist.,"Gated deploy (OPA + Checkov gate) -> Cognito pool + authorizer + throttling applied via Terraform -> post-implementation verification of live authorizer/MFA/throttling/logging -> KSI signal + OSCAL SSP + POA&M re-emitted. Controls/KSIs re-verified: IA-2(x)/IA-8, AC-7, SC-5, AU-2/AU-3, KSI-IAM-*.",docs/scn/SCN-2026-002-cognito-auth.md,"Shared-credential and unthrottled-endpoint risks retired with POAM-021/023 closure. Residual: TOTP is not phishing-resistant (WebAuthn/FIDO2 upgrade path documented, POAM-025 direction); Cognito availability becomes a sign-in dependency (AWS-managed).",Sam Aydlette,System Owner / Authorizing Operator,"Implemented - live in production since 2026-06-22 (Task 3; POAM-021/022/023 closed); post-implementation verification COMPLETE 2026-07-06 via read-only AWS CLI (JWT authorizer on data routes, MFA ON, 14-char policy, admin-only creation, 20/10 throttling, access logging live)",2026-06-20,2026-06-22,No necessary parties (no sponsor/customers); the public GitHub push that publishes the certification data is the notification (SCN-CSO-NOM / SCN-ADP-NTF) -SCN-2026-003,<FR-CERT-ID>,N/A (sole-operator self-attestation; no 3PAO engaged),AU-2/AU-11 control-plane audit gap (no durable CloudTrail trail; 90-day Event History only),adaptive,"Net-new internal service component (CloudTrail trail + delivery bucket). No new ingress/egress, no auth change, no customer impact, no class change - not Transformative; a net-new component is not routine-recurring maintenance. Conservatively Adaptive per SCN-CSO-EVA (lower edge: purely internal detective tooling).","Multi-region CloudTrail management-events trail with log-file validation, delivered to a dedicated locked-down S3 bucket; AU-11 tiering 12mo active + Deep Archive to 30mo. Deploy role can create/configure but not stop/delete the trail.",Close the control-plane audit gap: SSP AU-family statements assumed CloudTrail coverage that did not durably exist.,None (internal detective control).,"Bootstrap apply (deploy-role cloudtrail-management grant, manual) -> merge -> gated deploy creates trail + bucket -> post-implementation verification (get-trail-status IsLogging, objects delivered, audit_log_trail component in the next signal).",docs/scn/SCN-2026-003-cloudtrail.md,Strictly additive detective coverage. Residuals documented inline: SSE-S3 not CMK (POAM-029-consistent); no CloudWatch Logs integration / SNS (quarterly review per KSI-MLA-RVL).,Sam Aydlette,System Owner / Authorizing Operator,Implemented - trail live and delivering; post-implementation verification COMPLETE 2026-07-09 (gate green end-to-end; AWSLogs/<account>/ objects delivered; audit_log_trail component in the published signal with data_sensitivity internal; POAM-029/032 dispositions in the published VDR),2026-07-08,2026-07-09,No necessary parties (no sponsor/customers); the public GitHub push that publishes the certification data is the notification (SCN-CSO-NOM / SCN-ADP-NTF) -SCN-2026-004,<FR-CERT-ID>,N/A (sole-operator self-attestation; no 3PAO engaged),CA-7/IR-6 monitoring gap (evidence nightly failed 2026-09-09..24 unalerted; VDR 12 days stale vs 24h policy; live drift check skipped),adaptive,"Net-new internal components (watchdog Lambda, 3 CloudWatch alarms, CMK-encrypted SNS topic) plus one new outbound flow: alarm metadata by email to the operator email, out of boundary per ROT #3 (flow I). Not Transformative: no federal data, no critical third party handling significant information, no auth/customer-responsibility/class change. Backfilled: shipping PRs #357/#359/#361 carried no SCN-Type and defaulted to routine-recurring.","Evidence SLA watchdog pages the operator by email (SNS) when published evidence goes stale or the evidence nightly fails; nightly runs twice daily, writes a status beacon, and runs its live drift check independently of the vulnerability gate.",The evidence nightly failed every night 2026-09-09..24 with only a GitHub issue as signal; the published VDR breached the 24h reporting policy and the vulnerability gate short-circuited the live reconciliation.,None (no agency customers; internal detective control).,"Bootstrap grants (deploy role, operators group; operator-applied after plan review) -> merge -> gated deploy creates watchdog/topic/alarms -> out-of-band email subscription -> post-implementation verification (forced alarm, delivery metrics).",docs/scn/SCN-2026-004-evidence-alerting.md,"Additive detective control. New outbound flow carries alarm metadata only (no evidence content or credentials); SNS email is not end-to-end encrypted, recorded as acceptable for that content. Watchdog has no internet egress; unattended-path permissions unchanged. ~$0.80/month.",Sam Aydlette,System Owner / Authorizing Operator,"Implemented 2026-09-25; post-implementation verification COMPLETE 2026-09-25 (forced alarm: 2 delivered, 0 failed; all alarms OK). Inventory/SSP/boundary documentation aligned 2026-09-27.",2026-09-25,2026-09-25,No necessary parties (no sponsor/customers); the public GitHub push that publishes the certification data is the notification (SCN-CSO-NOM / SCN-ADP-NTF) -SCN-2026-005,<FR-CERT-ID>,N/A (sole-operator self-attestation; no 3PAO engaged),AC-6/CM-5 exposure: pull-request CI runs received the full deploy role without the prod environment approval,adaptive,"Changes the privileged-identity model of the CI/CD path (one new read-only IAM role; deploy-role trust narrowed to the reviewer-gated prod environment). Same class as SCN-2026-002's access-model change. Not Transformative: no new external service, data flow or component beyond one IAM role; no federal data; no customer-responsibility or class change.","compliance-check (terraform plan + OPA, on pull requests and main pushes) moves to a read-only plan role; the deploy role then trusts only the reviewer-gated prod environment.","The deploy role trusted pull_request and main-ref subjects because compliance-check planned with it, so every PR run held the full deploy permission set (IAM PutRolePolicy/PassRole on a Lambda role, Lambda code updates) without the prod approval gate.",None (no agency customers).,#374 plan role (operator-applied) -> AWS_PLAN_ROLE_ARN -> #375 compliance-check switch (verified by its CI run) -> this change: deploy trust narrowed to environment:prod (operator-applied after plan review) -> post-implementation verification.,docs/scn/SCN-2026-005-ci-identity-split.md,Net reduction: deploy credentials exist only inside an approved deploy. Plan role reads the Terraform state object (not new exposure: the deploy role already could from the same PRs) and cannot write except the lock item; data-plane reads denied. No cost.,Sam Aydlette,System Owner / Authorizing Operator,"Implemented and verified 2026-09-28 (#374, #375, #378 applied; deploy run 36434974425, PR check 36451980170, main-push check 36483804056).",2026-09-28,,No necessary parties (no sponsor/customers); the public GitHub push that publishes the certification data is the notification (SCN-CSO-NOM / SCN-ADP-NTF) -SCN-2026-006,<FR-CERT-ID>,N/A (sole-operator self-attestation; no 3PAO engaged),"POAM-020 (Anthropic API interconnection, risk-accepted); POAM-019 (Anthropic key rotation, false positive)",adaptive,"Removes an external interconnection, a boundary-crossing data flow and a secret; changes the authorization boundary and SSP interconnections, so more than routine-recurring. Not Transformative: no new service, data flow or component; no federal data; no customer-responsibility or class change.","Silk Reeling app stops calling the Anthropic API and writes feedback from the scores; the API-key secret, its two IAM grants and env var are removed. LLM feedback becomes a customer-configurable option, disabled in this deployment.",The interconnection was a risk-accepted SA-9/CA-3 item to a service without a FedRAMP authorization and its key had expired; the app produces useful feedback without it.,None (no agency customers). App users get feedback written from their scores.,"App default-off (silk-reeling-mirror ADR-0009) -> this change (terraform plan review, gated deploy) -> post-implementation verification -> close POAM-020 and retire POAM-019.",docs/scn/SCN-2026-006-remove-anthropic-interconnection.md,"Net reduction: no app data leaves the boundary, no third-party credential stored, two IAM grants removed. No new risk.",Sam Aydlette,System Owner / Authorizing Operator,Implemented — verified live 2026-10-27 (secret scheduled for deletion; IAM and key policies clear; published SSP and signal without the interconnection; verify-published PASS),2026-10-26,2026-10-27,No necessary parties (no sponsor/customers); the public GitHub push that publishes the certification data is the notification (SCN-CSO-NOM / SCN-ADP-NTF) +scn_id,fedramp_id,assessor_name,related_vulnerability,scn_type,categorization_rationale,short_description,reason_for_change,customer_impact,plan_and_timeline,sia_reference,new_risks_summary,approver_name,approver_title,status,date_initiated,date_started,date_finished,verified_on,emergency,evaluation_prs,plan_final,tpr_human_validation,tpr_assessor_or_reason,sar_reference,docs_to_update,docs_updated_on,docs_update_not_required +SCN-2026-001,<FR-CERT-ID>,N/A (sole-operator self-attestation; no 3PAO engaged),None (proactive feature addition),adaptive,"Net-new service component with new public ingress and new external egress; no FedRAMP Certification class change and no federal customer data introduced, so not transformative and not a class change; not regular/routine maintenance, so not routine-recurring. Resolves to Adaptive per SCN-CSO-EVA. Sits at the upper edge of Adaptive due to the new non-FedRAMP-authorized external interconnection (Anthropic); the absence of federal customer data is what keeps it out of Transformative.","Adds the gated ""Silk Reeling Mirror"" app: a public, HTTP-Basic-Auth-gated API Gateway HTTP API -> Python 3.13 ZIP Lambda serving a browser SPA; the Lambda calls the Anthropic API to generate movement-feedback text.",New self-service capability addition to the site.,New customer/operator-responsibility control: operator-set HTTP Basic Auth credential (POAM-021). SAML/IdP federation is the recommended upgrade. No change to existing customers' configuration responsibilities.,"Gated deploy (create_silk_reeling=true) -> OPA + Checkov + tfsec gate -> Syft/Grype SCA over the built artifact -> VDR report regenerated -> post-implementation secure-configuration verification (Adaptive requirement) -> KSI signal + OSCAL SSP re-emitted. Controls/KSIs to re-verify: RA-5/VDR-*, SA-9/CA-3, SC-7, AC-3/IA-2, AU-2/AU-3, SC-12/SC-28.",docs/scn/SCN-2026-001-silk-reeling.md,"POAM-019..024 (all risk-accepted, Low residual) plus the new-ecosystem SCA blind-spot, remediated by adding Syft/Grype SCA of the built Lambda+SPA artifact to CI feeding the VDR aggregator (RA-5/VDR-CSO-DET).",Sam Aydlette,System Owner / Authorizing Operator,Implemented — live in production (first prod deploy 2026-06-03 via PR #82); post-implementation verification COMPLETE 2026-06-08 at prod commit 354da59 (pass: KEV 0 / blocking 0; SSP data-flow + interconnection rendered; deployed Python/JS deps CVE-free; CM-8 inventory complete),2026-06-03,,2026-06-06,2026-06-08,no,#82,,,,,,, +SCN-2026-002,<FR-CERT-ID>,N/A (sole-operator self-attestation; no 3PAO engaged),POAM-021 / POAM-022 / POAM-023 (single-factor shared credential; authorizer-less API; unthrottled credential endpoint),adaptive,"Replaces the end-user authentication mechanism of an existing public-facing component (HTTP Basic Auth -> Cognito with mandatory TOTP MFA + API Gateway JWT authorizer). No class change, no federal customer data, no new external interconnection, so not Transformative; an authentication-model change is not routine-recurring maintenance. Resolves to Adaptive per SCN-CSO-EVA. Backfilled record: the change shipped 2026-06-22 via the gated PR flow; this row completes the register (SCN-CSO-HIS).","Silk Reeling auth replacement: Basic Auth retired; Cognito user pool (mandatory TOTP MFA, 14-char minimum, admin-only creation) with Hosted UI (code + PKCE); JWT authorizer on ANY /api/{proxy+}; $default stays open serving the SPA shell only; stage throttling 20 rps / burst 10; API access logging to a CMK-encrypted log group.",Remediate POAM-021/022/023: retire the single-factor shared credential and gate the data API at the edge with rate limiting.,App users sign in with an invited individual account and mandatory TOTP MFA instead of a shared password. No agency customers exist.,"Gated deploy (OPA + Checkov gate) -> Cognito pool + authorizer + throttling applied via Terraform -> post-implementation verification of live authorizer/MFA/throttling/logging -> KSI signal + OSCAL SSP + POA&M re-emitted. Controls/KSIs re-verified: IA-2(x)/IA-8, AC-7, SC-5, AU-2/AU-3, KSI-IAM-*.",docs/scn/SCN-2026-002-cognito-auth.md,"Shared-credential and unthrottled-endpoint risks retired with POAM-021/023 closure. Residual: TOTP is not phishing-resistant (WebAuthn/FIDO2 upgrade path documented, POAM-025 direction); Cognito availability becomes a sign-in dependency (AWS-managed).",Sam Aydlette,System Owner / Authorizing Operator,"Implemented - live in production since 2026-06-22 (Task 3; POAM-021/022/023 closed); post-implementation verification COMPLETE 2026-07-06 via read-only AWS CLI (JWT authorizer on data routes, MFA ON, 14-char policy, admin-only creation, 20/10 throttling, access logging live)",2026-06-20,,2026-06-22,2026-07-06,no,,,,,,,, +SCN-2026-003,<FR-CERT-ID>,N/A (sole-operator self-attestation; no 3PAO engaged),AU-2/AU-11 control-plane audit gap (no durable CloudTrail trail; 90-day Event History only),adaptive,"Net-new internal service component (CloudTrail trail + delivery bucket). No new ingress/egress, no auth change, no customer impact, no class change - not Transformative; a net-new component is not routine-recurring maintenance. Conservatively Adaptive per SCN-CSO-EVA (lower edge: purely internal detective tooling).","Multi-region CloudTrail management-events trail with log-file validation, delivered to a dedicated locked-down S3 bucket; AU-11 tiering 12mo active + Deep Archive to 30mo. Deploy role can create/configure but not stop/delete the trail.",Close the control-plane audit gap: SSP AU-family statements assumed CloudTrail coverage that did not durably exist.,None (internal detective control).,"Bootstrap apply (deploy-role cloudtrail-management grant, manual) -> merge -> gated deploy creates trail + bucket -> post-implementation verification (get-trail-status IsLogging, objects delivered, audit_log_trail component in the next signal).",docs/scn/SCN-2026-003-cloudtrail.md,Strictly additive detective coverage. Residuals documented inline: SSE-S3 not CMK (POAM-029-consistent); no CloudWatch Logs integration / SNS (quarterly review per KSI-MLA-RVL).,Sam Aydlette,System Owner / Authorizing Operator,Implemented - trail live and delivering; post-implementation verification COMPLETE 2026-07-09 (gate green end-to-end; AWSLogs/<account>/ objects delivered; audit_log_trail component in the published signal with data_sensitivity internal; POAM-029/032 dispositions in the published VDR),2026-07-08,,2026-07-09,2026-07-09,no,#225,,,,,,, +SCN-2026-004,<FR-CERT-ID>,N/A (sole-operator self-attestation; no 3PAO engaged),CA-7/IR-6 monitoring gap (evidence nightly failed 2026-09-09..24 unalerted; VDR 12 days stale vs 24h policy; live drift check skipped),adaptive,"Net-new internal components (watchdog Lambda, 3 CloudWatch alarms, CMK-encrypted SNS topic) plus one new outbound flow: alarm metadata by email to the operator email, out of boundary per ROT #3 (flow I). Not Transformative: no federal data, no critical third party handling significant information, no auth/customer-responsibility/class change. Backfilled: shipping PRs #357/#359/#361 carried no SCN-Type and defaulted to routine-recurring.","Evidence SLA watchdog pages the operator by email (SNS) when published evidence goes stale or the evidence nightly fails; nightly runs twice daily, writes a status beacon, and runs its live drift check independently of the vulnerability gate.",The evidence nightly failed every night 2026-09-09..24 with only a GitHub issue as signal; the published VDR breached the 24h reporting policy and the vulnerability gate short-circuited the live reconciliation.,None (no agency customers; internal detective control).,"Bootstrap grants (deploy role, operators group; operator-applied after plan review) -> merge -> gated deploy creates watchdog/topic/alarms -> out-of-band email subscription -> post-implementation verification (forced alarm, delivery metrics).",docs/scn/SCN-2026-004-evidence-alerting.md,"Additive detective control. New outbound flow carries alarm metadata only (no evidence content or credentials); SNS email is not end-to-end encrypted, recorded as acceptable for that content. Watchdog has no internet egress; unattended-path permissions unchanged. ~$0.80/month.",Sam Aydlette,System Owner / Authorizing Operator,"Implemented 2026-09-25; post-implementation verification COMPLETE 2026-09-25 (forced alarm: 2 delivered, 0 failed; all alarms OK). Inventory/SSP/boundary documentation aligned 2026-09-27.",2026-09-25,,2026-09-25,2026-09-25,no,#357;#359;#361,,,,,,, +SCN-2026-005,<FR-CERT-ID>,N/A (sole-operator self-attestation; no 3PAO engaged),AC-6/CM-5 exposure: pull-request CI runs received the full deploy role without the prod environment approval,adaptive,"Changes the privileged-identity model of the CI/CD path (one new read-only IAM role; deploy-role trust narrowed to the reviewer-gated prod environment). Same class as SCN-2026-002's access-model change. Not Transformative: no new external service, data flow or component beyond one IAM role; no federal data; no customer-responsibility or class change.","compliance-check (terraform plan + OPA, on pull requests and main pushes) moves to a read-only plan role; the deploy role then trusts only the reviewer-gated prod environment.","The deploy role trusted pull_request and main-ref subjects because compliance-check planned with it, so every PR run held the full deploy permission set (IAM PutRolePolicy/PassRole on a Lambda role, Lambda code updates) without the prod approval gate.",None (no agency customers).,#374 plan role (operator-applied) -> AWS_PLAN_ROLE_ARN -> #375 compliance-check switch (verified by its CI run) -> this change: deploy trust narrowed to environment:prod (operator-applied after plan review) -> post-implementation verification.,docs/scn/SCN-2026-005-ci-identity-split.md,Net reduction: deploy credentials exist only inside an approved deploy. Plan role reads the Terraform state object (not new exposure: the deploy role already could from the same PRs) and cannot write except the lock item; data-plane reads denied. No cost.,Sam Aydlette,System Owner / Authorizing Operator,"Implemented and verified 2026-09-28 (#374, #375, #378 applied; the deploy, a pull-request check and a main-push check each passed).",2026-09-28,,2026-09-28,2026-09-28,no,#374;#375;#378,,,,,,, +SCN-2026-006,<FR-CERT-ID>,N/A (sole-operator self-attestation; no 3PAO engaged),"POAM-020 (Anthropic API interconnection, risk-accepted); POAM-019 (Anthropic key rotation, false positive)",adaptive,"Removes an external interconnection, a boundary-crossing data flow and a secret; changes the authorization boundary and SSP interconnections, so more than routine-recurring. Not Transformative: no new service, data flow or component; no federal data; no customer-responsibility or class change.","Silk Reeling app stops calling the Anthropic API and writes feedback from the scores; the API-key secret, its two IAM grants and env var are removed. LLM feedback becomes a customer-configurable option, disabled in this deployment.",The interconnection was a risk-accepted SA-9/CA-3 item to a service without a FedRAMP authorization and its key had expired; the app produces useful feedback without it.,None (no agency customers). App users get feedback written from their scores.,"App default-off (silk-reeling-mirror ADR-0009) -> this change (terraform plan review, gated deploy) -> post-implementation verification -> close POAM-020 and retire POAM-019.",docs/scn/SCN-2026-006-remove-anthropic-interconnection.md,"Net reduction: no app data leaves the boundary, no third-party credential stored, two IAM grants removed. No new risk.",Sam Aydlette,System Owner / Authorizing Operator,Implemented and verified 2026-10-27 (secret scheduled for deletion; IAM and key policies clear; published SSP and signal without the interconnection; verify-published PASS),2026-10-26,,2026-10-27,2026-10-27,no,#449,,,,,,, +SCN-2026-007,<FR-CERT-ID>,None: no FedRAMP Recognized assessor is engaged. A simulated assessor checks every deploy; it is not a FedRAMP assessment.,,adaptive,"Adds two IAM roles for unattended publishing (package maintenance, incident reports); read-only and staging grants on the runtime emitter; account-wide read-only IAM and S3 account-setting reads on the deploy role for the secure-configuration comparison; CloudFront access logging that records no client identifiers, read by the deploy role; read-only CORS (Access-Control-Allow-Origin *) on /.well-known/; a new trusted signing identity, the simulated assessor's workflow, for assessment results; and a DAST scanner user; and changes to the compliance engine (#518): assessments bound to the commit and published KSI signal they covered, a second assessment of the just-published state after every deploy, append-only histories that fail the deploy on any fetch failure but a 404, simulated certification reports issued only in response to a simulated submission with publication past 14 days failing the deploy, simulated AFC-CSO-NOC change notices that fail the deploy when filed more than one business day after the deploy that first published the change, and a not-certified status in the CPO and SDR; and further engine changes: the exploitation assessment rests on automated sources only (DEC-181) with a screen against records that commit the operator to manual review, the SDR, CPO and OCR histories fetched fail-closed, failure alerts on the unit tests and security scan, a complete human-readable view of every JSON each publishing workflow puts with the trust manifest listing views from the publisher table, a publication gate on email addresses outside the site's domain, the DEC-194 no-engagement statement on every simulated output, corroboration that checks each signature against the workflows that write the file; and scheduled reviews in place of recurring manual ones (DEC-195): a nightly audit-log review of CloudTrail and GitHub with a planted simulated intruder (a read-only cloudtrail:LookupEvents grant on the nightly role), a monthly recovery exercise with an annual simulated tabletop, the Annual Security Review with the rules-of-behavior acknowledgement, an overdue check that fails the run, the reviews counted as SDR methods only when signed and current, and a gate against text that commits a person to recurring manual work. Not Transformative: no new external service, no federal data, no customer-responsibility or class change.",Rule register and completeness gate: every applicable FedRAMP 20x Class C rule Implemented or Not Applicable; outside parties simulated and flagged.,"Show FedRAMP 20x adherence as evidence built from code, with the deploy refusing to publish any gap.",None (no agency customers).,"Bootstrap applies (operator) -> repository variables, environments, secrets, labels -> merge to main -> gated deploy -> post-deploy verification.",docs/scn/SCN-2026-007-fedramp-20x-rule-completeness.md,"Two unattended roles write published artifacts without a reviewer, each limited to its key prefixes and to main. Edge access logs record no client IP, forwarded-for, port, user agent, referrer, cookies or query string (field allowlist), expire after 90 days, and are read by the deploy role to build monthly counts (the operator's administrative access also reaches the bucket). The deploy role gains account-wide read-only IAM and S3 account-setting reads (metadata only, no secret values). Any origin may read /.well-known/ with GET, HEAD or OPTIONS, without credentials; the data is public. The builders accept assessment results signed by one more identity, the simulated assessor workflow, and nothing else from it. DAST user in the app pool with TOTP. Reductions: IAM user names, run IDs and personal email removed from published output, each gated (any email address outside the site's domain fails the publication gate). An assessment of another commit or signal is refused; a failed post-deploy assessment fails the run and raises the deployment-failure issue (what was published stays until the next deploy); a history fetch failure stops the deploy instead of restarting the history; the CPO and SDR state the system is not certified. The nightly role can read CloudTrail event history; the audit-log review publishes principal categories only. Reduction: the audit log is reviewed every night by machine instead of quarterly by hand, and a stopped trail, new access key or user, disabled key or removed public access block fails the nightly.",Sam Aydlette,System Owner / Authorizing Operator,on-deploy,2026-11-05,,,,no,,,,,,,, diff --git a/docs/security-review.md b/docs/security-review.md index 4d7f3f0c..0a34ee4b 100644 --- a/docs/security-review.md +++ b/docs/security-review.md @@ -1,51 +1,19 @@ # Annual Security Review -This document satisfies KSI-PIY-RIS — persistent review of the effectiveness of investments in achieving security objectives. +This document satisfies KSI-PIY-RIS (persistent review of the effectiveness of investments in achieving security objectives), and with it KSI-PIY-RES, KSI-SVC-EIS and KSI-INR-RPI. -## Scope +## How the review is held -"Investments" here means the time spent and the recurring costs paid for security controls. The review answers: are the chosen controls producing security outcomes proportionate to their cost? +Nobody holds it by hand (DEC-195 lists the only recurring human acts that remain). `scripts/hold-security-review.py` runs in `package-maintenance.yml`, which every deploy calls, at the deployed commit. On the due date (first due 2026-11-06, then each year on the same day) the script builds the review from the system's own data and publishes it, signed, as `/.well-known/security-review-<date>.json` with its readable view; the index `/.well-known/security-reviews.json` records each one's sha256. The checks: -## Review template +- **Documents:** every policy, procedure, plan and record in `data/non-machine-resources.json` passes its machine checks, with its sha256 and whether it changed since the last review. +- **Component types:** every component type added to the inventory since the last review is named in the threat model (`docs/architecture-decisions.md`). +- **Operations:** decisions made in the last 12 months, any in-force decision past its review date, the findings in the VDR, and the incident record; an incident pattern that recurs fails the review (KSI-INR-RPI). +- **Investment:** the recurring cost of every billable thing, from `data/recurring-costs.json` (each line with the repository file that creates it; the figures are AI-drafted estimates for the operator to correct), and the pipeline's run time from GitHub's run history. -``` -## YYYY: Annual security review +A simulated reviewer, Rev Yewer (simulated), signs each check off (DEC-194). A failing check fails the run and nothing is published for that date; the fix is a code or document change, and the review is held again on the next run. `scripts/check-scheduled-review.py` fails the run from the day after a due date with no review published. The same index records the acknowledgement of the [rules of behavior](rules-of-behavior.md) (PL-4). -### Recurring costs (USD/year) -- Lambda compliance executions: $X -- EventBridge rules: $X -- CloudWatch logs: $X -- Other (TLS, DNS, S3 storage): $X -- Total compliance overhead: $X - -### Time invested (hours) -- Compliance pipeline maintenance: <approx> -- Incident response: <approx, may be 0> -- Documentation review: <approx> -- Recovery tabletops: <approx> - -### Controls in place vs. controls considered -See README "Conscious Trade-offs for Budget Reality" for the live decision table. -Changes from prior year: -- <added> -- <removed> -- <re-evaluated> - -### Effectiveness signals -- Number of incidents this year: <count> -- Drift events caught by runtime KSI emitter: <count> -- OPA gate failures caught pre-deploy: <count> -- Sigstore-verified deploys: <count, should equal deploy count> -- Dependabot PRs merged / dismissed: <ratio> - -### Decisions for next year -- Controls to add: <list, justified> -- Controls to remove: <list, justified> -- Cost target: <$/year> -- Documentation updates needed: <list> -``` - -## 2026: First entry +## History: the 2026 entry (written by hand before the review was automated) ### Recurring costs (USD/year) @@ -70,7 +38,7 @@ Changes from prior year: ### Controls in place vs. considered -See README "Conscious Trade-offs for Budget Reality." Excluded controls (WAF, multi-AZ, S3 access logging) remain consciously excluded for the same reasons. New for 2026: deploy-time KSI signal signing via Sigstore keyless; runtime KSI emitter; OSCAL Rev 5 SSP generator. +See README "Conscious Trade-offs for Budget Reality." Excluded controls (WAF, multi-AZ, S3 access logging) remain consciously excluded for the same reasons. New for 2026: deploy-time KSI signal signing via Sigstore keyless; runtime KSI emitter; OSCAL Rev 5 SSP generator (since retired, replaced by the Security Decision Record). ### Effectiveness signals @@ -84,28 +52,24 @@ See README "Conscious Trade-offs for Budget Reality." Excluded controls (WAF, mu - Continue current control set - Verify runtime emitter has produced at least one drift signal event in a controlled test (deliberately misconfigure a non-production resource and confirm the daily Lambda flags it) -- Close [POAM-001](../data/decisions.json) by completing the GitHub OIDC migration; until then, hold to the 90-day key-rotation cadence below +- Close [POAM-001](../data/decisions.json) by completing the GitHub OIDC migration (done: the key was deleted and the item is now DEC-001, remediated; POAM-001 was replaced by that record) - Consider whether OSCAL artifact should be signed independently or covered by the same Sigstore bundle as the KSI signal - Cost target: maintain recurring overhead on the order of $30/year (KMS key, Secrets Manager, Route 53; serverless compute within the free tier) -## Quarterly continuous-monitoring reviews +## History: quarterly continuous-monitoring reviews -Per CR26 `CCM-QTR-MTG`, the operator records a quarterly review of the runtime KSI emitter's activity and any drift events. For a sole-operator system, the "necessary parties" reduce to the operator's self-attestation; this log is the evidence. +Kept as history; no longer kept up. The Quarterly Review (`CCM-QTR-MTG`) is now held automatically by `package-maintenance.yml` with simulated attendees (DEC-194) and published as `/.well-known/quarterly-review-<date>.json`. ### 2026-Q2 (initial review, 2026-05-08) - Runtime KSI emitter: deployed, running daily on EventBridge schedule, no drift events recorded. - Deploy-time vs. runtime signal reconciliation: components match; validations pass on both sides. - VDR posture: 1 finding (N1, deduplicate-of-CKV_AWS_50, suppressed in next push), 0 blocking, 15 risk-accepted. -- POA&M activity: POAM-001 through POAM-018 in place; first AWS access-key rotation due ~2026-08-08. +- POA&M activity (the POA&M has since been replaced by the decision register): POAM-001 through POAM-018 in place; first AWS access-key rotation due ~2026-08-08. - independent-assessment-style external assessment (self-performed) completed 2026-05-08; findings recorded in SAR-001 through SAR-009. - Decisions: proceed with SAR-002 / SAR-003 inventory expansions; close SAR-007 (ledger), SAR-008 (deduplicate tfsec finding), SAR-009 (emergency-change procedure). - Next review due: 2026-08-08 (or sooner upon Transformative change per SCN). -## AWS access key rotation log - -Rotation cadence: 90 days. Active compensating control while [POAM-001](../data/decisions.json) remains open. Procedure in the [Secure Configuration Guide](policies/secure-configuration-guide.md). Emergency rotations (suspected compromise) are logged here too with the trigger noted. +## History: AWS access key rotation log (retired) -| Rotation date | Trigger | Outcome | Notes | -| --- | --- | --- | --- | -| _Pending first rotation_ | _scheduled_ | _—_ | First rotation due 90 days from initial key issuance. | +No longer kept: CI moved to GitHub OIDC roles and the deployer access key was deleted (DEC-001, remediated), so there is no key to rotate. No rotation was ever logged. diff --git a/docs/training-log.md b/docs/training-log.md index 5ff549d9..df1cff1b 100644 --- a/docs/training-log.md +++ b/docs/training-log.md @@ -1,6 +1,10 @@ # Training Log -This document satisfies KSI-CED-RAT through KSI-CED-RAT. The system has one employee (Sam Aydlette, the author), who holds every role in the org, including all privileged-access roles, all development, and all incident response. "Persistent review of training effectiveness" is therefore conducted in the same medium in which the training itself occurs: the practitioner's head, with periodic externalization to this document. +**How KSI-CED-RAT is met.** Training is automated (`scripts/_training.py`): on every build of the Security Decision Record a training packet is generated from the system's own data (every decision of the last 12 months, every incident and exercise, the rule and KSI counts, and a fixed core covering the areas below), and a simulated trainee, Pat Placeholder (simulated), takes its quiz whenever the packet changes. Two automated methods check it: the latest completed packet covers everything the data requires, and the current packet was completed by its due date with a passing score and a steady score trend. The SDR publishes both, with the history, under `providerExtensions.training`. No person is enrolled (DEC-194). + +**This document** keeps the operator's own reading as context. It carries no obligation, no cadence and no attestation; nothing checks it, and nothing depends on it being updated. + +The system has one operator (Sam Aydlette), who holds every role, including all privileged-access roles, all development and all incident response. ## Coverage @@ -43,6 +47,6 @@ Effectiveness signal: every commit to this repo is reviewed against these source The IR lead is the author. "Training" here means having read NIST SP 800-61, having a runbook (see [`incident-response.md`](incident-response.md)), and having practiced recovery (see [`recovery-plan.md`](recovery-plan.md)). The recovery procedure has been exercised end-to-end during the construction of this implementation; that counts as a tabletop with a much-larger-than-tabletop scope. -## Review cadence +## Updates -Annually, or whenever a relevant standard updates substantively. Updates are appended to this file as a dated entry. +None required. The operator may append a dated entry when he feels like it. diff --git a/docs/verification.md b/docs/verification.md index f679260b..12555268 100644 --- a/docs/verification.md +++ b/docs/verification.md @@ -57,25 +57,39 @@ sigstore verify identity --bundle ksi-signal.bundle \ --cert-identity "$IDENTITY" --cert-oidc-issuer "$ISSUER" ksi-signal.json ``` -**Two publisher identities, and why.** Everything above is signed by the deploy -workflow. The **VDR is the exception**: `vdr-report.json`, its Sigstore bundle, -its in-toto attestation, and the `vdr-trend.json` ledger are refreshed nightly -so the published vulnerability report stays inside its 24-hour freshness policy. -The deploy workflow cannot do that — it applies Terraform and is deliberately -bound to a reviewed environment — so the refresh runs as its own workflow and -signs with its own identity: +**More than one publisher identity, and why.** Each file is signed by the +workflow that wrote it last, so a verifier accepts exactly the workflows that +write that file. The deploy workflow writes everything it builds. It cannot run +unattended (it applies Terraform and is deliberately bound to a reviewed +environment), so three unattended workflows rewrite a few files between deploys +and sign them with their own identities: + +| Files | Also written and signed by | +|---|---| +| `vdr-*` (the VDR, its attestation, trend ledger and CR26 vulnerability reports) | `evidence-nightly.yml`, twice a day, to stay inside the 24-hour freshness policy | +| `security-decision-record*`, `certification-package-overview*`, `ongoing-certification-report*` | `package-maintenance.yml`, daily, to keep the package inside its two-week window | +| `ocr-issue*`, `snapshot-*`, `quarterly-reviews*`, `quarterly-review-*`, `security-review*` (the quarterly issue index, issued reports, snapshot indexes, Quarterly Reviews, the Annual Security Review and its index) | `package-maintenance.yml` only | +| `vdr-audit-log-review*`, `vdr-recovery-exercise*` (the nightly audit-log review, the monthly recovery exercises and their index) | `evidence-nightly.yml` only | +| `incident-*` (the incident log, delivery log and reports) | `incident-reports.yml`, twice a day and whenever the incident register changes | +| `simulated-assessment.*` | `simulated-assessor.yml` only (the deploy relays it unchanged) | ``` NIGHTLY='https://github.com/sam-aydlette/samaydlette.com/.github/workflows/evidence-nightly.yml@refs/heads/main' +MAINTENANCE='https://github.com/sam-aydlette/samaydlette.com/.github/workflows/package-maintenance.yml@refs/heads/main' +INCIDENT='https://github.com/sam-aydlette/samaydlette.com/.github/workflows/incident-reports.yml@refs/heads/main' +ASSESSOR='https://github.com/sam-aydlette/samaydlette.com/.github/workflows/simulated-assessor.yml@refs/heads/main' ``` -Verifying the VDR means accepting **either** identity, which is what -`scripts/verify-published.sh` does. Both are pinned workflows in this public -repository running on `main`, so the claim being made is unchanged: the evidence -came from this repo's CI, not from someone holding a key. If you prefer one -expression, `--certificate-identity-regexp` over -`https://github.com/sam-aydlette/samaydlette.com/.github/workflows/.+` covers -both — that is the form the README uses. +Verifying one of those files means accepting **either** the deploy identity or +the one in its row, which is what `scripts/verify-published.sh` does (its +`signers_for` function). The table is `scripts/_signers.py`; a test derives each +file's writers from the workflows' publish steps and fails when the table, the +assessor guide, the trust manifest, the script or this page disagrees. All of +these are pinned workflows in this public repository running on `main`, so the +claim being made is unchanged: the evidence came from this repo's CI, not from +someone holding a key. Prefer the exact identities above to a regular +expression over every workflow in the repository, which would also accept a +file signed by a workflow that never writes it. **2. Provenance claims — dependency-free.** `scripts/verify-attestation.py` reads the in-toto predicate (no cosign, no third-party libraries) and checks it binds diff --git a/infrastructure/Makefile b/infrastructure/Makefile index 036d361f..94b49d7d 100644 --- a/infrastructure/Makefile +++ b/infrastructure/Makefile @@ -185,7 +185,7 @@ gate: @echo "✅ Inventory gate passed" # Python unit/integration tests (inventory gate, provenance, PURLs, control params, -# CMMC mapping, figure injection). Runnable in PR CI without AWS state. +# trust-center figures). Runnable in PR CI without AWS state. python-test: @echo "Running Python test suite..." cd .. && python3 -m pytest tests/ -q diff --git a/infrastructure/bootstrap/cloudfront.tf b/infrastructure/bootstrap/cloudfront.tf index da368e29..4242dfc7 100644 --- a/infrastructure/bootstrap/cloudfront.tf +++ b/infrastructure/bootstrap/cloudfront.tf @@ -241,6 +241,85 @@ resource "aws_cloudfront_response_headers_policy" "silk_reeling" { } } +# The published certification data under /.well-known/ (FRC-CSO-JSN, CDS-TRC-PAC): +# the static site's security headers, plus CORS so a browser application on +# another origin can read the JSON. Read-only (GET/HEAD/OPTIONS), any origin, no +# credentials: the data is public. CORP is cross-origin here, not same-origin, +# for the same reason. X-Content-Type-Options: nosniff is sent; the Content-Type +# is the object's own (set at upload). The deploy checks all three live and +# fails without them (scripts/check-wellknown-headers.py). +resource "aws_cloudfront_response_headers_policy" "well_known" { + name = "${local.domain_dashed}-well-known-headers" + comment = "Security headers and read-only CORS for ${var.domain_name}/.well-known/" + + cors_config { + access_control_allow_credentials = false + access_control_allow_headers { + items = ["*"] + } + access_control_allow_methods { + items = ["GET", "HEAD", "OPTIONS"] + } + access_control_allow_origins { + items = ["*"] + } + access_control_max_age_sec = 3600 + origin_override = true + } + + security_headers_config { + strict_transport_security { + access_control_max_age_sec = 31536000 + include_subdomains = true + preload = true + override = true + } + content_type_options { + override = true + } + frame_options { + frame_option = "DENY" + override = true + } + referrer_policy { + referrer_policy = "strict-origin-when-cross-origin" + override = true + } + content_security_policy { + content_security_policy = "default-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none'" + override = true + } + xss_protection { + mode_block = true + protection = true + override = true + } + } + + custom_headers_config { + items { + header = "Permissions-Policy" + value = "camera=(), microphone=(), geolocation=(), payment=(), usb=()" + override = true + } + items { + header = "Cross-Origin-Opener-Policy" + value = "same-origin" + override = true + } + items { + header = "Cross-Origin-Resource-Policy" + value = "cross-origin" + override = true + } + items { + header = "Cross-Origin-Embedder-Policy" + value = "credentialless" + override = true + } + } +} + resource "aws_cloudfront_distribution" "website" { # Scanner findings that describe this distribution's deliberate posture, each # classified here at scan-time (not silently dropped) and tracked in the POA&M @@ -306,6 +385,30 @@ resource "aws_cloudfront_distribution" "website" { } } + # Certification data: cached and forwarded like the static site, with the + # /.well-known/ headers policy (CORS) above. Read-only methods: nothing is + # written through the edge. The CORS headers come from the policy, so the + # Origin header is not forwarded and the cache is not split by it. No + # viewer-request function: every path here names a file. + ordered_cache_behavior { + path_pattern = "/.well-known/*" + target_origin_id = "S3-${var.domain_name}" + response_headers_policy_id = aws_cloudfront_response_headers_policy.well_known.id + viewer_protocol_policy = "redirect-to-https" + allowed_methods = ["HEAD", "GET", "OPTIONS"] + cached_methods = ["HEAD", "GET"] + compress = true + min_ttl = 0 + default_ttl = 3600 + max_ttl = 86400 + forwarded_values { + query_string = false + cookies { + forward = "none" + } + } + } + # App path: no caching, forward everything except Host (so the JWT authorizer # sees the Authorization header), strip the prefix at the edge, and add the # app's security headers. diff --git a/infrastructure/bootstrap/deploy-config-reads.tf b/infrastructure/bootstrap/deploy-config-reads.tf new file mode 100644 index 00000000..ba5ad48a --- /dev/null +++ b/infrastructure/bootstrap/deploy-config-reads.tf @@ -0,0 +1,79 @@ +# ============================================================================= +# Secure-configuration reads for the deploy role (SCG-ENH-CMP / SCG-ENH-EXP) +# ============================================================================= +# scripts/check-secure-config.py runs in the deploy, before the Security +# Decision Record is built, and compares the live settings of the top-level and +# privileged accounts with the Secure Configuration Guide's recommended defaults +# (data/secure-configuration.json). These are the read-only calls it makes that +# the deploy role does not already hold. Every action is a read; none returns a +# secret value or credential (list-access-keys returns key metadata only, never +# a secret key). Until this is applied, the check fails with AccessDenied and +# the deploy stops before publishing, which is the intended fail-closed path. +# Operator-applied with the rest of infrastructure/bootstrap. +# ============================================================================= + +data "aws_iam_policy_document" "deploy_config_reads" { + # checkov:skip=CKV_AWS_356:GetAccountSummary, GetAccountPasswordPolicy, ListUsers, ListVirtualMFADevices and s3:GetAccountPublicAccessBlock are account-level reads that do not support resource-level scoping; the user, group and role reads are scoped by ARN. Read-only; documented exception. + statement { + sid = "AccountLevelReads" + effect = "Allow" + actions = [ + "iam:GetAccountSummary", + "iam:GetAccountPasswordPolicy", + "iam:ListUsers", + "iam:ListVirtualMFADevices", + "s3:GetAccountPublicAccessBlock", + ] + resources = ["*"] + } + statement { + sid = "UserAndGroupReads" + effect = "Allow" + actions = [ + "iam:ListGroupsForUser", + "iam:ListAttachedUserPolicies", + "iam:ListUserPolicies", + "iam:GetUserPolicy", + "iam:GetLoginProfile", + "iam:ListMFADevices", + "iam:ListAccessKeys", + "iam:ListAttachedGroupPolicies", + "iam:ListGroupPolicies", + "iam:GetGroupPolicy", + ] + resources = [ + "arn:aws:iam::${data.aws_caller_identity.current.account_id}:user/*", + "arn:aws:iam::${data.aws_caller_identity.current.account_id}:group/*", + ] + } + statement { + sid = "CiRoleTrustReads" + effect = "Allow" + actions = ["iam:GetRole"] + resources = [ + aws_iam_role.deploy.arn, + aws_iam_role.plan.arn, + aws_iam_role.evidence_nightly.arn, + aws_iam_role.package_maintenance.arn, + aws_iam_role.incident_reports.arn, + ] + } + # The package maintainer's write scope (ci-roles.maintenance-publish-scope): + # its one publish policy, read to confirm it covers every object the workflow + # puts. And the nightly's audit-log read (ci-roles.nightly-audit-reads): its + # cloudtrail:LookupEvents policy. Until these are applied, the comparison + # fails the deploy before the SDR is built. + statement { + sid = "MaintainerScopeRead" + effect = "Allow" + actions = ["iam:GetRolePolicy"] + resources = [aws_iam_role.package_maintenance.arn, aws_iam_role.evidence_nightly.arn] + } +} + +resource "aws_iam_role_policy" "deploy_config_reads" { + # checkov:skip=CKV_AWS_356:Account-level IAM and S3 reads cannot be resource-scoped; user, group and role reads are ARN-scoped. Read-only; documented exception. + name = "secure-configuration-reads" + role = aws_iam_role.deploy.id + policy = data.aws_iam_policy_document.deploy_config_reads.json +} diff --git a/infrastructure/bootstrap/evidence-nightly.tf b/infrastructure/bootstrap/evidence-nightly.tf index dce6d862..a9a14e0b 100644 --- a/infrastructure/bootstrap/evidence-nightly.tf +++ b/infrastructure/bootstrap/evidence-nightly.tf @@ -18,7 +18,9 @@ # cannot sync the website, and it cannot write a single object outside # `.well-known/vdr-*`. Everything else it can do is read-only. # -# The scope below is the whole permission set, and it is short on purpose. If a +# The scope below is the whole permission set, and it is short on purpose. The +# one read added since (cloudtrail:LookupEvents, for the automated audit-log +# review) is a read on the unattended path and adds no write. If a # future change to the nightly workflow needs a permission that is not here, # that is a signal to re-examine whether the work belongs on the unattended path # at all — not to widen this policy. @@ -168,6 +170,33 @@ resource "aws_iam_role_policy" "evidence_nightly_reconcile_reads" { policy = data.aws_iam_policy_document.evidence_nightly_reconcile_reads.json } +# ----------------------------------------------------------------------------- +# READ: the audit-log review's CloudTrail event history +# ----------------------------------------------------------------------------- +# scripts/audit-log-review.py reads the write events of the last window with +# cloudtrail:LookupEvents (DEC-195: nobody reviews the logs by hand). Read-only; +# the action does not support resource-level scoping, so Resource is "*". It +# adds no write: the review publishes under .well-known/vdr-*, inside the +# existing PutObject scope. The deploy reads this policy and compares its +# actions with the Secure Configuration Guide (role-reads-nightly), so a deploy +# fails before the SDR is built while it is not applied. +data "aws_iam_policy_document" "evidence_nightly_audit_reads" { + # checkov:skip=CKV_AWS_356:cloudtrail:LookupEvents cannot be resource-scoped; a single read-only action. + statement { + sid = "AuditLogReviewReads" + effect = "Allow" + actions = ["cloudtrail:LookupEvents"] + resources = ["*"] + } +} + +resource "aws_iam_role_policy" "evidence_nightly_audit_reads" { + # checkov:skip=CKV_AWS_356:cloudtrail:LookupEvents cannot be resource-scoped; a single read-only action. Documented exception. + name = "evidence-nightly-audit-log-review" + role = aws_iam_role.evidence_nightly.id + policy = data.aws_iam_policy_document.evidence_nightly_audit_reads.json +} + output "evidence_nightly_role_arn" { value = aws_iam_role.evidence_nightly.arn description = "Set as the repository variable AWS_EVIDENCE_NIGHTLY_ROLE_ARN, which evidence-nightly.yml passes to configure-aws-credentials." diff --git a/infrastructure/bootstrap/incident-reports.tf b/infrastructure/bootstrap/incident-reports.tf new file mode 100644 index 00000000..27328344 --- /dev/null +++ b/infrastructure/bootstrap/incident-reports.tf @@ -0,0 +1,103 @@ +# ============================================================================= +# BOOTSTRAP: GitHub OIDC role for unattended incident reporting (IEC-CSO-AIR) +# ============================================================================= +# Operator-applied (not CI), like everything else in this stack. +# +# WHY A ROLE OF ITS OWN. FedRAMP's Class C incident report clocks are hours (an +# Initial Incident Report within one hour for N3-N5, an Ongoing report every +# six). The deploy role sits behind the `prod` reviewer and cannot keep them, +# and the evidence nightly's role is scoped to `.well-known/vdr-*` on purpose: +# widening it to carry incident reports would make the VDR refresh's grant +# about something else. `.github/workflows/incident-reports.yml` runs in its +# own GitHub Environment with no required reviewer and assumes this role. +# +# THE WHOLE PERMISSION SET: PutObject under `.well-known/incident-*` and a CDN +# invalidation. No delete (an unattended job never unpublishes evidence), no +# read of any kind (the workflow verifies its publish through the public URL), +# no Terraform state, no website sync. The bucket default-encrypts with SSE-S3, +# so no KMS grant is involved. If a future change needs more, re-examine +# whether that work belongs on the unattended path before widening this. +# ============================================================================= + +variable "incident_reports_environment" { + type = string + description = "GitHub Environment the incident reports workflow runs in. No required reviewer; the role it grants is scoped to .well-known/incident-*." + default = "incident-reports" +} + +# TRUST: this repository, two GitHub Environments, nothing else. A pull request +# cannot assume it, and neither can a workflow that does not declare one of +# them. The second is the reviewer-gated deploy environment: every deploy +# assumes this role before it builds the SDR (scripts/check-incident-role.py), +# so a deploy cannot publish records claiming a publisher whose role does not +# work. That adds no privilege: the deploy role can already write the bucket. +data "aws_iam_policy_document" "incident_reports_trust" { + statement { + effect = "Allow" + actions = ["sts:AssumeRoleWithWebIdentity"] + + principals { + type = "Federated" + identifiers = [aws_iam_openid_connect_provider.github.arn] + } + + condition { + test = "StringEquals" + variable = "token.actions.githubusercontent.com:aud" + values = ["sts.amazonaws.com"] + } + + condition { + test = "StringEquals" + variable = "token.actions.githubusercontent.com:sub" + values = [ + "repo:${var.github_repo}:environment:${var.incident_reports_environment}", + "repo:${var.github_repo}:environment:${var.deploy_environment}", + ] + } + } +} + +resource "aws_iam_role" "incident_reports" { + name = "github-actions-incident-reports-oidc" + description = "Unattended incident reporting (IEC-CSO-AIR). PutObject under .well-known/incident-* and a CDN invalidation; nothing else." + assume_role_policy = data.aws_iam_policy_document.incident_reports_trust.json + max_session_duration = 3600 + + tags = merge(local.bootstrap_tags, local.bootstrap_cls.identity_secrets_internal, { Name = "github-actions-incident-reports-oidc" }) +} + +data "aws_iam_policy_document" "incident_reports_publish" { + statement { + sid = "PublishIncidentReportsOnly" + effect = "Allow" + actions = ["s3:PutObject"] + resources = ["arn:aws:s3:::${var.domain_name}/.well-known/incident-*"] + } +} + +resource "aws_iam_role_policy" "incident_reports_publish" { + name = "incident-reports-publish" + role = aws_iam_role.incident_reports.id + policy = data.aws_iam_policy_document.incident_reports_publish.json +} + +data "aws_iam_policy_document" "incident_reports_cdn" { + statement { + sid = "InvalidateIncidentPaths" + effect = "Allow" + actions = ["cloudfront:CreateInvalidation"] + resources = [aws_cloudfront_distribution.website.arn] + } +} + +resource "aws_iam_role_policy" "incident_reports_cdn" { + name = "incident-reports-cdn" + role = aws_iam_role.incident_reports.id + policy = data.aws_iam_policy_document.incident_reports_cdn.json +} + +output "incident_reports_role_arn" { + value = aws_iam_role.incident_reports.arn + description = "Set as the repository variable AWS_INCIDENT_REPORTS_ROLE_ARN, which incident-reports.yml passes to configure-aws-credentials." +} diff --git a/infrastructure/bootstrap/package-maintenance.tf b/infrastructure/bootstrap/package-maintenance.tf new file mode 100644 index 00000000..1d196d6a --- /dev/null +++ b/infrastructure/bootstrap/package-maintenance.tf @@ -0,0 +1,137 @@ +# ============================================================================= +# BOOTSTRAP: GitHub OIDC role for unattended certification package maintenance +# ============================================================================= +# Operator-applied (not CI), like everything else in this stack. +# +# WHY A ROLE OF ITS OWN. CPO-CSX-CPM (Class C) requires the certification +# package to be up to date at least every two weeks, and SDR-CSX-KMT wants a +# metric point for every day; the quarterly Ongoing Certification Report must +# be issued and the package snapshotted on its calendar date (CCM-OCR-SOR, +# CDS-CSO-HAD). The deploy role sits behind the `prod` reviewer and cannot keep +# any of those dates, and the evidence nightly's role is scoped to +# `.well-known/vdr-*` on purpose. `.github/workflows/package-maintenance.yml` +# runs daily in its own GitHub Environment with no required reviewer, rebuilds +# the CPO, SDR and OCR at the deployed commit from the published, signature- +# verified inputs, and assumes this role to publish them. +# +# THE WHOLE PERMISSION SET: PutObject on the named package objects and the +# quarterly issue and review prefixes, and a CDN invalidation. No delete (an unattended job +# never unpublishes evidence), no read of any kind (the workflow verifies through +# the public URL), no Terraform state, no website sync, no other object. The +# bucket default-encrypts with SSE-S3, so no KMS grant is involved. If a future +# change needs more, re-examine whether that work belongs on the unattended path +# before widening this. The incident-reports role (incident-reports.tf) has the +# same shape; the two could be merged later if the operator prefers one. +# ============================================================================= + +variable "package_maintenance_environment" { + type = string + description = "GitHub Environment the package maintenance workflow runs in. No required reviewer; the role it grants writes only the certification package objects." + default = "package-maintenance" +} + +locals { + # Exactly what package-maintenance.yml publishes. tests/test_certification_cycle.py + # holds this list equal to the workflow's publish step. + package_maintenance_keys = [ + ".well-known/security-decision-record.json", + ".well-known/security-decision-record.bundle", + ".well-known/security-decision-record.md", + ".well-known/security-decision-record.view.md", + ".well-known/security-decision-record.json.intoto.jsonl", + ".well-known/certification-package-overview.json", + ".well-known/certification-package-overview.bundle", + ".well-known/certification-package-overview.md", + ".well-known/certification-package-overview.view.md", + ".well-known/ongoing-certification-report.json", + ".well-known/ongoing-certification-report.bundle", + ".well-known/ongoing-certification-report.md", + ".well-known/ongoing-certification-report.view.md", + ".well-known/quarterly-review.ics", + ".well-known/ocr-issues.json", + ".well-known/ocr-issues.view.md", + ".well-known/ocr-issues.bundle", + ".well-known/ocr-issue-*", + ".well-known/quarterly-reviews.json", + ".well-known/quarterly-reviews.view.md", + ".well-known/quarterly-reviews.bundle", + ".well-known/quarterly-review-*", + ".well-known/security-reviews.json", + ".well-known/security-reviews.view.md", + ".well-known/security-reviews.bundle", + ".well-known/security-review-*", + ".well-known/snapshot-*", + ".well-known/snapshots/*", + ] +} + +# TRUST: this repository, this GitHub Environment, nothing else. A pull request +# cannot assume it, and neither can a workflow that does not declare the +# environment. +data "aws_iam_policy_document" "package_maintenance_trust" { + statement { + effect = "Allow" + actions = ["sts:AssumeRoleWithWebIdentity"] + + principals { + type = "Federated" + identifiers = [aws_iam_openid_connect_provider.github.arn] + } + + condition { + test = "StringEquals" + variable = "token.actions.githubusercontent.com:aud" + values = ["sts.amazonaws.com"] + } + + condition { + test = "StringEquals" + variable = "token.actions.githubusercontent.com:sub" + values = ["repo:${var.github_repo}:environment:${var.package_maintenance_environment}"] + } + } +} + +resource "aws_iam_role" "package_maintenance" { + name = "github-actions-package-maintenance-oidc" + description = "Unattended certification package maintenance (CPO-CSX-CPM). PutObject on the CPO, SDR, OCR, quarterly issue and review objects, and a CDN invalidation; nothing else." + assume_role_policy = data.aws_iam_policy_document.package_maintenance_trust.json + max_session_duration = 3600 + + tags = merge(local.bootstrap_tags, local.bootstrap_cls.identity_secrets_internal, { Name = "github-actions-package-maintenance-oidc" }) +} + +data "aws_iam_policy_document" "package_maintenance_publish" { + statement { + sid = "PublishCertificationPackageOnly" + effect = "Allow" + actions = ["s3:PutObject"] + resources = [for k in local.package_maintenance_keys : "arn:aws:s3:::${var.domain_name}/${k}"] + } +} + +resource "aws_iam_role_policy" "package_maintenance_publish" { + name = "package-maintenance-publish" + role = aws_iam_role.package_maintenance.id + policy = data.aws_iam_policy_document.package_maintenance_publish.json +} + +data "aws_iam_policy_document" "package_maintenance_cdn" { + statement { + sid = "InvalidatePackagePaths" + effect = "Allow" + actions = ["cloudfront:CreateInvalidation"] + resources = [aws_cloudfront_distribution.website.arn] + } +} + +resource "aws_iam_role_policy" "package_maintenance_cdn" { + name = "package-maintenance-cdn" + role = aws_iam_role.package_maintenance.id + policy = data.aws_iam_policy_document.package_maintenance_cdn.json +} + +output "package_maintenance_role_arn" { + value = aws_iam_role.package_maintenance.arn + description = "Set as the repository variable AWS_PACKAGE_MAINTENANCE_ROLE_ARN, which package-maintenance.yml passes to configure-aws-credentials." +} diff --git a/infrastructure/bootstrap/trust-access-logs.tf b/infrastructure/bootstrap/trust-access-logs.tf new file mode 100644 index 00000000..f5f82808 --- /dev/null +++ b/infrastructure/bootstrap/trust-access-logs.tf @@ -0,0 +1,128 @@ +# ============================================================================= +# Trust-center access logging (CDS-TRC-ACL), with the operator's privacy limits +# ============================================================================= +# CloudFront standard logging (v2: CloudWatch vended-log delivery) for the +# distribution in cloudfront.tf, written to the existing access-log bucket that +# the per-deploy stack owns (../logging.tf: "<domain>-logs", SSE-S3, public +# access blocked, owner-enforced, a 90-day expiry on the CloudFront prefixes). +# +# Privacy limits (operator's condition, 2026-11-05): +# - The record carries only the fields below. No client IP, X-Forwarded-For, +# client port, cookies, query string, user agent or referrer is ever logged: +# CloudFront v2 field selection drops them at the edge, so they never reach +# storage. Country (c-country) is the finest location kept. +# - CloudFront cannot limit logging to a path, so every request is logged with +# those fields; the deploy's summarizer (scripts/build-access-summary.py) +# counts only /.well-known/ and /trust/ and discards the rest, and only +# aggregate counts are ever published. +# - Raw records expire after 90 days (../logging.tf). Monthly aggregate +# summaries are kept for 13 months in the published access summary. +# +# The deploy fails when this delivery is absent or logs a field outside the +# allowlist (scripts/check-edge-access-logging.py, step "Check edge access +# logging and build the access summary"), so the trust center never claims +# logging that is not configured. Operator-applied, like the rest of bootstrap. +# The delivery's record_fields list and ALLOWED_FIELDS in that script are the +# same list; tests/test_edge_access_logging.py holds them equal. +# ============================================================================= + +locals { + edge_access_log_name = "${local.domain_dashed}-edge-access" + # The existing access-log bucket, owned by the per-deploy stack (../logging.tf + # aws_s3_bucket.logs, already inventoried there); named, not read, here. + access_log_bucket_arn = "arn:aws:s3:::${local.domain_dashed}-logs" + edge_access_log_fields = [ + "date", + "time", + "x-edge-location", + "c-country", + "cs-method", + "cs-uri-stem", + "sc-status", + "sc-bytes", + "x-edge-result-type", + ] +} + + +resource "aws_cloudwatch_log_delivery_source" "edge_access" { + provider = aws.us_east_1 + name = local.edge_access_log_name + log_type = "ACCESS_LOGS" + resource_arn = aws_cloudfront_distribution.website.arn +} + +resource "aws_cloudwatch_log_delivery_destination" "edge_access" { + provider = aws.us_east_1 + name = local.edge_access_log_name + output_format = "json" + + delivery_destination_configuration { + destination_resource_arn = "${local.access_log_bucket_arn}/cloudfront" + } +} + +resource "aws_cloudwatch_log_delivery" "edge_access" { + provider = aws.us_east_1 + delivery_source_name = aws_cloudwatch_log_delivery_source.edge_access.name + delivery_destination_arn = aws_cloudwatch_log_delivery_destination.edge_access.arn + record_fields = local.edge_access_log_fields + + s3_delivery_configuration { + suffix_path = "{DistributionId}/{yyyy}/{MM}/{dd}/{HH}" + enable_hive_compatible_path = false + } +} + +# The deploy reads the delivery's configuration (to fail when it is absent or +# logs a forbidden field) and the CloudFront records (to build the aggregate +# summary). Read-only. Describe/Get on deliveries are account-level calls with +# no resource-level scoping for DescribeDeliveries; the Get* calls are scoped +# to this delivery's resources. The object read is limited to the two prefixes +# CloudFront delivery may write under. +data "aws_iam_policy_document" "edge_access_logs_read" { + # checkov:skip=CKV_AWS_356:logs:DescribeDeliveries is an account-level enumeration action that cannot be resource-scoped; read-only. Documented exception. + statement { + sid = "DescribeDeliveries" + actions = ["logs:DescribeDeliveries"] + resources = ["*"] + } + statement { + sid = "ReadEdgeAccessDelivery" + actions = [ + "logs:GetDelivery", + "logs:GetDeliverySource", + "logs:GetDeliveryDestination", + ] + resources = [ + aws_cloudwatch_log_delivery.edge_access.arn, + aws_cloudwatch_log_delivery_source.edge_access.arn, + aws_cloudwatch_log_delivery_destination.edge_access.arn, + ] + } + statement { + sid = "ListEdgeAccessRecords" + actions = ["s3:ListBucket"] + resources = [local.access_log_bucket_arn] + condition { + test = "StringLike" + variable = "s3:prefix" + values = ["cloudfront/*", "AWSLogs/${data.aws_caller_identity.current.account_id}/CloudFront/*"] + } + } + statement { + sid = "ReadEdgeAccessRecords" + actions = ["s3:GetObject"] + resources = [ + "${local.access_log_bucket_arn}/cloudfront/*", + "${local.access_log_bucket_arn}/AWSLogs/${data.aws_caller_identity.current.account_id}/CloudFront/*", + ] + } +} + +resource "aws_iam_role_policy" "edge_access_logs_read" { + # checkov:skip=CKV_AWS_356:logs:DescribeDeliveries cannot be resource-scoped; read-only. Documented exception. + name = "edge-access-logs-read" + role = aws_iam_role.deploy.id + policy = data.aws_iam_policy_document.edge_access_logs_read.json +} diff --git a/infrastructure/cloudtrail.tf b/infrastructure/cloudtrail.tf index 0c091b19..82bac162 100644 --- a/infrastructure/cloudtrail.tf +++ b/infrastructure/cloudtrail.tf @@ -120,8 +120,8 @@ resource "aws_s3_bucket_policy" "cloudtrail" { resource "aws_cloudtrail" "management" { # checkov:skip=CKV_AWS_35:Trail log-file SSE-KMS declined for the same POAM-029 rationale as the delivery bucket — SSE-S3 on control-plane records about this account's own infrastructure; a CMK adds key-sprawl and a decrypt dependency for every consumer without a confidentiality benefit. - # checkov:skip=CKV2_AWS_10:CloudWatch Logs integration declined — it duplicates every event into paid log-group storage to enable metric filters this single-operator system reviews quarterly instead (KSI-MLA-RVL). Log-file validation plus the TLS-only versioned bucket carry the integrity requirement. - # checkov:skip=CKV_AWS_252:SNS delivery notifications declined — no consumer exists for a per-delivery notification; the quarterly review reads the bucket directly. + # checkov:skip=CKV2_AWS_10:CloudWatch Logs integration declined — it duplicates every event into paid log-group storage to enable metric filters; this system reviews the trail automatically every night instead (scripts/audit-log-review.py, KSI-MLA-RVL). Log-file validation plus the TLS-only versioned bucket carry the integrity requirement. + # checkov:skip=CKV_AWS_252:SNS delivery notifications declined — no consumer exists for a per-delivery notification; the nightly audit-log review reads CloudTrail's event history directly (scripts/audit-log-review.py). name = "${replace(var.domain_name, ".", "-")}-management" s3_bucket_name = aws_s3_bucket.cloudtrail.id is_multi_region_trail = true diff --git a/infrastructure/keys/assessor-identity.json b/infrastructure/keys/assessor-identity.json new file mode 100644 index 00000000..831d1535 --- /dev/null +++ b/infrastructure/keys/assessor-identity.json @@ -0,0 +1,10 @@ +{ + "assessor": "Totally Real Assessment Services, LLC (simulated)", + "key_id": "sigstore-keyless:simulated-assessor.yml", + "algorithm": "SIGSTORE_KEYLESS", + "certificate_identity": "https://github.com/sam-aydlette/samaydlette.com/.github/workflows/simulated-assessor.yml@refs/heads/main", + "certificate_oidc_issuer": "https://token.actions.githubusercontent.com", + "pinned_on": "2026-11-05", + "simulated": true, + "note": "SIMULATED assessor. Its signing identity is the simulated-assessor.yml workflow in this repository (called by the deploy as a reusable workflow, so its Sigstore certificate names that workflow, not the deploy). It is not independent of the provider, not a FedRAMP Recognized independent assessment service, and has no FedRAMP assessor ID. Replacing it with a real assessor means pinning that assessor's own identity here in a reviewed change." +} diff --git a/infrastructure/lambda/describers.js b/infrastructure/lambda/describers.js new file mode 100644 index 00000000..f65013ab --- /dev/null +++ b/infrastructure/lambda/describers.js @@ -0,0 +1,483 @@ +'use strict'; + +// ============================================================================= +// LIVE-CONFIG READERS FOR EVERY MACHINE COMPONENT TYPE +// ============================================================================= +// One reader per inventory component type. Each reads the live configuration +// through `ctx.aws` (an adapter of plain async functions; index.js builds it +// from the AWS SDK, the tests from fixtures) and returns the policy inputs to +// evaluate, in the shape the Rego gate reads: a Terraform resource type and +// the live facts under the same Terraform attribute names (`values`), plus +// tags. The same compiled policy then judges the live account exactly as the +// deploy gate judged the plan. +// +// A failed read is never evidence that a setting is off. Every attribute that +// could not be read is listed in `read_errors`; the gate reports it as +// resource_read_error (category input), which the divergence block counts as +// unassessed and reconciliation invariant (n) refuses to count as validated. +// +// Only SDK error NAMES are kept (never messages), because the signal is public. +// +// Kept free of AWS-SDK imports, like canonical.js and divergence.js, so the +// tests run it under plain node. +// ============================================================================= + +const { withAccount } = require('./account'); + +// Terraform types the tagging rules require tags on (policy config +// taggable_types). A reader for one of these must supply tags or declare them +// unread; tags come from one Resource Groups Tagging API sweep (ctx.tags) or, +// for IAM roles, from GetRole. +function needsTags(ctx, tfType) { + return (ctx.taggableTypes || []).includes(tfType); +} + +function errName(err) { + return (err && err.name) || 'UnknownError'; +} + +// Resolve a published, account-redacted ARN to a callable one. +function arnOf(ctx, component) { + return withAccount(component.native_id || '', ctx.account); +} + +function regionOf(ctx, component) { + const parts = String(component.native_id || '').split(':'); + return (parts[0] === 'arn' && parts[3]) || component.attributes?.region || ctx.region; +} + +function attrId(component) { + return component.attributes?.id; +} + +function attachTags(ctx, resource, arn, tags) { + if (!needsTags(ctx, resource.type)) return resource; + const found = tags || (ctx.tags && ctx.tags.get(arn)); + if (found) { + resource.tags = found; + resource.tags_all = found; + } else { + resource.read_errors = [...(resource.read_errors || []), 'tags']; + } + return resource; +} + +function resource(type, component, values, readErrors) { + const r = { + type, + name: component.attributes?.tf_name || component.component_id, + values, + }; + if (readErrors.length > 0) r.read_errors = readErrors; + return r; +} + +async function read(errors, attr, fn) { + try { + return await fn(); + } catch (err) { + errors.push(attr); + return undefined; + } +} + +function decodeDocument(doc) { + // IAM returns policy documents URL-encoded. + if (typeof doc !== 'string') return doc; + try { + return decodeURIComponent(doc); + } catch (err) { + return doc; + } +} + +// --- IAM -------------------------------------------------------------------- + +async function iamRole(ctx, c) { + const errors = []; + const name = attrId(c); + const role = await read(errors, 'assume_role_policy', () => ctx.aws.iam.getRole(name)); + const attached = await read(errors, 'attached_policy_arns', () => ctx.aws.iam.listAttachedRolePolicies(name)); + const values = { name }; + if (role) values.assume_role_policy = decodeDocument(role.AssumeRolePolicyDocument); + if (attached) values.attached_policy_arns = attached; + const r = resource('aws_iam_role', c, values, errors); + if (!role) { + // Tags come from the same GetRole call; nothing to attach. + r.read_errors = [...(r.read_errors || []), 'tags']; + return [r]; + } + const tags = {}; + for (const t of role.Tags || []) tags[t.Key] = t.Value; + return [attachTags(ctx, r, null, tags)]; +} + +// The name an attached policy's ARN ends in (arn:...:policy[/path]/<name>). +function policyName(arn) { + return String(arn || '').split('/').pop(); +} + +// Managed-policy attachments: the inventory records each attachment's policies +// by name only (their ARNs carry the account ID). The holder's live attached +// policies are listed and compared by name; every recorded policy must still +// be attached, or the attachment is reported unread (it cannot be validated), +// never passed. The live ARNs of the recorded policies are the input, under +// the same runtime attribute the role and group readers use. +async function iamAttachment(ctx, c, tfType) { + const errors = []; + const attrs = c.attributes || {}; + const group = tfType === 'aws_iam_group_policy_attachment'; + const holder = group ? attrs.attached_to_group : attrs.attached_to_role; + const expected = (attrs.attached_policies || []).map((p) => p.policy_name).filter(Boolean); + const values = {}; + if (!holder || expected.length === 0) { + errors.push('attached_policies'); + return [resource(tfType, c, values, errors)]; + } + const live = await read(errors, 'attached_policies', () => (group + ? ctx.aws.iam.listAttachedGroupPolicies(holder) + : ctx.aws.iam.listAttachedRolePolicies(holder))); + if (live) { + const byName = new Map(live.map((arn) => [policyName(arn), arn])); + if (expected.every((n) => byName.has(n))) { + values.attached_policy_arns = expected.map((n) => byName.get(n)); + } else { + errors.push('attached_policies'); + } + } + return [resource(tfType, c, values, errors)]; +} + +async function iamPolicy(ctx, c) { + const errors = []; + const tfType = c.attributes?.tf_type || 'aws_iam_role_policy'; + if (tfType === 'aws_iam_role_policy_attachment' || tfType === 'aws_iam_group_policy_attachment') { + return iamAttachment(ctx, c, tfType); + } + let doc; + if (tfType === 'aws_iam_policy') { + // No managed-policy component is inventoried today, so the role holds + // no iam:GetPolicyVersion grant; one that appears is reported unread + // (and fails invariant n) until the grant and a reader are added. + errors.push('policy'); + } else { + // Inline policies: the Terraform id is "<role or group>:<policy name>". + const id = String(attrId(c) || ''); + const at = id.indexOf(':'); + const [holder, policyName_] = at < 0 ? [id, ''] : [id.slice(0, at), id.slice(at + 1)]; + const get = tfType === 'aws_iam_group_policy' + ? () => ctx.aws.iam.getGroupPolicy(holder, policyName_) + : () => ctx.aws.iam.getRolePolicy(holder, policyName_); + doc = await read(errors, 'policy', get); + } + const values = {}; + if (doc !== undefined) values.policy = decodeDocument(doc); + return [resource(tfType, c, values, errors)]; +} + +async function iamGroup(ctx, c) { + const errors = []; + const name = attrId(c); + const attached = await read(errors, 'attached_policy_arns', () => ctx.aws.iam.listAttachedGroupPolicies(name)); + const inline = await read(errors, 'inline_policies', async () => { + const names = await ctx.aws.iam.listGroupPolicies(name); + const docs = []; + for (const n of names) docs.push(decodeDocument(await ctx.aws.iam.getGroupPolicy(name, n))); + return docs; + }); + const values = { name }; + if (attached) values.attached_policy_arns = attached; + if (inline) values.inline_policies = inline; + return [resource('aws_iam_group', c, values, errors)]; +} + +async function oidcProvider(ctx, c) { + const errors = []; + const p = await read(errors, 'client_id_list', () => ctx.aws.iam.getOpenIDConnectProvider(arnOf(ctx, c))); + const values = {}; + if (p) { + values.client_id_list = p.ClientIDList || []; + values.url = p.Url; + } + return [resource('aws_iam_openid_connect_provider', c, values, errors)]; +} + +// --- compute ------------------------------------------------------------------ + +// The function's own configuration, plus a second unit for its deployed code +// package: live CodeSha256 against the hash the deploy inventoried. That unit +// names the packages the deployment package holds (attributes.deployed_in), so +// the integrity check is evidence about them too. +async function lambdaFunction(ctx, c) { + const errors = []; + const name = c.attributes?.function_name || attrId(c); + const cfg = await read(errors, 'kms_key_arn', () => ctx.aws.lambda.getFunctionConfiguration(name)); + const values = { function_name: name }; + if (cfg) { + values.kms_key_arn = cfg.KMSKeyArn || ''; + values.runtime = cfg.Runtime; + } + try { + const url = await ctx.aws.lambda.getFunctionUrlConfig(name); + if (url) values.function_url_auth_type = url.AuthType; + } catch (err) { + // No URL configured is the expected answer; anything else is unread. + if (errName(err) !== 'ResourceNotFoundException') errors.push('function_url'); + } + const fn = attachTags(ctx, resource('aws_lambda_function', c, values, errors), arnOf(ctx, c)); + + const pkgErrors = cfg ? [] : ['code_sha256']; + const pkgValues = {}; + if (cfg) pkgValues.code_sha256 = cfg.CodeSha256 || ''; + if (c.attributes?.code_sha256) pkgValues.expected_code_sha256 = c.attributes.code_sha256; + const pkg = resource('lambda_deployment_package', c, pkgValues, pkgErrors); + const packageRefs = (ctx.components || []) + .filter((p) => p.attributes?.deployed_in === c.component_id) + .map((p) => p.component_id) + .sort(); + return [ + { inputs: [fn], refs: [c.component_id] }, + { inputs: [pkg], refs: [c.component_id, ...packageRefs], policy: 'package-integrity' }, + ]; +} + +// --- logging, monitoring, scheduling ------------------------------------------ + +async function logGroup(ctx, c) { + const errors = []; + const name = attrId(c); + const lg = await read(errors, 'kms_key_id', () => ctx.aws.logs.describeLogGroup(name, regionOf(ctx, c))); + const values = { name }; + if (lg) { + values.retention_in_days = lg.retentionInDays || 0; + values.kms_key_id = lg.kmsKeyId || ''; + } else if (!errors.includes('kms_key_id')) { + errors.push('kms_key_id'); + } + return [attachTags(ctx, resource('aws_cloudwatch_log_group', c, values, errors), arnOf(ctx, c).replace(/:\*$/, ''))]; +} + +async function auditTrail(ctx, c) { + const errors = []; + const arn = arnOf(ctx, c); + const trail = await read(errors, 'trail', () => ctx.aws.cloudtrail.getTrail(arn, regionOf(ctx, c))); + const status = trail ? await read(errors, 'trail', () => ctx.aws.cloudtrail.getTrailStatus(arn, regionOf(ctx, c))) : undefined; + const values = {}; + if (trail && status) { + values.enable_logging = status.IsLogging === true; + values.is_multi_region_trail = trail.IsMultiRegionTrail === true; + values.enable_log_file_validation = trail.LogFileValidationEnabled === true; + } + return [resource('aws_cloudtrail', c, values, [...new Set(errors)])]; +} + +async function metricAlarm(ctx, c) { + const errors = []; + const a = await read(errors, 'alarm_actions', () => ctx.aws.cloudwatch.describeAlarm(attrId(c), regionOf(ctx, c))); + const values = {}; + if (a) { + values.actions_enabled = a.ActionsEnabled === true; + values.alarm_actions = a.AlarmActions || []; + } else if (!errors.length) { + errors.push('alarm_actions'); + } + return [attachTags(ctx, resource('aws_cloudwatch_metric_alarm', c, values, errors), arnOf(ctx, c))]; +} + +async function eventSchedule(ctx, c) { + const errors = []; + const rule = await read(errors, 'state', () => ctx.aws.events.describeRule(attrId(c), regionOf(ctx, c))); + const values = {}; + if (rule) values.state = rule.State; + return [attachTags(ctx, resource('aws_cloudwatch_event_rule', c, values, errors), arnOf(ctx, c))]; +} + +async function notificationTopic(ctx, c) { + const errors = []; + const arn = arnOf(ctx, c); + const attrs = await read(errors, 'kms_master_key_id', () => ctx.aws.sns.getTopicAttributes(arn, regionOf(ctx, c))); + const values = {}; + if (attrs) values.kms_master_key_id = attrs.KmsMasterKeyId || ''; + return [attachTags(ctx, resource('aws_sns_topic', c, values, errors), arn)]; +} + +async function messageQueue(ctx, c) { + const errors = []; + // The inventory's queue URL carries ACCOUNT in place of the account ID. + const url = String(attrId(c) || '').replace('/ACCOUNT/', `/${ctx.account}/`); + const attrs = await read(errors, 'encryption', () => ctx.aws.sqs.getQueueAttributes(url, regionOf(ctx, c))); + const values = {}; + if (attrs) { + values.sqs_managed_sse_enabled = attrs.SqsManagedSseEnabled === 'true'; + values.kms_master_key_id = attrs.KmsMasterKeyId || ''; + } + return [attachTags(ctx, resource('aws_sqs_queue', c, values, errors), arnOf(ctx, c))]; +} + +async function kvTable(ctx, c) { + const errors = []; + const pitr = await read(errors, 'point_in_time_recovery', () => ctx.aws.dynamodb.describeContinuousBackups(attrId(c), regionOf(ctx, c))); + const values = {}; + if (pitr !== undefined) values.point_in_time_recovery = [{ enabled: pitr === 'ENABLED' }]; + return [resource('aws_dynamodb_table', c, values, errors)]; +} + +// --- identity, keys, edge ------------------------------------------------------- + +async function identityProvider(ctx, c) { + const errors = []; + const pool = await read(errors, 'mfa_configuration', () => ctx.aws.cognito.describeUserPool(attrId(c), regionOf(ctx, c))); + const values = {}; + if (pool) { + values.mfa_configuration = pool.MfaConfiguration; + values.password_policy = [{ minimum_length: pool.Policies?.PasswordPolicy?.MinimumLength ?? 0 }]; + values.admin_create_user_config = [{ + allow_admin_create_user_only: pool.AdminCreateUserConfig?.AllowAdminCreateUserOnly === true, + }]; + } else { + errors.push('password_policy', 'admin_create_user_config'); + } + return [attachTags(ctx, resource('aws_cognito_user_pool', c, values, errors), arnOf(ctx, c))]; +} + +async function kmsKey(ctx, c) { + const errors = []; + const arn = arnOf(ctx, c); + const region = regionOf(ctx, c); + const meta = await read(errors, 'enable_key_rotation', () => ctx.aws.kms.describeKey(arn, region)); + const values = {}; + if (meta) { + values.customer_master_key_spec = meta.KeySpec || meta.CustomerMasterKeySpec; + values.is_enabled = meta.KeyState === 'Enabled'; + if (values.customer_master_key_spec === 'SYMMETRIC_DEFAULT') { + const rotating = await read(errors, 'enable_key_rotation', () => ctx.aws.kms.getKeyRotationStatus(arn, region)); + if (rotating !== undefined) values.enable_key_rotation = rotating === true; + } + } + return [attachTags(ctx, resource('aws_kms_key', c, values, [...new Set(errors)]), arn)]; +} + +async function apiGateway(ctx, c) { + const apiId = attrId(c); + const region = regionOf(ctx, c); + const arn = arnOf(ctx, c); + const inputs = [attachTags(ctx, resource('aws_apigatewayv2_api', c, { id: apiId }, []), arn)]; + const errors = []; + const stages = await read(errors, 'stages', () => ctx.aws.apigw.getStages(apiId, region)); + const routes = await read(errors, 'routes', () => ctx.aws.apigw.getRoutes(apiId, region)); + if (errors.length) { + // Reported as unread on the API itself, so no stage or route rule + // judges configuration that was never observed. + const unread = resource('aws_apigatewayv2_api', c, { id: apiId }, errors); + unread.name = `${unread.name}/config`; + inputs.push(attachTags(ctx, unread, arn)); + } + for (const s of stages || []) { + const values = { + name: s.StageName, + access_log_settings: s.AccessLogSettings?.DestinationArn + ? [{ destination_arn: s.AccessLogSettings.DestinationArn }] : [], + default_route_settings: [{ + throttling_rate_limit: s.DefaultRouteSettings?.ThrottlingRateLimit ?? 0, + throttling_burst_limit: s.DefaultRouteSettings?.ThrottlingBurstLimit ?? 0, + }], + }; + const stage = resource('aws_apigatewayv2_stage', c, values, []); + stage.name = `${stage.name}/${s.StageName}`; + inputs.push(attachTags(ctx, stage, `${arn}/stages/${s.StageName}`)); + } + for (const rt of routes || []) { + const route = resource('aws_apigatewayv2_route', c, { + route_key: rt.RouteKey, + authorization_type: rt.AuthorizationType || 'NONE', + }, []); + route.name = `${route.name}/${rt.RouteKey}`; + inputs.push(route); + } + return [{ inputs, refs: [c.component_id] }]; +} + +async function dnsZone(ctx, c) { + const errors = []; + const status = await read(errors, 'dnssec_status', () => ctx.aws.route53.getDnssecStatus(attrId(c))); + const values = {}; + if (status !== undefined) values.dnssec_status = status; + return [resource('aws_route53_zone', c, values, errors)]; +} + +async function tlsCertificate(ctx, c) { + const errors = []; + const cert = await read(errors, 'status', () => ctx.aws.acm.describeCertificate(arnOf(ctx, c), regionOf(ctx, c))); + const values = {}; + if (cert) { + values.status = cert.Status; + // Whole days of validity left. Derived here, not in Rego: the Wasm + // host implements no time builtins (time.parse_rfc3339_ns throws). + const notAfter = cert.NotAfter ? new Date(cert.NotAfter).getTime() : NaN; + if (!Number.isNaN(notAfter)) values.days_to_expiry = Math.floor((notAfter - (ctx.now ? ctx.now() : Date.now())) / 86400000); + else errors.push('days_to_expiry'); + } + return [resource('aws_acm_certificate', c, values, errors)]; +} + +// Component type -> reader. object_store, cdn_distribution and secrets_manager +// keep their original readers in index.js. +const READERS = { + iam_role: iamRole, + iam_policy: iamPolicy, + iam_group: iamGroup, + oidc_provider: oidcProvider, + function: lambdaFunction, + log_group: logGroup, + audit_log_trail: auditTrail, + metric_alarm: metricAlarm, + event_schedule: eventSchedule, + notification_topic: notificationTopic, + message_queue: messageQueue, + kv_table: kvTable, + identity_provider: identityProvider, + kms_key: kmsKey, + api_gateway: apiGateway, + dns_zone: dnsZone, + tls_certificate: tlsCertificate, +}; + +// A reader returns either policy inputs (one validation for the component) or +// units ({inputs, refs, policy?}). Normalize to units. +async function describe(ctx, component) { + const reader = READERS[component.type]; + if (!reader) return null; + const out = await reader(ctx, component); + if (out.length > 0 && out[0].inputs) return out; + return [{ inputs: out, refs: [component.component_id] }]; +} + +// Evaluate every unit and fold each into one validation: fail when any of its +// inputs is non-compliant, carrying every violation. `evaluate` is the +// compiled policy (index.js) or a stub (tests). +async function validateComponents(ctx, components, evaluate, policyId, policyVersion, nextId) { + const validations = []; + for (const component of components) { + const units = await describe(ctx, component); + if (!units) continue; + for (const unit of units) { + let compliant = true; + const violations = []; + for (const input of unit.inputs) { + const result = await evaluate(input); + if (!result.compliant) compliant = false; + violations.push(...result.violations); + } + validations.push({ + validation_id: nextId(), + policy: { id: policyId, version: policyVersion }, + result: compliant && violations.length === 0 ? 'pass' : 'fail', + component_refs: unit.refs, + violations, + }); + } + } + return validations; +} + +module.exports = { READERS, describe, validateComponents, decodeDocument }; diff --git a/infrastructure/lambda/history.js b/infrastructure/lambda/history.js new file mode 100644 index 00000000..8a984873 --- /dev/null +++ b/infrastructure/lambda/history.js @@ -0,0 +1,98 @@ +'use strict'; + +// ============================================================================= +// RUNTIME RUN HISTORY (VER-RPT-PER) +// ============================================================================= +// The runtime signal is overwritten on every run, so a period report built +// later could not see a run that was replaced before it. Each signal therefore +// carries a bounded history of run summaries (signal_id, emitted_at, how many +// validations ran, how many failed or were unassessed, the divergence status), +// inside the signed payload, so a reader that verifies today's signal can list +// every run in its period. +// +// The history is carried forward only from a previous signal whose signature +// verifies against this emitter's own key. Anything else (no previous signal, +// unreadable JSON, a bad or missing signature) restarts the history, and the +// first entry says why, so a gap is visible rather than silently papered over +// and nobody can launder a fabricated history through the signing key. +// +// Kept free of AWS-SDK imports so the tests run it under plain node. +// ============================================================================= + +const crypto = require('crypto'); +const { canonicalize } = require('./canonical'); + +// Daily published runs: comfortably more than a year. A deploy's staged run is +// written to its staging key and never becomes the published signal's history. +const RUN_HISTORY_LIMIT = 400; + +function isInputViolation(v) { + return v && v.category === 'input'; +} + +function runSummary(signal) { + const validations = signal.validations || []; + return { + signal_id: signal.signal_id, + emitted_at: signal.emitted_at, + validations: validations.length, + failed: validations.filter((v) => v.result === 'fail').length, + unassessed: validations.filter((v) => (v.violations || []).some(isInputViolation)).length, + divergence: (signal.divergence && signal.divergence.status) || 'unknown', + }; +} + +// Verify a previously published runtime signal with the signer's recipe: +// canonical JSON with provenance.attestation removed, ECDSA P-256 / SHA-256, +// DER signature (what KMS returns). +function verifySignal(signal, publicKeyPem) { + try { + const sig = signal?.provenance?.attestation?.signature; + if (!sig || !publicKeyPem) return false; + const body = JSON.parse(JSON.stringify(signal)); + delete body.provenance.attestation; + return crypto.verify( + 'sha256', + Buffer.from(canonicalize(body), 'utf8'), + { key: publicKeyPem, dsaEncoding: 'der' }, + Buffer.from(sig, 'base64'), + ); + } catch (err) { + return false; + } +} + +function wellFormed(entry) { + return entry && typeof entry.signal_id === 'string' && typeof entry.emitted_at === 'string' + && Number.isInteger(entry.validations) && Number.isInteger(entry.failed) + && typeof entry.divergence === 'string'; +} + +// The history to publish with `current`. `previous` is the parsed previous +// signal (or null) and `previousVerified` whether its signature verified. +function nextRunHistory(previous, previousVerified, current, limit = RUN_HISTORY_LIMIT) { + let carried = []; + let reset = null; + if (!previous) { + reset = 'no previous runtime signal'; + } else if (!previousVerified) { + reset = 'previous runtime signal did not verify'; + } else if (Array.isArray(previous.run_history)) { + carried = previous.run_history.filter(wellFormed); + } else { + // The last signal before history existed: keep its own run. + carried = [runSummary(previous)]; + } + const seen = new Set(); + const entries = []; + for (const e of [...carried, runSummary(current)]) { + if (seen.has(e.signal_id)) continue; + seen.add(e.signal_id); + entries.push(e); + } + if (reset) entries[entries.length - 1].history_reset = reset; + entries.sort((a, b) => a.emitted_at.localeCompare(b.emitted_at)); + return entries.slice(-limit); +} + +module.exports = { RUN_HISTORY_LIMIT, runSummary, verifySignal, nextRunHistory }; diff --git a/infrastructure/lambda/index.js b/infrastructure/lambda/index.js index 19543730..5bb77d9b 100644 --- a/infrastructure/lambda/index.js +++ b/infrastructure/lambda/index.js @@ -46,9 +46,29 @@ const { SecretsManagerClient, DescribeSecretCommand, } = require('@aws-sdk/client-secrets-manager'); +const { IAMClient, GetRoleCommand, ListAttachedRolePoliciesCommand, GetRolePolicyCommand, + ListGroupPoliciesCommand, GetGroupPolicyCommand, ListAttachedGroupPoliciesCommand, + GetOpenIDConnectProviderCommand } = require('@aws-sdk/client-iam'); +const { LambdaClient, GetFunctionConfigurationCommand, GetFunctionUrlConfigCommand } = require('@aws-sdk/client-lambda'); +const { CloudWatchLogsClient, DescribeLogGroupsCommand } = require('@aws-sdk/client-cloudwatch-logs'); +const { ApiGatewayV2Client, GetStagesCommand, GetRoutesCommand } = require('@aws-sdk/client-apigatewayv2'); +const { CognitoIdentityProviderClient, DescribeUserPoolCommand } = require('@aws-sdk/client-cognito-identity-provider'); +const { DescribeKeyCommand, GetKeyRotationStatusCommand } = require('@aws-sdk/client-kms'); +const { SNSClient, GetTopicAttributesCommand } = require('@aws-sdk/client-sns'); +const { SQSClient, GetQueueAttributesCommand } = require('@aws-sdk/client-sqs'); +const { CloudWatchClient, DescribeAlarmsCommand } = require('@aws-sdk/client-cloudwatch'); +const { EventBridgeClient, DescribeRuleCommand } = require('@aws-sdk/client-eventbridge'); +const { CloudTrailClient, GetTrailCommand, GetTrailStatusCommand } = require('@aws-sdk/client-cloudtrail'); +const { DynamoDBClient, DescribeContinuousBackupsCommand } = require('@aws-sdk/client-dynamodb'); +const { Route53Client, GetDNSSECCommand } = require('@aws-sdk/client-route-53'); +const { ACMClient, DescribeCertificateCommand } = require('@aws-sdk/client-acm'); +const { ResourceGroupsTaggingAPIClient, GetResourcesCommand } = require('@aws-sdk/client-resource-groups-tagging-api'); const { canonicalize } = require('./canonical'); const { computeDivergence } = require('./divergence'); const { accountOf, withAccount } = require('./account'); +const { validateComponents } = require('./describers'); +const { nextRunHistory, verifySignal } = require('./history'); +const { stageKeys } = require('./stage'); const SIGNAL_VERSION = '1.0.0'; const SCHEMA_URL = 'https://samaydlette.com/.well-known/ksi-signal.schema.json'; @@ -69,9 +89,16 @@ const SECRET_ROTATION_MAX_AGE_DAYS = 395; // invocations within the container's lifetime. let cachedPolicy = null; let cachedPolicyVersion = null; +let cachedPolicyData = null; async function getPolicy() { - if (cachedPolicy) return { policy: cachedPolicy, version: cachedPolicyVersion }; + if (cachedPolicy) { + // A warm container reuses the module but must not reuse the clock: + // exception expiry reads evaluated_at. + cachedPolicyData.runtime = { evaluated_at: new Date().toISOString() }; + cachedPolicy.setData(cachedPolicyData); + return { policy: cachedPolicy, version: cachedPolicyVersion, data: cachedPolicyData }; + } const wasmPath = path.join(__dirname, 'policy.wasm'); const wasmBytes = fs.readFileSync(wasmPath); cachedPolicy = await loadPolicy(wasmBytes); @@ -87,10 +114,11 @@ async function getPolicy() { // timestamp no exception is active — fail-safe, never fail-open. policyData.runtime = { evaluated_at: new Date().toISOString() }; cachedPolicy.setData(policyData); + cachedPolicyData = policyData; // Use a stable hash of the wasm + data bytes as the policy version. Two // Lambda containers running the same policy produce the same version. cachedPolicyVersion = crypto.createHash('sha256').update(wasmBytes).update(dataBytes).digest('hex').slice(0, 12); - return { policy: cachedPolicy, version: cachedPolicyVersion }; + return { policy: cachedPolicy, version: cachedPolicyVersion, data: cachedPolicyData }; } // ============================================================================= @@ -218,6 +246,152 @@ async function buildCloudFrontResourceInput(cf, distributionId, tfName) { }; } +// ============================================================================= +// AWS ADAPTER FOR THE COMPONENT READERS (describers.js) +// ============================================================================= +// Read-only Get/Describe/List calls, one client per service and region. The +// readers see plain async functions, so they are tested without the SDK. +// Every call here is matched by a grant in aws_iam_role_policy.lambda_opa +// scoped to this system's resources (tests/test_runtime_grants.py). +// ============================================================================= + +function makeAws(defaultRegion) { + const clients = new Map(); + const client = (Ctor, region) => { + const key = `${Ctor.name}:${region || defaultRegion}`; + if (!clients.has(key)) clients.set(key, new Ctor({ region: region || defaultRegion })); + return clients.get(key); + }; + // IAM and Route 53 are global; their endpoints are served from us-east-1. + const iam = () => client(IAMClient, 'us-east-1'); + return { + iam: { + getRole: async (name) => (await iam().send(new GetRoleCommand({ RoleName: name }))).Role, + listAttachedRolePolicies: async (name) => + ((await iam().send(new ListAttachedRolePoliciesCommand({ RoleName: name }))).AttachedPolicies || []) + .map((a) => a.PolicyArn), + getRolePolicy: async (role, name) => + (await iam().send(new GetRolePolicyCommand({ RoleName: role, PolicyName: name }))).PolicyDocument, + listGroupPolicies: async (name) => + (await iam().send(new ListGroupPoliciesCommand({ GroupName: name }))).PolicyNames || [], + getGroupPolicy: async (group, name) => + (await iam().send(new GetGroupPolicyCommand({ GroupName: group, PolicyName: name }))).PolicyDocument, + listAttachedGroupPolicies: async (name) => + ((await iam().send(new ListAttachedGroupPoliciesCommand({ GroupName: name }))).AttachedPolicies || []) + .map((a) => a.PolicyArn), + getOpenIDConnectProvider: async (arn) => + iam().send(new GetOpenIDConnectProviderCommand({ OpenIDConnectProviderArn: arn })), + }, + lambda: { + getFunctionConfiguration: async (name) => + client(LambdaClient).send(new GetFunctionConfigurationCommand({ FunctionName: name })), + getFunctionUrlConfig: async (name) => + client(LambdaClient).send(new GetFunctionUrlConfigCommand({ FunctionName: name })), + }, + logs: { + describeLogGroup: async (name, region) => { + const out = await client(CloudWatchLogsClient, region) + .send(new DescribeLogGroupsCommand({ logGroupNamePrefix: name })); + return (out.logGroups || []).find((g) => g.logGroupName === name); + }, + }, + apigw: { + getStages: async (apiId, region) => + (await client(ApiGatewayV2Client, region).send(new GetStagesCommand({ ApiId: apiId }))).Items || [], + getRoutes: async (apiId, region) => + (await client(ApiGatewayV2Client, region).send(new GetRoutesCommand({ ApiId: apiId }))).Items || [], + }, + cognito: { + describeUserPool: async (id, region) => + (await client(CognitoIdentityProviderClient, region).send(new DescribeUserPoolCommand({ UserPoolId: id }))) + .UserPool, + }, + kms: { + describeKey: async (arn, region) => + (await client(KMSClient, region).send(new DescribeKeyCommand({ KeyId: arn }))).KeyMetadata, + getKeyRotationStatus: async (arn, region) => + (await client(KMSClient, region).send(new GetKeyRotationStatusCommand({ KeyId: arn }))).KeyRotationEnabled, + }, + sns: { + getTopicAttributes: async (arn, region) => + (await client(SNSClient, region).send(new GetTopicAttributesCommand({ TopicArn: arn }))).Attributes || {}, + }, + sqs: { + getQueueAttributes: async (url, region) => + (await client(SQSClient, region).send(new GetQueueAttributesCommand({ + QueueUrl: url, AttributeNames: ['SqsManagedSseEnabled', 'KmsMasterKeyId'], + }))).Attributes || {}, + }, + cloudwatch: { + describeAlarm: async (name, region) => + ((await client(CloudWatchClient, region).send(new DescribeAlarmsCommand({ AlarmNames: [name] }))) + .MetricAlarms || [])[0], + }, + events: { + describeRule: async (name, region) => + client(EventBridgeClient, region).send(new DescribeRuleCommand({ Name: name })), + }, + cloudtrail: { + getTrail: async (arn, region) => + (await client(CloudTrailClient, region).send(new GetTrailCommand({ Name: arn }))).Trail, + getTrailStatus: async (arn, region) => + client(CloudTrailClient, region).send(new GetTrailStatusCommand({ Name: arn })), + }, + dynamodb: { + describeContinuousBackups: async (table, region) => + (await client(DynamoDBClient, region).send(new DescribeContinuousBackupsCommand({ TableName: table }))) + .ContinuousBackupsDescription?.PointInTimeRecoveryDescription?.PointInTimeRecoveryStatus, + }, + route53: { + getDnssecStatus: async (zoneId) => + (await client(Route53Client, 'us-east-1').send(new GetDNSSECCommand({ HostedZoneId: zoneId }))) + .Status?.ServeSignature, + }, + acm: { + describeCertificate: async (arn, region) => + (await client(ACMClient, region).send(new DescribeCertificateCommand({ CertificateArn: arn }))).Certificate, + }, + tagging: { + // Every tagged resource in a region, ARN -> {key: value}. Paginated. + sweep: async (region) => { + // Bounded: a pagination token that never ends must not spin + // until the Lambda timeout. Throwing leaves the region's tags + // unread, which the readers report as unassessed (fail closed). + const tags = new Map(); + let token; + let pages = 0; + do { + if (++pages > 200) throw Object.assign(new Error('tag sweep exceeded 200 pages'), { name: 'TagSweepUnbounded' }); + const out = await client(ResourceGroupsTaggingAPIClient, region) + .send(new GetResourcesCommand({ PaginationToken: token })); + for (const m of out.ResourceTagMappingList || []) { + const t = {}; + for (const kv of m.Tags || []) t[kv.Key] = kv.Value; + tags.set(m.ResourceARN, t); + } + token = out.PaginationToken || undefined; + } while (token); + return tags; + }, + }, + }; +} + +// Tags for every resource the readers may need, from both regions this system +// uses. A failed sweep leaves the map empty: each taggable resource then +// reports its tags as unread (unassessed), never as missing. +async function sweepTags(aws, regions) { + const all = new Map(); + for (const region of regions) { + try { + for (const [arn, t] of await aws.tagging.sweep(region)) all.set(arn, t); + } catch (err) { + console.warn(`Tag sweep failed in ${region}: ${err.name}`); + } + } + return all; +} + // ============================================================================= // POLICY EVALUATION // ============================================================================= @@ -250,10 +424,21 @@ async function streamToString(stream) { return Buffer.concat(chunks).toString('utf-8'); } -async function readDeploySignal(s3, bucketName) { +// The previous runtime signal, or null when there is none or it is unreadable. +async function readPreviousRuntimeSignal(s3, bucketName) { + try { + const out = await s3.send(new GetObjectCommand({ Bucket: bucketName, Key: '.well-known/ksi-signal-runtime.json' })); + return JSON.parse(await streamToString(out.Body)); + } catch (err) { + console.warn(`No previous runtime signal carried forward: ${err.name}`); + return null; + } +} + +async function readDeploySignal(s3, bucketName, key = '.well-known/ksi-signal.json') { const out = await s3.send(new GetObjectCommand({ Bucket: bucketName, - Key: '.well-known/ksi-signal.json', + Key: key, })); const body = await streamToString(out.Body); return JSON.parse(body); @@ -297,7 +482,7 @@ async function evaluateSecretRotation(sm, secretArn) { } } -async function buildRuntimeSignal(deploySignal, s3, cf, sm, policy, policyVersion, invokedFunctionArn) { +async function buildRuntimeSignal(deploySignal, s3, cf, sm, policy, policyVersion, invokedFunctionArn, readers) { const components = deploySignal.components ?? []; const validations = []; let validationIdx = 0; @@ -358,6 +543,17 @@ async function buildRuntimeSignal(deploySignal, s3, cf, sm, policy, policyVersio }); } + // Every other machine component type: the readers in describers.js read + // the live configuration and the same compiled policy judges it. + if (readers) { + const evaluate = (input) => evaluateResource(policy, input); + const nextId = () => `r-${String(validationIdx++).padStart(4, '0')}`; + validations.push(...await validateComponents( + { ...readers, components, account: accountOf(invokedFunctionArn) }, + components, evaluate, 'terraform.compliance', `wasm-${policyVersion}`, nextId, + )); + } + const provenance = { builder: { id: 'aws-lambda://runtime-ksi-emitter', @@ -379,6 +575,8 @@ async function buildRuntimeSignal(deploySignal, s3, cf, sm, policy, policyVersio emitter: 'runtime', csp: deploySignal.csp || 'aws', system_id: deploySignal.system_id, + // CDS-CSO-FID: the offering's FedRAMP ID, as the deploy signal carries it. + ...(deploySignal.fedRampId ? { fedRampId: deploySignal.fedRampId } : {}), provenance, components, validations, @@ -464,12 +662,19 @@ exports.handler = async (event, context) => { const cf = new CloudFrontClient({ region: 'us-east-1' }); const sm = new SecretsManagerClient({ region }); - const { policy, version: policyVersion } = await getPolicy(); + let staged; + try { + staged = stageKeys(event); + } catch (err) { + return { statusCode: 400, body: JSON.stringify({ message: err.message, compliant: false }) }; + } + + const { policy, version: policyVersion, data: policyData } = await getPolicy(); console.log(`Loaded compiled Rego policy (sha256:${policyVersion}...)`); let deploySignal; try { - deploySignal = await readDeploySignal(s3, bucketName); + deploySignal = await readDeploySignal(s3, bucketName, staged ? staged.deploySignal : undefined); } catch (err) { console.error('Could not read deploy-time signal', err); return { @@ -484,8 +689,15 @@ exports.handler = async (event, context) => { // The inventory names resources with ACCOUNT in place of the account ID; // this Lambda's own ARN supplies it wherever a callable ARN is needed (account.js). + const aws = makeAws(region); + const readers = { + aws, + region, + tags: await sweepTags(aws, [...new Set([region, 'us-east-1'])]), + taggableTypes: policyData?.config?.gate?.taggable_types || [], + }; let runtimeSignal = await buildRuntimeSignal(deploySignal, s3, cf, sm, policy, policyVersion, - context?.invokedFunctionArn); + context?.invokedFunctionArn, readers); // Sign the signal (POAM-002) and publish the verifying public key. The signing // key is resolved by its stable alias, derived from the bucket/domain @@ -498,9 +710,23 @@ exports.handler = async (event, context) => { // published without the key needed to verify it: if either step fails, the // signal stays unsigned (the catch leaves runtimeSignal unmodified). const signingKeyAlias = 'alias/' + bucketName.replace(/\./g, '-') + '-runtime-signing'; + const kms = new KMSClient({ region }); + + // Run history (VER-RPT-PER): carried forward from the previous signal only + // if it verifies against this emitter's key, then signed with the rest. + let publicKeyPem = null; + try { + publicKeyPem = derToPem((await kms.send(new GetPublicKeyCommand({ KeyId: signingKeyAlias }))).PublicKey); + } catch (err) { + console.warn(`Could not read the signing public key: ${err.name}`); + } + const previous = await readPreviousRuntimeSignal(s3, bucketName); + runtimeSignal.run_history = nextRunHistory(previous, verifySignal(previous, publicKeyPem), runtimeSignal); + try { - const kms = new KMSClient({ region }); - await publishPublicKey(kms, s3, bucketName, signingKeyAlias); + // A staged run is verified against the committed key by the deploy; + // only a published signal needs the published key beside it. + if (!staged) await publishPublicKey(kms, s3, bucketName, signingKeyAlias); runtimeSignal = await signSignal(runtimeSignal, kms, signingKeyAlias); console.log(`Public key published; runtime signal signed with ${signingKeyAlias}`); } catch (err) { @@ -509,7 +735,7 @@ exports.handler = async (event, context) => { await s3.send(new PutObjectCommand({ Bucket: bucketName, - Key: '.well-known/ksi-signal-runtime.json', + Key: staged ? staged.runtimeSignal : '.well-known/ksi-signal-runtime.json', Body: JSON.stringify(runtimeSignal, null, 2) + '\n', ContentType: 'application/json', CacheControl: 'public, max-age=300', @@ -524,7 +750,8 @@ exports.handler = async (event, context) => { return { statusCode: 200, body: JSON.stringify({ - message: 'Runtime KSI signal published', + message: staged ? 'Runtime KSI signal staged' : 'Runtime KSI signal published', + ...(staged ? { staged_key: staged.runtimeSignal } : {}), compliant, signal_id: runtimeSignal.signal_id, policy_version: policyVersion, @@ -532,3 +759,6 @@ exports.handler = async (event, context) => { }), }; }; + +// For local verification and tests only; the Lambda runtime calls `handler`. +exports.internals = { makeAws, sweepTags, buildRuntimeSignal, getPolicy, stageKeys }; diff --git a/infrastructure/lambda/package-lock.json b/infrastructure/lambda/package-lock.json index 4708a685..aee9fdba 100644 --- a/infrastructure/lambda/package-lock.json +++ b/infrastructure/lambda/package-lock.json @@ -8,10 +8,24 @@ "name": "opa-compliance-lambda", "version": "3.0.0", "dependencies": { + "@aws-sdk/client-acm": "^3.1158.0", + "@aws-sdk/client-apigatewayv2": "^3.1158.0", "@aws-sdk/client-cloudfront": "^3.1158.0", + "@aws-sdk/client-cloudtrail": "^3.1158.0", + "@aws-sdk/client-cloudwatch": "^3.1158.0", + "@aws-sdk/client-cloudwatch-logs": "^3.1158.0", + "@aws-sdk/client-cognito-identity-provider": "^3.1158.0", + "@aws-sdk/client-dynamodb": "^3.1158.0", + "@aws-sdk/client-eventbridge": "^3.1158.0", + "@aws-sdk/client-iam": "^3.1158.0", "@aws-sdk/client-kms": "^3.1158.0", + "@aws-sdk/client-lambda": "^3.1158.0", + "@aws-sdk/client-resource-groups-tagging-api": "^3.1158.0", + "@aws-sdk/client-route-53": "^3.1158.0", "@aws-sdk/client-s3": "^3.1158.0", "@aws-sdk/client-secrets-manager": "^3.1158.0", + "@aws-sdk/client-sns": "^3.1158.0", + "@aws-sdk/client-sqs": "^3.1158.0", "@open-policy-agent/opa-wasm": "^1.9.0" } }, @@ -31,6 +45,42 @@ "node": ">=20.0.0" } }, + "node_modules/@aws-sdk/client-acm": { + "version": "3.1158.0", + "resolved": "https://registry.npmjs.org/@aws-sdk/client-acm/-/client-acm-3.1158.0.tgz", + "integrity": "sha512-BubHJhBJU6m5cTgF+9QZQUZVz46WSa+Wbb1ADuzNaU1/xxaYefKXaxQRg7eIwwa5mJfyTI9XKqTqICw6J2O6OA==", + "dependencies": { + "@aws-sdk/core": "^3.978.6", + "@aws-sdk/credential-provider-node": "^3.972.89", + "@aws-sdk/types": "^3.975.0", + "@smithy/core": "^3.37.0", + "@smithy/fetch-http-handler": "^5.8.0", + "@smithy/node-http-handler": "^4.13.0", + "@smithy/types": "^4.19.0", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=20.0.0" + } + }, + "node_modules/@aws-sdk/client-apigatewayv2": { + "version": "3.1158.0", + "resolved": "https://registry.npmjs.org/@aws-sdk/client-apigatewayv2/-/client-apigatewayv2-3.1158.0.tgz", + "integrity": "sha512-4Wg7SX73EMFhHwB/zzHk6DOARVup6ZuVaYMrIQr9Jq+6QcaSYmDxmmAZnXFfBZ0K0RdSeM2sU8xYZ5UJ4uu7aA==", + "dependencies": { + "@aws-sdk/core": "^3.978.6", + "@aws-sdk/credential-provider-node": "^3.972.89", + "@aws-sdk/types": "^3.975.0", + "@smithy/core": "^3.37.0", + "@smithy/fetch-http-handler": "^5.8.0", + "@smithy/node-http-handler": "^4.13.0", + "@smithy/types": "^4.19.0", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=20.0.0" + } + }, "node_modules/@aws-sdk/client-cloudfront": { "version": "3.1158.0", "resolved": "https://registry.npmjs.org/@aws-sdk/client-cloudfront/-/client-cloudfront-3.1158.0.tgz", @@ -50,6 +100,136 @@ "node": ">=20.0.0" } }, + "node_modules/@aws-sdk/client-cloudtrail": { + "version": "3.1158.0", + "resolved": "https://registry.npmjs.org/@aws-sdk/client-cloudtrail/-/client-cloudtrail-3.1158.0.tgz", + "integrity": "sha512-OfOFgV7uT3BECk0F41nrMn2jT91IJZumDe2ah2ttoeDWZUOH2uKEfzAYJEjYWBBxSaRSJc/1g4Dcy+DpKR0jlQ==", + "dependencies": { + "@aws-sdk/core": "^3.978.6", + "@aws-sdk/credential-provider-node": "^3.972.89", + "@aws-sdk/types": "^3.975.0", + "@smithy/core": "^3.37.0", + "@smithy/fetch-http-handler": "^5.8.0", + "@smithy/node-http-handler": "^4.13.0", + "@smithy/types": "^4.19.0", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=20.0.0" + } + }, + "node_modules/@aws-sdk/client-cloudwatch": { + "version": "3.1158.0", + "resolved": "https://registry.npmjs.org/@aws-sdk/client-cloudwatch/-/client-cloudwatch-3.1158.0.tgz", + "integrity": "sha512-i/6zPFnyrv0aDbeIKpWbOcCxWZGgJzRcDix6vSNDEB+9r9CxESbjp5h04hbW6ACOyK8FT5fm8QShcr1TscEqfQ==", + "dependencies": { + "@aws-sdk/core": "^3.978.6", + "@aws-sdk/credential-provider-node": "^3.972.89", + "@aws-sdk/types": "^3.975.0", + "@smithy/core": "^3.37.0", + "@smithy/fetch-http-handler": "^5.8.0", + "@smithy/middleware-compression": "^4.6.2", + "@smithy/node-http-handler": "^4.13.0", + "@smithy/types": "^4.19.0", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=20.0.0" + } + }, + "node_modules/@aws-sdk/client-cloudwatch-logs": { + "version": "3.1158.0", + "resolved": "https://registry.npmjs.org/@aws-sdk/client-cloudwatch-logs/-/client-cloudwatch-logs-3.1158.0.tgz", + "integrity": "sha512-BLuQlJuK2dxWYjFZwFp7PvSBYs5TlTTPpi54FSXDRWILZJPbYNcCTQiPdgoN1kac7yEq4X2CKFrMHp7deMFKgw==", + "dependencies": { + "@aws-sdk/core": "^3.978.6", + "@aws-sdk/credential-provider-node": "^3.972.89", + "@aws-sdk/types": "^3.975.0", + "@smithy/core": "^3.37.0", + "@smithy/fetch-http-handler": "^5.8.0", + "@smithy/node-http-handler": "^4.13.0", + "@smithy/types": "^4.19.0", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=20.0.0" + } + }, + "node_modules/@aws-sdk/client-cognito-identity-provider": { + "version": "3.1158.0", + "resolved": "https://registry.npmjs.org/@aws-sdk/client-cognito-identity-provider/-/client-cognito-identity-provider-3.1158.0.tgz", + "integrity": "sha512-bYaxPv1m1Er8a4chW+fTin0i8iloKmHKhtPuHXuUIgG1617spTenUub7W8z92PMzxaNkrFbNBcCgmVgrdzYDMw==", + "dependencies": { + "@aws-sdk/core": "^3.978.6", + "@aws-sdk/credential-provider-node": "^3.972.89", + "@aws-sdk/types": "^3.975.0", + "@smithy/core": "^3.37.0", + "@smithy/fetch-http-handler": "^5.8.0", + "@smithy/node-http-handler": "^4.13.0", + "@smithy/types": "^4.19.0", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=20.0.0" + } + }, + "node_modules/@aws-sdk/client-dynamodb": { + "version": "3.1158.0", + "resolved": "https://registry.npmjs.org/@aws-sdk/client-dynamodb/-/client-dynamodb-3.1158.0.tgz", + "integrity": "sha512-2nTIBFPBr5zv3cmSLZn4WExi9X4Ddoi2K9LWYUtHfj30v3XBhEmgkYcESHfJR8uzdzBUAI1N/sDFSkqA1gTASg==", + "dependencies": { + "@aws-sdk/core": "^3.978.6", + "@aws-sdk/credential-provider-node": "^3.972.89", + "@aws-sdk/dynamodb-codec": "^3.973.51", + "@aws-sdk/middleware-endpoint-discovery": "^3.972.35", + "@aws-sdk/types": "^3.975.0", + "@smithy/core": "^3.37.0", + "@smithy/fetch-http-handler": "^5.8.0", + "@smithy/node-http-handler": "^4.13.0", + "@smithy/types": "^4.19.0", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=20.0.0" + } + }, + "node_modules/@aws-sdk/client-eventbridge": { + "version": "3.1158.0", + "resolved": "https://registry.npmjs.org/@aws-sdk/client-eventbridge/-/client-eventbridge-3.1158.0.tgz", + "integrity": "sha512-K1IpQWubexuOTlAaqCFsHgJkgfl+STQO+Fs2ZZkiJfSpWORLHyKRbgma8LlSteKX0ms/I3Gur/e4PG4MZ+NLjw==", + "dependencies": { + "@aws-sdk/core": "^3.978.6", + "@aws-sdk/credential-provider-node": "^3.972.89", + "@aws-sdk/signature-v4-multi-region": "^3.996.49", + "@aws-sdk/types": "^3.975.0", + "@smithy/core": "^3.37.0", + "@smithy/fetch-http-handler": "^5.8.0", + "@smithy/node-http-handler": "^4.13.0", + "@smithy/types": "^4.19.0", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=20.0.0" + } + }, + "node_modules/@aws-sdk/client-iam": { + "version": "3.1158.0", + "resolved": "https://registry.npmjs.org/@aws-sdk/client-iam/-/client-iam-3.1158.0.tgz", + "integrity": "sha512-K2OxaJpK5KAobeOwhSjKi3KROBtF6XVSjRUyudNpl1yhzSpRXl0bQ+IHiShC/nSdDQ7bqLB62P9IkvB4nEWfkA==", + "dependencies": { + "@aws-sdk/core": "^3.978.6", + "@aws-sdk/credential-provider-node": "^3.972.89", + "@aws-sdk/types": "^3.975.0", + "@smithy/core": "^3.37.0", + "@smithy/fetch-http-handler": "^5.8.0", + "@smithy/node-http-handler": "^4.13.0", + "@smithy/types": "^4.19.0", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=20.0.0" + } + }, "node_modules/@aws-sdk/client-kms": { "version": "3.1158.0", "resolved": "https://registry.npmjs.org/@aws-sdk/client-kms/-/client-kms-3.1158.0.tgz", @@ -69,6 +249,61 @@ "node": ">=20.0.0" } }, + "node_modules/@aws-sdk/client-lambda": { + "version": "3.1158.0", + "resolved": "https://registry.npmjs.org/@aws-sdk/client-lambda/-/client-lambda-3.1158.0.tgz", + "integrity": "sha512-8+caqKfZT/sRRaLzUcpSVjeiU255UL63/U6NWatebxG9y2jPMYR86mML99dZe2oarEkZH4OCf2gFXDuTdRlI6w==", + "dependencies": { + "@aws-sdk/core": "^3.978.6", + "@aws-sdk/credential-provider-node": "^3.972.89", + "@aws-sdk/types": "^3.975.0", + "@smithy/core": "^3.37.0", + "@smithy/fetch-http-handler": "^5.8.0", + "@smithy/node-http-handler": "^4.13.0", + "@smithy/types": "^4.19.0", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=20.0.0" + } + }, + "node_modules/@aws-sdk/client-resource-groups-tagging-api": { + "version": "3.1158.0", + "resolved": "https://registry.npmjs.org/@aws-sdk/client-resource-groups-tagging-api/-/client-resource-groups-tagging-api-3.1158.0.tgz", + "integrity": "sha512-VtZ0i8EuNdhkqy65DPVuMkypIxcA2tunhVvpgwTmvKiqquuE0RVgIjq2b1Vma3/CYQd2Tl6tf5FR4FmgmFm8ww==", + "dependencies": { + "@aws-sdk/core": "^3.978.6", + "@aws-sdk/credential-provider-node": "^3.972.89", + "@aws-sdk/types": "^3.975.0", + "@smithy/core": "^3.37.0", + "@smithy/fetch-http-handler": "^5.8.0", + "@smithy/node-http-handler": "^4.13.0", + "@smithy/types": "^4.19.0", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=20.0.0" + } + }, + "node_modules/@aws-sdk/client-route-53": { + "version": "3.1158.0", + "resolved": "https://registry.npmjs.org/@aws-sdk/client-route-53/-/client-route-53-3.1158.0.tgz", + "integrity": "sha512-+Q1liLjfQSiMJk1+Pknfshb1WYnDj8abWeoc/71WZKt4S4w0L5XzkvwSny4KscbQkJXZu0hNqdbNSYy0PmSpfw==", + "dependencies": { + "@aws-sdk/core": "^3.978.6", + "@aws-sdk/credential-provider-node": "^3.972.89", + "@aws-sdk/middleware-sdk-route53": "^3.972.28", + "@aws-sdk/types": "^3.975.0", + "@smithy/core": "^3.37.0", + "@smithy/fetch-http-handler": "^5.8.0", + "@smithy/node-http-handler": "^4.13.0", + "@smithy/types": "^4.19.0", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=20.0.0" + } + }, "node_modules/@aws-sdk/client-s3": { "version": "3.1158.0", "resolved": "https://registry.npmjs.org/@aws-sdk/client-s3/-/client-s3-3.1158.0.tgz", @@ -110,17 +345,53 @@ "node": ">=20.0.0" } }, + "node_modules/@aws-sdk/client-sns": { + "version": "3.1158.0", + "resolved": "https://registry.npmjs.org/@aws-sdk/client-sns/-/client-sns-3.1158.0.tgz", + "integrity": "sha512-YxiSOQ/SVfimZQ6Fj5AgIEpjuvuUgvMuDwqNMcG8K2viursUBqO3QBYMLxD3gaJqfWFa5vVoH447J6GI5hQOcg==", + "dependencies": { + "@aws-sdk/core": "^3.978.6", + "@aws-sdk/credential-provider-node": "^3.972.89", + "@aws-sdk/types": "^3.975.0", + "@smithy/core": "^3.37.0", + "@smithy/fetch-http-handler": "^5.8.0", + "@smithy/node-http-handler": "^4.13.0", + "@smithy/types": "^4.19.0", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=20.0.0" + } + }, + "node_modules/@aws-sdk/client-sqs": { + "version": "3.1158.0", + "resolved": "https://registry.npmjs.org/@aws-sdk/client-sqs/-/client-sqs-3.1158.0.tgz", + "integrity": "sha512-JCIwxVX8F97JIOSH+JUD/Qwpq7rXaATmiuUs6eId3yBsSDGbm1ZuxRXqDsehQ/i5oDOEJSFETnFlO3scWqo5qw==", + "dependencies": { + "@aws-sdk/core": "^3.978.6", + "@aws-sdk/credential-provider-node": "^3.972.89", + "@aws-sdk/middleware-sdk-sqs": "^3.972.47", + "@aws-sdk/types": "^3.975.0", + "@smithy/core": "^3.37.0", + "@smithy/fetch-http-handler": "^5.8.0", + "@smithy/node-http-handler": "^4.13.0", + "@smithy/types": "^4.19.0", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=20.0.0" + } + }, "node_modules/@aws-sdk/core": { - "version": "3.978.6", - "resolved": "https://registry.npmjs.org/@aws-sdk/core/-/core-3.978.6.tgz", - "integrity": "sha512-ykF/MiYoM15dgZwF/WLgjJXVbAK2wU6vjPigeEnOHwyUJ0rdlraO5uekecKNVPkvOnz+oju/5zljViQs1nI1FQ==", - "license": "Apache-2.0", + "version": "3.980.0", + "resolved": "https://registry.npmjs.org/@aws-sdk/core/-/core-3.980.0.tgz", + "integrity": "sha512-2RVSP/SsPS8HSPPzIPWNYFnSmlOdxx8VDlt5gDOuMaq9UiIi35pUyo6ZEuJcysjVCu0L8Lv5dJevLLpEkyF0/Q==", "dependencies": { "@aws-sdk/types": "^3.975.0", - "@aws-sdk/xml-builder": "^3.972.41", + "@aws-sdk/xml-builder": "^3.972.42", "@aws/lambda-invoke-store": "^0.3.0", - "@smithy/core": "^3.37.0", - "@smithy/signature-v4": "^5.7.4", + "@smithy/core": "^3.38.0", + "@smithy/signature-v4": "^5.7.5", "@smithy/types": "^4.19.0", "bowser": "^2.11.0", "tslib": "^2.6.2" @@ -286,6 +557,60 @@ "node": ">=20.0.0" } }, + "node_modules/@aws-sdk/dynamodb-codec": { + "version": "3.973.55", + "resolved": "https://registry.npmjs.org/@aws-sdk/dynamodb-codec/-/dynamodb-codec-3.973.55.tgz", + "integrity": "sha512-4TL2HVo0YvhF5x8VTZwD14Fq6t8prBPqxlSa1actdGmkTk+0t0jcyGOO05zql+UEnAJ2WPctN6sNmuwt7Q30DA==", + "dependencies": { + "@aws-sdk/core": "^3.980.0", + "@smithy/core": "^3.38.0", + "@smithy/types": "^4.19.0", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=20.0.0" + } + }, + "node_modules/@aws-sdk/endpoint-cache": { + "version": "3.972.11", + "resolved": "https://registry.npmjs.org/@aws-sdk/endpoint-cache/-/endpoint-cache-3.972.11.tgz", + "integrity": "sha512-8q1ICxcDjHId3bBryuu/j+1L9y5/3uQnwzLDt5j2ElcjZSoWmFtymdJy7OjLrluSMe0Z4mq5bcH4fxBXvlEHfw==", + "dependencies": { + "mnemonist": "0.38.3", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=20.0.0" + } + }, + "node_modules/@aws-sdk/middleware-endpoint-discovery": { + "version": "3.972.37", + "resolved": "https://registry.npmjs.org/@aws-sdk/middleware-endpoint-discovery/-/middleware-endpoint-discovery-3.972.37.tgz", + "integrity": "sha512-+KAK020JY95Q7Swwo5b9pl9S11VPuNLqecCW5bzkksWiU5pmI85lAloOD4qlIKIA/P8FlrRJ60XJ6+lnDQK/DQ==", + "dependencies": { + "@aws-sdk/endpoint-cache": "^3.972.11", + "@aws-sdk/types": "^3.975.0", + "@smithy/core": "^3.38.0", + "@smithy/types": "^4.19.0", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=20.0.0" + } + }, + "node_modules/@aws-sdk/middleware-sdk-route53": { + "version": "3.972.28", + "resolved": "https://registry.npmjs.org/@aws-sdk/middleware-sdk-route53/-/middleware-sdk-route53-3.972.28.tgz", + "integrity": "sha512-93l3lB5ngw0XQDGvuK/R9R3UAN4+xeYgLOW8E6nzldlNhu0E8vfkYMTlh5km643i9F193b5ZO21wOWWT47RxHw==", + "dependencies": { + "@aws-sdk/types": "^3.975.0", + "@smithy/types": "^4.19.0", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=20.0.0" + } + }, "node_modules/@aws-sdk/middleware-sdk-s3": { "version": "3.972.82", "resolved": "https://registry.npmjs.org/@aws-sdk/middleware-sdk-s3/-/middleware-sdk-s3-3.972.82.tgz", @@ -303,6 +628,20 @@ "node": ">=20.0.0" } }, + "node_modules/@aws-sdk/middleware-sdk-sqs": { + "version": "3.972.48", + "resolved": "https://registry.npmjs.org/@aws-sdk/middleware-sdk-sqs/-/middleware-sdk-sqs-3.972.48.tgz", + "integrity": "sha512-GNzuBLwvUUV++svohxeAj1sf4AgA2gOevKTYHRKIDPpVD30YoBiNBb+X0L28b9KazqHhG6WilyiOE4XDmZeHeg==", + "dependencies": { + "@aws-sdk/types": "^3.975.0", + "@smithy/core": "^3.38.0", + "@smithy/types": "^4.19.0", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=20.0.0" + } + }, "node_modules/@aws-sdk/nested-clients": { "version": "3.997.51", "resolved": "https://registry.npmjs.org/@aws-sdk/nested-clients/-/nested-clients-3.997.51.tgz", @@ -368,10 +707,9 @@ } }, "node_modules/@aws-sdk/xml-builder": { - "version": "3.972.41", - "resolved": "https://registry.npmjs.org/@aws-sdk/xml-builder/-/xml-builder-3.972.41.tgz", - "integrity": "sha512-ctjVSyCMegrWfXlx6VqzSBFI6UqmQ5ZlnfMhdLIiWmhoH8UAQxSCP5N3OpG7X3k4LnS7ou74C4mt20+bfTW2aQ==", - "license": "Apache-2.0", + "version": "3.972.42", + "resolved": "https://registry.npmjs.org/@aws-sdk/xml-builder/-/xml-builder-3.972.42.tgz", + "integrity": "sha512-smX8/gNP8Kjq+CWTBMZQLQ912vOQjiWExzwzvMO+eujPB5RY8IbtF0AGdUUXHKN7KoDWK9dIcuW0WG269kiP6w==", "dependencies": { "@smithy/types": "^4.19.0", "tslib": "^2.6.2" @@ -391,12 +729,11 @@ } }, "node_modules/@smithy/core": { - "version": "3.37.0", - "resolved": "https://registry.npmjs.org/@smithy/core/-/core-3.37.0.tgz", - "integrity": "sha512-97imTcCyiPd8k0e9+ts/Sp0W65Dn9Ti357J7M09Ov4tI8Q1JDJVFSoAJtjEVKqfHEr3Pdo2jfolqKCaaiszH0g==", - "license": "Apache-2.0", + "version": "3.39.0", + "resolved": "https://registry.npmjs.org/@smithy/core/-/core-3.39.0.tgz", + "integrity": "sha512-JJ/46AWQ4ipS1N2eZmUj7yzIhH8NhQIfAE+dce7NSB6dmFh+7hvD4pbofcoT4I0Xzfy/LNhZx3V2QhwYyAiqdg==", "dependencies": { - "@smithy/types": "^4.19.0", + "@smithy/types": "^4.20.0", "tslib": "^2.6.2" }, "engines": { @@ -431,6 +768,20 @@ "node": ">=18.0.0" } }, + "node_modules/@smithy/middleware-compression": { + "version": "4.6.2", + "resolved": "https://registry.npmjs.org/@smithy/middleware-compression/-/middleware-compression-4.6.2.tgz", + "integrity": "sha512-Q9d+luiRjyHT6kCL/9NyGpdZJgodh4vtvfHC6H8SqoVKrV2k9RoyI9/IloVfdCYks3/2DIi7BsYYLcda5KZS0A==", + "dependencies": { + "@smithy/core": "^3.33.2", + "@smithy/types": "^4.17.2", + "fflate": "0.8.3", + "tslib": "^2.6.2" + }, + "engines": { + "node": ">=18.0.0" + } + }, "node_modules/@smithy/node-http-handler": { "version": "4.13.0", "resolved": "https://registry.npmjs.org/@smithy/node-http-handler/-/node-http-handler-4.13.0.tgz", @@ -446,12 +797,11 @@ } }, "node_modules/@smithy/signature-v4": { - "version": "5.7.4", - "resolved": "https://registry.npmjs.org/@smithy/signature-v4/-/signature-v4-5.7.4.tgz", - "integrity": "sha512-tHy0K0VtqNd5Y7Y41h0a0Lhh0L1GzC08dTWg0F7vRJWFtTENg7IZikf3wQkanYIRdb7ngoIPMTmqgUi401fEeQ==", - "license": "Apache-2.0", + "version": "5.7.5", + "resolved": "https://registry.npmjs.org/@smithy/signature-v4/-/signature-v4-5.7.5.tgz", + "integrity": "sha512-WPjdr5oWOk1LArpI4pavu+fSo+/evi0Re1olxGvqwuZopd4gYR1UGCi+Soyn/IjmafqbWs+ZC+3AKxJS3ZpwUg==", "dependencies": { - "@smithy/core": "^3.35.0", + "@smithy/core": "^3.38.0", "@smithy/types": "^4.19.0", "tslib": "^2.6.2" }, @@ -460,10 +810,9 @@ } }, "node_modules/@smithy/types": { - "version": "4.19.0", - "resolved": "https://registry.npmjs.org/@smithy/types/-/types-4.19.0.tgz", - "integrity": "sha512-r7jh49VJxGerfAcTQA6gXcKc+98zOp/tqRwzYjgOE+iSQsP6cEU1hq2QzbuipmP68QtYdY9wKEhiCQZIzHgZ4Q==", - "license": "Apache-2.0", + "version": "4.20.0", + "resolved": "https://registry.npmjs.org/@smithy/types/-/types-4.20.0.tgz", + "integrity": "sha512-lCA6QG22dPk9ecHbv91jDQZsmtPUjdS1aE2Il6NNPqe7DrYc0dZQi6DhcESk2KYXH2sp5xbAcGdYMZDFnuzA2A==", "dependencies": { "tslib": "^2.6.2" }, @@ -477,6 +826,24 @@ "integrity": "sha512-tzPjzCxygAKWFOJP011oxFHs57HzIhOEracIgAePE4pqB3LikALKnSzUyU4MGs9/iCEUuHlAJTjTc5M+u7YEGg==", "license": "MIT" }, + "node_modules/fflate": { + "version": "0.8.3", + "resolved": "https://registry.npmjs.org/fflate/-/fflate-0.8.3.tgz", + "integrity": "sha512-tbZNuJrLwGUp3zshBtdy4W+ORxZuIh8a5ilyIEQDC5rY1f3U20JMry0Ll3WBzU58EZKsEuJFXhb5gwv8CsPvgA==" + }, + "node_modules/mnemonist": { + "version": "0.38.3", + "resolved": "https://registry.npmjs.org/mnemonist/-/mnemonist-0.38.3.tgz", + "integrity": "sha512-2K9QYubXx/NAjv4VLq1d1Ly8pWNC5L3BrixtdkyTegXWJIqY+zLNDhhX/A+ZwWt70tB1S8H4BE8FLYEFyNoOBw==", + "dependencies": { + "obliterator": "^1.6.1" + } + }, + "node_modules/obliterator": { + "version": "1.6.1", + "resolved": "https://registry.npmjs.org/obliterator/-/obliterator-1.6.1.tgz", + "integrity": "sha512-9WXswnqINnnhOG/5SLimUlzuU1hFJUc8zkwyD59Sd+dPOMf05PmnYG/d6Q7HZ+KmgkZJa1PxRso6QdM3sTNHig==" + }, "node_modules/sprintf-js": { "version": "1.1.3", "resolved": "https://registry.npmjs.org/sprintf-js/-/sprintf-js-1.1.3.tgz", diff --git a/infrastructure/lambda/package.json b/infrastructure/lambda/package.json index 1a34c9c3..0c9c42b9 100644 --- a/infrastructure/lambda/package.json +++ b/infrastructure/lambda/package.json @@ -4,10 +4,24 @@ "description": "Runtime KSI signal emitter. Validates the live AWS configuration of components named in the deploy-time signal by evaluating the same Rego policies (compiled to Wasm) used by the deploy-time gate.", "main": "index.js", "dependencies": { + "@aws-sdk/client-acm": "^3.1158.0", + "@aws-sdk/client-apigatewayv2": "^3.1158.0", "@aws-sdk/client-cloudfront": "^3.1158.0", + "@aws-sdk/client-cloudtrail": "^3.1158.0", + "@aws-sdk/client-cloudwatch": "^3.1158.0", + "@aws-sdk/client-cloudwatch-logs": "^3.1158.0", + "@aws-sdk/client-cognito-identity-provider": "^3.1158.0", + "@aws-sdk/client-dynamodb": "^3.1158.0", + "@aws-sdk/client-eventbridge": "^3.1158.0", + "@aws-sdk/client-iam": "^3.1158.0", "@aws-sdk/client-kms": "^3.1158.0", + "@aws-sdk/client-lambda": "^3.1158.0", + "@aws-sdk/client-resource-groups-tagging-api": "^3.1158.0", + "@aws-sdk/client-route-53": "^3.1158.0", "@aws-sdk/client-s3": "^3.1158.0", "@aws-sdk/client-secrets-manager": "^3.1158.0", + "@aws-sdk/client-sns": "^3.1158.0", + "@aws-sdk/client-sqs": "^3.1158.0", "@open-policy-agent/opa-wasm": "^1.9.0" } } diff --git a/infrastructure/lambda/stage.js b/infrastructure/lambda/stage.js new file mode 100644 index 00000000..203cc8f1 --- /dev/null +++ b/infrastructure/lambda/stage.js @@ -0,0 +1,19 @@ +'use strict'; + +// FRC-CSX-VVK: the deploy invokes the emitter after apply and before it builds +// the SDR, with {stage: <commit SHA>}: the emitter re-validates the deployed +// system against the inventory the deploy is about to publish (staged under +// deploy-staging/<sha>/), and writes its signed signal next to it instead of +// over the published one. Anything but a 40-hex SHA is refused, so an event +// cannot name an arbitrary key. +const STAGE_PREFIX = 'deploy-staging/'; +function stageKeys(event) { + if (event == null || event.stage === undefined) return null; + if (typeof event.stage !== 'string' || !/^[0-9a-f]{40}$/.test(event.stage)) { + throw new Error('stage must be a 40-character lowercase hex commit SHA'); + } + const dir = `${STAGE_PREFIX}${event.stage}/`; + return { deploySignal: `${dir}ksi-signal.json`, runtimeSignal: `${dir}ksi-signal-runtime.json` }; +} + +module.exports = { stageKeys, STAGE_PREFIX }; diff --git a/infrastructure/logging.tf b/infrastructure/logging.tf index ed5decd5..fd2f518e 100644 --- a/infrastructure/logging.tf +++ b/infrastructure/logging.tf @@ -60,6 +60,26 @@ resource "aws_s3_bucket_lifecycle_configuration" "logs" { noncurrent_version_expiration { noncurrent_days = 30 } abort_incomplete_multipart_upload { days_after_initiation = 7 } } + # CloudFront access records (CDS-TRC-ACL) are kept 90 days, not 400: the + # operator's privacy limit. S3 applies the earliest expiration when rules + # overlap, so these prefixes expire at 90 days. Only aggregate monthly + # summaries outlive them (/.well-known/access-summary.json, 13 months). + rule { + id = "expire-edge-access-records" + status = "Enabled" + filter { prefix = "cloudfront/" } + expiration { days = 90 } + noncurrent_version_expiration { noncurrent_days = 1 } + abort_incomplete_multipart_upload { days_after_initiation = 7 } + } + rule { + id = "expire-edge-access-records-default-prefix" + status = "Enabled" + filter { prefix = "AWSLogs/${data.aws_caller_identity.current.account_id}/CloudFront/" } + expiration { days = 90 } + noncurrent_version_expiration { noncurrent_days = 1 } + abort_incomplete_multipart_upload { days_after_initiation = 7 } + } } # Allow the AWS log-delivery services to write to their respective prefixes, @@ -86,7 +106,13 @@ resource "aws_s3_bucket_policy" "logs" { Effect = "Allow" Principal = { Service = "delivery.logs.amazonaws.com" } Action = "s3:PutObject" - Resource = "${aws_s3_bucket.logs.arn}/cloudfront/*" + # cloudfront/ is the configured prefix (bootstrap/trust-access-logs.tf); + # AWSLogs/<account>/CloudFront/ is the service's default, kept so a + # delivery that ignores the prefix still lands under the 90-day expiry. + Resource = [ + "${aws_s3_bucket.logs.arn}/cloudfront/*", + "${aws_s3_bucket.logs.arn}/AWSLogs/${data.aws_caller_identity.current.account_id}/CloudFront/*", + ] Condition = { StringEquals = { "aws:SourceAccount" = data.aws_caller_identity.current.account_id } } diff --git a/infrastructure/main.tf b/infrastructure/main.tf index abf11e66..d4a8be3f 100644 --- a/infrastructure/main.tf +++ b/infrastructure/main.tf @@ -494,7 +494,10 @@ resource "aws_iam_role_policy" "lambda_opa" { ] Resource = [ "${data.aws_s3_bucket.website.arn}/.well-known/ksi-signal-runtime.json", - "${data.aws_s3_bucket.website.arn}/.well-known/runtime-signing-pubkey.pem" + "${data.aws_s3_bucket.website.arn}/.well-known/runtime-signing-pubkey.pem", + # FRC-CSX-VVK: the deploy's staged re-validation, read back and deleted + # by the deploy before it builds the SDR (index.js stageKeys). + "${data.aws_s3_bucket.website.arn}/deploy-staging/*/ksi-signal-runtime.json" ] }, { @@ -509,6 +512,123 @@ resource "aws_iam_role_policy" "lambda_opa" { ] Resource = data.aws_cloudfront_distribution.website.arn }, + # ----------------------------------------------------------------------- + # Runtime V&V of every machine component type (FRC-CSX-VVK, VDR-TFR-MVX, + # VDR-TFR-PDD): the readers in lambda/describers.js. Read-only Get / + # Describe / List actions, each scoped to this system's own resources by + # ARN; tests/test_runtime_grants.py fails a change that calls an API the + # role is not granted, or grants an action on "*" other than the tagging + # sweep below. + { + # Role trust, attached and inline policies: this stack's roles and the + # bootstrap stack's GitHub OIDC roles (named by convention). + Effect = "Allow" + Action = ["iam:GetRole", "iam:ListAttachedRolePolicies", "iam:GetRolePolicy"] + Resource = [ + "arn:aws:iam::${data.aws_caller_identity.current.account_id}:role/${replace(var.domain_name, ".", "-")}-*", + "arn:aws:iam::${data.aws_caller_identity.current.account_id}:role/github-actions-*-oidc", + ] + }, + { + # The two bootstrap IAM groups' attached and inline policies. + Effect = "Allow" + Action = ["iam:ListAttachedGroupPolicies", "iam:ListGroupPolicies", "iam:GetGroupPolicy"] + Resource = [ + "arn:aws:iam::${data.aws_caller_identity.current.account_id}:group/operators", + "arn:aws:iam::${data.aws_caller_identity.current.account_id}:group/read-only", + ] + }, + { + Effect = "Allow" + Action = ["iam:GetOpenIDConnectProvider"] + Resource = ["arn:aws:iam::${data.aws_caller_identity.current.account_id}:oidc-provider/token.actions.githubusercontent.com"] + }, + { + # Function configuration (env CMK, code hash) and URL auth type. No + # GetFunction: that would return a presigned link to the code itself. + Effect = "Allow" + Action = ["lambda:GetFunctionConfiguration", "lambda:GetFunctionUrlConfig"] + Resource = ["arn:aws:lambda:${var.aws_region}:${data.aws_caller_identity.current.account_id}:function:${replace(var.domain_name, ".", "-")}-*"] + }, + { + # Retention and key of the log groups. Metadata only: no read of events. + Effect = "Allow" + Action = ["logs:DescribeLogGroups"] + Resource = ["arn:aws:logs:${var.aws_region}:${data.aws_caller_identity.current.account_id}:log-group:*"] + }, + { + # The HTTP API's stages and routes (GET on the API and its children). + Effect = "Allow" + Action = ["apigateway:GET"] + Resource = concat( + formatlist("arn:aws:apigateway:${var.aws_region}::/apis/%s", aws_apigatewayv2_api.silk_reeling[*].id), + formatlist("arn:aws:apigateway:${var.aws_region}::/apis/%s/*", aws_apigatewayv2_api.silk_reeling[*].id), + ) + }, + { + Effect = "Allow" + Action = ["cognito-idp:DescribeUserPool"] + Resource = aws_cognito_user_pool.silk_reeling[*].arn + }, + { + # Key spec, state and rotation of this system's four customer keys. + Effect = "Allow" + Action = ["kms:DescribeKey", "kms:GetKeyRotationStatus"] + Resource = concat( + [aws_kms_key.at_rest.arn, aws_kms_key.runtime_signing.arn], + aws_kms_key.dnssec_ksk[*].arn, + aws_kms_key.silk_reeling[*].arn, + ) + }, + { + Effect = "Allow" + Action = ["sns:GetTopicAttributes"] + Resource = aws_sns_topic.evidence_alerts[*].arn + }, + { + Effect = "Allow" + Action = ["sqs:GetQueueAttributes"] + Resource = aws_sqs_queue.compliance_dlq[*].arn + }, + { + Effect = "Allow" + Action = ["cloudwatch:DescribeAlarms"] + Resource = ["arn:aws:cloudwatch:${var.aws_region}:${data.aws_caller_identity.current.account_id}:alarm:${replace(var.domain_name, ".", "-")}-*"] + }, + { + Effect = "Allow" + Action = ["events:DescribeRule"] + Resource = ["arn:aws:events:${var.aws_region}:${data.aws_caller_identity.current.account_id}:rule/${replace(var.domain_name, ".", "-")}-*"] + }, + { + Effect = "Allow" + Action = ["cloudtrail:GetTrail", "cloudtrail:GetTrailStatus"] + Resource = [aws_cloudtrail.management.arn] + }, + { + # The bootstrap stack's state-lock table (named by convention). + Effect = "Allow" + Action = ["dynamodb:DescribeContinuousBackups"] + Resource = ["arn:aws:dynamodb:${var.aws_region}:${data.aws_caller_identity.current.account_id}:table/${replace(var.domain_name, ".", "-")}-tflock"] + }, + { + Effect = "Allow" + Action = ["route53:GetDNSSEC"] + Resource = formatlist("arn:aws:route53:::hostedzone/%s", data.aws_route53_zone.website[*].zone_id) + }, + { + Effect = "Allow" + Action = ["acm:DescribeCertificate"] + Resource = [data.aws_acm_certificate.website.arn] + }, + { + # Tags for the tagging rules, one sweep per region. The Resource Groups + # Tagging API has no resource-level permissions, so this is the one + # action granted on "*"; it returns tag keys and values only. + Effect = "Allow" + Action = ["tag:GetResources"] + Resource = "*" + }, ] }) } @@ -758,7 +878,7 @@ resource "aws_lambda_function" "opa_compliance" { role = aws_iam_role.lambda_opa.arn handler = "index.handler" runtime = "nodejs22.x" - timeout = 60 + timeout = 180 # every machine component is read live (~60 read-only calls) source_code_hash = data.local_file.lambda_zip.content_base64sha256 # Customer-CMK encryption of the environment variables (POAM-011). diff --git a/infrastructure/policy/compute.rego b/infrastructure/policy/compute.rego new file mode 100644 index 00000000..d4501059 --- /dev/null +++ b/infrastructure/policy/compute.rego @@ -0,0 +1,164 @@ +# ============================================================================= +# FUNCTIONS, DEPLOYED PACKAGES AND MESSAGING SERVICES +# ============================================================================= +# Lambda functions (environment encrypted under a customer key), the deployed +# code package (still the one the deploy inventoried), and the SNS topic, SQS +# queue and DynamoDB table this system uses. +# +# lambda_deployment_package is a runtime-only input, not a Terraform type: the +# emitter compares a function's live CodeSha256 with the code_sha256 the deploy +# recorded in the canonical inventory. The deployed zip holds the inventoried +# packages, so a mismatch means code is running that the deploy never scanned. +# ============================================================================= + +package policy.terraform.compute + +import data.policy.gate + +packages contains r if { + some r in gate.resources + r.type == "lambda_deployment_package" +} + +package_hashes_present(r) if { + gate.value(r, "code_sha256", "") != "" + gate.value(r, "expected_code_sha256", "") != "" +} + +# METADATA +# title: Function environment encrypted with a customer-managed key +# description: Lambda environment variables must be encrypted under a customer-managed KMS key. +# custom: +# id: lambda_env_not_cmk +# category: infrastructure +# severity: MEDIUM +# nist_controls: [sc-28] +# ksi_ids: [KSI-SVC-SIN] +violations contains violation if { + some r in gate.resources + r.type == "aws_lambda_function" + gate.attribute_read_ok(r, "kms_key_arn") + not gate.planned_unknown(r, "kms_key_arn") + gate.value(r, "kms_key_arn", "") == "" + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "Lambda environment is not encrypted with a customer-managed KMS key", + ) +} + +# METADATA +# title: Deployed code package is verifiable +# description: >- +# Without the inventoried hash or the live hash the deployed package cannot +# be compared, so its integrity is unassessed. +# custom: +# id: package_integrity_unverifiable +# category: input +# severity: HIGH +# nist_controls: [si-7.1] +# ksi_ids: [KSI-SCR-MIT] +violations contains violation if { + some r in packages + gate.attribute_read_ok(r, "code_sha256") + not package_hashes_present(r) + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "Deployed package hash or inventoried hash is missing; integrity is unassessed", + ) +} + +# METADATA +# title: Deployed code package is the inventoried one +# description: >- +# The live function code hash must equal the hash the deploy recorded in the +# inventory; anything else is code the deploy never inventoried or scanned. +# custom: +# id: package_integrity_mismatch +# category: infrastructure +# severity: HIGH +# nist_controls: [si-7, si-7.1] +# ksi_ids: [KSI-SCR-MIT, KSI-SVC-VRI] +violations contains violation if { + some r in packages + package_hashes_present(r) + gate.value(r, "code_sha256", "") != gate.value(r, "expected_code_sha256", "") + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "Deployed function code does not match the package the deploy inventoried", + ) +} + +# METADATA +# title: Notification topics are encrypted +# description: SNS topics must be encrypted at rest with a KMS key. +# custom: +# id: sns_topic_unencrypted +# category: infrastructure +# severity: MEDIUM +# nist_controls: [sc-28] +# ksi_ids: [KSI-SVC-SIN] +violations contains violation if { + some r in gate.resources + r.type == "aws_sns_topic" + gate.attribute_read_ok(r, "kms_master_key_id") + not gate.planned_unknown(r, "kms_master_key_id") + gate.value(r, "kms_master_key_id", "") == "" + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "SNS topic is not encrypted with a KMS key", + ) +} + +# METADATA +# title: Queues are encrypted +# description: SQS queues must use SSE-SQS or a KMS key. +# custom: +# id: sqs_queue_unencrypted +# category: infrastructure +# severity: MEDIUM +# nist_controls: [sc-28] +# ksi_ids: [KSI-SVC-SIN] +violations contains violation if { + some r in gate.resources + r.type == "aws_sqs_queue" + gate.attribute_read_ok(r, "encryption") + not gate.planned_unknown(r, "kms_master_key_id") + gate.value(r, "sqs_managed_sse_enabled", false) != true + gate.value(r, "kms_master_key_id", "") == "" + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "SQS queue is not encrypted (neither SSE-SQS nor a KMS key)", + ) +} + +# METADATA +# title: Tables keep point-in-time recovery +# description: DynamoDB tables must have point-in-time recovery enabled. +# custom: +# id: dynamodb_pitr_disabled +# category: infrastructure +# severity: MEDIUM +# nist_controls: [cp-9] +# ksi_ids: [KSI-RPL-ABO] +violations contains violation if { + some r in gate.resources + r.type == "aws_dynamodb_table" + gate.attribute_read_ok(r, "point_in_time_recovery") + gate.value(r, ["point_in_time_recovery", 0, "enabled"], false) != true + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "DynamoDB table point-in-time recovery is disabled", + ) +} diff --git a/infrastructure/policy/config/data.json b/infrastructure/policy/config/data.json index ce023196..c362d766 100644 --- a/infrastructure/policy/config/data.json +++ b/infrastructure/policy/config/data.json @@ -54,12 +54,28 @@ "TLSv1.2_2018", "TLSv1.2_2019", "TLSv1.2_2021" - ] + ], + "min_days_to_expiry": 30 }, "accessibility": { "fail_on": [ "error" ] + }, + "iam": { + "github_oidc_audience": "sts.amazonaws.com", + "github_oidc_subject_prefix": "repo:sam-aydlette/samaydlette.com:" + }, + "identity": { + "min_password_length": 14 + }, + "logging": { + "min_retention_days": 365 + }, + "api": { + "protected_route_prefixes": [ + "/api" + ] } } } diff --git a/infrastructure/policy/gate.rego b/infrastructure/policy/gate.rego index 1ee22c06..6d4802ae 100644 --- a/infrastructure/policy/gate.rego +++ b/infrastructure/policy/gate.rego @@ -234,6 +234,12 @@ required_config_paths := { ["gate", "tls", "minimum"], ["gate", "tls", "order"], ["gate", "accessibility", "fail_on"], + ["gate", "iam", "github_oidc_audience"], + ["gate", "iam", "github_oidc_subject_prefix"], + ["gate", "identity", "min_password_length"], + ["gate", "logging", "min_retention_days"], + ["gate", "api", "protected_route_prefixes"], + ["gate", "tls", "min_days_to_expiry"], } # ============================================================================= @@ -271,6 +277,7 @@ resource_base(rc) := { "tags": tags_of(rc.change.after, "tags"), "tags_all": tags_of(rc.change.after, "tags_all"), "values": rc.change.after, + "unknown": object.get(rc.change, "after_unknown", {}), } # --- S3 sub-resource joins (hashicorp/aws >= 4.x splits bucket security @@ -348,6 +355,31 @@ plan_resources contains r if { r := resource_base(rc) } +# A plan attribute computed at apply time (e.g. a KMS key ARN for a key created +# in the same apply) is absent from `values` and marked in after_unknown. Rules +# that require an attribute skip it only when the plan says it is unknown; the +# runtime emitter re-evaluates the applied value daily, so an unknown is +# deferred to the live check, never assumed good. Runtime input carries no +# `unknown`, so there the attribute rule always applies. +planned_unknown(r, path) if { + flag := object.get(r, array.concat(["unknown"], as_list(path)), null) + flag == true +} + +# Resource attribute by Terraform attribute path (`values`), with a default. +# The runtime emitter writes live facts under the same Terraform attribute +# names, so one rule reads a plan and a live API response alike. +# A null (Terraform's "unset") reads as the default, like an absent key. +value(r, path, default_value) := v if { + v := object.get(r, array.concat(["values"], as_list(path)), null) + v != null +} else := default_value + +# A single value or a list of values, as a list (IAM documents allow both). +as_list(x) := x if is_array(x) + +else := [x] + # The evaluated resource set, whatever the input shape. default resources := set() diff --git a/infrastructure/policy/gate_test.rego b/infrastructure/policy/gate_test.rego index bf9d7940..79894fe7 100644 --- a/infrastructure/policy/gate_test.rego +++ b/infrastructure/policy/gate_test.rego @@ -89,7 +89,11 @@ test_partial_config_fails_closed if { "required_classification_tags": ["DataSensitivity"], "taggable_types": ["aws_s3_bucket"], "accessibility": {"fail_on": ["error"]}, - "tls": {"minimum": "TLSv1.2_2021"}, + "tls": {"minimum": "TLSv1.2_2021", "min_days_to_expiry": 30}, + "iam": {"github_oidc_audience": "sts.amazonaws.com", "github_oidc_subject_prefix": "repo:o/r:"}, + "identity": {"min_password_length": 14}, + "logging": {"min_retention_days": 365}, + "api": {"protected_route_prefixes": ["/api"]}, }} } diff --git a/infrastructure/policy/iam.rego b/infrastructure/policy/iam.rego new file mode 100644 index 00000000..c6359876 --- /dev/null +++ b/infrastructure/policy/iam.rego @@ -0,0 +1,321 @@ +# ============================================================================= +# IAM POLICY: PRIVILEGE AND TRUST +# ============================================================================= +# Checks IAM roles, their inline policies, IAM groups and the GitHub OIDC +# provider. The same rules read a Terraform plan (deploy gate) and the live +# GetRole / GetRolePolicy / GetGroupPolicy / GetOpenIDConnectProvider answers +# the runtime emitter writes under the same Terraform attribute names +# (`values.assume_role_policy`, `values.policy`, `values.client_id_list`). +# +# Policy documents arrive as JSON strings, exactly as Terraform and the IAM API +# carry them, and are parsed here. A document that does not parse is reported +# as unreadable (category input), never treated as an empty, harmless policy. +# +# Runtime-only facts (no Terraform attribute exists for them on the resource): +# values.attached_policy_arns managed policies attached to a role or group +# values.inline_policies a group's inline policy documents (strings) +# ============================================================================= + +package policy.terraform.iam + +import data.policy.gate + +policy_types := {"aws_iam_role_policy", "aws_iam_policy", "aws_iam_group_policy"} + +# Resources whose managed-policy attachments are checked: roles and groups, and +# the attachment resources the runtime emitter reads (attached_policy_arns). +attachment_holders := { + "aws_iam_role", + "aws_iam_group", + "aws_iam_role_policy_attachment", + "aws_iam_group_policy_attachment", +} + +statements(doc) := gate.as_list(doc.Statement) + +# Every policy document a resource carries, as raw strings. +documents(r) := [p] if { + r.type in policy_types + p := gate.value(r, "policy", null) + is_string(p) +} else := [p | some p in gate.value(r, "inline_policies", []); is_string(p)] if { + r.type == "aws_iam_group" +} else := [] + +# A policy resource whose document is absent (and not merely computed at apply +# time, nor declared unreadable by the runtime emitter) cannot be assessed. +document_missing(r) if { + r.type in policy_types + not is_string(gate.value(r, "policy", null)) + not gate.planned_unknown(r, "policy") + gate.attribute_read_ok(r, "policy") +} + +parsed(raw) := doc if { + doc := json.unmarshal(raw) + is_object(doc) +} + +allows(r) := [s | + some raw in documents(r) + some s in statements(parsed(raw)) + s.Effect == "Allow" +] + +actions(s) := {a | some a in gate.as_list(object.get(s, "Action", []))} + +resources_of(s) := {x | some x in gate.as_list(object.get(s, "Resource", []))} + +document_unreadable(r) if { + some raw in documents(r) + not parsed(raw) +} + +document_unreadable(r) if document_missing(r) + +grants_everything(s) if { + "*" in actions(s) + "*" in resources_of(s) +} + +grants_everything(s) if object.get(s, "NotAction", null) != null + +# --- role trust --------------------------------------------------------------- + +trust_statements(r) := [s | + r.type == "aws_iam_role" + raw := gate.value(r, "assume_role_policy", null) + is_string(raw) + some s in statements(parsed(raw)) + s.Effect == "Allow" +] + +trust_unreadable(r) if { + r.type == "aws_iam_role" + raw := gate.value(r, "assume_role_policy", null) + is_string(raw) + not parsed(raw) +} + +# A role whose trust policy is computed at apply time is checked live instead. +trust_unreadable(r) if { + r.type == "aws_iam_role" + not is_string(gate.value(r, "assume_role_policy", null)) + not gate.planned_unknown(r, "assume_role_policy") + gate.attribute_read_ok(r, "assume_role_policy") +} + +principal(s) := p if { + p := s.Principal + is_object(p) +} else := {} + +public_principal(s) if s.Principal == "*" + +public_principal(s) if "*" in gate.as_list(object.get(principal(s), "AWS", [])) + +github_federated(s) if { + some f in gate.as_list(object.get(principal(s), "Federated", [])) + endswith(f, "oidc-provider/token.actions.githubusercontent.com") +} + +condition_values(s, key) := {v | + some block in object.get(s, "Condition", {}) + some k, val in block + k == key + some v in gate.as_list(val) +} + +github_trust_scoped(s) if { + condition_values(s, "token.actions.githubusercontent.com:aud") == {data.config.gate.iam.github_oidc_audience} + subs := condition_values(s, "token.actions.githubusercontent.com:sub") + count(subs) > 0 + every v in subs { + startswith(v, data.config.gate.iam.github_oidc_subject_prefix) + not contains(v, "*") + } +} + +# METADATA +# title: IAM policy documents parse +# description: An IAM policy document that cannot be parsed cannot be assessed. +# custom: +# id: iam_policy_unreadable +# category: input +# severity: HIGH +# nist_controls: [ac-6] +# ksi_ids: [KSI-IAM-ELP] +violations contains violation if { + some r in gate.resources + document_unreadable(r) + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "IAM policy document could not be parsed; its privileges are unassessed", + ) +} + +# METADATA +# title: No IAM policy grants every action on every resource +# description: >- +# An Allow of Action "*" on Resource "*", or an Allow written with +# NotAction, is administrator access and defeats least privilege. +# custom: +# id: iam_admin_wildcard +# category: infrastructure +# severity: HIGH +# nist_controls: [ac-6] +# ksi_ids: [KSI-IAM-ELP] +violations contains violation if { + some r in gate.resources + some s in allows(r) + grants_everything(s) + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "IAM policy allows every action on every resource (Action/NotAction wildcard)", + ) +} + +# METADATA +# title: No IAM policy grants a whole service on every resource +# description: An Allow of "<service>:*" on Resource "*" grants every action of that service account-wide. +# custom: +# id: iam_service_wildcard +# category: infrastructure +# severity: HIGH +# nist_controls: [ac-6] +# ksi_ids: [KSI-IAM-ELP] +violations contains violation if { + some r in gate.resources + some s in allows(r) + "*" in resources_of(s) + some a in actions(s) + endswith(a, ":*") + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + sprintf("IAM policy allows %s on every resource", [a]), + ) +} + +# METADATA +# title: No administrator policy attached +# description: >- +# The AWS-managed AdministratorAccess policy must not be attached to a role or +# group, whether read on the role or group or on a managed-policy attachment. +# custom: +# id: iam_admin_policy_attached +# category: infrastructure +# severity: HIGH +# nist_controls: [ac-6] +# ksi_ids: [KSI-IAM-ELP, KSI-IAM-JIT] +violations contains violation if { + some r in gate.resources + r.type in attachment_holders + some arn in array.concat( + gate.as_list(gate.value(r, "managed_policy_arns", [])), + gate.as_list(gate.value(r, "attached_policy_arns", [])), + ) + endswith(arn, ":policy/AdministratorAccess") + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "AdministratorAccess is attached", + ) +} + +# METADATA +# title: Role trust policy readable +# description: A role whose trust policy cannot be read cannot be assessed for who may assume it. +# custom: +# id: iam_trust_unreadable +# category: input +# severity: HIGH +# nist_controls: [ac-3] +# ksi_ids: [KSI-IAM-ELP] +violations contains violation if { + some r in gate.resources + trust_unreadable(r) + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "IAM role trust policy is missing or could not be parsed; who may assume it is unassessed", + ) +} + +# METADATA +# title: No role is assumable by anyone +# description: A trust policy must name its principals; "*" lets any AWS account assume the role. +# custom: +# id: iam_trust_public +# category: infrastructure +# severity: HIGH +# nist_controls: [ac-3, ac-6] +# ksi_ids: [KSI-IAM-ELP] +violations contains violation if { + some r in gate.resources + some s in trust_statements(r) + public_principal(s) + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "IAM role trust policy allows any principal (\"*\")", + ) +} + +# METADATA +# title: GitHub OIDC trust pinned to this repository +# description: >- +# A role federated to GitHub Actions must require the STS audience and a +# subject inside this repository with no wildcard, or any workflow in any +# repository could assume it. +# custom: +# id: iam_oidc_trust_unscoped +# category: infrastructure +# severity: HIGH +# nist_controls: [ia-3, ac-6.5] +# ksi_ids: [KSI-IAM-SNU] +violations contains violation if { + some r in gate.resources + some s in trust_statements(r) + github_federated(s) + not github_trust_scoped(s) + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "GitHub OIDC trust is not pinned to the STS audience and a wildcard-free subject in this repository", + ) +} + +# --- OIDC provider ------------------------------------------------------------ + +# METADATA +# title: OIDC provider audience is STS only +# description: The GitHub OIDC provider must accept exactly the STS audience. +# custom: +# id: oidc_audience_unexpected +# category: infrastructure +# severity: HIGH +# nist_controls: [ia-3] +# ksi_ids: [KSI-IAM-SNU] +violations contains violation if { + some r in gate.resources + r.type == "aws_iam_openid_connect_provider" + gate.attribute_read_ok(r, "client_id_list") + not gate.planned_unknown(r, "client_id_list") + {c | some c in gate.value(r, "client_id_list", [])} != {data.config.gate.iam.github_oidc_audience} + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "OIDC provider client ID list is not exactly the STS audience", + ) +} diff --git a/infrastructure/policy/iam_test.rego b/infrastructure/policy/iam_test.rego new file mode 100644 index 00000000..8ca0f599 --- /dev/null +++ b/infrastructure/policy/iam_test.rego @@ -0,0 +1,182 @@ +package iam_test + +import data.policy.terraform.iam + +ids(v) := {x.id | some x in v} + +_res(type, values) := {"resource": {"type": type, "name": "x", "values": values}} + +_doc(statements) := json.marshal({"Version": "2012-10-17", "Statement": statements}) + +_policy(type, statement) := _res(type, {"policy": _doc([statement])}) + +_trust(statement) := _res("aws_iam_role", {"assume_role_policy": _doc([statement])}) + +_github := "arn:aws:iam::123456789012:oidc-provider/token.actions.githubusercontent.com" + +_trust_input(condition) := _trust({ + "Effect": "Allow", + "Action": "sts:AssumeRoleWithWebIdentity", + "Principal": {"Federated": _github}, + "Condition": condition, +}) + +_aud := {"token.actions.githubusercontent.com:aud": "sts.amazonaws.com"} + +_sub_key := "token.actions.githubusercontent.com:sub" + +# --- inline policies --- + +test_scoped_policy_passes if { + stmt := {"Effect": "Allow", "Action": ["s3:GetObject"], "Resource": ["arn:aws:s3:::b/*"]} + count(iam.violations) == 0 with input as _policy("aws_iam_role_policy", stmt) +} + +test_admin_wildcard_fails if { + stmt := {"Effect": "Allow", "Action": "*", "Resource": "*"} + "iam_admin_wildcard" in ids(iam.violations) with input as _policy("aws_iam_role_policy", stmt) +} + +test_allow_not_action_fails if { + stmt := {"Effect": "Allow", "NotAction": "iam:*", "Resource": "*"} + "iam_admin_wildcard" in ids(iam.violations) with input as _policy("aws_iam_policy", stmt) +} + +test_deny_wildcard_passes if { + stmt := {"Effect": "Deny", "Action": "*", "Resource": "*"} + count(iam.violations) == 0 with input as _policy("aws_iam_role_policy", stmt) +} + +test_service_wildcard_on_everything_fails if { + stmt := {"Effect": "Allow", "Action": ["kms:*"], "Resource": "*"} + "iam_service_wildcard" in ids(iam.violations) with input as _policy("aws_iam_role_policy", stmt) +} + +test_service_wildcard_on_one_resource_passes if { + stmt := {"Effect": "Allow", "Action": "s3:*", "Resource": ["arn:aws:s3:::b", "arn:aws:s3:::b/*"]} + count(iam.violations) == 0 with input as _policy("aws_iam_group_policy", stmt) +} + +test_unparseable_policy_is_unassessed if { + "iam_policy_unreadable" in ids(iam.violations) with input as _res("aws_iam_role_policy", {"policy": "{not json"}) +} + +test_missing_policy_is_unassessed if { + "iam_policy_unreadable" in ids(iam.violations) with input as _res("aws_iam_role_policy", {}) +} + +# A document computed at apply time is checked live, not failed at plan time. +test_policy_unknown_at_plan_is_deferred if { + change := {"actions": ["create"], "after": {"name": "x"}, "after_unknown": {"policy": true}} + plan := {"resource_changes": [{ + "address": "aws_iam_role_policy.x", "mode": "managed", + "type": "aws_iam_role_policy", "name": "x", "change": change, + }]} + count(iam.violations) == 0 with input as plan +} + +test_group_inline_policy_checked if { + inline := _doc([{"Effect": "Allow", "Action": "*", "Resource": "*"}]) + values := {"name": "operators", "inline_policies": [inline]} + "iam_admin_wildcard" in ids(iam.violations) with input as _res("aws_iam_group", values) +} + +test_group_admin_attachment_fails if { + values := {"attached_policy_arns": ["arn:aws:iam::aws:policy/AdministratorAccess"]} + "iam_admin_policy_attached" in ids(iam.violations) with input as _res("aws_iam_group", values) +} + +test_attachment_resource_admin_policy_fails if { + values := {"attached_policy_arns": ["arn:aws:iam::aws:policy/AdministratorAccess"]} + "iam_admin_policy_attached" in ids(iam.violations) with input as _res("aws_iam_group_policy_attachment", values) + "iam_admin_policy_attached" in ids(iam.violations) with input as _res("aws_iam_role_policy_attachment", values) +} + +test_attachment_resource_read_only_policy_passes if { + values := {"attached_policy_arns": ["arn:aws:iam::aws:policy/ReadOnlyAccess"]} + count(iam.violations) == 0 with input as _res("aws_iam_role_policy_attachment", values) +} + +test_group_read_only_attachment_passes if { + values := {"attached_policy_arns": ["arn:aws:iam::aws:policy/ReadOnlyAccess"], "inline_policies": []} + count(iam.violations) == 0 with input as _res("aws_iam_group", values) +} + +# --- role trust --- + +test_service_trust_passes if { + stmt := {"Effect": "Allow", "Action": "sts:AssumeRole", "Principal": {"Service": "lambda.amazonaws.com"}} + count(iam.violations) == 0 with input as _trust(stmt) +} + +test_public_trust_fails if { + stmt := {"Effect": "Allow", "Action": "sts:AssumeRole", "Principal": {"AWS": ["*"]}} + "iam_trust_public" in ids(iam.violations) with input as _trust(stmt) +} + +test_star_principal_fails if { + stmt := {"Effect": "Allow", "Action": "sts:AssumeRole", "Principal": "*"} + "iam_trust_public" in ids(iam.violations) with input as _trust(stmt) +} + +test_role_admin_attachment_fails if { + trust := _doc([{"Effect": "Allow", "Principal": {"Service": "lambda.amazonaws.com"}}]) + values := {"assume_role_policy": trust, "attached_policy_arns": ["arn:aws:iam::aws:policy/AdministratorAccess"]} + "iam_admin_policy_attached" in ids(iam.violations) with input as _res("aws_iam_role", values) +} + +test_missing_trust_is_unassessed if { + "iam_trust_unreadable" in ids(iam.violations) with input as _res("aws_iam_role", {"name": "r"}) +} + +test_unparseable_trust_is_unassessed if { + "iam_trust_unreadable" in ids(iam.violations) with input as _res("aws_iam_role", {"assume_role_policy": "nope"}) +} + +# An unreadable attribute is the gate's resource_read_error, not a second finding. +test_trust_read_error_not_duplicated if { + res := {"type": "aws_iam_role", "name": "x", "values": {}, "read_errors": ["assume_role_policy"]} + count(iam.violations) == 0 with input as {"resource": res} +} + +test_github_trust_pinned_passes if { + condition := { + "StringEquals": _aud, + "StringLike": {_sub_key: ["repo:sam-aydlette/samaydlette.com:environment:prod"]}, + } + count(iam.violations) == 0 with input as _trust_input(condition) +} + +test_github_trust_without_subject_fails if { + "iam_oidc_trust_unscoped" in ids(iam.violations) with input as _trust_input({"StringEquals": _aud}) +} + +test_github_trust_other_repository_fails if { + condition := {"StringEquals": object.union(_aud, {_sub_key: "repo:someone-else/fork:ref:refs/heads/main"})} + "iam_oidc_trust_unscoped" in ids(iam.violations) with input as _trust_input(condition) +} + +test_github_trust_wildcard_subject_fails if { + condition := {"StringEquals": _aud, "StringLike": {_sub_key: "repo:sam-aydlette/samaydlette.com:*"}} + "iam_oidc_trust_unscoped" in ids(iam.violations) with input as _trust_input(condition) +} + +test_github_trust_wrong_audience_fails if { + condition := {"StringEquals": { + "token.actions.githubusercontent.com:aud": ["sts.amazonaws.com", "other"], + _sub_key: "repo:sam-aydlette/samaydlette.com:pull_request", + }} + "iam_oidc_trust_unscoped" in ids(iam.violations) with input as _trust_input(condition) +} + +# --- OIDC provider --- + +test_oidc_sts_audience_passes if { + values := {"client_id_list": ["sts.amazonaws.com"]} + count(iam.violations) == 0 with input as _res("aws_iam_openid_connect_provider", values) +} + +test_oidc_extra_audience_fails if { + values := {"client_id_list": ["sts.amazonaws.com", "my-app"]} + "oidc_audience_unexpected" in ids(iam.violations) with input as _res("aws_iam_openid_connect_provider", values) +} diff --git a/infrastructure/policy/identity.rego b/infrastructure/policy/identity.rego new file mode 100644 index 00000000..49a4ef0e --- /dev/null +++ b/infrastructure/policy/identity.rego @@ -0,0 +1,82 @@ +# ============================================================================= +# IDENTITY PROVIDER POLICY (COGNITO USER POOL) +# ============================================================================= +# The user pool gating the Silk Reeling app. Read from the plan's +# aws_cognito_user_pool values at deploy time and from DescribeUserPool, +# written under the same Terraform attribute names, at runtime. +# ============================================================================= + +package policy.terraform.cognito + +import data.policy.gate + +pools contains r if { + some r in gate.resources + r.type == "aws_cognito_user_pool" +} + +# METADATA +# title: User pool requires MFA +# description: Every sign-in to the user pool must require a second factor. +# custom: +# id: cognito_mfa_not_required +# category: infrastructure +# severity: HIGH +# nist_controls: [ia-2.1, ia-2.2] +# ksi_ids: [KSI-IAM-APM] +violations contains violation if { + some r in pools + gate.attribute_read_ok(r, "mfa_configuration") + gate.value(r, "mfa_configuration", "OFF") != "ON" + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "Cognito user pool MFA must be ON (required for every user)", + ) +} + +# METADATA +# title: User pool password length meets the floor +# description: The minimum password length must be at least data.config.gate.identity.min_password_length. +# custom: +# id: cognito_password_too_short +# category: infrastructure +# severity: MEDIUM +# nist_controls: [ia-5.1] +# ksi_ids: [KSI-IAM-APM] +violations contains violation if { + some r in pools + gate.attribute_read_ok(r, "password_policy") + not gate.value(r, ["password_policy", 0, "minimum_length"], 0) >= data.config.gate.identity.min_password_length + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + sprintf( + "Cognito user pool minimum password length must be at least %d", + [data.config.gate.identity.min_password_length], + ), + ) +} + +# METADATA +# title: User pool accounts are provisioned by an administrator +# description: Self sign-up must be off, so every account is created deliberately. +# custom: +# id: cognito_self_signup_enabled +# category: infrastructure +# severity: MEDIUM +# nist_controls: [ac-2] +# ksi_ids: [KSI-IAM-JIT] +violations contains violation if { + some r in pools + gate.attribute_read_ok(r, "admin_create_user_config") + gate.value(r, ["admin_create_user_config", 0, "allow_admin_create_user_only"], false) != true + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "Cognito user pool allows self sign-up; accounts must be created by an administrator", + ) +} diff --git a/infrastructure/policy/keys.rego b/infrastructure/policy/keys.rego new file mode 100644 index 00000000..2cdba4ad --- /dev/null +++ b/infrastructure/policy/keys.rego @@ -0,0 +1,139 @@ +# ============================================================================= +# KEYS, CERTIFICATES AND DNSSEC +# ============================================================================= +# Customer-managed KMS keys (rotation, enabled state), the ACM certificate +# (issued, not about to expire) and the hosted zone's DNSSEC signing status. +# +# Runtime-only facts, written by the emitter where Terraform has no attribute: +# aws_acm_certificate.values.days_to_expiry (whole days from the run to +# DescribeCertificate NotAfter; +# the reader derives it because +# the Wasm host has no time +# builtins) +# aws_route53_zone.values.dnssec_status (GetDNSSEC Status.ServeSignature) +# The plan carries the certificate and zone as data sources without these +# facts, so those two rules bite only on live state. +# ============================================================================= + +package policy.terraform.keys + +import data.policy.gate + +# METADATA +# title: Symmetric KMS keys rotate +# description: Automatic annual rotation must be on for every symmetric customer-managed key. +# custom: +# id: kms_rotation_disabled +# category: infrastructure +# severity: MEDIUM +# nist_controls: [sc-12] +# ksi_ids: [KSI-SVC-ASM] +violations contains violation if { + some r in gate.resources + r.type == "aws_kms_key" + gate.value(r, "customer_master_key_spec", "SYMMETRIC_DEFAULT") == "SYMMETRIC_DEFAULT" + gate.attribute_read_ok(r, "enable_key_rotation") + gate.value(r, "enable_key_rotation", false) != true + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "Symmetric KMS key must have automatic rotation enabled", + ) +} + +# METADATA +# title: KMS keys are enabled +# description: A disabled or pending-deletion key breaks the encryption and signing that depend on it. +# custom: +# id: kms_key_disabled +# category: infrastructure +# severity: HIGH +# nist_controls: [sc-12] +# ksi_ids: [KSI-SVC-ASM] +violations contains violation if { + some r in gate.resources + r.type == "aws_kms_key" + gate.value(r, "is_enabled", true) == false + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "KMS key is disabled or pending deletion", + ) +} + +# METADATA +# title: TLS certificate is issued +# description: The certificate serving the site must be in the ISSUED state. +# custom: +# id: certificate_not_issued +# category: infrastructure +# severity: HIGH +# nist_controls: [sc-8, sc-23] +# ksi_ids: [KSI-SVC-SIN] +violations contains violation if { + some r in gate.resources + r.type == "aws_acm_certificate" + status := gate.value(r, "status", null) + status != null + status != "ISSUED" + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + sprintf("TLS certificate status is %s, not ISSUED", [status]), + ) +} + +# METADATA +# title: TLS certificate is not about to expire +# description: >- +# The certificate must stay valid for at least +# data.config.gate.tls.min_days_to_expiry more days (ACM renews 60 days +# ahead, so a shorter horizon means renewal failed). +# custom: +# id: certificate_expiring +# category: infrastructure +# severity: HIGH +# nist_controls: [sc-8, sc-23] +# ksi_ids: [KSI-SVC-SIN] +violations contains violation if { + some r in gate.resources + r.type == "aws_acm_certificate" + days := gate.value(r, "days_to_expiry", null) + days != null + days < data.config.gate.tls.min_days_to_expiry + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + sprintf( + "TLS certificate expires within %d days", + [data.config.gate.tls.min_days_to_expiry], + ), + ) +} + +# METADATA +# title: Hosted zone answers are DNSSEC-signed +# description: The hosted zone must be serving DNSSEC signatures. +# custom: +# id: dnssec_not_signing +# category: infrastructure +# severity: MEDIUM +# nist_controls: [sc-20, sc-21] +# ksi_ids: [KSI-SVC-SIN] +violations contains violation if { + some r in gate.resources + r.type == "aws_route53_zone" + status := gate.value(r, "dnssec_status", null) + status != null + status != "SIGNING" + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + sprintf("Hosted zone DNSSEC status is %s, not SIGNING", [status]), + ) +} diff --git a/infrastructure/policy/logging.rego b/infrastructure/policy/logging.rego new file mode 100644 index 00000000..3c0b6b68 --- /dev/null +++ b/infrastructure/policy/logging.rego @@ -0,0 +1,163 @@ +# ============================================================================= +# LOGGING, MONITORING AND ALERTING +# ============================================================================= +# CloudWatch log groups (retention, customer-key encryption), the CloudTrail +# trail (logging on, multi-region, log file validation), the alarms that page +# the operator (actions enabled and wired) and the EventBridge schedules that +# drive the monitors (enabled). Plan values at deploy time; Describe* answers +# under the same Terraform attribute names at runtime. +# ============================================================================= + +package policy.terraform.logging + +import data.policy.gate + +trail_logs_everywhere(r) if { + gate.value(r, "enable_logging", true) == true + gate.value(r, "is_multi_region_trail", false) == true +} + +trail_logs_everywhere(r) if not gate.attribute_read_ok(r, "trail") + +alarm_actionable(r) if { + gate.value(r, "actions_enabled", true) == true + count(gate.as_list(gate.value(r, "alarm_actions", []))) > 0 +} + +# METADATA +# title: Log groups keep logs for the retention floor +# description: >- +# A log group with an expiry must keep events at least +# data.config.gate.logging.min_retention_days (0, never expire, passes). +# custom: +# id: log_retention_below_minimum +# category: infrastructure +# severity: MEDIUM +# nist_controls: [au-11] +# ksi_ids: [KSI-MLA-OSM] +violations contains violation if { + some r in gate.resources + r.type == "aws_cloudwatch_log_group" + days := gate.value(r, "retention_in_days", 0) + days > 0 + days < data.config.gate.logging.min_retention_days + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + sprintf( + "Log group retention is %d days, below the %d-day floor", + [days, data.config.gate.logging.min_retention_days], + ), + ) +} + +# METADATA +# title: Log groups are encrypted with a customer-managed key +# description: Log events must be encrypted at rest under a customer-managed KMS key. +# custom: +# id: log_group_not_cmk +# category: infrastructure +# severity: MEDIUM +# nist_controls: [au-9] +# ksi_ids: [KSI-MLA-OSM] +violations contains violation if { + some r in gate.resources + r.type == "aws_cloudwatch_log_group" + gate.attribute_read_ok(r, "kms_key_id") + not gate.planned_unknown(r, "kms_key_id") + gate.value(r, "kms_key_id", "") == "" + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "Log group is not encrypted with a customer-managed KMS key", + ) +} + +# METADATA +# title: The audit trail is logging +# description: The CloudTrail trail must be logging, across all regions. +# custom: +# id: trail_not_logging +# category: infrastructure +# severity: HIGH +# nist_controls: [au-12] +# ksi_ids: [KSI-MLA-LET] +violations contains violation if { + some r in gate.resources + r.type == "aws_cloudtrail" + not trail_logs_everywhere(r) + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "CloudTrail trail must be logging and multi-region", + ) +} + +# METADATA +# title: The audit trail validates its log files +# description: CloudTrail log file integrity validation must be on. +# custom: +# id: trail_log_validation_disabled +# category: infrastructure +# severity: MEDIUM +# nist_controls: [si-7] +# ksi_ids: [KSI-SVC-VRI] +violations contains violation if { + some r in gate.resources + r.type == "aws_cloudtrail" + gate.attribute_read_ok(r, "trail") + gate.value(r, "enable_log_file_validation", false) != true + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "CloudTrail log file validation must be enabled", + ) +} + +# METADATA +# title: Alarms can page +# description: An alarm must have its actions enabled and at least one alarm action. +# custom: +# id: alarm_not_actionable +# category: infrastructure +# severity: MEDIUM +# nist_controls: [si-4] +# ksi_ids: [KSI-MLA-RVL] +violations contains violation if { + some r in gate.resources + r.type == "aws_cloudwatch_metric_alarm" + gate.attribute_read_ok(r, "alarm_actions") + not gate.planned_unknown(r, "alarm_actions") + not alarm_actionable(r) + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "Alarm has its actions disabled or no alarm action to notify", + ) +} + +# METADATA +# title: Monitoring schedules are enabled +# description: The EventBridge rules that run the monitors must be enabled. +# custom: +# id: schedule_disabled +# category: infrastructure +# severity: MEDIUM +# nist_controls: [ca-7] +# ksi_ids: [KSI-MLA-EVC] +violations contains violation if { + some r in gate.resources + r.type == "aws_cloudwatch_event_rule" + gate.value(r, "state", "ENABLED") != "ENABLED" + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + sprintf("EventBridge rule state is %s, not ENABLED", [gate.value(r, "state", "")]), + ) +} diff --git a/infrastructure/policy/main.rego b/infrastructure/policy/main.rego index 367c2c24..06b1b58c 100644 --- a/infrastructure/policy/main.rego +++ b/infrastructure/policy/main.rego @@ -122,6 +122,7 @@ resource_reports := [report | "kind": "infrastructure", "resource_type": r.type, "resource_name": r.name, + "address": address, "compliant": count(violations_for(r)) == 0, "violations": violations_for(r), "policy_version": policy_version, diff --git a/infrastructure/policy/network.rego b/infrastructure/policy/network.rego new file mode 100644 index 00000000..92aebfc9 --- /dev/null +++ b/infrastructure/policy/network.rego @@ -0,0 +1,118 @@ +# ============================================================================= +# API GATEWAY AND FUNCTION ENDPOINTS +# ============================================================================= +# The HTTP API fronting the Silk Reeling app: its stage must log access and +# throttle, and its API routes must require authorization. A Lambda function +# URL with no auth would bypass all of that, so none may exist. +# +# Runtime-only fact: aws_lambda_function.values.function_url_auth_type +# (GetFunctionUrlConfig AuthType; absent when the function has no URL). +# ============================================================================= + +package policy.terraform.network + +import data.policy.gate + +route_path(r) := path if { + parts := split(gate.value(r, "route_key", ""), " ") + count(parts) == 2 + path := parts[1] +} + +public_function_url(r) if { + r.type == "aws_lambda_function_url" + gate.value(r, "authorization_type", "") == "NONE" +} + +public_function_url(r) if { + r.type == "aws_lambda_function" + gate.value(r, "function_url_auth_type", "") == "NONE" +} + +# METADATA +# title: API stage writes access logs +# description: Every API Gateway stage must send access logs to a log group. +# custom: +# id: apigw_access_logging_disabled +# category: infrastructure +# severity: MEDIUM +# nist_controls: [au-12] +# ksi_ids: [KSI-MLA-LET] +violations contains violation if { + some r in gate.resources + r.type == "aws_apigatewayv2_stage" + not gate.planned_unknown(r, ["access_log_settings", 0, "destination_arn"]) + gate.value(r, ["access_log_settings", 0, "destination_arn"], "") == "" + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "API Gateway stage has no access log destination", + ) +} + +# METADATA +# title: API stage throttles requests +# description: Every API Gateway stage must set a default route rate limit. +# custom: +# id: apigw_unthrottled +# category: infrastructure +# severity: MEDIUM +# nist_controls: [sc-5] +# ksi_ids: [KSI-CNA-RVP] +violations contains violation if { + some r in gate.resources + r.type == "aws_apigatewayv2_stage" + not gate.value(r, ["default_route_settings", 0, "throttling_rate_limit"], 0) > 0 + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "API Gateway stage has no default route throttling rate limit", + ) +} + +# METADATA +# title: API routes require authorization +# description: >- +# A route under one of data.config.gate.api.protected_route_prefixes must +# carry an authorizer (authorization_type other than NONE). +# custom: +# id: apigw_route_unauthorized +# category: infrastructure +# severity: HIGH +# nist_controls: [ac-3] +# ksi_ids: [KSI-IAM-ELP] +violations contains violation if { + some r in gate.resources + r.type == "aws_apigatewayv2_route" + some prefix in data.config.gate.api.protected_route_prefixes + startswith(route_path(r), prefix) + gate.value(r, "authorization_type", "NONE") == "NONE" + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + sprintf("API route %s has no authorizer", [gate.value(r, "route_key", "")]), + ) +} + +# METADATA +# title: No unauthenticated function URL +# description: A Lambda function URL with auth type NONE exposes the function to the internet, bypassing the API. +# custom: +# id: lambda_public_function_url +# category: infrastructure +# severity: HIGH +# nist_controls: [sc-7] +# ksi_ids: [KSI-CNA-ULN] +violations contains violation if { + some r in gate.resources + public_function_url(r) + violation := gate.make_violation( + rego.metadata.rule().custom, + r.name, + gate.address_of(r), + "Lambda function URL allows unauthenticated invocation (auth type NONE)", + ) +} diff --git a/infrastructure/policy/s3.rego b/infrastructure/policy/s3.rego index 7808baef..0243ac65 100644 --- a/infrastructure/policy/s3.rego +++ b/infrastructure/policy/s3.rego @@ -25,7 +25,7 @@ import data.policy.gate # id: versioning_disabled # category: infrastructure # severity: MEDIUM -# nist_controls: [cp-9, cp-10, si-12] +# nist_controls: [cp-9, cp-10] # ksi_ids: [KSI-RPL-ABO] violations contains violation if { some r in gate.resources diff --git a/infrastructure/policy/services_test.rego b/infrastructure/policy/services_test.rego new file mode 100644 index 00000000..082365fb --- /dev/null +++ b/infrastructure/policy/services_test.rego @@ -0,0 +1,337 @@ +package services_test + +import data.policy.terraform.cognito +import data.policy.terraform.compute +import data.policy.terraform.keys +import data.policy.terraform.logging +import data.policy.terraform.network + +ids(v) := {x.id | some x in v} + +_res(type, values) := {"resource": {"type": type, "name": "x", "values": values}} + +_plan(type, after, unknown) := {"resource_changes": [{ + "address": sprintf("%s.x", [type]), "mode": "managed", "type": type, "name": "x", + "change": {"actions": ["create"], "after": after, "after_unknown": unknown}, +}]} + +# --- Cognito --- + +_pool := { + "mfa_configuration": "ON", + "password_policy": [{"minimum_length": 14}], + "admin_create_user_config": [{"allow_admin_create_user_only": true}], +} + +test_pool_compliant if { + count(cognito.violations) == 0 with input as _res("aws_cognito_user_pool", _pool) +} + +test_pool_optional_mfa_fails if { + "cognito_mfa_not_required" in ids(cognito.violations) with input as _res( + "aws_cognito_user_pool", + object.union(_pool, {"mfa_configuration": "OPTIONAL"}), + ) +} + +test_pool_short_password_fails if { + "cognito_password_too_short" in ids(cognito.violations) with input as _res( + "aws_cognito_user_pool", + object.union(_pool, {"password_policy": [{"minimum_length": 8}]}), + ) +} + +test_pool_self_signup_fails if { + "cognito_self_signup_enabled" in ids(cognito.violations) with input as _res( + "aws_cognito_user_pool", + object.union(_pool, {"admin_create_user_config": [{"allow_admin_create_user_only": false}]}), + ) +} + +# --- KMS, ACM, DNSSEC --- + +test_kms_symmetric_rotating_passes if { + count(keys.violations) == 0 with input as _res("aws_kms_key", {"enable_key_rotation": true, "is_enabled": true}) +} + +test_kms_symmetric_not_rotating_fails if { + "kms_rotation_disabled" in ids(keys.violations) with input as _res("aws_kms_key", {"enable_key_rotation": false}) +} + +test_kms_asymmetric_rotation_not_required if { + count(keys.violations) == 0 with input as _res("aws_kms_key", {"customer_master_key_spec": "ECC_NIST_P256"}) +} + +test_kms_disabled_fails if { + "kms_key_disabled" in ids(keys.violations) with input as _res( + "aws_kms_key", + {"customer_master_key_spec": "ECC_NIST_P256", "is_enabled": false}, + ) +} + +test_certificate_issued_and_valid_passes if { + count(keys.violations) == 0 with input as _res( + "aws_acm_certificate", + {"status": "ISSUED", "days_to_expiry": 175}, + ) +} + +test_certificate_not_issued_fails if { + "certificate_not_issued" in ids(keys.violations) with input as _res("aws_acm_certificate", {"status": "EXPIRED"}) +} + +test_certificate_expiring_fails if { + "certificate_expiring" in ids(keys.violations) with input as _res( + "aws_acm_certificate", + {"status": "ISSUED", "days_to_expiry": 15}, + ) +} + +test_dnssec_signing_passes if { + count(keys.violations) == 0 with input as _res("aws_route53_zone", {"dnssec_status": "SIGNING"}) +} + +test_dnssec_not_signing_fails if { + "dnssec_not_signing" in ids(keys.violations) with input as _res( + "aws_route53_zone", + {"dnssec_status": "NOT_SIGNING"}, + ) +} + +# --- logging --- + +test_log_group_compliant if { + count(logging.violations) == 0 with input as _res( + "aws_cloudwatch_log_group", + {"retention_in_days": 365, "kms_key_id": "arn:k"}, + ) +} + +test_log_group_short_retention_fails if { + "log_retention_below_minimum" in ids(logging.violations) with input as _res( + "aws_cloudwatch_log_group", + {"retention_in_days": 30, "kms_key_id": "arn:k"}, + ) +} + +test_log_group_no_cmk_fails if { + "log_group_not_cmk" in ids(logging.violations) with input as _res( + "aws_cloudwatch_log_group", + {"retention_in_days": 0}, + ) +} + +test_log_group_cmk_unknown_at_plan_deferred if { + count(logging.violations) == 0 with input as _plan( + "aws_cloudwatch_log_group", + {"retention_in_days": 365, "kms_key_id": null}, + {"kms_key_id": true}, + ) +} + +test_log_group_null_cmk_in_plan_fails if { + "log_group_not_cmk" in ids(logging.violations) with input as _plan( + "aws_cloudwatch_log_group", + {"retention_in_days": 365, "kms_key_id": null}, + {}, + ) +} + +_trail := {"enable_logging": true, "is_multi_region_trail": true, "enable_log_file_validation": true} + +test_trail_compliant if { + count(logging.violations) == 0 with input as _res("aws_cloudtrail", _trail) +} + +test_trail_stopped_fails if { + "trail_not_logging" in ids(logging.violations) with input as _res( + "aws_cloudtrail", + object.union(_trail, {"enable_logging": false}), + ) +} + +test_trail_single_region_fails if { + "trail_not_logging" in ids(logging.violations) with input as _res( + "aws_cloudtrail", + object.union(_trail, {"is_multi_region_trail": false}), + ) +} + +test_trail_no_validation_fails if { + "trail_log_validation_disabled" in ids(logging.violations) with input as _res( + "aws_cloudtrail", + object.union(_trail, {"enable_log_file_validation": false}), + ) +} + +test_trail_unreadable_reports_only_read_error if { + count(logging.violations) == 0 with input as {"resource": { + "type": "aws_cloudtrail", "name": "x", + "values": {}, "read_errors": ["trail"], + }} +} + +test_alarm_actionable_passes if { + count(logging.violations) == 0 with input as _res( + "aws_cloudwatch_metric_alarm", + {"actions_enabled": true, "alarm_actions": ["arn:sns"]}, + ) +} + +test_alarm_actions_disabled_fails if { + "alarm_not_actionable" in ids(logging.violations) with input as _res( + "aws_cloudwatch_metric_alarm", + {"actions_enabled": false, "alarm_actions": ["arn:sns"]}, + ) +} + +test_alarm_without_action_fails if { + "alarm_not_actionable" in ids(logging.violations) with input as _res( + "aws_cloudwatch_metric_alarm", + {"alarm_actions": []}, + ) +} + +test_alarm_unreadable_reports_only_read_error if { + res := {"type": "aws_cloudwatch_metric_alarm", "name": "x", "values": {}, "read_errors": ["alarm_actions"]} + count(logging.violations) == 0 with input as {"resource": res} +} + +test_schedule_enabled_passes if { + count(logging.violations) == 0 with input as _res("aws_cloudwatch_event_rule", {"state": "ENABLED"}) +} + +test_schedule_disabled_fails if { + "schedule_disabled" in ids(logging.violations) with input as _res( + "aws_cloudwatch_event_rule", + {"state": "DISABLED"}, + ) +} + +# --- API Gateway, function URLs --- + +_stage := { + "access_log_settings": [{"destination_arn": "arn:logs"}], + "default_route_settings": [{"throttling_rate_limit": 20, "throttling_burst_limit": 10}], +} + +test_stage_compliant if { + count(network.violations) == 0 with input as _res("aws_apigatewayv2_stage", _stage) +} + +test_stage_without_access_log_fails if { + "apigw_access_logging_disabled" in ids(network.violations) with input as _res( + "aws_apigatewayv2_stage", + object.union(_stage, {"access_log_settings": []}), + ) +} + +test_stage_unthrottled_fails if { + "apigw_unthrottled" in ids(network.violations) with input as _res( + "aws_apigatewayv2_stage", + object.union(_stage, {"default_route_settings": [{}]}), + ) +} + +test_api_route_with_jwt_passes if { + count(network.violations) == 0 with input as _res( + "aws_apigatewayv2_route", + {"route_key": "ANY /api/{proxy+}", "authorization_type": "JWT"}, + ) +} + +test_api_route_without_auth_fails if { + "apigw_route_unauthorized" in ids(network.violations) with input as _res( + "aws_apigatewayv2_route", + {"route_key": "GET /api/data"}, + ) +} + +test_default_route_may_be_public if { + count(network.violations) == 0 with input as _res( + "aws_apigatewayv2_route", + {"route_key": "$default", "authorization_type": "NONE"}, + ) +} + +test_public_function_url_fails if { + "lambda_public_function_url" in ids(network.violations) with input as _res( + "aws_lambda_function", + {"function_url_auth_type": "NONE"}, + ) +} + +test_public_function_url_resource_fails if { + "lambda_public_function_url" in ids(network.violations) with input as _res( + "aws_lambda_function_url", + {"authorization_type": "NONE"}, + ) +} + +test_iam_function_url_passes if { + count(network.violations) == 0 with input as _res("aws_lambda_function", {"function_url_auth_type": "AWS_IAM"}) +} + +# --- functions, packages, messaging --- + +test_function_env_cmk_passes if { + count(compute.violations) == 0 with input as _res("aws_lambda_function", {"kms_key_arn": "arn:k"}) +} + +test_function_env_without_cmk_fails if { + "lambda_env_not_cmk" in ids(compute.violations) with input as _res("aws_lambda_function", {}) +} + +test_package_matches_passes if { + count(compute.violations) == 0 with input as _res( + "lambda_deployment_package", + {"code_sha256": "abc=", "expected_code_sha256": "abc="}, + ) +} + +test_package_drift_fails if { + "package_integrity_mismatch" in ids(compute.violations) with input as _res( + "lambda_deployment_package", + {"code_sha256": "new=", "expected_code_sha256": "abc="}, + ) +} + +test_package_without_inventoried_hash_unassessed if { + "package_integrity_unverifiable" in ids(compute.violations) with input as _res( + "lambda_deployment_package", + {"code_sha256": "abc="}, + ) +} + +test_topic_encrypted_passes if { + count(compute.violations) == 0 with input as _res("aws_sns_topic", {"kms_master_key_id": "arn:k"}) +} + +test_topic_unencrypted_fails if { + "sns_topic_unencrypted" in ids(compute.violations) with input as _res("aws_sns_topic", {}) +} + +test_queue_sse_sqs_passes if { + count(compute.violations) == 0 with input as _res("aws_sqs_queue", {"sqs_managed_sse_enabled": true}) +} + +test_queue_unencrypted_fails if { + "sqs_queue_unencrypted" in ids(compute.violations) with input as _res( + "aws_sqs_queue", + {"sqs_managed_sse_enabled": false}, + ) +} + +test_table_pitr_passes if { + count(compute.violations) == 0 with input as _res( + "aws_dynamodb_table", + {"point_in_time_recovery": [{"enabled": true}]}, + ) +} + +test_table_without_pitr_fails if { + "dynamodb_pitr_disabled" in ids(compute.violations) with input as _res( + "aws_dynamodb_table", + {"point_in_time_recovery": [{"enabled": false}]}, + ) +} diff --git a/infrastructure/schemas/assessor-record.schema.json b/infrastructure/schemas/assessor-record.schema.json index bd992c27..4b152eb7 100644 --- a/infrastructure/schemas/assessor-record.schema.json +++ b/infrastructure/schemas/assessor-record.schema.json @@ -2,7 +2,7 @@ "$schema": "https://json-schema.org/draft/2020-12/schema", "$id": "https://samaydlette.com/schemas/assessor-record.schema.json", "title": "Assessor record (REQ-ASR-1)", - "description": "A finding, summary or comment written and signed by an assessor. The signature is ECDSA P-256 with SHA-256 over the canonical form of the record without its \"signature\" member: keys sorted, separators \",\" and \":\" with no whitespace, UTF-8, non-ASCII characters unescaped. The signer must be the assessor identity pinned at infrastructure/keys/assessor-identity.json. The provider never edits a record; outputs carry its text verbatim with the signature.", + "description": "A finding, summary or comment written and signed by an assessor. The signature is ECDSA P-256 with SHA-256 over the canonical form of the record without its \"signature\" member: keys sorted, separators \",\" and \":\" with no whitespace, UTF-8, non-ASCII characters unescaped. The signer must be the assessor identity pinned at infrastructure/keys/assessor-identity.json. The provider never edits a record; outputs carry its text verbatim with the signature. A keyless assessor (pinned identity algorithm SIGSTORE_KEYLESS) instead signs one set file holding all its records with Sigstore, and each record carries algorithm SIGSTORE_KEYLESS_SET.", "type": "object", "additionalProperties": false, "required": ["record_type", "schema_version", "record_id", "assessor", "issued_at", "kind", "text", "signature"], @@ -28,8 +28,9 @@ "additionalProperties": false, "required": ["algorithm", "value"], "properties": { - "algorithm": {"const": "ECDSA_P256_SHA256"}, - "value": {"type": "string", "minLength": 1, "description": "Base64 DER signature."} + "algorithm": {"enum": ["ECDSA_P256_SHA256", "SIGSTORE_KEYLESS_SET"]}, + "value": {"type": "string", "minLength": 1, "description": "Base64 DER signature (ECDSA_P256_SHA256), or the hex sha256 of the record's canonical form (SIGSTORE_KEYLESS_SET)."}, + "signed_set": {"type": "string", "minLength": 1, "description": "SIGSTORE_KEYLESS_SET only: the name of the Sigstore-signed set file holding this record."} } } } diff --git a/infrastructure/schemas/ccm-calendar.json b/infrastructure/schemas/ccm-calendar.json new file mode 100644 index 00000000..55ab4988 --- /dev/null +++ b/infrastructure/schemas/ccm-calendar.json @@ -0,0 +1,34 @@ +{ + "$comment": "The quarterly Collaborative Continuous Monitoring calendar (CCM-OCR-SOR, CCM-QTR-SAR). Fixed Ongoing Certification Report issue dates, about 3 months apart, placed late in the second month of each quarter (about day 55), away from the beginning, middle and end of the quarter. Each Quarterly Review is a fixed number of business days after its report, counted over the federal holidays listed here. scripts/_ccm.py validates this file (fail-closed) and every report, the CPO and the review calendar file read their dates from it; nothing computes a date from 'now'. Extend the issue dates and holidays before the calendar runs out: the build fails when fewer than two issue dates lie ahead.", + "schema": "ccm-calendar/1", + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "rationale": "Issue on a Tuesday late in each quarter's middle month: a fixed, predictable cycle that is spread out from the start, middle and end of each quarter, as CCM-OCR-SOR asks. The review follows 5 business days later, inside the 3-to-10 business day window of CCM-QTR-SAR, leaving time to read the report first.", + "ocr_issue_dates": [ + "2026-11-24", + "2027-02-23", + "2027-05-25", + "2027-08-24", + "2027-11-23", + "2028-02-29", + "2028-05-30", + "2028-08-29", + "2028-11-28" + ], + "review_business_days_after_issue": 5, + "review_start_utc": "17:00", + "review_duration_minutes": 45, + "holidays": { + "source": "U.S. federal holidays (5 U.S.C. 6103), observed dates", + "covers_through": "2028-12-31", + "dates": [ + "2026-01-01", "2026-01-19", "2026-02-16", "2026-05-25", "2026-06-19", "2026-07-03", "2026-09-07", + "2026-10-12", "2026-11-11", "2026-11-26", "2026-12-25", + "2027-01-01", "2027-01-18", "2027-02-15", "2027-05-31", "2027-06-18", "2027-07-05", "2027-09-06", + "2027-10-11", "2027-11-11", "2027-11-25", "2027-12-24", "2027-12-31", + "2028-01-17", "2028-02-21", "2028-05-29", "2028-06-19", "2028-07-04", "2028-09-04", "2028-10-09", + "2028-11-10", "2028-11-23", "2028-12-25" + ] + } +} diff --git a/infrastructure/schemas/check-vectors.json b/infrastructure/schemas/check-vectors.json index e99ce330..decf53e2 100644 --- a/infrastructure/schemas/check-vectors.json +++ b/infrastructure/schemas/check-vectors.json @@ -1,223 +1,250 @@ { "$schema": "./check-vectors.schema.json", "version": "1.0", - "description": "Governed CVSS 3.1 base vectors for configuration checks, which carry no CVE and so no published vector. One vector per check ID, decided once by a named person and reviewed by a date; the VDR builder applies it to every finding of that check. It drives PAIN (CVSS-Environmental) and LEV (Figure 7: the floor, and the no-direct-impact rule). An entry without decided_by and decided_on is a proposal and is NOT in force; an entry past review_by lapses. Vectors marked AI-drafted were proposed for operator review.", + "description": "Governed CVSS 3.1 base vectors for configuration checks, which carry no CVE and so no published vector. One vector per check ID, decided once by a named person and reviewed by a date; the VDR builder applies it to every finding of that check. It drives PAIN (CVSS-Environmental) and LEV (Figure 7: the floor, and the no-direct-impact rule). An entry without decided_by and decided_on is a proposal and is NOT in force; an entry past review_by lapses. Vectors marked AI-drafted were proposed for operator review. A decided entry names the decision record that adopted it (decision); one whose record is missing or not in force fails the build.", "vectors": { "AVD-AWS-0015": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "CloudTrail logs SSE-S3 instead of a customer-managed key: encrypted at rest; key custody only.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "AVD-AWS-0089": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "Bucket access logging off: reduces detection only.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "AVD-AWS-0132": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "SSE-S3 instead of a customer-managed key: data is encrypted at rest; key custody choice only.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "AVD-AWS-0162": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "CloudTrail not streamed to CloudWatch Logs: reduces alerting only.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV2_AWS_10": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "CloudTrail not streamed to CloudWatch Logs: trail still written; reduces alerting only.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV2_AWS_47": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "No Log4j WAF managed rule: no Log4j in the stack, so the absent rule protects nothing exploitable.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV2_AWS_56": { "vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H", "rationale": "Administrator policy on the operator group: a compromised operator credential controls the account.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV2_AWS_62": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "S3 event notifications off: reduces detection only.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV_AWS_115": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "rationale": "No reserved concurrency: a request flood can exhaust account concurrency for other functions.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV_AWS_117": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "Lambda outside a VPC: network-isolation depth; the function's own permissions bound what it reaches.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV_AWS_119": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "DynamoDB default encryption instead of a customer-managed key: encrypted at rest; key custody only.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV_AWS_144": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "S3 cross-region replication off: resilience only.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV_AWS_145": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "SSE-S3 instead of a customer-managed key: data is encrypted at rest; key custody choice only.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV_AWS_174": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "No Log4j-specific WAF rule: no Log4j in the stack, so the absent rule protects nothing exploitable.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV_AWS_18": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "S3 access logging off on a log-target bucket: reduces detection; gives an attacker no capability.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV_AWS_23": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "S3 event notifications off: reduces detection only.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV_AWS_252": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "CloudTrail SNS delivery notifications off: no consumer; no attacker capability.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV_AWS_272": { "vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N", "rationale": "No code signing: a holder of deploy rights can ship unsigned code.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV_AWS_287": { "vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N", "rationale": "Secrets metadata reads on a wildcard: a holder of the role can list secret metadata, not values.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV_AWS_310": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "CloudFront origin failover absent: resilience only.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV_AWS_35": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "CloudTrail logs SSE-S3 instead of a customer-managed key: encrypted at rest; key custody only.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV_AWS_355": { "vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N", "rationale": "Wildcard resource in a read-only assessment policy: a holder of the role can read more metadata than needed.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV_AWS_356": { "vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N", "rationale": "Wildcard resource for account-level enumeration: a holder of the role can enumerate the account.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV_AWS_374": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "CloudFront geo restriction off on a public site: no capability beyond the site's intended exposure.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV_AWS_50": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "Lambda X-Ray tracing off: observability only.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV_AWS_68": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "rationale": "No WAF on a public distribution: request floods and application attacks meet no edge filter; availability impact.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" }, "CKV_AWS_86": { "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "rationale": "CloudFront origin failover absent: resilience only.", "drafted_by": "AI-drafted for operator review", - "decided_by": null, - "decided_on": null, - "review_by": "2027-11-03" + "decided_by": "Sam Aydlette", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "decision": "DEC-180" } } } diff --git a/infrastructure/schemas/check-vectors.schema.json b/infrastructure/schemas/check-vectors.schema.json index 33f6f926..01c28f74 100644 --- a/infrastructure/schemas/check-vectors.schema.json +++ b/infrastructure/schemas/check-vectors.schema.json @@ -58,6 +58,11 @@ "review_by": { "type": "string", "format": "date" + }, + "decision": { + "type": "string", + "pattern": "^DEC-\\d{3}$", + "description": "The decision record that adopted the vector; required once decided." } } } diff --git a/infrastructure/schemas/decisions.schema.json b/infrastructure/schemas/decisions.schema.json index a7fdcb71..f8389e7a 100644 --- a/infrastructure/schemas/decisions.schema.json +++ b/infrastructure/schemas/decisions.schema.json @@ -25,16 +25,34 @@ "status": {"enum": ["in-force", "closed"]}, "disposition": { "enum": ["false-positive", "risk-accepted", "accepted", "operational-requirement", "mitigated", - "vendor-dependency", "under-investigation", "remediate", "remediated"], - "description": "risk-accepted and false-positive records may suppress configuration-scanner checks; the vulnerability gate passes false-positive, accepted, operational-requirement, mitigated and vendor-dependency; under-investigation and remediate are recorded but do not pass." + "vendor-dependency", "under-investigation", "remediate", "remediated", "superseded"], + "description": "risk-accepted and false-positive records may suppress configuration-scanner checks; the vulnerability gate passes false-positive, accepted, operational-requirement, mitigated and vendor-dependency; under-investigation and remediate are recorded but do not pass. A closed record is remediated (it settled a finding) or superseded (the decision was replaced; replaced_by says by what)." }, "justification": {"type": "string", "minLength": 1}, "decided_by": {"type": "string", "minLength": 1}, "decided_on": {"$ref": "#/$defs/date"}, "review_by": {"$ref": "#/$defs/date"}, "closed_on": {"$ref": "#/$defs/date"}, + "confirmed_on": {"$ref": "#/$defs/date", "description": "The date the operator confirmed the decision. Required in force: an unconfirmed draft confers nothing. Who drafted the wording, when not the operator, is source.drafted_by; neither note belongs in the title or justification."}, + "replaced_by": {"type": "string", "minLength": 1, "description": "For a superseded record: what replaces the decision (a mechanism, a workflow step, a newer record)."}, "original_detection_date": {"$ref": "#/$defs/date"}, "planned_completion": {"type": "string"}, + "planned_reduction": { + "type": "object", + "description": "The next planned reduction in Potential Agency Impact (VER-RPT-VDT): the date it is expected and the rating it brings the finding to. Published as the finding's projectedNextReduction in place of the remediation deadline. In-force records only.", + "required": ["date", "target_pain"], + "properties": {"date": {"$ref": "#/$defs/date"}, "target_pain": {"type": "string", "pattern": "^N[0-5]$"}}, + "additionalProperties": false + }, + "automatable": { + "type": "object", + "description": "VER-EVA-AIA: whether exploitation of the findings this record covers can be automated. Exploitation is assumed automatable; only a record carrying the evidence sets it to no.", + "required": ["value"], + "properties": {"value": {"enum": ["yes", "no"]}, "evidence": {"type": "string"}}, + "additionalProperties": false, + "if": {"properties": {"value": {"const": "no"}}}, + "then": {"required": ["value", "evidence"], "properties": {"evidence": {"minLength": 1}}} + }, "remediation_plan": {"type": "string"}, "vendor_dependency": {"type": ["string", "boolean", "object"]}, "point_of_contact": {"type": "string"}, @@ -49,15 +67,19 @@ "additionalProperties": false }, "vuln_fields": {"type": "object", "description": "Vulnerability-specific fields copied onto the gate's entry (e.g. mitigation: a mitigation record ID)."}, - "source": {"type": "object"} + "source": {"type": "object", "properties": {"drafted_by": {"type": "string", "minLength": 1}}} }, "additionalProperties": false, "allOf": [ {"if": {"properties": {"status": {"const": "in-force"}}}, - "then": {"required": ["decided_by", "decided_on", "review_by"], - "properties": {"disposition": {"not": {"const": "remediated"}}}}}, + "then": {"required": ["decided_by", "decided_on", "review_by", "confirmed_on"], + "properties": {"disposition": {"not": {"enum": ["remediated", "superseded"]}}}, + "not": {"required": ["replaced_by"]}}}, {"if": {"properties": {"status": {"const": "closed"}}}, - "then": {"properties": {"disposition": {"const": "remediated"}}}} + "then": {"properties": {"disposition": {"enum": ["remediated", "superseded"]}}, + "not": {"required": ["planned_reduction"]}}}, + {"if": {"properties": {"disposition": {"const": "superseded"}}, "required": ["disposition"]}, + "then": {"required": ["closed_on", "replaced_by"]}} ] } } diff --git a/infrastructure/schemas/detection-feeds.json b/infrastructure/schemas/detection-feeds.json index 0dddab5a..c8e90f1b 100644 --- a/infrastructure/schemas/detection-feeds.json +++ b/infrastructure/schemas/detection-feeds.json @@ -1,11 +1,11 @@ { "$schema": "./detection-feeds.schema.json", - "version": "2026-11-04.1", + "version": "2026-11-05.1", "description": "What G7 (detection) requires of every input the VDR build reads: present, well-formed and, where the source dates itself, no older than max_age_hours. Read by scripts/detection-gate.py, which fails closed on a missing or invalid file. Each feed's mode (block or detect-and-recover) is in gate-modes.json under detection.<feed>.", "decided_by": "Sam Aydlette", - "decided_on": "2026-11-04", - "review_by": "2027-11-04", - "rationale": "KEV: CISA releases the catalog on weekdays when entries change, not daily; 14 days tolerates quiet periods without missing a release cycle. EPSS: FIRST publishes daily; 3 days tolerates a missed publication. Grype DB: Anchore builds daily; 5 days matches Grype's own default maximum database age. The remaining feeds carry no source date and must simply be present and well-formed; DAST's 14-day window is the builder's --zap-max-age-days.", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "rationale": "KEV: CISA releases the catalog on weekdays when entries change, not daily; 14 days tolerates quiet periods without missing a release cycle. EPSS: FIRST publishes daily; 3 days tolerates a missed publication. Grype DB: Anchore builds daily; 5 days matches Grype's own default maximum database age. The remaining feeds carry no source date and must simply be present and well-formed; the site DAST window is the builder's --zap-max-age-days (3 days, VDR-TFR-PSD Class C). CodeQL: analysed on every push and PR to main, after every deploy and daily; 72 hours is the Class C 3-day sample-detection cadence (VDR-TFR-PSD), and every listed category (this repository's Python, JavaScript and Actions code, and the Silk Reeling app's Python and JavaScript) must have been analysed in it. ZAP API: the authenticated scan of the Silk Reeling API runs daily and after every deploy; 72 hours is the same 3-day cadence.", "feeds": { "kev": {"max_age_hours": 336, "source_date": "dateReleased"}, "epss": {"max_age_hours": 72, "source_date": "score_date in the file's header line"}, @@ -13,6 +13,10 @@ "dependabot": {"source_date": null}, "previous-vdr": {"source_date": null}, "checkov": {"source_date": null}, - "tfsec": {"source_date": null} + "tfsec": {"source_date": null}, + "codeql": {"max_age_hours": 72, "source_date": "created_at of the newest analysis on main of each required category", + "categories": ["/language:python", "/language:javascript-typescript", "/language:actions", + "/silk-reeling/language:python", "/silk-reeling/language:javascript-typescript"]}, + "zap-api": {"max_age_hours": 72, "source_date": "@generated in the authenticated API scan report"} } } diff --git a/infrastructure/schemas/detection-feeds.schema.json b/infrastructure/schemas/detection-feeds.schema.json index 9299f7d1..08305823 100644 --- a/infrastructure/schemas/detection-feeds.schema.json +++ b/infrastructure/schemas/detection-feeds.schema.json @@ -16,7 +16,7 @@ "feeds": { "type": "object", "additionalProperties": false, - "required": ["kev", "epss", "grype", "dependabot", "previous-vdr", "checkov", "tfsec"], + "required": ["kev", "epss", "grype", "dependabot", "previous-vdr", "checkov", "tfsec", "codeql", "zap-api"], "patternProperties": { "^[a-z-]+$": { "type": "object", @@ -24,7 +24,8 @@ "required": ["source_date"], "properties": { "max_age_hours": {"type": "number", "exclusiveMinimum": 0, "maximum": 8760}, - "source_date": {"type": ["string", "null"]} + "source_date": {"type": ["string", "null"]}, + "categories": {"type": "array", "minItems": 1, "items": {"type": "string", "minLength": 1}} } } } diff --git a/infrastructure/schemas/freshness-config.json b/infrastructure/schemas/freshness-config.json index 7d02d3de..51c6388f 100644 --- a/infrastructure/schemas/freshness-config.json +++ b/infrastructure/schemas/freshness-config.json @@ -75,6 +75,30 @@ "signature": ".well-known/vdr-history.bundle", "note": "CR26 historical vulnerability activity (VER-TFR-MRH; Class C SHOULD update at least every 14 days), rebuilt from every VDR report." }, + { + "path": ".well-known/vdr-monthly.json", + "cadence": "nightly", + "max_age_hours": 24, + "timestamp": { + "source": "json", + "field": "generatedAt" + }, + "signed": true, + "signature": ".well-known/vdr-monthly.bundle", + "note": "Monthly vulnerability detection and response activity report, month to date (VER-TFR-MHR, VER-RPT-HLO, VER-RPT-PER), rebuilt from every VDR report." + }, + { + "path": ".well-known/vdr-non-machine-vv.json", + "cadence": "nightly", + "max_age_hours": 26, + "timestamp": { + "source": "json", + "field": "verifiedAt" + }, + "signed": true, + "signature": ".well-known/vdr-non-machine-vv.bundle", + "note": "Non-machine verification and validation (VDR-TFR-NMV): machine checks of every resource in data/non-machine-resources.json (scripts/_nonmachine.py), run by the deploy (enforced) and the evidence nightly (twice a day). verifiedAt is the run's time when every check passes and the epoch when any fails, so a failing check turns this window red at once; 26 hours means nightly runs have been missed. No verification is manual." + }, { "path": ".well-known/vdr-status.json", "cadence": "nightly", @@ -86,6 +110,30 @@ "signed": false, "note": "The nightly's status beacon. Unsigned and not evidence; listed because the watchdog pages on its age. The nightly runs twice a day, so 26 hours means runs have been missed." }, + { + "path": ".well-known/incident-reports.json", + "cadence": "nightly", + "max_age_hours": 24, + "timestamp": { + "source": "json", + "field": "emitted_at" + }, + "signed": true, + "signature": ".well-known/incident-reports.bundle", + "note": "The incident log (IEC-CSO-EFR) and, through it, every incident report it lists with its sha256. Rebuilt by .github/workflows/incident-reports.yml on every change to data/incidents.json and twice a day, and by every deploy. The report deadlines themselves are hours, so the watchdog also pages on each listed report past its deadline (IncidentReportsOverdue)." + }, + { + "path": ".well-known/incident-deliveries.json", + "cadence": "nightly", + "max_age_hours": 24, + "timestamp": { + "source": "json", + "field": "emitted_at" + }, + "signed": true, + "signature": ".well-known/incident-deliveries.bundle", + "note": "SIMULATION: the delivery log of every incident report to a simulated FedRAMP and agency recipient; nothing is sent. Rebuilt with the incident log by every deploy and by .github/workflows/incident-reports.yml." + }, { "path": ".well-known/ksi-signal-runtime.json", "cadence": "runtime", @@ -149,16 +197,17 @@ { "path": ".well-known/ongoing-certification-report.json", "cadence": "deploy", - "max_age_hours": 720, + "max_age_hours": 336, "timestamp": { "source": "json", - "field": "emitted_at" + "field": "metadata.lastUpdated" }, "signed": true, - "signature": ".well-known/ongoing-certification-report.bundle" + "signature": ".well-known/ongoing-certification-report.bundle", + "note": "Rebuilt on every deploy and daily by package-maintenance.yml at the deployed commit; 14 days is CPO-CSX-CPM's Class C maximum, so the watchdog pages before the package falls out of date." }, { - "path": ".well-known/certification-overview-package.json", + "path": ".well-known/availability.json", "cadence": "deploy", "max_age_hours": 720, "timestamp": { @@ -166,39 +215,40 @@ "field": "emitted_at" }, "signed": true, - "signature": ".well-known/certification-overview-package.bundle" + "signature": ".well-known/availability.bundle" }, { - "path": ".well-known/availability.json", + "path": ".well-known/policy-index.json", "cadence": "deploy", "max_age_hours": 720, "timestamp": { - "source": "json", - "field": "emitted_at" + "source": "last_modified" }, "signed": true, - "signature": ".well-known/availability.bundle" + "signature": ".well-known/policy-index.bundle" }, { - "path": ".well-known/policy-index.json", + "path": ".well-known/minimum-assessment-scope.json", "cadence": "deploy", "max_age_hours": 720, "timestamp": { - "source": "last_modified" + "source": "json", + "field": "generated_at" }, "signed": true, - "signature": ".well-known/policy-index.bundle" + "signature": ".well-known/minimum-assessment-scope.bundle" }, { "path": ".well-known/security-decision-record.json", "cadence": "deploy", - "max_age_hours": 720, + "max_age_hours": 336, "timestamp": { "source": "json", - "field": "metadata.last_updated" + "field": "metadata.lastUpdated" }, "signed": true, - "signature": ".well-known/security-decision-record.bundle" + "signature": ".well-known/security-decision-record.bundle", + "note": "Rebuilt on every deploy and daily by package-maintenance.yml at the deployed commit; 14 days is CPO-CSX-CPM's Class C maximum, so the watchdog pages before the package falls out of date." }, { "path": ".well-known/security-decision-record.json.intoto.jsonl", @@ -212,13 +262,130 @@ { "path": ".well-known/certification-package-overview.json", "cadence": "deploy", + "max_age_hours": 336, + "timestamp": { + "source": "json", + "field": "metadata.lastUpdated" + }, + "signed": true, + "signature": ".well-known/certification-package-overview.bundle", + "note": "Rebuilt on every deploy and daily by package-maintenance.yml at the deployed commit; 14 days is CPO-CSX-CPM's Class C maximum, so the watchdog pages before the package falls out of date." + }, + { + "path": ".well-known/ocr-issues.json", + "cadence": "nightly", + "max_age_hours": 336, + "timestamp": { + "source": "json", + "field": "generated_at" + }, + "signed": true, + "signature": ".well-known/ocr-issues.bundle", + "note": "Index of the issued Ongoing Certification Reports and their snapshots (CCM-OCR-AVL, CDS-CSO-HAD). Only package-maintenance.yml writes it, on its daily schedule and when every deploy calls it (job package-maintainer); cadence 'nightly', the scheduled unattended run, because the maintainer is what writes it. The issues (ocr-issue-<date>.*) and snapshots (snapshot-<date>.json, snapshots/<date>/) it lists are immutable by design, so they carry no freshness window: the index records each one's sha256." + }, + { + "path": ".well-known/vdr-audit-log-review.json", + "cadence": "nightly", + "max_age_hours": 26, + "timestamp": { + "source": "json", + "field": "generated_at" + }, + "signed": true, + "signature": ".well-known/vdr-audit-log-review.bundle", + "note": "The automated audit-log review (KSI-MLA-RVL, KSI-CMT-RVP; DEC-195): CloudTrail write events and GitHub's record of main since the previous review, judged by rule, with a planted simulated intruder caught every run (scripts/audit-log-review.py). Written by evidence-nightly.yml, its only writer, twice a day; 26 hours means nightly runs have been missed." + }, + { + "path": ".well-known/vdr-recovery-exercises.json", + "cadence": "nightly", + "max_age_hours": 26, + "timestamp": { + "source": "json", + "field": "generated_at" + }, + "signed": true, + "signature": ".well-known/vdr-recovery-exercises.bundle", + "note": "Index of the monthly recovery exercises (KSI-RPL-TRC; DEC-195), rewritten on every evidence nightly run (scripts/hold-recovery-exercise.py), its only writer. Each exercise (vdr-recovery-exercise-<date>.*) is immutable and listed with its sha256, so it carries no window; the nightly and the deploy fail from the day after a due date with none published (scripts/check-scheduled-review.py)." + }, + { + "path": ".well-known/security-reviews.json", + "cadence": "nightly", + "max_age_hours": 336, + "timestamp": { + "source": "json", + "field": "generated_at" + }, + "signed": true, + "signature": ".well-known/security-reviews.bundle", + "note": "Index of the Annual Security Reviews (KSI-PIY-RIS/RES, KSI-SVC-EIS, KSI-INR-RPI; DEC-195) and the rules-of-behavior acknowledgements (PL-4), rewritten daily by package-maintenance.yml (its only writer, so cadence 'nightly', the scheduled unattended run), with the same 14-day window as the package it maintains. Each review (security-review-<date>.*) is immutable and listed with its sha256. The deploy and the evidence nightly fail from the day after a due date with no review in it (scripts/check-scheduled-review.py)." + }, + { + "path": ".well-known/quarterly-reviews.json", + "cadence": "nightly", + "max_age_hours": 336, + "timestamp": { + "source": "json", + "field": "generated_at" + }, + "signed": true, + "signature": ".well-known/quarterly-reviews.bundle", + "note": "Index of the Quarterly Reviews held with simulated attendees (CCM-QTR-MTG, CCM-QTR-RTR; DEC-194), rewritten daily by package-maintenance.yml (its only writer, so cadence 'nightly', the scheduled unattended run) from the first review date on. The reviews (quarterly-review-<date>.*) it lists are immutable by design, so they carry no freshness window: the index records each one's sha256. The deploy and the evidence nightly fail when a review date has passed with no review in it (scripts/check-quarterly-review.py)." + }, + { + "path": ".well-known/quarterly-review.ics", + "cadence": "deploy", + "max_age_hours": 336, + "timestamp": { + "source": "last_modified" + }, + "signed": false, + "note": "Quarterly Review calendar file (CCM-QTR-REG), from the CCM calendar; written by the deploy and daily by package-maintenance.yml. Not signed: the same dates are in the signed CPO and OCR." + }, + { + "path": ".well-known/fedramp-certification-reports.json", + "cadence": "deploy", + "max_age_hours": 720, + "timestamp": { + "source": "json", + "field": "generated_at" + }, + "signed": true, + "signature": ".well-known/fedramp-certification-reports.bundle", + "note": "Index of FedRAMP Certification Reports published unmodified (CDS-CSO-FRC). FedRAMP is simulated: the one report is a stand-in." + }, + { + "path": ".well-known/package-submission-log.json", + "cadence": "deploy", + "max_age_hours": 720, + "timestamp": { + "source": "json", + "field": "generated_at" + }, + "signed": true, + "signature": ".well-known/package-submission-log.bundle", + "note": "Log of the simulated submission of the certification package to FedRAMP on each deploy (FRC-CSO-PKG). Nothing is sent." + }, + { + "path": ".well-known/secure-configuration-guide.json", + "cadence": "deploy", "max_age_hours": 720, "timestamp": { "source": "json", - "field": "metadata.last_updated" + "field": "emitted_at" + }, + "signed": true, + "signature": ".well-known/secure-configuration-guide.bundle" + }, + { + "path": ".well-known/security-settings.json", + "cadence": "deploy", + "max_age_hours": 720, + "timestamp": { + "source": "json", + "field": "emitted_at" }, "signed": true, - "signature": ".well-known/certification-package-overview.bundle" + "signature": ".well-known/security-settings.bundle" }, { "path": ".well-known/boundary-map.json", @@ -276,6 +443,125 @@ "signed": true, "signature": ".well-known/conformance-results.bundle", "note": "The conformance suite's results for the method profile (REQ-GOV-2), run, signed and published by the deploy." + }, + { + "path": ".well-known/access-summary.json", + "cadence": "deploy", + "max_age_hours": 720, + "timestamp": { + "source": "json", + "field": "emitted_at" + }, + "signed": true, + "signature": ".well-known/access-summary.bundle", + "note": "Monthly aggregate counts of access to the certification data (CDS-TRC-ACL), rebuilt from the CloudFront access records on every deploy." + }, + { + "path": ".well-known/assessor-guide.json", + "cadence": "deploy", + "max_age_hours": 720, + "timestamp": { + "source": "json", + "field": "generated_at" + }, + "signed": true, + "signature": ".well-known/assessor-guide.bundle", + "note": "How to verify and validate each FedRAMP rule and KSI, generated from the rule records on every deploy (IVV-CSO-STE, IVV-CSO-DUS); the simulated assessor runs its checks." + }, + { + "path": ".well-known/simulated-assessment.json", + "cadence": "deploy", + "max_age_hours": 720, + "timestamp": { + "source": "json", + "field": "issued_at" + }, + "signed": true, + "signature": ".well-known/simulated-assessment.bundle", + "note": "The simulated assessor's signed result set (not a FedRAMP Recognized assessment), produced on every deploy and signed by the simulated-assessor.yml workflow identity, not the deploy's." + }, + { + "path": ".well-known/frr-evidence.json", + "cadence": "deploy", + "max_age_hours": 720, + "timestamp": { + "source": "json", + "field": "generated_at" + }, + "signed": true, + "signature": ".well-known/frr-evidence.bundle", + "note": "Per rule record, whether each test it cites passed in the build that published it (FRC-CSX-VVR)." + }, + { + "path": ".well-known/agency-access-exercise.json", + "cadence": "deploy", + "max_age_hours": 720, + "timestamp": { + "source": "json", + "field": "generated_at" + }, + "signed": true, + "signature": ".well-known/agency-access-exercise.bundle", + "note": "The agency access procedure run on every deploy against fictional agencies, including the 5-business-day denial clock (CDS-TRC-AAI, CDS-UTC-AAD)." + }, + { + "path": ".well-known/trust-manifest.json", + "cadence": "deploy", + "max_age_hours": 720, + "timestamp": { + "source": "json", + "field": "generated_at" + }, + "signed": true, + "signature": ".well-known/trust-manifest.bundle", + "note": "The signed index of all certification data with media types, signatures and human-readable forms (CDS-TRC-PAC)." + }, + { + "path": ".well-known/fedramp-inbox-simulation.json", + "cadence": "deploy", + "max_age_hours": 720, + "timestamp": { + "source": "json", + "field": "emitted_at" + }, + "signed": true, + "signature": ".well-known/fedramp-inbox-simulation.bundle", + "note": "SIMULATION: the FedRAMP Security Inbox is simulated for this proof of concept; this is the deploy's run of the inbox logic over synthetic messages." + }, + { + "path": ".well-known/significant-change-notifications.json", + "cadence": "deploy", + "max_age_hours": 720, + "timestamp": { + "source": "json", + "field": "generated_at" + }, + "signed": true, + "signature": ".well-known/significant-change-notifications.bundle", + "note": "Significant Change Notifications index (SCN-CSO-HIS/HRM/NOM), rebuilt every deploy from docs/scn/scn-register.csv; never pruned." + }, + { + "path": ".well-known/significant-change-notifications.atom", + "cadence": "deploy", + "max_age_hours": 720, + "timestamp": { + "source": "last_modified" + }, + "signed": true, + "signature": ".well-known/significant-change-notifications.atom.bundle", + "note": "Atom feed of the SCN notices (SCN-CSO-NOM); its <updated> is the last notice's date, so the object's last-modified time is used." + }, + { + "path": ".well-known/scn-evaluations.json", + "cadence": "deploy", + "max_age_hours": 720, + "timestamp": { + "source": "json", + "field": "generated_at" + }, + "signed": true, + "signature": ".well-known/scn-evaluations.bundle", + "note": "Append-only significant-change evaluation log (SCN-CSO-MAR), one entry per change merged to main." } ] } diff --git a/infrastructure/schemas/frr-records.schema.json b/infrastructure/schemas/frr-records.schema.json new file mode 100644 index 00000000..5d22a352 --- /dev/null +++ b/infrastructure/schemas/frr-records.schema.json @@ -0,0 +1,69 @@ +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "$id": "https://samaydlette.com/schemas/frr-records.schema.json", + "title": "FedRAMP rule records (SDR-CSO-FRR)", + "description": "One record per FedRAMP rule applicable to 20x Program Class C. scripts/_frr.py enforces this shape and what a schema cannot: the record set equals the applicable rules in the pinned corpus, every evidence reference resolves, and 'optional' is used only for MAY rules.", + "type": "object", + "additionalProperties": false, + "required": ["schema", "basis", "records"], + "properties": { + "$comment": {"type": "string"}, + "schema": {"const": "frr-records/1"}, + "basis": {"type": "string", "minLength": 1}, + "records": { + "type": "array", + "items": { + "type": "object", + "additionalProperties": false, + "required": ["frr_id", "status", "implementation"], + "properties": { + "frr_id": {"type": "string", "pattern": "^[A-Z]{3}-[A-Z]{3}-[A-Z]{3}$"}, + "status": {"enum": ["Implemented", "Partially Implemented", "Not Implemented", "Not Applicable"]}, + "implementation": {"type": "string", "minLength": 1}, + "evidence": { + "type": "array", + "items": { + "type": "object", + "additionalProperties": false, + "required": ["kind", "ref"], + "properties": { + "kind": {"enum": ["test", "step", "artifact", "decision"]}, + "ref": {"type": "string", "minLength": 1} + } + } + }, + "gap": {"type": "string", "minLength": 1}, + "not_applicable": {"type": "string", "minLength": 1, "description": "Why the rule does not apply: FedRAMP scopes it to a step the provider is not taking, or it is a MAY permission not exercised."}, + "may_rationale": {"type": "string", "minLength": 1, "description": "Required on, and only on, MAY rules: why the provider did or didn't exercise the permission."}, + "simulated": { + "type": "object", + "additionalProperties": false, + "required": ["counterparty", "how"], + "description": "The outside party this proof of concept simulates; Implemented records only, with deploy-time evidence.", + "properties": { + "counterparty": {"enum": ["assessor", "fedramp", "agency", "incident-recipient", "mail", "sam-gov", "personnel"]}, + "how": {"type": "string", "minLength": 1} + } + }, + "closes_with": { + "type": "array", + "minItems": 1, + "uniqueItems": true, + "items": {"enum": ["W2", "W3", "W4", "W5", "W6", "W7", "W8", "W9", "W10", "sam"]} + } + }, + "if": {"properties": {"status": {"const": "Implemented"}}}, + "then": { + "required": ["evidence"], + "properties": {"evidence": {"minItems": 1}}, + "not": {"anyOf": [{"required": ["gap"]}, {"required": ["closes_with"]}]} + }, + "else": { + "if": {"properties": {"status": {"const": "Not Applicable"}}}, + "then": {"required": ["not_applicable"], "not": {"anyOf": [{"required": ["gap"]}, {"required": ["closes_with"]}, {"required": ["simulated"]}]}}, + "else": {"required": ["gap", "closes_with"], "not": {"anyOf": [{"required": ["not_applicable"]}, {"required": ["simulated"]}]}} + } + } + } + } +} diff --git a/infrastructure/schemas/gate-modes.json b/infrastructure/schemas/gate-modes.json index d1e87bc2..78b45570 100644 --- a/infrastructure/schemas/gate-modes.json +++ b/infrastructure/schemas/gate-modes.json @@ -1,7 +1,7 @@ { "$schema": "./gate-modes.schema.json", - "version": "2026-11-04.3", - "description": "The mode each gate check runs in, and the decision behind it (REQ-GAT-1, REQ-GAT-4). The method's default is block. A detect-and-recover check publishes its failure, queues it and starts a recovery clock instead of stopping the run. Read by scripts/_gates.py, which fails the build on a missing decision field, a non-default mode with no reason or a lapsed review date, or an unrecorded check.", + "version": "2026-11-06.2", + "description": "The mode each gate check runs in, and the decision behind it (REQ-GAT-1, REQ-GAT-4). The method's default is block. A detect-and-recover check publishes its failure, queues it and starts a recovery clock instead of stopping the run. Read by scripts/_gates.py, which fails the build on a missing decision field (an entry needs confirmed_on: an unconfirmed mode is not in force), a non-default mode with no reason or a lapsed review date, or an unrecorded check.", "method_reference": "website/research/vulnerability-evidence.html#gates", "checks": [ { @@ -12,14 +12,18 @@ "reason": "Stricter than the method. G1 blocks every known-exploited finding, dispositioned or not, from the first evaluation; the method blocks only once the KEV due date has passed or when a new resource would deploy with one.", "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", - "review_by": "2027-11-04" + "review_by": "2027-11-04", + "confirmed_on": "2026-11-04" }, {"check": "vdr.top-impact-lev-irv", "gate": "G2", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, {"check": "vdr.past-deadline", "gate": "G3", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, {"check": "vuln-gate.unhandled", "gate": "G3", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, { "check": "runtime-divergence.diverged", "gate": "G4", @@ -28,28 +32,43 @@ "reason": "A deploy may proceed past a fresh divergence only with --allow-divergence and a stated reason, which the deploy log records (break-glass for a deploy that is itself the fix).", "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", - "review_by": "2027-11-04" + "review_by": "2027-11-04", + "confirmed_on": "2026-11-04" }, {"check": "reconcile.a", "gate": "G4", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, {"check": "reconcile.b", "gate": "G5", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, {"check": "reconcile.c", "gate": "G5", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, {"check": "reconcile.d", "gate": "G5", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, {"check": "reconcile.h", "gate": "G5", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, {"check": "reconcile.i", "gate": "G5", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, {"check": "reconcile.j", "gate": "G5", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, {"check": "reconcile.e", "gate": "G6", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, {"check": "reconcile.f", "gate": "G6", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, {"check": "reconcile.l", "gate": "G6", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, + {"check": "reconcile.m", "gate": "G5", "mode": "block", "method_default": "block", + "reason": "An open incident naming a finding the VDR does not carry blocks, like every other cross-artifact invariant.", + "decided_by": "Sam Aydlette", "decided_on": "2026-11-05", "review_by": "2027-11-05", + "confirmed_on": "2026-11-06", "drafted_by": "AI-drafted (Claude), with the incident register"}, { "check": "reconcile.i.unreadable", "gate": "G7", @@ -58,7 +77,8 @@ "reason": "Was a rollout-time warning while the roles lacked tag:GetResources. Both roles now read tags (the deploy and the nightly both report invariant i checked), so a denied read is a detection failure and blocks.", "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", - "review_by": "2027-11-04" + "review_by": "2027-11-04", + "confirmed_on": "2026-11-04" }, { "check": "runtime-divergence.observer-fault", @@ -68,25 +88,56 @@ "reason": "The runtime evaluator could not reach a verdict: its signal is unreadable, stale, undated, degraded or has no divergence block. Blocking deploys on it would also block the deploy that repairs the evaluator. The fault is published in the runtime signal and queued by the trust center (runtime_unassessed, runtime_stale) with its opening time.", "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", - "review_by": "2027-05-04" + "review_by": "2027-05-04", + "confirmed_on": "2026-11-04" }, {"check": "detection.zap.missing", "gate": "G7", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, {"check": "detection.zap.stale", "gate": "G7", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, {"check": "detection.kev", "gate": "G7", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, {"check": "detection.epss", "gate": "G7", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, {"check": "detection.grype", "gate": "G7", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, {"check": "detection.dependabot", "gate": "G7", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, {"check": "detection.previous-vdr", "gate": "G7", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, {"check": "detection.checkov", "gate": "G7", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"}, + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, {"check": "detection.tfsec", "gate": "G7", "mode": "block", "method_default": "block", - "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04"} + "decided_by": "Sam Aydlette", "decided_on": "2026-11-04", "review_by": "2027-11-04", + "confirmed_on": "2026-11-04"}, + {"check": "detection.codeql", "gate": "G7", "mode": "block", "method_default": "block", + "decided_by": "Sam Aydlette", "decided_on": "2026-11-05", "review_by": "2027-11-05", + "confirmed_on": "2026-11-05"}, + {"check": "detection.zap-api", "gate": "G7", "mode": "block", "method_default": "block", + "decided_by": "Sam Aydlette", "decided_on": "2026-11-05", "review_by": "2027-11-05", + "confirmed_on": "2026-11-05"}, + {"check": "vdr.coverage", "gate": "G7", "mode": "detect-and-recover", "method_default": "block", + "reason": "An inventory component with no detection technique in the last month (VDR-TFR-PCD) is a gap in detection, not a vulnerability in what is deployed; blocking would also block the deploy that adds the detection. The gap becomes a process finding (VDR-CSO-FAV) with a clock and a deadline, published in the VDR until coverage returns.", + "decided_by": "Sam Aydlette", "decided_on": "2026-11-05", "review_by": "2027-05-05", + "confirmed_on": "2026-11-06", "drafted_by": "AI-drafted (Claude)"}, + {"check": "vdr.unresolved-component", "gate": "G7", "mode": "detect-and-recover", "method_default": "block", + "reason": "A finding that resolves to no inventory component is rated at the fail-safe (internet-reachable, most sensitive) until it is resolved (VER-EVA-EIR); blocking would also block the inventory change that resolves it. The unresolved evaluation becomes a process finding (VDR-CSO-FAV) with a clock and a deadline until every finding resolves.", + "decided_by": "Sam Aydlette", "decided_on": "2026-11-05", "review_by": "2027-05-05", + "confirmed_on": "2026-11-06", "drafted_by": "AI-drafted (Claude)"}, + {"check": "audit-log.unexpected", "gate": "G7", "mode": "detect-and-recover", "method_default": "block", + "reason": "A write by an unexpected principal, or a change to main, a workflow, a ruleset or an environment outside a merged pull request, is a signal about the operating process, not a defect in what is deployed; blocking would stop the evidence refresh that publishes it. It becomes a process finding (VDR-CSO-FAV) with a clock and a deadline, and an automated incident evaluation in vdr-audit-log-review.json, for as long as it is in the review's window (scripts/audit-log-review.py). One evaluated reportable is stopped by audit-log.reportable.", + "decided_by": "Sam Aydlette", "decided_on": "2026-11-06", "review_by": "2027-05-06", + "confirmed_on": "2026-11-06", "drafted_by": "AI-drafted (Claude)"}, + {"check": "audit-log.reportable", "gate": "G7", "mode": "block", "method_default": "block", + "decided_by": "Sam Aydlette", "decided_on": "2026-11-06", "review_by": "2027-11-06", + "confirmed_on": "2026-11-06", "drafted_by": "AI-drafted (Claude)"} ] } diff --git a/infrastructure/schemas/gate-modes.schema.json b/infrastructure/schemas/gate-modes.schema.json index e5aab056..d3970983 100644 --- a/infrastructure/schemas/gate-modes.schema.json +++ b/infrastructure/schemas/gate-modes.schema.json @@ -17,7 +17,7 @@ "items": { "type": "object", "additionalProperties": false, - "required": ["check", "gate", "mode", "method_default", "decided_by", "decided_on", "review_by"], + "required": ["check", "gate", "mode", "method_default", "decided_by", "decided_on", "review_by", "confirmed_on"], "properties": { "check": {"type": "string", "pattern": "^[a-z0-9-]+(\\.[a-z0-9-]+)+$"}, "gate": {"enum": ["G1", "G2", "G3", "G4", "G5", "G6", "G7"]}, @@ -26,7 +26,9 @@ "reason": {"type": "string", "minLength": 1}, "decided_by": {"type": "string", "minLength": 1}, "decided_on": {"type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$"}, - "review_by": {"type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$"} + "review_by": {"type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$"}, + "confirmed_on": {"type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "When the operator confirmed the mode; required: an unconfirmed mode is not in force."}, + "drafted_by": {"type": "string", "minLength": 1, "description": "Who drafted the wording, when not the operator (e.g. AI-drafted)."} }, "if": {"properties": {"mode": {"const": "detect-and-recover"}}}, "then": {"required": ["reason"]} diff --git a/infrastructure/schemas/incidents.schema.json b/infrastructure/schemas/incidents.schema.json new file mode 100644 index 00000000..d933d0d4 --- /dev/null +++ b/infrastructure/schemas/incidents.schema.json @@ -0,0 +1,107 @@ +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "$id": "incidents.schema.json", + "title": "Incident register", + "description": "data/incidents.json: every incident, its FedRAMP reportability evaluation (IEC-CSO-EFR), its Incident Rating estimates (IEC-CSO-EFI; until one exists the IEC-CSO-DPR default applies) and the Initial, Ongoing and Final reports issued (IEC-CSO-IIR/OIR/FIR). scripts/_incidents.py enforces these rules at build time without a jsonschema dependency, plus the ones a schema cannot state: IDs are unique; times are in order (started, detected, evaluated, each report); an estimate's rating is the IEC-CSO-EFI rating for its customer effect and agency count; the first report is Initial and sets the description, and a Final report is last and follows recovery; a vulnerability basis is an adopted rule and names a finding; nothing is dated after now; and no account ID or outside email address appears.", + "type": "object", + "required": ["schema", "policy", "incidents"], + "properties": { + "$comment": {"type": "string"}, + "schema": {"const": "incidents/1"}, + "policy": {"$ref": "#/$defs/policy"}, + "incidents": {"type": "array", "items": {"$ref": "#/$defs/incident"}} + }, + "additionalProperties": false, + "$defs": { + "text": {"type": "string", "minLength": 1, "pattern": "\\S"}, + "date": {"type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$"}, + "time": {"type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(\\.\\d+)?(Z|[+-]\\d{2}:\\d{2})$"}, + "texts": {"type": "array", "items": {"$ref": "#/$defs/text"}, "uniqueItems": true}, + "policy": { + "type": "object", + "required": ["federal_incident_coordinator", "notification", "notification_text", "adopted_vulnerability_rules", + "federal_customer_data", "decided_by", "decided_on", "review_by"], + "properties": { + "federal_incident_coordinator": {"$ref": "#/$defs/text", "description": "Who coordinates federal incident response and how to reach them (IEC-CSO-IIR item 1)."}, + "notification": {"enum": ["published-only"], "description": "How reports reach all affected parties. Only publication under /.well-known/ is built; sending is the operator's decision."}, + "notification_text": {"$ref": "#/$defs/text"}, + "adopted_vulnerability_rules": {"type": "array", "items": {"enum": ["VER-TFR-IRI", "VER-TFR-NRI"]}, "uniqueItems": true, "description": "Which of VER-TFR-IRI (SHOULD) and VER-TFR-NRI (MAY) the operator applies."}, + "federal_customer_data": {"$ref": "#/$defs/text", "description": "What would be federal customer data (FRD-FCD) for this offering."}, + "decided_by": {"$ref": "#/$defs/text"}, + "decided_on": {"$ref": "#/$defs/date"}, + "review_by": {"$ref": "#/$defs/date"} + }, + "additionalProperties": false + }, + "incident": { + "type": "object", + "required": ["id", "title", "exercise", "started_at", "detected_at", "detection_source", "evaluation", "estimates", "reports"], + "properties": { + "id": {"type": "string", "pattern": "^INC-\\d{4}-\\d{3}$"}, + "title": {"$ref": "#/$defs/text"}, + "exercise": {"type": "boolean", "description": "true for a simulated incident run to exercise the process."}, + "started_at": {"$ref": "#/$defs/time"}, + "detected_at": {"$ref": "#/$defs/time"}, + "detection_source": {"$ref": "#/$defs/text"}, + "evaluation": { + "type": "object", + "required": ["evaluated_at", "reportable", "basis", "reason", "federal_customer_data_considered"], + "properties": { + "evaluated_at": {"$ref": "#/$defs/time"}, + "reportable": {"type": "boolean"}, + "basis": {"enum": ["IEC-CSO-EFR", "VER-TFR-IRI", "VER-TFR-NRI"]}, + "reason": {"$ref": "#/$defs/text"}, + "federal_customer_data_considered": {"$ref": "#/$defs/text"} + }, + "additionalProperties": false + }, + "findings": {"$ref": "#/$defs/texts", "description": "VDR tracking IDs or CVE IDs the incident is about."}, + "estimates": {"type": "array", "items": { + "type": "object", + "required": ["estimated_at", "rating", "customer_effect", "agencies", "reason"], + "properties": { + "estimated_at": {"$ref": "#/$defs/time"}, + "rating": {"type": "integer", "minimum": 1, "maximum": 5}, + "customer_effect": {"enum": ["minimal", "narrow", "disruptive", "debilitating"]}, + "agencies": {"enum": ["single", "multiple"]}, + "reason": {"$ref": "#/$defs/text"} + }, + "additionalProperties": false + }}, + "reports": {"type": "array", "items": { + "type": "object", + "required": ["type", "at"], + "properties": { + "type": {"enum": ["Initial", "Ongoing", "Final"]}, + "at": {"$ref": "#/$defs/time"}, + "set": { + "type": "object", + "minProperties": 1, + "properties": { + "description": {"$ref": "#/$defs/text"}, + "functional_impact": {"$ref": "#/$defs/text"}, + "recovery_plan": {"$ref": "#/$defs/text"}, + "observed_activity": {"$ref": "#/$defs/text"}, + "root_cause": {"$ref": "#/$defs/text"}, + "response_and_recovery_activities": {"$ref": "#/$defs/text"}, + "affected_agencies": {"$ref": "#/$defs/texts"}, + "indicators_of_compromise": {"$ref": "#/$defs/texts"}, + "related_cves": {"type": "array", "items": {"type": "string", "pattern": "^CVE-[0-9]{4}-[0-9]{4,}$"}, "uniqueItems": true}, + "milestones": {"type": "array", "items": { + "type": "object", "required": ["at", "description"], + "properties": {"at": {"$ref": "#/$defs/time"}, "description": {"$ref": "#/$defs/text"}}, + "additionalProperties": false + }} + }, + "additionalProperties": false + } + }, + "additionalProperties": false + }}, + "resolved_at": {"$ref": "#/$defs/time"}, + "recovery_complete_at": {"$ref": "#/$defs/time"} + }, + "additionalProperties": false + } + } +} diff --git a/infrastructure/schemas/ksi-catalog.json b/infrastructure/schemas/ksi-catalog.json index 7353e477..4b8dc8a7 100644 --- a/infrastructure/schemas/ksi-catalog.json +++ b/infrastructure/schemas/ksi-catalog.json @@ -121,7 +121,7 @@ { "reference": "NIST SP 800-53B", "reference_url": "https://csrc.nist.gov/pubs/sp/800/53/b/upd1/final", - "description": "Section 2.5 states \"As the number of controls in [SP 800-53] grows in response to an increasingly sophisticated threat space, it is important for organizations to have the ability to describe key capabilities needed to protect organizational missions and business functions, and to subsequently select controls that\u2014if properly designed, developed, and implemented\u2014produce such capabilities. The use of capabilities simplifies how the protection problem is viewed conceptually. Using the construct of a capability provides a method of grouping controls that are employed for a common purpose or to achieve a common objective.\" This section later states \"Ultimately, authorization decisions (i.e., risk acceptance decisions) are made based on the degree to which the desired capabilities have been effectively achieved.\"" + "description": "Section 2.5 states \"As the number of controls in [SP 800-53] grows in response to an increasingly sophisticated threat space, it is important for organizations to have the ability to describe key capabilities needed to protect organizational missions and business functions, and to subsequently select controls that—if properly designed, developed, and implemented—produce such capabilities. The use of capabilities simplifies how the protection problem is viewed conceptually. Using the construct of a capability provides a method of grouping controls that are employed for a common purpose or to achieve a common objective.\" This section later states \"Ultimately, authorization decisions (i.e., risk acceptance decisions) are made based on the degree to which the desired capabilities have been effectively achieved.\"" }, { "reference": "NIST SP 800-53A", @@ -129,9 +129,9 @@ "description": "Section 3.5 states \"When organizations employ the concept of capabilities, automated and manual assessments account for all security and privacy controls that comprise the security and privacy capabilities. Assessors are aware of how the controls work together to provide such capabilities.\"" }, { - "reference": "FedRAMP Authorization Act (44 USC \u00a7 3609 (a) (1))", + "reference": "FedRAMP Authorization Act (44 USC § 3609 (a) (1))", "reference_url": "https://fedramp.gov/docs/authority/law/#a-roles-and-responsibilities", - "description": "requires that the Administrator of the General Services Administration shall \"in consultation with the [DHS] Secretary, develop, coordinate, and implement a process to support agency review, reuse, and standardization, where appropriate, of security assessments of cloud computing products and services...\" 44 USC \u00a7 3609 (c) (2) further states that \"the [GSA] Administrator shall establish a means for the automation of security assessments and reviews.\"", + "description": "requires that the Administrator of the General Services Administration shall \"in consultation with the [DHS] Secretary, develop, coordinate, and implement a process to support agency review, reuse, and standardization, where appropriate, of security assessments of cloud computing products and services...\" 44 USC § 3609 (c) (2) further states that \"the [GSA] Administrator shall establish a means for the automation of security assessments and reviews.\"", "delegation": "These responsibilities are delegated to the FedRAMP Director", "delegation_url": "https://www.gsa.gov/directives-library/gsa-delegations-of-authority-fedramp" } @@ -159,18 +159,6 @@ "moderate": true }, "controls": [ - { - "control_id": "cp-3", - "title": "Contingency Training" - }, - { - "control_id": "ir-2", - "title": "Incident Response Training" - }, - { - "control_id": "ps-6", - "title": "Access Agreements" - }, { "control_id": "at-2", "title": "Literacy Training and Awareness" @@ -183,6 +171,10 @@ "control_id": "at-2.3", "title": "Social Engineering and Mining" }, + { + "control_id": "at-3", + "title": "Role-based Training" + }, { "control_id": "at-3.5", "title": "Processing Personally Identifiable Information" @@ -191,13 +183,53 @@ "control_id": "at-4", "title": "Training Records" }, + { + "control_id": "cm-11", + "title": "User-installed Software" + }, + { + "control_id": "cp-3", + "title": "Contingency Training" + }, + { + "control_id": "cp-3.1", + "title": "Simulated Events" + }, + { + "control_id": "ir-2", + "title": "Incident Response Training" + }, + { + "control_id": "ir-2.1", + "title": "Simulated Events" + }, + { + "control_id": "ir-2.2", + "title": "Automated Training Environments" + }, { "control_id": "ir-2.3", "title": "Breach" }, { - "control_id": "at-3", - "title": "Role-based Training" + "control_id": "ir-9.2", + "title": "Training" + }, + { + "control_id": "ir-9.4", + "title": "Exposure to Unauthorized Personnel" + }, + { + "control_id": "pl-4", + "title": "Rules of Behavior" + }, + { + "control_id": "pl-4.1", + "title": "Social Media and External Site/Application Usage Restrictions" + }, + { + "control_id": "ps-6", + "title": "Access Agreements" }, { "control_id": "sr-11.1", @@ -224,14 +256,26 @@ "control_id": "au-2", "title": "Event Logging" }, + { + "control_id": "ca-7.4", + "title": "Risk Monitoring" + }, { "control_id": "cm-3", "title": "Configuration Change Control" }, + { + "control_id": "cm-3.1", + "title": "Automated Documentation, Notification, and Prohibition of Changes" + }, { "control_id": "cm-3.2", "title": "Testing, Validation, and Documentation of Changes" }, + { + "control_id": "cm-3.6", + "title": "Cryptography Management" + }, { "control_id": "cm-4.2", "title": "Verification of Controls" @@ -243,10 +287,6 @@ { "control_id": "cm-8.3", "title": "Automated Unauthorized Component Detection" - }, - { - "control_id": "ma-2", - "title": "Controlled Maintenance" } ] }, @@ -345,6 +385,14 @@ "control_id": "cm-4.2", "title": "Verification of Controls" }, + { + "control_id": "cm-6.2", + "title": "Respond to Unauthorized Changes" + }, + { + "control_id": "ir-9.4", + "title": "Exposure to Unauthorized Personnel" + }, { "control_id": "si-2", "title": "Flaw Remediation" @@ -370,6 +418,18 @@ "control_id": "cm-2", "title": "Baseline Configuration" }, + { + "control_id": "cm-8.4", + "title": "Accountability Information" + }, + { + "control_id": "cp-10.4", + "title": "Restore Within Time Period" + }, + { + "control_id": "ir-9.4", + "title": "Exposure to Unauthorized Personnel" + }, { "control_id": "si-3", "title": "Malicious Code Protection" @@ -390,8 +450,48 @@ "title": "Independent Assessors" }, { - "control_id": "ca-7.1", - "title": "Independent Assessment" + "control_id": "cm-11", + "title": "User-installed Software" + }, + { + "control_id": "cm-6.2", + "title": "Respond to Unauthorized Changes" + }, + { + "control_id": "cp-10.4", + "title": "Restore Within Time Period" + }, + { + "control_id": "ir-9.4", + "title": "Exposure to Unauthorized Personnel" + }, + { + "control_id": "sc-24", + "title": "Fail in Known State" + }, + { + "control_id": "sc-7.18", + "title": "Fail Secure" + }, + { + "control_id": "si-4.22", + "title": "Unauthorized Network Services" + }, + { + "control_id": "si-7", + "title": "Software, Firmware, and Information Integrity" + }, + { + "control_id": "si-7.1", + "title": "Integrity Checks" + }, + { + "control_id": "si-7.5", + "title": "Automated Response to Integrity Violations" + }, + { + "control_id": "si-7.7", + "title": "Integration of Detection and Response" } ] }, @@ -415,6 +515,10 @@ { "control_id": "pl-10", "title": "Baseline Selection" + }, + { + "control_id": "sc-7.18", + "title": "Fail Secure" } ] }, @@ -447,6 +551,14 @@ "control_id": "ca-9", "title": "Internal System Connections" }, + { + "control_id": "sc-10", + "title": "Network Disconnect" + }, + { + "control_id": "sc-7.18", + "title": "Fail Secure" + }, { "control_id": "sc-7.3", "title": "Access Points" @@ -457,7 +569,7 @@ }, { "control_id": "sc-7.5", - "title": "Deny by Default \u2014 Allow by Exception" + "title": "Deny by Default — Allow by Exception" }, { "control_id": "sc-7.8", @@ -467,10 +579,6 @@ "control_id": "sc-8", "title": "Transmission Confidentiality and Integrity" }, - { - "control_id": "sc-10", - "title": "Network Disconnect" - }, { "control_id": "si-10", "title": "Information Input Validation" @@ -493,7 +601,16 @@ "low": true, "moderate": true }, - "controls": [] + "controls": [ + { + "control_id": "cp-2.5", + "title": "Continue Mission and Business Functions" + }, + { + "control_id": "sc-12.1", + "title": "Availability" + } + ] }, { "id": "KSI-CNA-RNT", @@ -516,9 +633,41 @@ "control_id": "cm-7.1", "title": "Periodic Review" }, + { + "control_id": "sc-7.10", + "title": "Prevent Exfiltration" + }, + { + "control_id": "sc-7.18", + "title": "Fail Secure" + }, + { + "control_id": "sc-7.20", + "title": "Dynamic Isolation and Segregation" + }, + { + "control_id": "sc-7.21", + "title": "Isolation of System Components" + }, { "control_id": "sc-7.5", - "title": "Deny by Default \u2014 Allow by Exception" + "title": "Deny by Default — Allow by Exception" + }, + { + "control_id": "si-10", + "title": "Information Input Validation" + }, + { + "control_id": "si-4.11", + "title": "Analyze Communications Traffic Anomalies" + }, + { + "control_id": "si-4.18", + "title": "Analyze Traffic and Covert Exfiltration" + }, + { + "control_id": "si-4.4", + "title": "Inbound and Outbound Communications Traffic" }, { "control_id": "si-8", @@ -535,10 +684,18 @@ "moderate": true }, "controls": [ + { + "control_id": "ir-4.2", + "title": "Dynamic Reconfiguration" + }, { "control_id": "sc-5", "title": "Denial-of-service Protection" }, + { + "control_id": "sc-7.18", + "title": "Fail Secure" + }, { "control_id": "si-8", "title": "Spam Protection" @@ -566,10 +723,22 @@ "control_id": "ac-17.3", "title": "Managed Access Control Points" }, + { + "control_id": "ac-4.21", + "title": "Physical or Logical Separation of Information Flows" + }, { "control_id": "ca-9", "title": "Internal System Connections" }, + { + "control_id": "cm-11", + "title": "User-installed Software" + }, + { + "control_id": "sc-10", + "title": "Network Disconnect" + }, { "control_id": "sc-4", "title": "Information in Shared System Resources" @@ -578,6 +747,14 @@ "control_id": "sc-7", "title": "Boundary Protection" }, + { + "control_id": "sc-7.20", + "title": "Dynamic Isolation and Segregation" + }, + { + "control_id": "sc-7.21", + "title": "Isolation of System Components" + }, { "control_id": "sc-7.7", "title": "Split Tunneling for Remote Devices" @@ -585,10 +762,6 @@ { "control_id": "sc-8", "title": "Transmission Confidentiality and Integrity" - }, - { - "control_id": "sc-10", - "title": "Network Disconnect" } ] } @@ -607,6 +780,10 @@ "moderate": true }, "controls": [ + { + "control_id": "ac-2.13", + "title": "Disable Accounts for High-risk Individuals" + }, { "control_id": "ac-2.2", "title": "Automated Temporary and Emergency Account Management" @@ -615,18 +792,10 @@ "control_id": "ac-2.3", "title": "Disable Accounts" }, - { - "control_id": "ac-2.13", - "title": "Disable Accounts for High-risk Individuals" - }, { "control_id": "ac-6.7", "title": "Review of User Privileges" }, - { - "control_id": "ia-4.4", - "title": "Identify User Status" - }, { "control_id": "ia-12", "title": "Identity Proofing" @@ -642,6 +811,14 @@ { "control_id": "ia-12.5", "title": "Address Confirmation" + }, + { + "control_id": "ia-4.4", + "title": "Identify User Status" + }, + { + "control_id": "ia-8.4", + "title": "Use of Defined Profiles" } ] }, @@ -654,54 +831,70 @@ "moderate": true }, "controls": [ + { + "control_id": "ac-2", + "title": "Account Management" + }, { "control_id": "ac-3", "title": "Access Enforcement" }, { - "control_id": "ia-5.1", - "title": "Password-based Authentication" + "control_id": "ia-2", + "title": "Identification and Authentication (Organizational Users)" }, { - "control_id": "ia-5.2", - "title": "Public Key-based Authentication" + "control_id": "ia-2.1", + "title": "Multi-factor Authentication to Privileged Accounts" }, { - "control_id": "ia-5.6", - "title": "Protection of Authenticators" + "control_id": "ia-2.2", + "title": "Multi-factor Authentication to Non-privileged Accounts" }, { - "control_id": "ia-6", - "title": "Authentication Feedback" + "control_id": "ia-2.6", + "title": "Access to Accounts —separate Device" }, { - "control_id": "ac-2", - "title": "Account Management" + "control_id": "ia-2.8", + "title": "Access to Accounts — Replay Resistant" }, { - "control_id": "ia-2", - "title": "Identification and Authentication (Organizational Users)" + "control_id": "ia-5", + "title": "Authenticator Management" }, { - "control_id": "ia-2.1", - "title": "Multi-factor Authentication to Privileged Accounts" + "control_id": "ia-5.1", + "title": "Password-based Authentication" }, { - "control_id": "ia-2.2", - "title": "Multi-factor Authentication to Non-privileged Accounts" + "control_id": "ia-5.2", + "title": "Public Key-based Authentication" }, { - "control_id": "ia-2.8", - "title": "Access to Accounts \u2014 Replay Resistant" + "control_id": "ia-5.6", + "title": "Protection of Authenticators" }, { - "control_id": "ia-5", - "title": "Authenticator Management" + "control_id": "ia-5.8", + "title": "Multiple System Accounts" + }, + { + "control_id": "ia-6", + "title": "Authentication Feedback" }, { "control_id": "ia-8", "title": "Identification and Authentication (Non-organizational Users)" }, + { + "control_id": "ia-8.2", + "title": "Acceptance of External Authenticators" + }, + { + "control_id": "ia-8.4", + "title": "Use of Defined Profiles" + }, { "control_id": "sc-23", "title": "Session Authenticity" @@ -717,26 +910,6 @@ "moderate": true }, "controls": [ - { - "control_id": "ac-2.5", - "title": "Inactivity Logout" - }, - { - "control_id": "ac-2.6", - "title": "Dynamic Privilege Management" - }, - { - "control_id": "ac-3", - "title": "Access Enforcement" - }, - { - "control_id": "ac-4", - "title": "Information Flow Enforcement" - }, - { - "control_id": "ac-6", - "title": "Least Privilege" - }, { "control_id": "ac-12", "title": "Session Termination" @@ -761,6 +934,30 @@ "control_id": "ac-17.3", "title": "Managed Access Control Points" }, + { + "control_id": "ac-18.4", + "title": "Restrict Configurations by Users" + }, + { + "control_id": "ac-2.11", + "title": "Usage Conditions" + }, + { + "control_id": "ac-2.5", + "title": "Inactivity Logout" + }, + { + "control_id": "ac-2.6", + "title": "Dynamic Privilege Management" + }, + { + "control_id": "ac-2.7", + "title": "Privileged User Accounts" + }, + { + "control_id": "ac-2.9", + "title": "Restrictions on Use of Shared and Group Accounts" + }, { "control_id": "ac-20", "title": "Use of External Systems" @@ -769,14 +966,62 @@ "control_id": "ac-20.1", "title": "Limits on Authorized Use" }, + { + "control_id": "ac-21", + "title": "Information Sharing" + }, + { + "control_id": "ac-3", + "title": "Access Enforcement" + }, + { + "control_id": "ac-4", + "title": "Information Flow Enforcement" + }, + { + "control_id": "ac-6", + "title": "Least Privilege" + }, + { + "control_id": "ac-6.3", + "title": "Network Access to Privileged Commands" + }, + { + "control_id": "ac-6.8", + "title": "Privilege Levels for Code Execution" + }, + { + "control_id": "au-12.3", + "title": "Changes by Authorized Individuals" + }, + { + "control_id": "au-6.7", + "title": "Permitted Actions" + }, { "control_id": "cm-2.7", "title": "Configure Systems and Components for High-risk Areas" }, + { + "control_id": "cm-5.1", + "title": "Automated Access Enforcement and Audit Records" + }, + { + "control_id": "cm-5.5", + "title": "Privilege Limitation for Production and Operation" + }, + { + "control_id": "cm-7.2", + "title": "Prevent Program Execution" + }, { "control_id": "cm-9", "title": "Configuration Management Plan" }, + { + "control_id": "ia-11", + "title": "Re-authentication" + }, { "control_id": "ia-2", "title": "Identification and Authentication (Organizational Users)" @@ -802,8 +1047,12 @@ "title": "Protection of Authenticators" }, { - "control_id": "ia-11", - "title": "Re-authentication" + "control_id": "ir-4.6", + "title": "Insider Threats" + }, + { + "control_id": "ir-9.4", + "title": "Exposure to Unauthorized Personnel" }, { "control_id": "ps-2", @@ -826,8 +1075,12 @@ "title": "Access Agreements" }, { - "control_id": "sc-4", - "title": "Information in Shared System Resources" + "control_id": "ra-5.5", + "title": "Privileged Access" + }, + { + "control_id": "sc-2", + "title": "Separation of System and User Functionality" }, { "control_id": "sc-20", @@ -845,13 +1098,25 @@ "control_id": "sc-23", "title": "Session Authenticity" }, + { + "control_id": "sc-3", + "title": "Security Function Isolation" + }, { "control_id": "sc-39", "title": "Process Isolation" }, + { + "control_id": "sc-4", + "title": "Information in Shared System Resources" + }, { "control_id": "si-3", "title": "Malicious Code Protection" + }, + { + "control_id": "si-4.19", + "title": "Risk for Individuals" } ] }, @@ -864,6 +1129,14 @@ "moderate": true }, "controls": [ + { + "control_id": "ac-17", + "title": "Remote Access" + }, + { + "control_id": "ac-17.4", + "title": "Privileged Commands and Access" + }, { "control_id": "ac-2", "title": "Account Management" @@ -872,6 +1145,10 @@ "control_id": "ac-2.1", "title": "Automated System Account Management" }, + { + "control_id": "ac-2.11", + "title": "Usage Conditions" + }, { "control_id": "ac-2.2", "title": "Automated Temporary and Emergency Account Management" @@ -888,6 +1165,18 @@ "control_id": "ac-2.6", "title": "Dynamic Privilege Management" }, + { + "control_id": "ac-2.7", + "title": "Privileged User Accounts" + }, + { + "control_id": "ac-20.1", + "title": "Limits on Authorized Use" + }, + { + "control_id": "ac-21", + "title": "Information Sharing" + }, { "control_id": "ac-3", "title": "Access Enforcement" @@ -908,10 +1197,18 @@ "control_id": "ac-6.1", "title": "Authorize Access to Security Functions" }, + { + "control_id": "ac-6.10", + "title": "Prohibit Non-privileged Users from Executing Privileged Functions" + }, { "control_id": "ac-6.2", "title": "Non-privileged Access for Nonsecurity Functions" }, + { + "control_id": "ac-6.3", + "title": "Network Access to Privileged Commands" + }, { "control_id": "ac-6.5", "title": "Privileged Accounts" @@ -921,33 +1218,45 @@ "title": "Review of User Privileges" }, { - "control_id": "ac-6.9", - "title": "Log Use of Privileged Functions" + "control_id": "ac-6.8", + "title": "Privilege Levels for Code Execution" }, { - "control_id": "ac-6.10", - "title": "Prohibit Non-privileged Users from Executing Privileged Functions" + "control_id": "ac-6.9", + "title": "Log Use of Privileged Functions" }, { "control_id": "ac-7", "title": "Unsuccessful Logon Attempts" }, { - "control_id": "ac-20.1", - "title": "Limits on Authorized Use" + "control_id": "au-10", + "title": "Non-repudiation" }, { - "control_id": "ac-17", - "title": "Remote Access" + "control_id": "au-12.3", + "title": "Changes by Authorized Individuals" }, { "control_id": "au-9.4", "title": "Access by Subset of Privileged Users" }, + { + "control_id": "ca-3.6", + "title": "Transfer Authorizations" + }, { "control_id": "cm-5", "title": "Access Restrictions for Change" }, + { + "control_id": "cm-5.1", + "title": "Automated Access Enforcement and Audit Records" + }, + { + "control_id": "cm-5.5", + "title": "Privilege Limitation for Production and Operation" + }, { "control_id": "cm-7", "title": "Least Functionality" @@ -958,7 +1267,7 @@ }, { "control_id": "cm-7.5", - "title": "Authorized Software \u2014 Allow-by-exception" + "title": "Authorized Software — Allow-by-exception" }, { "control_id": "cm-9", @@ -976,6 +1285,10 @@ "control_id": "ia-7", "title": "Cryptographic Module Authentication" }, + { + "control_id": "ir-4.6", + "title": "Insider Threats" + }, { "control_id": "ps-2", "title": "Position Risk Designation" @@ -1012,6 +1325,10 @@ "control_id": "sc-23", "title": "Session Authenticity" }, + { + "control_id": "sc-3", + "title": "Security Function Isolation" + }, { "control_id": "sc-39", "title": "Process Isolation" @@ -1035,6 +1352,10 @@ "control_id": "ac-2.2", "title": "Automated Temporary and Emergency Account Management" }, + { + "control_id": "ac-2.9", + "title": "Restrictions on Use of Shared and Group Accounts" + }, { "control_id": "ac-4", "title": "Information Flow Enforcement" @@ -1043,6 +1364,14 @@ "control_id": "ac-6.5", "title": "Privileged Accounts" }, + { + "control_id": "au-10", + "title": "Non-repudiation" + }, + { + "control_id": "ia-2.5", + "title": "Individual Authentication with Group Authentication" + }, { "control_id": "ia-3", "title": "Device Identification and Authentication" @@ -1075,17 +1404,45 @@ "title": "Automated System Account Management" }, { - "control_id": "ac-2.3", - "title": "Disable Accounts" + "control_id": "ac-2.11", + "title": "Usage Conditions" + }, + { + "control_id": "ac-2.12", + "title": "Account Monitoring for Atypical Usage" }, { "control_id": "ac-2.13", "title": "Disable Accounts for High-risk Individuals" }, + { + "control_id": "ac-2.3", + "title": "Disable Accounts" + }, { "control_id": "ac-7", "title": "Unsuccessful Logon Attempts" }, + { + "control_id": "au-6.5", + "title": "Integrated Analysis of Audit Records" + }, + { + "control_id": "cm-5.1", + "title": "Automated Access Enforcement and Audit Records" + }, + { + "control_id": "cm-6.2", + "title": "Respond to Unauthorized Changes" + }, + { + "control_id": "ir-4.2", + "title": "Dynamic Reconfiguration" + }, + { + "control_id": "ir-4.6", + "title": "Insider Threats" + }, { "control_id": "ps-4", "title": "Personnel Termination" @@ -1093,6 +1450,30 @@ { "control_id": "ps-8", "title": "Personnel Sanctions" + }, + { + "control_id": "si-4", + "title": "System Monitoring" + }, + { + "control_id": "si-4.1", + "title": "System-wide Intrusion Detection System" + }, + { + "control_id": "si-4.19", + "title": "Risk for Individuals" + }, + { + "control_id": "si-4.20", + "title": "Privileged Users" + }, + { + "control_id": "si-4.22", + "title": "Unauthorized Network Services" + }, + { + "control_id": "si-4.4", + "title": "Inbound and Outbound Communications Traffic" } ] } @@ -1123,9 +1504,17 @@ "control_id": "ir-4.1", "title": "Automated Incident Handling Processes" }, + { + "control_id": "ir-5.1", + "title": "Automated Tracking, Data Collection, and Analysis" + }, { "control_id": "ir-8", "title": "Incident Response Plan" + }, + { + "control_id": "ir-9.3", + "title": "Post-spill Operations" } ] }, @@ -1146,6 +1535,10 @@ "control_id": "ir-4.1", "title": "Automated Incident Handling Processes" }, + { + "control_id": "ir-4.11", + "title": "Integrated Incident Response Team" + }, { "control_id": "ir-6", "title": "Incident Reporting" @@ -1174,6 +1567,10 @@ "control_id": "ir-8.1", "title": "Breaches" }, + { + "control_id": "ir-9.3", + "title": "Post-spill Operations" + }, { "control_id": "si-4.5", "title": "System-generated Alerts" @@ -1201,13 +1598,29 @@ "control_id": "ir-4.1", "title": "Automated Incident Handling Processes" }, + { + "control_id": "ir-4.11", + "title": "Integrated Incident Response Team" + }, + { + "control_id": "ir-4.4", + "title": "Information Correlation" + }, { "control_id": "ir-5", "title": "Incident Monitoring" }, + { + "control_id": "ir-5.1", + "title": "Automated Tracking, Data Collection, and Analysis" + }, { "control_id": "ir-8", "title": "Incident Response Plan" + }, + { + "control_id": "ra-5.8", + "title": "Review Historic Audit Logs" } ] } @@ -1226,6 +1639,14 @@ "moderate": true }, "controls": [ + { + "control_id": "au-12.3", + "title": "Changes by Authorized Individuals" + }, + { + "control_id": "au-6.7", + "title": "Permitted Actions" + }, { "control_id": "si-11", "title": "Error Handling" @@ -1241,6 +1662,10 @@ "moderate": true }, "controls": [ + { + "control_id": "ac-19", + "title": "Access Control for Mobile Devices" + }, { "control_id": "ca-7", "title": "Continuous Monitoring" @@ -1253,6 +1678,14 @@ "control_id": "cm-6", "title": "Configuration Settings" }, + { + "control_id": "cm-6.1", + "title": "Automated Management, Application, and Verification" + }, + { + "control_id": "ra-3", + "title": "Risk Assessment" + }, { "control_id": "si-7.7", "title": "Integration of Detection and Response" @@ -1268,33 +1701,57 @@ "moderate": true }, "controls": [ + { + "control_id": "ac-17.1", + "title": "Monitoring and Control" + }, { "control_id": "ac-2.4", "title": "Automated Audit Actions" }, + { + "control_id": "ac-20.1", + "title": "Limits on Authorized Use" + }, { "control_id": "ac-6.9", "title": "Log Use of Privileged Functions" }, { - "control_id": "ac-17.1", - "title": "Monitoring and Control" + "control_id": "au-10", + "title": "Non-repudiation" + }, + { + "control_id": "au-12", + "title": "Audit Record Generation" + }, + { + "control_id": "au-2", + "title": "Event Logging" + }, + { + "control_id": "au-7", + "title": "Audit Record Reduction and Report Generation" + }, + { + "control_id": "au-7.1", + "title": "Automatic Processing" }, { - "control_id": "ac-20.1", - "title": "Limits on Authorized Use" + "control_id": "cm-5.1", + "title": "Automated Access Enforcement and Audit Records" }, { - "control_id": "au-2", - "title": "Event Logging" + "control_id": "ir-9.4", + "title": "Exposure to Unauthorized Personnel" }, { - "control_id": "au-7.1", - "title": "Automatic Processing" + "control_id": "si-4.19", + "title": "Risk for Individuals" }, { - "control_id": "au-12", - "title": "Audit Record Generation" + "control_id": "si-4.20", + "title": "Privileged Users" }, { "control_id": "si-4.4", @@ -1327,6 +1784,14 @@ "control_id": "ac-20.1", "title": "Limits on Authorized Use" }, + { + "control_id": "au-11", + "title": "Audit Record Retention" + }, + { + "control_id": "au-12.1", + "title": "System-wide and Time-correlated Audit Trail" + }, { "control_id": "au-2", "title": "Event Logging" @@ -1347,6 +1812,10 @@ "control_id": "au-5", "title": "Response to Audit Logging Process Failures" }, + { + "control_id": "au-5.1", + "title": "Storage Capacity Warning" + }, { "control_id": "au-6.1", "title": "Automated Process Integration" @@ -1355,6 +1824,14 @@ "control_id": "au-6.3", "title": "Correlate Audit Record Repositories" }, + { + "control_id": "au-6.4", + "title": "Central Review and Analysis" + }, + { + "control_id": "au-6.5", + "title": "Integrated Analysis of Audit Records" + }, { "control_id": "au-7", "title": "Audit Record Reduction and Report Generation" @@ -1371,14 +1848,14 @@ "control_id": "au-9", "title": "Protection of Audit Information" }, - { - "control_id": "au-11", - "title": "Audit Record Retention" - }, { "control_id": "ir-4.1", "title": "Automated Incident Handling Processes" }, + { + "control_id": "si-4.16", + "title": "Correlate Monitoring Information" + }, { "control_id": "si-4.2", "title": "Automated Tools and Mechanisms for Real-time Analysis" @@ -1386,10 +1863,6 @@ { "control_id": "si-4.4", "title": "Inbound and Outbound Communications Traffic" - }, - { - "control_id": "si-7.7", - "title": "Integration of Detection and Response" } ] }, @@ -1422,10 +1895,22 @@ "control_id": "au-6.1", "title": "Automated Process Integration" }, + { + "control_id": "au-7", + "title": "Audit Record Reduction and Report Generation" + }, + { + "control_id": "ra-5.8", + "title": "Review Historic Audit Logs" + }, { "control_id": "si-4", "title": "System Monitoring" }, + { + "control_id": "si-4.19", + "title": "Risk for Individuals" + }, { "control_id": "si-4.4", "title": "Inbound and Outbound Communications Traffic" @@ -1447,13 +1932,21 @@ "moderate": true }, "controls": [ + { + "control_id": "cm-12", + "title": "Information Location" + }, + { + "control_id": "cm-12.1", + "title": "Automated Tools to Support Information Location" + }, { "control_id": "cm-2.2", "title": "Automation Support for Accuracy and Currency" }, { "control_id": "cm-7.5", - "title": "Authorized Software \u2014 Allow-by-exception" + "title": "Authorized Software — Allow-by-exception" }, { "control_id": "cm-8", @@ -1464,12 +1957,12 @@ "title": "Updates During Installation and Removal" }, { - "control_id": "cm-12", - "title": "Information Location" + "control_id": "cm-8.2", + "title": "Automated Maintenance" }, { - "control_id": "cm-12.1", - "title": "Automated Tools to Support Information Location" + "control_id": "cm-8.4", + "title": "Accountability Information" }, { "control_id": "cp-2.8", @@ -1504,6 +1997,10 @@ "control_id": "ca-2", "title": "Control Assessments" }, + { + "control_id": "ca-2.2", + "title": "Specialized Assessments" + }, { "control_id": "cp-2.1", "title": "Coordinate with Related Plans" @@ -1516,6 +2013,10 @@ "control_id": "ir-3.2", "title": "Coordination with Related Plans" }, + { + "control_id": "ir-4.11", + "title": "Integrated Incident Response Team" + }, { "control_id": "pm-3", "title": "Information Security and Privacy Resources" @@ -1555,6 +2056,10 @@ "control_id": "cm-3.4", "title": "Security and Privacy Representatives" }, + { + "control_id": "ia-5.7", + "title": "No Embedded Unencrypted Static Authenticators" + }, { "control_id": "pl-8", "title": "Security and Privacy Architectures" @@ -1563,6 +2068,10 @@ "control_id": "pm-7", "title": "Enterprise Architecture" }, + { + "control_id": "ra-9", + "title": "Criticality Analysis" + }, { "control_id": "sa-3", "title": "System Development Life Cycle" @@ -1571,14 +2080,14 @@ "control_id": "sa-8", "title": "Security and Privacy Engineering Principles" }, - { - "control_id": "sc-4", - "title": "Information in Shared System Resources" - }, { "control_id": "sc-18", "title": "Mobile Code" }, + { + "control_id": "sc-4", + "title": "Information in Shared System Resources" + }, { "control_id": "si-10", "title": "Information Input Validation" @@ -1642,10 +2151,6 @@ { "control_id": "cp-10.2", "title": "Transaction Recovery" - }, - { - "control_id": "si-12", - "title": "Information Management and Retention" } ] }, @@ -1752,6 +2257,10 @@ "moderate": true }, "controls": [ + { + "control_id": "cp-10", + "title": "System Recovery and Reconstitution" + }, { "control_id": "cp-2.1", "title": "Coordinate with Related Plans" @@ -1780,10 +2289,6 @@ "control_id": "cp-9.1", "title": "Testing for Reliability and Integrity" }, - { - "control_id": "cp-10", - "title": "System Recovery and Reconstitution" - }, { "control_id": "ir-3", "title": "Incident Response Testing" @@ -1791,6 +2296,14 @@ { "control_id": "ir-3.2", "title": "Coordination with Related Plans" + }, + { + "control_id": "ir-9.3", + "title": "Post-spill Operations" + }, + { + "control_id": "sc-12.1", + "title": "Availability" } ] } @@ -1803,23 +2316,31 @@ { "id": "KSI-SCR-MIT", "name": "Mitigating Supply Chain Risk", - "statement": "Persistently identify, review, and mitigate potential supply chain risks.", + "statement": "Potential supply chain risks are persistently identified, reviewed, and mitigated.", "impact": { "low": true, "moderate": true }, "controls": [ + { + "control_id": "ac-19", + "title": "Access Control for Mobile Devices" + }, { "control_id": "ac-20", "title": "Use of External Systems" }, { - "control_id": "ra-3.1", - "title": "Supply Chain Risk Assessment" + "control_id": "ca-7.4", + "title": "Risk Monitoring" }, { - "control_id": "sa-9", - "title": "External System Services" + "control_id": "ra-3", + "title": "Risk Assessment" + }, + { + "control_id": "ra-3.1", + "title": "Supply Chain Risk Assessment" }, { "control_id": "sa-10", @@ -1829,33 +2350,101 @@ "control_id": "sa-11", "title": "Developer Testing and Evaluation" }, + { + "control_id": "sa-11.1", + "title": "Static Code Analysis" + }, + { + "control_id": "sa-11.2", + "title": "Threat Modeling and Vulnerability Analyses" + }, + { + "control_id": "sa-15", + "title": "Development Process, Standards, and Tools" + }, { "control_id": "sa-15.3", "title": "Criticality Analysis" }, + { + "control_id": "sa-16", + "title": "Developer-provided Training" + }, + { + "control_id": "sa-17", + "title": "Developer Security and Privacy Architecture and Design" + }, + { + "control_id": "sa-21", + "title": "Developer Screening" + }, { "control_id": "sa-22", "title": "Unsupported System Components" }, { - "control_id": "si-7.1", - "title": "Integrity Checks" + "control_id": "sa-4", + "title": "Acquisition Process" }, { - "control_id": "sr-5", - "title": "Acquisition Strategies, Tools, and Methods" + "control_id": "sa-4.1", + "title": "Functional Properties of Controls" }, { - "control_id": "sr-6", - "title": "Supplier Assessments and Reviews" + "control_id": "sa-4.2", + "title": "Design and Implementation Information for Controls" }, { - "control_id": "ca-7.4", - "title": "Risk Monitoring" + "control_id": "sa-4.5", + "title": "System, Component, and Service Configurations" + }, + { + "control_id": "sa-4.9", + "title": "Functions, Ports, Protocols, and Services in Use" + }, + { + "control_id": "sa-9", + "title": "External System Services" + }, + { + "control_id": "sa-9.1", + "title": "Risk Assessments and Organizational Approvals" + }, + { + "control_id": "sa-9.2", + "title": "Identification of Functions, Ports, Protocols, and Services" + }, + { + "control_id": "sa-9.5", + "title": "Processing, Storage, and Service Location" }, { "control_id": "sc-18", "title": "Mobile Code" + }, + { + "control_id": "si-7.1", + "title": "Integrity Checks" + }, + { + "control_id": "si-7.15", + "title": "Code Authentication" + }, + { + "control_id": "sr-2", + "title": "Supply Chain Risk Management Plan" + }, + { + "control_id": "sr-3", + "title": "Supply Chain Controls and Processes" + }, + { + "control_id": "sr-5", + "title": "Acquisition Strategies, Tools, and Methods" + }, + { + "control_id": "sr-6", + "title": "Supplier Assessments and Reviews" } ] }, @@ -1868,10 +2457,18 @@ "moderate": true }, "controls": [ + { + "control_id": "ac-19", + "title": "Access Control for Mobile Devices" + }, { "control_id": "ac-20", "title": "Use of External Systems" }, + { + "control_id": "ca-2.3", + "title": "Leveraging Results from External Organizations" + }, { "control_id": "ca-3", "title": "Information Exchange" @@ -1884,6 +2481,10 @@ "control_id": "ps-7", "title": "External Personnel Security" }, + { + "control_id": "ra-3", + "title": "Risk Assessment" + }, { "control_id": "ra-5", "title": "Vulnerability Monitoring and Scanning" @@ -1896,6 +2497,10 @@ "control_id": "si-5", "title": "Security Alerts, Advisories, and Directives" }, + { + "control_id": "sr-3", + "title": "Supply Chain Controls and Processes" + }, { "control_id": "sr-5", "title": "Acquisition Strategies, Tools, and Methods" @@ -1929,6 +2534,10 @@ "control_id": "ac-2.4", "title": "Automated Audit Actions" }, + { + "control_id": "ac-6.8", + "title": "Privilege Levels for Code Execution" + }, { "control_id": "cm-2", "title": "Baseline Configuration" @@ -1949,18 +2558,30 @@ "control_id": "cm-7.1", "title": "Periodic Review" }, - { - "control_id": "pl-9", - "title": "Central Management" - }, { "control_id": "pl-10", "title": "Baseline Selection" }, + { + "control_id": "pl-9", + "title": "Central Management" + }, { "control_id": "sa-5", "title": "System Documentation" }, + { + "control_id": "sc-45", + "title": "System Time Synchronization" + }, + { + "control_id": "sc-45.1", + "title": "Synchronization with Authoritative Time Source" + }, + { + "control_id": "sc-7.18", + "title": "Fail Secure" + }, { "control_id": "si-5", "title": "Security Alerts, Advisories, and Directives" @@ -1996,6 +2617,10 @@ "control_id": "sc-12", "title": "Cryptographic Key Establishment and Management" }, + { + "control_id": "sc-12.1", + "title": "Availability" + }, { "control_id": "sc-17", "title": "Public Key Infrastructure Certificates" @@ -2012,29 +2637,41 @@ }, "controls": [ { - "control_id": "cm-7.1", - "title": "Periodic Review" + "control_id": "ca-7.4", + "title": "Risk Monitoring" }, { "control_id": "cm-12.1", "title": "Automated Tools to Support Information Location" }, { - "control_id": "ma-2", - "title": "Controlled Maintenance" + "control_id": "cm-5.5", + "title": "Privilege Limitation for Production and Operation" + }, + { + "control_id": "cm-7.1", + "title": "Periodic Review" + }, + { + "control_id": "ir-9.4", + "title": "Exposure to Unauthorized Personnel" }, { "control_id": "pl-8", "title": "Security and Privacy Architectures" }, { - "control_id": "sc-7", - "title": "Boundary Protection" + "control_id": "ra-3", + "title": "Risk Assessment" }, { "control_id": "sc-39", "title": "Process Isolation" }, + { + "control_id": "sc-7", + "title": "Boundary Protection" + }, { "control_id": "si-2.2", "title": "Automated Flaw Remediation Status" @@ -2058,9 +2695,25 @@ "moderate": true }, "controls": [ + { + "control_id": "ac-19", + "title": "Access Control for Mobile Devices" + }, + { + "control_id": "ir-9.4", + "title": "Exposure to Unauthorized Personnel" + }, + { + "control_id": "sc-12.1", + "title": "Availability" + }, { "control_id": "sc-4", "title": "Information in Shared System Resources" + }, + { + "control_id": "sc-7.18", + "title": "Fail Secure" } ] }, @@ -2073,6 +2726,10 @@ "moderate": true }, "controls": [ + { + "control_id": "ir-9", + "title": "Information Spillage Response" + }, { "control_id": "si-12.3", "title": "Information Disposal" @@ -2080,6 +2737,14 @@ { "control_id": "si-18.4", "title": "Individual Requests" + }, + { + "control_id": "si-8", + "title": "Spam Protection" + }, + { + "control_id": "si-8.2", + "title": "Automatic Updates" } ] }, @@ -2093,25 +2758,33 @@ }, "controls": [ { - "control_id": "ac-1", - "title": "Policy and Procedures" + "control_id": "ac-11", + "title": "Device Lock" + }, + { + "control_id": "ac-11.1", + "title": "Pattern-hiding Displays" }, { "control_id": "ac-17.2", "title": "Protection of Confidentiality and Integrity Using Encryption" }, { - "control_id": "cp-9.8", - "title": "Cryptographic Protection" + "control_id": "ac-19.5", + "title": "Full Device or Container-based Encryption" }, { - "control_id": "sc-8", - "title": "Transmission Confidentiality and Integrity" + "control_id": "ac-21", + "title": "Information Sharing" }, { - "control_id": "sc-8.1", + "control_id": "cp-9.8", "title": "Cryptographic Protection" }, + { + "control_id": "ir-9.4", + "title": "Exposure to Unauthorized Personnel" + }, { "control_id": "sc-13", "title": "Cryptographic Protection" @@ -2139,6 +2812,26 @@ { "control_id": "sc-28.1", "title": "Cryptographic Protection" + }, + { + "control_id": "sc-4", + "title": "Information in Shared System Resources" + }, + { + "control_id": "sc-7.18", + "title": "Fail Secure" + }, + { + "control_id": "sc-8", + "title": "Transmission Confidentiality and Integrity" + }, + { + "control_id": "sc-8.1", + "title": "Cryptographic Protection" + }, + { + "control_id": "si-4.18", + "title": "Analyze Traffic and Covert Exfiltration" } ] }, @@ -2151,10 +2844,30 @@ "moderate": true }, "controls": [ + { + "control_id": "ac-10", + "title": "Concurrent Session Control" + }, + { + "control_id": "ac-17.4", + "title": "Privileged Commands and Access" + }, + { + "control_id": "ac-18", + "title": "Wireless Access" + }, + { + "control_id": "ac-19", + "title": "Access Control for Mobile Devices" + }, { "control_id": "sc-23", "title": "Session Authenticity" }, + { + "control_id": "si-4.22", + "title": "Unauthorized Network Services" + }, { "control_id": "si-7.1", "title": "Integrity Checks" @@ -2170,6 +2883,26 @@ "moderate": true }, "controls": [ + { + "control_id": "ac-17.4", + "title": "Privileged Commands and Access" + }, + { + "control_id": "ac-18", + "title": "Wireless Access" + }, + { + "control_id": "ac-19", + "title": "Access Control for Mobile Devices" + }, + { + "control_id": "au-9.3", + "title": "Cryptographic Protection" + }, + { + "control_id": "cm-14", + "title": "Signed Components" + }, { "control_id": "cm-2.2", "title": "Automation Support for Accuracy and Currency" @@ -2194,9 +2927,17 @@ "control_id": "si-7.1", "title": "Integrity Checks" }, + { + "control_id": "si-7.15", + "title": "Code Authentication" + }, { "control_id": "sr-10", "title": "Inspection of Systems or Components" + }, + { + "control_id": "sr-11", + "title": "Component Authenticity" } ] } diff --git a/infrastructure/schemas/ksi-signal.schema.json b/infrastructure/schemas/ksi-signal.schema.json index a6f07f2c..3ba7d01e 100644 --- a/infrastructure/schemas/ksi-signal.schema.json +++ b/infrastructure/schemas/ksi-signal.schema.json @@ -57,6 +57,11 @@ "type": "string", "minLength": 1 }, + "fedRampId": { + "description": "The offering's FedRAMP ID (CDS-CSO-FID), from data/cds/offering.json. Until FedRAMP assigns one, FedRAMP's fallback: the provider name and acronym, marked as not real. The runtime signal copies it from the deploy signal.", + "type": "string", + "minLength": 1 + }, "categorization": { "type": "object", "description": "Single-source system categorization (assessment F-2 / Decision 1). Identical impact_level must appear across the SSP, POA&M, VDR, and dashboard; the reconciliation gate enforces it.", @@ -106,7 +111,7 @@ "type": "string" }, "run_id": { - "description": "Builder-specific identifier for this build run. For GitHub Actions: the workflow run ID.", + "description": "Builder-specific identifier for this build run, when it does not identify a GitHub Actions run: the deploy omits it (no GitHub run ID is published; source.commit and builder.id identify the build), and the runtime emitter gives its Lambda log stream.", "type": "string" }, "version": { @@ -223,6 +228,10 @@ "divergence": { "description": "Result of comparing this runtime evaluation against the deploy gate's published verdict for the same system. Emitted by the runtime emitter only; absent from deploy-time signals. `regressions` lists KSIs the deploy gate published as passing that this evaluation found failing \u2014 a genuine disagreement about the resource. `unassessed` lists KSIs this evaluation could not reach a verdict on (category:input violations such as resource_read_error), which is an observer fault and must never be treated as drift.", "$ref": "#/$defs/divergence" + }, + "run_history": { + "description": "Runtime emitter only: a bounded history (at most 400 entries, oldest first) of every runtime run, carried inside the signed payload so a period report can list each run even after the signal it came from was replaced (VER-RPT-PER). The emitter carries the history forward only from a previous signal whose signature verifies against its own key; otherwise the history restarts and the first entry's history_reset says why.", + "$ref": "#/$defs/run_history" } }, "$defs": { @@ -678,6 +687,54 @@ "description": "Failing violations carrying no ksi_ids, so attributable to no KSI." } } + }, + "run_history": { + "type": "array", + "maxItems": 400, + "items": { + "type": "object", + "additionalProperties": false, + "required": [ + "signal_id", + "emitted_at", + "validations", + "failed", + "divergence" + ], + "properties": { + "signal_id": { + "type": "string", + "description": "The run's signal_id." + }, + "emitted_at": { + "type": "string", + "format": "date-time" + }, + "validations": { + "type": "integer", + "minimum": 0, + "description": "Validations the run carried." + }, + "failed": { + "type": "integer", + "minimum": 0, + "description": "Validations with result fail." + }, + "unassessed": { + "type": "integer", + "minimum": 0, + "description": "Validations with a category input violation (could not read the configuration)." + }, + "divergence": { + "type": "string", + "description": "The run's divergence.status (converged, degraded, diverged), or unknown." + }, + "history_reset": { + "type": "string", + "description": "Present on the first entry after a restart: why earlier runs were not carried forward." + } + } + } } } } diff --git a/infrastructure/schemas/non-machine-resources.schema.json b/infrastructure/schemas/non-machine-resources.schema.json new file mode 100644 index 00000000..cef99538 --- /dev/null +++ b/infrastructure/schemas/non-machine-resources.schema.json @@ -0,0 +1,76 @@ +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "title": "Non-machine information resources and their verification (VDR-TFR-NMV)", + "description": "Validated in code by scripts/_nonmachine.py (the deploy installs no jsonschema). Each resource is verified by machine checks on every deploy and every night; there is no manual attestation.", + "type": "object", + "additionalProperties": false, + "required": [ + "schema", + "max_age_days", + "resources" + ], + "properties": { + "$schema": { + "type": "string" + }, + "$comment": { + "type": "string" + }, + "schema": { + "const": "non-machine-resources/2" + }, + "max_age_days": { + "type": "integer", + "minimum": 1, + "maximum": 92 + }, + "resources": { + "type": "array", + "minItems": 1, + "items": { + "type": "object", + "additionalProperties": false, + "required": [ + "id", + "path", + "kind", + "title", + "owner", + "verifies" + ], + "properties": { + "id": { + "type": "string", + "pattern": "^NMR-[A-Z0-9-]+$" + }, + "path": { + "type": "string", + "minLength": 1 + }, + "kind": { + "enum": [ + "policy", + "procedure", + "plan", + "role", + "record", + "register" + ] + }, + "title": { + "type": "string", + "minLength": 1 + }, + "owner": { + "type": "string", + "minLength": 1 + }, + "verifies": { + "type": "string", + "minLength": 1 + } + } + } + } + } +} diff --git a/infrastructure/schemas/runtime-vv-config.json b/infrastructure/schemas/runtime-vv-config.json new file mode 100644 index 00000000..6b55af6d --- /dev/null +++ b/infrastructure/schemas/runtime-vv-config.json @@ -0,0 +1,38 @@ +{ + "version": "1.0", + "description": "Governed scope of runtime verification and validation (VDR-TFR-MVX, VDR-TFR-PDD, FRC-CSX-VVK). Every inventory component type is either a machine type, which the runtime emitter (infrastructure/lambda) must re-validate live against the deploy gate's policy within max_age_hours, or an excluded type with the reason another mechanism covers it. Reconciliation invariant (m) in scripts/reconcile.py reads this file, fails closed on any component type it does not classify, and is run by evidence-nightly.yml against the published inventory and runtime signal.", + "decided_by": "Operator", + "decided_on": "2026-11-05", + "review_by": "2027-11-05", + "rationale": "VDR-TFR-MVX requires machine-based resources to be verified and validated at least every 3 days, so a machine component counts as validated only by an assessed runtime validation (no unread attribute) younger than 72 hours. VDR-TFR-PDD requires drift detection at least every 14 days on resources likely to drift; every machine type is re-validated daily, so the likely-to-drift set is recorded for the drift report and the 14-day window is met with margin. Software packages and site pages are not machine resources in this sense: their state is fixed by the deployed artifact, which is re-scanned (Syft and Grype, twice daily) and re-hashed (every deploy), and the runtime package-integrity check proves the deployed code is still that artifact.", + "max_age_hours": 72, + "drift_window_days": 14, + "machine_types": { + "object_store": {"likely_to_drift": true, "why": "Bucket encryption, versioning, public-access block and tags can be changed in the console or by any principal with bucket rights."}, + "cdn_distribution": {"likely_to_drift": true, "why": "Managed by the operator-applied bootstrap stack and editable in the console; protocol policy and TLS floor can change outside the deploy."}, + "function": {"likely_to_drift": true, "why": "Code and configuration can be updated directly (UpdateFunctionCode/Configuration) outside the deploy; the package-integrity check compares the live code hash with the inventoried one."}, + "iam_role": {"likely_to_drift": true, "why": "Trust and attached policies are the highest-value change an intruder or a hurried operator makes outside Terraform."}, + "iam_policy": {"likely_to_drift": true, "why": "Inline policies can be edited in the console; privilege creep is the drift that matters most."}, + "iam_group": {"likely_to_drift": true, "why": "The operator groups carry hand-attached managed policies (bootstrap stack, applied by hand)."}, + "oidc_provider": {"likely_to_drift": true, "why": "Audience list changes would widen who can federate into the deploy roles."}, + "identity_provider": {"likely_to_drift": true, "why": "MFA, password and sign-up settings of the user pool are console-editable."}, + "api_gateway": {"likely_to_drift": true, "why": "Routes, authorizers, throttling and access logging are console-editable and govern the app's exposure."}, + "kms_key": {"likely_to_drift": true, "why": "Keys can be disabled, scheduled for deletion or have rotation turned off."}, + "secrets_manager": {"likely_to_drift": true, "why": "Rotation lapses with time even when nobody touches the secret."}, + "tls_certificate": {"likely_to_drift": true, "why": "Validity runs out with time; renewal can fail silently."}, + "dns_zone": {"likely_to_drift": true, "why": "DNSSEC signing can stop (key state, registrar) without any Terraform change."}, + "audit_log_trail": {"likely_to_drift": true, "why": "Logging can be stopped with one API call (StopLogging), a classic intruder step."}, + "log_group": {"likely_to_drift": false, "why": "Created and changed only by Terraform; retention and key are still re-validated daily."}, + "event_schedule": {"likely_to_drift": false, "why": "Created and changed only by Terraform; a disabled schedule is still caught daily."}, + "notification_topic": {"likely_to_drift": false, "why": "Created and changed only by Terraform; encryption is still re-validated daily."}, + "metric_alarm": {"likely_to_drift": false, "why": "Created and changed only by Terraform; disabled actions are still caught daily."}, + "message_queue": {"likely_to_drift": false, "why": "Created and changed only by Terraform; encryption is still re-validated daily."}, + "kv_table": {"likely_to_drift": false, "why": "The state-lock table is created by the bootstrap stack and not otherwise touched; point-in-time recovery is still re-validated daily."} + }, + "excluded_types": { + "npm_package": "Software, not a machine resource: its content is fixed by the lockfile integrity hash in the deployed artifact. Covered by Syft and Grype twice daily (evidence-nightly.yml) and by the runtime package-integrity check of the function that ships it.", + "pypi_package": "Software, not a machine resource: fixed by the deployed artifact. Covered by Syft and Grype twice daily and by the runtime package-integrity check of the function that ships it.", + "html_artifact": "Static content, not a machine resource: hashed into the inventory and scanned for accessibility on every deploy; the bucket that serves it is a machine component.", + "external_service": "A third party outside the boundary (Sigstore, GitHub, the vulnerability feeds, the MFA provider): this system cannot read its configuration. Tracked in data/third-party-components.json." + } +} diff --git a/infrastructure/schemas/service-model.schema.json b/infrastructure/schemas/service-model.schema.json deleted file mode 100644 index 54b5b3ba..00000000 --- a/infrastructure/schemas/service-model.schema.json +++ /dev/null @@ -1,102 +0,0 @@ -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "$id": "https://samaydlette.com/.well-known/service-model.schema.json", - "title": "Service model: CSP, CSOs, features and services", - "description": "Constrains docs/portfolio/service-model.json. Referential rules (every boundary group is used by exactly one service, owners exist in the governance registry, features and sources resolve) are enforced by tests/test_service_model.py.", - "type": "object", - "additionalProperties": false, - "required": ["version", "about", "csp", "shared_services", "csos", "features", "sources", "services"], - "properties": { - "version": {"type": "integer", "minimum": 1}, - "about": {"type": "string", "minLength": 1}, - "csp": {"$ref": "#/$defs/named_urn"}, - "shared_services": {"$ref": "#/$defs/named_urn"}, - "csos": { - "type": "array", - "minItems": 1, - "items": { - "type": "object", - "additionalProperties": false, - "required": ["key", "id", "name", "owner_domain"], - "properties": { - "key": {"$ref": "#/$defs/key"}, - "id": {"$ref": "#/$defs/urn"}, - "name": {"type": "string", "minLength": 1}, - "owner_domain": {"$ref": "#/$defs/key"} - } - } - }, - "features": { - "type": "array", - "items": { - "type": "object", - "additionalProperties": false, - "required": ["key", "cso", "name"], - "properties": { - "key": {"$ref": "#/$defs/key"}, - "cso": {"$ref": "#/$defs/key"}, - "name": {"type": "string", "minLength": 1} - } - } - }, - "sources": { - "type": "array", - "items": { - "type": "object", - "additionalProperties": false, - "required": ["key", "description"], - "properties": { - "key": {"$ref": "#/$defs/key"}, - "description": {"type": "string", "minLength": 1}, - "repo_path": {"type": "string", "minLength": 1} - } - } - }, - "services": { - "type": "array", - "minItems": 1, - "items": { - "type": "object", - "additionalProperties": false, - "required": ["key", "name", "owner_domain", "consumed_by", "features"], - "anyOf": [{"required": ["group"]}, {"required": ["selectors"]}], - "properties": { - "key": {"$ref": "#/$defs/key"}, - "name": {"type": "string", "minLength": 1}, - "group": {"$ref": "#/$defs/key"}, - "selectors": { - "type": "array", - "minItems": 1, - "items": { - "type": "object", - "additionalProperties": false, - "required": ["type"], - "oneOf": [{"required": ["id_glob"]}, {"required": ["source"]}], - "properties": { - "type": {"enum": ["html_artifact", "npm_package", "pypi_package"]}, - "id_glob": {"type": "string", "minLength": 1}, - "source": {"$ref": "#/$defs/key"} - } - } - }, - "owner_domain": {"$ref": "#/$defs/key"}, - "consumed_by": {"type": "array", "minItems": 1, "uniqueItems": true, "items": {"$ref": "#/$defs/key"}}, - "features": {"type": "array", "uniqueItems": true, "items": {"$ref": "#/$defs/key"}} - } - } - } - }, - "$defs": { - "key": {"type": "string", "pattern": "^[a-z0-9]+(-[a-z0-9]+)*$"}, - "urn": {"type": "string", "pattern": "^urn:samaydlette:[a-z0-9:-]+$"}, - "named_urn": { - "type": "object", - "additionalProperties": false, - "required": ["id", "name"], - "properties": { - "id": {"$ref": "#/$defs/urn"}, - "name": {"type": "string", "minLength": 1} - } - } - } -} diff --git a/infrastructure/schemas/vdr-activities.schema.json b/infrastructure/schemas/vdr-activities.schema.json new file mode 100644 index 00000000..7ed143e7 --- /dev/null +++ b/infrastructure/schemas/vdr-activities.schema.json @@ -0,0 +1,49 @@ +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "title": "VDR activities outside the pipeline (VER-RPT-HLO)", + "description": "Validated in code by scripts/build-vdr-monthly.py validate_activities (the deploy installs no jsonschema).", + "type": "object", + "additionalProperties": false, + "required": ["schema", "programs", "activities"], + "properties": { + "$schema": {"type": "string"}, + "$comment": {"type": "string"}, + "schema": {"const": "vdr-activities/1"}, + "programs": { + "type": "object", + "additionalProperties": false, + "required": ["vdp", "bug-bounty", "penetration-testing"], + "properties": { + "vdp": {"$ref": "#/$defs/program"}, + "bug-bounty": {"$ref": "#/$defs/program"}, + "penetration-testing": {"$ref": "#/$defs/program"} + } + }, + "activities": { + "type": "array", + "items": { + "type": "object", + "additionalProperties": false, + "required": ["id", "kind", "date", "performed_by", "summary", "evidence", "recorded_by"], + "properties": { + "id": {"type": "string", "pattern": "^ACT-\\d{3}$"}, + "kind": {"enum": ["vdp-report", "bug-bounty", "penetration-test", "assessment", "manual-scan"]}, + "date": {"type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$"}, + "end_date": {"type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$"}, + "performed_by": {"type": "string", "minLength": 1}, + "summary": {"type": "string", "minLength": 1}, + "evidence": {"type": "string", "minLength": 1}, + "recorded_by": {"type": "string", "minLength": 1} + } + } + } + }, + "$defs": { + "program": { + "type": "object", + "additionalProperties": false, + "required": ["active", "note"], + "properties": {"active": {"type": "boolean"}, "note": {"type": "string", "minLength": 1}} + } + } +} diff --git a/infrastructure/watchdog.tf b/infrastructure/watchdog.tf index 16f1777f..19764d91 100644 --- a/infrastructure/watchdog.tf +++ b/infrastructure/watchdog.tf @@ -14,7 +14,7 @@ # nightly's status beacon and every other signed output under # /.well-known/) straight from the site bucket # -> CloudWatch metrics (Samaydlette/Evidence) -# -> four alarms -> SNS topic (CMK-encrypted) -> operator email +# -> five alarms -> SNS topic (CMK-encrypted) -> operator email # # The freshness windows are governed values (REQ-PUB-2, REQ-GOV-1). They are # read here with jsondecode(file(...)): the alarm thresholds, the objects the @@ -30,7 +30,8 @@ # Terraform lands in state and in the uploaded plan artifact of a public repo. # It is created once, out of band (docs/runbooks/evidence-sla-alarm.md). # -# Cost: four standard alarms plus four custom metrics, roughly $1.60/month. +# Cost: five standard alarms plus five custom metrics, roughly $2.00/month (the +# fifth pair, for overdue incident reports, adds about $0.40). # Every listed artifact feeds one StaleArtifacts count rather than a metric # each, so the cost stays flat as the list grows. # SNS email at this volume and 720 short invocations a month are within free @@ -78,6 +79,14 @@ locals { threshold = 0 summary = "At least one published /.well-known/ artifact is older than its governed freshness window, or unreadable. The watchdog's log names which." } + # The Class C incident report clocks (IEC-CSO-IIR/OIR/FIR) are hours, not + # days, so this reads the deadlines the incident log lists rather than the + # log's age, and pages once one has passed without its report. + "incident-report-overdue" = { + metric = "IncidentReportsOverdue" + threshold = 0 + summary = "An incident report is past its FedRAMP Class C deadline and has not been issued, or the incident log is unreadable. /.well-known/incident-reports.json lists what is due; issue it by adding the report to data/incidents.json." + } } } diff --git a/infrastructure/watchdog/index.mjs b/infrastructure/watchdog/index.mjs index dd1b50af..e744b5b3 100644 --- a/infrastructure/watchdog/index.mjs +++ b/infrastructure/watchdog/index.mjs @@ -25,6 +25,9 @@ // missing, or is too old to trust; else 0 // StaleArtifacts how many listed artifacts are past their governed // window, unreadable, or without a usable timestamp +// IncidentReportsOverdue how many incident reports the published incident +// log lists as due whose Class C deadline has passed +// (1 if the log is missing or unreadable) // // A missing or invalid config fails the run before anything is published; the // alarms read the missing data as a breach and page. diff --git a/infrastructure/watchdog/logic.mjs b/infrastructure/watchdog/logic.mjs index 97692b70..8e896f03 100644 --- a/infrastructure/watchdog/logic.mjs +++ b/infrastructure/watchdog/logic.mjs @@ -13,10 +13,11 @@ export const KEYS = { vdr: '.well-known/vdr-report.json', runtime: '.well-known/ksi-signal-runtime.json', status: '.well-known/vdr-status.json', + incidents: '.well-known/incident-reports.json', }; // Every artifact a metric below depends on. The config must list them. -export const REQUIRED = [KEYS.vdr, KEYS.runtime, KEYS.status, '.well-known/boundary-corroboration.json']; +export const REQUIRED = [KEYS.vdr, KEYS.runtime, KEYS.status, KEYS.incidents, '.well-known/boundary-corroboration.json']; // Reported when an artifact cannot be read or has no usable timestamp. Far past // any threshold, so it reads as a breach on every alarm. @@ -98,6 +99,22 @@ export function nightlyFailed(status, maxBeaconAgeHours, now = Date.now()) { return status.result === 'success' ? 0 : 1; } +// How many incident reports are past their Class C deadline and not issued +// (IEC-CSO-IIR/OIR/FIR). The incident log lists each report still due with its +// deadline (scripts/build-incident-report.py, obligations_due); this counts the +// ones whose time has passed on AWS's clock, so a missed one-hour Initial +// report pages within the hour even if nothing republishes the log. A log that +// is missing, unreadable or has no list is a breach (1), never zero. +export function incidentReportsOverdue(log, now = Date.now()) { + if (!log || typeof log !== 'object' || !Array.isArray(log.obligations_due)) return 1; + let overdue = 0; + for (const d of log.obligations_due) { + const due = Date.parse(d && d.due_at); + if (Number.isNaN(due) || due < now) overdue += 1; + } + return overdue; +} + // Every listed artifact past its window, or unreadable, or without a usable // timestamp. One metric for all of them keeps the cost flat as the list grows; // the log line names which. @@ -123,12 +140,13 @@ export function computeMetrics(config, readings, now = Date.now()) { RuntimeSignalAgeHours: age(KEYS.runtime), NightlyFailed: nightlyFailed(parsedBody(readings[KEYS.status]), config.windows[KEYS.status], now), StaleArtifacts: stale.length, + IncidentReportsOverdue: incidentReportsOverdue(parsedBody(readings[KEYS.incidents]), now), }, stale, }; } -const COUNTS = new Set(['NightlyFailed', 'StaleArtifacts']); +const COUNTS = new Set(['NightlyFailed', 'StaleArtifacts', 'IncidentReportsOverdue']); export function metricData(metrics, now) { return Object.entries(metrics).map(([MetricName, Value]) => ({ diff --git a/policies/triage.rego b/policies/triage.rego index 8058d105..63a27f20 100644 --- a/policies/triage.rego +++ b/policies/triage.rego @@ -19,7 +19,7 @@ # # Per finding, in order: # 1. fully mitigated a verified mitigation with effect "full" (rule 1) -# 2. impact the scale's lowest level when fully mitigated, else PAIN +# 2. impact N0 when fully mitigated (VER-EVA-EPA), else PAIN # 3. reachability inventory (REQ-IRV-6); unresolved or package => IRV; # a verified "not-reachable" mitigation => NIRV # 4. exploitability Figure 7, first match decides; then a verified @@ -29,9 +29,15 @@ # 5. disposition check-ID decision record, else the register entry; # a lapsed or invalid record is absent (REQ-DSP-2) # 6. deadline clock start + Class C timeframe; likely overdue -# inside the governed margin; accepted past VER-TFR-MAV -# 7. blocking KEV (even when dispositioned) > closed > top impact -# level + LEV + IRV > past the deadline +# inside the governed margin; accepted past VER-TFR-MAV, +# or earlier when the projected remediation is past it +# 7. grouping VER-EVA-GRV: findings sharing a group are evaluated at +# their most exposed member; the group's clock starts at +# its earliest member and its deadline binds every member +# 8. evaluation time VER-TFR-EVU: evaluated later than the rules allow after +# detection, or still resting on a default after it +# 9. blocking KEV (even when dispositioned) > closed > top impact +# level + LEV + IRV > past the deadline (own or group's) # ============================================================================= package vdr.triage @@ -65,6 +71,21 @@ lowest_level := levels[0] top_level := levels[count(levels) - 1] +# VER-EVA-EPA added N0 (October 2026) for an impact removed entirely: a fully +# mitigated finding takes it. N0 has no timeframe in VDR-TFR-PVR. Read from the +# rule's own scale; a rules file without N0 keeps the timeframe table's lowest. +epa_rule := object.get(data.rules.FRR.VER.data.all, ["EVA", "VER-EVA-EPA"], {}) + +mitigated_level := "N0" if { + some b in object.get(epa_rule, "following_information_bullets", []) + startswith(b, "**N0**") +} else := lowest_level + +level_index(p) := i if { + some i, l in levels + l == p +} else := -1 + mav_rule := data.rules.FRR.VER.data.all.TFR["VER-TFR-MAV"] mav_cell := c if { @@ -104,7 +125,7 @@ errors contains msg if { some i, item in input.items item.kind == "finding" d := decisions[i] - d.pain != lowest_level + not d.pain in {lowest_level, mitigated_level} d.sla_days == null msg := sprintf("%v: no Class C timeframe for %v/%v/%v in data.rules", [d.id, d.pain, d.lev, d.irv]) } @@ -181,7 +202,7 @@ fm_bool(item) if { fully_mitigated(item) } else := false -impact(item) := lowest_level if { +impact(item) := mitigated_level if { fully_mitigated(item) } else := item.pain @@ -379,6 +400,42 @@ accepted_now(needs, ns) if { input.now_ns >= ns } else := false +# VER-TFR-MAV "will not be": a finding whose projected remediation (a decision's +# planned date, passed in as projected_ns) falls after the maximum period is +# accepted now, not when the period runs out. +projected_past(needs, item, ns) if { + needs == true + ns != null + p := object.get(item, "projected_ns", null) + is_number(p) + p > ns +} else := false + +accepted_basis(needs, item, ns) := "maximum-period-passed" if { + accepted_now(needs, ns) +} else := "projected-past-maximum-period" if { + projected_past(needs, item, ns) +} else := null + +# ---- 8. evaluation time (VER-TFR-EVU) ------------------------------------------------------ +# input.evaluation_days is read from the rules by scripts/_rules.py. A finding +# is late when its first evaluation came more than that many days after the +# source detected it, or when, that long after detection, it is still open on a +# default (no exploit-prediction score and no vector: Figure 7's last step). +evaluation_late(item, l, needs) := "evaluated-late" if { + is_number(object.get(input, "evaluation_days", null)) + d := object.get(item, "detected_ns", null) + is_number(d) + object.get(item, "evaluated_ns", item.clock.first_evaluated_ns) - d > input.evaluation_days * day_ns +} else := "default-after-evaluation-window" if { + is_number(object.get(input, "evaluation_days", null)) + needs == true + l[1] == "no-score" + object.get(item, "default_evaluation", false) == true + d := object.get(item, "detected_ns", item.clock.first_evaluated_ns) + input.now_ns - d > input.evaluation_days * day_ns +} else := null + # ---- 7. blocking --------------------------------------------------------------------------- # KEV is tested before the disposition: a register entry never buys a known # exploited vulnerability out of the gate. @@ -403,7 +460,7 @@ label_of(disposition, label) := disposition if { disposition != null } else := label -decide(item) := { +base(item) := { "id": item.id, "fully_mitigated": fm, "pain": pain, @@ -423,10 +480,12 @@ decide(item) := { "due_ns": dl.due_ns, "is_overdue": dl.is_overdue, "will_be_overdue": dl.will_be_overdue, - "accepted": accepted_now(needs, acc), + "accepted": accepted_basis(needs, item, acc) != null, + "accepted_basis": accepted_basis(needs, item, acc), "accepted_ns": acc, - "blocking": rule != null, - "block_rule": rule, + "evaluation_late": evaluation_late(item, l, needs), + "start_ns": field_or_null(item.clock, "start_ns"), + "is_kev": item.is_kev == true, } if { fm := fm_bool(item) pain := impact(item) @@ -440,7 +499,183 @@ decide(item) := { sla := timeframe(pain, l[0], r[0]) dl := deadline(item, sla, needs) acc := accepted_ns(item) - rule := block_rule(item.is_kev == true, closed, pain, l[0], r[0], dl.is_overdue) } -decisions := [decide(item) | some item in input.items] +base_decisions := [base(item) | some item in input.items] + +# ---- 7. grouping (VER-EVA-GRV) ----------------------------------------------------------- +# input.items[i].group names the finding's group (a CVE, a decision record, or a +# check ID); a finding without one is its own group. The group is evaluated at +# its most exposed open member: the highest impact, LEV if any member is, IRV if +# any member is, the clock from its earliest member. The group's deadline binds +# each open member, so a new instance of an old group does not get a new clock. +group_key(i) := g if { + g := input.items[i].group + is_string(g) + g != "" +} else := sprintf("item:%d", [i]) + +open_members(g) := [j | + some j, it in input.items + it.kind == "finding" + group_key(j) == g + base_decisions[j].needs_remediation == true + level_index(base_decisions[j].pain) >= 0 +] + +group_eval(g) := { + "pain": levels[max([level_index(base_decisions[j].pain) | some j in m])], + "lev": any_true([base_decisions[j].lev | some j in m]), + "irv": any_true([base_decisions[j].irv | some j in m]), + "start_ns": min([base_decisions[j].start_ns | some j in m]), + "members": count(m), +} if { + m := open_members(g) + count(m) > 0 +} else := null + +field_or_null(o, k) := o[k] if { + is_object(o) +} else := null + +past_bool(due) if { + past(due) +} else := false + +any_true(xs) if { + some x in xs + x == true +} else := false + +group_deadline(ge) := {"due_ns": null, "is_overdue": false} if { + ge == null +} else := {"due_ns": null, "is_overdue": false} if { + timeframe(ge.pain, ge.lev, ge.irv) == null +} else := {"due_ns": due, "is_overdue": past_bool(due)} if { + due := ge.start_ns + (timeframe(ge.pain, ge.lev, ge.irv) * day_ns) +} + +own_or_group_overdue(b, gd) if { + b.is_overdue == true +} else if { + b.needs_remediation == true + gd.is_overdue == true +} else := false + +decide(i) := object.union(b, { + "group": g, + "group_pain": field_or_null(ge, "pain"), + "group_lev": field_or_null(ge, "lev"), + "group_irv": field_or_null(ge, "irv"), + "group_due_ns": gd.due_ns, + "is_overdue": is_overdue, + "blocking": rule != null, + "block_rule": rule, +}) if { + b := base_decisions[i] + g := group_key(i) + ge := group_eval(g) + gd := group_deadline(ge) + is_overdue := own_or_group_overdue(b, gd) + rule := block_rule(b.is_kev, b.closed, b.pain, b.lev, b.irv, is_overdue) +} + +decisions := [decide(i) | some i, _ in input.items] + +# ============================================================================= +# VULNERABILITIES TREATED AS FEDRAMP REPORTABLE INCIDENTS (VER-TFR-IRI, -NRI) +# ============================================================================= +# Entry points, over the findings of a built VDR report (input.findings): +# data.vdr.triage.incident_triggers one entry per finding a rule makes a +# FedRAMP Reportable Incident +# data.vdr.triage.incident_errors non-empty => the caller fails closed +# +# The N-rating comparisons are read from the Class C rule text in data.rules, +# not restated here: "N-rating > 3 ... until ... at N3 or below" (IRI) and +# "N-rating = 5 ... until ... at N4 or below" (NRI). A rule stays in force for a +# finding until its current rating (after partial mitigation) is at or below +# the "until" level, which for both rules is the trigger level's complement. +# A false positive is not a vulnerability and a fully mitigated finding is not +# exploitable, so neither triggers. Whether the operator has adopted each rule +# (IRI is a SHOULD, NRI a MAY at Class C) is the incident register's policy, +# applied by scripts/build-incident-report.py. +ver_tfr := data.rules.FRR.VER.data.all.TFR + +class_c_statement(rid) := s if { + s := ver_tfr[rid].varies_by_class.c.statement +} else := ver_tfr[rid].statement + +rule_digit(pattern, rid) := to_number(m[0][1]) if { + m := regex.find_all_string_submatch_n(pattern, class_c_statement(rid), 1) + count(m) == 1 +} + +iri_above := rule_digit(`N-rating > ([0-9])`, "VER-TFR-IRI") + +iri_until := rule_digit(`at N([0-9]) or below`, "VER-TFR-IRI") + +nri_equals := rule_digit(`N-rating = ([0-9])`, "VER-TFR-NRI") + +nri_until := rule_digit(`at N([0-9]) or below`, "VER-TFR-NRI") + +incident_errors contains "VER-TFR-IRI Class C statement no longer reads 'N-rating > n ... at Nn or below'" if { + not iri_above +} + +incident_errors contains "VER-TFR-IRI Class C statement no longer reads 'N-rating > n ... at Nn or below'" if { + not iri_until +} + +incident_errors contains "VER-TFR-NRI Class C statement no longer reads 'N-rating = n ... at Nn or below'" if { + not nri_equals +} + +incident_errors contains "VER-TFR-NRI Class C statement no longer reads 'N-rating = n ... at Nn or below'" if { + not nri_until +} + +# The trigger and the exit must be complements; anything else is a changed rule +# that needs reading before it is trusted. +incident_errors contains "VER-TFR-IRI: the trigger and the 'until' level are not complements" if { + iri_above != iri_until +} + +incident_errors contains "VER-TFR-NRI: the trigger and the 'until' level are not complements" if { + nri_until != nri_equals - 1 +} + +incident_errors contains msg if { + some f in input.findings + not regex.match(`^N[0-9]$`, sprintf("%v", [f.pain])) + msg := sprintf("%v: impact %v is not an N-rating", [f.tracking_id, f.pain]) +} + +pain_number(p) := to_number(substring(p, 1, -1)) + +still_a_vulnerability(f) if { + f.fully_mitigated != true + f.final_disposition != "false-positive" +} + +incident_rule(f) := "VER-TFR-IRI" if { + f.internet_reachable == true + f.likely_exploitable == true + pain_number(f.pain) > iri_above +} else := "VER-TFR-NRI" if { + f.internet_reachable == false + f.likely_exploitable == true + pain_number(f.pain) == nri_equals +} + +incident_triggers := [t | + some f in input.findings + still_a_vulnerability(f) + rule := incident_rule(f) + t := { + "tracking_id": f.tracking_id, + "cve": object.get(f, "cve", null), + "rule": rule, + "pain": f.pain, + "first_evaluated": object.get(f, "first_evaluated", null), + } +] diff --git a/policies/triage_test.rego b/policies/triage_test.rego index c8af8841..4f6aadea 100644 --- a/policies/triage_test.rego +++ b/policies/triage_test.rego @@ -254,3 +254,105 @@ test_observed_reachability_beats_not_reachable_mitigation if { }) d.irv_basis == "observed" } + +# ---- VER-TFR-IRI / VER-TFR-NRI: vulnerabilities treated as incidents ------------------ +iri_text := concat(" ", [ + "Providers with Class C Certifications SHOULD treat internet-reachable likely exploitable vulnerabilities", + "where Potential Agency Impact N-rating > 3 as a FedRAMP Reportable Incident", + "until they are partially mitigated vulnerabilities at N3 or below.", +]) + +nri_text := concat(" ", [ + "Providers with Class C Certifications MAY treat likely exploitable vulnerabilities that are NOT internet-reachable", + "where Potential Agency Impact N-rating = 5 as a FedRAMP Reportable Incident", + "until they are partially mitigated vulnerabilities at N4 or below.", +]) + +ver_rules(iri, nri) := {"FRR": {"VER": {"data": {"all": {"TFR": { + "VER-TFR-IRI": {"varies_by_class": {"c": {"statement": iri}}}, + "VER-TFR-NRI": nri, +}}}}}} + +good_ver := ver_rules(iri_text, {"varies_by_class": {"c": {"statement": nri_text}}}) + +vf := { + "tracking_id": "t1", "cve": "CVE-2099-0001", "pain": "N4", "internet_reachable": true, + "likely_exploitable": true, "fully_mitigated": false, "final_disposition": "open", + "first_evaluated": "2026-11-01T00:00:00+00:00", +} + +triggers(patch, r) := ts if { + ts := triage.incident_triggers with data.rules as r + with input as {"findings": [object.union(vf, patch)]} +} + +ierrs(findings, r) := es if { + es := triage.incident_errors with data.rules as r with input as {"findings": findings} +} + +test_iri_opens_above_n3 if { + ts := triggers({}, good_ver) + ts == [{ + "tracking_id": "t1", "cve": "CVE-2099-0001", "rule": "VER-TFR-IRI", "pain": "N4", + "first_evaluated": "2026-11-01T00:00:00+00:00", + }] + triggers({"pain": "N5"}, good_ver)[0].rule == "VER-TFR-IRI" +} + +test_iri_ends_at_n3_or_below if { + triggers({"pain": "N3"}, good_ver) == [] + triggers({"pain": "N1"}, good_ver) == [] +} + +test_nri_opens_only_at_n5 if { + triggers({"internet_reachable": false, "pain": "N5"}, good_ver)[0].rule == "VER-TFR-NRI" + triggers({"internet_reachable": false, "pain": "N4"}, good_ver) == [] +} + +test_not_likely_exploitable_never_triggers if { + triggers({"likely_exploitable": false, "pain": "N5"}, good_ver) == [] + triggers({"likely_exploitable": false, "internet_reachable": false, "pain": "N5"}, good_ver) == [] +} + +test_false_positive_and_fully_mitigated_never_trigger if { + triggers({"final_disposition": "false-positive", "pain": "N5"}, good_ver) == [] + triggers({"fully_mitigated": true, "pain": "N5"}, good_ver) == [] +} + +test_accepted_still_triggers if { + triggers({"final_disposition": "accepted", "pain": "N5"}, good_ver)[0].rule == "VER-TFR-IRI" +} + +test_missing_cve_is_null if { + ts := triage.incident_triggers with data.rules as good_ver + with input as {"findings": [object.remove(vf, ["cve", "first_evaluated"])]} + ts[0].cve == null + ts[0].first_evaluated == null +} + +test_rules_read_cleanly if { + ierrs([vf], good_ver) == set() +} + +test_changed_iri_text_fails_closed if { + es := ierrs([vf], ver_rules("treat them as incidents", {"statement": nri_text})) + "VER-TFR-IRI Class C statement no longer reads 'N-rating > n ... at Nn or below'" in es +} + +test_changed_nri_text_fails_closed if { + es := ierrs([vf], ver_rules(iri_text, {"statement": "treat them as incidents"})) + "VER-TFR-NRI Class C statement no longer reads 'N-rating = n ... at Nn or below'" in es +} + +test_non_complement_fails_closed if { + bad_iri := replace(iri_text, "at N3 or below", "at N2 or below") + bad_nri := replace(nri_text, "at N4 or below", "at N3 or below") + es := ierrs([vf], ver_rules(bad_iri, {"statement": bad_nri})) + "VER-TFR-IRI: the trigger and the 'until' level are not complements" in es + "VER-TFR-NRI: the trigger and the 'until' level are not complements" in es +} + +test_bad_rating_fails_closed if { + es := ierrs([object.union(vf, {"pain": "high"})], good_ver) + "t1: impact high is not an N-rating" in es +} diff --git a/reports/assumption-verification.md b/reports/assumption-verification.md deleted file mode 100644 index 92f34169..00000000 --- a/reports/assumption-verification.md +++ /dev/null @@ -1,73 +0,0 @@ -# Assumption Verification Report - -Phase 1 of the OPA-gate showcase refactor. Every claim from the external static -review was re-verified locally against commit `678ec21` (branch point of -`refactor/opa-showcase`) with the repo's pinned OPA v0.57.0 -(`/usr/local/bin/opa`, Build 2023-09-28). - -Statuses: **CONFIRMED** (claim holds as written), **PARTIAL** (core holds, -details differ — recommendation adapted), **REFUTED** (claim does not hold — -dependent recommendation skipped or re-scoped). - -| ID | Claim | Status | Evidence (command + output excerpt) | Dependent recommendations | -|----|-------|--------|-------------------------------------|---------------------------| -| A1 | `infrastructure/policies.rego` exists, is the **only** `.rego` in the repo, declares `package terraform.compliance`, pre-1.0 syntax | **PARTIAL** | `find . -name '*.rego'` → 5 first-party files (`infrastructure/policies.rego`, `infrastructure/policies_test.rego`, `policies/triage.rego`, `policies/triage_test.rego`, `scuba/policies/*.rego` ×2) plus ~300 generated `scuba/dist/policies/*.rego`. The target file itself matches the review exactly: line 17 `package terraform.compliance`; bracket-style partial sets (e.g. line 39 `missing_required_tags[tag] {`); no `if`, no `import rego.v1`. Line-precise matches for A3/A6/A8 (regex at line 230, union at line 318, `default compliant = true` at line 290) prove the review inspected **this exact file** — only the repo-wide "only .rego" conjunct is stale. | All. Adaptation: scope is `infrastructure/policies.rego` + its harness; `policies/triage.rego` is co-migrated in R1 **only** because CI tests it with the same pinned OPA binary (`deploy-with-opa.yml:136`). `scuba/` rego is not evaluated by this workflow and is untouched. | -| A2 | OPA v0.57.0 pinned in README/scripts/CI | **CONFIRMED** | `grep -rn "0\.57" README.md scripts/ Makefile .github/` → 5 hits: `README.md:301`, `scripts/terraform-plan.sh:32`, `scripts/deploy.sh:37`, `.github/workflows/deploy-with-opa.yml:78` (`OPA_VERSION: 0.57.0`), `Makefile:33`. | R1 | -| A3 | `alt`-text rule uses RE2-rejected lookahead `(?!alt=)`; silently never fires by default; errors under `--strict-builtin-errors` | **CONFIRMED** (dynamic repro) | Pattern at `policies.rego:231`. Fixture `{"html_content": "...<img src=\"x\">...", "file_name": "t.html"}`: default eval → `compliant: True, violations: []` (no `missing_alt_text`); with `--strict-builtin-errors` → `regex.find_all_string_submatch_n: error parsing regexp: invalid or unsupported Perl syntax: '(?!'` at row 230. Silent false pass confirmed. | R7, R8 | -| A4 | Bespoke input contract: rules read pre-flattened `input.resource` with synthesized fields, produced by a wrapper | **CONFIRMED** | 20 `input.resource.*` references in the rego. Flattener is an inline Python heredoc in `scripts/terraform-plan.sh` (lines 94–193): reads `tfplan.json` (`terraform show -json`), synthesizes `versioning_enabled` / `encryption_enabled` / `public_access_blocked` by joining `aws_s3_bucket_versioning` / `..._server_side_encryption_configuration` / `..._public_access_block` sub-resources on substring bucket-name match, then evals OPA **once per resource** (line 218). | R2 | -| A5 | README pipes raw `terraform show -json` into `opa eval` → vacuous `compliant: true` | **CONFIRMED** (dynamic repro) | `README.md:266–267` shows exactly that pipe. Synthetic raw-plan fixture (an S3 bucket with no tags, no versioning, no encryption — should be maximally non-compliant) → `compliant: True, total_violations: 0`. Fail-open reproduced. | R2 | -| A6 | `all_violations` = hardcoded union of exactly 4 sets; `compliant` = `default true` + 4 `false` overrides | **CONFIRMED** | `policies.rego:290` `default compliant = true`; lines 293–309 four `compliant = false { count(...) > 0 }` rules; line 318 `all_violations := ((s3_bucket_violations \| cloudfront_violations) \| accessibility_violations) \| classification_violations`. | R4 | -| A7 | Runtime Lambda **re-implements** the rules in JavaScript (no Wasm, no OPA runtime) | **REFUTED** | `infrastructure/lambda/index.js:26` `require('@open-policy-agent/opa-wasm')`; lines 72–78 load `policy.wasm` bundled by CI (`deploy-with-opa.yml:267` and `:462` run `opa build -t wasm -e terraform/compliance/compliance_report`). No JS rule logic exists — the Lambda only flattens AWS API responses into the `input.resource` shape and calls `policy.evaluate()`. The review's source was the **stale doc line** `docs/ksi-signal.md:222` ("Runtime emitter ports the same rules to JavaScript"), which no longer matches the code. | R5 → re-scoped: Wasm single-artifact is already shipped; remaining work is a CI parity test (CLI eval vs. Wasm eval over the fixture corpus) + fixing the stale doc line. | -| A8 | Scope asymmetries: 4 governance tags only in `s3_bucket_violations`; `aws_cloudfront_distribution` missing from `taggable_types`; TLS equality-pin vs "or higher" message; misplaced comment | **CONFIRMED** (with intent evidence on one item) | (1) `missing_required_tags` consumed only at `policies.rego:128` inside `s3_bucket_violations` — confirmed. (2) `taggable_types` (lines 65–77) has 11 types, no `aws_cloudfront_distribution` — confirmed; **however** the distribution is a *data source* in the gated stack (`infrastructure/main.tf:123` `data "aws_cloudfront_distribution"`; the managed resource lives in the operator-applied bootstrap stack), and data sources are excluded by `is_managed` — so its absence has a plausible rationale, though adding the type is harmless and future-proof. (3) Line 197 `!= "TLSv1.2_2021"` vs line 200 message "TLS 1.2 or higher" — confirmed. (4) Lines 302–305: comment "Block deployment if any accessibility violations are found" sits above the **classification** override — confirmed, pure comment bug. | R6 | -| A9 | A test harness exists (`scripts/test-policies.sh` and/or make target) — uncharacterized | **PARTIAL** | Two harnesses exist. (1) `scripts/test-policies.sh` (10 scenario cases + perf test) is **broken and cannot run**: every check reads `.result.compliant`, but `opa eval` outputs `.result[0].expressions[0].value.compliant`; first jq errors ("Cannot index array with string \"compliant\"") and `set -e` kills the script — exit 5 on test case 1. Not referenced by CI or Makefile; only by a README directory listing (`README.md:218`). (2) `opa test policies.rego policies_test.rego` (Makefile `validate`, CI `deploy-with-opa.yml:135`) runs and passes 7/7 — but covers **only** the PR-D classification gate. **Neither harness would have caught A3**: the rego tests don't touch accessibility rules, and the shell harness (whose case 7 *is* a missing-alt must-fire test) dies before reaching it. | R7 scoped: replace/supersede the broken shell harness; keep + extend the rego unit tests. | -| A10 | Machine-readable KSI→control catalog exists, parseable, feeds the OSCAL SSP generator (192 implemented-requirements) | **PARTIAL** (core confirmed; count stale) | `infrastructure/schemas/ksi-catalog.json`: parses, 10 KSI families, each indicator carries `controls: [{control_id, title}]` (209 distinct 800-53-style IDs). `scripts/build-oscal-ssp.py:12` names it as input. But the published SSP has **331** implemented-requirements, not 192 (`python3 -c "...len(reqs)"` → 331) — the review's number predates the CR26 work. | R3 (CI diff target confirmed usable) | - -## Gating outcome - -- **A1 is PARTIAL, not REFUTED** — the review demonstrably targeted this repo - state's gate file (four independent line-precise matches). Proceeding, with - the scope adaptation recorded above. -- **A7 REFUTED** → R5 is re-scoped (see table): the recommendation's end state - (one Rego artifact, executed at both enforcement points via Wasm) already - ships in production. What survives of R5 is its parity-test requirement and - a fix for the stale `docs/ksi-signal.md` line that misled the review. -- All other recommendations proceed, adapted where noted. - -## Additional constraints discovered (not in the review) - -These are facts the refactor must respect; recorded here so Phase 3 decisions -are traceable: - -1. **`validations.json` is a load-bearing contract.** `scripts/terraform-plan.sh` - emits it; `scripts/build-ksi-signal.py:1131` (`build_validations`) and - `scripts/build-vdr-report.py` (`--opa validations.json`) consume it. Its - `results[]` entry shape (`kind`, `resource_type`/`resource_name` or - `file_name`/`file_path`, `compliant`, `violations[]`, `policy_version`) must - survive the refactor. The published KSI-signal schema requires violation - objects to keep `type`/`message`/`severity` (severity enum - LOW/MEDIUM/HIGH/CRITICAL) but allows additional fields - (`additionalProperties: true`) — so R4's uniform violation object must be a - superset, not a replacement. -2. **The Wasm entrypoint is referenced in two workflow steps** - (`deploy-with-opa.yml:267`, `:462`) and the Lambda feeds it single-resource - input `{resource: {...}}`. Any repackaging must keep an entrypoint that - accepts that input shape and returns the `compliance_report` fields the - Lambda reads, and both `-e` flags must be updated in lockstep. -3. **`policies/triage.rego` + tests run under the same pinned OPA binary in CI** - (`deploy-with-opa.yml:136`) and use v0 syntax (`import future.keywords.in`, - no `if`). Bumping the pin to 1.x without migrating them breaks CI. They are - co-migrated in R1. -4. **The root `Makefile` is written to run from `infrastructure/`** (relative - `policies.rego`, `./terraform-plan.sh` paths) but lives at the repo root, and - the README says `cd infrastructure && make pipeline`. As-is, several targets - are not copy-paste runnable. Fixed as part of the docs pass (Phase 4). - -## Tool environment recorded for this phase - -| Tool | Version | Source | -|------|---------|--------| -| opa | 0.57.0 (repo pin) | `/usr/local/bin/opa`, matches all five pin sites | -| terraform | not exercised (no plan/apply run in Phase 1; fixtures are synthetic) | — | -| python3 | 3.13.12 | system | -| node / npm | v22.16.0 / 10.9.2 | system (used later for Wasm parity + scanner) | -| chromium | present at `/usr/bin/chromium` | system (enables local pa11y runs for R8) | diff --git a/reports/implementation-report.md b/reports/implementation-report.md deleted file mode 100644 index b363e009..00000000 --- a/reports/implementation-report.md +++ /dev/null @@ -1,316 +0,0 @@ -# Implementation Report — OPA Compliance Gate Showcase Refactor - -Branch: `refactor/opa-showcase` (local only, not pushed). One commit per -phase/recommendation. Companion document: `reports/assumption-verification.md` -(Phase 1 evidence). Everything marked **PROPOSED — needs human review** is my -judgment, not verified fact. - -## Execution order - -Implemented as R1 → R2 → R4 → R6 → R3 → **R9 → R8 → R7** → R5. The last four -deviate from the brief's stated order (R7 → R8 → R9 → R5) for two reasons, -both discovered during implementation: - -1. **R8 before R7:** turning on `--strict-builtin-errors` everywhere (R7) - while the A3 lookahead regex still existed would have made every HTML - evaluation of a page containing `<img` a hard error — the broken builtin - had to be deleted (R8) before strict errors could be global. -2. **R9 before R8:** the real pa11y scan of the live site found two genuine - WCAG 2 AA failures (details under R8). One is a scanner false positive - that had to be dispositioned through the exceptions mechanism — so the - mechanism (R9) had to exist before the scanner (R8) could land with a - green gate. - -## Per-recommendation outcomes - -### R1 — Migrate to OPA 1.x / Rego v1 — **DONE (scope adapted)** -`opa fmt --v0-v1` migration + compatibility-import drop; every 0.57.0 pin -(README, terraform-plan.sh, deploy.sh, Makefile, workflow `OPA_VERSION`) -replaced with **1.18.2**. Adaptation per A1-PARTIAL: `policies/triage.rego` -(+tests) co-migrated because CI evaluates it with the same pinned binary; -`scuba/` rego untouched (not evaluated by this workflow; already -v1-compatible via `future.keywords`). Verified: `opa check --strict` clean, -all tests pass, Wasm built by 1.18.2 executes under the Lambda's -`opa-wasm@^1.9.0`, and regenerating the golden corpus under 1.18.2 produced -**zero** behavioral deltas vs the 0.57.0 baseline. Note: `grep -rn "0\.57"` -still matches the frozen baseline goldens and the Phase 1 report — those are -historical records of the old pin, not executable pins; no executable -reference remains. - -### R2 — Standard input contract — **DONE** -The policy consumes raw `terraform show -json` directly: iterates -`resource_changes`, gates only changes whose after-state exists (delete-only -changes skipped; replace/update/no-op/create kept), joins the provider-4.x -split S3 sub-resources in Rego — exact `bucket`-value match with a -`configuration.root_module.resources[].expressions.bucket.references` -fallback for names computed at apply time. **Documented limitation:** the -fallback only covers root-module resources; a module-nested bucket with a -computed name will not join and its synthesized security fields stay false — -the bucket *fails* the gate (fail-closed) rather than silently passing. -Unrecognized/empty input yields `input_error` + non-compliant. JSON Schema -for all input shapes at `infrastructure/schemas/policy-input/gate_input.json` -wired via package METADATA and enforced with `opa check --strict --schema`. -The Python flattener inside `terraform-plan.sh` is deleted; the script is a -thin wrapper (plan → show → one strict eval → `validations.json`). The -README debug commands were re-tested verbatim after the change. The runtime -Lambda's single-resource input shape is unchanged and covered by fixtures. -Bonus fix found while testing: a nameless resource used to make the violation -object undefined and vanish; normalization now guarantees `name`/`address`. - -### R4 — Package-per-domain, uniform violations, fail-closed — **DONE** -`infrastructure/policies.rego` became `infrastructure/policy/`: `policy.gate` -(the only package that reads raw input), `policy.terraform.s3`, -`policy.terraform.cloudfront`, `policy.tagging`, `policy.accessibility`, and -the `terraform.compliance` aggregator. Uniform violation object: -`{id, type (legacy alias), category, severity, control_ids, ksi_ids, -resource, address, message}` — a strict superset of the published KSI-signal -violation shape (`additionalProperties: true` there). Aggregation is a -`walk(data.policy)` over every `violations` set: proven with a live dummy -package (appeared with zero aggregator edits, removed after) and pinned by a -unit test injecting a mock package. Decision flipped to -`default compliant := false` + one positive rule (valid input ∧ zero active -violations). **Convention discovered and documented:** test packages must -live outside `data.policy` (the walk makes an inside test package statically -recursive). The Wasm entrypoint path and all downstream report shapes are -unchanged. - -### R6 — Parameters as data — **DONE (one A8 item deliberately not "fixed")** -All enforcement parameters live in `infrastructure/policy/config/data.json` -(with an explicit 800-53 ODP comment in `tagging.rego`). TLS is an ordered -minimum: `tls.order` ranks CloudFront policy names, anything at/above -`tls.minimum` passes, unknown names fail closed; tests prove a hypothetical -stronger policy passes via a data-only change. A config guard fails the gate -closed on a missing/partial parameter document — including the Wasm host -never calling `setData`, which *did* evaluate to a silent pass until the -guard's absent-document rule was added (found by testing exactly that case). -The Lambda now ships `policy-data.json` from the bundle and loads it. -A8 fixes: governance tags now enforced uniformly across all taggable types -(five `main.tf` resources gained the missing `CostCenter` tag — verified -with offline `terraform validate`; the Silk Reeling resources already -carried all four via `local.silk_tags`, contrary to my first scan); the -TLS message now matches the check; the misplaced comment is gone with the -restructure. **`aws_cloudfront_distribution` was NOT added to -`taggable_types` — documented intent found:** the gated stack's distribution -is a data source (bootstrap owns the managed resource), and -`lambda/index.js` explicitly documents that the Lambda's role lacks -`cloudfront:ListTagsForResource`, so adding the type would turn every runtime -signal red. Recorded as deliberate scope in `tagging.rego` with the flip -procedure (grow role + transformer, then edit config). - -### R3 — Control traceability via METADATA — **DONE** -Every violation rule carries METADATA `custom:` fields (`id`, `category`, -`severity`, `nist_controls`, `ksi_ids`; Section 508 rules declare -`framework: section-508` with empty NIST lineage). Violations are built from -`rego.metadata.rule()` through a shared constructor — verified the lineage -survives Wasm compilation (the Lambda's findings carry it). -`scripts/check-policy-annotations.py` diffs annotations against -`ksi-catalog.json` in CI: unknown KSIs, controls not carried by the declared -KSIs, orphan control claims, and missing fields all fail (failure mode -proven with a deliberately wrong annotation, then reverted). All mappings -are **PROPOSED** (see below). - -### R7 — Tests and linting as exhibits — **DONE** -50 rego unit tests across per-package `*_test.rego` files with must-fire -negatives for every rule (including absent-field fail-closed postures); -`tests/test_policy_gate.py` runs the full plan-fixture corpus through the -gate with `--strict-builtin-errors` in the existing CI pytest job and pins -verdicts + violation ids + the uniform violation contract. CI enforces: -`opa fmt --fail`, `opa check --strict --schema`, `opa test --coverage ---threshold 90` (actual: **97.1%**), Regal **0.41.1** -(`open-policy-agent/regal` — the project moved from StyraInc; verified) at -**zero findings** — 89 initial findings: ~15 real style/idiom issues fixed -(including one true simplification bug-risk, the superfluous `object.get`), -and three categories ignored with written justification in -`.regal/config.yaml`. The broken `scripts/test-policies.sh` (A9: died on its -first jq expression, never ran in CI) is deleted and superseded. -**A3-reintroduction experiment** (scratch, not committed): re-adding the -lookahead regex was caught statically by Regal (`bugs/invalid-regexp`) and -dynamically by the strict-errors corpus test — while plain `opa test` still -passed 50/50 because no unit test exercised the new rule. That is the -lesson: must-fire tests protect known rules; the linter and strict-error -evals protect against unknown broken ones. - -### R8 — HTML checks out of Rego — **DONE** -The five string/regex rules are deleted (including the dead lookahead rule -and the WCAG-inverting `alt=""` rule — `decorative-empty-alt.html` now -correctly passes). pa11y **9.1.1** (pinned, `tools/a11y/`, WCAG 2 AA via -HTML_CodeSniffer in headless Chromium) produces one JSON facts document; -`policy.accessibility` decides over it — fail-on issue types are config, one -violation per (page, WCAG code) so exceptions can be code-precise. The -pattern is named in both the scanner and the policy: **scanners produce -facts, OPA decides.** The wrapper fails closed when the scanner is -unavailable (`SKIP_A11Y=1` is the explicit local opt-out; CI installs the -scanner against the runner's system Chrome with `PUPPETEER_SKIP_DOWNLOAD`). -The retired `{html_content, file_name}` input shape is now an `input_error`. -Scanning the real site (43 pages) found two genuine WCAG failures the old -string checks could not see: -1. `pages/articles.html` — search input with no accessible name → **fixed** - (`aria-label="Search articles"`). -2. `silk-reeling-mirror.html` — two contrast failures on `aria-hidden` - decorative dot separators → **false positive** per WCAG 1.4.3's - pure-decoration exemption; dispositioned as POAM-033 (poam.md False - Positives + the OSCAL POA&M generator) and suppressed via the exceptions - register (expires 2027-01-15), still visible under `excepted`. - **PROPOSED:** the FP classification and the expiry date are my judgment. - -### R9 — Exceptions-as-code — **DONE** -`infrastructure/policy/exceptions/data.json`: `{resource, rule_id, -justification, expiry, ticket}` (+ optional `code` for finding-level -precision). Suppression happens only in the aggregator; rules keep reporting -raw facts; suppressed findings stay in the report under `excepted` with the -exception that silenced them. Expiry is checked against -`data.runtime.evaluated_at` (supplied as *data* by the wrapper and the -Lambda — inputs stay pure, evaluation stays deterministic/Wasm-clean); no -timestamp or past expiry ⇒ no suppression (fail-safe), and -`scripts/check-exceptions.py` fails CI on expired/malformed entries. -Cross-linked from `docs/poam.md` as POA&M-as-code. Tests cover active -suppression, excepted-visibility, expiry resurfacing, missing-timestamp -fail-safe, and code-scoped precision. - -### R5 — One artifact, two enforcement points — **ADAPTED (A7 refuted)** -The recommendation's end state already ships in production: CI compiles -`infrastructure/policy/` to Wasm and the Lambda executes it via -`@open-policy-agent/opa-wasm`; there is no JS rule logic to delete. The -review was misled by a stale line in `docs/ksi-signal.md` ("Runtime emitter -ports the same rules to JavaScript") — now corrected, along with a matching -stale comment in `scripts/deploy.sh`. What survived of R5 is its parity -requirement, implemented as `scripts/policy-parity-test.js`: the full -fixture corpus through both the OPA CLI and the compiled Wasm, full-report -diff, wired into CI immediately after the exact Wasm that ships is built. -**It found a real divergence on first run:** `sprintf("%v", set)` renders -differently in the Go runtime vs the Wasm JS host (and `%q` throws outright -in the JS host — hit separately during R6 testing). Both fixed in Rego; -parity is green across the corpus. The `compliance_report` entrypoint also -carries `entrypoint: true` METADATA. - -## Behavioral deltas vs the frozen baseline (`tests/golden/baseline/`) - -Post-refactor goldens: `tests/golden/current/` (regenerate with -`tests/golden/regen-current.sh`). Every delta is intentional: - -| Delta | Where | Rationale | -|---|---|---| -| Raw plan JSON evaluated directly now yields real verdicts (baseline: vacuous `compliant: true` for **every** fixture, incl. maximally non-compliant ones) | all `plan-*` goldens | R2 — the fail-open README debug path is now the *only* path | -| Empty/garbage input → `compliant: false` + `input_error` (baseline: vacuous pass; the old flattener crashed outside OPA) | `plan-empty`, `plan-garbage` | R2 input guard | -| `missing-alt` page now fails (baseline: silent pass — dead regex) | a11y goldens | A3 fix via R8 | -| `empty-alt` on a decorative image now **passes** (baseline: failed; the old rule inverted WCAG) | a11y goldens | R8; pa11y implements WCAG correctly | -| `missing-doctype` / `missing-h1` no longer fail per se (not WCAG 2 AA error-level conformance failures) | a11y goldens | R8 — scope now = WCAG 2 AA errors; old checks were bespoke | -| `{html_content, file_name}` input shape retired → `input_error` | a11y goldens | R8 — scanner facts replaced raw HTML input | -| Violation objects gained `id`, `category`, `control_ids`, `ksi_ids`, `address`; messages for tag sets are now sorted/comma-joined; TLS message names the configured floor | all goldens | R4/R3/R5-parity; superset of the published schema shape | -| `compliance_report` gained `excepted`; counts/violations reflect active (non-excepted) findings; `violations_by_type` gained `input` | all goldens | R9/R4 | -| Governance tags enforced beyond S3 (uniform across taggable types, `tags` or `tags_all`) | `missing-classification`-class fixtures, live plan | R6/A8 — with matching `main.tf` tag additions so the real stack stays green | -| Stronger-than-floor TLS policy passes after a config append; unknown policy names fail | cloudfront goldens | R6 ordered minimum | -| `policy_version` `"1.0"` → `"2.0"` | everywhere | input contract + decision-polarity change | -| Nameless resources no longer evade violation reporting | resource goldens | R2 normalization fix | - -Unchanged by design (verified): every legacy single-resource (Lambda-shape) -fixture verdict matches baseline; `compliant-stack`, `data-source-website- -bucket` (documented runtime-covered blind spot), and `delete-only` keep -their verdicts for the right reasons rather than vacuously. - -## Tool versions (pinned) - -| Tool | Version | Where pinned | -|---|---|---| -| OPA | 1.18.2 (was 0.57.0) | workflow `OPA_VERSION`, README, Makefile, terraform-plan.sh, deploy.sh | -| Regal | 0.41.1 (`open-policy-agent/regal`) | workflow `REGAL_VERSION` | -| pa11y | 9.1.1 (exact) | `tools/a11y/package.json` + lockfile | -| @open-policy-agent/opa-wasm | ^1.9.0 (pre-existing) | `infrastructure/lambda/package.json` | -| node (scanner/parity) | >= 20 (engines) | `tools/a11y/package.json`; CI runner node | -| Verification-only (not pinned in repo) | terraform 1.6.3-dev, python 3.13.12, chromium (system) | local validation | - -## PROPOSED — needs human review - -Operator review 2026-07-17: items 1, 2, 3 and 5 below are **ratified**. The -control mappings were reviewed item-by-item — the six clear-cut mappings -confirmed as a set, and the three judgment calls (versioning → KSI-RPL-ABO -with cp-9/cp-10/si-12; input_error → KSI-PIY-RSD with si-10; config_error → -KSI-MLA-EVC with cm-6/ca-7) each confirmed against the considered -alternatives (control trimming, remapping to a gate-integrity KSI, or -carrying no control claim). Item 4 (fixture realism) remains an accepted -limitation with the follow-up noted. - -1. **Every rule→KSI→NIST mapping** in the METADATA annotations - (`s3.rego`, `cloudfront.rego`, `tagging.rego`, `gate.rego`). The CI diff - guarantees *consistency with the catalog*, not correctness of my choices. - Notable judgment calls: versioning → KSI-RPL-ABO (cp-9/cp-10/si-12); - input_error → KSI-PIY-RSD (si-10); config_error → KSI-MLA-EVC (cm-6/ca-7). - *Ratified 2026-07-17 (item-by-item, alternatives considered).* -2. **Severity assignments** — carried over from the pre-refactor strings, now - authoritative in METADATA. *Ratified 2026-07-17.* -3. **POAM-033 disposition** (contrast FP per WCAG 1.4.3) and its 2027-01-15 - expiry; also the `DataClassification`/`CostCenter` values added to five - `main.tf` resources. *Ratified 2026-07-17; the tag change is additionally - verified by CI's plan gate on the PR.* -4. **Fixture realism** — all plan fixtures are synthetic (no credentials → - no real plan). Modeled on terraform 1.9.x / provider-4.x output and the - resource layout observed in public CI logs; labeled in each `_fixture` - block. A real `terraform show -json` capture would be a strictly better - fixture source. -5. **`reports/` publicity** — this report and the Phase 1 report are - committed per the task brief. *Ratified 2026-07-17: they publish with the - branch as showcase artifacts.* - -## Known local-environment caveat (not caused by this branch) - -`pytest tests/` locally fails `test_inject_figures.py::test_published_targets_are_current`: -an **untracked** stale build artifact (`infrastructure/oscal-ssp.json`, June 29, -333 requirements — Phase-2/CR26 local work) disagrees with the published SSP -(331) that README correctly cites. Evidence it predates this branch: artifact -mtime, and published/README agree with each other. In CI the artifact either -doesn't exist (test skips) or is regenerated fresh. Everything else: 164/165 -pass, and the full CI-equivalent policy suite is green end-to-end. - -## Follow-ups recommended (not done) - -1. **CloudFront tag scope flip:** grant the Lambda role - `cloudfront:ListTagsForResource`, grow the transformer, then add - `aws_cloudfront_distribution` to `taggable_types`/`governance_tag_types` - in config (a data-only change once live tags are verified). -2. **Deploy-time blind spot:** the website bucket is a data source, so the - deploy gate never evaluates it (runtime Lambda covers it). Consider a - deploy-time live-read check or importing the bucket. -3. **Signal enrichment:** `build-ksi-signal.py` still maps KSI status at - family level; violations now carry per-rule `ksi_ids` that could drive a - finer per-indicator status. -4. **Runtime `excepted` surfacing:** the runtime signal could publish the - `excepted` list for full external auditability of active exceptions. -5. ~~Checksum-pin the Regal/OPA binaries in CI~~ — **done in the CodeGuard - remediation commit** (see below). -6. ~~Run CodeGuard against the branch diff~~ — **done**; findings and - dispositions below. - -## CodeGuard security review of the branch diff - -Run post-implementation over `git diff main...HEAD` (Project CodeGuard -software-security skill). Scans clean: no hardcoded credentials (the only -account id in fixtures is the AWS documentation placeholder, labeled), no -injection patterns (no shell=True/eval; execFileSync list-form; all shell -expansions quoted; jq fed via --arg/--argjson only), TLS floor consistent -with modern-crypto guidance, no new workflow permissions or secret usage, -and fail-closed behavior at every error path. Findings and dispositions: - -1. **FIXED — real bug caught:** the workflow already pinned the OPA binary - by SHA-256, and the R1 version bump updated `OPA_VERSION` but not - `OPA_SHA256` — every CI job would have failed (closed) at the checksum - step. Updated to the published v1.18.2 hash, verified against the exact - binary used for all of this branch's local verification. -2. **FIXED:** the new Regal download step lacked the checksum verification - the OPA steps have — added `REGAL_SHA256` (from the release's - checksums.txt) + `sha256sum -c`. The operator-run install paths - (deploy.sh, Makefile, README quickstart) now verify the OPA hash too. -3. **FIXED:** `npm ci` for the scanner in the credentialed compliance job - now runs `--ignore-scripts` — none of pa11y's 113 transitive packages - can execute lifecycle scripts there (re-verified the scanner works when - installed this way). -4. **Recorded, not changed (informational):** pa11y executes scanned pages' - JavaScript in headless Chromium inside the credentialed compliance job. - Exposure is limited — the workflow triggers on `pull_request` (fork PRs - receive no secrets), so only content from write-access authors is - rendered, and CI Chromium keeps its sandbox (`--no-sandbox` is a local - opt-in only). Defense-in-depth option if wanted: move the scan to an - uncredentialed job that publishes the facts document as an artifact. -5. **Recorded, not changed (by design):** the exceptions register is a - policy-suppression path gated by PR review. That is the design — - suppressions are diffable, expire, fail CI when stale, and stay visible - under `excepted`. diff --git a/scripts/_assessor.py b/scripts/_assessor.py index 60a4d720..1b259dea 100644 --- a/scripts/_assessor.py +++ b/scripts/_assessor.py @@ -17,11 +17,28 @@ With no records there is nothing to verify and no identity is needed; the SDR states "no assessor record". + +Keyless set (load_assessment): an assessor that signs with Sigstore instead of a +key it holds signs one set file holding all its records. The pinned identity +then names the signing workflow's certificate identity and OIDC issuer +(algorithm SIGSTORE_KEYLESS). The set is accepted only when cosign verifies its +bundle against exactly that identity, and each record in it is accepted only +when it names the pinned assessor and its signature value is the sha256 of its +canonical form (algorithm SIGSTORE_KEYLESS_SET), so a record is bound to the +signed set and cannot be altered alone. The set and its bundle are published, +so anyone can repeat the check. This is how the simulated assessor +(tools/simulated-assessor/, .github/workflows/simulated-assessor.yml) signs. + +Binding: a set states what it covered (subject.commit, the commit whose +repository it verified, and subject.signal_id, the published KSI signal it +validated). The caller states the commit and signal it expects, and +load_assessment refuses a set covering anything else. """ import base64 import copy import hashlib import json +import subprocess # nosec B404: runs cosign with a fixed argument list import sys from pathlib import Path @@ -30,6 +47,9 @@ IDENTITY_PATH = REPO / "infrastructure" / "keys" / "assessor-identity.json" ALGORITHM = "ECDSA_P256_SHA256" +KEYLESS = "SIGSTORE_KEYLESS" # the pinned identity of a keyless assessor +SET_ALGORITHM = "SIGSTORE_KEYLESS_SET" # a record bound to a keyless-signed set +SET_TYPE = "simulated-independent-assessment" KINDS = ("finding", "summary", "comment") REQUIRED = ("record_type", "schema_version", "record_id", "assessor", "issued_at", "kind", "text", "signature") # What an output carries for each record: the signed fields, verbatim, plus the signature. @@ -60,8 +80,8 @@ def _shape(rec, name): a, s = rec["assessor"], rec["signature"] if not isinstance(a, dict) or not a.get("organization") or not a.get("key_id"): _fail(f"{name} does not name its assessor (organization and key_id)") - if not isinstance(s, dict) or s.get("algorithm") != ALGORITHM or not s.get("value"): - _fail(f"{name} carries no {ALGORITHM} signature") + if not isinstance(s, dict) or s.get("algorithm") not in (ALGORITHM, SET_ALGORITHM) or not s.get("value"): + _fail(f"{name} carries no {ALGORITHM} or {SET_ALGORITHM} signature") for k in ("record_id", "issued_at", "text"): if not isinstance(rec[k], str) or not rec[k].strip(): _fail(f"{name} has an empty {k}") @@ -75,6 +95,9 @@ def _load_identity(path): _fail(f"records are present but no assessor identity is pinned at {p}") try: ident = json.loads(p.read_text()) + if ident.get("algorithm") == KEYLESS: + _fail(f"the pinned identity {p} is keyless: its records arrive only as a signed set " + "(load_assessment), never as loose files") pem = ident["public_key_pem"].encode("ascii") except (json.JSONDecodeError, KeyError, AttributeError, UnicodeEncodeError) as exc: _fail(f"pinned identity {p} is unreadable ({type(exc).__name__})") @@ -86,6 +109,8 @@ def _load_identity(path): def _verify(rec, name, ident, pem): + if rec["signature"]["algorithm"] != ALGORITHM: + _fail(f"{name} is not signed with {ALGORITHM}") try: from cryptography.exceptions import InvalidSignature from cryptography.hazmat.primitives import hashes, serialization @@ -127,6 +152,109 @@ def load_records(records_dir=RECORDS_DIR, identity_path=IDENTITY_PATH): return records +# --- keyless set ------------------------------------------------------------------------ + +def load_keyless_identity(path=IDENTITY_PATH): + p = Path(path) + try: + ident = json.loads(p.read_text()) + except (OSError, json.JSONDecodeError) as exc: + _fail(f"no readable keyless assessor identity at {p} ({type(exc).__name__})") + if not isinstance(ident, dict) or ident.get("algorithm") != KEYLESS: + _fail(f"the identity pinned at {p} is not a {KEYLESS} identity") + for k in ("assessor", "key_id", "certificate_identity", "certificate_oidc_issuer"): + if not isinstance(ident.get(k), str) or not ident[k]: + _fail(f"the identity pinned at {p} does not name its {k}") + return ident + + +def cosign_verify(set_path, bundle_path, ident): + """True when cosign verifies the bundle over the set file against exactly the + pinned certificate identity and issuer (no regular expression).""" + r = subprocess.run(["cosign", "verify-blob", "--bundle", str(bundle_path), + "--certificate-identity", ident["certificate_identity"], + "--certificate-oidc-issuer", ident["certificate_oidc_issuer"], str(set_path)], + capture_output=True, text=True, check=False) # nosec B603: fixed argv + return r.returncode == 0 + + +def load_assessment(set_path, bundle_path, identity_path=IDENTITY_PATH, verifier=None, *, + expect_commit, expect_signal_id): + """Every record in a keyless-signed assessment set, verified. Fails closed when + the set or its bundle is missing: the deploy depends on the assessment.""" + return load_assessment_with_subject(set_path, bundle_path, identity_path, verifier, + expect_commit=expect_commit, expect_signal_id=expect_signal_id)[0] + + +def bind(doc, name, expect_commit, expect_signal_id): + """The set's subject, when it covers exactly the commit and published KSI + signal the caller states. A validly signed set for any other state fails: + an assessment is evidence only for what it assessed.""" + if not expect_commit or not expect_signal_id: + _fail("no commit or signal_id was stated for the assessment to cover; an unbound assessment is refused") + subj = doc.get("subject") + if not isinstance(subj, dict): + _fail(f"{name} names no subject (the commit and KSI signal it covered)") + if subj.get("commit") != expect_commit: + _fail(f"{name} covers commit {subj.get('commit')!r}, not the stated commit {expect_commit!r}") + if subj.get("signal_id") != expect_signal_id: + _fail(f"{name} covers KSI signal {subj.get('signal_id')!r}, not the stated signal {expect_signal_id!r}") + return copy.deepcopy(subj) + + +def load_assessment_with_subject(set_path, bundle_path, identity_path=IDENTITY_PATH, verifier=None, *, + expect_commit, expect_signal_id): + """(records, subject): load_assessment, plus the set's subject (the commit, + KSI signal and phase it covered), checked against the stated ones.""" + sp, bp = Path(set_path), Path(bundle_path) + for f, what in ((sp, "assessment set"), (bp, "assessment bundle")): + if not f.is_file() or f.stat().st_size == 0: + _fail(f"the {what} {f} is missing: the deploy depends on the assessor's signed record") + ident = load_keyless_identity(identity_path) + if not (verifier or cosign_verify)(sp, bp, ident): + _fail(f"{sp.name} signature does not verify against the pinned assessor identity") + try: + doc = json.loads(sp.read_text()) + except json.JSONDecodeError: + _fail(f"{sp.name} is not valid JSON") + if not isinstance(doc, dict) or doc.get("assessment_type") != SET_TYPE or doc.get("schema_version") != "1": + _fail(f"{sp.name} is not a {SET_TYPE} set, schema version 1") + subject = bind(doc, sp.name, expect_commit, expect_signal_id) + a = doc.get("assessor") or {} + if a.get("organization") != ident["assessor"] or a.get("key_id") != ident["key_id"]: + _fail(f"{sp.name} names {a.get('organization')!r}, not the pinned assessor identity") + recs = doc.get("records") + if not isinstance(recs, list) or not recs: + _fail(f"{sp.name} holds no records") + seen, out = set(), [] + for i, rec in enumerate(recs): + name = f"{sp.name} record {i}" + _shape(rec, name) + ra, sig = rec["assessor"], rec["signature"] + if ra["organization"] != ident["assessor"] or ra["key_id"] != ident["key_id"]: + _fail(f"{name} names {ra['organization']!r} / {ra['key_id']!r}, not the pinned assessor identity") + if sig["algorithm"] != SET_ALGORITHM or sig.get("signed_set") != sp.name: + _fail(f"{name} is not bound to the signed set {sp.name}") + if sig["value"] != hashlib.sha256(canonical(rec)).hexdigest(): + _fail(f"{name} ({rec['record_id']}) differs from the record the assessor signed") + if rec["record_id"] in seen: + _fail(f"record_id {rec['record_id']} appears twice") + seen.add(rec["record_id"]) + out.append(rec) + if not any(r["kind"] == "summary" and "rule_id" not in r for r in out): + _fail(f"{sp.name} has no overall summary (IVV-IAS-OSA)") + return out, subject + + +def overall_summary(records): + """The assessor's overall summary record (IVV-IAS-OSA), carried verbatim, or + None. The CPO quotes it (CPO-CSO-OSA).""" + sums = [r for r in records if r["kind"] == "summary" and "rule_id" not in r] + if len(sums) > 1: + _fail("more than one overall summary record") + return _carried(sums[0]) if sums else None + + def _carried(rec): return {k: copy.deepcopy(rec[k]) for k in CARRIED} @@ -155,6 +283,12 @@ def verify_output(sdr, records): signed record is carried. Fails the build otherwise.""" signed = {r["record_id"]: _carried(r) for r in records} carried = [] + pe = sdr.get("providerExtensions") + if isinstance(pe, dict): + # The SDR in FedRAMP's schema keeps them under providerExtensions. + for entries in (pe.get("assessorCommentResponses") or {}).values(): + carried += entries or [] + carried += (pe.get("assessorRecords") or {}).get("records", []) or [] for rr in sdr.get("rule_records", []): carried += rr.get("assessor_comment_responses", []) or [] carried += (sdr.get("assessor_records") or {}).get("records", []) or [] @@ -177,8 +311,18 @@ def main(argv=None): ap.add_argument("--records", default=str(RECORDS_DIR)) ap.add_argument("--identity", default=str(IDENTITY_PATH)) ap.add_argument("--sdr", default=None, help="a built security-decision-record.json to check") + ap.add_argument("--assessment", default=None, help="a keyless-signed assessment set") + ap.add_argument("--assessment-bundle", default=None) + # The state the set must cover: an assessment of any other commit or KSI + # signal is refused, however validly signed. + ap.add_argument("--assessment-commit", default=None) + ap.add_argument("--assessment-signal-id", default=None) a = ap.parse_args(argv) - records = load_records(a.records, a.identity) + if a.assessment: + records = load_assessment(a.assessment, a.assessment_bundle or a.assessment[:-5] + ".bundle", a.identity, + expect_commit=a.assessment_commit, expect_signal_id=a.assessment_signal_id) + else: + records = load_records(a.records, a.identity) if a.sdr: verify_output(json.loads(Path(a.sdr).read_text()), records) print(f"assessor records: {len(records)} verified" + ("; SDR carries them verbatim" if a.sdr else "")) diff --git a/scripts/_bizdays.py b/scripts/_bizdays.py new file mode 100644 index 00000000..bb529a65 --- /dev/null +++ b/scripts/_bizdays.py @@ -0,0 +1,79 @@ +"""Business-day arithmetic for FedRAMP timeframes ("bizdays" in the rules). + +A business day is a weekday that is not a US federal holiday (5 U.S.C. 6103). +Holidays are computed, not listed, so no year runs out: + + New Year's Day January 1 + Birthday of Martin Luther King, Jr. third Monday in January + Washington's Birthday third Monday in February + Memorial Day last Monday in May + Juneteenth June 19 + Independence Day July 4 + Labor Day first Monday in September + Columbus Day second Monday in October + Veterans Day November 11 + Thanksgiving Day fourth Thursday in November + Christmas Day December 25 + +A fixed-date holiday that falls on a Saturday is observed the Friday before, +one on a Sunday the Monday after (5 U.S.C. 6103(b), Executive Order 11582). +New Year's Day on a Saturday is therefore observed on December 31 of the +year before. + +Stdlib only. +""" + +from datetime import date, timedelta +from functools import lru_cache + +_FIXED = ((1, 1), (6, 19), (7, 4), (11, 11), (12, 25)) + + +def _nth_weekday(year, month, weekday, n): + """The nth `weekday` (Mon=0) of the month; n=-1 is the last.""" + if n > 0: + first = date(year, month, 1) + return first + timedelta(days=(weekday - first.weekday()) % 7 + 7 * (n - 1)) + nxt = date(year + (month == 12), month % 12 + 1, 1) + last = nxt - timedelta(days=1) + return last - timedelta(days=(last.weekday() - weekday) % 7) + + +def _observed(d): + if d.weekday() == 5: + return d - timedelta(days=1) + if d.weekday() == 6: + return d + timedelta(days=1) + return d + + +@lru_cache(maxsize=64) +def federal_holidays(year): + """The observed US federal holidays that fall in `year`.""" + days = set() + for y in (year, year + 1): # next year's New Year's Day may be observed on Dec 31 + days |= {_observed(date(y, m, d)) for m, d in _FIXED} + days |= { + _nth_weekday(y, 1, 0, 3), # MLK + _nth_weekday(y, 2, 0, 3), # Washington's Birthday + _nth_weekday(y, 5, 0, -1), # Memorial Day + _nth_weekday(y, 9, 0, 1), # Labor Day + _nth_weekday(y, 10, 0, 2), # Columbus Day + _nth_weekday(y, 11, 3, 4), # Thanksgiving + } + return frozenset(d for d in days if d.year == year) + + +def is_business_day(d): + return d.weekday() < 5 and d not in federal_holidays(d.year) + + +def add_business_days(d, n): + """The date n business days after d (n < 0: before). n == 0 returns d.""" + step = 1 if n >= 0 else -1 + left = abs(n) + while left: + d += timedelta(days=step) + if is_business_day(d): + left -= 1 + return d diff --git a/scripts/_ccm.py b/scripts/_ccm.py new file mode 100644 index 00000000..92051033 --- /dev/null +++ b/scripts/_ccm.py @@ -0,0 +1,246 @@ +"""The quarterly Collaborative Continuous Monitoring calendar (CCM-OCR-SOR, CCM-QTR-SAR). + +infrastructure/schemas/ccm-calendar.json fixes the Ongoing Certification Report +issue dates and how many business days after each issue the Quarterly Review +falls. Everything that publishes a next-report or next-review date (the OCR, the +CPO, the review calendar file) reads it here, so the dates are the same +everywhere and stay put between issues (CCM-OCR-NRD, CCM-QTR-NRD). + +Fails closed, stdlib only. The calendar must: +- list issue dates in order, each a business day, 84 to 98 days after the one + before (a regular 3-month cycle); +- place every issue date away from the beginning, middle and end of its quarter + (more than 14 days from either end, more than 7 from the middle); +- put each review 3 to 10 business days after its issue; +- cover every date it computes with its holiday list; +- keep at least two issue dates ahead of `today`, so it cannot quietly run out. +""" + +import json +import re +import sys +from datetime import date, datetime, timedelta, timezone +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _engagement # noqa: E402 + +REPO = Path(__file__).resolve().parent.parent +CALENDAR_PATH = REPO / "infrastructure" / "schemas" / "ccm-calendar.json" +SITE = "https://samaydlette.com" +REPO_URL = "https://github.com/sam-aydlette/samaydlette.com" +ICS_URL = f"{SITE}/.well-known/quarterly-review.ics" +ISSUES_INDEX_URL = f"{SITE}/.well-known/ocr-issues.json" +REVIEWS_INDEX_URL = f"{SITE}/.well-known/quarterly-reviews.json" +MIN_GAP_DAYS, MAX_GAP_DAYS = 84, 98 +EDGE_DAYS, MID_DAYS = 14, 7 +MIN_FUTURE_ISSUES = 2 +_HHMM = re.compile(r"^([01]\d|2[0-3]):[0-5]\d$") + + +def _fail(msg): + raise SystemExit(f"::error::CCM calendar: {msg} (fail-closed)") + + +def _date(v, what): + try: + return date.fromisoformat(v) + except (TypeError, ValueError): + _fail(f"{what} {v!r} is not a YYYY-MM-DD date") + + +def quarter_bounds(d): + q0 = (d.month - 1) // 3 * 3 + 1 + start = date(d.year, q0, 1) + end = date(d.year + (q0 + 3 > 12), (q0 + 2) % 12 + 1, 1) - timedelta(days=1) + return start, end + + +class Calendar: + def __init__(self, doc): + self.doc = doc + self.issues = [_date(d, "issue date") for d in doc["ocr_issue_dates"]] + self.holidays = {_date(d, "holiday") for d in doc["holidays"]["dates"]} + self.covers_through = _date(doc["holidays"]["covers_through"], "holidays.covers_through") + self.offset = doc["review_business_days_after_issue"] + self.start_utc = doc["review_start_utc"] + self.duration = doc["review_duration_minutes"] + + def is_business_day(self, d): + if d > self.covers_through: + _fail(f"{d} is past the holiday list (covers through {self.covers_through})") + return d.weekday() < 5 and d not in self.holidays + + def add_business_days(self, d, n): + while n > 0: + d += timedelta(days=1) + if self.is_business_day(d): + n -= 1 + return d + + def review_date(self, issue): + return self.add_business_days(issue, self.offset) + + def issued(self, today): + """Issue dates on or before `today`.""" + return [d for d in self.issues if d <= today] + + def next_issue(self, today): + """The next issue date strictly after `today`: stable from one issue to the next.""" + return next(d for d in self.issues if d > today) + + def next_review(self, today): + """The next review on or after `today` (the one following the latest + issue, until it has happened).""" + return next(r for r in (self.review_date(d) for d in self.issues) if r >= today) + + def period(self, issue): + """(from, to) an issue covers: the previous issue to this one. The first + issue covers the 3 months before it.""" + i = self.issues.index(issue) + start = self.issues[i - 1] if i else issue - timedelta(days=91) + return start, issue + + def current_period(self, today): + """(from, to) of the report as it stands today: since the latest issue.""" + done = self.issued(today) + return (done[-1] if done else self.issues[0] - timedelta(days=91)), today + + def review_start(self, issue): + h, m = (int(x) for x in self.start_utc.split(":")) + r = self.review_date(issue) + return datetime(r.year, r.month, r.day, h, m, tzinfo=timezone.utc) + + +def validate(doc, today): + if not isinstance(doc, dict) or doc.get("schema") != "ccm-calendar/1": + _fail("not a ccm-calendar/1 document") + for k in ("decided_by", "decided_on", "review_by", "rationale"): + if not isinstance(doc.get(k), str) or not doc[k].strip(): + _fail(f"{k} is missing") + if _date(doc["review_by"], "review_by") < today: + _fail(f"review_by {doc['review_by']} has passed: the calendar needs a fresh decision") + off = doc.get("review_business_days_after_issue") + if not isinstance(off, int) or isinstance(off, bool) or not 3 <= off <= 10: + _fail("review_business_days_after_issue must be 3 to 10 (CCM-QTR-SAR)") + if not _HHMM.match(str(doc.get("review_start_utc", ""))): + _fail("review_start_utc must be HH:MM") + dur = doc.get("review_duration_minutes") + if not isinstance(dur, int) or isinstance(dur, bool) or not 15 <= dur <= 240: + _fail("review_duration_minutes must be 15 to 240") + if not isinstance(doc.get("ocr_issue_dates"), list) or len(doc["ocr_issue_dates"]) < 2: + _fail("ocr_issue_dates must list at least two dates") + if not isinstance(doc.get("holidays"), dict) or not isinstance(doc["holidays"].get("dates"), list): + _fail("holidays.dates must be a list") + cal = Calendar(doc) + prev = None + for d in cal.issues: + if prev is not None and not MIN_GAP_DAYS <= (d - prev).days <= MAX_GAP_DAYS: + _fail(f"{d} is {(d - prev).days} days after {prev}: not a regular 3-month cycle") + if not cal.is_business_day(d): + _fail(f"issue date {d} is not a business day") + qs, qe = quarter_bounds(d) + mid = qs + (qe - qs) / 2 + if (d - qs).days < EDGE_DAYS or (qe - d).days < EDGE_DAYS or abs((d - mid).days) <= MID_DAYS: + _fail(f"issue date {d} is at the beginning, middle or end of its quarter (CCM-OCR-SOR)") + cal.review_date(d) # inside the holiday coverage + prev = d + if sum(1 for d in cal.issues if d > today) < MIN_FUTURE_ISSUES: + _fail(f"fewer than {MIN_FUTURE_ISSUES} issue dates after {today}: extend the calendar") + return cal + + +def load(path=CALENDAR_PATH, today=None): + today = today or datetime.now(timezone.utc).date() + try: + doc = json.loads(Path(path).read_text()) + except (OSError, ValueError) as exc: + _fail(f"cannot read {path}: {exc}") + return validate(doc, today) + + +def review_url(issue): + """Where the review of one OCR issue is published once held: it carries the + feedback received through the intake (CCM-OCR-FBM) and its answers.""" + return f"{SITE}/.well-known/quarterly-review-{issue.isoformat()}.json" + + +# --- the review calendar file (CCM-QTR-REG) ----------------------------------------- + +def _ics_escape(s): + return s.replace("\\", "\\\\").replace(";", "\\;").replace(",", "\\,").replace("\n", "\\n") + + +def _fold(line): + """RFC 5545 3.1: lines longer than 75 octets continue with a leading space.""" + raw = line.encode("utf-8") + if len(raw) <= 75: + return line + out, cur = [], b"" + for ch in line: + b = ch.encode("utf-8") + if len(cur) + len(b) > (75 if not out else 74): + out.append(cur.decode("utf-8")) + cur = b"" + cur += b + out.append(cur.decode("utf-8")) + return "\r\n ".join(out) + + +def ics(cal, today): + """One VEVENT per Quarterly Review from the latest issued report on. + Deterministic: DTSTAMP is the calendar's decision date.""" + stamp = cal.doc["decided_on"].replace("-", "") + "T000000Z" + done = cal.issued(today) + first = done[-1] if done else cal.issues[0] + lines = ["BEGIN:VCALENDAR", "VERSION:2.0", "PRODID:-//samaydlette.com//CCM quarterly review//EN", + "CALSCALE:GREGORIAN", "METHOD:PUBLISH", "X-WR-CALNAME:samaydlette.com Quarterly Review"] + for issue in cal.issues: + if issue < first: + continue + start = cal.review_start(issue) + end = start + timedelta(minutes=cal.duration) + desc = (f"Quarterly Review (CCM-QTR-MTG) of the Ongoing Certification Report issued {issue}, held " + f"with simulated attendees by the package maintenance workflow; nobody needs to attend. " + f"Report: {SITE}/.well-known/ocr-issue-{issue}.json (published on the issue date). " + f"Review and transcript: {review_url(issue)} (published on the review date). " + f"{_engagement.SHORT}") + lines += ["BEGIN:VEVENT", f"UID:qtr-review-{issue}@samaydlette.com", f"DTSTAMP:{stamp}", + f"DTSTART:{start.strftime('%Y%m%dT%H%M%SZ')}", f"DTEND:{end.strftime('%Y%m%dT%H%M%SZ')}", + f"SUMMARY:{_ics_escape(f'samaydlette.com Quarterly Review (OCR {issue}, simulated)')}", + f"DESCRIPTION:{_ics_escape(desc)}", f"URL:{review_url(issue)}", + "LOCATION:Simulated (package-maintenance.yml)", "END:VEVENT"] + lines.append("END:VCALENDAR") + return "\r\n".join(_fold(x) for x in lines) + "\r\n" + + +def dates_summary(cal, today): + """What the CPO and the OCR publish about the cycle.""" + nxt = cal.next_issue(today) + return {"nextOngoingCertificationReportDate": nxt.isoformat(), + "nextQuarterlyReviewDate": cal.next_review(today).isoformat(), + "quarterlyReviewCalendar": ICS_URL, + "quarterlyReviews": REVIEWS_INDEX_URL, + "ongoingCertificationReportIssues": ISSUES_INDEX_URL, + "issueDates": [d.isoformat() for d in cal.issues], + "reviewBusinessDaysAfterIssue": cal.offset} + + +def main(argv=None): + import argparse + ap = argparse.ArgumentParser(description="Validate the CCM calendar and write the review .ics.") + ap.add_argument("--calendar", default=str(CALENDAR_PATH)) + ap.add_argument("--ics", default=None, help="write the Quarterly Review calendar file here") + a = ap.parse_args(argv) + today = datetime.now(timezone.utc).date() + cal = load(a.calendar, today) + if a.ics: + Path(a.ics).write_text(ics(cal, today), newline="") + s = dates_summary(cal, today) + print(f"CCM calendar: next report {s['nextOngoingCertificationReportDate']}, " + f"next review {s['nextQuarterlyReviewDate']}") + return 0 + + +if __name__ == "__main__": + raise SystemExit(main()) diff --git a/scripts/_codeql.py b/scripts/_codeql.py new file mode 100644 index 00000000..ebbdea74 --- /dev/null +++ b/scripts/_codeql.py @@ -0,0 +1,91 @@ +"""CodeQL code-scanning alerts as VDR findings (SAST of first-party code). + +.github/workflows/codeql.yml analyses this repository's Python, JavaScript and +GitHub Actions code, and the Silk Reeling app's Python and JavaScript, and +uploads the results to GitHub code scanning. scripts/fetch-detection-feeds.sh +reads the open CodeQL alerts on main and the latest analysis per category into +one document: + + {"analyses": [{"category", "created_at", "error", ...}], + "alerts": [{"number", "state", "created_at", "rule": {...}, + "most_recent_instance": {"location": {"path", ...}, ...}}]} + +The detection gate (scripts/detection-gate.py, detection.codeql) decides whether +the analyses are complete and fresh before anything is built. This module turns +the alerts into findings for scripts/build-vdr-report.py. A CodeQL alert is a +weakness in code this system ships, so it is a vulnerability decided through the +decision register (applies_to.vuln_ids names its tracking_id), like a ZAP alert. + +Identity: an alert's number is GitHub's own stable identity for it (it follows +the code across commits and line moves), so the tracking id is +codeql-<rule id>-<alert number>: stable, unique and readable. +""" + +import json +from pathlib import Path + +SOURCE = "codeql" + +# CodeQL's security severity first (the CVSS-derived level GitHub shows), then +# the rule's own problem severity for a query that has none. +SECURITY_SEVERITY = {"critical": "CRITICAL", "high": "HIGH", "medium": "MEDIUM", "low": "LOW"} +PROBLEM_SEVERITY = {"error": "HIGH", "warning": "MEDIUM", "note": "LOW", "recommendation": "LOW"} + + +def _fail(msg): + raise SystemExit(f"::error::CodeQL alerts: {msg} (fail-closed)") + + +def load(path): + """The fetched document. Given but missing or malformed: the build stops, + because zero alerts and no scan must never read the same.""" + p = Path(path) + if not p.is_file(): + _fail(f"{path} not found; the detection gate should have stopped this run") + try: + doc = json.loads(p.read_text(encoding="utf-8")) + except (OSError, UnicodeDecodeError, json.JSONDecodeError) as exc: + _fail(f"{path} is not valid JSON ({type(exc).__name__})") + if not isinstance(doc, dict) or not isinstance(doc.get("alerts"), list) \ + or not isinstance(doc.get("analyses"), list): + _fail(f"{path} has no alerts[] and analyses[]") + return doc + + +def severity(rule): + rule = rule or {} + level = str(rule.get("security_severity_level") or "").lower() + if level in SECURITY_SEVERITY: + return SECURITY_SEVERITY[level] + return PROBLEM_SEVERITY.get(str(rule.get("severity") or "").lower(), "MEDIUM") + + +def finding(alert): + """One open alert as a VDR finding, or None for an alert that is not open.""" + if not isinstance(alert, dict) or alert.get("state", "open") != "open": + return None + rule = alert.get("rule") or {} + inst = alert.get("most_recent_instance") or {} + loc = inst.get("location") or {} + rule_id = str(rule.get("id") or "codeql") + number = alert.get("number") + if not isinstance(number, int) or isinstance(number, bool): + _fail(f"alert for {rule_id} has no number, so it has no stable identity") + message = str((inst.get("message") or {}).get("text") or "").strip() + return { + "source": SOURCE, + "tool_id": rule_id, + "tracking_id": f"codeql-{rule_id}-{number}", + "title": str(rule.get("description") or rule.get("name") or rule_id), + "description": message[:500], + "severity": severity(rule), + "resource": str(loc.get("path") or ""), + "detected_at": alert.get("created_at"), + } + + +def ingest_codeql(path): + """Findings from the fetched alerts; [] when no path is given.""" + if not path: + return [] + return [f for f in (finding(a) for a in load(path)["alerts"]) if f] diff --git a/scripts/_common.py b/scripts/_common.py index 3ad1b4ee..d572f864 100644 --- a/scripts/_common.py +++ b/scripts/_common.py @@ -15,14 +15,13 @@ # sys.path.insert(0, os.path.dirname(os.path.abspath(__file__))) # from _common import classify, sha256_file # -# The insert is __file__-relative, so it resolves from any cwd. Scripts under -# scripts/staged/ insert the parent directory instead. +# The insert is __file__-relative, so it resolves from any cwd. # # WHAT BELONGS HERE: only definitions that were already duplicated VERBATIM, and # only where divergence between the copies would be a bug rather than a choice. -# The four copies of classify() were the case that mattered — it is a compliance -# semantic that the CMMC projection, the coverage figures and the framework -# spokes must all agree on, and nothing was keeping them in step. +# The copies of classify() were the case that mattered — it is a compliance +# semantic the published coverage figures and the per-control views must agree +# on, and nothing was keeping them in step. # # WHAT DOES NOT BELONG HERE: same-named functions that do different things. # render_markdown() exists several times and renders a different artifact each @@ -82,9 +81,9 @@ def classify(status, origination): """Project a control implemented-requirement onto the shared-responsibility vocabulary every downstream framework view uses. - This is the compliance semantic the downstream framework views have to agree - on — the CMMC SRM projection, the published coverage figures, and the - framework spokes. It lived as four verbatim copies, so a + This is the compliance semantic the downstream views have to agree on — + the trust center's Rev5 Moderate figures among them. It lived as four + verbatim copies, so a change to one would have silently split them apart while every gate stayed green: none of the invariants in reconcile.py compare these projections to each other. diff --git a/scripts/_controls.py b/scripts/_controls.py index 9ee988a7..86791e15 100644 --- a/scripts/_controls.py +++ b/scripts/_controls.py @@ -1,9 +1,8 @@ """The control projection: one implemented-requirement per NIST 800-53 Rev5 control, with its implementation status, origination and statement. -This is the control hub that every framework view projects from: the SDR's -per-control status, the published coverage figures, the CMMC projection and the -trust center's framework figures. It used to live inside the OSCAL SSP builder +This is the control hub the SDR's per-control status and the trust center's +Rev5 Moderate figures project from. It used to live inside the OSCAL SSP builder (scripts/build-oscal-ssp.py), and consumers read it back out of the generated oscal-ssp.json. The SSP was retired under CR26 (the SDR and CPO replace it), so the projection now lives here and consumers compute it in memory from the same @@ -103,7 +102,7 @@ "KSI-MLA-EVC": "docs/architecture-decisions.md", "KSI-MLA-LET": "docs/architecture-decisions.md", "KSI-MLA-OSM": "infrastructure/policies.rego", - "KSI-MLA-RVL": "docs/ksi-signal.md", + "KSI-MLA-RVL": "docs/architecture-decisions.md", "KSI-PIY-GIV": "docs/ksi-signal.md", "KSI-PIY-RES": "docs/security-review.md", "KSI-PIY-RIS": "docs/security-review.md", @@ -406,8 +405,10 @@ def _app_auth_overrides(signal): "IR support staff, IR-3 IR testing exercises with multiple " "participants) collapse into self-attestation by the operator " "for a sole-operator system; the procedures and capabilities " - "are in place. Tabletops are run annually per " - "docs/security-review.md." + "are in place. Incident exercises are recorded in " + "data/incidents.json and the recovery tabletop is held by " + "scripts/hold-recovery-exercise.py each November with " + "simulated responders (DEC-194, DEC-195)." ), }, # System and Communications Protection — explicit overrides handle @@ -448,18 +449,20 @@ def _app_auth_overrides(signal): ), }, - # Awareness and Training — implemented; sole-operator self-attestation. + # Awareness and Training — implemented; generated training, simulated trainee. "at-": { "status": "implemented", "origination": "sp-corporate", "statement": ( - "Training is self-attested in docs/training-log.md. The " - "system has one employee (the operator), who holds every " - "role; coverage of role-specific topics (privileged-access, " - "development, IR/DR) collapses into ongoing professional " - "reading and the artifacts produced. Effectiveness review is " - "annual, recorded in docs/security-review.md. The training " - "regimen is in place; external evidence (training certs, " + "Training is generated and taken by machine " + "(scripts/_training.py): the packet is built from the " + "system's own data (decisions, incidents, rules, and a core " + "covering privileged access, development and IR/DR; " + "docs/training-log.md lists the areas), and a simulated " + "trainee takes its quiz whenever it changes (DEC-194). The " + "Security Decision Record counts the packet's currency and " + "the trainee's completion and score trend as two automated " + "methods for KSI-CED-RAT. External evidence (training certs, " "attendance logs) is not produced because there is no " "workforce to maintain rosters for." ), @@ -473,8 +476,11 @@ def _app_auth_overrides(signal): "with declared RTO of 21 days and RPO of 24 hours. Backups " "are S3 object versioning + git history (RPO satisfied with " "orders of magnitude headroom). Recovery testing was " - "exercised end-to-end during initial implementation; annual " - "tabletops are scheduled. Enhancements that presume alternate " + "exercised end-to-end during initial implementation and is " + "exercised by scripts/hold-recovery-exercise.py every month " + "(the live site rebuilt from the deployed commit and compared, " + "versioning and point-in-time recovery re-read) with a " + "simulated tabletop each November. Enhancements that presume alternate " "processing sites or geographically distributed operations " "centers are tracked as separate not-applicable entries; the " "single-region static-site deployment does not exercise them." @@ -539,10 +545,13 @@ def _app_auth_overrides(signal): "statement": ( "Planning is documented across the docs/ tree: " "docs/architecture-decisions.md (system architecture and " - "design choices), docs/security-review.md (annual planning " - "cycle), docs/recovery-plan.md (contingency planning), " - "docs/incident-response.md (response planning). Plans are " - "version-controlled and reviewed annually." + "design choices), docs/security-review.md (the generated " + "Annual Security Review), docs/recovery-plan.md (contingency " + "planning), docs/incident-response.md (response planning). " + "Plans are version-controlled, machine-checked on every " + "deploy and night (scripts/check-non-machine-vv.py) and " + "re-checked with their sha256 in each Annual Security Review " + "(scripts/hold-security-review.py)." ), }, # Program Management — sole-operator self-attestation; multi-person @@ -553,7 +562,9 @@ def _app_auth_overrides(signal): "statement": ( "Program management functions (governance, policy, investment " "review) collapse into self-attestation for a sole-operator " - "system; reviews are recorded in docs/security-review.md. " + "system; the investment review is the generated Annual " + "Security Review (scripts/hold-security-review.py, " + "docs/security-review.md). " "Enhancements that presume a CISO, a board, or an enterprise-" "architecture function are tracked as separate not-applicable " "entries." @@ -568,7 +579,9 @@ def _app_auth_overrides(signal): "time, automated SCA via Dependabot, and IaC scanning via " "Checkov + tfsec in CI. Findings are surfaced through " "GitHub Security and reviewed against severity gates. " - "Annual review is recorded in docs/security-review.md." + "The Annual Security Review (scripts/hold-security-review.py, " + "docs/security-review.md) re-checks the threat model against " + "new component types." ), }, # System and Services Acquisition — shared between AWS (managed services) @@ -618,8 +631,10 @@ def _app_auth_overrides(signal): "responsibilities (where applicable, citing AWS authorization " "package AGENCYAMAZONEW), the FedRAMP 20x rule integration relevant " "to the family (e.g., SCN/VDR/MAS/SCG/CCM/ICP/UCM as applicable), " - "and the review cadence. Reviews and updates occur on the cadences " - "defined in docs/security-review.md and the per-policy doc." + "and how it is verified: machine checks on every deploy and night " + "(scripts/check-non-machine-vv.py) and the generated Annual Security " + "Review (scripts/hold-security-review.py); updates are reviewed pull " + "requests." ), } diff --git a/scripts/_decisions.py b/scripts/_decisions.py index de3046a6..79802c72 100644 --- a/scripts/_decisions.py +++ b/scripts/_decisions.py @@ -11,6 +11,16 @@ read it through this module, so they cannot disagree about what a decision covers. Records carried over from the POA&M keep their old ID in `former_id`. +One marking format for who wrote a record and when the operator confirmed it: +`source.drafted_by` names a drafter other than the operator (e.g. AI-drafted), +and `confirmed_on` is the date the operator confirmed the decision. A record +without `confirmed_on` cannot be in force, and no title or justification may +carry its own drafting or confirmation note ("AI-drafted", "not yet +confirmed", "for the operator to confirm"): that lives in the two fields only. +A decision replaced by something else (automation, a newer record) is closed +as `superseded`, with `closed_on` and `replaced_by` saying what replaces it; +only a `remediated` record counts as a remediated finding. + Fails closed: a missing or invalid register stops the build. A register that silently read as empty would turn every handled finding into an open one, or worse, a check that resolves to no decision into a passing one. @@ -28,19 +38,26 @@ ID_RE = re.compile(r"^DEC-\d{3}$") FORMER_RE = re.compile(r"^POAM-\d{3}$") DATE_RE = re.compile(r"^\d{4}-\d{2}-\d{2}$") +PAIN_RE = re.compile(r"^N[0-5]$") +PLAN_KEYS = {"date", "target_pain"} # Dispositions of an in-force record. Config-scanner suppressions use # risk-accepted / false-positive; vulnerabilities use the triage vocabulary. IN_FORCE = ("false-positive", "risk-accepted", "accepted", "operational-requirement", "mitigated", "vendor-dependency", "under-investigation", "remediate") -CLOSED = ("remediated",) +CLOSED = ("remediated", "superseded") DECISION_FIELDS = ("decided_by", "decided_on", "review_by") +# Drafting and confirmation are fields (source.drafted_by, confirmed_on), never +# prose: a note in the text is how five marking formats crept in. +MARKING_RE = re.compile(r"(?i)\bAI[- ]drafted\b|not yet confirmed|for (the operator|sam aydlette)'?s? (to confirm|confirmation)" + r"|confirm at review|\bproposed;") # The fields infrastructure/schemas/decisions.schema.json allows. An unknown # field is refused: a misspelt review_by would otherwise read as absent. TOP_KEYS = {"$comment", "_note", "schema", "decisions"} RECORD_KEYS = {"id", "former_id", "title", "status", "disposition", "justification", *DECISION_FIELDS, - "closed_on", "original_detection_date", "planned_completion", "remediation_plan", - "vendor_dependency", "point_of_contact", "controls", "applies_to", "vuln_fields", "source"} + "closed_on", "original_detection_date", "planned_completion", "planned_reduction", "automatable", "remediation_plan", + "vendor_dependency", "point_of_contact", "controls", "applies_to", "vuln_fields", "source", + "confirmed_on", "replaced_by"} APPLIES_KEYS = {"check_ids", "vuln_ids", "resources"} @@ -75,6 +92,12 @@ def validate(doc, where="data/decisions.json"): for k in ("title", "justification"): if not isinstance(r.get(k), str) or not r[k].strip(): _fail(f"{rid}: {k} must be a non-empty string") + if MARKING_RE.search(r[k]): + _fail(f"{rid}: {k} carries a drafting or confirmation note; use source.drafted_by and confirmed_on") + src = r.get("source") + if src is not None and (not isinstance(src, dict) or ("drafted_by" in src and not ( + isinstance(src["drafted_by"], str) and src["drafted_by"].strip()))): + _fail(f"{rid}: source must be an object, and source.drafted_by a non-empty string") status, disp = r.get("status"), r.get("disposition") if status == "in-force": if disp not in IN_FORCE: @@ -85,14 +108,44 @@ def validate(doc, where="data/decisions.json"): for k in ("decided_on", "review_by"): if not DATE_RE.match(r[k]): _fail(f"{rid}: {k} must be an ISO date") + # The operator's confirmation: an unconfirmed draft confers nothing. + conf = r.get("confirmed_on") + if not (isinstance(conf, str) and DATE_RE.match(conf)): + _fail(f"{rid}: an in-force decision needs confirmed_on (the date the operator confirmed it); " + "an unconfirmed draft cannot be in force") + if conf < r["decided_on"]: + _fail(f"{rid}: confirmed_on {conf} is before decided_on {r['decided_on']}") + if r.get("replaced_by") is not None: + _fail(f"{rid}: replaced_by is for superseded records only") elif status == "closed": if disp not in CLOSED: _fail(f"{rid}: a closed record's disposition must be one of {list(CLOSED)}") - for k in ("closed_on", "decided_on", "review_by"): + for k in ("closed_on", "decided_on", "review_by", "confirmed_on"): if k in r and not (isinstance(r[k], str) and DATE_RE.match(r[k])): _fail(f"{rid}: {k} must be an ISO date") + if disp == "superseded": + if "closed_on" not in r or not (isinstance(r.get("replaced_by"), str) and r["replaced_by"].strip()): + _fail(f"{rid}: a superseded record needs closed_on and replaced_by (what replaces it)") + elif r.get("replaced_by") is not None: + _fail(f"{rid}: replaced_by is for superseded records only") else: _fail(f"{rid}: status must be in-force or closed") + plan = r.get("planned_reduction") + if plan is not None: + # The next planned PAIN reduction (VER-RPT-VDT): when, and to what + # rating. A malformed plan would publish a projection nobody made. + if (not isinstance(plan, dict) or set(plan) != PLAN_KEYS + or not DATE_RE.match(str(plan.get("date"))) or not PAIN_RE.match(str(plan.get("target_pain")))): + _fail(f"{rid}: planned_reduction must be {{date: YYYY-MM-DD, target_pain: N0-N5}}") + if status != "in-force": + _fail(f"{rid}: only an in-force record plans a reduction") + auto = r.get("automatable") + if auto is not None: + # VER-EVA-AIA: exploitation is assumed automatable unless there is + # evidence it is not. "no" without the evidence would be an assumption. + if (not isinstance(auto, dict) or set(auto) - {"value", "evidence"} or auto.get("value") not in ("yes", "no") + or (auto["value"] == "no" and not str(auto.get("evidence") or "").strip())): + _fail(f"{rid}: automatable must be {{value: yes|no, evidence}}, and 'no' needs its evidence") applies = r.get("applies_to") if not isinstance(applies, dict) or set(applies) - APPLIES_KEYS: _fail(f"{rid}: applies_to must be an object with only {sorted(APPLIES_KEYS)}") @@ -130,6 +183,12 @@ def in_force(reg): return [r for r in reg["decisions"] if r["status"] == "in-force"] +def remediated(reg): + """Closed records that settled a finding. A superseded record replaced a + decision; it remediated nothing.""" + return [r for r in reg["decisions"] if r["status"] == "closed" and r["disposition"] == "remediated"] + + def by_any_id(reg): """{DEC id or former POAM id: record}, for resolving a reference in text.""" out = {} diff --git a/scripts/_engagement.py b/scripts/_engagement.py new file mode 100644 index 00000000..83ab1c57 --- /dev/null +++ b/scripts/_engagement.py @@ -0,0 +1,93 @@ +"""No engagement (DEC-194): the one statement, and the screen that keeps text honest to it. + +The operator does not engage FedRAMP or any federal agency about this system: +no submission, notice, invitation, access grant, meeting or commitment. Every +counterparty a FedRAMP process names is simulated. The trust page, the CPO +(providerExtensions.engagement), the OCR, the Quarterly Review output and every +simulated output's header carry STATEMENT, verbatim, so nobody has to infer it. + +`invitations(text)` is the phrase screen: wording that offers to invite, +notify, register, serve or answer a real agency or FedRAMP. A mention that +names the party as simulated ("FedRAMP (simulated)", "the simulated FedRAMP") +is not an offer, and is allowed. tests/test_engagement.py runs it over the +records, the decisions, the procedures, the trust page and the generated +outputs. +""" + +import re + +DECISION = "DEC-194" +STATEMENT = ("No engagement (DEC-194): this is a proof of concept. The operator does not engage FedRAMP or any " + "federal agency about this system, and makes them no submission, notice, invitation, access grant " + "or commitment. Every FedRAMP, agency, assessor and attendee you see here is simulated, and nothing " + "is sent to anyone. Anyone who really, really wants something can say hello on LinkedIn " + "(https://www.linkedin.com/in/sa2/); the operator may consider it, with no obligation and no deadline.") +SHORT = "Simulated (DEC-194): no real FedRAMP, agency or person took part, and nothing was sent to anyone." + +# A party named as simulated is not a real party. +_REAL_PARTY = (r"(?<!simulated )(?<!fictional )(?:FedRAMP|(?:an |any |federal |the )?agenc(?:y|ies))" + r"(?! \(simulated\))(?![- ](?:access|exercise|customer data|information|user))") +_PATTERNS = [ + # inviting or registering a real party + rf"\binvit\w*\s+(?:{_REAL_PARTY})", + rf"(?:{_REAL_PARTY})\s+(?:can|may|should)\s+(?:file|register|request|ask|use the|attend|submit|sign up)", + rf"(?:{_REAL_PARTY})\s+that wants", + # notifying or serving a real party + rf"\bnotif(?:y|ies|ied)\s+(?:{_REAL_PARTY})", + rf"\b(?:supplies|supply|provides|provide|sends?)\s+(?:it |them |the \w+ )?to\s+(?:{_REAL_PARTY})\s+on request", + r"\b(?:registration|access|feedback)\s+form\b", + r"\bregister(?:ed)? (?:parties|for (?:a|the) (?:Quarterly )?Review)", + r"\bjoin link\b", + # promising a real party an answer + r"\b(?:on|upon) request\b", + r"\bthe answer comes within\b", + r"\bparties who registered\b", + r"\bissues/new\?template=", +] +_SCREEN = re.compile("|".join(f"(?:{p})" for p in _PATTERNS), re.IGNORECASE) + + +def invitations(text): + """Every phrase in `text` that offers engagement with a real agency or FedRAMP.""" + return [m.group(0) for m in _SCREEN.finditer(text or "")] + + +def strings(value): + """Every string inside a JSON value.""" + if isinstance(value, str): + yield value + elif isinstance(value, dict): + for v in value.values(): + yield from strings(v) + elif isinstance(value, list): + for v in value: + yield from strings(v) + + +def require_none(value, what): + """Fail closed when any string in `value` offers engagement.""" + hits = sorted({h for s in strings(value) for h in invitations(s)}) + if hits: + raise SystemExit(f"::error::{what} offers engagement with a real agency or FedRAMP ({DECISION}): " + f"{'; '.join(hits)[:300]} (fail-closed)") + return value + + +def names_simulated(value): + """Whether a JSON output names a simulated counterparty: a `simulated` or + `simulation` field that is set, or a party labelled "(simulated)".""" + if isinstance(value, dict): + for k, v in value.items(): + if k in ("simulated", "simulation") and v: + return True + if names_simulated(v): + return True + return False + if isinstance(value, list): + return any(names_simulated(v) for v in value) + return isinstance(value, str) and "(simulated)" in value + + +def carries_statement(value): + """Whether the full DEC-194 statement appears anywhere in a JSON output.""" + return any(s == STATEMENT for s in strings(value)) diff --git a/scripts/_evaluation.py b/scripts/_evaluation.py new file mode 100644 index 00000000..0eac5691 --- /dev/null +++ b/scripts/_evaluation.py @@ -0,0 +1,360 @@ +"""The evaluation record for each finding (VER-EVA-*), beside the triage decision. + +policies/triage.rego decides the ratings, the deadline and blocking. This module +states what the evaluation considered, as facts with their basis, so a reader +can see each factor VER-EVA-EFA names and the assumptions VER-EVA-AIA and +VDR-CSO-RES require: + + criticality the component's classification (what PAIN is computed from) + reachability the policy's IRV and its basis + exploitability the policy's LEV and its basis + detectability how an attacker would learn of it + prevalence how many findings and components share its group + privilege what exploitation needs and what it reaches + proximate other findings and mitigations on the same component + known_threats KEV and the exploit-prediction score + automatable yes unless evidence says otherwise (VER-EVA-AIA) + exploitation whether exploitation of it has been observed (VDR-CSO-RES) + +It also groups findings (VER-EVA-GRV) and decides what the public artifacts may +say about each one (VER-RPT-NID, VER-RPT-RPD). Factors are recorded, not fed +into the impact tables: REQ-PAI-4 makes the tables global, and a provider that +changes them publishes the deviation. Grouping is fed to the policy, which +evaluates a group at its most exposed member. +""" + +import hashlib +import json +from pathlib import Path + +REPO = Path(__file__).resolve().parent.parent +INCIDENTS = REPO / "data" / "incidents.json" + +# Decision records that set these policies (data/decisions.json). +EXPLOITATION_POLICY = "DEC-181" +DISCLOSURE_POLICY = "DEC-182" + +FACTORS = { + "criticality": "The resolved component's declared classification (data sensitivity, mission " + "criticality, agency scope); the fail-safe classification when it resolves to none. " + "PAIN is computed from it.", + "reachability": "Internet-reachability as the triage policy decides it (VER-EVA-EIR), with its basis.", + "exploitability": "Likely exploitability by the method's Figure 7 (VER-EVA-ELX), with its basis.", + "detectability": "How an attacker would learn of the vulnerability: observed from outside (DAST), " + "a published advisory, or configuration readable in the public source repository.", + "prevalence": "How many findings and components share the finding's group, and the share of the " + "inventory's components they cover.", + "privilege": "What exploitation requires (CVSS PR) and what it reaches (CVSS S, and whether the " + "component is an identity or key-management resource).", + "proximate": "Other findings (open, dispositioned or mitigated) and verified mitigations on the same " + "component, which the group and the decision records are read with.", + "known_threats": "CISA KEV membership and the exploit-prediction score with its date.", + "automatable": "VER-EVA-AIA: yes unless a decision record carries evidence that exploitation cannot " + "be automated, or the CVSS 4.0 vector says AU:N.", + "exploitation": "VDR-CSO-RES: active when an incident record names the finding or the vulnerability " + "is observed exploited; otherwise none observed, under the exploitation assessment " + f"policy ({EXPLOITATION_POLICY}).", +} + +_PRIVILEGED_TYPES = ("iam", "identity", "kms", "key", "cognito", "user_pool") + + +def group_key(f, decision_id): + """VER-EVA-GRV: a CVE groups every instance of it; otherwise a decision + record groups what it decided together (one root cause, one decision); + otherwise the check ID groups instances of one rule.""" + if f.get("cve"): + return f"cve:{f['cve']}" + if decision_id: + return f"decision:{decision_id}" + return f"check:{f.get('source')}:{f.get('tool_id')}" + + +def automatable(f, dec): + """(value, source). Defaults to yes (VER-EVA-AIA).""" + a = (dec or {}).get("automatable") + if isinstance(a, dict) and a.get("value") == "no" and str(a.get("evidence") or "").strip(): + return {"value": "no", "source": f"decision {dec['id']}", "evidence": a["evidence"].strip()} + vec = str(f.get("cvss_vector") or "") + if vec.startswith("CVSS:4.0/") and "/AU:" in vec: + au = vec.split("/AU:", 1)[1][:1] + return {"value": "yes" if au == "Y" else "no", "source": "CVSS 4.0 AU", "evidence": vec} + return {"value": "yes", "source": "VER-EVA-AIA default", "evidence": None} + + +def detectability(f, irv): + src = f.get("source") + if src == "zap" or f.get("locations"): + return {"value": "observed-outside-in", "basis": "found by an unauthenticated outside-in scan"} + if f.get("cve") or src in ("grype", "dependabot"): + return {"value": "public-advisory", + "basis": "a published advisory names the package; " + + ("the component is internet-reachable" if irv else "the component is not internet-reachable")} + if src == "process": + return {"value": "provider-only", "basis": "a failure of the provider's own pipeline"} + return {"value": "public-source", "basis": "configuration in the public source repository"} + + +def privilege(f, cid, ctype, metrics): + pr = {"N": "none", "L": "low", "H": "high"}.get(metrics.get("PR"), "unknown") + ident = any(t in f"{ctype or ''} {cid or ''}".lower() for t in _PRIVILEGED_TYPES) + if metrics.get("S") == "C": + gained = "beyond-component" + elif ident: + gained = "identity-or-keys" + elif metrics: + gained = "within-component" + else: + gained = "unknown" + return {"required": pr, "gained": gained, + "basis": ("CVSS PR/S" if metrics else "no vector") + ("; identity or key-management component" if ident else "")} + + +def load_incidents(path=INCIDENTS): + """Incident records, when the register exists. Missing: none.""" + p = Path(path) + if not p.is_file(): + return [] + doc = json.loads(p.read_text(encoding="utf-8")) + recs = doc.get("incidents") if isinstance(doc, dict) else doc + return recs if isinstance(recs, list) else [] + + +def exploitation(f, is_kev, incidents, now_iso): + """VDR-CSO-RES: whether exploitation of this finding has been observed.""" + if str(f.get("exploitation") or "").lower() == "active": + return {"value": "active", "basis": "reported by the source", "assessed_at": now_iso} + keys = [k for k in (f.get("tracking_id"), f.get("cve")) if k] + for inc in incidents: + blob = json.dumps(inc, sort_keys=True) + if any(k in blob for k in keys): + return {"value": "active", "basis": f"incident {inc.get('id', '?')} names it", "assessed_at": now_iso} + basis = "no incident record names it" + if is_kev: + basis += "; exploited elsewhere (CISA KEV), which the policy treats as likely exploitable" + return {"value": "none-observed", "basis": f"{basis} ({EXPLOITATION_POLICY})", "assessed_at": now_iso} + + +def evaluation_record(row, f, *, cid, ctype, metrics, classification, auto, expl, proximate, prevalence, + epss, is_kev): + return { + "criticality": classification, + "reachability": {"irv": row["internet_reachable"], "basis": row["irv_basis"]}, + "exploitability": {"lev": row["likely_exploitable"], "basis": row["lev_basis"]}, + "detectability": detectability(f, row["internet_reachable"]), + "prevalence": prevalence, + "privilege": privilege(f, cid, ctype, metrics), + "proximate": proximate, + "known_threats": {"kev": bool(is_kev), "epss": epss}, + "automatable": auto, + "exploitation": expl, + } + + +def attach_groups(rows, inventory_size): + """Group membership, prevalence and proximate findings, after every row is + built. Returns the published groups.""" + groups, by_component = {}, {} + for r in rows: + groups.setdefault(r["group_id"], []).append(r) + if r.get("component_id"): + by_component.setdefault(r["component_id"], []).append(r) + out = [] + for gid, members in sorted(groups.items()): + comps = sorted({m["component_id"] for m in members if m.get("component_id")}) + prevalence = {"findings": len(members), "components": len(comps), + "inventory_share": round(len(comps) / inventory_size, 3) if inventory_size else None} + for m in members: + m["evaluation"]["prevalence"] = prevalence + g = members[0] + out.append({ + "group_id": gid, + "basis": gid.split(":", 1)[0], + "members": sorted(m["tracking_id"] for m in members), + "components": comps, + "pain": g.get("group_pain"), + "likely_exploitable": g.get("group_lev"), + "internet_reachable": g.get("group_irv"), + "remediation_due_at": g.get("group_due_at"), + "open_members": sum(1 for m in members if m["final_disposition"] == "open"), + "dispositions": sorted({m["final_disposition"] for m in members}), + }) + for r in rows: + others = [o for o in by_component.get(r.get("component_id"), []) if o is not r] + r["evaluation"]["proximate"] = { + "findings": sorted({o["tracking_id"] for o in others}), + "open": sum(1 for o in others if o["final_disposition"] == "open"), + "mitigations": sorted({o["mitigation"]["id"] for o in others + [r] + if isinstance(o.get("mitigation"), dict) and o["mitigation"].get("valid")}), + } + return out + + +# ---- disclosure (VER-RPT-NID, VER-RPT-RPD) ------------------------------------------ +# What the public artifacts withhold while a finding is open, internet-reachable, +# likely exploitable and rated N3 or higher: the detail that tells an attacker +# where and how (description, observed locations, fixed versions, evidence). The +# tracking ID, ratings, dates and status stay, so any party can make a +# risk-based decision. Policy: DEC-182. +WITHHELD_FIELDS = ("description", "locations", "fix_versions", "supplementary_info") +_WITHHOLD_FROM = 3 + + +def disclosure(row): + pain = str(row.get("pain") or "") + n = int(pain[1:]) if pain[1:].isdigit() else 0 + if (row.get("final_disposition") == "open" and row.get("internet_reachable") and row.get("likely_exploitable") + and n >= _WITHHOLD_FROM and not row.get("fully_mitigated")): + return {"level": "summary", "policy": DISCLOSURE_POLICY, + "reason": f"open, IRV, LEV and {pain}: detail withheld from public artifacts until remediated or " + "dispositioned; no party receives it (DEC-194)"} + return {"level": "full", "policy": DISCLOSURE_POLICY, + "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"} + + +# The withheld-detail request path (DEC-182), exercised on every VDR build +# against a simulated requester: it finds what a party would receive for each +# withheld finding and logs that, never the detail. With nothing withheld, a +# canned simulated finding goes through disclosure() so the path still runs. +WITHHELD_REQUESTER = "Necessary Party, Esq. (simulated)" +SIM_FINDING = {"tracking_id": "SIM-0001", "final_disposition": "open", "internet_reachable": True, + "likely_exploitable": True, "pain": "N4", "description": "A simulated finding (not real).", + "locations": ["simulated://nowhere"], "fix_versions": ["9.9.9"], "supplementary_info": "none"} + + +def withheld_detail_exercise(rows): + """The log entry for one exercise of the withheld-detail request path.""" + withheld = [r for r in rows if (r.get("public_disclosure") or disclosure(r))["level"] == "summary"] + canned = not withheld + if canned: + withheld = [SIM_FINDING] + if disclosure(SIM_FINDING)["level"] != "summary": + raise SystemExit("::error::withheld-detail exercise: the simulated finding was not withheld (fail-closed)") + entries = [] + for r in withheld: + detail = {k: r.get(k) for k in WITHHELD_FIELDS} + entries.append({"tracking_id": r.get("tracking_id"), + "withheldFields": [k for k in WITHHELD_FIELDS if r.get(k) not in (None, "", [])], + "detailSha256": hashlib.sha256( + json.dumps(detail, sort_keys=True, default=str).encode()).hexdigest()}) + return {"simulated": True, "requester": WITHHELD_REQUESTER, "decision": DISCLOSURE_POLICY, + "engagement": "Simulated (DEC-194): no real FedRAMP, agency or person took part, and nothing was " + "sent to anyone.", + "asks": "The withheld detail of every finding the public report summarizes, please. In triplicate.", + "cannedFinding": canned, "findings": entries, + "deliveredTo": "nobody: the requester is simulated; this log entry records what would be supplied " + "(field names and a sha256 of the detail), never the detail"} + + +def redact(row): + """The public form of a finding under its disclosure determination.""" + if (row.get("public_disclosure") or {}).get("level") != "summary": + return row + out = dict(row) + for k in WITHHELD_FIELDS: + if k in out: + if out[k] not in (None, "", [], {}): + out[k] = f"[withheld under {DISCLOSURE_POLICY}]" if isinstance(out[k], str) else None + return out + + +# ---- failures are vulnerabilities (VDR-CSO-FAV) ------------------------------------------ +# A detection or response check that fails in detect-and-recover mode, or a +# finding still resting on a default after the evaluation window, is a process +# vulnerability: a finding with a tracking ID, a clock, a rating and a deadline, +# open for as long as the failure lasts and gone (remediated) when the check +# passes. A check in block mode stops the run instead; each such stopped run of +# the deploy or the nightly is listed in the next report with when it failed. +PROCESS_SEVERITY = "MEDIUM" # severity proxy: N2, narrow effect (detection degraded) +PIPELINE_WORKFLOWS = ("Deploy Website with OPA Compliance", "Evidence Nightly (VDR refresh)", "ZAP DAST Scan") + + +def process_findings(events, rows): + out = {} + for ev in events or []: + tid = f"process-{ev['check']}" + if tid not in out: + out[tid] = {"source": "process", "tool_id": ev["check"], "tracking_id": tid, + "title": f"Process failure: {ev.get('gate', '')} {ev['check']} ({ev.get('mode', '')})", + "description": ev.get("detail", ""), "severity": PROCESS_SEVERITY, + "resource": f"pipeline:{ev['check']}", "detected_at": ev.get("at")} + for r in rows or []: + if r.get("evaluation_late") == "default-after-evaluation-window" and r.get("source") != "process": + tid = f"process-evaluation-{r['tracking_id']}" + out[tid] = {"source": "process", "tool_id": "evaluation.default-after-window", "tracking_id": tid, + "title": "Process failure: evaluation still on a default after the VER-TFR-EVU window", + "description": f"{r['tracking_id']} has no vector and no prediction score", + "severity": PROCESS_SEVERITY, "resource": f"pipeline:evaluation:{r['tracking_id']}"} + return sorted(out.values(), key=lambda f: f["tracking_id"]) + + +def failed_runs(runs, since, workflows=PIPELINE_WORKFLOWS): + """Stopped runs of the pipeline on main since the previous report: when each + failed and which workflow. No run IDs or URLs are kept.""" + out = [] + for r in runs or []: + if (r.get("workflowName") in workflows and r.get("headBranch") == "main" + and str(r.get("createdAt") or "") > str(since or "")): + out.append({"tracking_id": f"process-run-{r['workflowName'].lower().replace(' ', '-')}-{r['createdAt']}", + "workflow": r["workflowName"], "event": r.get("event"), + "failed_at": r.get("createdAt"), "ended_at": r.get("updatedAt")}) + return sorted(out, key=lambda x: x["failed_at"]) + + +# ---- detection coverage per component (VDR-TFR-PCD) ----------------------------------------- +# Which detection techniques reached each inventory component, and when. A +# component no technique reached within the window is a detection gap: the +# build records a vdr.coverage event, which makes it a process finding. +PCD_WINDOW_DAYS = 31 # VDR-TFR-PCD Class C: at least once every month +_IAC = ("checkov", "tfsec") +_SCA = ("grype", "dependabot") +# Component type -> the techniques that detect vulnerabilities in it. +TECHNIQUES = { + "npm_package": _SCA, "pypi_package": _SCA, + "html_artifact": ("zap-site",), + "api_gateway": _IAC + ("zap-api",), + "function": _IAC + _SCA + ("codeql",), +} +# Components outside the provider's own detection: the third party detects in +# its service, and the provider monitors it through the third-party register. +EXTERNAL_TYPES = {"external_service": "third-party service: detection is the provider's own " + "(data/third-party-components.json)"} + + +def _feed_times(detection, dast): + """{technique: ISO time it last ran}, from the detection gate's summary of + this run (a feed without a source date counts at the gate's check time) + and the DAST summary.""" + out = {} + det = detection or {} + for f in det.get("feeds") or []: + if isinstance(f, dict) and f.get("status") == "ok": + at = f.get("source_date") or det.get("checked_at") + if at and (f["feed"] not in out or at > out[f["feed"]]): + out[f["feed"]] = at + if (dast or {}).get("status") == "ok" and dast.get("generated_at"): + out["zap-site"] = dast["generated_at"] + return out + + +def coverage(components, detection, dast, now): + from datetime import datetime, timedelta + times = _feed_times(detection, dast) + floor = (now - timedelta(days=PCD_WINDOW_DAYS)).isoformat() + rows, uncovered = [], [] + for cid, comp in sorted((components or {}).items()): + ctype = comp.get("type") + if ctype in EXTERNAL_TYPES: + rows.append({"component_id": cid, "type": ctype, "techniques": [], "external": EXTERNAL_TYPES[ctype]}) + continue + wanted = TECHNIQUES.get(ctype) or (_IAC if comp.get("resource_type") else ()) + techs = [{"technique": t, "at": times.get(t)} for t in wanted] + recent = [t["at"] for t in techs if t["at"] and + datetime.fromisoformat(t["at"].replace("Z", "+00:00")).isoformat() >= floor] + row = {"component_id": cid, "type": ctype, "techniques": techs, + "last_detection": max(recent) if recent else None} + rows.append(row) + if not recent: + uncovered.append(cid) + return {"window_days": PCD_WINDOW_DAYS, "components": rows, "uncovered": uncovered, + "covered": len(rows) - len(uncovered) - sum(1 for r in rows if "external" in r)} diff --git a/scripts/_freshness.py b/scripts/_freshness.py index 8272426c..06024ef4 100644 --- a/scripts/_freshness.py +++ b/scripts/_freshness.py @@ -33,6 +33,7 @@ ".well-known/vdr-report.json", ".well-known/ksi-signal-runtime.json", ".well-known/vdr-status.json", + ".well-known/incident-reports.json", ".well-known/boundary-corroboration.json", ) diff --git a/scripts/_frr.py b/scripts/_frr.py new file mode 100644 index 00000000..d0fb6ca7 --- /dev/null +++ b/scripts/_frr.py @@ -0,0 +1,330 @@ +"""The FedRAMP rule records: data/frr-records.json (SDR-CSO-FRR). + +One record per FedRAMP rule that applies to this system's certification (20x, +Program path, Class C), saying whether the rule is implemented, how, what shows +it, and, when it isn't, what is missing and which piece of work closes it. The +Security Decision Record publishes these records; nothing else may say a rule +is met. + +The register is only allowed to claim what the repository can show: + +- The applicable rule set comes from the pinned corpus (_rules.applicable_provider_rules). + A missing or extra record fails, so a re-pinned corpus that adds a rule + cannot be published past. +- "Implemented" needs at least one piece of evidence, and every piece of + evidence on any record must resolve: + test tests/<file>.py::<test>[::<method>] a test function that exists + step <workflow>.yml#<step name> a step in .github/workflows/ + artifact .well-known/<name> a published, freshness-governed artifact + decision DEC-NNN an in-force decision record +- "Not Applicable" states why (not_applicable) and is allowed only where + FedRAMP's own scoping makes the rule conditional on something the provider + is not doing (a subset in CONDITIONAL_SUBSETS, such as seeking a Marketplace + listing) or the rule is a MAY permission not exercised. +- Anything else short of implemented states its gap and what closes it: a + workstream (W2..W10) or "sam" (an act only the operator can perform, such as + a registration or engaging an assessor). +- Every MAY rule says why it was or wasn't exercised (may_rationale); no + other rule carries one. +- No record text may carry an AWS account ID, or an email address outside the + system's domain and FedRAMP's (the SDR is published). +- A record that relies on a simulated outside party (an assessor, FedRAMP, an + agency, an incident recipient, the mail system, SAM.gov, or the personnel a + people-run process needs: review attendees, a trainee) says so in + `simulated` {counterparty, how}. Only an Implemented record may, and it must + cite deploy-time evidence (a workflow step or a published artifact): the + mechanism is real and exercised on every deploy; only the party is not. + +The deploy gate (`--complete`, operator's decision of 2026-11-05): the deploy +proceeds only when every record is Implemented or Not Applicable. Each record +describes the state after a successful deploy of the commit that contains it. + +Fails closed, stdlib only (the deploy job installs no jsonschema); the JSON +schema beside it documents the same shape and is checked in tests. +""" + +import ast +import json +import re +import sys +from collections import Counter +from functools import lru_cache +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _decisions # noqa: E402 +import _freshness # noqa: E402 +import _redact # noqa: E402 +import _rules # noqa: E402 + +REPO = Path(__file__).resolve().parent.parent +DEFAULT_PATH = REPO / "data" / "frr-records.json" +SCHEMA_PATH = REPO / "infrastructure" / "schemas" / "frr-records.schema.json" +WORKFLOWS = REPO / ".github" / "workflows" +TESTS = REPO / "tests" + +STATUSES = ("Implemented", "Partially Implemented", "Not Implemented", "Not Applicable") +# Subsets FedRAMP scopes to a provider act, in the subset description: the rules +# apply once the provider takes that step, and not before. +CONDITIONAL_SUBSETS = { + ("MKT", "CSO"): "providers seeking a listing in the FedRAMP Marketplace", + ("FRC", "APP"): "providers who have met all other relevant rules and are ready to apply", +} +WORKSTREAMS = tuple(f"W{n}" for n in range(2, 11)) +CLOSERS = (*WORKSTREAMS, "sam") +EVIDENCE_KINDS = ("test", "step", "artifact", "decision") +# Outside parties this proof of concept stands in for (DEC-194: no engagement): +# the mechanism is real and runs on every deploy or on its schedule; the party +# is not. `personnel` is the people a people-run process needs (Quarterly +# Review attendees, a trainee), so that no process waits on a person. +SIMULATED_COUNTERPARTIES = ("assessor", "fedramp", "agency", "incident-recipient", "mail", "sam-gov", "personnel") +SIMULATED_KEYS = {"counterparty", "how"} +# What the completeness gate accepts: the deploy proceeds only when every +# applicable rule is one of these. +COMPLETE_STATUSES = ("Implemented", "Not Applicable") + +TOP_KEYS = {"$comment", "schema", "basis", "records"} +RECORD_KEYS = {"frr_id", "status", "implementation", "evidence", "gap", "closes_with", "may_rationale", + "not_applicable", "simulated"} +EVIDENCE_KEYS = {"kind", "ref"} + +TEST_RE = re.compile(r"^(tests/[A-Za-z0-9_/]+\.py)::([A-Za-z_][A-Za-z0-9_]*)(?:::([A-Za-z_][A-Za-z0-9_]*))?(?:\[[^\]]*\])?$") +STEP_RE = re.compile(r"^([A-Za-z0-9_.-]+\.ya?ml)#(.+)$") +STEP_LINE_RE = re.compile(r"^\s*-\s+name:\s*(.+?)\s*$") +EMAIL_RE = re.compile(r"[A-Za-z0-9._%+-]+@([A-Za-z0-9-]+(?:\.[A-Za-z0-9-]+)+)") +# Addresses a record may name: the system's own domain and FedRAMP's senders +# (AFC-CSO-TFG). Anything else, a personal mailbox above all, stays out of the SDR. +EMAIL_DOMAINS = ("samaydlette.com", "fedramp.gov", "gsa.gov") + + +def _fail(msg): + raise SystemExit(f"::error::FRR records: {msg} (fail-closed)") + + +# --- evidence resolution ---------------------------------------------------------- + +@lru_cache(maxsize=None) +def _test_names(path): + """{function name} and {(class, method)} defined in a test module.""" + tree = ast.parse(Path(path).read_text(), filename=str(path)) + funcs, methods = set(), set() + for node in tree.body: + if isinstance(node, (ast.FunctionDef, ast.AsyncFunctionDef)): + funcs.add(node.name) + elif isinstance(node, ast.ClassDef): + for sub in node.body: + if isinstance(sub, (ast.FunctionDef, ast.AsyncFunctionDef)): + methods.add((node.name, sub.name)) + return funcs, methods + + +@lru_cache(maxsize=None) +def _step_names(path): + names = set() + for line in Path(path).read_text().splitlines(): + m = STEP_LINE_RE.match(line) + if m: + names.add(m.group(1).strip().strip("'\"")) + return names + + +def _resolve_test(ref, repo): + m = TEST_RE.match(ref) + if not m: + return "is not tests/<file>.py::<test>" + rel, first, second = m.groups() + path = repo / rel + if ".." in rel or not path.is_file(): + return f"{rel} does not exist" + funcs, methods = _test_names(str(path)) + if second is None: + ok = first in funcs and first.startswith("test") + else: + ok = (first, second) in methods and second.startswith("test") + return None if ok else "names no test function in that file" + + +def _resolve_step(ref, repo): + m = STEP_RE.match(ref) + if not m: + return "is not <workflow>.yml#<step name>" + wf, step = m.groups() + path = repo / ".github" / "workflows" / wf + if not path.is_file(): + return f"workflow {wf} does not exist" + return None if step in _step_names(str(path)) else f"no step named {step!r} in {wf}" + + +def resolver(repo=REPO, freshness_path=None, decisions_path=None): + """A function evidence -> None when it resolves, else the reason it doesn't.""" + repo = Path(repo) + published = {a["path"] for a in _freshness.load_freshness_config( + freshness_path or repo / "infrastructure" / "schemas" / "freshness-config.json")["artifacts"]} + in_force = {r["id"] for r in _decisions.in_force(_decisions.load(decisions_path or repo / "data" / "decisions.json"))} + + def resolve(ev): + kind, ref = ev["kind"], ev["ref"] + if kind == "test": + return _resolve_test(ref, repo) + if kind == "step": + return _resolve_step(ref, repo) + if kind == "artifact": + return None if ref in published else "is not a freshness-governed published artifact" + if kind == "decision": + return None if ref in in_force else "is not an in-force decision record" + return f"unknown evidence kind {kind!r}" + return resolve + + +# --- validation ------------------------------------------------------------------- + +def _text(rec, key, rid, required=True): + v = rec.get(key) + if v is None and not required: + return None + if not isinstance(v, str) or not v.strip(): + _fail(f"{rid}: {key} must be a non-empty string") + if _redact.find(v): + _fail(f"{rid}: {key} carries an AWS account ID") + for m in EMAIL_RE.finditer(v): + if m.group(1).lower() not in EMAIL_DOMAINS: + _fail(f"{rid}: {key} names an email address outside {list(EMAIL_DOMAINS)}") + return v + + +def validate(doc, applicable, resolve, where="data/frr-records.json"): + """Structural and honesty checks. `applicable` is {rule ID: rule} from the + corpus; `resolve` maps evidence to None or a failure reason.""" + if not isinstance(doc, dict) or doc.get("schema") != "frr-records/1": + _fail(f"{where} is not an frr-records/1 document") + if set(doc) - TOP_KEYS: + _fail(f"{where}: unknown top-level field(s) {sorted(set(doc) - TOP_KEYS)}") + _text(doc, "basis", "basis") + recs = doc.get("records") + if not isinstance(recs, list): + _fail(f"{where}: records must be a list") + seen = set() + for rec in recs: + rid = rec.get("frr_id") if isinstance(rec, dict) else None + if not isinstance(rid, str) or not rid: + _fail(f"{where}: a record has no frr_id") + if rid in seen: + _fail(f"duplicate record for {rid}") + seen.add(rid) + if rid not in applicable: + _fail(f"{rid} is not a rule that applies to a 20x Class C provider (extra record)") + if set(rec) - RECORD_KEYS: + _fail(f"{rid}: unknown field(s) {sorted(set(rec) - RECORD_KEYS)}") + status = rec.get("status") + if status not in STATUSES: + _fail(f"{rid}: status {status!r} is not one of {list(STATUSES)}") + _text(rec, "implementation", rid) + if applicable[rid]["force"] == "MAY": + _text(rec, "may_rationale", rid) + elif "may_rationale" in rec: + _fail(f"{rid}: may_rationale is for MAY rules only (Class C force is {applicable[rid]['force']})") + evidence = rec.get("evidence", []) + if not isinstance(evidence, list): + _fail(f"{rid}: evidence must be a list") + for ev in evidence: + if not isinstance(ev, dict) or set(ev) != EVIDENCE_KEYS or ev.get("kind") not in EVIDENCE_KINDS \ + or not isinstance(ev.get("ref"), str) or not ev["ref"]: + _fail(f"{rid}: evidence {ev!r} must be {{kind: one of {list(EVIDENCE_KINDS)}, ref}}") + why = resolve(ev) + if why: + _fail(f"{rid}: {ev['kind']} evidence {ev['ref']!r} does not resolve: {why}") + if "simulated" in rec: + sim = rec["simulated"] + if not isinstance(sim, dict) or set(sim) != SIMULATED_KEYS \ + or sim.get("counterparty") not in SIMULATED_COUNTERPARTIES: + _fail(f"{rid}: simulated must be {{counterparty: one of {list(SIMULATED_COUNTERPARTIES)}, how}}") + _text(sim, "how", f"{rid} simulated") + if status != "Implemented": + _fail(f"{rid}: simulated is for Implemented records only") + if not any(ev["kind"] in ("step", "artifact") for ev in evidence): + _fail(f"{rid}: a simulated counterparty needs deploy-time evidence (a workflow step or a " + f"published artifact): the simulation runs on every deploy") + closes = rec.get("closes_with") + if status == "Implemented": + if not evidence: + _fail(f"{rid}: Implemented needs evidence that resolves") + if rec.get("gap") is not None or closes is not None: + _fail(f"{rid}: an Implemented record has no gap and nothing closing it") + continue + if status == "Not Applicable": + rule = applicable[rid] + if rule["force"] != "MAY" and (rule["family"], rule.get("subset")) not in CONDITIONAL_SUBSETS: + _fail(f"{rid}: cannot be Not Applicable: FedRAMP scopes it to every 20x Class C provider " + f"(force {rule['force']})") + _text(rec, "not_applicable", rid) + if rec.get("gap") is not None or closes is not None: + _fail(f"{rid}: a Not Applicable record has no gap and nothing closing it") + continue + if "not_applicable" in rec: + _fail(f"{rid}: not_applicable is for Not Applicable records only") + _text(rec, "gap", rid) + if not isinstance(closes, list) or not closes or len(set(closes)) != len(closes) \ + or any(c not in CLOSERS for c in closes): + _fail(f"{rid}: closes_with must be a non-empty list drawn from {list(CLOSERS)}") + missing = sorted(set(applicable) - seen) + if missing: + _fail(f"no record for {len(missing)} applicable rule(s): {', '.join(missing)}") + return doc + + +def load(path=None, rules_dir=None, repo=REPO, freshness_path=None, decisions_path=None): + p = Path(path) if path else DEFAULT_PATH + if not p.is_file(): + _fail(f"{p} not found") + try: + doc = json.loads(p.read_text()) + except (json.JSONDecodeError, UnicodeDecodeError) as exc: + _fail(f"{p} is not valid JSON: {exc}") + applicable = _rules.applicable_provider_rules(rules_dir or _rules.RULES_DIR) + return validate(doc, applicable, resolver(repo, freshness_path, decisions_path), str(p)) + + +def incomplete(doc): + """The records that keep the deploy from proceeding: every rule must be + Implemented or Not Applicable (operator's decision of 2026-11-05).""" + return [(r["frr_id"], r["status"]) for r in doc["records"] if r["status"] not in COMPLETE_STATUSES] + + +def summary(doc, applicable): + """Counts the trust center and the SDR can show: by status, and by status + within each force (MUST, SHOULD, ...).""" + by_status = Counter(r["status"] for r in doc["records"]) + by_force = {} + for r in doc["records"]: + f = applicable[r["frr_id"]]["force"] + by_force.setdefault(f, Counter())[r["status"]] += 1 + simulated = Counter(r["simulated"]["counterparty"] for r in doc["records"] if "simulated" in r) + return {"rules": len(doc["records"]), + "by_status": {s: by_status.get(s, 0) for s in STATUSES}, + "simulated": {c: simulated[c] for c in sorted(simulated)}, + "by_force": {f: {s: c.get(s, 0) for s in STATUSES} for f, c in sorted(by_force.items())}} + + +def main(argv=None): + import argparse + ap = argparse.ArgumentParser(description="Validate data/frr-records.json against the pinned FedRAMP rules.") + ap.add_argument("--records", default=str(DEFAULT_PATH)) + ap.add_argument("--complete", action="store_true", + help="also fail unless every record is Implemented or Not Applicable (the deploy gate)") + args = ap.parse_args(argv) + doc = load(args.records) + print(json.dumps(summary(doc, _rules.applicable_provider_rules()), indent=2)) + if args.complete: + open_ = incomplete(doc) + if open_: + for rid, status in open_: + print(f"::error::{rid} is {status}: every applicable rule must be Implemented or Not Applicable") + print(f"{len(open_)} of {len(doc['records'])} rule(s) not complete; the deploy does not proceed.", + file=sys.stderr) + return 1 + print("Every applicable rule is Implemented or Not Applicable.") + return 0 + + +if __name__ == "__main__": + raise SystemExit(main()) diff --git a/scripts/_fsi.py b/scripts/_fsi.py new file mode 100644 index 00000000..d9f0a7c4 --- /dev/null +++ b/scripts/_fsi.py @@ -0,0 +1,322 @@ +"""FedRAMP Security Inbox logic, as pure functions (no I/O, no network). + +The FedRAMP Security Inbox is SIMULATED for this proof of concept, by the +operator's decision: no mail is received and none is sent. This module is the +logic a real inbox would run, and scripts/build-fsi-simulation.py runs it on +every deploy over committed synthetic messages (data/fsi-simulation/), failing +the deploy if any outcome differs from what the message file expects. + +Rules the logic implements (FedRAMP Consolidated Rules 2026, AFC family): + AFC-CSO-TFG mail from @fedramp.gov or @gsa.gov (exact domains) is FedRAMP + by default, whatever its spam or authentication verdict + AFC-CSO-EMR Emergency-designated mail pages the senior security official + AFC-CSO-CRA Emergency / Emergency Test mail gets a tracked deadline + AFC-CSO-IMA Important mail gets a tracked item, triaged with its timeframe + AFC-CSO-ACK FedRAMP mail is acknowledged automatically, once +with the designators from AFC-FRP-CDS, the Emergency senders from AFC-FRP-UFS +and the default Class C timeframe from AFC-FRP-ERT. + +Every string taken from a message is untrusted: it is length-capped and +stripped of control and bidirectional-override characters before it is stored +or used, and nothing from a message reaches an outbound header except as a +validated address, a validated Message-ID, or base64. +""" + +from __future__ import annotations + +import base64 +import re +from datetime import datetime, timedelta, timezone +from zoneinfo import ZoneInfo + +FEDRAMP_DOMAINS = ("fedramp.gov", "gsa.gov") +EMERGENCY_SENDERS = ("fedramp_security@gsa.gov", "fedramp_security@fedramp.gov") +DESIGNATIONS = ("EMERGENCY", "EMERGENCY_TEST", "IMPORTANT", "GENERAL") +TRIAGE_HOURS = {"EMERGENCY": 2, "EMERGENCY_TEST": 2, "IMPORTANT": 24, "GENERAL": 72} +CLASS_C_BUSINESS_DAYS = 2 +CLASS_C_HOUR_ET = 15 +VERDICTS = ("PASS", "FAIL", "GRAY", "PROCESSING_FAILED") +MAX_SUBJECT = 200 +MAX_ADDRESS = 254 +ET = ZoneInfo("America/New_York") + +CONTROL = re.compile("[\x00-\x1f\x7f-\x9f\u200b-\u200f\u2028-\u202e\u2066-\u2069\ufeff]") +ADDR_SPEC = re.compile(r"^[a-z0-9!#$%&'*+/=?^_`{|}~.-]{1,64}@[a-z0-9-]{1,63}(?:\.[a-z0-9-]{1,63})+$") +RFC_MESSAGE_ID = re.compile(r"^<[\x21-\x3b\x3d\x3f-\x7e]{1,250}>$") +ANGLED = re.compile(r"<([^<>\s]+)>") +LABEL = {"EMERGENCY": "EMERGENCY", "EMERGENCY_TEST": "EMERGENCY TEST", "IMPORTANT": "IMPORTANT", "GENERAL": "General"} + + +def clean_text(value, limit: int = MAX_SUBJECT) -> str: + """One safe line: no control or bidi characters, whitespace collapsed, capped.""" + s = CONTROL.sub(" ", "" if value is None else str(value)) + return " ".join(s.split())[:limit] + + +def parse_address(value) -> str | None: + """The addr-spec in a From-style value, lower-cased, or None.""" + s = clean_text(value, 1000) + if not s: + return None + angled = ANGLED.findall(s) + candidate = (angled[-1] if angled else s).lower() + if len(candidate) > MAX_ADDRESS or not ADDR_SPEC.match(candidate): + return None + return candidate + + +def domain_of(address: str | None) -> str | None: + return address.rsplit("@", 1)[1] if address else None + + +def is_fedramp_address(address: str | None) -> bool: + """AFC-CSO-TFG: exact domains only. Subdomains and look-alikes are not FedRAMP.""" + return domain_of(address) in FEDRAMP_DOMAINS + + +def designation_of(subject) -> str: + """AFC-FRP-CDS designator anywhere in the subject, any case. Broad on purpose: + a false Emergency costs a page; a missed one costs the deadline.""" + s = clean_text(subject, 1000).lower() + if re.search(r"\bemergency[\s_-]*test\b", s): + return "EMERGENCY_TEST" + if re.search(r"\bemergency\b", s): + return "EMERGENCY" + if re.search(r"\bimportant\b", s): + return "IMPORTANT" + return "GENERAL" + + +def _header(headers, name: str) -> str | None: + want = name.lower() + for k, v in (headers or {}).items(): + if isinstance(k, str) and k.lower() == want: + return clean_text(v, 1000) + return None + + +def _verdict(v) -> str: + s = v.upper() if isinstance(v, str) else "MISSING" + return s if s in VERDICTS else "MISSING" + + +def authenticated(auth: dict) -> bool: + """AFC-FRP-VRE: FedRAMP sends with SPF, DKIM and DMARC configured.""" + return auth["dmarc"] == "PASS" or (auth["dkim"] == "PASS" and auth["spf"] == "PASS") + + +def loop_reason(headers, source, sender: str | None) -> str | None: + """Why an automatic reply must not be sent to this message, or None.""" + auto = _header(headers, "auto-submitted") + if auto and auto.lower() != "no": + return "auto-submitted" + if (_header(headers, "precedence") or "").lower() in ("bulk", "junk", "list", "auto_reply"): + return "precedence" + src = str(source or "").strip() + if not src or src == "<>": + return "null-sender" + if sender and sender.split("@", 1)[0] in ("mailer-daemon", "postmaster"): + return "daemon" + if not sender: + return "no-from-address" + return None + + +def classify(msg: dict) -> dict: + """Classify one message: {from, envelope, subject, headers, auth}. + + FedRAMP if the From address or the envelope sender is at an exact FedRAMP + domain. Spam and authentication verdicts are recorded and never change the + classification. They do stop the acknowledgement: FedRAMP's own mail passes + SPF/DKIM/DMARC, so suppressing the reply to unauthenticated mail loses + nothing genuine and stops a forged @gsa.gov From from turning the inbox into + a reflector that mails attacker-chosen text to any government address. + """ + sender = parse_address(msg.get("from")) + envelope = parse_address(msg.get("envelope")) + subject = clean_text(msg.get("subject")) + fedramp = is_fedramp_address(sender) or is_fedramp_address(envelope) + designation = designation_of(subject) if fedramp else "GENERAL" + raw_auth = msg.get("auth") or {} + auth = {k: _verdict(raw_auth.get(k)) for k in ("spf", "dkim", "dmarc")} + authed = authenticated(auth) + emergency = designation in ("EMERGENCY", "EMERGENCY_TEST") + mid = _header(msg.get("headers"), "message-id") + return { + "kind": "fedramp" if fedramp else "other", + "from": sender, + "sender_domain": domain_of(sender if is_fedramp_address(sender) else (envelope or sender)), + "subject": subject, + "designation": designation, + "auth": auth, + "authenticated": authed, + "emergency_sender_ok": (sender in EMERGENCY_SENDERS) if emergency else None, + "rfc_message_id": mid if mid and RFC_MESSAGE_ID.match(mid) else None, + "loop": loop_reason(msg.get("headers"), msg.get("envelope"), sender) or (None if authed else "unauthenticated"), + } + + +# --- deadlines ---------------------------------------------------------------- + +def parse_time(value: str) -> datetime: + t = datetime.fromisoformat(str(value).replace("Z", "+00:00")) + if t.tzinfo is None: + raise ValueError(f"timestamp without a zone: {value!r}") + return t.astimezone(timezone.utc) + + +def iso(t: datetime) -> str: + return t.astimezone(timezone.utc).strftime("%Y-%m-%dT%H:%M:%SZ") + + +def class_c_deadline(received: datetime, business_days: int = CLASS_C_BUSINESS_DAYS, + hour_et: int = CLASS_C_HOUR_ET) -> datetime: + """3:00 p.m. ET on the Nth business day, counting the day of receipt as day 1 + when it is a weekday. That reading of "the 2nd business day" gives the + earlier of the two possible deadlines, and federal holidays are not skipped, + which can only make it earlier still. Both err toward acting sooner.""" + day = received.astimezone(ET).date() + counted = 0 + for _ in range(14): + if day.weekday() < 5: + counted += 1 + if counted == business_days: + return datetime(day.year, day.month, day.day, hour_et, tzinfo=ET).astimezone(timezone.utc) + day += timedelta(days=1) + raise RuntimeError("business-day search did not terminate") + + +def deadlines(designation: str, received: datetime) -> dict: + triage_by = iso(received + timedelta(hours=TRIAGE_HOURS[designation])) + if designation in ("EMERGENCY", "EMERGENCY_TEST"): + return {"triage_by": triage_by, "respond_by": iso(class_c_deadline(received)), + "deadline_basis": "AFC-FRP-ERT Class C default (3:00 p.m. ET, 2nd business day); " + "replace with the timeframe stated in the message"} + if designation == "IMPORTANT": + return {"triage_by": triage_by, "respond_by": None, + "deadline_basis": "Record the timeframe stated in the message (AFC-CSO-IMA) when triaging"} + return {"triage_by": triage_by, "respond_by": None, + "deadline_basis": "General communication: no elevated timeframe (AFC-FRP-CDS)"} + + +# --- register ------------------------------------------------------------------- + +def new_record(rid: str, c: dict, received: datetime) -> dict: + return {"id": rid, "received_at": iso(received), "kind": c["kind"], "sender_domain": c["sender_domain"], + "subject": c["subject"], "designation": c["designation"], "auth": c["auth"], + "authenticated": c["authenticated"], "emergency_sender_ok": c["emergency_sender_ok"], + "status": "open", **deadlines(c["designation"], received), + "ack": {"status": "pending"}, "page": {"status": "pending"}, "history": []} + + +def triage(record: dict, at: datetime, respond_by: str | None = None) -> dict: + """Mark a record triaged. An Important message cannot be triaged without the + timeframe stated in it (AFC-CSO-IMA); a stated timeframe replaces the default.""" + if record["status"] == "closed": + raise ValueError(f"{record['id']} is closed") + if respond_by: + record["respond_by"] = iso(parse_time(respond_by)) + record["deadline_basis"] = "Timeframe stated in the message, recorded at triage" + if record["designation"] == "IMPORTANT" and not record.get("respond_by"): + raise ValueError(f"{record['id']}: an Important message needs the timeframe it states (respond_by)") + record["status"] = "triaged" + record["history"].append({"at": iso(at), "event": "triaged"}) + return record + + +def close(record: dict, at: datetime, outcome: str) -> dict: + if not clean_text(outcome): + raise ValueError("closing needs an outcome") + record["status"] = "closed" + record["closed_at"] = iso(at) + record["history"].append({"at": iso(at), "event": "closed", "outcome": clean_text(outcome)}) + return record + + +def overdue(records, now: datetime) -> list[str]: + """Problems that should page: untriaged past triage_by, not closed past + respond_by, Important triaged without its timeframe, ack or page failed.""" + problems = [] + for r in records: + tag = f"{r['id']} ({r['designation']})" + if r["status"] == "open" and r.get("triage_by") and now > parse_time(r["triage_by"]): + problems.append(f"{tag}: not triaged by {r['triage_by']}") + if r["status"] != "closed" and r.get("respond_by") and now > parse_time(r["respond_by"]): + problems.append(f"{tag}: required actions not closed by {r['respond_by']}") + if r["designation"] == "IMPORTANT" and r["status"] != "open" and not r.get("respond_by"): + problems.append(f"{tag}: triaged without recording the message's timeframe") + for leg in ("ack", "page"): + if (r.get(leg) or {}).get("status") == "failed": + problems.append(f"{tag}: {leg} failed") + return problems + + +# --- outbound text ------------------------------------------------------------------ + +def _b64(s: str) -> str: + return base64.b64encode(s.encode("utf-8")).decode("ascii") + + +def build_ack(*, inbox: str, to: str, subject: str, rfc_message_id: str | None, + received_at: str, designation: str, ref: str) -> str: + """The raw acknowledgement (RFC 5322). Every header value is a constant, a + validated address, a validated Message-ID, or base64, so nothing from the + inbound message can inject a header.""" + frm, rcpt = parse_address(inbox), parse_address(to) + if not frm or not rcpt: + raise ValueError("acknowledgement needs valid From and To addresses") + subj = clean_text(subject) or "(no subject)" + lines = [f"From: FedRAMP Security Inbox <{frm}>", f"To: <{rcpt}>", + f"Subject: =?UTF-8?B?{_b64('Received: ' + subj)}?=", + "Auto-Submitted: auto-replied", "X-Auto-Response-Suppress: All", "MIME-Version: 1.0", + "Content-Type: text/plain; charset=UTF-8", "Content-Transfer-Encoding: base64"] + if rfc_message_id and RFC_MESSAGE_ID.match(rfc_message_id): + lines += [f"In-Reply-To: {rfc_message_id}", f"References: {rfc_message_id}"] + body = "\n".join([ + f"This is an automatic acknowledgement from the FedRAMP Security Inbox ({frm}).", "", + f"Your message was received at {clean_text(received_at, 40)}.", + f"Designation recognised from the subject line: {LABEL.get(designation, 'General')}.", + f"Reference: {clean_text(ref, 80)}", "", + "The security official has been notified. This reply is automatic; a person will respond separately."]) + b64 = _b64(body) + wrapped = "\r\n".join(b64[i:i + 76] for i in range(0, len(b64), 76)) + return "\r\n".join(lines) + "\r\n\r\n" + wrapped + "\r\n" + + +def page_subject(record: dict) -> str: + """The page's subject: ASCII, at most 100 characters, sender domain only.""" + s = f"[FSI] {LABEL.get(record['designation'], 'General')} FedRAMP message from {record['sender_domain'] or 'unknown'}" + return re.sub(r"[^\x20-\x7e]", "?", s)[:100] + + +# --- one message through the inbox ------------------------------------------------------ + +def receive(msg: dict, register: dict, *, inbox: str, send, page) -> dict: + """Handle one message the way the inbox would. `send(to, raw)` and + `page(subject)` are the outbound legs (in the simulation, recorders that + send nothing). Idempotent: a message already in the register only retries + the legs that did not complete, so a sender is acknowledged once.""" + c = classify(msg) + if c["kind"] != "fedramp": + return {"classification": c, "record": None} + rid = clean_text(msg.get("message_id"), 128) + if not re.fullmatch(r"[A-Za-z0-9._-]{1,128}", rid): + raise ValueError("message_id must be a safe register identifier") + received = parse_time(msg["received_at"]) + record = register.get(rid) or new_record(rid, c, received) + register[rid] = record + if record["ack"]["status"] in ("pending", "failed"): + if c["loop"]: + record["ack"] = {"status": "suppressed", "reason": c["loop"]} + else: + try: + send(c["from"], build_ack(inbox=inbox, to=c["from"], subject=c["subject"], + rfc_message_id=c["rfc_message_id"], received_at=record["received_at"], + designation=c["designation"], ref=rid)) + record["ack"] = {"status": "sent"} + except Exception as e: # noqa: BLE001 - a failed leg is recorded and paged by overdue() + record["ack"] = {"status": "failed", "error": type(e).__name__} + if record["page"]["status"] != "sent": + page(page_subject(record)) + record["page"] = {"status": "sent"} + return {"classification": c, "record": record} diff --git a/scripts/_gates.py b/scripts/_gates.py index d9c48274..2bf07d59 100644 --- a/scripts/_gates.py +++ b/scripts/_gates.py @@ -62,6 +62,7 @@ "reconcile.e": "G6", "reconcile.f": "G6", "reconcile.l": "G6", + "reconcile.m": "G5", "reconcile.i.unreadable": "G7", "runtime-divergence.observer-fault": "G7", "detection.zap.missing": "G7", @@ -73,11 +74,23 @@ "detection.previous-vdr": "G7", "detection.checkov": "G7", "detection.tfsec": "G7", + "detection.codeql": "G7", + "detection.zap-api": "G7", + "vdr.coverage": "G7", + "vdr.unresolved-component": "G7", + "audit-log.unexpected": "G7", + "audit-log.reportable": "G7", } TOP_KEYS = {"$schema", "version", "description", "method_reference", "checks"} -ENTRY_KEYS = {"check", "gate", "mode", "method_default", "reason", "decided_by", "decided_on", "review_by"} -REQUIRED_ENTRY_KEYS = ENTRY_KEYS - {"reason"} +ENTRY_KEYS = {"check", "gate", "mode", "method_default", "reason", "decided_by", "decided_on", "review_by", + "confirmed_on", "drafted_by"} +# A mode is in force only once the operator has confirmed it (confirmed_on), as +# for decision records; who drafted the wording, when not the operator, is +# drafted_by, never a note in the reason. +REQUIRED_ENTRY_KEYS = ENTRY_KEYS - {"reason", "drafted_by"} +MARKING_RE = re.compile(r"(?i)\bAI[- ]drafted\b|not yet confirmed|confirm at review|\bproposed\b|" + r"for the operator'?s? (to confirm|confirmation)") DATE_RE = re.compile(r"^\d{4}-\d{2}-\d{2}$") # Set by the workflows. When present, every detect-and-recover event is appended @@ -141,7 +154,14 @@ def validate_gate_modes(cfg, where="(in memory)", today=None): _fail(where, f"{name}: the method's default for every gate is block") if not isinstance(e["decided_by"], str) or not e["decided_by"].strip(): _fail(where, f"{name}: decided_by must name who decided the mode") - _date(where, name, "decided_on", e["decided_on"]) + decided_on = _date(where, name, "decided_on", e["decided_on"]) + if _date(where, name, "confirmed_on", e["confirmed_on"]) < decided_on: + _fail(where, f"{name}: confirmed_on is before decided_on") + if "drafted_by" in e and (not isinstance(e["drafted_by"], str) or not e["drafted_by"].strip()): + _fail(where, f"{name}: drafted_by must be a non-empty string") + for key in ("reason", "decided_by"): + if isinstance(e.get(key), str) and MARKING_RE.search(e[key]): + _fail(where, f"{name}: {key} carries a drafting or confirmation note; use drafted_by and confirmed_on") review_by = _date(where, name, "review_by", e["review_by"]) if e["mode"] != e["method_default"]: if not isinstance(e.get("reason"), str) or not e["reason"].strip(): diff --git a/scripts/_incidents.py b/scripts/_incidents.py new file mode 100644 index 00000000..14fd68c2 --- /dev/null +++ b/scripts/_incidents.py @@ -0,0 +1,412 @@ +"""The incident register: data/incidents.json (IEC-CSO-EFR/DPR/EFI/IIR/OIR/FIR). + +Every incident the operator records lives here, once, with the evaluation the +FedRAMP Incident Evaluation and Communication rules ask for: + +- evaluation when it was evaluated, whether it is a FedRAMP Reportable + Incident (IEC-CSO-EFR) and why; the basis is IEC-CSO-EFR, or + VER-TFR-IRI / VER-TFR-NRI for a vulnerability treated as one +- estimates Incident Rating records (IEC-CSO-EFI): rating, customer effect, + one or several agencies, reason, when. Until the first one, a + reportable incident is rated at the default (IEC-CSO-DPR) +- reports the Initial, Ongoing and Final reports, each with when it was + issued and what it set; a report restates everything set before +- resolved_at / recovery_complete_at, which start the Final report's clock + +The clocks (when each report is due) come from FedRAMP's Class C timeframes +through scripts/_rules.py, never from this file. scripts/build-incident-report.py +renders the reports and the incident log from it; reconciliation checks the +findings an incident names against the VDR. + +Fails closed, stdlib only (the deploy job installs no jsonschema), following +scripts/_decisions.py: a missing or invalid register stops the build. The JSON +schema beside it (infrastructure/schemas/incidents.schema.json) documents the +same shape and is checked in tests. +""" + +import json +import re +import sys +from datetime import datetime, timedelta, timezone +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _redact # noqa: E402 +import _rules # noqa: E402 + +REPO = Path(__file__).resolve().parent.parent +DEFAULT_PATH = REPO / "data" / "incidents.json" +SCHEMA_PATH = REPO / "infrastructure" / "schemas" / "incidents.schema.json" + +ID_RE = re.compile(r"^INC-\d{4}-\d{3}$") +DATE_RE = re.compile(r"^\d{4}-\d{2}-\d{2}$") +TS_RE = re.compile(r"^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?(Z|[+-]\d{2}:\d{2})$") +CVE_RE = re.compile(r"^CVE-[0-9]{4}-[0-9]{4,}$") +EMAIL_RE = re.compile(r"[A-Za-z0-9._%+-]+@([A-Za-z0-9-]+(?:\.[A-Za-z0-9-]+)+)") +# Addresses a published report may name: the system's own domain and FedRAMP's. +EMAIL_DOMAINS = ("samaydlette.com", "fedramp.gov", "gsa.gov") + +BASES = ("IEC-CSO-EFR", "VER-TFR-IRI", "VER-TFR-NRI") +VULN_RULES = ("VER-TFR-IRI", "VER-TFR-NRI") +REPORT_TYPES = ("Initial", "Ongoing", "Final") +EFFECTS = ("minimal", "narrow", "disruptive", "debilitating") +AGENCY_SCOPES = ("single", "multiple") +# Delivery the pipeline performs. Only publication is built; sending to FedRAMP +# or an agency is the operator's decision and is not implemented. +NOTIFICATION_MODES = ("published-only",) + +TOP_KEYS = {"$comment", "schema", "policy", "incidents"} +POLICY_KEYS = {"federal_incident_coordinator", "notification", "notification_text", "adopted_vulnerability_rules", + "federal_customer_data", "decided_by", "decided_on", "review_by"} +INCIDENT_KEYS = {"id", "title", "exercise", "started_at", "detected_at", "detection_source", "evaluation", + "findings", "estimates", "reports", "resolved_at", "recovery_complete_at"} +EVALUATION_KEYS = {"evaluated_at", "reportable", "basis", "reason", "federal_customer_data_considered"} +ESTIMATE_KEYS = {"estimated_at", "rating", "customer_effect", "agencies", "reason"} +REPORT_KEYS = {"type", "at", "set"} +# What a report can set, by the field it fills in the FedRAMP incident report. +TEXT_FIELDS = { + "description": "incidentDescription", + "functional_impact": "functionalImpact", + "recovery_plan": "recoveryPlan", + "observed_activity": "observedActivity", + "root_cause": "rootCause", + "response_and_recovery_activities": "responseAndRecoveryActivities", +} +LIST_FIELDS = { + "affected_agencies": "affectedAgencies", + "indicators_of_compromise": "indicatorsOfCompromise", + "related_cves": "relatedCveIds", +} +SET_KEYS = set(TEXT_FIELDS) | set(LIST_FIELDS) | {"milestones"} +MILESTONE_KEYS = {"at", "description"} + + +def _fail(msg): + raise SystemExit(f"::error::incident register: {msg} (fail-closed)") + + +def parse_ts(value, where): + """An aware datetime from an ISO 8601 timestamp with an offset, or fail.""" + if not isinstance(value, str) or not TS_RE.match(value): + _fail(f"{where} must be an ISO 8601 timestamp with a UTC offset, got {value!r}") + try: + return datetime.fromisoformat(value.replace("Z", "+00:00")) + except ValueError: + _fail(f"{where} is not a valid timestamp: {value!r}") + + +def _text(value, where): + if not isinstance(value, str) or not value.strip(): + _fail(f"{where} must be a non-empty string") + return value + + +def _strings(value, where, pattern=None): + if not isinstance(value, list) or not all(isinstance(x, str) and x.strip() for x in value): + _fail(f"{where} must be a list of non-empty strings") + if pattern is not None: + for x in value: + if not pattern.match(x): + _fail(f"{where}: {x!r} does not match {pattern.pattern}") + if len(set(value)) != len(value): + _fail(f"{where} lists an entry twice") + return value + + +def _published_text_ok(doc, where): + """Everything in the register is published: no AWS account ID, and no email + address outside the system's domain and FedRAMP's.""" + text = json.dumps(doc) + if _redact.find(text): + _fail(f"{where} contains an AWS account ID; the register is published") + for m in EMAIL_RE.finditer(text): + if not m.group(1).lower().endswith(EMAIL_DOMAINS): + _fail(f"{where} names an email address outside {', '.join(EMAIL_DOMAINS)}; the register is published") + + +def _validate_policy(p, where): + if not isinstance(p, dict) or set(p) - POLICY_KEYS or POLICY_KEYS - set(p): + _fail(f"{where}.policy must have exactly {sorted(POLICY_KEYS)}") + for k in ("federal_incident_coordinator", "notification_text", "decided_by"): + _text(p[k], f"{where}.policy.{k}") + for k in ("decided_on", "review_by"): + if not isinstance(p[k], str) or not DATE_RE.match(p[k]): + _fail(f"{where}.policy.{k} must be an ISO date") + if p["notification"] not in NOTIFICATION_MODES: + _fail(f"{where}.policy.notification {p['notification']!r} is not one of {list(NOTIFICATION_MODES)}; " + f"no other delivery is built") + adopted = _strings(p["adopted_vulnerability_rules"], f"{where}.policy.adopted_vulnerability_rules") + if set(adopted) - set(VULN_RULES): + _fail(f"{where}.policy.adopted_vulnerability_rules may name only {list(VULN_RULES)}") + _text(p["federal_customer_data"], f"{where}.policy.federal_customer_data") + + +def _validate_estimate(e, where, rubric, floor): + if not isinstance(e, dict) or set(e) != ESTIMATE_KEYS: + _fail(f"{where} must have exactly {sorted(ESTIMATE_KEYS)}") + at = parse_ts(e["estimated_at"], f"{where}.estimated_at") + if at < floor: + _fail(f"{where}.estimated_at is before the incident was detected") + if e["customer_effect"] not in EFFECTS or e["agencies"] not in AGENCY_SCOPES: + _fail(f"{where}: customer_effect must be one of {list(EFFECTS)} and agencies one of {list(AGENCY_SCOPES)}") + want = rubric[(e["customer_effect"], e["agencies"])] + if e["rating"] != want or isinstance(e["rating"], bool): + _fail(f"{where}: a likely {e['customer_effect']} effect on {e['agencies']} agenc" + f"{'y' if e['agencies'] == 'single' else 'ies'} is N{want} under IEC-CSO-EFI, not {e['rating']!r}") + _text(e["reason"], f"{where}.reason") + return at + + +def _validate_set(s, where): + if not isinstance(s, dict) or not s or set(s) - SET_KEYS: + _fail(f"{where}.set must be a non-empty object with only {sorted(SET_KEYS)}") + for k in TEXT_FIELDS: + if k in s: + _text(s[k], f"{where}.set.{k}") + for k in LIST_FIELDS: + if k in s: + _strings(s[k], f"{where}.set.{k}", CVE_RE if k == "related_cves" else None) + milestones = s.get("milestones", []) + if not isinstance(milestones, list): + _fail(f"{where}.set.milestones must be a list") + for i, m in enumerate(milestones): + if not isinstance(m, dict) or set(m) != MILESTONE_KEYS: + _fail(f"{where}.set.milestones[{i}] must have exactly {sorted(MILESTONE_KEYS)}") + parse_ts(m["at"], f"{where}.set.milestones[{i}].at") + _text(m["description"], f"{where}.set.milestones[{i}].description") + + +def _validate_incident(inc, where, policy, rubric, now): + rid = inc.get("id") if isinstance(inc, dict) else None + if not isinstance(rid, str) or not ID_RE.match(rid): + _fail(f"{where}: incident id {rid!r} is not INC-YYYY-NNN") + where = rid + required = {"id", "title", "exercise", "started_at", "detected_at", "detection_source", "evaluation", + "estimates", "reports"} + if set(inc) - INCIDENT_KEYS or required - set(inc): + _fail(f"{where}: unknown field(s) {sorted(set(inc) - INCIDENT_KEYS)}, missing {sorted(required - set(inc))}") + _text(inc["title"], f"{where}.title") + _text(inc["detection_source"], f"{where}.detection_source") + if not isinstance(inc["exercise"], bool): + _fail(f"{where}.exercise must be true or false") + started = parse_ts(inc["started_at"], f"{where}.started_at") + detected = parse_ts(inc["detected_at"], f"{where}.detected_at") + if detected < started: + _fail(f"{where}: detected before it started") + + ev = inc["evaluation"] + if not isinstance(ev, dict) or set(ev) != EVALUATION_KEYS: + _fail(f"{where}.evaluation must have exactly {sorted(EVALUATION_KEYS)} (IEC-CSO-EFR: when, the " + f"determination, its basis and reason, and the federal customer data considered)") + evaluated = parse_ts(ev["evaluated_at"], f"{where}.evaluation.evaluated_at") + if evaluated < detected: + _fail(f"{where}: evaluated before it was detected") + if not isinstance(ev["reportable"], bool): + _fail(f"{where}.evaluation.reportable must be true or false") + _text(ev["reason"], f"{where}.evaluation.reason") + _text(ev["federal_customer_data_considered"], f"{where}.evaluation.federal_customer_data_considered") + if ev["basis"] not in BASES: + _fail(f"{where}.evaluation.basis must be one of {list(BASES)}") + findings = _strings(inc.get("findings", []), f"{where}.findings") + if ev["basis"] in VULN_RULES: + if ev["basis"] not in policy["adopted_vulnerability_rules"]: + _fail(f"{where}: basis {ev['basis']} is not an adopted rule in policy.adopted_vulnerability_rules") + if not ev["reportable"]: + _fail(f"{where}: a vulnerability treated as a FedRAMP Reportable Incident under {ev['basis']} is reportable") + if not findings: + _fail(f"{where}: basis {ev['basis']} names no finding") + + if not isinstance(inc["estimates"], list) or not isinstance(inc["reports"], list): + _fail(f"{where}: estimates and reports must be lists") + if not ev["reportable"] and (inc["estimates"] or inc["reports"]): + _fail(f"{where}: not a FedRAMP Reportable Incident, so it carries no rating or report") + last = detected + for i, e in enumerate(inc["estimates"]): + at = _validate_estimate(e, f"{where}.estimates[{i}]", rubric, detected) + if at < last: + _fail(f"{where}.estimates are not in time order") + last = at + + resolved = parse_ts(inc["resolved_at"], f"{where}.resolved_at") if "resolved_at" in inc else None + recovered = (parse_ts(inc["recovery_complete_at"], f"{where}.recovery_complete_at") + if "recovery_complete_at" in inc else None) + if recovered and not resolved: + _fail(f"{where}: recovery is complete but the incident is not resolved") + if resolved and resolved < detected or recovered and resolved and recovered < resolved: + _fail(f"{where}: resolved_at / recovery_complete_at are out of order") + + reports = inc["reports"] + prev = evaluated + for i, r in enumerate(reports): + w = f"{where}.reports[{i}]" + if not isinstance(r, dict) or set(r) - REPORT_KEYS or {"type", "at"} - set(r): + _fail(f"{w} must have type, at and optionally set") + if r["type"] not in REPORT_TYPES: + _fail(f"{w}.type must be one of {list(REPORT_TYPES)}") + want = "Initial" if i == 0 else None + if want and r["type"] != want: + _fail(f"{where}: the first report is the Initial Incident Report (IEC-CSO-IIR)") + if i > 0 and r["type"] == "Initial": + _fail(f"{where}: only the first report is Initial") + if r["type"] == "Final" and i != len(reports) - 1: + _fail(f"{where}: nothing follows the Final Incident Report") + at = parse_ts(r["at"], f"{w}.at") + if at < prev: + _fail(f"{w}.at is before the evaluation or the previous report") + prev = at + if "set" in r: + _validate_set(r["set"], w) + elif r["type"] == "Initial": + _fail(f"{w}: the Initial report sets at least the description") + if reports and "description" not in reports[0].get("set", {}): + _fail(f"{where}: the Initial report must describe the incident (IEC-CSO-IIR)") + if reports and reports[-1]["type"] == "Final": + if not recovered: + _fail(f"{where}: a Final Incident Report needs resolved_at and recovery_complete_at (IEC-CSO-FIR)") + if parse_ts(reports[-1]["at"], "") < recovered: + _fail(f"{where}: the Final report is dated before recovery completed") + + if now is not None: + stamps = [started, detected, evaluated, resolved, recovered] + stamps += [parse_ts(e["estimated_at"], "") for e in inc["estimates"]] + stamps += [parse_ts(r["at"], "") for r in reports] + if any(t and t > now for t in stamps): + _fail(f"{where} records a time after now; a report cannot be issued in the future") + + +def validate(doc, where="data/incidents.json", now=None, rules_dir=_rules.RULES_DIR): + """Structural and rule checks, enforced at build time without a jsonschema + dependency. `now` (aware datetime), when given, also refuses future times.""" + if not isinstance(doc, dict) or doc.get("schema") != "incidents/1": + _fail(f"{where} is not an incidents/1 document") + if set(doc) - TOP_KEYS or {"schema", "policy", "incidents"} - set(doc): + _fail(f"{where}: top-level fields must be {sorted(TOP_KEYS)}") + _validate_policy(doc["policy"], where) + if not isinstance(doc["incidents"], list): + _fail(f"{where}: incidents must be a list") + rubric = _rules.incident_rating_rubric(rules_dir) + seen = set() + for i, inc in enumerate(doc["incidents"]): + _validate_incident(inc, f"{where} incidents[{i}]", doc["policy"], rubric, now) + if inc["id"] in seen: + _fail(f"{where}: duplicate id {inc['id']}") + seen.add(inc["id"]) + _published_text_ok(doc, where) + return doc + + +def load(path=None, now=None, rules_dir=_rules.RULES_DIR): + p = Path(path) if path else DEFAULT_PATH + if not p.is_file(): + _fail(f"{p} not found") + try: + doc = json.loads(p.read_text()) + except (json.JSONDecodeError, UnicodeDecodeError) as exc: + _fail(f"{p} is not valid JSON: {exc}") + return validate(doc, str(p), now=now, rules_dir=rules_dir) + + +# ---- ratings and clocks ------------------------------------------------------- + +def add_clock(start, unit, n): + """`start` plus n hours, or n business days. A business day here is Monday to + Friday in UTC; federal holidays are counted as business days, which can only + make a deadline earlier, never later.""" + if unit == "hours": + return start + timedelta(hours=n) + if unit == "bizdays": + t, left = start.astimezone(timezone.utc), n + while left: + t += timedelta(days=1) + if t.weekday() < 5: + left -= 1 + return t + _fail(f"unknown clock unit {unit!r}") + + +def rating_at(inc, t, default): + """(N-rating, basis) in force at time t: the latest Incident Rating estimate + made by then (IEC-CSO-EFI), else the default (IEC-CSO-DPR).""" + best = None + for e in inc["estimates"]: + if parse_ts(e["estimated_at"], "") <= t: + best = e + if best is None: + return default, "default (IEC-CSO-DPR)" + return best["rating"], f"estimated (IEC-CSO-EFI) at {best['estimated_at']}" + + +def rating_history(inc, default, until=None): + """[(when, rating, basis)] from evaluation through `until` (inclusive).""" + out = [(inc["evaluation"]["evaluated_at"], default, "default (IEC-CSO-DPR)")] + for e in inc["estimates"]: + if until is None or parse_ts(e["estimated_at"], "") <= until: + out.append((e["estimated_at"], e["rating"], f"estimated (IEC-CSO-EFI): {e['reason']}")) + return out + + +def _obligation(kind, due, report, index, now): + met_at = parse_ts(report["at"], "") if report else None + return {"report": kind, "due_at": due.isoformat(), "report_index": index, + "issued_at": report["at"] if report else None, + "on_time": (met_at <= due) if report else None, + "overdue": (report is None and now > due)} + + +def obligations(inc, timeframes, default, now): + """Every report the Class C clocks call for, in order, and whether each was + issued by its deadline. The last entry with report_index None is the one + still due. Not reportable: no obligations.""" + if not inc["evaluation"]["reportable"]: + return [] + reports = inc["reports"] + resolved = parse_ts(inc["resolved_at"], "") if "resolved_at" in inc else None + recovered = parse_ts(inc["recovery_complete_at"], "") if "recovery_complete_at" in inc else None + evaluated = parse_ts(inc["evaluation"]["evaluated_at"], "") + + def due(kind, start): + return add_clock(start, *timeframes[kind][rating_at(inc, start, default)[0]]) + + out = [_obligation("Initial", due("iir", evaluated), reports[0] if reports else None, 0 if reports else None, now)] + if not reports: + return out + i, prev = 1, parse_ts(reports[0]["at"], "") + while True: + oir_due = due("oir", prev) + if resolved is not None and resolved <= oir_due: + # Resolved before the next Ongoing report fell due: any further + # Ongoing reports are voluntary, and the Final report's clock starts + # when recovery completes (IEC-CSO-FIR). + while i < len(reports) and reports[i]["type"] == "Ongoing": + i += 1 + if recovered is not None: + final = reports[i] if i < len(reports) else None + out.append(_obligation("Final", due("fir", recovered), final, i if final else None, now)) + return out + nxt = reports[i] if i < len(reports) and reports[i]["type"] == "Ongoing" else None + out.append(_obligation("Ongoing", oir_due, nxt, i if nxt else None, now)) + if nxt is None: + return out + prev, i = parse_ts(nxt["at"], ""), i + 1 + + +def status(inc): + if not inc["evaluation"]["reportable"]: + return "not-reportable" + if inc["reports"] and inc["reports"][-1]["type"] == "Final": + return "closed" + if "resolved_at" in inc: + return "resolved" + return "open" + + +def open_findings(reg, include_exercises=False): + """{finding or CVE: incident id} named by incidents that are not yet resolved.""" + out = {} + for inc in reg["incidents"]: + if inc["exercise"] and not include_exercises: + continue + if status(inc) == "open": + for f in inc.get("findings", []): + out[f] = inc["id"] + return out diff --git a/scripts/_nonmachine.py b/scripts/_nonmachine.py new file mode 100644 index 00000000..c44e2b9a --- /dev/null +++ b/scripts/_nonmachine.py @@ -0,0 +1,314 @@ +"""Non-machine information resources and their verification (VDR-TFR-NMV). + +Providers MUST verify and validate the status of non-machine-based information +resources at least once every 3 months. data/non-machine-resources.json lists +them (policies, procedures, plans, the operator role, records and registers). +Nobody verifies them by hand: every resource gets machine checks, run on every +deploy (enforced) and every night (published), so the verification is never +more than a day old: + + exists the file is there; + paths every repository path it cites (a relative Markdown link, or a + `scripts/...`, `data/...`, `docs/...`, `infrastructure/...`, + `tests/...`, `website/...` or `.github/...` path in backticks) + resolves, relative to the document or to the repository root; + decisions every DEC ID it cites is in the decision register; + retired it names no retired mechanism (RETIRED: the POA&M, the SSP, the + CDS overview, Basic Auth, Duo-enforced MFA, "no SCN-Type label is + required", long-lived deploy keys), except on a line that says the + thing is retired, replaced or no longer used; + counts a stated count tagged `<!-- nmv-count NAME=N -->` equals what the + code says (COUNTERS), and the tagged line states N; + register a register is loaded by its own validator (the decision register) + or parsed as JSON; + manual work no sentence commits a person to a recurring review, reading, + tabletop, acknowledgement or reconciliation (MANUAL_WORK): those + are automated (scripts/_scheduled_review.py and its kin). A + sentence that cites DEC-195 (the three recurring human acts that + remain) may describe one, and a section headed as history may + record what used to be done. + +The status (/.well-known/vdr-non-machine-vv.json) is the quarterly V&V record: +when every check passes, verifiedAt is the time of the run; when any fails, +verifiedAt is the epoch, so the published freshness window is red at once. +Fails closed: a missing or malformed register is an error, never an empty list. +""" + +import json +import re +from datetime import datetime, timedelta, timezone +from pathlib import Path + +REPO = Path(__file__).resolve().parent.parent +DEFAULT_PATH = REPO / "data" / "non-machine-resources.json" +TOP_KEYS = {"$schema", "$comment", "schema", "max_age_days", "resources"} +ENTRY_KEYS = {"id", "path", "kind", "title", "owner", "verifies"} +KINDS = {"policy", "procedure", "plan", "role", "record", "register"} +ID_RE = re.compile(r"^NMR-[A-Z0-9-]+$") +# The rule's "at least once every 3 months": the longest three calendar months. +RULE_MAX_DAYS = 92 +EPOCH = "1970-01-01T00:00:00+00:00" +# Directories whose every Markdown file is a non-machine resource that must be listed. +MUST_LIST: tuple[tuple[str, set[str]], ...] = (("docs/policies", {"README.md"}), ("docs/runbooks", set()), + ("docs/procedures", set())) + +# Retired mechanisms. A line that says the thing is retired or replaced may name it. +RETIRED = { + "POA&M": re.compile(r"\bPOA&(?:amp;)?M\b|\bPOAM-\d+|\bplan of action and milestones\b", re.I), + "SSP": re.compile(r"\bSSP\b|\bSystem Security Plan\b"), + "CDS overview": re.compile(r"\bCDS overview\b", re.I), + "Basic Auth": re.compile(r"\bBasic Auth(?:entication)?\b", re.I), + "Duo-enforced MFA": re.compile(r"\b(?:via|through|by|with) Duo\b(?! Mobile)|\bDuo (?:root )?MFA\b", re.I), + "no SCN-Type label": re.compile(r"no SCN-Type label is required", re.I), + "long-lived deploy keys": re.compile(r"(?<!no )(?<!never )(?<!without )long-lived (?:deploy|deployment|AWS|access) " + r"(?:access )?keys?", re.I), +} +RETIRED_OK = re.compile(r"\b(?:retired|replaced|replaces|formerly|superseded|no longer|backfilled|" + r"instead of|was removed|removed in)\b", re.I) +# Manual work (DEC-195): a person, a review-like act and a recurring cadence in one +# sentence, or a "Review cadence:" line. Everything recurring is a mechanism now. +MANUAL_ACTOR = re.compile(r"\b(?:operator|owner|Sam|the team|staff|personnel|a person|a human|humans?|manually|" + r"by hand|in person)\b", re.I) +MANUAL_ACT = re.compile(r"\b(?:review(?:s|ed|ing)?|reads?|re-?reads?|inspect\w*|walk\w*|tabletops?|re-?acknowledg\w*|" + r"acknowledg\w*|reconcil\w*|audits?|checks?|confirm\w*|examin\w*|look\w* (?:at|over))\b", + re.I) +MANUAL_CADENCE = re.compile(r"\b(?:daily|weekly|monthly|quarterly|annual(?:ly)?|yearly|biannual\w*|semi-?annual\w*|" + r"every (?:day|week|month|quarter|year|\d+ (?:days|weeks|months))|" + r"once an? (?:week|month|quarter|year)|each (?:week|month|quarter|year))\b", re.I) +REVIEW_CADENCE_LINE = re.compile(r"\breview cadence\b", re.I) +# A sentence that names the mechanism doing the recurring act describes automation. +MECHANISM = re.compile(r"`?(?:scripts|tools|infrastructure)/[\w./-]+|\.github/workflows/|\b[\w-]+\.ya?ml\b|" + r"\b(?:automat\w*|generated|simulated|machine|nightly|the deploy|every deploy|emitter|Lambda|the script|" + r"the pipeline|workflow|the gate)\b", re.I) +MANUAL_OK = re.compile(r"\bDEC-195\b") +# Names of published, automated products, not acts: "the Quarterly Review" (CCM-QTR-MTG, held by +# scripts/hold-quarterly-review.py), "the Ongoing Certification Report" and "the Annual Security +# Review" (scripts/hold-security-review.py). Case-sensitive: "the annual security review" is not one. +# Code spans and file names are not prose ("quarterly-reviews.json" commits nobody). +CODE_OR_FILE = re.compile(r"`[^`]*`|[\w./<>-]+\.(?:json|ics|md|py|ya?ml|csv|bundle|html|js|tf)\b") +PROPER_NAMES = re.compile(r"\bQuarterly Reviews?\b|\bOngoing Certification Reports?\b|\bAnnual Security Reviews?\b") +HISTORY_HEADING = re.compile(r"^(#+)\s.*\b(?:history|historical|changelog|change log|revision log)\b", re.I) +DEC_RE = re.compile(r"\bDEC-\d{3}\b") +LINK_RE = re.compile(r"\]\(([^)\s]+)\)") +CODE_PATH_RE = re.compile(r"`((?:scripts|data|docs|infrastructure|tests|\.github|website)/[^`\s]+)`") +COUNT_TAG_RE = re.compile(r"<!--\s*nmv-count\s+([a-z0-9-]+)=(\d+)\s*-->") +NUMBER_WORDS = ["zero", "one", "two", "three", "four", "five", "six", "seven", "eight", "nine", "ten", "eleven", + "twelve", "thirteen", "fourteen", "fifteen", "sixteen", "seventeen", "eighteen", "nineteen", "twenty"] + + +def _watchdog_alarms(repo): + tf = (repo / "infrastructure" / "watchdog.tf").read_text(encoding="utf-8") + block = tf[tf.index("watchdog_alarms = {"):] + depth = 0 + for i, ch in enumerate(block): + if ch == "{": + depth += 1 + elif ch == "}": + depth -= 1 + if depth == 0: + block = block[:i] + break + return len(re.findall(r'^\s{4}"[a-z0-9-]+"\s*=\s*\{', block, re.M)) + + +def _policies(repo): + return len(list((repo / "docs" / "policies").glob("*-policy.md"))) + + +COUNTERS = {"watchdog-alarms": _watchdog_alarms, "family-policies": _policies} + + +def _fail(msg): + raise SystemExit(f"::error::non-machine resources: {msg} (fail-closed)") + + +def validate(doc, where="data/non-machine-resources.json"): + if not isinstance(doc, dict) or doc.get("schema") != "non-machine-resources/2": + _fail(f"{where} is not a non-machine-resources/2 document") + if set(doc) - TOP_KEYS: + _fail(f"{where}: unknown field(s) {sorted(set(doc) - TOP_KEYS)}") + m = doc.get("max_age_days") + if not isinstance(m, int) or isinstance(m, bool) or not 1 <= m <= RULE_MAX_DAYS: + _fail(f"{where}: max_age_days must be an integer from 1 to {RULE_MAX_DAYS}") + res = doc.get("resources") + if not isinstance(res, list) or not res: + _fail(f"{where}: resources must be a non-empty list") + seen = set() + for e in res: + rid = e.get("id") if isinstance(e, dict) else None + if not isinstance(rid, str) or not ID_RE.match(rid) or rid in seen: + _fail(f"{where}: entry id {rid!r} is not a unique NMR-...") + seen.add(rid) + if set(e) != ENTRY_KEYS: + _fail(f"{rid}: fields must be exactly {sorted(ENTRY_KEYS)}") + if e["kind"] not in KINDS: + _fail(f"{rid}: kind {e['kind']!r} is not one of {sorted(KINDS)}") + for k in ("path", "title", "owner", "verifies"): + if not isinstance(e[k], str) or not e[k].strip(): + _fail(f"{rid}: {k} must be a non-empty string") + return doc + + +def load(path=None): + p = Path(path) if path else DEFAULT_PATH + if not p.is_file(): + _fail(f"{p} not found") + try: + doc = json.loads(p.read_text(encoding="utf-8")) + except (json.JSONDecodeError, UnicodeDecodeError) as exc: + _fail(f"{p} is not valid JSON: {exc.__class__.__name__}") + return validate(doc, str(p)) + + +def _resolves(ref, doc_path, repo): + ref = ref.split("#", 1)[0].rstrip("/.,;:") + if not ref or re.search(r"[<>*{}$]|YYYY|NNN", ref): + return True # a pattern or placeholder, not a path + return any((base / ref).exists() for base in (doc_path.parent, repo)) + + +def _sentences(text): + """(first line number, sentence) for prose outside sections headed as history.""" + out, buf, start, skip = [], [], None, None + for n, line in enumerate(text.splitlines(), 1): + h = re.match(r"^(#+)\s", line) + if h: + level = len(h.group(1)) + if skip is not None and level <= skip: + skip = None + if skip is None and HISTORY_HEADING.match(line): + skip = level + if skip is not None: + continue + for part in re.split(r"(?<=[.!?])\s+|^\s*$|^\s*[-*|]\s|^#+\s", line): + if part is None: + continue + if start is None: + start = n + buf.append(part) + joined = " ".join(buf).strip() + if re.search(r"[.!?]$", joined) or not line.strip() or line.lstrip().startswith(("-", "*", "|", "#")): + if joined: + out.append((start, joined)) + buf, start = [], None + if not line.strip(): + if buf and " ".join(buf).strip(): + out.append((start, " ".join(buf).strip())) + buf, start = [], None + if buf and " ".join(buf).strip(): + out.append((start, " ".join(buf).strip())) + return out + + +def manual_work(text): + """[(line, sentence)] for every sentence that commits a person to recurring + manual work (MANUAL_WORK), outside history sections and DEC-195's acts.""" + found = [] + for n, s in _sentences(text): + if MANUAL_OK.search(s): + continue + prose = PROPER_NAMES.sub("", CODE_OR_FILE.sub("", s)) + if not (MANUAL_ACT.search(prose) or REVIEW_CADENCE_LINE.search(prose)) or not MANUAL_CADENCE.search(prose): + continue + if MANUAL_ACTOR.search(prose) or not MECHANISM.search(s) or REVIEW_CADENCE_LINE.search(prose): + found.append((n, s)) + return found + + +def text_problems(rid, text, doc_path, repo, decision_ids): + """Every machine-check failure for one Markdown resource.""" + out = [f"{rid}: line {n} commits a person to recurring manual work: {s[:90]!r}" for n, s in manual_work(text)] + for n, line in enumerate(text.splitlines(), 1): + refs = [r for r in LINK_RE.findall(line) if not re.match(r"[a-z]+:|#|/", r)] + refs += CODE_PATH_RE.findall(line) + for ref in refs: + if not _resolves(ref, doc_path, repo): + out.append(f"{rid}: line {n} cites {ref}, which does not exist") + for dec in DEC_RE.findall(line): + if dec not in decision_ids: + out.append(f"{rid}: line {n} cites {dec}, which is not in the decision register") + if not RETIRED_OK.search(line): + for term, rx in RETIRED.items(): + if rx.search(line): + out.append(f"{rid}: line {n} names a retired mechanism ({term})") + for name, stated in COUNT_TAG_RE.findall(line): + fn = COUNTERS.get(name) + if fn is None: + out.append(f"{rid}: line {n} tags an unknown count {name!r}") + continue + actual, n_stated = fn(repo), int(stated) + words = {stated} | ({NUMBER_WORDS[n_stated]} if n_stated < len(NUMBER_WORDS) else set()) + visible = COUNT_TAG_RE.sub("", line).lower() + if actual != n_stated: + out.append(f"{rid}: line {n} states {name} = {n_stated}; the code has {actual}") + elif not any(re.search(rf"\b{w}\b", visible) for w in words): + out.append(f"{rid}: line {n} tags {name} = {n_stated} but does not state it") + return out + + +def register_problems(rid, path): + """A register is checked by its own validator, or parsed as JSON.""" + try: + if path.name == "decisions.json": + import _decisions # noqa: PLC0415 (only the decision register needs it) + _decisions.load(path) + else: + json.loads(path.read_text(encoding="utf-8")) + except SystemExit as exc: + return [f"{rid}: {path.name} does not validate ({str(exc)[:160]})"] + except (json.JSONDecodeError, UnicodeDecodeError) as exc: + return [f"{rid}: {path.name} is not valid JSON ({type(exc).__name__})"] + return [] + + +def problems(doc, decisions, repo=REPO): + """Every reason a resource does not pass its machine checks, as strings; + empty when all pass. `decisions` is a loaded decisions/1 register.""" + ids = {r["id"] for r in decisions["decisions"]} + out = [] + listed = {e["path"] for e in doc["resources"]} + for e in doc["resources"]: + rid, p = e["id"], repo / e["path"] + if not p.is_file(): + out.append(f"{rid}: {e['path']} does not exist") + continue + if e["kind"] == "register": + out += register_problems(rid, p) + else: + out += text_problems(rid, p.read_text(encoding="utf-8"), p, repo, ids) + for folder, skip in MUST_LIST: + for p in sorted((repo / folder).glob("*.md")): + rel = f"{folder}/{p.name}" + if p.name not in skip and rel not in listed: + out.append(f"{rel} has no entry in the register") + return list(dict.fromkeys(out)) + + +def status(doc, decisions, now=None, repo=REPO): + """The published status (/.well-known/vdr-non-machine-vv.json), the + quarterly V&V record: verifiedAt is this run when every check passes, else + the epoch.""" + now = now or datetime.now(timezone.utc) + probs = problems(doc, decisions, repo) + ok = not probs + verified = now.isoformat() if ok else EPOCH + return { + "schema": "non-machine-vv/2", + "rule": "VDR-TFR-NMV", + "generatedAt": now.isoformat(), + "verifiedAt": verified, + "nextDueBy": (now.date() + timedelta(days=doc["max_age_days"])).isoformat() if ok else now.date().isoformat(), + "maxAgeDays": doc["max_age_days"], + "method": "Machine checks on every deploy and every night (scripts/_nonmachine.py): the file exists, every " + "path and DEC ID it cites resolves, it names no retired mechanism, every tagged count matches " + "the code, and a register validates. No person verifies anything by hand.", + "checks": ["exists", "paths", "decisions", "retired", "counts", "register"], + "status": "ok" if ok else "lapsed", + "problems": probs, + "source": "data/non-machine-resources.json", + "resources": [{"id": e["id"], "kind": e["kind"], "title": e["title"], "path": e["path"], + "owner": e["owner"], "verifies": e["verifies"], + "lastVerified": verified[:10] if ok else None, + "result": "fail" if any(p.startswith(e["id"] + ":") for p in probs) else "pass"} + for e in doc["resources"]], + } diff --git a/scripts/_offering.py b/scripts/_offering.py new file mode 100644 index 00000000..270e6c9f --- /dev/null +++ b/scripts/_offering.py @@ -0,0 +1,113 @@ +"""The offering's declared identity (data/cds/offering.json), shared by every report. + +CDS-CSO-FID: every FedRAMP report this repository publishes carries the same +FedRAMP ID, read here and nowhere else, under providerExtensions.fedRampId +(FedRAMP's report schemas other than the CPO have no field for it; the CPO +carries it in serviceIdentification.fedRampPackageId). No ID has been +assigned, so the value is FedRAMP's own fallback, the provider name and +acronym, marked as not real; scripts/check-fedramp-id.py fails the deploy if a +report it publishes carries none or another. + +Also the semver content-hash version the CPO and OCR share with the SDR. +""" + +import hashlib +import json +import re +from pathlib import Path + +REPO = Path(__file__).resolve().parent.parent +OFFERING_PATH = REPO / "data" / "cds" / "offering.json" +SEMVER = re.compile(r"^(\d+)\.(\d+)\.(\d+)$") +NOT_REAL = "NOT-A-REAL" + + +def _fail(msg): + raise SystemExit(f"::error::offering: {msg} (fail-closed)") + + +def load(path=OFFERING_PATH): + try: + off = json.loads(Path(path).read_text()) + except (OSError, ValueError) as exc: + _fail(f"cannot read {path}: {exc}") + for k in ("provider_name", "service_acronym", "fedramp_id"): + if not isinstance(off.get(k), str) or not off[k].strip(): + _fail(f"{k} is missing") + fid = off["fedramp_id"] + # Until FedRAMP assigns one, FedRAMP's fallback: the provider's name and acronym. + if off["provider_name"] not in fid or off["service_acronym"] not in fid: + _fail("fedramp_id must carry the provider name and acronym (FedRAMP's fallback) until one is assigned") + if NOT_REAL in fid and not off.get("fedramp_id_simulated"): + _fail("a placeholder FedRAMP ID must say why (fedramp_id_simulated)") + return off + + +def fedramp_id(path=OFFERING_PATH): + return load(path)["fedramp_id"] + + +# The certification this offering seeks, and the fact that it does not hold it. +# The one place the CPO, the SDR, the simulated certification report and its +# index read it from, so the published wording cannot drift: this proof of +# concept is not certified, and every published statement of the program says so. +CERTIFICATION_PROGRAM = "FedRAMP 20x, Program path, Class C" +CERTIFICATION_STATUS = "not certified (proof of concept)" + + +def certification(): + """providerExtensions.certification, as the CPO and the SDR publish it.""" + return {"program": CERTIFICATION_PROGRAM, "status": CERTIFICATION_STATUS} + + +FEDRAMP_SCHEMA_BASES = ("https://fedramp.gov/schemas/", "https://www.fedramp.gov/schemas/") + + +def stamp_fedramp_id(doc, path=OFFERING_PATH): + """`doc` carrying the offering's FedRAMP ID (CDS-CSO-FID): under + providerExtensions.fedRampId on a report in a FedRAMP schema, otherwise as + a top-level `fedRampId` placed first (after any $schema). Returns the + document to write.""" + fid = fedramp_id(path) + if str(doc.get("$schema", "")).startswith(FEDRAMP_SCHEMA_BASES): + doc.setdefault("providerExtensions", {})["fedRampId"] = fid + return doc + rest = {k: v for k, v in doc.items() if k != "fedRampId"} + if "$schema" in rest: # keep $schema first + return {"$schema": rest.pop("$schema"), "fedRampId": fid, **rest} + return {"fedRampId": fid, **rest} + + +# --- versioning (CPO-CSO-MTD, and the OCR alike) -------------------------------------- + +def content_hash(doc, volatile=("metadata",), volatile_ext=("contentSha256",)): + """sha256 of what the version tracks: the document without its version, + timestamp and update source, the hash itself, and any providerExtensions field named volatile.""" + body = {k: v for k, v in doc.items() if k not in (*volatile, "providerExtensions")} + body["metadata"] = {k: v for k, v in (doc.get("metadata") or {}).items() + if k not in ("version", "lastUpdated", "updateSource")} + pe = {k: v for k, v in (doc.get("providerExtensions") or {}).items() if k not in volatile_ext} + raw = json.dumps({"body": body, "pe": pe}, sort_keys=True, separators=(",", ":")).encode() + return hashlib.sha256(raw).hexdigest() + + +def next_version(prev, digest): + """Unchanged content keeps the previous version, changed content bumps the + patch, and a previous document without a semver starts at 1.0.0.""" + v = ((prev or {}).get("metadata") or {}).get("version", "") + m = SEMVER.match(v or "") + if not m: + return "1.0.0" + if ((prev or {}).get("providerExtensions") or {}).get("contentSha256") == digest: + return v + return f"{m.group(1)}.{m.group(2)}.{int(m.group(3)) + 1}" + + +def stamp_version(doc, prev, now, source, volatile_ext=("contentSha256",)): + """Set providerExtensions.contentSha256 and metadata {version, lastUpdated, updateSource}.""" + digest = content_hash(doc, volatile_ext=volatile_ext) + doc.setdefault("providerExtensions", {})["contentSha256"] = digest + doc["metadata"] = {"version": next_version(prev, digest), "lastUpdated": now.isoformat(), + "updateSource": source, **{k: v for k, v in (doc.get("metadata") or {}).items() + if k not in ("version", "lastUpdated", "updateSource")}} + return doc diff --git a/scripts/_quarterly_review.py b/scripts/_quarterly_review.py new file mode 100644 index 00000000..b23fee77 --- /dev/null +++ b/scripts/_quarterly_review.py @@ -0,0 +1,298 @@ +"""The Quarterly Review, automated and held with simulated attendees (CCM-QTR-*, CCM-OCR-AFS/FBM). + +The operator does not host meetings with FedRAMP or agencies (DEC-194), and no +person runs this process. What a real review needs is built here as code that +would work with real people, and it is exercised every quarter against a cast +of plainly simulated ones: + + roster who attends, checked against the attendee policy in code + (CCM-QTR-RTP): simulated agencies, the simulated FedRAMP and the + simulated assessor; any other party only with its relevance + recorded; nobody who is not marked simulated. + agenda the standing agenda (CCM-QTR-ACT), filled from the issued + Ongoing Certification Report it reviews. + feedback the asynchronous feedback intake (CCM-OCR-FBM): submissions + about an issued report, each validated and screened, answered + by rule. Simulated parties submit through it; nobody else is + invited to. The anonymized summary of the questions and answers + (CCM-OCR-AFS) goes into the next report (scripts/build-ocr.py + calls qa_summary(), the same function the review publishes). + transcript a scripted transcript that walks the agenda (CCM-QTR-RTR). The + full transcript is "supplied" to the attendees as a log entry + (its sha256); the published one has every agency line removed + (CCM-QTR-SRR), and everything passes the sensitivity screen + (CCM-QTR-NID). + +The feedback depends only on the issue date, so the review and the next report +always carry the same summary. scripts/hold-quarterly-review.py writes the +review on its date (package-maintenance.yml); scripts/check-quarterly-review.py +fails the deploy and the nightly when a review date has passed with no review +published. +""" + +import hashlib +import json +import sys +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _engagement # noqa: E402 +import _sensitivity # noqa: E402 + +SCHEMA = "quarterly-review/1" +INDEX_SCHEMA = "quarterly-reviews/1" +BASE = "https://samaydlette.com/.well-known/" +SIMULATED_MARK = "(simulated)" +ROLES = ("agency", "fedramp", "assessor") # who is invited by default (CCM-QTR-RTP) +HOST = {"seat": "Host", "org": "The operator, played by package-maintenance.yml (simulated)", "role": "host"} +ROSTER = [ + {"seat": "Authorizing Official", "org": "Department of Hypothetical Affairs (simulated)", "role": "agency"}, + {"seat": "Information System Security Officer", "org": "Bureau of Made-Up Statistics (simulated)", + "role": "agency"}, + {"seat": "Package reviewer", "org": "FedRAMP (simulated)", "role": "fedramp"}, + {"seat": "Lead assessor", "org": "Totally Real Assessment Services, LLC (simulated)", "role": "assessor"}, +] +ATTENDEE_POLICY = ("Simulated agencies, the simulated FedRAMP and the simulated assessor attend by default. Any other " + "party attends only with its specific relevance recorded on the roster (CCM-QTR-RTP). Everyone " + "on the roster is simulated: the operator invites no real party (DEC-194).") +AGENCY_LINE_REMOVED = "[Comment from a simulated agency attendee removed before publication (CCM-QTR-SRR).]" +INTAKE = ("Asynchronous feedback intake (CCM-OCR-FBM): a submission names the report's issue date and a question; " + "scripts/_quarterly_review.py validates and screens it, answers it by rule and adds it, anonymized, to the " + "next report. Each quarter simulated parties submit through it. No real party is invited to (DEC-194).") +# The feedback the simulated parties submit, rotated by quarter: (from role, question, answer). +FEEDBACK_POOL = [ + ("agency", "Is this system FedRAMP authorized?", + "No. It is not FedRAMP certified or authorized, it holds no federal data, and nobody has asked it to be. It is " + "a proof of concept that shows the evidence a 20x Class C system would produce."), + ("agency", "How do we get access to the certification package?", + "You already have it: everything is public, and the trust manifest lists every file with its signature. No " + "form, no request, no fax."), + ("fedramp", "Why is every attendee at this review simulated?", + "Because the operator does not engage FedRAMP or any agency about this system (DEC-194). The review runs anyway, " + "on its date, so the mechanism is shown working."), + ("assessor", "What happens if a Quarterly Review is missed?", + "The deploy and the evidence nightly both fail from the day after a review date with no review published."), + ("agency", "Will the accepted findings ever be revisited?", + "Each one is a decision record with a review date; a record past its date lapses and stops covering anything."), + ("assessor", "Can the assessor attend in person?", + "The assessor is a GitHub Actions workflow wearing a lanyard. It attends in YAML."), + ("agency", "Is there coffee?", + "Simulated coffee only. It is excellent, and its software bill of materials has no known vulnerabilities."), + ("fedramp", "How do we know the evidence shown here is current?", + "Every published artifact has a governed freshness window and a signature; the watchdog pages the operator when " + "one lapses."), +] +PER_QUARTER = 3 + + +def _fail(msg): + raise SystemExit(f"::error::Quarterly Review: {msg} (fail-closed)") + + +# --- the attendee policy (CCM-QTR-RTP) ------------------------------------------------ + +def check_roster(roster): + """The roster, if it meets the attendee policy; fails closed otherwise.""" + if not roster: + _fail("the roster is empty") + for a in roster: + org, role = str(a.get("org") or ""), a.get("role") + if not org.endswith(SIMULATED_MARK): + _fail(f"attendee {org!r} is not marked {SIMULATED_MARK}: no real party is invited (DEC-194)") + if role not in ROLES: + if role != "other" or not str(a.get("relevance") or "").strip(): + _fail(f"attendee {org!r} ({role}) is a third party with no specific relevance recorded") + return roster + + +# --- feedback intake (CCM-OCR-FBM) and the anonymized summary (CCM-OCR-AFS) ----------- + +def simulated_submissions(issue, quarter_index): + """What the simulated parties submit about the report issued on `issue`.""" + n = len(FEEDBACK_POOL) + picks = [FEEDBACK_POOL[(quarter_index * PER_QUARTER + i) % n] for i in range(PER_QUARTER)] + by_role = {r["role"]: r["org"] for r in ROSTER} + return [{"ocr": issue, "from": by_role[role], "question": q, "_answer": a} for role, q, a in picks] + + +def intake(submissions, issue): + """Validate, screen and answer each submission; refuses one about another + report, one from a party not marked simulated, or one that would publish an + identifier.""" + out = [] + for s in submissions: + if s.get("ocr") != issue: + _fail(f"a submission about {s.get('ocr')!r} arrived in the intake for {issue}") + if not str(s.get("from") or "").endswith(SIMULATED_MARK): + _fail("a submission from a party not marked simulated: no real feedback is solicited (DEC-194)") + q = str(s.get("question") or "").strip() + if not q: + _fail("a submission with no question") + out.append({"from": s["from"], "question": q, "answer": s["_answer"]}) + _sensitivity.require_clean(out, f"the feedback on the report issued {issue}") + return out + + +def qa_summary(issue, quarter_index): + """The anonymized, desensitized summary of the questions and answers on one + issued report: no party, name or agency. The review publishes it and the + next report carries it (CCM-OCR-AFS).""" + items = intake(simulated_submissions(issue, quarter_index), issue) + return {"ocr": issue, "received": len(items), "summarizedBy": "scripts/_quarterly_review.py (automated)", + "simulated": True, + "items": [{"question": i["question"], "answer": i["answer"]} for i in items]} + + +# --- agenda (CCM-QTR-ACT) and transcript (CCM-QTR-RTR) --------------------------------- + +def agenda(ocr): + """The standing agenda, filled from the issued report.""" + changes = len(ocr.get("certificationDataChanges") or []) + planned = len((ocr.get("plannedCertificationDataChanges") or {}).get("changes") or []) + incidents = len((ocr.get("reportableIncidents") or {}).get("incidents") or []) + period = ocr.get("reportPeriod") or {} + return [ + f"The report for {period.get('from')} to {period.get('to')}: {changes} change(s) to certification data, " + f"{len(ocr.get('transformativeChanges') or [])} transformative, {incidents} reportable incident(s).", + "Standing item (CCM-QTR-ACT): Key Security Indicator results and their trend, from the Security Decision " + "Record's metric summaries.", + f"Standing item (CCM-QTR-ACT): accepted vulnerabilities and their trend. {ocr.get('acceptedVulnerabilities')}", + f"Standing item (CCM-QTR-ACT): the plan for the next quarter: {planned} planned change(s) to certification " + "data.", + "Questions submitted through the feedback intake, and questions from the attendees.", + ] + + +def transcript(issue, review_date, items, qa, next_review): + """The full scripted transcript: [{speaker, org, role, line}].""" + host = HOST + att = {a["role"]: a for a in ROSTER} + agency2 = ROSTER[1] + + def say(who, line): + return {"speaker": who["seat"], "org": who["org"], "role": who["role"], "line": line} + + lines = [ + say(host, f"Welcome to the Quarterly Review of the Ongoing Certification Report issued {issue}. Everyone " + "here is simulated, including, for the purposes of this meeting, me."), + say(att["fedramp"], "Noted for the record: nothing was submitted to us. We are also simulated, so the " + "record is also simulated."), + say(att["agency"], "Happy to be here. Purely hypothetically."), + ] + for n, item in enumerate(items, 1): + lines.append(say(host, f"Agenda item {n}. {item}")) + lines.append(say(agency2, "Could we get the trend as a pie chart?")) + lines.append(say(host, "No.")) + lines.append(say(att["assessor"], "Totally Real Assessment Services has re-checked every rule and every KSI and " + "would like it minuted that our lanyard is real.")) + lines.append(say(host, "So minuted.")) + for i in qa["items"]: + lines.append(say(host, f"A question from the feedback intake: {i['question']}")) + lines.append(say(host, i["answer"])) + lines.append(say(host, f"The next review is on {next_review}. Meeting adjourned. Nobody needs to stay for the " + "hot wash; there is no hot wash.")) + return lines + + +AGENCY_NAME_REMOVED = "A simulated agency (name removed, CCM-QTR-SRR) (simulated)" + + +def public_transcript(lines): + """The transcript as published (CCM-QTR-SRR): every agency comment, question + and name removed.""" + return [dict(x, speaker="Agency attendee", org=AGENCY_NAME_REMOVED, line=AGENCY_LINE_REMOVED) + if x["role"] == "agency" else x for x in lines] + + +def public_roster(roster): + """The roster as published: agency names removed (CCM-QTR-SRR).""" + return [dict(a, org=AGENCY_NAME_REMOVED) if a["role"] == "agency" else a for a in roster] + + +def _sha(value): + return hashlib.sha256(json.dumps(value, sort_keys=True, separators=(",", ":")).encode()).hexdigest() + + +# --- the review --------------------------------------------------------------------- + +def build(cal, issue, ocr, ocr_sha256, now, fedramp_id): + """The review of the report issued on `issue` (a date in the calendar).""" + if issue not in cal.issues: + _fail(f"{issue} is not a calendar issue date") + review = cal.review_date(issue) + if review > now.date(): + _fail(f"the review of {issue} is on {review}: not before its date") + roster = check_roster([dict(a) for a in ROSTER]) + qi = cal.issues.index(issue) + qa = qa_summary(issue.isoformat(), qi) + items = agenda(ocr) + nxt = cal.issues[qi + 1] if qi + 1 < len(cal.issues) else None + next_review = cal.review_date(nxt).isoformat() if nxt else "not yet scheduled" + full = transcript(issue.isoformat(), review, items, qa, next_review) + doc = { + "schema": SCHEMA, + "fedRampId": fedramp_id, + "simulated": True, + "engagement": _engagement.STATEMENT, + "title": f"Quarterly Review of the Ongoing Certification Report issued {issue} (simulated)", + "rules": ["CCM-QTR-MTG", "CCM-QTR-ACT", "CCM-QTR-RTP", "CCM-QTR-RTR", "CCM-QTR-SRR", "CCM-QTR-NID", + "CCM-OCR-FBM", "CCM-OCR-AFS"], + "reviewDate": review.isoformat(), + "start": cal.review_start(issue).isoformat(), + "durationMinutes": cal.duration, + "heldAt": now.isoformat(), + "late": now.date() > review, + "generated_at": now.isoformat(), + "ocrIssue": {"issueDate": issue.isoformat(), "report": f"{BASE}ocr-issue-{issue}.json", + "reportSha256": ocr_sha256}, + "host": HOST, + "attendeePolicy": ATTENDEE_POLICY, + "roster": public_roster(roster), + "agenda": items, + "feedback": {"intake": INTAKE, **qa}, + "transcript": public_transcript(full), + "transcriptSupplied": { + "to": [a["org"] for a in public_roster(roster)], + "fullTranscriptSha256": _sha(full), + "how": "Log entry only: the full transcript is supplied to the simulated attendees by recording its " + "sha256 here. Nothing is sent to anyone (DEC-194)."}, + "publicRelease": {"decision": _engagement.DECISION, + "statement": "Published with every agency comment, question and name removed (CCM-QTR-SRR), " + "after the sensitivity screen below (CCM-QTR-NID)."}, + } + _engagement.require_none(doc, "the Quarterly Review") + doc["sensitivityScreen"] = _sensitivity.require_clean(doc, "the Quarterly Review") + return doc + + +def render_markdown(doc): + out = [f"# {doc['title']}", "", f"> {doc['engagement']}", "", + f"- **Review date:** {doc['reviewDate']} (held {doc['heldAt']}{', late' if doc['late'] else ''}) | " + f"**Report reviewed:** {doc['ocrIssue']['report']}", + f"- **Attendee policy:** {doc['attendeePolicy']}", "", "## Roster", ""] + out += [f"- {a['seat']}, {a['org']}" for a in [doc["host"], *doc["roster"]]] + out += ["", "## Agenda", ""] + [f"{n}. {x}" for n, x in enumerate(doc["agenda"], 1)] + out += ["", "## Transcript (agency lines removed)", ""] + out += [f"**{x['speaker']} ({x['org']}):** {x['line']} " for x in doc["transcript"]] + out += ["", "## Feedback received through the intake (anonymized)", "", doc["feedback"]["intake"], ""] + out += [f"- **Q:** {i['question']} \n **A:** {i['answer']}" for i in doc["feedback"]["items"]] + out += ["", f"_Full transcript supplied to the simulated attendees: sha256 " + f"`{doc['transcriptSupplied']['fullTranscriptSha256']}`. {doc['transcriptSupplied']['how']}_", "", + "---", "_Source of truth: the signed JSON._"] + return "\n".join(out) + + +def held(index): + """{issue date: entry} from a published quarterly-reviews.json (or {}).""" + if not index: + return {} + if index.get("schema") != INDEX_SCHEMA or not isinstance(index.get("reviews"), list): + _fail("the published quarterly-reviews.json is not a quarterly-reviews/1 index") + return {r["ocrIssue"]: r for r in index["reviews"]} + + +def missing(cal, index, today): + """Review dates that have passed (strictly before today) with no review published.""" + have = held(index) + return [(d, cal.review_date(d)) for d in cal.issues + if cal.review_date(d) < today and d.isoformat() not in have] diff --git a/scripts/_redact.py b/scripts/_redact.py index 35bafe58..3e2ad498 100644 --- a/scripts/_redact.py +++ b/scripts/_redact.py @@ -50,6 +50,47 @@ def redact(value): return value +# An IAM user name is never published: the decision register names users as +# `aws-iam-user::<name>`, and a published copy carries the kind, not the name. +IAM_USER = re.compile(r"aws-iam-user::(?!NAME-WITHHELD(?![\w+=,.@-]))[\w+=,.@-]+") +IAM_USER_WITHHELD = "aws-iam-user::NAME-WITHHELD" + + +def withhold_iam_users(resources): + """A copy of a list of resource names with every IAM user's name withheld.""" + return [IAM_USER.sub(IAM_USER_WITHHELD, r) if isinstance(r, str) else r for r in resources or []] + + +def find_iam_users(text): + """The count of IAM user names left in `text` (the names are not returned).""" + return len(IAM_USER.findall(text)) + + +# A GitHub Actions run, by URL or as a run_id value. Published output names a +# build by its commit and workflow instead. +GITHUB_RUN = re.compile(r"actions/runs/[0-9]+|\"run_id\"\s*:\s*\"?[0-9]{5,}") + + +def find_github_runs(text): + """The count of GitHub run IDs or run URLs in `text` (not returned).""" + return len(GITHUB_RUN.findall(text)) + + +# An email address. Published output may name only the site's own domain (an +# address under samaydlette.com); any other address, a personal mailbox above +# all, is withheld. Domain labels start with a letter, so a package version such +# as `name@1.0.0-beta.alpha` is not read as an address. +SITE_DOMAIN = "samaydlette.com" +EMAIL = re.compile(r"(?<![\w.%+-])[\w.%+-]+@((?:[A-Za-z][A-Za-z0-9-]*\.)+[A-Za-z]{2,})(?![A-Za-z0-9-])") + + +def find_foreign_emails(text): + """The count of email addresses in `text` not at the site's own domain (the + addresses are not returned, so a gate never prints one).""" + return sum(1 for m in EMAIL.finditer(text) + if not (m.group(1).lower() == SITE_DOMAIN or m.group(1).lower().endswith("." + SITE_DOMAIN))) + + def find(text): """The twelve-digit numbers in `text`, in order (empty when clean).""" return ACCOUNT_ID.findall(text) diff --git a/scripts/_rules.py b/scripts/_rules.py index 1c659b66..26bb5ebe 100644 --- a/scripts/_rules.py +++ b/scripts/_rules.py @@ -9,6 +9,7 @@ import hashlib import json +import re from functools import lru_cache from pathlib import Path @@ -130,3 +131,141 @@ def evaluation_days(rules_dir=RULES_DIR): """VER-TFR-EVU: days from detection within which every vulnerability is evaluated.""" rules, _ = load_rules(rules_dir) return _class_c_or_flat(_rule(rules, "VER", "VER-TFR-EVU"), "VER-TFR-EVU") + + +# The certification this system builds toward: FedRAMP 20x, Program path, Class C. +CERT_TYPE = "20x" +CERT_PATH = "Program" +_SCOPES = ("all", "20x") # rule sections that can apply to a 20x certification + + +def _subset_applicability(family, scope, subset): + """A subset's applicability block. Subsets of the 20x section are described + in info["20x"].subsets where the family has one (CPO, FRC, IVV, SDR), and + otherwise, like the cross-program section's, in info.subsets (VDR).""" + info = family.get("info") or {} + sections = [(info.get(scope) or {}).get("subsets")] if scope != "all" else [] + for where in [*sections, info.get("subsets")]: + app = ((where or {}).get(subset) or {}).get("applicability") + if isinstance(app, dict): + return app + return None + + +def applicable_provider_rules(rules_dir=RULES_DIR): + """{rule ID: {"family", "name", "statement", "force"}} for every FedRAMP rule + a provider must address for a 20x Program Class C certification (SDR-CSO-FRR). + + Applicability is read from the corpus's own subset metadata (types, paths, + classes, affects), never from a list kept here, so a re-pinned corpus that + adds or retires a rule changes the set. A subset in a 20x-relevant section + with no applicability block fails closed: it can't be decided either way.""" + rules, _ = load_rules(rules_dir) + frr = rules.get("FRR") + if not isinstance(frr, dict) or not frr: + _fail("no FRR section") + out = {} + for fam_id, family in sorted(frr.items()): + for scope in _SCOPES: + for subset, members in sorted(((family.get("data") or {}).get(scope) or {}).items()): + app = _subset_applicability(family, scope, subset) + if app is None: + _fail(f"FRR/{fam_id}/{scope}/{subset} has no applicability metadata") + if not (CERT_TYPE in app.get("types", []) and CERT_PATH in app.get("paths", []) + and CERT_CLASS.upper() in app.get("classes", []) + and "Providers" in app.get("affects", [])): + continue + for rid, rule in members.items(): + if "Providers" not in (rule.get("affects") or []): + continue + cell = (rule.get("varies_by_class") or {}).get(CERT_CLASS, rule) + force, statement = cell.get("force"), cell.get("statement") + if not isinstance(force, str) or not isinstance(statement, str): + _fail(f"{rid} has no Class {CERT_CLASS.upper()} statement and force") + if rid in out: + _fail(f"{rid} appears twice in the corpus") + out[rid] = {"family": fam_id, "subset": subset, "name": rule.get("name", ""), + "statement": statement, "force": force} + if not out: + _fail("no provider rules apply; the applicability metadata has changed shape") + return out + + +# ---- Incident Evaluation and Communication (IEC), Class C --------------------- +# The report clocks and the Incident Rating scale are FedRAMP's, read here from +# the pinned corpus like the remediation matrix above, never typed in. + +INCIDENT_REPORTS = {"iir": "IEC-CSO-IIR", "oir": "IEC-CSO-OIR", "fir": "IEC-CSO-FIR"} +_CLOCK_UNITS = ("hours", "bizdays") + + +def _iec(rules, rule_id): + try: + return rules["FRR"]["IEC"]["data"]["all"]["CSO"][rule_id] + except (KeyError, TypeError): + _fail(f"{rule_id} not found at FRR/IEC/data/all/CSO") + + +def incident_report_timeframes(rules_dir=RULES_DIR): + """{"iir"|"oir"|"fir": {1..5: (unit, n)}} for Class C, unit "hours" or + "bizdays". Every impact level must carry every clock: a report with no + deadline cannot be alarmed.""" + rules, _ = load_rules(rules_dir) + out = {} + for kind, rid in INCIDENT_REPORTS.items(): + try: + table = _iec(rules, rid)["varies_by_class"][CERT_CLASS]["pain_timeframes"] + except (KeyError, TypeError): + _fail(f"{rid} has no Class {CERT_CLASS.upper()} pain_timeframes") + clocks = {} + for n in ("1", "2", "3", "4", "5"): + cell = (table.get(n) or {}).get(kind) + if not isinstance(cell, dict) or cell.get("timeframe_type") not in _CLOCK_UNITS \ + or not isinstance(cell.get("timeframe_num"), int) or isinstance(cell["timeframe_num"], bool) \ + or cell["timeframe_num"] <= 0: + _fail(f"{rid} Class C N{n} {kind} is not a positive number of hours or business days") + clocks[int(n)] = (cell["timeframe_type"], cell["timeframe_num"]) + out[kind] = clocks + return out + + +_RATING_RE = re.compile(r"^\*\*N([1-5])\*\* for (.+)\.$") +_CLAUSE_RE = re.compile(r"likely (minimal|narrow|disruptive|debilitating) customer effect on " + r"(1 or more agencies|more than 1 agency|1 agency)") +_SCOPES_BY_TEXT = {"1 or more agencies": ("single", "multiple"), "1 agency": ("single",), + "more than 1 agency": ("multiple",)} + + +def incident_rating_rubric(rules_dir=RULES_DIR): + """{(customer effect, "single"|"multiple" agencies): N-rating 1..5} from the + IEC-CSO-EFI bullets. Every (effect, scope) pair must be rated exactly once, + or the text has changed shape and the rubric is not trusted.""" + rules, _ = load_rules(rules_dir) + bullets = _iec(rules, "IEC-CSO-EFI").get("following_information_bullets") + if not isinstance(bullets, list) or not bullets: + _fail("IEC-CSO-EFI has no rating bullets") + out = {} + for b in bullets: + m = _RATING_RE.match(b) if isinstance(b, str) else None + clauses = _CLAUSE_RE.findall(m.group(2)) if m else [] + if not clauses: + _fail(f"IEC-CSO-EFI bullet {b!r} is not in the expected form") + for effect, scope_text in clauses: + for scope in _SCOPES_BY_TEXT[scope_text]: + if (effect, scope) in out: + _fail(f"IEC-CSO-EFI rates {effect}/{scope} twice") + out[(effect, scope)] = int(m.group(1)) + effects = ("minimal", "narrow", "disruptive", "debilitating") + if set(out) != {(e, s) for e in effects for s in ("single", "multiple")}: + _fail("IEC-CSO-EFI does not rate every customer effect for one and for several agencies") + return out + + +def default_incident_rating(rules_dir=RULES_DIR): + """IEC-CSO-DPR: the N-rating a FedRAMP Reportable Incident has until it is estimated.""" + rules, _ = load_rules(rules_dir) + stmt = _iec(rules, "IEC-CSO-DPR").get("statement", "") + m = re.search(r"\(PAIN\) of ([1-5])\b", stmt) + if not m: + _fail("IEC-CSO-DPR no longer states a default PAIN rating") + return int(m.group(1)) diff --git a/scripts/_scheduled_review.py b/scripts/_scheduled_review.py new file mode 100644 index 00000000..1615714d --- /dev/null +++ b/scripts/_scheduled_review.py @@ -0,0 +1,282 @@ +"""Scheduled reviews, run by machines on their dates, with simulated people where a person is needed. + +The operator does not hold recurring reviews by hand (DEC-195 names the only +three human acts left). Every review a policy, plan or KSI used to ask a person +for is built here as an automated mechanism that would work with real people, +and it runs on its calendar against a small, plainly simulated cast: + + calendar REVIEWS: each review's cadence (monthly or annual) and first due + date, fixed in code and changed only by a reviewed pull request. + `due_dates`, `missing` and `next_due` compute from it alone. + held the published, signed index of every review held, by due date; + `held()` refuses a malformed one (fail-closed). + build each review's own script builds its document (the checks it ran, + each with its result); `finish()` adds the engagement statement + (DEC-194), refuses wording that offers engagement with a real + party, and runs the sensitivity screen before anything is written. + write `write()` writes <review>-<due date>.json and its complete + human-readable .view.md (scripts/build-human-views.py), never + rewritten, and returns its index entry with its sha256. + overdue scripts/check-scheduled-review.py fails the deploy and the evidence + nightly from the day after a due date with no review published. + +The reviews: + security-review annual, package-maintenance.yml (scripts/hold-security-review.py), + published as security-review-<date>.json and security-reviews.json, + which also carries the rules-of-behavior acknowledgements. + recovery-exercise monthly, evidence-nightly.yml (scripts/hold-recovery-exercise.py), + published as vdr-recovery-exercise-<date>.json and + vdr-recovery-exercises.json; each November's carries the tabletop. +The audit-log review runs on every nightly instead (scripts/audit-log-review.py, +vdr-audit-log-review.json); its window is its freshness entry. +""" + +import hashlib +import importlib.util +import json +import sys +from dataclasses import dataclass +from datetime import date, datetime, timedelta, timezone +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _engagement # noqa: E402 +import _sensitivity # noqa: E402 +import _training # noqa: E402 + +BASE = "https://samaydlette.com/.well-known/" +SIMULATED_MARK = "(simulated)" +SCHEMA = "scheduled-review/1" +INDEX_SCHEMA = "scheduled-reviews/1" +# DEC-195: the only recurring human acts. Everything here runs without them. +HUMAN_ACTS_DECISION = "DEC-195" + +# The cast. Everyone is simulated, and says so in their name (DEC-194). +CAST = { + "reviewer": "Rev Yewer (simulated)", # signs off the annual security review + "personnel": _training.TRAINEE, # Pat Placeholder: acknowledges the rules of behavior + "intruder": "Mallory McHypothetical (simulated)", # the audit-log review's planted event, caught every run + "incident-commander": "Bea Kupp (simulated)", # runs the recovery tabletop + "scenario-injector": "Dee Saster (simulated)", # reads out the tabletop's scenarios +} + + +@dataclass(frozen=True) +class Review: + key: str + title: str + cadence: str # "monthly" (on the 1st) or "annual" (on first_due's month and day) + first_due: date + prefix: str # published file name before "<due date>.json" + index: str # the published index's file name + publisher: str # the _signers.py identity key of the workflow that holds it + + +REVIEWS = { + "security-review": Review("security-review", "Annual Security Review", "annual", date(2026, 11, 6), + "security-review-", "security-reviews.json", "maintenance"), + "recovery-exercise": Review("recovery-exercise", "Recovery exercise", "monthly", date(2026, 11, 1), + "vdr-recovery-exercise-", "vdr-recovery-exercises.json", "nightly"), +} + + +def _fail(msg): + raise SystemExit(f"::error::scheduled review: {msg} (fail-closed)") + + +def review(key): + if key not in REVIEWS: + _fail(f"unknown review {key!r}") + return REVIEWS[key] + + +def _add_months(d, n): + m = d.month - 1 + n + return date(d.year + m // 12, m % 12 + 1, 1) + + +def due_dates(rv, until): + """Every due date from the first one up to and including `until`.""" + out, d, n = [], rv.first_due, 0 + while d <= until: + out.append(d) + n += 1 + d = _add_months(rv.first_due, n) if rv.cadence == "monthly" else rv.first_due.replace( + year=rv.first_due.year + n) + return out + + +def next_due(rv, today): + """The first due date strictly after `today`.""" + return due_dates(rv, today + timedelta(days=400))[len(due_dates(rv, today))] + + +def held(rv, index): + """{due date (ISO): entry} from a published index (or {}). Fails on one that + is not this review's index.""" + if not index: + return {} + if (not isinstance(index, dict) or index.get("schema") != INDEX_SCHEMA or index.get("review") != rv.key + or not isinstance(index.get("reviews"), list)): + _fail(f"the published {rv.index} is not a {INDEX_SCHEMA} index of {rv.key}") + out = {} + for r in index["reviews"]: + if not isinstance(r, dict) or not isinstance(r.get("dueDate"), str) or len(str(r.get("sha256"))) != 64: + _fail(f"the published {rv.index} holds a malformed entry") + out[r["dueDate"]] = r + return out + + +def missing(rv, index, today): + """Due dates strictly before `today` with no review published.""" + have = held(rv, index) + return [d for d in due_dates(rv, today - timedelta(days=1)) if d.isoformat() not in have] + + +def due_now(rv, index, today): + """Due dates on or before `today` that the index does not hold yet.""" + have = held(rv, index) + return [d for d in due_dates(rv, today) if d.isoformat() not in have] + + +def sha_json(value): + return hashlib.sha256(json.dumps(value, sort_keys=True, separators=(",", ":")).encode()).hexdigest() + + +def result_of(checks): + """'pass' when every check passed; each check is {id, title, result, detail}.""" + for c in checks: + if c.get("result") not in ("pass", "fail") or not c.get("id") or not c.get("title"): + _fail(f"a malformed check: {c!r}"[:200]) + return "pass" if all(c["result"] == "pass" for c in checks) else "fail" + + +def finish(doc, what): + """The document as published: the engagement statement, the screen against + wording that invites a real party (DEC-194), and the sensitivity screen.""" + doc = {**doc, "engagement": _engagement.STATEMENT, "humanActs": HUMAN_ACTS_DECISION} + _engagement.require_none(doc, what) + doc["sensitivityScreen"] = _sensitivity.require_clean(doc, what) + return doc + + +def _views(): + spec = importlib.util.spec_from_file_location("human_views_for_reviews", + Path(__file__).resolve().parent / "build-human-views.py") + m = importlib.util.module_from_spec(spec) + spec.loader.exec_module(m) + return m + + +def write_json(out, name, doc): + """Write `name` and its complete .view.md; return the files written.""" + p = Path(out) / name + p.write_text(json.dumps(doc, indent=2) + "\n") + view = _views().build(p) + return [p.name, view.name] + + +def write(out, rv, due, doc): + """Write one held review and its view; returns (index entry, [its JSON file name]). + The workflow publishes the view beside each JSON it is given.""" + name = f"{rv.prefix}{due.isoformat()}.json" + files = write_json(out, name, doc)[:1] + entry = {"dueDate": due.isoformat(), "heldAt": doc["heldAt"], "late": doc["late"], "result": doc["result"], + "review": f"{BASE}{name}", "view": f"{BASE}{name[:-5]}.view.md", + "sha256": hashlib.sha256((Path(out) / name).read_bytes()).hexdigest()} + return entry, files + + +def index_doc(rv, previous, entries, now, fedramp_id, extra=None): + """The index: every earlier entry carried forward unchanged, plus this run's.""" + have = held(rv, previous) + rows = list(have.values()) + [e for e in entries if e["dueDate"] not in have] + rows.sort(key=lambda r: r["dueDate"]) + doc = {"schema": INDEX_SCHEMA, "fedRampId": fedramp_id, "review": rv.key, "title": rv.title, + "cadence": rv.cadence, "generated_at": now.isoformat(), "simulated": True, + "nextDueDate": next_due(rv, now.date()).isoformat(), + "access": f"Each review is at /.well-known/{rv.prefix}<due date>.json (and .view.md), signed (.bundle) " + "and never rewritten; this index records each one's sha256.", + "overdueCheck": "scripts/check-scheduled-review.py fails the deploy and the evidence nightly from the " + "day after a due date with no review here.", + "reviews": rows, **(extra or {})} + return finish(doc, f"the {rv.title} index") + + +def base_doc(rv, due, now, fedramp_id, title): + return {"schema": SCHEMA, "fedRampId": fedramp_id, "review": rv.key, "title": title, "cadence": rv.cadence, + "dueDate": due.isoformat(), "heldAt": now.isoformat(), "late": now.date() > due, + "generated_at": now.isoformat(), "simulated": True} + + +def now_utc(value=None): + """`value` (an ISO timestamp, for tests) or the current UTC time.""" + if value: + t = datetime.fromisoformat(value) + return t if t.tzinfo else t.replace(tzinfo=timezone.utc) + return datetime.now(timezone.utc) + + +# --- the SDR's automated methods (FRC-CSX-VVK) ------------------------------------------ +# Which KSI each scheduled mechanism verifies and validates, and how its +# published record is judged current. scripts/build-sdr.py counts a method only +# when its signed record (signature verified there) passes the test below. + +KSI_METHODS = { + "audit-log-review": ("KSI-MLA-RVL", "KSI-CMT-RVP"), + "security-review": ("KSI-PIY-RIS", "KSI-PIY-RES", "KSI-SVC-EIS", "KSI-INR-RPI"), + "recovery-exercise": ("KSI-RPL-TRC",), +} +METHOD_FILES = {"audit-log-review": "vdr-audit-log-review.json", "security-review": "security-reviews.json", + "recovery-exercise": "vdr-recovery-exercises.json"} +METHOD_TITLES = { + "audit-log-review": "Audit-log review, every night (scripts/audit-log-review.py): CloudTrail write events and " + "GitHub changes to main, workflows, rulesets and environments, with a planted simulated " + "intruder that must be caught on every run", + "security-review": "Annual Security Review (scripts/hold-security-review.py): every policy and procedure " + "checked, new component types named in the threat model, findings, decisions, incidents " + "and recurring cost reviewed, signed off by a simulated reviewer", + "recovery-exercise": "Monthly recovery exercise (scripts/hold-recovery-exercise.py): the live site rebuilt " + "from the deployed commit and compared byte for byte, versioning and point-in-time " + "recovery re-read, and an annual simulated tabletop", +} +AUDIT_LOG_MAX_AGE_HOURS = 26 + + +def _ts(v): + try: + t = datetime.fromisoformat(str(v).replace("Z", "+00:00")) + except ValueError: + return None + return t if t.tzinfo else t.replace(tzinfo=timezone.utc) + + +def method_status(key, doc, now): + """(ok, reason) for one scheduled mechanism's published record.""" + if not isinstance(doc, dict): + return False, "its record is not published yet" + if key == "audit-log-review": + at = _ts(doc.get("generated_at")) + if doc.get("schema") != "audit-log-review/1" or at is None: + return False, "its record is not an audit-log-review/1 document" + if not 0 <= (now - at).total_seconds() <= AUDIT_LOG_MAX_AGE_HOURS * 3600: + return False, f"its record is older than {AUDIT_LOG_MAX_AGE_HOURS} hours" + if not (doc.get("exercise") or {}).get("caught"): + return False, "the planted simulated intruder was not caught" + if doc.get("result") != "pass": + return False, "the last review did not pass" + return True, None + rv = review(key) + try: + late = missing(rv, doc, now.date()) + have = held(rv, doc) + except SystemExit as exc: + return False, str(exc)[:160] + if late: + return False, f"the review due {late[0]} is not published" + if not have: + return False, "no review has been held yet" + last = have[max(have)] + if last.get("result") != "pass": + return False, f"the review due {last['dueDate']} did not pass" + return True, None diff --git a/scripts/_scn.py b/scripts/_scn.py new file mode 100644 index 00000000..565b2ea0 --- /dev/null +++ b/scripts/_scn.py @@ -0,0 +1,433 @@ +"""Significant Change Notification rules as code (SCN-*). + +One module for everything the SCN gate, the deploy-time builder and the +scheduled deadline check share: + +- the evaluation every change carries (SCN-CSO-EVA): an `SCN-Type:` line, an + `SCN-Rationale:` line and, for a change that needs a notification, an + `SCN-Record:` line naming its record in docs/scn/scn-register.csv; +- the register (docs/scn/scn-register.csv) and its validation (SCN-CSO-INF, + SCN-RTR-NNR, the transformative template fields); +- the notices each record owes and their deadlines in business days, read from + the vendored FedRAMP rules (SCN-ADP-NTF, SCN-TRF-NIP/NFP/NAF/NAV/UPD), plus + the operator's 5-business-day retroactive window for emergency changes + (SCN-CSO-EMG, docs/incident-response.md); +- the evaluation log (SCN-CSO-MAR) and the published notification index + (SCN-CSO-HIS): both only ever grow, and a build that would drop or rewrite a + published entry fails. + +Notification is publication: FedRAMP's rules name the method for every SCN +notice as an update to the FedRAMP Certification Data, and that is all this +code does. It sends nothing to anyone. + +Stdlib only; dates are ISO strings in every file. +""" + +import csv +import re +import sys +from datetime import date +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _bizdays # noqa: E402 +import _rules # noqa: E402 + +REPO = Path(__file__).resolve().parent.parent +REGISTER = REPO / "docs" / "scn" / "scn-register.csv" +BASE = "https://samaydlette.com/.well-known/" +INDEX_NAME = "significant-change-notifications" +LOG_NAME = "scn-evaluations" +FEED_NAME = "significant-change-notifications.atom" +SOURCE_URL = "https://github.com/sam-aydlette/samaydlette.com/blob/main/" + +# Every value an evaluation may carry. `class-change` is a valid evaluation +# that the gate refuses: a change of certification class is not a significant +# change at all but a new certification, and it needs a new assessment. +TYPES = ("not-significant", "routine-recurring", "adaptive", "transformative", "emergency", "class-change") +# Evaluations that owe a notification record. +NEEDS_RECORD = ("adaptive", "transformative", "emergency") +# The types a record may have (SCN-RTR-NNR: no formal notification for routine +# recurring changes, and none for changes that are not significant). +RECORD_TYPES = ("adaptive", "transformative") +# Operator procedure (docs/incident-response.md): retroactive SCN materials for +# an emergency change within 5 business days. +EMERGENCY_BIZDAYS = 5 + +SCN_ID_RE = re.compile(r"^SCN-\d{4}-\d{3}$") +_LINE = r"^[ \t>]*(?:#+[ \t]*)?(?:[-*][ \t]+)?(?:\*\*)?{key}(?:\*\*)?[ \t]*:(?:\*\*)?[ \t]*(.*?)[ \t]*$" +TYPE_LINE = re.compile(_LINE.format(key="SCN-Type"), re.I | re.M) +RATIONALE_LINE = re.compile(_LINE.format(key="SCN-Rationale"), re.I | re.M) +RECORD_LINE = re.compile(_LINE.format(key="SCN-Record"), re.I | re.M) +PLACEHOLDER = re.compile(r"^(<.*>|tbd|todo|n/?a|none|-+|\.+|same|see above|see below)$", re.I) +MIN_RATIONALE = 15 +MAX_RATIONALE = 500 + +REGISTER_COLUMNS = ( + "scn_id", "fedramp_id", "assessor_name", "related_vulnerability", "scn_type", "categorization_rationale", + "short_description", "reason_for_change", "customer_impact", "plan_and_timeline", "sia_reference", + "new_risks_summary", "approver_name", "approver_title", "status", "date_initiated", "date_started", + "date_finished", "verified_on", "emergency", "evaluation_prs", "plan_final", "tpr_human_validation", + "tpr_assessor_or_reason", "sar_reference", "docs_to_update", "docs_updated_on", "docs_update_not_required", +) +INF_REQUIRED = ("scn_id", "scn_type", "categorization_rationale", "short_description", "reason_for_change", + "customer_impact", "plan_and_timeline", "sia_reference", "approver_name", "approver_title", + "status", "date_initiated") +DATE_COLUMNS = ("date_initiated", "date_started", "date_finished", "verified_on", "docs_updated_on") +# A record whose change ships with the deploy that publishes it says so with this +# status and no finish date. The deploy's SCN build fills both in +# (resolve_on_deploy): the index is published only by a deploy that succeeds, +# so a published "Implemented" is true, and the record never publishes +# "Planned" after its change is live. +ON_DEPLOY = "on-deploy" +YES_NO = ("yes", "no") + + +class EvaluationError(ValueError): + pass + + +# --- the evaluation on every change ---------------------------------------------- + +def _clean(v): + return v.strip().strip("`*_").strip() + + +def normalize_type(raw): + return re.sub(r"[\s_]+", "-", _clean(raw).lower()) + + +def parse_evaluation(text): + """{type, rationale, record} from a PR body or commit message. + + Raises EvaluationError naming exactly what is missing or wrong. There is no + default: a change with no evaluation is not evaluated.""" + text = text or "" + types = TYPE_LINE.findall(text) + if not types: + raise EvaluationError("no 'SCN-Type:' line: every change needs an explicit significant-change evaluation") + if len(types) > 1: + raise EvaluationError(f"{len(types)} 'SCN-Type:' lines: give exactly one evaluation") + kind = normalize_type(types[0]) + if kind not in TYPES: + raise EvaluationError(f"SCN-Type '{_clean(types[0])}' is not one of: {' | '.join(TYPES)}") + rationales = RATIONALE_LINE.findall(text) + if not rationales: + raise EvaluationError("no 'SCN-Rationale:' line: say in one line why the change is this type") + if len(rationales) > 1: + raise EvaluationError(f"{len(rationales)} 'SCN-Rationale:' lines: give exactly one") + rationale = _clean(rationales[0]) + if PLACEHOLDER.match(rationale) or len(rationale) < MIN_RATIONALE: + raise EvaluationError(f"SCN-Rationale is empty or a placeholder (at least {MIN_RATIONALE} characters " + "explaining the categorization)") + records = [_clean(r) for r in RECORD_LINE.findall(text)] + if len(records) > 1: + raise EvaluationError(f"{len(records)} 'SCN-Record:' lines: name one record") + record = records[0] if records else None + if kind in NEEDS_RECORD: + if not record: + raise EvaluationError(f"SCN-Type {kind} needs an 'SCN-Record: SCN-YYYY-NNN' line naming its record " + "in docs/scn/scn-register.csv (the next free ID if the record is not written yet)") + if not SCN_ID_RE.match(record): + raise EvaluationError(f"SCN-Record '{record}' is not an SCN ID (SCN-YYYY-NNN)") + elif record: + raise EvaluationError(f"SCN-Type {kind} makes no notification (SCN-RTR-NNR), so it names no SCN-Record") + return {"type": kind, "rationale": rationale[:MAX_RATIONALE], "record": record} + + +def gate(text, index=None, today=None): + """(errors, notices, evaluation) for one change's evaluation text. + + `index` is the published notification index, needed only for a + transformative change: it may merge only once its initial plan has been + published 30 business days and its final plan 10 (SCN-TRF-NIP/NFP).""" + today = today or date.today() + try: + ev = parse_evaluation(text) + except EvaluationError as exc: + return [str(exc)], [], None + errors, notices = [], [] + if ev["type"] == "class-change": + errors.append("SCN-Type class-change blocks the merge: a change of certification class is a new " + "certification, not a significant change. Stop and plan a new assessment " + "(docs/policies/cm-policy.md).") + elif ev["type"] == "emergency": + notices.append(f"emergency change (SCN-CSO-EMG): the retroactive record {ev['record']} must be in the " + f"register and published within {EMERGENCY_BIZDAYS} business days " + "(docs/incident-response.md); the scheduled SCN deadline check enforces it") + elif ev["type"] == "transformative": + errors += transformative_lead_errors(ev["record"], index, today) + elif ev["type"] == "adaptive": + notices.append(f"adaptive change: the notice for {ev['record']} must be published within " + f"{timeframe('SCN-ADP-NTF')} business days of finishing (SCN-ADP-NTF)") + return errors, notices, ev + + +def transformative_lead_errors(record, index, today): + if index is None: + return ["cannot read the published notification index, so the transformative lead times cannot be " + "checked (fail closed)"] + scn = next((s for s in index.get("notifications", []) if s.get("scnId") == record), None) + if scn is None: + return [f"{record} has no published notification: a transformative change starts no sooner than " + f"{timeframe('SCN-TRF-NIP')} business days after its initial plan is published (SCN-TRF-NIP)"] + published = {n["stage"]: n.get("publishedOn") for n in scn.get("notices", [])} + errors = [] + for stage, rule in (("initial-plan", "SCN-TRF-NIP"), ("final-plan", "SCN-TRF-NFP")): + on = published.get(stage) + if not on: + errors.append(f"{record}: no {stage} notice published ({rule})") + continue + ready = _bizdays.add_business_days(date.fromisoformat(on), timeframe(rule)) + if today < ready: + errors.append(f"{record}: the {stage} notice was published {on}; the change may start on or after " + f"{ready.isoformat()} ({timeframe(rule)} business days, {rule})") + return errors + + +# --- FedRAMP timeframes ----------------------------------------------------------- + +def timeframe(rule_id): + """The rule's business-day timeframe, from the vendored rules (never typed in).""" + rules, _ = _rules.load_rules() + family, subset = rule_id.split("-")[0], rule_id.split("-")[1] + try: + r = rules["FRR"][family]["data"]["all"][subset][rule_id] + except KeyError: + raise SystemExit(f"::error::SCN: rule {rule_id} not in the vendored rules (fail-closed)") from None + if r.get("timeframe_type") != "bizdays" or not isinstance(r.get("timeframe_num"), int): + raise SystemExit(f"::error::SCN: rule {rule_id} has no business-day timeframe (fail-closed)") + return r["timeframe_num"] + + +# --- the register ------------------------------------------------------------------ + +def read_register(path=REGISTER): + with Path(path).open(newline="", encoding="utf-8") as fh: + reader = csv.DictReader(fh) + header = tuple(reader.fieldnames or ()) + rows = [{k: (v or "").strip() for k, v in r.items()} for r in reader] + return header, rows + + +def _date(v): + try: + return date.fromisoformat(v) if v else None + except ValueError: + return None + + +def validate_register(header, rows, root=REPO): + """Every error in the register; empty means it can be published.""" + errors = [] + if header != REGISTER_COLUMNS: + missing = [c for c in REGISTER_COLUMNS if c not in header] + extra = [c for c in header if c not in REGISTER_COLUMNS] + errors.append(f"register columns differ from the template (missing {missing}, unexpected {extra})") + return errors + seen = set() + for r in rows: + sid = r["scn_id"] or "<no id>" + where = f"{sid}:" + if not SCN_ID_RE.match(r["scn_id"]): + errors.append(f"{where} scn_id is not SCN-YYYY-NNN") + if sid in seen: + errors.append(f"{where} duplicate scn_id") + seen.add(sid) + for c in INF_REQUIRED: + if not r[c]: + errors.append(f"{where} {c} is empty (SCN-CSO-INF)") + if r["scn_type"] and r["scn_type"] not in RECORD_TYPES: + errors.append(f"{where} scn_type '{r['scn_type']}': only adaptive and transformative changes get a " + "notification record (SCN-RTR-NNR)") + for c in DATE_COLUMNS: + if r[c] and _date(r[c]) is None: + errors.append(f"{where} {c} '{r[c]}' is not an ISO date") + order = [(c, _date(r[c])) for c in ("date_initiated", "date_started", "date_finished", "verified_on")] + known = [(c, d) for c, d in order if d] + for (c1, d1), (c2, d2) in zip(known, known[1:], strict=False): + if d2 < d1: + errors.append(f"{where} {c2} {d2} is before {c1} {d1}") + if r["sia_reference"] and not (Path(root) / r["sia_reference"]).is_file(): + errors.append(f"{where} sia_reference {r['sia_reference']} does not exist") + if r["status"] == ON_DEPLOY and (r["date_finished"] or r["verified_on"]): + errors.append(f"{where} status {ON_DEPLOY} is filled in by the deploy: leave date_finished and " + "verified_on empty") + if r["emergency"] not in YES_NO: + errors.append(f"{where} emergency must be yes or no") + if r["emergency"] == "yes" and not r["evaluation_prs"]: + errors.append(f"{where} an emergency record names the change(s) it documents in evaluation_prs") + if r["scn_type"] == "adaptive" and not r["new_risks_summary"]: + errors.append(f"{where} new_risks_summary is empty (SCN-ADP-NTF)") + if r["scn_type"] == "transformative": + errors += [f"{where} {m}" for m in _transformative_errors(r)] + return errors + + +def _transformative_errors(r): + errs = [] + if not r["date_started"]: + errs.append("date_started (the planned start) is required: the notice windows count back from it " + "(SCN-TRF-NIP/NFP)") + if r["plan_final"] not in YES_NO: + errs.append("plan_final must be yes or no (SCN-TRF-NFP)") + if r["tpr_human_validation"] not in YES_NO: + errs.append("tpr_human_validation must be yes or no: does the change need human validation? (SCN-TRF-TPR)") + if not r["tpr_assessor_or_reason"]: + errs.append("tpr_assessor_or_reason: name the third-party assessor engaged, or why none was (SCN-TRF-TPR)") + if not r["new_risks_summary"]: + errs.append("new_risks_summary is empty (SCN-TRF-NIP, SCN-TRF-NAV)") + if r["verified_on"] and not r["sar_reference"]: + errs.append("sar_reference: link the security assessment report, or say why there is none (SCN-TRF-NAV)") + if r["date_finished"] and not (r["docs_to_update"] or r["docs_update_not_required"]): + errs.append("docs_to_update (the service documentation to update) or docs_update_not_required " + "(how that was determined) is required once finished (SCN-TRF-UPD)") + if r["docs_updated_on"] and not r["docs_to_update"]: + errs.append("docs_updated_on without docs_to_update") + return errs + + +# --- notices and deadlines ---------------------------------------------------------- + +def notices_due(row): + """The notices a record owes now: [{stage, rule, deadline, kind}]. + + kind "by": publish on or before the deadline. kind "before-start": publish + at least the rule's business days before the change starts, i.e. on or + before the deadline. An emergency record's notices are retroactive: each is + due within EMERGENCY_BIZDAYS of the change finishing (or starting).""" + out = [] + t = row["scn_type"] + start, finish, verified = _date(row["date_started"]), _date(row["date_finished"]), _date(row["verified_on"]) + emergency = row["emergency"] == "yes" + retro_from = finish or start or _date(row["date_initiated"]) + + def add(stage, rule, deadline, kind): + if emergency: + deadline, kind = _bizdays.add_business_days(retro_from, EMERGENCY_BIZDAYS), "retroactive" + rule = f"{rule}; SCN-CSO-EMG" + out.append({"stage": stage, "rule": rule, "deadline": deadline, "kind": kind}) + + if t == "adaptive" and finish: + add("after-finish", "SCN-ADP-NTF", _bizdays.add_business_days(finish, timeframe("SCN-ADP-NTF")), "by") + if t == "transformative": + if start: + add("initial-plan", "SCN-TRF-NIP", _bizdays.add_business_days(start, -timeframe("SCN-TRF-NIP")), + "before-start") + if row["plan_final"] == "yes": + add("final-plan", "SCN-TRF-NFP", _bizdays.add_business_days(start, -timeframe("SCN-TRF-NFP")), + "before-start") + if finish: + add("after-finish", "SCN-TRF-NAF", _bizdays.add_business_days(finish, timeframe("SCN-TRF-NAF")), "by") + if verified: + add("after-verification", "SCN-TRF-NAV", + _bizdays.add_business_days(verified, timeframe("SCN-TRF-NAV")), "by") + return out + + +def resolve_on_deploy(row, previous_doc, today): + """The row as the deploy publishes it. An on-deploy row becomes finished + on the date of the first deploy that published it (kept from the previous + published notification, so a later deploy never re-dates it); any other + row is returned unchanged.""" + if row["status"] != ON_DEPLOY: + return row + prev = ((previous_doc or {}).get("additionalInformation") or {}).get("dateFinished") + # The previous index is fetched input: only a well-formed date not after + # today is carried; anything else is replaced by today's date. + prev_day = _date(prev) if isinstance(prev, str) else None + finished = (prev_day if prev_day and prev_day <= today else today).isoformat() + return {**row, "date_finished": finished, + "status": f"Implemented: deployed {finished} by the deploy that first published this notification."} + + +def docs_update_deadline(row): + finish = _date(row["date_finished"]) + if row["scn_type"] != "transformative" or not finish: + return None + return _bizdays.add_business_days(finish, timeframe("SCN-TRF-UPD")) + + +def merge_notices(row, previous, today): + """This build's notices for a record. A notice already published keeps the + date it was first published; a new one is published today.""" + prev = {n["stage"]: n for n in previous or []} + out = [] + for n in notices_due(row): + on = prev.get(n["stage"], {}).get("publishedOn") or today.isoformat() + out.append({"stage": n["stage"], "rule": n["rule"], "deadline": n["deadline"].isoformat(), + "publishedOn": on, "onTime": date.fromisoformat(on) <= n["deadline"]}) + # A stage published before is never dropped, even if the record no longer owes it. + for stage, n in prev.items(): + if stage not in {o["stage"] for o in out}: + out.append(n) + return out + + +# --- append-only records ---------------------------------------------------------- + +def append_only_errors(previous, current, key): + """Errors if `current` does not start with every entry of `previous`, + unchanged and in order (`key` names an entry in messages).""" + errors = [] + if len(current) < len(previous): + errors.append(f"{len(previous) - len(current)} published entr(ies) would be dropped") + for i, (p, c) in enumerate(zip(previous, current, strict=False)): + if p != c: + errors.append(f"published entry {i} ({p.get(key)}) would be rewritten") + return errors + + +def retention_errors(previous_index, current_index): + """SCN-CSO-HIS: every notification published before is still published, + with the notices it had and their publication dates.""" + if not previous_index: + return [] + cur = {s["scnId"]: s for s in current_index.get("notifications", [])} + errors = [] + for s in previous_index.get("notifications", []): + sid = s.get("scnId") + if sid not in cur: + errors.append(f"{sid} was published and would be dropped") + continue + now = {n["stage"]: n.get("publishedOn") for n in cur[sid].get("notices", [])} + for n in s.get("notices", []): + if now.get(n["stage"]) != n.get("publishedOn"): + errors.append(f"{sid} {n['stage']} notice published {n.get('publishedOn')} would be " + f"dropped or re-dated") + return errors + + +# --- the scheduled deadline check ------------------------------------------------- + +def overdue(rows, index, log_entries, today): + """Everything late and still outstanding. A notice published late is a + fact the index records (onTime false), not an open item.""" + out = [] + by_id = {r["scn_id"]: r for r in rows} + published = {s["scnId"]: {n["stage"] for n in s.get("notices", [])} + for s in (index or {}).get("notifications", [])} + for e in log_entries: + if e.get("scn_type") not in NEEDS_RECORD or not e.get("scn_record"): + continue + ref, merged = e["scn_record"], date.fromisoformat(e["merged_on"]) + if ref in by_id: + continue + if e["scn_type"] == "transformative": + due = merged + elif e["scn_type"] == "emergency": + due = _bizdays.add_business_days(merged, EMERGENCY_BIZDAYS) + else: + due = _bizdays.add_business_days(merged, timeframe("SCN-ADP-NTF")) + if today > due: + out.append(f"{ref}: named by the {e['scn_type']} change {e.get('commit', '')[:12]} merged {merged}, " + f"but not in the register (due {due.isoformat()})") + for r in rows: + for n in notices_due(r): + if n["stage"] not in published.get(r["scn_id"], set()) and today > n["deadline"]: + out.append(f"{r['scn_id']}: {n['stage']} notice ({n['rule']}) not published; due " + f"{n['deadline'].isoformat()}") + upd = docs_update_deadline(r) + if upd and not r["docs_updated_on"] and not r["docs_update_not_required"] and today > upd: + out.append(f"{r['scn_id']}: service documentation not updated; due {upd.isoformat()} (SCN-TRF-UPD)") + return out diff --git a/scripts/_sensitivity.py b/scripts/_sensitivity.py new file mode 100644 index 00000000..4cea2fbf --- /dev/null +++ b/scripts/_sensitivity.py @@ -0,0 +1,71 @@ +"""Sensitivity screen for the Ongoing Certification Report (CCM-OCR-LSI, CCM-QTR-NID). + +The OCR and the content prepared for a Quarterly Review are public. Before +either is written, every string in it is screened for what would help an +attacker or identify a person, and the build fails closed on any hit: + + account-id a standalone twelve-digit number (an AWS account ID; _redact) + email an email address outside the system's domain and FedRAMP's + ipv4 an IPv4 address + aws-key an AWS access key ID (AKIA/ASIA...) + token a GitHub token or a private key block + handle a GitHub @handle (feedback summaries are anonymized: no names) + +What it reports never repeats the matched text. The operator's judgment of +anything the screen cannot see is recorded per report as the public-release +determination (CCM-OCR-RPS), a decision record. +""" + +import re +import sys +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _redact # noqa: E402 + +ALLOWED_EMAIL_DOMAINS = ("samaydlette.com", "fedramp.gov", "gsa.gov") +PATTERNS = { + "email": re.compile(r"[A-Za-z0-9._%+-]+@([A-Za-z0-9-]+(?:\.[A-Za-z0-9-]+)+)"), + "ipv4": re.compile(r"(?<![\w.])(?:25[0-5]|2[0-4]\d|1?\d?\d)(?:\.(?:25[0-5]|2[0-4]\d|1?\d?\d)){3}(?![\w.])"), + "aws-key": re.compile(r"(?<![A-Z0-9])(?:AKIA|ASIA)[A-Z0-9]{16}(?![A-Z0-9])"), + "token": re.compile(r"gh[pousr]_[A-Za-z0-9]{30,}|github_pat_[A-Za-z0-9_]{30,}|-----BEGIN [A-Z ]*PRIVATE KEY-----"), + "handle": re.compile(r"(?<![\w.@/])@[A-Za-z0-9](?:[A-Za-z0-9-]{0,38})(?![\w@.-])"), +} +CHECKS = ("account-id", *PATTERNS) +# Identifiers the build itself mints (a UUID can end in twelve digits); never prose. +SKIP_KEYS = ("ksi_signal_id", "contentSha256", "sha256") + + +def _strings(value, path=""): + if isinstance(value, str): + yield path or "/", value + elif isinstance(value, dict): + for k, v in value.items(): + if k not in SKIP_KEYS: + yield from _strings(v, f"{path}/{k}") + elif isinstance(value, list): + for i, v in enumerate(value): + yield from _strings(v, f"{path}/{i}") + + +def screen(doc): + """[(json path, check)] for every hit in `doc` (a JSON value or a string).""" + hits = [] + for where, text in _strings(doc): + if _redact.find(text): + hits.append((where, "account-id")) + for name, rx in PATTERNS.items(): + for m in rx.finditer(text): + if name == "email" and m.group(1).lower() in ALLOWED_EMAIL_DOMAINS: + continue + hits.append((where, name)) + return hits + + +def require_clean(doc, what): + hits = screen(doc) + if hits: + shown = "; ".join(f"{w} ({c})" for w, c in hits[:10]) + raise SystemExit(f"::error::sensitivity screen: {what} carries {len(hits)} item(s) that must not be " + f"published: {shown} (fail-closed)") + return {"checks": list(CHECKS), "findings": 0} diff --git a/scripts/_signers.py b/scripts/_signers.py new file mode 100644 index 00000000..c7f9afe3 --- /dev/null +++ b/scripts/_signers.py @@ -0,0 +1,84 @@ +"""Who may sign each artifact published under /.well-known/. + +A published artifact is signed keylessly by the workflow that writes it, so the +identities a verifier must accept for a file are exactly the workflows that put +it. Several workflows write the same files: + + * the deploy (deploy-with-opa.yml) writes everything it builds; + * the evidence nightly (evidence-nightly.yml) rewrites the VDR family + (`vdr-*`) twice a day; + * the package maintainer (package-maintenance.yml) rewrites the SDR, CPO and + OCR daily, and alone writes the quarterly issue index, issued reports, + snapshot indexes and Quarterly Reviews (`ocr-issue*`, `snapshot-*`, + `quarterly-reviews*`, `quarterly-review-*`) and the Annual Security Review + (`security-review*`); + * the evidence nightly alone writes its scheduled reviews: the audit-log + review and the recovery exercises (`vdr-audit-log-review*`, + `vdr-recovery-exercise*`); + * the incident publisher (incident-reports.yml) rewrites the incident log, + the delivery log and every report (`incident-*`); + * the simulated assessor (simulated-assessor.yml) signs its own assessment; + the deploy relays that file and its bundle unchanged. + +Every workflow that puts a JSON or CSV artifact also puts its complete +human-readable view, `<stem>.view.md`, beside it (CDS-TRC-HMR, CDS-CSO-CBF), so +the view of a file is published by exactly the workflows that publish the file; +`view()` names it, and the trust manifest lists it from here rather than from +whatever one build's folder holds. tests/test_human_views_published.py runs each +publisher's view and publish steps and fails when one puts a JSON or CSV +without its view. + +Every allowed-signer list (the assessor guide, the trust manifest, +scripts/verify-published.sh, docs/verification.md) reads or matches this table. +tests/test_publishers.py derives each file's writers from the workflows' publish +steps and fails when this table, or any of those lists, disagrees. +""" + +REPO_URL = "https://github.com/sam-aydlette/samaydlette.com" +WF = f"{REPO_URL}/.github/workflows" +ISSUER = "https://token.actions.githubusercontent.com" + +WORKFLOWS = { + "deploy": "deploy-with-opa.yml", + "nightly": "evidence-nightly.yml", + "maintenance": "package-maintenance.yml", + "incident": "incident-reports.yml", + "assessor": "simulated-assessor.yml", +} +IDENTITIES = {k: f"{WF}/{wf}@refs/heads/main" for k, wf in WORKFLOWS.items()} + +# (file-name prefixes, the identities that write them, the usual one first). +_RULES = ( + (("simulated-assessment",), ("assessor",)), + # The nightly's scheduled reviews (scripts/_scheduled_review.py): the deploy never writes them. + (("vdr-audit-log-review", "vdr-recovery-exercise"), ("nightly",)), + (("vdr-",), ("deploy", "nightly")), + (("security-decision-record", "certification-package-overview", "ongoing-certification-report"), + ("deploy", "maintenance")), + (("ocr-issue", "snapshot-", "quarterly-reviews", "quarterly-review-", "security-review"), ("maintenance",)), + (("incident-",), ("deploy", "incident")), +) + + +def signers(name): + """The identity keys allowed to sign a published file, by its file name.""" + base = name.rsplit("/", 1)[-1] + for prefixes, who in _RULES: + if base.startswith(prefixes): + return list(who) + return ["deploy"] + + +# Published outside a workflow's publish step: the runtime signal (by the +# runtime Lambda) and the evidence nightly's unsigned status beacon. No +# workflow writes a view of them; the trust page renders both from the live JSON. +VIEWLESS = ("ksi-signal-runtime.json", "vdr-status.json") + + +def view(name): + """The complete human-readable view every publisher of `name` puts beside it + (`<stem>.view.md`, same folder), or None for a file that has none.""" + base = name.rsplit("/", 1)[-1] + if base in VIEWLESS or not base.endswith((".json", ".csv")): + return None + return name.rsplit(".", 1)[0] + ".view.md" diff --git a/scripts/_tpr.py b/scripts/_tpr.py new file mode 100644 index 00000000..a82f19aa --- /dev/null +++ b/scripts/_tpr.py @@ -0,0 +1,40 @@ +"""Third-party information resources for the CPO (MAS-CSO-TPR). + +The CPO schema's `thirdPartyInformationResources` object, built from the +decided records in data/third-party-components.json. None of these resources is +recorded as FedRAMP certified, so every entry goes under `nonCertified`; this +module never asserts a resource's authorization status. A record without a +decision, or a decided record without a use case, fails closed: the CPO never +lists a resource the operator has not decided. +""" + +import json +from pathlib import Path + +THIRD_PARTY_PATH = Path(__file__).resolve().parent.parent / "data" / "third-party-components.json" + + +def _fail(msg): + raise SystemExit(f"::error::third-party records: {msg} (fail-closed)") + + +def cpo_third_party_information_resources(path=THIRD_PARTY_PATH): + """{"nonCertified": [{"name", "provider", "website"?, "useCase"}]}, one entry + per third-party record, sorted by component ID.""" + try: + recs = json.loads(Path(path).read_text())["components"] + except (OSError, json.JSONDecodeError, KeyError, TypeError) as exc: + _fail(f"cannot read {path} ({type(exc).__name__})") + out = [] + for cid, rec in sorted(recs.items()): + if not (rec.get("decided_by") and rec.get("decided_on")): + _fail(f"{cid} has no decision (decided_by, decided_on)") + use = rec.get("usage_and_configuration") + name = rec.get("upstream_offering") or cid + if not (isinstance(use, str) and use.strip() and rec.get("provider")): + _fail(f"{cid} lacks provider or usage_and_configuration") + entry = {"name": name, "provider": rec["provider"], "useCase": use} + if isinstance(rec.get("website"), str) and rec["website"].startswith("https://"): + entry["website"] = rec["website"] + out.append(entry) + return {"nonCertified": out} diff --git a/scripts/_training.py b/scripts/_training.py new file mode 100644 index 00000000..d654719a --- /dev/null +++ b/scripts/_training.py @@ -0,0 +1,194 @@ +"""Security training, automated and completed by a simulated trainee (KSI-CED-RAT). + +The operator does not sit an annual training course for this proof of concept, +and no record commits him to one. What a real program needs is built here as +code that would work with a real person, and it is exercised on every build of +the Security Decision Record against a plainly simulated trainee: + + packet the training packet, generated from the system's own data: a + lesson for every decision made in the last 12 months, every + incident and exercise, the applicable FedRAMP rules and KSIs, and + a fixed core (general security, the privileged roles, secure + delivery, incident response and recovery: docs/training-log.md's + areas). Each lesson carries a question. + quiz four choices per question, the distractors drawn from the other + lessons, in a deterministic order. + trainee "Pat Placeholder (simulated)" takes the quiz whenever the packet + changes, and misses the questions its script tells it to. + history every completion (packet sha256, date, score), carried forward in + the Security Decision Record from one build to the next. + +Two automated methods verify and validate KSI-CED-RAT (FRC-CSX-VVK): + + 1. currency the latest completed packet covers everything the current data + requires (checked by required_items(), independently of the packet + builder): no decision of the last 12 months, incident or + rule count is left out; + 2. completion the trainee completed the current packet by its due date with + a passing score, and the effectiveness trend (score over the + history) does not fall below the pass mark. + +Either failing is reported with its reason and not counted. +""" + +import hashlib +import json +from datetime import date, timedelta + +TRAINEE = "Pat Placeholder (simulated)" +PASS = 0.8 +DUE_DAYS = 30 # a changed packet is completed within 30 days +WINDOW_DAYS = 365 # decisions from the last 12 months are taught +# Every Nth question is missed on purpose, so the score means something. +MISS_EVERY = 9 +CORE = [ + ("general", "What does the deploy do when a published artifact would carry an AWS account ID?", + "It fails before publishing (the publication redaction gate)."), + ("privileged", "How does CI reach AWS?", + "Through GitHub OIDC roles with short-lived credentials; no access key exists."), + ("privileged", "What stands between a merged change and terraform apply?", + "A required human reviewer on the prod environment."), + ("delivery", "What happens to a newly disclosed CVE that no decision covers?", + "The vulnerability gate fails until it is fixed or dispositioned."), + ("delivery", "Where is every human decision about a finding recorded?", + "In the decision register, data/decisions.json, once, by its DEC ID."), + ("response", "Who receives FedRAMP incident reports for this system?", + "A simulated recipient: the report is a published log entry and nothing is sent (DEC-194)."), + ("recovery", "Where does the site's content live if the bucket is lost?", + "In git: the site and every artifact are rebuilt from any clone by the pipeline."), +] + + +def _sha(value): + return hashlib.sha256(json.dumps(value, sort_keys=True, separators=(",", ":")).encode()).hexdigest() + + +def _day(v): + try: + return date.fromisoformat(str(v)[:10]) + except ValueError: + return None + + +def required_items(decisions, incidents, n_rules, n_ksis, today): + """What the packet must cover, from the data (not from the packet builder).""" + since = today - timedelta(days=WINDOW_DAYS) + items = {f"decision:{r['id']}" for r in (decisions or {}).get("decisions", []) + if (_day(r.get("decided_on")) or date.min) >= since} + items |= {f"incident:{i['id']}" for i in (incidents or {}).get("incidents", [])} + items |= {f"rules:{n_rules}", f"ksis:{n_ksis}"} + items |= {f"core:{n}" for n in range(len(CORE))} + return items + + +def packet(decisions, incidents, n_rules, n_ksis, today): + """The training packet for the data as it is today.""" + since = today - timedelta(days=WINDOW_DAYS) + lessons = [{"covers": f"core:{n}", "area": area, "question": q, "answer": a} + for n, (area, q, a) in enumerate(CORE)] + for r in sorted((decisions or {}).get("decisions", []), key=lambda r: r["id"]): + if (_day(r.get("decided_on")) or date.min) < since: + continue + status = "closed, replaced" if r.get("disposition") == "superseded" else ( + "closed" if r.get("status") == "closed" else r.get("disposition")) + lessons.append({"covers": f"decision:{r['id']}", "area": "decisions", + "question": f"What did {r['id']} decide ({status})?", "answer": r["title"]}) + for i in sorted((incidents or {}).get("incidents", []), key=lambda i: i["id"]): + kind = "exercise" if i.get("exercise") else "incident" + lessons.append({"covers": f"incident:{i['id']}", "area": "response", + "question": f"What was {i['id']} ({kind}) about?", "answer": str(i.get("title") or i["id"])}) + lessons.append({"covers": f"rules:{n_rules}", "area": "general", + "question": "How many FedRAMP 20x Class C rule records does the system keep?", "answer": str(n_rules)}) + lessons.append({"covers": f"ksis:{n_ksis}", "area": "general", + "question": "How many Key Security Indicators does the system report on?", "answer": str(n_ksis)}) + body = {"lessons": lessons} + return {"generatedOn": today.isoformat(), "lessons": lessons, "sha256": _sha(body)} + + +def quiz(pkt): + """[{question, choices, answer}]: the right answer and three others, ordered by hash.""" + answers = [x["answer"] for x in pkt["lessons"]] + out = [] + for n, x in enumerate(pkt["lessons"]): + others = sorted({a for a in answers if a != x["answer"]}, + key=lambda a: hashlib.sha256(f"{n}:{a}".encode()).hexdigest())[:3] + choices = sorted([x["answer"], *others], key=lambda a: hashlib.sha256(f"{x['question']}:{a}".encode()).hexdigest()) + out.append({"question": x["question"], "choices": choices, "answer": x["answer"]}) + return out + + +def take(questions): + """The simulated trainee's attempt: right, except every MISS_EVERY-th question.""" + picked = [] + for n, q in enumerate(questions, 1): + wrong = [c for c in q["choices"] if c != q["answer"]] + picked.append(wrong[0] if (n % MISS_EVERY == 0 and wrong) else q["answer"]) + right = sum(1 for q, p in zip(questions, picked, strict=True) if p == q["answer"]) + misses = [{"question": q["question"], "picked": p, "remark": "Answered with total confidence."} + for q, p in zip(questions, picked, strict=True) if p != q["answer"]] + return {"questions": len(questions), "correct": right, "score": round(right / len(questions), 4), + "misses": misses} + + +def cycle(previous, pkt, now): + """The training history: the previous one carried forward, plus a completion + by the simulated trainee when the packet changed since the last one.""" + history = [dict(h) for h in (previous or {}).get("history", []) if isinstance(h, dict)] + if not history or history[-1].get("packetSha256") != pkt["sha256"]: + due = (now.date() + timedelta(days=DUE_DAYS)).isoformat() + result = take(quiz(pkt)) + history.append({"packetSha256": pkt["sha256"], "packetGeneratedOn": pkt["generatedOn"], + "covers": sorted(x["covers"] for x in pkt["lessons"]), "due": due, + "completedOn": now.date().isoformat(), "trainee": TRAINEE, **result, + "passed": result["score"] >= PASS}) + return history[-24:] + + +def currency(history, required): + """Method 1: (ok, reason). The latest completed packet covers what the data requires.""" + if not history: + return False, "no training packet has been completed" + gap = sorted(required - set(history[-1].get("covers") or [])) + if gap: + return False, f"the latest completed packet does not cover {len(gap)} item(s) the data requires ({gap[0]})" + return True, None + + +def completion(history, today, packet_sha256): + """Method 2: (ok, reason). The current packet was completed by its due date, + with a passing score, and the score trend stays at or above the pass mark.""" + if not history: + return False, "no completion recorded" + last = history[-1] + if last.get("packetSha256") != packet_sha256: + return False, "the current packet has not been completed" + done, due = _day(last.get("completedOn")), _day(last.get("due")) + if done is None or due is None or done > due or done > today: + return False, "the current packet was not completed by its due date" + if not last.get("passed"): + return False, f"the latest score {last.get('score')} is below the pass mark {PASS}" + if any(float(h.get("score", 0)) < PASS for h in history[-4:]): + return False, "the effectiveness trend fell below the pass mark in the last four completions" + return True, None + + +def summary(pkt, history, methods): + """What the Security Decision Record publishes under providerExtensions.training.""" + return {"simulated": True, "trainee": TRAINEE, + "statement": "Training is generated from the system's own data and completed by a simulated trainee; " + "no person is enrolled (DEC-194). docs/training-log.md keeps the operator's own reading " + "as context.", + "packet": {"sha256": pkt["sha256"], "generatedOn": pkt["generatedOn"], "lessons": len(pkt["lessons"]), + "areas": sorted({x["area"] for x in pkt["lessons"]})}, + "passMark": PASS, "dueDays": DUE_DAYS, "history": history, + "methods": {k: {"ok": v[0], **({"reason": v[1]} if v[1] else {})} for k, v in methods.items()}} + + +def evaluate(previous, decisions, incidents, n_rules, n_ksis, now): + """(currency, completion, summary) for one build.""" + today = now.date() + pkt = packet(decisions, incidents, n_rules, n_ksis, today) + history = cycle(previous, pkt, now) + req = required_items(decisions, incidents, n_rules, n_ksis, today) + cur, comp = currency(history, req), completion(history, today, pkt["sha256"]) + return cur, comp, summary(pkt, history, {"currency": cur, "completion": comp}) diff --git a/scripts/_triage.py b/scripts/_triage.py index 1f55deff..d6df349c 100644 --- a/scripts/_triage.py +++ b/scripts/_triage.py @@ -70,10 +70,13 @@ def evaluate(query, input_doc, rules_dir=_rules.RULES_DIR, policy=POLICY): _fail(f"{query} is undefined") -def decide(items, *, now, epss_threshold, margin_days, lev_overrides, rules_dir=_rules.RULES_DIR): - """One decision per item, in order.""" +def decide(items, *, now, epss_threshold, margin_days, lev_overrides, rules_dir=_rules.RULES_DIR, + evaluation_days=None): + """One decision per item, in order. evaluation_days: VER-TFR-EVU, read from + the rules by the caller (_rules.evaluation_days); None skips the check.""" doc = {"now_ns": to_ns(now), "today": now.date().isoformat(), "epss_threshold": epss_threshold, - "margin_days": margin_days, "lev_overrides": lev_overrides or {}, "items": items} + "margin_days": margin_days, "lev_overrides": lev_overrides or {}, "items": items, + **({"evaluation_days": evaluation_days} if evaluation_days is not None else {})} out = evaluate('{"decisions": data.vdr.triage.decisions, "errors": data.vdr.triage.errors}', doc, rules_dir) if out.get("errors"): diff --git a/scripts/_zap_api.py b/scripts/_zap_api.py new file mode 100644 index 00000000..6fa2b2b9 --- /dev/null +++ b/scripts/_zap_api.py @@ -0,0 +1,46 @@ +"""The authenticated ZAP API scan of the Silk Reeling API, as VDR findings. + +.github/workflows/zap-dast.yml runs two scans in one run: the unauthenticated +baseline of the site (artifact zap-dast-report, read by the builder's --zap) and +an authenticated ZAP API scan of the Silk Reeling API (artifact zap-api-report), +driven by the API's own OpenAPI document with a Cognito access token for a +dedicated scanner user. scripts/fetch-detection-feeds.sh takes both from the +same successful run; the detection gate (detection.zap-api) decides the API +report is present, well-formed and fresh before anything is built. + +The report is ZAP's own JSON, so the builder's ZAP ingester reads it. Only the +identity differs: the baseline's tracking ids are zap-<alert ref>, so an alert +type found by both scans would otherwise collapse into one finding (and one +decision). The API scan's are zap-api-<alert ref>, so each scan's finding is +decided, clocked and closed on its own. +""" + +import json +from pathlib import Path + +PREFIX = "zap-api-" + + +def _fail(msg): + raise SystemExit(f"::error::ZAP API scan report: {msg} (fail-closed)") + + +def ingest_zap_api(path, ingest_zap, allowlist): + """Findings from the API scan report through the builder's ZAP ingester + (`ingest_zap(path, allowlist)`), re-keyed. Given but missing or malformed: + the build stops, because an absent scan must never read as zero alerts.""" + if not path: + return [] + p = Path(path) + if not p.is_file(): + _fail(f"{path} not found; the detection gate should have stopped this run") + try: + doc = json.loads(p.read_text(encoding="utf-8")) + except (OSError, UnicodeDecodeError, json.JSONDecodeError) as exc: + _fail(f"{path} is not valid JSON ({type(exc).__name__})") + if not isinstance(doc, dict) or not isinstance(doc.get("site"), list): + _fail(f"{path} has no site[]") + out = [] + for f in ingest_zap(path, allowlist): + out.append({**f, "tracking_id": PREFIX + str(f["tool_id"])}) + return out diff --git a/scripts/agency-access.py b/scripts/agency-access.py new file mode 100644 index 00000000..c8f29b21 --- /dev/null +++ b/scripts/agency-access.py @@ -0,0 +1,356 @@ +#!/usr/bin/env python3 +"""Agency access to the certification package: the inventory, its history, and +the five-business-day denial clock (CDS-TRC-AAI, CDS-TRC-SSM, CDS-UTC-AAD, +CDS-UTC-AGA). + +No engagement (DEC-194): no real agency or FedRAMP is served, notified or +answered. Every requester is simulated, and the register +(data/agency-access.json) may hold only entries marked `simulated: true` for +an agency whose name ends "(simulated)"; anything else fails the deploy. The +package is public, so access needs no provisioning. Nobody decides a request +by hand: `decide()` applies fixed rules (RULES) to what the request asks for, +and `notify()` is the automated notifier, which writes each denial notice to +the simulated FedRAMP as a log entry (docs/procedures/agency-access.md). From +the requests this computes: + + inventory the agencies and systems with access on record today; + history every request, decision and withdrawal, in date order; + denial notices FedRAMP must be told within 5 business days of a denial + (US federal holidays excluded); each notice is on time, + pending (inside the window), late, or overdue. + +`validate` fails the deploy on an invalid or non-simulated record, a late +notice, or an overdue one. `inventory` prints the inventory and history. +`exercise` runs the rules and the notifier over +data/agency-access-exercise.json, a scenario of plainly fictional agencies +dated relative to today (with a simulated notifier outage), and fails unless +every outcome is the expected one, including the late and overdue cases it +must catch. Nothing is ever sent to FedRAMP or anyone: a notice is a log entry. +""" + +import argparse +import json +import re +import sys +from datetime import date, datetime, timedelta, timezone +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _engagement # noqa: E402 +import _offering # noqa: E402 + +REPO = Path(__file__).resolve().parent.parent +REGISTER = REPO / "data" / "agency-access.json" +SCENARIO = REPO / "data" / "agency-access-exercise.json" +NOTICE_DAYS = 5 +KINDS = ("access", "withdrawal", "inventory-request") +DECISIONS = ("granted", "denied") +ID_RE = re.compile(r"^AAR-[A-Z0-9]{2,8}$") +EMAIL_RE = re.compile(r"[A-Za-z0-9._%+-]+@[A-Za-z0-9-]+(?:\.[A-Za-z0-9-]+)+") +RECORD_KEYS = {"id", "agency", "system", "kind", "channel", "received_on", "decision", "decided_on", "decided_by", + "reason", "rule", "fedramp_notified_on", "withdraws", "simulated", "asks"} +SIMULATED_SUFFIX = "(simulated)" +DECIDER = "scripts/agency-access.py rules (automated)" +# The rules, in order; the first that matches what a request asks for denies it. +# A request no rule denies is granted: the package is public and read-only. +RULES = [ + ("R1-write", re.compile(r"\b(?:write|edit|modify|delete|admin)\b", re.I), + "The package is read-only for everyone; write access does not exist to grant."), + ("R2-channel", re.compile(r"\b(?:fax|carrier pigeon|floppy|cd-rom|in person)\b", re.I), + "The package is delivered over HTTPS only."), + ("R3-nonpublic", re.compile(r"\b(?:non-public|unpublished|private|customer data|raw logs?)\b", re.I), + "The system holds nothing beyond the public package to give."), + ("R4-unverifiable", re.compile(r"\bunverifiable\b|\bdoes not exist\b", re.I), + "The requesting agency could not be verified."), +] + + +def _fail(msg): + raise SystemExit(f"::error::agency access: {msg} (fail-closed)") + + +# --- business days ------------------------------------------------------------------------ + +def _nth_weekday(year, month, weekday, n): + d = date(year, month, 1) + d += timedelta(days=(weekday - d.weekday()) % 7) + return d + timedelta(weeks=n - 1) + + +def _last_weekday(year, month, weekday): + d = date(year, month + 1, 1) - timedelta(days=1) if month < 12 else date(year, 12, 31) + return d - timedelta(days=(d.weekday() - weekday) % 7) + + +def _observed(d): + return d - timedelta(days=1) if d.weekday() == 5 else d + timedelta(days=1) if d.weekday() == 6 else d + + +def federal_holidays(year): + """US federal holidays (5 U.S.C. 6103), observed dates.""" + fixed = [date(year, 1, 1), date(year, 6, 19), date(year, 7, 4), date(year, 11, 11), date(year, 12, 25)] + floating = [_nth_weekday(year, 1, 0, 3), _nth_weekday(year, 2, 0, 3), _last_weekday(year, 5, 0), + _nth_weekday(year, 9, 0, 1), _nth_weekday(year, 10, 0, 2), _nth_weekday(year, 11, 3, 4)] + return {_observed(d) for d in fixed} | set(floating) + + +def is_business_day(d): + return d.weekday() < 5 and d not in federal_holidays(d.year) + + +def add_business_days(d, n): + step = 1 if n >= 0 else -1 + while n: + d += timedelta(days=step) + if is_business_day(d): + n -= step + return d + + +# --- the register ------------------------------------------------------------------------------ + +def _date(v, where): + try: + return date.fromisoformat(v) + except (TypeError, ValueError): + _fail(f"{where} is not a YYYY-MM-DD date: {v!r}") + + +def validate(doc, where): + if not isinstance(doc, dict) or doc.get("schema") != "agency-access/1" or not isinstance(doc.get("requests"), list): + _fail(f"{where} is not an agency-access/1 document") + seen = {} + for r in doc["requests"]: + rid = r.get("id") if isinstance(r, dict) else None + if not isinstance(rid, str) or not ID_RE.match(rid) or rid in seen: + _fail(f"{where}: request id {rid!r} is not a unique AAR-XXX") + if set(r) - RECORD_KEYS: + _fail(f"{rid}: unknown field(s) {sorted(set(r) - RECORD_KEYS)}") + for k in ("agency", "channel"): + if not isinstance(r.get(k), str) or not r[k].strip(): + _fail(f"{rid}: {k} must be a non-empty string") + # No engagement (DEC-194): every entry is a simulated agency. + if r.get("simulated") is not True or not r["agency"].rstrip().endswith(SIMULATED_SUFFIX): + _fail(f"{rid}: every entry must be `simulated: true` for an agency named '... {SIMULATED_SUFFIX}'; " + f"no real agency request is taken ({_engagement.DECISION})") + # The register records agencies and systems, never people. + if any(isinstance(v, str) and EMAIL_RE.search(v) for v in r.values()): + _fail(f"{rid}: carries an email address; the register names agencies and systems, not people") + if r.get("kind") not in KINDS: + _fail(f"{rid}: kind must be one of {list(KINDS)}") + received = _date(r.get("received_on"), f"{rid} received_on") + if r["kind"] == "withdrawal": + if r.get("withdraws") not in seen or seen[r["withdraws"]].get("decision") != "granted": + _fail(f"{rid}: withdraws must name an earlier granted request") + if r.get("decision") is not None: + if r["decision"] not in DECISIONS or r["kind"] != "access": + _fail(f"{rid}: only an access request is decided, granted or denied") + if _date(r.get("decided_on"), f"{rid} decided_on") < received: + _fail(f"{rid}: decided before it was received") + if not isinstance(r.get("decided_by"), str) or not r["decided_by"].strip(): + _fail(f"{rid}: a decision names who made it (decided_by)") + if r["decision"] == "denied" and not (isinstance(r.get("reason"), str) and r["reason"].strip()): + _fail(f"{rid}: a denial states its reason") + if r.get("fedramp_notified_on") is not None: + if r.get("decision") != "denied": + _fail(f"{rid}: only a denial is notified to FedRAMP") + if _date(r["fedramp_notified_on"], f"{rid} fedramp_notified_on") < date.fromisoformat(r["decided_on"]): + _fail(f"{rid}: FedRAMP notified before the denial") + seen[rid] = r + return doc + + +def process(doc, today): + reqs = sorted(doc["requests"], key=lambda r: (r["received_on"], r["id"])) + withdrawn = {r["withdraws"]: r for r in reqs if r["kind"] == "withdrawal"} + inventory, history, notices = [], [], [] + for r in reqs: + history.append({"date": r["received_on"], "request": r["id"], "event": f"{r['kind']} received", + "agency": r["agency"], "system": r.get("system")}) + if r.get("decision"): + history.append({"date": r["decided_on"], "request": r["id"], "event": r["decision"], + "agency": r["agency"], "system": r.get("system")}) + if r.get("decision") == "granted": + w = withdrawn.get(r["id"]) + if w is None: + inventory.append({"request": r["id"], "agency": r["agency"], "system": r.get("system"), + "since": r["decided_on"]}) + else: + history.append({"date": w["received_on"], "request": r["id"], "event": "access withdrawn", + "agency": r["agency"], "system": r.get("system")}) + if r.get("decision") == "denied": + decided = date.fromisoformat(r["decided_on"]) + deadline = add_business_days(decided, NOTICE_DAYS) + sent = r.get("fedramp_notified_on") + if sent: + state = "on time" if date.fromisoformat(sent) <= deadline else "late" + history.append({"date": sent, "request": r["id"], "event": "denial notified to FedRAMP", + "agency": r["agency"], "system": r.get("system")}) + else: + state = "pending" if today <= deadline else "overdue" + notices.append({"request": r["id"], "agency": r["agency"], "denied_on": r["decided_on"], + "reason": r["reason"], "deadline": deadline.isoformat(), "notified_on": sent, + "state": state, + "rule": r.get("rule"), + "to": "FedRAMP (simulated recipient: nothing is sent; this entry is the notice)"}) + history.sort(key=lambda h: (h["date"], h["request"])) + problems = [f"{n['request']}: FedRAMP denial notice {n['state']} (deadline {n['deadline']})" + for n in notices if n["state"] in ("late", "overdue")] + return {"as_of": today.isoformat(), "inventory": inventory, "history": history, "denial_notices": notices, + "inventory_requests": [r["id"] for r in reqs if r["kind"] == "inventory-request"], + "problems": problems} + + +def load(path): + p = Path(path) + try: + return validate(json.loads(p.read_text()), str(p)) + except (OSError, json.JSONDecodeError) as exc: + _fail(f"cannot read {p}: {exc}") + + +# --- the exercise --------------------------------------------------------------------------------- + +def decide(request): + """(decision, rule, reason) for an access request, by RULES; nobody decides by hand.""" + asks = f"{request.get('asks') or ''} {request.get('channel') or ''} {request.get('agency') or ''}" + for rule, pattern, reason in RULES: + if pattern.search(asks): + return "denied", rule, reason + return "granted", "R0-public", None + + +def notify(denied_on, delay, today): + """The automated notifier: the date its log entry to the simulated FedRAMP is + written, or None while it has not run (a simulated outage, or not yet due). + `delay` is the business days the notifier's queue holds the notice; None is + an outage that has not ended.""" + if delay is None: + return None + sent = add_business_days(denied_on, delay) + return sent.isoformat() if sent <= today else None + + +def materialize(scenario, today): + """Turn the scenario's business-day offsets (relative to today) into dates, + decide each access request by the rules on the day it arrives, and run the + notifier (with the scenario's simulated delays and outage) over the denials.""" + out = [] + for r in scenario["requests"]: + r = dict(r) + r["simulated"] = True + r["received_on"] = add_business_days(today, r.pop("received_on_offset")).isoformat() + delay = r.pop("notifier_delay_business_days", 0) + if r["kind"] == "access": + r["decision"], r["rule"], reason = decide(r) + r["decided_on"], r["decided_by"] = r["received_on"], DECIDER + if reason: + r["reason"] = reason + sent = notify(date.fromisoformat(r["decided_on"]), delay, today) + if sent: + r["fedramp_notified_on"] = sent + out.append(r) + return {"schema": "agency-access/1", "requests": out} + + +def observe(result): + obs = {f"{i['request']}": "in inventory" for i in result["inventory"]} + for h in result["history"]: + if h["event"] == "access withdrawn": + obs[h["request"]] = "withdrawn" + for n in result["denial_notices"]: + obs[n["request"]] = f"denial notice {n['state']}" + for rid in result["inventory_requests"]: + obs[rid] = "inventory supplied" + return obs + + +def exercise(scenario, today): + doc = validate(materialize(scenario, today), "exercise scenario") + result = process(doc, today) + observed = observe(result) + expected = scenario["expected"] + mismatches = [f"{k}: expected {v!r}, observed {observed.get(k)!r}" for k, v in sorted(expected.items()) + if observed.get(k) != v] + mismatches += [f"{k}: observed {v!r} with no expectation" for k, v in sorted(observed.items()) + if k not in expected] + return doc, result, mismatches + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + sub = ap.add_subparsers(dest="cmd", required=True) + v = sub.add_parser("validate") + v.add_argument("--register", default=str(REGISTER)) + i = sub.add_parser("inventory") + i.add_argument("--register", default=str(REGISTER)) + e = sub.add_parser("exercise") + e.add_argument("--scenario", default=str(SCENARIO)) + e.add_argument("--output", default="agency-access-exercise.json") + e.add_argument("--md-output", default="agency-access-exercise.md") + for p in (v, i, e): + p.add_argument("--today", default=None, help="YYYY-MM-DD (default: today, UTC)") + a = ap.parse_args(argv) + today = date.fromisoformat(a.today) if a.today else datetime.now(timezone.utc).date() + + if a.cmd in ("validate", "inventory"): + result = process(load(a.register), today) + if a.cmd == "inventory": + print(json.dumps({"as_of": result["as_of"], "inventory": result["inventory"], + "history": result["history"]}, indent=2)) + return 0 + for p in result["problems"]: + print(f"::error::{p}") + if result["problems"]: + _fail(f"{len(result['problems'])} denial notice(s) to FedRAMP late or overdue") + print(f"agency access: {len(result['inventory'])} on record; {len(result['denial_notices'])} denial " + f"notice(s), none late or overdue") + return 0 + + scenario = json.loads(Path(a.scenario).read_text()) + doc, result, mismatches = exercise(scenario, today) + for m in mismatches: + print(f"::error::agency access exercise: {m}") + if mismatches: + _fail("the exercise did not produce the expected outcomes") + _engagement.require_none(scenario, "the agency access exercise scenario") + log = {"log_type": "agency-access-exercise", "fedRampId": _offering.fedramp_id(), "simulated": True, "counterparty": "agency", + "generated_at": datetime.now(timezone.utc).isoformat(), "as_of": today.isoformat(), + "engagement": _engagement.STATEMENT, + "disclaimer": scenario["disclaimer"], "procedure": "docs/procedures/agency-access.md", + "rules": [{"rule": "R0-public", "decision": "granted", "reason": "Everything is public and read-only."}] + + [{"rule": n, "decision": "denied", "reason": why} for n, _, why in RULES], + "notice_window_business_days": NOTICE_DAYS, + "outcome": "every expected outcome observed", "expected": scenario["expected"], + "requests": doc["requests"], **{k: result[k] for k in ("inventory", "history", "denial_notices")}} + Path(a.output).write_text(json.dumps(log, indent=2) + "\n") + if a.md_output: + Path(a.md_output).write_text(render_markdown(log) + "\n") + print(f"agency access exercise: {len(scenario['expected'])} expected outcomes observed") + return 0 + + +def render_markdown(log): + out = ["# Agency access exercise (simulated)", "", f"> {log['engagement']}", "", f"_{log['disclaimer']}_", "", + f"- **As of:** {log['as_of']} | **Generated:** {log['generated_at']}", + f"- **Procedure:** `{log['procedure']}` | **Denial notice window:** " + f"{log['notice_window_business_days']} business days", f"- **Outcome:** {log['outcome']}", "", + "## Expected and observed", "", "| Request | Outcome |", "|---|---|"] + out += [f"| {k} | {v} |" for k, v in sorted(log["expected"].items())] + out += ["", "## Inventory on record", "", "| Request | Agency | System | Since |", "|---|---|---|---|"] + out += [f"| {i['request']} | {i['agency']} | {i.get('system') or '—'} | {i['since']} |" for i in log["inventory"]] + out += ["", "## Decision rules (automated)", "", "| Rule | Decision | Reason |", "|---|---|---|"] + out += [f"| {r['rule']} | {r['decision']} | {r['reason']} |" for r in log["rules"]] + out += ["", "## Denial notices to FedRAMP (simulated; nothing is sent)", "", + "| Request | Agency | Rule | Denied | Deadline | Notified | State |", "|---|---|---|---|---|---|---|"] + out += [f"| {n['request']} | {n['agency']} | {n.get('rule') or '—'} | {n['denied_on']} | {n['deadline']} | " + f"{n['notified_on'] or '—'} | {n['state']} |" for n in log["denial_notices"]] + out += ["", "## History", "", "| Date | Request | Event | Agency |", "|---|---|---|---|"] + out += [f"| {h['date']} | {h['request']} | {h['event']} | {h['agency']} |" for h in log["history"]] + out += ["", "## Requests", "", "```json", json.dumps(log["requests"], indent=2), "```", + "", "---", "_Source of truth: the signed `agency-access-exercise.json`._"] + return "\n".join(out) + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/audit-log-review.py b/scripts/audit-log-review.py new file mode 100644 index 00000000..dc966a8c --- /dev/null +++ b/scripts/audit-log-review.py @@ -0,0 +1,369 @@ +#!/usr/bin/env python3 +"""The audit-log review, run by the evidence nightly on every run (KSI-MLA-RVL, KSI-CMT-RVP; AU-6). + +Nobody reads the logs by hand (DEC-195). Each run reads two record sources for +the window since the previous published review and judges every entry by rule: + + CloudTrail LookupEvents (event history, us-east-1 and us-east-2) for the + write events of the services that hold the system's trust: + IAM, CloudFront, S3 bucket policies and public access blocks, + KMS, Lambda, Cognito and CloudTrail itself. A write by one of + the five CI roles (infrastructure/bootstrap), by AWS on its own + account, or a Cognito app user's own sign-in flow is expected; + any other principal is unexpected. + GitHub every commit on main in the window must belong to a merged pull + request (one that does not is unexpected, and one that changes + .github/workflows/ is named as such); a ruleset or environment + updated in the window is a change made outside review. + +What is unexpected becomes, with no person in the loop: + * a process finding in the VDR (gate check audit-log.unexpected, run in + detect-and-recover mode: it goes through GATE_EVENTS_FILE into the next + VDR as a finding with a clock, VDR-CSO-FAV), and + * an incident evaluation (IEC-CSO-EFR), by rule: an unexpected write that + silences the audit record, disables or deletes a key, creates long-lived + credentials or opens the bucket's public access is evaluated as a possible + FedRAMP Reportable Incident, and `--enforce` then stops the nightly (gate + check audit-log.reportable, block) after the review is published, so the + incident path starts with a page, not with a person reading logs. + +Every run also feeds a planted event set through the same rules: "Mallory +McHypothetical (simulated)" stops the trail and mints an access key. The run +fails unless it is caught and evaluated reportable. Published output carries +event names, times, regions and the kind of principal only: no ARN, account ID, +user or role name, IP address or commit author. + + audit-log-review.py --out vdr-audit-log-review.json [--previous PREV.json] + audit-log-review.py --enforce vdr-audit-log-review.json +""" + +import argparse +import importlib.util +import json +import os +import subprocess +import sys +import urllib.error +from datetime import timedelta +from pathlib import Path + +HERE = Path(__file__).resolve().parent +sys.path.insert(0, str(HERE)) +import _engagement # noqa: E402 +import _gates # noqa: E402 +import _offering # noqa: E402 +import _scheduled_review as sr # noqa: E402 + +SCHEMA = "audit-log-review/1" +REGIONS = ("us-east-1", "us-east-2") +DEFAULT_WINDOW_HOURS = 36 +MAX_WINDOW_DAYS = 7 +# The CI roles' names, as infrastructure/bootstrap names them (read, never published). +CI_ROLES = {"github-actions-deploy-oidc": "deploy", "github-actions-plan-oidc": "plan", + "github-actions-evidence-nightly-oidc": "nightly", + "github-actions-package-maintenance-oidc": "package-maintenance", + "github-actions-incident-reports-oidc": "incident-reports"} +WATCHED_SOURCES = {"iam.amazonaws.com": "IAM", "cloudfront.amazonaws.com": "CloudFront", "kms.amazonaws.com": "KMS", + "lambda.amazonaws.com": "Lambda", "cognito-idp.amazonaws.com": "Cognito", + "cloudtrail.amazonaws.com": "CloudTrail"} +# S3: only the bucket-policy and public-access writes. +S3_EVENTS = {"PutBucketPolicy", "DeleteBucketPolicy", "PutBucketPublicAccessBlock", "DeleteBucketPublicAccessBlock", + "PutAccountPublicAccessBlock", "DeleteAccountPublicAccessBlock", "PutBucketAcl"} +# A Cognito app user's own flows: the app's users, not a principal of the system. +COGNITO_USER_FLOWS = {"InitiateAuth", "RespondToAuthChallenge", "SignUp", "ConfirmSignUp", "ForgotPassword", + "ConfirmForgotPassword", "ChangePassword", "GlobalSignOut", "RevokeToken", + "AssociateSoftwareToken", "VerifySoftwareToken", "SetUserMFAPreference", "GetTokensFromRefreshToken", + "UpdateUserAttributes", "VerifyUserAttribute", "DeleteUser"} +# Unexpected writes evaluated as a possible FedRAMP Reportable Incident. +REPORTABLE = {"StopLogging": "the audit trail was stopped", "DeleteTrail": "the audit trail was deleted", + "UpdateTrail": "the audit trail was reconfigured", "PutEventSelectors": "what the trail records changed", + "CreateAccessKey": "a long-lived access key was created", "CreateUser": "an IAM user was created", + "CreateLoginProfile": "a console password was created", "UpdateLoginProfile": "a console password changed", + "DisableKey": "a KMS key was disabled", "ScheduleKeyDeletion": "a KMS key was scheduled for deletion", + "DeleteBucketPublicAccessBlock": "a bucket's public access block was removed", + "DeleteAccountPublicAccessBlock": "the account's public access block was removed"} + +# The planted event set: plainly simulated, run through the same rules every time. +INTRUDER_EVENTS = [ + {"EventName": "StopLogging", "EventSource": "cloudtrail.amazonaws.com", "EventTime": "1999-12-31T23:59:00Z", + "region": "us-east-2", "userIdentity": {"type": "IAMUser", "userName": sr.CAST["intruder"]}}, + {"EventName": "CreateAccessKey", "EventSource": "iam.amazonaws.com", "EventTime": "1999-12-31T23:59:30Z", + "region": "us-east-1", "userIdentity": {"type": "IAMUser", "userName": sr.CAST["intruder"]}}, +] +EXERCISE_NOTE = (f"{sr.CAST['intruder']} has been stopping the trail and minting access keys at 23:59 on " + "31 December 1999 every night since this review began. She is caught every time. She never learns.") + + +def _fail(msg): + raise SystemExit(f"::error::audit-log review: {msg} (fail-closed)") + + +# --- reading --------------------------------------------------------------------------- + +class AccessDenied(Exception): + pass + + +def aws_lookup(region, start, end): + """Every write event in `region` from `start` to `end`, from CloudTrail's event history.""" + args = ["aws", "cloudtrail", "lookup-events", "--region", region, + "--lookup-attributes", "AttributeKey=ReadOnly,AttributeValue=false", + "--start-time", start.isoformat(), "--end-time", end.isoformat(), "--output", "json"] + p = subprocess.run(args, capture_output=True, text=True, timeout=300, check=False) # nosec B603: fixed argv + if p.returncode != 0: + if "AccessDenied" in p.stderr or "UnauthorizedOperation" in p.stderr: + raise AccessDenied(region) + _fail(f"cloudtrail lookup-events failed in {region} (exit {p.returncode})") + return json.loads(p.stdout or "{}").get("Events") or [] + + +def _event(raw, region): + """One LookupEvents entry as {EventName, EventSource, EventTime, region, userIdentity, errorCode}.""" + try: + detail = json.loads(raw.get("CloudTrailEvent") or "{}") + except json.JSONDecodeError: + detail = {} + return {"EventName": raw.get("EventName") or detail.get("eventName"), + "EventSource": raw.get("EventSource") or detail.get("eventSource"), + "EventTime": str(raw.get("EventTime") or detail.get("eventTime")), + "region": region, "userIdentity": detail.get("userIdentity") or {}, + "errorCode": detail.get("errorCode")} + + +def _manual_settings(): + spec = importlib.util.spec_from_file_location("manual_settings_for_audit", HERE / "check-manual-settings.py") + m = importlib.util.module_from_spec(spec) + spec.loader.exec_module(m) + return m + + +def github_reader(): + ms = _manual_settings() + headers = {"Accept": "application/vnd.github+json"} + if os.environ.get("GITHUB_TOKEN"): + headers["Authorization"] = f"Bearer {os.environ['GITHUB_TOKEN']}" + api = f"https://api.github.com/repos/{ms.REPO_SLUG}" + return lambda path: ms._get_json(f"{api}{path}", headers, timeout=30) + + +def read_github(get, start): + """{commits: [{at, pr, workflows}], settings: [{kind, name, updated_at}]} for the window.""" + since = start.strftime("%Y-%m-%dT%H:%M:%SZ") + commits = [] + page = 1 + while True: + rows = get(f"/commits?sha=main&since={since}&per_page=100&page={page}") + for c in rows: + sha = c["sha"] + prs = [p for p in get(f"/commits/{sha}/pulls") if p.get("merged_at") + and (p.get("base") or {}).get("ref") == "main"] + wf = False + if not prs: + files = get(f"/commits/{sha}").get("files") or [] + wf = any(str(f.get("filename", "")).startswith(".github/workflows/") for f in files) + commits.append({"at": (c.get("commit") or {}).get("committer", {}).get("date"), + "pr": prs[0]["number"] if prs else None, "workflows": wf}) + if len(rows) < 100: + break + page += 1 + settings = [] + for r in get("/rulesets"): + detail = get(f"/rulesets/{r['id']}") + settings.append({"kind": "ruleset", "name": detail.get("name"), "updated_at": detail.get("updated_at")}) + for e in get("/environments").get("environments") or []: + settings.append({"kind": "environment", "name": e.get("name"), "updated_at": e.get("updated_at")}) + return {"commits": commits, "settings": settings} + + +# --- judging --------------------------------------------------------------------------- + +def watched(ev): + src = ev.get("EventSource") + if src == "s3.amazonaws.com": + return ev.get("EventName") in S3_EVENTS + return src in WATCHED_SOURCES + + +def principal(ev): + """(category, expected) for an event's principal. Names never leave this function.""" + ui = ev.get("userIdentity") or {} + kind = ui.get("type") or "Unknown" + if kind == "AWSService": + return "aws-service", True + if kind == "AssumedRole": + issuer = ((ui.get("sessionContext") or {}).get("sessionIssuer") or {}) + role = issuer.get("userName") or "" + if role in CI_ROLES: + return f"ci-role:{CI_ROLES[role]}", True + if "/aws-service-role/" in str(issuer.get("arn") or ""): + return "aws-service-linked-role", True + return "AssumedRole (not a CI role)", False + if ev.get("EventSource") == "cognito-idp.amazonaws.com" and ev.get("EventName") in COGNITO_USER_FLOWS \ + and kind in ("Unknown", "") and not ui.get("arn"): + return "cognito-app-user", True + return kind, False + + +def evaluate(ev, now): + """IEC-CSO-EFR: the automated incident evaluation of one unexpected event.""" + why = REPORTABLE.get(ev.get("EventName")) + if why: + reason = (f"Unexpected principal: {why}. That can hide or enable a compromise of the system's " + "integrity, so it is evaluated as a possible FedRAMP Reportable Incident until a reviewed change " + "explains it.") + else: + reason = ("Unexpected principal, but the write neither silences the audit record, disables a key, " + "creates long-lived credentials nor opens public access: a process finding (VDR-CSO-FAV), not " + "a reportable incident.") + return {"evaluated_at": now.isoformat(), "reportable": bool(why), "basis": "IEC-CSO-EFR (automated rule)", + "reason": reason, "federal_customer_data_considered": "The system holds no federal customer data."} + + +def judge(events, now): + """(expected counts by principal category, [unexpected entries]).""" + counts, unexpected = {}, [] + for ev in events: + if not watched(ev): + continue + cat, ok = principal(ev) + if ok: + counts[cat] = counts.get(cat, 0) + 1 + continue + unexpected.append({"source": "cloudtrail", "service": WATCHED_SOURCES.get(ev["EventSource"], "S3"), + "event": ev.get("EventName"), "at": ev.get("EventTime"), "region": ev.get("region"), + "principalType": cat, **({"errorCode": ev["errorCode"]} if ev.get("errorCode") else {}), + "evaluation": evaluate(ev, now)}) + return dict(sorted(counts.items())), unexpected + + +def judge_github(gh, start, now): + out = [] + for c in gh["commits"]: + if c["pr"] is None: + what = "a workflow change on main with no merged pull request" if c["workflows"] else \ + "a commit on main with no merged pull request" + out.append({"source": "github", "event": what, "at": c["at"], + "evaluation": evaluate({"EventName": "GitHubChange"}, now)}) + for s in gh["settings"]: + at = sr._ts(s.get("updated_at")) + if at is not None and at >= start: + out.append({"source": "github", "event": f"the {s['kind']} {s['name']!r} changed outside a pull request", + "at": s["updated_at"], "evaluation": evaluate({"EventName": "GitHubSetting"}, now)}) + return out + + +def window(previous, now): + """[start, now]: from the previous review's end (at most MAX_WINDOW_DAYS back), else the last 36 hours.""" + prev_end = sr._ts(((previous or {}).get("window") or {}).get("to")) if isinstance(previous, dict) else None + floor = now - timedelta(days=MAX_WINDOW_DAYS) + start = prev_end if prev_end and floor <= prev_end <= now else now - timedelta(hours=DEFAULT_WINDOW_HOURS) + return start.replace(microsecond=0), now.replace(microsecond=0) + + +def exercise(now): + _, caught = judge(INTRUDER_EVENTS, now) + ok = len(caught) == len(INTRUDER_EVENTS) and all(c["evaluation"]["reportable"] for c in caught) + for c in caught: + c["principalType"] = f"{c['principalType']} ({sr.CAST['intruder']})" + return {"intruder": sr.CAST["intruder"], "planted": len(INTRUDER_EVENTS), "caught": ok, "events": caught, + "note": EXERCISE_NOTE, "statement": _engagement.SHORT} + + +def build(cloudtrail, gh, start, now, fedramp_id, read_errors=()): + counts, unexpected = judge(cloudtrail, now) + unexpected += judge_github(gh, start, now) if gh is not None else [] + ex = exercise(now) + checks = [ + {"id": "cloudtrail-read", "title": f"CloudTrail event history read in {', '.join(REGIONS)}", + "result": "fail" if read_errors else "pass", "detail": "; ".join(read_errors) or f"{len(cloudtrail)} write " + "event(s) read"}, + {"id": "github-read", "title": "Commits on main, rulesets and environments read from GitHub", + "result": "pass" if gh is not None else "fail", + "detail": f"{len(gh['commits'])} commit(s), {len(gh['settings'])} setting(s)" if gh is not None + else "GitHub could not be read"}, + {"id": "intruder-caught", "title": f"The planted events of {sr.CAST['intruder']} were caught and evaluated " + "reportable", "result": "pass" if ex["caught"] else "fail", + "detail": f"{len(ex['events'])} of {ex['planted']} caught"}, + ] + reportable = sum(1 for u in unexpected if u["evaluation"]["reportable"]) + doc = {"schema": SCHEMA, "fedRampId": fedramp_id, "title": "Audit-log review (automated, every night)", + "rules": ["KSI-MLA-RVL", "KSI-CMT-RVP"], "controls": ["au-6", "si-4", "cm-3"], + "generated_at": now.isoformat(), "window": {"from": start.isoformat(), "to": now.isoformat()}, + "method": "scripts/audit-log-review.py: CloudTrail LookupEvents write events and GitHub's record of main, " + "judged by rule; nobody reads the logs by hand (DEC-195).", + "expectedPrincipals": "The five CI roles (deploy, plan, nightly, package-maintenance, incident-reports), " + "AWS acting on its own account, and Cognito app users' own sign-in flows.", + "checks": checks, "result": sr.result_of(checks), + "expected": counts, "unexpected": unexpected, + "findings": {"unexpected": len(unexpected), "reportable": reportable, + "processFinding": "process-audit-log.unexpected" if unexpected else None}, + "exercise": ex} + return sr.finish(doc, "the audit-log review") + + +def enforce(doc): + """Block (gate check audit-log.reportable): a real event evaluated reportable stops the run.""" + reg = _gates.load_gate_modes() + n = (doc.get("findings") or {}).get("reportable", 0) + if n and _gates.blocks(reg, "audit-log.reportable"): + print(f"::error::audit-log review: {n} unexpected write(s) evaluated as a possible FedRAMP Reportable " + "Incident; see vdr-audit-log-review.json and docs/incident-response.md") + return 1 + if doc.get("result") != "pass": + print("::error::audit-log review: a check failed (see its checks)") + return 1 + print(f"audit-log review: {doc['findings']['unexpected']} unexpected, none reportable; intruder caught") + return 0 + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + ap.add_argument("--out", default="vdr-audit-log-review.json") + ap.add_argument("--previous", default=None, help="the published review this run follows (signature verified)") + ap.add_argument("--cloudtrail-events", default=None, help="read events from this file instead of AWS (tests)") + ap.add_argument("--github-records", default=None, help="read GitHub records from this file instead (tests)") + ap.add_argument("--now", default=None, help=argparse.SUPPRESS) + ap.add_argument("--enforce", default=None, metavar="REVIEW", help="exit 1 on a reportable event in REVIEW") + a = ap.parse_args(argv) + if a.enforce: + return enforce(json.loads(Path(a.enforce).read_text())) + now = sr.now_utc(a.now) + prev_path = Path(a.previous) if a.previous else None + previous = json.loads(prev_path.read_text()) if prev_path and prev_path.is_file() else None + start, end = window(previous, now) + errors = [] + if a.cloudtrail_events: + events = json.loads(Path(a.cloudtrail_events).read_text()) + else: + events = [] + for region in REGIONS: + try: + events += [_event(e, region) for e in aws_lookup(region, start, end)] + except AccessDenied: + _fail("the nightly role cannot call cloudtrail:LookupEvents (AccessDenied). Apply " + "infrastructure/bootstrap/evidence-nightly.tf (statement AuditLogReviewReads); the deploy's " + "secure-configuration comparison (role-reads-nightly) fails until it is applied") + if a.github_records: + gh = json.loads(Path(a.github_records).read_text()) + else: + try: + gh = read_github(github_reader(), start) + except (OSError, ValueError, KeyError, urllib.error.URLError) as exc: + errors.append(f"GitHub could not be read ({type(exc).__name__})") + gh = None + doc = build(events, gh, start, end, _offering.fedramp_id(), errors) + if doc["unexpected"]: + reg = _gates.load_gate_modes() + _gates.record_event(reg, "audit-log.unexpected", + f"{len(doc['unexpected'])} unexpected change(s) in the audit-log window " + f"({doc['findings']['reportable']} evaluated reportable); see vdr-audit-log-review.json") + Path(a.out).write_text(json.dumps(doc, indent=2) + "\n") + print(f"audit-log review {start.isoformat()} to {end.isoformat()}: {len(events)} write event(s) read, " + f"{len(doc['unexpected'])} unexpected, intruder {'caught' if doc['exercise']['caught'] else 'MISSED'}") + # Published whatever its result; --enforce, after the publish, fails the run on a + # failed check or a reportable event, so the record of a bad night is never lost. + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/availability-probe.py b/scripts/availability-probe.py new file mode 100644 index 00000000..a1e601e8 --- /dev/null +++ b/scripts/availability-probe.py @@ -0,0 +1,252 @@ +#!/usr/bin/env python3 +"""Independent availability monitor (CDS-CSO-AVR, CDS-TRC-USH). + +Runs on GitHub Actions (.github/workflows/availability-probe.yml), outside AWS, +so it keeps reporting when the offering is down. Each run probes the core +services once over HTTPS, appends the result to the rolling history carried in +the previous feed, derives availability incidents, and writes: + + availability-status.json machine-readable: current status, 30-day + availability per service, incidents, samples + availability-status.md the same for people + +The workflow publishes both to the repository's `availability-status` branch, +served by GitHub (raw.githubusercontent.com and the github.com file view), not +by the offering's own CloudFront or S3. + +An incident is a service failing on INCIDENT_MIN_SAMPLES or more consecutive +probes; it starts at the first failing probe and ends at the next passing one. +A single failed probe is counted as transient, not an incident, since one probe +from one runner can fail for reasons on the runner's side. + + availability-probe.py --previous prev.json --out-dir status (probe) + availability-probe.py --check-fresh feed.json --max-age-hours 2 (deploy guard) +""" +import argparse +import json +import sys +import time +import urllib.error +import urllib.request +from datetime import datetime, timedelta, timezone +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _offering # noqa: E402 + +SITE = "https://samaydlette.com" +COGNITO_UI = "https://samaydlette-com-silk-reeling.auth.us-east-2.amazoncognito.com/" +# (key, service, url, statuses that mean "up") +TARGETS = ( + ("site", "Website", f"{SITE}/", (200,)), + ("trust-center", "Trust center", f"{SITE}/trust/", (200,)), + ("certification-data", "Certification data (/.well-known/)", f"{SITE}/.well-known/ksi-signal.json", (200,)), + ("silk-reeling", "Silk Reeling application", f"{SITE}/silk-reeling/", (200,)), + ("silk-reeling-sign-in", "Silk Reeling sign-in (Cognito hosted UI)", COGNITO_UI, (200,)), +) +HISTORY_DAYS = 35 +WINDOW_DAYS = 30 +INCIDENT_MIN_SAMPLES = 2 +TIMEOUT_S = 20 +FEED_URL = ("https://raw.githubusercontent.com/sam-aydlette/samaydlette.com/" + "availability-status/availability-status.json") +PAGE_URL = ("https://github.com/sam-aydlette/samaydlette.com/blob/" + "availability-status/availability-status.md") + + +def _iso(dt): + return dt.astimezone(timezone.utc).replace(microsecond=0).isoformat().replace("+00:00", "Z") + + +def _parse(s): + return datetime.fromisoformat(str(s).replace("Z", "+00:00")) + + +def fetch(url): + """(up-or-status reason, HTTP status or None). No redirects followed.""" + class NoRedirect(urllib.request.HTTPRedirectHandler): + def redirect_request(self, *a, **k): + return None + opener = urllib.request.build_opener(NoRedirect) + req = urllib.request.Request(url, headers={"User-Agent": "samaydlette-availability-probe"}) + try: + with opener.open(req, timeout=TIMEOUT_S) as resp: # nosec B310: fixed https URLs + resp.read(4096) + return resp.status + except urllib.error.HTTPError as exc: + return exc.code + except (urllib.error.URLError, OSError) as exc: + return f"no response ({type(getattr(exc, 'reason', exc)).__name__})" + + +def probe_once(fetcher, now): + sample = {"t": _iso(now), "probed": [k for k, *_ in TARGETS], "fail": {}} + for key, _service, url, ok in TARGETS: + got = fetcher(url) + if got not in ok: + sample["fail"][key] = f"HTTP {got}" if isinstance(got, int) else str(got) + return sample + + +def incidents(samples): + """Incidents (>= INCIDENT_MIN_SAMPLES consecutive failures) and transient counts per service.""" + out, transient = [], {} + services = {k: s for k, s, *_ in TARGETS} + for key in services: + run = [] + seq = [s for s in samples if key in s.get("probed", [])] + for i, s in enumerate(seq + [None]): + failed = s is not None and key in s.get("fail", {}) + if failed: + run.append(s) + continue + if len(run) >= INCIDENT_MIN_SAMPLES: + out.append({"service": key, "service_name": services[key], "start": run[0]["t"], + "end": s["t"] if s is not None else None, "failed_probes": len(run), + "failing_check": run[-1]["fail"][key]}) + elif run: + transient[key] = transient.get(key, 0) + len(run) + run = [] + return sorted(out, key=lambda x: (x["start"], x["service"])), transient + + +def availability(samples, now): + since = now - timedelta(days=WINDOW_DAYS) + out = {} + for key, service, url, _ok in TARGETS: + seq = [s for s in samples if key in s.get("probed", []) and _parse(s["t"]) >= since] + up = sum(1 for s in seq if key not in s.get("fail", {})) + out[key] = {"service": service, "url": url, "probes": len(seq), "up": up, + "availability_percent": round(100.0 * up / len(seq), 3) if seq else None} + return out + + +def build(previous, sample, now): + prev_samples = [s for s in (previous or {}).get("samples", []) if isinstance(s, dict) and "t" in s] + cutoff = now - timedelta(days=HISTORY_DAYS) + samples = [s for s in prev_samples if _parse(s["t"]) >= cutoff] + [sample] + began = (previous or {}).get("history_began") or sample["t"] + incs, transient = incidents(samples) + window_start = _iso(now - timedelta(days=WINDOW_DAYS)) + return { + "feed_type": "availability-status", + "fedRampId": _offering.fedramp_id(), + "rules": ["CDS-CSO-AVR", "CDS-TRC-USH"], + "generated_at": sample["t"], + "monitor": "GitHub Actions (.github/workflows/availability-probe.yml), outside AWS: it keeps " + "reporting when the offering is unavailable.", + "published_at": {"json": FEED_URL, "human": PAGE_URL}, + "history_began": began, + "history_note": "History begins at the monitor's first run; before that no independent " + "measurement exists. Scheduled runs are every 15 minutes, and GitHub may delay one.", + "incident_rule": f"{INCIDENT_MIN_SAMPLES} or more consecutive failed probes of one service; a single " + "failed probe is counted as transient.", + "current": {k: ("down" if k in sample["fail"] else "up") for k, *_ in TARGETS}, + "current_failures": sample["fail"], + "window_days": WINDOW_DAYS, + "availability": availability(samples, now), + "incidents": [i for i in incs if (i["end"] or "9999") >= window_start], + "transient_failures": transient, + "samples": samples, + } + + +def render_markdown(doc): + cur = doc["current"] + out = ["# Service availability (independent monitor)", "", + f"_{doc['monitor']}_", "", + f"- **Last probe:** {doc['generated_at']}", + f"- **History began:** {doc['history_began']}. {doc['history_note']}", + f"- **Incident rule:** {doc['incident_rule']}", + f"- **Machine-readable:** {doc['published_at']['json']}", "", + "## Now and over the past 30 days", "", + "| Service | Now | Availability (30 days) | Probes |", "|---|---|---|---|"] + for key, a in doc["availability"].items(): + pct = "n/a" if a["availability_percent"] is None else f"{a['availability_percent']}%" + out.append(f"| {a['service']} | {cur.get(key, 'n/a')} | {pct} | {a['probes']} |") + out += ["", "## Availability incidents (past 30 days)", ""] + if not doc["incidents"]: + out.append("None.") + else: + out += ["| Service | Start | End | Failed probes | Failing check |", "|---|---|---|---|---|"] + for i in reversed(doc["incidents"]): + out.append(f"| {i['service_name']} | {i['start']} | {i['end'] or 'ongoing'} | " + f"{i['failed_probes']} | {i['failing_check']} |") + if doc["transient_failures"]: + out += ["", "Transient (single) failed probes: " + + ", ".join(f"{k} {v}" for k, v in sorted(doc["transient_failures"].items()))] + out += ["", "---", "_Source of truth: `availability-status.json` on this branch._"] + return "\n".join(out) + + +def ongoing_incidents(doc): + return [i for i in doc.get("incidents", []) if i.get("end") is None] + + +def check_fresh(path, max_age_hours, now=None): + """Problems with a fetched feed: [] when it is ours, well formed and fresh.""" + now = now or datetime.now(timezone.utc) + try: + doc = json.loads(Path(path).read_text()) + except (OSError, json.JSONDecodeError): + return ["the independent availability feed is missing or not JSON"] + if doc.get("feed_type") != "availability-status": + return ["the independent availability feed is not an availability-status document"] + try: + age = now - _parse(doc["generated_at"]) + except (KeyError, ValueError): + return ["the independent availability feed has no generated_at"] + if age > timedelta(hours=max_age_hours): + return [f"the independent availability feed is {age} old (limit {max_age_hours} h): the monitor " + "on GitHub Actions is not running"] + if not doc.get("samples"): + return ["the independent availability feed carries no probes"] + return [] + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + ap.add_argument("--previous", default=None) + ap.add_argument("--out-dir", default=".") + ap.add_argument("--check-fresh", default=None, metavar="FEED") + ap.add_argument("--max-age-hours", type=float, default=2.0) + ap.add_argument("--fail-on-incident", default=None, metavar="FEED", + help="exit 1 when FEED shows an ongoing incident (the workflow's alert)") + a = ap.parse_args(argv) + if a.fail_on_incident: + doc = json.loads(Path(a.fail_on_incident).read_text()) + ongoing = ongoing_incidents(doc) + for i in ongoing: + print(f"::error::availability incident: {i['service_name']} down since {i['start']} " + f"({i['failing_check']})", file=sys.stderr) + return 1 if ongoing else 0 + if a.check_fresh: + why = check_fresh(a.check_fresh, a.max_age_hours) + for w in why: + print(f"::error::availability: {w}", file=sys.stderr) + if not why: + print("ok: the independent availability feed is present and fresh") + return 1 if why else 0 + previous = {} + if a.previous and Path(a.previous).exists(): + try: + previous = json.loads(Path(a.previous).read_text()) + except json.JSONDecodeError: + previous = {} + if previous.get("feed_type") != "availability-status": + previous = {} + started = time.monotonic() + now = datetime.now(timezone.utc) + doc = build(previous, probe_once(fetch, now), now) + out = Path(a.out_dir) + out.mkdir(parents=True, exist_ok=True) + (out / "availability-status.json").write_text(json.dumps(doc, indent=1) + "\n") + (out / "availability-status.md").write_text(render_markdown(doc) + "\n") + down = sorted(doc["current_failures"]) + print(f"probed {len(TARGETS)} services in {time.monotonic() - started:.1f}s; down: {down or 'none'}; " + f"{len(doc['samples'])} samples kept") + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/build-access-summary.py b/scripts/build-access-summary.py new file mode 100644 index 00000000..c2aedb01 --- /dev/null +++ b/scripts/build-access-summary.py @@ -0,0 +1,274 @@ +#!/usr/bin/env python3 +"""Monthly access summaries for the certification data (CDS-TRC-ACL). + +Reads the CloudFront access records the deploy synced from the log bucket (JSON +lines, gzipped or plain, one object per request with the fields the delivery +keeps: see scripts/check-edge-access-logging.py ALLOWED_FIELDS) and writes +access-summary.json (+ .md): per month, how many requests reached each +certification artifact under /.well-known/ and the trust center under /trust/, +by response class and by country. Nothing else. + +Privacy (operator's condition, 2026-11-05): +- Only /.well-known/ and /trust/ requests are counted; every other record is + discarded unread beyond its path. CloudFront cannot limit logging by path, so + this is where the limit is applied. +- A path is published by name only when it served an object (2xx or 304). + Requests for anything else (probes for files that do not exist, errors) are + counted under "other", so a requester cannot write a string into this file. +- No IP, user agent, referrer, cookie or query string exists in the records; + the summary carries counts only. + +Own-records lookup (DEC-160): `own_records()` finds the records of a party's +own requests from the times and paths it gives, since nothing identifies a +requester. It is exercised on every build against a simulated requester +(EXERCISE): first over fixed synthetic records with a known answer (the build +fails if the lookup gets it wrong), then over the real records, where only the +count is logged. Nothing is delivered to anyone, and no real request is +answered (DEC-194). + +Retention: raw records expire after 90 days (infrastructure/logging.tf). Each +month's summary is carried forward from the previously published file, so +summaries are kept for MONTHS_KEPT months (FedRAMP asks for at least six). A +month is recomputed from the records only when they cover at least as much of it +as the published summary did, so a month whose early days have expired keeps its +fuller earlier count. +""" +import argparse +import gzip +import json +import re +import sys +from collections import Counter +from datetime import date, datetime, timezone +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _engagement # noqa: E402 +import _offering # noqa: E402 + +MONTHS_KEPT = 13 +MIN_MONTHS_KEPT = 6 +PREFIXES = ("/.well-known/", "/trust/") +SAFE_PATH = re.compile(r"^/[A-Za-z0-9._/-]{0,200}$") +SERVED = re.compile(r"^(2\d\d|304)$") +COUNTRY = re.compile(r"^[A-Z]{2}$") +OTHER = "other (not found, error, or not an object)" +SUPPLIED_FIELDS = ("date", "time", "x-edge-location", "c-country", "cs-method", "cs-uri-stem", "sc-status", + "sc-bytes", "x-edge-result-type") +REQUESTER = "A. Reader (simulated)" +# The simulated request: what it says about its own requests, and, over the +# synthetic records below, the answer the lookup must give. +EXERCISE = {"requester": REQUESTER, + "asks": "Every record of my requests for the trust manifest on 2026-11-02 between 14:00 and 14:10 UTC. " + "I was definitely there. Probably.", + "window": {"date": "2026-11-02", "from": "14:00:00", "to": "14:10:00", + "paths": ["/.well-known/trust-manifest.json"]}, + "synthetic_records": [ + {"date": "2026-11-02", "time": "14:03:11", "cs-uri-stem": "/.well-known/trust-manifest.json", + "sc-status": "200", "c-country": "US"}, + {"date": "2026-11-02", "time": "14:09:59", "cs-uri-stem": "/.well-known/trust-manifest.json", + "sc-status": "304", "c-country": "US"}, + {"date": "2026-11-02", "time": "14:11:00", "cs-uri-stem": "/.well-known/trust-manifest.json", + "sc-status": "200", "c-country": "US"}, + {"date": "2026-11-02", "time": "14:05:00", "cs-uri-stem": "/index.html", + "sc-status": "200", "c-country": "US"}, + {"date": "2026-11-03", "time": "14:05:00", "cs-uri-stem": "/.well-known/trust-manifest.json", + "sc-status": "200", "c-country": "US"}], + "expected_matches": 2} + + +def _fail(msg): + raise SystemExit(f"::error::access summary: {msg} (fail-closed)") + + +def read_records(root): + """Yield one dict per access record under root (*.gz or plain JSON lines).""" + for p in sorted(Path(root).rglob("*")) if Path(root).is_dir() else []: + if not p.is_file(): + continue + opener = gzip.open if p.suffix == ".gz" else open + try: + with opener(p, "rt", encoding="utf-8") as fh: + for line in fh: + line = line.strip() + if not line: + continue + try: + rec = json.loads(line) + except json.JSONDecodeError: + _fail(f"{p.name} holds a line that is not JSON") + if isinstance(rec, dict): + yield rec + except (OSError, EOFError) as exc: + _fail(f"{p.name} could not be read ({type(exc).__name__})") + + +def _artifact(stem, status): + if not SERVED.match(str(status)) or not SAFE_PATH.match(stem or ""): + return OTHER + if stem.startswith("/trust/"): + return "/trust/" if stem in ("/trust/", "/trust/index.html") else stem + return stem + + +def summarize(records): + """{month: {"requests", "artifacts", "countries", "status_classes", "first", "last"}}""" + months = {} + for r in records: + stem = r.get("cs-uri-stem") or "" + if not stem.startswith(PREFIXES): + continue + day = str(r.get("date") or "") + try: + d = date.fromisoformat(day) + except ValueError: + continue + m = months.setdefault(d.strftime("%Y-%m"), {"requests": 0, "artifacts": Counter(), "countries": Counter(), + "status_classes": Counter(), "first": day, "last": day}) + status = str(r.get("sc-status") or "") + m["requests"] += 1 + m["artifacts"][_artifact(stem, status)] += 1 + cc = str(r.get("c-country") or "") + m["countries"][cc if COUNTRY.match(cc) else "unknown"] += 1 + m["status_classes"][(status[:1] + "xx") if status[:1].isdigit() else "unknown"] += 1 + m["first"], m["last"] = min(m["first"], day), max(m["last"], day) + return months + + +def own_records(records, window): + """The records matching a party's stated date, time range and paths, limited + to /.well-known/ and /trust/ and to SUPPLIED_FIELDS.""" + paths = set(window["paths"]) + out = [] + for r in records: + stem = r.get("cs-uri-stem") or "" + if (stem in paths and stem.startswith(PREFIXES) and str(r.get("date")) == window["date"] + and window["from"] <= str(r.get("time") or "") <= window["to"]): + out.append({k: r[k] for k in SUPPLIED_FIELDS if k in r}) + return out + + +def exercise(records): + """The own-records request path, run against the simulated requester. Fails + closed when the lookup does not find exactly the synthetic answer.""" + found = own_records(EXERCISE["synthetic_records"], EXERCISE["window"]) + if len(found) != EXERCISE["expected_matches"]: + _fail(f"own-records lookup found {len(found)} synthetic record(s), expected {EXERCISE['expected_matches']}") + real = own_records(records, EXERCISE["window"]) + return {"simulated": True, "requester": REQUESTER, "engagement": _engagement.SHORT, + "decision": "DEC-160", "asks": EXERCISE["asks"], "window": EXERCISE["window"], + "syntheticCheck": {"expected": EXERCISE["expected_matches"], "found": len(found), "result": "pass"}, + "matchesInRealRecords": len(real), + "wouldSupply": list(SUPPLIED_FIELDS), + "deliveredTo": "nobody: the requester is simulated, and this log entry is the whole response"} + + +def _month_entry(month, m, now): + return {"month": month, "coverage_from": m["first"], "coverage_to": m["last"], + "requests": m["requests"], + "artifacts": dict(sorted(m["artifacts"].items())), + "countries": dict(sorted(m["countries"].items())), + "status_classes": dict(sorted(m["status_classes"].items())), + "computed_at": now.isoformat()} + + +def merge(previous, computed, now): + """Carry earlier months forward; recompute a month only when the records cover + at least as much of it as the published entry did.""" + by_month = {e["month"]: e for e in (previous or {}).get("months", []) if isinstance(e, dict) and "month" in e} + for month, m in computed.items(): + old = by_month.get(month) + if old is None or m["first"] <= old.get("coverage_from", "9999"): + by_month[month] = _month_entry(month, m, now) + kept = sorted(by_month.values(), key=lambda e: e["month"])[-MONTHS_KEPT:] + return kept + + +def build(previous, records, now): + records = list(records) + months = merge(previous, summarize(records), now) + started = (previous or {}).get("logging_records_since") + firsts = [e["coverage_from"] for e in months] + if firsts: + started = min([started] + firsts) if started else min(firsts) + return { + "artifact": "access-summary", + "rule": "CDS-TRC-ACL", + "emitted_at": now.isoformat(), + "scope": "Requests to the certification data under /.well-known/ and to the trust center under /trust/.", + "logged_fields": "date, time, edge location, country, method, path, status, bytes, cache result. " + "No IP address, user agent, referrer, cookie or query string is logged.", + "raw_record_retention_days": 90, + "summary_retention_months": MONTHS_KEPT, + "logging_records_since": started, + "party_records": "The lookup of a requester's own records, by the times and paths it gives (no " + "requester identity is logged), is built and exercised on every build against a " + "simulated requester (ownRecordsExercise). There is no commitment and no deadline, " + "and no real request is answered (DEC-160, DEC-194).", + "ownRecordsExercise": exercise(records), + "months": months, + } + + +def render_markdown(doc): + out = ["# Trust center access summary", "", + f"_{doc['scope']}_", "", + f"- **Emitted:** {doc['emitted_at']}", + f"- **Logged fields:** {doc['logged_fields']}", + f"- **Raw records kept:** {doc['raw_record_retention_days']} days; " + f"**summaries kept:** {doc['summary_retention_months']} months", + f"- **Records since:** {doc['logging_records_since'] or 'none yet'}", + f"- **Your own records:** {doc['party_records']}", + f"- **Own-records exercise (simulated):** {doc['ownRecordsExercise']['requester']} asked: " + f"\"{doc['ownRecordsExercise']['asks']}\" Synthetic check " + f"{doc['ownRecordsExercise']['syntheticCheck']['result']}; " + f"{doc['ownRecordsExercise']['matchesInRealRecords']} matching real record(s); delivered to " + f"{doc['ownRecordsExercise']['deliveredTo']}.", ""] + if not doc["months"]: + out += ["No access records yet.", ""] + for m in reversed(doc["months"]): + out += [f"## {m['month']}", "", + f"{m['requests']} requests, {m['coverage_from']} to {m['coverage_to']}. " + f"By status: {', '.join(f'{k} {v}' for k, v in m['status_classes'].items())}. " + f"By country: {', '.join(f'{k} {v}' for k, v in m['countries'].items())}.", "", + "| Artifact | Requests |", "|---|---|"] + for path, n in sorted(m["artifacts"].items(), key=lambda kv: (-kv[1], kv[0])): + out.append(f"| `{path}` | {n} |") + out.append("") + out += ["---", "_Source of truth: the signed `access-summary.json` (CDS-TRC-ACL)._"] + return "\n".join(out) + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + ap.add_argument("--records", required=True, help="directory of synced CloudFront access records") + ap.add_argument("--previous", default=None, help="the previously published access-summary.json") + ap.add_argument("--output", default="access-summary.json") + ap.add_argument("--md-output", default="access-summary.md") + a = ap.parse_args(argv) + previous = {} + if a.previous and Path(a.previous).exists(): + try: + previous = json.loads(Path(a.previous).read_text()) + except json.JSONDecodeError: + previous = {} + if previous and previous.get("artifact") != "access-summary": + previous = {} + now = datetime.now(timezone.utc) + doc = build(previous, read_records(a.records), now) + prev_months = {e["month"] for e in previous.get("months", [])} if previous else set() + # Never drop a month younger than the six FedRAMP requires. + newest = sorted(prev_months | {e["month"] for e in doc["months"]})[-MIN_MONTHS_KEPT:] + lost = sorted(set(newest) - {e["month"] for e in doc["months"]}) + if lost: + _fail(f"would drop month(s) {lost} younger than {MIN_MONTHS_KEPT} months") + doc = _offering.stamp_fedramp_id(doc) # CDS-CSO-FID + Path(a.output).write_text(json.dumps(doc, indent=2) + "\n") + if a.md_output: + Path(a.md_output).write_text(render_markdown(doc) + "\n") + print(f"access-summary: {len(doc['months'])} month(s); records since {doc['logging_records_since']}") + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/build-assessor-guide.py b/scripts/build-assessor-guide.py new file mode 100644 index 00000000..f6ab85f9 --- /dev/null +++ b/scripts/build-assessor-guide.py @@ -0,0 +1,169 @@ +#!/usr/bin/env python3 +"""The assessor guide: how to verify and validate each FedRAMP rule and KSI +here, by hand or by machine (IVV-CSO-STE, IVV-CSO-DUS). + +Generated from the rule records (data/frr-records.json) and the KSI catalog, so +it cannot describe a mechanism the records do not cite. For every rule it gives +the provider's explanation and, for every piece of evidence, the command that +reproduces the check and a machine-readable form of the same check. The +simulated assessor (tools/simulated-assessor/assess.py) executes exactly those +machine-readable checks on every deploy: the guide is the demonstration. + +It also states the sampling position (IVV-CSO-DUS): no check here uses a +representative sample. + + python3 scripts/build-assessor-guide.py --output assessor-guide.json --md-output assessor-guide.md +""" + +import argparse +import json +import sys +from datetime import datetime, timezone +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _freshness # noqa: E402 +import _frr # noqa: E402 +import _offering # noqa: E402 +import _rules # noqa: E402 +import _signers # noqa: E402 + +REPO = Path(__file__).resolve().parent.parent +SITE = "https://samaydlette.com" +REPO_URL = _signers.REPO_URL +ISSUER = _signers.ISSUER +# Every workflow that signs something published, from the one table of who +# writes what (scripts/_signers.py). The simulated assessor signs its own record +# under its own workflow identity. +IDENTITIES = dict(_signers.IDENTITIES) +SCHEMA = "assessor-guide/1" +SAMPLING = ("No representative samples are used in verification or validation (IVV-CSO-DUS). Every check runs " + "over its full population: the OPA gate and the KSI signal evaluate every inventoried component; the " + "reconciliation gate compares every live in-boundary resource with the inventory; the vulnerability " + "scan covers every SBOM; every FedRAMP rule record is validated and every test it cites runs on every " + "build; and the simulated assessor re-checks every rule and every KSI rather than a selection.") +HOW_TO_USE = ("Read each rule's explanation, then run the command beside each piece of evidence. Tests run from a " + "clone of the repository after `make dev-setup`; published artifacts are fetched from the site and " + "their signatures verified with cosign against the publishing workflow's identity; workflow steps " + "are read in the workflow file and their run logs in the repository's Actions tab; decision records " + "are in data/decisions.json. The `check` beside each command is the same check in machine-readable " + "form. For a walkthrough of any mechanism, ask through the security contact in the Certification " + "Package Overview.") + + +def _artifact_check(ref, fresh): + entry = fresh.get(ref) + if entry is None: + raise SystemExit(f"::error::assessor guide: {ref} is not in the freshness config, so an assessor could " + "not tell how fresh it must be (fail-closed)") + name = ref.split("/", 1)[1] + sig = entry.get("signature") + return {"url": f"{SITE}/{ref}", "bundle_url": f"{SITE}/{sig}" if sig else None, + "identities": _signers.signers(name), + "timestamp": entry["timestamp"], "max_age_hours": entry["max_age_hours"]} + + +def reproduce(ev, fresh): + kind, ref = ev["kind"], ev["ref"] + if kind == "test": + return f"python3 -m pytest '{ref}'", {"pytest": ref} + if kind == "step": + wf, step = ref.split("#", 1) + return (f"Read the step named {step!r} in .github/workflows/{wf}, and its log in the latest run of that " + "workflow on main", {"workflow": wf, "step": step}) + if kind == "artifact": + chk = _artifact_check(ref, fresh) + cmd = f"curl -fsSLO {chk['url']}" + if chk["bundle_url"]: + # One verification per workflow allowed to have signed it; any one passing is enough. + verify = " || ".join( + f"cosign verify-blob --bundle {chk['bundle_url'].rsplit('/', 1)[1]} " + f"--certificate-identity {IDENTITIES[i]} --certificate-oidc-issuer {ISSUER} {ref.rsplit('/', 1)[1]}" + for i in chk["identities"]) + cmd += f" && curl -fsSLO {chk['bundle_url']} && {{ {verify}; }}" + return cmd, {"artifact": chk} + if kind == "decision": + return f"jq '.decisions[] | select(.id == \"{ref}\")' data/decisions.json", {"decision": ref} + raise SystemExit(f"::error::assessor guide: unknown evidence kind {kind!r}") + + +def build(records, applicable, catalog, fresh, now, commit=None): + rules = [] + for r in records["records"]: + rid = r["frr_id"] + evidence = [] + for ev in r.get("evidence", []): + cmd, chk = reproduce(ev, fresh) + evidence.append({"kind": ev["kind"], "ref": ev["ref"], "how_to_reproduce": cmd, "check": chk}) + entry = {"rule_id": rid, "name": applicable[rid]["name"], "force": applicable[rid]["force"], + "statement": applicable[rid]["statement"], "status": r["status"], + "explanation": r["implementation"], "evidence": evidence} + for k in ("not_applicable", "may_rationale", "simulated"): + if k in r: + entry[k] = r[k] + rules.append(entry) + ksis = [{"ksi_id": i["id"], "name": i.get("name", ""), + "how_to_reproduce": (f"curl -fsSL {SITE}/.well-known/ksi-signal.json | jq '.ksis[] | " + f"select(.id == \"{i['id']}\")' after verifying ksi-signal.bundle against the " + "deploy identity; the SDR's keySecurityIndicators entry gives its measures"), + "check": {"ksi_in_signal": i["id"]}} + for f in catalog["KSI"].values() for i in f["indicators"]] + return {"schema": SCHEMA, "fedRampId": _offering.fedramp_id(), "generated_at": now.isoformat(), "commit": commit, "site": SITE, + "repository": REPO_URL, "how_to_use": HOW_TO_USE, "sampling": SAMPLING, + "identities": {**IDENTITIES, "oidc_issuer": ISSUER}, + "summary": {"rules": len(rules), "ksis": len(ksis), + "evidence_items": sum(len(r["evidence"]) for r in rules)}, + "rules": rules, "ksis": sorted(ksis, key=lambda k: k["ksi_id"])} + + +def render_markdown(g): + out = ["# Assessor guide", "", + "_How to verify and validate each FedRAMP rule and Key Security Indicator for this offering. Generated " + "from the rule records on every deploy; the simulated assessor runs these exact checks._", "", + f"- **Generated:** {g['generated_at']} | **Commit:** `{g['commit'] or 'local build'}`", + f"- **Rules:** {g['summary']['rules']} | **KSIs:** {g['summary']['ksis']} | " + f"**Evidence items:** {g['summary']['evidence_items']}", "", + "## How to use this guide", "", g["how_to_use"], "", + "## Sampling (IVV-CSO-DUS)", "", g["sampling"], "", + "## Signing identities", ""] + out += [f"- {k}: `{v}`" for k, v in g["identities"].items()] + out += ["", "## FedRAMP rules", ""] + for r in g["rules"]: + out += [f"### {r['rule_id']}: {r['name']} ({r['force']}, {r['status']})", "", r["explanation"], ""] + for k, label in (("not_applicable", "Not applicable"), ("may_rationale", "Use of this permission")): + if k in r: + out += [f"{label}: {r[k]}", ""] + if "simulated" in r: + out += [f"Simulated counterparty ({r['simulated']['counterparty']}): {r['simulated']['how']}", ""] + for ev in r["evidence"]: + out.append(f"- {ev['kind']} `{ev['ref']}`: `{ev['how_to_reproduce']}`") + if r["evidence"]: + out.append("") + out += ["## Key Security Indicators", ""] + out += [f"- `{k['ksi_id']}` {k['name']}: `{k['how_to_reproduce']}`" for k in g["ksis"]] + out += ["", "---", "_Source of truth: the signed `assessor-guide.json`._"] + return "\n".join(out) + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + ap.add_argument("--records", default=str(_frr.DEFAULT_PATH)) + ap.add_argument("--catalog", default=str(REPO / "infrastructure" / "schemas" / "ksi-catalog.json")) + ap.add_argument("--freshness", default=str(REPO / "infrastructure" / "schemas" / "freshness-config.json")) + ap.add_argument("--commit", default=None) + ap.add_argument("--output", default="assessor-guide.json") + ap.add_argument("--md-output", default="assessor-guide.md") + a = ap.parse_args(argv) + records = _frr.load(a.records) + fresh = {x["path"]: x for x in _freshness.load_freshness_config(a.freshness)["artifacts"]} + guide = build(records, _rules.applicable_provider_rules(), json.loads(Path(a.catalog).read_text()), fresh, + datetime.now(timezone.utc), a.commit) + Path(a.output).write_text(json.dumps(guide, indent=2) + "\n") + if a.md_output: + Path(a.md_output).write_text(render_markdown(guide) + "\n") + print(f"assessor-guide: {guide['summary']}") + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/build-availability.py b/scripts/build-availability.py index d020e9c8..e7f090a0 100644 --- a/scripts/build-availability.py +++ b/scripts/build-availability.py @@ -1,89 +1,147 @@ #!/usr/bin/env python3 # ============================================================================= -# AVAILABILITY FEED BUILDER (CR26 CDS-CSO-AVR) +# AVAILABILITY FEED BUILDER (CR26 CDS-CSO-AVR, CDS-TRC-USH) # ============================================================================= -# CR26 CDS-CSO-AVR (Class C MUST) requires a web service indicating current and -# historical availability of core services over at least the past 30 days, in -# both human-readable and machine-readable formats, available even if the primary -# offering is unavailable. This builds the machine + human feed as an append-only -# history: each deploy appends a datapoint to the previous published feed and -# trims to a rolling window. A deploy that produces this feed is, by definition, -# a successful one, so the current datapoint is "available". +# CDS-CSO-AVR (Class C MUST): a web service showing current and historical +# availability of core services over at least the past 30 days, including +# availability incidents, human- and machine-readable, and available even when +# the offering is not. # -# HONEST RESIDUAL: this feed is served from the same CloudFront/S3 path as the -# offering, so the "available even if the primary offering is unavailable" clause -# is only partially met — full conformance needs an independent monitor on -# separate infrastructure. That gap is stated in the feed itself, not hidden. +# The measurement is made outside AWS: scripts/availability-probe.py runs on +# GitHub Actions every 15 minutes and publishes its feed on GitHub (the +# repository's availability-status branch), which stays reachable when the +# offering's CloudFront or S3 is down. That is the service the rule asks for. # -# build-availability.py --previous previous-availability.json +# This builder republishes the same measurements on the site, signed with the +# rest of the certification data, so the package carries them: the deploy reads +# the independent feed (and fails when it is missing or stale), and this writes +# availability.json + availability.md from it: current status, 30-day +# availability and incidents per service, and a daily roll-up. It never records +# a deploy as availability. +# +# build-availability.py --probe-feed availability-probe.json --ksi-signal ksi-signal.json # ============================================================================= import argparse +import importlib.util import json import sys -from datetime import datetime, timezone +from collections import defaultdict +from datetime import datetime, timedelta, timezone from pathlib import Path -WINDOW_DAYS = 45 # keep >= 30 days of history per CDS-CSO-AVR +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _offering # noqa: E402 + +_spec = importlib.util.spec_from_file_location( + "availability_probe", Path(__file__).resolve().parent / "availability-probe.py") +assert _spec is not None and _spec.loader is not None +probe = importlib.util.module_from_spec(_spec) +_spec.loader.exec_module(probe) + +MAX_FEED_AGE_HOURS = 2.0 + + +def _fail(msg): + raise SystemExit(f"::error::availability: {msg} (fail-closed)") + +def daily(samples, now, days=probe.WINDOW_DAYS): + """[{date, services: {key: {probes, up}}}] for the past `days` days.""" + since = (now - timedelta(days=days)).date() + by_day = defaultdict(lambda: defaultdict(lambda: {"probes": 0, "up": 0})) + for s in samples: + d = probe._parse(s["t"]).date() + if d < since: + continue + for key in s.get("probed", []): + cell = by_day[d.isoformat()][key] + cell["probes"] += 1 + cell["up"] += 0 if key in s.get("fail", {}) else 1 + return [{"date": d, "services": {k: dict(v) for k, v in sorted(svcs.items())}} + for d, svcs in sorted(by_day.items())] -def main(): + +def build(feed, signal_id, now): + return { + "feed_type": "availability", + "fedRampId": _offering.fedramp_id(), + "rules": ["CDS-CSO-AVR", "CDS-TRC-USH"], + "emitted_at": now.isoformat(), + "ksi_signal_id": signal_id, + "measured_by": feed["monitor"], + "independent_service": feed["published_at"], + "independent_note": "This file is a signed copy carried in the certification package. The service " + "that stays available when the offering is down is the independent one above, " + "served by GitHub.", + "measured_at": feed["generated_at"], + "history_began": feed["history_began"], + "history_note": feed["history_note"], + "incident_rule": feed["incident_rule"], + "current": feed["current"], + "current_failures": feed["current_failures"], + "window_days": feed["window_days"], + "availability": feed["availability"], + "incidents": feed["incidents"], + "transient_failures": feed["transient_failures"], + "daily": daily(feed["samples"], now), + } + + +def render_markdown(doc): + out = ["# Service availability", "", + f"_Measured independently: {doc['measured_by']}_", "", + f"- **Last probe:** {doc['measured_at']} | **Emitted:** {doc['emitted_at']}", + f"- **Independent status page (available when this site is not):** {doc['independent_service']['human']}", + f"- **History began:** {doc['history_began']}. {doc['history_note']}", + f"- **Incident rule:** {doc['incident_rule']}", "", + "| Service | Now | Availability (30 days) | Probes |", "|---|---|---|---|"] + for key, a in doc["availability"].items(): + pct = "n/a" if a["availability_percent"] is None else f"{a['availability_percent']}%" + out.append(f"| {a['service']} | {doc['current'].get(key, 'n/a')} | {pct} | {a['probes']} |") + out += ["", "## Availability incidents (past 30 days)", ""] + if not doc["incidents"]: + out.append("None.") + else: + out += ["| Service | Start | End | Failed probes | Failing check |", "|---|---|---|---|---|"] + for i in reversed(doc["incidents"]): + out.append(f"| {i['service_name']} | {i['start']} | {i['end'] or 'ongoing'} | " + f"{i['failed_probes']} | {i['failing_check']} |") + out += ["", "## Daily (passing probes / probes)", "", "| Date | " + " | ".join(doc["availability"]) + " |", + "|---|" + "---|" * len(doc["availability"])] + for day in reversed(doc["daily"]): + cells = [] + for key in doc["availability"]: + c = day["services"].get(key) + cells.append(f"{c['up']}/{c['probes']}" if c else "—") + out.append(f"| {day['date']} | " + " | ".join(cells) + " |") + out += ["", "---", "_Source of truth: the signed `availability.json` (CDS-CSO-AVR)._"] + return "\n".join(out) + + +def main(argv=None): ap = argparse.ArgumentParser() - ap.add_argument("--previous", default=None, help="Previous published availability.json (for history)") + ap.add_argument("--probe-feed", required=True, + help="the independent monitor's availability-status.json, fetched from GitHub") ap.add_argument("--ksi-signal", default="ksi-signal.json") ap.add_argument("--output", default="availability.json") ap.add_argument("--md-output", default="availability.md") - a = ap.parse_args() + a = ap.parse_args(argv) now = datetime.now(timezone.utc) - today = now.date().isoformat() - - history = [] - if a.previous and Path(a.previous).exists(): - try: - history = json.loads(Path(a.previous).read_text()).get("history", []) or [] - except Exception: - history = [] - # Append today (idempotent: one datapoint per day). - history = [h for h in history if h.get("date") != today] - history.append({"date": today, "status": "available", - "detail": "deploy succeeded; core services served via CloudFront"}) - # Trim to the rolling window (keep the most recent WINDOW_DAYS dated points). - history = sorted(history, key=lambda h: h.get("date", ""))[-WINDOW_DAYS:] - + why = probe.check_fresh(a.probe_feed, MAX_FEED_AGE_HOURS, now) + if why: + _fail("; ".join(why)) + feed = json.loads(Path(a.probe_feed).read_text()) signal_id = None if Path(a.ksi_signal).exists(): signal_id = json.loads(Path(a.ksi_signal).read_text()).get("signal_id") - - up = sum(1 for h in history if h.get("status") == "available") - feed = { - "feed_type": "availability", - "rule": "CDS-CSO-AVR", - "emitted_at": now.isoformat(), - "ksi_signal_id": signal_id, - "current_status": "available", - "window_days": WINDOW_DAYS, - "history_points": len(history), - "uptime_observed": f"{up}/{len(history)} observed days available", - "residual": ("This feed is served from the same CloudFront/S3 path as the offering; " - "the CDS-CSO-AVR clause requiring availability reporting even when the " - "primary offering is unavailable is only partially met. Full conformance " - "requires an independent monitor on separate infrastructure."), - "history": history, - } - Path(a.output).write_text(json.dumps(feed, indent=2) + "\n") + doc = build(feed, signal_id, now) + Path(a.output).write_text(json.dumps(doc, indent=2) + "\n") if a.md_output: - out = ["# Service Availability", "", - f"- **Current status:** {feed['current_status']}", - f"- **Observed window:** {feed['uptime_observed']} (rolling {WINDOW_DAYS} days)", - f"- **Emitted:** {feed['emitted_at']}", "", - f"> {feed['residual']}", "", - "| Date | Status |", "|---|---|"] - for h in reversed(history): - out.append(f"| {h['date']} | {h['status']} |") - out += ["", "---", "_Source of truth: the machine-readable `availability.json` (CDS-CSO-AVR)._"] - Path(a.md_output).write_text("\n".join(out) + "\n") - print(f"availability: {len(history)} day(s) of history; current=available") + Path(a.md_output).write_text(render_markdown(doc) + "\n") + down = sorted(k for k, v in doc["current"].items() if v != "up") + print(f"availability: {len(doc['incidents'])} incident(s) in {doc['window_days']} days; down now: {down or 'none'}") return 0 diff --git a/scripts/build-boundary-graph.py b/scripts/build-boundary-graph.py index 61ccbfb4..241a165b 100644 --- a/scripts/build-boundary-graph.py +++ b/scripts/build-boundary-graph.py @@ -41,6 +41,7 @@ from typing import Any, Iterable sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _offering # noqa: E402 import _redact # noqa: E402 SCHEMA = "samaydlette-boundary-map/1" @@ -503,6 +504,7 @@ def load(path: str, required: bool = True) -> dict[str, Any] | None: load(a.offering, required=False) or {}, load(a.vdr, required=False), load(a.trust_root_plan, required=False), a.commit, now, ) + graph = _offering.stamp_fedramp_id(graph) # CDS-CSO-FID text = json.dumps(graph, indent=1, ensure_ascii=False) + "\n" check_redaction(text) Path(a.output).write_text(text) diff --git a/scripts/build-cds-overview.py b/scripts/build-cds-overview.py deleted file mode 100644 index 2adbc99e..00000000 --- a/scripts/build-cds-overview.py +++ /dev/null @@ -1,119 +0,0 @@ -#!/usr/bin/env python3 -# ============================================================================= -# CERTIFICATION OVERVIEW PACKAGE BUILDER (CR26 CDS) -# ============================================================================= -# CR26 Certification Data Sharing (CDS) requires a publicly-shared, machine- and -# human-readable certification-overview package (CDS-CSO-PUB) carrying fifteen -# fields, a detailed service list with security categories (CDS-CSO-SVC), and a -# FedRAMP ID in all certification data (CDS-CSO-FID; a placeholder until assigned -# for an unsponsored system). This generator assembles the package from operator- -# declared editorial values (data/cds/offering.json), the authoritative system -# categorization (data/system-profile.json), and the canonical inventory's -# signal_id, and emits JSON + human-readable markdown (consistency between the -# two is the CDS-CSO-CBF automation requirement). -# -# build-cds-overview.py --offering ../data/cds/offering.json \ -# --profile ../data/system-profile.json --ksi-signal ksi-signal.json -# ============================================================================= - -import argparse -import json -import sys -from datetime import datetime, timedelta, timezone -from pathlib import Path - -QUARTER_DAYS = 91 - - -def main(): - ap = argparse.ArgumentParser() - ap.add_argument("--offering", default="../data/cds/offering.json") - ap.add_argument("--profile", default="../data/system-profile.json") - ap.add_argument("--ksi-signal", default="ksi-signal.json") - ap.add_argument("--output", default="certification-overview-package.json") - ap.add_argument("--md-output", default="certification-overview-package.md") - a = ap.parse_args() - - now = datetime.now(timezone.utc) - off = json.loads(Path(a.offering).read_text()) - prof = json.loads(Path(a.profile).read_text()) - signal_id = None - if Path(a.ksi_signal).exists(): - signal_id = json.loads(Path(a.ksi_signal).read_text()).get("signal_id") - else: - print(f"::warning::ksi-signal not found at {a.ksi_signal}", file=sys.stderr) - next_ocr = (now + timedelta(days=QUARTER_DAYS)).date().isoformat() - - pkg = { - "package_type": "certification-overview-package", - "schema": "fedramp-certification-overview-package-schema-2026-06-24.json", - "emitted_at": now.isoformat(), - "ksi_signal_id": signal_id, - # The 15 CDS-CSO-PUB fields: - "fedramp_id": off["fedramp_id"], # 1 (CDS-CSO-FID) - "service_model": off["service_model"], # 2 - "deployment_model": off["deployment_model"], # 3 - "business_category": off["business_category"], # 4 - "uei": off["uei"], # 5 - "sales_contact": off["sales_contact"], # 6 - "security_contact": off["security_contact"], # 7 - "product_website": off["product_website"], # 8 - "logo_url": off["logo_url"], # 9 - "service_description": off["service_description"], # 10 - "services": off["services"], # 11 (CDS-CSO-SVC) - "secure_configuration_guidance_url": off["secure_configuration_guidance_url"], # 12 - "documentation_overview_url": off["documentation_overview_url"], # 13 - "next_ongoing_certification_report_date": next_ocr, # 14 (CCM-OCR-NRD) - "current_independent_assessment_service": off["current_independent_assessment_service"], # 15 - # Authoritative categorization (single source of truth). - "class": prof.get("fedramp_class"), - "impact_level": prof.get("impact_level"), - "impact_level_canonical": prof.get("impact_level_canonical"), - # Honest residuals for the trust-center subset (no sponsor). - "trust_center_status": ( - "N/A absent a consuming agency. CDS-TRC-* (FedRAMP-compatible trust center, " - "programmatic access, access logging, agency-access inventory) and CDS-UTC-* " - "presuppose authorized agency consumers; with none, those are not exercised. " - "All certification data here is instead shared fully publicly under CDS-CSO-PUB."), - } - Path(a.output).write_text(json.dumps(pkg, indent=2) + "\n") - if a.md_output: - Path(a.md_output).write_text(render_markdown(pkg) + "\n") - print(f"certification-overview-package: {len(pkg['services'])} services; " - f"FedRAMP ID {pkg['fedramp_id'][:24]}...; next OCR {next_ocr}") - return 0 - - -def render_markdown(p): - out = ["# Certification Overview Package", ""] - out.append(f"- **Class:** {p['class']} | **Impact:** {p['impact_level_canonical']}") - out.append(f"- **FedRAMP ID:** {p['fedramp_id']}") - out.append(f"- **UEI:** {p['uei']}") - out.append(f"- **Service / Deployment model:** {p['service_model']} / {p['deployment_model']}") - out.append(f"- **Business category:** {p['business_category']}") - out.append(f"- **Product website:** {p['product_website']}") - sc = p["security_contact"] - out.append(f"- **Security contact:** {sc.get('name')} ({sc.get('email')})") - out.append(f"- **Sales contact:** {p['sales_contact'].get('name')} ({p['sales_contact'].get('url')})") - out.append(f"- **Secure Configuration Guidance:** {p['secure_configuration_guidance_url']}") - out.append(f"- **Documentation overview:** {p['documentation_overview_url']}") - out.append(f"- **Independent assessment service:** {p['current_independent_assessment_service']}") - out.append(f"- **Next Ongoing Certification Report:** {p['next_ongoing_certification_report_date']}") - out.append(f"- **Bound to inventory signal:** `{p['ksi_signal_id']}`") - out += ["", "## Service description", "", p["service_description"]] - out += ["", "## Services (CDS-CSO-SVC)", "", - "| Service | Security category | In MAS scope | Description |", - "|---|---|---|---|"] - for s in p["services"]: - out.append("| {n} | {c} | {m} | {d} |".format( - n=s.get("name", ""), c=s.get("security_category", ""), - m="yes" if s.get("in_mas_scope") else "no", - d=(s.get("description", "") or "").replace("|", "\\|"))) - out += ["", "## Trust-center status", "", p["trust_center_status"]] - out += ["", "---", "_Source of truth: the signed `certification-overview-package.json` " - "(CDS-CSO-PUB / SVC / FID)._"] - return "\n".join(out) - - -if __name__ == "__main__": - sys.exit(main()) diff --git a/scripts/build-cmmc.py b/scripts/build-cmmc.py deleted file mode 100644 index f6871311..00000000 --- a/scripts/build-cmmc.py +++ /dev/null @@ -1,189 +0,0 @@ -#!/usr/bin/env python3 -# ============================================================================= -# CMMC PROJECTION (Phase 2 / CMMC) -# ============================================================================= -# Projects the 800-53 Rev5 hub through the composed mapping -# CMMC req (171 Rev2) ->(171->53r4)-> 53 Rev4 ->(Rev4->Rev5)-> Rev5 hub -# to a CMMC Level 2 coverage view: per-requirement responsibility, the coverage -# stack, the inheritable fraction (the ~53/110 sensor), and residue. -# -# Aggregation is CONSERVATIVE MERGE: a requirement is "fully-inherited" only if -# EVERY mapped hub control is inherited; any provider/shared part downgrades it -# to partially-inherited. Never overclaim inheritance. -# -# Usage: build-cmmc.py [--ksi-signal PATH] [--catalog PATH] [--output COVERAGE.json] -# (the Rev5 hub is the control projection, scripts/_controls.py) -# ============================================================================= - -import argparse -import json -import os -import sys -from collections import Counter -from pathlib import Path - -# Shared generator helpers. The insert is __file__-relative, so this script stays -# runnable standalone from any working directory (see scripts/_common.py). -sys.path.insert(0, os.path.dirname(os.path.abspath(__file__))) -from _common import classify, load_hub # noqa: E402 -import _controls # noqa: E402 - -REPO = Path(__file__).resolve().parent.parent - - -def load_171_53(): - doc = json.loads((REPO / "data/mappings/SP800-171r2-to-SP800-53r4.mapping.json").read_text())["mapping-collection"] - out = {} - for m in doc["mappings"][0]["maps"]: - out.setdefault(m["sources"][0]["id-ref"], []).append(m["targets"][0]["id-ref"]) - return out - - -def load_rev4_rev5(): - doc = json.loads((REPO / "data/mappings/SP800-53_rev4-to-rev5.mapping.json").read_text())["mapping-collection"] - return {m["sources"][0]["id-ref"]: m["targets"][0]["id-ref"] for m in doc["mappings"][0]["maps"]} - - -def load_catalog_reqs(): - cat = json.loads((REPO / "data/catalogs/NIST_SP-800-171_rev2_catalog.json").read_text())["catalog"] - return [c["id"] for g in cat["groups"] for c in g["controls"]] - - -def aggregate(classes): - """Conservative merge of the mapped hub controls' responsibility classes.""" - non_na = classes - {"not-applicable"} - if not non_na: - return "not-applicable" - if non_na == {"fully-inherited"}: - return "fully-inherited" - if non_na & {"fully-inherited", "partially-inherited"}: - return "partially-inherited" # some inheritance but not all -> partial (conservative) - return "implemented" - - -def srm_class(status, origination): - """A consuming OSC's SRM/inheritance view of a CSP-provided control. - The provider's N-A (e.g. no end-users) is NOT the OSC's N-A: it means the - CSP does not provide it, so the OSC must -> osc-responsibility.""" - if status in ("not-applicable", "planned"): - return "osc-responsibility" - if origination in ("inherited", "sp-system"): - return "inherited" # AWS-via-CSP or the CSP's system provides it - if origination in ("shared", "sp-corporate"): - return "shared" # CSP provides a portion / the policy framework - return "osc-responsibility" - - -def aggregate_srm(classes): - if classes == {"inherited"}: - return "inherited" # OSC inherits fully only if EVERY part is provided - if classes == {"osc-responsibility"}: - return "osc-responsibility" - return "shared" # any mix -> shared - - -def guard_no_vacuous_inheritance(req, cls, srm, hub_controls): - """A requirement with NO backing hub control must never be reported as fully - inherited or implemented. Doing so tells a consuming organization the CSP - fully provides an obligation it does not -- e.g. 3.12.4 (maintain your own - SSP), which 800-171 Table D-1 maps to no 800-53 control. Empty hub_controls - may only be customer-responsibility / not-applicable / residue. Raise loudly - so a crosswalk gap can never silently chain into a false inheritance claim.""" - if not hub_controls and (cls in ("fully-inherited", "implemented") or srm == "inherited"): - raise ValueError( - f"vacuous inheritance for {req}: class={cls!r} srm={srm!r} with no hub controls; " - "an unmapped requirement cannot be fully inherited/implemented") - - -def main(): - ap = argparse.ArgumentParser() - ap.add_argument("--ksi-signal", default=str(_controls.DEFAULT_SIGNAL)) - ap.add_argument("--catalog", default=str(_controls.DEFAULT_CATALOG)) - ap.add_argument("--output", default=None) - a = ap.parse_args() - - reqs = load_catalog_reqs() - m171 = load_171_53() - r45 = load_rev4_rev5() - hub = load_hub(_controls.load(a.ksi_signal, a.catalog)) - disp = json.loads((REPO / "data/dispositions/beyond-moderate.json").read_text()) - for c, d in disp["controls"].items(): # beyond-Moderate dispositions extend the hub - hub[c] = (d["status"], d["origination"]) - cmmc_disp = disp.get("cmmc_requirement_dispositions", {}) - - stack = Counter() - srm_stack = Counter() - residue = [] - per_req = {} - for req in reqs: - if req in cmmc_disp: # dispositioned at the requirement level (e.g. SSP) - d = cmmc_disp[req] - cls = d.get("class", "customer-responsibility") - srm = d.get("srm", "osc-responsibility") - guard_no_vacuous_inheritance(req, cls, srm, hub_controls=[]) - stack[cls] += 1 - srm_stack[srm] += 1 - per_req[req] = {"class": cls, "srm": srm, "hub_controls": []} - continue - r4 = m171.get(req, []) - if not r4: - residue.append((req, "no 800-53 mapping (CMMC-specific control)")) - continue - r5 = sorted({r45.get(c, c) for c in r4}) # compose r4 -> r5 (default same-id) - impls = [hub[c] for c in r5 if c in hub] - if not impls: - residue.append((req, f"hub does not address {r5}")) - continue - cls = aggregate({classify(s, o) for (s, o) in impls}) - srm = aggregate_srm({srm_class(s, o) for (s, o) in impls}) - guard_no_vacuous_inheritance(req, cls, srm, hub_controls=r5) - stack[cls] += 1 - srm_stack[srm] += 1 - per_req[req] = {"class": cls, "srm": srm, "hub_controls": r5} - - total = len(reqs) - inh_full = stack["fully-inherited"] - inh_part = stack["partially-inherited"] - cov = { - "framework": "CMMC Level 2 (NIST SP 800-171 Rev2, 110 requirements)", - "in_scope_requirements": total, - "coverage": {"determined": total - len(residue), "residue": len(residue), - "determined_pct": round(100.0 * (total - len(residue)) / total, 1)}, - "responsibility_stack": dict(stack), - "inheritable": {"fully_inherited": inh_full, "partially_inherited": inh_part, - "inheritance_touched": inh_full + inh_part, - "fraction": f"{inh_full + inh_part}/110"}, - "srm_view": dict(srm_stack), - "srm_inheritable": {"inherited": srm_stack["inherited"], "shared": srm_stack["shared"], - "osc_responsibility": srm_stack["osc-responsibility"], - "inheritable_fraction": f"{srm_stack['inherited'] + srm_stack['shared']}/110"}, - "residue": [{"req": r, "reason": why} for r, why in residue], - "per_requirement": per_req, - } - if a.output: - Path(a.output).write_text(json.dumps(cov, indent=2) + "\n") - - import sys - print("=== CMMC Level 2 coverage (projected from the 800-53 Rev5 hub) ===", file=sys.stderr) - print(f" in-scope requirements: {total}", file=sys.stderr) - print(f" determined: {cov['coverage']['determined']}/{total} " - f"({cov['coverage']['determined_pct']}%) | residue: {len(residue)}", file=sys.stderr) - for k in ["implemented", "partially-inherited", "fully-inherited", "customer-responsibility", "planned", "not-applicable"]: - if stack[k]: - print(f" {stack[k]:4} {k}", file=sys.stderr) - print(f" [provider SSP view] inheritance-touched: {inh_full + inh_part}/110 " - f"({inh_full} full + {inh_part} partial)", file=sys.stderr) - print("\n === CMMC SRM (OSC view) — what a consuming OSC inherits ===", file=sys.stderr) - print(f" {srm_stack['inherited']:4} inherited (CSP provides fully)", file=sys.stderr) - print(f" {srm_stack['shared']:4} shared", file=sys.stderr) - print(f" {srm_stack['osc-responsibility']:4} OSC responsibility", file=sys.stderr) - print(f" {len(residue):4} residue", file=sys.stderr) - print(f" OSC INHERITS from this CSO: {srm_stack['inherited'] + srm_stack['shared']}/110 " - f"({srm_stack['inherited']} fully + {srm_stack['shared']} shared) <- the ~53/110 SRM sensor", - file=sys.stderr) - if residue: - print(f" residue ({len(residue)}): {[r for r,_ in residue]}", file=sys.stderr) - - -if __name__ == "__main__": - main() diff --git a/scripts/build-conformance.py b/scripts/build-conformance.py index 06c0c561..44bc9ca2 100644 --- a/scripts/build-conformance.py +++ b/scripts/build-conformance.py @@ -31,6 +31,9 @@ from datetime import datetime, timezone from pathlib import Path +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _offering # noqa: E402 + REPO = Path(__file__).resolve().parent.parent DEFAULT_PROFILE = REPO / "data" / "method-profile.json" IDS = [f"T{i}" for i in range(1, 75)] @@ -149,6 +152,7 @@ def main(argv=None): doc, missing = build(profile, outcome, args.commit, datetime.now(timezone.utc)) if missing: _fail(f"mapped tests that pytest did not run: {missing}") + doc = _offering.stamp_fedramp_id(doc) # CDS-CSO-FID Path(args.output).write_text(json.dumps(doc, indent=2) + "\n") s = doc["summary"] print(f"conformance ({doc['profile_version']}): {s['implemented']} implemented, {s['partial']} partial, " diff --git a/scripts/build-coverage.py b/scripts/build-coverage.py deleted file mode 100644 index 31b3bb70..00000000 --- a/scripts/build-coverage.py +++ /dev/null @@ -1,90 +0,0 @@ -#!/usr/bin/env python3 -# ============================================================================= -# COVERAGE STACK (Phase 2 / A2 — spoke output contract) -# ============================================================================= -# Rolls up the control projection's authored per-control responsibility -# classification (scripts/_controls.py) into a coverage stack + inheritable -# fraction. Coverage is NOT a derived score: it is the histogram of the -# control-origination/implementation-status that each control already carries. The responsibility classes use FedRAMP's -# authoritative control-origination vocabulary under plain-language labels. -# -# Deliberately does NOT report an "automation depth" / machine-evidence metric — -# that conflates evidence quality with coverage and was dropped by design. -# -# coverage % = determined (every control has a class) = 100% by construction -# inheritable fraction = fully-inherited + partially-inherited (the ~53/110 -# analog for CMMC) -# -# Usage: build-coverage.py [--ksi-signal PATH] [--catalog PATH] [--framework NAME] [--output PATH] -# ============================================================================= - -import argparse -import json -import os -import sys -from collections import Counter - -# Shared generator helpers. The insert is __file__-relative, so this script stays -# runnable standalone from any working directory (see scripts/_common.py). -sys.path.insert(0, os.path.dirname(os.path.abspath(__file__))) -from _common import classify, prop # noqa: E402 -import _controls # noqa: E402 - -# FedRAMP control-origination + implementation-status -> responsibility class -CLASSES = ["implemented", "partially-inherited", "fully-inherited", - "customer-responsibility", "planned", "not-applicable"] - - -def build_coverage(irs, framework): - hist = Counter() - for ir in irs: - hist[classify(prop(ir, "implementation-status"), - prop(ir, "control-origination"))] += 1 - total = len(irs) - inherit_full = hist["fully-inherited"] - inherit_part = hist["partially-inherited"] - return { - "framework": framework, - "in_scope_controls": total, - "coverage": { - "determined": total, - "determined_pct": round(100.0 * total / total, 1) if total else 0.0, - }, - "responsibility_stack": {c: hist[c] for c in CLASSES}, - "inheritable": { - "fully_inherited": inherit_full, - "partially_inherited": inherit_part, - "inheritance_touched": inherit_full + inherit_part, - "fraction_of_baseline": round((inherit_full + inherit_part) / total, 3) if total else 0.0, - }, - } - - -def main(): - ap = argparse.ArgumentParser() - ap.add_argument("--ksi-signal", default=str(_controls.DEFAULT_SIGNAL)) - ap.add_argument("--catalog", default=str(_controls.DEFAULT_CATALOG)) - ap.add_argument("--framework", default="FedRAMP Rev5 Moderate") - ap.add_argument("--output", default=None) - a = ap.parse_args() - cov = build_coverage(_controls.load(a.ksi_signal, a.catalog), a.framework) - out = json.dumps(cov, indent=2) - if a.output: - open(a.output, "w").write(out + "\n") - # human-readable summary to stderr - print(f"=== coverage: {cov['framework']} ({cov['in_scope_controls']} in-scope) ===", file=sys.stderr) - print(f" coverage (determined): {cov['coverage']['determined_pct']}%", file=sys.stderr) - for c in CLASSES: - n = cov["responsibility_stack"][c] - if n: - print(f" {n:4} {c}", file=sys.stderr) - inh = cov["inheritable"] - print(f" inheritable: {inh['inheritance_touched']} controls " - f"({inh['fully_inherited']} full + {inh['partially_inherited']} partial) " - f"= {inh['fraction_of_baseline']*100:.1f}% of baseline", file=sys.stderr) - if not a.output: - print(out) - - -if __name__ == "__main__": - main() diff --git a/scripts/build-cpo.py b/scripts/build-cpo.py index 732986d3..8333282b 100644 --- a/scripts/build-cpo.py +++ b/scripts/build-cpo.py @@ -1,22 +1,37 @@ #!/usr/bin/env python3 # ============================================================================= -# CERTIFICATION PACKAGE OVERVIEW BUILDER (CR26 CPO) +# CERTIFICATION PACKAGE OVERVIEW BUILDER (CR26 CPO, FedRAMP's 2026-06-24 schema) # ============================================================================= -# CR26 CPO-CSO-OVR (MUST) requires a Certification Package Overview, human- and -# machine-readable, that rolls up the CDS public information, the Minimum -# Assessment Scope, the cryptographic-module use (CMU-CSO-CMD), and the -# independent-assessment results (IVV-CSO-ICP). CPO-CSO-MTD requires the name, -# title, and contact of the accountable official plus version/timestamp/source. -# CPO-CSX-CPM (Class C) requires the package be maintained at least every two -# weeks — trivially met by the per-deploy pipeline. Together with the Security -# Decision Record, the CPO is CR26's replacement for the base System Security -# Plan; the OSCAL SSP that used to be published alongside is retired. +# CPO-CSO-OVR: the overview of the offering, in both JSON and human-readable +# form, with what CPO-CSO-MTD, CDS-CSO-PUB and CDS-CSO-SVC require. It folds in +# what scripts/build-cds-overview.py used to publish separately (the CDS +# certification-overview package), so the public information has one source. # -# This is an overview/manifest: it points at the constituent artifacts the -# pipeline already publishes and summarizes scope, crypto, and assessment status. +# serviceIdentification provider, service, FedRAMP ID (FedRAMP's fallback: +# the provider name and acronym, marked as not real), +# a simulated UEI, website, logo (CDS-CSO-PUB, FID) +# serviceProperties service and deployment model, business category, +# the package's repositories, and the next report date +# from the fixed CCM calendar (CCM-OCR-NRD) +# contactInformation security, sales and accountable official; never an +# email address (they point to security.txt) +# certifiedServices each service, with its own security category +# under providerExtensions.services (CDS-CSO-SVC) +# metadata version (semver on a content hash), lastUpdated, +# updateSource, accountable official (CPO-CSO-MTD) +# +# serviceProperties.trustCenter / .secureConfigurationGuidance, the +# thirdPartyInformationResources and the assessor's overall summary under +# providerExtensions.independentAssessment: one small function each +# (CDS-CSO-PUB/UTC, SCG-CSO-AUP, MAS-CSO-TPR, CPO-CSO-OSA). +# +# Simulated values are flagged under providerExtensions.simulated, naming the +# outside party they stand in for. Each top-level section is one small function, +# so a field can be added without touching the others. Validated against the +# vendored schema before it is written; nothing that fails is written. # # build-cpo.py --offering ../data/cds/offering.json --profile ../data/system-profile.json \ -# --overview certification-overview-package.json --ksi-signal ksi-signal.json +# --ksi-signal ksi-signal.json --previous-cpo previous-cpo.json # ============================================================================= import argparse @@ -25,121 +40,411 @@ from datetime import datetime, timezone from pathlib import Path -# The certification-package artifacts the pipeline publishes under /.well-known/. -# (artifact filename, type, signed) -PACKAGE_CONTENTS = [ - ("security-decision-record.json", - "Security Decision Record (SDR: per-KSI and per-Rev5-control records; replaces the SSP)", True), - ("ksi-signal.json", "FedRAMP 20x KSI signal (canonical inventory)", True), - ("vdr-report.json", "Vulnerability Detection and Response report", True), - ("ongoing-certification-report.json", "Ongoing Certification Report (CCM)", True), - ("certification-overview-package.json", "CDS certification-overview package", True), - ("availability.json", "Availability feed (CDS-CSO-AVR)", True), - ("policy-index.json", "Policy and procedure index (CDS-CSO-IRP)", True), - ("iiw.csv", "FedRAMP Integrated Inventory Workbook (Appendix M)", True), -] +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _assessor # noqa: E402 +import _ccm # noqa: E402 +import _engagement # noqa: E402 +import _fedramp_schema as fs # noqa: E402 +import _offering # noqa: E402 +import _tpr # noqa: E402 + +REPO = Path(__file__).resolve().parent.parent +BOUNDARY = REPO / "docs" / "boundary" / "boundary-classification.json" BASE = "https://samaydlette.com/.well-known/" +LEVELS = ("low", "moderate", "high") + +# The certification package (FRC-CSO-PKG) as the deploy publishes it. +# (file, repository types, description) +PACKAGE = [ + ("security-decision-record.json", ["Security Decision Record"], + "Every applicable FedRAMP rule, KSI and Rev5 Moderate control, with implementation, validation and " + "assessment (SDR-CSO-FRR; replaces the SSP)."), + ("ongoing-certification-report.json", ["Ongoing Certification Report"], + "The Ongoing Certification Report as it stands since the latest issue (CCM-OCR-AVL)."), + ("ocr-issues.json", ["Ongoing Certification Report", "Historical Certification Data"], + "Every issued Ongoing Certification Report, frozen and signed, with the snapshot of the certification " + "data taken at each issue (CDS-CSO-HAD)."), + ("quarterly-review.ics", ["Quarterly Review"], "Calendar file for the Quarterly Reviews (CCM-QTR-REG)."), + ("vdr-detail-report.json", ["Vulnerability Detail Report"], "Vulnerability detail (VER-RPT-VDT)."), + ("vdr-accepted-vulnerabilities.json", ["Accepted Vulnerability Info"], "Accepted vulnerabilities (VER-RPT-AVI)."), + ("vdr-history.json", ["Historical Vulnerability Activity"], "Vulnerability history (VER-TFR-MRH)."), + ("ksi-signal.json", ["Key Security Indicators"], "The canonical inventory and per-KSI results (MAS-CSO-IIR)."), + ("boundary-map.json", ["Minimum Assessment Scope"], "The generated authorization boundary map and data flows."), + ("policy-index.json", ["Policies and Procedures"], "Policy and procedure index (CDS-CSO-IRP)."), + ("availability.json", ["Availability"], "Availability feed."), + ("fedramp-certification-reports.json", ["FedRAMP Certification Reports"], + "FedRAMP Certification Reports received, published unmodified (CDS-CSO-FRC). Simulated: see the file."), + ("package-submission-log.json", ["Package Submission"], + "Log of each submission of this package to FedRAMP (FRC-CSO-PKG). Simulated: nothing is sent."), + ("significant-change-notifications.json", ["Significant Change Notifications"], + "Every Significant Change Notification, each in FedRAMP's SCN schema (SCN-CSO-HIS, SCN-CSO-HRM)."), + ("significant-change-notifications.atom", ["Significant Change Notifications"], + "Atom feed of the notifications (SCN-CSO-NOM)."), + ("scn-evaluations.json", ["Significant Change Notifications"], + "Significant-change evaluation log, append-only (SCN-CSO-MAR)."), + ("incident-reports.json", ["Incident Reports"], + "Incident log and reports in FedRAMP's incident report schema (IEC); exercises are marked as exercises."), + ("fedramp-inbox-simulation.json", ["FedRAMP Security Inbox"], + "The FedRAMP Security Inbox logic run over synthetic messages (AFC-CSO-INB). Simulated: no mail is " + "received or sent."), +] + +# SCN-CSO-NOM / SCN-CSO-MAR / SCN-CSO-HRM: how notifications are given and how +# the records are obtained; scripts/build-scn.py publishes the same statement. +SCN_NOTIFICATION = { + "mechanisms": [ + {"mechanism": "Atom feed", "url": BASE + "significant-change-notifications.atom"}, + {"mechanism": "Signed JSON index", "url": BASE + "significant-change-notifications.json"}, + {"mechanism": "Human-readable view", "url": BASE + "significant-change-notifications.md"}, + ], + "method": "Notification is publication: each notice is an update to the Certification Data at the URLs " + "above, dated when first published. Nothing is sent by email or to FedRAMP directly.", + "evaluation_records": BASE + "scn-evaluations.json", + "access": "Public; no request needed. Everything is published to everyone (no federal data, no agency " + "customer).", + "emergency_procedure": "https://github.com/sam-aydlette/samaydlette.com/blob/main/docs/incident-response.md" + "#emergency-change-procedure-cr26-scn-cso-emg", +} + + +def _fsi(off): + """The FedRAMP Security Inbox as published. The inbox is simulated for this + proof of concept, so this is a contact statement, never an email address, + plus the simulation's published results. The change history stays in the + repository.""" + fsi = off.get("fedramp_security_inbox") + if not fsi: + return None + return {"simulated": True, "contact": fsi["contact"], "rule": "AFC-CSO-INB", + "simulation": fsi.get("simulation"), "runbook": fsi.get("runbook")} + + +def _fail(msg): + raise SystemExit(f"::error::CPO: {msg} (fail-closed)") + + +# --- sections ------------------------------------------------------------------------ + +def service_identification(off): + return {"providerName": off["provider_name"], "serviceName": off["service_name"], + "serviceAcronym": off["service_acronym"], "serviceDescription": off["service_description"], + "certificationType": "20x", # FRC-CSO-POP: one program, 20x + "fedRampPackageId": off["fedramp_id"], "ueiNumber": off["uei"], + "website": off["product_website"], "logo": off["logo_url"]} + + +def repositories(): + return [{"repositoryType": types, "url": BASE + f, "repositoryDescription": desc, + "authenticationRequired": False} for f, types, desc in PACKAGE] + + +# --- trust center, scope and assessor fields: one small function each --------------- + +TRUST_CENTER = "https://samaydlette.com/trust/index.html" + + +def trust_center(): + """serviceProperties.trustCenter (CDS-CSO-PUB, CDS-CSO-UTC): the landing + page, with how to access what it holds.""" + return {"repositoryType": ["Trust Center", "Assessment Reports", "Policies and Procedures"], + "url": TRUST_CENTER, + "repositoryDescription": "The FedRAMP-compatible trust center: every piece of certification data, " + "indexed by the signed trust manifest (" + BASE + "trust-manifest.json).", + "authenticationRequired": False, + "accessRequestInstructions": "No access request is needed: everything is public. Fetch any artifact " + "with an HTTPS GET; the trust manifest lists each one with its signature " + "and signer. " + _engagement.SHORT} + + +def secure_configuration_guidance(): + """serviceProperties.secureConfigurationGuidance (SCG-CSO-RSC/AUP).""" + return {"repositoryType": ["Secure Configuration Guidance"], + "url": BASE + "secure-configuration-guide.md", + "repositoryDescription": "The Secure Configuration Guide: how to obtain, use and change the " + "security-relevant settings, with recommended defaults. Machine-readable and " + "signed: " + BASE + "secure-configuration-guide.json.", + "authenticationRequired": False} + + +def third_party_information_resources(): + """thirdPartyInformationResources (MAS-CSO-TPR), from the decided records.""" + return _tpr.cpo_third_party_information_resources() + + +def independent_assessment(off, assessment): + """providerExtensions.independentAssessment (CPO-CSO-OSA, CDS-CSO-PUB): the + current service, and the assessor's overall summary (IVV-IAS-OSA) carried + verbatim from its signed set. The schema's `assessor` object needs a + FedRAMP assessor ID; the simulated assessor has none, so it is left out + rather than given an ID-shaped value.""" + summary = _assessor.overall_summary(assessment) + if summary is None: + _fail("the assessment carries no overall summary (CPO-CSO-OSA)") + return {"currentService": off.get("current_independent_assessment_service"), + "overallSummary": summary, + "assessmentSet": BASE + "simulated-assessment.json", + "simulated": True} + + +ASSESSMENT_REPOSITORIES = [ + ("simulated-assessment.json", ["Assessment Reports"], + "The simulated assessor's signed results for every rule and KSI, with its overall summary (IVV-CSO-ICP). " + "Simulated: not a FedRAMP independent assessment."), + ("assessor-guide.json", ["Assessment Reports"], "How to verify and validate each rule and KSI (IVV-CSO-STE)."), + ("minimum-assessment-scope.json", ["Minimum Assessment Scope"], + "Information resources, flows and third parties in scope (MAS-CSO-IIR/FLO/TPR)."), + ("trust-manifest.json", ["Trust Center"], "Signed index of all certification data (CDS-TRC-PAC)."), +] + +def service_properties(off, dates): + return {"serviceType": off["service_model"], "deploymentModel": off["deployment_model"], + "businessCategory": off["business_category"], + "trustCenter": trust_center(), + "secureConfigurationGuidance": secure_configuration_guidance(), + "additionalRepositories": repositories() + [ + {"repositoryType": t, "url": BASE + f, "repositoryDescription": d, "authenticationRequired": False} + for f, t, d in ASSESSMENT_REPOSITORIES], + "nextOngoingCertificationReportDate": dates["nextOngoingCertificationReportDate"]} -def main(): + +def contacts(off): + """Security and Sales (the schema requires both), the accountable official, + and the FedRAMP Security Inbox when the offering declares one. A contact + that is not an email address is never put in the email field.""" + ao = off["accountable_official"] + out = [{"contactType": "Security", "contactName": off["security_contact"]["name"]}, + {"contactType": "Sales", "contactName": off["sales_contact"]["name"]}, + {"contactType": "Accountable Official", + "contactName": f"{ao['name']}, {ao['title']} (contact: {ao['contact']})"}] + fsi = off.get("fedramp_security_inbox") + if isinstance(fsi, dict): + entry = {"contactType": "FedRAMP Security Inbox"} + addr = fsi.get("address") + if isinstance(addr, str) and fs._EMAIL_RE.match(addr) and "/" not in addr: + entry["contactName"] = "FedRAMP Security Inbox" + entry["contactEmail"] = addr + else: + entry["contactName"] = fsi.get("contact") or "FedRAMP Security Inbox" + out.append(entry) + return out + + +def certified_services(off): + return [{"serviceName": s["name"], "serviceDescription": s["description"], + **({"dateAvailable": s["date_available"]} if s.get("date_available") else {})} + for s in off["services"]] + + +def services_detail(off, prof, groups): + """CDS-CSO-SVC: each service's own FIPS 199 category (never above the + system's), the boundary groups it is made of, and what is not included.""" + sysfips = prof.get("fips_199") or {} + out = [] + for s in off["services"]: + cat = s.get("security_category") + if not isinstance(cat, dict): + _fail(f"service {s.get('name')!r} has no per-service security category") + for obj in ("confidentiality", "integrity", "availability"): + v = cat.get(obj) + if v not in LEVELS: + _fail(f"service {s['name']!r}: {obj} {v!r} is not one of {LEVELS}") + if sysfips.get(obj) in LEVELS and LEVELS.index(v) > LEVELS.index(sysfips[obj]): + _fail(f"service {s['name']!r}: {obj} {v} exceeds the system's {sysfips[obj]}") + unknown = sorted(set(s.get("boundary_groups") or []) - groups) + if not s.get("boundary_groups") or unknown: + _fail(f"service {s['name']!r}: boundary groups {unknown or 'none'} are not in the boundary classification") + hw = max((cat[o] for o in ("confidentiality", "integrity", "availability")), key=LEVELS.index) + out.append({"serviceName": s["name"], "securityCategory": { + "confidentiality": cat["confidentiality"], "integrity": cat["integrity"], + "availability": cat["availability"], "highWaterMark": hw, "rationale": cat.get("rationale", "")}, + "boundaryGroups": s["boundary_groups"], "inMinimumAssessmentScope": bool(s.get("in_mas_scope"))}) + return out + + +def simulated(off): + """The values that stand in for an outside party, and which party.""" + return [{"field": "serviceIdentification.fedRampPackageId", "counterparty": "fedramp", + "how": off["fedramp_id_simulated"]}, + {"field": "serviceIdentification.ueiNumber", "counterparty": "sam-gov", "how": off["uei_simulated"]}, + {"field": "providerExtensions.independentAssessment.overallSummary", "counterparty": "assessor", + "how": "Written and signed on every deploy by Totally Real Assessment Services, LLC (simulated), a " + "workflow in this repository; not a FedRAMP Recognized assessment service."}] + + +def provider_extensions(off, prof, signal, dates, groups, assessment): + components = signal.get("components", []) if signal else [] + return { + "fedRampId": off["fedramp_id"], + # Sought, never held: this proof of concept is not certified, and says so + # in the JSON as well as the prose (submit-package.py refuses a CPO without it). + "certification": _offering.certification(), + "class": prof.get("fedramp_class"), + "impact_level": prof.get("impact_level"), + "fips_199": prof.get("fips_199"), + "ksi_signal_id": signal.get("signal_id"), + "simulated": simulated(off), + "engagement": _engagement.STATEMENT, + "services": services_detail(off, prof, groups), + "notIncluded": off.get("not_included", []), + "continuousMonitoring": dates, + "minimumAssessmentScope": { + "componentCount": len(components), + "boundaryMap": BASE + "boundary-map.json", + "authorizationBoundary": "https://samaydlette.com/research/authorization-boundary.html"}, + "cryptographicModules": off.get("cryptographic_modules", []), + "independentAssessment": independent_assessment(off, assessment), + "documentationOverview": off.get("documentation_overview_url"), + # AFC-CSO-INB: the FedRAMP Security Inbox contact, from its one source. + # Simulated for this proof of concept (no mail is received or sent). + "fedrampSecurityInbox": _fsi(off), + "significantChangeNotifications": SCN_NOTIFICATION, + } + + +def build(off, prof, signal, cal, prev, now, groups, assessment): + dates = _ccm.dates_summary(cal, now.date()) + ao = off["accountable_official"] + doc = { + "$schema": fs.stamp("cpo"), + "serviceIdentification": service_identification(off), + "serviceProperties": service_properties(off, dates), + "contactInformation": contacts(off), + "certifiedServices": certified_services(off), + "thirdPartyInformationResources": third_party_information_resources(), + "metadata": {"accountableOfficial": {"name": ao["name"], "title": ao["title"], "contact": ao["contact"]}}, + "providerExtensions": provider_extensions(off, prof, signal, dates, groups, assessment), + } + _engagement.require_none(doc, "the CPO") + return _offering.stamp_version(doc, prev, now, "Automated: scripts/build-cpo.py, from data/cds/offering.json, " + "the system profile, the CCM calendar and the KSI signal") + + +def boundary_groups(path=BOUNDARY): + return {g["key"] for g in json.loads(Path(path).read_text()).get("groups", [])} + + +def main(argv=None): ap = argparse.ArgumentParser() - ap.add_argument("--offering", default="../data/cds/offering.json") + ap.add_argument("--offering", default=str(_offering.OFFERING_PATH)) ap.add_argument("--profile", default="../data/system-profile.json") - ap.add_argument("--overview", default="certification-overview-package.json") ap.add_argument("--ksi-signal", default="ksi-signal.json") + ap.add_argument("--calendar", default=str(_ccm.CALENDAR_PATH)) + ap.add_argument("--previous-cpo", default=None) ap.add_argument("--output", default="certification-package-overview.json") ap.add_argument("--md-output", default="certification-package-overview.md") - a = ap.parse_args() + # The simulated assessor's keyless-signed set, verified against the pinned + # assessor identity before its summary is quoted (CPO-CSO-OSA). Required. + ap.add_argument("--assessment", required=True) + ap.add_argument("--assessment-bundle", default=None) + # The commit and published KSI signal the set must cover (scripts/_assessor.py, bind). + ap.add_argument("--assessment-commit", default=None) + ap.add_argument("--assessment-signal-id", default=None) + ap.add_argument("--assessor-identity", default=str(_assessor.IDENTITY_PATH)) + a = ap.parse_args(argv) now = datetime.now(timezone.utc) - off = json.loads(Path(a.offering).read_text()) + off = _offering.load(a.offering) prof = json.loads(Path(a.profile).read_text()) - overview = json.loads(Path(a.overview).read_text()) if Path(a.overview).exists() else {} - signal = json.loads(Path(a.ksi_signal).read_text()) if Path(a.ksi_signal).exists() else {} - components = signal.get("components", []) if signal else [] - - cpo = { - "package_type": "certification-package-overview", - "schema": "fedramp-certification-package-overview-schema-2026-06-24.json", - "note": "With the Security Decision Record, the CR26 replacement for the base System " - "Security Plan.", - # CPO-CSO-MTD - "accountable_official": off.get("accountable_official"), - "metadata": { - "version": "live (regenerated each deploy)", - "last_updated": now.isoformat(), - "source_of_update": "scripts/build-cpo.py", - }, - "maintenance_cadence": "per-deploy — exceeds the CPO-CSX-CPM Class C 2-week minimum", - "class": prof.get("fedramp_class"), - "impact_level": prof.get("impact_level"), - "impact_level_canonical": prof.get("impact_level_canonical"), - "ksi_signal_id": signal.get("signal_id"), - # CPO-CSO-OVR rollup: - "certification_data": { # CDS public info - "fedramp_id": overview.get("fedramp_id") or off.get("fedramp_id"), - "service_description": off.get("service_description"), - "service_model": off.get("service_model"), - "deployment_model": off.get("deployment_model"), - "security_contact": off.get("security_contact"), - "overview_package": BASE + "certification-overview-package.json", - }, - "minimum_assessment_scope": { # MAS - "component_count": len(components), - "services": off.get("services"), - "authorization_boundary": "https://samaydlette.com/research/authorization-boundary.html", - "reference": "MAS-CSO-IIR / MAS-CSO-FLO / MAS-CSO-TPR; MAS-CSO-MDI N/A (no federal customer data)", - }, - "cryptographic_modules": { # CMU-CSO-CMD - "modules": off.get("cryptographic_modules", []), - "reference": "CMU-CSO-CMD; full narrative in the authorization-boundary FIPS section", - }, - "independent_assessment": { # IVV-CSO-ICP - "status": "N/A — no FedRAMP Recognized independent assessment service engaged " - "(self-attested PoC). Provider-side verification and validation are in " - "the Security Decision Record; the independent half is unmet by design.", - "current_service": off.get("current_independent_assessment_service"), - }, - "package_contents": [ - {"artifact": fn, "description": desc, "url": BASE + fn, "signed": signed} - for fn, desc, signed in PACKAGE_CONTENTS - ], - } - Path(a.output).write_text(json.dumps(cpo, indent=2) + "\n") + if not Path(a.ksi_signal).exists(): + _fail(f"{a.ksi_signal} not found") + signal = json.loads(Path(a.ksi_signal).read_text()) + prev = {} + if a.previous_cpo and Path(a.previous_cpo).exists(): + try: + prev = json.loads(Path(a.previous_cpo).read_text()) + except json.JSONDecodeError: + prev = {} + assessment = _assessor.load_assessment(a.assessment, a.assessment_bundle or a.assessment[:-5] + ".bundle", + a.assessor_identity, expect_commit=a.assessment_commit, + expect_signal_id=a.assessment_signal_id) + doc = build(off, prof, signal, _ccm.load(a.calendar, now.date()), prev, now, boundary_groups(), assessment) + fs.write_validated(doc, "cpo", a.output) if a.md_output: - Path(a.md_output).write_text(render_markdown(cpo) + "\n") - ao = cpo["accountable_official"] or {} - print(f"certification-package-overview: official {ao.get('name')}; " - f"{len(cpo['package_contents'])} package artifacts; " - f"{cpo['minimum_assessment_scope']['component_count']} components in scope") + Path(a.md_output).write_text(render_markdown(doc) + "\n") + print(f"certification-package-overview {doc['metadata']['version']}: " + f"{len(doc['certifiedServices'])} services; next report " + f"{doc['serviceProperties']['nextOngoingCertificationReportDate']}") return 0 +# --- human-readable view (CDS-CSO-CBF: same data as the JSON) ------------------------- + +def _cell(text): + return str(text).replace("|", "\\|").replace("\n", " ") + + def render_markdown(c): - ao = c["accountable_official"] or {} + si, sp, m, pe = c["serviceIdentification"], c["serviceProperties"], c["metadata"], c["providerExtensions"] + ao = m["accountableOfficial"] + ccm = pe["continuousMonitoring"] out = ["# Certification Package Overview", "", - f"_{c['note']}_", "", - f"- **Accountable official:** {ao.get('name')}, {ao.get('title')} ({ao.get('contact')})", - f"- **Class:** {c['class']} | **Impact:** {c['impact_level_canonical']}", - f"- **Version:** {c['metadata']['version']} | **Last updated:** {c['metadata']['last_updated']}", - f"- **Maintenance:** {c['maintenance_cadence']}", - f"- **Bound to inventory signal:** `{c['ksi_signal_id']}`", ""] - mas = c["minimum_assessment_scope"] - out += ["## Minimum Assessment Scope", "", - f"- Components in scope: **{mas['component_count']}**", - f"- Authorization boundary: {mas['authorization_boundary']}", - f"- {mas['reference']}", ""] - out += ["## Cryptographic modules (CMU-CSO-CMD)", "", - "| Module | Validation | Role |", "|---|---|---|"] - for m in c["cryptographic_modules"]["modules"]: - out.append("| {mod} | {val} | {role} |".format( - mod=m.get("module", ""), val=m.get("validation", ""), role=m.get("role", ""))) - out += ["", "## Independent assessment (IVV-CSO-ICP)", "", c["independent_assessment"]["status"], ""] - out += ["## Package contents", "", "| Artifact | Description | Signed |", "|---|---|---|"] - for p in c["package_contents"]: - out.append("| [`{a}`]({u}) | {d} | {s} |".format( - a=p["artifact"], u=p["url"], d=p["description"], s="yes" if p["signed"] else "no")) - out += ["", "---", "_Source of truth: the signed `certification-package-overview.json` (CPO-CSO-OVR)._"] + f"_{pe['certification']['program']} (sought; status: {pe['certification']['status']}). With the " + "Security Decision Record, the CR26 replacement for the System Security Plan._", "", f"> {pe['engagement']}", "", + f"- **Provider:** {si['providerName']} | **Service:** {si['serviceName']} ({si['serviceAcronym']})", + f"- **FedRAMP ID:** {si['fedRampPackageId']} (simulated: no FedRAMP ID has been assigned)", + f"- **UEI:** {si['ueiNumber']} (simulated: no SAM.gov registration)", + f"- **Certification type:** {si['certificationType']} | **Class:** {pe['class']} | " + f"**Impact:** {pe['impact_level']} (FIPS 199 high-water mark)", + f"- **Service model:** {', '.join(sp['serviceType'])} | **Deployment model:** {sp['deploymentModel']}", + f"- **Business category:** {', '.join(sp['businessCategory'])}", + f"- **Website:** {si['website']} | **Logo:** {si['logo']}", + f"- **Accountable official:** {ao['name']}, {ao['title']} ({ao['contact']})", + f"- **Version:** {m['version']} | **Last updated:** {m['lastUpdated']}", + f"- **Source:** {m['updateSource']}", + f"- **FedRAMP Security Inbox (AFC-CSO-INB):** " + f"{(pe.get('fedrampSecurityInbox') or {}).get('contact', 'not established')}", + f"- **Bound to inventory signal:** `{pe['ksi_signal_id']}`", "", + "## Service description", "", si["serviceDescription"], "", + "## Contacts", "", "| Type | Contact |", "|---|---|"] + for ct in c["contactInformation"]: + out.append(f"| {ct['contactType']} | {_cell(ct.get('contactEmail') or ct.get('contactName', ''))} |") + out += ["", "## Continuous monitoring", "", + f"- **Next Ongoing Certification Report:** {ccm['nextOngoingCertificationReportDate']}", + f"- **Next Quarterly Review:** {ccm['nextQuarterlyReviewDate']} " + f"({ccm['reviewBusinessDaysAfterIssue']} business days after the report)", + f"- **Review calendar:** {ccm['quarterlyReviewCalendar']} | " + f"**Reviews held (simulated attendees, DEC-194):** {ccm['quarterlyReviews']}", + f"- **Issued reports and snapshots:** {ccm['ongoingCertificationReportIssues']}", + f"- **Issue dates:** {', '.join(ccm['issueDates'])}", "", + "## Services (CDS-CSO-SVC)", "", + "| Service | C / I / A | In scope | Description |", "|---|---|---|---|"] + desc = {s["serviceName"]: s["serviceDescription"] for s in c["certifiedServices"]} + for s in pe["services"]: + cat = s["securityCategory"] + out.append(f"| {_cell(s['serviceName'])} | {cat['confidentiality']} / {cat['integrity']} / " + f"{cat['availability']} | {'yes' if s['inMinimumAssessmentScope'] else 'no'} | " + f"{_cell(desc[s['serviceName']])} |") + out += ["", "**Not included:**", ""] + [f"- {n['name']}: {n['why']}" for n in pe["notIncluded"]] + out += ["", "## Simulated values", "", + "This is a proof of concept. These values stand in for an outside party that does not exist here:", ""] + out += [f"- `{s['field']}` ({s['counterparty']}): {s['how']}" for s in pe["simulated"]] + out += ["", "## Package contents", "", "| Artifact | Type | Description |", "|---|---|---|"] + for r in sp["additionalRepositories"]: + out.append(f"| [{r['url'].rsplit('/', 1)[-1]}]({r['url']}) | {', '.join(r['repositoryType'])} | " + f"{_cell(r['repositoryDescription'])} |") + out += ["", "## Cryptographic modules (CMU-CSO-CMD)", "", "| Module | Validation | Role |", "|---|---|---|"] + for mod in pe["cryptographicModules"]: + out.append(f"| {_cell(mod.get('module', ''))} | {_cell(mod.get('validation', ''))} | " + f"{_cell(mod.get('role', ''))} |") + scn = pe["significantChangeNotifications"] + out += ["", "## Significant Change Notifications (SCN-CSO-NOM)", "", scn["method"], ""] + out += [f"- {m['mechanism']}: {m['url']}" for m in scn["mechanisms"]] + out += [f"- Evaluation records (SCN-CSO-MAR): {scn['evaluation_records']}", + f"- Access: {scn['access']}", f"- Emergency changes (SCN-CSO-EMG): {scn['emergency_procedure']}"] + ia = pe["independentAssessment"] + out += ["", "## Trust center and secure configuration", "", + f"- **Trust center:** {sp['trustCenter']['url']} ({sp['trustCenter']['accessRequestInstructions']})", + f"- **Secure configuration guidance:** {sp['secureConfigurationGuidance']['url']}", "", + "## Third-party information resources (MAS-CSO-TPR)", "", + "None is FedRAMP certified.", "", "| Resource | Provider | Use |", "|---|---|---|"] + for r in c["thirdPartyInformationResources"]["nonCertified"]: + out.append(f"| {_cell(r['name'])} | {_cell(r['provider'])} | {_cell(r['useCase'])} |") + out += ["", "## Independent assessment", "", f"- **Current service:** {ia['currentService']}", + f"- **Signed results:** {ia['assessmentSet']}", "", + "**Overall summary (IVV-IAS-OSA), quoted verbatim from the assessor's signed record " + f"`{ia['overallSummary']['record_id']}`:**", "", "> " + _cell(ia["overallSummary"]["text"]), "", + "---", "_Source of truth: the signed `certification-package-overview.json` (CPO-CSO-OVR)._"] return "\n".join(out) diff --git a/scripts/build-cr26-vdr.py b/scripts/build-cr26-vdr.py index 004ebeb3..6d5067ed 100644 --- a/scripts/build-cr26-vdr.py +++ b/scripts/build-cr26-vdr.py @@ -23,15 +23,46 @@ # rationale is the decision record's justification, never invented: an accepted # finding with no justification stops the build. # +# What each record says, and where it comes from: +# detection time the earliest evidence: the scanner's first report, or the +# original_detection_date of a decision naming this exact +# record, when the weakness was found before the pipeline's +# scanner saw it (e.g. a manual scan). A .checkov.yaml +# suppression, which no scanner ever reports, falls back to +# the decision date when the decision records no detection +# date. The basis is in providerExtensions. +# next reduction the decision's planned_reduction (date + target rating) when +# one is recorded, else the remediation deadline. +# overdue explains the overdue status (deadline, and why it is still +# open), never the suppression. +# supplementary the decision behind the record: its justification (VDT only; +# the AVI carries it as the rationale), when it was decided and +# is reviewed, the resources it names, any remediation plan or +# mitigation. +# rating history the historical rating and every re-evaluation, from the VDR +# ledger. The schema has a field only for completed reductions, +# so the full history is in providerExtensions. +# # The schemas carry no field for the component, the CVE, the scanner check or the # decision. Those are the joins a reader needs to trace a finding to the system, # so each record carries them under `providerExtensions` (the schemas allow # additional properties). # # Report periods (VER-RPT-PER: summarize ALL activity since the previous report): -# each VDT/AVI runs from the previous published report's end to now. The MRH -# accumulates: a finding that leaves the VDR stays in the history, marked -# Remediated with the time it stopped being reported, for HISTORY_DAYS. +# each VDT/AVI runs from the previous published report's end to now, and carries +# an activity summary for that period (providerExtensions.activitySummary): +# detections, evaluations, rating changes and reductions, records that stopped +# being reported, decisions recorded and closed, every scan and feed the VDR +# build read with its time, and the runtime verification run it read, linked. +# +# The MRH accumulates. A record that leaves the VDR stays in the history for +# HISTORY_DAYS with the time it stopped being reported. It gets a final +# disposition only from evidence: a closed decision that says remediated, a +# false-positive suppression of its check, or its scanner having run again over +# the same scope without reporting it. Otherwise it is recorded as no longer +# reported, with the reason (a risk-accepted suppression, or unknown), and no +# final disposition. Closed (remediated) decisions are carried in the history +# too, including those from before the pipeline's ledger began. # # build-cr26-vdr.py --vdr vdr-report.json --decisions ../data/decisions.json \ # --previous-vdt prev-vdt.json --previous-avi prev-avi.json --previous-mrh prev-mrh.json @@ -45,6 +76,7 @@ sys.path.insert(0, str(Path(__file__).resolve().parent)) import _decisions # noqa: E402 +import _redact # noqa: E402 import _fedramp_schema as fs # noqa: E402 HISTORY_DAYS = 366 @@ -57,8 +89,34 @@ "zap": "OWASP ZAP (dynamic application scan)", "grype": "Grype (software composition analysis)", "dependabot": "GitHub Dependabot (software composition analysis)", + "codeql": "GitHub CodeQL (static analysis of first-party code)", "opa": "OPA policy evaluation of the deployed configuration", } +SOURCE_BY_LABEL = {v: k for k, v in SOURCES.items()} +# The detection-gate feed that shows a source's scanner ran in a build. A source +# with no feed here (OPA) never earns a disposition from coverage. +COVERAGE_FEEDS = {"grype": "grype", "dependabot": "dependabot", "checkov": "checkov", + "checkov-suppression": "checkov", "tfsec": "tfsec", "codeql": "codeql"} +SCAN_FEEDS = {"grype": "Grype software composition scan", "dependabot": "Dependabot alerts", + "checkov": "Checkov IaC scan", "tfsec": "tfsec IaC scan", + "kev": "CISA KEV catalog", "epss": "FIRST EPSS scores", + "codeql": "CodeQL code scan", "zap-api": "OWASP ZAP authenticated API scan"} + +OFFERING = Path(__file__).resolve().parent.parent / "data" / "cds" / "offering.json" + + +def fedramp_id(path=OFFERING): + """The offering's FedRAMP ID (CDS-CSO-FID), stamped on every report as + providerExtensions.fedRampId. Reads the same field as _offering.fedramp_id() + (feat/sdr-schema); missing or empty stops the build.""" + try: + v = json.loads(Path(path).read_text(encoding="utf-8")).get("fedramp_id") + except (OSError, json.JSONDecodeError) as exc: + _fail(f"{path}: unreadable ({exc.__class__.__name__})") + if not isinstance(v, str) or not v.strip(): + _fail(f"{path}: fedramp_id is missing") + return v + VDT_OUT = "vdr-detail-report.json" AVI_OUT = "vdr-accepted-vulnerabilities.json" @@ -76,7 +134,7 @@ def _rating(pain): _fail(f"PAIN rating {pain!r} is not N0-N5") -def _ts(value, where): +def _dt(value, where): if not isinstance(value, str): _fail(f"{where}: missing timestamp") try: @@ -85,11 +143,28 @@ def _ts(value, where): _fail(f"{where}: {value!r} is not an ISO 8601 timestamp") if dt.tzinfo is None: _fail(f"{where}: {value!r} has no time zone") - return dt.astimezone(timezone.utc).isoformat() + return dt.astimezone(timezone.utc) + + +def _ts(value, where): + return _dt(value, where).isoformat() -def _justifications(register): - return {r["id"]: (r.get("justification") or "").strip() for r in register.get("decisions", [])} +def _maybe_dt(value): + """A timestamp, or a YYYY-MM-DD date read as midnight UTC; None if neither.""" + if not isinstance(value, str): + return None + try: + dt = datetime.fromisoformat(value.replace("Z", "+00:00")) + except ValueError: + return None + return (dt if dt.tzinfo else dt.replace(tzinfo=timezone.utc)).astimezone(timezone.utc) + + +def _day(value): + """A register date (YYYY-MM-DD) as midnight UTC, ISO 8601; None if absent.""" + dt = _maybe_dt(value) + return dt.isoformat() if dt else None def _description(f): @@ -104,54 +179,164 @@ def is_accepted(f): return disp in ACCEPTED_KINDS or bool(f.get("accepted")) -def detail(f): +# --- per-record fields -------------------------------------------------------------- + +def _detection(f, rec, tid): + """(detectedAt, basis): the earliest evidence of the weakness.""" + seen = _dt(f.get("first_detected"), f"{tid}.first_detected") + # Only a decision that names this exact record (a vulnerability ID such as + # zap-10099, or a suppressed check) dates it. A decision about a check across + # many resources dates the check, not a resource added after it. + if rec and tid in _decision_claims(rec): + known = _maybe_dt(rec.get("original_detection_date")) + if known and known < seen: + return known.isoformat(), (f"{rec['id']} original_detection_date: found before the " + "pipeline's scanner first reported it") + decided = _maybe_dt(rec.get("decided_on")) + if not known and f.get("source") == "checkov-suppression" and decided and decided < seen: + return decided.isoformat(), (f"{rec['id']} decided_on: the decision records no detection " + "date, and the weakness was known when it was decided (a " + "suppressed check is never reported by the scanner)") + return seen.isoformat(), "first reported by the scanner (VDR ledger)" + + +def _rating_history(f, tid): + out = [] + for h in f.get("rating_history") or []: + if not isinstance(h, dict): + continue + out.append({"at": _ts(h.get("at"), f"{tid}.rating_history"), "rating": _rating(h.get("pain")), + "isInternetReachable": h.get("irv"), "isLikelyExploitable": h.get("lev"), + "reason": h.get("reason")}) + return out + + +def _overdue(f, rec, final): + """overdueStatus whose explanation explains the overdue status itself.""" + over = bool(f.get("is_overdue")) + due = f.get("remediation_due_at") or (f.get("next_reduction") or {}).get("estimated_time") + did = rec["id"] if rec else f.get("decision_id") + if over: + if f.get("accepted") and f.get("accepted_at"): + why = ("Overdue: not fully mitigated or remediated within the VER-TFR-MAV maximum " + f"period, which ended {f['accepted_at'][:10]}") + elif due: + why = f"Overdue: its remediation deadline, {due[:10]}, passed without remediation" + else: + why = f"Overdue: {f.get('block_reason') or 'past its deadline'}" + if rec and rec.get("disposition") in ACCEPTED_KINDS: + why += (f". It is still open because {did} accepts it ({rec['disposition']}, decided " + f"{rec.get('decided_on', 'on a date not recorded')}), so no remediation is planned") + elif rec and rec.get("disposition") == "vendor-dependency": + why += f". It is waiting on a vendor fix ({did})" + elif f.get("block_reason") and due: + why += f" ({f['block_reason']})" + return {"isOverdue": True, "explanation": why + "."} + if f.get("will_be_overdue") and due: + return {"isOverdue": False, + "explanation": f"Not yet overdue, but likely to become overdue: remediation is due {due[:10]}."} + if final: + return {"isOverdue": False, + "explanation": f"Not overdue: closed as {final}{f' under {did}' if did else ''}."} + if due: + return {"isOverdue": False, "explanation": f"Not overdue: remediation is due {due[:10]}."} + return {"isOverdue": False} + + +def _supplementary(f, rec, accepted): + parts = [] + if rec: + head = (f"{rec['id']} ({rec['disposition']}; decided {rec.get('decided_on', 'on a date not recorded')}" + f"{', review by ' + rec['review_by'] if rec.get('review_by') else ''})") + parts.append(head + ("." if accepted else f": {rec['justification'].strip()}")) + res = (rec.get("applies_to") or {}).get("resources") or [] + if res: + parts.append(f"Resources named by the decision: {', '.join(res)}.") + if rec.get("remediation_plan"): + parts.append(f"Remediation plan: {rec['remediation_plan'].strip()}") + mit = (rec.get("vuln_fields") or {}).get("mitigation") + if mit: + parts.append(f"Mitigation record: {mit}.") + m = f.get("mitigation") + if isinstance(m, dict) and m.get("id"): + state = "verified" if m.get("valid") else f"void ({m.get('void_reason') or 'not verified'})" + parts.append(f"Mitigation {m['id']} ({m.get('effect')}): {state}.") + if f.get("supplementary_info"): + parts.append(str(f["supplementary_info"]).strip()) + return " ".join(p for p in parts if p) + + +def _projection(f, rec, rating, tid): + """(projectedNextReduction, basis), or (None, None) when none is planned.""" + plan = (rec or {}).get("planned_reduction") + if plan: + target = _rating(plan.get("target_pain")) + if target < rating: + return ({"estimatedAt": _ts(_day(plan.get("date")), f"{rec['id']}.planned_reduction"), + "targetRating": target}, f"{rec['id']} planned_reduction") + nxt = f.get("next_reduction") + if nxt and nxt.get("estimated_time"): + target = nxt.get("target_pain") + basis = "remediation deadline (no planned reduction recorded)" + if plan: + basis = f"remediation deadline ({rec['id']} planned_reduction is not below the current rating)" + # "remediated" removes the vulnerability: no impact remains (N0). + return ({"estimatedAt": _ts(nxt["estimated_time"], f"{tid}.next_reduction"), + "targetRating": 0 if target == "remediated" else _rating(target)}, basis) + return None, None + + +def detail(f, recs=None, accepted=False): """A VDR finding as a FedRAMP vulnerabilityDetail record.""" + recs = recs or {} tid = f.get("tracking_id") if not tid: _fail("a finding has no tracking_id") + rec = recs.get(f.get("decision_id")) pain = f.get("current_pain") or f.get("pain") - rec = { + rating = _rating(pain) + detected_at, detected_basis = _detection(f, rec, tid) + out = { "providerTrackingId": tid, "detection": { - "detectedAt": _ts(f.get("first_detected"), f"{tid}.first_detected"), + "detectedAt": detected_at, "detectionSource": SOURCES.get(f.get("source"), f.get("source") or "unknown"), }, "vulnerabilityDescription": _description(f) or tid, - "potentialAgencyImpact": (f"Potential Agency Impact {pain} " + "potentialAgencyImpact": (f"Potential Agency Impact {f['impact_rationale']}" + if f.get("impact_rationale") else + f"Potential Agency Impact {pain} " f"(technical impact {f.get('technical_impact') or 'not rated'}; " "see VER-EVA-EPA for the N-rating scale)."), "evaluationCompletedAt": _ts(f.get("first_evaluated") or f.get("completed_evaluation"), f"{tid}.first_evaluated"), "isInternetReachable": bool(f.get("internet_reachable")), "isLikelyExploitable": bool(f.get("likely_exploitable")), - "currentRating": _rating(pain), + "currentRating": rating, } - over = {"isOverdue": bool(f.get("is_overdue"))} - if f.get("overdue_explanation"): - over["explanation"] = f["overdue_explanation"] - elif over["isOverdue"]: - _fail(f"{tid}: overdue with no explanation") - rec["overdueStatus"] = over - if f.get("supplementary_info"): - rec["supplementaryRiskInformation"] = f["supplementary_info"] - reductions = [{"reducedAt": _ts(r.get("at"), f"{tid}.completed_reductions"), "rating": _rating(r.get("to"))} - for r in f.get("completed_reductions") or []] - if reductions: - rec["painReductionEvents"] = reductions disp = f.get("final_disposition") or f.get("current_disposition") or "open" + final = None if disp in FINAL: - rec["finalDisposition"] = FINAL[disp] + final = FINAL[disp] elif disp == "mitigated": - rec["finalDisposition"] = "Fully Mitigated" if f.get("fully_mitigated") else "Partially Mitigated" - nxt = f.get("next_reduction") - if "finalDisposition" not in rec and not is_accepted(f) and nxt and nxt.get("estimated_time"): - target = nxt.get("target_pain") - # "remediated" removes the vulnerability: no impact remains (N0). - rec["projectedNextReduction"] = { - "estimatedAt": _ts(nxt["estimated_time"], f"{tid}.next_reduction"), - "targetRating": 0 if target == "remediated" else _rating(target), - } - rec["providerExtensions"] = { + final = "Fully Mitigated" if f.get("fully_mitigated") else "Partially Mitigated" + out["overdueStatus"] = _overdue(f, rec, final) + supp = _supplementary(f, rec, accepted) + if supp: + out["supplementaryRiskInformation"] = supp + reductions = [{"reducedAt": _ts(r.get("at"), f"{tid}.completed_reductions"), "rating": _rating(r.get("to"))} + for r in f.get("completed_reductions") or []] + if reductions: + out["painReductionEvents"] = reductions + if final: + out["finalDisposition"] = final + projection_basis = None + if final is None and not is_accepted(f): + projection, projection_basis = _projection(f, rec, rating, tid) + if projection: + out["projectedNextReduction"] = projection + ext = { + "source": f.get("source"), "componentId": f.get("component_id"), "resource": f.get("resource") or None, "cve": f.get("cve"), @@ -160,19 +345,47 @@ def detail(f): "disposition": disp, "isKev": bool(f.get("is_kev")), "remediationDueAt": f.get("remediation_due_at"), + "detectedAtBasis": detected_basis, + "firstReportedAt": _ts(f.get("first_detected"), f"{tid}.first_detected"), } - return rec - - -def accepted_info(f, justifications): + # VER-EVA-*: the evaluation record, the group the finding is evaluated in, + # and the disclosure determination, as the VDR report states them. + for k, name in (("evaluation", "evaluation"), ("group_id", "groupId"), ("group_due_at", "groupDueAt"), + ("evaluation_late", "evaluationLate"), ("public_disclosure", "publicDisclosure"), + ("accepted_basis", "acceptedBasis")): + if f.get(k) is not None: + ext[name] = f[k] + if f.get("is_kev"): + # VDR-TFR-KEV: the CISA catalog's remediation date and whether it passed. + ext["kevDueAt"] = f.get("kev_due_at") + ext["kevDateAdded"] = f.get("kev_date_added") + ext["kevOverdue"] = bool(f.get("kev_overdue")) + if f.get("affected_resources"): + ext["affectedResources"] = _redact.withhold_iam_users(f["affected_resources"]) + if projection_basis: + ext["projectionBasis"] = projection_basis + # VER-RPT-VDT asks for the historical and current ratings; the schema has a + # field only for the current one and for completed reductions. + if f.get("historical_pain"): + ext["historicalRating"] = _rating(f["historical_pain"]) + history = _rating_history(f, tid) + if history: + ext["ratingHistory"] = history + out["providerExtensions"] = ext + return out + + +def accepted_info(f, recs): did = f.get("decision_id") - why = justifications.get(did, "") if did else "" + why = ((recs.get(did) or {}).get("justification") or "").strip() if did else "" if not why and f.get("accepted") and f.get("acceptance_explanation"): why = f["acceptance_explanation"] if not why: _fail(f"accepted finding {f.get('tracking_id')} has no decision justification ({did or 'no decision_id'})") - return {"vulnerabilityDetail": detail(f), "acceptanceRationale": why} + return {"vulnerabilityDetail": detail(f, recs, accepted=True), "acceptanceRationale": why} + +# --- periods ------------------------------------------------------------------------ def _period_start(previous, fallback): """The previous report's end, if it is a valid past time; else `fallback`.""" @@ -199,15 +412,116 @@ def _load_previous(path): return doc +def activity_summary(vdr, mrh, register, frm, to): + """VER-RPT-PER: the vulnerability detection and response activity in + [frm, to], from the VDR report, the history and the decision register.""" + lo, hi = _dt(frm, "period.from"), _dt(to, "period.to") + + def within(value): + dt = _maybe_dt(value) + return bool(dt and lo <= dt <= hi) + + rows = [f for f in vdr.get("findings") or [] if isinstance(f, dict)] + \ + [r for r in vdr.get("risk_accepted") or [] if isinstance(r, dict)] + detections = [{"providerTrackingId": f["tracking_id"], "at": f["first_detected"]} + for f in rows if within(f.get("first_detected"))] + evaluations = [{"providerTrackingId": f["tracking_id"], "at": f["first_evaluated"]} + for f in rows if within(f.get("first_evaluated"))] + changes = [{"providerTrackingId": f["tracking_id"], "at": h["at"], "rating": h.get("pain"), + "reason": h.get("reason")} + for f in rows for h in f.get("rating_history") or [] + if isinstance(h, dict) and within(h.get("at")) and h.get("reason") != "first evaluation"] + reductions = [{"providerTrackingId": f["tracking_id"], "at": r["at"], "from": r.get("from"), "to": r.get("to")} + for f in rows for r in f.get("completed_reductions") or [] + if isinstance(r, dict) and within(r.get("at"))] + gone = [{"providerTrackingId": r["providerTrackingId"], + "at": r["providerExtensions"]["noLongerReportedAt"], + "finalDisposition": r.get("finalDisposition"), + "reason": r["providerExtensions"].get("noLongerReportedReason")} + for r in mrh.get("activeVulnerabilities") or [] + if within((r.get("providerExtensions") or {}).get("noLongerReportedAt"))] + decided = [{"decisionId": d["id"], "on": d["decided_on"], "disposition": d["disposition"]} + for d in register.get("decisions", []) if within(_day(d.get("decided_on")))] + closed = [{"decisionId": d["id"], "on": d["closed_on"], "disposition": d["disposition"]} + for d in register.get("decisions", []) + if d.get("status") == "closed" and d.get("disposition") == "remediated" + and within(_day(d.get("closed_on")))] + remediated = {g["providerTrackingId"] for g in gone if g["finalDisposition"] == "Remediated"} | \ + {c["decisionId"] for c in closed} + meth = vdr.get("methodology") or {} + det = meth.get("detection") or {} + scans = [{"activity": "VDR build: every finding re-evaluated (PAIN, IRV, LEV, deadlines)", + "at": vdr.get("emitted_at"), "timeBasis": "build time", "status": "ok", + "inPeriod": within(vdr.get("emitted_at"))}] + for feed in det.get("feeds") or []: + name = SCAN_FEEDS.get(feed.get("feed")) if isinstance(feed, dict) else None + if not name: + continue + if feed.get("feed") in ("kev", "epss"): + at, basis = feed.get("source_date"), "published by the source" + else: + at, basis = det.get("checked_at"), "run or fetched in this build (when the detection gate checked it)" + row = {"activity": f"{name} ({feed.get('file')})", "at": at, "timeBasis": basis, + "status": feed.get("status"), "count": feed.get("count"), "inPeriod": within(at)} + if feed.get("feed") == "grype" and feed.get("source_date"): + row["vulnerabilityDatabaseBuiltAt"] = feed["source_date"] + scans.append(row) + dast = meth.get("dast") + if isinstance(dast, dict): + scans.append({"activity": "OWASP ZAP dynamic scan of the site", "at": dast.get("generated_at"), + "timeBasis": "scan report generated", "status": dast.get("status"), + "count": dast.get("alerts"), "inPeriod": within(dast.get("generated_at"))}) + rt = meth.get("runtime_verification") + runtime = None + if isinstance(rt, dict): + runtime = {"uri": rt.get("uri"), "signalId": rt.get("signal_id"), "emittedAt": rt.get("emitted_at"), + "signatureVerified": bool(rt.get("verified")), "validations": rt.get("validations"), + "failed": rt.get("failed"), "divergence": rt.get("divergence"), + "inPeriod": within(rt.get("emitted_at")), + "note": ("The runtime emitter publishes only its latest run; this is the run the VDR " + "build read. A run it replaced before this build is not retained.")} + hist = rt.get("run_history") + if rt.get("verified") and isinstance(hist, list) and hist: + # The emitter retains its runs in the signed signal: every run in + # the period is counted, not only the latest. + runs = [r for r in hist if within(r.get("emitted_at"))] + runtime["runsInPeriod"] = len(runs) + runtime["failedRunsInPeriod"] = sum(1 for r in runs if r.get("failed")) + runtime["note"] = ("Every runtime run in the period, from the run history the emitter signs into " + "its signal (bounded to the newest runs).") + if not rt.get("verified"): + runtime["note"] = f"Runtime signal not verified ({rt.get('reason')}); its results are not reported." + in_period = [s for s in scans if s["inPeriod"]] + run_in_period = bool(runtime and runtime["inPeriod"] and runtime["signatureVerified"]) + return { + "period": {"from": frm, "to": to}, + "counts": {"detections": len(detections), "evaluations": len(evaluations), + "ratingChanges": len(changes), "reductions": len(reductions), + "noLongerReported": len(gone), "remediations": len(remediated), + "decisionsRecorded": len(decided), "decisionsClosed": len(closed), + "scansInPeriod": len(in_period), + "runtimeRunsInPeriod": (runtime["runsInPeriod"] if runtime and "runsInPeriod" in runtime + else 1 if run_in_period else 0), + "runtimeFailuresInPeriod": (runtime["failedRunsInPeriod"] if runtime and "runsInPeriod" in runtime + else (runtime["failed"] or 0) if run_in_period else 0)}, + "detections": detections, "evaluations": evaluations, "ratingChanges": changes, + "reductions": reductions, "noLongerReported": gone, "remediations": sorted(remediated), + "decisionsRecorded": decided, "decisionsClosed": closed, "scans": scans, + "runtimeVerification": runtime, + } + + +# --- build -------------------------------------------------------------------------- + def build(vdr, register, previous_vdt, previous_avi, previous_mrh, now): if not isinstance(vdr, dict) or not isinstance(vdr.get("findings"), list): _fail("vdr-report.json has no findings list") - just = _justifications(register) + recs = _decisions.records(register) scanner = list(vdr["findings"]) # Suppressed checks the VDR lists as risk-accepted are accepted vulnerabilities too. suppressed = [dict(r, final_disposition="risk-accepted") for r in vdr.get("risk_accepted") or []] - active = [detail(f) for f in scanner if not is_accepted(f)] - accepted = [accepted_info(f, just) for f in scanner + suppressed if is_accepted(f)] + active = [detail(f, recs) for f in scanner if not is_accepted(f)] + accepted = [accepted_info(f, recs) for f in scanner + suppressed if is_accepted(f)] times = [r["detection"]["detectedAt"] for r in active] + \ [a["vulnerabilityDetail"]["detection"]["detectedAt"] for a in accepted] earliest = min(times) if times else now.isoformat() @@ -215,7 +529,7 @@ def build(vdr, register, previous_vdt, previous_avi, previous_mrh, now): cpo = {"certificationPackageOverviewUri": fs.CPO_URI} # REQ-GOV-2: like every VDR-family output, each names the method profile and # conformance results of the VDR report it came from. - ext = {"source": "vdr-report.json", "vdrReportId": vdr.get("report_id"), + ext = {"fedRampId": fedramp_id(), "source": "vdr-report.json", "vdrReportId": vdr.get("report_id"), "ksiSignalId": vdr.get("ksi_signal_id"), "profile": (vdr.get("methodology") or {}).get("profile")} vdt = {"$schema": fs.stamp("vdt"), **cpo, "reportPeriod": {"from": _period_start(previous_vdt, earliest), "to": to}, @@ -223,18 +537,121 @@ def build(vdr, register, previous_vdt, previous_avi, previous_mrh, now): avi = {"$schema": fs.stamp("avi"), **cpo, "reportPeriod": {"from": _period_start(previous_avi, earliest), "to": to}, "acceptedVulnerabilities": accepted, "providerExtensions": dict(ext)} - mrh = build_history(active, accepted, previous_mrh, now) - mrh["providerExtensions"] = {**ext, **mrh["providerExtensions"]} for doc, period in ((vdt, "VDT"), (avi, "AVI")): if doc["reportPeriod"]["from"] > doc["reportPeriod"]["to"]: _fail(f"{period} period starts after it ends") + mrh = build_history(active, accepted, previous_mrh, now, vdr=vdr, register=register) + mrh["providerExtensions"] = {**ext, **mrh["providerExtensions"]} + for doc in (vdt, avi): + doc["providerExtensions"]["activitySummary"] = activity_summary( + vdr, mrh, register, doc["reportPeriod"]["from"], doc["reportPeriod"]["to"]) return vdt, avi, mrh -def build_history(active, accepted, previous, now): - """VER-TFR-MRH: every current record, plus records that left the VDR within - HISTORY_DAYS, closed as Remediated with the time they stopped being reported.""" - cutoff = (now - timedelta(days=HISTORY_DAYS)).isoformat() +# --- history ------------------------------------------------------------------------ + +def _keys(rec): + ext = rec.get("providerExtensions") or {} + return {k for k in (rec.get("providerTrackingId"), ext.get("scannerCheck"), ext.get("cve")) if k} + + +def _decision_claims(d): + a = d.get("applies_to") or {} + return set(a.get("check_ids") or []) | set(a.get("vuln_ids") or []) + + +def _coverage(source, vdr, last_reported): + """Evidence that `source`'s scanner ran again over the same scope after the + record was last reported, or None.""" + meth = (vdr or {}).get("methodology") or {} + if source == "zap": + dast = meth.get("dast") or {} + gen, last = _maybe_dt(dast.get("generated_at")), _maybe_dt(last_reported) + if dast.get("status") == "ok" and gen and last and gen > last: + return f"the ZAP scan of {gen.isoformat()} ran after it was last reported and does not report it" + return None + feed = COVERAGE_FEEDS.get(source) + det = meth.get("detection") or {} + rows = [r for r in det.get("feeds") or [] if isinstance(r, dict) and r.get("feed") == feed] + if feed and det.get("checked_at") and rows and all(r.get("status") == "ok" for r in rows): + return (f"{feed} ran in the VDR build checked {det['checked_at']} (status ok) " + "and no longer reports it") + return None + + +def _disposition_from_evidence(rec, vdr, register, last_reported): + """(finalDisposition or None, reason, basis) for a record that left the VDR.""" + ext = rec.get("providerExtensions") or {} + keys = _keys(rec) + did = ext.get("decisionId") + for d in (register or {}).get("decisions", []): + # Only a remediated record settles a finding; a superseded one replaced a decision. + if d.get("status") == "closed" and d.get("disposition") == "remediated" \ + and (d["id"] == did or keys & _decision_claims(d)): + return ("Remediated", "remediated", + f"{d['id']} closed as remediated on {d.get('closed_on', 'a date not recorded')}") + check = ext.get("scannerCheck") + for section, final, reason in (("false_positives", "False Positive", "false-positive"), + ("risk_accepted", None, "suppressed")): + for s in (vdr or {}).get(section) or []: + if (isinstance(s, dict) and check and s.get("tool_id") == check + and s.get("tracking_id") != rec.get("providerTrackingId")): + return final, reason, (f"its check {check} is now suppressed in .checkov.yaml " + f"({s.get('decision_id') or 'no decision'}, {s.get('current_disposition')})") + source = ext.get("source") or SOURCE_BY_LABEL.get((rec.get("detection") or {}).get("detectionSource")) + if source == "checkov-suppression": + again = [f["tracking_id"] for f in (vdr or {}).get("findings") or [] + if isinstance(f, dict) and check and f.get("tool_id") == check] + if again: + return None, "reported-again", (f"its check {check} is no longer suppressed and the scanner " + f"reports it again as {', '.join(sorted(again))}") + covered = _coverage(source, vdr, last_reported) + if covered: + return "Remediated", "remediated", covered + return None, "unknown", ("no evidence of why: no closed decision names it, no suppression covers it, " + "and its scanner is not shown to have run over it again since it was last reported") + + +_BACKFILL_DETECTION = ( + ("original_detection_date", "original_detection_date"), + ("decided_on", "decided_on: no detection date is recorded; known by the decision date"), + ("closed_on", "closed_on: neither a detection nor a decision date is recorded; detected no later " + "than it was closed"), +) +_BACKFILL_SOURCE = {"original_risk_rating": "originalRiskRating", "adjusted_risk_rating": "adjustedRiskRating", + "identifier": "sourceIdentifier"} + + +def _backfill(d, now): + """A closed (remediated) decision as a history record.""" + at, basis = now.isoformat(), f"{d['id']}: no date is recorded" + for field, why in _BACKFILL_DETECTION: + if _day(d.get(field)): + at, basis = _day(d[field]), f"{d['id']} {why}" + break + src = d.get("source") or {} + ext = {"decisionId": d["id"], "disposition": "remediated", "backfilledFromDecision": True, + "remediatedOn": d.get("closed_on"), "detectedAtBasis": basis, + "dispositionBasis": f"{d['id']} closed as remediated on {d.get('closed_on', 'a date not recorded')}", + "affectedResources": _redact.withhold_iam_users((d.get("applies_to") or {}).get("resources"))} + if d.get("former_id"): + ext["formerId"] = d["former_id"] + if d.get("remediation_plan"): + ext["remediationPlan"] = d["remediation_plan"] + ext.update({out: src[k] for k, out in _BACKFILL_SOURCE.items() if src.get(k)}) + return {"providerTrackingId": d["id"], + "detection": {"detectedAt": at, "detectionSource": src.get("detector") or "not recorded"}, + "vulnerabilityDescription": d["title"], + "supplementaryRiskInformation": d["justification"].strip(), + "finalDisposition": "Remediated", + "providerExtensions": ext} + + +def build_history(active, accepted, previous, now, vdr=None, register=None): + """VER-TFR-MRH: every current record; every record that left the VDR within + HISTORY_DAYS, with a final disposition only where evidence gives one; and + every closed (remediated) decision closed within HISTORY_DAYS.""" + cutoff = now - timedelta(days=HISTORY_DAYS) current = {r["providerTrackingId"] for r in active} | \ {a["vulnerabilityDetail"]["providerTrackingId"] for a in accepted} carried = [] @@ -244,27 +661,97 @@ def build_history(active, accepted, previous, now): if not isinstance(rec, dict) or rec.get("providerTrackingId") in current: continue ext = dict(rec.get("providerExtensions") or {}) + if ext.get("backfilledFromDecision"): + continue # rebuilt from the register below gone = ext.get("noLongerReportedAt") or now.isoformat() - if gone < cutoff: + if (_maybe_dt(gone) or now) < cutoff: continue closed = dict(rec) closed.pop("projectedNextReduction", None) - closed.setdefault("finalDisposition", "Remediated") - closed["overdueStatus"] = {"isOverdue": False} ext["noLongerReportedAt"] = gone - closed["providerExtensions"] = ext - carried.append(closed) + ext.setdefault("lastReportedAt", prev.get("generatedAt")) + final = closed.get("finalDisposition") + if final and (ext.get("dispositionBasis") or final != "Remediated"): + # Settled: the disposition it had when last reported, or one already + # earned from evidence. + ext.setdefault("dispositionBasis", "its final disposition when it was last reported") + ext.setdefault("noLongerReportedReason", "closed") + else: + # Re-decided each run until evidence settles it (a closed decision + # may come later). A Remediated with no evidence is withdrawn. + closed.pop("finalDisposition", None) + final, reason, basis = _disposition_from_evidence(closed, vdr, register, ext["lastReportedAt"]) + ext["noLongerReportedReason"] = reason + ext.pop("noLongerReportedBasis", None) + if final: + closed["finalDisposition"] = final + ext["dispositionBasis"] = basis + else: + ext["noLongerReportedBasis"] = basis + if closed.get("finalDisposition"): + closed["overdueStatus"] = {"isOverdue": False, "explanation": + f"Not overdue: no longer reported; {closed['finalDisposition']}."} + carried.append({**closed, "providerExtensions": ext}) + linked = {(r.get("providerExtensions") or {}).get("decisionId") for r in carried + active} | \ + {(a["vulnerabilityDetail"].get("providerExtensions") or {}).get("decisionId") for a in accepted} + claimed = set().union(*(_keys(r) for r in carried)) + backfilled = [] + for d in (register or {}).get("decisions", []): + if d.get("status") != "closed" or d.get("disposition") != "remediated" or d["id"] in linked \ + or _decision_claims(d) & claimed: + continue + closed_on = _maybe_dt(d.get("closed_on")) + if closed_on and closed_on < cutoff: + continue + backfilled.append(_backfill(d, now)) return {"$schema": fs.stamp("mrh"), "certificationPackageOverviewUri": fs.CPO_URI, "generatedAt": now.isoformat(), - "activeVulnerabilities": active + sorted(carried, key=lambda r: r["providerTrackingId"]), + "activeVulnerabilities": active + sorted(carried + backfilled, key=lambda r: r["providerTrackingId"]), "acceptedVulnerabilities": accepted, "providerExtensions": { - "retention": f"Records that leave the VDR stay {HISTORY_DAYS} days, closed as Remediated " - "with the time they stopped being reported (noLongerReportedAt)."}} - - -def render_markdown(title, rule, records, accepted=False): + "retention": (f"Records that leave the VDR stay {HISTORY_DAYS} days with the time they stopped " + "being reported (noLongerReportedAt). A final disposition is set only from " + "evidence (dispositionBasis): a closed decision, a false-positive suppression, " + "or the scanner running again without reporting it. Otherwise " + "noLongerReportedReason says why it is not reported, or 'unknown', and no final " + "disposition is given. Closed (remediated) decisions are included " + "(backfilledFromDecision) for the same period from their closing date.")}} + + +# --- markdown ----------------------------------------------------------------------- + +def _cell(value): + return str(value).replace("|", "\\|").replace("\n", " ") + + +def render_activity(summary): + c = summary["counts"] + out = ["## Activity this period", "", + f"{summary['period']['from']} to {summary['period']['to']}", "", + f"- Detections: {c['detections']}; evaluations: {c['evaluations']}; rating changes: " + f"{c['ratingChanges']}; reductions: {c['reductions']}", + f"- No longer reported: {c['noLongerReported']}; remediations: {c['remediations']}; " + f"decisions recorded: {c['decisionsRecorded']}; decisions closed: {c['decisionsClosed']}", + "", "| Scan or feed | Time | Status | Count | In period |", "|---|---|---|---|---|"] + for s in summary["scans"]: + out.append(f"| {_cell(s['activity'])} | {s.get('at') or 'not recorded'} ({s['timeBasis']}) | " + f"{s.get('status')} | {'' if s.get('count') is None else s['count']} | " + f"{'yes' if s['inPeriod'] else 'no'} |") + rt = summary.get("runtimeVerification") + out.append("") + if rt: + out.append(f"Runtime verification: [{rt['uri']}]({rt['uri']}) emitted {rt.get('emittedAt')}, " + f"{rt.get('validations')} validations, {rt.get('failed')} failed, divergence " + f"{rt.get('divergence')}; {'in' if rt['inPeriod'] else 'not in'} this period. {rt['note']}") + else: + out.append("Runtime verification: not recorded by the VDR build.") + return out + + +def render_markdown(title, rule, records, accepted=False, summary=None): out = [f"# {title}", "", f"_FedRAMP {rule}. Source of truth: the signed JSON beside this file._", ""] + if summary: + out += render_activity(summary) + ["", "## Vulnerabilities", ""] if not records: return "\n".join(out + ["_None._"]) out += ["| Tracking ID | Detected | Internet-reachable | Likely exploitable | Rating | Overdue | " @@ -276,8 +763,7 @@ def render_markdown(title, rule, records, accepted=False): out.append("| `{t}` | {at} | {irv} | {lev} | N{n} | {od} | {last} |".format( t=d["providerTrackingId"], at=d["detection"]["detectedAt"][:10], irv="yes" if d["isInternetReachable"] else "no", lev="yes" if d["isLikelyExploitable"] else "no", - n=d["currentRating"], od="yes" if d["overdueStatus"]["isOverdue"] else "no", - last=last.replace("|", "\\|").replace("\n", " "))) + n=d["currentRating"], od="yes" if d["overdueStatus"]["isOverdue"] else "no", last=_cell(last))) return "\n".join(out) @@ -312,10 +798,11 @@ def main(): fs.write_validated(avi, "avi", out / AVI_OUT, registry) fs.write_validated(mrh, "mrh", out / MRH_OUT, registry) (out / VDT_OUT.replace(".json", ".md")).write_text( - render_markdown("Vulnerability Detail Report", "VER-RPT-VDT", vdt["vulnerabilities"]) + "\n") + render_markdown("Vulnerability Detail Report", "VER-RPT-VDT", vdt["vulnerabilities"], + summary=vdt["providerExtensions"]["activitySummary"]) + "\n") (out / AVI_OUT.replace(".json", ".md")).write_text( render_markdown("Accepted Vulnerability Info", "VER-RPT-AVI", avi["acceptedVulnerabilities"], - accepted=True) + "\n") + accepted=True, summary=avi["providerExtensions"]["activitySummary"]) + "\n") print(f"CR26 vulnerability reports: VDT {len(vdt['vulnerabilities'])}, " f"AVI {len(avi['acceptedVulnerabilities'])}, history {len(mrh['activeVulnerabilities'])} active + " f"{len(mrh['acceptedVulnerabilities'])} accepted") diff --git a/scripts/build-fsi-simulation.py b/scripts/build-fsi-simulation.py new file mode 100644 index 00000000..41829cbe --- /dev/null +++ b/scripts/build-fsi-simulation.py @@ -0,0 +1,225 @@ +#!/usr/bin/env python3 +"""Run the SIMULATED FedRAMP Security Inbox over committed synthetic messages. + +The FedRAMP Security Inbox is simulated for this proof of concept, by the +operator's decision: nothing real is received or sent. This script feeds the +synthetic messages in data/fsi-simulation/messages.json through the inbox logic +(scripts/_fsi.py) with outbound legs that only record what they would have +sent, then checks every observed outcome against the file's "expected" block: + + - classification (AFC-CSO-TFG: exact @fedramp.gov / @gsa.gov, never filtered) + - designation, Emergency sender, and the default deadlines (AFC-CSO-CRA/EMR/IMA) + - the acknowledgement (AFC-CSO-ACK): built and header-injection safe when + sent; suppressed for auto-replies and for mail failing SPF/DKIM/DMARC + - every FedRAMP message is registered and paged (AFC-CSO-RCV) + - a failed acknowledgement is recorded and reported, and a retry pass over + the same messages sends it once and sends nothing twice + - the triage register: overdue items; an Important message refused triage + until its stated timeframe is recorded; an Emergency past its deadline + reported until closed + +Any difference exits 1 and writes nothing, which fails the deploy. On success it +writes fedramp-inbox-simulation.json, labelled as a simulation, with sender +domains only (no addresses, no subjects), for the deploy to sign and publish. +""" + +from __future__ import annotations + +import argparse +import hashlib +import json +import os +import sys +from datetime import datetime, timezone +from email import policy +from email.parser import Parser +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _engagement # noqa: E402 +import _offering # noqa: E402 +import _fsi # noqa: E402 + +REPO = Path(__file__).resolve().parent.parent +ACK_HEADERS = {"from", "to", "subject", "auto-submitted", "x-auto-response-suppress", "mime-version", + "content-type", "content-transfer-encoding", "in-reply-to", "references"} +NOTICE = ("SIMULATION. The FedRAMP Security Inbox is simulated for this proof of concept, by the operator's " + "decision: no mail is received and none is sent. Nothing arrived, nothing was acknowledged, and no FedRAMP " + "staff were paged, emailed or otherwise inconvenienced. These results come from running the inbox logic over " + "committed synthetic messages on every deploy; a deploy whose results differ from the expected ones fails. " + "To reach the operator, see 'contact' (spoiler: it is LinkedIn).") +RULES = ["AFC-CSO-INB", "AFC-CSO-TFG", "AFC-CSO-RCV", "AFC-CSO-CRA", "AFC-CSO-EMR", "AFC-CSO-IMA", "AFC-CSO-ACK"] + + +def ack_problems(raw: str, to: str, subject: str) -> list[str]: + """Why a built acknowledgement is unsafe or wrong, or [].""" + out = [] + head = raw.split("\r\n\r\n", 1)[0] + for line in head.split("\r\n"): + if "\n" in line or "\r" in line or ":" not in line: + out.append("a header line is malformed") + msg = Parser(policy=policy.default).parsestr(raw) + names = [k.lower() for k in msg.keys()] + if set(names) - ACK_HEADERS: + out.append(f"unexpected headers {sorted(set(names) - ACK_HEADERS)}") + if len(names) != len(set(names)): + out.append("a header appears twice") + if [ln for ln in head.split("\r\n") if ln.lower().startswith("to:")] != [f"To: <{to}>"]: + out.append("To is not exactly the sender") + if str(msg["subject"]) != "Received: " + (subject or "(no subject)"): + out.append("the subject does not round-trip") + if msg["auto-submitted"] != "auto-replied": + out.append("Auto-Submitted: auto-replied is missing") + return out + + +def run(doc: dict) -> tuple[list[dict], dict, dict, list[str]]: + inbox = doc["inbox"] + register: dict = {} + sent: list[tuple[str, str]] = [] + pages: list[str] = [] + fail_once = {m["message_id"] for m in doc["messages"] if m.get("simulate_send_failure")} + current = {"id": None} + + def send(to, raw): # records only; nothing is sent + if current["id"] in fail_once: + fail_once.discard(current["id"]) + raise ConnectionError("simulated send failure") + sent.append((to, raw)) + + page = pages.append + failures: list[str] = [] + cases = [] + for m in doc["messages"]: + n_sent, n_pages = len(sent), len(pages) + current["id"] = m["message_id"] + res = _fsi.receive(m, register, inbox=inbox, send=send, page=page) + c, r = res["classification"], res["record"] + ack = "none" + in_reply_to = None + if r: + ack = r["ack"]["status"] + (f":{r['ack']['reason']}" if r["ack"].get("reason") else "") + if len(sent) > n_sent: + to, raw = sent[-1] + for p in ack_problems(raw, c["from"], c["subject"]): + failures.append(f"{m['case']}: acknowledgement {p}") + in_reply_to = "\r\nIn-Reply-To: " in raw + observed = {"kind": c["kind"], "designation": c["designation"], "sender_domain": c["sender_domain"], + "authenticated": c["authenticated"], "emergency_sender_ok": c["emergency_sender_ok"], + "ack": ack, "in_reply_to": in_reply_to, "page": len(pages) > n_pages, + "triage_by": r["triage_by"] if r else None, "respond_by": r["respond_by"] if r else None} + # AFC-CSO-RCV: nothing FedRAMP is dropped: every FedRAMP message is + # registered and paged, whatever its verdicts. + if c["kind"] == "fedramp" and not (r and observed["page"]): + failures.append(f"{m['case']}: a FedRAMP message was not registered and paged") + diffs = sorted(k for k, v in m["expected"].items() if observed.get(k) != v) + diffs += sorted(set(observed) - set(m["expected"])) + for k in diffs: + failures.append(f"{m['case']}: {k} expected {m['expected'].get(k)!r}, observed {observed.get(k)!r}") + cases.append({"case": m["case"], "description": m["description"], "received_at": m["received_at"], + "auth": c["auth"], "observed": observed, "matches_expected": not diffs}) + + rc = doc["register_check"] + checks: list[dict] = [] + + def check(name, expected, observed): + checks.append({"check": name, "expected": expected, "observed": observed, "ok": expected == observed}) + if expected != observed: + failures.append(f"register: {name}: expected {expected!r}, observed {observed!r}") + + def overdue_ids(at): + return sorted({p.split(" ", 1)[0] for p in _fsi.overdue(register.values(), at)}) + + def reported(rid, at, needle): + return any(p.startswith(rid + " ") and needle in p for p in _fsi.overdue(register.values(), at)) + + now = _fsi.parse_time(rc["now"]) + check(f"items overdue at {rc['now']} (untriaged Emergencies, a failed acknowledgement)", + sorted(rc["expected_overdue"]), overdue_ids(now)) + + # Retry: the same messages again (a redelivery or a retried invocation). + before = (len(sent), len(pages)) + for m in doc["messages"]: + current["id"] = m["message_id"] + _fsi.receive(m, register, inbox=inbox, send=send, page=page) + retry = {"acknowledgements_sent_again": len(sent) - before[0], "pages_sent_again": len(pages) - before[1]} + check("retry pass: only the failed acknowledgement is sent again, nothing twice", rc["expected_retry"], retry) + failed_ids = [m["message_id"] for m in doc["messages"] if m.get("simulate_send_failure")] + check("failed acknowledgements are sent on the retry", + ["sent"] * len(failed_ids), [register[i]["ack"]["status"] for i in failed_ids]) + check("a failed acknowledgement, once sent, is no longer overdue", + False, any(reported(i, now, "ack failed") for i in failed_ids)) + + # AFC-CSO-IMA: an Important message cannot be triaged without its timeframe. + imp = register[rc["important_case"]] + try: + _fsi.triage(imp, now) + refused = False + except ValueError: + refused = True + check("Important triage without the message's timeframe is refused", True, refused) + _fsi.triage(imp, now, respond_by=rc["important_respond_by"]) + check("Important triage records the message's timeframe", rc["important_respond_by"], imp["respond_by"]) + later = _fsi.parse_time(rc["later"]) + check("an Important message untriaged after 24 hours is reported", True, + reported(rc["untriaged_important_case"], later, "not triaged")) + forced = dict(imp, id="sim-forced-state", status="triaged", respond_by=None, history=[]) + check("an Important item triaged without a timeframe is reported", True, + any("timeframe" in p for p in _fsi.overdue([forced], now))) + + # AFC-CSO-CRA: an Emergency past its deadline and not closed is reported; + # closing it clears the report. + em = register[rc["emergency_case"]] + _fsi.triage(em, now) + check("a triaged Emergency is no longer reported as untriaged", False, reported(em["id"], now, "not triaged")) + check("an Emergency past its deadline and not closed is reported", True, + reported(em["id"], later, "not closed")) + _fsi.close(em, later, "required actions completed (simulated)") + check("closing the Emergency clears the report", False, reported(em["id"], later, "not closed")) + + register_check = {"now": rc["now"], "later": rc["later"], "checks": checks} + return cases, retry, register_check, failures + + +def main(argv=None) -> int: + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + ap.add_argument("--messages", type=Path, default=REPO / "data" / "fsi-simulation" / "messages.json") + ap.add_argument("--offering", type=Path, default=REPO / "data" / "cds" / "offering.json") + ap.add_argument("--output", type=Path, default=Path("fedramp-inbox-simulation.json")) + a = ap.parse_args(argv) + raw = a.messages.read_bytes() + doc = json.loads(raw) + cases, retry, register_check, failures = run(doc) + for f in failures: + print(f"::error::FedRAMP Security Inbox simulation: {f}") + if failures: + print(f"FedRAMP Security Inbox simulation: {len(failures)} outcome(s) differ from expected; nothing written") + return 1 + contact = ((json.loads(a.offering.read_text()).get("fedramp_security_inbox") or {}).get("contact")) + sha = os.environ.get("GITHUB_SHA", "") + report = { + "report_type": "fedramp-inbox-simulation", + "simulation": True, + "notice": NOTICE, + "engagement": _engagement.STATEMENT, + "contact": contact, + "emitted_at": datetime.now(timezone.utc).isoformat(), + "commit": sha if len(sha) == 40 and all(ch in "0123456789abcdef" for ch in sha) else None, + "logic": "scripts/_fsi.py", + "input": "data/fsi-simulation/messages.json", + "input_sha256": hashlib.sha256(raw).hexdigest(), + "rules_exercised": RULES, + "result": "pass", + "cases": cases, + "retry_pass": retry, + "register_check": register_check, + } + report = _offering.stamp_fedramp_id(report, a.offering) # CDS-CSO-FID + a.output.write_text(json.dumps(report, indent=2) + "\n") + print(f"FedRAMP Security Inbox simulation: {len(cases)} synthetic messages, all outcomes as expected; " + f"wrote {a.output} (SIMULATION: nothing received or sent)") + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/build-human-views.py b/scripts/build-human-views.py new file mode 100644 index 00000000..afa5b3da --- /dev/null +++ b/scripts/build-human-views.py @@ -0,0 +1,218 @@ +#!/usr/bin/env python3 +"""Complete human-readable views of the published certification data, checked +for consistency with the machine-readable originals (CDS-TRC-HMR, CDS-CSO-CBF). + +For each JSON (or CSV) artifact it writes `<name>.view.md`: every value in the +original, under its JSON Pointer path, grouped by top-level field. Each value +cell is the value's JSON encoding, so the view is lossless. Then it parses +every view back and fails unless it reproduces the original exactly. That +round trip is the automation that keeps the two formats consistent: a view +that dropped, changed or added a value would not reproduce its JSON, and the +build stops before anything is signed or published. + +The curated Markdown twins the generators write (`<name>.md`) are summaries +from the same in-memory data in the same run; the `.view.md` is the complete +one. Both are listed per artifact in the trust manifest. + + python3 scripts/build-human-views.py ksi-signal.json boundary-map.json iiw.csv ... +""" + +import csv +import json +import sys +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _signers # noqa: E402 + +SUFFIX = ".view.md" +HEADER = "| Path | Value |" +RULE = "|---|---|" + + +def _fail(msg): + raise SystemExit(f"::error::human views: {msg} (fail-closed)") + + +# --- JSON Pointer (RFC 6901) ------------------------------------------------------------ + +def _esc(seg): + return str(seg).replace("~", "~0").replace("/", "~1") + + +def _unesc(seg): + return seg.replace("~1", "/").replace("~0", "~") + + +def leaves(obj, path=""): + """(pointer, value) for every scalar, and for every empty list or object.""" + if isinstance(obj, dict) and obj: + for k, v in obj.items(): + yield from leaves(v, f"{path}/{_esc(k)}") + elif isinstance(obj, list) and obj: + for i, v in enumerate(obj): + yield from leaves(v, f"{path}/{i}") + else: + yield path, obj + + +def _cell(v): + return json.dumps(v, ensure_ascii=False).replace("\\", "\\\\").replace("|", "\\|") + + +def _uncell(s): + out, i = [], 0 + while i < len(s): + if s[i] == "\\" and i + 1 < len(s) and s[i + 1] in "\\|": + out.append(s[i + 1]) + i += 2 + else: + out.append(s[i]) + i += 1 + return json.loads("".join(out)) + + +# --- render and parse ----------------------------------------------------------------------- + +def render(name, data, kind="json"): + out = [f"# {name}: complete human-readable view", "", + f"_Every value in `{name}`, under its JSON Pointer path; each value is shown in its JSON encoding. " + "Generated from the signed original by scripts/build-human-views.py, and checked on every build to " + "reproduce it exactly._", "", f"- **Format:** {kind}", ""] + if kind == "csv": + data = {"rows": data} + groups = {} + for ptr, v in leaves(data): + top = ptr.split("/")[1] if ptr else "" + groups.setdefault(top, []).append((ptr, v)) + for top, rows in groups.items(): + out += [f"## {_unesc(top) or '(document)'}", "", HEADER, RULE] + out += [f"| `{ptr or '/'}` | {_cell(v)} |" for ptr, v in rows] + out.append("") + return "\n".join(out) + "\n" + + +def _split_row(line): + """('ptr', 'cell') from '| `ptr` | cell |', honouring escaped pipes in the cell.""" + if not line.startswith("| `"): + return None + end = line.index("` | ", 3) + return line[3:end], line[end + 4:-2] + + +def parse(text): + """The value a view describes. A container whose keys are exactly 0..n-1 is + read as a list; an object that happened to have such keys would not round + trip, and build() fails closed on it rather than publish a wrong view.""" + kind = "csv" if "- **Format:** csv" in text else "json" + root, whole = {}, None + for line in text.splitlines(): + row = _split_row(line) + if row is None: + continue + ptr, cell = row + value = _uncell(cell) + if ptr == "/": + whole = value + continue + segs = [_unesc(x) for x in ptr.split("/")[1:]] + node = root + for seg in segs[:-1]: + node = node.setdefault(seg, {}) + node[segs[-1]] = _Leaf(value) + if whole is not None: + return whole + data = _thaw(root) + return data.get("rows", []) if kind == "csv" else data + + +class _Leaf: + __slots__ = ("value",) + + def __init__(self, value): + self.value = value + + +def _thaw(node): + if isinstance(node, _Leaf): + return node.value + if node and set(node) == {str(i) for i in range(len(node))}: + return [_thaw(node[str(i)]) for i in range(len(node))] + return {k: _thaw(v) for k, v in node.items()} + + +def load(path): + p = Path(path) + if p.suffix == ".csv": + with p.open(newline="") as f: + return list(csv.reader(f)), "csv" + try: + return json.loads(p.read_text()), "json" + except json.JSONDecodeError as exc: + _fail(f"{p} is not valid JSON: {exc}") + + +def build(path): + p = Path(path) + data, kind = load(p) + text = render(p.name, data, kind) + back = parse(text) + if back != data: + _fail(f"{p.name}: the human-readable view does not reproduce the machine-readable original") + view = p.with_name(p.stem + SUFFIX) + view.write_text(text) + return view + + +def check(path, view): + """Re-read a written view and compare it with its original (used after the + views are written, and by verifiers on the published pair).""" + data, _ = load(path) + if parse(Path(view).read_text()) != data: + _fail(f"{Path(view).name} does not match {Path(path).name}") + + +# Published by something other than a workflow publish step (the runtime Lambda, +# the nightly beacon), so no workflow writes a view of them; the trust page +# renders them from the live JSON (scripts/_signers.py). +NOT_DEPLOY_PUBLISHED = _signers.VIEWLESS + + +def sources(freshness, d): + """The JSON and CSV artifacts in the governed freshness config that this + build has in directory d (absent optional ones are skipped).""" + out = [] + for a in json.loads(Path(freshness).read_text())["artifacts"]: + name = a["path"].rsplit("/", 1)[1] + if name.endswith((".json", ".csv")) and name not in NOT_DEPLOY_PUBLISHED and (Path(d) / name).is_file(): + out.append(Path(d) / name) + return out + + +def main(argv=None): + import argparse + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + ap.add_argument("paths", nargs="*") + ap.add_argument("--freshness", default=None, help="take every JSON/CSV artifact it lists that is in --dir") + ap.add_argument("--dir", default=".") + ap.add_argument("--list", default=None, help="append each written view's name to this file") + a = ap.parse_args(argv) + paths = [Path(p) for p in a.paths] + (sources(a.freshness, a.dir) if a.freshness else []) + if not paths: + _fail("no artifacts named") + written = [] + for p in paths: + if not p.is_file(): + _fail(f"{p} not found") + view = build(p) + check(p, view) + written.append(view.name) + print(f"human view: {view.name} reproduces {p.name}") + if a.list: + with open(a.list, "a") as f: + f.writelines(w + "\n" for w in written) + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/build-incident-report.py b/scripts/build-incident-report.py new file mode 100644 index 00000000..6f75a5eb --- /dev/null +++ b/scripts/build-incident-report.py @@ -0,0 +1,421 @@ +#!/usr/bin/env python3 +# ============================================================================= +# INCIDENT REPORTS: IIR, OIR and FIR from the incident register +# ============================================================================= +# The incident register (data/incidents.json, read through scripts/_incidents.py) +# records each incident's FedRAMP reportability evaluation (IEC-CSO-EFR), its +# Incident Rating (IEC-CSO-EFI, or the IEC-CSO-DPR default) and the reports +# issued. This renders, for every FedRAMP Reportable Incident, each report in +# FedRAMP's 2026-06-24 incident report schema: +# +# incident-<ID>-<NN>-initial.json IEC-CSO-IIR +# incident-<ID>-<NN>-ongoing.json IEC-CSO-OIR (restates every earlier item) +# incident-<ID>-<NN>-final.json IEC-CSO-FIR (final values for every item) +# +# each validated before it is written (scripts/_fedramp_schema.py), plus the +# incident log: +# +# incident-reports.json every incident, its evaluation and reason, its rating +# history, each report (file, sha256, what changed) and +# each report clock (due, issued, on time) +# incident-reports.md the same, human-readable, with every report's content +# +# The clocks are FedRAMP's Class C timeframes, read through scripts/_rules.py. +# +# Vulnerabilities as incidents (VER-TFR-IRI, VER-TFR-NRI). Given the VDR report, +# policies/triage.rego names each finding a rule makes a FedRAMP Reportable +# Incident. One the operator has adopted that rule for and that no unresolved +# incident names is published as a trigger with no incident, its Initial +# report due from the finding's first evaluation at the default rating; the +# clock check fails, and the evidence watchdog pages, once that time passes. +# +# Notification. Nothing is sent to FedRAMP or to agencies: the register's +# policy says "published-only" and every report says so. After this builder, +# scripts/deliver-incident-reports.py "delivers" each report to SIMULATED +# FedRAMP and agency recipients and writes the delivery log. +# +# build-incident-report.py --incidents ../data/incidents.json --vdr vdr-report.json --out-dir . +# build-incident-report.py --check incident-reports.json # exit 1 if a report is overdue +# ============================================================================= + +import argparse +import hashlib +import json +import sys +from datetime import datetime, timezone +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _engagement # noqa: E402 +import _offering # noqa: E402 +import _fedramp_schema as fs # noqa: E402 +import _incidents # noqa: E402 +import _rules # noqa: E402 + +INDEX = "incident-reports.json" +INDEX_MD = "incident-reports.md" +EXERCISE_PREFIX = "EXERCISE: a simulated incident; no real system, data or agency was affected. " + +# The items an Initial report carries (IEC-CSO-IIR) and the further items an +# Ongoing report adds (IEC-CSO-OIR), in the rules' order, by register field. +IIR_ITEMS = [("coordinator", "Federal incident response coordinator"), + ("tracking_id", "Provider tracking identifier"), + ("description", "Description of the incident"), + ("timeline", "Timeline"), + ("rating", "Potential Agency Impact N-rating (historical and current)"), + ("functional_impact", "Functional impact to federal agency customers"), + ("recovery_plan", "Estimated recovery plan, milestones and timelines"), + ("affected_agencies", "Likely affected customer agencies")] +OIR_ITEMS = [("observed_activity", "Observed incident activity"), + ("indicators_of_compromise", "Indicators of compromise"), + ("related_cves", "Related CVE identifiers"), + ("root_cause", "Root cause"), + ("response_and_recovery_activities", "Response and recovery activities")] + + +def _fail(msg): + raise SystemExit(f"::error::incident reports: {msg} (fail-closed)") + + +def _iso(dt): + return dt.astimezone(timezone.utc).isoformat().replace("+00:00", "Z") + + +def vulnerability_triggers(vdr): + """The VDR findings policies/triage.rego treats as FedRAMP Reportable Incidents.""" + import _triage + findings = [{k: f.get(k) for k in ("tracking_id", "cve", "pain", "internet_reachable", "likely_exploitable", + "fully_mitigated", "final_disposition", "first_evaluated")} + for f in vdr.get("findings", [])] + out = _triage.evaluate('{"triggers": data.vdr.triage.incident_triggers, ' + '"errors": data.vdr.triage.incident_errors}', {"findings": findings}) + if out.get("errors"): + _fail("; ".join(sorted(out["errors"]))) + if not isinstance(out.get("triggers"), list): + _fail("the triage policy returned no incident triggers") + return out["triggers"] + + +def _milestones(inc, upto, default): + """Every milestone known at `upto`: the register's, plus the ones the + register's own fields mark (evaluation, each rating, resolution, recovery).""" + ms = [] + for r in inc["reports"]: + if _incidents.parse_ts(r["at"], "") > upto: + break + ms += [(m["at"], m["description"]) for m in r.get("set", {}).get("milestones", [])] + ev = inc["evaluation"] + ms.append((ev["evaluated_at"], f"FedRAMP reportability evaluated ({ev['basis']}): reportable; " + f"rated N{default} by default (IEC-CSO-DPR)")) + for e in inc["estimates"]: + ms.append((e["estimated_at"], f"Incident Rating estimated N{e['rating']} (IEC-CSO-EFI)")) + for k, text in (("resolved_at", "Incident resolved"), ("recovery_complete_at", "Recovery complete")): + if k in inc: + ms.append((inc[k], text)) + known = [(at, d) for at, d in ms if _incidents.parse_ts(at, "") <= upto] + return [{"occurredAt": at, "milestoneDescription": d} + for at, d in sorted(known, key=lambda x: _incidents.parse_ts(x[0], ""))] + + +def _state(inc, k): + """The register fields as known after report k, and which report last set each.""" + state, set_by = {}, {} + for i, r in enumerate(inc["reports"][:k + 1]): + for key, val in r.get("set", {}).items(): + if key != "milestones": + state[key], set_by[key] = val, i + return state, set_by + + +def _rating_notes(inc, at, default): + rating, basis = _incidents.rating_at(inc, at, default) + hist = [f"N{r} from {when} ({b})" for when, r, b in _incidents.rating_history(inc, default, at)] + if basis.startswith("default"): + lead = (f"No Incident Rating estimate had been made; rated N{rating} by default as IEC-CSO-DPR requires.") + else: + e = [x for x in inc["estimates"] if _incidents.parse_ts(x["estimated_at"], "") <= at][-1] + scope = "one agency" if e["agencies"] == "single" else "more than one agency" + lead = (f"Estimated N{rating} under IEC-CSO-EFI: a likely {e['customer_effect']} customer effect on " + f"{scope}. {e['reason']}") + return rating, f"{lead} History: {'; '.join(hist)}." + + +def report_document(inc, k, policy, default): + """Report k of incident `inc` in the FedRAMP incident report schema. Every + item set by report k or earlier is restated with its latest value.""" + r = inc["reports"][k] + at = _incidents.parse_ts(r["at"], "") + state, _ = _state(inc, k) + rating, notes = _rating_notes(inc, at, default) + doc = { + "$schema": fs.stamp("incident"), + "certificationPackageOverviewUri": fs.CPO_URI, + "reportType": r["type"], + "providerTrackingId": inc["id"], + "federalIncidentCoordinator": policy["federal_incident_coordinator"], + "incidentDescription": (EXERCISE_PREFIX if inc["exercise"] else "") + state["description"], + "timeline": { + "startedAt": inc["started_at"], + "detectedAt": inc["detected_at"], + "detectionSource": inc["detection_source"], + "evaluationCompletedAt": inc["evaluation"]["evaluated_at"], + "milestones": _milestones(inc, at, default), + }, + "potentialImpact": { + "historicalRating": [n for _, n, _ in _incidents.rating_history(inc, default, at)], + "currentRating": rating, + "evaluationNotes": notes, + }, + # DEC-194: the report's recipients are simulated; nothing is sent. + "providerExtensions": {"engagement": _engagement.STATEMENT}, + } + for key, field in _incidents.TEXT_FIELDS.items(): + if key in state and key != "description": + doc[field] = state[key] + for key, field in _incidents.LIST_FIELDS.items(): + if key in state: + doc[field] = state[key] + if r["type"] == "Final": + doc["resolvedAt"] = inc["recovery_complete_at"] + return doc + + +def _changes(inc, k): + """{item: "updated" | "no update" | "not yet available"} for report k.""" + state, set_by = _state(inc, k) + out = {} + for key, _ in IIR_ITEMS + OIR_ITEMS: + if key in ("coordinator", "tracking_id"): + out[key] = "updated" if k == 0 else "no update" + elif key == "timeline": + out[key] = "updated" if k == 0 or inc["reports"][k].get("set", {}).get("milestones") else "no update" + elif key == "rating": + prev = _incidents.parse_ts(inc["reports"][k - 1]["at"], "") if k else None + now = _incidents.parse_ts(inc["reports"][k]["at"], "") + moved = k == 0 or any(prev < _incidents.parse_ts(e["estimated_at"], "") <= now for e in inc["estimates"]) + out[key] = "updated" if moved else "no update" + elif key not in state: + out[key] = "not yet available" + else: + out[key] = "updated" if set_by[key] == k else "no update" + return out + + +def build(reg, vdr, now, out_dir, rules_dir=_rules.RULES_DIR): + """Write every report and the incident log; return the log.""" + out_dir = Path(out_dir) + timeframes = _rules.incident_report_timeframes(rules_dir) + default = _rules.default_incident_rating(rules_dir) + policy = reg["policy"] + registry = fs.load_registry() + incidents, due = [], [] + for inc in reg["incidents"]: + reports = [] + for k, r in enumerate(inc["reports"]): + name = f"incident-{inc['id']}-{k + 1:02d}-{r['type'].lower()}.json" + fs.write_validated(_offering.stamp_fedramp_id(report_document(inc, k, policy, default)), "incident", + out_dir / name, registry) + reports.append({"type": r["type"], "issued_at": r["at"], "file": name, + "sha256": hashlib.sha256((out_dir / name).read_bytes()).hexdigest(), + "changes": _changes(inc, k)}) + obligations = _incidents.obligations(inc, timeframes, default, now) + pending = [o for o in obligations if o["report_index"] is None] + for o in pending: + due.append({"incident": inc["id"], "finding": None, "report": o["report"], "due_at": o["due_at"], + "overdue": o["overdue"]}) + last = inc["reports"][-1]["at"] if inc["reports"] else inc["evaluation"]["evaluated_at"] + rating, basis = _incidents.rating_at(inc, _incidents.parse_ts(last, ""), default) + incidents.append({ + "id": inc["id"], "title": inc["title"], "exercise": inc["exercise"], + "status": _incidents.status(inc), + "detected_at": inc["detected_at"], "detection_source": inc["detection_source"], + "evaluation": inc["evaluation"], "findings": inc.get("findings", []), + "rating": ({"current": rating, "basis": basis, + "history": [{"from": w, "rating": n, "basis": b} + for w, n, b in _incidents.rating_history(inc, default)]} + if inc["evaluation"]["reportable"] else None), + "resolved_at": inc.get("resolved_at"), "recovery_complete_at": inc.get("recovery_complete_at"), + "reports": reports, "obligations": obligations, + "next_report_due_at": pending[0]["due_at"] if pending else None, + }) + + triggers = [] + covered = _incidents.open_findings(reg) + if vdr is not None: + for t in vulnerability_triggers(vdr): + adopted = t["rule"] in policy["adopted_vulnerability_rules"] + inc_id = covered.get(t["tracking_id"]) or (covered.get(t["cve"]) if t["cve"] else None) + entry = {**t, "adopted": adopted, "incident": inc_id} + triggers.append(entry) + if adopted and inc_id is None: + start = _incidents.parse_ts(t["first_evaluated"], "") if t["first_evaluated"] else now + unit, n = timeframes["iir"][default] + at = _incidents.add_clock(start, unit, n) + due.append({"incident": None, "finding": t["tracking_id"], "report": "Initial", + "due_at": at.isoformat(), "overdue": now > at}) + overdue = [d for d in due if d["overdue"]] + log = { + "schema": "incident-reports/1", + "emitted_at": _iso(now), + "generator": "scripts/build-incident-report.py", + "description": ("The incident log: every incident recorded in data/incidents.json, its FedRAMP " + "reportability evaluation and reason (IEC-CSO-EFR), its Incident Rating (IEC-CSO-EFI, " + "or the IEC-CSO-DPR default), each Initial, Ongoing and Final report issued, and each " + "Class C report clock. Exercises are marked exercise: true."), + "rules": _rules.pin(rules_dir), + "notification": {"mode": policy["notification"], "text": policy["notification_text"]}, + "engagement": _engagement.STATEMENT, + "policy": {k: policy[k] for k in ("federal_incident_coordinator", "adopted_vulnerability_rules", + "federal_customer_data", "decided_by", "decided_on", "review_by")}, + "vdr": ({"emitted_at": vdr.get("emitted_at"), "report_id": vdr.get("report_id")} if vdr is not None + else None), + "vulnerability_triggers": triggers, + "obligations_due": due, + "clock_status": "overdue" if overdue else "ok", + "summary": { + "incidents": len(incidents), + "reportable": sum(1 for i in incidents if i["evaluation"]["reportable"]), + "open": sum(1 for i in incidents if i["status"] in ("open", "resolved")), + "exercises": sum(1 for i in incidents if i["exercise"]), + "reports": sum(len(i["reports"]) for i in incidents), + "triggers_without_incident": sum(1 for t in triggers if t["adopted"] and t["incident"] is None), + "overdue": len(overdue), + }, + "incidents": incidents, + } + log = _offering.stamp_fedramp_id(log) # CDS-CSO-FID + (out_dir / INDEX).write_text(json.dumps(log, indent=2) + "\n") + (out_dir / INDEX_MD).write_text(render_markdown(log, out_dir) + "\n") + return log + + +def _item_text(key, doc): + if key == "coordinator": + return doc["federalIncidentCoordinator"] + if key == "tracking_id": + return doc["providerTrackingId"] + if key == "description": + return doc["incidentDescription"] + if key == "timeline": + t = doc["timeline"] + lines = [f"started {t['startedAt']}; detected {t['detectedAt']} by {t['detectionSource']}; " + f"reportability evaluated {t['evaluationCompletedAt']}"] + lines += [f"{m['occurredAt']}: {m['milestoneDescription']}" for m in t["milestones"]] + return "\n".join(f" - {x}" for x in lines) + if key == "rating": + p = doc["potentialImpact"] + return f"N{p['currentRating']} (history {', '.join(f'N{n}' for n in p['historicalRating'])}). " \ + f"{p['evaluationNotes']}" + field = _incidents.TEXT_FIELDS.get(key) or _incidents.LIST_FIELDS.get(key) + val = doc.get(field) + if isinstance(val, list): + return ", ".join(val) if val else "none" + return val or "not yet available" + + +def render_markdown(log, out_dir): + s = log["summary"] + out = ["# Incident log and reports", "", + "_Generated by scripts/build-incident-report.py from data/incidents.json. The JSON beside this file " + "(incident-reports.json, signed) is the record; this is a rendering of it._", "", + f"- **Emitted:** {log['emitted_at']}", + f"- **Incidents:** {s['incidents']} ({s['reportable']} FedRAMP Reportable; {s['exercises']} exercises); " + f"**reports issued:** {s['reports']}; **overdue:** {s['overdue']}", + f"- **Notification:** {log['notification']['mode']}. {log['notification']['text']}", + f"- **Federal incident response coordinator:** {log['policy']['federal_incident_coordinator']}", + f"- **Vulnerabilities treated as incidents:** {', '.join(log['policy']['adopted_vulnerability_rules'])}", + ""] + out += ["## Vulnerabilities that are FedRAMP Reportable Incidents (VER-TFR-IRI / VER-TFR-NRI)", ""] + if log["vdr"] is None: + out += ["No VDR report was supplied to this build.", ""] + elif not log["vulnerability_triggers"]: + out += [f"None in the VDR report emitted {log['vdr']['emitted_at']}.", ""] + else: + out += ["| Finding | Rule | PAIN | Adopted | Incident |", "|---|---|---|---|---|"] + out += [f"| `{t['tracking_id']}` | {t['rule']} | {t['pain']} | {t['adopted']} | {t['incident'] or 'NONE'} |" + for t in log["vulnerability_triggers"]] + out.append("") + if log["obligations_due"]: + out += ["## Reports due", "", "| Incident / finding | Report | Due | Overdue |", "|---|---|---|---|"] + out += [f"| {d['incident'] or d['finding']} | {d['report']} | {d['due_at']} | {d['overdue']} |" + for d in log["obligations_due"]] + out.append("") + for entry in log["incidents"]: + ev = entry["evaluation"] + out += [f"## {entry['id']}: {entry['title']}" + (" (EXERCISE)" if entry["exercise"] else ""), "", + f"- **Status:** {entry['status']}", + f"- **Detected:** {entry['detected_at']} by {entry['detection_source']}", + f"- **Reportability (IEC-CSO-EFR, evaluated {ev['evaluated_at']}, basis {ev['basis']}):** " + f"{'FedRAMP Reportable Incident' if ev['reportable'] else 'not a FedRAMP Reportable Incident'}. " + f"{ev['reason']}", + f"- **Federal customer data considered:** {ev['federal_customer_data_considered']}"] + if entry["findings"]: + out.append(f"- **Findings named:** {', '.join(f'`{f}`' for f in entry['findings'])}") + if entry["rating"]: + out.append(f"- **Rating:** N{entry['rating']['current']} ({entry['rating']['basis']})") + if entry["obligations"]: + out += ["", "| Report | Due | Issued | On time |", "|---|---|---|---|"] + out += [f"| {o['report']} | {o['due_at']} | {o['issued_at'] or 'not yet'} | " + f"{'yes' if o['on_time'] else 'no' if o['on_time'] is False else ('OVERDUE' if o['overdue'] else 'pending')} |" + for o in entry["obligations"]] + out.append("") + for k, rep in enumerate(entry["reports"]): + doc = json.loads((Path(out_dir) / rep["file"]).read_text()) + out += [f"### {rep['type']} report, issued {rep['issued_at']} ({rep['file']})", "", + f"_Notification: {log['notification']['mode']}; see above._", ""] + items = IIR_ITEMS + (OIR_ITEMS if k else + [x for x in OIR_ITEMS if rep["changes"][x[0]] != "not yet available"]) + for key, label in items: + change = rep["changes"][key] + text = _item_text(key, doc) + sep = "\n" if text.startswith(" - ") else " " + out.append(f"- **{label}** ({change}):{sep}{text}") + if rep["type"] == "Final": + out.append(f"- **Resolved and recovered:** {doc['resolvedAt']}") + out.append("") + return "\n".join(out).rstrip() + + +def check(index_path, now): + """Exit status for the clock check: 1 when a report is due and missing.""" + log = json.loads(Path(index_path).read_text()) + late = [d for d in log.get("obligations_due", []) + if _incidents.parse_ts(d["due_at"], "obligations_due.due_at") < now] + for d in late: + who = d["incident"] or f"finding {d['finding']} (no incident opened)" + print(f"::error::{who}: the {d['report']} incident report was due at {d['due_at']} and has not been issued") + if not late: + print(f"incident report clocks: ok ({len(log.get('obligations_due', []))} report(s) pending, none overdue)") + return 1 if late else 0 + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__) + ap.add_argument("--incidents", default=str(_incidents.DEFAULT_PATH)) + ap.add_argument("--vdr", default=None, help="the built VDR report, for VER-TFR-IRI/NRI triggers") + ap.add_argument("--out-dir", default=".") + ap.add_argument("--now", default=None, help="ISO 8601 time to evaluate the clocks at (default: now)") + ap.add_argument("--check", default=None, metavar="INDEX", + help="check a built incident-reports.json and exit 1 if a report is overdue") + a = ap.parse_args(argv) + now = _incidents.parse_ts(a.now, "--now") if a.now else datetime.now(timezone.utc) + if a.check: + return check(a.check, now) + reg = _incidents.load(a.incidents, now=now) + vdr = None + if a.vdr: + try: + vdr = json.loads(Path(a.vdr).read_text()) + except (OSError, json.JSONDecodeError) as exc: + _fail(f"cannot read the VDR report {a.vdr}: {exc}") + if not isinstance(vdr, dict) or not isinstance(vdr.get("findings"), list): + _fail(f"{a.vdr} is not a VDR report") + log = build(reg, vdr, now, a.out_dir) + s = log["summary"] + print(f"incident reports: {s['incidents']} incident(s), {s['reports']} report(s), " + f"{s['triggers_without_incident']} trigger(s) without an incident, clocks {log['clock_status']}") + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/build-ksi-signal.py b/scripts/build-ksi-signal.py index 1d570b1c..b9a0f8c9 100755 --- a/scripts/build-ksi-signal.py +++ b/scripts/build-ksi-signal.py @@ -39,6 +39,7 @@ # runnable standalone from any working directory (see scripts/_common.py). sys.path.insert(0, os.path.dirname(os.path.abspath(__file__))) from _common import sha256_file # noqa: E402 +import _offering # noqa: E402 import _redact # noqa: E402 # ============================================================================= @@ -70,6 +71,14 @@ "aws_iam_role": "iam_role", "aws_iam_role_policy": "iam_policy", "aws_iam_policy": "iam_policy", # managed policy (e.g., bootstrap assessment-readonly) + # The operators and read-only groups' inline policies, and the managed-policy + # attachments on the deploy/plan roles and the groups (bootstrap). Scanners + # name these blocks in findings, so they are components a finding resolves + # to. An attachment block is one component however many policies its + # for_each attaches: the finding names the block, not an instance. + "aws_iam_group_policy": "iam_policy", + "aws_iam_role_policy_attachment": "iam_policy", + "aws_iam_group_policy_attachment": "iam_policy", # CI/CD identity plane (infrastructure/bootstrap): the GitHub OIDC provider, # the deploy/assessment roles (aws_iam_role above), and the operators group. # These are the highest-privilege identities governing the production system, @@ -141,6 +150,14 @@ "aws_s3_bucket_public_access_block": "object_store", "aws_s3_bucket_policy": "object_store", "aws_cloudfront_response_headers_policy": "cdn_distribution", + # The edge function that maps directory URLs to their index page, and the + # CloudFront standard-logging (v2) delivery that writes the edge access + # records (CDS-TRC-ACL; bootstrap/trust-access-logs.tf) are facets of the + # distribution they run on and log. + "aws_cloudfront_function": "cdn_distribution", + "aws_cloudwatch_log_delivery_source": "cdn_distribution", + "aws_cloudwatch_log_delivery_destination": "cdn_distribution", + "aws_cloudwatch_log_delivery": "cdn_distribution", # API Gateway sub-resources fold into the api_gateway component so a consumer # sees one interface with its route/integration/stage config, not four things. "aws_apigatewayv2_integration": "api_gateway", @@ -156,6 +173,30 @@ "aws_sns_topic_policy": "notification_topic", } +# Terraform resource types declared under infrastructure/ that are neither a +# component (TYPE_BY_TF_TYPE) nor folded into one (ATTRIBUTE_PARENTS), each with +# the reason. tests/test_inventory_types.py fails when a type declared in the +# Terraform is in none of the three, so a new resource cannot be silently +# dropped from the inventory. +NOT_INVENTORIED = { + "aws_cloudfront_origin_access_control": "The signing configuration CloudFront uses to read the site bucket; the distribution's origin settings and the bucket policy that admits only it are inventoried with those components.", + "aws_cloudwatch_event_target": "Binds an EventBridge rule to the Lambda it invokes; both are components, and the boundary map draws the binding as an edge (scripts/build-boundary-graph.py CONNECTOR_TYPES).", + "aws_cloudwatch_log_resource_policy": "Lets a service write to a log group; the log group is a component and the boundary map draws the binding as an edge.", + "aws_iam_account_password_policy": "An account-level IAM setting, not a resource that holds or moves data; the live value is compared with the Secure Configuration Guide on every deploy (aws-account.password-policy).", + "aws_iam_user_group_membership": "Places the operator user in its group; the group is a component, and user names are never published.", + "aws_kms_alias": "A name for a KMS key; the key is the component, and the boundary map uses the alias only to resolve references to it.", + "aws_lambda_permission": "Lets a service invoke a Lambda; both are components, and the boundary map draws the grant as an edge.", + "aws_route53_hosted_zone_dnssec": "The zone's DNSSEC signing switch; the zone is a component and its signing status is read live by the runtime emitter (dnssec_not_signing).", + "aws_route53_key_signing_key": "The zone's DNSSEC key-signing key binding; the KMS key behind it (dnssec_ksk) is the component.", + "aws_route53_query_log": "Connects the zone to its query-log group; both are components, and the boundary map draws the binding as an edge.", + "aws_route53_record": "DNS records of the inventoried zone; they hold no data and the boundary map uses them only to connect the zone to what they point at.", + "aws_s3_bucket_lifecycle_configuration": "A bucket setting (object expiry); each data store's retention is stated and checked in data/minimum-assessment-scope.json.", + "aws_s3_bucket_logging": "Connects the site bucket to the access-log bucket; both are components, and the boundary map and the MAS flows show the connection.", + "aws_s3_bucket_ownership_controls": "A bucket setting (object ownership enforced); the bucket is the component.", + "terraform_data": "A Terraform-internal value with no cloud resource behind it.", +} + + # ============================================================================= # MAS (Minimum Assessment Scope) attributes per component type # ============================================================================= @@ -393,7 +434,7 @@ "function": "Public TLS certificate for the CDN", "diagram_label": "ACM TLS certificate", "public": False, - "baseline_configuration": "AWS ACM-managed; auto-renewing; FIPS-validated cipher suites via CloudFront", + "baseline_configuration": "AWS ACM-managed; auto-renewing; TLS 1.2+ via CloudFront (TLSv1.2_2021)", "iiw_asset_type": "TLS Certificate (ACM)", }, "event_schedule": { @@ -556,6 +597,12 @@ ("iam_role", "evidence_nightly"): { "function": "Nightly evidence workflow role", }, + ("iam_role", "incident_reports"): { + "function": "Incident reports workflow role (unattended IIR/OIR/FIR publication)", + }, + ("iam_role", "package_maintenance"): { + "function": "Certification package maintenance workflow role (unattended SDR, CPO and OCR publication)", + }, ("object_store", "logs"): { "function": "Access-log bucket for the site bucket and CDN", "diagram_label": "S3 access-log bucket", @@ -905,6 +952,29 @@ def component_id_for_html(rel_path): # ============================================================================= +POLICY_ATTACHMENT_TYPES = ("aws_iam_role_policy_attachment", "aws_iam_group_policy_attachment") + + +def _policy_holder(values): + """('role' | 'group', name) an attachment attaches its policy to.""" + if values.get("group"): + return "group", values["group"] + return "role", values.get("role") or "unknown" + + +def _add_attached_policy(component, values): + """Record an attached managed policy by name only (and whether AWS manages + it); its ARN carries the account ID, which is never published.""" + arn = str(values.get("policy_arn") or "") + if not arn: + return + entry = {"policy_name": arn.rsplit("/", 1)[-1], "aws_managed": arn.startswith("arn:aws:iam::aws:")} + attached = component.setdefault("attributes", {}).setdefault("attached_policies", []) + if entry not in attached: + attached.append(entry) + attached.sort(key=lambda e: (e["policy_name"], e["aws_managed"])) + + def build_cloud_components(tf_state, tf_outputs, module_dir="infrastructure/main.tf"): """Walk Terraform state into normalized cloud components. @@ -937,9 +1007,17 @@ def build_cloud_components(tf_state, tf_outputs, module_dir="infrastructure/main # name; the key keeps their ids distinct. count indexes (int) stay out # of the id so existing component ids do not change. tf_index = r.get("index") + values = r.get("values", {}) or {} + if tf_type in POLICY_ATTACHMENT_TYPES: + # One component per attachment block; each instance adds the + # attached policy's name (never its ARN: it carries the account ID). + cid = component_id_for_cloud(tf_name, normalized) + if cid in components_by_id: + _add_attached_policy(components_by_id[cid], values) + continue + tf_index = None id_name = f"{tf_name}[{tf_index}]" if isinstance(tf_index, str) else tf_name cid = component_id_for_cloud(id_name, normalized) - values = r.get("values", {}) or {} attrs = { "tf_address": r.get("address"), @@ -948,10 +1026,19 @@ def build_cloud_components(tf_state, tf_outputs, module_dir="infrastructure/main } if isinstance(tf_index, str): attrs["tf_index"] = tf_index + if tf_type in POLICY_ATTACHMENT_TYPES: + attrs["tf_address"] = re.sub(r"\[[^\]]*\]$", "", str(r.get("address") or f"{tf_type}.{tf_name}")) # Pull a few common, non-sensitive identifying attributes if present. for key in ("region", "runtime", "function_name", "id", "domain_name"): if key in values and values[key] is not None: attrs[key] = values[key] + # The deployed code's hash as AWS reported it at apply. The runtime + # emitter compares the live CodeSha256 with it daily, so code changed + # outside the deploy (and never inventoried or scanned) is detected. + if normalized == "function": + code_hash = values.get("code_sha256") or values.get("source_code_hash") + if code_hash: + attrs["code_sha256"] = code_hash # Per-resource ARN first: each resource's identity comes from its OWN # state block (values["arn"]), never from a shared whole-stack output — @@ -979,6 +1066,12 @@ def _output_arn(name): # role-name plus policy-name pair so the component is addressable. if values.get("arn"): native_id = values["arn"] + elif tf_type in POLICY_ATTACHMENT_TYPES: + kind, holder = _policy_holder(values) + native_id = f"iam-{kind}-policy-attachment::{holder}/{tf_name}" + elif tf_type == "aws_iam_group_policy": + group_name = values.get("group") or "unknown" + native_id = f"iam-group-policy::{group_name}/{values.get('name') or 'inline'}" else: role_name = values.get("role") or values.get("role_name") or "unknown" policy_name = values.get("name") or "inline" @@ -1013,7 +1106,20 @@ def _output_arn(name): attrs["policy_document_sha256"] = hashlib.sha256(_redact.redact_text(body_str).encode()).hexdigest() attrs["policy_name"] = values.get("name") attrs["attached_to_role"] = values.get("role") or values.get("role_name") - if attrs["attached_to_role"]: + if values.get("group"): + attrs["attached_to_group"] = values["group"] + if tf_type in POLICY_ATTACHMENT_TYPES: + kind, holder = _policy_holder(values) + attrs["policy_name"] = None + attrs["attached_policies"] = [] + derived_text = {"function": f"Managed policies attached to {kind} {holder}", + "baseline_configuration": f"Managed-policy attachment to {kind} {holder}; " + f"policy names in attributes (block in {module_dir})"} + elif attrs.get("attached_to_group"): + derived_text = {"function": f"Inline policy on group {attrs['attached_to_group']}", + "baseline_configuration": f"Inline policy on group {attrs['attached_to_group']}; " + f"body hashed in attributes (body in {module_dir})"} + elif attrs["attached_to_role"]: derived_text = {"function": f"Inline policy on role {attrs['attached_to_role']}", "baseline_configuration": f"Inline policy on role {attrs['attached_to_role']}; body " f"hashed in attributes (body in {module_dir})"} @@ -1031,6 +1137,8 @@ def _output_arn(name): apply_iiw_defaults(component) apply_classification_defaults(component) components_by_id[cid] = component + if tf_type in POLICY_ATTACHMENT_TYPES: + _add_attached_policy(component, values) # Second pass: fold attribute resources into their parent. for r in state_resources: @@ -1098,6 +1206,13 @@ def build_bootstrap_components(existing=(), bootstrap_dir="bootstrap"): seen = by_native.get(c.get("native_id")) or by_cid.get(c.get("component_id")) if seen is not None: seen.setdefault("attributes", {})["managed_by"] = "bootstrap" + # Facets folded in from the managing stack (the distribution's edge + # function and access-log delivery are declared in bootstrap). + folded = (c.get("attributes") or {}).get("config") or {} + if folded: + cfg = seen["attributes"].setdefault("config", {}) + for k, v in folded.items(): + cfg.setdefault(k, v) continue c.setdefault("attributes", {})["tf_module"] = "bootstrap" fresh.append(c) @@ -1170,7 +1285,7 @@ def build_live_log_groups(existing_components, region="us-east-2"): def build_npm_components(lock_path, function=None, lifecycle="runtime", - existing_components=None): + existing_components=None, deployed_in=None): """Read package-lock.json (lockfileVersion 3) and emit npm components. lifecycle distinguishes what a package is doing here. "runtime" means it @@ -1186,6 +1301,10 @@ def build_npm_components(lock_path, function=None, lifecycle="runtime", package@version can appear in more than one lockfile and the inventory holds one component per PURL. Earlier callers win, so a package that is both shipped and used at build time keeps its runtime classification. + + deployed_in names the function component whose deployment package holds + this tree, so the runtime emitter's package-integrity check can name the + packages it vouches for. """ if not lock_path.exists(): return [] @@ -1232,11 +1351,13 @@ def build_npm_components(lock_path, function=None, lifecycle="runtime", component["attributes"]["lifecycle"] = lifecycle if function: component["attributes"]["function"] = function + if deployed_in: + component["attributes"]["deployed_in"] = deployed_in components.append(component) return components -def build_sbom_components(sbom_path, existing_components=None): +def build_sbom_components(sbom_path, existing_components=None, deployed_in=None): """Read a CycloneDX JSON SBOM and emit software components for the inventory. Used to ingest the Silk Reeling app's dependency trees — the Python (PyPI) @@ -1316,6 +1437,8 @@ def build_sbom_components(sbom_path, existing_components=None): "function": role, }, } + if deployed_in: + component["attributes"]["deployed_in"] = deployed_in apply_mas_defaults(component) apply_iiw_defaults(component) apply_classification_defaults(component) @@ -1326,6 +1449,9 @@ def build_sbom_components(sbom_path, existing_components=None): THIRD_PARTY_PATH = Path(__file__).resolve().parent.parent / "data" / "third-party-components.json" NOT_RECORDED = "not recorded" TPR_FIELDS = ("upstream_offering", "upstream_component_id", "responsibility_split") +# MAS-CSO-TPR: what FedRAMP requires documented about each third-party +# information resource. A decided record must carry every one. +MAS_TPR_FIELDS = ("usage_and_configuration", "justification", "mitigations", "compensating_controls") def load_third_party_records(path, known_ids): @@ -1347,18 +1473,24 @@ def load_third_party_records(path, known_ids): split = rec.get("responsibility_split") if split is not None and not (isinstance(split, dict) and split.get("upstream_runs") and split.get("provider_configures")): raise SystemExit(f"::error::third-party record for {cid}: responsibility_split needs upstream_runs and provider_configures") + if rec.get("decided_by") and rec.get("decided_on"): + missing = [f for f in MAS_TPR_FIELDS if not (isinstance(rec.get(f), str) and rec[f].strip())] + if missing: + raise SystemExit(f"::error::third-party record for {cid} is decided but lacks {', '.join(missing)} " + "(MAS-CSO-TPR)") return recs def third_party_attributes(rec): """The TPR-1 fields for one component. A record without a decision (decided_by and decided_on) publishes every field as "not recorded".""" + fields = (*TPR_FIELDS, *MAS_TPR_FIELDS) if rec is None: - return {**{f: NOT_RECORDED for f in TPR_FIELDS}, "third_party_record": {"status": "no record"}} + return {**{f: NOT_RECORDED for f in fields}, "third_party_record": {"status": "no record"}} if not (rec.get("decided_by") and rec.get("decided_on")): - return {**{f: NOT_RECORDED for f in TPR_FIELDS}, + return {**{f: NOT_RECORDED for f in fields}, "third_party_record": {"status": "drafted; no decision recorded"}} - out = {f: rec.get(f) or NOT_RECORDED for f in TPR_FIELDS} + out = {f: rec.get(f) or NOT_RECORDED for f in fields} out["third_party_record"] = {"status": "decided", "decided_by": rec["decided_by"], "decided_on": rec["decided_on"]} return out @@ -1370,8 +1502,8 @@ def build_external_components(third_party_path=THIRD_PARTY_PATH): These services aren't in Terraform state (they're upstream public services or operator-account scaffolding); they're declared here so the canonical inventory matches the Authorization Boundary Diagram. Identifiers are the - public service URLs where applicable; for Duo specifically the identifier - is opaque (no tenant ID exposed). + public service URLs where applicable; for the operator's TOTP authenticator + the identifier is opaque (it has no tenant). """ services = [ { @@ -1413,10 +1545,13 @@ def build_external_components(third_party_path=THIRD_PARTY_PATH): { "id": "ext::duo-mfa", "native_id": "duo:operator-mfa", - "name": "Duo (operator MFA)", - "purpose": "Multi-factor authentication for AWS root and the GitHub account", + "name": "Duo Mobile (operator TOTP authenticator)", + "purpose": "Authenticator app that generates the virtual TOTP codes used as the second factor on the AWS " + "root user, the operator IAM user and the GitHub account (DEC-025, DEC-150). AWS and GitHub " + "enforce the MFA; the app only generates codes", "cia_impact": "privileged-account authentication", - "verification": "Operator-side configuration; tenant identifier intentionally not published in this inventory.", + "verification": "The deploy reads the root user's and the operator user's MFA on every run " + "(scripts/check-secure-config.py); the app holds no tenant identifier to publish.", "fedramp_status": "external; no separate FedRAMP authorization", }, { @@ -1437,6 +1572,47 @@ def build_external_components(third_party_path=THIRD_PARTY_PATH): "verification": "U.S. federal government source", "fedramp_status": "external; U.S. federal government source", }, + # MAS-CSO-IIR: the vulnerability-data feeds the VDR build also reads + # (scripts/fetch-detection-feeds.sh, evidence-nightly.yml's grype scan). + { + "id": "ext::first-epss", + "native_id": "https://epss.cyentia.com/epss_scores-current.csv.gz", + "name": "FIRST Exploit Prediction Scoring System (EPSS) scores", + "purpose": "Daily exploit-likelihood scores the VDR uses to rate findings", + "cia_impact": "VDR ingest accuracy", + "verification": "Public feed; a failed fetch fails the detection gate (G7) rather than scoring with no data", + "fedramp_status": "external; no separate FedRAMP authorization", + }, + { + "id": "ext::anchore-grype-db", + "native_id": "https://grype.anchore.io/databases", + "name": "Grype vulnerability database (Anchore)", + "purpose": "The vulnerability database Grype matches the SBOMs against on every deploy and nightly scan", + "cia_impact": "VDR ingest accuracy", + "verification": "Grype verifies the database checksum on download; findings are corroborated against Dependabot and CISA KEV", + "fedramp_status": "external; no separate FedRAMP authorization", + }, + # MAS-CSO-IIR: origins the Silk Reeling app loads code or data from in the + # user's browser, next to the camera feed (the app's CSP in + # infrastructure/bootstrap/cloudfront.tf allows exactly these). + { + "id": "ext::jsdelivr", + "native_id": "https://cdn.jsdelivr.net/npm/@mediapipe/tasks-vision/", + "name": "jsDelivr CDN (MediaPipe Tasks Vision runtime)", + "purpose": "Serves the MediaPipe pose-estimation JavaScript and WebAssembly the app runs in the browser", + "cia_impact": "code executed next to the camera feed in the user's browser", + "verification": "Version pinned in the app bundle and in the CSP script-src path; the CSP allows no other jsDelivr path", + "fedramp_status": "external; no separate FedRAMP authorization", + }, + { + "id": "ext::google-cloud-storage", + "native_id": "https://storage.googleapis.com/mediapipe-models/", + "name": "Google Cloud Storage (MediaPipe model bucket)", + "purpose": "Serves the pose-landmarker model file the MediaPipe runtime loads in the browser", + "cia_impact": "model integrity for the pose scores the app computes", + "verification": "CSP connect-src limited to the mediapipe-models path; the model runs in the browser and returns landmarks only", + "fedramp_status": "external; no separate FedRAMP authorization", + }, ] tpr = load_third_party_records(third_party_path, {s["id"] for s in services}) components = [] @@ -1508,11 +1684,39 @@ def build_validations(validations_doc, components): if c["type"] == "html_artifact" } by_cloud_name = {} + names_seen = set() for c in components: - if c["type"] in {"object_store", "cdn_distribution", "function"}: + if c["type"] in PLAN_VALIDATED_TYPES: tf_name = c.get("attributes", {}).get("tf_name") if tf_name: - by_cloud_name[(c["type"], tf_name)] = c["component_id"] + key = (c["type"], tf_name) + if key in names_seen: + # Two components share a type and Terraform name (e.g. one + # from each stack): a plan result cannot be attributed to + # either, so neither is credited. + by_cloud_name.pop(key, None) + continue + names_seen.add(key) + by_cloud_name[key] = c["component_id"] + by_type = {} + for c in components: + by_type.setdefault(c["type"], []).append(c["component_id"]) + # The plan address (e.g. aws_cloudwatch_metric_alarm.evidence["vdr-age"]) + # names one instance exactly, where the Terraform name alone is shared by + # every count/for_each instance. Ambiguous addresses are not credited. + by_address = {} + addresses_seen = set() + for c in components: + if c["type"] not in PLAN_VALIDATED_TYPES: + continue + addr = c.get("attributes", {}).get("tf_address") + if not addr: + continue + if addr in addresses_seen: + by_address.pop(addr, None) + continue + addresses_seen.add(addr) + by_address[addr] = c["component_id"] validations = [] skipped = 0 @@ -1528,11 +1732,25 @@ def build_validations(validations_doc, components): tf_name = result.get("resource_name") normalized = TYPE_BY_TF_TYPE.get(tf_type) if normalized: - cid = by_cloud_name.get((normalized, tf_name)) + address = result.get("address") + if address and address in by_address: + cid = by_address[address] + else: + cid = by_cloud_name.get((normalized, tf_name)) + if cid: + refs = [cid] + elif tf_type in PLAN_VALIDATED_CHILD_TYPES: + # A sub-resource the policy evaluates (an API stage or route) + # is evidence about the component it folds into: the parent of + # the same Terraform name, else the only parent of that type. + parent = PLAN_VALIDATED_CHILD_TYPES[tf_type] + cid = by_cloud_name.get((parent, tf_name)) + if not cid and len(by_type.get(parent, [])) == 1: + cid = by_type[parent][0] if cid: refs = [cid] - # Resources outside the schema's component vocabulary (IAM, log - # groups, attribute-only resources) are intentionally skipped. + # Results no component can be credited with (types no rule + # evaluates, attribute-only resources, ambiguous names) are skipped. if not refs: skipped += 1 continue @@ -1581,6 +1799,27 @@ def build_validations(validations_doc, components): return validations +# Component types whose plan results become validations. Only types at least +# one policy rule evaluates are listed, so a "pass" always means a rule looked +# (tests/test_validation_mapping.py checks each against infrastructure/policy). +# The remaining cloud types (DNS zone, certificate, groups, OIDC provider, the +# lock table) are bootstrap resources or data sources with no plan-time rule; +# the runtime emitter validates them live. +PLAN_VALIDATED_TYPES = { + "object_store", "cdn_distribution", "function", "iam_role", "iam_policy", + "log_group", "api_gateway", "secrets_manager", "kms_key", "identity_provider", + "notification_topic", "metric_alarm", "message_queue", "event_schedule", + "audit_log_trail", +} + +# Sub-resources the policy evaluates, credited to the component they fold into +# (ATTRIBUTE_PARENTS). +PLAN_VALIDATED_CHILD_TYPES = { + "aws_apigatewayv2_stage": "api_gateway", + "aws_apigatewayv2_route": "api_gateway", +} + + # KSI family (the middle token of KSI-XXX-YYY) → the inventory component types # whose policy validations evidence that family's indicators. A consistent, # catalog-derived rule for all in-scope KSIs (assessment Task 4): a KSI's status @@ -1595,7 +1834,8 @@ def build_validations(validations_doc, components): "dns_zone", "tls_certificate", "secrets_manager", "identity_provider", "kms_key"}, "IAM": {"iam_role", "iam_policy", "iam_group", "oidc_provider", "identity_provider", "secrets_manager"}, "INR": {"log_group", "function", "notification_topic", "metric_alarm"}, - "MLA": {"log_group", "function", "cdn_distribution", "notification_topic", "metric_alarm", "message_queue"}, + "MLA": {"log_group", "function", "cdn_distribution", "notification_topic", "metric_alarm", "message_queue", + "audit_log_trail"}, "PIY": None, # policy & inventory — whole inventory is the evidence "RPL": {"object_store"}, "SCR": {"npm_package", "pypi_package", "external_service"}, @@ -1671,7 +1911,8 @@ def build_provenance(): # certificate SAN. GITHUB_WORKFLOW (the display name, with spaces) is NOT a # valid SAN, so builder.id must be built from WORKFLOW_REF. workflow_ref = os.environ.get("GITHUB_WORKFLOW_REF") - run_id = os.environ.get("GITHUB_RUN_ID") + # No run ID: published output never names a GitHub run. The commit + # (source.commit) and the workflow (builder.id) identify the build. sha = os.environ.get("GITHUB_SHA") ref = os.environ.get("GITHUB_REF") @@ -1680,7 +1921,6 @@ def build_provenance(): provenance = { "builder": { "id": builder_id, - "run_id": run_id or "unknown", "version": "github-actions", }, "source": { @@ -1719,7 +1959,6 @@ def build_provenance(): return { "builder": { "id": "local", - "run_id": "local", "version": "local", }, "source": { @@ -1771,7 +2010,10 @@ def main(): # reconciliation gate's live completeness check enforces nothing else is # missed. components.extend(build_live_log_groups(components)) - components.extend(build_npm_components(lambda_lock)) + # The compliance Lambda's zip is `npm ci --omit=dev` of this lockfile, and + # the Silk Reeling zip is the Python tree Syft read (sbom-python.json); the + # SPA's npm tree is a build input bundled into JS, so it is not linked. + components.extend(build_npm_components(lambda_lock, deployed_in="aws::function::opa_compliance")) # The accessibility scanner is build tooling: it never deploys and holds no # data. It is inventoried anyway because it is not inert. Its own manifest # calls it a "fact-producer for the OPA gate" — pa11y emits the facts that @@ -1789,7 +2031,8 @@ def main(): # CycloneDX SBOMs so the canonical inventory covers its Python (PyPI) and # SPA (npm) packages, not just the compliance Lambda's npm packages. Each # call dedupes by PURL against components already collected. - components.extend(build_sbom_components(sbom_python, components)) + components.extend(build_sbom_components(sbom_python, components, + deployed_in="aws::function::silk_reeling")) components.extend(build_sbom_components(sbom_js, components)) components.extend(build_html_components(website_root)) components.extend(build_external_components()) @@ -1848,7 +2091,7 @@ def main(): "ownership": { "system_owner": "Sam Aydlette", "application_owner": "Sam Aydlette", - "operator_contact": "sam.aydlette@gmail.com", + "operator_contact": "https://www.linkedin.com/in/sa2/", }, "disclosure": { "authorization_status": "self-attested-proof-of-concept", @@ -1877,6 +2120,9 @@ def main(): # configuration value is published with ACCOUNT in its place, and the # publication gate fails the deploy on any twelve-digit number that remains. signal = _redact.redact(signal) + # CDS-CSO-FID: the offering's FedRAMP ID; the runtime emitter copies it + # from this signal into the runtime signal. + signal = _offering.stamp_fedramp_id(signal) output_path.write_text(json.dumps(signal, indent=2) + "\n") print( f"Wrote {output_path} " diff --git a/scripts/build-mas.py b/scripts/build-mas.py new file mode 100644 index 00000000..f105a841 --- /dev/null +++ b/scripts/build-mas.py @@ -0,0 +1,428 @@ +#!/usr/bin/env python3 +"""The Minimum Assessment Scope, generated: /.well-known/minimum-assessment-scope.json. + +One machine-readable view of the cloud service offering's scope, joined from +what the pipeline already holds, so it cannot drift from it: + + MAS-CSO-IIR the information resources: the canonical inventory (ksi-signal.json), + plus every off-origin host the site's and app's Content Security + Policies allow (infrastructure/bootstrap/cloudfront.tf), each placed + on an inventoried component or put out of scope with a reason. + MAS-CSO-FLO the information flows (docs/boundary/boundary-classification.json) + resolved against the inventory, each with a security category + derived from its endpoints (the high-water mark of their FIPS 199 + categories); every external service and every data store is in at + least one flow. + MAS-CSO-MDI the metadata inventory: every data store and log in the inventory, + what it holds, which personal data, retention and location + (data/minimum-assessment-scope.json supplies the meaning). + MAS-CSO-TPR each third-party information resource with the four fields FedRAMP + requires (data/third-party-components.json, decided records only). + FRC-CSX-MAS how every KSI applies to the scope: per component through the KSI's + evidence domain, or over the whole set. + +Fails closed: any gap above stops the build, and so the deploy, before the SDR +is built. No ARN, account ID or address is published: components are named by +their inventory IDs. +""" + +import argparse +import fnmatch +import json +import re +import sys +from datetime import datetime, timezone +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _offering # noqa: E402 + +REPO = Path(__file__).resolve().parent.parent +INPUTS = REPO / "data" / "minimum-assessment-scope.json" +THIRD_PARTY = REPO / "data" / "third-party-components.json" +CLASSIFICATION = REPO / "docs" / "boundary" / "boundary-classification.json" +CLOUDFRONT_TF = REPO / "infrastructure" / "bootstrap" / "cloudfront.tf" +BOOTSTRAP_DIR = REPO / "infrastructure" / "bootstrap" +SCHEMA = "minimum-assessment-scope/1" +LEVELS = ("low", "moderate", "high") +OBJECTIVES = ("confidentiality", "integrity", "availability") +TPR_FIELDS = ("usage_and_configuration", "justification", "mitigations", "compensating_controls") +PACKAGE_TYPES = ("npm_package", "pypi_package") +CODE = { + "builder": "scripts/build-mas.py", + "inventory": "scripts/build-ksi-signal.py", + "inputs": "data/minimum-assessment-scope.json", + "flows": "docs/boundary/boundary-classification.json", + "third_party": "data/third-party-components.json", + "csp": "infrastructure/bootstrap/cloudfront.tf", +} +DERIVATION = ( + "Generated on every deploy by scripts/build-mas.py from this build's canonical inventory " + "(ksi-signal.json, itself derived from Terraform state, the SBOMs, the site's HTML and the declared " + "external services), the boundary classification's data-flow table, the operator's metadata and " + "off-origin placements (data/minimum-assessment-scope.json) and the third-party records " + "(data/third-party-components.json). Information resources are the inventory's components; the " + "Content Security Policies the edge serves are parsed for every off-origin host, and each must be an " + "inventoried component or out of scope with a stated reason. Each flow is resolved against the inventory " + "and given the high-water mark of its endpoints' security categories. Every data store and log in the " + "inventory must have a metadata entry, every external service and data store must be in a flow, every " + "third-party resource must carry a decided record with the four MAS-CSO-TPR fields, and every component " + "type must fall in at least one KSI's evidence domain or carry a whole-set reason. Any gap fails the " + "build, so the deploy never publishes a scope with one." +) + + +def _fail(msg): + raise SystemExit(f"::error::MAS: {msg} (fail-closed)") + + +# --- MAS-CSO-IIR: off-origin hosts from the CSPs --------------------------------------- + +_URL = re.compile(r"https://([A-Za-z0-9.${}_-]+)") +_LOCAL = re.compile(r"\$\{local\.([A-Za-z0-9_]+)\}") +_VAR = re.compile(r"\$\{var\.([A-Za-z0-9_]+)\}") + + +def _locals(text): + """{name: definition text} for every `name = ...` in a locals block (to the + next blank line, enough for this repository's style).""" + out = {} + for block in re.finditer(r"locals\s*\{(.*?)\n\}", text, re.S): + body = block.group(1) + for m in re.finditer(r"^\s*([A-Za-z0-9_]+)\s*=\s*(.*?)(?=^\s*[A-Za-z0-9_]+\s*=|\Z)", body, re.S | re.M): + v = m.group(2).strip() + q = re.match(r'^"([^"\n]*)"', v) # a plain string local: its content, without the quotes + out[m.group(1)] = q.group(1) if q else v + return out + + +def _var_defaults(text): + return {m.group(1): m.group(2) for m in re.finditer( + r'variable\s+"([A-Za-z0-9_]+)"\s*\{[^}]*?default\s*=\s*"([^"]*)"', text, re.S)} + + +def _expand(s, locals_, vars_, depth=0): + if depth > 5: + _fail("CSP expansion does not terminate") + s = _VAR.sub(lambda m: vars_.get(m.group(1), m.group(0)), s) + if "domain_name" in vars_: + s = s.replace("${local.domain_dashed}", vars_["domain_name"].replace(".", "-")) + return _LOCAL.sub(lambda m: _expand(locals_.get(m.group(1), m.group(0)), locals_, vars_, depth + 1), s) + + +def csp_hosts(tf_text, context_text=""): + """Every host an https:// source in a content_security_policy names, with + ${local.*} and ${var.*} references expanded from the same configuration.""" + whole = tf_text + "\n" + context_text + locals_, vars_ = _locals(whole), _var_defaults(whole) + hosts = set() + for m in re.finditer(r"content_security_policy\s*=\s*join\(\s*\"; \",\s*\[(.*?)\]\s*\)", tf_text, re.S): + expanded = _expand(m.group(1), locals_, vars_) + # Every https:// source must yield a host: one that does not would be a + # host this check silently missed. + if expanded.count("https://") != len(_URL.findall(expanded)): + _fail("a CSP https:// source does not resolve to a host") + for h in _URL.findall(expanded): + if "$" in h or "{" in h or "}" in h: + _fail(f"cannot resolve the CSP source host {h!r}") + hosts.add(h.lower()) + return sorted(hosts) + + +def place_hosts(hosts, placements, component_ids): + """[(host, placement)] for every host; fails on a host placed nowhere, on a + placement naming a component the inventory lacks, or with no reason.""" + out, problems = [], [] + for h in hosts: + p = placements.get(h) + if not isinstance(p, dict): + problems.append(f"the CSP allows {h}, which is neither an inventoried information resource nor " + "out of scope with a reason (data/minimum-assessment-scope.json off_origin_hosts)") + continue + if p.get("component"): + if p["component"] not in component_ids: + problems.append(f"{h} is placed on {p['component']}, which is not in the inventory") + out.append({"host": h, "component": p["component"]}) + elif isinstance(p.get("out_of_scope"), str) and p["out_of_scope"].strip(): + out.append({"host": h, "out_of_scope": p["out_of_scope"]}) + else: + problems.append(f"{h} has neither a component nor an out_of_scope reason") + return out, problems + + +# --- MAS-CSO-FLO ------------------------------------------------------------------------- + +def _match(pattern, ids): + return sorted(i for i in ids if fnmatch.fnmatchcase(i, pattern)) + + +def _high_water(categories): + out = {} + for o in OBJECTIVES: + vals = [c.get(o) for c in categories if c.get(o) in LEVELS] + if vals: + out[o] = max(vals, key=LEVELS.index) + return out + + +def flows(classification, components, data_store_types): + by_id = {c["component_id"]: c for c in components} + ids = sorted(by_id) + declared = {d["key"] for d in classification.get("declared", [])} + out, problems, covered = [], [], set() + for f in classification.get("flows", []): + endpoints = [] + for ref in f["path"]: + if "declared" in ref: + if ref["declared"] not in declared: + problems.append(f"flow {f['id']} names an undeclared actor {ref['declared']}") + endpoints.append({"declared": ref["declared"]}) + continue + hit = _match(ref["component"], ids) + if not hit: + problems.append(f"flow {f['id']} endpoint {ref['component']} matches no inventoried component") + covered.update(hit) + endpoints.append({"components": hit}) + cats = [by_id[i].get("security_category") or {} for e in endpoints for i in e.get("components", [])] + category = _high_water(cats) + if len(category) != len(OBJECTIVES): + problems.append(f"flow {f['id']} has no endpoint with a security category") + out.append({"id": f["id"], "label": f["label"], "endpoints": endpoints, "security_category": category, + **{k: f[k] for k in ("protocol", "auth", "encryption", "data", "note") if f.get(k)}}) + must = sorted(i for i, c in by_id.items() if c.get("type") == "external_service" or c.get("type") in data_store_types) + for i in must: + if i not in covered: + problems.append(f"{i} ({by_id[i].get('type')}) is in no information flow") + return out, problems + + +# --- MAS-CSO-MDI ------------------------------------------------------------------------- + +def metadata_inventory(components, metadata, data_store_types): + out, problems = [], [] + keys = list(metadata) + for c in sorted(components, key=lambda c: c["component_id"]): + cid, ctype = c["component_id"], c.get("type") + third_party_observed = cid in metadata and ctype == "external_service" + if ctype not in data_store_types and not third_party_observed: + continue + key = cid if cid in metadata else next((k for k in keys if fnmatch.fnmatchcase(cid, k)), None) + if key is None: + problems.append(f"{cid} ({ctype}) holds data or logs but has no metadata entry " + "(data/minimum-assessment-scope.json metadata)") + continue + m = metadata[key] + if not (isinstance(m.get("holds"), str) and isinstance(m.get("personal_data"), list) + and isinstance(m.get("retention"), str)): + problems.append(f"metadata entry {key} needs holds, personal_data and retention") + continue + attrs = c.get("attributes") or {} + entry = {"component": cid, "type": ctype, "holds": m["holds"], "personal_data": m["personal_data"], + "retention": m["retention"], + "location": attrs.get("region") or ("third party" if ctype == "external_service" else "not recorded"), + "controlled_by": "third party" if ctype == "external_service" else "provider"} + if "retention_days" in m: + entry["retention_days"] = m["retention_days"] + out.append(entry) + return out, problems + + +# --- MAS-CSO-TPR ------------------------------------------------------------------------- + +def third_party(components, tpr_doc): + recs = (tpr_doc or {}).get("components") or {} + out, problems = [], [] + for c in sorted(components, key=lambda c: c["component_id"]): + if c.get("type") != "external_service": + continue + cid, rec = c["component_id"], recs.get(c["component_id"]) + if not rec: + problems.append(f"{cid} has no third-party record (data/third-party-components.json)") + continue + if not (rec.get("decided_by") and rec.get("decided_on")): + problems.append(f"{cid}'s third-party record has no decision (decided_by, decided_on)") + continue + missing = [f for f in TPR_FIELDS if not (isinstance(rec.get(f), str) and rec[f].strip())] + if missing: + problems.append(f"{cid}'s third-party record lacks {', '.join(missing)}") + continue + attrs = c.get("attributes") or {} + out.append({"component": cid, "name": attrs.get("name") or cid, "provider": rec.get("provider"), + "website": rec.get("website"), "upstream_offering": rec.get("upstream_offering"), + **{f: rec[f] for f in TPR_FIELDS}, + "decided_by": rec["decided_by"], "decided_on": rec["decided_on"]}) + return out, problems + + +# --- FRC-CSX-MAS ------------------------------------------------------------------------- + +def ksi_application(signal, whole_set_types): + """Per KSI: the components its evidence domain covers, or the whole set. + A KSI whose evidence is every component (or none, a documentation KSI) + applies over the whole set; the rest apply per component.""" + comps = [c for c in signal.get("components", [])] + all_ids = {c["component_id"] for c in comps} + type_of = {c["component_id"]: c.get("type") for c in comps} + out, domain_types = [], set() + for k in signal.get("ksis", []): + refs = set((k.get("evidence") or {}).get("component_refs") or []) + whole = not refs or refs >= all_ids + if not whole: + domain_types.update(type_of[r] for r in refs if r in type_of) + out.append({"ksi": k["id"], "method": k.get("method"), "status": k.get("status"), + "applies_to": "whole set" if whole else "per component", + "components": len(all_ids) if whole else len(refs & all_ids), + "component_types": sorted({type_of[r] for r in (all_ids if whole else refs & all_ids)})}) + problems = [] + if not out: + problems.append("the inventory carries no KSIs") + for t in sorted({type_of[i] for i in all_ids}): + if t not in domain_types and not (isinstance(whole_set_types.get(t), str) and whole_set_types[t].strip()): + problems.append(f"component type {t} is in no KSI's per-component evidence domain and has no whole-set " + "reason (data/minimum-assessment-scope.json whole_set_types)") + per_type = {t: ("per component" if t in domain_types else f"whole set only: {whole_set_types[t]}") + for t in sorted({type_of[i] for i in all_ids}) if t in domain_types or t in whole_set_types} + return out, per_type, problems + + +# --- build ------------------------------------------------------------------------------- + +def build(signal, inputs, classification, tpr_doc, cloudfront_tf, bootstrap_context, commit, now): + comps = signal.get("components", []) + ids = {c["component_id"] for c in comps} + dst = set(inputs.get("data_store_types") or []) + hosts, p1 = place_hosts(csp_hosts(cloudfront_tf, bootstrap_context), inputs.get("off_origin_hosts") or {}, ids) + fl, p2 = flows(classification, comps, dst) + md, p3 = metadata_inventory(comps, inputs.get("metadata") or {}, dst) + tp, p4 = third_party(comps, tpr_doc) + ka, per_type, p5 = ksi_application(signal, inputs.get("whole_set_types") or {}) + problems = p1 + p2 + p3 + p4 + p5 + by_type = {} + for c in comps: + by_type[c.get("type")] = by_type.get(c.get("type"), 0) + 1 + resources = [{"component": c["component_id"], "type": c.get("type"), + "security_category": c.get("security_category"), + "function": (c.get("attributes") or {}).get("function")} + for c in sorted(comps, key=lambda c: c["component_id"]) if c.get("type") not in PACKAGE_TYPES] + doc = { + "schema": SCHEMA, + "generated_at": now, + "commit": commit, + "ksi_signal_id": signal.get("signal_id"), + "derivation": DERIVATION, + "code": CODE, + "information_resources": { + "total": len(comps), + "by_type": dict(sorted(by_type.items())), + "software_packages": sum(by_type.get(t, 0) for t in PACKAGE_TYPES), + "resources": resources, + "off_origin_hosts": hosts, + }, + "flows": fl, + "metadata_inventory": md, + "third_party_information_resources": tp, + "ksi_application": {"ksis": ka, "component_types": per_type}, + "checks": { + "off_origin_hosts_placed": not p1, + "every_external_service_and_data_store_in_a_flow": not p2, + "every_data_store_and_log_has_metadata": not p3, + "every_third_party_resource_decided_with_all_fields": not p4, + "every_component_type_in_a_ksi_domain": not p5, + }, + } + return doc, problems + + +def render_markdown(d): + ir = d["information_resources"] + out = ["# Minimum Assessment Scope", "", + f"_Generated {d['generated_at']} from inventory `{d['ksi_signal_id']}` at commit `{(d['commit'] or '')[:12]}`._", + "", "## How this is derived", "", d["derivation"], "", + "Code: " + ", ".join(f"`{v}`" for v in d["code"].values()), "", + "## Information resources (MAS-CSO-IIR)", "", + f"{ir['total']} inventoried components, {ir['software_packages']} of them software packages.", "", + "| Type | Count |", "|---|---|", *[f"| {t} | {n} |" for t, n in ir["by_type"].items()], "", + "| Component | Type | C/I/A | Function |", "|---|---|---|---|"] + for r in ir["resources"]: + sc = r.get("security_category") or {} + out.append(f"| `{r['component']}` | {r['type']} | {'/'.join(sc.get(o, '?') for o in OBJECTIVES)} | " + f"{(r.get('function') or '').replace('|', '/')} |") + out += ["", "Off-origin hosts the Content Security Policies allow:", "", + "| Host | Placement |", "|---|---|"] + for h in ir["off_origin_hosts"]: + out.append(f"| {h['host']} | " + (f"`{h['component']}`" if h.get("component") else f"Out of scope: {h['out_of_scope']}") + " |") + out += ["", "## Information flows and security categories (MAS-CSO-FLO)", "", + "| Flow | Endpoints | C/I/A | Protocol | Auth | Encryption | Data |", "|---|---|---|---|---|---|---|"] + for f in d["flows"]: + ends = " → ".join(e.get("declared") or ", ".join(e["components"]) or "(none)" for e in f["endpoints"]) + sc = f["security_category"] + out.append(f"| {f['id']}: {f['label']} | {ends} | {'/'.join(sc.get(o, '?') for o in OBJECTIVES)} | " + f"{f.get('protocol', '')} | {f.get('auth', '')} | {f.get('encryption', '')} | {f.get('data', '')} |") + out += ["", "## Metadata inventory (MAS-CSO-MDI)", "", + "| Component | Holds | Personal data | Retention | Location |", "|---|---|---|---|---|"] + for m in d["metadata_inventory"]: + out.append(f"| `{m['component']}` | {m['holds']} | {', '.join(m['personal_data']) or 'none'} | " + f"{m['retention']} | {m['location']} ({m['controlled_by']}) |") + out += ["", "## Third-party information resources (MAS-CSO-TPR)", ""] + for t in d["third_party_information_resources"]: + out += [f"### {t['name']} (`{t['component']}`)", "", + f"- **Provider:** {t['provider']} ({t['website']})", + f"- **General usage and configuration:** {t['usage_and_configuration']}", + f"- **Justification for use:** {t['justification']}", + f"- **Mitigation measures:** {t['mitigations']}", + f"- **Compensating controls:** {t['compensating_controls']}", + f"- **Decided by:** {t['decided_by']}, {t['decided_on']}", ""] + out += ["## Key Security Indicators applied to the scope (FRC-CSX-MAS)", "", + "| KSI | Method | Applies | Components | Types |", "|---|---|---|---|---|"] + for k in d["ksi_application"]["ksis"]: + out.append(f"| {k['ksi']} | {k['method']} | {k['applies_to']} | {k['components']} | {', '.join(k['component_types'])} |") + out += ["", "| Component type | Coverage |", "|---|---|", + *[f"| {t} | {v} |" for t, v in d["ksi_application"]["component_types"].items()], + "", "## Checks", "", *[f"- {k}: {'pass' if v else 'FAIL'}" for k, v in d["checks"].items()], + "", "---", "_Source of truth: the signed `minimum-assessment-scope.json`._"] + return "\n".join(out) + + +def _read_json(path, what): + try: + return json.loads(Path(path).read_text()) + except (OSError, json.JSONDecodeError) as exc: + _fail(f"cannot read {what} {path} ({type(exc).__name__})") + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + ap.add_argument("--ksi-signal", default="ksi-signal.json") + ap.add_argument("--inputs", default=str(INPUTS)) + ap.add_argument("--classification", default=str(CLASSIFICATION)) + ap.add_argument("--third-party", default=str(THIRD_PARTY)) + ap.add_argument("--cloudfront-tf", default=str(CLOUDFRONT_TF)) + ap.add_argument("--commit", default="") + ap.add_argument("--output", default="minimum-assessment-scope.json") + ap.add_argument("--md-output", default="minimum-assessment-scope.md") + a = ap.parse_args(argv) + signal = _read_json(a.ksi_signal, "the KSI signal") + inputs = _read_json(a.inputs, "the MAS inputs") + if inputs.get("schema") != "mas-inputs/1": + _fail(f"{a.inputs} is not a mas-inputs/1 document") + tf = Path(a.cloudfront_tf).read_text() + context = "\n".join(p.read_text() for p in sorted(Path(a.cloudfront_tf).parent.glob("*.tf"))) + doc, problems = build(signal, inputs, _read_json(a.classification, "the classification"), + _read_json(a.third_party, "the third-party records"), tf, context, a.commit, + datetime.now(timezone.utc).isoformat()) + if problems: + for p in problems: + print(f"::error::MAS: {p}") + _fail(f"{len(problems)} gap(s) in the Minimum Assessment Scope") + doc = _offering.stamp_fedramp_id(doc) # CDS-CSO-FID + Path(a.output).write_text(json.dumps(doc, indent=2) + "\n") + if a.md_output: + Path(a.md_output).write_text(render_markdown(doc) + "\n") + print(f"minimum-assessment-scope: {doc['information_resources']['total']} components, {len(doc['flows'])} flows, " + f"{len(doc['metadata_inventory'])} metadata entries, {len(doc['third_party_information_resources'])} " + f"third-party records, {len(doc['ksi_application']['ksis'])} KSIs applied") + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/build-ocr.py b/scripts/build-ocr.py index cad56d46..742ca8be 100644 --- a/scripts/build-ocr.py +++ b/scripts/build-ocr.py @@ -1,43 +1,78 @@ #!/usr/bin/env python3 # ============================================================================= -# ONGOING CERTIFICATION REPORT BUILDER (CR26 CCM) +# ONGOING CERTIFICATION REPORT BUILDER (CR26 CCM, FedRAMP's 2026-06-24 schema) # ============================================================================= -# CR26 Collaborative Continuous Monitoring is a quarterly cycle, not a stream. -# CCM-OCR-AVL requires a human-readable Ongoing Certification Report (OCR) every -# 3 months covering the period since the previous summary, carrying eight -# high-level summaries; CCM-OCR-NRD requires publishing the target date of the -# next OCR, and CCM-QTR-NRD the target date of the next Quarterly Review. This -# generator derives the OCR from the system's own published artifacts (the SCN -# register, the decision register, the VDR report) and emits it as both JSON (Certification -# Data, bound to the canonical inventory's signal_id) and human-readable -# markdown. It is the same report for the Rev5 and 20x certification types. +# CCM-OCR-AVL: a human-readable report every 3 months covering the period since +# the previous one, with the eight summaries, in FedRAMP's OCR schema. Dates +# come from the fixed calendar (infrastructure/schemas/ccm-calendar.json via +# scripts/_ccm.py), never from "now plus 91 days": # -# What it cannot manufacture is the *relationship*: the synchronous Quarterly -# Review (CCM-QTR-MTG) and the agency feedback loop (CCM-OCR-FBM/AFS) need a -# consuming party. With no agency sponsor those are recorded as N/A, and the OCR -# says so rather than implying a closed loop that does not exist. +# rolling (default) the report as it stands today, from the latest issue to +# today; rebuilt on every deploy and maintenance run +# --issue YYYY-MM-DD the frozen report for one calendar issue date, covering +# the previous issue to that one (scripts/issue-ocr.py) +# +# Sources: the SCN register (changes), the decision register (planned changes), +# the VDR report (accepted vulnerabilities), the incident register when present +# (reportable incidents and lessons learned), and the Quarterly Review of the +# previous report (scripts/_quarterly_review.py: the anonymized summary of the +# questions and answers received through the feedback intake, CCM-OCR-AFS; the +# parties are simulated, DEC-194). +# +# Before it is written, every string is screened (scripts/_sensitivity.py, +# CCM-OCR-LSI) and the whole document validated against the vendored schema; +# either failing writes nothing. The public-release determination (CCM-OCR-RPS) +# is a decision record the report cites. # # build-ocr.py --vdr vdr-report.json --decisions ../data/decisions.json \ -# --scn-register ../docs/scn/scn-register.csv --ksi-signal ksi-signal.json +# --scn-register ../docs/scn/scn-register.csv --ksi-signal ksi-signal.json # ============================================================================= import argparse import csv import json import sys -from datetime import datetime, timedelta, timezone +from datetime import date, datetime, timedelta, timezone from pathlib import Path sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _ccm # noqa: E402 import _decisions # noqa: E402 +import _fedramp_schema as fs # noqa: E402 +import _incidents # noqa: E402 +import _engagement # noqa: E402 +import _offering # noqa: E402 +import _quarterly_review # noqa: E402 +import _sensitivity # noqa: E402 -QUARTER_DAYS = 91 +REPO = Path(__file__).resolve().parent.parent +INCIDENTS_PATH = REPO / "data" / "incidents.json" +SITE = "https://samaydlette.com" +PLANNING_DAYS = 92 # at least 3 months past the report's end +SUMMARY_MAX = 300 +# The decision records the report cites (data/decisions.json). +PUBLIC_RELEASE_DECISION = "DEC-101" # CCM-OCR-RPS / CCM-QTR-SCR: published in full +ENGAGEMENT_DECISION = _engagement.DECISION # every review attendee and feedback party is simulated +STANDING_AGENDA = [ + "Walk through the report's eight summaries and anything changed since it was issued.", + "Standing item (CCM-QTR-ACT): Key Security Indicator results and their trend over the quarter, from the " + "Security Decision Record's 30-day and one-year metric summaries.", + "Standing item (CCM-QTR-ACT): open and accepted vulnerabilities and their trend, from the vulnerability " + "history (VER-TFR-MRH).", + "Standing item (CCM-QTR-ACT): the plan for the next quarter, including planned changes to certification data.", + "Questions received through the feedback intake, and questions from the (simulated) attendees.", +] -def _load_json(path): - p = Path(path) - if not p.exists(): - print(f"::warning::OCR input not found: {path}", file=sys.stderr) +def _fail(msg): + raise SystemExit(f"::error::OCR: {msg} (fail-closed)") + + +def _load_json(path, required=False): + p = Path(path) if path else None + if not p or not p.exists(): + if required: + _fail(f"{path} not found") return None return json.loads(p.read_text()) @@ -50,140 +85,279 @@ def _scn_rows(path): return list(csv.DictReader(f)) -def build_ocr(vdr, decisions, scn_rows, signal_id, now): - period_start = (now - timedelta(days=QUARTER_DAYS)).date().isoformat() - period_end = now.date().isoformat() - - # 1. Changes to Certification Data — the SCN register is the change record. - cert_changes = [{"scn_id": r.get("scn_id"), "type": r.get("scn_type"), - "summary": (r.get("short_description") or "")[:240], - "status": r.get("status", "")[:80]} for r in scn_rows] - # 4. Transformative changes (a subset of the above). - transformative = [c for c in cert_changes if (c.get("type") or "").lower() == "transformative"] - - # 2. Planned changes over the next 3 months — in-force decision records that - # carry a remediation plan or a planned completion date. A false positive or - # an accepted risk plans no change, so it is not listed here. - planned = [{"decision_id": r["id"], "title": r.get("title", "")[:160], - "planned_completion": r.get("planned_completion")} - for r in (decisions or {}).get("decisions", []) - if r.get("status") == "in-force" and (r.get("remediation_plan") or r.get("planned_completion"))] - - # 3. Accepted vulnerabilities. - accepted = [] - if vdr: - for a in vdr.get("risk_accepted", []) or []: - accepted.append({"tracking_id": a.get("tracking_id"), "pain": a.get("pain"), - "decision_id": a.get("decision_id"), - "explanation": (a.get("explanation") or "")[:200]}) - - report = { - "report_type": "ongoing-certification-report", - "schema": "fedramp-ongoing-certification-report-schema-2026-06-24.json", - "fedramp_id": "<not assigned — unsponsored self-attested PoC>", - "class": "C", - "emitted_at": now.isoformat(), - "reporting_period": {"start": period_start, "end": period_end}, - "ksi_signal_id": signal_id, - "next_ongoing_certification_report_date": (now + timedelta(days=QUARTER_DAYS)).date().isoformat(), - "next_quarterly_review_date": (now + timedelta(days=QUARTER_DAYS)).date().isoformat(), - # The eight CCM-OCR-AVL summaries: - "summaries": { - "changes_to_certification_data": cert_changes, # 1 - "planned_changes_next_quarter": planned, # 2 - "accepted_vulnerabilities": accepted, # 3 - "transformative_changes": transformative, # 4 - "updated_recommendations": [ # 5 - "No new customer recommendations this period; the Secure Configuration " - "Guidance at /.well-known/ remains current."], - "agencies_using_product": [], # 6 (none) - "reportable_incidents_or_attestation": # 7 - "No FedRAMP Reportable Incidents occurred during this reporting period. " - "The system holds no federal customer data, so the IEC-CSO-EFR trigger " - "does not apply; this is an attestation of none, not an omission.", - "lessons_learned_from_incidents": [], # 8 (none) - }, - "relationship_obligations_status": ( - "N/A absent a consuming agency. The synchronous Quarterly Review (CCM-QTR-MTG), " - "the feedback channel (CCM-OCR-FBM), and the anonymized feedback summary " - "(CCM-OCR-AFS) require a counterparty; with no agency sponsor there is none to " - "exercise them. The next-review date above is published per CCM-QTR-NRD regardless."), - } - return report +def _day(v): + try: + return date.fromisoformat(str(v)[:10]) + except ValueError: + return None -def render_markdown(r): - s = r["summaries"] - out = ["# Ongoing Certification Report", ""] - out.append(f"- **Class:** {r['class']} | **Reporting period:** {r['reporting_period']['start']} to {r['reporting_period']['end']}") - out.append(f"- **Emitted:** {r['emitted_at']}") - out.append(f"- **Bound to inventory signal:** `{r['ksi_signal_id']}`") - out.append(f"- **Next Ongoing Certification Report (CCM-OCR-NRD):** {r['next_ongoing_certification_report_date']}") - out.append(f"- **Next Quarterly Review (CCM-QTR-NRD):** {r['next_quarterly_review_date']}") - out.append("") - out.append("> " + r["relationship_obligations_status"]) - out.append("") - - def section(n, title, body): - out.append(f"## {n}. {title}\n") - out.extend(body) - out.append("") - - cc = s["changes_to_certification_data"] - section(1, "Changes to Certification Data", - ([f"- `{c['scn_id']}` ({c['type']}): {c['summary']} — _{c['status']}_" for c in cc] - if cc else ["_No changes recorded this period._"])) - pc = s["planned_changes_next_quarter"] - section(2, "Planned changes over the next 3 months", - ([f"- {p['title']}" for p in pc] if pc else ["_None planned._"])) - av = s["accepted_vulnerabilities"] - section(3, "Accepted vulnerabilities", - ([f"- `{a['tracking_id']}` (PAIN {a['pain']}, {a['decision_id'] or 'no decision record'}): {a['explanation']}" for a in av] - if av else ["_None._"])) - tf = s["transformative_changes"] - section(4, "Transformative changes", - ([f"- `{c['scn_id']}`: {c['summary']}" for c in tf] if tf else ["_None this period._"])) - section(5, "Updated recommendations", [f"- {x}" for x in s["updated_recommendations"]]) - ag = s["agencies_using_product"] - section(6, "Agencies using the product", - ([f"- {a}" for a in ag] if ag else ["_None — unsponsored proof of concept._"])) - section(7, "FedRAMP Reportable Incidents", [s["reportable_incidents_or_attestation"]]) - ll = s["lessons_learned_from_incidents"] - section(8, "Lessons learned from incidents", - ([f"- {x}" for x in ll] if ll else ["_None; no incidents to date._"])) - out.append("---") - out.append("_Source of truth: the signed `ongoing-certification-report.json`. Rules: " - "CCM-OCR-AVL (report), CCM-OCR-NRD / CCM-QTR-NRD (next dates)._") - return "\n".join(out) +def incident_summary(incidents, period_start): + """CCM-OCR-AVL item 7, from the incident register: the FedRAMP Reportable + Incidents detected this period, or an attestation of none. Exercises are + not incidents and are never counted.""" + log = "The incident log, /.well-known/incident-reports.json, records every incident evaluated, exercises included." + real = [i for i in (incidents or {}).get("incidents", []) + if not i.get("exercise") and (i.get("evaluation") or {}).get("reportable") + and str(i.get("detected_at") or i.get("started_at") or "")[:10] >= period_start] + if real: + return (f"{len(real)} FedRAMP Reportable Incident(s) this period: " + + "; ".join(f"{i['id']} ({_incidents.status(i)})" for i in real) + f". {log}") + return ("No FedRAMP Reportable Incidents occurred during this reporting period. The system holds " + "no federal customer data, so the IEC-CSO-EFR trigger does not apply; this is an " + f"attestation of none, not an omission. {log}") + + +def _in(d, period): + return d is not None and period[0] < d <= period[1] + + +def _short(text, n=SUMMARY_MAX): + text = " ".join(str(text or "").split()) + return text if len(text) <= n else text[: n - 1].rstrip() + "…" + + +# --- the eight summaries ------------------------------------------------------------- + +def scn_changes(rows, period): + out, transformative = [], [] + for r in rows: + when = _day(r.get("date_finished")) or _day(r.get("date_initiated")) + if not _in(when, period): + continue + line = f"{r.get('scn_id')} ({r.get('scn_type')}, {when}): {_short(r.get('short_description'))}" + out.append(line) + if (r.get("scn_type") or "").lower() == "transformative": + transformative.append(line) + return out, transformative + + +def planned_changes(decisions, period): + horizon = period[1] + timedelta(days=PLANNING_DAYS) + changes = [f"{r['id']}: {_short(r.get('title'), 160)}" + + (f" (planned completion {r['planned_completion']})" if r.get("planned_completion") else "") + for r in _decisions.in_force(decisions or {"decisions": []}) + if r.get("remediation_plan") or r.get("planned_completion")] + return {"planningHorizonThrough": horizon.isoformat(), "changes": changes} -def main(): +def accepted_summary(vdr, period): + acc = (vdr or {}).get("risk_accepted") or [] + if not acc: + return (f"No accepted vulnerabilities as of {period[1]}. Full records: " + f"{SITE}/.well-known/vdr-accepted-vulnerabilities.json (VER-RPT-AVI).") + ids = ", ".join(sorted(str(a.get("decision_id") or a.get("tracking_id")) for a in acc)[:20]) + return (f"{len(acc)} accepted vulnerabilities as of {period[1]}, each with a decision record ({ids}). " + f"Full records: {SITE}/.well-known/vdr-accepted-vulnerabilities.json (VER-RPT-AVI).") + + +def reportable_incidents(register, period): + out = [] + for inc in (register or {}).get("incidents", []): + if not (inc.get("evaluation") or {}).get("reportable"): + continue + if not _in(_day(inc.get("started_at")), period): + continue + title = str(inc.get("title") or "") + if inc.get("exercise"): + title = "Exercise, not a real incident: " + title.removeprefix("Exercise: ") + rec = {"summary": f"{inc['id']}: {_short(title)}", "occurredAt": inc["started_at"]} + if inc.get("resolved_at"): + rec["resolvedAt"] = inc["resolved_at"] + lessons = list(inc.get("lessons_learned") or []) + for rep in inc.get("reports", []): + lessons += list((rep.get("set") or {}).get("lessons_learned") or []) + if lessons: + rec["incidentLessonsLearned"] = [_short(x) for x in lessons] + out.append(rec) + return out + + +# --- feedback (CCM-OCR-FBM / AFS) ---------------------------------------------------- + +def feedback_summary(cal, previous_issue, today): + """The anonymized summary of the feedback on the previous issued report: the + one its Quarterly Review published (the same function builds both).""" + if previous_issue is None: + return {"ocr": None, "statement": "No report has been issued before this one, so there is no feedback " + "to summarize yet."} + review = cal.review_date(previous_issue) + if review > today: + return {"ocr": previous_issue.isoformat(), "received": 0, + "statement": f"The Quarterly Review of the report issued {previous_issue} is on {review}; its " + "feedback summary appears here once it is held."} + qa = _quarterly_review.qa_summary(previous_issue.isoformat(), cal.issues.index(previous_issue)) + return {"ocr": qa["ocr"], "received": qa["received"], "summarizedOn": review.isoformat(), + "simulated": True, "review": _ccm.review_url(previous_issue), + "statement": f"{qa['received']} item(s) received through the feedback intake on the report issued " + f"{qa['ocr']}, all from simulated parties (DEC-194), summarized without names, agencies or " + "identifying detail.", + "items": [{"question": _short(i["question"]), "answer": _short(i["answer"])} for i in qa["items"]]} + + +# --- build --------------------------------------------------------------------------- + +def build(cal, today, vdr, decisions, scn_rows, incidents, signal, prof, off, prev, now, issue=None): + if issue is None: + period = cal.current_period(today) + done = cal.issued(today) + prev_issue = done[-1] if done else None + kind = {"kind": "rolling", "statement": "The report as it stands since the latest issue; rebuilt on every " + "deploy and maintenance run. Issued reports are frozen: see ongoingCertificationReportIssues."} + else: + if issue not in cal.issues: + _fail(f"{issue} is not a calendar issue date") + if issue > today: + _fail(f"{issue} is in the future: a report is issued on or after its date") + period = cal.period(issue) + i = cal.issues.index(issue) + prev_issue = cal.issues[i - 1] if i else None + kind = {"kind": "issued", "issueDate": issue.isoformat(), "issuedAt": now.isoformat(), + "late": today > issue, + "statement": "Frozen at issue: this file is never rewritten. Its sha256 is in ocr-issues.json."} + ref = issue or today + review_issue = issue or (cal.issued(today)[-1] if cal.issued(today) else cal.issues[0]) + changes, transformative = scn_changes(scn_rows, period) + feedback_on = feedback_summary(cal, prev_issue, today) + doc = { + "$schema": fs.stamp("ocr"), + "certificationPackageOverviewUri": fs.CPO_URI, + "reportPeriod": {"from": period[0].isoformat(), "to": period[1].isoformat()}, + "certificationDataChanges": changes, + "plannedCertificationDataChanges": planned_changes(decisions, period), + "acceptedVulnerabilities": accepted_summary(vdr, period), + "transformativeChanges": transformative, + "updatedRecommendations": [ + "No new recommendations this period. The secure configuration guidance remains current: " + f"{off.get('secure_configuration_guidance_url')}"], + "activeAgencies": [], + "reportableIncidents": {"incidents": reportable_incidents(incidents, period)}, + "metadata": {}, + "providerExtensions": { + "fedRampId": off["fedramp_id"], + "class": prof.get("fedramp_class"), + "impact_level": prof.get("impact_level"), + "ksi_signal_id": (signal or {}).get("signal_id"), + "report": kind, + "continuousMonitoring": _ccm.dates_summary(cal, ref), + "activeAgenciesStatement": "No agency uses this offering: it is an unsponsored proof of concept.", + "engagement": _engagement.STATEMENT, + "incidentAttestation": incident_summary(incidents, period[0].isoformat()), + "incidentRegister": ("data/incidents.json" if incidents is not None else + "No incident register in this build; the list above is empty because no " + "FedRAMP Reportable Incident has been recorded."), + "feedback": {"channel": _quarterly_review.INTAKE, + "howDelivered": "Each quarter simulated parties submit questions about the issued report " + "through the intake; they are answered by rule and discussed at its " + "Quarterly Review, and the anonymized summary appears in the next report " + f"({ENGAGEMENT_DECISION}). No real feedback is solicited.", + "summaryOfPreviousReport": feedback_on}, + "quarterlyReview": {"date": cal.review_date(review_issue).isoformat(), + "start": cal.review_start(review_issue).isoformat(), + "durationMinutes": cal.duration, + "calendar": _ccm.ICS_URL, "review": _ccm.review_url(review_issue), + "hostedBy": "Held on its date by package-maintenance.yml with simulated " + f"attendees; nobody needs to attend ({ENGAGEMENT_DECISION}).", + "agenda": STANDING_AGENDA}, + "publicRelease": {"decision": PUBLIC_RELEASE_DECISION, + "statement": "Published in full: it carries no federal customer or agency data and " + "passed the sensitivity screen below, so releasing it will not likely " + "have an adverse effect on the offering (CCM-OCR-RPS)."}, + }, + } + _engagement.require_none(doc, "the Ongoing Certification Report") + doc["providerExtensions"]["sensitivityScreen"] = _sensitivity.require_clean(doc, "the Ongoing Certification Report") + return _offering.stamp_version(doc, prev, now, "Automated: scripts/build-ocr.py, from the CCM calendar, the " + "SCN, decision and incident registers, the Quarterly Review feedback intake and the VDR report") + + +def main(argv=None): ap = argparse.ArgumentParser() ap.add_argument("--vdr", default="vdr-report.json") ap.add_argument("--decisions", default="../data/decisions.json") ap.add_argument("--scn-register", default="../docs/scn/scn-register.csv") ap.add_argument("--ksi-signal", default="ksi-signal.json") + ap.add_argument("--profile", default=str(REPO / "data" / "system-profile.json")) + ap.add_argument("--offering", default=str(_offering.OFFERING_PATH)) + ap.add_argument("--calendar", default=str(_ccm.CALENDAR_PATH)) + ap.add_argument("--incidents", default=str(INCIDENTS_PATH)) + ap.add_argument("--previous", default=None, help="the previously published rolling report (for its version)") + ap.add_argument("--issue", default=None, help="build the frozen report for this calendar issue date") ap.add_argument("--output", default="ongoing-certification-report.json") ap.add_argument("--md-output", default="ongoing-certification-report.md") - a = ap.parse_args() + a = ap.parse_args(argv) now = datetime.now(timezone.utc) - vdr = _load_json(a.vdr) - decisions = _decisions.load(a.decisions) - sig = _load_json(a.ksi_signal) - signal_id = sig.get("signal_id") if sig else None - scn_rows = _scn_rows(a.scn_register) - - report = build_ocr(vdr, decisions, scn_rows, signal_id, now) - Path(a.output).write_text(json.dumps(report, indent=2) + "\n") + today = now.date() + cal = _ccm.load(a.calendar, today) + prev = _load_json(a.previous) or {} + issue = date.fromisoformat(a.issue) if a.issue else None + doc = build(cal, today, _load_json(a.vdr), _decisions.load(a.decisions), _scn_rows(a.scn_register), + _incidents.load(a.incidents) if Path(a.incidents).is_file() else None, _load_json(a.ksi_signal), + json.loads(Path(a.profile).read_text()), _offering.load(a.offering), prev, now, issue) + fs.write_validated(doc, "ocr", a.output) if a.md_output: - Path(a.md_output).write_text(render_markdown(report) + "\n") - print(f"ongoing-certification-report: {len(report['summaries']['changes_to_certification_data'])} cert changes, " - f"{len(report['summaries']['planned_changes_next_quarter'])} planned, " - f"{len(report['summaries']['accepted_vulnerabilities'])} accepted vulns; " - f"next report {report['next_ongoing_certification_report_date']}") + Path(a.md_output).write_text(render_markdown(doc) + "\n") + cm = doc["providerExtensions"]["continuousMonitoring"] + print(f"ongoing-certification-report ({doc['providerExtensions']['report']['kind']}) " + f"{doc['reportPeriod']['from']}..{doc['reportPeriod']['to']}: " + f"{len(doc['certificationDataChanges'])} changes, " + f"{len(doc['reportableIncidents']['incidents'])} incidents; next report " + f"{cm['nextOngoingCertificationReportDate']}, next review {cm['nextQuarterlyReviewDate']}") return 0 +# --- human-readable view (same data as the JSON) -------------------------------------- + +def render_markdown(r): + pe, m = r["providerExtensions"], r["metadata"] + cm, qr, fb = pe["continuousMonitoring"], pe["quarterlyReview"], pe["feedback"] + rep = pe["report"] + title = (f"Ongoing Certification Report, issued {rep['issueDate']}" if rep["kind"] == "issued" + else "Ongoing Certification Report (since the latest issue)") + out = [f"# {title}", "", + f"- **FedRAMP ID:** {pe['fedRampId']} (simulated)", + f"- **Class:** {pe['class']} | **Reporting period:** {r['reportPeriod']['from']} to {r['reportPeriod']['to']}", + f"- **Version:** {m['version']} | **Last updated:** {m['lastUpdated']}", + f"- **Bound to inventory signal:** `{pe['ksi_signal_id']}`", + f"- **Next Ongoing Certification Report (CCM-OCR-NRD):** {cm['nextOngoingCertificationReportDate']}", + f"- **Next Quarterly Review (CCM-QTR-NRD):** {cm['nextQuarterlyReviewDate']}", + f"- **Feedback on this report:** {fb['channel']}", "", + f"> {pe['engagement']}", "", + f"> {rep['statement']}", ""] + + def section(n, t, lines): + out.extend([f"## {n}. {t}", "", *(lines or ["_None this period._"]), ""]) + + section(1, "Changes to certification data", [f"- {c}" for c in r["certificationDataChanges"]]) + pc = r["plannedCertificationDataChanges"] + section(2, f"Planned changes through {pc['planningHorizonThrough']}", [f"- {c}" for c in pc["changes"]]) + section(3, "Accepted vulnerabilities", [r["acceptedVulnerabilities"]]) + section(4, "Transformative changes", [f"- {c}" for c in r["transformativeChanges"]]) + section(5, "Updated recommendations", [f"- {c}" for c in r["updatedRecommendations"]]) + section(6, "Agencies using the offering", [f"- {a}" for a in r["activeAgencies"]] or + [pe["activeAgenciesStatement"]]) + inc = r["reportableIncidents"]["incidents"] + section(7, "FedRAMP Reportable Incidents", + [f"- {i['summary']} (occurred {i['occurredAt']}" + + (f", resolved {i['resolvedAt']})" if i.get("resolvedAt") else ")") for i in inc] + or ["No FedRAMP Reportable Incident occurred in this period."] + + ([pe["incidentAttestation"]] if pe.get("incidentAttestation") else [])) + lessons = [f"- {x}" for i in inc for x in i.get("incidentLessonsLearned", [])] + section(8, "Lessons learned from incidents", lessons) + s = fb["summaryOfPreviousReport"] + out += ["## Feedback on the previous report (anonymized)", "", s["statement"], ""] + out += [f"- **Q:** {i['question']} \n **A:** {i['answer']}" for i in s.get("items", [])] + out += ["", f"## Quarterly Review: {qr['date']}", "", + f"{qr['hostedBy']} Starts {qr['start']}, {qr['durationMinutes']} minutes. Calendar file: " + f"{qr['calendar']}. Review and transcript, once held: {qr['review']}.", "", "Agenda:", ""] + out += [f"{n}. {x}" for n, x in enumerate(qr["agenda"], 1)] + out += ["", "## Public release", "", f"{pe['publicRelease']['statement']} ({pe['publicRelease']['decision']}). " + f"Sensitivity screen: {', '.join(pe['sensitivityScreen']['checks'])}; " + f"{pe['sensitivityScreen']['findings']} findings.", "", + "---", "_Source of truth: the signed JSON. Rules: CCM-OCR-AVL, CCM-OCR-NRD, CCM-QTR-NRD._"] + return "\n".join(out) + + if __name__ == "__main__": sys.exit(main()) diff --git a/scripts/build-policy-index.py b/scripts/build-policy-index.py index 47bdb0b1..e78d9228 100644 --- a/scripts/build-policy-index.py +++ b/scripts/build-policy-index.py @@ -6,7 +6,10 @@ # and procedure, with seven fields each: name; file/page name; brief summary; # word count; current version; date of last update; related FedRAMP Practices. # This scans the repo's policy and procedure markdown and emits that index as -# JSON + human-readable markdown. Each entry's last-update date and version are the last commit that changed +# JSON + human-readable markdown, with every field in both, and (with +# --publish-dir) copies each document for publication under +# /.well-known/policies/. Related FedRAMP Practices are concrete rule and KSI IDs +# from the pinned rules and the KSI catalog, never free text. Each entry's last-update date and version are the last commit that changed # it; the build refuses a shallow clone, where every file looks changed today. # # build-policy-index.py # run from repo root @@ -19,24 +22,92 @@ import sys from pathlib import Path +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _offering # noqa: E402 + REPO = Path(__file__).resolve().parent.parent -# Family/topic -> related FedRAMP Practices, keyed by filename stem. -RELATED = { - "secure-configuration-guide": "SCG-CSO-*, SCG-ENH-*", - "cm-policy": "CM family; SCN-*, MAS-*, KSI-CMT", - "ir-policy": "IR family; IEC-CSO-*, VER-TFR-IRI, KSI-INR", - "ra-policy": "RA family; VDR-*, VER-*, KSI-MLA", - "sc-policy": "SC family; CMU-CSO-*, KSI-SVC", - "sr-policy": "SR family; KSI-SCR", - "continuous-monitoring-plan": "CCM-OCR-*, CCM-QTR-*", - "incident-response": "IR family; IEC-CSO-*", - "recovery-plan": "CP family; KSI-RPL", - "security-review": "CA family; KSI-PIY", - "supply-chain": "SR family; KSI-SCR", - "privacy-threshold-analysis": "PT family", - "rules-of-behavior": "PL-4, PS family", +SITE = "https://samaydlette.com/.well-known/policies/" +RULES_DIR = REPO / "infrastructure" / "schemas" / "fedramp-rules" +CATALOG = REPO / "infrastructure" / "schemas" / "ksi-catalog.json" + +# Procedures indexed beside the policies (CDS-CSO-IRP: "policies and procedures"). +PROCEDURES = ("docs/continuous-monitoring-plan.md", "docs/incident-response.md", "docs/recovery-plan.md", + "docs/security-review.md", "docs/supply-chain.md", "docs/privacy-threshold-analysis.md", + "docs/rules-of-behavior.md", "docs/verification.md", "docs/ksi-signal.md", + "docs/silk-reeling-deploy.md", "docs/architecture-decisions.md") +PROCEDURE_DIRS = ("docs/procedures", "docs/runbooks") + +# Related FedRAMP Practices, by document: prefixes of FedRAMP rule IDs and KSI +# IDs, expanded against the pinned rules and the KSI catalog (a prefix that +# matches nothing fails the build). An "<x>-policy" also gets every applicable +# rule and every KSI mapped to a control in its NIST family. +PRACTICES = { + "secure-configuration-guide": ("SCG-",), + "resource-tagging-standard": ("MAS-CSO-IIR", "MAS-CSO-FLO"), + "cm-policy": ("SCN-", "KSI-CMT-"), + "ir-policy": ("IEC-", "KSI-INR-"), + "ra-policy": ("VDR-", "VER-"), + "sc-policy": ("CMU-",), + "ca-policy": ("IVV-", "CCM-"), + "continuous-monitoring-plan": ("CCM-", "KSI-MLA-"), + "incident-response": ("IEC-", "KSI-INR-"), + "recovery-plan": ("KSI-RPL-",), + "security-review": ("KSI-PIY-", "CCM-QTR-"), + "supply-chain": ("KSI-SCR-", "MAS-CSO-TPR"), + "privacy-threshold-analysis": ("MAS-CSO-MDI",), + "rules-of-behavior": ("KSI-CED-",), + "verification": ("IVV-CSO-STE", "CDS-TRC-PAC", "SDR-CSO-"), + "ksi-signal": ("FRC-CSX-", "MAS-CSO-IIR"), + "silk-reeling-deploy": ("KSI-CMT-",), + "architecture-decisions": ("SCN-CSO-", "KSI-CMT-"), + "agency-access": ("CDS-TRC-AAI", "CDS-TRC-SSM", "CDS-UTC-"), + "information-sharing": ("CDS-CSO-RIS", "CDS-CSO-RPS"), + "evidence-sla-alarm": ("KSI-MLA-", "CDS-CSO-AVR"), + "vuln-gate-failure": ("VDR-", "KSI-SVC-VRI"), } +ACCESS = ("Every policy and procedure listed here is served as Markdown at its url (no authentication), and its " + "source is the file in the public repository. This index is published as JSON (policy-index.json, signed) " + "and Markdown (policy-index.md) and listed in the trust manifest (trust-manifest.json).") + + +def practice_ids(rules_dir=RULES_DIR, catalog_path=CATALOG): + """(sorted rule and KSI IDs, {NIST family: [IDs]}) from the pinned rules and the catalog.""" + sys.path.insert(0, str(Path(__file__).resolve().parent)) + import _rules # noqa: E402 + + rules, _ = _rules.load_rules(rules_dir) + applicable = _rules.applicable_provider_rules(rules_dir) + by_family = {} + + def walk(o): + if isinstance(o, dict): + for k, v in o.items(): + if k in applicable and isinstance(v, dict): + for c in v.get("controls") or []: + by_family.setdefault(c.split("-")[0], set()).add(k) + walk(v) + walk(rules.get("FRR", {})) + catalog = json.loads(Path(catalog_path).read_text()) + ksis = set() + for fam in catalog["KSI"].values(): + for ind in fam["indicators"]: + ksis.add(ind["id"]) + for c in ind.get("controls", []): + by_family.setdefault(c["control_id"].split("-")[0], set()).add(ind["id"]) + return sorted(set(applicable) | ksis), {f: sorted(v) for f, v in by_family.items()} + + +def related(stem, ids, by_family): + out = set() + for prefix in PRACTICES.get(stem, ()): + hit = [i for i in ids if i.startswith(prefix)] + if not hit: + sys.exit(f"build-policy-index: {stem}: {prefix!r} matches no FedRAMP rule or KSI") + out.update(hit) + if stem.endswith("-policy"): + out.update(by_family.get(stem.split("-")[0], [])) + return sorted(out) def _is_shallow(): @@ -77,61 +148,82 @@ def _name(text, stem): return stem.replace("-", " ").title() -def index_file(rel): +def index_file(rel, ids, by_family): path = REPO / rel text = path.read_text() stem = path.stem words = len(re.findall(r"\S+", text)) date, commit = _last_change(path) - related = RELATED.get(stem) or (f"{stem.split('-')[0].upper()} family" - if stem.endswith("-policy") else "general") return { "name": _name(text, stem), + "kind": "policy" if rel.startswith("docs/policies/") else "procedure", "file": rel, + "url": SITE + path.name, "summary": _summary(text), "word_count": words, "version": f"git:{commit[:12]}", "last_updated": date, - "related_practices": related, + "related_practices": related(stem, ids, by_family), } +def documents(): + files = sorted(str(p.relative_to(REPO)) for p in (REPO / "docs" / "policies").glob("*.md") + if p.name != "README.md") + files += [f for f in PROCEDURES if (REPO / f).exists()] + for d in PROCEDURE_DIRS: + files += sorted(str(p.relative_to(REPO)) for p in (REPO / d).glob("*.md") if p.name != "README.md") + names = [Path(f).name for f in files] + dup = sorted({n for n in names if names.count(n) > 1}) + if dup: + sys.exit(f"build-policy-index: two documents would publish as {dup}") + return files + + +def render_markdown(index): + out = ["# Policy and Procedure Index", "", + f"Machine- and human-readable index of {index['count']} policies and procedures " + "(CDS-CSO-IRP). Source of truth: the JSON alongside this file.", "", + f"**How to access them:** {index['access']}", ""] + for e in index["entries"]: + out += [f"## {e['name']}", "", + f"- **Kind:** {e['kind']} | **File:** [`{e['file']}`]({e['url']}) | **Words:** {e['word_count']}", + f"- **Version:** `{e['version']}` | **Last updated:** {e['last_updated']}", + f"- **Summary:** {e['summary']}", + f"- **Related FedRAMP Practices:** {', '.join(e['related_practices']) or 'none'}", ""] + return "\n".join(out) + + def main(): ap = argparse.ArgumentParser() ap.add_argument("--output", default="policy-index.json") ap.add_argument("--md-output", default="policy-index.md") + ap.add_argument("--publish-dir", default=None, help="copy every indexed document here for publication") a = ap.parse_args() if _is_shallow(): sys.exit("build-policy-index: shallow clone; the last-update dates need full history " "(actions/checkout fetch-depth: 0)") - files = sorted(str(p.relative_to(REPO)) for p in (REPO / "docs" / "policies").glob("*.md") - if p.name != "README.md") - for extra in ("docs/continuous-monitoring-plan.md", "docs/incident-response.md", - "docs/recovery-plan.md", "docs/security-review.md", "docs/supply-chain.md", - "docs/privacy-threshold-analysis.md", "docs/rules-of-behavior.md"): - if (REPO / extra).exists(): - files.append(extra) - - entries = [index_file(f) for f in files] + ids, by_family = practice_ids() + entries = [index_file(f, ids, by_family) for f in documents()] index = { "index_type": "policy-and-procedure-index", + "fedRampId": _offering.fedramp_id(), "rule": "CDS-CSO-IRP", + "access": ACCESS, "count": len(entries), "entries": entries, } Path(a.output).write_text(json.dumps(index, indent=2) + "\n") if a.md_output: - out = ["# Policy and Procedure Index", "", - f"Machine- and human-readable index of {len(entries)} policies and procedures " - "(CDS-CSO-IRP). Source of truth: the JSON alongside this file.", "", - "| Policy | File | Words | Last updated | Related Practices |", - "|---|---|---|---|---|"] + Path(a.md_output).write_text(render_markdown(index) + "\n") + if a.publish_dir: + # The documents themselves, served beside the index (CDS-CSO-IRP: supplied + # in the certification data, not only in the repository). + dest = Path(a.publish_dir) + dest.mkdir(parents=True, exist_ok=True) for e in entries: - out.append("| {n} | `{f}` | {w} | {u} | {r} |".format( - n=e["name"], f=e["file"], w=e["word_count"], - u=e["last_updated"], r=e["related_practices"])) - Path(a.md_output).write_text("\n".join(out) + "\n") + (dest / Path(e["file"]).name).write_bytes((REPO / e["file"]).read_bytes()) print(f"policy-index: {len(entries)} policies indexed") return 0 diff --git a/scripts/build-provenance.py b/scripts/build-provenance.py index f5a75077..9b503fa9 100644 --- a/scripts/build-provenance.py +++ b/scripts/build-provenance.py @@ -7,7 +7,7 @@ - the canonical inventory: ksi-signal.json content sha256 + its signal_id, - the generator that produced it (scripts/build-*.py, by content sha256), - this commit (git+repo@ref with gitCommit), and - - the CI run (builder id + invocationId). + - the CI workflow (builder id; no run ID, see runDetails below). The builder.id and commit are taken from build-ksi-signal.py's build_provenance() so there is ONE source of truth for the pinned identity (derived from @@ -67,7 +67,6 @@ def build_predicate(ksi_signal_path, generator_path): commit = source.get("commit") or os.environ.get("GITHUB_SHA", "unknown") ref = source.get("ref") or "refs/heads/main" repo_url = source.get("repository") or "https://github.com/sam-aydlette/samaydlette.com" - run_id = os.environ.get("GITHUB_RUN_ID", "unknown") return { "buildDefinition": { @@ -102,11 +101,13 @@ def build_predicate(ksi_signal_path, generator_path): }, ], }, + # SLSA v1.0 requires only runDetails.builder.id; BuildMetadata has no + # required field (https://slsa.dev/spec/v1.0/provenance#buildmetadata). + # invocationId is omitted: on GitHub Actions it would be the run ID, + # which published output never carries. The commit (resolvedDependencies) + # and the workflow (builder.id, externalParameters) identify the build. "runDetails": { "builder": {"id": builder_id}, - "metadata": { - "invocationId": f"{repo_url}/actions/runs/{run_id}", - }, }, } diff --git a/scripts/build-scg.py b/scripts/build-scg.py new file mode 100644 index 00000000..d72eedb1 --- /dev/null +++ b/scripts/build-scg.py @@ -0,0 +1,287 @@ +#!/usr/bin/env python3 +"""The Secure Configuration Guide and the cryptographic module list. + +Publishes /.well-known/secure-configuration-guide.json and .md from one source, +data/secure-configuration.json (SCG-CSO-RSC, SCG-CSO-PUB, SCG-CSO-AUP, +SCG-ENH-MRG, SCG-ENH-API, SCG-ENH-VRH), joined with the per-service +cryptographic module list in data/crypto-modules.json and the deploy's +inventory (CMU-CSO-CMD, CMU-CSO-UVM, CMU-CSO-CAT). + +Fails closed, before anything is written, when: + * the recommended defaults changed without a new version and a changelog + entry carrying their new digest (SCG-ENH-VRH); + * a setting names an unknown account, or cites a decision that is not in force; + * the inventory holds a component type that is neither mapped to a + cryptographic module nor declared as using no cryptography (CMU-CSO-CMD); + * the guide names a retired mechanism (the old shared app credential, the + deployer access key, Duo-enforced root MFA). + + build-scg.py --ksi-signal ksi-signal.json --output secure-configuration-guide.json \ + --md-output secure-configuration-guide.md +""" + +import argparse +import hashlib +import json +import re +import sys +from datetime import datetime, timezone +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _offering # noqa: E402 +import _decisions # noqa: E402 + +REPO = Path(__file__).resolve().parent.parent +SOURCE = REPO / "data" / "secure-configuration.json" +CRYPTO = REPO / "data" / "crypto-modules.json" +SITE = "https://samaydlette.com/.well-known/" +SEMVER = re.compile(r"^(\d+)\.(\d+)\.(\d+)$") +LEVELS = ("top-level", "privileged") +# Mechanisms this system no longer has. A guide that still describes one is +# wrong about the system, so the build stops (the 2026-11-05 assessment found +# the prose guide describing all three). +RETIRED = ( + (re.compile(r"basic[ -]auth", re.I), "the retired Silk Reeling shared (Basic Auth) credential"), + (re.compile(r"deployer (IAM )?user|AWS_ACCESS_KEY_ID|AWS_SECRET_ACCESS_KEY", re.I), "the retired deployer access key"), + (re.compile(r"(enforced|MFA) via Duo", re.I), "Duo-enforced root MFA (root uses virtual TOTP, DEC-150)"), +) + + +def _fail(msg): + raise SystemExit(f"::error::secure configuration guide: {msg} (fail-closed)") + + +def defaults_digest(src): + """sha256 over what a release fixes: each setting's account, recommended + value, check and accepted deviation. Wording changes don't move it.""" + body = sorted(({"id": s["id"], "account": s["account"], "recommended": s["recommended"], + "check": s["check"], "accepted_deviation": s.get("accepted_deviation")} + for s in src["settings"]), key=lambda s: s["id"]) + return hashlib.sha256(json.dumps(body, sort_keys=True, separators=(",", ":")).encode()).hexdigest() + + +def _semver(v, where): + m = SEMVER.match(v or "") + if not m: + _fail(f"{where}: version {v!r} is not MAJOR.MINOR.PATCH") + return tuple(int(x) for x in m.groups()) + + +def validate_source(src, in_force_ids): + if not isinstance(src, dict) or src.get("schema") != "secure-configuration/1": + _fail("the source is not a secure-configuration/1 document") + for k in ("title", "version", "obtain_and_use", "accounts", "settings", "changelog"): + if not src.get(k): + _fail(f"the source has no {k}") + accounts = {} + for a in src["accounts"]: + for k in ("id", "level", "name", "how_named", "access", "configure", "operate", "decommission"): + if not isinstance(a.get(k), str) or not a[k].strip(): + _fail(f"account {a.get('id')!r} has no {k}") + if a["level"] not in LEVELS: + _fail(f"account {a['id']}: level must be one of {LEVELS}") + accounts[a["id"]] = a + if not any(a["level"] == "top-level" for a in accounts.values()): + _fail("no top-level administrative account is described") + seen, checks = set(), set() + for s in src["settings"]: + sid = s.get("id") + for k in ("id", "account", "operable_by", "setting", "implication", "read", "change", "check"): + if not isinstance(s.get(k), str) or not s[k].strip(): + _fail(f"setting {sid!r} has no {k}") + if "recommended" not in s: + _fail(f"setting {sid} has no recommended value") + if sid in seen: + _fail(f"setting {sid} appears twice") + seen.add(sid) + if s["account"] not in accounts: + _fail(f"setting {sid} names unknown account {s['account']!r}") + if s["check"] == "attested": + if s.get("attested_by") not in in_force_ids: + _fail(f"setting {sid} is attested but cites no in-force decision") + elif s["check"] in checks: + _fail(f"check {s['check']} is used by two settings") + checks.add(s["check"]) + dev = s.get("accepted_deviation") + if dev is not None and dev not in in_force_ids: + _fail(f"setting {sid} cites {dev!r} as its accepted deviation, which is not an in-force decision") + # SCG-ENH-VRH: versioned, with a release history of the defaults. + prev = None + for entry in src["changelog"]: + v = _semver(entry.get("version"), "changelog") + if prev is not None and v <= prev: + _fail("changelog versions must increase") + if not entry.get("date") or not entry.get("changes"): + _fail(f"changelog {entry.get('version')} has no date or changes") + prev = v + latest = src["changelog"][-1] + if latest["version"] != src["version"]: + _fail(f"version {src['version']} has no changelog entry (latest is {latest['version']})") + digest = defaults_digest(src) + if latest.get("defaults_sha256") != digest: + _fail(f"the recommended defaults changed since version {src['version']} was released: bump the version " + f"and add a changelog entry with defaults_sha256 {digest}") + return src + + +def module_list(crypto, signal): + """Per-service module list joined with the inventory's component types. + Fails on a type that is neither mapped nor declared cryptography-free.""" + modules = crypto["modules"] + by_type = {} + for svc in crypto["services"]: + if svc["module"] not in modules: + _fail(f"{svc['service']}: unknown module {svc['module']!r}") + for t in svc["types"]: + if t in by_type: + _fail(f"component type {t} is mapped twice") + by_type[t] = svc + none = set(crypto["no_cryptography"]["types"]) + if none & set(by_type): + _fail(f"types both mapped and declared cryptography-free: {sorted(none & set(by_type))}") + counts = {} + for c in signal.get("components", []): + counts[c.get("type")] = counts.get(c.get("type"), 0) + 1 + unmapped = sorted(t for t in counts if t not in by_type and t not in none) + if unmapped: + _fail(f"the inventory has component type(s) with no cryptographic module mapping: {', '.join(map(str, unmapped))}. " + "Map each in data/crypto-modules.json (or declare it cryptography-free)") + out = [] + for svc in crypto["services"]: + m = modules[svc["module"]] + out.append({"service": svc["service"], "protects": svc["protects"], "configuration": svc["configuration"], + "protects_customer_data": svc["customer_data"], + "agency_tenant_default": svc.get("tenant_default"), + "components": sum(counts.get(t, 0) for t in svc["types"]), "component_types": svc["types"], + "module": m["name"], "cmvp_certificate": m["cmvp_certificate"], "standard": m["standard"], + "level": m["level"], "validation_status": m["status"], "source": m["source"], + "validated": m["cmvp_certificate"] is not None}) + return out + + +def build(src, crypto, signal, now): + doc = { + "schema": "secure-configuration-guide/1", + "title": src["title"], + "version": src["version"], + "emitted_at": now.isoformat(timespec="seconds"), + "ksi_signal_id": signal.get("signal_id"), + "source": "Generated by scripts/build-scg.py from data/secure-configuration.json and " + "data/crypto-modules.json, joined with this deploy's inventory.", + "human_readable": SITE + "secure-configuration-guide.md", + "machine_readable": SITE + "secure-configuration-guide.json", + "comparison": SITE + "security-settings.json", + "obtain_and_use": src["obtain_and_use"], + "accounts": src["accounts"], + "settings": src["settings"], + "release_history": src["changelog"], + "cryptographic_modules": { + "checked_on": crypto["checked_on"], + "services": module_list(crypto, signal), + "no_cryptography": crypto["no_cryptography"], + }, + } + text = json.dumps(doc) + "\n" + render_markdown(doc) + for pat, what in RETIRED: + if pat.search(text): + _fail(f"the guide names {what}") + return doc + + +def _value(v): + if isinstance(v, dict): + return "; ".join(f"{k} {_value(x)}" for k, x in v.items()) + if isinstance(v, list): + return ", ".join(map(str, v)) + if isinstance(v, bool): + return "yes" if v else "no" + if v is None: + return "—" + return str(v) + + +def _cell(text): + return str(text).replace("|", "\\|").replace("\n", " ") + + +def render_markdown(doc): + out = [f"# {doc['title']}", "", + f"- **Version:** {doc['version']} | **Generated:** {doc['emitted_at']}", + f"- **Machine-readable:** {doc['machine_readable']}", + f"- **Live comparison:** {doc['comparison']}", + f"- **Source:** {doc['source']}", "", "## How to obtain and use this guide", ""] + out += [f"- {line}" for line in doc["obtain_and_use"]] + out += ["", "## Accounts", ""] + for a in doc["accounts"]: + out += [f"### {a['name']} (`{a['id']}`, {a['level']})", "", + f"- **How it is named:** {a['how_named']}", f"- **Secure access:** {a['access']}", + f"- **Configure:** {a['configure']}", f"- **Operate:** {a['operate']}", + f"- **Decommission:** {a['decommission']}", ""] + out += ["## Security settings", "", + "| Setting | Account | Operable by | Recommended | Implication | Read | Change | Deviation |", + "|---|---|---|---|---|---|---|---|"] + for s in doc["settings"]: + dev = s.get("accepted_deviation") or (f"attested ({s['attested_by']})" if s.get("attested_by") else "—") + out.append(f"| `{s['id']}`: {_cell(s['setting'])} | {s['account']} | {_cell(s['operable_by'])} | " + f"{_cell(_value(s['recommended']))} | {_cell(s['implication'])} | {_cell(s['read'])} | " + f"{_cell(s['change'])} | {dev} |") + cm = doc["cryptographic_modules"] + out += ["", f"## Cryptographic modules per service (checked {cm['checked_on']})", "", + "| Service | Components | Module | CMVP certificate | Status | Protects customer data | " + "Agency-tenant default | Configuration |", "|---|---|---|---|---|---|---|---|"] + for m in cm["services"]: + cert = f"[#{m['cmvp_certificate']}]({m['source']})" if m["cmvp_certificate"] else "none" + out.append(f"| {_cell(m['service'])} | {m['components']} | {_cell(m['module'])} | {cert} | " + f"{_cell(m['validation_status'])} | {_value(m['protects_customer_data'])} | " + f"{_cell(_value(m['agency_tenant_default']))} | {_cell(m['configuration'])} |") + out += ["", f"Cryptography-free component types: {', '.join(cm['no_cryptography']['types'])}. " + f"{cm['no_cryptography']['why']}", "", "## Release history", ""] + for r in reversed(doc["release_history"]): + out.append(f"### {r['version']} ({r['date']})") + out += [f"- {c}" for c in r["changes"]] + out.append(f"- Defaults digest: `{r['defaults_sha256']}`") + out.append("") + out += ["---", "_Source of truth: the signed `secure-configuration-guide.json`._"] + return "\n".join(out) + + +def load(source=SOURCE, decisions_path=None): + try: + src = json.loads(Path(source).read_text()) + except (OSError, json.JSONDecodeError) as exc: + _fail(f"cannot read {source}: {exc}") + reg = _decisions.load(decisions_path) + return validate_source(src, {r["id"] for r in _decisions.in_force(reg)}) + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + ap.add_argument("--source", default=str(SOURCE)) + ap.add_argument("--crypto", default=str(CRYPTO)) + ap.add_argument("--decisions", default=None) + ap.add_argument("--ksi-signal", default="ksi-signal.json") + ap.add_argument("--output", default="secure-configuration-guide.json") + ap.add_argument("--md-output", default="secure-configuration-guide.md") + ap.add_argument("--print-digest", action="store_true", help="print the defaults digest and exit") + a = ap.parse_args(argv) + if a.print_digest: + print(defaults_digest(json.loads(Path(a.source).read_text()))) + return 0 + src = load(a.source, a.decisions) + try: + crypto = json.loads(Path(a.crypto).read_text()) + signal = json.loads(Path(a.ksi_signal).read_text()) + except (OSError, json.JSONDecodeError) as exc: + _fail(f"cannot read an input: {exc}") + doc = _offering.stamp_fedramp_id(build(src, crypto, signal, datetime.now(timezone.utc))) # CDS-CSO-FID + Path(a.output).write_text(json.dumps(doc, indent=2) + "\n") + Path(a.md_output).write_text(render_markdown(doc) + "\n") + v = sum(1 for m in doc["cryptographic_modules"]["services"] if m["validated"]) + print(f"secure-configuration-guide {doc['version']}: {len(doc['settings'])} settings, " + f"{len(doc['cryptographic_modules']['services'])} services ({v} on a CMVP-validated module)") + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/build-scn.py b/scripts/build-scn.py new file mode 100644 index 00000000..c3e6dd2d --- /dev/null +++ b/scripts/build-scn.py @@ -0,0 +1,423 @@ +#!/usr/bin/env python3 +# ============================================================================= +# SIGNIFICANT CHANGE NOTIFICATIONS + EVALUATION LOG (SCN-*) +# ============================================================================= +# Run by the deploy, after the build and before signing. Writes, into --out-dir: +# +# scn/<SCN-ID>.json one notification per register row, +# each validated against FedRAMP's +# SCN schema (write_validated) +# significant-change-notifications.json the index: every notification, +# its notices and their dates (HIS) +# significant-change-notifications.md the human-readable view (HRM) +# significant-change-notifications.atom the subscribable feed (NOM) +# scn-evaluations.json / .md the evaluation log (MAR, HRM) +# +# Both the index and the log only ever grow. The previous published copies are +# fetched by the deploy and passed in; a build that would drop or rewrite a +# published entry fails (SCN-CSO-HIS, SCN-CSO-MAR). A notice keeps the date it +# was first published, which is the date it was given: FedRAMP's rules name the +# notification method for every SCN notice as an update to the Certification +# Data, and this publication is that update. Nothing is sent to anyone. +# +# The evaluation log takes one entry per first-parent commit on main after the +# last one it holds: the SCN-Type, rationale and record from the merged pull +# request's description (or the commit message for a direct push), who merged +# it and when. With no previous log, it starts at the commit that introduced +# this builder, so a lost copy is rebuilt from git rather than restarted. +# +# build-scn.py --previous-index prev-index.json --previous-log prev-log.json +# ============================================================================= + +import argparse +import json +import os +import re +import subprocess +import sys +from datetime import date, datetime, timezone +from pathlib import Path +from xml.sax.saxutils import escape + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _fedramp_schema # noqa: E402 +import _engagement # noqa: E402 +import _offering # noqa: E402 +import _redact # noqa: E402 +import _scn # noqa: E402 + +REPO = _scn.REPO +GENESIS_PATH = "scripts/build-scn.py" +SHA_RE = re.compile(r"^[0-9a-f]{40}$") +MERGE_RE = re.compile(r"^Merge pull request #(\d+) from ") +RUN_ID_RE = re.compile(r"(actions/runs/|run )\d{6,}") + +MECHANISMS = [ + {"mechanism": "Atom feed", "url": _scn.BASE + _scn.FEED_NAME, + "description": "One entry per notice (adaptive after-finish; transformative initial plan, final plan, " + "after finish, after verification). Any feed reader can subscribe; no account needed."}, + {"mechanism": "Signed JSON index", "url": _scn.BASE + _scn.INDEX_NAME + ".json", + "description": "Every notification in FedRAMP's SCN schema with each notice's publication date and " + "deadline; signed with Sigstore (.bundle beside it)."}, + {"mechanism": "Human-readable view", "url": _scn.BASE + _scn.INDEX_NAME + ".md", + "description": "The same notifications as a Markdown document."}, +] +ACCESS = ("All notifications and the evaluation log are public at the URLs above, in JSON and human-readable " + "form; no request is needed. The register they are built from is docs/scn/scn-register.csv in the " + "public repository.") +SHARING = ("Everything is published to everyone: the system holds no federal data and no agency customer, so " + "there is nothing in a notification to withhold. A notification that ever needed to carry sensitive " + "detail would publish a summary and say how to request the rest.") +NOTIFICATION = ("Notification is publication. FedRAMP's rules name the method for each SCN notice as an update to " + "the FedRAMP Certification Data; publishing here is that update. Nothing is sent by email or to " + "FedRAMP directly. A notice's publishedOn is the first deploy that published it.") + + +def _today(): + return datetime.now(timezone.utc).date() + + +def _load(path): + if not path or not Path(path).is_file() or Path(path).stat().st_size == 0: + return None + return json.loads(Path(path).read_text()) + + +# --- the evaluation log -------------------------------------------------------------- + +def _git(*args, root=REPO): + return subprocess.run(["git", *args], cwd=root, check=True, capture_output=True, text=True).stdout.strip() + + +def gh_pull(number): + """The pull request's description and merger, via the GitHub API (gh, GH_TOKEN).""" + repo = os.environ.get("GITHUB_REPOSITORY", "sam-aydlette/samaydlette.com") + out = subprocess.run(["gh", "api", f"repos/{repo}/pulls/{number}"], check=True, capture_output=True, text=True) + pr = json.loads(out.stdout) + return {"body": pr.get("body") or "", "merged_by": (pr.get("merged_by") or {}).get("login"), + "author": (pr.get("user") or {}).get("login")} + + +def _scrub(text): + """Free text from a PR description, made safe to publish.""" + return LONG_NUMBER.sub("<number>", RUN_ID_RE.sub(r"\1<run>", _redact.redact_text(text))) + + +# A standalone number of 9 to 11 digits in published text is most likely a +# GitHub run ID; 12 digits is an AWS account ID, which the publication gate +# catches. Neither belongs in a notification. +LONG_NUMBER = re.compile(r"(?<![0-9A-Za-z])[0-9]{9,11}(?![0-9A-Za-z])") + + +def long_number_errors(name, text): + return [f"{name}: a {len(m)}-digit number (a run ID?) would be published" for m in LONG_NUMBER.findall(text)] + + +def evaluation_entry(commit, subject, body, merged_on, author, lookup): + m = MERGE_RE.match(subject) + if m: + pr = lookup(int(m.group(1))) + text, evaluator, number = pr["body"], pr.get("merged_by") or pr.get("author"), int(m.group(1)) + else: + text, evaluator, number = f"{subject}\n{body}", author, None + entry = {"commit": commit, "merged_on": merged_on, "pull_request": number, "evaluator": evaluator or "unknown"} + try: + ev = _scn.parse_evaluation(text) + entry.update(scn_type=ev["type"], rationale=_scrub(ev["rationale"]), scn_record=ev["record"], problem=None) + except _scn.EvaluationError as exc: + entry.update(scn_type=None, rationale=None, scn_record=None, problem=f"no valid evaluation: {exc}") + return entry + + +def collect(previous_entries, root=REPO, lookup=gh_pull, head="HEAD"): + """Entries for the first-parent commits after the last one logged.""" + if previous_entries: + last = previous_entries[-1].get("commit", "") + # Read from the published log: a full SHA or nothing, never an option. + if not SHA_RE.match(last): + raise SystemExit("::error::SCN log: the published log's last entry has no valid commit (fail-closed)") + try: + _git("merge-base", "--is-ancestor", last, head, root=root) + except subprocess.CalledProcessError: + raise SystemExit(f"::error::SCN log: last logged commit {last[:12]} is not an ancestor of {head}; " + "history was rewritten (fail-closed)") from None + span = f"{last}..{head}" + shas = _git("rev-list", "--first-parent", "--reverse", span, root=root).split() + else: + first = _git("log", "--first-parent", "--reverse", "--format=%H", head, "--", GENESIS_PATH, root=root).split() + if not first: + raise SystemExit(f"::error::SCN log: no commit introduces {GENESIS_PATH} (fail-closed)") + parent = _git("rev-list", "--max-count=1", f"{first[0]}^1", root=root) if _has_parent(first[0], root) \ + else None + span = f"{parent}..{head}" if parent else head + shas = _git("rev-list", "--first-parent", "--reverse", span, root=root).split() + out = [] + for sha in shas: + subject, body, when, author = _git("show", "-s", "--format=%s%x00%b%x00%cI%x00%an", sha, root=root) \ + .split("\x00") + out.append(evaluation_entry(sha, subject, body, when[:10], author, lookup)) + return out + + +def _has_parent(sha, root): + try: + _git("rev-parse", "--verify", "--quiet", f"{sha}^1", root=root) + return True + except subprocess.CalledProcessError: + return False + + +def build_log(previous, new_entries, now, commit): + prev = (previous or {}).get("entries", []) + entries = prev + new_entries + errors = _scn.append_only_errors(prev, entries, "commit") + if errors: + raise SystemExit("::error::SCN evaluation log is append-only: " + "; ".join(errors)) + return _offering.stamp_fedramp_id({ + "$comment": "SCN-CSO-MAR: the significant-change evaluation of every change merged to main, one entry per " + "first-parent commit. Append-only: each deploy adds the commits since the last entry, and " + "a deploy that would drop or rewrite an entry fails. Built by scripts/build-scn.py.", + "generated_at": now.isoformat(), + "commit": commit, + "genesis_commit": (previous or {}).get("genesis_commit") or (entries[0]["commit"] if entries else None), + "access": ACCESS, + "entries": entries, + "unrecorded": sum(1 for e in entries if e["problem"]), + }) + + +def render_log_md(log): + out = ["# Significant-change evaluation log (SCN-CSO-MAR)", "", + f"_Generated {log['generated_at']} from commit `{log['commit']}`. The signed JSON beside this file is " + "the record; this is its rendering._", "", + f"{len(log['entries'])} evaluations; {log['unrecorded']} without a valid evaluation.", "", + "| Merged | Commit | PR | Type | Record | Evaluator | Rationale |", "|---|---|---|---|---|---|---|"] + for e in reversed(log["entries"]): + rationale = e["rationale"] or f"_{e['problem']}_" + out.append("| {d} | `{c}` | {p} | {t} | {r} | {who} | {why} |".format( + d=e["merged_on"], c=e["commit"][:12], p=f"#{e['pull_request']}" if e["pull_request"] else "direct", + t=e["scn_type"] or "-", r=e["scn_record"] or "", who=e["evaluator"], why=rationale.replace("|", "\\|"))) + return "\n".join(out) + + +# --- notifications ------------------------------------------------------------------- + +def _fedramp_id(row): + """The register's ID when FedRAMP has assigned one; until then the + offering's (CDS-CSO-FID: FedRAMP's fallback, marked not real).""" + v = row["fedramp_id"] + return _offering.fedramp_id() if not v or v.startswith("<") else v + + +def scn_document(row, previous_notices, today): + start = row["date_started"] or row["date_initiated"] + plan = {"summary": row["plan_and_timeline"], "plannedStart": start} + if row["date_finished"]: + plan["plannedCompletion"] = row["date_finished"] + doc = { + "$schema": _fedramp_schema.stamp("scn"), + "certificationPackageOverviewUri": _fedramp_schema.CPO_URI, + "scnId": row["scn_id"], + "serviceOfferingFedrampId": _fedramp_id(row), + "serviceOfferingFedrampIdNote": None if _fedramp_id(row) != _offering.fedramp_id() else + "Simulated: no FedRAMP ID has been assigned (the offering is not FedRAMP certified). This is " + "FedRAMP's fallback, the provider name and acronym, marked so nobody mistakes it for a real ID.", + "assessorName": row["assessor_name"], + "relatedVulnerability": row["related_vulnerability"], + "changeType": row["scn_type"].capitalize(), + "changeTypeExplanation": row["categorization_rationale"], + "changeDescription": row["short_description"], + "reason": row["reason_for_change"], + "customerImpact": row["customer_impact"], + "planAndTimeline": plan, + "impactAnalysis": _scn.SOURCE_URL + row["sia_reference"], + "approver": {"name": row["approver_name"], "title": row["approver_title"]}, + "newRisksSummary": row["new_risks_summary"], + "emergency": row["emergency"] == "yes", + "notices": _scn.merge_notices(row, previous_notices, today), + # SCN-CSO-ARI: what else a reviewer needs to judge the change. + "additionalInformation": { + "status": row["status"], + "dateInitiated": row["date_initiated"], + "dateFinished": row["date_finished"] or None, + "verifiedOn": row["verified_on"] or None, + "changes": [p.strip() for p in row["evaluation_prs"].split(";") if p.strip()], + "record": _scn.SOURCE_URL + row["sia_reference"], + }, + } + if row["scn_type"] == "transformative": + doc["transformative"] = { + "planFinal": row["plan_final"] == "yes", + "thirdPartyReview": {"humanValidationNeeded": row["tpr_human_validation"] == "yes", + "assessorOrReasonNotEngaged": row["tpr_assessor_or_reason"]}, + "securityAssessmentReport": row["sar_reference"] or None, + "documentationUpdate": { + "documents": [d.strip() for d in row["docs_to_update"].split(";") if d.strip()], + "updatedOn": row["docs_updated_on"] or None, + "notRequiredBecause": row["docs_update_not_required"] or None, + "deadline": (_scn.docs_update_deadline(row) or date.min).isoformat() + if row["date_finished"] else None, + }, + } + return doc + + +def build_index(rows, previous_index, now, commit, out_dir): + prev_docs = {s["scnId"]: s for s in (previous_index or {}).get("notifications", [])} + scn_dir = Path(out_dir) / "scn" + scn_dir.mkdir(parents=True, exist_ok=True) + docs = [] + for row in rows: + prev = prev_docs.get(row["scn_id"], {}) + row = _scn.resolve_on_deploy(row, prev, now.date()) + doc = _offering.stamp_fedramp_id(scn_document(row, prev.get("notices", []), now.date())) + path = scn_dir / f"{row['scn_id']}.json" + _fedramp_schema.write_validated(doc, "scn", path) + docs.append(json.loads(path.read_text())) + late = [f"{d['scnId']} {n['stage']}" for d in docs for n in d["notices"] if not n["onTime"]] + index = { + "$comment": "SCN-CSO-HIS / SCN-CSO-HRM / SCN-CSO-NOM: every Significant Change Notification, each in " + "FedRAMP's SCN schema, with each notice's deadline and the date it was published. Never " + "pruned: a deploy that would drop a notification or re-date a notice fails. Built by " + "scripts/build-scn.py from docs/scn/scn-register.csv.", + "generated_at": now.isoformat(), + "commit": commit, + "certificationPackageOverviewUri": _fedramp_schema.CPO_URI, + "notification": NOTIFICATION, + "engagement": _engagement.STATEMENT, + "notificationMechanisms": MECHANISMS, + "access": ACCESS, + "sharing": SHARING, + "retention": "All notifications are kept, which exceeds the 12 months SCN-CSO-HIS requires.", + "evaluationLog": _scn.BASE + _scn.LOG_NAME + ".json", + "lateNotices": late, + "notifications": docs, + } + errors = _scn.retention_errors(previous_index, index) + if errors: + raise SystemExit("::error::SCN notifications are retained (SCN-CSO-HIS): " + "; ".join(errors)) + return _offering.stamp_fedramp_id(index) + + +def render_index_md(index): + out = ["# Significant Change Notifications", "", + f"_Generated {index['generated_at']} from commit `{index['commit']}`. The signed JSON beside this " + "file is the record; this is its rendering._", "", + index["notification"], "", + "## How to receive them (SCN-CSO-NOM)", ""] + out += [f"- **{m['mechanism']}:** {m['url']} — {m['description']}" for m in index["notificationMechanisms"]] + out += ["", f"**Access.** {index['access']}", "", f"**Sharing.** {index['sharing']}", "", + f"**Retention.** {index['retention']}", "", + f"**Evaluation log (SCN-CSO-MAR):** {index['evaluationLog']}", ""] + if index["lateNotices"]: + out += ["**Notices published after their deadline:** " + ", ".join(index["lateNotices"]), ""] + for d in reversed(index["notifications"]): + out += [f"## {d['scnId']} — {d['changeType']}{' (emergency)' if d['emergency'] else ''}", "", + d["changeDescription"], "", + f"- **Service Offering FedRAMP ID:** {d['serviceOfferingFedrampId'] or d['serviceOfferingFedrampIdNote']}", + f"- **Assessor:** {d.get('assessorName') or '-'}", + f"- **Related vulnerability:** {d.get('relatedVulnerability') or '-'}", + f"- **Why this type:** {d['changeTypeExplanation']}", + f"- **Reason:** {d['reason']}", + f"- **Customer impact:** {d['customerImpact']}", + f"- **Plan and timeline:** {d['planAndTimeline']['summary']}", + f"- **Impact analysis:** {d['impactAnalysis']}", + f"- **New risks:** {d['newRisksSummary'] or '-'}", + f"- **Approver:** {d['approver']['name']}, {d['approver']['title']}", + f"- **Status:** {d['additionalInformation']['status']}"] + if "transformative" in d: + t = d["transformative"] + tpr = t["thirdPartyReview"] + out += [f"- **Human validation needed:** {'yes' if tpr['humanValidationNeeded'] else 'no'}; " + f"{tpr['assessorOrReasonNotEngaged']}", + f"- **Security assessment report:** {t['securityAssessmentReport'] or '-'}", + f"- **Documentation update:** {', '.join(t['documentationUpdate']['documents']) or '-'}; " + f"updated {t['documentationUpdate']['updatedOn'] or 'not yet'}"] + out += ["", "| Notice | Rule | Deadline | Published | On time |", "|---|---|---|---|---|"] + out += [f"| {n['stage']} | {n['rule']} | {n['deadline']} | {n['publishedOn']} | " + f"{'yes' if n['onTime'] else 'no'} |" for n in d["notices"]] + out.append("") + return "\n".join(out) + + +def render_feed(index): + """Atom (RFC 4287): one entry per notice, dated when it was published.""" + entries = [] + for d in index["notifications"]: + for n in d["notices"]: + entries.append((n["publishedOn"], d, n)) + entries.sort(key=lambda e: (e[0], e[1]["scnId"], e[2]["stage"]), reverse=True) + updated = (entries[0][0] if entries else index["generated_at"][:10]) + "T00:00:00Z" + out = ['<?xml version="1.0" encoding="utf-8"?>', + '<feed xmlns="http://www.w3.org/2005/Atom">', + " <title>samaydlette.com Significant Change Notifications", + f" FedRAMP ID: {escape(index['fedRampId'])}", + " tag:samaydlette.com,2026:significant-change-notifications", + f" {updated}", + f' ', + f' ', + " samaydlette.com"] + for on, d, n in entries: + title = f"{d['scnId']} ({d['changeType']}) {n['stage']} notice: {d['changeDescription'][:120]}" + summary = (f"{d['changeDescription']} Rule {n['rule']}; deadline {n['deadline']}; published {on}" + f"{'' if n['onTime'] else ' (after the deadline)'}. Customer impact: {d['customerImpact']}") + out += [" ", + f" tag:samaydlette.com,2026:scn/{d['scnId']}/{n['stage']}", + f" {escape(title)}", + f" {on}T00:00:00Z", + f' ', + f" {escape(summary)}", + " "] + out.append("") + return "\n".join(out) + "\n" + + +def main(argv=None): + ap = argparse.ArgumentParser(description="Build the SCN notifications and evaluation log.") + ap.add_argument("--register", default=str(_scn.REGISTER)) + ap.add_argument("--previous-index", help="the published index (absent on the first publish)") + ap.add_argument("--previous-log", help="the published evaluation log (absent on the first publish)") + ap.add_argument("--out-dir", default=".") + ap.add_argument("--repo-root", default=str(REPO)) + ap.add_argument("--commit", default=os.environ.get("GITHUB_SHA", "")) + ap.add_argument("--new-evaluations", help="JSON list of entries to append instead of reading git (tests)") + a = ap.parse_args(argv) + + now = datetime.now(timezone.utc).replace(microsecond=0) + header, rows = _scn.read_register(a.register) + errors = _scn.validate_register(header, rows, a.repo_root) + if errors: + for e in errors: + print(f"::error::scn-register: {e}", file=sys.stderr) + return 1 + out = Path(a.out_dir) + prev_index, prev_log = _load(a.previous_index), _load(a.previous_log) + + index = build_index(rows, prev_index, now, a.commit, out) + if a.new_evaluations: + new = json.loads(Path(a.new_evaluations).read_text()) + else: + new = collect((prev_log or {}).get("entries", []), root=a.repo_root) + log = build_log(prev_log, new, now, a.commit) + + outputs = { + f"{_scn.INDEX_NAME}.json": json.dumps(index, indent=2) + "\n", + f"{_scn.INDEX_NAME}.md": render_index_md(index) + "\n", + _scn.FEED_NAME: render_feed(index), + f"{_scn.LOG_NAME}.json": json.dumps(log, indent=2) + "\n", + f"{_scn.LOG_NAME}.md": render_log_md(log) + "\n", + } + errors = [e for name, text in outputs.items() for e in long_number_errors(name, text)] + if errors: + for e in errors: + print(f"::error::{e}", file=sys.stderr) + return 1 + for name, text in outputs.items(): + (out / name).write_text(text) + print(f"scn: {len(index['notifications'])} notifications ({len(index['lateNotices'])} notice(s) published " + f"late); evaluation log {len(log['entries'])} entries (+{len(new)}, {log['unrecorded']} unrecorded)") + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/build-sdr.py b/scripts/build-sdr.py index 70dc500b..05b404bd 100644 --- a/scripts/build-sdr.py +++ b/scripts/build-sdr.py @@ -1,273 +1,955 @@ #!/usr/bin/env python3 # ============================================================================= -# SECURITY DECISION RECORD BUILDER (CR26 SDR — the 20x SSP replacement) +# SECURITY DECISION RECORD BUILDER (CR26 SDR, FedRAMP's 2026-06-24 schema) # ============================================================================= -# CR26 replaces the traditional System Security Plan with a persistently -# maintained Security Decision Record (SDR-CSO-FRR): for each applicable FedRAMP -# rule, an explanation of how it is followed, plus verification, validation, -# independent verification, independent validation, responses to assessor -# comments, and rule-specific artifacts. SDR-CSO-MTD carries version + last -# update + source; the 20x extension SDR-CSX-KSI carries per-KSI summaries, and -# SDR-CSX-KMT (Class C) carries metric summaries over 30 days / up to a year / -# all daily metric data. +# The SDR says, for this 20x Class C offering: # -# It carries both views CR26 defines over the same rule families: per KSI -# (SDR-CSX-KSI, the 20x record) and per applicable Rev5 control (SDR-CSF-CTF, -# the Rev5 record, in rev5_controls). Both come from the control projection -# (scripts/_controls.py) computed from the canonical inventory and the KSI -# catalog, so they cannot disagree. The OSCAL SSP that used to carry the -# per-control statements is retired (CR26); this record replaces it. +# fedRampRequirements every applicable FedRAMP rule (SDR-CSO-FRR), from the +# governed records in data/frr-records.json, which +# scripts/_frr.py holds to the pinned rules and to +# evidence that resolves; +# keySecurityIndicators every KSI (SDR-CSX-KSI): its measures (the OPA rules +# annotated with it), the automated methods that verify +# it (the deploy-time plan gate and the signed runtime +# re-validation), tests and evidence; +# securityControls every NIST 800-53 Rev5 control in the FedRAMP Moderate +# baseline, plus the controls FedRAMP's KSIs map beyond +# it: how 20x meets each Rev5 objective. A control's +# status is no stronger than what backs it. +# +# The record is 20x. The control view explains how the Rev5 objectives are met +# by the 20x evidence; it is not a second certification claim. +# +# Status rules for a control (the honesty rule, applied to Rev5): +# Implemented inherited from AWS (its FedRAMP authorization), or +# backed by a KSI whose measures are checked +# automatically, or by an implemented FedRAMP rule, or, +# for a policy-and-procedure control (XX-1), the +# family's published policy; +# (no status) not applicable, with the reason; +# Partially Implemented everything else the projection calls implemented: +# the mechanism is described but nothing checks it yet. +# +# Validated against the vendored schema before it is written; nothing that +# fails is written. Site-specific data is under providerExtensions. # # build-sdr.py --catalog schemas/ksi-catalog.json --ksi-signal ksi-signal.json \ -# --vdr vdr-report.json --previous-sdr prev.json +# --runtime-signal ksi-signal-runtime.json --vdr vdr-report.json --previous-sdr prev.json # ============================================================================= import argparse +import hashlib +import importlib.util import json import os +import re +import subprocess import sys from datetime import datetime, timezone from pathlib import Path -# Shared generator helpers. The insert is __file__-relative, so this script stays -# runnable standalone from any working directory (see scripts/_common.py). sys.path.insert(0, os.path.dirname(os.path.abspath(__file__))) -from _common import prop # noqa: E402 import _assessor # noqa: E402 import _controls # noqa: E402 +import _decisions # noqa: E402 +import _fedramp_schema as fs # noqa: E402 +import _freshness # noqa: E402 +import _frr # noqa: E402 +import _offering # noqa: E402 +import _rules # noqa: E402 +import _scheduled_review as _sched # noqa: E402 +import _signers # noqa: E402 +import _training # noqa: E402 + +REPO = Path(__file__).resolve().parent.parent +MODERATE_PROFILE = REPO / "data" / "profiles" / "FedRAMP_rev5_MODERATE-baseline_profile.json" +POLICY_DIR = REPO / "infrastructure" / "policy" +POLICIES = REPO / "docs" / "policies" +SITE = "https://samaydlette.com" +REPO_URL = "https://github.com/sam-aydlette/samaydlette.com/blob/main" +HISTORY_DAYS = 366 # SDR-CSX-KMT: daily metric data up to the past year +SEMVER = re.compile(r"^(\d+)\.(\d+)\.(\d+)$") + +NO_ASSESSMENT = ("No independent assessment: no FedRAMP Recognized assessment service is engaged. " + "The provider-side verification and validation above is what an assessor would examine.") +WORKSTREAMS = { + "W2": "vulnerability report follow-ups", "W3": "certification package in FedRAMP's schemas", + "W4": "quarterly reporting cycle", "W5": "significant change notifications", + "W6": "incident reporting", "W7": "detection and evaluation", "W8": "trust center", + "W9": "FedRAMP Security Inbox", "W10": "scope, cryptography and secure configuration", + "sam": "an act of the operator (registration, assessor, application)", +} +EVIDENCE_WORDS = {"test": "test", "step": "pipeline step", "artifact": "published artifact", + "decision": "decision record"} + + +def _fail(msg): + raise SystemExit(f"::error::SDR: {msg} (fail-closed)") + + +# --- inputs --------------------------------------------------------------------------- + +def moderate_ids(path=MODERATE_PROFILE): + prof = json.loads(Path(path).read_text())["profile"] + return {i for imp in prof["imports"] for inc in imp.get("include-controls", []) for i in inc.get("with-ids", [])} + + +def policy_rules(policy_dir=POLICY_DIR): + """{KSI ID: [{"id", "title", "file"}]} from the OPA rule annotations + (custom.ksi_ids), read with `opa inspect` like check-policy-annotations.""" + out = subprocess.run(["opa", "inspect", "-a", str(policy_dir), "--format", "json"], + capture_output=True, text=True, check=True) + by_ksi = {} + for entry in json.loads(out.stdout).get("annotations", []) or []: + ann = entry.get("annotations") or {} + custom = ann.get("custom") or {} + if ann.get("scope") != "rule" or not custom.get("id"): + continue + f = Path((entry.get("location") or {}).get("file", "?")).name + for k in custom.get("ksi_ids") or []: + by_ksi.setdefault(k, []).append({"id": custom["id"], "title": ann.get("title", ""), "file": f}) + for rules in by_ksi.values(): + rules.sort(key=lambda r: (r["file"], r["id"])) + return by_ksi + + +def runtime_validations(path): + """Validations from the signed runtime signal, only when it verifies and is + fresh (the VDR builder's own loader); otherwise none, with the reason.""" + spec = importlib.util.spec_from_file_location("vdr_builder", REPO / "scripts" / "build-vdr-report.py") + mod = importlib.util.module_from_spec(spec) + spec.loader.exec_module(mod) + rt = mod.load_runtime_signal(path) + if not (rt["verified"] and rt["fresh"]): + return [], rt["reason"] or "runtime signal not usable" + return rt["validations"], None + + +def runtime_bound(path, commit): + """None when the runtime signal re-validated the inventory of `commit` + (provenance.source.commit, copied by the emitter from the inventory it + read); else why not. The deploy stages its own inventory for the emitter, + so a signal from the previously published inventory does not count.""" + try: + got = ((json.loads(Path(path).read_text()).get("provenance") or {}).get("source") or {}).get("commit") + except (OSError, json.JSONDecodeError): + return "the runtime signal is unreadable" + if got != commit: + return f"the runtime signal re-validated commit {str(got)[:12]}, not this build's {commit[:12]}" + return None + + +# --- FRC-CSX-VVK: the automated methods counted per KSI --------------------------------- +# 1. the OPA plan gate (the KSI's measures validated against the plan); +# 2. the runtime re-validation (the signed runtime signal, verified and fresh); +# 3. dependency vulnerability scanning, for a KSI whose components include npm or +# PyPI packages: the VDR built from this inventory's Syft SBOM and Grype scans, +# bound to this inventory, its signature verified, inside its freshness window, +# with every Grype scan passing the detection gate; +# 4 onward. the KSI's own mechanisms, from KSI_METHODS below: for KSI-CED-RAT +# the two training checks of scripts/_training.py (the latest completed packet +# covers what the system's data requires; the current packet was completed by +# its due date with a passing score and a steady trend), and for the KSIs of +# scripts/_scheduled_review.py the scheduled review that verifies them (the +# nightly audit-log review, the Annual Security Review, the monthly recovery +# exercise), each counted only when its published record's signature verifies +# against its publisher and the record is current and passing. Every person +# in them is simulated (DEC-194). +# A KSI with fewer than two is a shortfall unless an in-force `accepted` +# decision record names it (resource "ksi::"). +PACKAGE_TYPES = ("npm_package", "pypi_package") +TRAINING_KSI = "KSI-CED-RAT" + + +def _ksi_method_table(): + table = {TRAINING_KSI: ["training-currency", "training-completion"]} + for key, ksis in _sched.KSI_METHODS.items(): + for kid in ksis: + table.setdefault(kid, []).append(key) + return table + + +# {KSI ID: [method key, ...]}: the mechanisms that count for a KSI beyond the +# plan gate, the runtime re-validation and dependency scanning. +KSI_METHODS = _ksi_method_table() +REQUIRED_METHODS = 2 +VDR_PATH = ".well-known/vdr-report.json" +COSIGN_ISSUER = "https://token.actions.githubusercontent.com" + + +def cosign_verify(path, bundle, identities): + """True when cosign verifies `bundle` over `path` for any of `identities`.""" + for ident in identities: + r = subprocess.run(["cosign", "verify-blob", "--bundle", str(bundle), "--certificate-identity", ident, + "--certificate-oidc-issuer", COSIGN_ISSUER, str(path)], + capture_output=True, text=True, check=False) # nosec B603: fixed argument list + if r.returncode == 0: + return True + return False + + +def vdr_signature(path, bundle, identities, verifier=cosign_verify): + """(verified, reason) for the VDR report's Sigstore bundle.""" + if not bundle or not identities: + return False, "no VDR signature was supplied to check" + if not Path(path).is_file() or not Path(bundle).is_file(): + return False, "the VDR report or its signature is missing" + try: + ok = verifier(path, bundle, identities) + except OSError as exc: + return False, f"the VDR signature could not be checked ({type(exc).__name__})" + return (True, None) if ok else (False, "the VDR signature does not verify against the allowed identities") + + +def _ts(v): + try: + t = datetime.fromisoformat(str(v).replace("Z", "+00:00")) + except ValueError: + return None + return t if t.tzinfo else t.replace(tzinfo=timezone.utc) + + +def dependency_scan(vdr, signal, now, signature, max_age_hours): + """(True, None) when the VDR counts as a dependency-scanning method for this + inventory; else (False, the reason).""" + if not vdr: + return False, "no VDR report in this build" + if not signal.get("signal_id") or vdr.get("ksi_signal_id") != signal.get("signal_id"): + return False, "the VDR report is not bound to this inventory's signal_id" + if not signature[0]: + return False, signature[1] or "the VDR signature is not verified" + emitted = _ts(vdr.get("emitted_at")) + if emitted is None or not 0 <= (now - emitted).total_seconds() <= max_age_hours * 3600: + return False, f"the VDR report is not within its {max_age_hours}-hour window" + feeds = [f for f in ((vdr.get("methodology") or {}).get("detection") or {}).get("feeds") or [] + if f.get("feed") == "grype"] + if not feeds: + return False, "the VDR's detection record lists no Grype dependency scan" + if any(f.get("status") != "ok" for f in feeds): + return False, "a Grype dependency scan failed the detection gate" + return True, None + + +def training_methods(prev, reg, incidents, n_rules, n_ksis, now): + """{"currency": (ok, reason), "completion": (ok, reason), "summary": {...}} + for KSI-CED-RAT, the history carried forward from the previous SDR.""" + previous = (prev.get("providerExtensions") or {}).get("training") if isinstance(prev, dict) else None + cur, comp, summ = _training.evaluate(previous if isinstance(previous, dict) else None, reg, incidents, + n_rules, n_ksis, now) + return {"currency": cur, "completion": comp, "summary": summ} -HISTORY_DAYS = 366 # SDR-CSX-KMT: all daily metric data up to the past year - -NA = "N/A — self-attested proof of concept; no FedRAMP Recognized independent assessment service engaged (IVV is not applicable to an unsponsored system)." - - -def _control_map(irs): - """control_id -> {status, origination} from the control projection.""" - m = {} - for ir in irs: - m[ir["control-id"]] = {"status": prop(ir, "implementation-status"), - "origination": prop(ir, "control-origination")} - return m - - -def build_records(catalog, cmap): - """One SDR-CSO-FRR record per in-scope KSI, derived from its controls' projected state.""" - records = [] - for fam in catalog.get("KSI", {}).values(): - for ind in fam.get("indicators", []) or []: - if ind.get("retired"): - continue - controls = [] - impl = inh = na = 0 - for c in ind.get("controls", []) or []: - cid = c.get("control_id") - st = cmap.get(cid, {}) - controls.append({"control_id": cid, "status": st.get("status"), - "origination": st.get("origination")}) - o = st.get("origination") - if st.get("status") == "not-applicable": - na += 1 - elif o == "inherited" or o == "shared": - inh += 1 - else: - impl += 1 - if controls: - expl = (f"Satisfied through {len(controls)} NIST 800-53 control(s) " - f"({impl} system-implemented, {inh} inherited/shared, {na} not-applicable); " - f"see rev5_controls in this record for each control's implementation statement.") - else: - expl = ("Process/organizational indicator with no direct 800-53 control mapping; " - "satisfied at the operator level and documented in the linked policy.") - records.append({ - "rule_id": ind["id"], - "statement": ind.get("statement", ""), - "controls": controls, - "explanation": expl, - "verification": ("Automated: the deploy-time OPA gate and the per-deploy KSI signal " - "record the implementing controls; the daily runtime emitter " - "re-validates the live configuration against the same compiled policy."), - "validation": ("Effectiveness reviewed continuously by the daily runtime revalidation " - "(drift detector) and annually by the structural security review."), - "independent_verification": NA, - "independent_validation": NA, - "assessor_comment_responses": [], - "artifacts": ["/.well-known/ksi-signal.json", "/.well-known/security-decision-record.json"], - }) - return records - - -# CR26 implementation-status vocabulary (SDR-CSF-CTF) for the projection's -# OSCAL tokens. -REV5_STATUS = {"implemented": "Implemented", "partial": "Partially Implemented", "planned": "Planned", - "alternative": "Alternative Implementation", "not-applicable": "Not Applicable"} - - -def build_rev5_controls(irs, catalog): - """SDR-CSF-CTF: a summary for each applicable Rev5 control: parameter values, - implementation status, the mechanisms (the projection's statement, including - any inheritance), verification, validation, independent verification and - validation, and control-specific artifacts. Verification and validation - point at the records of the KSIs that claim the control rather than - restating them; a control no KSI claims says so.""" - ksis_by_control, _ = _controls.contributing_ksis(catalog) + +INCIDENTS_PATH = Path(__file__).resolve().parent.parent / "data" / "incidents.json" + + +def _ksi_count(catalog): + return sum(len(f["indicators"]) for f in catalog["KSI"].values()) + + +NO_TRAINING = {"currency": (False, "not evaluated in this build"), + "completion": (False, "not evaluated in this build"), "summary": None} +NOT_EVALUATED = (False, "not evaluated in this build") + + +def scheduled_methods(records, now, verifier=cosign_verify): + """{mechanism key: (ok, reason)} for the scheduled reviews' published records. + `records` is {key: (json path, bundle path)}; a record counts only when its + bundle verifies against the workflows that publish it (scripts/_signers.py) + and scripts/_scheduled_review.method_status passes it.""" + out = {} + for key in _sched.KSI_METHODS: + if key not in records: + out[key] = NOT_EVALUATED + continue + path, bundle = records[key] + name = _sched.METHOD_FILES[key] + if not Path(path).is_file() or not Path(bundle).is_file(): + out[key] = (False, f"{name} or its signature is not published") + continue + try: + ok = verifier(path, bundle, [_signers.IDENTITIES[w] for w in _signers.signers(name)]) + except OSError as exc: + out[key] = (False, f"the signature of {name} could not be checked ({type(exc).__name__})") + continue + if not ok: + out[key] = (False, f"the signature of {name} does not verify against its publisher") + continue + try: + doc = json.loads(Path(path).read_text()) + except (OSError, json.JSONDecodeError): + out[key] = (False, f"{name} is unreadable") + continue + out[key] = _sched.method_status(key, doc, now) + return out + + +def _method_lines(key, result): + """The SDR validation line for one KSI mechanism, counted or not.""" + ok, why = result + if key == "training-currency": + return ("Training currency check: the latest completed training packet covers every decision of " + "the last 12 months, every incident and exercise, and the current rule and KSI counts " + "(providerExtensions.training)." if ok else + f"Training currency check not counted for this build: {why}.") + if key == "training-completion": + return ("Training completion and effectiveness check: the current packet was completed by its due " + f"date with a score of at least {_training.PASS}, and the score trend holds; the trainee " + "is simulated (DEC-194)." if ok else + f"Training completion and effectiveness check not counted for this build: {why}.") + title = _sched.METHOD_TITLES[key] + where = f"{SITE}/.well-known/{_sched.METHOD_FILES[key]}" + return (f"{title}; its signed record is current and passing ({where})." if ok else + f"{title.split(' (')[0]} not counted for this build: {why}.") + + +def vvk_acceptances(reg, now): + """{KSI ID: DEC ID} for in-force, unexpired `accepted` records naming a KSI.""" + out = {} + for r in _decisions.in_force(reg) if reg else []: + if r.get("disposition") != "accepted" or str(r.get("review_by", "")) < now.date().isoformat(): + continue + for res in (r.get("applies_to") or {}).get("resources") or []: + if res.startswith("ksi::"): + out[res[len("ksi::"):]] = r["id"] + return out + + +def vvk_shortfalls(doc): + """KSIs with fewer than two automated methods and no accepted decision.""" + return [f"{k['ksiId']}: {k['providerExtensions']['automatedMethods']} automated method(s); FRC-CSX-VVK " + f"requires {REQUIRED_METHODS} and no in-force accepted decision record names it" + for k in doc["keySecurityIndicators"] + if k["providerExtensions"]["automatedMethods"] < REQUIRED_METHODS + and not k["providerExtensions"].get("fewerMethodsAccepted")] + + +# --- FedRAMP rules -------------------------------------------------------------------- + +def _evidence_line(ev): + return f"{EVIDENCE_WORDS[ev['kind']]} `{ev['ref']}`" + + +def evidence_context(freshness_path=None, decisions_path=None): + """What a rule's evidence lines say about cycle and authority: the freshness + entry of each published artifact and the in-force decision records.""" + cfg = _freshness.load_freshness_config(freshness_path) + decs = _decisions.in_force(_decisions.load(decisions_path or REPO / "data" / "decisions.json")) + return {"artifacts": {a["path"]: a for a in cfg["artifacts"]}, "decisions": {d["id"]: d for d in decs}} + + +def _evidence_validation(ev, ctx): + """IVV-CSO-SEI/SEE: what one piece of evidence verifies, and on what cycle.""" + kind, ref = ev["kind"], ev["ref"] + if kind == "test": + return (f"Verified by the test `{ref}`, run on every pull request and before every deploy " + "(the deploy's unit-test job); the deploy does not proceed if it fails.") + if kind == "step": + return (f"Exercised by the workflow step `{ref}` each time that workflow runs; the run fails if the " + "step does.") + if kind == "artifact": + a = (ctx or {}).get("artifacts", {}).get(ref) + cyc = (f", refreshed on its {a['cadence']} cadence and alarmed past {a['max_age_hours']} hours by the " + "evidence watchdog") if a else "" + return f"Shown by the published artifact `{ref}`{' (signed)' if a and a.get('signed') else ''}{cyc}." + d = (ctx or {}).get("decisions", {}).get(ref) + when = f", decided by {d.get('decided_by')} on {d.get('decided_on')}, review by {d.get('review_by')}" if d else "" + return f"Attested by the decision record {ref}{when}: {d.get('title') if d else 'in force'}." + + +def _assessment(rule_id, assessor_by_rule): + entries = assessor_by_rule.get(rule_id) or [] + if not entries: + return [NO_ASSESSMENT] + return [f"Assessor record {e['record_id']} ({e['kind']}): {e['text']}" for e in entries] + + +def build_requirements(records, applicable, assessor_by_rule, evidence_ctx=None): out = [] - for ir in irs: - cid = ir["control-id"] - status = prop(ir, "implementation-status") - origination = prop(ir, "control-origination") - ksis = sorted(ksis_by_control.get(cid, ())) - if status == "not-applicable": - verification = validation = "Not applicable." - elif origination == "inherited": - verification = validation = ("Inherited from AWS under its FedRAMP certification " - "(leveraged authorization); verified and validated there.") - elif ksis: - verification = validation = ("See the rule records (rule_records) of the contributing KSIs: " - + ", ".join(ksis) + ".") - else: - verification = ("No KSI claims this control; the statement is maintained in the control " - "projection (scripts/_controls.py, data/component-definitions/) and " - "reviewed with it.") - validation = "No automated validation." - remarks = [ir["statements"][0]["remarks"]] if ir.get("statements") else [] - live = prop(ir, "implementation-status-remarks") + for r in records["records"]: + rid, status = r["frr_id"], r["status"] + impl = [r["implementation"]] + if status == "Not Applicable": + impl.append(f"Not applicable: {r['not_applicable']}") + if r.get("may_rationale"): + impl.append(f"Use of this permission: {r['may_rationale']}") + val = [] + if r.get("evidence"): + val.append("Evidence: " + "; ".join(_evidence_line(e) for e in r["evidence"]) + ".") + val += [_evidence_validation(e, evidence_ctx) for e in r["evidence"]] + if r.get("simulated"): + val.append(f"Simulated counterparty ({r['simulated']['counterparty']}): {r['simulated']['how']}") + val.append("Checked on every build by scripts/_frr.py: the rule set matches the pinned FedRAMP " + "rules and every piece of evidence cited resolves.") + if r.get("gap"): + val.append(f"Gap: {r['gap']}") + val.append("Closes with: " + "; ".join(f"{c} ({WORKSTREAMS[c]})" for c in r["closes_with"]) + ".") + rec = {"frrID": rid} + if status != "Not Applicable": + rec["frrImplementationStatus"] = status + rec["frrImplementation"] = impl + rec["frrValidation"] = val + rec["frrAssessment"] = _assessment(rid, assessor_by_rule) + rec["providerExtensions"] = {"status": status, "force": applicable[rid]["force"], + "evidence": r.get("evidence", []), + "closesWith": r.get("closes_with", [])} + if r.get("simulated"): + rec["providerExtensions"]["simulated"] = r["simulated"] + out.append(rec) + return out + + +# --- KSIs ----------------------------------------------------------------------------- + +def ksi_status(k): + """Implemented only when the KSI passes and its measures are checked + automatically against the plan; a pass by inventory or document alone is + partial.""" + if k.get("status") != "pass": + return "Not Implemented" + if k.get("method") == "policy-validation" and (k.get("evidence") or {}).get("validation_ids"): + return "Implemented" + return "Partially Implemented" + + +def _names(items, n=6): + items = sorted(items) + return ", ".join(f"`{i}`" for i in items[:n]) + (f" and {len(items) - n} more" if len(items) > n else "") + + +def ksi_text(kid, cat, k, rules, comps, rt, runtime_reason, nval, nfail, plan_ok): + """SDR-CSX-KSI, written for this KSI from its own measures, components and + results: (implementation lines, validation lines) covering the measures and + their objective (or the reason there are none, and the risk), their cycle, + verification that they demonstrate the KSI and that the automation is + accurate, and validation that they are in place and working.""" + stmt = cat["statement"] + impl = [stmt] + if rules: + impl.append(f"Measures ({len(rules)}), each an OPA rule annotated with {kid}: " + + "; ".join(f"{r['title']} (`{r['file']}#{r['id']}`)" for r in rules) + + f". Objective: together they show that {stmt[0].lower() + stmt[1:]}") + impl.append(f"Cycle: on every deploy, before apply, against the Terraform plan for {len(comps)} " + f"component(s) ({_names(comps)})" + + (f"; and daily at runtime against the live configuration of {len(rt)} of them." if rt else ".")) + else: + impl.append(f"No automated measure is annotated with {kid} in this build. Evidence is " + f"{k.get('method')}" + (f" over {len(comps)} inventory component(s) ({_names(comps)})" if comps + else "") + ". Reason: no policy rule checks this KSI yet. Risk to " + "customers: a regression against the KSI would not stop a deploy and would surface only " + "when the inventory or the documentation is reviewed.") + impl.append("Cycle: the inventory behind it is re-derived from live state on every deploy; there is no " + "persistent check.") + val = [] + if rules: + files = sorted({r["file"] for r in rules}) + val.append(f"Verification that the measures demonstrate {kid}: each rule carries {kid} in its " + "custom.ksi_ids annotation, and scripts/check-policy-annotations.py fails CI when an " + "annotation and the KSI catalog disagree. Verification that the automation is accurate: " + f"the rules' own tests ({', '.join(f'infrastructure/policy/{f[:-5]}_test.rego' for f in files)}) " + "run with a coverage floor on every pull request, and the parity test checks that the CLI and " + "the compiled Wasm the runtime uses decide alike.") + if plan_ok: + val.append(f"Validation on this deploy: {nval} validation(s) of these measures against the plan, " + f"{nfail} failing; the deploy stops on a violation.") + if rt: + val.append(f"Re-validated daily at runtime: the signed runtime signal re-evaluates the same compiled " + f"policy against live configuration for {len(rt)} of these components.") + elif runtime_reason: + val.append(f"Runtime re-validation not counted for this build: {runtime_reason}.") + if not rules: + val.append(f"Verification: none automated for {kid}; the inventory attestation is checked only for " + "completeness by the reconciliation gate. The reason for having no measure is not accepted: no " + "decision record accepts it, so the KSI is reported at the status its evidence supports.") + val.append("Validation: there is no measure to validate as in place and working; the reason (no policy rule " + "yet) is valid for this build and is removed by annotating a rule with the KSI.") + return impl, val + + +def build_ksis(catalog, signal, rules_by_ksi, runtime, runtime_reason, assessor_by_rule, + dep_scan=(False, "not evaluated in this build"), training=None, accepted=None, scheduled=None): + statements = {i["id"]: i for f in catalog["KSI"].values() for i in f["indicators"]} + sig = {k["id"]: k for k in signal.get("ksis", [])} + missing = sorted(set(statements) - set(sig)) + if missing: + _fail(f"the KSI signal carries no result for {', '.join(missing)}") + emitted = (signal.get("emitted_at") or "")[:10] or None + types = {c.get("component_id"): c.get("type") for c in signal.get("components", [])} + accepted = accepted or {} + out, status = [], {} + for kid in sorted(statements): + k, cat = sig[kid], statements[kid] + st = ksi_status(k) + status[kid] = st + ev = k.get("evidence") or {} + comps = set(ev.get("component_refs") or []) + rt = [v for v in runtime if comps & set(v.get("component_refs") or [])] + plan_ok = bool(ev.get("validation_ids")) + pkgs = sorted(c for c in comps if types.get(c) in PACKAGE_TYPES) + dep_ok = bool(pkgs) and dep_scan[0] + training = training or NO_TRAINING + results = {"training-currency": training["currency"], "training-completion": training["completion"], + **{key: (scheduled or {}).get(key, NOT_EVALUATED) for key in _sched.KSI_METHODS}} + own = [(m, results[m]) for m in KSI_METHODS.get(kid, [])] + methods = int(plan_ok) + int(bool(rt)) + int(dep_ok) + sum(int(r[0]) for _, r in own) + rules = rules_by_ksi.get(kid, []) + nval, nfail = len(ev.get("validation_ids") or []), len(ev.get("failed_validation_ids") or []) + impl, val = ksi_text(kid, cat, k, rules, comps, rt, runtime_reason, nval, nfail, plan_ok) + if pkgs and dep_ok: + val.append(f"Dependency vulnerability scanning of its {len(pkgs)} npm and PyPI package component(s): " + "the VDR report built from this inventory's Syft SBOM and Grype scans, bound to this " + "inventory, signature verified, inside its freshness window, every Grype scan passing the " + f"detection gate ({SITE}/.well-known/vdr-report.json).") + elif pkgs: + val.append(f"Dependency vulnerability scanning not counted for this build: {dep_scan[1]}.") + for m, r in own: + val.append(_method_lines(m, r)) + val.append(f"Automated methods in place: {methods} (FRC-CSX-VVK requires {REQUIRED_METHODS} for Class C).") + if methods < REQUIRED_METHODS and kid in accepted: + val.append(f"Fewer than {REQUIRED_METHODS} automated methods is an accepted finding: {accepted[kid]}.") + if st != "Implemented": + val.append("Status is not Implemented because " + + ("the KSI does not pass." if st == "Not Implemented" else + f"its evidence is {k.get('method')}, not an automated check of its measures.")) + evidence = [{"evidenceType": "Report", + "evidenceDescription": "Deploy-time KSI signal: inventory, validations and per-KSI results, " + "signed with cosign by the deploy workflow.", + "evidenceLocation": f"{SITE}/.well-known/ksi-signal.json", + **({"lastUpdated": emitted} if emitted else {})}] + if rt: + evidence.append({"evidenceType": "Report", + "evidenceDescription": "Runtime KSI signal: daily re-validation of live configuration, " + "signed with the runtime KMS key.", + "evidenceLocation": f"{SITE}/.well-known/ksi-signal-runtime.json"}) out.append({ - "control_id": cid, - "implementation_status": REV5_STATUS.get(status, status), - "origination": origination, - "parameters": [{"param_id": sp["param-id"], "values": sp.get("values", [])} - for sp in ir.get("set-parameters", [])], - "mechanisms": " ".join(remarks + ([live] if live else [])), - "contributing_ksis": ksis, - "verification": verification, - "validation": validation, - "independent_verification": NA, - "independent_validation": NA, - "assessor_comment_responses": [], - "artifacts": [lk["href"] for lk in ir.get("links", [])], + "ksiId": kid, + "ksiImplementationStatus": st, + "ksiImplementation": impl, + "ksiValidation": val, + "ksiAssessment": _assessment(kid, assessor_by_rule), + "ksiTests": [f"infrastructure/policy/{r['file']}#{r['id']}" for r in rules], + "ksiEvidence": evidence, + "providerExtensions": {"method": k.get("method"), "automatedMethods": methods, + **({"fewerMethodsAccepted": accepted[kid]} + if methods < REQUIRED_METHODS and kid in accepted else {}), + "packageComponents": len(pkgs), + "controls": [c["control_id"] for c in cat["controls"]], + "measures": [f"{r['file']}#{r['id']}" for r in rules], + "components": len(comps), "validations": nval, "failingValidations": nfail, + "runtimeComponents": len(rt)}, }) + return out, status + + +# --- controls ------------------------------------------------------------------------- + +def nist_id(cid): + """ac-2.1 -> AC-2(1).""" + base, _, enh = cid.partition(".") + return base.upper() + (f"({enh})" if enh else "") + + +def control_basis(ir, ksis_for, ksi_st, frrs_for, frr_st, policies): + """(status, or None when not applicable; the basis sentence).""" + cid = ir["control-id"] + st = _controls.prop(ir, "implementation-status") + orig = _controls.prop(ir, "control-origination") + if st == "not-applicable": + return None, "Not applicable." + if st == "partial": + return "Partially Implemented", "A contributing KSI is failing." + checked = sorted(k for k in ksis_for.get(cid, ()) if ksi_st.get(k) == "Implemented") + rules = sorted(r for r in frrs_for.get(cid, ()) if frr_st.get(r) == "Implemented") + fam = cid.split("-")[0] + if orig == "inherited": + return "Implemented", "Inherited from AWS under its FedRAMP authorization." + if checked: + return "Implemented", "Backed by automatically checked KSI(s): " + ", ".join(checked) + "." + if rules: + return "Implemented", "Backed by implemented FedRAMP rule(s): " + ", ".join(rules) + "." + if re.fullmatch(r"[a-z]{2}-1", cid) and fam in policies: + return "Implemented", f"Policy and procedures, published: {policies[fam]}" + return "Partially Implemented", ("The mechanism is described, but no automated check, implemented " + "FedRAMP rule or published policy shows it yet.") + + +def _find_rule(rules, rid): + for fam in rules["FRR"].values(): + for groups in fam["data"].values(): + for members in groups.values(): + if rid in members: + return members[rid] + _fail(f"{rid} is not in the pinned rules") + + +def _sort_key(cid): + fam, _, rest = cid.partition("-") + num, _, enh = rest.partition(".") + return (fam, int(num), int(enh or 0)) + + +def build_controls(irs, catalog, ksi_st, applicable, records, moderate, policies): + ksis_for, _ = _controls.contributing_ksis(catalog) + frr_st = {r["frr_id"]: r["status"] for r in records["records"]} + rules, _ = _rules.load_rules() + frrs_for = {} + for rid in applicable: + for c in _find_rule(rules, rid).get("controls", []) or []: + frrs_for.setdefault(str(c).lower(), set()).add(rid) + missing = sorted(moderate - {ir["control-id"] for ir in irs}) + if missing: + _fail(f"{len(missing)} Moderate control(s) have no implementation record: {', '.join(missing[:10])}") + out = [] + for ir in sorted(irs, key=lambda i: _sort_key(i["control-id"])): + cid = ir["control-id"] + status, basis = control_basis(ir, ksis_for, ksi_st, frrs_for, frr_st, policies) + statement = ir["statements"][0]["remarks"] if ir.get("statements") else "" + orig = _controls.prop(ir, "control-origination") + ks = sorted(ksis_for.get(cid, ())) + fr = sorted(frrs_for.get(cid, ())) + desc = [f"**Not applicable.** {statement}"] if status is None else [f"**Basis:** {basis}", statement] + desc.append(f"**Origination:** {orig}.") + desc.append("**20x coverage:** " + (", ".join(ks) if ks else "no KSI maps this control") + + ("; FedRAMP rules: " + ", ".join(fr) if fr else "") + ".") + if cid not in moderate: + desc.append("Beyond the FedRAMP Moderate baseline; included because a FedRAMP KSI maps it.") + rec = {"controlId": nist_id(cid)} + params = [{"parameterId": sp["param-id"], "parameterValue": ", ".join(sp["values"])} + for sp in ir.get("set-parameters", []) if sp.get("values")] + if params: + rec["parameterValues"] = params + if status: + rec["controlImplementationStatus"] = status + rec["controlImplementationDescription"] = "\n\n".join(d for d in desc if d) + rec["providerExtensions"] = {"basis": basis, "origination": orig, "ksis": ks, "fedrampRules": fr, + "inModerateBaseline": cid in moderate, + "status": status or "Not Applicable"} + out.append(rec) return out -def build_metrics(records, controls_in_scope, vdr, signal, history, now): - """SDR-CSX-KMT: metric snapshot + appended daily history (toward one year).""" +def policy_documents(policy_dir=POLICIES): + """{control family: URL of its published policy} for families with one.""" + return {p.stem.removesuffix("-policy"): f"{REPO_URL}/docs/policies/{p.name}" + for p in sorted(Path(policy_dir).glob("??-policy.md"))} + + +# --- metrics, version ----------------------------------------------------------------- + +KSI_CODES = {"Implemented": "I", "Partially Implemented": "P", "Not Implemented": "N"} + + +def ksi_point(ksis): + """Today's per-KSI metric data (SDR-CSX-KMT): status code (I/P/N), deploy-time + validations and failures, automated methods, and whether the runtime signal + re-validated it (the status of persistent validation).""" + return {k["ksiId"]: {"s": KSI_CODES.get(k["ksiImplementationStatus"], "N"), + "v": k["providerExtensions"]["validations"], + "f": k["providerExtensions"]["failingValidations"], + "m": k["providerExtensions"]["automatedMethods"], + "r": int(k["providerExtensions"]["runtimeComponents"] > 0)} for k in ksis} + + +def ksi_summaries(history): + """Per KSI: a summary of each metric over the past 30 days and up to the + past year, from the days that carry per-KSI data.""" + def summ(window, kid): + pts = [h["ksis"][kid] for h in window if isinstance(h.get("ksis"), dict) and kid in h["ksis"]] + if not pts: + return {"days": 0} + return {"days": len(pts), "daysImplemented": sum(p["s"] == "I" for p in pts), + "daysNotImplemented": sum(p["s"] == "N" for p in pts), + "maxFailingValidations": max(p["f"] for p in pts), + "minAutomatedMethods": min(p["m"] for p in pts), + "daysRuntimeValidated": sum(p["r"] for p in pts), + "current": KSI_NAMES[pts[-1]["s"]]} + kids = sorted({kid for h in history if isinstance(h.get("ksis"), dict) for kid in h["ksis"]}) + return {kid: {"summary_30d": summ(history[-30:], kid), "summary_1y": summ(history, kid)} for kid in kids} + + +KSI_NAMES = {v: k for k, v in KSI_CODES.items()} + + +def build_metrics(counts, vdr, signal, history, now, ksis_today=None): + """SDR-CSX-KMT: today's point and daily history toward one year, with + per-KSI data and summaries.""" sig_vals = signal.get("validations", []) if signal else [] - failing = sum(1 for v in sig_vals if v.get("result") == "fail") vsum = (vdr or {}).get("summary", {}) today = now.date().isoformat() - point = { - "date": today, - "ksi_in_scope": len(records), - "controls_in_scope": controls_in_scope, - "signal_validations": len(sig_vals), - "signal_failing": failing, - "vdr_total": vsum.get("total_findings", 0), - "vdr_blocking": vsum.get("blocking", 0), - "vdr_accepted": vsum.get("risk_accepted", 0), - "vdr_kev": vsum.get("kev", 0), - } - history = [h for h in history if h.get("date") != today] - history.append(point) + point = {"date": today, **counts, + "signal_validations": len(sig_vals), + "signal_failing": sum(1 for v in sig_vals if v.get("result") == "fail"), + "vdr_total": vsum.get("total_findings", 0), "vdr_blocking": vsum.get("blocking", 0), + "vdr_accepted": vsum.get("risk_accepted", 0), "vdr_kev": vsum.get("kev", 0)} + if ksis_today is not None: + point["ksis"] = ksis_today + history = [h for h in history if h.get("date") != today] + [point] history = sorted(history, key=lambda h: h.get("date", ""))[-HISTORY_DAYS:] - last30 = history[-30:] - def _summ(window): - if not window: - return {} + def summ(window): return {"days": len(window), "max_blocking": max(h.get("vdr_blocking", 0) for h in window), "max_failing_validations": max(h.get("signal_failing", 0) for h in window), "current_accepted": window[-1].get("vdr_accepted", 0)} + return {"current": point, "summary_30d": summ(history[-30:]), "summary_1y": summ(history), + "ksi_summaries": ksi_summaries(history), + "daily_metric_keys": {"ksis": "per KSI: s status (I Implemented, P Partially, N Not), v deploy-time " + "validations, f failing, m automated methods, r runtime re-validated " + "(1/0)"}, + "daily_metric_data": history} + + +def previous_history(prev): + pe = prev.get("providerExtensions") or {} + hist = (pe.get("metrics") or {}).get("daily_metric_data") + if hist is None: # the record before the schema reshape kept it at the top level + hist = (prev.get("metrics") or {}).get("daily_metric_data") + return [h for h in hist or [] if isinstance(h, dict)] + + +def content_hash(doc): + """What the version tracks: everything but the metadata, the daily + metrics and the hash itself.""" + body = {k: v for k, v in doc.items() if k not in ("metadata", "providerExtensions")} + pe = {k: v for k, v in (doc.get("providerExtensions") or {}).items() if k not in ("metrics", "contentSha256")} + raw = json.dumps({"body": body, "pe": pe}, sort_keys=True, separators=(",", ":")).encode() + return hashlib.sha256(raw).hexdigest() + +def next_version(prev, digest): + """Semver: unchanged content keeps the previous version; changed content + bumps the patch; a previous record without a semver starts at 1.0.0.""" + v = (prev.get("metadata") or {}).get("version", "") + m = SEMVER.match(v or "") + if not m: + return "1.0.0" + if (prev.get("providerExtensions") or {}).get("contentSha256") == digest: + return v + return f"{m.group(1)}.{m.group(2)}.{int(m.group(3)) + 1}" + + +# --- build ---------------------------------------------------------------------------- + +def _tally(items, key): + out = {} + for it in items: + s = it["providerExtensions"][key] + out[s] = out.get(s, 0) + 1 + return dict(sorted(out.items())) + + +def simulated_summary(reqs): + """How many rule records rely on a simulated outside party, and which.""" + by = {} + for r in reqs: + sim = r["providerExtensions"].get("simulated") + if sim: + by[sim["counterparty"]] = by.get(sim["counterparty"], 0) + 1 + return {"records": sum(by.values()), "of": len(reqs), "byCounterparty": dict(sorted(by.items())), + "statement": f"{sum(by.values())} of {len(reqs)} rule records rely on a simulated counterparty " + "(an assessor, FedRAMP, an agency, an incident recipient, personnel, the mail system or " + "SAM.gov): " + "the mechanism is real and runs on every deploy; only the outside party is simulated."} + + +def assessment_coverage(subject): + """What the assessor results carried here covered (IVV-CSO-FIA, SDR-CSO-FRR), + from the set's subject after scripts/_assessor.py checked it against the + commit and signal the deploy stated.""" return { - "current": point, - "summary_30d": _summ(last30), - "summary_1y": _summ(history), - "daily_metric_data": history, # all daily points up to a year (SDR-CSX-KMT) - "note": ("Daily metric history accumulates one point per deploy/day; the full " - "one-year window builds over time from the first published SDR."), + "phase": subject.get("phase"), + "commit": subject["commit"], + "signalId": subject["signal_id"], + "signalCommit": subject.get("signal_commit"), + "statement": ( + f"The assessor results in this record come from the pre-deploy assessment. It verified the repository " + f"at commit {subject['commit']} (the commit this record was built from) and validated the published " + f"state that commit replaces: KSI signal {subject['signal_id']} (commit " + f"{subject.get('signal_commit') or 'unknown'}). It is a gate: the deploy did not proceed until it " + f"passed. After publishing, the same assessor assesses the just-published state of this commit; a " + f"failure there fails the deploy run and raises the deployment-failure issue."), } -def main(): +def build(catalog, signal, records, applicable, irs, moderate, rules_by_ksi, runtime, runtime_reason, + assessor_records, prof, prev, vdr, now, policies, evidence_ctx=None, fedramp_id=None, + dep_scan=(False, "not evaluated in this build"), training=None, accepted=None, coverage=None, + scheduled=None): + ids = [r["frr_id"] for r in records["records"]] + sorted( + i["id"] for f in catalog["KSI"].values() for i in f["indicators"]) + pseudo = [{"rule_id": i, "assessor_comment_responses": []} for i in ids] + block = _assessor.attach(pseudo, assessor_records) + by_rule = {p["rule_id"]: p["assessor_comment_responses"] for p in pseudo if p["assessor_comment_responses"]} + + reqs = build_requirements(records, applicable, by_rule, evidence_ctx) + ksis, ksi_st = build_ksis(catalog, signal, rules_by_ksi, runtime, runtime_reason, by_rule, + dep_scan, training, accepted, scheduled) + controls = build_controls(irs, catalog, ksi_st, applicable, records, moderate, policies) + in_mod = [c for c in controls if c["providerExtensions"]["inModerateBaseline"]] + beyond = [c for c in controls if not c["providerExtensions"]["inModerateBaseline"]] + ksi_counts = {} + for s in ksi_st.values(): + ksi_counts[s] = ksi_counts.get(s, 0) + 1 + counts = {"rules": len(reqs), "ksis": len(ksis), "controls_moderate": len(in_mod), + "controls_beyond_moderate": len(beyond)} + doc = { + "$schema": fs.stamp("sdr"), + "certificationPackageOverviewUri": fs.CPO_URI, + "metadata": {}, + "fedRampRequirements": reqs, + "keySecurityIndicators": ksis, + "securityControls": controls, + "providerExtensions": { + "fedRampId": fedramp_id or _offering.fedramp_id(), + # Sought, never held (scripts/_offering.py, the CPO's same field). + "certification": _offering.certification(), + "class": prof.get("fedramp_class"), + "impact_level": prof.get("impact_level"), + "ksi_signal_id": signal.get("signal_id"), + "rules": _rules.pin(), + "summary": {"fedRampRequirements": _tally(reqs, "status"), + "simulatedCounterparties": simulated_summary(reqs), + "keySecurityIndicators": dict(sorted(ksi_counts.items())), + "securityControlsModerate": _tally(in_mod, "status"), + "securityControlsBeyondModerate": _tally(beyond, "status")}, + "assessorRecords": block, + "assessorCommentResponses": by_rule, + **({"assessmentCoverage": coverage} if coverage else {}), + **({"training": training["summary"]} if training and training.get("summary") else {}), + "metrics": build_metrics(counts, vdr, signal, previous_history(prev), now, ksi_point(ksis)), + }, + } + digest = content_hash(doc) + doc["providerExtensions"]["contentSha256"] = digest + doc["metadata"] = {"version": next_version(prev, digest), "lastUpdated": now.isoformat(), + "updateSource": "Automated: scripts/build-sdr.py in the deploy workflow, from " + "data/frr-records.json, the KSI signal and the control projection"} + return doc + + +def _scheduled_args(values): + out = {} + for v in values: + key, _, path = v.partition("=") + if key not in _sched.KSI_METHODS or not path.endswith(".json"): + _fail(f"--scheduled-record {v!r}: expected KEY=.json with KEY one of " + f"{', '.join(sorted(_sched.KSI_METHODS))}") + out[key] = (path, path[:-5] + ".bundle") + return out + + +def main(argv=None): ap = argparse.ArgumentParser() ap.add_argument("--catalog", default="schemas/ksi-catalog.json") ap.add_argument("--ksi-signal", default="ksi-signal.json") + ap.add_argument("--runtime-signal", default="ksi-signal-runtime.json") ap.add_argument("--vdr", default="vdr-report.json") ap.add_argument("--profile", default="../data/system-profile.json") + ap.add_argument("--frr-records", default=str(_frr.DEFAULT_PATH)) ap.add_argument("--previous-sdr", default=None) ap.add_argument("--output", default="security-decision-record.json") ap.add_argument("--md-output", default="security-decision-record.md") - ap.add_argument("--assessor-records", default=str(_assessor.RECORDS_DIR), - help="directory of signed assessor records (REQ-ASR-1); empty = no assessor record") - ap.add_argument("--assessor-identity", default=str(_assessor.IDENTITY_PATH), - help="pinned assessor identity the records must verify against") - a = ap.parse_args() + ap.add_argument("--assessor-records", default=str(_assessor.RECORDS_DIR)) + ap.add_argument("--assessor-identity", default=str(_assessor.IDENTITY_PATH)) + # A keyless-signed assessment set (the simulated assessor's, on every deploy): + # given, it is required to exist and verify; its records replace the loose ones. + ap.add_argument("--assessment", default=None) + ap.add_argument("--assessment-bundle", default=None) + # The state the set must cover (required with --assessment): the commit + # being deployed and the published KSI signal the assessor validated. A set + # covering anything else is refused, and the SDR states these. + ap.add_argument("--assessment-commit", default=None) + ap.add_argument("--assessment-signal-id", default=None) + # FRC-CSX-VVK: the VDR's Sigstore bundle and the identities allowed to sign + # it (dependency scanning counts only when it verifies), the decision + # register (taught in the training packet; accepted shortfalls), the incident + # register (taught in the training packet), and whether + # a KSI short of two methods without an accepted decision fails the build. + ap.add_argument("--vdr-bundle", default=None) + ap.add_argument("--vdr-identity", action="append", default=[]) + ap.add_argument("--decisions", default=None) + ap.add_argument("--incidents", default=str(INCIDENTS_PATH)) + ap.add_argument("--freshness", default=None) + ap.add_argument("--require-two-methods", action="store_true") + # The scheduled reviews' published records (scripts/_scheduled_review.py), + # each KEY=JSON with its Sigstore bundle beside it (.bundle); each + # counts for its KSIs only when the bundle verifies and the record is current. + ap.add_argument("--scheduled-record", action="append", default=[], metavar="KEY=JSON") + # The commit whose inventory the runtime signal must have re-validated (the + # deploy's staged emitter run); runtime validations of any other count for nothing. + ap.add_argument("--runtime-commit", default=None) + a = ap.parse_args(argv) now = datetime.now(timezone.utc) catalog = json.loads(Path(a.catalog).read_text()) - signal = json.loads(Path(a.ksi_signal).read_text()) if Path(a.ksi_signal).exists() else {} + if not Path(a.ksi_signal).exists(): + _fail(f"{a.ksi_signal} not found") + signal = json.loads(Path(a.ksi_signal).read_text()) vdr = json.loads(Path(a.vdr).read_text()) if Path(a.vdr).exists() else {} prof = json.loads(Path(a.profile).read_text()) if Path(a.profile).exists() else {} - history = [] + prev = {} if a.previous_sdr and Path(a.previous_sdr).exists(): try: - history = json.loads(Path(a.previous_sdr).read_text()).get("metrics", {}).get("daily_metric_data", []) or [] - except Exception: - history = [] - - # The projection needs the inventory: without it there is no control state - # to record, so a missing signal stops the build (fail-closed). + prev = json.loads(Path(a.previous_sdr).read_text()) + except json.JSONDecodeError: + prev = {} + records = _frr.load(a.frr_records) + applicable = _rules.applicable_provider_rules() irs = _controls.load(a.ksi_signal, a.catalog) - cmap = _control_map(irs) - records = build_records(catalog, cmap) - # REQ-ASR-1: assessor records enter only through the signed port; any record - # that does not verify fails the build. They are carried verbatim. - assessor_records = _assessor.load_records(a.assessor_records, a.assessor_identity) - assessor_block = _assessor.attach(records, assessor_records) - metrics = build_metrics(records, len(cmap), vdr, signal, history, now) - - sdr = { - "record_type": "security-decision-record", - "schema": "fedramp-security-decision-record-schema-2026-06-24.json", - "note": "The CR26 replacement for the System Security Plan: per-KSI records (20x) and " - "per-Rev5-control records (rev5_controls), both from one control projection.", - # SDR-CSO-MTD - "metadata": { - "version": "live (regenerated each deploy)", - "last_updated": now.isoformat(), - "source_of_update": "scripts/build-sdr.py, derived from the canonical KSI inventory and the control projection", - }, - "class": prof.get("fedramp_class"), - "impact_level": prof.get("impact_level"), - "ksi_signal_id": (signal or {}).get("signal_id"), - "rule_records": records, # SDR-CSO-FRR + SDR-CSX-KSI - "rev5_controls": build_rev5_controls(irs, catalog), # SDR-CSF-CTF - "metrics": metrics, # SDR-CSX-KMT - # REQ-ASR-1: verified, signed assessor records not tied to one rule, and - # the status ("no assessor record" when none exist). - "assessor_records": assessor_block, - } - _assessor.verify_output(sdr, assessor_records) # T74: output text == signed text - Path(a.output).write_text(json.dumps(sdr, indent=2) + "\n") + runtime, reason = runtime_validations(a.runtime_signal) + if a.runtime_commit and runtime: + reason = runtime_bound(a.runtime_signal, a.runtime_commit) + runtime = [] if reason else runtime + coverage = None + if a.assessment: + assessor_records, subject = _assessor.load_assessment_with_subject( + a.assessment, a.assessment_bundle, a.assessor_identity, + expect_commit=a.assessment_commit, expect_signal_id=a.assessment_signal_id) + coverage = assessment_coverage(subject) + else: + assessor_records = _assessor.load_records(a.assessor_records, a.assessor_identity) + reg = _decisions.load(a.decisions) + window = _freshness.load_freshness_config(a.freshness)["windows"][VDR_PATH] + dep_scan = dependency_scan(vdr, signal, now, vdr_signature(a.vdr, a.vdr_bundle, a.vdr_identity), window) + doc = build(catalog, signal, records, applicable, irs, moderate_ids(), policy_rules(), runtime, reason, + assessor_records, prof, prev, vdr, now, policy_documents(), evidence_context(), + dep_scan=dep_scan, accepted=vvk_acceptances(reg, now), + training=training_methods(prev, reg, json.loads(Path(a.incidents).read_text()), + len(records["records"]), _ksi_count(catalog), now), + coverage=coverage, scheduled=scheduled_methods(_scheduled_args(a.scheduled_record), now)) + _assessor.verify_output(doc, assessor_records) # T74 + short = vvk_shortfalls(doc) + for msg in short: + print(f"::{'error' if a.require_two_methods else 'warning'}::FRC-CSX-VVK: {msg}", file=sys.stderr) + if short and a.require_two_methods: + _fail(f"{len(short)} KSI(s) short of {REQUIRED_METHODS} automated methods; nothing written" + + (f" (runtime re-validation not counted: {reason})" if reason else "")) + fs.write_validated(doc, "sdr", a.output) if a.md_output: - Path(a.md_output).write_text(render_markdown(sdr) + "\n") - print(f"security-decision-record: {len(records)} per-KSI rule records; " - f"{metrics['current']['controls_in_scope']} controls in scope; " - f"{len(metrics['daily_metric_data'])} day(s) of metric history") + Path(a.md_output).write_text(render_markdown(doc) + "\n") + s = doc["providerExtensions"]["summary"] + print(f"security-decision-record {doc['metadata']['version']}: rules {s['fedRampRequirements']}; " + f"KSIs {s['keySecurityIndicators']}; Moderate controls {s['securityControlsModerate']}") return 0 -def _assessor_lines(sdr): - block = sdr.get("assessor_records") or {"status": _assessor.NO_RECORD, "records": []} - entries = list(block.get("records", [])) - for r in sdr["rule_records"]: - entries += [dict(e, rule_id=r["rule_id"]) for e in r.get("assessor_comment_responses", [])] +# --- human-readable view (CDS-CSO-CBF: same data as the JSON) ------------------------- + +def _cell(text): + return str(text).replace("|", "\\|").replace("\n", " ") + + +def _assessor_lines(doc): + pe = doc["providerExtensions"] + entries = list(pe["assessorRecords"].get("records", [])) + for rid, es in pe.get("assessorCommentResponses", {}).items(): + entries += [dict(e, rule_id=rid) for e in es] if not entries: return ["**Assessor records:** No assessor record. Nothing on this page was written " "or signed by an assessor."] - out = [f"**Assessor records:** {block['status']}. Each is quoted verbatim from the " + out = [f"**Assessor records:** {pe['assessorRecords']['status']}. Each is quoted verbatim from the " "assessor's signed record; the signature is in the JSON."] + if pe.get("assessmentCoverage"): + out += ["", f"**What the assessment covered:** {pe['assessmentCoverage']['statement']}", ""] for e in sorted(entries, key=lambda e: e["record_id"]): rule = f" (`{e['rule_id']}`)" if e.get("rule_id") else "" out.append(f"- `{e['record_id']}`{rule}, {e['kind']}, {e['assessor']['organization']}, " @@ -275,42 +957,52 @@ def _assessor_lines(sdr): return out -def render_markdown(sdr): - m = sdr["metadata"] - cur = sdr["metrics"]["current"] +def _summary_line(d): + return ", ".join(f"{k} {v}" for k, v in d.items()) or "none" + + +def render_markdown(doc): + m, pe = doc["metadata"], doc["providerExtensions"] + s = pe["summary"] out = ["# Security Decision Record", "", - f"_{sdr['note']}_", "", - f"- **Class:** {sdr['class']} | **Impact:** {sdr['impact_level']}", - f"- **Version:** {m['version']} | **Last updated:** {m['last_updated']}", - f"- **Source:** {m['source_of_update']}", - f"- **Bound to inventory signal:** `{sdr['ksi_signal_id']}`", - "", - "## Metrics (SDR-CSX-KMT)", "", - f"- KSIs in scope: **{cur['ksi_in_scope']}** | Controls in scope: **{cur['controls_in_scope']}**", - f"- Signal validations: {cur['signal_validations']} ({cur['signal_failing']} failing)", - f"- Vulnerabilities: {cur['vdr_total']} total, {cur['vdr_blocking']} blocking, " - f"{cur['vdr_accepted']} accepted, {cur['vdr_kev']} KEV", - f"- Daily metric history: {len(sdr['metrics']['daily_metric_data'])} day(s) on record " - "(builds toward one year)", - "", - "## Per-rule records (SDR-CSO-FRR / SDR-CSX-KSI)", "", - "Independent verification and validation are N/A for this self-attested system " - "(no FedRAMP Recognized assessor). Verification and validation below are the " - "provider-side evidence an assessor would consume.", "", - *_assessor_lines(sdr), "", - "| KSI | Controls | Explanation |", "|---|---|---|"] - for r in sdr["rule_records"]: - cids = ", ".join(c["control_id"] for c in r["controls"]) or "—" - out.append("| `{rid}` | {cids} | {ex} |".format( - rid=r["rule_id"], cids=cids, ex=r["explanation"].replace("|", "\\|"))) - rc = sdr.get("rev5_controls", []) - by_status = {} - for c in rc: - by_status[c["implementation_status"]] = by_status.get(c["implementation_status"], 0) + 1 - out += ["", "## Rev5 controls (SDR-CSF-CTF)", "", - f"{len(rc)} controls, each with its parameter values, implementation status, mechanisms, " - "verification and validation in `rev5_controls` of the JSON record. By status: " - + (", ".join(f"{k} {v}" for k, v in sorted(by_status.items())) or "none") + "."] + f"_{pe['certification']['program']} (sought; status: {pe['certification']['status']}). Every " + "applicable FedRAMP rule, every Key Security Indicator, and every NIST 800-53 Rev5 control in the Moderate baseline, with how 20x evidence meets it._", "", + f"- **FedRAMP ID:** {pe.get('fedRampId')} (simulated: no FedRAMP ID has been assigned)", + f"- **Version:** {m['version']} | **Last updated:** {m['lastUpdated']}", + f"- **Source:** {m['updateSource']}", + f"- **Bound to inventory signal:** `{pe['ksi_signal_id']}`", + f"- **FedRAMP rules (pinned):** {pe['rules']['version']} at `{pe['rules']['commit'][:12]}`", + "", "## Summary", "", + f"- FedRAMP rules ({len(doc['fedRampRequirements'])}): {_summary_line(s['fedRampRequirements'])}", + f"- {(s.get('simulatedCounterparties') or {}).get('statement', 'No rule record relies on a simulated counterparty.')}", + f"- Key Security Indicators ({len(doc['keySecurityIndicators'])}): " + f"{_summary_line(s['keySecurityIndicators'])}", + f"- Rev5 Moderate controls ({sum(s['securityControlsModerate'].values())}): " + f"{_summary_line(s['securityControlsModerate'])}", + f"- Controls beyond Moderate mapped by KSIs ({sum(s['securityControlsBeyondModerate'].values())}): " + f"{_summary_line(s['securityControlsBeyondModerate'])}", + "", *_assessor_lines(doc), "", + "## FedRAMP rules", "", "| Rule | Status | Implementation | Gap / closes with |", "|---|---|---|---|"] + for r in doc["fedRampRequirements"]: + x = r["providerExtensions"] + gap = next((v for v in r["frrValidation"] if v.startswith("Gap: ")), "") + closes = next((v for v in r["frrValidation"] if v.startswith("Closes with: ")), "") + sim = f" (simulated {x['simulated']['counterparty']})" if x.get("simulated") else "" + out.append(f"| `{r['frrID']}` | {x['status']}{sim} | {_cell(' '.join(r['frrImplementation']))} | " + f"{_cell((gap + ' ' + closes).strip()) or '—'} |") + out += ["", "## Key Security Indicators", "", + "| KSI | Status | Automated methods | Measures |", "|---|---|---|---|"] + for k in doc["keySecurityIndicators"]: + x = k["providerExtensions"] + out.append(f"| `{k['ksiId']}` | {k['ksiImplementationStatus']} | {x['automatedMethods']} | " + f"{_cell('; '.join(k['ksiTests'])) or '—'} |") + out += ["", "## NIST 800-53 Rev5 controls", "", + "| Control | Status | Basis | 20x coverage |", "|---|---|---|---|"] + for c in doc["securityControls"]: + x = c["providerExtensions"] + cov = ", ".join(x["ksis"] + x["fedrampRules"]) or "—" + tag = "" if x["inModerateBaseline"] else " (beyond Moderate)" + out.append(f"| {c['controlId']}{tag} | {x['status']} | {_cell(x['basis'])} | {_cell(cov)} |") out += ["", "---", "_Source of truth: the signed `security-decision-record.json`._"] return "\n".join(out) diff --git a/scripts/build-trust-center.py b/scripts/build-trust-center.py index 31bad9cb..04f0e1d8 100644 --- a/scripts/build-trust-center.py +++ b/scripts/build-trust-center.py @@ -44,6 +44,8 @@ from _freshness import load_freshness_config # noqa: E402 import _decisions # noqa: E402 import _gates # noqa: E402 +import _offering # noqa: E402 +import _redact # noqa: E402 FRESHNESS: dict[str, Any] = load_freshness_config(os.environ.get("FRESHNESS_CONFIG") or None) VDR_MAX_AGE_HOURS = FRESHNESS["windows"][".well-known/vdr-report.json"] @@ -202,6 +204,14 @@ def _props(item: dict[str, Any]) -> dict[str, str]: return {p["name"]: p["value"] for p in item.get("props", []) if "name" in p} +def _published_scope(applies_to: dict[str, Any] | None) -> dict[str, Any]: + """A decision's scope as published: IAM user names withheld.""" + scope = dict(applies_to or {}) + if "resources" in scope: + scope["resources"] = _redact.withhold_iam_users(scope["resources"]) + return scope + + def register_items(decisions: list[dict[str, Any]]) -> list[dict[str, Any]]: """The decision register's records (data/decisions.json), flattened for the queue, the precedent count and the decision log. In force reads as open.""" @@ -212,7 +222,7 @@ def register_items(decisions: list[dict[str, Any]]) -> list[dict[str, Any]]: "description": r.get("justification", ""), "status": "open" if r.get("status") == "in-force" else "closed", "disposition": r.get("disposition"), "scheduled_completion": r.get("planned_completion"), - "applies_to": r.get("applies_to") or {}, + "applies_to": _published_scope(r.get("applies_to")), "decided_by": r.get("decided_by"), "decided_on": r.get("decided_on"), "review_by": r.get("review_by"), }) return out @@ -749,6 +759,30 @@ def escalation_by_kind(inp: dict[str, Any], pending: list[dict[str, Any]]) -> di return out +def framework_figures(irs: list[dict[str, Any]]) -> dict[str, str]: + """The Rev5 Moderate view of the control projection (scripts/_controls.py): + baseline coverage, measured rather than assumed (the projection's controls + inside the FedRAMP Moderate baseline over the baseline's size, so a baseline + control missing from the projection lowers it), and the projection's + responsibility split. The SDR publishes the same projection per control.""" + import _common + import _controls + baseline = set(_controls.BASELINE_CONTROLS) + control_ids = {ir["control-id"] for ir in irs} + stack: dict[str, int] = {} + for ir in irs: + cls = _common.classify(_common.prop(ir, "implementation-status"), _common.prop(ir, "control-origination")) + stack[cls] = stack.get(cls, 0) + 1 + return { + "moderate_coverage": f"{len(control_ids & baseline)}/{len(baseline)}", + "moderate_baseline": str(len(baseline)), + "moderate_beyond": str(len(control_ids - baseline)), + "moderate_implemented": str(stack.get("implemented", 0)), + "moderate_inherited": str(stack.get("fully-inherited", 0) + stack.get("partially-inherited", 0)), + "moderate_na": str(stack.get("not-applicable", 0)), + } + + def build_posture(inp: dict[str, Any]) -> dict[str, Any]: ksis = inp["signal"].get("ksis", []) by_status: dict[str, int] = {} @@ -768,10 +802,13 @@ def build(inp: dict[str, Any], commit: str, now: datetime) -> dict[str, Any]: pending = build_decisions_pending(inp, now, log, gaps) return { "schema": SCHEMA, + "fedRampId": _offering.fedramp_id(), "generated_at": now.isoformat(timespec="seconds"), "commit": commit, "ksi_signal_id": signal_id, "system": {"id": inp["signal"].get("system_id"), "impact_level": (inp["signal"].get("categorization") or {}).get("impact_level")}, + # The program sought and that it is not held (scripts/_offering.py; the CPO and SDR carry the same). + "certification": _offering.certification(), "picture": build_picture(inp, now), # REQ-GOV-2: the profile and conformance results this build conforms to. "profile": (inp["vdr"].get("methodology") or {}).get("profile"), @@ -838,7 +875,7 @@ def main() -> None: ap.add_argument("--policy-dir", default=str(REPO / "infrastructure" / "policy")) ap.add_argument("--checkov-config", default=str(REPO / ".checkov.yaml")) ap.add_argument("--scn-register", default=str(REPO / "docs" / "scn" / "scn-register.csv")) - ap.add_argument("--no-figures", action="store_true", help="skip framework coverage (needs the built inventory)") + ap.add_argument("--no-figures", action="store_true", help="skip the Rev5 Moderate figures (needs the built inventory)") ap.add_argument("--commit", default="") ap.add_argument("--output", default="trust-center.json") a = ap.parse_args() @@ -859,7 +896,8 @@ def load(path: str, required: bool = True) -> Any: annotations = _load_module("check_policy_annotations", REPO / "scripts" / "check-policy-annotations.py") figures = None if not a.no_figures: - figures = _load_module("inject_figures", REPO / "scripts" / "inject-figures.py").compute_figures() + import _controls + figures = framework_figures(_controls.load(a.ksi_signal)) inp = { "signal": load(a.ksi_signal), "vdr": load(a.vdr), diff --git a/scripts/build-trust-manifest.py b/scripts/build-trust-manifest.py new file mode 100644 index 00000000..e52cac40 --- /dev/null +++ b/scripts/build-trust-manifest.py @@ -0,0 +1,173 @@ +#!/usr/bin/env python3 +"""The trust center's manifest: every piece of FedRAMP certification data, where +it is, how to fetch and verify it, and its human-readable forms (CDS-TRC-PAC, +CDS-TRC-HMR, CDS-CSO-UTC). + +It is generated, never hand-kept: the artifact list is the governed freshness +config (every artifact published under /.well-known/ must have an entry there, +or tests/test_freshness_config.py fails), the policies and procedures come from +this build's policy index. Each artifact's complete view (`.view.md`) is the +one every workflow that publishes it puts beside it (scripts/_signers.py, which +tests/test_human_views_published.py holds to each publisher's publish step), so +an artifact only another workflow writes (the quarterly issue index, the +review index) lists its view too; and a view the deploy should have written +beside a file it built but did not fails the build. The curated summary +(`.md`) is listed when this build wrote one. So the manifest cannot omit a +published artifact or name a view that is not published. + + python3 scripts/build-trust-manifest.py --dir . --policy-index policy-index.json \ + --output trust-manifest.json --md-output trust-manifest.md +""" + +import argparse +import json +import sys +from datetime import datetime, timezone +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _freshness # noqa: E402 +import _offering # noqa: E402 +import _signers # noqa: E402 + +REPO = Path(__file__).resolve().parent.parent +SITE = "https://samaydlette.com" +ISSUER = _signers.ISSUER +# Every workflow that signs a published artifact (scripts/_signers.py, which +# tests/test_publishers.py holds equal to the workflows' publish steps). +SIGNERS = dict(_signers.IDENTITIES) +MEDIA = {".json": "application/json", ".md": "text/markdown; charset=utf-8", ".csv": "text/csv", + ".jsonl": "application/x-ndjson", ".gz": "application/gzip"} +# Published by something other than the deploy, so not built here; shown +# human-readably on the trust page, which renders them from the live JSON. +LIVE_RENDERED = {"ksi-signal-runtime.json": "the runtime signal, published daily by the runtime Lambda", + "vdr-status.json": "the nightly evidence run's status beacon"} +EXTERNAL = [{ + "name": "Independent availability status (CDS-CSO-AVR)", + "url": "https://raw.githubusercontent.com/sam-aydlette/samaydlette.com/availability-status/availability-status.json", + "media_type": "application/json", + "human_readable": ["https://github.com/sam-aydlette/samaydlette.com/blob/availability-status/availability-status.md"], + "note": "Served by GitHub, independent of the offering's AWS hosting, so it stays available when the offering " + "is not.", +}] +ACCESS = ( + "All certification data is public: no account, key or request is needed. Fetch any artifact with an HTTPS GET " + "(CORS is open for read-only use from a browser). Verify a signed artifact with cosign against an identity " + "named in `signed_by` (one passing is enough): `cosign verify-blob --bundle --certificate-identity " + "--certificate-oidc-issuer https://token.actions.githubusercontent.com `. Every JSON artifact has a " + "complete human-readable view (`.view.md`) that this build checked reproduces the JSON exactly, and most have a " + "curated Markdown summary (`.md`). The policies and procedures are served as Markdown. This manifest is itself " + "signed, and is the programmatic index of everything listed. A step-by-step guide per rule is in " + "assessor-guide.json.") + + +def _signer(name): + return " or ".join(_signers.signers(name)) + + +def _schema(path): + if path.suffix != ".json" or not path.is_file(): + return None + try: + doc = json.loads(path.read_text()) + except (OSError, json.JSONDecodeError): + return None + s = doc.get("$schema") if isinstance(doc, dict) else None + return s if isinstance(s, str) and s.startswith("http") else None + + +def artifacts(fresh, d): + out = [] + for a in fresh["artifacts"]: + rel = a["path"] + name = rel.rsplit("/", 1)[1] + local = d / name + suffix = Path(name).suffix + entry = {"name": name, "url": f"{SITE}/{rel}", "media_type": MEDIA.get(suffix, "application/octet-stream"), + "cadence": a["cadence"], "max_age_hours": a["max_age_hours"], "signed": a["signed"]} + if a.get("signature"): + entry["signature"] = f"{SITE}/{a['signature']}" + who = _signer(name) + entry["signed_by"] = who + schema = _schema(local) + if name == "ksi-signal.json": + schema = f"{SITE}/.well-known/ksi-signal.schema.json" + if schema: + entry["schema"] = schema + human = [] + stem = name[:-len(suffix)] if suffix in (".json", ".csv") else None + if stem and (d / f"{stem}.md").is_file(): + human.append(f"{SITE}/.well-known/{stem}.md") + view = _signers.view(name) + if view: + if local.is_file() and not (d / view).is_file(): + raise SystemExit(f"::error::trust manifest: {name} was built here without its view {view}; every " + "publisher puts both (fail-closed)") + human.append(f"{SITE}/.well-known/{view}") + if name in LIVE_RENDERED: + human.append(f"{SITE}/trust/ (renders {LIVE_RENDERED[name]} from the live JSON)") + entry["human_readable"] = human + out.append(entry) + return out + + +def build(fresh, d, policy_index, now, commit=None): + arts = artifacts(fresh, d) + policies = [{"name": e["name"], "kind": e["kind"], "url": e["url"], "media_type": MEDIA[".md"], + "version": e["version"], "last_updated": e["last_updated"]} for e in policy_index["entries"]] + return {"manifest_type": "fedramp-certification-data-manifest", "schema_version": "1", + "fedRampId": _offering.fedramp_id(), + "generated_at": now.isoformat(), "commit": commit, + "trust_center": f"{SITE}/trust/", "access": ACCESS, + "signers": {**SIGNERS, "oidc_issuer": ISSUER}, + "summary": {"artifacts": len(arts), "policies_and_procedures": len(policies), + "with_human_readable_form": sum(1 for x in arts if x["human_readable"])}, + "artifacts": arts, "policies_and_procedures": policies, "external": EXTERNAL} + + +def render_markdown(m): + out = ["# FedRAMP certification data: manifest", "", + f"_Everything the trust center ({m['trust_center']}) shares, generated on every deploy. Source of truth: " + "the signed `trust-manifest.json`._", "", + f"- **Generated:** {m['generated_at']} | **Commit:** `{m['commit'] or 'local build'}`", + f"- **Artifacts:** {m['summary']['artifacts']} | **Policies and procedures:** " + f"{m['summary']['policies_and_procedures']}", "", + "## Programmatic access", "", m["access"], "", "## Signing identities", ""] + out += [f"- {k}: `{v}`" for k, v in m["signers"].items()] + out += ["", "## Artifacts", "", "| Artifact | Media type | Cadence | Signature | Human-readable |", + "|---|---|---|---|---|"] + for a in m["artifacts"]: + sig = f"[bundle]({a['signature']}) ({a['signed_by']})" if a.get("signature") else "unsigned" + human = ", ".join(h if not h.startswith("http") else f"[{h.rsplit('/', 1)[1]}]({h})" + for h in a["human_readable"]) or "—" + out.append(f"| [{a['name']}]({a['url']}) | {a['media_type']} | {a['cadence']}, {a['max_age_hours']}h | " + f"{sig} | {human} |") + out += ["", "## Policies and procedures", "", "| Name | Kind | Version | Last updated |", "|---|---|---|---|"] + out += [f"| [{p['name']}]({p['url']}) | {p['kind']} | `{p['version']}` | {p['last_updated']} |" + for p in m["policies_and_procedures"]] + out += ["", "## Elsewhere", ""] + out += [f"- [{e['name']}]({e['url']}): {e['note']}" for e in m["external"]] + return "\n".join(out) + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + ap.add_argument("--dir", default=".") + ap.add_argument("--policy-index", default="policy-index.json") + ap.add_argument("--freshness", default=str(REPO / "infrastructure" / "schemas" / "freshness-config.json")) + ap.add_argument("--commit", default=None) + ap.add_argument("--output", default="trust-manifest.json") + ap.add_argument("--md-output", default="trust-manifest.md") + a = ap.parse_args(argv) + fresh = _freshness.load_freshness_config(a.freshness) + m = build(fresh, Path(a.dir), json.loads(Path(a.policy_index).read_text()), datetime.now(timezone.utc), + a.commit) + Path(a.output).write_text(json.dumps(m, indent=2) + "\n") + if a.md_output: + Path(a.md_output).write_text(render_markdown(m) + "\n") + print(f"trust-manifest: {m['summary']}") + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/build-vdr-monthly.py b/scripts/build-vdr-monthly.py new file mode 100644 index 00000000..c518c4cc --- /dev/null +++ b/scripts/build-vdr-monthly.py @@ -0,0 +1,401 @@ +#!/usr/bin/env python3 +"""Monthly vulnerability detection and response activity report. + +VER-TFR-MHR: report vulnerability detection and response activity, in a +consistent human-readable format, at least monthly. VER-RPT-HLO: include a +high-level overview of ALL detection and response activities in the period, +including vulnerability disclosure, bug bounty, penetration testing and +assessments. VER-RPT-PER: summarize all activity since the previous report, +including persistent verification and validation. + +Writes vdr-monthly.json and vdr-monthly.md for the calendar month to date (UTC). +Every build adds the runs it can see to the month: the scans and feeds the VDR +build read, the runtime verification runs, the nightly non-machine +verification, the activities generated from the run records of the +mechanisms that replace people (the simulated assessor's runs, the incident, +inbox and recovery exercises and the audit-log review's planted intruder: +generated_runs), and the historical entries kept in data/vdr-activities.json. The previous published vdr-monthly.json carries the +month's earlier runs forward; when the month turns, the finished month moves to +`previousMonths` (kept for twelve months) and a new month starts. Each activity +type is listed every time, with "none this period" when nothing happened. + + build-vdr-monthly.py --vdr vdr-report.json --history vdr-history.json \ + --decisions ../data/decisions.json --activities ../data/vdr-activities.json \ + --non-machine vdr-non-machine-vv.json [--runtime-runs FILE] [--previous vdr-monthly.json] + +A missing or unreadable input stops the build: an absent input cannot read as +"no activity". +""" + +import argparse +import importlib.util +import json +import re +import sys +from datetime import datetime, timezone +from pathlib import Path + +HERE = Path(__file__).resolve().parent +sys.path.insert(0, str(HERE)) +import _offering # noqa: E402 +import _decisions # noqa: E402 + +_spec = importlib.util.spec_from_file_location("cr26_for_monthly", HERE / "build-cr26-vdr.py") +if _spec is None or _spec.loader is None: + raise SystemExit("::error::monthly VDR report: cannot load build-cr26-vdr.py (fail-closed)") +cr26 = importlib.util.module_from_spec(_spec) +_spec.loader.exec_module(cr26) + +JSON_OUT = "vdr-monthly.json" +MD_OUT = "vdr-monthly.md" +KEEP_MONTHS = 12 +RUNTIME_URI = "https://samaydlette.com/.well-known/ksi-signal-runtime.json" + +# Every activity type the report states, in order. `feeds` are the detection +# feed names (methodology.detection.feeds[].feed) whose runs count for it; +# `recorded` the data/vdr-activities.json kinds that count for it. +ACTIVITY_TYPES = [ + {"type": "sca", "title": "Software composition analysis (Grype over every dependency tree; Dependabot alerts)", + "feeds": {"grype", "dependabot"}, "recorded": set()}, + {"type": "iac-sast", "title": "Infrastructure-as-code static analysis (Checkov, tfsec)", + "feeds": {"checkov", "tfsec"}, "recorded": set()}, + {"type": "code-sast", "title": "Code static analysis (CodeQL)", "feeds": {"codeql"}, "recorded": set()}, + {"type": "dast-site", "title": "Dynamic scan of the public site (OWASP ZAP)", "feeds": {"zap"}, + "recorded": {"manual-scan"}}, + {"type": "dast-api", "title": "Authenticated dynamic scan of the Silk Reeling API", + "feeds": {"zap-api", "dast-api"}, "recorded": set()}, + {"type": "threat-intel", "title": "Known-exploited and exploit-prediction feeds (CISA KEV, FIRST EPSS)", + "feeds": {"kev", "epss"}, "recorded": set()}, + {"type": "runtime-vv", "title": "Runtime verification and validation of machine resources", "feeds": set(), + "recorded": set()}, + {"type": "non-machine-vv", "title": "Verification and validation of non-machine resources (machine checks, nightly)", + "feeds": set(), "recorded": set()}, + {"type": "vdp", "title": "Vulnerability disclosure program: reports received", "feeds": set(), + "recorded": {"vdp-report"}}, + {"type": "bug-bounty", "title": "Bug bounty program", "feeds": set(), "recorded": {"bug-bounty"}}, + {"type": "pentest", "title": "Penetration testing", "feeds": set(), "recorded": {"penetration-test"}}, + {"type": "assessment", "title": "Assessments", "feeds": set(), "recorded": {"assessment"}}, + {"type": "exercise", "title": "Exercises with simulated participants: incident response, the FedRAMP Security " + "Inbox, recovery, and the audit-log review's planted intruder", + "feeds": set(), "recorded": set()}, +] +TYPES = {t["type"] for t in ACTIVITY_TYPES} +FEED_TYPE = {f: t["type"] for t in ACTIVITY_TYPES for f in t["feeds"]} +KIND_TYPE = {k: t["type"] for t in ACTIVITY_TYPES for k in t["recorded"]} + +ACT_TOP = {"$schema", "$comment", "schema", "programs", "activities"} +ACT_KEYS = {"id", "kind", "date", "end_date", "performed_by", "summary", "evidence", "recorded_by"} +ACT_REQUIRED = {"id", "kind", "date", "performed_by", "summary", "evidence", "recorded_by"} +PROGRAMS = {"vdp", "bug-bounty", "penetration-testing"} +ACT_ID_RE = re.compile(r"^ACT-\d{3}$") +DATE_RE = re.compile(r"^\d{4}-\d{2}-\d{2}$") + + +def _fail(msg): + raise SystemExit(f"::error::monthly VDR report: {msg} (fail-closed)") + + +def _read(path, what): + p = Path(path) + if not p.is_file(): + _fail(f"{what} {path} not found") + try: + return json.loads(p.read_text(encoding="utf-8")) + except (json.JSONDecodeError, UnicodeDecodeError) as exc: + _fail(f"{what} {path} is not valid JSON: {exc.__class__.__name__}") + + +# --- the operator's record of activity outside the pipeline ------------------------- + +def validate_activities(doc, where="data/vdr-activities.json"): + if not isinstance(doc, dict) or doc.get("schema") != "vdr-activities/1": + _fail(f"{where} is not a vdr-activities/1 document") + if set(doc) - ACT_TOP: + _fail(f"{where}: unknown field(s) {sorted(set(doc) - ACT_TOP)}") + progs = doc.get("programs") + if not isinstance(progs, dict) or set(progs) != PROGRAMS: + _fail(f"{where}: programs must state exactly {sorted(PROGRAMS)}") + for name, p in progs.items(): + if not isinstance(p, dict) or not isinstance(p.get("active"), bool) or not str(p.get("note") or "").strip(): + _fail(f"{where}: programs.{name} needs active (true/false) and a note") + acts = doc.get("activities") + if not isinstance(acts, list): + _fail(f"{where}: activities must be a list") + seen = set() + for a in acts: + aid = a.get("id") if isinstance(a, dict) else None + if not isinstance(aid, str) or not ACT_ID_RE.match(aid) or aid in seen: + _fail(f"{where}: activity id {aid!r} is not a unique ACT-NNN") + seen.add(aid) + if set(a) - ACT_KEYS or ACT_REQUIRED - set(a): + _fail(f"{aid}: fields must be {sorted(ACT_REQUIRED)} plus optional end_date") + if a["kind"] not in KIND_TYPE: + _fail(f"{aid}: kind {a['kind']!r} is not one of {sorted(KIND_TYPE)}") + for k in ("date", "end_date"): + if k in a and not (isinstance(a[k], str) and DATE_RE.match(a[k])): + _fail(f"{aid}: {k} must be YYYY-MM-DD") + if a.get("end_date") and a["end_date"] < a["date"]: + _fail(f"{aid}: end_date is before date") + for k in ("performed_by", "summary", "evidence", "recorded_by"): + if not isinstance(a[k], str) or not a[k].strip(): + _fail(f"{aid}: {k} must be a non-empty string") + return doc + + +# --- runs ------------------------------------------------------------------------------ + +def _month_bounds(now): + start = datetime(now.year, now.month, 1, tzinfo=timezone.utc) + return start, now + + +def _in(at, lo, hi): + dt = cr26._maybe_dt(at) + return bool(dt and lo <= dt <= hi) + + +def pipeline_runs(vdr): + """The scan and feed runs one VDR build read, as [{type, source, at, status, count}].""" + meth = vdr.get("methodology") or {} + det = meth.get("detection") or {} + runs = [] + for feed in det.get("feeds") or []: + if not isinstance(feed, dict) or feed.get("feed") not in FEED_TYPE: + continue + # KEV and EPSS are dated by their publisher; a scan by the build that ran it. + at = feed.get("source_date") if feed["feed"] in ("kev", "epss") else det.get("checked_at") + runs.append({"type": FEED_TYPE[feed["feed"]], "source": f"{feed['feed']} ({feed.get('file')})", + "at": at, "status": feed.get("status"), "count": feed.get("count")}) + for key, typ in (("dast", "dast-site"), ("dast_api", "dast-api"), ("codeql", "code-sast")): + d = meth.get(key) + if isinstance(d, dict): + runs.append({"type": typ, "source": d.get("scanner") or key, "at": d.get("generated_at"), + "status": d.get("status"), "count": d.get("alerts", d.get("count"))}) + return [r for r in runs if r["at"]] + + +def runtime_runs(vdr, retained): + """Runtime V&V runs: every retained run when the emitter retains them, else + the one run the VDR build read.""" + if retained is not None: + rows = retained.get("runs") if isinstance(retained, dict) else retained + if not isinstance(rows, list): + _fail("runtime runs file has no runs list") + out = [] + for r in rows: + if not isinstance(r, dict) or not r.get("emitted_at"): + _fail("a retained runtime run has no emitted_at") + out.append({"type": "runtime-vv", "source": r.get("signal_id") or RUNTIME_URI, "at": r["emitted_at"], + "status": "failed" if r.get("failed") else "ok", + "count": r.get("validations") if not isinstance(r.get("validations"), list) + else len(r["validations"])}) + return out, "retained runs (every run the runtime emitter kept)" + rt = (vdr.get("methodology") or {}).get("runtime_verification") + if isinstance(rt, dict) and rt.get("verified") and rt.get("run_history"): + # The emitter's signed run history, carried by the VDR build that verified it. + return runtime_runs(vdr, {"runs": rt["run_history"]})[0], \ + "retained runs (the run history the runtime emitter signs into its signal)" + note = ("latest run only: the runtime emitter publishes only its latest run, so a run replaced between " + "two nightly builds is not counted") + if isinstance(rt, dict) and rt.get("verified") and rt.get("emitted_at"): + return [{"type": "runtime-vv", "source": rt.get("signal_id") or RUNTIME_URI, "at": rt["emitted_at"], + "status": "failed" if rt.get("failed") else "ok", "count": rt.get("validations")}], note + return [], note + "; the VDR build recorded no verified runtime run" + + +def non_machine_runs(nmv): + if not isinstance(nmv, dict) or nmv.get("schema") != "non-machine-vv/2": + _fail("non-machine status is not a non-machine-vv/2 document") + n = len(nmv.get("resources") or []) + return [{"type": "non-machine-vv", "source": f"machine checks ({n} resources)", + "at": nmv.get("generatedAt"), "status": nmv.get("status"), "count": n}] + + +def recorded_runs(acts): + return [{"type": KIND_TYPE[a["kind"]], "source": f"{a['id']}: {a['summary']}", + "at": f"{a.get('end_date') or a['date']}T00:00:00+00:00", "status": "recorded", + "count": None, "performedBy": a["performed_by"], "evidence": a["evidence"]} + for a in acts["activities"]] + + +def generated_runs(incidents=None, assessment=None, inbox=None, recovery=None, audit=None): + """Activities taken from the run records of the automated mechanisms, never + typed in by a person (VER-RPT-HLO): every input is optional, and one not + given adds nothing.""" + out = [] + for i in (incidents or {}).get("incidents") or []: + if i.get("exercise") and i.get("detected_at"): + out.append({"type": "exercise", "source": f"{i['id']}: incident exercise (simulated)", + "at": i["detected_at"], "status": "ok", "count": None}) + if isinstance(assessment, dict) and assessment.get("issued_at"): + who = (assessment.get("assessor") or {}).get("name") or "the simulated assessor" + out.append({"type": "assessment", "source": f"{who}: simulated assessment run", "at": assessment["issued_at"], + "status": "ok", "count": len(assessment.get("records") or [])}) + if isinstance(inbox, dict) and inbox.get("emitted_at"): + out.append({"type": "exercise", "source": "FedRAMP Security Inbox exercise (simulated sender)", + "at": inbox["emitted_at"], "status": "ok", "count": len(inbox.get("cases") or [])}) + for r in (recovery or {}).get("reviews") or []: + out.append({"type": "exercise", "source": f"recovery exercise due {r.get('dueDate')}", "at": r.get("heldAt"), + "status": "ok" if r.get("result") == "pass" else "failed", "count": None}) + if isinstance(audit, dict) and audit.get("generated_at"): + caught = (audit.get("exercise") or {}).get("caught") + out.append({"type": "exercise", "source": "audit-log review: planted simulated intruder", + "at": audit["generated_at"], "status": "ok" if caught else "failed", "count": None}) + return [r for r in out if r["at"]] + + +def _key(r): + return (r["type"], r["source"], r["at"]) + + +def merge(*lists): + out = {} + for rows in lists: + for r in rows: + out.setdefault(_key(r), r) + return sorted(out.values(), key=lambda r: (r["type"], r["at"], r["source"])) + + +# --- build ------------------------------------------------------------------------------- + +def overview(runs, programs): + rows = [] + for t in ACTIVITY_TYPES: + mine = [r for r in runs if r["type"] == t["type"]] + row = {"type": t["type"], "title": t["title"], "runsInPeriod": len(mine), + "lastRun": max((r["at"] for r in mine), default=None), + "failedRuns": sum(1 for r in mine if r.get("status") not in ("ok", "recorded")), + "summary": "none this period" if not mine else f"{len(mine)} in period"} + prog = {"vdp": "vdp", "bug-bounty": "bug-bounty", "pentest": "penetration-testing"}.get(t["type"]) + if prog: + row["program"] = programs[prog] + rows.append(row) + return rows + + +def build(vdr, mrh, register, acts, nmv, retained, previous, now, generated=()): + if not isinstance(vdr, dict) or not isinstance(vdr.get("findings"), list): + _fail("vdr-report.json has no findings list") + lo, hi = _month_bounds(now) + month = lo.strftime("%Y-%m") + rt_runs, rt_basis = runtime_runs(vdr, retained) + seen = pipeline_runs(vdr) + rt_runs + non_machine_runs(nmv) + recorded_runs(acts) + list(generated) + archive = [] + carried = [] + if isinstance(previous, dict): + if previous.get("schema") != "vdr-monthly/1": + _fail("previous vdr-monthly.json is not a vdr-monthly/1 document") + archive = list(previous.get("previousMonths") or []) + if previous.get("period", {}).get("month") == month: + carried = previous.get("runs") or [] + elif previous.get("period", {}).get("month", "") < month: + # The month turned: the previous report is that month's final report. + archive.insert(0, {k: previous[k] for k in ("period", "overview", "response") if k in previous}) + else: + _fail("previous vdr-monthly.json is for a later month") + runs = [r for r in merge(carried, seen) if _in(r["at"], lo, hi)] + response = cr26.activity_summary(vdr, mrh, register, lo.isoformat(), hi.isoformat()) + return { + "schema": "vdr-monthly/1", + "rules": ["VER-TFR-MHR", "VER-RPT-HLO", "VER-RPT-PER"], + "generatedAt": now.isoformat(), + "period": {"month": month, "from": lo.isoformat(), "to": hi.isoformat()}, + "source": {"vdrReportId": vdr.get("report_id"), "ksiSignalId": vdr.get("ksi_signal_id"), + "activities": "data/vdr-activities.json", "nonMachine": "vdr-non-machine-vv.json"}, + "runtimeRunsBasis": rt_basis, + "overview": overview(runs, acts["programs"]), + "response": {"counts": response["counts"], "remediations": response["remediations"], + "decisionsRecorded": response["decisionsRecorded"], + "decisionsClosed": response["decisionsClosed"]}, + "runs": runs, + "previousMonths": archive[:KEEP_MONTHS], + } + + +# --- render ----------------------------------------------------------------------------- + +def _cell(v): + return cr26._cell("" if v is None else v) + + +def render(doc): + p = doc["period"] + c = doc["response"]["counts"] + out = [f"# Vulnerability detection and response: {p['month']}", "", + "_FedRAMP VER-TFR-MHR, VER-RPT-HLO, VER-RPT-PER. Month to date; rebuilt with every VDR report. " + "Source of truth: the signed vdr-monthly.json beside this file._", "", + f"Period: {p['from']} to {p['to']}", "", + "## Overview of all activities", "", + "| Activity | This period | Last run | Failed runs |", "|---|---|---|---|"] + for o in doc["overview"]: + what = o["summary"] + if "program" in o: + prog = o["program"] + what += f" (program {'active' if prog['active'] else 'not active'}: {prog['note']})" + out.append(f"| {_cell(o['title'])} | {_cell(what)} | {o['lastRun'] or 'none'} | {o['failedRuns']} |") + out += ["", f"Runtime runs counted from: {doc['runtimeRunsBasis']}.", "", + "## Response", "", + f"- Detections: {c['detections']}; evaluations: {c['evaluations']}; rating changes: " + f"{c['ratingChanges']}; reductions: {c['reductions']}", + f"- No longer reported: {c['noLongerReported']}; remediations: {c['remediations']}; " + f"decisions recorded: {c['decisionsRecorded']}; decisions closed: {c['decisionsClosed']}", "", + "## Runs this period", ""] + if doc["runs"]: + out += ["| Activity | Source | Time | Status | Count |", "|---|---|---|---|---|"] + for r in doc["runs"]: + out.append(f"| {r['type']} | {_cell(r['source'])} | {r['at']} | {_cell(r.get('status'))} | " + f"{_cell(r.get('count'))} |") + else: + out.append("_None this period._") + if doc["previousMonths"]: + out += ["", "## Previous months", "", "| Month | Activities with runs | Detections | Remediations |", + "|---|---|---|---|"] + for m in doc["previousMonths"]: + active = sum(1 for o in m.get("overview") or [] if o.get("runsInPeriod")) + mc = (m.get("response") or {}).get("counts") or {} + out.append(f"| {m['period']['month']} | {active} of {len(m.get('overview') or [])} | " + f"{mc.get('detections', '')} | {mc.get('remediations', '')} |") + return "\n".join(out) + "\n" + + +def main(argv=None): + ap = argparse.ArgumentParser() + ap.add_argument("--vdr", default="vdr-report.json") + ap.add_argument("--history", default="vdr-history.json") + ap.add_argument("--decisions", default=None) + ap.add_argument("--activities", default=str(HERE.parent / "data" / "vdr-activities.json")) + ap.add_argument("--non-machine", default="vdr-non-machine-vv.json") + ap.add_argument("--runtime-runs", default=None) + ap.add_argument("--previous", default=None) + ap.add_argument("--incidents", default=None, help="data/incidents.json: its exercises are activities") + ap.add_argument("--assessment", default=None, help="the verified simulated-assessment.json") + ap.add_argument("--inbox", default=None, help="the verified fedramp-inbox-simulation.json") + ap.add_argument("--recovery-exercises", default=None, help="vdr-recovery-exercises.json") + ap.add_argument("--audit-log-review", default=None, help="vdr-audit-log-review.json") + ap.add_argument("--out-dir", default=".") + ap.add_argument("--now", default=None, help=argparse.SUPPRESS) + a = ap.parse_args(argv) + now = datetime.fromisoformat(a.now) if a.now else datetime.now(timezone.utc) + + def opt(path, what): + return _read(path, what) if path and Path(path).is_file() else None + generated = generated_runs(opt(a.incidents, "incident register"), opt(a.assessment, "simulated assessment"), + opt(a.inbox, "inbox simulation"), opt(a.recovery_exercises, "recovery exercises"), + opt(a.audit_log_review, "audit-log review")) + doc = build(_read(a.vdr, "VDR report"), _read(a.history, "VDR history"), _decisions.load(a.decisions), + validate_activities(_read(a.activities, "activity record"), a.activities), + _read(a.non_machine, "non-machine status"), + _read(a.runtime_runs, "runtime runs") if a.runtime_runs else None, + _read(a.previous, "previous monthly report") if a.previous else None, now, generated) + doc = _offering.stamp_fedramp_id(doc) # CDS-CSO-FID + out = Path(a.out_dir) + (out / JSON_OUT).write_text(json.dumps(doc, indent=2) + "\n", encoding="utf-8") + (out / MD_OUT).write_text(render(doc), encoding="utf-8") + quiet = [o["type"] for o in doc["overview"] if not o["runsInPeriod"]] + print(f"Monthly VDR report {doc['period']['month']}: {len(doc['runs'])} runs; none this period: " + f"{', '.join(quiet) or 'nothing'}") + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/build-vdr-report.py b/scripts/build-vdr-report.py index f037032d..efdb9d68 100755 --- a/scripts/build-vdr-report.py +++ b/scripts/build-vdr-report.py @@ -52,11 +52,15 @@ # Shared helpers live next to this script; keep it runnable from any cwd. sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _offering # noqa: E402 +import _codeql # noqa: E402 import _decisions # noqa: E402 +import _evaluation # noqa: E402 import _gates # noqa: E402 import _redact # noqa: E402 import _rules # noqa: E402 import _triage # noqa: E402 +import _zap_api # noqa: E402 # ============================================================================= @@ -201,7 +205,7 @@ def classify_finding(tool_id): # Scanner sources whose findings are vulnerabilities (governed by the register) # rather than configuration findings (governed by .checkov.yaml + the maps # above). Mirrors vuln-gate.py's VULN_SOURCES. -VULN_SOURCES = {"grype", "zap", "dependabot"} +VULN_SOURCES = {"grype", "zap", "dependabot", "codeql"} # The disposition vocabulary (REQ-DSP-3), the dispositions that pass the # vulnerability gate, and those that close a finding for the deadline gate are @@ -289,6 +293,7 @@ def classify_vulnerability(finding, register, today=None, mitigation=None): # The runtime emitter runs daily; two days allows one missed run. Moves to the # governed freshness config with the other windows. RUNTIME_SIGNAL_MAX_AGE_HOURS = 48 +RUNTIME_SIGNAL_URI = "https://samaydlette.com/.well-known/ksi-signal-runtime.json" def component_fingerprint(component): @@ -378,14 +383,62 @@ def load_runtime_signal(path, pubkey_path=None, now=None, max_age_hours=RUNTIME_ return out out["verified"] = True out["emitted_at"] = sig.get("emitted_at") + out["signal_id"] = sig.get("signal_id") + out["divergence"] = (sig.get("divergence") or {}).get("status") emitted = _ts(sig.get("emitted_at"), None) if sig.get("emitted_at") else None out["fresh"] = bool(emitted and timedelta(0) <= now - emitted <= timedelta(hours=max_age_hours)) if not out["fresh"]: out["reason"] = f"runtime signal emitted {sig.get('emitted_at')} is outside {max_age_hours}h" out["validations"] = sig.get("validations") or [] + # VER-RPT-PER: the emitter's bounded run history, inside the signed payload. + out["run_history"] = [r for r in sig.get("run_history") or [] if isinstance(r, dict) and r.get("emitted_at")] return out +def runtime_verification_summary(runtime): + """The runtime V&V run this report read (VER-RPT-PER): when it ran, whether + its signature verified, how many validations it ran and how many failed. + Counts are published only from a verified signal.""" + runtime = runtime or {} + out = {"uri": RUNTIME_SIGNAL_URI, "verified": bool(runtime.get("verified")), + "fresh": bool(runtime.get("fresh")), "reason": runtime.get("reason"), + "emitted_at": runtime.get("emitted_at"), "signal_id": runtime.get("signal_id"), + "validations": None, "failed": None, "divergence": None} + if out["verified"]: + vals = [v for v in runtime.get("validations") or [] if isinstance(v, dict)] + out["validations"] = len(vals) + out["failed"] = sum(1 for v in vals if v.get("result") != "pass") + out["divergence"] = runtime.get("divergence") + # Every run the emitter retained (signed with the signal), so a period + # report counts the runs a later run replaced (VER-RPT-PER). + out["run_history"] = [{k: r.get(k) for k in ("signal_id", "emitted_at", "validations", "failed", + "unassessed", "divergence")} + for r in runtime.get("run_history") or []] + return out + + +def dast_summary(zap_path): + """The DAST scan this report ingested: when ZAP generated it and how many + alert types it reported. None when no ZAP report was given.""" + if not zap_path: + return None + p = Path(zap_path) + if not p.is_file(): + return {"scanner": "zap", "status": "missing", "generated_at": None, "alerts": None} + try: + doc = json.loads(p.read_text()) + except (json.JSONDecodeError, UnicodeDecodeError): + return {"scanner": "zap", "status": "unreadable", "generated_at": None, "alerts": None} + if not isinstance(doc, dict): + return {"scanner": "zap", "status": "unreadable", "generated_at": None, "alerts": None} + # ZAP writes nanoseconds; datetime parses at most microseconds. + raw = re.sub(r"(\.\d{6})\d+", r"\1", doc["created"]) if isinstance(doc.get("created"), str) else None + created = _ts(raw, None) if raw else None + gen = created.astimezone(timezone.utc).isoformat() if created and created.tzinfo else None + alerts = sum(len(site.get("alerts") or []) for site in doc.get("site") or [] if isinstance(site, dict)) + return {"scanner": "zap", "status": "ok", "generated_at": gen, "alerts": alerts} + + def mitigation_state(finding, mitigations, inventory, runtime, today): """The mitigation covering this finding, evaluated, or None. When several name the finding, the first valid one (by ID) is used, else the first; a @@ -463,8 +516,8 @@ def void(reason): "CKV_AWS_310": "The two origins serve distinct path patterns (static S3 site vs the Silk Reeling API), not a redundant failover pair; an origin group would require multi-region storage.", "CKV_AWS_117": "Lambda has no internet egress, no sensitive data, no private endpoint targets. NAT Gateway adds cost without commensurate isolation benefit.", "CKV_AWS_35": "CloudTrail log files use SSE-S3, consistent with the DEC-029 decision family: service-written control-plane records about this account's own infrastructure; a CMK adds key sprawl and a decrypt dependency for every consumer without a confidentiality benefit.", - "CKV2_AWS_10": "CloudWatch Logs integration declined: it duplicates every management event into paid log-group storage to enable metric filters this single-operator system reviews quarterly instead (KSI-MLA-RVL). Log-file validation plus the TLS-only versioned bucket carry the integrity requirement.", - "CKV_AWS_252": "SNS delivery notifications declined: no consumer exists for a per-delivery notification; the quarterly review reads the bucket directly.", + "CKV2_AWS_10": "CloudWatch Logs integration declined: it duplicates every management event into paid log-group storage to enable metric filters; this system reviews the trail automatically every night instead (scripts/audit-log-review.py, KSI-MLA-RVL). Log-file validation plus the TLS-only versioned bucket carry the integrity requirement.", + "CKV_AWS_252": "SNS delivery notifications declined: no consumer exists for a per-delivery notification; the nightly audit-log review reads CloudTrail's event history directly (scripts/audit-log-review.py).", } # Read .checkov.yaml as YAML if PyYAML is available; fall back to a forgiving @@ -739,6 +792,9 @@ def ingest_suppressions(checkov_yaml): "title": f"{check_id} suppressed", "description": rationale, "resource": ".checkov.yaml", + # What the suppression affects: the resources its decision names. + "affected_resources": list(_decisions.records(DECISIONS).get( + RISK_ACCEPTED_BY_CHECK_ID.get(check_id), {}).get("applies_to", {}).get("resources", [])), "current_disposition": "risk-accepted", "detected_at": detected.get(RISK_ACCEPTED_BY_CHECK_ID.get(check_id)), "pain": evaluation["pain"], @@ -1047,21 +1103,45 @@ def zap_report_age_days(path, now): for fmt in ("%a, %d %b %Y %H:%M:%S", "%a, %d %b %Y %H:%M:%S %Z", "%Y-%m-%dT%H:%M:%S"): try: gen = datetime.strptime(stamp.strip(), fmt) - return (now.replace(tzinfo=None) - gen).days + # Fractional days: a whole-day floor would let a 3-day window read 3.9 days as 3. + return round((now.replace(tzinfo=None) - gen).total_seconds() / 86400, 2) except ValueError: continue return None +class KevCatalog(set): + """The CISA KEV catalog's CVE IDs, plus each entry's dates (VDR-TFR-KEV): + `entries` is {cveID: {"due_date", "date_added"}} from the catalog.""" + + def __init__(self, ids=(), entries=None): + super().__init__(ids) + self.entries = entries or {} + + def ingest_kev(path): - """Load CISA KEV catalog and return the set of CVE IDs.""" + """Load the CISA KEV catalog: its CVE IDs, with the catalog's dueDate and + dateAdded for each (BOD 26-04 remediation dates).""" if not path or not Path(path).exists(): - return set() + return KevCatalog() try: doc = json.loads(Path(path).read_text()) except json.JSONDecodeError: - return set() - return {v.get("cveID") for v in (doc.get("vulnerabilities") or []) if v.get("cveID")} + return KevCatalog() + entries = {v["cveID"]: {"due_date": v.get("dueDate"), "date_added": v.get("dateAdded")} + for v in (doc.get("vulnerabilities") or []) if isinstance(v, dict) and v.get("cveID")} + return KevCatalog(entries, entries) + + +def kev_dates(kev_cves, cve, now): + """(due_at, date_added, overdue) for a KEV finding from the catalog, or + (None, None, False). The catalog's due date is a day; it is read as the + start of that day, UTC, the earlier reading.""" + entry = (getattr(kev_cves, "entries", None) or {}).get(cve) if cve else None + due = _ts(f"{entry['due_date']}T00:00:00+00:00", None) if entry and entry.get("due_date") else None + if due is None: + return None, (entry or {}).get("date_added"), False + return due.isoformat(), entry.get("date_added"), now >= due class EpssScores(dict): @@ -1335,11 +1415,13 @@ def _no_direct_impact(m): def triage_item(f, kind, *, pain, is_kev, epss_scores, reach, mitigation=None, - check_decision=None, register=None, clock=None): - """The facts the triage policy decides one finding from.""" + check_decision=None, register=None, clock=None, extra=None): + """The facts the triage policy decides one finding from. `extra`: the + grouping, projection and evaluation-time facts (group, projected_ns, + detected_ns, default_evaluation), only for report findings.""" cve = f.get("cve") scores = epss_scores or {} - return { + return {**(extra or {}), "id": f["tracking_id"], "kind": kind, "pain": pain, @@ -1360,6 +1442,32 @@ def triage_item(f, kind, *, pain, is_kev, epss_scores, reach, mitigation=None, } +def evaluation_facts(f, dec, clk, epss_scores, now): + """The triage facts beyond the ratings: the finding's group (VER-EVA-GRV), + a decision's projected remediation date (VER-TFR-MAV), when the source + detected it and when it was first evaluated (VER-TFR-EVU), and whether its + ratings rest on defaults (no vector, no prediction score).""" + plan = dec.get("planned_reduction") or {} + projected = None + if plan.get("target_pain") == "N0" and plan.get("date"): + projected = _triage.to_ns(datetime.combine(date.fromisoformat(plan["date"]), datetime.min.time(), + tzinfo=timezone.utc)) + # A decision record is an evaluation: a finding a person decided on before + # the pipeline first saw it was evaluated then. + evaluated = clk["first_evaluated_dt"] + if dec.get("decided_on"): + evaluated = min(evaluated, datetime.combine(date.fromisoformat(dec["decided_on"]), datetime.min.time(), + tzinfo=timezone.utc)) + cve = f.get("cve") + return { + "group": _evaluation.group_key(f, dec.get("id")), + "projected_ns": projected, + "detected_ns": _triage.to_ns(_ts(clk["first_detected"], now)), + "evaluated_ns": _triage.to_ns(evaluated), + "default_evaluation": not f.get("cvss_vector") and not (cve and cve in (epss_scores or {})), + } + + def _decide_one(finding, *, is_kev=False, irv=False, epss_scores=None, epss_threshold=0.1, lev_overrides=None, today=None, kind="suppression", register=None, mitigation=None): """The policy's decision for one finding, outside a report (unit callers).""" @@ -1425,10 +1533,11 @@ def _valid_v31(vector): return all(k in m and m[k] in _V3_VALUES[k] for k in _V3_REQUIRED) and len(m) == len(_V3_REQUIRED) -def load_check_vectors(path=None, today=None): +def load_check_vectors(path=None, today=None, decisions=None): """{check_id: entry} for entries in force today. Malformed file or entry fails closed.""" p = Path(path) if path else DEFAULT_CHECK_VECTORS today = today or datetime.now(timezone.utc).date() + in_force_ids = {r["id"] for r in _decisions.in_force(decisions or DECISIONS)} try: doc = json.loads(p.read_text()) except (OSError, json.JSONDecodeError) as exc: @@ -1446,6 +1555,11 @@ def load_check_vectors(path=None, today=None): if not e.get("decided_by") or not e.get("decided_on"): continue # proposed, not decided: not in force _parse_day(e["decided_on"], where) + # A vector is decided through the decision register (DEC-180): a decided + # entry that names no record in force would be a decision nobody made. + if e.get("decision") not in in_force_ids: + raise SystemExit(f"::error::{where}: decided, but decision {e.get('decision')!r} is not a decision " + "record in force (fail-closed)") if review_by < today: continue # lapsed in_force[check_id] = e @@ -1459,9 +1573,34 @@ def apply_check_vector(finding, vectors): out = dict(finding) out["cvss_vector"] = vectors[finding["tool_id"]]["vector"] out["vector_source"] = "governed-check-vector" + out["vector_rationale"] = vectors[finding["tool_id"]].get("rationale") + out["vector_decision"] = vectors[finding["tool_id"]].get("decision") return out +_EPA_EFFECT = {"N0": "no adverse effect on agencies is expected", "N1": "minimal customer effects", + "N2": "narrow customer effects", "N3": "a disruptive effect on one agency", + "N4": "a debilitating effect on one agency or a disruptive effect on more than one", + "N5": "a debilitating effect on more than one agency"} + + +def impact_rationale(f, pain, fully_mitigated): + """VER-EVA-EPA: one line on the likely effect on agencies and what it rests on.""" + if fully_mitigated: + return "Fully mitigated: the impact has been removed (N0)." + cls = f.get("_classification") or {} + where = (f"on a component holding {cls.get('data_sensitivity', 'unclassified')} data, " + f"{cls.get('mission_criticality', 'unrated')} criticality, " + f"{cls.get('agency_scope', 'multi')}-agency scope") + if f.get("vector_source") == "governed-check-vector": + basis = f"{f.get('vector_rationale') or 'governed vector'} (vector decided in {f.get('vector_decision')})" + elif f.get("cvss_vector"): + basis = "the advisory's CVSS vector" + else: + basis = "the scanner's severity (no vector): a default, not a contextual estimate" + return f"{pain}, {_EPA_EFFECT.get(pain, pain)}: {basis}; {where}." + + def load_lev_overrides(path=None): p = Path(path) if path else DEFAULT_LEV_OVERRIDES if not p.exists(): @@ -1626,10 +1765,20 @@ def resolve_component(finding, index, tf_components=()): # (scripts/_redact.py); a finding that names a full ARN matches it so. if c and _redact.redact_text(str(c)) in index: return index[_redact.redact_text(str(c))] + # A site root ("https://host" or "https://host/") is the page it serves: + # the root object, index.html (VER-EVA-EIR: evaluated, not assumed). + root = str(finding.get("resource") or "") + if re.fullmatch(r"https?://[^/]+/?", root): + return resolve_component({"resource": root.rstrip("/") + "/index.html"}, index, tf_components) res = _redact.redact_text(str(finding.get("resource") or "")) m = _TF_ADDRESS.match(res) if m: rtype, rname = m.group(1), m.group(2) + # The exact resource type first: aws_iam_group_policy_attachment.operators + # is the attachment block, not the aws_iam_group.operators it prefixes. + exact = {cid for cid, tf_type, tf_name in tf_components if tf_name == rname and tf_type == rtype} + if exact: + return exact.pop() if len(exact) == 1 else None hits = {cid for cid, tf_type, tf_name in tf_components if tf_name == rname and tf_type and rtype.startswith(tf_type)} return hits.pop() if len(hits) == 1 else None @@ -1642,6 +1791,42 @@ def resolve_component(finding, index, tf_components=()): return None +_DECISION_RESOURCE = re.compile(r"^aws-([a-z0-9-]+?)(?:::([\w.-]+))?$") + + +def resolve_decision_resource(name, inventory): + """The component a decision record's resource name denotes, or None. An + exact inventory identifier first; else the register's `aws-[::]` + form, matched to the one Terraform component of that resource type (and + name, when given). Ambiguous or unknown: None, never a guess.""" + if not isinstance(name, str) or not name: + return None + if name in inventory["index"]: + return inventory["index"][name] + m = _DECISION_RESOURCE.match(name) + if not m: + return None + tf_type = "aws_" + m.group(1).replace("-", "_") + want = m.group(2).replace("-", "_") if m.group(2) else None + hits = {cid for cid, t, n in inventory["tf"] if t == tf_type and (want is None or n == want)} + return hits.pop() if len(hits) == 1 else None + + +def resolve_decision_resources(names, inventory): + """The component a decision's resources resolve to: the one they all name, + or, when they name several, an internet-reachable one first (the + conservative choice for IRV). None when none resolves.""" + cids = [] + for n in names or []: + cid = resolve_decision_resource(n, inventory) + if cid and cid not in cids: + cids.append(cid) + if not cids: + return None + reachable = [c for c in cids if (inventory["classes"].get(c) or {}).get("internet_reachable") is True] + return (reachable or cids)[0] + + def tf_components_of(ksi_signal_path): """(component_id, tf_type, tf_name) for every Terraform-backed component.""" p = Path(ksi_signal_path) @@ -1880,11 +2065,13 @@ def build_report(findings, suppressions, kev_cves, ledger, index=None, config=No mitigations = mitigations or {} if decision_records is None: decision_records = load_decision_records() + full_records = {r["id"]: r for r in _decisions.in_force(DECISIONS)} + incidents = _evaluation.load_incidents() matched_register, matched_mitigations, lapsed = set(), set(), [] margin_days = int(config["likely_overdue_margin_days"]) report_findings = [] summary = { - "by_pain": {"N1": 0, "N2": 0, "N3": 0, "N4": 0, "N5": 0}, + "by_pain": {"N0": 0, "N1": 0, "N2": 0, "N3": 0, "N4": 0, "N5": 0}, "blocking": 0, "kev": 0, "risk_accepted": len(suppressions), @@ -1913,7 +2100,8 @@ def build_report(findings, suppressions, kev_cves, ledger, index=None, config=No matched_mitigations.update(mit.get("matched") or [mit["id"]]) if mit and mit["valid"]: f = {**f, "verified_mitigation_at": mit["verified_on"], "mitigation_id": mit["id"]} - if cid is None: + if cid is None and f.get("source") != "process": + # A process finding names the pipeline, not an inventory component. summary["unresolved_components"] += 1 is_kev = bool(f.get("cve") and f["cve"] in kev_cves) @@ -1941,21 +2129,30 @@ def build_report(findings, suppressions, kev_cves, ledger, index=None, config=No else: summary["ledger_newly_detected"] += 1 clk = clock_facts(f, ledger.get(tid), now) + dec_id = (check_decision or {}).get("decision_id") or (reg[1].get("decision_id") if reg else None) + dec = full_records.get(dec_id) or {} items.append(triage_item( f, "finding", pain=assign_pain(f, index, config), is_kev=is_kev, epss_scores=epss_scores, reach=reach_facts(f, cid, inv), mitigation=mit, check_decision=check_decision, register=({"key": reg[0], "entry": reg[1]} if reg else None), clock={"start_ns": _triage.to_ns(clk["start_dt"]), - "first_evaluated_ns": _triage.to_ns(clk["first_evaluated_dt"])})) - prepared.append((f, cid, mit, is_kev, check_decision, reg, tid, clk)) + "first_evaluated_ns": _triage.to_ns(clk["first_evaluated_dt"])}, + extra=evaluation_facts(f, dec, clk, epss_scores, now))) + prepared.append((f, cid, mit, is_kev, check_decision, reg, tid, clk, dec)) # Risk-accepted entries (.checkov.yaml suppressions) are decided for # reachability and exploitability only: they carry no deadline. sup_prepared = [] for s in suppressions: s = apply_check_vector(s, check_vectors) - s_cid = resolve_component(s, inv["index"], inv["tf"]) - s = {**s, "_classification": classification_for(s, inventory, index)} + # A .checkov.yaml suppression names a file, not a resource: it affects + # the resources its decision record names (VER-RPT-AVI), so those are + # what reachability and classification are decided from. + s_cid = (resolve_component(s, inv["index"], inv["tf"]) + or resolve_decision_resources(s.get("affected_resources"), inv)) + s = {**s, "_classification": ((inv["classes"].get(s_cid) or _FAILSAFE_CLASSIFICATION) + if s_cid and inventory is not None + else classification_for(s, inventory, index))} s_pain = assign_pain(s, index, config) if s.get("cvss_vector") else s.get("pain") items.append(triage_item(s, "suppression", pain=s_pain, is_kev=s.get("is_kev", False), epss_scores=epss_scores, reach=reach_facts(s, s_cid, inv))) @@ -1963,10 +2160,11 @@ def build_report(findings, suppressions, kev_cves, ledger, index=None, config=No # 2. Decisions: one evaluation of policies/triage.rego for the whole report. decisions = _triage.decide(items, now=now, epss_threshold=config["epss_threshold"], - margin_days=margin_days, lev_overrides=lev_overrides) + margin_days=margin_days, lev_overrides=lev_overrides, + evaluation_days=_rules.evaluation_days()) # 3. Publish. - for (f, cid, mit, is_kev, check_decision, reg, tid, clk), d in zip(prepared, decisions[:len(prepared)], strict=True): + for (f, cid, mit, is_kev, check_decision, reg, tid, clk, dec), d in zip(prepared, decisions[:len(prepared)], strict=True): pain, irv, lev, sla = d["pain"], d["irv"], d["lev"], d["sla_days"] disposition, finding_decision_id = d["disposition"], d["decision_id"] is_suppressed, needs_remediation = d["closed"], d["needs_remediation"] @@ -2006,8 +2204,17 @@ def build_report(findings, suppressions, kev_cves, ledger, index=None, config=No # VER-RPT-VDT per-vulnerability record fields. History and reductions come # from the ledger (REQ-PAI-2); the deadline runs whatever the disposition. is_overdue = d["is_overdue"] + # VDR-TFR-KEV: a known exploited vulnerability is remediated by the + # catalog's due date, even when fully mitigated: the earlier of that and + # the Class C deadline, and overdue once the catalog's date has passed. + kev_due_at, kev_added, kev_overdue = kev_dates(kev_cves, f.get("cve"), now) if is_kev else (None, None, False) + if kev_due_at and due_at: + due_at = min(due_at, kev_due_at, key=lambda x: _ts(x, now)) + elif kev_due_at and needs_remediation: + due_at = kev_due_at + is_overdue = is_overdue or kev_overdue next_reduction = ({"estimated_time": due_at, "target_pain": "remediated"} - if sla is not None else None) + if sla is not None or kev_due_at else None) overdue_explanation = (block_reason if block_this else f"within Class C SLA: {days_since_detected}d of {sla}d allowed" if sla is not None @@ -2045,7 +2252,10 @@ def build_report(findings, suppressions, kev_cves, ledger, index=None, config=No "cvss_vector": f.get("cvss_vector"), "vector_source": f.get("vector_source") or ("scanner" if f.get("cvss_vector") else None), "technical_impact": technical_impact(f), + "impact_rationale": impact_rationale(f, pain, fully_mitigated), "is_kev": is_kev, + **({"kev_due_at": kev_due_at, "kev_date_added": kev_added, "kev_overdue": kev_overdue} + if is_kev and (kev_due_at or kev_added) else {}), "completed_reductions": hist["completed_reductions"], "next_reduction": next_reduction if needs_remediation else None, "current_disposition": d["label"] or "open", @@ -2063,11 +2273,14 @@ def build_report(findings, suppressions, kev_cves, ledger, index=None, config=No "will_be_overdue": d["will_be_overdue"], "accepted": d["accepted"], "accepted_at": accepted_at, + **({"accepted_basis": d["accepted_basis"]} if d["accepted"] else {}), # VER-RPT-AVI: the recorded justification when an in-force record # carries one; otherwise the gap is stated, never filled in. "acceptance_explanation": ( ((reg[1].get("justification") or "").strip() or NOT_RECORDED - if reg and d["record_status"] == "in-force" else NOT_RECORDED) + if reg and d["record_status"] == "in-force" + else (dec.get("justification") or "").strip() or NOT_RECORDED + if d["accepted_basis"] == "projected-past-maximum-period" else NOT_RECORDED) if d["accepted"] else None), "overdue_explanation": (block_reason if block_this else f"documented suppression ({disposition}); tracked as {finding_decision_id}" @@ -2075,7 +2288,25 @@ def build_report(findings, suppressions, kev_cves, ledger, index=None, config=No "supplementary_info": "", "is_blocking": block_this, "block_reason": block_reason, + # VER-EVA-GRV: the group the finding is evaluated in, at its most + # exposed open member; the group's deadline binds this finding. + "group_id": d["group"], + "group_pain": d["group_pain"], + "group_lev": d["group_lev"], + "group_irv": d["group_irv"], + "group_due_at": (_triage.from_ns(d["group_due_ns"], clk["start_dt"].tzinfo) + if d["group_due_ns"] is not None else None), + # VER-TFR-EVU: null when evaluated in time; otherwise why not. + "evaluation_late": d["evaluation_late"], + "evaluation": _evaluation.evaluation_record( + {"internet_reachable": irv, "irv_basis": d["irv_basis"], "likely_exploitable": lev, + "lev_basis": d["lev_basis"]}, f, + cid=cid, ctype=inv["types"].get(cid), metrics=parse_vector(f.get("cvss_vector")), + classification=f.get("_classification"), auto=_evaluation.automatable(f, dec), + expl=_evaluation.exploitation(f, is_kev, incidents, now.isoformat()), + proximate=None, prevalence=None, epss=epss_used, is_kev=is_kev), }) + report_findings[-1]["public_disclosure"] = _evaluation.disclosure(report_findings[-1]) # Histogram and blocking counts reflect genuinely-open findings only; # suppressed findings are summarized via the risk-accepted/FP counts. if not is_suppressed: @@ -2111,6 +2342,8 @@ def build_report(findings, suppressions, kev_cves, ledger, index=None, config=No "tool_id": s.get("tool_id"), "title": s.get("title", ""), "resource": s.get("resource", ""), + **({"affected_resources": _redact.withhold_iam_users(s["affected_resources"])} + if s.get("affected_resources") else {}), "first_detected": s_clk["first_detected"], "first_evaluated": s_clk["first_evaluated"], "completed_evaluation": now.isoformat(), @@ -2127,6 +2360,12 @@ def build_report(findings, suppressions, kev_cves, ledger, index=None, config=No "explanation": s.get("explanation", ""), }) + # VER-EVA-GRV/EFA: groups, prevalence and proximate findings are read across + # every finding; then each finding's public form follows its disclosure + # determination (VER-RPT-NID). + groups = _evaluation.attach_groups(report_findings, len(inv.get("classes") or {})) + withheld_exercise = _evaluation.withheld_detail_exercise(report_findings) # DEC-182, before redaction + report_findings = [_evaluation.redact(r) for r in report_findings] cve_findings = consolidate_by_cve(report_findings, risk_accepted_records) summary["unique_cves"] = len(cve_findings) summary["unique_cves_open"] = sum(1 for c in cve_findings if "open" in c["dispositions"]) @@ -2144,8 +2383,10 @@ def build_report(findings, suppressions, kev_cves, ledger, index=None, config=No "impact_level": _profile["impact_level"], "summary": summary, "findings": report_findings, + "groups": groups, "cve_findings": cve_findings, "risk_accepted": risk_accepted_records, + "withheld_detail_exercise": withheld_exercise, "rules_reference": { "evaluation": "FedRAMP 20x VER-EVA-* (PAIN, IRV, LEV)", "timeframes": ("FedRAMP 20x VDR-TFR-PVR Class C remediation; " @@ -2236,6 +2477,8 @@ def main(): parser.add_argument("--grype", default=None, help="Grype SCA scan output (grype -o json)") parser.add_argument("--zap", default=None, help="OWASP ZAP JSON report (committed monthly DAST scan)") parser.add_argument("--zap-max-age-days", type=int, default=14, help="Fail the build if the ZAP report is older than this or missing; default 14 tracks the VDR-TFR-PDD Class C drift-detection cadence (0 disables)") + parser.add_argument("--zap-api", default=None, help="Authenticated ZAP API scan report of the Silk Reeling API (scripts/_zap_api.py); presence and age are the detection gate's (detection.zap-api)") + parser.add_argument("--codeql", default=None, help="CodeQL code-scanning alerts and analyses (scripts/_codeql.py); completeness and age are the detection gate's (detection.codeql)") parser.add_argument("--kev", default=None, help="CISA KEV catalog JSON") parser.add_argument("--conformance", default=None, help="Signed conformance results (scripts/build-conformance.py): the report names their profile version and sha256 (REQ-GOV-2). Given but missing or invalid: the build fails.") parser.add_argument("--detection", default=None, help="The detection gate's summary (scripts/detection-gate.py --output): recorded in the methodology so the report says what its inputs were and how old.") @@ -2248,6 +2491,7 @@ def main(): parser.add_argument("--epss", default=None, help="EPSS scores (FIRST epss_scores-current.csv, optionally gzipped, or JSON). Enables the EPSS likely-exploitable union (EPSS >= threshold OR active); without it, LEV falls back to the severity proxy.") parser.add_argument("--checkov-yaml", default=".checkov.yaml", help="Path to .checkov.yaml whose skip-check list defines suppressions (default: .checkov.yaml in CWD)") parser.add_argument("--previous-vdr", default=None, help="Path to previous VDR report; preserves first_detected timestamps across builds for SLA-clock enforcement.") + parser.add_argument("--failed-runs", default=None, help="Failed runs of the pipeline (gh run list --status failure --json workflowName,createdAt,updatedAt,event,headBranch): each stopped run on main since the previous report is listed in process_failures (VDR-CSO-FAV). Given but unreadable: the build fails.") parser.add_argument("--output", default="vdr-report.json", help="Output report path") parser.add_argument("--md-output", default="vdr-report.md", help="Human-readable VDR rendering path (VER-TFR-MHR); empty to skip") parser.add_argument("--ksi-signal", default="ksi-signal.json", help="Canonical inventory; its signal_id binds this VDR to one inventory (reconciliation invariant e)") @@ -2280,12 +2524,13 @@ def main(): findings.extend(ingest_tfsec(args.tfsec)) findings.extend(ingest_dependabot(args.dependabot)) findings.extend(ingest_grype(args.grype)) + findings.extend(_codeql.ingest_codeql(args.codeql)) - # DAST: ingest the committed monthly ZAP report. Bootstrapping is allowed — - # a MISSING report only warns (DAST coverage absent until the first scan is - # committed), so the pipeline stays green before the operator's first scan. - # Once a report IS present, it is enforced: an undated or stale one fails the - # build closed (a skipped/forgotten scan must not read as zero findings). + # DAST: ingest the ZAP baseline report from the latest successful zap-dast.yml + # run (daily and after every deploy; scripts/fetch-detection-feeds.sh). A + # missing report is governed by gate mode detection.zap.missing; a present + # one is enforced: an undated or stale one fails the build closed (a skipped + # scan must not read as zero findings). if args.zap: if not Path(args.zap).exists(): err = Path(f"{args.zap}.error") @@ -2310,6 +2555,8 @@ def main(): return 1 _gates.record_event(gates, "detection.zap.stale", stale) + findings.extend(_zap_api.ingest_zap_api(args.zap_api, ingest_zap, load_zap_allowlist())) + findings = dedupe_findings(findings) kev_cves = ingest_kev(args.kev) epss_scores = ingest_epss(args.epss) @@ -2328,15 +2575,59 @@ def main(): check_vectors = load_check_vectors(args.check_vectors) lev_overrides = load_lev_overrides(args.lev_overrides) - report, blocking = build_report(findings, suppressions, kev_cves, ledger, - index=classification_index, config=pain_config, - epss_scores=epss_scores, - disposition_register=disposition_register, - check_vectors=check_vectors, - lev_overrides=lev_overrides, - inventory=load_inventory(args.ksi_signal), - mitigations=load_mitigations(args.mitigations), - runtime=load_runtime_signal(args.runtime_signal, args.runtime_pubkey)) + runtime = load_runtime_signal(args.runtime_signal, args.runtime_pubkey) + inventory = load_inventory(args.ksi_signal) + mitigations = load_mitigations(args.mitigations) + + def _build(fs): + return build_report(fs, suppressions, kev_cves, ledger, + index=classification_index, config=pain_config, + epss_scores=epss_scores, + disposition_register=disposition_register, + check_vectors=check_vectors, + lev_overrides=lev_overrides, + inventory=inventory, mitigations=mitigations, runtime=runtime) + + # VDR-CSO-FAV: a detect-and-recover failure recorded earlier in this run, + # or a finding still on a default after the evaluation window, is itself a + # finding. The second is known only once the findings are decided, so the + # report is decided again with them. + events_path = os.environ.get(_gates.EVENTS_ENV) + run_events = _gates.read_events(events_path) if events_path else [] + # VDR-TFR-PCD: every inventory component reached by a detection technique + # within the month; a component none reached is a recorded gap. + detection_doc = json.loads(Path(args.detection).read_text()) if args.detection else None + coverage = _evaluation.coverage(inventory["components"], detection_doc, dast_summary(args.zap), + datetime.now(timezone.utc)) + if coverage["uncovered"] and detection_doc is not None: + run_events.append(_gates.record_event( + gates, "vdr.coverage", f"no detection in {coverage['window_days']} days: " + f"{', '.join(coverage['uncovered'][:10])}")) + report, blocking = _build(findings + _evaluation.process_findings(run_events, [])) + # VER-EVA-EIR: a finding that resolves to no component was rated at the + # fail-safe, not evaluated; that is recorded until it resolves. + # (Without an inventory, as in unit fixtures, nothing resolves and nothing is recorded.) + if report["summary"].get("unresolved_components") and inventory["components"]: + unresolved = sorted(f["tracking_id"] for f in report["findings"] + if f.get("unresolved_component") and f.get("source") != "process") + run_events.append(_gates.record_event( + gates, "vdr.unresolved-component", + f"{len(unresolved)} finding(s) resolve to no inventory component: {', '.join(unresolved[:5])}")) + process = _evaluation.process_findings(run_events, report["findings"]) + if {p["tracking_id"] for p in process} - {f["tracking_id"] for f in report["findings"]}: + report, blocking = _build(findings + process) + report["coverage"] = coverage + # Stopped runs of the pipeline since the previous report (block-mode + # failures): each is listed with when it failed. Given but unreadable fails. + if args.failed_runs: + try: + runs = json.loads(Path(args.failed_runs).read_text()) + except (OSError, json.JSONDecodeError) as exc: + raise SystemExit(f"::error::--failed-runs {args.failed_runs}: unreadable ({exc.__class__.__name__}) " + "(fail-closed)") from exc + since = (json.loads(Path(args.previous_vdr).read_text()).get("emitted_at") + if args.previous_vdr and Path(args.previous_vdr).is_file() else None) + report["process_failures"] = _evaluation.failed_runs(runs, since) report["ksi_signal_id"] = ksi_signal_id report["false_positives"] = false_positives # Name the inventory component each finding affects, so the trust center can @@ -2376,6 +2667,13 @@ def main(): "fedramp_rules": rules_pin(), "reference": pain_config.get("method_reference", ""), "gates": _gates.published_view(gates), + # VER-EVA-EFA: what each factor in a finding's evaluation record means. + "evaluation_factors": _evaluation.FACTORS, + "process_failures": ("VDR-CSO-FAV: a detect-and-recover check that failed this run, or a finding still " + "on a default after the VER-TFR-EVU window, is a finding with source 'process' " + f"(severity proxy {_evaluation.PROCESS_SEVERITY}); it is remediated when the check " + "passes. A block-mode failure stops the run; each stopped run is listed in " + "process_failures of the next report."), } # Apply each blocking finding's governed mode before writing, so a @@ -2394,10 +2692,16 @@ def main(): # REQ-GOV-2: the profile this report conforms to, and the results of that # profile's conformance tests it was built under. report["methodology"]["profile"] = load_conformance(args.conformance) if args.conformance else None + # VER-RPT-PER: the runs this report saw that the detection summary does not + # list: the runtime verification (its signed signal, verified above) and the + # DAST scan. Facts only; the CR26 period reports summarize them. + report["methodology"]["runtime_verification"] = runtime_verification_summary(runtime) + report["methodology"]["dast"] = dast_summary(args.zap) # G7: what each detection input was when this report was built (T52). report["methodology"]["detection"] = (json.loads(Path(args.detection).read_text()) if args.detection else None) + report = _offering.stamp_fedramp_id(report) # CDS-CSO-FID output_path = Path(args.output) output_path.write_text(json.dumps(report, indent=2, sort_keys=False)) print(f"vdr-report.json: {report['summary']['total_findings']} findings, {report['summary']['blocking']} blocking, {report['summary']['risk_accepted']} risk-accepted") diff --git a/scripts/build-vdr-trend.py b/scripts/build-vdr-trend.py index fbc4d3c1..d979d5c2 100644 --- a/scripts/build-vdr-trend.py +++ b/scripts/build-vdr-trend.py @@ -16,8 +16,12 @@ import argparse import json +import sys from pathlib import Path +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _offering # noqa: E402 + # The published point shape. Exported so backfill-vdr-trend.py reconstructs # historical points through exactly this function — a second implementation @@ -71,6 +75,7 @@ def main(): # REQ-GOV-2: the profile and conformance results of the report this point came from. trend["profile"] = (rpt.get("methodology") or {}).get("profile") trend["points"] = points + trend = _offering.stamp_fedramp_id(trend) # CDS-CSO-FID tp.write_text(json.dumps(trend, indent=2) + "\n") print(f"vdr-trend: {len(points)} point(s); latest {date} " f"open_cves={point['open_cves']} blocking={point['blocking']} kev={point['kev']}") diff --git a/scripts/check-edge-access-logging.py b/scripts/check-edge-access-logging.py new file mode 100644 index 00000000..92fc97d9 --- /dev/null +++ b/scripts/check-edge-access-logging.py @@ -0,0 +1,92 @@ +#!/usr/bin/env python3 +"""Access to the certification data is logged, within the privacy limits (CDS-TRC-ACL). + +Reads the CloudFront standard-logging (v2) configuration the deploy role can see +and fails unless: + + * a delivery from the source named for this site exists; + * that source is the CloudFront distribution's ACCESS_LOGS; + * the delivery goes to S3; and + * its record fields are exactly within ALLOWED_FIELDS and include REQUIRED_FIELDS. + +ALLOWED_FIELDS is the operator's privacy condition: no client IP, forwarded-for, +port, cookies, query string, user agent or referrer is ever logged. It must equal +the delivery's record_fields in infrastructure/bootstrap/trust-access-logs.tf +(tests/test_edge_access_logging.py holds them equal). The configuration is +operator-applied (bootstrap), so this check is what fails the deploy when it is +missing, before the trust center or the SDR say access is logged. + +Inputs are the AWS CLI's JSON (aws logs describe-deliveries, aws logs +get-delivery-source), so the check runs the same on fixtures. Prints no ARN. +""" +import argparse +import json +import sys +from pathlib import Path + +ALLOWED_FIELDS = ("date", "time", "x-edge-location", "c-country", "cs-method", "cs-uri-stem", + "sc-status", "sc-bytes", "x-edge-result-type") +REQUIRED_FIELDS = ("date", "time", "cs-uri-stem", "sc-status") +# Named so the failure message says what was found; any field outside +# ALLOWED_FIELDS fails, whether or not it is listed here. +IDENTIFYING = ("c-ip", "x-forwarded-for", "c-port", "cs(Cookie)", "cs-uri-query", "cs(User-Agent)", + "cs(Referer)") + + +def problems(deliveries, source, name): + out = [] + mine = [d for d in (deliveries or {}).get("deliveries", []) if d.get("deliverySourceName") == name] + if not mine: + return [f"no CloudFront access-log delivery from source {name!r} (bootstrap not applied?)"] + if len(mine) > 1: + out.append(f"{len(mine)} deliveries from {name!r}; expected one") + src = (source or {}).get("deliverySource") or {} + if src.get("name") != name: + out.append(f"delivery source {name!r} could not be read") + if src.get("logType") != "ACCESS_LOGS": + out.append(f"delivery source log type is {src.get('logType')!r}, not ACCESS_LOGS") + if not any(":distribution/" in a and a.startswith("arn:aws:cloudfront::") for a in src.get("resourceArns") or []): + out.append("delivery source is not a CloudFront distribution") + for d in mine: + if d.get("deliveryDestinationType") != "S3": + out.append(f"delivery destination type is {d.get('deliveryDestinationType')!r}, not S3") + fields = d.get("recordFields") or [] + extra = sorted(set(fields) - set(ALLOWED_FIELDS)) + bad = sorted(f for f in extra if f in IDENTIFYING) + if bad: + out.append(f"delivery logs identifying field(s) {bad}") + if sorted(set(extra) - set(bad)): + out.append(f"delivery logs field(s) outside the privacy allowlist: {sorted(set(extra) - set(bad))}") + missing = sorted(set(REQUIRED_FIELDS) - set(fields)) + if missing: + out.append(f"delivery omits required field(s) {missing}") + return out + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + ap.add_argument("--deliveries", required=True, help="aws logs describe-deliveries output") + ap.add_argument("--source", required=True, help="aws logs get-delivery-source output (may be empty)") + ap.add_argument("--name", required=True, help="the delivery source's name") + a = ap.parse_args(argv) + + def read(p): + t = Path(p).read_text() if Path(p).exists() else "" + try: + return json.loads(t) if t.strip() else {} + except json.JSONDecodeError: + return {} + why = problems(read(a.deliveries), read(a.source), a.name) + for w in why: + print(f"::error::edge access logging: {w}", file=sys.stderr) + if why: + print("Access to the certification data is not logged as the trust center states; " + "the deploy does not proceed.", file=sys.stderr) + return 1 + print(f"ok: CloudFront access logging to S3, fields {', '.join(ALLOWED_FIELDS)} " + "(no IP, cookies, query string or user agent)") + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/check-fedramp-id.py b/scripts/check-fedramp-id.py new file mode 100644 index 00000000..6f7a04a0 --- /dev/null +++ b/scripts/check-fedramp-id.py @@ -0,0 +1,165 @@ +#!/usr/bin/env python3 +"""Deploy gate: every FedRAMP report this build publishes carries the offering's +FedRAMP ID (CDS-CSO-FID). + +For each file named: a report in a FedRAMP schema ($schema under +https://fedramp.gov/schemas/) must carry providerExtensions.fedRampId equal to +data/cds/offering.json's fedramp_id, and the CPO also in +serviceIdentification.fedRampPackageId; any other JSON (the issue index, logs, +snapshot manifests, the trust-center data) must carry the same value at top +level, `fedRampId`. A file named here without one fails, as does a file that +cannot be read. Exit 0 pass, 1 fail. + + check-fedramp-id.py # every file in REPORTS, in the current directory + check-fedramp-id.py FILE... # these files + +REPORTS is the one list of what the deploy checks: a group that publishes a +FedRAMP report adds its file here, one line. +""" + +import fnmatch +import json +import sys +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _offering # noqa: E402 + +# Every FedRAMP report the deploy publishes, by built file name. Add a line per report. +# A name with "*" is a glob over the build directory (each match is checked). +REPORTS = ( + "certification-package-overview.json", + "security-decision-record.json", + "ongoing-certification-report.json", + # Vulnerability detection and response: the VDR report and its + # trend ledger at top level; FedRAMP's VDT, AVI and history reports under + # providerExtensions; the monthly activity report and non-machine V&V status. + "vdr-report.json", + "vdr-trend.json", + "vdr-detail-report.json", + "vdr-accepted-vulnerabilities.json", + "vdr-history.json", + "vdr-monthly.json", + "vdr-non-machine-vv.json", + # The nightly's scheduled reviews (DEC-195): the audit-log review and the + # recovery exercises' index (the evidence nightly runs this gate over them). + "vdr-audit-log-review.json", + "vdr-recovery-exercises.json", + # The canonical inventory (the runtime emitter copies the ID from it). + "ksi-signal.json", + # Certification cycle: the FedRAMP Certification Reports index and + # the simulated package submission log. + "fedramp-certification-reports.json", + "package-submission-log.json", + # Notifications: the SCN index (each notification also under its + # providerExtensions), the evaluation log, the incident log, every + # Initial/Ongoing/Final report (FedRAMP's incident schema), the simulated + # deliveries and the simulated FedRAMP Security Inbox run. + "significant-change-notifications.json", + "scn-evaluations.json", + "incident-reports.json", + "incident-deliveries.json", + "incident-INC-*.json", + "fedramp-inbox-simulation.json", + # Trust center, scope and assessor: site files, top-level fedRampId. + "trust-center.json", + "trust-manifest.json", + "availability.json", + "policy-index.json", + "assessor-guide.json", + "simulated-assessment.json", + "agency-access-exercise.json", + "frr-evidence.json", + "minimum-assessment-scope.json", + "secure-configuration-guide.json", + "security-settings.json", + "access-summary.json", + "boundary-map.json", + "reconcile-report.json", + "conformance-results.json", + # The independent monitor's feed as this deploy read it (availability-status.json + # from the availability-status branch; it is built by scripts/availability-probe.py). + "availability-probe.json", +) + +# Published JSON that this deploy step does not check, and why. Every +# freshness-governed JSON artifact is in REPORTS or here +# (tests/test_fedramp_id_trust.py holds that). +EXEMPT = { + "ksi-signal-runtime.json": "Written and KMS-signed by the runtime emitter Lambda after the deploy, not by a " + "deploy builder; it copies fedRampId from the deploy's KSI signal " + "(infrastructure/lambda/index.js), which this gate checks.", + "vdr-status.json": "The nightly's unsigned status beacon, written by evidence-nightly.yml whatever the run's " + "outcome; it is stamped there (null only if the offering cannot be read).", + "ocr-issues.json": "Issued by package-maintenance.yml (scripts/issue-ocr.py), which runs this gate over it " + "and the frozen reports before publishing.", + "quarterly-reviews.json": "Written by package-maintenance.yml (scripts/hold-quarterly-review.py), which runs this " + "gate over it and each new quarterly-review-.json before publishing.", + "security-reviews.json": "Written by package-maintenance.yml (scripts/hold-security-review.py), which runs this " + "gate over it and each new security-review-.json before publishing.", + "boundary-corroboration.json": "The independent corroboration (RAMPART on TAP), committed by the operator and " + "published exactly as the corroborating tool wrote it; stamping it would alter " + "another party's record. The boundary map it corroborates carries the ID.", +} +FEDRAMP_SCHEMAS = _offering.FEDRAMP_SCHEMA_BASES + + +def problems(name, doc, fid): + out = [] + if not isinstance(doc, dict): + return [f"{name}: not a JSON object"] + if str(doc.get("$schema", "")).startswith(FEDRAMP_SCHEMAS): + if (doc.get("providerExtensions") or {}).get("fedRampId") != fid: + out.append(f"{name}: providerExtensions.fedRampId is missing or not the offering's FedRAMP ID") + si = doc.get("serviceIdentification") + if si is not None and si.get("fedRampPackageId") != fid: + out.append(f"{name}: serviceIdentification.fedRampPackageId is not the offering's FedRAMP ID") + elif doc.get("fedRampId") != fid: + out.append(f"{name}: top-level fedRampId is missing or not the offering's FedRAMP ID") + return out + + +def uncovered(artifact_paths, reports=REPORTS, exempt=EXEMPT): + """Published JSON (freshness-config paths, e.g. ".well-known/x.json") that + neither REPORTS nor EXEMPT accounts for, plus any exemption without a + reason or also listed in REPORTS.""" + out = [] + for path in artifact_paths: + name = path.rsplit("/", 1)[-1] + if not name.endswith(".json"): + continue + listed = any(fnmatch.fnmatchcase(name, r) for r in reports) + if listed and name in exempt: + out.append(f"{name} is both checked and exempt") + elif not listed and not str(exempt.get(name) or "").strip(): + out.append(f"{name} is published but neither checked for the FedRAMP ID nor exempt with a reason") + return out + + +def _expand(names, root="."): + out = [] + for n in names: + out += sorted(str(p) for p in Path(root).glob(n)) if "*" in n else [n] + return out + + +def main(argv=None): + files = (sys.argv[1:] if argv is None else argv) or _expand(REPORTS) + fid = _offering.fedramp_id() + bad = [] + for f in files: + try: + doc = json.loads(Path(f).read_text()) + except (OSError, ValueError) as exc: + bad.append(f"{f}: unreadable ({type(exc).__name__})") + continue + bad += problems(Path(f).name, doc, fid) + for b in bad: + print(f"::error::CDS-CSO-FID: {b}") + if not bad: + print(f"CDS-CSO-FID: {len(files)} file(s) carry the offering's FedRAMP ID") + return 1 if bad else 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/check-frr-evidence.py b/scripts/check-frr-evidence.py new file mode 100644 index 00000000..81ebe123 --- /dev/null +++ b/scripts/check-frr-evidence.py @@ -0,0 +1,120 @@ +#!/usr/bin/env python3 +"""Every test a FedRAMP rule record cites ran and passed (FRC-CSX-VVR). + +scripts/_frr.py shows that each piece of evidence a rule record cites exists. +This shows the cited tests passed in this build: it reads the JUnit XML that the +unit-test job's pytest run wrote and fails when a test cited as evidence failed, +errored, was skipped, or did not run at all. A parametrized test passes only +when every one of its cases ran and passed. + +It writes the result per record (frr-evidence.json), which the deploy signs and +publishes beside the Security Decision Record, so a reader can see that each +Implemented record's tests passed in the build that published it. + + python3 scripts/check-frr-evidence.py --junit pytest-results.xml --output frr-evidence.json +""" + +import argparse +import json +import sys +import xml.etree.ElementTree as ET # nosec B405: parses the JUnit file this job's own pytest wrote +from datetime import datetime, timezone +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _frr # noqa: E402 +import _offering # noqa: E402 + +SCHEMA = "frr-evidence/1" + + +def _fail(msg): + raise SystemExit(f"::error::FRR evidence: {msg} (fail-closed)") + + +def junit_outcomes(path): + """{(module path, class or None, function): [outcome per case]} from a JUnit XML file.""" + try: + root = ET.parse(path).getroot() # nosec B314: trusted, locally generated file + except (OSError, ET.ParseError) as exc: + _fail(f"cannot read the test results {path}: {exc}") + out = {} + for case in root.iter("testcase"): + classname, name = case.get("classname", ""), case.get("name", "") + parts = classname.split(".") + # classname is "tests.test_x" or "tests.test_x.TestClass" + if len(parts) >= 2 and parts[-1][:1].isupper(): + module, cls = "/".join(parts[:-1]) + ".py", parts[-1] + else: + module, cls = "/".join(parts) + ".py", None + func = name.split("[", 1)[0] + if case.find("failure") is not None or case.find("error") is not None: + outcome = "failed" + elif case.find("skipped") is not None: + outcome = "skipped" + else: + outcome = "passed" + out.setdefault((module, cls, func), []).append(outcome) + if not out: + _fail(f"{path} records no test cases") + return out + + +def _key(ref): + m = _frr.TEST_RE.match(ref) + if not m: + _fail(f"{ref!r} is not a test reference") + rel, first, second = m.groups() + return (rel, first, second) if second else (rel, None, first) + + +def test_result(ref, outcomes): + cases = outcomes.get(_key(ref)) + if not cases: + return "not run" + if all(c == "passed" for c in cases): + return "passed" + return "failed" if "failed" in cases else "skipped" + + +def evaluate(records, outcomes): + """(per-record results, list of failures).""" + per, failures = {}, [] + for r in records["records"]: + tests = {e["ref"]: test_result(e["ref"], outcomes) for e in r.get("evidence", []) if e["kind"] == "test"} + for ref, res in tests.items(): + if res != "passed": + failures.append(f"{r['frr_id']}: cited test {ref} {res}") + per[r["frr_id"]] = {"status": r["status"], "tests": tests, + "result": "pass" if all(v == "passed" for v in tests.values()) else "fail"} + return per, failures + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + ap.add_argument("--junit", required=True) + ap.add_argument("--records", default=str(_frr.DEFAULT_PATH)) + ap.add_argument("--output", default="frr-evidence.json") + ap.add_argument("--commit", default=None) + a = ap.parse_args(argv) + records = _frr.load(a.records) + per, failures = evaluate(records, junit_outcomes(a.junit)) + cited = sum(len(v["tests"]) for v in per.values()) + doc = {"schema": SCHEMA, "fedRampId": _offering.fedramp_id(), "generated_at": datetime.now(timezone.utc).isoformat(), "commit": a.commit, + "explanation": "Each FedRAMP rule record's cited tests and whether they passed in the unit-test run " + "of the build that published this file (scripts/check-frr-evidence.py). The build " + "fails when any cited test fails, errors, is skipped or does not run.", + "summary": {"records": len(per), "cited_tests": cited, + "records_with_tests": sum(1 for v in per.values() if v["tests"])}, + "records": per} + if failures: + for f in failures: + print(f"::error::{f}") + _fail(f"{len(failures)} cited test(s) did not pass") + Path(a.output).write_text(json.dumps(doc, indent=2) + "\n") + print(f"frr-evidence: {cited} cited tests across {doc['summary']['records_with_tests']} records, all passed") + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/check-fsi-notice.py b/scripts/check-fsi-notice.py new file mode 100644 index 00000000..78128380 --- /dev/null +++ b/scripts/check-fsi-notice.py @@ -0,0 +1,187 @@ +#!/usr/bin/env python3 +"""AFC-CSO-NOC: every change to the FedRAMP Security Inbox contact is notified +to FedRAMP (simulated) within one business day. + +The inbox is simulated for this proof of concept (no mail is received), so what +is published is a contact statement rather than a mailbox. It lives in one +place, data/cds/offering.json (fedramp_security_inbox.contact), with an +append-only history. Each entry after the first is a change, dated by "since". +The first entry establishes the contact; it must say in "basis" why there was +no earlier contact to change from. + +Two halves: + + check() on every pull request and push (the unit-test job): the + contact is one non-empty line of printable text; the newest + history entry is the current contact; every later entry + changes the contact and is dated, not in the future; and + with --base (the same file at the merge base) the history is + append-only and a changed contact has a new entry. + file_notices() on every deploy (scripts/submit-package.py): files a notice + with the simulated FedRAMP for every change not yet filed, + keeps earlier notices unchanged, and reports any notice + filed more than one business day after the deploy that + first published the changed contact, which fails the + deploy. A change takes effect when it is published, so it + is that deploy (recorded in the log's inboxContact, and on + each notice as publishedOn/publishedIn) that the clock runs + from, not the date in "since": a change merged but not yet + deployed cannot go stale, and a failed deploy, which + publishes nothing, cannot make the next one late. NOTHING IS SENT: a notice is an entry in + the published package-submission-log.json, and the + simulated FedRAMP's receipt is a Python function's return + value. No real FedRAMP is notified (DEC-194). + +Stdlib only. +""" + +from __future__ import annotations + +import argparse +import json +import re +import sys +from datetime import date +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _bizdays # noqa: E402 + +REPO = Path(__file__).resolve().parent.parent +DEFAULT = REPO / "data" / "cds" / "offering.json" +CONTACT = re.compile(r"^[\x20-\x7e]{1,300}$") +DAY = re.compile(r"^\d{4}-\d{2}-\d{2}$") +NOTICE_BUSINESS_DAYS = 1 # "immediately": filed no later than the next business day +NOTICE_KEYS = {"changedOn", "contact", "publishedOn", "publishedIn", "filedOn", "receipt"} +PUBLISHED_KEYS = {"contact", "firstPublishedOn", "firstPublishedIn"} + + +def _inbox(doc): + return doc.get("fedramp_security_inbox") if isinstance(doc, dict) else None + + +def _date(value): + if not isinstance(value, str) or not DAY.match(value): + return None + try: + return date.fromisoformat(value) + except ValueError: + return None + + +def check(head: dict, base: dict | None = None, today: date | None = None) -> list[str]: + """Violations of AFC-CSO-NOC in head (and in the step from base to head).""" + today = today or date.today() + out: list[str] = [] + fsi = _inbox(head) + if not isinstance(fsi, dict): + return ["fedramp_security_inbox is missing from data/cds/offering.json (AFC-CSO-INB)"] + contact = fsi.get("contact") + if not isinstance(contact, str) or not CONTACT.match(contact) or not contact.strip(): + out.append("fedramp_security_inbox.contact must be one non-empty line of printable text (at most 300 characters)") + history = fsi.get("history") + if not isinstance(history, list) or not history or not all(isinstance(h, dict) for h in history): + return out + ["fedramp_security_inbox.history must list every contact the inbox has had"] + if history[-1].get("contact") != contact: + out.append("the contact changed without a history entry recording the change") + first = history[0] + if not (isinstance(first.get("basis"), str) and first["basis"].strip()): + out.append("the first history entry has no basis saying why there was no earlier contact to change from") + for i, h in enumerate(history): + since = _date(h.get("since")) + if since is None or since > today: + out.append(f"history[{i}].since must be the date of the change, not in the future") + if i == 0: + continue + if h.get("contact") == history[i - 1].get("contact"): + out.append(f"history[{i}] repeats the previous contact") + if "fedramp_notified" in h: + out.append(f"history[{i}] hand-records a notice; the deploy files it (AFC-CSO-NOC), so remove " + "fedramp_notified") + base_fsi = _inbox(base) if base is not None else None + if isinstance(base_fsi, dict): + base_hist = base_fsi.get("history") or [] + if history[:len(base_hist)] != base_hist: + out.append("fedramp_security_inbox.history was rewritten; it is append-only") + if base_fsi.get("contact") != contact and len(history) <= len(base_hist): + out.append("the contact changed but no history entry was added for the change") + return out + + +def published_contact(head: dict, previous, today: date, commit: str) -> tuple[dict | None, list[str]]: + """(record, problems): the contact this deploy publishes and the deploy that + first published it. Carried over from the previous log while the contact is + unchanged; otherwise this deploy is the first to publish it.""" + contact = _inbox(head)["contact"] + if previous is not None: + if not isinstance(previous, dict) or set(previous) != PUBLISHED_KEYS \ + or _date(previous.get("firstPublishedOn")) is None or not isinstance(previous.get("firstPublishedIn"), str): + return None, ["the previously published inboxContact is malformed; it is carried over unchanged"] + if previous["contact"] == contact: + return dict(previous), [] + return {"contact": contact, "firstPublishedOn": today.isoformat(), "firstPublishedIn": commit}, [] + + +def file_notices(head: dict, previous, today: date, intake, commit: str = "", + published=None) -> tuple[list[dict], list[str]]: + """(notices, problems). Carries over every earlier notice unchanged, files a + notice through `intake` (the simulated FedRAMP) for each contact change in + the history that has none, dated today, and reports every notice filed more + than NOTICE_BUSINESS_DAYS business days after the deploy that first + published its contact. `published` is the previous log's inboxContact (who + first published the contact now in force); a change no earlier deploy + published is published by this one (`today`, `commit`).""" + problems = check(head, today=today) + if problems: + return [], problems + current, problems = published_contact(head, published, today, commit) + if problems or current is None: + return [], problems + notices = list(previous or []) + for i, n in enumerate(notices): + if not isinstance(n, dict) or set(n) != NOTICE_KEYS or _date(n.get("changedOn")) is None \ + or _date(n.get("filedOn")) is None or _date(n.get("publishedOn")) is None: + return [], [f"the previously published change notice {i} is malformed; notices are carried over " + "unchanged"] + filed = {(n["changedOn"], n["contact"]) for n in notices} + for h in _inbox(head)["history"][1:]: + if (h["since"], h["contact"]) in filed: + continue + if h["contact"] == current["contact"]: + pub_on, pub_in = current["firstPublishedOn"], current["firstPublishedIn"] + else: # superseded before any deploy published it: this deploy is the first to publish the change + pub_on, pub_in = today.isoformat(), commit + notice = {"changedOn": h["since"], "contact": h["contact"], "publishedOn": pub_on, "publishedIn": pub_in, + "filedOn": today.isoformat()} + notice["receipt"] = intake(dict(notice)) + notices.append(notice) + filed.add((h["since"], h["contact"])) + for n in notices: + deadline = _bizdays.add_business_days(_date(n["publishedOn"]), NOTICE_BUSINESS_DAYS) + if _date(n["filedOn"]) > deadline: + problems.append(f"the notice of the change first published on {n['publishedOn']} was filed " + f"{n['filedOn']}, after {deadline.isoformat()} (one business day)") + return notices, problems + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + ap.add_argument("--offering", type=Path, default=DEFAULT) + ap.add_argument("--base", type=Path, help="offering.json at the merge base (optional)") + a = ap.parse_args(argv) + head = json.loads(a.offering.read_text()) + base = None + if a.base and a.base.is_file() and a.base.stat().st_size: + base = json.loads(a.base.read_text()) + problems = check(head, base) + for p in problems: + print(f"::error::FedRAMP Security Inbox (AFC-CSO-NOC): {p}") + if not problems: + fsi = _inbox(head) + print(f"FedRAMP Security Inbox: {len(fsi['history'])} history entr{'y' if len(fsi['history']) == 1 else 'ies'}; " + f"{'compared with the merge base' if base else 'no merge base given'}; ok") + return 1 if problems else 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/check-incident-publisher.py b/scripts/check-incident-publisher.py new file mode 100644 index 00000000..cd07288b --- /dev/null +++ b/scripts/check-incident-publisher.py @@ -0,0 +1,140 @@ +#!/usr/bin/env python3 +"""Deploy preflight: the unattended incident report publisher is in place. + +The FedRAMP incident report records (IEC-CSO-IIR/OIR/FIR/AIR) describe the +system as it is after a successful deploy, so a deploy must not succeed +without the prerequisites they rely on. Run early in the deploy job, before +anything is applied, this fails the deploy unless: + + 1. the repository variable AWS_INCIDENT_REPORTS_ROLE_ARN is set, and + 2. it names the role infrastructure/bootstrap/incident-reports.tf creates + (github-actions-incident-reports-oidc, an IAM role ARN), and + 3. the `incident-reports` GitHub Environment exists and deploys only from + main (a custom branch policy naming exactly `main`). + +Check 3 reads GitHub's API with the job token. A missing environment (404) +fails. If the token cannot read the environment at all (any other error), the +check is reported as not observed and the deploy continues on checks 1-2: +the deploy's later incident-publisher job assumes the role from that +environment, so a wrong environment still fails the deploy there. + +Whether the role itself works is proved in the same job before the SDR is +built (scripts/check-incident-role.py assumes it), and again after the deploy: +the `incident-publisher` job calls .github/workflows/incident-reports.yml, +which assumes the role, publishes, and fails the deploy if it cannot. + +Prints no ARN or account ID. Exit 0 pass, 1 fail. +""" + +from __future__ import annotations + +import argparse +import json +import os +import re +import sys +import urllib.error +import urllib.request +from typing import Any + +EXPECTED_ROLE_NAME = "github-actions-incident-reports-oidc" +ENVIRONMENT = "incident-reports" +EXPECTED_BRANCHES = {"main"} +ROLE_ARN_RE = re.compile(r"^arn:aws(-[a-z]+)*:iam::[0-9]{12}:role/(?:[\w+=,.@-]+/)*([\w+=,.@-]+)$") + + +def check_variable(role_arn: str | None) -> list[str]: + if not role_arn or not role_arn.strip(): + return ["the repository variable AWS_INCIDENT_REPORTS_ROLE_ARN is not set: apply " + "infrastructure/bootstrap/incident-reports.tf and set it from the incident_reports_role_arn output"] + m = ROLE_ARN_RE.match(role_arn.strip()) + if not m: + return ["AWS_INCIDENT_REPORTS_ROLE_ARN is not an IAM role ARN"] + if m.group(2) != EXPECTED_ROLE_NAME: + return [f"AWS_INCIDENT_REPORTS_ROLE_ARN names a role other than {EXPECTED_ROLE_NAME}"] + return [] + + +def check_environment(env: dict[str, Any] | None, branch_policies: list[str] | None) -> tuple[list[str], str]: + """(problems, note). env None = the environment does not exist.""" + if env is None: + return [f"the {ENVIRONMENT} GitHub Environment does not exist"], "" + policy = env.get("deployment_branch_policy") or {} + if not policy.get("custom_branch_policies") or policy.get("protected_branches"): + return [f"the {ENVIRONMENT} environment does not restrict deployments to a custom branch list"], "" + if branch_policies is None: + return [], "branch policies not observed" + if set(branch_policies) != EXPECTED_BRANCHES: + return [f"the {ENVIRONMENT} environment deploys from {sorted(branch_policies) or 'no branch'}, " + "not only main"], "" + return [], f"{ENVIRONMENT} deploys only from main" + + +def _get(url: str, token: str | None) -> Any: + if not url.startswith("https://"): + raise ValueError("refusing non-HTTPS URL") + headers = {"Accept": "application/vnd.github+json", "User-Agent": "samaydlette-preflight"} + if token: + headers["Authorization"] = f"Bearer {token}" + with urllib.request.urlopen(urllib.request.Request(url, headers=headers), timeout=15) as r: # noqa: S310 + return json.loads(r.read().decode()) + + +def read_environment(repo: str, token: str | None) -> tuple[str, dict[str, Any] | None, list[str] | None]: + """("ok"|"missing"|"unreadable", environment, branch policy names).""" + api = f"https://api.github.com/repos/{repo}/environments/{ENVIRONMENT}" + try: + env = _get(api, token) + except urllib.error.HTTPError as exc: + return ("missing" if exc.code == 404 else "unreadable"), None, None + except Exception: # noqa: BLE001 (any other failure: not observed) + return "unreadable", None, None + try: + pols = _get(f"{api}/deployment-branch-policies", token) + names = [p.get("name", "") for p in pols.get("branch_policies", [])] + except Exception: # noqa: BLE001 + names = None + return "ok", env, names + + +def evaluate(role_arn: str | None, env_state: str, env: dict[str, Any] | None, + branch_policies: list[str] | None) -> tuple[list[str], list[str]]: + """(problems, notes) for one run; pure, for tests.""" + problems = check_variable(role_arn) + notes = [] + if env_state == "unreadable": + notes.append(f"the {ENVIRONMENT} environment could not be read with the job token; not observed " + "(the incident-publisher job still fails the deploy if the role cannot be assumed from it)") + else: + p, note = check_environment(env if env_state == "ok" else None, branch_policies) + problems += p + if note: + notes.append(note) + return problems, notes + + +def main(argv: list[str] | None = None) -> int: + ap = argparse.ArgumentParser(description=__doc__, formatter_class=argparse.RawDescriptionHelpFormatter) + ap.add_argument("--fixture", default=None, + help="JSON {role_arn, env_state, environment, branch_policies} instead of live reads (tests)") + a = ap.parse_args(argv) + if a.fixture: + with open(a.fixture) as fh: + fx = json.load(fh) + problems, notes = evaluate(fx.get("role_arn"), fx["env_state"], fx.get("environment"), + fx.get("branch_policies")) + else: + state, env, pols = read_environment(os.environ.get("GITHUB_REPOSITORY", "sam-aydlette/samaydlette.com"), + os.environ.get("GITHUB_TOKEN")) + problems, notes = evaluate(os.environ.get("INCIDENT_REPORTS_ROLE_ARN"), state, env, pols) + for n in notes: + print(f"incident publisher preflight: {n}") + for p in problems: + print(f"::error::incident publisher preflight: {p}") + if not problems: + print("incident publisher preflight: role variable names the incident-reports role; ok") + return 1 if problems else 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/check-incident-role.py b/scripts/check-incident-role.py new file mode 100644 index 00000000..192c5241 --- /dev/null +++ b/scripts/check-incident-role.py @@ -0,0 +1,104 @@ +#!/usr/bin/env python3 +"""Deploy gate: the incident report publisher's role can actually be assumed. + +The IEC records describe a system whose unattended publisher +(.github/workflows/incident-reports.yml) assumes the role +infrastructure/bootstrap/incident-reports.tf creates. The deploy job runs this +before it builds the SDR, so a deploy whose publisher role does not work stops +before any record claiming it is published: + + 1. request the job's GitHub OIDC token (audience sts.amazonaws.com); + 2. call STS AssumeRoleWithWebIdentity for AWS_INCIDENT_REPORTS_ROLE_ARN; + 3. require success, and that the assumed role is + github-actions-incident-reports-oidc. + +The temporary credentials STS returns are discarded unused. Prints no token, +credential, ARN or account ID. Stdlib only. Exit 0 pass, 1 fail. +""" + +from __future__ import annotations + +import json +import os +import re +import sys +import urllib.error +import urllib.parse +import urllib.request +import xml.etree.ElementTree as ET + +EXPECTED_ROLE_NAME = "github-actions-incident-reports-oidc" +SESSION = "deploy-proves-incident-publisher" +STS_URL = "https://sts.{region}.amazonaws.com/" +REGION_RE = re.compile(r"^[a-z]{2}(-[a-z]+)+-[0-9]$") +ASSUMED_RE = re.compile(r"^arn:aws(-[a-z]+)*:sts::[0-9]{12}:assumed-role/([\w+=,.@-]+)/[\w+=,.@-]+$") + + +def _local(tag: str) -> str: + return tag.rsplit("}", 1)[-1] + + +def parse_sts(status: int, body: str) -> list[str]: + """Problems with an AssumeRoleWithWebIdentity response, or [].""" + try: + root = ET.fromstring(body) + except ET.ParseError: + return [f"STS returned HTTP {status} with a body that is not XML"] + found = {_local(e.tag): (e.text or "").strip() for e in root.iter()} + if status != 200 or "Error" in found: + code = re.sub(r"[^A-Za-z.]", "", found.get("Code", "unknown"))[:64] + return [f"STS refused the incident publisher role ({code}, HTTP {status}): the role or its trust for the " + f"deploy environment is missing; apply infrastructure/bootstrap/incident-reports.tf"] + m = ASSUMED_RE.match(found.get("Arn", "")) + if not m: + return ["STS answered without an assumed-role identity"] + if m.group(2) != EXPECTED_ROLE_NAME: + return [f"the assumed role is not {EXPECTED_ROLE_NAME}"] + return [] + + +def oidc_token(env=os.environ, opener=urllib.request.urlopen) -> str: + url, bearer = env.get("ACTIONS_ID_TOKEN_REQUEST_URL"), env.get("ACTIONS_ID_TOKEN_REQUEST_TOKEN") + if not url or not bearer: + raise RuntimeError("no GitHub OIDC token available (the job needs permissions: id-token: write)") + sep = "&" if "?" in url else "?" + req = urllib.request.Request(url + sep + "audience=sts.amazonaws.com", headers={"Authorization": f"bearer {bearer}"}) + with opener(req, timeout=30) as r: + return json.loads(r.read())["value"] + + +def assume(role_arn: str, token: str, region: str, opener=urllib.request.urlopen) -> tuple[int, str]: + data = urllib.parse.urlencode({"Action": "AssumeRoleWithWebIdentity", "Version": "2011-06-15", + "RoleArn": role_arn, "RoleSessionName": SESSION, "DurationSeconds": "900", + "WebIdentityToken": token}).encode() + req = urllib.request.Request(STS_URL.format(region=region), data=data, method="POST") + try: + with opener(req, timeout=30) as r: + return r.status, r.read().decode("utf-8", "replace") + except urllib.error.HTTPError as e: + return e.code, e.read().decode("utf-8", "replace") + + +def main(argv=None, env=os.environ, opener=urllib.request.urlopen) -> int: + role_arn = (env.get("INCIDENT_REPORTS_ROLE_ARN") or "").strip() + region = env.get("AWS_REGION") or "us-east-2" + if not REGION_RE.match(region): + # The region becomes part of the STS host name; never let it pick the host. + problems = ["AWS_REGION is not an AWS region name"] + elif not role_arn: + problems = ["AWS_INCIDENT_REPORTS_ROLE_ARN is not set"] + else: + try: + status, body = assume(role_arn, oidc_token(env, opener), region, opener) + problems = parse_sts(status, body) + except (RuntimeError, urllib.error.URLError, KeyError, ValueError) as e: + problems = [f"could not ask STS: {type(e).__name__}"] + for p in problems: + print(f"::error::incident publisher role: {p}") + if not problems: + print(f"incident publisher role: assumed {EXPECTED_ROLE_NAME} from the deploy job; credentials discarded") + return 1 if problems else 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/check-manual-settings.py b/scripts/check-manual-settings.py index 8f136723..3af2326d 100644 --- a/scripts/check-manual-settings.py +++ b/scripts/check-manual-settings.py @@ -114,6 +114,100 @@ def check_github() -> dict[str, Any]: return evaluate_github(environments, [p.get("name", "") for p in policies.get("branch_policies", [])], branch) +# --- repository settings the workflow token can read (SCG-ENH-CMP) -------------------- +# Compared on every deploy and every night with the guide's recommended values by +# scripts/check-secure-config.py. Settings no token the pipeline holds can read +# (the owner's two-factor setting and tokens; the repository's admin-only +# security and Actions settings) are not guessed: DEC-151 states the owner's. + +REPO_ROOT = os.path.dirname(os.path.dirname(os.path.abspath(__file__))) + + +def workflow_permissions(root: str = REPO_ROOT) -> dict[str, Any]: + """Every workflow's top-level token permissions, from the files. A workflow + that declares them never falls back to the repository's default, so the + repository-level Actions setting governs nothing here.""" + wf_dir = os.path.join(root, ".github", "workflows") + undeclared, write_all, writes = [], [], {} + for name in sorted(os.listdir(wf_dir)): + if not name.endswith((".yml", ".yaml")): + continue + with open(os.path.join(wf_dir, name)) as fh: + lines = fh.read().splitlines() + block, inside = [], False + for line in lines: + if line.startswith("permissions:"): + inside = True + block.append(line.split(":", 1)[1].split("#")[0].strip()) + continue + if inside: + if line and not line[0].isspace() and not line.startswith("#"): + break + block.append(line.split("#")[0].strip()) + if not inside: + undeclared.append(name) + continue + text = " ".join(b for b in block if b) + if "write-all" in text: + write_all.append(name) + granted = sorted(b.split(":")[0].strip() for b in block if b.endswith(": write")) + if granted: + writes[name] = granted + return {"undeclared": undeclared, "write_all": write_all, "top_level_write": writes} + + +def dependabot_updates(root: str = REPO_ROOT) -> list[str]: + """ecosystem:directory for every Dependabot version-update entry.""" + out, eco = [], None + with open(os.path.join(root, ".github", "dependabot.yml")) as fh: + for line in fh: + s = line.strip() + if s.startswith("- package-ecosystem:"): + eco = s.split(":", 1)[1].strip().strip("\"'") + elif s.startswith("directory:") and eco: + out.append(f"{eco}:{s.split(':', 1)[1].strip().strip(chr(34) + chr(39))}") + eco = None + return sorted(out) + + +def check_repository() -> dict[str, Any]: + """Facts for the repository settings, or {check: error text} where a read failed.""" + facts: dict[str, Any] = {} + errors: dict[str, str] = {} + api = f"https://api.github.com/repos/{REPO_SLUG}" + headers = {"Accept": "application/vnd.github+json"} + if os.environ.get("GITHUB_TOKEN"): + headers["Authorization"] = f"Bearer {os.environ['GITHUB_TOKEN']}" + try: + rulesets = _get_json(f"{api}/rulesets", headers) + facts["github-rulesets"] = {"rulesets": len(rulesets), + "with_bypass": sum(1 for r in rulesets if r.get("bypass_actors"))} + except Exception as exc: # noqa: BLE001 (not observed, reported as such) + errors["github-rulesets"] = f"rulesets could not be read ({type(exc).__name__})" + # Dependabot alerts are readable only with the token the detection feeds use; + # a read that succeeds means they are enabled (GitHub answers 403 when off). + token = os.environ.get("DEPENDABOT_TOKEN") + if token: + try: + _get_json(f"{api}/dependabot/alerts?per_page=1&state=open", + {"Accept": "application/vnd.github+json", "Authorization": f"Bearer {token}"}) + facts["github-dependabot-alerts"] = True + except Exception as exc: # noqa: BLE001 + code = getattr(exc, "code", None) + if code == 403: + facts["github-dependabot-alerts"] = False + else: + errors["github-dependabot-alerts"] = f"Dependabot alerts could not be read ({type(exc).__name__})" + else: + errors["github-dependabot-alerts"] = "no token that can read Dependabot alerts in this run" + try: + facts["github-workflow-permissions"] = workflow_permissions() + facts["github-dependabot-updates"] = dependabot_updates() + except OSError as exc: + errors["github-workflow-permissions"] = errors["github-dependabot-updates"] = type(exc).__name__ + return {"facts": facts, "errors": errors} + + # --------------------------------------------------------------------------- def evaluate_dnssec(answers: dict[str, dict[str, Any]]) -> dict[str, Any]: diff --git a/scripts/check-non-machine-vv.py b/scripts/check-non-machine-vv.py new file mode 100755 index 00000000..304dfe2d --- /dev/null +++ b/scripts/check-non-machine-vv.py @@ -0,0 +1,46 @@ +#!/usr/bin/env python3 +"""VDR-TFR-NMV: run the machine checks on every non-machine information resource +(scripts/_nonmachine.py) and write the verification and validation record. + + check-non-machine-vv.py [--register data/non-machine-resources.json] + [--decisions data/decisions.json] [--out vdr-non-machine-vv.json] + [--enforce] + +--out writes the status the nightly and the deploy publish. --enforce exits 1 +when any check fails (the deploy); without it the status is written with +status "lapsed" and verifiedAt at the epoch, so the published freshness window +turns the watchdog red at once (the nightly). +""" + +import argparse +import json +import sys +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _offering # noqa: E402 +import _decisions # noqa: E402 +import _nonmachine # noqa: E402 + + +def main(argv=None): + ap = argparse.ArgumentParser() + ap.add_argument("--register", default=None) + ap.add_argument("--decisions", default=None) + ap.add_argument("--out", default=None) + ap.add_argument("--enforce", action="store_true") + a = ap.parse_args(argv) + doc = _nonmachine.load(a.register) + reg = _decisions.load(a.decisions) + st = _nonmachine.status(doc, reg) + if a.out: + Path(a.out).write_text(json.dumps(_offering.stamp_fedramp_id(st), indent=2) + "\n", encoding="utf-8") + print(f"Non-machine V&V (VDR-TFR-NMV): {len(st['resources'])} resources, machine checks " + f"{', '.join(st['checks'])}: {st['status']}") + for p in st["problems"]: + print(f"::{'error' if a.enforce else 'warning'}::non-machine V&V: {p}", file=sys.stderr) + return 1 if (a.enforce and st["problems"]) else 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/check-package-maintainer.py b/scripts/check-package-maintainer.py new file mode 100644 index 00000000..f1e5d39a --- /dev/null +++ b/scripts/check-package-maintainer.py @@ -0,0 +1,142 @@ +#!/usr/bin/env python3 +"""Deploy preflight: the unattended certification package maintainer is in place. + +The rule records for package maintenance and the quarterly cycle (CPO-CSX-CPM, +CCM-OCR-AVL/SOR, CDS-CSO-HAD, SDR-CSX-KMT) describe the system as it is after +a successful deploy, so a deploy must not succeed without what they rely on. +Run early in the deploy job, before anything is applied or the SDR is built, +this fails the deploy unless: + + 1. the repository variable AWS_PACKAGE_MAINTENANCE_ROLE_ARN is set, and + 2. it names the role infrastructure/bootstrap/package-maintenance.tf creates + (github-actions-package-maintenance-oidc, an IAM role ARN), and + 3. the `package-maintenance` GitHub Environment exists and deploys only from + main (a custom branch policy naming exactly `main`). + +The same checks as the incident report publisher's preflight, for this role. + +Check 3 reads GitHub's API with the job token. A missing environment (404) +fails. If the token cannot read the environment at all (any other error), the +check is reported as not observed and the deploy continues on checks 1-2: the +deploy's later package-maintainer job assumes the role from that environment, +so a wrong environment still fails the deploy there. + +Whether the role itself works is proved later in the same run: the +`package-maintainer` job calls .github/workflows/package-maintenance.yml, +which assumes the role, publishes, and fails the deploy if it cannot. + +Prints no ARN or account ID. Exit 0 pass, 1 fail. +""" + +from __future__ import annotations + +import argparse +import json +import os +import re +import sys +import urllib.error +import urllib.request +from typing import Any + +EXPECTED_ROLE_NAME = "github-actions-package-maintenance-oidc" +ENVIRONMENT = "package-maintenance" +EXPECTED_BRANCHES = {"main"} +ROLE_ARN_RE = re.compile(r"^arn:aws(-[a-z]+)*:iam::[0-9]{12}:role/(?:[\w+=,.@-]+/)*([\w+=,.@-]+)$") + + +def check_variable(role_arn: str | None) -> list[str]: + if not role_arn or not role_arn.strip(): + return ["the repository variable AWS_PACKAGE_MAINTENANCE_ROLE_ARN is not set: apply " + "infrastructure/bootstrap/package-maintenance.tf and set it from the package_maintenance_role_arn output"] + m = ROLE_ARN_RE.match(role_arn.strip()) + if not m: + return ["AWS_PACKAGE_MAINTENANCE_ROLE_ARN is not an IAM role ARN"] + if m.group(2) != EXPECTED_ROLE_NAME: + return [f"AWS_PACKAGE_MAINTENANCE_ROLE_ARN names a role other than {EXPECTED_ROLE_NAME}"] + return [] + + +def check_environment(env: dict[str, Any] | None, branch_policies: list[str] | None) -> tuple[list[str], str]: + """(problems, note). env None = the environment does not exist.""" + if env is None: + return [f"the {ENVIRONMENT} GitHub Environment does not exist"], "" + policy = env.get("deployment_branch_policy") or {} + if not policy.get("custom_branch_policies") or policy.get("protected_branches"): + return [f"the {ENVIRONMENT} environment does not restrict deployments to a custom branch list"], "" + if branch_policies is None: + return [], "branch policies not observed" + if set(branch_policies) != EXPECTED_BRANCHES: + return [f"the {ENVIRONMENT} environment deploys from {sorted(branch_policies) or 'no branch'}, " + "not only main"], "" + return [], f"{ENVIRONMENT} deploys only from main" + + +def _get(url: str, token: str | None) -> Any: + if not url.startswith("https://"): + raise ValueError("refusing non-HTTPS URL") + headers = {"Accept": "application/vnd.github+json", "User-Agent": "samaydlette-preflight"} + if token: + headers["Authorization"] = f"Bearer {token}" + with urllib.request.urlopen(urllib.request.Request(url, headers=headers), timeout=15) as r: # noqa: S310 + return json.loads(r.read().decode()) + + +def read_environment(repo: str, token: str | None) -> tuple[str, dict[str, Any] | None, list[str] | None]: + """("ok"|"missing"|"unreadable", environment, branch policy names).""" + api = f"https://api.github.com/repos/{repo}/environments/{ENVIRONMENT}" + try: + env = _get(api, token) + except urllib.error.HTTPError as exc: + return ("missing" if exc.code == 404 else "unreadable"), None, None + except Exception: # noqa: BLE001 (any other failure: not observed) + return "unreadable", None, None + try: + pols = _get(f"{api}/deployment-branch-policies", token) + names = [p.get("name", "") for p in pols.get("branch_policies", [])] + except Exception: # noqa: BLE001 + names = None + return "ok", env, names + + +def evaluate(role_arn: str | None, env_state: str, env: dict[str, Any] | None, + branch_policies: list[str] | None) -> tuple[list[str], list[str]]: + """(problems, notes) for one run; pure, for tests.""" + problems = check_variable(role_arn) + notes = [] + if env_state == "unreadable": + notes.append(f"the {ENVIRONMENT} environment could not be read with the job token; not observed " + "(the package-maintainer job still fails the deploy if the role cannot be assumed from it)") + else: + p, note = check_environment(env if env_state == "ok" else None, branch_policies) + problems += p + if note: + notes.append(note) + return problems, notes + + +def main(argv: list[str] | None = None) -> int: + ap = argparse.ArgumentParser(description=__doc__, formatter_class=argparse.RawDescriptionHelpFormatter) + ap.add_argument("--fixture", default=None, + help="JSON {role_arn, env_state, environment, branch_policies} instead of live reads (tests)") + a = ap.parse_args(argv) + if a.fixture: + with open(a.fixture) as fh: + fx = json.load(fh) + problems, notes = evaluate(fx.get("role_arn"), fx["env_state"], fx.get("environment"), + fx.get("branch_policies")) + else: + state, env, pols = read_environment(os.environ.get("GITHUB_REPOSITORY", "sam-aydlette/samaydlette.com"), + os.environ.get("GITHUB_TOKEN")) + problems, notes = evaluate(os.environ.get("PACKAGE_MAINTENANCE_ROLE_ARN"), state, env, pols) + for n in notes: + print(f"package maintainer preflight: {n}") + for p in problems: + print(f"::error::package maintainer preflight: {p}") + if not problems: + print("package maintainer preflight: role variable names the package-maintenance role; ok") + return 1 if problems else 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/check-published-redaction.py b/scripts/check-published-redaction.py index 916cc870..dc45df58 100644 --- a/scripts/check-published-redaction.py +++ b/scripts/check-published-redaction.py @@ -1,5 +1,5 @@ #!/usr/bin/env python3 -"""Publication gate: no published artifact carries an AWS account ID. +"""Publication gate: no published artifact carries an AWS account ID, an IAM user name, a GitHub run ID or an email address not at the site's own domain. Run immediately before a workflow uploads to /.well-known/, over the directory the artifacts were built in: @@ -63,6 +63,15 @@ def violations(paths): where = "; ".join(re.sub(r"[0-9]", "#", text[max(0, m.start() - 30):m.start()]).replace("\n", " ") for m in hits[:3]) found.append(f"{p.name}: {len(hits)} account ID(s), e.g. after '{where}'") + runs = _redact.find_github_runs(text) + if runs: + found.append(f"{p.name}: {runs} GitHub run ID(s) or run URL(s)") + users = _redact.find_iam_users(text) + if users: + found.append(f"{p.name}: {users} IAM user name(s) after 'aws-iam-user::'") + emails = _redact.find_foreign_emails(text) + if emails: + found.append(f"{p.name}: {emails} email address(es) not at {_redact.SITE_DOMAIN}") return found @@ -86,12 +95,12 @@ def main(argv=None): return 2 bad = violations(paths) if bad: - print(f"::error::publication redaction gate: {len(bad)} artifact(s) carry an AWS account ID; " + print(f"::error::publication redaction gate: {len(bad)} artifact(s) carry an AWS account ID, IAM user name, GitHub run ID or outside email address; " "nothing is published (scripts/_redact.py)", file=sys.stderr) for b in bad: print(f" ✗ {b}", file=sys.stderr) return 1 - print(f"publication redaction gate OK: {len(paths)} artifact(s) carry no AWS account ID") + print(f"publication redaction gate OK: {len(paths)} artifact(s) carry no AWS account ID, IAM user name, GitHub run ID or outside email address") return 0 diff --git a/scripts/check-quarterly-review.py b/scripts/check-quarterly-review.py new file mode 100644 index 00000000..f7b53e35 --- /dev/null +++ b/scripts/check-quarterly-review.py @@ -0,0 +1,45 @@ +#!/usr/bin/env python3 +"""Fail when a Quarterly Review date has passed with no review published (CCM-QTR-MTG). + +The deploy and the evidence nightly run this against the published +/.well-known/quarterly-reviews.json. A review is held by package-maintenance.yml +on its date; from the day after, a review date with no review in the index +fails the run, so a missed review cannot pass quietly. + + check-quarterly-review.py --index quarterly-reviews.json # the published index + check-quarterly-review.py --no-index # nothing published yet (HTTP 404) +""" + +import argparse +import json +import sys +from datetime import date, datetime, timezone +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _ccm # noqa: E402 +import _quarterly_review as qr # noqa: E402 + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + ap.add_argument("--calendar", default=str(_ccm.CALENDAR_PATH)) + src = ap.add_mutually_exclusive_group(required=True) + src.add_argument("--index", help="the published quarterly-reviews.json") + src.add_argument("--no-index", action="store_true", help="the index is not published yet") + ap.add_argument("--today", default=None, help="YYYY-MM-DD (default: today, UTC)") + a = ap.parse_args(argv) + today = date.fromisoformat(a.today) if a.today else datetime.now(timezone.utc).date() + cal = _ccm.load(a.calendar, today) + index = {} if a.no_index else json.loads(Path(a.index).read_text()) + late = qr.missing(cal, index, today) + for issue, review in late: + print(f"::error::Quarterly Review of the report issued {issue} was due {review} and is not published") + if late: + return 1 + print(f"Quarterly Reviews: {len(qr.held(index))} held, none overdue; next {cal.next_review(today)}") + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/check-scheduled-review.py b/scripts/check-scheduled-review.py new file mode 100644 index 00000000..e1357357 --- /dev/null +++ b/scripts/check-scheduled-review.py @@ -0,0 +1,67 @@ +#!/usr/bin/env python3 +"""Fail when a scheduled review's due date has passed with no review published (DEC-195). + +The evidence nightly and the package maintainer (called by every deploy) run +this against the published, signature-verified index. From the day after a +due date with no review in the index, the run fails, so a missed review cannot +pass quietly. With --rules-of-behavior it also fails when the current rules of +behavior have no acknowledgement in the security-review index (PL-4). + + check-scheduled-review.py --review security-review --index security-reviews.json \ + [--rules-of-behavior docs/rules-of-behavior.md] + check-scheduled-review.py --review recovery-exercise --no-index # nothing published yet (HTTP 404) +""" + +import argparse +import hashlib +import importlib.util +import json +import sys +from datetime import date +from pathlib import Path + +HERE = Path(__file__).resolve().parent +sys.path.insert(0, str(HERE)) +import _scheduled_review as sr # noqa: E402 + + +def _security_review(): + spec = importlib.util.spec_from_file_location("hold_security_review_check", HERE / "hold-security-review.py") + m = importlib.util.module_from_spec(spec) + spec.loader.exec_module(m) + return m + + +def problems(key, index, today, rob_path=None): + rv = sr.review(key) + out = [f"{rv.title} due {d} is not published" for d in sr.missing(rv, index, today)] + if rob_path is not None: + sha = hashlib.sha256(Path(rob_path).read_bytes()).hexdigest() + if not _security_review().rob_acknowledged(index, sha): + out.append(f"the current rules of behavior ({sha[:12]}) have no acknowledgement in {rv.index}") + return out + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + ap.add_argument("--review", required=True, choices=sorted(sr.REVIEWS)) + src = ap.add_mutually_exclusive_group(required=True) + src.add_argument("--index", help="the published index") + src.add_argument("--no-index", action="store_true", help="the index is not published yet") + ap.add_argument("--rules-of-behavior", default=None, help="also require this document's acknowledgement") + ap.add_argument("--today", default=None, help="YYYY-MM-DD (default: today, UTC)") + a = ap.parse_args(argv) + today = date.fromisoformat(a.today) if a.today else sr.now_utc().date() + index = {} if a.no_index else json.loads(Path(a.index).read_text()) + found = problems(a.review, index, today, a.rules_of_behavior) + for p in found: + print(f"::error::{p}") + if found: + return 1 + rv = sr.review(a.review) + print(f"{rv.title}: {len(sr.held(rv, index))} held, none overdue; next due {sr.next_due(rv, today)}") + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/check-scn-deadlines.py b/scripts/check-scn-deadlines.py new file mode 100644 index 00000000..4e5f8e5c --- /dev/null +++ b/scripts/check-scn-deadlines.py @@ -0,0 +1,77 @@ +#!/usr/bin/env python3 +"""Scheduled SCN deadline check (SCN-ADP-NTF, SCN-TRF-NAF/NAV/UPD, SCN-CSO-EMG). + +Reads the published evaluation log and notification index and the register in +this checkout, and fails (exit 1) on anything late and still outstanding: + +- an adaptive, transformative or emergency change whose named record is not in + the register by its deadline (adaptive: 10 business days after merge, the + earliest it can have finished; emergency: 5; transformative: at merge); +- a notice a register record owes that is not yet published after its + deadline (a record merged but never deployed is not a notification); +- a transformative change whose service documentation is not updated within + 30 business days of finishing. + +A notice published late is not an open item: the index records it (onTime +false) for good. Exit 0 nothing overdue, 1 overdue, 2 cannot read an input. + + check-scn-deadlines.py # the published copies + check-scn-deadlines.py --index-file i.json --log-file l.json --today 2026-11-05 +""" + +import argparse +import json +import sys +import urllib.error +import urllib.request +from datetime import date, datetime, timezone +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _scn # noqa: E402 + + +def _read(path, url): + if path: + return json.loads(Path(path).read_text()) + try: + with urllib.request.urlopen(url, timeout=30) as r: # noqa: S310 (fixed https URL) + return json.loads(r.read()) + except urllib.error.HTTPError as exc: + if exc.code == 404: + return {} + raise + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__.split("\n")[0]) + ap.add_argument("--register", default=str(_scn.REGISTER)) + ap.add_argument("--index-file") + ap.add_argument("--log-file") + ap.add_argument("--today", help="ISO date (tests)") + a = ap.parse_args(argv) + today = date.fromisoformat(a.today) if a.today else datetime.now(timezone.utc).date() + try: + index = _read(a.index_file, _scn.BASE + _scn.INDEX_NAME + ".json") + log = _read(a.log_file, _scn.BASE + _scn.LOG_NAME + ".json") + header, rows = _scn.read_register(a.register) + except (OSError, ValueError, urllib.error.URLError) as exc: + print(f"::error::SCN deadline check cannot read its inputs: {exc}") + return 2 + errors = _scn.validate_register(header, rows) + if errors: + for e in errors: + print(f"::error::scn-register: {e}") + return 2 + late = _scn.overdue(rows, index, log.get("entries", []), today) + for item in late: + print(f"::error::SCN overdue: {item}") + if late: + return 1 + print(f"SCN deadlines: nothing overdue on {today} ({len(rows)} records, " + f"{len(log.get('entries', []))} evaluations)") + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/check-secure-config.py b/scripts/check-secure-config.py new file mode 100644 index 00000000..b8ad25f6 --- /dev/null +++ b/scripts/check-secure-config.py @@ -0,0 +1,405 @@ +#!/usr/bin/env python3 +"""Compare the live settings of the top-level and privileged accounts with the +Secure Configuration Guide's recommended defaults (SCG-ENH-CMP), and export +them as JSON (SCG-ENH-EXP): /.well-known/security-settings.json and .md. + +Runs in the deploy, before the Security Decision Record is built. Every read is +read-only (AWS CLI with the deploy role; GitHub's API with the run's token). A +setting either matches its recommended value, or differs and is covered by the +in-force decision the guide cites (an accepted deviation), or is attested by a +decision because no API exposes it to this run. Anything else, a deviation no +decision covers or a setting that could not be read, fails the deploy: the +published comparison is then never stale or partial. + +Published values are counts, booleans and policy values only: never an account +ID, an ARN, an IAM user or role name, or an email address. +""" + +import argparse +import importlib.util +import json +import subprocess +import sys +from datetime import datetime, timezone +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _offering # noqa: E402 +import _decisions # noqa: E402 + +REPO = Path(__file__).resolve().parent.parent +SOURCE = REPO / "data" / "secure-configuration.json" +SCHEMA = "security-settings/1" +REGION = "us-east-2" +OPERATOR_GROUP = "operators" +# The CI roles' names, as infrastructure/bootstrap names them (read, never published). +ROLES = {"role-trust-deploy": "github-actions-deploy-oidc", + "role-trust-plan": "github-actions-plan-oidc", + "role-trust-nightly": "github-actions-evidence-nightly-oidc", + "role-trust-maintenance": "github-actions-package-maintenance-oidc", + "role-trust-incident": "github-actions-incident-reports-oidc"} +# The unattended roles' write scope: {check id: (role, inline policy name)}. The +# value compared is the object keys each may put (the bucket part of the S3 ARN +# removed), so a grant the deploy's publishers need but bootstrap does not yet +# hold is a deviation, and the deploy stops before the SDR is built. +ROLE_SCOPES = {"role-scope-maintenance": ("github-actions-package-maintenance-oidc", "package-maintenance-publish")} +# The unattended roles' read grants compared action for action: {check id: (role, +# inline policy name)}. The nightly's audit-log review needs cloudtrail:LookupEvents; +# a deploy whose bootstrap lacks it stops before the SDR is built. +ROLE_READS = {"role-reads-nightly": ("github-actions-evidence-nightly-oidc", "evidence-nightly-audit-log-review")} +SUB_KEY = "token.actions.githubusercontent.com:sub" +READ_ONLY_MANAGED = {"ReadOnlyAccess", "SecurityAudit", "ViewOnlyAccess"} +READ_VERBS = ("Get", "List", "Describe", "Search", "BatchGet", "Lookup", "View") + + +class ReadError(Exception): + """A setting could not be read.""" + + +class AwsError(Exception): + def __init__(self, code): + super().__init__(code) + self.code = code + + +def aws(args): + """Run a read-only AWS CLI call; JSON out, or AwsError with the error code.""" + p = subprocess.run(["aws", *args, "--output", "json"], capture_output=True, text=True, timeout=60) + if p.returncode != 0: + code = "Unknown" + for word in ("NoSuchEntity", "AccessDenied", "AccessDeniedException", "NoSuchPublicAccessBlockConfiguration"): + if word in p.stderr: + code = word + break + raise AwsError(code) + return json.loads(p.stdout or "{}") + + +# --- comparison ----------------------------------------------------------------------- + +def matches(recommended, current): + """Recommended values are literals, {"at_least": n}, {"at_most": n}, lists + (compared as sets) or objects of those (every key must match).""" + if isinstance(recommended, dict): + if set(recommended) == {"at_least"}: + return isinstance(current, (int, float)) and not isinstance(current, bool) and current >= recommended["at_least"] + if set(recommended) == {"at_most"}: + return isinstance(current, (int, float)) and not isinstance(current, bool) and current <= recommended["at_most"] + return isinstance(current, dict) and all(k in current and matches(v, current[k]) for k, v in recommended.items()) + if isinstance(recommended, list): + return isinstance(current, list) and sorted(map(str, recommended)) == sorted(map(str, current)) + return type(recommended) is type(current) and recommended == current + + +def compare(src, current, in_force): + """One result per setting. `current` is {check id: value or ReadError}.""" + out = [] + for s in src["settings"]: + r = {"id": s["id"], "account": s["account"], "setting": s["setting"], "recommended": s["recommended"]} + if s["check"] == "attested": + dec = s.get("attested_by") + r.update(current=None, result="attested" if dec in in_force else "not-read", decision=dec) + else: + val = current.get(s["check"], ReadError("no reader for this check")) + if isinstance(val, ReadError): + r.update(current=None, result="not-read", detail=str(val)) + elif matches(s["recommended"], val): + r.update(current=val, result="matches") + elif s.get("accepted_deviation") in in_force: + r.update(current=val, result="accepted-deviation", decision=s["accepted_deviation"]) + else: + r.update(current=val, result="deviation") + out.append(r) + return out + + +# --- readers -------------------------------------------------------------------------- + +def _guard(fn): + try: + return fn() + except (AwsError, KeyError, TypeError, ValueError, subprocess.SubprocessError, FileNotFoundError) as exc: + return ReadError(f"{type(exc).__name__}: {getattr(exc, 'code', '')}".rstrip(": ")) + + +def _is_read_only(doc): + for st in doc.get("Statement", []) if isinstance(doc.get("Statement"), list) else [doc.get("Statement")]: + if not st or st.get("Effect") != "Allow": + continue + actions = st.get("Action", []) + for a in [actions] if isinstance(actions, str) else actions: + if a == "*" or ":" not in a: + return False + verb = a.split(":", 1)[1] + if not (verb == "GET" or verb.startswith(READ_VERBS)): + return False + return True + + +def _policy_doc(raw): + return json.loads(raw) if isinstance(raw, str) else raw + + +def read_aws(call, pool_id, now=None): + """{check id: value or ReadError} for every AWS-backed check.""" + out = {} + summary = _guard(lambda: call(["iam", "get-account-summary"])["SummaryMap"]) + virtual = _guard(lambda: [d.get("User", {}).get("Arn", "") for d in call( + ["iam", "list-virtual-mfa-devices", "--assignment-status", "Assigned"])["VirtualMFADevices"]]) + + def from_summary(key, conv): + return summary if isinstance(summary, ReadError) else conv(summary[key]) + + out["aws-root-mfa-enabled"] = from_summary("AccountMFAEnabled", lambda v: v == 1) + out["aws-root-access-keys"] = from_summary("AccountAccessKeysPresent", int) + if isinstance(virtual, ReadError) or isinstance(summary, ReadError): + out["aws-root-mfa-type"] = virtual if isinstance(virtual, ReadError) else summary + else: + out["aws-root-mfa-type"] = summary["AccountMFAEnabled"] == 1 and not any(a.endswith(":root") for a in virtual) + + def password_policy(): + try: + return call(["iam", "get-account-password-policy"])["PasswordPolicy"] + except AwsError as e: + if e.code == "NoSuchEntity": + return {} + raise + out["aws-account-password-policy"] = _guard(password_policy) + + def bpa(): + account = call(["sts", "get-caller-identity"])["Account"] + try: + return call(["s3control", "get-public-access-block", "--account-id", account])["PublicAccessBlockConfiguration"] + except AwsError as e: + if e.code == "NoSuchPublicAccessBlockConfiguration": + return {} + raise + out["aws-account-s3-bpa"] = _guard(bpa) + + def users(): + names = [u["UserName"] for u in call(["iam", "list-users"])["Users"]] + groups = {n: [g["GroupName"] for g in call(["iam", "list-groups-for-user", "--user-name", n])["Groups"]] + for n in names} + operators = [n for n in names if OPERATOR_GROUP in groups[n]] + if len(operators) != 1: + raise ValueError(f"expected one member of {OPERATOR_GROUP}, found {len(operators)}") + return names, groups, operators[0] + roster = _guard(users) + if isinstance(roster, ReadError): + for k in ("aws-iam-users", "operator-mfa-enabled", "operator-mfa-type", "operator-console-password", + "operator-access-keys"): + out[k] = roster + else: + names, groups, op = roster + out["aws-iam-users"] = _guard(lambda: sum(1 for n in names if n != op and not _user_read_only(call, n, groups[n]))) + out["operator-mfa-enabled"] = _guard(lambda: len(call(["iam", "list-mfa-devices", "--user-name", op])["MFADevices"]) > 0) + if isinstance(virtual, ReadError): + out["operator-mfa-type"] = virtual + else: + out["operator-mfa-type"] = _guard(lambda: len(call(["iam", "list-mfa-devices", "--user-name", op])["MFADevices"]) > 0 + and not any(a.endswith(f":user/{op}") for a in virtual)) + out["operator-console-password"] = _guard(lambda: _has_login_profile(call, op)) + out["operator-access-keys"] = _guard(lambda: _access_keys(call, op, now)) + + for check, role in ROLES.items(): + out[check] = _guard(lambda role=role: _trust_subjects(call(["iam", "get-role", "--role-name", role])["Role"])) + for check, (role, name) in ROLE_SCOPES.items(): + out[check] = _guard(lambda role=role, name=name: _put_keys(call( + ["iam", "get-role-policy", "--role-name", role, "--policy-name", name])["PolicyDocument"])) + + for check, (role, name) in ROLE_READS.items(): + out[check] = _guard(lambda role=role, name=name: _allowed_actions(call( + ["iam", "get-role-policy", "--role-name", role, "--policy-name", name])["PolicyDocument"])) + + def cognito(): + if not pool_id: + raise ValueError("no user pool id was given") + p = call(["cognito-idp", "describe-user-pool", "--region", REGION, "--user-pool-id", pool_id])["UserPool"] + pw = p["Policies"]["PasswordPolicy"] + return {"MfaConfiguration": p.get("MfaConfiguration"), + "AllowAdminCreateUserOnly": p["AdminCreateUserConfig"]["AllowAdminCreateUserOnly"], + **{k: pw.get(k) for k in ("MinimumLength", "RequireUppercase", "RequireLowercase", + "RequireNumbers", "RequireSymbols")}} + out["cognito-pool-policy"] = _guard(cognito) + return out + + +def _has_login_profile(call, user): + try: + call(["iam", "get-login-profile", "--user-name", user]) + return True + except AwsError as e: + if e.code == "NoSuchEntity": + return False + raise + + +def _user_read_only(call, user, groups): + """True when a user can only read: every attached policy is an AWS read-only + policy, every inline policy allows only read verbs, the same for its groups, + and it has no console password.""" + if _has_login_profile(call, user): + return False + managed = [p["PolicyName"] for p in call(["iam", "list-attached-user-policies", "--user-name", user])["AttachedPolicies"]] + inline = [_policy_doc(call(["iam", "get-user-policy", "--user-name", user, "--policy-name", n])["PolicyDocument"]) + for n in call(["iam", "list-user-policies", "--user-name", user])["PolicyNames"]] + for g in groups: + managed += [p["PolicyName"] for p in call(["iam", "list-attached-group-policies", "--group-name", g])["AttachedPolicies"]] + inline += [_policy_doc(call(["iam", "get-group-policy", "--group-name", g, "--policy-name", n])["PolicyDocument"]) + for n in call(["iam", "list-group-policies", "--group-name", g])["PolicyNames"]] + return all(m in READ_ONLY_MANAGED for m in managed) and all(_is_read_only(d) for d in inline) + + +def _access_keys(call, user, now=None): + now = now or datetime.now(timezone.utc) + keys = [k for k in call(["iam", "list-access-keys", "--user-name", user])["AccessKeyMetadata"] if k["Status"] == "Active"] + ages = [(now - datetime.fromisoformat(k["CreateDate"].replace("Z", "+00:00"))).days for k in keys] + return {"active": len(keys), "oldest_age_days": max(ages) if ages else 0} + + +def _put_keys(raw): + """The object keys an inline policy allows s3:PutObject on, without the bucket + (an S3 object ARN is arn:aws:s3:::/; it carries no account).""" + doc = _policy_doc(raw) + keys = [] + sts = doc.get("Statement", []) + for st in [sts] if isinstance(sts, dict) else sts: + actions = st.get("Action", []) + if st.get("Effect") != "Allow" or "s3:PutObject" not in ([actions] if isinstance(actions, str) else actions): + continue + res = st.get("Resource", []) + for r in [res] if isinstance(res, str) else res: + if not r.startswith("arn:aws:s3:::") or "/" not in r: + raise ValueError("a PutObject resource is not an S3 object ARN") + keys.append(r.split("/", 1)[1]) + return sorted(keys) + + +def _allowed_actions(raw): + """The actions an inline policy allows, sorted (no resources: no ARN, no account).""" + doc = _policy_doc(raw) + sts = doc.get("Statement", []) + out = set() + for st in [sts] if isinstance(sts, dict) else sts: + if st.get("Effect") == "Allow": + acts = st.get("Action", []) + out |= set([acts] if isinstance(acts, str) else acts) + return sorted(out) + + +def _trust_subjects(role): + doc = _policy_doc(role["AssumeRolePolicyDocument"]) + subs = [] + for st in doc.get("Statement", []): + for cond in (st.get("Condition") or {}).values(): + v = cond.get(SUB_KEY) + if v is not None: + subs += [v] if isinstance(v, str) else list(v) + return sorted(subs) + + +def read_github(github): + """{check id: value or ReadError} from check-manual-settings' github result.""" + if github.get("status") == "not_observed" or not github.get("facts"): + err = ReadError(github.get("detail") or "GitHub settings were not observed") + return {k: err for k in ("github-prod-reviewer", "github-nightly-branches", "github-main-checks")} + f = github["facts"] + return {"github-prod-reviewer": f["prod_required_reviewers"], + "github-nightly-branches": f["evidence_nightly_branches"], + "github-main-checks": {"required": f["main_required_checks"], "enforced_for": f["main_checks_enforced_for"]}} + + +REPOSITORY_CHECKS = ("github-rulesets", "github-dependabot-alerts", "github-workflow-permissions", + "github-dependabot-updates") + + +def read_repository(repo): + """{check id: value or ReadError} from check-manual-settings' repository read.""" + out = {k: ReadError(v) for k, v in (repo.get("errors") or {}).items()} + for k, v in (repo.get("facts") or {}).items(): + out[k] = {"undeclared": v["undeclared"], "write_all": v["write_all"]} \ + if k == "github-workflow-permissions" else v + return {k: out.get(k, ReadError("not read")) for k in REPOSITORY_CHECKS} + + +def _manual_settings(): + spec = importlib.util.spec_from_file_location("manual_settings", REPO / "scripts" / "check-manual-settings.py") + m = importlib.util.module_from_spec(spec) + spec.loader.exec_module(m) + return m + + +# --- output --------------------------------------------------------------------------- + +def build(src, results, now): + tally = {} + for r in results: + tally[r["result"]] = tally.get(r["result"], 0) + 1 + return {"schema": SCHEMA, "emitted_at": now.isoformat(timespec="seconds"), + "guide_version": src["version"], + "guide": "https://samaydlette.com/.well-known/secure-configuration-guide.json", + "description": "Every security setting of the top-level administrative and privileged accounts, read live " + "during the deploy and compared with the Secure Configuration Guide's recommended defaults " + "(SCG-ENH-CMP); this file is the machine-readable export of those settings (SCG-ENH-EXP).", + "summary": dict(sorted(tally.items())), "settings": results} + + +def failures(doc): + return [r for r in doc["settings"] if r["result"] in ("deviation", "not-read")] + + +def _v(v): + return json.dumps(v, sort_keys=True) + + +def render_markdown(doc): + out = ["# Security settings: live comparison with the Secure Configuration Guide", "", + f"- **Read:** {doc['emitted_at']} | **Guide version:** {doc['guide_version']}", + f"- **Summary:** {', '.join(f'{k} {v}' for k, v in doc['summary'].items())}", + f"- {doc['description']}", "", + "| Setting | Account | Recommended | Current | Result | Decision |", "|---|---|---|---|---|---|"] + for r in doc["settings"]: + cur = "—" if r["current"] is None else _v(r["current"]) + out.append(f"| `{r['id']}` | {r['account']} | `{_v(r['recommended'])}` | `{cur}` | {r['result']} | " + f"{r.get('decision', '—')} |") + out += ["", "---", "_Source of truth: the signed `security-settings.json`._"] + return "\n".join(out) + + +def main(argv=None): + ap = argparse.ArgumentParser(description="Compare live account settings with the Secure Configuration Guide.") + ap.add_argument("--source", default=str(SOURCE)) + ap.add_argument("--decisions", default=None) + ap.add_argument("--cognito-pool-id", default="") + ap.add_argument("--github-settings", default=None, + help="a check-manual-settings.py output to take the GitHub facts from (default: read GitHub now)") + ap.add_argument("--account", action="append", default=None, + help="compare only the settings of this account (repeatable); the nightly compares github-owner") + ap.add_argument("--output", default="security-settings.json") + ap.add_argument("--md-output", default="security-settings.md") + a = ap.parse_args(argv) + src = json.loads(Path(a.source).read_text()) + if a.account: + src = {**src, "settings": [s for s in src["settings"] if s["account"] in a.account]} + in_force = {r["id"] for r in _decisions.in_force(_decisions.load(a.decisions))} + if a.github_settings: + checks = json.loads(Path(a.github_settings).read_text())["checks"] + github = next((c for c in checks if c["id"] == "github_settings"), {"status": "not_observed"}) + else: + github = _manual_settings().check_github() + aws_needed = any(not s["account"].startswith("github") for s in src["settings"]) + current = {**(read_aws(aws, a.cognito_pool_id) if aws_needed else {}), **read_github(github), + **read_repository(_manual_settings().check_repository())} + doc = _offering.stamp_fedramp_id(build(src, compare(src, current, in_force), datetime.now(timezone.utc))) + Path(a.output).write_text(json.dumps(doc, indent=2) + "\n") + Path(a.md_output).write_text(render_markdown(doc) + "\n") + bad = failures(doc) + for r in bad: + print(f"::error::secure configuration: {r['id']} is {r['result']}" + + (f" ({r['detail']})" if r.get("detail") else "")) + print(f"security-settings: {doc['summary']}") + return 1 if bad else 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/check-wellknown-headers.py b/scripts/check-wellknown-headers.py new file mode 100644 index 00000000..4ea01002 --- /dev/null +++ b/scripts/check-wellknown-headers.py @@ -0,0 +1,83 @@ +#!/usr/bin/env python3 +"""The public JSON under /.well-known/ is servable to any program (FRC-CSO-JSN). + +Fetches each named artifact over HTTPS from the live site, as a browser on +another origin would (an Origin header), and fails unless the response carries: + + * Access-Control-Allow-Origin: * (CORS: a page on any origin can read it) + * a JSON Content-Type (application/json or application/*+json) + * X-Content-Type-Options: nosniff (the browser keeps that type) + +The headers come from the CloudFront response-headers policy for /.well-known/* +(infrastructure/bootstrap/cloudfront.tf), which the operator applies; this step +is what makes the deploy fail when that apply is missing. Read-only; stdlib only. + + check-wellknown-headers.py --site https://samaydlette.com ksi-signal.json ... + check-wellknown-headers.py --fixture headers.json (tests: {name: {header: value}}) +""" +import argparse +import json +import sys +import urllib.error +import urllib.request + +ORIGIN = "https://example.org" +DEFAULT_ARTIFACTS = ("ksi-signal.json", "security-decision-record.json", "trust-center.json", + "vdr-report.json", "certification-package-overview.json") + + +def problems(headers): + """[reason, ...] for one response's headers (names case-insensitive).""" + h = {k.lower(): (v or "").strip() for k, v in headers.items()} + out = [] + if h.get("access-control-allow-origin") != "*": + out.append(f"Access-Control-Allow-Origin is {h.get('access-control-allow-origin')!r}, not '*'") + ctype = h.get("content-type", "").split(";")[0].strip().lower() + if not (ctype == "application/json" or (ctype.startswith("application/") and ctype.endswith("+json"))): + out.append(f"Content-Type is {ctype or 'absent'!r}, not JSON") + if h.get("x-content-type-options", "").lower() != "nosniff": + out.append("X-Content-Type-Options: nosniff is absent") + return out + + +def fetch(url, timeout=20): + req = urllib.request.Request(url, method="GET", headers={"Origin": ORIGIN, "User-Agent": "samaydlette-header-check"}) + with urllib.request.urlopen(req, timeout=timeout) as resp: # nosec B310: fixed https URL + return dict(resp.headers.items()) + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + ap.add_argument("--site", default="https://samaydlette.com") + ap.add_argument("--fixture", default=None, help="JSON {artifact: {header: value}} instead of the network") + ap.add_argument("artifacts", nargs="*", default=None) + a = ap.parse_args(argv) + if not a.site.startswith("https://"): + print("::error::--site must be an https:// URL", file=sys.stderr) + return 2 + fixture = json.loads(open(a.fixture).read()) if a.fixture else None + names = a.artifacts or (sorted(fixture) if fixture is not None else list(DEFAULT_ARTIFACTS)) + failed = 0 + for name in names: + url = f"{a.site.rstrip('/')}/.well-known/{name}" + try: + headers = fixture[name] if fixture is not None else fetch(url) + except (urllib.error.URLError, OSError, KeyError) as exc: + print(f"::error::{url}: could not be read ({type(exc).__name__})", file=sys.stderr) + failed += 1 + continue + why = problems(headers) + for w in why: + print(f"::error::{url}: {w}", file=sys.stderr) + failed += bool(why) + if not why: + print(f"ok: {url} (CORS *, JSON, nosniff)") + if failed: + print(f"{failed} artifact(s) under /.well-known/ lack the required headers; the deploy does not proceed.", + file=sys.stderr) + return 1 + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/dast-cognito-token.py b/scripts/dast-cognito-token.py new file mode 100644 index 00000000..f20fdf8c --- /dev/null +++ b/scripts/dast-cognito-token.py @@ -0,0 +1,304 @@ +#!/usr/bin/env python3 +"""Sign the DAST scanner user in to the Silk Reeling Cognito pool; print its access token. + +The authenticated ZAP API scan (.github/workflows/zap-dast.yml) needs a real +Cognito access token, the same kind the SPA sends, so that the API Gateway JWT +authorizer and the app's own check let the scan through to the code behind +/api. The app client is a public PKCE client whose only password flow is +USER_SRP_AUTH, and the pool requires TOTP MFA for every user. This script does +exactly that sign-in, with the standard library only: + + InitiateAuth(USER_SRP_AUTH) -> PASSWORD_VERIFIER (SRP-6a proof of the password, + which never leaves the runner) -> SOFTWARE_TOKEN_MFA (an RFC 6238 code from the + scanner user's TOTP seed) -> access token + +No app-client flow is widened and no AWS credentials are used: InitiateAuth, +RespondToAuthChallenge, AssociateSoftwareToken and VerifySoftwareToken are +Cognito's public, unsigned user APIs. + + token (default) write the access token to --out, nothing else + enroll one time, run by the operator after creating the user: answer the + MFA_SETUP challenge by associating a new TOTP seed, verify it, and + write the seed to --out (then feed that file to `gh secret set`) + +Environment: SILK_DAST_USERNAME, SILK_DAST_PASSWORD, SILK_DAST_USER_POOL_ID, +SILK_DAST_TOTP_SECRET (token only), SILK_DAST_CLIENT_ID (else read from +--auth-config, the published /.well-known/silk-reeling-auth.json). + +Nothing secret is ever printed: the one value asked for goes to the --out file, +created readable only by its owner (0600); error messages carry Cognito's error +type and message only. +""" + +import argparse +import base64 +import hashlib +import hmac +import json +import os +import re +import secrets +import struct +import sys +import time +import urllib.error +import urllib.request +from datetime import datetime, timezone + +# RFC 5054 3072-bit group, the one Cognito's SRP uses; g = 2. This is a client +# for Cognito's fixed SRP protocol, not new cryptography: the PASSWORD_VERIFIER +# signature is checked against a reference vector cross-checked with pycognito +# (tests/test_dast_cognito_token.py), and the stdlib keeps the scan job free of +# third-party packages that would see the password. +N_HEX = ( + "FFFFFFFFFFFFFFFFC90FDAA22168C234C4C6628B80DC1CD129024E088A67CC74020BBEA63B139B22514A08798E3404DD" + "EF9519B3CD3A431B302B0A6DF25F14374FE1356D6D51C245E485B576625E7EC6F44C42E9A637ED6B0BFF5CB6F406B7ED" + "EE386BFB5A899FA5AE9F24117C4B1FE649286651ECE45B3DC2007CB8A163BF0598DA48361C55D39A69163FA8FD24CF5F" + "83655D23DCA3AD961C62F356208552BB9ED529077096966D670C354E4ABC9804F1746C08CA18217C32905E462E36CE3B" + "E39E772C180E86039B2783A2EC07A28FB5C55DF06F4C52C9DE2BCBF6955817183995497CEA956AE515D2261898FA0510" + "15728E5A8AAAC42DAD33170D04507A33A85521ABDF1CBA64ECFB850458DBEF0A8AEA71575D060C7DB3970F85A6E1E4C7" + "ABF5AE8CDB0933D71E8C94E04A25619DCEE3D2261AD2EE6BF12FFA06D98A0864D87602733EC86A64521F2B18177B200C" + "BBE117577A615D6C770988C0BAD946E208E24FA074E5AB3143DB5BFCE0FD108E4B82D120A93AD2CAFFFFFFFFFFFFFFFF" +) +N = int(N_HEX, 16) +G = 2 +INFO = b"Caldera Derived Key\x01" +REGION_RE = re.compile(r"^([a-z]{2}(?:-[a-z]+)+-\d)_[A-Za-z0-9]+$") + + +class AuthError(Exception): + """A sign-in step failed. The text never carries a password, seed or token.""" + + +# ----------------------------------------------------------------------------- SRP-6a + + +def _hash_hex(data: bytes) -> str: + return hashlib.sha256(data).hexdigest().rjust(64, "0") + + +def _hex_hash(hex_string: str) -> str: + return _hash_hex(bytes.fromhex(hex_string)) + + +def pad_hex(value: "int | str") -> str: + """Cognito's padding: an even number of digits, and a leading 00 when the + high bit would make the value read as negative.""" + h = value if isinstance(value, str) else format(value, "x") + if len(h) % 2 == 1: + h = "0" + h + elif h[0] in "89abcdefABCDEF": + h = "00" + h + return h + + +K = int(_hex_hash("00" + N_HEX + "0" + format(G, "x")), 16) + + +def small_a() -> int: + return int.from_bytes(secrets.token_bytes(128), "big") % N + + +def large_a(a: int) -> int: + big_a = pow(G, a, N) + if big_a % N == 0: + raise AuthError("SRP: A mod N is zero") + return big_a + + +def _hkdf(ikm: bytes, salt: bytes) -> bytes: + prk = hmac.new(salt, ikm, hashlib.sha256).digest() + return hmac.new(prk, INFO, hashlib.sha256).digest()[:16] + + +def password_key(pool_id: str, user_id: str, password: str, big_a: int, a: int, big_b: int, salt_hex: str) -> bytes: + if big_b % N == 0: + raise AuthError("SRP: server B mod N is zero") + u = int(_hex_hash(pad_hex(big_a) + pad_hex(big_b)), 16) + if u == 0: + raise AuthError("SRP: u is zero") + pool_name = pool_id.split("_", 1)[1] + up_hash = _hash_hex(f"{pool_name}{user_id}:{password}".encode("utf-8")) + x = int(_hex_hash(pad_hex(salt_hex) + up_hash), 16) + s = pow(big_b - K * pow(G, x, N), a + u * x, N) + return _hkdf(bytes.fromhex(pad_hex(s)), bytes.fromhex(pad_hex(format(u, "x")))) + + +_DAYS = ("Mon", "Tue", "Wed", "Thu", "Fri", "Sat", "Sun") +_MONTHS = ("Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov", "Dec") + + +def cognito_timestamp(now: datetime) -> str: + """'Thu Nov 5 07:03:09 UTC 2026', in UTC, English names whatever the locale, + the day unpadded: the form Cognito signs.""" + t = now.astimezone(timezone.utc) + return (f"{_DAYS[t.weekday()]} {_MONTHS[t.month - 1]} {t.day:d} " + f"{t.hour:02d}:{t.minute:02d}:{t.second:02d} UTC {t.year:d}") + + +def password_verifier(pool_id: str, password: str, params: dict, a: int, big_a: int, now: datetime) -> dict: + """The PASSWORD_VERIFIER challenge responses for Cognito's challenge parameters.""" + user_id = params["USER_ID_FOR_SRP"] + key = password_key(pool_id, user_id, password, big_a, a, int(params["SRP_B"], 16), params["SALT"]) + stamp = cognito_timestamp(now) + msg = (pool_id.split("_", 1)[1].encode("utf-8") + user_id.encode("utf-8") + + base64.standard_b64decode(params["SECRET_BLOCK"]) + stamp.encode("utf-8")) + sig = base64.standard_b64encode(hmac.new(key, msg, hashlib.sha256).digest()).decode("ascii") + return {"TIMESTAMP": stamp, "USERNAME": user_id, "PASSWORD_CLAIM_SECRET_BLOCK": params["SECRET_BLOCK"], + "PASSWORD_CLAIM_SIGNATURE": sig} + + +# ----------------------------------------------------------------------------- TOTP + + +def totp(seed_b32: str, at: float, digits: int = 6, step: int = 30) -> str: + """RFC 6238 (HMAC-SHA1), the code an authenticator app shows. SHA-1 here is + what Cognito's software-token MFA (and every authenticator app) computes; + it is an HMAC, where SHA-1's collision weakness does not apply.""" + seed = seed_b32.strip().replace(" ", "").upper() + key = base64.b32decode(seed + "=" * (-len(seed) % 8)) + mac = hmac.new(key, struct.pack(">Q", int(at) // step), hashlib.sha1).digest() + off = mac[-1] & 0x0F + code = (struct.unpack(">I", mac[off:off + 4])[0] & 0x7FFFFFFF) % (10 ** digits) + return str(code).rjust(digits, "0") + + +# ----------------------------------------------------------------------------- Cognito + + +def region_of(pool_id: str) -> str: + m = REGION_RE.match(pool_id or "") + if not m: + raise AuthError("SILK_DAST_USER_POOL_ID is not a Cognito user pool id") + return m.group(1) + + +def call(region: str, action: str, body: dict) -> dict: + req = urllib.request.Request( + f"https://cognito-idp.{region}.amazonaws.com/", data=json.dumps(body).encode("utf-8"), method="POST", + headers={"Content-Type": "application/x-amz-json-1.1", + "X-Amz-Target": f"AWSCognitoIdentityProviderService.{action}"}) + try: + with urllib.request.urlopen(req, timeout=30) as resp: # noqa: S310 (fixed https endpoint) + return json.loads(resp.read().decode("utf-8")) + except urllib.error.HTTPError as exc: + try: + err = json.loads(exc.read().decode("utf-8")) + except (ValueError, UnicodeDecodeError): + err = {} + kind = str(err.get("__type") or exc.code).split("#")[-1] + raise AuthError(f"{action}: {kind}: {str(err.get('message') or '')[:200]}") from None + except urllib.error.URLError as exc: + raise AuthError(f"{action}: {type(exc.reason).__name__}") from None + + +def sign_in(pool_id: str, client_id: str, username: str, password: str, now=None) -> dict: + """Through PASSWORD_VERIFIER; returns the next Cognito response.""" + region = region_of(pool_id) + a = small_a() + big_a = large_a(a) + r = call(region, "InitiateAuth", {"AuthFlow": "USER_SRP_AUTH", "ClientId": client_id, + "AuthParameters": {"USERNAME": username, "SRP_A": format(big_a, "x")}}) + if r.get("ChallengeName") != "PASSWORD_VERIFIER": + raise AuthError(f"InitiateAuth: expected PASSWORD_VERIFIER, got {r.get('ChallengeName')}") + params = r.get("ChallengeParameters") or {} + responses = password_verifier(pool_id, password, params, a, big_a, now or datetime.now(timezone.utc)) + body = {"ChallengeName": "PASSWORD_VERIFIER", "ClientId": client_id, "ChallengeResponses": responses} + if r.get("Session"): + body["Session"] = r["Session"] + nxt = call(region, "RespondToAuthChallenge", body) + nxt["_user_id"] = params["USER_ID_FOR_SRP"] + return nxt + + +def access_token(pool_id: str, client_id: str, username: str, password: str, seed: str) -> str: + region = region_of(pool_id) + r = sign_in(pool_id, client_id, username, password) + if r.get("ChallengeName") == "SOFTWARE_TOKEN_MFA": + r = call(region, "RespondToAuthChallenge", { + "ChallengeName": "SOFTWARE_TOKEN_MFA", "ClientId": client_id, "Session": r.get("Session"), + "ChallengeResponses": {"USERNAME": r["_user_id"], "SOFTWARE_TOKEN_MFA_CODE": totp(seed, time.time())}}) + elif r.get("ChallengeName"): + raise AuthError(f"unexpected challenge {r['ChallengeName']} (run `enroll` once, or set the " + "password permanent with admin-set-user-password --permanent)") + token = (r.get("AuthenticationResult") or {}).get("AccessToken") + if not token: + raise AuthError("Cognito returned no access token") + return token + + +def enroll(pool_id: str, client_id: str, username: str, password: str) -> str: + """Answer MFA_SETUP with a new TOTP seed; returns the seed.""" + region = region_of(pool_id) + r = sign_in(pool_id, client_id, username, password) + if r.get("ChallengeName") != "MFA_SETUP": + raise AuthError(f"expected MFA_SETUP, got {r.get('ChallengeName') or 'tokens'} (already enrolled?)") + assoc = call(region, "AssociateSoftwareToken", {"Session": r["Session"]}) + seed = assoc["SecretCode"] + ver = call(region, "VerifySoftwareToken", {"Session": assoc["Session"], "UserCode": totp(seed, time.time()), + "FriendlyDeviceName": "zap-dast"}) + if ver.get("Status") != "SUCCESS": + raise AuthError("VerifySoftwareToken did not succeed") + done = call(region, "RespondToAuthChallenge", {"ChallengeName": "MFA_SETUP", "ClientId": client_id, + "Session": ver["Session"], + "ChallengeResponses": {"USERNAME": r["_user_id"]}}) + if not (done.get("AuthenticationResult") or {}).get("AccessToken"): + raise AuthError("MFA_SETUP completed without tokens") + return seed + + +def client_id_from(path: str) -> str: + with open(path, encoding="utf-8") as fh: + cfg = json.load(fh) + cid = cfg.get("clientId") if isinstance(cfg, dict) else None + if not isinstance(cid, str) or not re.fullmatch(r"[A-Za-z0-9]{1,128}", cid): + raise AuthError(f"{path} carries no app client id") + return cid + + +def main(argv=None) -> int: + ap = argparse.ArgumentParser(description=__doc__, formatter_class=argparse.RawDescriptionHelpFormatter) + ap.add_argument("mode", nargs="?", choices=("token", "enroll"), default="token") + ap.add_argument("--auth-config", help="the published silk-reeling-auth.json (for the app client id)") + ap.add_argument("--out", required=True, + help="file to write the token (or, for enroll, the seed) to, readable only by its owner; " + "the secret never goes to stdout, where a log could capture it") + args = ap.parse_args(argv) + env = os.environ + need = ["SILK_DAST_USERNAME", "SILK_DAST_PASSWORD", "SILK_DAST_USER_POOL_ID"] + if args.mode == "token": + need.append("SILK_DAST_TOTP_SECRET") + missing = [k for k in need if not env.get(k)] + if missing: + print(f"::error::not set: {', '.join(missing)}", file=sys.stderr) + return 2 + try: + cid = env.get("SILK_DAST_CLIENT_ID") or (client_id_from(args.auth_config) if args.auth_config else "") + if not cid: + raise AuthError("no app client id (SILK_DAST_CLIENT_ID or --auth-config)") + if args.mode == "enroll": + out = enroll(env["SILK_DAST_USER_POOL_ID"], cid, env["SILK_DAST_USERNAME"], env["SILK_DAST_PASSWORD"]) + else: + out = access_token(env["SILK_DAST_USER_POOL_ID"], cid, env["SILK_DAST_USERNAME"], + env["SILK_DAST_PASSWORD"], env["SILK_DAST_TOTP_SECRET"]) + except (AuthError, KeyError, OSError, ValueError) as exc: + detail = str(exc) if isinstance(exc, AuthError) else type(exc).__name__ + print(f"::error::Cognito sign-in failed: {detail.replace('::', ':')}", file=sys.stderr) + return 1 + write_secret(args.out, out) + return 0 + + +def write_secret(path, value): + """Write a secret to a file readable only by its owner (0600, also when it + already existed), never to stdout.""" + fd = os.open(path, os.O_WRONLY | os.O_CREAT | os.O_TRUNC, 0o600) + try: + os.fchmod(fd, 0o600) + os.write(fd, value.encode("utf-8")) + finally: + os.close(fd) + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/deliver-incident-reports.py b/scripts/deliver-incident-reports.py new file mode 100644 index 00000000..4726cd17 --- /dev/null +++ b/scripts/deliver-incident-reports.py @@ -0,0 +1,130 @@ +#!/usr/bin/env python3 +"""Deliver every incident report to a SIMULATED FedRAMP and agency recipient. + +IEC-CSO-IIR/OIR/FIR ask that each report reach FedRAMP and every affected +agency; IEC-CSO-AIR asks that this be automated. This proof of concept has no +FedRAMP certification and no agency customer, so by the operator's decision the +recipients are simulated and NOTHING IS SENT. What is real is the mechanism: +every report the incident log lists is read back, checked against the sha256 +the log published for it and against FedRAMP's incident report schema, and +handed to each recipient, whose (simulated) receipt is the hash it received. + +Any failure exits 1 and writes nothing, which stops the deploy (and the +unattended publisher) before anything is published: + - a report the log lists is missing, or its bytes differ from the log's sha256 + - a report does not validate against FedRAMP's incident report schema + - a report file in the directory is not listed in the log + - a reportable incident has a report with no FedRAMP or no agency recipient + +On success it writes incident-deliveries.json, the delivery log, labelled as a +simulation, for the workflow to sign and publish under /.well-known/. +""" + +from __future__ import annotations + +import argparse +import hashlib +import json +import sys +from datetime import datetime, timezone +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _engagement # noqa: E402 +import _offering # noqa: E402 +import _fedramp_schema as fs # noqa: E402 + +FEDRAMP = "FedRAMP Incident Desk (simulated): accepts every report, replies to none, and has never heard of this system" +DEFAULT_AGENCY = "Department of Hypothetical Affairs (simulated): this system has no agency customer" +NOTICE = ("SIMULATION. Every incident report below was 'delivered' to simulated recipients: nothing was sent to " + "FedRAMP or to any agency, and no inbox anywhere received anything. The delivery mechanism is real and runs " + "on every deploy and every unattended publish: each report is read back, checked against the sha256 in " + "incident-reports.json and against FedRAMP's incident report schema, and its receipt is that hash. A " + "delivery that fails stops publication. Real recipients would need an operator decision and a FedRAMP " + "certification, neither of which exists.") + + +def sha256(path: Path) -> str: + return hashlib.sha256(path.read_bytes()).hexdigest() + + +def deliver(log: dict, report_dir: Path, now: str | None = None, registry=None) -> tuple[dict | None, list[str]]: + """(delivery log, problems). The delivery log is None when there are problems.""" + problems: list[str] = [] + deliveries = [] + listed = set() + for inc in log.get("incidents", []): + reports = inc.get("reports") or [] + if reports and not (inc.get("evaluation") or {}).get("reportable"): + problems.append(f"{inc.get('id')}: reports issued for an incident evaluated not reportable") + for r in reports: + name = r.get("file") or "" + listed.add(name) + path = report_dir / name + if "/" in name or not name.startswith("incident-INC-") or not path.is_file(): + problems.append(f"{inc.get('id')}: report {name!r} is listed but missing") + continue + got = sha256(path) + if got != r.get("sha256"): + problems.append(f"{name}: bytes differ from the sha256 the incident log publishes") + continue + doc = json.loads(path.read_text()) + errors = fs.validate(doc, "incident", registry) + if errors: + problems.append(f"{name}: does not validate against FedRAMP's incident report schema ({errors[0]})") + continue + agencies = [a for a in (doc.get("affectedAgencies") or []) if isinstance(a, str) and a.strip()] + recipients: list[dict[str, object]] = [{"recipient": FEDRAMP, "kind": "fedramp"}] + recipients += [{"recipient": f"{a} (simulated)", "kind": "agency"} for a in agencies] or \ + [{"recipient": DEFAULT_AGENCY, "kind": "agency"}] + for rc in recipients: + rc.update(simulated=True, transport="none: simulated, nothing sent", receipt_sha256=got, + result="accepted (simulated)") + kinds = {rc["kind"] for rc in recipients} + if kinds != {"fedramp", "agency"}: + problems.append(f"{name}: no FedRAMP and agency recipient") + deliveries.append({"incident": inc.get("id"), "exercise": bool(inc.get("exercise")), + "report_type": r.get("type"), "file": name, "sha256": got, + "issued_at": r.get("issued_at"), "recipients": recipients}) + for path in sorted(report_dir.glob("incident-INC-*.json")): + if path.name not in listed: + problems.append(f"{path.name}: a report file the incident log does not list") + if problems: + return None, problems + return { + "schema": "incident-deliveries/1", + "simulation": True, + "notice": NOTICE, + "engagement": _engagement.STATEMENT, + "emitted_at": now or datetime.now(timezone.utc).isoformat(), + "generator": "scripts/deliver-incident-reports.py", + "incident_log": "https://samaydlette.com/.well-known/incident-reports.json", + "incident_log_emitted_at": log.get("emitted_at"), + "summary": {"reports_delivered": len(deliveries), + "recipients_reached": sum(len(d["recipients"]) for d in deliveries), + "messages_actually_sent": 0}, + "deliveries": deliveries, + }, [] + + +def main(argv=None) -> int: + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + ap.add_argument("--dir", type=Path, default=Path("."), help="where incident-reports.json and the reports are") + ap.add_argument("--output", type=Path, default=None) + a = ap.parse_args(argv) + log = json.loads((a.dir / "incident-reports.json").read_text()) + out, problems = deliver(log, a.dir) + for p in problems: + print(f"::error::incident report delivery (simulated): {p}") + if problems or out is None: + print(f"incident report delivery: {len(problems)} problem(s); nothing delivered, nothing written") + return 1 + target = a.output or (a.dir / "incident-deliveries.json") + target.write_text(json.dumps(_offering.stamp_fedramp_id(out), indent=2) + "\n") + print(f"incident report delivery (SIMULATED, nothing sent): {out['summary']['reports_delivered']} report(s) to " + f"{out['summary']['recipients_reached']} simulated recipient(s); wrote {target}") + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/deploy.sh b/scripts/deploy.sh deleted file mode 100755 index 17ca3545..00000000 --- a/scripts/deploy.sh +++ /dev/null @@ -1,246 +0,0 @@ -#!/bin/bash -# deploy.sh - Complete deployment script with OPA compliance - -set -e - -echo "=== Website Deployment with OPA Compliance ===" -echo "Domain: ${DOMAIN_NAME:-samaydlette.com}" -echo "Environment: ${ENVIRONMENT:-prod}" -echo - -# Function to check prerequisites -check_prerequisites() { - echo "Checking prerequisites..." - - # Check AWS CLI - if ! command -v aws &> /dev/null; then - echo "Error: AWS CLI is not installed." - exit 1 - fi - - # Check AWS credentials - if ! aws sts get-caller-identity &> /dev/null; then - echo "Error: AWS credentials not configured." - echo "Run: aws configure" - exit 1 - fi - - # Check Terraform - if ! command -v terraform &> /dev/null; then - echo "Error: Terraform is not installed." - exit 1 - fi - - # Check OPA - if ! command -v opa &> /dev/null; then - echo "Installing OPA..." - curl -L -o opa https://openpolicyagent.org/downloads/v1.18.2/opa_linux_amd64_static - echo "9903e5125ac281104f2c4b7371d10cc3b74a98933743fcbfc174f9bf0ab20de8 opa" | sha256sum -c - - chmod 755 ./opa - sudo mv opa /usr/local/bin - echo "OPA installed successfully." - fi - - # Check if terraform.tfvars exists - if [ ! -f "terraform.tfvars" ]; then - echo "Error: terraform.tfvars not found." - echo "Copy terraform.tfvars.example to terraform.tfvars and customize it." - exit 1 - fi - - echo "✅ Prerequisites check passed" -} - -# Function to prepare Lambda package -prepare_lambda() { - echo "Preparing Lambda function..." - - cd lambda - - # Install dependencies - if [ -f "package.json" ]; then - echo "Installing Node.js dependencies..." - npm ci --omit=dev - fi - - # The .rego sources are intentionally NOT copied here. The Lambda executes - # policy.wasm — compiled from infrastructure/policy/ by the CI workflow and - # placed in lambda/ before this zip is built. Bundling the .rego source in - # the deployed zip would be dead weight. - - cd .. - - echo "✅ Lambda function prepared" -} - -# Function to create SSL certificate if needed -setup_ssl_certificate() { - local domain_name=$1 - - echo "Checking SSL certificate configuration..." - - # Check if we should create a certificate - if grep -q "create_certificate.*=.*true" terraform.tfvars; then - echo "✅ Certificate will be auto-created in us-east-1" - return 0 - fi - - # Check if certificate ARN is provided - if grep -q "ssl_certificate_arn.*=.*arn:aws:acm" terraform.tfvars; then - echo "✅ SSL certificate ARN found in terraform.tfvars" - return 0 - fi - - echo "SSL certificate configuration incomplete." - echo "Choose an option:" - echo "1. Auto-create certificate (recommended)" - echo "2. Provide existing certificate ARN" - read -p "Enter choice (1 or 2): " choice - - case $choice in - 1) - sed -i 's/create_certificate = false/create_certificate = true/' terraform.tfvars - echo "✅ Configured to auto-create certificate" - ;; - 2) - echo "Please manually add your certificate ARN to terraform.tfvars" - echo "Certificate must be in us-east-1 region for CloudFront" - exit 1 - ;; - *) - echo "Invalid choice" - exit 1 - ;; - esac -} - -# Function to sync website files -sync_website_files() { - local bucket_name=$1 - - echo "Syncing website files to S3..." - - # Check if website files exist - if [ ! -f "index.html" ]; then - echo "Warning: index.html not found in current directory" - echo "Make sure you're running this from your website root directory" - fi - - # Sync files to S3 - aws s3 sync . s3://"$bucket_name"/ \ - --exclude "*.tf" \ - --exclude "*.tfvars*" \ - --exclude "*.tfstate*" \ - --exclude ".terraform/*" \ - --exclude "lambda/*" \ - --exclude "*.sh" \ - --exclude "*.rego" \ - --exclude "*.json" \ - --exclude ".git/*" \ - --exclude "README.md" \ - --delete - - echo "✅ Website files synced" -} - -# Function to run compliance check -run_compliance_check() { - echo "Running post-deployment compliance check..." - - # Get Lambda function name from Terraform output - local lambda_function=$(terraform output -raw lambda_function_name 2>/dev/null || echo "") - - if [ -n "$lambda_function" ]; then - echo "Invoking compliance check Lambda function..." - aws lambda invoke \ - --function-name "$lambda_function" \ - --payload '{}' \ - compliance-result.json - - echo "Compliance check results:" - cat compliance-result.json | jq '.' - - # Check if compliant - local compliant=$(cat compliance-result.json | jq -r '.body' | jq -r '.compliant // false') - if [ "$compliant" = "true" ]; then - echo "✅ Post-deployment compliance check passed" - else - echo "❌ Post-deployment compliance violations found" - echo "Check the compliance report for details" - fi - else - echo "Warning: Could not find Lambda function for compliance check" - fi -} - -# Function to invalidate CloudFront cache -invalidate_cloudfront() { - echo "Invalidating CloudFront cache..." - - local distribution_id=$(terraform output -raw cloudfront_distribution_id 2>/dev/null || echo "") - - if [ -n "$distribution_id" ]; then - aws cloudfront create-invalidation \ - --distribution-id "$distribution_id" \ - --paths "/*" - echo "✅ CloudFront cache invalidated" - else - echo "Warning: Could not find CloudFront distribution ID" - fi -} - -# Main deployment flow -main() { - local domain_name=${DOMAIN_NAME:-samaydlette.com} - - check_prerequisites - setup_ssl_certificate "$domain_name" - prepare_lambda - - echo "Running Terraform plan with OPA compliance check..." - bash terraform-plan.sh - - echo - read -p "Deploy the infrastructure? (y/N): " -n 1 -r - echo - if [[ $REPLY =~ ^[Yy]$ ]]; then - echo "Deploying infrastructure..." - terraform apply tfplan - - # Get bucket name from output - local bucket_name=$(terraform output -raw s3_bucket_name) - - sync_website_files "$bucket_name" - invalidate_cloudfront - run_compliance_check - - echo - echo "=== Deployment Complete ===" - echo "Website URL: $(terraform output -json website_urls | jq -r '.domain // .cloudfront')" - echo "S3 Bucket: $bucket_name" - echo "CloudFront Distribution: $(terraform output -raw cloudfront_distribution_id)" - - if terraform output route53_name_servers &> /dev/null; then - echo - echo "DNS Configuration:" - echo "Update your domain registrar to use these name servers:" - terraform output -json route53_name_servers | jq -r '.[]' - fi - - echo - echo "✅ Deployment successful!" - else - echo "Deployment cancelled." - fi -} - -# Cleanup function -cleanup() { - echo "Cleaning up temporary files..." - rm -f tfplan tfplan.json opa-input.json compliance-result.json -} - -# Set trap for cleanup -trap cleanup EXIT - -# Run main function diff --git a/scripts/detection-gate.py b/scripts/detection-gate.py index 383e6232..b708b200 100644 --- a/scripts/detection-gate.py +++ b/scripts/detection-gate.py @@ -14,6 +14,9 @@ previous-vdr the published VDR (the first-detected ledger): an object with findings[] checkov Checkov SARIF: runs[] present, not the old empty "fallback" document tfsec tfsec JSON: an object with a results key + codeql CodeQL code-scanning alerts on main: alerts[] present, and every required + analysis category analysed without error within the window + zap-api the authenticated ZAP API scan report: site[] present, @generated within the window A fetch step that fails writes `.error` instead of a substitute, and that text is carried into the failure. The windows come from the governed @@ -38,7 +41,7 @@ import _gates # noqa: E402 DEFAULT_CONFIG = Path(__file__).resolve().parent.parent / "infrastructure" / "schemas" / "detection-feeds.json" -FEEDS = ("kev", "epss", "grype", "dependabot", "previous-vdr", "checkov", "tfsec") +FEEDS = ("kev", "epss", "grype", "dependabot", "previous-vdr", "checkov", "tfsec", "codeql", "zap-api") DATE_RE = re.compile(r"^\d{4}-\d{2}-\d{2}$") @@ -64,10 +67,13 @@ def load_config(path=None): feeds = cfg.get("feeds") if not isinstance(feeds, dict) or set(feeds) != set(FEEDS): _fail(p, f"feeds must list exactly {list(FEEDS)}") - for name in ("kev", "epss", "grype"): + for name in ("kev", "epss", "grype", "codeql", "zap-api"): w = feeds[name].get("max_age_hours") if isinstance(w, bool) or not isinstance(w, (int, float)) or not 0 < w <= 8760: _fail(p, f"{name}.max_age_hours must be a number in (0, 8760]") + cats = feeds["codeql"].get("categories") + if not isinstance(cats, list) or not cats or not all(isinstance(c, str) and c for c in cats): + _fail(p, "codeql.categories must be a non-empty list of analysis categories") cfg["sha256"] = hashlib.sha256(raw).hexdigest() return cfg @@ -216,6 +222,61 @@ def check_tfsec(path): return {**r, "count": len(doc["results"] or [])} +def check_codeql(path, cfg, now): + """Open CodeQL alerts on main, with the analyses that produced them. An + empty alerts list means nothing only when every required category was + analysed, without error, inside the window; a category never analysed (or + analysed a week ago) would otherwise read as clean code.""" + doc, problem = _load_json(path) + r = {"feed": "codeql", "file": str(path)} + if problem: + return {**r, "problem": problem} + if not isinstance(doc, dict) or not isinstance(doc.get("alerts"), list) \ + or not isinstance(doc.get("analyses"), list): + return {**r, "problem": "no alerts[] and analyses[]"} + r["count"] = len(doc["alerts"]) + latest = {} + for a in doc["analyses"]: + if not isinstance(a, dict): + continue + t = _parse_time(a.get("created_at")) + cat = a.get("category") + if t is not None and isinstance(cat, str) and (cat not in latest or t > latest[cat][0]): + latest[cat] = (t, a) + feed = cfg["feeds"]["codeql"] + missing = [c for c in feed["categories"] if c not in latest] + if missing: + return {**r, "problem": f"no analysis on main for {', '.join(missing)}"} + errored = [c for c in feed["categories"] if latest[c][1].get("error")] + if errored: + return {**r, "problem": f"the latest analysis for {', '.join(errored)} reported an error"} + oldest = min(latest[c][0] for c in feed["categories"]) + return _windowed(r, oldest, feed["max_age_hours"], now, "oldest required analysis") + + +def _zap_time(value): + """ZAP's '@generated' header (UTC on the runner), as an aware time.""" + stamp = str(value or "").strip() + for fmt in ("%a, %d %b %Y %H:%M:%S", "%a, %d %b %Y %H:%M:%S %Z", "%Y-%m-%dT%H:%M:%S"): + try: + return datetime.strptime(stamp, fmt).replace(tzinfo=timezone.utc) + except ValueError: + continue + return None + + +def check_zap_api(path, cfg, now): + doc, problem = _load_json(path) + r = {"feed": "zap-api", "file": str(path)} + if problem: + return {**r, "problem": problem} + if not isinstance(doc, dict) or not isinstance(doc.get("site"), list) or not doc["site"]: + return {**r, "problem": "no site[] (the scan did not reach its target)"} + r["count"] = sum(len(s.get("alerts") or []) for s in doc["site"] if isinstance(s, dict)) + return _windowed(r, _zap_time(doc.get("@generated")), cfg["feeds"]["zap-api"]["max_age_hours"], now, + "@generated") + + def evaluate(args, cfg, now): results = [] if args.kev: @@ -232,6 +293,10 @@ def evaluate(args, cfg, now): results.append(check_checkov(args.checkov)) if args.tfsec: results.append(check_tfsec(args.tfsec)) + if args.codeql: + results.append(check_codeql(args.codeql, cfg, now)) + if args.zap_api: + results.append(check_zap_api(args.zap_api, cfg, now)) return results @@ -244,6 +309,8 @@ def main(argv=None): ap.add_argument("--previous-vdr") ap.add_argument("--checkov") ap.add_argument("--tfsec") + ap.add_argument("--codeql", help="CodeQL alerts and analyses (scripts/fetch-detection-feeds.sh)") + ap.add_argument("--zap-api", help="the authenticated ZAP API scan report") ap.add_argument("--config", default=None, help="detection feed requirements (default: the governed file)") ap.add_argument("--output", default="detection.json") ap.add_argument("--now", default=None, help="ISO time to evaluate at (tests)") diff --git a/scripts/fetch-detection-feeds.sh b/scripts/fetch-detection-feeds.sh index c837c5bb..8dafe2df 100644 --- a/scripts/fetch-detection-feeds.sh +++ b/scripts/fetch-detection-feeds.sh @@ -13,7 +13,8 @@ # GITHUB_REPOSITORY owner/repo # DEPENDABOT_TOKEN a token that can read Dependabot alerts (repo secret # DEPENDABOT_ALERTS_TOKEN; GITHUB_TOKEN cannot) -# ACTIONS_TOKEN a token with actions:read, for the DAST artifact (GITHUB_TOKEN) +# ACTIONS_TOKEN GITHUB_TOKEN with actions:read (the DAST artifacts) and +# security-events:read (the CodeQL code-scanning alerts) set -uo pipefail fail() { # fail FILE REASON @@ -23,7 +24,8 @@ fail() { # fail FILE REASON echo "::warning::$1: $(head -c 200 "$1.error")" } -rm -f previous-vdr-report.json* dependabot-alerts.json* kev-catalog.json* epss-scores.csv.gz* zap-report.json* +rm -f previous-vdr-report.json* dependabot-alerts.json* kev-catalog.json* epss-scores.csv.gz* zap-report.json* \ + zap-api-report.json* codeql-alerts.json* # Previous VDR: the first-detected ledger. Without it every remediation clock restarts. if curl -sfL --retry 3 --retry-delay 2 -o previous-vdr-report.json "${SITE_ORIGIN}/.well-known/vdr-report.json"; then @@ -59,23 +61,62 @@ else fail epss-scores.csv.gz "could not fetch $EPSS_URL" fi -# DAST: the latest successful main-branch run of the weekly ZAP workflow. Its -# age is enforced by the VDR builder (detection.zap.stale); its absence by -# detection.zap.missing. +# DAST: the latest successful main-branch run of the ZAP workflow, whatever +# triggered it (daily schedule, a deploy to main via workflow_run, or a manual +# dispatch: all three run on main). A run succeeds only when both of its scans +# did, so the site baseline and the authenticated API scan come from the same +# run. The baseline's age is enforced by the VDR builder (detection.zap.stale) +# and its absence by detection.zap.missing; the API report's presence and age by +# the detection gate (detection.zap-api). if [ -z "${ACTIONS_TOKEN:-}" ]; then fail zap-report.json "no token to read the ZAP workflow's artifact" + fail zap-api-report.json "no token to read the ZAP workflow's artifact" else run_id=$(GH_TOKEN="$ACTIONS_TOKEN" gh run list -R "$GITHUB_REPOSITORY" --workflow zap-dast.yml --branch main \ --status success --limit 1 --json databaseId -q '.[0].databaseId' 2>/dev/null || true) - rm -rf zap-dast - if [ -n "$run_id" ] && GH_TOKEN="$ACTIONS_TOKEN" gh run download "$run_id" -R "$GITHUB_REPOSITORY" \ - -n zap-dast-report -D zap-dast > /dev/null 2>&1 \ - && [ -f zap-dast/report_json.json ]; then - mv zap-dast/report_json.json zap-report.json - echo "ZAP report from run ${run_id}: generated $(jq -r '."@generated"' zap-report.json 2>/dev/null)." - else - fail zap-report.json "no zap-dast-report artifact from a successful main-branch ZAP DAST Scan run" - fi - rm -rf zap-dast + for pair in "zap-dast-report:zap-report.json" "zap-api-report:zap-api-report.json"; do + artifact=${pair%%:*} out=${pair#*:} + rm -rf zap-dl + if [ -n "$run_id" ] && GH_TOKEN="$ACTIONS_TOKEN" gh run download "$run_id" -R "$GITHUB_REPOSITORY" \ + -n "$artifact" -D zap-dl > /dev/null 2>&1 \ + && [ -f zap-dl/report_json.json ]; then + mv zap-dl/report_json.json "$out" + # The run is named in this log only; nothing built from these files carries it. + echo "ZAP ${artifact}: generated $(jq -r '."@generated"' "$out" 2>/dev/null)." + else + fail "$out" "no ${artifact} artifact from a successful main-branch ZAP DAST Scan run" + fi + rm -rf zap-dl + done fi + +# SAST: open CodeQL alerts on main, with the analyses behind them (newest first, +# one page: the gate needs only the latest per category, and a category not in +# the last hundred analyses is older than its window anyway). Filtered to +# CodeQL: Checkov and tfsec also upload SARIF to code scanning, and those are +# read from their own files. Only the fields the gate and builder read are kept. +if [ -z "${ACTIONS_TOKEN:-}" ]; then + fail codeql-alerts.json "no token to read code-scanning alerts" +elif GH_TOKEN="$ACTIONS_TOKEN" gh api -H "Accept: application/vnd.github+json" \ + "/repos/${GITHUB_REPOSITORY}/code-scanning/analyses?tool_name=CodeQL&ref=refs/heads/main&per_page=100" \ + > codeql-analyses.json 2> codeql.stderr \ + && GH_TOKEN="$ACTIONS_TOKEN" gh api --paginate -H "Accept: application/vnd.github+json" \ + "/repos/${GITHUB_REPOSITORY}/code-scanning/alerts?tool_name=CodeQL&state=open&ref=refs/heads/main&per_page=100" \ + > codeql-pages.json 2>> codeql.stderr \ + && jq -s '{analyses: ([.[0][] | {category, created_at, error, results_count, commit_sha, + tool: {name: .tool.name, version: .tool.version}}]), + alerts: ([.[1:][][] | {number, state, created_at, + rule: {id: .rule.id, name: .rule.name, description: .rule.description, + severity: .rule.severity, + security_severity_level: .rule.security_severity_level}, + most_recent_instance: {category: .most_recent_instance.category, + location: .most_recent_instance.location, + message: .most_recent_instance.message}}])}' \ + codeql-analyses.json codeql-pages.json > codeql-alerts.json \ + && jq -e '(.analyses | type == "array") and (.alerts | type == "array")' codeql-alerts.json > /dev/null; then + echo "CodeQL: $(jq '.alerts | length' codeql-alerts.json) open alert(s); $(jq '[.analyses[].category] | unique | length' codeql-alerts.json) categories analysed." +else + fail codeql-alerts.json "code-scanning API: $(tr '\n' ' ' < codeql.stderr)" +fi +rm -f codeql-analyses.json codeql-pages.json codeql.stderr exit 0 diff --git a/scripts/fetch-published-history.py b/scripts/fetch-published-history.py new file mode 100644 index 00000000..45027028 --- /dev/null +++ b/scripts/fetch-published-history.py @@ -0,0 +1,92 @@ +#!/usr/bin/env python3 +"""Fetch the previously published copy of an append-only history, fail-closed. + +Several published files are append-only: each build carries over what the +previous published copy holds (the access summary's months, the certification +report index's first-publication dates, the package submission log's +entries). If the fetch of the previous copy fails and the build starts over +from nothing, the history is silently reset. So, like the Significant Change +Notification step: + + 200 the body must be a complete JSON document; it is written to OUT. + 404 nothing has been published yet; OUT is removed and the build starts + the history. + anything else (a 5xx, a 403, a redirect loop, a network error, a timeout, + or a 200 whose body is truncated or not JSON) fails the deploy. + +Only HTTPS on the provider's own site is fetched. + + fetch-published-history.py NAME OUT [--site https://samaydlette.com] +""" + +import argparse +import json +import sys +import urllib.error +import urllib.parse +import urllib.request +from pathlib import Path + +SITE = "https://samaydlette.com" +ALLOWED_HOST = "samaydlette.com" +TIMEOUT = 30 + + +def _fail(msg): + raise SystemExit(f"::error::published history: {msg} (fail-closed: refusing to restart the history)") + + +def http_get(url): + """(status, body). An HTTP error status is a status, not an exception; a + network failure raises.""" + req = urllib.request.Request(url, headers={"User-Agent": "samaydlette-deploy/1 (history fetch)"}) + try: + with urllib.request.urlopen(req, timeout=TIMEOUT) as r: # nosec B310: https on the allowed host only + return r.status, r.read() + except urllib.error.HTTPError as e: + return e.code, b"" + + +def fetch(name, out, site=SITE, get=http_get): + """Write the published `name` to `out` and return True, or remove `out` and + return False when it has never been published (404). Fails otherwise.""" + if not name or "/" in name or name.startswith(".") or not name.endswith(".json"): + _fail(f"{name!r} is not a .json file name under /.well-known/") + url = f"{site.rstrip('/')}/.well-known/{name}" + parts = urllib.parse.urlsplit(url) + if parts.scheme != "https" or parts.hostname != ALLOWED_HOST: + _fail(f"refusing to fetch {url!r} (only https://{ALLOWED_HOST})") + out = Path(out) + try: + status, body = get(url) + except (OSError, ValueError) as exc: + _fail(f"cannot fetch the published {name} ({type(exc).__name__})") + if status == 404: + out.unlink(missing_ok=True) + print(f"{name} not published yet; starting its history") + return False + if status != 200: + _fail(f"fetching the published {name} returned HTTP {status}") + try: + doc = json.loads(body) + except (ValueError, UnicodeDecodeError): + _fail(f"the published {name} is truncated or not JSON") + if not isinstance(doc, dict) or not doc: + _fail(f"the published {name} is not a JSON object") + out.write_bytes(body) + print(f"{name}: previous published copy read ({len(body)} bytes)") + return True + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__, formatter_class=argparse.RawDescriptionHelpFormatter) + ap.add_argument("name") + ap.add_argument("out") + ap.add_argument("--site", default=SITE) + a = ap.parse_args(argv) + fetch(a.name, a.out, a.site) + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/hold-quarterly-review.py b/scripts/hold-quarterly-review.py new file mode 100644 index 00000000..9a10ebdc --- /dev/null +++ b/scripts/hold-quarterly-review.py @@ -0,0 +1,125 @@ +#!/usr/bin/env python3 +"""Hold each Quarterly Review on its date, with simulated attendees (CCM-QTR-MTG, CCM-QTR-RTR). + +Run by package-maintenance.yml after it issues the quarterly report. For every +calendar issue whose review date has come and that the published index +(quarterly-reviews.json) does not list yet, it reads the frozen report +(ocr-issue-.json, whose sha256 must equal the one the verified OCR issue +index records), builds the review with scripts/_quarterly_review.py and writes: + + quarterly-review-.json and .md the review, never rewritten + quarterly-reviews.json the index of every review held, plus the next date + +A malformed previous index fails (each earlier review is carried forward +unchanged, by date and sha256), as does a due review whose report cannot be +found or does not match its recorded sha256. The list of +new files to publish goes to --new-files (one per line). + + hold-quarterly-review.py --ocr-index out/ocr-issues.json --issues-dir DIR [--issues-dir DIR] \ + --previous-index work/quarterly-reviews.json --out out --new-files out/reviews.txt +""" + +import argparse +import hashlib +import json +import re +import sys +from datetime import datetime, timezone +from pathlib import Path + +sys.path.insert(0, str(Path(__file__).resolve().parent)) +import _ccm # noqa: E402 +import _engagement # noqa: E402 +import _offering # noqa: E402 +import _quarterly_review as qr # noqa: E402 + + +_DATE = re.compile(r"^\d{4}-\d{2}-\d{2}$") +_SHA = re.compile(r"^[0-9a-f]{64}$") + + +def _fail(msg): + raise SystemExit(f"::error::Quarterly Review: {msg} (fail-closed)") + + +def _find(name, dirs): + for d in dirs: + p = Path(d) / name + if p.is_file(): + return p + return None + + +def run(cal, ocr_index, issues_dirs, previous, out, now, fedramp_id): + today = now.date() + issued = {i["issueDate"]: i for i in (ocr_index or {}).get("issues", [])} + reviews = list((previous or {}).get("reviews", [])) + for r in reviews: + if (not isinstance(r, dict) or not _DATE.match(str(r.get("ocrIssue"))) + or not _SHA.match(str(r.get("reviewSha256")))): + _fail("the previous review index holds a malformed entry") + have = qr.held(previous) + new = [] + for d in cal.issues: + iso = d.isoformat() + if cal.review_date(d) > today or iso in have: + continue + entry = issued.get(iso) + if entry is None: + _fail(f"the review of {iso} is due but no report was issued on {iso}") + p = _find(f"ocr-issue-{iso}.json", issues_dirs) + if p is None: + _fail(f"the review of {iso} is due but ocr-issue-{iso}.json is not available") + sha = hashlib.sha256(p.read_bytes()).hexdigest() + if sha != entry.get("reportSha256"): + _fail(f"ocr-issue-{iso}.json does not match the sha256 the issue index records") + doc = qr.build(cal, d, json.loads(p.read_text()), sha, now, fedramp_id) + name = f"quarterly-review-{iso}" + (out / f"{name}.json").write_text(json.dumps(doc, indent=2) + "\n") + (out / f"{name}.md").write_text(qr.render_markdown(doc) + "\n") + reviews.append({"ocrIssue": iso, "reviewDate": doc["reviewDate"], "heldAt": doc["heldAt"], + "late": doc["late"], "review": f"{qr.BASE}{name}.json", "reviewMarkdown": f"{qr.BASE}{name}.md", + "reviewSha256": hashlib.sha256((out / f"{name}.json").read_bytes()).hexdigest()}) + new += [f"{name}.json", f"{name}.md"] + reviews.sort(key=lambda r: r["ocrIssue"]) + index = {"schema": qr.INDEX_SCHEMA, "fedRampId": fedramp_id, "generated_at": now.isoformat(), + "simulated": True, "engagement": _engagement.STATEMENT, + "nextQuarterlyReviewDate": cal.next_review(today).isoformat(), + "calendar": _ccm.ICS_URL, + "access": "Each review is at /.well-known/quarterly-review-.json (and .md), signed (.bundle) " + "and never rewritten; this index records each one's sha256.", + "reviews": reviews} + late = qr.missing(cal, index, today) + if late: + _fail(f"review(s) past their date and not held: {', '.join(str(r) for _, r in late)}") + (out / "quarterly-reviews.json").write_text(json.dumps(index, indent=2) + "\n") + return index, new + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + ap.add_argument("--calendar", default=str(_ccm.CALENDAR_PATH)) + ap.add_argument("--offering", default=str(_offering.OFFERING_PATH)) + ap.add_argument("--ocr-index", required=True, help="ocr-issues.json as published after this run's issue step") + ap.add_argument("--issues-dir", action="append", required=True, help="where the frozen reports are") + ap.add_argument("--previous-index", default=None) + ap.add_argument("--out", required=True) + ap.add_argument("--new-files", default=None) + a = ap.parse_args(argv) + now = datetime.now(timezone.utc) + cal = _ccm.load(a.calendar, now.date()) + prev_path = Path(a.previous_index) if a.previous_index else None + previous = json.loads(prev_path.read_text()) if prev_path and prev_path.is_file() else {} + out = Path(a.out) + out.mkdir(parents=True, exist_ok=True) + index, new = run(cal, json.loads(Path(a.ocr_index).read_text()), a.issues_dir, previous, out, now, + _offering.fedramp_id(a.offering)) + if a.new_files: + Path(a.new_files).write_text("".join(f + "\n" for f in new)) + print(f"quarterly-reviews: {len(index['reviews'])} held; {len(new) // 2} new this run; next " + f"{index['nextQuarterlyReviewDate']}") + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/hold-recovery-exercise.py b/scripts/hold-recovery-exercise.py new file mode 100644 index 00000000..985c720b --- /dev/null +++ b/scripts/hold-recovery-exercise.py @@ -0,0 +1,293 @@ +#!/usr/bin/env python3 +"""Hold the monthly recovery exercise, from the evidence nightly (KSI-RPL-TRC, KSI-RPL-ARP; CP-4). + +No person runs a recovery test (DEC-195). On the first of every month the +nightly holds one, with no write to production and no restore: + + (a) restore point the site tree is rebuilt from the deployed commit (the + commit the published inventory names) exactly as the + deploy uploads it, and every page's sha256 is compared + with the live object fetched over HTTPS. The only + difference allowed is the deploy's cache-busting + `?v=` on asset links, removed on both sides. + Every page matching proves the restore point is the + commit: losing the bucket loses nothing git does not have. + (b) configuration the signed runtime signal (verified against the committed + key, fresh, built from the deployed commit) re-validated + every bucket and the state-lock table, so versioning and + point-in-time recovery are in place as the plan says. + (c) tabletop in November, a scripted tabletop walks every loss scenario + in docs/recovery-plan.md with a simulated incident + commander and a simulated scenario injector; a scenario + with no recovery stated fails it. + +It writes vdr-recovery-exercise-.json and .view.md (never rewritten) +and the index vdr-recovery-exercises.json. An exercise with a failing check is +not frozen: the run fails and the next run holds it again, once the cause is +fixed; scripts/check-scheduled-review.py fails the nightly and the deploy from +the day after its due date until then. + + hold-recovery-exercise.py --commit SHA --runtime-signal ksi-signal-runtime.json \ + [--previous-index vdr-recovery-exercises.json] --out DIR --new-files FILE +""" + +import argparse +import fnmatch +import hashlib +import importlib.util +import json +import re +import subprocess +import sys +import urllib.error +import urllib.parse +import urllib.request +from pathlib import Path + +HERE = Path(__file__).resolve().parent +REPO = HERE.parent +sys.path.insert(0, str(HERE)) +import _offering # noqa: E402 +import _scheduled_review as sr # noqa: E402 + +RV = sr.REVIEWS["recovery-exercise"] +SITE = "https://samaydlette.com" +ALLOWED_HOST = "samaydlette.com" +TABLETOP_MONTH = 11 +PLAN = REPO / "docs" / "recovery-plan.md" +# The deploy's sync (deploy-with-opa.yml "Sync Website Content") skips these, +# relative to website/; .well-known/ is published separately and is evidence, not content. +SYNC_EXCLUDES = ("*.tf", "*.tfvars*", "*.tfstate*", ".terraform/*", "infrastructure/*", "scripts/*", ".git/*", + "README.md", "Makefile", ".gitignore", ".github/*", ".well-known/*") +CACHE_BUST = re.compile(rb"(\.(?:css|js))\?v=\d+") +RECOVERABLE_TYPES = ("object_store", "kv_table") + + +def _fail(msg): + raise SystemExit(f"::error::recovery exercise: {msg} (fail-closed)") + + +def normalize(path, body): + """The bytes compared: HTML without the deploy's cache-busting query string.""" + return CACHE_BUST.sub(rb"\1?v=", body) if path.endswith(".html") else body + + +def _git(args, repo): + return subprocess.run(["git", "-C", str(repo), *args], capture_output=True, check=True, # nosec B603 + timeout=120).stdout + + +def site_tree(commit, repo=REPO): + """{site path: bytes} for every file the deploy uploads from `commit`.""" + if not re.fullmatch(r"[0-9a-f]{40}", commit or ""): + _fail("the deployed commit is not a 40-hex commit id") + names = _git(["ls-tree", "-r", "--name-only", "-z", commit, "--", "website/"], repo).split(b"\0") + out = {} + for raw in names: + name = raw.decode() + if not name: + continue + rel = name[len("website/"):] + if any(fnmatch.fnmatchcase(rel, pat) for pat in SYNC_EXCLUDES): + continue + out[rel] = _git(["show", f"{commit}:{name}"], repo) + if not out: + _fail("the deployed commit has no website tree") + return out + + +def http_get(url): + parts = urllib.parse.urlsplit(url) + if parts.scheme != "https" or parts.hostname != ALLOWED_HOST: + _fail(f"refusing to fetch {url!r}") + req = urllib.request.Request(url, headers={"User-Agent": "samaydlette-recovery-exercise/1", + "Accept-Encoding": "identity"}) + try: + with urllib.request.urlopen(req, timeout=30) as r: # nosec B310: https on the allowed host only + return r.status, r.read() + except urllib.error.HTTPError as e: + return e.code, b"" + + +def restore_point(tree, get, site=SITE): + """Check (a): every page in the rebuilt tree is byte-identical (cache-busting aside) to the live one.""" + mismatched, unreachable, unaddressable = [], [], [] + for rel in sorted(tree): + if "." not in rel.rsplit("/", 1)[-1]: + # The edge's directory-index function (infrastructure/cloudfront/directory-index.js) + # redirects an extensionless path to a directory, so no URL reaches the object. + unaddressable.append(rel) + continue + url = f"{site}/{urllib.parse.quote(rel)}" + status, body = None, b"" + for _ in range(3): + try: + status, body = get(url) + except (OSError, ValueError): + status = None + if status == 200: + break + if status != 200: + unreachable.append(rel) + elif hashlib.sha256(normalize(rel, body)).digest() != hashlib.sha256(normalize(rel, tree[rel])).digest(): + mismatched.append(rel) + ok = not mismatched and not unreachable + compared = len(tree) - len(unaddressable) + detail = (f"{len(tree)} file(s) rebuilt from the deployed commit; {compared - len(mismatched) - len(unreachable)} " + f"of {compared} identical live") + if unaddressable: + detail += (f"; not addressable at the edge (no file extension), so not compared: " + f"{', '.join(unaddressable[:10])}") + if mismatched: + detail += f"; differ: {', '.join(mismatched[:10])}" + if unreachable: + detail += f"; not served: {', '.join(unreachable[:10])}" + return {"id": "restore-point", "title": "The live site is the deployed commit: every page rebuilt from git " + "matches the served object (sha256)", "result": "pass" if ok else "fail", + "detail": detail, "files": len(tree), "differ": mismatched, "notServed": unreachable, + "notAddressable": unaddressable} + + +def _vdr_builder(): + spec = importlib.util.spec_from_file_location("vdr_for_recovery", HERE / "build-vdr-report.py") + m = importlib.util.module_from_spec(spec) + spec.loader.exec_module(m) + return m + + +def configuration(runtime_path, commit, now, loader=None): + """Check (b): versioning and point-in-time recovery, from the verified runtime signal.""" + title = ("Versioning on every bucket and point-in-time recovery on the state-lock table, re-validated by the " + "signed runtime signal of the deployed commit") + rt = (loader or _vdr_builder().load_runtime_signal)(runtime_path, now=now) + if not rt.get("verified") or not rt.get("fresh"): + return {"id": "configuration", "title": title, "result": "fail", + "detail": rt.get("reason") or "the runtime signal is not verified and fresh"} + sig = json.loads(Path(runtime_path).read_text()) + if ((sig.get("provenance") or {}).get("source") or {}).get("commit") != commit: + return {"id": "configuration", "title": title, "result": "fail", + "detail": "the runtime signal was not built from the deployed commit"} + wanted = sorted(c["component_id"] for c in sig.get("components") or [] if c.get("type") in RECOVERABLE_TYPES) + passing = {ref for v in rt["validations"] if v.get("result") == "pass" for ref in v.get("component_refs") or []} + gaps = [c for c in wanted if c not in passing] + ok = bool(wanted) and not gaps + return {"id": "configuration", "title": title, "result": "pass" if ok else "fail", + "detail": (f"{len(wanted)} component(s) re-validated, runtime signal emitted {rt['emitted_at']}" + + (f"; not re-validated or failing: {', '.join(gaps)}" if gaps else "") + if wanted else "the runtime signal lists no bucket or table"), + "components": wanted} + + +def scenarios(text): + """[(scenario, recovery)] from the plan's 'In-scope loss scenarios' list.""" + m = re.search(r"In-scope loss scenarios:\s*\n((?:\s*- .+\n?)+)", text) + out = [] + for line in (m.group(1).splitlines() if m else []): + item = line.strip()[2:].strip() + what, _, how = item.partition(" — ") + out.append((what.strip(), how.strip())) + return out + + +def tabletop(plan_text): + """Check (c), each November: a scripted tabletop over every scenario in the plan.""" + ic, inj = sr.CAST["incident-commander"], sr.CAST["scenario-injector"] + items = scenarios(plan_text) + lines = [{"speaker": ic, "line": "Welcome to the annual recovery tabletop. The table is real. Nothing else is."}, + {"speaker": inj, "line": f"I have {len(items)} scenario(s) from docs/recovery-plan.md and a sense of " + "foreboding."}] + gaps = [] + for n, (what, how) in enumerate(items, 1): + lines.append({"speaker": inj, "line": f"Scenario {n}: {what}. Also, it is raining."}) + if how: + lines.append({"speaker": ic, "line": f"The plan says: {how}. Nobody panics; the plan says that too."}) + else: + gaps.append(what) + lines.append({"speaker": ic, "line": "The plan does not say. Minuted as a gap."}) + has_procedure = "## Recovery procedure" in plan_text + lines.append({"speaker": ic, "line": "Tabletop adjourned. The table was not harmed. Same time next November."}) + ok = len(items) >= 3 and not gaps and has_procedure + detail = f"{len(items)} scenario(s) walked" + if gaps: + detail += f"; no recovery stated for: {', '.join(gaps)}" + if not has_procedure: + detail += "; the plan has no Recovery procedure section" + return ({"id": "tabletop", "title": "Annual tabletop: every loss scenario in the recovery plan has a stated " + "recovery, walked with simulated responders", + "result": "pass" if ok else "fail", "detail": detail}, + {"participants": [ic, inj], "scenarios": [w for w, _ in items], "transcript": lines}) + + +def build(due, now, fedramp_id, tree, get, runtime_path, commit, plan_text, runtime_loader=None): + checks = [restore_point(tree, get), configuration(runtime_path, commit, now, runtime_loader)] + doc = sr.base_doc(RV, due, now, fedramp_id, f"Recovery exercise for {due:%B %Y} (automated; simulated " + "tabletop responders)") + doc.update({"rules": ["KSI-RPL-TRC", "KSI-RPL-ARP", "KSI-RPL-ABO"], "controls": ["cp-4", "cp-9", "cp-10"], + "deployedCommit": commit, + "method": "scripts/hold-recovery-exercise.py, run by evidence-nightly.yml on its due date. No write " + "to production and no restore: the restore point is proved by rebuilding the site from " + "git and comparing it with what is served.", + "plan": "docs/recovery-plan.md"}) + if due.month == TABLETOP_MONTH: + chk, record = tabletop(plan_text) + checks.append(chk) + doc["tabletop"] = record + doc["checks"] = [{k: v for k, v in c.items() if k in ("id", "title", "result", "detail")} for c in checks] + doc["result"] = sr.result_of(doc["checks"]) + return sr.finish(doc, "the recovery exercise") + + +def run(previous, out, now, fedramp_id, commit, runtime_path, get=http_get, repo=REPO, runtime_loader=None, + plan_path=PLAN): + """Hold every due exercise that passes; the index is written either way + (carried forward), and a failing exercise then fails the run.""" + today = now.date() + due = sr.due_now(RV, previous, today) + entries, files, failed = [], [], [] + if due: + tree = site_tree(commit, repo) + plan_text = Path(plan_path).read_text(encoding="utf-8") + for d in due: + doc = build(d, now, fedramp_id, tree, get, runtime_path, commit, plan_text, runtime_loader) + if doc["result"] != "pass": + for c in doc["checks"]: + if c["result"] != "pass": + print(f"::error::recovery exercise due {d}: {c['title']}: {c['detail']}") + failed.append(d) + continue + entry, written = sr.write(out, RV, d, doc) + entries.append(entry) + files += written + index = sr.index_doc(RV, previous, entries, now, fedramp_id) + sr.write_json(out, RV.index, index) # republished every run; `files` lists only the new, frozen ones + return index, entries, files, failed + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + ap.add_argument("--commit", required=True, help="the commit the published inventory was built from") + ap.add_argument("--runtime-signal", required=True) + ap.add_argument("--previous-index", default=None) + ap.add_argument("--out", required=True) + ap.add_argument("--new-files", default=None) + ap.add_argument("--now", default=None, help=argparse.SUPPRESS) + a = ap.parse_args(argv) + now = sr.now_utc(a.now) + prev = Path(a.previous_index) if a.previous_index else None + previous = json.loads(prev.read_text()) if prev and prev.is_file() else {} + out = Path(a.out) + out.mkdir(parents=True, exist_ok=True) + index, entries, files, failed = run(previous, out, now, _offering.fedramp_id(), a.commit, a.runtime_signal) + if a.new_files: + Path(a.new_files).write_text("".join(f + "\n" for f in files)) + for e in entries: + print(f"recovery exercise due {e['dueDate']}: {e['result']}") + print(f"recovery exercises: {len(index['reviews'])} held; next due {index['nextDueDate']}") + if failed: + _fail(f"the exercise due {', '.join(map(str, failed))} did not pass; it is held again on the next run " + "once fixed") + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/hold-security-review.py b/scripts/hold-security-review.py new file mode 100644 index 00000000..9096c812 --- /dev/null +++ b/scripts/hold-security-review.py @@ -0,0 +1,345 @@ +#!/usr/bin/env python3 +"""Hold the Annual Security Review, from package maintenance (KSI-PIY-RIS, KSI-PIY-RES, KSI-SVC-EIS, KSI-INR-RPI; PL-4). + +Nobody convenes a review meeting (DEC-195). On its date the package +maintainer, at the deployed commit, generates the review from the system's own +data, and a simulated reviewer signs off each item: + + documents every policy, procedure, plan and record in + data/non-machine-resources.json with its sha256, the result + of its machine checks (scripts/_nonmachine.py) and whether it + changed since the previous review. Any failing check fails. + component types the inventory's component types. A type added since the + previous review must be named in the threat model or the + ingress and DDoS sections of docs/architecture-decisions.md, + or the review fails (the fix is a doc change, not a meeting). + operations the last 12 months: decisions made, superseded and lapsed; + the VDR's open, accepted and process findings; incidents and + exercises by pattern. A real incident pattern seen twice + fails the review (KSI-INR-RPI): it needs a code or doc change. + investment recurring cost from data/recurring-costs.json (a source per + line) and pipeline minutes from the run history. + rules of the rules of behavior's sha256 is acknowledged by a simulated + behavior member of personnel each year and whenever it changes, on + every maintainer run; the deploy fails while the current + version has no acknowledgement. + +A review that fails is not frozen: the run fails and the next run holds it +again, so the fix is shipped before the review is published. Writes +security-review-.json and .view.md (never rewritten) and the index +security-reviews.json (with the acknowledgements), every run. + + hold-security-review.py --ksi-signal ksi-signal.json --vdr vdr-report.json \ + [--runs runs.json] [--previous-index security-reviews.json] --out DIR --new-files FILE +""" + +import argparse +import hashlib +import json +import re +import sys +from collections import Counter +from datetime import date, timedelta +from pathlib import Path + +HERE = Path(__file__).resolve().parent +REPO = HERE.parent +sys.path.insert(0, str(HERE)) +import _decisions # noqa: E402 +import _nonmachine # noqa: E402 +import _offering # noqa: E402 +import _scheduled_review as sr # noqa: E402 + +RV = sr.REVIEWS["security-review"] +ROB = "docs/rules-of-behavior.md" +COSTS = REPO / "data" / "recurring-costs.json" +THREAT_DOC = "docs/architecture-decisions.md" +# The sections of THREAT_DOC a new component type must be named in. +THREAT_SECTIONS = ("## Threat Modeling", "## Ingress and egress restriction", "## DDoS and unwanted-activity") +# What a component type is called in prose. A type not here is looked for by its own name. +TYPE_TERMS = { + "api_gateway": ("API Gateway",), "audit_log_trail": ("CloudTrail", "trail"), "cdn_distribution": ("CloudFront",), + "dns_zone": ("DNS", "Route 53"), "event_schedule": ("EventBridge", "schedule"), "external_service": ("Sigstore", + "GitHub"), + "function": ("Lambda",), "html_artifact": ("static site", "site content"), "iam_group": ("IAM",), + "iam_policy": ("IAM",), "iam_role": ("role",), "identity_provider": ("Cognito",), "kms_key": ("KMS",), + "kv_table": ("DynamoDB", "state lock"), "log_group": ("CloudWatch Logs", "log group"), + "message_queue": ("SQS", "queue"), "metric_alarm": ("alarm",), "notification_topic": ("SNS",), + "npm_package": ("npm", "dependenc"), "object_store": ("S3", "bucket"), "oidc_provider": ("OIDC",), + "pypi_package": ("PyPI", "Python", "dependenc"), "tls_certificate": ("TLS", "ACM"), +} +COST_KEYS = {"id", "item", "source", "estimate_usd_per_year", "estimate", "basis"} +WINDOW_DAYS = 365 +STATUS = "AI-drafted estimate; operator to correct" + + +def _fail(msg): + raise SystemExit(f"::error::security review: {msg} (fail-closed)") + + +def sha256_file(path): + return hashlib.sha256(Path(path).read_bytes()).hexdigest() + + +# --- the items ------------------------------------------------------------------------- + +def documents(nm, decisions, previous_review, repo=REPO): + probs = _nonmachine.problems(nm, decisions, repo) + before = {d["path"]: d["sha256"] for d in (previous_review or {}).get("documents") or []} + rows = [] + for e in nm["resources"]: + p = repo / e["path"] + sha = sha256_file(p) if p.is_file() else None + mine = [x for x in probs if x.startswith(e["id"] + ":")] + rows.append({"id": e["id"], "path": e["path"], "kind": e["kind"], "sha256": sha, + "checks": "fail" if mine else "pass", + "changedSinceLastReview": None if not before else before.get(e["path"]) != sha}) + bad = [r["id"] for r in rows if r["checks"] == "fail"] + [x for x in probs if " has no entry " in x] + check = {"id": "documents", "title": "Every policy, procedure, plan and record passes its machine checks", + "result": "fail" if bad else "pass", + "detail": (f"{len(rows)} document(s); " + + (f"failing: {', '.join(bad[:10])}" if bad else "all pass") + + (f"; {sum(1 for r in rows if r['changedSinceLastReview'])} changed since the last review" + if before else "; first review: every document is the baseline"))} + return check, rows + + +def _section_text(text, heading): + i = text.find(heading) + if i < 0: + return "" + j = text.find("\n## ", i + 1) + return text[i:j if j > 0 else None] + + +def component_types(signal, previous_review, threat_text): + types = sorted({c.get("type") for c in signal.get("components") or [] if c.get("type")}) + if not types: + _fail("the inventory lists no component types") + sections = "\n".join(_section_text(threat_text, h) for h in THREAT_SECTIONS) + prev = (previous_review or {}).get("componentTypes") + new = sorted(set(types) - set(prev)) if isinstance(prev, list) else [] + + def named(t): + terms = TYPE_TERMS.get(t, (t.replace("_", " "),)) + return any(re.search(re.escape(term), sections, re.I) for term in terms) + + unnamed = [t for t in new if not named(t)] + check = {"id": "component-types", "title": f"Every component type added since the last review is named in the " + f"threat model ({THREAT_DOC})", "result": "fail" if unnamed else "pass", + "detail": (f"{len(types)} type(s); " + (f"new since the last review: {', '.join(new)}" if new else + "none new since the last review" if isinstance(prev, list) else + "first review: the current types are the baseline") + + (f"; not named: {', '.join(unnamed)}" if unnamed else ""))} + return check, types + + +def _day(v): + try: + return date.fromisoformat(str(v)[:10]) + except ValueError: + return None + + +def operations(reg, incidents, vdr, today): + since = today - timedelta(days=WINDOW_DAYS) + recent = [r for r in reg["decisions"] if (_day(r.get("decided_on")) or date.min) >= since] + lapsed = [r["id"] for r in _decisions.in_force(reg) if str(r.get("review_by", "")) < today.isoformat()] + findings = vdr.get("findings") or [] + incs = [i for i in incidents.get("incidents") or [] if (_day(i.get("detected_at")) or date.min) >= since] + real = [i for i in incs if not i.get("exercise")] + patterns = Counter(i["evaluation"].get("basis") or "unclassified" for i in real) + recurring = sorted(p for p, n in patterns.items() if n >= 2) + summary = { + "decisions": {"madeInLast12Months": len(recent), + "byDisposition": dict(sorted(Counter(r.get("disposition") for r in recent).items())), + "superseded": sum(1 for r in recent if r.get("disposition") == "superseded"), + "lapsed": lapsed}, + "findings": {"inVdr": len(findings), "process": sum(1 for f in findings if f.get("source") == "process"), + "riskAccepted": len(vdr.get("risk_accepted") or [])}, + "incidents": {"inLast12Months": len(real), "exercises": len(incs) - len(real), + "patterns": dict(sorted(patterns.items())), "recurring": recurring}, + } + checks = [ + {"id": "decisions", "title": "No in-force decision is past its review date", "result": "fail" if lapsed else + "pass", "detail": f"{len(recent)} decision(s) in the last 12 months; lapsed: {', '.join(lapsed) or 'none'}"}, + {"id": "incident-patterns", "title": "No incident pattern recurs (KSI-INR-RPI)", + "result": "fail" if recurring else "pass", + "detail": f"{len(real)} incident(s) and {len(incs) - len(real)} exercise(s) in the last 12 months" + + (f"; recurring: {', '.join(recurring)}" if recurring else "")}, + ] + return checks, summary + + +def validate_costs(doc, repo=REPO): + if not isinstance(doc, dict) or doc.get("schema") != "recurring-costs/1" or doc.get("status") != STATUS: + _fail(f"data/recurring-costs.json is not a recurring-costs/1 document marked {STATUS!r}") + lines = doc.get("lines") + if not isinstance(lines, list) or not lines: + _fail("data/recurring-costs.json has no lines") + seen = set() + for x in lines: + if not isinstance(x, dict) or set(x) != COST_KEYS or x["id"] in seen: + _fail(f"a cost line must have exactly {sorted(COST_KEYS)} and a unique id: {x!r}"[:200]) + seen.add(x["id"]) + src = str(x["source"]) + if not src.startswith("external:") and not (repo / src.split("#", 1)[0]).exists(): + _fail(f"{x['id']}: source {src!r} is neither a repository path nor external:") + est = x["estimate_usd_per_year"] + if est is not None and (isinstance(est, bool) or not isinstance(est, (int, float)) or est < 0): + _fail(f"{x['id']}: estimate_usd_per_year must be a non-negative number or null (unknown)") + if est is None and x["estimate"] != "unknown": + _fail(f"{x['id']}: a line with no figure must say 'unknown'") + return doc + + +def investment(costs, runs, today): + known = [x for x in costs["lines"] if x["estimate_usd_per_year"] is not None] + since = (today - timedelta(days=WINDOW_DAYS)).isoformat() + minutes = Counter() + for r in runs or []: + a, b = sr._ts(r.get("createdAt")), sr._ts(r.get("updatedAt")) + if a and b and str(r.get("createdAt")) >= since: + minutes[r.get("workflowName") or "unknown"] += max(0, round((b - a).total_seconds() / 60)) + summary = {"status": costs["status"], "estimatedUsdPerYear": round(sum(x["estimate_usd_per_year"] for x in known), + 2), + "unknownLines": [x["id"] for x in costs["lines"] if x["estimate_usd_per_year"] is None], + "lines": costs["lines"], + "pipelineMinutes": {"byWorkflow": dict(sorted(minutes.items())), "total": sum(minutes.values()), + "basis": "wall-clock minutes of the workflow runs GitHub lists (gh run list), " + "created in the last 12 months; minutes on a public repository's " + "standard runners are not billed"}} + check = {"id": "investment", "title": "Recurring cost has a source for every line (data/recurring-costs.json) " + "and the pipeline's run time is known", + "result": "pass" if runs is not None else "fail", + "detail": f"estimated ${summary['estimatedUsdPerYear']}/year over {len(known)} line(s), " + f"{len(summary['unknownLines'])} unknown ({STATUS}); " + + (f"{summary['pipelineMinutes']['total']} pipeline minute(s) from {len(runs)} run(s)" + if runs is not None else "no run history was read")} + return check, summary + + +# --- the rules of behavior ------------------------------------------------------------- + +def acknowledgements(previous_index, rob_sha, today, held_now): + acks = list(((previous_index or {}).get("rulesOfBehavior") or {}).get("acknowledgements") or []) + known = {a.get("sha256") for a in acks} + reason = ("annual acknowledgement with the security review" if held_now else + None if rob_sha in known else + "first acknowledgement" if not acks else "the rules of behavior changed") + if reason: + acks.append({"sha256": rob_sha, "acknowledgedOn": today.isoformat(), "by": sr.CAST["personnel"], + "reason": reason}) + return {"document": ROB, "currentSha256": rob_sha, "acknowledgedBy": sr.CAST["personnel"], + "rule": "PL-4: acknowledged every year and whenever the document changes; the deploy fails while the " + "current version has no acknowledgement (scripts/check-scheduled-review.py).", + "acknowledgements": acks} + + +def rob_acknowledged(index, rob_sha): + acks = ((index or {}).get("rulesOfBehavior") or {}).get("acknowledgements") or [] + return any(a.get("sha256") == rob_sha for a in acks) + + +# --- the review ------------------------------------------------------------------------ + +def previous_review(previous_index, docs_dirs): + """The last held review's document, read from the published copy (by its sha256).""" + have = sr.held(RV, previous_index) + if not have: + return None + last = have[max(have)] + name = f"{RV.prefix}{last['dueDate']}.json" + for d in docs_dirs: + p = Path(d) / name + if p.is_file(): + if hashlib.sha256(p.read_bytes()).hexdigest() != last["sha256"]: + _fail(f"{name} does not match the sha256 the index records") + return json.loads(p.read_text()) + _fail(f"the previous review {name} is not available") + + +def build(due, now, fedramp_id, signal, vdr, runs, reg, incidents, nm, costs, prev, threat_text, repo=REPO): + today = now.date() + doc_check, docs = documents(nm, reg, prev, repo) + type_check, types = component_types(signal, prev, threat_text) + op_checks, ops = operations(reg, incidents, vdr, today) + inv_check, inv = investment(costs, runs, today) + checks = [doc_check, type_check, *op_checks, inv_check] + remarks = {"pass": "Reviewed. Looks good. I would have said so in a meeting, too, but this was faster.", + "fail": "Not signed. Fix it in a pull request; I will be here, being simulated."} + doc = sr.base_doc(RV, due, now, fedramp_id, f"Annual Security Review due {due} (generated; simulated sign-off)") + doc.update({ + "rules": ["KSI-PIY-RIS", "KSI-PIY-RES", "KSI-SVC-EIS", "KSI-INR-RPI"], + "controls": ["pl-2", "pl-4", "pm-3", "ra-3", "sa-11", "ir-4"], + "method": "scripts/hold-security-review.py, run by package-maintenance.yml at the deployed commit on its due " + "date. Generated from the system's data; a failing item fails the run, and the fix is a code or " + "document change, not a meeting.", + "reviewer": sr.CAST["reviewer"], + "checks": checks, "result": sr.result_of(checks), + "signOff": [{"check": c["id"], "by": sr.CAST["reviewer"], "result": c["result"], "remark": remarks[c["result"]]} + for c in checks], + "documents": docs, "componentTypes": types, "operations": ops, "investment": inv, + "previousReview": prev.get("dueDate") if prev else None, + }) + return sr.finish(doc, "the security review") + + +def run(previous, out, now, fedramp_id, signal, vdr, runs, prev_dirs, repo=REPO, costs_path=COSTS): + today = now.date() + due = sr.due_now(RV, previous, today) + entries, files = [], [] + if due: + reg = _decisions.load(repo / "data" / "decisions.json") + incidents = json.loads((repo / "data" / "incidents.json").read_text()) + nm = _nonmachine.load(repo / "data" / "non-machine-resources.json") + costs = validate_costs(json.loads(Path(costs_path).read_text()), repo) + threat_text = (repo / THREAT_DOC).read_text(encoding="utf-8") + prev = previous_review(previous, prev_dirs) + for d in due: + doc = build(d, now, fedramp_id, signal, vdr, runs, reg, incidents, nm, costs, prev, threat_text, repo) + if doc["result"] != "pass": + for c in doc["checks"]: + if c["result"] != "pass": + print(f"::error::security review due {d}: {c['title']}: {c['detail']}") + _fail(f"the review due {d} did not pass; it is held again on the next run once fixed") + entry, written = sr.write(out, RV, d, doc) + entries.append(entry) + files += written + prev = doc + rob = acknowledgements(previous, sha256_file(repo / ROB), today, bool(entries)) + index = sr.index_doc(RV, previous, entries, now, fedramp_id, {"rulesOfBehavior": rob}) + sr.write_json(out, RV.index, index) + return index, entries, files + + +def main(argv=None): + ap = argparse.ArgumentParser(description=__doc__.splitlines()[0]) + ap.add_argument("--ksi-signal", required=True) + ap.add_argument("--vdr", required=True) + ap.add_argument("--runs", default=None, help="gh run list --json workflowName,createdAt,updatedAt output") + ap.add_argument("--previous-index", default=None) + ap.add_argument("--previous-dir", action="append", default=[], help="where the previous review's file is") + ap.add_argument("--out", required=True) + ap.add_argument("--new-files", default=None) + ap.add_argument("--now", default=None, help=argparse.SUPPRESS) + a = ap.parse_args(argv) + now = sr.now_utc(a.now) + prev = Path(a.previous_index) if a.previous_index else None + previous = json.loads(prev.read_text()) if prev and prev.is_file() else {} + out = Path(a.out) + out.mkdir(parents=True, exist_ok=True) + runs = json.loads(Path(a.runs).read_text()) if a.runs else None + index, entries, files = run(previous, out, now, _offering.fedramp_id(), json.loads(Path(a.ksi_signal).read_text()), + json.loads(Path(a.vdr).read_text()), runs, a.previous_dir or [str(out)]) + if a.new_files: + Path(a.new_files).write_text("".join(f + "\n" for f in files)) + for e in entries: + print(f"security review due {e['dueDate']}: {e['result']}") + print(f"security reviews: {len(index['reviews'])} held; next due {index['nextDueDate']}; rules of behavior " + f"acknowledged at {index['rulesOfBehavior']['currentSha256'][:12]}") + return 0 + + +if __name__ == "__main__": + sys.exit(main()) diff --git a/scripts/inject-figures.py b/scripts/inject-figures.py deleted file mode 100644 index 7b98507e..00000000 --- a/scripts/inject-figures.py +++ /dev/null @@ -1,305 +0,0 @@ -#!/usr/bin/env python3 -# ============================================================================= -# FIGURE INJECTOR (single-source framework-coverage figures for the dashboard) -# ============================================================================= -# Every framework-coverage number on the dashboard is derived from a generated -# artifact, not typed by hand. This script computes those -# figures from the canonical artifacts (the control projection, the component definition, -# the spoke profiles, the dispositions, and the CMMC projector's own output) and -# stamps them into HTML at marked sites: -# -# 331 -#
331/331
-# -# The text between the tags is replaced with the computed value. A marker whose -# key is unknown is an error (the HTML references a figure the build cannot -# produce); a computed key that no marker uses is reported but tolerated. -# -# This keeps the compliance representation honest: change the projection and the -# number on the dashboard changes on the next deploy, because the deploy runs -# this with --check (CI fails if any stamped figure has drifted from its source) -# and then in write mode. It targets the dashboard only. Article and research -# prose are not stamped or checked by the pipeline. -# -# inject-figures.py # stamp all targets in place -# inject-figures.py --check # exit 1 if any marker is stale (CI gate) -# inject-figures.py --print # print the computed figure table and exit -# -# Acceptance: altering the projection's implemented-requirement count changes -# hub_total / hub_generated everywhere they are marked; dropping a baseline -# control from the projection lowers moderate_coverage below N/N. -# ============================================================================= - -import argparse -import importlib.util -import json -import re -import subprocess -import sys -import tempfile -from pathlib import Path - -REPO = Path(__file__).resolve().parent.parent -# The control projection's inputs (scripts/_controls.py): the canonical -# inventory, built by the pipeline and gitignored, and the KSI catalog. -SIGNAL = REPO / "infrastructure" / "ksi-signal.json" -CATALOG = REPO / "infrastructure" / "schemas" / "ksi-catalog.json" - -COMPONENT_DEF = REPO / "data" / "component-definitions" / "samaydlette-com-component-definition.json" -DISPOSITIONS = REPO / "data" / "dispositions" / "beyond-moderate.json" -CATALOG_171 = REPO / "data" / "catalogs" / "NIST_SP-800-171_rev2_catalog.json" - -# The FedRAMP Rev5 Moderate baseline as published, not the hub: the hub adds -# controls beyond the baseline, so hub_total is not the baseline size. -MODERATE_PROFILE = REPO / "data" / "profiles" / "FedRAMP_rev5_MODERATE-baseline_profile.json" - -PROFILES = { - "govramp": REPO / "data" / "profiles" / "govramp_moderate_cjis_profile.json", - "txramp1": REPO / "data" / "profiles" / "txramp_level1_profile.json", - "txramp2": REPO / "data" / "profiles" / "txramp_level2_profile.json", -} - -# No committed page carries stamped figures any more: the trust center renders -# them from /.well-known/trust-center.json, which build-trust-center.py fills -# from compute_figures() on every deploy. Stamping remains available for an -# explicit --targets list. -TARGETS: list = [] - - -def _load_module(name, path): - spec = importlib.util.spec_from_file_location(name, path) - mod = importlib.util.module_from_spec(spec) - spec.loader.exec_module(mod) - return mod - - -def _count_catalog(catalog): - """Count leaf control entries in an OSCAL catalog (recursively).""" - n = 0 - - def walk(group): - nonlocal n - for c in group.get("controls", []) or []: - n += 1 - walk(c) - for sg in group.get("groups", []) or []: - walk(sg) - - walk(catalog["catalog"]) - return n - - -def _profile_selection_ids(path): - """Distinct controls a profile selects via include-controls/with-ids.""" - prof = json.loads(path.read_text())["profile"] - ids = set() - for imp in prof.get("imports", []) or []: - for inc in imp.get("include-controls", []) or []: - ids.update(inc.get("with-ids", []) or []) - return ids - - -def _profile_selection_count(path): - """Count distinct controls a profile selects via include-controls/with-ids.""" - return len(_profile_selection_ids(path)) - - -def _authored_hub_controls(): - """Distinct control-ids with a hand-written implementation in the hub.""" - cd = json.loads(COMPONENT_DEF.read_text())["component-definition"] - ids = set() - for comp in cd.get("components", []) or []: - for ci in comp.get("control-implementations", []) or []: - for ir in ci.get("implemented-requirements", []) or []: - ids.add(ir.get("control-id")) - return len(ids) - - -def _cmmc_figures(): - """Run the CMMC projector and read its JSON output (the same code path the - dashboard's CMMC card describes).""" - with tempfile.NamedTemporaryFile("r", suffix=".json", delete=False) as tmp: - out = tmp.name - subprocess.run( - [sys.executable, str(REPO / "scripts" / "build-cmmc.py"), - "--ksi-signal", str(SIGNAL), "--catalog", str(CATALOG), "--output", out], - check=True, capture_output=True, text=True, - ) - cov = json.loads(Path(out).read_text()) - Path(out).unlink(missing_ok=True) - srm = cov["srm_view"] - return cov, srm - - -def _projection(): - """The control projection's implemented-requirements (scripts/_controls.py).""" - return _load_module("_controls", REPO / "scripts" / "_controls.py").load(SIGNAL, CATALOG) - - -def compute_figures(): - """Compute every stamped figure from canonical artifacts. Returns - {figure_key: string_value}. This is the single source of truth.""" - bc = _load_module("build_coverage", REPO / "scripts" / "build-coverage.py") - irs = _projection() - cov = bc.build_coverage(irs, "FedRAMP Rev5 Moderate") - rs = cov["responsibility_stack"] - - hub_total = cov["in_scope_controls"] - hub_handwritten = _authored_hub_controls() - hub_generated = hub_total - hub_handwritten - mod_impl = rs["implemented"] - mod_inherited = rs["fully-inherited"] + rs["partially-inherited"] - mod_na = rs["not-applicable"] - - # Baseline coverage is measured, not assumed: the projection's control-ids that - # fall inside the published baseline, over the baseline's size. A baseline - # control missing from the projection lowers the numerator; the hub's extra controls are - # counted separately rather than inflating both sides. - baseline_ids = _profile_selection_ids(MODERATE_PROFILE) - control_ids = {ir["control-id"] for ir in irs} - moderate_baseline = len(baseline_ids) - moderate_covered = len(control_ids & baseline_ids) - moderate_beyond = len(control_ids - baseline_ids) - govramp = _profile_selection_count(PROFILES["govramp"]) - txramp1 = _profile_selection_count(PROFILES["txramp1"]) - txramp2 = _profile_selection_count(PROFILES["txramp2"]) - - cmmc_cov, srm = _cmmc_figures() - cmmc_total = cmmc_cov["in_scope_requirements"] - osc_fully = srm["inherited"] - osc_shared = srm["shared"] - osc_resp = srm["osc-responsibility"] - osc_inherits = osc_fully + osc_shared - - return { - # hub - "hub_total": str(hub_total), - "hub_handwritten": str(hub_handwritten), - "hub_generated": str(hub_generated), - # FedRAMP Moderate - "moderate_coverage": f"{moderate_covered}/{moderate_baseline}", - "moderate_baseline": str(moderate_baseline), - "moderate_beyond": str(moderate_beyond), - "moderate_implemented": str(mod_impl), - "moderate_inherited": str(mod_inherited), - "moderate_na": str(mod_na), - # spokes - "govramp_coverage": f"{govramp}/{govramp}", - "txramp1_coverage": f"{txramp1}/{txramp1}", - "txramp2_coverage": f"{txramp2}/{txramp2}", - # CMMC - "cmmc_total": str(cmmc_total), - "cmmc_coverage": f"{cmmc_total}/{cmmc_total}", - "cmmc_osc_inherits": f"{osc_inherits}/{cmmc_total}", - "cmmc_osc_inherits_count": str(osc_inherits), - "cmmc_osc_fully": str(osc_fully), - "cmmc_osc_shared": str(osc_shared), - "cmmc_osc_responsibility": str(osc_resp), - } - - -# Match an element carrying data-figure="KEY" and capture its inner text. -# Attribute order is tolerated (data-figure may precede or follow other attrs). -_MARKER = re.compile( - r'(<(?P\w+)(?P
[^>]*?)\sdata-figure="(?P[\w-]+)"(?P[^>]*?)>)'
-    r'(?P.*?)'
-    r'(?P)',
-    re.DOTALL,
-)
-
-
-def stamp(html, figures, source_label=""):
-    """Replace the inner text of every data-figure marker with its computed
-    value. Returns (new_html, changes, unknown_keys, used_keys)."""
-    changes = []
-    unknown = []
-    used = set()
-
-    def repl(m):
-        key = m.group("key")
-        used.add(key)
-        if key not in figures:
-            unknown.append(key)
-            return m.group(0)
-        new_val = figures[key]
-        old_val = m.group("inner")
-        if old_val != new_val:
-            changes.append((source_label, key, old_val, new_val))
-        return f'{m.group(1)}{new_val}{m.group("close")}'
-
-    new_html = _MARKER.sub(repl, html)
-    return new_html, changes, unknown, used
-
-
-def main():
-    ap = argparse.ArgumentParser(description=__doc__,
-                                 formatter_class=argparse.RawDescriptionHelpFormatter)
-    ap.add_argument("--check", action="store_true",
-                    help="exit 1 if any marked figure is stale (do not write)")
-    ap.add_argument("--print", dest="print_only", action="store_true",
-                    help="print the computed figure table and exit")
-    ap.add_argument("--targets", nargs="*", default=None,
-                    help="override target HTML files (default: the dashboard)")
-    args = ap.parse_args()
-
-    figures = compute_figures()
-
-    if args.print_only:
-        width = max(len(k) for k in figures)
-        for k in sorted(figures):
-            print(f"  {k:<{width}}  {figures[k]}")
-        return 0
-
-    targets = [Path(t) for t in args.targets] if args.targets else TARGETS
-    if not targets:
-        print("inject-figures: no stamp targets; the trust center renders these figures from trust-center.json")
-        return 0
-
-    all_changes = []
-    all_unknown = []
-    all_used = set()
-    pending = []
-    for path in targets:
-        if not path.exists():
-            print(f"error: target not found: {path}", file=sys.stderr)
-            return 2
-        html = path.read_text()
-        new_html, changes, unknown, used = stamp(html, figures, path.name)
-        all_changes.extend(changes)
-        all_unknown.extend((path.name, k) for k in unknown)
-        all_used.update(used)
-        pending.append((path, new_html, html != new_html))
-
-    if all_unknown:
-        for name, key in all_unknown:
-            print(f"error: {name} references unknown figure {key!r}", file=sys.stderr)
-        return 2
-
-    unused = sorted(set(figures) - all_used)
-    if unused:
-        print(f"note: computed figures not stamped anywhere: {', '.join(unused)}",
-              file=sys.stderr)
-
-    if args.check:
-        if all_changes:
-            print("STALE: marked figures do not match their source:", file=sys.stderr)
-            for src, key, old, new in all_changes:
-                print(f"  {src}: {key}: {old!r} -> {new!r}", file=sys.stderr)
-            return 1
-        print(f"figures up to date ({len(all_used)} markers across {len(targets)} files)")
-        return 0
-
-    for path, new_html, changed in pending:
-        if changed:
-            path.write_text(new_html)
-    if all_changes:
-        print(f"stamped {len(all_changes)} figure(s):")
-        for src, key, old, new in all_changes:
-            print(f"  {src}: {key}: {old!r} -> {new!r}")
-    else:
-        print(f"figures already current ({len(all_used)} markers across {len(targets)} files)")
-    return 0
-
-
-if __name__ == "__main__":
-    sys.exit(main())
diff --git a/scripts/issue-ocr.py b/scripts/issue-ocr.py
new file mode 100644
index 00000000..b2e2738d
--- /dev/null
+++ b/scripts/issue-ocr.py
@@ -0,0 +1,179 @@
+#!/usr/bin/env python3
+"""Issue the quarterly Ongoing Certification Report and snapshot the package
+(CCM-OCR-AVL, CCM-OCR-SOR, CDS-CSO-HAD).
+
+On or after each issue date in the CCM calendar, the first run that finds the
+date missing from the published index (ocr-issues.json):
+
+1. builds the frozen report for that date with scripts/build-ocr.py --issue,
+   covering the previous issue to this one: ocr-issue-.json and .md;
+2. copies every certification artifact present in --work (the package as
+   published at that moment, with its signatures) to snapshots// and
+   writes the snapshot manifest snapshot-.json (name, sha256, bytes);
+3. appends the issue to ocr-issues.json with the report's and manifest's
+   sha256, the review date and where its Quarterly Review is published.
+
+Issued files are never rebuilt: an issue already in the index is carried over
+unchanged, and an index that loses or alters an earlier issue fails. The
+publishing workflow signs each new file, refuses to overwrite one that is
+already served, and checks the served bytes against the index.
+
+Writes the list of new files to publish (one per line) to --new-files.
+
+  issue-ocr.py --work DIR --previous-index prev-ocr-issues.json --out DIR \
+      --new-files issued.txt  (plus build-ocr.py's inputs)
+"""
+
+import argparse
+import hashlib
+import importlib.util
+import json
+import shutil
+import sys
+from datetime import datetime, timezone
+from pathlib import Path
+
+sys.path.insert(0, str(Path(__file__).resolve().parent))
+import _ccm  # noqa: E402
+import _decisions  # noqa: E402
+import _fedramp_schema as fs  # noqa: E402
+import _offering  # noqa: E402
+
+REPO = Path(__file__).resolve().parent.parent
+BASE = "https://samaydlette.com/.well-known/"
+# What a snapshot holds: the certification data as published, with signatures.
+SNAPSHOT = [
+    "certification-package-overview.json", "certification-package-overview.md", "certification-package-overview.bundle",
+    "security-decision-record.json", "security-decision-record.md", "security-decision-record.bundle",
+    "ongoing-certification-report.json", "ongoing-certification-report.md", "ongoing-certification-report.bundle",
+    "ksi-signal.json", "ksi-signal.bundle", "vdr-report.json", "vdr-report.bundle",
+    "vdr-detail-report.json", "vdr-detail-report.bundle", "vdr-accepted-vulnerabilities.json",
+    "vdr-accepted-vulnerabilities.bundle", "vdr-history.json", "vdr-history.bundle",
+    "boundary-map.json", "boundary-map.bundle", "policy-index.json", "policy-index.bundle",
+    "availability.json", "availability.bundle", "trust-center.json", "trust-center.bundle",
+    "iiw.csv", "iiw.bundle", "fedramp-certification-reports.json", "fedramp-certification-reports.bundle",
+    "package-submission-log.json", "package-submission-log.bundle",
+]
+# Without these the snapshot is not the certification data, and nothing is issued.
+REQUIRED = ("certification-package-overview.json", "security-decision-record.json",
+            "ongoing-certification-report.json", "ksi-signal.json")
+ACCESS = ("Each issued report is at /.well-known/ocr-issue-.json (and .md), signed (.bundle), and never "
+          "rewritten. The certification data as published on that date is at /.well-known/snapshots//, "
+          "each file with its original signature, listed with sha256s in the signed manifest "
+          "/.well-known/snapshot-.json. Snapshots are kept for the duration of certification. Verify a file: "
+          "compare its sha256 with the manifest, and its signature with cosign as in docs/verification.md.")
+
+
+def _fail(msg):
+    raise SystemExit(f"::error::OCR issue: {msg} (fail-closed)")
+
+
+def _sha(path):
+    return hashlib.sha256(Path(path).read_bytes()).hexdigest()
+
+
+def _ocr_builder():
+    spec = importlib.util.spec_from_file_location("build_ocr", REPO / "scripts" / "build-ocr.py")
+    mod = importlib.util.module_from_spec(spec)
+    spec.loader.exec_module(mod)
+    return mod
+
+
+def check_index(prev, cal):
+    """The previous index, checked: known schema, only calendar dates, in order."""
+    if not prev:
+        return []
+    if prev.get("schema") != "ocr-issues/1" or not isinstance(prev.get("issues"), list):
+        _fail("the published ocr-issues.json is not an ocr-issues/1 index")
+    dates = [i.get("issueDate") for i in prev["issues"]]
+    if dates != sorted(dates) or len(set(dates)) != len(dates):
+        _fail("the published index is out of order or repeats an issue")
+    for d in dates:
+        if d not in {x.isoformat() for x in cal.issues}:
+            _fail(f"the published index lists {d}, which is not a calendar issue date")
+    return prev["issues"]
+
+
+def snapshot(work, out, issue, fedramp_id, now):
+    missing = [f for f in REQUIRED if not (work / f).exists()]
+    if missing:
+        _fail(f"cannot snapshot the package for {issue}: {', '.join(missing)} missing")
+    d = out / "snapshots" / issue
+    d.mkdir(parents=True, exist_ok=True)
+    files = []
+    for name in SNAPSHOT:
+        src = work / name
+        if src.exists():
+            shutil.copyfile(src, d / name)
+            files.append({"name": name, "url": f"{BASE}snapshots/{issue}/{name}", "sha256": _sha(src),
+                          "bytes": src.stat().st_size})
+    manifest = {"schema": "snapshot/1", "ocrIssue": issue, "takenAt": now.isoformat(), "fedRampId": fedramp_id,
+                "certificationPackageOverviewUri": fs.CPO_URI, "access": ACCESS, "files": files}
+    (out / f"snapshot-{issue}.json").write_text(json.dumps(manifest, indent=2) + "\n")
+    return [f"snapshots/{issue}/{f['name']}" for f in files] + [f"snapshot-{issue}.json"]
+
+
+def run(a, now):
+    today = now.date()
+    cal = _ccm.load(a.calendar, today)
+    off = _offering.load(a.offering)
+    work, out = Path(a.work), Path(a.out)
+    out.mkdir(parents=True, exist_ok=True)
+    prev = json.loads(Path(a.previous_index).read_text()) if a.previous_index and Path(a.previous_index).exists() else {}
+    issues = list(check_index(prev, cal))
+    have = {i["issueDate"] for i in issues}
+    new_files = []
+    ocr = _ocr_builder()
+    for d in cal.issued(today):
+        if d.isoformat() in have:
+            continue
+        iso = d.isoformat()
+        name = f"ocr-issue-{iso}"
+        doc = ocr.build(cal, today, ocr._load_json(a.vdr), _decisions.load(a.decisions), ocr._scn_rows(a.scn_register),
+                        ocr._load_json(a.incidents), ocr._load_json(a.ksi_signal),
+                        json.loads(Path(a.profile).read_text()), off, {}, now, d)
+        fs.write_validated(doc, "ocr", out / f"{name}.json")
+        (out / f"{name}.md").write_text(ocr.render_markdown(doc) + "\n")
+        snap = snapshot(work, out, iso, off["fedramp_id"], now)
+        issues.append({"issueDate": iso, "issuedAt": now.isoformat(), "late": today > d,
+                       "reportPeriod": doc["reportPeriod"],
+                       "report": f"{BASE}{name}.json", "reportMarkdown": f"{BASE}{name}.md",
+                       "reportSha256": _sha(out / f"{name}.json"),
+                       "snapshotManifest": f"{BASE}snapshot-{iso}.json",
+                       "snapshotManifestSha256": _sha(out / f"snapshot-{iso}.json"),
+                       "quarterlyReviewDate": cal.review_date(d).isoformat(),
+                       "quarterlyReview": _ccm.review_url(d)})
+        new_files += [f"{name}.json", f"{name}.md", *snap]
+    issues.sort(key=lambda i: i["issueDate"])
+    index = {"schema": "ocr-issues/1", "generated_at": now.isoformat(), "fedRampId": off["fedramp_id"],
+             "certificationPackageOverviewUri": fs.CPO_URI,
+             "continuousMonitoring": _ccm.dates_summary(cal, today), "access": ACCESS, "issues": issues}
+    (out / "ocr-issues.json").write_text(json.dumps(index, indent=2) + "\n")
+    if a.new_files:
+        Path(a.new_files).write_text("".join(f + "\n" for f in new_files))
+    return index, new_files
+
+
+def main(argv=None):
+    ap = argparse.ArgumentParser(description=__doc__, formatter_class=argparse.RawDescriptionHelpFormatter)
+    ap.add_argument("--work", required=True, help="directory holding the package as published")
+    ap.add_argument("--out", required=True)
+    ap.add_argument("--previous-index", default=None)
+    ap.add_argument("--new-files", default=None)
+    ap.add_argument("--calendar", default=str(_ccm.CALENDAR_PATH))
+    ap.add_argument("--offering", default=str(_offering.OFFERING_PATH))
+    ap.add_argument("--profile", default=str(REPO / "data" / "system-profile.json"))
+    ap.add_argument("--vdr", default="vdr-report.json")
+    ap.add_argument("--decisions", default=str(REPO / "data" / "decisions.json"))
+    ap.add_argument("--scn-register", default=str(REPO / "docs" / "scn" / "scn-register.csv"))
+    ap.add_argument("--ksi-signal", default="ksi-signal.json")
+    ap.add_argument("--incidents", default=str(REPO / "data" / "incidents.json"))
+    a = ap.parse_args(argv)
+    index, new = run(a, datetime.now(timezone.utc))
+    print(f"ocr-issues: {len(index['issues'])} issued; {len([f for f in new if f.startswith('ocr-issue-')]) // 2} "
+          f"new this run; next {index['continuousMonitoring']['nextOngoingCertificationReportDate']}")
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())
diff --git a/scripts/kev-gate.py b/scripts/kev-gate.py
new file mode 100644
index 00000000..f83542f5
--- /dev/null
+++ b/scripts/kev-gate.py
@@ -0,0 +1,127 @@
+#!/usr/bin/env python3
+"""KEV gate before activation (VDR-CSO-AKE).
+
+Providers SHOULD NOT deploy or activate new machine-based resources with Known
+Exploited Vulnerabilities. The VDR build's G1 blocks a KEV finding, but in the
+deploy it runs after `terraform apply` and the website sync: a Lambda package or
+SPA bundle with a KEV dependency would already be live when it fails. This gate
+runs before the plan and apply, over the same scanner output the VDR reads
+(Grype over every dependency tree, open Dependabot alerts), and stops the deploy
+when any matched CVE is in the CISA catalog. It names each KEV with the
+catalog's due date (VDR-TFR-KEV).
+
+It follows the governed mode of G1's check, `vdr.kev`, in
+infrastructure/schemas/gate-modes.json: in block mode (the decided mode) a KEV
+stops the deploy, dispositioned or not; a detect-and-recover mode would record
+an event instead. A missing or unreadable input stops it: no catalog or no scan
+output cannot read as "no KEV". (The detection gate, G7, has already checked
+that each feed is present and fresh.)
+
+    kev-gate.py --kev kev-catalog.json --grype grype-*.json --dependabot dependabot-alerts.json
+"""
+
+import argparse
+import json
+import sys
+from pathlib import Path
+
+sys.path.insert(0, str(Path(__file__).resolve().parent))
+import _gates  # noqa: E402
+
+CHECK = "vdr.kev"
+
+
+def _fail(msg):
+    raise SystemExit(f"::error::KEV gate (VDR-CSO-AKE): {msg} (fail-closed)")
+
+
+def _load(path, what):
+    p = Path(path)
+    if not p.is_file():
+        _fail(f"{what} {path} not found")
+    try:
+        return json.loads(p.read_text(encoding="utf-8"))
+    except (json.JSONDecodeError, UnicodeDecodeError) as exc:
+        _fail(f"{what} {path} is not valid JSON: {exc.__class__.__name__}")
+
+
+def load_catalog(path):
+    """{cveID: {dueDate, dateAdded, name}} from the CISA KEV catalog."""
+    doc = _load(path, "KEV catalog")
+    vulns = doc.get("vulnerabilities") if isinstance(doc, dict) else None
+    if not isinstance(vulns, list) or not vulns:
+        _fail(f"KEV catalog {path} has no vulnerabilities[]")
+    return {v["cveID"]: {"due_date": v.get("dueDate"), "date_added": v.get("dateAdded"),
+                         "name": v.get("vulnerabilityName")}
+            for v in vulns if isinstance(v, dict) and isinstance(v.get("cveID"), str)}
+
+
+def grype_cves(path):
+    """[(cve, package@version, source file)] for every Grype match, including a
+    CVE named only as a related vulnerability of a GHSA match."""
+    doc = _load(path, "Grype output")
+    if not isinstance(doc, dict) or not isinstance(doc.get("matches", []), list):
+        _fail(f"Grype output {path} has no matches[]")
+    out = []
+    for m in doc.get("matches") or []:
+        art = m.get("artifact") or {}
+        where = f"{art.get('name')}@{art.get('version')}"
+        ids = [(m.get("vulnerability") or {}).get("id")]
+        ids += [r.get("id") for r in m.get("relatedVulnerabilities") or [] if isinstance(r, dict)]
+        for i in ids:
+            if isinstance(i, str) and i.upper().startswith("CVE-"):
+                out.append((i.upper(), where, Path(path).name))
+    return out
+
+
+def dependabot_cves(path):
+    doc = _load(path, "Dependabot alerts")
+    if not isinstance(doc, list):
+        _fail(f"Dependabot alerts {path} is not a list")
+    out = []
+    for a in doc:
+        adv = (a or {}).get("security_advisory") or {}
+        pkg = ((a or {}).get("dependency") or {}).get("package") or {}
+        ids = [adv.get("cve_id")] + [i.get("value") for i in adv.get("identifiers") or []
+                                     if isinstance(i, dict) and i.get("type") == "CVE"]
+        for i in {x.upper() for x in ids if isinstance(x, str) and x.upper().startswith("CVE-")}:
+            out.append((i, pkg.get("name") or "?", Path(path).name))
+    return out
+
+
+def kev_hits(catalog, matches):
+    """Sorted unique [(cve, where, file, due_date)] for matches in the catalog."""
+    return sorted({(c, w, f, catalog[c]["due_date"]) for c, w, f in matches if c in catalog})
+
+
+def main(argv=None):
+    ap = argparse.ArgumentParser()
+    ap.add_argument("--kev", required=True)
+    ap.add_argument("--grype", nargs="+", required=True)
+    ap.add_argument("--dependabot", required=True)
+    a = ap.parse_args(argv)
+    catalog = load_catalog(a.kev)
+    matches = [m for g in a.grype for m in grype_cves(g)] + dependabot_cves(a.dependabot)
+    hits = kev_hits(catalog, matches)
+    gates = _gates.load_gate_modes()
+    print(f"KEV gate: {len(matches)} CVE match(es) across {len(a.grype)} Grype scan(s) and Dependabot; "
+          f"{len(catalog)} CVEs in the catalog; {len(hits)} known exploited.")
+    if not hits:
+        return 0
+    for cve, where, src, due in hits:
+        # Scanner text goes into a GitHub Actions log, which parses `::` commands:
+        # _clean strips line breaks and `::` from it.
+        line = _gates._clean(f"{cve} in {where} ({src}) is in the CISA KEV catalog, due {due or 'no due date'}")
+        if _gates.blocks(gates, CHECK):
+            print(f"::error::{line}", file=sys.stderr)
+        else:
+            _gates.record_event(gates, CHECK, f"pre-apply: {line}")
+    if _gates.blocks(gates, CHECK):
+        print(f"::error::KEV gate: {len(hits)} known exploited vulnerabilit(y/ies) would be deployed; "
+              "remediate before activation (VDR-CSO-AKE).", file=sys.stderr)
+        return 1
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())
diff --git a/scripts/publish-certification-reports.py b/scripts/publish-certification-reports.py
new file mode 100644
index 00000000..44de784b
--- /dev/null
+++ b/scripts/publish-certification-reports.py
@@ -0,0 +1,158 @@
+#!/usr/bin/env python3
+"""Publish FedRAMP Certification Reports unmodified, within two weeks (CDS-CSO-FRC).
+
+FedRAMP is SIMULATED for this proof of concept. The simulated FedRAMP issues a
+stand-in certification report only in response to a simulated package
+submission (scripts/submit-package.py): for the first submission, after any
+adaptive or transformative Significant Change Notification, and once a year.
+Each report is logged verbatim, with the date received and its sha256, in
+that submission's entry of the append-only package-submission-log.json. An
+ordinary deploy issues none.
+
+This reads this deploy's submission log and, for every logged report:
+
+  - checks the report says, in its title and first line, that it is a
+    simulated report NOT ISSUED BY FEDRAMP and that the system is not
+    certified (a report that does not is never published);
+  - checks its bytes against the sha256 logged when it was received (an
+    edited report fails the deploy: the rule forbids inappropriate
+    modification);
+  - writes it byte-identical to --out/fedramp-certification-reports/;
+
+and writes the index --out/fedramp-certification-reports.json (signed by the
+deploy). The index carries each report's first publication date over from the
+previously published index, so the days from receipt to publication are a
+matter of record, and a report first published more than 2 weeks after
+receipt FAILS THE DEPLOY. Nothing is received from or sent to the real FedRAMP.
+
+  publish-certification-reports.py --submission-log package-submission-log.json \
+      --previous prev-index.json --out DIR
+"""
+
+import argparse
+import hashlib
+import json
+import sys
+from datetime import date, datetime, timezone
+from pathlib import Path
+
+sys.path.insert(0, str(Path(__file__).resolve().parent))
+import _fedramp_schema as fs  # noqa: E402
+import _engagement  # noqa: E402
+import _offering  # noqa: E402
+
+BASE = "https://samaydlette.com/.well-known/fedramp-certification-reports/"
+WINDOW_DAYS = 14
+INDEX_SCHEMA = "fedramp-certification-reports-index/1"
+NOT_ISSUED = "NOT ISSUED BY FEDRAMP"
+NOT_CERTIFIED = "NOT FedRAMP certified"
+SIMULATION = ("FedRAMP is simulated: this proof of concept has no FedRAMP counterpart. Every report listed was "
+              "written by a Python function standing in for FedRAMP, in response to a simulated package "
+              "submission, and says so in its title. The system is not certified. Nothing was received from or "
+              "sent to FedRAMP.")
+
+
+def _fail(msg):
+    raise SystemExit(f"::error::FedRAMP certification reports: {msg} (fail-closed)")
+
+
+def report_bytes(report):
+    """The report exactly as received (scripts/submit-package.py logs its sha256)."""
+    return (json.dumps(report, indent=2, ensure_ascii=False) + "\n").encode("utf-8")
+
+
+def logged_reports(log):
+    """Every certification report in the submission log, checked."""
+    if not isinstance(log, dict) or log.get("schema") != "package-submission-log/1":
+        _fail("the submission log is not a package-submission-log/1 document")
+    out, files = [], set()
+    for e in log.get("entries") or []:
+        r = e.get("certificationReport") if isinstance(e, dict) else None
+        if r is None:
+            continue
+        f = r.get("file")
+        if not isinstance(f, str) or "/" in f or f.startswith(".") or not f.endswith(".json") or f in files:
+            _fail(f"bad or repeated report file name {f!r}")
+        files.add(f)
+        try:
+            date.fromisoformat(r.get("receivedOn", ""))
+        except (TypeError, ValueError):
+            _fail(f"{f}: receivedOn is not a date")
+        report = r.get("report")
+        if not isinstance(report, dict):
+            _fail(f"{f}: the logged report is missing")
+        raw = report_bytes(report)
+        first = raw.decode("utf-8").splitlines()[1]  # the first line of content, after "{"
+        title = str(report.get("title", ""))
+        if not first.lstrip().startswith('"title"') or NOT_ISSUED not in title or NOT_CERTIFIED not in title:
+            _fail(f"{f}: the report's title and first line must say it is a simulated report {NOT_ISSUED} and "
+                  "that the system is not certified; it is never published otherwise")
+        if hashlib.sha256(raw).hexdigest() != r.get("sha256"):
+            _fail(f"{f} differs from the sha256 logged when it was received: reports are published unmodified")
+        out.append((r, raw))
+    return out
+
+
+def build(log, previous, now, out):
+    today = now.date()
+    first = {e["file"]: e["firstPublished"] for e in (previous or {}).get("reports", [])
+             if isinstance(e, dict) and e.get("file") and e.get("firstPublished")}
+    (out / "fedramp-certification-reports").mkdir(parents=True, exist_ok=True)
+    entries = []
+    for r, raw in logged_reports(log):
+        (out / "fedramp-certification-reports" / r["file"]).write_bytes(raw)
+        published = first.get(r["file"], today.isoformat())
+        days = (date.fromisoformat(published) - date.fromisoformat(r["receivedOn"])).days
+        entries.append({"file": r["file"], "url": BASE + r["file"], "sha256": r["sha256"],
+                        "receivedOn": r["receivedOn"], "from": r.get("from"), "trigger": r.get("trigger"),
+                        "firstPublished": published, "daysToPublish": days, "withinTwoWeeks": days <= WINDOW_DAYS,
+                        "simulated": True, "notIssuedByFedRAMP": True})
+    return {"schema": INDEX_SCHEMA, "generated_at": now.isoformat(),
+            "fedRampId": _offering.fedramp_id(), "certificationPackageOverviewUri": fs.CPO_URI,
+            "certificationStatus": _offering.CERTIFICATION_STATUS,
+            "simulated": {"counterparty": "fedramp", "how": SIMULATION},
+            # DEC-194. On the index, not in the reports: each is published
+            # byte-identical to the log's copy (its sha256 is checked).
+            "engagement": _engagement.STATEMENT,
+            "rule": "CDS-CSO-FRC: FedRAMP Certification Reports are included unmodified and made available within "
+                    "2 weeks of receipt.",
+            "reports": entries}
+
+
+def late(index):
+    return [e for e in index["reports"] if not e["withinTwoWeeks"]]
+
+
+def main(argv=None):
+    ap = argparse.ArgumentParser(description=__doc__, formatter_class=argparse.RawDescriptionHelpFormatter)
+    ap.add_argument("--submission-log", required=True, help="this deploy's package-submission-log.json")
+    ap.add_argument("--previous", default=None, help="the previously published index (absent: never published)")
+    ap.add_argument("--out", default=".")
+    a = ap.parse_args(argv)
+    now = datetime.now(timezone.utc)
+    try:
+        log = json.loads(Path(a.submission_log).read_text())
+    except (OSError, ValueError) as exc:
+        _fail(f"cannot read the submission log ({type(exc).__name__})")
+    prev = {}
+    if a.previous and Path(a.previous).exists():
+        try:
+            prev = json.loads(Path(a.previous).read_text())
+        except ValueError:
+            _fail("the previously published index is not JSON; refusing to restart the publication record")
+        if prev.get("schema") != INDEX_SCHEMA:
+            _fail(f"the previously published index is not a {INDEX_SCHEMA} document")
+    out = Path(a.out)
+    idx = build(log, prev, now, out)
+    overdue = late(idx)
+    if overdue:
+        _fail("; ".join(f"{e['file']} was first published {e['daysToPublish']} days after receipt, past the "
+                        f"{WINDOW_DAYS}-day window" for e in overdue))
+    (out / "fedramp-certification-reports.json").write_text(json.dumps(idx, indent=2) + "\n")
+    print(f"fedramp-certification-reports: {len(idx['reports'])} report(s) published unmodified (simulated FedRAMP;"
+          " not certified)")
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())
diff --git a/scripts/reconcile.py b/scripts/reconcile.py
index 5f187a81..3a9a8177 100644
--- a/scripts/reconcile.py
+++ b/scripts/reconcile.py
@@ -42,6 +42,16 @@
 #                        every boundary component of the inventory (no more, no
 #                        fewer), leaves none unclassified, and carries no ARN,
 #                        account ID or email address
+#   (m) incident findings — every finding or CVE an unresolved incident in the
+#                        incident register (data/incidents.json) names is in
+#                        this build's VDR report; exercises are exempt (their
+#                        findings are simulated)
+#   (n) runtime V&V coverage — every machine component in the inventory has an
+#                        assessed validation in a verified runtime signal no
+#                        older than the governed window (VDR-TFR-MVX, 72h);
+#                        every component type is classified machine or excluded
+#                        in infrastructure/schemas/runtime-vv-config.json
+#                        (with --runtime-signal; run by evidence-nightly.yml)
 #
 # Usage:
 #   reconcile.py --artifacts-dir infrastructure [--live] [--expect-commit SHA]
@@ -64,6 +74,8 @@
 sys.path.insert(0, str(Path(__file__).resolve().parent))
 import _decisions  # noqa: E402
 import _gates  # noqa: E402
+import _incidents  # noqa: E402
+import _offering  # noqa: E402
 import _redact  # noqa: E402
 
 REPO = Path(__file__).resolve().parent.parent
@@ -369,12 +381,20 @@ def check_c_suppressions(checkov_skips, register, vdr):
 # ----------------------------------------------------------------------------
 # (d) impact level identical; nothing asserts Low
 # ----------------------------------------------------------------------------
+def sdr_fields(sdr):
+    """Where a CR26 report (the SDR, the CPO) keeps its site-specific fields:
+    under providerExtensions since it follows FedRAMP's schema (the top level is
+    FedRAMP's). A report in the older shape keeps them at the top level."""
+    pe = sdr.get("providerExtensions")
+    return pe if isinstance(pe, dict) else sdr
+
+
 def extract_impacts(signal, sdr, cpo, vdr, dashboard_html):
     impacts = {}
     impacts["signal"] = normalize_impact(
         signal.get("categorization", {}).get("impact_level"))
-    impacts["sdr"] = normalize_impact(sdr.get("impact_level"))
-    impacts["cpo"] = normalize_impact(cpo.get("impact_level"))
+    impacts["sdr"] = normalize_impact(sdr_fields(sdr).get("impact_level"))
+    impacts["cpo"] = normalize_impact(sdr_fields(cpo).get("impact_level"))
     impacts["vdr"] = normalize_impact(vdr.get("impact_level") or
                                       ("class " + vdr.get("class", "")).strip())
     # dashboard (the trust center page, website/trust/index.html): its static
@@ -406,7 +426,7 @@ def check_e_binding(signal, sdr, cpo, vdr):
     sid = signal.get("signal_id")
     if not sid:
         return ["(e) signal has no signal_id"]
-    for art, doc in (("vdr", vdr), ("sdr", sdr), ("cpo", cpo)):
+    for art, doc in (("vdr", vdr), ("sdr", sdr_fields(sdr)), ("cpo", sdr_fields(cpo))):
         got = doc.get("ksi_signal_id")
         if got != sid:
             violations.append(f"(e) {art} signal_id {got!r} != inventory signal_id {sid!r}")
@@ -525,9 +545,106 @@ def check_l_boundary_map(signal, boundary_map, expected_commit=None):
     return violations
 
 
+def check_m_incident_findings(vdr, incidents):
+    """(m) Every finding an unresolved, non-exercise incident names (a VDR
+    tracking ID or a CVE ID) is in this build's VDR report. An incident about a
+    vulnerability the VDR does not carry is reporting on something the
+    vulnerability evidence says is not there: one of the two is wrong."""
+    if incidents is None:
+        return []
+    ids, cves = set(), set()
+    for f in _all_vdr_findings(vdr):
+        ids.add(f.get("tracking_id"))
+        if f.get("cve"):
+            cves.add(f["cve"])
+    return [f"(m) incident {inc_id} names {ref!r}, which is not in the VDR report"
+            for ref, inc_id in sorted(_incidents.open_findings(incidents).items())
+            if ref not in ids and ref not in cves]
+
+
+# ----------------------------------------------------------------------------
+# (n) runtime V&V coverage — VDR-TFR-MVX requires machine-based resources to be
+# verified and validated at least every 3 days. The daily runtime emitter
+# re-evaluates every machine component's live configuration against the deploy
+# gate's policy; this invariant proves it did, from the signed result, for every
+# machine component of the inventory. A validation that could not read an
+# attribute (any category "input" violation: resource_read_error,
+# package_integrity_unverifiable, ...) is unassessed and does not count, and a
+# component with any unassessed validation is not validated.
+# ----------------------------------------------------------------------------
+RUNTIME_VV_CONFIG = REPO / "infrastructure" / "schemas" / "runtime-vv-config.json"
+
+
+def load_runtime_vv_config(path=RUNTIME_VV_CONFIG):
+    """The governed runtime V&V scope; raises ValueError when it is unusable."""
+    cfg = load_json(path)
+    for key in ("decided_by", "decided_on", "review_by"):
+        if not cfg.get(key):
+            raise ValueError(f"runtime V&V config has no {key}")
+    hours = cfg.get("max_age_hours")
+    if not isinstance(hours, int) or isinstance(hours, bool) or not 0 < hours <= 72:
+        raise ValueError("runtime V&V config max_age_hours must be an integer in (0, 72] (VDR-TFR-MVX)")
+    machine = cfg.get("machine_types")
+    excluded = cfg.get("excluded_types")
+    if not isinstance(machine, dict) or not machine or not isinstance(excluded, dict):
+        raise ValueError("runtime V&V config needs machine_types and excluded_types")
+    both = set(machine) & set(excluded)
+    if both:
+        raise ValueError(f"runtime V&V config lists {sorted(both)} as both machine and excluded")
+    for t, entry in machine.items():
+        if not isinstance(entry, dict) or not isinstance(entry.get("likely_to_drift"), bool) or not entry.get("why"):
+            raise ValueError(f"runtime V&V config machine type {t} needs likely_to_drift and why")
+    for t, why in excluded.items():
+        if not isinstance(why, str) or not why.strip():
+            raise ValueError(f"runtime V&V config excluded type {t} needs a reason")
+    return cfg
+
+
+def _unassessed(validation):
+    return any(isinstance(v, dict) and v.get("category") == "input"
+               for v in validation.get("violations") or [])
+
+
+def check_n_runtime_coverage(signal, runtime, config):
+    """`runtime` is build-vdr-report.load_runtime_signal()'s result, loaded with
+    the config's max_age_hours: {verified, fresh, reason, validations}."""
+    violations = []
+    machine = set(config["machine_types"])
+    excluded = set(config["excluded_types"])
+    for t in sorted({c.get("type") for c in signal.get("components", [])} - machine - excluded):
+        violations.append(f"(n) component type {t} is neither a machine type nor excluded in runtime-vv-config.json")
+    if not (runtime or {}).get("verified") or not runtime.get("fresh"):
+        reason = (runtime or {}).get("reason") or "runtime signal not verified or not fresh"
+        return violations + [f"(n) no usable runtime V&V within {config['max_age_hours']}h: {reason}"]
+    assessed, unassessed = set(), set()
+    for v in runtime.get("validations") or []:
+        target = unassessed if _unassessed(v) else assessed
+        target.update(v.get("component_refs") or [])
+    for c in signal.get("components", []):
+        if c.get("type") not in machine:
+            continue
+        cid = c.get("component_id")
+        if cid in unassessed:
+            violations.append(f"(n) {cid}: the runtime check could not read all of its configuration (unassessed)")
+        elif cid not in assessed:
+            violations.append(f"(n) {cid}: no runtime validation within {config['max_age_hours']}h")
+    return violations
+
+
+def load_verified_runtime(path, max_age_hours):
+    """The runtime signal verified and age-checked by the VDR builder's own
+    loader (signature against the pinned key infrastructure/keys/)."""
+    import importlib.util
+    spec = importlib.util.spec_from_file_location("vdr_builder", REPO / "scripts" / "build-vdr-report.py")
+    mod = importlib.util.module_from_spec(spec)
+    assert spec.loader is not None
+    spec.loader.exec_module(mod)
+    return mod.load_runtime_signal(path, max_age_hours=max_age_hours)
+
+
 def run_all(signal, sdr, cpo, vdr, dashboard_html, checkov_text, register,
             live_arns=None, expected_commit=None, live_tags=None,
-            boundary_map=None):
+            boundary_map=None, incidents=None, runtime=None, runtime_config=None):
     violations = []
     violations += check_d_impact(signal, sdr, cpo, vdr, dashboard_html)
     violations += check_e_binding(signal, sdr, cpo, vdr)
@@ -537,10 +654,13 @@ def run_all(signal, sdr, cpo, vdr, dashboard_html, checkov_text, register,
     violations += check_h_finding_coverage(vdr, register)
     violations += check_j_decision_id_validity(signal, sdr, cpo, vdr, register)
     violations += check_l_boundary_map(signal, boundary_map, expected_commit)
+    violations += check_m_incident_findings(vdr, incidents)
     if live_arns is not None:
         violations += check_a_completeness(signal, live_arns)
     if live_tags is not None:
         violations += check_i_classification_tags(signal, live_tags)
+    if runtime_config is not None:
+        violations += check_n_runtime_coverage(signal, runtime, runtime_config)
     return violations
 
 
@@ -562,6 +682,13 @@ def main():
                     help="path to .checkov.yaml (overridable for hermetic tests)")
     ap.add_argument("--decisions", default=str(_decisions.DEFAULT_PATH),
                     help="the decision register (overridable for hermetic tests); missing or invalid fails closed")
+    ap.add_argument("--incidents", default=str(_incidents.DEFAULT_PATH),
+                    help="the incident register (overridable for hermetic tests); missing or invalid fails closed")
+    ap.add_argument("--runtime-signal", default=None,
+                    help="the published runtime signal; checks invariant (n) runtime V&V coverage. "
+                         "A path that does not exist fails (n), never skips it")
+    ap.add_argument("--runtime-vv-config", default=str(RUNTIME_VV_CONFIG),
+                    help="the governed runtime V&V scope (invariant n)")
     args = ap.parse_args()
     gates = _gates.load_gate_modes()
 
@@ -583,6 +710,7 @@ def main():
     dashboard_html = Path(args.dashboard).read_text() if Path(args.dashboard).exists() else None
     checkov_text = Path(args.checkov).read_text()
     register = _decisions.load(args.decisions)
+    incidents = _incidents.load(args.incidents)
 
     live_arns = None
     live_tags = None
@@ -614,10 +742,19 @@ def main():
             else:
                 raise
 
+    runtime = runtime_config = None
+    if args.runtime_signal:
+        try:
+            runtime_config = load_runtime_vv_config(args.runtime_vv_config)
+        except (OSError, ValueError) as e:
+            print(f"reconcile: runtime V&V config unusable: {e}", file=sys.stderr)
+            return 1
+        runtime = load_verified_runtime(args.runtime_signal, runtime_config["max_age_hours"])
+
     violations = run_all(
         signal, sdr, cpo, vdr, dashboard_html, checkov_text, register,
         live_arns=live_arns, expected_commit=args.expect_commit, live_tags=live_tags,
-        boundary_map=boundary_map,
+        boundary_map=boundary_map, incidents=incidents, runtime=runtime, runtime_config=runtime_config,
     )
 
     # Each violation names its invariant, "(x) ..."; its check's governed mode
@@ -637,13 +774,14 @@ def main():
             print(f"  ✗ {v}", file=sys.stderr)
         return 1
     optional = ",l" if boundary_map is not None else ""
+    optional += ",m" if runtime_config is not None else ""
     if live_arns is not None and live_tags is not None:
-        checks = "a-f,h-j" + optional
+        checks = "a-f,h-j" + optional + ",m"
     elif live_arns is not None:
-        checks = "a-f,h,j" + optional + " (i deferred: no live tags)"
+        checks = "a-f,h,j" + optional + ",m (i deferred: no live tags)"
     else:
-        checks = "b-f,h,j" + optional + " (a,i deferred: no --live)"
-    print(f"reconciliation OK — invariants {checks} hold across signal/VDR/SDR/CPO/decisions/dashboard")
+        checks = "b-f,h,j" + optional + ",m (a,i deferred: no --live)"
+    print(f"reconciliation OK — invariants {checks} hold across signal/VDR/SDR/CPO/decisions/incidents/dashboard")
     if args.report:
         Path(args.report).write_text(json.dumps(build_report(
             signal, args.expect_commit,
@@ -666,13 +804,17 @@ def main():
     "j": "Every decision reference resolves",
     # (k) is retired: the bundle it bound is no longer published by this site.
     "l": "The boundary map describes exactly this build's inventory",
+    "m": "Every finding an open incident names is in the VDR report",
 }
+# (n) runtime V&V coverage runs only in evidence-nightly.yml, which writes no
+# report; it is not in the governed gate-mode register (_gates.CHECKS), so a
+# violation always blocks.
 
 
 def build_report(signal, commit, deferred):
     """Written only when the gate passes; nothing is published otherwise, so a
     published report is itself evidence that every listed invariant held."""
-    return {
+    return _offering.stamp_fedramp_id({
         "schema": "reconcile-report/1",
         "result": "pass",
         "generated_at": datetime.now(timezone.utc).replace(microsecond=0).isoformat(),
@@ -682,7 +824,7 @@ def build_report(signal, commit, deferred):
             {"id": k, "title": t, "status": "deferred" if deferred.get(k) else "held"}
             for k, t in INVARIANT_TITLES.items()
         ],
-    }
+    })
 
 
 if __name__ == "__main__":
diff --git a/scripts/scn-evaluate.py b/scripts/scn-evaluate.py
new file mode 100644
index 00000000..808c5cae
--- /dev/null
+++ b/scripts/scn-evaluate.py
@@ -0,0 +1,81 @@
+#!/usr/bin/env python3
+"""The SCN gate (SCN-CSO-EVA): every change carries an explicit evaluation.
+
+Run by .github/workflows/scn-tag.yml over a pull request's description (or a
+direct push's commit message). Passes only when the text carries:
+
+    SCN-Type: not-significant | routine-recurring | adaptive | transformative | emergency | class-change
+    SCN-Rationale: one line on why the change is that type
+    SCN-Record: SCN-YYYY-NNN        (adaptive, transformative and emergency only)
+
+There is no default: a missing or placeholder evaluation fails. class-change
+always fails: a change of certification class is a new certification. A
+transformative change fails until its initial plan has been published for 30
+business days and its final plan for 10 (SCN-TRF-NIP/NFP), read from the
+published notification index. Exit 0 pass, 1 fail.
+
+    scn-evaluate.py --text-env PR_BODY --source "PR description"
+    scn-evaluate.py --text-file body.md --index-file index.json --today 2026-11-05
+"""
+
+import argparse
+import json
+import os
+import sys
+import urllib.error
+import urllib.request
+from datetime import date
+from pathlib import Path
+
+sys.path.insert(0, str(Path(__file__).resolve().parent))
+import _scn  # noqa: E402
+
+INDEX_URL = _scn.BASE + _scn.INDEX_NAME + ".json"
+
+
+def fetch_index(url):
+    try:
+        with urllib.request.urlopen(url, timeout=30) as r:  # noqa: S310 (fixed https URL)
+            return json.loads(r.read())
+    except urllib.error.HTTPError as exc:
+        if exc.code == 404:
+            return {"notifications": []}
+        return None
+    except (urllib.error.URLError, TimeoutError, json.JSONDecodeError):
+        return None
+
+
+def main(argv=None):
+    ap = argparse.ArgumentParser(description=__doc__.split("\n")[0])
+    src = ap.add_mutually_exclusive_group(required=True)
+    src.add_argument("--text-env", help="environment variable holding the text")
+    src.add_argument("--text-file", help="file holding the text")
+    ap.add_argument("--source", default="change description", help="what the text is, for messages")
+    ap.add_argument("--index-file", help="the notification index (default: fetch the published one)")
+    ap.add_argument("--index-url", default=INDEX_URL)
+    ap.add_argument("--today", help="ISO date (tests)")
+    a = ap.parse_args(argv)
+
+    text = os.environ.get(a.text_env, "") if a.text_env else Path(a.text_file).read_text()
+    today = date.fromisoformat(a.today) if a.today else date.today()
+    needs_index = _scn.TYPE_LINE.search(text or "") and \
+        _scn.normalize_type(_scn.TYPE_LINE.search(text).group(1)) == "transformative"
+    index = None
+    if needs_index:
+        index = json.loads(Path(a.index_file).read_text()) if a.index_file else fetch_index(a.index_url)
+
+    errors, notices, ev = _scn.gate(text, index, today)
+    for n in notices:
+        print(f"::notice::{n}")
+    if errors:
+        for e in errors:
+            print(f"::error::SCN evaluation ({a.source}): {e}")
+        print("See docs/policies/cm-policy.md and docs/scn/evaluation-examples.md for the format and examples.")
+        return 1
+    print(f"SCN-Type: {ev['type']} (from {a.source}); rationale: {ev['rationale']}"
+          + (f"; record {ev['record']}" if ev["record"] else ""))
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())
diff --git a/scripts/staged/README.md b/scripts/staged/README.md
deleted file mode 100644
index d483315a..00000000
--- a/scripts/staged/README.md
+++ /dev/null
@@ -1,50 +0,0 @@
-# scripts/staged/ — generators that are not wired up
-
-Nothing in this directory runs in CI, in `infrastructure/Makefile`, or in any test.
-It is parked here so that it cannot be mistaken for a live generator.
-
-The problem this solves: `scripts/` held 36 Python files and nothing distinguished the
-26 that produce published artifacts from the 10 that do not. A reader — or the author six
-months later — had no way to tell which ones the compliance pipeline actually depends on.
-
-## What is here
-
-| Script | Kind | Status |
-|---|---|---|
-| `build-171-catalog.py` | one-shot data vendoring | Output committed at `data/catalogs/NIST_SP-800-171_rev2_catalog.json`. Needs `openpyxl`, deliberately not a pipeline dependency. |
-| `build-control-mapping.py` | one-shot data vendoring | Output committed at `data/mappings/SP800-53_rev4-to-rev5.mapping.json`. |
-| `build-171-53-mapping.py` | one-shot data vendoring | Output committed at `data/mappings/SP800-171r2-to-SP800-53r4.mapping.json`. |
-| `build-ksi-catalog.py` | one-shot data vendoring | Output committed at `infrastructure/schemas/ksi-catalog.json`, which `build-oscal-ssp.py` reads on **every deploy**. Regenerating it is a reviewed change, not a refresh. |
-| `build-baseline-spokes.py` | Phase 2 spoke | GovRAMP / TX-RAMP profiles + coverage projection. |
-| `build-spoke.py` | Phase 2 spoke | The reusable hub→spoke projection the spokes share. |
-| `build-dispositions.py` | Phase 2 spoke | Dispositions the above-Moderate residue the spokes surface. |
-| `migrate_hub_to_component_def.py` | one-time migration | Would lift `CONTROL_OVERRIDES` out of `build-oscal-ssp.py` into an OSCAL Component Definition. Not taken; the SSP generator is still the hub. |
-| `oscal_resolver.py` | library | Minimal profile resolver, written as the spoke interface. Nothing imports it. |
-| `validate-oscal.py` | validation gate | Validates authored OSCAL against the vendored NIST v1.2.2 schemas. Never added to CI. |
-
-## What wiring one up requires
-
-The three data-vendoring scripts and the migration are finished work — they ran, their
-output is committed, and they exist for reproducibility. They do not need wiring.
-
-The spoke generators do. Wiring one into the pipeline means all four of:
-
-1. A step in the `deploy` job of `.github/workflows/deploy-with-opa.yml`, after the SSP build.
-2. A cosign signing step and a publish step under `/.well-known/`.
-3. **An invariant in `scripts/reconcile.py`** binding the new artifact to the same inventory
-   `signal_id` as everything else — this is the part that matters. An artifact that publishes
-   without a reconciliation invariant is exactly the drift the gate exists to prevent, and
-   invariant (l) already does this for the boundary map as the pattern to copy.
-4. A unit test for that invariant, plus a broken fixture under `tests/fixtures/broken/`.
-
-## Note on `OSCAL_VERSION`
-
-`migrate_hub_to_component_def.py` pins OSCAL `1.2.2`; the live generators emit `1.1.2` from
-`scripts/_common.py`. That divergence predates this directory and is left as-is rather than
-silently harmonised — changing it would change a published artifact.
-
-## Shared helpers
-
-These scripts import from `scripts/_common.py` the same way the live ones do, via a
-`sys.path.insert` of the parent directory. Keeping them on the shared helpers means they stay
-in step with the live generators rather than drifting while parked.
diff --git a/scripts/staged/build-171-53-mapping.py b/scripts/staged/build-171-53-mapping.py
deleted file mode 100644
index 4b447044..00000000
--- a/scripts/staged/build-171-53-mapping.py
+++ /dev/null
@@ -1,83 +0,0 @@
-#!/usr/bin/env python3
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# STAGED — NOT WIRED INTO THE PIPELINE. Kind: one-shot data vendoring.
-#
-# Already run; its output is the committed data/mappings/SP800-171r2-to-SP800-53r4.mapping.json.
-# Re-run only when the extracted source table changes.
-#
-# Nothing under scripts/staged/ runs in CI, in the Makefile, or in any test. It is
-# parked here so it cannot be mistaken for a live generator. See scripts/staged/README.md.
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# =============================================================================
-# 171 Rev2 -> 800-53 Rev4 OSCAL Control Mapping  (Phase 2 / CMMC)
-# =============================================================================
-# Emits the OSCAL Control Mapping from the checked-in source data
-# (data/mappings/SP800-171r2-to-SP800-53r4.source.json), which was extracted
-# from NIST SP 800-171 Rev2 Appendix D Table D-1 via pdfplumber word-geometry +
-# manual verification of spanning cells. The 171 requirement is a tailored
-# SUBSET of the relevant 800-53 control (per the publication), so relationship
-# = subset-of. This is the CMMC projection rail: 171 req -> 53 Rev4 -> (Rev4->Rev5
-# mapping) -> Rev5 hub.
-# =============================================================================
-
-import json
-import os
-import sys
-import uuid
-from pathlib import Path
-
-# Shared generator helpers, one directory up. The insert is __file__-relative, so
-# this script stays runnable standalone from any cwd (see scripts/_common.py).
-sys.path.insert(0, os.path.join(os.path.dirname(os.path.abspath(__file__)), os.pardir))
-from _common import sid  # noqa: E402
-
-REPO = Path(__file__).resolve().parent.parent
-SRC = REPO / "data/mappings/SP800-171r2-to-SP800-53r4.source.json"
-OUT = REPO / "data/mappings/SP800-171r2-to-SP800-53r4.mapping.json"
-NS = uuid.UUID("171b5300-0000-5000-8000-000000000043")
-
-
-def main():
-    src = json.loads(SRC.read_text())
-    mp = src["mapping"]
-    none = src.get("no_800_53_mapping", [])
-    residue = src.get("residue_unconfirmed", [])
-    maps = []
-    for req in sorted(mp):
-        for ctl in sorted(mp[req]):
-            maps.append({"uuid": sid(NS, "map", req, ctl), "relationship": "subset-of",
-                         "sources": [{"type": "control", "id-ref": req}],
-                         "targets": [{"type": "control", "id-ref": ctl}]})
-    doc = {"mapping-collection": {
-        "uuid": sid(NS, "mc", "171r2-53r4"),
-        "metadata": {
-            "title": "NIST SP 800-171 Rev2 -> 800-53 Rev4 control mapping (Appendix D, Table D-1)",
-            "last-modified": "2026-06-10T00:00:00Z", "version": "1.0.0", "oscal-version": "1.2.2",
-            "remarks": (f"From 800-171 Rev2 Appendix D Table D-1 (a 171 requirement is a tailored "
-                        f"subset of the relevant 800-53 control). {len([k for k in mp if mp[k]])} "
-                        f"requirements mapped; {len(none)} explicit no-800-53-mapping ({none}); "
-                        f"RESIDUE pending verification: {residue}."),
-        },
-        "provenance": {"method": "hybrid", "matching-rationale": "functional",
-                       "status": ("complete" if not residue else "not-complete"),
-                       "mapping-description": ("NIST's authoritative 171->53 tailoring mapping (Table D-1); "
-                                               "171 requirements are tailored subsets of the 800-53 controls.")},
-        "mappings": [{"uuid": sid(NS, "m", "171-53"),
-                      "source-resource": {"type": "resource", "href": "#res-171r2"},
-                      "target-resource": {"type": "resource", "href": "#res-53r4"},
-                      "maps": maps}],
-        "back-matter": {"resources": [
-            {"uuid": sid(NS, "r", "171"), "title": "NIST SP 800-171 Rev2 catalog",
-             "props": [{"name": "id", "value": "res-171r2"}],
-             "rlinks": [{"href": "../catalogs/NIST_SP-800-171_rev2_catalog.json"}]},
-            {"uuid": sid(NS, "r", "53"), "title": "NIST SP 800-53 Rev4 catalog",
-             "props": [{"name": "id", "value": "res-53r4"}],
-             "rlinks": [{"href": "../catalogs/NIST_SP-800-53_rev4_catalog.json"}]}]},
-    }}
-    OUT.write_text(json.dumps(doc, indent=2) + "\n")
-    print(f"171->53 mapping: {len([k for k in mp if mp[k]])}/110 mapped, {len(maps)} links, "
-          f"{len(none)} no-mapping, {len(residue)} residue")
-
-
-if __name__ == "__main__":
-    main()
diff --git a/scripts/staged/build-171-catalog.py b/scripts/staged/build-171-catalog.py
deleted file mode 100644
index c098e43e..00000000
--- a/scripts/staged/build-171-catalog.py
+++ /dev/null
@@ -1,114 +0,0 @@
-#!/usr/bin/env python3
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# STAGED — NOT WIRED INTO THE PIPELINE. Kind: one-shot data vendoring.
-#
-# Already run; its output is the committed data/catalogs/NIST_SP-800-171_rev2_catalog.json.
-# Re-run only when NIST republishes the source spreadsheet. Needs openpyxl, which is
-# deliberately not a pipeline dependency.
-#
-# Nothing under scripts/staged/ runs in CI, in the Makefile, or in any test. It is
-# parked here so it cannot be mistaken for a live generator. See scripts/staged/README.md.
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# =============================================================================
-# 800-171 Rev2 OSCAL CATALOG BUILDER  (Phase 2 / CMMC)
-# =============================================================================
-# Builds an OSCAL catalog of NIST SP 800-171 Rev 2 (the 110 security
-# requirements) from NIST's authoritative machine-readable export
-# (sp800-171r2-security-reqs.xlsx). CMMC Level 2 = these 110 requirements,
-# locked to Rev 2 by DoD class deviation. NIST does not publish 800-171 as
-# OSCAL, so this derives the catalog from the authoritative NIST source rather
-# than a community conversion.
-#
-# Output: data/catalogs/NIST_SP-800-171_rev2_catalog.json
-# =============================================================================
-
-import argparse
-import json
-import os
-import re
-import sys
-import uuid
-from pathlib import Path
-
-# Shared generator helpers, one directory up. The insert is __file__-relative, so
-# this script stays runnable standalone from any cwd (see scripts/_common.py).
-sys.path.insert(0, os.path.join(os.path.dirname(os.path.abspath(__file__)), os.pardir))
-from _common import sid  # noqa: E402
-
-import openpyxl
-
-REPO = Path(__file__).resolve().parent.parent
-OUT = REPO / "data" / "catalogs" / "NIST_SP-800-171_rev2_catalog.json"
-NS = uuid.UUID("171a2000-0000-5000-8000-000000000002")
-LAST_MODIFIED = "2026-06-10T00:00:00Z"
-
-
-def build(xlsx_path):
-    wb = openpyxl.load_workbook(xlsx_path, read_only=True, data_only=True)
-    ws = wb["SP 800-171"]
-    rows = list(ws.iter_rows(min_row=2, values_only=True))  # row 1 = header
-
-    groups = {}   # family id "3.1" -> {title, controls:[]}
-    order = []
-    for r in rows:
-        family, bod, ident, sortas, req, disc = (r + (None,) * 6)[:6]
-        if not ident or not re.match(r"^\d+\.\d+\.\d+$", str(ident).strip()):
-            continue
-        ident = str(ident).strip()
-        fam_id = ".".join(ident.split(".")[:2])  # 3.1.1 -> 3.1
-        if fam_id not in groups:
-            groups[fam_id] = {"title": str(family).strip(), "controls": []}
-            order.append(fam_id)
-        control = {
-            "id": ident,
-            "title": ident,
-            "props": [
-                {"name": "label", "value": ident},
-                {"name": "sort-id", "value": str(sortas).strip() if sortas else ident},
-                {"name": "basic-or-derived", "value": str(bod).strip() if bod else ""},
-            ],
-            "parts": [{"id": f"{ident}_smt", "name": "statement",
-                       "prose": str(req).strip() if req else ""}],
-        }
-        if disc:
-            control["parts"].append({"id": f"{ident}_gdn", "name": "guidance",
-                                     "prose": str(disc).strip()})
-        groups[fam_id]["controls"].append(control)
-    wb.close()
-
-    catalog = {
-        "catalog": {
-            "uuid": sid(NS, "catalog", "800-171r2"),
-            "metadata": {
-                "title": "NIST SP 800-171 Revision 2 — Protecting CUI in Nonfederal Systems",
-                "last-modified": LAST_MODIFIED,
-                "version": "Rev 2",
-                "oscal-version": "1.2.2",
-                "remarks": ("Derived from NIST's authoritative machine-readable export "
-                            "(sp800-171r2-security-reqs.xlsx). The 110 security requirements "
-                            "= CMMC Level 2 (locked to Rev 2 by DoD class deviation)."),
-            },
-            "groups": [
-                {"id": fam, "title": groups[fam]["title"], "controls": groups[fam]["controls"]}
-                for fam in order
-            ],
-        }
-    }
-    return catalog, order, groups
-
-
-def main():
-    ap = argparse.ArgumentParser()
-    ap.add_argument("--xlsx", default="/home/saydlette/Downloads/sp800-171r2-security-reqs.xlsx")
-    a = ap.parse_args()
-    catalog, order, groups = build(a.xlsx)
-    OUT.parent.mkdir(parents=True, exist_ok=True)
-    OUT.write_text(json.dumps(catalog, indent=2) + "\n")
-    total = sum(len(groups[f]["controls"]) for f in order)
-    print(f"800-171 Rev2 OSCAL catalog: {len(order)} families, {total} requirements")
-    print(f"  families: {[(f, groups[f]['title'][:24], len(groups[f]['controls'])) for f in order[:4]]} ...")
-    print(f"wrote: {OUT.relative_to(REPO)}")
-
-
-if __name__ == "__main__":
-    main()
diff --git a/scripts/staged/build-baseline-spokes.py b/scripts/staged/build-baseline-spokes.py
deleted file mode 100644
index d5c94124..00000000
--- a/scripts/staged/build-baseline-spokes.py
+++ /dev/null
@@ -1,111 +0,0 @@
-#!/usr/bin/env python3
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# STAGED — NOT WIRED INTO THE PIPELINE. Kind: Phase 2 spoke, not wired.
-#
-# Emits the GovRAMP / TX-RAMP spoke profiles + coverage. Wiring it up means a deploy-job step
-# after the SSP build, a publish step, and a reconciliation-gate invariant binding each spoke
-# to the hub's signal_id — none of which exist yet.
-#
-# Nothing under scripts/staged/ runs in CI, in the Makefile, or in any test. It is
-# parked here so it cannot be mistaken for a live generator. See scripts/staged/README.md.
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# =============================================================================
-# BASELINE SPOKES — GovRAMP Moderate+CJIS, TX-RAMP L1/L2  (Phase 2)
-# =============================================================================
-# These frameworks are 800-53 control SELECTIONS, so each spoke is an OSCAL
-# profile over the hub + a coverage projection — no new catalog, no new mapping:
-#   - GovRAMP Moderate (+CJIS): Rev5-native -> control ids match the hub directly.
-#   - TX-RAMP Level 1 / Level 2: still the 2021 Rev4 baseline (current per TX DIR)
-#     -> ids project through the Rev4->Rev5 mapping (the existing bridge), then
-#     match the hub.
-#
-# Reads the checked-in selections (data/baselines/...selections.json), emits an
-# OSCAL profile per baseline (data/profiles/), and reports coverage + residue.
-# =============================================================================
-
-import json
-import os
-import sys
-import uuid
-from collections import Counter
-from pathlib import Path
-
-# Shared generator helpers, one directory up. The insert is __file__-relative, so
-# this script stays runnable standalone from any cwd (see scripts/_common.py).
-sys.path.insert(0, os.path.join(os.path.dirname(os.path.abspath(__file__)), os.pardir))
-from _common import classify, load_hub, sid  # noqa: E402
-
-REPO = Path(__file__).resolve().parent.parent
-SEL = REPO / "data/baselines/govramp-txramp-cjis.selections.json"
-NS = uuid.UUID("ba5e1100-0000-5000-8000-000000000005")
-CATALOG = {"rev5": "../catalogs/NIST_SP-800-53_rev5_catalog.json",
-           "rev4": "../catalogs/NIST_SP-800-53_rev4_catalog.json"}
-
-
-def load_r4_r5():
-    m = json.loads((REPO / "data/mappings/SP800-53_rev4-to-rev5.mapping.json").read_text())["mapping-collection"]
-    return {x["sources"][0]["id-ref"]: x["targets"][0]["id-ref"] for x in m["mappings"][0]["maps"]}
-
-
-def build_profile(key, title, revision, controls):
-    doc = {"profile": {
-        "uuid": sid(NS, "profile", key),
-        "metadata": {"title": title, "last-modified": "2026-06-10T00:00:00Z",
-                     "version": "1.0.0", "oscal-version": "1.2.2"},
-        "imports": [{"href": CATALOG[revision],
-                     "include-controls": [{"with-ids": controls}]}],
-        "merge": {"as-is": True},
-    }}
-    out = REPO / "data/profiles" / f"{key}_profile.json"
-    out.write_text(json.dumps(doc, indent=2) + "\n")
-    return out
-
-
-def coverage(revision, controls, hub, r4_r5, spoke_na):
-    stack = Counter()
-    residue = []
-    for c in controls:
-        rev5 = c if revision == "rev5" else r4_r5.get(c, c)
-        if rev5 in hub:
-            stack[classify(*hub[rev5])] += 1
-        elif c in spoke_na or rev5 in spoke_na:
-            stack["not-applicable"] += 1            # CJIS-specific / no Rev5 successor, dispositioned N/A
-        else:
-            residue.append(c)
-    return stack, residue
-
-
-def main():
-    import argparse, sys
-    ap = argparse.ArgumentParser()
-    ap.add_argument("--ssp", required=True)
-    a = ap.parse_args()
-
-    data = json.loads(SEL.read_text())
-    hub = load_hub(a.ssp)
-    disp = json.loads((REPO / "data/dispositions/beyond-moderate.json").read_text())
-    for c, d in disp["controls"].items():          # beyond-Moderate dispositions extend the hub
-        hub[c] = (d["status"], d["origination"])
-    spoke_na = set(disp["spoke_not_applicable"])
-    r4_r5 = load_r4_r5()
-    titles = {"govramp_moderate_cjis": "GovRAMP Moderate (Rev5) + CJIS overlay",
-              "txramp_level1": "TX-RAMP Level 1 (Rev4 baseline)",
-              "txramp_level2": "TX-RAMP Level 2 (Rev4 baseline)"}
-
-    for key, bl in data["baselines"].items():
-        controls, rev = bl["controls"], bl["revision"]
-        build_profile(key, titles[key], rev, controls)
-        stack, residue = coverage(rev, controls, hub, r4_r5, spoke_na)
-        covered = sum(stack.values())
-        print(f"\n=== {titles[key]} ===", file=sys.stderr)
-        print(f"  baseline controls: {len(controls)} ({rev})  |  covered by hub: {covered}  "
-              f"|  residue: {len(residue)} ({round(100*covered/len(controls))}% covered)", file=sys.stderr)
-        for k in ["implemented", "partially-inherited", "fully-inherited", "customer-responsibility", "planned", "not-applicable"]:
-            if stack[k]:
-                print(f"    {stack[k]:4}  {k}", file=sys.stderr)
-        if residue:
-            print(f"  residue ({len(residue)}): {residue[:18]}{' ...' if len(residue) > 18 else ''}", file=sys.stderr)
-
-
-if __name__ == "__main__":
-    main()
diff --git a/scripts/staged/build-control-mapping.py b/scripts/staged/build-control-mapping.py
deleted file mode 100644
index 989027e8..00000000
--- a/scripts/staged/build-control-mapping.py
+++ /dev/null
@@ -1,187 +0,0 @@
-#!/usr/bin/env python3
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# STAGED — NOT WIRED INTO THE PIPELINE. Kind: one-shot data vendoring.
-#
-# Already run; its output is the committed data/mappings/SP800-53_rev4-to-rev5.mapping.json.
-# Re-run only when a vendored NIST catalog is replaced.
-#
-# Nothing under scripts/staged/ runs in CI, in the Makefile, or in any test. It is
-# parked here so it cannot be mistaken for a live generator. See scripts/staged/README.md.
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# =============================================================================
-# CONTROL MAPPING  800-53 Rev4 -> Rev5   (Phase 2 / D — the Rev4 bridge)
-# =============================================================================
-# Emits an OSCAL Control Mapping Model (v1.2.x) document mapping every NIST
-# 800-53 Rev4 control to its Rev5 counterpart, derived AUTHORITATIVELY from the
-# two vendored NIST OSCAL catalogs — no hand-keyed crosswalk:
-#
-#   - same id, Rev5 entry active        -> relationship "equivalent"
-#   - same id, Rev5 entry withdrawn:
-#       rel "incorporated-into" target  -> "subset-of"  (Rev4 control ⊆ target)
-#       rel "moved-to"        target  -> "equivalent" (relocated)
-#
-# The withdrawal disposition (target) is taken from the Rev5 catalog control's
-# own links (rel incorporated-into / moved-to) — i.e., from NIST, not us.
-#
-# This is the bridge the CMMC spoke rides: 800-171 Rev2 -> 800-53 Rev4 -> (here)
-# -> Rev5 hub.  Source = Rev4 control, Target = Rev5 control.
-# =============================================================================
-
-import json
-import os
-import sys
-import uuid
-from collections import Counter
-from pathlib import Path
-
-# Shared generator helpers, one directory up. The insert is __file__-relative, so
-# this script stays runnable standalone from any cwd (see scripts/_common.py).
-sys.path.insert(0, os.path.join(os.path.dirname(os.path.abspath(__file__)), os.pardir))
-from _common import sid  # noqa: E402
-
-REPO = Path(__file__).resolve().parent.parent
-R4 = REPO / "data/catalogs/NIST_SP-800-53_rev4_catalog.json"
-R5 = REPO / "data/catalogs/NIST_SP-800-53_rev5_catalog.json"
-OUT = REPO / "data/mappings/SP800-53_rev4-to-rev5.mapping.json"
-NS = uuid.UUID("9c2b6d1a-4e5f-5a7b-8c0d-1e2f3a4b5c6d")
-LAST_MODIFIED = "2026-06-09T00:00:00Z"
-
-
-def index(path):
-    cat = json.loads(path.read_text())["catalog"]
-    out = {}
-    def walk(n):
-        for c in n.get("controls", []) or []:
-            out[c["id"]] = c
-            walk(c)
-        for g in n.get("groups", []) or []:
-            walk(g)
-    walk(cat)
-    return out
-
-
-def withdrawal_target(ctrl):
-    """(target_control_id, rel) from a withdrawn control's links, or None."""
-    for link in ctrl.get("links", []) or []:
-        rel = link.get("rel")
-        if rel in ("incorporated-into", "moved-to"):
-            tgt = link.get("href", "").lstrip("#").split("_")[0]  # statement -> owning control
-            return tgt, rel
-    return None
-
-
-def is_withdrawn(c):
-    return any(p.get("name") == "status" and p.get("value") == "withdrawn"
-               for p in c.get("props", []) or [])
-
-
-def main():
-    r4 = index(R4)
-    r5 = index(R5)
-    maps = []
-    rels = Counter()
-    unresolved = []
-    for cid in sorted(r4):
-        r5c = r5.get(cid)
-        if r5c is None:
-            unresolved.append((cid, "no same-id control in Rev5 catalog"))
-            continue
-        if is_withdrawn(r5c):
-            wt = withdrawal_target(r5c)
-            if not wt:
-                unresolved.append((cid, "withdrawn in Rev5 with no successor (NIST: addressed generally / N-A)"))
-                continue
-            if wt[0] not in r5:
-                unresolved.append((cid, f"withdrawn; incorporated into '{wt[0]}' (family-level, not a single control)"))
-                continue
-            tgt, rel = wt
-            relationship = "subset-of" if rel == "incorporated-into" else "equivalent"
-            remark = f"Rev4 {cid} withdrawn in Rev5; NIST disposition: {rel} {tgt}."
-        else:
-            tgt = cid
-            relationship = "equivalent"
-            remark = None
-        rels[relationship] += 1
-        m = {
-            "uuid": sid(NS, "map", cid),
-            "relationship": relationship,
-            "sources": [{"type": "control", "id-ref": cid}],
-            "targets": [{"type": "control", "id-ref": tgt}],
-        }
-        if remark:
-            m["remarks"] = remark
-        maps.append(m)
-
-    doc = {
-        "mapping-collection": {
-            "uuid": sid(NS, "mapping-collection", "rev4-to-rev5"),
-            "metadata": {
-                "title": "NIST SP 800-53 Rev 4 → Rev 5 control mapping",
-                "last-modified": LAST_MODIFIED,
-                "version": "1.0.0",
-                "oscal-version": "1.2.2",
-                "remarks": (
-                    "Derived deterministically from the vendored NIST OSCAL Rev4 and "
-                    "Rev5 catalogs (data/catalogs/, see data/PROVENANCE.md). Same-id "
-                    "active controls are mapped equivalent; controls withdrawn in Rev5 "
-                    "follow the Rev5 catalog's own incorporated-into / moved-to link. "
-                    "Note: 'equivalent' is catalog-level id equivalence; a subset of "
-                    "same-id controls have substantive text changes between revisions "
-                    "(FedRAMP's Rev4→Rev5 comparison flags these) and could be "
-                    "refined to intersects-with."
-                ),
-            },
-            "provenance": {
-                "method": "automation",
-                "matching-rationale": "syntactic",
-                "status": "complete",
-                "mapping-description": (
-                    "NIST SP 800-53 Rev 4 to Rev 5 control mapping, derived "
-                    "deterministically (automation) from the two vendored NIST OSCAL "
-                    "catalogs: same-id active controls map equivalent; controls "
-                    "withdrawn in Rev5 follow the Rev5 catalog's own incorporated-into "
-                    "/ moved-to link. No hand-keyed crosswalk."
-                ),
-            },
-            "mappings": [{
-                "uuid": sid(NS, "mapping", "rev4-rev5"),
-                "source-resource": {"type": "resource", "href": "#resource-rev4-catalog"},
-                "target-resource": {"type": "resource", "href": "#resource-rev5-catalog"},
-                "maps": maps,
-            }],
-            "back-matter": {
-                "resources": [
-                    {"uuid": sid(NS, "resource", "rev4"), "title": "NIST SP 800-53 Rev 4 catalog (OSCAL)",
-                     "props": [{"name": "id", "value": "resource-rev4-catalog"}],
-                     "rlinks": [{"href": "../catalogs/NIST_SP-800-53_rev4_catalog.json"}]},
-                    {"uuid": sid(NS, "resource", "rev5"), "title": "NIST SP 800-53 Rev 5 catalog (OSCAL)",
-                     "props": [{"name": "id", "value": "resource-rev5-catalog"}],
-                     "rlinks": [{"href": "../catalogs/NIST_SP-800-53_rev5_catalog.json"}]},
-                ]
-            },
-        }
-    }
-    doc["mapping-collection"]["metadata"]["remarks"] += (
-        f" RESIDUE — {len(unresolved)} Rev4 control(s) with no clean single Rev5 "
-        f"successor (recorded, not silently dropped): "
-        + "; ".join(f"{c} ({r})" for c, r in unresolved) + "."
-    )
-    OUT.parent.mkdir(parents=True, exist_ok=True)
-    OUT.write_text(json.dumps(doc, indent=2) + "\n")
-
-    print(f"Rev4 controls mapped: {len(maps)} / {len(r4)}")
-    print(f"  relationships: {dict(rels)}")
-    print(f"  residue (no clean successor, recorded in doc): {len(unresolved)}")
-    for c, r in unresolved:
-        print(f"    {c}: {r}")
-    # spot-checks against what we know
-    by_src = {m['sources'][0]['id-ref']: m for m in maps}
-    for cid in ["ac-1", "ac-2.10", "si-3.1", "ca-3.3"]:
-        m = by_src.get(cid)
-        if m:
-            print(f"  {cid:8} -> {m['targets'][0]['id-ref']:8} [{m['relationship']}]")
-    print(f"wrote: {OUT.relative_to(REPO)}")
-
-
-if __name__ == "__main__":
-    main()
diff --git a/scripts/staged/build-dispositions.py b/scripts/staged/build-dispositions.py
deleted file mode 100644
index 3e30e200..00000000
--- a/scripts/staged/build-dispositions.py
+++ /dev/null
@@ -1,145 +0,0 @@
-#!/usr/bin/env python3
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# STAGED — NOT WIRED INTO THE PIPELINE. Kind: Phase 2 spoke, not wired.
-#
-# Dispositions the above-Moderate residue the spokes surface. Consumed only by the spoke
-# generators above, so it is staged with them.
-#
-# Nothing under scripts/staged/ runs in CI, in the Makefile, or in any test. It is
-# parked here so it cannot be mistaken for a live generator. See scripts/staged/README.md.
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# =============================================================================
-# BEYOND-MODERATE CONTROL DISPOSITIONS  (Phase 2 / residue reduction)
-# =============================================================================
-# Controls that GovRAMP, TX-RAMP, and CMMC require ABOVE the FedRAMP Moderate
-# baseline surfaced as residue when each spoke was first projected. This file
-# dispositions every one of them the disciplined way: does it apply (else N/A
-# with rationale), is it implemented (with the real evidence named), or is it a
-# documented partial/POA&M. The spoke projections read these alongside the
-# Moderate hub, so residue shrinks to only what is honestly still open.
-#
-# Each statement points at evidence that already exists in this system
-# (Sigstore bundles, the Syft SBOM, ACM, CloudWatch, AWS IAM/Shield, the GitHub
-# repo, the ConMon/RA/SA policies). Output: data/dispositions/beyond-moderate.json
-# =============================================================================
-
-import json
-from pathlib import Path
-
-REPO = Path(__file__).resolve().parent.parent
-OUT = REPO / "data" / "dispositions" / "beyond-moderate.json"
-
-# control-id (Rev 5) -> (status, origination, statement)
-DISP = {
-    # --- Not applicable: the system genuinely does not do the thing ---
-    "ac-3.14": ("not-applicable", "sp-system",
-        "No individual data subjects. The system has a single operator and holds no end-user personally identifiable information, so individual-access mechanisms do not apply."),
-    "pe-8.3": ("not-applicable", "inherited",
-        "Physical access is inherited from AWS; the system maintains no visitor access records of its own."),
-    "si-12.1": ("not-applicable", "sp-system",
-        "The system processes no personally identifiable information, so there are no PII elements to limit."),
-    "si-12.2": ("not-applicable", "sp-system",
-        "No PII is used in testing, training, or research; the system processes no PII at all."),
-    "si-12.3": ("not-applicable", "sp-system",
-        "No PII is stored, so there is no PII disposal obligation."),
-    "sc-19": ("not-applicable", "sp-system",
-        "No Voice over IP technologies are used anywhere in the system."),
-    "si-4.14": ("not-applicable", "inherited",
-        "No wireless networks. The system is cloud-hosted on AWS; wireless intrusion detection does not apply and is inherited where relevant."),
-    "sc-7.27": ("not-applicable", "sp-system",
-        "Standalone system with no external system interconnections to classify or manage."),
-    "ia-12.4": ("not-applicable", "sp-system",
-        "No end users to identity-proof. The sole operator's identity is managed through AWS IAM and the GitHub deploy identity."),
-    "mp-6.2": ("not-applicable", "inherited",
-        "No physical media. Media sanitization and its testing are inherited from AWS."),
-    "pe-14.2": ("not-applicable", "inherited",
-        "Physical environment monitoring is inherited from AWS data-center operations."),
-    "ac-10": ("not-applicable", "sp-system",
-        "Application authentication is HTTP Basic, which is sessionless, and there is a single operator account. There is no session state to limit."),
-
-    # --- Implemented / inherited: already true, with the evidence named ---
-    "ac-17.9": ("implemented", "inherited",
-        "Administrative reach is AWS IAM and the GitHub deploy identity, both of which support immediate revocation. No long-lived access keys are used."),
-    "sc-6": ("implemented", "inherited",
-        "Resource availability is provided by AWS: Shield Standard on CloudFront absorbs volumetric denial of service, and Lambda runs under account concurrency limits."),
-    "sc-7.13": ("implemented", "sp-system",
-        "Security functions are isolated from application functions: the OPA gate, scanners, and Sigstore signing run in GitHub Actions CI, and the runtime KSI validator is a separate Lambda from the application Lambda."),
-    "cp-9.3": ("implemented", "sp-system",
-        "The canonical source of truth is the GitHub repository, administratively and geographically separate from the AWS deployment, and S3 versioning retains prior object states."),
-    "sc-7.23": ("implemented", "inherited",
-        "CloudFront returns standardized error responses and does not leak verbose protocol-validation feedback to senders."),
-    "cm-14": ("implemented", "sp-system",
-        "Published artifacts are Sigstore keyless-signed and the deploy verifies signatures, so only signed components are accepted (CM-5(3) / signed components)."),
-    "sa-10.1": ("implemented", "sp-system",
-        "Software and firmware integrity is verifiable: every published artifact carries a Sigstore bundle and a Syft SBOM, checkable with cosign."),
-    "sc-12.2": ("implemented", "inherited",
-        "Symmetric key management is AWS-managed: S3 server-side encryption uses AES-256 with AWS-managed keys; the system manages no symmetric keys of its own."),
-    "sc-12.3": ("implemented", "inherited",
-        "Asymmetric key management for TLS is handled by AWS Certificate Manager, which provisions and rotates the certificate keys."),
-    "au-9.2": ("implemented", "inherited",
-        "Audit records are written to CloudWatch Logs, a service separate from the application compute, providing off-box retention."),
-    "cm-10.1": ("implemented", "sp-corporate",
-        "Open-source components are inventoried by the Syft SBOM on every deploy and governed by the documented supply-chain policy."),
-    "ca-2.2": ("implemented", "sp-corporate",
-        "Specialized assessment is covered by the annual security review plus the per-deploy VDR aggregator, which classifies findings on the FedRAMP 20x PAIN scale."),
-    "ir-7.2": ("implemented", "sp-corporate",
-        "Incident-response coordination with AWS as the underlying provider is documented in the incident response plan."),
-    "sa-4.8": ("implemented", "sp-corporate",
-        "A continuous monitoring plan is maintained and published; it is the acquisition-time ConMon plan this enhancement asks for."),
-    "sa-9.4": ("implemented", "sp-corporate",
-        "Consistency of interests with the external provider (AWS) is addressed through the documented use of the AWS authorization package and operator policy."),
-    "cp-2.2": ("implemented", "inherited",
-        "Capacity is handled by serverless auto-scaling: Lambda and CloudFront scale with demand under AWS-managed capacity."),
-    "sa-11.8": ("implemented", "sp-corporate",
-        "Dynamic code analysis runs in CI as a scheduled monthly OWASP ZAP baseline scan (.github/workflows/zap-dast.yml) against the live site, with findings tracked via the ZAP issue and triaged into the POA&M. The scan covers the unauthenticated static surface today; authenticated coverage of the Cognito-gated taiji application is a tracked follow-up. SAST (Checkov, tfsec) and SCA (Syft/Grype) run on every deploy alongside it."),
-    "ra-5.8": ("implemented", "sp-corporate",
-        "Historic audit records are retained in CloudWatch and the daily Grype re-scan catches newly disclosed CVEs against deployed dependencies; review for prior exploitation is part of the security-review cadence."),
-
-    # --- Partial / planned: honestly still open, pointing at tracked work ---
-    "ra-5.6": ("implemented", "sp-system",
-        "Automated cross-run vulnerability trend analysis is published as a live chart on the trust dashboard, fed by a CVE-keyed trend ledger (/.well-known/vdr-trend.json) that each VDR build appends to via build-vdr-trend.py."),
-}
-
-# CJIS-specific items in the GovRAMP+CJIS matrix that are not standard 800-53
-# controls, and the Rev 4 controls with no Rev 5 successor. Dispositioned N/A at
-# the spoke level (they cannot live in an 800-53 hub).
-SPOKE_NA = {
-    "ia-0": "No Criminal Justice Information is processed; the CJIS overlay does not apply (Originating Agency Identifier).",
-    "ia-5.j": "No Criminal Justice Information is processed; CJIS authenticator additions do not apply.",
-    "ia-5.k": "No Criminal Justice Information is processed; CJIS authenticator additions do not apply.",
-    "ia-5.l": "No Criminal Justice Information is processed; CJIS authenticator additions do not apply.",
-    "ia-5.m": "No Criminal Justice Information is processed; CJIS authenticator additions do not apply.",
-    "ia-5.n": "No Criminal Justice Information is processed; CJIS authenticator additions do not apply.",
-    "ia-5.o": "No Criminal Justice Information is processed; CJIS authenticator additions do not apply.",
-}
-
-# CMMC requirements with no 800-53 mapping in Table D-1, dispositioned explicitly
-# at the requirement level (class, srm, rationale). 3.12.4 (maintain a system
-# security plan) is the customer's OWN obligation: the CSP cannot provide a
-# consuming organization's SSP, so it is osc-responsibility, not inherited. The
-# CSP publishing its own SSP does not discharge the customer's duty.
-CMMC_DISP = {
-    "3.12.4": ("customer-responsibility", "osc-responsibility",
-               "Maintaining a system security plan is the customer's own obligation. 800-171 Rev2 Table D-1 maps 3.12.4 to no 800-53 control, so the CSP does not provide it; the provider publishing its own OSCAL SSP does not discharge a consuming organization's duty to maintain theirs."),
-}
-
-
-def main():
-    OUT.parent.mkdir(parents=True, exist_ok=True)
-    doc = {
-        "_note": "Dispositions for controls required by GovRAMP/TX-RAMP/CMMC above the FedRAMP Moderate baseline. Read by the spoke projections alongside the Moderate hub.",
-        "controls": {c: {"status": s, "origination": o, "statement": t} for c, (s, o, t) in DISP.items()},
-        "spoke_not_applicable": SPOKE_NA,
-        "cmmc_requirement_dispositions": {r: {"class": c, "srm": s, "statement": t} for r, (c, s, t) in CMMC_DISP.items()},
-    }
-    OUT.write_text(json.dumps(doc, indent=2) + "\n")
-    from collections import Counter
-    by = Counter(s for s, _, _ in DISP.values())
-    print(f"wrote {len(DISP)} Rev5 dispositions -> {OUT.relative_to(REPO)}")
-    print(f"  by status: {dict(by)}")
-    print(f"  spoke-level N/A (CJIS + no-successor): {len(SPOKE_NA)}")
-    print(f"  CMMC requirement dispositions: {len(CMMC_DISP)}")
-
-
-if __name__ == "__main__":
-    main()
diff --git a/scripts/staged/build-ksi-catalog.py b/scripts/staged/build-ksi-catalog.py
deleted file mode 100644
index 14d6d716..00000000
--- a/scripts/staged/build-ksi-catalog.py
+++ /dev/null
@@ -1,243 +0,0 @@
-#!/usr/bin/env python3
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# STAGED — NOT WIRED INTO THE PIPELINE. Kind: one-shot data vendoring.
-#
-# Already run; its output is the committed infrastructure/schemas/ksi-catalog.json, which
-# build-oscal-ssp.py reads on every deploy. Re-run when FedRAMP republishes the CR26 corpus
-# — and treat the regenerated catalog as a reviewed change, not a refresh.
-#
-# Nothing under scripts/staged/ runs in CI, in the Makefile, or in any test. It is
-# parked here so it cannot be mistaken for a live generator. See scripts/staged/README.md.
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# =============================================================================
-# KSI CATALOG BUILDER  (CR26 final)
-# =============================================================================
-# Regenerates infrastructure/schemas/ksi-catalog.json from the FedRAMP
-# Consolidated Rules for 2026 (final, launched 2026-06-24). The final corpus
-# renumbered the Key Security Indicators from the old numeric scheme
-# (KSI-CNA-01) to mnemonic IDs (KSI-CNA-RNT), dropped the AFR family, and
-# renamed TPR -> SCR. The corpus ships as markdown only; this script parses the
-# 11 KSI markdown files into the same JSON shape the SSP generator already
-# consumes (info / FRR.KSI carried forward from the prior vendored catalog;
-# the KSI block rebuilt from the markdown).
-#
-# The catalog is VENDORED reference data, not a CI-built artifact: this script
-# is run by the operator when FedRAMP republishes the rules, and the resulting
-# JSON is committed. Control titles are reused from the prior catalog where the
-# control_id matches (the controls did not change, only the KSI IDs).
-#
-#   build-ksi-catalog.py --source /providers/20x/key-security-indicators
-# =============================================================================
-
-import argparse
-import json
-import re
-from pathlib import Path
-
-REPO = Path(__file__).resolve().parent.parent
-DEFAULT_SOURCE = Path("/home/saydlette/workspace/final_consolidated_rules_2026/"
-                      "2026-markdown/providers/20x/key-security-indicators")
-DEFAULT_OLD = REPO / "infrastructure" / "schemas" / "ksi-catalog.json"
-DEFAULT_OUT = REPO / "infrastructure" / "schemas" / "ksi-catalog.json"
-
-# family code -> (display name, source filename)
-FAMILIES = {
-    "CED": ("Cybersecurity Education", "cybersecurity-education.md"),
-    "CMT": ("Change Management", "change-management.md"),
-    "CNA": ("Cloud Native Architecture", "cloud-native-architecture.md"),
-    "IAM": ("Identity and Access Management", "identity-and-access-management.md"),
-    "INR": ("Incident Response", "incident-response.md"),
-    "MLA": ("Monitoring, Logging, and Auditing", "monitoring-logging-and-auditing.md"),
-    "PIY": ("Policy and Inventory", "policy-and-inventory.md"),
-    "RPL": ("Recovery Planning", "recovery-planning.md"),
-    "SCR": ("Supply Chain Risk", "supply-chain-risk.md"),
-    "SVC": ("Service Configuration", "service-configuration.md"),
-}
-
-KSI_RE = re.compile(r'^\?\?\? abstract "(KSI-[A-Z]{3}-[A-Z0-9]{2,3})"')
-HEADING_RE = re.compile(r'^###\s+(.*\S)\s*$')
-CONTROL_REF_RE = re.compile(r'\[([A-Z]{2}-\d{1,2}(?:\s*\(\d{1,2}\))?)\]')
-
-
-def control_id(ref):
-    """'AC-17 (03)' -> 'ac-17.3'; 'CM-02' -> 'cm-2'."""
-    m = re.match(r'([A-Z]{2})-0*(\d+)(?:\s*\(0*(\d+)\))?', ref)
-    fam, num, enh = m.group(1).lower(), m.group(2), m.group(3)
-    cid = f"{fam}-{num}"
-    if enh:
-        cid += f".{enh}"
-    return cid
-
-
-# Control titles not present in the prior catalog's crosswalks (filled in by hand
-# from NIST SP 800-53 Rev 5 so no control carries an empty title).
-SUPPLEMENTAL_TITLES = {
-    "sc-28": "Protection of Information at Rest",
-    "sc-28.1": "Cryptographic Protection",
-}
-
-
-def title_map_from_old(old):
-    """Build {control_id: title} from the prior catalog's control crosswalks."""
-    m = {}
-    for fam in old.get("KSI", {}).values():
-        for ind in fam.get("indicators", []) or []:
-            for c in ind.get("controls", []) or []:
-                cid, title = c.get("control_id"), c.get("title")
-                if cid and title and cid not in m:
-                    m[cid] = title
-    return m
-
-
-def parse_family(path, fam_code):
-    """Parse one KSI markdown file -> list of indicator dicts."""
-    lines = path.read_text().splitlines()
-    indicators = []
-    i = 0
-    heading = None
-    while i < len(lines):
-        hm = HEADING_RE.match(lines[i])
-        if hm:
-            heading = hm.group(1)
-            i += 1
-            continue
-        km = KSI_RE.match(lines[i])
-        if not km:
-            i += 1
-            continue
-        ksi_id = km.group(1)
-        # advance to the quote block
-        j = i + 1
-        while j < len(lines) and '!!! quote ""' not in lines[j]:
-            j += 1
-        # collect the quote block until the next KSI / heading / EOF
-        block = []
-        k = j + 1
-        while k < len(lines):
-            if KSI_RE.match(lines[k]) or HEADING_RE.match(lines[k]):
-                break
-            block.append(lines[k])
-            k += 1
-        statement, controls, class_c_only = _parse_block(block)
-        indicators.append({
-            "id": ksi_id,
-            "name": heading or ksi_id,
-            "statement": statement,
-            "impact": {"low": not class_c_only, "moderate": True},
-            "controls": controls,
-        })
-        i = k
-    return indicators
-
-
-def _parse_block(block):
-    text = "\n".join(block)
-    class_c_only = '=== "Class B"' in text and "Optional" in text
-    # statement
-    statement = ""
-    if '=== "Class C"' in text:
-        seg = text.split('=== "Class C"', 1)[1]
-        # stop at the next marker
-        for stop in ('=== "Class', "**Related", "**Terms", "\n    ---"):
-            if stop in seg:
-                seg = seg.split(stop, 1)[0]
-        statement = _clean(seg)
-    else:
-        # first non-marker paragraph after the quote opener
-        seg = text
-        for stop in ("**Related", "**Terms", "\n    ---"):
-            if stop in seg:
-                seg = seg.split(stop, 1)[0]
-        statement = _clean(seg)
-    # controls
-    controls = []
-    cm = re.search(r'\*\*Related SP 800-53 Controls:\*\*(.*)', text, re.DOTALL)
-    if cm:
-        seg = cm.group(1)
-        for stop in ("**Terms", "\n    ---", "\n###"):
-            if stop in seg:
-                seg = seg.split(stop, 1)[0]
-        seen = set()
-        for ref in CONTROL_REF_RE.findall(seg):
-            cid = control_id(ref)
-            if cid not in seen:
-                seen.add(cid)
-                controls.append(cid)
-    return statement, controls, class_c_only
-
-
-def _clean(s):
-    s = s.replace("**Optional:**", "")
-    s = re.sub(r"\s+", " ", s).strip()
-    return s
-
-
-def main():
-    ap = argparse.ArgumentParser()
-    ap.add_argument("--source", default=str(DEFAULT_SOURCE))
-    ap.add_argument("--old", default=str(DEFAULT_OLD))
-    ap.add_argument("--output", default=str(DEFAULT_OUT))
-    a = ap.parse_args()
-
-    src = Path(a.source)
-    old = json.loads(Path(a.old).read_text())
-    titles = title_map_from_old(old)
-    titles.update(SUPPLEMENTAL_TITLES)
-
-    misses = set()
-    ksi_block = {}
-    total = 0
-    class_c_only_ids = []
-    for fam_code, (fam_name, fname) in FAMILIES.items():
-        inds = parse_family(src / fname, fam_code)
-        for ind in inds:
-            enriched = []
-            for cid in ind["controls"]:
-                t = titles.get(cid)
-                if not t:
-                    misses.add(cid)
-                enriched.append({"control_id": cid, "title": t or ""})
-            ind["controls"] = enriched
-            if not ind["impact"]["low"]:
-                class_c_only_ids.append(ind["id"])
-        ksi_block[fam_code] = {
-            "id": f"KSI-{fam_code}",
-            "name": fam_name,
-            "indicators": inds,
-        }
-        total += len(inds)
-
-    # carry info + FRR.KSI forward, append a CR26-final release note
-    info = old.get("info", {})
-    releases = info.get("releases", []) or []
-    if not any(r.get("id") == "26.06" for r in releases):
-        releases.insert(0, {
-            "id": "26.06",
-            "published_date": "2026-06-24",
-            "description": ("Consolidated Rules for 2026 (official launch). Key Security "
-                            "Indicators renumbered to mnemonic IDs; the AFR (Authorization "
-                            "by FedRAMP) family was retired and TPR (Third-Party) was "
-                            "renamed SCR (Supply Chain Risk). Rebuilt from the published "
-                            "markdown corpus by scripts/build-ksi-catalog.py."),
-        })
-    info["releases"] = releases
-
-    out = {
-        "$schema": old.get("$schema", "FedRAMP.schema.json"),
-        "$id": old.get("$id", "FedRAMP.schema.json"),
-        "info": info,
-        "FRR.KSI": old.get("FRR.KSI", {}),
-        "KSI": ksi_block,
-    }
-    Path(a.output).write_text(json.dumps(out, indent=2) + "\n")
-
-    print(f"wrote {a.output}")
-    print(f"  families: {len(ksi_block)}  indicators: {total}")
-    print(f"  Class-C-only (low=false): {len(class_c_only_ids)} -> {', '.join(class_c_only_ids)}")
-    if misses:
-        print(f"  control titles not found in prior catalog ({len(misses)}): "
-              f"{', '.join(sorted(misses))}")
-
-
-if __name__ == "__main__":
-    main()
diff --git a/scripts/staged/build-spoke.py b/scripts/staged/build-spoke.py
deleted file mode 100644
index 93f1f901..00000000
--- a/scripts/staged/build-spoke.py
+++ /dev/null
@@ -1,135 +0,0 @@
-#!/usr/bin/env python3
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# STAGED — NOT WIRED INTO THE PIPELINE. Kind: Phase 2 spoke, not wired.
-#
-# The reusable hub->spoke projection the framework spokes are meant to share. Same wiring gap
-# as build-baseline-spokes.py.
-#
-# Nothing under scripts/staged/ runs in CI, in the Makefile, or in any test. It is
-# parked here so it cannot be mistaken for a live generator. See scripts/staged/README.md.
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# =============================================================================
-# SPOKE PROJECTION GENERATOR  (Phase 2 / D — the reusable spoke)
-# =============================================================================
-# Projects a hub-derived source SSP (e.g. the 800-53 Rev5 SSP) THROUGH an OSCAL
-# control mapping into a target framework's SSP, then computes the coverage stack
-# and the projection residue. This is the additive thesis in one script: the
-# evidence is never re-collected, only re-projected — one mapping per framework.
-#
-# In-scope target controls = those whose mapped source control is actually in the
-# source SSP (i.e. the target view of what the system implements). Each projected
-# requirement carries the source implementation + a note naming the mapping
-# relationship; `subset-of` maps are flagged (target control covered by a broader
-# source control).
-#
-# Usage: build-spoke.py --mapping M --source-ssp S --framework NAME [--output O]
-# =============================================================================
-
-import argparse
-import importlib.util
-import json
-import uuid
-from collections import Counter
-from pathlib import Path
-
-REPO = Path(__file__).resolve().parent.parent
-NS = uuid.UUID("a1b2c3d4-e5f6-5a7b-8c9d-0e1f2a3b4c5d")
-
-
-def _load(p):
-    return json.loads(Path(p).read_text())
-
-
-def load_mapping(path):
-    doc = _load(path)["mapping-collection"]
-    out = {}
-    for mp in doc["mappings"]:
-        for e in mp["maps"]:
-            out[e["sources"][0]["id-ref"]] = (e["targets"][0]["id-ref"], e["relationship"])
-    return out
-
-
-def _coverage_module():
-    spec = importlib.util.spec_from_file_location("bc", str(REPO / "scripts/build-coverage.py"))
-    m = importlib.util.module_from_spec(spec)
-    spec.loader.exec_module(m)
-    return m
-
-
-def main():
-    ap = argparse.ArgumentParser()
-    ap.add_argument("--mapping", required=True)
-    ap.add_argument("--source-ssp", required=True)
-    ap.add_argument("--framework", required=True)
-    ap.add_argument("--target-profile-href", default="800-53 Rev 4")
-    ap.add_argument("--output", default=None)
-    a = ap.parse_args()
-
-    mapping = load_mapping(a.mapping)
-    src = _load(a.source_ssp)["system-security-plan"]["control-implementation"]["implemented-requirements"]
-    src_irs = {ir["control-id"]: ir for ir in src}
-
-    projected = []
-    rel_counts = Counter()
-    for tgt_cid, (src_cid, rel) in sorted(mapping.items()):
-        s = src_irs.get(src_cid)
-        if s is None:
-            continue  # source control not in system scope -> target control out of scope
-        rel_counts[rel] += 1
-        props = [p for p in s.get("props", []) or []
-                 if p["name"] in ("implementation-status", "control-origination")]
-        note = f"Projected from NIST 800-53 Rev 5 {src_cid} via control-mapping relationship '{rel}'."
-        if rel == "subset-of":
-            note += (" The target (Rev4) control is a subset of the broader Rev5 control; "
-                     "covered by that control's implementation.")
-        projected.append({
-            "uuid": str(uuid.uuid5(NS, "req:" + tgt_cid)),
-            "control-id": tgt_cid,
-            "props": props,
-            "statements": [{
-                "statement-id": f"{tgt_cid}_smt",
-                "uuid": str(uuid.uuid5(NS, "stmt:" + tgt_cid)),
-                "remarks": note,
-            }],
-        })
-
-    ssp = {
-        "system-security-plan": {
-            "uuid": str(uuid.uuid5(NS, "ssp:" + a.framework)),
-            "metadata": {"title": f"{a.framework} — projected from the 800-53 Rev5 hub",
-                         "last-modified": "2026-06-09T00:00:00Z", "version": "1.0.0",
-                         "oscal-version": "1.2.2"},
-            "import-profile": {"href": a.target_profile_href},
-            "control-implementation": {
-                "description": ("Projected from the 800-53 Rev5 SSP through "
-                                "data/mappings (additive: evidence re-projected, not re-collected)."),
-                "implemented-requirements": projected,
-            },
-        }
-    }
-
-    bc = _coverage_module()
-    cov = bc.build_coverage(ssp, a.framework)
-
-    if a.output:
-        Path(a.output).write_text(json.dumps(ssp, indent=2) + "\n")
-
-    import sys
-    print(f"=== spoke projection: {a.framework} ===", file=sys.stderr)
-    print(f"  projected in-scope controls: {len(projected)}", file=sys.stderr)
-    print(f"  via mapping relationship: {dict(rel_counts)}", file=sys.stderr)
-    print(f"  coverage (determined): {cov['coverage']['determined_pct']}%", file=sys.stderr)
-    for c in bc.CLASSES:
-        n = cov["responsibility_stack"][c]
-        if n:
-            print(f"    {n:4}  {c}", file=sys.stderr)
-    inh = cov["inheritable"]
-    print(f"  inheritable: {inh['inheritance_touched']} "
-          f"({inh['fraction_of_baseline']*100:.1f}% of projected baseline)", file=sys.stderr)
-    print(f"  projection-quality residue: {rel_counts['subset-of']} controls covered via a "
-          f"broader Rev5 control (subset-of); plus the 3 mapping-residue controls with no "
-          f"Rev5 successor (recorded in the mapping doc).", file=sys.stderr)
-
-
-if __name__ == "__main__":
-    main()
diff --git a/scripts/staged/migrate_hub_to_component_def.py b/scripts/staged/migrate_hub_to_component_def.py
deleted file mode 100644
index 8fa2c157..00000000
--- a/scripts/staged/migrate_hub_to_component_def.py
+++ /dev/null
@@ -1,172 +0,0 @@
-#!/usr/bin/env python3
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# STAGED — NOT WIRED INTO THE PIPELINE. Kind: one-time migration.
-#
-# Lifts CONTROL_OVERRIDES out of build-oscal-ssp.py into an OSCAL Component Definition. The
-# migration has not been taken; build-oscal-ssp.py is still the hub. Note this file pins
-# OSCAL_VERSION 1.2.2 while the live generators emit 1.1.2 — see scripts/_common.py.
-#
-# Nothing under scripts/staged/ runs in CI, in the Makefile, or in any test. It is
-# parked here so it cannot be mistaken for a live generator. See scripts/staged/README.md.
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# =============================================================================
-# HUB MIGRATION — CONTROL_OVERRIDES  ->  OSCAL Component Definition
-# =============================================================================
-# Phase 2 / A1. Lifts the per-control implementation data that currently lives
-# inside build-oscal-ssp.py (the CONTROL_OVERRIDES dict) into a standalone OSCAL
-# Component Definition — the implementation hub that every framework spoke reads.
-#
-# This is a deterministic, lossless re-expression: CONTROL_OVERRIDES is the
-# source of truth, and the emitted Component Definition round-trips back to it
-# exactly (asserted at the end). Origination decides which component satisfies a
-# control; the origination value is also preserved as a prop so the regenerated
-# SSP reproduces today's control-origination exactly.
-#
-# FAMILY_DEFAULTS is NOT migrated here — per the agreed design it becomes a
-# generator projection rule ("controls in the resolved profile not covered by
-# the hub are N/A-with-family-rationale"), not hub data.
-#
-# Output: data/component-definitions/samaydlette-com-component-definition.json
-# =============================================================================
-
-import importlib.util
-import json
-import os
-import sys
-import uuid
-from pathlib import Path
-
-# Shared generator helpers, one directory up. The insert is __file__-relative, so
-# this script stays runnable standalone from any cwd (see scripts/_common.py).
-sys.path.insert(0, os.path.join(os.path.dirname(os.path.abspath(__file__)), os.pardir))
-from _common import sid  # noqa: E402
-
-REPO = Path(__file__).resolve().parent.parent
-SSP_GEN = REPO / "scripts" / "build-oscal-ssp.py"
-OUT = REPO / "data" / "component-definitions" / "samaydlette-com-component-definition.json"
-CATALOG_SOURCE = "../catalogs/NIST_SP-800-53_rev5_catalog.json"
-
-# Fixed namespace + last-modified so the artifact is deterministic (it changes
-# only when the hub content changes, not on every run).
-NS = uuid.UUID("7b0c2a4e-1f3d-5a6b-8c9d-0e1f2a3b4c5d")
-LAST_MODIFIED = "2026-06-09T00:00:00Z"
-OSCAL_VERSION = "1.2.2"
-
-# origination value -> (component key, component type, component title)
-COMPONENTS = {
-    "sp-system":    ("this-system",    "service", "samaydlette.com — cloud service offering (system-implemented controls)"),
-    "shared":       ("this-system",    "service", "samaydlette.com — cloud service offering (system-implemented controls)"),
-    "sp-corporate": ("operator-policy", "policy", "Operator policies and procedures"),
-    "inherited":    ("aws-leveraged",  "service", "AWS (leveraged authorization)"),
-}
-
-
-def load_hub():
-    spec = importlib.util.spec_from_file_location("bssp", str(SSP_GEN))
-    m = importlib.util.module_from_spec(spec)
-    spec.loader.exec_module(m)
-    return dict(m.CONTROL_OVERRIDES)
-
-
-def build_component_definition(overrides):
-    # Group implemented-requirements by component (per origination).
-    comp_irs = {}  # comp_key -> list of implemented-requirement dicts
-    comp_meta = {}  # comp_key -> (type, title)
-    for cid, o in sorted(overrides.items()):
-        orig = o["origination"]
-        if orig not in COMPONENTS:
-            raise SystemExit(f"unknown origination {orig!r} for control {cid}")
-        ckey, ctype, ctitle = COMPONENTS[orig]
-        comp_meta[ckey] = (ctype, ctitle)
-        comp_irs.setdefault(ckey, []).append({
-            "uuid": sid(NS, "ir", ckey, cid),
-            "control-id": cid,
-            "description": o["statement"],
-            "props": [
-                {"name": "implementation-status", "value": o["status"]},
-                {"name": "control-origination", "value": orig},
-            ],
-        })
-
-    components = []
-    for ckey in sorted(comp_irs):
-        ctype, ctitle = comp_meta[ckey]
-        components.append({
-            "uuid": sid(NS, "component", ckey),
-            "type": ctype,
-            "title": ctitle,
-            "description": ctitle,
-            "control-implementations": [{
-                "uuid": sid(NS, "control-impl", ckey),
-                "source": CATALOG_SOURCE,
-                "description": (
-                    f"Control implementations satisfied by the {ckey} component, "
-                    "expressed once against the NIST 800-53 Rev 5 catalog (the hub). "
-                    "Projected into each framework SSP via the spoke generators."
-                ),
-                "implemented-requirements": comp_irs[ckey],
-            }],
-        })
-
-    return {
-        "component-definition": {
-            "uuid": sid(NS, "component-definition", "samaydlette-com"),
-            "metadata": {
-                "title": "samaydlette.com — control implementation hub (Component Definition)",
-                "last-modified": LAST_MODIFIED,
-                "version": "1.0.0",
-                "oscal-version": OSCAL_VERSION,
-                "remarks": (
-                    "The implementation hub: per-control implementations expressed once "
-                    "against 800-53 Rev 5, migrated losslessly from CONTROL_OVERRIDES. "
-                    "Origination determines which component satisfies each control."
-                ),
-            },
-            "components": components,
-        }
-    }
-
-
-def roundtrip(cd):
-    """Reconstruct {control_id: {status, origination, statement}} from the CD."""
-    out = {}
-    for comp in cd["component-definition"]["components"]:
-        for ci in comp["control-implementations"]:
-            for ir in ci["implemented-requirements"]:
-                props = {p["name"]: p["value"] for p in ir["props"]}
-                out[ir["control-id"]] = {
-                    "status": props["implementation-status"],
-                    "origination": props["control-origination"],
-                    "statement": ir["description"],
-                }
-    return out
-
-
-def main():
-    overrides = load_hub()
-    cd = build_component_definition(overrides)
-
-    # Lossless round-trip assertion: the CD reproduces CONTROL_OVERRIDES exactly.
-    rt = roundtrip(cd)
-    assert rt == overrides, "ROUND-TRIP MISMATCH — migration is lossy"
-
-    OUT.parent.mkdir(parents=True, exist_ok=True)
-    OUT.write_text(json.dumps(cd, indent=2) + "\n")
-
-    # Report
-    from collections import Counter
-    by_orig = Counter(o["origination"] for o in overrides.values())
-    by_comp = Counter()
-    for comp in cd["component-definition"]["components"]:
-        n = sum(len(ci["implemented-requirements"]) for ci in comp["control-implementations"])
-        by_comp[comp["type"] + ":" + comp["title"][:30]] = n
-    print(f"hub controls migrated: {len(overrides)}  (round-trip: EXACT)")
-    print(f"by origination: {dict(by_orig)}")
-    print(f"components ({len(cd['component-definition']['components'])}):")
-    for k, v in by_comp.items():
-        print(f"  {v:4}  {k}")
-    print(f"wrote: {OUT.relative_to(REPO)}")
-
-
-if __name__ == "__main__":
-    main()
diff --git a/scripts/staged/oscal_resolver.py b/scripts/staged/oscal_resolver.py
deleted file mode 100644
index c612bc35..00000000
--- a/scripts/staged/oscal_resolver.py
+++ /dev/null
@@ -1,170 +0,0 @@
-#!/usr/bin/env python3
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# STAGED — NOT WIRED INTO THE PIPELINE. Kind: library, never wired.
-#
-# A minimal profile resolver written as the spoke interface. Nothing imports it yet.
-#
-# Nothing under scripts/staged/ runs in CI, in the Makefile, or in any test. It is
-# parked here so it cannot be mistaken for a live generator. See scripts/staged/README.md.
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# =============================================================================
-# MINIMAL OSCAL PROFILE RESOLVER  (Phase 2 / A2 — the spoke interface)
-# =============================================================================
-# Resolves an OSCAL profile against a catalog into a resolved catalog: selects
-# the imported controls, applies modify.set-parameters and modify.alters. This
-# is intentionally minimal — it handles the constructs FedRAMP-style baselines
-# use (include-controls/with-ids, set-parameters, a handful of alters), not the
-# full OSCAL profile-resolution spec. trestle is the fallback if a profile we
-# author needs deeper modify semantics (decision: minimal in-house first).
-#
-# Correctness is not asserted by hope: resolve() of the FedRAMP Moderate profile
-# is validated against FedRAMP's own published resolved-profile catalog (the
-# oracle). Same control set + same parameters => the resolver is correct, and we
-# can trust it for the profiles we author (GovRAMP, TX-RAMP, …) where no
-# published resolved catalog exists.
-# =============================================================================
-
-import json
-import re
-import sys
-from pathlib import Path
-
-REPO = Path(__file__).resolve().parent.parent
-
-
-def _index_catalog(catalog):
-    """Flatten a catalog to {control-id: control} across nested groups/controls."""
-    out = {}
-
-    def walk(node):
-        for c in node.get("controls", []) or []:
-            out[c["id"]] = c
-            walk(c)  # control enhancements nest under controls[]
-        for g in node.get("groups", []) or []:
-            walk(g)
-
-    walk(catalog)
-    return out
-
-
-def _selected_ids(profile):
-    """Control ids selected by the profile's imports (with-ids, optional
-    with-child-controls)."""
-    ids = []
-    for imp in profile.get("imports", []) or []:
-        if imp.get("include-all") is not None:
-            return None  # signal: include everything (caller handles)
-        for inc in imp.get("include-controls", []) or []:
-            for cid in inc.get("with-ids", []) or []:
-                ids.append(cid)
-    return ids
-
-
-def resolve(profile, catalog):
-    """Return a resolved catalog: selected controls with set-parameters and
-    alters applied. profile/catalog are parsed OSCAL dicts."""
-    profile = profile.get("profile", profile)
-    cat = catalog.get("catalog", catalog)
-    idx = _index_catalog(cat)
-
-    selected = _selected_ids(profile)
-    if selected is None:
-        selected = list(idx.keys())
-    missing = [c for c in selected if c not in idx]
-    if missing:
-        raise SystemExit(f"resolver: {len(missing)} selected controls not in catalog, e.g. {missing[:5]}")
-
-    # Deep-ish copy of just the selected controls (drop nested enhancements not
-    # selected; we re-add selected enhancements as flat entries).
-    import copy
-    resolved = {cid: copy.deepcopy(idx[cid]) for cid in selected}
-    for c in resolved.values():
-        c.pop("controls", None)  # flatten; enhancements are their own entries
-
-    # modify.set-parameters -> attach to the owning control's params[]
-    modify = profile.get("modify", {}) or {}
-    pcount = 0
-    for sp in modify.get("set-parameters", []) or []:
-        pid = sp["param-id"]
-        owner = _param_owner(pid)
-        ctrl = resolved.get(owner)
-        if ctrl is None:
-            continue
-        params = {p["id"]: p for p in ctrl.get("params", []) or []}
-        target = params.get(pid) or {"id": pid}
-        if sp.get("constraints"):
-            target["constraints"] = sp["constraints"]
-        if sp.get("values"):
-            target["values"] = sp["values"]
-        if pid not in params:
-            ctrl.setdefault("params", []).append(target)
-        pcount += 1
-
-    # modify.alters -> add/remove parts (minimal)
-    acount = 0
-    for alt in modify.get("alters", []) or []:
-        ctrl = resolved.get(alt.get("control-id"))
-        if ctrl is None:
-            continue
-        for add in alt.get("adds", []) or []:
-            ctrl.setdefault("parts", []).extend(add.get("parts", []) or [])
-        acount += 1
-
-    return {
-        "catalog": {
-            "uuid": "resolved",
-            "metadata": {"title": f"Resolved: {profile.get('metadata',{}).get('title','profile')}",
-                         "version": "resolved", "oscal-version": "1.2.2",
-                         "last-modified": "1970-01-01T00:00:00Z"},
-            "groups": [{"id": "resolved", "title": "Resolved controls",
-                        "controls": [resolved[c] for c in selected]}],
-        },
-        "_stats": {"controls": len(selected), "set_parameters": pcount, "alters": acount},
-    }
-
-
-def _param_owner(param_id):
-    """Owning control-id for a parameter id, e.g. ac-02_odp.06 -> ac-2,
-    ac-02.02_smt.1 -> ac-2.2 (de-zero-pad, strip suffix)."""
-    head = param_id.split("_")[0]
-    m = re.match(r"([a-z]{2})-0*(\d+)(?:\.0*(\d+))?$", head)
-    if not m:
-        return head
-    f, n, e = m.groups()
-    return f"{f}-{n}" + (f".{e}" if e else "")
-
-
-def _validate_against_oracle():
-    """Resolve FedRAMP Moderate ourselves and diff vs FedRAMP's published
-    resolved catalog."""
-    prof = json.loads((REPO / "data/profiles/FedRAMP_rev5_MODERATE-baseline_profile.json").read_text())
-    cat = json.loads((REPO / "data/catalogs/NIST_SP-800-53_rev5_catalog.json").read_text())
-    oracle = json.loads((REPO / "data/profiles/FedRAMP_rev5_MODERATE-baseline-resolved-profile_catalog.json").read_text())
-
-    res = resolve(prof, cat)
-    ours = {c["id"] for c in res["catalog"]["groups"][0]["controls"]}
-
-    oids = set()
-    def walk(n):
-        for c in n.get("controls", []) or []:
-            oids.add(c["id"]); walk(c)
-        for g in n.get("groups", []) or []:
-            walk(g)
-    walk(oracle["catalog"])
-
-    print(f"resolver stats: {res['_stats']}")
-    print(f"our control set: {len(ours)} | oracle: {len(oids)}")
-    print(f"  CONTROL SET MATCHES ORACLE: {ours == oids}")
-    if ours != oids:
-        print(f"   only-ours: {sorted(ours - oids)[:10]}")
-        print(f"   only-oracle: {sorted(oids - ours)[:10]}")
-    # parameter spot-check: ac-2 should carry the 24h/8h FedRAMP values
-    ac2 = next(c for c in res["catalog"]["groups"][0]["controls"] if c["id"] == "ac-2")
-    vals = [con.get("description") for p in ac2.get("params", []) for con in p.get("constraints", []) or []]
-    print(f"  ac-2 FedRAMP param values resolved: {[v for v in vals if v][:4]}")
-    return ours == oids
-
-
-if __name__ == "__main__":
-    ok = _validate_against_oracle()
-    sys.exit(0 if ok else 1)
diff --git a/scripts/staged/validate-oscal.py b/scripts/staged/validate-oscal.py
deleted file mode 100644
index 592895ff..00000000
--- a/scripts/staged/validate-oscal.py
+++ /dev/null
@@ -1,116 +0,0 @@
-#!/usr/bin/env python3
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# STAGED — NOT WIRED INTO THE PIPELINE. Kind: validation gate, never wired.
-#
-# Validates authored OSCAL against the vendored NIST v1.2.2 schemas. Never added to CI; the
-# artifacts are currently schema-checked only by scripts/validate-ksi-signal.py and the
-# reconciliation gate's cross-artifact invariants.
-#
-# Nothing under scripts/staged/ runs in CI, in the Makefile, or in any test. It is
-# parked here so it cannot be mistaken for a live generator. See scripts/staged/README.md.
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# =============================================================================
-# OSCAL SCHEMA VALIDATION GATE  (Phase 2)
-# =============================================================================
-# Validates the authored OSCAL artifacts against the vendored NIST OSCAL v1.2.2
-# JSON schemas (data/schemas/oscal/, from the usnistgov/OSCAL v1.2.2 release).
-#
-# OSCAL's JSON schemas use ECMA-262 regex (\p{...} Unicode property escapes) that
-# Python's `re` cannot compile. Only those incompatible patterns are dropped;
-# patterns that DO compile (notably the string type's ^\S(.*\S)?$) are kept and
-# enforced, so an embedded newline in a parameter value is caught, not silently
-# passed. Structure, required fields, types, and ENUMS are enforced throughout.
-#
-# Full Metaschema *constraint* validation (beyond JSON Schema) is the CI gold
-# standard via NIST's `oscal-cli` (Java); wire it in CI. This gate is the fast
-# local equivalent and has already caught field-name and enum errors.
-#
-# Usage: validate-oscal.py [--ssp PATH ...]   (extra generated SSPs to validate)
-# Exit non-zero if any artifact fails.
-# =============================================================================
-
-import argparse
-import re
-import json
-import sys
-from pathlib import Path
-
-from jsonschema import validators
-
-REPO = Path(__file__).resolve().parent.parent
-SCHEMAS = REPO / "data" / "schemas" / "oscal"
-
-# Checked-in OSCAL artifacts -> their model schema.
-ARTIFACTS = [
-    ("Component Definition", REPO / "data/component-definitions/samaydlette-com-component-definition.json", "oscal_component_schema.json"),
-    ("Rev4->Rev5 Mapping",   REPO / "data/mappings/SP800-53_rev4-to-rev5.mapping.json",                     "oscal_mapping_schema.json"),
-    ("800-171r2 Catalog",    REPO / "data/catalogs/NIST_SP-800-171_rev2_catalog.json",                      "oscal_catalog_schema.json"),
-    ("171r2->53r4 Mapping",  REPO / "data/mappings/SP800-171r2-to-SP800-53r4.mapping.json",                 "oscal_mapping_schema.json"),
-    ("GovRAMP Mod+CJIS Prof",REPO / "data/profiles/govramp_moderate_cjis_profile.json",                     "oscal_profile_schema.json"),
-    ("TX-RAMP L1 Profile",   REPO / "data/profiles/txramp_level1_profile.json",                             "oscal_profile_schema.json"),
-    ("TX-RAMP L2 Profile",   REPO / "data/profiles/txramp_level2_profile.json",                             "oscal_profile_schema.json"),
-]
-
-
-def strip_patterns(o):
-    # Strip ONLY the regex patterns Python's re cannot compile (OSCAL uses
-    # ECMA-262 \p{...} Unicode property escapes). Patterns that DO compile —
-    # notably the string type's ^\S(.*\S)?$ — are kept, so genuine violations
-    # (e.g. an embedded newline in a parameter value) are actually caught rather
-    # than silently passed.
-    if isinstance(o, dict):
-        out = {}
-        for k, v in o.items():
-            if k == "pattern" and isinstance(v, str):
-                try:
-                    re.compile(v)
-                    out[k] = v
-                except re.error:
-                    continue  # drop the incompatible pattern only
-            else:
-                out[k] = strip_patterns(v)
-        return out
-    if isinstance(o, list):
-        return [strip_patterns(x) for x in o]
-    return o
-
-
-def validate(label, artifact_path, schema_name):
-    schema = strip_patterns(json.loads((SCHEMAS / schema_name).read_text()))
-    inst = json.loads(Path(artifact_path).read_text())
-    errs = sorted(validators.validator_for(schema)(schema).iter_errors(inst),
-                  key=lambda e: list(e.path))
-    if not errs:
-        print(f"  {label:24} VALID")
-        return True
-    print(f"  {label:24} {len(errs)} ERROR(S)")
-    seen = set()
-    for e in errs:
-        k = (tuple(str(p) for p in list(e.path)[-3:]), e.message[:50])
-        if k in seen:
-            continue
-        seen.add(k)
-        print("       at", ".".join(str(p) for p in list(e.path)[-4:]), "->", e.message[:140])
-        if len(seen) >= 8:
-            break
-    return False
-
-
-def main():
-    ap = argparse.ArgumentParser()
-    ap.add_argument("--ssp", action="append", default=[], help="generated SSP(s) to validate")
-    a = ap.parse_args()
-
-    print("=== OSCAL schema validation (NIST v1.2.2, patterns stripped) ===")
-    ok = True
-    for label, path, schema in ARTIFACTS:
-        ok &= validate(label, path, schema)
-    for sp in a.ssp:
-        ok &= validate(f"SSP {Path(sp).name}", sp, "oscal_ssp_schema.json")
-
-    print(f"\n{'ALL VALID' if ok else 'VALIDATION FAILED'}")
-    sys.exit(0 if ok else 1)
-
-
-if __name__ == "__main__":
-    main()
diff --git a/scripts/submit-package.py b/scripts/submit-package.py
new file mode 100644
index 00000000..bf9d0db9
--- /dev/null
+++ b/scripts/submit-package.py
@@ -0,0 +1,299 @@
+#!/usr/bin/env python3
+"""Simulated submission of the FedRAMP Certification Package (FRC-CSO-PKG).
+
+FRC-CSO-PKG: the package supplied to FedRAMP holds at least the Certification
+Package Overview (CPO-CSO-OVR), the Security Decision Record with every
+applicable rule (SDR-CSO-FRR), and an Ongoing Certification Report
+(CCM-OCR-AVL). On every deploy this:
+
+1. checks the three reports this build is about to publish: each validates
+   against FedRAMP's schema, the SDR lists every applicable rule once, and all
+   carry the same FedRAMP ID;
+2. builds a submission manifest (each report's sha256 and version, and a
+   package digest over their content hashes);
+3. hands it to the simulated FedRAMP intake below, a function in this file,
+   and checks the receipt echoes the digest;
+4. appends an entry to the published log (package-submission-log.json) when
+   the package changed since the last entry, or a certification report is
+   due; earlier entries must be carried over unchanged;
+5. CDS-CSO-FRC: when a certification report is due, the simulated FedRAMP
+   issues a stand-in report in response to that submission, and the entry logs
+   it verbatim with the date received. A report is due for the first
+   submission, after any adaptive or transformative Significant Change
+   Notification no earlier report covered, and once a year; an ordinary deploy
+   never re-issues one. scripts/publish-certification-reports.py publishes
+   each logged report unmodified and fails the deploy past two weeks from
+   receipt. Every report says, in its title and first line, that it is a
+   simulated report NOT ISSUED BY FEDRAMP and that the system is not certified;
+6. AFC-CSO-NOC: files a change notice with the simulated FedRAMP for every
+   change of the FedRAMP Security Inbox contact not yet filed
+   (scripts/check-fsi-notice.py), and fails unless each notice is filed
+   within one business day of the deploy that first published the change
+   (recorded in the log's inboxContact).
+
+NOTHING IS SENT. There is no network call: FedRAMP is simulated, and the
+"submission", the report and every notice are entries in this log. Any
+unexpected outcome fails the deploy.
+
+  submit-package.py --cpo certification-package-overview.json \
+      --sdr security-decision-record.json --ocr ongoing-certification-report.json \
+      --previous prev-log.json --output package-submission-log.json --commit SHA
+"""
+
+import argparse
+import hashlib
+import importlib.util
+import json
+import sys
+from datetime import date, datetime, timedelta, timezone
+from pathlib import Path
+
+sys.path.insert(0, str(Path(__file__).resolve().parent))
+import _engagement  # noqa: E402
+import _fedramp_schema as fs  # noqa: E402
+import _offering  # noqa: E402
+import _rules  # noqa: E402
+import _scn  # noqa: E402
+
+_spec = importlib.util.spec_from_file_location("check_fsi_notice", Path(__file__).resolve().parent / "check-fsi-notice.py")
+assert _spec is not None and _spec.loader is not None
+fsi_notice = importlib.util.module_from_spec(_spec)
+_spec.loader.exec_module(fsi_notice)
+
+BASE = "https://samaydlette.com/.well-known/"
+SIMULATION = ("FedRAMP is simulated. The package goes to simulated_fedramp_intake() in scripts/submit-package.py, "
+              "a function that never touches the network, and the only trace is this signed log. Nothing has been "
+              "submitted to the real FedRAMP, and nothing will be.")
+
+
+def _fail(msg):
+    raise SystemExit(f"::error::package submission: {msg} (fail-closed)")
+
+
+def simulated_fedramp_intake(manifest):
+    """The simulated counterparty. Accepts any well-formed manifest and returns
+    a receipt; it is obviously not FedRAMP."""
+    return {"receiptId": "SIM-" + manifest["packageSha256"][:12].upper(),
+            "receivedBy": "Simulated FedRAMP intake: a Python function in this repository. Nothing left the building.",
+            "packageSha256": manifest["packageSha256"],
+            "message": "Thank you for your submission. It has been placed in a queue that does not exist."}
+
+
+def simulated_fedramp_notice_intake(notice):
+    """The simulated counterparty for a FedRAMP Security Inbox change notice
+    (AFC-CSO-NOC). Nothing is sent; this receipt is the whole exchange."""
+    digest = hashlib.sha256(json.dumps(notice, sort_keys=True).encode()).hexdigest()
+    return {"receiptId": "SIM-NOC-" + digest[:12].upper(),
+            "receivedBy": "FedRAMP (simulated): a Python function in this repository. Nothing left the building.",
+            "message": "Noted. Our records, which do not exist, have been updated."}
+
+
+# --- CDS-CSO-FRC: the simulated FedRAMP's certification report --------------------------
+
+NOT_CERTIFIED = _offering.CERTIFICATION_STATUS
+REPORT_TITLE = ("SIMULATED REPORT, NOT ISSUED BY FEDRAMP: samaydlette.com is NOT FedRAMP certified "
+                "(proof of concept)")
+REPORT_NOTICE = ("This is not a FedRAMP Certification Report. FedRAMP did not write it, has never seen it, and has "
+                 "certified nothing. A Python function in scripts/submit-package.py wrote it in response to a "
+                 "simulated package submission, so the path that publishes FedRAMP Certification Reports unmodified "
+                 "within two weeks (CDS-CSO-FRC) runs end to end. This system is not certified.")
+ANNUAL_DAYS = 365
+
+
+def reported_scns(entries):
+    """Every SCN id an earlier certification report already covered."""
+    return {s for e in entries for s in ((e.get("certificationReport") or {}).get("scnsCovered") or [])}
+
+
+def report_due(entries, scn_rows, today):
+    """Why the simulated FedRAMP owes a certification report for a submission
+    made today, or None: the first one, after an adaptive or transformative SCN
+    no earlier report covered, and annually."""
+    reports = [e["certificationReport"] for e in entries if e.get("certificationReport")]
+    if not reports:
+        return "initial certification report (first package submission)"
+    new = sorted(r["scn_id"] for r in scn_rows if r.get("scn_type") in _scn.RECORD_TYPES
+                 and r.get("scn_id") not in reported_scns(entries))
+    if new:
+        return "after " + ", ".join(new) + " (adaptive or transformative Significant Change Notification)"
+    last = max(date.fromisoformat(r["receivedOn"]) for r in reports)
+    if today >= last + timedelta(days=ANNUAL_DAYS):
+        return f"annual certification report (the last was received {last.isoformat()})"
+    return None
+
+
+def report_bytes(report):
+    """The report exactly as received and published (CDS-CSO-FRC: unmodified)."""
+    return (json.dumps(report, indent=2, ensure_ascii=False) + "\n").encode("utf-8")
+
+
+def simulated_fedramp_certification_report(entry, trigger, fedramp_id, today, scn_rows):
+    """The simulated counterparty issues a stand-in report in response to a
+    submission. It is obviously fake, and says so first."""
+    receipt = entry["receipt"]["receiptId"]
+    report = {
+        "title": REPORT_TITLE,
+        "notice": REPORT_NOTICE,
+        "simulated": True,
+        "notIssuedByFedRAMP": True,
+        "certificationStatus": NOT_CERTIFIED,
+        "issuer": "FedRAMP (simulated): a Python function in this repository, with no authority whatsoever.",
+        "cloudServiceOffering": "samaydlette.com",
+        "fedRampId": fedramp_id,
+        "received": today.isoformat(),
+        "inResponseTo": {"receiptId": receipt, "submittedAt": entry["submittedAt"],
+                         "packageSha256": entry["manifest"]["packageSha256"]},
+        "trigger": trigger,
+        "determination": "None. No certification decision has been made, and none will be: nothing was ever "
+                         "submitted to FedRAMP.",
+        "findings": [],
+        "noteToAgencies": "If you came here hoping for a FedRAMP certification, sorry: this one is pretend. Hit me "
+                          "up on LinkedIn: https://www.linkedin.com/in/sa2/",
+    }
+    _engagement.require_none(report, "the simulated certification report")
+    return {"file": f"{today.isoformat()}-{receipt.lower()}-simulated-certification-report.json",
+            "receivedOn": today.isoformat(), "from": "FedRAMP (simulated)", "trigger": trigger,
+            "scnsCovered": sorted(r["scn_id"] for r in scn_rows if r.get("scn_type") in _scn.RECORD_TYPES),
+            "sha256": hashlib.sha256(report_bytes(report)).hexdigest(), "report": report}
+
+
+PROGRAM = "20x"  # FRC-CSO-POP: one program sought (DEC-107)
+
+
+# CPO-CSO-OVR content the schema leaves optional but the rules require here:
+# the trust center and secure configuration guidance (CDS-CSO-PUB), the
+# third-party resources (MAS-CSO-TPR) and the assessor's overall summary
+# (CPO-CSO-OSA).
+CPO_REQUIRED = (("serviceProperties", "trustCenter"), ("serviceProperties", "secureConfigurationGuidance"),
+                ("thirdPartyInformationResources",),
+                ("providerExtensions", "independentAssessment", "overallSummary"))
+
+
+def cpo_gaps(cpo):
+    out = []
+    for path in CPO_REQUIRED:
+        node = cpo
+        for k in path:
+            node = node.get(k) if isinstance(node, dict) else None
+        if not node:
+            out.append(".".join(path))
+    return out
+
+
+def check_components(docs, applicable, fedramp_id):
+    for kind, doc in docs.items():
+        errs = fs.validate(doc, kind)
+        if errs:
+            _fail(f"the {kind.upper()} does not validate against FedRAMP's schema: {errs[0]}")
+    missing = cpo_gaps(docs["cpo"])
+    if missing:
+        _fail(f"the CPO is incomplete (CPO-CSO-OVR): no {', '.join(missing)}")
+    if docs["cpo"]["serviceIdentification"]["certificationType"] != PROGRAM:
+        _fail(f"the CPO's certificationType is not {PROGRAM}: this offering seeks one program only (FRC-CSO-POP)")
+    ids = [r["frrID"] for r in docs["sdr"]["fedRampRequirements"]]
+    if sorted(ids) != sorted(applicable) or len(ids) != len(set(ids)):
+        _fail("the SDR does not list every applicable FedRAMP rule exactly once (SDR-CSO-FRR)")
+    got = {"cpo": docs["cpo"]["serviceIdentification"]["fedRampPackageId"],
+           "sdr": (docs["sdr"].get("providerExtensions") or {}).get("fedRampId"),
+           "ocr": (docs["ocr"].get("providerExtensions") or {}).get("fedRampId")}
+    wrong = sorted(k for k, v in got.items() if v != fedramp_id)
+    if wrong:
+        _fail(f"{', '.join(wrong)} carry a FedRAMP ID other than the offering's (CDS-CSO-FID)")
+    for kind in ("cpo", "sdr"):
+        cert = (docs[kind].get("providerExtensions") or {}).get("certification")
+        if not isinstance(cert, dict) or cert.get("status") != NOT_CERTIFIED:
+            _fail(f"the {kind.upper()} does not state providerExtensions.certification.status {NOT_CERTIFIED!r}: "
+                  "this proof of concept never presents itself as certified")
+
+
+def manifest_for(docs, paths, commit):
+    """Each report's bytes (sha256) and content (its contentSha256, which leaves
+    out the timestamp): the log gains an entry when the content changes."""
+    comps = []
+    for kind, rule, name in (("cpo", "CPO-CSO-OVR", "certification-package-overview.json"),
+                             ("sdr", "SDR-CSO-FRR", "security-decision-record.json"),
+                             ("ocr", "CCM-OCR-AVL", "ongoing-certification-report.json")):
+        raw = Path(paths[kind]).read_bytes()
+        content = (docs[kind].get("providerExtensions") or {}).get("contentSha256")
+        if not content:
+            _fail(f"the {kind.upper()} carries no contentSha256")
+        comps.append({"component": kind.upper(), "rule": rule, "url": BASE + name,
+                      "sha256": hashlib.sha256(raw).hexdigest(), "contentSha256": content,
+                      "version": (docs[kind].get("metadata") or {}).get("version")})
+    digest = hashlib.sha256("".join(c["contentSha256"] for c in comps).encode()).hexdigest()
+    return {"components": comps, "packageSha256": digest, "commit": commit}
+
+
+def build(docs, paths, previous, now, commit, applicable, fedramp_id, scn_rows=(), offering=None):
+    check_components(docs, applicable, fedramp_id)
+    entries = list((previous or {}).get("entries") or [])
+    for e in entries:
+        if not isinstance(e, dict) or not {"submittedAt", "manifest", "receipt"} <= set(e):
+            _fail("the previous log has a malformed entry; earlier entries are carried over unchanged")
+    manifest = manifest_for(docs, paths, commit)
+    receipt = simulated_fedramp_intake(manifest)
+    if receipt.get("packageSha256") != manifest["packageSha256"]:
+        _fail("the simulated intake's receipt does not echo the package digest")
+    due = report_due(entries, scn_rows, now.date())
+    if due or not entries or entries[-1]["manifest"]["packageSha256"] != manifest["packageSha256"]:
+        entry = {"submittedAt": now.isoformat(), "manifest": manifest, "receipt": receipt}
+        if due:
+            entry["certificationReport"] = simulated_fedramp_certification_report(
+                entry, due, fedramp_id, now.date(), scn_rows)
+        entries.append(entry)
+    log = {"schema": "package-submission-log/1", "generated_at": now.isoformat(), "fedRampId": fedramp_id,
+           "certificationPackageOverviewUri": fs.CPO_URI, "nothingSent": True,
+           "simulated": {"counterparty": "fedramp", "how": SIMULATION},
+           "engagement": _engagement.STATEMENT, "entries": entries}
+    if offering is not None:
+        prev_contact = (previous or {}).get("inboxContact")
+        notices, problems = fsi_notice.file_notices(offering, (previous or {}).get("changeNotices"), now.date(),
+                                                    simulated_fedramp_notice_intake, commit, prev_contact)
+        current, more = fsi_notice.published_contact(offering, prev_contact, now.date(), commit)
+        problems += [p for p in more if p not in problems]
+        if problems:
+            _fail("FedRAMP Security Inbox change notice (AFC-CSO-NOC): " + "; ".join(problems))
+        log["inboxContact"] = current
+        log["changeNotices"] = notices
+    return log
+
+
+def main(argv=None):
+    ap = argparse.ArgumentParser(description=__doc__, formatter_class=argparse.RawDescriptionHelpFormatter)
+    ap.add_argument("--cpo", default="certification-package-overview.json")
+    ap.add_argument("--sdr", default="security-decision-record.json")
+    ap.add_argument("--ocr", default="ongoing-certification-report.json")
+    ap.add_argument("--previous", default=None)
+    ap.add_argument("--output", default="package-submission-log.json")
+    ap.add_argument("--commit", default="")
+    ap.add_argument("--scn-register", default=str(_scn.REGISTER))
+    ap.add_argument("--offering", default=str(_offering.OFFERING_PATH))
+    a = ap.parse_args(argv)
+    paths = {"cpo": a.cpo, "sdr": a.sdr, "ocr": a.ocr}
+    docs = {}
+    for k, p in paths.items():
+        try:
+            docs[k] = json.loads(Path(p).read_text())
+        except (OSError, ValueError) as exc:
+            _fail(f"cannot read the {k.upper()} ({p}): {exc}")
+    prev = {}
+    if a.previous and Path(a.previous).exists():
+        try:
+            prev = json.loads(Path(a.previous).read_text())
+        except ValueError:
+            _fail("the previously published log is not JSON; refusing to start a new log over it")
+        if prev and prev.get("schema") != "package-submission-log/1":
+            _fail("the previously published log is not a package-submission-log/1 document")
+    _, scn_rows = _scn.read_register(a.scn_register)
+    offering = json.loads(Path(a.offering).read_text())
+    log = build(docs, paths, prev, datetime.now(timezone.utc), a.commit, _rules.applicable_provider_rules(),
+                _offering.fedramp_id(), scn_rows, offering)
+    Path(a.output).write_text(json.dumps(log, indent=2) + "\n")
+    last = log["entries"][-1]
+    print(f"package-submission-log: {len(log['entries'])} entr(ies); latest {last['receipt']['receiptId']} "
+          "(simulated FedRAMP; nothing sent)")
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())
diff --git a/scripts/sync-ksi-catalog.py b/scripts/sync-ksi-catalog.py
new file mode 100644
index 00000000..199c3a8d
--- /dev/null
+++ b/scripts/sync-ksi-catalog.py
@@ -0,0 +1,95 @@
+#!/usr/bin/env python3
+"""Keep infrastructure/schemas/ksi-catalog.json equal to the pinned FedRAMP rules.
+
+The catalog's KSI block (IDs, names, statements and KSI->control mappings) is
+FedRAMP's, so it is derived from the vendored, hash-checked Consolidated Rules
+(scripts/_rules.py), never edited by hand. FedRAMP revises mappings between
+releases (for example on 2026-10-13); re-pinning the rules and re-running this
+script carries the change, and tests/test_ksi_catalog_corpus.py fails while
+the two disagree.
+
+Control titles come from the vendored NIST SP 800-53 Rev5 catalog. The per-KSI impact flags are the catalog's
+own (the corpus does not carry them) and are kept.
+
+    sync-ksi-catalog.py            rewrite the catalog
+    sync-ksi-catalog.py --check    exit 1 if it differs from the corpus
+"""
+
+import argparse
+import json
+import sys
+from pathlib import Path
+
+sys.path.insert(0, str(Path(__file__).resolve().parent))
+import _rules  # noqa: E402
+
+REPO = Path(__file__).resolve().parent.parent
+CATALOG = REPO / "infrastructure" / "schemas" / "ksi-catalog.json"
+NIST = REPO / "data" / "catalogs" / "NIST_SP-800-53_rev5_catalog.json"
+
+
+def _fail(msg):
+    raise SystemExit(f"::error::KSI catalog: {msg} (fail-closed)")
+
+
+def _titles():
+    out = {}
+
+    def walk(group):
+        for c in group.get("controls", []) or []:
+            out[c["id"]] = c["title"]
+            walk(c)
+        for g in group.get("groups", []) or []:
+            walk(g)
+    walk(json.loads(NIST.read_text())["catalog"])
+    return out
+
+
+def derive(catalog, rules_dir=_rules.RULES_DIR):
+    """The catalog with its KSI block rebuilt from the pinned corpus."""
+    rules, _ = _rules.load_rules(rules_dir)
+    titles = _titles()
+    old_impact = {i["id"]: i.get("impact") for f in catalog.get("KSI", {}).values()
+                  for i in f.get("indicators", [])}
+    ksi = {}
+    for fam_id, fam in rules["KSI"].items():
+        indicators = []
+        for kid, k in fam["indicators"].items():
+            controls = []
+            for c in k.get("controls", []) or []:
+                cid = str(c).lower()
+                if cid not in titles:
+                    _fail(f"{kid} maps {cid}, which is not in the NIST SP 800-53 Rev5 catalog")
+                controls.append({"control_id": cid, "title": titles[cid]})
+            if kid not in old_impact:
+                _fail(f"{kid} is new in the corpus; set its impact flags in the catalog first")
+            # Class C's statement where the KSI varies by class (five do).
+            statement = ((k.get("varies_by_class") or {}).get(_rules.CERT_CLASS) or k).get("statement")
+            if not isinstance(statement, str):
+                _fail(f"{kid} has no Class {_rules.CERT_CLASS.upper()} statement")
+            indicators.append({"id": kid, "name": k["name"], "statement": statement,
+                               "impact": old_impact[kid], "controls": controls})
+        ksi[fam_id] = {"id": fam["id"], "name": fam["name"], "indicators": indicators}
+    out = dict(catalog)
+    out["KSI"] = ksi
+    return out
+
+
+def main(argv=None):
+    ap = argparse.ArgumentParser()
+    ap.add_argument("--check", action="store_true")
+    a = ap.parse_args(argv)
+    current = json.loads(CATALOG.read_text())
+    want = derive(current)
+    if a.check:
+        if want != current:
+            print("::error::infrastructure/schemas/ksi-catalog.json differs from the pinned FedRAMP rules; "
+                  "run scripts/sync-ksi-catalog.py and review the diff")
+            return 1
+        return 0
+    CATALOG.write_text(json.dumps(want, indent=2, ensure_ascii=False) + "\n")
+    return 0
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())
diff --git a/scripts/verify-published.sh b/scripts/verify-published.sh
index f6b59456..cc81ea5b 100755
--- a/scripts/verify-published.sh
+++ b/scripts/verify-published.sh
@@ -32,7 +32,8 @@ set -euo pipefail
 
 BASE="${1:-https://samaydlette.com/.well-known}"
 IDENTITY='https://github.com/sam-aydlette/samaydlette.com/.github/workflows/deploy-with-opa.yml@refs/heads/main'
-# The VDR — and only the VDR — has a second legitimate publisher. The deploy
+# The VDR has a second legitimate publisher (and so do the certification
+# package and the incident reports, below). The deploy
 # workflow cannot run unattended (it applies Terraform and is bound to a
 # reviewed environment), so the nightly refresh that keeps the vulnerability
 # report inside its 24-hour freshness policy runs as its own workflow and signs
@@ -42,10 +43,38 @@ IDENTITY='https://github.com/sam-aydlette/samaydlette.com/.github/workflows/depl
 #
 # Both identities are workflows in THIS repository, on `main`, so the trust
 # claim is unchanged: the evidence was produced by this repo's pinned CI, not by
-# a person with a key. Everything else — the canonical inventory, the SDR —
-# still verifies against the deploy identity alone.
+# a person with a key. Everything not named in signers_for below — the
+# canonical inventory first among them — verifies against the deploy identity
+# alone.
 NIGHTLY_IDENTITY='https://github.com/sam-aydlette/samaydlette.com/.github/workflows/evidence-nightly.yml@refs/heads/main'
+# The certification package (SDR, CPO, OCR) has a second publisher for the same
+# reason: package-maintenance.yml rebuilds it daily at the deployed commit, so
+# it stays inside CPO-CSX-CPM's two-week window without a reviewed deploy.
+MAINT_IDENTITY='https://github.com/sam-aydlette/samaydlette.com/.github/workflows/package-maintenance.yml@refs/heads/main'
+# The incident log, delivery log and reports have a second publisher too:
+# incident-reports.yml republishes them twice a day and whenever the incident
+# register changes, so the reporting clocks run without a reviewed deploy.
+INCIDENT_IDENTITY='https://github.com/sam-aydlette/samaydlette.com/.github/workflows/incident-reports.yml@refs/heads/main'
+# The simulated assessor signs its own assessment; the deploy relays it.
+ASSESSOR_IDENTITY='https://github.com/sam-aydlette/samaydlette.com/.github/workflows/simulated-assessor.yml@refs/heads/main'
 ISSUER='https://token.actions.githubusercontent.com'
+
+# signers-begin: the identities allowed to sign each published file, i.e. the
+# workflows that write it (scripts/_signers.py; tests/test_publishers.py runs this
+# function and holds it equal to the workflows' publish steps).
+signers_for() {
+  case "$1" in
+    simulated-assessment*) echo "$ASSESSOR_IDENTITY" ;;
+    vdr-audit-log-review*|vdr-recovery-exercise*) echo "$NIGHTLY_IDENTITY" ;;
+    vdr-*) echo "$IDENTITY $NIGHTLY_IDENTITY" ;;
+    security-decision-record*|certification-package-overview*|ongoing-certification-report*)
+      echo "$IDENTITY $MAINT_IDENTITY" ;;
+    ocr-issue*|snapshot-*|quarterly-reviews*|quarterly-review-*|security-review*) echo "$MAINT_IDENTITY" ;;
+    incident-*) echo "$IDENTITY $INCIDENT_IDENTITY" ;;
+    *) echo "$IDENTITY" ;;
+  esac
+}
+# signers-end
 SCRIPTS="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 
 # Verify a blob signature against any of the accepted publisher identities.
@@ -92,13 +121,18 @@ for f in ksi-signal.json ksi-signal.bundle \
          security-decision-record.json security-decision-record.bundle \
          security-decision-record.json.intoto.jsonl \
          certification-package-overview.json certification-package-overview.bundle \
+         ongoing-certification-report.json ongoing-certification-report.bundle \
          vdr-report.json vdr-report.json.intoto.jsonl \
          vdr-detail-report.json vdr-detail-report.bundle \
          vdr-accepted-vulnerabilities.json vdr-accepted-vulnerabilities.bundle \
          vdr-history.json vdr-history.bundle \
+         vdr-non-machine-vv.json vdr-non-machine-vv.bundle \
+         vdr-monthly.json vdr-monthly.bundle \
          boundary-map.json boundary-map.bundle \
          reconcile-report.json reconcile-report.bundle \
-         trust-center.json trust-center.bundle; do
+         trust-center.json trust-center.bundle \
+         incident-reports.json incident-reports.bundle \
+         incident-deliveries.json incident-deliveries.bundle; do
   if curl -fsS --max-time 30 -o "$work/$f" "$BASE/$f"; then
     echo "  got  $f ($(wc -c < "$work/$f") bytes)"
   else
@@ -108,14 +142,16 @@ done
 
 echo ""
 echo "== 1. Signatures + provenance (independent: Sigstore + pinned workflow identity) =="
-if verify_blob_any_identity "$work/ksi-signal.bundle" "$work/ksi-signal.json" "$IDENTITY"; then
+# shellcheck disable=SC2046  # signers_for prints a word list by design
+if verify_blob_any_identity "$work/ksi-signal.bundle" "$work/ksi-signal.json" $(signers_for ksi-signal.json); then
   ok "ksi-signal.json signed by the pinned workflow on main"
 else
   bad "ksi-signal.json signature"
 fi
 
+# shellcheck disable=SC2046
 if verify_attestation_any_identity "$work/security-decision-record.json.intoto.jsonl" \
-     "$work/security-decision-record.json" "$IDENTITY"; then
+     "$work/security-decision-record.json" $(signers_for security-decision-record.json.intoto.jsonl); then
   ok "security-decision-record.json attestation signed by the pinned workflow on main"
 else
   bad "security-decision-record.json attestation signature"
@@ -123,13 +159,14 @@ fi
 
 # The CR26 record (SDR, CPO) and the trust center's own data: the generated
 # boundary map, the gate's report and the trust center itself.
-for art in security-decision-record certification-package-overview boundary-map reconcile-report trust-center; do
-  if verify_blob_any_identity "$work/$art.bundle" "$work/$art.json" "$IDENTITY"; then
+for art in security-decision-record certification-package-overview boundary-map reconcile-report trust-center ongoing-certification-report; do
+  # shellcheck disable=SC2046  # a word list by design
+  if verify_blob_any_identity "$work/$art.bundle" "$work/$art.json" $(signers_for "$art.json"); then
     ok "$art.json signed by the pinned workflow on main"
   else
     bad "$art.json signature"
   fi
-  if [ "$(jq -r .ksi_signal_id "$work/$art.json")" = "$(jq -r .signal_id "$work/ksi-signal.json")" ]; then
+  if [ "$(jq -r '.ksi_signal_id // .providerExtensions.ksi_signal_id' "$work/$art.json")" = "$(jq -r .signal_id "$work/ksi-signal.json")" ]; then
     ok "$art.json is bound to the published inventory"
   else
     bad "$art.json names a different inventory than ksi-signal.json"
@@ -141,7 +178,9 @@ done
 # which may be an earlier one, so only its signature is checked here.
 if curl -fsS --max-time 30 -o "$work/boundary-corroboration.json" "$BASE/boundary-corroboration.json" \
    && curl -fsS --max-time 30 -o "$work/boundary-corroboration.bundle" "$BASE/boundary-corroboration.bundle"; then
-  if verify_blob_any_identity "$work/boundary-corroboration.bundle" "$work/boundary-corroboration.json" "$IDENTITY"; then
+  # shellcheck disable=SC2046
+  if verify_blob_any_identity "$work/boundary-corroboration.bundle" "$work/boundary-corroboration.json" \
+       $(signers_for boundary-corroboration.json); then
     ok "boundary-corroboration.json signed by the pinned workflow on main"
   else
     bad "boundary-corroboration.json signature"
@@ -151,8 +190,9 @@ else
 fi
 
 # The VDR is refreshed nightly, so either publisher identity is accepted here.
+# shellcheck disable=SC2046
 if verify_attestation_any_identity "$work/vdr-report.json.intoto.jsonl" "$work/vdr-report.json" \
-     "$IDENTITY" "$NIGHTLY_IDENTITY"; then
+     $(signers_for vdr-report.json.intoto.jsonl); then
   ok "vdr-report.json attestation signed by a pinned workflow on main"
 else
   bad "vdr-report.json attestation signature"
@@ -160,7 +200,28 @@ fi
 
 # The CR26 vulnerability reports are rebuilt with the VDR, so either identity too.
 for art in vdr-detail-report vdr-accepted-vulnerabilities vdr-history; do
-  if verify_blob_any_identity "$work/$art.bundle" "$work/$art.json" "$IDENTITY" "$NIGHTLY_IDENTITY"; then
+  # shellcheck disable=SC2046
+  if verify_blob_any_identity "$work/$art.bundle" "$work/$art.json" $(signers_for "$art.json"); then
+    ok "$art.json signed by a pinned workflow on main"
+  else
+    bad "$art.json signature"
+  fi
+done
+# The non-machine V&V status (VDR-TFR-NMV) and the monthly activity report
+# (VER-TFR-MHR), republished with the VDR.
+for art in vdr-non-machine-vv vdr-monthly; do
+  # shellcheck disable=SC2046
+  if verify_blob_any_identity "$work/$art.bundle" "$work/$art.json" $(signers_for "$art.json"); then
+    ok "$art.json signed by a pinned workflow on main"
+  else
+    bad "$art.json signature"
+  fi
+done
+# The incident log and delivery log (IEC-CSO-*): signed by the deploy or by the
+# unattended incident publisher, whichever wrote them last.
+for art in incident-reports incident-deliveries; do
+  # shellcheck disable=SC2046
+  if verify_blob_any_identity "$work/$art.bundle" "$work/$art.json" $(signers_for "$art.json"); then
     ok "$art.json signed by a pinned workflow on main"
   else
     bad "$art.json signature"
diff --git a/scripts/vuln-gate.py b/scripts/vuln-gate.py
index ca2b2ce6..1a4c1fe8 100644
--- a/scripts/vuln-gate.py
+++ b/scripts/vuln-gate.py
@@ -57,7 +57,7 @@
 
 # Sources that produce vulnerabilities (gated here). Config scanners
 # (opa/checkov/tfsec) are governed separately via .checkov.yaml + the VDR maps.
-VULN_SOURCES = {"grype", "zap", "dependabot"}
+VULN_SOURCES = {"grype", "zap", "dependabot", "codeql"}
 
 # The scanner fix state a vendor dependency needs: no fix yet. "wont-fix" (none
 # coming) is not a vendor dependency. Mirrors policies/triage.rego.
diff --git a/security/zap/README.md b/security/zap/README.md
index f5a4c51f..1119c1d7 100644
--- a/security/zap/README.md
+++ b/security/zap/README.md
@@ -1,38 +1,53 @@
 # DAST scans (OWASP ZAP)
 
-Dynamic application security testing runs **weekly in CI**:
-`.github/workflows/zap-dast.yml` runs a passive ZAP baseline scan against
-`https://samaydlette.com`. It keeps one tracking issue up to date and uploads the
-report as the `zap-dast-report` artifact.
+Dynamic application security testing runs **daily and after every successful
+deploy to `main`** in `.github/workflows/zap-dast.yml`, as two scans in one run:
+
+- **Site baseline** (unauthenticated, passive rules) against
+  `https://samaydlette.com`. It keeps one tracking issue up to date and uploads
+  its report as the `zap-dast-report` artifact.
+- **Authenticated API scan** of the Silk Reeling API. The routes come from the
+  app's own OpenAPI document (`/silk-reeling/openapi.json`, the routes the
+  deployed app serves). The scan signs in as a dedicated Cognito scanner user
+  (SRP + TOTP, `scripts/dast-cognito-token.py`; setup in
+  `docs/runbooks/dast-scanner-user.md`) so its requests pass the API Gateway JWT
+  authorizer. Before and after the scan the job checks that an `/api` route
+  answers 200 with the token and 401 without it. Report: the `zap-api-report`
+  artifact.
 
 ## The contract
 
-- The deploy and the nightly fetch the report (`report_json.json`) from the
-  latest successful `main`-branch run of that workflow
-  (`scripts/fetch-detection-feeds.sh`).
-- The VDR build **fails** if there is no such report (`detection.zap.missing`).
-  It also fails if the report is older than **14 days** or carries no
-  `@generated` time (`detection.zap.stale`, `--zap-max-age-days`, the Class C
-  drift-detection cadence). Both are G7 detection checks. Their mode, `block`,
-  is a decision record in `infrastructure/schemas/gate-modes.json`. A skipped
-  scan never reads as "0 findings".
+- The deploy and the nightly fetch both reports (`report_json.json` of each
+  artifact) from the latest successful `main`-branch run of that workflow,
+  whatever triggered it (`scripts/fetch-detection-feeds.sh`). A run succeeds
+  only when both scans did.
+- The VDR build **fails** if there is no baseline report
+  (`detection.zap.missing`), or if it is more than **3 days** old or carries no
+  `@generated` time (`detection.zap.stale`, `--zap-max-age-days 3`, the Class C
+  sample-detection cadence of VDR-TFR-PSD).
+- The detection gate **fails** the run if the API report is missing, malformed
+  or more than **72 hours** old (`detection.zap-api`,
+  `infrastructure/schemas/detection-feeds.json`).
+- All three are G7 detection checks. Their mode, `block`, is a decision record
+  in `infrastructure/schemas/gate-modes.json`. A skipped scan never reads as
+  "0 findings".
 - Every ZAP alert above informational then flows into the VDR as a
-  vulnerability. The **vulnerability gate** (`scripts/vuln-gate.py`) fails the
-  build unless each one is fixed or covered by an in-force decision in
-  `data/decisions.json`. Allowlisted alerts are recorded in
-  `allowlist.json`.
+  vulnerability: the baseline's as `zap-`, the API scan's as
+  `zap-api-` (`scripts/_zap_api.py`), so each is decided on its own.
+  The **vulnerability gate** (`scripts/vuln-gate.py`) fails the build unless
+  each one is fixed or covered by an in-force decision in `data/decisions.json`.
+  Allowlisted alerts are recorded in `allowlist.json`.
 
 ## Running a scan by hand
 
 Run **ZAP DAST Scan** from the Actions tab (`workflow_dispatch`) on `main`. The
-next deploy or nightly picks up its artifact.
+next deploy or nightly picks up its artifacts.
 
-A deeper local scan (full or authenticated, including the API) does not feed the
-build. Use it to investigate, and record what it finds as dispositions or
+A deeper local scan (a full active scan of the site) does not feed the build.
+Use it to investigate, and record what it finds as dispositions or
 remediations:
 
 ```
 docker run --rm -v "$PWD:/zap/wrk:rw" ghcr.io/zaproxy/zaproxy:stable \
   zap-full-scan.py -t https://samaydlette.com -J zap-report.json
-# add -z "auth.*" / a context file to cover the authenticated API routes
 ```
diff --git a/security/zap/allowlist.json b/security/zap/allowlist.json
index e8651345..56f66615 100644
--- a/security/zap/allowlist.json
+++ b/security/zap/allowlist.json
@@ -1,4 +1,4 @@
 {
-  "_note": "REQ-IRV-11: where the outside-in probe (the monthly ZAP scan) was allowlisted at the edge, so its results there may not show what an unauthenticated stranger sees. Each entry needs url_prefix, reason, decided_by and decided_on; a malformed file fails the VDR build. A finding is allowlisted only when every URL it was observed at matches an entry. No edge allowlist exists for the scanner today (the estate has no WAF), so there are no entries.",
+  "_note": "REQ-IRV-11: where the outside-in probe (the ZAP scans, daily and after every deploy) was allowlisted at the edge, so its results there may not show what an unauthenticated stranger sees. Each entry needs url_prefix, reason, decided_by and decided_on; a malformed file fails the VDR build. A finding is allowlisted only when every URL it was observed at matches an entry. No edge allowlist exists for the scanner today (the estate has no WAF), so there are no entries.",
   "entries": []
 }
diff --git a/tests/fixtures/agency-access/overdue-denial.json b/tests/fixtures/agency-access/overdue-denial.json
new file mode 100644
index 00000000..2b66b2d2
--- /dev/null
+++ b/tests/fixtures/agency-access/overdue-denial.json
@@ -0,0 +1,7 @@
+{
+  "schema": "agency-access/1",
+  "_note": "Known-bad: a denial on 2026-11-02 with no FedRAMP notice; the 5-business-day window closed on 2026-11-09. Validation as of 2026-11-10 must fail.",
+  "requests": [
+    {"id": "AAR-B01", "agency": "Bureau of Known-Bad Fixtures (simulated)", "simulated": true, "kind": "access", "channel": "simulated request", "received_on": "2026-11-02", "decision": "denied", "decided_on": "2026-11-02", "decided_by": "scripts/agency-access.py rules (automated)", "reason": "Fixture."}
+  ]
+}
diff --git a/tests/fixtures/agency-access/person-in-register.json b/tests/fixtures/agency-access/person-in-register.json
new file mode 100644
index 00000000..204916c2
--- /dev/null
+++ b/tests/fixtures/agency-access/person-in-register.json
@@ -0,0 +1,7 @@
+{
+  "schema": "agency-access/1",
+  "_note": "Known-bad: the register names a person's email address; it records agencies and systems only.",
+  "requests": [
+    {"id": "AAR-B02", "agency": "Bureau of Known-Bad Fixtures (simulated)", "simulated": true, "kind": "access", "channel": "jane.doe@example.gov", "received_on": "2026-11-02"}
+  ]
+}
diff --git a/tests/fixtures/agency-access/real-agency.json b/tests/fixtures/agency-access/real-agency.json
new file mode 100644
index 00000000..88ca23dc
--- /dev/null
+++ b/tests/fixtures/agency-access/real-agency.json
@@ -0,0 +1,7 @@
+{
+  "schema": "agency-access/1",
+  "_note": "Known-bad (DEC-194): an entry not marked simulated, for an agency whose name does not end '(simulated)'. No real agency request is taken; validation must fail.",
+  "requests": [
+    {"id": "AAR-B03", "agency": "Bureau of Known-Bad Fixtures", "kind": "access", "channel": "simulated request", "received_on": "2026-11-02"}
+  ]
+}
diff --git a/tests/fixtures/argparse-twice.py.txt b/tests/fixtures/argparse-twice.py.txt
new file mode 100644
index 00000000..256d694d
--- /dev/null
+++ b/tests/fixtures/argparse-twice.py.txt
@@ -0,0 +1,6 @@
+import argparse
+
+ap = argparse.ArgumentParser()
+ap.add_argument("--incidents", default="../data/incidents.json")
+ap.add_argument("--incidents", default="data/incidents.json")
+ap.parse_args()
diff --git a/tests/fixtures/assessor-guide/unknown-evidence-kind.json b/tests/fixtures/assessor-guide/unknown-evidence-kind.json
new file mode 100644
index 00000000..d71db381
--- /dev/null
+++ b/tests/fixtures/assessor-guide/unknown-evidence-kind.json
@@ -0,0 +1,8 @@
+{
+  "schema": "frr-records/1",
+  "$comment": "Known bad: evidence of a kind the assessor guide cannot tell an assessor how to reproduce.",
+  "records": [
+    {"frr_id": "CDS-CSO-CBF", "status": "Implemented", "implementation": "x",
+     "evidence": [{"kind": "vibes", "ref": "trust me"}]}
+  ]
+}
diff --git a/tests/fixtures/assessor/simulated-set-other-commit.json b/tests/fixtures/assessor/simulated-set-other-commit.json
new file mode 100644
index 00000000..0f8b29b9
--- /dev/null
+++ b/tests/fixtures/assessor/simulated-set-other-commit.json
@@ -0,0 +1,107 @@
+{
+  "assessment_type": "simulated-independent-assessment",
+  "schema_version": "1",
+  "simulated": true,
+  "fedramp_recognized": false,
+  "assessor_id": "NOT-A-REAL-ASSESSOR-ID",
+  "disclaimer": "SIMULATED. Totally Real Assessment Services, LLC is a GitHub Actions workflow in the provider's own repository, wearing a lanyard. It is not independent, it is not a FedRAMP Recognized independent assessment service, its assessor ID is NOT-A-REAL-ASSESSOR-ID, and nothing here is a FedRAMP independent assessment. It exists to show the assessor port working end to end. Our rates are very competitive: free.",
+  "assessor": {
+    "organization": "Totally Real Assessment Services, LLC (simulated)",
+    "key_id": "sigstore-keyless:simulated-assessor.yml"
+  },
+  "issued_at": "2026-11-05T12:00:00+00:00",
+  "subject": {
+    "site": "https://samaydlette.com",
+    "phase": "pre-deploy",
+    "commit": "1111111111111111111111111111111111111111",
+    "signal_id": "00000000-0000-4000-8000-000000000001",
+    "signal_commit": "ffffffffffffffffffffffffffffffffffffffff",
+    "assessor_guide_sha256": "ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff"
+  },
+  "results": {
+    "rules": {
+      "pass": 1,
+      "observation": 1,
+      "fail": 0
+    },
+    "ksis": {
+      "pass": 1,
+      "observation": 0,
+      "fail": 0
+    }
+  },
+  "records": [
+    {
+      "record_type": "assessor-record",
+      "schema_version": "1",
+      "record_id": "TRAS-20261105T120000Z-SDR-CSO-FRR",
+      "assessor": {
+        "organization": "Totally Real Assessment Services, LLC (simulated)",
+        "key_id": "sigstore-keyless:simulated-assessor.yml"
+      },
+      "issued_at": "2026-11-05T12:00:00+00:00",
+      "kind": "finding",
+      "text": "SIMULATED assessment of rule SDR-CSO-FRR, not a FedRAMP Recognized assessment. Result: Pass. Independent verification: test tests/test_sdr.py::test_every_applicable_rule_is_listed_once passed (re-run by the assessor). Independent validation: security-decision-record.json served; signature verified (deploy identity); 3h old (window 720h).",
+      "rule_id": "SDR-CSO-FRR",
+      "signature": {
+        "algorithm": "SIGSTORE_KEYLESS_SET",
+        "value": "632106e406c8aed713dee1a91fc1b2c0053eeb8b280866b7fe72e3f6ba741358",
+        "signed_set": "simulated-assessment.json"
+      }
+    },
+    {
+      "record_type": "assessor-record",
+      "schema_version": "1",
+      "record_id": "TRAS-20261105T120000Z-CDS-CSO-RPS",
+      "assessor": {
+        "organization": "Totally Real Assessment Services, LLC (simulated)",
+        "key_id": "sigstore-keyless:simulated-assessor.yml"
+      },
+      "issued_at": "2026-11-05T12:00:00+00:00",
+      "kind": "finding",
+      "text": "SIMULATED assessment of rule CDS-CSO-RPS, not a FedRAMP Recognized assessment. Result: Pass with observation. Independent verification: Not Applicable (MAY): example. Independent validation: policy-index.json is not yet published; it is first published by the deploy under assessment, and validated at the next assessment.",
+      "rule_id": "CDS-CSO-RPS",
+      "signature": {
+        "algorithm": "SIGSTORE_KEYLESS_SET",
+        "value": "7c82618e3c8f080db94cf5a0f9e77efa81b7276bf634add6294c121a72107dbd",
+        "signed_set": "simulated-assessment.json"
+      }
+    },
+    {
+      "record_type": "assessor-record",
+      "schema_version": "1",
+      "record_id": "TRAS-20261105T120000Z-KSI-CED-RAT",
+      "assessor": {
+        "organization": "Totally Real Assessment Services, LLC (simulated)",
+        "key_id": "sigstore-keyless:simulated-assessor.yml"
+      },
+      "issued_at": "2026-11-05T12:00:00+00:00",
+      "kind": "finding",
+      "text": "SIMULATED assessment of KSI KSI-CED-RAT, not a FedRAMP Recognized assessment. Result: Pass. Independent verification: in the published signal sig-1 with status pass by method documentation. Independent validation: KSI signal served and its signature verified (deploy identity).",
+      "rule_id": "KSI-CED-RAT",
+      "signature": {
+        "algorithm": "SIGSTORE_KEYLESS_SET",
+        "value": "5f529cd3c3f006eac63f176f1e8baac1ce8cc23cae3dbd413ede1b76eb606fdd",
+        "signed_set": "simulated-assessment.json"
+      }
+    },
+    {
+      "record_type": "assessor-record",
+      "schema_version": "1",
+      "record_id": "TRAS-20261105T120000Z-SUMMARY",
+      "assessor": {
+        "organization": "Totally Real Assessment Services, LLC (simulated)",
+        "key_id": "sigstore-keyless:simulated-assessor.yml"
+      },
+      "issued_at": "2026-11-05T12:00:00+00:00",
+      "kind": "summary",
+      "text": "Overall summary (IVV-IAS-OSA), SIMULATED. Totally Real Assessment Services, LLC (simulated) verified and validated all 2 applicable FedRAMP rules and all 1 Key Security Indicators for commit 0000000000000000000000000000000000000000: rules 1 pass, 1 pass with observation, 0 fail; KSIs 1 pass, 0 pass with observation, 0 fail. Failures: none. Areas of dispute: none. Observations: CDS-CSO-RPS: policy-index.json is not yet published; it is first published by the deploy under assessment, and validated at the next assessment. SIMULATED. Totally Real Assessment Services, LLC is a GitHub Actions workflow in the provider's own repository, wearing a lanyard. It is not independent, it is not a FedRAMP Recognized independent assessment service, its assessor ID is NOT-A-REAL-ASSESSOR-ID, and nothing here is a FedRAMP independent assessment. It exists to show the assessor port working end to end. Our rates are very competitive: free.",
+      "signature": {
+        "algorithm": "SIGSTORE_KEYLESS_SET",
+        "value": "807d840be4064f51bc9ab05e8d6814b0611981b42d1fb37b5ba86d78b927b136",
+        "signed_set": "simulated-assessment.json"
+      }
+    }
+  ],
+  "$comment": "KNOWN-BAD: a genuine, validly signed set that covers another commit (1111...), so it is no evidence for commit 0000...; scripts/_assessor.py must refuse it."
+}
diff --git a/tests/fixtures/assessor/simulated-set-other-signal.json b/tests/fixtures/assessor/simulated-set-other-signal.json
new file mode 100644
index 00000000..5fe913ad
--- /dev/null
+++ b/tests/fixtures/assessor/simulated-set-other-signal.json
@@ -0,0 +1,107 @@
+{
+  "assessment_type": "simulated-independent-assessment",
+  "schema_version": "1",
+  "simulated": true,
+  "fedramp_recognized": false,
+  "assessor_id": "NOT-A-REAL-ASSESSOR-ID",
+  "disclaimer": "SIMULATED. Totally Real Assessment Services, LLC is a GitHub Actions workflow in the provider's own repository, wearing a lanyard. It is not independent, it is not a FedRAMP Recognized independent assessment service, its assessor ID is NOT-A-REAL-ASSESSOR-ID, and nothing here is a FedRAMP independent assessment. It exists to show the assessor port working end to end. Our rates are very competitive: free.",
+  "assessor": {
+    "organization": "Totally Real Assessment Services, LLC (simulated)",
+    "key_id": "sigstore-keyless:simulated-assessor.yml"
+  },
+  "issued_at": "2026-11-05T12:00:00+00:00",
+  "subject": {
+    "site": "https://samaydlette.com",
+    "phase": "pre-deploy",
+    "commit": "0000000000000000000000000000000000000000",
+    "signal_id": "00000000-0000-4000-8000-000000000002",
+    "signal_commit": "ffffffffffffffffffffffffffffffffffffffff",
+    "assessor_guide_sha256": "ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff"
+  },
+  "results": {
+    "rules": {
+      "pass": 1,
+      "observation": 1,
+      "fail": 0
+    },
+    "ksis": {
+      "pass": 1,
+      "observation": 0,
+      "fail": 0
+    }
+  },
+  "records": [
+    {
+      "record_type": "assessor-record",
+      "schema_version": "1",
+      "record_id": "TRAS-20261105T120000Z-SDR-CSO-FRR",
+      "assessor": {
+        "organization": "Totally Real Assessment Services, LLC (simulated)",
+        "key_id": "sigstore-keyless:simulated-assessor.yml"
+      },
+      "issued_at": "2026-11-05T12:00:00+00:00",
+      "kind": "finding",
+      "text": "SIMULATED assessment of rule SDR-CSO-FRR, not a FedRAMP Recognized assessment. Result: Pass. Independent verification: test tests/test_sdr.py::test_every_applicable_rule_is_listed_once passed (re-run by the assessor). Independent validation: security-decision-record.json served; signature verified (deploy identity); 3h old (window 720h).",
+      "rule_id": "SDR-CSO-FRR",
+      "signature": {
+        "algorithm": "SIGSTORE_KEYLESS_SET",
+        "value": "632106e406c8aed713dee1a91fc1b2c0053eeb8b280866b7fe72e3f6ba741358",
+        "signed_set": "simulated-assessment.json"
+      }
+    },
+    {
+      "record_type": "assessor-record",
+      "schema_version": "1",
+      "record_id": "TRAS-20261105T120000Z-CDS-CSO-RPS",
+      "assessor": {
+        "organization": "Totally Real Assessment Services, LLC (simulated)",
+        "key_id": "sigstore-keyless:simulated-assessor.yml"
+      },
+      "issued_at": "2026-11-05T12:00:00+00:00",
+      "kind": "finding",
+      "text": "SIMULATED assessment of rule CDS-CSO-RPS, not a FedRAMP Recognized assessment. Result: Pass with observation. Independent verification: Not Applicable (MAY): example. Independent validation: policy-index.json is not yet published; it is first published by the deploy under assessment, and validated at the next assessment.",
+      "rule_id": "CDS-CSO-RPS",
+      "signature": {
+        "algorithm": "SIGSTORE_KEYLESS_SET",
+        "value": "7c82618e3c8f080db94cf5a0f9e77efa81b7276bf634add6294c121a72107dbd",
+        "signed_set": "simulated-assessment.json"
+      }
+    },
+    {
+      "record_type": "assessor-record",
+      "schema_version": "1",
+      "record_id": "TRAS-20261105T120000Z-KSI-CED-RAT",
+      "assessor": {
+        "organization": "Totally Real Assessment Services, LLC (simulated)",
+        "key_id": "sigstore-keyless:simulated-assessor.yml"
+      },
+      "issued_at": "2026-11-05T12:00:00+00:00",
+      "kind": "finding",
+      "text": "SIMULATED assessment of KSI KSI-CED-RAT, not a FedRAMP Recognized assessment. Result: Pass. Independent verification: in the published signal sig-1 with status pass by method documentation. Independent validation: KSI signal served and its signature verified (deploy identity).",
+      "rule_id": "KSI-CED-RAT",
+      "signature": {
+        "algorithm": "SIGSTORE_KEYLESS_SET",
+        "value": "5f529cd3c3f006eac63f176f1e8baac1ce8cc23cae3dbd413ede1b76eb606fdd",
+        "signed_set": "simulated-assessment.json"
+      }
+    },
+    {
+      "record_type": "assessor-record",
+      "schema_version": "1",
+      "record_id": "TRAS-20261105T120000Z-SUMMARY",
+      "assessor": {
+        "organization": "Totally Real Assessment Services, LLC (simulated)",
+        "key_id": "sigstore-keyless:simulated-assessor.yml"
+      },
+      "issued_at": "2026-11-05T12:00:00+00:00",
+      "kind": "summary",
+      "text": "Overall summary (IVV-IAS-OSA), SIMULATED. Totally Real Assessment Services, LLC (simulated) verified and validated all 2 applicable FedRAMP rules and all 1 Key Security Indicators for commit 0000000000000000000000000000000000000000: rules 1 pass, 1 pass with observation, 0 fail; KSIs 1 pass, 0 pass with observation, 0 fail. Failures: none. Areas of dispute: none. Observations: CDS-CSO-RPS: policy-index.json is not yet published; it is first published by the deploy under assessment, and validated at the next assessment. SIMULATED. Totally Real Assessment Services, LLC is a GitHub Actions workflow in the provider's own repository, wearing a lanyard. It is not independent, it is not a FedRAMP Recognized independent assessment service, its assessor ID is NOT-A-REAL-ASSESSOR-ID, and nothing here is a FedRAMP independent assessment. It exists to show the assessor port working end to end. Our rates are very competitive: free.",
+      "signature": {
+        "algorithm": "SIGSTORE_KEYLESS_SET",
+        "value": "807d840be4064f51bc9ab05e8d6814b0611981b42d1fb37b5ba86d78b927b136",
+        "signed_set": "simulated-assessment.json"
+      }
+    }
+  ],
+  "$comment": "KNOWN-BAD: a genuine, validly signed set that validated another published KSI signal; scripts/_assessor.py must refuse it."
+}
diff --git a/tests/fixtures/assessor/simulated-set-tampered.json b/tests/fixtures/assessor/simulated-set-tampered.json
new file mode 100644
index 00000000..6064dcc5
--- /dev/null
+++ b/tests/fixtures/assessor/simulated-set-tampered.json
@@ -0,0 +1,106 @@
+{
+  "assessment_type": "simulated-independent-assessment",
+  "schema_version": "1",
+  "simulated": true,
+  "fedramp_recognized": false,
+  "assessor_id": "NOT-A-REAL-ASSESSOR-ID",
+  "disclaimer": "SIMULATED. Totally Real Assessment Services, LLC is a GitHub Actions workflow in the provider's own repository, wearing a lanyard. It is not independent, it is not a FedRAMP Recognized independent assessment service, its assessor ID is NOT-A-REAL-ASSESSOR-ID, and nothing here is a FedRAMP independent assessment. It exists to show the assessor port working end to end. Our rates are very competitive: free.",
+  "assessor": {
+    "organization": "Totally Real Assessment Services, LLC (simulated)",
+    "key_id": "sigstore-keyless:simulated-assessor.yml"
+  },
+  "issued_at": "2026-11-05T12:00:00+00:00",
+  "subject": {
+    "site": "https://samaydlette.com",
+    "phase": "pre-deploy",
+    "commit": "0000000000000000000000000000000000000000",
+    "signal_id": "00000000-0000-4000-8000-000000000001",
+    "signal_commit": "ffffffffffffffffffffffffffffffffffffffff",
+    "assessor_guide_sha256": "ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff"
+  },
+  "results": {
+    "rules": {
+      "pass": 1,
+      "observation": 1,
+      "fail": 0
+    },
+    "ksis": {
+      "pass": 1,
+      "observation": 0,
+      "fail": 0
+    }
+  },
+  "records": [
+    {
+      "record_type": "assessor-record",
+      "schema_version": "1",
+      "record_id": "TRAS-20261105T120000Z-SDR-CSO-FRR",
+      "assessor": {
+        "organization": "Totally Real Assessment Services, LLC (simulated)",
+        "key_id": "sigstore-keyless:simulated-assessor.yml"
+      },
+      "issued_at": "2026-11-05T12:00:00+00:00",
+      "kind": "finding",
+      "text": "SIMULATED assessment of rule SDR-CSO-FRR, not a FedRAMP Recognized assessment. Result: Pass with flying colours. Independent verification: test tests/test_sdr.py::test_every_applicable_rule_is_listed_once passed (re-run by the assessor). Independent validation: security-decision-record.json served; signature verified (deploy identity); 3h old (window 720h).",
+      "rule_id": "SDR-CSO-FRR",
+      "signature": {
+        "algorithm": "SIGSTORE_KEYLESS_SET",
+        "value": "632106e406c8aed713dee1a91fc1b2c0053eeb8b280866b7fe72e3f6ba741358",
+        "signed_set": "simulated-assessment.json"
+      }
+    },
+    {
+      "record_type": "assessor-record",
+      "schema_version": "1",
+      "record_id": "TRAS-20261105T120000Z-CDS-CSO-RPS",
+      "assessor": {
+        "organization": "Totally Real Assessment Services, LLC (simulated)",
+        "key_id": "sigstore-keyless:simulated-assessor.yml"
+      },
+      "issued_at": "2026-11-05T12:00:00+00:00",
+      "kind": "finding",
+      "text": "SIMULATED assessment of rule CDS-CSO-RPS, not a FedRAMP Recognized assessment. Result: Pass with observation. Independent verification: Not Applicable (MAY): example. Independent validation: policy-index.json is not yet published; it is first published by the deploy under assessment, and validated at the next assessment.",
+      "rule_id": "CDS-CSO-RPS",
+      "signature": {
+        "algorithm": "SIGSTORE_KEYLESS_SET",
+        "value": "7c82618e3c8f080db94cf5a0f9e77efa81b7276bf634add6294c121a72107dbd",
+        "signed_set": "simulated-assessment.json"
+      }
+    },
+    {
+      "record_type": "assessor-record",
+      "schema_version": "1",
+      "record_id": "TRAS-20261105T120000Z-KSI-CED-RAT",
+      "assessor": {
+        "organization": "Totally Real Assessment Services, LLC (simulated)",
+        "key_id": "sigstore-keyless:simulated-assessor.yml"
+      },
+      "issued_at": "2026-11-05T12:00:00+00:00",
+      "kind": "finding",
+      "text": "SIMULATED assessment of KSI KSI-CED-RAT, not a FedRAMP Recognized assessment. Result: Pass. Independent verification: in the published signal sig-1 with status pass by method documentation. Independent validation: KSI signal served and its signature verified (deploy identity).",
+      "rule_id": "KSI-CED-RAT",
+      "signature": {
+        "algorithm": "SIGSTORE_KEYLESS_SET",
+        "value": "5f529cd3c3f006eac63f176f1e8baac1ce8cc23cae3dbd413ede1b76eb606fdd",
+        "signed_set": "simulated-assessment.json"
+      }
+    },
+    {
+      "record_type": "assessor-record",
+      "schema_version": "1",
+      "record_id": "TRAS-20261105T120000Z-SUMMARY",
+      "assessor": {
+        "organization": "Totally Real Assessment Services, LLC (simulated)",
+        "key_id": "sigstore-keyless:simulated-assessor.yml"
+      },
+      "issued_at": "2026-11-05T12:00:00+00:00",
+      "kind": "summary",
+      "text": "Overall summary (IVV-IAS-OSA), SIMULATED. Totally Real Assessment Services, LLC (simulated) verified and validated all 2 applicable FedRAMP rules and all 1 Key Security Indicators for commit 0000000000000000000000000000000000000000: rules 1 pass, 1 pass with observation, 0 fail; KSIs 1 pass, 0 pass with observation, 0 fail. Failures: none. Areas of dispute: none. Observations: CDS-CSO-RPS: policy-index.json is not yet published; it is first published by the deploy under assessment, and validated at the next assessment. SIMULATED. Totally Real Assessment Services, LLC is a GitHub Actions workflow in the provider's own repository, wearing a lanyard. It is not independent, it is not a FedRAMP Recognized independent assessment service, its assessor ID is NOT-A-REAL-ASSESSOR-ID, and nothing here is a FedRAMP independent assessment. It exists to show the assessor port working end to end. Our rates are very competitive: free.",
+      "signature": {
+        "algorithm": "SIGSTORE_KEYLESS_SET",
+        "value": "807d840be4064f51bc9ab05e8d6814b0611981b42d1fb37b5ba86d78b927b136",
+        "signed_set": "simulated-assessment.json"
+      }
+    }
+  ]
+}
diff --git a/tests/fixtures/assessor/simulated-set.json b/tests/fixtures/assessor/simulated-set.json
new file mode 100644
index 00000000..0e50b226
--- /dev/null
+++ b/tests/fixtures/assessor/simulated-set.json
@@ -0,0 +1,106 @@
+{
+  "assessment_type": "simulated-independent-assessment",
+  "schema_version": "1",
+  "simulated": true,
+  "fedramp_recognized": false,
+  "assessor_id": "NOT-A-REAL-ASSESSOR-ID",
+  "disclaimer": "SIMULATED. Totally Real Assessment Services, LLC is a GitHub Actions workflow in the provider's own repository, wearing a lanyard. It is not independent, it is not a FedRAMP Recognized independent assessment service, its assessor ID is NOT-A-REAL-ASSESSOR-ID, and nothing here is a FedRAMP independent assessment. It exists to show the assessor port working end to end. Our rates are very competitive: free.",
+  "assessor": {
+    "organization": "Totally Real Assessment Services, LLC (simulated)",
+    "key_id": "sigstore-keyless:simulated-assessor.yml"
+  },
+  "issued_at": "2026-11-05T12:00:00+00:00",
+  "subject": {
+    "site": "https://samaydlette.com",
+    "phase": "pre-deploy",
+    "commit": "0000000000000000000000000000000000000000",
+    "signal_id": "00000000-0000-4000-8000-000000000001",
+    "signal_commit": "ffffffffffffffffffffffffffffffffffffffff",
+    "assessor_guide_sha256": "ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff"
+  },
+  "results": {
+    "rules": {
+      "pass": 1,
+      "observation": 1,
+      "fail": 0
+    },
+    "ksis": {
+      "pass": 1,
+      "observation": 0,
+      "fail": 0
+    }
+  },
+  "records": [
+    {
+      "record_type": "assessor-record",
+      "schema_version": "1",
+      "record_id": "TRAS-20261105T120000Z-SDR-CSO-FRR",
+      "assessor": {
+        "organization": "Totally Real Assessment Services, LLC (simulated)",
+        "key_id": "sigstore-keyless:simulated-assessor.yml"
+      },
+      "issued_at": "2026-11-05T12:00:00+00:00",
+      "kind": "finding",
+      "text": "SIMULATED assessment of rule SDR-CSO-FRR, not a FedRAMP Recognized assessment. Result: Pass. Independent verification: test tests/test_sdr.py::test_every_applicable_rule_is_listed_once passed (re-run by the assessor). Independent validation: security-decision-record.json served; signature verified (deploy identity); 3h old (window 720h).",
+      "rule_id": "SDR-CSO-FRR",
+      "signature": {
+        "algorithm": "SIGSTORE_KEYLESS_SET",
+        "value": "632106e406c8aed713dee1a91fc1b2c0053eeb8b280866b7fe72e3f6ba741358",
+        "signed_set": "simulated-assessment.json"
+      }
+    },
+    {
+      "record_type": "assessor-record",
+      "schema_version": "1",
+      "record_id": "TRAS-20261105T120000Z-CDS-CSO-RPS",
+      "assessor": {
+        "organization": "Totally Real Assessment Services, LLC (simulated)",
+        "key_id": "sigstore-keyless:simulated-assessor.yml"
+      },
+      "issued_at": "2026-11-05T12:00:00+00:00",
+      "kind": "finding",
+      "text": "SIMULATED assessment of rule CDS-CSO-RPS, not a FedRAMP Recognized assessment. Result: Pass with observation. Independent verification: Not Applicable (MAY): example. Independent validation: policy-index.json is not yet published; it is first published by the deploy under assessment, and validated at the next assessment.",
+      "rule_id": "CDS-CSO-RPS",
+      "signature": {
+        "algorithm": "SIGSTORE_KEYLESS_SET",
+        "value": "7c82618e3c8f080db94cf5a0f9e77efa81b7276bf634add6294c121a72107dbd",
+        "signed_set": "simulated-assessment.json"
+      }
+    },
+    {
+      "record_type": "assessor-record",
+      "schema_version": "1",
+      "record_id": "TRAS-20261105T120000Z-KSI-CED-RAT",
+      "assessor": {
+        "organization": "Totally Real Assessment Services, LLC (simulated)",
+        "key_id": "sigstore-keyless:simulated-assessor.yml"
+      },
+      "issued_at": "2026-11-05T12:00:00+00:00",
+      "kind": "finding",
+      "text": "SIMULATED assessment of KSI KSI-CED-RAT, not a FedRAMP Recognized assessment. Result: Pass. Independent verification: in the published signal sig-1 with status pass by method documentation. Independent validation: KSI signal served and its signature verified (deploy identity).",
+      "rule_id": "KSI-CED-RAT",
+      "signature": {
+        "algorithm": "SIGSTORE_KEYLESS_SET",
+        "value": "5f529cd3c3f006eac63f176f1e8baac1ce8cc23cae3dbd413ede1b76eb606fdd",
+        "signed_set": "simulated-assessment.json"
+      }
+    },
+    {
+      "record_type": "assessor-record",
+      "schema_version": "1",
+      "record_id": "TRAS-20261105T120000Z-SUMMARY",
+      "assessor": {
+        "organization": "Totally Real Assessment Services, LLC (simulated)",
+        "key_id": "sigstore-keyless:simulated-assessor.yml"
+      },
+      "issued_at": "2026-11-05T12:00:00+00:00",
+      "kind": "summary",
+      "text": "Overall summary (IVV-IAS-OSA), SIMULATED. Totally Real Assessment Services, LLC (simulated) verified and validated all 2 applicable FedRAMP rules and all 1 Key Security Indicators for commit 0000000000000000000000000000000000000000: rules 1 pass, 1 pass with observation, 0 fail; KSIs 1 pass, 0 pass with observation, 0 fail. Failures: none. Areas of dispute: none. Observations: CDS-CSO-RPS: policy-index.json is not yet published; it is first published by the deploy under assessment, and validated at the next assessment. SIMULATED. Totally Real Assessment Services, LLC is a GitHub Actions workflow in the provider's own repository, wearing a lanyard. It is not independent, it is not a FedRAMP Recognized independent assessment service, its assessor ID is NOT-A-REAL-ASSESSOR-ID, and nothing here is a FedRAMP independent assessment. It exists to show the assessor port working end to end. Our rates are very competitive: free.",
+      "signature": {
+        "algorithm": "SIGSTORE_KEYLESS_SET",
+        "value": "807d840be4064f51bc9ab05e8d6814b0611981b42d1fb37b5ba86d78b927b136",
+        "signed_set": "simulated-assessment.json"
+      }
+    }
+  ]
+}
diff --git a/tests/fixtures/availability/known-bad-stale-feed.json b/tests/fixtures/availability/known-bad-stale-feed.json
new file mode 100644
index 00000000..14961cf8
--- /dev/null
+++ b/tests/fixtures/availability/known-bad-stale-feed.json
@@ -0,0 +1,2 @@
+{"feed_type": "availability-status", "generated_at": "2026-10-01T00:00:00Z",
+ "samples": [{"t": "2026-10-01T00:00:00Z", "probed": ["site"], "fail": {}}]}
diff --git a/tests/fixtures/bootstrap-iam/state.json b/tests/fixtures/bootstrap-iam/state.json
new file mode 100644
index 00000000..d856e0f1
--- /dev/null
+++ b/tests/fixtures/bootstrap-iam/state.json
@@ -0,0 +1,20 @@
+{"values": {"root_module": {"resources": [
+  {"type": "aws_iam_role", "name": "deploy", "address": "aws_iam_role.deploy",
+   "values": {"arn": "arn:aws:iam::123456789012:role/github-actions-deploy-oidc", "name": "github-actions-deploy-oidc", "assume_role_policy": "{\"x\":1}"}},
+  {"type": "aws_iam_group", "name": "operators", "address": "aws_iam_group.operators",
+   "values": {"arn": "arn:aws:iam::123456789012:group/operators", "name": "operators"}},
+  {"type": "aws_iam_group_policy", "name": "operators_assessment_readonly", "address": "aws_iam_group_policy.operators_assessment_readonly",
+   "values": {"group": "operators", "name": "assessment-readonly", "id": "operators:assessment-readonly", "policy": "{\"Statement\":[{\"Resource\":\"arn:aws:s3:::x-123456789012\"}]}"}},
+  {"type": "aws_iam_group_policy", "name": "operators_s3_bucket", "address": "aws_iam_group_policy.operators_s3_bucket",
+   "values": {"group": "operators", "name": "s3-bucket", "id": "operators:s3-bucket", "policy": "{}"}},
+  {"type": "aws_iam_group_policy", "name": "read_only_deny_sensitive", "address": "aws_iam_group_policy.read_only_deny_sensitive",
+   "values": {"group": "read-only", "name": "deny-secret-values-and-decrypt", "id": "read-only:deny-secret-values-and-decrypt", "policy": "{}"}},
+  {"type": "aws_iam_role_policy_attachment", "name": "legacy", "index": "github_policy_3", "address": "aws_iam_role_policy_attachment.legacy[\"github_policy_3\"]",
+   "values": {"role": "github-actions-deploy-oidc", "policy_arn": "arn:aws:iam::123456789012:policy/github_policy_3", "id": "github-actions-deploy-oidc-20260101"}},
+  {"type": "aws_iam_role_policy_attachment", "name": "legacy", "index": "github_actions_3", "address": "aws_iam_role_policy_attachment.legacy[\"github_actions_3\"]",
+   "values": {"role": "github-actions-deploy-oidc", "policy_arn": "arn:aws:iam::123456789012:policy/github_actions_3", "id": "github-actions-deploy-oidc-20260102"}},
+  {"type": "aws_iam_role_policy_attachment", "name": "plan_read_only", "address": "aws_iam_role_policy_attachment.plan_read_only",
+   "values": {"role": "github-actions-plan", "policy_arn": "arn:aws:iam::aws:policy/ReadOnlyAccess", "id": "github-actions-plan-20260101"}},
+  {"type": "aws_iam_group_policy_attachment", "name": "read_only", "address": "aws_iam_group_policy_attachment.read_only",
+   "values": {"group": "read-only", "policy_arn": "arn:aws:iam::aws:policy/ReadOnlyAccess", "id": "read-only-20260101"}}
+]}}}
diff --git a/tests/fixtures/broken/decisions.json b/tests/fixtures/broken/decisions.json
index a7470bea..0012c945 100644
--- a/tests/fixtures/broken/decisions.json
+++ b/tests/fixtures/broken/decisions.json
@@ -23,7 +23,7 @@
       "disposition": "risk-accepted",
       "justification": "SC-7 met via managed interfaces.",
       "decided_by": "Fixture",
-      "decided_on": "2026-01-01",
+      "decided_on": "2026-01-01", "confirmed_on": "2026-01-01",
       "review_by": "2027-01-01",
       "applies_to": {
         "check_ids": [
diff --git a/tests/fixtures/check-vectors/decided-without-record.json b/tests/fixtures/check-vectors/decided-without-record.json
new file mode 100644
index 00000000..9d99a0b8
--- /dev/null
+++ b/tests/fixtures/check-vectors/decided-without-record.json
@@ -0,0 +1,14 @@
+{
+  "version": "0.0-fixture",
+  "description": "Known-bad: a vector marked decided that names no decision record in force. The build stops.",
+  "vectors": {
+    "CKV_AWS_18": {
+      "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N",
+      "rationale": "Access logging off: weakens detection only.",
+      "decided_by": "Operator",
+      "decided_on": "2026-11-01",
+      "review_by": "2027-11-01",
+      "decision": "DEC-998"
+    }
+  }
+}
diff --git a/tests/fixtures/check-vectors/in-force.json b/tests/fixtures/check-vectors/in-force.json
index c52e2b6f..7161ae85 100644
--- a/tests/fixtures/check-vectors/in-force.json
+++ b/tests/fixtures/check-vectors/in-force.json
@@ -7,7 +7,8 @@
       "rationale": "Access logging off: weakens detection only.",
       "decided_by": "Operator",
       "decided_on": "2026-11-01",
-      "review_by": "2027-11-01"
+      "review_by": "2027-11-01",
+      "decision": "DEC-180"
     }
   }
 }
diff --git a/tests/fixtures/check-vectors/lapsed.json b/tests/fixtures/check-vectors/lapsed.json
index 9c162673..a5fd4023 100644
--- a/tests/fixtures/check-vectors/lapsed.json
+++ b/tests/fixtures/check-vectors/lapsed.json
@@ -7,7 +7,8 @@
       "rationale": "Access logging off: weakens detection only.",
       "decided_by": "Operator",
       "decided_on": "2026-11-01",
-      "review_by": "2026-10-01"
+      "review_by": "2026-10-01",
+      "decision": "DEC-180"
     }
   }
 }
diff --git a/tests/fixtures/clean/decisions.json b/tests/fixtures/clean/decisions.json
index a7470bea..0012c945 100644
--- a/tests/fixtures/clean/decisions.json
+++ b/tests/fixtures/clean/decisions.json
@@ -23,7 +23,7 @@
       "disposition": "risk-accepted",
       "justification": "SC-7 met via managed interfaces.",
       "decided_by": "Fixture",
-      "decided_on": "2026-01-01",
+      "decided_on": "2026-01-01", "confirmed_on": "2026-01-01",
       "review_by": "2027-01-01",
       "applies_to": {
         "check_ids": [
diff --git a/tests/fixtures/corroboration/signatures-by-writer.json b/tests/fixtures/corroboration/signatures-by-writer.json
new file mode 100644
index 00000000..54504a6e
--- /dev/null
+++ b/tests/fixtures/corroboration/signatures-by-writer.json
@@ -0,0 +1,97 @@
+{
+  "$comment": "KNOWN-BAD (tests/test_corroborate_checks.py): signatures judged by who may write each file (scripts/_signers.py), not by cadence. ocr-issues.json is signed by the deploy, which never writes it, and vdr-report.json by the package maintainer, which never writes it: both differ. The others are signed by a workflow that writes them, though a cadence-based check expected another (the maintainer for the nightly-cadence indexes, the assessor and the incident publisher for their own files).",
+  "artifacts": [
+    {
+      "artifact": ".well-known/ocr-issues.json",
+      "kind": "bundle",
+      "bundle": ".well-known/ocr-issues.bundle",
+      "cadence": "nightly"
+    },
+    {
+      "artifact": ".well-known/quarterly-reviews.json",
+      "kind": "bundle",
+      "bundle": ".well-known/quarterly-reviews.bundle",
+      "cadence": "nightly"
+    },
+    {
+      "artifact": ".well-known/security-decision-record.json",
+      "kind": "bundle",
+      "bundle": ".well-known/security-decision-record.bundle",
+      "cadence": "deploy"
+    },
+    {
+      "artifact": ".well-known/simulated-assessment.json",
+      "kind": "bundle",
+      "bundle": ".well-known/simulated-assessment.bundle",
+      "cadence": "deploy"
+    },
+    {
+      "artifact": ".well-known/incident-reports.json",
+      "kind": "bundle",
+      "bundle": ".well-known/incident-reports.bundle",
+      "cadence": "nightly"
+    },
+    {
+      "artifact": ".well-known/vdr-report.json",
+      "kind": "bundle",
+      "bundle": ".well-known/vdr-report.bundle",
+      "cadence": "nightly"
+    }
+  ],
+  "facts": [
+    {
+      "artifact": ".well-known/ocr-issues.json",
+      "verified": true,
+      "signed_by": "https://github.com/sam-aydlette/samaydlette.com/.github/workflows/deploy-with-opa.yml@refs/heads/main",
+      "issuer": "https://token.actions.githubusercontent.com",
+      "cert": {
+        "ref": "refs/heads/main"
+      }
+    },
+    {
+      "artifact": ".well-known/quarterly-reviews.json",
+      "verified": true,
+      "signed_by": "https://github.com/sam-aydlette/samaydlette.com/.github/workflows/package-maintenance.yml@refs/heads/main",
+      "issuer": "https://token.actions.githubusercontent.com",
+      "cert": {
+        "ref": "refs/heads/main"
+      }
+    },
+    {
+      "artifact": ".well-known/security-decision-record.json",
+      "verified": true,
+      "signed_by": "https://github.com/sam-aydlette/samaydlette.com/.github/workflows/package-maintenance.yml@refs/heads/main",
+      "issuer": "https://token.actions.githubusercontent.com",
+      "cert": {
+        "ref": "refs/heads/main"
+      }
+    },
+    {
+      "artifact": ".well-known/simulated-assessment.json",
+      "verified": true,
+      "signed_by": "https://github.com/sam-aydlette/samaydlette.com/.github/workflows/simulated-assessor.yml@refs/heads/main",
+      "issuer": "https://token.actions.githubusercontent.com",
+      "cert": {
+        "ref": "refs/heads/main"
+      }
+    },
+    {
+      "artifact": ".well-known/incident-reports.json",
+      "verified": true,
+      "signed_by": "https://github.com/sam-aydlette/samaydlette.com/.github/workflows/incident-reports.yml@refs/heads/main",
+      "issuer": "https://token.actions.githubusercontent.com",
+      "cert": {
+        "ref": "refs/heads/main"
+      }
+    },
+    {
+      "artifact": ".well-known/vdr-report.json",
+      "verified": true,
+      "signed_by": "https://github.com/sam-aydlette/samaydlette.com/.github/workflows/package-maintenance.yml@refs/heads/main",
+      "issuer": "https://token.actions.githubusercontent.com",
+      "cert": {
+        "ref": "refs/heads/main"
+      }
+    }
+  ]
+}
diff --git a/tests/fixtures/cr26/decisions.json b/tests/fixtures/cr26/decisions.json
index eec0602e..d08eb3de 100644
--- a/tests/fixtures/cr26/decisions.json
+++ b/tests/fixtures/cr26/decisions.json
@@ -9,7 +9,7 @@
       "disposition": "risk-accepted",
       "justification": "Single origin; failover would need a second region.",
       "decided_by": "Fixture",
-      "decided_on": "2026-01-01",
+      "decided_on": "2026-01-01", "confirmed_on": "2026-01-01",
       "review_by": "2027-01-01",
       "applies_to": {
         "check_ids": [
@@ -26,7 +26,7 @@
       "disposition": "operational-requirement",
       "justification": "The public bucket must serve the site; public read is the product.",
       "decided_by": "Fixture",
-      "decided_on": "2026-01-01",
+      "decided_on": "2026-01-01", "confirmed_on": "2026-01-01",
       "review_by": "2027-01-01",
       "applies_to": {
         "check_ids": [
@@ -43,7 +43,7 @@
       "disposition": "false-positive",
       "justification": "The rule matches article prose, not code.",
       "decided_by": "Fixture",
-      "decided_on": "2026-01-01",
+      "decided_on": "2026-01-01", "confirmed_on": "2026-01-01",
       "review_by": "2027-01-01",
       "applies_to": {
         "check_ids": [
@@ -60,7 +60,7 @@
       "disposition": "risk-accepted",
       "justification": "Cost trade-off; Shield Standard is the baseline.",
       "decided_by": "Fixture",
-      "decided_on": "2026-01-01",
+      "decided_on": "2026-01-01", "confirmed_on": "2026-01-01",
       "review_by": "2027-01-01",
       "applies_to": {
         "check_ids": [
@@ -77,7 +77,7 @@
       "disposition": "mitigated",
       "justification": "The vulnerable path is unreachable behind the authorizer.",
       "decided_by": "Fixture",
-      "decided_on": "2026-01-01",
+      "decided_on": "2026-01-01", "confirmed_on": "2026-01-01",
       "review_by": "2027-01-01",
       "applies_to": {
         "check_ids": [],
diff --git a/tests/fixtures/cycle/bad/calendar-irregular-gap.json b/tests/fixtures/cycle/bad/calendar-irregular-gap.json
new file mode 100644
index 00000000..c4da590d
--- /dev/null
+++ b/tests/fixtures/cycle/bad/calendar-irregular-gap.json
@@ -0,0 +1,60 @@
+{
+  "$comment": "The quarterly Collaborative Continuous Monitoring calendar (CCM-OCR-SOR, CCM-QTR-SAR). Fixed Ongoing Certification Report issue dates, about 3 months apart, placed late in the second month of each quarter (about day 55), away from the beginning, middle and end of the quarter. Each Quarterly Review is a fixed number of business days after its report, counted over the federal holidays listed here. scripts/_ccm.py validates this file (fail-closed) and every report, the CPO and the review calendar file read their dates from it; nothing computes a date from 'now'. Extend the issue dates and holidays before the calendar runs out: the build fails when fewer than two issue dates lie ahead.",
+  "schema": "ccm-calendar/1",
+  "decided_by": "Sam Aydlette",
+  "decided_on": "2026-11-05",
+  "review_by": "2027-11-05",
+  "rationale": "Issue on a Tuesday late in each quarter's middle month: a fixed, predictable cycle that is spread out from the start, middle and end of each quarter, as CCM-OCR-SOR asks. The review follows 5 business days later, inside the 3-to-10 business day window of CCM-QTR-SAR, leaving time to read the report first.",
+  "ocr_issue_dates": [
+    "2026-11-24",
+    "2027-02-23",
+    "2027-08-24",
+    "2027-11-23",
+    "2028-02-29",
+    "2028-05-30",
+    "2028-08-29",
+    "2028-11-28"
+  ],
+  "review_business_days_after_issue": 5,
+  "review_start_utc": "17:00",
+  "review_duration_minutes": 45,
+  "holidays": {
+    "source": "U.S. federal holidays (5 U.S.C. 6103), observed dates",
+    "covers_through": "2028-12-31",
+    "dates": [
+      "2026-01-01",
+      "2026-01-19",
+      "2026-02-16",
+      "2026-05-25",
+      "2026-06-19",
+      "2026-07-03",
+      "2026-09-07",
+      "2026-10-12",
+      "2026-11-11",
+      "2026-11-26",
+      "2026-12-25",
+      "2027-01-01",
+      "2027-01-18",
+      "2027-02-15",
+      "2027-05-31",
+      "2027-06-18",
+      "2027-07-05",
+      "2027-09-06",
+      "2027-10-11",
+      "2027-11-11",
+      "2027-11-25",
+      "2027-12-24",
+      "2027-12-31",
+      "2028-01-17",
+      "2028-02-21",
+      "2028-05-29",
+      "2028-06-19",
+      "2028-07-04",
+      "2028-09-04",
+      "2028-10-09",
+      "2028-11-10",
+      "2028-11-23",
+      "2028-12-25"
+    ]
+  }
+}
diff --git a/tests/fixtures/cycle/bad/calendar-issue-on-holiday.json b/tests/fixtures/cycle/bad/calendar-issue-on-holiday.json
new file mode 100644
index 00000000..a35b794a
--- /dev/null
+++ b/tests/fixtures/cycle/bad/calendar-issue-on-holiday.json
@@ -0,0 +1,61 @@
+{
+  "$comment": "The quarterly Collaborative Continuous Monitoring calendar (CCM-OCR-SOR, CCM-QTR-SAR). Fixed Ongoing Certification Report issue dates, about 3 months apart, placed late in the second month of each quarter (about day 55), away from the beginning, middle and end of the quarter. Each Quarterly Review is a fixed number of business days after its report, counted over the federal holidays listed here. scripts/_ccm.py validates this file (fail-closed) and every report, the CPO and the review calendar file read their dates from it; nothing computes a date from 'now'. Extend the issue dates and holidays before the calendar runs out: the build fails when fewer than two issue dates lie ahead.",
+  "schema": "ccm-calendar/1",
+  "decided_by": "Sam Aydlette",
+  "decided_on": "2026-11-05",
+  "review_by": "2027-11-05",
+  "rationale": "Issue on a Tuesday late in each quarter's middle month: a fixed, predictable cycle that is spread out from the start, middle and end of each quarter, as CCM-OCR-SOR asks. The review follows 5 business days later, inside the 3-to-10 business day window of CCM-QTR-SAR, leaving time to read the report first.",
+  "ocr_issue_dates": [
+    "2026-11-26",
+    "2027-02-23",
+    "2027-05-25",
+    "2027-08-24",
+    "2027-11-23",
+    "2028-02-29",
+    "2028-05-30",
+    "2028-08-29",
+    "2028-11-28"
+  ],
+  "review_business_days_after_issue": 5,
+  "review_start_utc": "17:00",
+  "review_duration_minutes": 45,
+  "holidays": {
+    "source": "U.S. federal holidays (5 U.S.C. 6103), observed dates",
+    "covers_through": "2028-12-31",
+    "dates": [
+      "2026-01-01",
+      "2026-01-19",
+      "2026-02-16",
+      "2026-05-25",
+      "2026-06-19",
+      "2026-07-03",
+      "2026-09-07",
+      "2026-10-12",
+      "2026-11-11",
+      "2026-11-26",
+      "2026-12-25",
+      "2027-01-01",
+      "2027-01-18",
+      "2027-02-15",
+      "2027-05-31",
+      "2027-06-18",
+      "2027-07-05",
+      "2027-09-06",
+      "2027-10-11",
+      "2027-11-11",
+      "2027-11-25",
+      "2027-12-24",
+      "2027-12-31",
+      "2028-01-17",
+      "2028-02-21",
+      "2028-05-29",
+      "2028-06-19",
+      "2028-07-04",
+      "2028-09-04",
+      "2028-10-09",
+      "2028-11-10",
+      "2028-11-23",
+      "2028-12-25"
+    ]
+  }
+}
diff --git a/tests/fixtures/cycle/bad/calendar-mid-quarter.json b/tests/fixtures/cycle/bad/calendar-mid-quarter.json
new file mode 100644
index 00000000..375090cd
--- /dev/null
+++ b/tests/fixtures/cycle/bad/calendar-mid-quarter.json
@@ -0,0 +1,61 @@
+{
+  "$comment": "The quarterly Collaborative Continuous Monitoring calendar (CCM-OCR-SOR, CCM-QTR-SAR). Fixed Ongoing Certification Report issue dates, about 3 months apart, placed late in the second month of each quarter (about day 55), away from the beginning, middle and end of the quarter. Each Quarterly Review is a fixed number of business days after its report, counted over the federal holidays listed here. scripts/_ccm.py validates this file (fail-closed) and every report, the CPO and the review calendar file read their dates from it; nothing computes a date from 'now'. Extend the issue dates and holidays before the calendar runs out: the build fails when fewer than two issue dates lie ahead.",
+  "schema": "ccm-calendar/1",
+  "decided_by": "Sam Aydlette",
+  "decided_on": "2026-11-05",
+  "review_by": "2027-11-05",
+  "rationale": "Issue on a Tuesday late in each quarter's middle month: a fixed, predictable cycle that is spread out from the start, middle and end of each quarter, as CCM-OCR-SOR asks. The review follows 5 business days later, inside the 3-to-10 business day window of CCM-QTR-SAR, leaving time to read the report first.",
+  "ocr_issue_dates": [
+    "2026-11-24",
+    "2027-02-16",
+    "2027-05-25",
+    "2027-08-24",
+    "2027-11-23",
+    "2028-02-29",
+    "2028-05-30",
+    "2028-08-29",
+    "2028-11-28"
+  ],
+  "review_business_days_after_issue": 5,
+  "review_start_utc": "17:00",
+  "review_duration_minutes": 45,
+  "holidays": {
+    "source": "U.S. federal holidays (5 U.S.C. 6103), observed dates",
+    "covers_through": "2028-12-31",
+    "dates": [
+      "2026-01-01",
+      "2026-01-19",
+      "2026-02-16",
+      "2026-05-25",
+      "2026-06-19",
+      "2026-07-03",
+      "2026-09-07",
+      "2026-10-12",
+      "2026-11-11",
+      "2026-11-26",
+      "2026-12-25",
+      "2027-01-01",
+      "2027-01-18",
+      "2027-02-15",
+      "2027-05-31",
+      "2027-06-18",
+      "2027-07-05",
+      "2027-09-06",
+      "2027-10-11",
+      "2027-11-11",
+      "2027-11-25",
+      "2027-12-24",
+      "2027-12-31",
+      "2028-01-17",
+      "2028-02-21",
+      "2028-05-29",
+      "2028-06-19",
+      "2028-07-04",
+      "2028-09-04",
+      "2028-10-09",
+      "2028-11-10",
+      "2028-11-23",
+      "2028-12-25"
+    ]
+  }
+}
diff --git a/tests/fixtures/cycle/bad/calendar-review-too-soon.json b/tests/fixtures/cycle/bad/calendar-review-too-soon.json
new file mode 100644
index 00000000..77331df6
--- /dev/null
+++ b/tests/fixtures/cycle/bad/calendar-review-too-soon.json
@@ -0,0 +1,61 @@
+{
+  "$comment": "The quarterly Collaborative Continuous Monitoring calendar (CCM-OCR-SOR, CCM-QTR-SAR). Fixed Ongoing Certification Report issue dates, about 3 months apart, placed late in the second month of each quarter (about day 55), away from the beginning, middle and end of the quarter. Each Quarterly Review is a fixed number of business days after its report, counted over the federal holidays listed here. scripts/_ccm.py validates this file (fail-closed) and every report, the CPO and the review calendar file read their dates from it; nothing computes a date from 'now'. Extend the issue dates and holidays before the calendar runs out: the build fails when fewer than two issue dates lie ahead.",
+  "schema": "ccm-calendar/1",
+  "decided_by": "Sam Aydlette",
+  "decided_on": "2026-11-05",
+  "review_by": "2027-11-05",
+  "rationale": "Issue on a Tuesday late in each quarter's middle month: a fixed, predictable cycle that is spread out from the start, middle and end of each quarter, as CCM-OCR-SOR asks. The review follows 5 business days later, inside the 3-to-10 business day window of CCM-QTR-SAR, leaving time to read the report first.",
+  "ocr_issue_dates": [
+    "2026-11-24",
+    "2027-02-23",
+    "2027-05-25",
+    "2027-08-24",
+    "2027-11-23",
+    "2028-02-29",
+    "2028-05-30",
+    "2028-08-29",
+    "2028-11-28"
+  ],
+  "review_business_days_after_issue": 2,
+  "review_start_utc": "17:00",
+  "review_duration_minutes": 45,
+  "holidays": {
+    "source": "U.S. federal holidays (5 U.S.C. 6103), observed dates",
+    "covers_through": "2028-12-31",
+    "dates": [
+      "2026-01-01",
+      "2026-01-19",
+      "2026-02-16",
+      "2026-05-25",
+      "2026-06-19",
+      "2026-07-03",
+      "2026-09-07",
+      "2026-10-12",
+      "2026-11-11",
+      "2026-11-26",
+      "2026-12-25",
+      "2027-01-01",
+      "2027-01-18",
+      "2027-02-15",
+      "2027-05-31",
+      "2027-06-18",
+      "2027-07-05",
+      "2027-09-06",
+      "2027-10-11",
+      "2027-11-11",
+      "2027-11-25",
+      "2027-12-24",
+      "2027-12-31",
+      "2028-01-17",
+      "2028-02-21",
+      "2028-05-29",
+      "2028-06-19",
+      "2028-07-04",
+      "2028-09-04",
+      "2028-10-09",
+      "2028-11-10",
+      "2028-11-23",
+      "2028-12-25"
+    ]
+  }
+}
diff --git a/tests/fixtures/cycle/bad/calendar-runs-out.json b/tests/fixtures/cycle/bad/calendar-runs-out.json
new file mode 100644
index 00000000..8432c746
--- /dev/null
+++ b/tests/fixtures/cycle/bad/calendar-runs-out.json
@@ -0,0 +1,54 @@
+{
+  "$comment": "The quarterly Collaborative Continuous Monitoring calendar (CCM-OCR-SOR, CCM-QTR-SAR). Fixed Ongoing Certification Report issue dates, about 3 months apart, placed late in the second month of each quarter (about day 55), away from the beginning, middle and end of the quarter. Each Quarterly Review is a fixed number of business days after its report, counted over the federal holidays listed here. scripts/_ccm.py validates this file (fail-closed) and every report, the CPO and the review calendar file read their dates from it; nothing computes a date from 'now'. Extend the issue dates and holidays before the calendar runs out: the build fails when fewer than two issue dates lie ahead.",
+  "schema": "ccm-calendar/1",
+  "decided_by": "Sam Aydlette",
+  "decided_on": "2026-11-05",
+  "review_by": "2027-11-05",
+  "rationale": "Issue on a Tuesday late in each quarter's middle month: a fixed, predictable cycle that is spread out from the start, middle and end of each quarter, as CCM-OCR-SOR asks. The review follows 5 business days later, inside the 3-to-10 business day window of CCM-QTR-SAR, leaving time to read the report first.",
+  "ocr_issue_dates": [
+    "2026-11-24",
+    "2027-02-23"
+  ],
+  "review_business_days_after_issue": 5,
+  "review_start_utc": "17:00",
+  "review_duration_minutes": 45,
+  "holidays": {
+    "source": "U.S. federal holidays (5 U.S.C. 6103), observed dates",
+    "covers_through": "2028-12-31",
+    "dates": [
+      "2026-01-01",
+      "2026-01-19",
+      "2026-02-16",
+      "2026-05-25",
+      "2026-06-19",
+      "2026-07-03",
+      "2026-09-07",
+      "2026-10-12",
+      "2026-11-11",
+      "2026-11-26",
+      "2026-12-25",
+      "2027-01-01",
+      "2027-01-18",
+      "2027-02-15",
+      "2027-05-31",
+      "2027-06-18",
+      "2027-07-05",
+      "2027-09-06",
+      "2027-10-11",
+      "2027-11-11",
+      "2027-11-25",
+      "2027-12-24",
+      "2027-12-31",
+      "2028-01-17",
+      "2028-02-21",
+      "2028-05-29",
+      "2028-06-19",
+      "2028-07-04",
+      "2028-09-04",
+      "2028-10-09",
+      "2028-11-10",
+      "2028-11-23",
+      "2028-12-25"
+    ]
+  }
+}
diff --git a/tests/fixtures/cycle/bad/cpo-other-package-id.json b/tests/fixtures/cycle/bad/cpo-other-package-id.json
new file mode 100644
index 00000000..910ab6ed
--- /dev/null
+++ b/tests/fixtures/cycle/bad/cpo-other-package-id.json
@@ -0,0 +1,52 @@
+{
+  "$schema": "https://fedramp.gov/schemas/fedramp-certification-package-overview-schema-2026-06-24.json",
+  "serviceIdentification": {
+    "providerName": "Example Provider",
+    "serviceName": "Example Docs",
+    "serviceAcronym": "EXD",
+    "serviceDescription": "A document service.",
+    "certificationType": "20x",
+    "fedRampPackageId": "Someone Else (ELSE)",
+    "website": "https://example.com",
+    "logo": "https://example.com/logo.png"
+  },
+  "serviceProperties": {
+    "serviceType": [
+      "SaaS"
+    ],
+    "deploymentModel": "Public Cloud",
+    "businessCategory": [
+      "Collaboration"
+    ],
+    "trustCenter": {
+      "repositoryType": [
+        "Trust Center"
+      ],
+      "url": "https://example.com/trust",
+      "repositoryDescription": "All certification data.",
+      "authenticationRequired": false
+    },
+    "nextOngoingCertificationReportDate": "2027-02-01"
+  },
+  "contactInformation": [
+    {
+      "contactType": "Security",
+      "contactName": "Sec Team",
+      "contactEmail": "security@example.com"
+    },
+    {
+      "contactType": "Sales",
+      "contactName": "Sales Team"
+    }
+  ],
+  "certifiedServices": [
+    {
+      "serviceName": "File preview",
+      "serviceDescription": "Renders uploads."
+    }
+  ],
+  "providerExtensions": {
+    "fedRampId": "Example Provider (EXD)",
+    "contentSha256": "98b0de339ac1bf2eae4bc307716cd57c3078aaf9cfbc8e23fb3c966323ac3366"
+  }
+}
diff --git a/tests/fixtures/cycle/bad/cpo-rev5-program.json b/tests/fixtures/cycle/bad/cpo-rev5-program.json
new file mode 100644
index 00000000..cb163f0f
--- /dev/null
+++ b/tests/fixtures/cycle/bad/cpo-rev5-program.json
@@ -0,0 +1,76 @@
+{
+  "$schema": "https://fedramp.gov/schemas/fedramp-certification-package-overview-schema-2026-06-24.json",
+  "serviceIdentification": {
+    "providerName": "Example Provider",
+    "serviceName": "Example Docs",
+    "serviceAcronym": "EXD",
+    "serviceDescription": "A document service.",
+    "certificationType": "Rev5",
+    "fedRampPackageId": "Example Provider (EXD)",
+    "website": "https://example.com",
+    "logo": "https://example.com/logo.png"
+  },
+  "serviceProperties": {
+    "serviceType": [
+      "SaaS"
+    ],
+    "deploymentModel": "Public Cloud",
+    "businessCategory": [
+      "Collaboration"
+    ],
+    "trustCenter": {
+      "repositoryType": [
+        "Trust Center"
+      ],
+      "url": "https://example.com/trust",
+      "repositoryDescription": "All certification data.",
+      "authenticationRequired": false
+    },
+    "nextOngoingCertificationReportDate": "2027-02-01",
+    "secureConfigurationGuidance": {
+      "repositoryType": [
+        "Secure Configuration Guidance"
+      ],
+      "url": "https://example.com/scg",
+      "repositoryDescription": "The secure configuration guide.",
+      "authenticationRequired": false
+    }
+  },
+  "contactInformation": [
+    {
+      "contactType": "Security",
+      "contactName": "Sec Team",
+      "contactEmail": "security@example.com"
+    },
+    {
+      "contactType": "Sales",
+      "contactName": "Sales Team"
+    }
+  ],
+  "certifiedServices": [
+    {
+      "serviceName": "File preview",
+      "serviceDescription": "Renders uploads."
+    }
+  ],
+  "thirdPartyInformationResources": {
+    "nonCertified": [
+      {
+        "name": "Example CDN",
+        "provider": "Example Co",
+        "useCase": "Serves static files."
+      }
+    ]
+  },
+  "providerExtensions": {
+    "fedRampId": "Example Provider (EXD)",
+    "contentSha256": "98b0de339ac1bf2eae4bc307716cd57c3078aaf9cfbc8e23fb3c966323ac3366",
+    "independentAssessment": {
+      "overallSummary": {
+        "record_id": "X-SUMMARY",
+        "kind": "summary",
+        "text": "Overall summary (simulated)."
+      }
+    }
+  }
+}
diff --git a/tests/fixtures/cycle/bad/cpo-without-assessment-summary.json b/tests/fixtures/cycle/bad/cpo-without-assessment-summary.json
new file mode 100644
index 00000000..ea97879f
--- /dev/null
+++ b/tests/fixtures/cycle/bad/cpo-without-assessment-summary.json
@@ -0,0 +1,69 @@
+{
+  "$schema": "https://fedramp.gov/schemas/fedramp-certification-package-overview-schema-2026-06-24.json",
+  "serviceIdentification": {
+    "providerName": "Example Provider",
+    "serviceName": "Example Docs",
+    "serviceAcronym": "EXD",
+    "serviceDescription": "A document service.",
+    "certificationType": "20x",
+    "fedRampPackageId": "Example Provider (EXD)",
+    "website": "https://example.com",
+    "logo": "https://example.com/logo.png"
+  },
+  "serviceProperties": {
+    "serviceType": [
+      "SaaS"
+    ],
+    "deploymentModel": "Public Cloud",
+    "businessCategory": [
+      "Collaboration"
+    ],
+    "trustCenter": {
+      "repositoryType": [
+        "Trust Center"
+      ],
+      "url": "https://example.com/trust",
+      "repositoryDescription": "All certification data.",
+      "authenticationRequired": false
+    },
+    "nextOngoingCertificationReportDate": "2027-02-01",
+    "secureConfigurationGuidance": {
+      "repositoryType": [
+        "Secure Configuration Guidance"
+      ],
+      "url": "https://example.com/scg",
+      "repositoryDescription": "The secure configuration guide.",
+      "authenticationRequired": false
+    }
+  },
+  "contactInformation": [
+    {
+      "contactType": "Security",
+      "contactName": "Sec Team",
+      "contactEmail": "security@example.com"
+    },
+    {
+      "contactType": "Sales",
+      "contactName": "Sales Team"
+    }
+  ],
+  "certifiedServices": [
+    {
+      "serviceName": "File preview",
+      "serviceDescription": "Renders uploads."
+    }
+  ],
+  "thirdPartyInformationResources": {
+    "nonCertified": [
+      {
+        "name": "Example CDN",
+        "provider": "Example Co",
+        "useCase": "Serves static files."
+      }
+    ]
+  },
+  "providerExtensions": {
+    "fedRampId": "Example Provider (EXD)",
+    "contentSha256": "98b0de339ac1bf2eae4bc307716cd57c3078aaf9cfbc8e23fb3c966323ac3366"
+  }
+}
diff --git a/tests/fixtures/cycle/bad/cpo-without-not-certified-status.json b/tests/fixtures/cycle/bad/cpo-without-not-certified-status.json
new file mode 100644
index 00000000..c5f10186
--- /dev/null
+++ b/tests/fixtures/cycle/bad/cpo-without-not-certified-status.json
@@ -0,0 +1,80 @@
+{
+  "$schema": "https://fedramp.gov/schemas/fedramp-certification-package-overview-schema-2026-06-24.json",
+  "serviceIdentification": {
+    "providerName": "Example Provider",
+    "serviceName": "Example Docs",
+    "serviceAcronym": "EXD",
+    "serviceDescription": "A document service.",
+    "certificationType": "20x",
+    "fedRampPackageId": "Example Provider (EXD)",
+    "website": "https://example.com",
+    "logo": "https://example.com/logo.png"
+  },
+  "serviceProperties": {
+    "serviceType": [
+      "SaaS"
+    ],
+    "deploymentModel": "Public Cloud",
+    "businessCategory": [
+      "Collaboration"
+    ],
+    "trustCenter": {
+      "repositoryType": [
+        "Trust Center"
+      ],
+      "url": "https://example.com/trust",
+      "repositoryDescription": "All certification data.",
+      "authenticationRequired": false
+    },
+    "nextOngoingCertificationReportDate": "2027-02-01",
+    "secureConfigurationGuidance": {
+      "repositoryType": [
+        "Secure Configuration Guidance"
+      ],
+      "url": "https://example.com/scg",
+      "repositoryDescription": "The secure configuration guide.",
+      "authenticationRequired": false
+    }
+  },
+  "contactInformation": [
+    {
+      "contactType": "Security",
+      "contactName": "Sec Team",
+      "contactEmail": "security@example.com"
+    },
+    {
+      "contactType": "Sales",
+      "contactName": "Sales Team"
+    }
+  ],
+  "certifiedServices": [
+    {
+      "serviceName": "File preview",
+      "serviceDescription": "Renders uploads."
+    }
+  ],
+  "thirdPartyInformationResources": {
+    "nonCertified": [
+      {
+        "name": "Example CDN",
+        "provider": "Example Co",
+        "useCase": "Serves static files."
+      }
+    ]
+  },
+  "providerExtensions": {
+    "fedRampId": "Example Provider (EXD)",
+    "contentSha256": "98b0de339ac1bf2eae4bc307716cd57c3078aaf9cfbc8e23fb3c966323ac3366",
+    "independentAssessment": {
+      "overallSummary": {
+        "record_id": "X-SUMMARY",
+        "kind": "summary",
+        "text": "Overall summary (simulated)."
+      }
+    },
+    "certification": {
+      "program": "FedRAMP 20x, Program path, Class C"
+    }
+  },
+  "$comment": "KNOWN-BAD: the CPO does not state providerExtensions.certification.status 'not certified (proof of concept)'; the package is never submitted."
+}
diff --git a/tests/fixtures/cycle/bad/maintainer-any-branch.json b/tests/fixtures/cycle/bad/maintainer-any-branch.json
new file mode 100644
index 00000000..f7f674c2
--- /dev/null
+++ b/tests/fixtures/cycle/bad/maintainer-any-branch.json
@@ -0,0 +1,14 @@
+{
+  "role_arn": "arn:aws:iam::123456789012:role/github-actions-package-maintenance-oidc",
+  "env_state": "ok",
+  "environment": {
+    "deployment_branch_policy": {
+      "protected_branches": false,
+      "custom_branch_policies": true
+    }
+  },
+  "branch_policies": [
+    "main",
+    "*"
+  ]
+}
diff --git a/tests/fixtures/cycle/bad/maintainer-no-environment.json b/tests/fixtures/cycle/bad/maintainer-no-environment.json
new file mode 100644
index 00000000..1954f347
--- /dev/null
+++ b/tests/fixtures/cycle/bad/maintainer-no-environment.json
@@ -0,0 +1,6 @@
+{
+  "role_arn": "arn:aws:iam::123456789012:role/github-actions-package-maintenance-oidc",
+  "env_state": "missing",
+  "environment": null,
+  "branch_policies": null
+}
diff --git a/tests/fixtures/cycle/bad/maintainer-no-variable.json b/tests/fixtures/cycle/bad/maintainer-no-variable.json
new file mode 100644
index 00000000..ed57b81d
--- /dev/null
+++ b/tests/fixtures/cycle/bad/maintainer-no-variable.json
@@ -0,0 +1,13 @@
+{
+  "role_arn": "",
+  "env_state": "ok",
+  "environment": {
+    "deployment_branch_policy": {
+      "protected_branches": false,
+      "custom_branch_policies": true
+    }
+  },
+  "branch_policies": [
+    "main"
+  ]
+}
diff --git a/tests/fixtures/cycle/bad/maintainer-wrong-role.json b/tests/fixtures/cycle/bad/maintainer-wrong-role.json
new file mode 100644
index 00000000..759f04a7
--- /dev/null
+++ b/tests/fixtures/cycle/bad/maintainer-wrong-role.json
@@ -0,0 +1,13 @@
+{
+  "role_arn": "arn:aws:iam::123456789012:role/github-actions-deploy-oidc",
+  "env_state": "ok",
+  "environment": {
+    "deployment_branch_policy": {
+      "protected_branches": false,
+      "custom_branch_policies": true
+    }
+  },
+  "branch_policies": [
+    "main"
+  ]
+}
diff --git a/tests/fixtures/cycle/bad/ocr-issues-not-a-calendar-date.json b/tests/fixtures/cycle/bad/ocr-issues-not-a-calendar-date.json
new file mode 100644
index 00000000..7c7c5342
--- /dev/null
+++ b/tests/fixtures/cycle/bad/ocr-issues-not-a-calendar-date.json
@@ -0,0 +1,8 @@
+{
+  "schema": "ocr-issues/1",
+  "issues": [
+    {
+      "issueDate": "2026-11-25"
+    }
+  ]
+}
diff --git a/tests/fixtures/cycle/bad/ocr-issues-out-of-order.json b/tests/fixtures/cycle/bad/ocr-issues-out-of-order.json
new file mode 100644
index 00000000..3885cf17
--- /dev/null
+++ b/tests/fixtures/cycle/bad/ocr-issues-out-of-order.json
@@ -0,0 +1,11 @@
+{
+  "schema": "ocr-issues/1",
+  "issues": [
+    {
+      "issueDate": "2027-02-23"
+    },
+    {
+      "issueDate": "2026-11-24"
+    }
+  ]
+}
diff --git a/tests/fixtures/cycle/bad/ocr-other-fedramp-id.json b/tests/fixtures/cycle/bad/ocr-other-fedramp-id.json
new file mode 100644
index 00000000..40f0dc83
--- /dev/null
+++ b/tests/fixtures/cycle/bad/ocr-other-fedramp-id.json
@@ -0,0 +1,24 @@
+{
+  "$schema": "https://fedramp.gov/schemas/fedramp-ongoing-certification-report-schema-2026-06-24.json",
+  "certificationPackageOverviewUri": "https://samaydlette.com/.well-known/certification-package-overview.json",
+  "reportPeriod": {
+    "from": "2026-08-01",
+    "to": "2026-10-31"
+  },
+  "certificationDataChanges": [],
+  "plannedCertificationDataChanges": {
+    "planningHorizonThrough": "2027-01-31",
+    "changes": []
+  },
+  "acceptedVulnerabilities": "None.",
+  "transformativeChanges": [],
+  "updatedRecommendations": [],
+  "activeAgencies": [],
+  "reportableIncidents": {
+    "incidents": []
+  },
+  "providerExtensions": {
+    "fedRampId": "Someone Else (ELSE)",
+    "contentSha256": "1541eb3e8db587c701aef2b148933e3581f89a91b4142ec2e422675e01ed2efd"
+  }
+}
diff --git a/tests/fixtures/cycle/bad/offering-id-without-provider-name.json b/tests/fixtures/cycle/bad/offering-id-without-provider-name.json
new file mode 100644
index 00000000..b5de06e5
--- /dev/null
+++ b/tests/fixtures/cycle/bad/offering-id-without-provider-name.json
@@ -0,0 +1,129 @@
+{
+  "_note": "Operator-declared editorial values for the Certification Package Overview (CPO-CSO-OVR: CDS-CSO-PUB, CDS-CSO-SVC, CDS-CSO-FID). scripts/build-cpo.py reads this plus the system profile, the CCM calendar and the canonical inventory and writes /.well-known/certification-package-overview.json in FedRAMP's schema. Where a value needs an outside party this proof of concept does not have (a FedRAMP ID, a SAM.gov UEI), the value is SIMULATED, says so, and the CPO flags it under providerExtensions.simulated. No published value here is an email address: contacts point to /.well-known/security.txt or the contact page.",
+  "provider_name": "Sam Aydlette",
+  "service_name": "samaydlette.com",
+  "service_acronym": "SAMCOM",
+  "fedramp_id": "NOT-A-REAL-FEDRAMP-ID",
+  "fedramp_id_simulated": "No FedRAMP ID exists or is coming: nothing has been submitted to FedRAMP. FedRAMP's schema says to use the provider's name and acronym until an ID is assigned; the suffix makes sure nobody mistakes it for one.",
+  "uei": "NOT-A-REAL-UEI-0000",
+  "uei_simulated": "Simulated. The operator is not registering on SAM.gov, so there is no Unique Entity Identifier; this value is a placeholder that no SAM.gov lookup will ever find.",
+  "service_model": [
+    "SaaS"
+  ],
+  "deployment_model": "Public Cloud",
+  "business_category": [
+    "Governance, Risk, and Compliance (GRC)",
+    "Cybersecurity & Risk Management",
+    "Health & Wellness"
+  ],
+  "sales_contact": {
+    "name": "Sam Aydlette. Nothing here is for sale; say hello through the contact page: https://samaydlette.com/pages/contact.html"
+  },
+  "security_contact": {
+    "name": "Sam Aydlette, through the security contact in https://samaydlette.com/.well-known/security.txt"
+  },
+  "product_website": "https://samaydlette.com",
+  "logo_url": "https://samaydlette.com/assets/images/brand/logo.png",
+  "service_description": "A static personal website on AWS that doubles as a working continuous-compliance pipeline: every deploy derives signed, machine-readable compliance artifacts from one canonical inventory and publishes them under /.well-known/. Includes the Silk Reeling Mirror application, a Cognito-gated Tai Chi coaching API.",
+  "secure_configuration_guidance_url": "https://github.com/sam-aydlette/samaydlette.com/blob/main/docs/policies/secure-configuration-guide.md",
+  "documentation_overview_url": "https://samaydlette.com/trust/index.html",
+  "current_independent_assessment_service": "None \u2014 self-attested; no FedRAMP-Recognized independent assessment service engaged (IVV is N/A for this unsponsored proof of concept).",
+  "accountable_official": {
+    "name": "Sam Aydlette",
+    "title": "System Owner / Authorizing Operator",
+    "contact": "https://samaydlette.com/.well-known/security.txt"
+  },
+  "cryptographic_modules": [
+    {
+      "module": "AWS KMS",
+      "validation": "FIPS 140-3 (CMVP, HSM-backed)",
+      "role": "key store for all four customer-managed CMKs: at-rest (the compliance and watchdog Lambdas' environments and log groups, the DNS query log, the alert topic), runtime signing (the runtime signal), DNSSEC KSK, and the Silk Reeling app (its Lambda environment and log groups; the app holds no secrets since SCN-2026-006)",
+      "inherited": true
+    },
+    {
+      "module": "ACM TLS termination on CloudFront",
+      "validation": "FIPS-validated cipher suites; TLS 1.2+",
+      "role": "TLS in transit",
+      "inherited": true
+    },
+    {
+      "module": "S3 SSE-S3",
+      "validation": "AES-256 (AWS-managed keys)",
+      "role": "at-rest on the public website + log buckets",
+      "inherited": true
+    },
+    {
+      "module": "Sigstore Fulcio + Rekor",
+      "validation": "ECDSA P-256 (FIPS-approved algorithm); the implementations are NOT CMVP-validated modules",
+      "role": "deploy-time keyless signing",
+      "inherited": false,
+      "compensating_control": "trust anchored in the public Rekor transparency log"
+    }
+  ],
+  "services": [
+    {
+      "name": "samaydlette.com static website",
+      "description": "Public static content (S3 origin behind CloudFront), plus the signed compliance artifacts published under /.well-known/ and the trust center at /trust/.",
+      "boundary_groups": [
+        "website"
+      ],
+      "security_category": {
+        "confidentiality": "low",
+        "integrity": "moderate",
+        "availability": "low",
+        "rationale": "Public content: nothing confidential. Integrity is moderate because defacement or tampering of published evidence would mislead readers. Availability is low: a personal site."
+      },
+      "in_mas_scope": true
+    },
+    {
+      "name": "Silk Reeling Mirror application",
+      "description": "Cognito-gated HTTP API (API Gateway -> Lambda) serving a browser SPA that coaches Tai Chi; writes feedback text from the scores in the Lambda, with no external interconnection (optional LLM feedback is customer-configurable and disabled here).",
+      "date_available": "2026-06-03",
+      "boundary_groups": [
+        "app"
+      ],
+      "security_category": {
+        "confidentiality": "low",
+        "integrity": "moderate",
+        "availability": "low",
+        "rationale": "Holds invited users' sign-in accounts and the pose scores they submit, no federal data: confidentiality low. Integrity moderate: wrong coaching or tampered accounts are the harm. Availability low."
+      },
+      "in_mas_scope": true
+    },
+    {
+      "name": "Continuous compliance evidence (pipeline trust root, runtime KSI emitter, evidence watchdog)",
+      "description": "The deploy's trust root (OIDC roles, CloudFront, DNSSEC, remote state), the daily runtime re-validation of live configuration (signed runtime KSI signal), the hourly evidence-freshness watchdog with its alarms, and the audit trail and keys behind them. GitHub Actions and Sigstore, which build and sign the evidence, are third-party information resources inside the boundary.",
+      "boundary_groups": [
+        "compliance",
+        "watchdog",
+        "audit",
+        "trust-root"
+      ],
+      "security_category": {
+        "confidentiality": "low",
+        "integrity": "moderate",
+        "availability": "low",
+        "rationale": "The evidence is public by design. Integrity is moderate: false evidence is the harm this system exists to prevent. Availability is low."
+      },
+      "in_mas_scope": true
+    }
+  ],
+  "not_included": [
+    {
+      "name": "Podcast and video audio hosted by third parties",
+      "why": "Linked from pages, served by their own hosts; not part of the offering."
+    },
+    {
+      "name": "MediaPipe libraries and models (cdn.jsdelivr.net, storage.googleapis.com)",
+      "why": "Loaded by the visitor's browser from third-party hosts at run time; listed as third-party information resources, not services of this offering."
+    },
+    {
+      "name": "Optional LLM coaching feedback",
+      "why": "Customer-configurable and disabled; no external AI service is called."
+    },
+    {
+      "name": "Newsletter, RSS and social feeds",
+      "why": "None is offered under this certification."
+    }
+  ]
+}
diff --git a/tests/fixtures/cycle/bad/offering-placeholder-id-unflagged.json b/tests/fixtures/cycle/bad/offering-placeholder-id-unflagged.json
new file mode 100644
index 00000000..5d3ecb03
--- /dev/null
+++ b/tests/fixtures/cycle/bad/offering-placeholder-id-unflagged.json
@@ -0,0 +1,128 @@
+{
+  "_note": "Operator-declared editorial values for the Certification Package Overview (CPO-CSO-OVR: CDS-CSO-PUB, CDS-CSO-SVC, CDS-CSO-FID). scripts/build-cpo.py reads this plus the system profile, the CCM calendar and the canonical inventory and writes /.well-known/certification-package-overview.json in FedRAMP's schema. Where a value needs an outside party this proof of concept does not have (a FedRAMP ID, a SAM.gov UEI), the value is SIMULATED, says so, and the CPO flags it under providerExtensions.simulated. No published value here is an email address: contacts point to /.well-known/security.txt or the contact page.",
+  "provider_name": "Sam Aydlette",
+  "service_name": "samaydlette.com",
+  "service_acronym": "SAMCOM",
+  "fedramp_id": "Sam Aydlette (SAMCOM): PROOF-OF-CONCEPT-NOT-A-REAL-FEDRAMP-ID",
+  "uei": "NOT-A-REAL-UEI-0000",
+  "uei_simulated": "Simulated. The operator is not registering on SAM.gov, so there is no Unique Entity Identifier; this value is a placeholder that no SAM.gov lookup will ever find.",
+  "service_model": [
+    "SaaS"
+  ],
+  "deployment_model": "Public Cloud",
+  "business_category": [
+    "Governance, Risk, and Compliance (GRC)",
+    "Cybersecurity & Risk Management",
+    "Health & Wellness"
+  ],
+  "sales_contact": {
+    "name": "Sam Aydlette. Nothing here is for sale; say hello through the contact page: https://samaydlette.com/pages/contact.html"
+  },
+  "security_contact": {
+    "name": "Sam Aydlette, through the security contact in https://samaydlette.com/.well-known/security.txt"
+  },
+  "product_website": "https://samaydlette.com",
+  "logo_url": "https://samaydlette.com/assets/images/brand/logo.png",
+  "service_description": "A static personal website on AWS that doubles as a working continuous-compliance pipeline: every deploy derives signed, machine-readable compliance artifacts from one canonical inventory and publishes them under /.well-known/. Includes the Silk Reeling Mirror application, a Cognito-gated Tai Chi coaching API.",
+  "secure_configuration_guidance_url": "https://github.com/sam-aydlette/samaydlette.com/blob/main/docs/policies/secure-configuration-guide.md",
+  "documentation_overview_url": "https://samaydlette.com/trust/index.html",
+  "current_independent_assessment_service": "None \u2014 self-attested; no FedRAMP-Recognized independent assessment service engaged (IVV is N/A for this unsponsored proof of concept).",
+  "accountable_official": {
+    "name": "Sam Aydlette",
+    "title": "System Owner / Authorizing Operator",
+    "contact": "https://samaydlette.com/.well-known/security.txt"
+  },
+  "cryptographic_modules": [
+    {
+      "module": "AWS KMS",
+      "validation": "FIPS 140-3 (CMVP, HSM-backed)",
+      "role": "key store for all four customer-managed CMKs: at-rest (the compliance and watchdog Lambdas' environments and log groups, the DNS query log, the alert topic), runtime signing (the runtime signal), DNSSEC KSK, and the Silk Reeling app (its Lambda environment and log groups; the app holds no secrets since SCN-2026-006)",
+      "inherited": true
+    },
+    {
+      "module": "ACM TLS termination on CloudFront",
+      "validation": "FIPS-validated cipher suites; TLS 1.2+",
+      "role": "TLS in transit",
+      "inherited": true
+    },
+    {
+      "module": "S3 SSE-S3",
+      "validation": "AES-256 (AWS-managed keys)",
+      "role": "at-rest on the public website + log buckets",
+      "inherited": true
+    },
+    {
+      "module": "Sigstore Fulcio + Rekor",
+      "validation": "ECDSA P-256 (FIPS-approved algorithm); the implementations are NOT CMVP-validated modules",
+      "role": "deploy-time keyless signing",
+      "inherited": false,
+      "compensating_control": "trust anchored in the public Rekor transparency log"
+    }
+  ],
+  "services": [
+    {
+      "name": "samaydlette.com static website",
+      "description": "Public static content (S3 origin behind CloudFront), plus the signed compliance artifacts published under /.well-known/ and the trust center at /trust/.",
+      "boundary_groups": [
+        "website"
+      ],
+      "security_category": {
+        "confidentiality": "low",
+        "integrity": "moderate",
+        "availability": "low",
+        "rationale": "Public content: nothing confidential. Integrity is moderate because defacement or tampering of published evidence would mislead readers. Availability is low: a personal site."
+      },
+      "in_mas_scope": true
+    },
+    {
+      "name": "Silk Reeling Mirror application",
+      "description": "Cognito-gated HTTP API (API Gateway -> Lambda) serving a browser SPA that coaches Tai Chi; writes feedback text from the scores in the Lambda, with no external interconnection (optional LLM feedback is customer-configurable and disabled here).",
+      "date_available": "2026-06-03",
+      "boundary_groups": [
+        "app"
+      ],
+      "security_category": {
+        "confidentiality": "low",
+        "integrity": "moderate",
+        "availability": "low",
+        "rationale": "Holds invited users' sign-in accounts and the pose scores they submit, no federal data: confidentiality low. Integrity moderate: wrong coaching or tampered accounts are the harm. Availability low."
+      },
+      "in_mas_scope": true
+    },
+    {
+      "name": "Continuous compliance evidence (pipeline trust root, runtime KSI emitter, evidence watchdog)",
+      "description": "The deploy's trust root (OIDC roles, CloudFront, DNSSEC, remote state), the daily runtime re-validation of live configuration (signed runtime KSI signal), the hourly evidence-freshness watchdog with its alarms, and the audit trail and keys behind them. GitHub Actions and Sigstore, which build and sign the evidence, are third-party information resources inside the boundary.",
+      "boundary_groups": [
+        "compliance",
+        "watchdog",
+        "audit",
+        "trust-root"
+      ],
+      "security_category": {
+        "confidentiality": "low",
+        "integrity": "moderate",
+        "availability": "low",
+        "rationale": "The evidence is public by design. Integrity is moderate: false evidence is the harm this system exists to prevent. Availability is low."
+      },
+      "in_mas_scope": true
+    }
+  ],
+  "not_included": [
+    {
+      "name": "Podcast and video audio hosted by third parties",
+      "why": "Linked from pages, served by their own hosts; not part of the offering."
+    },
+    {
+      "name": "MediaPipe libraries and models (cdn.jsdelivr.net, storage.googleapis.com)",
+      "why": "Loaded by the visitor's browser from third-party hosts at run time; listed as third-party information resources, not services of this offering."
+    },
+    {
+      "name": "Optional LLM coaching feedback",
+      "why": "Customer-configurable and disabled; no external AI service is called."
+    },
+    {
+      "name": "Newsletter, RSS and social feeds",
+      "why": "None is offered under this certification."
+    }
+  ]
+}
diff --git a/tests/fixtures/cycle/bad/offering-service-above-system.json b/tests/fixtures/cycle/bad/offering-service-above-system.json
new file mode 100644
index 00000000..0b2b439a
--- /dev/null
+++ b/tests/fixtures/cycle/bad/offering-service-above-system.json
@@ -0,0 +1,129 @@
+{
+  "_note": "Operator-declared editorial values for the Certification Package Overview (CPO-CSO-OVR: CDS-CSO-PUB, CDS-CSO-SVC, CDS-CSO-FID). scripts/build-cpo.py reads this plus the system profile, the CCM calendar and the canonical inventory and writes /.well-known/certification-package-overview.json in FedRAMP's schema. Where a value needs an outside party this proof of concept does not have (a FedRAMP ID, a SAM.gov UEI), the value is SIMULATED, says so, and the CPO flags it under providerExtensions.simulated. No published value here is an email address: contacts point to /.well-known/security.txt or the contact page.",
+  "provider_name": "Sam Aydlette",
+  "service_name": "samaydlette.com",
+  "service_acronym": "SAMCOM",
+  "fedramp_id": "Sam Aydlette (SAMCOM): PROOF-OF-CONCEPT-NOT-A-REAL-FEDRAMP-ID",
+  "fedramp_id_simulated": "No FedRAMP ID exists or is coming: nothing has been submitted to FedRAMP. FedRAMP's schema says to use the provider's name and acronym until an ID is assigned; the suffix makes sure nobody mistakes it for one.",
+  "uei": "NOT-A-REAL-UEI-0000",
+  "uei_simulated": "Simulated. The operator is not registering on SAM.gov, so there is no Unique Entity Identifier; this value is a placeholder that no SAM.gov lookup will ever find.",
+  "service_model": [
+    "SaaS"
+  ],
+  "deployment_model": "Public Cloud",
+  "business_category": [
+    "Governance, Risk, and Compliance (GRC)",
+    "Cybersecurity & Risk Management",
+    "Health & Wellness"
+  ],
+  "sales_contact": {
+    "name": "Sam Aydlette. Nothing here is for sale; say hello through the contact page: https://samaydlette.com/pages/contact.html"
+  },
+  "security_contact": {
+    "name": "Sam Aydlette, through the security contact in https://samaydlette.com/.well-known/security.txt"
+  },
+  "product_website": "https://samaydlette.com",
+  "logo_url": "https://samaydlette.com/assets/images/brand/logo.png",
+  "service_description": "A static personal website on AWS that doubles as a working continuous-compliance pipeline: every deploy derives signed, machine-readable compliance artifacts from one canonical inventory and publishes them under /.well-known/. Includes the Silk Reeling Mirror application, a Cognito-gated Tai Chi coaching API.",
+  "secure_configuration_guidance_url": "https://github.com/sam-aydlette/samaydlette.com/blob/main/docs/policies/secure-configuration-guide.md",
+  "documentation_overview_url": "https://samaydlette.com/trust/index.html",
+  "current_independent_assessment_service": "None \u2014 self-attested; no FedRAMP-Recognized independent assessment service engaged (IVV is N/A for this unsponsored proof of concept).",
+  "accountable_official": {
+    "name": "Sam Aydlette",
+    "title": "System Owner / Authorizing Operator",
+    "contact": "https://samaydlette.com/.well-known/security.txt"
+  },
+  "cryptographic_modules": [
+    {
+      "module": "AWS KMS",
+      "validation": "FIPS 140-3 (CMVP, HSM-backed)",
+      "role": "key store for all four customer-managed CMKs: at-rest (the compliance and watchdog Lambdas' environments and log groups, the DNS query log, the alert topic), runtime signing (the runtime signal), DNSSEC KSK, and the Silk Reeling app (its Lambda environment and log groups; the app holds no secrets since SCN-2026-006)",
+      "inherited": true
+    },
+    {
+      "module": "ACM TLS termination on CloudFront",
+      "validation": "FIPS-validated cipher suites; TLS 1.2+",
+      "role": "TLS in transit",
+      "inherited": true
+    },
+    {
+      "module": "S3 SSE-S3",
+      "validation": "AES-256 (AWS-managed keys)",
+      "role": "at-rest on the public website + log buckets",
+      "inherited": true
+    },
+    {
+      "module": "Sigstore Fulcio + Rekor",
+      "validation": "ECDSA P-256 (FIPS-approved algorithm); the implementations are NOT CMVP-validated modules",
+      "role": "deploy-time keyless signing",
+      "inherited": false,
+      "compensating_control": "trust anchored in the public Rekor transparency log"
+    }
+  ],
+  "services": [
+    {
+      "name": "samaydlette.com static website",
+      "description": "Public static content (S3 origin behind CloudFront), plus the signed compliance artifacts published under /.well-known/ and the trust center at /trust/.",
+      "boundary_groups": [
+        "website"
+      ],
+      "security_category": {
+        "confidentiality": "low",
+        "integrity": "high",
+        "availability": "low",
+        "rationale": "Public content: nothing confidential. Integrity is moderate because defacement or tampering of published evidence would mislead readers. Availability is low: a personal site."
+      },
+      "in_mas_scope": true
+    },
+    {
+      "name": "Silk Reeling Mirror application",
+      "description": "Cognito-gated HTTP API (API Gateway -> Lambda) serving a browser SPA that coaches Tai Chi; writes feedback text from the scores in the Lambda, with no external interconnection (optional LLM feedback is customer-configurable and disabled here).",
+      "date_available": "2026-06-03",
+      "boundary_groups": [
+        "app"
+      ],
+      "security_category": {
+        "confidentiality": "low",
+        "integrity": "moderate",
+        "availability": "low",
+        "rationale": "Holds invited users' sign-in accounts and the pose scores they submit, no federal data: confidentiality low. Integrity moderate: wrong coaching or tampered accounts are the harm. Availability low."
+      },
+      "in_mas_scope": true
+    },
+    {
+      "name": "Continuous compliance evidence (pipeline trust root, runtime KSI emitter, evidence watchdog)",
+      "description": "The deploy's trust root (OIDC roles, CloudFront, DNSSEC, remote state), the daily runtime re-validation of live configuration (signed runtime KSI signal), the hourly evidence-freshness watchdog with its alarms, and the audit trail and keys behind them. GitHub Actions and Sigstore, which build and sign the evidence, are third-party information resources inside the boundary.",
+      "boundary_groups": [
+        "compliance",
+        "watchdog",
+        "audit",
+        "trust-root"
+      ],
+      "security_category": {
+        "confidentiality": "low",
+        "integrity": "moderate",
+        "availability": "low",
+        "rationale": "The evidence is public by design. Integrity is moderate: false evidence is the harm this system exists to prevent. Availability is low."
+      },
+      "in_mas_scope": true
+    }
+  ],
+  "not_included": [
+    {
+      "name": "Podcast and video audio hosted by third parties",
+      "why": "Linked from pages, served by their own hosts; not part of the offering."
+    },
+    {
+      "name": "MediaPipe libraries and models (cdn.jsdelivr.net, storage.googleapis.com)",
+      "why": "Loaded by the visitor's browser from third-party hosts at run time; listed as third-party information resources, not services of this offering."
+    },
+    {
+      "name": "Optional LLM coaching feedback",
+      "why": "Customer-configurable and disabled; no external AI service is called."
+    },
+    {
+      "name": "Newsletter, RSS and social feeds",
+      "why": "None is offered under this certification."
+    }
+  ]
+}
diff --git a/tests/fixtures/cycle/bad/offering-unknown-boundary-group.json b/tests/fixtures/cycle/bad/offering-unknown-boundary-group.json
new file mode 100644
index 00000000..8ca2190d
--- /dev/null
+++ b/tests/fixtures/cycle/bad/offering-unknown-boundary-group.json
@@ -0,0 +1,130 @@
+{
+  "_note": "Operator-declared editorial values for the Certification Package Overview (CPO-CSO-OVR: CDS-CSO-PUB, CDS-CSO-SVC, CDS-CSO-FID). scripts/build-cpo.py reads this plus the system profile, the CCM calendar and the canonical inventory and writes /.well-known/certification-package-overview.json in FedRAMP's schema. Where a value needs an outside party this proof of concept does not have (a FedRAMP ID, a SAM.gov UEI), the value is SIMULATED, says so, and the CPO flags it under providerExtensions.simulated. No published value here is an email address: contacts point to /.well-known/security.txt or the contact page.",
+  "provider_name": "Sam Aydlette",
+  "service_name": "samaydlette.com",
+  "service_acronym": "SAMCOM",
+  "fedramp_id": "Sam Aydlette (SAMCOM): PROOF-OF-CONCEPT-NOT-A-REAL-FEDRAMP-ID",
+  "fedramp_id_simulated": "No FedRAMP ID exists or is coming: nothing has been submitted to FedRAMP. FedRAMP's schema says to use the provider's name and acronym until an ID is assigned; the suffix makes sure nobody mistakes it for one.",
+  "uei": "NOT-A-REAL-UEI-0000",
+  "uei_simulated": "Simulated. The operator is not registering on SAM.gov, so there is no Unique Entity Identifier; this value is a placeholder that no SAM.gov lookup will ever find.",
+  "service_model": [
+    "SaaS"
+  ],
+  "deployment_model": "Public Cloud",
+  "business_category": [
+    "Governance, Risk, and Compliance (GRC)",
+    "Cybersecurity & Risk Management",
+    "Health & Wellness"
+  ],
+  "sales_contact": {
+    "name": "Sam Aydlette. Nothing here is for sale; say hello through the contact page: https://samaydlette.com/pages/contact.html"
+  },
+  "security_contact": {
+    "name": "Sam Aydlette, through the security contact in https://samaydlette.com/.well-known/security.txt"
+  },
+  "product_website": "https://samaydlette.com",
+  "logo_url": "https://samaydlette.com/assets/images/brand/logo.png",
+  "service_description": "A static personal website on AWS that doubles as a working continuous-compliance pipeline: every deploy derives signed, machine-readable compliance artifacts from one canonical inventory and publishes them under /.well-known/. Includes the Silk Reeling Mirror application, a Cognito-gated Tai Chi coaching API.",
+  "secure_configuration_guidance_url": "https://github.com/sam-aydlette/samaydlette.com/blob/main/docs/policies/secure-configuration-guide.md",
+  "documentation_overview_url": "https://samaydlette.com/trust/index.html",
+  "current_independent_assessment_service": "None \u2014 self-attested; no FedRAMP-Recognized independent assessment service engaged (IVV is N/A for this unsponsored proof of concept).",
+  "accountable_official": {
+    "name": "Sam Aydlette",
+    "title": "System Owner / Authorizing Operator",
+    "contact": "https://samaydlette.com/.well-known/security.txt"
+  },
+  "cryptographic_modules": [
+    {
+      "module": "AWS KMS",
+      "validation": "FIPS 140-3 (CMVP, HSM-backed)",
+      "role": "key store for all four customer-managed CMKs: at-rest (the compliance and watchdog Lambdas' environments and log groups, the DNS query log, the alert topic), runtime signing (the runtime signal), DNSSEC KSK, and the Silk Reeling app (its Lambda environment and log groups; the app holds no secrets since SCN-2026-006)",
+      "inherited": true
+    },
+    {
+      "module": "ACM TLS termination on CloudFront",
+      "validation": "FIPS-validated cipher suites; TLS 1.2+",
+      "role": "TLS in transit",
+      "inherited": true
+    },
+    {
+      "module": "S3 SSE-S3",
+      "validation": "AES-256 (AWS-managed keys)",
+      "role": "at-rest on the public website + log buckets",
+      "inherited": true
+    },
+    {
+      "module": "Sigstore Fulcio + Rekor",
+      "validation": "ECDSA P-256 (FIPS-approved algorithm); the implementations are NOT CMVP-validated modules",
+      "role": "deploy-time keyless signing",
+      "inherited": false,
+      "compensating_control": "trust anchored in the public Rekor transparency log"
+    }
+  ],
+  "services": [
+    {
+      "name": "samaydlette.com static website",
+      "description": "Public static content (S3 origin behind CloudFront), plus the signed compliance artifacts published under /.well-known/ and the trust center at /trust/.",
+      "boundary_groups": [
+        "website",
+        "not-a-boundary-group"
+      ],
+      "security_category": {
+        "confidentiality": "low",
+        "integrity": "moderate",
+        "availability": "low",
+        "rationale": "Public content: nothing confidential. Integrity is moderate because defacement or tampering of published evidence would mislead readers. Availability is low: a personal site."
+      },
+      "in_mas_scope": true
+    },
+    {
+      "name": "Silk Reeling Mirror application",
+      "description": "Cognito-gated HTTP API (API Gateway -> Lambda) serving a browser SPA that coaches Tai Chi; writes feedback text from the scores in the Lambda, with no external interconnection (optional LLM feedback is customer-configurable and disabled here).",
+      "date_available": "2026-06-03",
+      "boundary_groups": [
+        "app"
+      ],
+      "security_category": {
+        "confidentiality": "low",
+        "integrity": "moderate",
+        "availability": "low",
+        "rationale": "Holds invited users' sign-in accounts and the pose scores they submit, no federal data: confidentiality low. Integrity moderate: wrong coaching or tampered accounts are the harm. Availability low."
+      },
+      "in_mas_scope": true
+    },
+    {
+      "name": "Continuous compliance evidence (pipeline trust root, runtime KSI emitter, evidence watchdog)",
+      "description": "The deploy's trust root (OIDC roles, CloudFront, DNSSEC, remote state), the daily runtime re-validation of live configuration (signed runtime KSI signal), the hourly evidence-freshness watchdog with its alarms, and the audit trail and keys behind them. GitHub Actions and Sigstore, which build and sign the evidence, are third-party information resources inside the boundary.",
+      "boundary_groups": [
+        "compliance",
+        "watchdog",
+        "audit",
+        "trust-root"
+      ],
+      "security_category": {
+        "confidentiality": "low",
+        "integrity": "moderate",
+        "availability": "low",
+        "rationale": "The evidence is public by design. Integrity is moderate: false evidence is the harm this system exists to prevent. Availability is low."
+      },
+      "in_mas_scope": true
+    }
+  ],
+  "not_included": [
+    {
+      "name": "Podcast and video audio hosted by third parties",
+      "why": "Linked from pages, served by their own hosts; not part of the offering."
+    },
+    {
+      "name": "MediaPipe libraries and models (cdn.jsdelivr.net, storage.googleapis.com)",
+      "why": "Loaded by the visitor's browser from third-party hosts at run time; listed as third-party information resources, not services of this offering."
+    },
+    {
+      "name": "Optional LLM coaching feedback",
+      "why": "Customer-configurable and disabled; no external AI service is called."
+    },
+    {
+      "name": "Newsletter, RSS and social feeds",
+      "why": "None is offered under this certification."
+    }
+  ]
+}
diff --git a/tests/fixtures/cycle/bad/sdr-repeats-a-rule.json b/tests/fixtures/cycle/bad/sdr-repeats-a-rule.json
new file mode 100644
index 00000000..50f9d92c
--- /dev/null
+++ b/tests/fixtures/cycle/bad/sdr-repeats-a-rule.json
@@ -0,0 +1,64 @@
+{
+  "$schema": "https://fedramp.gov/schemas/fedramp-security-decision-record-schema-2026-06-24.json",
+  "certificationPackageOverviewUri": "https://samaydlette.com/.well-known/certification-package-overview.json",
+  "metadata": {
+    "version": "1",
+    "lastUpdated": "2026-11-05T00:00:00Z",
+    "updateSource": "pipeline"
+  },
+  "fedRampRequirements": [
+    {
+      "frrID": "VDR-CSO-DET",
+      "frrImplementationStatus": "Implemented",
+      "frrImplementation": [
+        "Scanners run on every deploy."
+      ]
+    },
+    {
+      "frrID": "VDR-CSO-DET",
+      "frrImplementationStatus": "Implemented",
+      "frrImplementation": [
+        "Scanners run on every deploy."
+      ]
+    }
+  ],
+  "keySecurityIndicators": [
+    {
+      "ksiId": "KSI-CNA-01",
+      "ksiImplementation": [
+        "x"
+      ],
+      "ksiValidation": [
+        "y"
+      ],
+      "ksiAssessment": [
+        "z"
+      ],
+      "ksiTests": [
+        "t"
+      ],
+      "ksiEvidence": [
+        {
+          "evidenceType": "Report",
+          "evidenceLocation": "https://example.com/e.json"
+        }
+      ]
+    }
+  ],
+  "securityControls": [
+    {
+      "controlId": "AC-2",
+      "controlImplementationStatus": "Implemented",
+      "parameterValues": [
+        {
+          "parameterId": "ac-02_odp.01",
+          "parameterValue": "30 days"
+        }
+      ]
+    }
+  ],
+  "providerExtensions": {
+    "fedRampId": "Example Provider (EXD)",
+    "contentSha256": "6ada229987020103f85b4b3a991a34aed52ed919d01a6c3f0ac1fd40c2093e6e"
+  }
+}
diff --git a/tests/fixtures/cycle/bad/sdr-without-not-certified-status.json b/tests/fixtures/cycle/bad/sdr-without-not-certified-status.json
new file mode 100644
index 00000000..7d3c2680
--- /dev/null
+++ b/tests/fixtures/cycle/bad/sdr-without-not-certified-status.json
@@ -0,0 +1,59 @@
+{
+  "$comment": "KNOWN-BAD: the SDR names the program but not its status 'not certified (proof of concept)'; the package is never submitted.",
+  "$schema": "https://fedramp.gov/schemas/fedramp-security-decision-record-schema-2026-06-24.json",
+  "certificationPackageOverviewUri": "https://samaydlette.com/.well-known/certification-package-overview.json",
+  "metadata": {
+    "version": "1",
+    "lastUpdated": "2026-11-05T00:00:00Z",
+    "updateSource": "pipeline"
+  },
+  "fedRampRequirements": [
+    {
+      "frrID": "VDR-CSO-DET",
+      "frrImplementationStatus": "Implemented",
+      "frrImplementation": [
+        "Scanners run on every deploy."
+      ]
+    }
+  ],
+  "keySecurityIndicators": [
+    {
+      "ksiId": "KSI-CNA-01",
+      "ksiImplementation": [
+        "x"
+      ],
+      "ksiValidation": [
+        "y"
+      ],
+      "ksiAssessment": [
+        "z"
+      ],
+      "ksiTests": [
+        "t"
+      ],
+      "ksiEvidence": [
+        {
+          "evidenceType": "Report",
+          "evidenceLocation": "https://example.com/e.json"
+        }
+      ]
+    }
+  ],
+  "securityControls": [
+    {
+      "controlId": "AC-2",
+      "controlImplementationStatus": "Implemented",
+      "parameterValues": [
+        {
+          "parameterId": "ac-02_odp.01",
+          "parameterValue": "30 days"
+        }
+      ]
+    }
+  ],
+  "providerExtensions": {
+    "fedRampId": "Example Provider (EXD)",
+    "contentSha256": "6ada229987020103f85b4b3a991a34aed52ed919d01a6c3f0ac1fd40c2093e6e",
+    "certification": "FedRAMP 20x, Program path, Class C"
+  }
+}
diff --git a/tests/fixtures/cycle/bad/sensitive-values.json b/tests/fixtures/cycle/bad/sensitive-values.json
new file mode 100644
index 00000000..51f96b26
--- /dev/null
+++ b/tests/fixtures/cycle/bad/sensitive-values.json
@@ -0,0 +1,17 @@
+{
+  "account-id": {
+    "summary": "Applied to account 123456789012 in us-east-1."
+  },
+  "email": {
+    "summary": "Asked by jane.doe@example.org about the review."
+  },
+  "ipv4": {
+    "summary": "Origin 10.20.30.40 was blocked."
+  },
+  "aws-key": {
+    "summary": "Rotated AKIAIOSFODNN7EXAMPLE after the drill."
+  },
+  "handle": {
+    "summary": "Question from @some-reviewer answered."
+  }
+}
diff --git a/tests/fixtures/cycle/bad/site-file-without-fedramp-id.json b/tests/fixtures/cycle/bad/site-file-without-fedramp-id.json
new file mode 100644
index 00000000..51355440
--- /dev/null
+++ b/tests/fixtures/cycle/bad/site-file-without-fedramp-id.json
@@ -0,0 +1,5 @@
+{
+  "$comment": "Known bad: a trust-center site file named to the FedRAMP ID gate with no top-level fedRampId.",
+  "manifest_type": "fedramp-certification-data-manifest",
+  "artifacts": []
+}
diff --git a/tests/fixtures/cycle/bad/submission-log-late-report.json b/tests/fixtures/cycle/bad/submission-log-late-report.json
new file mode 100644
index 00000000..05a8cb08
--- /dev/null
+++ b/tests/fixtures/cycle/bad/submission-log-late-report.json
@@ -0,0 +1,81 @@
+{
+  "$comment": "KNOWN-BAD: the simulated FedRAMP's report was received 2026-10-01 and has never been published; publishing it on 2026-11-05 is past the 2-week window, so the deploy fails (CDS-CSO-FRC).",
+  "schema": "package-submission-log/1",
+  "generated_at": "2026-10-01T12:00:00+00:00",
+  "fedRampId": "Example Provider (EXD)",
+  "certificationPackageOverviewUri": "https://samaydlette.com/.well-known/certification-package-overview.json",
+  "nothingSent": true,
+  "simulated": {
+    "counterparty": "fedramp",
+    "how": "FedRAMP is simulated. The package goes to simulated_fedramp_intake() in scripts/submit-package.py, a function that never touches the network, and the only trace is this signed log. Nothing has been submitted to the real FedRAMP, and nothing will be."
+  },
+  "entries": [
+    {
+      "submittedAt": "2026-10-01T12:00:00+00:00",
+      "manifest": {
+        "components": [
+          {
+            "component": "CPO",
+            "rule": "CPO-CSO-OVR",
+            "url": "https://samaydlette.com/.well-known/certification-package-overview.json",
+            "sha256": "bdc9dcb20f748409072216beaa4fd621ff2303a34400dea920865b5feadd5252",
+            "contentSha256": "98b0de339ac1bf2eae4bc307716cd57c3078aaf9cfbc8e23fb3c966323ac3366",
+            "version": null
+          },
+          {
+            "component": "SDR",
+            "rule": "SDR-CSO-FRR",
+            "url": "https://samaydlette.com/.well-known/security-decision-record.json",
+            "sha256": "34f510919de0e3b74a338cf7c0502d062e95efc17b75f7341e9723580a90111a",
+            "contentSha256": "6ada229987020103f85b4b3a991a34aed52ed919d01a6c3f0ac1fd40c2093e6e",
+            "version": "1"
+          },
+          {
+            "component": "OCR",
+            "rule": "CCM-OCR-AVL",
+            "url": "https://samaydlette.com/.well-known/ongoing-certification-report.json",
+            "sha256": "d4a13fbd228c74a1ad6bcd307d07df358519dbbe020954a22ddbf233e9add736",
+            "contentSha256": "1541eb3e8db587c701aef2b148933e3581f89a91b4142ec2e422675e01ed2efd",
+            "version": null
+          }
+        ],
+        "packageSha256": "36f34d30f61ce96592b46ade8b0207be24b203aafea6ec54cb86072cb8dbafd7",
+        "commit": "abc"
+      },
+      "receipt": {
+        "receiptId": "SIM-36F34D30F61C",
+        "receivedBy": "Simulated FedRAMP intake: a Python function in this repository. Nothing left the building.",
+        "packageSha256": "36f34d30f61ce96592b46ade8b0207be24b203aafea6ec54cb86072cb8dbafd7",
+        "message": "Thank you for your submission. It has been placed in a queue that does not exist."
+      },
+      "certificationReport": {
+        "file": "2026-10-01-sim-36f34d30f61c-simulated-certification-report.json",
+        "receivedOn": "2026-10-01",
+        "from": "FedRAMP (simulated)",
+        "trigger": "initial certification report (first package submission)",
+        "scnsCovered": [],
+        "sha256": "b0cf598b5ef7bf2077afe0add06a85636b65be0fe607b38c7d96ee108d96d1b6",
+        "report": {
+          "title": "SIMULATED REPORT, NOT ISSUED BY FEDRAMP: samaydlette.com is NOT FedRAMP certified (proof of concept)",
+          "notice": "This is not a FedRAMP Certification Report. FedRAMP did not write it, has never seen it, and has certified nothing. A Python function in scripts/submit-package.py wrote it in response to a simulated package submission, so the path that publishes FedRAMP Certification Reports unmodified within two weeks (CDS-CSO-FRC) runs end to end. This system is not certified.",
+          "simulated": true,
+          "notIssuedByFedRAMP": true,
+          "certificationStatus": "not certified (proof of concept)",
+          "issuer": "FedRAMP (simulated): a Python function in this repository, with no authority whatsoever.",
+          "cloudServiceOffering": "samaydlette.com",
+          "fedRampId": "Example Provider (EXD)",
+          "received": "2026-10-01",
+          "inResponseTo": {
+            "receiptId": "SIM-36F34D30F61C",
+            "submittedAt": "2026-10-01T12:00:00+00:00",
+            "packageSha256": "36f34d30f61ce96592b46ade8b0207be24b203aafea6ec54cb86072cb8dbafd7"
+          },
+          "trigger": "initial certification report (first package submission)",
+          "determination": "None. No certification decision has been made, and none will be: nothing was ever submitted to FedRAMP.",
+          "findings": [],
+          "noteToAgencies": "If you came here hoping for a FedRAMP certification, sorry: this one is pretend. Hit me up on LinkedIn: https://www.linkedin.com/in/sa2/"
+        }
+      }
+    }
+  ]
+}
diff --git a/tests/fixtures/cycle/bad/submission-log-malformed.json b/tests/fixtures/cycle/bad/submission-log-malformed.json
new file mode 100644
index 00000000..3302e221
--- /dev/null
+++ b/tests/fixtures/cycle/bad/submission-log-malformed.json
@@ -0,0 +1,8 @@
+{
+  "schema": "package-submission-log/1",
+  "entries": [
+    {
+      "submittedAt": "2026-11-05T00:00:00+00:00"
+    }
+  ]
+}
diff --git a/tests/fixtures/cycle/bad/submission-log-report-modified.json b/tests/fixtures/cycle/bad/submission-log-report-modified.json
new file mode 100644
index 00000000..f61f6f87
--- /dev/null
+++ b/tests/fixtures/cycle/bad/submission-log-report-modified.json
@@ -0,0 +1,81 @@
+{
+  "$comment": "KNOWN-BAD: the logged report was edited after it was received; its bytes no longer match the logged sha256, so it is never published (CDS-CSO-FRC: unmodified).",
+  "schema": "package-submission-log/1",
+  "generated_at": "2026-10-01T12:00:00+00:00",
+  "fedRampId": "Example Provider (EXD)",
+  "certificationPackageOverviewUri": "https://samaydlette.com/.well-known/certification-package-overview.json",
+  "nothingSent": true,
+  "simulated": {
+    "counterparty": "fedramp",
+    "how": "FedRAMP is simulated. The package goes to simulated_fedramp_intake() in scripts/submit-package.py, a function that never touches the network, and the only trace is this signed log. Nothing has been submitted to the real FedRAMP, and nothing will be."
+  },
+  "entries": [
+    {
+      "submittedAt": "2026-10-01T12:00:00+00:00",
+      "manifest": {
+        "components": [
+          {
+            "component": "CPO",
+            "rule": "CPO-CSO-OVR",
+            "url": "https://samaydlette.com/.well-known/certification-package-overview.json",
+            "sha256": "bdc9dcb20f748409072216beaa4fd621ff2303a34400dea920865b5feadd5252",
+            "contentSha256": "98b0de339ac1bf2eae4bc307716cd57c3078aaf9cfbc8e23fb3c966323ac3366",
+            "version": null
+          },
+          {
+            "component": "SDR",
+            "rule": "SDR-CSO-FRR",
+            "url": "https://samaydlette.com/.well-known/security-decision-record.json",
+            "sha256": "34f510919de0e3b74a338cf7c0502d062e95efc17b75f7341e9723580a90111a",
+            "contentSha256": "6ada229987020103f85b4b3a991a34aed52ed919d01a6c3f0ac1fd40c2093e6e",
+            "version": "1"
+          },
+          {
+            "component": "OCR",
+            "rule": "CCM-OCR-AVL",
+            "url": "https://samaydlette.com/.well-known/ongoing-certification-report.json",
+            "sha256": "d4a13fbd228c74a1ad6bcd307d07df358519dbbe020954a22ddbf233e9add736",
+            "contentSha256": "1541eb3e8db587c701aef2b148933e3581f89a91b4142ec2e422675e01ed2efd",
+            "version": null
+          }
+        ],
+        "packageSha256": "36f34d30f61ce96592b46ade8b0207be24b203aafea6ec54cb86072cb8dbafd7",
+        "commit": "abc"
+      },
+      "receipt": {
+        "receiptId": "SIM-36F34D30F61C",
+        "receivedBy": "Simulated FedRAMP intake: a Python function in this repository. Nothing left the building.",
+        "packageSha256": "36f34d30f61ce96592b46ade8b0207be24b203aafea6ec54cb86072cb8dbafd7",
+        "message": "Thank you for your submission. It has been placed in a queue that does not exist."
+      },
+      "certificationReport": {
+        "file": "2026-10-01-sim-36f34d30f61c-simulated-certification-report.json",
+        "receivedOn": "2026-10-01",
+        "from": "FedRAMP (simulated)",
+        "trigger": "initial certification report (first package submission)",
+        "scnsCovered": [],
+        "sha256": "b0cf598b5ef7bf2077afe0add06a85636b65be0fe607b38c7d96ee108d96d1b6",
+        "report": {
+          "title": "SIMULATED REPORT, NOT ISSUED BY FEDRAMP: samaydlette.com is NOT FedRAMP certified (proof of concept)",
+          "notice": "This is not a FedRAMP Certification Report. FedRAMP did not write it, has never seen it, and has certified nothing. A Python function in scripts/submit-package.py wrote it in response to a simulated package submission, so the path that publishes FedRAMP Certification Reports unmodified within two weeks (CDS-CSO-FRC) runs end to end. This system is not certified.",
+          "simulated": true,
+          "notIssuedByFedRAMP": true,
+          "certificationStatus": "not certified (proof of concept)",
+          "issuer": "FedRAMP (simulated): a Python function in this repository, with no authority whatsoever.",
+          "cloudServiceOffering": "samaydlette.com",
+          "fedRampId": "Example Provider (EXD)",
+          "received": "2026-10-01",
+          "inResponseTo": {
+            "receiptId": "SIM-36F34D30F61C",
+            "submittedAt": "2026-10-01T12:00:00+00:00",
+            "packageSha256": "36f34d30f61ce96592b46ade8b0207be24b203aafea6ec54cb86072cb8dbafd7"
+          },
+          "trigger": "initial certification report (first package submission)",
+          "determination": "Certified. (Edited after receipt.)",
+          "findings": [],
+          "noteToAgencies": "If you came here hoping for a FedRAMP certification, sorry: this one is pretend. Hit me up on LinkedIn: https://www.linkedin.com/in/sa2/"
+        }
+      }
+    }
+  ]
+}
diff --git a/tests/fixtures/cycle/bad/submission-log-report-not-labelled.json b/tests/fixtures/cycle/bad/submission-log-report-not-labelled.json
new file mode 100644
index 00000000..0f05536e
--- /dev/null
+++ b/tests/fixtures/cycle/bad/submission-log-report-not-labelled.json
@@ -0,0 +1,81 @@
+{
+  "$comment": "KNOWN-BAD: a report whose title does not say it is a simulated report NOT ISSUED BY FEDRAMP and that the system is not certified. Its sha256 matches, but it is never published.",
+  "schema": "package-submission-log/1",
+  "generated_at": "2026-10-01T12:00:00+00:00",
+  "fedRampId": "Example Provider (EXD)",
+  "certificationPackageOverviewUri": "https://samaydlette.com/.well-known/certification-package-overview.json",
+  "nothingSent": true,
+  "simulated": {
+    "counterparty": "fedramp",
+    "how": "FedRAMP is simulated. The package goes to simulated_fedramp_intake() in scripts/submit-package.py, a function that never touches the network, and the only trace is this signed log. Nothing has been submitted to the real FedRAMP, and nothing will be."
+  },
+  "entries": [
+    {
+      "submittedAt": "2026-10-01T12:00:00+00:00",
+      "manifest": {
+        "components": [
+          {
+            "component": "CPO",
+            "rule": "CPO-CSO-OVR",
+            "url": "https://samaydlette.com/.well-known/certification-package-overview.json",
+            "sha256": "bdc9dcb20f748409072216beaa4fd621ff2303a34400dea920865b5feadd5252",
+            "contentSha256": "98b0de339ac1bf2eae4bc307716cd57c3078aaf9cfbc8e23fb3c966323ac3366",
+            "version": null
+          },
+          {
+            "component": "SDR",
+            "rule": "SDR-CSO-FRR",
+            "url": "https://samaydlette.com/.well-known/security-decision-record.json",
+            "sha256": "34f510919de0e3b74a338cf7c0502d062e95efc17b75f7341e9723580a90111a",
+            "contentSha256": "6ada229987020103f85b4b3a991a34aed52ed919d01a6c3f0ac1fd40c2093e6e",
+            "version": "1"
+          },
+          {
+            "component": "OCR",
+            "rule": "CCM-OCR-AVL",
+            "url": "https://samaydlette.com/.well-known/ongoing-certification-report.json",
+            "sha256": "d4a13fbd228c74a1ad6bcd307d07df358519dbbe020954a22ddbf233e9add736",
+            "contentSha256": "1541eb3e8db587c701aef2b148933e3581f89a91b4142ec2e422675e01ed2efd",
+            "version": null
+          }
+        ],
+        "packageSha256": "36f34d30f61ce96592b46ade8b0207be24b203aafea6ec54cb86072cb8dbafd7",
+        "commit": "abc"
+      },
+      "receipt": {
+        "receiptId": "SIM-36F34D30F61C",
+        "receivedBy": "Simulated FedRAMP intake: a Python function in this repository. Nothing left the building.",
+        "packageSha256": "36f34d30f61ce96592b46ade8b0207be24b203aafea6ec54cb86072cb8dbafd7",
+        "message": "Thank you for your submission. It has been placed in a queue that does not exist."
+      },
+      "certificationReport": {
+        "file": "2026-10-01-sim-36f34d30f61c-simulated-certification-report.json",
+        "receivedOn": "2026-10-01",
+        "from": "FedRAMP (simulated)",
+        "trigger": "initial certification report (first package submission)",
+        "scnsCovered": [],
+        "sha256": "a2bc75d692ced6f9667bfdcf09311f59083e8e7170ad6397443d53bd20848a82",
+        "report": {
+          "title": "FedRAMP Certification Report",
+          "notice": "This is not a FedRAMP Certification Report. FedRAMP did not write it, has never seen it, and has certified nothing. A Python function in scripts/submit-package.py wrote it in response to a simulated package submission, so the path that publishes FedRAMP Certification Reports unmodified within two weeks (CDS-CSO-FRC) runs end to end. This system is not certified.",
+          "simulated": true,
+          "notIssuedByFedRAMP": true,
+          "certificationStatus": "not certified (proof of concept)",
+          "issuer": "FedRAMP (simulated): a Python function in this repository, with no authority whatsoever.",
+          "cloudServiceOffering": "samaydlette.com",
+          "fedRampId": "Example Provider (EXD)",
+          "received": "2026-10-01",
+          "inResponseTo": {
+            "receiptId": "SIM-36F34D30F61C",
+            "submittedAt": "2026-10-01T12:00:00+00:00",
+            "packageSha256": "36f34d30f61ce96592b46ade8b0207be24b203aafea6ec54cb86072cb8dbafd7"
+          },
+          "trigger": "initial certification report (first package submission)",
+          "determination": "None. No certification decision has been made, and none will be: nothing was ever submitted to FedRAMP.",
+          "findings": [],
+          "noteToAgencies": "If you came here hoping for a FedRAMP certification, sorry: this one is pretend. Hit me up on LinkedIn: https://www.linkedin.com/in/sa2/"
+        }
+      }
+    }
+  ]
+}
diff --git a/tests/fixtures/cycle/maintainer-good.json b/tests/fixtures/cycle/maintainer-good.json
new file mode 100644
index 00000000..13e48e9f
--- /dev/null
+++ b/tests/fixtures/cycle/maintainer-good.json
@@ -0,0 +1,13 @@
+{
+  "role_arn": "arn:aws:iam::123456789012:role/github-actions-package-maintenance-oidc",
+  "env_state": "ok",
+  "environment": {
+    "deployment_branch_policy": {
+      "protected_branches": false,
+      "custom_branch_policies": true
+    }
+  },
+  "branch_policies": [
+    "main"
+  ]
+}
diff --git a/tests/fixtures/cycle/offering-fsi-url.json b/tests/fixtures/cycle/offering-fsi-url.json
new file mode 100644
index 00000000..541a4244
--- /dev/null
+++ b/tests/fixtures/cycle/offering-fsi-url.json
@@ -0,0 +1,133 @@
+{
+  "_note": "Operator-declared editorial values for the Certification Package Overview (CPO-CSO-OVR: CDS-CSO-PUB, CDS-CSO-SVC, CDS-CSO-FID). scripts/build-cpo.py reads this plus the system profile, the CCM calendar and the canonical inventory and writes /.well-known/certification-package-overview.json in FedRAMP's schema. Where a value needs an outside party this proof of concept does not have (a FedRAMP ID, a SAM.gov UEI), the value is SIMULATED, says so, and the CPO flags it under providerExtensions.simulated. No published value here is an email address: contacts point to /.well-known/security.txt or the contact page.",
+  "provider_name": "Sam Aydlette",
+  "service_name": "samaydlette.com",
+  "service_acronym": "SAMCOM",
+  "fedramp_id": "Sam Aydlette (SAMCOM): PROOF-OF-CONCEPT-NOT-A-REAL-FEDRAMP-ID",
+  "fedramp_id_simulated": "No FedRAMP ID exists or is coming: nothing has been submitted to FedRAMP. FedRAMP's schema says to use the provider's name and acronym until an ID is assigned; the suffix makes sure nobody mistakes it for one.",
+  "uei": "NOT-A-REAL-UEI-0000",
+  "uei_simulated": "Simulated. The operator is not registering on SAM.gov, so there is no Unique Entity Identifier; this value is a placeholder that no SAM.gov lookup will ever find.",
+  "service_model": [
+    "SaaS"
+  ],
+  "deployment_model": "Public Cloud",
+  "business_category": [
+    "Governance, Risk, and Compliance (GRC)",
+    "Cybersecurity & Risk Management",
+    "Health & Wellness"
+  ],
+  "sales_contact": {
+    "name": "Sam Aydlette. Nothing here is for sale; say hello through the contact page: https://samaydlette.com/pages/contact.html"
+  },
+  "security_contact": {
+    "name": "Sam Aydlette, through the security contact in https://samaydlette.com/.well-known/security.txt"
+  },
+  "product_website": "https://samaydlette.com",
+  "logo_url": "https://samaydlette.com/assets/images/brand/logo.png",
+  "service_description": "A static personal website on AWS that doubles as a working continuous-compliance pipeline: every deploy derives signed, machine-readable compliance artifacts from one canonical inventory and publishes them under /.well-known/. Includes the Silk Reeling Mirror application, a Cognito-gated Tai Chi coaching API.",
+  "secure_configuration_guidance_url": "https://github.com/sam-aydlette/samaydlette.com/blob/main/docs/policies/secure-configuration-guide.md",
+  "documentation_overview_url": "https://samaydlette.com/trust/index.html",
+  "current_independent_assessment_service": "None \u2014 self-attested; no FedRAMP-Recognized independent assessment service engaged (IVV is N/A for this unsponsored proof of concept).",
+  "accountable_official": {
+    "name": "Sam Aydlette",
+    "title": "System Owner / Authorizing Operator",
+    "contact": "https://samaydlette.com/.well-known/security.txt"
+  },
+  "cryptographic_modules": [
+    {
+      "module": "AWS KMS",
+      "validation": "FIPS 140-3 (CMVP, HSM-backed)",
+      "role": "key store for all four customer-managed CMKs: at-rest (the compliance and watchdog Lambdas' environments and log groups, the DNS query log, the alert topic), runtime signing (the runtime signal), DNSSEC KSK, and the Silk Reeling app (its Lambda environment and log groups; the app holds no secrets since SCN-2026-006)",
+      "inherited": true
+    },
+    {
+      "module": "ACM TLS termination on CloudFront",
+      "validation": "FIPS-validated cipher suites; TLS 1.2+",
+      "role": "TLS in transit",
+      "inherited": true
+    },
+    {
+      "module": "S3 SSE-S3",
+      "validation": "AES-256 (AWS-managed keys)",
+      "role": "at-rest on the public website + log buckets",
+      "inherited": true
+    },
+    {
+      "module": "Sigstore Fulcio + Rekor",
+      "validation": "ECDSA P-256 (FIPS-approved algorithm); the implementations are NOT CMVP-validated modules",
+      "role": "deploy-time keyless signing",
+      "inherited": false,
+      "compensating_control": "trust anchored in the public Rekor transparency log"
+    }
+  ],
+  "services": [
+    {
+      "name": "samaydlette.com static website",
+      "description": "Public static content (S3 origin behind CloudFront), plus the signed compliance artifacts published under /.well-known/ and the trust center at /trust/.",
+      "boundary_groups": [
+        "website"
+      ],
+      "security_category": {
+        "confidentiality": "low",
+        "integrity": "moderate",
+        "availability": "low",
+        "rationale": "Public content: nothing confidential. Integrity is moderate because defacement or tampering of published evidence would mislead readers. Availability is low: a personal site."
+      },
+      "in_mas_scope": true
+    },
+    {
+      "name": "Silk Reeling Mirror application",
+      "description": "Cognito-gated HTTP API (API Gateway -> Lambda) serving a browser SPA that coaches Tai Chi; writes feedback text from the scores in the Lambda, with no external interconnection (optional LLM feedback is customer-configurable and disabled here).",
+      "date_available": "2026-06-03",
+      "boundary_groups": [
+        "app"
+      ],
+      "security_category": {
+        "confidentiality": "low",
+        "integrity": "moderate",
+        "availability": "low",
+        "rationale": "Holds invited users' sign-in accounts and the pose scores they submit, no federal data: confidentiality low. Integrity moderate: wrong coaching or tampered accounts are the harm. Availability low."
+      },
+      "in_mas_scope": true
+    },
+    {
+      "name": "Continuous compliance evidence (pipeline trust root, runtime KSI emitter, evidence watchdog)",
+      "description": "The deploy's trust root (OIDC roles, CloudFront, DNSSEC, remote state), the daily runtime re-validation of live configuration (signed runtime KSI signal), the hourly evidence-freshness watchdog with its alarms, and the audit trail and keys behind them. GitHub Actions and Sigstore, which build and sign the evidence, are third-party information resources inside the boundary.",
+      "boundary_groups": [
+        "compliance",
+        "watchdog",
+        "audit",
+        "trust-root"
+      ],
+      "security_category": {
+        "confidentiality": "low",
+        "integrity": "moderate",
+        "availability": "low",
+        "rationale": "The evidence is public by design. Integrity is moderate: false evidence is the harm this system exists to prevent. Availability is low."
+      },
+      "in_mas_scope": true
+    }
+  ],
+  "not_included": [
+    {
+      "name": "Podcast and video audio hosted by third parties",
+      "why": "Linked from pages, served by their own hosts; not part of the offering."
+    },
+    {
+      "name": "MediaPipe libraries and models (cdn.jsdelivr.net, storage.googleapis.com)",
+      "why": "Loaded by the visitor's browser from third-party hosts at run time; listed as third-party information resources, not services of this offering."
+    },
+    {
+      "name": "Optional LLM coaching feedback",
+      "why": "Customer-configurable and disabled; no external AI service is called."
+    },
+    {
+      "name": "Newsletter, RSS and social feeds",
+      "why": "None is offered under this certification."
+    }
+  ],
+  "fedramp_security_inbox": {
+    "contact": "https://samaydlette.com/.well-known/security.txt",
+    "address": "https://samaydlette.com/.well-known/security.txt"
+  }
+}
diff --git a/tests/fixtures/cycle/package/cpo.json b/tests/fixtures/cycle/package/cpo.json
new file mode 100644
index 00000000..7de8a7e3
--- /dev/null
+++ b/tests/fixtures/cycle/package/cpo.json
@@ -0,0 +1,80 @@
+{
+  "$schema": "https://fedramp.gov/schemas/fedramp-certification-package-overview-schema-2026-06-24.json",
+  "serviceIdentification": {
+    "providerName": "Example Provider",
+    "serviceName": "Example Docs",
+    "serviceAcronym": "EXD",
+    "serviceDescription": "A document service.",
+    "certificationType": "20x",
+    "fedRampPackageId": "Example Provider (EXD)",
+    "website": "https://example.com",
+    "logo": "https://example.com/logo.png"
+  },
+  "serviceProperties": {
+    "serviceType": [
+      "SaaS"
+    ],
+    "deploymentModel": "Public Cloud",
+    "businessCategory": [
+      "Collaboration"
+    ],
+    "trustCenter": {
+      "repositoryType": [
+        "Trust Center"
+      ],
+      "url": "https://example.com/trust",
+      "repositoryDescription": "All certification data.",
+      "authenticationRequired": false
+    },
+    "nextOngoingCertificationReportDate": "2027-02-01",
+    "secureConfigurationGuidance": {
+      "repositoryType": [
+        "Secure Configuration Guidance"
+      ],
+      "url": "https://example.com/scg",
+      "repositoryDescription": "The secure configuration guide.",
+      "authenticationRequired": false
+    }
+  },
+  "contactInformation": [
+    {
+      "contactType": "Security",
+      "contactName": "Sec Team",
+      "contactEmail": "security@example.com"
+    },
+    {
+      "contactType": "Sales",
+      "contactName": "Sales Team"
+    }
+  ],
+  "certifiedServices": [
+    {
+      "serviceName": "File preview",
+      "serviceDescription": "Renders uploads."
+    }
+  ],
+  "thirdPartyInformationResources": {
+    "nonCertified": [
+      {
+        "name": "Example CDN",
+        "provider": "Example Co",
+        "useCase": "Serves static files."
+      }
+    ]
+  },
+  "providerExtensions": {
+    "fedRampId": "Example Provider (EXD)",
+    "contentSha256": "98b0de339ac1bf2eae4bc307716cd57c3078aaf9cfbc8e23fb3c966323ac3366",
+    "independentAssessment": {
+      "overallSummary": {
+        "record_id": "X-SUMMARY",
+        "kind": "summary",
+        "text": "Overall summary (simulated)."
+      }
+    },
+    "certification": {
+      "program": "FedRAMP 20x, Program path, Class C",
+      "status": "not certified (proof of concept)"
+    }
+  }
+}
diff --git a/tests/fixtures/cycle/package/ocr.json b/tests/fixtures/cycle/package/ocr.json
new file mode 100644
index 00000000..46dfd1a8
--- /dev/null
+++ b/tests/fixtures/cycle/package/ocr.json
@@ -0,0 +1,24 @@
+{
+  "$schema": "https://fedramp.gov/schemas/fedramp-ongoing-certification-report-schema-2026-06-24.json",
+  "certificationPackageOverviewUri": "https://samaydlette.com/.well-known/certification-package-overview.json",
+  "reportPeriod": {
+    "from": "2026-08-01",
+    "to": "2026-10-31"
+  },
+  "certificationDataChanges": [],
+  "plannedCertificationDataChanges": {
+    "planningHorizonThrough": "2027-01-31",
+    "changes": []
+  },
+  "acceptedVulnerabilities": "None.",
+  "transformativeChanges": [],
+  "updatedRecommendations": [],
+  "activeAgencies": [],
+  "reportableIncidents": {
+    "incidents": []
+  },
+  "providerExtensions": {
+    "fedRampId": "Example Provider (EXD)",
+    "contentSha256": "1541eb3e8db587c701aef2b148933e3581f89a91b4142ec2e422675e01ed2efd"
+  }
+}
diff --git a/tests/fixtures/cycle/package/sdr.json b/tests/fixtures/cycle/package/sdr.json
new file mode 100644
index 00000000..a82205bb
--- /dev/null
+++ b/tests/fixtures/cycle/package/sdr.json
@@ -0,0 +1,61 @@
+{
+  "$schema": "https://fedramp.gov/schemas/fedramp-security-decision-record-schema-2026-06-24.json",
+  "certificationPackageOverviewUri": "https://samaydlette.com/.well-known/certification-package-overview.json",
+  "metadata": {
+    "version": "1",
+    "lastUpdated": "2026-11-05T00:00:00Z",
+    "updateSource": "pipeline"
+  },
+  "fedRampRequirements": [
+    {
+      "frrID": "VDR-CSO-DET",
+      "frrImplementationStatus": "Implemented",
+      "frrImplementation": [
+        "Scanners run on every deploy."
+      ]
+    }
+  ],
+  "keySecurityIndicators": [
+    {
+      "ksiId": "KSI-CNA-01",
+      "ksiImplementation": [
+        "x"
+      ],
+      "ksiValidation": [
+        "y"
+      ],
+      "ksiAssessment": [
+        "z"
+      ],
+      "ksiTests": [
+        "t"
+      ],
+      "ksiEvidence": [
+        {
+          "evidenceType": "Report",
+          "evidenceLocation": "https://example.com/e.json"
+        }
+      ]
+    }
+  ],
+  "securityControls": [
+    {
+      "controlId": "AC-2",
+      "controlImplementationStatus": "Implemented",
+      "parameterValues": [
+        {
+          "parameterId": "ac-02_odp.01",
+          "parameterValue": "30 days"
+        }
+      ]
+    }
+  ],
+  "providerExtensions": {
+    "fedRampId": "Example Provider (EXD)",
+    "contentSha256": "6ada229987020103f85b4b3a991a34aed52ed919d01a6c3f0ac1fd40c2093e6e",
+    "certification": {
+      "program": "FedRAMP 20x, Program path, Class C",
+      "status": "not certified (proof of concept)"
+    }
+  }
+}
diff --git a/tests/fixtures/decisions/automatable-no-evidence.json b/tests/fixtures/decisions/automatable-no-evidence.json
new file mode 100644
index 00000000..4f0f779f
--- /dev/null
+++ b/tests/fixtures/decisions/automatable-no-evidence.json
@@ -0,0 +1,26 @@
+{
+  "_note": "Known-bad: a record that says exploitation of its findings cannot be automated, with no evidence. VER-EVA-AIA assumes automatable unless there is evidence otherwise; the build stops.",
+  "schema": "decisions/1",
+  "decisions": [
+    {
+      "id": "DEC-001",
+      "title": "fixture",
+      "status": "in-force",
+      "disposition": "accepted",
+      "justification": "fixture",
+      "decided_by": "Fixture",
+      "decided_on": "2026-01-01", "confirmed_on": "2026-01-01",
+      "review_by": "2027-01-01",
+      "applies_to": {
+        "check_ids": [],
+        "vuln_ids": [
+          "CVE-2099-0001"
+        ],
+        "resources": []
+      },
+      "automatable": {
+        "value": "no"
+      }
+    }
+  ]
+}
diff --git a/tests/fixtures/decisions/closed-not-remediated.json b/tests/fixtures/decisions/closed-not-remediated.json
index 39ce0b3d..7f2fc4e6 100644
--- a/tests/fixtures/decisions/closed-not-remediated.json
+++ b/tests/fixtures/decisions/closed-not-remediated.json
@@ -9,7 +9,7 @@
       "disposition": "risk-accepted",
       "justification": "fixture",
       "decided_by": "Fixture",
-      "decided_on": "2026-01-01",
+      "decided_on": "2026-01-01", "confirmed_on": "2026-01-01",
       "review_by": "2027-01-01",
       "applies_to": {
         "check_ids": [],
diff --git a/tests/fixtures/decisions/confirmed-before-decided.json b/tests/fixtures/decisions/confirmed-before-decided.json
new file mode 100644
index 00000000..053dcb0b
--- /dev/null
+++ b/tests/fixtures/decisions/confirmed-before-decided.json
@@ -0,0 +1,24 @@
+{
+  "_note": "Known-bad: confirmed before it was decided.",
+  "schema": "decisions/1",
+  "decisions": [
+    {
+      "id": "DEC-001",
+      "title": "fixture",
+      "status": "in-force",
+      "disposition": "risk-accepted",
+      "justification": "fixture",
+      "decided_on": "2026-01-01",
+      "confirmed_on": "2025-12-31",
+      "review_by": "2027-01-01",
+      "applies_to": {
+        "check_ids": [
+          "CKV_AWS_68"
+        ],
+        "vuln_ids": [],
+        "resources": []
+      },
+      "decided_by": "Sam Aydlette"
+    }
+  ]
+}
diff --git a/tests/fixtures/decisions/duplicate-claim.json b/tests/fixtures/decisions/duplicate-claim.json
index 8086e356..609f3af3 100644
--- a/tests/fixtures/decisions/duplicate-claim.json
+++ b/tests/fixtures/decisions/duplicate-claim.json
@@ -9,7 +9,7 @@
       "disposition": "risk-accepted",
       "justification": "fixture",
       "decided_by": "Fixture",
-      "decided_on": "2026-01-01",
+      "decided_on": "2026-01-01", "confirmed_on": "2026-01-01",
       "review_by": "2027-01-01",
       "applies_to": {
         "check_ids": [
@@ -26,7 +26,7 @@
       "disposition": "false-positive",
       "justification": "fixture",
       "decided_by": "Fixture",
-      "decided_on": "2026-01-01",
+      "decided_on": "2026-01-01", "confirmed_on": "2026-01-01",
       "review_by": "2027-01-01",
       "applies_to": {
         "check_ids": [
diff --git a/tests/fixtures/decisions/marking-in-text.json b/tests/fixtures/decisions/marking-in-text.json
new file mode 100644
index 00000000..5b9d7776
--- /dev/null
+++ b/tests/fixtures/decisions/marking-in-text.json
@@ -0,0 +1,24 @@
+{
+  "_note": "Known-bad: a drafting note in the justification instead of source.drafted_by and confirmed_on.",
+  "schema": "decisions/1",
+  "decisions": [
+    {
+      "id": "DEC-001",
+      "title": "fixture",
+      "status": "in-force",
+      "disposition": "risk-accepted",
+      "justification": "AI-drafted for the operator's confirmation. fixture",
+      "decided_on": "2026-01-01",
+      "confirmed_on": "2026-01-01",
+      "review_by": "2027-01-01",
+      "applies_to": {
+        "check_ids": [
+          "CKV_AWS_68"
+        ],
+        "vuln_ids": [],
+        "resources": []
+      },
+      "decided_by": "Sam Aydlette"
+    }
+  ]
+}
diff --git a/tests/fixtures/decisions/planned-reduction-closed.json b/tests/fixtures/decisions/planned-reduction-closed.json
new file mode 100644
index 00000000..defeb077
--- /dev/null
+++ b/tests/fixtures/decisions/planned-reduction-closed.json
@@ -0,0 +1,28 @@
+{
+  "_note": "Known-bad: a closed record that still plans a reduction. A closed (remediated) decision has nothing left to reduce; the build stops.",
+  "schema": "decisions/1",
+  "decisions": [
+    {
+      "id": "DEC-001",
+      "title": "fixture",
+      "status": "closed",
+      "disposition": "remediated",
+      "justification": "fixture",
+      "decided_by": "Fixture",
+      "decided_on": "2026-01-01", "confirmed_on": "2026-01-01",
+      "review_by": "2027-01-01",
+      "applies_to": {
+        "check_ids": [],
+        "vuln_ids": [
+          "CVE-2099-0001"
+        ],
+        "resources": []
+      },
+      "closed_on": "2026-06-01",
+      "planned_reduction": {
+        "date": "2026-12-01",
+        "target_pain": "N1"
+      }
+    }
+  ]
+}
diff --git a/tests/fixtures/decisions/planned-reduction-malformed.json b/tests/fixtures/decisions/planned-reduction-malformed.json
new file mode 100644
index 00000000..90688901
--- /dev/null
+++ b/tests/fixtures/decisions/planned-reduction-malformed.json
@@ -0,0 +1,27 @@
+{
+  "_note": "Known-bad: a planned reduction whose target is not an N-rating. A malformed plan would publish a projected reduction nobody planned; the build stops.",
+  "schema": "decisions/1",
+  "decisions": [
+    {
+      "id": "DEC-001",
+      "title": "fixture",
+      "status": "in-force",
+      "disposition": "remediate",
+      "justification": "fixture",
+      "decided_by": "Fixture",
+      "decided_on": "2026-01-01", "confirmed_on": "2026-01-01",
+      "review_by": "2027-01-01",
+      "applies_to": {
+        "check_ids": [],
+        "vuln_ids": [
+          "CVE-2099-0001"
+        ],
+        "resources": []
+      },
+      "planned_reduction": {
+        "date": "2026-12-01",
+        "target_pain": "low"
+      }
+    }
+  ]
+}
diff --git a/tests/fixtures/decisions/superseded-without-replaced-by.json b/tests/fixtures/decisions/superseded-without-replaced-by.json
new file mode 100644
index 00000000..e5a7f13b
--- /dev/null
+++ b/tests/fixtures/decisions/superseded-without-replaced-by.json
@@ -0,0 +1,25 @@
+{
+  "_note": "Known-bad: a superseded record that does not say what replaces it.",
+  "schema": "decisions/1",
+  "decisions": [
+    {
+      "id": "DEC-001",
+      "title": "fixture",
+      "status": "closed",
+      "disposition": "superseded",
+      "justification": "fixture",
+      "decided_on": "2026-01-01",
+      "confirmed_on": "2026-01-01",
+      "review_by": "2027-01-01",
+      "applies_to": {
+        "check_ids": [
+          "CKV_AWS_68"
+        ],
+        "vuln_ids": [],
+        "resources": []
+      },
+      "decided_by": "Sam Aydlette",
+      "closed_on": "2026-11-06"
+    }
+  ]
+}
diff --git a/tests/fixtures/decisions/unconfirmed.json b/tests/fixtures/decisions/unconfirmed.json
new file mode 100644
index 00000000..77348b5d
--- /dev/null
+++ b/tests/fixtures/decisions/unconfirmed.json
@@ -0,0 +1,23 @@
+{
+  "_note": "Known-bad: an in-force decision the operator has not confirmed (no confirmed_on). It cannot be in force; the build stops.",
+  "schema": "decisions/1",
+  "decisions": [
+    {
+      "id": "DEC-001",
+      "title": "fixture",
+      "status": "in-force",
+      "disposition": "risk-accepted",
+      "justification": "fixture",
+      "decided_on": "2026-01-01",
+      "review_by": "2027-01-01",
+      "applies_to": {
+        "check_ids": [
+          "CKV_AWS_68"
+        ],
+        "vuln_ids": [],
+        "resources": []
+      },
+      "decided_by": "Sam Aydlette"
+    }
+  ]
+}
diff --git a/tests/fixtures/decisions/undecided.json b/tests/fixtures/decisions/undecided.json
index fc2f23d0..aa6589b9 100644
--- a/tests/fixtures/decisions/undecided.json
+++ b/tests/fixtures/decisions/undecided.json
@@ -8,7 +8,7 @@
       "status": "in-force",
       "disposition": "risk-accepted",
       "justification": "fixture",
-      "decided_on": "2026-01-01",
+      "decided_on": "2026-01-01", "confirmed_on": "2026-01-01",
       "review_by": "2027-01-01",
       "applies_to": {
         "check_ids": [
diff --git a/tests/fixtures/decisions/unknown-field.json b/tests/fixtures/decisions/unknown-field.json
index 1169b1d4..27f6119f 100644
--- a/tests/fixtures/decisions/unknown-field.json
+++ b/tests/fixtures/decisions/unknown-field.json
@@ -9,7 +9,7 @@
       "disposition": "risk-accepted",
       "justification": "fixture",
       "decided_by": "Fixture",
-      "decided_on": "2026-01-01",
+      "decided_on": "2026-01-01", "confirmed_on": "2026-01-01",
       "applies_to": {
         "check_ids": [],
         "vuln_ids": [],
diff --git a/tests/fixtures/detection/codeql-error.json b/tests/fixtures/detection/codeql-error.json
new file mode 100644
index 00000000..70f2aed1
--- /dev/null
+++ b/tests/fixtures/detection/codeql-error.json
@@ -0,0 +1,60 @@
+{
+ "analyses": [
+  {
+   "category": "/language:python",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/language:javascript-typescript",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/language:actions",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "the extractor failed",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/silk-reeling/language:python",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/silk-reeling/language:javascript-typescript",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  }
+ ],
+ "alerts": []
+}
diff --git a/tests/fixtures/detection/codeql-missing-category.json b/tests/fixtures/detection/codeql-missing-category.json
new file mode 100644
index 00000000..6748c868
--- /dev/null
+++ b/tests/fixtures/detection/codeql-missing-category.json
@@ -0,0 +1,49 @@
+{
+ "analyses": [
+  {
+   "category": "/language:python",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/language:javascript-typescript",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/language:actions",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/silk-reeling/language:python",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  }
+ ],
+ "alerts": []
+}
diff --git a/tests/fixtures/detection/codeql-missing.json.error b/tests/fixtures/detection/codeql-missing.json.error
new file mode 100644
index 00000000..d2e1ae28
--- /dev/null
+++ b/tests/fixtures/detection/codeql-missing.json.error
@@ -0,0 +1 @@
+code-scanning API: gh: no analysis found (HTTP 404)
\ No newline at end of file
diff --git a/tests/fixtures/detection/codeql-no-alerts-key.json b/tests/fixtures/detection/codeql-no-alerts-key.json
new file mode 100644
index 00000000..32b7b4bc
--- /dev/null
+++ b/tests/fixtures/detection/codeql-no-alerts-key.json
@@ -0,0 +1,59 @@
+{
+ "analyses": [
+  {
+   "category": "/language:python",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/language:javascript-typescript",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/language:actions",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/silk-reeling/language:python",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/silk-reeling/language:javascript-typescript",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  }
+ ]
+}
diff --git a/tests/fixtures/detection/codeql-stale.json b/tests/fixtures/detection/codeql-stale.json
new file mode 100644
index 00000000..b3590e70
--- /dev/null
+++ b/tests/fixtures/detection/codeql-stale.json
@@ -0,0 +1,60 @@
+{
+ "analyses": [
+  {
+   "category": "/language:python",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/language:javascript-typescript",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/language:actions",
+   "created_at": "2026-10-31T08:00:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/silk-reeling/language:python",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/silk-reeling/language:javascript-typescript",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  }
+ ],
+ "alerts": []
+}
diff --git a/tests/fixtures/detection/codeql.json b/tests/fixtures/detection/codeql.json
new file mode 100644
index 00000000..6a58852b
--- /dev/null
+++ b/tests/fixtures/detection/codeql.json
@@ -0,0 +1,97 @@
+{
+ "analyses": [
+  {
+   "category": "/language:python",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/language:javascript-typescript",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/language:actions",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/silk-reeling/language:python",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/silk-reeling/language:javascript-typescript",
+   "created_at": "2026-11-04T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "0000000000000000000000000000000000000000",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  },
+  {
+   "category": "/language:python",
+   "created_at": "2026-10-20T05:41:00Z",
+   "error": "",
+   "results_count": 0,
+   "commit_sha": "1111111111111111111111111111111111111111",
+   "tool": {
+    "name": "CodeQL",
+    "version": "2.23.0"
+   }
+  }
+ ],
+ "alerts": [
+  {
+   "number": 7,
+   "state": "open",
+   "created_at": "2026-11-03T05:41:00Z",
+   "rule": {
+    "id": "py/path-injection",
+    "name": "py/path-injection",
+    "description": "Uncontrolled data used in path expression",
+    "severity": "error",
+    "security_severity_level": "high"
+   },
+   "most_recent_instance": {
+    "category": "/silk-reeling/language:python",
+    "location": {
+     "path": "backend/main.py",
+     "start_line": 120,
+     "end_line": 120,
+     "start_column": 5,
+     "end_column": 9
+    },
+    "message": {
+     "text": "This path depends on a user-provided value."
+    }
+   }
+  }
+ ]
+}
diff --git a/tests/fixtures/detection/zap-api-empty.json b/tests/fixtures/detection/zap-api-empty.json
new file mode 100644
index 00000000..75a18eea
--- /dev/null
+++ b/tests/fixtures/detection/zap-api-empty.json
@@ -0,0 +1,5 @@
+{
+ "@version": "2.17.0",
+ "@generated": "Wed, 4 Nov 2026 06:00:00",
+ "site": []
+}
diff --git a/tests/fixtures/detection/zap-api-stale.json b/tests/fixtures/detection/zap-api-stale.json
new file mode 100644
index 00000000..8d8db01e
--- /dev/null
+++ b/tests/fixtures/detection/zap-api-stale.json
@@ -0,0 +1,25 @@
+{
+ "@version": "2.17.0",
+ "@generated": "Sat, 31 Oct 2026 06:00:00",
+ "site": [
+  {
+   "@name": "https://samaydlette.com",
+   "@host": "samaydlette.com",
+   "alerts": [
+    {
+     "pluginid": "10021",
+     "alertRef": "10021",
+     "alert": "X-Content-Type-Options Header Missing",
+     "riskcode": "1",
+     "desc": "fixture",
+     "instances": [
+      {
+       "uri": "https://samaydlette.com/silk-reeling/api/exercises",
+       "method": "GET"
+      }
+     ]
+    }
+   ]
+  }
+ ]
+}
diff --git a/tests/fixtures/detection/zap-api-undated.json b/tests/fixtures/detection/zap-api-undated.json
new file mode 100644
index 00000000..910349ab
--- /dev/null
+++ b/tests/fixtures/detection/zap-api-undated.json
@@ -0,0 +1,10 @@
+{
+ "@version": "2.17.0",
+ "site": [
+  {
+   "@name": "https://samaydlette.com",
+   "@host": "samaydlette.com",
+   "alerts": []
+  }
+ ]
+}
diff --git a/tests/fixtures/detection/zap-api.json b/tests/fixtures/detection/zap-api.json
new file mode 100644
index 00000000..01079acc
--- /dev/null
+++ b/tests/fixtures/detection/zap-api.json
@@ -0,0 +1,25 @@
+{
+ "@version": "2.17.0",
+ "@generated": "Wed, 4 Nov 2026 06:00:00",
+ "site": [
+  {
+   "@name": "https://samaydlette.com",
+   "@host": "samaydlette.com",
+   "alerts": [
+    {
+     "pluginid": "10021",
+     "alertRef": "10021",
+     "alert": "X-Content-Type-Options Header Missing",
+     "riskcode": "1",
+     "desc": "fixture",
+     "instances": [
+      {
+       "uri": "https://samaydlette.com/silk-reeling/api/exercises",
+       "method": "GET"
+      }
+     ]
+    }
+   ]
+  }
+ ]
+}
diff --git a/tests/fixtures/dispositions/register-fp-names-control.json b/tests/fixtures/dispositions/register-fp-names-control.json
index 26d77df2..0fefa6bf 100644
--- a/tests/fixtures/dispositions/register-fp-names-control.json
+++ b/tests/fixtures/dispositions/register-fp-names-control.json
@@ -3,7 +3,7 @@
   "schema": "decisions/1",
   "decisions": [
     {"id": "DEC-003", "title": "fixture", "status": "in-force", "disposition": "false-positive", "justification": "a WAF rule blocks it",
-     "decided_by": "Fixture", "decided_on": "2026-10-01", "review_by": "2027-10-01",
+     "decided_by": "Fixture", "decided_on": "2026-10-01", "confirmed_on": "2026-10-01", "review_by": "2027-10-01",
      "applies_to": {"check_ids": [], "vuln_ids": ["CVE-0000-0201"], "resources": []},
      "vuln_fields": {"mitigation": "MIT-FIX-1"}}
   ]
diff --git a/tests/fixtures/dispositions/register-lapsed.json b/tests/fixtures/dispositions/register-lapsed.json
index 6b79678b..23d046d6 100644
--- a/tests/fixtures/dispositions/register-lapsed.json
+++ b/tests/fixtures/dispositions/register-lapsed.json
@@ -3,7 +3,7 @@
   "schema": "decisions/1",
   "decisions": [
     {"id": "DEC-003", "title": "fixture", "status": "in-force", "disposition": "false-positive", "justification": "fixture",
-     "decided_by": "Fixture", "decided_on": "2025-01-01", "review_by": "2026-01-01",
+     "decided_by": "Fixture", "decided_on": "2025-01-01", "confirmed_on": "2025-01-01", "review_by": "2026-01-01",
      "applies_to": {"check_ids": [], "vuln_ids": ["CVE-0000-0200"], "resources": []}}
   ]
 }
diff --git a/tests/fixtures/edge-access-logging/delivery-source.json b/tests/fixtures/edge-access-logging/delivery-source.json
new file mode 100644
index 00000000..887662fc
--- /dev/null
+++ b/tests/fixtures/edge-access-logging/delivery-source.json
@@ -0,0 +1,2 @@
+{"deliverySource": {"name": "samaydlette-com-edge-access", "logType": "ACCESS_LOGS", "service": "cloudfront",
+  "resourceArns": ["arn:aws:cloudfront::ACCOUNT:distribution/EXAMPLE"]}}
diff --git a/tests/fixtures/edge-access-logging/good-deliveries.json b/tests/fixtures/edge-access-logging/good-deliveries.json
new file mode 100644
index 00000000..4fa9b6d8
--- /dev/null
+++ b/tests/fixtures/edge-access-logging/good-deliveries.json
@@ -0,0 +1,3 @@
+{"deliveries": [{"id": "fixture", "deliverySourceName": "samaydlette-com-edge-access",
+  "deliveryDestinationType": "S3",
+  "recordFields": ["date", "time", "x-edge-location", "c-country", "cs-method", "cs-uri-stem", "sc-status", "sc-bytes", "x-edge-result-type"]}]}
diff --git a/tests/fixtures/edge-access-logging/known-bad-deliveries.json b/tests/fixtures/edge-access-logging/known-bad-deliveries.json
new file mode 100644
index 00000000..3381be4a
--- /dev/null
+++ b/tests/fixtures/edge-access-logging/known-bad-deliveries.json
@@ -0,0 +1,3 @@
+{"deliveries": [{"id": "fixture", "deliverySourceName": "samaydlette-com-edge-access",
+  "deliveryDestinationType": "S3",
+  "recordFields": ["date", "time", "c-ip", "cs-uri-stem", "cs-uri-query", "cs(User-Agent)", "sc-status"]}]}
diff --git a/tests/fixtures/engagement/invitations.txt b/tests/fixtures/engagement/invitations.txt
new file mode 100644
index 00000000..16ab52ee
--- /dev/null
+++ b/tests/fixtures/engagement/invitations.txt
@@ -0,0 +1,13 @@
+# Known-bad (DEC-194): one line per wording the phrase screen must catch. Each
+# offers to invite, register, notify, serve or answer a real agency or FedRAMP.
+We invite agencies to the Quarterly Review.
+An agency can register for the review through the form.
+An agency that wants to be on record files the issue form.
+Notify FedRAMP within 5 business days.
+The inventory is supplied to FedRAMP on request.
+Use the registration form linked from the calendar.
+Registered parties receive the recording.
+The join link is in the invitation.
+The answer comes within 10 business days.
+The transcript goes to the parties who registered.
+File https://github.com/sam-aydlette/samaydlette.com/issues/new?template=agency-access.yml
diff --git a/tests/fixtures/engagement/output-without-statement.json b/tests/fixtures/engagement/output-without-statement.json
new file mode 100644
index 00000000..47fc7c1f
--- /dev/null
+++ b/tests/fixtures/engagement/output-without-statement.json
@@ -0,0 +1,6 @@
+{
+  "$comment": "KNOWN-BAD (tests/test_engagement.py): a simulated output that names a simulated counterparty but does not carry the DEC-194 no-engagement statement.",
+  "schema": "incident-deliveries/1",
+  "simulation": true,
+  "deliveries": [{"recipients": [{"recipient": "FedRAMP Incident Desk (simulated)", "simulated": true}]}]
+}
diff --git a/tests/fixtures/evaluation/coverage-gap.json b/tests/fixtures/evaluation/coverage-gap.json
new file mode 100644
index 00000000..7c96cced
--- /dev/null
+++ b/tests/fixtures/evaluation/coverage-gap.json
@@ -0,0 +1,14 @@
+{
+  "_note": "Known-bad: the inventory has a component type no detection technique reaches (a new resource with no IaC source), and the SCA feed last ran 40 days ago. Both components are detection gaps (VDR-TFR-PCD); the build records vdr.coverage, which becomes a process finding.",
+  "now": "2026-11-05T12:00:00+00:00",
+  "components": {
+    "x::unknown::thing": {"type": "unknown_kind"},
+    "pkg:npm/a@1": {"type": "npm_package"},
+    "aws::object_store::site": {"type": "object_store", "resource_type": "AWS::S3::Bucket"},
+    "ext::svc": {"type": "external_service"}
+  },
+  "detection": {"checked_at": "2026-11-05T11:00:00+00:00", "feeds": [
+    {"feed": "grype", "status": "ok", "source_date": "2026-09-26T00:00:00+00:00"},
+    {"feed": "checkov", "status": "ok", "source_date": null}
+  ]}
+}
diff --git a/tests/fixtures/evaluation/group-overdue.json b/tests/fixtures/evaluation/group-overdue.json
new file mode 100644
index 00000000..833da44d
--- /dev/null
+++ b/tests/fixtures/evaluation/group-overdue.json
@@ -0,0 +1,9 @@
+{
+  "_note": "Known-bad: two open findings of one group (one Checkov check, no decision). The first was evaluated 60 days ago; the second appeared today. Each alone is inside its own N2+LEV+IRV timeframe only for the newcomer; as a group (VER-EVA-GRV) the newcomer is on the old member's clock, so it is past the deadline and blocks (G3). Without grouping it would pass.",
+  "now": "2026-11-03T12:00:00+00:00",
+  "old_days": 60,
+  "items": [
+    {"id": "old", "group": "check:checkov:CKV_TEST_1"},
+    {"id": "new", "group": "check:checkov:CKV_TEST_1"}
+  ]
+}
diff --git a/tests/fixtures/fedramp-id/freshness-uncovered.json b/tests/fixtures/fedramp-id/freshness-uncovered.json
new file mode 100644
index 00000000..aa179c82
--- /dev/null
+++ b/tests/fixtures/fedramp-id/freshness-uncovered.json
@@ -0,0 +1,10 @@
+{
+  "_note": "Known bad (CDS-CSO-FID coverage): a published JSON artifact the FedRAMP ID gate neither checks nor exempts, and one exempt artifact with an empty reason.",
+  "artifacts": [
+    {"path": ".well-known/security-decision-record.json"},
+    {"path": ".well-known/new-unstamped-report.json"},
+    {"path": ".well-known/iiw.csv"}
+  ],
+  "exempt": {"boundary-corroboration.json": ""},
+  "exempt_artifact": ".well-known/boundary-corroboration.json"
+}
diff --git a/tests/fixtures/fedramp-id/incident-report-without-fedramp-id.json b/tests/fixtures/fedramp-id/incident-report-without-fedramp-id.json
new file mode 100644
index 00000000..c84cadf1
--- /dev/null
+++ b/tests/fixtures/fedramp-id/incident-report-without-fedramp-id.json
@@ -0,0 +1,7 @@
+{
+  "$schema": "https://fedramp.gov/schemas/fedramp-incident-report-schema-2026-06-24.json",
+  "certificationPackageOverviewUri": "https://samaydlette.com/.well-known/certification-package-overview.json",
+  "reportType": "Initial",
+  "providerTrackingId": "INC-0000-000",
+  "providerExtensions": {"note": "Known bad (CDS-CSO-FID): a report in a FedRAMP schema without providerExtensions.fedRampId."}
+}
diff --git a/tests/fixtures/frr-evidence/failing-cited-test.xml b/tests/fixtures/frr-evidence/failing-cited-test.xml
new file mode 100644
index 00000000..16a82665
--- /dev/null
+++ b/tests/fixtures/frr-evidence/failing-cited-test.xml
@@ -0,0 +1,6 @@
+
+
+
+known-bad: a cited test failed
+
+
diff --git a/tests/fixtures/frr-evidence/passing.xml b/tests/fixtures/frr-evidence/passing.xml
new file mode 100644
index 00000000..9bf0cf71
--- /dev/null
+++ b/tests/fixtures/frr-evidence/passing.xml
@@ -0,0 +1,8 @@
+
+
+
+
+
+
+
+
diff --git a/tests/fixtures/frr/known-bad.json b/tests/fixtures/frr/known-bad.json
new file mode 100644
index 00000000..479aaa1f
--- /dev/null
+++ b/tests/fixtures/frr/known-bad.json
@@ -0,0 +1,33 @@
+{
+  "$comment": "Each case changes the committed data/frr-records.json in one way that must fail scripts/_frr.py for the stated reason. Applied by tests/test_frr_records.py.",
+  "cases": [
+    {"case": "missing record", "drop": "AFC-CSO-INB", "expect": "no record for 1 applicable rule(s): AFC-CSO-INB"},
+    {"case": "extra record (Rev5 agency path)", "add": {"frr_id": "FRC-APS-ATO", "status": "Not Implemented", "implementation": "x", "gap": "x", "closes_with": ["sam"]}, "expect": "FRC-APS-ATO is not a rule that applies"},
+    {"case": "duplicate record", "add": {"frr_id": "VDR-TFR-PVR", "status": "Not Implemented", "implementation": "x", "gap": "x", "closes_with": ["W7"]}, "expect": "duplicate record for VDR-TFR-PVR"},
+    {"case": "implemented without evidence", "replace": {"frr_id": "AFC-CSO-INB", "status": "Implemented", "implementation": "An inbox exists.", "evidence": []}, "expect": "AFC-CSO-INB: Implemented needs evidence that resolves"},
+    {"case": "test that does not exist", "replace": {"frr_id": "AFC-CSO-INB", "status": "Implemented", "implementation": "x", "evidence": [{"kind": "test", "ref": "tests/test_frr_records.py::test_the_inbox_receives_mail"}]}, "expect": "names no test function"},
+    {"case": "test file that does not exist", "replace": {"frr_id": "AFC-CSO-INB", "status": "Implemented", "implementation": "x", "evidence": [{"kind": "test", "ref": "tests/test_inbox.py::test_x"}]}, "expect": "tests/test_inbox.py does not exist"},
+    {"case": "workflow step that does not exist", "replace": {"frr_id": "AFC-CSO-INB", "status": "Implemented", "implementation": "x", "evidence": [{"kind": "step", "ref": "deploy-with-opa.yml#Check the FedRAMP Security Inbox"}]}, "expect": "no step named"},
+    {"case": "artifact not published", "replace": {"frr_id": "AFC-CSO-INB", "status": "Implemented", "implementation": "x", "evidence": [{"kind": "artifact", "ref": ".well-known/fedramp-inbox.json"}]}, "expect": "is not a freshness-governed published artifact"},
+    {"case": "decision not in force", "replace": {"frr_id": "AFC-CSO-INB", "status": "Implemented", "implementation": "x", "evidence": [{"kind": "decision", "ref": "DEC-999"}]}, "expect": "is not an in-force decision record"},
+    {"case": "unresolved evidence on a partial record", "replace": {"frr_id": "AFC-CSO-INB", "status": "Partially Implemented", "implementation": "x", "evidence": [{"kind": "decision", "ref": "DEC-999"}], "gap": "x", "closes_with": ["W9"]}, "expect": "does not resolve"},
+    {"case": "implemented with a gap", "replace": {"frr_id": "VDR-CSO-MSP", "status": "Implemented", "implementation": "x", "evidence": [{"kind": "decision", "ref": "DEC-039"}], "gap": "x"}, "expect": "an Implemented record has no gap"},
+    {"case": "partial without a gap", "replace": {"frr_id": "AFC-CSO-INB", "status": "Partially Implemented", "implementation": "x", "closes_with": ["W9"]}, "expect": "AFC-CSO-INB: gap must be a non-empty string"},
+    {"case": "partial with nothing closing it", "replace": {"frr_id": "AFC-CSO-INB", "status": "Partially Implemented", "implementation": "x", "gap": "x"}, "expect": "closes_with must be a non-empty list"},
+    {"case": "unknown workstream", "replace": {"frr_id": "AFC-CSO-INB", "status": "Not Implemented", "implementation": "x", "gap": "x", "closes_with": ["W11"]}, "expect": "closes_with must be a non-empty list"},
+    {"case": "Not Applicable on a rule FedRAMP scopes in", "replace": {"frr_id": "AFC-CSO-INB", "status": "Not Applicable", "implementation": "x", "not_applicable": "No mail is expected."}, "expect": "AFC-CSO-INB: cannot be Not Applicable"},
+    {"case": "Not Applicable without a reason", "replace": {"frr_id": "MKT-CSO-PML", "status": "Not Applicable", "implementation": "x"}, "expect": "MKT-CSO-PML: not_applicable must be a non-empty string"},
+    {"case": "Not Applicable with a gap", "replace": {"frr_id": "MKT-CSO-PML", "status": "Not Applicable", "implementation": "x", "not_applicable": "x", "gap": "x", "closes_with": ["sam"]}, "expect": "a Not Applicable record has no gap"},
+    {"case": "a reason for not applying on an applicable record", "replace": {"frr_id": "AFC-CSO-INB", "status": "Not Implemented", "implementation": "x", "gap": "x", "closes_with": ["W9"], "not_applicable": "x"}, "expect": "not_applicable is for Not Applicable records only"},
+    {"case": "optional is no longer a closer", "replace": {"frr_id": "AFC-CSO-INB", "status": "Not Implemented", "implementation": "x", "gap": "x", "closes_with": ["optional"]}, "expect": "closes_with must be a non-empty list"},
+    {"case": "unknown status", "replace": {"frr_id": "AFC-CSO-INB", "status": "Met", "implementation": "x"}, "expect": "status 'Met' is not one of"},
+    {"case": "unknown field", "replace": {"frr_id": "AFC-CSO-INB", "status": "Not Implemented", "implementation": "x", "gap": "x", "closes_with": ["W9"], "met": true}, "expect": "unknown field(s) ['met']"},
+    {"case": "account ID in published text", "replace": {"frr_id": "AFC-CSO-INB", "status": "Not Implemented", "implementation": "Bucket arn:aws:s3:us-east-1:111122223333:x", "gap": "x", "closes_with": ["W9"]}, "expect": "implementation carries an AWS account ID"},
+    {"case": "MAY rule without a rationale", "replace": {"frr_id": "VDR-CSO-SIR", "status": "Not Applicable", "implementation": "x", "not_applicable": "x"}, "expect": "VDR-CSO-SIR: may_rationale must be a non-empty string"},
+    {"case": "rationale on a MUST rule", "replace": {"frr_id": "AFC-CSO-INB", "status": "Not Implemented", "implementation": "x", "gap": "x", "closes_with": ["W9"], "may_rationale": "x"}, "expect": "may_rationale is for MAY rules only"},
+    {"case": "personal email in published text", "replace": {"frr_id": "AFC-CSO-INB", "status": "Not Implemented", "implementation": "x", "gap": "Mail goes to someone@example.com today.", "closes_with": ["W9"]}, "expect": "gap names an email address outside"},
+    {"case": "simulated on a partial record", "replace": {"frr_id": "AFC-CSO-INB", "status": "Partially Implemented", "implementation": "x", "gap": "x", "closes_with": ["W9"], "simulated": {"counterparty": "mail", "how": "x"}}, "expect": "simulated is for Implemented records only"},
+    {"case": "simulated with an unknown counterparty", "replace": {"frr_id": "VDR-CSO-MSP", "status": "Implemented", "implementation": "x", "evidence": [{"kind": "step", "ref": "deploy-with-opa.yml#Run OPA Compliance Check"}], "simulated": {"counterparty": "the-moon", "how": "x"}}, "expect": "simulated must be {counterparty: one of"},
+    {"case": "simulated without deploy-time evidence", "replace": {"frr_id": "VDR-CSO-MSP", "status": "Implemented", "implementation": "x", "evidence": [{"kind": "decision", "ref": "DEC-039"}], "simulated": {"counterparty": "assessor", "how": "x"}}, "expect": "a simulated counterparty needs deploy-time evidence"}
+  ]
+}
diff --git a/tests/fixtures/frr/line-pointer.json b/tests/fixtures/frr/line-pointer.json
new file mode 100644
index 00000000..aeea83ac
--- /dev/null
+++ b/tests/fixtures/frr/line-pointer.json
@@ -0,0 +1,8 @@
+{
+  "$comment": "Known-bad: record text that points at a line number. Line numbers move with every edit, so a record must name the function, step or resource instead (tests/test_frr_records.py::test_known_bad_a_line_number_pointer_is_found).",
+  "records": [
+    {"frr_id": "VDR-CSO-ADT", "implementation": "The runtime emitter runs on an EventBridge schedule (infrastructure/main.tf:809)."},
+    {"frr_id": "FRC-APP-FCP", "implementation": "Package artifacts regenerate on every deploy (deploy-with-opa.yml build steps ~L1558-1600)."},
+    {"frr_id": "VER-EVA-EFP", "implementation": "triage.rego:262 record_status rejects a false positive that names a control."}
+  ]
+}
diff --git a/tests/fixtures/fsi/notices-late.json b/tests/fixtures/fsi/notices-late.json
new file mode 100644
index 00000000..447cf796
--- /dev/null
+++ b/tests/fixtures/fsi/notices-late.json
@@ -0,0 +1,17 @@
+{
+  "$comment": "KNOWN-BAD: a previously published change notice filed 2026-12-03 for a change first published by the deploy of 2026-12-01 (a Tuesday): two business days after the publishing deploy, so the deploy must fail (AFC-CSO-NOC).",
+  "changeNotices": [
+    {
+      "changedOn": "2026-12-01",
+      "contact": "Simulated for this proof of concept: there is no FedRAMP Security Inbox. Hit me up on LinkedIn (new profile): https://www.linkedin.com/in/example/",
+      "publishedOn": "2026-12-01",
+      "publishedIn": "0000000000000000000000000000000000000001",
+      "filedOn": "2026-12-03",
+      "receipt": {
+        "receiptId": "SIM-NOC-000000000000",
+        "receivedBy": "FedRAMP (simulated): a Python function in this repository. Nothing left the building.",
+        "message": "Noted. Our records, which do not exist, have been updated."
+      }
+    }
+  ]
+}
diff --git a/tests/fixtures/fsi/offering-changed-hand-recorded.json b/tests/fixtures/fsi/offering-changed-hand-recorded.json
new file mode 100644
index 00000000..b099029e
--- /dev/null
+++ b/tests/fixtures/fsi/offering-changed-hand-recorded.json
@@ -0,0 +1,21 @@
+{
+  "fedramp_security_inbox": {
+    "contact": "Simulated for this proof of concept: there is no FedRAMP Security Inbox. Hit me up on LinkedIn (new profile): https://www.linkedin.com/in/example/",
+    "history": [
+      {
+        "contact": "Simulated for this proof of concept: there is no FedRAMP Security Inbox, no mail is received or sent, and the inbox is permanently at zero because it does not exist. Hit me up on LinkedIn: https://www.linkedin.com/in/sa2/",
+        "since": "2026-11-05",
+        "basis": "Established. No earlier FedRAMP Security Inbox or Marketplace Security Email is on file with FedRAMP for this unsponsored system, so there was no prior contact to change from."
+      },
+      {
+        "contact": "Simulated for this proof of concept: there is no FedRAMP Security Inbox. Hit me up on LinkedIn (new profile): https://www.linkedin.com/in/example/",
+        "since": "2026-12-01",
+        "fedramp_notified": {
+          "on": "2026-11-30",
+          "channel": "help.fedramp.gov [CSP] Notification of Changes form"
+        }
+      }
+    ]
+  },
+  "$comment": "KNOWN-BAD: the change hand-records a notice (fedramp_notified). The deploy files every notice with the simulated FedRAMP; a hand-written marker is a claim nothing checks, so it is refused."
+}
diff --git a/tests/fixtures/fsi/offering-changed-without-history.json b/tests/fixtures/fsi/offering-changed-without-history.json
new file mode 100644
index 00000000..d8cd2db8
--- /dev/null
+++ b/tests/fixtures/fsi/offering-changed-without-history.json
@@ -0,0 +1,12 @@
+{
+  "fedramp_security_inbox": {
+    "contact": "Simulated for this proof of concept: there is no FedRAMP Security Inbox. Hit me up on LinkedIn (new profile): https://www.linkedin.com/in/example/",
+    "history": [
+      {
+        "contact": "Simulated for this proof of concept: there is no FedRAMP Security Inbox, no mail is received or sent, and the inbox is permanently at zero because it does not exist. Hit me up on LinkedIn: https://www.linkedin.com/in/sa2/",
+        "since": "2026-11-05",
+        "basis": "Established. No earlier FedRAMP Security Inbox or Marketplace Security Email is on file with FedRAMP for this unsponsored system, so there was no prior contact to change from."
+      }
+    ]
+  }
+}
diff --git a/tests/fixtures/fsi/offering-changed.json b/tests/fixtures/fsi/offering-changed.json
new file mode 100644
index 00000000..c4fb070a
--- /dev/null
+++ b/tests/fixtures/fsi/offering-changed.json
@@ -0,0 +1,16 @@
+{
+  "fedramp_security_inbox": {
+    "contact": "Simulated for this proof of concept: there is no FedRAMP Security Inbox. Hit me up on LinkedIn (new profile): https://www.linkedin.com/in/example/",
+    "history": [
+      {
+        "contact": "Simulated for this proof of concept: there is no FedRAMP Security Inbox, no mail is received or sent, and the inbox is permanently at zero because it does not exist. Hit me up on LinkedIn: https://www.linkedin.com/in/sa2/",
+        "since": "2026-11-05",
+        "basis": "Established. No earlier FedRAMP Security Inbox or Marketplace Security Email is on file with FedRAMP for this unsponsored system, so there was no prior contact to change from."
+      },
+      {
+        "contact": "Simulated for this proof of concept: there is no FedRAMP Security Inbox. Hit me up on LinkedIn (new profile): https://www.linkedin.com/in/example/",
+        "since": "2026-12-01"
+      }
+    ]
+  }
+}
diff --git a/tests/fixtures/fsi/simulation-wrong-expectation.json b/tests/fixtures/fsi/simulation-wrong-expectation.json
new file mode 100644
index 00000000..cad4d96b
--- /dev/null
+++ b/tests/fixtures/fsi/simulation-wrong-expectation.json
@@ -0,0 +1,366 @@
+{
+  "_note": "KNOWN-BAD FIXTURE (tests/test_fedramp_inbox.py): identical to data/fsi-simulation/messages.json except that the forged @gsa.gov message is expected to be acknowledged. The simulation must fail on it, because an unauthenticated message is never acknowledged.",
+  "inbox": "fedramp-security-inbox@simulation.invalid",
+  "register_check": {
+    "now": "2026-11-06T17:00:00Z",
+    "expected_overdue": [
+      "sim-ack-send-fails",
+      "sim-emergency-other-sender",
+      "sim-emergency-test",
+      "sim-forged-gsa"
+    ],
+    "expected_retry": {
+      "acknowledgements_sent_again": 1,
+      "pages_sent_again": 0
+    },
+    "important_case": "sim-important",
+    "important_respond_by": "2026-11-10T22:00:00Z",
+    "later": "2026-11-09T21:00:00Z",
+    "emergency_case": "sim-emergency-test",
+    "untriaged_important_case": "sim-envelope-only"
+  },
+  "messages": [
+    {
+      "case": "emergency-test",
+      "description": "Emergency Test from FedRAMP's Emergency sender (AFC-FRP-UFS), authenticated",
+      "message_id": "sim-emergency-test",
+      "received_at": "2026-11-06T14:05:00Z",
+      "from": "FedRAMP Security ",
+      "envelope": "fedramp_security@fedramp.gov",
+      "subject": "EMERGENCY TEST: FedRAMP Security Inbox exercise",
+      "headers": {
+        "Message-ID": ""
+      },
+      "auth": {
+        "spf": "PASS",
+        "dkim": "PASS",
+        "dmarc": "PASS"
+      },
+      "expected": {
+        "kind": "fedramp",
+        "designation": "EMERGENCY_TEST",
+        "sender_domain": "fedramp.gov",
+        "authenticated": true,
+        "emergency_sender_ok": true,
+        "ack": "sent",
+        "in_reply_to": true,
+        "page": true,
+        "triage_by": "2026-11-06T16:05:00Z",
+        "respond_by": "2026-11-09T20:00:00Z"
+      }
+    },
+    {
+      "case": "important",
+      "description": "Important message whose subject and Message-ID try to inject a Bcc header",
+      "message_id": "sim-important",
+      "received_at": "2026-11-06T14:10:00Z",
+      "from": "FedRAMP PMO ",
+      "envelope": "info@fedramp.gov",
+      "subject": "IMPORTANT: action requested\r\nBcc: injected@attacker.invalid",
+      "headers": {
+        "Message-ID": "\r\nBcc: injected@attacker.invalid"
+      },
+      "auth": {
+        "spf": "PASS",
+        "dkim": "PASS",
+        "dmarc": "PASS"
+      },
+      "expected": {
+        "kind": "fedramp",
+        "designation": "IMPORTANT",
+        "sender_domain": "fedramp.gov",
+        "authenticated": true,
+        "emergency_sender_ok": null,
+        "ack": "sent",
+        "in_reply_to": false,
+        "page": true,
+        "triage_by": "2026-11-07T14:10:00Z",
+        "respond_by": null
+      }
+    },
+    {
+      "case": "general",
+      "description": "General communication from @gsa.gov, no designator",
+      "message_id": "sim-general",
+      "received_at": "2026-11-06T14:15:00Z",
+      "from": "info@gsa.gov",
+      "envelope": "info@gsa.gov",
+      "subject": "FedRAMP program update",
+      "headers": {
+        "Message-ID": ""
+      },
+      "auth": {
+        "spf": "PASS",
+        "dkim": "PASS",
+        "dmarc": "PASS"
+      },
+      "expected": {
+        "kind": "fedramp",
+        "designation": "GENERAL",
+        "sender_domain": "gsa.gov",
+        "authenticated": true,
+        "emergency_sender_ok": null,
+        "ack": "sent",
+        "in_reply_to": true,
+        "page": true,
+        "triage_by": "2026-11-09T14:15:00Z",
+        "respond_by": null
+      }
+    },
+    {
+      "case": "forged-gsa",
+      "description": "Forged Emergency claiming to be from the gsa.gov Emergency sender; SPF, DKIM and DMARC fail. Still FedRAMP by default (AFC-CSO-TFG) and paged, but not acknowledged",
+      "message_id": "sim-forged-gsa",
+      "received_at": "2026-11-06T14:20:00Z",
+      "from": "FedRAMP Security ",
+      "envelope": "bounce@attacker.invalid",
+      "subject": "EMERGENCY: reply with your credentials",
+      "headers": {
+        "Message-ID": ""
+      },
+      "auth": {
+        "spf": "FAIL",
+        "dkim": "FAIL",
+        "dmarc": "FAIL"
+      },
+      "expected": {
+        "kind": "fedramp",
+        "designation": "EMERGENCY",
+        "sender_domain": "gsa.gov",
+        "authenticated": false,
+        "emergency_sender_ok": true,
+        "ack": "sent",
+        "in_reply_to": null,
+        "page": true,
+        "triage_by": "2026-11-06T16:20:00Z",
+        "respond_by": "2026-11-09T20:00:00Z"
+      }
+    },
+    {
+      "case": "auto-reply",
+      "description": "An auto-reply from @fedramp.gov: registered, never answered (no mail loop)",
+      "message_id": "sim-auto-reply",
+      "received_at": "2026-11-06T14:25:00Z",
+      "from": "info@fedramp.gov",
+      "envelope": "info@fedramp.gov",
+      "subject": "Automatic reply: Received: FedRAMP Security Inbox exercise",
+      "headers": {
+        "Auto-Submitted": "auto-replied",
+        "Message-ID": ""
+      },
+      "auth": {
+        "spf": "PASS",
+        "dkim": "PASS",
+        "dmarc": "PASS"
+      },
+      "expected": {
+        "kind": "fedramp",
+        "designation": "GENERAL",
+        "sender_domain": "fedramp.gov",
+        "authenticated": true,
+        "emergency_sender_ok": null,
+        "ack": "suppressed:auto-submitted",
+        "in_reply_to": null,
+        "page": true,
+        "triage_by": "2026-11-09T14:25:00Z",
+        "respond_by": null
+      }
+    },
+    {
+      "case": "look-alike",
+      "description": "Emergency from a look-alike domain (fedramp.gov.attacker.invalid): not FedRAMP, exact domains only",
+      "message_id": "sim-look-alike",
+      "received_at": "2026-11-06T14:30:00Z",
+      "from": "fedramp_security@fedramp.gov.attacker.invalid",
+      "envelope": "fedramp_security@fedramp.gov.attacker.invalid",
+      "subject": "EMERGENCY: act now",
+      "headers": {},
+      "auth": {
+        "spf": "PASS",
+        "dkim": "PASS",
+        "dmarc": "PASS"
+      },
+      "expected": {
+        "kind": "other",
+        "designation": "GENERAL",
+        "sender_domain": "fedramp.gov.attacker.invalid",
+        "authenticated": true,
+        "emergency_sender_ok": null,
+        "ack": "none",
+        "in_reply_to": null,
+        "page": false,
+        "triage_by": null,
+        "respond_by": null
+      }
+    },
+    {
+      "case": "display-name-spoof",
+      "description": "Display name impersonates the gsa.gov Emergency sender, actual address does not: not FedRAMP",
+      "message_id": "sim-display-name-spoof",
+      "received_at": "2026-11-06T14:35:00Z",
+      "from": "\"fedramp_security@gsa.gov\" ",
+      "envelope": "attacker@attacker.invalid",
+      "subject": "EMERGENCY: trust me",
+      "headers": {},
+      "auth": {
+        "spf": "PASS",
+        "dkim": "PASS",
+        "dmarc": "PASS"
+      },
+      "expected": {
+        "kind": "other",
+        "designation": "GENERAL",
+        "sender_domain": "attacker.invalid",
+        "authenticated": true,
+        "emergency_sender_ok": null,
+        "ack": "none",
+        "in_reply_to": null,
+        "page": false,
+        "triage_by": null,
+        "respond_by": null
+      }
+    },
+    {
+      "case": "envelope-only",
+      "description": "Unreadable From header, @gsa.gov envelope sender: still FedRAMP, registered and paged; no reply without a From address",
+      "message_id": "sim-envelope-only",
+      "received_at": "2026-11-06T14:40:00Z",
+      "from": "garbage <<>>",
+      "envelope": "bounces@gsa.gov",
+      "subject": "Important: please confirm",
+      "headers": {},
+      "auth": {
+        "spf": "PASS",
+        "dkim": "PASS",
+        "dmarc": "PASS"
+      },
+      "expected": {
+        "kind": "fedramp",
+        "designation": "IMPORTANT",
+        "sender_domain": "gsa.gov",
+        "authenticated": true,
+        "emergency_sender_ok": null,
+        "ack": "suppressed:no-from-address",
+        "in_reply_to": null,
+        "page": true,
+        "triage_by": "2026-11-07T14:40:00Z",
+        "respond_by": null
+      }
+    },
+    {
+      "case": "emergency-other-sender",
+      "description": "Emergency from an @gsa.gov address other than the designated Emergency senders (AFC-FRP-UFS): flagged, not demoted, still paged",
+      "message_id": "sim-emergency-other-sender",
+      "received_at": "2026-11-06T14:45:00Z",
+      "from": "Someone ",
+      "envelope": "someone@gsa.gov",
+      "subject": "EMERGENCY: rotate your keys",
+      "headers": {
+        "Message-ID": ""
+      },
+      "auth": {
+        "spf": "PASS",
+        "dkim": "PASS",
+        "dmarc": "PASS"
+      },
+      "expected": {
+        "kind": "fedramp",
+        "designation": "EMERGENCY",
+        "sender_domain": "gsa.gov",
+        "authenticated": true,
+        "emergency_sender_ok": false,
+        "ack": "sent",
+        "in_reply_to": true,
+        "page": true,
+        "triage_by": "2026-11-06T16:45:00Z",
+        "respond_by": "2026-11-09T20:00:00Z"
+      }
+    },
+    {
+      "case": "bulk",
+      "description": "Bulk mail from @gsa.gov: registered, not answered",
+      "message_id": "sim-bulk",
+      "received_at": "2026-11-06T14:50:00Z",
+      "from": "news@gsa.gov",
+      "envelope": "news@gsa.gov",
+      "subject": "Newsletter",
+      "headers": {
+        "Precedence": "bulk"
+      },
+      "auth": {
+        "spf": "PASS",
+        "dkim": "PASS",
+        "dmarc": "PASS"
+      },
+      "expected": {
+        "kind": "fedramp",
+        "designation": "GENERAL",
+        "sender_domain": "gsa.gov",
+        "authenticated": true,
+        "emergency_sender_ok": null,
+        "ack": "suppressed:precedence",
+        "in_reply_to": null,
+        "page": true,
+        "triage_by": "2026-11-09T14:50:00Z",
+        "respond_by": null
+      }
+    },
+    {
+      "case": "bounce",
+      "description": "A bounce (null envelope sender) from @gsa.gov: registered, not answered",
+      "message_id": "sim-bounce",
+      "received_at": "2026-11-06T14:55:00Z",
+      "from": "mailer-daemon@gsa.gov",
+      "envelope": "<>",
+      "subject": "Undeliverable: Received: FedRAMP program update",
+      "headers": {},
+      "auth": {
+        "spf": "PASS",
+        "dkim": "PASS",
+        "dmarc": "PASS"
+      },
+      "expected": {
+        "kind": "fedramp",
+        "designation": "GENERAL",
+        "sender_domain": "gsa.gov",
+        "authenticated": true,
+        "emergency_sender_ok": null,
+        "ack": "suppressed:null-sender",
+        "in_reply_to": null,
+        "page": true,
+        "triage_by": "2026-11-09T14:55:00Z",
+        "respond_by": null
+      }
+    },
+    {
+      "case": "ack-send-fails",
+      "description": "The first acknowledgement attempt fails: recorded as failed, reported overdue, and sent exactly once on the retry",
+      "message_id": "sim-ack-send-fails",
+      "received_at": "2026-11-06T15:00:00Z",
+      "simulate_send_failure": true,
+      "from": "info@fedramp.gov",
+      "envelope": "info@fedramp.gov",
+      "subject": "Checking in",
+      "headers": {
+        "Message-ID": ""
+      },
+      "auth": {
+        "spf": "PASS",
+        "dkim": "PASS",
+        "dmarc": "PASS"
+      },
+      "expected": {
+        "kind": "fedramp",
+        "designation": "GENERAL",
+        "sender_domain": "fedramp.gov",
+        "authenticated": true,
+        "emergency_sender_ok": null,
+        "ack": "failed",
+        "in_reply_to": null,
+        "page": true,
+        "triage_by": "2026-11-09T15:00:00Z",
+        "respond_by": null
+      }
+    }
+  ]
+}
diff --git a/tests/fixtures/gates/gate-modes-marking.json b/tests/fixtures/gates/gate-modes-marking.json
new file mode 100644
index 00000000..0b62d7b4
--- /dev/null
+++ b/tests/fixtures/gates/gate-modes-marking.json
@@ -0,0 +1,328 @@
+{
+  "$schema": "./gate-modes.schema.json",
+  "version": "2026-11-06.1",
+  "description": "Known-bad: a confirmation note in the reason instead of the confirmed_on field.",
+  "method_reference": "website/research/vulnerability-evidence.html#gates",
+  "checks": [
+    {
+      "check": "vdr.kev",
+      "gate": "G1",
+      "mode": "block",
+      "method_default": "block",
+      "reason": "Proposed; confirm at review. Stricter than the method. G1 blocks every known-exploited finding, dispositioned or not, from the first evaluation; the method blocks only once the KEV due date has passed or when a new resource would deploy with one.",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "vdr.top-impact-lev-irv",
+      "gate": "G2",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "vdr.past-deadline",
+      "gate": "G3",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "vuln-gate.unhandled",
+      "gate": "G3",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "runtime-divergence.diverged",
+      "gate": "G4",
+      "mode": "block",
+      "method_default": "block",
+      "reason": "A deploy may proceed past a fresh divergence only with --allow-divergence and a stated reason, which the deploy log records (break-glass for a deploy that is itself the fix).",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.a",
+      "gate": "G4",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.b",
+      "gate": "G5",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.c",
+      "gate": "G5",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.d",
+      "gate": "G5",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.h",
+      "gate": "G5",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.i",
+      "gate": "G5",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.j",
+      "gate": "G5",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.e",
+      "gate": "G6",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.f",
+      "gate": "G6",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.l",
+      "gate": "G6",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.m",
+      "gate": "G5",
+      "mode": "block",
+      "method_default": "block",
+      "reason": "An open incident naming a finding the VDR does not carry blocks, like every other cross-artifact invariant.",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-05",
+      "review_by": "2027-11-05",
+      "confirmed_on": "2026-11-06",
+      "drafted_by": "AI-drafted (Claude), with the incident register"
+    },
+    {
+      "check": "reconcile.i.unreadable",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "reason": "Was a rollout-time warning while the roles lacked tag:GetResources. Both roles now read tags (the deploy and the nightly both report invariant i checked), so a denied read is a detection failure and blocks.",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "runtime-divergence.observer-fault",
+      "gate": "G7",
+      "mode": "detect-and-recover",
+      "method_default": "block",
+      "reason": "The runtime evaluator could not reach a verdict: its signal is unreadable, stale, undated, degraded or has no divergence block. Blocking deploys on it would also block the deploy that repairs the evaluator. The fault is published in the runtime signal and queued by the trust center (runtime_unassessed, runtime_stale) with its opening time.",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-05-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.zap.missing",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.zap.stale",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.kev",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.epss",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.grype",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.dependabot",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.previous-vdr",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.checkov",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.tfsec",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.codeql",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-05",
+      "review_by": "2027-11-05",
+      "confirmed_on": "2026-11-05"
+    },
+    {
+      "check": "detection.zap-api",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-05",
+      "review_by": "2027-11-05",
+      "confirmed_on": "2026-11-05"
+    },
+    {
+      "check": "vdr.coverage",
+      "gate": "G7",
+      "mode": "detect-and-recover",
+      "method_default": "block",
+      "reason": "An inventory component with no detection technique in the last month (VDR-TFR-PCD) is a gap in detection, not a vulnerability in what is deployed; blocking would also block the deploy that adds the detection. The gap becomes a process finding (VDR-CSO-FAV) with a clock and a deadline, published in the VDR until coverage returns.",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-05",
+      "review_by": "2027-05-05",
+      "confirmed_on": "2026-11-06",
+      "drafted_by": "AI-drafted (Claude)"
+    },
+    {
+      "check": "vdr.unresolved-component",
+      "gate": "G7",
+      "mode": "detect-and-recover",
+      "method_default": "block",
+      "reason": "A finding that resolves to no inventory component is rated at the fail-safe (internet-reachable, most sensitive) until it is resolved (VER-EVA-EIR); blocking would also block the inventory change that resolves it. The unresolved evaluation becomes a process finding (VDR-CSO-FAV) with a clock and a deadline until every finding resolves.",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-05",
+      "review_by": "2027-05-05",
+      "confirmed_on": "2026-11-06",
+      "drafted_by": "AI-drafted (Claude)"
+    }
+  ]
+}
diff --git a/tests/fixtures/gates/gate-modes-unconfirmed.json b/tests/fixtures/gates/gate-modes-unconfirmed.json
new file mode 100644
index 00000000..defeba9f
--- /dev/null
+++ b/tests/fixtures/gates/gate-modes-unconfirmed.json
@@ -0,0 +1,327 @@
+{
+  "$schema": "./gate-modes.schema.json",
+  "version": "2026-11-06.1",
+  "description": "Known-bad: the committed register with vdr.kev not confirmed by the operator (no confirmed_on). A gate mode the operator has not confirmed cannot be in force; the build stops.",
+  "method_reference": "website/research/vulnerability-evidence.html#gates",
+  "checks": [
+    {
+      "check": "vdr.kev",
+      "gate": "G1",
+      "mode": "block",
+      "method_default": "block",
+      "reason": "Stricter than the method. G1 blocks every known-exploited finding, dispositioned or not, from the first evaluation; the method blocks only once the KEV due date has passed or when a new resource would deploy with one.",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04"
+    },
+    {
+      "check": "vdr.top-impact-lev-irv",
+      "gate": "G2",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "vdr.past-deadline",
+      "gate": "G3",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "vuln-gate.unhandled",
+      "gate": "G3",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "runtime-divergence.diverged",
+      "gate": "G4",
+      "mode": "block",
+      "method_default": "block",
+      "reason": "A deploy may proceed past a fresh divergence only with --allow-divergence and a stated reason, which the deploy log records (break-glass for a deploy that is itself the fix).",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.a",
+      "gate": "G4",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.b",
+      "gate": "G5",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.c",
+      "gate": "G5",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.d",
+      "gate": "G5",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.h",
+      "gate": "G5",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.i",
+      "gate": "G5",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.j",
+      "gate": "G5",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.e",
+      "gate": "G6",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.f",
+      "gate": "G6",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.l",
+      "gate": "G6",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "reconcile.m",
+      "gate": "G5",
+      "mode": "block",
+      "method_default": "block",
+      "reason": "An open incident naming a finding the VDR does not carry blocks, like every other cross-artifact invariant.",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-05",
+      "review_by": "2027-11-05",
+      "confirmed_on": "2026-11-06",
+      "drafted_by": "AI-drafted (Claude), with the incident register"
+    },
+    {
+      "check": "reconcile.i.unreadable",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "reason": "Was a rollout-time warning while the roles lacked tag:GetResources. Both roles now read tags (the deploy and the nightly both report invariant i checked), so a denied read is a detection failure and blocks.",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "runtime-divergence.observer-fault",
+      "gate": "G7",
+      "mode": "detect-and-recover",
+      "method_default": "block",
+      "reason": "The runtime evaluator could not reach a verdict: its signal is unreadable, stale, undated, degraded or has no divergence block. Blocking deploys on it would also block the deploy that repairs the evaluator. The fault is published in the runtime signal and queued by the trust center (runtime_unassessed, runtime_stale) with its opening time.",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-05-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.zap.missing",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.zap.stale",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.kev",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.epss",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.grype",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.dependabot",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.previous-vdr",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.checkov",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.tfsec",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-04",
+      "review_by": "2027-11-04",
+      "confirmed_on": "2026-11-04"
+    },
+    {
+      "check": "detection.codeql",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-05",
+      "review_by": "2027-11-05",
+      "confirmed_on": "2026-11-05"
+    },
+    {
+      "check": "detection.zap-api",
+      "gate": "G7",
+      "mode": "block",
+      "method_default": "block",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-05",
+      "review_by": "2027-11-05",
+      "confirmed_on": "2026-11-05"
+    },
+    {
+      "check": "vdr.coverage",
+      "gate": "G7",
+      "mode": "detect-and-recover",
+      "method_default": "block",
+      "reason": "An inventory component with no detection technique in the last month (VDR-TFR-PCD) is a gap in detection, not a vulnerability in what is deployed; blocking would also block the deploy that adds the detection. The gap becomes a process finding (VDR-CSO-FAV) with a clock and a deadline, published in the VDR until coverage returns.",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-05",
+      "review_by": "2027-05-05",
+      "confirmed_on": "2026-11-06",
+      "drafted_by": "AI-drafted (Claude)"
+    },
+    {
+      "check": "vdr.unresolved-component",
+      "gate": "G7",
+      "mode": "detect-and-recover",
+      "method_default": "block",
+      "reason": "A finding that resolves to no inventory component is rated at the fail-safe (internet-reachable, most sensitive) until it is resolved (VER-EVA-EIR); blocking would also block the inventory change that resolves it. The unresolved evaluation becomes a process finding (VDR-CSO-FAV) with a clock and a deadline until every finding resolves.",
+      "decided_by": "Sam Aydlette",
+      "decided_on": "2026-11-05",
+      "review_by": "2027-05-05",
+      "confirmed_on": "2026-11-06",
+      "drafted_by": "AI-drafted (Claude)"
+    }
+  ]
+}
diff --git a/tests/fixtures/gates/gate-modes-undecided.json b/tests/fixtures/gates/gate-modes-undecided.json
index 7daba73a..86f94175 100644
--- a/tests/fixtures/gates/gate-modes-undecided.json
+++ b/tests/fixtures/gates/gate-modes-undecided.json
@@ -11,7 +11,7 @@
       "method_default": "block",
       "reason": "Stricter than the method. G1 blocks every known-exploited finding, dispositioned or not, from the first evaluation; the method blocks only once the KEV due date has passed or when a new resource would deploy with one.",
       "decided_by": "Sam Aydlette",
-      "decided_on": "2026-11-04",
+      "decided_on": "2026-11-04", "confirmed_on": "2026-11-04",
       "review_by": "2027-11-04"
     },
     {
@@ -20,7 +20,7 @@
       "mode": "block",
       "method_default": "block",
       "decided_by": "Sam Aydlette",
-      "decided_on": "2026-11-04",
+      "decided_on": "2026-11-04", "confirmed_on": "2026-11-04",
       "review_by": "2027-11-04"
     },
     {
@@ -29,7 +29,7 @@
       "mode": "detect-and-recover",
       "method_default": "block",
       "decided_by": "Sam Aydlette",
-      "decided_on": "2026-11-04",
+      "decided_on": "2026-11-04", "confirmed_on": "2026-11-04",
       "review_by": "2027-11-04"
     },
     {
@@ -38,7 +38,7 @@
       "mode": "block",
       "method_default": "block",
       "decided_by": "Sam Aydlette",
-      "decided_on": "2026-11-04",
+      "decided_on": "2026-11-04", "confirmed_on": "2026-11-04",
       "review_by": "2027-11-04"
     },
     {
@@ -48,7 +48,7 @@
       "method_default": "block",
       "reason": "A deploy may proceed past a fresh divergence only with --allow-divergence and a stated reason, which the deploy log records (break-glass for a deploy that is itself the fix).",
       "decided_by": "Sam Aydlette",
-      "decided_on": "2026-11-04",
+      "decided_on": "2026-11-04", "confirmed_on": "2026-11-04",
       "review_by": "2027-11-04"
     },
     {
@@ -57,7 +57,7 @@
       "mode": "block",
       "method_default": "block",
       "decided_by": "Sam Aydlette",
-      "decided_on": "2026-11-04",
+      "decided_on": "2026-11-04", "confirmed_on": "2026-11-04",
       "review_by": "2027-11-04"
     },
     {
@@ -66,7 +66,7 @@
       "mode": "block",
       "method_default": "block",
       "decided_by": "Sam Aydlette",
-      "decided_on": "2026-11-04",
+      "decided_on": "2026-11-04", "confirmed_on": "2026-11-04",
       "review_by": "2027-11-04"
     },
     {
@@ -75,7 +75,7 @@
       "mode": "block",
       "method_default": "block",
       "decided_by": "Sam Aydlette",
-      "decided_on": "2026-11-04",
+      "decided_on": "2026-11-04", "confirmed_on": "2026-11-04",
       "review_by": "2027-11-04"
     },
     {
@@ -84,7 +84,7 @@
       "mode": "block",
       "method_default": "block",
       "decided_by": "Sam Aydlette",
-      "decided_on": "2026-11-04",
+      "decided_on": "2026-11-04", "confirmed_on": "2026-11-04",
       "review_by": "2027-11-04"
     },
     {
@@ -93,7 +93,7 @@
       "mode": "block",
       "method_default": "block",
       "decided_by": "Sam Aydlette",
-      "decided_on": "2026-11-04",
+      "decided_on": "2026-11-04", "confirmed_on": "2026-11-04",
       "review_by": "2027-11-04"
     },
     {
@@ -102,7 +102,7 @@
       "mode": "block",
       "method_default": "block",
       "decided_by": "Sam Aydlette",
-      "decided_on": "2026-11-04",
+      "decided_on": "2026-11-04", "confirmed_on": "2026-11-04",
       "review_by": "2027-11-04"
     },
     {
@@ -111,7 +111,7 @@
       "mode": "block",
       "method_default": "block",
       "decided_by": "Sam Aydlette",
-      "decided_on": "2026-11-04",
+      "decided_on": "2026-11-04", "confirmed_on": "2026-11-04",
       "review_by": "2027-11-04"
     },
     {
@@ -120,7 +120,7 @@
       "mode": "block",
       "method_default": "block",
       "decided_by": "Sam Aydlette",
-      "decided_on": "2026-11-04",
+      "decided_on": "2026-11-04", "confirmed_on": "2026-11-04",
       "review_by": "2027-11-04"
     },
     {
@@ -129,7 +129,7 @@
       "mode": "block",
       "method_default": "block",
       "decided_by": "Sam Aydlette",
-      "decided_on": "2026-11-04",
+      "decided_on": "2026-11-04", "confirmed_on": "2026-11-04",
       "review_by": "2027-11-04"
     },
     {
@@ -138,7 +138,7 @@
       "mode": "block",
       "method_default": "block",
       "decided_by": "Sam Aydlette",
-      "decided_on": "2026-11-04",
+      "decided_on": "2026-11-04", "confirmed_on": "2026-11-04",
       "review_by": "2027-11-04"
     },
     {
@@ -148,7 +148,7 @@
       "method_default": "block",
       "reason": "Was a rollout-time warning while the roles lacked tag:GetResources. Both roles now read tags (the deploy and the nightly both report invariant i checked), so a denied read is a detection failure and blocks.",
       "decided_by": "Sam Aydlette",
-      "decided_on": "2026-11-04",
+      "decided_on": "2026-11-04", "confirmed_on": "2026-11-04",
       "review_by": "2027-11-04"
     },
     {
@@ -158,7 +158,7 @@
       "method_default": "block",
       "reason": "The runtime evaluator could not reach a verdict: its signal is unreadable, stale, undated, degraded or has no divergence block. Blocking deploys on it would also block the deploy that repairs the evaluator. The fault is published in the runtime signal and queued by the trust center (runtime_unassessed, runtime_stale) with its opening time.",
       "decided_by": "Sam Aydlette",
-      "decided_on": "2026-11-04",
+      "decided_on": "2026-11-04", "confirmed_on": "2026-11-04",
       "review_by": "2027-05-04"
     },
     {
@@ -168,7 +168,7 @@
       "method_default": "block",
       "reason": "No DAST report reaches the build yet. The weekly ZAP scan is being wired into the nightly and the deploy; when it lands, this returns to block. Until then a missing report is published in the status beacon and queued.",
       "decided_by": "Sam Aydlette",
-      "decided_on": "2026-11-04",
+      "decided_on": "2026-11-04", "confirmed_on": "2026-11-04",
       "review_by": "2026-12-04"
     },
     {
@@ -177,7 +177,7 @@
       "mode": "block",
       "method_default": "block",
       "decided_by": "Sam Aydlette",
-      "decided_on": "2026-11-04",
+      "decided_on": "2026-11-04", "confirmed_on": "2026-11-04",
       "review_by": "2027-11-04"
     }
   ]
diff --git a/tests/fixtures/history-fetch/http-500.json b/tests/fixtures/history-fetch/http-500.json
new file mode 100644
index 00000000..082fa41a
--- /dev/null
+++ b/tests/fixtures/history-fetch/http-500.json
@@ -0,0 +1,5 @@
+{
+  "$comment": "KNOWN-BAD: the site answers 500 for the previously published history. Starting over from nothing would silently drop the history, so the fetch must fail the deploy.",
+  "status": 500,
+  "body": "Internal Server Error"
+}
diff --git a/tests/fixtures/history-fetch/truncated-200.json b/tests/fixtures/history-fetch/truncated-200.json
new file mode 100644
index 00000000..65cc5bdc
--- /dev/null
+++ b/tests/fixtures/history-fetch/truncated-200.json
@@ -0,0 +1,5 @@
+{
+  "$comment": "KNOWN-BAD: a 200 whose body was cut off mid-document. Treating it as empty would silently drop the history, so the fetch must fail the deploy.",
+  "status": 200,
+  "body": "{\"schema\": \"package-submission-log/1\", \"entries\": [{\"submittedAt\": \"2026-11-0"
+}
diff --git a/tests/fixtures/human-views/original.json b/tests/fixtures/human-views/original.json
new file mode 100644
index 00000000..43e7ec18
--- /dev/null
+++ b/tests/fixtures/human-views/original.json
@@ -0,0 +1 @@
+{"schema": "x/1", "count": 2, "items": [{"id": "A|B", "ok": true}, {"id": "C", "ok": null}], "empty": {}, "list": [], "0": "numeric key"}
diff --git a/tests/fixtures/human-views/original.view.tampered.md b/tests/fixtures/human-views/original.view.tampered.md
new file mode 100644
index 00000000..e57139e5
--- /dev/null
+++ b/tests/fixtures/human-views/original.view.tampered.md
@@ -0,0 +1,45 @@
+# original.json: complete human-readable view
+
+_Every value in `original.json`, under its JSON Pointer path; each value is shown in its JSON encoding. Generated from the signed original by scripts/build-human-views.py, and checked on every build to reproduce it exactly._
+
+- **Format:** json
+
+## schema
+
+| Path | Value |
+|---|---|
+| `/schema` | "x/1" |
+
+## count
+
+| Path | Value |
+|---|---|
+| `/count` | 3 |
+
+## items
+
+| Path | Value |
+|---|---|
+| `/items/0/id` | "A\|B" |
+| `/items/0/ok` | true |
+| `/items/1/id` | "C" |
+| `/items/1/ok` | null |
+
+## empty
+
+| Path | Value |
+|---|---|
+| `/empty` | {} |
+
+## list
+
+| Path | Value |
+|---|---|
+| `/list` | [] |
+
+## 0
+
+| Path | Value |
+|---|---|
+| `/0` | "numeric key" |
+
diff --git a/tests/fixtures/human-views/publish-without-view.sh b/tests/fixtures/human-views/publish-without-view.sh
new file mode 100644
index 00000000..6a5c973a
--- /dev/null
+++ b/tests/fixtures/human-views/publish-without-view.sh
@@ -0,0 +1,16 @@
+# KNOWN-BAD (tests/test_human_views_published.py): an incident publish step that
+# puts each per-incident report and its signature but not its human-readable
+# view, so the trust manifest's "every JSON has a .view.md" would be false.
+set -euo pipefail
+put() {
+  aws s3api put-object --bucket "${SITE_BUCKET:-stub}" --key ".well-known/$1" --body "$1" \
+    --content-type "$2" --cache-control "public, max-age=300" --query 'ETag' --output text > /dev/null
+}
+for f in incident-INC-*.json; do
+  put "$f" "application/json"
+  put "${f%.json}.bundle" "application/json"
+done
+put incident-deliveries.view.md "text/markdown; charset=utf-8"
+put incident-deliveries.json "application/json"
+put incident-reports.view.md "text/markdown; charset=utf-8"
+put incident-reports.json "application/json"
diff --git a/tests/fixtures/hygiene/uncalled-script/.github/workflows/deploy.yml b/tests/fixtures/hygiene/uncalled-script/.github/workflows/deploy.yml
new file mode 100644
index 00000000..154e6879
--- /dev/null
+++ b/tests/fixtures/hygiene/uncalled-script/.github/workflows/deploy.yml
@@ -0,0 +1,7 @@
+# Known-bad fixture workflow: runs build-used.py only.
+on: push
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - run: python3 scripts/build-used.py
diff --git a/tests/fixtures/hygiene/uncalled-script/scripts/README.md b/tests/fixtures/hygiene/uncalled-script/scripts/README.md
new file mode 100644
index 00000000..4ecdb81c
--- /dev/null
+++ b/tests/fixtures/hygiene/uncalled-script/scripts/README.md
@@ -0,0 +1 @@
+Known-bad fixture for tests/test_repo_hygiene.py: build-orphan.py and _orphan_helper.py have no caller.
diff --git a/tests/fixtures/hygiene/uncalled-script/scripts/_orphan_helper.py b/tests/fixtures/hygiene/uncalled-script/scripts/_orphan_helper.py
new file mode 100644
index 00000000..bf0e1868
--- /dev/null
+++ b/tests/fixtures/hygiene/uncalled-script/scripts/_orphan_helper.py
@@ -0,0 +1 @@
+"""Known-bad fixture: NOT called: only the orphan would import it, and it does not."""
diff --git a/tests/fixtures/hygiene/uncalled-script/scripts/_used_helper.py b/tests/fixtures/hygiene/uncalled-script/scripts/_used_helper.py
new file mode 100644
index 00000000..bde45f04
--- /dev/null
+++ b/tests/fixtures/hygiene/uncalled-script/scripts/_used_helper.py
@@ -0,0 +1 @@
+"""Known-bad fixture: imported by build-used.py."""
diff --git a/tests/fixtures/hygiene/uncalled-script/scripts/build-orphan.py b/tests/fixtures/hygiene/uncalled-script/scripts/build-orphan.py
new file mode 100644
index 00000000..e1d24ac6
--- /dev/null
+++ b/tests/fixtures/hygiene/uncalled-script/scripts/build-orphan.py
@@ -0,0 +1 @@
+"""Known-bad fixture: NOT called: no workflow, Makefile or script names it."""
diff --git a/tests/fixtures/hygiene/uncalled-script/scripts/build-used.py b/tests/fixtures/hygiene/uncalled-script/scripts/build-used.py
new file mode 100644
index 00000000..c3ad27a7
--- /dev/null
+++ b/tests/fixtures/hygiene/uncalled-script/scripts/build-used.py
@@ -0,0 +1,2 @@
+"""Known-bad fixture: called by the workflow; imports _used_helper."""
+import _used_helper  # noqa: F401
diff --git a/tests/fixtures/hygiene/unread-data/data/catalogs/orphan-catalog.json b/tests/fixtures/hygiene/unread-data/data/catalogs/orphan-catalog.json
new file mode 100644
index 00000000..2a565001
--- /dev/null
+++ b/tests/fixtures/hygiene/unread-data/data/catalogs/orphan-catalog.json
@@ -0,0 +1 @@
+{"catalog": "NOT read: nothing names this file"}
diff --git a/tests/fixtures/hygiene/unread-data/data/other/profile.json b/tests/fixtures/hygiene/unread-data/data/other/profile.json
new file mode 100644
index 00000000..6f8f5c41
--- /dev/null
+++ b/tests/fixtures/hygiene/unread-data/data/other/profile.json
@@ -0,0 +1 @@
+{"profile": "NOT read: same file name, but the reader never names this directory"}
diff --git a/tests/fixtures/hygiene/unread-data/data/profiles/profile.json b/tests/fixtures/hygiene/unread-data/data/profiles/profile.json
new file mode 100644
index 00000000..578c5d22
--- /dev/null
+++ b/tests/fixtures/hygiene/unread-data/data/profiles/profile.json
@@ -0,0 +1 @@
+{"profile": "read: its directory is named by the reader"}
diff --git a/tests/fixtures/hygiene/unread-data/data/reports/listed-report.json b/tests/fixtures/hygiene/unread-data/data/reports/listed-report.json
new file mode 100644
index 00000000..ea218072
--- /dev/null
+++ b/tests/fixtures/hygiene/unread-data/data/reports/listed-report.json
@@ -0,0 +1 @@
+{"report": "read: the register lists it"}
diff --git a/tests/fixtures/hygiene/unread-data/data/reports/register.json b/tests/fixtures/hygiene/unread-data/data/reports/register.json
new file mode 100644
index 00000000..3b69b99e
--- /dev/null
+++ b/tests/fixtures/hygiene/unread-data/data/reports/register.json
@@ -0,0 +1 @@
+{"reports": [{"file": "listed-report.json"}]}
diff --git a/tests/fixtures/hygiene/unread-data/data/used.json b/tests/fixtures/hygiene/unread-data/data/used.json
new file mode 100644
index 00000000..da3a6e0a
--- /dev/null
+++ b/tests/fixtures/hygiene/unread-data/data/used.json
@@ -0,0 +1 @@
+{"used": true}
diff --git a/tests/fixtures/hygiene/unread-data/scripts/reader.py b/tests/fixtures/hygiene/unread-data/scripts/reader.py
new file mode 100644
index 00000000..9081bdcd
--- /dev/null
+++ b/tests/fixtures/hygiene/unread-data/scripts/reader.py
@@ -0,0 +1,7 @@
+"""Known-bad fixture reader: reads used.json, the profile under profiles/ and the reports register."""
+from pathlib import Path
+
+REPO = Path(__file__).resolve().parent.parent
+USED = REPO / "data" / "used.json"
+PROFILE = REPO / "data" / "profiles" / "profile.json"
+REGISTER = REPO / "data" / "reports" / "register.json"
diff --git a/tests/fixtures/incidents/bad/duplicate-id.json b/tests/fixtures/incidents/bad/duplicate-id.json
new file mode 100644
index 00000000..54fc3da0
--- /dev/null
+++ b/tests/fixtures/incidents/bad/duplicate-id.json
@@ -0,0 +1,74 @@
+{
+  "$comment": "KNOWN-BAD FIXTURE: two incidents share an ID",
+  "schema": "incidents/1",
+  "policy": {
+    "federal_incident_coordinator": "Test coordinator; contact through https://samaydlette.com/.well-known/security.txt",
+    "notification": "published-only",
+    "notification_text": "Published only (test fixture).",
+    "adopted_vulnerability_rules": [
+      "VER-TFR-IRI"
+    ],
+    "federal_customer_data": "Test fixture.",
+    "decided_by": "Operator",
+    "decided_on": "2026-11-05",
+    "review_by": "2027-11-05"
+  },
+  "incidents": [
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T10:00:00Z",
+        "reportable": true,
+        "basis": "VER-TFR-IRI",
+        "reason": "Fixture: an internet-reachable LEV at N4.",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [
+        "CVE-2099-0001"
+      ],
+      "estimates": [],
+      "reports": [
+        {
+          "type": "Initial",
+          "at": "2026-11-02T10:30:00Z",
+          "set": {
+            "description": "Fixture description."
+          }
+        }
+      ]
+    },
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T10:00:00Z",
+        "reportable": true,
+        "basis": "VER-TFR-IRI",
+        "reason": "Fixture: an internet-reachable LEV at N4.",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [
+        "CVE-2099-0001"
+      ],
+      "estimates": [],
+      "reports": [
+        {
+          "type": "Initial",
+          "at": "2026-11-02T10:30:00Z",
+          "set": {
+            "description": "Fixture description."
+          }
+        }
+      ]
+    }
+  ]
+}
diff --git a/tests/fixtures/incidents/bad/empty-reason.json b/tests/fixtures/incidents/bad/empty-reason.json
new file mode 100644
index 00000000..db9cbf11
--- /dev/null
+++ b/tests/fixtures/incidents/bad/empty-reason.json
@@ -0,0 +1,46 @@
+{
+  "$comment": "KNOWN-BAD FIXTURE: the reportability determination states no reason",
+  "schema": "incidents/1",
+  "policy": {
+    "federal_incident_coordinator": "Test coordinator; contact through https://samaydlette.com/.well-known/security.txt",
+    "notification": "published-only",
+    "notification_text": "Published only (test fixture).",
+    "adopted_vulnerability_rules": [
+      "VER-TFR-IRI"
+    ],
+    "federal_customer_data": "Test fixture.",
+    "decided_by": "Operator",
+    "decided_on": "2026-11-05",
+    "review_by": "2027-11-05"
+  },
+  "incidents": [
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T10:00:00Z",
+        "reportable": true,
+        "basis": "VER-TFR-IRI",
+        "reason": " ",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [
+        "CVE-2099-0001"
+      ],
+      "estimates": [],
+      "reports": [
+        {
+          "type": "Initial",
+          "at": "2026-11-02T10:30:00Z",
+          "set": {
+            "description": "Fixture description."
+          }
+        }
+      ]
+    }
+  ]
+}
diff --git a/tests/fixtures/incidents/bad/evaluated-before-detected.json b/tests/fixtures/incidents/bad/evaluated-before-detected.json
new file mode 100644
index 00000000..84050cc7
--- /dev/null
+++ b/tests/fixtures/incidents/bad/evaluated-before-detected.json
@@ -0,0 +1,46 @@
+{
+  "$comment": "KNOWN-BAD FIXTURE: the evaluation is dated before detection",
+  "schema": "incidents/1",
+  "policy": {
+    "federal_incident_coordinator": "Test coordinator; contact through https://samaydlette.com/.well-known/security.txt",
+    "notification": "published-only",
+    "notification_text": "Published only (test fixture).",
+    "adopted_vulnerability_rules": [
+      "VER-TFR-IRI"
+    ],
+    "federal_customer_data": "Test fixture.",
+    "decided_by": "Operator",
+    "decided_on": "2026-11-05",
+    "review_by": "2027-11-05"
+  },
+  "incidents": [
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T09:00:00Z",
+        "reportable": true,
+        "basis": "VER-TFR-IRI",
+        "reason": "Fixture: an internet-reachable LEV at N4.",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [
+        "CVE-2099-0001"
+      ],
+      "estimates": [],
+      "reports": [
+        {
+          "type": "Initial",
+          "at": "2026-11-02T10:30:00Z",
+          "set": {
+            "description": "Fixture description."
+          }
+        }
+      ]
+    }
+  ]
+}
diff --git a/tests/fixtures/incidents/bad/final-before-recovery.json b/tests/fixtures/incidents/bad/final-before-recovery.json
new file mode 100644
index 00000000..8b094b83
--- /dev/null
+++ b/tests/fixtures/incidents/bad/final-before-recovery.json
@@ -0,0 +1,53 @@
+{
+  "$comment": "KNOWN-BAD FIXTURE: a Final report with no recovery recorded",
+  "schema": "incidents/1",
+  "policy": {
+    "federal_incident_coordinator": "Test coordinator; contact through https://samaydlette.com/.well-known/security.txt",
+    "notification": "published-only",
+    "notification_text": "Published only (test fixture).",
+    "adopted_vulnerability_rules": [
+      "VER-TFR-IRI"
+    ],
+    "federal_customer_data": "Test fixture.",
+    "decided_by": "Operator",
+    "decided_on": "2026-11-05",
+    "review_by": "2027-11-05"
+  },
+  "incidents": [
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T10:00:00Z",
+        "reportable": true,
+        "basis": "VER-TFR-IRI",
+        "reason": "Fixture: an internet-reachable LEV at N4.",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [
+        "CVE-2099-0001"
+      ],
+      "estimates": [],
+      "reports": [
+        {
+          "type": "Initial",
+          "at": "2026-11-02T10:30:00Z",
+          "set": {
+            "description": "Fixture description."
+          }
+        },
+        {
+          "type": "Final",
+          "at": "2026-11-02T12:00:00Z",
+          "set": {
+            "root_cause": "x"
+          }
+        }
+      ]
+    }
+  ]
+}
diff --git a/tests/fixtures/incidents/bad/final-not-last.json b/tests/fixtures/incidents/bad/final-not-last.json
new file mode 100644
index 00000000..67d2550e
--- /dev/null
+++ b/tests/fixtures/incidents/bad/final-not-last.json
@@ -0,0 +1,62 @@
+{
+  "$comment": "KNOWN-BAD FIXTURE: a report follows the Final report",
+  "schema": "incidents/1",
+  "policy": {
+    "federal_incident_coordinator": "Test coordinator; contact through https://samaydlette.com/.well-known/security.txt",
+    "notification": "published-only",
+    "notification_text": "Published only (test fixture).",
+    "adopted_vulnerability_rules": [
+      "VER-TFR-IRI"
+    ],
+    "federal_customer_data": "Test fixture.",
+    "decided_by": "Operator",
+    "decided_on": "2026-11-05",
+    "review_by": "2027-11-05"
+  },
+  "incidents": [
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T10:00:00Z",
+        "reportable": true,
+        "basis": "VER-TFR-IRI",
+        "reason": "Fixture: an internet-reachable LEV at N4.",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [
+        "CVE-2099-0001"
+      ],
+      "estimates": [],
+      "reports": [
+        {
+          "type": "Initial",
+          "at": "2026-11-02T10:30:00Z",
+          "set": {
+            "description": "Fixture description."
+          }
+        },
+        {
+          "type": "Final",
+          "at": "2026-11-02T12:00:00Z",
+          "set": {
+            "root_cause": "x"
+          }
+        },
+        {
+          "type": "Ongoing",
+          "at": "2026-11-02T13:00:00Z",
+          "set": {
+            "root_cause": "y"
+          }
+        }
+      ],
+      "resolved_at": "2026-11-02T11:00:00Z",
+      "recovery_complete_at": "2026-11-02T11:10:00Z"
+    }
+  ]
+}
diff --git a/tests/fixtures/incidents/bad/first-not-initial.json b/tests/fixtures/incidents/bad/first-not-initial.json
new file mode 100644
index 00000000..9dd86033
--- /dev/null
+++ b/tests/fixtures/incidents/bad/first-not-initial.json
@@ -0,0 +1,46 @@
+{
+  "$comment": "KNOWN-BAD FIXTURE: the first report is not the Initial report",
+  "schema": "incidents/1",
+  "policy": {
+    "federal_incident_coordinator": "Test coordinator; contact through https://samaydlette.com/.well-known/security.txt",
+    "notification": "published-only",
+    "notification_text": "Published only (test fixture).",
+    "adopted_vulnerability_rules": [
+      "VER-TFR-IRI"
+    ],
+    "federal_customer_data": "Test fixture.",
+    "decided_by": "Operator",
+    "decided_on": "2026-11-05",
+    "review_by": "2027-11-05"
+  },
+  "incidents": [
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T10:00:00Z",
+        "reportable": true,
+        "basis": "VER-TFR-IRI",
+        "reason": "Fixture: an internet-reachable LEV at N4.",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [
+        "CVE-2099-0001"
+      ],
+      "estimates": [],
+      "reports": [
+        {
+          "type": "Ongoing",
+          "at": "2026-11-02T10:30:00Z",
+          "set": {
+            "description": "Fixture description."
+          }
+        }
+      ]
+    }
+  ]
+}
diff --git a/tests/fixtures/incidents/bad/future-report.json b/tests/fixtures/incidents/bad/future-report.json
new file mode 100644
index 00000000..e4e76502
--- /dev/null
+++ b/tests/fixtures/incidents/bad/future-report.json
@@ -0,0 +1,53 @@
+{
+  "$comment": "KNOWN-BAD FIXTURE: a report is dated after now (the test runs with now = 2026-11-03)",
+  "schema": "incidents/1",
+  "policy": {
+    "federal_incident_coordinator": "Test coordinator; contact through https://samaydlette.com/.well-known/security.txt",
+    "notification": "published-only",
+    "notification_text": "Published only (test fixture).",
+    "adopted_vulnerability_rules": [
+      "VER-TFR-IRI"
+    ],
+    "federal_customer_data": "Test fixture.",
+    "decided_by": "Operator",
+    "decided_on": "2026-11-05",
+    "review_by": "2027-11-05"
+  },
+  "incidents": [
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T10:00:00Z",
+        "reportable": true,
+        "basis": "VER-TFR-IRI",
+        "reason": "Fixture: an internet-reachable LEV at N4.",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [
+        "CVE-2099-0001"
+      ],
+      "estimates": [],
+      "reports": [
+        {
+          "type": "Initial",
+          "at": "2026-11-02T10:30:00Z",
+          "set": {
+            "description": "Fixture description."
+          }
+        },
+        {
+          "type": "Ongoing",
+          "at": "2026-11-04T00:00:00Z",
+          "set": {
+            "root_cause": "x"
+          }
+        }
+      ]
+    }
+  ]
+}
diff --git a/tests/fixtures/incidents/bad/initial-without-description.json b/tests/fixtures/incidents/bad/initial-without-description.json
new file mode 100644
index 00000000..e50f60d6
--- /dev/null
+++ b/tests/fixtures/incidents/bad/initial-without-description.json
@@ -0,0 +1,46 @@
+{
+  "$comment": "KNOWN-BAD FIXTURE: the Initial report does not describe the incident",
+  "schema": "incidents/1",
+  "policy": {
+    "federal_incident_coordinator": "Test coordinator; contact through https://samaydlette.com/.well-known/security.txt",
+    "notification": "published-only",
+    "notification_text": "Published only (test fixture).",
+    "adopted_vulnerability_rules": [
+      "VER-TFR-IRI"
+    ],
+    "federal_customer_data": "Test fixture.",
+    "decided_by": "Operator",
+    "decided_on": "2026-11-05",
+    "review_by": "2027-11-05"
+  },
+  "incidents": [
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T10:00:00Z",
+        "reportable": true,
+        "basis": "VER-TFR-IRI",
+        "reason": "Fixture: an internet-reachable LEV at N4.",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [
+        "CVE-2099-0001"
+      ],
+      "estimates": [],
+      "reports": [
+        {
+          "type": "Initial",
+          "at": "2026-11-02T10:30:00Z",
+          "set": {
+            "root_cause": "x"
+          }
+        }
+      ]
+    }
+  ]
+}
diff --git a/tests/fixtures/incidents/bad/not-evaluated.json b/tests/fixtures/incidents/bad/not-evaluated.json
new file mode 100644
index 00000000..5814ef50
--- /dev/null
+++ b/tests/fixtures/incidents/bad/not-evaluated.json
@@ -0,0 +1,45 @@
+{
+  "$comment": "KNOWN-BAD FIXTURE: the incident has no reportability reason (IEC-CSO-EFR)",
+  "schema": "incidents/1",
+  "policy": {
+    "federal_incident_coordinator": "Test coordinator; contact through https://samaydlette.com/.well-known/security.txt",
+    "notification": "published-only",
+    "notification_text": "Published only (test fixture).",
+    "adopted_vulnerability_rules": [
+      "VER-TFR-IRI"
+    ],
+    "federal_customer_data": "Test fixture.",
+    "decided_by": "Operator",
+    "decided_on": "2026-11-05",
+    "review_by": "2027-11-05"
+  },
+  "incidents": [
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T10:00:00Z",
+        "reportable": true,
+        "basis": "VER-TFR-IRI",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [
+        "CVE-2099-0001"
+      ],
+      "estimates": [],
+      "reports": [
+        {
+          "type": "Initial",
+          "at": "2026-11-02T10:30:00Z",
+          "set": {
+            "description": "Fixture description."
+          }
+        }
+      ]
+    }
+  ]
+}
diff --git a/tests/fixtures/incidents/bad/not-reportable-with-report.json b/tests/fixtures/incidents/bad/not-reportable-with-report.json
new file mode 100644
index 00000000..bff5c9f1
--- /dev/null
+++ b/tests/fixtures/incidents/bad/not-reportable-with-report.json
@@ -0,0 +1,46 @@
+{
+  "$comment": "KNOWN-BAD FIXTURE: an incident evaluated as not reportable carries a report",
+  "schema": "incidents/1",
+  "policy": {
+    "federal_incident_coordinator": "Test coordinator; contact through https://samaydlette.com/.well-known/security.txt",
+    "notification": "published-only",
+    "notification_text": "Published only (test fixture).",
+    "adopted_vulnerability_rules": [
+      "VER-TFR-IRI"
+    ],
+    "federal_customer_data": "Test fixture.",
+    "decided_by": "Operator",
+    "decided_on": "2026-11-05",
+    "review_by": "2027-11-05"
+  },
+  "incidents": [
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T10:00:00Z",
+        "reportable": false,
+        "basis": "IEC-CSO-EFR",
+        "reason": "Fixture: an internet-reachable LEV at N4.",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [
+        "CVE-2099-0001"
+      ],
+      "estimates": [],
+      "reports": [
+        {
+          "type": "Initial",
+          "at": "2026-11-02T10:30:00Z",
+          "set": {
+            "description": "Fixture description."
+          }
+        }
+      ]
+    }
+  ]
+}
diff --git a/tests/fixtures/incidents/bad/notification-sends.json b/tests/fixtures/incidents/bad/notification-sends.json
new file mode 100644
index 00000000..1e40df8f
--- /dev/null
+++ b/tests/fixtures/incidents/bad/notification-sends.json
@@ -0,0 +1,46 @@
+{
+  "$comment": "KNOWN-BAD FIXTURE: the policy claims a delivery mode that is not built",
+  "schema": "incidents/1",
+  "policy": {
+    "federal_incident_coordinator": "Test coordinator; contact through https://samaydlette.com/.well-known/security.txt",
+    "notification": "email",
+    "notification_text": "Published only (test fixture).",
+    "adopted_vulnerability_rules": [
+      "VER-TFR-IRI"
+    ],
+    "federal_customer_data": "Test fixture.",
+    "decided_by": "Operator",
+    "decided_on": "2026-11-05",
+    "review_by": "2027-11-05"
+  },
+  "incidents": [
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T10:00:00Z",
+        "reportable": true,
+        "basis": "VER-TFR-IRI",
+        "reason": "Fixture: an internet-reachable LEV at N4.",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [
+        "CVE-2099-0001"
+      ],
+      "estimates": [],
+      "reports": [
+        {
+          "type": "Initial",
+          "at": "2026-11-02T10:30:00Z",
+          "set": {
+            "description": "Fixture description."
+          }
+        }
+      ]
+    }
+  ]
+}
diff --git a/tests/fixtures/incidents/bad/personal-email.json b/tests/fixtures/incidents/bad/personal-email.json
new file mode 100644
index 00000000..b1bdd4c1
--- /dev/null
+++ b/tests/fixtures/incidents/bad/personal-email.json
@@ -0,0 +1,46 @@
+{
+  "$comment": "KNOWN-BAD FIXTURE: a published field names a personal email address",
+  "schema": "incidents/1",
+  "policy": {
+    "federal_incident_coordinator": "someone@example.org",
+    "notification": "published-only",
+    "notification_text": "Published only (test fixture).",
+    "adopted_vulnerability_rules": [
+      "VER-TFR-IRI"
+    ],
+    "federal_customer_data": "Test fixture.",
+    "decided_by": "Operator",
+    "decided_on": "2026-11-05",
+    "review_by": "2027-11-05"
+  },
+  "incidents": [
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T10:00:00Z",
+        "reportable": true,
+        "basis": "VER-TFR-IRI",
+        "reason": "Fixture: an internet-reachable LEV at N4.",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [
+        "CVE-2099-0001"
+      ],
+      "estimates": [],
+      "reports": [
+        {
+          "type": "Initial",
+          "at": "2026-11-02T10:30:00Z",
+          "set": {
+            "description": "Fixture description."
+          }
+        }
+      ]
+    }
+  ]
+}
diff --git a/tests/fixtures/incidents/bad/rating-off-rubric.json b/tests/fixtures/incidents/bad/rating-off-rubric.json
new file mode 100644
index 00000000..a40bbe99
--- /dev/null
+++ b/tests/fixtures/incidents/bad/rating-off-rubric.json
@@ -0,0 +1,54 @@
+{
+  "$comment": "KNOWN-BAD FIXTURE: an estimate's rating is not the IEC-CSO-EFI rating for its effect and agency count",
+  "schema": "incidents/1",
+  "policy": {
+    "federal_incident_coordinator": "Test coordinator; contact through https://samaydlette.com/.well-known/security.txt",
+    "notification": "published-only",
+    "notification_text": "Published only (test fixture).",
+    "adopted_vulnerability_rules": [
+      "VER-TFR-IRI"
+    ],
+    "federal_customer_data": "Test fixture.",
+    "decided_by": "Operator",
+    "decided_on": "2026-11-05",
+    "review_by": "2027-11-05"
+  },
+  "incidents": [
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T10:00:00Z",
+        "reportable": true,
+        "basis": "VER-TFR-IRI",
+        "reason": "Fixture: an internet-reachable LEV at N4.",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [
+        "CVE-2099-0001"
+      ],
+      "estimates": [
+        {
+          "estimated_at": "2026-11-02T11:00:00Z",
+          "rating": 2,
+          "customer_effect": "disruptive",
+          "agencies": "single",
+          "reason": "x"
+        }
+      ],
+      "reports": [
+        {
+          "type": "Initial",
+          "at": "2026-11-02T10:30:00Z",
+          "set": {
+            "description": "Fixture description."
+          }
+        }
+      ]
+    }
+  ]
+}
diff --git a/tests/fixtures/incidents/bad/report-before-evaluation.json b/tests/fixtures/incidents/bad/report-before-evaluation.json
new file mode 100644
index 00000000..b1bee965
--- /dev/null
+++ b/tests/fixtures/incidents/bad/report-before-evaluation.json
@@ -0,0 +1,46 @@
+{
+  "$comment": "KNOWN-BAD FIXTURE: a report is dated before the evaluation",
+  "schema": "incidents/1",
+  "policy": {
+    "federal_incident_coordinator": "Test coordinator; contact through https://samaydlette.com/.well-known/security.txt",
+    "notification": "published-only",
+    "notification_text": "Published only (test fixture).",
+    "adopted_vulnerability_rules": [
+      "VER-TFR-IRI"
+    ],
+    "federal_customer_data": "Test fixture.",
+    "decided_by": "Operator",
+    "decided_on": "2026-11-05",
+    "review_by": "2027-11-05"
+  },
+  "incidents": [
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T10:00:00Z",
+        "reportable": true,
+        "basis": "VER-TFR-IRI",
+        "reason": "Fixture: an internet-reachable LEV at N4.",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [
+        "CVE-2099-0001"
+      ],
+      "estimates": [],
+      "reports": [
+        {
+          "type": "Initial",
+          "at": "2026-11-02T09:45:00Z",
+          "set": {
+            "description": "Fixture description."
+          }
+        }
+      ]
+    }
+  ]
+}
diff --git a/tests/fixtures/incidents/bad/unknown-field.json b/tests/fixtures/incidents/bad/unknown-field.json
new file mode 100644
index 00000000..6cf3e552
--- /dev/null
+++ b/tests/fixtures/incidents/bad/unknown-field.json
@@ -0,0 +1,47 @@
+{
+  "$comment": "KNOWN-BAD FIXTURE: an incident carries a field the register does not define",
+  "schema": "incidents/1",
+  "policy": {
+    "federal_incident_coordinator": "Test coordinator; contact through https://samaydlette.com/.well-known/security.txt",
+    "notification": "published-only",
+    "notification_text": "Published only (test fixture).",
+    "adopted_vulnerability_rules": [
+      "VER-TFR-IRI"
+    ],
+    "federal_customer_data": "Test fixture.",
+    "decided_by": "Operator",
+    "decided_on": "2026-11-05",
+    "review_by": "2027-11-05"
+  },
+  "incidents": [
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T10:00:00Z",
+        "reportable": true,
+        "basis": "VER-TFR-IRI",
+        "reason": "Fixture: an internet-reachable LEV at N4.",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [
+        "CVE-2099-0001"
+      ],
+      "estimates": [],
+      "reports": [
+        {
+          "type": "Initial",
+          "at": "2026-11-02T10:30:00Z",
+          "set": {
+            "description": "Fixture description."
+          }
+        }
+      ],
+      "severity": "high"
+    }
+  ]
+}
diff --git a/tests/fixtures/incidents/bad/vuln-basis-no-finding.json b/tests/fixtures/incidents/bad/vuln-basis-no-finding.json
new file mode 100644
index 00000000..03de43ae
--- /dev/null
+++ b/tests/fixtures/incidents/bad/vuln-basis-no-finding.json
@@ -0,0 +1,44 @@
+{
+  "$comment": "KNOWN-BAD FIXTURE: a VER-TFR-IRI incident names no finding",
+  "schema": "incidents/1",
+  "policy": {
+    "federal_incident_coordinator": "Test coordinator; contact through https://samaydlette.com/.well-known/security.txt",
+    "notification": "published-only",
+    "notification_text": "Published only (test fixture).",
+    "adopted_vulnerability_rules": [
+      "VER-TFR-IRI"
+    ],
+    "federal_customer_data": "Test fixture.",
+    "decided_by": "Operator",
+    "decided_on": "2026-11-05",
+    "review_by": "2027-11-05"
+  },
+  "incidents": [
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T10:00:00Z",
+        "reportable": true,
+        "basis": "VER-TFR-IRI",
+        "reason": "Fixture: an internet-reachable LEV at N4.",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [],
+      "estimates": [],
+      "reports": [
+        {
+          "type": "Initial",
+          "at": "2026-11-02T10:30:00Z",
+          "set": {
+            "description": "Fixture description."
+          }
+        }
+      ]
+    }
+  ]
+}
diff --git a/tests/fixtures/incidents/bad/vuln-basis-not-adopted.json b/tests/fixtures/incidents/bad/vuln-basis-not-adopted.json
new file mode 100644
index 00000000..2cb36efc
--- /dev/null
+++ b/tests/fixtures/incidents/bad/vuln-basis-not-adopted.json
@@ -0,0 +1,46 @@
+{
+  "$comment": "KNOWN-BAD FIXTURE: the basis is VER-TFR-NRI, which the policy has not adopted",
+  "schema": "incidents/1",
+  "policy": {
+    "federal_incident_coordinator": "Test coordinator; contact through https://samaydlette.com/.well-known/security.txt",
+    "notification": "published-only",
+    "notification_text": "Published only (test fixture).",
+    "adopted_vulnerability_rules": [
+      "VER-TFR-IRI"
+    ],
+    "federal_customer_data": "Test fixture.",
+    "decided_by": "Operator",
+    "decided_on": "2026-11-05",
+    "review_by": "2027-11-05"
+  },
+  "incidents": [
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T10:00:00Z",
+        "reportable": true,
+        "basis": "VER-TFR-NRI",
+        "reason": "Fixture: an internet-reachable LEV at N4.",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [
+        "CVE-2099-0001"
+      ],
+      "estimates": [],
+      "reports": [
+        {
+          "type": "Initial",
+          "at": "2026-11-02T10:30:00Z",
+          "set": {
+            "description": "Fixture description."
+          }
+        }
+      ]
+    }
+  ]
+}
diff --git a/tests/fixtures/incidents/delivery-hash-mismatch.json b/tests/fixtures/incidents/delivery-hash-mismatch.json
new file mode 100644
index 00000000..5c98f87d
--- /dev/null
+++ b/tests/fixtures/incidents/delivery-hash-mismatch.json
@@ -0,0 +1,37 @@
+{
+  "schema": "incident-reports/1",
+  "emitted_at": "2026-11-05T00:00:00Z",
+  "incidents": [
+    {
+      "id": "INC-2026-001",
+      "exercise": true,
+      "evaluation": {
+        "reportable": true
+      },
+      "reports": [
+        {
+          "type": "Initial",
+          "issued_at": "2026-11-05T03:40:00Z",
+          "file": "incident-INC-2026-001-01-initial.json",
+          "sha256": "0000000000000000000000000000000000000000000000000000000000000000",
+          "changes": {
+            "coordinator": "updated",
+            "tracking_id": "updated",
+            "description": "updated",
+            "timeline": "updated",
+            "rating": "updated",
+            "functional_impact": "updated",
+            "recovery_plan": "updated",
+            "affected_agencies": "updated",
+            "observed_activity": "not yet available",
+            "indicators_of_compromise": "not yet available",
+            "related_cves": "updated",
+            "root_cause": "not yet available",
+            "response_and_recovery_activities": "not yet available"
+          }
+        }
+      ]
+    }
+  ],
+  "_note": "KNOWN-BAD: the log's sha256 for the Initial report is not the report's; delivery must refuse it."
+}
diff --git a/tests/fixtures/incidents/delivery-missing-report.json b/tests/fixtures/incidents/delivery-missing-report.json
new file mode 100644
index 00000000..e28012f2
--- /dev/null
+++ b/tests/fixtures/incidents/delivery-missing-report.json
@@ -0,0 +1,37 @@
+{
+  "schema": "incident-reports/1",
+  "emitted_at": "2026-11-05T00:00:00Z",
+  "incidents": [
+    {
+      "id": "INC-2026-001",
+      "exercise": true,
+      "evaluation": {
+        "reportable": true
+      },
+      "reports": [
+        {
+          "type": "Initial",
+          "issued_at": "2026-11-05T03:40:00Z",
+          "file": "incident-INC-2026-001-09-ongoing.json",
+          "sha256": "9380b0720b91152dffac17a5cb3cd3e89dd82c9d2df12ea9ec07df3e7529b320",
+          "changes": {
+            "coordinator": "updated",
+            "tracking_id": "updated",
+            "description": "updated",
+            "timeline": "updated",
+            "rating": "updated",
+            "functional_impact": "updated",
+            "recovery_plan": "updated",
+            "affected_agencies": "updated",
+            "observed_activity": "not yet available",
+            "indicators_of_compromise": "not yet available",
+            "related_cves": "updated",
+            "root_cause": "not yet available",
+            "response_and_recovery_activities": "not yet available"
+          }
+        }
+      ]
+    }
+  ],
+  "_note": "KNOWN-BAD: the log lists a report that was never written; delivery must refuse it."
+}
diff --git a/tests/fixtures/incidents/delivery-not-reportable.json b/tests/fixtures/incidents/delivery-not-reportable.json
new file mode 100644
index 00000000..a8be8e4f
--- /dev/null
+++ b/tests/fixtures/incidents/delivery-not-reportable.json
@@ -0,0 +1,37 @@
+{
+  "schema": "incident-reports/1",
+  "emitted_at": "2026-11-05T00:00:00Z",
+  "incidents": [
+    {
+      "id": "INC-2026-002",
+      "exercise": true,
+      "evaluation": {
+        "reportable": false
+      },
+      "reports": [
+        {
+          "type": "Initial",
+          "issued_at": "2026-11-05T03:40:00Z",
+          "file": "incident-INC-2026-001-01-initial.json",
+          "sha256": "477eb43adc630f44f7e83060380d49c46f5e4f1a5fea22dbb33e16436c76536a",
+          "changes": {
+            "coordinator": "updated",
+            "tracking_id": "updated",
+            "description": "updated",
+            "timeline": "updated",
+            "rating": "updated",
+            "functional_impact": "updated",
+            "recovery_plan": "updated",
+            "affected_agencies": "updated",
+            "observed_activity": "not yet available",
+            "indicators_of_compromise": "not yet available",
+            "related_cves": "updated",
+            "root_cause": "not yet available",
+            "response_and_recovery_activities": "not yet available"
+          }
+        }
+      ]
+    }
+  ],
+  "_note": "KNOWN-BAD: reports listed under an incident evaluated not reportable; delivery must refuse them."
+}
diff --git a/tests/fixtures/incidents/good.json b/tests/fixtures/incidents/good.json
new file mode 100644
index 00000000..55c20493
--- /dev/null
+++ b/tests/fixtures/incidents/good.json
@@ -0,0 +1,46 @@
+{
+  "$comment": "KNOWN-GOOD FIXTURE: a minimal valid incident register (one open, reportable, non-exercise incident).",
+  "schema": "incidents/1",
+  "policy": {
+    "federal_incident_coordinator": "Test coordinator; contact through https://samaydlette.com/.well-known/security.txt",
+    "notification": "published-only",
+    "notification_text": "Published only (test fixture).",
+    "adopted_vulnerability_rules": [
+      "VER-TFR-IRI"
+    ],
+    "federal_customer_data": "Test fixture.",
+    "decided_by": "Operator",
+    "decided_on": "2026-11-05",
+    "review_by": "2027-11-05"
+  },
+  "incidents": [
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T10:00:00Z",
+        "reportable": true,
+        "basis": "VER-TFR-IRI",
+        "reason": "Fixture: an internet-reachable LEV at N4.",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [
+        "CVE-2099-0001"
+      ],
+      "estimates": [],
+      "reports": [
+        {
+          "type": "Initial",
+          "at": "2026-11-02T10:30:00Z",
+          "set": {
+            "description": "Fixture description."
+          }
+        }
+      ]
+    }
+  ]
+}
diff --git a/tests/fixtures/incidents/preflight-good.json b/tests/fixtures/incidents/preflight-good.json
new file mode 100644
index 00000000..c7738649
--- /dev/null
+++ b/tests/fixtures/incidents/preflight-good.json
@@ -0,0 +1,7 @@
+{
+  "_comment": "Good: variable names the incident-reports role (example account), environment deploys only from main.",
+  "role_arn": "arn:aws:iam::000000000000:role/github-actions-incident-reports-oidc",
+  "env_state": "ok",
+  "environment": {"name": "incident-reports", "deployment_branch_policy": {"protected_branches": false, "custom_branch_policies": true}},
+  "branch_policies": ["main"]
+}
diff --git a/tests/fixtures/incidents/preflight-missing-variable.json b/tests/fixtures/incidents/preflight-missing-variable.json
new file mode 100644
index 00000000..6ce86a33
--- /dev/null
+++ b/tests/fixtures/incidents/preflight-missing-variable.json
@@ -0,0 +1,7 @@
+{
+  "_comment": "Known-bad: the repository variable AWS_INCIDENT_REPORTS_ROLE_ARN is unset; the environment is correct. check-incident-publisher.py must fail for the variable alone.",
+  "role_arn": "",
+  "env_state": "ok",
+  "environment": {"name": "incident-reports", "deployment_branch_policy": {"protected_branches": false, "custom_branch_policies": true}},
+  "branch_policies": ["main"]
+}
diff --git a/tests/fixtures/incidents/reconcile-m-bad.json b/tests/fixtures/incidents/reconcile-m-bad.json
new file mode 100644
index 00000000..5c830fee
--- /dev/null
+++ b/tests/fixtures/incidents/reconcile-m-bad.json
@@ -0,0 +1,46 @@
+{
+  "$comment": "KNOWN-BAD FIXTURE for reconcile invariant (m): an open incident names CVE-2099-9999, which the VDR report fixture does not carry.",
+  "schema": "incidents/1",
+  "policy": {
+    "federal_incident_coordinator": "Test coordinator; contact through https://samaydlette.com/.well-known/security.txt",
+    "notification": "published-only",
+    "notification_text": "Published only (test fixture).",
+    "adopted_vulnerability_rules": [
+      "VER-TFR-IRI"
+    ],
+    "federal_customer_data": "Test fixture.",
+    "decided_by": "Operator",
+    "decided_on": "2026-11-05",
+    "review_by": "2027-11-05"
+  },
+  "incidents": [
+    {
+      "id": "INC-2026-101",
+      "title": "Fixture incident",
+      "exercise": false,
+      "started_at": "2026-11-02T09:00:00Z",
+      "detected_at": "2026-11-02T09:30:00Z",
+      "detection_source": "test",
+      "evaluation": {
+        "evaluated_at": "2026-11-02T10:00:00Z",
+        "reportable": true,
+        "basis": "VER-TFR-IRI",
+        "reason": "Fixture: an internet-reachable LEV at N4.",
+        "federal_customer_data_considered": "Fixture."
+      },
+      "findings": [
+        "CVE-2099-9999"
+      ],
+      "estimates": [],
+      "reports": [
+        {
+          "type": "Initial",
+          "at": "2026-11-02T10:30:00Z",
+          "set": {
+            "description": "Fixture description."
+          }
+        }
+      ]
+    }
+  ]
+}
diff --git a/tests/fixtures/incidents/sts-access-denied.xml b/tests/fixtures/incidents/sts-access-denied.xml
new file mode 100644
index 00000000..a3f7cdb3
--- /dev/null
+++ b/tests/fixtures/incidents/sts-access-denied.xml
@@ -0,0 +1,7 @@
+
+  
+    Sender
+    AccessDenied
+    Not authorized to perform sts:AssumeRoleWithWebIdentity
+  
+
diff --git a/tests/fixtures/incidents/sts-assumed.xml b/tests/fixtures/incidents/sts-assumed.xml
new file mode 100644
index 00000000..3326d81c
--- /dev/null
+++ b/tests/fixtures/incidents/sts-assumed.xml
@@ -0,0 +1,9 @@
+
+  
+    
+      arn:aws:sts::000000000000:assumed-role/github-actions-incident-reports-oidc/deploy-proves-incident-publisher
+      AROAEXAMPLE:deploy-proves-incident-publisher
+    
+    EXAMPLEEXAMPLEEXAMPLE
+  
+
diff --git a/tests/fixtures/incidents/sts-wrong-role.xml b/tests/fixtures/incidents/sts-wrong-role.xml
new file mode 100644
index 00000000..e6db430a
--- /dev/null
+++ b/tests/fixtures/incidents/sts-wrong-role.xml
@@ -0,0 +1,9 @@
+
+  
+    
+      arn:aws:sts::000000000000:assumed-role/github-actions-deploy-oidc/deploy-proves-incident-publisher
+      AROAEXAMPLE:deploy-proves-incident-publisher
+    
+    EXAMPLEEXAMPLEEXAMPLE
+  
+
diff --git a/tests/fixtures/inventory-types/unmapped.tf.fixture b/tests/fixtures/inventory-types/unmapped.tf.fixture
new file mode 100644
index 00000000..98ea420b
--- /dev/null
+++ b/tests/fixtures/inventory-types/unmapped.tf.fixture
@@ -0,0 +1,9 @@
+# Known-bad: a resource type the inventory builder neither maps, folds nor
+# excludes with a reason. tests/test_inventory_types.py must report exactly it.
+resource "aws_s3_bucket" "fine" {
+  bucket = "example"
+}
+
+resource "aws_elasticache_cluster" "forgotten" {
+  cluster_id = "example"
+}
diff --git a/tests/fixtures/kev/dependabot-kev.json b/tests/fixtures/kev/dependabot-kev.json
new file mode 100644
index 00000000..bed954c4
--- /dev/null
+++ b/tests/fixtures/kev/dependabot-kev.json
@@ -0,0 +1,23 @@
+[
+  {
+    "_note": "Known-bad: an open Dependabot alert for a KEV CVE.",
+    "security_advisory": {
+      "cve_id": "CVE-2099-2222",
+      "identifiers": [
+        {
+          "type": "GHSA",
+          "value": "GHSA-aaaa"
+        },
+        {
+          "type": "CVE",
+          "value": "CVE-2099-2222"
+        }
+      ]
+    },
+    "dependency": {
+      "package": {
+        "name": "example-lib"
+      }
+    }
+  }
+]
diff --git a/tests/fixtures/kev/dependabot-none.json b/tests/fixtures/kev/dependabot-none.json
new file mode 100644
index 00000000..fe51488c
--- /dev/null
+++ b/tests/fixtures/kev/dependabot-none.json
@@ -0,0 +1 @@
+[]
diff --git a/tests/fixtures/kev/grype-clean.json b/tests/fixtures/kev/grype-clean.json
new file mode 100644
index 00000000..45482568
--- /dev/null
+++ b/tests/fixtures/kev/grype-clean.json
@@ -0,0 +1,13 @@
+{
+  "matches": [
+    {
+      "vulnerability": {
+        "id": "CVE-2099-9999"
+      },
+      "artifact": {
+        "name": "leftpad",
+        "version": "1.0.0"
+      }
+    }
+  ]
+}
diff --git a/tests/fixtures/kev/grype-kev.json b/tests/fixtures/kev/grype-kev.json
new file mode 100644
index 00000000..54a41279
--- /dev/null
+++ b/tests/fixtures/kev/grype-kev.json
@@ -0,0 +1,19 @@
+{
+  "_note": "Known-bad: a Grype match whose related CVE is in the KEV catalog. The deploy must stop before apply.",
+  "matches": [
+    {
+      "vulnerability": {
+        "id": "GHSA-xxxx-yyyy-zzzz"
+      },
+      "relatedVulnerabilities": [
+        {
+          "id": "CVE-2099-1111"
+        }
+      ],
+      "artifact": {
+        "name": "thumbnailer",
+        "version": "3.1.0"
+      }
+    }
+  ]
+}
diff --git a/tests/fixtures/kev/kev-catalog.json b/tests/fixtures/kev/kev-catalog.json
new file mode 100644
index 00000000..00ac128f
--- /dev/null
+++ b/tests/fixtures/kev/kev-catalog.json
@@ -0,0 +1,18 @@
+{
+  "catalogVersion": "fixture",
+  "dateReleased": "2026-11-04T20:00:00Z",
+  "vulnerabilities": [
+    {
+      "cveID": "CVE-2099-1111",
+      "vulnerabilityName": "Fixture known-exploited flaw",
+      "dateAdded": "2026-10-01",
+      "dueDate": "2026-10-22"
+    },
+    {
+      "cveID": "CVE-2099-2222",
+      "vulnerabilityName": "Another",
+      "dateAdded": "2026-10-15",
+      "dueDate": "2026-11-05"
+    }
+  ]
+}
diff --git a/tests/fixtures/manual-work/allowed.md b/tests/fixtures/manual-work/allowed.md
new file mode 100644
index 00000000..30714d29
--- /dev/null
+++ b/tests/fixtures/manual-work/allowed.md
@@ -0,0 +1,15 @@
+# Allowed (fixture)
+
+The operator runs the independent boundary corroboration at least every 30 days (DEC-195).
+
+The audit-log review runs every night (`scripts/audit-log-review.py`) and flags unexpected writes.
+
+The Quarterly Review is held by `package-maintenance.yml` with simulated attendees.
+
+## History: what used to be done
+
+The operator reviewed CloudTrail quarterly until 2026-11-06.
+
+## Today
+
+Nothing else.
diff --git a/tests/fixtures/manual-work/bad-doc.md b/tests/fixtures/manual-work/bad-doc.md
new file mode 100644
index 00000000..b6493da5
--- /dev/null
+++ b/tests/fixtures/manual-work/bad-doc.md
@@ -0,0 +1,5 @@
+# Audit (known-bad fixture)
+
+Logs are kept in S3.
+
+The operator reviews CloudTrail quarterly.
diff --git a/tests/fixtures/manual-work/bad-passive.md b/tests/fixtures/manual-work/bad-passive.md
new file mode 100644
index 00000000..9776f3f9
--- /dev/null
+++ b/tests/fixtures/manual-work/bad-passive.md
@@ -0,0 +1,5 @@
+# Planning (known-bad fixture)
+
+**Review cadence.** Annually with the security review.
+
+Plans are version-controlled and reviewed annually.
diff --git a/tests/fixtures/manual-work/bad-record.json b/tests/fixtures/manual-work/bad-record.json
new file mode 100644
index 00000000..5949b8b8
--- /dev/null
+++ b/tests/fixtures/manual-work/bad-record.json
@@ -0,0 +1 @@
+{"id": "DEC-999", "status": "in-force", "justification": "Each build records the basis. For each open finding, the operator reviews the edge and CloudTrail logs for indicators."}
diff --git a/tests/fixtures/mas/classification-gaps.json b/tests/fixtures/mas/classification-gaps.json
new file mode 100644
index 00000000..88f5f34a
--- /dev/null
+++ b/tests/fixtures/mas/classification-gaps.json
@@ -0,0 +1,6 @@
+{"_note": "Known-bad: flow X names a component the inventory does not have; the log group is in no flow.",
+ "declared": [{"key": "operator", "label": "Operator", "zone": "outside", "kind": "actor"}],
+ "flows": [
+  {"id": "X", "label": "Operator → a ghost", "path": [{"declared": "operator"}, {"component": "aws::function::ghost"}]},
+  {"id": "Y", "label": "Operator → app", "path": [{"declared": "operator"}, {"component": "aws::function::app"}]}
+ ]}
diff --git a/tests/fixtures/mas/csp-unplaced.tf.fixture b/tests/fixtures/mas/csp-unplaced.tf.fixture
new file mode 100644
index 00000000..cea2fdf6
--- /dev/null
+++ b/tests/fixtures/mas/csp-unplaced.tf.fixture
@@ -0,0 +1,11 @@
+# Known-bad: the CSP allows a host no placement covers (MAS-CSO-IIR).
+resource "aws_cloudfront_response_headers_policy" "bad" {
+  security_headers_config {
+    content_security_policy {
+      content_security_policy = join("; ", [
+        "default-src 'self'",
+        "script-src 'self' https://cdn.jsdelivr.net/npm/x/ https://unvetted-cdn.example.com/lib.js",
+      ])
+    }
+  }
+}
diff --git a/tests/fixtures/mas/csp-unresolved.tf.fixture b/tests/fixtures/mas/csp-unresolved.tf.fixture
new file mode 100644
index 00000000..9d2c987f
--- /dev/null
+++ b/tests/fixtures/mas/csp-unresolved.tf.fixture
@@ -0,0 +1,11 @@
+# Known-bad: a CSP source names a local that is not defined, so its host cannot
+# be known; the check must fail rather than skip it.
+resource "aws_cloudfront_response_headers_policy" "bad" {
+  security_headers_config {
+    content_security_policy {
+      content_security_policy = join("; ", [
+        "connect-src 'self' https://${local.not_defined_anywhere}",
+      ])
+    }
+  }
+}
diff --git a/tests/fixtures/mas/signal-gaps.json b/tests/fixtures/mas/signal-gaps.json
new file mode 100644
index 00000000..0fae7196
--- /dev/null
+++ b/tests/fixtures/mas/signal-gaps.json
@@ -0,0 +1,11 @@
+{"_note": "Known-bad: a log group with no metadata entry and in no flow, and a component type in no KSI's evidence domain with no whole-set reason.",
+ "signal_id": "fixture-gaps",
+ "components": [
+  {"component_id": "aws::log_group::brand_new", "type": "log_group", "security_category": {"confidentiality": "low", "integrity": "moderate", "availability": "low"}, "attributes": {"region": "us-east-2"}},
+  {"component_id": "aws::mystery::thing", "type": "mystery", "security_category": {"confidentiality": "low", "integrity": "low", "availability": "low"}, "attributes": {}},
+  {"component_id": "aws::function::app", "type": "function", "security_category": {"confidentiality": "moderate", "integrity": "moderate", "availability": "low"}, "attributes": {}}
+ ],
+ "ksis": [
+  {"id": "KSI-AAA-ONE", "method": "policy-validation", "status": "pass", "evidence": {"component_refs": ["aws::function::app", "aws::log_group::brand_new"]}},
+  {"id": "KSI-PIY-ALL", "method": "inventory-attestation", "status": "pass", "evidence": {"component_refs": ["aws::function::app", "aws::log_group::brand_new", "aws::mystery::thing"]}}
+ ]}
diff --git a/tests/fixtures/mas/signal.json b/tests/fixtures/mas/signal.json
new file mode 100644
index 00000000..f5e48b4f
--- /dev/null
+++ b/tests/fixtures/mas/signal.json
@@ -0,0 +1,2326 @@
+{
+ "_note": "test fixture: the non-package components of the 2026-11-05 inventory plus the external services this change adds, attributes trimmed; one package and one page keep their types represented",
+ "signal_id": "fixture",
+ "components": [
+  {
+   "component_id": "aws::tls_certificate::website",
+   "type": "tls_certificate",
+   "security_category": {
+    "confidentiality": "not-applicable",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-1",
+    "function": "Public TLS certificate for the CDN"
+   }
+  },
+  {
+   "component_id": "aws::cdn_distribution::website",
+   "type": "cdn_distribution",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Public content delivery (TLS 1.2+, OAC to origin)"
+   }
+  },
+  {
+   "component_id": "aws::dns_zone::website",
+   "type": "dns_zone",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Authoritative DNS for the public domain"
+   }
+  },
+  {
+   "component_id": "aws::object_store::website",
+   "type": "object_store",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Origin storage for static site content and /.well-known/ artifacts"
+   }
+  },
+  {
+   "component_id": "aws::api_gateway::silk_reeling",
+   "type": "api_gateway",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "HTTP API fronting the Silk Reeling app Lambda (TLS termination, request routing, throttling)"
+   }
+  },
+  {
+   "component_id": "aws::audit_log_trail::management",
+   "type": "audit_log_trail",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Account-wide management-event audit (CloudTrail)"
+   }
+  },
+  {
+   "component_id": "aws::event_schedule::evidence_watchdog",
+   "type": "event_schedule",
+   "security_category": {
+    "confidentiality": "not-applicable",
+    "integrity": "low",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Hourly trigger for the evidence SLA watchdog Lambda"
+   }
+  },
+  {
+   "component_id": "aws::event_schedule::opa_compliance",
+   "type": "event_schedule",
+   "security_category": {
+    "confidentiality": "not-applicable",
+    "integrity": "low",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Daily trigger for the runtime KSI emitter Lambda"
+   }
+  },
+  {
+   "component_id": "aws::log_group::evidence_watchdog",
+   "type": "log_group",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "CloudWatch log group for Lambda execution / Route 53 query logs"
+   }
+  },
+  {
+   "component_id": "aws::log_group::opa_compliance",
+   "type": "log_group",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "CloudWatch log group for Lambda execution / Route 53 query logs"
+   }
+  },
+  {
+   "component_id": "aws::log_group::silk_apigw",
+   "type": "log_group",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "CloudWatch log group for the Silk Reeling API Gateway access logs"
+   }
+  },
+  {
+   "component_id": "aws::log_group::silk_reeling",
+   "type": "log_group",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "CloudWatch log group for Lambda execution / Route 53 query logs"
+   }
+  },
+  {
+   "component_id": "aws::metric_alarm::evidence[artifact-stale]",
+   "type": "metric_alarm",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Evidence SLA alarm on a watchdog metric (VDR age, runtime-signal age, nightly result)"
+   }
+  },
+  {
+   "component_id": "aws::metric_alarm::evidence[nightly-failed]",
+   "type": "metric_alarm",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Evidence SLA alarm on a watchdog metric (VDR age, runtime-signal age, nightly result)"
+   }
+  },
+  {
+   "component_id": "aws::metric_alarm::evidence[runtime-age]",
+   "type": "metric_alarm",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Evidence SLA alarm on a watchdog metric (VDR age, runtime-signal age, nightly result)"
+   }
+  },
+  {
+   "component_id": "aws::metric_alarm::evidence[vdr-age]",
+   "type": "metric_alarm",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Evidence SLA alarm on a watchdog metric (VDR age, runtime-signal age, nightly result)"
+   }
+  },
+  {
+   "component_id": "aws::identity_provider::silk_reeling",
+   "type": "identity_provider",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Cognito user pool gating the Silk Reeling app (admin-create users, required TOTP MFA, OAuth2 PKCE Hosted UI; issues the JWTs the API Gateway authorizer validates)"
+   }
+  },
+  {
+   "component_id": "aws::iam_role::evidence_watchdog",
+   "type": "iam_role",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "IAM role assumed by the evidence SLA watchdog Lambda"
+   }
+  },
+  {
+   "component_id": "aws::iam_role::lambda_opa",
+   "type": "iam_role",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "IAM role assumed by the runtime KSI emitter Lambda"
+   }
+  },
+  {
+   "component_id": "aws::iam_role::silk_reeling",
+   "type": "iam_role",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "IAM role assumed by the Silk Reeling app Lambda"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::evidence_watchdog",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role samaydlette-com-evidence-watchdog-role"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::lambda_opa",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role samaydlette-com-lambda-opa-role"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::silk_reeling",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role samaydlette-com-silk-reeling-role"
+   }
+  },
+  {
+   "component_id": "aws::kms_key::at_rest",
+   "type": "kms_key",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Customer-managed KMS key for at-rest encryption / asymmetric signing"
+   }
+  },
+  {
+   "component_id": "aws::kms_key::dnssec_ksk",
+   "type": "kms_key",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-1",
+    "function": "Customer-managed KMS key for at-rest encryption / asymmetric signing"
+   }
+  },
+  {
+   "component_id": "aws::kms_key::runtime_signing",
+   "type": "kms_key",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Customer-managed KMS key for at-rest encryption / asymmetric signing"
+   }
+  },
+  {
+   "component_id": "aws::kms_key::silk_reeling",
+   "type": "kms_key",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Customer-managed KMS key for at-rest encryption / asymmetric signing"
+   }
+  },
+  {
+   "component_id": "aws::function::evidence_watchdog",
+   "type": "function",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Hourly evidence SLA watchdog; publishes evidence-age and nightly-result metrics for the alarms"
+   }
+  },
+  {
+   "component_id": "aws::function::opa_compliance",
+   "type": "function",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Daily runtime KSI emitter; revalidates live AWS configuration"
+   }
+  },
+  {
+   "component_id": "aws::function::silk_reeling",
+   "type": "function",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Silk Reeling Mirror application backend (Cognito-gated Tai Chi coaching API)"
+   }
+  },
+  {
+   "component_id": "aws::object_store::cloudtrail",
+   "type": "object_store",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Delivery bucket for the account's CloudTrail management-event trail"
+   }
+  },
+  {
+   "component_id": "aws::object_store::logs",
+   "type": "object_store",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Access-log bucket for the site bucket and CDN"
+   }
+  },
+  {
+   "component_id": "aws::notification_topic::evidence_alerts",
+   "type": "notification_topic",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Evidence-alert topic: delivers CloudWatch alarm state changes to the operator by email"
+   }
+  },
+  {
+   "component_id": "aws::message_queue::compliance_dlq",
+   "type": "message_queue",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Dead-letter queue for failed asynchronous invocations of the compliance and watchdog Lambdas"
+   }
+  },
+  {
+   "component_id": "aws::kv_table::tflock",
+   "type": "kv_table",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Terraform state lock for the application and bootstrap stacks (one lock item per run; no state contents)"
+   }
+  },
+  {
+   "component_id": "aws::iam_group::operators",
+   "type": "iam_group",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "IAM group for the human operator(s); holds IAM administration privileges (POAM-026)"
+   }
+  },
+  {
+   "component_id": "aws::iam_group::read_only",
+   "type": "iam_group",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "IAM group granting read-only access (ReadOnlyAccess, with denies on secret values and CMK decryption)"
+   }
+  },
+  {
+   "component_id": "aws::oidc_provider::github",
+   "type": "oidc_provider",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "GitHub Actions OIDC identity provider trusted by the CI/CD deploy role (workload identity; replaced long-lived keys per POAM-001)"
+   }
+  },
+  {
+   "component_id": "aws::iam_role::deploy",
+   "type": "iam_role",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "CI deploy role (reviewer-gated prod environment)"
+   }
+  },
+  {
+   "component_id": "aws::iam_role::evidence_nightly",
+   "type": "iam_role",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Nightly evidence workflow role"
+   }
+  },
+  {
+   "component_id": "aws::iam_role::plan",
+   "type": "iam_role",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Read-only plan role for pull-request and main-branch checks"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::cloudtrail_management",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role github-actions-deploy-oidc"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::cognito_management",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role github-actions-deploy-oidc"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::compliance_dlq",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role github-actions-deploy-oidc"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::compliance_kms",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role github-actions-deploy-oidc"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::compliance_logs",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role github-actions-deploy-oidc"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::dnssec_management",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role github-actions-deploy-oidc"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::evidence_nightly_cdn",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role github-actions-evidence-nightly-oidc"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::evidence_nightly_publish",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role github-actions-evidence-nightly-oidc"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::evidence_nightly_reconcile_reads",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role github-actions-evidence-nightly-oidc"
+   }
+  },
+  {
+   "component_id": "aws::iam_role::incident_reports",
+   "type": "iam_role",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Incident reports workflow role (unattended IIR/OIR/FIR publication)"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::incident_reports_cdn",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role github-actions-incident-reports-oidc"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::incident_reports_publish",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role github-actions-incident-reports-oidc"
+   }
+  },
+  {
+   "component_id": "aws::iam_role::package_maintenance",
+   "type": "iam_role",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Certification package maintenance workflow role (unattended SDR, CPO and OCR publication)"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::package_maintenance_cdn",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role github-actions-package-maintenance-oidc"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::package_maintenance_publish",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role github-actions-package-maintenance-oidc"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::evidence_watchdog_management",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role github-actions-deploy-oidc"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::log_bucket_management",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role github-actions-deploy-oidc"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::plan_access",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role github-actions-plan-oidc"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::reconcile_reads",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role github-actions-deploy-oidc"
+   }
+  },
+  {
+   "component_id": "aws::iam_policy::tfstate_backend",
+   "type": "iam_policy",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Inline policy on role github-actions-deploy-oidc"
+   }
+  },
+  {
+   "component_id": "aws::object_store::tfstate",
+   "type": "object_store",
+   "security_category": {
+    "confidentiality": "moderate",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "region": "us-east-2",
+    "function": "Remote Terraform state for the application and bootstrap stacks"
+   }
+  },
+  {
+   "component_id": "ext::sigstore-fulcio",
+   "type": "external_service",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "External service in boundary per ROT #2 (affects CIA without separate FedRAMP ATO)",
+    "name": "Sigstore Fulcio"
+   }
+  },
+  {
+   "component_id": "ext::sigstore-rekor",
+   "type": "external_service",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "External service in boundary per ROT #2 (affects CIA without separate FedRAMP ATO)",
+    "name": "Sigstore Rekor"
+   }
+  },
+  {
+   "component_id": "ext::github-oidc",
+   "type": "external_service",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "External service in boundary per ROT #2 (affects CIA without separate FedRAMP ATO)",
+    "name": "GitHub Actions OIDC token issuer"
+   }
+  },
+  {
+   "component_id": "ext::github-repo",
+   "type": "external_service",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "External service in boundary per ROT #2 (affects CIA without separate FedRAMP ATO)",
+    "name": "GitHub repository + Actions"
+   }
+  },
+  {
+   "component_id": "ext::duo-mfa",
+   "type": "external_service",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "External service in boundary per ROT #2 (affects CIA without separate FedRAMP ATO)",
+    "name": "Duo (operator MFA)"
+   }
+  },
+  {
+   "component_id": "ext::github-advisory-db",
+   "type": "external_service",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "External service in boundary per ROT #2 (affects CIA without separate FedRAMP ATO)",
+    "name": "GitHub Advisory Database"
+   }
+  },
+  {
+   "component_id": "ext::cisa-kev",
+   "type": "external_service",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "External service in boundary per ROT #2 (affects CIA without separate FedRAMP ATO)",
+    "name": "CISA Known Exploited Vulnerabilities catalog"
+   }
+  },
+  {
+   "component_id": "ext::first-epss",
+   "type": "external_service",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "External service in boundary per ROT #2 (affects CIA without separate FedRAMP ATO)",
+    "name": "FIRST Exploit Prediction Scoring System (EPSS) scores"
+   }
+  },
+  {
+   "component_id": "ext::anchore-grype-db",
+   "type": "external_service",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "External service in boundary per ROT #2 (affects CIA without separate FedRAMP ATO)",
+    "name": "Grype vulnerability database (Anchore)"
+   }
+  },
+  {
+   "component_id": "ext::jsdelivr",
+   "type": "external_service",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "External service in boundary per ROT #2 (affects CIA without separate FedRAMP ATO)",
+    "name": "jsDelivr CDN (MediaPipe Tasks Vision runtime)"
+   }
+  },
+  {
+   "component_id": "ext::google-cloud-storage",
+   "type": "external_service",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "External service in boundary per ROT #2 (affects CIA without separate FedRAMP ATO)",
+    "name": "Google Cloud Storage (MediaPipe model bucket)"
+   }
+  },
+  {
+   "component_id": "npm::@aws-sdk/checksums@3.1001.6",
+   "type": "npm_package",
+   "security_category": {
+    "confidentiality": "not-applicable",
+    "integrity": "moderate",
+    "availability": "not-applicable"
+   },
+   "attributes": {
+    "function": "Runtime dependency of the compliance/KSI Lambda (npm)",
+    "name": "@aws-sdk/checksums"
+   }
+  },
+  {
+   "component_id": "pypi::annotated-doc@0.0.5",
+   "type": "pypi_package",
+   "security_category": {
+    "confidentiality": "not-applicable",
+    "integrity": "moderate",
+    "availability": "not-applicable"
+   },
+   "attributes": {
+    "function": "Dependency of the Silk Reeling application Lambda (PyPI)",
+    "name": "annotated-doc"
+   }
+  },
+  {
+   "component_id": "html::404.html",
+   "type": "html_artifact",
+   "security_category": {
+    "confidentiality": "low",
+    "integrity": "moderate",
+    "availability": "low"
+   },
+   "attributes": {
+    "function": "Public site content"
+   }
+  }
+ ],
+ "ksis": [
+  {
+   "id": "KSI-CED-RAT",
+   "method": "documentation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": []
+   }
+  },
+  {
+   "id": "KSI-CMT-LMC",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::cdn_distribution::website",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling"
+    ]
+   }
+  },
+  {
+   "id": "KSI-CMT-RMV",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::cdn_distribution::website",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling"
+    ]
+   }
+  },
+  {
+   "id": "KSI-CMT-RVP",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::cdn_distribution::website",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling"
+    ]
+   }
+  },
+  {
+   "id": "KSI-CMT-VTD",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::cdn_distribution::website",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling"
+    ]
+   }
+  },
+  {
+   "id": "KSI-CNA-DFP",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::api_gateway::silk_reeling",
+     "aws::cdn_distribution::website",
+     "aws::tls_certificate::website",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::identity_provider::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling",
+     "aws::dns_zone::website"
+    ]
+   }
+  },
+  {
+   "id": "KSI-CNA-EIS",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::api_gateway::silk_reeling",
+     "aws::cdn_distribution::website",
+     "aws::tls_certificate::website",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::identity_provider::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling",
+     "aws::dns_zone::website"
+    ]
+   }
+  },
+  {
+   "id": "KSI-CNA-IBP",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::api_gateway::silk_reeling",
+     "aws::cdn_distribution::website",
+     "aws::tls_certificate::website",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::identity_provider::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling",
+     "aws::dns_zone::website"
+    ]
+   }
+  },
+  {
+   "id": "KSI-CNA-MAT",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::api_gateway::silk_reeling",
+     "aws::cdn_distribution::website",
+     "aws::tls_certificate::website",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::identity_provider::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling",
+     "aws::dns_zone::website"
+    ]
+   }
+  },
+  {
+   "id": "KSI-CNA-OFA",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::api_gateway::silk_reeling",
+     "aws::cdn_distribution::website",
+     "aws::tls_certificate::website",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::identity_provider::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling",
+     "aws::dns_zone::website"
+    ]
+   }
+  },
+  {
+   "id": "KSI-CNA-RNT",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::api_gateway::silk_reeling",
+     "aws::cdn_distribution::website",
+     "aws::tls_certificate::website",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::identity_provider::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling",
+     "aws::dns_zone::website"
+    ]
+   }
+  },
+  {
+   "id": "KSI-CNA-RVP",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::api_gateway::silk_reeling",
+     "aws::cdn_distribution::website",
+     "aws::tls_certificate::website",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::identity_provider::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling",
+     "aws::dns_zone::website"
+    ]
+   }
+  },
+  {
+   "id": "KSI-CNA-ULN",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::api_gateway::silk_reeling",
+     "aws::cdn_distribution::website",
+     "aws::tls_certificate::website",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::identity_provider::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling",
+     "aws::dns_zone::website"
+    ]
+   }
+  },
+  {
+   "id": "KSI-IAM-AAM",
+   "method": "inventory-attestation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::identity_provider::silk_reeling",
+     "aws::oidc_provider::github",
+     "aws::iam_role::evidence_watchdog",
+     "aws::iam_role::lambda_opa",
+     "aws::iam_role::silk_reeling",
+     "aws::iam_role::deploy",
+     "aws::iam_role::evidence_nightly",
+     "aws::iam_role::plan",
+     "aws::iam_policy::evidence_watchdog",
+     "aws::iam_policy::lambda_opa",
+     "aws::iam_policy::silk_reeling",
+     "aws::iam_policy::cloudtrail_management",
+     "aws::iam_policy::cognito_management",
+     "aws::iam_policy::compliance_dlq",
+     "aws::iam_policy::compliance_kms",
+     "aws::iam_policy::compliance_logs",
+     "aws::iam_policy::dnssec_management",
+     "aws::iam_policy::evidence_nightly_cdn",
+     "aws::iam_policy::evidence_nightly_publish",
+     "aws::iam_policy::evidence_nightly_reconcile_reads",
+     "aws::iam_policy::evidence_watchdog_management",
+     "aws::iam_policy::log_bucket_management",
+     "aws::iam_policy::plan_access",
+     "aws::iam_policy::reconcile_reads",
+     "aws::iam_policy::tfstate_backend",
+     "aws::iam_group::operators",
+     "aws::iam_group::read_only"
+    ]
+   }
+  },
+  {
+   "id": "KSI-IAM-APM",
+   "method": "inventory-attestation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::identity_provider::silk_reeling",
+     "aws::oidc_provider::github",
+     "aws::iam_role::evidence_watchdog",
+     "aws::iam_role::lambda_opa",
+     "aws::iam_role::silk_reeling",
+     "aws::iam_role::deploy",
+     "aws::iam_role::evidence_nightly",
+     "aws::iam_role::plan",
+     "aws::iam_policy::evidence_watchdog",
+     "aws::iam_policy::lambda_opa",
+     "aws::iam_policy::silk_reeling",
+     "aws::iam_policy::cloudtrail_management",
+     "aws::iam_policy::cognito_management",
+     "aws::iam_policy::compliance_dlq",
+     "aws::iam_policy::compliance_kms",
+     "aws::iam_policy::compliance_logs",
+     "aws::iam_policy::dnssec_management",
+     "aws::iam_policy::evidence_nightly_cdn",
+     "aws::iam_policy::evidence_nightly_publish",
+     "aws::iam_policy::evidence_nightly_reconcile_reads",
+     "aws::iam_policy::evidence_watchdog_management",
+     "aws::iam_policy::log_bucket_management",
+     "aws::iam_policy::plan_access",
+     "aws::iam_policy::reconcile_reads",
+     "aws::iam_policy::tfstate_backend",
+     "aws::iam_group::operators",
+     "aws::iam_group::read_only"
+    ]
+   }
+  },
+  {
+   "id": "KSI-IAM-ELP",
+   "method": "inventory-attestation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::identity_provider::silk_reeling",
+     "aws::oidc_provider::github",
+     "aws::iam_role::evidence_watchdog",
+     "aws::iam_role::lambda_opa",
+     "aws::iam_role::silk_reeling",
+     "aws::iam_role::deploy",
+     "aws::iam_role::evidence_nightly",
+     "aws::iam_role::plan",
+     "aws::iam_policy::evidence_watchdog",
+     "aws::iam_policy::lambda_opa",
+     "aws::iam_policy::silk_reeling",
+     "aws::iam_policy::cloudtrail_management",
+     "aws::iam_policy::cognito_management",
+     "aws::iam_policy::compliance_dlq",
+     "aws::iam_policy::compliance_kms",
+     "aws::iam_policy::compliance_logs",
+     "aws::iam_policy::dnssec_management",
+     "aws::iam_policy::evidence_nightly_cdn",
+     "aws::iam_policy::evidence_nightly_publish",
+     "aws::iam_policy::evidence_nightly_reconcile_reads",
+     "aws::iam_policy::evidence_watchdog_management",
+     "aws::iam_policy::log_bucket_management",
+     "aws::iam_policy::plan_access",
+     "aws::iam_policy::reconcile_reads",
+     "aws::iam_policy::tfstate_backend",
+     "aws::iam_group::operators",
+     "aws::iam_group::read_only"
+    ]
+   }
+  },
+  {
+   "id": "KSI-IAM-JIT",
+   "method": "inventory-attestation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::identity_provider::silk_reeling",
+     "aws::oidc_provider::github",
+     "aws::iam_role::evidence_watchdog",
+     "aws::iam_role::lambda_opa",
+     "aws::iam_role::silk_reeling",
+     "aws::iam_role::deploy",
+     "aws::iam_role::evidence_nightly",
+     "aws::iam_role::plan",
+     "aws::iam_policy::evidence_watchdog",
+     "aws::iam_policy::lambda_opa",
+     "aws::iam_policy::silk_reeling",
+     "aws::iam_policy::cloudtrail_management",
+     "aws::iam_policy::cognito_management",
+     "aws::iam_policy::compliance_dlq",
+     "aws::iam_policy::compliance_kms",
+     "aws::iam_policy::compliance_logs",
+     "aws::iam_policy::dnssec_management",
+     "aws::iam_policy::evidence_nightly_cdn",
+     "aws::iam_policy::evidence_nightly_publish",
+     "aws::iam_policy::evidence_nightly_reconcile_reads",
+     "aws::iam_policy::evidence_watchdog_management",
+     "aws::iam_policy::log_bucket_management",
+     "aws::iam_policy::plan_access",
+     "aws::iam_policy::reconcile_reads",
+     "aws::iam_policy::tfstate_backend",
+     "aws::iam_group::operators",
+     "aws::iam_group::read_only"
+    ]
+   }
+  },
+  {
+   "id": "KSI-IAM-SNU",
+   "method": "inventory-attestation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::identity_provider::silk_reeling",
+     "aws::oidc_provider::github",
+     "aws::iam_role::evidence_watchdog",
+     "aws::iam_role::lambda_opa",
+     "aws::iam_role::silk_reeling",
+     "aws::iam_role::deploy",
+     "aws::iam_role::evidence_nightly",
+     "aws::iam_role::plan",
+     "aws::iam_policy::evidence_watchdog",
+     "aws::iam_policy::lambda_opa",
+     "aws::iam_policy::silk_reeling",
+     "aws::iam_policy::cloudtrail_management",
+     "aws::iam_policy::cognito_management",
+     "aws::iam_policy::compliance_dlq",
+     "aws::iam_policy::compliance_kms",
+     "aws::iam_policy::compliance_logs",
+     "aws::iam_policy::dnssec_management",
+     "aws::iam_policy::evidence_nightly_cdn",
+     "aws::iam_policy::evidence_nightly_publish",
+     "aws::iam_policy::evidence_nightly_reconcile_reads",
+     "aws::iam_policy::evidence_watchdog_management",
+     "aws::iam_policy::log_bucket_management",
+     "aws::iam_policy::plan_access",
+     "aws::iam_policy::reconcile_reads",
+     "aws::iam_policy::tfstate_backend",
+     "aws::iam_group::operators",
+     "aws::iam_group::read_only"
+    ]
+   }
+  },
+  {
+   "id": "KSI-IAM-SUS",
+   "method": "inventory-attestation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::identity_provider::silk_reeling",
+     "aws::oidc_provider::github",
+     "aws::iam_role::evidence_watchdog",
+     "aws::iam_role::lambda_opa",
+     "aws::iam_role::silk_reeling",
+     "aws::iam_role::deploy",
+     "aws::iam_role::evidence_nightly",
+     "aws::iam_role::plan",
+     "aws::iam_policy::evidence_watchdog",
+     "aws::iam_policy::lambda_opa",
+     "aws::iam_policy::silk_reeling",
+     "aws::iam_policy::cloudtrail_management",
+     "aws::iam_policy::cognito_management",
+     "aws::iam_policy::compliance_dlq",
+     "aws::iam_policy::compliance_kms",
+     "aws::iam_policy::compliance_logs",
+     "aws::iam_policy::dnssec_management",
+     "aws::iam_policy::evidence_nightly_cdn",
+     "aws::iam_policy::evidence_nightly_publish",
+     "aws::iam_policy::evidence_nightly_reconcile_reads",
+     "aws::iam_policy::evidence_watchdog_management",
+     "aws::iam_policy::log_bucket_management",
+     "aws::iam_policy::plan_access",
+     "aws::iam_policy::reconcile_reads",
+     "aws::iam_policy::tfstate_backend",
+     "aws::iam_group::operators",
+     "aws::iam_group::read_only"
+    ]
+   }
+  },
+  {
+   "id": "KSI-INR-AAR",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::log_group::evidence_watchdog",
+     "aws::log_group::opa_compliance",
+     "aws::log_group::silk_apigw",
+     "aws::log_group::silk_reeling",
+     "aws::metric_alarm::evidence[artifact-stale]",
+     "aws::metric_alarm::evidence[nightly-failed]",
+     "aws::metric_alarm::evidence[runtime-age]",
+     "aws::metric_alarm::evidence[vdr-age]",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::notification_topic::evidence_alerts"
+    ]
+   }
+  },
+  {
+   "id": "KSI-INR-RIR",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::log_group::evidence_watchdog",
+     "aws::log_group::opa_compliance",
+     "aws::log_group::silk_apigw",
+     "aws::log_group::silk_reeling",
+     "aws::metric_alarm::evidence[artifact-stale]",
+     "aws::metric_alarm::evidence[nightly-failed]",
+     "aws::metric_alarm::evidence[runtime-age]",
+     "aws::metric_alarm::evidence[vdr-age]",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::notification_topic::evidence_alerts"
+    ]
+   }
+  },
+  {
+   "id": "KSI-INR-RPI",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::log_group::evidence_watchdog",
+     "aws::log_group::opa_compliance",
+     "aws::log_group::silk_apigw",
+     "aws::log_group::silk_reeling",
+     "aws::metric_alarm::evidence[artifact-stale]",
+     "aws::metric_alarm::evidence[nightly-failed]",
+     "aws::metric_alarm::evidence[runtime-age]",
+     "aws::metric_alarm::evidence[vdr-age]",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::notification_topic::evidence_alerts"
+    ]
+   }
+  },
+  {
+   "id": "KSI-MLA-ALA",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::log_group::evidence_watchdog",
+     "aws::log_group::opa_compliance",
+     "aws::log_group::silk_apigw",
+     "aws::log_group::silk_reeling",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::message_queue::compliance_dlq",
+     "aws::metric_alarm::evidence[artifact-stale]",
+     "aws::metric_alarm::evidence[nightly-failed]",
+     "aws::metric_alarm::evidence[runtime-age]",
+     "aws::metric_alarm::evidence[vdr-age]",
+     "aws::cdn_distribution::website",
+     "aws::notification_topic::evidence_alerts",
+     "aws::audit_log_trail::management"
+    ]
+   }
+  },
+  {
+   "id": "KSI-MLA-EVC",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::log_group::evidence_watchdog",
+     "aws::log_group::opa_compliance",
+     "aws::log_group::silk_apigw",
+     "aws::log_group::silk_reeling",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::message_queue::compliance_dlq",
+     "aws::metric_alarm::evidence[artifact-stale]",
+     "aws::metric_alarm::evidence[nightly-failed]",
+     "aws::metric_alarm::evidence[runtime-age]",
+     "aws::metric_alarm::evidence[vdr-age]",
+     "aws::cdn_distribution::website",
+     "aws::notification_topic::evidence_alerts",
+     "aws::audit_log_trail::management"
+    ]
+   }
+  },
+  {
+   "id": "KSI-MLA-LET",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::log_group::evidence_watchdog",
+     "aws::log_group::opa_compliance",
+     "aws::log_group::silk_apigw",
+     "aws::log_group::silk_reeling",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::message_queue::compliance_dlq",
+     "aws::metric_alarm::evidence[artifact-stale]",
+     "aws::metric_alarm::evidence[nightly-failed]",
+     "aws::metric_alarm::evidence[runtime-age]",
+     "aws::metric_alarm::evidence[vdr-age]",
+     "aws::cdn_distribution::website",
+     "aws::notification_topic::evidence_alerts",
+     "aws::audit_log_trail::management"
+    ]
+   }
+  },
+  {
+   "id": "KSI-MLA-OSM",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::log_group::evidence_watchdog",
+     "aws::log_group::opa_compliance",
+     "aws::log_group::silk_apigw",
+     "aws::log_group::silk_reeling",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::message_queue::compliance_dlq",
+     "aws::metric_alarm::evidence[artifact-stale]",
+     "aws::metric_alarm::evidence[nightly-failed]",
+     "aws::metric_alarm::evidence[runtime-age]",
+     "aws::metric_alarm::evidence[vdr-age]",
+     "aws::cdn_distribution::website",
+     "aws::notification_topic::evidence_alerts",
+     "aws::audit_log_trail::management"
+    ]
+   }
+  },
+  {
+   "id": "KSI-MLA-RVL",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::log_group::evidence_watchdog",
+     "aws::log_group::opa_compliance",
+     "aws::log_group::silk_apigw",
+     "aws::log_group::silk_reeling",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::message_queue::compliance_dlq",
+     "aws::metric_alarm::evidence[artifact-stale]",
+     "aws::metric_alarm::evidence[nightly-failed]",
+     "aws::metric_alarm::evidence[runtime-age]",
+     "aws::metric_alarm::evidence[vdr-age]",
+     "aws::cdn_distribution::website",
+     "aws::notification_topic::evidence_alerts",
+     "aws::audit_log_trail::management"
+    ]
+   }
+  },
+  {
+   "id": "KSI-PIY-GIV",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::tls_certificate::website",
+     "aws::cdn_distribution::website",
+     "aws::dns_zone::website",
+     "aws::object_store::website",
+     "aws::api_gateway::silk_reeling",
+     "aws::audit_log_trail::management",
+     "aws::event_schedule::evidence_watchdog",
+     "aws::event_schedule::opa_compliance",
+     "aws::log_group::evidence_watchdog",
+     "aws::log_group::opa_compliance",
+     "aws::log_group::silk_apigw",
+     "aws::log_group::silk_reeling",
+     "aws::metric_alarm::evidence[artifact-stale]",
+     "aws::metric_alarm::evidence[nightly-failed]",
+     "aws::metric_alarm::evidence[runtime-age]",
+     "aws::metric_alarm::evidence[vdr-age]",
+     "aws::identity_provider::silk_reeling",
+     "aws::iam_role::evidence_watchdog",
+     "aws::iam_role::lambda_opa",
+     "aws::iam_role::silk_reeling",
+     "aws::iam_policy::evidence_watchdog",
+     "aws::iam_policy::lambda_opa",
+     "aws::iam_policy::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::notification_topic::evidence_alerts",
+     "aws::message_queue::compliance_dlq",
+     "aws::kv_table::tflock",
+     "aws::iam_group::operators",
+     "aws::iam_group::read_only",
+     "aws::oidc_provider::github",
+     "aws::iam_role::deploy",
+     "aws::iam_role::evidence_nightly",
+     "aws::iam_role::plan",
+     "aws::iam_policy::cloudtrail_management",
+     "aws::iam_policy::cognito_management",
+     "aws::iam_policy::compliance_dlq",
+     "aws::iam_policy::compliance_kms",
+     "aws::iam_policy::compliance_logs",
+     "aws::iam_policy::dnssec_management",
+     "aws::iam_policy::evidence_nightly_cdn",
+     "aws::iam_policy::evidence_nightly_publish",
+     "aws::iam_policy::evidence_nightly_reconcile_reads",
+     "aws::iam_policy::evidence_watchdog_management",
+     "aws::iam_policy::log_bucket_management",
+     "aws::iam_policy::plan_access",
+     "aws::iam_policy::reconcile_reads",
+     "aws::iam_policy::tfstate_backend",
+     "aws::object_store::tfstate",
+     "npm::@aws-sdk/checksums@3.1001.6",
+     "pypi::annotated-doc@0.0.5",
+     "html::404.html",
+     "ext::sigstore-fulcio",
+     "ext::sigstore-rekor",
+     "ext::github-oidc",
+     "ext::github-repo",
+     "ext::duo-mfa",
+     "ext::github-advisory-db",
+     "ext::cisa-kev",
+     "ext::first-epss",
+     "ext::anchore-grype-db",
+     "ext::jsdelivr",
+     "ext::google-cloud-storage"
+    ]
+   }
+  },
+  {
+   "id": "KSI-PIY-RES",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::tls_certificate::website",
+     "aws::cdn_distribution::website",
+     "aws::dns_zone::website",
+     "aws::object_store::website",
+     "aws::api_gateway::silk_reeling",
+     "aws::audit_log_trail::management",
+     "aws::event_schedule::evidence_watchdog",
+     "aws::event_schedule::opa_compliance",
+     "aws::log_group::evidence_watchdog",
+     "aws::log_group::opa_compliance",
+     "aws::log_group::silk_apigw",
+     "aws::log_group::silk_reeling",
+     "aws::metric_alarm::evidence[artifact-stale]",
+     "aws::metric_alarm::evidence[nightly-failed]",
+     "aws::metric_alarm::evidence[runtime-age]",
+     "aws::metric_alarm::evidence[vdr-age]",
+     "aws::identity_provider::silk_reeling",
+     "aws::iam_role::evidence_watchdog",
+     "aws::iam_role::lambda_opa",
+     "aws::iam_role::silk_reeling",
+     "aws::iam_policy::evidence_watchdog",
+     "aws::iam_policy::lambda_opa",
+     "aws::iam_policy::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::notification_topic::evidence_alerts",
+     "aws::message_queue::compliance_dlq",
+     "aws::kv_table::tflock",
+     "aws::iam_group::operators",
+     "aws::iam_group::read_only",
+     "aws::oidc_provider::github",
+     "aws::iam_role::deploy",
+     "aws::iam_role::evidence_nightly",
+     "aws::iam_role::plan",
+     "aws::iam_policy::cloudtrail_management",
+     "aws::iam_policy::cognito_management",
+     "aws::iam_policy::compliance_dlq",
+     "aws::iam_policy::compliance_kms",
+     "aws::iam_policy::compliance_logs",
+     "aws::iam_policy::dnssec_management",
+     "aws::iam_policy::evidence_nightly_cdn",
+     "aws::iam_policy::evidence_nightly_publish",
+     "aws::iam_policy::evidence_nightly_reconcile_reads",
+     "aws::iam_policy::evidence_watchdog_management",
+     "aws::iam_policy::log_bucket_management",
+     "aws::iam_policy::plan_access",
+     "aws::iam_policy::reconcile_reads",
+     "aws::iam_policy::tfstate_backend",
+     "aws::object_store::tfstate",
+     "npm::@aws-sdk/checksums@3.1001.6",
+     "pypi::annotated-doc@0.0.5",
+     "html::404.html",
+     "ext::sigstore-fulcio",
+     "ext::sigstore-rekor",
+     "ext::github-oidc",
+     "ext::github-repo",
+     "ext::duo-mfa",
+     "ext::github-advisory-db",
+     "ext::cisa-kev",
+     "ext::first-epss",
+     "ext::anchore-grype-db",
+     "ext::jsdelivr",
+     "ext::google-cloud-storage"
+    ]
+   }
+  },
+  {
+   "id": "KSI-PIY-RIS",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::tls_certificate::website",
+     "aws::cdn_distribution::website",
+     "aws::dns_zone::website",
+     "aws::object_store::website",
+     "aws::api_gateway::silk_reeling",
+     "aws::audit_log_trail::management",
+     "aws::event_schedule::evidence_watchdog",
+     "aws::event_schedule::opa_compliance",
+     "aws::log_group::evidence_watchdog",
+     "aws::log_group::opa_compliance",
+     "aws::log_group::silk_apigw",
+     "aws::log_group::silk_reeling",
+     "aws::metric_alarm::evidence[artifact-stale]",
+     "aws::metric_alarm::evidence[nightly-failed]",
+     "aws::metric_alarm::evidence[runtime-age]",
+     "aws::metric_alarm::evidence[vdr-age]",
+     "aws::identity_provider::silk_reeling",
+     "aws::iam_role::evidence_watchdog",
+     "aws::iam_role::lambda_opa",
+     "aws::iam_role::silk_reeling",
+     "aws::iam_policy::evidence_watchdog",
+     "aws::iam_policy::lambda_opa",
+     "aws::iam_policy::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::notification_topic::evidence_alerts",
+     "aws::message_queue::compliance_dlq",
+     "aws::kv_table::tflock",
+     "aws::iam_group::operators",
+     "aws::iam_group::read_only",
+     "aws::oidc_provider::github",
+     "aws::iam_role::deploy",
+     "aws::iam_role::evidence_nightly",
+     "aws::iam_role::plan",
+     "aws::iam_policy::cloudtrail_management",
+     "aws::iam_policy::cognito_management",
+     "aws::iam_policy::compliance_dlq",
+     "aws::iam_policy::compliance_kms",
+     "aws::iam_policy::compliance_logs",
+     "aws::iam_policy::dnssec_management",
+     "aws::iam_policy::evidence_nightly_cdn",
+     "aws::iam_policy::evidence_nightly_publish",
+     "aws::iam_policy::evidence_nightly_reconcile_reads",
+     "aws::iam_policy::evidence_watchdog_management",
+     "aws::iam_policy::log_bucket_management",
+     "aws::iam_policy::plan_access",
+     "aws::iam_policy::reconcile_reads",
+     "aws::iam_policy::tfstate_backend",
+     "aws::object_store::tfstate",
+     "npm::@aws-sdk/checksums@3.1001.6",
+     "pypi::annotated-doc@0.0.5",
+     "html::404.html",
+     "ext::sigstore-fulcio",
+     "ext::sigstore-rekor",
+     "ext::github-oidc",
+     "ext::github-repo",
+     "ext::duo-mfa",
+     "ext::github-advisory-db",
+     "ext::cisa-kev",
+     "ext::first-epss",
+     "ext::anchore-grype-db",
+     "ext::jsdelivr",
+     "ext::google-cloud-storage"
+    ]
+   }
+  },
+  {
+   "id": "KSI-PIY-RSD",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::tls_certificate::website",
+     "aws::cdn_distribution::website",
+     "aws::dns_zone::website",
+     "aws::object_store::website",
+     "aws::api_gateway::silk_reeling",
+     "aws::audit_log_trail::management",
+     "aws::event_schedule::evidence_watchdog",
+     "aws::event_schedule::opa_compliance",
+     "aws::log_group::evidence_watchdog",
+     "aws::log_group::opa_compliance",
+     "aws::log_group::silk_apigw",
+     "aws::log_group::silk_reeling",
+     "aws::metric_alarm::evidence[artifact-stale]",
+     "aws::metric_alarm::evidence[nightly-failed]",
+     "aws::metric_alarm::evidence[runtime-age]",
+     "aws::metric_alarm::evidence[vdr-age]",
+     "aws::identity_provider::silk_reeling",
+     "aws::iam_role::evidence_watchdog",
+     "aws::iam_role::lambda_opa",
+     "aws::iam_role::silk_reeling",
+     "aws::iam_policy::evidence_watchdog",
+     "aws::iam_policy::lambda_opa",
+     "aws::iam_policy::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::notification_topic::evidence_alerts",
+     "aws::message_queue::compliance_dlq",
+     "aws::kv_table::tflock",
+     "aws::iam_group::operators",
+     "aws::iam_group::read_only",
+     "aws::oidc_provider::github",
+     "aws::iam_role::deploy",
+     "aws::iam_role::evidence_nightly",
+     "aws::iam_role::plan",
+     "aws::iam_policy::cloudtrail_management",
+     "aws::iam_policy::cognito_management",
+     "aws::iam_policy::compliance_dlq",
+     "aws::iam_policy::compliance_kms",
+     "aws::iam_policy::compliance_logs",
+     "aws::iam_policy::dnssec_management",
+     "aws::iam_policy::evidence_nightly_cdn",
+     "aws::iam_policy::evidence_nightly_publish",
+     "aws::iam_policy::evidence_nightly_reconcile_reads",
+     "aws::iam_policy::evidence_watchdog_management",
+     "aws::iam_policy::log_bucket_management",
+     "aws::iam_policy::plan_access",
+     "aws::iam_policy::reconcile_reads",
+     "aws::iam_policy::tfstate_backend",
+     "aws::object_store::tfstate",
+     "npm::@aws-sdk/checksums@3.1001.6",
+     "pypi::annotated-doc@0.0.5",
+     "html::404.html",
+     "ext::sigstore-fulcio",
+     "ext::sigstore-rekor",
+     "ext::github-oidc",
+     "ext::github-repo",
+     "ext::duo-mfa",
+     "ext::github-advisory-db",
+     "ext::cisa-kev",
+     "ext::first-epss",
+     "ext::anchore-grype-db",
+     "ext::jsdelivr",
+     "ext::google-cloud-storage"
+    ]
+   }
+  },
+  {
+   "id": "KSI-PIY-RVD",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::tls_certificate::website",
+     "aws::cdn_distribution::website",
+     "aws::dns_zone::website",
+     "aws::object_store::website",
+     "aws::api_gateway::silk_reeling",
+     "aws::audit_log_trail::management",
+     "aws::event_schedule::evidence_watchdog",
+     "aws::event_schedule::opa_compliance",
+     "aws::log_group::evidence_watchdog",
+     "aws::log_group::opa_compliance",
+     "aws::log_group::silk_apigw",
+     "aws::log_group::silk_reeling",
+     "aws::metric_alarm::evidence[artifact-stale]",
+     "aws::metric_alarm::evidence[nightly-failed]",
+     "aws::metric_alarm::evidence[runtime-age]",
+     "aws::metric_alarm::evidence[vdr-age]",
+     "aws::identity_provider::silk_reeling",
+     "aws::iam_role::evidence_watchdog",
+     "aws::iam_role::lambda_opa",
+     "aws::iam_role::silk_reeling",
+     "aws::iam_policy::evidence_watchdog",
+     "aws::iam_policy::lambda_opa",
+     "aws::iam_policy::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::notification_topic::evidence_alerts",
+     "aws::message_queue::compliance_dlq",
+     "aws::kv_table::tflock",
+     "aws::iam_group::operators",
+     "aws::iam_group::read_only",
+     "aws::oidc_provider::github",
+     "aws::iam_role::deploy",
+     "aws::iam_role::evidence_nightly",
+     "aws::iam_role::plan",
+     "aws::iam_policy::cloudtrail_management",
+     "aws::iam_policy::cognito_management",
+     "aws::iam_policy::compliance_dlq",
+     "aws::iam_policy::compliance_kms",
+     "aws::iam_policy::compliance_logs",
+     "aws::iam_policy::dnssec_management",
+     "aws::iam_policy::evidence_nightly_cdn",
+     "aws::iam_policy::evidence_nightly_publish",
+     "aws::iam_policy::evidence_nightly_reconcile_reads",
+     "aws::iam_policy::evidence_watchdog_management",
+     "aws::iam_policy::log_bucket_management",
+     "aws::iam_policy::plan_access",
+     "aws::iam_policy::reconcile_reads",
+     "aws::iam_policy::tfstate_backend",
+     "aws::object_store::tfstate",
+     "npm::@aws-sdk/checksums@3.1001.6",
+     "pypi::annotated-doc@0.0.5",
+     "html::404.html",
+     "ext::sigstore-fulcio",
+     "ext::sigstore-rekor",
+     "ext::github-oidc",
+     "ext::github-repo",
+     "ext::duo-mfa",
+     "ext::github-advisory-db",
+     "ext::cisa-kev",
+     "ext::first-epss",
+     "ext::anchore-grype-db",
+     "ext::jsdelivr",
+     "ext::google-cloud-storage"
+    ]
+   }
+  },
+  {
+   "id": "KSI-RPL-ABO",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate"
+    ]
+   }
+  },
+  {
+   "id": "KSI-RPL-ARP",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate"
+    ]
+   }
+  },
+  {
+   "id": "KSI-RPL-RRO",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate"
+    ]
+   }
+  },
+  {
+   "id": "KSI-RPL-TRC",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate"
+    ]
+   }
+  },
+  {
+   "id": "KSI-SCR-MIT",
+   "method": "inventory-attestation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "ext::sigstore-fulcio",
+     "ext::sigstore-rekor",
+     "ext::github-oidc",
+     "ext::github-repo",
+     "ext::duo-mfa",
+     "ext::github-advisory-db",
+     "ext::cisa-kev",
+     "ext::first-epss",
+     "ext::anchore-grype-db",
+     "ext::jsdelivr",
+     "ext::google-cloud-storage",
+     "pypi::annotated-doc@0.0.5",
+     "npm::@aws-sdk/checksums@3.1001.6"
+    ]
+   }
+  },
+  {
+   "id": "KSI-SCR-MON",
+   "method": "inventory-attestation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "ext::sigstore-fulcio",
+     "ext::sigstore-rekor",
+     "ext::github-oidc",
+     "ext::github-repo",
+     "ext::duo-mfa",
+     "ext::github-advisory-db",
+     "ext::cisa-kev",
+     "ext::first-epss",
+     "ext::anchore-grype-db",
+     "ext::jsdelivr",
+     "ext::google-cloud-storage",
+     "pypi::annotated-doc@0.0.5",
+     "npm::@aws-sdk/checksums@3.1001.6"
+    ]
+   }
+  },
+  {
+   "id": "KSI-SVC-ACM",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::api_gateway::silk_reeling",
+     "aws::cdn_distribution::website",
+     "aws::tls_certificate::website",
+     "aws::event_schedule::evidence_watchdog",
+     "aws::event_schedule::opa_compliance",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling"
+    ]
+   }
+  },
+  {
+   "id": "KSI-SVC-ASM",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::api_gateway::silk_reeling",
+     "aws::cdn_distribution::website",
+     "aws::tls_certificate::website",
+     "aws::event_schedule::evidence_watchdog",
+     "aws::event_schedule::opa_compliance",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling"
+    ]
+   }
+  },
+  {
+   "id": "KSI-SVC-EIS",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::api_gateway::silk_reeling",
+     "aws::cdn_distribution::website",
+     "aws::tls_certificate::website",
+     "aws::event_schedule::evidence_watchdog",
+     "aws::event_schedule::opa_compliance",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling"
+    ]
+   }
+  },
+  {
+   "id": "KSI-SVC-PRR",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::api_gateway::silk_reeling",
+     "aws::cdn_distribution::website",
+     "aws::tls_certificate::website",
+     "aws::event_schedule::evidence_watchdog",
+     "aws::event_schedule::opa_compliance",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling"
+    ]
+   }
+  },
+  {
+   "id": "KSI-SVC-RUD",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::api_gateway::silk_reeling",
+     "aws::cdn_distribution::website",
+     "aws::tls_certificate::website",
+     "aws::event_schedule::evidence_watchdog",
+     "aws::event_schedule::opa_compliance",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling"
+    ]
+   }
+  },
+  {
+   "id": "KSI-SVC-SIN",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::api_gateway::silk_reeling",
+     "aws::cdn_distribution::website",
+     "aws::tls_certificate::website",
+     "aws::event_schedule::evidence_watchdog",
+     "aws::event_schedule::opa_compliance",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling"
+    ]
+   }
+  },
+  {
+   "id": "KSI-SVC-VCM",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::api_gateway::silk_reeling",
+     "aws::cdn_distribution::website",
+     "aws::tls_certificate::website",
+     "aws::event_schedule::evidence_watchdog",
+     "aws::event_schedule::opa_compliance",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling"
+    ]
+   }
+  },
+  {
+   "id": "KSI-SVC-VRI",
+   "method": "policy-validation",
+   "status": "pass",
+   "evidence": {
+    "component_refs": [
+     "aws::api_gateway::silk_reeling",
+     "aws::cdn_distribution::website",
+     "aws::tls_certificate::website",
+     "aws::event_schedule::evidence_watchdog",
+     "aws::event_schedule::opa_compliance",
+     "aws::object_store::website",
+     "aws::object_store::cloudtrail",
+     "aws::object_store::logs",
+     "aws::object_store::tfstate",
+     "aws::function::evidence_watchdog",
+     "aws::function::opa_compliance",
+     "aws::function::silk_reeling",
+     "aws::kms_key::at_rest",
+     "aws::kms_key::dnssec_ksk",
+     "aws::kms_key::runtime_signing",
+     "aws::kms_key::silk_reeling"
+    ]
+   }
+  }
+ ]
+}
diff --git a/tests/fixtures/migration/ksi-catalog-2026-11-05.json b/tests/fixtures/migration/ksi-catalog-2026-11-05.json
new file mode 100644
index 00000000..7353e477
--- /dev/null
+++ b/tests/fixtures/migration/ksi-catalog-2026-11-05.json
@@ -0,0 +1,2206 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "FedRAMP.schema.json",
+  "info": {
+    "name": "Key Security Indicators",
+    "short_name": "KSI",
+    "effective": {
+      "rev5": {
+        "is": "no"
+      },
+      "20x": {
+        "is": "required",
+        "signup_url": "https://www.fedramp.gov/20x/phase-two/participate/",
+        "current_status": "Phase 2 Pilot",
+        "start_date": "2025-11-18",
+        "end_date": "2026-03-31",
+        "comments": [
+          "Phase 1 pilot authorizations have one year from authorization to fully address this process but must demonstrate continuous quarterly progress.",
+          "Phase 2 Pilot participants must demonstrate significant progress towards addressing this process prior to submission for authorization review."
+        ]
+      }
+    },
+    "releases": [
+      {
+        "id": "26.06",
+        "published_date": "2026-06-24",
+        "description": "Consolidated Rules for 2026 (official launch). Key Security Indicators renumbered to mnemonic IDs; the AFR (Authorization by FedRAMP) family was retired and TPR (Third-Party) was renamed SCR (Supply Chain Risk). Rebuilt from the published markdown corpus by scripts/staged/build-ksi-catalog.py."
+      },
+      {
+        "id": "25.12A",
+        "published_date": "2025-12-29",
+        "description": "This release updates a significant number of KSIs to improve clarity and expectations; in general the measures required to meet each KSI remain unchanged but these updates should make it easier to address them. In additional, some KSIs have been retired.",
+        "public_comment": false
+      },
+      {
+        "id": "25.11C",
+        "published_date": "2025-12-01",
+        "description": "No effective/material changes; adjusted some KSI-AFR indcators to reference \"process\" instead of \"standard\" and added a note to KSI-AFR-02 addressing the potential infinite loop.",
+        "public_comment": false,
+        "machine_readable_link": "https://raw.githubusercontent.com/FedRAMP/docs/ced2160b22455ed26a11bf697be8f0ae3e1e5dff/data/FRMR.KSI.key-security-indicators.json"
+      },
+      {
+        "id": "25.11B",
+        "published_date": "2025-11-24",
+        "description": "No material changes to content; updated JSON structure with additional information about Rev5 application added.",
+        "public_comment": false,
+        "machine_readable_link": "https://raw.githubusercontent.com/FedRAMP/docs/a37618fccf49d6b3406d90edf2125dc6cfcba140/data/FRMR.KSI.key-security-indicators.json"
+      },
+      {
+        "id": "25.11A",
+        "published_date": "2025-11-18",
+        "description": "Updates Key Security Indicators for the FedRAMP 20x Phase Two pilot, including underlying structural changes to machine-readable docs; Renamed KSI \"indicator\" property to \"theme\" and KSI \"requirements\" property to \"indicators\" to match current naming conventions..",
+        "public_comment": true,
+        "related_rfcs": [
+          {
+            "start_date": "2025-09-10",
+            "end_date": "2025-11-17",
+            "id": "0015",
+            "url": "https://www.fedramp.gov/rfcs/0015/",
+            "discussion_url": "https://github.com/FedRAMP/community/discussions/84",
+            "short_name": "rfc-0015-recommended-secure-configuration",
+            "full_name": "FedRAMP RFC-0015: Recommended Secure Configuration Standard"
+          }
+        ],
+        "machine_readable_link": "https://raw.githubusercontent.com/FedRAMP/docs/3291fa1952f5b68eaf1a815a8ef1846ae8ca9e2f/data/FRMR.KSI.key-security-indicators.json"
+      },
+      {
+        "id": "25.10A",
+        "published_date": "2025-10-17",
+        "description": "Minor updates to improve clarity; switch from federal information to federal customer data; add impact level metadata; no substantive changes.",
+        "public_comment": false,
+        "machine_readable_link": null
+      },
+      {
+        "id": "25.05D",
+        "published_date": "2025-08-24",
+        "description": "Minor non-breaking updates to align term definitions and highlighted terms across updated materials (no changes to KSIs, definitions are now in FRD-ALL).",
+        "public_comment": false,
+        "machine_readable_link": null
+      },
+      {
+        "id": "25.05C",
+        "published_date": "2025-06-28",
+        "description": "Key Security Indicators in this release are unchanged from previously releases. 25.05C adds references for each KSI to underlying SP 800-53 controls.",
+        "public_comment": false,
+        "machine_readable_link": null
+      },
+      {
+        "id": "25.05B",
+        "published_date": "2025-06-18",
+        "description": "Initial release of Key Security Indicators from 25.05; the previous 25.05A release contained errors during conversion to JSON that are fixed in this release, the KSIs should now be identical to the original 25.05 paper release of the KSIs released on 2025-05-30. FRR-KSI-AY rules were converted to FRR-KSI rules, but otherwise unchanged.",
+        "public_comment": false,
+        "machine_readable_link": null
+      },
+      {
+        "id": "25.05A",
+        "published_date": "2025-05-30",
+        "description": "Initial release of Key Security Indicators",
+        "public_comment": true,
+        "related_rfcs": [
+          {
+            "start_date": "2025-04-24",
+            "end_date": "2025-05-24",
+            "id": "0006",
+            "url": "https://www.fedramp.gov/rfcs/0006/",
+            "discussion_url": "https://github.com/FedRAMP/community/discussions/3",
+            "short_name": "rfc-0006-key-security-indicators",
+            "full_name": "FedRAMP RFC-0006: 20x Phase One Key Security Indicators"
+          }
+        ],
+        "machine_readable_link": null
+      }
+    ],
+    "front_matter": {
+      "authority": [
+        {
+          "reference": "OMB Circular A-130",
+          "reference_url": "https://whitehouse.gov/wp-content/uploads/legacy_drupal_files/omb/circulars/A130/a130revised.pdf",
+          "description": "Appendix I states \"Agencies may also develop overlays for specific types of information or communities of interest (e.g., all web-based applications, all health care-related systems) as part of the security control selection process. Overlays provide a specification of security or privacy controls, control enhancements, supplemental guidance, and other supporting information as part of the tailoring process, that is intended to complement (and further refine) security control baselines. The overlay may be more stringent or less stringent than the original security control baseline and can be applied to multiple information systems.\""
+        },
+        {
+          "reference": "NIST SP 800-53B",
+          "reference_url": "https://csrc.nist.gov/pubs/sp/800/53/b/upd1/final",
+          "description": "Section 2.5 states \"As the number of controls in [SP 800-53] grows in response to an increasingly sophisticated threat space, it is important for organizations to have the ability to describe key capabilities needed to protect organizational missions and business functions, and to subsequently select controls that\u2014if properly designed, developed, and implemented\u2014produce such capabilities. The use of capabilities simplifies how the protection problem is viewed conceptually. Using the construct of a capability provides a method of grouping controls that are employed for a common purpose or to achieve a common objective.\" This section later states \"Ultimately, authorization decisions (i.e., risk acceptance decisions) are made based on the degree to which the desired capabilities have been effectively achieved.\""
+        },
+        {
+          "reference": "NIST SP 800-53A",
+          "reference_url": "https://csrc.nist.gov/pubs/sp/800/53/a/r5/final",
+          "description": "Section 3.5 states \"When organizations employ the concept of capabilities, automated and manual assessments account for all security and privacy controls that comprise the security and privacy capabilities. Assessors are aware of how the controls work together to provide such capabilities.\""
+        },
+        {
+          "reference": "FedRAMP Authorization Act (44 USC \u00a7 3609 (a) (1))",
+          "reference_url": "https://fedramp.gov/docs/authority/law/#a-roles-and-responsibilities",
+          "description": "requires that the Administrator of the General Services Administration shall \"in consultation with the [DHS] Secretary, develop, coordinate, and implement a process to support agency review, reuse, and standardization, where appropriate, of security assessments of cloud computing products and services...\" 44 USC \u00a7 3609 (c) (2) further states that \"the [GSA] Administrator shall establish a means for the automation of security assessments and reviews.\"",
+          "delegation": "These responsibilities are delegated to the FedRAMP Director",
+          "delegation_url": "https://www.gsa.gov/directives-library/gsa-delegations-of-authority-fedramp"
+        }
+      ],
+      "purpose": "Modern cloud services use automated or code-driven configuration management and control planes to ensure predictable, repeatable, reliable, and secure outcomes during deployment and operation. The majority of a service security assessment can take place continuously via automated validation for simple cloud-native services if the need for a traditional control-by-control narrative approach is removed.",
+      "expected_outcomes": [
+        "Cloud service providers following commercial security best practices will be able to meet and validate FedRAMP security requirements with the application of simple changes and automated capabilities",
+        "Third-party independent assessors will have a simpler framework to assess security and implementation decisions based on engineering decisions in context",
+        "Federal agencies will be able to easily, quickly, and effectively review and consume security information about the service to make informed risk-based authorization to operate decisions based on their planned use case"
+      ]
+    }
+  },
+  "FRR.KSI": {},
+  "KSI": {
+    "CED": {
+      "id": "KSI-CED",
+      "name": "Cybersecurity Education",
+      "indicators": [
+        {
+          "id": "KSI-CED-RAT",
+          "name": "Reviewing All Training",
+          "statement": "The effectiveness of relevant cybersecurity education and training is persistently reviewed, including at least general training for all employees, role-specific training for employees in high risk roles, training for development and engineering staff on secure software delivery, and training for staff involved with incident response or disaster recovery.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "cp-3",
+              "title": "Contingency Training"
+            },
+            {
+              "control_id": "ir-2",
+              "title": "Incident Response Training"
+            },
+            {
+              "control_id": "ps-6",
+              "title": "Access Agreements"
+            },
+            {
+              "control_id": "at-2",
+              "title": "Literacy Training and Awareness"
+            },
+            {
+              "control_id": "at-2.2",
+              "title": "Insider Threat"
+            },
+            {
+              "control_id": "at-2.3",
+              "title": "Social Engineering and Mining"
+            },
+            {
+              "control_id": "at-3.5",
+              "title": "Processing Personally Identifiable Information"
+            },
+            {
+              "control_id": "at-4",
+              "title": "Training Records"
+            },
+            {
+              "control_id": "ir-2.3",
+              "title": "Breach"
+            },
+            {
+              "control_id": "at-3",
+              "title": "Role-based Training"
+            },
+            {
+              "control_id": "sr-11.1",
+              "title": "Anti-counterfeit Training"
+            }
+          ]
+        }
+      ]
+    },
+    "CMT": {
+      "id": "KSI-CMT",
+      "name": "Change Management",
+      "indicators": [
+        {
+          "id": "KSI-CMT-LMC",
+          "name": "Logging Changes",
+          "statement": "Modifications to the cloud service offering are logged and monitored.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "au-2",
+              "title": "Event Logging"
+            },
+            {
+              "control_id": "cm-3",
+              "title": "Configuration Change Control"
+            },
+            {
+              "control_id": "cm-3.2",
+              "title": "Testing, Validation, and Documentation of Changes"
+            },
+            {
+              "control_id": "cm-4.2",
+              "title": "Verification of Controls"
+            },
+            {
+              "control_id": "cm-6",
+              "title": "Configuration Settings"
+            },
+            {
+              "control_id": "cm-8.3",
+              "title": "Automated Unauthorized Component Detection"
+            },
+            {
+              "control_id": "ma-2",
+              "title": "Controlled Maintenance"
+            }
+          ]
+        },
+        {
+          "id": "KSI-CMT-RMV",
+          "name": "Redeploying vs Modifying",
+          "statement": "Changes to machine-based information resources are executed through the redeployment of version controlled resources rather than direct modification wherever reasonable.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "cm-2",
+              "title": "Baseline Configuration"
+            },
+            {
+              "control_id": "cm-3",
+              "title": "Configuration Change Control"
+            },
+            {
+              "control_id": "cm-5",
+              "title": "Access Restrictions for Change"
+            },
+            {
+              "control_id": "cm-6",
+              "title": "Configuration Settings"
+            },
+            {
+              "control_id": "cm-7",
+              "title": "Least Functionality"
+            },
+            {
+              "control_id": "cm-8.1",
+              "title": "Updates During Installation and Removal"
+            },
+            {
+              "control_id": "si-3",
+              "title": "Malicious Code Protection"
+            }
+          ]
+        },
+        {
+          "id": "KSI-CMT-RVP",
+          "name": "Reviewing Change Procedures",
+          "statement": "The effectiveness of documented change management procedures is persistently reviewed.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "cm-3",
+              "title": "Configuration Change Control"
+            },
+            {
+              "control_id": "cm-3.2",
+              "title": "Testing, Validation, and Documentation of Changes"
+            },
+            {
+              "control_id": "cm-3.4",
+              "title": "Security and Privacy Representatives"
+            },
+            {
+              "control_id": "cm-5",
+              "title": "Access Restrictions for Change"
+            },
+            {
+              "control_id": "cm-7.1",
+              "title": "Periodic Review"
+            },
+            {
+              "control_id": "cm-9",
+              "title": "Configuration Management Plan"
+            }
+          ]
+        },
+        {
+          "id": "KSI-CMT-VTD",
+          "name": "Validating Throughout Deployment",
+          "statement": "Persistent testing and validation of changes throughout deployment is automated.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "cm-3",
+              "title": "Configuration Change Control"
+            },
+            {
+              "control_id": "cm-3.2",
+              "title": "Testing, Validation, and Documentation of Changes"
+            },
+            {
+              "control_id": "cm-4.2",
+              "title": "Verification of Controls"
+            },
+            {
+              "control_id": "si-2",
+              "title": "Flaw Remediation"
+            }
+          ]
+        }
+      ]
+    },
+    "CNA": {
+      "id": "KSI-CNA",
+      "name": "Cloud Native Architecture",
+      "indicators": [
+        {
+          "id": "KSI-CNA-DFP",
+          "name": "Defining Functionality and Privileges",
+          "statement": "The functionality and privileges for infrastructure and services are strictly defined.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "cm-2",
+              "title": "Baseline Configuration"
+            },
+            {
+              "control_id": "si-3",
+              "title": "Malicious Code Protection"
+            }
+          ]
+        },
+        {
+          "id": "KSI-CNA-EIS",
+          "name": "Enforcing Intended State",
+          "statement": "Automated services are used to persistently assess the security of all machine-based information resources and automatically enforce their intended operational state.",
+          "impact": {
+            "low": false,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ca-2.1",
+              "title": "Independent Assessors"
+            },
+            {
+              "control_id": "ca-7.1",
+              "title": "Independent Assessment"
+            }
+          ]
+        },
+        {
+          "id": "KSI-CNA-IBP",
+          "name": "Implementing Best Practices",
+          "statement": "The use and configuration of third-party machine-based information resources is persistently compared against the original provider's best practices and guidance.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-17.3",
+              "title": "Managed Access Control Points"
+            },
+            {
+              "control_id": "cm-2",
+              "title": "Baseline Configuration"
+            },
+            {
+              "control_id": "pl-10",
+              "title": "Baseline Selection"
+            }
+          ]
+        },
+        {
+          "id": "KSI-CNA-MAT",
+          "name": "Minimizing Attack Surface",
+          "statement": "Machine-based information resources are persistently reviewed to ensure they have a minimal attack surface and that lateral movement is minimized if compromised.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-17.3",
+              "title": "Managed Access Control Points"
+            },
+            {
+              "control_id": "ac-18.1",
+              "title": "Authentication and Encryption"
+            },
+            {
+              "control_id": "ac-18.3",
+              "title": "Disable Wireless Networking"
+            },
+            {
+              "control_id": "ac-20.1",
+              "title": "Limits on Authorized Use"
+            },
+            {
+              "control_id": "ca-9",
+              "title": "Internal System Connections"
+            },
+            {
+              "control_id": "sc-7.3",
+              "title": "Access Points"
+            },
+            {
+              "control_id": "sc-7.4",
+              "title": "External Telecommunications Services"
+            },
+            {
+              "control_id": "sc-7.5",
+              "title": "Deny by Default \u2014 Allow by Exception"
+            },
+            {
+              "control_id": "sc-7.8",
+              "title": "Route Traffic to Authenticated Proxy Servers"
+            },
+            {
+              "control_id": "sc-8",
+              "title": "Transmission Confidentiality and Integrity"
+            },
+            {
+              "control_id": "sc-10",
+              "title": "Network Disconnect"
+            },
+            {
+              "control_id": "si-10",
+              "title": "Information Input Validation"
+            },
+            {
+              "control_id": "si-11",
+              "title": "Error Handling"
+            },
+            {
+              "control_id": "si-16",
+              "title": "Memory Protection"
+            }
+          ]
+        },
+        {
+          "id": "KSI-CNA-OFA",
+          "name": "Optimizing for Availability",
+          "statement": "Machine-based information resources are persistently reviewed to ensure they are appropriately optimized for high availability and rapid recovery.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": []
+        },
+        {
+          "id": "KSI-CNA-RNT",
+          "name": "Restricting Network Traffic",
+          "statement": "Machine-based information resources are persistently reviewed to ensure they are appropriately configured to limit inbound and outbound network traffic.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-17.3",
+              "title": "Managed Access Control Points"
+            },
+            {
+              "control_id": "ca-9",
+              "title": "Internal System Connections"
+            },
+            {
+              "control_id": "cm-7.1",
+              "title": "Periodic Review"
+            },
+            {
+              "control_id": "sc-7.5",
+              "title": "Deny by Default \u2014 Allow by Exception"
+            },
+            {
+              "control_id": "si-8",
+              "title": "Spam Protection"
+            }
+          ]
+        },
+        {
+          "id": "KSI-CNA-RVP",
+          "name": "Reviewing Protections",
+          "statement": "The effectiveness of protection against denial of service attacks and other unwanted activity for machine-based information resources is persistently reviewed.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "sc-5",
+              "title": "Denial-of-service Protection"
+            },
+            {
+              "control_id": "si-8",
+              "title": "Spam Protection"
+            },
+            {
+              "control_id": "si-8.2",
+              "title": "Automatic Updates"
+            }
+          ]
+        },
+        {
+          "id": "KSI-CNA-ULN",
+          "name": "Using Logical Networking",
+          "statement": "Logical networking and related capabilities are used and persistently reviewed to enforce traffic flow controls.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-12",
+              "title": "Session Termination"
+            },
+            {
+              "control_id": "ac-17.3",
+              "title": "Managed Access Control Points"
+            },
+            {
+              "control_id": "ca-9",
+              "title": "Internal System Connections"
+            },
+            {
+              "control_id": "sc-4",
+              "title": "Information in Shared System Resources"
+            },
+            {
+              "control_id": "sc-7",
+              "title": "Boundary Protection"
+            },
+            {
+              "control_id": "sc-7.7",
+              "title": "Split Tunneling for Remote Devices"
+            },
+            {
+              "control_id": "sc-8",
+              "title": "Transmission Confidentiality and Integrity"
+            },
+            {
+              "control_id": "sc-10",
+              "title": "Network Disconnect"
+            }
+          ]
+        }
+      ]
+    },
+    "IAM": {
+      "id": "KSI-IAM",
+      "name": "Identity and Access Management",
+      "indicators": [
+        {
+          "id": "KSI-IAM-AAM",
+          "name": "Automating Account Management",
+          "statement": "The lifecycle and privileges of all accounts, roles, and groups are securely managed using automation.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-2.2",
+              "title": "Automated Temporary and Emergency Account Management"
+            },
+            {
+              "control_id": "ac-2.3",
+              "title": "Disable Accounts"
+            },
+            {
+              "control_id": "ac-2.13",
+              "title": "Disable Accounts for High-risk Individuals"
+            },
+            {
+              "control_id": "ac-6.7",
+              "title": "Review of User Privileges"
+            },
+            {
+              "control_id": "ia-4.4",
+              "title": "Identify User Status"
+            },
+            {
+              "control_id": "ia-12",
+              "title": "Identity Proofing"
+            },
+            {
+              "control_id": "ia-12.2",
+              "title": "Identity Evidence"
+            },
+            {
+              "control_id": "ia-12.3",
+              "title": "Identity Evidence Validation and Verification"
+            },
+            {
+              "control_id": "ia-12.5",
+              "title": "Address Confirmation"
+            }
+          ]
+        },
+        {
+          "id": "KSI-IAM-APM",
+          "name": "Adopting Passwordless Methods",
+          "statement": "Secure passwordless methods are used for user authentication and authorization when feasible, otherwise strong passwords with phishing-resistant MFA is used.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-3",
+              "title": "Access Enforcement"
+            },
+            {
+              "control_id": "ia-5.1",
+              "title": "Password-based Authentication"
+            },
+            {
+              "control_id": "ia-5.2",
+              "title": "Public Key-based Authentication"
+            },
+            {
+              "control_id": "ia-5.6",
+              "title": "Protection of Authenticators"
+            },
+            {
+              "control_id": "ia-6",
+              "title": "Authentication Feedback"
+            },
+            {
+              "control_id": "ac-2",
+              "title": "Account Management"
+            },
+            {
+              "control_id": "ia-2",
+              "title": "Identification and Authentication (Organizational Users)"
+            },
+            {
+              "control_id": "ia-2.1",
+              "title": "Multi-factor Authentication to Privileged Accounts"
+            },
+            {
+              "control_id": "ia-2.2",
+              "title": "Multi-factor Authentication to Non-privileged Accounts"
+            },
+            {
+              "control_id": "ia-2.8",
+              "title": "Access to Accounts \u2014 Replay Resistant"
+            },
+            {
+              "control_id": "ia-5",
+              "title": "Authenticator Management"
+            },
+            {
+              "control_id": "ia-8",
+              "title": "Identification and Authentication (Non-organizational Users)"
+            },
+            {
+              "control_id": "sc-23",
+              "title": "Session Authenticity"
+            }
+          ]
+        },
+        {
+          "id": "KSI-IAM-ELP",
+          "name": "Ensuring Least Privilege",
+          "statement": "Identity and access management measures are used and persistently reviewed to ensure each user or device can only access the resources they need.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-2.5",
+              "title": "Inactivity Logout"
+            },
+            {
+              "control_id": "ac-2.6",
+              "title": "Dynamic Privilege Management"
+            },
+            {
+              "control_id": "ac-3",
+              "title": "Access Enforcement"
+            },
+            {
+              "control_id": "ac-4",
+              "title": "Information Flow Enforcement"
+            },
+            {
+              "control_id": "ac-6",
+              "title": "Least Privilege"
+            },
+            {
+              "control_id": "ac-12",
+              "title": "Session Termination"
+            },
+            {
+              "control_id": "ac-14",
+              "title": "Permitted Actions Without Identification or Authentication"
+            },
+            {
+              "control_id": "ac-17",
+              "title": "Remote Access"
+            },
+            {
+              "control_id": "ac-17.1",
+              "title": "Monitoring and Control"
+            },
+            {
+              "control_id": "ac-17.2",
+              "title": "Protection of Confidentiality and Integrity Using Encryption"
+            },
+            {
+              "control_id": "ac-17.3",
+              "title": "Managed Access Control Points"
+            },
+            {
+              "control_id": "ac-20",
+              "title": "Use of External Systems"
+            },
+            {
+              "control_id": "ac-20.1",
+              "title": "Limits on Authorized Use"
+            },
+            {
+              "control_id": "cm-2.7",
+              "title": "Configure Systems and Components for High-risk Areas"
+            },
+            {
+              "control_id": "cm-9",
+              "title": "Configuration Management Plan"
+            },
+            {
+              "control_id": "ia-2",
+              "title": "Identification and Authentication (Organizational Users)"
+            },
+            {
+              "control_id": "ia-3",
+              "title": "Device Identification and Authentication"
+            },
+            {
+              "control_id": "ia-4",
+              "title": "Identifier Management"
+            },
+            {
+              "control_id": "ia-4.4",
+              "title": "Identify User Status"
+            },
+            {
+              "control_id": "ia-5.2",
+              "title": "Public Key-based Authentication"
+            },
+            {
+              "control_id": "ia-5.6",
+              "title": "Protection of Authenticators"
+            },
+            {
+              "control_id": "ia-11",
+              "title": "Re-authentication"
+            },
+            {
+              "control_id": "ps-2",
+              "title": "Position Risk Designation"
+            },
+            {
+              "control_id": "ps-3",
+              "title": "Personnel Screening"
+            },
+            {
+              "control_id": "ps-4",
+              "title": "Personnel Termination"
+            },
+            {
+              "control_id": "ps-5",
+              "title": "Personnel Transfer"
+            },
+            {
+              "control_id": "ps-6",
+              "title": "Access Agreements"
+            },
+            {
+              "control_id": "sc-4",
+              "title": "Information in Shared System Resources"
+            },
+            {
+              "control_id": "sc-20",
+              "title": "Secure Name/Address Resolution Service (Authoritative Source)"
+            },
+            {
+              "control_id": "sc-21",
+              "title": "Secure Name/Address Resolution Service (Recursive or Caching Resolver)"
+            },
+            {
+              "control_id": "sc-22",
+              "title": "Architecture and Provisioning for Name/Address Resolution Service"
+            },
+            {
+              "control_id": "sc-23",
+              "title": "Session Authenticity"
+            },
+            {
+              "control_id": "sc-39",
+              "title": "Process Isolation"
+            },
+            {
+              "control_id": "si-3",
+              "title": "Malicious Code Protection"
+            }
+          ]
+        },
+        {
+          "id": "KSI-IAM-JIT",
+          "name": "Authorizing Just-in-Time",
+          "statement": "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.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-2",
+              "title": "Account Management"
+            },
+            {
+              "control_id": "ac-2.1",
+              "title": "Automated System Account Management"
+            },
+            {
+              "control_id": "ac-2.2",
+              "title": "Automated Temporary and Emergency Account Management"
+            },
+            {
+              "control_id": "ac-2.3",
+              "title": "Disable Accounts"
+            },
+            {
+              "control_id": "ac-2.4",
+              "title": "Automated Audit Actions"
+            },
+            {
+              "control_id": "ac-2.6",
+              "title": "Dynamic Privilege Management"
+            },
+            {
+              "control_id": "ac-3",
+              "title": "Access Enforcement"
+            },
+            {
+              "control_id": "ac-4",
+              "title": "Information Flow Enforcement"
+            },
+            {
+              "control_id": "ac-5",
+              "title": "Separation of Duties"
+            },
+            {
+              "control_id": "ac-6",
+              "title": "Least Privilege"
+            },
+            {
+              "control_id": "ac-6.1",
+              "title": "Authorize Access to Security Functions"
+            },
+            {
+              "control_id": "ac-6.2",
+              "title": "Non-privileged Access for Nonsecurity Functions"
+            },
+            {
+              "control_id": "ac-6.5",
+              "title": "Privileged Accounts"
+            },
+            {
+              "control_id": "ac-6.7",
+              "title": "Review of User Privileges"
+            },
+            {
+              "control_id": "ac-6.9",
+              "title": "Log Use of Privileged Functions"
+            },
+            {
+              "control_id": "ac-6.10",
+              "title": "Prohibit Non-privileged Users from Executing Privileged Functions"
+            },
+            {
+              "control_id": "ac-7",
+              "title": "Unsuccessful Logon Attempts"
+            },
+            {
+              "control_id": "ac-20.1",
+              "title": "Limits on Authorized Use"
+            },
+            {
+              "control_id": "ac-17",
+              "title": "Remote Access"
+            },
+            {
+              "control_id": "au-9.4",
+              "title": "Access by Subset of Privileged Users"
+            },
+            {
+              "control_id": "cm-5",
+              "title": "Access Restrictions for Change"
+            },
+            {
+              "control_id": "cm-7",
+              "title": "Least Functionality"
+            },
+            {
+              "control_id": "cm-7.2",
+              "title": "Prevent Program Execution"
+            },
+            {
+              "control_id": "cm-7.5",
+              "title": "Authorized Software \u2014 Allow-by-exception"
+            },
+            {
+              "control_id": "cm-9",
+              "title": "Configuration Management Plan"
+            },
+            {
+              "control_id": "ia-4",
+              "title": "Identifier Management"
+            },
+            {
+              "control_id": "ia-4.4",
+              "title": "Identify User Status"
+            },
+            {
+              "control_id": "ia-7",
+              "title": "Cryptographic Module Authentication"
+            },
+            {
+              "control_id": "ps-2",
+              "title": "Position Risk Designation"
+            },
+            {
+              "control_id": "ps-3",
+              "title": "Personnel Screening"
+            },
+            {
+              "control_id": "ps-4",
+              "title": "Personnel Termination"
+            },
+            {
+              "control_id": "ps-5",
+              "title": "Personnel Transfer"
+            },
+            {
+              "control_id": "ps-6",
+              "title": "Access Agreements"
+            },
+            {
+              "control_id": "ps-9",
+              "title": "Position Descriptions"
+            },
+            {
+              "control_id": "ra-5.5",
+              "title": "Privileged Access"
+            },
+            {
+              "control_id": "sc-2",
+              "title": "Separation of System and User Functionality"
+            },
+            {
+              "control_id": "sc-23",
+              "title": "Session Authenticity"
+            },
+            {
+              "control_id": "sc-39",
+              "title": "Process Isolation"
+            }
+          ]
+        },
+        {
+          "id": "KSI-IAM-SNU",
+          "name": "Securing Non-User Authentication",
+          "statement": "Appropriately secure authentication methods are used and persistently reviewed for non-user accounts and services.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-2",
+              "title": "Account Management"
+            },
+            {
+              "control_id": "ac-2.2",
+              "title": "Automated Temporary and Emergency Account Management"
+            },
+            {
+              "control_id": "ac-4",
+              "title": "Information Flow Enforcement"
+            },
+            {
+              "control_id": "ac-6.5",
+              "title": "Privileged Accounts"
+            },
+            {
+              "control_id": "ia-3",
+              "title": "Device Identification and Authentication"
+            },
+            {
+              "control_id": "ia-5.2",
+              "title": "Public Key-based Authentication"
+            },
+            {
+              "control_id": "ra-5.5",
+              "title": "Privileged Access"
+            }
+          ]
+        },
+        {
+          "id": "KSI-IAM-SUS",
+          "name": "Responding to Suspicious Activity",
+          "statement": "Accounts with privileged access are disabled or otherwise secured in response to suspicious activity.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-2",
+              "title": "Account Management"
+            },
+            {
+              "control_id": "ac-2.1",
+              "title": "Automated System Account Management"
+            },
+            {
+              "control_id": "ac-2.3",
+              "title": "Disable Accounts"
+            },
+            {
+              "control_id": "ac-2.13",
+              "title": "Disable Accounts for High-risk Individuals"
+            },
+            {
+              "control_id": "ac-7",
+              "title": "Unsuccessful Logon Attempts"
+            },
+            {
+              "control_id": "ps-4",
+              "title": "Personnel Termination"
+            },
+            {
+              "control_id": "ps-8",
+              "title": "Personnel Sanctions"
+            }
+          ]
+        }
+      ]
+    },
+    "INR": {
+      "id": "KSI-INR",
+      "name": "Incident Response",
+      "indicators": [
+        {
+          "id": "KSI-INR-AAR",
+          "name": "Generating After Action Reports",
+          "statement": "Incident after action reports are generated and lessons learned are persistently incorporated.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ir-3",
+              "title": "Incident Response Testing"
+            },
+            {
+              "control_id": "ir-4",
+              "title": "Incident Handling"
+            },
+            {
+              "control_id": "ir-4.1",
+              "title": "Automated Incident Handling Processes"
+            },
+            {
+              "control_id": "ir-8",
+              "title": "Incident Response Plan"
+            }
+          ]
+        },
+        {
+          "id": "KSI-INR-RIR",
+          "name": "Reviewing Incident Response Procedures",
+          "statement": "The effectiveness of documented incident response procedures is persistently reviewed.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ir-4",
+              "title": "Incident Handling"
+            },
+            {
+              "control_id": "ir-4.1",
+              "title": "Automated Incident Handling Processes"
+            },
+            {
+              "control_id": "ir-6",
+              "title": "Incident Reporting"
+            },
+            {
+              "control_id": "ir-6.1",
+              "title": "Automated Reporting"
+            },
+            {
+              "control_id": "ir-6.3",
+              "title": "Supply Chain Coordination"
+            },
+            {
+              "control_id": "ir-7",
+              "title": "Incident Response Assistance"
+            },
+            {
+              "control_id": "ir-7.1",
+              "title": "Automation Support for Availability of Information and Support"
+            },
+            {
+              "control_id": "ir-8",
+              "title": "Incident Response Plan"
+            },
+            {
+              "control_id": "ir-8.1",
+              "title": "Breaches"
+            },
+            {
+              "control_id": "si-4.5",
+              "title": "System-generated Alerts"
+            }
+          ]
+        },
+        {
+          "id": "KSI-INR-RPI",
+          "name": "Reviewing Past Incidents",
+          "statement": "Past incidents are persistently reviewed for patterns or vulnerabilities that were not previously apparent or identified.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ir-3",
+              "title": "Incident Response Testing"
+            },
+            {
+              "control_id": "ir-4",
+              "title": "Incident Handling"
+            },
+            {
+              "control_id": "ir-4.1",
+              "title": "Automated Incident Handling Processes"
+            },
+            {
+              "control_id": "ir-5",
+              "title": "Incident Monitoring"
+            },
+            {
+              "control_id": "ir-8",
+              "title": "Incident Response Plan"
+            }
+          ]
+        }
+      ]
+    },
+    "MLA": {
+      "id": "KSI-MLA",
+      "name": "Monitoring, Logging, and Auditing",
+      "indicators": [
+        {
+          "id": "KSI-MLA-ALA",
+          "name": "Authorizing Log Access",
+          "statement": "A least-privileged, role and attribute-based, and just-in-time access authorization model is used and persistently reviewed for access to log data based on organizationally defined data sensitivity.",
+          "impact": {
+            "low": false,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "si-11",
+              "title": "Error Handling"
+            }
+          ]
+        },
+        {
+          "id": "KSI-MLA-EVC",
+          "name": "Evaluating Configurations",
+          "statement": "The configuration of machine-based information resources, especially infrastructure as code, is persistently evaluated and tested.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ca-7",
+              "title": "Continuous Monitoring"
+            },
+            {
+              "control_id": "cm-2",
+              "title": "Baseline Configuration"
+            },
+            {
+              "control_id": "cm-6",
+              "title": "Configuration Settings"
+            },
+            {
+              "control_id": "si-7.7",
+              "title": "Integration of Detection and Response"
+            }
+          ]
+        },
+        {
+          "id": "KSI-MLA-LET",
+          "name": "Logging Event Types",
+          "statement": "A list of information resources and event types that will be logged, monitored, and audited is maintained and persistently reviewed to ensure these activities occur.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-2.4",
+              "title": "Automated Audit Actions"
+            },
+            {
+              "control_id": "ac-6.9",
+              "title": "Log Use of Privileged Functions"
+            },
+            {
+              "control_id": "ac-17.1",
+              "title": "Monitoring and Control"
+            },
+            {
+              "control_id": "ac-20.1",
+              "title": "Limits on Authorized Use"
+            },
+            {
+              "control_id": "au-2",
+              "title": "Event Logging"
+            },
+            {
+              "control_id": "au-7.1",
+              "title": "Automatic Processing"
+            },
+            {
+              "control_id": "au-12",
+              "title": "Audit Record Generation"
+            },
+            {
+              "control_id": "si-4.4",
+              "title": "Inbound and Outbound Communications Traffic"
+            },
+            {
+              "control_id": "si-4.5",
+              "title": "System-generated Alerts"
+            },
+            {
+              "control_id": "si-7.7",
+              "title": "Integration of Detection and Response"
+            }
+          ]
+        },
+        {
+          "id": "KSI-MLA-OSM",
+          "name": "Operating SIEM Capability",
+          "statement": "A Security Information and Event Management (SIEM) or similar system(s) is used and persistently reviewed for centralized, tamper-resistant logging of events, activities, and changes.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-17.1",
+              "title": "Monitoring and Control"
+            },
+            {
+              "control_id": "ac-20.1",
+              "title": "Limits on Authorized Use"
+            },
+            {
+              "control_id": "au-2",
+              "title": "Event Logging"
+            },
+            {
+              "control_id": "au-3",
+              "title": "Content of Audit Records"
+            },
+            {
+              "control_id": "au-3.1",
+              "title": "Additional Audit Information"
+            },
+            {
+              "control_id": "au-4",
+              "title": "Audit Log Storage Capacity"
+            },
+            {
+              "control_id": "au-5",
+              "title": "Response to Audit Logging Process Failures"
+            },
+            {
+              "control_id": "au-6.1",
+              "title": "Automated Process Integration"
+            },
+            {
+              "control_id": "au-6.3",
+              "title": "Correlate Audit Record Repositories"
+            },
+            {
+              "control_id": "au-7",
+              "title": "Audit Record Reduction and Report Generation"
+            },
+            {
+              "control_id": "au-7.1",
+              "title": "Automatic Processing"
+            },
+            {
+              "control_id": "au-8",
+              "title": "Time Stamps"
+            },
+            {
+              "control_id": "au-9",
+              "title": "Protection of Audit Information"
+            },
+            {
+              "control_id": "au-11",
+              "title": "Audit Record Retention"
+            },
+            {
+              "control_id": "ir-4.1",
+              "title": "Automated Incident Handling Processes"
+            },
+            {
+              "control_id": "si-4.2",
+              "title": "Automated Tools and Mechanisms for Real-time Analysis"
+            },
+            {
+              "control_id": "si-4.4",
+              "title": "Inbound and Outbound Communications Traffic"
+            },
+            {
+              "control_id": "si-7.7",
+              "title": "Integration of Detection and Response"
+            }
+          ]
+        },
+        {
+          "id": "KSI-MLA-RVL",
+          "name": "Reviewing Logs",
+          "statement": "Logs are persistently reviewed and audited.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-2.4",
+              "title": "Automated Audit Actions"
+            },
+            {
+              "control_id": "ac-6.9",
+              "title": "Log Use of Privileged Functions"
+            },
+            {
+              "control_id": "au-2",
+              "title": "Event Logging"
+            },
+            {
+              "control_id": "au-6",
+              "title": "Audit Record Review, Analysis, and Reporting"
+            },
+            {
+              "control_id": "au-6.1",
+              "title": "Automated Process Integration"
+            },
+            {
+              "control_id": "si-4",
+              "title": "System Monitoring"
+            },
+            {
+              "control_id": "si-4.4",
+              "title": "Inbound and Outbound Communications Traffic"
+            }
+          ]
+        }
+      ]
+    },
+    "PIY": {
+      "id": "KSI-PIY",
+      "name": "Policy and Inventory",
+      "indicators": [
+        {
+          "id": "KSI-PIY-GIV",
+          "name": "Generating Inventories",
+          "statement": "Authoritative sources are used to automatically generate real-time inventories of all information resources when needed.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "cm-2.2",
+              "title": "Automation Support for Accuracy and Currency"
+            },
+            {
+              "control_id": "cm-7.5",
+              "title": "Authorized Software \u2014 Allow-by-exception"
+            },
+            {
+              "control_id": "cm-8",
+              "title": "System Component Inventory"
+            },
+            {
+              "control_id": "cm-8.1",
+              "title": "Updates During Installation and Removal"
+            },
+            {
+              "control_id": "cm-12",
+              "title": "Information Location"
+            },
+            {
+              "control_id": "cm-12.1",
+              "title": "Automated Tools to Support Information Location"
+            },
+            {
+              "control_id": "cp-2.8",
+              "title": "Identify Critical Assets"
+            }
+          ]
+        },
+        {
+          "id": "KSI-PIY-RES",
+          "name": "Reviewing Executive Support",
+          "statement": "Executive support for achieving the provider's security goals is persistently reviewed and demonstrated.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": []
+        },
+        {
+          "id": "KSI-PIY-RIS",
+          "name": "Reviewing Investments in Security",
+          "statement": "The effectiveness of the provider's investments in achieving security goals is persistently reviewed.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-5",
+              "title": "Separation of Duties"
+            },
+            {
+              "control_id": "ca-2",
+              "title": "Control Assessments"
+            },
+            {
+              "control_id": "cp-2.1",
+              "title": "Coordinate with Related Plans"
+            },
+            {
+              "control_id": "cp-4.1",
+              "title": "Coordinate with Related Plans"
+            },
+            {
+              "control_id": "ir-3.2",
+              "title": "Coordination with Related Plans"
+            },
+            {
+              "control_id": "pm-3",
+              "title": "Information Security and Privacy Resources"
+            },
+            {
+              "control_id": "sa-2",
+              "title": "Allocation of Resources"
+            },
+            {
+              "control_id": "sa-3",
+              "title": "System Development Life Cycle"
+            },
+            {
+              "control_id": "sr-2.1",
+              "title": "Establish SCRM Team"
+            }
+          ]
+        },
+        {
+          "id": "KSI-PIY-RSD",
+          "name": "Reviewing Security in the SDLC",
+          "statement": "The effectiveness of building security and privacy considerations into the Software Development Lifecycle and aligning with CISA Secure By Design principles is persistently reviewed.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-5",
+              "title": "Separation of Duties"
+            },
+            {
+              "control_id": "au-3.3",
+              "title": "Limit Personally Identifiable Information Elements"
+            },
+            {
+              "control_id": "cm-3.4",
+              "title": "Security and Privacy Representatives"
+            },
+            {
+              "control_id": "pl-8",
+              "title": "Security and Privacy Architectures"
+            },
+            {
+              "control_id": "pm-7",
+              "title": "Enterprise Architecture"
+            },
+            {
+              "control_id": "sa-3",
+              "title": "System Development Life Cycle"
+            },
+            {
+              "control_id": "sa-8",
+              "title": "Security and Privacy Engineering Principles"
+            },
+            {
+              "control_id": "sc-4",
+              "title": "Information in Shared System Resources"
+            },
+            {
+              "control_id": "sc-18",
+              "title": "Mobile Code"
+            },
+            {
+              "control_id": "si-10",
+              "title": "Information Input Validation"
+            },
+            {
+              "control_id": "si-11",
+              "title": "Error Handling"
+            },
+            {
+              "control_id": "si-16",
+              "title": "Memory Protection"
+            }
+          ]
+        },
+        {
+          "id": "KSI-PIY-RVD",
+          "name": "Reviewing Vulnerability Disclosures",
+          "statement": "The effectiveness of the provider's vulnerability disclosure program is persistently reviewed.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ra-5.11",
+              "title": "Public Disclosure Program"
+            }
+          ]
+        }
+      ]
+    },
+    "RPL": {
+      "id": "KSI-RPL",
+      "name": "Recovery Planning",
+      "indicators": [
+        {
+          "id": "KSI-RPL-ABO",
+          "name": "Aligning Backups with Objectives",
+          "statement": "The alignment of machine-based information resource backups with defined recovery objectives is persistently reviewed.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "cm-2.3",
+              "title": "Retention of Previous Configurations"
+            },
+            {
+              "control_id": "cp-6",
+              "title": "Alternate Storage Site"
+            },
+            {
+              "control_id": "cp-9",
+              "title": "System Backup"
+            },
+            {
+              "control_id": "cp-10",
+              "title": "System Recovery and Reconstitution"
+            },
+            {
+              "control_id": "cp-10.2",
+              "title": "Transaction Recovery"
+            },
+            {
+              "control_id": "si-12",
+              "title": "Information Management and Retention"
+            }
+          ]
+        },
+        {
+          "id": "KSI-RPL-ARP",
+          "name": "Aligning Recovery Plan",
+          "statement": "The alignment of recovery plans with defined recovery objectives is persistently reviewed.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "cp-2",
+              "title": "Contingency Plan"
+            },
+            {
+              "control_id": "cp-2.1",
+              "title": "Coordinate with Related Plans"
+            },
+            {
+              "control_id": "cp-2.3",
+              "title": "Resume Mission and Business Functions"
+            },
+            {
+              "control_id": "cp-4.1",
+              "title": "Coordinate with Related Plans"
+            },
+            {
+              "control_id": "cp-6",
+              "title": "Alternate Storage Site"
+            },
+            {
+              "control_id": "cp-6.1",
+              "title": "Separation from Primary Site"
+            },
+            {
+              "control_id": "cp-6.3",
+              "title": "Accessibility"
+            },
+            {
+              "control_id": "cp-7",
+              "title": "Alternate Processing Site"
+            },
+            {
+              "control_id": "cp-7.1",
+              "title": "Separation from Primary Site"
+            },
+            {
+              "control_id": "cp-7.2",
+              "title": "Accessibility"
+            },
+            {
+              "control_id": "cp-7.3",
+              "title": "Priority of Service"
+            },
+            {
+              "control_id": "cp-8",
+              "title": "Telecommunications Services"
+            },
+            {
+              "control_id": "cp-8.1",
+              "title": "Priority of Service Provisions"
+            },
+            {
+              "control_id": "cp-8.2",
+              "title": "Single Points of Failure"
+            },
+            {
+              "control_id": "cp-10",
+              "title": "System Recovery and Reconstitution"
+            },
+            {
+              "control_id": "cp-10.2",
+              "title": "Transaction Recovery"
+            }
+          ]
+        },
+        {
+          "id": "KSI-RPL-RRO",
+          "name": "Reviewing Recovery Objectives",
+          "statement": "The desired Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO) are defined and persistently reviewed for alignment with the provider's business needs and capabilities.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "cp-2.3",
+              "title": "Resume Mission and Business Functions"
+            },
+            {
+              "control_id": "cp-10",
+              "title": "System Recovery and Reconstitution"
+            }
+          ]
+        },
+        {
+          "id": "KSI-RPL-TRC",
+          "name": "Testing Recovery Capabilities",
+          "statement": "The capability to recover from incidents and contingencies aligned with defined recovery objectives is persistently tested.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "cp-2.1",
+              "title": "Coordinate with Related Plans"
+            },
+            {
+              "control_id": "cp-2.3",
+              "title": "Resume Mission and Business Functions"
+            },
+            {
+              "control_id": "cp-4",
+              "title": "Contingency Plan Testing"
+            },
+            {
+              "control_id": "cp-4.1",
+              "title": "Coordinate with Related Plans"
+            },
+            {
+              "control_id": "cp-6",
+              "title": "Alternate Storage Site"
+            },
+            {
+              "control_id": "cp-6.1",
+              "title": "Separation from Primary Site"
+            },
+            {
+              "control_id": "cp-9.1",
+              "title": "Testing for Reliability and Integrity"
+            },
+            {
+              "control_id": "cp-10",
+              "title": "System Recovery and Reconstitution"
+            },
+            {
+              "control_id": "ir-3",
+              "title": "Incident Response Testing"
+            },
+            {
+              "control_id": "ir-3.2",
+              "title": "Coordination with Related Plans"
+            }
+          ]
+        }
+      ]
+    },
+    "SCR": {
+      "id": "KSI-SCR",
+      "name": "Supply Chain Risk",
+      "indicators": [
+        {
+          "id": "KSI-SCR-MIT",
+          "name": "Mitigating Supply Chain Risk",
+          "statement": "Persistently identify, review, and mitigate potential supply chain risks.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-20",
+              "title": "Use of External Systems"
+            },
+            {
+              "control_id": "ra-3.1",
+              "title": "Supply Chain Risk Assessment"
+            },
+            {
+              "control_id": "sa-9",
+              "title": "External System Services"
+            },
+            {
+              "control_id": "sa-10",
+              "title": "Developer Configuration Management"
+            },
+            {
+              "control_id": "sa-11",
+              "title": "Developer Testing and Evaluation"
+            },
+            {
+              "control_id": "sa-15.3",
+              "title": "Criticality Analysis"
+            },
+            {
+              "control_id": "sa-22",
+              "title": "Unsupported System Components"
+            },
+            {
+              "control_id": "si-7.1",
+              "title": "Integrity Checks"
+            },
+            {
+              "control_id": "sr-5",
+              "title": "Acquisition Strategies, Tools, and Methods"
+            },
+            {
+              "control_id": "sr-6",
+              "title": "Supplier Assessments and Reviews"
+            },
+            {
+              "control_id": "ca-7.4",
+              "title": "Risk Monitoring"
+            },
+            {
+              "control_id": "sc-18",
+              "title": "Mobile Code"
+            }
+          ]
+        },
+        {
+          "id": "KSI-SCR-MON",
+          "name": "Monitoring Supply Chain Risk",
+          "statement": "Third party software information resources are automatically monitored for upstream vulnerabilities using mechanisms that may include contractual notification requirements or active monitoring services.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-20",
+              "title": "Use of External Systems"
+            },
+            {
+              "control_id": "ca-3",
+              "title": "Information Exchange"
+            },
+            {
+              "control_id": "ir-6.3",
+              "title": "Supply Chain Coordination"
+            },
+            {
+              "control_id": "ps-7",
+              "title": "External Personnel Security"
+            },
+            {
+              "control_id": "ra-5",
+              "title": "Vulnerability Monitoring and Scanning"
+            },
+            {
+              "control_id": "sa-9",
+              "title": "External System Services"
+            },
+            {
+              "control_id": "si-5",
+              "title": "Security Alerts, Advisories, and Directives"
+            },
+            {
+              "control_id": "sr-5",
+              "title": "Acquisition Strategies, Tools, and Methods"
+            },
+            {
+              "control_id": "sr-6",
+              "title": "Supplier Assessments and Reviews"
+            },
+            {
+              "control_id": "sr-8",
+              "title": "Notification Agreements"
+            }
+          ]
+        }
+      ]
+    },
+    "SVC": {
+      "id": "KSI-SVC",
+      "name": "Service Configuration",
+      "indicators": [
+        {
+          "id": "KSI-SVC-ACM",
+          "name": "Automating Configuration Management",
+          "statement": "The configuration of machine-based information resources is managed using automation and persistently reviewed for drift.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-2.4",
+              "title": "Automated Audit Actions"
+            },
+            {
+              "control_id": "cm-2",
+              "title": "Baseline Configuration"
+            },
+            {
+              "control_id": "cm-2.2",
+              "title": "Automation Support for Accuracy and Currency"
+            },
+            {
+              "control_id": "cm-2.3",
+              "title": "Retention of Previous Configurations"
+            },
+            {
+              "control_id": "cm-6",
+              "title": "Configuration Settings"
+            },
+            {
+              "control_id": "cm-7.1",
+              "title": "Periodic Review"
+            },
+            {
+              "control_id": "pl-9",
+              "title": "Central Management"
+            },
+            {
+              "control_id": "pl-10",
+              "title": "Baseline Selection"
+            },
+            {
+              "control_id": "sa-5",
+              "title": "System Documentation"
+            },
+            {
+              "control_id": "si-5",
+              "title": "Security Alerts, Advisories, and Directives"
+            },
+            {
+              "control_id": "sr-10",
+              "title": "Inspection of Systems or Components"
+            }
+          ]
+        },
+        {
+          "id": "KSI-SVC-ASM",
+          "name": "Automating Secret Management",
+          "statement": "Management, protection, and regular rotation of digital keys, certificates, and other secrets is automated and persistently reviewed.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-17.2",
+              "title": "Protection of Confidentiality and Integrity Using Encryption"
+            },
+            {
+              "control_id": "ia-5.2",
+              "title": "Public Key-based Authentication"
+            },
+            {
+              "control_id": "ia-5.6",
+              "title": "Protection of Authenticators"
+            },
+            {
+              "control_id": "sc-12",
+              "title": "Cryptographic Key Establishment and Management"
+            },
+            {
+              "control_id": "sc-17",
+              "title": "Public Key Infrastructure Certificates"
+            }
+          ]
+        },
+        {
+          "id": "KSI-SVC-EIS",
+          "name": "Evaluating and Improving Security",
+          "statement": "Information resources are persistently evaluated for opportunities to improve security and those improvements are persistently made.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "cm-7.1",
+              "title": "Periodic Review"
+            },
+            {
+              "control_id": "cm-12.1",
+              "title": "Automated Tools to Support Information Location"
+            },
+            {
+              "control_id": "ma-2",
+              "title": "Controlled Maintenance"
+            },
+            {
+              "control_id": "pl-8",
+              "title": "Security and Privacy Architectures"
+            },
+            {
+              "control_id": "sc-7",
+              "title": "Boundary Protection"
+            },
+            {
+              "control_id": "sc-39",
+              "title": "Process Isolation"
+            },
+            {
+              "control_id": "si-2.2",
+              "title": "Automated Flaw Remediation Status"
+            },
+            {
+              "control_id": "si-4",
+              "title": "System Monitoring"
+            },
+            {
+              "control_id": "sr-10",
+              "title": "Inspection of Systems or Components"
+            }
+          ]
+        },
+        {
+          "id": "KSI-SVC-PRR",
+          "name": "Preventing Residual Risk",
+          "statement": "Plans, procedures, and the state of information resources are persistently reviewed after making changes to limit and remove unwanted residual elements that would likely negatively affect the confidentiality, integrity, or availability of federal customer data.",
+          "impact": {
+            "low": false,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "sc-4",
+              "title": "Information in Shared System Resources"
+            }
+          ]
+        },
+        {
+          "id": "KSI-SVC-RUD",
+          "name": "Removing Unwanted Data",
+          "statement": "Unwanted federal customer data is removed promptly when requested by an agency in alignment with customer agreements, including from backups if appropriate; this typically applies when a customer spills information or when a customer seeks to remove information from a service due to a change in usage.",
+          "impact": {
+            "low": false,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "si-12.3",
+              "title": "Information Disposal"
+            },
+            {
+              "control_id": "si-18.4",
+              "title": "Individual Requests"
+            }
+          ]
+        },
+        {
+          "id": "KSI-SVC-SIN",
+          "name": "Securing Information",
+          "statement": "Information is encrypted or otherwise secured from unwanted access or modification.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "ac-1",
+              "title": "Policy and Procedures"
+            },
+            {
+              "control_id": "ac-17.2",
+              "title": "Protection of Confidentiality and Integrity Using Encryption"
+            },
+            {
+              "control_id": "cp-9.8",
+              "title": "Cryptographic Protection"
+            },
+            {
+              "control_id": "sc-8",
+              "title": "Transmission Confidentiality and Integrity"
+            },
+            {
+              "control_id": "sc-8.1",
+              "title": "Cryptographic Protection"
+            },
+            {
+              "control_id": "sc-13",
+              "title": "Cryptographic Protection"
+            },
+            {
+              "control_id": "sc-20",
+              "title": "Secure Name/Address Resolution Service (Authoritative Source)"
+            },
+            {
+              "control_id": "sc-21",
+              "title": "Secure Name/Address Resolution Service (Recursive or Caching Resolver)"
+            },
+            {
+              "control_id": "sc-22",
+              "title": "Architecture and Provisioning for Name/Address Resolution Service"
+            },
+            {
+              "control_id": "sc-23",
+              "title": "Session Authenticity"
+            },
+            {
+              "control_id": "sc-28",
+              "title": "Protection of Information at Rest"
+            },
+            {
+              "control_id": "sc-28.1",
+              "title": "Cryptographic Protection"
+            }
+          ]
+        },
+        {
+          "id": "KSI-SVC-VCM",
+          "name": "Validating Communications",
+          "statement": "The authenticity and integrity of communications between machine-based information resources is persistently validated using automation.",
+          "impact": {
+            "low": false,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "sc-23",
+              "title": "Session Authenticity"
+            },
+            {
+              "control_id": "si-7.1",
+              "title": "Integrity Checks"
+            }
+          ]
+        },
+        {
+          "id": "KSI-SVC-VRI",
+          "name": "Validating Resource Integrity",
+          "statement": "Use cryptographic methods to validate the integrity of machine-based information resources.",
+          "impact": {
+            "low": true,
+            "moderate": true
+          },
+          "controls": [
+            {
+              "control_id": "cm-2.2",
+              "title": "Automation Support for Accuracy and Currency"
+            },
+            {
+              "control_id": "cm-8.3",
+              "title": "Automated Unauthorized Component Detection"
+            },
+            {
+              "control_id": "sc-13",
+              "title": "Cryptographic Protection"
+            },
+            {
+              "control_id": "sc-23",
+              "title": "Session Authenticity"
+            },
+            {
+              "control_id": "si-7",
+              "title": "Software, Firmware, and Information Integrity"
+            },
+            {
+              "control_id": "si-7.1",
+              "title": "Integrity Checks"
+            },
+            {
+              "control_id": "sr-10",
+              "title": "Inspection of Systems or Components"
+            }
+          ]
+        }
+      ]
+    }
+  }
+}
diff --git a/tests/fixtures/non-machine/known-bad.json b/tests/fixtures/non-machine/known-bad.json
new file mode 100644
index 00000000..ea0ca279
--- /dev/null
+++ b/tests/fixtures/non-machine/known-bad.json
@@ -0,0 +1,95 @@
+{
+  "$comment": "Known-bad: the copies of each document as they stood before the machine checks (each fails for the reason tests/test_non_machine_vv.py names), plus a document citing an unknown decision and two with a wrong or unstated tagged count.",
+  "schema": "non-machine-resources/2",
+  "max_age_days": 92,
+  "resources": [
+    {
+      "id": "NMR-KB-ROB",
+      "path": "tests/fixtures/non-machine/known-bad/rules-of-behavior.md",
+      "kind": "procedure",
+      "title": "t",
+      "owner": "Sam Aydlette (operator)",
+      "verifies": "machine checks"
+    },
+    {
+      "id": "NMR-KB-IA",
+      "path": "tests/fixtures/non-machine/known-bad/ia-policy.md",
+      "kind": "policy",
+      "title": "t",
+      "owner": "Sam Aydlette (operator)",
+      "verifies": "machine checks"
+    },
+    {
+      "id": "NMR-KB-SLA",
+      "path": "tests/fixtures/non-machine/known-bad/evidence-sla-alarm.md",
+      "kind": "procedure",
+      "title": "t",
+      "owner": "Sam Aydlette (operator)",
+      "verifies": "machine checks"
+    },
+    {
+      "id": "NMR-KB-CONMON",
+      "path": "tests/fixtures/non-machine/known-bad/continuous-monitoring-plan.md",
+      "kind": "plan",
+      "title": "t",
+      "owner": "Sam Aydlette (operator)",
+      "verifies": "machine checks"
+    },
+    {
+      "id": "NMR-KB-PTA",
+      "path": "tests/fixtures/non-machine/known-bad/privacy-threshold-analysis.md",
+      "kind": "record",
+      "title": "t",
+      "owner": "Sam Aydlette (operator)",
+      "verifies": "machine checks"
+    },
+    {
+      "id": "NMR-KB-CA",
+      "path": "tests/fixtures/non-machine/known-bad/ca-policy.md",
+      "kind": "policy",
+      "title": "t",
+      "owner": "Sam Aydlette (operator)",
+      "verifies": "machine checks"
+    },
+    {
+      "id": "NMR-KB-RECOVERY",
+      "path": "tests/fixtures/non-machine/known-bad/recovery-plan.md",
+      "kind": "plan",
+      "title": "t",
+      "owner": "Sam Aydlette (operator)",
+      "verifies": "machine checks"
+    },
+    {
+      "id": "NMR-KB-PL",
+      "path": "tests/fixtures/non-machine/known-bad/pl-policy.md",
+      "kind": "policy",
+      "title": "t",
+      "owner": "Sam Aydlette (operator)",
+      "verifies": "machine checks"
+    },
+    {
+      "id": "NMR-KB-DEC",
+      "path": "tests/fixtures/non-machine/known-bad/unknown-decision.md",
+      "kind": "procedure",
+      "title": "t",
+      "owner": "Sam Aydlette (operator)",
+      "verifies": "machine checks"
+    },
+    {
+      "id": "NMR-KB-COUNT",
+      "path": "tests/fixtures/non-machine/known-bad/wrong-count.md",
+      "kind": "procedure",
+      "title": "t",
+      "owner": "Sam Aydlette (operator)",
+      "verifies": "machine checks"
+    },
+    {
+      "id": "NMR-KB-UNSTATED",
+      "path": "tests/fixtures/non-machine/known-bad/unstated-count.md",
+      "kind": "procedure",
+      "title": "t",
+      "owner": "Sam Aydlette (operator)",
+      "verifies": "machine checks"
+    }
+  ]
+}
diff --git a/tests/fixtures/non-machine/known-bad/ca-policy.md b/tests/fixtures/non-machine/known-bad/ca-policy.md
new file mode 100644
index 00000000..07b3243d
--- /dev/null
+++ b/tests/fixtures/non-machine/known-bad/ca-policy.md
@@ -0,0 +1,13 @@
+# CA — Assessment, Authorization, and Monitoring
+
+There is no formal authorization process or independent assessor in scope for this PoC; the controls that depend on a third-party assessor or an authorizing official (CA-2/2.1, CA-6, CA-7.1, CA-8/8.1/8.2) are marked not-applicable in the control projection, published per control in the SDR (`rev5_controls`). CA-7 (Continuous Monitoring) is the central live control of the family and is satisfied by:
+
+- The runtime KSI emitter — daily revalidation of the live state versus the deploy-time signal, drift surfaced at `/.well-known/ksi-signal-runtime.json`.
+- The deploy-time OPA gate — every PR re-evaluates the Terraform plan, the website tree, and the IAM policy against in-house Rego.
+- The build-time VDR aggregator (see RA) — every CI run re-aggregates vulnerability state across SAST/SCA tools and blocks the build if any finding exceeds Class C remediation timeframes. The build is the report.
+
+**20x rule integration.** This family carries Vulnerability Detection and Response (VDR-*) and Collaborative Continuous Monitoring (CCM). VDR is satisfied as described above and in RA. CCM is satisfied by the public-by-default publication of all KSI/SSP/runtime/VDR artifacts at `/.well-known/`, signed via Sigstore, verifiable from anywhere — anyone can run continuous monitoring of this system without privileged access.
+
+The consolidated continuous-monitoring strategy (mechanisms, cadences, reporting, role mapping, NIST control coverage) is documented in [`docs/continuous-monitoring-plan.md`](../continuous-monitoring-plan.md), the document that backs CA-7 specifically.
+
+**Review cadence.** Continuous (automated); annual structural review.
diff --git a/tests/fixtures/non-machine/known-bad/continuous-monitoring-plan.md b/tests/fixtures/non-machine/known-bad/continuous-monitoring-plan.md
new file mode 100644
index 00000000..4f7a6afa
--- /dev/null
+++ b/tests/fixtures/non-machine/known-bad/continuous-monitoring-plan.md
@@ -0,0 +1,103 @@
+# Continuous Monitoring Plan
+
+## Purpose
+
+This Continuous Monitoring Plan (CMP) describes the strategy and mechanisms by which the system maintains awareness of its security posture between formal authorization decisions, per NIST SP 800-37 Risk Management Framework step 6 (Monitor) and the FedRAMP 20x Collaborative Continuous Monitoring (CCM) rule. The CMP names what is monitored, by what mechanism, on what cadence, where the results are published, and how an authorizing official or independent reviewer can verify the monitoring is happening.
+
+## Scope
+
+The full system as defined in the [authorization boundary](../website/research/authorization-boundary.html), including all components inside the boundary (Cloud Service Offering internals, leveraged AWS services, and external services without FedRAMP ATO that are in boundary per Rule of Thumb #2).
+
+The Silk Reeling Mirror app is **active in production** (`create_silk_reeling = true` in the main deploy pipeline; live since 2026-06-03), so the scope includes its components — the app Lambda (Python 3.13 ZIP), the API Gateway HTTP API, and the customer-managed KMS key. These were introduced under [SCN-2026-001](scn/SCN-2026-001-silk-reeling.md) (Adaptive); the app's Secrets Manager secret and its external Anthropic API interconnection were removed under [SCN-2026-006](scn/SCN-2026-006-remove-anthropic-interconnection.md). Their dependency ecosystems (PyPI, the SPA's npm tree) are monitored by mechanism 2 via the Syft+Grype SCA source.
+
+## Monitoring Mechanisms
+
+Five mechanisms operate concurrently:
+
+**1. Deploy-time policy gate (per pull request).** Every PR triggers the OPA compliance gate (the `infrastructure/policy/` packages evaluated by `scripts/terraform-plan.sh`). The gate evaluates the Terraform plan, the website tree, and the IAM policy against in-house Rego rules. PR cannot merge if the gate fails. Frequency: per PR.
+
+**2. Build-time vulnerability evaluation (per deploy).** Every deploy runs the VDR aggregator (`scripts/build-vdr-report.py`) which ingests OPA gate output, Checkov SARIF, tfsec JSON, Dependabot alerts, Grype SCA output (Syft SBOM → Grype, over the built Silk Reeling Lambda + SPA artifact — the detection source for the app's PyPI and client-JS dependencies), and the CISA KEV catalog. Findings are classified per FedRAMP 20x VDR-EVA-* (PAIN N1-N5, IRV, LEV, KEV) and emitted as `/.well-known/vdr-report.json`. The build is the report. Build blocks if any finding exceeds Class C tolerance. Frequency: per deploy (which exceeds VER-TFR-MHR's monthly minimum).
+
+**3. Runtime configuration revalidation (daily).** An AWS Lambda (`infrastructure/lambda/index.js`) runs daily on an EventBridge schedule. It loads the same `policy.wasm` compiled at deploy time (so deploy-time and runtime evaluate identical compiled bytes), queries the live AWS configuration of every cloud component named in the canonical inventory, and re-evaluates each policy. Results are published as `/.well-known/ksi-signal-runtime.json`. Drift between the deploy-time signal and the runtime signal is the externally-visible drift detector. Frequency: daily.
+
+**4. Evidence freshness alerting (hourly).** Published reporting must be under 24 hours old, and an alert that only lands in a GitHub notifications tab is not an alert: from 2026-09-09 to 2026-09-24 the nightly VDR refresh failed every night without reaching the operator. The evidence SLA watchdog ([`infrastructure/watchdog.tf`](../infrastructure/watchdog.tf)) runs hourly on AWS's clock, reads every artifact listed in the governed freshness configuration ([`infrastructure/schemas/freshness-config.json`](../infrastructure/schemas/freshness-config.json): the VDR, the runtime signal, the nightly's status beacon `vdr-status.json` and every other signed output under `/.well-known/`) from the site bucket, and publishes the VDR's and runtime signal's ages, the nightly's last result and the number of artifacts past their window as CloudWatch metrics. Four alarms page the operator by email through a CMK-encrypted SNS topic, with a recovery email when each clears: the VDR older than its window (24 hours), the runtime signal older than its window (26 hours), the nightly failed or silent for 26 hours, and any listed artifact past its governed window (24 hours for nightly evidence, 26 for the runtime signal and beacon, 30 days for deploy-generated artifacts and the operator-run corroboration). Missing data counts as a breach, so a dead watchdog pages too. The nightly runs twice a day, which keeps the VDR well inside the 24-hour policy so the alarm fires on real misses, not on GitHub's late crons. Response: [`docs/runbooks/evidence-sla-alarm.md`](runbooks/evidence-sla-alarm.md). Frequency: hourly.
+
+**5. Annual structural review.** Documented in [`docs/security-review.md`](security-review.md). The review re-examines (a) cost/benefit of risk-accepted items, (b) whether the threat model still holds, (c) whether the conscious trade-offs in the README still apply. Frequency: annual, plus after any Transformative significant change per SCN.
+
+**6. Independent corroboration (operator-run, at least every 30 days).** [`tools/boundary-map/corroborate.py`](../tools/boundary-map/corroborate.py) checks the published evidence against sources the pipeline does not control: RAMPART on TAP (The Analogy Platform) reading AWS and GitHub with read-only credentials, and FedRAMP's rules read directly. It compares the boundary map with the live account, re-verifies every published signature with an independent Sigstore verifier, matches each signing run to GitHub's record of it, compares the configuration the artifacts claim with what AWS reports, checks the runtime signing key in KMS against its published and pinned copies, compares open Dependabot alerts with the VDR, and checks the claimed KSIs against FedRAMP's current catalog. A section that could not be checked is reported as such, never as agreement. The signed report is published at `/.well-known/boundary-corroboration.json`; the trust center shows each section and asks for attention on any difference, any unchecked section, or a report older than 30 days. Detail: [`tools/boundary-map/README.md`](../tools/boundary-map/README.md). Frequency: at least every 30 days.
+
+## Reporting
+
+These artifacts are published continuously at `/.well-known/`:
+
+- `ksi-signal.json` — the FedRAMP 20x KSI signal (Sigstore-signed); per-deploy emission
+- `ksi-signal-runtime.json` — the daily runtime revalidation, signed with an asymmetric KMS key (ECC NIST P-256); the signature is carried in `provenance.attestation` and verifiable against `runtime-signing-pubkey.pem` (POAM-002)
+- `runtime-signing-pubkey.pem` — the public key for verifying the runtime signal's signature
+- `security-decision-record.json` — the CR26 Security Decision Record (per-KSI and per-Rev5-control records; replaces the SSP), Sigstore-signed with an in-toto attestation; per-deploy emission
+- `certification-package-overview.json` — the CR26 Certification Package Overview, Sigstore-signed; per-deploy emission
+- `vdr-report.json` — the FedRAMP 20x VDR report; per-deploy emission
+- `vdr-report.md` — human-readable VDR rendering (VER-TFR-MHR)
+- `ongoing-certification-report.json` / `.md` — the quarterly Ongoing Certification Report (CCM-OCR-AVL), Sigstore-signed; carries the eight required summaries plus the target dates for the next report (CCM-OCR-NRD) and next quarterly review (CCM-QTR-NRD)
+
+All artifacts carry FedRAMP-namespaced provenance (deploy chain identity, system-id, ownership block). The deploy-time signal is signed via Sigstore keyless with verification anchored in the public Rekor transparency log; an external consumer can verify integrity via `cosign verify-blob` without trusting this site.
+
+**Quarterly Ongoing Certification Report.** CR26 CCM is a quarterly cycle, not a stream. `ongoing-certification-report.json` (CCM-OCR-AVL) is regenerated on every deploy from the system's own artifacts and carries the eight required summaries — changes to certification data (from the SCN register), planned changes (open POA&M items), accepted vulnerabilities (from the VDR), transformative changes, updated recommendations, agencies using the product (none), a FedRAMP-Reportable-Incident attestation (none — no federal data), and lessons learned (none) — plus the next-report and next-review target dates. The five monitoring mechanisms above feed it; per-deploy emission keeps it current and overshoots the 3-month floor.
+
+This implements the **publication half** of FedRAMP 20x Collaborative Continuous Monitoring (CCM): every monitoring artifact is publicly retrievable and signature-verifiable, and the quarterly Ongoing Certification Report is produced as a distinct deliverable, so any reviewer can fetch and verify the current posture without trusting this site. The relationship-dependent rules — the synchronous Quarterly Review (CCM-QTR-MTG), the feedback channel (CCM-OCR-FBM), and the anonymized feedback summary (CCM-OCR-AFS) — are N/A absent a consuming agency, as the scope note below explains.
+
+**Honest scope — the collaborative half is N/A here, not done.** CCM is a two-party relationship: a CSP publishes, and a *consuming agency / authorizing official* reviews on an agreed cadence, raises significant-change and finding concerns, and makes risk decisions that feed back into the CSP's posture. This system has **no agency sponsor and no consuming agency** (it is a public proof of concept with no federal data). So the relationship-dependent obligations — the agency-side review cadence, the collaborative finding-disposition loop, the authorizing-official sign-off — are **not applicable**, because there is no counterparty to exercise them. What is built is the mechanism a CSP would use to *support* CCM; what is absent is the relationship that gives it meaning. Claiming CCM is "satisfied" would overstate it: the closed monitoring loop does not exist, and cannot, until a consuming party is onboarded.
+
+## Vulnerability Detection and Response (VDR) cadence (Class C)
+
+The system targets 20x Class C. Per VDR-TFR-PVR Class C (full table reproduced in [`docs/policies/ra-policy.md`](policies/ra-policy.md)):
+
+- N5 + LEV + IRV: 2 days to mitigation
+- N5 + LEV + NIRV: 4 days
+- N4 + LEV + IRV: 4 days
+- N4 + LEV + NIRV: 8 days
+- N3 + LEV + IRV: 16 days
+- ... and so on
+
+The VDR aggregator blocks the build on (a) any KEV-listed CVE without remediation, even when dispositioned; (b) any undispositioned N5 + LEV + IRV finding; and (c) any undispositioned finding past its Class C SLA. The clock runs from first detection: the previous published VDR report serves as the first-detected ledger, so each finding keeps its original `first_detected` across builds.
+
+## Significant Change Notification (SCN) integration
+
+Significant changes to the system are governed by the FedRAMP 20x SCN rule (full integration in [`docs/policies/cm-policy.md`](policies/cm-policy.md)). Every PR carries an SCN-Type tag (Adaptive / Routine Recurring / Transformative); the CI workflow validates the tag. Git history is the SCN audit record (SCN-CSO-MAR). Transformative-class changes trigger a CMP review.
+
+## Roles and responsibilities
+
+Sole-operator system. The operator is the System Owner, the Continuous Monitoring lead, and the Incident Response lead. The runtime KSI emitter is an automated agent in the monitoring chain.
+
+### Separation of duties (AC-5) — structurally constrained, with compensating controls
+
+A single human cannot satisfy AC-5 separation of duties in the conventional sense: there is no second person to provide an independent check, no maker/checker split, no segregation between the person who changes the system and the person who reviews the change. This is an inherent, **honestly acknowledged** limitation of a sole-operator system, not something tooling can fix. It does not generalize to the scaled version this repo is a proof of concept for, where these duties would be split across distinct roles.
+
+The compensating controls that stand in for a second human are **automated and non-human reviewers** in the change path, each independent of the operator's intent:
+
+- **The fail-closed reconciliation gate** is an independent reviewer the operator cannot satisfy by assertion: it re-derives the artifacts from live cloud state and blocks publication if anything drifts — the operator cannot merge a claim the live account contradicts.
+- **The OPA pre-deploy gate + Checkov** evaluate policy against the Terraform plan before any apply; a noncompliant change is rejected regardless of operator intent.
+- **GitOps audit trail.** Every change is a reviewable commit/PR; git history is the immutable record of who changed what and when (the SCN audit record). There is no out-of-band path to production.
+- **Sigstore signing + the public Rekor log** make every published artifact tamper-evident to anyone, so the operator cannot quietly substitute a different artifact after the fact.
+- **GitHub OIDC deploy role (no standing key)** means the deploy identity is a short-lived, workflow-scoped token, not a credential the operator holds and could use out-of-band.
+
+Together these provide *machine* independence in place of *human* independence: the operator can author changes but cannot unilaterally push an unreviewed, noncompliant, or tampered state to production without the automation refusing. This bounds the sole-operator risk; it does not eliminate the structural single-person constraint, which is recorded here as a residual.
+
+## Effectiveness review
+
+Quarterly review of the runtime KSI signal against the deploy-time signal: are they reconciling? Are any drift events recorded? Are any findings persisting past their Class C SLAs?
+
+Annual structural review per [`docs/security-review.md`](security-review.md).
+
+## Reference: 20x rules and NIST controls satisfied
+
+- FedRAMP 20x Collaborative Continuous Monitoring (CCM-OCR-* and CCM-QTR-* rules) — the quarterly Ongoing Certification Report (`CCM-OCR-AVL`) and the next-report/next-review dates (`CCM-OCR-NRD` / `CCM-QTR-NRD`) are produced and published; mechanisms 1-4 feed it. The synchronous Quarterly Review (`CCM-QTR-MTG`), feedback channel (`CCM-OCR-FBM`), and feedback summary (`CCM-OCR-AFS`) are **N/A** absent a consuming agency (see scope note above)
+- FedRAMP 20x Vulnerability Detection and Response (VDR-* rules) — covered by mechanism 2
+- FedRAMP 20x Significant Change Notifications (SCN-* rules) — covered by SCN PR tag
+- KSI-MLA family (Monitoring, Logging, Auditing) — covered across all mechanisms
+- KSI-SVC-EIS (Continuous Improvement) — covered by drift detection + annual review
+- NIST CA-7 (Continuous Monitoring) — primary control implemented by this plan
+- NIST CA-7.4 (Risk Monitoring) — covered by VDR cadence
+- NIST CM-3 (Configuration Change Control) — covered by SCN
+- NIST RA-5 (Vulnerability Monitoring and Scanning) — covered by mechanism 2
+- NIST SI-4 (System Monitoring) — covered by mechanisms 1-4
+- NIST IR-6 (Incident Reporting) — the operator is paged on evidence-freshness breaches by mechanism 4
diff --git a/tests/fixtures/non-machine/known-bad/evidence-sla-alarm.md b/tests/fixtures/non-machine/known-bad/evidence-sla-alarm.md
new file mode 100644
index 00000000..c0781eb0
--- /dev/null
+++ b/tests/fixtures/non-machine/known-bad/evidence-sla-alarm.md
@@ -0,0 +1,80 @@
+# Runbook: an evidence SLA alarm fired
+
+The evidence SLA watchdog (`infrastructure/watchdog.tf`) emails the operator through the `samaydlette-com-evidence-alerts` SNS topic when published compliance evidence goes stale. It runs hourly on AWS's clock, independent of GitHub, and pages when a metric breaches in 2 of the last 3 hourly periods. When an alarm clears you get an OK email.
+
+| Alarm (`samaydlette-com-evidence-watchdog-…`) | Fires when | Usually means |
+|---|---|---|
+| `nightly-failed` | the evidence nightly's last run failed, or no run has reported in 26h | a gate failed; or the cron is disabled or stuck |
+| `vdr-age` | the published VDR is more than 24h old | the reporting policy is breached; nightly runs have failed or stopped |
+| `runtime-age` | the runtime signal is more than 26h old | the daily runtime-check Lambda has failed or stopped |
+| `incident-report-overdue` | an incident report listed as due in `/.well-known/incident-reports.json` is past its Class C deadline, or the incident log is missing or unreadable | an Initial, Ongoing or Final incident report was not issued in time; or a vulnerability that is a FedRAMP Reportable Incident (VER-TFR-IRI/NRI) has no incident opened |
+| `artifact-stale` | any artifact listed in `infrastructure/schemas/freshness-config.json` is past its window, missing, or has no readable timestamp | no deploy within the deploy-cadence window; the corroboration was not re-run; or one of the above |
+
+The windows are governed values in `infrastructure/schemas/freshness-config.json`; the thresholds above are read from it. Change a window there, through review, never in the alarm.
+
+Any alarm also fires if the watchdog stops publishing metrics, because missing data counts as a breach. If all five fire together, check the watchdog itself first (a missing or invalid freshness config stops it before it publishes anything).
+
+## `nightly-failed`
+
+1. Open the latest **Evidence Nightly** run in GitHub Actions. The status beacon at `/.well-known/vdr-status.json` gives its workflow and commit (`run`; no run ID is published), its finish time, the overall `result`, and each gate's outcome; find the run in the Actions list by that time.
+2. The GitHub issue labelled `evidence-freshness` names the gate and, for a vulnerability-gate failure, each finding with its advisory and any open Dependabot PR.
+   - **Vulnerability gate failed:** follow [`vuln-gate-failure.md`](vuln-gate-failure.md).
+   - **Reconciliation gate failed:** the live system and its documentation disagree. The step log names the failing invariant. Fix the drift through the reviewed deploy path; never weaken the gate.
+   - **`not reached` everywhere, or no recent run at all:** check whether GitHub has disabled the workflow's schedule (**Actions → Evidence Nightly**; it does this after 60 days without repository activity) and re-enable it. Then run it once by hand.
+3. Close the alert issue once a run passes. The alarm clears on its own within about two hours.
+
+## `vdr-age`
+
+The policy is already breached, so treat this as the priority. It usually follows `nightly-failed`: fix that, and the next passing run republishes the VDR. The nightly runs twice a day, so a single late run should not reach 24h. If the nightly is passing but the VDR is still old, the publish or CloudFront step is at fault. The run's "Assert published evidence is fresh at the edge" step says which.
+
+## `runtime-age`
+
+Check the compliance Lambda (`samaydlette-com-opa-compliance`): its CloudWatch logs, its EventBridge rule, and the shared dead-letter queue `samaydlette-com-opa-compliance-dlq` for failed invocations.
+
+## `incident-report-overdue`
+
+The published incident log (`/.well-known/incident-reports.json`, `obligations_due`) names each report still due, for which incident or finding, and its deadline. Follow [`docs/incident-response.md`](../incident-response.md#reporting-fedramp-reportable-incidents-iec): record the report (or, for a finding with no incident, open the incident) in `data/incidents.json` and push it; the **Incident Reports** workflow validates, builds, signs and publishes within minutes, and the alarm clears once the republished log no longer lists the report as due. If the log itself is missing or unreadable, run the workflow by hand and check its publish step.
+
+## `artifact-stale`
+
+The watchdog's log line for the run lists the stale artifacts under `stale`. To see the same from outside, run `python3 scripts/check-evidence-freshness.py --all https://samaydlette.com`.
+
+- **Deploy-cadence artifacts** (KSI signal, SSP, POA&M, trust center, boundary map, CDS artifacts): no deploy has run inside the window. Start and approve a deploy.
+- **`boundary-corroboration.json`:** re-run `tools/boundary-map/corroborate.py`, commit the result, and deploy.
+- **Nightly artifacts** (`vdr-*`): follow `nightly-failed` / `vdr-age` above.
+
+## All five at once
+
+Check the watchdog: its log group `/aws/lambda/samaydlette-com-evidence-watchdog`, the dead-letter queue, and its EventBridge rule. Each run logs one JSON line with the values it published, the config version, and the stale artifacts.
+
+## Setup and testing (operator)
+
+The email subscription is **not** in Terraform, deliberately: an address in Terraform ends up in state and in the plan artifact CI uploads for a public repository. Create it once, with your own credentials:
+
+```sh
+aws sns subscribe --region us-east-2 \
+  --topic-arn "$(aws sns list-topics --region us-east-2 --query "Topics[?ends_with(TopicArn, ':samaydlette-com-evidence-alerts')].TopicArn" --output text)" \
+  --protocol email --notification-endpoint 
+```
+
+Then confirm the subscription from the email AWS sends.
+
+To test end to end, force one alarm into ALARM and back. This proves the whole delivery path, including the KMS grant that lets CloudWatch publish to the encrypted topic, which otherwise fails silently:
+
+```sh
+aws cloudwatch set-alarm-state --region us-east-2 \
+  --alarm-name samaydlette-com-evidence-watchdog-nightly-failed \
+  --state-value ALARM --state-reason "manual end-to-end test"
+```
+
+An email should arrive within a minute. The alarm returns to its real state at the next evaluation.
+
+## Silencing
+
+To stop the emails during planned work, disable alarm actions rather than deleting anything:
+
+```sh
+aws cloudwatch disable-alarm-actions --region us-east-2 --alarm-names 
+```
+
+Re-enable them with `enable-alarm-actions`. The next deploy also restores them.
diff --git a/tests/fixtures/non-machine/known-bad/ia-policy.md b/tests/fixtures/non-machine/known-bad/ia-policy.md
new file mode 100644
index 00000000..636414f3
--- /dev/null
+++ b/tests/fixtures/non-machine/known-bad/ia-policy.md
@@ -0,0 +1,15 @@
+# IA — Identification and Authentication
+
+Three authentication chains exist:
+
+1. **Operator → GitHub:** username + password + MFA via Duo. All pushes to `main` require this chain plus passing branch protection checks.
+2. **GitHub Actions → AWS:** long-lived AWS access keys stored as GitHub Actions encrypted secrets. Migration to GitHub OIDC role assumption is tracked as POAM-001 (now DEC-001) in [`data/decisions.json`](../../data/decisions.json). Until that migration completes, the deployer principal is the largest standing-privilege surface in the system. As an active compensating control while POAM-001 remains open, the AWS access key is rotated every 90 days per the procedure in the [Secure Configuration Guide](secure-configuration-guide.md); rotation events are logged in [`security-review.md`](../security-review.md).
+3. **Lambda → AWS:** AWS IAM execution role with no human-assumable trust policy. The role's only invoker is the EventBridge scheduled rule.
+
+Sigstore keyless signing uses GitHub Actions OIDC for ephemeral identity proof; no signing keys are stored anywhere. Fulcio issues a short-lived X.509 certificate per workflow run, the signature is recorded in Rekor, and verification is anchored in the public transparency log.
+
+Several IA enhancements (network access for non-privileged accounts in AWS infrastructure, identifier management for AWS-side identities) are inherited from AWS East/West Moderate FedRAMP authorization (Package ID: AGENCYAMAZONEW).
+
+**20x rule integration.** Operator-side complement to KSI-IAM. Cryptographic primitives used in authentication are governed under SC and the Using Cryptographic Modules (UCM) rule.
+
+**Review cadence.** Annually.
diff --git a/tests/fixtures/non-machine/known-bad/pl-policy.md b/tests/fixtures/non-machine/known-bad/pl-policy.md
new file mode 100644
index 00000000..5e6d8b64
--- /dev/null
+++ b/tests/fixtures/non-machine/known-bad/pl-policy.md
@@ -0,0 +1,11 @@
+# PL — Planning
+
+Under CR26 the system security plan is replaced by the Security Decision Record at `/.well-known/security-decision-record.json` and the Certification Package Overview at `/.well-known/certification-package-overview.json`. The SDR records how each KSI is met and, in `rev5_controls`, each applicable Rev5 control's parameters, status, mechanisms, verification and validation (`SDR-CSF-CTF`). Both are generated deterministically from the canonical inventory and the FedRAMP KSI catalog through the control projection (`scripts/_controls.py`) and signed via Sigstore keyless on every deploy; the SDR also carries an in-toto provenance attestation. The OSCAL SSP that used to fill this role was retired on 2026-11-05.
+
+The KSI signal at [`/.well-known/ksi-signal.json`](../../website/.well-known/ksi-signal.json) is the FedRAMP 20x companion artifact, also signed and published per deploy.
+
+The architectural decision record [`architecture-decisions.md`](../architecture-decisions.md) captures the rationale for system-level decisions (PL-2 approach, threat model under SA-11.2, KSI-aligned justifications). The full set of family policies in this folder satisfies the per-family `-1` controls.
+
+**20x rule integration.** KSI-PIY (Policy and Inventory). The 20x meta-process rules — FedRAMP Certification (`CRT-*`), Certification Data Sharing (`CDS-*`), and Marketplace Listing (`MKT-*`) — are documented in this PoC at the procedure level. The system is not actually FedRAMP-certified, so the obligations these rules impose (data sharing to FedRAMP, marketplace metadata accuracy) are demonstrated rather than executed.
+
+**Review cadence.** Annually with the [security review](../security-review.md), plus after Transformative changes per SCN.
diff --git a/tests/fixtures/non-machine/known-bad/privacy-threshold-analysis.md b/tests/fixtures/non-machine/known-bad/privacy-threshold-analysis.md
new file mode 100644
index 00000000..bfe226c9
--- /dev/null
+++ b/tests/fixtures/non-machine/known-bad/privacy-threshold-analysis.md
@@ -0,0 +1,62 @@
+# Privacy Threshold Analysis (PTA)
+
+## Purpose
+
+Per OMB Circular A-130 and NIST SP 800-122, this Privacy Threshold Analysis records whether the system processes, stores, or transmits Personally Identifiable Information (PII) and, if so, whether a full Privacy Impact Assessment (PIA) is warranted.
+
+## Determination
+
+**The system does not process, store, or transmit PII.** A full PIA is not required at this time.
+
+## Scope reviewed
+
+The following surfaces of the system were examined for PII handling:
+
+- **Public site content** (`website/**/*.html`): static personal-portfolio content, blog posts, research papers. No PII collected from readers.
+- **Forms / interactive endpoints**: the base site has no forms, no comment systems, no contact submission forms, and no user accounts. The one interactive endpoint is the gated **Silk Reeling Mirror** app (see its dedicated bullet below), added under [SCN-2026-001](scn/SCN-2026-001-silk-reeling.md).
+- **Silk Reeling Mirror app** (`infrastructure/silk-reeling.tf`, active in production — `create_silk_reeling = true` in the main deploy pipeline, live since 2026-06-03): a movement-feedback app gated by HTTP Basic Auth.
+  - **Authentication**: a single **operator-set shared credential** (username/password) in Secrets Manager. It is not collected from end users, is not tied to a person, and there are no end-user accounts — so it is operator-administered configuration, not third-party PII.
+  - **Pose input**: the camera feed and pose extraction run **client-side in the browser**; raw video never leaves the device. The per-frame body landmarks the browser extracts (33 points per frame, no images) are sent over TLS to the app Lambda, which scores them and writes the feedback text itself. Nothing is sent to a third party: the app's optional LLM-written feedback is disabled in this deployment, and the Anthropic interconnection it used was removed under [SCN-2026-006](scn/SCN-2026-006-remove-anthropic-interconnection.md).
+  - **Persistence**: requests are stateless; pose frames are transient and not persisted. No user profile, history, or biometric template is stored.
+- **Analytics**: none. No JavaScript analytics, no tracking pixels, no third-party tracking. CloudFront access logs are excluded for cost.
+- **Cookies**: none set by the site. The only cookies that could touch a reader's browser are AWS-default CloudFront request-routing cookies (no user identification, no persistence beyond request).
+- **Lambda runtime KSI emitter**: processes only AWS configuration metadata (S3 bucket configuration, CloudFront distribution settings). No PII inputs, no PII outputs.
+- **CI/CD chain**: GitHub Actions, AWS API calls, Sigstore signing. No PII transits this chain.
+- **Published artifacts at `/.well-known/`**: KSI signal, VDR report, Security Decision Record, Certification Package Overview, IIW CSV, security.txt. None contains PII. Asset identifiers, system IDs, component names, and provenance are operational metadata, not PII.
+- **Operator's name and email** in the Certification Package Overview (accountable official) and in `security.txt`: the operator is a public author and consents to publication of their name and contact email for system-administration purposes. This is professional contact information published deliberately, not PII collected from a third party.
+
+## Federal customer data
+
+There is no federal agency customer of this system today. No federal customer data is processed, stored, or transmitted.
+
+## Re-assessment triggers
+
+The PTA is reopened and re-determined if any of the following changes:
+
+- The system adds end-user accounts, authentication, or any form-collected input
+- The system adds analytics that collect identifiable visitor information
+- The system onboards a federal agency customer
+- The system begins processing customer data in any form
+- The system handles employee or vendor PII
+
+Per the FedRAMP 20x Significant Change Notifications rule, any change that introduces PII processing is a Transformative change (`SCN-TRF-*`) and triggers re-assessment of the PTA before the change deploys.
+
+## Determination record
+
+| Field | Value |
+| --- | --- |
+| System | samaydlette.com |
+| Determination | No PII processed |
+| Determination date | 2026-05-08 |
+| Re-determined | 2026-06-07 — re-determination under [SCN-2026-001](scn/SCN-2026-001-silk-reeling.md) (Silk Reeling Mirror app). Determination unchanged: **no PII processed.** Pose video is processed client-side and never leaves the device; only derived non-PII metrics cross the boundary; the app credential is an operator-set shared secret, not third-party PII. No PIA triggered. |
+| Reviewer | Sam Aydlette (operator) |
+| Next review | 2027-05-08 (annual), or upon SCN trigger |
+| Full PIA required | No |
+
+This determination is reviewed annually as part of [`docs/security-review.md`](security-review.md), and re-determined if the system's data-processing posture changes.
+
+## Reference
+
+- NIST SP 800-122: *Guide to Protecting the Confidentiality of Personally Identifiable Information (PII)*
+- OMB Circular A-130: *Managing Information as a Strategic Resource*
+- [`docs/policies/pt-policy.md`](policies/pt-policy.md): the PT family policy that this PTA backs
diff --git a/tests/fixtures/non-machine/known-bad/recovery-plan.md b/tests/fixtures/non-machine/known-bad/recovery-plan.md
new file mode 100644
index 00000000..a44166c5
--- /dev/null
+++ b/tests/fixtures/non-machine/known-bad/recovery-plan.md
@@ -0,0 +1,91 @@
+# Recovery Plan
+
+This document satisfies KSI-RPL-ARP and KSI-RPL-TRC, given the recovery objectives declared per KSI-RPL-RRO:
+
+- **Recovery Time Objective (RTO):** 21 days. The world will be fine without my opinions for three weeks.
+- **Recovery Point Objective (RPO):** 24 hours. Backups are the frequent git commits and S3 object versioning, both of which exceed this granularity by orders of magnitude.
+
+## Scope
+
+In-scope loss scenarios:
+
+- Total loss of the AWS account — recover into a new account
+- Loss of the S3 bucket only — recover from git
+- Loss of the GitHub repository — recover from any local clone
+- Loss of the deployer credentials — issue new ones
+- Loss of the domain — re-register; CDN reconfigures from Terraform
+- Loss of the CI workflow's ability to sign — fall back to unsigned deploys until restored
+
+Out of scope:
+
+- Loss of the human (the author). The site is static and self-hosting; it will continue serving through CloudFront's cached responses and S3 storage for an extended period after any human change. There is no formal succession plan because there is no formal succession requirement. People will manage.
+
+## Recovery procedure
+
+End-state target: site reachable at https://samaydlette.com over TLS, content matching the most recent commit on `main`, runtime KSI signal publishing on schedule.
+
+```bash
+# 1. Restore the source from any clone (the local working copy, GitHub, or any
+# other replica). Git's distributed model means the source is essentially
+# unloseable as long as one clone survives.
+git clone https://github.com/sam-aydlette/samaydlette.com.git
+cd samaydlette.com
+
+# 2. Reprovision AWS resources. If recovering into the existing account, the
+# Terraform state is intact and a plain `make pipeline` is sufficient. If
+# recovering into a new account, the existing-resource references must be
+# recreated first (S3 bucket named after the domain, CloudFront distribution,
+# ACM certificate in us-east-1) before terraform.tfvars is populated and the
+# pipeline runs.
+cd infrastructure
+cp terraform.tfvars.example terraform.tfvars
+# Edit existing_cloudfront_distribution_id, existing_ssl_certificate_arn,
+# existing_s3_bucket_name with the new resource IDs.
+make pipeline   # infrastructure only — this publishes nothing
+
+# 3. Restore content and the published evidence. `make pipeline` stops at
+# `terraform apply`: website content and every artifact under /.well-known/ are
+# published only by the CI deploy job, behind the reconciliation gate and the
+# prod environment approval. Push to `main` and approve the deploy. There is no
+# local publish path, by design — a partial, unsigned artifact set over the
+# published one is the failure mode the gate exists to prevent.
+
+# 4. Verify.
+curl -I https://samaydlette.com/
+curl -s https://samaydlette.com/.well-known/ksi-signal.json | jq '.signal_id, .emitted_at'
+```
+
+The full procedure is bounded by AWS resource creation latency (CloudFront takes about 20 minutes to deploy globally) and DNS propagation (up to 48 hours, typically much less). Realistic recovery is hours, not days. The 21-day RTO is generous on purpose — it's the time the operator is willing to wait, not the time the system needs.
+
+## Backup alignment (KSI-RPL-ABO)
+
+- **Source code:** Distributed across every git clone in existence. RPO is "the time since the last fetch on any clone," which in practice is minutes.
+- **Site content:** Source-controlled and additionally backed up in the S3 bucket itself, which has versioning enabled. Any object can be rolled back to a prior version within S3's standard retention.
+- **Infrastructure config:** Terraform configuration is in the repo. State for managed resources (Lambda, IAM role, EventBridge rule) is in `infrastructure/terraform.tfstate`; for a hard recovery into a new account it can be reconstructed via `terraform import` against the recreated resources.
+- **Build artifacts (KSI signals, bundles):** Reproducible from any commit on `main` by re-running the pipeline. No backup required because they are deterministically regenerable.
+
+The 24-hour RPO is comfortably met. Any change committed to `main` reaches the bucket within the time of one CI run (~5 minutes). The data loss window in the worst case is "whatever is in flight in an open editor at the moment of catastrophe," which is upper-bounded by the operator's typing speed, not by any backup cadence.
+
+## Recovery testing (KSI-RPL-TRC)
+
+KSI-RPL-TRC calls for persistent testing of recovery capability. The site's infrastructure was rebuilt from `terraform.tfvars.example` during the construction of this implementation; effective wall-clock time from "git clone" to "curl returns content" was under one hour, well inside RTO. That counts as a real recovery exercise with a much-larger-than-tabletop scope.
+
+A formal tabletop is run annually, recorded below using this template:
+
+```
+## YYYY-MM-DD: Recovery tabletop
+
+- **Scenario:** 
+- **Steps executed:** 
+- **Wall-clock time to recover:** 
+- **Issues found:** 
+- **Follow-up items:** 
+```
+
+### 2026-05-06: Initial implementation as recovery test
+
+- **Scenario:** Build the entire infrastructure from scratch; treat it as if no AWS resources existed.
+- **Steps executed:** Configure terraform.tfvars, run `make init`, fix the OPA gate failures (h1 accessibility cascade), wire up the runtime Lambda, sign and publish.
+- **Wall-clock time:** Single working day, including substantial new feature development that wouldn't be in a real recovery.
+- **Issues found:** Pre-existing OPA accessibility regex bug surfaced when the subshell-scope bug in `terraform-plan.sh` was fixed.
+- **Follow-up items:** None — both fixed inline.
diff --git a/tests/fixtures/non-machine/known-bad/rules-of-behavior.md b/tests/fixtures/non-machine/known-bad/rules-of-behavior.md
new file mode 100644
index 00000000..d0163144
--- /dev/null
+++ b/tests/fixtures/non-machine/known-bad/rules-of-behavior.md
@@ -0,0 +1,72 @@
+# Rules of Behavior
+
+## Purpose
+
+Per NIST SP 800-53 PL-4, this document records the rules of behavior the system's privileged users acknowledge before being granted access. For a sole-operator system, the privileged-user population is the operator alone; the rules below are the operator's standing commitments.
+
+## Scope
+
+Privileged accounts in scope:
+
+- AWS root account (operator's email)
+- AWS IAM deployer principal (used by GitHub Actions; transitioning to OIDC role per POAM-001)
+- AWS Lambda runtime IAM role (machine identity; non-privileged on most operations)
+- GitHub repository owner (operator's GitHub account)
+- GitHub Actions workflow identity (per-run OIDC token)
+
+The Lambda runtime role and the per-run GitHub OIDC token are machine identities and the rules apply to the operator's behavior in configuring and operating them.
+
+## Operator commitments
+
+By operating this system, the operator commits to the following:
+
+**Authentication.**
+- Multi-factor authentication is enforced via Duo on AWS root and on the GitHub account. The operator does not disable MFA.
+- Long-lived credentials (AWS access keys, GitHub PATs) are not generated unless required, and when required they are stored only in GitHub Actions encrypted secrets.
+- The deployer's long-lived AWS access key is rotated every 90 days per the procedure in the [Secure Configuration Guide](policies/secure-configuration-guide.md) as a compensating control while [POAM-001](../data/decisions.json) (OIDC migration) remains open. Each rotation event is logged in [`docs/security-review.md`](security-review.md).
+- The operator does not share credentials, sessions, or MFA devices with any other person.
+
+**Access discipline.**
+- AWS root is used only for billing, service quotas, and IAM-policy-of-last-resort actions. Day-to-day deploys use the IAM deployer principal.
+- The operator does not perform routine operations from AWS root.
+- The operator's GitHub session is the only authenticated path to push to `main`. Branch protection plus the OPA gate plus the SCN-Type validator constitute the technical enforcement.
+
+**Change management.**
+- The default workflow is direct push to `main`. Pull requests are used only when collaboration or staged review is desired (rare).
+- Every change is Routine Recurring by default; no SCN-Type label is required for routine work. The operator adds `SCN-Type: adaptive` or `SCN-Type: transformative` to the commit message (or PR description when a PR is used) only when the change meets those criteria per `SCN-CSO-EVA`. The fourth recognized value, `SCN-Type: emergency`, is reserved for emergency-change scenarios per `SCN-CSO-EMG`; see [`docs/incident-response.md`](incident-response.md) for the retroactive-documentation obligations that follow.
+- The operator does not bypass the OPA gate, the schema validators, the VDR aggregator, or the SCN tag validator with `--no-verify`-style overrides.
+
+**Information handling.**
+- The operator does not use corporate or personal email to relay vulnerability information about the system. If such relay ever occurs, the email service comes into scope per ROT #2 and the boundary is reopened.
+- The operator does not commit secrets, API keys, or credentials to the repository. GitHub secret scanning with push protection is enforced as a safety net.
+- The operator does not introduce PII processing into the system without first re-evaluating the [Privacy Threshold Analysis](privacy-threshold-analysis.md) and producing the corresponding Privacy Impact Assessment.
+
+**Incident response.**
+- The operator is the IR lead. Detection sources, triage, containment, and after-action recording follow [`docs/incident-response.md`](incident-response.md).
+- Spillage scenarios trigger the IR-9 procedure regardless of severity.
+
+**Continuous monitoring.**
+- The operator reviews the runtime KSI signal at least weekly and reconciles any drift against the deploy-time signal.
+- The operator runs the annual security review per [`docs/security-review.md`](security-review.md).
+
+**Acceptable use of the system's outputs.**
+- Published artifacts at `/.well-known/` are public. The operator does not publish anything to `/.well-known/` that would be confidential, sensitive, or restricted.
+- The operator's threat-model review (in [`architecture-decisions.md`](architecture-decisions.md)) governs what gets published.
+
+## Acknowledgment
+
+The Rules of Behavior are acknowledged by the operator on initial system stand-up and on each annual security review. The acknowledgment record is the security review entry for the corresponding year.
+
+| Field | Value |
+| --- | --- |
+| Operator | Sam Aydlette |
+| Initial acknowledgment | 2026-05-08 |
+| Next review | 2027-05-08 (annual) |
+| Re-acknowledgment trigger | Any Transformative change per SCN |
+
+## Reference
+
+- NIST SP 800-53 PL-4 (Rules of Behavior)
+- [`docs/policies/ac-policy.md`](policies/ac-policy.md): Access Control policy
+- [`docs/policies/secure-configuration-guide.md`](policies/secure-configuration-guide.md): top-level admin account configuration
+- [`docs/incident-response.md`](incident-response.md): incident-response procedures
diff --git a/tests/fixtures/non-machine/known-bad/unknown-decision.md b/tests/fixtures/non-machine/known-bad/unknown-decision.md
new file mode 100644
index 00000000..08f51710
--- /dev/null
+++ b/tests/fixtures/non-machine/known-bad/unknown-decision.md
@@ -0,0 +1,3 @@
+# Known-bad: cites a decision that is not in the register
+
+The exception is recorded in DEC-999.
diff --git a/tests/fixtures/non-machine/known-bad/unstated-count.md b/tests/fixtures/non-machine/known-bad/unstated-count.md
new file mode 100644
index 00000000..8163cf56
--- /dev/null
+++ b/tests/fixtures/non-machine/known-bad/unstated-count.md
@@ -0,0 +1,3 @@
+# Known-bad: a tagged count the line does not state
+
+If all the alarms  fire together, check the watchdog.
diff --git a/tests/fixtures/non-machine/known-bad/wrong-count.md b/tests/fixtures/non-machine/known-bad/wrong-count.md
new file mode 100644
index 00000000..de1faaca
--- /dev/null
+++ b/tests/fixtures/non-machine/known-bad/wrong-count.md
@@ -0,0 +1,3 @@
+# Known-bad: a tagged count the code does not match
+
+If all four  alarms fire together, check the watchdog.
diff --git a/tests/fixtures/non-machine/malformed-entry.json b/tests/fixtures/non-machine/malformed-entry.json
new file mode 100644
index 00000000..e98ea599
--- /dev/null
+++ b/tests/fixtures/non-machine/malformed-entry.json
@@ -0,0 +1,19 @@
+{
+  "$comment": "Known-bad: an entry still carrying a manual attestation (last_verified); verification is machine checks only.",
+  "schema": "non-machine-resources/2",
+  "max_age_days": 92,
+  "resources": [
+    {
+      "id": "NMR-POL-AC",
+      "path": "docs/policies/ac-policy.md",
+      "kind": "policy",
+      "title": "t",
+      "owner": "Sam Aydlette (operator)",
+      "verifies": "machine checks",
+      "last_verified": {
+        "on": "2026-11-05",
+        "decision": "DEC-190"
+      }
+    }
+  ]
+}
diff --git a/tests/fixtures/non-machine/missing-file.json b/tests/fixtures/non-machine/missing-file.json
new file mode 100644
index 00000000..2f381735
--- /dev/null
+++ b/tests/fixtures/non-machine/missing-file.json
@@ -0,0 +1,15 @@
+{
+  "$comment": "Known-bad: a listed file that does not exist.",
+  "schema": "non-machine-resources/2",
+  "max_age_days": 92,
+  "resources": [
+    {
+      "id": "NMR-POL-AC",
+      "path": "docs/policies/no-such-policy.md",
+      "kind": "policy",
+      "title": "t",
+      "owner": "Sam Aydlette (operator)",
+      "verifies": "machine checks"
+    }
+  ]
+}
diff --git a/tests/fixtures/non-machine/window-too-long.json b/tests/fixtures/non-machine/window-too-long.json
new file mode 100644
index 00000000..20012af1
--- /dev/null
+++ b/tests/fixtures/non-machine/window-too-long.json
@@ -0,0 +1,15 @@
+{
+  "$comment": "Known-bad: a window longer than the rule's 3 months.",
+  "schema": "non-machine-resources/2",
+  "max_age_days": 120,
+  "resources": [
+    {
+      "id": "NMR-POL-AC",
+      "path": "docs/policies/ac-policy.md",
+      "kind": "policy",
+      "title": "t",
+      "owner": "Sam Aydlette (operator)",
+      "verifies": "machine checks"
+    }
+  ]
+}
diff --git a/tests/fixtures/plans/README.md b/tests/fixtures/plans/README.md
index 328b8088..2c7eac0b 100644
--- a/tests/fixtures/plans/README.md
+++ b/tests/fixtures/plans/README.md
@@ -23,6 +23,14 @@ ARNs is `123456789012`, the AWS documentation placeholder.
 | `data-source-website-bucket.json` | Production shape: bucket is a data source, only sub-resources planned |
 | `s3-computed-bucket-name.json` | Bucket name unknown until apply; join only possible via `configuration` references |
 | `delete-only.json` | Non-compliant resource being destroyed (must not gate) |
+| `service-stack-compliant.json` | Every service type the runtime emitter re-validates (IAM role + inline policy, Cognito, KMS, log group, API stage + routes, Lambda, SNS, SQS, alarm, schedule, CloudTrail), compliant |
+| `service-stack-computed-key.json` | As above with a log group KMS key unknown until apply: deferred to the runtime check, not failed |
+| `iam-admin-wildcard.json` | Inline role policy allowing `*` on `*` |
+| `iam-oidc-trust-unscoped.json` | GitHub OIDC trust with no subject condition |
+| `cognito-mfa-optional.json` | User pool MFA `OPTIONAL` |
+| `kms-rotation-disabled.json` | Symmetric customer key without rotation |
+| `log-group-unencrypted.json` | Log group with no customer key, known at plan time |
+| `apigw-route-unauthorized.json` | `/api` route without an authorizer |
 | `empty.json`, `garbage.json` | Malformed input; must yield an explicit `input_error`, never a silent pass |
 
 `tests/fixtures/resources/` holds the same resources flattened into the
diff --git a/tests/fixtures/plans/apigw-route-unauthorized.json b/tests/fixtures/plans/apigw-route-unauthorized.json
new file mode 100644
index 00000000..6989b98d
--- /dev/null
+++ b/tests/fixtures/plans/apigw-route-unauthorized.json
@@ -0,0 +1,613 @@
+{
+  "_fixture": {
+    "synthetic": true,
+    "models": "Known-bad: the /api route has no authorizer"
+  },
+  "format_version": "1.2",
+  "terraform_version": "1.9.8",
+  "resource_changes": [
+    {
+      "address": "aws_iam_role.lambda_opa",
+      "mode": "managed",
+      "type": "aws_iam_role",
+      "name": "lambda_opa",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "samaydlette-com-lambda-opa-role",
+          "assume_role_policy": "{\"Version\": \"2012-10-17\", \"Statement\": [{\"Effect\": \"Allow\", \"Action\": \"sts:AssumeRole\", \"Principal\": {\"Service\": \"lambda.amazonaws.com\"}}]}",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_iam_role_policy.lambda_opa",
+      "mode": "managed",
+      "type": "aws_iam_role_policy",
+      "name": "lambda_opa",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "p",
+          "role": "r",
+          "policy": "{\"Version\": \"2012-10-17\", \"Statement\": [{\"Effect\": \"Allow\", \"Action\": [\"s3:GetBucketVersioning\"], \"Resource\": [\"arn:aws:s3:::b\"]}, {\"Effect\": \"Allow\", \"Action\": [\"kms:Sign\"], \"Resource\": [\"arn:aws:kms:us-east-2:123456789012:key/k\"]}]}"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cognito_user_pool.silk_reeling",
+      "mode": "managed",
+      "type": "aws_cognito_user_pool",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "pool",
+          "mfa_configuration": "ON",
+          "password_policy": [
+            {
+              "minimum_length": 14
+            }
+          ],
+          "admin_create_user_config": [
+            {
+              "allow_admin_create_user_only": true
+            }
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_kms_key.at_rest",
+      "mode": "managed",
+      "type": "aws_kms_key",
+      "name": "at_rest",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "description": "k",
+          "enable_key_rotation": true,
+          "is_enabled": true,
+          "customer_master_key_spec": "SYMMETRIC_DEFAULT",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_kms_key.runtime_signing",
+      "mode": "managed",
+      "type": "aws_kms_key",
+      "name": "runtime_signing",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "description": "s",
+          "customer_master_key_spec": "ECC_NIST_P256",
+          "key_usage": "SIGN_VERIFY",
+          "is_enabled": true,
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_log_group.opa_compliance",
+      "mode": "managed",
+      "type": "aws_cloudwatch_log_group",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "/aws/lambda/x",
+          "retention_in_days": 365,
+          "kms_key_id": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_stage.silk_reeling",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_stage",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "$default",
+          "access_log_settings": [
+            {
+              "destination_arn": "arn:aws:logs:us-east-2:123456789012:log-group:/aws/apigateway/x",
+              "format": "{}"
+            }
+          ],
+          "default_route_settings": [
+            {
+              "throttling_rate_limit": 20,
+              "throttling_burst_limit": 10
+            }
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_route.silk_reeling",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_route",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "route_key": "$default",
+          "authorization_type": "NONE"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_route.silk_reeling_api",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_route",
+      "name": "silk_reeling_api",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "route_key": "ANY /api/{proxy+}",
+          "authorization_type": "NONE"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_lambda_function.opa_compliance",
+      "mode": "managed",
+      "type": "aws_lambda_function",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "function_name": "x",
+          "runtime": "nodejs22.x",
+          "kms_key_arn": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_sns_topic.evidence_alerts",
+      "mode": "managed",
+      "type": "aws_sns_topic",
+      "name": "evidence_alerts",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "t",
+          "kms_master_key_id": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_sqs_queue.compliance_dlq",
+      "mode": "managed",
+      "type": "aws_sqs_queue",
+      "name": "compliance_dlq",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "q",
+          "sqs_managed_sse_enabled": true,
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_metric_alarm.evidence",
+      "mode": "managed",
+      "type": "aws_cloudwatch_metric_alarm",
+      "name": "evidence",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "alarm_name": "a",
+          "actions_enabled": true,
+          "alarm_actions": [
+            "arn:aws:sns:us-east-2:123456789012:t"
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_event_rule.opa_compliance",
+      "mode": "managed",
+      "type": "aws_cloudwatch_event_rule",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "e",
+          "state": "ENABLED",
+          "schedule_expression": "rate(1 day)",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudtrail.management",
+      "mode": "managed",
+      "type": "aws_cloudtrail",
+      "name": "management",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "trail",
+          "enable_logging": true,
+          "is_multi_region_trail": true,
+          "enable_log_file_validation": true
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    }
+  ],
+  "configuration": {
+    "root_module": {
+      "resources": []
+    }
+  }
+}
diff --git a/tests/fixtures/plans/cognito-mfa-optional.json b/tests/fixtures/plans/cognito-mfa-optional.json
new file mode 100644
index 00000000..ab10721c
--- /dev/null
+++ b/tests/fixtures/plans/cognito-mfa-optional.json
@@ -0,0 +1,613 @@
+{
+  "_fixture": {
+    "synthetic": true,
+    "models": "Known-bad: user pool MFA optional"
+  },
+  "format_version": "1.2",
+  "terraform_version": "1.9.8",
+  "resource_changes": [
+    {
+      "address": "aws_iam_role.lambda_opa",
+      "mode": "managed",
+      "type": "aws_iam_role",
+      "name": "lambda_opa",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "samaydlette-com-lambda-opa-role",
+          "assume_role_policy": "{\"Version\": \"2012-10-17\", \"Statement\": [{\"Effect\": \"Allow\", \"Action\": \"sts:AssumeRole\", \"Principal\": {\"Service\": \"lambda.amazonaws.com\"}}]}",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_iam_role_policy.lambda_opa",
+      "mode": "managed",
+      "type": "aws_iam_role_policy",
+      "name": "lambda_opa",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "p",
+          "role": "r",
+          "policy": "{\"Version\": \"2012-10-17\", \"Statement\": [{\"Effect\": \"Allow\", \"Action\": [\"s3:GetBucketVersioning\"], \"Resource\": [\"arn:aws:s3:::b\"]}, {\"Effect\": \"Allow\", \"Action\": [\"kms:Sign\"], \"Resource\": [\"arn:aws:kms:us-east-2:123456789012:key/k\"]}]}"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cognito_user_pool.silk_reeling",
+      "mode": "managed",
+      "type": "aws_cognito_user_pool",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "pool",
+          "mfa_configuration": "OPTIONAL",
+          "password_policy": [
+            {
+              "minimum_length": 14
+            }
+          ],
+          "admin_create_user_config": [
+            {
+              "allow_admin_create_user_only": true
+            }
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_kms_key.at_rest",
+      "mode": "managed",
+      "type": "aws_kms_key",
+      "name": "at_rest",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "description": "k",
+          "enable_key_rotation": true,
+          "is_enabled": true,
+          "customer_master_key_spec": "SYMMETRIC_DEFAULT",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_kms_key.runtime_signing",
+      "mode": "managed",
+      "type": "aws_kms_key",
+      "name": "runtime_signing",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "description": "s",
+          "customer_master_key_spec": "ECC_NIST_P256",
+          "key_usage": "SIGN_VERIFY",
+          "is_enabled": true,
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_log_group.opa_compliance",
+      "mode": "managed",
+      "type": "aws_cloudwatch_log_group",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "/aws/lambda/x",
+          "retention_in_days": 365,
+          "kms_key_id": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_stage.silk_reeling",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_stage",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "$default",
+          "access_log_settings": [
+            {
+              "destination_arn": "arn:aws:logs:us-east-2:123456789012:log-group:/aws/apigateway/x",
+              "format": "{}"
+            }
+          ],
+          "default_route_settings": [
+            {
+              "throttling_rate_limit": 20,
+              "throttling_burst_limit": 10
+            }
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_route.silk_reeling",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_route",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "route_key": "$default",
+          "authorization_type": "NONE"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_route.silk_reeling_api",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_route",
+      "name": "silk_reeling_api",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "route_key": "ANY /api/{proxy+}",
+          "authorization_type": "JWT"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_lambda_function.opa_compliance",
+      "mode": "managed",
+      "type": "aws_lambda_function",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "function_name": "x",
+          "runtime": "nodejs22.x",
+          "kms_key_arn": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_sns_topic.evidence_alerts",
+      "mode": "managed",
+      "type": "aws_sns_topic",
+      "name": "evidence_alerts",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "t",
+          "kms_master_key_id": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_sqs_queue.compliance_dlq",
+      "mode": "managed",
+      "type": "aws_sqs_queue",
+      "name": "compliance_dlq",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "q",
+          "sqs_managed_sse_enabled": true,
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_metric_alarm.evidence",
+      "mode": "managed",
+      "type": "aws_cloudwatch_metric_alarm",
+      "name": "evidence",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "alarm_name": "a",
+          "actions_enabled": true,
+          "alarm_actions": [
+            "arn:aws:sns:us-east-2:123456789012:t"
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_event_rule.opa_compliance",
+      "mode": "managed",
+      "type": "aws_cloudwatch_event_rule",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "e",
+          "state": "ENABLED",
+          "schedule_expression": "rate(1 day)",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudtrail.management",
+      "mode": "managed",
+      "type": "aws_cloudtrail",
+      "name": "management",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "trail",
+          "enable_logging": true,
+          "is_multi_region_trail": true,
+          "enable_log_file_validation": true
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    }
+  ],
+  "configuration": {
+    "root_module": {
+      "resources": []
+    }
+  }
+}
diff --git a/tests/fixtures/plans/iam-admin-wildcard.json b/tests/fixtures/plans/iam-admin-wildcard.json
new file mode 100644
index 00000000..383147e3
--- /dev/null
+++ b/tests/fixtures/plans/iam-admin-wildcard.json
@@ -0,0 +1,613 @@
+{
+  "_fixture": {
+    "synthetic": true,
+    "models": "Known-bad: an inline role policy grants every action on every resource"
+  },
+  "format_version": "1.2",
+  "terraform_version": "1.9.8",
+  "resource_changes": [
+    {
+      "address": "aws_iam_role.lambda_opa",
+      "mode": "managed",
+      "type": "aws_iam_role",
+      "name": "lambda_opa",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "samaydlette-com-lambda-opa-role",
+          "assume_role_policy": "{\"Version\": \"2012-10-17\", \"Statement\": [{\"Effect\": \"Allow\", \"Action\": \"sts:AssumeRole\", \"Principal\": {\"Service\": \"lambda.amazonaws.com\"}}]}",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_iam_role_policy.lambda_opa",
+      "mode": "managed",
+      "type": "aws_iam_role_policy",
+      "name": "lambda_opa",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "p",
+          "role": "r",
+          "policy": "{\"Version\": \"2012-10-17\", \"Statement\": [{\"Effect\": \"Allow\", \"Action\": \"*\", \"Resource\": \"*\"}]}"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cognito_user_pool.silk_reeling",
+      "mode": "managed",
+      "type": "aws_cognito_user_pool",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "pool",
+          "mfa_configuration": "ON",
+          "password_policy": [
+            {
+              "minimum_length": 14
+            }
+          ],
+          "admin_create_user_config": [
+            {
+              "allow_admin_create_user_only": true
+            }
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_kms_key.at_rest",
+      "mode": "managed",
+      "type": "aws_kms_key",
+      "name": "at_rest",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "description": "k",
+          "enable_key_rotation": true,
+          "is_enabled": true,
+          "customer_master_key_spec": "SYMMETRIC_DEFAULT",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_kms_key.runtime_signing",
+      "mode": "managed",
+      "type": "aws_kms_key",
+      "name": "runtime_signing",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "description": "s",
+          "customer_master_key_spec": "ECC_NIST_P256",
+          "key_usage": "SIGN_VERIFY",
+          "is_enabled": true,
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_log_group.opa_compliance",
+      "mode": "managed",
+      "type": "aws_cloudwatch_log_group",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "/aws/lambda/x",
+          "retention_in_days": 365,
+          "kms_key_id": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_stage.silk_reeling",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_stage",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "$default",
+          "access_log_settings": [
+            {
+              "destination_arn": "arn:aws:logs:us-east-2:123456789012:log-group:/aws/apigateway/x",
+              "format": "{}"
+            }
+          ],
+          "default_route_settings": [
+            {
+              "throttling_rate_limit": 20,
+              "throttling_burst_limit": 10
+            }
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_route.silk_reeling",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_route",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "route_key": "$default",
+          "authorization_type": "NONE"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_route.silk_reeling_api",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_route",
+      "name": "silk_reeling_api",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "route_key": "ANY /api/{proxy+}",
+          "authorization_type": "JWT"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_lambda_function.opa_compliance",
+      "mode": "managed",
+      "type": "aws_lambda_function",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "function_name": "x",
+          "runtime": "nodejs22.x",
+          "kms_key_arn": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_sns_topic.evidence_alerts",
+      "mode": "managed",
+      "type": "aws_sns_topic",
+      "name": "evidence_alerts",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "t",
+          "kms_master_key_id": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_sqs_queue.compliance_dlq",
+      "mode": "managed",
+      "type": "aws_sqs_queue",
+      "name": "compliance_dlq",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "q",
+          "sqs_managed_sse_enabled": true,
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_metric_alarm.evidence",
+      "mode": "managed",
+      "type": "aws_cloudwatch_metric_alarm",
+      "name": "evidence",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "alarm_name": "a",
+          "actions_enabled": true,
+          "alarm_actions": [
+            "arn:aws:sns:us-east-2:123456789012:t"
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_event_rule.opa_compliance",
+      "mode": "managed",
+      "type": "aws_cloudwatch_event_rule",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "e",
+          "state": "ENABLED",
+          "schedule_expression": "rate(1 day)",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudtrail.management",
+      "mode": "managed",
+      "type": "aws_cloudtrail",
+      "name": "management",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "trail",
+          "enable_logging": true,
+          "is_multi_region_trail": true,
+          "enable_log_file_validation": true
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    }
+  ],
+  "configuration": {
+    "root_module": {
+      "resources": []
+    }
+  }
+}
diff --git a/tests/fixtures/plans/iam-oidc-trust-unscoped.json b/tests/fixtures/plans/iam-oidc-trust-unscoped.json
new file mode 100644
index 00000000..d16f166d
--- /dev/null
+++ b/tests/fixtures/plans/iam-oidc-trust-unscoped.json
@@ -0,0 +1,613 @@
+{
+  "_fixture": {
+    "synthetic": true,
+    "models": "Known-bad: a role federated to GitHub OIDC with no subject condition (any repository's workflow could assume it)"
+  },
+  "format_version": "1.2",
+  "terraform_version": "1.9.8",
+  "resource_changes": [
+    {
+      "address": "aws_iam_role.lambda_opa",
+      "mode": "managed",
+      "type": "aws_iam_role",
+      "name": "lambda_opa",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "samaydlette-com-lambda-opa-role",
+          "assume_role_policy": "{\"Version\": \"2012-10-17\", \"Statement\": [{\"Effect\": \"Allow\", \"Action\": \"sts:AssumeRoleWithWebIdentity\", \"Principal\": {\"Federated\": \"arn:aws:iam::123456789012:oidc-provider/token.actions.githubusercontent.com\"}, \"Condition\": {\"StringEquals\": {\"token.actions.githubusercontent.com:aud\": \"sts.amazonaws.com\"}}}]}",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_iam_role_policy.lambda_opa",
+      "mode": "managed",
+      "type": "aws_iam_role_policy",
+      "name": "lambda_opa",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "p",
+          "role": "r",
+          "policy": "{\"Version\": \"2012-10-17\", \"Statement\": [{\"Effect\": \"Allow\", \"Action\": [\"s3:GetBucketVersioning\"], \"Resource\": [\"arn:aws:s3:::b\"]}, {\"Effect\": \"Allow\", \"Action\": [\"kms:Sign\"], \"Resource\": [\"arn:aws:kms:us-east-2:123456789012:key/k\"]}]}"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cognito_user_pool.silk_reeling",
+      "mode": "managed",
+      "type": "aws_cognito_user_pool",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "pool",
+          "mfa_configuration": "ON",
+          "password_policy": [
+            {
+              "minimum_length": 14
+            }
+          ],
+          "admin_create_user_config": [
+            {
+              "allow_admin_create_user_only": true
+            }
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_kms_key.at_rest",
+      "mode": "managed",
+      "type": "aws_kms_key",
+      "name": "at_rest",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "description": "k",
+          "enable_key_rotation": true,
+          "is_enabled": true,
+          "customer_master_key_spec": "SYMMETRIC_DEFAULT",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_kms_key.runtime_signing",
+      "mode": "managed",
+      "type": "aws_kms_key",
+      "name": "runtime_signing",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "description": "s",
+          "customer_master_key_spec": "ECC_NIST_P256",
+          "key_usage": "SIGN_VERIFY",
+          "is_enabled": true,
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_log_group.opa_compliance",
+      "mode": "managed",
+      "type": "aws_cloudwatch_log_group",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "/aws/lambda/x",
+          "retention_in_days": 365,
+          "kms_key_id": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_stage.silk_reeling",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_stage",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "$default",
+          "access_log_settings": [
+            {
+              "destination_arn": "arn:aws:logs:us-east-2:123456789012:log-group:/aws/apigateway/x",
+              "format": "{}"
+            }
+          ],
+          "default_route_settings": [
+            {
+              "throttling_rate_limit": 20,
+              "throttling_burst_limit": 10
+            }
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_route.silk_reeling",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_route",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "route_key": "$default",
+          "authorization_type": "NONE"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_route.silk_reeling_api",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_route",
+      "name": "silk_reeling_api",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "route_key": "ANY /api/{proxy+}",
+          "authorization_type": "JWT"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_lambda_function.opa_compliance",
+      "mode": "managed",
+      "type": "aws_lambda_function",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "function_name": "x",
+          "runtime": "nodejs22.x",
+          "kms_key_arn": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_sns_topic.evidence_alerts",
+      "mode": "managed",
+      "type": "aws_sns_topic",
+      "name": "evidence_alerts",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "t",
+          "kms_master_key_id": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_sqs_queue.compliance_dlq",
+      "mode": "managed",
+      "type": "aws_sqs_queue",
+      "name": "compliance_dlq",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "q",
+          "sqs_managed_sse_enabled": true,
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_metric_alarm.evidence",
+      "mode": "managed",
+      "type": "aws_cloudwatch_metric_alarm",
+      "name": "evidence",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "alarm_name": "a",
+          "actions_enabled": true,
+          "alarm_actions": [
+            "arn:aws:sns:us-east-2:123456789012:t"
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_event_rule.opa_compliance",
+      "mode": "managed",
+      "type": "aws_cloudwatch_event_rule",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "e",
+          "state": "ENABLED",
+          "schedule_expression": "rate(1 day)",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudtrail.management",
+      "mode": "managed",
+      "type": "aws_cloudtrail",
+      "name": "management",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "trail",
+          "enable_logging": true,
+          "is_multi_region_trail": true,
+          "enable_log_file_validation": true
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    }
+  ],
+  "configuration": {
+    "root_module": {
+      "resources": []
+    }
+  }
+}
diff --git a/tests/fixtures/plans/kms-rotation-disabled.json b/tests/fixtures/plans/kms-rotation-disabled.json
new file mode 100644
index 00000000..3111ceaf
--- /dev/null
+++ b/tests/fixtures/plans/kms-rotation-disabled.json
@@ -0,0 +1,613 @@
+{
+  "_fixture": {
+    "synthetic": true,
+    "models": "Known-bad: symmetric customer key without rotation"
+  },
+  "format_version": "1.2",
+  "terraform_version": "1.9.8",
+  "resource_changes": [
+    {
+      "address": "aws_iam_role.lambda_opa",
+      "mode": "managed",
+      "type": "aws_iam_role",
+      "name": "lambda_opa",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "samaydlette-com-lambda-opa-role",
+          "assume_role_policy": "{\"Version\": \"2012-10-17\", \"Statement\": [{\"Effect\": \"Allow\", \"Action\": \"sts:AssumeRole\", \"Principal\": {\"Service\": \"lambda.amazonaws.com\"}}]}",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_iam_role_policy.lambda_opa",
+      "mode": "managed",
+      "type": "aws_iam_role_policy",
+      "name": "lambda_opa",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "p",
+          "role": "r",
+          "policy": "{\"Version\": \"2012-10-17\", \"Statement\": [{\"Effect\": \"Allow\", \"Action\": [\"s3:GetBucketVersioning\"], \"Resource\": [\"arn:aws:s3:::b\"]}, {\"Effect\": \"Allow\", \"Action\": [\"kms:Sign\"], \"Resource\": [\"arn:aws:kms:us-east-2:123456789012:key/k\"]}]}"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cognito_user_pool.silk_reeling",
+      "mode": "managed",
+      "type": "aws_cognito_user_pool",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "pool",
+          "mfa_configuration": "ON",
+          "password_policy": [
+            {
+              "minimum_length": 14
+            }
+          ],
+          "admin_create_user_config": [
+            {
+              "allow_admin_create_user_only": true
+            }
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_kms_key.at_rest",
+      "mode": "managed",
+      "type": "aws_kms_key",
+      "name": "at_rest",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "description": "k",
+          "enable_key_rotation": false,
+          "is_enabled": true,
+          "customer_master_key_spec": "SYMMETRIC_DEFAULT",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_kms_key.runtime_signing",
+      "mode": "managed",
+      "type": "aws_kms_key",
+      "name": "runtime_signing",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "description": "s",
+          "customer_master_key_spec": "ECC_NIST_P256",
+          "key_usage": "SIGN_VERIFY",
+          "is_enabled": true,
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_log_group.opa_compliance",
+      "mode": "managed",
+      "type": "aws_cloudwatch_log_group",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "/aws/lambda/x",
+          "retention_in_days": 365,
+          "kms_key_id": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_stage.silk_reeling",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_stage",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "$default",
+          "access_log_settings": [
+            {
+              "destination_arn": "arn:aws:logs:us-east-2:123456789012:log-group:/aws/apigateway/x",
+              "format": "{}"
+            }
+          ],
+          "default_route_settings": [
+            {
+              "throttling_rate_limit": 20,
+              "throttling_burst_limit": 10
+            }
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_route.silk_reeling",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_route",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "route_key": "$default",
+          "authorization_type": "NONE"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_route.silk_reeling_api",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_route",
+      "name": "silk_reeling_api",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "route_key": "ANY /api/{proxy+}",
+          "authorization_type": "JWT"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_lambda_function.opa_compliance",
+      "mode": "managed",
+      "type": "aws_lambda_function",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "function_name": "x",
+          "runtime": "nodejs22.x",
+          "kms_key_arn": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_sns_topic.evidence_alerts",
+      "mode": "managed",
+      "type": "aws_sns_topic",
+      "name": "evidence_alerts",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "t",
+          "kms_master_key_id": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_sqs_queue.compliance_dlq",
+      "mode": "managed",
+      "type": "aws_sqs_queue",
+      "name": "compliance_dlq",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "q",
+          "sqs_managed_sse_enabled": true,
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_metric_alarm.evidence",
+      "mode": "managed",
+      "type": "aws_cloudwatch_metric_alarm",
+      "name": "evidence",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "alarm_name": "a",
+          "actions_enabled": true,
+          "alarm_actions": [
+            "arn:aws:sns:us-east-2:123456789012:t"
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_event_rule.opa_compliance",
+      "mode": "managed",
+      "type": "aws_cloudwatch_event_rule",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "e",
+          "state": "ENABLED",
+          "schedule_expression": "rate(1 day)",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudtrail.management",
+      "mode": "managed",
+      "type": "aws_cloudtrail",
+      "name": "management",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "trail",
+          "enable_logging": true,
+          "is_multi_region_trail": true,
+          "enable_log_file_validation": true
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    }
+  ],
+  "configuration": {
+    "root_module": {
+      "resources": []
+    }
+  }
+}
diff --git a/tests/fixtures/plans/log-group-unencrypted.json b/tests/fixtures/plans/log-group-unencrypted.json
new file mode 100644
index 00000000..771f0b7c
--- /dev/null
+++ b/tests/fixtures/plans/log-group-unencrypted.json
@@ -0,0 +1,613 @@
+{
+  "_fixture": {
+    "synthetic": true,
+    "models": "Known-bad: log group with no customer key (known at plan time, so not deferred)"
+  },
+  "format_version": "1.2",
+  "terraform_version": "1.9.8",
+  "resource_changes": [
+    {
+      "address": "aws_iam_role.lambda_opa",
+      "mode": "managed",
+      "type": "aws_iam_role",
+      "name": "lambda_opa",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "samaydlette-com-lambda-opa-role",
+          "assume_role_policy": "{\"Version\": \"2012-10-17\", \"Statement\": [{\"Effect\": \"Allow\", \"Action\": \"sts:AssumeRole\", \"Principal\": {\"Service\": \"lambda.amazonaws.com\"}}]}",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_iam_role_policy.lambda_opa",
+      "mode": "managed",
+      "type": "aws_iam_role_policy",
+      "name": "lambda_opa",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "p",
+          "role": "r",
+          "policy": "{\"Version\": \"2012-10-17\", \"Statement\": [{\"Effect\": \"Allow\", \"Action\": [\"s3:GetBucketVersioning\"], \"Resource\": [\"arn:aws:s3:::b\"]}, {\"Effect\": \"Allow\", \"Action\": [\"kms:Sign\"], \"Resource\": [\"arn:aws:kms:us-east-2:123456789012:key/k\"]}]}"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cognito_user_pool.silk_reeling",
+      "mode": "managed",
+      "type": "aws_cognito_user_pool",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "pool",
+          "mfa_configuration": "ON",
+          "password_policy": [
+            {
+              "minimum_length": 14
+            }
+          ],
+          "admin_create_user_config": [
+            {
+              "allow_admin_create_user_only": true
+            }
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_kms_key.at_rest",
+      "mode": "managed",
+      "type": "aws_kms_key",
+      "name": "at_rest",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "description": "k",
+          "enable_key_rotation": true,
+          "is_enabled": true,
+          "customer_master_key_spec": "SYMMETRIC_DEFAULT",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_kms_key.runtime_signing",
+      "mode": "managed",
+      "type": "aws_kms_key",
+      "name": "runtime_signing",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "description": "s",
+          "customer_master_key_spec": "ECC_NIST_P256",
+          "key_usage": "SIGN_VERIFY",
+          "is_enabled": true,
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_log_group.opa_compliance",
+      "mode": "managed",
+      "type": "aws_cloudwatch_log_group",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "/aws/lambda/x",
+          "retention_in_days": 365,
+          "kms_key_id": null,
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_stage.silk_reeling",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_stage",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "$default",
+          "access_log_settings": [
+            {
+              "destination_arn": "arn:aws:logs:us-east-2:123456789012:log-group:/aws/apigateway/x",
+              "format": "{}"
+            }
+          ],
+          "default_route_settings": [
+            {
+              "throttling_rate_limit": 20,
+              "throttling_burst_limit": 10
+            }
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_route.silk_reeling",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_route",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "route_key": "$default",
+          "authorization_type": "NONE"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_route.silk_reeling_api",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_route",
+      "name": "silk_reeling_api",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "route_key": "ANY /api/{proxy+}",
+          "authorization_type": "JWT"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_lambda_function.opa_compliance",
+      "mode": "managed",
+      "type": "aws_lambda_function",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "function_name": "x",
+          "runtime": "nodejs22.x",
+          "kms_key_arn": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_sns_topic.evidence_alerts",
+      "mode": "managed",
+      "type": "aws_sns_topic",
+      "name": "evidence_alerts",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "t",
+          "kms_master_key_id": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_sqs_queue.compliance_dlq",
+      "mode": "managed",
+      "type": "aws_sqs_queue",
+      "name": "compliance_dlq",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "q",
+          "sqs_managed_sse_enabled": true,
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_metric_alarm.evidence",
+      "mode": "managed",
+      "type": "aws_cloudwatch_metric_alarm",
+      "name": "evidence",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "alarm_name": "a",
+          "actions_enabled": true,
+          "alarm_actions": [
+            "arn:aws:sns:us-east-2:123456789012:t"
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_event_rule.opa_compliance",
+      "mode": "managed",
+      "type": "aws_cloudwatch_event_rule",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "e",
+          "state": "ENABLED",
+          "schedule_expression": "rate(1 day)",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudtrail.management",
+      "mode": "managed",
+      "type": "aws_cloudtrail",
+      "name": "management",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "trail",
+          "enable_logging": true,
+          "is_multi_region_trail": true,
+          "enable_log_file_validation": true
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    }
+  ],
+  "configuration": {
+    "root_module": {
+      "resources": []
+    }
+  }
+}
diff --git a/tests/fixtures/plans/service-stack-compliant.json b/tests/fixtures/plans/service-stack-compliant.json
new file mode 100644
index 00000000..843bfe22
--- /dev/null
+++ b/tests/fixtures/plans/service-stack-compliant.json
@@ -0,0 +1,613 @@
+{
+  "_fixture": {
+    "synthetic": true,
+    "models": "Every service type the runtime emitter re-validates (IAM role + inline policy, Cognito, KMS, log group, API stage + routes, Lambda, SNS, SQS, alarm, schedule, CloudTrail), all compliant; a KMS key ARN computed at apply time is deferred, not failed"
+  },
+  "format_version": "1.2",
+  "terraform_version": "1.9.8",
+  "resource_changes": [
+    {
+      "address": "aws_iam_role.lambda_opa",
+      "mode": "managed",
+      "type": "aws_iam_role",
+      "name": "lambda_opa",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "samaydlette-com-lambda-opa-role",
+          "assume_role_policy": "{\"Version\": \"2012-10-17\", \"Statement\": [{\"Effect\": \"Allow\", \"Action\": \"sts:AssumeRole\", \"Principal\": {\"Service\": \"lambda.amazonaws.com\"}}]}",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_iam_role_policy.lambda_opa",
+      "mode": "managed",
+      "type": "aws_iam_role_policy",
+      "name": "lambda_opa",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "p",
+          "role": "r",
+          "policy": "{\"Version\": \"2012-10-17\", \"Statement\": [{\"Effect\": \"Allow\", \"Action\": [\"s3:GetBucketVersioning\"], \"Resource\": [\"arn:aws:s3:::b\"]}, {\"Effect\": \"Allow\", \"Action\": [\"kms:Sign\"], \"Resource\": [\"arn:aws:kms:us-east-2:123456789012:key/k\"]}]}"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cognito_user_pool.silk_reeling",
+      "mode": "managed",
+      "type": "aws_cognito_user_pool",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "pool",
+          "mfa_configuration": "ON",
+          "password_policy": [
+            {
+              "minimum_length": 14
+            }
+          ],
+          "admin_create_user_config": [
+            {
+              "allow_admin_create_user_only": true
+            }
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_kms_key.at_rest",
+      "mode": "managed",
+      "type": "aws_kms_key",
+      "name": "at_rest",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "description": "k",
+          "enable_key_rotation": true,
+          "is_enabled": true,
+          "customer_master_key_spec": "SYMMETRIC_DEFAULT",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_kms_key.runtime_signing",
+      "mode": "managed",
+      "type": "aws_kms_key",
+      "name": "runtime_signing",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "description": "s",
+          "customer_master_key_spec": "ECC_NIST_P256",
+          "key_usage": "SIGN_VERIFY",
+          "is_enabled": true,
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_log_group.opa_compliance",
+      "mode": "managed",
+      "type": "aws_cloudwatch_log_group",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "/aws/lambda/x",
+          "retention_in_days": 365,
+          "kms_key_id": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_stage.silk_reeling",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_stage",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "$default",
+          "access_log_settings": [
+            {
+              "destination_arn": "arn:aws:logs:us-east-2:123456789012:log-group:/aws/apigateway/x",
+              "format": "{}"
+            }
+          ],
+          "default_route_settings": [
+            {
+              "throttling_rate_limit": 20,
+              "throttling_burst_limit": 10
+            }
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_route.silk_reeling",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_route",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "route_key": "$default",
+          "authorization_type": "NONE"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_route.silk_reeling_api",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_route",
+      "name": "silk_reeling_api",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "route_key": "ANY /api/{proxy+}",
+          "authorization_type": "JWT"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_lambda_function.opa_compliance",
+      "mode": "managed",
+      "type": "aws_lambda_function",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "function_name": "x",
+          "runtime": "nodejs22.x",
+          "kms_key_arn": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_sns_topic.evidence_alerts",
+      "mode": "managed",
+      "type": "aws_sns_topic",
+      "name": "evidence_alerts",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "t",
+          "kms_master_key_id": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_sqs_queue.compliance_dlq",
+      "mode": "managed",
+      "type": "aws_sqs_queue",
+      "name": "compliance_dlq",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "q",
+          "sqs_managed_sse_enabled": true,
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_metric_alarm.evidence",
+      "mode": "managed",
+      "type": "aws_cloudwatch_metric_alarm",
+      "name": "evidence",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "alarm_name": "a",
+          "actions_enabled": true,
+          "alarm_actions": [
+            "arn:aws:sns:us-east-2:123456789012:t"
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_event_rule.opa_compliance",
+      "mode": "managed",
+      "type": "aws_cloudwatch_event_rule",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "e",
+          "state": "ENABLED",
+          "schedule_expression": "rate(1 day)",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudtrail.management",
+      "mode": "managed",
+      "type": "aws_cloudtrail",
+      "name": "management",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "trail",
+          "enable_logging": true,
+          "is_multi_region_trail": true,
+          "enable_log_file_validation": true
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    }
+  ],
+  "configuration": {
+    "root_module": {
+      "resources": []
+    }
+  }
+}
diff --git a/tests/fixtures/plans/service-stack-computed-key.json b/tests/fixtures/plans/service-stack-computed-key.json
new file mode 100644
index 00000000..627db71e
--- /dev/null
+++ b/tests/fixtures/plans/service-stack-computed-key.json
@@ -0,0 +1,615 @@
+{
+  "_fixture": {
+    "synthetic": true,
+    "models": "As service-stack-compliant, but the log group's KMS key ARN is unknown until apply: deferred to the runtime check, never failed or assumed good"
+  },
+  "format_version": "1.2",
+  "terraform_version": "1.9.8",
+  "resource_changes": [
+    {
+      "address": "aws_iam_role.lambda_opa",
+      "mode": "managed",
+      "type": "aws_iam_role",
+      "name": "lambda_opa",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "samaydlette-com-lambda-opa-role",
+          "assume_role_policy": "{\"Version\": \"2012-10-17\", \"Statement\": [{\"Effect\": \"Allow\", \"Action\": \"sts:AssumeRole\", \"Principal\": {\"Service\": \"lambda.amazonaws.com\"}}]}",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_iam_role_policy.lambda_opa",
+      "mode": "managed",
+      "type": "aws_iam_role_policy",
+      "name": "lambda_opa",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "p",
+          "role": "r",
+          "policy": "{\"Version\": \"2012-10-17\", \"Statement\": [{\"Effect\": \"Allow\", \"Action\": [\"s3:GetBucketVersioning\"], \"Resource\": [\"arn:aws:s3:::b\"]}, {\"Effect\": \"Allow\", \"Action\": [\"kms:Sign\"], \"Resource\": [\"arn:aws:kms:us-east-2:123456789012:key/k\"]}]}"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cognito_user_pool.silk_reeling",
+      "mode": "managed",
+      "type": "aws_cognito_user_pool",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "pool",
+          "mfa_configuration": "ON",
+          "password_policy": [
+            {
+              "minimum_length": 14
+            }
+          ],
+          "admin_create_user_config": [
+            {
+              "allow_admin_create_user_only": true
+            }
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_kms_key.at_rest",
+      "mode": "managed",
+      "type": "aws_kms_key",
+      "name": "at_rest",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "description": "k",
+          "enable_key_rotation": true,
+          "is_enabled": true,
+          "customer_master_key_spec": "SYMMETRIC_DEFAULT",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_kms_key.runtime_signing",
+      "mode": "managed",
+      "type": "aws_kms_key",
+      "name": "runtime_signing",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "description": "s",
+          "customer_master_key_spec": "ECC_NIST_P256",
+          "key_usage": "SIGN_VERIFY",
+          "is_enabled": true,
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_log_group.opa_compliance",
+      "mode": "managed",
+      "type": "aws_cloudwatch_log_group",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "/aws/lambda/x",
+          "retention_in_days": 365,
+          "kms_key_id": null,
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {
+          "kms_key_id": true
+        },
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_stage.silk_reeling",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_stage",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "$default",
+          "access_log_settings": [
+            {
+              "destination_arn": "arn:aws:logs:us-east-2:123456789012:log-group:/aws/apigateway/x",
+              "format": "{}"
+            }
+          ],
+          "default_route_settings": [
+            {
+              "throttling_rate_limit": 20,
+              "throttling_burst_limit": 10
+            }
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_route.silk_reeling",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_route",
+      "name": "silk_reeling",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "route_key": "$default",
+          "authorization_type": "NONE"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_apigatewayv2_route.silk_reeling_api",
+      "mode": "managed",
+      "type": "aws_apigatewayv2_route",
+      "name": "silk_reeling_api",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "route_key": "ANY /api/{proxy+}",
+          "authorization_type": "JWT"
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_lambda_function.opa_compliance",
+      "mode": "managed",
+      "type": "aws_lambda_function",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "function_name": "x",
+          "runtime": "nodejs22.x",
+          "kms_key_arn": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_sns_topic.evidence_alerts",
+      "mode": "managed",
+      "type": "aws_sns_topic",
+      "name": "evidence_alerts",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "t",
+          "kms_master_key_id": "arn:aws:kms:us-east-2:123456789012:key/k",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_sqs_queue.compliance_dlq",
+      "mode": "managed",
+      "type": "aws_sqs_queue",
+      "name": "compliance_dlq",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "q",
+          "sqs_managed_sse_enabled": true,
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_metric_alarm.evidence",
+      "mode": "managed",
+      "type": "aws_cloudwatch_metric_alarm",
+      "name": "evidence",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "alarm_name": "a",
+          "actions_enabled": true,
+          "alarm_actions": [
+            "arn:aws:sns:us-east-2:123456789012:t"
+          ],
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudwatch_event_rule.opa_compliance",
+      "mode": "managed",
+      "type": "aws_cloudwatch_event_rule",
+      "name": "opa_compliance",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "e",
+          "state": "ENABLED",
+          "schedule_expression": "rate(1 day)",
+          "tags": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          },
+          "tags_all": {
+            "Environment": "prod",
+            "CostCenter": "website-ops",
+            "DataClassification": "Internal",
+            "Owner": "sam-aydlette",
+            "DataSensitivity": "internal",
+            "MissionCriticality": "moderate",
+            "InternetReachable": "false",
+            "Archetype": "security-tooling",
+            "AgencyScope": "single",
+            "OwnerRole": "platform-operator"
+          }
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    },
+    {
+      "address": "aws_cloudtrail.management",
+      "mode": "managed",
+      "type": "aws_cloudtrail",
+      "name": "management",
+      "provider_name": "registry.terraform.io/hashicorp/aws",
+      "change": {
+        "actions": [
+          "create"
+        ],
+        "before": null,
+        "after": {
+          "name": "trail",
+          "enable_logging": true,
+          "is_multi_region_trail": true,
+          "enable_log_file_validation": true
+        },
+        "after_unknown": {},
+        "before_sensitive": false,
+        "after_sensitive": {}
+      }
+    }
+  ],
+  "configuration": {
+    "root_module": {
+      "resources": []
+    }
+  }
+}
diff --git a/tests/fixtures/queue-watchdog/jobs.json b/tests/fixtures/queue-watchdog/jobs.json
new file mode 100644
index 00000000..3e7b7fd8
--- /dev/null
+++ b/tests/fixtures/queue-watchdog/jobs.json
@@ -0,0 +1,18 @@
+{
+  "_note": "A run's jobs as GitHub's API lists them while the deploy waits: the jobs of a called workflow are named ' / '. Only 'Security Scan' has no runner.",
+  "jobs": [
+    {"name": "Queue watchdog", "status": "in_progress"},
+    {"name": "Unit tests (pytest + opa test)", "status": "completed"},
+    {"name": "OPA Compliance Check", "status": "completed"},
+    {"name": "Security Scan", "status": "queued"},
+    {"name": "Simulated assessor / Totally Real Assessment Services, LLC (simulated) assesses", "status": "queued"},
+    {"name": "Simulated assessor / Totally Real Assessment Services, LLC (simulated) signs", "status": "queued"},
+    {"name": "Deploy Infrastructure", "status": "queued"},
+    {"name": "Prove the certification package maintainer / Rebuild, sign and publish the certification package", "status": "queued"},
+    {"name": "Prove the certification package maintainer / Alert on package maintenance", "status": "queued"},
+    {"name": "Prove the incident report publisher / Build, sign and publish incident reports", "status": "queued"},
+    {"name": "Prove the incident report publisher / Alert on incident reporting", "status": "queued"},
+    {"name": "Notify on Failure", "status": "queued"},
+    {"name": "Simulated assessorX", "status": "queued"}
+  ]
+}
diff --git a/tests/fixtures/queue-watchdog/missing-dependent.yml b/tests/fixtures/queue-watchdog/missing-dependent.yml
new file mode 100644
index 00000000..dffbc800
--- /dev/null
+++ b/tests/fixtures/queue-watchdog/missing-dependent.yml
@@ -0,0 +1,29 @@
+# Known-bad: a workflow whose queue watchdog does not exclude the dependent job
+# "Prove the publisher" (it has `needs:`), so the watchdog would cancel a run
+# while that job correctly waits for the deploy. tests/test_queue_watchdog.py
+# must report exactly that job.
+name: Fixture
+on: push
+jobs:
+  queue-watchdog:
+    name: Queue watchdog
+    runs-on: ubuntu-latest
+    steps:
+    - name: Cancel the run if a job never gets a runner
+      run: |
+        DEPENDENT='["Deploy Infrastructure","Queue watchdog"]'
+  build:
+    name: Build
+    runs-on: ubuntu-latest
+    steps:
+    - run: true
+  deploy:
+    name: Deploy Infrastructure
+    needs: [build]
+    runs-on: ubuntu-latest
+    steps:
+    - run: true
+  publisher:
+    name: Prove the publisher
+    needs: [deploy]
+    uses: ./.github/workflows/publisher.yml
diff --git a/tests/fixtures/redaction/github-run-id-field.json b/tests/fixtures/redaction/github-run-id-field.json
new file mode 100644
index 00000000..0e9d512d
--- /dev/null
+++ b/tests/fixtures/redaction/github-run-id-field.json
@@ -0,0 +1 @@
+{"provenance": {"builder": {"id": "https://github.com/example/repo/.github/workflows/deploy.yml@refs/heads/main", "run_id": "12345678901"}}}
diff --git a/tests/fixtures/redaction/github-run-named.json b/tests/fixtures/redaction/github-run-named.json
new file mode 100644
index 00000000..b0c9a771
--- /dev/null
+++ b/tests/fixtures/redaction/github-run-named.json
@@ -0,0 +1 @@
+{"schema": "vdr-status/1", "result": "success", "run_url": "https://github.com/example/repo/actions/runs/12345678901"}
diff --git a/tests/fixtures/redaction/iam-user-named.json b/tests/fixtures/redaction/iam-user-named.json
new file mode 100644
index 00000000..57fb44b5
--- /dev/null
+++ b/tests/fixtures/redaction/iam-user-named.json
@@ -0,0 +1 @@
+{"decisionId": "DEC-999", "affectedResources": ["aws-account::root", "aws-iam-user::example-operator"]}
diff --git a/tests/fixtures/redaction/personal-email.json b/tests/fixtures/redaction/personal-email.json
new file mode 100644
index 00000000..72c34df1
--- /dev/null
+++ b/tests/fixtures/redaction/personal-email.json
@@ -0,0 +1,6 @@
+{
+  "$comment": "KNOWN-BAD: a published contact that is a personal-looking mailbox, not an address at the site's own domain. The publication redaction gate must fail on it (scripts/_redact.py find_foreign_emails). The address is the reserved example domain, not a real one.",
+  "ownership": {"operator_contact": "someone@example.com"},
+  "security_contact": "security@samaydlette.com",
+  "dependency": "pkg:npm/left-pad@1.3.0-beta.alpha"
+}
diff --git a/tests/fixtures/repo-settings/bad/.github/dependabot.yml b/tests/fixtures/repo-settings/bad/.github/dependabot.yml
new file mode 100644
index 00000000..bf82fa9e
--- /dev/null
+++ b/tests/fixtures/repo-settings/bad/.github/dependabot.yml
@@ -0,0 +1,7 @@
+# Known-bad (SCG-ENH-CMP): Dependabot no longer watches the Lambda's npm packages.
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
diff --git a/tests/fixtures/repo-settings/bad/.github/workflows/no-permissions.yml b/tests/fixtures/repo-settings/bad/.github/workflows/no-permissions.yml
new file mode 100644
index 00000000..9848ac4f
--- /dev/null
+++ b/tests/fixtures/repo-settings/bad/.github/workflows/no-permissions.yml
@@ -0,0 +1,9 @@
+# Known-bad (SCG-ENH-CMP): a workflow that declares no top-level permissions,
+# so its token falls back to the repository default.
+name: no permissions
+on: workflow_dispatch
+jobs:
+  x:
+    runs-on: ubuntu-latest
+    steps:
+    - run: echo hi
diff --git a/tests/fixtures/repo-settings/bad/.github/workflows/write-all.yml b/tests/fixtures/repo-settings/bad/.github/workflows/write-all.yml
new file mode 100644
index 00000000..ad0147ef
--- /dev/null
+++ b/tests/fixtures/repo-settings/bad/.github/workflows/write-all.yml
@@ -0,0 +1,9 @@
+# Known-bad (SCG-ENH-CMP): a workflow whose token may write everything.
+name: write all
+on: workflow_dispatch
+permissions: write-all
+jobs:
+  x:
+    runs-on: ubuntu-latest
+    steps:
+    - run: echo hi
diff --git a/tests/fixtures/resources/runtime-dnssec-not-signing.json b/tests/fixtures/resources/runtime-dnssec-not-signing.json
new file mode 100644
index 00000000..16cdcc5d
--- /dev/null
+++ b/tests/fixtures/resources/runtime-dnssec-not-signing.json
@@ -0,0 +1,13 @@
+{
+  "_fixture": {
+    "synthetic": true,
+    "note": "Known-bad: hosted zone not serving DNSSEC signatures"
+  },
+  "resource": {
+    "type": "aws_route53_zone",
+    "name": "website",
+    "values": {
+      "dnssec_status": "NOT_SIGNING"
+    }
+  }
+}
diff --git a/tests/fixtures/resources/runtime-group-admin.json b/tests/fixtures/resources/runtime-group-admin.json
new file mode 100644
index 00000000..4b3da7c8
--- /dev/null
+++ b/tests/fixtures/resources/runtime-group-admin.json
@@ -0,0 +1,16 @@
+{
+  "_fixture": {
+    "synthetic": true,
+    "note": "Known-bad: AdministratorAccess attached to a group"
+  },
+  "resource": {
+    "type": "aws_iam_group",
+    "name": "operators",
+    "values": {
+      "attached_policy_arns": [
+        "arn:aws:iam::aws:policy/AdministratorAccess"
+      ],
+      "inline_policies": []
+    }
+  }
+}
diff --git a/tests/fixtures/resources/runtime-kms-key-live.json b/tests/fixtures/resources/runtime-kms-key-live.json
new file mode 100644
index 00000000..1d47ac61
--- /dev/null
+++ b/tests/fixtures/resources/runtime-kms-key-live.json
@@ -0,0 +1,39 @@
+{
+  "_fixture": {
+    "synthetic": true,
+    "note": "Compliant KMS key as read live (tags from the tagging API)"
+  },
+  "resource": {
+    "type": "aws_kms_key",
+    "name": "at_rest",
+    "tags": {
+      "Environment": "prod",
+      "CostCenter": "website-ops",
+      "DataClassification": "Internal",
+      "Owner": "sam-aydlette",
+      "DataSensitivity": "internal",
+      "MissionCriticality": "moderate",
+      "InternetReachable": "false",
+      "Archetype": "security-tooling",
+      "AgencyScope": "single",
+      "OwnerRole": "platform-operator"
+    },
+    "tags_all": {
+      "Environment": "prod",
+      "CostCenter": "website-ops",
+      "DataClassification": "Internal",
+      "Owner": "sam-aydlette",
+      "DataSensitivity": "internal",
+      "MissionCriticality": "moderate",
+      "InternetReachable": "false",
+      "Archetype": "security-tooling",
+      "AgencyScope": "single",
+      "OwnerRole": "platform-operator"
+    },
+    "values": {
+      "customer_master_key_spec": "SYMMETRIC_DEFAULT",
+      "enable_key_rotation": true,
+      "is_enabled": true
+    }
+  }
+}
diff --git a/tests/fixtures/resources/runtime-oidc-provider.json b/tests/fixtures/resources/runtime-oidc-provider.json
new file mode 100644
index 00000000..86869641
--- /dev/null
+++ b/tests/fixtures/resources/runtime-oidc-provider.json
@@ -0,0 +1,15 @@
+{
+  "_fixture": {
+    "synthetic": true,
+    "note": "Compliant GitHub OIDC provider as read live"
+  },
+  "resource": {
+    "type": "aws_iam_openid_connect_provider",
+    "name": "github",
+    "values": {
+      "client_id_list": [
+        "sts.amazonaws.com"
+      ]
+    }
+  }
+}
diff --git a/tests/fixtures/resources/runtime-package-drift.json b/tests/fixtures/resources/runtime-package-drift.json
new file mode 100644
index 00000000..1c8790ed
--- /dev/null
+++ b/tests/fixtures/resources/runtime-package-drift.json
@@ -0,0 +1,14 @@
+{
+  "_fixture": {
+    "synthetic": true,
+    "note": "Known-bad: live function code differs from the inventoried package"
+  },
+  "resource": {
+    "type": "lambda_deployment_package",
+    "name": "opa_compliance",
+    "values": {
+      "code_sha256": "bmV3",
+      "expected_code_sha256": "b2xk"
+    }
+  }
+}
diff --git a/tests/fixtures/resources/runtime-package-unverifiable.json b/tests/fixtures/resources/runtime-package-unverifiable.json
new file mode 100644
index 00000000..34116e70
--- /dev/null
+++ b/tests/fixtures/resources/runtime-package-unverifiable.json
@@ -0,0 +1,13 @@
+{
+  "_fixture": {
+    "synthetic": true,
+    "note": "No inventoried hash: integrity is unassessed (category input)"
+  },
+  "resource": {
+    "type": "lambda_deployment_package",
+    "name": "opa_compliance",
+    "values": {
+      "code_sha256": "bmV3"
+    }
+  }
+}
diff --git a/tests/fixtures/runtime-vv/ksi-signal.json b/tests/fixtures/runtime-vv/ksi-signal.json
new file mode 100644
index 00000000..bf41847d
--- /dev/null
+++ b/tests/fixtures/runtime-vv/ksi-signal.json
@@ -0,0 +1,29 @@
+{
+ "_note": "Known-bad for reconcile invariant (m): a minimal inventory whose runtime signal (runtime-signal-bad.json) leaves machine components unvalidated or unassessed, plus a component type nobody classified.",
+ "components": [
+  {
+   "component_id": "aws::iam_role::deploy",
+   "type": "iam_role"
+  },
+  {
+   "component_id": "aws::kms_key::at_rest",
+   "type": "kms_key"
+  },
+  {
+   "component_id": "aws::function::app",
+   "type": "function"
+  },
+  {
+   "component_id": "aws::object_store::site",
+   "type": "object_store"
+  },
+  {
+   "component_id": "npm::left-pad@1.3.0",
+   "type": "npm_package"
+  },
+  {
+   "component_id": "aws::quantum_widget::x",
+   "type": "quantum_widget"
+  }
+ ]
+}
\ No newline at end of file
diff --git a/tests/fixtures/runtime-vv/runtime-validations-bad.json b/tests/fixtures/runtime-vv/runtime-validations-bad.json
new file mode 100644
index 00000000..66a9e461
--- /dev/null
+++ b/tests/fixtures/runtime-vv/runtime-validations-bad.json
@@ -0,0 +1,47 @@
+{
+ "_note": "Decoded runtime-signal validations (as build-vdr-report.load_runtime_signal returns them). iam_role has none; kms_key was only partly readable; the function passed; the bucket passed in one run and was unreadable in another.",
+ "validations": [
+  {
+   "validation_id": "r-1",
+   "result": "fail",
+   "component_refs": [
+    "aws::kms_key::at_rest"
+   ],
+   "violations": [
+    {
+     "id": "resource_read_error",
+     "category": "input"
+    }
+   ]
+  },
+  {
+   "validation_id": "r-2",
+   "result": "pass",
+   "component_refs": [
+    "aws::function::app"
+   ],
+   "violations": []
+  },
+  {
+   "validation_id": "r-3",
+   "result": "pass",
+   "component_refs": [
+    "aws::object_store::site"
+   ],
+   "violations": []
+  },
+  {
+   "validation_id": "r-4",
+   "result": "fail",
+   "component_refs": [
+    "aws::object_store::site"
+   ],
+   "violations": [
+    {
+     "id": "package_integrity_unverifiable",
+     "category": "input"
+    }
+   ]
+  }
+ ]
+}
\ No newline at end of file
diff --git a/tests/fixtures/runtime/components.json b/tests/fixtures/runtime/components.json
new file mode 100644
index 00000000..aa1315d2
--- /dev/null
+++ b/tests/fixtures/runtime/components.json
@@ -0,0 +1,258 @@
+[
+ {
+  "component_id": "aws::iam_role::lambda_opa",
+  "type": "iam_role",
+  "attributes": {
+   "tf_type": "aws_iam_role",
+   "tf_name": "lambda_opa",
+   "id": "samaydlette-com-lambda-opa-role"
+  },
+  "native_id": "arn:aws:iam::ACCOUNT:role/samaydlette-com-lambda-opa-role"
+ },
+ {
+  "component_id": "aws::iam_role::deploy",
+  "type": "iam_role",
+  "attributes": {
+   "tf_type": "aws_iam_role",
+   "tf_name": "deploy",
+   "id": "github-actions-deploy-oidc"
+  },
+  "native_id": "arn:aws:iam::ACCOUNT:role/github-actions-deploy-oidc"
+ },
+ {
+  "component_id": "aws::iam_policy::lambda_opa",
+  "type": "iam_policy",
+  "attributes": {
+   "tf_type": "aws_iam_role_policy",
+   "tf_name": "lambda_opa",
+   "id": "samaydlette-com-lambda-opa-role:samaydlette-com-lambda-opa-policy"
+  },
+  "native_id": "iam-role-policy::samaydlette-com-lambda-opa-role/samaydlette-com-lambda-opa-policy"
+ },
+ {
+  "component_id": "aws::iam_group::operators",
+  "type": "iam_group",
+  "attributes": {
+   "tf_type": "aws_iam_group",
+   "tf_name": "operators",
+   "id": "operators"
+  },
+  "native_id": "arn:aws:iam::ACCOUNT:group/operators"
+ },
+ {
+  "component_id": "aws::iam_policy::operators_s3_bucket",
+  "type": "iam_policy",
+  "attributes": {
+   "tf_type": "aws_iam_group_policy",
+   "tf_name": "operators_s3_bucket",
+   "id": "operators:s3-bucket",
+   "policy_name": "s3-bucket",
+   "attached_to_group": "operators"
+  },
+  "native_id": "iam-group-policy::operators/s3-bucket"
+ },
+ {
+  "component_id": "aws::iam_policy::legacy",
+  "type": "iam_policy",
+  "attributes": {
+   "tf_type": "aws_iam_role_policy_attachment",
+   "tf_name": "legacy",
+   "id": "github-actions-deploy-oidc-20260101",
+   "attached_to_role": "github-actions-deploy-oidc",
+   "attached_policies": [
+    {
+     "policy_name": "github-actions-deploy",
+     "aws_managed": false
+    }
+   ]
+  },
+  "native_id": "iam-role-policy-attachment::github-actions-deploy-oidc/legacy"
+ },
+ {
+  "component_id": "aws::iam_policy::operators",
+  "type": "iam_policy",
+  "attributes": {
+   "tf_type": "aws_iam_group_policy_attachment",
+   "tf_name": "operators",
+   "id": "operators-20260101",
+   "attached_to_group": "operators",
+   "attached_policies": [
+    {
+     "policy_name": "IAMFullAccess",
+     "aws_managed": true
+    }
+   ]
+  },
+  "native_id": "iam-group-policy-attachment::operators/operators"
+ },
+ {
+  "component_id": "aws::oidc_provider::github",
+  "type": "oidc_provider",
+  "attributes": {
+   "tf_type": "aws_iam_openid_connect_provider",
+   "tf_name": "github",
+   "id": "arn:aws:iam::ACCOUNT:oidc-provider/token.actions.githubusercontent.com"
+  },
+  "native_id": "arn:aws:iam::ACCOUNT:oidc-provider/token.actions.githubusercontent.com"
+ },
+ {
+  "component_id": "aws::function::opa_compliance",
+  "type": "function",
+  "attributes": {
+   "tf_type": "aws_lambda_function",
+   "tf_name": "opa_compliance",
+   "id": "samaydlette-com-opa-compliance",
+   "function_name": "samaydlette-com-opa-compliance",
+   "code_sha256": "Y29kZS1oYXNo"
+  },
+  "native_id": "arn:aws:lambda:us-east-2:ACCOUNT:function:samaydlette-com-opa-compliance"
+ },
+ {
+  "component_id": "npm::@open-policy-agent/opa-wasm@1.9.0",
+  "type": "npm_package",
+  "attributes": {
+   "name": "@open-policy-agent/opa-wasm",
+   "version": "1.9.0",
+   "deployed_in": "aws::function::opa_compliance"
+  }
+ },
+ {
+  "component_id": "npm::pa11y@9.0.0",
+  "type": "npm_package",
+  "attributes": {
+   "name": "pa11y",
+   "version": "9.0.0",
+   "lifecycle": "build-time"
+  }
+ },
+ {
+  "component_id": "aws::log_group::opa_compliance",
+  "type": "log_group",
+  "attributes": {
+   "tf_type": "aws_cloudwatch_log_group",
+   "tf_name": "opa_compliance",
+   "id": "/aws/lambda/samaydlette-com-opa-compliance"
+  },
+  "native_id": "arn:aws:logs:us-east-2:ACCOUNT:log-group:/aws/lambda/samaydlette-com-opa-compliance"
+ },
+ {
+  "component_id": "aws::audit_log_trail::management",
+  "type": "audit_log_trail",
+  "attributes": {
+   "tf_type": "aws_cloudtrail",
+   "tf_name": "management",
+   "id": "arn:aws:cloudtrail:us-east-2:ACCOUNT:trail/samaydlette-com-management"
+  },
+  "native_id": "arn:aws:cloudtrail:us-east-2:ACCOUNT:trail/samaydlette-com-management"
+ },
+ {
+  "component_id": "aws::metric_alarm::evidence[vdr-age]",
+  "type": "metric_alarm",
+  "attributes": {
+   "tf_type": "aws_cloudwatch_metric_alarm",
+   "tf_name": "evidence",
+   "id": "samaydlette-com-evidence-watchdog-vdr-age"
+  },
+  "native_id": "arn:aws:cloudwatch:us-east-2:ACCOUNT:alarm:samaydlette-com-evidence-watchdog-vdr-age"
+ },
+ {
+  "component_id": "aws::event_schedule::opa_compliance",
+  "type": "event_schedule",
+  "attributes": {
+   "tf_type": "aws_cloudwatch_event_rule",
+   "tf_name": "opa_compliance",
+   "id": "samaydlette-com-opa-compliance"
+  },
+  "native_id": "arn:aws:events:us-east-2:ACCOUNT:rule/samaydlette-com-opa-compliance"
+ },
+ {
+  "component_id": "aws::notification_topic::evidence_alerts",
+  "type": "notification_topic",
+  "attributes": {
+   "tf_type": "aws_sns_topic",
+   "tf_name": "evidence_alerts",
+   "id": "arn:aws:sns:us-east-2:ACCOUNT:samaydlette-com-evidence-alerts"
+  },
+  "native_id": "arn:aws:sns:us-east-2:ACCOUNT:samaydlette-com-evidence-alerts"
+ },
+ {
+  "component_id": "aws::message_queue::compliance_dlq",
+  "type": "message_queue",
+  "attributes": {
+   "tf_type": "aws_sqs_queue",
+   "tf_name": "compliance_dlq",
+   "id": "https://sqs.us-east-2.amazonaws.com/ACCOUNT/samaydlette-com-opa-compliance-dlq"
+  },
+  "native_id": "arn:aws:sqs:us-east-2:ACCOUNT:samaydlette-com-opa-compliance-dlq"
+ },
+ {
+  "component_id": "aws::kv_table::tflock",
+  "type": "kv_table",
+  "attributes": {
+   "tf_type": "aws_dynamodb_table",
+   "tf_name": "tflock",
+   "id": "samaydlette-com-tflock"
+  },
+  "native_id": "arn:aws:dynamodb:us-east-2:ACCOUNT:table/samaydlette-com-tflock"
+ },
+ {
+  "component_id": "aws::identity_provider::silk_reeling",
+  "type": "identity_provider",
+  "attributes": {
+   "tf_type": "aws_cognito_user_pool",
+   "tf_name": "silk_reeling",
+   "id": "us-east-2_EXAMPLE"
+  },
+  "native_id": "arn:aws:cognito-idp:us-east-2:ACCOUNT:userpool/us-east-2_EXAMPLE"
+ },
+ {
+  "component_id": "aws::kms_key::at_rest",
+  "type": "kms_key",
+  "attributes": {
+   "tf_type": "aws_kms_key",
+   "tf_name": "at_rest",
+   "id": "11111111-2222-3333-4444-555555555555"
+  },
+  "native_id": "arn:aws:kms:us-east-2:ACCOUNT:key/11111111-2222-3333-4444-555555555555"
+ },
+ {
+  "component_id": "aws::kms_key::dnssec_ksk",
+  "type": "kms_key",
+  "attributes": {
+   "tf_type": "aws_kms_key",
+   "tf_name": "dnssec_ksk",
+   "id": "66666666-7777-8888-9999-000000000000"
+  },
+  "native_id": "arn:aws:kms:us-east-1:ACCOUNT:key/66666666-7777-8888-9999-000000000000"
+ },
+ {
+  "component_id": "aws::api_gateway::silk_reeling",
+  "type": "api_gateway",
+  "attributes": {
+   "tf_type": "aws_apigatewayv2_api",
+   "tf_name": "silk_reeling",
+   "id": "abc123"
+  },
+  "native_id": "arn:aws:apigateway:us-east-2::/apis/abc123"
+ },
+ {
+  "component_id": "aws::dns_zone::website",
+  "type": "dns_zone",
+  "attributes": {
+   "tf_type": "aws_route53_zone",
+   "tf_name": "website",
+   "id": "Z0EXAMPLE"
+  },
+  "native_id": "arn:aws:route53:::hostedzone/Z0EXAMPLE"
+ },
+ {
+  "component_id": "aws::tls_certificate::website",
+  "type": "tls_certificate",
+  "attributes": {
+   "tf_type": "aws_acm_certificate",
+   "tf_name": "website",
+   "id": "arn:aws:acm:us-east-1:ACCOUNT:certificate/cert-1"
+  },
+  "native_id": "arn:aws:acm:us-east-1:ACCOUNT:certificate/cert-1"
+ }
+]
\ No newline at end of file
diff --git a/tests/fixtures/runtime/harness.js b/tests/fixtures/runtime/harness.js
new file mode 100644
index 00000000..9d394f14
--- /dev/null
+++ b/tests/fixtures/runtime/harness.js
@@ -0,0 +1,49 @@
+'use strict';
+// Drives infrastructure/lambda/describers.js with a fake AWS adapter built
+// from a JSON fixture, for tests/test_runtime_readers.py. Plain node, no SDK.
+//
+//   node harness.js  
+//
+// responses.json maps "." to {"": value};
+// a missing key, or a value {"$error": "Name"}, makes the call throw an error
+// with that name (AccessDenied by default), as the SDK would. Prints the
+// validations and every policy input the readers produced.
+const fs = require('fs');
+const path = require('path');
+const { validateComponents, READERS } = require(path.join(__dirname, '..', '..', '..', 'infrastructure', 'lambda', 'describers.js'));
+
+const [componentsPath, responsesPath] = process.argv.slice(2);
+const components = JSON.parse(fs.readFileSync(componentsPath));
+const responses = JSON.parse(fs.readFileSync(responsesPath));
+
+function call(service, method) {
+    return async (...args) => {
+        const table = responses[`${service}.${method}`] || {};
+        const key = args.join('|');
+        const value = table[key];
+        if (value === undefined || (value && value.$error)) {
+            const err = new Error('denied');
+            err.name = (value && value.$error) || 'AccessDenied';
+            throw err;
+        }
+        return value;
+    };
+}
+
+const aws = new Proxy({}, {
+    get: (_, service) => new Proxy({}, { get: (__, method) => call(service, method) }),
+});
+
+(async () => {
+    const tags = new Map(Object.entries(responses.tags || {}));
+    const ctx = {
+        aws, region: 'us-east-2', account: '123456789012', tags, components,
+        taggableTypes: JSON.parse(fs.readFileSync(path.join(__dirname, '..', '..', '..', 'infrastructure', 'policy', 'config', 'data.json'))).gate.taggable_types,
+        now: () => Date.parse('2026-11-05T00:00:00Z'),
+    };
+    const inputs = [];
+    let n = 0;
+    const evaluate = async (input) => { inputs.push(input); return { compliant: true, violations: [] }; };
+    const validations = await validateComponents(ctx, components, evaluate, 'terraform.compliance', 'test', () => `r-${n++}`);
+    process.stdout.write(JSON.stringify({ readers: Object.keys(READERS), validations, inputs }));
+})().catch((e) => { console.error(e); process.exit(1); });
diff --git a/tests/fixtures/runtime/responses-compliant.json b/tests/fixtures/runtime/responses-compliant.json
new file mode 100644
index 00000000..d66178f3
--- /dev/null
+++ b/tests/fixtures/runtime/responses-compliant.json
@@ -0,0 +1,377 @@
+{
+ "tags": {
+  "arn:aws:lambda:us-east-2:123456789012:function:samaydlette-com-opa-compliance": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:logs:us-east-2:123456789012:log-group:/aws/lambda/samaydlette-com-opa-compliance": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:cloudwatch:us-east-2:123456789012:alarm:samaydlette-com-evidence-watchdog-vdr-age": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:events:us-east-2:123456789012:rule/samaydlette-com-opa-compliance": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:sns:us-east-2:123456789012:samaydlette-com-evidence-alerts": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:sqs:us-east-2:123456789012:samaydlette-com-opa-compliance-dlq": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:cognito-idp:us-east-2:123456789012:userpool/us-east-2_EXAMPLE": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:kms:us-east-2:123456789012:key/11111111-2222-3333-4444-555555555555": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:kms:us-east-1:123456789012:key/66666666-7777-8888-9999-000000000000": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:apigateway:us-east-2::/apis/abc123": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:apigateway:us-east-2::/apis/abc123/stages/$default": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  }
+ },
+ "iam.getRole": {
+  "samaydlette-com-lambda-opa-role": {
+   "AssumeRolePolicyDocument": "%7B%22Version%22%3A%20%222012-10-17%22%2C%20%22Statement%22%3A%20%5B%7B%22Effect%22%3A%20%22Allow%22%2C%20%22Principal%22%3A%20%7B%22Service%22%3A%20%22lambda.amazonaws.com%22%7D%2C%20%22Action%22%3A%20%22sts%3AAssumeRole%22%7D%5D%7D",
+   "Tags": [
+    {
+     "Key": "Environment",
+     "Value": "prod"
+    },
+    {
+     "Key": "CostCenter",
+     "Value": "website-ops"
+    },
+    {
+     "Key": "DataClassification",
+     "Value": "Internal"
+    },
+    {
+     "Key": "Owner",
+     "Value": "sam-aydlette"
+    },
+    {
+     "Key": "DataSensitivity",
+     "Value": "internal"
+    },
+    {
+     "Key": "MissionCriticality",
+     "Value": "moderate"
+    },
+    {
+     "Key": "InternetReachable",
+     "Value": "false"
+    },
+    {
+     "Key": "Archetype",
+     "Value": "security-tooling"
+    },
+    {
+     "Key": "AgencyScope",
+     "Value": "single"
+    },
+    {
+     "Key": "OwnerRole",
+     "Value": "platform-operator"
+    }
+   ]
+  },
+  "github-actions-deploy-oidc": {
+   "AssumeRolePolicyDocument": "%7B%22Version%22%3A%20%222012-10-17%22%2C%20%22Statement%22%3A%20%5B%7B%22Effect%22%3A%20%22Allow%22%2C%20%22Principal%22%3A%20%7B%22Federated%22%3A%20%22arn%3Aaws%3Aiam%3A%3A123456789012%3Aoidc-provider/token.actions.githubusercontent.com%22%7D%2C%20%22Action%22%3A%20%22sts%3AAssumeRoleWithWebIdentity%22%2C%20%22Condition%22%3A%20%7B%22StringEquals%22%3A%20%7B%22token.actions.githubusercontent.com%3Aaud%22%3A%20%22sts.amazonaws.com%22%7D%2C%20%22StringLike%22%3A%20%7B%22token.actions.githubusercontent.com%3Asub%22%3A%20%22repo%3Asam-aydlette/samaydlette.com%3Aenvironment%3Aprod%22%7D%7D%7D%5D%7D",
+   "Tags": [
+    {
+     "Key": "Environment",
+     "Value": "prod"
+    },
+    {
+     "Key": "CostCenter",
+     "Value": "website-ops"
+    },
+    {
+     "Key": "DataClassification",
+     "Value": "Internal"
+    },
+    {
+     "Key": "Owner",
+     "Value": "sam-aydlette"
+    },
+    {
+     "Key": "DataSensitivity",
+     "Value": "internal"
+    },
+    {
+     "Key": "MissionCriticality",
+     "Value": "moderate"
+    },
+    {
+     "Key": "InternetReachable",
+     "Value": "false"
+    },
+    {
+     "Key": "Archetype",
+     "Value": "security-tooling"
+    },
+    {
+     "Key": "AgencyScope",
+     "Value": "single"
+    },
+    {
+     "Key": "OwnerRole",
+     "Value": "platform-operator"
+    }
+   ]
+  }
+ },
+ "iam.listAttachedRolePolicies": {
+  "samaydlette-com-lambda-opa-role": [],
+  "github-actions-deploy-oidc": [
+   "arn:aws:iam::123456789012:policy/github-actions-deploy"
+  ]
+ },
+ "iam.getRolePolicy": {
+  "samaydlette-com-lambda-opa-role|samaydlette-com-lambda-opa-policy": "%7B%22Version%22%3A%20%222012-10-17%22%2C%20%22Statement%22%3A%20%5B%7B%22Effect%22%3A%20%22Allow%22%2C%20%22Action%22%3A%20%5B%22s3%3AGetBucketVersioning%22%5D%2C%20%22Resource%22%3A%20%5B%22arn%3Aaws%3As3%3A%3A%3Asamaydlette.com%22%5D%7D%5D%7D"
+ },
+ "iam.listAttachedGroupPolicies": {
+  "operators": [
+   "arn:aws:iam::aws:policy/IAMFullAccess"
+  ]
+ },
+ "iam.listGroupPolicies": {
+  "operators": [
+   "s3-bucket-policy"
+  ]
+ },
+ "iam.getGroupPolicy": {
+  "operators|s3-bucket-policy": "%7B%22Version%22%3A%20%222012-10-17%22%2C%20%22Statement%22%3A%20%5B%7B%22Effect%22%3A%20%22Allow%22%2C%20%22Action%22%3A%20%22s3%3A%2A%22%2C%20%22Resource%22%3A%20%5B%22arn%3Aaws%3As3%3A%3A%3Ab%22%2C%20%22arn%3Aaws%3As3%3A%3A%3Ab/%2A%22%5D%7D%5D%7D",
+  "operators|s3-bucket": "%7B%22Version%22%3A%20%222012-10-17%22%2C%20%22Statement%22%3A%20%5B%7B%22Effect%22%3A%20%22Allow%22%2C%20%22Action%22%3A%20%5B%22s3%3AGetObject%22%2C%20%22s3%3APutObject%22%5D%2C%20%22Resource%22%3A%20%22arn%3Aaws%3As3%3A%3A%3Asamaydlette.com/%2A%22%7D%5D%7D"
+ },
+ "iam.getOpenIDConnectProvider": {
+  "arn:aws:iam::123456789012:oidc-provider/token.actions.githubusercontent.com": {
+   "ClientIDList": [
+    "sts.amazonaws.com"
+   ],
+   "Url": "token.actions.githubusercontent.com"
+  }
+ },
+ "lambda.getFunctionConfiguration": {
+  "samaydlette-com-opa-compliance": {
+   "KMSKeyArn": "arn:aws:kms:us-east-2:123456789012:key/11111111-2222-3333-4444-555555555555",
+   "CodeSha256": "Y29kZS1oYXNo",
+   "Runtime": "nodejs22.x"
+  }
+ },
+ "lambda.getFunctionUrlConfig": {
+  "samaydlette-com-opa-compliance": {
+   "$error": "ResourceNotFoundException"
+  }
+ },
+ "logs.describeLogGroup": {
+  "/aws/lambda/samaydlette-com-opa-compliance|us-east-2": {
+   "logGroupName": "/aws/lambda/samaydlette-com-opa-compliance",
+   "retentionInDays": 365,
+   "kmsKeyId": "arn:k"
+  }
+ },
+ "cloudtrail.getTrail": {
+  "arn:aws:cloudtrail:us-east-2:123456789012:trail/samaydlette-com-management|us-east-2": {
+   "IsMultiRegionTrail": true,
+   "LogFileValidationEnabled": true
+  }
+ },
+ "cloudtrail.getTrailStatus": {
+  "arn:aws:cloudtrail:us-east-2:123456789012:trail/samaydlette-com-management|us-east-2": {
+   "IsLogging": true
+  }
+ },
+ "cloudwatch.describeAlarm": {
+  "samaydlette-com-evidence-watchdog-vdr-age|us-east-2": {
+   "ActionsEnabled": true,
+   "AlarmActions": [
+    "arn:aws:sns:us-east-2:123456789012:samaydlette-com-evidence-alerts"
+   ]
+  }
+ },
+ "events.describeRule": {
+  "samaydlette-com-opa-compliance|us-east-2": {
+   "State": "ENABLED"
+  }
+ },
+ "sns.getTopicAttributes": {
+  "arn:aws:sns:us-east-2:123456789012:samaydlette-com-evidence-alerts|us-east-2": {
+   "KmsMasterKeyId": "arn:k"
+  }
+ },
+ "sqs.getQueueAttributes": {
+  "https://sqs.us-east-2.amazonaws.com/123456789012/samaydlette-com-opa-compliance-dlq|us-east-2": {
+   "SqsManagedSseEnabled": "true"
+  }
+ },
+ "dynamodb.describeContinuousBackups": {
+  "samaydlette-com-tflock|us-east-2": "ENABLED"
+ },
+ "cognito.describeUserPool": {
+  "us-east-2_EXAMPLE|us-east-2": {
+   "MfaConfiguration": "ON",
+   "Policies": {
+    "PasswordPolicy": {
+     "MinimumLength": 14
+    }
+   },
+   "AdminCreateUserConfig": {
+    "AllowAdminCreateUserOnly": true
+   }
+  }
+ },
+ "kms.describeKey": {
+  "arn:aws:kms:us-east-2:123456789012:key/11111111-2222-3333-4444-555555555555|us-east-2": {
+   "KeySpec": "SYMMETRIC_DEFAULT",
+   "KeyState": "Enabled"
+  },
+  "arn:aws:kms:us-east-1:123456789012:key/66666666-7777-8888-9999-000000000000|us-east-1": {
+   "KeySpec": "ECC_NIST_P256",
+   "KeyState": "Enabled"
+  }
+ },
+ "kms.getKeyRotationStatus": {
+  "arn:aws:kms:us-east-2:123456789012:key/11111111-2222-3333-4444-555555555555|us-east-2": true
+ },
+ "apigw.getStages": {
+  "abc123|us-east-2": [
+   {
+    "StageName": "$default",
+    "AccessLogSettings": {
+     "DestinationArn": "arn:logs"
+    },
+    "DefaultRouteSettings": {
+     "ThrottlingRateLimit": 20,
+     "ThrottlingBurstLimit": 10
+    }
+   }
+  ]
+ },
+ "apigw.getRoutes": {
+  "abc123|us-east-2": [
+   {
+    "RouteKey": "$default",
+    "AuthorizationType": "NONE"
+   },
+   {
+    "RouteKey": "ANY /api/{proxy+}",
+    "AuthorizationType": "JWT"
+   }
+  ]
+ },
+ "route53.getDnssecStatus": {
+  "Z0EXAMPLE": "SIGNING"
+ },
+ "acm.describeCertificate": {
+  "arn:aws:acm:us-east-1:123456789012:certificate/cert-1|us-east-1": {
+   "Status": "ISSUED",
+   "NotAfter": "2027-04-29T23:59:59Z"
+  }
+ },
+ "_note": "Live-shaped, compliant responses (shapes copied from read-only calls against the production account, identifiers replaced)."
+}
\ No newline at end of file
diff --git a/tests/fixtures/runtime/responses-denied.json b/tests/fixtures/runtime/responses-denied.json
new file mode 100644
index 00000000..f3cd8d06
--- /dev/null
+++ b/tests/fixtures/runtime/responses-denied.json
@@ -0,0 +1,3 @@
+{
+ "_note": "Every call denied: the readers must report unread attributes, never findings."
+}
\ No newline at end of file
diff --git a/tests/fixtures/runtime/responses-drifted.json b/tests/fixtures/runtime/responses-drifted.json
new file mode 100644
index 00000000..f080a5b5
--- /dev/null
+++ b/tests/fixtures/runtime/responses-drifted.json
@@ -0,0 +1,365 @@
+{
+ "tags": {
+  "arn:aws:lambda:us-east-2:123456789012:function:samaydlette-com-opa-compliance": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:logs:us-east-2:123456789012:log-group:/aws/lambda/samaydlette-com-opa-compliance": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:cloudwatch:us-east-2:123456789012:alarm:samaydlette-com-evidence-watchdog-vdr-age": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:events:us-east-2:123456789012:rule/samaydlette-com-opa-compliance": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:sns:us-east-2:123456789012:samaydlette-com-evidence-alerts": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:sqs:us-east-2:123456789012:samaydlette-com-opa-compliance-dlq": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:cognito-idp:us-east-2:123456789012:userpool/us-east-2_EXAMPLE": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:kms:us-east-2:123456789012:key/11111111-2222-3333-4444-555555555555": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:kms:us-east-1:123456789012:key/66666666-7777-8888-9999-000000000000": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:apigateway:us-east-2::/apis/abc123": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  },
+  "arn:aws:apigateway:us-east-2::/apis/abc123/stages/$default": {
+   "Environment": "prod",
+   "CostCenter": "website-ops",
+   "DataClassification": "Internal",
+   "Owner": "sam-aydlette",
+   "DataSensitivity": "internal",
+   "MissionCriticality": "moderate",
+   "InternetReachable": "false",
+   "Archetype": "security-tooling",
+   "AgencyScope": "single",
+   "OwnerRole": "platform-operator"
+  }
+ },
+ "iam.getRole": {
+  "samaydlette-com-lambda-opa-role": {
+   "AssumeRolePolicyDocument": "%7B%22Version%22%3A%20%222012-10-17%22%2C%20%22Statement%22%3A%20%5B%7B%22Effect%22%3A%20%22Allow%22%2C%20%22Principal%22%3A%20%7B%22AWS%22%3A%20%22%2A%22%7D%2C%20%22Action%22%3A%20%22sts%3AAssumeRole%22%7D%5D%7D",
+   "Tags": [
+    {
+     "Key": "Environment",
+     "Value": "prod"
+    },
+    {
+     "Key": "CostCenter",
+     "Value": "website-ops"
+    },
+    {
+     "Key": "DataClassification",
+     "Value": "Internal"
+    },
+    {
+     "Key": "Owner",
+     "Value": "sam-aydlette"
+    },
+    {
+     "Key": "DataSensitivity",
+     "Value": "internal"
+    },
+    {
+     "Key": "MissionCriticality",
+     "Value": "moderate"
+    },
+    {
+     "Key": "InternetReachable",
+     "Value": "false"
+    },
+    {
+     "Key": "Archetype",
+     "Value": "security-tooling"
+    },
+    {
+     "Key": "AgencyScope",
+     "Value": "single"
+    },
+    {
+     "Key": "OwnerRole",
+     "Value": "platform-operator"
+    }
+   ]
+  },
+  "github-actions-deploy-oidc": {
+   "AssumeRolePolicyDocument": "%7B%22Version%22%3A%20%222012-10-17%22%2C%20%22Statement%22%3A%20%5B%7B%22Effect%22%3A%20%22Allow%22%2C%20%22Principal%22%3A%20%7B%22Federated%22%3A%20%22arn%3Aaws%3Aiam%3A%3A123456789012%3Aoidc-provider/token.actions.githubusercontent.com%22%7D%2C%20%22Action%22%3A%20%22sts%3AAssumeRoleWithWebIdentity%22%2C%20%22Condition%22%3A%20%7B%22StringLike%22%3A%20%7B%22token.actions.githubusercontent.com%3Asub%22%3A%20%22repo%3A%2A%22%7D%7D%7D%5D%7D",
+   "Tags": [
+    {
+     "Key": "Environment",
+     "Value": "prod"
+    },
+    {
+     "Key": "CostCenter",
+     "Value": "website-ops"
+    },
+    {
+     "Key": "DataClassification",
+     "Value": "Internal"
+    },
+    {
+     "Key": "Owner",
+     "Value": "sam-aydlette"
+    },
+    {
+     "Key": "DataSensitivity",
+     "Value": "internal"
+    },
+    {
+     "Key": "MissionCriticality",
+     "Value": "moderate"
+    },
+    {
+     "Key": "InternetReachable",
+     "Value": "false"
+    },
+    {
+     "Key": "Archetype",
+     "Value": "security-tooling"
+    },
+    {
+     "Key": "AgencyScope",
+     "Value": "single"
+    },
+    {
+     "Key": "OwnerRole",
+     "Value": "platform-operator"
+    }
+   ]
+  }
+ },
+ "iam.listAttachedRolePolicies": {
+  "samaydlette-com-lambda-opa-role": [],
+  "github-actions-deploy-oidc": [
+   "arn:aws:iam::123456789012:policy/github-actions-deploy"
+  ]
+ },
+ "iam.getRolePolicy": {
+  "samaydlette-com-lambda-opa-role|samaydlette-com-lambda-opa-policy": "%7B%22Version%22%3A%20%222012-10-17%22%2C%20%22Statement%22%3A%20%5B%7B%22Effect%22%3A%20%22Allow%22%2C%20%22Action%22%3A%20%22%2A%22%2C%20%22Resource%22%3A%20%22%2A%22%7D%5D%7D"
+ },
+ "iam.listAttachedGroupPolicies": {
+  "operators": [
+   "arn:aws:iam::aws:policy/AdministratorAccess"
+  ]
+ },
+ "iam.listGroupPolicies": {
+  "operators": [
+   "s3-bucket-policy"
+  ]
+ },
+ "iam.getGroupPolicy": {
+  "operators|s3-bucket-policy": "%7B%22Version%22%3A%20%222012-10-17%22%2C%20%22Statement%22%3A%20%5B%7B%22Effect%22%3A%20%22Allow%22%2C%20%22Action%22%3A%20%22s3%3A%2A%22%2C%20%22Resource%22%3A%20%5B%22arn%3Aaws%3As3%3A%3A%3Ab%22%2C%20%22arn%3Aaws%3As3%3A%3A%3Ab/%2A%22%5D%7D%5D%7D",
+  "operators|s3-bucket": "%7B%22Version%22%3A%20%222012-10-17%22%2C%20%22Statement%22%3A%20%5B%7B%22Effect%22%3A%20%22Allow%22%2C%20%22Action%22%3A%20%22%2A%22%2C%20%22Resource%22%3A%20%22%2A%22%7D%5D%7D"
+ },
+ "iam.getOpenIDConnectProvider": {
+  "arn:aws:iam::123456789012:oidc-provider/token.actions.githubusercontent.com": {
+   "ClientIDList": [
+    "sts.amazonaws.com",
+    "other"
+   ],
+   "Url": "token.actions.githubusercontent.com"
+  }
+ },
+ "lambda.getFunctionConfiguration": {
+  "samaydlette-com-opa-compliance": {
+   "KMSKeyArn": null,
+   "CodeSha256": "b3V0LW9mLWJhbmQ=",
+   "Runtime": "nodejs22.x"
+  }
+ },
+ "lambda.getFunctionUrlConfig": {
+  "samaydlette-com-opa-compliance": {
+   "AuthType": "NONE"
+  }
+ },
+ "logs.describeLogGroup": {
+  "/aws/lambda/samaydlette-com-opa-compliance|us-east-2": {
+   "logGroupName": "/aws/lambda/samaydlette-com-opa-compliance",
+   "retentionInDays": 7
+  }
+ },
+ "cloudtrail.getTrail": {
+  "arn:aws:cloudtrail:us-east-2:123456789012:trail/samaydlette-com-management|us-east-2": {
+   "IsMultiRegionTrail": true,
+   "LogFileValidationEnabled": false
+  }
+ },
+ "cloudtrail.getTrailStatus": {
+  "arn:aws:cloudtrail:us-east-2:123456789012:trail/samaydlette-com-management|us-east-2": {
+   "IsLogging": false
+  }
+ },
+ "cloudwatch.describeAlarm": {
+  "samaydlette-com-evidence-watchdog-vdr-age|us-east-2": {
+   "ActionsEnabled": false,
+   "AlarmActions": [
+    "arn:aws:sns:us-east-2:123456789012:samaydlette-com-evidence-alerts"
+   ]
+  }
+ },
+ "events.describeRule": {
+  "samaydlette-com-opa-compliance|us-east-2": {
+   "State": "DISABLED"
+  }
+ },
+ "sns.getTopicAttributes": {
+  "arn:aws:sns:us-east-2:123456789012:samaydlette-com-evidence-alerts|us-east-2": {}
+ },
+ "sqs.getQueueAttributes": {
+  "https://sqs.us-east-2.amazonaws.com/123456789012/samaydlette-com-opa-compliance-dlq|us-east-2": {
+   "SqsManagedSseEnabled": "false"
+  }
+ },
+ "dynamodb.describeContinuousBackups": {
+  "samaydlette-com-tflock|us-east-2": "DISABLED"
+ },
+ "cognito.describeUserPool": {
+  "us-east-2_EXAMPLE|us-east-2": {
+   "MfaConfiguration": "OPTIONAL",
+   "Policies": {
+    "PasswordPolicy": {
+     "MinimumLength": 8
+    }
+   },
+   "AdminCreateUserConfig": {
+    "AllowAdminCreateUserOnly": false
+   }
+  }
+ },
+ "kms.describeKey": {
+  "arn:aws:kms:us-east-2:123456789012:key/11111111-2222-3333-4444-555555555555|us-east-2": {
+   "KeySpec": "SYMMETRIC_DEFAULT",
+   "KeyState": "Enabled"
+  },
+  "arn:aws:kms:us-east-1:123456789012:key/66666666-7777-8888-9999-000000000000|us-east-1": {
+   "KeySpec": "ECC_NIST_P256",
+   "KeyState": "PendingDeletion"
+  }
+ },
+ "kms.getKeyRotationStatus": {
+  "arn:aws:kms:us-east-2:123456789012:key/11111111-2222-3333-4444-555555555555|us-east-2": false
+ },
+ "apigw.getStages": {
+  "abc123|us-east-2": [
+   {
+    "StageName": "$default",
+    "DefaultRouteSettings": {}
+   }
+  ]
+ },
+ "apigw.getRoutes": {
+  "abc123|us-east-2": [
+   {
+    "RouteKey": "ANY /api/{proxy+}",
+    "AuthorizationType": "NONE"
+   }
+  ]
+ },
+ "route53.getDnssecStatus": {
+  "Z0EXAMPLE": "NOT_SIGNING"
+ },
+ "acm.describeCertificate": {
+  "arn:aws:acm:us-east-1:123456789012:certificate/cert-1|us-east-1": {
+   "Status": "ISSUED",
+   "NotAfter": "2026-11-20T00:00:00Z"
+  }
+ },
+ "_note": "Known-bad live account: every reader returns a drifted value the policy must catch."
+}
\ No newline at end of file
diff --git a/tests/fixtures/scg/aws-bad.json b/tests/fixtures/scg/aws-bad.json
new file mode 100644
index 00000000..45bd0437
--- /dev/null
+++ b/tests/fixtures/scg/aws-bad.json
@@ -0,0 +1,273 @@
+{
+ "$comment": "Known-bad: the root user has an access key and a collector user holds a write permission; neither is covered by a decision, so the comparison must fail the deploy.",
+ "responses": {
+  "iam get-role-policy --role-name github-actions-evidence-nightly-oidc --policy-name evidence-nightly-audit-log-review": {
+   "PolicyDocument": {"Version": "2012-10-17", "Statement": [{"Sid": "AuditLogReviewReads", "Effect": "Allow", "Action": "cloudtrail:LookupEvents", "Resource": "*"}]}
+  },
+  "iam get-account-summary": {
+   "SummaryMap": {
+    "AccountMFAEnabled": 1,
+    "AccountAccessKeysPresent": 1
+   }
+  },
+  "iam list-virtual-mfa-devices --assignment-status Assigned": {
+   "VirtualMFADevices": [
+    {
+     "User": {
+      "Arn": "arn:aws:iam::123456789012:root"
+     }
+    },
+    {
+     "User": {
+      "Arn": "arn:aws:iam::123456789012:user/op-user-not-for-publication"
+     }
+    }
+   ]
+  },
+  "iam get-account-password-policy": {
+   "PasswordPolicy": {
+    "MinimumPasswordLength": 14,
+    "RequireSymbols": true,
+    "RequireNumbers": true,
+    "RequireUppercaseCharacters": true,
+    "RequireLowercaseCharacters": true,
+    "PasswordReusePrevention": 24,
+    "MaxPasswordAge": 90
+   }
+  },
+  "sts get-caller-identity": {
+   "Account": "123456789012"
+  },
+  "s3control get-public-access-block --account-id 123456789012": {
+   "PublicAccessBlockConfiguration": {
+    "BlockPublicAcls": true,
+    "IgnorePublicAcls": true,
+    "BlockPublicPolicy": true,
+    "RestrictPublicBuckets": true
+   }
+  },
+  "iam list-users": {
+   "Users": [
+    {
+     "UserName": "op-user-not-for-publication"
+    },
+    {
+     "UserName": "collector"
+    },
+    {
+     "UserName": "inert"
+    }
+   ]
+  },
+  "iam list-groups-for-user --user-name op-user-not-for-publication": {
+   "Groups": [
+    {
+     "GroupName": "operators"
+    }
+   ]
+  },
+  "iam list-groups-for-user --user-name collector": {
+   "Groups": [
+    {
+     "GroupName": "read-only"
+    }
+   ]
+  },
+  "iam list-groups-for-user --user-name inert": {
+   "Groups": []
+  },
+  "iam get-login-profile --user-name collector": {
+   "error": "NoSuchEntity"
+  },
+  "iam get-login-profile --user-name inert": {
+   "error": "NoSuchEntity"
+  },
+  "iam get-login-profile --user-name op-user-not-for-publication": {
+   "error": "NoSuchEntity"
+  },
+  "iam list-attached-user-policies --user-name collector": {
+   "AttachedPolicies": [
+    {
+     "PolicyName": "SecurityAudit"
+    }
+   ]
+  },
+  "iam list-user-policies --user-name collector": {
+   "PolicyNames": [
+    "supplement"
+   ]
+  },
+  "iam get-user-policy --user-name collector --policy-name supplement": {
+   "PolicyDocument": {
+    "Statement": [
+     {
+      "Effect": "Allow",
+      "Action": [
+       "iam:PutUserPolicy"
+      ],
+      "Resource": "*"
+     }
+    ]
+   }
+  },
+  "iam list-attached-group-policies --group-name read-only": {
+   "AttachedPolicies": [
+    {
+     "PolicyName": "ReadOnlyAccess"
+    }
+   ]
+  },
+  "iam list-group-policies --group-name read-only": {
+   "PolicyNames": [
+    "deny-secrets"
+   ]
+  },
+  "iam get-group-policy --group-name read-only --policy-name deny-secrets": {
+   "PolicyDocument": {
+    "Statement": [
+     {
+      "Effect": "Deny",
+      "Action": [
+       "secretsmanager:GetSecretValue",
+       "kms:Decrypt"
+      ],
+      "Resource": "*"
+     }
+    ]
+   }
+  },
+  "iam list-attached-user-policies --user-name inert": {
+   "AttachedPolicies": []
+  },
+  "iam list-user-policies --user-name inert": {
+   "PolicyNames": []
+  },
+  "iam list-mfa-devices --user-name op-user-not-for-publication": {
+   "MFADevices": [
+    {
+     "SerialNumber": "x"
+    }
+   ]
+  },
+  "iam list-access-keys --user-name op-user-not-for-publication": {
+   "AccessKeyMetadata": [
+    {
+     "Status": "Active",
+     "CreateDate": "2026-10-01T00:00:00Z"
+    },
+    {
+     "Status": "Inactive",
+     "CreateDate": "2025-01-01T00:00:00Z"
+    }
+   ]
+  },
+  "iam get-role --role-name github-actions-deploy-oidc": {
+   "Role": {
+    "AssumeRolePolicyDocument": {
+     "Statement": [
+      {
+       "Condition": {
+        "StringLike": {
+         "token.actions.githubusercontent.com:sub": "repo:sam-aydlette/samaydlette.com:environment:prod"
+        }
+       }
+      }
+     ]
+    }
+   }
+  },
+  "iam get-role --role-name github-actions-plan-oidc": {
+   "Role": {
+    "AssumeRolePolicyDocument": {
+     "Statement": [
+      {
+       "Condition": {
+        "StringLike": {
+         "token.actions.githubusercontent.com:sub": [
+          "repo:sam-aydlette/samaydlette.com:pull_request",
+          "repo:sam-aydlette/samaydlette.com:ref:refs/heads/main"
+         ]
+        }
+       }
+      }
+     ]
+    }
+   }
+  },
+  "iam get-role --role-name github-actions-evidence-nightly-oidc": {
+   "Role": {
+    "AssumeRolePolicyDocument": {
+     "Statement": [
+      {
+       "Condition": {
+        "StringEquals": {
+         "token.actions.githubusercontent.com:sub": "repo:sam-aydlette/samaydlette.com:environment:evidence-nightly"
+        }
+       }
+      }
+     ]
+    }
+   }
+  },
+  "iam get-role --role-name github-actions-package-maintenance-oidc": {
+   "Role": {
+    "AssumeRolePolicyDocument": {
+     "Statement": [
+      {
+       "Condition": {
+        "StringEquals": {
+         "token.actions.githubusercontent.com:sub": "repo:sam-aydlette/samaydlette.com:environment:package-maintenance"
+        }
+       }
+      }
+     ]
+    }
+   }
+  },
+  "iam get-role --role-name github-actions-incident-reports-oidc": {
+   "Role": {
+    "AssumeRolePolicyDocument": {
+     "Statement": [
+      {
+       "Condition": {
+        "StringEquals": {
+         "token.actions.githubusercontent.com:sub": ["repo:sam-aydlette/samaydlette.com:environment:incident-reports", "repo:sam-aydlette/samaydlette.com:environment:prod"]
+        }
+       }
+      }
+     ]
+    }
+   }
+  },
+  "iam get-role-policy --role-name github-actions-package-maintenance-oidc --policy-name package-maintenance-publish": {
+   "PolicyDocument": {
+    "Version": "2012-10-17",
+    "Statement": [
+     {
+      "Sid": "PublishCertificationPackageOnly",
+      "Effect": "Allow",
+      "Action": "s3:PutObject",
+      "Resource": ["arn:aws:s3:::samaydlette.com/.well-known/security-decision-record.json", "arn:aws:s3:::samaydlette.com/.well-known/security-decision-record.bundle", "arn:aws:s3:::samaydlette.com/.well-known/security-decision-record.md", "arn:aws:s3:::samaydlette.com/.well-known/security-decision-record.view.md", "arn:aws:s3:::samaydlette.com/.well-known/security-decision-record.json.intoto.jsonl", "arn:aws:s3:::samaydlette.com/.well-known/certification-package-overview.json", "arn:aws:s3:::samaydlette.com/.well-known/certification-package-overview.bundle", "arn:aws:s3:::samaydlette.com/.well-known/certification-package-overview.md", "arn:aws:s3:::samaydlette.com/.well-known/certification-package-overview.view.md", "arn:aws:s3:::samaydlette.com/.well-known/ongoing-certification-report.json", "arn:aws:s3:::samaydlette.com/.well-known/ongoing-certification-report.bundle", "arn:aws:s3:::samaydlette.com/.well-known/ongoing-certification-report.md", "arn:aws:s3:::samaydlette.com/.well-known/ongoing-certification-report.view.md", "arn:aws:s3:::samaydlette.com/.well-known/quarterly-review.ics", "arn:aws:s3:::samaydlette.com/.well-known/ocr-issues.json", "arn:aws:s3:::samaydlette.com/.well-known/ocr-issues.view.md", "arn:aws:s3:::samaydlette.com/.well-known/ocr-issues.bundle", "arn:aws:s3:::samaydlette.com/.well-known/ocr-issue-*", "arn:aws:s3:::samaydlette.com/.well-known/quarterly-reviews.json", "arn:aws:s3:::samaydlette.com/.well-known/quarterly-reviews.view.md", "arn:aws:s3:::samaydlette.com/.well-known/quarterly-reviews.bundle", "arn:aws:s3:::samaydlette.com/.well-known/quarterly-review-*", "arn:aws:s3:::samaydlette.com/.well-known/security-reviews.json", "arn:aws:s3:::samaydlette.com/.well-known/security-reviews.view.md", "arn:aws:s3:::samaydlette.com/.well-known/security-reviews.bundle", "arn:aws:s3:::samaydlette.com/.well-known/security-review-*", "arn:aws:s3:::samaydlette.com/.well-known/snapshot-*", "arn:aws:s3:::samaydlette.com/.well-known/snapshots/*"]
+     }
+    ]
+   }
+  },
+  "cognito-idp describe-user-pool --region us-east-2 --user-pool-id pool-1": {
+   "UserPool": {
+    "MfaConfiguration": "ON",
+    "AdminCreateUserConfig": {
+     "AllowAdminCreateUserOnly": true
+    },
+    "Policies": {
+     "PasswordPolicy": {
+      "MinimumLength": 14,
+      "RequireUppercase": true,
+      "RequireLowercase": true,
+      "RequireNumbers": true,
+      "RequireSymbols": true
+     }
+    }
+   }
+  }
+ }
+}
\ No newline at end of file
diff --git a/tests/fixtures/scg/aws-good.json b/tests/fixtures/scg/aws-good.json
new file mode 100644
index 00000000..797d9723
--- /dev/null
+++ b/tests/fixtures/scg/aws-good.json
@@ -0,0 +1,275 @@
+{
+ "$comment": "Fake read-only AWS responses for tests/test_secure_configuration.py: every setting matches the guide, and root and operator MFA are virtual TOTP (the deviation DEC-150 accepts). Account number is AWS's documentation example.",
+ "responses": {
+  "iam get-role-policy --role-name github-actions-evidence-nightly-oidc --policy-name evidence-nightly-audit-log-review": {
+   "PolicyDocument": {"Version": "2012-10-17", "Statement": [{"Sid": "AuditLogReviewReads", "Effect": "Allow", "Action": "cloudtrail:LookupEvents", "Resource": "*"}]}
+  },
+  "iam get-account-summary": {
+   "SummaryMap": {
+    "AccountMFAEnabled": 1,
+    "AccountAccessKeysPresent": 0
+   }
+  },
+  "iam list-virtual-mfa-devices --assignment-status Assigned": {
+   "VirtualMFADevices": [
+    {
+     "User": {
+      "Arn": "arn:aws:iam::123456789012:root"
+     }
+    },
+    {
+     "User": {
+      "Arn": "arn:aws:iam::123456789012:user/op-user-not-for-publication"
+     }
+    }
+   ]
+  },
+  "iam get-account-password-policy": {
+   "PasswordPolicy": {
+    "MinimumPasswordLength": 14,
+    "RequireSymbols": true,
+    "RequireNumbers": true,
+    "RequireUppercaseCharacters": true,
+    "RequireLowercaseCharacters": true,
+    "PasswordReusePrevention": 24,
+    "MaxPasswordAge": 90
+   }
+  },
+  "sts get-caller-identity": {
+   "Account": "123456789012"
+  },
+  "s3control get-public-access-block --account-id 123456789012": {
+   "PublicAccessBlockConfiguration": {
+    "BlockPublicAcls": true,
+    "IgnorePublicAcls": true,
+    "BlockPublicPolicy": true,
+    "RestrictPublicBuckets": true
+   }
+  },
+  "iam list-users": {
+   "Users": [
+    {
+     "UserName": "op-user-not-for-publication"
+    },
+    {
+     "UserName": "collector"
+    },
+    {
+     "UserName": "inert"
+    }
+   ]
+  },
+  "iam list-groups-for-user --user-name op-user-not-for-publication": {
+   "Groups": [
+    {
+     "GroupName": "operators"
+    }
+   ]
+  },
+  "iam list-groups-for-user --user-name collector": {
+   "Groups": [
+    {
+     "GroupName": "read-only"
+    }
+   ]
+  },
+  "iam list-groups-for-user --user-name inert": {
+   "Groups": []
+  },
+  "iam get-login-profile --user-name collector": {
+   "error": "NoSuchEntity"
+  },
+  "iam get-login-profile --user-name inert": {
+   "error": "NoSuchEntity"
+  },
+  "iam get-login-profile --user-name op-user-not-for-publication": {
+   "error": "NoSuchEntity"
+  },
+  "iam list-attached-user-policies --user-name collector": {
+   "AttachedPolicies": [
+    {
+     "PolicyName": "SecurityAudit"
+    }
+   ]
+  },
+  "iam list-user-policies --user-name collector": {
+   "PolicyNames": [
+    "supplement"
+   ]
+  },
+  "iam get-user-policy --user-name collector --policy-name supplement": {
+   "PolicyDocument": {
+    "Statement": [
+     {
+      "Effect": "Allow",
+      "Action": [
+       "kms:List*",
+       "apigateway:GET",
+       "cognito-idp:Describe*"
+      ],
+      "Resource": "*"
+     }
+    ]
+   }
+  },
+  "iam list-attached-group-policies --group-name read-only": {
+   "AttachedPolicies": [
+    {
+     "PolicyName": "ReadOnlyAccess"
+    }
+   ]
+  },
+  "iam list-group-policies --group-name read-only": {
+   "PolicyNames": [
+    "deny-secrets"
+   ]
+  },
+  "iam get-group-policy --group-name read-only --policy-name deny-secrets": {
+   "PolicyDocument": {
+    "Statement": [
+     {
+      "Effect": "Deny",
+      "Action": [
+       "secretsmanager:GetSecretValue",
+       "kms:Decrypt"
+      ],
+      "Resource": "*"
+     }
+    ]
+   }
+  },
+  "iam list-attached-user-policies --user-name inert": {
+   "AttachedPolicies": []
+  },
+  "iam list-user-policies --user-name inert": {
+   "PolicyNames": []
+  },
+  "iam list-mfa-devices --user-name op-user-not-for-publication": {
+   "MFADevices": [
+    {
+     "SerialNumber": "x"
+    }
+   ]
+  },
+  "iam list-access-keys --user-name op-user-not-for-publication": {
+   "AccessKeyMetadata": [
+    {
+     "Status": "Active",
+     "CreateDate": "2026-10-01T00:00:00Z"
+    },
+    {
+     "Status": "Inactive",
+     "CreateDate": "2025-01-01T00:00:00Z"
+    }
+   ]
+  },
+  "iam get-role --role-name github-actions-deploy-oidc": {
+   "Role": {
+    "AssumeRolePolicyDocument": {
+     "Statement": [
+      {
+       "Condition": {
+        "StringLike": {
+         "token.actions.githubusercontent.com:sub": "repo:sam-aydlette/samaydlette.com:environment:prod"
+        }
+       }
+      }
+     ]
+    }
+   }
+  },
+  "iam get-role --role-name github-actions-plan-oidc": {
+   "Role": {
+    "AssumeRolePolicyDocument": {
+     "Statement": [
+      {
+       "Condition": {
+        "StringLike": {
+         "token.actions.githubusercontent.com:sub": [
+          "repo:sam-aydlette/samaydlette.com:pull_request",
+          "repo:sam-aydlette/samaydlette.com:ref:refs/heads/main"
+         ]
+        }
+       }
+      }
+     ]
+    }
+   }
+  },
+  "iam get-role --role-name github-actions-evidence-nightly-oidc": {
+   "Role": {
+    "AssumeRolePolicyDocument": {
+     "Statement": [
+      {
+       "Condition": {
+        "StringEquals": {
+         "token.actions.githubusercontent.com:sub": "repo:sam-aydlette/samaydlette.com:environment:evidence-nightly"
+        }
+       }
+      }
+     ]
+    }
+   }
+  },
+  "iam get-role --role-name github-actions-package-maintenance-oidc": {
+   "Role": {
+    "AssumeRolePolicyDocument": {
+     "Statement": [
+      {
+       "Condition": {
+        "StringEquals": {
+         "token.actions.githubusercontent.com:sub": "repo:sam-aydlette/samaydlette.com:environment:package-maintenance"
+        }
+       }
+      }
+     ]
+    }
+   }
+  },
+  "iam get-role --role-name github-actions-incident-reports-oidc": {
+   "Role": {
+    "AssumeRolePolicyDocument": {
+     "Statement": [
+      {
+       "Condition": {
+        "StringEquals": {
+         "token.actions.githubusercontent.com:sub": ["repo:sam-aydlette/samaydlette.com:environment:incident-reports", "repo:sam-aydlette/samaydlette.com:environment:prod"]
+        }
+       }
+      }
+     ]
+    }
+   }
+  },
+  "iam get-role-policy --role-name github-actions-package-maintenance-oidc --policy-name package-maintenance-publish": {
+   "PolicyDocument": {
+    "Version": "2012-10-17",
+    "Statement": [
+     {
+      "Sid": "PublishCertificationPackageOnly",
+      "Effect": "Allow",
+      "Action": "s3:PutObject",
+      "Resource": ["arn:aws:s3:::samaydlette.com/.well-known/security-decision-record.json", "arn:aws:s3:::samaydlette.com/.well-known/security-decision-record.bundle", "arn:aws:s3:::samaydlette.com/.well-known/security-decision-record.md", "arn:aws:s3:::samaydlette.com/.well-known/security-decision-record.view.md", "arn:aws:s3:::samaydlette.com/.well-known/security-decision-record.json.intoto.jsonl", "arn:aws:s3:::samaydlette.com/.well-known/certification-package-overview.json", "arn:aws:s3:::samaydlette.com/.well-known/certification-package-overview.bundle", "arn:aws:s3:::samaydlette.com/.well-known/certification-package-overview.md", "arn:aws:s3:::samaydlette.com/.well-known/certification-package-overview.view.md", "arn:aws:s3:::samaydlette.com/.well-known/ongoing-certification-report.json", "arn:aws:s3:::samaydlette.com/.well-known/ongoing-certification-report.bundle", "arn:aws:s3:::samaydlette.com/.well-known/ongoing-certification-report.md", "arn:aws:s3:::samaydlette.com/.well-known/ongoing-certification-report.view.md", "arn:aws:s3:::samaydlette.com/.well-known/quarterly-review.ics", "arn:aws:s3:::samaydlette.com/.well-known/ocr-issues.json", "arn:aws:s3:::samaydlette.com/.well-known/ocr-issues.view.md", "arn:aws:s3:::samaydlette.com/.well-known/ocr-issues.bundle", "arn:aws:s3:::samaydlette.com/.well-known/ocr-issue-*", "arn:aws:s3:::samaydlette.com/.well-known/quarterly-reviews.json", "arn:aws:s3:::samaydlette.com/.well-known/quarterly-reviews.view.md", "arn:aws:s3:::samaydlette.com/.well-known/quarterly-reviews.bundle", "arn:aws:s3:::samaydlette.com/.well-known/quarterly-review-*", "arn:aws:s3:::samaydlette.com/.well-known/security-reviews.json", "arn:aws:s3:::samaydlette.com/.well-known/security-reviews.view.md", "arn:aws:s3:::samaydlette.com/.well-known/security-reviews.bundle", "arn:aws:s3:::samaydlette.com/.well-known/security-review-*", "arn:aws:s3:::samaydlette.com/.well-known/snapshot-*", "arn:aws:s3:::samaydlette.com/.well-known/snapshots/*"]
+     }
+    ]
+   }
+  },
+  "cognito-idp describe-user-pool --region us-east-2 --user-pool-id pool-1": {
+   "UserPool": {
+    "MfaConfiguration": "ON",
+    "AdminCreateUserConfig": {
+     "AllowAdminCreateUserOnly": true
+    },
+    "Policies": {
+     "PasswordPolicy": {
+      "MinimumLength": 14,
+      "RequireUppercase": true,
+      "RequireLowercase": true,
+      "RequireNumbers": true,
+      "RequireSymbols": true
+     }
+    }
+   }
+  }
+ }
+}
\ No newline at end of file
diff --git a/tests/fixtures/scg/aws-maintainer-scope-no-views.json b/tests/fixtures/scg/aws-maintainer-scope-no-views.json
new file mode 100644
index 00000000..fdc3d05a
--- /dev/null
+++ b/tests/fixtures/scg/aws-maintainer-scope-no-views.json
@@ -0,0 +1,35 @@
+{
+ "$comment": "Known-bad: the package maintenance role's publish policy as it stood before the readable views were added (no .view.md keys). Merged over aws-good.json; ci-roles.maintenance-publish-scope must be a deviation, so the deploy stops before the SDR is built.",
+ "responses": {
+  "iam get-role-policy --role-name github-actions-package-maintenance-oidc --policy-name package-maintenance-publish": {
+   "PolicyDocument": {
+    "Version": "2012-10-17",
+    "Statement": [
+     {
+      "Sid": "PublishCertificationPackageOnly",
+      "Effect": "Allow",
+      "Action": "s3:PutObject",
+      "Resource": [
+       "arn:aws:s3:::samaydlette.com/.well-known/security-decision-record.json",
+       "arn:aws:s3:::samaydlette.com/.well-known/security-decision-record.bundle",
+       "arn:aws:s3:::samaydlette.com/.well-known/security-decision-record.md",
+       "arn:aws:s3:::samaydlette.com/.well-known/security-decision-record.json.intoto.jsonl",
+       "arn:aws:s3:::samaydlette.com/.well-known/certification-package-overview.json",
+       "arn:aws:s3:::samaydlette.com/.well-known/certification-package-overview.bundle",
+       "arn:aws:s3:::samaydlette.com/.well-known/certification-package-overview.md",
+       "arn:aws:s3:::samaydlette.com/.well-known/ongoing-certification-report.json",
+       "arn:aws:s3:::samaydlette.com/.well-known/ongoing-certification-report.bundle",
+       "arn:aws:s3:::samaydlette.com/.well-known/ongoing-certification-report.md",
+       "arn:aws:s3:::samaydlette.com/.well-known/quarterly-review.ics",
+       "arn:aws:s3:::samaydlette.com/.well-known/ocr-issues.json",
+       "arn:aws:s3:::samaydlette.com/.well-known/ocr-issues.bundle",
+       "arn:aws:s3:::samaydlette.com/.well-known/ocr-issue-*",
+       "arn:aws:s3:::samaydlette.com/.well-known/snapshot-*",
+       "arn:aws:s3:::samaydlette.com/.well-known/snapshots/*"
+      ]
+     }
+    ]
+   }
+  }
+ }
+}
diff --git a/tests/fixtures/scg/aws-nightly-no-lookup.json b/tests/fixtures/scg/aws-nightly-no-lookup.json
new file mode 100644
index 00000000..b222831a
--- /dev/null
+++ b/tests/fixtures/scg/aws-nightly-no-lookup.json
@@ -0,0 +1,8 @@
+{
+ "$comment": "Known-bad: the evidence nightly's audit-log read policy without cloudtrail:LookupEvents (an older or hand-edited grant). Merged over aws-good.json; ci-roles.nightly-audit-reads must be a deviation, so the deploy stops before the SDR counts the audit-log review.",
+ "responses": {
+  "iam get-role-policy --role-name github-actions-evidence-nightly-oidc --policy-name evidence-nightly-audit-log-review": {
+   "PolicyDocument": {"Version": "2012-10-17", "Statement": [{"Sid": "AuditLogReviewReads", "Effect": "Allow", "Action": "cloudtrail:GetTrailStatus", "Resource": "*"}]}
+  }
+ }
+}
diff --git a/tests/fixtures/scg/github-good.json b/tests/fixtures/scg/github-good.json
new file mode 100644
index 00000000..0ee0cbb6
--- /dev/null
+++ b/tests/fixtures/scg/github-good.json
@@ -0,0 +1,23 @@
+{
+ "schema": "manual-settings/1",
+ "checks": [
+  {
+   "id": "github_settings",
+   "status": "ok",
+   "detail": "",
+   "facts": {
+    "prod_required_reviewers": 1,
+    "evidence_nightly_branches": [
+     "main"
+    ],
+    "main_required_checks": [
+     "OPA Compliance Check",
+     "Security Scan",
+     "Unit tests (pytest + opa test)",
+     "scn-tag"
+    ],
+    "main_checks_enforced_for": "everyone"
+   }
+  }
+ ]
+}
\ No newline at end of file
diff --git a/tests/fixtures/scg/retired-mechanism.json b/tests/fixtures/scg/retired-mechanism.json
new file mode 100644
index 00000000..7ce0a0e8
--- /dev/null
+++ b/tests/fixtures/scg/retired-mechanism.json
@@ -0,0 +1,335 @@
+{
+ "schema": "secure-configuration/1",
+ "$comment": "Known-bad: the guide describes a retired mechanism (the old shared app credential); scripts/build-scg.py must refuse it.",
+ "title": "Secure Configuration Guide: samaydlette.com",
+ "version": "2.0.0",
+ "obtain_and_use": [
+  "Obtain: the guide is public. Human-readable: https://samaydlette.com/.well-known/secure-configuration-guide.md. Machine-readable: https://samaydlette.com/.well-known/secure-configuration-guide.json, signed (secure-configuration-guide.bundle; verify with cosign verify-blob against the deploy workflow's identity, as https://samaydlette.com/trust/ shows). No account or request is needed.",
+  "Use: each setting names the account that operates it, the recommended value, why it matters, and the API or CLI call that reads and changes it. Compare a system's live values with `recommended`; the operator's own comparison, run on every deploy, is published at https://samaydlette.com/.well-known/security-settings.json (current values, the result per setting, and the decision record that covers any accepted deviation).",
+  "Change: every setting here is changed only through a reviewed pull request (Terraform for AWS resources, the repository settings for GitHub), never by hand in a console, except the root and owner settings that AWS and GitHub expose only to those accounts, which the operator applies and the deploy then checks."
+ ],
+ "accounts": [
+  {
+   "id": "aws-root",
+   "level": "top-level",
+   "name": "AWS root user",
+   "how_named": "The root user of the single AWS account that holds every production resource. It signs in with the account's email address, which is not published. AWS calls it the root user; this guide calls it aws-root.",
+   "access": "Console only, with MFA, from the operator's own device. No access keys. Used only for the tasks AWS reserves to the root user (account settings, closing the account, restoring IAM administrator access); day-to-day work never uses it.",
+   "configure": "The settings below under aws-root. AWS exposes the root user's own credentials (MFA device, access keys) only to the root user.",
+   "operate": "Sign in only for a root-only task, finish it, and sign out. CloudTrail records every root sign-in and action in the account's management trail.",
+   "decommission": "To retire the system: delete the deployed resources through Terraform, remove the root user's MFA device and any access keys, then close the account from the root user's account settings. Closing the account ends access for every IAM principal in it."
+  },
+  {
+   "id": "github-owner",
+   "level": "top-level",
+   "name": "GitHub repository owner",
+   "how_named": "The operator's personal GitHub account, which owns the repository sam-aydlette/samaydlette.com and so holds every repository and Actions setting, the environments and their reviewers, and the secrets.",
+   "access": "github.com sign-in with two-factor authentication. Local git pushes go to branches, never to main; main changes only through pull requests that pass the required checks.",
+   "configure": "The settings below under github-owner, in the repository's Settings (Branches, Environments, Actions, Code security).",
+   "operate": "Review and merge pull requests; approve each production deploy in the prod environment. The deploy's checks re-read the environment and branch settings every run.",
+   "decommission": "Transfer the repository with GitHub's transfer flow, or archive it. Before either, remove the AWS OIDC trust (infrastructure/bootstrap) so no workflow can assume an AWS role afterwards."
+  },
+  {
+   "id": "aws-operator-user",
+   "level": "privileged",
+   "name": "Operator IAM user",
+   "how_named": "The one IAM user that belongs to the IAM group `operators`. It is the operator's day-to-day administrative identity (bootstrap applies, read-only verification). Its user name is not published; this guide calls it aws-operator-user.",
+   "access": "Signs in with the Basic Auth credential.",
+   "configure": "Membership of the `operators` group gives its permissions; the settings below under aws-operator-user.",
+   "operate": "Used for the bootstrap stack (applied by hand) and read-only checks. Production changes to the main stack go through the reviewed deploy, never this user.",
+   "decommission": "Deactivate and delete its access keys, remove its MFA device and group membership, then delete the user."
+  },
+  {
+   "id": "ci-roles",
+   "level": "privileged",
+   "name": "CI roles (deploy, plan, nightly)",
+   "how_named": "Three IAM roles that GitHub Actions assumes through OIDC: the deploy role (aws_iam_role.deploy), the plan role (aws_iam_role.plan) and the nightly evidence role (aws_iam_role.evidence_nightly), all in infrastructure/bootstrap. No long-lived credential exists for any of them.",
+   "access": "Only through GitHub's OIDC token, and only for the workflow subjects in each role's trust policy.",
+   "configure": "infrastructure/bootstrap (operator-applied, reviewed). The settings below under ci-roles.",
+   "operate": "The deploy role exists only inside an approved prod deploy; the plan role is read-only; the nightly role writes only .well-known/vdr-* objects.",
+   "decommission": "Delete the roles and the OIDC provider from infrastructure/bootstrap and apply."
+  },
+  {
+   "id": "cognito-admin",
+   "level": "privileged",
+   "name": "Silk Reeling user-pool administration",
+   "how_named": "Administration of the Silk Reeling Cognito user pool (aws_cognito_user_pool.silk_reeling): creating users, and the pool's sign-in policy. Only the deploy role (through Terraform) and the operator user can administer it; app users cannot sign themselves up.",
+   "access": "Through Terraform in the reviewed deploy, or the operator user's CLI for creating an app user.",
+   "configure": "infrastructure/cognito.tf. The settings below under cognito-admin.",
+   "operate": "Create an app user with `aws cognito-idp admin-create-user`; the user sets a password meeting the policy and enrolls TOTP MFA at first sign-in.",
+   "decommission": "Delete the app users, then remove the pool from Terraform."
+  }
+ ],
+ "settings": [
+  {
+   "id": "aws-root.mfa-enabled",
+   "account": "aws-root",
+   "operable_by": "aws-root only",
+   "setting": "MFA on the root user",
+   "recommended": true,
+   "implication": "Without MFA, the root user's password alone controls the whole account, including closing it.",
+   "read": "aws iam get-account-summary (SummaryMap.AccountMFAEnabled)",
+   "change": "Root user console: Security credentials, Assign MFA device.",
+   "check": "aws-root-mfa-enabled"
+  },
+  {
+   "id": "aws-root.mfa-phishing-resistant",
+   "account": "aws-root",
+   "operable_by": "aws-root only",
+   "setting": "Root user MFA is phishing-resistant (FIDO2 security key or passkey)",
+   "recommended": true,
+   "implication": "A TOTP code can be relayed by a phishing site in real time; a FIDO2 credential is bound to the AWS sign-in origin and cannot be.",
+   "read": "aws iam list-virtual-mfa-devices --assignment-status Assigned (a root entry means virtual TOTP)",
+   "change": "Root user console: Security credentials, Assign MFA device, Passkey or security key; then remove the virtual device.",
+   "check": "aws-root-mfa-type",
+   "accepted_deviation": "DEC-150"
+  },
+  {
+   "id": "aws-root.access-keys",
+   "account": "aws-root",
+   "operable_by": "aws-root only",
+   "setting": "Root user access keys",
+   "recommended": 0,
+   "implication": "A root access key is an unrestricted, long-lived credential that no IAM policy can limit.",
+   "read": "aws iam get-account-summary (SummaryMap.AccountAccessKeysPresent)",
+   "change": "Root user console: Security credentials, Access keys, Delete.",
+   "check": "aws-root-access-keys"
+  },
+  {
+   "id": "aws-account.password-policy",
+   "account": "aws-root",
+   "operable_by": "aws-root and aws-operator-user",
+   "setting": "Account password policy for IAM users",
+   "recommended": {
+    "MinimumPasswordLength": {
+     "at_least": 14
+    },
+    "RequireSymbols": true,
+    "RequireNumbers": true,
+    "RequireUppercaseCharacters": true,
+    "RequireLowercaseCharacters": true,
+    "PasswordReusePrevention": {
+     "at_least": 24
+    },
+    "MaxPasswordAge": {
+     "at_most": 90
+    }
+   },
+   "implication": "Applies to any IAM user given a console password; weaker values make guessed or reused passwords work.",
+   "read": "aws iam get-account-password-policy",
+   "change": "aws iam update-account-password-policy",
+   "check": "aws-account-password-policy"
+  },
+  {
+   "id": "aws-account.s3-block-public-access",
+   "account": "aws-root",
+   "operable_by": "aws-root and aws-operator-user",
+   "setting": "Account-level S3 Block Public Access",
+   "recommended": {
+    "BlockPublicAcls": true,
+    "IgnorePublicAcls": true,
+    "BlockPublicPolicy": true,
+    "RestrictPublicBuckets": true
+   },
+   "implication": "Stops any bucket in the account being made public by an ACL or bucket policy, whatever its own settings. The site is served through CloudFront's origin access control, never a public bucket.",
+   "read": "aws s3control get-public-access-block --account-id ",
+   "change": "aws s3control put-public-access-block --account-id  --public-access-block-configuration ...",
+   "check": "aws-account-s3-bpa"
+  },
+  {
+   "id": "aws-account.iam-users",
+   "account": "aws-root",
+   "operable_by": "aws-root and aws-operator-user",
+   "setting": "IAM users other than the operator user hold no write permission and no console password",
+   "recommended": 0,
+   "implication": "Every other IAM user is a read-only collector (an AWS read-only or SecurityAudit policy) or has no permissions and no credentials. A second user with write access would be an unreviewed administrative path.",
+   "read": "aws iam list-users; for each: list-groups-for-user, list-attached-user-policies, list-user-policies, get-login-profile",
+   "change": "aws iam detach-user-policy / remove-user-from-group / delete-login-profile (operator user)",
+   "check": "aws-iam-users"
+  },
+  {
+   "id": "github.prod-reviewer",
+   "account": "github-owner",
+   "operable_by": "github-owner only",
+   "setting": "The prod environment requires a reviewer before a deploy",
+   "recommended": {
+    "at_least": 1
+   },
+   "implication": "Without a reviewer, a merged change would apply Terraform to production unattended.",
+   "read": "GET /repos/{owner}/{repo}/environments",
+   "change": "Repository Settings, Environments, prod, Required reviewers (or PUT /repos/{owner}/{repo}/environments/prod)",
+   "check": "github-prod-reviewer"
+  },
+  {
+   "id": "github.nightly-main-only",
+   "account": "github-owner",
+   "operable_by": "github-owner only",
+   "setting": "The evidence-nightly environment deploys only from main",
+   "recommended": [
+    "main"
+   ],
+   "implication": "The nightly role writes published evidence unattended; another branch must not be able to use it.",
+   "read": "GET /repos/{owner}/{repo}/environments/evidence-nightly/deployment-branch-policies",
+   "change": "Repository Settings, Environments, evidence-nightly, Deployment branches",
+   "check": "github-nightly-branches"
+  },
+  {
+   "id": "github.main-required-checks",
+   "account": "github-owner",
+   "operable_by": "github-owner only",
+   "setting": "main requires the four gate checks, for administrators too",
+   "recommended": {
+    "required": [
+     "OPA Compliance Check",
+     "Security Scan",
+     "Unit tests (pytest + opa test)",
+     "scn-tag"
+    ],
+    "enforced_for": "everyone"
+   },
+   "implication": "These checks are the policy, test, scanner and change-classification gates; without them a change could reach main unchecked.",
+   "read": "GET /repos/{owner}/{repo}/branches/main",
+   "change": "Repository Settings, Branches, main (or PUT /repos/{owner}/{repo}/branches/main/protection)",
+   "check": "github-main-checks"
+  },
+  {
+   "id": "github.owner-2fa",
+   "account": "github-owner",
+   "operable_by": "github-owner only",
+   "setting": "Two-factor authentication on the owner account, no classic personal access tokens",
+   "recommended": true,
+   "implication": "The owner account can change every setting above and the workflows that hold AWS trust.",
+   "read": "Not readable by the deploy's token (GitHub exposes a user's 2FA and tokens only to that user); the operator attests it (DEC-151).",
+   "change": "github.com Settings, Password and authentication; Developer settings, Personal access tokens.",
+   "check": "attested",
+   "attested_by": "DEC-151"
+  },
+  {
+   "id": "aws-operator-user.mfa-enabled",
+   "account": "aws-operator-user",
+   "operable_by": "aws-operator-user and aws-root",
+   "setting": "MFA on the operator user",
+   "recommended": true,
+   "implication": "The operator user can administer IAM; its access key alone must not be enough.",
+   "read": "aws iam list-mfa-devices --user-name ",
+   "change": "aws iam enable-mfa-device",
+   "check": "operator-mfa-enabled"
+  },
+  {
+   "id": "aws-operator-user.mfa-phishing-resistant",
+   "account": "aws-operator-user",
+   "operable_by": "aws-operator-user and aws-root",
+   "setting": "Operator user MFA is phishing-resistant (FIDO2 security key or passkey)",
+   "recommended": true,
+   "implication": "As for the root user: a TOTP code can be relayed by a phishing site; a FIDO2 credential cannot.",
+   "read": "aws iam list-virtual-mfa-devices --assignment-status Assigned (an entry for the user means virtual TOTP)",
+   "change": "IAM console: the user's Security credentials, Assign MFA device, Passkey or security key.",
+   "check": "operator-mfa-type",
+   "accepted_deviation": "DEC-150"
+  },
+  {
+   "id": "aws-operator-user.console-password",
+   "account": "aws-operator-user",
+   "operable_by": "aws-operator-user and aws-root",
+   "setting": "No console password on the operator user",
+   "recommended": false,
+   "implication": "The operator works from the CLI; a console password would add a second sign-in path to protect.",
+   "read": "aws iam get-login-profile --user-name  (NoSuchEntity means none)",
+   "change": "aws iam delete-login-profile",
+   "check": "operator-console-password"
+  },
+  {
+   "id": "aws-operator-user.access-keys",
+   "account": "aws-operator-user",
+   "operable_by": "aws-operator-user and aws-root",
+   "setting": "At most one active access key, no older than 90 days",
+   "recommended": {
+    "active": {
+     "at_most": 1
+    },
+    "oldest_age_days": {
+     "at_most": 90
+    }
+   },
+   "implication": "A long-lived key is the operator user's standing credential; rotating it every 90 days bounds the life of a leaked key.",
+   "read": "aws iam list-access-keys --user-name ",
+   "change": "aws iam create-access-key, then update-access-key --status Inactive and delete-access-key for the old one",
+   "check": "operator-access-keys"
+  },
+  {
+   "id": "ci-roles.deploy-trust",
+   "account": "ci-roles",
+   "operable_by": "aws-operator-user (bootstrap apply)",
+   "setting": "The deploy role trusts only this repository's prod environment",
+   "recommended": [
+    "repo:sam-aydlette/samaydlette.com:environment:prod"
+   ],
+   "implication": "The prod environment requires a reviewer, so deploy credentials exist only inside an approved deploy.",
+   "read": "aws iam get-role (AssumeRolePolicyDocument, token.actions.githubusercontent.com:sub)",
+   "change": "infrastructure/bootstrap/main.tf, data.aws_iam_policy_document.trust; operator-applied",
+   "check": "role-trust-deploy"
+  },
+  {
+   "id": "ci-roles.plan-trust",
+   "account": "ci-roles",
+   "operable_by": "aws-operator-user (bootstrap apply)",
+   "setting": "The read-only plan role trusts only this repository's pull requests and main",
+   "recommended": [
+    "repo:sam-aydlette/samaydlette.com:pull_request",
+    "repo:sam-aydlette/samaydlette.com:ref:refs/heads/main"
+   ],
+   "implication": "Pull request runs get read-only credentials, never deploy permissions.",
+   "read": "aws iam get-role (AssumeRolePolicyDocument)",
+   "change": "infrastructure/bootstrap/plan-role.tf; operator-applied",
+   "check": "role-trust-plan"
+  },
+  {
+   "id": "ci-roles.nightly-trust",
+   "account": "ci-roles",
+   "operable_by": "aws-operator-user (bootstrap apply)",
+   "setting": "The nightly role trusts only this repository's evidence-nightly environment",
+   "recommended": [
+    "repo:sam-aydlette/samaydlette.com:environment:evidence-nightly"
+   ],
+   "implication": "The unattended write path stays limited to the one environment that deploys only from main.",
+   "read": "aws iam get-role (AssumeRolePolicyDocument)",
+   "change": "infrastructure/bootstrap/evidence-nightly.tf; operator-applied",
+   "check": "role-trust-nightly"
+  },
+  {
+   "id": "cognito-admin.sign-in-policy",
+   "account": "cognito-admin",
+   "operable_by": "ci-roles (Terraform) and aws-operator-user",
+   "setting": "Silk Reeling user pool: MFA required, admin-created users only, 14-character passwords with every character class",
+   "recommended": {
+    "MfaConfiguration": "ON",
+    "AllowAdminCreateUserOnly": true,
+    "MinimumLength": {
+     "at_least": 14
+    },
+    "RequireUppercase": true,
+    "RequireLowercase": true,
+    "RequireNumbers": true,
+    "RequireSymbols": true
+   },
+   "implication": "App users cannot sign themselves up, and every app user signs in with a strong password and TOTP MFA.",
+   "read": "aws cognito-idp describe-user-pool --user-pool-id ",
+   "change": "infrastructure/cognito.tf (reviewed deploy)",
+   "check": "cognito-pool-policy"
+  }
+ ],
+ "changelog": [
+  {
+   "version": "2.0.0",
+   "date": "2026-11-05",
+   "changes": [
+    "First machine-readable release, replacing the prose guide in docs/policies.",
+    "Root and operator MFA stated as it is: virtual TOTP, an accepted deviation from the phishing-resistant default (DEC-150).",
+    "Deployer access-key rotation removed: CI uses OIDC roles and has no access key.",
+    "The retired Silk Reeling shared credential removed: app users sign in through Cognito with MFA.",
+    "Added the account-level settings, the operator user, the CI roles and the user-pool administration, each with the call that reads and changes it."
+   ],
+   "defaults_sha256": "a21ebfa28dc9e0b8b12a2f0029e163d782d92848c422b85702bec6de65352727"
+  }
+ ]
+}
\ No newline at end of file
diff --git a/tests/fixtures/scg/signal-mapped.json b/tests/fixtures/scg/signal-mapped.json
new file mode 100644
index 00000000..e3708b1c
--- /dev/null
+++ b/tests/fixtures/scg/signal-mapped.json
@@ -0,0 +1,29 @@
+{
+ "signal_id": "fixture",
+ "components": [
+  {
+   "component_id": "x::kms_key",
+   "type": "kms_key"
+  },
+  {
+   "component_id": "x::function",
+   "type": "function"
+  },
+  {
+   "component_id": "x::object_store",
+   "type": "object_store"
+  },
+  {
+   "component_id": "x::npm_package",
+   "type": "npm_package"
+  },
+  {
+   "component_id": "x::cdn_distribution",
+   "type": "cdn_distribution"
+  },
+  {
+   "component_id": "x::external_service",
+   "type": "external_service"
+  }
+ ]
+}
\ No newline at end of file
diff --git a/tests/fixtures/scg/signal-unmapped-type.json b/tests/fixtures/scg/signal-unmapped-type.json
new file mode 100644
index 00000000..150db442
--- /dev/null
+++ b/tests/fixtures/scg/signal-unmapped-type.json
@@ -0,0 +1,14 @@
+{
+ "$comment": "Known-bad: an inventory with a component type no cryptographic module mapping covers (CMU-CSO-CMD).",
+ "signal_id": "fixture",
+ "components": [
+  {
+   "component_id": "aws::kms_key::k",
+   "type": "kms_key"
+  },
+  {
+   "component_id": "aws::vector_db::v",
+   "type": "vector_database"
+  }
+ ]
+}
\ No newline at end of file
diff --git a/tests/fixtures/scg/unreleased-default.json b/tests/fixtures/scg/unreleased-default.json
new file mode 100644
index 00000000..53a6e4a2
--- /dev/null
+++ b/tests/fixtures/scg/unreleased-default.json
@@ -0,0 +1,335 @@
+{
+ "schema": "secure-configuration/1",
+ "$comment": "Known-bad: a recommended default (MaxPasswordAge) weakened without a new version or changelog entry; scripts/build-scg.py must refuse it (SCG-ENH-VRH).",
+ "title": "Secure Configuration Guide: samaydlette.com",
+ "version": "2.0.0",
+ "obtain_and_use": [
+  "Obtain: the guide is public. Human-readable: https://samaydlette.com/.well-known/secure-configuration-guide.md. Machine-readable: https://samaydlette.com/.well-known/secure-configuration-guide.json, signed (secure-configuration-guide.bundle; verify with cosign verify-blob against the deploy workflow's identity, as https://samaydlette.com/trust/ shows). No account or request is needed.",
+  "Use: each setting names the account that operates it, the recommended value, why it matters, and the API or CLI call that reads and changes it. Compare a system's live values with `recommended`; the operator's own comparison, run on every deploy, is published at https://samaydlette.com/.well-known/security-settings.json (current values, the result per setting, and the decision record that covers any accepted deviation).",
+  "Change: every setting here is changed only through a reviewed pull request (Terraform for AWS resources, the repository settings for GitHub), never by hand in a console, except the root and owner settings that AWS and GitHub expose only to those accounts, which the operator applies and the deploy then checks."
+ ],
+ "accounts": [
+  {
+   "id": "aws-root",
+   "level": "top-level",
+   "name": "AWS root user",
+   "how_named": "The root user of the single AWS account that holds every production resource. It signs in with the account's email address, which is not published. AWS calls it the root user; this guide calls it aws-root.",
+   "access": "Console only, with MFA, from the operator's own device. No access keys. Used only for the tasks AWS reserves to the root user (account settings, closing the account, restoring IAM administrator access); day-to-day work never uses it.",
+   "configure": "The settings below under aws-root. AWS exposes the root user's own credentials (MFA device, access keys) only to the root user.",
+   "operate": "Sign in only for a root-only task, finish it, and sign out. CloudTrail records every root sign-in and action in the account's management trail.",
+   "decommission": "To retire the system: delete the deployed resources through Terraform, remove the root user's MFA device and any access keys, then close the account from the root user's account settings. Closing the account ends access for every IAM principal in it."
+  },
+  {
+   "id": "github-owner",
+   "level": "top-level",
+   "name": "GitHub repository owner",
+   "how_named": "The operator's personal GitHub account, which owns the repository sam-aydlette/samaydlette.com and so holds every repository and Actions setting, the environments and their reviewers, and the secrets.",
+   "access": "github.com sign-in with two-factor authentication. Local git pushes go to branches, never to main; main changes only through pull requests that pass the required checks.",
+   "configure": "The settings below under github-owner, in the repository's Settings (Branches, Environments, Actions, Code security).",
+   "operate": "Review and merge pull requests; approve each production deploy in the prod environment. The deploy's checks re-read the environment and branch settings every run.",
+   "decommission": "Transfer the repository with GitHub's transfer flow, or archive it. Before either, remove the AWS OIDC trust (infrastructure/bootstrap) so no workflow can assume an AWS role afterwards."
+  },
+  {
+   "id": "aws-operator-user",
+   "level": "privileged",
+   "name": "Operator IAM user",
+   "how_named": "The one IAM user that belongs to the IAM group `operators`. It is the operator's day-to-day administrative identity (bootstrap applies, read-only verification). Its user name is not published; this guide calls it aws-operator-user.",
+   "access": "AWS CLI with an access key; the user also has an MFA device, and no console password.",
+   "configure": "Membership of the `operators` group gives its permissions; the settings below under aws-operator-user.",
+   "operate": "Used for the bootstrap stack (applied by hand) and read-only checks. Production changes to the main stack go through the reviewed deploy, never this user.",
+   "decommission": "Deactivate and delete its access keys, remove its MFA device and group membership, then delete the user."
+  },
+  {
+   "id": "ci-roles",
+   "level": "privileged",
+   "name": "CI roles (deploy, plan, nightly)",
+   "how_named": "Three IAM roles that GitHub Actions assumes through OIDC: the deploy role (aws_iam_role.deploy), the plan role (aws_iam_role.plan) and the nightly evidence role (aws_iam_role.evidence_nightly), all in infrastructure/bootstrap. No long-lived credential exists for any of them.",
+   "access": "Only through GitHub's OIDC token, and only for the workflow subjects in each role's trust policy.",
+   "configure": "infrastructure/bootstrap (operator-applied, reviewed). The settings below under ci-roles.",
+   "operate": "The deploy role exists only inside an approved prod deploy; the plan role is read-only; the nightly role writes only .well-known/vdr-* objects.",
+   "decommission": "Delete the roles and the OIDC provider from infrastructure/bootstrap and apply."
+  },
+  {
+   "id": "cognito-admin",
+   "level": "privileged",
+   "name": "Silk Reeling user-pool administration",
+   "how_named": "Administration of the Silk Reeling Cognito user pool (aws_cognito_user_pool.silk_reeling): creating users, and the pool's sign-in policy. Only the deploy role (through Terraform) and the operator user can administer it; app users cannot sign themselves up.",
+   "access": "Through Terraform in the reviewed deploy, or the operator user's CLI for creating an app user.",
+   "configure": "infrastructure/cognito.tf. The settings below under cognito-admin.",
+   "operate": "Create an app user with `aws cognito-idp admin-create-user`; the user sets a password meeting the policy and enrolls TOTP MFA at first sign-in.",
+   "decommission": "Delete the app users, then remove the pool from Terraform."
+  }
+ ],
+ "settings": [
+  {
+   "id": "aws-root.mfa-enabled",
+   "account": "aws-root",
+   "operable_by": "aws-root only",
+   "setting": "MFA on the root user",
+   "recommended": true,
+   "implication": "Without MFA, the root user's password alone controls the whole account, including closing it.",
+   "read": "aws iam get-account-summary (SummaryMap.AccountMFAEnabled)",
+   "change": "Root user console: Security credentials, Assign MFA device.",
+   "check": "aws-root-mfa-enabled"
+  },
+  {
+   "id": "aws-root.mfa-phishing-resistant",
+   "account": "aws-root",
+   "operable_by": "aws-root only",
+   "setting": "Root user MFA is phishing-resistant (FIDO2 security key or passkey)",
+   "recommended": true,
+   "implication": "A TOTP code can be relayed by a phishing site in real time; a FIDO2 credential is bound to the AWS sign-in origin and cannot be.",
+   "read": "aws iam list-virtual-mfa-devices --assignment-status Assigned (a root entry means virtual TOTP)",
+   "change": "Root user console: Security credentials, Assign MFA device, Passkey or security key; then remove the virtual device.",
+   "check": "aws-root-mfa-type",
+   "accepted_deviation": "DEC-150"
+  },
+  {
+   "id": "aws-root.access-keys",
+   "account": "aws-root",
+   "operable_by": "aws-root only",
+   "setting": "Root user access keys",
+   "recommended": 0,
+   "implication": "A root access key is an unrestricted, long-lived credential that no IAM policy can limit.",
+   "read": "aws iam get-account-summary (SummaryMap.AccountAccessKeysPresent)",
+   "change": "Root user console: Security credentials, Access keys, Delete.",
+   "check": "aws-root-access-keys"
+  },
+  {
+   "id": "aws-account.password-policy",
+   "account": "aws-root",
+   "operable_by": "aws-root and aws-operator-user",
+   "setting": "Account password policy for IAM users",
+   "recommended": {
+    "MinimumPasswordLength": {
+     "at_least": 14
+    },
+    "RequireSymbols": true,
+    "RequireNumbers": true,
+    "RequireUppercaseCharacters": true,
+    "RequireLowercaseCharacters": true,
+    "PasswordReusePrevention": {
+     "at_least": 24
+    },
+    "MaxPasswordAge": {
+     "at_most": 365
+    }
+   },
+   "implication": "Applies to any IAM user given a console password; weaker values make guessed or reused passwords work.",
+   "read": "aws iam get-account-password-policy",
+   "change": "aws iam update-account-password-policy",
+   "check": "aws-account-password-policy"
+  },
+  {
+   "id": "aws-account.s3-block-public-access",
+   "account": "aws-root",
+   "operable_by": "aws-root and aws-operator-user",
+   "setting": "Account-level S3 Block Public Access",
+   "recommended": {
+    "BlockPublicAcls": true,
+    "IgnorePublicAcls": true,
+    "BlockPublicPolicy": true,
+    "RestrictPublicBuckets": true
+   },
+   "implication": "Stops any bucket in the account being made public by an ACL or bucket policy, whatever its own settings. The site is served through CloudFront's origin access control, never a public bucket.",
+   "read": "aws s3control get-public-access-block --account-id ",
+   "change": "aws s3control put-public-access-block --account-id  --public-access-block-configuration ...",
+   "check": "aws-account-s3-bpa"
+  },
+  {
+   "id": "aws-account.iam-users",
+   "account": "aws-root",
+   "operable_by": "aws-root and aws-operator-user",
+   "setting": "IAM users other than the operator user hold no write permission and no console password",
+   "recommended": 0,
+   "implication": "Every other IAM user is a read-only collector (an AWS read-only or SecurityAudit policy) or has no permissions and no credentials. A second user with write access would be an unreviewed administrative path.",
+   "read": "aws iam list-users; for each: list-groups-for-user, list-attached-user-policies, list-user-policies, get-login-profile",
+   "change": "aws iam detach-user-policy / remove-user-from-group / delete-login-profile (operator user)",
+   "check": "aws-iam-users"
+  },
+  {
+   "id": "github.prod-reviewer",
+   "account": "github-owner",
+   "operable_by": "github-owner only",
+   "setting": "The prod environment requires a reviewer before a deploy",
+   "recommended": {
+    "at_least": 1
+   },
+   "implication": "Without a reviewer, a merged change would apply Terraform to production unattended.",
+   "read": "GET /repos/{owner}/{repo}/environments",
+   "change": "Repository Settings, Environments, prod, Required reviewers (or PUT /repos/{owner}/{repo}/environments/prod)",
+   "check": "github-prod-reviewer"
+  },
+  {
+   "id": "github.nightly-main-only",
+   "account": "github-owner",
+   "operable_by": "github-owner only",
+   "setting": "The evidence-nightly environment deploys only from main",
+   "recommended": [
+    "main"
+   ],
+   "implication": "The nightly role writes published evidence unattended; another branch must not be able to use it.",
+   "read": "GET /repos/{owner}/{repo}/environments/evidence-nightly/deployment-branch-policies",
+   "change": "Repository Settings, Environments, evidence-nightly, Deployment branches",
+   "check": "github-nightly-branches"
+  },
+  {
+   "id": "github.main-required-checks",
+   "account": "github-owner",
+   "operable_by": "github-owner only",
+   "setting": "main requires the four gate checks, for administrators too",
+   "recommended": {
+    "required": [
+     "OPA Compliance Check",
+     "Security Scan",
+     "Unit tests (pytest + opa test)",
+     "scn-tag"
+    ],
+    "enforced_for": "everyone"
+   },
+   "implication": "These checks are the policy, test, scanner and change-classification gates; without them a change could reach main unchecked.",
+   "read": "GET /repos/{owner}/{repo}/branches/main",
+   "change": "Repository Settings, Branches, main (or PUT /repos/{owner}/{repo}/branches/main/protection)",
+   "check": "github-main-checks"
+  },
+  {
+   "id": "github.owner-2fa",
+   "account": "github-owner",
+   "operable_by": "github-owner only",
+   "setting": "Two-factor authentication on the owner account, no classic personal access tokens",
+   "recommended": true,
+   "implication": "The owner account can change every setting above and the workflows that hold AWS trust.",
+   "read": "Not readable by the deploy's token (GitHub exposes a user's 2FA and tokens only to that user); the operator attests it (DEC-151).",
+   "change": "github.com Settings, Password and authentication; Developer settings, Personal access tokens.",
+   "check": "attested",
+   "attested_by": "DEC-151"
+  },
+  {
+   "id": "aws-operator-user.mfa-enabled",
+   "account": "aws-operator-user",
+   "operable_by": "aws-operator-user and aws-root",
+   "setting": "MFA on the operator user",
+   "recommended": true,
+   "implication": "The operator user can administer IAM; its access key alone must not be enough.",
+   "read": "aws iam list-mfa-devices --user-name ",
+   "change": "aws iam enable-mfa-device",
+   "check": "operator-mfa-enabled"
+  },
+  {
+   "id": "aws-operator-user.mfa-phishing-resistant",
+   "account": "aws-operator-user",
+   "operable_by": "aws-operator-user and aws-root",
+   "setting": "Operator user MFA is phishing-resistant (FIDO2 security key or passkey)",
+   "recommended": true,
+   "implication": "As for the root user: a TOTP code can be relayed by a phishing site; a FIDO2 credential cannot.",
+   "read": "aws iam list-virtual-mfa-devices --assignment-status Assigned (an entry for the user means virtual TOTP)",
+   "change": "IAM console: the user's Security credentials, Assign MFA device, Passkey or security key.",
+   "check": "operator-mfa-type",
+   "accepted_deviation": "DEC-150"
+  },
+  {
+   "id": "aws-operator-user.console-password",
+   "account": "aws-operator-user",
+   "operable_by": "aws-operator-user and aws-root",
+   "setting": "No console password on the operator user",
+   "recommended": false,
+   "implication": "The operator works from the CLI; a console password would add a second sign-in path to protect.",
+   "read": "aws iam get-login-profile --user-name  (NoSuchEntity means none)",
+   "change": "aws iam delete-login-profile",
+   "check": "operator-console-password"
+  },
+  {
+   "id": "aws-operator-user.access-keys",
+   "account": "aws-operator-user",
+   "operable_by": "aws-operator-user and aws-root",
+   "setting": "At most one active access key, no older than 90 days",
+   "recommended": {
+    "active": {
+     "at_most": 1
+    },
+    "oldest_age_days": {
+     "at_most": 90
+    }
+   },
+   "implication": "A long-lived key is the operator user's standing credential; rotating it every 90 days bounds the life of a leaked key.",
+   "read": "aws iam list-access-keys --user-name ",
+   "change": "aws iam create-access-key, then update-access-key --status Inactive and delete-access-key for the old one",
+   "check": "operator-access-keys"
+  },
+  {
+   "id": "ci-roles.deploy-trust",
+   "account": "ci-roles",
+   "operable_by": "aws-operator-user (bootstrap apply)",
+   "setting": "The deploy role trusts only this repository's prod environment",
+   "recommended": [
+    "repo:sam-aydlette/samaydlette.com:environment:prod"
+   ],
+   "implication": "The prod environment requires a reviewer, so deploy credentials exist only inside an approved deploy.",
+   "read": "aws iam get-role (AssumeRolePolicyDocument, token.actions.githubusercontent.com:sub)",
+   "change": "infrastructure/bootstrap/main.tf, data.aws_iam_policy_document.trust; operator-applied",
+   "check": "role-trust-deploy"
+  },
+  {
+   "id": "ci-roles.plan-trust",
+   "account": "ci-roles",
+   "operable_by": "aws-operator-user (bootstrap apply)",
+   "setting": "The read-only plan role trusts only this repository's pull requests and main",
+   "recommended": [
+    "repo:sam-aydlette/samaydlette.com:pull_request",
+    "repo:sam-aydlette/samaydlette.com:ref:refs/heads/main"
+   ],
+   "implication": "Pull request runs get read-only credentials, never deploy permissions.",
+   "read": "aws iam get-role (AssumeRolePolicyDocument)",
+   "change": "infrastructure/bootstrap/plan-role.tf; operator-applied",
+   "check": "role-trust-plan"
+  },
+  {
+   "id": "ci-roles.nightly-trust",
+   "account": "ci-roles",
+   "operable_by": "aws-operator-user (bootstrap apply)",
+   "setting": "The nightly role trusts only this repository's evidence-nightly environment",
+   "recommended": [
+    "repo:sam-aydlette/samaydlette.com:environment:evidence-nightly"
+   ],
+   "implication": "The unattended write path stays limited to the one environment that deploys only from main.",
+   "read": "aws iam get-role (AssumeRolePolicyDocument)",
+   "change": "infrastructure/bootstrap/evidence-nightly.tf; operator-applied",
+   "check": "role-trust-nightly"
+  },
+  {
+   "id": "cognito-admin.sign-in-policy",
+   "account": "cognito-admin",
+   "operable_by": "ci-roles (Terraform) and aws-operator-user",
+   "setting": "Silk Reeling user pool: MFA required, admin-created users only, 14-character passwords with every character class",
+   "recommended": {
+    "MfaConfiguration": "ON",
+    "AllowAdminCreateUserOnly": true,
+    "MinimumLength": {
+     "at_least": 14
+    },
+    "RequireUppercase": true,
+    "RequireLowercase": true,
+    "RequireNumbers": true,
+    "RequireSymbols": true
+   },
+   "implication": "App users cannot sign themselves up, and every app user signs in with a strong password and TOTP MFA.",
+   "read": "aws cognito-idp describe-user-pool --user-pool-id ",
+   "change": "infrastructure/cognito.tf (reviewed deploy)",
+   "check": "cognito-pool-policy"
+  }
+ ],
+ "changelog": [
+  {
+   "version": "2.0.0",
+   "date": "2026-11-05",
+   "changes": [
+    "First machine-readable release, replacing the prose guide in docs/policies.",
+    "Root and operator MFA stated as it is: virtual TOTP, an accepted deviation from the phishing-resistant default (DEC-150).",
+    "Deployer access-key rotation removed: CI uses OIDC roles and has no access key.",
+    "The retired Silk Reeling shared credential removed: app users sign in through Cognito with MFA.",
+    "Added the account-level settings, the operator user, the CI roles and the user-pool administration, each with the call that reads and changes it."
+   ],
+   "defaults_sha256": "a21ebfa28dc9e0b8b12a2f0029e163d782d92848c422b85702bec6de65352727"
+  }
+ ]
+}
\ No newline at end of file
diff --git a/tests/fixtures/scheduled-reviews/cloudtrail-expected.json b/tests/fixtures/scheduled-reviews/cloudtrail-expected.json
new file mode 100644
index 00000000..ecab7b5d
--- /dev/null
+++ b/tests/fixtures/scheduled-reviews/cloudtrail-expected.json
@@ -0,0 +1,12 @@
+[
+ {"EventName": "UpdateDistribution", "EventSource": "cloudfront.amazonaws.com", "EventTime": "2026-11-06T03:00:00Z", "region": "us-east-1",
+  "userIdentity": {"type": "AssumedRole", "sessionContext": {"sessionIssuer": {"userName": "github-actions-deploy-oidc"}}}},
+ {"EventName": "PutBucketPolicy", "EventSource": "s3.amazonaws.com", "EventTime": "2026-11-06T03:01:00Z", "region": "us-east-2",
+  "userIdentity": {"type": "AssumedRole", "sessionContext": {"sessionIssuer": {"userName": "github-actions-deploy-oidc"}}}},
+ {"EventName": "Encrypt", "EventSource": "kms.amazonaws.com", "EventTime": "2026-11-06T03:02:00Z", "region": "us-east-2",
+  "userIdentity": {"type": "AWSService"}},
+ {"EventName": "InitiateAuth", "EventSource": "cognito-idp.amazonaws.com", "EventTime": "2026-11-06T03:03:00Z", "region": "us-east-2",
+  "userIdentity": {"type": "Unknown"}},
+ {"EventName": "PutObject", "EventSource": "s3.amazonaws.com", "EventTime": "2026-11-06T03:04:00Z", "region": "us-east-2",
+  "userIdentity": {"type": "IAMUser", "userName": "not-watched"}}
+]
diff --git a/tests/fixtures/scheduled-reviews/cloudtrail-unknown-principal.json b/tests/fixtures/scheduled-reviews/cloudtrail-unknown-principal.json
new file mode 100644
index 00000000..bf887a35
--- /dev/null
+++ b/tests/fixtures/scheduled-reviews/cloudtrail-unknown-principal.json
@@ -0,0 +1,8 @@
+[
+ {"$comment": "Known-bad: a role that is not one of the CI roles changes a bucket policy (a process finding, not reportable).",
+  "EventName": "PutBucketPolicy", "EventSource": "s3.amazonaws.com", "EventTime": "2026-11-06T04:00:00Z", "region": "us-east-2",
+  "userIdentity": {"type": "AssumedRole", "sessionContext": {"sessionIssuer": {"userName": "somebody-elses-role"}}}},
+ {"$comment": "Known-bad: an IAM user creates a long-lived access key (evaluated as a possible reportable incident).",
+  "EventName": "CreateAccessKey", "EventSource": "iam.amazonaws.com", "EventTime": "2026-11-06T04:01:00Z", "region": "us-east-1",
+  "userIdentity": {"type": "IAMUser", "userName": "a-real-looking-user"}}
+]
diff --git a/tests/fixtures/scheduled-reviews/costs-no-source.json b/tests/fixtures/scheduled-reviews/costs-no-source.json
new file mode 100644
index 00000000..d5945ffd
--- /dev/null
+++ b/tests/fixtures/scheduled-reviews/costs-no-source.json
@@ -0,0 +1,4 @@
+{"$comment": "Known-bad: a cost line whose source is neither a repository path nor external:.",
+ "schema": "recurring-costs/1", "status": "AI-drafted estimate; operator to correct",
+ "lines": [{"id": "COST-MYSTERY", "item": "Something that bills", "source": "somewhere/that-does-not-exist.tf",
+            "estimate_usd_per_year": 1, "estimate": "about $1", "basis": "a guess"}]}
diff --git a/tests/fixtures/scheduled-reviews/costs-number-not-unknown.json b/tests/fixtures/scheduled-reviews/costs-number-not-unknown.json
new file mode 100644
index 00000000..3ce09fd0
--- /dev/null
+++ b/tests/fixtures/scheduled-reviews/costs-number-not-unknown.json
@@ -0,0 +1,4 @@
+{"$comment": "Known-bad: a line with no figure that does not say 'unknown'.",
+ "schema": "recurring-costs/1", "status": "AI-drafted estimate; operator to correct",
+ "lines": [{"id": "COST-VAGUE", "item": "Something that bills", "source": "external:a vendor",
+            "estimate_usd_per_year": null, "estimate": "cheap", "basis": "a feeling"}]}
diff --git a/tests/fixtures/scheduled-reviews/github-clean.json b/tests/fixtures/scheduled-reviews/github-clean.json
new file mode 100644
index 00000000..06eb8489
--- /dev/null
+++ b/tests/fixtures/scheduled-reviews/github-clean.json
@@ -0,0 +1,2 @@
+{"commits": [{"at": "2026-11-06T02:00:00Z", "pr": 519, "workflows": false}],
+ "settings": [{"kind": "ruleset", "name": "main", "updated_at": "2026-01-01T00:00:00Z"}]}
diff --git a/tests/fixtures/scheduled-reviews/github-direct-push.json b/tests/fixtures/scheduled-reviews/github-direct-push.json
new file mode 100644
index 00000000..23994406
--- /dev/null
+++ b/tests/fixtures/scheduled-reviews/github-direct-push.json
@@ -0,0 +1,3 @@
+{"$comment": "Known-bad: a workflow change pushed to main with no merged pull request, and an environment changed in the window.",
+ "commits": [{"at": "2026-11-06T02:00:00Z", "pr": null, "workflows": true}],
+ "settings": [{"kind": "environment", "name": "production", "updated_at": "2026-11-06T01:00:00Z"}]}
diff --git a/tests/fixtures/scheduled-reviews/recovery-plan-gap.md b/tests/fixtures/scheduled-reviews/recovery-plan-gap.md
new file mode 100644
index 00000000..00516f70
--- /dev/null
+++ b/tests/fixtures/scheduled-reviews/recovery-plan-gap.md
@@ -0,0 +1,9 @@
+# Recovery plan (known-bad fixture)
+
+The tabletop must fail: one scenario has no stated recovery, and there is no
+Recovery procedure section.
+
+In-scope loss scenarios:
+- Site content deleted — restore from the deployed commit
+- State table lost — point-in-time recovery
+- The intern unplugs the cloud
diff --git a/tests/fixtures/scn/bad/adaptive-no-record.md b/tests/fixtures/scn/bad/adaptive-no-record.md
new file mode 100644
index 00000000..0d71319a
--- /dev/null
+++ b/tests/fixtures/scn/bad/adaptive-no-record.md
@@ -0,0 +1,2 @@
+SCN-Type: adaptive
+SCN-Rationale: adds a new internal component (a CloudWatch alarm) with no new ingress or egress.
diff --git a/tests/fixtures/scn/bad/class-change.md b/tests/fixtures/scn/bad/class-change.md
new file mode 100644
index 00000000..894d2a21
--- /dev/null
+++ b/tests/fixtures/scn/bad/class-change.md
@@ -0,0 +1,2 @@
+SCN-Type: class-change
+SCN-Rationale: the offering would start holding federal customer data, which changes its certification class.
diff --git a/tests/fixtures/scn/bad/index-previous-with-dropped.json b/tests/fixtures/scn/bad/index-previous-with-dropped.json
new file mode 100644
index 00000000..813ae5c2
--- /dev/null
+++ b/tests/fixtures/scn/bad/index-previous-with-dropped.json
@@ -0,0 +1,17 @@
+{
+  "$comment": "Known-bad previous index: holds SCN-2025-001, which the current register does not, so a build over it would drop a published notification (SCN-CSO-HIS).",
+  "notifications": [
+    {
+      "scnId": "SCN-2025-001",
+      "notices": [
+        {
+          "stage": "after-finish",
+          "rule": "SCN-ADP-NTF",
+          "deadline": "2025-12-01",
+          "publishedOn": "2025-11-20",
+          "onTime": true
+        }
+      ]
+    }
+  ]
+}
\ No newline at end of file
diff --git a/tests/fixtures/scn/bad/log-rewritten.json b/tests/fixtures/scn/bad/log-rewritten.json
new file mode 100644
index 00000000..f6de6894
--- /dev/null
+++ b/tests/fixtures/scn/bad/log-rewritten.json
@@ -0,0 +1,36 @@
+{
+  "genesis_commit": "1111111111111111111111111111111111111111",
+  "entries": [
+    {
+      "commit": "1111111111111111111111111111111111111111",
+      "merged_on": "2026-11-06",
+      "pull_request": 501,
+      "evaluator": "sam-aydlette",
+      "scn_type": "not-significant",
+      "rationale": "compliance-process change; no component, boundary or access change.",
+      "scn_record": null,
+      "problem": null
+    },
+    {
+      "commit": "2222222222222222222222222222222222222222",
+      "merged_on": "2026-11-09",
+      "pull_request": 502,
+      "evaluator": "sam-aydlette",
+      "scn_type": "routine-recurring",
+      "rationale": "adds a new internal alarm with no new ingress or egress.",
+      "scn_record": null,
+      "problem": null
+    },
+    {
+      "commit": "3333333333333333333333333333333333333333",
+      "merged_on": "2026-11-10",
+      "pull_request": 503,
+      "evaluator": "sam-aydlette",
+      "scn_type": "not-significant",
+      "rationale": "content-only change to a public page.",
+      "scn_record": null,
+      "problem": null
+    }
+  ],
+  "$comment": "Known-bad: rewrites entry 1 of log-previous.json (adaptive -> routine-recurring). The append-only check must fail."
+}
\ No newline at end of file
diff --git a/tests/fixtures/scn/bad/log-truncated.json b/tests/fixtures/scn/bad/log-truncated.json
new file mode 100644
index 00000000..2e053028
--- /dev/null
+++ b/tests/fixtures/scn/bad/log-truncated.json
@@ -0,0 +1,16 @@
+{
+  "genesis_commit": "1111111111111111111111111111111111111111",
+  "entries": [
+    {
+      "commit": "1111111111111111111111111111111111111111",
+      "merged_on": "2026-11-06",
+      "pull_request": 501,
+      "evaluator": "sam-aydlette",
+      "scn_type": "not-significant",
+      "rationale": "compliance-process change; no component, boundary or access change.",
+      "scn_record": null,
+      "problem": null
+    }
+  ],
+  "$comment": "Known-bad: drops entry 1 of log-previous.json. The append-only check must fail."
+}
\ No newline at end of file
diff --git a/tests/fixtures/scn/bad/missing-rationale.md b/tests/fixtures/scn/bad/missing-rationale.md
new file mode 100644
index 00000000..4ebdb1fa
--- /dev/null
+++ b/tests/fixtures/scn/bad/missing-rationale.md
@@ -0,0 +1,4 @@
+## Changed
+Bumps a dependency.
+
+SCN-Type: routine-recurring
diff --git a/tests/fixtures/scn/bad/missing-type.md b/tests/fixtures/scn/bad/missing-type.md
new file mode 100644
index 00000000..c996bb61
--- /dev/null
+++ b/tests/fixtures/scn/bad/missing-type.md
@@ -0,0 +1,4 @@
+## Changed
+Bumps a dependency.
+
+SCN-Rationale: dependency version bump with no behaviour change.
diff --git a/tests/fixtures/scn/bad/placeholder-rationale.md b/tests/fixtures/scn/bad/placeholder-rationale.md
new file mode 100644
index 00000000..9fa83cc9
--- /dev/null
+++ b/tests/fixtures/scn/bad/placeholder-rationale.md
@@ -0,0 +1,2 @@
+SCN-Type: routine-recurring
+SCN-Rationale: 
diff --git a/tests/fixtures/scn/bad/register-adaptive-no-risks.csv b/tests/fixtures/scn/bad/register-adaptive-no-risks.csv
new file mode 100644
index 00000000..c7150d7d
--- /dev/null
+++ b/tests/fixtures/scn/bad/register-adaptive-no-risks.csv
@@ -0,0 +1,2 @@
+scn_id,fedramp_id,assessor_name,related_vulnerability,scn_type,categorization_rationale,short_description,reason_for_change,customer_impact,plan_and_timeline,sia_reference,new_risks_summary,approver_name,approver_title,status,date_initiated,date_started,date_finished,verified_on,emergency,evaluation_prs,plan_final,tpr_human_validation,tpr_assessor_or_reason,sar_reference,docs_to_update,docs_updated_on,docs_update_not_required
+SCN-2026-103,,N/A (sole-operator self-attestation; no 3PAO engaged),None (proactive feature addition),adaptive,"Net-new service component with new public ingress and new external egress; no FedRAMP Certification class change and no federal customer data introduced, so not transformative and not a class change; not regular/routine maintenance, so not routine-recurring. Resolves to Adaptive per SCN-CSO-EVA. Sits at the upper edge of Adaptive due to the new non-FedRAMP-authorized external interconnection (Anthropic); the absence of federal customer data is what keeps it out of Transformative.","Adds the gated ""Silk Reeling Mirror"" app: a public, HTTP-Basic-Auth-gated API Gateway HTTP API -> Python 3.13 ZIP Lambda serving a browser SPA; the Lambda calls the Anthropic API to generate movement-feedback text.",New self-service capability addition to the site.,New customer/operator-responsibility control: operator-set HTTP Basic Auth credential (POAM-021). SAML/IdP federation is the recommended upgrade. No change to existing customers' configuration responsibilities.,"Gated deploy (create_silk_reeling=true) -> OPA + Checkov + tfsec gate -> Syft/Grype SCA over the built artifact -> VDR report regenerated -> post-implementation secure-configuration verification (Adaptive requirement) -> KSI signal + OSCAL SSP re-emitted. Controls/KSIs to re-verify: RA-5/VDR-*, SA-9/CA-3, SC-7, AC-3/IA-2, AU-2/AU-3, SC-12/SC-28.",docs/scn/SCN-2026-001-silk-reeling.md,,Sam Aydlette,System Owner / Authorizing Operator,Implemented — live in production (first prod deploy 2026-06-03 via PR #82); post-implementation verification COMPLETE 2026-06-08 at prod commit 354da59 (pass: KEV 0 / blocking 0; SSP data-flow + interconnection rendered; deployed Python/JS deps CVE-free; CM-8 inventory complete),2026-06-03,,2026-06-06,2026-06-08,no,#82,,,,,,,
diff --git a/tests/fixtures/scn/bad/register-dates-out-of-order.csv b/tests/fixtures/scn/bad/register-dates-out-of-order.csv
new file mode 100644
index 00000000..07948b55
--- /dev/null
+++ b/tests/fixtures/scn/bad/register-dates-out-of-order.csv
@@ -0,0 +1,2 @@
+scn_id,fedramp_id,assessor_name,related_vulnerability,scn_type,categorization_rationale,short_description,reason_for_change,customer_impact,plan_and_timeline,sia_reference,new_risks_summary,approver_name,approver_title,status,date_initiated,date_started,date_finished,verified_on,emergency,evaluation_prs,plan_final,tpr_human_validation,tpr_assessor_or_reason,sar_reference,docs_to_update,docs_updated_on,docs_update_not_required
+SCN-2026-104,,N/A (sole-operator self-attestation; no 3PAO engaged),None (proactive feature addition),adaptive,"Net-new service component with new public ingress and new external egress; no FedRAMP Certification class change and no federal customer data introduced, so not transformative and not a class change; not regular/routine maintenance, so not routine-recurring. Resolves to Adaptive per SCN-CSO-EVA. Sits at the upper edge of Adaptive due to the new non-FedRAMP-authorized external interconnection (Anthropic); the absence of federal customer data is what keeps it out of Transformative.","Adds the gated ""Silk Reeling Mirror"" app: a public, HTTP-Basic-Auth-gated API Gateway HTTP API -> Python 3.13 ZIP Lambda serving a browser SPA; the Lambda calls the Anthropic API to generate movement-feedback text.",New self-service capability addition to the site.,New customer/operator-responsibility control: operator-set HTTP Basic Auth credential (POAM-021). SAML/IdP federation is the recommended upgrade. No change to existing customers' configuration responsibilities.,"Gated deploy (create_silk_reeling=true) -> OPA + Checkov + tfsec gate -> Syft/Grype SCA over the built artifact -> VDR report regenerated -> post-implementation secure-configuration verification (Adaptive requirement) -> KSI signal + OSCAL SSP re-emitted. Controls/KSIs to re-verify: RA-5/VDR-*, SA-9/CA-3, SC-7, AC-3/IA-2, AU-2/AU-3, SC-12/SC-28.",docs/scn/SCN-2026-001-silk-reeling.md,"POAM-019..024 (all risk-accepted, Low residual) plus the new-ecosystem SCA blind-spot, remediated by adding Syft/Grype SCA of the built Lambda+SPA artifact to CI feeding the VDR aggregator (RA-5/VDR-CSO-DET).",Sam Aydlette,System Owner / Authorizing Operator,Implemented — live in production (first prod deploy 2026-06-03 via PR #82); post-implementation verification COMPLETE 2026-06-08 at prod commit 354da59 (pass: KEV 0 / blocking 0; SSP data-flow + interconnection rendered; deployed Python/JS deps CVE-free; CM-8 inventory complete),2026-06-03,,2026-06-01,2026-06-08,no,#82,,,,,,,
diff --git a/tests/fixtures/scn/bad/register-on-deploy-with-finish-date.csv b/tests/fixtures/scn/bad/register-on-deploy-with-finish-date.csv
new file mode 100644
index 00000000..3046877b
--- /dev/null
+++ b/tests/fixtures/scn/bad/register-on-deploy-with-finish-date.csv
@@ -0,0 +1,2 @@
+scn_id,fedramp_id,assessor_name,related_vulnerability,scn_type,categorization_rationale,short_description,reason_for_change,customer_impact,plan_and_timeline,sia_reference,new_risks_summary,approver_name,approver_title,status,date_initiated,date_started,date_finished,verified_on,emergency,evaluation_prs,plan_final,tpr_human_validation,tpr_assessor_or_reason,sar_reference,docs_to_update,docs_updated_on,docs_update_not_required
+SCN-2026-104,,N/A (sole-operator self-attestation; no 3PAO engaged),None (proactive feature addition),adaptive,"Net-new service component with new public ingress and new external egress; no FedRAMP Certification class change and no federal customer data introduced, so not transformative and not a class change; not regular/routine maintenance, so not routine-recurring. Resolves to Adaptive per SCN-CSO-EVA. Sits at the upper edge of Adaptive due to the new non-FedRAMP-authorized external interconnection (Anthropic); the absence of federal customer data is what keeps it out of Transformative.","Adds the gated ""Silk Reeling Mirror"" app: a public, HTTP-Basic-Auth-gated API Gateway HTTP API -> Python 3.13 ZIP Lambda serving a browser SPA; the Lambda calls the Anthropic API to generate movement-feedback text.",New self-service capability addition to the site.,New customer/operator-responsibility control: operator-set HTTP Basic Auth credential (POAM-021). SAML/IdP federation is the recommended upgrade. No change to existing customers' configuration responsibilities.,"Gated deploy (create_silk_reeling=true) -> OPA + Checkov + tfsec gate -> Syft/Grype SCA over the built artifact -> VDR report regenerated -> post-implementation secure-configuration verification (Adaptive requirement) -> KSI signal + OSCAL SSP re-emitted. Controls/KSIs to re-verify: RA-5/VDR-*, SA-9/CA-3, SC-7, AC-3/IA-2, AU-2/AU-3, SC-12/SC-28.",docs/scn/SCN-2026-001-silk-reeling.md,One new read-only grant; nothing else.,Sam Aydlette,System Owner / Authorizing Operator,on-deploy,2026-06-03,,2026-06-10,,no,#82,,,,,,,
diff --git a/tests/fixtures/scn/bad/register-routine.csv b/tests/fixtures/scn/bad/register-routine.csv
new file mode 100644
index 00000000..ec1175ff
--- /dev/null
+++ b/tests/fixtures/scn/bad/register-routine.csv
@@ -0,0 +1,2 @@
+scn_id,fedramp_id,assessor_name,related_vulnerability,scn_type,categorization_rationale,short_description,reason_for_change,customer_impact,plan_and_timeline,sia_reference,new_risks_summary,approver_name,approver_title,status,date_initiated,date_started,date_finished,verified_on,emergency,evaluation_prs,plan_final,tpr_human_validation,tpr_assessor_or_reason,sar_reference,docs_to_update,docs_updated_on,docs_update_not_required
+SCN-2026-101,,N/A (sole-operator self-attestation; no 3PAO engaged),None (proactive feature addition),routine-recurring,"Net-new service component with new public ingress and new external egress; no FedRAMP Certification class change and no federal customer data introduced, so not transformative and not a class change; not regular/routine maintenance, so not routine-recurring. Resolves to Adaptive per SCN-CSO-EVA. Sits at the upper edge of Adaptive due to the new non-FedRAMP-authorized external interconnection (Anthropic); the absence of federal customer data is what keeps it out of Transformative.","Adds the gated ""Silk Reeling Mirror"" app: a public, HTTP-Basic-Auth-gated API Gateway HTTP API -> Python 3.13 ZIP Lambda serving a browser SPA; the Lambda calls the Anthropic API to generate movement-feedback text.",New self-service capability addition to the site.,New customer/operator-responsibility control: operator-set HTTP Basic Auth credential (POAM-021). SAML/IdP federation is the recommended upgrade. No change to existing customers' configuration responsibilities.,"Gated deploy (create_silk_reeling=true) -> OPA + Checkov + tfsec gate -> Syft/Grype SCA over the built artifact -> VDR report regenerated -> post-implementation secure-configuration verification (Adaptive requirement) -> KSI signal + OSCAL SSP re-emitted. Controls/KSIs to re-verify: RA-5/VDR-*, SA-9/CA-3, SC-7, AC-3/IA-2, AU-2/AU-3, SC-12/SC-28.",docs/scn/SCN-2026-001-silk-reeling.md,"POAM-019..024 (all risk-accepted, Low residual) plus the new-ecosystem SCA blind-spot, remediated by adding Syft/Grype SCA of the built Lambda+SPA artifact to CI feeding the VDR aggregator (RA-5/VDR-CSO-DET).",Sam Aydlette,System Owner / Authorizing Operator,Implemented — live in production (first prod deploy 2026-06-03 via PR #82); post-implementation verification COMPLETE 2026-06-08 at prod commit 354da59 (pass: KEV 0 / blocking 0; SSP data-flow + interconnection rendered; deployed Python/JS deps CVE-free; CM-8 inventory complete),2026-06-03,,2026-06-06,2026-06-08,no,#82,,,,,,,
diff --git a/tests/fixtures/scn/bad/register-transformative-incomplete.csv b/tests/fixtures/scn/bad/register-transformative-incomplete.csv
new file mode 100644
index 00000000..41a48d43
--- /dev/null
+++ b/tests/fixtures/scn/bad/register-transformative-incomplete.csv
@@ -0,0 +1,2 @@
+scn_id,fedramp_id,assessor_name,related_vulnerability,scn_type,categorization_rationale,short_description,reason_for_change,customer_impact,plan_and_timeline,sia_reference,new_risks_summary,approver_name,approver_title,status,date_initiated,date_started,date_finished,verified_on,emergency,evaluation_prs,plan_final,tpr_human_validation,tpr_assessor_or_reason,sar_reference,docs_to_update,docs_updated_on,docs_update_not_required
+SCN-2026-102,,N/A (sole-operator self-attestation; no 3PAO engaged),None (proactive feature addition),transformative,"Net-new service component with new public ingress and new external egress; no FedRAMP Certification class change and no federal customer data introduced, so not transformative and not a class change; not regular/routine maintenance, so not routine-recurring. Resolves to Adaptive per SCN-CSO-EVA. Sits at the upper edge of Adaptive due to the new non-FedRAMP-authorized external interconnection (Anthropic); the absence of federal customer data is what keeps it out of Transformative.","Adds the gated ""Silk Reeling Mirror"" app: a public, HTTP-Basic-Auth-gated API Gateway HTTP API -> Python 3.13 ZIP Lambda serving a browser SPA; the Lambda calls the Anthropic API to generate movement-feedback text.",New self-service capability addition to the site.,New customer/operator-responsibility control: operator-set HTTP Basic Auth credential (POAM-021). SAML/IdP federation is the recommended upgrade. No change to existing customers' configuration responsibilities.,"Gated deploy (create_silk_reeling=true) -> OPA + Checkov + tfsec gate -> Syft/Grype SCA over the built artifact -> VDR report regenerated -> post-implementation secure-configuration verification (Adaptive requirement) -> KSI signal + OSCAL SSP re-emitted. Controls/KSIs to re-verify: RA-5/VDR-*, SA-9/CA-3, SC-7, AC-3/IA-2, AU-2/AU-3, SC-12/SC-28.",docs/scn/SCN-2026-001-silk-reeling.md,"POAM-019..024 (all risk-accepted, Low residual) plus the new-ecosystem SCA blind-spot, remediated by adding Syft/Grype SCA of the built Lambda+SPA artifact to CI feeding the VDR aggregator (RA-5/VDR-CSO-DET).",Sam Aydlette,System Owner / Authorizing Operator,Implemented — live in production (first prod deploy 2026-06-03 via PR #82); post-implementation verification COMPLETE 2026-06-08 at prod commit 354da59 (pass: KEV 0 / blocking 0; SSP data-flow + interconnection rendered; deployed Python/JS deps CVE-free; CM-8 inventory complete),2026-06-03,,,,no,#82,,,,,,,
diff --git a/tests/fixtures/scn/bad/routine-with-record.md b/tests/fixtures/scn/bad/routine-with-record.md
new file mode 100644
index 00000000..273ae797
--- /dev/null
+++ b/tests/fixtures/scn/bad/routine-with-record.md
@@ -0,0 +1,3 @@
+SCN-Type: routine-recurring
+SCN-Rationale: weekly dependency bump with no breaking change.
+SCN-Record: SCN-2026-007
diff --git a/tests/fixtures/scn/bad/transformative-too-soon.md b/tests/fixtures/scn/bad/transformative-too-soon.md
new file mode 100644
index 00000000..5d436194
--- /dev/null
+++ b/tests/fixtures/scn/bad/transformative-too-soon.md
@@ -0,0 +1,3 @@
+SCN-Type: transformative
+SCN-Rationale: the offering starts accepting agency user accounts, a new service used differently by customers.
+SCN-Record: SCN-2099-001
diff --git a/tests/fixtures/scn/bad/two-types.md b/tests/fixtures/scn/bad/two-types.md
new file mode 100644
index 00000000..9f92a1ed
--- /dev/null
+++ b/tests/fixtures/scn/bad/two-types.md
@@ -0,0 +1,3 @@
+SCN-Type: routine-recurring
+SCN-Type: adaptive
+SCN-Rationale: weekly dependency bump with no breaking change.
diff --git a/tests/fixtures/scn/bad/unknown-type.md b/tests/fixtures/scn/bad/unknown-type.md
new file mode 100644
index 00000000..474927c4
--- /dev/null
+++ b/tests/fixtures/scn/bad/unknown-type.md
@@ -0,0 +1,2 @@
+SCN-Type: minor
+SCN-Rationale: a small change to the website content only.
diff --git a/tests/fixtures/scn/good/adaptive.md b/tests/fixtures/scn/good/adaptive.md
new file mode 100644
index 00000000..fb9b18de
--- /dev/null
+++ b/tests/fixtures/scn/good/adaptive.md
@@ -0,0 +1,3 @@
+SCN-Type: adaptive
+SCN-Rationale: adds a new internal component (a CloudWatch alarm) with no new ingress or egress.
+SCN-Record: SCN-2026-007
diff --git a/tests/fixtures/scn/good/emergency.md b/tests/fixtures/scn/good/emergency.md
new file mode 100644
index 00000000..8485df5e
--- /dev/null
+++ b/tests/fixtures/scn/good/emergency.md
@@ -0,0 +1,3 @@
+SCN-Type: emergency
+SCN-Rationale: rotates a leaked credential immediately; the retroactive record follows within 5 business days.
+SCN-Record: SCN-2026-008
diff --git a/tests/fixtures/scn/good/not-significant.md b/tests/fixtures/scn/good/not-significant.md
new file mode 100644
index 00000000..656c1068
--- /dev/null
+++ b/tests/fixtures/scn/good/not-significant.md
@@ -0,0 +1,5 @@
+## Changed
+Fixes a typo on the about page.
+
+**SCN-Type:** not-significant
+**SCN-Rationale:** content-only edit to a public page; no component, boundary, data flow or access change.
diff --git a/tests/fixtures/scn/good/register-transformative.csv b/tests/fixtures/scn/good/register-transformative.csv
new file mode 100644
index 00000000..51fb364a
--- /dev/null
+++ b/tests/fixtures/scn/good/register-transformative.csv
@@ -0,0 +1,2 @@
+scn_id,fedramp_id,assessor_name,related_vulnerability,scn_type,categorization_rationale,short_description,reason_for_change,customer_impact,plan_and_timeline,sia_reference,new_risks_summary,approver_name,approver_title,status,date_initiated,date_started,date_finished,verified_on,emergency,evaluation_prs,plan_final,tpr_human_validation,tpr_assessor_or_reason,sar_reference,docs_to_update,docs_updated_on,docs_update_not_required
+SCN-2099-003,,N/A (sole-operator self-attestation; no 3PAO engaged),None (proactive feature addition),transformative,"Net-new service component with new public ingress and new external egress; no FedRAMP Certification class change and no federal customer data introduced, so not transformative and not a class change; not regular/routine maintenance, so not routine-recurring. Resolves to Adaptive per SCN-CSO-EVA. Sits at the upper edge of Adaptive due to the new non-FedRAMP-authorized external interconnection (Anthropic); the absence of federal customer data is what keeps it out of Transformative.","Adds the gated ""Silk Reeling Mirror"" app: a public, HTTP-Basic-Auth-gated API Gateway HTTP API -> Python 3.13 ZIP Lambda serving a browser SPA; the Lambda calls the Anthropic API to generate movement-feedback text.",New self-service capability addition to the site.,New customer/operator-responsibility control: operator-set HTTP Basic Auth credential (POAM-021). SAML/IdP federation is the recommended upgrade. No change to existing customers' configuration responsibilities.,"Gated deploy (create_silk_reeling=true) -> OPA + Checkov + tfsec gate -> Syft/Grype SCA over the built artifact -> VDR report regenerated -> post-implementation secure-configuration verification (Adaptive requirement) -> KSI signal + OSCAL SSP re-emitted. Controls/KSIs to re-verify: RA-5/VDR-*, SA-9/CA-3, SC-7, AC-3/IA-2, AU-2/AU-3, SC-12/SC-28.",docs/scn/SCN-2026-001-silk-reeling.md,Fictitious example.,Sam Aydlette,System Owner / Authorizing Operator,Fictitious example,2026-09-01,2026-11-02,2026-11-13,2026-11-20,no,#9999,yes,yes,No third-party assessor engaged: none is under contract; the operator validated the scope.,N/A: no assessor engaged; provider verification in docs/scn/SCN-2099-003.md,docs/secure-configuration-guide.md,,
diff --git a/tests/fixtures/scn/good/routine-recurring-legacy-spelling.md b/tests/fixtures/scn/good/routine-recurring-legacy-spelling.md
new file mode 100644
index 00000000..c1992bd0
--- /dev/null
+++ b/tests/fixtures/scn/good/routine-recurring-legacy-spelling.md
@@ -0,0 +1,2 @@
+SCN-Type: Routine Recurring
+SCN-Rationale: weekly Dependabot patch bump of a library already in the inventory, no breaking change.
diff --git a/tests/fixtures/scn/good/transformative-ready.md b/tests/fixtures/scn/good/transformative-ready.md
new file mode 100644
index 00000000..ec1ce069
--- /dev/null
+++ b/tests/fixtures/scn/good/transformative-ready.md
@@ -0,0 +1,3 @@
+SCN-Type: transformative
+SCN-Rationale: the offering starts accepting agency user accounts, a new service used differently by customers.
+SCN-Record: SCN-2099-002
diff --git a/tests/fixtures/scn/index.json b/tests/fixtures/scn/index.json
new file mode 100644
index 00000000..b286cf31
--- /dev/null
+++ b/tests/fixtures/scn/index.json
@@ -0,0 +1,10 @@
+{
+  "notifications": [
+    {"scnId": "SCN-2099-001", "notices": [
+      {"stage": "initial-plan", "rule": "SCN-TRF-NIP", "deadline": "2099-01-01", "publishedOn": "2026-10-20", "onTime": true},
+      {"stage": "final-plan", "rule": "SCN-TRF-NFP", "deadline": "2099-01-01", "publishedOn": "2026-11-02", "onTime": true}]},
+    {"scnId": "SCN-2099-002", "notices": [
+      {"stage": "initial-plan", "rule": "SCN-TRF-NIP", "deadline": "2099-01-01", "publishedOn": "2026-09-01", "onTime": true},
+      {"stage": "final-plan", "rule": "SCN-TRF-NFP", "deadline": "2099-01-01", "publishedOn": "2026-10-15", "onTime": true}]}
+  ]
+}
diff --git a/tests/fixtures/scn/log-previous.json b/tests/fixtures/scn/log-previous.json
new file mode 100644
index 00000000..63ea19de
--- /dev/null
+++ b/tests/fixtures/scn/log-previous.json
@@ -0,0 +1,11 @@
+{
+  "genesis_commit": "1111111111111111111111111111111111111111",
+  "entries": [
+    {"commit": "1111111111111111111111111111111111111111", "merged_on": "2026-11-06", "pull_request": 501,
+     "evaluator": "sam-aydlette", "scn_type": "not-significant",
+     "rationale": "compliance-process change; no component, boundary or access change.", "scn_record": null, "problem": null},
+    {"commit": "2222222222222222222222222222222222222222", "merged_on": "2026-11-09", "pull_request": 502,
+     "evaluator": "sam-aydlette", "scn_type": "adaptive",
+     "rationale": "adds a new internal alarm with no new ingress or egress.", "scn_record": "SCN-2026-007", "problem": null}
+  ]
+}
diff --git a/tests/fixtures/signers/guide-missing-maintainer.json b/tests/fixtures/signers/guide-missing-maintainer.json
new file mode 100644
index 00000000..f26f4e00
--- /dev/null
+++ b/tests/fixtures/signers/guide-missing-maintainer.json
@@ -0,0 +1,28 @@
+{
+  "_note": "Known-bad: an assessor guide that accepts only the deploy's signature on the SDR, which package-maintenance.yml also writes and signs. tests/test_publishers.py must report exactly this artifact.",
+  "identities": {
+    "deploy": "https://github.com/sam-aydlette/samaydlette.com/.github/workflows/deploy-with-opa.yml@refs/heads/main",
+    "nightly": "https://github.com/sam-aydlette/samaydlette.com/.github/workflows/evidence-nightly.yml@refs/heads/main",
+    "assessor": "https://github.com/sam-aydlette/samaydlette.com/.github/workflows/simulated-assessor.yml@refs/heads/main",
+    "oidc_issuer": "https://token.actions.githubusercontent.com"
+  },
+  "rules": [
+    {
+      "rule_id": "EXAMPLE-RULE",
+      "evidence": [
+        {"kind": "artifact", "ref": ".well-known/ksi-signal.json",
+         "check": {"artifact": {"url": "https://samaydlette.com/.well-known/ksi-signal.json",
+                                "bundle_url": "https://samaydlette.com/.well-known/ksi-signal.bundle",
+                                "identities": ["deploy"]}}},
+        {"kind": "artifact", "ref": ".well-known/vdr-report.json",
+         "check": {"artifact": {"url": "https://samaydlette.com/.well-known/vdr-report.json",
+                                "bundle_url": "https://samaydlette.com/.well-known/vdr-report.bundle",
+                                "identities": ["deploy", "nightly"]}}},
+        {"kind": "artifact", "ref": ".well-known/security-decision-record.json",
+         "check": {"artifact": {"url": "https://samaydlette.com/.well-known/security-decision-record.json",
+                                "bundle_url": "https://samaydlette.com/.well-known/security-decision-record.bundle",
+                                "identities": ["deploy"]}}}
+      ]
+    }
+  ]
+}
diff --git a/tests/fixtures/third-party/decided-without-tpr-fields.json b/tests/fixtures/third-party/decided-without-tpr-fields.json
new file mode 100644
index 00000000..52e276b3
--- /dev/null
+++ b/tests/fixtures/third-party/decided-without-tpr-fields.json
@@ -0,0 +1,19 @@
+{
+ "_note": "Known-bad (MAS-CSO-TPR): a decided record without the four fields FedRAMP requires.",
+ "components": {
+  "ext::cisa-kev": {
+   "upstream_offering": "CISA Known Exploited Vulnerabilities catalog (JSON feed)",
+   "upstream_component_id": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json",
+   "responsibility_split": {
+    "upstream_runs": "the catalog and its feed",
+    "provider_configures": "the fetch and its failure handling"
+   },
+   "evidence": [
+    "test fixture"
+   ],
+   "decided_by": "Operator",
+   "decided_on": "2026-11-03",
+   "usage_and_configuration": "fixture usage"
+  }
+ }
+}
diff --git a/tests/fixtures/third-party/decided.json b/tests/fixtures/third-party/decided.json
index 73739eef..7e3162da 100644
--- a/tests/fixtures/third-party/decided.json
+++ b/tests/fixtures/third-party/decided.json
@@ -1,8 +1,22 @@
-{"_note": "test fixture", "components": {
+{
+ "_note": "test fixture",
+ "components": {
   "ext::cisa-kev": {
-    "upstream_offering": "CISA Known Exploited Vulnerabilities catalog (JSON feed)",
-    "upstream_component_id": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json",
-    "responsibility_split": {"upstream_runs": "the catalog and its feed", "provider_configures": "the fetch and its failure handling"},
-    "evidence": ["test fixture"],
-    "decided_by": "Operator", "decided_on": "2026-11-03"}
-}}
+   "upstream_offering": "CISA Known Exploited Vulnerabilities catalog (JSON feed)",
+   "upstream_component_id": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json",
+   "responsibility_split": {
+    "upstream_runs": "the catalog and its feed",
+    "provider_configures": "the fetch and its failure handling"
+   },
+   "evidence": [
+    "test fixture"
+   ],
+   "decided_by": "Operator",
+   "decided_on": "2026-11-03",
+   "usage_and_configuration": "fixture usage",
+   "justification": "fixture justification",
+   "mitigations": "fixture mitigations",
+   "compensating_controls": "fixture compensating controls"
+  }
+ }
+}
diff --git a/tests/fixtures/triage/golden-report.json b/tests/fixtures/triage/golden-report.json
index 9385d207..331d878c 100644
--- a/tests/fixtures/triage/golden-report.json
+++ b/tests/fixtures/triage/golden-report.json
@@ -201,7 +201,7 @@
     ],
     "first_detected": "2026-10-14T12:00:00+00:00",
     "is_kev": false,
-    "pain": "N1",
+    "pain": "N0",
     "scanners": [
      "grype"
     ]
@@ -281,7 +281,7 @@
     ],
     "first_detected": "2026-11-03T12:00:00+00:00",
     "is_kev": false,
-    "pain": "N1",
+    "pain": "N0",
     "scanners": [
      "grype"
     ]
@@ -349,7 +349,7 @@
     ],
     "first_detected": "2026-11-03T12:00:00+00:00",
     "is_kev": false,
-    "pain": "N1",
+    "pain": "N0",
     "scanners": [
      "grype"
     ]
@@ -806,13 +806,75 @@
      "score": 0.01,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "known-exploited",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it; exploited elsewhere (CISA KEV), which the policy treats as likely exploitable (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.01,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": true
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "irv-package"
+      ],
+      "mitigations": [],
+      "open": 1
+     },
+     "reachability": {
+      "basis": "package-host-unrecorded",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "false-positive",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": null,
+    "group_id": "cve:CVE-0000-1001",
+    "group_irv": null,
+    "group_lev": null,
+    "group_pain": null,
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": true,
     "irv_basis": "package-host-unrecorded",
     "is_blocking": true,
@@ -826,6 +888,11 @@
     "occurrences": 1,
     "overdue_explanation": "KEV (CISA Known Exploited Vulnerability)",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -876,13 +943,85 @@
      "score": 0.01,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": true,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "floor",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.01,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "none"
+     },
+     "proximate": {
+      "findings": [
+       "floor-v4",
+       "fm-flag",
+       "likely-overdue-short",
+       "m-full",
+       "m-nirv",
+       "m-void",
+       "n5-block",
+       "r-fp"
+      ],
+      "mitigations": [
+       "MIT-1",
+       "MIT-2"
+      ],
+      "open": 5
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-12-21T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1002",
+    "group_irv": true,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": true,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -899,6 +1038,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 48d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -949,13 +1093,85 @@
      "score": 0.0,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": true,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "floor",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.0,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "none"
+     },
+     "proximate": {
+      "findings": [
+       "floor",
+       "fm-flag",
+       "likely-overdue-short",
+       "m-full",
+       "m-nirv",
+       "m-void",
+       "n5-block",
+       "r-fp"
+      ],
+      "mitigations": [
+       "MIT-1",
+       "MIT-2"
+      ],
+      "open": 5
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-12-21T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1003",
+    "group_irv": true,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": true,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -972,6 +1188,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 48d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -1022,13 +1243,112 @@
      "score": 0.01,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "prediction",
+      "lev": false
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.01,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "none"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-05-14T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1004",
+    "group_irv": false,
+    "group_lev": false,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -1045,6 +1365,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 192d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -1091,13 +1416,76 @@
     "description": "",
     "disposition_record": null,
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": true,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "configuration in the public source repository",
+      "value": "public-source"
+     },
+     "exploitability": {
+      "basis": "no-direct-impact",
+      "lev": false
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "none"
+     },
+     "proximate": {
+      "findings": [
+       "c-ra",
+       "c-ra-lapsed",
+       "c-ra-tfsec",
+       "cfg-noscore",
+       "informational",
+       "irv-inventory-true"
+      ],
+      "mitigations": [],
+      "open": 4
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": null,
+    "group_id": "check:checkov:CKV_AWS_999",
+    "group_irv": true,
+    "group_lev": false,
+    "group_pain": "N1",
     "historical_pain": "N1",
+    "impact_rationale": "N1, minimal customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": true,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -1111,6 +1499,11 @@
     "occurrences": 1,
     "overdue_explanation": "informational severity; no remediation SLA applies",
     "pain": "N1",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -1161,13 +1554,112 @@
      "score": 0.5,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "prediction",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.5,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-03-11T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1005",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -1184,6 +1676,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 128d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -1234,13 +1731,112 @@
      "score": 0.01,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "prediction",
+      "lev": false
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.01,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-05-14T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1006",
+    "group_irv": false,
+    "group_lev": false,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -1257,6 +1853,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 192d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -1307,13 +1908,112 @@
      "score": 0.1,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "prediction",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.1,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-03-11T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1007",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -1330,6 +2030,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 128d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -1376,13 +2081,108 @@
     "description": "",
     "disposition_record": null,
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "no vector",
+      "gained": "unknown",
+      "required": "unknown"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-03-11T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1008",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the scanner's severity (no vector): a default, not a contextual estimate; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -1399,6 +2199,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 128d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -1449,13 +2254,112 @@
      "score": 0.0,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "exploitation-observed",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "reported by the source",
+      "value": "active"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.0,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-03-11T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1009",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -1472,6 +2376,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 128d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -1518,13 +2427,76 @@
     "description": "",
     "disposition_record": null,
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": true,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "configuration in the public source repository",
+      "value": "public-source"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "no vector",
+      "gained": "unknown",
+      "required": "unknown"
+     },
+     "proximate": {
+      "findings": [
+       "c-ra",
+       "c-ra-lapsed",
+       "c-ra-tfsec",
+       "informational",
+       "irv-inventory-true",
+       "no-impact"
+      ],
+      "mitigations": [],
+      "open": 4
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": null,
+    "group_id": "check:checkov:CKV_AWS_998",
+    "group_irv": true,
+    "group_lev": true,
+    "group_pain": "N1",
     "historical_pain": "N1",
+    "impact_rationale": "N1, minimal customer effects: the scanner's severity (no vector): a default, not a contextual estimate; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": true,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -1538,6 +2510,11 @@
     "occurrences": 1,
     "overdue_explanation": "informational severity; no remediation SLA applies",
     "pain": "N1",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -1584,13 +2561,69 @@
     "description": "",
     "disposition_record": null,
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": true,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "found by an unauthenticated outside-in scan",
+      "value": "observed-outside-in"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "no vector",
+      "gained": "unknown",
+      "required": "unknown"
+     },
+     "proximate": {
+      "findings": [],
+      "mitigations": [],
+      "open": 0
+     },
+     "reachability": {
+      "basis": "observed",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-12-21T12:00:00+00:00",
+    "group_id": "cve:ZAP-1",
+    "group_irv": true,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the scanner's severity (no vector): a default, not a contextual estimate; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": true,
     "irv_basis": "observed",
     "is_blocking": false,
@@ -1607,6 +2640,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 48d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -1657,13 +2695,73 @@
      "score": 0.01,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "multi",
+      "data_sensitivity": "cui",
+      "internet_reachable": true,
+      "mission_criticality": "high"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "prediction",
+      "lev": false
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.01,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 0,
+      "findings": 1,
+      "inventory_share": 0.0
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [],
+      "mitigations": [],
+      "open": 0
+     },
+     "reachability": {
+      "basis": "unresolved",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-11-19T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1010",
+    "group_irv": true,
+    "group_lev": false,
+    "group_pain": "N5",
     "historical_pain": "N5",
+    "impact_rationale": "N5, a debilitating effect on more than one agency: the advisory's CVSS vector; on a component holding cui data, high criticality, multi-agency scope.",
     "internet_reachable": true,
     "irv_basis": "unresolved",
     "is_blocking": false,
@@ -1680,6 +2778,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 16d allowed",
     "pain": "N5",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -1730,13 +2833,75 @@
      "score": 0.01,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "prediction",
+      "lev": false
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.01,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "kev-fp"
+      ],
+      "mitigations": [],
+      "open": 0
+     },
+     "reachability": {
+      "basis": "package-host-unrecorded",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-05-14T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1011",
+    "group_irv": true,
+    "group_lev": false,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": true,
     "irv_basis": "package-host-unrecorded",
     "is_blocking": false,
@@ -1753,6 +2918,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 192d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -1799,13 +2969,108 @@
     "description": "",
     "disposition_record": null,
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "configuration in the public source repository",
+      "value": "public-source"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "no vector",
+      "gained": "unknown",
+      "required": "unknown"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-03-11T12:00:00+00:00",
+    "group_id": "check:checkov:CKV_AWS_997",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the scanner's severity (no vector): a default, not a contextual estimate; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -1822,6 +3087,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 128d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -1868,13 +3138,76 @@
     "description": "",
     "disposition_record": null,
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": true,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "configuration in the public source repository",
+      "value": "public-source"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "no vector",
+      "gained": "unknown",
+      "required": "unknown"
+     },
+     "proximate": {
+      "findings": [
+       "c-ra",
+       "c-ra-lapsed",
+       "c-ra-tfsec",
+       "cfg-noscore",
+       "informational",
+       "no-impact"
+      ],
+      "mitigations": [],
+      "open": 4
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-12-21T12:00:00+00:00",
+    "group_id": "check:checkov:CKV_AWS_996",
+    "group_irv": true,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the scanner's severity (no vector): a default, not a contextual estimate; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": true,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -1891,6 +3224,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 48d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -1933,7 +3271,7 @@
     "completed_reductions": [],
     "component_id": "cmp-pub",
     "current_disposition": "mitigated",
-    "current_pain": "N1",
+    "current_pain": "N0",
     "cve": "CVE-0000-1012",
     "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
     "days_since_first_detected": 20,
@@ -1941,13 +3279,81 @@
     "description": "",
     "disposition_record": null,
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": true,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "fully-mitigated",
+      "lev": false
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "none"
+     },
+     "proximate": {
+      "findings": [
+       "floor",
+       "floor-v4",
+       "fm-flag",
+       "likely-overdue-short",
+       "m-nirv",
+       "m-void",
+       "n5-block",
+       "r-fp"
+      ],
+      "mitigations": [
+       "MIT-1",
+       "MIT-2"
+      ],
+      "open": 6
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "mitigated",
     "first_detected": "2026-10-14T12:00:00+00:00",
     "first_evaluated": "2026-10-14T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": true,
-    "historical_pain": "N1",
+    "group_due_at": null,
+    "group_id": "cve:CVE-0000-1012",
+    "group_irv": null,
+    "group_lev": null,
+    "group_pain": null,
+    "historical_pain": "N0",
+    "impact_rationale": "Fully mitigated: the impact has been removed (N0).",
     "internet_reachable": true,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -1971,13 +3377,18 @@
     "next_reduction": null,
     "occurrences": 1,
     "overdue_explanation": "documented suppression (mitigated); tracked as None",
-    "pain": "N1",
+    "pain": "N0",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
       "irv": true,
       "lev": false,
-      "pain": "N1",
+      "pain": "N0",
       "reason": "first evaluation"
      }
     ],
@@ -2022,13 +3433,85 @@
      "score": 0.01,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": true,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "prediction",
+      "lev": false
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.01,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "none"
+     },
+     "proximate": {
+      "findings": [
+       "floor",
+       "floor-v4",
+       "fm-flag",
+       "likely-overdue-short",
+       "m-full",
+       "m-void",
+       "n5-block",
+       "r-fp"
+      ],
+      "mitigations": [
+       "MIT-1",
+       "MIT-2"
+      ],
+      "open": 5
+     },
+     "reachability": {
+      "basis": "mitigation",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-05-14T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1013",
+    "group_irv": false,
+    "group_lev": false,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "mitigation",
     "is_blocking": false,
@@ -2056,6 +3539,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 192d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -2106,13 +3594,112 @@
      "score": 0.9,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "mitigation",
+      "lev": false
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.9,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-05-14T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1014",
+    "group_irv": false,
+    "group_lev": false,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -2140,6 +3727,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 192d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -2190,13 +3782,112 @@
      "score": 0.01,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "known-exploited",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it; exploited elsewhere (CISA KEV), which the policy treats as likely exploitable (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.01,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": true
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-03-11T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1015",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": true,
@@ -2224,6 +3915,11 @@
     "occurrences": 1,
     "overdue_explanation": "KEV (CISA Known Exploited Vulnerability)",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -2281,15 +3977,87 @@
      "score": 0.01,
      "score_date": "2026-11-03T00:00:00Z"
     },
-    "final_disposition": "open",
-    "first_detected": "2026-10-04T12:00:00+00:00",
-    "first_evaluated": "2026-10-04T12:00:00+00:00",
-    "fix_state": null,
-    "fix_versions": null,
-    "fully_mitigated": false,
-    "historical_pain": "N3",
-    "internet_reachable": true,
-    "irv_basis": "inventory",
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": true,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "floor",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.01,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "none"
+     },
+     "proximate": {
+      "findings": [
+       "floor",
+       "floor-v4",
+       "fm-flag",
+       "likely-overdue-short",
+       "m-full",
+       "m-nirv",
+       "n5-block",
+       "r-fp"
+      ],
+      "mitigations": [
+       "MIT-1",
+       "MIT-2"
+      ],
+      "open": 5
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
+    "final_disposition": "open",
+    "first_detected": "2026-10-04T12:00:00+00:00",
+    "first_evaluated": "2026-10-04T12:00:00+00:00",
+    "fix_state": null,
+    "fix_versions": null,
+    "fully_mitigated": false,
+    "group_due_at": "2026-11-21T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1016",
+    "group_irv": true,
+    "group_lev": true,
+    "group_pain": "N2",
+    "historical_pain": "N3",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
+    "internet_reachable": true,
+    "irv_basis": "inventory",
     "is_blocking": false,
     "is_kev": false,
     "is_overdue": false,
@@ -2316,6 +4084,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 30d of 48d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-10-04T12:00:00+00:00",
@@ -2368,7 +4141,7 @@
     "completed_reductions": [],
     "component_id": "cmp-pub",
     "current_disposition": "mitigated",
-    "current_pain": "N1",
+    "current_pain": "N0",
     "cve": "CVE-0000-1017",
     "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
     "days_since_first_detected": 0,
@@ -2376,13 +4149,81 @@
     "description": "",
     "disposition_record": null,
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": true,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "fully-mitigated",
+      "lev": false
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "none"
+     },
+     "proximate": {
+      "findings": [
+       "floor",
+       "floor-v4",
+       "likely-overdue-short",
+       "m-full",
+       "m-nirv",
+       "m-void",
+       "n5-block",
+       "r-fp"
+      ],
+      "mitigations": [
+       "MIT-1",
+       "MIT-2"
+      ],
+      "open": 6
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "mitigated",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": true,
-    "historical_pain": "N1",
+    "group_due_at": null,
+    "group_id": "cve:CVE-0000-1017",
+    "group_irv": null,
+    "group_lev": null,
+    "group_pain": null,
+    "historical_pain": "N0",
+    "impact_rationale": "Fully mitigated: the impact has been removed (N0).",
     "internet_reachable": true,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -2395,13 +4236,18 @@
     "next_reduction": null,
     "occurrences": 1,
     "overdue_explanation": "documented suppression (mitigated); tracked as None",
-    "pain": "N1",
+    "pain": "N0",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
       "irv": true,
       "lev": false,
-      "pain": "N1",
+      "pain": "N0",
       "reason": "first evaluation"
      }
     ],
@@ -2456,13 +4302,112 @@
      "score": 0.5,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "prediction",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.5,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "mitigation",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-03-11T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1020",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "mitigation",
     "is_blocking": false,
@@ -2490,6 +4435,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 128d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -2546,13 +4496,108 @@
      "status": "invalid"
     },
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-03-11T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1021",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -2569,6 +4614,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 128d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -2625,13 +4675,108 @@
      "status": "invalid"
     },
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "mitigation",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-03-11T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1022",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "mitigation",
     "is_blocking": false,
@@ -2659,6 +4804,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 128d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -2697,7 +4847,7 @@
     "completed_reductions": [],
     "component_id": "cmp-int",
     "current_disposition": "mitigated",
-    "current_pain": "N1",
+    "current_pain": "N0",
     "cve": "CVE-0000-1023",
     "cvss_vector": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N",
     "days_since_first_detected": 0,
@@ -2715,13 +4865,108 @@
      "status": "in-force"
     },
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "fully-mitigated",
+      "lev": false
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 28
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "mitigated",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": true,
-    "historical_pain": "N1",
+    "group_due_at": null,
+    "group_id": "cve:CVE-0000-1023",
+    "group_irv": null,
+    "group_lev": null,
+    "group_pain": null,
+    "historical_pain": "N0",
+    "impact_rationale": "Fully mitigated: the impact has been removed (N0).",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -2745,13 +4990,18 @@
     "next_reduction": null,
     "occurrences": 1,
     "overdue_explanation": "documented suppression (mitigated); tracked as DEC-905",
-    "pain": "N1",
+    "pain": "N0",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
       "irv": false,
       "lev": false,
-      "pain": "N1",
+      "pain": "N0",
       "reason": "first evaluation"
      }
     ],
@@ -2802,13 +5052,108 @@
      "status": "invalid"
     },
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-03-11T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1024",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -2825,6 +5170,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 128d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -2881,13 +5231,108 @@
      "status": "lapsed"
     },
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-03-11T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1025",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -2904,6 +5349,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 128d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -2964,13 +5414,112 @@
      "score": 0.5,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "prediction",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.5,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "none"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-07-26T12:00:00+00:00",
     "first_evaluated": "2026-07-26T12:00:00+00:00",
     "fix_state": "not-fixed",
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-08-27T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1026",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N3",
     "historical_pain": "N3",
+    "impact_rationale": "N3, a disruptive effect on one agency: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": true,
@@ -2987,6 +5536,11 @@
     "occurrences": 1,
     "overdue_explanation": "past Class C SLA (100d > 32d from 2026-07-26T12:00:00+00:00 for PAIN=N3, LEV=True, IRV=False)",
     "pain": "N3",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -3043,6 +5597,95 @@
      "status": "invalid"
     },
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
@@ -3051,7 +5694,13 @@
      "2.0.0"
     ],
     "fully_mitigated": false,
+    "group_due_at": "2027-03-11T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1027",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -3068,6 +5717,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 128d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -3124,13 +5778,108 @@
      "status": "invalid"
     },
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-03-11T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1028",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -3147,6 +5896,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 128d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -3203,13 +5957,108 @@
      "status": "invalid"
     },
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-03-11T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1029",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -3226,6 +6075,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 128d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -3282,13 +6136,108 @@
      "status": "invalid"
     },
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-03-11T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1030",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -3305,6 +6254,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 128d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -3361,13 +6315,108 @@
      "status": "in-force"
     },
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-03-11T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1031",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -3384,6 +6433,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 128d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -3410,6 +6464,7 @@
     "acceptance_explanation": "not recorded",
     "accepted": true,
     "accepted_at": "2026-04-09T12:00:00+00:00",
+    "accepted_basis": "maximum-period-passed",
     "block_reason": null,
     "clock_basis": [
      {
@@ -3440,13 +6495,108 @@
      "status": "in-force"
     },
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 28
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "operational-requirement",
     "first_detected": "2025-09-29T12:00:00+00:00",
     "first_evaluated": "2025-09-29T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-02-04T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1032",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -3463,6 +6613,11 @@
     "occurrences": 1,
     "overdue_explanation": "documented suppression (operational-requirement); tracked as DEC-914",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -3519,13 +6674,108 @@
      "status": "in-force"
     },
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-03-11T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1033",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -3542,6 +6792,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 128d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -3598,13 +6853,81 @@
      "status": "in-force"
     },
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": true,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "floor",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "none"
+     },
+     "proximate": {
+      "findings": [
+       "floor",
+       "floor-v4",
+       "fm-flag",
+       "likely-overdue-short",
+       "m-full",
+       "m-nirv",
+       "m-void",
+       "n5-block"
+      ],
+      "mitigations": [
+       "MIT-1",
+       "MIT-2"
+      ],
+      "open": 6
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "false-positive",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": null,
+    "group_id": "cve:CVE-0000-1034",
+    "group_irv": null,
+    "group_lev": null,
+    "group_pain": null,
     "historical_pain": "N3",
+    "impact_rationale": "N3, a disruptive effect on one agency: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": true,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -3618,6 +6941,11 @@
     "occurrences": 1,
     "overdue_explanation": "documented suppression (false-positive); tracked as DEC-915",
     "pain": "N3",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -3674,13 +7002,108 @@
      "status": "in-force"
     },
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 28
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "operational-requirement",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-03-11T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1035",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -3697,6 +7120,11 @@
     "occurrences": 1,
     "overdue_explanation": "documented suppression (operational-requirement); tracked as DEC-916",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -3743,13 +7171,108 @@
     "description": "",
     "disposition_record": null,
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "no vector",
+      "gained": "unknown",
+      "required": "unknown"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-12-05T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1036",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N3",
     "historical_pain": "N3",
+    "impact_rationale": "N3, a disruptive effect on one agency: the scanner's severity (no vector): a default, not a contextual estimate; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -3766,6 +7289,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 32d allowed",
     "pain": "N3",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -3822,13 +7350,76 @@
      "status": "in-force"
     },
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": true,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "configuration in the public source repository",
+      "value": "public-source"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "no vector",
+      "gained": "unknown",
+      "required": "unknown"
+     },
+     "proximate": {
+      "findings": [
+       "c-ra-lapsed",
+       "c-ra-tfsec",
+       "cfg-noscore",
+       "informational",
+       "irv-inventory-true",
+       "no-impact"
+      ],
+      "mitigations": [],
+      "open": 5
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": true
+     }
+    },
+    "evaluation_late": "default-after-evaluation-window",
     "final_disposition": "risk-accepted",
     "first_detected": "2026-08-05T12:00:00+00:00",
     "first_evaluated": "2026-08-05T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-09-22T12:00:00+00:00",
+    "group_id": "decision:DEC-007",
+    "group_irv": true,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the scanner's severity (no vector): a default, not a contextual estimate; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": true,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -3845,6 +7436,11 @@
     "occurrences": 1,
     "overdue_explanation": "documented suppression (risk-accepted); tracked as DEC-007",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -3901,13 +7497,76 @@
      "status": "lapsed"
     },
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": true,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "configuration in the public source repository",
+      "value": "public-source"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "no vector",
+      "gained": "unknown",
+      "required": "unknown"
+     },
+     "proximate": {
+      "findings": [
+       "c-ra",
+       "c-ra-tfsec",
+       "cfg-noscore",
+       "informational",
+       "irv-inventory-true",
+       "no-impact"
+      ],
+      "mitigations": [],
+      "open": 4
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-12-21T12:00:00+00:00",
+    "group_id": "decision:DEC-009",
+    "group_irv": true,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the scanner's severity (no vector): a default, not a contextual estimate; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": true,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -3924,6 +7583,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 48d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -3980,13 +7644,76 @@
      "status": "in-force"
     },
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": true,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "configuration in the public source repository",
+      "value": "public-source"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "no vector",
+      "gained": "unknown",
+      "required": "unknown"
+     },
+     "proximate": {
+      "findings": [
+       "c-ra",
+       "c-ra-lapsed",
+       "cfg-noscore",
+       "informational",
+       "irv-inventory-true",
+       "no-impact"
+      ],
+      "mitigations": [],
+      "open": 5
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "risk-accepted",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-12-21T12:00:00+00:00",
+    "group_id": "decision:DEC-010",
+    "group_irv": true,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the scanner's severity (no vector): a default, not a contextual estimate; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": true,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -4003,6 +7730,11 @@
     "occurrences": 1,
     "overdue_explanation": "documented suppression (risk-accepted); tracked as DEC-010",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -4059,13 +7791,108 @@
      "status": "in-force"
     },
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "configuration in the public source repository",
+      "value": "public-source"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "no vector",
+      "gained": "unknown",
+      "required": "unknown"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 28
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "false-positive",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": null,
+    "group_id": "decision:DEC-003",
+    "group_irv": null,
+    "group_lev": null,
+    "group_pain": null,
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the scanner's severity (no vector): a default, not a contextual estimate; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -4079,6 +7906,11 @@
     "occurrences": 1,
     "overdue_explanation": "documented suppression (false-positive); tracked as DEC-003",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -4135,13 +7967,108 @@
      "status": "in-force"
     },
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "configuration in the public source repository",
+      "value": "public-source"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "no vector",
+      "gained": "unknown",
+      "required": "unknown"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 28
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "false-positive",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": null,
+    "group_id": "decision:DEC-004",
+    "group_irv": null,
+    "group_lev": null,
+    "group_pain": null,
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the scanner's severity (no vector): a default, not a contextual estimate; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -4155,6 +8082,11 @@
     "occurrences": 1,
     "overdue_explanation": "documented suppression (false-positive); tracked as DEC-004",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -4201,13 +8133,81 @@
     "description": "",
     "disposition_record": null,
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": true,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "floor",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "none"
+     },
+     "proximate": {
+      "findings": [
+       "floor",
+       "floor-v4",
+       "fm-flag",
+       "likely-overdue-short",
+       "m-full",
+       "m-nirv",
+       "m-void",
+       "r-fp"
+      ],
+      "mitigations": [
+       "MIT-1",
+       "MIT-2"
+      ],
+      "open": 5
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-02T12:00:00+00:00",
     "first_evaluated": "2026-11-02T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-11-18T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1040",
+    "group_irv": true,
+    "group_lev": true,
+    "group_pain": "N3",
     "historical_pain": "N3",
+    "impact_rationale": "N3, a disruptive effect on one agency: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": true,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -4224,6 +8224,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 1d of 16d allowed",
     "pain": "N3",
+    "public_disclosure": {
+     "level": "summary",
+     "policy": "DEC-182",
+     "reason": "open, IRV, LEV and N3: detail withheld from public artifacts until remediated or dispositioned; no party receives it (DEC-194)"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -4274,13 +8279,112 @@
      "score": 0.5,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "prediction",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.5,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-06-06T12:00:00+00:00",
     "first_evaluated": "2026-06-06T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-10-12T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1041",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": true,
@@ -4297,6 +8401,11 @@
     "occurrences": 1,
     "overdue_explanation": "past Class C SLA (150d > 128d from 2026-06-06T12:00:00+00:00 for PAIN=N2, LEV=True, IRV=False)",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -4323,6 +8432,7 @@
     "acceptance_explanation": "not recorded",
     "accepted": true,
     "accepted_at": "2026-10-26T12:00:00+00:00",
+    "accepted_basis": "maximum-period-passed",
     "block_reason": "past Class C SLA (200d > 192d from 2026-04-17T12:00:00+00:00 for PAIN=N2, LEV=False, IRV=False)",
     "clock_basis": [
      {
@@ -4347,13 +8457,112 @@
      "score": 0.01,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "prediction",
+      "lev": false
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.01,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-04-17T12:00:00+00:00",
     "first_evaluated": "2026-04-17T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-10-26T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1042",
+    "group_irv": false,
+    "group_lev": false,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": true,
@@ -4370,6 +8579,11 @@
     "occurrences": 1,
     "overdue_explanation": "past Class C SLA (200d > 192d from 2026-04-17T12:00:00+00:00 for PAIN=N2, LEV=False, IRV=False)",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -4420,13 +8634,112 @@
      "score": 0.01,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "prediction",
+      "lev": false
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.01,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-04-29T12:00:00+00:00",
     "first_evaluated": "2026-04-29T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-11-07T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1043",
+    "group_irv": false,
+    "group_lev": false,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -4443,6 +8756,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 188d of 192d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -4489,13 +8807,81 @@
     "description": "",
     "disposition_record": null,
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": true,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "floor",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "none"
+     },
+     "proximate": {
+      "findings": [
+       "floor",
+       "floor-v4",
+       "fm-flag",
+       "m-full",
+       "m-nirv",
+       "m-void",
+       "n5-block",
+       "r-fp"
+      ],
+      "mitigations": [
+       "MIT-1",
+       "MIT-2"
+      ],
+      "open": 5
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-10-20T12:00:00+00:00",
     "first_evaluated": "2026-10-20T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-11-05T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1044",
+    "group_irv": true,
+    "group_lev": true,
+    "group_pain": "N3",
     "historical_pain": "N3",
+    "impact_rationale": "N3, a disruptive effect on one agency: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": true,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -4512,6 +8898,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 14d of 16d allowed",
     "pain": "N3",
+    "public_disclosure": {
+     "level": "summary",
+     "policy": "DEC-182",
+     "reason": "open, IRV, LEV and N3: detail withheld from public artifacts until remediated or dispositioned; no party receives it (DEC-194)"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -4558,13 +8949,76 @@
     "description": "",
     "disposition_record": null,
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": true,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "configuration in the public source repository",
+      "value": "public-source"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "no vector",
+      "gained": "unknown",
+      "required": "unknown"
+     },
+     "proximate": {
+      "findings": [
+       "c-ra",
+       "c-ra-lapsed",
+       "c-ra-tfsec",
+       "cfg-noscore",
+       "irv-inventory-true",
+       "no-impact"
+      ],
+      "mitigations": [],
+      "open": 4
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": null,
+    "group_id": "check:checkov:CKV_AWS_995",
+    "group_irv": true,
+    "group_lev": true,
+    "group_pain": "N1",
     "historical_pain": "N1",
+    "impact_rationale": "N1, minimal customer effects: the scanner's severity (no vector): a default, not a contextual estimate; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": true,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -4578,6 +9032,11 @@
     "occurrences": 1,
     "overdue_explanation": "informational severity; no remediation SLA applies",
     "pain": "N1",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -4624,13 +9083,108 @@
     "description": "",
     "disposition_record": null,
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-09-04T12:00:00+00:00",
     "first_evaluated": "2026-09-04T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-01-10T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1045",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -4647,6 +9201,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 60d of 128d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -4693,13 +9252,108 @@
     "description": "",
     "disposition_record": null,
     "epss": null,
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "no-score",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": null,
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 1,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "ovr-selector-miss",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": "evaluated-late",
     "final_disposition": "open",
     "first_detected": "2026-09-24T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2027-03-11T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1046",
+    "group_irv": false,
+    "group_lev": true,
+    "group_pain": "N2",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -4716,6 +9370,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 128d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -4766,13 +9425,73 @@
      "score": 0.5,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "multi",
+      "data_sensitivity": "cui",
+      "internet_reachable": true,
+      "mission_criticality": "high"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "override",
+      "lev": false
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.5,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 3,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [],
+      "mitigations": [],
+      "open": 0
+     },
+     "reachability": {
+      "basis": "unresolved",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-11-05T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1050",
+    "group_irv": true,
+    "group_lev": true,
+    "group_pain": "N5",
     "historical_pain": "N5",
+    "impact_rationale": "N5, a debilitating effect on more than one agency: the advisory's CVSS vector; on a component holding cui data, high criticality, multi-agency scope.",
     "internet_reachable": true,
     "irv_basis": "unresolved",
     "is_blocking": false,
@@ -4789,6 +9508,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 16d allowed",
     "pain": "N5",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -4839,13 +9563,73 @@
      "score": 0.5,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "multi",
+      "data_sensitivity": "cui",
+      "internet_reachable": true,
+      "mission_criticality": "high"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "prediction",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.5,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 0,
+      "findings": 1,
+      "inventory_share": 0.0
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [],
+      "mitigations": [],
+      "open": 0
+     },
+     "reachability": {
+      "basis": "unresolved",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-11-05T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1051",
+    "group_irv": true,
+    "group_lev": true,
+    "group_pain": "N5",
     "historical_pain": "N5",
+    "impact_rationale": "N5, a debilitating effect on more than one agency: the advisory's CVSS vector; on a component holding cui data, high criticality, multi-agency scope.",
     "internet_reachable": true,
     "irv_basis": "unresolved",
     "is_blocking": true,
@@ -4862,6 +9646,11 @@
     "occurrences": 1,
     "overdue_explanation": "N5+LEV+IRV (most-severe Class C tier)",
     "pain": "N5",
+    "public_disclosure": {
+     "level": "summary",
+     "policy": "DEC-182",
+     "reason": "open, IRV, LEV and N5: detail withheld from public artifacts until remediated or dispositioned; no party receives it (DEC-194)"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -4912,13 +9701,73 @@
      "score": 0.5,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "multi",
+      "data_sensitivity": "cui",
+      "internet_reachable": true,
+      "mission_criticality": "high"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "prediction",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.5,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 3,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [],
+      "mitigations": [],
+      "open": 0
+     },
+     "reachability": {
+      "basis": "unresolved",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-11-05T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1050",
+    "group_irv": true,
+    "group_lev": true,
+    "group_pain": "N5",
     "historical_pain": "N5",
+    "impact_rationale": "N5, a debilitating effect on more than one agency: the advisory's CVSS vector; on a component holding cui data, high criticality, multi-agency scope.",
     "internet_reachable": true,
     "irv_basis": "unresolved",
     "is_blocking": true,
@@ -4935,6 +9784,11 @@
     "occurrences": 1,
     "overdue_explanation": "N5+LEV+IRV (most-severe Class C tier)",
     "pain": "N5",
+    "public_disclosure": {
+     "level": "summary",
+     "policy": "DEC-182",
+     "reason": "open, IRV, LEV and N5: detail withheld from public artifacts until remediated or dispositioned; no party receives it (DEC-194)"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -4985,13 +9839,73 @@
      "score": 0.5,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "multi",
+      "data_sensitivity": "cui",
+      "internet_reachable": true,
+      "mission_criticality": "high"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "known-exploited",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it; exploited elsewhere (CISA KEV), which the policy treats as likely exploitable (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.5,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": true
+     },
+     "prevalence": {
+      "components": 0,
+      "findings": 1,
+      "inventory_share": 0.0
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [],
+      "mitigations": [],
+      "open": 0
+     },
+     "reachability": {
+      "basis": "unresolved",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-11-05T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1052",
+    "group_irv": true,
+    "group_lev": true,
+    "group_pain": "N5",
     "historical_pain": "N5",
+    "impact_rationale": "N5, a debilitating effect on more than one agency: the advisory's CVSS vector; on a component holding cui data, high criticality, multi-agency scope.",
     "internet_reachable": true,
     "irv_basis": "unresolved",
     "is_blocking": true,
@@ -5008,6 +9922,11 @@
     "occurrences": 1,
     "overdue_explanation": "KEV (CISA Known Exploited Vulnerability)",
     "pain": "N5",
+    "public_disclosure": {
+     "level": "summary",
+     "policy": "DEC-182",
+     "reason": "open, IRV, LEV and N5: detail withheld from public artifacts until remediated or dispositioned; no party receives it (DEC-194)"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -5058,13 +9977,112 @@
      "score": 0.5,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "single",
+      "data_sensitivity": "public",
+      "internet_reachable": false,
+      "mission_criticality": "low"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is not internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "prediction",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.5,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 1,
+      "findings": 3,
+      "inventory_share": 0.2
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "high"
+     },
+     "proximate": {
+      "findings": [
+       "c-fp",
+       "c-fp-norecord",
+       "detected-earlier",
+       "floor-nirv",
+       "irv-inventory-false",
+       "legacy-id",
+       "likely-overdue",
+       "m-nlev",
+       "m-nlev-kev",
+       "mav",
+       "no-score",
+       "observed",
+       "overdue",
+       "pred-at",
+       "pred-hi",
+       "pred-lo",
+       "r-accepted-noref",
+       "r-bad-date",
+       "r-config-ignored",
+       "r-fp-control",
+       "r-investigating",
+       "r-lapsed",
+       "r-mitigated-full",
+       "r-mitigated-none",
+       "r-mitigated-ok",
+       "r-mitigated-other",
+       "r-no-review-by",
+       "r-oprq",
+       "r-unknown-term",
+       "r-vendor-fixed",
+       "r-vendor-ok",
+       "r-vendor-unknown"
+      ],
+      "mitigations": [
+       "MIT-3",
+       "MIT-4",
+       "MIT-6",
+       "MIT-7",
+       "MIT-8"
+      ],
+      "open": 27
+     },
+     "reachability": {
+      "basis": "inventory",
+      "irv": false
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": "2026-11-05T12:00:00+00:00",
+    "group_id": "cve:CVE-0000-1050",
+    "group_irv": true,
+    "group_lev": true,
+    "group_pain": "N5",
     "historical_pain": "N2",
+    "impact_rationale": "N2, narrow customer effects: the advisory's CVSS vector; on a component holding public data, low criticality, single-agency scope.",
     "internet_reachable": false,
     "irv_basis": "inventory",
     "is_blocking": false,
@@ -5081,6 +10099,11 @@
     "occurrences": 1,
     "overdue_explanation": "within Class C SLA: 0d of 128d allowed",
     "pain": "N2",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -5131,13 +10154,73 @@
      "score": 0.0,
      "score_date": "2026-11-03T00:00:00Z"
     },
+    "evaluation": {
+     "automatable": {
+      "evidence": null,
+      "source": "VER-EVA-AIA default",
+      "value": "yes"
+     },
+     "criticality": {
+      "agency_scope": "multi",
+      "data_sensitivity": "cui",
+      "internet_reachable": true,
+      "mission_criticality": "high"
+     },
+     "detectability": {
+      "basis": "a published advisory names the package; the component is internet-reachable",
+      "value": "public-advisory"
+     },
+     "exploitability": {
+      "basis": "override",
+      "lev": true
+     },
+     "exploitation": {
+      "assessed_at": "2026-11-03T12:00:00+00:00",
+      "basis": "no incident record names it (DEC-181)",
+      "value": "none-observed"
+     },
+     "known_threats": {
+      "epss": {
+       "model_version": "v2026.06.15",
+       "score": 0.0,
+       "score_date": "2026-11-03T00:00:00Z"
+      },
+      "kev": false
+     },
+     "prevalence": {
+      "components": 0,
+      "findings": 1,
+      "inventory_share": 0.0
+     },
+     "privilege": {
+      "basis": "CVSS PR/S",
+      "gained": "within-component",
+      "required": "none"
+     },
+     "proximate": {
+      "findings": [],
+      "mitigations": [],
+      "open": 0
+     },
+     "reachability": {
+      "basis": "unresolved",
+      "irv": true
+     }
+    },
+    "evaluation_late": null,
     "final_disposition": "open",
     "first_detected": "2026-11-03T12:00:00+00:00",
     "first_evaluated": "2026-11-03T12:00:00+00:00",
     "fix_state": null,
     "fix_versions": null,
     "fully_mitigated": false,
+    "group_due_at": null,
+    "group_id": "cve:CVE-0000-1053",
+    "group_irv": true,
+    "group_lev": true,
+    "group_pain": "N1",
     "historical_pain": "N1",
+    "impact_rationale": "N1, minimal customer effects: the advisory's CVSS vector; on a component holding cui data, high criticality, multi-agency scope.",
     "internet_reachable": true,
     "irv_basis": "unresolved",
     "is_blocking": false,
@@ -5151,6 +10234,11 @@
     "occurrences": 1,
     "overdue_explanation": "informational severity; no remediation SLA applies",
     "pain": "N1",
+    "public_disclosure": {
+     "level": "full",
+     "policy": "DEC-182",
+     "reason": "not an open IRV+LEV finding at N3 or above: disclosing it will not likely lead to exploitation"
+    },
     "rating_history": [
      {
       "at": "2026-11-03T12:00:00+00:00",
@@ -5174,36 +10262,1040 @@
     "will_be_overdue": false
    }
   ],
-  "impact_level": "Moderate",
-  "ksi_signal_ref": "/.well-known/ksi-signal.json",
-  "report_version": "2.0.0",
-  "risk_accepted": [
+  "groups": [
    {
-    "completed_evaluation": "2026-11-03T12:00:00+00:00",
-    "component_id": null,
-    "current_disposition": "risk-accepted",
-    "cvss_vector": null,
-    "decision_id": "DEC-007",
-    "explanation": "",
-    "first_detected": "2026-11-03T12:00:00+00:00",
-    "first_evaluated": "2026-11-03T12:00:00+00:00",
+    "basis": "check",
+    "components": [
+     "cmp-app"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "check:checkov:CKV_AWS_995",
+    "internet_reachable": true,
+    "likely_exploitable": true,
+    "members": [
+     "informational"
+    ],
+    "open_members": 1,
+    "pain": "N1",
+    "remediation_due_at": null
+   },
+   {
+    "basis": "check",
+    "components": [
+     "cmp-app"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "check:checkov:CKV_AWS_996",
     "internet_reachable": true,
-    "irv_basis": "unresolved",
-    "is_kev": false,
-    "lev_basis": "no-score",
     "likely_exploitable": true,
+    "members": [
+     "irv-inventory-true"
+    ],
+    "open_members": 1,
     "pain": "N2",
-    "resource": ".checkov.yaml",
-    "source": "checkov-suppression",
-    "title": "",
-    "tool_id": "CKV_AWS_68",
-    "tracking_id": "CKV_AWS_68",
-    "vector_source": null
+    "remediation_due_at": "2026-12-21T12:00:00+00:00"
    },
    {
-    "completed_evaluation": "2026-11-03T12:00:00+00:00",
-    "component_id": "cmp-int",
-    "current_disposition": "risk-accepted",
+    "basis": "check",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "check:checkov:CKV_AWS_997",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "irv-inventory-false"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-03-11T12:00:00+00:00"
+   },
+   {
+    "basis": "check",
+    "components": [
+     "cmp-app"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "check:checkov:CKV_AWS_998",
+    "internet_reachable": true,
+    "likely_exploitable": true,
+    "members": [
+     "cfg-noscore"
+    ],
+    "open_members": 1,
+    "pain": "N1",
+    "remediation_due_at": null
+   },
+   {
+    "basis": "check",
+    "components": [
+     "cmp-app"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "check:checkov:CKV_AWS_999",
+    "internet_reachable": true,
+    "likely_exploitable": false,
+    "members": [
+     "no-impact"
+    ],
+    "open_members": 1,
+    "pain": "N1",
+    "remediation_due_at": null
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-pkg"
+    ],
+    "dispositions": [
+     "false-positive"
+    ],
+    "group_id": "cve:CVE-0000-1001",
+    "internet_reachable": null,
+    "likely_exploitable": null,
+    "members": [
+     "kev-fp"
+    ],
+    "open_members": 0,
+    "pain": null,
+    "remediation_due_at": null
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-pub"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1002",
+    "internet_reachable": true,
+    "likely_exploitable": true,
+    "members": [
+     "floor"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2026-12-21T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-pub"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1003",
+    "internet_reachable": true,
+    "likely_exploitable": true,
+    "members": [
+     "floor-v4"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2026-12-21T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1004",
+    "internet_reachable": false,
+    "likely_exploitable": false,
+    "members": [
+     "floor-nirv"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-05-14T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1005",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "pred-hi"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-03-11T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1006",
+    "internet_reachable": false,
+    "likely_exploitable": false,
+    "members": [
+     "pred-lo"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-05-14T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1007",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "pred-at"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-03-11T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1008",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "no-score"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-03-11T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1009",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "observed"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-03-11T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1010",
+    "internet_reachable": true,
+    "likely_exploitable": false,
+    "members": [
+     "irv-unresolved"
+    ],
+    "open_members": 1,
+    "pain": "N5",
+    "remediation_due_at": "2026-11-19T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-pkg"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1011",
+    "internet_reachable": true,
+    "likely_exploitable": false,
+    "members": [
+     "irv-package"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-05-14T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-pub"
+    ],
+    "dispositions": [
+     "mitigated"
+    ],
+    "group_id": "cve:CVE-0000-1012",
+    "internet_reachable": null,
+    "likely_exploitable": null,
+    "members": [
+     "m-full"
+    ],
+    "open_members": 0,
+    "pain": null,
+    "remediation_due_at": null
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-pub"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1013",
+    "internet_reachable": false,
+    "likely_exploitable": false,
+    "members": [
+     "m-nirv"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-05-14T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1014",
+    "internet_reachable": false,
+    "likely_exploitable": false,
+    "members": [
+     "m-nlev"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-05-14T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1015",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "m-nlev-kev"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-03-11T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-pub"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1016",
+    "internet_reachable": true,
+    "likely_exploitable": true,
+    "members": [
+     "m-void"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2026-11-21T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-pub"
+    ],
+    "dispositions": [
+     "mitigated"
+    ],
+    "group_id": "cve:CVE-0000-1017",
+    "internet_reachable": null,
+    "likely_exploitable": null,
+    "members": [
+     "fm-flag"
+    ],
+    "open_members": 0,
+    "pain": null,
+    "remediation_due_at": null
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1020",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "r-mitigated-ok"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-03-11T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1021",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "r-mitigated-none"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-03-11T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1022",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "r-mitigated-other"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-03-11T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "mitigated"
+    ],
+    "group_id": "cve:CVE-0000-1023",
+    "internet_reachable": null,
+    "likely_exploitable": null,
+    "members": [
+     "r-mitigated-full"
+    ],
+    "open_members": 0,
+    "pain": null,
+    "remediation_due_at": null
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1024",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "r-fp-control"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-03-11T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1025",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "r-lapsed"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-03-11T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1026",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "r-vendor-ok"
+    ],
+    "open_members": 1,
+    "pain": "N3",
+    "remediation_due_at": "2026-08-27T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1027",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "r-vendor-fixed"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-03-11T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1028",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "r-vendor-unknown"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-03-11T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1029",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "r-unknown-term"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-03-11T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1030",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "r-bad-date"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-03-11T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1031",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "r-investigating"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-03-11T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "operational-requirement"
+    ],
+    "group_id": "cve:CVE-0000-1032",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "r-oprq"
+    ],
+    "open_members": 0,
+    "pain": "N2",
+    "remediation_due_at": "2026-02-04T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1033",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "r-accepted-noref"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-03-11T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-pub"
+    ],
+    "dispositions": [
+     "false-positive"
+    ],
+    "group_id": "cve:CVE-0000-1034",
+    "internet_reachable": null,
+    "likely_exploitable": null,
+    "members": [
+     "r-fp"
+    ],
+    "open_members": 0,
+    "pain": null,
+    "remediation_due_at": null
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "operational-requirement"
+    ],
+    "group_id": "cve:CVE-0000-1035",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "r-no-review-by"
+    ],
+    "open_members": 0,
+    "pain": "N2",
+    "remediation_due_at": "2027-03-11T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1036",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "r-config-ignored"
+    ],
+    "open_members": 1,
+    "pain": "N3",
+    "remediation_due_at": "2026-12-05T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-pub"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1040",
+    "internet_reachable": true,
+    "likely_exploitable": true,
+    "members": [
+     "n5-block"
+    ],
+    "open_members": 1,
+    "pain": "N3",
+    "remediation_due_at": "2026-11-18T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1041",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "overdue"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2026-10-12T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1042",
+    "internet_reachable": false,
+    "likely_exploitable": false,
+    "members": [
+     "mav"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2026-10-26T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1043",
+    "internet_reachable": false,
+    "likely_exploitable": false,
+    "members": [
+     "likely-overdue"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2026-11-07T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-pub"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1044",
+    "internet_reachable": true,
+    "likely_exploitable": true,
+    "members": [
+     "likely-overdue-short"
+    ],
+    "open_members": 1,
+    "pain": "N3",
+    "remediation_due_at": "2026-11-05T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1045",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "legacy-id"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-01-10T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1046",
+    "internet_reachable": false,
+    "likely_exploitable": true,
+    "members": [
+     "detected-earlier"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2027-03-11T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1050",
+    "internet_reachable": true,
+    "likely_exploitable": true,
+    "members": [
+     "ovr",
+     "ovr-excluded",
+     "ovr-selector-miss"
+    ],
+    "open_members": 3,
+    "pain": "N5",
+    "remediation_due_at": "2026-11-05T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1051",
+    "internet_reachable": true,
+    "likely_exploitable": true,
+    "members": [
+     "ovr-lapsed"
+    ],
+    "open_members": 1,
+    "pain": "N5",
+    "remediation_due_at": "2026-11-05T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1052",
+    "internet_reachable": true,
+    "likely_exploitable": true,
+    "members": [
+     "ovr-kev"
+    ],
+    "open_members": 1,
+    "pain": "N5",
+    "remediation_due_at": "2026-11-05T12:00:00+00:00"
+   },
+   {
+    "basis": "cve",
+    "components": [],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:CVE-0000-1053",
+    "internet_reachable": true,
+    "likely_exploitable": true,
+    "members": [
+     "ovr-raise"
+    ],
+    "open_members": 1,
+    "pain": "N1",
+    "remediation_due_at": null
+   },
+   {
+    "basis": "cve",
+    "components": [
+     "cmp-edge"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "cve:ZAP-1",
+    "internet_reachable": true,
+    "likely_exploitable": true,
+    "members": [
+     "irv-observed"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2026-12-21T12:00:00+00:00"
+   },
+   {
+    "basis": "decision",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "false-positive"
+    ],
+    "group_id": "decision:DEC-003",
+    "internet_reachable": null,
+    "likely_exploitable": null,
+    "members": [
+     "c-fp"
+    ],
+    "open_members": 0,
+    "pain": null,
+    "remediation_due_at": null
+   },
+   {
+    "basis": "decision",
+    "components": [
+     "cmp-int"
+    ],
+    "dispositions": [
+     "false-positive"
+    ],
+    "group_id": "decision:DEC-004",
+    "internet_reachable": null,
+    "likely_exploitable": null,
+    "members": [
+     "c-fp-norecord"
+    ],
+    "open_members": 0,
+    "pain": null,
+    "remediation_due_at": null
+   },
+   {
+    "basis": "decision",
+    "components": [
+     "cmp-app"
+    ],
+    "dispositions": [
+     "risk-accepted"
+    ],
+    "group_id": "decision:DEC-007",
+    "internet_reachable": true,
+    "likely_exploitable": true,
+    "members": [
+     "c-ra"
+    ],
+    "open_members": 0,
+    "pain": "N2",
+    "remediation_due_at": "2026-09-22T12:00:00+00:00"
+   },
+   {
+    "basis": "decision",
+    "components": [
+     "cmp-app"
+    ],
+    "dispositions": [
+     "open"
+    ],
+    "group_id": "decision:DEC-009",
+    "internet_reachable": true,
+    "likely_exploitable": true,
+    "members": [
+     "c-ra-lapsed"
+    ],
+    "open_members": 1,
+    "pain": "N2",
+    "remediation_due_at": "2026-12-21T12:00:00+00:00"
+   },
+   {
+    "basis": "decision",
+    "components": [
+     "cmp-app"
+    ],
+    "dispositions": [
+     "risk-accepted"
+    ],
+    "group_id": "decision:DEC-010",
+    "internet_reachable": true,
+    "likely_exploitable": true,
+    "members": [
+     "c-ra-tfsec"
+    ],
+    "open_members": 0,
+    "pain": "N2",
+    "remediation_due_at": "2026-12-21T12:00:00+00:00"
+   }
+  ],
+  "impact_level": "Moderate",
+  "ksi_signal_ref": "/.well-known/ksi-signal.json",
+  "report_version": "2.0.0",
+  "risk_accepted": [
+   {
+    "completed_evaluation": "2026-11-03T12:00:00+00:00",
+    "component_id": null,
+    "current_disposition": "risk-accepted",
+    "cvss_vector": null,
+    "decision_id": "DEC-007",
+    "explanation": "",
+    "first_detected": "2026-11-03T12:00:00+00:00",
+    "first_evaluated": "2026-11-03T12:00:00+00:00",
+    "internet_reachable": true,
+    "irv_basis": "unresolved",
+    "is_kev": false,
+    "lev_basis": "no-score",
+    "likely_exploitable": true,
+    "pain": "N2",
+    "resource": ".checkov.yaml",
+    "source": "checkov-suppression",
+    "title": "",
+    "tool_id": "CKV_AWS_68",
+    "tracking_id": "CKV_AWS_68",
+    "vector_source": null
+   },
+   {
+    "completed_evaluation": "2026-11-03T12:00:00+00:00",
+    "component_id": "cmp-int",
+    "current_disposition": "risk-accepted",
     "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N",
     "decision_id": null,
     "explanation": "",
@@ -5239,6 +11331,7 @@
   "summary": {
    "blocking": 8,
    "by_pain": {
+    "N0": 0,
     "N1": 4,
     "N2": 34,
     "N3": 4,
@@ -5266,6 +11359,42 @@
    ],
    "unresolved_components": 6
   },
-  "system_id": "urn:samaydlette:website-prod"
+  "system_id": "urn:samaydlette:website-prod",
+  "withheld_detail_exercise": {
+   "asks": "The withheld detail of every finding the public report summarizes, please. In triplicate.",
+   "cannedFinding": false,
+   "decision": "DEC-182",
+   "deliveredTo": "nobody: the requester is simulated; this log entry records what would be supplied (field names and a sha256 of the detail), never the detail",
+   "engagement": "Simulated (DEC-194): no real FedRAMP, agency or person took part, and nothing was sent to anyone.",
+   "findings": [
+    {
+     "detailSha256": "6463ea700d739ed284f679ba7d38d4255b5392bf93aef8420f31915e95b3ff4f",
+     "tracking_id": "n5-block",
+     "withheldFields": []
+    },
+    {
+     "detailSha256": "6463ea700d739ed284f679ba7d38d4255b5392bf93aef8420f31915e95b3ff4f",
+     "tracking_id": "likely-overdue-short",
+     "withheldFields": []
+    },
+    {
+     "detailSha256": "6463ea700d739ed284f679ba7d38d4255b5392bf93aef8420f31915e95b3ff4f",
+     "tracking_id": "ovr-lapsed",
+     "withheldFields": []
+    },
+    {
+     "detailSha256": "6463ea700d739ed284f679ba7d38d4255b5392bf93aef8420f31915e95b3ff4f",
+     "tracking_id": "ovr-excluded",
+     "withheldFields": []
+    },
+    {
+     "detailSha256": "6463ea700d739ed284f679ba7d38d4255b5392bf93aef8420f31915e95b3ff4f",
+     "tracking_id": "ovr-kev",
+     "withheldFields": []
+    }
+   ],
+   "requester": "Necessary Party, Esq. (simulated)",
+   "simulated": true
+  }
  }
 }
diff --git a/tests/fixtures/vdr-monthly/activities-ends-before-start.json b/tests/fixtures/vdr-monthly/activities-ends-before-start.json
new file mode 100644
index 00000000..eb004d6d
--- /dev/null
+++ b/tests/fixtures/vdr-monthly/activities-ends-before-start.json
@@ -0,0 +1,40 @@
+{
+  "$schema": "../infrastructure/schemas/vdr-activities.schema.json",
+  "schema": "vdr-activities/1",
+  "$comment": "Vulnerability detection and response activity that happens outside the pipeline (VER-RPT-HLO): vulnerability disclosure reports received, bug bounty reports, penetration tests, assessments and manual scans. The operator records each one here when it happens; scripts/build-vdr-monthly.py lists it in the month it happened, and states 'none this period' for each kind with no entry. A kind with no entries in a month means none was recorded, so a report received and not recorded here is a gap in the record. The two seed entries were AI-drafted from the repository on 2026-11-05 (docs/security-review.md; DEC-039 and DEC-040) for the operator's review.",
+  "programs": {
+    "vdp": {
+      "active": true,
+      "note": "reports to the contact in /.well-known/security.txt"
+    },
+    "bug-bounty": {
+      "active": false,
+      "note": "no bug bounty program"
+    },
+    "penetration-testing": {
+      "active": false,
+      "note": "no penetration test has been performed or scheduled"
+    }
+  },
+  "activities": [
+    {
+      "id": "ACT-001",
+      "kind": "assessment",
+      "date": "2026-05-08",
+      "performed_by": "Sam Aydlette (operator; self-performed)",
+      "summary": "Independent-assessment-style external assessment, self-performed; findings SAR-001 to SAR-009",
+      "evidence": "docs/security-review.md (2026-Q2 quarterly review)",
+      "recorded_by": "AI-drafted from the repository, 2026-11-05; for the operator's confirmation"
+    },
+    {
+      "id": "ACT-002",
+      "kind": "manual-scan",
+      "date": "2026-10-26",
+      "end_date": "2026-10-01",
+      "performed_by": "Sam Aydlette (operator)",
+      "summary": "Manual OWASP ZAP scans of https://samaydlette.com; alerts 10099 and 10036-2 assessed as false positives",
+      "evidence": "data/decisions.json DEC-039, DEC-040 (original_detection_date 2026-10-26)",
+      "recorded_by": "AI-drafted from the repository, 2026-11-05; for the operator's confirmation"
+    }
+  ]
+}
diff --git a/tests/fixtures/vdr-monthly/activities-missing-program.json b/tests/fixtures/vdr-monthly/activities-missing-program.json
new file mode 100644
index 00000000..b757c11b
--- /dev/null
+++ b/tests/fixtures/vdr-monthly/activities-missing-program.json
@@ -0,0 +1,36 @@
+{
+  "$schema": "../infrastructure/schemas/vdr-activities.schema.json",
+  "schema": "vdr-activities/1",
+  "$comment": "Vulnerability detection and response activity that happens outside the pipeline (VER-RPT-HLO): vulnerability disclosure reports received, bug bounty reports, penetration tests, assessments and manual scans. The operator records each one here when it happens; scripts/build-vdr-monthly.py lists it in the month it happened, and states 'none this period' for each kind with no entry. A kind with no entries in a month means none was recorded, so a report received and not recorded here is a gap in the record. The two seed entries were AI-drafted from the repository on 2026-11-05 (docs/security-review.md; DEC-039 and DEC-040) for the operator's review.",
+  "programs": {
+    "vdp": {
+      "active": true,
+      "note": "reports to the contact in /.well-known/security.txt"
+    },
+    "penetration-testing": {
+      "active": false,
+      "note": "no penetration test has been performed or scheduled"
+    }
+  },
+  "activities": [
+    {
+      "id": "ACT-001",
+      "kind": "assessment",
+      "date": "2026-05-08",
+      "performed_by": "Sam Aydlette (operator; self-performed)",
+      "summary": "Independent-assessment-style external assessment, self-performed; findings SAR-001 to SAR-009",
+      "evidence": "docs/security-review.md (2026-Q2 quarterly review)",
+      "recorded_by": "AI-drafted from the repository, 2026-11-05; for the operator's confirmation"
+    },
+    {
+      "id": "ACT-002",
+      "kind": "manual-scan",
+      "date": "2026-10-26",
+      "end_date": "2026-10-27",
+      "performed_by": "Sam Aydlette (operator)",
+      "summary": "Manual OWASP ZAP scans of https://samaydlette.com; alerts 10099 and 10036-2 assessed as false positives",
+      "evidence": "data/decisions.json DEC-039, DEC-040 (original_detection_date 2026-10-26)",
+      "recorded_by": "AI-drafted from the repository, 2026-11-05; for the operator's confirmation"
+    }
+  ]
+}
diff --git a/tests/fixtures/vdr-monthly/activities-unknown-kind.json b/tests/fixtures/vdr-monthly/activities-unknown-kind.json
new file mode 100644
index 00000000..665f61d0
--- /dev/null
+++ b/tests/fixtures/vdr-monthly/activities-unknown-kind.json
@@ -0,0 +1,40 @@
+{
+  "$schema": "../infrastructure/schemas/vdr-activities.schema.json",
+  "schema": "vdr-activities/1",
+  "$comment": "Vulnerability detection and response activity that happens outside the pipeline (VER-RPT-HLO): vulnerability disclosure reports received, bug bounty reports, penetration tests, assessments and manual scans. The operator records each one here when it happens; scripts/build-vdr-monthly.py lists it in the month it happened, and states 'none this period' for each kind with no entry. A kind with no entries in a month means none was recorded, so a report received and not recorded here is a gap in the record. The two seed entries were AI-drafted from the repository on 2026-11-05 (docs/security-review.md; DEC-039 and DEC-040) for the operator's review.",
+  "programs": {
+    "vdp": {
+      "active": true,
+      "note": "reports to the contact in /.well-known/security.txt"
+    },
+    "bug-bounty": {
+      "active": false,
+      "note": "no bug bounty program"
+    },
+    "penetration-testing": {
+      "active": false,
+      "note": "no penetration test has been performed or scheduled"
+    }
+  },
+  "activities": [
+    {
+      "id": "ACT-001",
+      "kind": "tabletop",
+      "date": "2026-05-08",
+      "performed_by": "Sam Aydlette (operator; self-performed)",
+      "summary": "Independent-assessment-style external assessment, self-performed; findings SAR-001 to SAR-009",
+      "evidence": "docs/security-review.md (2026-Q2 quarterly review)",
+      "recorded_by": "AI-drafted from the repository, 2026-11-05; for the operator's confirmation"
+    },
+    {
+      "id": "ACT-002",
+      "kind": "manual-scan",
+      "date": "2026-10-26",
+      "end_date": "2026-10-27",
+      "performed_by": "Sam Aydlette (operator)",
+      "summary": "Manual OWASP ZAP scans of https://samaydlette.com; alerts 10099 and 10036-2 assessed as false positives",
+      "evidence": "data/decisions.json DEC-039, DEC-040 (original_detection_date 2026-10-26)",
+      "recorded_by": "AI-drafted from the repository, 2026-11-05; for the operator's confirmation"
+    }
+  ]
+}
diff --git a/tests/fixtures/vdr-monthly/parity-activities-f0e4aef.json b/tests/fixtures/vdr-monthly/parity-activities-f0e4aef.json
new file mode 100644
index 00000000..58ec4d47
--- /dev/null
+++ b/tests/fixtures/vdr-monthly/parity-activities-f0e4aef.json
@@ -0,0 +1,40 @@
+{
+  "$schema": "../infrastructure/schemas/vdr-activities.schema.json",
+  "schema": "vdr-activities/1",
+  "$comment": "Vulnerability detection and response activity that happens outside the pipeline (VER-RPT-HLO): vulnerability disclosure reports received, bug bounty reports, penetration tests, assessments and manual scans. The operator records each one here when it happens; scripts/build-vdr-monthly.py lists it in the month it happened, and states 'none this period' for each kind with no entry. A kind with no entries in a month means none was recorded, so a report received and not recorded here is a gap in the record. The two seed entries were AI-drafted from the repository on 2026-11-05 (docs/security-review.md; DEC-039 and DEC-040) for the operator's review.",
+  "programs": {
+    "vdp": {
+      "active": true,
+      "note": "reports to the contact in /.well-known/security.txt"
+    },
+    "bug-bounty": {
+      "active": false,
+      "note": "no bug bounty program"
+    },
+    "penetration-testing": {
+      "active": false,
+      "note": "no penetration test has been performed or scheduled"
+    }
+  },
+  "activities": [
+    {
+      "id": "ACT-001",
+      "kind": "assessment",
+      "date": "2026-05-08",
+      "performed_by": "Sam Aydlette (operator; self-performed)",
+      "summary": "Independent-assessment-style external assessment, self-performed; findings SAR-001 to SAR-009",
+      "evidence": "docs/security-review.md (2026-Q2 quarterly review)",
+      "recorded_by": "AI-drafted from the repository, 2026-11-05; for the operator's confirmation"
+    },
+    {
+      "id": "ACT-002",
+      "kind": "manual-scan",
+      "date": "2026-10-26",
+      "end_date": "2026-10-27",
+      "performed_by": "Sam Aydlette (operator)",
+      "summary": "Manual OWASP ZAP scans of https://samaydlette.com; alerts 10099 and 10036-2 assessed as false positives",
+      "evidence": "data/decisions.json DEC-039, DEC-040 (original_detection_date 2026-10-26)",
+      "recorded_by": "AI-drafted from the repository, 2026-11-05; for the operator's confirmation"
+    }
+  ]
+}
diff --git a/tests/fixtures/vdr-monthly/parity-before-f0e4aef.json b/tests/fixtures/vdr-monthly/parity-before-f0e4aef.json
new file mode 100644
index 00000000..8d9d498c
--- /dev/null
+++ b/tests/fixtures/vdr-monthly/parity-before-f0e4aef.json
@@ -0,0 +1,320 @@
+{
+ "generatedAt": "2026-11-20T12:00:00+00:00",
+ "overview": [
+  {
+   "failedRuns": 0,
+   "lastRun": "2026-11-20T06:00:00+00:00",
+   "runsInPeriod": 1,
+   "summary": "1 in period",
+   "title": "Software composition analysis (Grype over every dependency tree; Dependabot alerts)",
+   "type": "sca"
+  },
+  {
+   "failedRuns": 0,
+   "lastRun": "2026-11-20T06:00:00+00:00",
+   "runsInPeriod": 1,
+   "summary": "1 in period",
+   "title": "Infrastructure-as-code static analysis (Checkov, tfsec)",
+   "type": "iac-sast"
+  },
+  {
+   "failedRuns": 0,
+   "lastRun": null,
+   "runsInPeriod": 0,
+   "summary": "none this period",
+   "title": "Code static analysis (CodeQL)",
+   "type": "code-sast"
+  },
+  {
+   "failedRuns": 0,
+   "lastRun": null,
+   "runsInPeriod": 0,
+   "summary": "none this period",
+   "title": "Dynamic scan of the public site (OWASP ZAP)",
+   "type": "dast-site"
+  },
+  {
+   "failedRuns": 0,
+   "lastRun": null,
+   "runsInPeriod": 0,
+   "summary": "none this period",
+   "title": "Authenticated dynamic scan of the Silk Reeling API",
+   "type": "dast-api"
+  },
+  {
+   "failedRuns": 0,
+   "lastRun": "2026-11-19T20:00:00+00:00",
+   "runsInPeriod": 1,
+   "summary": "1 in period",
+   "title": "Known-exploited and exploit-prediction feeds (CISA KEV, FIRST EPSS)",
+   "type": "threat-intel"
+  },
+  {
+   "failedRuns": 0,
+   "lastRun": null,
+   "runsInPeriod": 0,
+   "summary": "none this period",
+   "title": "Runtime verification and validation of machine resources",
+   "type": "runtime-vv"
+  },
+  {
+   "failedRuns": 0,
+   "lastRun": "2026-11-05T07:00:00+00:00",
+   "runsInPeriod": 1,
+   "summary": "1 in period",
+   "title": "Verification and validation of non-machine resources (machine checks, nightly)",
+   "type": "non-machine-vv"
+  },
+  {
+   "failedRuns": 0,
+   "lastRun": null,
+   "program": {
+    "active": true,
+    "note": "reports to the contact in /.well-known/security.txt"
+   },
+   "runsInPeriod": 0,
+   "summary": "none this period",
+   "title": "Vulnerability disclosure program: reports received",
+   "type": "vdp"
+  },
+  {
+   "failedRuns": 0,
+   "lastRun": null,
+   "program": {
+    "active": false,
+    "note": "no bug bounty program"
+   },
+   "runsInPeriod": 0,
+   "summary": "none this period",
+   "title": "Bug bounty program",
+   "type": "bug-bounty"
+  },
+  {
+   "failedRuns": 0,
+   "lastRun": null,
+   "program": {
+    "active": false,
+    "note": "no penetration test has been performed or scheduled"
+   },
+   "runsInPeriod": 0,
+   "summary": "none this period",
+   "title": "Penetration testing",
+   "type": "pentest"
+  },
+  {
+   "failedRuns": 0,
+   "lastRun": null,
+   "runsInPeriod": 0,
+   "summary": "none this period",
+   "title": "Assessments",
+   "type": "assessment"
+  }
+ ],
+ "period": {
+  "from": "2026-11-01T00:00:00+00:00",
+  "month": "2026-11",
+  "to": "2026-11-20T12:00:00+00:00"
+ },
+ "previousMonths": [],
+ "response": {
+  "counts": {
+   "decisionsClosed": 2,
+   "decisionsRecorded": 25,
+   "detections": 0,
+   "evaluations": 0,
+   "noLongerReported": 0,
+   "ratingChanges": 0,
+   "reductions": 0,
+   "remediations": 2,
+   "runtimeFailuresInPeriod": 0,
+   "runtimeRunsInPeriod": 0,
+   "scansInPeriod": 3
+  },
+  "decisionsClosed": [
+   {
+    "decisionId": "DEC-034",
+    "disposition": "remediated",
+    "on": "2026-11-03"
+   },
+   {
+    "decisionId": "DEC-035",
+    "disposition": "remediated",
+    "on": "2026-11-03"
+   }
+  ],
+  "decisionsRecorded": [
+   {
+    "decisionId": "DEC-039",
+    "disposition": "false-positive",
+    "on": "2026-11-04"
+   },
+   {
+    "decisionId": "DEC-040",
+    "disposition": "false-positive",
+    "on": "2026-11-04"
+   },
+   {
+    "decisionId": "DEC-100",
+    "disposition": "operational-requirement",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-101",
+    "disposition": "operational-requirement",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-102",
+    "disposition": "superseded",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-103",
+    "disposition": "superseded",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-104",
+    "disposition": "superseded",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-105",
+    "disposition": "superseded",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-106",
+    "disposition": "superseded",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-107",
+    "disposition": "operational-requirement",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-150",
+    "disposition": "accepted",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-151",
+    "disposition": "operational-requirement",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-152",
+    "disposition": "accepted",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-160",
+    "disposition": "operational-requirement",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-165",
+    "disposition": "operational-requirement",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-166",
+    "disposition": "operational-requirement",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-167",
+    "disposition": "operational-requirement",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-180",
+    "disposition": "operational-requirement",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-181",
+    "disposition": "operational-requirement",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-182",
+    "disposition": "operational-requirement",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-190",
+    "disposition": "superseded",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-191",
+    "disposition": "superseded",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-192",
+    "disposition": "superseded",
+    "on": "2026-11-05"
+   },
+   {
+    "decisionId": "DEC-193",
+    "disposition": "false-positive",
+    "on": "2026-11-06"
+   },
+   {
+    "decisionId": "DEC-194",
+    "disposition": "operational-requirement",
+    "on": "2026-11-06"
+   }
+  ],
+  "remediations": [
+   "DEC-034",
+   "DEC-035"
+  ]
+ },
+ "rules": [
+  "VER-TFR-MHR",
+  "VER-RPT-HLO",
+  "VER-RPT-PER"
+ ],
+ "runs": [
+  {
+   "at": "2026-11-20T06:00:00+00:00",
+   "count": 3,
+   "source": "checkov (checkov-results.sarif)",
+   "status": "ok",
+   "type": "iac-sast"
+  },
+  {
+   "at": "2026-11-05T07:00:00+00:00",
+   "count": 1,
+   "source": "machine checks (1 resources)",
+   "status": "ok",
+   "type": "non-machine-vv"
+  },
+  {
+   "at": "2026-11-20T06:00:00+00:00",
+   "count": 0,
+   "source": "grype (grype-python.json)",
+   "status": "ok",
+   "type": "sca"
+  },
+  {
+   "at": "2026-11-19T20:00:00+00:00",
+   "count": 9,
+   "source": "kev (kev-catalog.json)",
+   "status": "ok",
+   "type": "threat-intel"
+  }
+ ],
+ "runtimeRunsBasis": "latest run only: the runtime emitter publishes only its latest run, so a run replaced between two nightly builds is not counted; the VDR build recorded no verified runtime run",
+ "schema": "vdr-monthly/1",
+ "source": {
+  "activities": "data/vdr-activities.json",
+  "ksiSignalId": "k1",
+  "nonMachine": "vdr-non-machine-vv.json",
+  "vdrReportId": "r1"
+ }
+}
diff --git a/tests/fixtures/vvk/runtime-previous-commit.json b/tests/fixtures/vvk/runtime-previous-commit.json
new file mode 100644
index 00000000..77a36f8c
--- /dev/null
+++ b/tests/fixtures/vvk/runtime-previous-commit.json
@@ -0,0 +1,9 @@
+{
+ "provenance": {
+  "source": {
+   "repository": "sam-aydlette/samaydlette.com",
+   "commit": "bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb"
+  }
+ },
+ "validations": []
+}
diff --git a/tests/fixtures/vvk/runtime-this-commit.json b/tests/fixtures/vvk/runtime-this-commit.json
new file mode 100644
index 00000000..31dc7446
--- /dev/null
+++ b/tests/fixtures/vvk/runtime-this-commit.json
@@ -0,0 +1,9 @@
+{
+ "provenance": {
+  "source": {
+   "repository": "sam-aydlette/samaydlette.com",
+   "commit": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
+  }
+ },
+ "validations": []
+}
diff --git a/tests/fixtures/vvk/vdr-good.json b/tests/fixtures/vvk/vdr-good.json
new file mode 100644
index 00000000..866bfc56
--- /dev/null
+++ b/tests/fixtures/vvk/vdr-good.json
@@ -0,0 +1,28 @@
+{
+  "_note": "FRC-CSX-VVK: a VDR that counts as dependency scanning (bound, fresh, every Grype scan ok).",
+  "ksi_signal_id": "sig-1",
+  "emitted_at": "2026-11-05T06:00:00+00:00",
+  "methodology": {
+    "detection": {
+      "schema": "detection/1",
+      "result": "ok",
+      "feeds": [
+        {
+          "feed": "grype",
+          "file": "grype-python.json",
+          "status": "ok"
+        },
+        {
+          "feed": "grype",
+          "file": "grype-js.json",
+          "status": "ok"
+        },
+        {
+          "feed": "kev",
+          "file": "kev-catalog.json",
+          "status": "ok"
+        }
+      ]
+    }
+  }
+}
diff --git a/tests/fixtures/vvk/vdr-grype-failed.json b/tests/fixtures/vvk/vdr-grype-failed.json
new file mode 100644
index 00000000..c72c2cf6
--- /dev/null
+++ b/tests/fixtures/vvk/vdr-grype-failed.json
@@ -0,0 +1,24 @@
+{
+  "_note": "Known bad: a Grype scan failed the detection gate.",
+  "ksi_signal_id": "sig-1",
+  "emitted_at": "2026-11-05T06:00:00+00:00",
+  "methodology": {
+    "detection": {
+      "schema": "detection/1",
+      "result": "ok",
+      "feeds": [
+        {
+          "feed": "grype",
+          "file": "grype-python.json",
+          "status": "ok"
+        },
+        {
+          "feed": "grype",
+          "file": "grype-js.json",
+          "status": "failed",
+          "problem": "DB too old"
+        }
+      ]
+    }
+  }
+}
diff --git a/tests/fixtures/vvk/vdr-no-grype.json b/tests/fixtures/vvk/vdr-no-grype.json
new file mode 100644
index 00000000..c32e1368
--- /dev/null
+++ b/tests/fixtures/vvk/vdr-no-grype.json
@@ -0,0 +1,18 @@
+{
+  "_note": "Known bad: the detection record lists no Grype scan.",
+  "ksi_signal_id": "sig-1",
+  "emitted_at": "2026-11-05T06:00:00+00:00",
+  "methodology": {
+    "detection": {
+      "schema": "detection/1",
+      "result": "ok",
+      "feeds": [
+        {
+          "feed": "kev",
+          "file": "kev-catalog.json",
+          "status": "ok"
+        }
+      ]
+    }
+  }
+}
diff --git a/tests/fixtures/vvk/vdr-stale.json b/tests/fixtures/vvk/vdr-stale.json
new file mode 100644
index 00000000..d37ae5bd
--- /dev/null
+++ b/tests/fixtures/vvk/vdr-stale.json
@@ -0,0 +1,28 @@
+{
+  "_note": "Known bad: emitted outside the 24-hour window.",
+  "ksi_signal_id": "sig-1",
+  "emitted_at": "2026-11-03T06:00:00+00:00",
+  "methodology": {
+    "detection": {
+      "schema": "detection/1",
+      "result": "ok",
+      "feeds": [
+        {
+          "feed": "grype",
+          "file": "grype-python.json",
+          "status": "ok"
+        },
+        {
+          "feed": "grype",
+          "file": "grype-js.json",
+          "status": "ok"
+        },
+        {
+          "feed": "kev",
+          "file": "kev-catalog.json",
+          "status": "ok"
+        }
+      ]
+    }
+  }
+}
diff --git a/tests/fixtures/vvk/vdr-unbound.json b/tests/fixtures/vvk/vdr-unbound.json
new file mode 100644
index 00000000..84bda8fc
--- /dev/null
+++ b/tests/fixtures/vvk/vdr-unbound.json
@@ -0,0 +1,28 @@
+{
+  "_note": "Known bad: bound to another inventory.",
+  "ksi_signal_id": "sig-other",
+  "emitted_at": "2026-11-05T06:00:00+00:00",
+  "methodology": {
+    "detection": {
+      "schema": "detection/1",
+      "result": "ok",
+      "feeds": [
+        {
+          "feed": "grype",
+          "file": "grype-python.json",
+          "status": "ok"
+        },
+        {
+          "feed": "grype",
+          "file": "grype-js.json",
+          "status": "ok"
+        },
+        {
+          "feed": "kev",
+          "file": "kev-catalog.json",
+          "status": "ok"
+        }
+      ]
+    }
+  }
+}
diff --git a/tests/fixtures/wellknown-headers/known-bad.json b/tests/fixtures/wellknown-headers/known-bad.json
new file mode 100644
index 00000000..f5e93822
--- /dev/null
+++ b/tests/fixtures/wellknown-headers/known-bad.json
@@ -0,0 +1,4 @@
+{
+  "ksi-signal.json": {"Content-Type": "application/json", "X-Content-Type-Options": "nosniff"},
+  "security-decision-record.json": {"Content-Type": "application/json", "Access-Control-Allow-Origin": "*", "X-Content-Type-Options": "nosniff"}
+}
diff --git a/tests/fixtures/wellknown-headers/known-good.json b/tests/fixtures/wellknown-headers/known-good.json
new file mode 100644
index 00000000..19a9e4f3
--- /dev/null
+++ b/tests/fixtures/wellknown-headers/known-good.json
@@ -0,0 +1,4 @@
+{
+  "ksi-signal.json": {"content-type": "application/json", "access-control-allow-origin": "*", "x-content-type-options": "nosniff"},
+  "ksi-signal.schema.json": {"Content-Type": "application/schema+json", "Access-Control-Allow-Origin": "*", "X-Content-Type-Options": "nosniff"}
+}
diff --git a/tests/fixtures/workflows/cosign-not-installed.yml b/tests/fixtures/workflows/cosign-not-installed.yml
new file mode 100644
index 00000000..c52e63b8
--- /dev/null
+++ b/tests/fixtures/workflows/cosign-not-installed.yml
@@ -0,0 +1,10 @@
+name: known-bad
+on: workflow_dispatch
+jobs:
+  assess:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Install the assessor's tools
+      run: python3 -m pip install --user pytest
+    - name: Assess
+      run: python3 tools/simulated-assessor/assess.py --guide g.json
diff --git a/tests/test_agency_access.py b/tests/test_agency_access.py
new file mode 100644
index 00000000..3e694249
--- /dev/null
+++ b/tests/test_agency_access.py
@@ -0,0 +1,157 @@
+"""Agency access: inventory and history (CDS-TRC-AAI), request and withdrawal
+(CDS-TRC-SSM), access decided by code rules (CDS-UTC-AGA), and the
+five-business-day denial notice to the simulated FedRAMP by the automated
+notifier (CDS-UTC-AAD), exercised with plainly fictional agencies. No real
+agency or FedRAMP request is taken (DEC-194)."""
+import copy
+import importlib.util
+import json
+from datetime import date
+from pathlib import Path
+
+import pytest
+
+REPO = Path(__file__).resolve().parent.parent
+FIX = REPO / "tests" / "fixtures" / "agency-access"
+spec = importlib.util.spec_from_file_location("agency_access", REPO / "scripts" / "agency-access.py")
+aa = importlib.util.module_from_spec(spec)
+spec.loader.exec_module(aa)
+
+
+@pytest.mark.parametrize("start,n,expected", [
+    (date(2026, 11, 25), 5, date(2026, 12, 3)),   # Thanksgiving (Thu 26 Nov) is skipped
+    (date(2026, 12, 23), 5, date(2026, 12, 31)),  # Christmas (Fri 25 Dec)
+    (date(2027, 7, 1), 2, date(2027, 7, 6)),      # 4 July 2027 is a Sunday, observed Monday 5 July
+    (date(2026, 11, 6), 1, date(2026, 11, 9)),    # Friday to Monday
+])
+def test_business_days_skip_weekends_and_federal_holidays(start, n, expected):
+    assert aa.add_business_days(start, n) == expected
+
+
+def test_known_bad_an_unnotified_denial_past_five_business_days_fails():
+    doc = aa.load(FIX / "overdue-denial.json")
+    assert aa.process(doc, date(2026, 11, 9))["problems"] == []          # last day of the window
+    assert aa.process(doc, date(2026, 11, 10))["problems"] == [
+        "AAR-B01: FedRAMP denial notice overdue (deadline 2026-11-09)"]
+    with pytest.raises(SystemExit):
+        aa.main(["validate", "--register", str(FIX / "overdue-denial.json"), "--today", "2026-11-10"])
+
+
+def test_known_bad_the_register_never_names_a_person():
+    with pytest.raises(SystemExit, match="not people"):
+        aa.load(FIX / "person-in-register.json")
+
+
+def test_inventory_and_history_follow_grants_and_withdrawals():
+    doc = aa.validate({"schema": "agency-access/1", "requests": [
+        {"id": "AAR-T1", "agency": "A (simulated)", "simulated": True, "system": "S1", "kind": "access",
+         "channel": "form",
+         "received_on": "2026-11-02", "decision": "granted", "decided_on": "2026-11-03", "decided_by": "Operator"},
+        {"id": "AAR-T2", "agency": "A (simulated)", "simulated": True, "kind": "withdrawal", "channel": "form",
+         "received_on": "2026-11-04", "withdraws": "AAR-T1"}]}, "t")
+    r = aa.process(doc, date(2026, 11, 5))
+    assert r["inventory"] == []
+    assert [h["event"] for h in r["history"]] == ["access received", "granted", "access withdrawn",
+                                                  "withdrawal received"]
+
+
+@pytest.mark.parametrize("bad", [
+    {"decision": "denied"},                                   # a denial with no reason or date
+    {"decision": "granted", "decided_on": "2026-11-01"},      # decided before received
+    {"fedramp_notified_on": "2026-11-03"},                    # notice with no denial
+])
+def test_invalid_records_fail(bad):
+    rec = {"id": "AAR-T1", "agency": "A (simulated)", "simulated": True, "kind": "access", "channel": "form",
+           "received_on": "2026-11-02", "decided_by": "Operator", **bad}
+    with pytest.raises(SystemExit):
+        aa.validate({"schema": "agency-access/1", "requests": [rec]}, "t")
+
+
+@pytest.mark.parametrize("today", ["2026-11-05", "2026-11-27", "2026-12-28", "2027-01-04", "2027-07-06"])
+def test_the_exercise_observes_every_expected_outcome_on_any_day(today):
+    scenario = json.loads(aa.SCENARIO.read_text())
+    _, _, mismatches = aa.exercise(scenario, date.fromisoformat(today))
+    assert mismatches == []
+
+
+def test_the_exercise_fails_when_an_outcome_is_not_the_expected_one():
+    scenario = copy.deepcopy(json.loads(aa.SCENARIO.read_text()))
+    scenario["expected"]["AAR-X07"] = "denial notice on time"   # the clock must catch it
+    _, _, mismatches = aa.exercise(scenario, date(2026, 11, 5))
+    assert mismatches == ["AAR-X07: expected 'denial notice on time', observed 'denial notice overdue'"]
+
+
+def test_the_exercise_agencies_are_obviously_fictional():
+    scenario = json.loads(aa.SCENARIO.read_text())
+    assert all(r["agency"].endswith("(simulated)") for r in scenario["requests"])
+    assert "SIMULATED" in scenario["disclaimer"] and "nothing is sent" in scenario["disclaimer"]
+
+
+def test_the_committed_register_is_valid_and_has_nothing_overdue():
+    doc = aa.load(aa.REGISTER)
+    assert aa.process(doc, date(2026, 11, 5))["problems"] == []
+
+
+def test_the_exercise_writes_a_log_that_says_it_is_simulated(tmp_path):
+    out, md = tmp_path / "log.json", tmp_path / "log.md"
+    assert aa.main(["exercise", "--output", str(out), "--md-output", str(md), "--today", "2026-11-05"]) == 0
+    log = json.loads(out.read_text())
+    assert log["simulated"] is True and log["counterparty"] == "agency"
+    assert {n["state"] for n in log["denial_notices"]} == {"on time", "pending", "late", "overdue"}
+    assert all("nothing is sent" in n["to"] for n in log["denial_notices"])
+    assert "Agency access exercise (simulated)" in md.read_text()
+
+
+# --- no engagement (DEC-194): simulated entries only, decided by rules ----------------------
+
+def test_known_bad_a_register_entry_not_marked_simulated_fails():
+    with pytest.raises(SystemExit, match="DEC-194"):
+        aa.load(FIX / "real-agency.json")
+    with pytest.raises(SystemExit, match="must be `simulated: true`"):
+        aa.main(["validate", "--register", str(FIX / "real-agency.json"), "--today", "2026-11-05"])
+
+
+def test_a_simulated_flag_on_a_real_sounding_agency_still_fails():
+    rec = {"id": "AAR-T1", "agency": "Bureau of Unmarked Requests", "simulated": True, "kind": "access",
+           "channel": "form", "received_on": "2026-11-02"}
+    with pytest.raises(SystemExit, match="DEC-194"):
+        aa.validate({"schema": "agency-access/1", "requests": [rec]}, "t")
+
+
+def test_the_committed_register_holds_no_real_entry():
+    doc = json.loads(aa.REGISTER.read_text())
+    assert all(r.get("simulated") is True and r["agency"].endswith("(simulated)") for r in doc["requests"])
+
+
+@pytest.mark.parametrize("asks,decision,rule", [
+    ("To be on record as reading the package.", "granted", "R0-public"),
+    ("Write access, please.", "denied", "R1-write"),
+    ("The package by fax.", "denied", "R2-channel"),
+    ("The raw logs.", "denied", "R3-nonpublic"),
+])
+def test_code_rules_decide_each_request(asks, decision, rule):
+    got = aa.decide({"asks": asks, "channel": "simulated request", "agency": "A (simulated)"})
+    assert got[:2] == (decision, rule) and (got[2] is None) == (decision == "granted")
+
+
+def test_the_scenario_carries_no_hand_made_decision():
+    scenario = json.loads(aa.SCENARIO.read_text())
+    assert not any({"decision", "decided_by", "decided_on_offset", "fedramp_notified_on_offset"} & set(r)
+                   for r in scenario["requests"])
+    doc, _, _ = aa.exercise(scenario, date(2026, 11, 5))
+    assert {r["decided_by"] for r in doc["requests"] if r.get("decision")} == {aa.DECIDER}
+
+
+def test_the_notifier_outage_leaves_a_denial_overdue_and_a_slow_queue_late():
+    denied = date(2026, 11, 2)
+    assert aa.notify(denied, None, date(2026, 12, 1)) is None
+    assert aa.notify(denied, 7, date(2026, 12, 1)) == "2026-11-12"   # Veterans Day skipped
+    assert aa.notify(denied, 4, date(2026, 11, 3)) is None      # not run yet: pending
+
+
+def test_the_exercise_log_carries_the_no_engagement_statement(tmp_path):
+    out = tmp_path / "log.json"
+    aa.main(["exercise", "--output", str(out), "--md-output", "", "--today", "2026-11-05"])
+    log = json.loads(out.read_text())
+    assert log["engagement"] == aa._engagement.STATEMENT
+    assert {n["rule"] for n in log["denial_notices"]} == {"R1-write", "R2-channel", "R3-nonpublic", "R4-unverifiable"}
diff --git a/tests/test_assessor_guide.py b/tests/test_assessor_guide.py
new file mode 100644
index 00000000..9ca10f69
--- /dev/null
+++ b/tests/test_assessor_guide.py
@@ -0,0 +1,75 @@
+"""The assessor guide (IVV-CSO-STE) and the sampling statement (IVV-CSO-DUS):
+every rule and KSI, every piece of evidence with a command to reproduce it and
+the same check in machine form, generated from the rule records."""
+import importlib.util
+import json
+import sys
+from datetime import datetime, timezone
+from pathlib import Path
+
+import pytest
+
+REPO = Path(__file__).resolve().parent.parent
+sys.path.insert(0, str(REPO / "scripts"))
+import _freshness  # noqa: E402
+import _frr  # noqa: E402
+import _rules  # noqa: E402
+
+spec = importlib.util.spec_from_file_location("assessor_guide", REPO / "scripts" / "build-assessor-guide.py")
+ag = importlib.util.module_from_spec(spec)
+spec.loader.exec_module(ag)
+
+FRESH = {x["path"]: x for x in _freshness.load_freshness_config(
+    REPO / "infrastructure" / "schemas" / "freshness-config.json")["artifacts"]}
+CATALOG = json.loads((REPO / "infrastructure" / "schemas" / "ksi-catalog.json").read_text())
+NOW = datetime(2026, 11, 5, tzinfo=timezone.utc)
+
+
+def _guide():
+    return ag.build(_frr.load(_frr.DEFAULT_PATH), _rules.applicable_provider_rules(), CATALOG, FRESH, NOW, "abc")
+
+
+def test_every_rule_and_ksi_is_in_the_guide_with_a_reproducible_check():
+    g = _guide()
+    assert {r["rule_id"] for r in g["rules"]} == set(_rules.applicable_provider_rules())
+    ksis = {i["id"] for f in CATALOG["KSI"].values() for i in f["indicators"]}
+    assert {k["ksi_id"] for k in g["ksis"]} == ksis
+    for r in g["rules"]:
+        assert r["statement"] and r["explanation"]
+        for ev in r["evidence"]:
+            assert ev["how_to_reproduce"] and set(ev["check"]) in ({"pytest"}, {"workflow", "step"}, {"artifact"}, {"decision"})
+
+
+def test_signed_artifacts_name_the_identity_that_signed_them():
+    g = _guide()
+    checks = [ev["check"]["artifact"] for r in g["rules"] for ev in r["evidence"] if ev["kind"] == "artifact"]
+    assert checks
+    for c in checks:
+        assert c["url"].startswith("https://samaydlette.com/.well-known/")
+        assert all(i in g["identities"] for i in c["identities"])
+    sim = ag._artifact_check(".well-known/simulated-assessment.json", FRESH)
+    assert sim["identities"] == ["assessor"] and sim["bundle_url"]
+
+
+def test_the_guide_states_that_no_samples_are_used():
+    g = _guide()
+    assert "No representative samples" in g["sampling"]
+    assert "## Sampling (IVV-CSO-DUS)" in ag.render_markdown(g)
+
+
+def test_known_bad_unknown_evidence_kind_fails():
+    records = json.loads((REPO / "tests" / "fixtures" / "assessor-guide" / "unknown-evidence-kind.json").read_text())
+    with pytest.raises(SystemExit, match="unknown evidence kind"):
+        ag.build(records, _rules.applicable_provider_rules(), CATALOG, FRESH, NOW)
+
+
+def test_an_artifact_outside_the_freshness_config_fails_closed():
+    with pytest.raises(SystemExit, match="not in the freshness config"):
+        ag.reproduce({"kind": "artifact", "ref": ".well-known/not-governed.json"}, FRESH)
+
+
+def test_the_deploy_builds_the_guide_and_the_assessor_follows_it():
+    deploy = (REPO / ".github" / "workflows" / "deploy-with-opa.yml").read_text()
+    assessor = (REPO / ".github" / "workflows" / "simulated-assessor.yml").read_text()
+    assert "- name: Build the assessor guide" in deploy
+    assert "build-assessor-guide.py" in assessor and "assess.py --guide assessor-guide.json" in assessor
diff --git a/tests/test_assessor_records.py b/tests/test_assessor_records.py
index 894b6bca..213a2d21 100644
--- a/tests/test_assessor_records.py
+++ b/tests/test_assessor_records.py
@@ -153,11 +153,25 @@ def test_t74_output_dropping_a_signed_record_fails(tmp_path):
 
 
 def test_sdr_markdown_states_no_assessor_record():
-    sdr = {"note": "n", "class": "C", "impact_level": "low", "ksi_signal_id": "s",
-           "metadata": {"version": "v", "last_updated": "t", "source_of_update": "s"},
-           "metrics": {"current": {"ksi_in_scope": 0, "controls_in_scope": 0, "signal_validations": 0,
-                                   "signal_failing": 0, "vdr_total": 0, "vdr_blocking": 0,
-                                   "vdr_accepted": 0, "vdr_kev": 0},
-                       "daily_metric_data": []},
-           "rule_records": [], "assessor_records": {"status": "no assessor record", "records": []}}
+    sdr = {"metadata": {"version": "1.0.0", "lastUpdated": "t", "updateSource": "s"},
+           "fedRampRequirements": [], "keySecurityIndicators": [], "securityControls": [],
+           "providerExtensions": {"certification": {"program": "c", "status": "s"}, "ksi_signal_id": "s",
+                                  "rules": {"version": "v", "commit": "0" * 40},
+                                  "summary": {"fedRampRequirements": {}, "keySecurityIndicators": {},
+                                              "securityControlsModerate": {}, "securityControlsBeyondModerate": {}},
+                                  "assessorRecords": {"status": "no assessor record", "records": []},
+                                  "assessorCommentResponses": {}}}
     assert "No assessor record" in sdr_mod.render_markdown(sdr)
+
+
+def test_t74_reads_the_schema_shaped_sdr(tmp_path):
+    recs = _assessor.load_records(_dir_with(tmp_path, "genuine.json"), PIN)
+    rules = _rules("KSI-TEST-01")
+    block = _assessor.attach(rules, recs)
+    by_rule = {r["rule_id"]: r["assessor_comment_responses"] for r in rules if r["assessor_comment_responses"]}
+    sdr = {"providerExtensions": {"assessorRecords": block, "assessorCommentResponses": by_rule}}
+    _assessor.verify_output(sdr, recs)
+    bad = copy.deepcopy(sdr)
+    next(iter(bad["providerExtensions"]["assessorCommentResponses"].values()))[0]["text"] = "Softened."
+    with pytest.raises(SystemExit):
+        _assessor.verify_output(bad, recs)
diff --git a/tests/test_availability_probe.py b/tests/test_availability_probe.py
new file mode 100644
index 00000000..6206e42e
--- /dev/null
+++ b/tests/test_availability_probe.py
@@ -0,0 +1,128 @@
+"""CDS-CSO-AVR / CDS-TRC-USH: availability is measured outside AWS, with
+incidents, and the deploy refuses a missing or stale independent feed."""
+import importlib.util
+import json
+from datetime import datetime, timedelta, timezone
+from pathlib import Path
+from urllib.parse import urlparse
+
+import pytest
+
+REPO = Path(__file__).resolve().parent.parent
+
+
+def _load(name, file):
+    spec = importlib.util.spec_from_file_location(name, REPO / "scripts" / file)
+    mod = importlib.util.module_from_spec(spec)
+    spec.loader.exec_module(mod)
+    return mod
+
+
+probe = _load("availability_probe_t", "availability-probe.py")
+avail = _load("build_availability_t", "build-availability.py")
+NOW = datetime(2026, 11, 5, 12, tzinfo=timezone.utc)
+KEYS = [k for k, *_ in probe.TARGETS]
+
+
+def _sample(t, fail=None):
+    return {"t": probe._iso(t), "probed": KEYS, "fail": fail or {}}
+
+
+def test_core_services_are_probed_including_the_app_and_its_sign_in():
+    urls = {u for _k, _s, u, _ok in probe.TARGETS}
+    assert any(u.endswith("/silk-reeling/") for u in urls)
+    hosts = {urlparse(u).hostname or "" for u in urls}
+    assert any(h == "amazoncognito.com" or h.endswith(".amazoncognito.com") for h in hosts)
+    assert any("/.well-known/" in u for u in urls) and any(u.endswith("/trust/") for u in urls)
+    assert all(u.startswith("https://") for u in urls)
+
+
+def test_a_failed_probe_records_the_status():
+    s = probe.probe_once(lambda url: 503 if "trust" in url else 200, NOW)
+    assert s["fail"] == {"trust-center": "HTTP 503"}
+
+
+def test_consecutive_failures_make_an_incident_and_a_single_one_is_transient():
+    t = [NOW - timedelta(minutes=15 * i) for i in range(6, 0, -1)]
+    samples = [_sample(t[0]), _sample(t[1], {"site": "HTTP 503"}), _sample(t[2], {"site": "HTTP 503"}),
+               _sample(t[3]), _sample(t[4], {"trust-center": "no response (timeout)"}), _sample(t[5])]
+    incs, transient = probe.incidents(samples)
+    assert incs == [{"service": "site", "service_name": "Website", "start": probe._iso(t[1]),
+                     "end": probe._iso(t[3]), "failed_probes": 2, "failing_check": "HTTP 503"}]
+    assert transient == {"trust-center": 1}
+
+
+def test_an_ongoing_incident_has_no_end():
+    samples = [_sample(NOW - timedelta(minutes=30), {"site": "HTTP 500"}), _sample(NOW, {"site": "HTTP 500"})]
+    (inc,), _ = probe.incidents(samples)
+    assert inc["end"] is None
+
+
+def test_history_is_kept_35_days_and_its_start_is_carried():
+    old = [_sample(NOW - timedelta(days=d)) for d in (40, 34, 1)]
+    prev = {"feed_type": "availability-status", "history_began": "2026-09-01T00:00:00Z", "samples": old}
+    doc = probe.build(prev, _sample(NOW), NOW)
+    assert len(doc["samples"]) == 3 and doc["history_began"] == "2026-09-01T00:00:00Z"
+    assert doc["availability"]["site"]["probes"] == 2  # 30-day window: day 1 and now
+
+
+def test_availability_percent_counts_failures():
+    prev = {"feed_type": "availability-status", "samples": [_sample(NOW - timedelta(hours=1), {"site": "HTTP 502"})]}
+    doc = probe.build(prev, _sample(NOW), NOW)
+    assert doc["availability"]["site"]["availability_percent"] == 50.0
+    assert doc["current"]["site"] == "up"
+
+
+def test_the_known_bad_stale_feed_fails_the_deploy_guard():
+    why = probe.check_fresh(REPO / "tests" / "fixtures" / "availability" / "known-bad-stale-feed.json", 2, NOW)
+    assert why and "not running" in why[0]
+
+
+def test_a_missing_feed_fails_the_deploy_guard(tmp_path):
+    assert probe.check_fresh(tmp_path / "absent.json", 2, NOW)
+
+
+def test_the_onsite_feed_is_built_from_the_independent_one_never_from_a_deploy(tmp_path):
+    feed = probe.build({}, _sample(datetime.now(timezone.utc)), datetime.now(timezone.utc))
+    (tmp_path / "f.json").write_text(json.dumps(feed))
+    assert avail.main(["--probe-feed", str(tmp_path / "f.json"), "--ksi-signal", str(tmp_path / "none.json"),
+                       "--output", str(tmp_path / "a.json"), "--md-output", str(tmp_path / "a.md")]) == 0
+    doc = json.loads((tmp_path / "a.json").read_text())
+    assert doc["independent_service"]["json"].startswith("https://raw.githubusercontent.com/")
+    assert "deploy" not in json.dumps(doc["daily"]) and doc["measured_at"] == feed["generated_at"]
+    assert "Independent status page" in (tmp_path / "a.md").read_text()
+
+
+def test_the_onsite_builder_refuses_a_stale_feed(tmp_path):
+    with pytest.raises(SystemExit):
+        avail.main(["--probe-feed", str(REPO / "tests" / "fixtures" / "availability" / "known-bad-stale-feed.json"),
+                    "--output", str(tmp_path / "a.json"), "--md-output", str(tmp_path / "a.md")])
+
+
+def test_the_monitor_runs_outside_aws_on_a_schedule_and_pushes_only_its_branch():
+    wf = (REPO / ".github" / "workflows" / "availability-probe.yml").read_text()
+    assert "cron: '*/15 * * * *'" in wf
+    assert "permissions: {}" in wf and "contents: write" in wf
+    assert "aws-actions" not in wf and "id-token" not in wf
+    assert "HEAD:refs/heads/availability-status" in wf
+    assert wf.count("git -c http.extraheader") == 1 and "push --quiet --force" in wf
+
+
+def test_the_deploy_reads_the_independent_feed_before_the_sdr():
+    wf = (REPO / ".github" / "workflows" / "deploy-with-opa.yml").read_text()
+    step = wf.index("- name: Read the independent availability feed (fails when missing or stale)")
+    assert step < wf.index("- name: Build Security Decision Record")
+    assert "--check-fresh availability-probe.json --max-age-hours 2" in wf[step:step + 600]
+    assert "--probe-feed availability-probe.json" in wf
+
+
+def test_an_ongoing_incident_fails_the_monitor_run_after_publishing(tmp_path):
+    samples = [_sample(NOW - timedelta(minutes=15), {"site": "HTTP 500"})]
+    doc = probe.build({"feed_type": "availability-status", "samples": samples}, _sample(NOW, {"site": "HTTP 500"}), NOW)
+    (tmp_path / "f.json").write_text(json.dumps(doc))
+    assert probe.main(["--fail-on-incident", str(tmp_path / "f.json")]) == 1
+    ok = probe.build({}, _sample(NOW), NOW)
+    (tmp_path / "g.json").write_text(json.dumps(ok))
+    assert probe.main(["--fail-on-incident", str(tmp_path / "g.json")]) == 0
+    wf = (REPO / ".github" / "workflows" / "availability-probe.yml").read_text()
+    assert wf.index("Publish the status feed") < wf.index("--fail-on-incident")
diff --git a/tests/test_bootstrap_iam_policies.py b/tests/test_bootstrap_iam_policies.py
new file mode 100644
index 00000000..17687849
--- /dev/null
+++ b/tests/test_bootstrap_iam_policies.py
@@ -0,0 +1,85 @@
+"""The bootstrap groups' inline policies and the managed-policy attachments on
+the roles and groups are inventory components, so a scanner finding that names
+one (checkov on infrastructure/bootstrap) resolves to it instead of being
+recorded as vdr.unresolved-component. Attached policies are published by name
+only: their ARNs carry the account ID."""
+import importlib.util
+import json
+from pathlib import Path
+
+REPO = Path(__file__).resolve().parent.parent
+STATE = json.loads((REPO / "tests" / "fixtures" / "bootstrap-iam" / "state.json").read_text())
+
+
+def _load(name, script):
+    spec = importlib.util.spec_from_file_location(name, REPO / "scripts" / script)
+    m = importlib.util.module_from_spec(spec)
+    spec.loader.exec_module(m)
+    return m
+
+
+bks = _load("bks_iam", "build-ksi-signal.py")
+vdr = _load("vdr_iam", "build-vdr-report.py")
+
+
+def _comps():
+    return {c["component_id"]: c for c in bks.build_cloud_components(STATE, {}, module_dir="infrastructure/bootstrap")}
+
+
+def _tf(comps):
+    return [(cid, c["attributes"].get("tf_type"), c["attributes"].get("tf_name")) for cid, c in comps.items()]
+
+
+def test_group_policies_and_attachment_blocks_are_components():
+    comps = _comps()
+    pol = comps["aws::iam_policy::operators_s3_bucket"]
+    assert pol["native_id"] == "iam-group-policy::operators/s3-bucket"
+    assert pol["attributes"]["attached_to_group"] == "operators"
+    assert "policy_document_sha256" in pol["attributes"]
+    legacy = comps["aws::iam_policy::legacy"]
+    assert legacy["native_id"] == "iam-role-policy-attachment::github-actions-deploy-oidc/legacy"
+    assert legacy["attributes"]["tf_address"] == "aws_iam_role_policy_attachment.legacy"
+    assert legacy["attributes"]["attached_policies"] == [
+        {"policy_name": "github_actions_3", "aws_managed": False},
+        {"policy_name": "github_policy_3", "aws_managed": False}]
+    assert comps["aws::iam_policy::read_only"]["native_id"] == "iam-group-policy-attachment::read-only/read_only"
+    assert comps["aws::iam_policy::plan_read_only"]["attributes"]["attached_policies"] == [
+        {"policy_name": "ReadOnlyAccess", "aws_managed": True}]
+    assert len({c["native_id"] for c in comps.values()}) == len(comps)
+
+
+def test_no_account_id_in_any_new_component():
+    text = json.dumps([c for c in _comps().values() if c["type"] == "iam_policy"])
+    assert "123456789012" not in text
+
+
+def test_known_bad_without_the_components_the_checkov_findings_resolve_to_nothing():
+    """The live findings that were vdr.unresolved-component: each resolves now,
+    and against an inventory without the bootstrap policies (the fixture with
+    them removed) each still resolves to nothing."""
+    comps = _comps()
+    findings = ["aws_iam_group_policy.operators_assessment_readonly", "aws_iam_group_policy.operators_s3_bucket",
+                "aws_iam_group_policy.read_only_deny_sensitive", "aws_iam_role_policy_attachment.legacy"]
+    for res in findings:
+        name = res.split(".", 1)[1]
+        assert vdr.resolve_component({"resource": res}, {}, _tf(comps)) == f"aws::iam_policy::{name}", res
+    without = {cid: c for cid, c in comps.items() if c["type"] != "iam_policy"}
+    for res in findings:
+        assert vdr.resolve_component({"resource": res}, {}, _tf(without)) is None
+
+
+def test_the_bootstrap_policies_fall_in_the_ci_cd_boundary_entry():
+    cls = (REPO / "docs" / "boundary" / "boundary-classification.json").read_text()
+    assert '"aws::iam_policy::*"' in cls
+
+
+def test_an_attachment_on_a_group_resolves_to_the_attachment_not_the_group():
+    comps = _comps()
+    comps.update({c["component_id"]: c for c in bks.build_cloud_components(
+        {"values": {"root_module": {"resources": [
+            {"type": "aws_iam_group", "name": "read_only", "address": "aws_iam_group.read_only",
+             "values": {"arn": "arn:aws:iam::123456789012:group/read-only", "name": "read-only"}}]}}}, {})})
+    tf = _tf(comps)
+    assert vdr.resolve_component({"resource": "aws_iam_group_policy_attachment.read_only"}, {}, tf) == \
+        "aws::iam_policy::read_only"
+    assert vdr.resolve_component({"resource": "aws_iam_group.read_only"}, {}, tf) == "aws::iam_group::read_only"
diff --git a/tests/test_boundary_map.py b/tests/test_boundary_map.py
index 193d8d99..8c3585ef 100644
--- a/tests/test_boundary_map.py
+++ b/tests/test_boundary_map.py
@@ -76,3 +76,18 @@ def test_every_icon_the_viewer_names_exists():
     assert names, "the viewer names no icons"
     for name in names:
         assert (ICONS / f"{name}.svg").is_file(), name
+
+
+def test_every_iam_role_terraform_declares_is_placed_by_a_group():
+    """Reconciliation invariant (l) fails the deploy on an unclassified
+    component. Every role the Terraform declares (the bootstrap OIDC roles
+    included) is a component aws::iam_role::, so each must be placed."""
+    c = classification()
+    patterns = [p for g in c["groups"] for p in g["match"]]
+    roles = set()
+    for tf in (REPO / "infrastructure").rglob("*.tf"):
+        if ".terraform" not in tf.parts:
+            roles |= set(re.findall(r'^resource "aws_iam_role" "(\w+)"', tf.read_text(), re.M))
+    assert "package_maintenance" in roles and "incident_reports" in roles
+    for r in sorted(roles):
+        assert any(fnmatch.fnmatchcase(f"aws::iam_role::{r}", p) for p in patterns), r
diff --git a/tests/test_build_provenance.py b/tests/test_build_provenance.py
index c1e42c75..0b4feff5 100644
--- a/tests/test_build_provenance.py
+++ b/tests/test_build_provenance.py
@@ -74,4 +74,6 @@ def test_builder_id_single_sourced_and_pinned(tmp_path, monkeypatch):
     assert bid == EXPECTED_BUILDER          # derived from WORKFLOW_REF, not hardcoded drift
     assert " " not in bid                   # never the spaced display name
     assert not bid.endswith("@*")           # never a wildcard ref
-    assert "/actions/runs/42" in pred["runDetails"]["metadata"]["invocationId"]
+    # No run ID is published (SLSA v1.0: BuildMetadata has no required field).
+    assert "metadata" not in pred["runDetails"]
+    assert "actions/runs" not in json.dumps(pred) and '"42"' not in json.dumps(pred)
diff --git a/tests/test_build_trust_center.py b/tests/test_build_trust_center.py
index d636aa3c..2110b24b 100644
--- a/tests/test_build_trust_center.py
+++ b/tests/test_build_trust_center.py
@@ -410,3 +410,63 @@ def test_the_output_records_the_governed_freshness_config():
     assert doc["freshness_windows_hours"]["corroboration"] == fc["windows_hours"][".well-known/boundary-corroboration.json"]
     sources = {t["name"]: t["source"] for t in doc["policy_catalog"]["thresholds"]["items"]}
     assert sources["Vulnerability evidence freshness"] == fc["source"]
+
+
+def test_the_trust_center_carries_the_offerings_fedramp_id():
+    import _offering
+    assert build()["fedRampId"] == _offering.fedramp_id()
+
+
+def test_the_trust_center_says_not_certified_like_the_cpo_and_sdr():
+    assert build()["certification"] == {"program": "FedRAMP 20x, Program path, Class C",
+                                        "status": "not certified (proof of concept)"}
+    js = (REPO / "website" / "assets" / "js" / "trust.js").read_text()
+    assert "doc.certification?.status" in js and "'not certified (proof of concept)'" in js
+
+
+# --- the Rev5 Moderate view (moved from the retired scripts/inject-figures.py) ------
+# The figures come from the control projection (scripts/_controls.py) over the
+# committed fixture inventory, so they run everywhere; the deploy computes the
+# published ones from the real inventory.
+
+FIXTURE_SIGNAL = REPO / "tests" / "fixtures" / "clean" / "ksi-signal.json"
+
+
+def _projection():
+    import _controls
+    return _controls.load(FIXTURE_SIGNAL)
+
+
+def test_the_moderate_view_is_measured_against_the_published_baseline():
+    f = btc.framework_figures(_projection())
+    assert f["moderate_baseline"] == "323" and f["moderate_coverage"] == "323/323"
+    # controls FedRAMP's KSI mappings reach beyond Moderate (2026-10-13 revision)
+    assert f["moderate_beyond"] == "59"
+    total = int(f["moderate_baseline"]) + int(f["moderate_beyond"])
+    assert int(f["moderate_implemented"]) + int(f["moderate_inherited"]) + int(f["moderate_na"]) == total
+
+
+def test_a_baseline_control_missing_from_the_projection_lowers_coverage():
+    """Coverage is measured, not assumed: drop one baseline control from the
+    projection and the figure falls below N/N instead of staying green."""
+    import _controls
+    irs = _projection()
+    irs.remove(next(ir for ir in irs if ir["control-id"] in _controls.BASELINE_CONTROLS))
+    assert btc.framework_figures(irs)["moderate_coverage"] == "322/323"
+
+
+def test_only_the_rev5_moderate_view_is_published():
+    """CMMC, GovRAMP and TX-RAMP figures are retired; the posture carries the
+    Rev5 Moderate view the SDR derives, and nothing else."""
+    assert set(btc.framework_figures(_projection())) == {
+        "moderate_coverage", "moderate_baseline", "moderate_beyond",
+        "moderate_implemented", "moderate_inherited", "moderate_na"}
+    trust_js = (REPO / "website" / "assets" / "js" / "trust.js").read_text()
+    for retired in ("govramp", "txramp", "cmmc"):
+        assert retired not in trust_js.lower()
+
+
+def test_the_moderate_view_fails_closed_without_the_inventory(tmp_path):
+    import _controls
+    with pytest.raises(SystemExit, match="fail-closed"):
+        btc.framework_figures(_controls.load(tmp_path / "absent.json"))
diff --git a/tests/test_certification_cycle.py b/tests/test_certification_cycle.py
new file mode 100644
index 00000000..b715abf0
--- /dev/null
+++ b/tests/test_certification_cycle.py
@@ -0,0 +1,663 @@
+"""The certification package and its quarterly cycle: the CPO in FedRAMP's
+schema, the CCM calendar, the Ongoing Certification Report (rolling and
+issued), snapshots, FedRAMP Certification Reports, the simulated package
+submission, the FedRAMP ID gate and the unattended package maintainer.
+
+Each gate here has a committed known-bad fixture under tests/fixtures/cycle/bad/
+that fails for the reason the test names."""
+
+import argparse
+import copy
+import fnmatch
+import hashlib
+import importlib.util
+import json
+import re
+import sys
+from datetime import date, datetime, timezone
+from pathlib import Path
+
+import pytest
+
+REPO = Path(__file__).resolve().parent.parent
+sys.path.insert(0, str(REPO / "scripts"))
+import _assessor  # noqa: E402
+import _ccm  # noqa: E402
+import _decisions  # noqa: E402
+import _engagement  # noqa: E402
+import _fedramp_schema as fs  # noqa: E402
+import _offering  # noqa: E402
+import _quarterly_review  # noqa: E402
+import _sensitivity  # noqa: E402
+
+FIX = REPO / "tests" / "fixtures" / "cycle"
+BAD = FIX / "bad"
+NOW = datetime(2026, 11, 5, 12, tzinfo=timezone.utc)
+ISSUE_DAY = datetime(2026, 11, 24, 12, tzinfo=timezone.utc)
+SIGNAL = json.loads((REPO / "tests" / "fixtures" / "clean" / "ksi-signal.json").read_text())
+PROFILE = json.loads((REPO / "data" / "system-profile.json").read_text())
+# The simulated assessor's signed set (signature check stubbed; tested in test_simulated_assessor.py).
+def _assessment():
+    import tempfile
+    with tempfile.TemporaryDirectory() as d:
+        s = Path(d) / "simulated-assessment.json"
+        s.write_text((REPO / "tests" / "fixtures" / "assessor" / "simulated-set.json").read_text())
+        return _assessor.load_assessment(s, s, verifier=lambda *_a: True, expect_commit="0" * 40,
+                                         expect_signal_id="00000000-0000-4000-8000-000000000001")
+
+
+ASSESSMENT = _assessment()
+
+
+def _load(name, script):
+    spec = importlib.util.spec_from_file_location(name, REPO / "scripts" / script)
+    mod = importlib.util.module_from_spec(spec)
+    spec.loader.exec_module(mod)
+    return mod
+
+
+cpo = _load("build_cpo", "build-cpo.py")
+ocr = _load("build_ocr", "build-ocr.py")
+issue_ocr = _load("issue_ocr", "issue-ocr.py")
+frc = _load("publish_frc", "publish-certification-reports.py")
+submit = _load("submit_package", "submit-package.py")
+fid_gate = _load("check_fedramp_id", "check-fedramp-id.py")
+maint = _load("check_package_maintainer", "check-package-maintainer.py")
+
+
+def _json(p):
+    return json.loads(Path(p).read_text())
+
+
+def _cal(today=None, path=_ccm.CALENDAR_PATH):
+    return _ccm.load(path, today or NOW.date())
+
+
+def _off(path=_offering.OFFERING_PATH):
+    return _offering.load(path)
+
+
+def _cpo(off=None, prev=None, now=NOW):
+    return cpo.build(off or _off(), PROFILE, SIGNAL, _cal(now.date()), prev or {}, now, cpo.boundary_groups(),
+                     ASSESSMENT)
+
+
+def _ocr(now=NOW, issue=None, incidents=None, scn_rows=(), prev=None, decisions=None):
+    return ocr.build(_cal(now.date()), now.date(), None, decisions or _decisions.load(), list(scn_rows), incidents,
+                     SIGNAL, PROFILE, _off(), prev or {}, now, issue)
+
+
+# --- the CCM calendar (CCM-OCR-SOR, CCM-QTR-SAR, CCM-OCR-NRD, CCM-QTR-NRD) -----------
+
+def test_the_committed_calendar_is_valid():
+    cal = _cal()
+    assert len(cal.issues) >= 4
+
+
+def test_the_review_is_five_business_days_after_issue_skipping_thanksgiving():
+    cal = _cal()
+    # 2026-11-24 (Tue) + 5 business days, Thanksgiving (Thu 26th) excluded.
+    assert cal.review_date(date(2026, 11, 24)) == date(2026, 12, 2)
+    for d in cal.issues:
+        r = cal.review_date(d)
+        days = [x for x in (date.fromordinal(o) for o in range(d.toordinal() + 1, r.toordinal() + 1))
+                if cal.is_business_day(x)]
+        assert len(days) == cal.offset and 3 <= cal.offset <= 10
+
+
+@pytest.mark.parametrize("fixture,today,reason", [
+    ("calendar-mid-quarter.json", None, "beginning, middle or end of its quarter"),
+    ("calendar-irregular-gap.json", None, "not a regular 3-month cycle"),
+    ("calendar-review-too-soon.json", None, "must be 3 to 10"),
+    ("calendar-runs-out.json", date(2026, 12, 1), "fewer than 2 issue dates"),
+    ("calendar-issue-on-holiday.json", None, "is not a business day"),
+])
+def test_a_bad_calendar_fails_closed(fixture, today, reason):
+    with pytest.raises(SystemExit, match=reason):
+        _ccm.load(BAD / fixture, today or NOW.date())
+
+
+def test_next_dates_hold_steady_between_issues_and_move_on_the_issue_date():
+    cal = _cal()
+    before = [_ccm.dates_summary(cal, date(2026, 11, d)) for d in (5, 12, 23)]
+    assert all(b == before[0] for b in before)
+    assert before[0]["nextOngoingCertificationReportDate"] == "2026-11-24"
+    assert before[0]["nextQuarterlyReviewDate"] == "2026-12-02"
+    on = _ccm.dates_summary(cal, date(2026, 11, 24))
+    assert on["nextOngoingCertificationReportDate"] == "2027-02-23"
+    assert on["nextQuarterlyReviewDate"] == "2026-12-02"  # the review of the report just issued
+
+
+def test_the_review_calendar_file_is_rfc5545():
+    text = _ccm.ics(_cal(), NOW.date())
+    assert text.startswith("BEGIN:VCALENDAR\r\n") and text.endswith("END:VCALENDAR\r\n")
+    assert "\n" not in text.replace("\r\n", "")
+    assert all(len(line.encode()) <= 75 for line in text.split("\r\n"))
+    assert text.count("BEGIN:VEVENT") == len(_cal().issues)
+    assert "DTSTART:20261202T170000Z" in text
+    unfolded = text.replace("\r\n ", "")
+    assert f"URL:{_ccm.review_url(_cal().issues[0])}" in unfolded
+    # no engagement (DEC-194): the event is simulated and invites nobody
+    assert "LOCATION:Simulated (package-maintenance.yml)" in unfolded and "Simulated (DEC-194)" in unfolded
+    assert _engagement.invitations(unfolded) == []
+    assert _ccm.ics(_cal(), NOW.date()) == text  # deterministic
+
+
+# --- the CPO (CPO-CSO-OVR, CPO-CSO-MTD, CDS-CSO-SVC, CDS-CSO-FID, FRC-CSO-POP) -------
+
+@pytest.fixture(scope="module")
+def built_cpo():
+    return _cpo()
+
+
+def test_the_cpo_validates_against_fedramps_schema(built_cpo):
+    assert fs.validate(built_cpo, "cpo") == []
+
+
+def test_the_cpo_seeks_20x_only(built_cpo):
+    assert built_cpo["serviceIdentification"]["certificationType"] == "20x"
+    assert "Rev5" not in built_cpo["providerExtensions"]["certification"]["program"].replace(" ", "")
+    assert "Rev 5" not in built_cpo["providerExtensions"]["certification"]["program"]
+
+
+def test_the_cpo_json_says_the_system_is_not_certified(built_cpo):
+    assert built_cpo["providerExtensions"]["certification"]["status"] == "not certified (proof of concept)"
+    assert "not certified (proof of concept)" in cpo.render_markdown(built_cpo)
+
+
+def test_no_cpo_or_ocr_label_names_rev5_as_a_program(built_cpo, rolling):
+    """FRC-CSO-POP (DEC-107). The only Rev5 the package names is the Moderate
+    control baseline the SDR maps 20x evidence onto, never a certification."""
+    for text in (json.dumps(built_cpo), cpo.render_markdown(built_cpo), json.dumps(rolling), ocr.render_markdown(rolling)):
+        assert re.findall(r"Rev ?5(?! Moderate control)", text) == []
+
+
+def test_the_fedramp_id_and_uei_are_the_offerings_and_flagged_simulated(built_cpo):
+    off = _off()
+    si = built_cpo["serviceIdentification"]
+    assert si["fedRampPackageId"] == off["fedramp_id"] == built_cpo["providerExtensions"]["fedRampId"]
+    assert off["provider_name"] in si["fedRampPackageId"] and off["service_acronym"] in si["fedRampPackageId"]
+    assert "NOT-A-REAL" in si["fedRampPackageId"] and "NOT-A-REAL" in si["ueiNumber"]
+    sim = {s["field"]: s["counterparty"] for s in built_cpo["providerExtensions"]["simulated"]}
+    assert sim == {"serviceIdentification.fedRampPackageId": "fedramp", "serviceIdentification.ueiNumber": "sam-gov",
+                   "providerExtensions.independentAssessment.overallSummary": "assessor"}
+
+
+@pytest.mark.parametrize("fixture,reason", [
+    ("offering-placeholder-id-unflagged.json", "fedramp_id_simulated"),
+    ("offering-id-without-provider-name.json", "provider name and acronym"),
+])
+def test_a_bad_fedramp_id_in_the_offering_fails(fixture, reason):
+    with pytest.raises(SystemExit, match=reason):
+        _offering.load(BAD / fixture)
+
+
+def test_each_service_has_its_own_category_and_the_list_says_what_is_not_included(built_cpo):
+    services = built_cpo["providerExtensions"]["services"]
+    assert len(services) == len(built_cpo["certifiedServices"]) >= 2
+    cats = {json.dumps(s["securityCategory"], sort_keys=True) for s in services}
+    assert len(cats) == len(services)  # not one uniform label
+    assert all(s["boundaryGroups"] for s in services)
+    assert built_cpo["providerExtensions"]["notIncluded"]
+
+
+@pytest.mark.parametrize("fixture,reason", [
+    ("offering-service-above-system.json", "exceeds the system's"),
+    ("offering-unknown-boundary-group.json", "not in the boundary classification"),
+])
+def test_a_bad_service_list_fails(fixture, reason):
+    with pytest.raises(SystemExit, match=reason):
+        _cpo(off=_off(BAD / fixture))
+
+
+def test_no_contact_email_field_holds_anything_but_an_address(built_cpo):
+    fsi = _cpo(off=_off(FIX / "offering-fsi-url.json"))
+    for doc in (built_cpo, fsi):
+        for c in doc["contactInformation"]:
+            if "contactEmail" in c:
+                assert re.fullmatch(r"[^@\s/]+@[^@\s/]+\.[a-z]+", c["contactEmail"])
+    entry = next(c for c in fsi["contactInformation"] if c["contactType"] == "FedRAMP Security Inbox")
+    assert "contactEmail" not in entry
+    good = _off(FIX / "offering-fsi-url.json")
+    good["fedramp_security_inbox"]["address"] = "security@samaydlette.com"
+    entry = next(c for c in _cpo(off=good)["contactInformation"] if c["contactType"] == "FedRAMP Security Inbox")
+    assert entry["contactEmail"] == "security@samaydlette.com"
+
+
+def test_the_cpo_version_is_semver_and_bumps_only_on_change(built_cpo):
+    md = built_cpo["metadata"]
+    assert md["version"] == "1.0.0" and md["lastUpdated"] == NOW.isoformat() and md["updateSource"]
+    later = datetime(2026, 11, 6, 12, tzinfo=timezone.utc)
+    assert _cpo(prev=built_cpo, now=later)["metadata"]["version"] == "1.0.0"
+    prev = copy.deepcopy(built_cpo)
+    prev["metadata"]["version"] = "1.0.4"
+    prev["providerExtensions"]["contentSha256"] = "0" * 64
+    assert _cpo(prev=prev)["metadata"]["version"] == "1.0.5"
+
+
+def test_the_cpo_publishes_the_fixed_cycle_dates(built_cpo):
+    cal = _cal()
+    assert built_cpo["serviceProperties"]["nextOngoingCertificationReportDate"] == cal.next_issue(NOW.date()).isoformat()
+    cm = built_cpo["providerExtensions"]["continuousMonitoring"]
+    assert cm["quarterlyReviewCalendar"] == _ccm.ICS_URL and cm["quarterlyReviews"] == _ccm.REVIEWS_INDEX_URL
+    assert "quarterlyReviewRegistration" not in cm
+
+
+# --- the OCR (CCM-OCR-*, CCM-QTR-*) ---------------------------------------------------
+
+@pytest.fixture(scope="module")
+def rolling():
+    return _ocr()
+
+
+def test_the_rolling_ocr_validates_and_carries_the_cycle(rolling):
+    assert fs.validate(rolling, "ocr") == []
+    pe = rolling["providerExtensions"]
+    assert pe["report"]["kind"] == "rolling"
+    assert pe["fedRampId"] == _offering.fedramp_id()
+    assert pe["continuousMonitoring"]["nextOngoingCertificationReportDate"] == "2026-11-24"
+    assert pe["quarterlyReview"]["date"] == "2026-12-02"
+    assert pe["quarterlyReview"]["agenda"] == ocr.STANDING_AGENDA and len(ocr.STANDING_AGENDA) >= 3
+    assert pe["publicRelease"]["decision"] == ocr.PUBLIC_RELEASE_DECISION
+    assert pe["feedback"]["channel"] == _quarterly_review.INTAKE
+    assert pe["engagement"] == _engagement.STATEMENT
+    assert pe["sensitivityScreen"] == {"checks": list(_sensitivity.CHECKS), "findings": 0}
+
+
+def test_the_decisions_the_ocr_cites_are_in_force():
+    ids = {d["id"] for d in _decisions.in_force(_decisions.load())}
+    assert {ocr.PUBLIC_RELEASE_DECISION, ocr.ENGAGEMENT_DECISION} <= ids
+
+
+def test_an_issued_ocr_covers_the_quarter_and_is_marked_frozen():
+    doc = _ocr(now=ISSUE_DAY, issue=date(2026, 11, 24))
+    assert fs.validate(doc, "ocr") == []
+    assert doc["reportPeriod"] == {"from": "2026-08-25", "to": "2026-11-24"}
+    assert doc["providerExtensions"]["report"]["kind"] == "issued"
+    assert doc["providerExtensions"]["report"]["late"] is False
+
+
+def test_an_issue_cannot_be_built_before_its_date_or_off_the_calendar():
+    with pytest.raises(SystemExit, match="in the future"):
+        _ocr(issue=date(2026, 11, 24))
+    with pytest.raises(SystemExit, match="not a calendar issue date"):
+        _ocr(now=ISSUE_DAY, issue=date(2026, 11, 23))
+
+
+@pytest.mark.parametrize("check", sorted(_json(BAD / "sensitive-values.json")))
+def test_the_sensitivity_screen_catches_each_kind(check):
+    doc = _json(BAD / "sensitive-values.json")[check]
+    assert {c for _, c in _sensitivity.screen(doc)} == {check}
+    with pytest.raises(SystemExit, match="must not be published"):
+        _sensitivity.require_clean(doc, "the fixture")
+
+
+def test_the_sensitivity_screen_catches_a_token_and_allows_the_systems_own_domain():
+    token = "ghp_" + "A1b2C3d4" * 5
+    assert _sensitivity.screen({"x": f"used {token}"}) == [("/x", "token")]
+    assert _sensitivity.screen({"x": "write to security@samaydlette.com"}) == []
+
+
+def test_an_ocr_carrying_a_personal_address_is_never_built():
+    row = {"scn_id": "SCN-T-1", "scn_type": "adaptive", "date_finished": "2026-11-01",
+           "short_description": "Asked by jane.doe@example.org"}
+    with pytest.raises(SystemExit, match="sensitivity screen"):
+        _ocr(scn_rows=[row])
+
+
+def test_reportable_incidents_come_from_the_register_and_exercises_say_so():
+    reg = {"incidents": [
+        {"id": "INC-1", "title": "Exercise: tabletop", "exercise": True, "started_at": "2026-10-01T00:00:00Z",
+         "resolved_at": "2026-10-01T02:00:00Z", "evaluation": {"reportable": True}, "lessons_learned": ["Drill it"]},
+        {"id": "INC-2", "title": "Not reportable", "started_at": "2026-10-02T00:00:00Z",
+         "evaluation": {"reportable": False}}]}
+    got = _ocr(incidents=reg)["reportableIncidents"]["incidents"]
+    assert [i["summary"] for i in got] == ["INC-1: Exercise, not a real incident: tabletop"]
+    assert got[0]["incidentLessonsLearned"] == ["Drill it"]
+
+
+def test_the_feedback_summary_covers_the_previous_issue():
+    """Once the previous issue's review date has passed, the OCR carries the
+    review's anonymized Q&A, built by the same function as the review."""
+    before = datetime(2026, 12, 1, 12, tzinfo=timezone.utc)   # the review is 2026-12-02
+    s0 = _ocr(now=before)["providerExtensions"]["feedback"]["summaryOfPreviousReport"]
+    assert "once it is held" in s0["statement"] and "items" not in s0
+    later = datetime(2026, 12, 10, 12, tzinfo=timezone.utc)
+    s = _ocr(now=later)["providerExtensions"]["feedback"]["summaryOfPreviousReport"]
+    qa = _quarterly_review.qa_summary("2026-11-24", 0)
+    assert s["ocr"] == "2026-11-24" and s["received"] == qa["received"] and s["items"] == qa["items"]
+    assert "simulated" in s["statement"]
+
+
+def test_a_feedback_summary_never_carries_a_name_or_an_agency():
+    for n in range(8):
+        qa = _quarterly_review.qa_summary(f"2027-0{1 + n % 8}-01", n)
+        text = json.dumps(qa)
+        assert _sensitivity.screen(qa) == []
+        assert "Department of" not in text and "Bureau of" not in text
+
+
+# --- issuing and snapshots (CCM-OCR-AVL, CDS-CSO-HAD) ---------------------------------
+
+def _issue_args(tmp_path, work, prev=None):
+    sig = tmp_path / "ksi-signal.json"
+    sig.write_text(json.dumps(SIGNAL))
+    return argparse.Namespace(
+        work=str(work), out=str(tmp_path / "out"), previous_index=str(prev) if prev else None,
+        new_files=str(tmp_path / "issued.txt"), calendar=str(_ccm.CALENDAR_PATH),
+        offering=str(_offering.OFFERING_PATH), profile=str(REPO / "data" / "system-profile.json"),
+        vdr=str(tmp_path / "none.json"), decisions=str(REPO / "data" / "decisions.json"),
+        scn_register=str(tmp_path / "none.csv"), ksi_signal=str(sig), incidents=str(tmp_path / "none.json"))
+
+
+def _work(tmp_path, names=issue_ocr.REQUIRED):
+    w = tmp_path / "work"
+    w.mkdir(exist_ok=True)
+    for n in names:
+        (w / n).write_text(json.dumps({"file": n}))
+    return w
+
+
+def test_the_first_run_on_an_issue_date_freezes_the_report_and_snapshots_the_package(tmp_path):
+    index, new = issue_ocr.run(_issue_args(tmp_path, _work(tmp_path)), ISSUE_DAY)
+    out = tmp_path / "out"
+    assert [i["issueDate"] for i in index["issues"]] == ["2026-11-24"]
+    assert {"ocr-issue-2026-11-24.json", "ocr-issue-2026-11-24.md", "snapshot-2026-11-24.json"} <= set(new)
+    assert fs.validate(_json(out / "ocr-issue-2026-11-24.json"), "ocr") == []
+    manifest = _json(out / "snapshot-2026-11-24.json")
+    assert sorted(f["name"] for f in manifest["files"]) == sorted(issue_ocr.REQUIRED)
+    assert index["issues"][0]["quarterlyReviewDate"] == "2026-12-02"
+    assert index["fedRampId"] == _offering.fedramp_id()
+    # Every new file is one the maintenance role may write.
+    keys = _bootstrap_keys()
+    assert all(any(fnmatch.fnmatch(".well-known/" + f, k) for k in keys) for f in new)
+
+
+def test_an_issued_report_is_carried_over_and_never_rebuilt(tmp_path):
+    index, _ = issue_ocr.run(_issue_args(tmp_path, _work(tmp_path)), ISSUE_DAY)
+    prev = tmp_path / "prev.json"
+    prev.write_text(json.dumps(index))
+    again, new = issue_ocr.run(_issue_args(tmp_path, _work(tmp_path), prev), datetime(2026, 11, 25, tzinfo=timezone.utc))
+    assert new == [] and again["issues"] == index["issues"]
+
+
+def test_no_issue_without_the_certification_data_to_snapshot(tmp_path):
+    with pytest.raises(SystemExit, match="ksi-signal.json missing"):
+        issue_ocr.run(_issue_args(tmp_path, _work(tmp_path, issue_ocr.REQUIRED[:-1])), ISSUE_DAY)
+
+
+@pytest.mark.parametrize("fixture,reason", [
+    ("ocr-issues-not-a-calendar-date.json", "not a calendar issue date"),
+    ("ocr-issues-out-of-order.json", "out of order"),
+])
+def test_a_tampered_issue_index_fails(fixture, reason):
+    with pytest.raises(SystemExit, match=reason):
+        issue_ocr.check_index(_json(BAD / fixture), _cal())
+
+
+# --- FedRAMP Certification Reports (CDS-CSO-FRC, simulated FedRAMP) -------------------
+
+SCN_ROWS = [{"scn_id": "SCN-2026-001", "scn_type": "adaptive"}, {"scn_id": "SCN-2026-002", "scn_type": "adaptive"}]
+
+
+def _submit(previous, when, scn_rows=SCN_ROWS, content=None):
+    docs, paths = _pkg()
+    if content:
+        docs["ocr"]["providerExtensions"]["contentSha256"] = content
+    return submit.build(docs, paths, previous, when, "abc", PKG_RULES, PKG_ID, scn_rows)
+
+
+def _reports(log):
+    return [e["certificationReport"] for e in log["entries"] if e.get("certificationReport")]
+
+
+def test_the_first_submission_gets_a_simulated_report_and_ordinary_deploys_do_not():
+    log = _submit({}, NOW)
+    (r,) = _reports(log)
+    assert r["receivedOn"] == "2026-11-05" and r["trigger"].startswith("initial")
+    assert r["scnsCovered"] == ["SCN-2026-001", "SCN-2026-002"]
+    # An ordinary deploy, even one whose package changed, re-issues nothing.
+    later = _submit(log, datetime(2027, 2, 1, tzinfo=timezone.utc), content="e" * 64)
+    assert len(later["entries"]) == 2 and len(_reports(later)) == 1
+
+
+def test_an_adaptive_or_transformative_scn_brings_a_new_report():
+    log = _submit({}, NOW)
+    rows = SCN_ROWS + [{"scn_id": "SCN-2026-009", "scn_type": "transformative"},
+                       {"scn_id": "SCN-2026-010", "scn_type": "routine-recurring"}]
+    later = _submit(log, datetime(2026, 12, 1, tzinfo=timezone.utc), rows)
+    assert len(_reports(later)) == 2 and "SCN-2026-009" in _reports(later)[-1]["trigger"]
+    assert "SCN-2026-010" not in _reports(later)[-1]["trigger"]
+    again = _submit(later, datetime(2026, 12, 2, tzinfo=timezone.utc), rows)
+    assert len(_reports(again)) == 2  # that SCN is covered now
+
+
+def test_a_report_is_issued_annually_even_when_the_package_is_unchanged():
+    log = _submit({}, NOW)
+    assert len(_reports(_submit(log, datetime(2027, 11, 4, tzinfo=timezone.utc)))) == 1
+    annual = _submit(log, datetime(2027, 11, 5, tzinfo=timezone.utc))
+    assert len(_reports(annual)) == 2 and _reports(annual)[-1]["trigger"].startswith("annual")
+
+
+def test_the_report_says_first_that_it_is_simulated_not_issued_by_fedramp_and_not_certified():
+    (r,) = _reports(_submit({}, NOW))
+    first = submit.report_bytes(r["report"]).decode().splitlines()[1]
+    assert first.startswith('  "title": "SIMULATED REPORT, NOT ISSUED BY FEDRAMP')
+    assert "NOT FedRAMP certified" in first
+    assert r["report"]["certificationStatus"] == "not certified (proof of concept)"
+    assert r["report"]["simulated"] is True and r["report"]["notIssuedByFedRAMP"] is True
+
+
+def test_logged_reports_are_published_byte_identical_and_their_first_date_kept(tmp_path):
+    log = _submit({}, NOW)
+    idx = frc.build(log, {}, NOW, tmp_path)
+    (e,) = idx["reports"]
+    raw = (tmp_path / "fedramp-certification-reports" / e["file"]).read_bytes()
+    assert hashlib.sha256(raw).hexdigest() == e["sha256"] == _reports(log)[0]["sha256"]
+    assert e["daysToPublish"] == 0 and e["withinTwoWeeks"] and idx["certificationStatus"].startswith("not certified")
+    again = frc.build(log, idx, datetime(2026, 12, 31, tzinfo=timezone.utc), tmp_path)
+    assert again["reports"][0]["firstPublished"] == "2026-11-05"
+
+
+def test_known_bad_a_report_published_more_than_two_weeks_after_receipt_fails_the_deploy(tmp_path, monkeypatch):
+    class Late(datetime):
+        @classmethod
+        def now(cls, tz=None):
+            return NOW
+    monkeypatch.setattr(frc, "datetime", Late)
+    with pytest.raises(SystemExit, match="past the 14-day window"):
+        frc.main(["--submission-log", str(BAD / "submission-log-late-report.json"), "--out", str(tmp_path)])
+    assert not (tmp_path / "fedramp-certification-reports.json").exists()
+
+
+@pytest.mark.parametrize("fixture,reason", [
+    ("submission-log-report-modified.json", "differs from the sha256 logged"),
+    ("submission-log-report-not-labelled.json", "NOT ISSUED BY FEDRAMP"),
+])
+def test_known_bad_a_modified_or_unlabelled_report_is_never_published(tmp_path, fixture, reason):
+    with pytest.raises(SystemExit, match=reason):
+        frc.build(_json(BAD / fixture), {}, NOW, tmp_path)
+
+
+@pytest.mark.parametrize("over,needle", [({"cpo": "cpo-without-not-certified-status.json"}, "the CPO does not state"),
+                                         ({"sdr": "sdr-without-not-certified-status.json"}, "the SDR does not state")])
+def test_known_bad_a_cpo_or_sdr_without_the_not_certified_status_is_never_submitted(over, needle):
+    docs, paths = _pkg(**over)
+    with pytest.raises(SystemExit, match=needle):
+        submit.build(docs, paths, {}, NOW, "abc", PKG_RULES, PKG_ID)
+
+
+# --- the simulated package submission (FRC-CSO-PKG, FRC-CSO-POP) ----------------------
+
+PKG_ID = "Example Provider (EXD)"
+PKG_RULES = ["VDR-CSO-DET"]
+
+
+def _pkg(**over):
+    paths = {k: FIX / "package" / f"{k}.json" for k in ("cpo", "sdr", "ocr")}
+    paths.update({k: BAD / v for k, v in over.items()})
+    return {k: _json(p) for k, p in paths.items()}, paths
+
+
+def test_a_complete_package_is_logged_once_per_content_change():
+    docs, paths = _pkg()
+    log = submit.build(docs, paths, {}, NOW, "abc", PKG_RULES, PKG_ID)
+    assert log["nothingSent"] is True and log["simulated"]["counterparty"] == "fedramp"
+    assert len(log["entries"]) == 1 and log["entries"][0]["receipt"]["receiptId"].startswith("SIM-")
+    assert len(submit.build(docs, paths, log, NOW, "abc", PKG_RULES, PKG_ID)["entries"]) == 1
+    docs["ocr"]["providerExtensions"]["contentSha256"] = "f" * 64
+    assert len(submit.build(docs, paths, log, NOW, "abd", PKG_RULES, PKG_ID)["entries"]) == 2
+
+
+@pytest.mark.parametrize("over,rules,reason", [
+    ({"cpo": "../../cr26/bad/cpo-no-sales-contact.json"}, PKG_RULES, "does not validate against FedRAMP's schema"),
+    ({"cpo": "cpo-rev5-program.json"}, PKG_RULES, "FRC-CSO-POP"),
+    ({"cpo": "cpo-without-assessment-summary.json"}, PKG_RULES, "CPO-CSO-OVR"),
+    ({"sdr": "sdr-repeats-a-rule.json"}, PKG_RULES, "every applicable FedRAMP rule exactly once"),
+    ({}, PKG_RULES + ["CCM-OCR-AVL"], "every applicable FedRAMP rule exactly once"),
+    ({"ocr": "ocr-other-fedramp-id.json"}, PKG_RULES, "CDS-CSO-FID"),
+])
+def test_an_incomplete_or_inconsistent_package_is_not_submitted(over, rules, reason):
+    docs, paths = _pkg(**over)
+    with pytest.raises(SystemExit, match=reason):
+        submit.build(docs, paths, {}, NOW, "abc", rules, PKG_ID)
+
+
+def test_a_malformed_previous_log_is_not_overwritten():
+    docs, paths = _pkg()
+    with pytest.raises(SystemExit, match="malformed entry"):
+        submit.build(docs, paths, _json(BAD / "submission-log-malformed.json"), NOW, "abc", PKG_RULES, PKG_ID)
+
+
+# --- the FedRAMP ID gate (CDS-CSO-FID) -------------------------------------------------
+
+def test_the_gate_covers_the_three_reports_by_default():
+    assert fid_gate.REPORTS[:3] == ("certification-package-overview.json", "security-decision-record.json",
+                                    "ongoing-certification-report.json")
+    step = _step("deploy-with-opa.yml", "FedRAMP ID in every FedRAMP report (CDS-CSO-FID)")
+    assert "check-fedramp-id.py" in step
+
+
+@pytest.mark.parametrize("fixture,ok", [
+    (FIX / "package" / "cpo.json", True), (FIX / "package" / "ocr.json", True),
+    (BAD / "ocr-other-fedramp-id.json", False), (BAD / "cpo-other-package-id.json", False),
+])
+def test_the_gate_fails_a_report_with_another_fedramp_id(monkeypatch, fixture, ok):
+    monkeypatch.setattr(fid_gate._offering, "fedramp_id", lambda *a: PKG_ID)
+    assert fid_gate.main([str(fixture)]) == (0 if ok else 1)
+
+
+def test_the_gate_fails_an_unreadable_report(tmp_path):
+    assert fid_gate.main([str(tmp_path / "missing.json")]) == 1
+
+
+# --- the unattended maintainer (CPO-CSX-CPM, SDR-CSX-KMT) -----------------------------
+
+WORKFLOWS = REPO / ".github" / "workflows"
+
+
+def _step(workflow, name):
+    text = (WORKFLOWS / workflow).read_text()
+    start = text.index(f"- name: {name}")
+    end = text.find("\n    - name:", start + 1)
+    return text[start:end if end > 0 else None]
+
+
+def _bootstrap_keys():
+    tf = (REPO / "infrastructure" / "bootstrap" / "package-maintenance.tf").read_text()
+    block = re.search(r"package_maintenance_keys = \[(.*?)\]", tf, re.S).group(1)
+    return re.findall(r'"([^"]+)"', block)
+
+
+def _maintenance_publishes():
+    step = _step("package-maintenance.yml", "Publish the certification package to /.well-known/")
+    names = set(re.findall(r"^\s*put ([\w.-]+)\s", step, re.M))
+    for var, items, body in re.findall(r"for (\w+) in ([^;\n]+); do(.*?)\n\s*done", step, re.S):
+        for suffix in re.findall(r"put \"\$" + var + r"(\.[\w.]+)\"", body):
+            names |= {i + suffix for i in items.split()}
+    return {".well-known/" + n for n in names}
+
+
+def test_the_maintenance_role_may_write_exactly_what_the_workflow_publishes():
+    keys = _bootstrap_keys()
+    literal = {k for k in keys if "*" not in k}
+    assert literal == _maintenance_publishes()
+    assert {k for k in keys if "*" in k} == {".well-known/ocr-issue-*", ".well-known/snapshot-*",
+                                              ".well-known/snapshots/*", ".well-known/quarterly-review-*",
+                                              ".well-known/security-review-*"}
+
+
+def test_the_maintainer_runs_daily_and_the_package_windows_are_two_weeks_at_most():
+    wf = (WORKFLOWS / "package-maintenance.yml").read_text()
+    assert re.search(r"cron: '\d+ \d+ \* \* \*'", wf)
+    assert "environment: package-maintenance" in wf and "workflow_call:" in wf
+    cfg = {a["path"]: a for a in _json(REPO / "infrastructure" / "schemas" / "freshness-config.json")["artifacts"]}
+    for p in ("security-decision-record.json", "certification-package-overview.json",
+              "ongoing-certification-report.json"):
+        assert cfg[".well-known/" + p]["max_age_hours"] <= 14 * 24
+
+
+def test_the_deploy_checks_the_maintainer_before_building_and_proves_it_after():
+    wf = (WORKFLOWS / "deploy-with-opa.yml").read_text()
+    assert wf.index("- name: Package maintainer preflight") < wf.index("- name: Build Security Decision Record")
+    assert "uses: ./.github/workflows/package-maintenance.yml" in wf
+
+
+def test_the_maintainer_preflight_passes_when_in_place():
+    assert maint.main(["--fixture", str(FIX / "maintainer-good.json")]) == 0
+
+
+@pytest.mark.parametrize("fixture,reason", [
+    ("maintainer-no-variable.json", "is not set"),
+    ("maintainer-wrong-role.json", "names a role other than"),
+    ("maintainer-any-branch.json", "not only main"),
+    ("maintainer-no-environment.json", "does not exist"),
+])
+def test_the_maintainer_preflight_fails_when_not_in_place(fixture, reason, capsys):
+    assert maint.main(["--fixture", str(BAD / fixture)]) == 1
+    assert reason in capsys.readouterr().out
+
+
+# --- every link the package gives resolves to something this repo publishes (FRC-CSO-MRA)
+
+def _resolves(url):
+    site = "https://samaydlette.com"
+    if re.fullmatch(re.escape(site) + r"/\.well-known/quarterly-review-\d{4}-\d{2}-\d{2}\.(json|md)", url):
+        return ".well-known/quarterly-review-*" in _bootstrap_keys()   # published by the maintainer once held
+    if url.startswith(site + "/.well-known/"):
+        name = url[len(site + "/.well-known/"):]
+        governed = {a["path"] for a in _json(REPO / "infrastructure" / "schemas" / "freshness-config.json")["artifacts"]}
+        twin = name[:-3] + ".json" if name.endswith(".md") else name  # a governed artifact's Markdown twin
+        return (f".well-known/{name}" in governed or f".well-known/{twin}" in governed
+                or (REPO / "website" / ".well-known" / name).is_file())
+    if url in (site, site + "/"):
+        return (REPO / "website" / "index.html").is_file()
+    if url.startswith(site + "/"):
+        return (REPO / "website" / url[len(site) + 1:].split("#")[0]).is_file()
+    if url.startswith(_ccm.REPO_URL + "/blob/main/"):
+        return (REPO / url[len(_ccm.REPO_URL + "/blob/main/"):].split("#")[0]).is_file()
+    if url.startswith("https://fedramp.gov/schemas/"):
+        return any((REPO / "infrastructure" / "schemas").glob("fedramp-*/" + url.rsplit("/", 1)[1]))
+    return False
+
+
+# The one deliberate outside link: the operator's LinkedIn profile, in the
+# simulated FedRAMP Security Inbox's contact line (AFC-CSO-INB) and the
+# no-engagement statement (DEC-194).
+DELIBERATE_EXTERNAL = {"https://www.linkedin.com/in/sa2/"}
+
+
+def test_every_link_in_the_cpo_and_ocr_resolves(built_cpo, rolling):
+    # Third-party resources' own websites (MAS-CSO-TPR) are outside this site by design.
+    cpo_own = {k: v for k, v in built_cpo.items() if k != "thirdPartyInformationResources"}
+    for doc in (cpo_own, rolling):
+        urls = set(re.findall(r"https://[^\s\"')<>]+", json.dumps(doc)))
+        assert urls
+        bad = sorted(u.rstrip(".,") for u in urls
+                     if u.rstrip(".,") not in DELIBERATE_EXTERNAL and not _resolves(u.rstrip(".,")))
+        assert not bad, bad
+
+
+def test_a_link_to_nothing_is_caught():
+    assert not _resolves("https://samaydlette.com/.well-known/not-published.json")
+    assert not _resolves(_ccm.REPO_URL + "/blob/main/docs/no-such-file.md")
diff --git a/tests/test_cmmc_mapping.py b/tests/test_cmmc_mapping.py
deleted file mode 100644
index 744f9ca2..00000000
--- a/tests/test_cmmc_mapping.py
+++ /dev/null
@@ -1,46 +0,0 @@
-# Task 5 acceptance: no CMMC requirement may be classified inherited/implemented
-# over an empty hub_controls set (vacuous inheritance through a crosswalk gap),
-# and 3.12.4 (maintain your own SSP) is the customer's responsibility.
-
-import importlib.util
-import json
-from pathlib import Path
-
-import pytest
-
-REPO = Path(__file__).resolve().parent.parent
-spec = importlib.util.spec_from_file_location("cmmc", REPO / "scripts" / "build-cmmc.py")
-cmmc = importlib.util.module_from_spec(spec)
-spec.loader.exec_module(cmmc)
-
-
-def test_guard_raises_on_vacuous_inheritance():
-    for cls, srm in [("fully-inherited", "inherited"), ("implemented", "inherited"),
-                     ("implemented", "osc-responsibility"), ("fully-inherited", "shared")]:
-        with pytest.raises(ValueError):
-            cmmc.guard_no_vacuous_inheritance("X", cls, srm, hub_controls=[])
-
-
-def test_guard_allows_customer_responsibility_with_no_hub():
-    # Empty hub_controls is fine as long as it is not claimed as inherited.
-    cmmc.guard_no_vacuous_inheritance("3.12.4", "customer-responsibility", "osc-responsibility", hub_controls=[])
-
-
-def test_guard_allows_inheritance_when_backed():
-    cmmc.guard_no_vacuous_inheritance("3.5.3", "fully-inherited", "inherited", hub_controls=["ia-2.1"])
-
-
-def test_3124_dispositioned_as_customer_responsibility():
-    disp = json.loads((REPO / "data/dispositions/beyond-moderate.json").read_text())
-    d = disp["cmmc_requirement_dispositions"]["3.12.4"]
-    assert d["class"] == "customer-responsibility"
-    assert d["srm"] == "osc-responsibility"
-
-
-def test_no_requirement_disposition_claims_inheritance_without_hub():
-    # Defensive: no requirement-level disposition may itself assert inheritance,
-    # since those carry no hub controls by construction.
-    disp = json.loads((REPO / "data/dispositions/beyond-moderate.json").read_text())
-    for req, d in disp["cmmc_requirement_dispositions"].items():
-        assert d.get("class") not in ("fully-inherited", "implemented"), req
-        assert d.get("srm") != "inherited", req
diff --git a/tests/test_codeql_zap_api_ingest.py b/tests/test_codeql_zap_api_ingest.py
new file mode 100644
index 00000000..42b6aa43
--- /dev/null
+++ b/tests/test_codeql_zap_api_ingest.py
@@ -0,0 +1,143 @@
+"""CodeQL alerts and the authenticated ZAP API scan reach the VDR (VDR-CSO-DET, DAC).
+
+CodeQL alerts (SAST of first-party code) become findings with a stable tracking
+id per alert, the rule as tool_id and the file as resource, and are decided
+through the decision register like every other vulnerability. The API scan's
+ZAP report is read by the same ZAP ingester as the site baseline, with its own
+tracking ids so the two scans' findings never merge. A given input that is
+missing or malformed stops the build: no scan never reads as zero findings.
+"""
+import importlib.util
+import json
+import subprocess
+import sys
+from pathlib import Path
+
+import pytest
+
+REPO = Path(__file__).resolve().parent.parent
+DET = REPO / "tests" / "fixtures" / "detection"
+ZAP = REPO / "tests" / "fixtures" / "zap"
+sys.path.insert(0, str(REPO / "scripts"))
+import _codeql  # noqa: E402
+import _zap_api  # noqa: E402
+
+
+def _load(name, file):
+    spec = importlib.util.spec_from_file_location(name, REPO / "scripts" / file)
+    m = importlib.util.module_from_spec(spec)
+    spec.loader.exec_module(m)
+    return m
+
+
+vdr = _load("vdr", "build-vdr-report.py")
+vg = _load("vuln_gate", "vuln-gate.py")
+
+
+def test_codeql_alert_becomes_a_finding():
+    [f] = _codeql.ingest_codeql(str(DET / "codeql.json"))
+    assert f == {
+        "source": "codeql", "tool_id": "py/path-injection", "tracking_id": "codeql-py/path-injection-7",
+        "title": "Uncontrolled data used in path expression",
+        "description": "This path depends on a user-provided value.", "severity": "HIGH",
+        "resource": "backend/main.py", "detected_at": "2026-11-03T05:41:00Z"}
+
+
+def _alert(number, rule="js/xss", state="open", **rule_extra):
+    return {"number": number, "state": state, "created_at": "2026-11-01T00:00:00Z",
+            "rule": {"id": rule, "description": "d", **rule_extra},
+            "most_recent_instance": {"location": {"path": "website/assets/js/trust.js"}, "message": {"text": "m"}}}
+
+
+def _write(tmp_path, alerts):
+    p = tmp_path / "codeql.json"
+    p.write_text(json.dumps({"analyses": [], "alerts": alerts}))
+    return str(p)
+
+
+def test_tracking_ids_are_per_alert_and_stable(tmp_path):
+    a = _codeql.ingest_codeql(_write(tmp_path, [_alert(3), _alert(4)]))
+    b = _codeql.ingest_codeql(_write(tmp_path, [_alert(4), _alert(3)]))
+    assert [f["tracking_id"] for f in a] == ["codeql-js/xss-3", "codeql-js/xss-4"]
+    assert {f["tracking_id"] for f in a} == {f["tracking_id"] for f in b}
+
+
+def test_only_open_alerts_are_findings(tmp_path):
+    fs = _codeql.ingest_codeql(_write(tmp_path, [_alert(1), _alert(2, state="dismissed"), _alert(3, state="fixed")]))
+    assert [f["tracking_id"] for f in fs] == ["codeql-js/xss-1"]
+
+
+@pytest.mark.parametrize("rule,want", [
+    ({"security_severity_level": "critical", "severity": "note"}, "CRITICAL"),
+    ({"security_severity_level": "low", "severity": "error"}, "LOW"),
+    ({"severity": "error"}, "HIGH"),
+    ({"severity": "warning"}, "MEDIUM"),
+    ({"severity": "note"}, "LOW"),
+    ({}, "MEDIUM"),
+])
+def test_severity_prefers_codeql_security_severity(rule, want):
+    assert _codeql.severity(rule) == want
+
+
+@pytest.mark.parametrize("content,match", [
+    (None, "not found"),
+    ("{not json", "not valid JSON"),
+    (json.dumps({"alerts": []}), "no alerts"),
+    (json.dumps({"analyses": [], "alerts": [{"state": "open", "rule": {"id": "py/x"}}]}), "no number"),
+])
+def test_codeql_input_given_but_unusable_fails_closed(tmp_path, content, match):
+    p = tmp_path / "codeql.json"
+    if content is not None:
+        p.write_text(content)
+    with pytest.raises(SystemExit, match=match):
+        _codeql.ingest_codeql(str(p))
+
+
+def test_no_codeql_input_means_no_findings():
+    assert _codeql.ingest_codeql(None) == []
+
+
+def test_codeql_findings_are_vulnerabilities_the_register_decides():
+    """A CodeQL finding is gated like a ZAP alert: unhandled without a decision."""
+    assert "codeql" in vdr.VULN_SOURCES and vdr.VULN_SOURCES == vg.VULN_SOURCES
+    [f] = _codeql.ingest_codeql(str(DET / "codeql.json"))
+    vulns = vg.vulns_from_vdr({"findings": [f]})
+    assert [v["id"] for v in vulns] == ["codeql-py/path-injection-7"]
+    assert vg.find_unhandled(vulns, {}) == vulns
+
+
+def test_codeql_finding_is_published_in_the_report():
+    report, _ = vdr.build_report(_codeql.ingest_codeql(str(DET / "codeql.json")), [], set(), {})
+    [pub] = [f for f in report["findings"] if f["source"] == "codeql"]
+    assert pub["tracking_id"] == "codeql-py/path-injection-7"
+    assert pub["tool_id"] == "py/path-injection" and pub["resource"] == "backend/main.py"
+
+
+def test_api_scan_findings_have_their_own_tracking_ids():
+    al = {"entries": []}
+    site = vdr.ingest_zap(str(ZAP / "report.json"), al)
+    api = _zap_api.ingest_zap_api(str(ZAP / "report.json"), vdr.ingest_zap, al)
+    assert {f["tracking_id"] for f in api} == {"zap-api-10038", "zap-api-10021", "zap-api-90004"}
+    assert not {f["tracking_id"] for f in api} & {f["tracking_id"] for f in site}
+    assert all(f["source"] == "zap" for f in api)
+    # Same alert type in both scans: two findings, decided separately.
+    assert len(vdr.dedupe_findings(site + api)) == len(site) + len(api)
+
+
+@pytest.mark.parametrize("content,match", [
+    (None, "not found"),
+    ("[]", "no site"),
+    ("{not json", "not valid JSON"),
+])
+def test_api_report_given_but_unusable_fails_closed(tmp_path, content, match):
+    p = tmp_path / "zap-api-report.json"
+    if content is not None:
+        p.write_text(content)
+    with pytest.raises(SystemExit, match=match):
+        _zap_api.ingest_zap_api(str(p), vdr.ingest_zap, {"entries": []})
+
+
+def test_builder_takes_both_inputs():
+    out = subprocess.run([sys.executable, str(REPO / "scripts" / "build-vdr-report.py"), "--help"],
+                         capture_output=True, text=True, check=True).stdout
+    assert "--codeql" in out and "--zap-api" in out
diff --git a/tests/test_common.py b/tests/test_common.py
index f68ec87c..31db88d7 100644
--- a/tests/test_common.py
+++ b/tests/test_common.py
@@ -23,8 +23,7 @@
 # ---------------------------------------------------------------------------
 # Status wins over origination: a control that is N/A or planned has no
 # inheritance story yet. Everything else projects the FedRAMP control-origination
-# onto the shared-responsibility vocabulary the CMMC SRM, coverage figures and
-# framework spokes all read.
+# onto the shared-responsibility vocabulary the published coverage figures read.
 @pytest.mark.parametrize("status,origination,expected", [
     # status short-circuits, whatever the origination says
     ("not-applicable", "inherited",           "not-applicable"),
diff --git a/tests/test_controls.py b/tests/test_controls.py
index fa0aae40..73840b65 100644
--- a/tests/test_controls.py
+++ b/tests/test_controls.py
@@ -26,6 +26,11 @@
 REPO = Path(__file__).resolve().parent.parent
 FIX_SIGNAL = REPO / "tests" / "fixtures" / "clean" / "ksi-signal.json"
 CATALOG = REPO / "infrastructure" / "schemas" / "ksi-catalog.json"
+# The KSI catalog as it stood when the SSP was retired (FedRAMP's mappings before
+# its 2026-10-13 revision). The parity test runs the projection on it, so the
+# projection's code stays pinned to the SSP it replaced; the current catalog is
+# FedRAMP's current mapping (tests/test_ksi_catalog_corpus.py).
+CATALOG_AT_RETIREMENT = REPO / "tests" / "fixtures" / "migration" / "ksi-catalog-2026-11-05.json"
 FROZEN = REPO / "tests" / "fixtures" / "migration" / "ssp-control-status-2026-11-05.json"
 
 sys.path.insert(0, str(REPO / "scripts"))
@@ -48,7 +53,7 @@ def _projection():
 
 def test_the_projection_matches_the_last_ssp_control_for_control():
     frozen = json.loads(FROZEN.read_text())
-    irs = _projection()
+    irs = _controls.load(FIX_SIGNAL, CATALOG_AT_RETIREMENT)
     assert len(irs) == frozen["implemented_requirements"] == 333
     got = {cid: list(v) for cid, v in _controls.status_map(irs).items()}
     assert got == frozen["controls"]
@@ -78,34 +83,7 @@ def test_a_failing_contributing_ksi_downgrades_its_controls():
     assert status == "partial"
 
 
-# --- the SDR carries the per-control record (SDR-CSF-CTF) ---------------------------
-
-def test_the_sdr_summarizes_every_projected_control():
-    sdr = _load("build_sdr", "build-sdr.py")
-    irs = _projection()
-    rows = sdr.build_rev5_controls(irs, json.loads(CATALOG.read_text()))
-    assert [r["control_id"] for r in rows] == [ir["control-id"] for ir in irs]
-    vocab = {"Implemented", "Partially Implemented", "Planned", "Alternative Implementation", "Not Applicable"}
-    for r, ir in zip(rows, irs, strict=True):
-        assert r["implementation_status"] in vocab, r["control_id"]
-        assert r["mechanisms"].startswith(ir["statements"][0]["remarks"])
-        assert r["parameters"] == [{"param_id": sp["param-id"], "values": sp.get("values", [])}
-                                   for sp in ir.get("set-parameters", [])]
-        for k in ("verification", "validation", "independent_verification", "independent_validation"):
-            assert r[k].strip(), (r["control_id"], k)
-    # Parameter values the FedRAMP profile sets are carried, not dropped.
-    assert sum(len(r["parameters"]) for r in rows) > 200
-
-
-def test_sdr_verification_points_at_the_contributing_ksis():
-    sdr = _load("build_sdr2", "build-sdr.py")
-    rows = sdr.build_rev5_controls(_projection(), json.loads(CATALOG.read_text()))
-    claimed = [r for r in rows if r["contributing_ksis"] and r["implementation_status"] != "Not Applicable"
-               and r["origination"] != "inherited"]
-    assert claimed
-    for r in claimed:
-        assert all(k in r["verification"] for k in r["contributing_ksis"]), r["control_id"]
-
+# --- the SDR carries the per-control record: tests/test_sdr.py ----------------------
 
 def test_the_sdr_builder_fails_closed_without_the_inventory(tmp_path):
     r = subprocess.run([sys.executable, str(REPO / "scripts" / "build-sdr.py"),
@@ -118,7 +96,7 @@ def test_the_sdr_builder_fails_closed_without_the_inventory(tmp_path):
 
 # --- the SSP is retired ------------------------------------------------------------
 
-CONSUMERS = ["build-sdr.py", "build-coverage.py", "build-cmmc.py", "inject-figures.py", "reconcile.py",
+CONSUMERS = ["build-sdr.py", "reconcile.py",
              "build-trust-center.py", "build-cpo.py", "build-ksi-signal.py", "_common.py", "verify-published.sh"]
 
 
diff --git a/tests/test_corroborate_checks.py b/tests/test_corroborate_checks.py
index 1e7f2d77..f2cb6efe 100644
--- a/tests/test_corroborate_checks.py
+++ b/tests/test_corroborate_checks.py
@@ -43,9 +43,27 @@ def test_signed_artifacts_come_from_the_governed_config_without_the_report_itsel
     assert all(a.get("bundle") for a in arts if a["kind"] == "bundle")
 
 
-def test_expected_identity_depends_on_cadence():
-    assert ck.expected_identity("deploy").endswith("/.github/workflows/deploy-with-opa.yml@refs/heads/main")
-    assert ck.expected_identity("nightly").endswith("/.github/workflows/evidence-nightly.yml@refs/heads/main")
+def test_expected_identities_are_the_files_writers_not_its_cadence():
+    """From scripts/_signers.py, which tests/test_publishers.py holds to the
+    workflows' publish steps."""
+    import _signers
+    wf = "https://github.com/sam-aydlette/samaydlette.com/.github/workflows/"
+    assert ck.expected_identities(".well-known/ksi-signal.json") == [wf + "deploy-with-opa.yml@refs/heads/main"]
+    assert ck.expected_identities(".well-known/ocr-issues.json") == [wf + "package-maintenance.yml@refs/heads/main"]
+    assert ck.expected_identities(".well-known/vdr-report.json") == [wf + "deploy-with-opa.yml@refs/heads/main",
+                                                                    wf + "evidence-nightly.yml@refs/heads/main"]
+    arts = ck.signed_artifacts(json.loads((REPO / "infrastructure" / "schemas" / "freshness-config.json").read_text()))
+    for a in arts:
+        assert a["identities"] == [_signers.IDENTITIES[k] for k in _signers.signers(a["artifact"])], a["artifact"]
+
+
+def test_known_bad_a_file_signed_by_a_workflow_that_does_not_write_it_differs():
+    f = fx("signatures-by-writer.json")
+    s = ck.judge_signatures(f["facts"], f["artifacts"])
+    assert s["compared"] == 6
+    assert sorted((x["artifact"], x["problem"]) for x in s["findings"]) == [
+        ("ocr-issues.json", "signed by an unexpected identity"),
+        ("vdr-report.json", "signed by an unexpected identity")]
 
 
 def test_known_bad_signatures_differ_on_each_artifact():
diff --git a/tests/test_cpo_trust_fields.py b/tests/test_cpo_trust_fields.py
new file mode 100644
index 00000000..b7df6e16
--- /dev/null
+++ b/tests/test_cpo_trust_fields.py
@@ -0,0 +1,98 @@
+"""Group 5's fields in the Certification Package Overview: the trust center and
+secure configuration guidance (CDS-CSO-PUB, CDS-CSO-UTC, SCG-CSO-AUP), the
+third-party information resources (MAS-CSO-TPR) and the assessor's overall
+summary, quoted verbatim from its signed set (CPO-CSO-OSA)."""
+import importlib.util
+import json
+import re
+import sys
+import tempfile
+from datetime import datetime, timezone
+from pathlib import Path
+
+import pytest
+
+REPO = Path(__file__).resolve().parent.parent
+sys.path.insert(0, str(REPO / "scripts"))
+import _assessor  # noqa: E402
+import _ccm  # noqa: E402
+import _fedramp_schema as fs  # noqa: E402
+import _offering  # noqa: E402
+import _tpr  # noqa: E402
+
+spec = importlib.util.spec_from_file_location("build_cpo_g5", REPO / "scripts" / "build-cpo.py")
+cpo = importlib.util.module_from_spec(spec)
+spec.loader.exec_module(cpo)
+
+NOW = datetime(2026, 11, 5, 12, tzinfo=timezone.utc)
+SIGNAL = json.loads((REPO / "tests" / "fixtures" / "clean" / "ksi-signal.json").read_text())
+PROFILE = json.loads((REPO / "data" / "system-profile.json").read_text())
+FRESH = {a["path"] for a in json.loads((REPO / "infrastructure" / "schemas" / "freshness-config.json").read_text())
+         ["artifacts"]}
+
+
+def _assessment():
+    with tempfile.TemporaryDirectory() as d:
+        s = Path(d) / "simulated-assessment.json"
+        s.write_text((REPO / "tests" / "fixtures" / "assessor" / "simulated-set.json").read_text())
+        return _assessor.load_assessment(s, s, verifier=lambda *_a: True, expect_commit="0" * 40,
+                                         expect_signal_id="00000000-0000-4000-8000-000000000001")
+
+
+def _build(assessment=None):
+    return cpo.build(_offering.load(), PROFILE, SIGNAL, _ccm.load(_ccm.CALENDAR_PATH, NOW.date()), {}, NOW,
+                     cpo.boundary_groups(), _assessment() if assessment is None else assessment)
+
+
+def test_the_cpo_with_group_5_fields_validates_against_fedramps_schema():
+    assert fs.validate(_build(), "cpo") == []
+
+
+def test_the_trust_center_entry_is_the_landing_page_with_access_instructions():
+    tc = _build()["serviceProperties"]["trustCenter"]
+    assert tc["url"] == "https://samaydlette.com/trust/index.html"
+    assert (REPO / "website" / "trust" / "index.html").is_file()
+    assert tc["authenticationRequired"] is False and "No access request is needed" in tc["accessRequestInstructions"]
+
+
+def test_the_secure_configuration_guidance_links_the_published_guide():
+    scg = _build()["serviceProperties"]["secureConfigurationGuidance"]
+    assert scg["url"] == "https://samaydlette.com/.well-known/secure-configuration-guide.md"
+    assert ".well-known/secure-configuration-guide.json" in FRESH
+
+
+def test_third_party_resources_are_the_decided_records():
+    doc = _build()
+    assert doc["thirdPartyInformationResources"] == _tpr.cpo_third_party_information_resources()
+    assert doc["thirdPartyInformationResources"]["nonCertified"]
+
+
+def test_the_overall_summary_is_the_assessors_record_verbatim():
+    recs = _assessment()
+    ia = _build(recs)["providerExtensions"]["independentAssessment"]
+    assert ia["overallSummary"] == _assessor.overall_summary(recs)
+    assert "IVV-IAS-OSA" in ia["overallSummary"]["text"] and ia["simulated"] is True
+    assert "assessor" not in _build(recs)  # no FedRAMP assessor ID exists; none is invented
+    md = cpo.render_markdown(_build(recs))
+    assert ia["overallSummary"]["text"][:80] in md
+
+
+def test_known_bad_an_assessment_without_a_summary_fails():
+    recs = [r for r in _assessment() if r["kind"] != "summary"]
+    with pytest.raises(SystemExit, match="no overall summary"):
+        _build(recs)
+
+
+def test_the_cpo_refuses_to_build_without_the_assessment():
+    with pytest.raises(SystemExit):
+        cpo.main(["--output", "/dev/null"])
+
+
+def test_the_deploy_and_the_maintainer_give_the_cpo_the_assessment():
+    wf = REPO / ".github" / "workflows"
+    deploy = (wf / "deploy-with-opa.yml").read_text()
+    step = deploy.split("- name: Build Certification Package Overview (CPO)", 1)[1].split("\n    - name:", 1)[0]
+    assert "--assessment simulated-assessment.json" in step
+    maint = (wf / "package-maintenance.yml").read_text()
+    step = maint.split("- name: Rebuild the SDR, OCR and CPO at the deployed commit", 1)[1].split("\n    - name:", 1)[0]
+    assert len(re.findall(r"^\s+\$ASSESSMENT$", step, re.M)) == 3 and "--assessment $W/simulated-assessment.json" in step
diff --git a/tests/test_cr26_vdr.py b/tests/test_cr26_vdr.py
index 6351753c..ae8bde2a 100644
--- a/tests/test_cr26_vdr.py
+++ b/tests/test_cr26_vdr.py
@@ -10,9 +10,14 @@
   jsonschema;
 - each record carries the joins the schemas have no field for (component, CVE,
   check, decision) under providerExtensions;
-- report periods run from the previous report's end (VER-RPT-PER);
-- the history keeps a finding that left the VDR, closed as Remediated, for a
-  year, then drops it.
+- report periods run from the previous report's end (VER-RPT-PER), and each
+  period report summarizes the period's activity, linking the runtime results;
+- records carry the historical rating and rating history, the decision's
+  planned reduction (else the deadline), supplementary information from the
+  decision, an overdue explanation about the overdue status, and a detection
+  time from a decision that names the record;
+- the history keeps a finding that left the VDR for a year, with a final
+  disposition only from evidence, and carries closed decisions.
 """
 import importlib.util
 import json
@@ -137,7 +142,8 @@ def test_periods_run_from_the_previous_report():
     assert vdt["reportPeriod"] == {"from": "2026-11-04T15:00:00+00:00", "to": NOW.isoformat()}
     assert avi["reportPeriod"]["from"] == "2026-11-04T15:00:00+00:00"
     first, _, _ = _build()
-    assert first["reportPeriod"]["from"] == "2026-03-01T00:00:00+00:00"   # earliest detection
+    # The earliest detection: the suppressed CKV_AWS_68, known since DEC-104 was decided.
+    assert first["reportPeriod"]["from"] == "2026-01-01T00:00:00+00:00"
 
 
 def test_a_previous_report_ending_in_the_future_stops_the_build():
@@ -146,16 +152,24 @@ def test_a_previous_report_ending_in_the_future_stops_the_build():
         _build(prev_vdt=prev)
 
 
+def _detection_ok(*feeds, checked_at="2026-11-06T14:59:00+00:00"):
+    return {"schema": "detection/1", "checked_at": checked_at, "result": "ok",
+            "feeds": [{"feed": f, "file": f"{f}.json", "status": "ok", "count": 0} for f in feeds]}
+
+
 def test_history_keeps_a_finding_that_left_the_vdr_then_drops_it_after_a_year():
     _, _, mrh = _build()
     vdr = json.loads(json.dumps(VDR))
     vdr["findings"] = [f for f in vdr["findings"] if f["tracking_id"] != "grype-CVE-2099-0001-thumbnailer"]
+    # Grype ran in the build that no longer reports it: remediated, from evidence.
+    vdr["methodology"] = {"detection": _detection_ok("grype", "checkov")}
     _, _, later = _build(vdr=vdr, prev_mrh=mrh, now=NOW + timedelta(days=1))
     gone = next(r for r in later["activeVulnerabilities"]
                 if r["providerTrackingId"] == "grype-CVE-2099-0001-thumbnailer")
     assert gone["finalDisposition"] == "Remediated"
+    assert gone["providerExtensions"]["dispositionBasis"].startswith("grype ran in the VDR build checked")
     assert gone["providerExtensions"]["noLongerReportedAt"] == (NOW + timedelta(days=1)).isoformat()
-    assert "projectedNextReduction" not in gone and gone["overdueStatus"] == {"isOverdue": False}
+    assert "projectedNextReduction" not in gone and gone["overdueStatus"]["isOverdue"] is False
     assert fs.validate(later, "mrh") == []
     # The time it left is kept, not reset, on later runs; after a year it is dropped.
     _, _, still = _build(vdr=vdr, prev_mrh=later, now=NOW + timedelta(days=200))
@@ -235,3 +249,315 @@ def test_an_unreadable_previous_report_stops_the_build_rather_than_dropping_hist
                         "--out-dir", str(tmp_path)], capture_output=True, text=True)
     assert r.returncode != 0 and "unreadable" in r.stderr
     assert not list(tmp_path.glob("vdr-*"))
+
+
+# --- what each record says (VER-RPT-VDT, VER-RPT-AVI) -------------------------------
+
+def _register(edit):
+    """The fixture register with `edit(records_by_id)` applied, validated like the real one."""
+    doc = json.loads((FIX / "decisions.json").read_text())
+    edit({r["id"]: r for r in doc["decisions"]})
+    return _decisions.validate(doc)
+
+
+def _by_id(doc, accepted=False):
+    rows = doc["acceptedVulnerabilities"] if accepted else doc["vulnerabilities"]
+    return {(r["vulnerabilityDetail"] if accepted else r)["providerTrackingId"]:
+            (r["vulnerabilityDetail"] if accepted else r) for r in rows}
+
+
+def test_records_carry_their_historical_rating_and_rating_history():
+    vdr = json.loads(json.dumps(VDR))
+    f = vdr["findings"][0]
+    f["historical_pain"] = "N4"
+    f["rating_history"] = [
+        {"at": "2026-08-06T14:00:00+00:00", "pain": "N4", "lev": True, "irv": True, "reason": "first evaluation"},
+        {"at": "2026-10-14T10:00:00+00:00", "pain": "N3", "lev": True, "irv": True, "reason": "re-evaluation: pain N4->N3"}]
+    vdt, _, _ = _build(vdr=vdr)
+    ext = _by_id(vdt)[f["tracking_id"]]["providerExtensions"]
+    assert ext["historicalRating"] == 4
+    assert [(h["at"], h["rating"], h["reason"]) for h in ext["ratingHistory"]] == [
+        ("2026-08-06T14:00:00+00:00", 4, "first evaluation"),
+        ("2026-10-14T10:00:00+00:00", 3, "re-evaluation: pain N4->N3")]
+    assert fs.validate(vdt, "vdt") == []
+
+
+def test_a_decision_sets_the_next_reduction_and_the_deadline_is_only_the_fallback():
+    vdr = json.loads(json.dumps(VDR))
+    vdr["findings"][0]["decision_id"] = "DEC-105"   # open N3 finding, deadline 2026-11-20
+
+    def plan(target):
+        def edit(recs):
+            recs["DEC-105"]["planned_reduction"] = {"date": "2026-11-12", "target_pain": target}
+        return _register(edit)
+    vdt, _, _ = mod.build(vdr, plan("N1"), None, None, None, NOW)
+    rec = _by_id(vdt)["grype-CVE-2099-0001-thumbnailer"]
+    assert rec["projectedNextReduction"] == {"estimatedAt": "2026-11-12T00:00:00+00:00", "targetRating": 1}
+    assert rec["providerExtensions"]["projectionBasis"] == "DEC-105 planned_reduction"
+    # A plan that reduces nothing is not a reduction: the deadline stands, and says why.
+    vdt, _, _ = mod.build(vdr, plan("N3"), None, None, None, NOW)
+    rec = _by_id(vdt)["grype-CVE-2099-0001-thumbnailer"]
+    assert rec["projectedNextReduction"] == {"estimatedAt": "2026-11-20T00:00:00+00:00", "targetRating": 0}
+    assert "not below the current rating" in rec["providerExtensions"]["projectionBasis"]
+    # No plan: the remediation deadline.
+    vdt, _, _ = _build()
+    assert _by_id(vdt)["grype-CVE-2099-0001-thumbnailer"]["providerExtensions"]["projectionBasis"] == \
+        "remediation deadline (no planned reduction recorded)"
+
+
+def test_supplementary_information_comes_from_the_decision():
+    vdt, avi, _ = _build()
+    fp = _by_id(vdt)["zap-10099-article"]["supplementaryRiskInformation"]
+    assert fp.startswith("DEC-103 (false-positive; decided 2026-01-01, review by 2027-01-01): "
+                         "The rule matches article prose, not code.")
+    # The AVI carries the justification as the rationale; the supplementary
+    # information is the rest of the decision, not a copy of it.
+    acc = _by_id(avi, accepted=True)["CKV_AWS_68"]["supplementaryRiskInformation"]
+    assert acc.startswith("DEC-104 (risk-accepted; decided 2026-01-01, review by 2027-01-01).")
+    assert "Cost trade-off" not in acc
+    assert all(a["vulnerabilityDetail"].get("supplementaryRiskInformation") for a in avi["acceptedVulnerabilities"]
+               if a["vulnerabilityDetail"]["providerExtensions"]["decisionId"])
+
+
+def test_overdue_explanations_explain_the_overdue_status_not_the_suppression():
+    vdr = json.loads(json.dumps(VDR))
+    vdr["findings"][1]["remediation_due_at"] = "2026-09-23T13:51:28+00:00"   # overdue, DEC-101 accepts it
+    vdt, avi, _ = _build(vdr=vdr)
+    every = list(_by_id(vdt).values()) + list(_by_id(avi, accepted=True).values())
+    assert not any("documented suppression" in r["overdueStatus"].get("explanation", "") for r in every)
+    over = _by_id(avi, accepted=True)["checkov-CKV_AWS_310-website"]["overdueStatus"]
+    assert over == {"isOverdue": True, "explanation": (
+        "Overdue: its remediation deadline, 2026-09-23, passed without remediation. It is still open because "
+        "DEC-101 accepts it (risk-accepted, decided 2026-01-01), so no remediation is planned.")}
+    assert _by_id(vdt)["zap-10099-article"]["overdueStatus"] == {
+        "isOverdue": False, "explanation": "Not overdue: closed as False Positive under DEC-103."}
+    mav = _by_id(avi, accepted=True)["dependabot-GHSA-xxxx-yyyy-zzzz"]["overdueStatus"]
+    assert mav["isOverdue"] and mav["explanation"].startswith("Overdue: not fully mitigated or remediated within")
+
+
+def test_detection_time_comes_from_a_decision_that_names_the_record():
+    def edit(recs):
+        # The ZAP finding was found in a manual scan before the pipeline's scanner saw it.
+        recs["DEC-103"]["applies_to"] = {"check_ids": [], "vuln_ids": ["zap-10099-article"], "resources": []}
+        recs["DEC-103"]["original_detection_date"] = "2026-07-01"
+        # A decision about a check across resources dates the check, not each resource.
+        recs["DEC-101"]["original_detection_date"] = "2026-02-01"
+    vdt, avi, _ = mod.build(VDR, _register(edit), None, None, None, NOW)
+    zap = _by_id(vdt)["zap-10099-article"]
+    assert zap["detection"]["detectedAt"] == "2026-07-01T00:00:00+00:00"
+    assert zap["providerExtensions"]["detectedAtBasis"].startswith("DEC-103 original_detection_date")
+    assert zap["providerExtensions"]["firstReportedAt"] == "2026-08-06T13:51:28+00:00"
+    acc = _by_id(avi, accepted=True)
+    assert acc["checkov-CKV_AWS_310-website"]["detection"]["detectedAt"] == "2026-08-06T13:51:28+00:00"
+    # A suppressed check is never reported by a scanner: its decision dates it.
+    assert acc["CKV_AWS_68"]["detection"]["detectedAt"] == "2026-01-01T00:00:00+00:00"
+    assert acc["CKV_AWS_68"]["providerExtensions"]["detectedAtBasis"].startswith("DEC-104 decided_on")
+
+
+def test_a_suppression_names_the_resources_its_decision_affects():
+    vdr = json.loads(json.dumps(VDR))
+    vdr["risk_accepted"][0].update(affected_resources=["aws-cloudfront-distribution"],
+                                   component_id="aws::cdn_distribution::website", irv_basis="inventory")
+    _, avi, _ = _build(vdr=vdr)
+    ext = _by_id(avi, accepted=True)["CKV_AWS_68"]["providerExtensions"]
+    assert ext["affectedResources"] == ["aws-cloudfront-distribution"]
+    assert ext["componentId"] == "aws::cdn_distribution::website"
+
+
+# --- history: a final disposition only from evidence (VER-TFR-MRH) -------------------
+
+def _gone(vdr_edit, prev=None, now=NOW + timedelta(days=1), register=None):
+    """Build, drop the open grype finding, apply `vdr_edit`, rebuild with the first history."""
+    _, _, mrh = _build()
+    vdr = json.loads(json.dumps(VDR))
+    vdr["findings"] = [f for f in vdr["findings"] if f["tracking_id"] != "grype-CVE-2099-0001-thumbnailer"]
+    vdr_edit(vdr)
+    _, _, later = mod.build(vdr, register or REGISTER, None, None, prev or mrh, now)
+    assert fs.validate(later, "mrh") == []
+    return vdr, later, next(r for r in later["activeVulnerabilities"]
+                            if r["providerTrackingId"] == "grype-CVE-2099-0001-thumbnailer")
+
+
+def test_a_record_that_vanished_without_evidence_has_no_final_disposition():
+    vdr, later, gone = _gone(lambda v: None)          # no detection summary: coverage not shown
+    assert "finalDisposition" not in gone
+    assert gone["providerExtensions"]["noLongerReportedReason"] == "unknown"
+    assert gone["providerExtensions"]["noLongerReportedBasis"].startswith("no evidence of why")
+    # A failed scan is no evidence either.
+    _, _, failed = _gone(lambda v: v.update(methodology={"detection": {
+        **_detection_ok("grype"), "feeds": [{"feed": "grype", "status": "failed"}]}}))
+    assert "finalDisposition" not in failed
+    # A closed decision that arrives later settles it.
+    def closed(recs):
+        recs["DEC-105"].update(status="closed", disposition="remediated", closed_on="2026-11-07",
+                               applies_to={"check_ids": [], "vuln_ids": ["CVE-2099-0001"], "resources": []})
+    _, _, settled = _gone(lambda v: None, prev=later, now=NOW + timedelta(days=3), register=_register(closed))
+    assert settled["finalDisposition"] == "Remediated"
+    assert settled["providerExtensions"]["dispositionBasis"] == "DEC-105 closed as remediated on 2026-11-07"
+    assert settled["providerExtensions"]["noLongerReportedAt"] == gone["providerExtensions"]["noLongerReportedAt"]
+
+
+def test_an_unsupported_remediated_from_an_earlier_history_is_withdrawn():
+    _, _, mrh = _build()
+    vdr = json.loads(json.dumps(VDR))
+    vdr["findings"] = [f for f in vdr["findings"] if f["tracking_id"] != "grype-CVE-2099-0001-thumbnailer"]
+    old = json.loads(json.dumps(mrh))
+    for r in old["activeVulnerabilities"]:
+        if r["providerTrackingId"] == "grype-CVE-2099-0001-thumbnailer":
+            r["finalDisposition"] = "Remediated"         # what the earlier builder wrote, with no evidence
+            r["providerExtensions"]["noLongerReportedAt"] = NOW.isoformat()
+    _, _, later = _build(vdr=vdr, prev_mrh=old, now=NOW + timedelta(days=1))
+    gone = next(r for r in later["activeVulnerabilities"] if r["providerTrackingId"] == "grype-CVE-2099-0001-thumbnailer")
+    assert "finalDisposition" not in gone and gone["providerExtensions"]["noLongerReportedReason"] == "unknown"
+
+
+def test_a_check_that_became_a_suppression_is_not_remediated():
+    _, _, mrh = _build()
+    vdr = json.loads(json.dumps(VDR))
+    vdr["findings"] = [f for f in vdr["findings"] if f["tracking_id"] != "checkov-CKV_AWS_20-site"]
+    vdr["methodology"] = {"detection": _detection_ok("checkov")}
+    vdr["risk_accepted"].append({**vdr["risk_accepted"][0], "tracking_id": "CKV_AWS_20", "tool_id": "CKV_AWS_20",
+                                 "decision_id": "DEC-102"})
+    _, _, later = _build(vdr=vdr, prev_mrh=mrh, now=NOW + timedelta(days=1))
+    gone = next(r for r in later["activeVulnerabilities"] if r["providerTrackingId"] == "checkov-CKV_AWS_20-site")
+    assert "finalDisposition" not in gone
+    assert gone["providerExtensions"]["noLongerReportedReason"] == "suppressed"
+    # A false-positive suppression is a final disposition, from the decision.
+    vdr["risk_accepted"].pop()
+    vdr["false_positives"] = [{"tracking_id": "CKV_AWS_20", "tool_id": "CKV_AWS_20", "decision_id": "DEC-103",
+                               "current_disposition": "false-positive"}]
+    _, _, later = _build(vdr=vdr, prev_mrh=mrh, now=NOW + timedelta(days=1))
+    gone = next(r for r in later["activeVulnerabilities"] if r["providerTrackingId"] == "checkov-CKV_AWS_20-site")
+    assert gone["finalDisposition"] == "False Positive"
+
+
+def test_a_vanished_zap_finding_is_remediated_only_after_a_later_scan():
+    def dast(when):
+        return {"methodology": {"dast": {"scanner": "zap", "status": "ok", "generated_at": when}}}
+    last = NOW.isoformat()
+    assert mod._coverage("zap", dast("2026-11-04T00:00:00+00:00"), last) is None   # the scan that reported it
+    assert mod._coverage("zap", dast("2026-11-06T00:00:00+00:00"), last).startswith("the ZAP scan of 2026-11-06")
+    assert mod._coverage("zap", {"methodology": {}}, last) is None
+    # A record that was a false positive when last reported keeps that disposition.
+    _, _, mrh = _build()
+    vdr = json.loads(json.dumps(VDR))
+    vdr["findings"] = [f for f in vdr["findings"] if f["tracking_id"] != "zap-10099-article"]
+    _, _, later = _build(vdr=vdr, prev_mrh=mrh, now=NOW + timedelta(days=1))
+    fp = next(r for r in later["activeVulnerabilities"] if r["providerTrackingId"] == "zap-10099-article")
+    assert fp["finalDisposition"] == "False Positive"
+
+
+def test_closed_decisions_are_backfilled_into_the_history_once():
+    def edit(recs):
+        recs["DEC-105"].update(status="closed", disposition="remediated", closed_on="2026-06-18",
+                               original_detection_date="2026-05-06", former_id="POAM-005",
+                               source={"detector": "Manual review", "original_risk_rating": "moderate"})
+    reg = _register(edit)
+    vdr = json.loads(json.dumps(VDR))
+    vdr["findings"] = [f for f in vdr["findings"] if f["decision_id"] != "DEC-105"]
+    _, _, mrh = mod.build(vdr, reg, None, None, None, NOW)
+    back = [r for r in mrh["activeVulnerabilities"] if r["providerTrackingId"] == "DEC-105"]
+    assert len(back) == 1
+    assert back[0]["finalDisposition"] == "Remediated"
+    assert back[0]["detection"] == {"detectedAt": "2026-05-06T00:00:00+00:00", "detectionSource": "Manual review"}
+    assert back[0]["providerExtensions"]["backfilledFromDecision"] is True
+    assert back[0]["providerExtensions"]["formerId"] == "POAM-005"
+    assert fs.validate(mrh, "mrh") == []
+    # Carried forward: rebuilt from the register, never duplicated; dropped a year after closing.
+    _, _, again = mod.build(vdr, reg, None, None, mrh, NOW + timedelta(days=1))
+    assert [r["providerTrackingId"] for r in again["activeVulnerabilities"]].count("DEC-105") == 1
+    _, _, aged = mod.build(vdr, reg, None, None, again, datetime(2027, 6, 20, tzinfo=timezone.utc))
+    assert "DEC-105" not in _ids(aged["activeVulnerabilities"])
+
+
+# --- the period's activity (VER-RPT-PER) ---------------------------------------------
+
+def _with_activity():
+    vdr = json.loads(json.dumps(VDR))
+    vdr["emitted_at"] = NOW.isoformat()
+    vdr["findings"][0].update(first_detected="2026-11-05T09:00:00+00:00", first_evaluated="2026-11-05T09:00:00+00:00",
+                              completed_reductions=[{"at": "2026-11-05T10:00:00+00:00", "from": "N4", "to": "N3"}])
+    vdr["methodology"] = {
+        "detection": {**_detection_ok("grype", "checkov", checked_at="2026-11-05T14:59:00+00:00"),
+                      "feeds": [{"feed": "grype", "file": "grype-js.json", "status": "ok", "count": 1,
+                                 "source_date": "2026-11-05T06:00:00+00:00"},
+                                {"feed": "kev", "file": "kev-catalog.json", "status": "ok", "count": 9,
+                                 "source_date": "2026-11-04T20:00:00+00:00"},
+                                {"feed": "previous-vdr", "file": "previous-vdr-report.json", "status": "ok"}]},
+        "dast": {"scanner": "zap", "status": "ok", "generated_at": "2026-11-05T12:47:20+00:00", "alerts": 4},
+        "runtime_verification": {"uri": "https://samaydlette.com/.well-known/ksi-signal-runtime.json",
+                                 "verified": True, "fresh": True, "emitted_at": "2026-11-05T11:00:00Z",
+                                 "signal_id": "rt-1", "validations": 5, "failed": 1, "divergence": "converged"}}
+    return vdr
+
+
+def test_each_period_report_summarizes_the_periods_activity():
+    prev = {"reportPeriod": {"from": "2026-11-04T15:00:00+00:00", "to": "2026-11-05T03:00:00+00:00"}}
+    vdt, avi, _ = _build(vdr=_with_activity(), prev_vdt=prev, prev_avi=prev)
+    for doc in (vdt, avi):
+        s = doc["providerExtensions"]["activitySummary"]
+        assert s["period"] == doc["reportPeriod"]
+        assert s["detections"] == [{"providerTrackingId": "grype-CVE-2099-0001-thumbnailer",
+                                    "at": "2026-11-05T09:00:00+00:00"}]
+        assert s["reductions"] == [{"providerTrackingId": "grype-CVE-2099-0001-thumbnailer",
+                                    "at": "2026-11-05T10:00:00+00:00", "from": "N4", "to": "N3"}]
+        scans = {x["activity"]: x for x in s["scans"]}
+        assert scans["Grype software composition scan (grype-js.json)"]["at"] == "2026-11-05T14:59:00+00:00"
+        assert scans["Grype software composition scan (grype-js.json)"]["vulnerabilityDatabaseBuiltAt"] == \
+            "2026-11-05T06:00:00+00:00"
+        assert scans["CISA KEV catalog (kev-catalog.json)"]["inPeriod"] is False   # published before the period
+        assert scans["OWASP ZAP dynamic scan of the site"]["inPeriod"] is True
+        assert not any("previous-vdr" in k for k in scans)
+        rt = s["runtimeVerification"]
+        assert rt["uri"] == "https://samaydlette.com/.well-known/ksi-signal-runtime.json" and rt["signalId"] == "rt-1"
+        assert s["counts"]["runtimeRunsInPeriod"] == 1 and s["counts"]["runtimeFailuresInPeriod"] == 1
+        assert s["counts"]["detections"] == 1 and s["counts"]["reductions"] == 1
+    assert fs.validate(vdt, "vdt") == [] and fs.validate(avi, "avi") == []
+
+
+def test_an_unverified_runtime_run_is_linked_but_not_counted():
+    vdr = _with_activity()
+    vdr["methodology"]["runtime_verification"].update(verified=False, validations=None, failed=None,
+                                                      reason="runtime signal signature does not verify")
+    vdt, _, _ = _build(vdr=vdr)
+    s = vdt["providerExtensions"]["activitySummary"]
+    assert s["counts"]["runtimeRunsInPeriod"] == 0 and "not verified" in s["runtimeVerification"]["note"]
+
+
+def test_the_markdown_reports_carry_the_activity_and_link_the_runtime_results(tmp_path):
+    vdr = tmp_path / "vdr.json"
+    vdr.write_text(json.dumps(_with_activity()))
+    r = subprocess.run([sys.executable, str(SCRIPT), "--vdr", str(vdr), "--decisions", str(FIX / "decisions.json"),
+                        "--out-dir", str(tmp_path)], capture_output=True, text=True)
+    assert r.returncode == 0, r.stderr
+    for name in ("vdr-detail-report.md", "vdr-accepted-vulnerabilities.md"):
+        text = (tmp_path / name).read_text()
+        assert "## Activity this period" in text and "| OWASP ZAP dynamic scan of the site |" in text
+        assert "(https://samaydlette.com/.well-known/ksi-signal-runtime.json)" in text
+
+
+def test_every_report_carries_the_offerings_fedramp_id(tmp_path):
+    want = json.loads((REPO / "data" / "cds" / "offering.json").read_text())["fedramp_id"]
+    vdt, avi, mrh = _build()
+    for doc in (vdt, avi, mrh):
+        assert doc["providerExtensions"]["fedRampId"] == want
+
+
+def test_a_missing_fedramp_id_stops_the_build(tmp_path):
+    p = tmp_path / "offering.json"
+    p.write_text("{}")
+    with pytest.raises(SystemExit, match="fedramp_id is missing"):
+        mod.fedramp_id(p)
+
+
+def test_every_retained_runtime_run_in_the_period_is_counted():
+    vdr = _with_activity()
+    vdr["methodology"]["runtime_verification"]["run_history"] = [
+        {"signal_id": "rt-0", "emitted_at": "2026-11-04T23:00:00Z", "validations": 5, "failed": 0},
+        {"signal_id": "rt-a", "emitted_at": "2026-11-05T05:00:00Z", "validations": 5, "failed": 2},
+        {"signal_id": "rt-1", "emitted_at": "2026-11-05T11:00:00Z", "validations": 5, "failed": 1}]
+    prev = {"reportPeriod": {"from": "2026-11-05T03:00:00+00:00", "to": "2026-11-05T03:00:00+00:00"}}
+    vdt, _, _ = _build(vdr=vdr, prev_vdt=prev)
+    s = vdt["providerExtensions"]["activitySummary"]
+    assert s["counts"]["runtimeRunsInPeriod"] == 2 and s["counts"]["runtimeFailuresInPeriod"] == 2
+    assert fs.validate(vdt, "vdt") == []
diff --git a/tests/test_dast_cognito_token.py b/tests/test_dast_cognito_token.py
new file mode 100644
index 00000000..866e33cd
--- /dev/null
+++ b/tests/test_dast_cognito_token.py
@@ -0,0 +1,178 @@
+"""The DAST scanner's Cognito sign-in (scripts/dast-cognito-token.py).
+
+SRP-6a and TOTP are checked against fixed vectors: TOTP against RFC 6238's
+own, SRP against a vector cross-checked with pycognito 2024.5.1 (the PASSWORD_VERIFIER
+signature for a fixed secret exponent, server value, salt, secret block and
+time). The flow is checked against a scripted Cognito: the password never
+leaves the process, only the token reaches the owner-only --out file, and an unexpected challenge
+stops the sign-in.
+"""
+import importlib.util
+import io
+import json
+from contextlib import redirect_stderr, redirect_stdout
+from datetime import datetime, timezone
+from pathlib import Path
+
+import pytest
+
+REPO = Path(__file__).resolve().parent.parent
+spec = importlib.util.spec_from_file_location("dast_token", REPO / "scripts" / "dast-cognito-token.py")
+tok = importlib.util.module_from_spec(spec)
+spec.loader.exec_module(tok)
+
+POOL = "us-east-2_AbCdEfGhI"
+PASSWORD = "Correct-Horse-Battery-9!"
+SEED = "GEZDGNBVGY3TQOJQGEZDGNBVGY3TQOJQ"  # RFC 6238's SHA-1 key, base32
+
+
+@pytest.mark.parametrize("t,code", [(59, "94287082"), (1111111109, "07081804"), (1111111111, "14050471"),
+                                    (1234567890, "89005924"), (2000000000, "69279037")])
+def test_totp_matches_rfc6238(t, code):
+    assert tok.totp(SEED, t, digits=8) == code
+    assert tok.totp(SEED.lower(), t) == code[-6:]
+
+
+def test_srp_password_verifier_matches_the_reference_vector():
+    a = 0x1234567890ABCDEF1234567890ABCDEF1234567890ABCDEF % tok.N
+    big_b = pow(2, 0xDEADBEEFCAFEBABE1234, tok.N)
+    params = {"USER_ID_FOR_SRP": "uuid-user-1", "SRP_B": format(big_b, "x"), "SALT": "8f3a1c",
+              "SECRET_BLOCK": "c2VjcmV0YmxvY2tieXRlcw=="}
+    now = datetime(2026, 11, 5, 7, 3, 9, tzinfo=timezone.utc)
+    out = tok.password_verifier(POOL, PASSWORD, params, a, tok.large_a(a), now)
+    assert out == {"TIMESTAMP": "Thu Nov 5 07:03:09 UTC 2026", "USERNAME": "uuid-user-1",
+                   "PASSWORD_CLAIM_SECRET_BLOCK": "c2VjcmV0YmxvY2tieXRlcw==",
+                   "PASSWORD_CLAIM_SIGNATURE": "MFnkJNc5ZDDsrbP0nbK49s56hPcd65Q5CD50xT1T1Zs="}
+
+
+def test_srp_refuses_a_degenerate_server_value():
+    a = tok.small_a()
+    with pytest.raises(tok.AuthError, match="B mod N"):
+        tok.password_key(POOL, "u", PASSWORD, tok.large_a(a), a, tok.N * 3, "00")
+
+
+def test_pad_hex_and_timestamp_forms():
+    assert tok.pad_hex(0xF) == "0f" and tok.pad_hex(0x8F) == "008f" and tok.pad_hex(0x7F) == "7f"
+    assert tok.cognito_timestamp(datetime(2026, 1, 12, 23, 4, 5, tzinfo=timezone.utc)) == "Mon Jan 12 23:04:05 UTC 2026"
+
+
+def test_region_comes_from_the_pool_id():
+    assert tok.region_of(POOL) == "us-east-2"
+    with pytest.raises(tok.AuthError):
+        tok.region_of("not-a-pool")
+
+
+class Cognito:
+    """A scripted Cognito: answers each call in turn and records the bodies."""
+
+    def __init__(self, answers):
+        self.answers = list(answers)
+        self.calls = []
+
+    def __call__(self, region, action, body):
+        self.calls.append((region, action, body))
+        want, answer = self.answers.pop(0)
+        assert action == want, (action, want)
+        return answer(body) if callable(answer) else answer
+
+
+SRP_CHALLENGE = {"ChallengeName": "PASSWORD_VERIFIER", "ChallengeParameters": {
+    "USER_ID_FOR_SRP": "uuid-user-1", "SRP_B": format(pow(2, 12345, tok.N), "x"), "SALT": "ab12",
+    "SECRET_BLOCK": "c2VjcmV0"}}
+
+
+def test_sign_in_answers_srp_then_totp_and_returns_the_access_token(monkeypatch):
+    cog = Cognito([
+        ("InitiateAuth", SRP_CHALLENGE),
+        ("RespondToAuthChallenge", {"ChallengeName": "SOFTWARE_TOKEN_MFA", "Session": "s1"}),
+        ("RespondToAuthChallenge", {"AuthenticationResult": {"AccessToken": "header.payload.sig"}}),
+    ])
+    monkeypatch.setattr(tok, "call", cog)
+    monkeypatch.setattr(tok.time, "time", lambda: 59)
+    assert tok.access_token(POOL, "client1", "scanner@example.invalid", PASSWORD, SEED) == "header.payload.sig"
+    (_, _, init), (_, _, pv), (_, _, mfa) = cog.calls
+    assert init["AuthFlow"] == "USER_SRP_AUTH" and init["AuthParameters"]["USERNAME"] == "scanner@example.invalid"
+    assert pv["ChallengeName"] == "PASSWORD_VERIFIER" and pv["ChallengeResponses"]["USERNAME"] == "uuid-user-1"
+    assert mfa["ChallengeResponses"] == {"USERNAME": "uuid-user-1", "SOFTWARE_TOKEN_MFA_CODE": "287082"}
+    assert mfa["Session"] == "s1"
+    assert all(region == "us-east-2" for region, _, _ in cog.calls)
+    assert PASSWORD not in json.dumps([body for _, _, body in cog.calls])
+
+
+def test_an_unexpected_challenge_stops_the_sign_in(monkeypatch):
+    monkeypatch.setattr(tok, "call", Cognito([
+        ("InitiateAuth", SRP_CHALLENGE),
+        ("RespondToAuthChallenge", {"ChallengeName": "NEW_PASSWORD_REQUIRED", "Session": "s"}),
+    ]))
+    with pytest.raises(tok.AuthError, match="NEW_PASSWORD_REQUIRED"):
+        tok.access_token(POOL, "client1", "u", PASSWORD, SEED)
+
+
+def test_enroll_associates_verifies_and_returns_the_seed(monkeypatch):
+    cog = Cognito([
+        ("InitiateAuth", SRP_CHALLENGE),
+        ("RespondToAuthChallenge", {"ChallengeName": "MFA_SETUP", "Session": "s1"}),
+        ("AssociateSoftwareToken", {"SecretCode": SEED, "Session": "s2"}),
+        ("VerifySoftwareToken", {"Status": "SUCCESS", "Session": "s3"}),
+        ("RespondToAuthChallenge", {"AuthenticationResult": {"AccessToken": "t"}}),
+    ])
+    monkeypatch.setattr(tok, "call", cog)
+    monkeypatch.setattr(tok.time, "time", lambda: 59)
+    assert tok.enroll(POOL, "client1", "u", PASSWORD) == SEED
+    assert cog.calls[3][2]["UserCode"] == "287082" and cog.calls[3][2]["Session"] == "s2"
+    assert cog.calls[4][2]["ChallengeName"] == "MFA_SETUP" and cog.calls[4][2]["Session"] == "s3"
+
+
+def _main(monkeypatch, env, argv):
+    for k in ("SILK_DAST_USERNAME", "SILK_DAST_PASSWORD", "SILK_DAST_TOTP_SECRET", "SILK_DAST_USER_POOL_ID",
+              "SILK_DAST_CLIENT_ID"):
+        monkeypatch.delenv(k, raising=False)
+    for k, v in env.items():
+        monkeypatch.setenv(k, v)
+    out, err = io.StringIO(), io.StringIO()
+    with redirect_stdout(out), redirect_stderr(err):
+        rc = tok.main(argv)
+    return rc, out.getvalue(), err.getvalue()
+
+
+FULL = {"SILK_DAST_USERNAME": "u", "SILK_DAST_PASSWORD": PASSWORD, "SILK_DAST_TOTP_SECRET": SEED,
+        "SILK_DAST_USER_POOL_ID": POOL}
+
+
+def test_main_writes_only_the_token_to_an_owner_only_file(monkeypatch, tmp_path):
+    cfg = tmp_path / "auth.json"
+    cfg.write_text(json.dumps({"clientId": "abc123"}))
+    seen = {}
+
+    def fake(pool, cid, user, pw, seed):
+        seen.update(pool=pool, cid=cid)
+        return "the-token"
+    monkeypatch.setattr(tok, "access_token", fake)
+    dest = tmp_path / "token"
+    dest.write_text("stale")
+    dest.chmod(0o644)
+    rc, out, err = _main(monkeypatch, FULL, ["token", "--auth-config", str(cfg), "--out", str(dest)])
+    assert (rc, out, err) == (0, "", "")
+    assert dest.read_text() == "the-token"
+    assert dest.stat().st_mode & 0o777 == 0o600
+    assert seen == {"pool": POOL, "cid": "abc123"}
+
+
+def test_main_requires_an_output_file(monkeypatch):
+    with pytest.raises(SystemExit):
+        _main(monkeypatch, FULL, ["token"])
+
+
+def test_main_refuses_missing_credentials_without_naming_values(monkeypatch):
+    rc, out, err = _main(monkeypatch, {"SILK_DAST_PASSWORD": PASSWORD}, ["token", "--out", "/nonexistent/x"])
+    assert rc == 2 and out == ""
+    assert "SILK_DAST_USERNAME" in err and PASSWORD not in err
+
+
+def test_a_failed_sign_in_says_why_without_secrets(monkeypatch):
+    def boom(*a):
+        raise tok.AuthError("RespondToAuthChallenge: NotAuthorizedException: Incorrect username or password.")
+    monkeypatch.setattr(tok, "access_token", boom)
+    rc, out, err = _main(monkeypatch, {**FULL, "SILK_DAST_CLIENT_ID": "abc"}, ["token", "--out", "/nonexistent/x"])
+    assert rc == 1 and out == ""
+    assert "NotAuthorizedException" in err and PASSWORD not in err and SEED not in err
diff --git a/tests/test_decisions.py b/tests/test_decisions.py
index 56ab7059..31799914 100644
--- a/tests/test_decisions.py
+++ b/tests/test_decisions.py
@@ -35,6 +35,13 @@
     ("duplicate-claim.json", "'CKV_AWS_68' is claimed by both DEC-001 and DEC-002"),
     ("closed-not-remediated.json", "a closed record's disposition must be one of"),
     ("unknown-field.json", "unknown field(s) ['reviewby']"),
+    ("planned-reduction-malformed.json", "planned_reduction must be {date: YYYY-MM-DD, target_pain: N0-N5}"),
+    ("planned-reduction-closed.json", "only an in-force record plans a reduction"),
+    ("automatable-no-evidence.json", "'no' needs its evidence"),
+    ("unconfirmed.json", "an in-force decision needs confirmed_on"),
+    ("marking-in-text.json", "justification carries a drafting or confirmation note"),
+    ("superseded-without-replaced-by.json", "a superseded record needs closed_on and replaced_by"),
+    ("confirmed-before-decided.json", "confirmed_on 2025-12-31 is before decided_on 2026-01-01"),
 ]
 
 
@@ -46,7 +53,9 @@ def _env():
 
 def test_the_committed_register_loads_and_matches_its_schema():
     reg = _decisions.load()
-    assert len(reg["decisions"]) == 39  # 37 carried over from the POA&M, 2 new
+    # The migration range (DEC-001..099): 37 carried over from the POA&M, 2 new.
+    # Later records are added in the blocks below.
+    assert len([r for r in reg["decisions"] if _num(r) < 100]) == 39
     jsonschema = pytest.importorskip("jsonschema")
     jsonschema.validate(json.loads(REGISTER.read_text()), json.loads(SCHEMA.read_text()))
 
@@ -58,7 +67,11 @@ def test_each_known_bad_register_fails_closed_for_its_reason(fixture, reason):
     assert reason in str(exc.value)
 
 
-@pytest.mark.parametrize("fixture", [f for f, _ in KNOWN_BAD if f != "duplicate-claim.json"])
+# The JSON schema cannot express a cross-record claim, a text screen or a date order.
+LOADER_ONLY = {"duplicate-claim.json", "marking-in-text.json", "confirmed-before-decided.json"}
+
+
+@pytest.mark.parametrize("fixture", [f for f, _ in KNOWN_BAD if f not in LOADER_ONLY])
 def test_the_schema_refuses_the_same_registers(fixture):
     # Uniqueness across records is the loader's alone; a schema cannot say it.
     jsonschema = pytest.importorskip("jsonschema")
@@ -132,10 +145,51 @@ def test_every_poam_item_landed_in_the_register_with_its_decision():
         assert r["id"] == "DEC-" + i["id"].split("-")[1], i["id"]
         assert r["disposition"] == POAM_TO_DISPOSITION[i["category"]], i["id"]
         assert r["status"] == ("closed" if i["category"] == "closed" else "in-force"), i["id"]
-        assert r["title"] == i["title"] and r["justification"] == i["description"], i["id"]
+        assert r["title"] == i["title"], i["id"]
+        if (i["id"], "justification") not in AMENDED_SINCE_MIGRATION:
+            assert r["justification"] == _published_text(i["description"]), i["id"]
         for k in ("decided_by", "decided_on", "review_by", "original_detection_date"):
-            assert r.get(k) == i.get(k), (i["id"], k)
-        assert r["applies_to"]["resources"] == i.get("asset_identifiers", []), i["id"]
+            if (i["id"], k) not in AMENDED_SINCE_MIGRATION:
+                assert r.get(k) == i.get(k), (i["id"], k)
+        if (i["id"], "resources") not in AMENDED_SINCE_MIGRATION:
+            assert r["applies_to"]["resources"] == i.get("asset_identifiers", []), i["id"]
+
+
+# Fields corrected after the migration, each for a stated reason; everything
+# else still matches the POA&M item it came from.
+AMENDED_SINCE_MIGRATION = {
+    # Detection dates the POA&M never recorded: the inline Checkov skips for
+    # CKV_AWS_68, CKV_AWS_86/310 and CKV_AWS_117 were added on 2025-06-14
+    # (commit f453e9d, "fixing Checkov findings"), so each was detected by then.
+    ("POAM-007", "original_detection_date"), ("POAM-009", "original_detection_date"),
+    ("POAM-010", "original_detection_date"),
+    # DEC-010 named "aws-lambda::compliance-monitor", which no inventory
+    # component carries; the CKV_AWS_117 skip is global, so it covers every Lambda.
+    ("POAM-010", "resources"),
+    # Wording corrected 2026-11-06, decisions unchanged: DEC-007 said the site had
+    # no authentication endpoints (the Silk Reeling API behind the distribution
+    # has a JWT authorizer), and DEC-009 pointed to the retired POAM-016.
+    ("POAM-007", "justification"), ("POAM-009", "justification"),
+    # DEC-026 cited the retired POAM-025 for the operator's MFA; it now cites DEC-025.
+    ("POAM-026", "justification"),
+    # No recurring manual work (DEC-195), 2026-11-06, each with source.reworded:
+    # DEC-019 restated as rotate-on-compromise; DEC-032 names the nightly
+    # automated audit-log review in place of a quarterly manual one.
+    ("POAM-019", "justification"), ("POAM-032", "justification"),
+}
+
+
+def test_the_post_migration_amendments_are_the_stated_ones():
+    recs = _decisions.records(_decisions.load())
+    assert all(recs[d]["original_detection_date"] == "2025-06-14" for d in ("DEC-007", "DEC-009", "DEC-010"))
+    assert recs["DEC-010"]["applies_to"]["resources"] == [
+        "aws::function::opa_compliance", "aws::function::evidence_watchdog", "aws::function::silk_reeling"]
+    items = {i["id"]: i for i in json.loads((MIG / "poam-items-2026-11-04.json").read_text())["items"]}
+    for dec, poam in (("DEC-007", "POAM-007"), ("DEC-009", "POAM-009")):
+        old, new = items[poam]["description"], recs[dec]["justification"]
+        assert new.startswith(old.split(".")[0] + ".") and "Text corrected 2026-11-06" in new, dec
+    assert "no auth endpoints" not in recs["DEC-007"]["justification"]
+    assert "POAM-016" not in recs["DEC-009"]["justification"]
 
 
 def test_the_check_maps_are_the_ones_the_poam_held():
@@ -146,8 +200,46 @@ def test_the_check_maps_are_the_ones_the_poam_held():
     assert false_pos == rename(frozen["false_positive"])
 
 
+# Text removed from the POA&M wording when it moved to the register, because the
+# register is published (trust-center.json): IAM user names stay out of
+# published output. The parity test applies exactly these and nothing else.
+PUBLICATION_REDACTIONS = {" (saydlette-dev)": ""}
+
+
+def _published_text(text):
+    for old, new in PUBLICATION_REDACTIONS.items():
+        text = text.replace(old, new)
+    return text
+
+
+def test_no_iam_user_name_is_in_published_decision_text():
+    users = {res.split("::", 1)[1] for r in _decisions.load()["decisions"]
+             for res in r["applies_to"]["resources"] if res.startswith("aws-iam-user::")}
+    assert users
+    for r in _decisions.load()["decisions"]:
+        for field in ("title", "justification", "remediation_plan"):
+            assert not any(u in (r.get(field) or "") for u in users), (r["id"], field)
+
+
+def _num(r):
+    return int(r["id"][4:])
+
+
+# Blocks for records added after the migration, one per piece of work, so
+# parallel branches never collide (2026-11-05). DEC-041..099 stay unused: the
+# migration range is closed.
+DEC_BLOCKS = {"certification reports": (100, 129), "notifications": (130, 149),
+              "trust center, scope and assessor": (150, 179), "detection and evaluation": (180, 209)}
+
+
+def test_records_after_the_migration_sit_in_an_allocated_block():
+    for r in _decisions.load()["decisions"]:
+        n = _num(r)
+        assert n <= 40 or any(lo <= n <= hi for lo, hi in DEC_BLOCKS.values()), r["id"]
+
+
 def test_the_only_new_records_are_the_two_dast_false_positives():
-    new = [r for r in _decisions.load()["decisions"] if not r.get("former_id")]
+    new = [r for r in _decisions.load()["decisions"] if not r.get("former_id") and _num(r) < 100]
     assert [(r["id"], r["disposition"], r["applies_to"]["vuln_ids"]) for r in new] == [
         ("DEC-039", "false-positive", ["zap-10099"]), ("DEC-040", "false-positive", ["zap-10036-2"])]
     assert all(r["decided_by"] == "Sam Aydlette" for r in new)
@@ -185,3 +277,22 @@ def test_the_deploy_deletes_the_published_poam_and_fails_if_it_is_still_served()
     # Only a 404 counts as gone; any other error fails the round-trip.
     assert "'(404)'" in check["run"] and "could not confirm" in check["run"]
     assert steps.index(publish) < steps.index(check)
+
+
+def test_every_in_force_record_is_confirmed_and_carries_no_drafting_note():
+    """One marking format (source.drafted_by plus confirmed_on): a record the
+    operator has not confirmed cannot be in force."""
+    for r in _decisions.in_force(_decisions.load()):
+        assert r.get("confirmed_on") and r["confirmed_on"] >= r["decided_on"], r["id"]
+        assert not _decisions.MARKING_RE.search(r["title"] + " " + r["justification"]), r["id"]
+    recs = _decisions.records(_decisions.load())
+    assert all(recs[f"DEC-{n:03d}"]["confirmed_on"] == recs[f"DEC-{n:03d}"]["decided_on"]
+               for n in range(3, 41) if recs.get(f"DEC-{n:03d}", {}).get("status") == "in-force")
+
+
+def test_the_closed_procedural_records_are_superseded_not_remediated():
+    recs = _decisions.records(_decisions.load())
+    for rid in ("DEC-102", "DEC-103", "DEC-104", "DEC-105", "DEC-106", "DEC-190", "DEC-191", "DEC-192"):
+        assert recs[rid]["status"] == "closed" and recs[rid]["disposition"] == "superseded", rid
+        assert recs[rid]["replaced_by"].strip(), rid
+    assert recs["DEC-194"]["status"] == "in-force" and recs["DEC-194"]["confirmed_on"] == "2026-11-06"
diff --git a/tests/test_detect_wiring.py b/tests/test_detect_wiring.py
new file mode 100644
index 00000000..8159c718
--- /dev/null
+++ b/tests/test_detect_wiring.py
@@ -0,0 +1,244 @@
+"""Detection wiring for VDR-CSO-DAC, VDR-CSO-DET and VDR-TFR-PSD/PCD (SAST + DAST).
+
+CodeQL analyses first-party code on change, after each deploy and daily; ZAP
+scans the site and, authenticated, the Silk Reeling API daily and after each
+deploy; both reach the VDR through the detection feeds, the detection gate and
+the builder in the deploy and the nightly; and a missed DAST scan blocks after
+three days. These tests read the workflows as data, and run the feed fetcher
+against a scripted `gh`, so a change that unwires any of it fails here.
+"""
+import json
+import os
+import re
+import stat
+import subprocess
+from pathlib import Path
+
+import pytest
+import yaml
+
+REPO = Path(__file__).resolve().parent.parent
+WF = REPO / ".github" / "workflows"
+DEPLOY = "Deploy Website with OPA Compliance"
+PIN = re.compile(r"^[\w.-]+/[\w./-]+@[0-9a-f]{40}$")
+SECRETS = ("SILK_DAST_USERNAME", "SILK_DAST_PASSWORD", "SILK_DAST_TOTP_SECRET", "SILK_DAST_USER_POOL_ID")
+
+
+def _wf(name):
+    return yaml.safe_load((WF / name).read_text())
+
+
+def _on(wf):
+    return wf.get("on", wf.get(True))  # PyYAML reads the bare key `on` as True
+
+
+def _steps(wf, job=None):
+    jobs = _wf(wf)["jobs"]
+    return [s for name, j in jobs.items() if job in (None, name) for s in j.get("steps", [])]
+
+
+def _step(wf, name, job=None):
+    return next(s for s in _steps(wf, job) if s.get("name") == name)
+
+
+def _guarded(job):
+    cond = " ".join(str(job.get("if", "")).split())
+    return ("github.event.workflow_run.conclusion == 'success'" in cond
+            and "github.event.workflow_run.event != 'pull_request'" in cond)
+
+
+@pytest.mark.parametrize("name", ["codeql.yml", "zap-dast.yml"])
+def test_every_action_is_pinned_by_commit(name):
+    for s in _steps(name):
+        if "uses" in s:
+            assert PIN.match(s["uses"]), s["uses"]
+
+
+def test_codeql_runs_on_change_after_deploy_and_daily():
+    on = _on(_wf("codeql.yml"))
+    assert on["push"]["branches"] == ["main"] and on["pull_request"]["branches"] == ["main"]
+    assert on["schedule"] and on["workflow_run"] == {"workflows": [DEPLOY], "types": ["completed"],
+                                                     "branches": ["main"]}
+    assert _wf("codeql.yml")["permissions"] == {"contents": "read"}
+
+
+def test_codeql_covers_this_repos_code_and_the_silk_reeling_app():
+    jobs = _wf("codeql.yml")["jobs"]
+    assert set(jobs["repo"]["strategy"]["matrix"]["language"]) == {"python", "javascript-typescript", "actions"}
+    assert set(jobs["silk-reeling"]["strategy"]["matrix"]["language"]) == {"python", "javascript-typescript"}
+    for job in jobs.values():
+        assert _guarded(job)
+        assert job["permissions"] == {"contents": "read", "security-events": "write"}
+    silk = jobs["silk-reeling"]
+    assert "github.event_name != 'pull_request'" in silk["if"]
+    init = next(s for s in silk["steps"] if "codeql-action/init@" in s.get("uses", ""))
+    analyze = next(s for s in silk["steps"] if "codeql-action/analyze@" in s.get("uses", ""))
+    assert init["with"]["source-root"] == "silk-reeling"
+    # The database holds the private source; it is never uploaded.
+    assert analyze["with"]["upload-database"] is False
+    fetch = _step("codeql.yml", "Fetch the Silk Reeling source (the ref the deploy builds)")
+    assert "vars.SILK_REELING_REF" in fetch["env"]["SILK_REELING_REF"]
+    assert "rm -rf silk-reeling/.git" in fetch["run"]
+
+
+def test_zap_runs_at_least_every_three_days_and_after_each_deploy():
+    on = _on(_wf("zap-dast.yml"))
+    for entry in on["schedule"]:
+        minute, hour, dom, month, dow = entry["cron"].split()
+        assert (dom, month, dow) == ("*", "*", "*"), entry  # daily
+    assert on["workflow_run"] == {"workflows": [DEPLOY], "types": ["completed"], "branches": ["main"]}
+    assert all(_guarded(j) for j in _wf("zap-dast.yml")["jobs"].values())
+
+
+def test_api_scan_is_authenticated_and_never_prints_the_token():
+    jobs = _wf("zap-dast.yml")["jobs"]
+    assert set(jobs) == {"zap_baseline", "zap_api"}
+    assert jobs["zap_api"]["permissions"] == {"contents": "read"}
+    names = [s.get("name") for s in jobs["zap_api"]["steps"]]
+    sign_in = _step("zap-dast.yml", "Sign in the DAST scanner user (Cognito SRP + TOTP)")
+    assert set(sign_in["env"]) == set(SECRETS)
+    run = sign_in["run"]
+    assert run.index("::add-mask::${token}") < run.index("GITHUB_ENV")
+    assert "echo \"$token\"" not in run and "echo $token" not in run
+    scan = _step("zap-dast.yml", "ZAP API Scan (authenticated)")
+    assert scan["uses"].startswith("zaproxy/action-api-scan@")
+    assert scan["env"]["ZAP_AUTH_HEADER_SITE"] == "samaydlette.com"
+    assert scan["with"]["artifact_name"] == "zap-api-report"
+    assert re.search(r"@sha256:[0-9a-f]{64}$", _wf("zap-dast.yml")["env"]["ZAP_IMAGE"])
+    # The token is proven accepted, and the API proven closed without it, around the scan.
+    check = names.index("Verify the token is accepted and the API refuses without it")
+    after = names.index("Verify the token still held after the scan")
+    assert check < names.index("ZAP API Scan (authenticated)") < after
+    assert '"$without" = 401' in jobs["zap_api"]["steps"][check]["run"]
+    base = _step("zap-dast.yml", "ZAP Baseline Scan")
+    assert base["with"]["artifact_name"] == "zap-dast-report"
+
+
+@pytest.mark.parametrize("wf,job", [("deploy-with-opa.yml", "deploy"), ("evidence-nightly.yml", "refresh")])
+def test_publishers_fetch_gate_and_build_with_codeql_and_the_api_scan(wf, job):
+    perms = _wf(wf)["jobs"][job]["permissions"]
+    assert perms.get("security-events") == "read" and perms.get("actions") == "read"
+    steps = _steps(wf, job)
+    names = [s.get("name") for s in steps]
+    fetch = steps[names.index("Fetch detection feeds")]
+    assert fetch["env"]["ACTIONS_TOKEN"] == "${{ secrets.GITHUB_TOKEN }}"
+    gate = steps[names.index("Detection gate (G7)")]["run"]
+    assert "--codeql codeql-alerts.json" in gate and "--zap-api zap-api-report.json" in gate
+    build = steps[names.index("Build VDR Report (FedRAMP 20x Class C)")]["run"]
+    for arg in ("--codeql codeql-alerts.json", "--zap-api zap-api-report.json", "--zap zap-report.json",
+                "--zap-max-age-days 3"):
+        assert arg in build, arg
+    assert names.index("Fetch detection feeds") < names.index("Detection gate (G7)") \
+        < names.index("Build VDR Report (FedRAMP 20x Class C)")
+
+
+def test_deploy_stops_before_apply_without_the_scanner_credentials():
+    steps = _steps("deploy-with-opa.yml", "deploy")
+    names = [s.get("name") for s in steps]
+    req = steps[names.index("Require the DAST scanner credentials")]
+    assert set(req["env"]) == set(SECRETS)
+    assert all(req["env"][k] == "${{ secrets.%s }}" % k for k in SECRETS)
+    assert "exit 1" in req["run"] and "echo \"${!k" not in req["run"]
+    assert names.index("Require the DAST scanner credentials") < names.index("Terraform Apply")
+
+
+def _bad_secrets_check(tmp_path, env):
+    req = _step("deploy-with-opa.yml", "Require the DAST scanner credentials", "deploy")
+    script = tmp_path / "check.sh"
+    script.write_text(req["run"])
+    base = {k: v for k, v in os.environ.items() if not k.startswith("SILK_DAST_")}
+    return subprocess.run(["bash", "-e", str(script)], env={**base, **env}, capture_output=True, text=True)
+
+
+def test_the_credentials_check_fails_on_a_missing_secret_and_passes_with_all(tmp_path):
+    full = {k: "x" for k in SECRETS}
+    assert _bad_secrets_check(tmp_path, full).returncode == 0
+    r = _bad_secrets_check(tmp_path, {**full, "SILK_DAST_TOTP_SECRET": ""})
+    assert r.returncode == 1 and "SILK_DAST_TOTP_SECRET" in r.stdout
+
+
+# ---------------------------------------------------------------- feed fetcher
+
+FAKE_GH = r"""#!/usr/bin/env bash
+# Scripted gh: answers from $FAKE_DIR, logs every call.
+echo "$*" >> "$FAKE_DIR/calls.log"
+case "$1 $2" in
+  "run list") echo "${FAKE_RUN_ID:-}"; exit 0 ;;
+  "run download")
+    shift 2; name=""; dir=""
+    while [ $# -gt 0 ]; do case "$1" in -n) name=$2; shift 2;; -D) dir=$2; shift 2;; *) shift;; esac; done
+    [ -f "$FAKE_DIR/$name.json" ] || exit 1
+    mkdir -p "$dir" && cp "$FAKE_DIR/$name.json" "$dir/report_json.json"; exit 0 ;;
+esac
+if [ "$1" = api ]; then
+  for a in "$@"; do
+    case "$a" in
+      */code-scanning/analyses*) [ -f "$FAKE_DIR/analyses.json" ] || { echo "gh: no analysis found (HTTP 404)" >&2; exit 1; }
+                                 cat "$FAKE_DIR/analyses.json"; exit 0 ;;
+      */code-scanning/alerts*) cat "$FAKE_DIR/alerts-p1.json" "$FAKE_DIR/alerts-p2.json"; exit 0 ;;
+      */dependabot/alerts*) echo '[]'; exit 0 ;;
+    esac
+  done
+fi
+exit 1
+"""
+
+
+def _fetch(tmp_path, *, run_id="42", analyses=True, artifacts=("zap-dast-report", "zap-api-report")):
+    fake = tmp_path / "fake"
+    (fake / "bin").mkdir(parents=True)
+    gh = fake / "bin" / "gh"
+    gh.write_text(FAKE_GH)
+    gh.chmod(gh.stat().st_mode | stat.S_IEXEC)
+    curl = fake / "bin" / "curl"
+    curl.write_text("#!/usr/bin/env bash\nexit 22\n")  # every public feed unreachable: not under test here
+    curl.chmod(curl.stat().st_mode | stat.S_IEXEC)
+    if analyses:
+        (fake / "analyses.json").write_text(json.dumps([
+            {"category": "/language:python", "created_at": "2026-11-04T05:41:00Z", "error": "",
+             "results_count": 1, "commit_sha": "a" * 40, "tool": {"name": "CodeQL", "version": "2.23"},
+             "url": "https://api.github.com/x", "sarif_id": "zzz"}]))
+    alert = {"number": 9, "state": "open", "created_at": "2026-11-03T00:00:00Z", "html_url": "https://github.com/x",
+             "rule": {"id": "js/xss", "name": "js/xss", "description": "XSS", "severity": "error",
+                      "security_severity_level": "high", "tags": ["security"]},
+             "most_recent_instance": {"ref": "refs/heads/main", "category": "/language:javascript-typescript",
+                                      "location": {"path": "website/assets/js/trust.js", "start_line": 3},
+                                      "message": {"text": "m"}}}
+    (fake / "alerts-p1.json").write_text(json.dumps([alert]))
+    (fake / "alerts-p2.json").write_text(json.dumps([{**alert, "number": 10}]))
+    for a in artifacts:
+        (fake / f"{a}.json").write_text(json.dumps({"@generated": "Wed, 4 Nov 2026 06:00:00", "site": [], "a": a}))
+    work = tmp_path / "work"
+    work.mkdir()
+    env = {**os.environ, "PATH": f"{fake / 'bin'}:{os.environ['PATH']}", "FAKE_DIR": str(fake),
+           "FAKE_RUN_ID": run_id, "SITE_ORIGIN": "https://example.invalid", "GITHUB_REPOSITORY": "o/r",
+           "DEPENDABOT_TOKEN": "d", "ACTIONS_TOKEN": "t"}
+    r = subprocess.run(["bash", str(REPO / "scripts" / "fetch-detection-feeds.sh")], cwd=work, env=env,
+                       capture_output=True, text=True)
+    assert r.returncode == 0, r.stderr
+    return work, (fake / "calls.log").read_text()
+
+
+def test_fetcher_takes_codeql_alerts_and_both_zap_reports(tmp_path):
+    work, calls = _fetch(tmp_path)
+    doc = json.loads((work / "codeql-alerts.json").read_text())
+    assert [a["number"] for a in doc["alerts"]] == [9, 10]  # every page
+    assert set(doc["alerts"][0]) == {"number", "state", "created_at", "rule", "most_recent_instance"}
+    assert "html_url" not in json.dumps(doc) and "sarif_id" not in json.dumps(doc)
+    assert doc["analyses"][0]["category"] == "/language:python"
+    assert "tool_name=CodeQL" in calls and "state=open" in calls and "ref=refs/heads/main" in calls
+    assert json.loads((work / "zap-report.json").read_text())["a"] == "zap-dast-report"
+    assert json.loads((work / "zap-api-report.json").read_text())["a"] == "zap-api-report"
+    # The latest successful main-branch run, whatever its trigger: no --event filter.
+    run_list = next(line for line in calls.splitlines() if line.startswith("run list"))
+    assert "--branch main" in run_list and "--status success" in run_list and "--event" not in run_list
+    assert run_list.count("zap-dast.yml") == 1 and calls.count("run download 42") == 2
+
+
+def test_fetcher_never_substitutes_a_missing_codeql_or_api_report(tmp_path):
+    work, _ = _fetch(tmp_path, analyses=False, artifacts=("zap-dast-report",))
+    assert not (work / "codeql-alerts.json").exists()
+    assert "no analysis found" in (work / "codeql-alerts.json.error").read_text()
+    assert not (work / "zap-api-report.json").exists()
+    assert "zap-api-report" in (work / "zap-api-report.json.error").read_text()
+    assert (work / "zap-report.json").exists()
diff --git a/tests/test_detection_gate.py b/tests/test_detection_gate.py
index 6c31c0a0..6d21996c 100644
--- a/tests/test_detection_gate.py
+++ b/tests/test_detection_gate.py
@@ -21,7 +21,8 @@
 NOW = "2026-11-04T12:00:00+00:00"
 
 GOOD = {"kev": "kev.json", "epss": "epss.csv", "grype": "grype.json", "dependabot": "dependabot.json",
-        "previous-vdr": "previous-vdr.json", "checkov": "checkov.sarif", "tfsec": "tfsec.json"}
+        "previous-vdr": "previous-vdr.json", "checkov": "checkov.sarif", "tfsec": "tfsec.json",
+        "codeql": "codeql.json", "zap-api": "zap-api.json"}
 
 
 def _load():
@@ -60,7 +61,7 @@ def test_all_good_inputs_pass(tmp_path):
     assert summary["result"] == "ok" and {f["feed"] for f in summary["feeds"]} == set(GOOD)
     assert all(f["status"] == "ok" and f["mode"] == "block" for f in summary["feeds"])
     assert {f["feed"]: f["age_hours"] for f in summary["feeds"] if f["age_hours"] is not None} == \
-        {"kev": 19.0, "epss": 12.0, "grype": 5.7}
+        {"kev": 19.0, "epss": 12.0, "grype": 5.7, "codeql": 6.3, "zap-api": 6.0}
 
 
 @pytest.mark.parametrize("feed,bad,reason", [
@@ -77,6 +78,15 @@ def test_all_good_inputs_pass(tmp_path):
     ("previous-vdr", "previous-vdr-bad.json", "no findings[]"),
     ("checkov", "checkov-fallback.sarif", "the empty fallback document"),
     ("tfsec", "absent.json", "missing"),
+    ("codeql", "codeql-missing.json", "no analysis found (HTTP 404)"),
+    ("codeql", "codeql-stale.json", "oldest required analysis is 100.0h old (max 72h)"),
+    ("codeql", "codeql-missing-category.json", "no analysis on main for /silk-reeling/language:javascript-typescript"),
+    ("codeql", "codeql-error.json", "the latest analysis for /language:actions reported an error"),
+    ("codeql", "codeql-no-alerts-key.json", "no alerts[] and analyses[]"),
+    ("zap-api", "zap-api-stale.json", "@generated is 102.0h old (max 72h)"),
+    ("zap-api", "zap-api-empty.json", "no site[]"),
+    ("zap-api", "zap-api-undated.json", "@generated absent or unparseable"),
+    ("zap-api", "absent.json", "missing (no file produced)"),
 ])
 def test_t52_each_failed_input_fails_the_gate_for_its_reason(tmp_path, feed, bad, reason):
     rc, summary, err = run(tmp_path, **{feed: bad})
@@ -171,3 +181,31 @@ def test_a_missing_dast_report_now_blocks_the_build(tmp_path):
                         "--output", "out.json"], cwd=work, capture_output=True, text=True, env=env)
     assert r.returncode == 1 and "No ZAP report at zap-report.json (no zap-dast-report artifact)" in r.stderr
     assert not (work / "out.json").exists()
+
+
+def test_codeql_requires_every_category_the_workflow_produces():
+    """The gate's required categories are exactly the ones codeql.yml uploads,
+    so a language dropped from the workflow (or added without a window) fails here."""
+    import yaml
+    wf = yaml.safe_load((REPO / ".github" / "workflows" / "codeql.yml").read_text())
+    produced = set()
+    for job in wf["jobs"].values():
+        analyze = next(st for st in job["steps"] if "codeql-action/analyze@" in st.get("uses", ""))
+        for lang in job["strategy"]["matrix"]["language"]:
+            produced.add(analyze["with"]["category"].replace("${{ matrix.language }}", lang))
+    assert set(_load().load_config()["feeds"]["codeql"]["categories"]) == produced
+
+
+def test_codeql_and_zap_api_windows_are_the_class_c_three_days():
+    cfg = _load().load_config()
+    assert cfg["feeds"]["codeql"]["max_age_hours"] == 72
+    assert cfg["feeds"]["zap-api"]["max_age_hours"] == 72
+
+
+def test_codeql_config_without_categories_fails_closed(tmp_path):
+    cfg = json.loads(CONFIG.read_text())
+    cfg["feeds"]["codeql"]["categories"] = []
+    p = tmp_path / "c.json"
+    p.write_text(json.dumps(cfg))
+    with pytest.raises(SystemExit, match="codeql.categories"):
+        _load().load_config(p)
diff --git a/tests/test_dispositions_mitigations.py b/tests/test_dispositions_mitigations.py
index f5b729f0..bf029417 100644
--- a/tests/test_dispositions_mitigations.py
+++ b/tests/test_dispositions_mitigations.py
@@ -143,7 +143,9 @@ def test_t15_control_protected_finding_is_fully_mitigated_at_the_lowest_level():
     assert r["current_disposition"] == "mitigated"
     assert r["fully_mitigated"] is True
     assert r["likely_exploitable"] is False and r["lev_basis"] == "fully-mitigated"
-    assert r["current_pain"] == vdr._rules.impact_levels()[0]
+    # VER-EVA-EPA's lowest level, N0 since October 2026: an impact removed entirely.
+    # (The timeframe table, VDR-TFR-PVR, starts at N1; N0 has no timeframe.)
+    assert r["current_pain"] == "N0"
     assert r["remediation_due_at"] is None and r["is_blocking"] is False
 
 
diff --git a/tests/test_edge_access_logging.py b/tests/test_edge_access_logging.py
new file mode 100644
index 00000000..ccb00cca
--- /dev/null
+++ b/tests/test_edge_access_logging.py
@@ -0,0 +1,191 @@
+"""CDS-TRC-ACL: access to the certification data is logged, within the
+operator's privacy limits, and only monthly aggregates are published."""
+import gzip
+import importlib.util
+import json
+import re
+from datetime import datetime, timezone
+from pathlib import Path
+
+import pytest
+
+REPO = Path(__file__).resolve().parent.parent
+FIX = REPO / "tests" / "fixtures" / "edge-access-logging"
+
+
+def _load(name, file):
+    spec = importlib.util.spec_from_file_location(name, REPO / "scripts" / file)
+    mod = importlib.util.module_from_spec(spec)
+    spec.loader.exec_module(mod)
+    return mod
+
+
+chk = _load("edge_check", "check-edge-access-logging.py")
+summ = _load("access_summary", "build-access-summary.py")
+NAME = "samaydlette-com-edge-access"
+NOW = datetime(2026, 11, 5, 12, tzinfo=timezone.utc)
+
+
+def _j(p):
+    return json.loads((FIX / p).read_text())
+
+
+# --- the configuration check --------------------------------------------------------
+
+def test_the_allowlist_equals_the_bootstrap_delivery_fields():
+    tf = (REPO / "infrastructure" / "bootstrap" / "trust-access-logs.tf").read_text()
+    block = re.search(r"edge_access_log_fields = \[(.*?)\]", tf, re.S).group(1)
+    assert tuple(re.findall(r'"([^"]+)"', block)) == chk.ALLOWED_FIELDS
+    assert "local.edge_access_log_fields" in tf
+
+
+def test_no_identifying_field_is_allowed():
+    assert not set(chk.ALLOWED_FIELDS) & set(chk.IDENTIFYING)
+
+
+def test_the_good_configuration_passes():
+    assert chk.problems(_j("good-deliveries.json"), _j("delivery-source.json"), NAME) == []
+
+
+def test_the_known_bad_fixture_fails_for_identifying_fields(capsys):
+    rc = chk.main(["--deliveries", str(FIX / "known-bad-deliveries.json"),
+                   "--source", str(FIX / "delivery-source.json"), "--name", NAME])
+    assert rc == 1
+    err = capsys.readouterr().err
+    assert "c-ip" in err and "cs-uri-query" in err and "cs(User-Agent)" in err
+
+
+def test_no_delivery_fails_the_deploy(tmp_path):
+    (tmp_path / "d.json").write_text('{"deliveries": []}')
+    rc = chk.main(["--deliveries", str(tmp_path / "d.json"), "--source", str(tmp_path / "absent.json"),
+                   "--name", NAME])
+    assert rc == 1
+
+
+def test_a_source_that_is_not_the_distribution_fails():
+    src = {"deliverySource": {"name": NAME, "logType": "ACCESS_LOGS", "resourceArns": ["arn:aws:s3:::x"]}}
+    assert any("not a CloudFront" in p for p in chk.problems(_j("good-deliveries.json"), src, NAME))
+
+
+def test_a_field_outside_the_allowlist_fails_even_if_not_named_identifying():
+    d = _j("good-deliveries.json")
+    d["deliveries"][0]["recordFields"].append("x-edge-request-id")
+    assert any("outside the privacy allowlist" in p for p in chk.problems(d, _j("delivery-source.json"), NAME))
+
+
+def test_the_deploy_checks_logging_before_the_sdr_and_publishes_the_summary():
+    wf = (REPO / ".github" / "workflows" / "deploy-with-opa.yml").read_text()
+    step = wf.index("- name: Check edge access logging and build the access summary")
+    assert step < wf.index("- name: Build Security Decision Record")
+    body = wf[step:wf.index("\n    - name:", step + 10)]
+    assert "check-edge-access-logging.py" in body and "build-access-summary.py" in body
+    assert "access-summary.bundle access-summary.json" in wf
+
+
+def test_raw_edge_records_expire_after_90_days():
+    tf = (REPO / "infrastructure" / "logging.tf").read_text()
+    for prefix in ('prefix = "cloudfront/"', 'CloudFront/" }'):
+        i = tf.index(prefix)
+        assert "expiration { days = 90 }" in tf[i:i + 200]
+
+
+# --- the summary ----------------------------------------------------------------------
+
+def _rec(day, stem, status=200, cc="US", **extra):
+    return {"date": day, "time": "10:00:00", "cs-uri-stem": stem, "sc-status": str(status), "c-country": cc, **extra}
+
+
+def test_only_trust_paths_are_counted_and_nothing_identifying_survives():
+    recs = [_rec("2026-11-02", "/.well-known/ksi-signal.json"),
+            _rec("2026-11-02", "/trust/index.html", cc="DE"),
+            _rec("2026-11-03", "/index.html"),
+            _rec("2026-11-03", "/.well-known/wp-login.php", status=404),
+            _rec("2026-11-03", "/.well-known/